CVE-2022-34741
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 · uneditedThe NFC module has a buffer overflow vulnerability. Successful exploitation of this vulnerability may cause exceptions in NFC card registration, deletion, and activation.
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 buffer overflow vulnerability exists in the NFC module affecting card registration, deletion, and activation functions. Successful exploitation may cause exceptions, potentially allowing manipulation of NFC card operations due to insufficient bounds checking on input data.
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.0= 11.0.1= 12.0.0= 2.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 your Huawei EMUI versionGo to Settings > About Phone > Version on your Huawei device. Alternatively, use the command 'getprop ro.build.emui_ver' via ADB shell or terminal emulator.Affected if The version listed is 11.0.0, 11.0.1, or 12.0.0
-
Check your Huawei HarmonyOS versionGo to Settings > About Phone > HarmonyOS version. Alternatively, use 'getprop ro.build.version.harmonyos' via ADB shell or terminal emulator.Affected if The version is 2.0
-
Check your Huawei Magic UI versionGo to Settings > About Phone > Version. Alternatively, use 'getprop ro.build.version.magic' via ADB shell or terminal emulator.Affected if The version is 4.0.0
-
Verify NFC is enabled on the deviceGo to Settings > NFC and ensure the NFC toggle is turned ON. On some devices, this may be under Settings > Connections > NFC.Affected if NFC is enabled and the device matches any affected OS version from steps 1-3
-
Review NFC module logs for异常Use ADB to run 'logcat | grep -i nfc' to view NFC-related logs. Check for any exceptions, crashes, or abnormal behavior related to card registration, deletion, or activation operations.Affected if The device runs an affected version AND NFC is enabled AND you observe repeated NFC-related exceptions or unusual behavior during card operations
You are affected if your device runs EMUI 11.0.0, 11.0.1, or 12.0.0, HarmonyOS 2.0, or Magic UI 4.0.0 AND you have NFC enabled and actively use NFC card management features.
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 proper bounds checking and input validation in the NFC module's card management functions to prevent buffer overflows during registration, deletion, and activation operations.
- 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-2022-34741 — 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-2022-34741 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