<![CDATA[[Solved] Chrome 83.0.4103.61 detected as insecure]]>Chrome 83.0.4103.61 is detected as insecure and Vulndetect proposes 83.0.4103.97 but when trying to download latest Chrome version only .61 is available (french version).

Hope this helps.

]]>https://vulndetect.org/topic/855/solved-chrome-83-0-4103-61-detected-as-insecureRSS for NodeSun, 19 Jul 2026 21:32:21 GMTThu, 04 Jun 2020 19:43:27 GMT60<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Sun, 21 Jun 2020 16:47:13 GMT]]>OK, then I mark this issue as solved.

]]>https://vulndetect.org/post/3691https://vulndetect.org/post/3691Sun, 21 Jun 2020 16:47:13 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Sun, 21 Jun 2020 16:17:52 GMT]]>@Tom & @OLLI_S : I do not think this is useful to keep this one open as it is due to suppliers not delivering at the same time everywhere.

]]>https://vulndetect.org/post/3689https://vulndetect.org/post/3689Sun, 21 Jun 2020 16:17:52 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Sat, 06 Jun 2020 11:59:46 GMT]]>@Tom : Localization by internet tools is a very funny thing. Some years ago I was able to cross the Atlantic in a second :-) .
Are you sure that your french hosts are not found in USA or elsewhere?

]]>https://vulndetect.org/post/3586https://vulndetect.org/post/3586Sat, 06 Jun 2020 11:59:46 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Sat, 06 Jun 2020 11:32:06 GMT]]>@GregAlexandre It is good to know.

The thing is, that we have a bunch of test machines where we apply updates, and as I explained earlier, our packages download the installer from the vendors official sites / CDNs.

Coincidentally, we have some 15 (virtual) test hosts located in France, and I have never noticed such a delay for Chrome (or other software). We deploy updates to at least half of them within minutes after we prep the package and the remainder within a few days.

But I guess you are right, I'm just surprised we don't see it when we test - due to the way we do it, it would cause a 24 hour delay before we reattempt.

]]>https://vulndetect.org/post/3579https://vulndetect.org/post/3579Sat, 06 Jun 2020 11:32:06 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Sat, 06 Jun 2020 11:09:02 GMT]]>@Tom :

  • https://www.google.com/chrome/ with "Français - France" as language choice.
  • auto-update feature
    Both gave the same result: outdated version.
    For Edge I only tried thru parameters / about .
    I am not surprised but this behavior where updates arrive with some delays in Europe.
    My main point was to let you know, if needed, as this can be surprising when displayed in red. :-)
]]>https://vulndetect.org/post/3571https://vulndetect.org/post/3571Sat, 06 Jun 2020 11:09:02 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Sat, 06 Jun 2020 10:53:11 GMT]]>@OLLI_S : yes. Has to wait less than one hour after my last post to have it updated.

]]>https://vulndetect.org/post/3570https://vulndetect.org/post/3570Sat, 06 Jun 2020 10:53:11 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Sat, 06 Jun 2020 05:35:18 GMT]]>@GregAlexandre Where do you download it from?

Whenever we recommend new versions of Chrome, Edge and most other software, then we either already see users running the new version, or we see that the vendor update the versions on their download / release notes / announcements pages.

Only rarely do we see a delay in the exe file being published, mostly it is smaller projects, where they rely on free CDNs or download sites to distribute their software, in these cases we sometimes have to try more than one site, to find one with an updated installer.

]]>https://vulndetect.org/post/3567https://vulndetect.org/post/3567Sat, 06 Jun 2020 05:35:18 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 22:13:40 GMT]]>@GregAlexandre said in Chrome 83.0.4103.61 detected as insecure:

@Tom : Same problem with Edge chromium today: .44 available at this time and .45 known to be the latest version.

Edge was updated right now to Version 83.0.478.45

]]>https://vulndetect.org/post/3566https://vulndetect.org/post/3566Fri, 05 Jun 2020 22:13:40 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 20:05:36 GMT]]>@OLLI_S : Agree.
I used to find forbidden Chrome installations by taking them sending data to forbidden anonymizers.
So I do not use it but have to look at it.

]]>https://vulndetect.org/post/3565https://vulndetect.org/post/3565Fri, 05 Jun 2020 20:05:36 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 19:59:01 GMT]]>@Tom : Same problem with Edge chromium today: .44 available at this time and .45 known to be the latest version.

]]>https://vulndetect.org/post/3564https://vulndetect.org/post/3564Fri, 05 Jun 2020 19:59:01 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 16:23:14 GMT]]>@OLLI_S :rolling_on_the_floor_laughing:

]]>https://vulndetect.org/post/3563https://vulndetect.org/post/3563Fri, 05 Jun 2020 16:23:14 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 16:17:33 GMT]]>I don't use Chrome (I am using Microsoft Edge Chromioum).
The portable version of Google Chrome I have just for VulnDetect!

]]>https://vulndetect.org/post/3562https://vulndetect.org/post/3562Fri, 05 Jun 2020 16:17:33 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 16:10:39 GMT]]>@OLLI_S So why do you use it? There are so many alternatives.

]]>https://vulndetect.org/post/3560https://vulndetect.org/post/3560Fri, 05 Jun 2020 16:10:39 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 16:03:01 GMT]]>By the way: Google Chrome should be marked as Insecure by default, becuse it steals your data!
:devil:

]]>https://vulndetect.org/post/3559https://vulndetect.org/post/3559Fri, 05 Jun 2020 16:03:01 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 13:08:29 GMT]]>@GregAlexandre You may be right, but usually the new installer is available even before they publish the blog about the release.

I guess there can always be a few of their mirrors (or CDNs) that are out of sync.

]]>https://vulndetect.org/post/3557https://vulndetect.org/post/3557Fri, 05 Jun 2020 13:08:29 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 09:12:01 GMT]]>@Tom : Yes it is OK now.
I push you thru chat the account where I have seen this issue. If this can help.
I read the article you mention. Google commitment is to roll out the version for various OS "during next days/weeks". So there could be some latency.
Regards.

]]>https://vulndetect.org/post/3556https://vulndetect.org/post/3556Fri, 05 Jun 2020 09:12:01 GMT<![CDATA[Reply to [Solved] Chrome 83.0.4103.61 detected as insecure on Fri, 05 Jun 2020 05:27:15 GMT]]>Hi Greg,

That is odd, since Google usually are very fast in releasing their new versions.

Read this:
https://chromereleases.googleblog.com/2020/06/stable-channel-update-for-desktop.html

We have tested it and we have upgraded thousands of Google Chrome installations to .97 already, so the issue must be "local" to France, and most likely you will get the correct version now.

]]>https://vulndetect.org/post/3555https://vulndetect.org/post/3555Fri, 05 Jun 2020 05:27:15 GMT