Nowość! Produkt przeznaczony do ochrony aplikacji webowych został zaktualizowany do wersji 6.3.4. W nowej wersji wyeliminowano problemy zgłoszone przez administratorów, które powodowały na przykład restart systemu, przerywanie przesyłania plików przez FTP, czy wycieki pamięci. Zachęcamy do zapoznania się z listą zmian oraz do aktualizacji oprogramowania.
Rozwiązane problemy:
| Bug ID | Description |
|---|---|
| 0635271 | The length of the URL requested by the client exceeds the site publish URL limit, which results in authentication failure. |
| 0633427 | Uploading large file through FTP fails when the back end server’s performance is low. |
| 0631605 | Modified static route caused system outage. |
| 0630923/0630919 | For FortiWeb-VM with a license purchased earlier than February 2019, upgrading to 6.3.0/6.3.1/6.3.2/6.3.3 will cause FortiWeb-VM to break down or its performance drops down dramatically. |
| 0629617 | When the element type is JSON Elements, the created signature exception fails to be applied. |
| 0628496 | FortiWeb crashes when libcmime parses the MIME header if the protocol is ActiveSync for file security. |
| 0624865 | Multiple HTTP constraint exceptions fail to be added using the same hostname while different IPs in GUI. |
| 0622698 | MSG_ID is missing in 503 replacement response message. |
| 0618549 | When the connection ends abnormally, some modules may leak memory. |
| 0620888/0612474 | If the redirect action policy is triggered by a certain part of the request, FortiWeb directly executes the action, without parsing the rest part of the request. |
| 0606221 | When setting port1 as hbdev port and executing ha disconnect, port10 and above ports are not shut down unexpectedly. |
| 0604298 | With fortiguard-anycast enabled, if FortiWeb-VM is disconnected from FDS for over 4 hours, it won’t generate elog to warn this situation. |
| 0603448 | The IPv6 DAD checks VIP IPv6 conflict, but no event log is generated. |
Znane problemy:
| Bug ID | Description |
|---|---|
| 0604053 | FortiWeb 100D devices reboot for unknown reasons in rare cases. |
| 0604051 | Cannot get the API key when the API key is set in request body in HTTP2 environment. |
| 0602759 | Selecting NO-NAT or Pool in SNAT policy and leaving the Egress Interface blank may cause display problems on GUI. |
| 0602712 | Not configuring external and mapped addresses in DNAT policy may cause the port forwarding configurations to be lost. |
| 0598144 | In Web Cache, when the gzip response is cached but the client does not support gzip, it may result in page display issues at the client side. |
| 0597351 | In machine learning, for certain domain types with multiple patterns, it costs very long time to finish the sample collection. |
| 0596000 | Users with privileges to a certain ADOM can access contents restricted to other ADOMs through CLI. |
| 0595053 | If the IP address is IPv6 and the HTTP version is 1.1 or 2, the device tracking module does not work well. |
| 0578585 | In active-active high volume HA mode, if the physical port IP address and the VIP address are in the same network segment, the physical port’s mac address instead of the VIP’s mac address will be learned by the switch. |
| 0556301 | FortiWeb responds with different TCP ports when running sudo nmap towards a physical interface |
Zapraszamy do lektury notatek wydanych przez producenta, gdzie znajdą Państwo dużo więcej informacji na temat aktualizacji! Release Notes – FortiWeb 6.3.4—
Pozdrawiamy,
Zespół B&B
Bezpieczeństwo w biznesie
