dbcve.org
Network Computer Terminal Protection System FirmwareOperating system · Sun Moon Jingyao

CVE-2021-45917

CRITICAL · 9.0 CVSS v3.1 Published 2022-01-03
Fix available
A fix is available. Upgrade to 7.20.0401 or later.
See remediation →
92/100
Remediation priority · Urgent
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
The server-request receiver function of Shockwall system has an improper authentication vulnerability. An authenticated attacker of an agent computer within the local area network can use the local registry information to launch server-side request forgery (SSRF) attack on another agent computer, resulting in arbitrary code execution for controlling the system or disrupting service.

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

The Shockwall server-request receiver function contains an improper authentication vulnerability that allows an authenticated attacker on a LAN agent computer to leverage local registry information to perform SSRF attacks against other agent computers, leading to arbitrary code execution.

MitigationImplement proper authentication validation and authorization checks in the server-request receiver function, add SSRF protections, and restrict registry access permissions for agent processes.

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
Network Computer Terminal Protection System FirmwareOperating system
Affected:< 7.20.0401

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/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 if Sun Moon Jingyao Network Computer Terminal Protection System is installed
    Check system for presence of the Sun Moon Jingyao Network Computer Terminal Protection System software or service
    Affected if The product is not installed or has been removed, the system is not affected; if installed, continue to version check
  2. Check the installed firmware version
    Locate the version information for the Sun Moon Jingyao Network Computer Terminal Protection System and compare it against 7.20.0401
    Affected if The installed version is lower than 7.20.0401 (for example, 7.20.0300 or any version below 7.20.0401), the vulnerability is present
  3. Verify if the server-request receiver function is enabled
    Inspect the system configuration or service settings to determine whether the server-request receiver function is active and accessible
    Affected if The server-request receiver function is enabled and exposed, the attack surface exists for exploitation
  4. Check agent process registry access permissions
    Examine registry key permissions for the agent processes to determine if they allow unrestricted access from authenticated local users
    Affected if Registry access permissions are not properly restricted, an authenticated attacker could leverage registry information for SSRF attacks

A system is affected if it runs Sun Moon Jingyao Network Computer Terminal Protection System with firmware version below 7.20.0401, has the server-request receiver function enabled, and contains misconfigured registry permissions that permit authenticated local users to access agent registry data.

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
Upgrade available Upgrade to 7.20.0401 or later
Fixed in 7.20.0401
Interim mitigation

Implement proper authentication validation and authorization checks in the server-request receiver function, add SSRF protections, and restrict registry access permissions for agent processes.

Recommended fix High confidence

Firmware version 7.20.0401 or later

  1. Identify the current firmware version of the Network Computer Terminal Protection System (Shockwall)
  2. Download the updated firmware version 7.20.0401 or later from the official vendor source
  3. Review the vendor's firmware upgrade instructions and ensure proper backup of current configuration
  4. Upload and install the firmware update through the system's administrative interface
  5. Verify the firmware was successfully applied by checking the version number
  6. Restart the system if required by the upgrade procedure
  7. Confirm the vulnerability is remediated by verifying the server-request receiver function now properly authenticates requests

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

Fix this in Network Computer Terminal Protection System Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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