CVE-2023-46774
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 · uneditedVulnerability of uncaught exceptions in the NFC module. Successful exploitation of this vulnerability can affect NFC 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 confidenceThis vulnerability in the NFC module involves uncaught exceptions that can cause the NFC service to become unavailable. When malformed or unexpected NFC data is processed, the lack of proper exception handling allows the NFC module to crash or become unresponsive, leading to denial of service for NFC-dependent functionality.
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= 11.0.1= 12.0.0= 12.0.1= 13.0.0= 2.0.0= 2.0.1= 2.1.0= 3.0.0= 3.1.0= 4.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.
-
Identify device OS and versionCheck the device settings: go to Settings > About Phone > Version (or Settings > System > About Device). Confirm it runs Huawei EMUI or HarmonyOS and note the exact version number.Affected if The OS is EMUI 11.0.1, 12.0.0, 12.0.1, or 13.0.0; OR HarmonyOS 2.0.0, 2.0.1, 2.1.0, 3.0.0, 3.1.0, or 4.0.0
-
Confirm NFC is enabledNavigate to Settings > NFC (or Settings > Connections > NFC on some models). Verify if NFC toggle is turned on.Affected if NFC is enabled on a device running one of the affected versions listed above
-
Check NFC service statusUse device diagnostics or dial *#*#2846579#*#* to access service menu, then check NFC service status under ProjectMenu > Background settings > NFC service. Alternatively, attempt to use NFC (e.g., tap a tag or NFC-enabled device) and observe if it responds or crashes.Affected if NFC service fails to respond, crashes, or shows unavailable status when attempting to use NFC functionality on an affected version
-
Check for NFC-related crash logsAccess device logs via Settings > System > Developer options > Logging buffer (or use ADB logcat to filter for NFC-related crashes: adb logcat | grep -i nfc). Look for uncaught exception errors in the NFC module.Affected if Logs show uncaught exceptions or fatal errors related to NFC service that cause it to become unavailable
You are affected if your Huawei device runs EMUI 11.0.1, 12.0.0, 12.0.1, or 13.0.0 OR HarmonyOS 2.0.0, 2.0.1, 2.1.0, 3.0.0, 3.1.0, or 4.0.0, and NFC functionality is enabled or used.
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 dataImplement comprehensive exception handling throughout the NFC module to catch and properly manage all potential error conditions. Apply vendor-provided patches for the NFC component and validate that NFC services remain functional after implementation.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46774 — 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-2023-46774 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