CVE-2010-0733

Severity

35%

Complexity

68%

Confidentiality

48%

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.

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.

CVSS 2.0 Base Score 3.5. CVSS Attack Vector: network. CVSS Attack Complexity: medium. CVSS Vector: (AV:N/AC:M/Au:S/C:N/I:N/A:P).

Overview

First reported 14 years ago

2010-03-19 19:30:00

Last updated 7 years ago

2017-09-19 01:30:00

Affected Software

PostgreSQL 8.0

8.0

PostgreSQL PostgreSQL 8.0.1

8.0.1

PostgreSQL PostgreSQL 8.0.2

8.0.2

PostgreSQL PostgreSQL 8.0.3

8.0.3

PostgreSQL PostgreSQL 8.0.4

8.0.4

PostgreSQL PostgreSQL 8.0.5

8.0.5

PostgreSQL PostgreSQL 8.0.6

8.0.6

PostgreSQL PostgreSQL 8.0.7

8.0.7

PostgreSQL PostgreSQL 8.0.8

8.0.8

PostgreSQL PostgreSQL 8.0.9

8.0.9

PostgreSQL PostgreSQL 8.0.10

8.0.10

PostgreSQL PostgreSQL 8.0.11

8.0.11

PostgreSQL PostgreSQL 8.0.12

8.0.12

PostgreSQL PostgreSQL 8.0.13

8.0.13

PostgreSQL PostgreSQL 8.0.14

8.0.14

PostgreSQL PostgreSQL 8.0.15

8.0.15

PostgreSQL PostgreSQL 8.0.16

8.0.16

PostgreSQL PostgreSQL 8.0.17

8.0.17

PostgreSQL PostgreSQL 8.0.18

8.0.18

PostgreSQL PostgreSQL 8.0.19

8.0.19

PostgreSQL PostgreSQL 8.0.20

8.0.20

PostgreSQL PostgreSQL 8.0.21

8.0.21

PostgreSQL PostgreSQL 8.0.22

8.0.22

PostgreSQL PostgreSQL 8.0.23

8.0.23

PostgreSQL PostgreSQL 8.0.24

8.0.24

PostgreSQL 8.1

8.1

PostgreSQL 8.1.0

8.1.0

PostgreSQL 8.1.1

8.1.1

PostgreSQL 8.1.2

8.1.2

PostgreSQL 8.1.3

8.1.3

PostgreSQL 8.1.4

8.1.4

PostgreSQL 8.1.5

8.1.5

PostgreSQL 8.1.6

8.1.6

PostgreSQL 8.1.7

8.1.7

PostgreSQL 8.1.8

8.1.8

PostgreSQL 8.1.9

8.1.9

PostgreSQL 8.1.10

8.1.10

PostgreSQL 8.1.11

8.1.11

PostgreSQL 8.1.12

8.1.12

PostgreSQL 8.1.13

8.1.13

PostgreSQL 8.1.14

8.1.14

PostgreSQL 8.1.15

8.1.15

PostgreSQL 8.1.16

8.1.16

PostgreSQL 8.1.17

8.1.17

PostgreSQL 8.1.18

8.1.18

PostgreSQL 8.1.19

8.1.19

PostgreSQL 8.1.20

8.1.20

PostgreSQL 8.2

8.2

PostgreSQL 8.2.1

8.2.1

PostgreSQL 8.2.2

8.2.2

PostgreSQL 8.2.3

8.2.3

PostgreSQL 8.2.4

8.2.4

PostgreSQL 8.2.5

8.2.5

PostgreSQL 8.2.6

8.2.6

PostgreSQL 8.2.7

8.2.7

PostgreSQL 8.2.8

8.2.8

PostgreSQL 8.2.9

8.2.9

PostgreSQL 8.2.10

8.2.10

PostgreSQL 8.2.11

8.2.11

PostgreSQL 8.2.12

8.2.12

PostgreSQL 8.2.13

8.2.13

PostgreSQL 8.2.14

8.2.14

PostgreSQL 8.2.15

8.2.15

PostgreSQL 8.2.16

8.2.16

PostgreSQL 8.3

8.3

PostgreSQL 8.3.1

8.3.1

PostgreSQL 8.3.2

8.3.2

PostgreSQL 8.3.3

8.3.3

PostgreSQL 8.3.4

8.3.4

PostgreSQL 8.3.5

8.3.5

PostgreSQL 8.3.6

8.3.6

PostgreSQL 8.3.7

8.3.7

PostgreSQL 8.3.8

8.3.8

PostgreSQL 8.3.9

8.3.9

PostgreSQL 8.3.10

8.3.10

PostgreSQL 8.4

8.4

PostgreSQL

References

[pgsql-bugs] 20091028 BUG #5145: Complex query with lots of LEFT JOIN causes segfault

[pgsql-bugs] 20091029 Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault

[pgsql-bugs] 20091029 Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault

[pgsql-bugs] 20091030 Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault

http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=64b057e6823655fb6c5d1f24a28f236b94dd6c54

Patch

SUSE-SR:2010:014

39820

[oss-security] 20100309 CVE Request: postgresql integer overflow in hash table size calculation

[oss-security] 20100316 Re: CVE Request: postgresql integer overflow in hash table size calculation

RHSA-2010:0427

RHSA-2010:0428

RHSA-2010:0429

38619

ADV-2010-1197

https://bugzilla.redhat.com/show_bug.cgi?id=546621

Patch

oval:org.mitre.oval:def:10691

Stay updated

ExploitPedia is constantly evolving. Sign up to receive a notification when we release additional functionality.

Get in touch

If you'd like to report a bug or have any suggestions for improvements then please do get in touch with us using this form. We will get back to you as soon as we can.