Product Atlassian Jira Server

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

8.079
8.178
8.278
8.377
8.477

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

Official Fix103
Temporary Fix0
Workaround0
Unavailable0
Not Defined0

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

High0
Functional0
Proof-of-Concept0
Unproven0
Not Defined103

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

Not Defined0
Physical0
Local0
Adjacent3
Network100

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

Authentication

Not Defined0
High6
Low51
None46

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

User Interaction

Not Defined0
Required22
None81

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

≤10
≤20
≤30
≤415
≤533
≤628
≤715
≤88
≤94
≤100

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

≤10
≤20
≤30
≤416
≤533
≤629
≤716
≤85
≤94
≤100

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

≤10
≤20
≤34
≤418
≤531
≤629
≤77
≤814
≤90
≤100

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

≤10
≤20
≤30
≤41
≤517
≤622
≤714
≤812
≤95
≤104

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

CNA

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

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

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

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

Exploit 0-day

<1k36
<2k42
<5k25
<10k0
<25k0
<50k0
<100k0
≥100k0

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

<1k103
<2k0
<5k0
<10k0
<25k0
<50k0
<100k0
≥100k0

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 (164): 2, 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, 4.0, 5.0, 6.0, 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.3, 7.4, 7.5, 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.12, 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.5.13, 8.5.14, 8.5.15, 8.5.16, 8.5.17, 8.5.18, 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.13.5, 8.13.6, 8.13.7, 8.13.8, 8.13.9, 8.13.11, 8.14, 8.15, 8.16, 8.17, 8.18, 8.18.1, 8.19, 8.20

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

Software Type: Bug Tracking Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
11/03/20217.47.2Atlassian JIRA Server/Data Center Jira Service Management Project ViewCollectors improper authentication$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-41312
11/02/20214.84.7Atlassian JIRA Server/Data Center Associated Project AssociatedProjectsForCustomField.jspa cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-41310
11/01/20215.35.2Atlassian JIRA Server/Data Center Email Batch Confirguation ConfigureBatching!default.jspa improper authorization$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-41313
10/26/20214.84.7Atlassian JIRA Server/Data Center Error Message ImporterFinishedPage.jspa cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-41304
10/26/20216.46.2Atlassian JIRA Server/Data Center File Replication Setting ReplicationSettings!default.jspa improper authorization$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2021-41308
10/26/20217.47.2Atlassian JIRA Server/Data Center Private Project resource injection$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-41307
10/26/20215.95.8Atlassian JIRA Server/Data Center Private Project resource injection$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-41306
10/26/20217.47.2Atlassian JIRA Server/Data Center Project resource injection$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2021-41305
10/21/20215.85.7Atlassian JIRA Server/Data Center JQL Endpoint access control$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-39127
10/21/20216.16.1Atlassian JIRA Server/Data Center Referer cross-site request forgery$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-39126
09/16/20214.74.5Atlassian JIRA Server/Data Center Service Management Addon injection$0-$5k$0-$5kNot DefinedOfficial Fix0.11CVE-2021-39128
09/14/20213.53.4Atlassian JIRA Server/Data Center cross-site request forgery$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-39124
09/14/20215.35.1Atlassian JIRA Server/Data Center Endpoint generate denial of service$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-39123
09/14/20215.35.1Atlassian JIRA Server/Data Center Endpoint check access control$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2019-20101
09/14/20214.34.1Atlassian JIRA Server/Data Center Password Reset Page information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2021-39125
09/14/20214.34.1Atlassian JIRA Server/Data Center Endpoint render information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-39118
09/08/20214.34.1Atlassian JIRA Server/Data Center GIF Image Reader denial of service$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-39116
09/08/20214.34.1Atlassian JIRA Server Search Endpoint search information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.07CVE-2021-39122
09/08/20214.34.1Atlassian JIRA Server/Data Center Private Project key information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2021-39121
09/02/20215.55.3Atlassian JIRA Server/Data Center Notification access control$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-39119
08/30/20214.84.6Atlassian JIRA Server/Data Center Editor Plugin cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-39111
08/30/20213.53.4Atlassian JIRA Server/Data Center AssociateFieldToScreens Page cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-39117
08/30/20216.36.0Atlassian JIRA Server/Data Center Cache access control$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-39113
08/25/20215.55.3Atlassian JIRA Server/Data Center Project Shortcut redirect$0-$5k$0-$5kNot DefinedOfficial Fix0.07CVE-2021-39112
08/16/20214.34.1Atlassian JIRA Server/Data Center Endpoint web.xml path traversal$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-26086

78 more entries are not shown

more entries by Atlassian

Do you want to use VulDB in your project?

Use the official API to access entries easily!