CVE-2024-4317: PostgreSQL pg_stats_ext and pg_stats_ext_exprs lack authorization checks

Published May 9, 2024
·
Updated

Last updated 24 July 2024

Other sources

Missing authorization in PostgreSQL built-in views pgstatsext and pgstatsextexprs allows an unprivileged database user to read most common values and other statistics from CREATE STATISTICS commands of other users. The most common values may reveal column values the eavesdropper could not otherwise read or results of functions they cannot execute. Installing an unaffected version only fixes fresh PostgreSQL installations, namely those that are created with the initdb utility after installing that version. Current PostgreSQL installations will remain vulnerable until they follow the instructions in the release notes. Within major versions 14-16, minor versions before PostgreSQL 16.3, 15.7, and 14.12 are affected. Versions before PostgreSQL 14 are unaffected.

Launchpad

Affected Software

9 affected componentsFixes available
debian/postgresql-13
13.16-0+deb11u1
debian/postgresql-15<=15.8-0+deb12u1
debian/postgresql-16
16.4-1
PostgreSQL postgresql>=14.0<14.12
PostgreSQL postgresql>=15.0<15.7
PostgreSQL postgresql>=16.0<16.3
redhat/postgresql<16.3
16.3
redhat/postgresql<15.7
15.7
redhat/postgresql<14.12
14.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/postgresql-13 to a version that resolves this vulnerability.

    Fixed in 13.16-0+deb11u1
  2. Upgrade

    Upgrade debian/postgresql-16 to a version that resolves this vulnerability.

    Fixed in 16.4-1
  3. Upgrade

    Upgrade redhat/postgresql to a version that resolves this vulnerability.

    Fixed in 16.3
  4. Upgrade

    Upgrade redhat/postgresql to a version that resolves this vulnerability.

    Fixed in 15.7
  5. Upgrade

    Upgrade redhat/postgresql to a version that resolves this vulnerability.

    Fixed in 14.12
  6. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 16.3
  7. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 15.7
  8. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 14.12

Event History

May 9, 2024
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
May 14, 2024
Data Sourced
via NVD·03:43 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:43 PM
Affected Software
May 30, 2024
Data Sourced
via Launchpad·02:56 PM
Description
Sep 15, 2024
Data Sourced
via Ubuntu·03:11 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-4317?

CVE-2024-4317 is considered a medium severity vulnerability due to its potential to leak sensitive statistical information from PostgreSQL.

2

How do I fix CVE-2024-4317?

To remediate CVE-2024-4317, upgrade PostgreSQL to the recommended versions, including 13.16-0+deb11u1 for Debian or 16.4-1 for PostgreSQL 16.

3

Which PostgreSQL versions are affected by CVE-2024-4317?

CVE-2024-4317 affects PostgreSQL versions 13, 14, 15, and 16 up to specific release levels.

4

Can unprivileged users exploit CVE-2024-4317?

Yes, unprivileged database users can exploit CVE-2024-4317 to access statistical information of other users.

5

What are the risks of CVE-2024-4317?

The risks associated with CVE-2024-4317 include potential exposure of sensitive data through statistical values accessible to unauthorized users.

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