# CVE-2025-3938: Missing Cryptographic Step

> Attackers can perform cryptanalysis due to a missing cryptographic step in Tridium Niagara Framework, potentially exposing sensitive data.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2025
- **Updated:** 22 May 2025
- **Also known as:** GHSA-hcrg-qr57-hr37

## What is CVE-2025-3938?

CVE-2025-3938 is a medium-severity vulnerability in Tridium Niagara Enterprise Security, published on 22 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Missing Cryptographic Step vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Cryptanalysis. This issue affects Niagara Framework: before 4.14.2, before 4.15.1, before 4.10.11; Niagara Enterprise Security: before 4.14.2, before 4.15.1, before 4.10.11. Tridium recommends upgrading to Niagara Framework and Enterprise Security versions 4.14.2u2, 4.15.u1, or 4.10u.11.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-325 (Missing Cryptographic Step)

## Which versions are affected by CVE-2025-3938?

It affects 2 products.


Products: Tridium Niagara, Tridium Niagara Enterprise Security.

## How do I fix CVE-2025-3938?

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

## Is CVE-2025-3938 being exploited?

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

## Other vulnerabilities in Tridium Niagara Enterprise Security

- [CVE-2017-16748](https://insights.sbomify.com/CVE-2017-16748/): An attacker can log into the local Niagara platform (Niagara AX Framework Versions 3.8 and prior or Niagara 4 Framework Versions 4.4 and pri (critical 9.8)
- [CVE-2025-3937](https://insights.sbomify.com/CVE-2025-3937/): Use of Password Hash with Insufficient Computational Effort (high 7.7)
- [CVE-2025-3944](https://insights.sbomify.com/CVE-2025-3944/): Incorrect Permission Assignment for Critical Resource (high 7.2)
- [CVE-2025-3945](https://insights.sbomify.com/CVE-2025-3945/): Improper Neutralization of Argument Delimiters in a Command (‘Argument Injection’) (high 7.2)
- [CVE-2017-16744](https://insights.sbomify.com/CVE-2017-16744/): Path traversal in Niagara AX Framework and Niagara 4 Framework (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3938 and fix it if it is affected.

What it is: CVE-2025-3938 is a medium-severity vulnerability in Tridium Niagara Enterprise Security, published on 22 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3938 in the wild and no public exploit code.

Affected product: Tridium Niagara Enterprise Security. 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-2025-3938/ (Markdown: https://insights.sbomify.com/CVE-2025-3938/index.md)
```

## Sources

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

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