Skip to content

Jettison Out-of-bounds Write vulnerability

High severity GitHub Reviewed Published Dec 13, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

maven org.codehaus.jettison:jettison (Maven)

Affected versions

< 1.5.2

Patched versions

1.5.2

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.

References

Published by the National Vulnerability Database Dec 13, 2022
Published to the GitHub Advisory Database Dec 13, 2022
Reviewed Jan 4, 2023
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.104%
(44th percentile)

Weaknesses

CVE ID

CVE-2022-45693

GHSA ID

GHSA-grr4-wv38-f68w

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.