CVE-2021-22380
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 · uneditedThere is a Cleartext Transmission of Sensitive Information Vulnerability in Huawei Smartphone. Successful exploitation of this vulnerability may affect service confidentiality and 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 involves the cleartext (unencrypted) transmission of sensitive information in Huawei smartphones. Sensitive data such as credentials, personal information, or session tokens may be sent over the network without encryption, allowing attackers on the same network to intercept and read this data via man-in-the-middle attacks.
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= 9.1.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.
-
Identify the installed Emui versionGo to Settings > About Phone on the Huawei device and locate the EMUI version field. Alternatively, use the command 'getprop ro.build.version.emui' via ADB or terminal emulator.Affected if The version listed is exactly 9.1.0
-
Audit applications for cleartext network trafficUse a network traffic analysis tool (such as Wireshark, Burp Suite, or a mobile proxy) to capture and inspect outgoing network connections from the device. Look for HTTP (port 80) connections that transmit credentials, session tokens, personal information, or other sensitive data.Affected if Sensitive data is observed being transmitted over unencrypted HTTP connections rather than HTTPS
-
Check application configurations for unencrypted channelsReview the network security configuration files within installed applications. On Android-based Emui devices, examine the 'network_security_config.xml' files in app APKs or the AndroidManifest.xml for 'android:usesCleartextTraffic' set to true. Identify any apps that allow cleartext traffic to sensitive endpoints.Affected if Applications are configured to permit cleartext traffic to servers transmitting sensitive information
-
Monitor network interfaces for plaintext sensitive dataWhile connected to the same network as the Huawei device, use a network sniffer to capture broadcast traffic and unencrypted flows. Inspect packet contents for visible credentials, authentication tokens, or PII in plaintext.Affected if Readable sensitive information is present in captured network packets using non-encrypted protocols
A user is affected if their Huawei device runs Emui version 9.1.0 AND transmits sensitive data over unencrypted network channels (HTTP instead of HTTPS).
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 TLS/SSL encryption (or certificate pinning) for all network communications that transmit sensitive data. Ensure no sensitive information is transmitted over unencrypted channels (HTTP instead of HTTPS, unencrypted sockets, etc.).
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22380 — 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-2021-22380 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