dbcve.org
FusionmanagerApplication · Huawei

CVE-2014-9136

HIGH · 8.8 CVSS v3.0 Published 2017-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Huawei FusionManager with software V100R002C03 and V100R003C00 could allow an unauthenticated, remote attacker to conduct a CSRF attack against the user of the web interface.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in Huawei FusionManager web interface versions V100R002C03 and V100R003C00. An unauthenticated remote attacker can craft malicious links or pages that, when visited by an authenticated user, cause the user's browser to perform unintended actions on the FusionManager web interface without the user's knowledge or consent.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing forms and validate them server-side; also implement Referer/Origin header validation and SameSite cookie attributes. Check with Huawei for official patches for these versions.

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
FusionmanagerApplication
Affected:<= v100r002c03<= v100r003c00
Usg9500 FirmwareOperating system
Affected:<= v200r001c01spc800<= v300r001c00
Usg2100 FirmwareOperating system
Affected:<= v300r001c00spc900
Usg2200 FirmwareOperating system
Affected:<= v300r001c00spc900
Usg5100 FirmwareOperating system
Affected:<= v300r001c00spc900
Usg5500 FirmwareOperating system
Affected:<= v300r001c00spc900

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify product and version
    Access the device's web interface or use command line (display version) to determine if the system is running FusionManager or USG firmware, and note the exact version number
    Affected if The installed version matches Huawei FusionManager <= v100r002c03 or <= v100r003c00, or any USG firmware version listed in the affected ranges
  2. Confirm web interface is enabled
    Check if the FusionManager or USG web management interface is accessible by navigating to the management URL (typically https://IP:8443 for FusionManager or standard HTTPS port for USG devices)
    Affected if The web interface is exposed and accessible to users
  3. Inspect forms for anti-CSRF tokens
    Log into the web interface, navigate to state-changing forms (such as user management, system settings, or configuration pages), and view the page source or inspect form elements to verify if hidden token fields or anti-CSRF tokens are present
    Affected if State-changing forms lack hidden anti-CSRF token fields or the tokens are not validated server-side
  4. Check Referer/Origin header handling
    Submit a request to a state-changing action from an external or mismatched Referer/Origin header and observe whether the request is allowed or rejected by the server
    Affected if The server accepts state-changing requests without validating the Referer or Origin header
  5. Verify SameSite cookie attributes
    Using browser developer tools or a proxy, capture a login session cookie and inspect the Set-Cookie headers to check if the SameSite attribute is set
    Affected if Session cookies do not have the SameSite attribute set, or SameSite is set to None without Secure flag

A user is affected if their environment runs any of the listed Huawei product versions AND the web interface lacks anti-CSRF token validation, Referer/Origin header checks, and SameSite cookie attributes on session cookies.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing forms and validate them server-side; also implement Referer/Origin header validation and SameSite cookie attributes. Check with Huawei for official patches for these versions.

Fix this in Fusionmanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-9136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-9136 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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