CVE-2024-47916
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 · uneditedBoa web server - CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
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 · moderate confidenceA path traversal vulnerability exists in the Boa web server that allows attackers to access files outside the web root directory by manipulating file paths with sequences like '../'. This improper limitation of pathname to restricted directory (CWE-22) could allow unauthorized file system access.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 if Boa web server is runningCheck running processes for 'boa' or examine web server configurations for references to Boa. Look for process list or service status that mentions boa.Affected if Boa web server is not present in the environment, the vulnerability does not apply.
-
Determine the installed Boa versionRun 'boa -v' or 'boa --version' if available, or check package manager output (dpkg -l, rpm -qa) for boa packages, or inspect binary metadata.Affected if The installed version matches or falls within an affected version range for CVE-2024-47916.
-
Verify file serving functionality is enabledExamine Boa configuration file (commonly boa.conf) for directives that enable file serving, such as 'DocumentRoot', 'Directory', or alias mappings that serve files from the filesystem.Affected if File serving from the filesystem is enabled and the web server processes user-supplied paths.
-
Check for vulnerable path handling in configurationsReview Boa config for any path-handling directives that accept user input without sanitization, or test with a benign path traversal request (e.g., ../../etc/passwd) if safe to do so in a test environment.Affected if User-supplied file paths can reach the filesystem without canonicalization or validation checks.
Environment is affected if Boa web server is running with a vulnerable version and file serving from the filesystem is enabled, allowing user-controlled paths to reach disk operations.
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 dataImplement strict input validation and path canonicalization to ensure user-supplied file paths are restricted to the intended directory. Use functions that resolve and validate the full path before file access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47916 — 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-47916 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