# CVE-2018-10988: Code injection in n/a

> Attackers can execute arbitrary code as root by placing unsigned scripts in specific SD card directories during boot on Diqee360 devices.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 5 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9hrw-rg2r-v3pr

## What is CVE-2018-10988?

CVE-2018-10988 is a high-severity code injection vulnerability in n/a, published on 5 Jul 2018. 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 Diqee Diqee360 devices. A firmware update process, integrated into the firmware, starts at boot and tries to find the update folder on the microSD card. It executes code, without a digital signature, as root from the /mnt/sdcard/$PRO_NAME/upgrade.sh or /sdcard/upgrage_360/upgrade.sh pathname.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 1 product.


Products: Diqee Diqee360 Firmware.

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

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

## Is CVE-2018-10988 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10987](https://insights.sbomify.com/CVE-2018-10987/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-10988 is a high-severity code injection vulnerability in n/a, published on 5 Jul 2018. 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-2018-10988 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-2018-10988/ (Markdown: https://insights.sbomify.com/CVE-2018-10988/index.md)
```

## Sources

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

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