Read Time:9 Second
It was discovered that Minizip in zlib incorrectly handled certain zip
header fields. An attacker could possibly use this issue to cause a denial
of service, or execute arbitrary code.
Daily Archives: November 13, 2024
microcode_ctl-2.1-67.fc41
Read Time:5 Minute, 54 Second
FEDORA-2024-28ea86c8aa
Packages in this update:
microcode_ctl-2.1-67.fc41
Update description:
Update to upstream 2.1-47. 20241112
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode from revision 0x2b0005c0
up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode from revision 0x2b0005c0
up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode from revision
0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode from revision
0x2b0005c0 up to 0x2b000603;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode from revision
0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode (in
intel-ucode/06-97-02) from revision 0x36 up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode (in intel-ucode/06-97-02)
from revision 0x36 up to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode (in intel-ucode/06-97-02)
from revision 0x36 up to 0x37;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode (in
intel-ucode/06-97-05) from revision 0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode from revision 0x36
up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode (in intel-ucode/06-97-05)
from revision 0x36 up to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode (in intel-ucode/06-97-05)
from revision 0x36 up to 0x37;
Update of 06-9a-03/0x80 (ADL-P 6+8/U 9W L0/R0) microcode from revision
0x434 up to 0x435;
Update of 06-9a-04/0x80 (ADL-P 2+8 R0) microcode (in
intel-ucode/06-9a-03) from revision 0x434 up to 0x435;
Update of 06-9a-03/0x80 (ADL-P 6+8/U 9W L0/R0) microcode (in
intel-ucode/06-9a-04) from revision 0x434 up to 0x435;
Update of 06-9a-04/0x80 (ADL-P 2+8 R0) microcode from revision 0x434
up to 0x435;
Update of 06-aa-04/0xe6 (MTL-H/U C0) microcode from revision 0x1f
up to 0x20;
Update of 06-ba-02/0xe0 (RPL-H 6+8/P 6+8 J0) microcode from revision
0x4122 up to 0x4123;
Update of 06-ba-03/0xe0 (RPL-U 2+8 Q0) microcode (in
intel-ucode/06-ba-02) from revision 0x4122 up to 0x4123;
Update of 06-ba-08/0xe0 microcode (in intel-ucode/06-ba-02) from
revision 0x4122 up to 0x4123;
Update of 06-ba-02/0xe0 (RPL-H 6+8/P 6+8 J0) microcode (in
intel-ucode/06-ba-03) from revision 0x4122 up to 0x4123;
Update of 06-ba-03/0xe0 (RPL-U 2+8 Q0) microcode from revision 0x4122
up to 0x4123;
Update of 06-ba-08/0xe0 microcode (in intel-ucode/06-ba-03) from
revision 0x4122 up to 0x4123;
Update of 06-ba-02/0xe0 (RPL-H 6+8/P 6+8 J0) microcode (in
intel-ucode/06-ba-08) from revision 0x4122 up to 0x4123;
Update of 06-ba-03/0xe0 (RPL-U 2+8 Q0) microcode (in
intel-ucode/06-ba-08) from revision 0x4122 up to 0x4123;
Update of 06-ba-08/0xe0 microcode from revision 0x4122 up to 0x4123;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode (in
intel-ucode/06-bf-02) from revision 0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode (in
intel-ucode/06-bf-02) from revision 0x36 up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode from revision 0x36 up
to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode (in intel-ucode/06-bf-02)
from revision 0x36 up to 0x37;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode (in
intel-ucode/06-bf-05) from revision 0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode (in
intel-ucode/06-bf-05) from revision 0x36 up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode (in intel-ucode/06-bf-05)
from revision 0x36 up to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode from revision 0x36 up
to 0x37;
Update of 06-cf-01/0x87 (EMR-SP A0) microcode from revision 0x21000230
up to 0x21000283;
Update of 06-cf-02/0x87 (EMR-SP A1) microcode (in
intel-ucode/06-cf-01) from revision 0x21000230 up to 0x21000283;
Update of 06-cf-01/0x87 (EMR-SP A0) microcode (in
intel-ucode/06-cf-02) from revision 0x21000230 up to 0x21000283;
Update of 06-cf-02/0x87 (EMR-SP A1) microcode from revision 0x21000230
up to 0x21000283.
Addresses CVE-2024-21820, CVE-2024-21853, CVE-2024-23918, CVE-2024-23984
microcode_ctl-2.1-61.5.fc40
Read Time:6 Minute, 1 Second
FEDORA-2024-d20a106350
Packages in this update:
microcode_ctl-2.1-61.5.fc40
Update description:
Update to upstream 2.1-47. 20241112
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode from revision 0x2b0005c0
up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode from revision 0x2b0005c0
up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode from revision
0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode from revision
0x2b0005c0 up to 0x2b000603;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode from revision
0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode (in
intel-ucode/06-97-02) from revision 0x36 up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode (in intel-ucode/06-97-02)
from revision 0x36 up to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode (in intel-ucode/06-97-02)
from revision 0x36 up to 0x37;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode (in
intel-ucode/06-97-05) from revision 0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode from revision 0x36
up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode (in intel-ucode/06-97-05)
from revision 0x36 up to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode (in intel-ucode/06-97-05)
from revision 0x36 up to 0x37;
Update of 06-9a-03/0x80 (ADL-P 6+8/U 9W L0/R0) microcode from revision
0x434 up to 0x435;
Update of 06-9a-04/0x80 (ADL-P 2+8 R0) microcode (in
intel-ucode/06-9a-03) from revision 0x434 up to 0x435;
Update of 06-9a-03/0x80 (ADL-P 6+8/U 9W L0/R0) microcode (in
intel-ucode/06-9a-04) from revision 0x434 up to 0x435;
Update of 06-9a-04/0x80 (ADL-P 2+8 R0) microcode from revision 0x434
up to 0x435;
Update of 06-aa-04/0xe6 (MTL-H/U C0) microcode from revision 0x1f
up to 0x20;
Update of 06-ba-02/0xe0 (RPL-H 6+8/P 6+8 J0) microcode from revision
0x4122 up to 0x4123;
Update of 06-ba-03/0xe0 (RPL-U 2+8 Q0) microcode (in
intel-ucode/06-ba-02) from revision 0x4122 up to 0x4123;
Update of 06-ba-08/0xe0 microcode (in intel-ucode/06-ba-02) from
revision 0x4122 up to 0x4123;
Update of 06-ba-02/0xe0 (RPL-H 6+8/P 6+8 J0) microcode (in
intel-ucode/06-ba-03) from revision 0x4122 up to 0x4123;
Update of 06-ba-03/0xe0 (RPL-U 2+8 Q0) microcode from revision 0x4122
up to 0x4123;
Update of 06-ba-08/0xe0 microcode (in intel-ucode/06-ba-03) from
revision 0x4122 up to 0x4123;
Update of 06-ba-02/0xe0 (RPL-H 6+8/P 6+8 J0) microcode (in
intel-ucode/06-ba-08) from revision 0x4122 up to 0x4123;
Update of 06-ba-03/0xe0 (RPL-U 2+8 Q0) microcode (in
intel-ucode/06-ba-08) from revision 0x4122 up to 0x4123;
Update of 06-ba-08/0xe0 microcode from revision 0x4122 up to 0x4123;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode (in
intel-ucode/06-bf-02) from revision 0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode (in
intel-ucode/06-bf-02) from revision 0x36 up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode from revision 0x36 up
to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode (in intel-ucode/06-bf-02)
from revision 0x36 up to 0x37;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode (in
intel-ucode/06-bf-05) from revision 0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode (in
intel-ucode/06-bf-05) from revision 0x36 up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode (in intel-ucode/06-bf-05)
from revision 0x36 up to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode from revision 0x36 up
to 0x37;
Update of 06-cf-01/0x87 (EMR-SP A0) microcode from revision 0x21000230
up to 0x21000283;
Update of 06-cf-02/0x87 (EMR-SP A1) microcode (in
intel-ucode/06-cf-01) from revision 0x21000230 up to 0x21000283;
Update of 06-cf-01/0x87 (EMR-SP A0) microcode (in
intel-ucode/06-cf-02) from revision 0x21000230 up to 0x21000283;
Update of 06-cf-02/0x87 (EMR-SP A1) microcode from revision 0x21000230
up to 0x21000283.
Addresses CVE-2024-21820, CVE-2024-21853, CVE-2024-23918, CVE-2024-23984
Update to upstream 2.1-46. 20241029
Update of 06-b7-01/0x32 (RPL-S B0) microcode from revision 0x129 up
to 0x12b.
microcode_ctl-2.1-58.5.fc39
Read Time:6 Minute, 1 Second
FEDORA-2024-7dfc167df4
Packages in this update:
microcode_ctl-2.1-58.5.fc39
Update description:
Update to upstream 2.1-47. 20241112
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode from revision 0x2b0005c0
up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode (in
intel-ucode/06-8f-05) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode from revision 0x2b0005c0
up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode (in
intel-ucode/06-8f-06) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode from revision
0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode (in
intel-ucode/06-8f-07) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-04/0x87 (SPR-SP E0/S1) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-05/0x87 (SPR-SP E2) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-06/0x87 (SPR-SP E3) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-07/0x87 (SPR-SP E4/S2) microcode (in
intel-ucode/06-8f-08) from revision 0x2b0005c0 up to 0x2b000603;
Update of 06-8f-08/0x87 (SPR-SP E5/S3) microcode from revision
0x2b0005c0 up to 0x2b000603;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode from revision
0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode (in
intel-ucode/06-97-02) from revision 0x36 up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode (in intel-ucode/06-97-02)
from revision 0x36 up to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode (in intel-ucode/06-97-02)
from revision 0x36 up to 0x37;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode (in
intel-ucode/06-97-05) from revision 0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode from revision 0x36
up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode (in intel-ucode/06-97-05)
from revision 0x36 up to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode (in intel-ucode/06-97-05)
from revision 0x36 up to 0x37;
Update of 06-9a-03/0x80 (ADL-P 6+8/U 9W L0/R0) microcode from revision
0x434 up to 0x435;
Update of 06-9a-04/0x80 (ADL-P 2+8 R0) microcode (in
intel-ucode/06-9a-03) from revision 0x434 up to 0x435;
Update of 06-9a-03/0x80 (ADL-P 6+8/U 9W L0/R0) microcode (in
intel-ucode/06-9a-04) from revision 0x434 up to 0x435;
Update of 06-9a-04/0x80 (ADL-P 2+8 R0) microcode from revision 0x434
up to 0x435;
Update of 06-aa-04/0xe6 (MTL-H/U C0) microcode from revision 0x1f
up to 0x20;
Update of 06-ba-02/0xe0 (RPL-H 6+8/P 6+8 J0) microcode from revision
0x4122 up to 0x4123;
Update of 06-ba-03/0xe0 (RPL-U 2+8 Q0) microcode (in
intel-ucode/06-ba-02) from revision 0x4122 up to 0x4123;
Update of 06-ba-08/0xe0 microcode (in intel-ucode/06-ba-02) from
revision 0x4122 up to 0x4123;
Update of 06-ba-02/0xe0 (RPL-H 6+8/P 6+8 J0) microcode (in
intel-ucode/06-ba-03) from revision 0x4122 up to 0x4123;
Update of 06-ba-03/0xe0 (RPL-U 2+8 Q0) microcode from revision 0x4122
up to 0x4123;
Update of 06-ba-08/0xe0 microcode (in intel-ucode/06-ba-03) from
revision 0x4122 up to 0x4123;
Update of 06-ba-02/0xe0 (RPL-H 6+8/P 6+8 J0) microcode (in
intel-ucode/06-ba-08) from revision 0x4122 up to 0x4123;
Update of 06-ba-03/0xe0 (RPL-U 2+8 Q0) microcode (in
intel-ucode/06-ba-08) from revision 0x4122 up to 0x4123;
Update of 06-ba-08/0xe0 microcode from revision 0x4122 up to 0x4123;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode (in
intel-ucode/06-bf-02) from revision 0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode (in
intel-ucode/06-bf-02) from revision 0x36 up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode from revision 0x36 up
to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode (in intel-ucode/06-bf-02)
from revision 0x36 up to 0x37;
Update of 06-97-02/0x07 (ADL-HX/S 8+8 C0) microcode (in
intel-ucode/06-bf-05) from revision 0x36 up to 0x37;
Update of 06-97-05/0x07 (ADL-S 6+0 K0) microcode (in
intel-ucode/06-bf-05) from revision 0x36 up to 0x37;
Update of 06-bf-02/0x07 (ADL C0) microcode (in intel-ucode/06-bf-05)
from revision 0x36 up to 0x37;
Update of 06-bf-05/0x07 (ADL C0) microcode from revision 0x36 up
to 0x37;
Update of 06-cf-01/0x87 (EMR-SP A0) microcode from revision 0x21000230
up to 0x21000283;
Update of 06-cf-02/0x87 (EMR-SP A1) microcode (in
intel-ucode/06-cf-01) from revision 0x21000230 up to 0x21000283;
Update of 06-cf-01/0x87 (EMR-SP A0) microcode (in
intel-ucode/06-cf-02) from revision 0x21000230 up to 0x21000283;
Update of 06-cf-02/0x87 (EMR-SP A1) microcode from revision 0x21000230
up to 0x21000283.
Addresses CVE-2024-21820, CVE-2024-21853, CVE-2024-23918, CVE-2024-23984
Update to upstream 2.1-46. 20241029
Update of 06-b7-01/0x32 (RPL-S B0) microcode from revision 0x129 up
to 0x12b.
Mapping License Plate Scanners in the US
Read Time:13 Second
DeFlock is a crowd-sourced project to map license plate scanners.
It only records the fixed scanners, of course. The mobile scanners on cars are not mapped.
The post Mapping License Plate Scanners in the US appeared first on Schneier on Security.
USN-7089-4: Linux kernel vulnerabilities
Read Time:4 Minute, 22 Second
Chenyuan Yang discovered that the USB Gadget subsystem in the Linux
kernel did not properly check for the device to be enabled before
writing. A local attacker could possibly use this to cause a denial of
service. (CVE-2024-25741)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
– ARM32 architecture;
– MIPS architecture;
– PA-RISC architecture;
– PowerPC architecture;
– RISC-V architecture;
– S390 architecture;
– x86 architecture;
– Cryptographic API;
– Serial ATA and Parallel ATA drivers;
– Null block device driver;
– Bluetooth drivers;
– Cdrom driver;
– Clock framework and drivers;
– Hardware crypto device drivers;
– CXL (Compute Express Link) drivers;
– Cirrus firmware drivers;
– GPIO subsystem;
– GPU drivers;
– I2C subsystem;
– IIO subsystem;
– InfiniBand drivers;
– ISDN/mISDN subsystem;
– LED subsystem;
– Multiple devices driver;
– Media drivers;
– Fastrpc Driver;
– Network drivers;
– Microsoft Azure Network Adapter (MANA) driver;
– Near Field Communication (NFC) drivers;
– NVME drivers;
– NVMEM (Non Volatile Memory) drivers;
– PCI subsystem;
– Pin controllers subsystem;
– x86 platform drivers;
– S/390 drivers;
– SCSI drivers;
– Thermal drivers;
– TTY drivers;
– UFS subsystem;
– USB DSL drivers;
– USB core drivers;
– DesignWare USB3 driver;
– USB Gadget drivers;
– USB Serial drivers;
– VFIO drivers;
– VHOST drivers;
– File systems infrastructure;
– BTRFS file system;
– GFS2 file system;
– JFFS2 file system;
– JFS file system;
– Network file systems library;
– Network file system client;
– NILFS2 file system;
– NTFS3 file system;
– SMB network file system;
– Memory management;
– Netfilter;
– Tracing infrastructure;
– io_uring subsystem;
– BPF subsystem;
– Core kernel;
– Bluetooth subsystem;
– CAN network layer;
– Ceph Core library;
– Networking core;
– IPv4 networking;
– IPv6 networking;
– IUCV driver;
– MAC80211 subsystem;
– Network traffic control;
– Sun RPC protocol;
– Wireless networking;
– AMD SoC Alsa drivers;
– SoC Audio for Freescale CPUs drivers;
– MediaTek ASoC drivers;
– SoC audio core drivers;
– SOF drivers;
– Sound sequencer drivers;
(CVE-2024-41064, CVE-2024-41087, CVE-2023-52888, CVE-2024-42098,
CVE-2024-42111, CVE-2024-42076, CVE-2024-42088, CVE-2024-42135,
CVE-2024-42145, CVE-2024-42142, CVE-2024-41036, CVE-2024-41071,
CVE-2024-41012, CVE-2024-42091, CVE-2024-42253, CVE-2024-42119,
CVE-2024-42097, CVE-2024-42243, CVE-2024-39487, CVE-2024-42235,
CVE-2024-42120, CVE-2024-42149, CVE-2024-41015, CVE-2024-41074,
CVE-2024-42067, CVE-2024-42090, CVE-2024-42128, CVE-2024-41038,
CVE-2024-42113, CVE-2024-42102, CVE-2024-42231, CVE-2024-42080,
CVE-2024-42241, CVE-2024-42106, CVE-2024-42130, CVE-2024-42073,
CVE-2024-42153, CVE-2024-42156, CVE-2024-42118, CVE-2024-41007,
CVE-2024-41049, CVE-2024-39486, CVE-2024-42240, CVE-2024-41018,
CVE-2024-42251, CVE-2024-42280, CVE-2024-42096, CVE-2024-42121,
CVE-2024-42246, CVE-2024-42092, CVE-2024-41090, CVE-2024-42157,
CVE-2024-43858, CVE-2024-42150, CVE-2024-42110, CVE-2024-41010,
CVE-2024-41081, CVE-2024-41061, CVE-2024-41078, CVE-2024-41094,
CVE-2024-41039, CVE-2024-42114, CVE-2024-42109, CVE-2024-41030,
CVE-2024-42066, CVE-2024-41035, CVE-2024-42146, CVE-2024-42131,
CVE-2024-41059, CVE-2024-41067, CVE-2024-42138, CVE-2024-41050,
CVE-2024-41034, CVE-2024-41077, CVE-2024-41076, CVE-2024-41088,
CVE-2024-41096, CVE-2024-41073, CVE-2024-41037, CVE-2024-42232,
CVE-2024-41063, CVE-2024-42117, CVE-2024-42155, CVE-2024-41080,
CVE-2024-42132, CVE-2024-42084, CVE-2024-42136, CVE-2024-42223,
CVE-2024-41068, CVE-2024-42225, CVE-2024-42065, CVE-2024-41051,
CVE-2024-43855, CVE-2024-42238, CVE-2024-42250, CVE-2024-42112,
CVE-2024-41070, CVE-2023-52887, CVE-2024-42094, CVE-2024-42095,
CVE-2024-41086, CVE-2024-41020, CVE-2024-41082, CVE-2024-42115,
CVE-2024-42152, CVE-2024-42239, CVE-2024-42093, CVE-2024-42126,
CVE-2024-41022, CVE-2024-41017, CVE-2024-41092, CVE-2024-41044,
CVE-2024-42140, CVE-2024-41029, CVE-2024-41054, CVE-2024-42158,
CVE-2024-41066, CVE-2024-42244, CVE-2024-42070, CVE-2024-41025,
CVE-2024-42229, CVE-2024-42085, CVE-2024-41084, CVE-2024-41060,
CVE-2024-41062, CVE-2024-42105, CVE-2024-42124, CVE-2024-41045,
CVE-2024-42227, CVE-2024-41047, CVE-2024-41042, CVE-2024-42100,
CVE-2024-42247, CVE-2024-41041, CVE-2024-42087, CVE-2024-42252,
CVE-2024-41058, CVE-2024-42063, CVE-2024-42271, CVE-2024-41027,
CVE-2024-42079, CVE-2024-42104, CVE-2024-41098, CVE-2024-41033,
CVE-2024-41072, CVE-2024-41031, CVE-2024-42089, CVE-2024-41032,
CVE-2024-42127, CVE-2024-41093, CVE-2024-42082, CVE-2024-41023,
CVE-2024-41075, CVE-2024-42151, CVE-2024-42141, CVE-2024-42108,
CVE-2024-42068, CVE-2024-41085, CVE-2024-42103, CVE-2024-41057,
CVE-2024-42064, CVE-2024-42161, CVE-2024-41052, CVE-2024-41053,
CVE-2024-42069, CVE-2024-41021, CVE-2024-42147, CVE-2024-41065,
CVE-2024-41091, CVE-2024-41079, CVE-2024-42086, CVE-2024-42234,
CVE-2024-41055, CVE-2024-41083, CVE-2024-42101, CVE-2024-42230,
CVE-2024-41095, CVE-2024-41019, CVE-2024-42245, CVE-2024-42129,
CVE-2024-42144, CVE-2024-42236, CVE-2024-41028, CVE-2024-42077,
CVE-2024-42248, CVE-2024-41046, CVE-2024-42133, CVE-2024-42074,
CVE-2024-41089, CVE-2024-42237, CVE-2024-41056, CVE-2024-41048,
CVE-2024-42137, CVE-2024-41069, CVE-2024-41097)
Amazon MOVEit Leaker Claims to Be Ethical Hacker
Read Time:6 Second
An individual who posted data allegedly stolen via MOVEit from Amazon and other big-name firms claims not to be malicious
Microsoft Fixes Four More Zero-Days in November Patch Tuesday
Read Time:5 Second
Microsoft has addressed four zero-day vulnerabilities this month, two of which have been exploited
Fake Job Ads and Fake Identities: How North Korea Gets Its Hands on Our Data
Read Time:6 Minute, 20 Second
Data theft has become an undeniable geopolitical weapon, and no player has mastered this art quite like North Korea.
Rather than relying solely on traditional hacking methods, the regime has adopted a far more insidious approach — exploiting the vulnerabilities of the job market. This might be why fake job ad scams saw a 28% spike in 2023.
As these methods become more advanced, both companies and individuals need to stay vigilant to protect themselves from this rising threat.
Keep reading to learn how this threat works and how to defend your company against it.
The Growing Threat of North Korean Cyber Actors
With limited access to global markets due to international sanctions, the North Korean regime has developed sophisticated hacking capabilities that focus on stealing sensitive information, financial assets, and intellectual property.
These actors, often state-backed organizations like the Lazarus Group, have been involved in major attacks, including the Sony Pictures hack in 2014 and the WannaCry ransomware incident.
Their approach combines sophisticated hacking techniques with social engineering, allowing them to slip through traditional cybersecurity defenses. They often pose as legitimate job seekers or employers, using fake job ads and resumes to gain access to corporate networks. Once inside, they steal sensitive information such as corporate IP, financial data, and personal details.
But their tactics don’t stop at fake identities. North Korean hackers are also experts at faking entire websites to further their espionage goals.
They might take a page about invoice factoring for SMBs, copy everything, but redirect potential leads to a phishing page. These sites are designed to capture login credentials, personal information, and other sensitive data, making it easier for hackers to penetrate the target company’s systems undetected.
These hackers also use spear phishing, a highly targeted form of phishing. They research their victims and send emails that seem to come from trusted sources. These emails often contain malicious attachments or links that, once clicked, give the hackers access to the victim’s computer or network.
How They Use Fake Identities in Cyber Espionage
North Korean cyber actors are experts in using fake identities to conduct cyber espionage. They create synthetic identities, complete with fabricated resumes, professional profiles, and even fake references, to infiltrate companies and organizations.
These fake personas often appear highly qualified, sometimes posing as software developers, engineers, or other skilled professionals. The goal is to gain access to sensitive data, corporate networks, and intellectual property without raising suspicion.
These actors commonly use platforms like LinkedIn or job boards to build credible profiles that attract recruiters or hiring managers. Once hired or engaged in a business relationship, they can exploit access to sensitive information, such as internal emails, financial data, or proprietary technology.
This method allows them to bypass traditional security measures, as companies may not immediately flag a trusted employee or contractor as a potential threat.
How They Use Fake Job Ads to Target Developers
The ads typically offer high-paying remote or freelance positions, using credible job titles and descriptions to mimic real opportunities. The goal is to lure unsuspecting developers into engaging with these ads and unknowingly exposing their devices to malicious software.
Developers with expertise in frameworks like Salesforce, AWS, or Docker are particularly targeted because of their access to critical systems and data. This makes them an attractive entry point for hackers looking to infiltrate organizations.
Once hackers gain access through these developers, they can further penetrate corporate networks, potentially compromising the entire organization.
These scams are especially dangerous because they exploit human trust and bypass traditional security measures. The increasing sophistication of these tactics makes it essential for developers and companies to be cautious when responding to job offers.
Verifying the legitimacy of job ads and the companies behind them is crucial to avoid falling victim to such attacks.
The Impact on Companies and Developers
These hackers primarily aim to infiltrate organizations and steal sensitive data such as intellectual property, financial details, and employee information. Developers, given their access to critical systems, are prime targets. A single breach through a compromised developer can open the door to deeper network infiltration, putting the entire organization at risk.
Smaller companies are especially vulnerable. But what keeps them in such a state?
Many of them don’t prioritize having identity theft insurance, so they rely on meager cybersecurity systems and fail to conceal their employee database from the DPRK’s Bureau 121.
This notorious state-funded group of North Korean hackers exploits weak security defenses, making smaller businesses easy prey. The consequences can be devastating — ranging from stolen proprietary information to severe financial losses and reputational damage.
The risk is even higher for businesses that rely on AI tools for lead generation and data collection. If not properly configured, these tools can be manipulated by hackers to pull data from fake sites. While AI tools offer efficiency, they can inadvertently collect data from phishing sites, leaving the business exposed to cyberattacks.
Steps Companies Should Take to Protect Themselves
As the threat of North Korean cyber actors grows, companies must implement robust measures to protect themselves from infiltration through fake job ads and synthetic identities. The risks posed by these tactics require a proactive and multilayered approach to cybersecurity, with a focus on securing the recruitment process and internal networks.
Strengthen Hiring Practices
Companies need to implement rigorous background checks and verification processes for all job applicants. This includes verifying credentials, contacting previous employers, and using advanced tools to detect fraudulent resumes.
Automated identity verification systems can help identify discrepancies in job applications and flag synthetic identities before they gain access to sensitive data.
Cybersecurity Training for Employees
Training HR teams and hiring managers to spot the warning signs of fake job ads and synthetic identities is critical. Regular cybersecurity training sessions should cover phishing techniques, social engineering tactics, and the latest threat intelligence on cyber actors like North Korea.
This empowers employees to remain vigilant and reduces the likelihood of falling victim to these schemes.
Implement Access Controls
Limiting access to sensitive information and systems is an effective way to reduce the damage from potential breaches. Companies should implement least-privilege policies, ensuring that employees and contractors only have access to the data and systems they need for their roles.
Multi-factor authentication (MFA) should also be enforced for accessing sensitive areas of the network, adding an additional layer of security.
Monitor and Audit Network Activity
Continuous monitoring and auditing of network activity can help detect unusual behaviors that may indicate the presence of a malicious actor. Implementing tools that analyze user behavior, flag unusual login patterns, or detect abnormal data flows can catch cyber actors who manage to slip past initial defenses.
Also, keeping security policies and procedures up to date ensures that the company is prepared for evolving threats. This includes regularly reviewing and revising cybersecurity protocols, hiring processes, and employee training programs based on the latest intelligence and security trends.
Conclusion
Cyber espionage is no longer confined to covert government operations; it’s happening right now in job postings and inboxes around the world.
The stakes are high for companies and developers alike, as state-sponsored actors sharpen their methods, using sophisticated strategies to penetrate corporate defenses.
Protecting against this new breed of threat requires vigilance and a deep understanding of how attackers exploit the weakest links—often, the hiring process itself.
This is not a problem that can be solved with software alone. It demands a cultural shift, where security is embedded in every aspect of business operations and geopolitics alike, requiring the cooperation of everyone from interbank networks to NATO itself.
ZDI-24-1491: Ivanti Avalanche WLAvalancheService TV_FC Infinite Loop Denial-of-Service Vulnerability
Read Time:13 Second
This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of Ivanti Avalanche. Authentication is not required to exploit this vulnerability. The ZDI has assigned a CVSS rating of 7.5. The following CVEs are assigned: CVE-2024-50320.