# CVE-2023-38335: Missing authorization in n/a

> Attackers can bypass access controls to open libraries marked as always private in Omnis Studio, violating intended security restrictions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 20 Jul 2023
- **Updated:** 24 Oct 2024
- **Also known as:** GHSA-4x48-qpw5-qpgr

## What is CVE-2023-38335?

CVE-2023-38335 is a medium-severity missing authorization vulnerability in n/a, published on 20 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Omnis Studio 10.22.00 has incorrect access control. It advertises a feature for making Omnis libraries "always private" - this is supposed to be an irreversible operation. However, due to implementation issues, "always private" Omnis libraries can be opened by the Omnis Studio browser by bypassing specific checks. This violates the expected behavior of an "irreversible operation".

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Omnis Studio.

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

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

## Is CVE-2023-38335 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0449](https://insights.sbomify.com/CVE-2000-0449/): Weak cryptography in n/a (critical 10.0)
- [CVE-2023-38334](https://insights.sbomify.com/CVE-2023-38334/): Security feature bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38335 is a medium-severity missing authorization vulnerability in n/a, published on 20 Jul 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-38335 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-38335/ (Markdown: https://insights.sbomify.com/CVE-2023-38335/index.md)
```

## Sources

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

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