# CVE-2018-18838: Other in n/a

> Attackers can inject newlines into registry API logs via URL parameters, potentially corrupting log integrity in Netdata.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-18838, GHSA-hqrf-v6fm-gv6x, UBUNTU-CVE-2018-18838

## What is CVE-2018-18838?

CVE-2018-18838 is a high-severity vulnerability in n/a, published on 18 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Netdata 1.10.0. Log Injection (or Log Forgery) exists via a %0a sequence in the url parameter to api/v1/registry.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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

It affects 1 product.


Products: My-Netdata Netdata.

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

Upgrade to a fixed version.

## Is CVE-2018-18838 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18836](https://insights.sbomify.com/CVE-2018-18836/): Code injection in n/a (medium 6.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-18838 and fix it if it is affected.

What it is: CVE-2018-18838 is a high-severity vulnerability in n/a, published on 18 Jun 2019. 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-18838 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-18838/ (Markdown: https://insights.sbomify.com/CVE-2018-18838/index.md)
```

## Sources

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

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