Bug 1539848
Summary: | CVE-2018-6191 mupdf: Interger overflow in js_strtod function in jsdtoa.c [fedora-all] | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pedro Sampaio <psampaio> |
Component: | mupdf | Assignee: | Michael J Gruber <mjg> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 27 | CC: | mjg |
Target Milestone: | --- | Keywords: | Security, SecurityTracking |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Release Note | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-01-29 18:35:44 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: | |||
Bug Blocks: | 1539847 |
Description
Pedro Sampaio
2018-01-29 18:00:10 UTC
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1539847,1539848 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new Again, this automatically created bug against mupdf does not contain the necessary information. Instead, the automatically created bug against "vulnerability" that this one blocks - and that I'm not supposed to touch, I've been told - does contain the information over there that I'm supposed to act upon and discuss here. This misdesigned. Again, the template here is wrong: This bug blocks the other one, the other one is the tracker, not vice versa. You don't discuss in a tracker bug. In addition, the upstream bug is not against mupdf but mujs which we don't even build (nor build against, see `rm -rf thirdparty`) in spec. |