CVE-2002-1642: High severity PostgreSQL postgresql vulnerability
Published Oct 3, 2002
·Updated
PostgreSQL 7.2.1 and 7.2.2 allows local users to delete transaction log (pgclog) data and cause a denial of service (data loss) via the VACUUM command.
Affected Software
3 affected components
PostgreSQL postgresql=7.2
PostgreSQL postgresql=7.2.2
PostgreSQL postgresql=7.2.1
Remediation
Patch Available
Patch Available
Event History
Oct 3, 2002
CVE Published
04:00 AM
Mar 28, 2005
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2002-1642?
CVE-2002-1642 has a high severity rating due to its potential to cause denial of service and data loss.
2
How do I fix CVE-2002-1642?
To fix CVE-2002-1642, users should upgrade to a version of PostgreSQL that is not affected, specifically any version later than 7.2.2.
3
What impact does CVE-2002-1642 have on PostgreSQL databases?
The impact of CVE-2002-1642 includes the ability for local users to delete transaction log data, leading to service disruptions and possible data loss.
4
Who is affected by CVE-2002-1642?
Local users of PostgreSQL versions 7.2 and 7.2.2 are affected by CVE-2002-1642.
5
What versions of PostgreSQL are vulnerable to CVE-2002-1642?
PostgreSQL versions 7.2.1 and 7.2.2 are vulnerable to CVE-2002-1642.