dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-4999

CRITICAL · 9.4 CVSS v4.0 Published 2024-05-16
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 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
A vulnerability in the web-based management interface of multiple Ligowave devices could allow an authenticated remote attacker to execute arbitrary commands with elevated privileges.This issue affects UNITY: through 6.95-2; PRO: through 6.95-1.Rt3883; MIMO: through 6.95-1.Rt2880; APC Propeller: through 2-5.95-4.Rt3352.

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

Authenticated command injection vulnerability in Ligowave device web management interfaces. An attacker with valid credentials can execute arbitrary operating system commands with elevated (root) privileges through the web interface, affecting UNITY (through 6.95-2), PRO (through 6.95-1.Rt3883), MIMO (through 6.95-1.Rt2880), and APC Propeller (through 2-5.95-4.Rt3352) firmware versions.

MitigationApply vendor firmware updates when available. Until patched, restrict web management interface access to trusted IP addresses only via firewall rules, or disable web management if unnecessary.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Authentication
Y
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:U/V:D/RE:M/U:Amber

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 Ligowave device model
    Log into the device web interface or check the device label/documentation to determine the product line (UNITY, PRO, MIMO, or APC Propeller)
    Affected if Device is a Ligowave product in one of the affected product lines
  2. Check installed firmware version
    Access the web management interface System or Status page to view the firmware version, or use the device CLI command 'cat /proc/version' or check the firmware file name
    Affected if Firmware version is at or below the affected version for your product line (UNITY: 6.95-2, PRO: 6.95-1.Rt3883, MIMO: 6.95-1.Rt2880, APC Propeller: 2-5.95-4.Rt3352)
  3. Verify web management interface is enabled
    Check the device configuration under Network or Management settings to confirm the web interface (HTTP/HTTPS) is turned on
    Affected if Web management interface is enabled and accessible
  4. Check web management exposure
    Review firewall rules or network configuration to determine if the web interface is exposed to untrusted networks or the internet
    Affected if Web management is accessible from untrusted networks or directly from the internet

Your device is affected if it is a Ligowave UNITY, PRO, MIMO, or APC Propeller model running firmware at or below the specified version with the web management interface 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available. Until patched, restrict web management interface access to trusted IP addresses only via firewall rules, or disable web management if unnecessary.

Recommended fix Moderate confidence

Firmware version newer than 6.95-2 for UNITY, newer than 6.95-1 for PRO/MIMO, and newer than 2-5.95-4 for APC Propeller (contact vendor for exact patched releases)

  1. 1. Identify the exact Ligowave device model (UNITY, PRO, MIMO, or APC Propeller) from the affected hardware
  2. 2. Access the device's web-based management interface using administrative credentials
  3. 3. Navigate to the firmware upgrade section (typically under System, Administration, or Maintenance menu)
  4. 4. Download the latest firmware version from the official Ligowave support website (ligowave.com/support)
  5. 5. Upload and apply the firmware update following the on-screen instructions
  6. 6. After reboot, verify the new firmware version is installed and the device is functioning normally
  7. 7. Confirm the vulnerability is remediated by checking that the command injection vector is no longer exploitable
Caveat Standard firmware upgrade risks apply - ensure backup of configuration before upgrading, and plan for brief downtime during the update process

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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