{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-1568 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-1568 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1568 is a medium-severity vulnerability in n/a, published on 14 Jul 2005. 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-1568 and fix it if it is affected.\n\nWhat it is: CVE-2001-1568 is a medium-severity vulnerability in n/a, published on 14 Jul 2005. 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-1568 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-1568/ (Markdown: https://insights.sbomify.com/CVE-2001-1568/index.md)","id":"CVE-2001-1568","markdown":"https://insights.sbomify.com/CVE-2001-1568/index.md","name":"CVE-2001-1568","record":{"aliases":["GHSA-88p5-p62r-9756"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WAP gateway","requires_auth":"none","summary":"Remote attackers can spoof SSL certificates via man-in-the-middle attacks because the WAP gateway fails to verify fully qualified domain names in X.509 certificates.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wap_gateway","vendor":"cmg"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:N","version":"2.0"},"cwes":[],"description":"CMG WAP gateway does not verify the fully qualified domain name URL with X.509 certificates from root certificate authorities, which allows remote attackers to spoof SSL certificates via a man-in-the-middle attack.","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-2001-1568","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2001"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2001-1569"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2001-1567"},"products":["n/a"],"published":"2005-07-14","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-09-17","vendors":["n/a"]},"summary":"Remote attackers can spoof SSL certificates via man-in-the-middle attacks because the WAP gateway fails to verify fully qualified domain names in X.509 certificates.","url":"https://insights.sbomify.com/CVE-2001-1568/"}