CVE-2002-1642
First published: Thu Oct 03 2002(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PostgreSQL Common | =7.2 | |
| PostgreSQL Common | =7.2.2 | |
| PostgreSQL Common | =7.2.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
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.
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.
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.
Who is affected by CVE-2002-1642?
Local users of PostgreSQL versions 7.2 and 7.2.2 are affected by CVE-2002-1642.
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.
- agent/type
- agent/first-publish-date
- agent/remedy
- agent/references
- agent/weakness
- agent/severity
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/postgresql
- canonical/postgresql common
- version/postgresql common/7.2
- version/postgresql common/7.2.2
- version/postgresql common/7.2.1