CVE-2020-5849
Unraid 6.8.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2020-5849 is a high-severity Incorrect Comparison (CWE-697) vulnerability in Unraid Unraid. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Obfuscated Files or Information (T1027); ranked in the top 0.2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Unraid 6.8.0 contains an authentication bypass vulnerability tracked as CVE-2020-5849 and assigned CWE-697. The flaw received a CVSS 3.1 base score of 7.5 reflecting network attack vector, low complexity, and no required credentials or user interaction, resulting in high confidentiality impact while leaving integrity and availability unaffected.
Unauthenticated attackers with network access can exploit the issue to bypass authentication controls. Successful exploitation grants the ability to access restricted resources or data that would otherwise require valid credentials.
Public references, including disclosures on Packet Storm and detailed analyses from Sysdream, link the bypass to unauthenticated remote code execution as root on the affected Unraid release; the vendor’s announcement forum provides the primary channel for subsequent updates. No information on confirmed in-the-wild exploitation is supplied in the source data.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-27003
Vulnerability Data
Unraid 6.8.0 allows authentication bypass.
- CWE(s)
- KEV Date Added
- 03 November 2021
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly require correct logic for security comparisons and thereby prevent this class of flaw.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect incorrect comparison flaws before deployment.
Secure development lifecycle includes code review and testing that can catch incorrect comparison logic.
Application security requirements can mandate correct comparison logic for security decisions.
Secure architecture principles can require robust comparison mechanisms for access decisions.
Secure coding standards directly address avoiding incorrect comparison operators and logic.
Secure authentication mechanisms rely on correct comparison of credentials or tokens.