# CVE-2018-14839: LG N1A1 NAS Remote Command Execution

> Remote attackers can execute arbitrary code on LG N1A1 NAS devices via crafted HTTP POST requests.

- **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:** Yes, since 25 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-9h95-rv82-cwrc

## What is CVE-2018-14839?

CVE-2018-14839 is a critical command injection vulnerability in n/a, published on 14 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LG N1A1 NAS 3718.510 is affected by: Remote Command Execution. The impact is: execute arbitrary code (remote). The attack vector is: HTTP POST with parameters.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Lg N1a1 Firmware.

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

No fix has been published for CVE-2018-14839 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2018-14839 being exploited?

Yes. Attackers have exploited CVE-2018-14839 in the wild since at least 25 Mar 2022.

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14839 is a critical command injection vulnerability in n/a, published on 14 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-14839 in the wild since at least 25 Mar 2022.

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-14839/ (Markdown: https://insights.sbomify.com/CVE-2018-14839/index.md)
```

## Sources

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

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