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

> Unauthenticated access to job UUIDs and session IDs in ZStack Cloud enables privilege escalation, requiring immediate upgrade.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 30 Nov 2023
- **Updated:** 2 Aug 2024

## What is CVE-2023-46326?

CVE-2023-46326 is a high-severity vulnerability in n/a, published on 30 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZStack Cloud version 3.10.38 and before allows unauthenticated API access to the list of active job UUIDs and the session ID for each of these. This leads to privilege escalation.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

It affects 1 product.


Products: Zstack Zstack.

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

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

## Is CVE-2023-46326 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-32836](https://insights.sbomify.com/CVE-2021-32836/): Pre-auth unsafe deserialization in ZStack (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46326 is a high-severity vulnerability in n/a, published on 30 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-46326 in the wild and no public exploit code.

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-46326/ (Markdown: https://insights.sbomify.com/CVE-2023-46326/index.md)
```

## Sources

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

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