# CVE-2023-33768: Security feature bypass in n/a

> Attackers can cause a Denial of Service on Belkin Wemo Smart Plugs by uploading crafted firmware due to incorrect signature verification.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jul 2023
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-8c5w-9g3p-g72c

## What is CVE-2023-33768?

CVE-2023-33768 is a medium-severity vulnerability in n/a, published on 13 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Incorrect signature verification of the firmware during the Device Firmware Update process of Belkin Wemo Smart Plug WSP080 v1.2 allows attackers to cause a Denial of Service (DoS) via a crafted firmware file.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 1 product.


Products: Belkin Wemo Smart Plug Wsp080 Firmware.

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

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

## Is CVE-2023-33768 being exploited?

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

Public exploit code:

- DoS against Belkin smart plugs via crafted firmware injection (github_poc): https://github.com/purseclab/CVE-2023-33768
- DoS against Belkin smart plugs via crafted firmware injection (github_poc): https://github.com/Fr0stM0urne/CVE-2023-33768

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33768 is a medium-severity vulnerability in n/a, published on 13 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33768 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-33768/ (Markdown: https://insights.sbomify.com/CVE-2023-33768/index.md)
```

## Sources

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

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