LiveActive security incident?Get immediate response
CVE Record

CVE-2020-29445: Affected versions of Confluence Server before 7.4.8, and versions from 7.5.0 before 7.11.0 allow attackers...

Affected versions of Confluence Server before 7.4.8, and versions from 7.5.0 before 7.11.0 allow attackers to identify internal hosts and ports via a blind server-side request forgery vulnerability in Team Calendars parameters.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw lets a logged-in attacker use vulnerable Confluence Server Team Calendars handling to probe internal hosts and ports. The direct impact is information exposure, not data modification or service outage. Business urgency is moderate for internet-facing or broadly accessible Confluence systems because internal network mapping can support later attacks.

Executive priority

Treat as a moderate-priority remediation item. It is not listed as known exploited in the provided sources, but affected Confluence systems can disclose internal network information to authenticated attackers.

Technical view

CVE-2020-29445 is a blind SSRF in Atlassian Confluence Server Team Calendars parameters. Affected ranges are before 7.4.8 and 7.5.0 before 7.11.0. CVSS 3.1 is 4.3 with network access, low complexity, low privileges, no user interaction, and low confidentiality impact.

Likely exposure

Exposure is most likely where Atlassian Confluence Server is deployed in an affected version range and reachable by low-privileged users. The source bundle does not identify Confluence Data Center, Cloud, or other Atlassian products as affected.

Exploitation context

The provided data does not show CISA KEV listing or confirmed active exploitation. Exploitation requires low privileges and could reveal whether internal hosts and ports exist, which is useful reconnaissance but not direct code execution.

Researcher notes

Evidence is limited to the CVE record and Atlassian Jira reference. The source bundle does not provide exploit details, indicators of compromise, or named compensating controls beyond affected version boundaries.

Mitigation direction

  • Upgrade Confluence Server out of the affected version ranges.
  • Use Atlassian guidance for supported fixed versions and upgrade paths.
  • Restrict Confluence access to trusted users and networks where feasible.
  • Review Team Calendars exposure on affected Confluence Server instances.

Validation and detection

  • Inventory Confluence Server versions across production and non-production systems.
  • Flag versions before 7.4.8 and 7.5.0 through before 7.11.0.
  • Confirm whether vulnerable systems are reachable by low-privileged users.
  • Review Confluence logs for unusual Team Calendars request patterns.
Prepared
Confidence
high
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-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material 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-2020-29445 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2020-29445Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianConfluence Serverunspecified, 7.5.0, unspecifiedListed
Weakness

CWE details

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

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.