# CVE-2013-2297: Hardcoded credentials in n/a

> Local attackers can gain elevated privileges due to a blank root password in the default Eucalyptus EuStore configuration.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6v7w-m3c5-h9c6

## What is CVE-2013-2297?

CVE-2013-2297 is a medium-severity vulnerability in n/a, published on 17 Sep 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Eucalyptus EuStore sets a blank root password in the default configuration of EMI 3868652036, EMI 0400376721, EMI 2425352071, and EMI 1347115203, which allows local users to gain privileges via unspecified vectors, a related issue to CVE-2013-2069.

Weakness: CWE-255

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

It affects 1 product.


Products: Eucalyptus Eustore.

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

No fix has been published for CVE-2013-2297 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-2297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2297 is a medium-severity vulnerability in n/a, published on 17 Sep 2013. 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-2013-2297 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-2013-2297/ (Markdown: https://insights.sbomify.com/CVE-2013-2297/index.md)
```

## Sources

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

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