Vulnerability-Lookup

CNVD-2020-60992

Vulnerability from cnvd - Published: 2020-11-06

Title

Ruckus Networks Ruckus vRioT信任管理问题漏洞

Description

Ruckus Networks Ruckus vRioT是美国Ruckus Networks公司的一个基于蓝牙、ZigBee、LoRa实现端点连接的软件。 Ruckus Networks Ruckus vRioT 1.5.1.0.21之前版本存在信任管理问题漏洞，该漏洞源于Ruckus vRioT有一个API后门，未经身份验证的攻击者可以通过使用后门生成值作为Authorization标头来与服务API进行交互。

Severity

高

Patch Name

Ruckus Networks Ruckus vRioT信任管理问题漏洞的补丁

Patch Description

Formal description

目前厂商已发布升级补丁以修复漏洞，补丁获取链接： https://support.ruckuswireless.com/security_bulletins/305

Reference

https://twitter.com/TheXC3LL

Impacted products

Name
Ruckus Networks Ruckus vRioT <1.5.1.0.21

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2020-26879",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2020-26879"
    }
  },
  "description": "Ruckus Networks Ruckus vRioT\u662f\u7f8e\u56fdRuckus Networks\u516c\u53f8\u7684\u4e00\u4e2a\u57fa\u4e8e\u84dd\u7259\u3001ZigBee\u3001LoRa\u5b9e\u73b0\u7aef\u70b9\u8fde\u63a5\u7684\u8f6f\u4ef6\u3002\n\nRuckus Networks Ruckus vRioT 1.5.1.0.21\u4e4b\u524d\u7248\u672c\u5b58\u5728\u4fe1\u4efb\u7ba1\u7406\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8eRuckus vRioT\u6709\u4e00\u4e2aAPI\u540e\u95e8\uff0c\u672a\u7ecf\u8eab\u4efd\u9a8c\u8bc1\u7684\u653b\u51fb\u8005\u53ef\u4ee5\u901a\u8fc7\u4f7f\u7528\u540e\u95e8\u751f\u6210\u503c\u4f5c\u4e3aAuthorization\u6807\u5934\u6765\u4e0e\u670d\u52a1API\u8fdb\u884c\u4ea4\u4e92\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://support.ruckuswireless.com/security_bulletins/305",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2020-60992",
  "openTime": "2020-11-06",
  "patchDescription": "Ruckus Networks Ruckus vRioT\u662f\u7f8e\u56fdRuckus Networks\u516c\u53f8\u7684\u4e00\u4e2a\u57fa\u4e8e\u84dd\u7259\u3001ZigBee\u3001LoRa\u5b9e\u73b0\u7aef\u70b9\u8fde\u63a5\u7684\u8f6f\u4ef6\u3002\r\n\r\nRuckus Networks Ruckus vRioT 1.5.1.0.21\u4e4b\u524d\u7248\u672c\u5b58\u5728\u4fe1\u4efb\u7ba1\u7406\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8eRuckus vRioT\u6709\u4e00\u4e2aAPI\u540e\u95e8\uff0c\u672a\u7ecf\u8eab\u4efd\u9a8c\u8bc1\u7684\u653b\u51fb\u8005\u53ef\u4ee5\u901a\u8fc7\u4f7f\u7528\u540e\u95e8\u751f\u6210\u503c\u4f5c\u4e3aAuthorization\u6807\u5934\u6765\u4e0e\u670d\u52a1API\u8fdb\u884c\u4ea4\u4e92\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": "Ruckus Networks Ruckus vRioT\u4fe1\u4efb\u7ba1\u7406\u95ee\u9898\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "Ruckus Networks Ruckus vRioT \u003c1.5.1.0.21"
  },
  "referenceLink": "https://twitter.com/TheXC3LL",
  "serverity": "\u9ad8",
  "submitTime": "2020-10-27",
  "title": "Ruckus Networks Ruckus vRioT\u4fe1\u4efb\u7ba1\u7406\u95ee\u9898\u6f0f\u6d1e"
}

CVE-2020-26879 (GCVE-0-2020-26879)

Vulnerability from cvelistv5 – Published: 2020-10-26 19:20 – Updated: 2024-08-04 16:03

Summary

Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py. An unauthenticated attacker can interact with the service API by using a backdoor value as the Authorization header.

Severity

No CVSS data available.

CWE

Assigner

mitre mitre root

References

6 references

URL	Tags
https://adepts.of0x.cc	x_refsource_MISC
https://twitter.com/TheXC3LL	x_refsource_MISC
https://x-c3ll.github.io	x_refsource_MISC
https://support.ruckuswireless.com/documents	x_refsource_MISC
https://support.ruckuswireless.com/security_bulle…	x_refsource_CONFIRM
https://adepts.of0x.cc/ruckus-vriot-rce/	x_refsource_MISC

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T16:03:22.745Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://adepts.of0x.cc"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://twitter.com/TheXC3LL"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://x-c3ll.github.io"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://support.ruckuswireless.com/documents"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://support.ruckuswireless.com/security_bulletins/305"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://adepts.of0x.cc/ruckus-vriot-rce/"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py. An unauthenticated attacker can interact with the service API by using a backdoor value as the Authorization header."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2020-10-26T19:20:44.000Z",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://adepts.of0x.cc"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://twitter.com/TheXC3LL"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://x-c3ll.github.io"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://support.ruckuswireless.com/documents"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://support.ruckuswireless.com/security_bulletins/305"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://adepts.of0x.cc/ruckus-vriot-rce/"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2020-26879",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py. An unauthenticated attacker can interact with the service API by using a backdoor value as the Authorization header."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://adepts.of0x.cc",
              "refsource": "MISC",
              "url": "https://adepts.of0x.cc"
            },
            {
              "name": "https://twitter.com/TheXC3LL",
              "refsource": "MISC",
              "url": "https://twitter.com/TheXC3LL"
            },
            {
              "name": "https://x-c3ll.github.io",
              "refsource": "MISC",
              "url": "https://x-c3ll.github.io"
            },
            {
              "name": "https://support.ruckuswireless.com/documents",
              "refsource": "MISC",
              "url": "https://support.ruckuswireless.com/documents"
            },
            {
              "name": "https://support.ruckuswireless.com/security_bulletins/305",
              "refsource": "CONFIRM",
              "url": "https://support.ruckuswireless.com/security_bulletins/305"
            },
            {
              "name": "https://adepts.of0x.cc/ruckus-vriot-rce/",
              "refsource": "MISC",
              "url": "https://adepts.of0x.cc/ruckus-vriot-rce/"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2020-26879",
    "datePublished": "2020-10-26T19:20:44.000Z",
    "dateReserved": "2020-10-07T00:00:00.000Z",
    "dateUpdated": "2024-08-04T16:03:22.745Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

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.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.