CVE-2021-27845: A Divide-by-zero vulnerability exists in JasPer Image Coding Toolkit 2.0 in jasper/src/libjasper/jpc/jpc_enc.c
Noroxi assessment
Priority: Monitor (action score 22/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: 0.65% (FIRST EPSS); higher than 51.7% 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 (openSUSE:Leap 15.3) 2.0.14-3.22.1; jasper (openSUSE:Tumbleweed) 4.0.0-2.1; jasper (SUSE:Linux Enterprise Module for Basesystem 15 SP3) 2.0.14-3.22.1.
Low priority for now. Upgrade to jasper (openSUSE:Leap 15.3) 2.0.14-3.22.1; jasper (openSUSE:Tumbleweed) 4.0.0-2.1; jasper (SUSE:Linux Enterprise Module for Basesystem 15 SP3) 2.0.14-3.22.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
- Published
- Jul 15, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- CWE-369
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jasper project jasper2.0.0 and later · before 2.0.17
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.3 | jasper | before 2.0.14-3.22.1 | 2.0.14-3.22.1 |
| openSUSE:Tumbleweed | jasper | before 4.0.0-2.1 | 4.0.0-2.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | jasper | before 2.0.14-3.22.1 | 2.0.14-3.22.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | jasper | before 1.900.14-195.28.1 | 1.900.14-195.28.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-2021-3443Mar 25, 2021 · A NULL pointer dereference flaw was found in the way Jasper versions before 2.0.27 handled component references in the JP2 image format…22Monitor
- ← EarlierCVE-2021-3467Mar 25, 2021 · A NULL pointer dereference flaw was found in the way Jasper versions before 2.0.26 handled component references in CDEF box in the JP2…22Monitor
- Later →CVE-2022-40755Sep 16, 2022 · JasPer 3.0.6 allows denial of service via a reachable assertion in the function inttobits in libjasper/base/jas_image.c.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 |
|---|---|---|
| opensuse:jasper | 2.0.14-3.22.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| suse:jasper | 1.900.14-195.28.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | 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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-369 · Divide By ZeroCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →