This article explains how selected third-party software and technologies relate to standard Parallels Remote Application Server (RAS) components.
A vulnerability reported for third-party software does not automatically mean that Parallels RAS is affected. The reported component must be identified and checked against the RAS components installed in the environment.
Customer environments may also contain software that is installed and managed independently of RAS. Such software should be assessed according to the security guidance provided by the corresponding software vendor.
Third-party component applicability for RAS
| Component or technology | Used by standard RAS components? | Details |
|---|---|---|
| Java Oracle Java SE, JRE, JDK, or GraalVM |
No | Java is not used by standard Parallels RAS components and is not required for normal RAS operation. It may be installed independently for customer applications or other third-party software. |
| Node.js | Yes | Node.js is used by the RAS User Portal on the Secure Gateway. Vulnerabilities affecting the Node.js version used by this component may therefore be relevant to RAS. |
| .NET .NET Runtime |
Yes | .NET is used by applicable RAS components. Security updates for the .NET runtime may therefore be relevant to RAS. |
| nginx | No | nginx is not used by standard Parallels RAS components. It may be installed independently by the customer as a reverse proxy, load balancer, SSL termination service, or part of another application. |
| PHP | No | PHP is not used by the standard RAS Secure Gateway or RAS User Portal components. |
Important: A component may be installed on a server that also hosts RAS without being part of RAS. The presence of third-party software in the RAS environment does not, by itself, indicate that the software is included in the RAS product.
For additional information, see:
- PHP2Shell vulnerabilities do not affect Parallels RAS components
- Security update for Parallels RAS: Node.js and .NET components
HALB applicability
Parallels RAS High Availability Load Balancer (HALB) is a separate, Linux-based appliance. HALB must therefore be assessed separately from the RAS components that run on Windows.
| Component or technology | Used by HALB? | Details |
|---|---|---|
| Linux kernel | Yes | HALB is a Linux-based appliance and uses a Linux kernel. Linux kernel vulnerabilities may therefore be relevant to HALB. |
| HAProxy | Yes | HALB uses HAProxy to provide load-balancing functionality. |
| keepalived | Yes | HALB uses keepalived to provide high availability and virtual IP management. |
| PHP | No | HALB does not use PHP. HAProxy and keepalived provide the relevant HALB functionality. |
For additional information about HALB security updates and Linux kernel vulnerabilities, see Security update for Parallels RAS HALB: Linux kernel vulnerability.
How to assess third-party components
If a third-party component is used by a Parallels RAS component, vulnerabilities affecting that component may be relevant to RAS. In such cases, the component should be assessed together with the applicable RAS version, update, or hotfix.
If the third-party component is installed independently by the customer, for example as part of another application, reverse proxy, load balancer, monitoring solution, security product, or infrastructure service, it should be assessed and updated separately according to the software vendor's security guidance.
For HALB-specific vulnerabilities, assess the HALB appliance separately from the Windows-based RAS components. HALB is a Linux-based appliance and may be affected by vulnerabilities in its Linux kernel or other software used by the appliance.
To help maintain the stability of the RAS environment, do not manually replace, remove, or modify files managed by RAS or HALB as a vulnerability workaround unless instructed by Parallels Support.
If it is unclear whether a reported component is used by RAS, used by HALB, or installed independently in the customer environment, Parallels Support can help review the information.
Contacting Parallels Support
If you need assistance determining whether a reported component or vulnerability relates to Parallels RAS or HALB, you can contact Parallels Support for further review.
It may be helpful to contact Parallels Support in the following situations:
- You would like confirmation about whether a specific component or CVE applies to Parallels RAS or HALB.
- You are unable to determine whether a file, service, package, or appliance component belongs to RAS or HALB.
- A reported component is located in an RAS or HALB installation directory.
- The ownership of a service, executable, package, or library installed on an RAS server or HALB appliance is unclear.
- A reported Node.js or .NET version cannot be mapped to the installed RAS build.
- A reported Linux kernel, HAProxy, or keepalived vulnerability cannot be mapped to the installed HALB version.
- A vulnerability scanner identifies a component that requires additional investigation.
When contacting Parallels Support, please include the following information where available:
- RAS or HALB version and build.
- Affected host or appliance.
- RAS role installed on the affected host, if applicable.
- CVE or vulnerability identifier.
- Scanner output and reported severity.
- Detected component and version.
- Affected file path, package name, service name, or executable path.
- Relevant screenshots or scan reports.
- A RASReport, where available.
For information about preparing a RAS support request, see How to prepare a Parallels RAS support request.
For instructions on creating a support request, see How to create a support request.
Note: Do not manually replace, delete, or modify RAS- or HALB-managed files as a vulnerability workaround unless instructed by Parallels Support.
Was this article helpful?
Tell us how we can improve it.