medium
5.5
CWE
264
Advisory Published
Updated

CVE-2010-1975

First published: Wed May 19 2010(Updated: )

PostgreSQL 7.4 before 7.4.29, 8.0 before 8.0.25, 8.1 before 8.1.21, 8.2 before 8.2.17, 8.3 before 8.3.11, and 8.4 before 8.4.4 does not properly check privileges during certain RESET ALL operations, which allows remote authenticated users to remove arbitrary parameter settings via a (1) ALTER USER or (2) ALTER DATABASE statement.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
PostgreSQL Common=7.4
PostgreSQL Common=7.4.1
PostgreSQL Common=7.4.2
PostgreSQL Common=7.4.3
PostgreSQL Common=7.4.4
PostgreSQL Common=7.4.5
PostgreSQL Common=7.4.6
PostgreSQL Common=7.4.7
PostgreSQL Common=7.4.8
PostgreSQL Common=7.4.9
PostgreSQL Common=7.4.10
PostgreSQL Common=7.4.11
PostgreSQL Common=7.4.12
PostgreSQL Common=7.4.13
PostgreSQL Common=7.4.14
PostgreSQL Common=7.4.15
PostgreSQL Common=7.4.16
PostgreSQL Common=7.4.17
PostgreSQL Common=7.4.18
PostgreSQL Common=7.4.19
PostgreSQL Common=7.4.20
PostgreSQL Common=7.4.21
PostgreSQL Common=7.4.22
PostgreSQL Common=7.4.23
PostgreSQL Common=7.4.24
PostgreSQL Common=7.4.25
PostgreSQL Common=7.4.26
PostgreSQL Common=7.4.27
PostgreSQL Common=7.4.28
PostgreSQL Common=8.0
PostgreSQL Common=8.0.0
PostgreSQL Common=8.0.1
PostgreSQL Common=8.0.2
PostgreSQL Common=8.0.3
PostgreSQL Common=8.0.4
PostgreSQL Common=8.0.5
PostgreSQL Common=8.0.6
PostgreSQL Common=8.0.7
PostgreSQL Common=8.0.8
PostgreSQL Common=8.0.9
PostgreSQL Common=8.0.10
PostgreSQL Common=8.0.11
PostgreSQL Common=8.0.12
PostgreSQL Common=8.0.13
PostgreSQL Common=8.0.14
PostgreSQL Common=8.0.15
PostgreSQL Common=8.0.16
PostgreSQL Common=8.0.17
PostgreSQL Common=8.0.18
PostgreSQL Common=8.0.19
PostgreSQL Common=8.0.20
PostgreSQL Common=8.0.21
PostgreSQL Common=8.0.22
PostgreSQL Common=8.0.23
PostgreSQL Common=8.0.24
PostgreSQL Common=8.1
PostgreSQL Common=8.1.0
PostgreSQL Common=8.1.1
PostgreSQL Common=8.1.2
PostgreSQL Common=8.1.3
PostgreSQL Common=8.1.4
PostgreSQL Common=8.1.5
PostgreSQL Common=8.1.6
PostgreSQL Common=8.1.7
PostgreSQL Common=8.1.8
PostgreSQL Common=8.1.9
PostgreSQL Common=8.1.10
PostgreSQL Common=8.1.11
PostgreSQL Common=8.1.12
PostgreSQL Common=8.1.13
PostgreSQL Common=8.1.14
PostgreSQL Common=8.1.15
PostgreSQL Common=8.1.16
PostgreSQL Common=8.1.17
PostgreSQL Common=8.1.18
PostgreSQL Common=8.1.19
PostgreSQL Common=8.1.20
PostgreSQL Common=8.2
PostgreSQL Common=8.2.1
PostgreSQL Common=8.2.2
PostgreSQL Common=8.2.3
PostgreSQL Common=8.2.4
PostgreSQL Common=8.2.5
PostgreSQL Common=8.2.6
PostgreSQL Common=8.2.7
PostgreSQL Common=8.2.8
PostgreSQL Common=8.2.9
PostgreSQL Common=8.2.10
PostgreSQL Common=8.2.11
PostgreSQL Common=8.2.12
PostgreSQL Common=8.2.13
PostgreSQL Common=8.2.14
PostgreSQL Common=8.2.15
PostgreSQL Common=8.2.16
PostgreSQL Common=8.3
PostgreSQL Common=8.3.1
PostgreSQL Common=8.3.2
PostgreSQL Common=8.3.3
PostgreSQL Common=8.3.4
PostgreSQL Common=8.3.5
PostgreSQL Common=8.3.6
PostgreSQL Common=8.3.7
PostgreSQL Common=8.3.8
PostgreSQL Common=8.3.9
PostgreSQL Common=8.3.10
PostgreSQL Common=8.4
PostgreSQL Common=8.4.1
PostgreSQL Common=8.4.2
PostgreSQL Common=8.4.3
PostgreSQL Common=9.0.0-beta1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2010-1975?

    CVE-2010-1975 has been classified as a medium severity vulnerability due to improper privilege checks in PostgreSQL.

  • How do I fix CVE-2010-1975?

    To fix CVE-2010-1975, upgrade PostgreSQL to version 7.4.29, 8.0.25, 8.1.21, 8.2.17, 8.3.11, or 8.4.4 or later.

  • Which versions of PostgreSQL are affected by CVE-2010-1975?

    Affected versions include PostgreSQL 7.4 before 7.4.29, 8.0 before 8.0.25, 8.1 before 8.1.21, and several others listed.

  • What kind of attacks can exploit CVE-2010-1975?

    CVE-2010-1975 can be exploited by remote authenticated users to remove arbitrary parameter settings, potentially affecting application behavior.

  • Are there any workarounds for CVE-2010-1975?

    While there are no specific workarounds, disabling affected user privileges may mitigate some risk until an upgrade is performed.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203