| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in BEA WebLogic 8.1. This issue affects some unknown processing of the component WSSE Certificate Handler. Performing a manipulation results in Local Privilege Escalation. This vulnerability was named CVE-2007-0408. There is no available exploit. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as problematic has been found in BEA WebLogic 8.1 (Application Server Software). This affects an unknown code of the component WSSE Certificate Handler. The manipulation with an unknown input leads to a local privilege escalation vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
BEA Weblogic Server 8.1 through 8.1 SP4 does not properly validate client certificates when reusing cached connections, which allows remote attackers to obtain access via an untrusted X.509 certificate.
The weakness was presented 01/17/2007 with BEA (Website). The advisory is shared at dev2dev.bea.com. This vulnerability is uniquely identified as CVE-2007-0408 since 01/22/2007. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
It is declared as proof-of-concept. The commercial vulnerability scanner Qualys is able to test this issue with plugin 86766 (BEA WebLogic Multiple Vulnerabilities (2007)).
Applying a patch is able to eliminate this problem. The bugfix is ready for download at dev2dev.bea.com.
The vulnerability is also documented in the databases at SecurityFocus (BID 22082†), OSVDB (38500†), Secunia (SA23750†) and SecurityTracker (ID 1017519†). See VDB-2858, VDB-2856, VDB-2847 and VDB-2852 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.9
VulDB Temp Score: 5.3
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: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: dev2dev.bea.com
Timeline
01/16/2007 🔍01/16/2007 🔍
01/17/2007 🔍
01/17/2007 🔍
01/22/2007 🔍
01/22/2007 🔍
01/22/2007 🔍
07/22/2007 🔍
04/22/2018 🔍
Sources
Vendor: oracle.comAdvisory: dev2dev.bea.com
Researcher: http://www.bea.com
Organization: BEA
Status: Confirmed
CVE: CVE-2007-0408 (🔍)
GCVE (CVE): GCVE-0-2007-0408
GCVE (VulDB): GCVE-100-2853
SecurityFocus: 22082 - BEA Multiple Products Multiple Vulnerabilities
Secunia: 23750 - BEA WebLogic Multiple Vulnerabilities and Security Issues, Moderately Critical
OSVDB: 38500 - BEA WebLogic Server Cached Connection X.509 Certificate Validation Bypass
SecurityTracker: 1017519
Vupen: ADV-2007-0213
See also: 🔍
Entry
Created: 01/22/2007 10:51Updated: 04/22/2018 13:23
Changes: 01/22/2007 10:51 (69), 04/22/2018 13:23 (8)
Complete: 🔍
Cache ID: 216:E5F:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.