CNVD-2022-17781

Vulnerability from cnvd - Published: 2022-03-09
VLAI
Title
Siemens RUGGEDCOM ROS存在未明漏洞(CNVD-2022-17781)
Description
Siemens RuggedCom ROS是德国西门子(Siemens)公司的一套用于RuggedCom系列交换机中的操作系统。 Siemens RUGGEDCOM ROS存在安全漏洞,攻击者可利用漏洞导致数据损坏,并可能导致应用程序出现硬故障。
Severity
高
Patch Name
Siemens RUGGEDCOM ROS存在未明漏洞(CNVD-2022-17781)的补丁
Patch Description
Siemens RuggedCom ROS是德国西门子(Siemens)公司的一套用于RuggedCom系列交换机中的操作系统。 Siemens RUGGEDCOM ROS存在安全漏洞,攻击者可利用漏洞导致数据损坏,并可能导致应用程序出现硬故障。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

用户可参考如下供应商提供的安全公告获得补丁信息: https://cert-portal.siemens.com/productcert/pdf/ssa-256353.pdf

Reference
https://cert-portal.siemens.com/productcert/pdf/ssa-256353.pdf
Impacted products
Name
['Siemens RUGGEDCOM ROS M2100 < V5.6.0', 'Siemens RUGGEDCOM ROS RMC8388 devices < V5.6.0', 'Siemens RUGGEDCOM ROS RS416v2 < V5.6.0', 'Siemens RUGGEDCOM ROS RS900G < V5.6.0', 'Siemens RUGGEDCOM ROS RS900G (32M) < V5.6.0', 'Siemens RUGGEDCOM ROS RSG900 V5.X < V5.6.0', 'Siemens RUGGEDCOM ROS RSG920P V5.X < V5.6.0', 'Siemens RUGGEDCOM ROS RSG2100 (32M) V5.X < V5.6.0', 'Siemens RUGGEDCOM ROS RSG2100P < V5.6.0', 'Siemens RUGGEDCOM ROS RSG2100P (32M) V5.X < V5.6.0', 'Siemens RUGGEDCOM ROS RSG2288 V5.X < V5.6.0', 'Siemens RUGGEDCOM ROS RSG2300 V5.X < V5.6.0', 'Siemens RUGGEDCOM ROS RSG2300P V5.X < V5.6.0', 'Siemens RUGGEDCOM ROS RSG2488 V5.X < V5.6.0', 'Siemens RUGGEDCOM ROS RSL910 < V5.6.0', 'Siemens RUGGEDCOM ROS RST916C < V5.6.0', 'Siemens RUGGEDCOM ROS RST916P < V5.6.0', 'Siemens RUGGEDCOM ROS RST2228 < V5.6.0']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2021-42020"
    }
  },
  "description": "Siemens RuggedCom ROS\u662f\u5fb7\u56fd\u897f\u95e8\u5b50\uff08Siemens\uff09\u516c\u53f8\u7684\u4e00\u5957\u7528\u4e8eRuggedCom\u7cfb\u5217\u4ea4\u6362\u673a\u4e2d\u7684\u64cd\u4f5c\u7cfb\u7edf\u3002\n\nSiemens RUGGEDCOM ROS\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u6f0f\u6d1e\u5bfc\u81f4\u6570\u636e\u635f\u574f\uff0c\u5e76\u53ef\u80fd\u5bfc\u81f4\u5e94\u7528\u7a0b\u5e8f\u51fa\u73b0\u786c\u6545\u969c\u3002",
  "formalWay": "\u7528\u6237\u53ef\u53c2\u8003\u5982\u4e0b\u4f9b\u5e94\u5546\u63d0\u4f9b\u7684\u5b89\u5168\u516c\u544a\u83b7\u5f97\u8865\u4e01\u4fe1\u606f\uff1a\r\nhttps://cert-portal.siemens.com/productcert/pdf/ssa-256353.pdf",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2022-17781",
  "openTime": "2022-03-09",
  "patchDescription": "Siemens RuggedCom ROS\u662f\u5fb7\u56fd\u897f\u95e8\u5b50\uff08Siemens\uff09\u516c\u53f8\u7684\u4e00\u5957\u7528\u4e8eRuggedCom\u7cfb\u5217\u4ea4\u6362\u673a\u4e2d\u7684\u64cd\u4f5c\u7cfb\u7edf\u3002\r\n\r\nSiemens RUGGEDCOM ROS\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u6f0f\u6d1e\u5bfc\u81f4\u6570\u636e\u635f\u574f\uff0c\u5e76\u53ef\u80fd\u5bfc\u81f4\u5e94\u7528\u7a0b\u5e8f\u51fa\u73b0\u786c\u6545\u969c\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": "Siemens RUGGEDCOM ROS\u5b58\u5728\u672a\u660e\u6f0f\u6d1e\uff08CNVD-2022-17781\uff09\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Siemens RUGGEDCOM ROS M2100 \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RMC8388 devices \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RS416v2 \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RS900G \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RS900G (32M) \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSG900 V5.X \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSG920P V5.X \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSG2100 (32M) V5.X \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSG2100P \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSG2100P (32M) V5.X \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSG2288 V5.X \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSG2300 V5.X \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSG2300P V5.X \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSG2488 V5.X \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RSL910 \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RST916C \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RST916P \u003c V5.6.0",
      "Siemens RUGGEDCOM ROS RST2228 \u003c V5.6.0"
    ]
  },
  "referenceLink": "https://cert-portal.siemens.com/productcert/pdf/ssa-256353.pdf",
  "serverity": "\u9ad8",
  "submitTime": "2022-03-09",
  "title": "Siemens RUGGEDCOM ROS\u5b58\u5728\u672a\u660e\u6f0f\u6d1e\uff08CNVD-2022-17781\uff09"
}



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.