CNVD-2017-30486

Vulnerability from cnvd - Published: 2017-10-18
VLAI
Title
英特尔NUC套件SMM权限提升漏洞
Description
Intel NUC7i3BNK等都是美国英特尔(Intel)公司的CPU(中央处理器)产品。 多款Intel产品中的系统固件存在权限提升漏洞,该漏洞源于程序未能充分的验证输入。攻击者可通过操作内存利用该漏洞执行任意代码。
Severity
中
Patch Name
英特尔NUC套件SMM权限提升漏洞的补丁
Patch Description
Intel NUC7i3BNK等都是美国英特尔(Intel)公司的CPU(中央处理器)产品。 多款Intel产品中的系统固件存在权限提升漏洞,该漏洞源于程序未能充分的验证输入。攻击者可通过操作内存利用该漏洞执行任意代码。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布漏洞修复程序,请及时关注更新: https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00084&languageid=en-fr

Reference
https://nvd.nist.gov/vuln/detail/CVE-2017-5700
Impacted products
Name
['Intel NUC7i5BNK', 'Intel NUC7i5BNH', 'Intel NUC7i3BNK', 'Intel NUC7i3BNH', 'Intel BN0049', 'Intel NUC7i7BNH']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-5721"
    }
  },
  "description": "Intel NUC7i3BNK\u7b49\u90fd\u662f\u7f8e\u56fd\u82f1\u7279\u5c14\uff08Intel\uff09\u516c\u53f8\u7684CPU\uff08\u4e2d\u592e\u5904\u7406\u5668\uff09\u4ea7\u54c1\u3002\r\n\r\n\u591a\u6b3eIntel\u4ea7\u54c1\u4e2d\u7684\u7cfb\u7edf\u56fa\u4ef6\u5b58\u5728\u6743\u9650\u63d0\u5347\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u672a\u80fd\u5145\u5206\u7684\u9a8c\u8bc1\u8f93\u5165\u3002\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u64cd\u4f5c\u5185\u5b58\u5229\u7528\u8be5\u6f0f\u6d1e\u6267\u884c\u4efb\u610f\u4ee3\u7801\u3002",
  "discovererName": "unknown",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00084\u0026languageid=en-fr",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-30486",
  "openTime": "2017-10-18",
  "patchDescription": "Intel NUC7i3BNK\u7b49\u90fd\u662f\u7f8e\u56fd\u82f1\u7279\u5c14\uff08Intel\uff09\u516c\u53f8\u7684CPU\uff08\u4e2d\u592e\u5904\u7406\u5668\uff09\u4ea7\u54c1\u3002\r\n\r\n\u591a\u6b3eIntel\u4ea7\u54c1\u4e2d\u7684\u7cfb\u7edf\u56fa\u4ef6\u5b58\u5728\u6743\u9650\u63d0\u5347\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u672a\u80fd\u5145\u5206\u7684\u9a8c\u8bc1\u8f93\u5165\u3002\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u64cd\u4f5c\u5185\u5b58\u5229\u7528\u8be5\u6f0f\u6d1e\u6267\u884c\u4efb\u610f\u4ee3\u7801\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "\u82f1\u7279\u5c14NUC\u5957\u4ef6SMM\u6743\u9650\u63d0\u5347\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Intel NUC7i5BNK",
      "Intel NUC7i5BNH",
      "Intel NUC7i3BNK",
      "Intel NUC7i3BNH",
      "Intel BN0049",
      "Intel NUC7i7BNH"
    ]
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2017-5700",
  "serverity": "\u4e2d",
  "submitTime": "2017-10-11",
  "title": "\u82f1\u7279\u5c14NUC\u5957\u4ef6SMM\u6743\u9650\u63d0\u5347\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.