CVE-2018-8878
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 · uneditedInformation disclosure in Asuswrt-Merlin firmware for ASUS devices older than 384.4 and ASUS firmware before 3.0.0.4.382.50470 for devices allows remote attackers to acquire information on internal network devices' hostnames and MAC addresses by reading the custom_id variable on the blocking.asp page.
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 confidenceInformation disclosure vulnerability in Asuswrt-Merlin and ASUS router firmware where the custom_id variable on the blocking.asp page exposes internal network device hostnames and MAC addresses to remote attackers without authentication.
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< 384.4< 3.0.0.4.382.50470CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 router model and firmware typeLog into the router web interface (typically 192.168.1.1) and check the Firmware Version or Router Model field on the main status page. Alternatively, if you have SSH/telnet access, run 'nvram get model' or 'cat /proc/sys/kernel/router_firmware_version' if available.Affected if The router is an ASUS device running either stock ASUS firmware or the Asuswrt-Merlin third-party firmware variant.
-
Determine installed firmware versionIn the router web interface, navigate to Administration > Firmware Upgrade or a similar section to view the exact firmware version number. Note that some interfaces display this on the main Dashboard or System Overview page.Affected if The displayed firmware version is not visible or cannot be confirmed.
-
Compare against affected version rangesIf running Asuswrt-Merlin: check if version is less than 384.4. If running stock ASUS firmware: check if version is less than 3.0.0.4.382.50470. Compare your identified version numerically.Affected if The installed version is below 384.4 for Asuswrt-Merlin, or below 3.0.0.4.382.50470 for ASUS firmware.
You are affected if your router runs Asuswrt-Merlin firmware below version 384.4 or ASUS stock firmware below version 3.0.0.4.382.50470.
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 data3.0.0.4.382.50470384.4
Upgrade Asuswrt-Merlin firmware to version 384.4 or later, or ASUS firmware to 3.0.0.4.382.50470 or later.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8878 — 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-8878 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