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

> Remote attackers can execute arbitrary code via crafted UDP packets due to a stack-based buffer overflow in the libupnp SSDP parser.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mpm3-m3f6-fx5w

## What is CVE-2012-5958?

CVE-2012-5958 is a critical memory corruption vulnerability in n/a, published on 31 Jan 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable SDK for UPnP Devices (aka libupnp, formerly the Intel SDK for UPnP devices) before 1.6.18 allows remote attackers to execute arbitrary code via a UDP packet with a crafted string that is not properly handled after a certain pointer subtraction.

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

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

It affects 1 product.


Products: Libupnp Project Libupnp.

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

Upgrade to a fixed version.

## Is CVE-2012-5958 being exploited?

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

Public exploit code:

- Discover uPNP devices vulnerable to  CVE-2013-0229 / CVE-2013-0230 / CVE-2012-5958 / CVE-2012-5959 (github_poc): https://github.com/lochiiconnectivity/vulnupnp
- Portable UPnP SDK unique_service_name() Remote Code Execution (metasploit)
- Portable UPnP SDK - 'unique_service_name()' Remote Code Execution (Metasploit) (exploitdb)
- libupnp 1.6.18 - Stack-based buffer overflow (DoS) (exploitdb)
- Research-driven UPnP vulnerability scanner focusing on libupnp 1.6.19 and CVE-2012-5958. (github_poc): https://github.com/hmrumman777-beep/NetAudit-IoT
- UPnP SSDP M-SEARCH Information Discovery (metasploit)

## Other vulnerabilities in n/a

- [CVE-2012-5961](https://insights.sbomify.com/CVE-2012-5961/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5958 is a critical memory corruption vulnerability in n/a, published on 31 Jan 2013. 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-2012-5958 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-2012-5958/ (Markdown: https://insights.sbomify.com/CVE-2012-5958/index.md)
```

## Sources

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

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