CVE-2016-3675
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 · uneditedSQL injection vulnerability in Huawei Policy Center with software before V100R003C10SPC020 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors related to system databases.
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 confidenceSQL injection vulnerability in Huawei Policy Center allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors in system databases. The vulnerability affects versions prior to V100R003C10SPC020. Successful exploitation could allow an attacker to read, modify, or delete database contents including sensitive system data.
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= v100r003c00= v100r003c10CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Huawei Policy Center is installedCheck system information or firmware documentation to identify if the Huawei Policy Center product is deployed. Look for product name, model, or firmware files.Affected if The system runs Huawei Policy Center firmware.
-
Identify the installed firmware versionAccess the device management interface or check system files for the firmware version. Typically found in system status, about page, or by running 'display version' command if CLI access is available.Affected if The installed version is v100r003c00 or v100r003c10, or any version prior to V100R003C10SPC020.
-
Verify database management access is availableCheck if the system database functionality is accessible to authenticated users. This may involve reviewing user role permissions, database management interfaces, or system configuration for database-related features.Affected if Authenticated users have access to system database functions or SQL-executable interfaces.
-
Confirm network accessibility of management interfaceDetermine if the Policy Center management interface is network-accessible. Check firewall rules, interface bindings, and access control lists.Affected if The management interface is accessible from network segments where untrusted users could authenticate.
A user is affected if Huawei Policy Center is running firmware version v100r003c00 or v100r003c10 (or any version prior to V100R003C10SPC020) and authenticated users can access system database functionality.
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 dataUpdate Huawei Policy Center to version V100R003C10SPC020 or later to patch the SQL injection vulnerability. If immediate patching is not feasible, restrict the number of authenticated users with access to the system and implement database-level input validation as a temporary control.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3675 — 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-2016-3675 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