Bug 2258403

Summary: TRIAGE CVE-2023-51257 mingw-jasper: <media-libs/jasper-4.1.2: Invalid memory write [fedora-all]
Product: [Fedora] Fedora Reporter: Rohit Keshri <rkeshri>
Component: mingw-jasperAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 39CC: manisandro, rjones
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mingw-jasper-3.0.6-5.fc39 mingw-jasper-3.0.6-5.fc38 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-01-24 01:28:59 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: 2258400    

Description Rohit Keshri 2024-01-15 05:56:20 UTC
More information about this security flaw is available in the following bug:

http://bugzilla.redhat.com/show_bug.cgi?id=2258400

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Comment 1 Rohit Keshri 2024-01-15 05:56:23 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

# low, medium, high, urgent (required)
severity=low

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2258400,2258403

# 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

Comment 2 Fedora Update System 2024-01-15 10:13:34 UTC
FEDORA-2024-b5b85798cd has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-b5b85798cd

Comment 3 Fedora Update System 2024-01-15 10:13:34 UTC
FEDORA-2024-f53b383648 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-f53b383648

Comment 4 Fedora Update System 2024-01-16 01:06:41 UTC
FEDORA-2024-b5b85798cd has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-b5b85798cd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-b5b85798cd

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2024-01-16 01:19:05 UTC
FEDORA-2024-f53b383648 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-f53b383648`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f53b383648

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-01-24 01:28:59 UTC
FEDORA-2024-f53b383648 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2024-01-24 01:32:49 UTC
FEDORA-2024-b5b85798cd has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.