CVE-2019-3415
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 · uneditedZTE MW NR8000V2.4.4.03 and NR8000V2.4.4.04 are impacted by path traversal vulnerability. Due to path traversal,users can download any files.
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 confidenceZTE MW NR8000 versions 2.4.4.03 and 2.4.4.04 contain a path traversal vulnerability in the file download functionality. This allows authenticated or unauthenticated users to manipulate file paths using '../' sequences to access and download arbitrary files from the device filesystem, potentially exposing sensitive configuration files, credentials, or system files.
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= 2.4.4.03= 2.4.4.04CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:L/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 the device modelAccess the device management interface or use SNMP/SSH to confirm the device is a ZTE MW NR8000. Check system information or device status page for model identification.Affected if The device model is ZTE MW NR8000 and matches the affected product line
-
Check the installed firmware versionAccess the device web interface, go to the system status or firmware information page, or use CLI commands such as 'show version' or 'system info' to retrieve the firmware version.Affected if The firmware version is exactly 2.4.4.03 or 2.4.4.04
-
Locate the file download functionalityIdentify if the device has a web-based file download or file transfer feature. Check the web interface for download/export functions, typically found in system maintenance, backup, or file management sections.Affected if The file download feature is present and accessible on the device
-
Verify path traversal accessibilityIf the file download function accepts a path parameter, test whether the interface accepts directory traversal sequences like '../' in the file path parameter. Check if the feature is exposed without authentication or with weak authentication.Affected if The file download parameter accepts '../' sequences or allows access outside the intended directory
You are affected if you have a ZTE MW NR8000 device running firmware version 2.4.4.03 or 2.4.4.04 with the file download functionality accessible and vulnerable to path manipulation.
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 dataUpgrade to a patched version provided by ZTE. Implement strict input validation on file path parameters to ensure only allowed directories can be accessed, use canonical path resolution, and deny any path containing traversal sequences.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3415 — 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-3415 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