CVE-2024-58112
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 · uneditedException capture failure vulnerability in the SVG parsing module of the ArkUI framework Impact: Successful exploitation of this vulnerability may affect availability.
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 confidenceA vulnerability exists in ArkUI framework's SVG parsing module where the code fails to properly capture or handle exceptions. This exception handling flaw can be triggered by malformed SVG input, potentially causing the application to crash or become unavailable. The high CVSS score indicates reliable exploitability leading to denial of service.
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= 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 versionOn the device, go to Settings > About Phone > Version to view the HarmonyOS version number. Alternatively, use 'getprop ro.build.version.harmonyos' via ADB shell.Affected if The version displayed is exactly 5.0.0 (no other version numbers)
-
Identify if application uses ArkUI frameworkReview the application's codebase or documentation to confirm it uses the ArkUI framework for UI rendering. Check for imports or dependencies related to ArkUI or 'ohos.agp' components.Affected if The application leverages ArkUI for rendering or UI management
-
Confirm SVG parsing functionality existsSearch the application code for SVG handling - look for SVG-related classes, methods, or components such as 'SVG', 'SvgImage', 'SvgRenderer', or XML parsers processing .svg files. Also inspect any image loading or vector graphics code paths.Affected if The application parses, renders, or processes SVG files or SVG content
-
Test with malformed SVG inputIf possible, provide a malformed or specially crafted SVG file to the application's SVG parsing function and observe whether an unhandled exception occurs or the application crashes. Monitor logs for 'Exception', 'Error', or 'crash' messages during SVG processing.Affected if The application crashes or throws an uncaught exception when processing malformed SVG input
The environment is affected if running HarmonyOS version 5.0.0 AND the application uses ArkUI framework to parse SVG content, since the exception handling flaw in the SVG parsing module only applies under those specific conditions.
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 the vendor-provided patch for CVE-2024-58112 to the ArkUI framework. If no patch is available, implement robust exception handling and input validation around all SVG parsing operations to prevent unhandled exceptions.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-58112 — 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-58112 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