Acer Altos T110 F3 UEFI DXE Driver stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Acer Altos T110 F3, AP130 F2, Aspire 1600X, Aspire 1602M, Aspire 7600U, Aspire MC605, Aspire TC-105, Aspire TC-120, Aspire U5-620, Aspire X1935, Aspire X3475, Aspire X3995, Aspire XC100, Aspire XC600, Aspire Z3-615, Veriton E430G, Veriton B630_49, Veriton E430 and Veriton M2110G. It has been classified as critical. The affected element is an unknown function of the component UEFI DXE Driver. This manipulation causes stack-based overflow. This vulnerability is tracked as CVE-2022-30426. No exploit exists.
Details
A vulnerability was found in Acer Altos T110 F3, AP130 F2, Aspire 1600X, Aspire 1602M, Aspire 7600U, Aspire MC605, Aspire TC-105, Aspire TC-120, Aspire U5-620, Aspire X1935, Aspire X3475, Aspire X3995, Aspire XC100, Aspire XC600, Aspire Z3-615, Veriton E430G, Veriton B630_49, Veriton E430 and Veriton M2110G. It has been declared as critical. Affected by this vulnerability is an unknown code block of the component UEFI DXE Driver. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
There is a stack buffer overflow vulnerability, which could lead to arbitrary code execution in UEFI DXE driver on some Acer products. An attack could exploit this vulnerability to escalate privilege from ring 3 to ring 0, and hijack control flow during UEFI DXE execution. This affects Altos T110 F3 firmware version <= P13 (latest) and AP130 F2 firmware version <= P04 (latest) and Aspire 1600X firmware version <= P11.A3L (latest) and Aspire 1602M firmware version <= P11.A3L (latest) and Aspire 7600U firmware version <= P11.A4 (latest) and Aspire MC605 firmware version <= P11.A4L (latest) and Aspire TC-105 firmware version <= P12.B0L (latest) and Aspire TC-120 firmware version <= P11-A4 (latest) and Aspire U5-620 firmware version <= P11.A1 (latest) and Aspire X1935 firmware version <= P11.A3L (latest) and Aspire X3475 firmware version <= P11.A3L (latest) and Aspire X3995 firmware version <= P11.A3L (latest) and Aspire XC100 firmware version <= P11.B3 (latest) and Aspire XC600 firmware version <= P11.A4 (latest) and Aspire Z3-615 firmware version <= P11.A2L (latest) and Veriton E430G firmware version <= P21.A1 (latest) and Veriton B630_49 firmware version <= AAP02SR (latest) and Veriton E430 firmware version <= P11.A4 (latest) and Veriton M2110G firmware version <= P21.A3 (latest) and Veriton M2120G fir.
The weakness was disclosed 09/23/2022. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2022-30426 since 05/09/2022. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/28/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
- Altos T110 F3
- AP130 F2
- Aspire 1600X
- Aspire 1602M
- Aspire 7600U
- Aspire MC605
- Aspire TC-105
- Aspire TC-120
- Aspire U5-620
- Aspire X1935
- Aspire X3475
- Aspire X3995
- Aspire XC100
- Aspire XC600
- Aspire Z3-615
- Veriton B630_49
- Veriton E430
- Veriton E430G
- Veriton M2110G
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.9VulDB Meta Temp Score: 7.7
VulDB Base Score: 8.0
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD 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: Stack-based overflowCWE: CWE-121 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/09/2022 🔍09/23/2022 🔍
09/23/2022 🔍
05/28/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2022-30426 (🔍)
GCVE (CVE): GCVE-0-2022-30426
GCVE (VulDB): GCVE-100-209347
Entry
Created: 09/23/2022 08:26Updated: 05/28/2025 01:24
Changes: 09/23/2022 08:26 (37), 10/22/2022 14:09 (10), 05/28/2025 01:24 (15)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.