{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6829 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-6829 is a high-severity vulnerability in n/a, published on 7 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-6829 and fix it if it is affected.\n\nWhat it is: CVE-2018-6829 is a high-severity vulnerability in n/a, published on 7 Feb 2018. 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-2018-6829 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-6829/ (Markdown: https://insights.sbomify.com/CVE-2018-6829/index.md)","id":"CVE-2018-6829","markdown":"https://insights.sbomify.com/CVE-2018-6829/index.md","name":"CVE-2018-6829","record":{"aliases":["DEBIAN-CVE-2018-6829","GHSA-wcf7-2f92-j5mv","ROOT-OS-DEBIAN-12-CVE-2018-6829"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Libgcrypt crypto library","requires_auth":"none","summary":"Attackers can obtain sensitive information from ciphertext due to improper ElGamal encoding in Libgcrypt, violating semantic security assumptions.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libgcrypt","vendor":"gnupg"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Weak cryptography in n/a","id":"CVE-2018-6829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Path traversal in n/a","id":"CVE-2018-6830"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2018-6827"},"products":["n/a"],"published":"2018-02-07","related":[{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-3345","kev_date_added":null,"published":"2021-01-29"},{"cvss_score":6.7,"headline":"Memory corruption in Libgcrypt","id":"CVE-2026-41989","kev_date_added":null,"published":"2026-04-23"},{"cvss_score":5.9,"headline":"Weak cryptography in n/a","id":"CVE-2021-40528","kev_date_added":null,"published":"2021-09-06"},{"cvss_score":5.9,"headline":"Information disclosure in n/a","id":"CVE-2019-12904","kev_date_added":null,"published":"2019-06-19"},{"cvss_score":5.9,"headline":"Information disclosure in n/a","id":"CVE-2017-9526","kev_date_added":null,"published":"2017-06-11"},{"cvss_score":4,"headline":"Memory corruption in Libgcrypt","id":"CVE-2026-41990","kev_date_added":null,"published":"2026-04-23"}],"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-05","vendors":["n/a"]},"summary":"Attackers can obtain sensitive information from ciphertext due to improper ElGamal encoding in Libgcrypt, violating semantic security assumptions.","url":"https://insights.sbomify.com/CVE-2018-6829/"}