CVE-2018-18985
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTridium 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 identified that may allow a remote attacker to inject code to some web pages affecting confidentiality.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-site scripting (XSS) vulnerability in Tridium Niagara web framework versions prior to patches. Allows remote attackers to inject malicious script into web pages, potentially compromising user sessions and accessing sensitive data through the browser.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.4.93.40.2>= 4.6, < 4.6.96.28.4= 4.4u2< 3.8.401.1= 3.8u4< 2.3.118.6= 2.3u1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Tridium Niagara product installedLocate the Niagara installation directory or check running services for Tridium components. Look for 'Niagara', 'Nre', or 'Ntd' processes on the system.Affected if Any Tridium Niagara product (Niagara, Niagara Ax Framework, or Niagara Enterprise Security) is installed
-
Determine the installed Niagara versionAccess the Niagara web interface login page or check version information in the installation. The version is typically displayed on the login screen or can be found in system information files within the installation directory.Affected if The version displayed matches any of the affected ranges: < 4.4.93.40.2, = 4.4u2, >= 4.6 and < 4.6.96.28.4, < 3.8.401.1, = 3.8u4, < 2.3.118.6, or = 2.3u1
-
Verify the web interface is accessibleConfirm the Niagara web portal is reachable by accessing the host URL (typically ports 80, 443, or 8080). Check if the login page loads successfully.Affected if The web interface is exposed and accessible over the network
-
Compare your version to the affected rangesCross-reference your identified version against the vulnerable ranges: Niagara < 4.4.93.40.2 (except 4.4u2), Niagara 4.6 to < 4.6.96.28.4, Niagara Ax Framework < 3.8.401.1 (except 3.8u4), Niagara Enterprise Security < 2.3.118.6 (except 2.3u1).Affected if Your installed version falls within any of these vulnerable ranges
You are affected if a Tridium Niagara web interface is running with a version that matches any of the specified vulnerable version ranges and is accessible to users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.3.118.63.8.401.14.4.93.40.2
Apply vendor patches (2.3.118.6, 3.8.401.1, 4.4.93.40.2, 4.6.96.28.4 or later). Until patched, implement output encoding and input validation on affected web interfaces.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18985 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-18985 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data