dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-40150

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 Out of memory. 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 library versions prior to a fix fail to properly constrain memory allocation when parsing untrusted XML or JSON data. Attackers can supply specially crafted input that causes excessive memory consumption, triggering an Out of Memory condition that crashes the parser and results in Denial of Service.

MitigationImplement input validation with strict size limits on all untrusted XML/JSON data before passing to the Jettison parser, and configure parser resource constraints to prevent unbounded memory allocation.

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 your environment
    Search for files named 'jettison-*.jar' or check your application's dependency manifest (Maven pom.xml, Gradle build file, or JAR contents) for the Jettison library
    Affected if Jettison library is present in your environment
  2. Determine installed Jettison version
    If using Maven/Gradle, run 'mvn dependency:list' or 'gradle dependencies' to list the Jettison version. For Debian systems, run 'dpkg -l | grep jettison' or check the package version via 'apt show libjettison-java'
    Affected if The version displayed is 1.4.0 or lower, or on Debian 10/11 the package version matches the vulnerable release
  3. Identify if Jettison parses untrusted input
    Review application source code or configuration for XML/JSON parsing code that uses Jettison (look for imports like 'org.codehaus.jettison' or parser instantiation) and determine whether the data being parsed originates from untrusted sources such as user input, API requests, or external systems
    Affected if Jettison is used to parse XML or JSON data from untrusted sources without strict size limits applied beforehand
  4. Check for resource constraints on parser
    Inspect the parser configuration to verify whether memory limits, entity expansion limits, or input size constraints are explicitly set on the Jettison parser or the underlying XMLStreamReader/JSONParser
    Affected if No explicit memory or size constraints are configured on the parser, allowing unbounded input processing

You are affected if Jettison version 1.4.0 or lower is present in your environment and is used to parse untrusted XML or JSON data without input size limits configured on the parser.

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

Implement input validation with strict size limits on all untrusted XML/JSON data before passing to the Jettison parser, and configure parser resource constraints to prevent unbounded memory allocation.

Recommended fix Moderate confidence

Jettison 1.5.0 or later (1.5.x series)

  1. Identify all applications and dependencies that use the Jettison library (version 1.4.0 or earlier)
  2. For Maven-based projects: Update the Jettison dependency in pom.xml to version 1.5.0 or later by running: mvn dependency:tree to find Jettison dependencies, then update the version in pom.xml
  3. For Gradle-based projects: Update the Jettison dependency in build.gradle or build.gradle.kts to version 1.5.0 or later, for example: implementation('org.codehaus.jettison:jettison:1.5.0')
  4. For Debian Linux systems: Run 'apt update && apt install jettison' or 'apt update && apt upgrade' to install the latest security updates
  5. Rebuild and redeploy all affected applications after upgrading the library
  6. Monitor application memory usage after deployment to verify the fix is effective
Caveat Jettison 1.5.x may include API changes; review changelog and test applications in a non-production environment before deploying

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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