Skip to content
Fencer Intel
medium 4.3

CVE-2014-0153 json

The REST API in oVirt 3.4.0 and earlier stores session IDs in HTML5 local storage, which allows remote attackers to obtain sensitive inform…

published 2014-09-08 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0212

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

Summary

The REST API in oVirt 3.4.0 and earlier stores session IDs in HTML5 local storage, which allows remote attackers to obtain sensitive information via a crafted web page.

Patch / fix

  • rhevm rhev manager 3 3.4.0-0.21.el6ev
  • rhevm-lib rhev manager 3 3.4.0-0.21.el6ev
  • rhevm-setup rhev manager 3 3.4.0-0.21.el6ev
  • rhevm-tools rhev manager 3 3.4.0-0.21.el6ev
  • rhevm-backend rhev manager 3 3.4.0-0.21.el6ev
  • rhevm-restapi rhev manager 3 3.4.0-0.21.el6ev
  • rhevm-dbscripts rhev manager 3 3.4.0-0.21.el6ev
  • rhevm-setup-base rhev manager 3 3.4.0-0.21.el6ev

red hat advisories RHSA-2014:0506

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-0153 updated cvss 4.3

ovirt-engine-api: session ID stored in HTML5 local storage

  • Red Hat RHEV-M 3.4 rhevm 3.4.0-0.21.el6ev, rhevm-lib 3.4.0-0.21.el6ev, rhevm-setup 3.4.0-0.21.el6ev, rhevm-tools 3.4.0-0.21.el6ev, rhevm-backend 3.4.0-0.21.el6ev, rhevm-restapi 3.4.0-0.21.el6ev, +9 more
    fixed: vendor fix RHSA-2014:0506

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.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/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.