Skip to content

Ion Java StackOverflow vulnerability

High severity GitHub Reviewed Published Jan 3, 2024 in amazon-ion/ion-java • Updated Nov 4, 2025

Package

maven com.amazon.ion:ion-java (Maven)

Affected versions

< 1.10.5

Patched versions

1.10.5
maven software.amazon.ion:ion-java (Maven)
< 1.10.5
None

Description

Impact

A potential denial-of-service issue exists in ion-java for applications that use ion-java to:

  • Deserialize Ion text encoded data, or
  • Deserialize Ion text or binary encoded data into the IonValue model and then invoke certain IonValue methods on that in-memory representation.

An actor could craft Ion data that, when loaded by the affected application and/or processed using the IonValue model, results in a StackOverflowError originating from the ion-java library.

Impacted versions: <1.10.5

Patches

The patch is included in ion-java >= 1.10.5.

Workarounds

Do not load data which originated from an untrusted source or that could have been tampered with. Only load data you trust.

If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [email protected]. Please do not create a public GitHub issue.

[1] https://aws.amazon.com/security/vulnerability-reporting

References

@popematt popematt published to amazon-ion/ion-java Jan 3, 2024
Published to the GitHub Advisory Database Jan 3, 2024
Reviewed Jan 3, 2024
Published by the National Vulnerability Database Jan 3, 2024
Last updated Nov 4, 2025

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

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(55th percentile)

Weaknesses

Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Learn more on MITRE.

CVE ID

CVE-2024-21634

GHSA ID

GHSA-264p-99wq-f4j6

Source code

Credits

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