CVE-2016-9360
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 · uneditedAn issue was discovered in General Electric (GE) Proficy HMI/SCADA iFIX Version 5.8 SIM 13 and prior versions, Proficy HMI/SCADA CIMPLICITY Version 9.0 and prior versions, and Proficy Historian Version 6.0 and prior versions. An attacker may be able to retrieve user passwords if he or she has access to an authenticated 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 confidenceThis vulnerability allows authenticated users to retrieve user passwords in GE Proficy HMI/SCADA iFIX, CIMPLICITY, and Historian software. The issue stems from improper handling or storage of user credentials, enabling an authenticated attacker with session access to obtain plaintext or reversible passwords for other users.
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<= 9.0<= 6.0<= 5.8CVSS 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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L
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 productsReview installed software on the system for GE Cimplicity, GE Historian, or GE Ifix applications. Check Windows Programs and Features or the application installation directories.Affected if Any of these three products (Cimplicity, Historian, or Ifix) are installed on the system.
-
Determine the installed version of GE CimplicityOpen GE Cimplicity and navigate to Help > About, or check the program version through Windows Programs and Features. Compare the version number against the affected range.Affected if The installed version is 9.0 or earlier.
-
Determine the installed version of GE HistorianOpen GE Historian and check the version through Help > About, or check via Windows Programs and Features. Compare against the affected range.Affected if The installed version is 6.0 or earlier.
-
Determine the installed version of GE IfixOpen GE Ifix and navigate to Help > About, or check via Windows Programs and Features. Compare against the affected range.Affected if The installed version is 5.8 or earlier.
-
Verify if user authentication is configuredCheck the user management or security configuration within the GE product interface to confirm user accounts exist and authentication is enabled.Affected if User authentication is enabled with multiple user accounts configured, allowing authenticated session access.
A user is affected if any GE Cimplicity (<=9.0), GE Historian (<=6.0), or GE Ifix (<=5.8) is installed and user authentication is configured, enabling an authenticated attacker to retrieve other user passwords.
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 dataUpgrade to patched versions of the affected Proficy products and review user access controls. Implement network segmentation to limit authenticated session exposure and apply the principle of least privilege to reduce the attack surface.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9360 — 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-2016-9360 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