dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-40149

HIGH · 7.5 CVSS v3.1 Published 2022-09-16
Fix available
A fix is available. Upgrade to after 1.4.0 or later.
See remediation →
84/100
Remediation priority · High
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
Those using Jettison to parse untrusted XML or JSON data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack.

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

Jettison is a library for parsing and converting between XML and JSON. This vulnerability allows an attacker to cause a stack overflow in the parser by supplying specially crafted XML or JSON content, resulting in a denial of service condition.

MitigationUpgrade Jettison to a patched version. If immediate patching is not possible, avoid parsing untrusted XML/JSON data with Jettison or implement input validation/size limits.

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
Affected:= 10.0= 11.0
JettisonApplication
Affected:<= 1.4.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Locate Jettison library in the environment
    Search for Jettison JAR files (jettison-*.jar) or dependency declarations in your project's build files (pom.xml, build.gradle, requirements.txt for Java/Maven projects)
    Affected if Jettison library is present in your environment
  2. Determine installed Jettison version
    Inspect the JAR file name, MANIFEST.MF file inside the JAR, or check the dependency version in your build configuration
    Affected if The version is 1.4.0 or lower
  3. Check if your application uses Jettison for parsing
    Search code for imports of org.codehaus.jettison classes (e.g., org.codehaus.jettison.json.JSONReader, org.codehaus.jettison.mapped.Configuration) and identify where XML/JSON parsing occurs
    Affected if Your code invokes Jettison classes to parse XML or JSON data
  4. Identify data source for Jettison parsing
    Review the parsing calls identified above to determine the source of data being parsed (user input, external APIs, file uploads, etc.)
    Affected if Jettison is used to parse untrusted or externally-sourced XML/JSON content

Your environment is affected if Jettison version 1.4.0 or lower is present AND your application uses Jettison to parse XML or JSON data from any untrusted source.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.4.0
Interim mitigation

Upgrade Jettison to a patched version. If immediate patching is not possible, avoid parsing untrusted XML/JSON data with Jettison or implement input validation/size limits.

Recommended fix Moderate confidence

Jettison 1.4.1 or later (e.g., 1.4.2)

  1. Identify the Jettison dependency in your project (Maven pom.xml, Gradle build.gradle, or JAR file)
  2. Locate the current Jettison version (likely 1.4.0 or earlier based on the vulnerability scope)
  3. Upgrade Jettison to version 1.4.1 or later (e.g., 1.4.2 which includes additional fixes)
  4. For Maven: Update the dependency in pom.xml with the new version number, then run 'mvn clean compile' to rebuild
  5. For Gradle: Update the dependency in build.gradle, then run './gradlew build' to rebuild
  6. For Debian systems: Run 'apt-get update && apt-get install libjettison-java' to get the fixed package version
  7. Rebuild and redeploy your application to incorporate the fixed library
  8. Test that XML/JSON parsing functionality still works correctly with the updated library
Caveat Minimal risk - point upgrade should not break existing functionality; Jettison 1.4.x maintains API compatibility

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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