Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
85 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
FasterXML jackson-databind 2.x before 2.9.10.4, 2.8.11.6, and 2.7.9.7 mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPConfig (aka anteros-core).
Recommended action: Upgrade to 2.9.10.4, 2.8.11.6 or 2.7.9.7 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A flaw was discovered in jackson-databind in versions before 2.9.10, 2.8.11.5, and 2.6.7.3, where it would permit polymorphic deserialization of a malicious object using commons-configuration 1 and 2 JNDI classes. An attacker could use this flaw to execute arbitrary code.
Recommended action: Upgrade to 2.9.10, 2.8.11.5 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.aoju.bus.proxy.provider.remoting.RmiProvider (aka bus-proxy).
Recommended action: Upgrade to 2.9.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.activemq. (aka activemq-jms, activemq-core, activemq-pool, and activemq-pool-jms).
Recommended action: Upgrade to 2.9.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.openjpa.ee.WASRegistryManagedRuntime (aka openjpa).
Recommended action: Upgrade to 2.9.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.springframework.aop.config.MethodLocatingFactoryBean (aka spring-aop).
Recommended action: Upgrade to 2.9.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to javax.swing.JEditorPane.
Recommended action: Upgrade to 2.9.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.hadoop.shaded.com.zaxxer.hikari.HikariConfig (aka shaded hikari-config).
Recommended action: Upgrade to 2.9.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.jelly.impl.Embedded (aka commons-jelly).
Recommended action: Upgrade to 2.9.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.aries.transaction.jms.internal.XaPooledConnectionFactory (aka aries.transaction.jms).
Recommended action: Upgrade to 2.9.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
2.7.9.72.6.7.42.9.10.32.8.11.5· Vendor fix available
Issue
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.
Recommended action: Upgrade to 2.9.10.3, 2.8.11.5, 2.7.9.7 or 2.6.7.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
2.7.9.72.9.10.22.6.7.42.8.11.5· Vendor fix available
Issue
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.
Recommended action: Upgrade to 2.9.10.2, 2.8.11.5, 2.7.9.7 or 2.6.7.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 prior to 2.9.10.1, 2.8.11.5, and 2.6.7.3. 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.
Recommended action: Upgrade to 2.9.10.1, 2.8.11.5 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 prior to 2.9.10.1, 2.8.11.5, and 2.6.7.3. 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.
Recommended action: Upgrade to 2.9.10.1, 2.8.11.5 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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.
Recommended action: Upgrade to 2.9.10.1, 2.8.11.5 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10, 2.8.11.5, and 2.6.7.3. It is related to com.zaxxer.hikari.HikariDataSource. This is a different vulnerability than CVE-2019-14540.
Recommended action: Upgrade to 2.9.10, 2.8.11.5 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10, 2.8.11.5, and 2.6.7.3. It is related to com.zaxxer.hikari.HikariConfig.
Recommended action: Upgrade to 2.9.10, 2.8.11.5 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
2.8.11.42.6.7.32.9.9.22.7.9.6· Vendor fix available
Issue
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9.2, 2.8.11.4, 2.7.9.6, and 2.6.7.3. This occurs when Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the logback jar in the classpath.
Recommended action: Upgrade to 2.9.9.2, 2.8.11.4, 2.7.9.6 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
SubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2, 2.8.11.4, and 2.7.9.6 mishandles default typing when ehcache is used (because of net.sf.ehcache.transaction.manager.DefaultTransactionManagerLookup), leading to remote code execution.
Recommended action: Upgrade to 2.9.9.2, 2.8.11.4 or 2.7.9.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
2.8.11.42.6.7.32.9.9.12.7.9.6· Vendor fix available
Issue
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x through 2.9.9. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has JDOM 1.x or 2.x jar in the classpath, an attacker can send a specifically crafted JSON message that allows them to read arbitrary local files on the server.
Recommended action: Upgrade to 2.9.9.1, 2.8.11.4, 2.7.9.6 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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.
Recommended action: Upgrade to 2.9.6, 2.8.11.2 or 2.7.9.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
2.8.11.42.6.7.32.9.9.12.7.9.6· Vendor fix available
Issue
FasterXML jackson-databind 2.x before 2.9.9.1 might allow attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible.
Recommended action: Upgrade to 2.9.9.1, 2.8.11.4, 2.7.9.6 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint, the service has the mysql-connector-java jar (8.0.14 or earlier) in the classpath, and an attacker can host a crafted MySQL server reachable by the victim, an attacker can send a crafted JSON message that allows them to read arbitrary local files on the server. This occurs because of missing com.mysql.cj.jdbc.admin.MiniAdmin validation.
Recommended action: Upgrade to 2.9.9, 2.8.11.4, 2.7.9.6 or 2.6.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.
Recommended action: Upgrade to 2.9.6, 2.8.11.2 or 2.7.9.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
FasterXML jackson-databind 2.x before 2.9.7, 2.8.11.3, and 2.7.9.5 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.
Recommended action: Upgrade to 2.9.7, 2.8.11.3 or 2.7.9.5 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.