{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0427 exists.","fix":"No fix has been published for CVE-2000-0427 yet. Limit exposure of the affected software until one is available.","what":"CVE-2000-0427 is a medium-severity vulnerability in n/a, published on 12 Jul 2000. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2000-0427 and fix it if it is affected.\n\nWhat it is: CVE-2000-0427 is a medium-severity vulnerability in n/a, published on 12 Jul 2000. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0427 exists.\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-2000-0427/ (Markdown: https://insights.sbomify.com/CVE-2000-0427/index.md)","id":"CVE-2000-0427","markdown":"https://insights.sbomify.com/CVE-2000-0427/index.md","name":"CVE-2000-0427","record":{"aliases":["GHSA-3hmx-5jq6-252x"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"eToken hardware device","requires_auth":"none","summary":"Attackers with physical access can reset the PIN to bypass authentication and access sensitive data on the eToken device.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"etoken","vendor":"aladdin_knowledge_systems"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The Aladdin Knowledge Systems eToken device allows attackers with physical access to the device to obtain sensitive information without knowing the PIN of the owner by resetting the PIN in the EEPROM.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2000-05-04","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2000-05-04","kind":"exploitdb","ref":"19894","stars":null,"title":"Aladdin Knowledge Systems eToken 3.3.3 - eToken PIN Extraction"}],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2000-0427","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2000"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2000-0428"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2000-0426"},"products":["n/a"],"published":"2000-07-12","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Attackers with physical access can reset the PIN to bypass authentication and access sensitive data on the eToken device.","url":"https://insights.sbomify.com/CVE-2000-0427/"}