OctoPrint up to 1.10.2 Web Interface unverified password change
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in OctoPrint up to 1.10.2. This impacts an unknown function of the component Web Interface. The manipulation results in unverified password change. This vulnerability was named CVE-2024-51493. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in OctoPrint up to 1.10.2. Affected is an unknown function of the component Web Interface. The manipulation with an unknown input leads to a unverified password change vulnerability. CWE is classifying the issue as CWE-620. When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
OctoPrint provides a web interface for controlling consumer 3D printers. OctoPrint versions up until and including 1.10.2 contain a vulnerability that allows an attacker that has gained temporary control over an authenticated victim's OctoPrint browser session to retrieve/recreate/delete the user's or - if the victim has admin permissions - the global API key without having to reauthenticate by re-entering the user account's password. An attacker could use a stolen API key to access OctoPrint through its API, or disrupt workflows depending on the API key they deleted. This vulnerability will be patched in version 1.10.3 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2024-51493 since 10/28/2024. The exploitability is told to be easy. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1552.
Upgrading to version 1.10.3 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (GitHub_M): 🔍
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: 🔍
Exploiting
Class: Unverified password changeCWE: CWE-620 / CWE-640
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: OctoPrint 1.10.3
Timeline
10/28/2024 🔍11/05/2024 🔍
11/05/2024 🔍
12/18/2024 🔍
Sources
Product: github.comAdvisory: GHSA-cc6x-8cc7-9953
Status: Confirmed
CVE: CVE-2024-51493 (🔍)
GCVE (CVE): GCVE-0-2024-51493
GCVE (VulDB): GCVE-100-283248
Entry
Created: 11/05/2024 20:48Updated: 12/18/2024 17:57
Changes: 11/05/2024 20:48 (63), 12/18/2024 17:57 (12)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.