dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-35474

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
A Directory Traversal vulnerability in iceice666 ResourcePack Server before v1.0.8 allows a remote attacker to disclose files on the server, via setPath in ResourcePackFileServer.kt.

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

A directory traversal vulnerability exists in the ResourcePackFileServer.kt component of iceice666 ResourcePack Server versions prior to v1.0.8. The setPath function fails to properly validate or sanitize path traversal sequences (such as '../'), allowing a remote attacker to read arbitrary files on the server file system by crafting malicious path requests.

MitigationUpgrade to ResourcePack Server v1.0.8 or later, which contains the patch for this vulnerability. If immediate patching is not possible, implement input validation to reject path traversal sequences in the setPath function and restrict file access to intended directories.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ResourcePack Server installation
    Locate the ResourcePack Server application files or running process. Check for JAR files named 'ResourcePackServer' or similar, or look for a running Java process serving resource packs.
    Affected if ResourcePack Server is found installed or running on the system
  2. Determine installed version
    Check the version of the ResourcePack Server by examining the JAR file name, process arguments, or any version manifest. Compare the version to v1.0.8.
    Affected if The installed version is prior to v1.0.8 (e.g., v1.0.7, v1.0.6, or any version below 1.0.8)
  3. Verify file serving is enabled
    Check if the ResourcePackFileServer.kt component is actively being used or configured. Look for file serving endpoints or configurations that allow external path requests.
    Affected if The file serving functionality is enabled and accessible to network clients

You are affected if ResourcePack Server is running with a version prior to v1.0.8 and the file serving feature is exposed, allowing unauthenticated path traversal requests.

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

Upgrade to ResourcePack Server v1.0.8 or later, which contains the patch for this vulnerability. If immediate patching is not possible, implement input validation to reject path traversal sequences in the setPath function and restrict file access to intended directories.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

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