CVE-2011-3200

Stack-based buffer overflow in the parseLegacySyslogMsg function in tools/syslogd.c in rsyslogd in rsyslog 4.6.x before 4.6.8 and 5.2.0 through 5.8.4 might allow remote attackers to cause a denial of service (application exit) via a long TAG in a legacy syslog message.

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

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

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

CVE-2011-3200 的 EPSS(利用預測評分)

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

# 日期 舊 EPSS 分數 新 EPSS 分數 變化(新 − 舊)
1 2026-06-15 65.08% 20.76% -44.32%
2 2026-06-13 63.91% 65.08% +1.17%
3 2026-05-16 63.91%

完整 EPSS 歷史 (共 14 筆)

CVE-2011-3200 的 CVSS 指標

該 CVE 的 CVSS 指標。

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

CVE-2011-3200 的弱點列舉

CVE-2011-3200 的 OS 追蹤

vendor priority summary link
debian low CVE-2011-3200 low priority: Debian including 1 source packages (rsyslog), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2011-3200
redhat medium https://access.redhat.com/security/cve/CVE-2011-3200
suse medium CVE-2011-3200 severity moderate: SUSE including 129 source package names (rsyslog-5.10.1-0.11.1, rsyslog-5.10.1-0.7.49, …), 166 product×package rows across 23 product lines (SUSE Linux Enterprise Desktop 12, SUSE Linux Enterprise Desktop 12 SP1, … (23 product lines)): Fixed 166. https://www.suse.com/security/cve/CVE-2011-3200/
ubuntu low CVE-2011-3200 low priority: Ubuntu including 1 source packages (rsyslog), 5 status rows across 5 suites (hardy, lucid, maverick, natty, upstream): not-affected 3, released 2. https://ubuntu.com/security/CVE-2011-3200

CVE-2011-3200 的影響軟體 / 設定

