{"answers":{"affected":"2 open source packages ship an affected version, including astro. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56140 exists.","fix":"Upgrade astro to 4.16.17 or later.","what":"CVE-2024-56140 is a medium-severity vulnerability in withastro astro, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-56140 and fix it if it is affected.\n\nWhat it is: CVE-2024-56140 is a medium-severity vulnerability in withastro astro, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56140 exists.\n\nAffected packages and fixed versions:\n- astro (npm): affected all versions; fixed in 4.16.17\n- astro (npm): affected all versions; fixed in 4.16.17\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-56140/ (Markdown: https://insights.sbomify.com/CVE-2024-56140/index.md)","id":"CVE-2024-56140","markdown":"https://insights.sbomify.com/CVE-2024-56140/index.md","name":"CVE-2024-56140","record":{"aliases":["GHSA-c4pw-33h3-35xw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Astro web framework","requires_auth":"none","summary":"Attackers can bypass CSRF protections in Astro when origin checks are enabled, allowing unauthorized state-changing requests.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"astro","vendor":"astro"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Bypass of CSRF Middleware in Astro","id":"CVE-2024-56140","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":2,"n_references":4,"next":{"headline":"Minosoft has IV equal to key","id":"CVE-2024-56141"},"packages":[{"ecosystem":"npm","fixed":["4.16.17"],"introduced":["0"],"last_affected":[],"package":"astro","purl":null,"source":"GHSA-c4pw-33h3-35xw"},{"ecosystem":"npm","fixed":["4.16.17"],"introduced":["0"],"last_affected":[],"package":"astro","purl":"pkg:npm/astro","source":"GHSA-c4pw-33h3-35xw"}],"prev":{"headline":"A stack overflow Segmentation Fault (SEGV) and Memory Leak in pdftools","id":"CVE-2024-56139"},"products":["astro"],"published":"2024-12-18","related":[{"cvss_score":7.8,"headline":"Server source code is exposed to the public if sourcemaps are enabled","id":"CVE-2024-56159","kev_date_added":null,"published":"2024-12-19"},{"cvss_score":7.5,"headline":"Astro: Host header SSRF in prerendered error page fetch","id":"CVE-2026-54299","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":7.2,"headline":"astro allows bypass of image proxy domain validation leading to SSRF and potential XSS","id":"CVE-2025-59837","kev_date_added":null,"published":"2025-10-28"},{"cvss_score":7.1,"headline":"Astro: Reflected XSS via unescaped slot name","id":"CVE-2026-50146","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":7.1,"headline":"Astro is vulnerable to Reflected XSS via the server islands feature","id":"CVE-2025-64764","kev_date_added":null,"published":"2025-11-19"},{"cvss_score":6.9,"headline":"Astro middleware authentication checks based on url.pathname can be bypassed via url encoded values","id":"CVE-2025-64765","kev_date_added":null,"published":"2025-11-19"},{"cvss_score":6.9,"headline":"Unauthorized third-party images in Astro’s _image endpoint","id":"CVE-2025-55303","kev_date_added":null,"published":"2025-08-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-18","vendors":["withastro"]},"summary":"Attackers can bypass CSRF protections in Astro when origin checks are enabled, allowing unauthorized state-changing requests.","url":"https://insights.sbomify.com/CVE-2024-56140/"}