Vulnerability-Lookup

CNVD-2019-37734

Vulnerability from cnvd - Published: 2019-10-29

Title

ASUS ROG Zephyrus M GM501GS存在未明漏洞

Description

ASUS ROG Zephyrus M GM501GS是中国台湾华硕（ASUS）公司的一款笔记本电脑。 ASUS ROG Zephyrus M GM501GS（带有BIOS 313）中存在安全漏洞，攻击者可通过用尽主电池电量利用该漏洞重置BIOS配置并获取硬盘的直接访问权限。

Severity

高

Formal description

厂商尚未提供漏洞修复方案，请关注厂商主页更新： https://www.asus.com

Reference

https://blog.modpr0.be/2019/10/18/asus-rog-bios-reset-on-lost-battery-power/

Impacted products

Name
ASUS ROG Zephyrus M GM501GS

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2019-18216"
    }
  },
  "description": "ASUS ROG Zephyrus M GM501GS\u662f\u4e2d\u56fd\u53f0\u6e7e\u534e\u7855\uff08ASUS\uff09\u516c\u53f8\u7684\u4e00\u6b3e\u7b14\u8bb0\u672c\u7535\u8111\u3002\n\nASUS ROG Zephyrus M GM501GS\uff08\u5e26\u6709BIOS 313\uff09\u4e2d\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\uff0c\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u7528\u5c3d\u4e3b\u7535\u6c60\u7535\u91cf\u5229\u7528\u8be5\u6f0f\u6d1e\u91cd\u7f6eBIOS\u914d\u7f6e\u5e76\u83b7\u53d6\u786c\u76d8\u7684\u76f4\u63a5\u8bbf\u95ee\u6743\u9650\u3002",
  "formalWay": "\u5382\u5546\u5c1a\u672a\u63d0\u4f9b\u6f0f\u6d1e\u4fee\u590d\u65b9\u6848\uff0c\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u66f4\u65b0\uff1a\r\nhttps://www.asus.com",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2019-37734",
  "openTime": "2019-10-29",
  "products": {
    "product": "ASUS ROG Zephyrus M GM501GS"
  },
  "referenceLink": "https://blog.modpr0.be/2019/10/18/asus-rog-bios-reset-on-lost-battery-power/",
  "serverity": "\u9ad8",
  "submitTime": "2019-10-21",
  "title": "ASUS ROG Zephyrus M GM501GS\u5b58\u5728\u672a\u660e\u6f0f\u6d1e"
}

CVE-2019-18216 (GCVE-0-2019-18216)

Vulnerability from cvelistv5 – Published: 2019-10-20 15:21 – Updated: 2024-08-05 01:47 Disputed

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

Severity ?

No CVSS data available.

CWE

Assigner

mitre

References

URL

Tags

https://blog.modpr0.be/2019/10/18/asus-rog-bios-r…

x_refsource_MISC

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T01:47:14.035Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://blog.modpr0.be/2019/10/18/asus-rog-bios-reset-on-lost-battery-power/"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2019-10-20T15:21:24",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://blog.modpr0.be/2019/10/18/asus-rog-bios-reset-on-lost-battery-power/"
        }
      ],
      "tags": [
        "disputed"
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2019-18216",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "** DISPUTED ** 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."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://blog.modpr0.be/2019/10/18/asus-rog-bios-reset-on-lost-battery-power/",
              "refsource": "MISC",
              "url": "https://blog.modpr0.be/2019/10/18/asus-rog-bios-reset-on-lost-battery-power/"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2019-18216",
    "datePublished": "2019-10-20T15:21:24",
    "dateReserved": "2019-10-20T00:00:00",
    "dateUpdated": "2024-08-05T01:47:14.035Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

CNVD-2019-37734

CVE-2019-18216 (GCVE-0-2019-18216)

Tags

Sightings

Nomenclature