I'm working on the fixes today. This should result in two distinct fixes, potentially each getting its own CVE (will leave that up to the security team).
We will be fixing this by issuing a new upstream security release, most likely 2.0.2.
Will update once I have the fixes.
I'm working on the fixes today. This should result in two distinct fixes, potentially each getting its own CVE (will leave that up to the security team).
We will be fixing this by issuing a new upstream security release, most likely 2.0.2.
Will update once I have the fixes.