dbcve.org
Foxit Studio PhotoApplication · Foxitsoftware

CVE-2020-27855

HIGH · 7.8 CVSS v3.1 Published 2021-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
This vulnerability allows remote attackers to disclose sensitive information on affected installations of Foxit Studio Photo 3.6.6.922. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of SR2 files. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated structure. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of the current process. Was ZDI-CAN-11433.

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

Out-of-bounds read vulnerability in Foxit Studio Photo 3.6.6.922 during SR2 (Sony RAW) file parsing. The lack of proper validation of user-supplied data allows reading past the end of an allocated structure, leading to sensitive information disclosure. Requires user to open a malicious SR2 file.

MitigationApply vendor patch/update to Foxit Studio Photo; avoid opening untrusted SR2 files from unknown sources.

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
Foxit Studio PhotoApplication
Affected:= 3.6.6.922

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
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 checks

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

  1. Find installed Foxit Studio Photo version
    Open Windows Control Panel > Programs and Features, or right-click the application in Start menu and select Properties. Also check C:\Program Files\Foxit Studio Photo\ or C:\Program Files (x86)\Foxit Studio Photo\ for the executable and right-click to view Properties > Details for version info.
    Affected if Version shows 3.6.6.922 exactly, indicating the specific affected build.
  2. Verify exact build number
    In the application's Help menu, click About Foxit Studio Photo. The version dialog displays both version number and build number. Confirm the build is 922 to match the affected SR2 (Sony RAW) file parser version.
    Affected if Build number is 922, matching the exact vulnerable release.
  3. Check for SR2 file processing capability
    Verify the Foxit Studio Photo installation includes RAW/Sony SR2 parsing modules. Open the application and attempt to see if SR2 files appear in the Open File dialog (File > Open, then check file type filters).
    Affected if SR2 file type is available in the open dialog, indicating the vulnerable parser is present.
  4. Review recent file access logs
    Check Windows Event Viewer for application crash events, or examine Windows Prefetch files in C:\Windows\Prefetch\ for FoxitStudioPhoto.exe entries. Also check the application's recent files list if accessible.
    Affected if Evidence exists of opening SR2 files from untrusted sources, which would trigger the vulnerable code path.

You are affected if Foxit Studio Photo version 3.6.6.922 (build 922) is installed and SR2 file parsing functionality is present, especially if users have opened SR2 files from 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 patch/update to Foxit Studio Photo; avoid opening untrusted SR2 files from unknown sources.

Fix this in Foxit Studio Photo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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