# CVE-2023-45912: Information disclosure in n/a

> Unauthenticated attackers can read files and directory listings from the underlying operating system due to missing session validation in WIPOTEC ComScale.

- **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:** 18 Oct 2023
- **Updated:** 9 Jan 2025
- **Also known as:** GHSA-p7jx-m4x8-cghf

## What is CVE-2023-45912?

CVE-2023-45912 is a high-severity vulnerability in n/a, published on 18 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WIPOTEC GmbH ComScale v4.3.29.21344 and v4.4.12.723 fails to validate user sessions, allowing unauthenticated attackers to read files from the underlying operating system and obtain directory listings.

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

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

It affects 1 product.


Products: Wipotec Comscale.

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

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

## Is CVE-2023-45912 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45912 exists.

## Other vulnerabilities in n/a

- [CVE-2023-45911](https://insights.sbomify.com/CVE-2023-45911/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45912 is a high-severity vulnerability in n/a, published on 18 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45912 exists.

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

## Sources

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

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