# CVE-2020-27260: Code injection in BIGCOMPANYSOFT SOFTWARE PRODUCT

> Physically proximate attackers can inject HL7 segments into vital signs monitor messages via barcode readers, potentially altering patient data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9r75-h3r2-c7wf

## What is CVE-2020-27260?

CVE-2020-27260 is a medium-severity code injection vulnerability in BIGCOMPANYSOFT SOFTWARE PRODUCT, published on 8 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Innokas Yhtymä Oy Vital Signs Monitor VC150 prior to Version 1.7.15 HL7 v2.x injection vulnerabilities exist in the affected products that allow physically proximate attackers with a connected barcode reader to inject HL7 v2.x segments into specific HL7 v2.x messages via multiple expected parameters.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2020-27260?

It affects 1 product.


Products: Innokasmedical Vital Signs Monitor Vc150 Firmware.

## How do I fix CVE-2020-27260?

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

## Is CVE-2020-27260 being exploited?

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

## Other vulnerabilities in BIGCOMPANYSOFT SOFTWARE PRODUCT

- [CVE-2020-27262](https://insights.sbomify.com/CVE-2020-27262/): Cross-site scripting in Innokas Yhtymä Oy Vital Signs Monitor VC150 (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-27260 and fix it if it is affected.

What it is: CVE-2020-27260 is a medium-severity code injection vulnerability in BIGCOMPANYSOFT SOFTWARE PRODUCT, published on 8 Jan 2021. 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-2020-27260 in the wild and no public exploit code.

Affected product: BIGCOMPANYSOFT SOFTWARE PRODUCT. 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-2020-27260/ (Markdown: https://insights.sbomify.com/CVE-2020-27260/index.md)
```

## Sources

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

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