CNVD-2018-21197

Vulnerability from cnvd - Published: 2018-10-18
VLAI
Title
Cisco Wireless LAN Controller Software权限提升漏洞
Description
Cisco Wireless LAN Controller(WLC)是美国思科(Cisco)公司的一款无线局域网控制器产品。该产品在无线局域网中提供安全策略、入侵检测等功能。 Cisco Wireless LAN Controller Software存在权限提升漏洞,该漏洞是由于在从Cisco TrustSec域内的一个服务集标识符(SSID)到另一个服务集标识符(SSID)的无线漫游期间动态分配安全组标签(SGT)。攻击者利用此漏洞可以通过尝试从域内的其他SSID获取SGT。成功利用可能允许攻击者获得在正常情况下应禁止的特权网络访问。
Severity
中
Formal description

目前没有详细的解决方案提供: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20181017-wlan-escalation

Reference
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20181017-wlan-escalation
Impacted products
Name
Cisco Wireless LAN Controller
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2018-15395"
    }
  },
  "description": "Cisco Wireless LAN Controller\uff08WLC\uff09\u662f\u7f8e\u56fd\u601d\u79d1\uff08Cisco\uff09\u516c\u53f8\u7684\u4e00\u6b3e\u65e0\u7ebf\u5c40\u57df\u7f51\u63a7\u5236\u5668\u4ea7\u54c1\u3002\u8be5\u4ea7\u54c1\u5728\u65e0\u7ebf\u5c40\u57df\u7f51\u4e2d\u63d0\u4f9b\u5b89\u5168\u7b56\u7565\u3001\u5165\u4fb5\u68c0\u6d4b\u7b49\u529f\u80fd\u3002\r\n\r\nCisco Wireless LAN Controller Software\u5b58\u5728\u6743\u9650\u63d0\u5347\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u662f\u7531\u4e8e\u5728\u4eceCisco TrustSec\u57df\u5185\u7684\u4e00\u4e2a\u670d\u52a1\u96c6\u6807\u8bc6\u7b26\uff08SSID\uff09\u5230\u53e6\u4e00\u4e2a\u670d\u52a1\u96c6\u6807\u8bc6\u7b26\uff08SSID\uff09\u7684\u65e0\u7ebf\u6f2b\u6e38\u671f\u95f4\u52a8\u6001\u5206\u914d\u5b89\u5168\u7ec4\u6807\u7b7e\uff08SGT\uff09\u3002\u653b\u51fb\u8005\u5229\u7528\u6b64\u6f0f\u6d1e\u53ef\u4ee5\u901a\u8fc7\u5c1d\u8bd5\u4ece\u57df\u5185\u7684\u5176\u4ed6SSID\u83b7\u53d6SGT\u3002\u6210\u529f\u5229\u7528\u53ef\u80fd\u5141\u8bb8\u653b\u51fb\u8005\u83b7\u5f97\u5728\u6b63\u5e38\u60c5\u51b5\u4e0b\u5e94\u7981\u6b62\u7684\u7279\u6743\u7f51\u7edc\u8bbf\u95ee\u3002",
  "discovererName": "Cisco",
  "formalWay": "\u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u7684\u89e3\u51b3\u65b9\u6848\u63d0\u4f9b\uff1a\r\nhttps://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20181017-wlan-escalation",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-21197",
  "openTime": "2018-10-18",
  "products": {
    "product": "Cisco Wireless LAN Controller"
  },
  "referenceLink": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20181017-wlan-escalation",
  "serverity": "\u4e2d",
  "submitTime": "2018-10-18",
  "title": "Cisco Wireless LAN Controller Software\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.