https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 17:38:11 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-00065 bdu:2026-00065 https://cve.radiocsirt.org/vuln/bdu:2026-00065 https://cve.radiocsirt.org/vuln/euvd-2026-248757 EUVD-2026-248757 https://cve.radiocsirt.org/vuln/euvd-2026-248757 https://cve.radiocsirt.org/vuln/fkie_cve-2025-54581 <p>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 &#39;configuredUser-ttl-0&#39;), the modulo operation &#39;timestamp % ttl&#39; 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.</p> <p>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 &#39;configuredUser-ttl-0&#39;), the modulo operation &#39;timestamp % ttl&#39; 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-54581 https://cve.radiocsirt.org/vuln/ghsa-7h24-c332-p48c <p><strong>Affected:</strong> crates.io: vproxy</p> <p>### Summary Untrusted, user-controlled data from the HTTP Proxy-Authorization header can induce a denial of service state.</p> <p>### 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 &#39;configuredUser-ttl-0&#39;), the modulo operation &#39;timestamp % ttl&#39; will cause a division by zero panic, causing the server to crash causing a denial-of-service.</p> <p>The code assumed to be responsible for this can be found here: https://github.com/0x676e67/vproxy/blob/ab304c3854bf8480be577039ada0228907ba0923/src/extension.rs#L173-L183</p> <p>### 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 &#34;http://test-ttl-0:test@127.0.0.1:8101&#34; https://google.com``` 3. Wait for a cUrl error indicating &#34;Proxy CONNECT aborted&#34; 4. View logs from the vproxy server 5. Observe that the vproxy server crashed due to a divide-by-zero panic</p> <p>### Impact The resulting crash renders the proxy server unusable until it is reset.</p> <p>Finally, one last note: I&#39;m reporting this on behalf of another researcher at Black Duck. Credit for discovery should be attributed to David Bohannon ([dbohannon](https://github.com/dbohannon))</p> <p><strong>Affected:</strong> crates.io: vproxy</p> <p>### Summary Untrusted, user-controlled data from the HTTP Proxy-Authorization header can induce a denial of service state.</p> <p>### 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 &#39;configuredUser-ttl-0&#39;), the modulo operation &#39;timestamp % ttl&#39; will cause a division by zero panic, causing the server to crash causing a denial-of-service.</p> <p>The code assumed to be responsible for this can be found here: https://github.com/0x676e67/vproxy/blob/ab304c3854bf8480be577039ada0228907ba0923/src/extension.rs#L173-L183</p> <p>### 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 &#34;http://test-ttl-0:test@127.0.0.1:8101&#34; https://google.com``` 3. Wait for a cUrl error indicating &#34;Proxy CONNECT aborted&#34; 4. View logs from the vproxy server 5. Observe that the vproxy server crashed due to a divide-by-zero panic</p> <p>### Impact The resulting crash renders the proxy server unusable until it is reset.</p> <p>Finally, one last note: I&#39;m reporting this on behalf of another researcher at Black Duck. Credit for discovery should be attributed to David Bohannon ([dbohannon](https://github.com/dbohannon))</p> https://cve.radiocsirt.org/vuln/ghsa-7h24-c332-p48c