dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-36267

HIGH · 8.1 CVSS v3.1 Published 2024-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
Path traversal vulnerability exists in Redmine DMSF Plugin versions prior to 3.1.4. If this vulnerability is exploited, a logged-in user may obtain or delete arbitrary files on the server (within the privilege of the Redmine process).

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 confidence

Path traversal vulnerability in Redmine DMSF (Document Management System Framework) plugin allows authenticated users to access or manipulate files outside the intended directory through insufficient path validation. Successful exploitation enables reading or deleting arbitrary files on the server within the Redmine process privileges.

MitigationUpgrade DMSF plugin to version 3.1.4 or later to obtain the patch for proper path validation. Verify file access controls and monitor for anomalous file operations.

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 checks

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

  1. Confirm Redmine DMSF plugin is installed
    Locate the DMSF plugin directory in the Redmine installation (typically under plugins/ or in the Gemfile), or query the Redmine plugins list via admin interface or CLI: bundle exec rake redmine:plugins
    Affected if DMSF plugin directory or entry is not found, meaning the plugin is not installed and the system is not affected
  2. Identify the installed DMSF plugin version
    Check the version.rb or gemspec file within the DMSF plugin directory, or view the plugin version in Redmine's admin plugins page under the DMSF plugin entry
    Affected if Version is lower than 3.1.4 (e.g., 3.1.3, 3.1.2, 3.0.x, etc.)
  3. Verify document management features are enabled
    Log into Redmine as an authenticated user with document management permissions. Navigate to the DMSF module within a project (usually under Documents or a dedicated DMSF tab) and confirm the file upload/download/delete operations are accessible
    Affected if User can access and perform file operations through the DMSF interface; the vulnerability requires this module to be active
  4. Confirm user authentication is active
    Verify that Redmine requires authentication (not in anonymous mode) and that the DMSF plugin's access controls are enforced. Check that users must log in to access file management features
    Affected if DMSF is accessible to authenticated users; the path traversal requires an authenticated session to exploit

System is affected if DMSF plugin version is below 3.1.4 AND the DMSF document management module is enabled and accessible to authenticated users in Redmine.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade DMSF plugin to version 3.1.4 or later to obtain the patch for proper path validation. Verify file access controls and monitor for anomalous file operations.

Recommended fix Moderate confidence

DMSF Plugin version 3.1.4

  1. 1. Backup your current Redmine DMSF plugin directory and database before proceeding
  2. 2. Download Redmine DMSF Plugin version 3.1.4 from the official repository or release source
  3. 3. Extract the new version and replace the existing dmsf plugin files in Redmine's plugins directory
  4. 4. Run any required database migrations for the plugin (typically: bundle exec rake redmine:plugins:migrate)
  5. 5. Restart the Redmine application server to load the updated plugin
Caveat Review the plugin's changelog for any configuration or feature changes between your current version and 3.1.4

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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