CVE-2018-16950
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 · uneditedInteno DG400 WU7U_ELION3.11.6-170614_1328 devices allow remote attackers to cause a denial of service (connectivity loss) via a series of packets with random MAC addresses, as demonstrated by macof.
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 confidenceThe Inteno DG400 router firmware has a vulnerability where processing a flood of packets with random MAC addresses (using tools like macof) causes the device to exhaust resources and lose network connectivity. This is a classic MAC table overflow attack on the device's switching fabric.
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= wu7u_elion3.11.6-170614_1328CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:A/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 the device modelAccess the router admin interface or check the physical device label to confirm the model is Inteno DG400Affected if The device is not an Inteno DG400 model
-
Check the installed firmware versionLog into the router web interface or check via CLI command such as 'cat /etc/version' or 'version' to retrieve the firmware build stringAffected if The firmware version matches wu7u_elion3.11.6-170614_1328 exactly
-
Determine network exposureIdentify whether the router WAN or LAN interfaces are directly exposed to untrusted networks or the internet, or if upstream switch port security is disabledAffected if The device is accessible to attackers who can send arbitrary Ethernet frames to it
-
Monitor for MAC table exhaustion symptomsUse switch CLI commands like 'show mac address-table' or 'show mac-address-table' to observe if the MAC table is rapidly filling with random unknown source MAC addressesAffected if The MAC address table is flooding with numerous unfamiliar MAC addresses in a short time period, causing legitimate traffic to be dropped
-
Check for network connectivity lossObserve if devices behind the router suddenly lose network connectivity or experience severe packet loss during potential attack trafficAffected if Connected devices lose network access while the router remains powered on
You are affected if you have an Inteno DG400 router running firmware version wu7u_elion3.11.6-170614_1328 and the device is exposed to untrusted network segments where an attacker can flood it with random MAC addresses.
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.
From vendor dataApply vendor firmware updates when available; if no update exists, consider network segmentation or device replacement. Implement MAC address rate limiting on upstream switches to filter malicious traffic before reaching the affected device.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16950 — 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-16950 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