Codeready Linux BuilderApplication · Redhat

CVE-2019-8720

HIGH · 8.8 CVSS v3.1 Published 2023-03-06

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

In the wild Remotely reachable No privileges

Official description

NVD · unedited

A vulnerability was found in WebKit. The flaw is triggered when processing maliciously crafted web content that may lead to arbitrary code execution. Improved memory handling addresses the multiple memory corruption issues.

Technical summary

dbcve analysis · moderate confidence

CVE-2019-8720 is a memory corruption vulnerability in WebKit (the rendering engine used by Safari and iOS browsers) that is triggered when processing maliciously crafted web content. The flaw allows arbitrary code execution due to multiple memory handling issues that were addressed with improved memory management.

MitigationApply vendor patches by updating WebKit/WebKitGTK or Safari to the latest patched version. Organizations using WebKit in custom applications should update their WebKit dependency to a version containing the fix and restrict user access to untrusted websites until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Codeready Linux BuilderApplication

Affected:= 8.0

Codeready Linux Builder EusApplication

Affected:= 8.4= 8.6

Codeready Linux Builder For Arm64 EusApplication

Affected:= 8.0= 8.4= 8.6

Codeready Linux Builder For Ibm Z Systems EusApplication

Affected:= 8.0= 8.4= 8.6

Codeready Linux Builder For Power Little Endian EusApplication

Affected:= 8.0= 8.4= 8.6

Enterprise LinuxOperating system

Affected:= 8.0

Enterprise Linux DesktopOperating system

Affected:= 7.0

Enterprise Linux EusOperating system

Affected:= 8.4= 8.6

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

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

Identify if WebKit is installed

Run 'rpm -qa | grep -i webkit' to list installed WebKit packages such as webkit2gtk or webkitgtk

Affected if No WebKit packages are found, the system is not affected because the vulnerable component is not present
Check the WebKit package version

Run 'rpm -q --changelog webkit2gtk4' or 'rpm -q --changelog webkitgtk4' to see the installed version and compare it to the fixed versions in Red Hat advisories

Affected if The installed version matches the affected Red Hat Enterprise Linux versions 7.0, 8.0, 8.4, or 8.6 without corresponding security patches
Verify the RHEL release version

Run 'cat /etc/redhat-release' or 'hostnamectl' to determine the exact RHEL version

Affected if The system runs RHEL 7.0, RHEL 8.0, RHEL 8.4, or RHEL 8.6 and contains WebKit packages from the affected channels
Check for running WebKit-based applications

Run 'ps aux | grep -E "(webkit|midori|epiphany|gnome-web-photo)" or examine installed browsers that depend on WebKit

Affected if WebKit-based applications are installed and could be used to process untrusted web content, making the vulnerability exploitable
Review installed security advisories

Run 'yum updateinfo list installed' to see which security updates have been applied, specifically looking for RHSA entries addressing WebKit

Affected if Security updates for this CVE are not listed as installed, indicating the system remains vulnerable

A system is affected if it runs a Red Hat Enterprise Linux version 7.0, 8.0, 8.4, or 8.6 with WebKit packages installed that have not received the corresponding security patches for CVE-2019-8720.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply vendor patches by updating WebKit/WebKitGTK or Safari to the latest patched version. Organizations using WebKit in custom applications should update their WebKit dependency to a version containing the fix and restrict user access to untrusted websites until the patch is applied.

Recommended fix High confidence

Red Hat Enterprise Linux 8: webkit2gtk to version containing CVE-2019-8720 fix (via RHSA); Red Hat Enterprise Linux 7: webkitgtk3 to version containing CVE-2019-8720 fix (via RHSA)

Ensure your system is registered with Red Hat Subscription Management or Red Hat Satellite
Run 'yum check-update' or 'dnf check-update' to check for available updates
Update the webkit2gtk package by running 'yum update webkit2gtk' or 'dnf update webkit2gtk'
After the update completes, verify the installed version with 'rpm -q webkit2gtk'
Reboot the system or restart any affected services (such as browsers or applications using WebKit) to ensure the new library is loaded
Confirm the CVE is resolved by running 'yum updateinfo list installed | grep CVE-2019-8720' or checking the Red Hat Security Advisory RHSA

Caveat Standard WebKit library updates typically have no breaking changes; however, minor behavior differences in rendered web content may occur

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

Fix this in Codeready Linux Builder Exploited in the wild — priority engagement

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2019-8720 — 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

Primary sources

webkitgtk.orgVendor Advisory
bugzilla.redhat.comIssue TrackingThird Party Advisory
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2019-8720?

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.

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

At a glance

Exploited in the wildOn CISA’s known-exploited list · agencies must fix by 2022-06-13

A fix existsA vendor remedy is published

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 1.5%

Affects: Codeready Linux Builder

Remediation

Being exploited — close it fast

Fix this in Codeready Linux Builder 7 hrs · Moderate

Typical engagement from $1,240

Get it fixed fast See the full breakdown ↓

This CVE is on CISA’s actively-exploited list, so the clock is real — a vetted specialist can deliver a reviewed fix for your staging environment quickly.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References