Bug 929223 (CVE-2013-1899) - CVE-2013-1899 postgresql: Insecure switch parsing
Summary: CVE-2013-1899 postgresql: Insecure switch parsing
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-1899
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=important,public=20130404,repo...
Depends On: 947202 948308 948312
Blocks: 929332
TreeView+ depends on / blocked
 
Reported: 2013-03-29 14:48 UTC by Jan Lieskovsky
Modified: 2019-06-08 19:30 UTC (History)
4 users (show)

Fixed In Version: PostgreSQL 9.0.13, PostgreSQL 9.1.9, PostgreSQL 9.2.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-08 19:26:55 UTC


Attachments (Terms of Use)

Description Jan Lieskovsky 2013-03-29 14:48:40 UTC
A denial of service flaw was found in the way command switch parsing logic of PostgreSQL, an advanced Object-Relational database management system, processed certain database names (a database name beginning with '-' character was interpreted as it if were a command line switch for a standalone backend). A remote attacker could issue a specially-crafted SQL query that, when processed by the PostgreSQL server would lead to unauthorized modification of the server's configuration file or attacker's ability to replace server's critical database / table with a junk file (of their choose), during the server's crash recovery process (denial of service).

Comment 2 Jan Lieskovsky 2013-03-29 14:58:01 UTC
This issue does NOT affect the version of the postgresql package, as shipped with Red Hat Enterprise Linux 5.

--

This issue does NOT affect the version of the postgresql84 package, as shipped with Red Hat Enterprise Linux 5.

--

This issue does NOT affect the version of the postgresql package, as shipped with Red Hat Enterprise Linux 6.

--

This issue affects the versions of the postgresql package, as shipped with Fedora release of 17 and 18.

Comment 3 Jan Lieskovsky 2013-03-29 15:02:13 UTC
Acknowledgements:

Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Mitsumasa Kondo and Kyotaro Horiguchi as the original issue reporters.

Comment 6 Huzaifa S. Sidhpurwala 2013-04-01 06:51:38 UTC
Statement:

Not Vulnerable. This issue does not affect the version of postgresql as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of postgresql84 as shipped with Red Hat Enterprise Linux 5.

Comment 16 Vincent Danen 2013-04-04 14:42:10 UTC
Created postgresql tracking bugs for this issue

Affects: fedora-all [bug 948312]

Comment 17 Tomas Hoger 2013-04-04 14:56:02 UTC
Upstream announcement:

http://www.postgresql.org/about/news/1456/

Comment 18 Fedora Update System 2013-04-05 22:59:19 UTC
postgresql-9.2.4-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 19 Fedora Update System 2013-04-05 23:11:31 UTC
postgresql-9.1.9-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 20 Tomas Hoger 2013-04-07 19:53:01 UTC
Upstream FAQ for this issue:

http://www.postgresql.org/support/security/faq/2013-04-04/

Comment 22 Tomas Hoger 2013-04-10 05:55:51 UTC
LWN article related to this issue, from Josh Berkus is of the PostgreSQL Core Team:

https://lwn.net/Articles/546550/

Comment 23 Tomas Hoger 2013-04-10 05:57:09 UTC
Metasploit scanner to identify vulnerable PostgreSQL versions:

http://dev.metasploit.com/redmine/projects/framework/repository/entry/modules/auxiliary/scanner/postgres/postgres_dbname_flag_injection.rb

Comment 24 Jan Lieskovsky 2013-04-11 06:54:30 UTC
Third party analysis of the issue (and possible consequences):

http://blog.blackwinghq.com/2013/04/08/2/

Comment 25 Fedora Update System 2013-04-20 19:59:22 UTC
postgresql-9.2.4-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.