WaratekVRT Sign in

Medium CWE-200 CVEs with a working exploit

19 CVEs, 2 protected by Waratek

Reset
More filters (1)
Columns
CWE CWE-200✕
Overview 19 matches · 2 protected · 0 exploited · 0 CISA KEV · 8 EPSS ≥ 0.5
19matches 2protected10.5% 0exploited0.0% 0CISA KEV0.0% 8EPSS ≥ 0.542.1%
Protected by Waratek 2 10.5% Rule in development 0 0.0% Mitigation candidate 17 89.5% No exploit published 0 0.0%
Critical 0 0.0% High 0 0.0% Medium 19 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 2 10.5% partly blocked 0 0.0% not blocked 17 89.5% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 19 100.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 2 / year
Mitigation candidate: 17Protected by Waratek: 2 Medium: 19 not blocked: 17blocked by ARMR today: 2 Working exploit published: 19
20001 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20011 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20021 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20030 20040 20052 Mitigation candidate2 Medium2 not blocked2 Working exploit published2 20061 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20072 Mitigation candidate2 Medium2 not blocked2 Working exploit published2 20081 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20091 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20100 20110 20120 20131 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20140 20150 20160 20170 20181 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20192 Protected by Waratek1 Mitigation candidate1 Medium2 blocked by ARMR today1 not blocked1 Working exploit published2 20201 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20212 Protected by Waratek1 Mitigation candidate1 Medium2 blocked by ARMR today1 not blocked1 Working exploit published2 20220 20231 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20241 Mitigation candidate1 Medium1 not blocked1 Working exploit published1
2000200220042006200820102012201420162018202020222024
19 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2023-50290 Medium 2024-01-15 Mitigation candidate Working exploit published Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Solr. The Solr Metrics API publishes all unprotected environment variables available to each Apache Solr instance. Users are able to specify which environment variables to hide, however, the default list is designed to work for known secret Java system properties. Environment variables cannot be strictly defined in Solr, like Java system properties can be, and may be set for the entire host, unlike Java system properties which are set per-Java-proccess. The Solr Metrics API is protected by the "metrics-read" permission. Therefore, Solr Clouds with Authorization setup will only be vulnerable via users with the "metrics-read" permission. This issue affects Apache Solr: from 9.0.0 before 9.3.0. Users are recommended to upgrade to version 9.3.0 or later, in which environment variables are not published via the Metrics API.
CVE-2023-50720 Medium 2023-12-15 Mitigation candidate Working exploit published XWiki Platform is a generic wiki platform. Prior to versions 14.10.15, 15.5.2, and 15.7-rc-1, the Solr-based search in XWiki discloses the email addresses of users even when obfuscation of email addresses is enabled. To demonstrate the vulnerability, search for `objcontent:email*` using XWiki's regular search interface. This has been fixed in XWiki 14.10.15, 15.5.2 and 15.7RC1 by not indexing email address properties when obfuscation is enabled. There are no known workarounds for this vulnerability.
CVE-2021-22145 Medium 2021-07-21 Mitigation candidate Working exploit published A memory disclosure vulnerability was identified in Elasticsearch 7.10.0 to 7.13.3 error reporting. A user with the ability to submit arbitrary queries to Elasticsearch could submit a malformed query that would result in an error message returned containing previously used portions of a data buffer. This buffer could contain sensitive information such as Elasticsearch documents or authentication details.
CVE-2021-28164 Medium 2021-04-01 Protected by Waratek Working exploit published In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segments to access protected resources within the WEB-INF directory. For example a request to /context/%2e/WEB-INF/web.xml can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.
CVE-2020-2103 Medium 2020-01-29 Mitigation candidate Working exploit published Jenkins 2.218 and earlier, LTS 2.204.1 and earlier exposed session identifiers on a user's detail object in the whoAmI diagnostic page.
CVE-2019-10405 Medium 2019-09-25 Mitigation candidate Working exploit published Jenkins 2.196 and earlier, LTS 2.176.3 and earlier printed the value of the "Cookie" HTTP request header on the /whoAmI/ URL, allowing attackers exploiting another XSS vulnerability to obtain the HTTP session cookie despite it being marked HttpOnly.
CVE-2019-13237 Medium 2019-08-27 Protected by Waratek Working exploit published In Alkacon OpenCms 10.5.4 and 10.5.5, there are multiple resources vulnerable to Local File Inclusion that allow an attacker to access server resources: clearhistory.jsp, convertxml.jsp, group_new.jsp, loginmessage.jsp, xmlcontentrepair.jsp, and /system/workplace/admin/history/settings/index.jsp.
CVE-2018-1322 Medium 2018-03-20 Mitigation candidate Working exploit published An administrator with user search entitlements in Apache Syncope 1.2.x before 1.2.11, 2.0.x before 2.0.8, and unsupported releases 1.0.x and 1.1.x which may be also affected, can recover sensitive security values using the fiql and orderby parameters.
CVE-2013-1814 Medium 2013-03-14 Mitigation candidate Working exploit published The users/get program in the User RPC API in Apache Rave 0.11 through 0.20 allows remote authenticated users to obtain sensitive information about all user accounts via the offset parameter, as demonstrated by discovering password hashes in the password field of a response.
CVE-2009-0580 Medium 2009-06-05 Mitigation candidate Working exploit published Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when FORM authentication is used, allows remote attackers to enumerate valid usernames via requests to /j_security_check with malformed URL encoding of passwords, related to improper error checking in the (1) MemoryRealm, (2) DataSourceRealm, and (3) JDBCRealm authentication realms, as demonstrated by a % (percent) value for the j_password parameter.
CVE-2007-5333 Medium 2008-02-12 Mitigation candidate Working exploit published Apache Tomcat 6.0.0 through 6.0.14, 5.5.0 through 5.5.25, and 4.1.0 through 4.1.36 does not properly handle (1) double quote (") characters or (2) %5C (encoded backslash) sequences in a cookie value, which might cause sensitive information such as session IDs to be leaked to remote attackers and enable session hijacking attacks. NOTE: this issue exists because of an incomplete fix for CVE-2007-3385.
CVE-2007-3382 Medium 2007-08-14 Mitigation candidate Working exploit published Apache Tomcat 6.0.0 to 6.0.13, 5.5.0 to 5.5.24, 5.0.0 to 5.0.30, 4.1.0 to 4.1.36, and 3.3 to 3.3.2 treats single quotes ("'") as delimiters in cookies, which might cause sensitive information such as session IDs to be leaked and allow remote attackers to conduct session hijacking attacks.
CVE-2007-2353 Medium 2007-04-30 Mitigation candidate Working exploit published Apache Axis 1.0 allows remote attackers to obtain sensitive information by requesting a non-existent WSDL file, which reveals the installation path in the resulting exception message.
CVE-2006-3835 Medium 2006-07-25 Mitigation candidate Working exploit published Apache Tomcat 5 before 5.5.17 allows remote attackers to list directories via a semicolon (;) preceding a filename with a mapped extension, as demonstrated by URLs ending with /;index.jsp and /;help.do.
CVE-2005-4703 Medium 2005-12-31 Mitigation candidate Working exploit published Apache Tomcat 4.0.3, when running on Windows, allows remote attackers to obtain sensitive information via a request for a file that contains an MS-DOS device name such as lpt9, which leaks the pathname in an error message, as demonstrated by lpt9.xtp using Nikto.
CVE-2005-3747 Medium 2005-11-22 Mitigation candidate Working exploit published Unspecified vulnerability in Jetty before 5.1.6 allows remote attackers to obtain source code of JSP pages, possibly involving requests for .jsp files with URL-encoded backslash ("%5C") characters. NOTE: this might be the same issue as CVE-2006-2758.
CVE-2002-1148 Medium 2002-10-11 Mitigation candidate Working exploit published The default servlet (org.apache.catalina.servlets.DefaultServlet) in Tomcat 4.0.4 and 4.1.10 and earlier allows remote attackers to read source code for server files via a direct request to the servlet.
CVE-2001-0590 Medium 2001-08-02 Mitigation candidate Working exploit published Apache Software Foundation Tomcat Servlet prior to 3.2.2 allows a remote attacker to read the source code to arbitrary 'jsp' files via a malformed URL request which does not end with an HTTP protocol specification (i.e. HTTP/1.0).
CVE-2000-0759 Medium 2000-10-20 Mitigation candidate Working exploit published Jakarta Tomcat 3.1 under Apache reveals physical path information when a remote attacker requests a URL that does not exist, which generates an error message that includes the physical path.