CVE-2016-4319 Cross-site request forgery in Atlassian JIRA Server before 7.1.9
High 8.8
Published
Updated
Check this codebase for CVE-2016-4319 and fix it if it is affected.
What it is: CVE-2016-4319 is a high-severity vulnerability in Atlassian Jira, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-4319 in the wild and no public exploit code.
Affected product: Atlassian Jira. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2016-4319/ (Markdown: https://insights.sbomify.com/CVE-2016-4319/index.md)
Cross-site request forgery in Atlassian JIRA Server allows attackers to modify auditing settings via crafted requests.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2016-4319?
CVE-2016-4319 is a high-severity vulnerability in Atlassian Jira, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Atlassian JIRA Server before 7.1.9 has CSRF in auditing/settings.
Weakness: CWE-352
Which versions are affected by CVE-2016-4319?
It affects 1 product.
Products include Atlassian Jira.
How do I fix CVE-2016-4319?
No fix has been published for CVE-2016-4319 yet. Limit exposure of the affected software until one is available.
Is CVE-2016-4319 being exploited?
There is no known exploitation of CVE-2016-4319 in the wild and no public exploit code.
Other vulnerabilities in Atlassian Jira
Sources
Also known as GHSA-r798-mxm8-76rv.