FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to br.com.anter…
FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPDataSource (aka Anteros-DBCP).
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
https://cwe.mitre.org/data/definitions/502.html →Open in CWE collection →The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.
https://cwe.mitre.org/data/definitions/96.html →Open in CWE collection →An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
https://capec.mitre.org/data/definitions/35.html →Open in CAPEC collection →An attack of this type involves an adversary inserting malicious characters (such as a XSS redirection) into a filename, directly or indirectly that is then used by the target software to generate HTML text or other potentially executable content. Many websites rely on user-generated content and dynamically build resources like files, filenames, and URL links directly from user supplied data. In this attack pattern, the attacker uploads code that can execute in the client browser and/or redirect the client browser to a site that the attacker owns. All XSS attack payload variants can be used to pass and exploit these vulnerabilities.
https://capec.mitre.org/data/definitions/73.html →Open in CAPEC collection →This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.
https://capec.mitre.org/data/definitions/77.html →Open in CAPEC collection →Web Logs Tampering attacks involve an attacker injecting, deleting or otherwise tampering with the contents of web logs typically for the purposes of masking other malicious behavior. Additionally, writing malicious data to log files may target jobs, filters, reports, and other agents that process the logs in an asynchronous attack pattern. This pattern of attack is similar to "Log Injection-Tampering-Forging" except that in this case, the attack is targeting the logs of the web server and not the application.
https://capec.mitre.org/data/definitions/81.html →Open in CAPEC collection →This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.
https://capec.mitre.org/data/definitions/85.html →Open in CAPEC collection →An adversary attempts to exploit an application by injecting additional, malicious content during its processing of serialized objects. Developers leverage serialization in order to convert data or state into a static, binary format for saving to disk or transferring over a network. These objects are then deserialized when needed to recover the data/state. By injecting a malformed object into a vulnerable application, an adversary can potentially compromise the application by manipulating the deserialization process. This can result in a number of unwanted outcomes, including remote code execution.
https://capec.mitre.org/data/definitions/586.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| jackson-databind | Tracked | |
| active_iq_unified_manager | * | Tracked |
| agile_plm | * | Tracked |
| application_testing_suite | * | Tracked |
| autovue_for_agile_product_lifecycle_management | * | Tracked |
| banking_liquidity_management | * | Tracked |
| banking_supply_chain_finance | * | Tracked |