# CVE-2019-9555: Weak cryptography in n/a

> Sagemcom F@st 5260 routers use weak WPA PSKs with insufficient entropy, allowing attackers to easily guess the password and bypass network security.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 5 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rf22-j4q7-f2f8

## What is CVE-2019-9555?

CVE-2019-9555 is a medium-severity vulnerability in n/a, published on 5 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sagemcom F@st 5260 routers using firmware version 0.4.39, in WPA mode, default to using a PSK that is generated from a 2-part wordlist of known values and a nonce with insufficient entropy. The number of possible PSKs is about 1.78 billion, which is too small.

Weakness: CWE-331 (Insufficient Entropy)

## Which versions are affected by CVE-2019-9555?

It affects 1 product.


Products: Sagemcom F\@st 5260 Firmware.

## How do I fix CVE-2019-9555?

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

## Is CVE-2019-9555 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9555 and fix it if it is affected.

What it is: CVE-2019-9555 is a medium-severity vulnerability in n/a, published on 5 Mar 2019. 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-2019-9555 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-2019-9555/ (Markdown: https://insights.sbomify.com/CVE-2019-9555/index.md)
```

## Sources

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

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