CVE-2011-1919
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 · uneditedMultiple stack-based buffer overflows in GE Intelligent Platforms Proficy Applications before 4.4.1 SIM 101 and 5.x before 5.0 SIM 43 allow remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via crafted TCP message traffic to (1) PRProficyMgr.exe in Proficy Server Manager, (2) PRGateway.exe in Proficy Server Gateway, (3) PRRDS.exe in Proficy Remote Data Service, or (4) PRLicenseMgr.exe in Proficy Server License Manager.
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 overflows in multiple GE Intelligent Platforms Proficy applications (Proficy Server Manager, Gateway, Remote Data Service, and License Manager) allow remote attackers to send crafted TCP messages that can cause denial of service or potentially execute arbitrary code. The vulnerabilities affect versions before 4.4.1 SIM 101 and 5.x before 5.0 SIM 43.
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.4.1= 4.0= 5.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 installed GE Proficy applicationsCheck Windows Programs and Features or registry for Proficy Historian, Server Manager, Gateway, Remote Data Service, or License Manager installationsAffected if Any Proficy application from the affected product line is installed
-
Determine Proficy Historian versionLocate the Proficy Historian installation directory and check version info in the application properties or an About dialog, or query the installed software version via Windows registry under HKLM\SOFTWARE\GE Intelligence Platform\Proficy HistorianAffected if Version is 4.4.1 or earlier, or version 5.0 or earlier before SIM 43
-
Check Proficy component versionsFor Server Manager, Gateway, Remote Data Service, or License Manager, locate their executables and check file properties for version information, or query the specific component version through its service propertiesAffected if Any component version is before 4.4.1 SIM 101 or 5.x before 5.0 SIM 43
-
Identify listening TCP servicesUse netstat or TCPView to identify processes listening on common Proficy ports (typically ports 80, 443, 5000-5100 range for these services) and verify which Proficy services are bound to network interfacesAffected if Proficy TCP services are bound to accessible network interfaces rather than localhost only
-
Verify network exposureReview firewall rules and network configuration to determine if Proficy management or data ports are exposed beyond the local network or to untrusted systemsAffected if Proficy services are accessible from network segments containing untrusted systems
A system is affected if it runs any GE Proficy Historian or related component version before 4.4.1 SIM 101 or 5.x before 5.0 SIM 43 with TCP services exposed to the 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.
dbcve · scopedUpgrade to GE Proficy Applications 4.4.1 SIM 101 or 5.0 SIM 43 or later. Implement network segmentation to restrict access to these services and monitor for anomalous TCP traffic.
4.4.1 SIM 101+ or 5.0 SIM 43+ (contact GE for specific patch packages)
- Identify the exact version of GE Intelligent Platforms Proficy Applications currently installed (Proficy Server Manager, Proficy Server Gateway, Proficy Remote Data Service, and Proficy Server License Manager)
- For Proficy Applications version 4.x: Upgrade to version 4.4.1 with SIM (System Integration Module) 101 or later
- For Proficy Applications version 5.x: Upgrade to version 5.0 with SIM 43 or later
- Alternatively, contact GE Intelligent Platforms support to obtain the specific security patches for this vulnerability (SIM 101 for 4.x branch and SIM 43 for 5.x branch)
- Verify the patch was successfully applied by checking the version information of the affected executables (PRProficyMgr.exe, PRGateway.exe, PRRDS.exe, PRLicenseMgr.exe)
- Test the application functionality to ensure the patch does not break existing operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1919 — 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-1919 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