dbcve.org
Web Application FirewallApplication · Hillstonenet

CVE-2024-8073

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Input Validation vulnerability in Hillstone Networks Hillstone Networks Web Application Firewall on 5.5R6 allows Command Injection.This issue affects Hillstone Networks Web Application Firewall: from 5.5R6-2.6.7 through 5.5R6-2.8.13.

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

Improper input validation in Hillstone Networks Web Application Firewall (versions 5.5R6-2.6.7 through 5.5R6-2.8.13) allows remote attackers to inject and execute arbitrary operating system commands due to insufficient validation of user-supplied input before passing it to system calls.

MitigationApply vendor patches or upgrade to a non-vulnerable version. As a temporary measure, restrict management interface access to trusted networks only and disable unnecessary administrative access paths.

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
Web Application FirewallApplication
Affected:= 5.5r6-2.6.7= 5.5r6-2.8.13

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
High
Integrity
High
Availability
High

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

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

  1. Confirm Hillstone Networks WAF is installed
    Access the WAF management interface or check system inventory for Hillstonenet Web Application Firewall
    Affected if The product is Hillstone Networks WAF
  2. Identify the installed WAF version
    Log into the WAF admin interface and navigate to System > About, or check the version via CLI if available
    Affected if The displayed version falls between 5.5R6-2.6.7 and 5.5R6-2.8.13 inclusive
  3. Verify the management interface is network-accessible
    Attempt to reach the WAF web interface from an external network location, or review firewall rules allowing HTTP/HTTPS to the WAF IP
    Affected if The WAF management interface is reachable from untrusted networks (e.g., internet or shared subnets)
  4. Check for existing network access controls on the WAF
    Review firewall or ACL configurations restricting access to the WAF management ports (typically 443, 8443) to trusted IP ranges only
    Affected if No IP-based restrictions exist and the management interface is publicly accessible

You are affected if Hillstone Networks WAF is running and its version is between 5.5R6-2.6.7 and 5.5R6-2.8.13, especially if the management interface is accessible from untrusted networks.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches or upgrade to a non-vulnerable version. As a temporary measure, restrict management interface access to trusted networks only and disable unnecessary administrative access paths.

Recommended fix Moderate confidence

Upgrade to a version higher than 5.5R6-2.8.13 (contact Hillstone Networks for the exact fixed release)

  1. 1. Identify the current installed version of Hillstone Networks Web Application Firewall by accessing the admin console or checking system information.
  2. 2. Confirm the installed version is within the affected range: 5.5R6-2.6.7 through 5.5R6-2.8.13.
  3. 3. Contact Hillstone Networks support or visit their official support portal at www.hillstonenet.com.cn to obtain the latest stable version that includes the security fix for CVE-2024-8073.
  4. 4. Review the upgrade documentation and release notes for the target version to understand any prerequisites or configuration changes required.
  5. 5. Schedule a maintenance window and perform a full backup of the current WAF configuration.
  6. 6. Apply the upgrade following the official Hillstone Networks upgrade procedure.
  7. 7. After upgrade, verify the new version is running and confirm the vulnerability is remediated.
Caveat Review release notes for any configuration or compatibility changes between current and target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Web Application Firewall Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

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