# CVE-2024-3780: Information exposure vulnerability on Technicolor CGA2121

> A local attacker can obtain sensitive Wi-Fi SSID and password information from the Technicolor CGA2121 device.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Apr 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-fvhp-g7rg-4vvm

## What is CVE-2024-3780?

CVE-2024-3780 is a high-severity vulnerability in Technicolor CGA2121, published on 15 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability of Information Exposure has been found on Technicolor CGA2121 affecting the version 1.01, this vulnerability allows a local attacker to obtain sensitive information stored on the device such as wifi network's SSID and their respective passwords.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2024-3780 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3780 is a high-severity vulnerability in Technicolor CGA2121, published on 15 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-3780 in the wild and no public exploit code.

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

## Sources

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

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