CVE-2019-9139
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 · uneditedDaviewIndy 8.98.7 and earlier versions have a Integer overflow vulnerability, triggered when the user opens a malformed PDF file that is mishandled by Daview.exe. Attackers could exploit this and arbitrary code execution.
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 confidenceDaviewIndy 8.98.7 and earlier versions contain an integer overflow vulnerability in the PDF parsing component (Daview.exe). When processing a malformed PDF file, the integer overflow can be exploited to achieve arbitrary code execution on the targeted system.
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<= 8.98.7CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Daview.exeSearch for Daview.exe in common installation directories such as C:\Program Files\Datools\DaviewIndy\ or C:\Program Files (x86)\Datools\DaviewIndy\, or use the command 'dir /s /b C:\Daview.exe 2>nul' to search the entire C: driveAffected if Daview.exe is found on the system
-
Get the installed versionRight-click on Daview.exe, select Properties, then go to the Details tab to view the File Version, or use PowerShell: (Get-Item 'C:\Program Files\Datools\DaviewIndy\Daview.exe').VersionInfo.FileVersionAffected if The version displayed is 8.98.7 or lower, or the version field is empty/unavailable indicating an old installation
-
Confirm PDF parsing componentLaunch DaviewIndy and attempt to open a PDF file, or verify that Daview.exe is associated with PDF file handling by checking file associations in the Windows Registry under HKCR\.pdfAffected if DaviewIndy can open or process PDF files, indicating the vulnerable PDF parsing component is active
-
Check for recent usageReview recent files opened by DaviewIndy via Windows Jump List, recent documents, or application log files if available, or check prefetch files for Daview.exeAffected if PDF files have been recently opened with DaviewIndy, confirming the attack surface is present
The system is affected if Daview.exe version 8.98.7 or lower is installed and the application is capable of parsing PDF 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.
From vendor dataUpdate DaviewIndy to the latest version from the vendor. Until an update is available, exercise caution when opening PDF files from untrusted sources.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9139 — 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-2019-9139 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