CVE-2022-36947
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 · uneditedUnsafe Parsing of a PNG tRNS chunk in FastStone Image Viewer through 7.5 results in a stack buffer overflow.
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 confidenceFastStone Image Viewer through version 7.5 contains a stack buffer overflow vulnerability in PNG image parsing. The tRNS chunk, which stores transparency information for indexed-color and grayscale PNG images, is parsed unsafely allowing an attacker to overflow a stack-based buffer with specially crafted PNG files, potentially leading to arbitrary 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< 7.6CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 FastStone Image Viewer is installedLook for FastStone Image Viewer in your installed programs list (Windows Settings > Apps & Features, or use 'Get-ItemProperty' in PowerShell for registry keys like HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* or check common installation directories)Affected if The application is present on the system
-
Determine the installed version numberRight-click the FastStone Image Viewer executable, select Properties, and check the 'Details' tab for the Product Version, or launch the application and go to Help > About to view the versionAffected if The displayed version is any version prior to 7.6 (for example, 7.5, 7.4, etc.)
-
Identify if untrusted PNG files are openedReview whether users in your environment open PNG files from untrusted or external sources using FastStone Image ViewerAffected if Users routinely open PNG files from untrusted sources with a vulnerable version of the viewer
You are affected if FastStone Image Viewer version 7.5 or earlier is installed and users open specially crafted PNG files with the application.
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.
dbcve · scoped7.6
Upgrade to FastStone Image Viewer version 7.6 or later, or avoid opening untrusted PNG files with vulnerable versions until the update is applied.
FastStone Image Viewer 7.6 or later
- 1. Visit the official FastStone website at www.faststone.org
- 2. Navigate to the Downloads or Products section
- 3. Download the latest version of FastStone Image Viewer (version 7.6 or later)
- 4. Run the installer and follow the prompts to upgrade
- 5. Verify the installed version by opening FastStone Image Viewer and checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36947 — 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-2022-36947 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