CVE-2024-7001

Inappropriate implementation in HTML in Google Chrome prior to 127.0.6533.72 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

Published: 2024-08-06 Last update: 2025-03-19 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-7001 is rated Low Risk (29.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.42%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-7001

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.07% 0.42% +0.35%
2 2025-03-30 0.23% 0.07% -0.17%
3 2025-03-29 0.23%

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-7001

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 [email protected]
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-7001

OS Trackers for CVE-2024-7001

vendor priority summary link
debian end-of-life CVE-2024-7001 end-of-life priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-7001
gentoo high CVE-2024-7001: 1 GLSA(s) (202501-09), 1 atom(s) (dev-qt/qtwebengine); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-7001
ubuntu medium CVE-2024-7001 medium priority: Ubuntu including 1 source packages (chromium-browser), 4 status rows across 4 suites (focal, jammy, noble, upstream): not-affected 2, DNE 1, released 1. https://ubuntu.com/security/CVE-2024-7001

Affected software / configurations for CVE-2024-7001

Vendor Product Version Raw CPE
google chrome < 127.0.6533.72 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2024-7001

cvelogic Threat Intelligence