Strix
26.1K

CVE-2017-15099

UnknownEPSS 6.32%

Last modified

CVE-2017-15099 is a vulnerability of currently unknown severity. INSERT ... ON CONFLICT DO UPDATE commands in PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, and 9.5.x before 9.5.10 disclose table contents that the invoker lacks privilege to read. EPSS estimates a 6.32% chance of exploitation in the next 30 days.

Description

INSERT ... ON CONFLICT DO UPDATE commands in PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, and 9.5.x before 9.5.10 disclose table contents that the invoker lacks privilege to read. These exploits affect only tables where the attacker lacks full read access but has both INSERT and UPDATE privileges. Exploits bypass row level security policies and lack of SELECT privilege.

Metrics

EPSS Probability
6.32%

92.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
PostgresqlPostgresql9.5
PostgresqlPostgresql9.5.1
PostgresqlPostgresql9.5.2
PostgresqlPostgresql9.5.3
PostgresqlPostgresql9.5.4
PostgresqlPostgresql9.5.5
PostgresqlPostgresql9.5.6
PostgresqlPostgresql9.5.7
PostgresqlPostgresql9.5.8
PostgresqlPostgresql9.5.9
PostgresqlPostgresql9.6
PostgresqlPostgresql9.6.1
PostgresqlPostgresql9.6.2
PostgresqlPostgresql9.6.3
PostgresqlPostgresql9.6.4
PostgresqlPostgresql9.6.5
PostgresqlPostgresql10.0
DebianDebian Linux9.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-15099?
INSERT ... ON CONFLICT DO UPDATE commands in PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, and 9.5.x before 9.5.10 disclose table contents that the invoker lacks privilege to read. These exploits affect only tables where the attacker lacks full read access but has both INSERT and UPDATE privileges. Exploits bypass row level security policies and lack of SELECT privilege.
How severe is CVE-2017-15099?
Severity scoring for CVE-2017-15099 is pending analysis. The EPSS model estimates a 6.32% probability of exploitation in the next 30 days.
How do I fix CVE-2017-15099?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-15099?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST