CVE-2016-9879

An issue was discovered in Pivotal Spring Security before 3.2.10, 4.1.x before 4.1.4, and 4.2.x before 4.2.1. Spring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded "/" to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed. Users of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), getServletPath(), and getPathInfo(). Users of other Servlet containers based on Apache Tomcat may or may not be affected depending on whether or not the handling of path parameters has been modified. Users of IBM WebSphere Application Server 8.5.x are known to be affected. Users of other containers that implement the Servlet specification may be affected.

公開: 2017-01-06 最後更新: 2026-06-16 指派方: [email protected] 來源: [email protected]

結論預警: CVE-2016-9879 綜合評估為中等風險(55.2/100):CVSS 技術影響為高級,利用機率(EPSS 1.40%) 核心證據: 近一日 EPSS 上升 +1.08%,被利用關注度持續升高。 強制指令: 梳理受影響資產並納入修補計畫。

風險隨態勢動態變化;本站持續評估並同步更新本頁展示內容。

CVE-2016-9879 的 EPSS(利用預測評分)

EPSS 日更估計相對被利用可能性;百分位表示該 CVE 在已評分漏洞中的相對排名(越高表示相對更嚴重)。

# 日期 舊 EPSS 分數 新 EPSS 分數 變化(新 − 舊)
1 2026-06-15 0.32% 1.40% +1.08%
2 2025-03-30 1.10% 0.32% -0.78%
3 2025-03-29 1.10%

完整 EPSS 歷史 (共 6 筆)

CVE-2016-9879 的 CVSS 指標

該 CVE 的 CVSS 指標。

底座分 版本 嚴重度 向量 可利用性 影響 分數來源
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N 點擊展開
攻擊向量 (AV:N)
可經網際網路或企業內可路由網段從遠端觸達,攻擊者不必在裝置旁邊。
攻擊複雜度 (AC:L)
前置條件清楚,成功路徑穩定,不必仰賴罕見競態或極端環境。
權限需求 (PR:N)
不必事先登入或提權,匿名工作階段也可能成為跳板。
使用者互動 (UI:N)
不必受害者點連結、放行巨集或安裝軟體,攻擊鏈可自動走完。
作用域 (S:U)
破壞局限在脆弱元件原本的安全權限與信任域之內。
機密性影響 (C:N)
幾乎談不上實質的敏感資料外洩。
完整性影響 (I:H)
可竄改稽核紀錄、植入後門或大面積偽造業務資料,動搖信任根基。
可用性影響 (A:N)
不至於造成業務意義上的長時間停擺或災難性效能崩塌。
3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N 點擊展開
存取路徑 (AV:N)
只要路由可達,即可從遠端發動利用。
存取複雜度 (AC:L)
步驟短、路徑清楚,重現成本低。
認證 (AU:N)
全程無需有效身分。
機密性影響 (C:N)
對機密性無影響。
完整性影響 (I:P)
完整性受到部分損害。
可用性影響 (A:N)
對可用性無影響。
10.0 2.9 [email protected]

CVE-2016-9879 的弱點列舉

CVE-2016-9879 的 GitHub 安全公告

GHSA-v35c-49j6-q8hq · 嚴重度: high · 生態: maven — Security Constraint Bypass in Spring Security

CVE-2016-9879 的 OS 追蹤

vendor priority summary link
redhat medium https://access.redhat.com/security/cve/CVE-2016-9879

CVE-2016-9879 的影響軟體 / 設定

廠商 產品 版本 原始 CPE
vmware spring_security 3.2.0 cpe:2.3:a:vmware:spring_security:3.2.0:*:*:*:*:*:*:*
vmware spring_security 3.2.1 cpe:2.3:a:vmware:spring_security:3.2.1:*:*:*:*:*:*:*
vmware spring_security 3.2.2 cpe:2.3:a:vmware:spring_security:3.2.2:*:*:*:*:*:*:*
vmware spring_security 3.2.3 cpe:2.3:a:vmware:spring_security:3.2.3:*:*:*:*:*:*:*
vmware spring_security 3.2.4 cpe:2.3:a:vmware:spring_security:3.2.4:*:*:*:*:*:*:*
vmware spring_security 3.2.5 cpe:2.3:a:vmware:spring_security:3.2.5:*:*:*:*:*:*:*
vmware spring_security 3.2.6 cpe:2.3:a:vmware:spring_security:3.2.6:*:*:*:*:*:*:*
vmware spring_security 3.2.7 cpe:2.3:a:vmware:spring_security:3.2.7:*:*:*:*:*:*:*
vmware spring_security 3.2.8 cpe:2.3:a:vmware:spring_security:3.2.8:*:*:*:*:*:*:*
vmware spring_security 3.2.9 cpe:2.3:a:vmware:spring_security:3.2.9:*:*:*:*:*:*:*
vmware spring_security 4.1.0 cpe:2.3:a:vmware:spring_security:4.1.0:*:*:*:*:*:*:*
vmware spring_security 4.1.1 cpe:2.3:a:vmware:spring_security:4.1.1:*:*:*:*:*:*:*
vmware spring_security 4.1.2 cpe:2.3:a:vmware:spring_security:4.1.2:*:*:*:*:*:*:*
vmware spring_security 4.1.3 cpe:2.3:a:vmware:spring_security:4.1.3:*:*:*:*:*:*:*
vmware spring_security 4.2.0 cpe:2.3:a:vmware:spring_security:4.2.0:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.0.0 cpe:2.3:a:ibm:websphere_application_server:8.5.0.0:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.0.1 cpe:2.3:a:ibm:websphere_application_server:8.5.0.1:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.0.2 cpe:2.3:a:ibm:websphere_application_server:8.5.0.2:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.0 cpe:2.3:a:ibm:websphere_application_server:8.5.5.0:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.1 cpe:2.3:a:ibm:websphere_application_server:8.5.5.1:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.2 cpe:2.3:a:ibm:websphere_application_server:8.5.5.2:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.3 cpe:2.3:a:ibm:websphere_application_server:8.5.5.3:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.4 cpe:2.3:a:ibm:websphere_application_server:8.5.5.4:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.5 cpe:2.3:a:ibm:websphere_application_server:8.5.5.5:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.6 cpe:2.3:a:ibm:websphere_application_server:8.5.5.6:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.7 cpe:2.3:a:ibm:websphere_application_server:8.5.5.7:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.8 cpe:2.3:a:ibm:websphere_application_server:8.5.5.8:*:*:*:*:*:*:*
ibm websphere_application_server 8.5.5.9 cpe:2.3:a:ibm:websphere_application_server:8.5.5.9:*:*:*:*:*:*:*

CVE-2016-9879 的參考連結

cvelogic Threat Intelligence