Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 3 October 2024.
- Which products and versions are affected?
- @saltcorn/server (npm) SEMVER:introduced=0,fixed=1.0.0-beta.14; Saltcorn <= 1.0.0-beta.13.
- Is there a fix for This vulnerability?
- Yes. @saltcorn/server (npm): upgrade to 1.0.0-beta.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run @saltcorn/server (npm) or Saltcorn at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @saltcorn/server (npm): upgrade to 1.0.0-beta.14 or later
npm install @saltcorn/server@1.0.0-beta.14
Technical details
A path traversal vulnerability (CWE-22) exists in the @saltcorn/server package within the auto-backup download route. The application fails to properly sanitize the 'filename' parameter in the '/admin/auto-backup-download/:filename' endpoint before passing it to the 'res.download' API. While the code checks if the filename starts with a specific prefix and ends with '.zip', it does not resolve the path, allowing an attacker to use '../' sequences to escape the intended backup directory. Exploitation requires administrative privileges and the target file must have a .zip extension. The issue is fixed in version 1.0.0-beta.14 by resolving the filename before validation.
Affected products
- Saltcorn @saltcorn/server <= 1.0.0-beta.13
Timeline
- 2024-10-03: disclosed
- 2024-10-03: advisory
- 2024-10-03: patched