dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2017-13077

MEDIUM · 6.8 CVSS v3.0 Published 2017-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Pairwise Transient Key (PTK) Temporal Key (TK) during the four-way handshake, allowing an attacker within radio range to replay, decrypt, or spoof frames.

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 confidence

CVE-2017-13077 is a vulnerability in the WPA/WPA2 four-way handshake that allows reinstallation of the Pairwise Transient Key (PTK) Temporal Key (TK). An attacker within radio range can exploit this to replay, decrypt, or spoof Wi-Fi frames by forcing reinstallation of cryptographic keys during the handshake process.

MitigationApply vendor-specific patches to affected Wi-Fi access points and client devices. Until patched, use WPA3 where available or consider additional network-layer encryption (VPN) as a compensating control.

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
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 17.04
Debian LinuxOperating system
Affected:= 8.0= 9.0
FreeBSDOperating system
Affected:all versions= 10= 10.4= 11= 11.1
Enterprise Linux DesktopOperating system
Affected:= 7
Enterprise Linux ServerOperating system
Affected:= 7
LeapOperating system
Affected:= 42.2= 42.3
HostapdApplication
Affected:= 0.2.4= 0.2.5= 0.2.6= 0.2.8= 0.3.7= 0.3.9= 0.3.10= 0.3.11= 0.4.7= 0.4.8= 0.4.9= 0.4.10
Wpa SupplicantApplication
Affected:= 0.2.4= 0.2.5= 0.2.6= 0.2.7= 0.2.8= 0.3.7= 0.3.8= 0.3.9= 0.3.10= 0.3.11= 0.4.7= 0.4.8

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed hostapd version
    Run 'dpkg -l hostapd' (Debian/Ubuntu) or 'rpm -qi hostapd' (RHEL/openSUSE) or check /usr/sbin/hostapd --version
    Affected if The version matches any of: 0.2.4, 0.2.5, 0.2.6, 0.2.8, 0.3.7, 0.3.9, 0.3.10, 0.3.11, 0.4.7, 0.4.8, 0.4.9, 0.4.10
  2. Identify installed wpa_supplicant version
    Run 'dpkg -l wpasupplicant' (Debian/Ubuntu) or 'rpm -qi wpa_supplicant' (RHEL/openSUSE) or check wpa_supplicant --version
    Affected if The version matches any of: 0.2.4 through 0.2.8, 0.3.7 through 0.3.11, 0.4.7, 0.4.8
  3. Verify if Wi-Fi interface is configured
    Run 'ip link show' or 'iwconfig' to list wireless interfaces, then check 'iw dev <interface> info' for connection status
    Affected if A Wi-Fi interface exists and is using WPA/WPA2 authentication (check /etc/wpa_supplicant.conf or NetworkManager settings)
  4. Check FreeBSD base system version
    Run 'freebsd-version' or 'uname -r' on FreeBSD systems
    Affected if Version is 10.x, 10.4, 11.x, or 11.1 and the system runs hostapd or has wireless functionality enabled
  5. Check Linux distribution version for affected Ubuntu/Debian/RHEL
    Run 'lsb_release -a' (Ubuntu) or 'cat /etc/debian_version' (Debian) or 'cat /etc/redhat-release' (RHEL)
    Affected if Ubuntu 14.04, 16.04, or 17.04; Debian 8.0 or 9.0; RHEL 7 (Desktop or Server) is installed AND the system uses the affected Wi-Fi software versions

You are affected if your system runs a vulnerable version of hostapd or wpa_supplicant (matching the listed versions) and has an active Wi-Fi interface using WPA/WPA2 authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-specific patches to affected Wi-Fi access points and client devices. Until patched, use WPA3 where available or consider additional network-layer encryption (VPN) as a compensating control.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-13077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-13077 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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