BEA WebLogic Server up to 8.1 Security Provider 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.
5.7$0-$5k0.00

Summaryinfo

A vulnerability was found in BEA WebLogic Server up to 8.1. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the component Security Provider. This manipulation causes cross site scripting. This vulnerability appears as CVE-2005-1743. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in BEA WebLogic Server up to 8.1 (Application Server Software). It has been declared as problematic. Affected by this vulnerability is an unknown function of the component Security Provider. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

BEA WebLogic Server and WebLogic Express 8.1 through Service Pack 3 and 7.0 through Service Pack 5 does not properly handle when a security provider throws an exception, which may cause WebLogic to use incorrect identity for the thread, or to fail to audit security exceptions.

The bug was discovered 05/24/2005. The weakness was presented 05/24/2005 by Mitja Kolsek with ACROS Security (Website). The advisory is shared at vupen.com. This vulnerability is known as CVE-2005-1743 since 05/25/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 18365 (BEA WebLogic <= 8.1 SP4 Multiple Vulnerabilities (XSS, DoS, ID, more)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Web Servers and running in the context r.

Upgrading eliminates this vulnerability. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 11505.

The vulnerability is also documented in the databases at X-Force (20704), Tenable (18365), SecurityFocus (BID 13717†), OSVDB (16834†) and Secunia (SA15486†). See VDB-1229, VDB-1421, VDB-1512 and VDB-1518 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 5.7

VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 18365
Nessus Name: BEA WebLogic <= 8.1 SP4 Multiple Vulnerabilities (XSS, DoS, ID, more)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍
TippingPoint: 🔍

Timelineinfo

05/24/2005 🔍
05/24/2005 +0 days 🔍
05/24/2005 +0 days 🔍
05/24/2005 +0 days 🔍
05/24/2005 +0 days 🔍
05/24/2005 +0 days 🔍
05/24/2005 +0 days 🔍
05/25/2005 +1 days 🔍
05/25/2005 +0 days 🔍
07/13/2006 +414 days 🔍
03/11/2015 +3163 days 🔍
06/22/2019 +1564 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: vupen.com⛔
Researcher: Mitja Kolsek
Organization: ACROS Security
Status: Confirmed

CVE: CVE-2005-1743 (🔍)
GCVE (CVE): GCVE-0-2005-1743
GCVE (VulDB): GCVE-100-25333
X-Force: 20704
SecurityFocus: 13717 - BEA WebLogic Server and WebLogic Express Multiple Remote Vulnerabilities
Secunia: 15486 - BEA WebLogic Multiple Vulnerabilities, Moderately Critical
OSVDB: 16834 - CVE-2005-1743 - BEA - WebLogic Server and Express - Security Bypass Issue
SecurityTracker: 1014049
Vulnerability Center: 12255 - BEA WebLogic Server and Express Improper Handling of Exceptions, High
Vupen: ADV-2005-0603

See also: 🔍

Entryinfo

Created: 03/11/2015 11:41
Updated: 06/22/2019 11:31
Changes: 03/11/2015 11:41 (78), 06/22/2019 11:31 (4)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!