# CVE-2010-2891: Memory corruption in n/a

> A buffer overflow in libsmi allows remote attackers to execute arbitrary code via a crafted Object Identifier string.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2010
- **Updated:** 7 Aug 2024
- **Also known as:** AZL-34938, AZL-6647, AZL-7272, DEBIAN-CVE-2010-2891, DSA-2145-1, GHSA-gwqp-8wjj-p3gj, openSUSE-SU-2024:10266-1

## What is CVE-2010-2891?

CVE-2010-2891 is a high-severity memory corruption vulnerability in n/a, published on 27 Oct 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the smiGetNode function in lib/smi.c in libsmi 0.4.8 allows context-dependent attackers to execute arbitrary code via an Object Identifier (aka OID) represented as a numerical string containing many components separated by . (dot) characters.

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

## Which versions are affected by CVE-2010-2891?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libsmi` | openSUSE:Tumbleweed | All versions | 0.4.8-24.8 |

Products: Tu-Braunschweig Libsmi.

## How do I fix CVE-2010-2891?

Upgrade to a fixed version.

## Is CVE-2010-2891 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-2891 exists.

Public exploit code:

- LibSMI smiGetNode - Buffer Overflow When Long OID Is Given In Numerical Form (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2891 and fix it if it is affected.

What it is: CVE-2010-2891 is a high-severity memory corruption vulnerability in n/a, published on 27 Oct 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-2891 exists.

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-2010-2891/ (Markdown: https://insights.sbomify.com/CVE-2010-2891/index.md)
```

## Sources

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

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