{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2004-0063 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-0063 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-0063 is a high-severity vulnerability in n/a, published on 1 Sep 2004."},"fix_prompt":"Check this codebase for CVE-2004-0063 and fix it if it is affected.\n\nWhat it is: CVE-2004-0063 is a high-severity vulnerability in n/a, published on 1 Sep 2004. \nExploitation: There is no known exploitation of CVE-2004-0063 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-2004-0063/ (Markdown: https://insights.sbomify.com/CVE-2004-0063/index.md)","id":"CVE-2004-0063","markdown":"https://insights.sbomify.com/CVE-2004-0063/index.md","name":"CVE-2004-0063","record":{"aliases":["GHSA-fvx3-52x7-x6w4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"unknown","non_default_config":false,"product_category":"nCipher payShield SPP library","requires_auth":"none","summary":"The SPP_VerifyPVV function incorrectly returns success for invalid PINs, allowing attackers to bypass authentication checks in applications using the library.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"payshield_spp_library","vendor":"ncipher"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The SPP_VerifyPVV function in nCipher payShield SPP library 1.3.12, 1.5.18 and 1.6.18 returns a Status_OK value even if the HSM returns a different status code, which could cause applications to make incorrect security-critical decisions, e.g. by accepting an invalid PIN number.","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-2004-0063","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2004"},"n_packages":0,"n_references":5,"next":{"headline":"Path traversal in n/a","id":"CVE-2004-0064"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2004-0062"},"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 SPP_VerifyPVV function incorrectly returns success for invalid PINs, allowing attackers to bypass authentication checks in applications using the library.","url":"https://insights.sbomify.com/CVE-2004-0063/"}