| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in BEA WebLogic Server 9.0. The affected element is an unknown function. Performing a manipulation results in an unknown weakness. This vulnerability is known as CVE-2006-0432. No exploit is available.
Details
A vulnerability classified as problematic has been found in BEA WebLogic Server 9.0 (Application Server Software). This is going to have an impact on integrity. The summary by CVE is:
Unspecified vulnerability in BEA WebLogic Server and WebLogic Express 9.0, when an Administrator uses the WebLogic Administration Console to add custom security policies, causes incorrect policies to be created, which prevents the server from properly protecting JNDI resources.
The bug was discovered 01/23/2006. The weakness was published 01/25/2006 (Website). The advisory is shared at dev2dev.bea.com. This vulnerability is uniquely identified as CVE-2006-0432 since 01/25/2006. The exploitability is told to be easy. 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 vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $25k-$100k.
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 X-Force (24299), SecurityFocus (BID 16358†), OSVDB (22770†), Secunia (SA18592†) and SecurityTracker (ID 1015528†). Similar entries are available at VDB-2005, VDB-2009, VDB-2006 and VDB-2000. 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: 4.0VulDB Meta Temp Score: 3.8
VulDB Base Score: 4.0
VulDB Temp Score: 3.8
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: UnknownCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/23/2006 🔍01/23/2006 🔍
01/23/2006 🔍
01/24/2006 🔍
01/24/2006 🔍
01/25/2006 🔍
01/25/2006 🔍
01/25/2006 🔍
07/13/2006 🔍
03/12/2015 🔍
06/22/2019 🔍
Sources
Vendor: oracle.comAdvisory: dev2dev.bea.com
Status: Confirmed
CVE: CVE-2006-0432 (🔍)
GCVE (CVE): GCVE-0-2006-0432
GCVE (VulDB): GCVE-100-28485
X-Force: 24299
SecurityFocus: 16358 - BEA WebLogic Multiple Vulnerabilities
Secunia: 18592 - BEA WebLogic Server/Express Vulnerabilities and Security Issues, Moderately Critical
OSVDB: 22770 - CVE-2006-0432 - BEA - WebLogic Server And WebLogic Express - Unspecified Issue
SecurityTracker: 1015528
Vulnerability Center: 12267 - BEA WebLogic Server and Express Administration Console May Cause Incorrect Security Policies, Low
Vupen: ADV-2006-0313
See also: 🔍
Entry
Created: 03/12/2015 11:11Updated: 06/22/2019 12:44
Changes: 03/12/2015 11:11 (67), 06/22/2019 12:44 (3)
Complete: 🔍
Cache ID: 216::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.