SICK InspectorP61x/InspectorP62x up to 4.x Firmware Update reliance on obfuscation or encryption of security-relevant inputs without integrity checking
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as very critical, has been found in SICK InspectorP61x and InspectorP62x up to 4.x. This affects an unknown function of the component Firmware Update Handler. The manipulation leads to reliance on obfuscation or encryption of security-relevant inputs without integrity checking. This vulnerability is documented as CVE-2024-10772. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in SICK InspectorP61x and InspectorP62x up to 4.x and classified as very critical. This issue affects an unknown functionality of the component Firmware Update Handler. The manipulation with an unknown input leads to a reliance on obfuscation or encryption of security-relevant inputs without integrity checking vulnerability. Using CWE to declare the problem leads to CWE-649. The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Since the firmware update is not validated, an attacker can install modified firmware on the device. This has a high impact on the availabilty, integrity and confidentiality up to the complete compromise of the device.
The weakness was released by Manuel Stotz. The identification of this vulnerability is CVE-2024-10772 since 11/04/2024. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/06/2024).
Upgrading to version 5.0.0 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.6
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (SICK AG): 🔍
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: Reliance on obfuscation or encryption of security-relevant inputs without integrity checkingCWE: CWE-649 / CWE-325
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: InspectorP61x/InspectorP62x 5.0.0
Timeline
11/04/2024 🔍12/06/2024 🔍
12/06/2024 🔍
12/06/2024 🔍
Sources
Researcher: Manuel StotzStatus: Confirmed
CVE: CVE-2024-10772 (🔍)
GCVE (CVE): GCVE-0-2024-10772
GCVE (VulDB): GCVE-100-287141
Entry
Created: 12/06/2024 16:17Changes: 12/06/2024 16:17 (63)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.