Read the docs
TI-2019-13235 Aliases CVE-2019-18216GHSA-j988-q3vx-6wph

The BIOS configuration design on ASUS ROG Zephyrus M GM501GS laptops with BIOS 313 relies…

Priority LOW 30Published · Updated

Key facts

Attack vector
Physical
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA.

Summary

The BIOS configuration design on ASUS ROG Zephyrus M GM501GS laptops with BIOS 313 relies on the main battery instead of using a CMOS battery, which reduces the value of a protection mechanism in which booting from a USB device is prohibited. Attackers who have physical laptop access can exhaust the main battery to reset the BIOS configuration, and then achieve direct access to the hard drive by booting a live USB OS without disassembling the laptop. NOTE: the vendor has apparently indicated that this is "normal" and use of the same battery for the BIOS and the overall system is a "new design." However, the vendor apparently plans to "improve" this an unspecified later time

Why it matters now

EPSS 0.00376 31st percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
  • — Vendor— Affected all versions Fixed in — No fix listed CNA

CPE configurations NVD · 2

CPEVersionsRoleVendor
cpe:2.3:o:asus:rog_zephyrus_m_gm501gs_firmware:-:*:*:*:*:*:*:*not specified by NVDVulnerableASUS
cpe:2.3:h:asus:rog_zephyrus_m_gm501gs:-:*:*:*:*:*:*:*not specified by NVDRunning onASUS
  • cpe:2.3:o:asus:rog_zephyrus_m_gm501gs_firmware:-:*:*:*:*:*:*:* Versions not specified by NVD Vulnerable ·ASUS
  • cpe:2.3:h:asus:rog_zephyrus_m_gm501gs:-:*:*:*:*:*:*:* Versions not specified by NVD Running on ·ASUS

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2019-18216
  2. 2026-10-03 Alias added: GHSA-j988-q3vx-6wph

References

Sources