dbcve.org
FedoraOperating system · Fedoraproject

CVE-2020-10018

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-02
Fix available
A fix is available. Upgrade to 2.28.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
WebKitGTK through 2.26.4 and WPE WebKit through 2.26.4 (which are the versions right before 2.28.0) contains a memory corruption issue (use-after-free) that may lead to arbitrary code execution. This issue has been fixed in 2.28.0 with improved memory handling.

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 confidence

WebKitGTK through 2.26.4 and WPE WebKit through 2.26.4 contain a use-after-free memory corruption vulnerability that could allow an attacker to execute arbitrary code by exploiting improper memory handling in the web rendering engine.

MitigationUpgrade WebKitGTK and WPE WebKit to version 2.28.0 or later which contains improved memory handling to address the use-after-free vulnerability.

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
FedoraOperating system
Affected:= 30= 31
Debian LinuxOperating system
Affected:= 10.0
Ubuntu LinuxOperating system
Affected:= 18.04= 19.10
WebkitgtkWeb browser
Affected:< 2.28.0
Wpe WebkitWeb browser
Affected:< 2.28.0
LeapOperating system
Affected:= 15.1

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WebKitGTK is installed
    Check for webkitgtk packages using your system's package manager (e.g., rpm -qa | grep webkitgtk on RHEL/Fedora, dpkg -l | grep webkitgtk on Debian/Ubuntu, or zypper se webkitgtk on openSUSE)
    Affected if Any version of webkitgtk package is found on the system
  2. Determine WebKitGTK version
    Run the package manager query command for version information (e.g., rpm -q webkitgtk4 on Fedora/RHEL, dpkg -s libwebkit2gtk-4.0-37 on Debian/Ubuntu)
    Affected if The installed version is lower than 2.28.0 (e.g., 2.26.x or earlier)
  3. Identify if WPE WebKit is installed
    Check for wpewebkit packages using your system's package manager (e.g., rpm -qa | grep wpewebkit, dpkg -l | grep wpewebkit, or zypper se wpewebkit)
    Affected if Any version of wpewebkit package is found on the system
  4. Determine WPE WebKit version
    Run the package manager query command for version information (e.g., rpm -q wpewebkit, dpkg -s libwpebackend-fdo-1.0)
    Affected if The installed version is lower than 2.28.0 (e.g., 2.26.x or earlier)
  5. Check if WebKit is in use by applications
    Identify applications that depend on WebKitGTK or WPE WebKit (e.g., Epiphany browser, WebKit browsers, or custom applications using WebKit) and verify their linked WebKit library versions using ldd or examining application metadata
    Affected if The linked WebKit library version is < 2.28.0

The system is affected if WebKitGTK or WPE WebKit is installed and the installed version is below 2.28.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.28.0 or later
Fixed in 2.28.0
Interim mitigation

Upgrade WebKitGTK and WPE WebKit to version 2.28.0 or later which contains improved memory handling to address the use-after-free vulnerability.

Recommended fix High confidence

WebKitGTK 2.28.0 or later / WPE WebKit 2.28.0 or later

  1. Identify the WebKitGTK or WPE WebKit package installed on the system (e.g., `dpkg -l | grep webkit`, `rpm -qa | grep webkit`, or `zypper se webkit`)
  2. Update the package repository metadata
  3. Upgrade the webkit2gtk or wpewebkit package to version 2.28.0 or later (e.g., `dnf update webkit2gtk`, `apt-get update && apt-get upgrade libwebkit2gtk-4.0-37`, `zypper update webkit2gtk`)
  4. Verify the installed version is 2.28.0 or later using the package manager or `webkit2gtk --version`
  5. Restart any applications or services that depend on the WebKit library
Caveat Major WebKit version upgrades may include API changes; review release notes if using custom WebKit-dependent applications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10018 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10018 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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