# CVE-2013-7136: Weak cryptography in n/a

> Weak WPA-PSK passphrase generation in Cisco EPC 2425 routers allows remote attackers to gain network access via brute-force attacks.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w6xp-hv83-4q24

## What is CVE-2013-7136?

CVE-2013-7136 is a critical vulnerability in n/a, published on 19 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The UPC Ireland Cisco EPC 2425 router (aka Horizon Box) does not have a sufficiently large number of possible WPA-PSK passphrases, which makes it easier for remote attackers to obtain access via a brute-force attack.

Weakness: CWE-310

## Which versions are affected by CVE-2013-7136?

It affects 1 product.


Products: Upc Ireland Cisco Epc2425.

## How do I fix CVE-2013-7136?

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

## Is CVE-2013-7136 being exploited?

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

Public exploit code:

- UPC Ireland Cisco EPC 2425 Router / Horizon Box - WPA-PSK Handshake Information (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7136 and fix it if it is affected.

What it is: CVE-2013-7136 is a critical vulnerability in n/a, published on 19 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-7136 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-2013-7136/ (Markdown: https://insights.sbomify.com/CVE-2013-7136/index.md)
```

## Sources

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

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