VYPR

Niagara Ax

by Tridium

CVEs (7)

  • CVE-2017-16744HigAug 20, 2018
    risk 0.47cvss 7.2epss 0.06

    A path traversal vulnerability in Tridium Niagara AX Versions 3.8 and prior and Niagara 4 systems Versions 4.4 and prior installed on Microsoft Windows Systems can be exploited by leveraging valid platform (administrator) credentials.

  • CVE-2012-4701Feb 15, 2013
    risk 0.01cvss epss 0.06

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

  • CVE-2018-18985Jan 29, 2019
    risk 0.00cvss epss 0.01

    Tridium Niagara Enterprise Security 2.3u1, all versions prior to 2.3.118.6, Niagara AX 3.8u4, all versions prior to 3.8.401.1, Niagara 4.4u2, all versions prior to 4.4.93.40.2, and Niagara 4.6, all versions prior to 4.6.96.28.4 a cross-site scripting vulnerability has been…

  • CVE-2012-3025Aug 16, 2012
    risk 0.00cvss epss 0.02

    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 sniffing the network.

  • CVE-2012-3024Aug 16, 2012
    risk 0.00cvss epss 0.02

    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.

  • CVE-2012-4028Jul 16, 2012
    risk 0.00cvss epss 0.02

    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.

  • CVE-2012-4027Jul 16, 2012
    risk 0.00cvss epss 0.03

    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 reading the config.bog file.