GNU bug report logs -
#19565
Emacs vulnerable to endless-data attack (minor)
Previous Next
Full log
View this message in rfc822 format
Eli Zaretskii <eliz <at> gnu.org> writes:
>> I think this affects more than just package.el. AFAICT, anywhere we
>> use the url library, an endless data attack can get Emacs to fill up
>> all available memory (wasting also bandwidth resources, of course).
>
> At which point the system will kill the Emacs process. Why is that a
> problem we need to work, given that we already have at least some
> protection against stack overflows and running out of memory?
It's not something we have to do, but it would be nice to have some
protection against this.
>> For example, a new keyword argument :max-size, which would make it
>> stop after having reached that many bytes.
>
> The Gnu Coding Standards frown on having arbitrary limits in a
> program. So this could only work if we had some reasonable way of
> computing a limit that is not arbitrary.
I think it would perhaps make some sense to warn (or query) the user if
you get more data than `large-file-warning-threshold'. I think it would
be pretty trivial to implement -- at least in the new with-fetched-url
interface, which I think is where this pretty theoretical problem is
least theoretical, perhaps?
On the other hand, I could see that in some ways it would be easier to
implement in wait_reading_process_output: We could just maintain a byte
counter in the process objects (if we don't do that already) and have a
callback we call if that counter grows larger than
`large-file-warning-threshold'.
That way Emacs wouldn't be open to flooding from, say, rogue SMTP
servers, either.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
This bug report was last modified 5 years and 252 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.