CNVD-2018-06692

Vulnerability from cnvd - Published: 2018-03-29
VLAI
Title
Cisco StarOS CLI命令注入漏洞
Description
思科ASR 5000系列是一个运营商级平台,可用于部署高需求的3G网络以及向长期演进技术(LTE)迁移。Cisco StarOS是一套路由器操作系统,可控制整个系统逻辑,可控制进程和CLI。 Cisco ASR 5000系列路由器的Cisco StarOS操作系统存在CLI命令注入漏洞。该漏洞产生的原因是受影响的操作系统对用户提供的输入验证不足。本地攻击者可通过向受影响的系统认证并将恶意参数注入有漏洞的CLI命令利用该漏洞在受影响的系统上以root权限执行任意命令。
Severity
高
Patch Name
Cisco StarOS CLI命令注入漏洞的补丁
Patch Description
思科ASR 5000系列是一个运营商级平台,可用于部署高需求的3G网络以及向长期演进技术(LTE)迁移。Cisco StarOS是一套路由器操作系统,可控制整个系统逻辑,可控制进程和CLI。 Cisco ASR 5000系列路由器的Cisco StarOS操作系统存在CLI命令注入漏洞。该漏洞产生的原因是受影响的操作系统对用户提供的输入验证不足。本地攻击者可通过向受影响的系统认证并将恶意参数注入有漏洞的CLI命令利用该漏洞在受影响的系统上以root权限执行任意命令。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布漏洞修复程序,请及时关注更新: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180307-staros1

Reference
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180307-staros1
Impacted products
Name
['Cisco StarOS 0', 'Cisco ASR 5000 Series 21.5', 'Cisco ASR 5000 Series 21.3.0.67664']
Show details on source website

{
  "bids": {
    "bid": {
      "bidNumber": "103344"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2018-0224"
    }
  },
  "description": "\u601d\u79d1ASR 5000\u7cfb\u5217\u662f\u4e00\u4e2a\u8fd0\u8425\u5546\u7ea7\u5e73\u53f0\uff0c\u53ef\u7528\u4e8e\u90e8\u7f72\u9ad8\u9700\u6c42\u76843G\u7f51\u7edc\u4ee5\u53ca\u5411\u957f\u671f\u6f14\u8fdb\u6280\u672f(LTE)\u8fc1\u79fb\u3002Cisco StarOS\u662f\u4e00\u5957\u8def\u7531\u5668\u64cd\u4f5c\u7cfb\u7edf\uff0c\u53ef\u63a7\u5236\u6574\u4e2a\u7cfb\u7edf\u903b\u8f91\uff0c\u53ef\u63a7\u5236\u8fdb\u7a0b\u548cCLI\u3002\r\n\r\nCisco ASR 5000\u7cfb\u5217\u8def\u7531\u5668\u7684Cisco StarOS\u64cd\u4f5c\u7cfb\u7edf\u5b58\u5728CLI\u547d\u4ee4\u6ce8\u5165\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u4ea7\u751f\u7684\u539f\u56e0\u662f\u53d7\u5f71\u54cd\u7684\u64cd\u4f5c\u7cfb\u7edf\u5bf9\u7528\u6237\u63d0\u4f9b\u7684\u8f93\u5165\u9a8c\u8bc1\u4e0d\u8db3\u3002\u672c\u5730\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u5411\u53d7\u5f71\u54cd\u7684\u7cfb\u7edf\u8ba4\u8bc1\u5e76\u5c06\u6076\u610f\u53c2\u6570\u6ce8\u5165\u6709\u6f0f\u6d1e\u7684CLI\u547d\u4ee4\u5229\u7528\u8be5\u6f0f\u6d1e\u5728\u53d7\u5f71\u54cd\u7684\u7cfb\u7edf\u4e0a\u4ee5root\u6743\u9650\u6267\u884c\u4efb\u610f\u547d\u4ee4\u3002",
  "discovererName": "Cisco",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180307-staros1",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-06692",
  "openTime": "2018-03-29",
  "patchDescription": "\u601d\u79d1ASR 5000\u7cfb\u5217\u662f\u4e00\u4e2a\u8fd0\u8425\u5546\u7ea7\u5e73\u53f0\uff0c\u53ef\u7528\u4e8e\u90e8\u7f72\u9ad8\u9700\u6c42\u76843G\u7f51\u7edc\u4ee5\u53ca\u5411\u957f\u671f\u6f14\u8fdb\u6280\u672f(LTE)\u8fc1\u79fb\u3002Cisco StarOS\u662f\u4e00\u5957\u8def\u7531\u5668\u64cd\u4f5c\u7cfb\u7edf\uff0c\u53ef\u63a7\u5236\u6574\u4e2a\u7cfb\u7edf\u903b\u8f91\uff0c\u53ef\u63a7\u5236\u8fdb\u7a0b\u548cCLI\u3002\r\n\r\nCisco ASR 5000\u7cfb\u5217\u8def\u7531\u5668\u7684Cisco StarOS\u64cd\u4f5c\u7cfb\u7edf\u5b58\u5728CLI\u547d\u4ee4\u6ce8\u5165\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u4ea7\u751f\u7684\u539f\u56e0\u662f\u53d7\u5f71\u54cd\u7684\u64cd\u4f5c\u7cfb\u7edf\u5bf9\u7528\u6237\u63d0\u4f9b\u7684\u8f93\u5165\u9a8c\u8bc1\u4e0d\u8db3\u3002\u672c\u5730\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u5411\u53d7\u5f71\u54cd\u7684\u7cfb\u7edf\u8ba4\u8bc1\u5e76\u5c06\u6076\u610f\u53c2\u6570\u6ce8\u5165\u6709\u6f0f\u6d1e\u7684CLI\u547d\u4ee4\u5229\u7528\u8be5\u6f0f\u6d1e\u5728\u53d7\u5f71\u54cd\u7684\u7cfb\u7edf\u4e0a\u4ee5root\u6743\u9650\u6267\u884c\u4efb\u610f\u547d\u4ee4\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": "Cisco StarOS CLI\u547d\u4ee4\u6ce8\u5165\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Cisco StarOS 0",
      "Cisco ASR 5000 Series 21.5",
      "Cisco ASR 5000 Series 21.3.0.67664"
    ]
  },
  "referenceLink": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180307-staros1",
  "serverity": "\u9ad8",
  "submitTime": "2018-03-09",
  "title": "Cisco StarOS CLI\u547d\u4ee4\u6ce8\u5165\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.