# CVE-2019-10678: Other in n/a

> Domoticz fails to sanitize newline characters in arguments, potentially allowing attackers to inject commands or manipulate system behavior.

- **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:** No
- **Published:** 31 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-59gx-x7r4-97q5

## What is CVE-2019-10678?

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

### Official description

Domoticz before 4.10579 neglects to categorize \n and \r as insecure argument options.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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

It affects 1 product.


Products: Domoticz Domoticz.

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

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

## Is CVE-2019-10678 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-10678 exists.

Public exploit code:

- cve-2019-10678 (github_poc): https://github.com/cved-sources/cve-2019-10678
- Domoticz 4.10577 - Unauthenticated Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-10664](https://insights.sbomify.com/CVE-2019-10664/): SQL injection in n/a (critical 9.8)
- [CVE-2019-15480](https://insights.sbomify.com/CVE-2019-15480/): Domoticz 4.10717 has XSS via item.Name. (medium 5.4)
- [CVE-2026-1001](https://insights.sbomify.com/CVE-2026-1001/): Domoticz < 2026.1 Stored XSS via Hardware Configuration Endpoint (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10678 is a high-severity vulnerability in n/a, published on 31 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-10678 exists.

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

## Sources

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

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