Bug 1221541 (CVE-2015-3167) - CVE-2015-3167 postgresql: pgcrypto has multiple error messages for decryption with an incorrect key.
Summary: CVE-2015-3167 postgresql: pgcrypto has multiple error messages for decryption...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2015-3167
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: 1224319 1224320 1225794 1225795 1225797 1225798 1225799 1232680 1232685
Blocks: 1221543
TreeView+ depends on / blocked
 
Reported: 2015-05-14 10:21 UTC by Martin Prpič
Modified: 2023-05-12 09:03 UTC (History)
30 users (show)

Fixed In Version: postgresql 9.4.2, postgresql 9.3.7, postgresql 9.2.11, postgresql 9.1.16, postgresql 9.0.20
Doc Type: Bug Fix
Doc Text:
It was discovered that the pgcrypto module could return different error messages when decrypting certain data with an incorrect key. This could potentially help an authenticated user to launch a possible cryptographic attack, although no suitable attack is currently known.
Clone Of:
Environment:
Last Closed: 2015-07-10 04:31:49 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1194 0 normal SHIPPED_LIVE Moderate: postgresql security update 2015-06-29 20:43:24 UTC
Red Hat Product Errata RHSA-2015:1195 0 normal SHIPPED_LIVE Moderate: postgresql92-postgresql security update 2015-06-29 20:09:47 UTC
Red Hat Product Errata RHSA-2015:1196 0 normal SHIPPED_LIVE Moderate: rh-postgresql94-postgresql security update 2015-06-29 20:09:05 UTC

Description Martin Prpič 2015-05-14 10:21:49 UTC
The PostgreSQL project reports the following issue:

pgcrypto functions usually reported "Wrong key or corrupt data" upon decrypting with an incorrect key, but several other messages were possible when the errant decryption output resembled an OpenPGP packet header. Error message variance in other systems has enabled cryptologic attacks; see RFC 4880 section "14. Security Considerations". Whether these pgcrypto behaviors are likewise exploitable is unknown.

This flaw is fixed in upstream versions 9.4.2, 9.3.7, 9.2.11, 9.1.16, and 9.0.20 of PostgreSQL.

Acknowledgements:

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

Comment 3 Stefan Cornelius 2015-05-22 14:29:07 UTC
Public via:
http://www.postgresql.org/about/news/1587/

Comment 10 errata-xmlrpc 2015-06-29 16:09:34 UTC
This issue has been addressed in the following products:

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

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

Comment 11 errata-xmlrpc 2015-06-29 16:10:49 UTC
This issue has been addressed in the following products:

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

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

Comment 12 errata-xmlrpc 2015-06-29 16:45:28 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6
  Red Hat Enterprise Linux 7

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

Comment 13 Martin Prpič 2015-07-24 07:10:26 UTC
Statement:

Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This flaw has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.


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