Trusted Firmware-A up to 2.9 SDEI Service sdei_interrupt_bind out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Trusted Firmware-A up to 2.9. Affected is the function sdei_interrupt_bind of the component SDEI Service. The manipulation results in out-of-bounds.
This vulnerability was named CVE-2023-49100. There is no available exploit.
The affected component should be upgraded.
Details
A vulnerability was found in Trusted Firmware-A up to 2.9 (Firmware Software). It has been classified as problematic. Affected is the function sdei_interrupt_bind of the component SDEI Service. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. CVE summarizes:
Trusted Firmware-A (TF-A) before 2.10 has a potential read out-of-bounds in the SDEI service. The input parameter passed in register x1 is not validated well enough in the function sdei_interrupt_bind. The parameter is passed to a call to plat_ic_get_interrupt_type. It can be any arbitrary value passing checks in the function plat_ic_is_sgi. A compromised Normal World (Linux kernel) can enable a root-privileged attacker to issue arbitrary SMC calls. Using this primitive, he can control the content of registers x0 through x6, which are used to send parameters to TF-A. Out-of-bounds addresses can be read in the context of TF-A (EL3). Because the read value is never returned to non-secure memory or in registers, no leak is possible. An attacker can still crash TF-A, however.
The weakness was presented 02/21/2024. The advisory is available at trustedfirmware-a.readthedocs.io. This vulnerability is traded as CVE-2023-49100 since 11/21/2023. Technical details are known, but there is no available exploit.
Upgrading to version 2.10 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.1VulDB Meta Temp Score: 4.1
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.4
CNA Vector: 🔍
ADP CISA Base Score: 4.4
ADP CISA 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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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: Firmware-A 2.10
Timeline
11/21/2023 🔍02/21/2024 🔍
02/21/2024 🔍
04/15/2026 🔍
Sources
Advisory: trustedfirmware-a.readthedocs.ioStatus: Confirmed
CVE: CVE-2023-49100 (🔍)
GCVE (CVE): GCVE-0-2023-49100
GCVE (VulDB): GCVE-100-254418
Entry
Created: 02/21/2024 18:16Updated: 04/15/2026 17:37
Changes: 02/21/2024 18:16 (42), 11/01/2024 00:18 (27), 04/15/2026 17:37 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.