CVE-2025-1118 Grub2: commands/dump: the dump command is not in lockdown when secure boot is enabled

A flaw was found in grub2. Grub's dump command is not blocked when grub is in lockdown mode, which allows the user to read any memory information, and an attacker may leverage this in order to extract signatures, salts, and other sensitive information from the memory...

CVE-2025-1118 Grub2: commands/dump: the dump command is not in lockdown when secure boot is enabled

A flaw was found in grub2. Grub's dump command is not blocked when grub is in lockdown mode, which allows the user to read any memory information, and an attacker may leverage this in order to extract signatures, salts, and other sensitive information from the memory...

CVE-2025-1118

CVE-2025-1118 affects grub2 where the dump command is not blocked in lockdown/Secure Boot mode, allowing a local attacker to read arbitrary memory (signatures, salts, and other sensitive data). The issue is tied to grub2 memory access during lockdown and memory leakage from the dump/read path. Pu...

Security update for grub2

This update for grub2 fixes the following issues: CVE-2024-45781: Fixed strcpy overflow in ufs. bsc1233617 CVE-2024-56737: Fixed a heap-based buffer overflow in hfs. bsc1234958 CVE-2024-45782: Fixed strcpy overflow in hfs. bsc1233615 CVE-2024-45780: Fixed an overflow in tar/cpio. bsc1233614...

Security update for grub2

This update for grub2 fixes the following issues: CVE-2024-45781: Fixed strcpy overflow in ufs. bsc1233617 CVE-2024-56737: Fixed a heap-based buffer overflow in hfs. bsc1234958 CVE-2024-45782: Fixed strcpy overflow in hfs. bsc1233615 CVE-2024-45780: Fixed an overflow in tar/cpio. bsc1233614...

CVE-2025-1118

A flaw was found in grub2. Grub's dump command is not blocked when grub is in lockdown mode, which allows the user to read any memory information, and an attacker may leverage this in order to extract signatures, salts, and other sensitive information from the memory...

UBUNTU-CVE-2025-1118

A flaw was found in grub2. Grub's dump command is not blocked when grub is in lockdown mode, which allows the user to read any memory information, and an attacker may leverage this in order to extract signatures, salts, and other sensitive information from the memory...

PT-2025-7491

Name of the Vulnerable Software and Affected Versions Grub2 affected versions not specified Description A flaw was found in Grub2, where the dump command is not blocked when Grub is in lockdown mode. This allows a user to read any memory information, and an attacker may leverage this to extract...

PT-2025-6873

Name of the Vulnerable Software and Affected Versions Fedora Linux kernel versions 6.12 through 6.12.13 Description A critical flaw in the Fedora Linux kernel disables Lockdown Mode by default, potentially allowing attackers to bypass Secure Boot protections. This issue affects systems starting a...

CVE-2025-23530

Cross-Site Request Forgery CSRF vulnerability in yonisink Custom Post Type Lockdown custom-post-type-lockdown allows Privilege Escalation.This issue affects Custom Post Type Lockdown: from n/a through = 1.11...

CVE-2025-23530 WordPress Custom Post Type Lockdown plugin <= 1.11 - CSRF to Privilege Escalation vulnerability

Cross-Site Request Forgery CSRF vulnerability in Yonatan Reinberg of Social Ink Custom Post Type Lockdown allows Privilege Escalation.This issue affects Custom Post Type Lockdown: from n/a through 1.11...

CVE-2025-23530

CVE-2025-23530 (Custom Post Type Lockdown) is a CSRF-to-Privilege Escalation vulnerability affecting the Custom Post Type Lockdown WordPress plugin (affected: 1.0 through 1.11). Public data from NVD/Red Hat confirms a CVSS v3.1 base score of 8.8 (HIGH) with network attack vector, low attack compl...

CVE-2025-23530 WordPress Custom Post Type Lockdown plugin <= 1.11 - CSRF to Privilege Escalation vulnerability

Cross-Site Request Forgery CSRF vulnerability in yonisink Custom Post Type Lockdown custom-post-type-lockdown allows Privilege Escalation.This issue affects Custom Post Type Lockdown: from n/a through = 1.11...

WordPress Custom Post Type Lockdown plugin <= 1.11 - CSRF to Privilege Escalation vulnerability

CSRF to Privilege Escalation vulnerability discovered by Mika in WordPress Plugin Custom Post Type Lockdown versions = 1.11...

WordPress plugin Custom Post Type Lockdown 跨站请求伪造漏洞

WordPress and WordPress plugin are both products of the WordPress Foundation.WordPress is a blogging platform developed using the PHP language. The platform supports personal blog sites on PHP and MySQL servers.WordPress plugin is an application plugin. A cross-site request forgery vulnerability...

PT-2025-4924 · Unknown · Custom Post Type Lockdown

Name of the Vulnerable Software and Affected Versions: Custom Post Type Lockdown versions prior to 1.11 Description: The issue is a Cross-Site Request Forgery CSRF vulnerability that allows privilege escalation. This means an attacker can trick a user into performing unintended actions on a web...

CVE-2022-21505

In the linux kernel, if IMA appraisal is used with the "imaappraise=log" boot param, lockdown can be defeated with kexec on any machine when Secure Boot is disabled or unavailable. IMA prevents setting "imaappraise=log" from the boot param when Secure Boot is enabled, but this does not cover case...

CVE-2022-21505

In the linux kernel, if IMA appraisal is used with the "imaappraise=log" boot param, lockdown can be defeated with kexec on any machine when Secure Boot is disabled or unavailable. IMA prevents setting "imaappraise=log" from the boot param when Secure Boot is enabled, but this does not cover case...

DEBIAN-CVE-2022-21505

In the linux kernel, if IMA appraisal is used with the "imaappraise=log" boot param, lockdown can be defeated with kexec on any machine when Secure Boot is disabled or unavailable. IMA prevents setting "imaappraise=log" from the boot param when Secure Boot is enabled, but this does not cover case...

CVE-2022-21505

In the linux kernel, if IMA appraisal is used with the "imaappraise=log" boot param, lockdown can be defeated with kexec on any machine when Secure Boot is disabled or unavailable. IMA prevents setting "imaappraise=log" from the boot param when Secure Boot is enabled, but this does not cover case...