GEO 2.3.39 Release Notes

Refer to the sections below for details about firmware version 2.3.39. This was released on 2nd August 2017.

Issues Resolved

PD-9556

Fixed an issue with GEO custom locations.

PD-9551

It is possible to have GEO FQDN names containing underscores.

PD-9059

Improved GEO error handling.

PD-8118

Added a parameter to get the GEO update interface using the API.

PD-9581

Fixed an issue with the output of the PowerShell Set-GeoMiscParameter command.

Known Issues

PD-10980

A critical vulnerability (CVE-2018-9091) in the Multi-Tenant LoadMaster Operating System (MT-LMOS) related to Session Management could allow an unauthorized, remote attacker to bypass security protections, gain system privileges, and execute elevated commands such as ls, ps, cat, and so on, thereby compromising the system. Through this remote execution, in certain cases, exposure of sensitive system data such as certificates, private keys, and other information may be possible.
Further information can be found here: Mitigation For Remote Access Execution Vulnerability.

PD-8725

Proximity and Location Based scheduling do no work with IPv6 source addresses.

PD-9765

GEO does not support DNS TCP requests from unknown sources.

PD-10155

Issue with configuration corruption causes some GEO features not to function.

PD-9572

There are discrepancies displaying the location latitude/longitude parameter vales for some RESTful API commands.

PD-9570

There is a typo in the removecountry API response error message.

PD-9539

Issues with the PowerShell New-GeoCluster command in a specific scenario.

PD-9523

In a specific scenario, the RESTful API returns a success message when fetching a non-existing GEO FQDN.

Was this article helpful?

0 out of 0 found this helpful

Comments