Niagara Ax vulnerabilitiesRanked by how likely they are to be used.

Product4 versions
The short answer

Niagara Ax is made by Tridium. We track 6 published vulnerabilities listed under that exact name, across 4 versions. None of them is on the list of flaws known to be exploited today. Tridium lists newer releases under their own names, such as Niagara Ax Framework, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Niagara Ax listed under other names? Yes.

Tridium also lists Niagara Ax under more specific names, such as Niagara Ax Framework. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Niagara Ax vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Niagara Ax's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Niagara Ax flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 6.4%

    Directory traversal vulnerability in Tridium Niagara AX 3.5, 3.6, and 3.7 allows remote attackers to read sensitive files, and consequently execute arbitrary code, by leveraging (1) valid credentials or (2) the guest...

    CVSS9.3Published15 Feb 2013
  2. 2.5%

    Directory traversal vulnerability in Tridium Niagara AX Framework allows remote attackers to read files outside of the intended images, nav, and px folders by leveraging incorrect permissions, as demonstrated by...

    CVSS5.0Published16 Jul 2012
  3. 2.2%

    Tridium Niagara AX Framework through 3.6 uses predictable values for (1) session IDs and (2) keys, which might allow remote attackers to bypass authentication via a brute-force attack.

    CVSS5.0Published16 Aug 2012
  4. 1.9%

    The default configuration of Tridium Niagara AX Framework through 3.6 uses a cleartext base64 format for transmission of credentials in cookies, which allows remote attackers to obtain sensitive information by...

    CVSS5.0Published16 Aug 2012
  5. 1.6%

    Tridium Niagara AX Framework does not properly store credential data, which allows context-dependent attackers to bypass intended access restrictions by using the stored information for authentication.

    CVSS7.8Published16 Jul 2012
  6. 0.4%

    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...

    CVSS4.4Published24 Sep 2019
Precursor Intelligence

Running Niagara Ax? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 6 published vulnerabilities listed under the name Niagara Ax, across 4 versions.

None of Niagara Ax's vulnerabilities is on the list of flaws known to be exploited today.

Tridium also lists Niagara Ax under more specific names, such as Niagara Ax Framework. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Niagara Ax. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.