ARM v8-M Security Extensions Requirements on Development Tools unexpected data type
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in ARM v8-M Security Extensions Requirements on Development Tools up to 1.3 and classified as problematic. This vulnerability affects unknown code. Performing a manipulation results in improper handling of unexpected data type. This vulnerability is reported as CVE-2024-0151. No exploit exists. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in ARM v8-M Security Extensions Requirements on Development Tools up to 1.3. This affects an unknown part. The manipulation with an unknown input leads to a improper handling of unexpected data type vulnerability. CWE is classifying the issue as CWE-241. The product does not handle or incorrectly handles when a particular element is not the expected type, e.g. it expects a digit (0-9) but is provided with a letter (A-Z). This is going to have an impact on integrity. The summary by CVE is:
Insufficient argument checking in Secure state Entry functions in software using Cortex-M Security Extensions (CMSE), that has been compiled using toolchains that implement 'Arm v8-M Security Extensions Requirements on Development Tools' prior to version 1.4, allows an attacker to pass values to Secure state that are out of range for types smaller than 32-bits. Out of range values might lead to incorrect operations in secure state due.
The advisory is shared at developer.arm.com. This vulnerability is uniquely identified as CVE-2024-0151 since 12/11/2023. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.4 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: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
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: 🔍
Exploiting
Class: Improper handling of unexpected data typeCWE: CWE-241 / CWE-229 / CWE-20
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: v8-M Security Extensions Requirements on Development Tools 1.4
Timeline
12/11/2023 🔍04/24/2024 🔍
04/24/2024 🔍
08/09/2024 🔍
Sources
Advisory: developer.arm.comStatus: Confirmed
CVE: CVE-2024-0151 (🔍)
GCVE (CVE): GCVE-0-2024-0151
GCVE (VulDB): GCVE-100-261957
Entry
Created: 04/24/2024 20:48Updated: 08/09/2024 22:28
Changes: 04/24/2024 20:48 (52), 08/09/2024 22:28 (13)
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.