Source code disclosure via public server sourcemaps
Published Dec 19, 2024 · Updated Dec 20, 2024
Information disclosure in affected Astro 4 and 5 projects allows remote attackers to read server source code over HTTP. During the build, ssrMoveAssets places server-code map files in dist/client, and page routes produce predictable names such as pages/index.astro.mjs.map. Unauthenticated access requires a deployed server-output or static-output build with sourcemaps enabled; exposure is limited to source text and values embedded verbatim in it.
Summary
What happened
Information disclosure in affected Astro 4 and 5 projects allows remote attackers to read server source code over HTTP. During the build, ssrMoveAssets places server-code map files in dist/client, and page routes produce predictable names such as pages/index.astro.mjs.map. Unauthenticated access requires a deployed server-output or static-output build with sourcemaps enabled; exposure is limited to source text and values embedded verbatim in it.
The record
- CVE
- CVE-2024-56159
- Published
- Dec 19, 2024
- Updated
- Dec 20, 2024
- Vendor
- Astro Technology Company
- Product
- Astro
- Classifications
- CWE-219, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 19, 2024CVE publishedPublication date reported by the CVE source.
- Dec 20, 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=< 4.16.18
- Affected versionversion=>= 5.0.0, < 5.0.8
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 sourcemap disclosure demonstrationproof 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