Memory corruption via invalid JPEGTransW write
Published Jan 25, 2021 · Updated Aug 3, 2024
Memory corruption in IDE_ACDStd.apl in ACDSee Professional 2021 14.0 build 1721 allows context-dependent attackers to trigger an invalid write. JPEGTransW writes one byte through r9 minus four into inaccessible memory while the plug-in processes a crafted BMP image. Opening the crafted image is required; the debugger trace demonstrates exploitable process memory corruption, but no code-execution chain is public.
Summary
What happened
Memory corruption in IDE_ACDStd.apl in ACDSee Professional 2021 14.0 build 1721 allows context-dependent attackers to trigger an invalid write. JPEGTransW writes one byte through r9 minus four into inaccessible memory while the plug-in processes a crafted BMP image. Opening the crafted image is required; the debugger trace demonstrates exploitable process memory corruption, but no code-execution chain is public.
The record
- CVE
- CVE-2021-26026
- Published
- Jan 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo