dbcve.org
Connext ProfessionalApplication · Rti

CVE-2024-52063

HIGH · 8.6 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 →
95/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
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in RTI Connext Professional (Core Libraries, Routing Service) allows Overflow Variables and Tags.This issue affects Connext Professional: from 7.0.0 before 7.3.0.5, 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's Core Libraries and Routing Service. The flaw stems from copying data to a buffer without validating input size, allowing attackers to overflow variables and tags. This affects versions 7.0.0-7.3.0.4, 6.1.0-6.1.2.20, 6.0.0-6.0.1.39, and 5.0.0-5.3.1.44.

MitigationUpgrade to RTI Connext Professional version 7.3.0.5, 6.1.2.21, 6.0.1.40, or 5.3.1.45 or later. If immediate patching is not feasible, isolate affected systems via network segmentation and restrict external access to Routing Service interfaces.

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.5

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
Changed
Confidentiality
None
Integrity
High
Availability
None

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

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
    Check common installation paths: Windows (C:\Program Files\RTI\connext), Linux (/opt/rti/connext). Use 'where connext' on Windows or 'find /opt -name "rti*" -type d' on Linux.
    Affected if RTI Connext is installed in the environment
  2. Identify installed version
    Look for version file in installation directory (often named VERSION, rti_version.txt, or in the bin folder). Run 'rtiddsgen -version' if available, or check the DLL/shared library properties.
    Affected if Version falls within affected ranges: 5.0.0-5.3.1.44, 6.0.0-6.0.1.39, 6.1.0-6.1.2.20, or 7.0.0-7.3.0.4
  3. Determine if Routing Service is in use
    Check for Routing Service configuration files (routing_service.xml), running processes named 'routing_service', or examine the 'NDDSROUTER' environment variable.
    Affected if Routing Service is configured or running, as the vulnerability affects both Core Libraries and Routing Service
  4. Verify exposed network interfaces
    Review Routing Service XML configuration for <discovery> or <transport> elements exposing UDP/TCP ports to external networks. Check firewall rules for RTI ports (typically 7400-7401 range).
    Affected if Routing Service interfaces are accessible from untrusted networks

You are affected if RTI Connext Professional is installed with a version in the 5.0.0-5.3.1.44, 6.0.0-6.0.1.39, 6.1.0-6.1.2.20, or 7.0.0-7.3.0.4 range and the Core Libraries or Routing Service 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 to RTI Connext Professional version 7.3.0.5, 6.1.2.21, 6.0.1.40, or 5.3.1.45 or later. If immediate patching is not feasible, isolate affected systems via network segmentation and restrict external access to Routing Service interfaces.

Recommended fix High confidence

Upgrade to the minimum fixed version for your branch: 5.3.1.45 (for 5.x), 6.0.1.40 (for 6.0.x), 6.1.2.21 (for 6.1.x), or 7.3.0.5 (for 7.x)

  1. 1. Identify the current installed version of RTI Connext Professional by checking the installation directory or running 'rtiddsgen -version'
  2. 2. Determine which version branch you are currently on (5.x, 6.0.x, 6.1.x, or 7.x)
  3. 3. For Connext 5.x users: Upgrade to version 5.3.1.45 or later
  4. 4. For Connext 6.0.x users: Upgrade to version 6.0.1.40 or later
  5. 5. For Connext 6.1.x users: Upgrade to version 6.1.2.21 or later
  6. 6. For Connext 7.x users: Upgrade to version 7.3.0.5 or later
  7. 7. Verify the upgrade by checking the new version number matches the target fixed release
  8. 8. Test the upgraded Connext deployment in a staging environment before production rollout
Caveat Review RTI Connext release notes for your target version to check for any API or configuration changes that may affect existing applications

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

Fix this in Connext Professional Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
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,296.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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