OXAS-ADV-2023-0003: OX App Suite Security Advisory

References

• Release Notes
• CSAF document

Vulnerabilities

Frontend themes are defined by user-controllable jslob settings and could point to a malicious resource which gets processed during login.

Product status

Last affected

Remediations

Vendor fix (2023-04-20)

We now sanitize the theme value and use a default fallback if no theme matches.

For products:

• OX App Suite frontend 7.10.6-rev28

Threats

Exploit status

No publicly available exploits are known.

Impact

Malicious script code can be executed within the victims context. This can lead to session hijacking or triggering unwanted actions via the web interface and API. To exploit this an attacker would require temporary access to the users account or lure a user to a compromised account.

The users clientID at "application passwords" was not sanitized or escaped before being added to DOM.

Product status

Last affected

Remediations

Vendor fix (2023-04-20)

We now sanitize the user-controllable clientID parameter.

For products:

• OX App Suite frontend 7.10.6-rev28
• OX App Suite frontend 8.12

Threats

Exploit status

No publicly available exploits are known.

Impact

Malicious script code can be executed within the victims context. This can lead to session hijacking or triggering unwanted actions via the web interface and API. To exploit this an attacker would require temporary access to the users account or lure a user to a compromised account.

The "upsell" widget for the portal allows to specify a product description. This description taken from a user-controllable jslob did not get escaped before being added to DOM.

Product status

Last affected

Remediations

Vendor fix (2023-04-20)

We now sanitize jslob content.

For products:

• OX App Suite frontend 7.10.6-rev28

Threats

Exploit status

No publicly available exploits are known.

Impact

Malicious script code can be executed within the victims context. This can lead to session hijacking or triggering unwanted actions via the web interface and API. To exploit this an attacker would require temporary access to the users account or lure a user to a compromised account.

Custom log-in and log-out locations are used-defined as jslob but were not checked to contain malicious protocol handlers.

Product status

Last affected

Remediations

Vendor fix (2023-04-27)

We now sanitize jslob content for those locations to avoid redirects to malicious content.

For products:

• OX App Suite frontend 7.10.6-rev28

Threats

Exploit status

No publicly available exploits are known.

Impact

Malicious script code can be executed within the victims context. This can lead to session hijacking or triggering unwanted actions via the web interface and API. To exploit this an attacker would require temporary access to the users account or lure a user to a compromised account.

The "OX Chat" web service did not specify a media-type when processing responses by external resources.

Product status

Last affected

Remediations

Vendor fix (2023-04-19)

We are now defining the accepted media-type to avoid code execution.

For products:

• OX App Suite frontend 7.10.6-rev28

Threats

Exploit status

No publicly available exploits are known.

Impact

Malicious script code can be executed within the victims context. This can lead to session hijacking or triggering unwanted actions via the web interface and API. To exploit this an attacker would require temporary access to the users account or lure a user to a compromised account.

The "OX Count" web service did not specify a media-type when processing responses by external resources.

Product status

Last affected

Remediations

Vendor fix (2023-04-19)

We are now defining the accepted media-type to avoid code execution.

For products:

• OX App Suite frontend 7.10.6-rev28

Threats

Exploit status

No publicly available exploits are known.

Impact

Malicious script code can be executed within the victims context. This can lead to session hijacking or triggering unwanted actions via the web interface and API. To exploit this an attacker would require temporary access to the users account or lure a user to a compromised account.

External service lookups for a number of protocols were vulnerable to a time-of-check/time-of-use (TOCTOU) weakness, involving the JDK DNS cache. Attackers that were timing DNS cache expiry correctly were able to inject configuration that would bypass existing network deny-lists.

Product status

Last affected

Remediations

Vendor fix (2023-04-27)

Improvements were made to include deny-lists not only during the check of the provided connection data, but also during use.

For products:

• OX App Suite backend 7.10.6-rev43
• OX App Suite backend 8.11

Threats

Exploit status

No publicly available exploits are known.

Impact

Attackers could exploit this weakness to discover the existence of restricted network infrastructure and service availability.

