CVE-2019-5247
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 Atlas 300, Atlas 500 have a buffer overflow vulnerability. A local, authenticated attacker may craft specific parameter and send to the process to exploit this vulnerability. Successfully exploit may cause service crash.
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 · high confidenceBuffer overflow vulnerability in Huawei Atlas 300 and Atlas 500 AI accelerator products. A local, authenticated attacker can send specially crafted parameters to a specific process, triggering a buffer overflow that causes a denial of service (service crash).
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>= 1.0.0, < 1.0.0.spc102>= 1.0.0, < 1.0.0.spc102CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 model and firmware versionAccess the device management interface or use the CLI command to query the firmware version (e.g., 'show version' or through the device's web UI under System > Device Info).Affected if The device is a Huawei Atlas 300 or Atlas 500 with firmware version 1.0.0 or higher but lower than 1.0.0.spc102.
-
Confirm the vulnerable process is runningUse the device CLI or management interface to list running processes. Look for the specific process that handles parameter input and is susceptible to the buffer overflow (typically identified in device documentation or vendor advisories).Affected if The vulnerable process is active and accepting external parameters.
-
Check for service crash indicatorsReview system logs or crash dump files for recent service crashes related to the affected process. Use commands like 'show log' or check /var/log/ directories if accessible via CLI.Affected if There are recent crash logs or service restart events for the process that handles the vulnerable parameter input.
-
Verify access controls on the deviceReview user accounts and authentication settings on the device to determine if untrusted local users have authenticated access. Check admin/user privilege assignments.Affected if Multiple untrusted users have local authenticated access to the device.
A user is affected if they are running Huawei Atlas 300 or Atlas 500 firmware versions between 1.0.0 and 1.0.0.spc102 (exclusive), with the vulnerable process exposed to local authenticated attackers.
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 data1.0.0.spc102
Apply vendor security patches when available. Until patched, restrict physical and logical access to trusted administrators only, and monitor for suspicious process interaction attempts.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5247 — 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-5247 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