WaratekVRT Sign in
Reset
More filters (1)
Columns
Vendor igniterealtime✕
Overview 10 matches · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
10matches 0protected0.0% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 10 100.0%
Critical 0 0.0% High 0 0.0% Medium 10 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 10 100.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 10 100.0%
split by peak 5 / quarter
No exploit published: 10 Medium: 10 not blocked: 10 No public exploit: 10
Q4 141 No exploit published1 Medium1 not blocked1 No public exploit1 Q1 150 Q2 150 Q3 150 Q4 150 Q1 160 Q2 160 Q3 160 Q4 160 Q1 171 No exploit published1 Medium1 not blocked1 No public exploit1 Q2 170 Q3 170 Q4 171 No exploit published1 Medium1 not blocked1 No public exploit1 Q1 180 Q2 181 No exploit published1 Medium1 not blocked1 No public exploit1 Q3 180 Q4 180 Q1 190 Q2 190 Q3 191 No exploit published1 Medium1 not blocked1 No public exploit1 Q4 190 Q1 205 No exploit published5 Medium5 not blocked5 No public exploit5
Q1 15Q3 15Q1 16Q3 16Q1 17Q3 17Q1 18Q3 18Q1 19Q3 19Q1 20
10 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-2019-20527 Medium 2020-03-19 No exploit published No public exploit Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp serverURL parameter.
CVE-2019-20526 Medium 2020-03-19 No exploit published No public exploit Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp password parameter.
CVE-2019-20525 Medium 2020-03-19 No exploit published No public exploit Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp driver parameter.
CVE-2019-20528 Medium 2020-03-18 No exploit published No public exploit Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp username parameter.
CVE-2019-20366 Medium 2020-01-08 No exploit published No public exploit An XSS issue was discovered in Ignite Realtime Openfire 4.4.4 via isTrustStore to Manage Store Contents.
CVE-2019-15488 Medium 2019-08-23 No exploit published No public exploit Ignite Realtime Openfire before 4.4.1 has reflected XSS via an LDAP setup test.
CVE-2018-11688 Medium 2018-06-13 No exploit published No public exploit Ignite Realtime Openfire before 3.9.2 is vulnerable to cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability via a crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.
CVE-2017-15911 Medium 2017-10-26 No exploit published No public exploit The Admin Console in Ignite Realtime Openfire Server before 4.1.7 allows arbitrary client-side JavaScript code execution on victims who click a crafted setup/setup-host-settings.jsp?domain= link, aka XSS. Session ID and data theft may follow as well as the possibility of bypassing CSRF protections, injection of iframes to establish communication channels, etc. The vulnerability is present after login into the application.
CVE-2016-10027 Medium 2017-01-12 No exploit published No public exploit Race condition in the XMPP library in Smack before 4.1.9, when the SecurityMode.required TLS setting has been set, allows man-in-the-middle attackers to bypass TLS protections and trigger use of cleartext for client authentication by stripping the "starttls" feature from a server response.
CVE-2014-5075 Medium 2014-10-25 No exploit published No public exploit The Ignite Realtime Smack XMPP API 4.x before 4.0.2, and 3.x and 2.x when a custom SSLContext is used, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.