dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-3798

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 GET header parameter file 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 one of the following (depending on the chosen payload): shell command execution, reflected XSS or cross-site request forgery. 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 an SSRF (Server-Side Request Forgery) vulnerability in Phoniebox where GET header parameters are not validated, allowing attackers to craft malicious links that cause the server to make arbitrary requests to internal network hosts. This can lead to shell command execution, reflected XSS, or CSRF attacks.

MitigationUpgrade to Phoniebox version 3.0 or later. If upgrading is not feasible, disable external network access to the instance and implement strict input validation on all header parameters.

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:L/SI:L/SA:L/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. Locate Phoniebox installation directory
    Search for Phoniebox directories such as /var/www/phoniebox, /home/pi/phoniebox, or the installation path used during setup. Check for the presence of known Phoniebox files like index.php, config.php, or the 'web' subfolder.
    Affected if Phoniebox is installed but the directory cannot be found for version checking.
  2. Determine installed Phoniebox version
    Check for a version file in the Phoniebox directory (commonly VERSION, version.txt, or similar). If not present, examine the git tags if it was installed from source, or check the package manager if installed via apt or pip.
    Affected if The version is found to be below 3.0 (e.g., 2.x, 1.x) or the version cannot be determined and the software appears to be an older installation.
  3. Verify web interface is accessible
    Confirm that the Phoniebox web interface is running and reachable via HTTP/HTTPS on the expected port (commonly port 80, 8080, or the configured web server port). Use curl or a browser to test access.
    Affected if The web interface is exposed and GET requests can be made to the application endpoints.
  4. Inspect GET header handling behavior
    Review the PHP source code in the web directory for code that processes GET header parameters without validation. Look for uses of $_GET or $_REQUEST that are used in network requests, file includes, or command construction.
    Affected if Code exists that processes GET parameters from headers and uses them in requests without sanitization or validation checks.

A user is affected if their Phoniebox installation is version 2.x or earlier and the web interface is accessible, allowing unauthenticated GET header parameters to trigger arbitrary server requests.

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 later. If upgrading is not feasible, disable external network access to the instance and implement strict input validation on all header parameters.

Recommended fix High confidence

3.0 or later (any 3.x release)

  1. Backup the current Phoniebox installation and configuration
  2. Upgrade Phoniebox to version 3.0 or later by following the project's official upgrade instructions
  3. After upgrade, verify the installation is working correctly and the vulnerable endpoint is no longer exposed
  4. Test that legitimate functionality (playing audio, etc.) still works as expected
Caveat Major version upgrades may introduce breaking changes; review the project's release notes for migration details

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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-3798 — 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-3798 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