Memory leak during invalid option handling
Published Oct 14, 2022 · Updated May 15, 2025
Memory leakage in cmdopts_parse in JasPer 3.0.6 allows local users to leave allocated memory reachable by omitting a command-line option argument. The parser reports the missing argument but fails to release an 8,336-byte allocation before badusage terminates the process. Execution of the local jasper command with an option lacking its required argument is necessary; the allocation persists only until immediate process exit, so no continuing service interruption is demonstrated.
Summary
What happened
Memory leakage in cmdopts_parse in JasPer 3.0.6 allows local users to leave allocated memory reachable by omitting a command-line option argument. The parser reports the missing argument but fails to release an 8,336-byte allocation before badusage terminates the process. Execution of the local jasper command with an option lacking its required argument is necessary; the allocation persists only until immediate process exit, so no continuing service interruption is demonstrated.
The record
- CVE
- CVE-2022-2963
- Published
- Oct 14, 2022
- Updated
- May 15, 2025
- Vendor
- JasPer Software
- Product
- JasPer
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2022CVE publishedPublication date reported by the CVE source.
- May 15, 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=jasper 3.0.6
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
- Issue #332 Valgrind 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