security flaw

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 byt...

security flaw

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 via invalid encodings of multibyte characters, aka one variant of "Encoding-Based SQL...

postgresql -- encoding based SQL injection

The PostgreSQL development team reports: An attacker able to submit crafted strings to an application that will embed those strings in SQL commands can use invalidly-encoded multibyte characters to bypass standard string-escaping methods, resulting in possible injection of hostile SQL commands in...

CVE-2002-0802

The CVE-2002-0802 entry documents a vulnerability in PostgreSQL 6.5.x when using the SQL_ASCII encoding: multibyte support can consume an extra character while processing a character that cannot be converted, potentially removing an escape character from the query and making the application susce...

CVE-2002-0802

The multibyte support in PostgreSQL 6.5.x with SQLASCII 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...

@(#)Mordred Labs advisory 0x0004: Multiple buffer overflows in PostgreSQL.

//@ Mordred Labs advisory 0x0004 Release data: 20/08/02 Name: Two buffer overflows in PostgreSQL Versions affected: all versions Conditions: multibyte support Risk: average -- Description: I guess all of you already hear about the PostgreSQL. If not, try to visit...

CVE-2002-0802

The multibyte support in PostgreSQL 6.5.x with SQLASCII 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...