This week we look at updates for vulnerabilities in wpa_supplicant, Samba, systemd, wget and more and we talk to Joe about IoT security (or the prevailing lack-thereof).
Show Notes
Overview
This week we look at updates for vulnerabilities in wpa_supplicant, Samba, systemd, wget and more and we talk to Joe about IoT security (or the prevailing lack-thereof).
Failure to properly sanitize environment before using XDG_SEAT
Attacker could set XDG_SEAT such that they can have actions checked
against the wrong PolicyKit policy
Allows a remotely logged in attacker (SSH) to run commands which should
be restricted to only physically present users
Fixed by using secure_getenv() rather than just getenv() - so that if
running via su the existing value is effectively scrubbed from the
environment and ignored
Episode 27 covered mod_auth_digest bypass for other supported releases
Also includes 3 other issues:
Nonce generated to prevent reply attacks for HTTP digest authentication
challenenge wasn’t sufficiently random
Could allow and attacker to reply across a cluster of servers with
the same common digest authentication configuration
changed to actually use a proper random source
Possible OOB read -> crash -> DoS
Possible one-byte memory corruption if specify a character encoding of
only 1 byte (since assumes is at least 2 bytes and so writes a NULL at
index +2 which could be past the end of the header) - crash, DoS
[USN-3944-1] wpa_supplicant and hostapd vulnerabilities
5 CVEs addressed in Trusty, Xenial, Bionic, Cosmic
Fix fallback to low-quality PRNG if failed to get an actual random value for a WPS pin
Multiple vulnerabilities discovered in the implementation of WPA3 in
hostapd and wpa_supplicant (aka Dragonblood)
2 apply to SAE (Simultaneous Authentication of Equals , also known as
Dragonfly Key Exchange) not relevant since we don’t enable SAE support
in our builds (this is used for initial key exchange instead of PSK)
4 apply to the use of EAP-PWD - Extensible Authentication Protocol
Password
cache side channel attack
reflection attack
may allow an attacker to authenticate without the password but
likely not derive session key or complete the key exchange so no
loss of confidentiality
2 failure to validate crypto components
could allow attacker to authenticate AND gain access to session key
and get network access
Symlink directory traversal issue - gem would delete the target
destination before creating any new directories or files when extracting
a Gem - as this is often run via sudo could allow to delete anything on
target system
Fixed to check target paths are symlinks
5 different code-injection attacks:
4 via injection of terminal escape sequences in debug code paths to stdout
Possible to execute arbitrary shell commands since failed to properly
sanitize environment variables and command-line arguments when executing
rsync or scp