Wildbit ViewerApplication · Wildbit Soft

CVE-2020-23894

MEDIUM · 5.5 CVSS v3.1 Published 2021-11-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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
A User Mode Write AV in ntdll!RtlpCoalesceFreeBlocks+0x268 of WildBit Viewer v6.6 allows attackers to cause a denial of service (DoS) via a crafted tiff 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 · moderate confidence

WildBit Viewer v6.6 contains a user-mode write access violation vulnerability in the ntdll memory management function RtlpCoalesceFreeBlocks when processing a specially crafted TIFF file. This causes an application crash resulting in denial of service.

MitigationAvoid opening untrusted or unverified TIFF files with WildBit Viewer. Check for vendor updates or patches from WildBit. Consider using alternative image viewers that are actively maintained.

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
Wildbit ViewerApplication
Affected:= 6.6

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 WildBit Viewer installation
    Check for WildBit Viewer in the system: Look for 'WildBit Viewer' in Program Files (usually C:\Program Files\WildBit Viewer or C:\Program Files (x86)\WildBit Viewer). Also check Start Menu for WildBit Viewer shortcut.
    Affected if WildBit Viewer is installed on the system
  2. Confirm installed version number
    Open WildBit Viewer, go to Help > About, or right-click the executable and view Properties > Details to find the version. Alternatively, locate the Viewer.exe file and check its version property.
    Affected if The installed version is exactly 6.6 (the affected version)
  3. Identify TIFF file handling capability
    WildBit Viewer supports multiple image formats including TIFF. Check if the application has been used to open or can open .tif and .tiff files. The vulnerability triggers when processing a specially crafted TIFF file.
    Affected if WildBit Viewer 6.6 is used to open or process TIFF files from untrusted sources

A user is affected if WildBit Viewer version 6.6 is installed and a specially crafted TIFF file is opened with this application, leading to a crash.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid opening untrusted or unverified TIFF files with WildBit Viewer. Check for vendor updates or patches from WildBit. Consider using alternative image viewers that are actively maintained.

Fix this in Wildbit Viewer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $2,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-23894 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-23894 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