vproxy Divide by Zero DoS Vulnerability

Description

Summary

Untrusted, user-controlled data from the HTTP Proxy-Authorization header can induce a denial of service state.

Details

Untrusted data is extracted from the user-controlled HTTP Proxy-Authorization header and passed to Extension::try_from and flows into parse_ttl_extension where it is parsed as a TTL value. If an attacker supplies a TTL of zero (e.g. by using a username such as 'configuredUser-ttl-0'), the modulo operation 'timestamp % ttl' will cause a division by zero panic, causing the server to crash causing a denial-of-service.

The code assumed to be responsible for this can be found here: https://github.com/0x676e67/vproxy/blob/ab304c3854bf8480be577039ada0228907ba0923/src/extension.rs#L173-L183

PoC

  1. Download and run the latest version of vproxy
  2. Send a cUrl request like the following, adjusting address and port as necessary: curl -x "http://test-ttl-0:[email protected]:8101" https://google.com
  3. Wait for a cUrl error indicating "Proxy CONNECT aborted"
  4. View logs from the vproxy server
  5. Observe that the vproxy server crashed due to a divide-by-zero panic

Impact

The resulting crash renders the proxy server unusable until it is reset.

Finally, one last note: I'm reporting this on behalf of another researcher at Black Duck. Credit for discovery should be attributed to David Bohannon (dbohannon)

Basic information

Type
reviewed
Severity
high
Advisory on GitHub
Open advisory ↗
Repository advisory
Open repository advisory ↗
Source code
Browse source ↗
Published (advisory)
2025-07-30 16:33:41 UTC
Updated
2025-08-21 17:23:57 UTC
GitHub reviewed
2025-07-30 16:33:41 UTC
NVD published
2025-07-30

EPSS Score

Score Percentile
0.09% 24.82%

CVSS Scores

Base score Version Severity Vector
7.5 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.

Identifiers

CWEs

CWE id Name
CWE-369 Divide By Zero

Credits

  • bronallo-bd (reporter)

Affected packages (1)

Vulnerable version ranges and first patched releases as published by GitHub.

Ecosystem Package Vulnerable range First patched Vulnerable functions
rust vproxy <= 2.3.3 2.4.0

References

cvelogic Threat Intelligence