# CVE-2017-1473: Weak cryptography in Security Access Manager

> Weak cryptographic algorithms in IBM Security Access Manager allow attackers to decrypt highly sensitive information.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2cj7-cj42-3g7v

## What is CVE-2017-1473?

CVE-2017-1473 is a high-severity vulnerability in IBM Security Access Manager, published on 23 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM 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.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2017-1473?

It affects 3 products.


Products: Ibm Security Access Manager Firmware, Ibm Security Access Manager for Mobile, Ibm Security Access Manager for Web Firmware.

## How do I fix CVE-2017-1473?

No fix has been published for CVE-2017-1473 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-1473 being exploited?

There is no known exploitation of CVE-2017-1473 in the wild and no public exploit code.

## Other vulnerabilities in IBM Security Access Manager

- [CVE-2017-1534](https://insights.sbomify.com/CVE-2017-1534/): Open redirect in Security Access Manager (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1473 and fix it if it is affected.

What it is: CVE-2017-1473 is a high-severity vulnerability in IBM Security Access Manager, published on 23 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1473 in the wild and no public exploit code.

Affected product: IBM Security Access Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-1473/ (Markdown: https://insights.sbomify.com/CVE-2017-1473/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1473
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1473
- OSV: https://osv.dev/vulnerability/CVE-2017-1473

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-1473/
Summaries are generated and may contain mistakes; the official description above is the record.