CVE-2016-9353
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 Advantech SUISAccess Server Version 3.0 and prior. The admin password is stored in the system and is encrypted with a static key hard-coded in the program. Attackers could reverse the admin account password for use.
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 confidenceThe Advantech SUISAccess Server stores admin passwords using encryption with a hard-coded static key embedded in the application code. Attackers who can access the encrypted password storage can reverse-engineer the hard-coded key to decrypt and recover the admin password.
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.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Susiaccess versionLocate the Susiaccess installation directory and check the version information (typically in an About section, version file, or installer metadata). Compare the installed version to the affected range (<= 3.0).Affected if The installed version is 3.0 or lower.
-
Locate application binaries or scriptsFind the main Susiaccess installation folder (commonly in Program Files or a dedicated application directory). Identify executable files, DLLs, or scripts that handle encryption or password operations.Affected if Susiaccess binaries are present on the system.
-
Search for hard-coded encryption keysOpen the main application binaries or scripts in a text editor or hex viewer. Search for static string patterns related to encryption such as 'key', 'encrypt', 'cipher', 'password', or similar keywords. Look for hard-coded string literals used in encryption routines.Affected if A static, hard-coded encryption key is found embedded in the application code.
-
Examine password storage mechanismLocate the password storage file or database (typically in configuration files or a data directory within the Suisaccess installation). Verify if passwords are stored in encrypted form.Affected if Admin passwords are stored in encrypted format within the application data.
-
Confirm key is static and embeddedReview the encryption implementation to confirm the same key is used across all installations (not environment-specific). Check if the key value appears directly in the binary as a constant string rather than being retrieved from configuration or external source.Affected if The same encryption key value is used universally and embedded directly in the application code.
A system is affected if Susiaccess version 3.0 or lower is installed AND hard-coded static encryption keys are found embedded in the application binaries used for password encryption.
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 the hard-coded encryption key with proper key management (e.g., environment-specific keys, external key vault, or derived keys) and re-encrypt existing stored passwords using the new secure key management approach.
- Consultation3.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9353 — 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-9353 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