# CVE-2013-4218: The InitMethodAndPassword function in InfraStack/OSAgnostic/WiMax/Agents/Supplicant/Source/SupplicantAgent.c in the Intel WiMAX Network Serv


- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-752j-3qvg-4fc9

## What is CVE-2013-4218?

CVE-2013-4218 is a low-severity vulnerability in n/a, published on 25 Aug 2013. 

### Official description

The InitMethodAndPassword function in InfraStack/OSAgnostic/WiMax/Agents/Supplicant/Source/SupplicantAgent.c in the Intel WiMAX Network Service through 1.5.2 for Intel Wireless WiMAX Connection 2400 devices uses the same RSA private key in supplicant_key.pem on all systems, which allows local users to obtain sensitive information via unspecified decryption operations.

Weakness: CWE-310

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

It affects 1 product.


Products: Intel Wimax Network Service.

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

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

## Is CVE-2013-4218 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4219](https://insights.sbomify.com/CVE-2013-4219/): Integer overflow in n/a (high 7.5)
- [CVE-2013-4216](https://insights.sbomify.com/CVE-2013-4216/): Misconfiguration in n/a (low 2.1)
- [CVE-2013-4217](https://insights.sbomify.com/CVE-2013-4217/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4218 is a low-severity vulnerability in n/a, published on 25 Aug 2013. 
Exploitation: There is no known exploitation of CVE-2013-4218 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-4218/ (Markdown: https://insights.sbomify.com/CVE-2013-4218/index.md)
```

## Sources

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

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