Applicability / Mitigation Matrix Request
kranzrm opened this issue · 2 comments
First, thank you for your contributions to information security.
Many organizations are trying to understand how to fully mitigate this vulnerability. It is very clear that there is an inherent issue with the 4-way handshake as defined in the standard. However, it is unclear how this can be effectively mitigated. Obviously, patching ALL supplicants and authenticators will address the issue. But, it would be very helpful to understand where organizations can focus their efforts for best risk reduction.
From the paper, it appears that the wireless controllers can effectively prevent the client from using old replay counter. But, it is not clear (for those of us less familiar with the nuances of this technology) to understand exactly what is vulnerable and where the issue can be mitigated.
I think something like the below table would provide an incredible value to organizations (IT/Security Teams), helping us understand the risk and prioritize efforts. The table is meant to answer the question: "Which CVEs require me to patch just my authenticators to protect my network? Which ones require both?"
Some example values are filled in for each CVE to show what I was thinking.
| CVE | Vulnerable Component | Patch Needed |
|---|---|---|
| CVE-2017-13077 | Both | Supplicant |
| CVE-2017-13078 | Supplicant | Either |
| CVE-2017-13079 | Authenticator | Both |
| CVE-2017-13080 | ||
| CVE-2017-13081 | ||
| CVE-2017-13082 | ||
| CVE-2017-13084 | ||
| CVE-2017-13086 | ||
| CVE-2017-13087 | ||
| CVE-2017-13088 |
This would be a boon for the community.
From my current understanding, most of the burden is placed on the side of the client.