廠商 產品 版本 原始 CPE
rsyslog rsyslog 4.6.0 cpe:2.3:a:rsyslog:rsyslog:4.6.0:*:*:*:*:*:*:*
rsyslog rsyslog 4.6.1 cpe:2.3:a:rsyslog:rsyslog:4.6.1:*:*:*:*:*:*:*
rsyslog rsyslog 4.6.2 cpe:2.3:a:rsyslog:rsyslog:4.6.2:*:*:*:*:*:*:*
rsyslog rsyslog 4.6.3 cpe:2.3:a:rsyslog:rsyslog:4.6.3:*:*:*:*:*:*:*
rsyslog rsyslog 4.6.4 cpe:2.3:a:rsyslog:rsyslog:4.6.4:*:*:*:*:*:*:*
rsyslog rsyslog 4.6.5 cpe:2.3:a:rsyslog:rsyslog:4.6.5:*:*:*:*:*:*:*
rsyslog rsyslog 4.6.6 cpe:2.3:a:rsyslog:rsyslog:4.6.6:*:*:*:*:*:*:*
rsyslog rsyslog 4.6.7 cpe:2.3:a:rsyslog:rsyslog:4.6.7:*:*:*:*:*:*:*
rsyslog rsyslog 5.2.0 cpe:2.3:a:rsyslog:rsyslog:5.2.0:*:*:*:*:*:*:*
rsyslog rsyslog 5.2.1 cpe:2.3:a:rsyslog:rsyslog:5.2.1:*:*:*:*:*:*:*
rsyslog rsyslog 5.2.2 cpe:2.3:a:rsyslog:rsyslog:5.2.2:*:*:*:*:*:*:*
rsyslog rsyslog 5.3.1 cpe:2.3:a:rsyslog:rsyslog:5.3.1:*:*:*:*:*:*:*
rsyslog rsyslog 5.3.2 cpe:2.3:a:rsyslog:rsyslog:5.3.2:*:*:*:*:*:*:*
rsyslog rsyslog 5.3.3 cpe:2.3:a:rsyslog:rsyslog:5.3.3:*:*:*:*:*:*:*
rsyslog rsyslog 5.3.4 cpe:2.3:a:rsyslog:rsyslog:5.3.4:*:*:*:*:*:*:*
rsyslog rsyslog 5.3.5 cpe:2.3:a:rsyslog:rsyslog:5.3.5:*:*:*:*:*:*:*
rsyslog rsyslog 5.3.6 cpe:2.3:a:rsyslog:rsyslog:5.3.6:*:*:*:*:*:*:*
rsyslog rsyslog 5.3.7 cpe:2.3:a:rsyslog:rsyslog:5.3.7:*:*:*:*:*:*:*
rsyslog rsyslog 5.4.0 cpe:2.3:a:rsyslog:rsyslog:5.4.0:*:*:*:*:*:*:*
rsyslog rsyslog 5.4.1 cpe:2.3:a:rsyslog:rsyslog:5.4.1:*:*:*:*:*:*:*
rsyslog rsyslog 5.4.2 cpe:2.3:a:rsyslog:rsyslog:5.4.2:*:*:*:*:*:*:*
rsyslog rsyslog 5.5.0 cpe:2.3:a:rsyslog:rsyslog:5.5.0:*:*:*:*:*:*:*
rsyslog rsyslog 5.5.1 cpe:2.3:a:rsyslog:rsyslog:5.5.1:*:*:*:*:*:*:*
rsyslog rsyslog 5.5.2 cpe:2.3:a:rsyslog:rsyslog:5.5.2:*:*:*:*:*:*:*
rsyslog rsyslog 5.5.3 cpe:2.3:a:rsyslog:rsyslog:5.5.3:*:*:*:*:*:*:*
rsyslog rsyslog 5.5.4 cpe:2.3:a:rsyslog:rsyslog:5.5.4:*:*:*:*:*:*:*
rsyslog rsyslog 5.5.5 cpe:2.3:a:rsyslog:rsyslog:5.5.5:*:*:*:*:*:*:*
rsyslog rsyslog 5.5.6 cpe:2.3:a:rsyslog:rsyslog:5.5.6:*:*:*:*:*:*:*
rsyslog rsyslog 5.5.7 cpe:2.3:a:rsyslog:rsyslog:5.5.7:*:*:*:*:*:*:*
rsyslog rsyslog 5.6.0 cpe:2.3:a:rsyslog:rsyslog:5.6.0:*:*:*:*:*:*:*
rsyslog rsyslog 5.6.1 cpe:2.3:a:rsyslog:rsyslog:5.6.1:*:*:*:*:*:*:*
rsyslog rsyslog 5.6.2 cpe:2.3:a:rsyslog:rsyslog:5.6.2:*:*:*:*:*:*:*
rsyslog rsyslog 5.6.3 cpe:2.3:a:rsyslog:rsyslog:5.6.3:*:*:*:*:*:*:*
rsyslog rsyslog 5.6.4 cpe:2.3:a:rsyslog:rsyslog:5.6.4:*:*:*:*:*:*:*
rsyslog rsyslog 5.6.5 cpe:2.3:a:rsyslog:rsyslog:5.6.5:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.0 cpe:2.3:a:rsyslog:rsyslog:5.7.0:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.1 cpe:2.3:a:rsyslog:rsyslog:5.7.1:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.2 cpe:2.3:a:rsyslog:rsyslog:5.7.2:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.3 cpe:2.3:a:rsyslog:rsyslog:5.7.3:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.4 cpe:2.3:a:rsyslog:rsyslog:5.7.4:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.5 cpe:2.3:a:rsyslog:rsyslog:5.7.5:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.6 cpe:2.3:a:rsyslog:rsyslog:5.7.6:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.7 cpe:2.3:a:rsyslog:rsyslog:5.7.7:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.8 cpe:2.3:a:rsyslog:rsyslog:5.7.8:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.9 cpe:2.3:a:rsyslog:rsyslog:5.7.9:*:*:*:*:*:*:*
rsyslog rsyslog 5.7.10 cpe:2.3:a:rsyslog:rsyslog:5.7.10:*:*:*:*:*:*:*
rsyslog rsyslog 5.8.0 cpe:2.3:a:rsyslog:rsyslog:5.8.0:*:*:*:*:*:*:*
rsyslog rsyslog 5.8.1 cpe:2.3:a:rsyslog:rsyslog:5.8.1:*:*:*:*:*:*:*
rsyslog rsyslog 5.8.2 cpe:2.3:a:rsyslog:rsyslog:5.8.2:*:*:*:*:*:*:*
rsyslog rsyslog 5.8.3 cpe:2.3:a:rsyslog:rsyslog:5.8.3:*:*:*:*:*:*:*
rsyslog rsyslog 5.8.4 cpe:2.3:a:rsyslog:rsyslog:5.8.4:*:*:*:*:*:*:*

CVE-2011-3200 的參考連結

cvelogic Threat Intelligence