CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
3.9 | $0-$5k | 0.00 |
A vulnerability, which was classified as problematic, has been found in Java Search Engine 0.9.34 (Programming Language Software). This issue affects an unknown functionality of the file search.jsp of the component Search Engine. The manipulation of the argument q
with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. Impacted is integrity. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in search.jsp in Java Search Engine (JSE) 0.9.34 allows remote attackers to inject arbitrary web script or HTML via the q parameter.
The weakness was published 12/02/2005 by r0t (Website). The advisory is shared at vupen.com. The identification of this vulnerability is CVE-2005-3966 since 12/03/2005. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
After even before and not, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:search.jsp it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Exploit-DB (26700), SecurityFocus (BID 15687†), OSVDB (21376†) and Secunia (SA17834†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/02/2005 🔍12/02/2005 🔍
12/02/2005 🔍
12/02/2005 🔍
12/02/2005 🔍
12/03/2005 🔍
12/03/2005 🔍
03/11/2015 🔍
12/14/2024 🔍
Sources
Advisory: vupen.com⛔Researcher: r0t
Status: Not defined
CVE: CVE-2005-3966 (🔍)
GCVE (CVE): GCVE-0-2005-3966
GCVE (VulDB): GCVE-100-27245
SecurityFocus: 15687 - Java Search Engine Search.JSP Cross-Site Scripting Vulnerability
Secunia: 17834 - Java Search Engine "q" Cross-Site Scripting Vulnerability, Less Critical
OSVDB: 21376 - Java Search Engine (JSE) search.jsp q Parameter XSS
Vupen: ADV-2005-2690
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/11/2015 11:39 PMUpdated: 12/14/2024 09:07 PM
Changes: 03/11/2015 11:39 PM (55), 08/26/2017 06:44 AM (8), 12/14/2024 09:07 PM (23)
Complete: 🔍
Cache ID: 18:5E2:40
No comments yet. Languages: en.
Please log in to comment.