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.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.docx4j.org.apache.xalan.lib.sql.JNDIConnectionPool.
Recommended action: Upgrade to 2.9.10.8 or 2.6.7.5 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.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource.
Recommended action: Upgrade to 2.9.10.8 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.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.
Recommended action: Upgrade to 2.9.10.8 or 2.6.7.5 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.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.cpdsadapter.DriverAdapterCPDS.
Recommended action: Upgrade to 2.9.10.8 or 2.6.7.5 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.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.SharedPoolDataSource.
Recommended action: Upgrade to 2.9.10.8 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.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.
Recommended action: Upgrade to 2.9.10.8 or 2.6.7.5 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.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.cpdsadapter.DriverAdapterCPDS.
Recommended action: Upgrade to 2.9.10.8 or 2.6.7.5 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.6.7.5 and from 2.7.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration.
Recommended action: Upgrade to 2.9.10.6 or 2.6.7.5 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.8 mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in org.glassfish.web/javax.servlet.jsp.jstl).
Recommended action: Upgrade to 2.9.10.8 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.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.SharedPoolDataSource.
Recommended action: Upgrade to 2.9.10.8 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.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.PerUserPoolDataSource.
Recommended action: Upgrade to 2.9.10.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
This project contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. 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).
Recommended action: Upgrade to 2.9.10.6 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.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource.
Recommended action: Upgrade to 2.9.10.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability is data integrity.
Recommended action: Upgrade to 2.10.5.1, 2.9.10.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 flaw was found in jackson-databind before 2.9.10.7 and 2.6.7.5. FasterXML mishandles the interaction between serialization gadgets and typing. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Recommended action: Upgrade to 2.9.10.7 or 2.6.7.5 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.5 mishandles the interaction between serialization gadgets and typing, related to oracle.jms.AQjmsQueueConnectionFactory, oracle.jms.AQjmsXATopicConnectionFactory, oracle.jms.AQjmsTopicConnectionFactory, oracle.jms.AQjmsXAQueueConnectionFactory, and oracle.jms.AQjmsXAConnectionFactory (aka weblogic/oracle-aqjms).
Recommended action: Upgrade to 2.9.10.5 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.5 mishandles the interaction between serialization gadgets and typing, related to com.sun.org.apache.xalan.internal.lib.sql.JNDIConnectionPool (aka xalan2).
Recommended action: Upgrade to 2.9.10.5 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.5 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.xalan.lib.sql.JNDIConnectionPool (aka apache/drill).
Recommended action: Upgrade to 2.9.10.5 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.5 mishandles the interaction between serialization gadgets and typing, related to org.jsecurity.realm.jndi.JndiRealmFactory (aka org.jsecurity).
Recommended action: Upgrade to 2.9.10.5 or later, 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 Oracle JDBC jar 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.
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10 and 2.8.11.5. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.
Recommended action: Upgrade to 2.9.10 or 2.8.11.5 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.apache.commons.proxy.provider.remoting.RmiProvider (aka apache/commons-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, 2.8.11.6, and 2.7.9.7 mishandles the interaction between serialization gadgets and typing, related to com.ibatis.sqlmap.engine.transaction.jta.JtaTransactionConfig (aka ibatis-sqlmap).
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 FasterXML jackson-databind in all versions before 2.9.10 and 2.10.0, where it would permit polymorphic deserialization of malicious objects using the xalan JNDI gadget when used in conjunction with polymorphic type handling methods such as enableDefaultTyping() or when @JsonTypeInfo is using Id.CLASS or Id.MINIMALCLASS or in any other way which ObjectMapper.readValue might instantiate objects from unsafe sources. An attacker could use this flaw to execute arbitrary code.
Recommended action: Upgrade to 2.9.10 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 and 2.6.7.4 mishandles the interaction between serialization gadgets and typing, related to com.caucho.config.types.ResourceRef (aka caucho-quercus).
Recommended action: Upgrade to 2.9.10.4 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.