CVE-2018-0555
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 · uneditedBuffer overflow in Buffalo WZR-1750DHP2 Ver.2.30 and earlier allows an attacker to execute arbitrary code via a specially crafted file.
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 confidenceA buffer overflow vulnerability exists in Buffalo WZR-1750DHP2 routers (version 2.30 and earlier) that allows remote code execution via a specially crafted file, likely during file upload or parsing operations.
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<= 2.30CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Identify device modelAccess router web interface or check device label; confirm model is Buffalo WZR-1750DHP2Affected if Device is not a Buffalo WZR-1750DHP2 model (not affected)
-
Check firmware versionLog into router web interface (usually 192.168.11.1); navigate to Administration or System section; locate firmware version displayedAffected if Firmware version is 2.30 or lower (vulnerable)
-
Verify firmware version via CLIAccess router via telnet or SSH if enabled; run command 'cat /proc/version' or 'nvram get firmver' to retrieve firmware versionAffected if Returned version is 2.30 or earlier (vulnerable)
-
Check remote management exposureDetermine if router web interface is accessible from WAN (internet); test by accessing router's public IP on ports 80/443; check firewall/NAT settingsAffected if Remote management is enabled and router is internet-facing (higher risk of exploitation)
-
Assess file upload featuresLog into router web interface; look for firmware upgrade, configuration backup/restore, or firmware update functions in Administration or Maintenance sectionsAffected if File upload features are present and accessible (attack vector available)
Device is affected if it is a Buffalo WZR-1750DHP2 router running firmware version 2.30 or earlier, especially if the web interface is accessible from untrusted networks.
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 dataUpgrade Buffalo WZR-1750DHP2 firmware to a version newer than 2.30; if no patched firmware is available, consider network segmentation or device replacement.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0555 — 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-0555 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