Bug 2314994 - CVE-2024-47176 binds on UDP INADDR_ANY:631 trusting any packet from any source to trigger a Get-Printer-Attributes IPP request to an attacker controlled URL
Summary: CVE-2024-47176 binds on UDP INADDR_ANY:631 trusting any packet from any sourc...
Keywords:
Status: CLOSED DUPLICATE of bug 2314996
Alias: None
Product: Fedora
Classification: Fedora
Component: cups-browsed
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact:
URL: https://www.evilsocket.net/2024/09/26...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-26 20:05 UTC by Daniel Milnes
Modified: 2024-09-26 21:36 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-09-26 21:36:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Daniel Milnes 2024-09-26 20:05:36 UTC
CVE-2024-47176 | cups-browsed <= 2.0.1 binds on UDP INADDR_ANY:631 trusting any packet from any source to trigger a Get-Printer-Attributes IPP request to an attacker controlled URL.
CVE-2024-47076 | libcupsfilters <= 2.1b1 cfGetPrinterAttributes5 does not validate or sanitize the IPP attributes returned from an IPP server, providing attacker controlled data to the rest of the CUPS system.
CVE-2024-47175 | libppd <= 2.1b1 ppdCreatePPDFromIPP2 does not validate or sanitize the IPP attributes when writing them to a temporary PPD file, allowing the injection of attacker controlled data in the resulting PPD.
CVE-2024-47177 | cups-filters <= 2.0.1 foomatic-rip allows arbitrary command execution via the FoomaticRIPCommandLine PPD parameter.

https://www.evilsocket.net/2024/09/26/Attacking-UNIX-systems-via-CUPS-Part-I/

Still reading through these, but they've been hyped in the press all week. It would appear that they only matter if CUPS is network-exposed.

Reproducible: Always

Comment 1 Nick Tait 2024-09-26 21:36:36 UTC
Closing this as a dupe, in place of the official tracker.

*** This bug has been marked as a duplicate of bug 2314996 ***


Note You need to log in before you can comment on or make changes to this bug.