Re:You're probably not vulnerable to the CUPS CVE
by andersa on Friday September 27, 2024 @07:18AM
(#41668993)
Why is your printer exposed on your public IP?
[ Parent
| on HN ]
Re:You're probably not vulnerable to the CUPS CVE
by PedroBatista on Friday September 27, 2024 @07:31AM
(#41669090)
Do you really think out of the millions upon millions of installations with wildly diverse contexts and situations all the people including the unsuspecting users CHOOSE to "expose the printer to a public IP"?
Seriously, how are we still at this level of discussion?
Re:You're probably not vulnerable to the CUPS CVE
by andersa on Friday September 27, 2024 @07:43AM
(#41669181)
I am simply confused how it happened, because every consumer router I have ever used in the past decade defaults to not exposing devices.
Re:You're probably not vulnerable to the CUPS CVE
by anttihaapala on Friday September 27, 2024 @07:47AM
(#41669233)
IPv6?! The big thing about this was that you'd have end-to-end connections without NAT etc.
Re:You're probably not vulnerable to the CUPS CVE
by dathinab on Friday September 27, 2024 @08:15AM
(#41669510)
Which still doesn't mean exposing everything publicly, but that is a different discussion.
In general I agree, most people affected probably didn't choose to expose the port it just "somehow accidentally happened".
Re:You're probably not vulnerable to the CUPS CVE
by yjftsjthsd-h on Friday September 27, 2024 @08:48AM
(#41669799)
IPv6 doesn't mean no firewall.
Re:You're probably not vulnerable to the CUPS CVE
by shakna on Friday September 27, 2024 @11:52AM
(#41672061)
The wonderful setup of Telstra's Technicolor, at least the one I'm mandated to use by some great NBN contracting, automatically exposes:
+ All ports below 505.
+ Any port requested by NAT.
+ Any DynDNS request.
The printer made a NAT request, and now it's public.