Applies To:Show Versions
- 16.0.0, 15.1.0, 15.0.1, 15.0.0, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.3, 13.1.1, 13.1.0
The Edge Client version 18.104.22.168 is now available on downloads.f5.com.
- User documentation for this release
- Contacting F5
- Legal notices
User documentation for this release
For a comprehensive list of documentation that is relevant to this release, refer to the following pages:
Fixes in 22.214.171.124
The following issues have been fixed in this release.
|745969-1||Previously, in always connected mode, the VPN had trouble connecting after Edge Client version 7.1.5 or earlier auto-updated to version 7.1.6 or later due to certificate problems. This occurred because the Edge Client version 7.1.6 and above are signed with a new certificate, but the Stonewall service did not get updated with the auto-update and remained signed with an old certificate. The VPN now connects properly after auto-updates.|
|842717-5||Fixed the security risk where when the Windows Logon Integration feature is configured for the Edge Client, unauthorized users having physical access to an authorized user's machine could get shell access to internal resources or compromise the availability of the resources.|
|881293-7, 881317-9||Fixed the issue, where the temporary directory created by the Edge Client Windows Installer for extracting various archives and cab files had weak file and folder permissions. This vulnerability allowed the execution of signed .exe and MSI files and could be exploited by an unprivileged user to gain privileged escalation on the client system.|
|882185-7, 882189-7||Fixed a use-after-free memory vulnerability that existed in the Edge Client Windows ActiveX component. This vulnerability allowed an attacker to trigger memory corruption to the browser or execute code from the browser when the attacker crafted a malicious webpage and loaded it into the Internet Explorer browser.|
|899781-3||Previously, attempting to establish a VPN connection using a WinLogon Integration/Custom dialup failed and reported the following error:
...finished with code, -1073740512This issue has been fixed, and now WinLogon Integration/Custom dialup establishes VPN successfully.
|904977-1||Previously, Edge Client did not recognize the onkeypress event when used with a <input> tag, and users could not submit the login form by pressing the Enter key. This issue has been fixed, and now the Edge Client detects the Enter key, and the event attached to the onkeypress event is executed.|
|924941-1||Previously, on a client running Linux or macOS, when the hostname present in /etc/hosts partially matched the hostname configured in the static host entry in Network Access, the local host (/etc/hosts) entry got deleted. With this release, the local host entry is not deleted, and this issue has been fixed.|
|926689-3||Previously, after upgrading from 126.96.36.199.0.276 to 188.8.131.52, users could not connect to RDP via AppTunnel that loads the ActiveX control. With this release, the issue is fixed.|
|928173-1||Previously, the Edge Client for macOS did not properly support the Duo Trusted Endpoints feature when using Client Certificate Authentication. This prevented the client from connecting. It instead displayed the Your Session has Ended error. This issue has been fixed.|
|932781-2||Fixed the issue, where the Edge Client failed to connect on a system running Windows 10 and with Secure Boot enabled.
As a workaround, disable Secure Boot on Windows systems.
Note: Some systems running Windows 10 have Secure Boot enabled by default to ensure that the client computers boot using only software trusted by the computer.
|942953-2||Fixed the issue on Windows 10, the user could not type credentials in the Edge Client window. This occurred because when the user pressed the Ctrl key, the client went into press lock mode and did not allow to type credentials. With this release, skip logic was updated, and this issue is now fixed.|
You can find additional support resources and technical documentation through a variety of sources.
Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.
|AskF5 Knowledge Base||
The storehouse for thousands of knowledgebase articles that help you manage your F5 products more effectively. Whether you want to browse periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
|BIG-IP iHealth Diagnostics and BIG-IP iHealth Viewer||
BIG-IP iHealth Diagnostics identifies issues, including common configuration problems and known software issues. It also provides solutions and links to more information. With BIG-IP iHealth Viewer, you can see the status of your system at-a-glance, drill down for details, and view your network configuration.
Collaborate and share innovations including code samples, new techniques, and other tips, with more than 300,000 F5 users worldwide. DevCentral is the place to ask questions, find solutions, learn to harness the power of F5’s powerful scripting language, iRules, and much more.
|Communications Preference Center||
Here, you can subscribe to a number of communications from F5. For information about the types of notifications F5 provides, see K9970: Subscribing to email notifications regarding F5 products.