Vulnerability Description
PostgreSQL 7.2.1 and 7.2.2 allows local users to delete transaction log (pg_clog) data and cause a denial of service (data loss) via the VACUUM command.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Postgresql | Postgresql | 7.2 |
References
- http://archives.postgresql.org/pgsql-announce/2002-10/msg00000.phpPatch
- http://www.kb.cert.org/vuls/id/891177PatchUS Government Resource
- http://www.redhat.com/support/errata/RHSA-2003-001.htmlVendor Advisory
- http://www.securityfocus.com/bid/7657Patch
- https://exchange.xforce.ibmcloud.com/vulnerabilities/11102
- http://archives.postgresql.org/pgsql-announce/2002-10/msg00000.phpPatch
- http://www.kb.cert.org/vuls/id/891177PatchUS Government Resource
- http://www.redhat.com/support/errata/RHSA-2003-001.htmlVendor Advisory
- http://www.securityfocus.com/bid/7657Patch
- https://exchange.xforce.ibmcloud.com/vulnerabilities/11102
FAQ
What is CVE-2002-1642?
CVE-2002-1642 is a vulnerability with a CVSS score of 7.2 (HIGH). PostgreSQL 7.2.1 and 7.2.2 allows local users to delete transaction log (pg_clog) data and cause a denial of service (data loss) via the VACUUM command.
How severe is CVE-2002-1642?
CVE-2002-1642 has been rated HIGH with a CVSS base score of 7.2/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2002-1642?
Check the references section above for vendor advisories and patch information. Affected products include: Postgresql Postgresql.