Opc Factory ServerApplication · Schneider Electric

CVE-2015-1014

HIGH · 7.3 CVSS v3.0 Published 2019-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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 · unedited
A successful exploit of these vulnerabilities requires the local user to load a crafted DLL file in the system directory on servers running Schneider Electric OFS v3.5 with version v7.40 of SCADA Expert Vijeo Citect/CitectSCADA, OFS v3.5 with version v7.30 of Vijeo Citect/CitectSCADA, and OFS v3.5 with version v7.20 of Vijeo Citect/CitectSCADA.. If the application attempts to open that file, the application could crash or allow the attacker to execute arbitrary code. Schneider Electric recommends vulnerable users upgrade the OFS to V3.5 and install the latest service pack (SP 6 or newer) for their associated version.

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 confidence

This is a DLL hijacking vulnerability in Schneider Electric OFS (OPC Foundation Server) v3.5 when bundled with SCADA Expert Vijeo Citect/CitectSCADA versions 7.20, 7.30, and 7.40. A local authenticated user can place a malicious DLL in the system directory; when the application loads it, the application may crash or permit arbitrary code execution.

MitigationSchneider Electric recommends upgrading OFS to V3.5 and installing the latest service pack (SP6 or newer) for the associated Vijeo Citect/CitectSCADA version.

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
Opc Factory ServerApplication
Affected:= 3.5

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OFS version
    Locate the OPC Factory Server installation directory (typically under the SCADA software folder) and check the version information of the OFS executable or DLL files, or query the Windows registry for the installed version under the appropriate Schneider Electric product keys
    Affected if The installed OFS version is exactly 3.5 and is bundled with Vijeo Citect/CitectSCADA versions 7.20, 7.30, or 7.40
  2. Confirm bundled Vijeo Citect version
    Check the installed version of Vijeo Citect or CitectSCADA on the system by examining the program's version information in the installation directory or via Add/Remove Programs
    Affected if The system has Vijeo Citect/CitectSCADA version 7.20, 7.30, or 7.40 installed with OFS 3.5
  3. Verify OFS service exists and runs
    Open Windows Services console and locate the OPC Factory Server service, check its status and startup type
    Affected if The OFS service is present and configured to run (the DLL would only be loaded when the service executes)
  4. Assess DLL search order exposure
    Examine the OFS installation directory and system directories for weak permissions that would allow an authenticated user to write files, and identify which DLLs OFS attempts to load from the system directory
    Affected if Authenticated users have write access to directories where OFS loads DLLs from, creating a hijacking opportunity

A system is affected if it runs OFS version 3.5 bundled with Vijeo Citect/CitectSCADA 7.20, 7.30, or 7.40, where an authenticated local user could place a malicious DLL in a location that OFS loads from.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Schneider Electric recommends upgrading OFS to V3.5 and installing the latest service pack (SP6 or newer) for the associated Vijeo Citect/CitectSCADA version.

Fix this in Opc Factory Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-1014 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-1014 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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