Bug 1488958 (CVE-2017-13745)
| Summary: | CVE-2017-13745 jasper: reachable abort in jpc_dec_process_sot() | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Andrej Nemec <anemec> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | bmcclain, cfergeau, eedri, erik-fedora, jridky, lsurette, mgoldboi, michal.skrivanek, mike, mperina, rdieter, rh-spice-bugs, rjones, sbonazzo, sfowler, srevivo, tburke |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | jasper 2.0.17 | Doc Type: | If docs needed, set a value |
| Doc Text: |
A vulnerability was found in Jasper, where a flaw in the jpc_dec_process_sot function in jpc/jpc_dec.c can lead to a denial of service remote attacker could exploit this vulnerability by using a specially crafted file, causing the application to crash.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-10-21 11:56:16 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1434464, 1434465, 1434467, 1485274, 1610139, 1910580 | ||
| Bug Blocks: | 1449402 | ||
|
Description
Andrej Nemec
2017-09-06 13:54:47 UTC
Created jasper tracking bugs for this issue: Affects: fedora-all [bug 1434464] Created mingw-jasper tracking bugs for this issue: Affects: epel-7 [bug 1434465] Affects: fedora-all [bug 1434467] Reported upstream via: https://github.com/mdadams/jasper/issues/166 This issue remains unfixed in the current upstream version 2.0.14. *** Bug 1610135 has been marked as a duplicate of this bug. *** Upstream commit: https://github.com/jasper-software/jasper/commit/fcbabdaaba217124c92dc29472596146756b968e The issue was fixed upstream in jasper 2.0.17. |