# CVE-2023-41723: Information disclosure in One

> A read-only user can view dashboard schedules in Veeam ONE, exposing configuration details to unauthorized personnel.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2023
- **Updated:** 29 Oct 2024
- **Also known as:** GHSA-2jf9-9rxc-j63c

## What is CVE-2023-41723?

CVE-2023-41723 is a medium-severity vulnerability in Veeam One, published on 7 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in Veeam ONE allows a user with the Veeam ONE Read-Only User role to view the Dashboard Schedule. Note: The criticality of this vulnerability is reduced because the user with the Read-Only role is only able to view the schedule and cannot make changes.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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

It affects 1 product.


Products: Veeam One.

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

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

## Is CVE-2023-41723 being exploited?

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

## Other vulnerabilities in Veeam One

- [CVE-2023-38547](https://insights.sbomify.com/CVE-2023-38547/): Information disclosure in One (critical 9.9)
- [CVE-2023-38548](https://insights.sbomify.com/CVE-2023-38548/): Information disclosure in One (critical 9.8)
- [CVE-2020-10914](https://insights.sbomify.com/CVE-2020-10914/): Deserialization in One Agent (critical 9.8)
- [CVE-2020-10915](https://insights.sbomify.com/CVE-2020-10915/): Deserialization in One Agent (critical 9.8)
- [CVE-2024-42024](https://insights.sbomify.com/CVE-2024-42024/): Privilege escalation in One (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41723 is a medium-severity vulnerability in Veeam One, published on 7 Nov 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-41723 in the wild and no public exploit code.

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

## Sources

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

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