Skip to content
Fencer Intel
high 7.5

CVE-2018-11646 in the critical feed json

webkitFaviconDatabaseSetIconForPageURL and webkitFaviconDatabaseSetIconURLForPageURL in UIProcess/API/glib/WebKitFaviconDatabase.cpp in Web…

published 8y ago modified 4mo ago also EUVD-2018-3669

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
68.0%
EPSS 68.0% chance of exploitation in 30 days, percentile 99.3%
public exploits
3
Metasploit and Exploit-DB

Summary

webkitFaviconDatabaseSetIconForPageURL and webkitFaviconDatabaseSetIconURLForPageURL in UIProcess/API/glib/WebKitFaviconDatabase.cpp in WebKit, as used in WebKitGTK+ through 2.21.3, mishandle an unset pageURL, leading to an application crash.

Patch / fix

  • webkit2gtk Debian 14, Debian 13, Debian 12 2.20.3-1

debian advisories DEBIAN-CVE-2018-11646

  • webkit2gtk Ubuntu 16.04 LTS 2.20.1-0ubuntu0.16.04.1

ubuntu advisories UBUNTU-CVE-2018-11646

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • webkit2gtk3 SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 +2 more 2.20.3-2.23.8
  • webkit2gtk3 SLE Module for Desktop Applications 15, SLE Module for Basesystem 15 2.20.3-3.3.1

suse advisories SUSE-SU-2018:3387-1SUSE-SU-2018:2075-1

  • gtk3 openSUSE Tumbleweed 2.32.4-1.1

opensuse advisories openSUSE-SU-2024:11506-1

Is CVE-2018-11646 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (Metasploit auxiliary/dos/http/webkitplus)

Exploit prediction

68.02% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.