## Summary `RedisArrayAggregator` recently added `maxElements` and `maxNestedArrayDepth` limits to fix public Redis resource-exhaustion a

RedisArrayAggregator recently added maxElements and maxNestedArrayDepth limits to fix public Redis resource-exhaustion advisories. The limits are independent, but the allocator remains eager: every positive nested RESP array header creates new ArrayList<RedisMessage>(length) before any child element exists.

With the default constructor, an attacker can send nested array headers with length 1,000,000 until the default nesting limit of 1024 is reached. This can reserve up to 1,024,000,000 child slots from roughly 12 KB of RESP input. This is backing capacity, not logical list size: ArrayList(int) constructs an empty list with the specified initial capacity.

Current decodeRedisArrayHeader(...) checks the two limits independently:

 1if (header.length() > maxElements) {
 2    throw new CodecException("this codec doesn't support longer length than " + maxElements);
 3}
 4 
 5if (depths.size() >= maxNestedArrayDepth) {
 6    releaseAndClearDepths();
 7    throw new CodecException("max nested array depth exceeded: "  + maxNestedArrayDepth);
 8}
 9depths.push(new AggregateState((int) header.length()));

AggregateState i