-
Notifications
You must be signed in to change notification settings - Fork 133
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Removed support for legacy CUPS browsing and for LDAP
Legacy CUPS browsing is not needed any more. this functionality got removed from CUPS with version 1.6, more than a decade ago. In cups-browsed it was implemented as a legacy support layer for servers or clients running long-term-support enterprise distributions still using CUPS 1.5.x or older. Now the support life of all these distributions should have expired and so this legacy support by cups-browsed is not needed any more. In addition, the legacy CUPS browsing implementation in cups-browsed was listening for UDP packaets on port 631 and by default it accepted packets from any source, making it easy for attackers to set up forged printers which could make use of vulnerabilities of CUPS or just find out about the identity and properties of clients. This is CVE-2024-47176: https://ubuntu.com/security/CVE-2024-47176 GHSA-rj88-6mr5-rcw8 https://openprinting.github.io/OpenPrinting-News-Flash-cups-browsed-Remote-Code-Execution-vulnerability/ Shortly after it was also found a another vulnerability of the legacy CUPS browsing support. It was possible to send a well-formed CUPS broadcast packet to UDP port 631 of cups-browsed, but with a port 80 URL of a web site which redirects on the port and then cups-browsed falls into an infinite loop sending HTTP requests which can only be stopped by "kill -9": GHSA-rq86-c7g6-r2h8 The removal of the legacy CUPS browsing support removes these 2 vulnerabilities. The LDAP implementation in cups-browsed does not follow the LDAP printer schema RFC 7612 and is therefore of very limited use.
- Loading branch information
1 parent
b7461ec
commit 6fd2bdf
Showing
6 changed files
with
54 additions
and
1,544 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.