Atlassian Jira App Software Vulnerabilities

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.

Vendor

Identifying all affected vendors is a good starting point for an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Product

Zephyr for JIRA Test Management Plugin3
Infosysta In-App 3
Infosysta Desktop Notifications App3
Xray Test Management for Jira Plugin2
Gantt-Chart Module2

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

Official Fix13
Temporary Fix0
Workaround0
Unavailable0
Not Defined13

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

High1
Functional0
Proof-of-Concept2
Unproven0
Not Defined23

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
Local2
Adjacent1
Network23

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
High0
Low19
None7

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
Required9
None17

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

≤10
≤20
≤30
≤43
≤58
≤66
≤76
≤83
≤90
≤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
≤44
≤57
≤69
≤75
≤81
≤90
≤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
≤30
≤47
≤57
≤66
≤75
≤81
≤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
≤40
≤53
≤67
≤71
≤82
≤95
≤100

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

<1k14
<2k7
<5k5
<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

<1k24
<2k2
<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.

🔴 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 (18): Better PDF Exporter Add-on, Bobronix JEditor, Cprime Power Scripts App, Gantt-Chart Module, Gliffy, HipChat for JIRA Plugin, Infosysta In-App , Infosysta Desktop Notifications App, QMetry for JIRA Test Management Plugin, Ricksoft WBS Gantt-Chart, Tempo Plugin, Tenable for Jira Cloud, Time in Status App, TM Software Tempo, Transition Technologies The Scheduler App, Xray Test Management, Xray Test Management for Jira Plugin, Zephyr for JIRA Test Management Plugin

PublishedBaseTempVulnerabilityProductExpRemCTICVE
07/22/20223.53.5Better PDF Exporter Add-on PDF Templates Overview Page cross site scriptingBetter PDF Exporter Add-onNot DefinedNot Defined0.00CVE-2022-36131
05/12/20213.53.5Xray Test Management for Jira Plugin cross-site request forgeryXray Test Management for Jira PluginNot DefinedNot Defined0.08CVE-2021-21652
05/12/20215.55.5Xray Test Management for Jira Plugin HTTP Endpoint authorizationXray Test Management for Jira PluginNot DefinedNot Defined0.04CVE-2021-21653
03/11/20217.16.8Tenable for Jira Cloud yaml.load deserializationTenable for Jira CloudNot DefinedOfficial Fix0.03CVE-2021-21371
03/09/20214.44.3Time in Status App cross site scriptingTime in Status AppNot DefinedOfficial Fix0.04CVE-2021-27222
08/04/20204.44.3Gantt-Chart Module Dashboard Persistent cross site scriptingGantt-Chart ModuleNot DefinedOfficial Fix0.04CVE-2020-15944
08/04/20207.26.8Gantt-Chart Module Privilege Check authorizationGantt-Chart ModuleNot DefinedOfficial Fix0.07CVE-2020-15943
07/02/20205.35.3Zephyr for JIRA Test Management Plugin Permission Check improper authorizationZephyr for JIRA Test Management PluginNot DefinedNot Defined0.03CVE-2020-2216
07/02/20204.34.3Zephyr for JIRA Test Management Plugin cross-site request forgeryZephyr for JIRA Test Management PluginNot DefinedNot Defined0.00CVE-2020-2215
03/09/20205.45.4Zephyr for JIRA Test Management Plugin Credentials cleartext storageZephyr for JIRA Test Management PluginNot DefinedNot Defined0.02CVE-2020-2154

16 more entries are not shown

Do you know our Splunk app?

Download it now for free!