dbcve.org
Debian LinuxOperating system · Debian

CVE-2017-7525

CRITICAL · 9.8 CVSS v3.1 Published 2018-02-06
Fix available
A fix is available. Upgrade to 2.6.7.1 / 2.7.9.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
A deserialization flaw was discovered in the jackson-databind, versions before 2.6.7.1, 2.7.9.1 and 2.8.9, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper.

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

A detailed technical summary for this CVE is being prepared.

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
Affected:= 8.0= 9.0
Oncommand Performance ManagerApplication
Affected:all versions
Openshift Container PlatformApplication
Affected:= 4.1= 3.11
VirtualizationApplication
Affected:= 4.0
Virtualization HostApplication
Affected:= 4.0
Jboss Enterprise Application PlatformApplication
Affected:= 6.0.0= 6.4.0= 7.0= 7.1
Jackson DatabindApplication
Affected:< 2.6.7.1>= 2.7.0, < 2.7.9.1>= 2.8.0, < 2.8.9= 2.9.0
Oncommand BalanceApplication
Affected:all versions

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
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

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 · scoped
Upgrade available Upgrade to 2.6.7.1 / 2.7.9.1 / 2.8.9 or later
Fixed in 2.6.7.12.7.9.12.8.9
Vendor patch www.oracle.com →
Recommended fix High confidence

jackson-databind 2.6.7.1, 2.7.9.1, 2.8.9, or preferably >= 2.9.1 (latest 2.x release)

  1. 1. Identify the current version of jackson-databind in use by checking project dependencies (Maven pom.xml, Gradle build.gradle, or equivalent)
  2. 2. For Maven projects, update the jackson-databind dependency version to 2.7.9.1, 2.8.9, or preferably a version >= 2.9.1 (e.g., <artifactId>jackson-databind</artifactId><version>2.9.10.8</version>)
  3. 3. For Gradle projects, update the dependency to compile('com.fasterxml.jackson.core:jackson-databind:2.9.10.8') or newer
  4. 4. Rebuild the application and verify that the new Jackson Databind version is being used
  5. 5. Test the application thoroughly, especially any deserialization functionality using ObjectMapper.readValue()
  6. 6. Deploy the updated application
Caveat Minor version upgrades within the same major version are typically safe; however, review Jackson release notes for any behavior changes in deserialization that could affect existing code

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7525 — 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-2017-7525 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