CVE-2012-5483 json
tools/sample_data.sh in OpenStack Keystone 2012.1.3, when access to Amazon Elastic Compute Cloud (Amazon EC2) is configured, uses world-rea…
published 2012-12-26 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5400
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
tools/sample_data.sh in OpenStack Keystone 2012.1.3, when access to Amazon Elastic Compute Cloud (Amazon EC2) is configured, uses world-readable permissions for /etc/keystone/ec2rc, which allows local users to obtain access to EC2 services by reading administrative access and secret values from this file.
Patch / fix
- openstack-keystone openstack 1 2012.1.3-3.el6
- python-keystone openstack 1 2012.1.3-3.el6
- python-keystone-auth-token openstack 1 2012.1.3-3.el6
red hat advisories RHSA-2012:1556
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-5483 updated cvss 2.1
OpenStack: Keystone /etc/keystone/ec2rc secret key exposure
-
Red Hat RHOS Essex Release python-keystone 2012.1.3-3.el6, openstack-keystone 2012.1.3-3.el6, python-keystone-auth-token 2012.1.3-3.el6fixed: vendor fix RHSA-2012:1556
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.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
- CVE List CVE-2012-5483
- NVD CVE-2012-5483
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.