As of writing there is no Linux fix available for this high profile security issue. In the meantime it’s recommended to disable and remove the “cups-browsed” service, updating CUPS, or at least blocking all traffic to UDP port 631.
Source:
https://www.phoronix.com/news/Linux-CVSS-9.9-Rating
https://www.evilsocket.net/2024/09/26/Attacking-UNIX-systems-via-CUPS-Part-I/
systemctl status cups-browsed to check if you have it enabled
sudo systemctl disable --now cups-browsed to stop/disable.
But with this you will not be able to use network printers added automatically, you may need to add network printer manually after this.
From what I see, firewalld has port 631/udp closed by default.
Check it:
sudo firewall-cmd --list-all
closing it would be something like:
sudo firewall-cmd --remove-port=631/udp --permanent
sudo firewall-cmd --reload
And keep in mind only just read about this, personally not the pro on these things, feel free to add knowledge.
And in case the most simple way is to uninstall:
sudo pacman -R cups-browsed
To be on the securest side you could also go uninstall cups all together:
sudo pacman -Rc cups cups-browsed
(Check what it shows before proceed as of -c cascading option)
// edit//
The problem should already been solved by updating to cups-browsed-2.0.1-2.
Do your own research in addition!
With:
upgpkg: 2.0.1-2; don’t browse old cups protocol by default - CVE-2024-47176
https://gitlab.archlinux.org/archlinux/packaging/packages/cups/-/commit/494250067a97981fd1f56c5d6892a7584b4b0c9e
cups-browsed 2.0.1-2
The issue should be resolved (if it was a real issue in the first place)
https://access.redhat.com/security/cve/cve-2024-47176
This is exploitable from outside the LAN if the computer is exposed on the public internet.
(only as a sidenote)
Some helpful info from this post Cups is affected by a security vulnerability [26 September 2024] - #36 by andrewb