Windows 22H2 Being Reported as Vulnerable

ALangford · 2023-07-11T20:39:15+00:00

There was an error rendering this rich post.

I have a little over 250 devices that are reporting 22H2 as vulnerable in gravityzone starting around 7.7.23

CVE-2022-24502, CVE-2022-24503, CVE-2022-24505, CVE-2023-21554, CVE-2023-28252

I have pushed windows kb502166 to a test group of devices today but they are still showing vulnerable. PC's show windows build 10.0.19045.3208.

I have around 50 more that show the same updates applied before today that never came up as vulnerable in gravity zone as well. Any help would be appreciated!

Find more posts tagged with

gravityzone

Security

Accepted answers

All comments

Scott

HI @ALangford

This is something @Alex_Dr or @Andra_B will have to look into, as they both provide support for the business products.

You can also contact Bitdefender business support from here:

https://www.bitdefender.com/business/support/en/71263-85158-contact.html

Kind regards,

Scott

ALangford

Thanks Scott! I have a do have a ticket in with them as well.

treeves

I'm also having this issue. Doesn't seem to be any updates available for the PCs with this vulnerability.

Alex_Dr

Hello @alang5629 @ALangford,

Can you please let me know if the Bitdefender product is updated to the latest version? Also, given the number of endpoints at risk of infection, I strongly suggest getting in contact with the Enterprise Support team to troubleshoot the situation faster. Also,it would help if you would provide me the case number(after contacting the team) so I can follow-up with them to resolve this asap.

Best regards,

Alex D.

rforrister

I am in the same boat. Was there any advice given on how to handle the situation?

ALangford

Unfortunately, I did not get any direct updates but they did eventually drop off. I did have another issue that I reached out to BD support on who let me know that they had been having issues with risk scans opening then immediately closing. They had an update for it in fast ring updates, so I cloned our main policy and updated a test group to fast ring updates in the new policy and they started clearing out.