# CVE-2012-5483: Information disclosure in n/a

> Local attackers can read world-readable EC2 credentials from Keystone configuration files to gain unauthorized access to Amazon EC2 services.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8cx8-xmvm-66wj, RHSA-2012:1556

## What is CVE-2012-5483?

CVE-2012-5483 is a low-severity vulnerability in n/a, published on 26 Dec 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2012-5483?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-keystone` | Red Hat:openstack:1::el6 | All versions | 0:2012.1.3-3.el6 |
| `openstack-keystone-doc` | Red Hat:openstack:1::el6 | All versions | 0:2012.1.3-3.el6 |
| `python-keystone` | Red Hat:openstack:1::el6 | All versions | 0:2012.1.3-3.el6 |
| `python-keystone-auth-token` | Red Hat:openstack:1::el6 | All versions | 0:2012.1.3-3.el6 |

Products: Openstack Keystone.

## How do I fix CVE-2012-5483?

Apply the vendor's patch.

## Is CVE-2012-5483 being exploited?

There is no known exploitation of CVE-2012-5483 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-12690](https://insights.sbomify.com/CVE-2020-12690/): Insufficient Session Expiration in OpenStack Keystone (high 8.8)
- [CVE-2019-19687](https://insights.sbomify.com/CVE-2019-19687/): OpenStack Keystone Credential Leakage (high 8.8)
- [CVE-2026-43001](https://insights.sbomify.com/CVE-2026-43001/): OpenStack Keystone has an Incorrect Authorization Issue (high 7.9)
- [CVE-2014-2828](https://insights.sbomify.com/CVE-2014-2828/): OpenStack Identity (Keystone) DoS through V3 API authentication chaining (high 7.8)
- [CVE-2021-38155](https://insights.sbomify.com/CVE-2021-38155/): OpenStack Keystone allows information disclosure during account locking (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5483 and fix it if it is affected.

What it is: CVE-2012-5483 is a low-severity vulnerability in n/a, published on 26 Dec 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-5483 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-5483/ (Markdown: https://insights.sbomify.com/CVE-2012-5483/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-5483
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-5483
- OSV: https://osv.dev/vulnerability/CVE-2012-5483

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-5483/
Summaries are generated and may contain mistakes; the official description above is the record.