CVE-2014-9198
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 · uneditedThe FTP server on the Schneider Electric ETG3000 FactoryCast HMI Gateway with firmware through 1.60 IR 04 has hardcoded credentials, which makes it easier for remote attackers to obtain access via an FTP session.
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 confidenceThe Schneider Electric ETG3000 FactoryCast HMI Gateway FTP server contains hardcoded credentials embedded in the firmware, allowing remote attackers to authenticate without knowing the credentials. This is a critical vulnerability as it provides direct unauthenticated remote access to the industrial device.
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<= 1.60.4all versionsall versionsall versionsall versionsCVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label, web interface, or management console to confirm the exact model number (Etg3000, Tsxetg3000, Tsxetg3010, Tsxetg3021, or Tsxetg3022)Affected if The device model matches any of the affected models listed in the CVE (ETG3000 or any TSXETG variant)
-
Check the firmware versionAccess the device web interface or use SNMP/management interface to retrieve the firmware version informationAffected if For Etg3000 firmware: version is 1.60.4 or lower; for any TSXETG model: any version is affected
-
Verify if FTP service is enabledCheck device configuration or scan network for open port 21 (FTP) on the device IP addressAffected if FTP service is running and accessible on the device
-
Assess network exposure of FTP portReview firewall rules, network segmentation, and ACLs to determine if port 21 is reachable from untrusted networks or the internetAffected if FTP port is exposed to untrusted networks without proper access controls
-
Test FTP authenticationAttempt to connect to the FTP service using the device IP and try authentication - compare results against known hardcoded credential patterns for this deviceAffected if FTP authentication succeeds with default, manufacturer-embedded, or easily guessable credentials without user configuration
A user is affected if the device is a Schneider Electric ETG3000 or TSXETG3000-series model running the vulnerable firmware or any version, with FTP enabled and accessible from their network.
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 dataReplace or remove hardcoded FTP credentials, disable the FTP service if unnecessary, and update to a patched firmware version. Implement network segmentation to limit exposure of the device to untrusted networks.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9198 — 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-9198 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