Bea vulnerabilitiesNone on the known-exploited list.
Bea has 159 published vulnerabilities across 22 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Weblogic Server, with 150. If you run Bea software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Bea products have the most vulnerabilities?
Weblogic Server leads with 150 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Bea vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Bea's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Bea flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 84%CVE-2008-3257Critical
Stack-based buffer overflow in the Apache Connector (mod_wl) in Oracle WebLogic Server (formerly BEA WebLogic Server) 10.3 and earlier allows remote attackers to execute arbitrary code via a long HTTP version string,...
- 78%CVE-2001-0098Critical
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.
- 51%CVE-2000-0681Critical
Buffer overflow in BEA WebLogic server proxy plugin allows remote attackers to execute arbitrary commands via a long URL with a .JSP extension.
- 29%CVE-2007-2699High
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...
- 12%CVE-2000-0685Critical
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.
- 12%CVE-2000-0684Critical
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.
- 10.0%CVE-2008-0900Medium
Session fixation vulnerability in BEA WebLogic Server and Express 8.1 SP4 through SP6, 9.2 through MP1, and 10.0 allows remote authenticated users to hijack web sessions via unknown vectors.
- 8.0%CVE-2003-0621Medium
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.
- 7.1%CVE-2002-0106Medium
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.
All Bea products we track.
22 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
- Weblogic Serverweblogic_server150 vulnerabilities18 versions
- Tuxedotuxedo5 vulnerabilities7 versions
- Weblogic Integrationweblogic_integration4 vulnerabilities4 versions
- Weblogic Workshopweblogic_workshop4 vulnerabilities1 version
- Aqualogic Interactionaqualogic_interaction2 vulnerabilities5 versions
- Aqualogic Service Busaqualogic_service_bus2 vulnerabilities4 versions
- Aqualogic Enterprise Securityaqualogic_enterprise_security1 vulnerability3 versions
- Jrockitjrockit1 vulnerability1 version
- Liquid Dataliquid_data1 vulnerability1 version
- Weblogic Mobility Serverweblogic_mobility_server1 vulnerability3 versions
- Aqualogic .net Portlet Toolkitaqualogic_.net_portlet_toolkit0 vulnerabilities1 version
- Aqualogic Analyticsaqualogic_analytics0 vulnerabilities1 version
- Aqualogic Interaction Collaborationaqualogic_interaction_collaboration0 vulnerabilities1 version
- Aqualogic Interaction Content Service for Windows Filesaqualogic_interaction_content_service_for_windows_files0 vulnerabilities2 versions
- Aqualogic Interaction Identity Service for LDAPaqualogic_interaction_identity_service_for_ldap0 vulnerabilities1 version
- Joltjolt0 vulnerabilities1 version
- Jrockit JDKjrockit_jdk0 vulnerabilities1 version
- Jrockit JREjrockit_jre0 vulnerabilities1 version
- Jrockit Mission Controljrockit_mission_control0 vulnerabilities1 version
- Logging Utilitieslogging_utilities0 vulnerabilities1 version
- Weblogic Platformweblogic_platform0 vulnerabilities1 version
- Weblogic Portalweblogic_portal0 vulnerabilities3 versions
Running Bea? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Stack-based buffer overflow in the Apache Connector (mod_wl) in Oracle WebLogic Server (formerly BEA WebLogic Server) 10.3 and earlier allows remote attackers to execute arbitrary code via a long HTTP version string, as demonstrated by a string after "POST /.jsp" in an HTTP request.
- Matched to
- Weblogic Server on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 159 published vulnerabilities across 22 products and 62 versions from Bea.
None of Bea's vulnerabilities is on the list of flaws known to be exploited today.
Weblogic Server, with 150 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a EdgeProtect account and track the Bea products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.