Private library disclosure via browser check bypass
Published Jul 20, 2023 · Updated Oct 24, 2024
Access control bypass in the library browser in Omnis Studio 10.22.00 allows local users to read always-private libraries. The public proof of concept patches the running Studio process to bypass the browser check that prevents private libraries from loading. Access requires control of the Studio process and a protected library; exploitation exposes locked classes for analysis.
Summary
What happened
Access control bypass in the library browser in Omnis Studio 10.22.00 allows local users to read always-private libraries. The public proof of concept patches the running Studio process to bypass the browser check that prevents private libraries from loading. Access requires control of the Studio process and a protected library; exploitation exposes locked classes for analysis.
The record
- CVE
- CVE-2023-38335
- Published
- Jul 20, 2023
- Updated
- Oct 24, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-440, CWE-276, T1005
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 20, 2023CVE publishedPublication date reported by the CVE source.
- Oct 24, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Reversing the Irreversible - Part Iproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo