# CVE-2013-2074: Information disclosure in n/a

> Attackers can discover credentials via crafted requests triggering internal server errors in the KDE KIO library.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** Yes
- **Published:** 5 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wf2x-h8g9-42vj

## What is CVE-2013-2074?

CVE-2013-2074 is a medium-severity vulnerability in n/a, published on 5 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

kioslave/http/http.cpp in KIO in kdelibs 4.10.3 and earlier allows attackers to discover credentials via a crafted request that triggers an "internal server error," which includes the username and password in an error message.

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

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

It affects 1 product.


Products: Kde Kdelibs.

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

Upgrade to a fixed version.

## Is CVE-2013-2074 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2702](https://insights.sbomify.com/CVE-2009-2702/): Security feature bypass in n/a (high 7.5)
- [CVE-2004-1165](https://insights.sbomify.com/CVE-2004-1165/): Command injection in n/a (high 7.5)
- [CVE-2017-6410](https://insights.sbomify.com/CVE-2017-6410/): Information disclosure in n/a (medium 5.5)
- [CVE-2014-3494](https://insights.sbomify.com/CVE-2014-3494/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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