High Bea CVEs
33 CVEs, 1 protected by Waratek
Overview 33 matches · 1 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
1
3.0%
Rule in development
0
0.0%
Mitigation candidate
2
6.1%
No exploit published
30
90.9%
blocked by ARMR today
1
3.0%
partly blocked
0
0.0%
not blocked
32
97.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
2
6.1%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
31
93.9%
split by
peak 9 / year
20004
Mitigation candidate2
No exploit published2
High4
not blocked4
Working exploit published2
No public exploit2
20010
20022
No exploit published2
High2
not blocked2
No public exploit2
20032
No exploit published2
High2
not blocked2
No public exploit2
20043
No exploit published3
High3
not blocked3
No public exploit3
20058
No exploit published8
High8
not blocked8
No public exploit8
20063
No exploit published3
High3
not blocked3
No public exploit3
20079
Protected by Waratek1
No exploit published8
High9
blocked by ARMR today1
not blocked8
No public exploit9
20082
No exploit published2
High2
not blocked2
No public exploit2
200020012002200320042005200620072008
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2008-0901 | High | 2008-02-22 | No exploit published | No public exploit | BEA WebLogic Server and Express 7.0 through 10.0 allows remote attackers to conduct brute force password guessing attacks, even when account lockout has been activated, via crafted URLs that indicate whether a guessed password is successful or not. |
| CVE-2008-0897 | High | 2008-02-22 | No exploit published | No public exploit | Unspecified vulnerability in BEA WebLogic Server 9.0 through 10.0 allows remote authenticated users without "receive" permissions to bypass intended access restrictions and receive messages from a standalone JMS Topic or secured Distributed Topic member destination, related to durable subscriptions. |
| CVE-2007-6384 | High | 2007-12-15 | No exploit published | No public exploit | Unspecified vulnerability in the Image Converter functionality in BEA WebLogic Mobility Server 3.3, 3.5, and 3.6 through 3.6 SP1 allows remote attackers to obtain application file and resource access via unspecified vectors. |
| CVE-2007-4618 | High | 2007-08-31 | No exploit published | No public exploit | Unspecified vulnerability in BEA WebLogic Server 6.1 Gold through SP7 and 7.0 Gold through SP7 allows remote attackers to cause a denial of service (disk consumption) via certain malformed HTTP headers. |
| CVE-2007-4617 | High | 2007-08-31 | No exploit published | No public exploit | Unspecified vulnerability in BEA WebLogic Server 6.1 Gold through SP7, 7.0 Gold through SP7, and 8.1 Gold through SP4 allows remote attackers to cause a denial of service (server thread hang) via unspecified vectors. |
| CVE-2007-4614 | High | 2007-08-31 | No exploit published | No public exploit | BEA WebLogic Server 9.1 does not properly handle propagation of an admin server's security policy change log to temporarily unavailable managed servers, which might allow attackers to bypass intended restrictions, a different vulnerability than CVE-2007-0426. |
| CVE-2007-2705 | High | 2007-05-16 | Protected by Waratek | No public exploit | Directory traversal vulnerability in the Test View Console in BEA WebLogic Integration 9.2 before SP1 and WebLogic Workshop 8.1 SP2 through SP6, when "deployed in an exploded format," allows remote attackers to list a WebLogic Workshop Directory (wlwdir) parent directory via unspecified vectors. |
| CVE-2007-2699 | High | 2007-05-16 | No exploit published | No public exploit | The Administration Console in BEA WebLogic Express and WebLogic Server 9.0 and 9.1 does not properly enforce certain Domain Security Policies, which allows remote administrative users in the Deployer role to upload arbitrary files. |
| CVE-2007-0418 | High | 2007-01-23 | No exploit published | No public exploit | BEA WebLogic Server 7.0 through 7.0 SP6, 8.1 through 8.1 SP5, 9.0, and 9.1 does not enforce a security policy that declares permissions for EJB methods that have array parameters, which allows remote attackers to obtain unauthorized access to these methods. |
| CVE-2007-0417 | High | 2007-01-23 | No exploit published | No public exploit | BEA WebLogic Server 7.0 through 7.0 SP7, 8.1 through 8.1 SP5, 9.0, and 9.1, when using the WebLogic Server 6.1 compatibility realm, allows attackers to execute certain EJB container persistence operations with an administrative identity. |
| CVE-2007-0416 | High | 2007-01-23 | No exploit published | No public exploit | The WSEE runtime (WS-Security runtime) in BEA WebLogic Server 9.0 and 9.1 does not verify credentials when decrypting client messages, which allows remote attackers to bypass application security. |
| CVE-2006-2470 | High | 2006-05-19 | No exploit published | No public exploit | Unspecified vulnerability in the WebLogic Server Administration Console for BEA WebLogic Server 9.0 prevents the console from setting custom JDBC security policies correctly, which could allow attackers to bypass intended policies. |
| CVE-2006-2469 | High | 2006-05-19 | No exploit published | No public exploit | The HTTP handlers in BEA WebLogic Server 9.0, 8.1 up to SP5, 7.0 up to SP6, and 6.1 up to SP7 stores the username and password in cleartext in the WebLogic Server log when access to a web application or protected JWS fails, which allows attackers to gain privileges. |
| CVE-2006-0426 | High | 2006-01-25 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 through SP4, when configuration auditing is enabled and a password change occurs, stores the old and new passwords in cleartext in the DefaultAuditRecorder.log file, which could allow attackers to gain privileges. |
| CVE-2005-4765 | High | 2005-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier and 7.0 SP6 and earlier, when using the weblogic.Deployer command with the t3 protocol, does not use the secure t3s protocol even when an Administration port is enabled on the Administration server, which might allow remote attackers to sniff the connection. |
| CVE-2005-4764 | High | 2005-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 9.0, 8.1, and 7.0 lock out the admin user account after multiple incorrect password guesses, which allows remote attackers who know or guess the admin account name to cause a denial of service (blocked admin logins). |
| CVE-2005-4763 | High | 2005-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier, 7.0 SP6 and earlier, and 6.1 SP7 and earlier, when Internet Inter-ORB Protocol (IIOP) is used, sometimes include a password in an exception message that is sent to a client or stored in a log file, which might allow remote attackers to perform unauthorized actions. |
| CVE-2005-4762 | High | 2005-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier, 7.0 SP6 and earlier, and 6.1 SP7 and earlier sometimes stores the boot password in the registry in cleartext, which might allow local users to gain administrative privileges. |
| CVE-2005-4757 | High | 2005-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 SP3 and earlier, and 7.0 SP5 and earlier, do not properly "constrain" a "/" (slash) servlet root URL pattern, which might allow remote attackers to bypass intended servlet protections. |
| CVE-2005-4756 | High | 2005-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier, and 7.0 SP5 and earlier, do not properly validate derived Principals with multiple PrincipalValidators, which might allow attackers to gain privileges. |
| CVE-2005-4750 | High | 2005-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier, 7.0 SP5 and earlier, and 6.1 SP7 and earlier allow remote attackers to cause a denial of service (server thread hang) via unknown attack vectors. |
| CVE-2005-1743 | High | 2005-05-24 | No exploit published | No public exploit | 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. |
| CVE-2004-0652 | High | 2004-08-06 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 7.0 through 7.0 Service Pack 4, and 8.1 through 8.1 Service Pack 2, allows attackers to obtain the username and password for booting the server by directly accessing certain internal methods. |
| CVE-2004-0711 | High | 2004-07-27 | No exploit published | No public exploit | The URL pattern matching feature in BEA WebLogic Server 6.x matches illegal patterns ending in "*" as wildcards as if they were the legal "/*" pattern, which could cause WebLogic 7.x to allow remote attackers to bypass intended access restrictions because the illegal patterns are properly rejected. |
| CVE-2004-0470 | High | 2004-07-07 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 7.0 through SP5 and 8.1 through SP2, when editing weblogic.xml using WebLogic Builder or the SecurityRoleAssignmentMBean.toXML method, inadvertently removes security-role-assignment tags when weblogic.xml does not have a principal-name tag, which can remove intended access restrictions for the associated web application. |
| CVE-2003-1094 | High | 2003-12-31 | No exploit published | No public exploit | BEA WebLogic Server and Express version 7.0 SP3 may follow certain code execution paths that result in an incorrect current user, such as in the frequent use of JNDI initial contexts, which could allow remote authenticated users to gain privileges. |
| CVE-2003-0151 | High | 2003-03-24 | No exploit published | No public exploit | BEA WebLogic Server and Express 6.0 through 7.0 does not properly restrict access to certain internal servlets that perform administrative functions, which allows remote attackers to read arbitrary files or execute arbitrary code. |
| CVE-2002-2142 | High | 2002-12-31 | No exploit published | No public exploit | An undocumented extension for the Servlet mappings in the Servlet 2.3 specification, when upgrading to WebLogic Server and Express 7.0 Service Pack 1 from BEA WebLogic Server and Express 6.0 through 7.0.0.1, does not prepend a "/" character in certain URL patterns, which prevents the proper enforcement of role mappings and policies in applications that use the extension. |
| CVE-2002-2141 | High | 2002-12-31 | No exploit published | No public exploit | BEA WebLogic Server and Express 7.0 and 7.0.0.1, when running Servlets and Enterprise JavaBeans (EJB) on more than one server, will remove the security constraints and roles on all servers for any Servlets or EJB that are used by an application that is undeployed on one server, which could allow remote attackers to conduct unauthorized activities in violation of the intended restrictions. |
| CVE-2000-1238 | High | 2000-12-31 | No exploit published | No public exploit | BEA Systems WebLogic Express and WebLogic Server 5.1 SP1-SP6 allows remote attackers to bypass access controls for restricted JSP or servlet pages via a URL with multiple / (forward slash) characters before the restricted pages. |
| CVE-2000-0685 | High | 2000-10-20 | Mitigation candidate | Working exploit published | BEA WebLogic 5.1.x does not properly restrict access to the PageCompileServlet, which could allow remote attackers to compile and execute Java JHTML code by directly invoking the servlet on any source file. |
| CVE-2000-0684 | High | 2000-10-20 | Mitigation candidate | Working exploit published | BEA WebLogic 5.1.x does not properly restrict access to the JSPServlet, which could allow remote attackers to compile and execute Java JSP code by directly invoking the servlet on any source file. |
| CVE-2000-0499 | High | 2000-06-08 | No exploit published | No public exploit | The default configuration of BEA WebLogic 3.1.8 through 4.5.1 allows a remote attacker to view source code of a JSP program by requesting a URL which provides the JSP extension in upper case. |