Expand intel coverage and refresh monitoring

这个提交包含在:
hao
2026-03-18 14:18:09 -07:00
父节点 87008d1bd5
当前提交 00d828d090
修改 3658 个文件,包含 124245 行新增13073 行删除

查看文件

@@ -0,0 +1,107 @@
---
title: " Werkzeug safe_join() allows Windows special device names"
system_id: "werkzeug"
category: "frameworks"
advisory_mode: "core"
published_date: "2026-02-19T20:32:45Z"
updated_date: "2026-02-23T23:43:27.690386Z"
severity: "medium"
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-2026-27199"
- "GHSA-29vq-49wr-vm6x"
affected_versions:
- "0.1"
- "0.10"
- "0.10.1"
- "0.10.2"
- "0.10.3"
- "0.10.4"
- "0.11"
- "0.11.1"
- "0.11.10"
- "0.11.11"
- "0.11.12"
- "0.11.13"
- "0.11.14"
- "0.11.15"
- "0.11.2"
- "0.11.3"
- "0.11.4"
- "0.11.5"
- "0.11.6"
- "0.11.7"
fixed_versions:
- "3.1.6"
secure_code_topics:
- "proxy-trust-boundary"
- "request-smuggling-boundary"
primary_source: "https://github.com/pallets/werkzeug/security/advisories/GHSA-29vq-49wr-vm6x"
---
# Werkzeug safe_join() allows Windows special device names
## 本地实证状态
- 实证状态: `triage-manual`
- 实证方式: `synthetic`
- Artifact 模式: `synthetic`
- 最近运行: `-`
- 浏览器证据: `missing`
- Run Bundle: `-`
## 事件层
- Canonical ID: `werkzeug--CVE-2026-27199`
- 系统: `werkzeug`
- 严重度: `medium`
- 来源置信度: `official`
- 官方主源: https://github.com/pallets/werkzeug/security/advisories/GHSA-29vq-49wr-vm6x
- 影响版本: `0.1, 0.10, 0.10.1, 0.10.2, 0.10.3, 0.10.4, 0.11, 0.11.1, 0.11.10, 0.11.11`
- 修复版本: `3.1.6`
## 其他来源
- https://nvd.nist.gov/vuln/detail/CVE-2026-27199
- https://github.com/pallets/werkzeug/commit/f407712fdc60a09c2b3f4fe7db557703e5d9338d
- https://github.com/pallets/werkzeug
- https://github.com/pallets/werkzeug/releases/tag/3.1.6
## 实验层
- 仅用于自有资产、测试环境或已明确授权目标。
- 允许公网可达目标,但必须满足资产归属或明确授权前提。
- 最小化验证方式: 最小化验证、只读探测、可审计回显、受控注入。
- 若该案例涉及插件、模块或扩展,应同时检查供应链与升级策略。
- 禁止场景: 无归属证明或无明确授权的公网目标;知名公共网站或与测试无关的第三方资产;会造成持久破坏、数据越权下载或不可回滚影响的动作
## 修复示例
- [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:request-smuggling-boundary](/Users/x/websafe/05-defense/secure-code/javascript-typescript/request-smuggling-boundary.md)
- [nodejs:request-smuggling-boundary](/Users/x/websafe/05-defense/secure-code/nodejs/request-smuggling-boundary.md)
- [java:request-smuggling-boundary](/Users/x/websafe/05-defense/secure-code/java/request-smuggling-boundary.md)
- [php:request-smuggling-boundary](/Users/x/websafe/05-defense/secure-code/php/request-smuggling-boundary.md)
- [python:request-smuggling-boundary](/Users/x/websafe/05-defense/secure-code/python/request-smuggling-boundary.md)
- [ruby:request-smuggling-boundary](/Users/x/websafe/05-defense/secure-code/ruby/request-smuggling-boundary.md)
- [csharp:request-smuggling-boundary](/Users/x/websafe/05-defense/secure-code/csharp/request-smuggling-boundary.md)
- [go:request-smuggling-boundary](/Users/x/websafe/05-defense/secure-code/go/request-smuggling-boundary.md)