RTI Connext Professional up to 5.3.1.44/6.0.1.39/6.1.2.20/7.3.0.1 Core Libraries buffer overflow

Summaryinfo

A vulnerability was found in RTI Connext Professional up to 5.3.1.44/6.0.1.39/6.1.2.20/7.3.0.1. It has been rated as critical. This impacts an unknown function of the component Core Libraries. This manipulation causes buffer overflow. This vulnerability appears as CVE-2024-52064. The attack requires local access. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical was found in RTI Connext Professional up to 5.3.1.44/6.0.1.39/6.1.2.20/7.3.0.1. Affected by this vulnerability is an unknown function of the component Core Libraries. The manipulation with an unknown input leads to a buffer overflow vulnerability. The CWE definition for the vulnerability is CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at rti.com. This vulnerability is known as CVE-2024-52064 since 11/05/2024. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.

Upgrading to version 5.3.1.45, 6.0.1.40, 6.1.2.21 or 7.3.0.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• RTI

Name

• Connext Professional

Version

• 5.3.1.0
• 5.3.1.1
• 5.3.1.2
• 5.3.1.3
• 5.3.1.4
• 5.3.1.5
• 5.3.1.6
• 5.3.1.7
• 5.3.1.8
• 5.3.1.9
• 5.3.1.10
• 5.3.1.11
• 5.3.1.12
• 5.3.1.13
• 5.3.1.14
• 5.3.1.15
• 5.3.1.16
• 5.3.1.17
• 5.3.1.18
• 5.3.1.19
• 5.3.1.20
• 5.3.1.21
• 5.3.1.22
• 5.3.1.23
• 5.3.1.24
• 5.3.1.25
• 5.3.1.26
• 5.3.1.27
• 5.3.1.28
• 5.3.1.29
• 5.3.1.30
• 5.3.1.31
• 5.3.1.32
• 5.3.1.33
• 5.3.1.34
• 5.3.1.35
• 5.3.1.36
• 5.3.1.37
• 5.3.1.38
• 5.3.1.39
• 5.3.1.40
• 5.3.1.41
• 5.3.1.42
• 5.3.1.43
• 5.3.1.44
• 6.0.1.0
• 6.0.1.1
• 6.0.1.2
• 6.0.1.3
• 6.0.1.4
• 6.0.1.5
• 6.0.1.6
• 6.0.1.7
• 6.0.1.8
• 6.0.1.9
• 6.0.1.10
• 6.0.1.11
• 6.0.1.12
• 6.0.1.13
• 6.0.1.14
• 6.0.1.15
• 6.0.1.16
• 6.0.1.17
• 6.0.1.18
• 6.0.1.19
• 6.0.1.20
• 6.0.1.21
• 6.0.1.22
• 6.0.1.23
• 6.0.1.24
• 6.0.1.25
• 6.0.1.26
• 6.0.1.27
• 6.0.1.28
• 6.0.1.29
• 6.0.1.30
• 6.0.1.31
• 6.0.1.32
• 6.0.1.33
• 6.0.1.34
• 6.0.1.35
• 6.0.1.36
• 6.0.1.37
• 6.0.1.38
• 6.0.1.39
• 6.1.2.0
• 6.1.2.1
• 6.1.2.2
• 6.1.2.3
• 6.1.2.4
• 6.1.2.5
• 6.1.2.6
• 6.1.2.7
• 6.1.2.8
• 6.1.2.9
• 6.1.2.10
• 6.1.2.11
• 6.1.2.12
• 6.1.2.13
• 6.1.2.14
• 6.1.2.15
• 6.1.2.16
• 6.1.2.17
• 6.1.2.18
• 6.1.2.19
• 6.1.2.20
• 7.3.0.0
• 7.3.0.1

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion