dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-41360

HIGH · 8.7 CVSS v4.0 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
Uncontrolled resource consumption vulnerability in IDF v0.10.0-0C03-03 and ZLF v0.10.0-0C03-04. The device is vulnerable to a packet flooding denial of service attack.

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 · moderate confidence

IDF v0.10.0-0C03-03 and ZLF v0.10.0-0C03-04 contain an uncontrolled resource consumption vulnerability that allows remote attackers to cause denial of service through packet flooding, exhausting device resources without proper throttling or limits.

MitigationImplement network-level rate limiting, traffic filtering, or DDoS mitigation at the network perimeter to block or throttle excessive packet flows; if a patched version is available, upgrade accordingly.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 IDF version
    Locate and inspect the IDF installation directory, check for a version file or run 'idf --version' or 'idf -v' command if available
    Affected if Version is v0.10.0-0C03-03 exactly
  2. Identify ZLF version
    Locate and inspect the ZLF installation directory, check for a version file or run 'zlf --version' or 'zlf -v' command if available
    Affected if Version is v0.10.0-0C03-04 exactly
  3. Confirm network exposure
    Determine if IDF or ZLF network services are exposed to untrusted networks by reviewing firewall rules, network configuration, or listening ports
    Affected if Network services are accessible from external or untrusted networks without network-level filtering
  4. Check for rate limiting configuration
    Inspect configuration files for any rate limiting, throttling, or traffic control settings related to packet processing
    Affected if No rate limiting or throttling controls are configured or defined in the system

A defender is affected if they have IDF v0.10.0-0C03-03 or ZLF v0.10.0-0C03-04 installed with network-facing services and no rate limiting or traffic throttling controls in place.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement network-level rate limiting, traffic filtering, or DDoS mitigation at the network perimeter to block or throttle excessive packet flows; if a patched version is available, upgrade accordingly.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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