CVE-2025-4993
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 · uneditedUntrusted Pointer Dereference vulnerability in RTI Connext Professional (Core Libraries) allows Pointer Manipulation.This issue affects Connext Professional: from 7.4.0 before 7.6.0, from 7.0.0 before 7.3.0.10, from 6.1.0 before 6.1.2.27, from 6.0.0 before 6.0.1.43, from 5.3.0 before 5.3.*, from 4.4a before 5.2.*.
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 confidenceAn untrusted pointer dereference vulnerability in RTI Connext Professional Core Libraries allows attackers to manipulate pointers, potentially enabling arbitrary code execution or denial of service. This memory corruption issue affects multiple version branches of the middleware product.
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>= 4.4a, < 6.1.2.27>= 7.0.0, < 7.3.0.10>= 7.4.0, < 7.6.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate RTI Connext installationSearch for the rti_connext directory in common installation paths such as /opt/rti_connext (Linux) or C:\Program Files\rti_connext (Windows). Check for environment variable RTI_DIR or NDDSHOME if defined.Affected if RTI Connext is not installed on the system.
-
Identify installed versionOpen the installation directory and locate a version file or check the directory name. Common locations include VERSION.txt in the root install folder, or the library filenames (such as libnddscore.so or nddscore.dll) which may contain version strings. The version is also visible in the folder structure for most releases (e.g., rti_connext-6.1.2).Affected if Unable to determine the installed version from the installation.
-
Compare version against affected rangesCheck if the installed version falls into any of these vulnerable ranges: 4.4a up to 6.1.2.27 (exclusive), 7.0.0 up to 7.3.0.10 (exclusive), or 7.4.0 up to 7.6.0 (exclusive). Versions below 4.4a, 6.1.2.27 and above, 7.3.0.10 and above, or 7.6.0 and above are not affected.Affected if The installed version is within any of the three vulnerable ranges listed.
-
Verify the Core Libraries are in useConfirm that applications or services using the RTI Connext DDS middleware are running. Check for processes linked to libnddscore, libnddsc, or nddscore.dll/nddsc.dll. Review any DDS participant configurations (XML or code) that initialize Connext domains.Affected if The Core Libraries are actively loaded and used by running applications.
The system is affected if RTI Connext Professional is installed with a version matching any of the vulnerable ranges (4.4a to 6.1.2.26, 7.0.0 to 7.3.0.9, or 7.4.0 to 7.5.x) and the Core Libraries are in use.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.1.2.277.3.0.107.6.0
Upgrade RTI Connext Professional to version 7.6.0 or later, or to the appropriate patched version for your branch (7.3.0.10+, 6.1.2.27+, 6.0.1.43+, or 5.3.x/5.2.x latest). If immediate patching is not possible, restrict network access to Connext endpoints and implement input validation to reduce attack surface.
7.6.0 (for 7.4+ branches); 7.3.0.10 (for 7.0-7.3 branches); 6.1.2.27 (for 6.1 branches); 6.0.1.43 (for 6.0 branches); latest 5.3.x; latest 5.2.x
- 1. Identify the currently installed RTI Connext Professional version using 'rtiddsgen -version' or checking the installation directory
- 2. Determine which version branch you are on (4.x, 5.x, 6.x, or 7.x)
- 3. For version 7.4.0 and above: Upgrade to version 7.6.0 or later
- 4. For version 7.0.0 to 7.3.x: Upgrade to version 7.3.0.10 or later
- 5. For version 6.1.0 to 6.1.x: Upgrade to version 6.1.2.27 or later
- 6. For version 6.0.0 to 6.0.x: Upgrade to version 6.0.1.43 or later
- 7. For version 5.3.x: Upgrade to the latest 5.3.x patch release
- 8. For version 4.4a to 5.2.x: Upgrade to the latest 5.2.x patch release or migrate to a supported version (6.x/7.x)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4993 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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