Show filters
501 Total Results
Displaying 421-430 of 501
Sort by:
Attacker Value
Unknown

CVE-2017-16863

Disclosure Date: January 18, 2018 (last updated November 26, 2024)
The PieChart gadget in Atlassian Jira before version 7.5.3 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability through the name of a project or filter.
0
Attacker Value
Unknown

CVE-2017-18033

Disclosure Date: January 18, 2018 (last updated November 26, 2024)
The Jira-importers-plugin in Atlassian Jira before version 7.6.1 allows remote attackers to create new projects and abort an executing external system import via various Cross-site request forgery (CSRF) vulnerabilities.
0
Attacker Value
Unknown

CVE-2017-16865

Disclosure Date: January 17, 2018 (last updated November 26, 2024)
The Trello importer in Atlassian Jira before version 7.6.1 allows remote attackers to access the content of internal network resources via a Server Side Request Forgery (SSRF). When running in an environment like Amazon EC2, this flaw maybe used to access to a metadata resource that provides access credentials and other potentially confidential information.
0
Attacker Value
Unknown

CVE-2017-16862

Disclosure Date: January 12, 2018 (last updated November 26, 2024)
The IncomingMailServers resource in Atlassian Jira before version 7.6.2 allows remote attackers to modify the "incoming mail" whitelist setting via a Cross-site request forgery (CSRF) vulnerability.
0
Attacker Value
Unknown

CVE-2017-16864

Disclosure Date: January 12, 2018 (last updated November 26, 2024)
The issue search resource in Atlassian Jira before version 7.4.2 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the orderby parameter.
0
Attacker Value
Unknown

CVE-2017-14594

Disclosure Date: January 12, 2018 (last updated November 26, 2024)
The printable searchrequest issue resource in Atlassian Jira before version 7.2.12 and from version 7.3.0 before 7.6.1 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the jqlQuery query parameter.
0
Attacker Value
Unknown

CVE-2017-14590

Disclosure Date: December 13, 2017 (last updated November 26, 2024)
Bamboo did not check that the name of a branch in a Mercurial repository contained argument parameters. An attacker who has permission to create a repository in Bamboo, edit an existing plan that has a non-linked Mercurialrepository, create or edit a plan when there is at least one linked Mercurial repository that the attacker has permission to use, or commit to a Mercurial repository used by a Bamboo plan which has branch detection enabled can execute code of their choice on systems that run a vulnerable version of Bamboo Server. Versions of Bamboo starting with 2.7.0 before 6.1.6 (the fixed version for 6.1.x) and from 6.2.0 before 6.2.5 (the fixed version for 6.2.x) are affected by this vulnerability.
0
Attacker Value
Unknown

CVE-2017-14589

Disclosure Date: December 13, 2017 (last updated November 26, 2024)
It was possible for double OGNL evaluation in FreeMarker templates through Struts FreeMarker tags to occur. An attacker who has restricted administration rights to Bamboo or who hosts a website that a Bamboo administrator visits, is able to exploit this vulnerability to execute Java code of their choice on systems that run a vulnerable version of Bamboo. All versions of Bamboo before 6.1.6 (the fixed version for 6.1.x) and from 6.2.0 before 6.2.5 (the fixed version for 6.2.x) are affected by this vulnerability.
0
Attacker Value
Unknown

CVE-2017-16856

Disclosure Date: December 05, 2017 (last updated November 26, 2024)
The RSS Feed macro in Atlassian Confluence before version 6.5.2 allows remote attackers to inject arbitrary HTML or JavaScript via cross site scripting (XSS) vulnerabilities in various rss properties which were used as links without restriction on their scheme.
0
Attacker Value
Unknown

CVE-2017-16857

Disclosure Date: December 05, 2017 (last updated November 26, 2024)
It is possible to bypass the bitbucket auto-unapprove plugin via minimal brute-force because it is relying on asynchronous events on the back-end. This allows an attacker to merge any code into unsuspecting repositories. This affects all versions of the auto-unapprove plugin, however since the auto-unapprove plugin is not bundled with Bitbucket Server it does not affect any particular version of Bitbucket.
0