Trend officescan clients not updating Porno chat no sign

Posted by / 31-Oct-2020 11:28

Trend officescan clients not updating

After receiving this message the client connects back to the server for more information.

To make sure that clients won’t lost connection in case of changes in the network architecture this notification message already contains the most basic connection information like the server address or the proxy. We have already seen that encryption is not an issue, and most parameters are basically public version and configuration parameters.

I monitored the client-server communication for quite some time and I realized that after issuing a configuration change at the server, a special HTTP request is sent from the server to the TCP/61832 port of the client.

After installing a trial version (10.6 SP1) I could already tell that this software will worth the effort: And there are possibly many other fragile parts of the system.

I recently installed patch patch 11.1 (1639) on my Office Scan Server, all my 32 Bit clients updated automatically to the new version.

PS: Does anybody know future plans regarding the official TM forum (since there isn't one anymore)?

Analyzing the security of security software is one of my favorite research areas: it is always ironic to see software originally meant to protect your systems open a gaping door for the attackers.

Earlier this year I stumbled upon the Office Scan security suite by Trend Micro, a probably lesser known host protection solution (AV) still used at some interesting networks.

trend officescan clients not updating-58trend officescan clients not updating-25trend officescan clients not updating-38

I started to monitor the network connections of the clients and found some interesting interfaces, one of these looked like this: POST /officescan/cgi/isapi HTTP/1.1 User-Agent: 11111111111111111111111111111111 Accept: */* Host: 192.168.124.180 Content-Type: application/x-www-form-urlencoded Content-Length: 96 Proxy-Connection: Keep-Alive Cache-Control: no-cache Pragma: no-cache Connection: close Request ID=123&Function Type=0&UID=11111111-2222-3333-4444-555555555555&RELEASE=10.6&chk Database=1 The Request ID parameters were the same, but I quickly loaded the request to Burp Intruder and tried to brute-force other valid identifiers. 5231C05389DD886C99EA4646653498C2DB98EFD6EF61BD4907B2BD97E4ACDAED73AEE46B44AACBC450915317269 (...) which are (seemingly) encrypted, indicating that these params are something to protect.