# CVE-2011-3590: Information disclosure in n/a

> Attackers can obtain root SSH private keys by inspecting vmcore files generated by the mkdumprd script in Red Hat kexec-tools.

- **Severity:** Medium 5.7 (`AV:A/AC:M/Au:N/C:C/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:** 15 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-22w6-gp78-84rc

## What is CVE-2011-3590?

CVE-2011-3590 is a medium-severity vulnerability in n/a, published on 15 Feb 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Red Hat mkdumprd script for kexec-tools, as distributed in the kexec-tools 1.x before 1.102pre-154 and 2.x before 2.0.0-209 packages in Red Hat Enterprise Linux, includes all of root's SSH private keys within a vmcore file, which allows context-dependent attackers to obtain sensitive information by inspecting the file content.

Weakness: CWE-310

## Which versions are affected by CVE-2011-3590?

It affects 1 product.


Products: Redhat Kexec-Tools.

## How do I fix CVE-2011-3590?

Apply the vendor's patch.

## Is CVE-2011-3590 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3588](https://insights.sbomify.com/CVE-2011-3588/): Security feature bypass in n/a (medium 5.7)
- [CVE-2011-3589](https://insights.sbomify.com/CVE-2011-3589/): Information disclosure in n/a (medium 5.7)
- [CVE-2015-0267](https://insights.sbomify.com/CVE-2015-0267/): Path traversal in n/a (low 3.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3590 and fix it if it is affected.

What it is: CVE-2011-3590 is a medium-severity vulnerability in n/a, published on 15 Feb 2014. 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-2011-3590 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-2011-3590/ (Markdown: https://insights.sbomify.com/CVE-2011-3590/index.md)
```

## Sources

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

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