Atlassian JIRA 3.12 Error Message 500page.jsp cross site scripting

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.1$0-$5k0.00

Summaryinfo

A vulnerability has been found in Atlassian JIRA 3.12 and classified as problematic. This affects an unknown function of the file 500page.jsp of the component Error Message Handler. Performing a manipulation results in cross site scripting. This vulnerability was named CVE-2007-6617. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Atlassian JIRA 3.12 (Bug Tracking Software). This affects an unknown part of the file 500page.jsp of the component Error Message Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

Cross-site scripting (XSS) vulnerability in 500page.jsp in JIRA Enterprise Edition before 3.12.1 allows remote attackers to inject arbitrary web script or HTML, which is not properly handled when generating error messages, as demonstrated by input originally sent in the URI to secure/CreateIssue. NOTE: some of these details are obtained from third party information.

The bug was discovered 12/23/2007. The weakness was presented 12/24/2007 (Website). It is possible to read the advisory at confluence.atlassian.com. This vulnerability is uniquely identified as CVE-2007-6617 since 01/03/2008. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:500page.jsp it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 29834 (Atlassian JIRA 500page.jsp XSS), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses : XSS and running in the context r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 12581 (Atlassian JIRA Multiple XSS Vulnerabilities (JIRA Security Advisory 2007-12-24)).

Upgrading to version 3.12 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (39377), Tenable (29834), SecurityFocus (BID 27095†), OSVDB (42768†) and Secunia (SA27954†). See VDB-40325 and VDB-40324 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Cross site scripting
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 29834
Nessus Name: Atlassian JIRA 500page.jsp XSS
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: JIRA 3.12

Timelineinfo

12/23/2007 🔍
12/23/2007 +0 days 🔍
12/24/2007 +1 days 🔍
12/24/2007 +0 days 🔍
12/24/2007 +0 days 🔍
01/02/2008 +9 days 🔍
01/03/2008 +0 days 🔍
01/03/2008 +0 days 🔍
01/03/2008 +0 days 🔍
01/06/2008 +3 days 🔍
03/16/2015 +2626 days 🔍
08/02/2019 +1600 days 🔍

Sourcesinfo

Vendor: atlassian.com

Advisory: confluence.atlassian.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2007-6617 (🔍)
GCVE (CVE): GCVE-0-2007-6617
GCVE (VulDB): GCVE-100-40323
X-Force: 39377
SecurityFocus: 27095 - Atlassian JIRA Multiple Security Bypass Weaknesses
Secunia: 27954
OSVDB: 42768 - Atlassian JIRA Enterprise Edition 500page.jsp Error Message XSS
Vulnerability Center: 17265 - Atlassian JIRA Enterprise Edition XSS Vulnerability in 500page.jsp, Medium

See also: 🔍

Entryinfo

Created: 03/16/2015 13:43
Updated: 08/02/2019 16:45
Changes: 03/16/2015 13:43 (74), 08/02/2019 16:45 (5)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!