dbcve.org
BindiffApplication · Google

CVE-2021-22545

HIGH · 7.8 CVSS v3.1 Published 2021-06-29
Fix available
A fix is available. Upgrade to 7.0 or later.
See remediation →
80/100
Remediation priority · High
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 attacker can craft a specific IdaPro *.i64 file that will cause the BinDiff plugin to load an invalid memory offset. This can allow the attacker to control the instruction pointer and execute arbitrary code. It is recommended to upgrade BinDiff 7

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

A memory corruption vulnerability in the BinDiff IDA Pro plugin allows remote code execution when processing a specially crafted .i64 database file. The plugin loads an invalid memory offset controlled by the attacker, enabling arbitrary code execution via instruction pointer control.

MitigationUpgrade to BinDiff version 7 or later as specified in the official advisory.

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
BindiffApplication
Affected:< 7.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 BinDiff installation exists
    Check for BinDiff installation directories or executables on the system (common locations include Program Files/BinDiff or user-local BinDiff folders)
    Affected if BinDiff is installed on the system
  2. Identify the installed BinDiff version
    Use the BinDiff executable or check its version information (typically via --version flag or right-click properties in Windows)
    Affected if The version number returned is less than 7.0 (e.g., 6.x, 5.x, etc.)
  3. Confirm the IDA Pro plugin component is present
    Locate the bindiff*.idp or bindiff*.plw plugin file in the IDA Pro plugins directory (commonly IDA Pro/program files/ida plugins)
    Affected if The IDA Pro BinDiff plugin file exists in the plugins directory
  4. Determine if .i64 database files can be processed
    Check if IDA Pro is configured to load or has recently loaded .i64 files, or review BinDiff plugin settings for .i64 file handling
    Affected if The environment processes or can process .i64 database files with the BinDiff plugin enabled

A user is affected if BinDiff version 7.0 or later is NOT installed and the IDA Pro plugin processes .i64 database files.

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 7.0 or later
Fixed in 7.0
Interim mitigation

Upgrade to BinDiff version 7 or later as specified in the official advisory.

Fix this in Bindiff Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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