Nodegrid OsOperating system · Zpesystems

CVE-2023-44037

HIGH · 7.5 CVSS v3.1 Published 2023-10-14
Fix available
A fix is available. Upgrade to 5.8.14 / 5.10.6 or later.
See remediation →
84/100
Remediation priority · High
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 ZPE Systems, Inc Nodegrid OS v.5.8.10 thru v.5.8.13 and v.5.10.3 thru v.5.10.5 allows a remote attacker to obtain sensitive information via the TACACS+ server component.

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 remote information disclosure vulnerability exists in the TACACS+ server component of ZPE Systems Nodegrid OS versions 5.8.10-5.8.13 and 5.10.3-5.10.5. An unauthenticated remote attacker can obtain sensitive information through the TACACS+ service, which is used for network authentication and authorization.

MitigationApply vendor-supplied patches for Nodegrid OS or upgrade to a patched version. If patches are unavailable, consider restricting network access to the TACACS+ service, disabling it if not required, and monitoring for unauthorized access attempts.

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
Nodegrid OsOperating system
Affected:>= 5.8.10, < 5.8.14>= 5.10.3, < 5.10.6

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Nodegrid OS version
    Access the system management interface or run 'show version' command via CLI to determine the installed Nodegrid OS version
    Affected if The displayed version falls within 5.8.10-5.8.13 or 5.10.3-5.10.5 (or is between 5.8.10 and 5.8.13, or between 5.10.3 and 5.10.5)
  2. Verify TACACS+ service status
    Access the Nodegrid administrative interface and navigate to Services or Authentication settings to confirm whether the TACACS+ server component is enabled
    Affected if The TACACS+ service is currently enabled or running on the system
  3. Confirm TACACS+ network accessibility
    Check network configuration to determine if the TACACS+ service port (typically TCP 49) is exposed to untrusted networks or is accessible from outside the local management network
    Affected if The TACACS+ service port is reachable from untrusted or external network segments

A user is affected if their Nodegrid OS version is within 5.8.10-5.8.13 or 5.10.3-5.10.5 AND the TACACS+ server component is enabled and network-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.

dbcve · scoped
Upgrade available Upgrade to 5.8.14 / 5.10.6 or later
Fixed in 5.8.145.10.6
Interim mitigation

Apply vendor-supplied patches for Nodegrid OS or upgrade to a patched version. If patches are unavailable, consider restricting network access to the TACACS+ service, disabling it if not required, and monitoring for unauthorized access attempts.

Recommended fix High confidence

Nodegrid OS 5.8.14 (for 5.8.x branch) or Nodegrid OS 5.10.6 (for 5.10.x branch)

  1. 1. Identify the current Nodegrid OS version by checking the system settings or running 'show version' command
  2. 2. If running version 5.8.10 through 5.8.13, plan upgrade to version 5.8.14
  3. 3. If running version 5.10.3 through 5.10.5, plan upgrade to version 5.10.6
  4. 4. Schedule maintenance window as upgrade may require reboot
  5. 5. Perform upgrade via the Nodegrid admin interface or appropriate upgrade mechanism
  6. 6. After upgrade, verify the new version is installed and running
  7. 7. Verify TACACS+ server functionality is operational post-upgrade

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

Fix this in Nodegrid Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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