dbcve.org
Internet Security 2018Application · Bitdefender

CVE-2017-17410

HIGH · 8.8 CVSS v3.0 Published 2017-12-21
Fix available
A fix is available. Upgrade to 73456 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Bitdefender Internet Security 2018. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within emulator 0x102 in cevakrnl.xmd. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated object. An attacker can leverage this vulnerability to execute code under the context of SYSTEM. Was ZDI-CAN-5116.

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

Buffer overflow in Bitdefender Internet Security 2018's emulator component (cevakrnl.xmd, emulator 0x102) due to insufficient validation of user-supplied data, allowing write past end of allocated object and SYSTEM-level code execution.

MitigationApply vendor patch from Bitdefender; avoid opening untrusted files or visiting suspicious URLs until updated.

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
Internet Security 2018Application
Affected:< 73456

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 Bitdefender Internet Security 2018 is installed
    Open Programs and Features (or run 'appwiz.cpl') and look for 'Bitdefender Internet Security 2018' in the installed programs list, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Bitdefender*Internet*Security*2018*"}'
    Affected if Bitdefender Internet Security 2018 appears in the installed programs list
  2. Determine the installed Bitdefender version
    Open Bitdefender and navigate to the About section, or check the registry at HKLM\SOFTWARE\BitDefender under General_ProductVersion, or right-click the Bitdefender icon in the system tray and select 'About'
    Affected if The displayed version number is less than 73456 (e.g., 22.x, 23.x, etc.)
  3. Locate the vulnerable emulator component
    Search for the file 'cevakrnl.xmd' on the system - common paths include C:\Program Files\Bitdefender\Bitdefender Security\ or C:\Program Files\Bitdefender\Internet Security\ (use 'Get-ChildItem -Path "C:\Program Files\Bitdefender" -Recurse -Filter "cevakrnl.xmd" -ErrorAction SilentlyContinue')
    Affected if The file cevakrnl.xmd exists on the system, indicating the emulator component is present
  4. Confirm the overall affected condition
    If steps 1-3 confirm Bitdefender Internet Security 2018 is installed with version < 73456 and cevakrnl.xmd exists, the environment contains the vulnerable configuration
    Affected if All three conditions are met: Bitdefender Internet Security 2018 is installed, version is below 73456, and the emulator component cevakrnl.xmd is present

If Bitdefender Internet Security 2018 is installed with a version lower than 73456 and the cevakrnl.xmd emulator component exists, the system is affected by this vulnerability.

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.

From vendor data
Upgrade available Upgrade to 73456 or later
Fixed in 73456
Interim mitigation

Apply vendor patch from Bitdefender; avoid opening untrusted files or visiting suspicious URLs until updated.

Fix this in Internet Security 2018 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17410 — 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-2017-17410 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