Memory corruption via missing image bounds check
Published Feb 24, 2022 · Updated Aug 2, 2024
Out-of-bounds heap access in the image loader in Blender 3.x and 2.93.8 allows attackers to corrupt memory or crash through an image. The image loader omits a required bounds check while processing untrusted image data, permitting access beyond its allocated heap buffer. Reaching the flaw requires user interaction to load the image; confirmed consequences are memory corruption and a process crash.
Summary
What happened
Out-of-bounds heap access in the image loader in Blender 3.x and 2.93.8 allows attackers to corrupt memory or crash through an image. The image loader omits a required bounds check while processing untrusted image data, permitting access beyond its allocated heap buffer. Reaching the flaw requires user interaction to load the image; confirmed consequences are memory corruption and a process crash.
The record
- CVE
- CVE-2022-0546
- Published
- Feb 24, 2022
- Updated
- Aug 2, 2024
- Vendor
- Blender Foundation
- Product
- Blender
- Classifications
- CWE-190, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Blender 3.x and 2.93.8
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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