# CVE-2019-7268: File upload in n/a

> Unauthenticated attackers can upload arbitrary files to Linear eMerge devices, potentially leading to remote code execution.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cccq-r4fh-564m

## What is CVE-2019-7268?

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

### Official description

Linear eMerge 50P/5000P devices allow Unauthenticated File Upload.

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

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

It affects 2 products.


Products: Nortekcontrol Linear Emerge 5000p Firmware, Nortekcontrol Linear Emerge 50p Firmware.

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

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

## Is CVE-2019-7268 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-7266](https://insights.sbomify.com/CVE-2019-7266/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-7267](https://insights.sbomify.com/CVE-2019-7267/): Path traversal in n/a (critical 9.8)
- [CVE-2019-7269](https://insights.sbomify.com/CVE-2019-7269/): Command injection in n/a (critical 9.8)
- [CVE-2019-7271](https://insights.sbomify.com/CVE-2019-7271/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-7270](https://insights.sbomify.com/CVE-2019-7270/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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