# CVE-2019-6839: File upload in U.motion Servers (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX Server Plus, MEG6260-0410 - U.motion KNX Server Plus, Touch 10, and MEG6260-0415 - U.motion KNX Server Plus, Touch 1)

> Low-privilege users can upload malicious files to Schneider U.motion KNX servers, potentially leading to code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f2vv-v8xv-qgm8

## What is CVE-2019-6839?

CVE-2019-6839 is a high-severity vulnerability in U.motion Servers (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX Server Plus, MEG6260-0410 - U.motion KNX Server Plus, Touch 10, and MEG6260-0415 - U.motion KNX Server Plus, Touch 1), published on 17 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A CWE-434: Unrestricted Upload of File with Dangerous Type vulnerability exists in U.motion Server (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX Server Plus, MEG6260-0410 - U.motion KNX Server Plus, Touch 10, MEG6260-0415 - U.motion KNX Server Plus, Touch 15), which could allow a user with low privileges to upload a rogue file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 4 products.


Products: Schneider-Electric Meg6260-0410 Firmware, Schneider-Electric Meg6260-0415 Firmware, Schneider-Electric Meg6501-0001 Firmware, Schneider-Electric Meg6501-0002 Firmware.

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

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

## Is CVE-2019-6839 being exploited?

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

## Other vulnerabilities in U.motion Servers (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX Server Plus, MEG6260-0410 - U.motion KNX Server Plus, Touch 10, and MEG6260-0415 - U.motion KNX Server Plus, Touch 1)

- [CVE-2019-6840](https://insights.sbomify.com/CVE-2019-6840/): Code injection in U.motion Server (critical 9.8)
- [CVE-2019-6837](https://insights.sbomify.com/CVE-2019-6837/): Server-side request forgery in U.motion Server (critical 9.1)
- [CVE-2019-6836](https://insights.sbomify.com/CVE-2019-6836/): Missing authorization in U.motion Servers (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX Server Plus, MEG6260-0410 - U.motion KNX Server Plus, Touch 10, and MEG6260-0415 - U.motion KNX Server Plus, Touch 1) (high 7.5)
- [CVE-2019-6838](https://insights.sbomify.com/CVE-2019-6838/): Missing authorization in U.motion Servers (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX Server Plus, MEG6260-0410 - U.motion KNX Server Plus, Touch 10, and MEG6260-0415 - U.motion KNX Server Plus, Touch 1) (medium 6.5)
- [CVE-2019-6835](https://insights.sbomify.com/CVE-2019-6835/): Cross-site scripting in U.motion Server (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6839 is a high-severity vulnerability in U.motion Servers (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX Server Plus, MEG6260-0410 - U.motion KNX Server Plus, Touch 10, and MEG6260-0415 - U.motion KNX Server Plus, Touch 1), published on 17 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6839 in the wild and no public exploit code.

Affected product: U.motion Servers (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX Server Plus, MEG6260-0410 - U.motion KNX Server Plus, Touch 10, and MEG6260-0415 - U.motion KNX Server Plus, Touch 1). 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-6839/ (Markdown: https://insights.sbomify.com/CVE-2019-6839/index.md)
```

## Sources

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

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