CVE-2020-4062

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).

• CWE-284

• https://github.com/cyberark/conjur-oss-helm-chart/commit/2dab801ed4ab591c626fc6674f306fcf0d004c1ePatch, Third Party Advisory
• https://github.com/cyberark/conjur-oss-helm-chart/security/advisories/GHSA-mg2m-623j-wpxwThird Party Advisory
• https://github.com/cyberark/conjur-oss-helm-chart/commit/2dab801ed4ab591c626fc6674f306fcf0d004c1ePatch, Third Party Advisory
• https://github.com/cyberark/conjur-oss-helm-chart/security/advisories/GHSA-mg2m-623j-wpxwThird Party Advisory

Published

Jun 22, 2020

Last Modified

Jun 17, 2026

Status

Modified

• Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2020-4052In Wiki.js before 2.4.107, there is a stored cross-site scri…6.1
• CVE-2020-4053In Helm greater than or equal to 3.0.0 and less than 3.2.4, …6.8
• CVE-2020-4054In Sanitize (RubyGem sanitize) greater than or equal to 3.0.…7.3
• CVE-2020-4059In mversion before 2.0.0, there is a command injection vulne…7.3
• CVE-2020-4060In LoRa Basics Station before 2.0.4, there is a Use After Fr…5
• CVE-2020-4061In October from version 1.0.319 and before version 1.0.467, …5.4
• CVE-2020-4066In Limdu before 0.95, the trainBatch function has a command …7.2
• CVE-2020-4067In coturn before version 4.5.1.3, there is an issue whereby …7.5
• CVE-2020-4068In APNSwift 1.0.0, calling APNSwiftSigner.sign(digest:) is l…9.8
• CVE-2020-4070In CSS Validator less than or equal to commit 54d68a1, there…5.4
• CVE-2020-4071In django-basic-auth-ip-whitelist before 0.3.4, a potential …2.4
• CVE-2020-4072In generator-jhipster-kotlin version 1.6.0 log entries are c…5.3