Product Atlassian Jira

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.

Last Year

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.

Version »

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

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.

Last Year »

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.

Last Year »

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 Versions (249): 2, 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.0.11, 2.0.12, 2.0.13, 2.0.14, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 3.1, 3.1.1, 3.4.3, 3.6.2 156, 3.9, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 3.9.8, 3.9.9, 3.9.11, 3.9.12, 3.9.13, 3.9.14, 3.9.15, 3.9.16, 3.10.1, 3.10.2, 3.10.3, 3.10.4, 3.10.5, 3.10.6, 3.10.7, 3.10.8, 3.10.9, 3.12, 3.12.1, 3.12.2, 3.12.3, 3.13, 3.13.1, 3.13.2, 3.13.3, 3.13.4, 3.13.5, 3.16, 3.16.1, 3.16.2, 3.16.3, 3.16.4, 3.16.5, 3.16.6, 3.16.7, 3.16.8, 4.0, 4.0.1, 4.0.2, 4.1, 4.1.1, 4.1.2, 4.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2.5, 4.3, 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.4, 4.4.1, 4.4.2, 4.5, 4.6, 4.7, 4.8, 4.9, 4.10, 4.11, 5.0, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.1, 6.2, 7, 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.1, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.2, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.11, 7.3, 7.4, 7.4.1, 7.5, 7.5.1, 7.5.2, 7.5.3, 7.6, 7.6.1, 7.6.2, 7.6.3, 7.6.4, 7.6.5, 7.6.6, 7.6.7, 7.6.8, 7.6.9, 7.6.11, 7.6.12, 7.6.13, 7.6.14, 7.6.15, 7.6.16, 7.7, 7.7.1, 7.7.2, 7.7.3, 7.7.4, 7.8, 7.8.1, 7.8.2, 7.8.3, 7.8.4, 7.9, 7.9.1, 7.9.2, 7.10, 7.10.1, 7.10.2, 7.11, 7.11.1, 7.11.2, 7.12, 7.12.1, 7.12.2, 7.12.3, 7.13, 7.13.1, 7.13.2, 7.13.3, 7.13.4, 7.13.5, 7.13.6, 7.13.7, 7.13.8, 7.13.9, 7.13.11, 7.13.12, 7.13.13, 7.13.14, 7.13.15, 7.13.16, 7.13.17, 8, 8.0, 8.0.1, 8.0.2, 8.1, 8.1.1, 8.1.2, 8.2, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.3, 8.3.1, 8.3.2, 8.3.3, 8.4, 8.4.1, 8.5, 8.5.1, 8.5.2, 8.5.3, 8.5.4, 8.5.5, 8.5.6, 8.5.7, 8.5.8, 8.5.9, 8.5.11, 8.5.12, 8.6, 8.6.1, 8.7, 8.7.1, 8.8, 8.8.1, 8.9, 8.9.1, 8.10, 8.10.1, 8.11, 8.12, 8.12.1, 8.12.2, 8.13, 8.13.1, 8.13.2, 8.13.3, 8.13.4, 8.14, 8.15

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

Software Type: Bug Tracking Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
04/15/20213.73.6Atlassian JIRA Server/Data Center Cookie missing secure attribute$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-26076
04/15/20214.34.1Atlassian JIRA Server/Data Center Jira Importers Plugin information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-26075
04/15/20213.53.4Atlassian JIRA Server/Data Center Issue Navigation/Search View cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-36288
04/09/20217.37.0Atlassian JIRA Server/Data Center Dashboard Gadgets Preference Resource authorization$0-$5k$0-$5kNot DefinedOfficial Fix0.13CVE-2020-36287
04/01/20213.53.4Atlassian JIRA Server/Data Center SetFeatureEnabled.jspa cross-site request forgery$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-26071
04/01/20214.84.6Atlassian JIRA Server/Data Center JQL Search membersOf information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2020-36286
04/01/20214.84.6Atlassian JIRA Server/Data Center render information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2020-36238
03/22/20217.37.0Atlassian JIRA Server/Data Center behind-the-firewall Protection improper authentication$0-$5k$0-$5kNot DefinedOfficial Fix0.13CVE-2021-26070
03/22/20214.84.6Atlassian JIRA Server/Data Center API Endpoint ActionsAndOperations information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.07CVE-2021-26069
02/23/20217.57.2Atlassian JIRA Server for Slack Plugin Endpoint injection$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2021-26068
02/23/20215.35.1Atlassian JIRA Server/Data Center CachingResourceDownloadRewriteRule information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2020-29453
02/15/20215.35.1Atlassian JIRA Server/Data Center Custom Field information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-36237
02/15/20214.84.6Atlassian JIRA Server/Data Center Endpoint ViewWorkflowSchemes.jspa cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-36236
02/15/20215.35.1Atlassian JIRA Server/Data Center Custom Field information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-36235
02/15/20214.14.0Atlassian JIRA Server/Data Center Screens Modal View cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-36234
02/15/20214.34.1Atlassian JIRA Server/Data Center Plugin Report Page information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-29451
02/02/20214.34.1Atlassian JIRA Server/Data Center Metadata resource injection$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-36231
10/16/20205.35.1Atlassian JIRA Server Issue Key ActionsAndOperations permission$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-14185
10/12/20204.44.3Atlassian JIRA Server Issue Filter Export File cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-14184
10/07/20203.93.7Atlassian JIRA Server/Data Center SEN information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-14183
10/01/20206.46.1Atlassian JIRA Crowd Upgrade privileges management$0-$5k$0-$5kNot DefinedOfficial Fix0.07CVE-2019-20902
09/21/20204.34.1Atlassian Jira Service Desk Server/Data Center Project Request Type information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.01CVE-2020-14180
09/21/20205.35.1Atlassian JIRA Server/Data Center QueryComponent!Default.jspa information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-14179
09/21/20204.34.1Atlassian JIRA Server/Data Center incorrect regex$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-14177
09/17/20205.35.1Atlassian JIRA Server/Data Center ViewUserHover.jspa information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-14181

more entries by Atlassian

Do you want to use VulDB in your project?

Use the official API to access entries easily!