Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Printers: The Weak Link in Enterprise Security
Threaded  |  Newest First  |  Oldest First
AlyssaTallent
50%
50%
AlyssaTallent,
User Rank: Apprentice
10/16/2017 | 11:49:53 AM
Great
Ohhh that is pretty interesting 
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
10/17/2017 | 7:43:51 AM
A simple google search
Years ago there was published a simple, extended search string for Google that browsed the internal web page of millions of Officejet printers.  Fantastic.  Tried it and the pages were displayed along with internal IP settings which, for a hacker, is an open door.  I did not purposefully remember it but I am not surprised that printers are a wide open door.  
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
10/22/2017 | 10:53:24 AM
Re: A simple google search
Even beyond Google, there's Shodan for finding exposed embedded devices -- printers and otherwise. Security researchers have relied on Shodan quite a bit to pull off some interesting research/exposes.
glennjdavis
50%
50%
glennjdavis,
User Rank: Apprentice
10/20/2017 | 7:34:49 AM
hi
hi
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
10/21/2017 | 3:35:53 PM
For years
This has been an issue for quite a number of years, unfortunately. Printer vulnerabilities -- either because of poor enterprise practices or because of manufacturers not paying enough attention to their products -- really brought some attention the security weaknesses of embedded devices before the proliferation of IoT. Too bad manufacturers and enterprises didn't listen.
Olaf Barheine
50%
50%
Olaf Barheine,
User Rank: Apprentice
10/23/2017 | 4:32:10 AM
Wow!
I think I should switch my old printer from RJ45 to USB. A security test with NMAP showed that it's open like a barn door. And new firmware is not more available.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.