dbcve.org
Ofs Test Client Tlxcdlfofs33Application · Schneider Electric

CVE-2014-0774

MEDIUM · 6.9 CVSS v2.0 Published 2014-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
No privileges Zero-click

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
Stack-based buffer overflow in the C++ sample client in Schneider Electric OPC Factory Server (OFS) TLXCDSUOFS33 - 3.35, TLXCDSTOFS33 - 3.35, TLXCDLUOFS33 - 3.35, TLXCDLTOFS33 - 3.35, and TLXCDLFOFS33 - 3.35 allows local users to gain privileges via vectors involving a malformed configuration file.

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 confidence

Stack-based buffer overflow in the C++ sample client of Schneider Electric OPC Factory Server allows local users to gain privileges by supplying a malformed configuration file. The vulnerability stems from insufficient bounds checking when parsing the configuration, leading to stack memory corruption.

MitigationReplace or disable the vulnerable sample client in production environments. Apply vendor patches when available. If the sample client is required, implement strict input validation on configuration files before parsing.

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
Ofs Test Client Tlxcdlfofs33Application
Affected:= 3.35
Ofs Test Client Tlxcdltofs33Application
Affected:= 3.35
Ofs Test Client Tlxcdluofs33Application
Affected:= 3.35
Ofs Test Client Tlxcdstofs33Application
Affected:= 3.35
Ofs Test Client Tlxcdsuofs33Application
Affected:= 3.35
Opc Factory ServerApplication
Affected:= 3.35

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:M/Au:N/C:C/I:C/A:C

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 Schneider Electric OPC products
    Check the system for installed Schneider Electric OPC Factory Server or any Ofs Test Client components (Tlxcdlfofs33, Tlxcdltofs33, Tlxcdluofs33, Tlxcdstofs33, Tlxcdsuofs33) via installed programs list, registry keys (HKLM\SOFTWARE\Schneider Electric\ or similar), or file system inspection of typical installation directories (C:\Program Files\Schneider Electric\OPC Foundation\ or similar).
    Affected if Any of the listed products (OPC Factory Server or any Ofs Test Client variant) is present on the system.
  2. Verify the installed version is 3.35
    Locate the version information for the installed product - check the program's Properties in Add/Remove Programs, version info in the executable file properties, or version entries in the registry. Compare the version number to the affected version = 3.35.
    Affected if The installed version is exactly 3.35 for any affected product.
  3. Confirm the sample client component is present
    Search for the specific sample client executable or DLL files associated with the Ofs Test Client (commonly named containing 'testclient', 'sampleclient', 'tlxcdl' or similar patterns) within the OPC Factory Server installation directory.
    Affected if The C++ sample client (Ofs Test Client) executable or its binaries exist on the system.
  4. Locate configuration files for the sample client
    Search the installation directory and user directories for configuration files used by the sample client (look for .cfg, .ini, .xml, or similar config files associated with the test client).
    Affected if Configuration files intended for the sample client are present on the system.

A system is affected if Schneider Electric OPC Factory Server or any Ofs Test Client variant (Tlxcdlfofs33, Tlxcdltofs33, Tlxcdluofs33, Tlxcdstofs33, Tlxcdsuofs33) is installed with version exactly 3.35 and the sample client component is present and operational.

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

Replace or disable the vulnerable sample client in production environments. Apply vendor patches when available. If the sample client is required, implement strict input validation on configuration files before parsing.

Fix this in Ofs Test Client Tlxcdlfofs33 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2014-0774 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