# CVE-2023-31185: ROZCOM server framework

> Misconfiguration in ROZCOM server framework may allow attackers to disclose sensitive information via unspecified requests.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-6r86-g6rm-3wq5

## What is CVE-2023-31185?

CVE-2023-31185 is a high-severity vulnerability in ROZCOM server framework, published on 30 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ROZCOM server framework - Misconfiguration may allow information disclosure via an unspecified request.

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

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

It affects 1 product.


Products: Rozcom Rozcom Client.

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

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

## Is CVE-2023-31185 being exploited?

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

## Other vulnerabilities in ROZCOM server framework

- [CVE-2023-31184](https://insights.sbomify.com/CVE-2023-31184/): ROZCOM client (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31185 is a high-severity vulnerability in ROZCOM server framework, published on 30 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31185 in the wild and no public exploit code.

Affected product: ROZCOM server framework. 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-31185/ (Markdown: https://insights.sbomify.com/CVE-2023-31185/index.md)
```

## Sources

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

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