CVE-2017-1473
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 · uneditedIBM Security Access Manager Appliance 8.0.0 through 8.0.1.6 and 9.0.0 through 9.0.3.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 128605.
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 confidenceIBM Security Access Manager Appliance versions 8.0.0 through 8.0.1.6 and 9.0.0 through 9.0.3.1 implements weaker than expected cryptographic algorithms, potentially allowing attackers to decrypt sensitive information transmitted or stored by the appliance.
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= 8.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.4= 8.0.0.5= 8.0.1= 8.0.1.2= 8.0.1.3= 8.0.1.4= 8.0.1.5= 8.0.1.6= 8.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.4= 8.0.0.5= 8.0.1= 8.0.1.2= 8.0.1.3= 8.0.1.4= 8.0.1.5= 8.0.1.6= 9.0.0= 9.0.0.1= 9.0.1.0= 9.0.2.0= 9.0.2.1= 9.0.3= 9.0.3.1CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Check installed IBM Security Access Manager Appliance versionAccess the appliance admin console or use the command line interface (typically via SSH) and run the command to display the firmware version, often found in system information or version detailsAffected if The installed version is 8.0.0 through 8.0.1.6 or 9.0.0 through 9.0.3.1
-
Identify the specific product componentDetermine whether the appliance is running 'IBM Security Access Manager For Web', 'IBM Security Access Manager For Mobile', or the general 'IBM Security Access Manager' firmware componentAffected if The product component matches any of the affected variants listed in the CVE (For Web, For Mobile, or general Firmware) and the version falls within the affected ranges
-
Verify cryptographic algorithm configurationAccess the appliance security or cryptographic settings panel in the admin console or check the configuration files for the defined cipher suites and encryption algorithms in useAffected if Weak or deprecated cryptographic algorithms (such as weak ciphers or hashing algorithms) are enabled or configured on the appliance
-
Check SSL/TLS protocol settingsReview the SSL/TLS protocol version settings to determine if older protocol versions (SSLv3, TLS 1.0, TLS 1.1) are enabledAffected if Older protocol versions that support weak cryptographic algorithms are permitted or enabled
A user is affected if the installed IBM Security Access Manager Appliance version falls within 8.0.0-8.0.1.6 or 9.0.0-9.0.3.1 and weak cryptographic algorithms are in use.
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 a patched version of IBM Security Access Manager Appliance that addresses the weak cryptographic algorithms, or review and reconfigure cryptographic settings to use stronger algorithms if supported.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1473 — 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-2017-1473 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