On 15/01/16 07:10, Steve Kemp wrote:
> Great. I have about twenty more files that crash the version of
> catdoc available to sid. I will wait to see your fix, and once posted
> I'll test the current samples against them, I expect that some of them are
> non-unique.
The new upstream
On Wed Jan 13, 2016 at 18:08:44 -0300, Martín Ferrari wrote:
> > When running under valgrind we see that an attempt is made to access
> > an invalid pointer:
>
> This is a known issue (#679877), it was fixed when I took over this
> package, and it has already reached testing.
Having the fixed
On 14/01/16 07:51, Steve Kemp wrote:
> On Wed Jan 13, 2016 at 18:08:44 -0300, Martín Ferrari wrote:
>
>>> When running under valgrind we see that an attempt is made to access
>>> an invalid pointer:
>>
>> This is a known issue (#679877), it was fixed when I took over this
>> package, and it has
> Fair enough. In any case, I am going to upload to backports as soon as
> the version in sid stabilises.
Great.
> Well, I think a DSA would be too much for a tool like this :) Specially
> since there has not been any PoC to show a real security issue.
I won't try to force it, but I'd
Package: catdoc
Version: 0.94.4-1.1
Severity: important
Tags: security
Dear Maintainer,
The attached word document will cause catdoc to crash when executed:
catdoc x.doc
When running under valgrind we see that an attempt is made to access
an invalid pointer:
==6875== Invalid read of
Hi Steve,
On 13/01/16 07:24, Steve Kemp wrote:
> The attached word document will cause catdoc to crash when executed:
>
> catdoc x.doc
>
> When running under valgrind we see that an attempt is made to access
> an invalid pointer:
This is a known issue (#679877), it was fixed when I took
6 matches
Mail list logo
