# CVE-2018-19025: Command injection in JUUKO K-808

> An attacker can execute arbitrary commands on the JUUKO K-808 by sending a specially crafted packet, potentially compromising the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Nov 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-882m-qg83-2rhq

## What is CVE-2018-19025?

CVE-2018-19025 is a critical command injection vulnerability in JUUKO K-808, published on 2 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In JUUKO K-808, an attacker could specially craft a packet that encodes an arbitrary command, which could be executed on the K-808 (Firmware versions prior to numbers ending ...9A, ...9B, ...9C, etc.).

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2018-19025?

It affects 1 product.


Products: Juuko K-808 Firmware.

## How do I fix CVE-2018-19025?

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

## Is CVE-2018-19025 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19025 and fix it if it is affected.

What it is: CVE-2018-19025 is a critical command injection vulnerability in JUUKO K-808, published on 2 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19025 in the wild and no public exploit code.

Affected product: JUUKO K-808. 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-2018-19025/ (Markdown: https://insights.sbomify.com/CVE-2018-19025/index.md)
```

## Sources

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

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