Parser crash via unchecked TOML nesting depth
Published Aug 8, 2023 · Updated Sep 27, 2024
Improper input validation in FasterXML Jackson Dataformats Text before 2.15.0 allows remote attackers to crash TOML parsers. The TOML lexer applies no nesting-depth bound while the parser recursively processes nested arrays and inline tables, allowing crafted input to exhaust the JVM stack. Exploitation requires an application to parse attacker-supplied TOML; the resulting StackOverflowError interrupts that application's parsing service.
Summary
What happened
Improper input validation in FasterXML Jackson Dataformats Text before 2.15.0 allows remote attackers to crash TOML parsers. The TOML lexer applies no nesting-depth bound while the parser recursively processes nested arrays and inline tables, allowing crafted input to exhaust the JVM stack. Exploitation requires an application to parse attacker-supplied TOML; the resulting StackOverflowError interrupts that application's parsing service.
The record
- CVE
- CVE-2023-3894
- Published
- Aug 8, 2023
- Updated
- Sep 27, 2024
- Vendor
- FasterXML
- Product
- Jackson Dataformats Text
- Classifications
- CWE-787, CWE-400, CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2023CVE publishedPublication date reported by the CVE source.
- Sep 27, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.15.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- OSS-Fuzz TOMLFuzzer reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo