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

> Attackers can execute arbitrary code via JSON injection in the Netdata API, requiring an upgrade to secure the monitoring server.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-18836, GHSA-h9cp-8fw3-4wc5, UBUNTU-CVE-2018-18836

## What is CVE-2018-18836?

CVE-2018-18836 is a medium-severity code injection vulnerability in n/a, published on 18 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Netdata 1.10.0. JSON injection exists via the api/v1/data tqx parameter because of web_client_api_request_v1_data in web/api/web_api_v1.c.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: My-Netdata Netdata.

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

Upgrade to a fixed version.

## Is CVE-2018-18836 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18838](https://insights.sbomify.com/CVE-2018-18838/): Other in n/a (high 7.5)
- [CVE-2018-18837](https://insights.sbomify.com/CVE-2018-18837/): Other in n/a (medium 6.1)
- [CVE-2018-18839](https://insights.sbomify.com/CVE-2018-18839/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18836 is a medium-severity code injection vulnerability in n/a, published on 18 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-18836 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-18836/ (Markdown: https://insights.sbomify.com/CVE-2018-18836/index.md)
```

## Sources

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

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