# CVE-2024-4760: Voltage glitch during startup of the EEFC NVM controller can bypass the security bit

> Voltage glitching during startup bypasses security bits, allowing debug interface access to memory on Microchip SAM microcontrollers.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 May 2024
- **Updated:** 6 Jun 2025
- **Also known as:** GHSA-5mp7-g9p8-p9xx

## What is CVE-2024-4760?

CVE-2024-4760 is a medium-severity vulnerability in Microchip SAM3N, published on 16 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A voltage glitch during the startup of EEFC NVM controllers on Microchip SAM E70/S70/V70/V71, SAM G55, SAM 4C/4S/4N/4E, and SAM 3S/3N/3U microcontrollers allows access to the memory bus via the debug interface even if the security bit is set.

Weakness: CWE-1247 (Improper Protection Against Voltage and Clock Glitches)

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


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

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

## Is CVE-2024-4760 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4760 is a medium-severity vulnerability in Microchip SAM3N, published on 16 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-4760 in the wild and no public exploit code.

Affected product: Microchip SAM3N. 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-4760/ (Markdown: https://insights.sbomify.com/CVE-2024-4760/index.md)
```

## Sources

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

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