{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2005-3327 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-3327 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-3327 is a high-severity authentication bypass vulnerability in n/a, published on 27 Oct 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-3327 and fix it if it is affected.\n\nWhat it is: CVE-2005-3327 is a high-severity authentication bypass vulnerability in n/a, published on 27 Oct 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-2005-3327 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-2005-3327/ (Markdown: https://insights.sbomify.com/CVE-2005-3327/index.md)","id":"CVE-2005-3327","markdown":"https://insights.sbomify.com/CVE-2005-3327/index.md","name":"CVE-2005-3327","record":{"aliases":["GHSA-9489-pvch-g6j2"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Data ONTAP storage OS","requires_auth":"none","summary":"Attackers can bypass iSCSI authentication in Data ONTAP by skipping the security negotiation phase, gaining unauthorized access to storage resources.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Network Appliance Data ONTAP 7.0 and earlier allows iSCSI Initiators to bypass iSCSI authentication via a modified client that skips the Security (Start) mode, as required by the Login Negotiation protocol, and uses Operational mode without proving identity.","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":"Auth bypass in n/a","id":"CVE-2005-3327","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2005"},"n_packages":0,"n_references":6,"next":{"headline":"Code injection in n/a","id":"CVE-2005-3328"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2005-3326"},"products":["n/a"],"published":"2005-10-27","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-07","vendors":["n/a"]},"summary":"Attackers can bypass iSCSI authentication in Data ONTAP by skipping the security negotiation phase, gaining unauthorized access to storage resources.","url":"https://insights.sbomify.com/CVE-2005-3327/"}