# CVE-2020-15485: Information disclosure in n/a

> Attackers with physical access can read and tamper with cleartext data stored in the device's flash memory.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 26 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3847-mrxp-mph6

## What is CVE-2020-15485?

CVE-2020-15485 is a medium-severity vulnerability in n/a, published on 26 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on Nescomed Multipara Monitor M1000 devices. The onboard Flash memory stores data in cleartext, without integrity protection against tampering.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Niscomed M1000 Multipara Patient Monitor Firmware.

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

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

## Is CVE-2020-15485 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15482](https://insights.sbomify.com/CVE-2020-15482/): Hardcoded credentials in n/a (high 7.8)
- [CVE-2020-15484](https://insights.sbomify.com/CVE-2020-15484/): Information disclosure in n/a (high 7.5)
- [CVE-2020-15483](https://insights.sbomify.com/CVE-2020-15483/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-15485 is a medium-severity vulnerability in n/a, published on 26 Aug 2020. 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-15485 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-2020-15485/ (Markdown: https://insights.sbomify.com/CVE-2020-15485/index.md)
```

## Sources

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

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