{"answers":{"affected":"2 open source packages ship an affected version, including ibm_db.","exploited":"There is no known exploitation of GHSA-p77h-hv6g-fmfp in the wild and no public exploit code.","fix":"Upgrade ibm_db to 2.6.0 or later.","what":"GHSA-p77h-hv6g-fmfp is a vulnerability in ibm_db, 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-p77h-hv6g-fmfp and fix it if it is affected.\n\nWhat it is: GHSA-p77h-hv6g-fmfp is a vulnerability in ibm_db, 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-p77h-hv6g-fmfp in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ibm_db (npm): affected all versions; fixed in 2.6.0\n- ibm_db (npm): affected all versions; fixed in 2.6.0\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-p77h-hv6g-fmfp/ (Markdown: https://insights.sbomify.com/GHSA-p77h-hv6g-fmfp/index.md)","id":"GHSA-p77h-hv6g-fmfp","markdown":"https://insights.sbomify.com/GHSA-p77h-hv6g-fmfp/index.md","name":"GHSA-p77h-hv6g-fmfp","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Node.js database driver","requires_auth":"none","summary":"Attackers can read database credentials from logs if debug mode is enabled in the ibm_db Node.js library.","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":"Versions of `ibm_db` prior to 2.6.0 are vulnerable to Sensitive Data Exposure. The package printed database credentials in plaintext in logs while in debug mode.\n\n## Recommendation\n\nUpgrade to version 2.6.0 or later and ensure sensitive information was not logged.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Sensitive Data Exposure in ibm_db","id":"GHSA-p77h-hv6g-fmfp","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":["2.6.0"],"introduced":["0"],"last_affected":[],"package":"ibm_db","purl":null,"source":"GHSA-p77h-hv6g-fmfp"},{"ecosystem":"npm","fixed":["2.6.0"],"introduced":["0"],"last_affected":[],"package":"ibm_db","purl":"pkg:npm/ibm_db","source":"GHSA-p77h-hv6g-fmfp"}],"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 database credentials from logs if debug mode is enabled in the ibm_db Node.js library.","url":"https://insights.sbomify.com/GHSA-p77h-hv6g-fmfp/"}