Skip to main content
CVE-2024-39707VulnerabilityPublished Updated

CVE-2024-39707: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2024-39707, organizations should: 1) Identify all systems using Insyde IHISI firmware versions affected by this vulnerability. 2) Apply the firmware updates corresponding to kernel versions 5.2 through 5.6 as listed (05.29.19, 05.38.19, 05.46.19, 05.54.19, 05.61.19) promptly to ensure the authentication requirement is enforced for factory default restoration. 3) Restrict local administrative access to trusted personnel only, minimizing the risk of privilege abuse. 4) Monitor for unusual firmware-related activities or rollback attempts using endpoint detection tools capable of firmware integrity verification. 5) Implement layered security controls such as Secure Boot and measured boot to detect unauthorized firmware changes. 6) Regularly audit firmware versions and patch status as part of vulnerability management programs. 7) Educate IT staff about the risks of firmware rollback attacks and the importance of applying vendor firmware patches. 8) Where possible, leverage hardware-based security features like TPM to enhance firmware integrity protections. These steps go beyond generic advice by focusing on firmware-specific patching, access control, and monitoring strategies tailored to this vulnerability.

Description

Insyde IHISI function 0x49 can restore factory defaults for certain UEFI variables without further authentication by default, which could lead to a possible roll-back attack in certain platforms. This is fixed in: kernel 5.2, version 05.29.19; kernel 5.3, version 05.38.19; kernel 5.4, version 05.46.19; kernel 5.5, version 05.54.19; kernel 5.6, version 05.61.19.

References

Community reviews

Loading reviews…