dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-3799

HIGH · 8.7 CVSS v4.0 Published 2024-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Insecure handling of POST header parameter body included in requests being sent to an instance of the open-source project Phoniebox allows an attacker to create a website, which – when visited by a user – will send malicious requests to multiple hosts on the local network. If such a request reaches the server, it will cause a shell command execution. This issue affects Phoniebox in all releases through 2.7. Newer 2.x releases were not tested, but they might also be vulnerable. Phoniebox in version 3.0 and higher are not affected.

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

This is a command injection vulnerability in Phoniebox where the POST header parameter body is not properly sanitized before being used in shell command execution. An attacker can trick a user into visiting a malicious website that sends crafted requests to the Phoniebox server on the local network, leading to arbitrary shell command execution. This represents a Server-Side Request Forgery (SSRF) combined with remote code execution.

MitigationUpgrade to Phoniebox version 3.0 or higher, as versions through 2.7 and possibly newer 2.x releases are vulnerable. If upgrading is not feasible, implement strict input validation on all POST parameters and network isolation to limit exposure.

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
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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:X/AU:X/R:X/V:X/RE:X/U:X

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 installed Phoniebox version
    Check the version file, git tags, or the Phoniebox settings page (typically at /settings or /status) to determine the exact version number running on your system
    Affected if The version is 2.7 or any 2.x version below 3.0, as these are within the affected range stated in the summary
  2. Confirm web interface is enabled
    Verify that the Phoniebox web server (usually on port 80 or 8080) is running and accessible on the local network
    Affected if The web interface is active and accepts POST requests, which is required for the vulnerable code path to be reachable
  3. Locate the POST body parameter handler
    Examine the Phoniebox source code, specifically looking for route handlers that process POST requests and access the 'body' parameter without sanitization - typically in the web application's request handling modules
    Affected if Code exists that directly passes the POST 'body' parameter to shell execution functions (such as exec, shell_exec, or system calls) without input validation or escaping
  4. Check for input sanitization on POST parameters
    Review the application's input handling code to determine if functions like escapeshellarg or similar sanitization are applied to user-supplied POST data before shell command usage
    Affected if No sanitization functions are applied to the 'body' parameter before it is used in shell command construction

Your environment is affected if the installed Phoniebox version is below 3.0 and the web interface is accessible, as the vulnerable code path processes unsanitized POST 'body' parameter directly in shell commands.

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 Phoniebox version 3.0 or higher, as versions through 2.7 and possibly newer 2.x releases are vulnerable. If upgrading is not feasible, implement strict input validation on all POST parameters and network isolation to limit exposure.

Recommended fix Moderate confidence

version 3.0 or higher

  1. Back up the existing Phoniebox configuration and any custom audio files
  2. Review the Phoniebox upgrade documentation for your specific installation method (Raspbian/SSH, etc.)
  3. Upgrade the Phoniebox installation to version 3.0 or higher
  4. After upgrade, verify that the web interface is functional and the OS command injection vulnerability is no longer present by reviewing the code changes in the POST header handling
  5. Ensure all services are running correctly after the upgrade
Caveat Review release notes for version 3.0 to check for any breaking changes in configuration or functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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