CVE-2012-0802

Multiple buffer overflows in Spamdyke before 4.3.0 might allow remote attackers to execute arbitrary code via vectors related to "serious errors in the usage of snprintf()/vsnprintf()" in which the return values may be larger than the size of the buffer.

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

結論預警: CVE-2012-0802 綜合評估為中等風險(60.5/100):CVSS 技術影響為高級,利用機率偏高(EPSS 4.57%,百分位 90%) 核心證據: EPSS 顯示該漏洞近期被利用的可能性處於高位。 強制指令: 被利用機率偏高—請盤點暴露面並優先安排修補。

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

CVE-2012-0802 的 EPSS(利用預測評分)

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

# 日期 舊 EPSS 分數 新 EPSS 分數 變化(新 − 舊)
1 2026-06-15 5.75% 4.57% -1.17%
2 2025-03-30 7.03% 5.75% -1.29%
3 2025-03-29 7.03%

完整 EPSS 歷史 (共 17 筆)

CVE-2012-0802 的 CVSS 指標

該 CVE 的 CVSS 指標。

底座分 版本 嚴重度 向量 可利用性 影響 分數來源
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P 點擊展開
存取路徑 (AV:N)
只要路由可達,即可從遠端發動利用。
存取複雜度 (AC:L)
步驟短、路徑清楚,重現成本低。
認證 (AU:N)
全程無需有效身分。
機密性影響 (C:P)
機密性受到部分損害。
完整性影響 (I:P)
完整性受到部分損害。
可用性影響 (A:P)
可用性受到部分損害。
10.0 6.4 [email protected]

CVE-2012-0802 的弱點列舉

CVE-2012-0802 的 OS 追蹤

vendor priority summary link
gentoo high CVE-2012-0802: 1 GLSA(s) (201203-01), 1 atom(s) (mail-filter/spamdyke); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2012-0802

CVE-2012-0802 的影響軟體 / 設定

廠商 產品 版本 原始 CPE
spamdyke spamdyke <= 4.2.1 cpe:2.3:a:spamdyke:spamdyke:*:*:*:*:*:*:*:*
spamdyke spamdyke 3.0.0 cpe:2.3:a:spamdyke:spamdyke:3.0.0:*:*:*:*:*:*:*
spamdyke spamdyke 3.0.1 cpe:2.3:a:spamdyke:spamdyke:3.0.1:*:*:*:*:*:*:*
spamdyke spamdyke 3.1.0 cpe:2.3:a:spamdyke:spamdyke:3.1.0:*:*:*:*:*:*:*
spamdyke spamdyke 3.1.1 cpe:2.3:a:spamdyke:spamdyke:3.1.1:*:*:*:*:*:*:*
spamdyke spamdyke 3.1.2 cpe:2.3:a:spamdyke:spamdyke:3.1.2:*:*:*:*:*:*:*
spamdyke spamdyke 3.1.3 cpe:2.3:a:spamdyke:spamdyke:3.1.3:*:*:*:*:*:*:*
spamdyke spamdyke 3.1.4 cpe:2.3:a:spamdyke:spamdyke:3.1.4:*:*:*:*:*:*:*
spamdyke spamdyke 3.1.5 cpe:2.3:a:spamdyke:spamdyke:3.1.5:*:*:*:*:*:*:*
spamdyke spamdyke 3.1.6 cpe:2.3:a:spamdyke:spamdyke:3.1.6:*:*:*:*:*:*:*
spamdyke spamdyke 3.1.7 cpe:2.3:a:spamdyke:spamdyke:3.1.7:*:*:*:*:*:*:*
spamdyke spamdyke 3.1.8 cpe:2.3:a:spamdyke:spamdyke:3.1.8:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.0 cpe:2.3:a:spamdyke:spamdyke:4.0.0:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.0 cpe:2.3:a:spamdyke:spamdyke:4.0.0:beta1:*:*:*:*:*:*
spamdyke spamdyke 4.0.0 cpe:2.3:a:spamdyke:spamdyke:4.0.0:beta2:*:*:*:*:*:*
spamdyke spamdyke 4.0.0 cpe:2.3:a:spamdyke:spamdyke:4.0.0:beta3:*:*:*:*:*:*
spamdyke spamdyke 4.0.0 cpe:2.3:a:spamdyke:spamdyke:4.0.0:rc1:*:*:*:*:*:*
spamdyke spamdyke 4.0.1 cpe:2.3:a:spamdyke:spamdyke:4.0.1:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.2 cpe:2.3:a:spamdyke:spamdyke:4.0.2:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.3 cpe:2.3:a:spamdyke:spamdyke:4.0.3:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.4 cpe:2.3:a:spamdyke:spamdyke:4.0.4:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.5 cpe:2.3:a:spamdyke:spamdyke:4.0.5:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.5 cpe:2.3:a:spamdyke:spamdyke:4.0.5:beta1:*:*:*:*:*:*
spamdyke spamdyke 4.0.5 cpe:2.3:a:spamdyke:spamdyke:4.0.5:beta2:*:*:*:*:*:*
spamdyke spamdyke 4.0.5 cpe:2.3:a:spamdyke:spamdyke:4.0.5:beta3:*:*:*:*:*:*
spamdyke spamdyke 4.0.5 cpe:2.3:a:spamdyke:spamdyke:4.0.5:beta4:*:*:*:*:*:*
spamdyke spamdyke 4.0.6 cpe:2.3:a:spamdyke:spamdyke:4.0.6:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.7 cpe:2.3:a:spamdyke:spamdyke:4.0.7:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.8 cpe:2.3:a:spamdyke:spamdyke:4.0.8:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.9 cpe:2.3:a:spamdyke:spamdyke:4.0.9:*:*:*:*:*:*:*
spamdyke spamdyke 4.0.10 cpe:2.3:a:spamdyke:spamdyke:4.0.10:*:*:*:*:*:*:*
spamdyke spamdyke 4.1.0 cpe:2.3:a:spamdyke:spamdyke:4.1.0:*:*:*:*:*:*:*
spamdyke spamdyke 4.2.0 cpe:2.3:a:spamdyke:spamdyke:4.2.0:*:*:*:*:*:*:*

CVE-2012-0802 的參考連結

cvelogic Threat Intelligence