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

> Local attackers can exploit HP Smart Update Manager to obtain sensitive information and gain elevated privileges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2x8v-gq44-cr6h

## What is CVE-2014-2608?

CVE-2014-2608 is a high-severity vulnerability in n/a, published on 10 Dec 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in HP Smart Update Manager 6.x before 6.4.1 on Windows, and 6.2.x through 6.4.x before 6.4.1 on Linux, allows local users to obtain sensitive information, and consequently gain privileges, via unknown vectors.

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

It affects 1 product.


Products: Hpe Smart Update Manager.

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

No fix has been published for CVE-2014-2608 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-2608 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-7136](https://insights.sbomify.com/CVE-2020-7136/): Auth bypass in Smart Update Manager (SUM) (critical 9.8)
- [CVE-2019-11988](https://insights.sbomify.com/CVE-2019-11988/): Auth bypass in HPE Smart Update Manager (critical 9.8)
- [CVE-2019-11987](https://insights.sbomify.com/CVE-2019-11987/): Privilege escalation in HPE Smart Update Manager (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2608 is a high-severity vulnerability in n/a, published on 10 Dec 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2608 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-2608/ (Markdown: https://insights.sbomify.com/CVE-2014-2608/index.md)
```

## Sources

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

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