Findings for Critical #57
Comments
|
Finding [138476501|https://app.armorcode.com/#/findings/185/656/138476501] status changed from Open to Confirmed |
|
Finding [138476506|https://app.armorcode.com/#/findings/185/656/138476506] status changed from Open to Confirmed |
|
Finding [138476479|https://app.armorcode.com/#/findings/185/656/138476479] status changed from Open to Confirmed |
|
Finding [138476515|https://app.armorcode.com/#/findings/185/656/138476515] status changed from Open to Confirmed |
|
Finding [138476476|https://app.armorcode.com/#/findings/185/656/138476476] status changed from Open to Confirmed |
|
Finding [138476508|https://app.armorcode.com/#/findings/185/656/138476508] status changed from Open to Confirmed |
|
Finding [138476469|https://app.armorcode.com/#/findings/185/656/138476469] status changed from Open to Confirmed |
|
Finding [138476500|https://app.armorcode.com/#/findings/185/656/138476500] status changed from Open to Confirmed |
|
Finding [138476521|https://app.armorcode.com/#/findings/185/656/138476521] status changed from Open to Confirmed |
|
Finding [138476504|https://app.armorcode.com/#/findings/185/656/138476504] status changed from Open to Confirmed |
|
Finding [138476470|https://app.armorcode.com/#/findings/185/656/138476470] status changed from Open to Confirmed |
|
Finding [138476502|https://app.armorcode.com/#/findings/185/656/138476502] status changed from Open to Confirmed |
|
Finding [138476509|https://app.armorcode.com/#/findings/185/656/138476509] status changed from Open to Confirmed |
|
Finding [138476473|https://app.armorcode.com/#/findings/185/656/138476473] status changed from Open to Confirmed |
|
Finding [138476514|https://app.armorcode.com/#/findings/185/656/138476514] status changed from Open to Confirmed |
|
Finding [138476472|https://app.armorcode.com/#/findings/185/656/138476472] status changed from Open to Confirmed |
|
Finding [138476503|https://app.armorcode.com/#/findings/185/656/138476503] status changed from Open to Confirmed |
|
Finding [138476507|https://app.armorcode.com/#/findings/185/656/138476507] status changed from Open to Confirmed |
|
Finding [138476477|https://app.armorcode.com/#/findings/185/656/138476477] status changed from Open to Confirmed |
Findings for Critical
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a malicious payload.
References:
A deserialization flaw was discovered in the jackson-databind, versions before 2.6.7.1, 2.7.9.1 and 2.8.9, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper.
References:
FasterXML jackson-databind 2.x before 2.6.7.4, 2.7.x before 2.7.9.7, 2.8.x before 2.8.11.5 and 2.9.x before 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter.
References:
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to com.ibatis.sqlmap.engine.transaction.jta.JtaTransactionConfig (aka ibatis-sqlmap).
References:
jackson-databind in versions prior to 2.8.10 and 2.9.1, contain a deserialization flaw which allows an unauthenticated user to perform code execution by sending maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaw CVE-2017-7525, blacklisting additonal vulnerable classes.
References:
FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the blaze-ds-opt and blaze-ds-core classes from polymorphic deserialization.
References:
An issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.5. Use of Jackson default typing along with a gadget class from iBatis allows exfiltration of content. Fixed in 2.7.9.4, 2.8.11.2, and 2.9.6.
References:
A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.
References:
SubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2 mishandles default typing when ehcache is used (because of net.sf.ehcache.transaction.manager.DefaultTransactionManagerLookup), leading to remote code execution.
References:
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.
References:
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the p6spy (3.8.6) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of com.p6spy.engine.spy.P6DataSource mishandling.
References:
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.
References:
FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the slf4j-ext class from polymorphic deserialization.
References:
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariDataSource. This is a different vulnerability than CVE-2019-14540.
References:
FasterXML jackson-databind 2.x before 2.6.7.4, 2.7.x before 2.7.9.7, 2.8.x before 2.8.11.5 and 2.9.x before 2.9.10.2 lacks certain net.sf.ehcache blocking.
References:
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the commons-dbcp (1.4) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of org.apache.commons.dbcp.datasources.SharedPoolDataSource and org.apache.commons.dbcp.datasources.PerUserPoolDataSource mishandling.
References:
FasterXML jackson-databind before 2.8.11.1 and 2.9.x before 2.9.5 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the c3p0 libraries are available in the classpath.
References:
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPConfig (aka anteros-core).
References:
FasterXML jackson-databind through 2.8.10 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the Spring libraries are available in the classpath.
References:
The text was updated successfully, but these errors were encountered: