Difference between revisions of "Fax and Scanner"
| Line 33: | Line 33: | ||
== Scanner == | == Scanner == | ||
| − | Access to scan functionality on MFPs is not standardized and it seems only few vendors apply PJL commands for this task. Public documentation is missing, the [http://www.sane-project.org/sane-backends.html#SCANNERS SANE project] | + | Access to scan functionality on MFPs is not standardized and it seems only few vendors apply PJL commands for this task. Public documentation is missing, the [http://www.sane-project.org/sane-backends.html#SCANNERS SANE project] managed to reverse engineer various scanner devices. On Brother devices, the proprietary PostScript operator '''_brpdfscan''' may possibly be used. |
Revision as of 12:21, 5 January 2017
While single function printers are still common there is clearly a trend towards multi-function printers/peripherals (MFP), also referred to as multi-function devices (MFD) or all-in-one (AiO) devices, which have additional built-in functions like scanning and/or telefax.
Telefax
Fax messages are transmitted in the form of audio-frequency tones. They can be sent to any telefax-capable device available over the telephone system. Therefore, they could potentially be used to bypass typical company protection mechanisms like TCP/IP firewalls or intrusion detection systems and execute malicious commands on printers or MFPs in internal networks. In the middle of 90s Adobe introduced ‘PostScript fax’ as a language supplement [1], allowing compatible devices to receive PostScript files directly via fax. This enables an attacker to use ordinary telephone system as a channel to deploy malicious PostScript code to a printer. Unfortunately, PostScript fax never established itself and was only implemented in a handful of devices. Telefax messages instead are typically transmitted as graphical images like TIFF. Nevertheless, it cannot be ruled out that other vendors implement proprietary fax extensions to inbound receive arbitrary PDL datastreams instead of raw fax images. Theoretically, a ‘fax virus’ could be created which would spread by infecting other devices based on numbers from the MFPs's address book or by traditional wardialing.
Furthermore, outbound fax can often be controlled by proprietary PJL commands on today's MFPs. This can be used to cause financial loss to an institution by calling an 0900 number (which may be registered by the attacker herself) or as a backchannel to leak sensitive information. Examples are given below (mostly untested).
HP
According to [1] fax can be accessed using PML on HP devices.
Xerox
According to [2], Xerox uses proprietary PJL commands: @PJL COMMENT OID_ATT_FAX_DESTINATION_PHONE "..."
Brother
According to [3], Brother uses the proprietary FCL (Fax Control Language): <Esc>DIALNUM[ (...) ]
Lexmark
According to [4] Lexmark uses proprietary PJL commands: @PJL LFAX PHONENUMBER="..."
Kyocera
According to [5] Kyocera uses proprietary PJL commands: @PJL SET FAXTEL = ...
Ricoh
Accroding to [6] Ricoh uses proprietary PJL commands: @PJL ENTER LANGUAGE=RFAX
Scanner
Access to scan functionality on MFPs is not standardized and it seems only few vendors apply PJL commands for this task. Public documentation is missing, the SANE project managed to reverse engineer various scanner devices. On Brother devices, the proprietary PostScript operator _brpdfscan may possibly be used.- ↑ Adobe Systems Inc., PostScript Language Reference Manual Supplement for Version 2016, (1995), 18-35.
