CVE-2020-26879

{"id": "CVE-2020-26879", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 10.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:C/I:C/A:C", "authentication": "NONE", "integrityImpact": "COMPLETE", "accessComplexity": "LOW", "availabilityImpact": "COMPLETE", "confidentialityImpact": "COMPLETE"}, "acInsufInfo": false, "impactScore": 10.0, "baseSeverity": "HIGH", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "published": "2020-10-26T20:15:14.537", "references": [{"url": "https://adepts.of0x.cc", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://adepts.of0x.cc/ruckus-vriot-rce/", "tags": ["Exploit", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://support.ruckuswireless.com/documents", "tags": ["Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://support.ruckuswireless.com/security_bulletins/305", "tags": ["Product", "Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://twitter.com/TheXC3LL", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://x-c3ll.github.io", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://adepts.of0x.cc", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://adepts.of0x.cc/ruckus-vriot-rce/", "tags": ["Exploit", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://support.ruckuswireless.com/documents", "tags": ["Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://support.ruckuswireless.com/security_bulletins/305", "tags": ["Product", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://twitter.com/TheXC3LL", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://x-c3ll.github.io", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-798"}]}], "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."}, {"lang": "es", "value": "Ruckus vRioT versiones hasta 1.5.1.0.21, presenta una puerta trasera de API que est\u00e1 embebida en el archivo validate_token.py. Un atacante no autenticado puede interactuar con la API de servicio al usar un valor de backdoor como el encabezado Authorization"}], "lastModified": "2024-11-21T05:20:24.057", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:commscope:ruckus_vriot:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "8EB1CEDE-0933-4FF7-AC4F-5960645DB455", "versionEndIncluding": "1.5.1.0.21"}], "operator": "OR"}, {"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:h:commscope:ruckus_iot_module:-:*:*:*:*:*:*:*", "vulnerable": false, "matchCriteriaId": "648717FE-6843-4847-842B-AD879026A39B"}], "operator": "OR"}], "operator": "AND"}], "sourceIdentifier": "cve@mitre.org"}