CVE-2024-56140 json
Bypass of CSRF Middleware in Astro
published last yr. modified 4mo ago also EUVD-2024-3575 , GHSA-c4pw-33h3-35xw
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
Astro is a web framework for content-driven websites. In affected versions a bug in Astro’s CSRF-protection middleware allows requests to bypass CSRF checks. When the `security.checkOrigin` configuration option is set to `true`, Astro middleware will perform a CSRF check. However, a vulnerability exists that can bypass this security. A semicolon-delimited parameter is allowed after the type in `Content-Type`. Web browsers will treat a `Content-Type` such as `application/x-www-form-urlencoded; abc` as a `simple request` and will not perform preflight validation. In this case, CSRF is not blocked as expected. Additionally, the `Content-Type` header is not required for a request. This issue has been addressed in version 4.16.17 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
Patch / fix
Is CVE-2024-56140 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | astro | <4.16.17 |
4.16.17 |
Affected products
- withastro astro
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/withastro/astro/commit/e7d14c374b9d45e27089994a4eb72186d05514de
web, patch
-
github.com
/withastro/astro/security/advisories/GHSA-c4pw-33h3-35xw
web, vendor-advisory, advisory
-
developer.mozilla.org
/en-US/docs/Web/HTTP/CORS#simple_requests
web, technical-description
-
github.com
/withastro/astro/blob/6031962ab5f56457de986eb82bd24807e926ba1b/packages/astro/src/core/app/middlewares.ts
web, product
-
nvd.nist.gov
/vuln/detail/CVE-2024-56140
advisory
-
github.com
/withastro/astro
package
Sources
- CVE List CVE-2024-56140
- GitHub Advisory GHSA-c4pw-33h3-35xw
- NVD CVE-2024-56140
- Maintainer advisory GHSA-c4pw-33h3-35xw
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of withastro/astro published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.