Overview 12 matches · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
12matches
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
12
100.0%
Outside Waratek scope
0
0.0%
Not applicable
0
0.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
12
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
1
8.3%
Forecast only
0
0.0%
No public exploit
11
91.7%
split by
peak 5 / year
20081
No exploit published1
Medium1
not blocked1
No public exploit1
20090
20100
20110
20120
20130
20141
No exploit published1
High1
not blocked1
No public exploit1
20150
20160
20171
No exploit published1
Medium1
not blocked1
No public exploit1
20181
No exploit published1
Medium1
not blocked1
No public exploit1
20191
No exploit published1
Medium1
not blocked1
No public exploit1
20205
No exploit published5
Medium5
not blocked5
No public exploit5
20210
20220
20230
20241
No exploit published1
Critical1
not blocked1
Proof of concept only1
20251
No exploit published1
Medium1
not blocked1
No public exploit1
200920112013201520172019202120232025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-59154 | Medium | 2025-09-15 | No exploit published | No public exploit | Openfire is an XMPP server licensed under the Open Source Apache License. Openfire’s SASL EXTERNAL mechanism for client TLS authentication contains a vulnerability in how it extracts user identities from X.509 certificates. Instead of parsing the structured ASN.1 data, the code calls X509Certificate.getSubjectDN().getName() and applies a regex to look for CN=. This method produces a provider-dependent string that does not escape special characters. In SunJSSE (sun.security.x509.X500Name), for example, commas and equals signs inside attribute values are not escaped. As a result, a malicious certificate can embed CN= inside another attribute value (e.g. OU="CN=admin,"). The regex will incorrectly interpret this as a legitimate Common Name and extract admin. If SASL EXTERNAL is enabled and configured to map CNs to user accounts, this allows the attacker to impersonate another user. The fix is included in Openfire 5.0.2 and 5.1.0. |
| CVE-2024-25421 | Critical | 2024-03-26 | No exploit published | Proof of concept only | An issue in Ignite Realtime Openfire v.4.9.0 and before allows a remote attacker to escalate privileges via the ROOM_CACHE component. |
| 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-2014-2741 | High | 2014-04-11 | No exploit published | No public exploit | nio/XMLLightweightParser.java in Ignite Realtime Openfire before 3.9.2 does not properly restrict the processing of compressed XML elements, which allows remote attackers to cause a denial of service (resource consumption) via a crafted XMPP stream, aka an "xmppbomb" attack. |
| CVE-2008-1728 | Medium | 2008-04-11 | No exploit published | No public exploit | ConnectionManagerImpl.java in Ignite Realtime Openfire 3.4.5 allows remote authenticated users to cause a denial of service (daemon outage) by triggering large outgoing queues without reading messages. |