Attackers with access to user accounts can inject arbitrary control characters to SIEVE mail-filter rules.

Product status

Last affected

Remediations

Vendor fix (2023-04-26)

We have added sanitization to all mail-filter APIs to avoid forwardning control characters to subsystems.

For products:

• OX App Suite backend 7.10.6-rev43
• OX App Suite backend 8.11

Acknowledgments

• Tim 'foobar7' Coen

Threats

Exploit status

No publicly available exploits are known.

Impact

This could be abused to access SIEVE extension that are not allowed by App Suite or to inject rules which would break per-user filter processing, requiring manual cleanup of such rules.

Full-text autocomplete search allows user-provided SQL syntax to be injected to SQL statements.

Product status

Last affected

Remediations

Vendor fix (2023-04-27)

We now properly encode single quotes for SQL FULLTEXT queries.

For products:

• OX App Suite backend 7.10.6-rev43
• OX App Suite backend 8.12

Acknowledgments

• Mehmet 'mdisec' Ince

Threats

Exploit status

No publicly available exploits are known.

Impact

With existing sanitization in place, this can be abused to trigger benign SQL Exceptions but could potentially be escalated to a malicious SQL injection vulnerability.

Functions with insufficient randomness were used to generate authorization tokens of the integrated oAuth Authorization Service.

Product status

Last affected

Remediations

Vendor fix (2023-04-28)

We have updated the implementation to use sources with sufficient randomness to generate authorization tokens.

For products:

• OX App Suite backend 8.12

Acknowledgments

• Eldar 'HakuPiku' Zeynalli

Threats

Exploit status

No publicly available exploits are known.

Impact

Authorization codes were predictable for third parties and could be used to intercept and take over the client authorization process. As a result, other users accounts could be compromised. The oAuth Authorization Service is not enabled by default.

The cacheservice API could be abused to inject parameters with SQL syntax which was insufficiently sanitized before getting executed as SQL statement.

Product status

Last affected

Remediations

Vendor fix (2023-03-14)

We have improved the input check for API calls and filter for potentially malicious content.

For products:

• OX App Suite office 8.11

Acknowledgments

• Mehmet 'mdisec' Ince

Threats

Exploit status

No publicly available exploits are known.

Impact

Attackers with access to a local or restricted network were able to perform arbitrary SQL queries, discovering other users cached data.

The cacheservice API could be abused to indirectly inject parameters with SQL syntax which was insufficiently sanitized and would later be executed when creating new cache groups.

Product status

Last affected

Remediations

Vendor fix ()

We have improved the input check for API calls and filter for potentially malicious content.

For products:

• OX App Suite office 8.11

Acknowledgments

• Mehmet 'mdisec' Ince

Threats

Exploit status

No publicly available exploits are known.

Impact

Attackers with access to a local or restricted network could perform arbitrary SQL queries.

Cacheservice did not correctly check if relative cache object were pointing to the defined absolute location when accessing resources.

Product status

Last affected

Remediations

Vendor fix (2023-04-28)

We have improved path validation and make sure that any access is contained to the defined root directory.

For products:

• OX App Suite office 8.11

Acknowledgments

• Mehmet 'mdisec' Ince

Threats

Exploit status

No publicly available exploits are known.

Impact

An attacker with access to the database and a local or restricted network would be able to read arbitrary local file system resources that are accessible by the services system user account.

In case Cacheservice was configured to use a sproxyd object-storage backend, it would follow HTTP redirects issued by that backend.

Product status

Last affected

Remediations

Vendor fix ()

We have disabled the ability to follow HTTP redirects when connecting to sproxyd resources.

For products:

• OX App Suite office 8.11

Acknowledgments

• Mehmet 'mdisec' Ince

Threats

Exploit status

No publicly available exploits are known.

Impact

An attacker with access to a local or restricted network with the capability to intercept and replay HTTP requests to sproxyd (or who is in control of the sproxyd service) could perform a server-side request-forgery attack and make Cacheservice connect to unexpected resources.