dbcve.org
Spx Graphics ControllerApplication · Spx

CVE-2024-44623

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-16
Fix available
A fix is available. Upgrade to after 1.3.0 or later.
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
An issue in TuomoKu SPx-GC v.1.3.0 and before allows a remote attacker to execute arbitrary code via the child_process.js function.

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

A command injection vulnerability in the child_process.js function of TuomoKu SPx-GC v1.3.0 and prior allows remote unauthenticated attackers to execute arbitrary system commands by injecting malicious input into the function.

MitigationApply a patch if available from the vendor; otherwise, implement strict input validation and avoid passing unsanitized user input to child_process functions, or disable the vulnerable function until a fix is released.

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
Spx Graphics ControllerApplication
Affected:<= 1.3.0

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 if SPx Graphics Controller is installed
    Locate the SPx-GC application on the system by searching for its installation directory or checking for the service/process running under names related to 'SPx-GC', 'Spx Graphics Controller', or 'TuomoKu'.
    Affected if The application is present on the system.
  2. Determine the installed version
    Check the application's version information through its executable, configuration files, or by querying the running service. Common locations include the main binary, a version file in the installation directory, or the application startup output.
    Affected if The version is 1.3.0 or lower.
  3. Locate the child_process.js module
    Search the application installation directory for the file named 'child_process.js'. This may be found in the main application folder, a scripts directory, or a modules subdirectory.
    Affected if The file child_process.js exists in the SPx-GC installation directory.
  4. Verify the function is accessible to untrusted input
    Examine the application's configuration, exposed APIs, or network services to determine whether the child_process.js function can be reached by unauthenticated or external users. Check for exposed HTTP endpoints, API routes, or input pathways that could reach this function.
    Affected if The child_process.js function is exposed to network access or accepts input from untrusted sources without sanitization.

If SPx Graphics Controller version 1.3.0 or lower is installed and the child_process.js function is accessible to untrusted input, the environment is affected by this vulnerability.

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 a release after 1.3.0
Interim mitigation

Apply a patch if available from the vendor; otherwise, implement strict input validation and avoid passing unsanitized user input to child_process functions, or disable the vulnerable function until a fix is released.

Recommended fix Moderate confidence

Version 1.3.1 or later (verify on GitHub release page)

  1. 1. Check the official SPx Graphics Controller repository on GitHub for the latest release version
  2. 2. Verify if version 1.3.1 or higher contains the security fix for CVE-2024-44623
  3. 3. If a fixed version is available, download it from the official repository
  4. 4. Backup the current installation before upgrading
  5. 5. Replace the existing installation with the fixed version
  6. 6. Verify the child_process.js module no longer allows unsanitized input to be passed to execution functions
  7. 7. Test that the application functions normally after the upgrade
Caveat Check release notes for any breaking changes between 1.3.0 and the fixed version

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

Fix this in Spx Graphics Controller 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 the upgrade done

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-44623 — 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-44623 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