# CVE-2022-38392: Denial of service in n/a

> Physically proximate attackers can cause hard drive malfunction and system crash via resonant-frequency audio attacks, affecting older 5400 RPM drives.

- **Severity:** Medium 5.3 (`CVSS:3.1/AC:L/AV:P/A:H/C:N/I:N/PR:N/S:C/UI:N`)
- **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:** 17 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4355-8x7v-vfpv

## What is CVE-2022-38392?

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

### Official description

Certain 5400 RPM hard drives, for laptops and other PCs in approximately 2005 and later, allow physically proximate attackers to cause a denial of service (device malfunction and system crash) via a resonant-frequency attack with the audio signal from the Rhythm Nation music video. A reported product is Seagate STDT4000100 763649053447.

## Which versions are affected by CVE-2022-38392?

It affects 1 product.


Products: * 5400rmp Oem Harddrive.

## How do I fix CVE-2022-38392?

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

## Is CVE-2022-38392 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38392 and fix it if it is affected.

What it is: CVE-2022-38392 is a medium-severity denial of service vulnerability in n/a, published on 17 Aug 2022. 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-2022-38392 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-2022-38392/ (Markdown: https://insights.sbomify.com/CVE-2022-38392/index.md)
```

## Sources

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

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