dbcve.org
Connext ProfessionalApplication · Rti

CVE-2024-52064

HIGH · 7.1 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 5.3.1.45 / 6.0.1.40 or later.
See remediation →
74/100
Remediation priority · Elevated
No privileges

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
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in RTI Connext Professional (Core Libraries) allows Overflow Variables and Tags.This issue affects Connext Professional: from 7.0.0 before 7.3.0.2, from 6.1.0 before 6.1.2.21, from 6.0.0 before 6.0.1.40, from 5.0.0 before 5.3.1.45.

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 classic buffer overflow vulnerability exists in RTI Connext Professional Core Libraries where the software copies input data into a buffer without checking the size, allowing overflow of variables and tags. This could allow an attacker to corrupt memory, potentially leading to denial of service or arbitrary code execution.

MitigationUpgrade RTI Connext Professional to version 7.3.0.2, 6.1.2.21, 6.0.1.40, or 5.3.1.45 or later, depending on the current version branch in use.

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
Connext ProfessionalApplication
Affected:>= 4.4, < 5.3.1.45>= 6.0.0, < 6.0.1.40>= 6.1.0, < 6.1.2.21>= 7.0.0, < 7.3.0.2

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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. Locate RTI Connext installation directory
    Identify the installation path of RTI Connext Professional on the system. Common locations include /opt/rti/ or C:\Program Files\RTI\ on Windows. The version is often visible in the installation folder name (e.g., rti_connext_professional-6.1.0).
    Affected if The software is installed in a non-standard location or multiple versions exist.
  2. Identify installed version number
    Retrieve the exact version of RTI Connext Professional installed. This can be done by checking the installation directory name, a version file within the installation, or by running the 'rtiddsgen' command with a version flag if available.
    Affected if Unable to determine the exact version number from the installation.
  3. Compare version against affected ranges
    Check if the installed version falls within any of these vulnerable ranges: >= 4.4 and < 5.3.1.45; >= 6.0.0 and < 6.0.1.40; >= 6.1.0 and < 6.1.2.21; >= 7.0.0 and < 7.3.0.2.
    Affected if The installed version matches one of these ranges, indicating the vulnerability is present.
  4. Confirm Core Libraries component is in use
    Verify that the RTI Connext Core Libraries are actively being used by the system. This is typically the core messaging component required for DDS communication.
    Affected if The Core Libraries component is loaded and processing network data.

The environment is affected if RTI Connext Professional version falls within any of the vulnerable version ranges (4.4 to 5.3.1.44, 6.0.0 to 6.0.1.39, 6.1.0 to 6.1.2.20, or 7.0.0 to 7.3.0.1) and the Core Libraries are in use.

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 5.3.1.45 / 6.0.1.40 / 6.1.2.21 or later
Fixed in 5.3.1.456.0.1.406.1.2.21
Interim mitigation

Upgrade RTI Connext Professional to version 7.3.0.2, 6.1.2.21, 6.0.1.40, or 5.3.1.45 or later, depending on the current version branch in use.

Recommended fix High confidence

Upgrade to 7.3.0.2 (or latest 7.x), or 6.1.2.21 (or latest 6.1.x), or 6.0.1.40 (or latest 6.0.x), or 5.3.1.45 (or latest 5.x) depending on your branch

  1. 1. Identify the currently installed version of RTI Connext Professional by checking the installation directory or running 'rtiddsgen -version'
  2. 2. Determine which version branch you are on (5.x, 6.0.x, 6.1.x, or 7.x)
  3. 3. Download the appropriate fixed version from the RTI Customer Portal or official download site: 5.3.1.45 or later for 5.x, 6.0.1.40 or later for 6.0.x, 6.1.2.21 or later for 6.1.x, 7.3.0.2 or later for 7.x
  4. 4. Review the RTI Connext Professional release notes for the target version to understand any migration requirements
  5. 5. Back up all existing Connext configurations, XML files, and domain participant settings
  6. 6. Stop all running Connext applications and services
  7. 7. Install the upgraded version following the RTI installation guide
  8. 8. Restore configurations from the backup and test application functionality
Caveat Review release notes for API changes between versions; may require recompiling applications against new libraries

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

Fix this in Connext Professional Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,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 $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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