Listen to this Post
How the CVE Works
The vulnerability arises when untrusted data from the HTTP `Proxy-Authorization` header is processed by `Extension::try_from` and passed to parse_ttl_extension. The data is parsed as a Time-To-Live (TTL) value. If an attacker sets the TTL to zero (e.g., via a crafted username like configuredUser-ttl-0), the subsequent modulo operation `timestamp % ttl` triggers a division-by-zero panic. This crashes the vproxy server, leading to a denial-of-service condition. The flaw stems from insufficient input validation in the TTL parsing logic.
DailyCVE Form
Platform: vproxy
Version: Latest
Vulnerability: DoS
Severity: Critical
Date: 2024-XX-XX
Prediction: Patch by Q3 2024
What Undercode Say
curl -x "http://test-ttl-0:[email protected]:8101" https://google.com
// Vulnerable code snippet (extension.rs) timestamp % ttl // Division-by-zero panic
How Exploit
1. Craft malicious `Proxy-Authorization` header.
2. Set TTL to zero.
3. Trigger server crash.
Protection from this CVE
- Input validation for TTL.
- Zero-division checks.
- Patch update.
Impact
- Full proxy downtime.
- Service disruption.
🎯Let’s Practice Exploiting & Learn Patching For Free:
Sources:
Reported By: github.com
Extra Source Hub:
Undercode
