Amazing-Mirror/fragattacks
1
0
Fork 0
mirror of https://github.com/vanhoefm/fragattacks.git synced 2024-11-25 00:38:24 -05:00
Code Issues Projects Releases Wiki Activity

README: Further clarify A-MSDU tests

Browse Source
This commit is contained in:
vanhoefm 2021-06-26 03:01:22 +04:00 committed by GitHub
parent d07958d7f9
commit 67e72c1417
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -329,7 +329,8 @@ CVEs as a way to easily refer to each type of discovered implementation flaw.
<a id="id-test-amsdu"></a> <a id="id-test-amsdu"></a>
## 7.3. A-MSDU attack tests (§3 -- CVE-2020-24588) ## 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 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 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): the following two tests to check whether a device is _vulnerable_ to aggregation (A-MSDU) attacks (CVE-2020-24588):