CVE-2024-54909
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 · uneditedA vulnerability has been identified in GoldPanKit eva-server v4.1.0. It affects the path parameter of the /api/resource/local/download endpoint, where manipulation of this parameter can lead to arbitrary file download.
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 confidenceGoldPanKit eva-server v4.1.0 contains a path traversal vulnerability in the /api/resource/local/download endpoint. The path parameter is not properly validated, allowing attackers to manipulate it to download arbitrary files from the server's filesystem.
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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Confirm eva-server is installed and runningIdentify if the GoldPanKit eva-server process is running on the system, typically on its configured port (check running services or listening ports)Affected if eva-server is actively running on the host
-
Determine eva-server versionCheck the installed version of eva-server using its CLI tool, service banner, or version file (e.g., eva-server --version or check /opt/goldpankit/eva-server/version)Affected if the installed version is v4.1.0
-
Verify the vulnerable endpoint is exposedConfirm the /api/resource/local/download API endpoint is accessible by attempting a request to the endpoint (e.g., curl https://host:port/api/resource/local/download?path=test)Affected if the endpoint responds and accepts path parameters
-
Test path traversal vulnerabilitySend a request with a path parameter containing traversal sequences (e.g., path=../../../../etc/passwd) to /api/resource/local/downloadAffected if the server returns content from files outside the intended directory, confirming the path is not validated
-
Check application logs for exploitation attemptsReview eva-server access and error logs for requests to /api/resource/local/download with traversal patternsAffected if logs show requests with ../ sequences that successfully accessed arbitrary files
A user is affected if GoldPanKit eva-server v4.1.0 is running with the /api/resource/local/download endpoint exposed and the path parameter accepts traversal sequences without validation.
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 on the path parameter, ensuring it resolves to an allowed directory and does not contain traversal sequences (../). Use canonical path resolution and enforce allowlist-based access controls.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-54909 — 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-54909 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