CVE-2019-5277
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 CloudUSM-EUA V600R006C10;V600R019C00 have an information leak vulnerability. Due to improper configuration, the attacker may cause information leak by successful exploitation.
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 CloudUSM-EUA versions V600R006C10 and V600R019C00 contain an information leak vulnerability caused by improper configuration. Successful exploitation allows an attacker to gain unauthorized access to sensitive information stored or processed by the system. The CVSS 7.5 indicates network-exploitable with low attack complexity and no authentication required.
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= v600r006c10= v600r019c00CVSS 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
- None
CVSS:3.1/AV:N/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.
-
Identify Huawei CloudUSM-EUA installationLocate the Huawei CloudUSM-EUA appliance or software in your environment. Check system inventory, network scans, or documentation for presence of this product.Affected if Huawei CloudUSM-EUA is present in the environment
-
Determine installed firmware versionAccess the device management interface or system settings. Look for version information typically displayed in About, System Info, or Firmware sections. Use CLI commands such as 'display version' or check firmware file naming if accessible.Affected if Version is V600R006C10 or V600R019C00 exactly
-
Verify configuration exposure settingsExamine system configuration files or management interface settings related to access controls, user permissions, file sharing, or API access. Look for configurations that may allow unauthorized information access or directory traversal settings.Affected if Misconfigured access controls or exposed sensitive configuration settings are found
-
Check network accessibilityDetermine if the CloudUSM-EUA management interface or API endpoints are exposed to untrusted networks. Review firewall rules, NAT configurations, and ACLs applied to the device.Affected if Service is accessible from untrusted networks without proper authentication barriers
-
Review audit and access logsExamine system logs, access logs, or security event logs for unauthorized access attempts or successful connections from unexpected sources. Check for indicators of information leakage patterns.Affected if Logs show unauthorized access or anomalous data access patterns originating from external sources
User is affected if Huawei CloudUSM-EUA firmware version V600R006C10 or V600R019C00 is deployed and the system configuration allows unauthorized access to sensitive information from untrusted networks.
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 dataReview and remediate the improper configuration per Huawei security advisories; apply any available patches or updates to the affected versions. If patches are unavailable, implement compensating controls such as network segmentation and strict access controls.
- 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-2019-5277 — 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-5277 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