CVE-2014-2377
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 · uneditedEcava IntegraXor SCADA Server Stable 4.1.4360 and earlier and Beta 4.1.4392 and earlier allows remote attackers to discover full pathnames via an application tag.
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 · high confidenceEcava IntegraXor SCADA Server versions 4.1.4360 and earlier (stable) and 4.1.4392 and earlier (beta) contains an information disclosure vulnerability where application tags expose full server pathnames to remote attackers. This path disclosure could assist attackers in mapping system internals and crafting follow-up attacks.
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.1.4360<= 4.1.4392CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Verify Ecava IntegraXor is installedCheck for the IntegraXor service running on the system, or look for the installation directory (commonly at C:\IntegraXor or similar). In Windows, check Services list for 'IntegraXor' service.Affected if The IntegraXor service or installation is found on the system
-
Determine installed version numberOpen the IntegraXor web interface and navigate to the About/Help section, or check the version info in the installed executable files. The version is typically displayed in the application title bar or in the system tray icon tooltip when the service is running.Affected if Version returned is 4.1.4360 or lower for stable, or 4.1.4392 or lower for beta
-
Compare version to affected rangesDocument the exact version number found and compare against the affected ranges: stable versions <= 4.1.4360 and beta versions <= 4.1.4392Affected if The installed version falls within or below these version numbers
-
Inspect application tag responses for path disclosureIf the web interface is accessible, query application tags or metadata through the SCADA web API or pages. Observe whether the returned responses contain full Windows server pathnames (e.g., C:\IntegraXor\... or similar directory structures).Affected if Application tag data or metadata responses expose full local filesystem paths
A system is affected if Ecava IntegraXor SCADA Server is installed with a stable version <= 4.1.4360 or beta version <= 4.1.4392, and the application tags expose server filesystem paths.
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 dataUpgrade to a patched version of IntegraXor SCADA Server. If patching is not immediately feasible, implement network segmentation and access controls to limit exposure of the SCADA interface to trusted personnel only.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2377 — 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-2014-2377 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