dbcve.org
Ips ModuleOperating system · Huawei

CVE-2018-7994

HIGH · 7.5 CVSS v3.0 Published 2018-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Some Huawei products IPS Module V500R001C50; NGFW Module V500R001C50; V500R002C10; NIP6300 V500R001C50; NIP6600 V500R001C50; NIP6800 V500R001C50; Secospace USG6600 V500R001C50; USG9500 V500R001C50 have a memory leak vulnerability. The software does not release allocated memory properly when processing Protal questionnaire. A remote attacker could send a lot questionnaires to the device, successful exploit could cause the device to reboot since running out of memory.

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

A memory leak vulnerability exists in Huawei IPS/NGFW modules and USG appliances where allocated memory is not properly released when processing Portal questionnaires. A remote attacker can send a high volume of Portal questionnaire requests to exhaust device memory, causing the device to reboot due to memory exhaustion.

MitigationApply vendor-supplied firmware patches for the affected versions (V500R001C50, V500R002C10). As an interim control, implement rate-limiting on Portal authentication traffic and monitor memory utilization on affected devices for anomalous consumption patterns.

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
Ips ModuleOperating system
Affected:= v500r001c50
Ngfw ModuleOperating system
Affected:= v500r001c50= v500r002c10
Nip6300Operating system
Affected:= v500r001c50
Nip6600Operating system
Affected:= v500r001c50
Nip6800Operating system
Affected:= v500r001c50
Secospace Usg6600Operating system
Affected:= v500r001c50
Usg9500Operating system
Affected:= v500r001c50

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

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

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

  1. Identify the device model
    Log into the device CLI and run 'display device' or 'display version' to confirm the exact model number (e.g., Nip6300, Nip6600, Nip6800, Secospace Usg6600, Usg9500)
    Affected if The model matches one of the affected products: Nip6300, Nip6600, Nip6800, Secospace Usg6600, or Usg9500
  2. Check the software version
    Run 'display version' in the device CLI to retrieve the firmware version. Look for version numbers such as V500R001C50 or V500R002C10
    Affected if The installed version is exactly V500R001C50 or V500R002C10 (note: version matching must be exact, as only these specific versions are affected)
  3. Verify if Portal authentication is enabled
    Run 'display portal interface' or 'display authentication portal' to check if Portal authentication is configured on any interface
    Affected if Portal authentication is enabled on the device, as the memory leak occurs specifically when processing Portal questionnaires
  4. Check current memory utilization
    Run 'display memory' or 'display memory-usage' to view current memory consumption. Monitor for abnormally high memory usage over time
    Affected if Memory usage is unusually high or continuously increasing without returning to baseline levels
  5. Review Portal authentication statistics
    Run 'display portal traffic-statistics' or check authentication logs for a high volume of Portal questionnaire requests
    Affected if There is a high volume of Portal questionnaire requests or abnormal authentication patterns

The device is affected if it is one of the listed models (Nip6300, Nip6600, Nip6800, Secospace Usg6600, Usg9500) running exactly version V500R001C50 or V500R002C10, and Portal authentication is enabled, which would allow the memory leak to be triggered by external Portal questionnaire requests.

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

Apply vendor-supplied firmware patches for the affected versions (V500R001C50, V500R002C10). As an interim control, implement rate-limiting on Portal authentication traffic and monitor memory utilization on affected devices for anomalous consumption patterns.

Fix this in Ips Module Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7994 — 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-2018-7994 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