Debian has issued an advisory on March 20: https://www.debian.org/security/2018/dsa-4146 The issue was fixed upstream in 3.0.16.
We won't be fixing this, but I filed it so we would have a record of it.
Status: NEW => RESOLVEDResolution: (none) => OLD
Debian has issued an advisory for this for 3.0.x on March 22: https://www.debian.org/security/2018/dsa-4149