| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SICK APU. It has been rated as critical. The affected element is an unknown function of the component RDT400. The manipulation leads to modification of assumed-immutable data. This vulnerability is uniquely identified as CVE-2023-43697. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in SICK APU (version unknown). It has been rated as critical. This issue affects an unknown function of the component RDT400. The manipulation with an unknown input leads to a modification of assumed-immutable data vulnerability. Using CWE to declare the problem leads to CWE-471. The product does not properly protect an assumed-immutable element from being modified by an attacker. Impacted is integrity, and availability. The summary by CVE is:
Modification of Assumed-Immutable Data (MAID) in RDT400 in SICK APU allows an unprivileged remote attacker to make the site unable to load necessary strings via changing file paths using HTTP requests.
The weakness was disclosed 10/09/2023 as sca-2023-0010. The advisory is shared at sick.com. The identification of this vulnerability is CVE-2023-43697 since 09/21/2023. 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 10/09/2023).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.5
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
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: Modification of assumed-immutable dataCWE: CWE-471
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/21/2023 🔍10/09/2023 🔍
10/09/2023 🔍
10/09/2023 🔍
Sources
Advisory: sca-2023-0010Status: Confirmed
CVE: CVE-2023-43697 (🔍)
GCVE (CVE): GCVE-0-2023-43697
GCVE (VulDB): GCVE-100-241577
Entry
Created: 10/09/2023 15:42Changes: 10/09/2023 15:42 (47)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.