dbcve.org
UnidataApplication · Rocketsoftware

CVE-2023-28506

HIGH · 8.8 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to after 12.2.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 a stack-based buffer overflow, where a string is copied into a buffer using a memcpy-like function and a user-provided length. This requires a valid login to exploit.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stack-based buffer overflow in Rocket Software UniData and UniVerse where a memcpy-like function copies a string using a user-provided length. Successful exploitation could allow code execution or denial of service, but requires a valid login.

MitigationUpgrade to UniData 8.2.4 build 3003 or later, UniVerse 11.3.5 build 1001 or later, or UniVerse 12.2.1 build 2002 or later. As a compensating control, enforce strong authentication and restrict database access to minimize the attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
UnidataApplication
Affected:<= 8.2.4
UniverseApplication
Affected:<= 11.3.5>= 12.0.0, <= 12.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product
    Determine whether Rocket Software UniData or UniVerse is installed in your environment. Check for product-specific processes, services, or installation directories.
    Affected if Neither UniData nor UniVerse is installed.
  2. Check UniData version
    Run the command to display the UniData version (commonly 'uv -version' or check the installation manifest/file).
    Affected if UniData version is 8.2.4 or lower.
  3. Check UniVerse version
    Run the command to display the UniVerse version (commonly 'uv -version' or check the installation manifest/file).
    Affected if UniVerse version is 11.3.5 or lower, OR between 12.0.0 and 12.2.1 inclusive.
  4. Verify network exposure
    Determine if the UniData/UniVerse service is exposed to network access. Check firewall rules, listen addresses in configuration files, and whether remote connections are permitted.
    Affected if The service is network-accessible and accepts remote connections.
  5. Confirm authentication is required
    Review access controls and confirm that valid login credentials are necessary to interact with the database service.
    Affected if Anonymous or unauthenticated access is permitted to the database service.

You are affected if UniData <= 8.2.4 or UniVerse (any version <= 11.3.5 or between 12.0.0 and 12.2.1) is installed and the service is accessible to network users who can obtain valid credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.1
Interim mitigation

Upgrade to UniData 8.2.4 build 3003 or later, UniVerse 11.3.5 build 1001 or later, or UniVerse 12.2.1 build 2002 or later. As a compensating control, enforce strong authentication and restrict database access to minimize the attack surface.

Recommended fix High confidence

UniData 8.2.4 build 3003+ or UniVerse 11.3.5 build 1001+ / 12.2.1 build 2002+

  1. Identify which Rocket Software product is in use: UniData or UniVerse
  2. For UniData users: Upgrade to version 8.2.4 build 3003 or later
  3. For UniVerse users: Upgrade to version 11.3.5 build 1001 or later, OR version 12.2.1 build 2002 or later
  4. After upgrade, verify the build number matches the fixed release
  5. Test that the application functions normally post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unidata Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28506 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data