CVE-2017-15313
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 SmartCare V200R003C10 has a CSV injection vulnerability. An remote authenticated attacker could inject malicious CSV expression to the affected device.
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 confidenceCSV injection vulnerability in Huawei SmartCare V200R003C10 allows authenticated remote attackers to inject malicious spreadsheet formulas (e.g., =, +, -, @ commands) into CSV exports. When users open these exported CSV files in spreadsheet software, the injected formulas can execute arbitrary commands or exfiltrate data from the victim's system.
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= v200r003c10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Huawei SmartCare installation and versionLocate the SmartCare application or check system inventory for Huawei SmartCare software and retrieve its version number (typically via 'about' or 'system info' menu, or command line: 'show version' or similar)Affected if The installed version matches v200r003c10 exactly or is earlier (v200r003c10 and prior)
-
Confirm CSV export functionality existsAccess the SmartCare web interface or administrative console and locate any feature that exports data to CSV format (commonly under reports, logs, data export, or user data sections)Affected if CSV export feature is present and accessible to authenticated users
-
Check for suspicious CSV files in export directoriesSearch the SmartCare server file system for CSV files, particularly in export, download, temp, or report directories. Inspect recent CSV files for cells beginning with =, +, -, @, or tab characters followed by formula-like contentAffected if Any CSV files contain cells starting with formula-initiating characters (=, +, -, @) rather than plain data
You are affected if Huawei SmartCare v200r003c10 is installed and the CSV export feature is accessible to authenticated users, as attackers with valid credentials can inject and export malicious spreadsheet formulas.
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 strict input validation and sanitization for all user-supplied data before CSV export; apply available vendor patches from Huawei; consider disabling spreadsheet formula interpretation in CSV exports by prefixing data fields with a single quote or tab character.
- 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-2017-15313 — 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-2017-15313 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