dbcve.org
Presentations 2020Application · Corel

CVE-2021-38104

MEDIUM · 5.5 CVSS v3.1 Published 2021-10-01
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
IPPP72.FLT in Corel Presentations 2020 20.0.0.200 is affected by an Out-of-bounds Read vulnerability when parsing a crafted file. An unauthenticated attacker could leverage this vulnerability to access unauthorized system memory in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious PPT 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 confidence

IPPP72.FLT filter in Corel Presentations 2020 contains an out-of-bounds read vulnerability triggered when parsing a specially crafted PPT file. The vulnerability allows an attacker to read memory beyond allocated buffer boundaries, potentially exposing sensitive system information in the context of the current user session.

MitigationApply vendor-supplied patch for Corel Presentations 2020 when available. Until then, avoid opening PPT files from untrusted sources and consider running the application in an isolated sandbox environment to limit exposure.

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
Presentations 2020Application
Affected:= 20.0.0.200

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Corel Presentations 2020 installation
    Check for Corel Presentations 2020 in installed programs list via Control Panel > Programs and Features, or use command: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Corel Presentations*2020*'}
    Affected if Corel Presentations 2020 appears in the installed programs list
  2. Confirm installed version number
    Locate the executable or check program metadata: Navigate to the Corel Presentations installation directory (commonly C:\Program Files\Corel\Corel Presentations 2020\) and right-click on the executable to view Properties > Details, or use: (Get-Item 'C:\Program Files\Corel\Corel Presentations 2020\ Presentations.exe').VersionInfo.FileVersion
    Affected if Version displays as exactly 20.0.0.200
  3. Locate the IPPP72.FLT filter file
    Search for IPPP72.FLT in the Corel installation directory: Get-ChildItem -Path 'C:\Program Files\Corel\Corel Presentations 2020' -Filter '*.FLT' -Recurse | Select-Object FullName, Length
    Affected if IPPP72.FLT file exists in the filters or plugins subfolder of the Corel Presentations 2020 directory
  4. Assess exposure to PPT file processing
    Review whether the application is configured to automatically open or preview PPT files, or if users commonly import PPT files: Check file association settings via assoc .ppt and ftype PPTFile, and review trusted file locations in application options
    Affected if Corel Presentations 2020 is set as default handler for PPT files or users routinely open PPT attachments

A user is affected if Corel Presentations 2020 version 20.0.0.200 is installed with the IPPP72.FLT filter present and the application processes PPT files from potentially untrusted sources.

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

Apply vendor-supplied patch for Corel Presentations 2020 when available. Until then, avoid opening PPT files from untrusted sources and consider running the application in an isolated sandbox environment to limit exposure.

Fix this in Presentations 2020 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

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