Debian LinuxOperating system · Debian
CVE-2020-11620
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 · uneditedFasterXML 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).
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 confidenceThis is a deserialization vulnerability in FasterXML Jackson-databind where the library mishandles the interaction between serialization gadgets and polymorphic type handling. Specifically, the org.apache.commons.jelly.impl.Embedded class from commons-jelly can be leveraged as a gadget chain for remote code execution when JSON typing features are enabled.
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
Debian LinuxOperating system
= 8.0
Active Iq Unified ManagerApplication
>= 7.3>= 9.5>= 2.9.0, < 2.9.10.4all versions>= 2.4.0, <= 2.9.0= 8.0.0.4.0= 7.1= 10.0.1.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Jackson-databind versionLocate the jackson-databind library in your project dependencies (Maven pom.xml, Gradle build.gradle, or JAR file names) and note the exact version numberAffected if The installed version is 2.9.0 through 2.9.10.3 (any version >= 2.9.0 but < 2.9.10.4)
-
Check for polymorphic type handlingSearch your codebase for ObjectMapper configurations that enable default typing, such as enableDefaultTyping(), enableDefaultTypingAsProperty(), or @JsonTypeInfo annotations applied at class or field levelAffected if Polymorphic type handling (default typing) is explicitly enabled on any ObjectMapper instance processing untrusted JSON
-
Verify commons-jelly presenceSearch your classpath, build dependencies, or lib folders for commons-jelly JAR files (commons-jelly-*.jar)Affected if The commons-jelly library is present in the runtime classpath alongside vulnerable jackson-databind versions
You are affected if you have jackson-databind version 2.9.0-2.9.10.3 AND have polymorphic type handling enabled AND commons-jelly is in your classpath, allowing the gadget chain to execute.
Generated from the published advisory. Verify against your own configuration.
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 data2.9.10.4
Upgrade jackson-databind to version 2.9.10.4 or later, or disable polymorphic type handling for untrusted input.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2020-11620 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-11620 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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