cve.bz

CVE-2025-4215 Uncontrolled Resource Consumption

2.3 lowExploit referenceEPSS 0.8%Fix available

Low (2.3). EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability was found in gorhill uBlock Origin up to 1.63.3b16. It has been classified as problematic. Affected is the function currentStateChanged of the file src/js/1p-filters.js of the component UI. The manipulation leads to inefficient regular expression complexity. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 1.63.3b17 is able to address this issue. The patch is identified as eaedaf5b10d2f7857c6b77fbf7d4a80681d4d46c. It is recommended to upgrade the affected component.

Severity

CVSS 4.0

2.3 low
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-05-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-1333 Inefficient Regular Expression Complexity
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-4215 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-4215?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-4215?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-4215 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ublockorigin:ublock_originbefore 1.63.3
ublockorigin:ublock_origin1.63.3:beta1
ublockorigin:ublock_origin1.63.3:beta10
ublockorigin:ublock_origin1.63.3:beta11
ublockorigin:ublock_origin1.63.3:beta12
ublockorigin:ublock_origin1.63.3:beta13
ublockorigin:ublock_origin1.63.3:beta14
ublockorigin:ublock_origin1.63.3:beta15
ublockorigin:ublock_origin1.63.3:beta16
ublockorigin:ublock_origin1.63.3:beta2
ublockorigin:ublock_origin1.63.3:beta3
ublockorigin:ublock_origin1.63.3:beta4
ublockorigin:ublock_origin1.63.3:beta5
ublockorigin:ublock_origin1.63.3:beta6
ublockorigin:ublock_origin1.63.3:beta7
ublockorigin:ublock_origin1.63.3:beta8
ublockorigin:ublock_origin1.63.3:beta9
debian:debian_linux11.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11ublock-origin1.62.0+dfsg-0+deb11u1DLA-4215-1
Debian12ublock-origin1.62.0+dfsg-0+deb12u1DEBIAN-CVE-2025-4215
Debian13, 14ublock-origin1.62.0+dfsg-2DEBIAN-CVE-2025-4215
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 2 moreublock-originno fix listedUBUNTU-CVE-2025-4215

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-492 Regular Expression Exponential Blowup
  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON