Trusted Firmware-A up to 2.8 X.509 Parser out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Trusted Firmware-A up to 2.8. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the component X.509 Parser. This manipulation causes out-of-bounds. The identification of this vulnerability is CVE-2022-47630. There is no exploit available.
Details
A vulnerability classified as problematic was found in Trusted Firmware-A up to 2.8 (Firmware Software). Affected by this vulnerability is an unknown function of the component X.509 Parser. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality. The summary by CVE is:
Trusted Firmware-A through 2.8 has an out-of-bounds read in the X.509 parser for parsing boot certificates. This affects downstream use of get_ext and auth_nvctr. Attackers might be able to trigger dangerous read side effects or obtain sensitive information about microarchitectural state.
The weakness was shared 01/16/2023. The advisory is shared at trustedfirmware-a.readthedocs.io. This vulnerability is known as CVE-2022-47630 since 12/20/2022. Neither technical details nor an exploit are publicly available.
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
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.1
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.4
NVD Vector: 🔍
ADP CISA Base Score: 7.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: 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
12/20/2022 🔍01/16/2023 🔍
01/16/2023 🔍
06/06/2026 🔍
Sources
Advisory: trustedfirmware-a.readthedocs.ioStatus: Confirmed
CVE: CVE-2022-47630 (🔍)
GCVE (CVE): GCVE-0-2022-47630
GCVE (VulDB): GCVE-100-218449
Entry
Created: 01/16/2023 19:42Updated: 06/06/2026 00:54
Changes: 01/16/2023 19:42 (15), 01/16/2023 19:43 (23), 02/09/2023 08:23 (11), 11/27/2024 21:15 (16), 06/06/2026 00:54 (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.