{"answers":{"affected":"2 open source packages ship an affected version, including value-censorship.","exploited":"There is no known exploitation of GHSA-xrr6-6ww3-f3qm in the wild and no public exploit code.","fix":"No fix has been published for GHSA-xrr6-6ww3-f3qm yet. Limit exposure of the affected software until one is available.","what":"GHSA-xrr6-6ww3-f3qm is a code injection vulnerability in value-censorship, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-xrr6-6ww3-f3qm and fix it if it is affected.\n\nWhat it is: GHSA-xrr6-6ww3-f3qm is a code injection vulnerability in value-censorship, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-xrr6-6ww3-f3qm in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- value-censorship (npm): affected all versions; no fix listed\n- value-censorship (npm): affected all versions; no fix listed\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/GHSA-xrr6-6ww3-f3qm/ (Markdown: https://insights.sbomify.com/GHSA-xrr6-6ww3-f3qm/index.md)","id":"GHSA-xrr6-6ww3-f3qm","markdown":"https://insights.sbomify.com/GHSA-xrr6-6ww3-f3qm/index.md","name":"GHSA-xrr6-6ww3-f3qm","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"npm value-censorship library","requires_auth":"none","summary":"Attackers can execute arbitrary code via sandbox escape in the value-censorship npm package due to insufficient validation of async function constructors.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"All versions of `value-censorship` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to validate async function constructors allowing attackers to execute arbitrary code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Sandbox Breakout / Arbitrary Code Execution in value-censorship","id":"GHSA-xrr6-6ww3-f3qm","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":[],"package":"value-censorship","purl":null,"source":"GHSA-xrr6-6ww3-f3qm"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":[],"package":"value-censorship","purl":"pkg:npm/value-censorship","source":"GHSA-xrr6-6ww3-f3qm"}],"products":null,"published":"2020-09-02","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can execute arbitrary code via sandbox escape in the value-censorship npm package due to insufficient validation of async function constructors.","url":"https://insights.sbomify.com/GHSA-xrr6-6ww3-f3qm/"}