# CVE-2019-13528: Missing authorization in Niagara

> Attackers can read privileged files via a specific utility in Niagara building automation systems, exposing sensitive configuration data.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g38f-pqr8-74j5

## What is CVE-2019-13528?

CVE-2019-13528 is a medium-severity missing authorization vulnerability in Niagara, published on 24 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A specific utility may allow an attacker to gain read access to privileged files in the Niagara AX 3.8u4 (JACE 3e, JACE 6e, JACE 7, JACE-8000), Niagara 4.4u3 (JACE 3e, JACE 6e, JACE 7, JACE-8000), and Niagara 4.7u1 (JACE-8000, Edge 10).

Weakness: CWE-285 (Improper Authorization)

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

It affects 2 products.


Products: Tridium Niagara4, Tridium Niagara Ax.

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

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

## Is CVE-2019-13528 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13528 is a medium-severity missing authorization vulnerability in Niagara, published on 24 Sep 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-13528 in the wild and no public exploit code.

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

## Sources

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

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