OctoPrint up to 1.3.9 Service Port 8081 HTTP Requests information disclosure ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in OctoPrint up to 1.3.9. This issue affects some unknown processing of the component Service Port 8081. Executing a manipulation as part of HTTP Requests can lead to information disclosure. The identification of this vulnerability is CVE-2018-16710. The attack may be launched remotely. There is no exploit available. The actual existence of this vulnerability is currently in question. The application of restrictive firewalling is recommended.
Details
A vulnerability has been found in OctoPrint up to 1.3.9 and classified as critical. This vulnerability affects an unknown functionality of the component Service Port 8081. The manipulation as part of a HTTP Requests leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
** DISPUTED ** OctoPrint through 1.3.9 allows remote attackers to obtain sensitive information or cause a denial of service via HTTP requests on port 8081. NOTE: the vendor disputes the significance of this report because their documentation states that with "blind port forwarding ... Putting OctoPrint onto the public internet is a terrible idea, and I really can't emphasize that enough."
The weakness was shared 09/07/2018 (Website). The advisory is available at github.com. This vulnerability was named CVE-2018-16710 since 09/07/2018. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
The real existence of this vulnerability is still doubted at the moment.
Proper firewalling of tcp/8081 is able to address this issue.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
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.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
CNA Base Score: 9.1
CNA 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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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: FirewallStatus: 🔍
0-Day Time: 🔍
Firewalling: 🔍
Timeline
09/07/2018 🔍09/07/2018 🔍
09/07/2018 🔍
09/08/2018 🔍
08/05/2024 🔍
Sources
Advisory: 2814Status: Not defined
Disputed: 🔍
CVE: CVE-2018-16710 (🔍)
GCVE (CVE): GCVE-0-2018-16710
GCVE (VulDB): GCVE-100-123754
Entry
Created: 09/08/2018 08:43Updated: 08/05/2024 16:00
Changes: 09/08/2018 08:43 (40), 03/21/2020 17:43 (18), 05/07/2023 15:03 (4), 08/05/2024 16:00 (28)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.