Overview 158 matches · 135 in Waratek scope · 2 protected · 0 exploited · 0 CISA KEV · 12 public PoC · 4 EPSS ≥ 0.5
158matches
135in Waratek scope85.4%
2protected1.3%
0exploited0.0%
0CISA KEV0.0%
12public PoC7.6%
4EPSS ≥ 0.52.5%
Protected by Waratek
2
1.3%
Rule in development
0
0.0%
Mitigation candidate
7
4.4%
No exploit published
126
79.7%
Outside Waratek scope
17
10.8%
Not applicable
6
3.8%
Withdrawn CVE
0
0.0%
blocked by ARMR today
2
1.3%
partly blocked
0
0.0%
not blocked
156
98.7%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
12
7.6%
Proof of concept only
0
0.0%
Forecast only
1
0.6%
No public exploit
145
91.8%
split by
peak 40 / year
20008
Mitigation candidate3
No exploit published4
Outside Waratek scope1
High5
Medium3
not blocked8
Working exploit published3
Forecast only1
No public exploit4
20012
Outside Waratek scope1
Not applicable1
High1
Medium1
not blocked2
Working exploit published1
No public exploit1
20025
Mitigation candidate1
No exploit published4
High2
Medium1
Low2
not blocked5
Working exploit published1
No public exploit4
200320
Mitigation candidate1
No exploit published17
Outside Waratek scope2
High3
Medium13
Low4
not blocked20
Working exploit published2
No public exploit18
200415
Protected by Waratek1
No exploit published13
Outside Waratek scope1
High4
Medium9
Low2
blocked by ARMR today1
not blocked14
Working exploit published1
No public exploit14
200532
Mitigation candidate1
No exploit published30
Outside Waratek scope1
Critical1
High8
Medium21
Low2
not blocked32
Working exploit published1
No public exploit31
200624
No exploit published24
High3
Medium16
Low5
not blocked24
No public exploit24
200740
Protected by Waratek1
No exploit published24
Outside Waratek scope10
Not applicable5
High12
Medium27
Low1
blocked by ARMR today1
not blocked39
Working exploit published1
No public exploit39
200811
No exploit published10
Outside Waratek scope1
High3
Medium8
not blocked11
Working exploit published1
No public exploit10
20090
20101
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20002001200220032004200520062007200820092010
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2005-1747 | Medium | 2005-05-24 | No exploit published | No public exploit | Multiple cross-site scripting (XSS) vulnerabilities in BEA WebLogic Server and Express 8.1 through Service Pack 4, and 7.0 through Service Pack 6, allow remote attackers to inject arbitrary web script or HTML, and possibly gain administrative privileges, via the (1) j_username or (2) j_password parameters in the login page (LoginForm.jsp), (3) parameters to the error page in the Administration Console, (4) unknown vectors in the Server Console while the administrator has an active session to obtain the ADMINCONSOLESESSION cookie, or (5) an alternate vector in the Server Console that does not require an active session but also leaks the username and password. |
| CVE-2005-1746 | Medium | 2005-05-24 | No exploit published | No public exploit | The cluster cookie parsing code in BEA WebLogic Server 7.0 through Service Pack 5 attempts to contact any host or port specified in a cookie, even when it is not in the cluster, which allows remote attackers to cause a denial of service (cluster slowdown) via modified cookies. |
| CVE-2005-1745 | Medium | 2005-05-24 | No exploit published | No public exploit | The UserLogin control in BEA WebLogic Portal 8.1 through Service Pack 3 prints the password to standard output when an incorrect login attempt is made, which could make it easier for attackers to guess the correct password. |
| CVE-2005-1744 | Critical | 2005-05-24 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 7.0 through Service Pack 5 does not log out users when an application is redeployed, which allows those users to continue to access the application without having to log in again, which may be in violation of newly changed security constraints or role mappings. |
| 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-2005-1742 | Medium | 2005-05-24 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 SP2 and SP3 allows users with the Monitor security role to "shrink or reset JDBC connection pools." |
| CVE-2005-1380 | Medium | 2005-05-03 | Mitigation candidate | Working exploit published | Cross-site scripting (XSS) vulnerability in BEA Admin Console 8.1 allows remote attackers to execute arbitrary web script or HTML via the server parameter to a JndiFramesetAction action. |
| CVE-2005-0432 | Medium | 2005-05-02 | No exploit published | No public exploit | BEA WebLogic Server 7.0 Service Pack 5 and earlier, and 8.1 Service Pack 3 and earlier, generates different login exceptions that suggest why an authentication attempt fails, which makes it easier for remote attackers to guess passwords via brute force attacks. |
| CVE-2004-2696 | Medium | 2004-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 6.1, 7.0, and 8.1, when using Remote Method Invocation (RMI) over Internet Inter-ORB Protocol (IIOP), does not properly handle when multiple logins for different users coming from the same client, which could cause an "unexpected user identity" to be used in an RMI call. |
| CVE-2004-2424 | Medium | 2004-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 through 8.1 SP2 allow remote attackers to cause a denial of service (network port consumption) via unknown actions in HTTPS sessions, which prevents the server from releasing the network port when the session ends. |
| CVE-2004-2321 | Low | 2004-12-31 | No exploit published | No public exploit | BEA WebLogic Server and Express 8.1 SP1 and earlier allows local users in the Operator role to obtain administrator passwords via MBean attributes, including (1) ServerStartMBean.Password and (2) NodeManagerMBean.CertificatePassword. |
| CVE-2004-2320 | Medium | 2004-12-31 | Protected by Waratek | No public exploit | The default configuration of BEA WebLogic Server and Express 8.1 SP2 and earlier, 7.0 SP4 and earlier, 6.1 through SP6, and 5.1 through SP13 responds to the HTTP TRACE request, which can allow remote attackers to steal information using cross-site tracing (XST) attacks in applications that are vulnerable to cross-site scripting. |
| CVE-2004-1757 | Medium | 2004-12-31 | No exploit published | No public exploit | BEA WebLogic Server and Express 8.1, SP1 and earlier, stores the administrator password in cleartext in config.xml, which allows local users to gain privileges. |
| 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-0204 | High | 2004-08-06 | Outside Waratek scope | Working exploit published | Directory traversal vulnerability in the web viewers for Business Objects Crystal Reports 9 and 10, and Crystal Enterprise 9 or 10, as used in Visual Studio .NET 2003 and Outlook 2003 with Business Contact Manager, Microsoft Business Solutions CRM 1.2, and other products, allows remote attackers to read and delete arbitrary files via ".." sequences in the dynamicimag argument to crystalimagehandler.aspx. |
| CVE-2004-0715 | Medium | 2004-07-27 | No exploit published | No public exploit | The WebLogic Authentication provider for BEA WebLogic Server and WebLogic Express 8.1 through SP2 and 7.0 through SP4 does not properly clear member relationships when a group is deleted, which can cause a new group with the same name to have the members of the old group, which allows group members to gain privileges. |
| CVE-2004-0713 | Medium | 2004-07-27 | No exploit published | No public exploit | The remove method in a stateful Enterprise JavaBean (EJB) in BEA WebLogic Server and WebLogic Express version 8.1 through SP2, 7.0 through SP4, and 6.1 through SP6, does not properly check EJB permissions before unexporting a bean, which allows remote authenticated users to remove EJB objects from remote views before the security exception is thrown. |
| CVE-2004-0712 | Medium | 2004-07-27 | No exploit published | No public exploit | The configuration tools (1) config.sh in Unix or (2) config.cmd in Windows for BEA WebLogic Server 8.1 through SP2 create a log file that contains the administrative username and password in cleartext, which could allow local users to gain privileges. |
| 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-0471 | Low | 2004-07-07 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 7.0 through SP5 and 8.1 through SP2 does not enforce site restrictions for starting and stopping servers for users in the Admin and Operator security roles, which allows unauthorized users to cause a denial of service (service shutdown). |
| 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-2004-1758 | Medium | 2004-04-13 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express version 8.1 up to SP2, 7.0 up to SP4, and 6.1 up to SP6 may store the database username and password for an untargeted JDBC connection pool in plaintext in config.xml, which allows local users to gain privileges. |
| CVE-2004-1756 | Medium | 2004-04-13 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 8.1 SP2 and earlier, and 7.0 SP4 and earlier, when using 2-way SSL with a custom trust manager, may accept a certificate chain even if the trust manager rejects it, which allows remote attackers to spoof other users or servers. |
| CVE-2003-1438 | Medium | 2003-12-31 | No exploit published | No public exploit | Race condition in BEA WebLogic Server and Express 5.1 through 7.0.0.1, when using in-memory session replication or replicated stateful session beans, causes the same buffer to be provided to two users, which could allow one user to see session data that was intended for another user. |
| CVE-2003-1437 | Low | 2003-12-31 | No exploit published | No public exploit | BEA WebLogic Express and WebLogic Server 7.0 and 7.0.0.1, stores passwords in plaintext when a keystore is used to store a private key or trust certificate authorities, which allows local users to gain access. |
| CVE-2003-1290 | Medium | 2003-12-31 | No exploit published | No public exploit | BEA WebLogic Server and WebLogic Express 6.1, 7.0, and 8.1, with RMI and anonymous admin lookup enabled, allows remote attackers to obtain configuration information by accessing MBeanHome via the Java Naming and Directory Interface (JNDI). |
| CVE-2003-1226 | Low | 2003-12-31 | No exploit published | No public exploit | BEA WebLogic Server and Express 7.0 and 7.0.0.1 stores certain secrets concerning password encryption insecurely in config.xml, filerealm.properties, and weblogic-rar.xml, which allows local users to learn those secrets and decrypt passwords. |
| CVE-2003-1225 | Low | 2003-12-31 | No exploit published | No public exploit | The default CredentialMapper for BEA WebLogic Server and Express 7.0 and 7.0.0.1 stores passwords in cleartext on disk, which allows local users to extract passwords. |
| CVE-2003-1224 | Low | 2003-12-31 | No exploit published | No public exploit | Weblogic.admin for BEA WebLogic Server and Express 7.0 and 7.0.0.1 displays the JDBCConnectionPoolRuntimeMBean password to the screen in cleartext, which allows attackers to read a user's password by physically observing ("shoulder surfing") the screen. |
| CVE-2003-1223 | Medium | 2003-12-31 | No exploit published | No public exploit | The Node Manager for BEA WebLogic Express and Server 6.1 through 8.1 SP 1 allows remote attackers to cause a denial of service (Node Manager crash) via malformed data to the Node Manager's port, as demonstrated by nmap. |
| CVE-2003-1222 | Medium | 2003-12-31 | No exploit published | No public exploit | BEA Weblogic Express and Server 8.0 through 8.1 SP 1, when using a foreign Java Message Service (JMS) provider, echoes the password for the foreign provider to the console and stores it in cleartext in config.xml, which could allow attackers to obtain the password. |
| CVE-2003-1221 | Medium | 2003-12-31 | No exploit published | No public exploit | BEA WebLogic Express and Server 7.0 through 8.1 SP 1, under certain circumstances when a request to use T3 over SSL (t3s) is made to the insecure T3 port, may use a non-SSL connection for the communication, which could allow attackers to sniff sessions. |
| CVE-2003-1220 | Medium | 2003-12-31 | No exploit published | No public exploit | BEA WebLogic Server proxy plugin for BEA Weblogic Express and Server 6.1 through 8.1 SP 1 allows remote attackers to cause a denial of service (proxy plugin crash) via a malformed URL. |
| 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-1093 | Medium | 2003-12-31 | No exploit published | No public exploit | BEA WebLogic Server 6.1, 7.0 and 7.0.0.1, when routing messages to a JMS target domain that is inaccessible, may leak the user's password when it throws a ResourceAllocationException. |
| CVE-2003-0624 | Medium | 2003-12-01 | Outside Waratek scope | Working exploit published | Cross-site scripting (XSS) vulnerability in InteractiveQuery.jsp for BEA WebLogic 8.1 and earlier allows remote attackers to inject malicious web script via the person parameter. |
| CVE-2003-0623 | Medium | 2003-12-01 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in the Administration Console for BEA Tuxedo 8.1 and earlier allows remote attackers to inject arbitrary web script via the INIFILE argument. |
| CVE-2003-0622 | Medium | 2003-12-01 | No exploit published | No public exploit | The Administration Console for BEA Tuxedo 8.1 and earlier allows remote attackers to cause a denial of service (hang) via pathname arguments that contain MS-DOS device names such as CON and AUX. |
| CVE-2003-0621 | Medium | 2003-12-01 | Mitigation candidate | Working exploit published | The Administration Console for BEA Tuxedo 8.1 and earlier allows remote attackers to determine the existence of files outside the web root via modified paths in the INIFILE argument. |
| CVE-2003-0733 | Medium | 2003-10-20 | No exploit published | No public exploit | Multiple cross-site scripting (XSS) vulnerabilities in WebLogic Integration 7.0 and 2.0, Liquid Data 1.1, and WebLogic Server and Express 5.1 through 7.0, allow remote attackers to execute arbitrary web script and steal authentication credentials via (1) a forward instruction to the Servlet container or (2) other vulnerabilities in the WebLogic Server console application. |
| CVE-2003-0640 | High | 2003-08-27 | Outside Waratek scope | No public exploit | BEA WebLogic Server and Express, when using NodeManager to start servers, provides Operator users with privileges to overwrite usernames and passwords, which may allow Operators to gain Admin 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-2003-1095 | Medium | 2003-03-18 | No exploit published | No public exploit | BEA WebLogic Server and Express 7.0 and 7.0.0.1, when using "memory" session persistence for web applications, does not clear authentication information when a web application is redeployed, which could allow users of that application to gain access without having to re-authenticate. |
| CVE-2002-2177 | Low | 2002-12-31 | No exploit published | No public exploit | BEA WebLogic Server and Express 6.1 through 7.0.0.1 buffers HTTP requests in a way that can cause BEA to send the same response for two different HTTP requests, which could allow remote attackers to obtain sensitive information that was intended for other users. |
| 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-2002-1030 | Low | 2002-10-04 | No exploit published | No public exploit | Race condition in Performance Pack in BEA WebLogic Server and Express 5.1.x, 6.0.x, 6.1.x and 7.0 allows remote attackers to cause a denial of service (crash) via a flood of data and connections. |
| CVE-2002-0106 | Medium | 2002-03-25 | Mitigation candidate | Working exploit published | BEA Systems Weblogic Server 6.1 allows remote attackers to cause a denial of service via a series of requests to .JSP files that contain an MS-DOS device name. |
| CVE-2001-1477 | Medium | 2001-12-31 | Not applicable | No public exploit | The Domain gateway in BEA Tuxedo 7.1 does not perform authorization checks for imported services and qspaces on remote domains, even when an ACL exists, which allows users to access services in a remote domain. |
| CVE-2001-0098 | High | 2001-02-12 | Outside Waratek scope | Working exploit published | Buffer overflow in Bea WebLogic Server before 5.1.0 allows remote attackers to execute arbitrary commands via a long URL that begins with a ".." string. |
| 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-0683 | Medium | 2000-10-20 | No exploit published | No public exploit | BEA WebLogic 5.1.x allows remote attackers to read source code for parsed pages by inserting /*.shtml/ into the URL, which invokes the SSIServlet. |
| CVE-2000-0682 | Medium | 2000-10-20 | No exploit published | No public exploit | BEA WebLogic 5.1.x allows remote attackers to read source code for parsed pages by inserting /ConsoleHelp/ into the URL, which invokes the FileServlet. |
| CVE-2000-0681 | High | 2000-10-20 | Outside Waratek scope | Forecast only | Buffer overflow in BEA WebLogic server proxy plugin allows remote attackers to execute arbitrary commands via a long URL with a .JSP extension. |
| CVE-2000-0500 | Medium | 2000-06-21 | Mitigation candidate | Working exploit published | The default configuration of BEA WebLogic 5.1.0 allows a remote attacker to view source code of programs by requesting a URL beginning with /file/, which causes the default servlet to display the file without further processing. |
| 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. |