MGASA-2017-0316: postgresql9.4 Mageia
Vulnerability summary
MGASA-2017-0316 is a vulnerability in postgresql9.4 Mageia with no CVSS score yet.
Advisory lineage
Upstream 3 · Downstream 0Timeline
- 28-08-2017PublishedVulnerability first disclosed.
- 16-04-2026Last modifiedVulnerability information updated.
Description
Updated postgresql9.3/4/6 packages fix security vulnerabilities libpq, and by extension any connection driver that utilizes libpq, ignores empty passwords and does not transmit them to the server. When using libpq or a libpq-based connection driver to perform password-based authentication methods, it would appear that setting an empty password would be the equivalent of disabling password login. However, using a non-libpq based connection driver could allow a client with an empty password to log in (CVE-2017-7546). A user had access to see the options in pg_user_mappings even if the user did not have the USAGE permission on the associated foreign server. This meant that a user could see details such as a password that might have been set by the server administrator rather than the user (CVE-2017-7547). The lo_put() function should require the same permissions as lowrite(), but there was a missing permission check which would allow any user to change the data in a large object (CVE-2017-7548). Note: the CVE-2017-7547 issue requires manual intervention to fix on affected systems. See the references for details.
CVSS metrics
Risk metrics not yet published.
EPSS trend
No EPSS score has been published for this record yet.
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Mageia4 products
- postgresql9.3< 9.3.18-1.mga5
- postgresql9.4< 9.4.13-1.mga5
- postgresql9.4< 9.4.13-1.mga6
- postgresql9.6< 9.6.4-1.mga6
1 vendor · 4 products