CVE-2023-28503 — Authentication bypass in UniRPC's udadmin service

Rocket Software UniData versions prior to 8.2.4 build 3003 and UniVerse versions prior to 11.3.5 build 1001 or 12.2.1 build 2002 suffer from an authentication bypass vulnerability, where a special username with a deterministic password can be leveraged to bypass authentication checks and execute OS commands as the root user.

Published Mar 29, 2023Updated Feb 18, 2025Sources: cvelistV5, rapid7

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

62%

chance of exploitation in 30 days

Affects

rocket software

2 products listed

CVSS base

9.8

CRITICAL

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

PoC

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

rocket software

Products (2)

unidatauniverse

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	CRITICAL	—	—	cvelistV5

Weakness & attack patterns

CWE-798

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1552.001Unsecured Credentials: Credentials in files
T1078.001Valid Accounts: Default Accounts

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

metasploit

References

2 on the record

Elsewhere on this site

rocket softwareevery CVE for this vendor
CWE-798other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.