HP Ink Printers Remote Code Execution
support.hp.com
support.hp.com
Whereas with our Brother laser printer, I couldn't tell you the last time I bought toner, or gave that printer much thought at all other than grabbing a sheet off the print tray.
I make sure the printer supports AirPrint and "it just works" with Macs, and my IOS devices -- including my ancient circa 2010 iPad that hasn't seen an update in 7 years (yeah I got a newer iPad also).
In this time I have had enough inexplicable printer-related problems, that my views on printing are no longer fit for a public forum. If I could, I would go Office Space on each and every one of those hellish machines.
But I need to remember, it's not the printer's fault, it's Windows - on GNU/Linux, printing has Just Worked(tm) for me for the last ... about ten years. Once upon a time I was reduced to converting my print jobs to the printer's native language with Ghostscript and then cat(1) the resulting files (one per page) to the printer's device file. But then came CUPS, and while some people still complain that GNU/Linux is not suitable for desktop use, when it comes to printing the experience is lightyears ahead of Windows.
I have three printers at home (long story). I bring a Mac home, connect it to my network and it finds all three and I can immediately start printing. I bring home a Windows PC, I have to install printer drivers for three printers.
Well, guess what - vendor-supplied drivers suck donkey-balls, while third-party drivers (as supplied by CUPS or GhostScript) focus on supporting the functionality the printer in question provides and nothing else.
It's the same as with GPUs, except that printers are (AFAICT) less complicated than GPUs.
In theory, Windows can do some things you can not replicate on GNU/Linux and/or macOS without major pain - e.g. that client submit their print jobs in b/w unless specifically requested otherwise (because on our support contract, color printing costs ~10x as much per page as b/w). In practice, though, it works about as reliably as trying to photograph a specific star in the sky while blindfolded and with - at best - a fuzzy idea what day it is.
People keep telling me that Windows is a superior OS for desktop systems because it "just works", but clearly those people do not do a lot of printing. ;-)
In general though I agree, it's a mess and as a developer of output management software it causes me no end of problems.
I suspect the real story is that per-device drivers allow you to patch around a lot of stupid or wrong behavior on the hardware side, and on the low end, let the host do most of the image processing so the printer itself can be little more than a bag of dumb stepper motors and servos.
When Apple convinced printer manufacturers to support AirPrint in 2010, iOS wasn’t nearly as ubiquitous. You can find a fair amount of printers that support Google Cloud Print natively.
EDIT:
After reading a little bit more. It really is the fault of the vendors. MS tried to simplify it.
https://blog.thinprint.com/the-new-microsoft-v4-printer-driv...
One advantage Apple had was that printers had to be compatible with AirPrint without drivers for them to work on iOS, the Mac was able to piggyback off of that.
The best printer decision I've ever made is my current printer, an HP OfficeJet 8620 with an ink subscription program. This HP has printed 9620 trouble-free pages since I purchased it a bit over two years ago (May, 2016). Yes, the per-page cost is relatively expensive, but it's the least hassle I've ever had with a printer. New ink just magically shows up in the mail shortly before I need it and I mail the old cartridges back for recycling. I haven't heard "honey/dad, the printer is broken/jammed/out-of-ink/won't-print again" since I purchased it.
My first printer was an Apple thermal printer, my second an Epson MX 100, so I've dealt with _a lot_ of printers over the years, from Apple, Epson, Canon, Brother, HP, and maybe other brands I'm forgetting.
I previously tried things like bulk ink tanks and refilling toner cartridges. Not worth the hassle.
I'm glad you're happy with your Brother. Mine had great initial reviews, but then when I checked back on Amazon a year later other folks has the same fuser roller issue:
https://www.amazon.com/gp/customer-reviews/R16HGOAIYLS1IJ/re...
Maybe it was specific to that model (HL-3170CDW). I don't know.
http://fixitfastelectronics.com/mfc9330cdw-9140cdn-emboss.ht...
The TLDR there is that the HL-3170CDW has a sharper-than-normal lift off angle from the fuser roller (the part that fails). Inexpensive toner is more sticky than the Brother-brand toner, so it causes undue fatigue on the part.
We had this same issue happen to us about 1000 pages after switching to an ultra-cheap, pour-in toner option. We first replaced the roller with a cheap one from Ebay that ended up causing the printer to overheat. Then we bought a custom manufactured roller from the aforementioned Australian company. That one has lasted us more than 3000 page so far, even with the cheap toner.
Note: if you elect to change the roller yourself, don't touch the heating element / bulb inside of the roller with your fingers!
Obviously some people need to print a lot of stuff but I'd wager half the people with home printers would be better off without.
[1] https://www.youtube.com/watch?v=njVv7J2azY8 [2] http://gawker.com/5863388/hackers-could-turn-your-printer-in...
>Two security vulnerabilities have been identified with certain HP Inkjet printers.
and then list more than 200 (two hundred) printer models.
It seems to me that the given list could be better summed up with something like:
"All HP Inkjet printers manufactured in the last n years, with the exception of models A, B and C"."
Some were too old for this vulnerability?
More practically, a 3D printer is probably only a half step removed from a decent plotter if you just replace the head with a pen or something.
> HP has provided firmware updates for impacted printers as set forth in the table below.
> HP has provided firmware updates for impacted printers as set forth in the table below.
Printers should be on a seperate subnet, firewalled off to oncy accept incoming connections (and maybe outbound to specific radius and SMTP servers), and not given internet access.
The printer I work with these days will phone for supplies that tend to arrive the day before the toner runs out.
Although I imagine the network connection could be replaced with a phone line, but there’s only one landline in this company of 500+ people and I’m using it for something else.
But yeah, we keep our printers on the same network segment as the clients. Maybe we should change that. Then again, I have enough on my plate as it is.
You’d be surprised. One org I worked for had a Kyocera all kitted our for HIPAA compliance.
I looked through the manual for it once and it glossed over a number of very interesting data handling techniques. The only one I remember off the top of my head is that after a print job, the internal hard drive would scrub itself and repeatedly write garbage data over the location of the previous print job.
To the user it was seamless, except for the occasional tiny “Purging hard drive data” notice at the bottom of the printer’s screen.
Defcon presentation from Defcon 19 (I swear I remember something earlier than this, but this is just from a quick search) https://www.defcon.org/images/defcon-19/dc-19-presentations/...
Does PRET even still work? I'd be surprised if the vulnerabilities that allow PRET to work haven't been patched.