CVE Tools

CVE-2023-24932

Exploitation likely. EPSS gives it a 12% chance of exploitation in the next 30 days. Fixed versions are out.

Check it yourself

OpenVAS · 10 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.832058

Run the check

Published Updated Sources: CVE.org, NVD, BDU, CSAF

What to do

Find your product and version, then upgrade to the build on the right.

  • Microsoft Windows 10 Version 1809Affected: ≥ 10.0.17763.0, < 10.0.17763.7558Upgrade to: 10.0.17763.7558Affected: ≥ 10.0.0, < 10.0.19042.2965Upgrade to: 10.0.19042.2965Affected: ≥ 10.0.19044.0, < 10.0.19044.6093Upgrade to: 10.0.19044.6093Affected: ≥ 10.0.19045.0, < 10.0.19045.6093Upgrade to: 10.0.19045.6093 + 2 more branchesStated by: CVE record
  • Microsoft Windows 11 Version 24H2Affected: ≥ 10.0.26100.0, < 10.0.26100.4652Upgrade to: 10.0.26100.4652Affected: ≥ 10.0.22000.0, < 10.0.22000.3079Upgrade to: 10.0.22000.3079Affected: ≥ 10.0.22621.0, < 10.0.22621.5624Upgrade to: 10.0.22621.5624Affected: ≥ 10.0.22631.0, < 10.0.22631.5624Upgrade to: 10.0.22631.5624Stated by: CVE record
  • Microsoft Windows Server 2025Affected: ≥ 10.0.26100.0, < 10.0.26100.4652Upgrade to: 10.0.26100.4652Stated by: CVE record
  • Microsoft Windows Server 2019Affected: ≥ 10.0.17763.0, < 10.0.17763.7558Upgrade to: 10.0.17763.7558Stated by: CVE record
  • Microsoft Windows Server 2022Affected: ≥ 10.0.20348.0, < 10.0.20348.3932Upgrade to: 10.0.20348.3932Affected: ≥ 10.0.25398.0, < 10.0.25398.1732Upgrade to: 10.0.25398.1732Stated by: CVE record

Versions as the sources state them. 5 more products have version data. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which Windows version and build each of your PCs and servers is running (Settings > System > About).
  2. Confirm whether the build is older than the fixed version listed for your product (e.g., Windows 10 builds before 10.0.19045.2965, Windows 11 before 10.0.22000.1936/10.0.26100.4652, Windows Server 2019 before 10.0.17763.7558).
  3. Install the latest Windows Update, which includes the fix — no separate download is needed.
  4. If you use Siemens industrial equipment affected by this issue, also update the BIOS to version V1.0.212N or later.
  5. Restart affected machines after updating so the fix takes effect.

Coverage timeline

2 publishers
  1. ESET reports Windows variants of the SprySOCKS backdoor, including kernel-driver stealth and covert C2 communication methods used for espionage.

    ·The Hacker News summary

Sourced from public security reporting — each date is when it was published, not when it happened. 2 further articles named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

Secure Boot Security Feature Bypass Vulnerability

In plain language

Written by AI from the record

This is a flaw in Windows' Secure Boot that requires an attacker to already have deep access to a machine, there's no sign of real-world attacks, and an update exists — so most small businesses don't need to panic, just install Windows updates as usual.

Secure Boot Security Feature Bypass (CWE-863, improper authorization) allows an attacker with existing elevated local privileges to load unsigned bootkit-style code by evading Secure Boot's signature verification, undermining pre-OS integrity guarantees on affected Windows versions.

If you're affected

  • Persistent malware below the OS
  • Bootkit infection risk
  • Bypassed malware defenses
  • Hard-to-detect compromise

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

12% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 1143 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. EPSS band changelow → moderate
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Scored 6.7 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required HighRequires admin or elevated privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Windows 10 Version 1809, not every advisory.