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

> Remote attackers can hijack sessions on Siemens SCALANCE switches due to weak random number generation in the web server authentication.

- **Severity:** High 8.3 (`AV:N/AC:M/Au:N/C:P/I:P/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7qw8-4g2g-2m86

## What is CVE-2013-5709?

CVE-2013-5709 is a high-severity vulnerability in n/a, published on 17 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The authentication implementation in the web server on Siemens SCALANCE X-200 switches with firmware before 5.0.0 does not use a sufficient source of entropy for generating values of random numbers, which makes it easier for remote attackers to hijack sessions by predicting a value.

Weakness: CWE-189

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

It affects 9 products.


Products: Siemens Scalance X-200, Siemens Scalance X-200 Series Firmware, Siemens Scalance X-200rna, Siemens Scalance X200-4p Irt, Siemens Scalance X201-3p Irt, Siemens Scalance X202-2irt, Siemens Scalance X202-2p Irt, Siemens Scalance X204irt, Siemens Scalance Xf-200.

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

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

## Is CVE-2013-5709 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-5944](https://insights.sbomify.com/CVE-2013-5944/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5709 is a high-severity vulnerability in n/a, published on 17 Sep 2013. 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-2013-5709 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-5709/ (Markdown: https://insights.sbomify.com/CVE-2013-5709/index.md)
```

## Sources

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

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