CVE-2022-45693: Jettison Out-of-bounds Write vulnerability

Summary

13/12/2022
Yes i
High
7.5

CVE-2022-45693: Jettison Out-of-bounds Write vulnerability. Affects org.codehaus.jettison:jettison versions < 1.5.2. Fixed in 1.5.2. How to fix ↓

Also tracked for

The same CVE-2022-45693 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Jettison package, specifically versions before v1.5.2, is an open-source library for JSON processing in Java. It provides functionality for converting Java objects to JSON and vice versa. Jettison is commonly used in Maven projects and can be identified by the package name 'org.codehaus.jettison:jettison'. This vulnerability affects the map parameter and can lead to a stack overflow. Attackers can exploit this vulnerability to cause a Denial of Service (DoS) by providing a crafted string.

Vulnerability Detail

The Jettison Out-of-bounds Write vulnerability (CVE-2022-45693) arises from a stack overflow in Jettison versions prior to v1.5.2. This vulnerability can be triggered by manipulating the map parameter. By exploiting this vulnerability, an attacker can cause a Denial of Service (DoS) attack by supplying a specially crafted string. The impact of this vulnerability can result in the affected application becoming unresponsive or crashing. The Common Vulnerabilities and Exposures (CVE) identifier for this vulnerability is CVE-2022-45693. The vulnerability has been assigned a CVSSv3 score of 7.5, indicating a high severity level.

How To Fix

Latest published version: 1.5.7 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.5.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a workaround, if upgrading to the fixed version is not immediately feasible, developers can consider implementing input validation and sanitization for the map parameter. By carefully validating and sanitizing user-supplied input, the risk of exploitation can be mitigated. Here is an example of how input validation can be performed in Java:

String mapParam = request.getParameter("map");

if (mapParam != null && !mapParam.isEmpty()) {
    // Perform input validation and sanitization
    // ... (code omitted for brevity)
}

It is important to note that this workaround is not a substitute for upgrading to the fixed version, as it only reduces the risk rather than eliminating it.

Conclusion

The Jettison Out-of-bounds Write vulnerability (CVE-2022-45693) in versions prior to v1.5.2 can be exploited to cause a Denial of Service (DoS) attack. To mitigate this vulnerability, it is crucial to upgrade the Jettison package to version 1.5.2 or later. Developers can also consider implementing input validation and sanitization for the map parameter as a temporary workaround. For further assistance and support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for org.codehaus.jettison:jettison →

Share this vulnerability

FAQ

This vulnerability can lead to a Denial of Service (DoS) attack, causing the affected application to become unresponsive or crash.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it for any open-source vulnerabilities, including this one.

The CVSSv3 score for this vulnerability is 7.5, indicating a high severity level.

Yes, the recommended fix is to upgrade the Jettison package to version 1.5.2 or later.

While upgrading to the fixed version is the recommended approach, developers can implement input validation and sanitization for the map parameter as a temporary workaround.

Related vulnerabilities

Recent vulnerabilities recorded for org.codehaus.jettison:jettison.

How To Fix

Latest published version: 1.5.7 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.5.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback