Skip to main content
VulnerabilityPublished Updated

CVE-2024-45182: WIBU-SYSTEMS WibuKey · Improper Resource Shutdown or Release

Source CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium · fixed in 6.70 : update WIBU-SYSTEMS WibuKey when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects
WIBU-SYSTEMS WibuKey before 6.70
Patch
Available – fixed in 6.70
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Sep 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 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-45182, organizations should promptly upgrade WIBU-SYSTEMS WibuKey software to version 6.70 or later, where the vulnerability is fixed. In environments where immediate patching is not feasible, restrict local access to systems running the vulnerable driver to trusted personnel only, and monitor for unusual system crashes or instability that could indicate exploitation attempts. Employ endpoint protection solutions capable of detecting anomalous kernel driver behavior. Additionally, implement strict privilege management to minimize the number of users with local low-level access. Conduct regular audits of software versions and driver integrity to ensure compliance with security policies. For critical systems, consider isolating or segmenting machines running WibuKey to limit potential impact. Maintain up-to-date backups and incident response plans to quickly recover from potential denial of service events.

Description

An issue was discovered in WibuKey64.sys in WIBU-SYSTEMS WibuKey before v6.70 and fixed in v.6.70 An improper bounds check allows specially crafted packets to cause an arbitrary address read, resulting in Denial of Service.

References

Community reviews

Loading reviews…