# CVE-2024-44754: Hardcoded credentials in n/a

> Physically proximate attackers can extract cryptographic keys from internal flash to inject modified firmware into other Minut M2 devices via USB.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-79wv-5cfm-5wm8

## What is CVE-2024-44754?

CVE-2024-44754 is a medium-severity vulnerability in n/a, published on 28 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cryptographic key extraction from internal flash in Minut M2 with firmware version #15142 allows physically proximate attackers to inject modified firmware into any other Minut M2 product via USB.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2024-44754 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-44754 is a medium-severity vulnerability in n/a, published on 28 Feb 2025. 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-2024-44754 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-2024-44754/ (Markdown: https://insights.sbomify.com/CVE-2024-44754/index.md)
```

## Sources

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

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