P
Poor slob
Guest
I became aware of CVE-2020-17022 (Microsoft Windows Codecs Library Remote Code Execution Vulnerability). The FAQ says I'm affected if I have "HEVC video extensions from device manufacturer" installed. I do! It says I'll get the updated bugfix version via the Microsoft Store app. Yet the Microsoft Store app doesn't show it as an available update. I've had the Store app set for automatic updates for several days now. It's updated a number of my apps, but not the HEVC video extensions app.
According to Settings > Apps, my current HEVC video extensions app is version 1.0.32022.0, published by Microsoft. It was last updated on 8/19/20.
The CVE says that the "secure versions" are1.0.32762.0, 1.0.32763.0, and later.
Howcome Microsoft Store isn't updating my HEVC video extensions app?
I'm running Windows 10 Pro, version 1909 x64, on a PC. Windows Update delivered the October updates last week, so I'm up to date.
P.S. I've modeled this question on one posted in July 2020, with the same subject. That user had the same problem I'm having, with the same app but regarding earlier CVEs, and eventually reported that although Store didn't list the HEVC video extensions as an available update, leaving Store set to automatic update all apps eventually caused it to happen. I'm not having luck with that approach, as described above.
Continue reading...
According to Settings > Apps, my current HEVC video extensions app is version 1.0.32022.0, published by Microsoft. It was last updated on 8/19/20.
The CVE says that the "secure versions" are1.0.32762.0, 1.0.32763.0, and later.
Howcome Microsoft Store isn't updating my HEVC video extensions app?
I'm running Windows 10 Pro, version 1909 x64, on a PC. Windows Update delivered the October updates last week, so I'm up to date.
P.S. I've modeled this question on one posted in July 2020, with the same subject. That user had the same problem I'm having, with the same app but regarding earlier CVEs, and eventually reported that although Store didn't list the HEVC video extensions as an available update, leaving Store set to automatic update all apps eventually caused it to happen. I'm not having luck with that approach, as described above.
Continue reading...