Arbitrary file read via static-resource traversal
Published Jul 16, 2021 · Updated Aug 3, 2024
Path traversal in Micronaut Core before 2.5.9 allows remote attackers to read arbitrary filesystem files through crafted static-resource URLs. DefaultFileSystemResourceLoader resolves request paths but, before the patch, opens the result without verifying that its real path remains under the configured resource base. An unauthenticated network request reaches the flaw when file-backed static resources are enabled with a recursive ** mapping, exposing readable host files.
Summary
What happened
Path traversal in Micronaut Core before 2.5.9 allows remote attackers to read arbitrary filesystem files through crafted static-resource URLs. DefaultFileSystemResourceLoader resolves request paths but, before the patch, opens the result without verifying that its real path remains under the configured resource base. An unauthenticated network request reaches the flaw when file-backed static resources are enabled with a recursive ** mapping, exposing readable host files.
The record
- CVE
- CVE-2021-32769
- Published
- Jul 16, 2021
- Updated
- Aug 3, 2024
- Vendor
- Micronaut Foundation
- Product
- Micronaut Core
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=< 2.5.9
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
- Upstream curl path-traversal reproductionproof of concept · unverified
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