{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4440 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4440 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4440 is a medium-severity vulnerability in n/a, published on 21 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-4440 and fix it if it is affected.\n\nWhat it is: CVE-2005-4440 is a medium-severity vulnerability in n/a, published on 21 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-4440 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-4440/ (Markdown: https://insights.sbomify.com/CVE-2005-4440/index.md)","id":"CVE-2005-4440","markdown":"https://insights.sbomify.com/CVE-2005-4440/index.md","name":"CVE-2005-4440","record":{"aliases":["GHSA-9rvj-pj6p-4pj6"],"analysis":{"component_type":"network_device","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"802.1q VLAN protocol","requires_auth":"none","summary":"Remote attackers can bypass network segmentation and spoof VLAN traffic by sending double-tagged 802.1q frames, affecting network infrastructure security.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vlan_protocol","vendor":"vlan_protocol"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"The 802.1q VLAN protocol allows remote attackers to bypass network segmentation and spoof VLAN traffic via a message with two 802.1q tags, which causes the second tag to be redirected from a downstream switch after the first tag has been stripped, as demonstrated by Yersinia, aka \"double-tagging VLAN jumping 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":"Security feature bypass in n/a","id":"CVE-2005-4440","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2005"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2005-4441"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2005-4439"},"products":["n/a"],"published":"2005-12-21","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":"Remote attackers can bypass network segmentation and spoof VLAN traffic by sending double-tagged 802.1q frames, affecting network infrastructure security.","url":"https://insights.sbomify.com/CVE-2005-4440/"}