CVE-2014-9472

The email gateway in RT (aka Request Tracker) 3.0.0 through 4.x before 4.0.23 and 4.2.x before 4.2.10 allows remote attackers to cause a denial of service (CPU and disk consumption) via a crafted email.

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

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

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

CVE-2014-9472 的 EPSS(利用預測評分)

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

# 日期 舊 EPSS 分數 新 EPSS 分數 變化(新 − 舊)
1 2026-06-15 0.86% 2.84% +1.98%
2 2025-03-30 1.48% 0.86% -0.62%
3 2025-03-29 1.48%

完整 EPSS 歷史 (共 7 筆)

CVE-2014-9472 的 CVSS 指標

該 CVE 的 CVSS 指標。

底座分 版本 嚴重度 向量 可利用性 影響 分數來源
7.1 2.0 HIGH
AV:N/AC:M/Au:N/C:N/I:N/A:C 點擊展開
存取路徑 (AV:N)
只要路由可達,即可從遠端發動利用。
存取複雜度 (AC:M)
需要若干有利條件,但不必「千年一遇」。
認證 (AU:N)
全程無需有效身分。
機密性影響 (C:N)
對機密性無影響。
完整性影響 (I:N)
對完整性無影響。
可用性影響 (A:C)
可用性被完全破壞。
8.6 6.9 [email protected]

CVE-2014-9472 的弱點列舉

CVE-2014-9472 的 OS 追蹤

vendor priority summary link
debian not yet assigned CVE-2014-9472 not yet assigned priority: Debian including 1 source packages (request-tracker4), 2 status rows across 2 suites (bookworm, bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2014-9472
ubuntu medium CVE-2014-9472 medium priority: Ubuntu including 2 source packages (request-tracker3.8, request-tracker4), 28 status rows across 14 suites (artful, bionic, cosmic, disco, lucid, precise, trusty, upstream, utopic, vivid, wily, xenial, yakkety, zesty): DNE 13, not-affected 9, ignored 4, needs-triage 1, released 1. https://ubuntu.com/security/CVE-2014-9472

CVE-2014-9472 的影響軟體 / 設定

廠商 產品 版本 原始 CPE
debian debian_linux 7.0 cpe:2.3:o:debian:debian_linux:7.0:*:*:*:*:*:*:*
fedoraproject fedora 21 cpe:2.3:o:fedoraproject:fedora:21:*:*:*:*:*:*:*
fedoraproject fedora 22 cpe:2.3:o:fedoraproject:fedora:22:*:*:*:*:*:*:*
bestpractical request_tracker 3.6.8 cpe:2.3:a:bestpractical:request_tracker:3.6.8:*:*:*:*:*:*:*
bestpractical request_tracker 3.6.10 cpe:2.3:a:bestpractical:request_tracker:3.6.10:*:*:*:*:*:*:*
bestpractical request_tracker 3.6.11 cpe:2.3:a:bestpractical:request_tracker:3.6.11:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.3 cpe:2.3:a:bestpractical:request_tracker:3.8.3:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.4 cpe:2.3:a:bestpractical:request_tracker:3.8.4:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.7 cpe:2.3:a:bestpractical:request_tracker:3.8.7:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.9 cpe:2.3:a:bestpractical:request_tracker:3.8.9:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.10 cpe:2.3:a:bestpractical:request_tracker:3.8.10:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.11 cpe:2.3:a:bestpractical:request_tracker:3.8.11:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.12 cpe:2.3:a:bestpractical:request_tracker:3.8.12:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.13 cpe:2.3:a:bestpractical:request_tracker:3.8.13:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.14 cpe:2.3:a:bestpractical:request_tracker:3.8.14:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.15 cpe:2.3:a:bestpractical:request_tracker:3.8.15:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.16 cpe:2.3:a:bestpractical:request_tracker:3.8.16:*:*:*:*:*:*:*
bestpractical request_tracker 3.8.17 cpe:2.3:a:bestpractical:request_tracker:3.8.17:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.0 cpe:2.3:a:bestpractical:request_tracker:4.0.0:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.1 cpe:2.3:a:bestpractical:request_tracker:4.0.1:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.2 cpe:2.3:a:bestpractical:request_tracker:4.0.2:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.3 cpe:2.3:a:bestpractical:request_tracker:4.0.3:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.4 cpe:2.3:a:bestpractical:request_tracker:4.0.4:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.5 cpe:2.3:a:bestpractical:request_tracker:4.0.5:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.6 cpe:2.3:a:bestpractical:request_tracker:4.0.6:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.7 cpe:2.3:a:bestpractical:request_tracker:4.0.7:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.8 cpe:2.3:a:bestpractical:request_tracker:4.0.8:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.9 cpe:2.3:a:bestpractical:request_tracker:4.0.9:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.10 cpe:2.3:a:bestpractical:request_tracker:4.0.10:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.11 cpe:2.3:a:bestpractical:request_tracker:4.0.11:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.12 cpe:2.3:a:bestpractical:request_tracker:4.0.12:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.13 cpe:2.3:a:bestpractical:request_tracker:4.0.13:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.14 cpe:2.3:a:bestpractical:request_tracker:4.0.14:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.15 cpe:2.3:a:bestpractical:request_tracker:4.0.15:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.16 cpe:2.3:a:bestpractical:request_tracker:4.0.16:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.17 cpe:2.3:a:bestpractical:request_tracker:4.0.17:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.18 cpe:2.3:a:bestpractical:request_tracker:4.0.18:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.19 cpe:2.3:a:bestpractical:request_tracker:4.0.19:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.20 cpe:2.3:a:bestpractical:request_tracker:4.0.20:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.21 cpe:2.3:a:bestpractical:request_tracker:4.0.21:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.22 cpe:2.3:a:bestpractical:request_tracker:4.0.22:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.0 cpe:2.3:a:bestpractical:request_tracker:4.2.0:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.1 cpe:2.3:a:bestpractical:request_tracker:4.2.1:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.2 cpe:2.3:a:bestpractical:request_tracker:4.2.2:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.3 cpe:2.3:a:bestpractical:request_tracker:4.2.3:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.4 cpe:2.3:a:bestpractical:request_tracker:4.2.4:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.5 cpe:2.3:a:bestpractical:request_tracker:4.2.5:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.6 cpe:2.3:a:bestpractical:request_tracker:4.2.6:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.7 cpe:2.3:a:bestpractical:request_tracker:4.2.7:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.8 cpe:2.3:a:bestpractical:request_tracker:4.2.8:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.9 cpe:2.3:a:bestpractical:request_tracker:4.2.9:*:*:*:*:*:*:*

CVE-2014-9472 的參考連結

cvelogic Threat Intelligence