# CVE-2020-27375: Server-side request forgery in n/a

> The blood pressure monitor firmware allows attackers to transmit unauthorized write requests and characters, potentially compromising device integrity and data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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:** 7 Apr 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-qcx6-wgpr-5gxc

## What is CVE-2020-27375?

CVE-2020-27375 is a medium-severity server-side request forgery vulnerability in n/a, published on 7 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dr Trust USA iCheck Connect BP Monitor BP Testing 118 version 1.2.1 is vulnerable to Transmitting Write Requests and Chars.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Drtrustusa Icheck Connect Bp Monitor Bp Testing 118 Firmware.

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

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

## Is CVE-2020-27375 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-27373](https://insights.sbomify.com/CVE-2020-27373/): Command injection in n/a (high 8.8)
- [CVE-2020-27376](https://insights.sbomify.com/CVE-2020-27376/): Missing authorization in n/a (high 8.8)
- [CVE-2020-27374](https://insights.sbomify.com/CVE-2020-27374/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27375 is a medium-severity server-side request forgery vulnerability in n/a, published on 7 Apr 2022. 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-27375 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-27375/ (Markdown: https://insights.sbomify.com/CVE-2020-27375/index.md)
```

## Sources

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

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