Buffer overwrite via overflowing dimension-product check
Published Jul 27, 2025 · Updated Jul 28, 2025
Buffer overflow in Elliott Mahler Transpose 0.1.0 through 0.2.2 allows attackers to write beyond an output slice via crafted dimensions. The transpose::transpose safety check multiplies input_width by input_height without overflow detection, so a wrapped product can equal both slice lengths before unsafe writes proceed. Exploitation requires a release build and dimension values whose wrapped product matches the input and output lengths; successful triggering corrupts memory or crashes the consuming process.
Summary
What happened
Buffer overflow in Elliott Mahler Transpose 0.1.0 through 0.2.2 allows attackers to write beyond an output slice via crafted dimensions. The transpose::transpose safety check multiplies input_width by input_height without overflow detection, so a wrapped product can equal both slice lengths before unsafe writes proceed. Exploitation requires a release build and dimension values whose wrapped product matches the input and output lengths; successful triggering corrupts memory or crashes the consuming process.
The record
- CVE
- CVE-2023-53156
- Published
- Jul 27, 2025
- Updated
- Jul 28, 2025
- Vendor
- Elliott Mahler
- Product
- Transpose
- Classifications
- CWE-190, CWE-120
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 2025CVE publishedPublication date reported by the CVE source.
- Jul 28, 2025Record 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=0 <0.2.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Release-mode segmentation-fault reproducerproof of concept · demonstrated
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