# CVE-2024-2495: Cryptographic key in plain text vulnerability in FriendlyElec's FriendlyWrt

> Attackers can extract plaintext cryptographic keys from FriendlyWrt firmware to compromise encrypted data confidentiality and integrity.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-jjf7-vp9p-j843

## What is CVE-2024-2495?

CVE-2024-2495 is a medium-severity vulnerability in FriendlyElec FriendlyWrt, published on 15 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cryptographic key vulnerability encoded in the FriendlyWrt firmware affecting version 2022-11-16.51b3d35. This vulnerability could allow an attacker to compromise the confidentiality and integrity of encrypted data.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2024-2495?

It affects 1 product.


Products: Friendlyelec Friendlywrt.

## How do I fix CVE-2024-2495?

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

## Is CVE-2024-2495 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2495 and fix it if it is affected.

What it is: CVE-2024-2495 is a medium-severity vulnerability in FriendlyElec FriendlyWrt, published on 15 Mar 2024. 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-2024-2495 in the wild and no public exploit code.

Affected product: FriendlyElec FriendlyWrt. 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-2024-2495/ (Markdown: https://insights.sbomify.com/CVE-2024-2495/index.md)
```

## Sources

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

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