This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
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:
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 supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
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)
# low, medium, high, urgent (required)
# testing, stable
# Bug numbers: 1234,9876
# Description of your update
notes=Security fix for [PUT CVEs HERE]
# Enable request automation based on the stable/unstable karma thresholds
# Automatically close bugs when this marked as stable
# Suggest that users restart after update
Additionally, you may opt to use the bodhi web interface to submit updates:
While this is a bug and has been fixed  in bison-3.7.2 (already in rawhide), it is not a valid CVE:
I'm closing this as NOTABUG because this is associated with an invalid CVE-ID (one that has been rejected
as not having security implication).
Either way, it's fixed in rawhide via 3.7.2, so there is no necessary fix.
It is not worth fixing this in earlier versions of Fedora because a crash in bison because of
deliberately invalid input does not have runtime implications.
I used an incorrect CVE ID in my above comment, but the reasoning still stands.
Correct one is: https://nvd.nist.gov/vuln/detail/CVE-2020-24980