|Summary:||CVE-2020-12460 opendmarc: improper null termination in function opendmarc_xml_parse leads to heap-buffer overflow [fedora-all]|
|Product:||[Fedora] Fedora||Reporter:||Dhananjay Arunesh <darunesh>|
|Component:||opendmarc||Assignee:||Kevin Fenzi <kevin>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Target Milestone:||---||Keywords:||Security, SecurityTracking|
|Fixed In Version:||opendmarc-1.4.0-1.fc34||Doc Type:||No Doc Update|
|Doc Text:||Story Points:||---|
|Last Closed:||2021-05-08 01:33:41 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Dhananjay Arunesh 2020-07-30 05:46:47 UTC
Comment 1 Dhananjay Arunesh 2020-07-30 05:46:53 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=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1861991,1861992 # 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 Tomas Korbar 2021-02-22 08:28:43 UTC
Hi, unfortunately i do not have time to maintain Opendmarc. The package is now orphaned. If you are a maintainer then please consider taking it. Apologies.
Comment 3 Fedora Admin user for bugzilla script actions 2021-02-25 00:08:41 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 4 Fedora Program Management 2021-04-29 17:18:34 UTC
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 5 Fedora Update System 2021-04-29 20:46:14 UTC
FEDORA-2021-c1b846164e has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-c1b846164e
Comment 6 Fedora Update System 2021-04-30 01:43:03 UTC
FEDORA-2021-c1b846164e has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-c1b846164e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-c1b846164e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2021-05-08 01:33:41 UTC
FEDORA-2021-c1b846164e has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.