{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43398 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43398 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43398 is a medium-severity vulnerability in n/a, published on 4 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43398 and fix it if it is affected.\n\nWhat it is: CVE-2021-43398 is a medium-severity vulnerability in n/a, published on 4 Nov 2021. 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-2021-43398 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-2021-43398/ (Markdown: https://insights.sbomify.com/CVE-2021-43398/index.md)","id":"CVE-2021-43398","markdown":"https://insights.sbomify.com/CVE-2021-43398/index.md","name":"CVE-2021-43398","record":{"aliases":["GHSA-86rq-fj99-chhj"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Crypto++ library","requires_auth":"none","summary":"Timing leakage in Crypto++ may disclose private key length, though the vendor disputes this as intentional behavior.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"crypto\\+\\+","vendor":"cryptopp"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Crypto++ (aka Cryptopp) 8.6.0 and earlier contains a timing leakage in MakePublicKey(). There is a clear correlation between execution time and private key length, which may cause disclosure of the length information of the private key. This might allow attackers to conduct timing attacks. NOTE: this report is disputed by the vendor and multiple third parties. The execution-time differences are intentional. A user may make a choice of a longer key as a tradeoff between strength and performance. In making this choice, the amount of information leaked to an adversary is of infinitesimal value","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":"Information disclosure in n/a","id":"CVE-2021-43398","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2021-43399"},"packages":[],"prev":{"headline":"LiquidFiles before 3.6.3 allows remote attackers to elevate their privileges from Admin (or User Admin) to Sysadmin.","id":"CVE-2021-43397"},"products":["n/a"],"published":"2021-11-04","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2023-50980","kev_date_added":null,"published":"2023-12-18"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2023-50981","kev_date_added":null,"published":"2023-12-18"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2022-48570","kev_date_added":null,"published":"2023-08-22"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2016-3995","kev_date_added":null,"published":"2017-02-13"},{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2016-7544","kev_date_added":null,"published":"2017-01-30"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2016-9939","kev_date_added":null,"published":"2017-01-30"},{"cvss_score":5.9,"headline":"Information disclosure in n/a","id":"CVE-2023-50979","kev_date_added":null,"published":"2023-12-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Timing leakage in Crypto++ may disclose private key length, though the vendor disputes this as intentional behavior.","url":"https://insights.sbomify.com/CVE-2021-43398/"}