RpshareApplication · Plasmoapp

CVE-2024-33369

HIGH · 8.8 CVSS v3.1 Published 2024-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Directory Traversal vulnerability in Plasmoapp RPShare Fabric mod v.1.0.0 allows a remote attacker to execute arbitrary code via the getFileNameFromConnection method in DownloadTask

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

Directory traversal vulnerability in the getFileNameFromConnection method of the DownloadTask class in Plasmoapp RPShare Fabric mod v1.0.0 allows remote attackers to manipulate file paths and potentially execute arbitrary code by accessing files outside the intended directory.

MitigationApply any available vendor patch; if no patch exists, disable the mod or restrict network access to the affected service until remediation is possible. Implement strict path validation to ensure file paths resolve within intended boundaries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RpshareApplication
Affected:= 1.0.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Locate the RPShare mod file
    Browse to the Fabric mods directory (typically /path/to/fabric/mods/) and search for files containing 'rpshare' in the filename, or list all .jar files and look for the RPShare mod
    Affected if The RPShare mod JAR file exists in the mods folder
  2. Identify the installed version
    Open the mod's JAR file (or check modmenu/modlist) and locate the mod metadata to read the version number
    Affected if The version is exactly 1.0.0
  3. Confirm the download functionality is accessible
    Review the server or client configuration files for RPShare settings that enable or expose the download/file sharing feature
    Affected if The download feature is enabled or exposed to network connections
  4. Check for suspicious file access patterns
    Review server logs for any unusual file path requests containing '../' sequences or access to files outside the intended download directory
    Affected if Log entries show '../' path traversal attempts or unexpected file access

You are affected if RPShare version 1.0.0 is installed with the download feature enabled, as the directory traversal in getFileNameFromConnection can be exploited to access or write arbitrary files.

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

Apply any available vendor patch; if no patch exists, disable the mod or restrict network access to the affected service until remediation is possible. Implement strict path validation to ensure file paths resolve within intended boundaries.

Fix this in Rpshare Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-33369 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