CVE-2015-8265
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 · uneditedHuawei Mobile WiFi E5151 routers with software before E5151s-2TCPU-V200R001B146D27SP00C00 and E5186 routers with software before V200R001B310D01SP00C00 allow DNS query packets using the static source port, which makes it easier for remote attackers to spoof responses via unspecified vectors.
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 affected Huawei Mobile WiFi E5151 and E5186 routers use a static source port for DNS queries. This predictability reduces the entropy needed for DNS cache poisoning attacks, allowing remote attackers to spoof DNS responses and potentially redirect traffic.
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<= e5151s-2tcpu-v200r001b141d13sp00c1080<= v200r001b306d01c00CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 modelCheck the device label on the router or log into the web administration interface (typically at 192.168.1.1) to confirm the model number is either E5151 or E5186Affected if Router model is E5151 or E5186
-
Check E5151 firmware versionLog into the router web interface, navigate to Status or Device Information page, and record the firmware version stringAffected if Firmware version is e5151s-2tcpu-v200r001b141d13sp00c1080 or earlier (lexicographically earlier or equal to this version)
-
Check E5186 firmware versionLog into the router web interface, navigate to Status or Device Information page, and record the firmware version stringAffected if Firmware version is v200r001b306d01c00 or earlier (lexicographically earlier or equal to this version)
-
Verify static DNS source port configurationCapture DNS packets originating from the router (port 53) using tcpdump or packet capture on the WAN interface, then send multiple DNS queries and observe if the source port remains identical for each requestAffected if The source port in DNS queries is fixed and does not change between queries
You are affected if you have an E5151 router with firmware <= e5151s-2tcpu-v200r001b141d13sp00c1080, or an E5186 router with firmware <= v200r001b306d01c00, and the router uses a static source port for DNS queries.
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 dataUpdate router firmware to the patched versions: E5151s-2TCPU-V200R001B146D27SP00C00 or later for E5151, and V200R001B310D01SP00C00 or later for E5186.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8265 — 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-2015-8265 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