Service crash via unbounded recursive array parsing
Published Jun 24, 2025 · Updated Jun 24, 2025
Stack exhaustion in Oat++ 1.3.0 and 1.3.1 allows remote attackers to crash applications via deeply nested JSON arrays. The deserializeArray routine recursively invokes deserialize for every nested array without enforcing a depth limit, exhausting the process stack. Any network endpoint that passes attacker-controlled JSON to the object mapper exposes the hosting process to unauthenticated service interruption.
Summary
What happened
Stack exhaustion in Oat++ 1.3.0 and 1.3.1 allows remote attackers to crash applications via deeply nested JSON arrays. The deserializeArray routine recursively invokes deserialize for every nested array without enforcing a depth limit, exhausting the process stack. Any network endpoint that passes attacker-controlled JSON to the object mapper exposes the hosting process to unauthenticated service interruption.
The record
- CVE
- CVE-2025-6566
- Published
- Jun 24, 2025
- Updated
- Jun 24, 2025
- Vendor
- Oat++
- Product
- Oat++
- Classifications
- CWE-121, CWE-787, CWE-119, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2025CVE publishedPublication date reported by the CVE source.
- Jun 24, 2025Record 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=1.3.0
- Affected versionversion=1.3.1
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
- Nested-array crash input and sanitizer reproductionproof 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