Vendor Atlassian

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Type »

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product »

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation »

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability »

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector »

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication »

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction »

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index »

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base »

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp »

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB »

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD »

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

Vendor »

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research »

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day »

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today »

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume »

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities »

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (38): Activity Streams (1), Application Links (4), Atlaskit (1), Bamboo (12), Bitbucket Data Center (1), Bitbucket Server (10), Companion App (2), Confluence (10), Confluence Data Center (3), Confluence Questions (2), Confluence Server (16), Crowd (5), Crowd Data Center (1), Crucible (38), Data Center (64), Doxygen for Atlassian Confluence (3), Eucalyptus (1), FishEye (34), Fisheye (2), Floodlight Controller (2), HipChat (1), Hipchat Server (1), JIRA (40), JIRA Core (1), JIRA Server (65), JIRA Server for Slack Plugin (1), JIRA Software (1), Jira (2), Jira Data Center (1), Jira Service Desk Data Center (3), Jira Service Desk Server (5), Navigator Links (1), OAuth Plugin (1), SourceTree (5), Universal Plugin Manager (3), atlassian-gadgets (1), gajira-comment (1), gajira-create (1)

Link to Vendor Website: https://www.atlassian.com/

PublishedBaseTempVulnerabilityProdExpRemCTICVE
04/09/20217.37.3Atlassian JIRA Server/Data Center Dashboard Gadgets Preference Resource authorizationBug Tracking SoftwareNot DefinedOfficial Fix3.31-CVE-2020-36287
04/02/20216.36.0Atlassian Confluence Server/Confluence Data Center WidgetConnector Plugin server-side request forgeryUnknownNot DefinedOfficial Fix0.11CVE-2021-26072
04/01/20213.53.4Atlassian JIRA Server/Data Center SetFeatureEnabled.jspa cross-site request forgeryBug Tracking SoftwareNot DefinedOfficial Fix0.05CVE-2021-26071
04/01/20214.84.6Atlassian JIRA Server/Data Center JQL Search membersOf information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.05CVE-2020-36286
04/01/20214.84.6Atlassian JIRA Server/Data Center render information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.00CVE-2020-36238
03/22/20217.37.0Atlassian JIRA Server/Data Center behind-the-firewall Protection improper authenticationBug Tracking SoftwareNot DefinedOfficial Fix0.17CVE-2021-26070
03/22/20214.84.6Atlassian JIRA Server/Data Center API Endpoint ActionsAndOperations information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.06CVE-2021-26069
02/23/20217.57.2Atlassian JIRA Server for Slack Plugin Endpoint injectionBug Tracking SoftwareNot DefinedOfficial Fix0.04CVE-2021-26068
02/23/20215.35.1Atlassian atlassian-gadgets HTTP Request MessageBundleWhiteList server-side request forgeryUnknownNot DefinedOfficial Fix0.04CVE-2020-36232
02/23/20215.35.1Atlassian JIRA Server/Data Center CachingResourceDownloadRewriteRule information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.05CVE-2020-29453
02/23/20215.35.1Atlassian Confluence Server/Confluence Data Center ConfluenceResourceDownloadRewriteRule information disclosureUnknownNot DefinedOfficial Fix0.00CVE-2020-29448
02/19/20216.56.3Atlassian Bitbucket Server/Data Center Installer access controlUnknownNot DefinedOfficial Fix0.05CVE-2020-36233
02/15/20215.35.1Atlassian JIRA Server/Data Center Custom Field information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.05CVE-2020-36237
02/15/20214.84.6Atlassian JIRA Server/Data Center Endpoint ViewWorkflowSchemes.jspa cross site scriptingBug Tracking SoftwareNot DefinedOfficial Fix0.08CVE-2020-36236
02/15/20215.35.1Atlassian JIRA Server/Data Center Custom Field information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.09CVE-2020-36235
02/15/20214.14.0Atlassian JIRA Server/Data Center Screens Modal View cross site scriptingBug Tracking SoftwareNot DefinedOfficial Fix0.05CVE-2020-36234
02/15/20214.34.1Atlassian JIRA Server/Data Center Plugin Report Page information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.07CVE-2020-29451
02/02/20214.34.1Atlassian JIRA Server/Data Center Metadata resource injectionBug Tracking SoftwareNot DefinedOfficial Fix0.05CVE-2020-36231
01/28/20215.35.1Atlassian Bamboo Endpoint chart information disclosureUnknownNot DefinedOfficial Fix0.00CVE-2021-26067
01/19/20215.45.1Atlassian Confluence Server/Data Center Avatar Upload denial of serviceUnknownNot DefinedOfficial Fix0.05CVE-2020-29450
01/18/20214.84.6Atlassian FishEye/Crucible file accessProgramming Tool SoftwareNot DefinedOfficial Fix0.07CVE-2020-29446
12/21/20204.34.3Atlassian Crucible File Upload denial of serviceProgramming Tool SoftwareNot DefinedOfficial Fix0.03CVE-2020-29447
11/26/20205.95.6Atlassian Fisheye/Crucible MessageBundleResource denial of serviceProgramming Tool SoftwareNot DefinedOfficial Fix0.07CVE-2020-14191
11/26/20205.95.6Atlassian Fisheye/Crucible EyeQL incorrect regexProgramming Tool SoftwareNot DefinedOfficial Fix0.00CVE-2020-14190
11/10/20208.07.7Atlassian gajira-comment GitHub Action Remote Privilege EscalationUnknownNot DefinedOfficial Fix0.00CVE-2020-14189

Interested in the pricing of exploits?

See the underground prices here!