{"answers":{"affected":"It affects 16 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2640 exists.","fix":"No fix has been published for CVE-2005-2640 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2640 is a medium-severity vulnerability in n/a, published on 20 Aug 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-2005-2640 and fix it if it is affected.\n\nWhat it is: CVE-2005-2640 is a medium-severity vulnerability in n/a, published on 20 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2640 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-2005-2640/ (Markdown: https://insights.sbomify.com/CVE-2005-2640/index.md)","id":"CVE-2005-2640","markdown":"https://insights.sbomify.com/CVE-2005-2640/index.md","name":"CVE-2005-2640","record":{"aliases":["GHSA-8h6v-vg4c-567j"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Juniper Netscreen VPN","requires_auth":"none","summary":"Remote attackers can enumerate valid usernames via IKE Aggressive Mode packets in Juniper Netscreen VPN, exposing user account information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"netscreen-5gt","vendor":"juniper"},{"product":"netscreen-idp","vendor":"juniper"},{"product":"netscreen-idp_10","vendor":"juniper"},{"product":"netscreen-idp_100","vendor":"juniper"},{"product":"netscreen-idp_1000","vendor":"juniper"},{"product":"netscreen-idp_500","vendor":"juniper"},{"product":"netscreen_screenos","vendor":"juniper"},{"product":"instant_virtual_extranet","vendor":"neoteris"},{"product":"netscreen-sa_5000_series","vendor":"netscreen"},{"product":"netscreen-sa_5020_series","vendor":"netscreen"},{"product":"netscreen-sa_5050_series","vendor":"netscreen"},{"product":"ns-10","vendor":"netscreen"},{"product":"ns-100","vendor":"netscreen"},{"product":"ns-204","vendor":"netscreen"},{"product":"ns-500","vendor":"netscreen"},{"product":"ns-50ns25","vendor":"netscreen"}],"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":"Behavioral discrepancy information leak in Juniper Netscreen VPN running ScreenOS 5.2.0 and earlier, when using IKE with pre-shared key authentication, allows remote attackers to enumerate valid usernames via an IKE Aggressive Mode packet, which generates a response if the username is valid but does not respond when the username is invalid.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2005-08-18","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2005-08-18","kind":"exploitdb","ref":"26168","stars":null,"title":"Juniper NetScreen 5.0 - VPN 'Username' Enumeration"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2005-2640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":5,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2005-2641"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2005-2639"},"products":["n/a"],"published":"2005-08-20","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-07","vendors":["n/a"]},"summary":"Remote attackers can enumerate valid usernames via IKE Aggressive Mode packets in Juniper Netscreen VPN, exposing user account information.","url":"https://insights.sbomify.com/CVE-2005-2640/"}