CVE-2014-0064: Buffer Overflow

Published Feb 14, 2014
·
Updated

Multiple integer overflow flaws, leading to buffer overflows, were found in PostgreSQL. An authenticated database user could possibly use these flaws to crash the PostgreSQL server or execute arbitrary code.

Acknowledgements:

Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Heikki Linnakangas and Noah Misch as the original reporters.

Other sources

Multiple integer overflows in the pathin and other unspecified functions in PostgreSQL before 8.4.20, 9.0.x before 9.0.16, 9.1.x before 9.1.12, 9.2.x before 9.2.7, and 9.3.x before 9.3.3 allow remote authenticated users to have unspecified impact and attack vectors, which trigger a buffer overflow. NOTE: this identifier has been SPLIT due to different affected versions; use CVE-2014-2669 for the hstore vector.

MITRE

Affected Software

57 affected components
PostgreSQL postgresql<=8.4.19
PostgreSQL postgresql=8.4.1
PostgreSQL postgresql=8.4.2
PostgreSQL postgresql=8.4.3
PostgreSQL postgresql=8.4.4
PostgreSQL postgresql=8.4.5
PostgreSQL postgresql=8.4.6
PostgreSQL postgresql=8.4.7
PostgreSQL postgresql=8.4.8
PostgreSQL postgresql=8.4.9
PostgreSQL postgresql=8.4.10
PostgreSQL postgresql=8.4.11
PostgreSQL postgresql=8.4.12
PostgreSQL postgresql=8.4.13
PostgreSQL postgresql=8.4.14
PostgreSQL postgresql=8.4.15
PostgreSQL postgresql=8.4.16
PostgreSQL postgresql=8.4.17
PostgreSQL postgresql=8.4.18
PostgreSQL postgresql=9.0
PostgreSQL postgresql=9.0.1
PostgreSQL postgresql=9.0.2
PostgreSQL postgresql=9.0.3
PostgreSQL postgresql=9.0.4
PostgreSQL postgresql=9.0.5
PostgreSQL postgresql=9.0.6
PostgreSQL postgresql=9.0.7
PostgreSQL postgresql=9.0.8
PostgreSQL postgresql=9.0.9
PostgreSQL postgresql=9.0.10
PostgreSQL postgresql=9.0.11
PostgreSQL postgresql=9.0.12
PostgreSQL postgresql=9.0.13
PostgreSQL postgresql=9.0.14
PostgreSQL postgresql=9.0.15
PostgreSQL postgresql=9.1
PostgreSQL postgresql=9.1.1
PostgreSQL postgresql=9.1.2
PostgreSQL postgresql=9.1.3
PostgreSQL postgresql=9.1.4
PostgreSQL postgresql=9.1.5
PostgreSQL postgresql=9.1.6
PostgreSQL postgresql=9.1.7
PostgreSQL postgresql=9.1.8
PostgreSQL postgresql=9.1.9
PostgreSQL postgresql=9.1.10
PostgreSQL postgresql=9.1.11
PostgreSQL postgresql=9.2
PostgreSQL postgresql=9.2.1
PostgreSQL postgresql=9.2.2
PostgreSQL postgresql=9.2.3
PostgreSQL postgresql=9.2.4
PostgreSQL postgresql=9.2.5
PostgreSQL postgresql=9.2.6
PostgreSQL postgresql=9.3
PostgreSQL postgresql=9.3.1
PostgreSQL postgresql=9.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 8.4.20
  2. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 9.0.16
  3. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 9.1.12
  4. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 9.2.7
  5. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 9.3.3

Event History

Feb 14, 2014
Data Sourced
via Red Hat·07:31 AM
DescriptionSeverityAffected Software
Mar 28, 2014
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Mar 31, 2014
Data Sourced
via NVD·02:58 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2014-0064?

CVE-2014-0064 is classified as a high severity vulnerability due to the potential for remote code execution and denial of service.

2

How do I fix CVE-2014-0064?

To remediate CVE-2014-0064, upgrade PostgreSQL to a version that is not affected, specifically above 9.3.4.

3

What systems are affected by CVE-2014-0064?

CVE-2014-0064 affects PostgreSQL versions 8.4.x through 9.3.3.

4

Can CVE-2014-0064 be exploited remotely?

Yes, CVE-2014-0064 can be exploited by an authenticated user to cause crashes or execute arbitrary code which might lead to broader system access.

5

Is user authentication sufficient to mitigate CVE-2014-0064?

No, simply having user authentication does not mitigate the risks associated with CVE-2014-0064, as an authenticated user can 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