# CVE-2019-10968: Business logic in Philips Holter 2010 Plus

> Attackers can enable unpurchased system options in Philips Holter 2010 Plus, bypassing licensing restrictions.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-233r-xcpj-wqr5

## What is CVE-2019-10968?

CVE-2019-10968 is a medium-severity vulnerability in Philips Holter 2010 Plus, published on 24 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Philips Holter 2010 Plus, all versions. A vulnerability has been identified that may allow system options that were not purchased to be enabled.

Weakness: CWE-477 (Use of Obsolete Function)

## Which versions are affected by CVE-2019-10968?

It affects 1 product.


Products: Philips Zymed Holter 2010.

## How do I fix CVE-2019-10968?

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

## Is CVE-2019-10968 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10968 and fix it if it is affected.

What it is: CVE-2019-10968 is a medium-severity vulnerability in Philips Holter 2010 Plus, published on 24 Jul 2019. 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-2019-10968 in the wild and no public exploit code.

Affected product: Philips Holter 2010 Plus. 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-2019-10968/ (Markdown: https://insights.sbomify.com/CVE-2019-10968/index.md)
```

## Sources

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

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