{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2004-2621 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-2621 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-2621 is a medium-severity vulnerability in n/a, published on 4 Dec 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2004-2621 and fix it if it is affected.\n\nWhat it is: CVE-2004-2621 is a medium-severity vulnerability in n/a, published on 4 Dec 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2004-2621 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-2621/ (Markdown: https://insights.sbomify.com/CVE-2004-2621/index.md)","id":"CVE-2004-2621","markdown":"https://insights.sbomify.com/CVE-2004-2621/index.md","name":"CVE-2004-2621","record":{"aliases":["GHSA-8f69-wvhw-fqc8"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Nortel VPN Client","requires_auth":"none","summary":"A race condition in the Nortel Contivity VPN Client allows remote attackers to perform man-in-the-middle attacks by bypassing certificate validation during tunnel establishment.","user_interaction":"required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"contivity","vendor":"nortel"}],"cvss":{"score":4,"severity":"medium","source":"nvd","vector":"AV:N/AC:H/Au:N/C:P/I:P/A:N","version":"2.0"},"cwes":[],"description":"Nortel Contivity VPN Client 2.1.7, 3.00, 3.01, 4.91, and 5.01, when opening a VPN tunnel, does not check the gateway certificate until after a dialog box has been displayed to the user, which creates a race condition that allows remote attackers to perform a man-in-the-middle (MITM) 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":"Race condition in n/a","id":"CVE-2004-2621","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2004"},"n_packages":0,"n_references":6,"next":{"headline":"Auth bypass in n/a","id":"CVE-2004-2622"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2004-2620"},"products":["n/a"],"published":"2005-12-04","related":[{"cvss_score":10,"headline":"Hardcoded credentials in n/a","id":"CVE-2007-2333","kev_date_added":null,"published":"2007-04-27"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2007-2334","kev_date_added":null,"published":"2007-04-27"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2005-2579","kev_date_added":null,"published":"2005-08-16"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2005-1802","kev_date_added":null,"published":"2005-06-01"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2004-1105","kev_date_added":null,"published":"2004-12-01"},{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2000-0063","kev_date_added":null,"published":"2000-10-13"},{"cvss_score":5,"headline":"Command injection in n/a","id":"CVE-2000-0064","kev_date_added":null,"published":"2000-10-13"}],"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":"A race condition in the Nortel Contivity VPN Client allows remote attackers to perform man-in-the-middle attacks by bypassing certificate validation during tunnel establishment.","url":"https://insights.sbomify.com/CVE-2004-2621/"}