How severe is CVE-2022-45693?

CVE-2022-45693 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-45693?

CVE-2022-45693 affects the following packages: org.codehaus.jettison:jettison (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-45693?

Update org.codehaus.jettison:jettison to 1.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-45693 is resolved across your whole dependency graph.

How do I detect CVE-2022-45693 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.codehaus.jettison:jettison, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-45693 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2022-45693 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-45693, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-45693?

CVE-2022-45693 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-45693?

CVE-2022-45693 is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-45693 published, and has it been updated?

CVE-2022-45693 was published on December 13, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2022-45693 — jettison

HIGH

CVE-2022-45693 is a high-severity (CVSS 7.5) Out-of-bounds Write vulnerability in org.codehaus.jettison:jettison. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.codehaus.jettison:jettison — see the affected versions and patch details below.

Jettison Out-of-bounds Write vulnerability

Also known asGHSA-grr4-wv38-f68w

Published

Dec 13, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-45693.

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk+0.05%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.codehaus.jettison:jettison

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jettison before v1.5.2 was discovered to contain a stack overflow via the map parameter. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted string.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.codehaus.jettison:jettison`	all versions	1.5.2`org.codehaus.jettison:jettison:1.5.2`

Affected Products

2 products · 3 configurations

debian linuxdebian

2 versions

10.011.0

Application

jettisonjettison_project

< 1.5.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Jettison before v1.5.2 was discovered to contain a stack overflow via th…

github.comNVDDec 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.codehaus.jettison:jettison, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.codehaus.jettison:jettison to 1.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-45693 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat has determined the impact of this flaw to be Moderate; a successful attack using this flaw would require the processing of untrusted, unsanitized, or unrestricted user inputs, which runs counter to established Red Hat security practices.

Product	Fixed in	Advisory
MTA-6.2-RHEL-8	`mta/mta-rhel8-operator:6.2.2-3`	RHSA-2024:1027
OCP-Tools-4.12-RHEL-8	`jenkins-2-plugins-0:4.12.1686649756-1.el8`	RHSA-2023:3610
Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7	`eap7-apache-cxf-0:3.1.16-4.redhat_00003.1.ep7.el7`	RHSA-2025:1746
Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7	`eap7-jackson-modules-java8-0:2.10.4-2.redhat_00004.1.el7eap`	RHSA-2025:1747
Red Hat JBoss Enterprise Application Platform 7.4.9	`org.codehaus.jettison/jettison:1.5.2.redhat-00002`	RHSA-2023:0556
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8	`eap7-jettison-0:1.5.2-1.redhat_00002.1.el8eap`	RHSA-2023:0553
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9	`eap7-jettison-0:1.5.2-1.redhat_00002.1.el9eap`	RHSA-2023:0554
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7	`eap7-jettison-0:1.5.2-1.redhat_00002.1.el7eap`	RHSA-2023:0552

Frequently Asked Questions

Jettison before v1.5.2 was discovered to contain a stack overflow via the map parameter. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted string.

O3 Security · Impact-Aware SCA

Is CVE-2022-45693 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-787Out-of-bounds Write

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Dec 13, 2022

First exploit

Dec 16, 2022

3 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-45693

GHSA-grr4-wv38-f68w

References

Advisorygithub.com · CVE 2022 45693.json Advisorynvd.nist.gov · CVE 2022 45693 Advisorydebian.org · dsa 5312 Reportgithub.com Articlelists.debian.org · msg00045 Packagegithub.com · jettison

Related vulnerabilities

Also affects jettison

This CVE is high severity; 3 of 4 other CVEs affecting jettison are rated as high or higher (top: high).

CVE-2023-1436CVE-2022-45685CVE-2022-40149CVE-2022-40150

Same weakness: CWE-787

This CVE is high severity; 3 of 4 other CVEs with CWE-787 are rated as high or higher (top: high).

GHSA-p3jp-9v83-76w9GHSA-494m-4556-wf5pCVE-2026-93451CVE-2026-116590Browse all CWE-787

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-45693 — jettison

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-45693 in your dependencies?