Service interruption via unchecked SpEL array allocation
Published Aug 20, 2024 · Updated Oct 30, 2024
Resource exhaustion in Spring Framework 5.3.38 and earlier allows remote attackers to interrupt service via a crafted SpEL expression. ConstructorReference allocates arrays requested by an expression even when SimpleEvaluationContext has no constructor resolver, permitting attacker-controlled array sizes to consume memory. The application must evaluate user-supplied SpEL; the reported consequence is limited to availability, without data disclosure or modification.
Summary
What happened
Resource exhaustion in Spring Framework 5.3.38 and earlier allows remote attackers to interrupt service via a crafted SpEL expression. ConstructorReference allocates arrays requested by an expression even when SimpleEvaluationContext has no constructor resolver, permitting attacker-controlled array sizes to consume memory. The application must evaluate user-supplied SpEL; the reported consequence is limited to availability, without data disclosure or modification.
The record
- CVE
- CVE-2024-38808
- Published
- Aug 20, 2024
- Updated
- Oct 30, 2024
- Vendor
- Spring
- Product
- Spring Framework
- Classifications
- CWE-770, CAPEC-130, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2024CVE publishedPublication date reported by the CVE source.
- Oct 30, 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=5.3.0 <5.3.39, 6.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
No public exploit references are available in this record.
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