dbcve.org
Vns3Application · Cohesive

CVE-2024-8809

HIGH · 8.8 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 6.2.8 / 6.6.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Cohesive Networks VNS3 Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Cohesive Networks VNS3. Authentication is required to exploit this vulnerability. The specific flaw exists within the web service, which listens on TCP port 8000 by default. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-24178.

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

Command injection vulnerability in Cohesive Networks VNS3's web service (TCP port 8000). Authenticated attackers can inject arbitrary OS commands through unsanitized user input that is passed directly to a system call, executing with root privileges.

MitigationApply vendor patch when available; if no patch, implement strict input validation/sanitization on all user-supplied parameters before system calls, and restrict network access to port 8000 to trusted IPs only.

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
Vns3Application
Affected:>= 4.6.1, < 6.2.8>= 6.6.0, < 6.6.7

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm VNS3 web service is exposed on TCP port 8000
    Run 'netstat -tlnp | grep :8000' or 'ss -tlnp | grep :8000' to check if the VNS3 web interface is listening on port 8000
    Affected if Port 8000 is open and the VNS3 web service is accessible on the network
  2. Identify installed VNS3 version
    Access the VNS3 web UI at https://<host>:8000 and check the version displayed in the web interface, or run 'vns3_version' command via the VNS3 client if available
    Affected if Version cannot be determined or is not visible in the web interface
  3. Compare installed version against affected ranges
    If version is obtained, verify it falls within: 4.6.1 <= version < 6.2.8 OR 6.6.0 <= version < 6.6.7
    Affected if Installed version matches one of the affected ranges
  4. Verify authentication is enabled for the web service
    Confirm the VNS3 web service requires authentication (username/password or API key) for access
    Affected if Web service allows unauthenticated access (this would actually expand the attack surface, though the CVE specifies authenticated attackers)
  5. Check for suspicious command execution indicators
    Review system logs (/var/log/messages, /var/log/syslog) and VNS3 audit logs for unusual commands, shell invocations, or unexpected API calls around the time of suspicious activity
    Affected if Evidence of arbitrary command execution that was not initiated by legitimate administrative actions

The environment is affected if VNS3 web service is running on port 8000 AND the installed version falls within 4.6.1-6.2.7 or 6.6.0-6.6.6.

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 6.2.8 / 6.6.7 or later
Fixed in 6.2.86.6.7
Interim mitigation

Apply vendor patch when available; if no patch, implement strict input validation/sanitization on all user-supplied parameters before system calls, and restrict network access to port 8000 to trusted IPs only.

Recommended fix High confidence

VNS3 6.6.7 (or 6.2.8 for the 6.2.x branch)

  1. Identify the currently installed VNS3 version using the web interface or system commands
  2. If running version 6.6.x and below 6.6.7, upgrade to VNS3 version 6.6.7 or later
  3. If running version 6.2.x and below 6.2.8, upgrade to VNS3 version 6.2.8 or later
  4. If running version 4.6.x and below 6.2.8, consider upgrading to the 6.2.8+ or 6.6.7+ branch
  5. After upgrade, verify the web service on TCP port 8000 is functioning correctly
  6. Confirm the vulnerability is resolved by reviewing release notes from Cohesive Networks
Caveat Review Cohesive Networks release notes for any configuration or feature changes between current and target version before upgrading

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

Fix this in Vns3 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-8809 — 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-8809 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