# CVE-2019-12736: Command injection in n/a

> Attackers can execute arbitrary commands via unsanitized LDAP usernames in the Ktor framework, requiring an upgrade to mitigate.

- **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 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7wjj-fwv4-7v29

## What is CVE-2019-12736?

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

### Official description

JetBrains Ktor framework before 1.2.0-rc does not sanitize the username provided by the user for the LDAP protocol, leading to command injection.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2019-12736?

It affects 1 product.


Products: Jetbrains Ktor.

## How do I fix CVE-2019-12736?

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

## Is CVE-2019-12736 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29930](https://insights.sbomify.com/CVE-2022-29930/): SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. (high 8.7)
- [CVE-2023-45612](https://insights.sbomify.com/CVE-2023-45612/): XML external entity in Ktor (high 8.6)
- [CVE-2022-48476](https://insights.sbomify.com/CVE-2022-48476/): Path traversal in Ktor (high 7.5)
- [CVE-2021-43203](https://insights.sbomify.com/CVE-2021-43203/): Auth bypass in n/a (high 7.5)
- [CVE-2023-45613](https://insights.sbomify.com/CVE-2023-45613/): Security feature bypass in Ktor (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12736 and fix it if it is affected.

What it is: CVE-2019-12736 is a critical command injection vulnerability in n/a, published on 2 Oct 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-2019-12736 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-2019-12736/ (Markdown: https://insights.sbomify.com/CVE-2019-12736/index.md)
```

## Sources

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

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