# CVE-2021-34268: Denial of service in n/a

> A malformed USB device packet can cause a denial of service in STM32Cube Middleware, affecting embedded systems using this library.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xfw8-5222-p9q7

## What is CVE-2021-34268?

CVE-2021-34268 is a medium-severity denial of service vulnerability in n/a, published on 22 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in the USBH_ParseDevDesc() function of STMicroelectronics STM32Cube Middleware v1.8.0 and below causes a denial of service (DOS) via a malformed USB device packet.

## Which versions are affected by CVE-2021-34268?

It affects 1 product.


Products: St Stm32cube Middleware.

## How do I fix CVE-2021-34268?

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

## Is CVE-2021-34268 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-34259](https://insights.sbomify.com/CVE-2021-34259/): Memory corruption in n/a (medium 6.8)
- [CVE-2021-34260](https://insights.sbomify.com/CVE-2021-34260/): Memory corruption in n/a (medium 6.8)
- [CVE-2021-34262](https://insights.sbomify.com/CVE-2021-34262/): Memory corruption in n/a (medium 6.8)
- [CVE-2021-34261](https://insights.sbomify.com/CVE-2021-34261/): Denial of service in n/a (medium 4.6)
- [CVE-2021-34267](https://insights.sbomify.com/CVE-2021-34267/): Denial of service in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-34268 and fix it if it is affected.

What it is: CVE-2021-34268 is a medium-severity denial of service vulnerability in n/a, published on 22 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-34268 in the wild and no public exploit code.

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-2021-34268/ (Markdown: https://insights.sbomify.com/CVE-2021-34268/index.md)
```

## Sources

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

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