Introduction
This document reports the security audit results of the Confluence and Jira plugins “Requirement Yogi Cloud” and “Requirement Yogi for Jira Cloud” developed by the company Requirement Yogi.
ArcanSecurity did the audit between the 19th of April 2022 and the 21st of April 2022.
Requirement Yogi provided three accounts: Super Admin, Admin and User.
N.B: the results come from 3 days of audit. Thus, they may be only a subset of what an attacker with no time limit can find.
N.B.2: the results have been updated after a verification audit performed early July.
Risk analysis summary
The main risks which lead to this audit are:
Data leak of a customer
Unauthorized changes or deletion of customer’s data - Privilege escalation
The availability of the platform
During the audit, the auditor has determined four scenarios that could impact the company Requirement
- A user dumps data linked to another customer or a space he does not have access to
- A user changes data linked to another customer or a space he does not have access to
- A user performs a restricted action for which he does not have the granted rights
- An attacker performs a distributed denial of service on the platform
Risk assessment
| Probability of the risk | ||
|---|---|---|
| Impact | Description | |
| 4 | Strong | The environment or context of the company means that, if nothing is done, such a threat will certainly materialize in the short term. |
3 | Average | The environment and the context of the company mean that, if nothing is done, such a threat will materialize in the short term. |
| 2 | Low | Even in the absence of any security measure, the environment and the context mean that the probability of occurrence of such a threat, in the short or medium term, is low. |
| 1 | Unlikely | Regardless of any security measures, the probability of occurrence of such a threat is extremely low and negligible. |
| Impact of the risk | ||
|---|---|---|
| Impact | Description | |
| 4 | Strong | Unsustainable financial, legal, commercial or image impact. |
3 | Average | Significant financial, legal, commercial or image impact |
| 2 | Low | Weak financial, legal, commercial or image impact. |
| 1 | Minimal | Financial, legal, commercial or image impact without significant impact. |
Summary
Scenario | Probability | Impact | Risk | Action to lower the risk |
|---|---|---|---|---|
An attacker performs a distributed denial of service on the platform | 2 | 3 | 6 | Implement a rate-limiting system |
A user changes data linked to another customer or a space he does not have access to | 1 | 4 | 4 | Harden the overall system Secure the API |
A user dumps data linked to another customer or a space he does not have access to | 1 | 3 | 3 | Harden the overall system Secure the API |
A user performs a restricted action for which he does not have the granted rights | 1 | 3 | 3 | Harden the overall system Secure the API |
General overview
Strength
Good understanding of the cybersecurity risks |
Follow the guidelines from Atlassian |
Secure development |
Possible improvements
Make the API more consistent |
Integrate all the good practices in the whole stack of the system |
Address the current flaws |
Conclusion
During the audit, no critical or high vulnerabilities were found by the auditor.
By focusing on the security picture only, the plugin Requirement Yogi Cloud is at a good level.
An attacker will certainly take a considerable amount of time to find and exploit a potential vulnerability in the API. Thus, an attacker would try gaining access to the system by other meanings, like stealing the AWS credentials, doing a phishing attack on employees or other.
Among that, let’s not forget that on a bigger picture, the system needs some work to make the API fully consistent, less verbose, and more robust against denial of service.
By taking all of the steps mentioned in the given roadmap, the probability of an attack could be reduced, and so the risk too.