dbcve.org
Altos T110 F3 FirmwareOperating system · Acer

CVE-2022-30426

HIGH · 7.8 CVSS v3.1 Published 2022-09-23
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
80/100
Remediation priority · High
Public exploit Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-787

The program writes past the bounds of a buffer, overwriting adjacent memory an attacker can turn to their advantage. Crafted input can overwrite control data and redirect execution. Remediation is validating every index and length before a write, plus modern memory-safety mitigations.

General guidance for the out-of-bounds write class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Altos T110 F3 FirmwareOperating system
Affected:< p13
Ap130 F2 FirmwareOperating system
Affected:< p04
Aspire 1600x FirmwareOperating system
Affected:< p11.a3l
Aspire 1602m FirmwareOperating system
Affected:< p11.a3l
Aspire 7600u FirmwareOperating system
Affected:< p11.a4
Aspire Mc605 FirmwareOperating system
Affected:< p11.a4l
Aspire Tc 105 FirmwareOperating system
Affected:< p12.b0l
Aspire Tc 120 FirmwareOperating system
Affected:< p11-a4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Recommended fix Moderate confidence

Acer BIOS/UEFI firmware updates - contact Acer support or visit acer.com/support for model-specific patched firmware releases

  1. 1. Identify the exact Acer product model from the affected list (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, Veriton M2110G, Veriton M2120G, or other affected models).
  2. 2. Visit the official Acer support website (acer.com) and navigate to the Drivers & Downloads section for your specific product model.
  3. 3. Locate and download the latest BIOS/UEFI firmware version that is newer than the vulnerable version listed (e.g., for T110 F3: version newer than P13; for AP130 F2: version newer than P04).
  4. 4. Follow Acer's BIOS update instructions, which typically require running the firmware update utility from within Windows or creating a bootable USB update media.
  5. 5. Ensure the system maintains power throughout the firmware update process to prevent brickware.
Caveat UEFI firmware updates carry risk of system damage if interrupted; ensure stable power and follow update procedure exactly

Generated from the published advisory — verify against the referenced sources before acting.

No vendor fix exists Altos T110 F3 Firmware has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $3,200. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30426 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30426 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data