LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39109: The renderWidgetResource resource in Atlasian Atlasboard before version 1.1.9 allows remote attackers to re...

The renderWidgetResource resource in Atlasian Atlasboard before version 1.1.9 allows remote attackers to read arbitrary files via a path traversal vulnerability.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-39109 is a path traversal flaw in Atlassian Atlasboard before 1.1.9. A remote unauthenticated attacker could read arbitrary files from an affected server, creating confidentiality risk for secrets, configuration, and local data.

Executive priority

Prioritize remediation for any exposed Atlasboard deployment because the vulnerability can disclose server files without authentication. Internal-only systems still matter if they store credentials or configuration secrets.

Technical view

The vulnerable renderWidgetResource resource in Atlasboard allows path traversal leading to arbitrary file read. CVSS 3.1 is 7.5: network exploitable, low complexity, no privileges, no user interaction, high confidentiality impact, no integrity or availability impact listed.

Likely exposure

Exposure is likely limited to organizations running Atlassian Atlasboard versions before 1.1.9, especially if the application is reachable over a network or internet-facing. The source bundle provides no CPEs or detailed deployment indicators.

Exploitation context

The CVE record describes remote unauthenticated file read, but the bundle does not cite active exploitation. CISA KEV status is false. Treat exploitation as plausible due to low complexity, but do not assume observed attacks without local evidence.

Researcher notes

Evidence is concise: CWE-22 in renderWidgetResource, affected Atlasboard before 1.1.9, and a linked Atlassian commit. The bundle does not provide exploit details, affected CPEs, operational mitigations, or proof of exploitation.

Mitigation direction

  • Upgrade Atlasboard to version 1.1.9 or later.
  • Restrict network access to Atlasboard until upgraded.
  • Remove or disable unused Atlasboard deployments.
  • Review Atlassian commit and vendor guidance before applying compensating controls.
  • Reduce sensitive files accessible to the Atlasboard runtime account.

Validation and detection

  • Inventory Atlasboard instances and confirm their versions.
  • Check whether Atlasboard is reachable from untrusted networks.
  • Verify the renderWidgetResource behavior after upgrading.
  • Review application logs for suspicious resource path requests.
  • Confirm runtime file permissions limit access to secrets.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-39109 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-39109Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianAtlasboardunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.