# CVE-2015-5621: Memory corruption in n/a

> Remote attackers can cause a crash or execute arbitrary code via crafted SNMP packets due to improper memory handling in net-snmp.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Aug 2015
- **Updated:** 4 Dec 2025
- **Also known as:** DEBIAN-CVE-2015-5621, GHSA-w7cc-jv4p-qccr, SUSE-SU-2015:1524-1, SUSE-SU-2015:1556-1, UBUNTU-CVE-2015-5621

## What is CVE-2015-5621?

CVE-2015-5621 is a high-severity memory corruption vulnerability in n/a, published on 19 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The snmp_pdu_parse function in snmp_api.c in net-snmp 5.7.2 and earlier does not remove the varBind variable in a netsnmp_variable_list item when parsing of the SNMP PDU fails, which allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted packet.

Weakness: CWE-19, CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2015-5621?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `net-snmp` | SUSE:Linux Enterprise Desktop 11 SP3 | All versions | 5.4.2.1-8.12.24.1 |
| `net-snmp` | SUSE:Linux Enterprise Desktop 11 SP4 | All versions | 5.4.2.1-8.12.24.1 |
| `net-snmp` | SUSE:Linux Enterprise Desktop 12 | All versions | 5.7.2.1-4.3.2 |
| `net-snmp` | SUSE:Linux Enterprise Server 11 SP3 | All versions | 5.4.2.1-8.12.24.1 |
| `net-snmp` | SUSE:Linux Enterprise Server 11 SP3-TERADATA | All versions | 5.4.2.1-8.12.24.1 |
| `net-snmp` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 5.4.2.1-8.12.24.1 |
| `net-snmp` | SUSE:Linux Enterprise Server 12 | All versions | 5.7.2.1-4.3.2 |
| `net-snmp` | SUSE:Linux Enterprise Server for SAP Applications 11 SP3 | All versions | 5.4.2.1-8.12.24.1 |
| `net-snmp` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 5.4.2.1-8.12.24.1 |
| `net-snmp` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 5.7.2.1-4.3.2 |
| `net-snmp` | SUSE:Linux Enterprise Software Development Kit 11 SP3 | All versions | 5.4.2.1-8.12.24.1 |
| `net-snmp` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 5.4.2.1-8.12.24.1 |
| `net-snmp` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 5.7.2.1-4.3.2 |

Products: Net-Snmp Net-Snmp.

## How do I fix CVE-2015-5621?

Apply the vendor's patch.

## Is CVE-2015-5621 being exploited?

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

Public exploit code:

- net-snmp 5.7.3 - (Authenticated) Denial of Service (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-4837](https://insights.sbomify.com/CVE-2005-4837/): Use after free in n/a (critical 10.0)
- [CVE-2005-1740](https://insights.sbomify.com/CVE-2005-1740/): Path traversal in n/a (critical 10.0)
- [CVE-2007-5846](https://insights.sbomify.com/CVE-2007-5846/): Denial of service in n/a (high 7.8)
- [CVE-2018-18066](https://insights.sbomify.com/CVE-2018-18066/): Null dereference in n/a (high 7.5)
- [CVE-2008-4309](https://insights.sbomify.com/CVE-2008-4309/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5621 and fix it if it is affected.

What it is: CVE-2015-5621 is a high-severity memory corruption vulnerability in n/a, published on 19 Aug 2015. 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-2015-5621 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-2015-5621/ (Markdown: https://insights.sbomify.com/CVE-2015-5621/index.md)
```

## Sources

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

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