CVE-2012-3366 json
The Trigger plugin in bcfg2 1.2.x before 1.2.3 allows remote attackers with root access to the client to execute arbitrary commands via she…
published 2012-07-03 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-3340
- cvss
- 9.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
The Trigger plugin in bcfg2 1.2.x before 1.2.3 allows remote attackers with root access to the client to execute arbitrary commands via shell metacharacters in the UUID field to the server process (bcfg2-server).
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-3366 updated cvss 6.0
bcfg2: arbitrary code execution flaw in Trigger plugin
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.78% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
github.com
/Bcfg2/bcfg2/commit/a524967e8d5c4c22e49cd619aed20c87a316c0be
patch
-
debian.org
/security/2012/dsa-2503
vendor-advisory
-
secunia.com
/advisories/49690
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/49629
third-party-advisory, vendor-advisory
-
permalink.gmane.org
/gmane.comp.sysutils.bcfg2.devel/4539
mailing-list
-
securityfocus.com
/bid/54217
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/76616
vdb-entry
Sources
- CVE List CVE-2012-3366
- NVD CVE-2012-3366
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.