gpac: 0.8.0 -> 1.0.0 addressing numerous CVEs #95546
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
Addresses:
CVE-2019-20159
CVE-2019-20160
CVE-2019-20161
CVE-2019-20162
CVE-2019-20163
CVE-2019-20164
CVE-2019-20165
CVE-2019-20166
CVE-2019-20167
CVE-2019-20168
CVE-2019-20169
CVE-2019-20170
CVE-2019-20171
CVE-2019-20208
CVE-2020-11558
CVE-2020-6630
CVE-2020-6631
of mixed severity but at least a couple of them look pretty serious.
For each of these vulnerabilities, the trail leads to a commit included in 1.0.0.
Hopefully we could get a maintainer (@bluescreen303 ? @mgdelacroix ?) to take a look at this because I don't really know how to test it. The executables behave in a very similar (odd) way to the binaries in the previous 0.8.0 package, anyway.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)