When bsdinstall or bsdconfig are prompted to scan for nearby Wi-Fi networks, they build up a list of network names and use bsddialog(1) to prompt the user to select a network. This is implemented using a shell script, and the code which handled network names was not careful to prevent expansion by the shell. As a result, a suitably crafted network name can be used to execute commands via a subshell. The problem can be exploited to execute code as root on the system running bsdinstall or bsdconfig. The attacker would need to create an access point with a specially crafted name and be within range of a Wi-Fi scan. Note that bsdinstall and bsdconfig are vulnerable as soon as the user prompts them to scan for nearby networks; they do not need to actually select the malicious network.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:-:*:*:*:*:*:* | ||
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:p1:*:*:*:*:*:* | ||
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:p10:*:*:*:*:*:* | ||
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:p11:*:*:*:*:*:* | ||
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:p12:*:*:*:*:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
The average CVE in this peer group has 0.0 Twitter, 0.1 Reddit, 0.2 Bluesky, 0.1 Mastodon, and 0.1 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.2 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.