CVE-2024-0822
Auth Bypass in Ovirt-Engine
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-0822 is a high-severity Weak Authentication (CWE-1390) vulnerability in Ovirt Ovirt-Engine. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to IA-12 (Identity Proofing) and IA-2 (Identification and Authentication (Organizational Users)) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-16606
Vulnerability Data
An authentication bypass vulnerability was found in overt-engine. This flaw allows the creation of users in the system without authentication due to a flaw in the CreateUserSession command.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requires identity proofing at appropriate assurance levels before granting accounts, directly addressing insufficient proof of identity.
Requires unique identification and authentication of users, directly stopping weak mechanisms from being used.
Requires device identification and authentication before establishing connections.
Extends strong identification and authentication requirements to non-organizational users.
Mandates proper authenticator issuance, management, and strength to ensure claimed identities are verified.
Enforces access decisions based on authenticated identities, making weak authentication less exploitable.
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.
Mandating segregated approval and oversight for non-human identities reduces the chance that weak or orphaned credentials can be exploited for unauthorized authentication.
A.5.17 directly mandates non-guessable unique secrets, identity verification before issuance, secure transmission, immediate default changes, strong password enforcement, no reuse, and protected storage/transmission, which stops exploitation of most insufficient-proof cases in CWE-1390; the bounded remainder is non-password mechanisms (e.g. biometrics, certificates) or flawed protocol-level proof not covered by these password-centric rules.
Security requirements specified early and verified through testing drive the consistent implementation of authentication mechanisms, decreasing the likelihood that authentication steps are omitted or incorrectly applied.
A.8.26 explicitly requires identifying and addressing authentication-related requirements (including level of trust in identity via 8.5 and 5.17) as part of application development or acquisition, which prevents a slice of CWE-287 but leaves the dominant sufficiency-of-proof aspects (IA-2/IA-5) and many implementation defects untouched.
A.8.27 mandates security-by-design principles (least privilege, default-deny, never-trust/always-verify, MFA, end-to-end encryption of requests, distrust-external-input, secure session control, and explicit authentication/authorization in every layer), which directly stops most improper-authentication flaws from being exploitable; the bounded remainder is insufficient-proof cases that live only in the strength or correctness of the credential itself (IA-5/IA-2 territory).
A.8.5 directly mandates choosing sufficiently strong authentication techniques (including MFA, biometrics with fallback, brute-force protection, secure log-on procedures) that prove claimed identity, which stops exploitation of insufficient proof for most but not all cases in CWE-1390 (e.g. residual protocol-level or implementation-specific flaws remain possible).
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.