dbcve.org
Nvr 504 FirmwareOperating system · Systemk Corp

CVE-2023-7227

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-25
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
SystemK NVR 504/508/516 versions 2.3.5SK.30084998 and prior are vulnerable to a command injection vulnerability in the dynamic domain name system (DDNS) settings that could allow an attacker to execute arbitrary commands with root privileges.

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

SystemK NVR 504/508/516 devices running firmware version 2.3.5SK.30084998 and prior contain a command injection vulnerability in the DDNS (Dynamic DNS) settings functionality. Attackers can inject arbitrary OS commands through unsanitized DDNS configuration parameters, which are then executed with root privileges on the underlying Linux-based NVR system.

MitigationUpgrade the SystemK NVR firmware to version 2.3.5SK.30084998 or later. If no patch is available from the vendor, consider network isolating the affected devices and restricting management interface access to trusted IP addresses as compensating controls.

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
Nvr 504 FirmwareOperating system
Affected:= 2.3.5sk.30084998
Nvr 508 FirmwareOperating system
Affected:= 2.3.5sk.30084998
Nvr 516 FirmwareOperating system
Affected:= 2.3.5sk.30084998

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. Identify the NVR device model
    Access the NVR management interface and navigate to System > Device Information or check the physical device label to confirm the model is NVR 504, NVR 508, or NVR 516.
    Affected if The device is a SystemK Corp NVR 504, NVR 508, or NVR 516.
  2. Check the installed firmware version
    In the NVR web interface, go to System > System Information or Maintenance > Version Info to view the firmware version. Compare it against the affected version 2.3.5SK.30084998 or earlier.
    Affected if The firmware version is 2.3.5SK.30084998 or any version prior to it.
  3. Determine if DDNS is enabled
    In the NVR web interface, navigate to Network > DDNS or Remote Access > DDNS settings. Check whether the DDNS feature is currently enabled or configured.
    Affected if DDNS is enabled and configured on the device.
  4. Inspect DDNS configuration parameters
    In the DDNS settings page, examine the DDNS provider, hostname, username, and password fields for any unexpected or suspicious values that may indicate prior exploitation.
    Affected if DDNS parameters contain unusual characters, external IP addresses, or strings that resemble shell commands.
  5. Verify network exposure of the management interface
    Check if the NVR management web interface (typically ports 80/443 or 8080) is accessible from untrusted networks by reviewing firewall rules or performing a port scan from an external IP.
    Affected if The NVR management interface is exposed to the internet or untrusted networks without restriction.

The device is affected if it is a SystemK NVR 504/508/516 running firmware version 2.3.5SK.30084998 or earlier with DDNS functionality enabled and accessible.

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

Upgrade the SystemK NVR firmware to version 2.3.5SK.30084998 or later. If no patch is available from the vendor, consider network isolating the affected devices and restricting management interface access to trusted IP addresses as compensating controls.

Fix this in Nvr 504 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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