CVE-2013-2074
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedkioslave/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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe KIO kioslave HTTP implementation (kioslave/http/http.cpp) in kdelibs 4.10.3 and earlier contains an information disclosure vulnerability. When a crafted HTTP request triggers an internal server error, the error handling code incorrectly includes authentication credentials (username and password) in the error message, allowing remote attackers to obtain stored credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.10.3= 4.10.0= 4.10.1= 4.10.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed kdelibs versionRun 'dpkg -l | grep kdelibs' or 'rpm -qa | grep kdelibs' or check your package manager for kdelibs packages. Alternatively, look for kdelibs version in /usr/share/doc/kdelibs/ or via 'kde-config --version'Affected if The installed version is 4.10.3 or earlier (4.10.0, 4.10.1, 4.10.2, or any version <= 4.10.3)
-
Confirm kioslave HTTP component is presentCheck if the kioslave HTTP implementation exists at kioslave/http/http.cpp or verify the kdelibs-common package contains the http kioslave moduleAffected if The kioslave HTTP module is present in the kdelibs installation
-
Verify HTTP authentication is in useInspect KDE configuration files (typically in ~/.kde/ or ~/.kde4/) for stored HTTP credentials, or check if applications using KIO (like Dolphin, Konqueror) have saved passwords for HTTP/HTTPS serversAffected if HTTP or HTTPS URLs with saved credentials are configured in the KDE wallet or application settings
-
Check for exposure to remote HTTP serversReview system logs or application logs for any HTTP 500 errors or internal server errors when accessing authenticated HTTP resourcesAffected if The system makes authenticated HTTP requests and may receive error responses from servers
You are affected if KDE kdelibs version 4.10.3 or earlier is installed and the system or any KDE application uses HTTP authentication to access remote servers, as credentials could be leaked in error responses.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to kdelibs version 4.10.4 or later which contains the patched error handling code, or manually patch kioslave/http/http.cpp to sanitize credential information from error messages before they are returned to the client.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2074 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data