From 67e72c1417dc98f411321f7573990671291ece15 Mon Sep 17 00:00:00 2001 From: vanhoefm Date: Sat, 26 Jun 2021 03:01:22 +0400 Subject: [PATCH] README: Further clarify A-MSDU tests --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 00f68352a..6147428a0 100644 --- a/README.md +++ b/README.md @@ -329,7 +329,8 @@ CVEs as a way to easily refer to each type of discovered implementation flaw. ## 7.3. A-MSDU attack tests (ยง3 -- CVE-2020-24588) -The test `ping I,E --amsdu` checks if an implementation _supports_ non-SPP A-MSDUs. To prevent attacks, ideally +The test `ping I,E --amsdu` checks if an implementation _supports_ non-SPP A-MSDUs (it doesn't check if the device +is vulnerable to CVE-2020-24588). To prevent attacks, ideally the network must mandate the usage of SPP A-MSDUs and drop all non-SPP A-MSDUs. However, most vendors are currently implementing ad-hoc mitigations instead (see Section 7.2 of the paper). Because of this, you must use the following two tests to check whether a device is _vulnerable_ to aggregation (A-MSDU) attacks (CVE-2020-24588):