Local code execution via zero-length ICC text
Published Jan 16, 2024 · Updated Nov 4, 2025
Invalid memory write in JasPer 4.1.1 and earlier allows local users to execute arbitrary code by processing a crafted JP2 image. The jas_icctxt_input function allocates an ICC text buffer from an attacker-controlled count, then writes a terminator at count minus one without rejecting a zero count. A local user must cause JasPer or a linked application to decode the crafted file; code runs in the decoding process's security context.
Summary
What happened
Invalid memory write in JasPer 4.1.1 and earlier allows local users to execute arbitrary code by processing a crafted JP2 image. The jas_icctxt_input function allocates an ICC text buffer from an attacker-controlled count, then writes a terminator at count minus one without rejecting a zero count. A local user must cause JasPer or a linked application to decode the crafted file; code runs in the decoding process's security context.
The record
- CVE
- CVE-2023-51257
- Published
- Jan 16, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 16, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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?
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.
Weakness, pattern, technique
Public exploit references
- JasPer issue 367 crafted JP2 proof of conceptproof 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