CVE-2017-7486: Infoleak

Published May 4, 2017
·
Updated

A typical CREATE USER MAPPING command persists a foreign password in an "option" of the user mapping. Contrary to its documentation and at variance with the informationschema.usermappingoptions view, the pgusermappings view discloses user mapping options to any user having USAGE privilege on the associated foreign server. If someone revokes the USAGE grant, an attacker having captured the password this way might use it to connect another way. An attacker may use the password to run arbitrary queries against the server or others accepting the same credentials, not just the limited queries one can issue via foreign tables.

Affected versions: 8.4 - 9.6

Other sources

PostgreSQL versions 8.4 - 9.6 are vulnerable to information leak in pgusermappings view which discloses foreign server passwords to any user having USAGE privilege on the associated foreign server.

Affected Software

139 affected componentsFixes available
redhat/postgresql<9.2.21
9.2.21
redhat/postgresql<9.3.17
9.3.17
redhat/postgresql<9.4.12
9.4.12
redhat/postgresql<9.5.7
9.5.7
redhat/postgresql<9.6.3
9.6.3
PostgreSQL postgresql=8.4
PostgreSQL postgresql=8.4.1
PostgreSQL postgresql=8.4.2
PostgreSQL postgresql=8.4.3
PostgreSQL postgresql=8.4.4
PostgreSQL postgresql=8.4.5
PostgreSQL postgresql=8.4.6
PostgreSQL postgresql=8.4.7
PostgreSQL postgresql=8.4.8
PostgreSQL postgresql=8.4.9
PostgreSQL postgresql=8.4.10
PostgreSQL postgresql=8.4.11
PostgreSQL postgresql=8.4.12
PostgreSQL postgresql=8.4.13
PostgreSQL postgresql=8.4.14
PostgreSQL postgresql=8.4.15
PostgreSQL postgresql=8.4.16
PostgreSQL postgresql=8.4.17
PostgreSQL postgresql=8.4.18
PostgreSQL postgresql=8.4.19
PostgreSQL postgresql=8.4.20
PostgreSQL postgresql=8.4.21
PostgreSQL postgresql=8.4.22
PostgreSQL postgresql=9.0
PostgreSQL postgresql=9.0.1
PostgreSQL postgresql=9.0.2
PostgreSQL postgresql=9.0.3
PostgreSQL postgresql=9.0.4
PostgreSQL postgresql=9.0.5
PostgreSQL postgresql=9.0.6
PostgreSQL postgresql=9.0.7
PostgreSQL postgresql=9.0.8
PostgreSQL postgresql=9.0.9
PostgreSQL postgresql=9.0.10
PostgreSQL postgresql=9.0.11
PostgreSQL postgresql=9.0.12
PostgreSQL postgresql=9.0.13
PostgreSQL postgresql=9.0.14
PostgreSQL postgresql=9.0.15
PostgreSQL postgresql=9.0.16
PostgreSQL postgresql=9.0.17
PostgreSQL postgresql=9.0.18
PostgreSQL postgresql=9.0.19
PostgreSQL postgresql=9.0.20
PostgreSQL postgresql=9.0.21
PostgreSQL postgresql=9.0.22
PostgreSQL postgresql=9.0.23
PostgreSQL postgresql=9.1
PostgreSQL postgresql=9.1.1
PostgreSQL postgresql=9.1.2
PostgreSQL postgresql=9.1.3
PostgreSQL postgresql=9.1.4
PostgreSQL postgresql=9.1.5
PostgreSQL postgresql=9.1.6
PostgreSQL postgresql=9.1.7
PostgreSQL postgresql=9.1.8
PostgreSQL postgresql=9.1.9
PostgreSQL postgresql=9.1.10
PostgreSQL postgresql=9.1.11
PostgreSQL postgresql=9.1.12
PostgreSQL postgresql=9.1.13
PostgreSQL postgresql=9.1.14
PostgreSQL postgresql=9.1.15
PostgreSQL postgresql=9.1.16
PostgreSQL postgresql=9.1.17
PostgreSQL postgresql=9.1.18
PostgreSQL postgresql=9.1.19
PostgreSQL postgresql=9.1.20
PostgreSQL postgresql=9.1.21
PostgreSQL postgresql=9.1.22
PostgreSQL postgresql=9.1.23
PostgreSQL postgresql=9.1.24
PostgreSQL postgresql=9.2
PostgreSQL postgresql=9.2.1
PostgreSQL postgresql=9.2.2
PostgreSQL postgresql=9.2.3
PostgreSQL postgresql=9.2.4
PostgreSQL postgresql=9.2.5
PostgreSQL postgresql=9.2.6
PostgreSQL postgresql=9.2.7
PostgreSQL postgresql=9.2.8
PostgreSQL postgresql=9.2.9
PostgreSQL postgresql=9.2.10
PostgreSQL postgresql=9.2.11
PostgreSQL postgresql=9.2.12
PostgreSQL postgresql=9.2.13
PostgreSQL postgresql=9.2.14
PostgreSQL postgresql=9.2.15
PostgreSQL postgresql=9.2.16
PostgreSQL postgresql=9.2.17
PostgreSQL postgresql=9.2.18
PostgreSQL postgresql=9.2.19
PostgreSQL postgresql=9.2.20
PostgreSQL postgresql=9.2.21
PostgreSQL postgresql=9.3
PostgreSQL postgresql=9.3.1
PostgreSQL postgresql=9.3.2
PostgreSQL postgresql=9.3.3
PostgreSQL postgresql=9.3.4
PostgreSQL postgresql=9.3.5
PostgreSQL postgresql=9.3.6
PostgreSQL postgresql=9.3.7
PostgreSQL postgresql=9.3.8
PostgreSQL postgresql=9.3.9
PostgreSQL postgresql=9.3.10
PostgreSQL postgresql=9.3.11
PostgreSQL postgresql=9.3.12
PostgreSQL postgresql=9.3.13
PostgreSQL postgresql=9.3.14
PostgreSQL postgresql=9.3.15
PostgreSQL postgresql=9.3.16
PostgreSQL postgresql=9.3.17
PostgreSQL postgresql=9.4
PostgreSQL postgresql=9.4.1
PostgreSQL postgresql=9.4.2
PostgreSQL postgresql=9.4.3
PostgreSQL postgresql=9.4.4
PostgreSQL postgresql=9.4.5
PostgreSQL postgresql=9.4.6
PostgreSQL postgresql=9.4.7
PostgreSQL postgresql=9.4.8
PostgreSQL postgresql=9.4.9
PostgreSQL postgresql=9.4.10
PostgreSQL postgresql=9.4.11
PostgreSQL postgresql=9.4.12
PostgreSQL postgresql=9.5
PostgreSQL postgresql=9.5.1
PostgreSQL postgresql=9.5.2
PostgreSQL postgresql=9.5.3
PostgreSQL postgresql=9.5.4
PostgreSQL postgresql=9.5.5
PostgreSQL postgresql=9.5.6
PostgreSQL postgresql=9.5.7
PostgreSQL postgresql=9.6

Event History

May 12, 2017
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2017-7486?

CVE-2017-7486 has been classified as a moderate severity vulnerability affecting PostgreSQL.

2

How do I fix CVE-2017-7486?

To fix CVE-2017-7486, you need to upgrade PostgreSQL to version 9.2.21 or later, 9.3.17 or later, 9.4.12 or later, 9.5.7 or later, or 9.6.3 or later.

3

Which versions of PostgreSQL are affected by CVE-2017-7486?

CVE-2017-7486 affects PostgreSQL versions 8.4 through 9.6.

4

What does CVE-2017-7486 vulnerability expose?

CVE-2017-7486 exposes foreign server passwords through the pg_user_mappings view to any user with USAGE privilege on the foreign server.

5

Is CVE-2017-7486 still a risk if running a supported version of PostgreSQL?

If running a version of PostgreSQL that has been updated to the recommended releases, CVE-2017-7486 should no longer pose a risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203