dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2024-48294

MEDIUM · 5.5 CVSS v3.1 Published 2024-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
A NULL pointer dereference in the component libPdfCore.dll of Wondershare PDF Reader v1.0.9.2544 allows attackers to cause a Denial of Service (DoS) via a crafted PDF 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

A NULL pointer dereference vulnerability exists in libPdfCore.dll of Wondershare PDF Reader v1.0.9.2544. When the application parses a specially crafted PDF file, it attempts to dereference a NULL pointer, causing the application to crash and resulting in a denial of service.

MitigationAvoid opening PDF files from untrusted sources. Wait for and apply the vendor patch when available. Consider using alternative PDF readers as a workaround until the vendor releases a fix.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Check if Wondershare PDF Reader is installed
    Open Windows Settings > Apps > Apps & features, or use Control Panel > Programs and Features, and look for 'Wondershare PDF Reader' in the installed programs list.
    Affected if Wondershare PDF Reader appears in the installed programs list.
  2. Locate the installed version number
    Right-click on the Wondershare PDF Reader executable (usually in C:\Program Files\Wondershare\PDF Reader\ or C:\Program Files (x86)\Wondershare\PDF Reader\) or the libPdfCore.dll file, select Properties, and view the Details tab for the File Version.
    Affected if The version displayed is 1.0.9.2544.
  3. Compare installed version to affected version
    If the version cannot be obtained from the executable, open PowerShell and run: Get-ChildItem 'C:\Program Files\Wondershare\PDF Reader' -Recurse -Filter '*.exe' | ForEach-Object { $_.VersionInfo } to retrieve version information.
    Affected if The version matches 1.0.9.2544.
  4. Verify libPdfCore.dll exists
    Navigate to the installation directory (typically C:\Program Files\Wondershare\PDF Reader\) and confirm that libPdfCore.dll is present on the system.
    Affected if libPdfCore.dll exists in the installation folder and the application version is 1.0.9.2544.

You are affected if Wondershare PDF Reader version 1.0.9.2544 with libPdfCore.dll is installed on your system.

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 PDF files from untrusted sources. Wait for and apply the vendor patch when available. Consider using alternative PDF readers as a workaround until the vendor releases a fix.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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