# CVE-2017-12699: Privilege escalation in AzeoTech DAQFactory

> Local attackers can replace application files due to incorrect default permissions, leading to privilege escalation and potential code execution in DAQFactory.

- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 9 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h5fh-wgq8-2vr7

## What is CVE-2017-12699?

CVE-2017-12699 is a high-severity vulnerability in AzeoTech DAQFactory, published on 9 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Incorrect Default Permissions issue was discovered in AzeoTech DAQFactory versions prior to 17.1. Local, non-administrative users may be able to replace or modify original application files with malicious ones.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2017-12699?

It affects 1 product.


Products: Azeotech Daqfactory.

## How do I fix CVE-2017-12699?

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

## Is CVE-2017-12699 being exploited?

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

## Other vulnerabilities in AzeoTech DAQFactory

- [CVE-2011-3492](https://insights.sbomify.com/CVE-2011-3492/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4480](https://insights.sbomify.com/CVE-2009-4480/): Memory corruption in n/a (critical 9.3)
- [CVE-2026-12921](https://insights.sbomify.com/CVE-2026-12921/): Use after free in AzeoTech DAQFactory (high 8.4)
- [CVE-2026-12390](https://insights.sbomify.com/CVE-2026-12390/): Access of resource using incompatible type ('type confusion') in AzeoTech DAQFactory (high 8.4)
- [CVE-2025-66588](https://insights.sbomify.com/CVE-2025-66588/): Access of Uninitialized Pointer vulnerability in AzeoTech DAQFactory (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12699 and fix it if it is affected.

What it is: CVE-2017-12699 is a high-severity vulnerability in AzeoTech DAQFactory, published on 9 Sep 2017. 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-2017-12699 in the wild and no public exploit code.

Affected product: AzeoTech DAQFactory. 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-2017-12699/ (Markdown: https://insights.sbomify.com/CVE-2017-12699/index.md)
```

## Sources

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

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