First published: Tue Nov 18 2014(Updated: )
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.
Affected Software | Affected Version | How to fix |
---|---|---|
Ovirt | >=3.2.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1165311 is considered moderate due to session handling issues that could lead to unauthorized access.
To fix REDHAT-BUG-1165311, ensure that all relevant updates and patches for oVirt are applied to mitigate session termination issues.
oVirt versions 3.2.2 and later are affected by REDHAT-BUG-1165311.
REDHAT-BUG-1165311 affects the session termination mechanism between the web interface and the backend in oVirt.
Yes, user data may be at risk in REDHAT-BUG-1165311 due to improper session termination, allowing potential unauthorized access.