{"answers":{"affected":"2 open source packages ship an affected version, including put.","exploited":"There is no known exploitation of GHSA-v6gv-fg46-h89j in the wild and no public exploit code.","fix":"No fix has been published for GHSA-v6gv-fg46-h89j yet. Limit exposure of the affected software until one is available.","what":"GHSA-v6gv-fg46-h89j is a vulnerability in put, published on 3 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-v6gv-fg46-h89j and fix it if it is affected.\n\nWhat it is: GHSA-v6gv-fg46-h89j is a vulnerability in put, published on 3 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-v6gv-fg46-h89j in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- put (npm): affected all versions; no fix listed\n- put (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-v6gv-fg46-h89j/ (Markdown: https://insights.sbomify.com/GHSA-v6gv-fg46-h89j/index.md)","id":"GHSA-v6gv-fg46-h89j","markdown":"https://insights.sbomify.com/GHSA-v6gv-fg46-h89j/index.md","name":"GHSA-v6gv-fg46-h89j","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js buffer library","requires_auth":"none","summary":"Attackers can read sensitive uninitialized memory data due to incorrect buffer size calculation in the put package on older Node.js versions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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 `put` are vulnerable to Uninitialized Memory Exposure. The package incorrectly calculates the allocated Buffer size and does not trim the bytes written, which may allow attackers to access uninitialized memory containing sensitive data. This vulnerability only affects versions of Node.js \u003c=6.x.\n\n## Recommendation\n\nUpgrade your Node.js version or 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":"Sensitive Data Exposure in put","id":"GHSA-v6gv-fg46-h89j","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":[],"package":"put","purl":null,"source":"GHSA-v6gv-fg46-h89j"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":[],"package":"put","purl":"pkg:npm/put","source":"GHSA-v6gv-fg46-h89j"}],"products":null,"published":"2020-09-03","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 read sensitive uninitialized memory data due to incorrect buffer size calculation in the put package on older Node.js versions.","url":"https://insights.sbomify.com/GHSA-v6gv-fg46-h89j/"}