CVE-2010-0733: Integer Overflow

Published Dec 11, 2009
·
Updated

An integer overflow flaw was found in the way postgresql used to calculate size for the hashtable for joined relations. An attacker could formulate a specially-crafted sql query, which once processed would lead to denial of service (postgresql daemon crash).

Upstream bug report: -------------------- [1] http://archives.postgresql.org/pgsql-bugs/2009-10/msg00277.php

References: ----------- [2] http://archives.postgresql.org/pgsql-bugs/2009-10/msg00287.php [3] http://archives.postgresql.org/pgsql-bugs/2009-10/msg00310.php [4] http://archives.postgresql.org/pgsql-bugs/2009-10/msg00289.php

Upstream patch: --------------- git clone git://git.postgresql.org/git/postgresql.git cd postgresql && git show 64b057e6823655fb6c5d1f24a28f236b94dd6c54

Credit: ------- Bernt Marius Johnsen

Other sources

Integer overflow in src/backend/executor/nodeHash.c in PostgreSQL 8.4.1 and earlier, and 8.5 through 8.5alpha2, allows remote authenticated users to cause a denial of service (daemon crash) via a SELECT statement with many LEFT JOIN clauses, related to certain hashtable size calculations.

Red Hat

Affected Software

85 affected componentsFixes available
redhat/postgresql<0:7.4.29-1.el4_8.1
0:7.4.29-1.el4_8.1
redhat/postgresql<0:8.1.21-1.el5_5.1
0:8.1.21-1.el5_5.1
PostgreSQL postgresql=8.1.10
PostgreSQL postgresql=8.1.6
PostgreSQL postgresql=8.2.9
PostgreSQL postgresql=8.0.7
PostgreSQL postgresql=8.0.2
PostgreSQL postgresql=8.1.15
PostgreSQL postgresql=8.1.7
PostgreSQL postgresql=8.3.6
PostgreSQL postgresql=8.2.10
PostgreSQL postgresql=8.0.22
PostgreSQL postgresql=8.2.15
PostgreSQL postgresql=8.2.4
PostgreSQL postgresql=8.0.17
PostgreSQL postgresql=8.0.10
PostgreSQL postgresql=8.1.20
PostgreSQL postgresql=8.1
PostgreSQL postgresql=8.1.19
PostgreSQL postgresql=8.2.11
PostgreSQL postgresql=8.1.13
PostgreSQL postgresql=8.0.12
PostgreSQL postgresql=8.2.12
PostgreSQL postgresql=8.0.9
PostgreSQL postgresql=8.0.15
PostgreSQL postgresql=8.2.2
PostgreSQL postgresql=8.3.3
PostgreSQL postgresql=8.0.0
PostgreSQL postgresql=8.1.0
PostgreSQL postgresql=8.1.3
PostgreSQL postgresql=8.3.2
PostgreSQL postgresql=8.5
PostgreSQL postgresql=8.0.18
PostgreSQL postgresql=8.2.5
PostgreSQL postgresql=8.0.3
PostgreSQL postgresql=8.0.24
PostgreSQL postgresql=8.1.9
PostgreSQL postgresql=8.4
PostgreSQL postgresql<=8.4.1
PostgreSQL postgresql=8.2.1
PostgreSQL postgresql=8.3.1
PostgreSQL postgresql=8.5-alpha2
PostgreSQL postgresql=8.1.14
PostgreSQL postgresql=8.3.5
PostgreSQL postgresql=8.0.20
PostgreSQL postgresql=8.3.8
PostgreSQL postgresql=8.0.8
PostgreSQL postgresql=8.2.7
PostgreSQL postgresql=8.0.6
PostgreSQL postgresql=8.1.11
PostgreSQL postgresql=8.2.6
PostgreSQL postgresql=8.0.16
PostgreSQL postgresql=8.3.7
PostgreSQL postgresql=8.1.17
PostgreSQL postgresql=8.0.13
PostgreSQL postgresql=8.3.10
PostgreSQL postgresql=8.1.18
PostgreSQL postgresql=8.3
PostgreSQL postgresql=8.1.4
PostgreSQL postgresql=8.0.1
PostgreSQL postgresql=8.1.8
PostgreSQL postgresql=8.3.4
PostgreSQL postgresql=8.0.19
PostgreSQL postgresql=8.1.1
PostgreSQL postgresql=8.1.12
PostgreSQL postgresql=8.1.5
PostgreSQL postgresql=8.0.21
PostgreSQL postgresql=8.1.16
PostgreSQL postgresql=8.2.3
PostgreSQL postgresql=8.0.23
PostgreSQL postgresql=8.5-alpha1
PostgreSQL postgresql=8.3.9
PostgreSQL postgresql=8.2.16
PostgreSQL postgresql=8.0.4
PostgreSQL postgresql=8.0.5
PostgreSQL postgresql=8.0.14
PostgreSQL postgresql=8.2.8
PostgreSQL postgresql=8.2.13
PostgreSQL postgresql=8.2
PostgreSQL postgresql=8.0.11
PostgreSQL postgresql=8.0.317
PostgreSQL postgresql=8.0
PostgreSQL postgresql=8.2.14
PostgreSQL postgresql=8.1.2
PostgreSQL postgresql=8.0.24

Event History

Dec 11, 2009
Data Sourced
via Red Hat·01:30 PM
DescriptionSeverityAffected Software
Dec 14, 2009
CVE Published
via Red Hat·12:00 AM
Mar 19, 2010
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
Data Sourced
via NVD·07:30 PM
RemedyDescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2010-0733?

CVE-2010-0733 has a medium severity level as it allows remote authenticated users to cause denial of service through specific SQL queries.

2

How do I fix CVE-2010-0733?

To fix CVE-2010-0733, upgrade to PostgreSQL version 8.4.2 or later, as these versions include the necessary patches.

3

Which PostgreSQL versions are affected by CVE-2010-0733?

CVE-2010-0733 affects PostgreSQL versions 8.4.1 and earlier, as well as 8.5 through 8.5alpha2.

4

What type of vulnerability is CVE-2010-0733?

CVE-2010-0733 is classified as an integer overflow vulnerability leading to a denial of service.

5

Can CVE-2010-0733 be exploited without authentication?

No, CVE-2010-0733 requires remote authenticated users to exploit the vulnerability.

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