CVE-2024-25724
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 · uneditedIn RTI Connext Professional 5.3.1 through 6.1.0 before 6.1.1, a buffer overflow in XML parsing from Routing Service, Recording Service, Queuing Service, and Cloud Discovery Service allows attackers to execute code with the affected service's privileges, compromise the service's integrity, leak sensitive information, or crash the service. These attacks could be done via a remote malicious RTPS message; a compromised call with malicious parameters to the RTI_RoutingService_new, rti::recording::Service, RTI_QueuingService_new, or RTI_CDS_Service_new public APIs; or a compromised local file system containing a malicious XML file.
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 confidenceBuffer overflow vulnerability in XML parsing within RTI Connext Professional's Routing Service, Recording Service, Queuing Service, and Cloud Discovery Service. Attackers can trigger the overflow via malicious RTPS messages, compromised API calls with malicious XML parameters, or malicious XML files on the local filesystem. This allows code execution with service privileges, integrity compromise, information disclosure, or service crash.
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>= 5.3.0, < 5.3.1.44>= 6.0.0, < 6.0.1.35= 6.1.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed RTI Connext Professional versionLocate the RTI Connext installation directory and check the version manifest or use the rtiddsgen version command if available. Check files such as VERSION.txt in the installation root or examine the NDDSHOME version file.Affected if The installed version falls within >= 5.3.0 and < 5.3.1.44, OR >= 6.0.0 and < 6.1.1.35, OR equals exactly 6.1.0.
-
Identify which affected services are deployedReview your system for running instances or configured deployments of Routing Service, Recording Service, Queuing Service, or Cloud Discovery Service. Check for service configuration files, startup scripts, or process listings.Affected if Any of these four services (Routing Service, Recording Service, Queuing Service, Cloud Discovery Service) are running or configured to run.
-
Locate XML configuration files used by affected servicesSearch the filesystem for XML configuration files associated with these services, typically found in the RTI installation directory under rti_config or in user-specified paths. Look for .xml files with names like RoutingService.xml, RecordingService.xml, QueuingService.xml, or CloudDiscoveryService.xml.Affected if XML configuration files exist and are loaded by any of the affected services.
-
Check for exposed RTPS network portsReview network configuration and firewall rules for open ports associated with RTPS communication (typically UDP/TCP ports in the 7400-7409 range). Use netstat or similar tools to identify listening RTPS ports.Affected if RTPS ports are accessible from untrusted networks, allowing malicious RTPS messages to reach the services.
You are affected if your installed RTI Connext Professional version is within the vulnerable ranges AND any of the four affected services (Routing, Recording, Queuing, or Cloud Discovery) are deployed with accessible XML configuration or exposed RTPS ports.
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 · scoped5.3.1.446.0.1.35
Upgrade to RTI Connext Professional 6.1.1 or later to obtain the patch. If immediate patching is not feasible, restrict network access to RTPS ports and validate/audit all XML configuration files before loading.
RTI Connext Professional 6.1.1 (or 5.3.1.44 for 5.3.x releases, 6.0.1.35 for 6.0.x releases)
- 1. Identify the currently installed RTI Connext Professional version by checking the installation directory or using the version inquiry mechanism provided by RTI
- 2. For Connext Professional 5.3.x versions (>=5.3.0): Upgrade to version 5.3.1.44 or later
- 3. For Connext Professional 6.0.x versions (>=6.0.0): Upgrade to version 6.0.1.35 or later
- 4. For Connext Professional 6.1.0: Upgrade to version 6.1.1
- 5. After upgrading, restart all affected services (Routing Service, Recording Service, Queuing Service, and Cloud Discovery Service) to load the fixed libraries
- 6. Verify the upgrade by checking that the XML parser no longer accepts malformed input that could trigger the buffer overflow
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25724 — 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-2024-25724 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