# CVE-2015-3965: Privilege escalation in Symbiq Infusion System

> Remote authenticated users can escalate privileges to trigger unanticipated operations on Hospira Symbiq Infusion Systems.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fw6x-q668-xp72

## What is CVE-2015-3965?

CVE-2015-3965 is a high-severity vulnerability in Hospira Symbiq Infusion System, published on 23 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hospira Symbiq Infusion System 3.13 and earlier allows remote authenticated users to trigger "unanticipated operations" by leveraging "elevated privileges" for an unspecified call to an incorrectly exposed function.

Weakness: CWE-264

## Which versions are affected by CVE-2015-3965?

It affects 1 product.


Products: Pfizer Symbiq Infusion System Firmware.

## How do I fix CVE-2015-3965?

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

## Is CVE-2015-3965 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3965 and fix it if it is affected.

What it is: CVE-2015-3965 is a high-severity vulnerability in Hospira Symbiq Infusion System, published on 23 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3965 in the wild and no public exploit code.

Affected product: Hospira Symbiq Infusion System. 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-2015-3965/ (Markdown: https://insights.sbomify.com/CVE-2015-3965/index.md)
```

## Sources

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

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