{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11876 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11876 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11876 is a high-severity vulnerability in n/a, published on 17 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11876 and fix it if it is affected.\n\nWhat it is: CVE-2020-11876 is a high-severity vulnerability in n/a, published on 17 Apr 2020. 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-2020-11876 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-2020-11876/ (Markdown: https://insights.sbomify.com/CVE-2020-11876/index.md)","id":"CVE-2020-11876","markdown":"https://insights.sbomify.com/CVE-2020-11876/index.md","name":"CVE-2020-11876","record":{"aliases":["GHSA-4f6g-8xj6-wfjv"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Zoom Client","requires_auth":"none","summary":"Zoom Client uses a hardcoded key for AES initialization in unreachable code, posing a theoretical cryptographic weakness.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"meetings","vendor":"zoom"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"airhost.exe in Zoom Client for Meetings 4.6.11 uses the SHA-256 hash of 0123425234234fsdfsdr3242 for initialization of an OpenSSL EVP AES-256 CBC context. NOTE: the vendor states that this initialization only occurs within unreachable code","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2020-11876","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2020-11877"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2020-11875"},"products":["n/a"],"published":"2020-04-17","related":[{"cvss_score":9.8,"headline":"Code injection in Zoom Client for Meetings for Windows","id":"CVE-2021-33907","kev_date_added":null,"published":"2021-09-27"},{"cvss_score":8.8,"headline":"Local Privilege Escalation in Zoom Client Installer for macOS","id":"CVE-2022-28768","kev_date_added":null,"published":"2022-11-17"},{"cvss_score":8.8,"headline":"Improper URL parsing in Zoom Clients","id":"CVE-2022-28763","kev_date_added":null,"published":"2022-10-31"},{"cvss_score":8.8,"headline":"Local Privilege Escalation in Auto Updater for Zoom Client for Meetings for macOS","id":"CVE-2022-28757","kev_date_added":null,"published":"2022-08-18"},{"cvss_score":8.8,"headline":"Local Privilege Escalation in Zoom Client for Meetings for MacOS","id":"CVE-2022-28751","kev_date_added":null,"published":"2022-08-17"},{"cvss_score":8.8,"headline":"Local Privilege Escalation in Auto Updater for Zoom Client for Meetings for macOS","id":"CVE-2022-28756","kev_date_added":null,"published":"2022-08-15"},{"cvss_score":8.1,"headline":"Improper XML Parsing in Zoom Client for Meetings","id":"CVE-2022-22784","kev_date_added":null,"published":"2022-05-18"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Zoom Client uses a hardcoded key for AES initialization in unreachable code, posing a theoretical cryptographic weakness.","url":"https://insights.sbomify.com/CVE-2020-11876/"}