dbcve.org
UnidataApplication · Rocketsoftware

CVE-2023-28508

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 heap-based overflow vulnerability, where certain input can corrupt the heap and crash the forked process.

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

Rocket Software UniData and UniVerse database products contain a heap-based buffer overflow vulnerability in versions prior to the specified builds. The vulnerability allows specially crafted input to corrupt heap memory, potentially leading to process crash or potentially remote code execution in the forked process context.

MitigationUpgrade UniData to version 8.2.4 build 3003 or later, and UniVerse to version 11.3.5 build 1001 or 12.2.1 build 2002 or later to remediate this vulnerability.

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 Rocket database product
    Check for UniData or UniVerse installation directories, or run product-specific version commands such as 'uv -v' for UniVerse or check registry/service information for UniData
    Affected if Neither UniData nor UniVerse is installed (not affected)
  2. Determine UniData version and build
    Use UniData version query commands or check installation metadata for the exact version number and build (for example, 8.2.4 build XXXX)
    Affected if UniData version is 8.2.4 or lower, or version is unknown and build is below 3003
  3. Determine UniVerse version and build
    Use UniVerse version query commands (such as 'uv -v') or check installation metadata for the exact version number and build (for example, 11.3.5 build XXXX or 12.2.1 build XXXX)
    Affected if UniVerse version is 11.3.5 or lower, or is 12.0.0 through 12.2.1 with build below 1001 (for 11.3.5) or below 2002 (for 12.2.1)
  4. Verify database services are running
    Check if UniData or UniVerse database services/daemons are active, as the vulnerability affects the database server process handling input
    Affected if Database services are not running (not affected, as the vulnerable code path is not active)

The environment is affected if UniData version 8.2.4 or lower (build below 3003) or UniVerse version 11.3.5 or lower (build below 1001) or version 12.0.0-12.2.1 (build below 2002) is installed and the database services are active.

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 UniData to version 8.2.4 build 3003 or later, and UniVerse to version 11.3.5 build 1001 or 12.2.1 build 2002 or later to remediate this vulnerability.

Recommended fix Moderate confidence

UniData 8.2.4 build 3003+ | UniVerse 11.3.5 build 1001+ | UniVerse 12.2.1 build 2002+

  1. Upgrade UniData to version 8.2.4 build 3003 or later
  2. If running UniVerse 11.x, upgrade to version 11.3.5 build 1001 or later
  3. If running UniVerse 12.x, upgrade to version 12.2.1 build 2002 or later
  4. After upgrading, verify the heap-based overflow vulnerability is remediated by testing affected functionality

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

Fix this in Unidata Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28508 — 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-28508 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