CNVD-2021-05538

Vulnerability from cnvd - Published: 2021-01-25
VLAI
Title
Cisco AnyConnect Secure Mobility Client配置文件修改漏洞
Description
Cisco AnyConnect Secure Mobility Client是一种虚拟专用网络(VPN)客户端,适用于各种操作系统和硬件配置。 Cisco AnyConnect Secure Mobility Client 4.9.00086及更早版本(Windows版)中的进程间通信(IPC)通道存在配置文件修改漏洞。该漏洞源于对用户提供的输入验证不足。攻击者可通过向AnyConnect进程发送特制IPC消息利用该漏洞修改VPN配置文件。
Severity
低
Formal description

目前厂商暂未发布修复措施解决此安全问题,建议使用此软件的用户随时关注厂商主页或参考网址以获取解决办法: https://www.cisco.com/

Reference
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-anyconnect-profile-7u3PERKF
Impacted products
Name
Cisco Cisco AnyConnect Secure Mobility Client for Windows <=4.9.00086
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2020-3435",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2020-3435"
    }
  },
  "description": "Cisco AnyConnect Secure Mobility Client\u662f\u4e00\u79cd\u865a\u62df\u4e13\u7528\u7f51\u7edc\uff08VPN\uff09\u5ba2\u6237\u7aef\uff0c\u9002\u7528\u4e8e\u5404\u79cd\u64cd\u4f5c\u7cfb\u7edf\u548c\u786c\u4ef6\u914d\u7f6e\u3002\n\nCisco AnyConnect Secure Mobility Client 4.9.00086\u53ca\u66f4\u65e9\u7248\u672c\uff08Windows\u7248\uff09\u4e2d\u7684\u8fdb\u7a0b\u95f4\u901a\u4fe1\uff08IPC\uff09\u901a\u9053\u5b58\u5728\u914d\u7f6e\u6587\u4ef6\u4fee\u6539\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u5bf9\u7528\u6237\u63d0\u4f9b\u7684\u8f93\u5165\u9a8c\u8bc1\u4e0d\u8db3\u3002\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u5411AnyConnect\u8fdb\u7a0b\u53d1\u9001\u7279\u5236IPC\u6d88\u606f\u5229\u7528\u8be5\u6f0f\u6d1e\u4fee\u6539VPN\u914d\u7f6e\u6587\u4ef6\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u6682\u672a\u53d1\u5e03\u4fee\u590d\u63aa\u65bd\u89e3\u51b3\u6b64\u5b89\u5168\u95ee\u9898\uff0c\u5efa\u8bae\u4f7f\u7528\u6b64\u8f6f\u4ef6\u7684\u7528\u6237\u968f\u65f6\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u6216\u53c2\u8003\u7f51\u5740\u4ee5\u83b7\u53d6\u89e3\u51b3\u529e\u6cd5\uff1a\r\nhttps://www.cisco.com/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2021-05538",
  "openTime": "2021-01-25",
  "products": {
    "product": "Cisco Cisco AnyConnect Secure Mobility Client for Windows \u003c=4.9.00086"
  },
  "referenceLink": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-anyconnect-profile-7u3PERKF",
  "serverity": "\u4f4e",
  "submitTime": "2020-08-06",
  "title": "Cisco AnyConnect Secure Mobility Client\u914d\u7f6e\u6587\u4ef6\u4fee\u6539\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.