websafe-kb/07-framework-security/frameworks/nextjs/cases/nextjs-cve-2022-36046.md

---
title: "Unexpected server crash in Next.js"
system_id: "nextjs"
category: "frameworks"
advisory_mode: "core"
published_date: "2022-08-30T20:38:34Z"
updated_date: "2023-11-08T04:09:58.785797Z"
severity: "low"
exploit_status: "unknown"
source_confidence: "official"
verification_status: "triage-manual"
verification_mode: "synthetic"
artifact_mode: "official-source"
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-2022-36046"
  - "GHSA-wff4-fpwg-qqv3"
affected_versions:
  - "12.2.3"
  - "introduced=12.2.3, fixed<12.2.4"
fixed_versions:
  - "12.2.4"
entity_refs:
  - "nextjs:system:root-system"
  - "nextjs--project--next:project:affected-component"
secure_code_topics:
  - "authz-server-side-recheck"
  - "proxy-trust-boundary"
  - "token-cookie-storage"
primary_source: "https://github.com/vercel/next.js/security/advisories/GHSA-wff4-fpwg-qqv3"
---

# Unexpected server crash in Next.js

## 本地实证状态

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

## 事件层

- Canonical ID: `nextjs--CVE-2022-36046`
- 系统: `nextjs`
- 严重度: `low`
- 来源置信度: `official`
- 官方主源: https://github.com/vercel/next.js/security/advisories/GHSA-wff4-fpwg-qqv3
- 影响版本: `12.2.3, introduced=12.2.3, fixed<12.2.4`
- 修复版本: `12.2.4`

## 对象与版本映射

- Advisory Scope: `package`
- 影响对象: `next`
- Entity Refs: `nextjs, nextjs--project--next`
- 版本置信度: `high`
- 版本缺口: `-`
- 版本证据源: `https://github.com/vercel/next.js/security/advisories/GHSA-wff4-fpwg-qqv3, https://nvd.nist.gov/vuln/detail/CVE-2022-36046, https://github.com/vercel/next.js/releases/tag/v12.2.4`

## 受控验证流程

- Workflow ID: `nextjs--CVE-2022-36046--workflow`
- 漏洞家族: `proxy-boundary`
- 入口面: `proxy-header-or-trust-boundary`
- 需要角色: `reverse-proxy-or-edge-client`
- 触发向量: 对 `proxy-boundary` 家族入口投递最小化、可审计、可回滚的受控输入，比较修复前后差异。
- 请求/页面入口: `/middleware, /x-forwarded-* trust path`
- 输入形态: 提交受控代理头或来源头，验证信任边界和回源鉴权。
- 预期不安全行为: 仅凭代理头即可越过鉴权或来源控制。

## 其他来源

- https://nvd.nist.gov/vuln/detail/CVE-2022-36046
- https://github.com/vercel/next.js/releases/tag/v12.2.4

## 证据点与补丁验证

### 服务端证据点

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

### 浏览器证据点

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

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

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

### 检测信号

- WAF / reverse proxy 异常日志、访问日志和告警
- 应用审计日志中的权限错误、重定向异常、模板渲染或上传落盘事件
- 上游代理与应用层对 Content-Length / Transfer-Encoding / forwarded headers 的解释差异

### 补丁验证步骤

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

### 实验安全备注

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

## 实验层

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

## 修复示例

- [javascript-typescript:authz-server-side-recheck](/Users/x/websafe/05-defense/secure-code/javascript-typescript/authz-server-side-recheck.md)
- [nodejs:authz-server-side-recheck](/Users/x/websafe/05-defense/secure-code/nodejs/authz-server-side-recheck.md)
- [java:authz-server-side-recheck](/Users/x/websafe/05-defense/secure-code/java/authz-server-side-recheck.md)
- [php:authz-server-side-recheck](/Users/x/websafe/05-defense/secure-code/php/authz-server-side-recheck.md)
- [python:authz-server-side-recheck](/Users/x/websafe/05-defense/secure-code/python/authz-server-side-recheck.md)
- [ruby:authz-server-side-recheck](/Users/x/websafe/05-defense/secure-code/ruby/authz-server-side-recheck.md)
- [csharp:authz-server-side-recheck](/Users/x/websafe/05-defense/secure-code/csharp/authz-server-side-recheck.md)
- [go:authz-server-side-recheck](/Users/x/websafe/05-defense/secure-code/go/authz-server-side-recheck.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)
- [javascript-typescript:token-cookie-storage](/Users/x/websafe/05-defense/secure-code/javascript-typescript/token-cookie-storage.md)
- [nodejs:token-cookie-storage](/Users/x/websafe/05-defense/secure-code/nodejs/token-cookie-storage.md)
- [java:token-cookie-storage](/Users/x/websafe/05-defense/secure-code/java/token-cookie-storage.md)
- [php:token-cookie-storage](/Users/x/websafe/05-defense/secure-code/php/token-cookie-storage.md)
- [python:token-cookie-storage](/Users/x/websafe/05-defense/secure-code/python/token-cookie-storage.md)
- [ruby:token-cookie-storage](/Users/x/websafe/05-defense/secure-code/ruby/token-cookie-storage.md)
- [csharp:token-cookie-storage](/Users/x/websafe/05-defense/secure-code/csharp/token-cookie-storage.md)
- [go:token-cookie-storage](/Users/x/websafe/05-defense/secure-code/go/token-cookie-storage.md)