# CVE-2024-30212: Microchip Harmony 3 Core library allows read and write access to RAM via a SCSI READ or WRITE command

> An integer overflow in the SCSI command handler allows attackers to read and write arbitrary RAM, potentially exposing sensitive data or modifying memory pointers.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 28 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-30212?

CVE-2024-30212 is a high-severity vulnerability in Microchip MPLAB® Harmony 3 Core Module, published on 28 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

If a SCSI READ(10) command is initiated via USB using the largest LBA 
(0xFFFFFFFF) with it's default block size of 512 and a count of 1,

the first 512 byte of the 0x80000000 memory area is returned to the 
user. If the block count is increased, the full RAM can be exposed.

The same method works to write to this memory area. If RAM contains 
pointers, those can be - depending on the application - overwritten to

return data from any other offset including Progam and Boot Flash.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2024-30212?


## How do I fix CVE-2024-30212?

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

## Is CVE-2024-30212 being exploited?

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

Public exploit code:

- CVE-2024-30212 (github_poc): https://github.com/Fehr-GmbH/blackleak

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30212 and fix it if it is affected.

What it is: CVE-2024-30212 is a high-severity vulnerability in Microchip MPLAB® Harmony 3 Core Module, published on 28 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30212 exists.

Affected product: Microchip MPLAB® Harmony 3 Core Module. 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-2024-30212/ (Markdown: https://insights.sbomify.com/CVE-2024-30212/index.md)
```

## Sources

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

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