Bug 1188694 (CVE-2015-0244) - CVE-2015-0244 postgresql: loss of frontend/backend protocol synchronization after an error
Summary: CVE-2015-0244 postgresql: loss of frontend/backend protocol synchronization a...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2015-0244
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1192909 1192910 1198651 1198652 1198653 1198654 1198663 1198672 1198673 1198733
Blocks: 1188677
TreeView+ depends on / blocked
 
Reported: 2015-02-03 14:39 UTC by Martin Prpič
Modified: 2021-10-20 10:49 UTC (History)
15 users (show)

Fixed In Version: postgresql 9.0.19, postgresql 9.1.15, postgresql 9.2.10, postgresql 9.3.6, postgresql 9.4.1
Doc Type: Bug Fix
Doc Text:
A flaw was found in the way PostgreSQL handled certain errors that were generated during protocol synchronization. An authenticated database user could use this flaw to inject queries into an existing connection.
Clone Of:
Environment:
Last Closed: 2021-10-20 10:33:36 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0699 0 normal SHIPPED_LIVE Moderate: postgresql92-postgresql security update 2015-03-18 20:35:35 UTC
Red Hat Product Errata RHSA-2015:0750 0 normal SHIPPED_LIVE Moderate: postgresql security update 2015-03-30 15:30:43 UTC
Red Hat Product Errata RHSA-2015:0856 0 normal SHIPPED_LIVE Moderate: postgresql92-postgresql security update 2015-04-20 13:46:03 UTC

Description Martin Prpič 2015-02-03 14:39:49 UTC
The PostgreSQL project reports the following issue:

If any error occurred while the server was in the middle of reading a protocol message from the client, it could lose synchronization and incorrectly try to interpret part of the message's data as a new protocol message. An attacker able to submit crafted binary data within a command parameter might succeed in injecting his own SQL commands this way. Statement timeout and query cancellation are the most likely sources of errors triggering this scenario. Particularly vulnerable are applications that use a timeout and also submit arbitrary user-crafted data as binary query parameters. Disabling statement timeout will reduce, but not eliminate, the risk of exploit.

Acknowledgements:

Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Emil Lenngren as the original reporter.

Comment 1 Huzaifa S. Sidhpurwala 2015-02-16 05:17:28 UTC
External References:

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

Comment 2 Huzaifa S. Sidhpurwala 2015-02-16 05:54:43 UTC
Upstream commit:

https://github.com/postgres/postgres/commit/2b3a8b20c2da9f39ffecae25ab7c66974fbc0d3b

Comment 3 Huzaifa S. Sidhpurwala 2015-02-16 06:52:53 UTC
This issue was addressed in Fedora 20 and Fedora 21 via the following security advisories:

https://admin.fedoraproject.org/updates/FEDORA-2015-1728/postgresql-9.3.6-1.fc20
https://admin.fedoraproject.org/updates/FEDORA-2015-1745/postgresql-9.3.6-1.fc21

Comment 12 errata-xmlrpc 2015-03-18 16:36:22 UTC
This issue has been addressed in the following products:

  Red Hat Software Collections 1 for Red Hat Enterprise Linux 7
  Red Hat Software Collections 1 for Red Hat Enterprise Linux 6.6 EUS
  Red Hat Software Collections 1 for Red Hat Enterprise Linux 6
  Red Hat Software Collections 1 for Red Hat Enterprise Linux 6.5 EUS

Via RHSA-2015:0699 https://rhn.redhat.com/errata/RHSA-2015-0699.html

Comment 13 errata-xmlrpc 2015-03-30 11:31:55 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7
  Red Hat Enterprise Linux 6

Via RHSA-2015:0750 https://rhn.redhat.com/errata/RHSA-2015-0750.html

Comment 14 errata-xmlrpc 2015-04-20 09:46:37 UTC
This issue has been addressed in the following products:

  Red Hat Satellite Server v 5.7

Via RHSA-2015:0856 https://rhn.redhat.com/errata/RHSA-2015-0856.html


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