# CVE-2012-2658: Memory corruption in n/a

> Local attackers can crash unixODBC via a buffer overflow in SQLDriverConnect, though privilege escalation is unlikely.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2658, GHSA-8mx7-qh9r-7vj7, UBUNTU-CVE-2012-2658

## What is CVE-2012-2658?

CVE-2012-2658 is a low-severity memory corruption vulnerability in n/a, published on 31 Aug 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2012-2658?

It affects 1 product.


Products: Unixodbc Unixodbc.

## How do I fix CVE-2012-2658?

Upgrade to a fixed version.

## Is CVE-2012-2658 being exploited?

There is no known exploitation of CVE-2012-2658 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-7485](https://insights.sbomify.com/CVE-2018-7485/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-7409](https://insights.sbomify.com/CVE-2018-7409/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-1013](https://insights.sbomify.com/CVE-2024-1013/): Unixodbc: out of bounds stack write due to pointer-to-integer types conversion (high 7.8)
- [CVE-2012-2657](https://insights.sbomify.com/CVE-2012-2657/): Memory corruption in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2658 and fix it if it is affected.

What it is: CVE-2012-2658 is a low-severity memory corruption vulnerability in n/a, published on 31 Aug 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2658 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-2658/ (Markdown: https://insights.sbomify.com/CVE-2012-2658/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2658
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2658
- OSV: https://osv.dev/vulnerability/CVE-2012-2658

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-2658/
Summaries are generated and may contain mistakes; the official description above is the record.