dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-5433

MEDIUM · 5.3 CVSS v4.0 Published 2024-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Campbell Scientific CSI Web Server supports a command that will return the most recent file that matches a given expression. A specially crafted expression can lead to a path traversal vulnerability. This command combined with a specially crafted expression allows anonymous, unauthenticated access (allowed by default) by an attacker to files and directories outside of the webserver root directory they should be restricted to.

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 confidence

The Campbell Scientific CSI Web Server contains a path traversal vulnerability in a command that returns the most recent file matching a given expression. By crafting special expressions containing directory traversal sequences (such as ../), unauthenticated anonymous attackers can escape the webroot restriction and access sensitive files and directories on the underlying file system.

MitigationDisable or restrict the vulnerable file-matching command for anonymous users, implement strict input validation to reject path traversal sequences, and ensure anonymous access is disabled or properly restricted by default.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/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. Confirm Campbell Scientific CSI Web Server is installed
    Inspect the system for Campbell Scientific web server software. Check for CSI Web Server processes or installed components matching the Campbell Scientific product family.
    Affected if The product is present on the system
  2. Identify if the file-matching command is exposed
    Locate and inspect the web server configuration to determine if the vulnerable file-matching command endpoint is accessible. Review the web application's published routes or API endpoints.
    Affected if The file-matching command endpoint is accessible via the web interface
  3. Verify anonymous authentication is enabled
    Examine the web server authentication configuration to determine whether anonymous or unauthenticated access is permitted for the file-matching functionality.
    Affected if Anonymous/unauthenticated access is allowed for the affected command
  4. Check installed version against affected releases
    Retrieve the installed CSI Web Server version number from the software or its configuration files, then compare against any available version information from the vendor.
    Affected if The installed version falls within an affected version range (if such ranges become known)
  5. Review webroot configuration and access restrictions
    Inspect the web server's webroot configuration and access control lists to determine if directory traversal restrictions are properly enforced outside the intended web root.
    Affected if Webroot restrictions are misconfigured or insufficiently restrictive

A user is affected if the Campbell Scientific CSI Web Server is running with the vulnerable file-matching command exposed and anonymous access enabled, allowing path traversal outside the webroot.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or restrict the vulnerable file-matching command for anonymous users, implement strict input validation to reject path traversal sequences, and ensure anonymous access is disabled or properly restricted by default.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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