{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1657 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1657 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1657 is a high-severity vulnerability in Postgresql Postgresql, published on 22 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-1657 and fix it if it is affected.\n\nWhat it is: CVE-2002-1657 is a high-severity vulnerability in Postgresql Postgresql, published on 22 Apr 2005. 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-2002-1657 in the wild and no public exploit code.\n\nAffected product: Postgresql Postgresql. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2002-1657/ (Markdown: https://insights.sbomify.com/CVE-2002-1657/index.md)","id":"CVE-2002-1657","markdown":"https://insights.sbomify.com/CVE-2002-1657/index.md","name":"CVE-2002-1657","record":{"aliases":["GHSA-vjwv-wcj8-hxqj"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"PostgreSQL database","requires_auth":"none","summary":"PostgreSQL uses the username as a password salt, weakening password security and facilitating brute-force attacks against user credentials.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"postgresql","vendor":"postgresql"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-916","name":"Use of Password Hash With Insufficient Computational Effort"}],"description":"PostgreSQL uses the username for a salt when generating passwords, which makes it easier for remote attackers to guess passwords via a brute force attack.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2002-1657","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"postgresql:postgresql","products":["postgresql:postgresql"],"type":"weak_cryptography","year":"2002"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2002-1658"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2002-1656"},"products":["n/a"],"published":"2005-04-22","related":[{"cvss_score":10,"headline":"Information disclosure in n/a","id":"CVE-2013-1902","kev_date_added":null,"published":"2013-04-04"},{"cvss_score":10,"headline":"Information disclosure in n/a","id":"CVE-2013-1903","kev_date_added":null,"published":"2013-04-04"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2007-3279","kev_date_added":null,"published":"2007-06-19"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2002-1399","kev_date_added":null,"published":"2003-01-08"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2016-3065","kev_date_added":null,"published":"2016-04-11"},{"cvss_score":9,"headline":"Code injection in n/a","id":"CVE-2007-3280","kev_date_added":null,"published":"2007-06-19"},{"cvss_score":8.8,"headline":"PostgreSQL tsvector and tsquery undersize allocations, via integer wraparound","id":"CVE-2026-14662","kev_date_added":null,"published":"2026-08-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-01-16","vendors":["n/a"]},"summary":"PostgreSQL uses the username as a password salt, weakening password security and facilitating brute-force attacks against user credentials.","url":"https://insights.sbomify.com/CVE-2002-1657/"}