# CVE-2011-4023: Denial of service in n/a

> Remote authenticated users can cause a denial of service via SNMP requests due to a memory leak in Cisco NX-OS.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-8pjj-qqj4-3q78

## What is CVE-2011-4023?

CVE-2011-4023 is a high-severity denial of service vulnerability in Cisco Nx-Os, published on 3 May 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Memory leak in libcmd in Cisco NX-OS 5.0 on Nexus switches allows remote authenticated users to cause a denial of service (memory consumption) via SNMP requests, aka Bug ID CSCtr65682.

Weakness: CWE-399

## Which versions are affected by CVE-2011-4023?

It affects 12 products.


Products: Cisco Nexus 2148t Fex Switch, Cisco Nexus 2224tp Fex Switch, Cisco Nexus 2232pp Fex Switch, Cisco Nexus 2232tm Fex Switch, Cisco Nexus 2248tp E Fex Switch, Cisco Nexus 2248tp Fex Switch, Cisco Nexus 5010p Switch, Cisco Nexus 5020p Switch, Cisco Nexus 5548p, Cisco Nexus 5548up, Cisco Nexus 5596up, Cisco Nx-Os.

## How do I fix CVE-2011-4023?

No fix has been published for CVE-2011-4023 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-4023 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4023 and fix it if it is affected.

What it is: CVE-2011-4023 is a high-severity denial of service vulnerability in Cisco Nx-Os, published on 3 May 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4023 in the wild and no public exploit code.

Affected product: Cisco Nx-Os. 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-2011-4023/ (Markdown: https://insights.sbomify.com/CVE-2011-4023/index.md)
```

## Sources

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

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