# CVE-2015-0558: Weak cryptography in n/a

> The router uses a weak algorithm to generate WPA keys, allowing attackers to decrypt wireless traffic and bypass network security.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 14 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xj8f-gc6p-qfjp

## What is CVE-2015-0558?

CVE-2015-0558 is a medium-severity vulnerability in n/a, published on 14 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ADB (formerly Pirelli Broadband Solutions) P.DGA4001N router with firmware PDG_TEF_SP_4.06L.6, and possibly other routers, uses "1236790" and the MAC address to generate the WPA key.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2015-0558?

It affects 1 product.


Products: Adbglobal P.dga4001n Firmware.

## How do I fix CVE-2015-0558?

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

## Is CVE-2015-0558 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0558 and fix it if it is affected.

What it is: CVE-2015-0558 is a medium-severity vulnerability in n/a, published on 14 Jan 2020. 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-2015-0558 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-2015-0558/ (Markdown: https://insights.sbomify.com/CVE-2015-0558/index.md)
```

## Sources

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

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