dbcve.org
WibukeyApplication · Wibu

CVE-2024-45182

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 6.70 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WibuKey64.sys kernel driver in WibuKey before v6.70 contains an improper bounds check vulnerability. Specially crafted packets can trigger an arbitrary memory address read, leading to denial of service. This is a memory safety issue in a kernel-mode driver used by WibuKey software protection/licensing systems.

MitigationUpdate WibuKey to version 6.70 or later to obtain the fixed driver with proper bounds checking. As this is a kernel driver vulnerability with DoS impact, priority should be given to production systems using the affected software.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WibukeyApplication
Affected:< 6.70

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WibuKey driver is present
    Search for WibuKey64.sys file in the system drivers directory (e.g., C:\Windows\System32\drivers\) or check for WibuKey-related services/registry entries.
    Affected if WibuKey64.sys is found on the system, indicating WibuKey software protection is installed.
  2. Retrieve driver file version
    Right-click on WibuKey64.sys, select Properties, then view the Details tab for the File Version. Alternatively, use PowerShell: Get-ItemProperty on the driver path.
    Affected if The driver file exists and has a version property that can be inspected.
  3. Check WibuKey software version
    Check the installed WibuKey application version via Windows Programs and Features, or look for version information in the WibuKey installation directory.
    Affected if WibuKey software version is visible in installed programs or configuration files.
  4. Compare version to affected range
    Compare the installed WibuKey version (or WibuKey64.sys driver version) against the vulnerable range: versions prior to 6.70.
    Affected if Installed version is below 6.70 (e.g., 6.60, 6.50, etc.), meaning the improper bounds check vulnerability is present.
  5. Verify kernel driver is loaded
    Check if WibuKey64.sys is currently loaded in memory using 'driverquery /v' or 'Get-Process' with driver information, or check the Windows registry for the driver's service status.
    Affected if The vulnerable driver version is actively loaded in kernel mode, making the memory address read vulnerability reachable.

If WibuKey is installed with a version of WibuKey64.sys or WibuKey software below 6.70 and the driver is present or loaded, the system is affected by CVE-2024-45182.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.70 or later
Fixed in 6.70
Interim mitigation

Update WibuKey to version 6.70 or later to obtain the fixed driver with proper bounds checking. As this is a kernel driver vulnerability with DoS impact, priority should be given to production systems using the affected software.

Recommended fix High confidence

WibuKey v6.70

  1. Obtain WibuKey v6.70 or later from the official Wibu-Systems website (wibu.com or cdn.wibu.com)
  2. Apply the vendor's standard upgrade procedure for the WibuKey software to replace the vulnerable version
  3. Restart any services or systems using WibuKey after applying the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wibukey Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45182 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data