CVE-2011-1918
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 · uneditedStack-based buffer overflow in the Data Archiver service in GE Intelligent Platforms Proficy Historian before 3.5 SIM 17 and 4.x before 4.0 SIM 12 allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via crafted TCP message traffic.
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 confidenceStack-based buffer overflow in the Data Archiver service of GE Proficy Historian allows remote attackers to send crafted TCP messages that overflow a stack buffer, potentially enabling denial of service (daemon crash) or arbitrary code execution. The vulnerability exists in versions prior to 3.5 SIM 17 and 4.x before 4.0 SIM 12.
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<= 3.5= 4.0CVSS 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 if GE Proficy Historian is installedCheck installed programs or registry for GE Proficy Historian. Look in Program Files for GE Intelligent Platforms folders.Affected if GE Proficy Historian is found on the system
-
Determine the installed version of GE Proficy HistorianUse the Historian Administrator or check the program's About/Version information. Look for SIM (Service Information Module) version numbers.Affected if Version is 3.5 or earlier, or version 4.0 before SIM 12
-
Locate the Data Archiver serviceCheck Windows Services for 'GE Proficy Historian Data Archiver' or similar service name. The service typically runs as part of the Historian installation.Affected if Data Archiver service exists and is running
-
Assess network exposure of Data ArchiverCheck if the Data Archiver TCP port (default listener port) is exposed to untrusted networks. Use netstat or firewall rules to identify listening ports and their accessibility.Affected if Data Archiver port is accessible from untrusted or external networks
-
Compare your version against the fixed releasesVerify if your installed version is below 3.5 SIM 17 or 4.0 SIM 12. These are the minimum fixed versions.Affected if Installed version is below 3.5 SIM 17 or is 4.0 before SIM 12
You are affected if GE Proficy Historian is installed with a version prior to 3.5 SIM 17 or 4.0 SIM 12, and the Data Archiver service is network-accessible.
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.
dbcve · scopedUpgrade to GE Proficy Historian version 3.5 SIM 17 or 4.0 SIM 12 or later. If immediate patching is not feasible, isolate the Data Archiver service on a restricted network segment and monitor for anomalous TCP traffic.
Apply 3.5 SIM 17 (for v3.5 and below) or 4.0 SIM 12 (for v4.x)
- Identify the current version of GE Intelligent Platforms Proficy Historian installed in the environment
- Determine the current SIM (Security Improvement Module) version applied to the installation
- For Proficy Historian 3.5 versions: Apply SIM 17 or later to address the buffer overflow vulnerability
- For Proficy Historian 4.0 versions: Apply SIM 12 or later to address the buffer overflow vulnerability
- After applying the SIM, verify the Data Archiver service is running correctly
- Test that normal data collection and archival functions operate as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1918 — 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-2011-1918 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