Vulnerabilities / Threats

7/25/2017
06:45 PM
50%
50%

How 'Postcript' Exploits Networked Printers

At Black Hat 2017, a university researcher will demo how attackers can drill into networked printers by way of the ubiquitous PostScript programming language.

Network printer exploits are like old dogs learning new tricks, according to a security researcher with Ruhr University.

In his upcoming Black Hat presentation, Exploiting Network Printers, Jens Muller, Ruhr University chair for network and data security will delve into an analysis of printer attacks, in which he discovered 20 printer models were all vulnerable to at least one of the same attacks that he tested. Muller will also disclose unusual ways the Internet is enabling network printer attacks via advanced cross-site printing techniques.

The vulnerability, Muller says, stems from the 35-year-old PostScript programming language, which has connected printers to end-users for decades, even as technology evolved from the parallel printer cable, to the USB stick, to networked printers, and today to the cloud.

"Before, printers used parallel cables and having PostScript wasn't a problem." Muller says. "But now, the printer manufacturers are still using PostScript and they can easily be exploited remotely."

PostScript: An Industry Standard 

The PostScript programming language is an industry standard for network printers and its use is ubiquitous. But despite attackers ability to exploit this language, printer manufacturers have largely looked the other way, he says. Instead, manufacturers put the onus on network administrators to place the printers inside the network, where the devices are presumed to be protected from outside threats.

Even today, he notes, manufacturers do not seem to realize that attackers can drill into networked printers by way of the Internet.

On the networking side, network administrators tend to view their connected printers as nothing more than a printing device, as opposed to a potential vector of attack, he says, noting that the end result is that network admins may not think it's important to secure network printers.

Some of the attacks Muller has tested include a denial of service attack that damaged eight of the 20 printers he was testing. One new issue to emerge is the ability to set a printer back to its factory defaults by taking control of the printer remotely. Other printer attacks range from stealing print jobs containing sensitive information to pilfering system files.

Work Arounds

One potential solution to the problem, Muller says, is to corral all the connected printers and put them on a separate network with a print server. The downside: it would require a network administrator to oversee two networks, which, he says, could be difficult for midsized companies and result in the additional costs of installing and monitoring a second firewall.

"What CISOs should really do is ask themselves do they really need a device connected," Muller says. "It may make sense not to connect the printer to the cloud."

Related Content:

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET's ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Major International Airport System Access Sold for $10 on Dark Web
Kelly Sheridan, Staff Editor, Dark Reading,  7/11/2018
Mueller Probe Yields Hacking Indictments for 12 Russian Military Officers
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/13/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Cyberspace is much less secure than my old lamp.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14363
PUBLISHED: 2018-07-17
An issue was discovered in NeoMutt before 2018-07-16. newsrc.c does not properly restrict '/' characters that may have unsafe interaction with cache pathnames.
CVE-2018-14349
PUBLISHED: 2018-07-17
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a NO response without a message.
CVE-2018-14350
PUBLISHED: 2018-07-17
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/message.c has a stack-based buffer overflow for a FETCH response with a long INTERNALDATE field.
CVE-2018-14351
PUBLISHED: 2018-07-17
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a long IMAP status mailbox literal count size.
CVE-2018-14352
PUBLISHED: 2018-07-17
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap_quote_string in imap/util.c does not leave room for quote characters, leading to a stack-based buffer overflow.