CVE-2002-0802: SQL Injection
First published: Mon Aug 12 2002(Updated: )
The multibyte support in PostgreSQL 6.5.x with SQL_ASCII encoding consumes an extra character when processing a character that cannot be converted, which could remove an escape character from the query and make the application subject to SQL injection attacks.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PostgreSQL Common | =6.5.0 |
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-0802?
CVE-2002-0802 is considered a high severity vulnerability due to its potential for causing SQL injection attacks.
How do I fix CVE-2002-0802?
To mitigate CVE-2002-0802, it is recommended to upgrade PostgreSQL to a version that does not have this vulnerability.
Which versions of PostgreSQL are affected by CVE-2002-0802?
CVE-2002-0802 specifically affects PostgreSQL version 6.5.0 when using SQL_ASCII encoding.
What type of attack can CVE-2002-0802 allow?
CVE-2002-0802 could allow attackers to execute SQL injection attacks by manipulating the input query.
Does CVE-2002-0802 have a workaround?
There are no specific workarounds for CVE-2002-0802; upgrading to a fixed version is the recommended solution.
- agent/type
- agent/first-publish-date
- agent/references
- agent/weakness
- agent/severity
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/postgresql
- canonical/postgresql common
- version/postgresql common/6.5.0