Debian LTS Advisory ([SECURITY] [DLA 1867-1] wpa security update)

Published: 2019-08-01 02:00:14
CVE Author: NIST National Vulnerability Database

CVSS Base Vector:
AV:N/AC:M/Au:N/C:P/I:P/A:P

Summary:
The remote host is missing an update for the 'wpa' Linux Distribution Package(s) announced via the DSA-1867-1 advisory.

Detection Method:
Checks if a vulnerable Linux Distribution Package version is present on the target host.

Technical Details:
Several vulnerabilities were discovered in WPA supplicant / hostapd. Some of them could only partially be mitigated, please read below for details. CVE-2019-9495 Cache-based side-channel attack against the EAP-pwd implementation: an attacker able to run unprivileged code on the target machine (including for example javascript code in a browser on a smartphone) during the handshake could deduce enough information to discover the password in a dictionary attack. This issue has only very partially been mitigated against by reducing measurable timing differences during private key operations. More work is required to fully mitigate this vulnerability. CVE-2019-9497 Reflection attack against EAP-pwd server implementation: a lack of validation of received scalar and elements value in the EAP-pwd-Commit messages could have resulted in attacks that would have been able to complete EAP-pwd authentication exchange without the attacker having to know the password. This did not result in the attacker being able to derive the session key, complete the following key exchange and access the network. CVE-2019-9498 EAP-pwd server missing commit validation for scalar/element: hostapd didn't validate values received in the EAP-pwd-Commit message, so an attacker could have used a specially crafted commit message to manipulate the exchange in order for hostapd to derive a session key from a limited set of possible values. This could have resulted in an attacker being able to complete authentication and gain access to the network. This issue could only partially be mitigated. CVE-2019-9499 EAP-pwd peer missing commit validation for scalar/element: wpa_supplicant didn't validate values received in the EAP-pwd-Commit message, so an attacker could have used a specially crafted commit message to manipulate the exchange in order for wpa_supplicant to derive a session key from a limited set of possible values. This could have resulted in an attacker being able to complete authentication and operate as a rogue AP. This issue could only partially be mitigated. CVE-2019-11555 The EAP-pwd implementation did't properly validate fragmentation reassembly state when receiving an unexpected fragment. This could have lead to a process crash due to a NULL pointer derefrence. An attacker in radio range of a station or access point with EAP-pwd support could cause a crash of the relevant process (wpa_supplicant or hostapd), ensuring a denial of service.

Affected Versions:
'wpa' Linux Distribution Package(s) on Debian Linux.

Recommendations:
For Debian 8 'Jessie', these problems have been fixed in version 2.3-1+deb8u8. We recommend that you upgrade your wpa Linux Distribution Packages.

Solution Type:
Vendor Patch

Detection Type:
Linux Distribution Package

NIST (National Institute of Standards and Technology) NVD (National Vulnerability Database)

https://nvd.nist.gov/vuln/detail/CVE-2019-11555
https://nvd.nist.gov/vuln/detail/CVE-2019-9495
https://nvd.nist.gov/vuln/detail/CVE-2019-9497
https://nvd.nist.gov/vuln/detail/CVE-2019-9498
https://nvd.nist.gov/vuln/detail/CVE-2019-9499

References:

https://lists.debian.org/debian-lts-announce/2019/07/msg00030.html
https://security-tracker.debian.org/tracker/DLA-1867-1
https://bugs.debian.org/927463

Severity
Medium
CVSS Score
6.8
Published
2019-08-01
Modified
2019-08-01
Category
Debian Local Security Checks

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.

Router
Servers
Laptop
Database
Group
Cloud

Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities