Vulnerabilities · 2006 · Postgresql
CVE-2006-2314
Postgresql vulnerability
PostgreSQL 8.1.x before 8.1.4, 8.0.x before 8.0.8, 7.4.x before 7.4.13, 7.3.x before 7.3.15, and earlier versions allows context-dependent attackers to bypass SQL injection protection methods in applications that use multibyte encodings that allow the "\" (backslash) byte 0x5c to be the trailing byte of a multibyte character, such as SJIS, BIG5, GBK, GB18030, and UHC, which cannot be handled correctly by a client that does not understand multibyte encodings, aka a second variant of "Encoding-Based SQL Injection." NOTE: it could be argued that this is a class of issue related to interaction errors between the client and PostgreSQL, but a CVE has been assigned since PostgreSQL is treating this as a preventative measure against this class of problem.
Affected products
Postgresql. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Postgresql runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- archives.postgresql.org/pgsql-announce/2006-05/msg00010.php · Patch
- lists.suse.com/archive/suse-security-announce/2006-Jun/0002.html
- secunia.com/advisories/20231
- secunia.com/advisories/20232
- secunia.com/advisories/20314
- secunia.com/advisories/20435
- secunia.com/advisories/20451
- secunia.com/advisories/20503
- nvd.nist.gov/vuln/detail/CVE-2006-2314
- cve.org/CVERecord?id=CVE-2006-2314
More vulnerabilities in Postgresql products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.