CNVD-2017-38307

Vulnerability from cnvd - Published: 2017-12-28
VLAI
Title
Lenovo ThinkPad W541笔记本Seagate ST500LT015 hard disk drive绕过漏洞
Description
Lenovo ThinkPad W541 laptops with BIOS 2.21是中国联想(Lenovo)公司的一款使用BIOS 2.21版本的笔记本电脑。Seagate ST500LT015 hard disk drive是一款使用在电脑中的美国希捷(Seagate)公司生产的硬盘。 使用BIOS 2.21版本的Lenovo ThinkPad W541笔记本上的Seagate ST500LT015 hard disk drive存在安全漏洞。物理位置临近的攻击者可利用该漏洞绕过自我加密硬盘(SED)保护。
Severity
低
Formal description

厂商尚未提供漏洞修复方案,请关注厂商主页及时更新: https://www.seagate.com

Reference
https://www.blackhat.com/docs/eu-15/materials/eu-15-Boteanu-Bypassing-Self-Encrypting-Drives-SED-In-Enterprise-Environments-wp.pdf
Impacted products
Name
Lenovo ST500LT015
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2015-7269"
    }
  },
  "description": "Lenovo ThinkPad W541 laptops with BIOS 2.21\u662f\u4e2d\u56fd\u8054\u60f3\uff08Lenovo\uff09\u516c\u53f8\u7684\u4e00\u6b3e\u4f7f\u7528BIOS 2.21\u7248\u672c\u7684\u7b14\u8bb0\u672c\u7535\u8111\u3002Seagate ST500LT015 hard disk drive\u662f\u4e00\u6b3e\u4f7f\u7528\u5728\u7535\u8111\u4e2d\u7684\u7f8e\u56fd\u5e0c\u6377\uff08Seagate\uff09\u516c\u53f8\u751f\u4ea7\u7684\u786c\u76d8\u3002\r\n\r\n\u4f7f\u7528BIOS 2.21\u7248\u672c\u7684Lenovo ThinkPad W541\u7b14\u8bb0\u672c\u4e0a\u7684Seagate ST500LT015 hard disk drive\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u7269\u7406\u4f4d\u7f6e\u4e34\u8fd1\u7684\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u7ed5\u8fc7\u81ea\u6211\u52a0\u5bc6\u786c\u76d8\uff08SED\uff09\u4fdd\u62a4\u3002",
  "discovererName": "Lenovo",
  "formalWay": "\u5382\u5546\u5c1a\u672a\u63d0\u4f9b\u6f0f\u6d1e\u4fee\u590d\u65b9\u6848\uff0c\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u53ca\u65f6\u66f4\u65b0\uff1a\r\nhttps://www.seagate.com",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-38307",
  "openTime": "2017-12-28",
  "products": {
    "product": "Lenovo ST500LT015"
  },
  "referenceLink": "https://www.blackhat.com/docs/eu-15/materials/eu-15-Boteanu-Bypassing-Self-Encrypting-Drives-SED-In-Enterprise-Environments-wp.pdf",
  "serverity": "\u4f4e",
  "submitTime": "2017-11-29",
  "title": "Lenovo ThinkPad W541\u7b14\u8bb0\u672cSeagate ST500LT015 hard disk drive\u7ed5\u8fc7\u6f0f\u6d1e"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.