CVE-2011-3872

Puppet 2.6.x before 2.6.12 and 2.7.x before 2.7.6, and Puppet Enterprise (PE) Users 1.0, 1.1, and 1.2 before 1.2.4, when signing an agent certificate, adds the Puppet master's certdnsnames values to the X.509 Subject Alternative Name field of the certificate, which allows remote attackers to spoof a Puppet master via a man-in-the-middle (MITM) attack against an agent that uses an alternate DNS name for the master, aka "AltNames Vulnerability."

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

結論預警: CVE-2011-3872 綜合評估為低風險(39.2/100):CVSS 技術影響為低級,利用機率(EPSS 2.45%) 強制指令: 持續追蹤利用情報與 EPSS 變化,並適時複評優先級。

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

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

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

# 日期 舊 EPSS 分數 新 EPSS 分數 變化(新 − 舊)
1 2026-06-26 2.43% 2.45% +0.02%
2 2026-06-15 2.78% 2.43% -0.34%
3 2025-03-30 2.78%

完整 EPSS 歷史 (共 12 筆)

CVE-2011-3872 的 CVSS 指標

該 CVE 的 CVSS 指標。

底座分 版本 嚴重度 向量 可利用性 影響 分數來源
2.6 2.0 LOW
AV:N/AC:H/Au:N/C:N/I:P/A:N 點擊展開
存取路徑 (AV:N)
只要路由可達,即可從遠端發動利用。
存取複雜度 (AC:H)
依賴罕見組態或苛刻時機,實戰命中機率低。
認證 (AU:N)
全程無需有效身分。
機密性影響 (C:N)
對機密性無影響。
完整性影響 (I:P)
完整性受到部分損害。
可用性影響 (A:N)
對可用性無影響。
4.9 2.9 [email protected]

CVE-2011-3872 的弱點列舉

CVE-2011-3872 的 OS 追蹤

vendor priority summary link
debian not yet assigned CVE-2011-3872 not yet assigned priority: Debian including 1 source packages (puppet), 1 status rows across 1 suites (bullseye): resolved 1. https://security-tracker.debian.org/tracker/CVE-2011-3872
gentoo high CVE-2011-3872: 1 GLSA(s) (201203-03), 1 atom(s) (app-admin/puppet); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2011-3872
redhat high https://access.redhat.com/security/cve/CVE-2011-3872
ubuntu high CVE-2011-3872 high priority: Ubuntu including 1 source packages (puppet), 6 status rows across 6 suites (hardy, lucid, maverick, natty, oneiric, upstream): released 5, ignored 1. https://ubuntu.com/security/CVE-2011-3872

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

廠商 產品 版本 原始 CPE
puppet puppet 2.6.0 cpe:2.3:a:puppet:puppet:2.6.0:*:*:*:*:*:*:*
puppet puppet 2.6.1 cpe:2.3:a:puppet:puppet:2.6.1:*:*:*:*:*:*:*
puppet puppet 2.6.2 cpe:2.3:a:puppet:puppet:2.6.2:*:*:*:*:*:*:*
puppet puppet 2.6.3 cpe:2.3:a:puppet:puppet:2.6.3:*:*:*:*:*:*:*
puppet puppet 2.6.4 cpe:2.3:a:puppet:puppet:2.6.4:*:*:*:*:*:*:*
puppet puppet 2.6.5 cpe:2.3:a:puppet:puppet:2.6.5:*:*:*:*:*:*:*
puppet puppet 2.6.6 cpe:2.3:a:puppet:puppet:2.6.6:*:*:*:*:*:*:*
puppet puppet 2.6.7 cpe:2.3:a:puppet:puppet:2.6.7:*:*:*:*:*:*:*
puppet puppet 2.6.8 cpe:2.3:a:puppet:puppet:2.6.8:*:*:*:*:*:*:*
puppet puppet 2.6.9 cpe:2.3:a:puppet:puppet:2.6.9:*:*:*:*:*:*:*
puppet puppet 2.6.10 cpe:2.3:a:puppet:puppet:2.6.10:*:*:*:*:*:*:*
puppet puppet 2.6.11 cpe:2.3:a:puppet:puppet:2.6.11:*:*:*:*:*:*:*
puppet puppet 2.7.2 cpe:2.3:a:puppet:puppet:2.7.2:*:*:*:*:*:*:*
puppet puppet 2.7.3 cpe:2.3:a:puppet:puppet:2.7.3:*:*:*:*:*:*:*
puppet puppet 2.7.4 cpe:2.3:a:puppet:puppet:2.7.4:*:*:*:*:*:*:*
puppet puppet 2.7.5 cpe:2.3:a:puppet:puppet:2.7.5:*:*:*:*:*:*:*
puppetlabs puppet 2.7.0 cpe:2.3:a:puppetlabs:puppet:2.7.0:*:*:*:*:*:*:*
puppetlabs puppet 2.7.1 cpe:2.3:a:puppetlabs:puppet:2.7.1:*:*:*:*:*:*:*
puppet puppet_enterprise 1.2.0 cpe:2.3:a:puppet:puppet_enterprise:1.2.0:*:*:*:*:*:*:*
puppet puppet_enterprise 1.2.1 cpe:2.3:a:puppet:puppet_enterprise:1.2.1:*:*:*:*:*:*:*
puppet puppet_enterprise 1.2.2 cpe:2.3:a:puppet:puppet_enterprise:1.2.2:*:*:*:*:*:*:*
puppet puppet_enterprise 1.2.3 cpe:2.3:a:puppet:puppet_enterprise:1.2.3:*:*:*:*:*:*:*
puppetlabs puppet_enterprise_users 1.0 cpe:2.3:a:puppetlabs:puppet_enterprise_users:1.0:*:*:*:*:*:*:*
puppetlabs puppet_enterprise_users 1.1 cpe:2.3:a:puppetlabs:puppet_enterprise_users:1.1:*:*:*:*:*:*:*

CVE-2011-3872 的參考連結

cvelogic Threat Intelligence