---
title: "Undici vulnerable to data leak when using response.arrayBuffer()"
system_id: "undici"
category: "frameworks"
advisory_mode: "core"
published_date: "2024-07-09T13:32:30Z"
updated_date: "2024-07-09T13:57:47.271493Z"
severity: "low"
exploit_status: "unknown"
source_confidence: "official"
verification_status: "triage-manual"
verification_mode: "synthetic"
artifact_mode: "synthetic"
last_run_id: ""
target_types:
  - "lab-local"
  - "lab-public"
  - "authorized-third-party"
allow_public_validation: "yes, with ownership or explicit authorization"
authorization_prerequisite: "asset ownership proof or explicit written authorization"
minimal_validation: "read-only probe, controlled payload, reversible test"
aliases:
  - "CVE-2024-38372"
  - "GHSA-3g92-w8c5-73pq"
affected_versions:
  - "introduced=6.14.0, fixed<6.19.2"
fixed_versions:
  - "6.19.2"
entity_refs:
  - "undici:system:root-system"
  - "undici--project--undici:project:affected-component"
secure_code_topics:
  - "ssrf-url-validation"
  - "proxy-trust-boundary"
primary_source: "https://github.com/nodejs/undici/security/advisories/GHSA-3g92-w8c5-73pq"
---

# Undici vulnerable to data leak when using response.arrayBuffer()

## 本地实证状态

- 实证状态: `triage-manual`
- 实证方式: `synthetic`
- Artifact 模式: `synthetic`
- 最近运行: `-`
- 浏览器证据: `missing`
- Run Bundle: `-`

## 事件层

- Canonical ID: `undici--CVE-2024-38372`
- 系统: `undici`
- 严重度: `low`
- 来源置信度: `official`
- 官方主源: https://github.com/nodejs/undici/security/advisories/GHSA-3g92-w8c5-73pq
- 影响版本: `introduced=6.14.0, fixed<6.19.2`
- 修复版本: `6.19.2`

## 对象与版本映射

- Advisory Scope: `package`
- 影响对象: `undici`
- Entity Refs: `undici, undici--project--undici`
- 版本置信度: `high`
- 版本缺口: `-`
- 版本证据源: `https://github.com/nodejs/undici/security/advisories/GHSA-3g92-w8c5-73pq, https://github.com/nodejs/undici/commit/f979ec3204ca489abf30e7d20e9fee9ea7711d36, https://nvd.nist.gov/vuln/detail/CVE-2024-38372, https://github.com/nodejs/undici/issues/3328, https://github.com/nodejs/undici/issues/3337`

## 受控验证流程

- Workflow ID: `undici--CVE-2024-38372--workflow`
- 漏洞家族: `ssrf`
- 入口面: `remote-fetch-or-webhook-endpoint`
- 需要角色: `editor-or-admin`
- 触发向量: 对 `ssrf` 家族入口投递最小化、可审计、可回滚的受控输入，比较修复前后差异。
- 请求/页面入口: `/webhook/test, /remote-fetch, /import-url`
- 输入形态: 提交受控回环或哨兵 URL，验证协议、主机、IP 与重定向限制。
- 预期不安全行为: 服务端向受控目标发起非预期请求。

## 其他来源

- https://github.com/nodejs/undici/commit/f979ec3204ca489abf30e7d20e9fee9ea7711d36
- https://nvd.nist.gov/vuln/detail/CVE-2024-38372
- https://github.com/nodejs/undici/issues/3328
- https://github.com/nodejs/undici/issues/3337
- https://github.com/nodejs/undici/pull/3338
- https://github.com/nodejs/undici
- https://security.netapp.com/advisory/ntap-20240828-0009/

## 证据点与补丁验证

### 服务端证据点

- 应用日志中的命中路径、鉴权决策和异常栈
- 反向代理或边界层日志中的请求头、来源 IP 与路由决策

### 浏览器证据点

- 基线截图与攻击后截图的 DOM/视觉差异
- console、network 与 response metadata 中的异常信号

### 数据库/文件系统证据点

- 数据库中新增/越权读取的测试数据
- 文件系统中新增上传样本、缓存条目或越权读取痕迹

### 检测信号

- WAF / reverse proxy 异常日志、访问日志和告警
- 应用审计日志中的权限错误、重定向异常、模板渲染或上传落盘事件

### 补丁验证步骤

- 确认目标版本从 `introduced=6.14.0, fixed<6.19.2` 升级或回移到 `6.19.2`。
- 保留同一组受控输入，在修复前后分别执行并比对响应、日志与浏览器证据。
- 确认修复后仅保留预期业务行为，不再触发越权、回显、异常渲染或错误请求。
- 补充 `ssrf` 族自动化回归，避免同类路径在插件、主题或代理链中回归。

### 实验安全备注

- 只使用回环地址、哨兵目标、无害样本或可回滚测试数据。
- 禁止造成持久破坏、越权下载真实数据或不可回滚 side effect。
- 如需浏览器证据，保留 baseline / proof 两份快照以及 console / network 记录。

## 实验层

- 仅用于自有资产、测试环境或已明确授权目标。
- 允许公网可达目标，但必须满足资产归属或明确授权前提。
- 最小化验证方式: 最小化验证、只读探测、可审计回显、受控注入。
- 若该案例涉及插件、模块或扩展，应同时检查供应链与升级策略。
- 禁止场景: 无归属证明或无明确授权的公网目标；知名公共网站或与测试无关的第三方资产；会造成持久破坏、数据越权下载或不可回滚影响的动作

## 修复示例

- [javascript-typescript:ssrf-url-validation](/Users/x/websafe/05-defense/secure-code/javascript-typescript/ssrf-url-validation.md)
- [nodejs:ssrf-url-validation](/Users/x/websafe/05-defense/secure-code/nodejs/ssrf-url-validation.md)
- [java:ssrf-url-validation](/Users/x/websafe/05-defense/secure-code/java/ssrf-url-validation.md)
- [php:ssrf-url-validation](/Users/x/websafe/05-defense/secure-code/php/ssrf-url-validation.md)
- [python:ssrf-url-validation](/Users/x/websafe/05-defense/secure-code/python/ssrf-url-validation.md)
- [ruby:ssrf-url-validation](/Users/x/websafe/05-defense/secure-code/ruby/ssrf-url-validation.md)
- [csharp:ssrf-url-validation](/Users/x/websafe/05-defense/secure-code/csharp/ssrf-url-validation.md)
- [go:ssrf-url-validation](/Users/x/websafe/05-defense/secure-code/go/ssrf-url-validation.md)
- [javascript-typescript:proxy-trust-boundary](/Users/x/websafe/05-defense/secure-code/javascript-typescript/proxy-trust-boundary.md)
- [nodejs:proxy-trust-boundary](/Users/x/websafe/05-defense/secure-code/nodejs/proxy-trust-boundary.md)
- [java:proxy-trust-boundary](/Users/x/websafe/05-defense/secure-code/java/proxy-trust-boundary.md)
- [php:proxy-trust-boundary](/Users/x/websafe/05-defense/secure-code/php/proxy-trust-boundary.md)
- [python:proxy-trust-boundary](/Users/x/websafe/05-defense/secure-code/python/proxy-trust-boundary.md)
- [ruby:proxy-trust-boundary](/Users/x/websafe/05-defense/secure-code/ruby/proxy-trust-boundary.md)
- [csharp:proxy-trust-boundary](/Users/x/websafe/05-defense/secure-code/csharp/proxy-trust-boundary.md)
- [go:proxy-trust-boundary](/Users/x/websafe/05-defense/secure-code/go/proxy-trust-boundary.md)