{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1623 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1623 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1623 is a medium-severity vulnerability in n/a, published on 26 Mar 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-2002-1623 and fix it if it is affected.\n\nWhat it is: CVE-2002-1623 is a medium-severity vulnerability in n/a, published on 26 Mar 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-2002-1623 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-2002-1623/ (Markdown: https://insights.sbomify.com/CVE-2002-1623/index.md)","id":"CVE-2002-1623","markdown":"https://insights.sbomify.com/CVE-2002-1623/index.md","name":"CVE-2002-1623","record":{"aliases":["GHSA-ccfp-7gpg-fg7v"],"analysis":{"component_type":"network_device","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IKE protocol implementation","requires_auth":"none","summary":"Remote attackers can sniff IKE Aggressive Mode traffic to reveal valid usernames, exposing sensitive identity information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vpn-1_firewall-1","vendor":"checkpoint"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"The design of the Internet Key Exchange (IKE) protocol, when using Aggressive Mode for shared secret authentication, does not encrypt initiator or responder identities during negotiation, which may allow remote attackers to determine valid usernames by (1) monitoring responses before the password is supplied or (2) sniffing, as originally reported for FireWall-1 SecuRemote.","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":"Information disclosure in n/a","id":"CVE-2002-1623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2002"},"n_packages":0,"n_references":10,"next":{"headline":"Memory corruption in n/a","id":"CVE-2002-1624"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2002-1622"},"products":["n/a"],"published":"2005-03-26","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":"Remote attackers can sniff IKE Aggressive Mode traffic to reveal valid usernames, exposing sensitive identity information.","url":"https://insights.sbomify.com/CVE-2002-1623/"}