{"answers":{"affected":"2 open source packages ship an affected version, including parsel.","exploited":"There is no known exploitation of GHSA-wqgx-4q47-j2w5 in the wild and no public exploit code.","fix":"No fix has been published for GHSA-wqgx-4q47-j2w5 yet. Limit exposure of the affected software until one is available.","what":"GHSA-wqgx-4q47-j2w5 is a vulnerability in parsel, published on 4 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-wqgx-4q47-j2w5 and fix it if it is affected.\n\nWhat it is: GHSA-wqgx-4q47-j2w5 is a vulnerability in parsel, published on 4 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-wqgx-4q47-j2w5 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- parsel (npm): affected from 0.0.0; no fix listed\n- parsel (npm): affected from 0.0.0; 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-wqgx-4q47-j2w5/ (Markdown: https://insights.sbomify.com/GHSA-wqgx-4q47-j2w5/index.md)","id":"GHSA-wqgx-4q47-j2w5","markdown":"https://insights.sbomify.com/GHSA-wqgx-4q47-j2w5/index.md","name":"GHSA-wqgx-4q47-j2w5","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"end_of_life","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"npm cryptography library","requires_auth":"none","summary":"The parsel library uses insecure AES-256-CBC without integrity checks, allowing bit-flipping attacks; developers should migrate to a maintained alternative.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"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 `parsel` use an insecure cryptography algorithm. The package uses `aes-256-cbc` without integrity checks, which renders the ciphertext vulnerable to bit-flipping attacks.\n\n## Recommendation\n\nThe package is deprecated and will not be updated. Consider using an alternative package.","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":"Insecure Cryptography Algorithm in parsel","id":"GHSA-wqgx-4q47-j2w5","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"parsel","purl":null,"source":"GHSA-wqgx-4q47-j2w5"},{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"parsel","purl":"pkg:npm/parsel","source":"GHSA-wqgx-4q47-j2w5"}],"products":null,"published":"2020-09-04","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":"The parsel library uses insecure AES-256-CBC without integrity checks, allowing bit-flipping attacks; developers should migrate to a maintained alternative.","url":"https://insights.sbomify.com/GHSA-wqgx-4q47-j2w5/"}