{"vulnerability": "CVE-2024-43841", "sightings": [{"uuid": "d92780d4-0eb0-489f-9fb2-f96a719dbbb1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43841", "type": "seen", "source": "https://t.me/cvedetector/3423", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43841 - \"Wifi Virt_wifi SSID Spoofing Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-43841 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: virt_wifi: avoid reporting connection success with wrong SSID  \n  \nWhen user issues a connection with a different SSID than the one  \nvirt_wifi has advertised, the __cfg80211_connect_result() will  \ntrigger the warning: WARN_ON(bss_not_found).  \n  \nThe issue is because the connection code in virt_wifi does not  \ncheck the SSID from user space (it only checks the BSSID), and  \nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS  \neven if the SSID is different from the one virt_wifi has advertised.  \nEventually cfg80211 won't be able to find the cfg80211_bss and generate  \nthe warning.  \n  \nFixed it by checking the SSID (from user space) in the connection code. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:18.000000Z"}]}