CNVD-2017-34850

Vulnerability from cnvd - Published: 2017-11-21
VLAI
Title
多款Thales nShield Connect硬件权限访问控制漏洞
Description
Thales nShield Connect hardware models 500等都是美国Thales e-Security公司的网络型HSM(硬件安全模块)设备。 多款Thales nShield Connect硬件存在安全漏洞。物理位置临近的攻击者可利用该漏洞签署任意数据,提取任意的设备身份密钥,并欺骗nShield Connect设备。
Severity
高
Patch Name
多款Thales nShield Connect硬件权限访问控制漏洞的补丁
Patch Description
Thales nShield Connect hardware models 500等都是美国Thales e-Security公司的网络型HSM(硬件安全模块)设备。 多款Thales nShield Connect硬件存在安全漏洞。物理位置临近的攻击者可利用该漏洞签署任意数据,提取任意的设备身份密钥,并欺骗nShield Connect设备。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布了漏洞修复程序,请及时关注更新: http://www.thales-esecurity.com/

Reference
http://www.securitytracker.com/id/1032152
Impacted products
Name
['Thales e-Security nShield Connect 500 <11.72', 'Thales e-Security nShield Connect 1500 <11.72', 'Thales e-Security nShield Connect 6000 <11.72', 'Thales e-Security nShield Connect 500+ <11.72', 'Thales e-Security nShield Connect 1500+ <11.72', 'Thales e-Security nShield Connect 6000+ <11.72']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2015-1878"
    }
  },
  "description": "Thales nShield Connect hardware models 500\u7b49\u90fd\u662f\u7f8e\u56fdThales e-Security\u516c\u53f8\u7684\u7f51\u7edc\u578bHSM(\u786c\u4ef6\u5b89\u5168\u6a21\u5757)\u8bbe\u5907\u3002\r\n\r\n\u591a\u6b3eThales nShield Connect\u786c\u4ef6\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u7269\u7406\u4f4d\u7f6e\u4e34\u8fd1\u7684\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u7b7e\u7f72\u4efb\u610f\u6570\u636e\uff0c\u63d0\u53d6\u4efb\u610f\u7684\u8bbe\u5907\u8eab\u4efd\u5bc6\u94a5\uff0c\u5e76\u6b3a\u9a97nShield Connect\u8bbe\u5907\u3002",
  "discovererName": "unknwon",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttp://www.thales-esecurity.com/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-34850",
  "openTime": "2017-11-21",
  "patchDescription": "Thales nShield Connect hardware models 500\u7b49\u90fd\u662f\u7f8e\u56fdThales e-Security\u516c\u53f8\u7684\u7f51\u7edc\u578bHSM(\u786c\u4ef6\u5b89\u5168\u6a21\u5757)\u8bbe\u5907\u3002\r\n\r\n\u591a\u6b3eThales nShield Connect\u786c\u4ef6\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u7269\u7406\u4f4d\u7f6e\u4e34\u8fd1\u7684\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u7b7e\u7f72\u4efb\u610f\u6570\u636e\uff0c\u63d0\u53d6\u4efb\u610f\u7684\u8bbe\u5907\u8eab\u4efd\u5bc6\u94a5\uff0c\u5e76\u6b3a\u9a97nShield Connect\u8bbe\u5907\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": "\u591a\u6b3eThales nShield Connect\u786c\u4ef6\u6743\u9650\u8bbf\u95ee\u63a7\u5236\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Thales e-Security nShield Connect 500 \u003c11.72",
      "Thales e-Security nShield Connect 1500 \u003c11.72",
      "Thales e-Security nShield Connect 6000 \u003c11.72",
      "Thales e-Security nShield Connect 500+ \u003c11.72",
      "Thales e-Security nShield Connect 1500+ \u003c11.72",
      "Thales e-Security nShield Connect 6000+ \u003c11.72"
    ]
  },
  "referenceLink": "http://www.securitytracker.com/id/1032152",
  "serverity": "\u9ad8",
  "submitTime": "2017-09-22",
  "title": "\u591a\u6b3eThales nShield Connect\u786c\u4ef6\u6743\u9650\u8bbf\u95ee\u63a7\u5236\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.