Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 10.49% for the current model date.
BlackTreeCVE IntelligenceUnknown · Unknown
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | ghostscript | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.64~dfsg-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | ghostscript | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.64~dfsg-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | ghostscript | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.64~dfsg-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | ghostscript | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.64~dfsg-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verifiedThe jpc_crg_getparms function in libjasper/jpc/jpc_cs.c in JasPer 1.900.1 uses an incorrect data type during a certain size calculation, which allows remote attackers to trigger a heap-based buffer overflow and execute arbitrary code, or cause a denial of service (heap memory corruption), via a crafted component registration (CRG) marker segment in a JPEG2000 file.
The jpc_crg_getparms function in libjasper/jpc/jpc_cs.c in JasPer 1.900.1 uses an incorrect data type during a certain size calculation, which allows remote attackers to trigger a heap-based buffer overflow and execute arbitrary code, or cause a denial of service (heap memory corruption), via a crafted component registration (CRG) marker segment in a JPEG2000 file.
A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.
An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may execute code or commands in the affected security context.
The jpc_crg_getparms function in libjasper/jpc/jpc_cs.c in JasPer 1.900.1 uses an incorrect data type during a certain size calculation, which allows remote attackers to trigger a heap-based buffer overflow and execute arbitrary code, or cause a denial of service (heap memory corruption), via a crafted component registration (CRG) marker segment in a JPEG2000 file.
A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.
An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may execute code or commands in the affected security context.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.
AV:N/AC:M/Au:N/C:P/I:P/A:POperational remediation based on structured source evidence.
Published 15 Dec 2011 · Last source change 21 Oct 2024, 16:11 UTC · CWE-787 · Out-of-bounds Write
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.