CNVD-2022-88176

Vulnerability from cnvd - Published: 2022-12-16
VLAI
Title
Cisco ATA 190系列协议数据包输入验证错误漏洞
Description
ATA 190、ATA 191、ATA 192是一款Cisco ATA 190系列模拟电话适配器。 Cisco ATA 190(仅限本地部署)、ATA 191(本地部署或多平台部署)、ATA 192(仅限多平台部署)存在输入验证错误漏洞,该漏洞源于Cisco Discovery Protocol(CDP)思科发现协议功能存在安全问题,未经身份验证的远程攻击者可利用漏洞在受影响的设备上执行任意代码,并导致CDP思科发现协议服务重启。
Severity
高
Patch Name
Cisco ATA 190系列协议数据包输入验证错误漏洞的补丁
Patch Description
ATA 190、ATA 191、ATA 192是一款Cisco ATA 190系列模拟电话适配器。 Cisco ATA 190(仅限本地部署)、ATA 191(本地部署或多平台部署)、ATA 192(仅限多平台部署)存在输入验证错误漏洞,该漏洞源于Cisco Discovery Protocol(CDP)思科发现协议功能存在安全问题,未经身份验证的远程攻击者可利用漏洞在受影响的设备上执行任意代码,并导致CDP思科发现协议服务重启。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已发布升级补丁以修复漏洞,补丁获取链接: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ata19x-multivuln-GEZYVvs

Reference
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ata19x-multivuln-GEZYVvs
Impacted products
Name
['Cisco ATA 190', 'Cisco ATA 191', 'Cisco ATA 192']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2022-20688",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2022-20688"
    }
  },
  "description": "ATA 190\u3001ATA 191\u3001ATA 192\u662f\u4e00\u6b3eCisco ATA 190\u7cfb\u5217\u6a21\u62df\u7535\u8bdd\u9002\u914d\u5668\u3002\n\nCisco ATA 190\uff08\u4ec5\u9650\u672c\u5730\u90e8\u7f72\uff09\u3001ATA 191\uff08\u672c\u5730\u90e8\u7f72\u6216\u591a\u5e73\u53f0\u90e8\u7f72\uff09\u3001ATA 192\uff08\u4ec5\u9650\u591a\u5e73\u53f0\u90e8\u7f72\uff09\u5b58\u5728\u8f93\u5165\u9a8c\u8bc1\u9519\u8bef\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8eCisco Discovery Protocol\uff08CDP\uff09\u601d\u79d1\u53d1\u73b0\u534f\u8bae\u529f\u80fd\u5b58\u5728\u5b89\u5168\u95ee\u9898\uff0c\u672a\u7ecf\u8eab\u4efd\u9a8c\u8bc1\u7684\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u6f0f\u6d1e\u5728\u53d7\u5f71\u54cd\u7684\u8bbe\u5907\u4e0a\u6267\u884c\u4efb\u610f\u4ee3\u7801\uff0c\u5e76\u5bfc\u81f4CDP\u601d\u79d1\u53d1\u73b0\u534f\u8bae\u670d\u52a1\u91cd\u542f\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ata19x-multivuln-GEZYVvs",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2022-88176",
  "openTime": "2022-12-16",
  "patchDescription": "ATA 190\u3001ATA 191\u3001ATA 192\u662f\u4e00\u6b3eCisco ATA 190\u7cfb\u5217\u6a21\u62df\u7535\u8bdd\u9002\u914d\u5668\u3002\r\n\r\nCisco ATA 190\uff08\u4ec5\u9650\u672c\u5730\u90e8\u7f72\uff09\u3001ATA 191\uff08\u672c\u5730\u90e8\u7f72\u6216\u591a\u5e73\u53f0\u90e8\u7f72\uff09\u3001ATA 192\uff08\u4ec5\u9650\u591a\u5e73\u53f0\u90e8\u7f72\uff09\u5b58\u5728\u8f93\u5165\u9a8c\u8bc1\u9519\u8bef\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8eCisco Discovery Protocol\uff08CDP\uff09\u601d\u79d1\u53d1\u73b0\u534f\u8bae\u529f\u80fd\u5b58\u5728\u5b89\u5168\u95ee\u9898\uff0c\u672a\u7ecf\u8eab\u4efd\u9a8c\u8bc1\u7684\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u6f0f\u6d1e\u5728\u53d7\u5f71\u54cd\u7684\u8bbe\u5907\u4e0a\u6267\u884c\u4efb\u610f\u4ee3\u7801\uff0c\u5e76\u5bfc\u81f4CDP\u601d\u79d1\u53d1\u73b0\u534f\u8bae\u670d\u52a1\u91cd\u542f\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 ATA 190\u7cfb\u5217\u534f\u8bae\u6570\u636e\u5305\u8f93\u5165\u9a8c\u8bc1\u9519\u8bef\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Cisco ATA 190",
      "Cisco ATA 191",
      "Cisco ATA 192"
    ]
  },
  "referenceLink": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ata19x-multivuln-GEZYVvs",
  "serverity": "\u9ad8",
  "submitTime": "2022-10-11",
  "title": "Cisco ATA 190\u7cfb\u5217\u534f\u8bae\u6570\u636e\u5305\u8f93\u5165\u9a8c\u8bc1\u9519\u8bef\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.