- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
WPA2-PSK security type PTK reinstallation in 4-way handshake using the same ANonce is succeeding when trying KRACKs. The understanding is for the WPA/WPA2-PSK the offloaded wpa_supplicant is doing the 4-way handshake with the Access Point. Could you please help us to understand how this 4-way hadhake is happening in the cypress chipset CYW4373. Why is the cypress chipset reconnecting with Access point when AP sends same ANonce message in the security vulnerability. Is there any setting we need to do to avoid key re-installation of same ANonce or Random ANonce in the chipset. In Linux OS it rejects same ANonce but in Vxworks It is accepting and reconnecting to AP.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Cypress has reviewed recent reports on Wi-Fi security vulnerability outlined in CVE-2019-15126. Our customers can receive updates by creating a support case through our secure support portal or by contacting their Cypress representative.
If you believe you have identified a vulnerability in any Cypress product, please visit our security response page https://www.cypress.com/report-security-vulnerabilities and email the Product Security Incident Response Team (PSIRT) at psirt@cypress.com.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Cypress has reviewed recent reports on Wi-Fi security vulnerability outlined in CVE-2019-15126. Our customers can receive updates by creating a support case through our secure support portal or by contacting their Cypress representative.
If you believe you have identified a vulnerability in any Cypress product, please visit our security response page https://www.cypress.com/report-security-vulnerabilities and email the Product Security Incident Response Team (PSIRT) at psirt@cypress.com.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have identified the cause and rectified the issue. It was a minor mistake in our device side. Thank you for the reply.