7 CVE-2020-9484
Patch Exploit
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter="null" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.
https://nvd.nist.gov/vuln/detail/CVE-2020-9484
Categories
CWE-502 : Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Marshaling and unmarshaling are effectively synonyms for serialization and deserialization, respectively. In Python, the "pickle" functionality is used to perform serialization and deserialization. Some PHP application researchers use this term when attacking unsafe use of the unserialize() function; but it is also used for CWE-915. Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.) If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified. When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe. Explicitly define a final object() to prevent deserialization. Avoid having unnecessary types or gadgets available that can be leveraged for malicious ends. This limits the potential for unintended or unauthorized types and gadgets to be leveraged by the attacker. Add only acceptable classes to an allowlist. Note: new gadgets are constantly being discovered, so this alone is not a sufficient mitigation. chain: bypass of untrusted deserialization issue (CWE-502) by using an assumed-trusted class (CWE-183) Deserialization issue in commonly-used Java library allows remote execution. Deserialization issue in commonly-used Java library allows remote execution. Use of PHP unserialize function on untrusted input allows attacker to modify application configuration. Use of PHP unserialize function on untrusted input in content management system might allow code execution. Use of PHP unserialize function on untrusted input in content management system allows code execution using a crafted cookie value. Content management system written in PHP allows unserialize of arbitrary objects, possibly allowing code execution. Python script allows local users to execute code via pickled data. Unsafe deserialization using pickle in a Python script. Web browser allows execution of native methods via a crafted string to a JavaScript function that deserializes the string.
References
security@apache.org Patch
CPE
cpe | start | end |
---|---|---|
Configuration 1 | ||
cpe:2.3:a:apache:tomcat:*:*:*:*:*:*:*:* | >= 7.0.0 | < 7.0.108 |
cpe:2.3:a:apache:tomcat:*:*:*:*:*:*:*:* | >= 8.5.0 | < 8.5.63 |
cpe:2.3:a:apache:tomcat:*:*:*:*:*:*:*:* | >= 9.0.1 | < 9.0.43 |
cpe:2.3:a:apache:tomcat:9.0.0:milestone1:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone10:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone11:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone12:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone13:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone14:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone15:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone16:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone17:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone18:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone19:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone2:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone20:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone21:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone22:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone23:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone24:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone25:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone26:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone27:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone3:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone4:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone5:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone6:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone7:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone8:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:9.0.0:milestone9:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:10.0.0:milestone1:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:10.0.0:milestone2:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:10.0.0:milestone3:*:*:*:*:*:* | ||
cpe:2.3:a:apache:tomcat:10.0.0:milestone4:*:*:*:*:*:* | ||
Configuration 2 | ||
cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:* | ||
cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:* | ||
cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:* | ||
Configuration 3 | ||
cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:* | ||
Configuration 4 | ||
cpe:2.3:o:fedoraproject:fedora:31:*:*:*:*:*:*:* | ||
cpe:2.3:o:fedoraproject:fedora:32:*:*:*:*:*:*:* | ||
Configuration 5 | ||
cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:* | ||
cpe:2.3:o:canonical:ubuntu_linux:20.04:*:*:*:lts:*:*:* | ||
Configuration 6 | ||
cpe:2.3:a:oracle:agile_engineering_data_management:6.2.1.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:agile_plm:9.3.3:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:agile_plm:9.3.5:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:agile_plm:9.3.6:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:communications_cloud_native_core_binding_support_function:1.10.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:communications_cloud_native_core_policy:1.14.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:communications_diameter_signaling_router:*:*:*:*:*:*:*:* | >= 8.0.0.0 | <= 8.4.0.5 |
cpe:2.3:a:oracle:communications_element_manager:*:*:*:*:*:*:*:* | >= 8.2.0 | <= 8.2.2 |
cpe:2.3:a:oracle:communications_instant_messaging_server:10.0.1.4.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:communications_session_report_manager:*:*:*:*:*:*:*:* | >= 8.2.0 | <= 8.2.2 |
cpe:2.3:a:oracle:communications_session_route_manager:*:*:*:*:*:*:*:* | >= 8.2.0 | <= 8.2.2 |
cpe:2.3:a:oracle:database:12.2.0.1:*:*:*:enterprise:*:*:* | ||
cpe:2.3:a:oracle:database:19c:*:*:*:enterprise:*:*:* | ||
cpe:2.3:a:oracle:database:21c:*:*:*:enterprise:*:*:* | ||
cpe:2.3:a:oracle:fmw_platform:12.2.1.3.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:fmw_platform:12.2.1.4.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:hospitality_guest_access:4.2.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:hospitality_guest_access:4.2.1:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:instantis_enterprisetrack:*:*:*:*:*:*:*:* | >= 17.1 | <= 17.3 |
cpe:2.3:a:oracle:managed_file_transfer:12.2.1.3.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:managed_file_transfer:12.2.1.4.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:mysql_enterprise_monitor:*:*:*:*:*:*:*:* | <= 8.0.21 | |
cpe:2.3:a:oracle:retail_order_broker:15.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:siebel_apps_-_marketing:*:*:*:*:*:*:*:* | <= 21.9 | |
cpe:2.3:a:oracle:siebel_ui_framework:*:*:*:*:*:*:*:* | <= 20.12 | |
cpe:2.3:a:oracle:transportation_management:6.3.7:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:workload_manager:12.2.0.1:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:workload_manager:18c:*:*:*:*:*:*:* | ||
cpe:2.3:a:oracle:workload_manager:19c:*:*:*:*:*:*:* | ||
Configuration 7 | ||
cpe:2.3:a:mcafee:epolicy_orchestrator:5.9.0:*:*:*:*:*:*:* | ||
cpe:2.3:a:mcafee:epolicy_orchestrator:5.9.1:*:*:*:*:*:*:* | ||
cpe:2.3:a:mcafee:epolicy_orchestrator:5.10.0:-:*:*:*:*:*:* | ||
cpe:2.3:a:mcafee:epolicy_orchestrator:5.10.0:update_1:*:*:*:*:*:* | ||
cpe:2.3:a:mcafee:epolicy_orchestrator:5.10.0:update_2:*:*:*:*:*:* | ||
cpe:2.3:a:mcafee:epolicy_orchestrator:5.10.0:update_3:*:*:*:*:*:* |
REMEDIATION
Patch
EXPLOITS
Exploit-db.com
id | description | date | |
---|---|---|---|
No known exploits |
POC Github
Other Nist (github, ...)
Url |
---|
No known exploits |
CAPEC
Common Attack Pattern Enumerations and Classifications
id | description | severity |
---|---|---|
586 | Object Injection |
High |
Cybersecurity needs ?
Strengthen software security from the outset with our DevSecOps expertise
Integrate security right from the start of the software development cycle for more robust applications and greater customer confidence.
Our team of DevSecOps experts can help you secure your APIs, data pipelines, CI/CD chains, Docker containers and Kubernetes deployments.