More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2290901 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.
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=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2290901,2290919 # 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
I keep complaining about avoidable false positives with these security bug-filing scripts. Filing CVE bugs is a useful service, but only if the signal-to-noise ratio is reasonable. The spec file for this package already deletes all package-lock.json files in the JavaScript examples as a workaround for the bug-filing scripts, because otherwise I get a flood of CVE’s about vulnerable versions NPM libraries that are mentioned there – even though these libraries are not included in the RPM package, and would never even be downloaded unless someone went and manually built the examples. Now these scripts are apparently also digging through package.json files in the examples and filing bugs about those too. If nothing else, it would be great if the bug-filing scripts could at least ignore package.json/package-lock.json files that are marked %doc? I’m going to just stop packaging the examples. Hopefully that will be enough to prevent these bug reports in the future.