VDB-25418 · CVE-2005-1836 · SA15560

NEXTWEB NEXTWEB (i)Site jsp denial of service

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.
5.3$0-$5k0.00

Summaryinfo

A vulnerability categorized as problematic has been discovered in NEXTWEB NEXTWEB (i)Site. This affects an unknown function of the file jsp. Such manipulation leads to denial of service. This vulnerability is listed as CVE-2005-1836. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in NEXTWEB NEXTWEB (i)Site (affected version unknown). Affected by this issue is an unknown functionality of the file jsp. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. CVE summarizes:

NEXTWEB (i)Site allows remote attackers to cause a denial of service (error 500) via a crafted HTTP request, possibly involving wildcard requests for .jsp files.

The weakness was presented 06/01/2005 (Website). The advisory is available at secunia.com. This vulnerability is handled as CVE-2005-1836 since 06/02/2005. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit.

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 vulnerability database at Secunia (SA15560†). See VDB-25417 and VDB-25416 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

06/01/2005 🔍
06/01/2005 +0 days 🔍
06/01/2005 +0 days 🔍
06/02/2005 +1 days 🔍
03/11/2015 +3569 days 🔍
07/25/2017 +867 days 🔍

Sourcesinfo

Advisory: secunia.com
Status: Not defined

CVE: CVE-2005-1836 (🔍)
GCVE (CVE): GCVE-0-2005-1836
GCVE (VulDB): GCVE-100-25418
Secunia: 15560 - NEXTWEB (i)Site Multiple Vulnerabilities, Moderately Critical

See also: 🔍

Entryinfo

Created: 03/11/2015 11:41
Updated: 07/25/2017 11:44
Changes: 03/11/2015 11:41 (43), 07/25/2017 11:44 (7)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!