Security readout for executives and security teams
Plain-English summary
This issue affects Crucial MX500 SSD firmware M3CR046. A local, highly privileged actor could send specially crafted ATA traffic to the drive controller and trigger a buffer overflow. Business risk is highest where these drives store sensitive or operationally critical data. The supplier says remediation was completed in December 2024 and updated firmware is available.
Executive priority
Treat this as a targeted firmware-remediation task, not an emergency internet-facing incident. Prioritize high-value endpoints and servers with Crucial MX500 drives, because successful exploitation could affect stored data and system availability.
Technical view
CVE-2024-42642 is a CWE-120 buffer overflow in Micron Crucial MX500 Series Solid State Drives running M3CR046 firmware. The CVSS 3.1 score is 6.7 with local access, low complexity, high privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to systems using Crucial MX500 SSDs with the affected M3CR046 firmware. The CVE record’s structured affected-product fields are incomplete, so asset and firmware validation is necessary before scoping remediation.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires local access and high privileges on the host, which reduces internet-scale risk but matters on shared, compromised, or administrator-accessible systems.
Researcher notes
The public record names ATA packets from host to controller as the trigger and reports full remediation in December 2024. Avoid broad product assumptions: the structured affected fields are listed as n/a, and the bundle only supports MX500 firmware M3CR046.
Mitigation direction
- Identify systems with Crucial MX500 SSDs and record firmware versions.
- Update affected drives using Crucial’s official MX500 support guidance.
- Prioritize systems holding sensitive data or supporting critical operations.
- Review vendor guidance before relying on any workaround.
- Track the CVE record and Crucial support page for updates.
Validation and detection
- Confirm the drive model is Crucial MX500, not another SSD family.
- Verify whether firmware M3CR046 is present on each system.
- Check Crucial’s support page for the current remediated firmware.
- Document updated firmware versions after remediation.
- Confirm no KEV or cited source indicates active exploitation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-42642 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.7MediumVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/VL4DR/CVE-2024-42642/tree/mainCVE reference, mitre
- https://www.crucial.com/support/ssd-support/mx500-supportCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.