CVE-2024-3955
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 · uneditedURL GET parameter "logtime" utilized within the "downloadlog" function from "cbpi/http_endpoints/http_system.py" is subsequently passed to the "os.system" function in "cbpi/controller/system_controller.py" without prior validation allowing to execute arbitrary code.This issue affects CraftBeerPi 4: from 4.0.0.58 (commit 563fae9) before 4.4.1.a1 (commit 57572c7).
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 confidenceA command injection vulnerability exists in CraftBeerPi 4 where the 'logtime' GET parameter from the /downloadlog endpoint is passed directly to os.system() without any input validation or sanitization, allowing attackers to execute arbitrary system commands.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm CraftBeerPi 4 is installedIdentify the CraftBeerPi installation by checking for the web application process, the installation directory, or by accessing the web interfaceAffected if CraftBeerPi 4 is found running in the environment
-
Check the installed CraftBeerPi versionLocate and read the version file or check the package version (e.g., in setup.py, requirements.txt, or the application's version module)Affected if The version is earlier than 4.4.1.a1 (any 4.x.x version before 4.4.1.a1)
-
Verify the /downloadlog endpoint existsAttempt to access the /downloadlog endpoint on the CraftBeerPi web server (e.g., http://<host>/downloadlog)Affected if The endpoint responds, indicating it is exposed
-
Test if the logtime parameter is processedSend a benign GET request to /downloadlog?logtime=test and observe if the parameter is processed or returned in the responseAffected if The parameter is accepted and processed by the application
-
Confirm os.system() usage in the downloadlog handlerReview the source code of the /downloadlog endpoint handler (typically in a routes or controller file) to verify that the logtime parameter is passed to os.system() without sanitizationAffected if The code shows logtime parameter being passed directly to os.system()
The environment is affected if CraftBeerPi 4 version is earlier than 4.4.1.a1 AND the /downloadlog endpoint with the logtime parameter is accessible and passes the input unsanitized to os.system().
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.
dbcve · scopedUpgrade to CraftBeerPi 4.4.1.a1 or later. Until patched, restrict network access to the CraftBeerPi web interface and implement Web Application Firewall rules to detect and block command injection patterns in URL parameters.
4.4.1.a1
- Backup the current CraftBeerPi installation and configuration
- Update CraftBeerPi to version 4.4.1.a1 (commit 57572c7) or later
- Restart the CraftBeerPi service to apply the changes
- Verify the upgrade was successful by checking the version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3955 — 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-3955 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