CVE-2018-19542
published 2018-11-26CVE-2018-19542: An issue was discovered in JasPer 2.0.14. There is a NULL pointer dereference in the function jp2_decode in libjasper/jp2/jp2_dec.c, leading to a denial of…
PriorityP425medium6.5CVSS 3.0
AVNACLPRNUIRSUCNINAH
EPSS
1.95%
78.1th percentile
An issue was discovered in JasPer 2.0.14. There is a NULL pointer dereference in the function jp2_decode in libjasper/jp2/jp2_dec.c, leading to a denial of service.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| canonical | ubuntu_linux | — | — |
| debian | debian_linux | — | — |
| jasper_project | jasper | — | — |
| jasper_project | jasper | >= 0 < 1.900.1-debian1-2.4ubuntu1.3 | 1.900.1-debian1-2.4ubuntu1.3 |
| opensuse | leap | — | — |
| suse | linux_enterprise_desktop | — | — |
| suse | linux_enterprise_server | — | — |
| suse | linux_enterprise_server | — | — |
CVSS provenance
nvdv3.06.5MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:N/A:P
osv6.5MEDIUM
vendor_redhat6.5MEDIUM
vendor_ubuntu5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
JasPer vulnerabilities
vendor_ubuntu·2021-01-11·CVSS 5.5
CVE-2017-9782 [MEDIUM] JasPer vulnerabilities
Title: JasPer vulnerabilities
Summary: Several security issues were fixed in JasPer.
It was discovered that Jasper incorrectly certain files.
An attacker could possibly use this issue to cause a crash.
(CVE-2018-18873)
It was discovered that Jasper incorrectly handled certain files.
An attacker could possibly use this issue to cause a denial of service.
(CVE-2018-19542)
It was discovered that Jasper incorrectly handled certain JPC encoders.
An attacker could possibly use this issue to execute arbitrary code.
(CVE-2020-27828)
It was discovered that Jasper incorrectly handled certain images.
An attacker could possibly use this issue to expose sensitive information
or cause a crash.
(CVE-2017-9782)
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c
vendor_redhat·2018-07-13·CVSS 6.5
CVE-2018-19542 [MEDIUM] CWE-476 jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c
jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c
An issue was discovered in JasPer 2.0.14. There is a NULL pointer dereference in the function jp2_decode in libjasper/jp2/jp2_dec.c, leading to a denial of service.
A vulnerability was found in Jasper due to a NULL pointer dereference in the jp2_decode function within libjasper/jp2/jp2_dec.c, where an attacker could exploit this flaw by persuading a victim to open a specially crafted file, causing the application to crash and resulting in a denial of service condition.
Statement: This vulnerability was rated as LOW severity because it requires the victim to open a specially crafted file, it doesn't allow full system compromise, it can cause the application to crash temporarily.
Package: netpbm (Red Hat Enterprise Linux 5)
GHSA
GHSA-qp52-65cq-8g48: An issue was discovered in JasPer 2
ghsa_unreviewed·2022-05-13
CVE-2018-19542 [MEDIUM] CWE-476 GHSA-qp52-65cq-8g48: An issue was discovered in JasPer 2
An issue was discovered in JasPer 2.0.14. There is a NULL pointer dereference in the function jp2_decode in libjasper/jp2/jp2_dec.c, leading to a denial of service.
OSV
jasper vulnerabilities
osv·2021-01-11·CVSS 5.5
CVE-2018-18873 [MEDIUM] jasper vulnerabilities
jasper vulnerabilities
It was discovered that Jasper incorrectly certain files.
An attacker could possibly use this issue to cause a crash.
(CVE-2018-18873)
It was discovered that Jasper incorrectly handled certain files.
An attacker could possibly use this issue to cause a denial of service.
(CVE-2018-19542)
It was discovered that Jasper incorrectly handled certain JPC encoders.
An attacker could possibly use this issue to execute arbitrary code.
(CVE-2020-27828)
It was discovered that Jasper incorrectly handled certain images.
An attacker could possibly use this issue to expose sensitive information
or cause a crash.
(CVE-2017-9782)
OSV
CVE-2018-19542: An issue was discovered in JasPer 2
osv·2018-11-26·CVSS 6.5
CVE-2018-19542 [MEDIUM] CVE-2018-19542: An issue was discovered in JasPer 2
An issue was discovered in JasPer 2.0.14. There is a NULL pointer dereference in the function jp2_decode in libjasper/jp2/jp2_dec.c, leading to a denial of service.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-19542 jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c [fedora-all]
bugzilla·2018-12-12·CVSS 6.5
CVE-2018-19542 [MEDIUM] CVE-2018-19542 jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c [fedora-all]
CVE-2018-19542 jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supp
Bugzilla
CVE-2018-19542 jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c
bugzilla·2018-12-12·CVSS 6.5
CVE-2018-19542 [MEDIUM] CVE-2018-19542 jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c
CVE-2018-19542 jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c
An issue was discovered in JasPer 2.0.14. There is a NULL pointer dereference in the function jp2_decode in libjasper/jp2/jp2_dec.c, leading to a denial of service.
References:
https://github.com/mdadams/jasper/issues/182
Discussion:
Created jasper tracking bugs for this issue:
Affects: fedora-all [bug 1658792]
Created mingw-jasper tracking bugs for this issue:
Affects: epel-7 [bug 1658794]
Affects: fedora-all [bug 1658793]
---
Not really a NULL ptr deref, but it can end up using garbage memory and the outcome can look like it is
Bugzilla
CVE-2018-19542 mingw-jasper: jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c [fedora-all]
bugzilla·2018-12-12·CVSS 6.5
CVE-2018-19542 [MEDIUM] CVE-2018-19542 mingw-jasper: jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c [fedora-all]
CVE-2018-19542 mingw-jasper: jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects
Bugzilla
CVE-2018-19542 mingw-jasper: jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c [epel-7]
bugzilla·2018-12-12·CVSS 6.5
CVE-2018-19542 [MEDIUM] CVE-2018-19542 mingw-jasper: jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c [epel-7]
CVE-2018-19542 mingw-jasper: jasper: invalid access in jp2_decode in libjasper/jp2/jp2_dec.c [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following t
http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00004.htmlhttps://github.com/mdadams/jasper/issues/182https://lists.debian.org/debian-lts-announce/2019/01/msg00003.htmlhttps://www.oracle.com/security-alerts/cpuapr2020.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-05/msg00004.htmlhttps://github.com/mdadams/jasper/issues/182https://lists.debian.org/debian-lts-announce/2019/01/msg00003.htmlhttps://www.oracle.com/security-alerts/cpuapr2020.html
2018-11-26
Published