Security readout for executives and security teams
Plain-English summary
A malicious Photoshop PSD file can trigger a buffer overflow in FreeImage 3.19.0 r1859 when the thumbnail parser reads it. The reported impact is arbitrary code execution, so systems that automatically process untrusted PSD uploads deserve prompt attention.
Executive priority
Treat this as high priority where FreeImage processes external PSD files. Business risk is concentrated in upload, conversion, and thumbnailing services because a single malicious file could affect processing hosts.
Technical view
The issue is reported in psdThumbnail::Read in PSDParser.cpp in FreeImage 3.19.0 r1859. The CVE description says crafted PSD input can cause a buffer overflow and allow arbitrary code execution. The record provides no CVSS, CWE, CPE, or exact fixed version.
Likely exposure
Exposure is most likely in applications, services, or desktop workflows that use FreeImage to parse PSD files from users, partners, or public uploads.
Exploitation context
The supplied sources do not show active exploitation, and the CVE is not marked KEV. Exploitation appears file-triggered: an attacker would need a target workflow to open or process a crafted PSD.
Researcher notes
Evidence is incomplete. The affected field is n/a, but the title and description name FreeImage 3.19.0 r1859. No exploit status, CVSS, CPEs, or precise remediation version is included in the supplied bundle.
Mitigation direction
- Identify FreeImage usage in products, containers, and image-processing services.
- Prioritize systems that accept or automatically process PSD files.
- Check FreeImage and OS distributor advisories for fixed packages.
- Update affected packages where vendor fixes are available.
- Restrict or isolate PSD processing until patched.
- Monitor crash reports from image thumbnail or conversion pipelines.
Validation and detection
- Review SBOMs and package inventories for FreeImage 3.19.0 r1859.
- Map all upload and conversion paths that accept PSD files.
- Confirm whether Fedora or vendor package updates are installed.
- Check whether untrusted PSD parsing runs with least privilege.
- Verify file-type restrictions and sandboxing around image processing.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-24293 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://sourceforge.net/p/freeimage/discussion/36111/thread/afb98701eb/CVE reference
- FEDORA-2023-604a7d56b0CVE reference · vendor-advisory
- FEDORA-2023-8e640cb540CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.