Long ago, someplace here, likely in knowledge base, I got a list of proxy ports that Avast uses. Does anyone remember the link? I can’t find it anymore and want to check if my list is still valid.
Bump 
sorry.
Since nobody answered, if the link no longer exists, is the list in TCPview sufficient to know the entire list?
Not sure why you need to know or what you are going do with them, but TCP View should be enough, just look for the avastsvc.exe and TCP listening ports.
Any old topic may well be out of date with new functionality.
I’m not doing anything really. Just reviewing my firewall rules to confirm that programs that have no business going out don’t sneak out through the proxy ports. That’s all.
If it is programs that you are concerned with, I would be looking at ensuring your firewall (?) is capable of determining what is using (being redirected by) the avast web shield proxy and not just the proxy itself, then you probably don’t need to go down to port level.
Even then it would be possible for a program to slip out if the firewall can’t determine what is using the web shield proxy as you would be allowing the 12080 localhost port that is used by the web shield.
You will notice that these ate local ports and are Listening, so aren’t going anywhere.
So just allowing the avastsvc.exe and avast.setup should be all that it necessary, though avastUI.exe probably needs it also.
I don’t want anything to slip out and I don’t think anything does (firewall alerts or blocks when something tries to use proxy).
I only permit few applications to use 12080 (Opera, SeaMonkey, avast emergency updates, java updates, imageshack uploader, couple more). Nobody else allowed to send packets to Avastsvc listening on that port. Avastsvc then connects and all is well.
When I use IE, IE is allowed out through the 12080 proxy as well as to all local host ports since it needs to loopback.
There is some game proxy port avast uses. We don’t have games here, so nothing should go out through it.
Only mail client is allowed out through the other avast ports 12025, 12110, and 12995, 12465 for SSL. Nobody else can use’m.
Yes, AvastUI.exe and avast.setup do like to be allowed out, directly to avast servers port 80, but emergency updates are happy to request it through proxy.