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

> Attackers can predict session tokens to gain administrative access to Asus routers running asuswrt firmware.

- **Severity:** High 8.3 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xjwp-6c2p-p5mx

## What is CVE-2017-15654?

CVE-2017-15654 is a high-severity vulnerability in n/a, published on 31 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Highly predictable session tokens in the HTTPd server in all current versions (<= 3.0.0.4.380.7743) of Asus asuswrt allow gaining administrative router access.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Asus Asuswrt.

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

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

## Is CVE-2017-15654 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-20334](https://insights.sbomify.com/CVE-2018-20334/): Command injection in n/a (critical 9.8)
- [CVE-2018-5999](https://insights.sbomify.com/CVE-2018-5999/): Auth bypass in n/a (critical 9.8)
- [CVE-2018-6000](https://insights.sbomify.com/CVE-2018-6000/): Missing authorization in n/a (critical 9.8)
- [CVE-2017-15655](https://insights.sbomify.com/CVE-2017-15655/): Memory corruption in n/a (critical 9.6)
- [CVE-2017-15653](https://insights.sbomify.com/CVE-2017-15653/): Auth bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15654 is a high-severity vulnerability in n/a, published on 31 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-15654 in the wild and no public exploit code.

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-15654/ (Markdown: https://insights.sbomify.com/CVE-2017-15654/index.md)
```

## Sources

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

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