Skip to content
Fencer Intel
medium 5.0

CVE-2014-0154 json

oVirt Engine before 3.5.0 does not include the HTTPOnly flag in a Set-Cookie header for the session IDs, which makes it easier for remote a…

published 2015-02-13 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0213

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

oVirt Engine before 3.5.0 does not include the HTTPOnly flag in a Set-Cookie header for the session IDs, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

Patch / fix

  • rhevm rhev manager 3 3.5.0-0.29.el6ev
  • rhevm-lib rhev manager 3 3.5.0-0.29.el6ev
  • rhevm-setup rhev manager 3 3.5.0-0.29.el6ev
  • rhevm-tools rhev manager 3 3.5.0-0.29.el6ev
  • rhevm-backend rhev manager 3 3.5.0-0.29.el6ev
  • rhevm-restapi rhev manager 3 3.5.0-0.29.el6ev
  • rhevm-dbscripts rhev manager 3 3.5.0-0.29.el6ev
  • rhevm-setup-base rhev manager 3 3.5.0-0.29.el6ev

red hat advisories RHSA-2015:0158

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-0154 updated cvss 4.3

ovirt-engine-webadmin: HttpOnly flag is not included when the session ID is set

  • Red Hat RHEV-M 3.5 rhevm 3.5.0-0.29.el6ev, rhevm-lib 3.5.0-0.29.el6ev, rhevm-setup 3.5.0-0.29.el6ev, rhevm-tools 3.5.0-0.29.el6ev, rhevm-backend 3.5.0-0.29.el6ev, rhevm-restapi 3.5.0-0.29.el6ev, +11 more
    fixed: vendor fix RHSA-2015:0158

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.74% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.