angler-fishThe Vulnerability History Project

journald: set a limit on the number of fields (1k)

      We allocate a iovec entry for each field, so with many short entries,
our memory usage and processing time can be large, even with a relatively
small message size. Let's refuse overly long entries.

CVE-2018-16865
https://bugzilla.redhat.com/show_bug.cgi?id=1653861

What from I can see, the problem is not from an alloca, despite what the CVE
description says, but from the attack multiplication that comes from creating
many very small iovecs: (void* + size_t) for each three bytes of input message.
    
commit 052c57f132f04a3cf4148f87561618da1a6908b4
-5
-3
expand_less