Studio
by Omnis
CVEs (3)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2023-38334 | Med | 0.42 | 6.5 | 0.01 | Jul 20, 2023 | Omnis Studio 10.22.00 has incorrect access control. It advertises an irreversible feature for locking classes within Omnis libraries: it should be no longer possible to delete, view, change, copy, rename, duplicate, or print a locked class. Due to implementation issues, locked… | ||
| CVE-2023-38335 | Med | 0.35 | 5.3 | 0.01 | Jul 20, 2023 | 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… | ||
| CVE-2000-0449 | 0.03 | — | 0.02 | May 1, 2000 | Omnis Studio 2.4 uses weak encryption (trivial encoding) for encrypting database fields. |
- risk 0.42cvss 6.5epss 0.01
Omnis Studio 10.22.00 has incorrect access control. It advertises an irreversible feature for locking classes within Omnis libraries: it should be no longer possible to delete, view, change, copy, rename, duplicate, or print a locked class. Due to implementation issues, locked…
- risk 0.35cvss 5.3epss 0.01
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…
- CVE-2000-0449May 1, 2000risk 0.03cvss —epss 0.02
Omnis Studio 2.4 uses weak encryption (trivial encoding) for encrypting database fields.