Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

github логотип

GHSA-x4m5-4cw8-vc44

Опубликовано: 30 дек. 2025
Источник: github
Github: Прошло ревью
CVSS4: 6

Описание

axios-cache-interceptor Vulnerable to Cache Poisoning via Ignored HTTP Vary Header

Summary

When a server calls an upstream service using different auth tokens, axios-cache-interceptor returns incorrect cached responses, leading to authorization bypass.

Details

The cache key is generated only from the URL, ignoring request headers like Authorization. When the server responds with Vary: Authorization (indicating the response varies by auth token), the library ignores this, causing all requests to share the same cache regardless of authorization.

Impact

Affected: Server-side applications (APIs, proxies, backend services) that:

  • Use axios-cache-interceptor to cache requests to upstream services
  • Handle requests from multiple users with different auth tokens
  • Upstream services replies on Vary to differentiate caches

Not affected: Browser/client-side applications (single user per browser session).

Services using different auth tokens to call upstream services will return incorrect cached data, bypassing authorization checks and leaking user data across different authenticated sessions.

Solution

After v1.11.1, automatic Vary header support is now enabled by default.

When server responds with Vary: Authorization, cache keys now include the authorization header value. Each user gets their own cache.

// v1.11.1+ (automatic, no config needed) // User 123: key = hash(url + {authorization: 'Bearer 123'}) // User 456: key = hash(url + {authorization: 'Bearer 456'}) // ✓ Different caches, no poisoning

Remediation

Upgrade to v1.11.1 or later. No code changes required, protection is automatic

Proof of Concept

const http = require('node:http'); const axios = require('axios'); const { setupCache } = require('axios-cache-interceptor'); // Server that returns different responses based on Authorization const server = http.createServer((req, res) => { const auth = req.headers.authorization; res.setHeader('Vary', 'Authorization'); if (auth === 'Bearer 123') { res.write('Hello, user 123!'); } else if (auth === 'Bearer 456') { res.write('Hello, user 456!'); } else { res.write('Unknown'); } res.end(); }); server.listen(5000); // Client making requests with different tokens const cachedAxios = setupCache(axios.create()); const server2 = http.createServer(async (_req, res) => { const authHeader = Math.random() < 0.5 ? 'Bearer 123' : 'Bearer 456'; const response = await cachedAxios.get('http://localhost:5000', { headers: { Authorization: authHeader } }); console.log({ response: response.data, cached: response.cached, auth: authHeader }); res.write(response.data); res.end(); }); server2.listen(5001); // Trigger 10 requests Promise.all( Array.from({ length: 10 }, () => axios.get('http://localhost:5001').catch(console.error) ) ).finally(() => { server.close(); server2.close(); });

All 10 responses return "Hello, user 123!" even when using "Bearer 456" - users receive each other's cached data.

Ссылки

Пакеты

Наименование

axios-cache-interceptor

npm
Затронутые версииВерсия исправления

< 1.11.1

1.11.1

EPSS

Процентиль: 10%
0.00035
Низкий

6 Medium

CVSS4

CVE ID

CVE-2025-69202

Дефекты

CWE-524
CWE-639

Связанные уязвимости

nvd логотип

CVE-2025-69202

CVSS3: 6.5
nvd
около 1 месяца назад

Axios Cache Interceptor is a cache interceptor for axios. Prior to version 1.11.1, when a server calls an upstream service using different auth tokens, axios-cache-interceptor returns incorrect cached responses, leading to authorization bypass. The cache key is generated only from the URL, ignoring request headers like `Authorization`. When the server responds with `Vary: Authorization` (indicating the response varies by auth token), the library ignores this, causing all requests to share the same cache regardless of authorization. Server-side applications (APIs, proxies, backend services) that use axios-cache-interceptor to cache requests to upstream services, handle requests from multiple users with different auth tokens, and upstream services replies on `Vary` to differentiate caches are affected. Browser/client-side applications (single user per browser session) are not affected. Services using different auth tokens to call upstream services will return incorrect cached data, bypas

EPSS

Процентиль: 10%
0.00035
Низкий

6 Medium

CVSS4

CVE ID

CVE-2025-69202

Дефекты

CWE-524
CWE-639