CVE-2025-12601
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 · uneditedDenial of Service Due to SlowLoris.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.
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 confidenceA SlowLoris-style denial of service vulnerability exists in BLU-IC2 and BLU-IC4 devices through version 1.19.5. The attack works by establishing many HTTP connections and sending partial requests slowly, keeping connections open and exhausting server resources (connection pools), preventing legitimate users from accessing services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
NVD · CPE data< 1.20< 1.20CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck the physical device label or access the device management interface to confirm the model is BLU-IC2 or BLU-IC4Affected if Device is a BLU-IC2 or BLU-IC4 unit
-
Check firmware versionAccess the device web interface or use the vendor's management CLI to retrieve the current firmware version. Compare against the affected range of versions below 1.20Affected if Firmware version is below 1.20
-
Verify HTTP service exposureCheck network configuration to determine if the device HTTP service is accessible from external networks or the internet (check firewall rules, port forwarding, or NAT settings for port 80/443)Affected if HTTP service is network-accessible to untrusted sources
-
Inspect connection timeout settingsAccess the device administration panel or configuration files to examine current HTTP connection timeout values. Look for settings related to keep-alive, connection duration, or request timeoutsAffected if No connection timeouts are configured or timeouts are set to very high values (multiple minutes)
-
Check rate limiting configurationExamine the device security settings for any rate limiting or connection throttling options that may mitigate SlowLoris attacksAffected if No rate limiting is enabled and connections can remain open indefinitely
User is affected if they have a BLU-IC2 or BLU-IC4 device running firmware below version 1.20 with HTTP services exposed to the network without proper connection timeouts or rate limiting configured.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped1.20
Implement connection timeouts and request rate limiting on affected devices, or apply vendor-supplied firmware updates when available. Consider deploying a web application firewall or reverse proxy to mitigate SlowLoris attacks at the network perimeter.
BLU-IC2 and BLU-IC4 firmware version 1.20 or later
- 1. Identify the current firmware version of the BLU-IC2 and/or BLU-IC4 devices
- 2. Access the device management interface or use the vendor's firmware update mechanism
- 3. Download the firmware version 1.20 or later from the vendor's official support site
- 4. Apply the firmware upgrade following the vendor's documented upgrade procedure
- 5. Verify the upgrade was successful by confirming the new firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12601 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12601 in production — separate from our analysis above.
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.
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.
- 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