dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-7693

CRITICAL · 9.3 CVSS v4.0 Published 2025-08-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
A security issue exists due to improper handling of malformed CIP Forward Close packets during fuzzing. The controller enters a solid red Fault LED state and becomes unresponsive. Upon power cycle, the controller will enter recoverable fault where the MS LED and Fault LED become flashing red and reports fault code 0xF015. To recover, clear the fault.

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

This vulnerability exists in industrial controller firmware where malformed CIP (Common Industrial Protocol) Forward Close packets trigger a critical fault state. The controller enters an unresponsive state with solid red Fault LED, and after power cycle reports fault code 0xF015, requiring manual fault clearing to recover. This is a denial-of-service vulnerability exploitable via network-based fuzzing of CIP traffic.

MitigationImplement network segmentation to restrict CIP traffic to authorized devices only; apply vendor firmware updates when available; consider deploying ICS-aware firewalls or deep packet inspection to filter malformed CIP Forward Close packets before they reach the controller.

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:H/VI:H/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 if the device is an industrial controller using CIP
    Check the device documentation or network configuration for EtherNet/IP or Common Industrial Protocol (CIP) usage. Look for CIP-based devices on the network using inventory tools or by examining network traffic for CIP-specific protocols (EtherNet/IP, CIP Safety, etc.).
    Affected if The device is an industrial controller that processes CIP Forward Close packets as part of EtherNet/IP communication.
  2. Inspect the controller LED status
    Visually examine the controller front panel for LED indicators. Look for a solid red Fault LED, or after a power cycle, flashing red MS (Module Status) and Fault LEDs simultaneously.
    Affected if The controller displays a solid red Fault LED (currently unresponsive) or flashing red MS and Fault LEDs after power cycle, indicating the fault has occurred.
  3. Check for fault code 0xF015
    Connect to the controller via the vendor's programming software, HMI, or console interface and query the fault code/status registers. Look specifically for fault code 0xF015 in the fault history or current fault register.
    Affected if Fault code 0xF015 is present in the controller's fault log, confirming the malformed CIP Forward Close packet fault has triggered.
  4. Monitor network for CIP Forward Close packets
    Use a network sniffer (such as Wireshark with EtherNet/IP dissector) to capture traffic on the industrial network. Filter for CIP Forward Close messages (CIP layer, Forward Open/Close services). Inspect packet structure for malformed headers or unexpected field values.
    Affected if Malformed CIP Forward Close packets are observed on the network targeting the controller, indicating active exploitation attempt or the condition that triggered the fault.

A user is affected if their industrial controller displays a solid red Fault LED or shows fault code 0xF015 after processing malformed CIP Forward Close packets on an EtherNet/IP network.

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 segmentation to restrict CIP traffic to authorized devices only; apply vendor firmware updates when available; consider deploying ICS-aware firewalls or deep packet inspection to filter malformed CIP Forward Close packets before they reach the controller.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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