Mitsubishi Electric MELSEC-Q/MELSEC-L Packet incorrect pointer scaling
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as very critical has been detected in Mitsubishi Electric MELSEC-Q and MELSEC-L. This impacts an unknown function of the component Packet Handler. Performing a manipulation results in incorrect pointer scaling. This vulnerability is identified as CVE-2024-0802. The attack can be initiated remotely. There is not any exploit available. It is suggested to use restrictive firewalling.
Details
A vulnerability, which was classified as very critical, was found in Mitsubishi Electric MELSEC-Q and MELSEC-L (affected version not known). This affects some unknown functionality of the component Packet Handler. The manipulation with an unknown input leads to a incorrect pointer scaling vulnerability. CWE is classifying the issue as CWE-468. In C and C++, one may often accidentally refer to the wrong memory due to the semantics of when math operations are implicitly scaled. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at cisa.gov. This vulnerability is uniquely identified as CVE-2024-0802. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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 03/15/2024).
It is possible to mitigate the weakness by firewalling .
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: 9.8VulDB Meta Temp Score: 9.7
VulDB Base Score: 9.8
VulDB Temp Score: 9.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (Mitsubishi Electric Corporation): 🔍
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: Incorrect pointer scalingCWE: CWE-468
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: 🔍
Timeline
01/23/2024 🔍03/15/2024 🔍
03/15/2024 🔍
04/15/2024 🔍
Sources
Advisory: icsa-24-074-14Status: Confirmed
CVE: CVE-2024-0802 (🔍)
GCVE (CVE): GCVE-0-2024-0802
GCVE (VulDB): GCVE-100-256881
Entry
Created: 03/15/2024 01:07Updated: 04/15/2024 15:19
Changes: 03/15/2024 01:07 (36), 04/15/2024 15:13 (16), 04/15/2024 15:19 (11)
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.