CVE-2025-29745
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 · uneditedA vulnerability affecting the scanning module in Emsisoft Anti-Malware prior to 2024.12 allows attackers on a remote server to obtain Net-NTLMv2 hash information via a specially created A2S (Emsisoft Custom Scan) extension file.
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 confidenceA vulnerability in Emsisoft Anti-Malware's scanning module (versions prior to 2024.12) allows remote attackers to obtain Net-NTLMv2 hash information via specially crafted A2S (Emsisoft Custom Scan) extension files. This credential disclosure vulnerability has a CVSS score of 7.5 (HIGH) and could enable hash relay or cracking attacks against Windows authentication systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Emsisoft Anti-Malware is installedOpen Programs and Features in Windows Control Panel or use 'Get-ItemProperty' in PowerShell to query the registry under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Emsisoft entriesAffected if Emsisoft Anti-Malware is found on the system
-
Identify the installed versionRight-click the Emsisoft icon in the system tray and select 'About' or open the Emsisoft Control Center and navigate to Help > About; alternatively, check the uninstall entry in the registry for the DisplayVersion valueAffected if The displayed version number is lower than 2024.12 (e.g., 2024.11, 2024.10, earlier)
-
Confirm the vulnerability applies to this installVerify the version is a scanning module version prior to 2024.12 by comparing your exact version string against the affected rangeAffected if The installed version is any release prior to the 2024.12 patch release
You are affected if Emsisoft Anti-Malware is installed and the version is 2024.11 or earlier, as these versions contain the vulnerable A2S scanning module that can leak Net-NTLMv2 hashes when processing specially crafted custom scan files.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Emsisoft Anti-Malware to version 2024.12 or later to remediate this vulnerability. Until the patch is applied, avoid opening A2S extension files from untrusted sources.
Emsisoft Anti-Malware 2024.12 or later
- Download Emsisoft Anti-Malware version 2024.12 or later from the official Emsisoft website
- Ensure you are downloading from the legitimate vendor domain (emsisoft.com)
- Uninstall the current version of Emsisoft Anti-Malware
- Install the updated version 2024.12 or later
- Verify the installation was successful and the software is running the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29745 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-29745 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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