# CVE-2013-0212: OpenStack Glance logs user name and password in cleartext

> Authenticated users can obtain Swift credentials from logs when the endpoint is misconfigured in single tenant mode.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-0212, GHSA-xv7j-2v4w-cjvh, RHSA-2013:0209

## What is CVE-2013-0212?

CVE-2013-0212 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 24 Feb 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

store/swift.py in OpenStack Glance Essex (2012.1), Folsom (2012.2) before 2012.2.3, and Grizzly, when in Swift single tenant mode, logs the Swift endpoint's user name and password in cleartext when the endpoint is misconfigured or unusable, allows remote authenticated users to obtain sensitive information by reading the error messages.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-0212?

2 open source packages ship an affected version, including glance. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glance` | PyPI | From 2012.1 | 2012.2.3 |
| `glance` | PyPI | From 2012.1 | 2012.2.3 |
| `openstack-glance` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.1-4.el6ost |
| `openstack-glance-doc` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.1-4.el6ost |
| `python-glance` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.1-4.el6ost |

Products: Canonical Ubuntu Linux, Openstack Image Registry and Delivery Service \(Glance\).

## How do I fix CVE-2013-0212?

Upgrade glance to 2012.2.3 or later.

## Is CVE-2013-0212 being exploited?

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

Public exploit code:

- https://github.com/LogSec/CVE-2013-0212 (github_poc): https://github.com/LogSec/CVE-2013-0212

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0212 and fix it if it is affected.

What it is: CVE-2013-0212 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 24 Feb 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0212 in the wild and no public exploit code.

Affected packages and fixed versions:
- glance (PyPI): affected from 2012.1; fixed in 2012.2.3
- glance (PyPI): affected from 2012.1; fixed in 2012.2.3

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-2013-0212/ (Markdown: https://insights.sbomify.com/CVE-2013-0212/index.md)
```

## Sources

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

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