Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1539613 - (CVE-2018-1052) CVE-2018-1052 postgresql: Memory disclosure in table partitioning
CVE-2018-1052 postgresql: Memory disclosure in table partitioning
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180208,repor...
: Security
Depends On: 1539615
Blocks: 1539623
  Show dependency treegraph
 
Reported: 2018-01-29 05:36 EST by Adam Mariš
Modified: 2018-03-13 01:11 EDT (History)
58 users (show)

See Also:
Fixed In Version: postgresql 10.2
Doc Type: If docs needed, set a value
Doc Text:
A memory disclosure vulnerability in table partitioning was found in postgresql, allowing an authenticated attacker to read arbitrary bytes of server memory via purpose-crafted insert to a partitioned table.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-12 04:54:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2018-01-29 05:36:29 EST
Using a purpose-crafted insert to a partitioned table, an attacker can read arbitrary bytes of server memory. In the default configuration, any user can create a partitioned table suitable for this attack.

Vulnerable Versions: 10
Comment 1 Adam Mariš 2018-01-29 05:36:32 EST
Acknowledgments:

Name: the PostgreSQL project
Upstream: Álvaro Herrera, David Rowley
Comment 3 Adam Mariš 2018-02-09 03:12:43 EST
External References:

https://www.postgresql.org/about/news/1829/
Comment 4 Kurt Seifried 2018-02-13 11:51:20 EST
Statement:

This issue did not affect the versions of PostgreSQL as shipped with Red Hat Satellite 5 and CloudForms 5 as they use PostgreSQL version 9.x and this vulnerability is specific to PostgreSQL 10.x.

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