CVE-2024-8684
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 · uneditedOS Command Injection vulnerability in Revolution Pi version 2022-07-28-revpi-buster from KUNBUS GmbH. This vulnerability could allow an authenticated attacker to execute OS commands on the device via the ‘php/dal.php’ endpoint, in the ‘arrSaveConfig’ parameter.
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 confidenceOS Command Injection vulnerability in Revolution Pi firmware 2022-07-28-revpi-buster allows authenticated attackers to execute arbitrary operating system commands through the 'arrSaveConfig' parameter in the 'php/dal.php' endpoint. The application fails to properly sanitize user input before passing it to shell execution functions.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Revolution Pi deviceCheck if the target system is a Revolution Pi industrial IoT device by examining system information: cat /proc/cpuinfo (look for 'Revolution Pi' or 'RevPi' in hardware info) or check for /etc/revpi/* release filesAffected if System is not a Revolution Pi device, then not affected by this specific CVE
-
Determine firmware versionCheck the firmware version by reading /etc/revpi/image-release or /var/log/revpi*.log, or use command 'dpkg -l | grep revpi' if using Debian packagesAffected if Firmware version is older than or equal to the 2022-07-28-revpi-buster release, indicating it may contain the vulnerable code
-
Locate vulnerable PHP fileCheck if the file php/dal.php exists on the web server: locate dal.php or find /var/www -name dal.php 2>/dev/nullAffected if The file php/dal.php does not exist on the system, suggesting the vulnerability is not present
-
Check if web interface is exposedVerify if the PHP endpoint is accessible by testing HTTP/HTTPS access to the /php/dal.php path on the device's web server (typically on port 80/443 or custom port)Affected if The web interface is not accessible or the php/dal.php endpoint returns 404, reducing likelihood of exploitation
-
Verify authentication requirementsReview web server access logs or configuration to confirm if the php/dal.php endpoint requires authentication (check .htaccess, nginx auth requirements, or PHP session handling)Affected if The endpoint is publicly accessible without authentication, increasing exposure to the command injection flaw
A system is likely affected if it is a Revolution Pi device running firmware at or before the 2022-07-28-revpi-buster version with the php/dal.php endpoint accessible, particularly without proper authentication controls.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor firmware update when available; alternatively, implement strict input validation and avoid direct shell command execution in the affected PHP code. Network segmentation and limiting authentication exposure can reduce attack surface until patched.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-8684 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8684 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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