Skip to content

← Public intelligence

Maven package

org.igniterealtime.openfire:parent

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

11 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedMavenPublished

    XSS in Ignite Realtime Openfire via isTrustStore

    CVE-2019-20366 · GHSA-m6pr-xcrm-4qqp

    Affected
    • Maven org.igniterealtime.openfire:parent <= 4.4.4
    Fixed in
    4.5.0· Vendor fix available
    Issue
    An XSS issue was discovered in Ignite Realtime Openfire 4.4.4 via isTrustStore to Manage Store Contents.

    Recommended action: Upgrade to 4.5.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.1MavenPublished

    Ignite Realtime Openfire allows Cross-site Scripting

    CVE-2019-20526 · GHSA-5cg5-7vw6-jw4r

    Affected
    • Maven org.igniterealtime.openfire:parent < 4.4.2
    Fixed in
    4.4.2· Vendor fix available
    Issue
    Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp password parameter. This issue was fixed in version 4.4.2.

    Recommended action: Upgrade to 4.4.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 6.1MavenPublished

    Ignite Realtime Openfire allows Cross-site Scripting

    CVE-2019-20527 · GHSA-22c6-3h88-26m3

    Affected
    • Maven org.igniterealtime.openfire:parent < 4.4.2
    Fixed in
    4.4.2· Vendor fix available
    Issue
    Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp serverURL parameter. This issue was fixed in version 4.4.2.

    Recommended action: Upgrade to 4.4.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Medium, CVSS 6.1MavenPublished

    Ignite Realtime Openfire allows Cross-site Scripting

    CVE-2019-20525 · GHSA-h2mq-p9r5-wh94

    Affected
    • Maven org.igniterealtime.openfire:parent < 4.4.2
    Fixed in
    4.4.2· Vendor fix available
    Issue
    Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp driver parameter. This issue was fixed in version 4.4.2.

    Recommended action: Upgrade to 4.4.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  5. Critical, CVSS 9.8MavenPublished

    Ignite Realtime Openfire vulnerable to Server Side Request Forgery

    CVE-2019-18394 · GHSA-mfjw-x4q4-69p9

    Affected
    • Maven org.igniterealtime.openfire:parent < 4.5.0-beta
    Fixed in
    4.5.0-beta· Vendor fix available
    Issue
    A Server Side Request Forgery (SSRF) vulnerability in FaviconServlet.java in Ignite Realtime Openfire through 4.4.2 allows attackers to send arbitrary HTTP GET requests. The issue is fixed in version 4.5.0-beta.

    Recommended action: Upgrade to 4.5.0-beta (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  6. Medium, CVSS 5.3MavenPublished

    Ignite Realtime Openfire directory traversal vulnerability

    CVE-2019-18393 · GHSA-59h8-h34r-q9cv

    Affected
    • Maven org.igniterealtime.openfire:parent < 4.5.0-beta
    Fixed in
    4.5.0-beta· Vendor fix available
    Issue
    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. Version 4.5.0-beta contains a fix for the issue.

    Recommended action: Upgrade to 4.5.0-beta (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  7. High, CVSS 8.7MavenPublished

    Ignite Realtime Openfire vulnerable to XMPPbomb attack

    CVE-2014-2741 · GHSA-j5qh-cp3p-2h87

    Affected
    • Maven org.igniterealtime.openfire:parent < 3.9.2
    Fixed in
    3.9.2· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 3.9.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  8. Medium, CVSS 4.8MavenPublished

    Ignite Realtime Openfire Server has Cross-site Scripting vulnerability in admin console

    CVE-2017-15911 · GHSA-v3h2-4j2r-wqj8

    Affected
    • Maven org.igniterealtime.openfire:parent < 4.1.7
    Fixed in
    4.1.7· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 4.1.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  9. Medium, CVSS 6.1MavenPublished

    Ignite Realtime Openfire vulnerable to cross-site scripting

    CVE-2018-11688 · GHSA-jphj-5g3m-w7x6

    Affected
    • Maven org.igniterealtime.openfire:parent < 3.9.2
    Fixed in
    3.9.2· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 3.9.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  10. UnratedMavenPublished

    Ignite Realtime Openfire Allows Users to Change Passwords of Arbitrary Accounts

    CVE-2009-1595 · GHSA-r62w-x9pp-jrqp

    Affected
    • Maven org.igniterealtime.openfire:parent < 3.6.4
    Fixed in
    3.6.4· Vendor fix available
    Issue
    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 passwdchange action.

    Recommended action: Upgrade to 3.6.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  11. UnratedMavenPublished

    Ignite Realtime Openfire allows remote authenticated users to cause a denial of service

    CVE-2008-1728 · GHSA-x337-43mr-gg3h

    Affected
    • Maven org.igniterealtime.openfire:parent < 3.5.0
    Fixed in
    3.5.0· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 3.5.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →