CVE-2019-19441
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 · uneditedHUAWEI P30 smart phones with versions earlier than 10.0.0.166(C00E66R1P11) have an information leak vulnerability. An attacker could send specific command in the local area network (LAN) to exploit this vulnerability. Successful exploitation may cause information leak.
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 confidenceHUAWEI P30 smartphones running firmware versions earlier than 10.0.0.166(C00E66R1P11) contain an information leak vulnerability. An attacker on the same local area network can send specific commands to the device to trigger the vulnerability, potentially exposing sensitive information.
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< 10.0.0.166\(c00e66r1p11\)CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Confirm device model is Huawei P30Navigate to Settings > About Phone on the device, or check the device packaging/label, to verify the exact model number is HUAWEI P30 (model variants like ELE-L29, ELE-L04, etc. are also affected)Affected if Device model is any variant of Huawei P30
-
Locate firmware version in device settingsGo to Settings > About Phone > Version on the Huawei P30 device. Record the Build Number or Software Version displayed (typically shown as something like 10.0.0.xxx(Cxxx))Affected if Version information cannot be located or is not visible in the About Phone section
-
Compare installed firmware version against affected rangeCompare the displayed version number to the affected range: versions earlier than 10.0.0.166(C00E66R1P11). The first three octets (10.0.0) must be less than 166 in the build number to be vulnerable, or the full version string must lexically compare as earlier than 10.0.0.166(C00E66R1P11)Affected if Installed firmware version is any build number less than 10.0.0.166(C00E66R1P11), such as 10.0.0.165, 10.0.0.160, or earlier release branches
-
Check if device is on corporate or shared LANReview the network environment the Huawei P30 is connected to. Verify if the device is on the same local area network as untrusted or attacker-controlled devices, as the vulnerability is exploitable by attackers on the LANAffected if Device is connected to a LAN with untrusted or unknown devices present
The device is affected if it is a Huawei P30 running firmware version earlier than 10.0.0.166(C00E66R1P11) and is connected to a local network where an attacker could send specific commands.
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 data10.0.0.166
Update HUAWEI P30 firmware to version 10.0.0.166(C00E66R1P11) or later to remediate the vulnerability.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19441 — 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-2019-19441 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