unixODBC 2.3.1 SQLDriverConnect memory corruption ⚔ [Disputed]

Summaryinfo

A vulnerability marked as problematic has been reported in unixODBC 2.3.1. This impacts the function SQLDriverConnect. The manipulation leads to memory corruption. This vulnerability is documented as CVE-2012-2658. There is not any exploit available. There are still doubts about whether this vulnerability truly exists.

Detailsinfo

A vulnerability was found in unixODBC 2.3.1 (Operating System) and classified as problematic. This issue affects the function SQLDriverConnect. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is availability. The summary by CVE is:

** DISPUTED ** Buffer overflow in the SQLDriverConnect function in unixODBC 2.3.1 allows local users to cause a denial of service (crash) via a long string in the DRIVER option. NOTE: this issue might not be a vulnerability, since the ability to set this option typically implies that the attacker already has legitimate access to cause a DoS or execute code, and therefore the issue would not cross privilege boundaries. There may be limited attack scenarios if isql command-line options are exposed to an attacker, although it seems likely that other, more serious issues would also be exposed, and this issue might not cross privilege boundaries in that context.

The weakness was released 08/31/2012 (Website). The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2012-2658 since 05/14/2012. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

The real existence of this vulnerability is still doubted at the moment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (75940), SecurityFocus (BID 53712†) and OSVDB (82460†). Entry connected to this vulnerability is available at VDB-61960. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Operating System

Name

• unixODBC

Version

• 2.3.1

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion