Bug#864859: marked as done (jython: CVE-2016-4000: Unsafe deserialization leads to code execution)

2017-07-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jul 2017 18:33:20 + with message-id and subject line Bug#864859: fixed in jython 2.5.3-16+deb9u1 has caused the Debian Bug report #864859, regarding jython: CVE-2016-4000: Unsafe deserialization leads to code execution to be marked as done. This means that you claim

Bug#864859: marked as done (jython: CVE-2016-4000: Unsafe deserialization leads to code execution)

2017-06-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Jun 2017 21:18:27 + with message-id and subject line Bug#864859: fixed in jython 2.5.3-3+deb8u1 has caused the Debian Bug report #864859, regarding jython: CVE-2016-4000: Unsafe deserialization leads to code execution to be marked as done. This means that you claim

Bug#864859: marked as done (jython: CVE-2016-4000: Unsafe deserialization leads to code execution)

2017-06-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Jun 2017 21:04:57 + with message-id and subject line Bug#864859: fixed in jython 2.5.3-17 has caused the Debian Bug report #864859, regarding jython: CVE-2016-4000: Unsafe deserialization leads to code execution to be marked as done. This means that you claim that t