{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1446 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1446 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1446 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-1446 and fix it if it is affected.\n\nWhat it is: CVE-2002-1446 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. 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-2002-1446 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-2002-1446/ (Markdown: https://insights.sbomify.com/CVE-2002-1446/index.md)","id":"CVE-2002-1446","markdown":"https://insights.sbomify.com/CVE-2002-1446/index.md","name":"CVE-2002-1446","record":{"aliases":["GHSA-cxmh-cjjc-hchp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PKCS#11 cryptographic library","requires_auth":"none","summary":"The nCipher PKCS#11 library incorrectly reports valid signatures for invalid ones, allowing remote attackers to forge messages and bypass integrity checks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pkcs_11_library","vendor":"ncipher"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"The error checking routine used for the C_Verify call on a symmetric verification key in the nCipher PKCS#11 library 1.2.0 and later returns the CKR_OK status even when it detects an invalid signature, which could allow remote attackers to modify or forge messages.","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":"Security feature bypass in n/a","id":"CVE-2002-1446","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2002"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2002-1447"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2002-1445"},"products":["n/a"],"published":"2004-09-01","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"The nCipher PKCS#11 library incorrectly reports valid signatures for invalid ones, allowing remote attackers to forge messages and bypass integrity checks.","url":"https://insights.sbomify.com/CVE-2002-1446/"}