CVE-2020-27828: There's a flaw in jasper's jpc encoder in versions prior to 2.0.23.
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 72.6% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: jasper-devel (AlmaLinux:8) 2.0.14-5.el8; jasper-libs (AlmaLinux:8) 2.0.14-5.el8; jasper (openSUSE:Leap 15.2) 2.0.14-lp152.7.6.1.
Low priority for now. Upgrade to jasper-devel (AlmaLinux:8) 2.0.14-5.el8; jasper-libs (AlmaLinux:8) 2.0.14-5.el8; jasper (openSUSE:Leap 15.2) 2.0.14-lp152.7.6.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
There's a flaw in jasper's jpc encoder in versions prior to 2.0.23. Crafted input provided to jasper by an attacker could cause an arbitrary out-of-bounds write. This could potentially affect data confidentiality, integrity, or application availability.
- Published
- Dec 11, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 72th percentile
- CWE
- CWE-20
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jasper project | jasper | cpe:2.3:a:jasper_project:jasper |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a jasper
- prior to 2.0.23affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora32
- fedoraproject fedora33
- jasper project jasperbefore 2.0.23
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | jasper-devel | before 2.0.14-5.el8 | 2.0.14-5.el8 |
| AlmaLinux:8 | jasper-libs | before 2.0.14-5.el8 | 2.0.14-5.el8 |
| openSUSE:Leap 15.2 | jasper | before 2.0.14-lp152.7.6.1 | 2.0.14-lp152.7.6.1 |
| Red Hat:enterprise_linux:8::appstream | jasper | before 0:2.0.14-5.el8 | 0:2.0.14-5.el8 |
| Red Hat:enterprise_linux:8::appstream | jasper-debuginfo | before 0:2.0.14-5.el8 | 0:2.0.14-5.el8 |
| Red Hat:enterprise_linux:8::appstream | jasper-debugsource | before 0:2.0.14-5.el8 | 0:2.0.14-5.el8 |
| Red Hat:enterprise_linux:8::appstream | jasper-libs | before 0:2.0.14-5.el8 | 0:2.0.14-5.el8 |
| Red Hat:enterprise_linux:8::appstream | jasper-libs-debuginfo | before 0:2.0.14-5.el8 | 0:2.0.14-5.el8 |
| Red Hat:enterprise_linux:8::appstream | jasper-utils-debuginfo | before 0:2.0.14-5.el8 | 0:2.0.14-5.el8 |
| Red Hat:enterprise_linux:8::crb | jasper-devel | before 0:2.0.14-5.el8 | 0:2.0.14-5.el8 |
| Rocky Linux:8 | jasper | before 0:2.0.14-5.el8 | 0:2.0.14-5.el8 |
| SUSE:HPE Helion OpenStack 8 | jasper | before 1.900.14-195.25.1 | 1.900.14-195.25.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | jasper | before 2.0.14-3.19.1 | 2.0.14-3.19.1 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | jasper | before 1.900.14-134.33.20.1 | 1.900.14-134.33.20.1 |
Same product
jasper project: all recordsOther highest-scoring records for the same primary product.
- CVE-2008-3520Multiple integer overflows in JasPer 1.900.1 might allow context-dependent attackers to have an unknown impact via a crafted image file…38Monitor
- CVE-2015-8751Integer overflow in the jas_matrix_create function in JasPer allows context-dependent attackers to have unspecified impact via a crafted…36Monitor
- CVE-2018-19541An issue was discovered in JasPer 1.900.8, 1.900.9, 1.900.10, 1.900.11, 1.900.12, 1.900.13, 1.900.14, 1.900.15, 1.900.16, 1.900.17…36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2018-20584Dec 30, 2018 · JasPer 2.0.14 allows remote attackers to cause a denial of service (application hang) via an attempted conversion to the jp2 format.27Monitor
- ← EarlierCVE-2018-20622Dec 31, 2018 · JasPer 2.0.14 has a memory leak in base/jas_malloc.c in libjasper.a when "--output-format jp2" is used.27Monitor
- Later →CVE-2021-3272Jan 27, 2021 · jp2_decode in jp2/jp2_dec.c in libjasper in JasPer 2.0.24 has a heap-based buffer over-read when there is an invalid relationship between…22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:jasper-devel | 2.0.14-5.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:jasper-libs | 2.0.14-5.el8 · AlmaLinux:8 | Package registry (OSV) |
| opensuse:jasper | 2.0.14-lp152.7.6.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| red hat:jasper | 0:2.0.14-5.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jasper-debuginfo | 0:2.0.14-5.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jasper-debugsource | 0:2.0.14-5.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jasper-devel | 0:2.0.14-5.el8 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| red hat:jasper-libs | 0:2.0.14-5.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jasper-libs-debuginfo | 0:2.0.14-5.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jasper-utils-debuginfo | 0:2.0.14-5.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:jasper | 0:2.0.14-5.el8 · Rocky Linux:8 | Package registry (OSV) |
| suse:jasper | 2.0.14-3.19.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/COBEVDBUO3QTNR6YQBBTIQKNIB6W3MJ2/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EBZZ2SNTQ4BSA6PNJCTOAKXIAXYNNF6V/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/N4ALB4SXHURLVWKAOKYRNJXPABW3M22M/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UPOVZTSIQPW2H4AFLMI3LHJEZGBVEQET/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.