{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-3818 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3818 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3818 is a low-severity vulnerability in Redhat Openshift Container Platform, published on 5 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-3818 and fix it if it is affected.\n\nWhat it is: CVE-2019-3818 is a low-severity vulnerability in Redhat Openshift Container Platform, published on 5 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-3818 in the wild and no public exploit code.\n\nAffected product: Redhat Openshift Container Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-3818/ (Markdown: https://insights.sbomify.com/CVE-2019-3818/index.md)","id":"CVE-2019-3818","markdown":"https://insights.sbomify.com/CVE-2019-3818/index.md","name":"CVE-2019-3818","record":{"aliases":["GHSA-69hf-98q7-wjq8"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes RBAC proxy","requires_auth":"none","summary":"An attacker can break TLS encryption in kube-rbac-proxy due to insecure cipher and protocol support, potentially exposing sensitive traffic.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"kube-rbac-proxy","vendor":"kube-rbac-proxy_project"},{"product":"openshift_container_platform","vendor":"redhat"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"The kube-rbac-proxy container before version 0.4.1 as used in Red Hat OpenShift Container Platform does not honor TLS configurations, allowing for use of insecure ciphers and TLS 1.0. An attacker could target traffic sent over a TLS connection with a weak configuration and potentially break the encryption.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Weak cryptography in kube-rbac-proxy","id":"CVE-2019-3818","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:openshift_container_platform","products":["redhat:openshift_container_platform"],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in kernel:","id":"CVE-2019-3819"},"packages":[],"prev":{"headline":"Use after free in libcomps","id":"CVE-2019-3817"},"products":["kube-rbac-proxy"],"published":"2019-02-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["[UNKNOWN]"]},"summary":"An attacker can break TLS encryption in kube-rbac-proxy due to insecure cipher and protocol support, potentially exposing sensitive traffic.","url":"https://insights.sbomify.com/CVE-2019-3818/"}