--- title: "Next Vulnerable to Denial of Service with Server Components" system_id: "nextjs" category: "frameworks" advisory_mode: "core" published_date: "2025-12-11T22:49:27Z" updated_date: "2026-02-04T03:55:54.855562Z" severity: "low" exploit_status: "unknown" source_confidence: "official" verification_status: "verified-real" verification_mode: "real" artifact_mode: "local-fixture" last_run_id: "nextjs-nextjs--GHSA-mwv6-3258-q52c-20260318035842" 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: - "GHSA-mwv6-3258-q52c" affected_versions: - "introduced=13.3.0, fixed<14.2.34" - "introduced=15.0.0-canary.0, fixed<15.0.6" - "introduced=15.1.1-canary.0, fixed<15.1.10" - "introduced=15.2.0-canary.0, fixed<15.2.7" - "introduced=15.3.0-canary.0, fixed<15.3.7" - "introduced=15.4.0-canary.0, fixed<15.4.9" - "introduced=15.5.1-canary.0, fixed<15.5.8" - "introduced=15.6.0-canary.0, fixed<15.6.0-canary.59" - "introduced=16.0.0-beta.0, fixed<16.0.9" - "introduced=16.1.0-canary.0, fixed<16.1.0-canary.17" fixed_versions: - "14.2.34" - "15.0.6" - "15.1.10" - "15.2.7" - "15.3.7" - "15.4.9" - "15.5.8" - "15.6.0-canary.59" - "16.0.9" - "16.1.0-canary.17" 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" - "dependency-upgrade-policy" primary_source: "https://github.com/vercel/next.js/security/advisories/GHSA-mwv6-3258-q52c" --- # Next Vulnerable to Denial of Service with Server Components ## 本地实证状态 - 实证状态: `verified-real` - 实证方式: `real` - Artifact 模式: `local-fixture` - 最近运行: `nextjs-nextjs--GHSA-mwv6-3258-q52c-20260318035842` - 浏览器证据: `present` - Run Bundle: `/Users/x/websafe/06-case-studies/generated-runs/nextjs-nextjs--GHSA-mwv6-3258-q52c-20260318035842` ## 事件层 - Canonical ID: `nextjs--GHSA-mwv6-3258-q52c` - 系统: `nextjs` - 严重度: `low` - 来源置信度: `official` - 官方主源: https://github.com/vercel/next.js/security/advisories/GHSA-mwv6-3258-q52c - 影响版本: `introduced=13.3.0, fixed<14.2.34, introduced=15.0.0-canary.0, fixed<15.0.6, introduced=15.1.1-canary.0, fixed<15.1.10, introduced=15.2.0-canary.0, fixed<15.2.7, introduced=15.3.0-canary.0, fixed<15.3.7, introduced=15.4.0-canary.0, fixed<15.4.9, introduced=15.5.1-canary.0, fixed<15.5.8, introduced=15.6.0-canary.0, fixed<15.6.0-canary.59, introduced=16.0.0-beta.0, fixed<16.0.9, introduced=16.1.0-canary.0, fixed<16.1.0-canary.17` - 修复版本: `14.2.34, 15.0.6, 15.1.10, 15.2.7, 15.3.7, 15.4.9, 15.5.8, 15.6.0-canary.59, 16.0.9, 16.1.0-canary.17` ## 对象与版本映射 - Advisory Scope: `package` - 影响对象: `next` - Entity Refs: `nextjs, nextjs--project--next` - 版本置信度: `high` - 版本缺口: `-` - 版本证据源: `https://github.com/vercel/next.js/security/advisories/GHSA-mwv6-3258-q52c, https://github.com/vercel/next.js, https://nextjs.org/blog/security-update-2025-12-11, https://www.cve.org/CVERecord?id=CVE-2025-55184` ## 受控验证流程 - Workflow ID: `nextjs--GHSA-mwv6-3258-q52c--workflow` - 漏洞家族: `proxy-boundary` - 入口面: `proxy-header-or-trust-boundary` - 需要角色: `reverse-proxy-or-edge-client` - 触发向量: 对 `proxy-boundary` 家族入口投递最小化、可审计、可回滚的受控输入，比较修复前后差异。 - 请求/页面入口: `/middleware, /x-forwarded-* trust path` - 输入形态: 提交受控代理头或来源头，验证信任边界和回源鉴权。 - 预期不安全行为: 仅凭代理头即可越过鉴权或来源控制。 ## 其他来源 - https://github.com/vercel/next.js - https://nextjs.org/blog/security-update-2025-12-11 - https://www.cve.org/CVERecord?id=CVE-2025-55184 ## 证据点与补丁验证 ### 服务端证据点 - 应用日志中的命中路径、鉴权决策和异常栈 - 反向代理或边界层日志中的请求头、来源 IP 与路由决策 ### 浏览器证据点 - 基线截图与攻击后截图的 DOM/视觉差异 - console、network 与 response metadata 中的异常信号 ### 数据库/文件系统证据点 - 数据库中新增/越权读取的测试数据 - 文件系统中新增上传样本、缓存条目或越权读取痕迹 ### 检测信号 - WAF / reverse proxy 异常日志、访问日志和告警 - 应用审计日志中的权限错误、重定向异常、模板渲染或上传落盘事件 - 上游代理与应用层对 Content-Length / Transfer-Encoding / forwarded headers 的解释差异 ### 补丁验证步骤 - 确认目标版本从 `introduced=13.3.0, fixed<14.2.34, introduced=15.0.0-canary.0, fixed<15.0.6, introduced=15.1.1-canary.0, fixed<15.1.10` 升级或回移到 `14.2.34`。 - 保留同一组受控输入，在修复前后分别执行并比对响应、日志与浏览器证据。 - 确认修复后仅保留预期业务行为，不再触发越权、回显、异常渲染或错误请求。 - 补充 `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) - [javascript-typescript:dependency-upgrade-policy](/Users/x/websafe/05-defense/secure-code/javascript-typescript/dependency-upgrade-policy.md) - [nodejs:dependency-upgrade-policy](/Users/x/websafe/05-defense/secure-code/nodejs/dependency-upgrade-policy.md) - [java:dependency-upgrade-policy](/Users/x/websafe/05-defense/secure-code/java/dependency-upgrade-policy.md) - [php:dependency-upgrade-policy](/Users/x/websafe/05-defense/secure-code/php/dependency-upgrade-policy.md) - [python:dependency-upgrade-policy](/Users/x/websafe/05-defense/secure-code/python/dependency-upgrade-policy.md) - [ruby:dependency-upgrade-policy](/Users/x/websafe/05-defense/secure-code/ruby/dependency-upgrade-policy.md) - [csharp:dependency-upgrade-policy](/Users/x/websafe/05-defense/secure-code/csharp/dependency-upgrade-policy.md) - [go:dependency-upgrade-policy](/Users/x/websafe/05-defense/secure-code/go/dependency-upgrade-policy.md)