{"answers":{"affected":"2 open source packages ship an affected version, including quincy.","exploited":"There is no known exploitation of GHSA-hqmp-g7ph-x543 in the wild and no public exploit code.","fix":"No fix has been published for GHSA-hqmp-g7ph-x543 yet. Limit exposure of the affected software until one is available.","what":"GHSA-hqmp-g7ph-x543 is a vulnerability in quincy, published on 27 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-hqmp-g7ph-x543 and fix it if it is affected.\n\nWhat it is: GHSA-hqmp-g7ph-x543 is a vulnerability in quincy, published on 27 Dec 2024. 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 GHSA-hqmp-g7ph-x543 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- quincy (crates.io): affected all versions up to 0.13.0; no fix listed\n- quincy (crates.io): affected all versions up to 0.13.0; no fix listed\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/GHSA-hqmp-g7ph-x543/ (Markdown: https://insights.sbomify.com/GHSA-hqmp-g7ph-x543/index.md)","id":"GHSA-hqmp-g7ph-x543","markdown":"https://insights.sbomify.com/GHSA-hqmp-g7ph-x543/index.md","name":"GHSA-hqmp-g7ph-x543","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust DHCP client","requires_auth":"none","summary":"Attackers can bypass VPN encryption by injecting routing entries via DHCP option 121, redirecting traffic to the local network.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"A new decloaking technique for nearly all VPN implementations has been found, which allows attackers to inject entries into the routing tables of unsuspecting victims using DHCP option 121. This allows attackers to redirect traffic, which is supposed to be sent encrypted over the VPN, through the physical interface handling DHCP for the network the victim's computer is connected to, effectively bypassing the VPN connection.\n\n### Impact\nAll users are potentially affected, as this attack vector can be used against _any_ VPN implementation without mitigations in place.\n\n### Patches\nCurrently, there are no existing mitigations employed by Quincy.\n\n### Workarounds\nDisabling DHCP option 121 in the DHCP client is a potential workaround, as it prevents this kind of attack.\n\n### References\nhttps://www.leviathansecurity.com/blog/tunnelvision","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"TunnelVision - decloaking VPNs using DHCP","id":"GHSA-hqmp-g7ph-x543","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.13.0"],"package":"quincy","purl":null,"source":"GHSA-hqmp-g7ph-x543"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.13.0"],"package":"quincy","purl":"pkg:cargo/quincy","source":"GHSA-hqmp-g7ph-x543"}],"products":null,"published":"2024-12-27","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass VPN encryption by injecting routing entries via DHCP option 121, redirecting traffic to the local network.","url":"https://insights.sbomify.com/GHSA-hqmp-g7ph-x543/"}