# CVE-2023-5579: yhz66 Sandbox User Data information disclosure

> An attacker with permissions can access user data via the User Data Handler, leading to information disclosure in the Sandbox web application.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 14 Oct 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-3wvv-hwf3-3qv8

## What is CVE-2023-5579?

CVE-2023-5579 is a low-severity vulnerability in yhz66 Sandbox, published on 14 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in yhz66 Sandbox 6.1.0. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /im/user/ of the component User Data Handler. The manipulation leads to information disclosure. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-242144.

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

## Which versions are affected by CVE-2023-5579?

It affects 1 product.


Products: Yzh66 Sandbox.

## How do I fix CVE-2023-5579?

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

## Is CVE-2023-5579 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5579 and fix it if it is affected.

What it is: CVE-2023-5579 is a low-severity vulnerability in yhz66 Sandbox, published on 14 Oct 2023. 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-2023-5579 in the wild and no public exploit code.

Affected product: yhz66 Sandbox. 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-2023-5579/ (Markdown: https://insights.sbomify.com/CVE-2023-5579/index.md)
```

## Sources

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

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