# CVE-2019-16398: Code injection in n/a

> Attackers can execute arbitrary code on Keeper K5 devices by inserting a malicious SD card, requiring physical access to the device.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 19 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qqf3-72cc-jc99

## What is CVE-2019-16398?

CVE-2019-16398 is a medium-severity code injection vulnerability in n/a, published on 19 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On Keeper K5 20.1.0.25 and 20.1.0.63 devices, remote code execution can occur by inserting an SD card containing a file named zskj_script_run.sh that executes a reverse shell.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2019-16398?

It affects 1 product.


Products: Keeper K5 Firmware.

## How do I fix CVE-2019-16398?

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

## Is CVE-2019-16398 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16398 and fix it if it is affected.

What it is: CVE-2019-16398 is a medium-severity code injection vulnerability in n/a, published on 19 Sep 2019. 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-2019-16398 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-2019-16398/ (Markdown: https://insights.sbomify.com/CVE-2019-16398/index.md)
```

## Sources

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

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