Open grahamc opened 7 years ago
Master: unaffected 16.09: unaffected As both has version 2.0.12, which is after this CVE
we have jasper-2.0.10 not jasper-2.0.12
fwiw I've merged the .12 update, because they're usually worth updating to. This issue is still one.
The patches I madee are:
master: 6c17ad677c4970c87e8562574ea7e6fbf12b0813 release-16.09: 4368adb6ac631b3bdbb071e96dfc545c1f8f92e1 release-17.03: beab3073c9caec3e6b67558efc6111bb68c7a2ab
Here is a report from the oss-security mailing list for Vulnerability Roundup 27.
Skip to First Email
Instructions:
Identification
Identify if we have the software, in 16.09, 17.03, and unstable. Then determine if we are vulnerable, and make a comment with your findings. It can also be helpful to specify if you think there is a patch, or if it can be fixed via a general update.
Example:
IMPORTANT: If you believe there are possibly related issues, bring them up on the parent issue!
Patching
Start by commenting on this issue saying you're working on a patch. This way, we don't duplicate work.
If you open a pull request, tag this issue and the master issue for the roundup.
If you commit the patch directly to a branch, please leave a comment on this issue with the branch and the commit hash, example:
Skip to First Email
Upon Completion ...
Info
Triage Indicator:
Should the search term be changed from
jasper
? Suggest a new package search by commenting:Known CVEs: CVE-2016-10248
Skip to End
Thu, 20 Oct 2016 09:43:40 +0200 Agostino Sarubbo,
5184269.v1vKSl7Lqd@blackgate
Skip to End
Mon, 13 Mar 2017 11:31:33 +0100 Agostino Sarubbo,
2036100.Yz5vC6aIUd@blackgate
Skip to End