# Core 169 testing and change status vulnerability **URL:** \ **Category:** Security\ **Created:** [29 June 2022 12:34 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159 "2022-06-29T12:34:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![steph78630](https://community.ipfire.org/user_avatar/community.ipfire.org/steph78630/32/8251_2.png) [@steph78630](https://community.ipfire.org/u/steph78630)\ **Post date:** [29 June 2022 12:34 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159/1 "2022-06-29T12:34:52Z")
Hi, since the Core 169 testing update, my **Spectre Variant 4** vulnerability ( **CVE-2018-3639** ) moved from “ **Not Affected** ” to “ **Vulnerable** ”… Anyone see the same change ? ---
**Author:** ![ag](https://community.ipfire.org/user_avatar/community.ipfire.org/ag/32/12124_2.png) [@ag](https://community.ipfire.org/u/ag)\ **Post date:** [29 June 2022 14:01 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159/2 "2022-06-29T14:01:00Z")
I have noticed the same recently. Although the **[spectre-meltdown-checker](https://github.com/speed47/spectre-meltdown-checker)** also now shows the same where before it didn’t. It might be time for us to upgrade 😂 ![1](https://community.ipfire.org/uploads/default/original/2X/c/c07b8622b03285748c507901a8992677f7aa440d.png) spectre-meltdown-checker: ![2](https://community.ipfire.org/uploads/default/original/2X/f/fa0ba430b4d0b18480e56c1323249495d557be03.png) ---
**Author:** ![wiztech](https://community.ipfire.org/user_avatar/community.ipfire.org/wiztech/32/16667_2.png) [@wiztech](https://community.ipfire.org/u/wiztech)\ **Post date:** [29 June 2022 14:06 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159/3 "2022-06-29T14:06:54Z")
Hi, My Core169 test box shows Mitigated (same as before). ![spectre](https://community.ipfire.org/uploads/default/original/2X/a/a5c1b8bb7f911b3ae98f9dae7deac8d0940b6dbf.png) ---
**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\ **Post date:** [29 June 2022 14:16 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159/4 "2022-06-29T14:16:55Z")
spectre-meltdown-checker was upgraded to version 0.45 in Core Update 168. ---
**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\ **Post date:** [29 June 2022 20:38 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159/5 "2022-06-29T20:38:04Z")
Hi, if I recall correctly, the `spectre-meltdown-checker` update indeed caused a more accurate reporting of CPU vulnerabilities on my machines. Specifically, one it was actually _not_ vulnerable to has always been reported the other way round before; version 0.45 fixed this. As for the general sentiment, the output of `spectre-meltdown-checker` appears to be a bit more accurate than the CGI status (which is solely derived from the kernel’s own findings), so it might be useful to cross-check both if in doubt. There may well be a correction regarding Spectre v4 in the upstream kernel. I did not checked for that, but that particular one is a tricky beast, and it is possible that more CPU models are affected by it than previously assessed. Brave new world, I guess. 😑 Thanks, and best regards, Peter Müller ---
**Author:** ![xperimental](https://community.ipfire.org/user_avatar/community.ipfire.org/xperimental/32/16702_2.png) [@xperimental](https://community.ipfire.org/u/xperimental)\ **Post date:** [29 June 2022 20:41 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159/6 "2022-06-29T20:41:23Z")
Yep. I have that status " **Vulnerable**" already in core 168! 👍 So it’s not new. ---
**Author:** ![ag](https://community.ipfire.org/user_avatar/community.ipfire.org/ag/32/12124_2.png) [@ag](https://community.ipfire.org/u/ag)\ **Post date:** [12 July 2022 22:56 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159/7 "2022-07-12T22:56:18Z")
After upgrading to CU169 stable mitigation is enabled again. I can’t complain 👍 ![Screenshot from 2022-07-12 23-55-35](https://community.ipfire.org/uploads/default/original/2X/7/70eb63b237c373aaa86283a615ce3d2d22aa79f4.png) ---
**Author:** ![steph78630](https://community.ipfire.org/user_avatar/community.ipfire.org/steph78630/32/8251_2.png) [@steph78630](https://community.ipfire.org/u/steph78630)\ **Post date:** [13 July 2022 06:59 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159/8 "2022-07-13T06:59:02Z")
> [@steph78630](#): > > CVE-2018-3639 Same here since CU 169 stable (vulnerable \> not affected) ---
**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\ **Post date:** [13 July 2022 18:57 UTC](https://community.ipfire.org/t/core-169-testing-and-change-status-vulnerability/8159/9 "2022-07-13T18:57:55Z")
Hi all, just for the records: You may well see Specte v2 flapping back from “mitigated” to “vulnerable” on your machines. > **[AMD, Intel chips vulnerable to 'Retbleed' Spectre variant](https://www.theregister.com/2022/07/12/amd_intel_retbleed/)** > > Speculative execution side-channels continue to haunt silicon world Sorry to disappoint, and best regards, Peter Müller