dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2024-44754

MEDIUM · 6.8 CVSS v3.1 Published 2025-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Minut M2 device (firmware #15142) contains a vulnerability where cryptographic keys can be extracted from internal flash memory by physically proximate attackers. Once keys are extracted, attackers can inject modified firmware into any other Minut M2 device via USB connection.

MitigationLimit physical access to Minut M2 devices and apply any available firmware updates that address key storage vulnerabilities. Consider device replacement if hardware-level fixes are required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Minut M2 device
    Locate and confirm the device model in your inventory - look for 'Minut M2' label, serial number, or network discovery showing Minut M2 as the device type
    Affected if Device is a Minut M2 and firmware version is #15142
  2. Check firmware version
    Access device admin interface or use device management tool to retrieve the installed firmware version number
    Affected if Firmware version is exactly #15142 (no other versions are affected per this CVE)
  3. Verify USB access is enabled
    Check device configuration settings for USB firmware update interface, USB debugging, or USB device mode options
    Affected if USB interface is accessible or enabled, allowing potential firmware injection after key extraction
  4. Assess physical access controls
    Inspect physical location of device - check if device is in secured area, locked cabinet, or controlled access environment
    Affected if Device can be accessed by unauthorized or physically proximate attackers who could extract keys from flash memory

You are affected only if you have a Minut M2 device running firmware #15142 with USB access enabled in a physically accessible location.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Limit physical access to Minut M2 devices and apply any available firmware updates that address key storage vulnerabilities. Consider device replacement if hardware-level fixes are required.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44754 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-44754 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data