CVE-2020-8840
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.0.0 through 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter.
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 confidenceFasterXML jackson-databind versions 2.0.0 through 2.9.10.2 fails to block unsafe deserialization paths via xbean-reflect, specifically the JndiConverter class. This allows remote attackers to perform JNDI injection attacks leading to remote code execution by tricking jackson-databind into deserializing malicious payloads through the xbean-reflect library.
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= 8.0>= 2.0.0, < 2.7.9.7>= 2.8.0, < 2.8.11.5>= 2.9.0, < 2.9.10.3all versionsall versionsall versionsall versions= v300r006c20= v300r006c20spc100= v300r006c20spc200= v300r006c20spc300< 11.2.0.3.23>= 12.2.0.1.0, < 12.2.0.1.19>= 13.9.4.0.0, < 13.9.4.2.1CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 installationSearch for jackson-databind JAR files in your application directories, libraries, or container images. Check build files (pom.xml, build.gradle, package.json) for jackson-databind dependencies.Affected if jackson-databind is present in your environment
-
Determine installed jackson-databind versionInspect the JAR file name for the version (e.g., jackson-databind-2.9.10.jar), or check the manifest file inside the JAR, or look at the dependency declaration in your build configuration.Affected if version is 2.0.0 through 2.9.10.2 (specifically >= 2.0.0 and < 2.7.9.7, or >= 2.8.0 and < 2.8.11.5, or >= 2.9.0 and < 2.9.10.3)
-
Check for xbean-reflect dependencySearch for xbean-reflect in your classpath, dependencies, or build files. This library enables the JNDI injection vector.Affected if xbean-reflect is present in your runtime classpath
-
Determine if application deserializes untrusted JSONReview application code and configuration to identify if Jackson is used to deserialize JSON data from untrusted network sources, user input, or external APIs.Affected if application deserializes JSON from untrusted sources using ObjectMapper or similar Jackson APIs
You are affected if jackson-databind version is in the vulnerable range (2.0.0 to 2.9.10.2), xbean-reflect is in your classpath, and your application deserializes JSON from untrusted sources.
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.
dbcve · scoped2.7.9.72.8.11.52.9.10.3
Upgrade jackson-databind to version 2.9.10.3 or later which includes the xbean-reflect/JNDI blocking, or ensure jackson-databind is not used to deserialize untrusted data from untrusted sources.
Jackson Databind 2.9.10.4 (or latest 2.9.x stable release)
- 1. Identify all applications and services using FasterXML Jackson Databind within your environment
- 2. For each application, determine the current Jackson Databind version in use
- 3. If using version 2.9.0 to 2.9.10.2, upgrade to Jackson Databind 2.9.10.4 or later (preferably latest 2.9.x stable)
- 4. If using version 2.8.0 to 2.8.11.4, upgrade to Jackson Databind 2.8.11.5 or later (preferably latest 2.8.x stable)
- 5. If using version 2.0.0 to 2.7.9.6, upgrade to Jackson Databind 2.7.9.7 or later (preferably latest 2.7.x stable)
- 6. Update dependency management files (pom.xml, build.gradle, package.json, etc.) with the new version
- 7. Rebuild and redeploy all affected applications
- 8. Verify that the upgrade does not break existing functionality through testing
Generated from the published advisory — verify against the referenced sources before acting.
- 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-8840 — 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 sources- www.huawei.com
- github.com
- lists.debian.org
- security.netapp.com
- www.oracle.com
- www.oracle.com
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-8840 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