dbcve.org
Active Iq Unified ManagerApplication · Netapp

CVE-2020-14195

HIGH · 8.1 CVSS v3.1 Published 2020-06-16
Fix available
A fix is available. Upgrade to 2.9.10.5 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FasterXML jackson-databind versions before 2.9.10.5 improperly handles the interaction between serialization gadgets and polymorphic type handling, specifically when deserializing data involving the JndiRealmFactory class from org.jsecurity. This allows attackers to potentially exploit JNDI injection through crafted malicious serialized payloads, leading to remote code execution.

MitigationUpgrade jackson-databind to version 2.9.10.5 or later. Additionally, disable polymorphic type handling or enable strict whitelist filtering for untrusted input to mitigate deserialization attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Active Iq Unified ManagerApplication
Affected:>= 7.3>= 9.5
Debian LinuxOperating system
Affected:= 8.0
Jackson DatabindApplication
Affected:>= 2.9.0, < 2.9.10.5
Steelstore Cloud Integrated StorageApplication
Affected:all versions
Agile PlmApplication
Affected:= 9.3.6
Banking Digital ExperienceApplication
Affected:= 18.1= 18.2= 18.3= 19.1= 19.2= 20.1
Communications Calendar ServerApplication
Affected:= 8.0.0.4.0
Communications Contacts ServerApplication
Affected:= 8.0.0.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify jackson-databind version
    Locate the jackson-databind JAR file in your application classpath or dependencies (common paths: WEB-INF/lib, Maven local repository, Gradle cache). Check the filename or inspect the MANIFEST.MF file for the version. If using Maven, run 'mvn dependency:tree | grep jackson-databind' or check your pom.xml dependency declaration.
    Affected if The installed version is jackson-databind >= 2.9.0 and < 2.9.10.5 (or the specific product version falls within the affected ranges listed for Netapp, Oracle, or Debian)
  2. Determine if polymorphic type handling is enabled
    Search your Jackson ObjectMapper configuration code for settings like enableDefaultTyping(), enableDefaultTypingAsProperty(), or any use of ObjectMapper.DefaultTyping. Also check for @JsonTypeInfo annotations on your data models that allow dynamic type resolution.
    Affected if Polymorphic type handling is enabled (either via enableDefaultTyping() or default typing annotations) because this allows the deserialization of arbitrary classes specified in the JSON payload
  3. Check for presence of JndiRealmFactory in classpath
    Search for the JAR file containing JndiRealmFactory (org.jsecurity: realm or similar). Search your classpath directories for files containing 'JndiRealmFactory' or the org.jsecurity package. In Maven projects, run 'mvn dependency:tree' and look for jsecurity, shiro, or similar libraries.
    Affected if The JndiRealmFactory class from org.jsecurity is available in the runtime classpath, providing the gadget needed for JNDI injection
  4. Identify if JSON deserialization accepts untrusted input
    Review your application code to identify endpoints or services that accept JSON data from external sources and pass it to ObjectMapper for deserialization. Look for methods like readValue() receiving data from HTTP requests, message queues, or file uploads.
    Affected if Your application deserializes JSON data from untrusted or external sources using ObjectMapper without strict type whitelisting

You are affected if your environment uses jackson-databind version 2.9.0 through 2.9.10.4, has polymorphic type handling enabled, and deserializes untrusted JSON that could reference the JndiRealmFactory class.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2.9.10.5 or later
Fixed in 2.9.10.5
Interim mitigation

Upgrade jackson-databind to version 2.9.10.5 or later. Additionally, disable polymorphic type handling or enable strict whitelist filtering for untrusted input to mitigate deserialization attacks.

Fix this in Active Iq Unified Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14195 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14195 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data