CVE-2018-19120
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 · uneditedThe HTML thumbnailer plugin in KDE Applications before 18.12.0 allows attackers to trigger outbound TCP connections to arbitrary IP addresses, leading to disclosure of the source IP address.
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 HTML thumbnailer plugin in KDE Applications before 18.12.0 contains a Server-Side Request Forgery (SSRF) vulnerability where it processes URLs from untrusted input without proper validation, allowing attackers to force the application to initiate outbound TCP connections to arbitrary IP addresses, thereby exposing the server's source IP address.
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< 18.12.0CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Check KDE Applications versionRun 'kde-open5 --version' or check your package manager for installed kde-applications version (e.g., 'dpkg -l | grep -i kde' or 'rpm -qa | grep -i kde')Affected if Version is lower than 18.12.0
-
Locate the HTML thumbnailer pluginSearch for thumbnail generation plugins in ~/.local/share/thumbs or /usr/share/thumbnailers/ and look for 'html' or 'khtml' related thumbnailer configuration filesAffected if HTML thumbnailer plugin exists in the thumbnailer directories
-
Verify thumbnailer plugin is enabledCheck /etc/thumbnailers or ~/.config/thumbnailers/ for entries that invoke KDE's thumbnail generation on HTML filesAffected if An HTML thumbnailer entry exists and is enabled in the thumbnailer configuration
-
Inspect recent thumbnail generation logsReview system logs (journalctl, syslog) or thumbnail cache directories for evidence of recent HTML thumbnail generation requestsAffected if HTML thumbnails have been recently generated, indicating the plugin is active and processing files
You are affected if KDE Applications version is below 18.12.0 AND the HTML thumbnailer plugin is present and enabled on the system.
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 data18.12.0
Upgrade KDE Applications to version 18.12.0 or later. If upgrade is not feasible, implement URL allowlist validation in the thumbnailer to restrict connections to trusted domains only.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19120 — 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-2018-19120 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