Skip to content
Fencer Intel
low 2.1

CVE-2012-6117 json

Aeolus Configuration Server, as used in Red Hat CloudForms Cloud Engine before 1.1.2, uses world-readable permissions for /var/log/aeolus-c…

published 2013-03-12 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5984

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits
0
none known

Summary

Aeolus Configuration Server, as used in Red Hat CloudForms Cloud Engine before 1.1.2, uses world-readable permissions for /var/log/aeolus-configserver/configserver.log, which allows local users to read plaintext passwords by reading the log file.

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-6117 updated cvss 2.1

Configserver: Passwords from application blueprint stored plaintext in configserver.log

  • Red Hat CloudForms Cloud Engine for RHEL 6 Server oz 0.8.0-8.el6cf, aeolus-all 0.13.26-1.el6cf, imagefactory 1.0.3-1.el6cf, aeolus-conductor 0.13.26-1.el6cf, aeolus-configserver 0.4.12-3.el6cf, aeolus-conductor-daemons 0.13.26-1.el6cf, +2 more
    fixed: vendor fix RHSA-2013:0545

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

0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=875294 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

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.