Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-0243

postgresql: buffer overflow flaws in contrib/pgcrypto

Overview

Published
27 Jan 2020
Modified
21 Nov 2024
High CVE
0 Registry packages
31 OS packages
3 Linux distributions
Yes Fix available

Description

Multiple buffer overflows in contrib/pgcrypto in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allow remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors.

Source: OX vulnerability database

Severity

8.8 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-120

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 4 fixes

Oracle Linux 1 release · 1 package

fixed 1
postgresql
Oracle Linux fixes for CVE-2015-0243
ReleasePackageFixed in
7 postgresql +10 9.2.10-2.el7_1

Red Hat 1 release · 2 packages

fixed 2
postgresql92-postgresql postgresql
Red Hat fixes for CVE-2015-0243
ReleasePackageFixed inAdvisory
7 postgresql92-postgresql +10 0:9.2.10-1.el7 RHSA-2015:0699
7 postgresql +10 0:9.2.10-2.el7_1 RHSA-2015:0750

openSUSE 1 release · 1 package

fixed 1
postgresql93
openSUSE fixes for CVE-2015-0243
ReleasePackageFixed inAdvisory
Tumbleweed postgresql93 +8 9.3.15-1.1 openSUSE-SU-2024:10256-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.