Openfire Cross-site Scripting

Ignite Realtime Openfire 4.6.0 has create-bookmark.jsp groupchatJID Stored XSS. (2020-12-12, CVE-2020-35199)

Ignite Realtime Openfire 4.6.0 has create-bookmark.jsp users Stored XSS. (2020-12-12, CVE-2020-35201)

Ignite Realtime Openfire 4.6.0 has plugins/clientcontrol/spark-form.jsp Reflective XSS. (2020-12-12, CVE-2020-35200)

Ignite Realtime Openfire 4.6.0 has plugins/dbaccess/db-access.jsp sql Stored XSS. (2020-12-12, CVE-2020-35202)

Ignite Realtime Openfire 4.6.0 has plugins/bookmarks/create-bookmark.jsp Stored XSS. (2020-12-11, CVE-2020-35127)

A Reflected XSS vulnerability was discovered in Ignite Realtime Openfire version 4.5.1. The XSS vulnerability allows remote attackers to inject arbitrary web script or HTML via the GET request "searchName", "searchValue", "searchDescription", "searchDefaultValue","searchPlugin", "searchDescription" and "searchDynamic" in server-properties.jsp and security-audit-viewer.jsp (2020-09-02, CVE-2020-24604)

Ignite Realtime Openfire 4.5.1 has a reflected Cross-site scripting vulnerability which allows an attacker to execute arbitrary malicious URL via the vulnerable GET parameter searchName", "searchValue", "searchDescription", "searchDefaultValue","searchPlugin", "searchDescription" and "searchDynamic" in the Server Properties and Security Audit Viewer JSP page (2020-09-02, CVE-2020-24602)

In Ignite Realtime Openfire 4.5.1 a Stored Cross-site Vulnerability allows an attacker to execute an arbitrary malicious URL via the vulnerable POST parameter searchName", "alias" in the import certificate trusted page (2020-09-02, CVE-2020-24601)

Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp driver parameter. (2020-03-19, CVE-2019-20525)

Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp password parameter. (2020-03-19, CVE-2019-20526)

Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp serverURL parameter. (2020-03-19, CVE-2019-20527)

Ignite Realtime Openfire 4.4.1 allows XSS via the setup/setup-datasource-standard.jsp username parameter. (2020-03-18, CVE-2019-20528)

An XSS issue was discovered in Ignite Realtime Openfire 4.4.4 via alias to Manage Store Contents. (2020-01-08, CVE-2019-20363)

An XSS issue was discovered in Ignite Realtime Openfire 4.4.4 via cacheName to SystemCacheDetails.jsp. (2020-01-08, CVE-2019-20364)

An XSS issue was discovered in Ignite Realtime Openfire 4.4.4 via isTrustStore to Manage Store Contents. (2020-01-08, CVE-2019-20366)

An XSS issue was discovered in Ignite Realtime Openfire 4.4.4 via search to the Users/Group search page. (2020-01-08, CVE-2019-20365)

Ignite Realtime Openfire before 4.4.1 has reflected XSS via an LDAP setup test. (2019-08-23, CVE-2019-15488)

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. (2018-06-13, CVE-2018-11688)

Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.

The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:

https://server.com/confirmation?message=Transaction+Complete

what results in:

<span>Confirmation: Transaction Complete</span>

In that case the message can be modified to become a valid Javascript code, e.g.:

https://server.com/confirmation?message=<script>dangerous javascript code here</script>

and it will be executed locally by the user's browser with full access to the user's personal application/browser data:

<span>Confirmation: <script>dangerous javascript code here</script></span>