dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-40893

MEDIUM · 6.8 CVSS v3.1 Published 2024-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
Multiple authenticated operating system (OS) command injection vulnerabilities exist in Firewalla Box Software versions before 1.979. A physically close attacker that is authenticated to the Bluetooth Low-Energy (BTLE) interface can use the network configuration service to inject commands in various configuration parameters including networkConfig.Interface.Phy.Eth0.Extra.PingTestIP, networkConfig.Interface.Phy.Eth0.Extra.DNSTestDomain, and networkConfig.Interface.Phy.Eth0.Gateway6. Additionally, because the configuration can be synced to the Firewalla cloud, the attacker may be able to persist access even after hardware resets and firmware re-flashes.

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

Multiple authenticated OS command injection vulnerabilities exist in Firewalla Box Software versions before 1.979. A physically proximate attacker with BTLE authentication can inject OS commands through network configuration parameters (networkConfig.Interface.Phy.Eth0.Extra.PingTestIP, networkConfig.Interface.Phy.Eth0.Extra.DNSTestDomain, and networkConfig.Interface.Phy.Eth0.Gateway6). The attacker can persist access via cloud configuration sync even after hardware resets and firmware re-flashes.

MitigationUpgrade to Firewalla Box Software version 1.979 or later; consider disabling the BTLE interface if not required, and audit cloud-synced configurations for unauthorized changes.

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

CVSS:3.1/AV:A/AC:L/PR:H/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. Check the installed Firewalla Box software version
    Access the Firewalla web interface or run 'sudo firelog --version' via SSH to retrieve the current software version
    Affected if The installed version is before 1.979 (for example, 1.970, 1.950, etc.)
  2. Verify if BTLE interface is enabled
    Check the Firewalla settings interface or run 'hciconfig' via SSH to see if Bluetooth Low Energy is powered on and discoverable
    Affected if BTLE is enabled and accessible to a physically proximate attacker
  3. Inspect the PingTestIP network configuration parameter
    Query the network configuration via the Firewalla API or inspect the configuration file containing networkConfig.Interface.Phy.Eth0.Extra.PingTestIP
    Affected if This parameter contains arbitrary OS command strings rather than a valid IP address
  4. Inspect the DNSTestDomain network configuration parameter
    Query the network configuration via the Firewalla API or inspect the configuration file containing networkConfig.Interface.Phy.Eth0.Extra.DNSTestDomain
    Affected if This parameter contains arbitrary OS command strings rather than a valid DNS domain name
  5. Inspect the Gateway6 network configuration parameter
    Query the network configuration via the Firewalla API or inspect the configuration file containing networkConfig.Interface.Phy.Eth0.Gateway6
    Affected if This parameter contains arbitrary OS command strings rather than a valid IPv6 gateway address
  6. Check for unauthorized cloud configuration sync entries
    Review the cloud-synced configuration backup accessible through the Firewalla cloud interface for unexpected changes or persisted entries
    Affected if Unexpected configuration entries exist that were not set by the legitimate administrator

A user is affected if their Firewalla Box runs software version before 1.979, has BTLE enabled, and contains suspicious values in the three vulnerable network configuration parameters or unauthorized cloud sync entries.

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

Upgrade to Firewalla Box Software version 1.979 or later; consider disabling the BTLE interface if not required, and audit cloud-synced configurations for unauthorized changes.

Recommended fix Moderate confidence

Firewalla Box Software version 1.979 or later

  1. 1. Identify the current Firewalla Box Software version by accessing the Firewalla interface or checking system settings.
  2. 2. If the current version is before 1.979, download the latest firmware version from the official Firewalla support渠道 (typically via the Firewalla mobile app or web interface).
  3. 3. Apply the firmware update following Firewalla's standard upgrade procedure, ensuring stable power and network connectivity during the process.
  4. 4. After upgrading, verify the new version is 1.979 or later by checking the system information.
  5. 5. Since the vulnerability can persist via cloud sync, also review and reset any suspicious configurations in the Firewalla cloud dashboard to ensure no lingering malicious settings remain.
Caveat Review release notes for version 1.979 to check for any configuration or feature changes that may affect your deployment

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

Have this fixed 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 help mitigating

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-2024-40893 — 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-40893 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