# CVE-2023-2524: Control iD RHiD direct request

> Attackers can perform unauthorized direct requests to the RHiD web interface, potentially accessing or modifying data without authentication.

- **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:** 4 May 2023
- **Updated:** 29 Jan 2025
- **Also known as:** GHSA-5qvc-chcx-p36x

## What is CVE-2023-2524?

CVE-2023-2524 is a medium-severity missing authorization vulnerability in Control iD RHiD, published on 4 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in Control iD RHiD 23.3.19.0. This affects an unknown part of the file /v2/#/. The manipulation leads to direct request. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-228015. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-425 (Direct Request)

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

It affects 1 product.


Products: Controlid Rhid.

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

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

## Is CVE-2023-2524 being exploited?

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

## Other vulnerabilities in Control iD RHiD

- [CVE-2023-2421](https://insights.sbomify.com/CVE-2023-2421/): Control iD RHiD department cross site scripting (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-2524 is a medium-severity missing authorization vulnerability in Control iD RHiD, published on 4 May 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-2524 in the wild and no public exploit code.

Affected product: Control iD RHiD. 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-2524/ (Markdown: https://insights.sbomify.com/CVE-2023-2524/index.md)
```

## Sources

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

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