CVE-2014-7851: High severity ovirt vulnerability
It was reported that oVirt 3.2.2 and later did not correctly terminate sessions when a user logged out from the web interface (there are two sessions used between the browser and the backend: the engine and the restapi). Upon logout, only the engine session was invalidated but the restapi session persisted. If an attacker could obtain that session data and login with their own credentials, they could replace their session token with the stolen token and elevate their privileges to that of victim user. Note that in order for this to be exploited, the attacker must also have a valid login and authenticate successfully.
Other sources
oVirt 3.2.2 through 3.5.0 does not invalidate the restapi session after logout from the webadmin, which allows remote authenticated users with knowledge of another user's session data to gain that user's privileges by replacing their session token with that of another user.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2014-7851?
CVE-2014-7851 has a moderate severity level due to session management issues that could lead to unauthorized access after logout.
How do I fix CVE-2014-7851?
To fix CVE-2014-7851, ensure that your oVirt version is updated to at least 3.4.5 where the session termination issues have been resolved.
What are the affected versions of oVirt for CVE-2014-7851?
CVE-2014-7851 affects oVirt versions 3.2.2 and later, including various 3.3.x and 3.4.x versions.
What types of sessions are impacted in CVE-2014-7851?
CVE-2014-7851 specifically affects the engine session and the restapi session between the browser and backend.
Is user data at risk due to CVE-2014-7851?
Yes, due to improper session termination, there is a risk that user data could be exposed to unauthorized access after logging out.