# CVE-2017-17427: Weak cryptography in n/a

> Attackers can decrypt RSA-encrypted traffic and perform private key operations on Radware Alteon devices via a Bleichenbacher attack.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/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:** 13 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3ph6-jhvp-76gj

## What is CVE-2017-17427?

CVE-2017-17427 is a medium-severity vulnerability in n/a, published on 13 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Radware Alteon devices with a firmware version between 31.0.0.0-31.0.3.0 are vulnerable to an adaptive-chosen ciphertext attack ("Bleichenbacher attack"). This allows an attacker to decrypt observed traffic that has been encrypted with the RSA cipher and to perform other private key operations.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Radware Alteon Firmware.

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

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

## Is CVE-2017-17427 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-17427 exists.

Public exploit code:

- Scanner for Bleichenbacher Oracle in RSA PKCS #1 v1.5 (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17427 is a medium-severity vulnerability in n/a, published on 13 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-17427 exists.

Affected product: n/a. 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-17427/ (Markdown: https://insights.sbomify.com/CVE-2017-17427/index.md)
```

## Sources

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

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