Overview 26 matches · 1 protected · 0 exploited · 0 CISA KEV · 4 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
1
3.8%
Rule in development
0
0.0%
Mitigation candidate
4
15.4%
No exploit published
21
80.8%
blocked by ARMR today
1
3.8%
partly blocked
0
0.0%
not blocked
25
96.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
4
15.4%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
22
84.6%
split by
peak 12 / quarter
Q2 001
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
Q3 000
Q4 002
No exploit published2
Medium2
not blocked2
No public exploit2
Q1 010
Q2 010
Q3 010
Q4 010
Q1 021
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
Q2 020
Q3 020
Q4 020
Q1 031
No exploit published1
Medium1
not blocked1
No public exploit1
Q2 030
Q3 030
Q4 0312
Mitigation candidate2
No exploit published10
Medium12
not blocked12
Working exploit published2
No public exploit10
Q1 040
Q2 042
No exploit published2
Medium2
not blocked2
No public exploit2
Q3 043
No exploit published3
Medium3
not blocked3
No public exploit3
Q4 044
Protected by Waratek1
No exploit published3
Medium4
blocked by ARMR today1
not blocked3
No public exploit4
Q2 00Q4 00Q2 01Q4 01Q2 02Q4 02Q2 03Q4 03Q2 04Q4 04
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-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-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-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-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-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-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 | Mitigation candidate | 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-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-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-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-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. |