# CVE-2014-7898: Other in n/a

> Remote attackers can execute arbitrary code on HP Point of Sale Windows PCs via vulnerable OLE Point of Sale drivers.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 9 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-24r3-qrv6-6jx6

## What is CVE-2014-7898?

CVE-2014-7898 is a critical vulnerability in n/a, published on 9 Mar 2015. It can be exploited over the network.

### Official description

The OLE Point of Sale (OPOS) drivers before 1.13.003 on HP Point of Sale Windows PCs allow remote attackers to execute arbitrary code via unspecified vectors.

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

It affects 1 product.


Products: Hp Ole Point of Sale Driver.

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

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

## Is CVE-2014-7898 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-7888](https://insights.sbomify.com/CVE-2014-7888/): Code injection in n/a (critical 10.0)
- [CVE-2014-7889](https://insights.sbomify.com/CVE-2014-7889/): Code injection in n/a (critical 10.0)
- [CVE-2014-7890](https://insights.sbomify.com/CVE-2014-7890/): Code injection in n/a (critical 10.0)
- [CVE-2014-7891](https://insights.sbomify.com/CVE-2014-7891/): Code injection in n/a (critical 10.0)
- [CVE-2014-7892](https://insights.sbomify.com/CVE-2014-7892/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-7898 is a critical vulnerability in n/a, published on 9 Mar 2015. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2014-7898 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-7898/ (Markdown: https://insights.sbomify.com/CVE-2014-7898/index.md)
```

## Sources

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

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