CSRF bypass via permissive Content-Type matching
Published Dec 18, 2024 · Updated Dec 18, 2024
CSRF in Astro before 4.16.17 allows remote attackers to submit cross-origin requests through the checkOrigin middleware. The middleware compares the entire Content-Type header against exact form-media-type strings and skips its origin check when parameters are appended or the header is absent. Exploitation requires security.checkOrigin to be enabled and a browser user to send the request; the resulting operation executes with that user's application privileges.
Summary
What happened
CSRF in Astro before 4.16.17 allows remote attackers to submit cross-origin requests through the checkOrigin middleware. The middleware compares the entire Content-Type header against exact form-media-type strings and skips its origin check when parameters are appended or the header is absent. Exploitation requires security.checkOrigin to be enabled and a browser user to send the request; the resulting operation executes with that user's application privileges.
The record
- CVE
- CVE-2024-56140
- Published
- Dec 18, 2024
- Updated
- Dec 18, 2024
- Vendor
- Astro Technology Company
- Product
- Astro
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 18, 2024CVE publishedPublication date reported by the CVE source.
- Dec 18, 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.17
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