# CVE-2013-4217: Information disclosure in n/a

> Local attackers can read cleartext passwords from log files in the Intel WiMAX Network Service, exposing sensitive credentials.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 25 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pg5r-9882-vgp5

## What is CVE-2013-4217?

CVE-2013-4217 is a low-severity vulnerability in n/a, published on 25 Aug 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The OSAL_Crypt_SetEncryptedPassword function in InfraStack/OSDependent/Linux/OSAL/Services/wimax_osal_crypt_services.c in the OSAL crypt module in the Intel WiMAX Network Service through 1.5.2 for Intel Wireless WiMAX Connection 2400 devices logs a cleartext password during certain attempts to set a password, which allows local users to obtain sensitive information by reading a log file.

Weakness: CWE-310

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

It affects 1 product.


Products: Intel Wimax Network Service.

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

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

## Is CVE-2013-4217 being exploited?

There is no known exploitation of CVE-2013-4217 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-4218](https://insights.sbomify.com/CVE-2013-4218/): The InitMethodAndPassword function in InfraStack/OSAgnostic/WiMax/Agents/Supplicant/Source/SupplicantAgent.c in the Intel WiMAX Network Serv (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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