CVE-2021-31437
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 execute arbitrary code on affected installations of Foxit Studio Photo 3.6.6.931. 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 JP2 files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated structure. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-12384.
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 confidenceA buffer write overflow vulnerability exists in Foxit Studio Photo 3.6.6.931 during JP2 (JPEG 2000) file parsing. The lack of proper validation of user-supplied data allows an attacker to write past the end of an allocated structure, leading to arbitrary code execution in the context of the current process. User interaction is required (malicious file or page).
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.933CVSS 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 presence of Foxit Studio Photo on the system. Look for the application in Program Files or Program Files (x86), or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Foxit Studio Photo.Affected if The application is installed on the system.
-
Determine installed version numberRight-click the Foxit Studio Photo executable (usually named FoxitStudioPhoto.exe), select Properties, then go to the Details tab to view the File Version. Alternatively, check Add/Remove Programs or the registry uninstall key for the version string.Affected if The installed version is 3.6.6.933 or any version lower than 3.6.6.933.
-
Verify JP2 file handling is accessibleOpen Foxit Studio Photo and attempt to access features that parse JP2 (JPEG 2000) files. Check if the application can open, import, or process image files through File > Open or similar import functions.Affected if The application can load and parse JP2 files without additional plugins or configurations.
-
Inspect recent JP2 file interactions (optional)Review the application's recent files list, temporary folders (e.g., %TEMP%\FoxitStudioPhoto), or Windows Jump List for recently opened JP2 files. Also check browser download folders if the application has integration.Affected if Any JP2 files have been opened in the affected version of the software.
A user is affected if Foxit Studio Photo version 3.6.6.933 or lower is installed and the application has the capability to process JP2 (JPEG 2000) image 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 dataApply the vendor patch or update Foxit Studio Photo to the latest version. Until patched, avoid opening untrusted JP2 files from unknown sources.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-31437 — 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-2021-31437 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