• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 704
  • Last Modified:

TrendMicro OfficeScan registry edit

Do to this security vulnerability. "Microsoft Windows Unquoted Service Path Enumeration".
Can I script be ran to unload the OfficeScan which requires a password, make a registry edit, then restart OfficeScan?
0
GoHuskers
Asked:
GoHuskers
  • 3
  • 2
2 Solutions
 
btanExec ConsultantCommented:
not that I know Officescan has such ready script. But there are other script as shared in
a) MS forum - via SCCM DCM using VBscript
https://social.technet.microsoft.com/Forums/en-US/a34855ae-47e5-4567-bb1e-17bf6a97ab75/microsoft-windows-unquoted-service-path-enumeration

or b) Powershell script for detect and remediation
http://www.ryanandjeffshow.com/blog/2013/04/11/powershell-fixing-unquoted-service-paths-complete/
0
 
GoHuskersAuthor Commented:
thanks for the info on the scripts. I am using a version of it already to confirm the missing quotes.
you can't make the trend fix unless you unload trend first.
Trends solution is to uninstall/re-install which is way to resource intensive when all we have to do is to unload the trend and add "'s in two places etc.
so running a script to unload and running a script to make the registry changes makes more sense and is my goal.
0
 
btanExec ConsultantCommented:
In the past, the key Officescan client services below (from the admin guide) where other shared net stop (and some resort to taskkill /F /IM looping till) the services to disable the client eventually.
• OfficeScan NT Listener (TmListen.exe)
• OfficeScan NT RealTime Scan (NTRtScan.exe)
• OfficeScan NT Proxy Service (TmProxy.exe)
• OfficeScan NT Firewall (TmPfw.exe); if the firewall was enabled during installation
• Trend Micro Unauthorized Change Prevention Service (TMBMSRV.exe); only for computers running an x86 type processor

But the later version may already has client protection against such attempt and even after changes, the protection upon detection will revert back to original. in other words, changes to registry will not be possible too - not to say only disabling these client services.

I was separately thinking to rename such TM exe and keep looping till possible. With that window of opportunity, change registry but it may revert back the content so there is no guarantee though.

Another is boot to safe mode and try ...but if the protection is robust enough, this should not make any differences..there may not be necessary a workable yet resource saving mean as it seems to suggest to bypass AV (like a malicious code is attempting)

Maybe better for the TM support to clarify the right approach since this is a gap (there is a CVE for this vul)  in their solution
0
 
GoHuskersAuthor Commented:
TM support wants uninstall/re-install and that's all they offer.

And you are right it will not allow me to tskill any of them. The client protection must be in place which is why we have it I guess.

So unfortunately I do not think I can automate this at all.

thanks for the input
0
 
btanExec ConsultantCommented:
thanks for sharing
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now