CVE-2017-5729
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 · uneditedFrame replay vulnerability in Wi-Fi subsystem in Intel Dual-Band and Tri-Band Wireless-AC Products allows remote attacker to replay frames via channel-based man-in-the-middle.
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 frame replay vulnerability exists in the Wi-Fi subsystem of Intel Dual-Band and Tri-Band Wireless-AC Products. An attacker positioned as a channel-based man-in-the-middle can capture and replay valid Wi-Fi frames, potentially bypassing authentication or integrity controls.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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 wireless adapter modelOn Windows, run 'devmgmt.msc' and expand Network adapters, or use 'netsh wlan show interfaces' in Command Prompt. On Linux, run 'lspci | grep -i intel' or 'iwconfig'. Look for Intel wireless adapter names.Affected if The adapter model matches any of these: Intel Dual Band Wireless AC 3160, 7260, 7265, 3165 or Intel Wireless N 7260, 7265 (variants including 'Dual Band' or 'N' designations).
-
Confirm Wi-Fi is enabledOn Windows, check if Wi-Fi adapter status shows as 'Enabled' in Device Manager or checkairplane mode status. On Linux, run 'ip link show' or 'iwconfig' to see if the wireless interface (typically wlan0) is up.Affected if Wi-Fi functionality is active and the adapter is connected or capable of connecting to networks.
-
Verify driver version (optional)On Windows, right-click the wireless adapter in Device Manager, select Properties, then the Driver tab to see the driver version. On Linux, run 'ethtool -i wlan0' or check '/proc/driver/rtl*' paths depending on driver.Affected if Any driver version is installed, since all versions of the affected hardware are vulnerable.
Your system is affected if it contains any of the listed Intel wireless adapter models (3160, 7260, 7265, 3165 variants) with Wi-Fi functionality enabled, regardless of driver version.
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 Intel wireless adapter firmware/drivers to versions that implement proper frame sequence number validation and anti-replay mechanisms.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5729 — 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-2017-5729 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