# CVE-2023-27217: Memory corruption in n/a

> Attackers can cause a Denial of Service on Belkin Smart Outlet V2 devices via a crafted UPNP request exploiting a stack-based buffer overflow.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2023
- **Updated:** 22 Jan 2025
- **Also known as:** GHSA-hxhv-3r5g-q28x

## What is CVE-2023-27217?

CVE-2023-27217 is a critical memory corruption vulnerability in n/a, published on 18 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack-based buffer overflow in the ChangeFriendlyName() function of Belkin Smart Outlet V2 F7c063 firmware_2.00.11420.OWRT.PVT_SNSV2 allows attackers to cause a Denial of Service (DoS) via a crafted UPNP request.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-27217?

It affects 1 product.


Products: Belkin F7c063 Firmware.

## How do I fix CVE-2023-27217?

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

## Is CVE-2023-27217 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27217 and fix it if it is affected.

What it is: CVE-2023-27217 is a critical memory corruption vulnerability in n/a, published on 18 May 2023. 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-2023-27217 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-2023-27217/ (Markdown: https://insights.sbomify.com/CVE-2023-27217/index.md)
```

## Sources

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

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