{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2341 exists.","fix":"No fix has been published for CVE-2006-2341 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-2341 is a medium-severity vulnerability in n/a, published on 12 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-2341 and fix it if it is affected.\n\nWhat it is: CVE-2006-2341 is a medium-severity vulnerability in n/a, published on 12 May 2006. 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-2006-2341 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-2006-2341/ (Markdown: https://insights.sbomify.com/CVE-2006-2341/index.md)","id":"CVE-2006-2341","markdown":"https://insights.sbomify.com/CVE-2006-2341/index.md","name":"CVE-2006-2341","record":{"aliases":["GHSA-64qh-q5qg-p2h5"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Symantec Gateway Security","requires_auth":"none","summary":"Remote attackers can determine internal IP addresses via malformed HTTP requests when NAT is enabled on Symantec Gateway Security devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"enterprise_firewall","vendor":"symantec"},{"product":"gateway_security","vendor":"symantec"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The HTTP proxy in Symantec Gateway Security 5000 Series 2.0.1 and 3.0, and Enterprise Firewall 8.0, when NAT is being used, allows remote attackers to determine internal IP addresses by using malformed HTTP requests, as demonstrated using a get request without a space separating the URI.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-05-10","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-05-10","kind":"exploitdb","ref":"27852","stars":null,"title":"Symantec Enterprise Firewall / Gateway Security - HTTP Proxy Internal IP Leakage"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2006-2341","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":8,"next":{"headline":"Auth bypass in n/a","id":"CVE-2006-2342"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-2340"},"products":["n/a"],"published":"2006-05-12","related":[{"cvss_score":9.3,"headline":"Information disclosure in n/a","id":"CVE-2007-4422","kev_date_added":null,"published":"2007-08-18"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2005-3768","kev_date_added":null,"published":"2005-11-23"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2002-1463","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":7.5,"headline":"Server-side request forgery in n/a","id":"CVE-2002-0538","kev_date_added":null,"published":"2003-04-02"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2003-0106","kev_date_added":null,"published":"2003-03-27"},{"cvss_score":5,"headline":"Memory corruption in n/a","id":"CVE-2002-2294","kev_date_added":null,"published":"2007-10-18"}],"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)"},{"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 determine internal IP addresses via malformed HTTP requests when NAT is enabled on Symantec Gateway Security devices.","url":"https://insights.sbomify.com/CVE-2006-2341/"}