{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-0950 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-0950 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-0950 is a high-severity vulnerability in n/a, published on 2 Feb 2002. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2001-0950 and fix it if it is affected.\n\nWhat it is: CVE-2001-0950 is a high-severity vulnerability in n/a, published on 2 Feb 2002. 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-2001-0950 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-2001-0950/ (Markdown: https://insights.sbomify.com/CVE-2001-0950/index.md)","id":"CVE-2001-0950","markdown":"https://insights.sbomify.com/CVE-2001-0950/index.md","name":"CVE-2001-0950","record":{"aliases":["GHSA-949r-2wph-553m"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Certificate Authority Server","requires_auth":"none","summary":"Insufficient randomness in token and key generation allows attackers to guess credentials or certificates, compromising the ValiCert EVA Administration Server.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"enterprise_validation_authority","vendor":"valicert"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","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-331","name":"Insufficient Entropy"}],"description":"ValiCert Enterprise Validation Authority (EVA) Administration Server 3.3 through 4.2.1 uses insufficiently random data to (1) generate session tokens for HSMs using the C rand function, or (2) generate certificates or keys using /dev/urandom instead of another source which blocks when the entropy pool is low, which could make it easier for local or remote attackers to steal tokens or certificates via brute force guessing.","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-2001-0950","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2001"},"n_packages":0,"n_references":6,"next":{"headline":"Denial of service in n/a","id":"CVE-2001-0951"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2001-0949"},"products":["n/a"],"published":"2002-02-02","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2001-0947","kev_date_added":null,"published":"2002-02-02"},{"cvss_score":7.5,"headline":"Cross-site scripting in n/a","id":"CVE-2001-0948","kev_date_added":null,"published":"2002-02-02"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2001-0949","kev_date_added":null,"published":"2002-02-02"}],"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-08","vendors":["n/a"]},"summary":"Insufficient randomness in token and key generation allows attackers to guess credentials or certificates, compromising the ValiCert EVA Administration Server.","url":"https://insights.sbomify.com/CVE-2001-0950/"}