dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-9178

HIGH · 7.7 CVSS v4.0 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
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 denial-of-service security issue exists in the affected product and version. The security issue is caused through CIP communication using crafted payloads. The security issue could result in no CIP communication with 1715 EtherNet/IP Adapter.A restart is required to recover.

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

A denial-of-service vulnerability exists in the 1715 EtherNet/IP Adapter allowing remote attackers to cause CIP communication failure through crafted CIP payloads. The vulnerability can be exploited remotely via specially crafted CIP communication packets, resulting in complete loss of CIP communication with the device.

MitigationApply vendor-provided firmware updates when available; network segmentation and CIP traffic filtering can provide interim protection. A device restart is required to recover from successful exploitation.

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:N/SC:N/SI:N/SA:H/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 1715 EtherNet/IP Adapter presence
    Inventory network devices and verify if any 1715 EtherNet/IP Adapter units are deployed on the network. Check device asset records or perform network discovery scanning for EtherNet/IP enabled devices.
    Affected if The organization has 1715 EtherNet/IP Adapter devices in their industrial network environment.
  2. Determine device firmware version
    Access the device web interface, use the vendor management software, or query the device via EtherNet/IP CIP protocol to retrieve the current firmware version. Compare against any vendor-published affected version ranges.
    Affected if The device firmware version falls within the vulnerable version range as specified by the vendor.
  3. Verify CIP communication is enabled
    Check device configuration settings to confirm CIP (Common Industrial Protocol) communication is enabled. This is typically configured in the device network settings or communication profile.
    Affected if CIP communication is enabled and the device is actively processing CIP traffic.
  4. Check network exposure of EtherNet/IP ports
    Review firewall rules and network segmentation to determine if the device CIP ports (typically UDP/44818 for EtherNet/IP) are exposed to untrusted networks or the internet.
    Affected if The device CIP ports are reachable from untrusted or external network segments without proper filtering.
  5. Monitor for CIP communication failures
    Observe device status and CIP communication logs for any disruptions, timeouts, or failures in CIP communication. A successful exploit results in complete loss of CIP communication requiring device restart.
    Affected if CIP communication with the device fails or becomes unresponsive, especially after receiving unusual CIP packets.

The environment is affected if 1715 EtherNet/IP Adapter devices are deployed, CIP communication is enabled, and the firmware version falls within the vulnerable range as defined by the vendor.

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

Apply vendor-provided firmware updates when available; network segmentation and CIP traffic filtering can provide interim protection. A device restart is required to recover from successful exploitation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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