dbcve.org
Connext ProfessionalApplication · Rti

CVE-2025-1254

HIGH · 7.4 CVSS v3.1 Published 2025-05-08
Fix available
A fix is available. Upgrade to 6.1.2.23 / 7.3.0.7 or later.
See remediation →
83/100
Remediation priority · High
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
Out-of-bounds Read, Out-of-bounds Write vulnerability in RTI Connext Professional (Recording Service) allows Overflow Buffers, Overread Buffers.This issue affects Connext Professional: from 7.4.0 before 7.5.0, from 7.0.0 before 7.3.0.7, from 6.1.0 before 6.1.2.23, from 6.0.0 before 6.0.1.42.

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

Out-of-bounds read/write vulnerability in RTI Connext Professional Recording Service allows attackers to overflow or overread buffers. This memory safety flaw could enable code execution or information disclosure via specially crafted input to the Recording Service component.

MitigationUpgrade RTI Connext Professional to version 7.5.0 or later, or to the patched versions 7.3.0.7, 6.1.2.23, or 6.0.1.42 depending on the current branch.

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:>= 6.0.0, <= 6.0.1.40>= 6.1.0, < 6.1.2.23>= 7.0.0, < 7.3.0.7>= 7.4.0, < 7.5.0

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 Professional installation
    Search for RTI installation directories such as C:\Program Files\RTI\ or /opt/rti/ on Linux. Look for folders named 'connext' or 'rti_connext_professional'.
    Affected if The RTI Connext Professional software is found on the system.
  2. Identify installed version
    Check for a version file or manifest in the installation directory. Common locations: <install_dir>/version.txt, <install_dir>/release.txt, or inspect the 'rti Version' property in the About dialog if available via the launcher.
    Affected if Unable to determine version indicates potential unpatched installation.
  3. Verify version against affected ranges
    Compare the installed version number to these vulnerable ranges: 6.0.0 through 6.0.1.40, 6.1.0 through 6.1.2.22, 7.0.0 through 7.3.0.6, and 7.4.0 through 7.4.x. The version falls into any of these ranges.
  4. Confirm Recording Service component is present
    Check for the Recording Service binary or configuration files in <install_dir>/bin/ or <install_dir>/lib/. Look for executables named 'recorder', 'recording_service', or 'rtirecordingservice', or XML configuration files with 'recording' in the filename.
    Affected if The Recording Service component is installed and available on the system.

If RTI Connext Professional is installed with the Recording Service component and the version falls within any of the affected ranges (6.0.0-6.0.1.40, 6.1.0-6.1.2.22, 7.0.0-7.3.0.6, or 7.4.0-7.4.x), the environment is vulnerable to CVE-2025-1254.

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 6.1.2.23 / 7.3.0.7 / 7.5.0 or later
Fixed in 6.1.2.237.3.0.77.5.0
Interim mitigation

Upgrade RTI Connext Professional to version 7.5.0 or later, or to the patched versions 7.3.0.7, 6.1.2.23, or 6.0.1.42 depending on the current branch.

Recommended fix High confidence

Upgrade to the next available fixed release in your current major version line: 6.0.1.42, 6.1.2.23, 7.3.0.7, or 7.5.0

  1. 1. Identify the current installed version of RTI Connext Professional by checking the installation directory or running 'rtiddsgen -version'
  2. 2. Based on the current version, upgrade to the minimum fixed version in that release line: 6.0.1.42, 6.1.2.23, 7.3.0.7, or 7.5.0
  3. 3. Download the appropriate fixed version from the RTI Customer Portal at https://www.rti.com/downloads
  4. 4. Back up existing Connext configurations and data before upgrading
  5. 5. Install the upgraded version following RTI's standard installation procedures
  6. 6. Verify the Recording Service starts successfully and test that recording/playback functionality works as expected
  7. 7. Re-apply any custom configuration settings that were in place
Caveat Upgrades between minor versions in Connext typically maintain configuration compatibility, but review the release notes for any behavioral changes or deprecated features

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

Fix this in Connext Professional Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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