dbcve.org
Connext ProfessionalApplication · Rti

CVE-2024-52058

HIGH · 7.8 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 6.1.2.19 / 7.3.0.2 or later.
See remediation →
80/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in RTI Connext Professional (System Designer) allows OS Command Injection.This issue affects Connext Professional: from 7.0.0 before 7.3.0.2, from 6.1.0 before 6.1.2.19.

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

OS Command Injection vulnerability in RTI Connext Professional System Designer allows attackers to execute arbitrary OS commands due to improper neutralization of special elements. This affects versions 7.0.0 through 7.3.0.1 and 6.1.0 through 6.1.2.18, potentially enabling complete system compromise.

MitigationUpgrade to RTI Connext Professional version 7.3.0.2 or 6.1.2.19 and later. If immediate patching is not feasible, restrict network access to the System Designer component and implement network segmentation to limit exposure.

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.1.0, < 6.1.2.19>= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Identify RTI Connext Professional version
    Check the installed version of RTI Connext Professional by examining the product documentation, installation directory, or running the version command if available. Common locations include the installation folder or product metadata files.
    Affected if The installed version falls within 6.1.0 through 6.1.2.18 OR 7.0.0 through 7.3.0.1 (meaning version is >= 6.1.0 and < 6.1.2.19, or >= 7.0.0 and < 7.3.0.2)
  2. Verify System Designer component status
    Determine whether the System Designer component is installed and enabled in the RTI Connext Professional environment. This may be found in the product configuration, modular component list, or feature enablement settings.
    Affected if System Designer is installed and actively enabled in the environment
  3. Assess System Designer network exposure
    Review network configuration, firewall rules, and access controls to determine if the System Designer service is exposed to the network or accessible remotely.
    Affected if System Designer is accessible from network locations or has open network listeners
  4. Check for unauthorized command execution
    Review system logs, application logs, and process monitoring for any unexpected or suspicious command executions that may align with the timeframe of the vulnerable version deployment.
    Affected if Unexpected OS commands or suspicious process activity is found in logs or monitoring tools associated with RTI Connext or System Designer processes

You are affected if RTI Connext Professional version is 6.1.0 through 6.1.2.18 or 7.0.0 through 7.3.0.1 AND the System Designer component is enabled and accessible in your environment.

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.19 / 7.3.0.2 or later
Fixed in 6.1.2.197.3.0.2
Interim mitigation

Upgrade to RTI Connext Professional version 7.3.0.2 or 6.1.2.19 and later. If immediate patching is not feasible, restrict network access to the System Designer component and implement network segmentation to limit exposure.

Recommended fix High confidence

RTI Connext Professional 7.3.0.2 (or 6.1.2.19 for 6.1.x branch)

  1. 1. Identify the currently installed RTI Connext Professional version by checking the product documentation or system information
  2. 2. If running version 6.1.0 through 6.1.2.18, download and install version 6.1.2.19 from the RTI customer portal or official download site
  3. 3. If running version 7.0.0 through 7.3.0.1, download and install version 7.3.0.2 from the RTI customer portal or official download site
  4. 4. After installation, verify the new version is correctly installed and the System Designer component is functioning properly
  5. 5. Test that existing applications and configurations work correctly with the patched version

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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