flink: 1.9.0 -> 1.11.1, addressing CVE-2020-1960 #95592
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
https://nvd.nist.gov/vuln/detail/CVE-2020-1960
This is mainly for the eyes of maintainer @mbode to check whether this works acceptably for them. It would be nice to get a bump of the mainline package to as recent a version as possible before 20.09 branches, because future vulnerabilities are unlikely to see releases for older versions.
Note that upstream's 1.5 branch actually has a fix for this CVE @ apache/flink@f9b4e0d, but with no release accompanying it and because this is a binary package, we don't have the possibility of using it as a patch. So it looks like our
flink_1_5
will have to remain vulnerable for the time being (this is why binary packages make me sad).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)