# CVE-2011-4190: Missing verification of host key for kdump server

> A remote attacker can impersonate a kdump server to steal sensitive core dump files due to missing host key verification in SUSE kdump.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cp9h-xhgc-8r95

## What is CVE-2011-4190?

CVE-2011-4190 is a medium-severity missing authorization vulnerability in Suse Suse Linux Enterprise Desktop, published on 8 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The kdump implementation is missing the host key verification in the kdump and mkdumprd OpenSSH integration of kdump prior to version 2012-01-20. This is similar to CVE-2011-3588, but different in that the kdump implementation is specific to SUSE. A remote malicious kdump server could use this flaw to impersonate the correct kdump server to obtain security sensitive information (kdump core files).

Weakness: CWE-310, CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 2 products.


Products: Suse Suse Linux Enterprise Desktop, Suse Suse Linux Enterprise Server.

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

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

## Is CVE-2011-4190 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-4190 is a medium-severity missing authorization vulnerability in Suse Suse Linux Enterprise Desktop, published on 8 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4190 in the wild and no public exploit code.

Affected product: Suse Suse Linux Enterprise Desktop. 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-4190/ (Markdown: https://insights.sbomify.com/CVE-2011-4190/index.md)
```

## Sources

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

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