Galileusz Posted October 27, 2019 Report Share Posted October 27, 2019 Maxthon Browser for Windows - Unquoted Search Path and Potential Abuses (CVE-2019-16647) https://safebreach.com/Post/Maxthon-Browser-for-Windows-Unquoted-Search-Path-and-Potential-Abuses-CVE-2019-16647 Link to comment Share on other sites More sharing options...
pantantrollo Posted October 27, 2019 Report Share Posted October 27, 2019 Good link :-) , thx Fortunately the portable version doesn't have mxservice.exe. Even so, for my part, I have renamed some .dll and .exe, which I never liked (some related to synchronization that I don't use), and it still works without apparent problems (and they are a few renamed files). Link to comment Share on other sites More sharing options...
BugSir006 Posted October 28, 2019 Report Share Posted October 28, 2019 Hi there, this issue has been fixed in v5.3.8.2000. Link to comment Share on other sites More sharing options...
Galileusz Posted October 28, 2019 Author Report Share Posted October 28, 2019 1 hour ago, BugSir006 said: Hi there, this issue has been fixed in v5.3.8.2000. So why is this not included in the changelog? And, why do we find out about it from someone else, but not from you? Link to comment Share on other sites More sharing options...
BugSir006 Posted October 29, 2019 Report Share Posted October 29, 2019 On 10/28/2019 at 7:14 PM, Galileusz said: So why is this not included in the changelog? And, why do we find out about it from someone else, but not from you? Usually, we conclude the changelog from our internal bug list. When we received the users' feedback about this issue, this issue had been fixed by the dev team, so it didn't be added to the bug list. Link to comment Share on other sites More sharing options...
pantantrollo Posted October 29, 2019 Report Share Posted October 29, 2019 14 hours ago, BugSir006 said: Usually, we conclude the changelog from our internal bug list. So there are "external" errors ? 14 hours ago, BugSir006 said: When we received the users' feedback about this issue, this issue had been fixed by the dev team, so it didn't been added to the bug list. It means, that the "other" bugs reported from these same forums, and fixed by the development team, are included in the "change.log", "by the infuse science"... Link to comment Share on other sites More sharing options...
BugSir006 Posted October 30, 2019 Report Share Posted October 30, 2019 This issue had been fixed before we received users' feedback (forum and email), it fixed by the dev team long ago, so it didn't be added to the bug list. Usually, we submit a bug request to the dev team, it is convenient for checking the pending bugs. If it had been reported before the dev team confirmed and fixed it, it would have been added to the bug list and displayed in the changelog. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.