mitre / mitre/secure-coding-case-studies
Proposal: A Secure Coding Case Study of CVE-2019-8451 in the Atlassian Jira Platform
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
As part of our coursework in ISA-681, myself and Anudeep Nikku, propose to develop a case study on CVE-2019-8451, a Server-Side Request Forgery vulnerability that appeared in the Atlassian Jira platform versions before 8.4.0. This vulnerability occurred as a result of improper validation of user-supplied URLs which allowed attackers to manipulate the server into making unintended HTTP requests. In this case study we will analyze exploit write ups and technical analyses to expose how this vulnerability can be exploited for malicious intent. Additionally, we will examine the patch to identify the secure coding practices implemented to mitigate this vulnerability, such as input validation. Overall, this case study is extremely relevant to both our coursework (ISA-681) and real-world vulnerabilities. Improper validation of user input continues to be one of the most common vulnerabilities in software systems today. By analyzing this vulnerability, our study highlights the importance of implementing securing coding practices to prevent exploitation and protect resources.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No project files or tests are named. Start by reviewing the CVE-2019-8451 exploit write-ups, technical analyses, and the relevant Atlassian Jira patch; document how the SSRF occurred and which secure coding practices mitigated it. Done means a complete case study covering the vulnerability, exploitation context, and patch analysis.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100