Medium Igniterealtime CVEs
12 CVEs, 1 exploited, 1 protected by Waratek
Overview 12 matches · 1 protected · 1 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
1
8.3%
Rule in development
0
0.0%
Mitigation candidate
1
8.3%
No exploit published
10
83.3%
blocked by ARMR today
1
8.3%
partly blocked
0
0.0%
not blocked
11
91.7%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
8.3%
Working exploit published
1
8.3%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
10
83.3%
split by
peak 5 / year
20091
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20100
20110
20120
20130
20141
No exploit published1
Medium1
not blocked1
No public exploit1
20150
20160
20172
No exploit published2
Medium2
not blocked2
No public exploit2
20181
No exploit published1
Medium1
not blocked1
No public exploit1
20192
Protected by Waratek1
No exploit published1
Medium2
blocked by ARMR today1
not blocked1
Exploited1
No public exploit1
20205
No exploit published5
Medium5
not blocked5
No public exploit5
200920102011201220132014201520162017201820192020
| 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-18393 | Medium | 2019-10-24 | Protected by Waratek | Exploited | PluginServlet.java in Ignite Realtime Openfire through 4.4.2 does not ensure that retrieved files are located under the Openfire home directory, aka a directory traversal vulnerability. |
| 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. |
| CVE-2009-1595 | Medium | 2009-05-11 | Mitigation candidate | Working exploit published | The jabber:iq:auth implementation in IQAuthHandler.java in Ignite Realtime Openfire before 3.6.4 allows remote authenticated users to change the passwords of arbitrary accounts via a modified username element in a passwd_change action. |