CVE-2018-10244
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 · uneditedSuricata version 4.0.4 incorrectly handles the parsing of an EtherNet/IP PDU. A malformed PDU can cause the parsing code to read beyond the allocated data because DecodeENIPPDU in app-layer-enip-commmon.c has an integer overflow during a length check.
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 · high confidenceSuricata 4.0.4 contains an integer overflow vulnerability in the DecodeENIPPDU function within app-layer-enip-common.c. When parsing a malformed EtherNet/IP PDU, the length check overflows, allowing the parser to read beyond the allocated buffer bounds.
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= 4.0.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Verify Suricata installationRun 'suricata --version' or check package manager for suricata installationAffected if Suricata is not installed on the system
-
Confirm installed version is 4.0.4Execute 'suricata --version' and compare output to '4.0.4'Affected if Version is exactly 4.0.4 (other versions are not affected by this specific CVE)
-
Check if ENIP protocol detection is enabledInspect Suricata configuration file (suricata.yaml) for 'app-layer.protocols.enip' setting under 'providers' section, or run 'suricata --list-app-layer-protos' to confirm enip is listed as enabledAffected if EtherNet/IP (enip) protocol parsing is enabled in the Suricata configuration
System is affected only if running Suricata version 4.0.4 with EtherNet/IP (ENIP) app-layer protocol detection enabled, as the integer overflow occurs during ENIP PDU parsing.
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 · scopedUpgrade Suricata to a version that addresses this vulnerability. Until patched, restrict or monitor untrusted network traffic reaching Suricata instances processing EtherNet/IP traffic.
Suricata 4.0.5 or later (4.1.x, 5.0.x)
- 1. Back up current Suricata configuration files (/etc/suricata/ directory)
- 2. Download Suricata 4.0.5 or later from the official repository (oisf.net or GitHub)
- 3. Stop the Suricata service: systemctl stop suricata
- 4. Install the updated package or compile from source
- 5. Restore the configuration files from backup
- 6. Verify the installation: suricata --version
- 7. Start the Suricata service: systemctl start suricata
- 8. Validate normal operation by checking logs for errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10244 — 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-2018-10244 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