CVE-2024-57958
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 · uneditedOut-of-bounds array read vulnerability in the FFRT module Impact: Successful exploitation of this vulnerability may cause features to perform abnormally.
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 confidenceThis is an out-of-bounds array read vulnerability in the FFRT (Fast Forward Runtime) module. The vulnerability allows reading memory outside the bounds of an allocated array, which could lead to information disclosure, denial of service, or abnormal feature behavior. A CVSS score of 9.1 indicates the issue is remotely exploitable and could have severe impact on system integrity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 14.0.0= 4.0.0= 4.2.0= 4.3.0= 5.0.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check HarmonyOS or EMUI versionNavigate to Settings > About Phone on the Huawei device and verify the OS version. On command line, use 'getprop ro.build.version.emui' or 'getprop ro.build.version.huawei'Affected if The version matches 4.0.0, 4.2.0, 4.3.0, 5.0.0 (HarmonyOS) or 14.0.0 (EMUI)
-
Verify FFRT module presenceCheck if the FFRT library exists on the system. Use 'find /system/lib -name '*ffrt*' or 'ls -la /vendor/lib64/ffrt/' if availableAffected if The FFRT library files are present on the device
-
Check FFRT service statusQuery running services for FFRT-related processes using 'dumpsys' or check /proc/ for ffrt-related entries. Run 'dumpsys | grep -i ffrt'Affected if FFRT service or daemon is actively running on the system
-
Inspect FFRT configurationLook for FFRT configuration files in /etc/, /vendor/etc/, or /system/etc/ directories. Check for files named 'ffrt.conf', 'ffrt_config.xml', or similarAffected if FFRT configuration files exist and the module is enabled for use
-
Review system logs for FFRT errorsRun 'logcat -d | grep -i ffrt' or check /sys/fs/pstore/ for console-ramoops to look for out-of-bounds read errors or crashes related to FFRTAffected if Logs show FFRT-related crashes, array boundary errors, or memory access violations
The device is affected if it runs HarmonyOS 4.0.0/4.2.0/4.3.0/5.0.0 or EMUI 14.0.0 AND the FFRT module is present and enabled on the system.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-provided patches for the FFRT module to add proper bounds checking before array access. If no patch is available, implement input validation and boundary checks in the affected code paths.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57958 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-57958 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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