# CVE-2023-5223: HimitZH HOJ Topic sandbox

> Remote attackers can bypass the topic sandbox in HimitZH HOJ to execute arbitrary code or escalate privileges.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2023
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-j2hc-j6gw-fqgh

## What is CVE-2023-5223?

CVE-2023-5223 is a medium-severity vulnerability in HimitZH HOJ, published on 27 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in HimitZH HOJ up to 4.6-9a65e3f. This issue affects some unknown processing of the component Topic Handler. The manipulation leads to sandbox issue. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-240365 was assigned to this vulnerability.

Weakness: CWE-265

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

It affects 1 product.


Products: Hdoi Hcode Online Judge.

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

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

## Is CVE-2023-5223 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5223 is a medium-severity vulnerability in HimitZH HOJ, published on 27 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5223 in the wild and no public exploit code.

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

## Sources

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

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