CVE-2020-27856
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 · uneditedThis 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 CR2 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-11434.
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 confidenceThis is an information disclosure vulnerability in Foxit Studio Photo's CR2 (Canon RAW) file parser. The parser fails to properly validate user-supplied data, allowing a read past the end of an allocated buffer. While the primary impact is sensitive information disclosure, the advisory notes this can be chained with other vulnerabilities for code execution.
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= 3.6.6.922CVSS 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.
-
Confirm Foxit Studio Photo is installedCheck for the application in the system program files directory or look for the application in the Windows Start menu / Applications folder. On Windows, common paths include C:\Program Files\Foxit Studio Photo\ or C:\Program Files (x86)\Foxit Studio Photo\Affected if The application is found installed on the system
-
Identify the installed version numberRight-click the Foxit Studio Photo executable (typically named FoxitStudioPhoto.exe), select Properties, and view the Details tab for the Product Version. Alternatively, open the application and check Help > About Foxit Studio PhotoAffected if The installed version is exactly 3.6.6.922
-
Verify the CR2 parser functionality existsAttempt to open a legitimate .CR2 (Canon RAW) file with Foxit Studio Photo, or check if the software lists CR2 support in its supported formats documentation or file open dialogAffected if CR2 file parsing capability is present and functional in the installed version
-
Confirm the software processes Canon RAW filesAttempt to import or open any .CR2 file through the software's File > Open or Import functionality, or check the application's file type associations for CR2 extensionsAffected if The software can open and process CR2 files
A user is affected if Foxit Studio Photo version 3.6.6.922 is installed and the CR2 file parser feature is available and used to open Canon RAW 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 dataUsers should avoid opening untrusted or unverified CR2 files. The vendor should patch the CR2 parser to add proper bounds checking and validate user-supplied data before memory access operations.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27856 — 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-2020-27856 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