Tridium Niagara AX Framework does not properly store credential data, which allows context-dependent attackers to bypass intended access res
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.
- Published
- Jul 16, 2012
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 75th percentile
- CWE
- CWE-522
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| tridium | niagara ax | cpe:2.3:a:tridium:niagara_ax |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tridium niagara axall versions
Same product
tridium: all recordsOther highest-scoring records for the same primary product.
- CVE-2012-4701Directory traversal vulnerability in Tridium Niagara AX 3.5, 3.6, and 3.7 allows remote attackers to read sensitive files, and consequently 39Monitor
- CVE-2012-3025The default configuration of Tridium Niagara AX Framework through 3.6 uses a cleartext base64 format for transmission of credentials in cook21Monitor
- CVE-2012-3024Tridium Niagara AX Framework through 3.6 uses predictable values for (1) session IDs and (2) keys, which might allow remote attackers to byp21Monitor
- CVE-2012-4027Directory traversal vulnerability in Tridium Niagara AX Framework allows remote attackers to read files outside of the intended images, nav,21Monitor
- CVE-2019-13528A 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-80017Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- none
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-522 · Insufficiently Protected CredentialsCVSS vector
AV:N/AC:L/Au:N/C:C/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Session SidejackingCAPEC-102likelihood: High · High
- Signature Spoofing by Key TheftCAPEC-474likelihood: Medium · High
- Password Recovery ExploitationCAPEC-50likelihood: Medium · High
- KerberoastingCAPEC-509High
- Modify Existing ServiceCAPEC-551
- Remote Services with Stolen CredentialsCAPEC-555Very High
- Use of Known Domain CredentialsCAPEC-560likelihood: High · High
- Windows Admin Shares with Stolen CredentialsCAPEC-561
ATT&CK techniques
- Remote ServicesT1021
- Remote Services:SMB/Windows Admin SharesT1021.002
- Valid AccountsT1078
- Brute Force:Credential StuffingT1110.004
- Email Collection:Remote Email CollectionT1114.002
- External Remote ServicesT1133
- Create or Modify System ProcessT1543
- Use Alternate Authentication Material:Pass The HashT1550.002
- Use Alternate Authentication Material:Pass The TicketT1550.003
- Unsecured Credentials: Private KeysT1552.004
- Steal or Forge Kerberos TicketsT1558
- Steal or Forge Kerberos Tickets:KerberoastingT1558.003
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.washingtonpost.com/investigations/tridiums-niagara-framework-marvel-of-connectivity-illustrates-new-cyber-risks/2012/07/11/gJQARJL6dW_story.html
- www.tridium.com/galleries/briefings/NiagaraAX_Framework_Software_Security_Alert.pdf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.