CVE-2020-4062

HIGHNVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under NVD CVSS v3. EPSS exploit probability: 1.4% (71st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Conjur OSS Helm Chart before 2.0.0, a recently identified critical vulnerability resulted in the installation of the Conjur Postgres database with an open port. This allows an attacker to gain full read & write access to the Conjur Postgres database, including escalating the attacker's privileges to assume full control. A malicious actor who knows the IP address and port number of the Postgres database and has access into the Kubernetes cluster where Conjur runs can gain full read & write access to the Postgres database. This enables the attacker to write a policy that allows full access to retrieve any secret. This Helm chart is a method to install Conjur OSS into a Kubernetes environment. Hence, the systems impacted are only Conjur OSS systems that were deployed using this chart. Other deployments including Docker and the CyberArk Dynamic Access Provider (DAP) are not affected. To remediate this vulnerability, clone the latest Helm Chart and follow the upgrade instructions. If you are not able to fully remediate this vulnerability immediately, you can mitigate some of the risk by making sure Conjur OSS is deployed on an isolated Kubernetes cluster or namespace. The term "isolated" refers to: - No other workloads besides Conjur OSS and its backend database are running in that Kubernetes cluster/namespace. - Kubernetes and helm access to the cluster/namespace is limited to security administrators via Role-Based Access Control (RBAC).

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

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
Severity87% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.4%
EPSS %ILE
71st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 22, 2020

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Sep 1, 2026
Patch available. Sources: github, github_commit.
github Patch Available

Conjur communication with Postgres happens over insecure connection · Advisory · cyberark/conjur-oss-helm-chart · GitHub

https://github.com/cyberark/conjur-oss-helm-chart/security/advisories/GHSA-mg2m-623j-wpxw
github_commit Patch Available

commit 2dab801ed4ab (cyberark/conjur-oss-helm-chart)

Patch available: cyberark/conjur-oss-helm-chart v2.0.0 (contains commit 2dab801ed4ab)

https://github.com/cyberark/conjur-oss-helm-chart/commit/2dab801ed4ab591c626fc6674f306fcf0d004c1e

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 26× 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 164 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-4062?
CVE-2020-4062 is a high vulnerability published on June 22, 2020. In Conjur OSS Helm Chart before 2.0.0, a recently identified critical vulnerability resulted in the installation of the Conjur Postgres database with an open port. This allows an attacker to gain full read & write access to the Conjur Postgres database, including escalating the attacker's…
When was CVE-2020-4062 disclosed?
CVE-2020-4062 was first published on June 22, 2020, 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-2020-4062 actively exploited?
CVE-2020-4062 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (71st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-4062?
CVE-2020-4062 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2020-4062?
A fix for CVE-2020-4062 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-4062

Explore →

Is Your Infrastructure Affected by CVE-2020-4062?

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

Book a Demo →Browse All CVEs