# CVE-2014-0153: Information disclosure in n/a

> Remote attackers can steal session IDs from HTML5 local storage via a crafted web page, potentially leading to account takeover.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mpx4-8rp2-j882

## What is CVE-2014-0153?

CVE-2014-0153 is a medium-severity vulnerability in n/a, published on 8 Sep 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-0153?

It affects 1 product.


Products: Ovirt Ovirt.

## How do I fix CVE-2014-0153?

Upgrade to a fixed version.

## Is CVE-2014-0153 being exploited?

There is no known exploitation of CVE-2014-0153 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-1074](https://insights.sbomify.com/CVE-2018-1074/): Information disclosure in ovirt-engine (high 7.7)
- [CVE-2014-7851](https://insights.sbomify.com/CVE-2014-7851/): Auth bypass in n/a (high 7.5)
- [CVE-2017-15113](https://insights.sbomify.com/CVE-2017-15113/): Information disclosure in ovirt-engine (high 7.2)
- [CVE-2014-0152](https://insights.sbomify.com/CVE-2014-0152/): Auth bypass in n/a (medium 6.8)
- [CVE-2019-3879](https://insights.sbomify.com/CVE-2019-3879/): Missing authorization in ovirt-engine (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0153 and fix it if it is affected.

What it is: CVE-2014-0153 is a medium-severity vulnerability in n/a, published on 8 Sep 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-0153 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-0153/ (Markdown: https://insights.sbomify.com/CVE-2014-0153/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0153
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0153
- OSV: https://osv.dev/vulnerability/CVE-2014-0153

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-0153/
Summaries are generated and may contain mistakes; the official description above is the record.