CVE-2020-4062

{"id": "CVE-2020-4062", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 7.7, "accessVector": "ADJACENT_NETWORK", "vectorString": "AV:A/AC:L/Au:S/C:C/I:C/A:C", "authentication": "SINGLE", "integrityImpact": "COMPLETE", "accessComplexity": "LOW", "availabilityImpact": "COMPLETE", "confidentialityImpact": "COMPLETE"}, "acInsufInfo": false, "impactScore": 10.0, "baseSeverity": "HIGH", "obtainAllPrivilege": false, "exploitabilityScore": 5.1, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 9.0, "attackVector": "ADJACENT_NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 2.3}, {"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 8.7, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.8, "exploitabilityScore": 2.3}]}, "published": "2020-06-22T16:15:11.650", "references": [{"url": "https://github.com/cyberark/conjur-oss-helm-chart/commit/2dab801ed4ab591c626fc6674f306fcf0d004c1e", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/cyberark/conjur-oss-helm-chart/security/advisories/GHSA-mg2m-623j-wpxw", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-Other"}]}, {"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-284"}]}], "descriptions": [{"lang": "en", "value": "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)."}, {"lang": "es", "value": "En Conjur OSS Helm Chart versiones anteriores a 2.0.0, una vulnerabilidad cr\u00edtica recientemente identificada result\u00f3 en la instalaci\u00f3n de la base de datos de Conjur Postgres con un puerto abierto. Esto permite a un atacante conseguir acceso completo de lectura y escritura a la base de datos de Conjur Postgres, incluyendo el aumento de los privilegios del atacante para asumir el control total. Un actor malicioso que conoce la direcci\u00f3n IP y el n\u00famero de puerto de la base de datos de Postgres y tiene acceso al cl\u00faster de Kubernetes donde se ejecuta Conjur puede conseguir acceso completo de lectura y escritura a la base de datos de Postgres. Esto permite al atacante escribir una pol\u00edtica que permita el acceso total para recuperar cualquier secreto. Este Helm chart es un m\u00e9todo para instalar Conjur OSS en un entorno Kubernetes. Por lo tanto, los sistemas afectados son solo sistemas Conjur OSS que se implementaron usando este gr\u00e1fico. Otras implementaciones, incluidas Docker y CyberArk Dynamic Access Provider (DAP), no est\u00e1n afectadas. Para remediar esta vulnerabilidad, clone el \u00faltimo Helm Chart y siga las instrucciones de actualizaci\u00f3n. Si no es capaz de remediar completamente esta vulnerabilidad de inmediato, puede mitigar algunos de los riesgos asegur\u00e1ndose de que Conjur OSS se implemente en un cl\u00faster o espacio de nombres Kubernetes aislado. El t\u00e9rmino \"isolated\" se refiere a: - No se est\u00e1n ejecutando otras cargas de trabajo adem\u00e1s de Conjur OSS y su base de datos de backend en ese cl\u00faster y espacio de nombres de Kubernetes. - El acceso de Kubernetes y helm al cl\u00faster y espacio de nombres est\u00e1 limitado a los administradores de seguridad por medio del Control de Acceso basado en Roles (RBAC)"}], "lastModified": "2022-09-20T19:20:09.213", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:cyberark:conjur_oss_helm_chart:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "885557BF-E079-4340-8530-E0A192421AF2", "versionEndExcluding": "2.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}