Listen to this Post
How the CVE Works
The vulnerability arises due to improper path sanitization in the request processing logic. When a CDN caches static assets (e.g., .png, .json, .css), a malicious actor can craft a deceptive path (e.g., /api/auth/get-session/api/auth/image.png) that appears to be a static file but instead retrieves sensitive data. The library splits paths using `config.basePath` but fails to validate remaining components, allowing cache poisoning. This can expose user sessions and personal data when the CDN serves the cached response to other users.
DailyCVE Form
Platform: Better-Call
Version:
Vulnerability: Cache Deception
Severity: Critical
Date: 2023-XX-XX
Prediction: Patch expected by 2023-XX-XX
What Undercode Say
curl -X GET "https://target.com/api/auth/get-session/api/auth/image.png"
const processRequest = async (request) => {
const url = new URL(request.url);
const path = config?.basePath ? url.pathname.split(config.basePath)[bash] : url.pathname;
};
How Exploit
Craft malicious path mimicking static assets to bypass CDN cache rules.
Protection from this CVE
Disable CDN caching for dynamic endpoints. Enforce strict path validation.
Impact
Unauthorized access to user sessions and sensitive data via cached responses.
References
[Insert real CVE reference here]
Sources:
Reported By: github.com
Extra Source Hub:
Undercode
