SQL Injection Affecting postgresql package, versions [,7.3.15)[7.4.0,7.4.13)[8.0.0,8.0.8)[8.1.0,8.1.4)


Severity

Recommended
0.0
high
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
1.16% (85th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about SQL Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-UNMANAGED-POSTGRESQL-2336066
  • published12 Jan 2022
  • disclosed24 May 2006
  • creditUnknown

Introduced: 24 May 2006

CVE-2006-2314  (opens in a new tab)
CWE-89  (opens in a new tab)

How to fix?

Upgrade postgresql to version 7.3.15, 7.4.13, 8.0.8, 8.1.4 or higher.

Overview

Affected versions of this package are vulnerable to SQL Injection. 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.

CVSS Scores

version 3.1