How severe is GHSA-hqmp-g7ph-x543?

GHSA-hqmp-g7ph-x543 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-hqmp-g7ph-x543?

GHSA-hqmp-g7ph-x543 affects the following packages: quincy (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-hqmp-g7ph-x543?

No patched version of quincy has shipped for GHSA-hqmp-g7ph-x543 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-hqmp-g7ph-x543 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for quincy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hqmp-g7ph-x543 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hqmp-g7ph-x543?

O3 pinpoints whether GHSA-hqmp-g7ph-x543 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hqmp-g7ph-x543 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hqmp-g7ph-x543 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-hqmp-g7ph-x543 published, and has it been updated?

GHSA-hqmp-g7ph-x543 was published on December 27, 2024 and was last updated on May 19, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-hqmp-g7ph-x543: TunnelVision - decloaking VPNs using DHCP…

Blast Radius

1 pkg affected

🦀quincy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Impact

All users are potentially affected, as this attack vector can be used against any VPN implementation without mitigations in place.

Patches

Currently, there are no existing mitigations employed by Quincy.

Workarounds

Disabling DHCP option 121 in the DHCP client is a potential workaround, as it prevents this kind of attack.

References

https://www.leviathansecurity.com/blog/tunnelvision

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`quincy`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for quincy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of quincy has shipped for GHSA-hqmp-g7ph-x543 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hqmp-g7ph-x543 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hqmp-g7ph-x543. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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. ### Impact All users are potentially affected, as this attack vector can be used against _any_ VPN implementation without mitigations in place. ### Patches Currently, the

O3 Security · Impact-Aware SCA

Is GHSA-hqmp-g7ph-x543 in your dependencies?

O3 detects GHSA-hqmp-g7ph-x543 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-hqmp-g7ph-x543