Serv-U 15.5 release notes
Release date: October 16, 2024
Here's what's new in Serv-U File Server 15.5.
Learn more
- See the Serv-U release notes aggregator to view release notes for multiple versions of Serv-U on a single page.
- See Serv-U 15.5 system requirements to learn about prerequisites for running and installing Serv-U 15.5.
- See the Serv-U 15.5 Administrator Guide to learn how to work with Serv-U.
New features and improvements in Serv-U
Last updated:
-
Serv-U multi-factor authentication has now been extended to database users.
-
A new Serv-U login page provides modern custom branding.
-
New AES-GCM ciphers in Serv-U provide authenticated encryption.
-
The $FileShareComments and $FileShareSubject variables are now supported in Serv-U Events.
-
New Event types for MFA are also available.
Fixes
| Case number | Description |
|---|---|
| N/A | Serv-U now accurately accounts for session activities when calculating idle time. |
| N/A | The Upload dialog displays correctly in the new Web Client when the user sends fileshare sources, so that a guest user can upload only from the local computer. |
| N/A | The User Login Failure event triggers after the user enters an incorrect time-based one-time password (TOTP) password for the third time. |
| N/A | Serv-U allows uploads only within the size limits set in the Domain home directory. |
| 01561245 | Serv-U successfully completes SFTP sessions while connecting through the Gateway. |
| 01577428, 01592137 | The log rotation functionality accurately controls the number of log files at the user and group level. |
| 01608700 | Serv-U correctly authenticates HTTP sessions, even when passwords contain special characters. |
| 01598285, 01696417 | New file sharing option works as expected and no longer displays an error stating that the specified file or directory does not exist. |
| N/A | Users can log in successfully from the web client after having changed a password that contains special symbols. |
| 01609920, 01668949 | OpenSSL was upgraded from version 3.0.13 to version 3.0.15. |
| 01610037, 01732343 | Serv-U functions correctly when database user of admin type lists database groups in Management Console. |
| 01617752 | The system variable $SessionID is working as expected with File management events. |
| 01623240, 01746871 | Users can successfully download and open files via FTP Voyager JV. |
| 01668875 | Serv-U mobile web client login works correctly. |
| 01674806 | LDAP server port no longer resets after initial configuration. |
| 01673180 | New file sharing interface now allows the creation of Sends or Requests while the limit "Allow user-defined guest link expiration" is set to "No." |
| 01625009, 01636506 | Serv-U no longer blocks anonymous accounts if the accounts do not have a password. |
| N/A | Serv-U can accurately validate the password using the Integration DLL. |
| N/A | System variable $IP works correctly on Linux. |
| N/A | Error message displays after user session times out in new web client. |
| N/A | Serv-U users can select and download multiple zipped folders with files in them from the new web client simultaneously without issue. |
| N/A | After downloading two or more files from the home directory as a zipped directory archive, the central directory file header no longer misses the zip-stream flag. Zipped files can be extracted. |
CVEs
Last updated: 10/16/2024
SolarWinds would like to thank the security researchers below for reporting on the issue in a responsible manner and working with our security, product, and engineering teams to fix the vulnerability.
SolarWinds CVEs
| CVE-ID | Vulnerability Title | Description | Severity | Credit |
|---|---|---|---|---|
| CVE-2024-45711 | Directory Traversal Remote Code Execution | SolarWinds Serv-U is vulnerable to a directory traversal vulnerability where remote code execution is possible depending on privileges given of the authenticated user. This is present when software environment variables are abused. Authentication is required. | 7.5 High | Anonymous working with Trend Micro Zero Day Initiative |
| CVE-2024-45714 | Stored XSS Vulnerability | Application is vulnerable to Cross-Site Scripting (XSS). An authenticated attacker with users permissions can modify a variable with a payload. | 4.8 Medium | Simon Wattier |
Third Party CVEs
| CVE-ID | Vulnerability Title | Description | Severity |
|---|---|---|---|
| CVE-2024-4741 | OpenSSL Denial of Service Vulnerability | OpenSSL Denial of Service Vulnerability-Not published on CVE.org | 3.7 Low |
| CVE-2024-5535 | OpenSSL Denial of Service Vulnerability | ssue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application. The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists). This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem. In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur. This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available. | 9.1 Critical considered Low by OpenSSL |
| CVE-2024-4603 | OpenSSL Denial of Service Vulnerability | Checking excessively long DSA keys or parameters may be very slow. Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks. An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue. | 5.5 Medium |
Installation or upgrade
Last updated:
For new installations, you can download the installation file from the Serv-U product page on https://www.solarwinds.com or from the Customer Portal. For more information, see Install the SolarWinds Serv-U File Server.
For more information about upgrades, see Upgrade Serv-U File Server.
End of life
| Version | EoL Announcements | EoE Effective Dates | EoL Effective Dates |
|---|---|---|---|
| 15.1.7 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.1.7 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.1.7 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.1.7. |
| 15.2 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.2 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.2 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.2. |
| 15.2.1 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.2.1 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.2.1 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.2.1. |
| 15.2.2 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.2.2 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.2.2 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for 15.2.2. |
| 15.2.3 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.2.3 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.2.3 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.2.3. |
| 15.2.4 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.1.7 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.2.4 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.2.4. |
| 15.2.5 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.1.7 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.2.5 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.2.5. |
| 15.3 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.2.4 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.3 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.3. |
| 15.3.1 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.1.7 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.3.1 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.3.1. |
| 15.3.2 | December 5, 2023: End-of-Life (EoL) announcement – Customers on Serv-U 15.3.2 should begin transitioning to the latest version of Serv-U. | February 5, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.3.2 will no longer be actively supported by SolarWinds. | February 5, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.3.2. |
| 15.4.0 | April 17, 2024: End-of-Life (EoL) announcement – Customers on Serv-U 15.4.0 should begin transitioning to the latest version of Serv-U. | July 17, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.4.0 will no longer be actively supported by SolarWinds. | July 17, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.4.0. |
| 15.4.1 | October 16, 2024: End-of-Life (EoL) announcement – Customers on Serv-U 15.4.1 should begin transitioning to the latest version of Serv-U. | December 16, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Serv-U 15.4.1 will no longer be actively supported by SolarWinds. | December 16, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Serv-U 15.4.1. |
See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier Serv-U versions, see Serv-U release history.
Deprecation notice
Last updated:
The following platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms, and avoid using deprecated features.
| Type | Details |
|---|---|
| Web client modules | Java-based Serv-U web client modules FTP Voyager JV and Web Client Pro will be discontinued in an upcoming release. However, these modules are still available in version 15.5, together with the new Serv-U web client to support a migration path. |
Legal notices
© 2024 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.