Sc 6000 E3960 FirmwareOperating system · Hillstonenet

CVE-2023-46964

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
Cross Site Scripting (XSS) vulnerability in Hillstone Next Generation FireWall SG-6000-e3960 v.5.5 allows a remote attacker to execute arbitrary code via the use front-end filtering instead of back-end filtering.

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 confidence

Cross-Site Scripting (XSS) vulnerability in Hillstone SG-6000-e3960 firewall web interface allows remote attackers to inject malicious scripts through front-end filtering that should be handled server-side. The issue stems from the web management interface not properly sanitizing user inputs before rendering them, enabling arbitrary code execution in victim browsers.

MitigationImplement proper server-side (back-end) input validation and output encoding for all user-supplied data in the web interface. Ensure all user inputs are sanitized on the server before being rendered back to users.

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
Sc 6000 E3960 FirmwareOperating system
Affected:= 5.5

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

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

  1. Identify the firewall device model
    Access the device console or SSH interface and run: `show system info` or `get system status` to confirm the device is a Hillstone SG-6000-e3960 model
    Affected if Device model is Hillstone SG-6000-e3960
  2. Check the firmware version
    Run: `show version` or `get system version` on the device CLI to retrieve the installed firmware version number
    Affected if Firmware version is 5.5 (exact match)
  3. Verify web management interface is enabled
    Run: `show web-ui status` or check the HTTP/HTTPS service configuration via `show http server` or `show https server`
    Affected if Web management interface (HTTP or HTTPS) is enabled and accessible
  4. Confirm remote access is permitted
    Check management interface binding: `show management-interface` or review access control lists that determine if the web UI is exposed to untrusted networks
    Affected if Web interface is reachable from network segments outside the trusted management network

You are affected if you have a Hillstone SG-6000-e3960 device running firmware version 5.5 with the web management interface enabled and accessible to the network where attackers could inject malicious scripts.

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 proper server-side (back-end) input validation and output encoding for all user-supplied data in the web interface. Ensure all user inputs are sanitized on the server before being rendered back to users.

Fix this in Sc 6000 E3960 Firmware 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-2023-46964 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46964 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