# CVE-2024-28963: Information disclosure in Wyse Proprietary OS (Modern ThinOS)

> An unauthenticated local user can read sensitive proxy settings on Dell ThinOS devices, exposing configuration details.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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:** 24 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-pcc4-6p5c-3297

## What is CVE-2024-28963?

CVE-2024-28963 is a medium-severity vulnerability in Dell Wyse Proprietary OS (Modern ThinOS), published on 24 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Telemetry Dashboard v1.0.0.7 for Dell ThinOS 2402 contains a sensitive information disclosure vulnerability. An unauthenticated user with local access to the device could exploit this vulnerability to read sensitive proxy settings information.

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

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

It affects 1 product.


Products: Dell Telemetry Dashboard.

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

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

## Is CVE-2024-28963 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28963 is a medium-severity vulnerability in Dell Wyse Proprietary OS (Modern ThinOS), published on 24 Apr 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-28963 in the wild and no public exploit code.

Affected product: Dell Wyse Proprietary OS (Modern ThinOS). 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-28963/ (Markdown: https://insights.sbomify.com/CVE-2024-28963/index.md)
```

## Sources

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

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