Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

GHSA-c24f-2j3g-rg48

HIGHFix: charleskorn/kaml@5f82a2d

GHSA-c24f-2j3g-rg48 is a high-severity (CVSS 7.5) CWE-776 vulnerability in com.charleskorn.kaml:kaml. O3 Security confirms whether GHSA-c24f-2j3g-rg48 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

kaml has potential denial of service while parsing input with anchors and aliases

Also known asCVE-2023-28118
Published
Mar 20, 2023
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
com.charleskorn.kaml:kaml

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

Impact

Applications that use kaml to parse untrusted input containing anchors and aliases may consume excessive memory and crash.

Patches

Version 0.53.0 and later default to refusing to parse YAML documents containing anchors and aliases.

Workarounds

None.

References

Wikipedia has an explanation of this class of vulnerability: billion laughs attack

Acknowledgements

Thank you to @gdude2002 for reporting this issue.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.charleskorn.kaml:kamlall versions0.53.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.charleskorn.kaml:kaml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update com.charleskorn.kaml:kaml to 0.53.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c24f-2j3g-rg48 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-c24f-2j3g-rg48 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-c24f-2j3g-rg48. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Applications that use kaml to parse untrusted input containing anchors and aliases may consume excessive memory and crash. ### Patches Version 0.53.0 and later default to refusing to parse YAML documents containing anchors and aliases. ### Workarounds None. ### References Wikipedia has an explanation of this class of vulnerability: [billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack) ### Acknowledgements Thank you to @gdude2002 for reporting this issue.
O3 Security · Impact-Aware SCA

Is GHSA-c24f-2j3g-rg48 in your dependencies?

O3 detects GHSA-c24f-2j3g-rg48 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-c24f-2j3g-rg48: kaml (High 7.5) | O3 Security