CVE-2015-3167

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

contrib/pgcrypto in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 uses different error responses when an incorrect key is used, which makes it easier for attackers to obtain the key via a brute force attack.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation4% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
4%
EPSS %ILE
90%
KEV
Not listed

Published

November 20, 2019

Last Modified

November 21, 2024

References (18)

Vendor Advisories for CVE-2015-3167(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-9.1 (9.1.16-0ubuntu0.12.04) @ precise2026-05-27ubuntu
redhatrh-postgresql94-postgresql-0:9.4.4-1.el72015-06-29redhat
redhatpostgresql-0:9.2.13-1.ael7b_12015-06-29redhat
redhatpostgresql92-postgresql-0:9.2.13-1.el72015-06-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:8(2)
PackageVulnerable rangeFixed inDependents
postgresql-9.19.1.15-0+deb8u19.1.16-0+deb8u1—
postgresql-9.49.4.1-19.4.2-0+deb8u1—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
postgresql-8.48.4.10-0squeeze1 ... 8.4.9-1 (45 versions)8.4.22lts2-0+deb6u2—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
postgresql-9.19.1.10-0wheezy1 ... 9.1.9-5 (21 versions)9.1.16-0+deb7u1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 2× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-09-19 15:35 UTCEPSS rescore
  2. 2026-09-18 19:22 UTCEPSS rescore
  3. 2026-09-17 19:21 UTCEPSS rescore
  4. 2026-09-15 03:05 UTCEPSS rescore
  5. 2026-09-12 14:55 UTCEPSS rescore
  6. 2026-09-11 09:31 UTCEPSS rescore
  7. 2026-09-10 09:26 UTCEPSS rescore
  8. 2026-09-07 15:56 UTCEPSS rescore
  9. 2026-09-06 13:42 UTCEPSS rescore
  10. 2026-09-05 15:23 UTCEPSS rescore
  11. 2026-09-04 13:55 UTCEPSS rescore
  12. 2026-09-02 14:07 UTCEPSS rescore
  13. 2026-09-01 03:31 UTCEPSS rescore
  14. 2026-08-30 19:12 UTCEPSS rescore
  15. 2026-08-27 14:20 UTCEPSS rescore
  16. 2026-08-26 14:41 UTCEPSS rescore
  17. 2026-08-25 13:44 UTCEPSS rescore
  18. 2026-08-21 23:44 UTCEPSS rescore
  19. 2026-08-20 22:50 UTCEPSS rescore
  20. 2026-08-19 16:59 UTCEPSS rescore
  21. 2026-08-18 13:43 UTCEPSS rescore
  22. 2026-08-16 14:51 UTCEPSS rescore
  23. 2026-08-16 02:09 UTCEPSS rescore
  24. 2026-08-15 01:25 UTCEPSS rescore
  25. 2026-08-12 13:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-09 13:42 UTCEPSS rescore
  2. 2026-08-08 16:31 UTCEPSS rescore
  3. 2026-08-07 16:22 UTCEPSS rescore
  4. 2026-08-06 13:42 UTCEPSS rescore
  5. 2026-08-05 19:12 UTCEPSS rescore
  6. 2026-08-04 15:04 UTCEPSS rescore
  7. 2026-08-02 02:22 UTCEPSS rescore
  8. 2026-08-01 04:11 UTCEPSS rescore
  9. 2026-07-30 16:23 UTCEPSS rescore
  10. 2026-07-30 01:26 UTCEPSS rescore
  11. 2026-07-28 15:31 UTCEPSS rescore
  12. 2026-07-26 14:50 UTCEPSS rescore
  13. 2026-07-24 14:13 UTCEPSS rescore
  14. 2026-07-23 14:14 UTCEPSS rescore
  15. 2026-07-23 01:17 UTCEG score recompute
  16. 2026-07-23 00:19 UTCEG score recompute
  17. 2026-07-22 21:58 UTCEG score recompute
  18. 2026-07-22 14:04 UTCEPSS rescore
  19. 2026-07-21 15:21 UTCEPSS rescore
  20. 2026-07-21 15:21 UTCEPSS rescore
  21. 2026-07-20 17:03 UTCEPSS rescore
  22. 2026-07-19 14:27 UTCEPSS rescore
  23. 2026-07-19 14:27 UTCEPSS rescore
  24. 2026-07-19 02:26 UTCEPSS rescore
  25. 2026-07-19 02:26 UTCEPSS rescore
  26. 2026-07-18 10:00 UTCEPSS rescore
  27. 2026-07-16 16:59 UTCEPSS rescore
  28. 2026-07-16 16:59 UTCEPSS rescore
  29. 2026-07-15 16:54 UTCEPSS rescore
  30. 2026-07-15 16:54 UTCEPSS rescore
  31. 2026-07-15 01:56 UTCEPSS rescore
  32. 2026-07-13 22:26 UTCEPSS rescore
  33. 2026-07-12 05:42 UTCEPSS rescore
  34. 2026-07-11 08:23 UTCEPSS rescore
  35. 2026-07-09 19:05 UTCEPSS rescore
  36. 2026-07-08 15:10 UTCEPSS rescore
  37. 2026-07-07 13:42 UTCEPSS rescore
  38. 2026-07-06 16:24 UTCEPSS rescore
  39. 2026-07-06 02:20 UTCEPSS rescore
  40. 2026-07-05 02:26 UTCEPSS rescore
  41. 2026-07-04 06:27 UTCEPSS rescore
  42. 2026-07-02 15:21 UTCEPSS rescore
  43. 2026-07-01 15:02 UTCEPSS rescore
  44. 2026-07-01 15:02 UTCEPSS rescore
  45. 2026-06-30 23:19 UTCEPSS rescore
  46. 2026-06-30 23:19 UTCEPSS rescore
  47. 2026-06-29 14:03 UTCEPSS rescore
  48. 2026-06-28 14:03 UTCEPSS rescore
  49. 2026-06-28 04:53 UTCEPSS rescore
  50. 2026-06-27 03:05 UTCEPSS rescore
  51. 2026-06-25 13:47 UTCEPSS rescore
  52. 2026-06-25 13:47 UTCEPSS rescore
  53. 2026-06-24 14:02 UTCEPSS rescore
  54. 2026-06-24 14:02 UTCEPSS rescore
  55. 2026-06-23 21:30 UTCEPSS rescore
  56. 2026-06-22 14:23 UTCEPSS rescore
  57. 2026-06-22 14:22 UTCEPSS rescore
  58. 2026-06-21 14:54 UTCEPSS rescore
  59. 2026-06-21 01:57 UTCEPSS rescore
  60. 2026-06-21 01:57 UTCEPSS rescore
  61. 2026-06-19 19:23 UTCEPSS rescore
  62. 2026-06-19 19:23 UTCEPSS rescore
  63. 2026-06-18 17:50 UTCEPSS rescore
  64. 2026-06-18 17:49 UTCEPSS rescore
  65. 2026-06-17 17:49 UTCEPSS rescore
  66. 2026-06-16 17:50 UTCEPSS rescore
  67. 2026-06-16 17:49 UTCEPSS rescore
  68. 2026-06-15 17:45 UTCEPSS rescore
  69. 2026-06-14 23:14 UTCEPSS rescore
  70. 2026-06-13 22:57 UTCEPSS rescore
  71. 2026-06-12 23:09 UTCEPSS rescore
  72. 2026-06-11 13:57 UTCEPSS rescore
  73. 2026-06-10 22:15 UTCEPSS rescore
  74. 2026-06-08 14:14 UTCEPSS rescore
  75. 2026-06-07 15:22 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2015-3167?
CVE-2015-3167 is a high vulnerability published on November 20, 2019. contrib/pgcrypto in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 uses different error responses when an incorrect key is used, which makes it easier for attackers to obtain the key via a brute force attack.
When was CVE-2015-3167 disclosed?
CVE-2015-3167 was first published in the National Vulnerability Database on November 20, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-3167 actively exploited?
CVE-2015-3167 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4% probability of exploitation in the next 30 days, which ranks it in the top 9.6% of all scored CVEs.
What is the CVSS score of CVE-2015-3167?
CVE-2015-3167 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2015-3167?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-3167, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-3167

Explore →

Is Your Infrastructure Affected by CVE-2015-3167?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs