# CVE-2023-28390: Privilege escalation in SR-7100VN

> A network-adjacent attacker with admin privileges can escalate to OS root and execute arbitrary commands on ICOM SR-7100VN marine radios.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 23 May 2023
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-gfm4-w4mv-hcmp

## What is CVE-2023-28390?

CVE-2023-28390 is a medium-severity vulnerability in ICOM INCORPORATED SR-7100VN, published on 23 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Privilege escalation vulnerability in SR-7100VN firmware Ver.1.38(N) and earlier and SR-7100VN #31 firmware Ver.1.21 and earlier allows a network-adjacent attacker with administrative privilege of the affected product to obtain an administrative privilege of the OS (Operating System). As a result, an arbitrary OS command may be executed.

## Which versions are affected by CVE-2023-28390?

It affects 2 products.


Products: Icom Sr-7100vn\#31 Firmware, Icom Sr-7100vn Firmware.

## How do I fix CVE-2023-28390?

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

## Is CVE-2023-28390 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28390 and fix it if it is affected.

What it is: CVE-2023-28390 is a medium-severity vulnerability in ICOM INCORPORATED SR-7100VN, published on 23 May 2023. 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-2023-28390 in the wild and no public exploit code.

Affected product: ICOM INCORPORATED SR-7100VN. 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-2023-28390/ (Markdown: https://insights.sbomify.com/CVE-2023-28390/index.md)
```

## Sources

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

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