CVE-2021-39109: Path traversal vulnerability in atlasboard

atlasboard Updated 02 Oct 2025

Summary

02/09/2021
Yes i
High
7.5

CVE-2021-39109: Path traversal in atlasboard. Affects atlasboard versions < 1.1.9. Fixed in 1.1.9. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Atlasboard is an open-source dashboard framework developed by Atlassian. It allows users to create customizable dashboards for monitoring and visualizing data. The vulnerability identified as CVE-2021-39109 affects versions of Atlasboard prior to 1.1.9. This vulnerability enables remote attackers to read arbitrary files through a path traversal vulnerability in the renderWidgetResource resource.

Vulnerability Detail

The renderWidgetResource resource in Atlasboard before version 1.1.9 is susceptible to a path traversal vulnerability. This vulnerability allows remote attackers to access files outside of the intended directory by manipulating the file path in requests. By exploiting this vulnerability, an attacker can read arbitrary files on the server, potentially exposing sensitive information. The impact of this vulnerability depends on the nature of the files that can be accessed and the permissions of the server process.

How To Fix

Minimum fixed version

1.1.9

This is the first release that contains the fix.

npm install atlasboard@1.1.9

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version is not immediately feasible, a temporary workaround can be implemented by implementing input validation and sanitization on the file paths used in the renderWidgetResource resource. By ensuring that only valid and authorized file paths are accepted, the risk of path traversal attacks can be mitigated. Here is an example of how input validation can be implemented in Node.js:

function validateFilePath(filePath) {
  // Implement your validation logic here
  // Return true if the file path is valid, false otherwise
}

function renderWidgetResource(req, res) {
  const filePath = req.query.file;
  if (validateFilePath(filePath)) {
    // Proceed with rendering the widget resource
  } else {
    // Handle invalid file path
  }
}

Conclusion

The path traversal vulnerability in Atlasboard versions prior to 1.1.9 poses a risk of unauthorized file access. To mitigate this vulnerability, it is essential to upgrade to the latest version of Atlasboard or apply the provided workaround. Regularly monitoring for vulnerabilities and keeping dependencies up to date is crucial for maintaining the security of your application. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for atlasboard →

Share this vulnerability

FAQ

The vulnerability allows remote attackers to read arbitrary files on the server, potentially exposing sensitive information. The impact depends on the nature of the files that can be accessed and the permissions of the server process.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide your package-lock.json file, and Vulert will analyze it for any known vulnerabilities, including CVE-2021-39109.

At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is important to apply the recommended fix or workaround as soon as possible to mitigate the risk.

Yes, a patch is available in Atlasboard version 1.1.9. It is recommended to upgrade to this version or later to address the vulnerability.

In addition to upgrading to the latest version of Atlasboard, it is recommended to follow secure coding practices and implement input validation and sanitization on file paths used in the renderWidgetResource resource. Regularly monitoring and updating dependencies is also crucial to ensure the overall security of your application.

How To Fix

Minimum fixed version

1.1.9

This is the first release that contains the fix.

npm install atlasboard@1.1.9

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback