this post was submitted on 23 Feb 2024
277 points (98.6% liked)

Technology

59161 readers
2119 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
277
Two Wi-Fi flaws expose Android, Linux devices to attacks (thehackernews.com)
submitted 8 months ago* (last edited 8 months ago) by [email protected] to c/[email protected]
19 comments fedilink hide all child comments
 

Vulnerabilities:

CVE-2023-52160 (wpa_supplicant) and CVE-2023-52161 (Intel's iNet Wireless Daemon) allow attackers to:

  • Trick users into joining fake Wi-Fi networks: Attackers can create malicious clones of legitimate networks and steal user data.
  • Gain unauthorized access to secure Wi-Fi networks: Attackers can join password-protected networks without needing the password, putting devices and data at risk.

Affected devices:

  • CVE-2023-52160: Android devices using wpa_supplicant versions 2.10 and prior (requires specific configuration).
  • CVE-2023-52161: Linux devices using iNet Wireless Daemon versions 2.12 and lower (any network using a Linux access point).

Mitigation:

  • Update your Linux distribution and ChromeOS (version 118 or later).
  • Android fix not yet available, but manually configure CA certificate for any saved enterprise networks as a temporary workaround.

Exploitation:

  • Attacker needs SSID and physical proximity for CVE-2023-52160.
  • CVE-2023-52161 requires no special knowledge, affecting any vulnerable network.

Links:

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 11 points 8 months ago (2 children)

Hmm how would one know if their specific AP is affected? Lots of manufacturers won’t release updates.

[–] [email protected] 10 points 8 months ago* (last edited 8 months ago) (1 children)

TL;DR: If you're using a linux based AP, check if you're using iwd. If you are, you need to update immediately. Alternatively, if you're using an OpenWRT based router you're good.

It's not clear to me yet if this is specific to intel wireless devices (edit: the IWD wiki page says that it aims to be "a comprehensive Wi-Fi connectivity solution for Linux based devices" so it looks like it would cover any system using IWD, not just Intel AP's).

The article says "everyone using IWD as an access point" and "affects home WiFi networks".

So I went to the good ol' Arch wiki and it gives some details on iwd:

https://wiki.archlinux.org/title/Iwd

Long story short it looks like at a minimum you would need the iwd package installed on a linux based access point (think open source based routers and probably many ISP ones) and an easy way to test for that appears to be if the apps iwctl, iwd and / or iwmon are anywhere on the system (and / or if iwd is running).

If you run

ps -ef | grep iwd

on a normal linux box or

ps w | grep iwd

on openwrt based routers it should give you a clear indication.

The linux based router I'm using here has iw and iwlist but they're for a separate package and no iwd daemon running.

I am still digging on this and will be until I'm happy.

update: iwd 2.13 is vulnerable and was released 2024/01/12 so unless you're bang up to date, if you're using iwd you're exposed.

update: even newer versions of OpenWRT don't appear to use IWD.

[–] [email protected] 3 points 8 months ago (1 children)

Thanks a bunch

[–] [email protected] 3 points 8 months ago

No worries. :) It was a bit rambling there for a while but I finally got to the bottom of it all.

The article and / or CVE could have done a much better job of making it clear who wasn't affected or at least how to check if you are.

[–] [email protected] 3 points 8 months ago (1 children)

If these CVEs didn't expose a router that doesn't get updates, many others already have. OpenWRT might be more secure than OEM firmware.

[–] [email protected] 2 points 8 months ago

Unfortunately my AP doesn’t support OpenWRT.