{"answers":{"affected":"2 open source packages ship an affected version, including @kindspells/astro-shield. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-30250 in the wild and no public exploit code.","fix":"Upgrade @kindspells/astro-shield to 1.3.2 or later.","what":"CVE-2024-30250 is a high-severity vulnerability in kindspells astro-shield, published on 4 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-30250 and fix it if it is affected.\n\nWhat it is: CVE-2024-30250 is a high-severity vulnerability in kindspells astro-shield, published on 4 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-30250 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @kindspells/astro-shield (npm): affected from 1.2.0; fixed in 1.3.2\n- @kindspells/astro-shield (npm): affected from 1.2.0; fixed in 1.3.2\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-30250/ (Markdown: https://insights.sbomify.com/CVE-2024-30250/index.md)","id":"CVE-2024-30250","markdown":"https://insights.sbomify.com/CVE-2024-30250/index.md","name":"CVE-2024-30250","record":{"aliases":["GHSA-c4gr-q97g-ppwc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Astro security integration","requires_auth":"none","summary":"Attackers can bypass Astro-Shield's allow-lists by injecting code with valid integrity attributes, tricking browsers into accepting malicious resources.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"astro-shield","vendor":"kindspells"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Astro-Shield is an integration to enhance website security with SubResource Integrity hashes, Content-Security-Policy headers, and other techniques. Versions from 1.2.0 to 1.3.1 of Astro-Shield allow bypass to the allow-lists for cross-origin resources by introducing valid `integrity` attributes to the injected code. This implies that the injected SRI hash would be added to the generated CSP header, which would lead the browser to believe that the injected resource is legit. This vulnerability is patched in version 1.3.2.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"In Astro-Shield, setting a correct `integrity` attribute to injected code allows to bypass the allow-lists","id":"CVE-2024-30250","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":2,"n_references":4,"next":{"headline":"Denial of service when trying to parse malformed POST requests in aiohttp","id":"CVE-2024-30251"},"packages":[{"ecosystem":"npm","fixed":["1.3.2"],"introduced":["1.2.0"],"last_affected":[],"package":"@kindspells/astro-shield","purl":null,"source":"GHSA-c4gr-q97g-ppwc"},{"ecosystem":"npm","fixed":["1.3.2"],"introduced":["1.2.0"],"last_affected":[],"package":"@kindspells/astro-shield","purl":"pkg:npm/%40kindspells/astro-shield","source":"GHSA-c4gr-q97g-ppwc"}],"prev":{"headline":"Cloudburst Network DoS in RakNet connection handling","id":"CVE-2024-30249"},"products":["astro-shield"],"published":"2024-04-04","related":[{"cvss_score":7.5,"headline":"Astro-Shield's Content-Security-Policy header generation in middleware could be compromised by malicious injections","id":"CVE-2024-29896","kev_date_added":null,"published":"2024-03-28"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["kindspells"]},"summary":"Attackers can bypass Astro-Shield's allow-lists by injecting code with valid integrity attributes, tricking browsers into accepting malicious resources.","url":"https://insights.sbomify.com/CVE-2024-30250/"}