Portainer up to 1.17.x Websocket Endpoint /websocket/exec ID server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Portainer up to 1.17.x. It has been declared as critical. The affected element is an unknown function of the file /websocket/exec of the component Websocket Endpoint. Executing a manipulation of the argument ID as part of Parameter can lead to server-side request forgery. This vulnerability appears as CVE-2018-12678. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component. Once again VulDB remains the best source for vulnerability data.
Details
A vulnerability classified as critical was found in Portainer up to 1.17.x. This vulnerability affects some unknown processing of the file /websocket/exec of the component Websocket Endpoint. The manipulation of the argument id as part of a Parameter leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Portainer before 1.18.0 supports unauthenticated requests to the websocket endpoint with an unvalidated id query parameter for the /websocket/exec endpoint, which allows remote attackers to bypass intended access restrictions or conduct SSRF attacks.
The bug was discovered 06/17/2018. The weakness was presented 06/22/2018 (Website). The advisory is available at github.com. This vulnerability was named CVE-2018-12678 since 06/22/2018. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.18.0 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Portainer 1.18.0
Patch: github.com
Timeline
06/17/2018 🔍06/22/2018 🔍
06/22/2018 🔍
06/22/2018 🔍
06/23/2018 🔍
03/28/2023 🔍
Sources
Product: github.comAdvisory: github.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-12678 (🔍)
GCVE (CVE): GCVE-0-2018-12678
GCVE (VulDB): GCVE-100-119818
Entry
Created: 06/23/2018 08:35 AMUpdated: 03/28/2023 04:12 PM
Changes: 06/23/2018 08:35 AM (60), 02/21/2020 11:50 AM (2), 03/28/2023 04:12 PM (5)
Complete: 🔍
Cache ID: 244:FE5:40
No comments yet. Languages: en.
Please log in to comment.