vproxy is vulnerable to a divide by zero DoS attack
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| 0x676e67 | vproxy | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| 0x676e67 | Vproxy | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-23192 | vproxy Divide by Zero DoS Vulnerability |
Github GHSA |
GHSA-7h24-c332-p48c | vproxy Divide by Zero DoS Vulnerability |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.642% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
0x676e67
0x676e67 vproxy |
|
| Vendors & Products |
0x676e67
0x676e67 vproxy |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | vproxy is an HTTP/HTTPS/SOCKS5 proxy server. In versions 2.3.3 and below, 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. This is fixed in version 2.4.0. | |
| Title | vproxy is vulnerable to a divide by zero DoS attack | |
| Weaknesses | CWE-369 | |
| References |
| |
| Metrics |
cvssV3_1
|