# CVE-2019-12777: Misconfiguration in n/a

> Insecure directory permissions in ENTTEC firmware allow all users to modify system files, enabling privilege escalation and code execution.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2vvj-x2x5-ghqg

## What is CVE-2019-12777?

CVE-2019-12777 is a high-severity vulnerability in n/a, published on 7 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on the ENTTEC Datagate MK2, Storm 24, Pixelator, and E-Streamer MK2 with firmware 70044_update_05032019-482. They replace secure and protected directory permissions (set as default by the underlying operating system) with highly insecure read, write, and execute directory permissions for all users. By default, /usr/local and all of its subdirectories should have permissions set to only allow non-privileged users to read and execute from the tree structure, and to deny users from creating or editing files in this location. The ENTTEC firmware startup script permits all users to read, write, and execute (rwxrwxrwx) from the /usr, /usr/local, /usr/local/dmxis, and /usr/local/bin/ directories.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 4 products.


Products: Enttec Datagate Mk2 Firmware, Enttec E-Streamer Mk2 Firmware, Enttec Pixelator Firmware, Enttec Storm 24 Firmware.

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

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

## Is CVE-2019-12777 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12776](https://insights.sbomify.com/CVE-2019-12776/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-12775](https://insights.sbomify.com/CVE-2019-12775/): Privilege escalation in n/a (high 8.8)
- [CVE-2019-6542](https://insights.sbomify.com/CVE-2019-6542/): Missing authorization in Datagate MK2 (high 7.5)
- [CVE-2019-12774](https://insights.sbomify.com/CVE-2019-12774/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12777 is a high-severity vulnerability in n/a, published on 7 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12777 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-12777/ (Markdown: https://insights.sbomify.com/CVE-2019-12777/index.md)
```

## Sources

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

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