dbcve.org
UnidataApplication · Rocketsoftware

CVE-2023-28507

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to after 12.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 memory-exhaustion issue, where a decompression routine will allocate increasing amounts of memory until all system memory is exhausted and the forked process crashes.

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 · high confidence

A memory exhaustion vulnerability exists in the decompression routine of Rocket Software UniData and UniVerse. The routine allocates increasing amounts of memory during decompression without proper bounds, eventually consuming all available system memory and causing the forked process to crash, resulting in denial of service.

MitigationUpgrade UniData to version 8.2.4 build 3003 or later, and UniVerse to version 11.3.5 build 1001, 12.2.1 build 2002, or later. Alternatively, implement input validation and memory limits on decompression operations to prevent unbounded allocation.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Software product
    Run the version command for your installation. For UniData, typically use 'uv -version' or check the Unidata version file. For UniVerse, use 'uv -version' or check the Universe version file. Determine whether UniData or UniVerse (or both) is installed on the system.
    Affected if Either UniData version <= 8.2.4 or UniVerse version <= 11.3.5, or UniVerse version >= 12.0.0 and <= 12.2.1 is installed
  2. Verify UniData version against affected range
    If UniData is installed, check the exact version number and build. Compare against the affected range: any version <= 8.2.4.
    Affected if UniData version is 8.2.4 or lower
  3. Verify UniVerse version against affected range
    If UniVerse is installed, check the exact version number and build. Compare against the affected ranges: any version <= 11.3.5, or any version from 12.0.0 through 12.2.1.
    Affected if UniVerse version is 11.3.5 or lower, OR between 12.0.0 and 12.2.1 inclusive
  4. Check if decompression operations are in use
    Review application logs and configuration to determine if the system performs decompression operations on external data. This vulnerability is triggered when decompressing untrusted or crafted input through the affected routine.
    Affected if Decompression of external or untrusted data is performed using the built-in decompression functionality

The environment is affected if either UniData <= 8.2.4 or UniVerse <= 11.3.5 (or >= 12.0.0 through <= 12.2.1) is installed AND the system uses decompression operations on external data.

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, 12.2.1 build 2002, or later. Alternatively, implement input validation and memory limits on decompression operations to prevent unbounded allocation.

Recommended fix High confidence

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

  1. For UniData: Upgrade to version 8.2.4 build 3003 or later
  2. For UniVerse 11.x: Upgrade to version 11.3.5 build 1001 or later
  3. For UniVerse 12.x: Upgrade to version 12.2.1 build 2002 or later
  4. After upgrade, verify the decompression routines are functioning correctly and monitor memory usage to confirm the fix is effective

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-28507 — 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-28507 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