Report: Full Disclosure mailing list, 2026-10-29,
https://seclists.org/fulldisclosure/2026/Nov/0
Disposition: KNOWN-NON-FINDING (THREAT_MODEL.md section 11a, resource
consumption within a configured bound)
TLP:CLEAR

In short

This is not a vulnerability in Apache Struts. The body is bounded by
struts.json.maxLength, the parse is linear in that bound, and a single map
entry is retained.

What the report describes

StrutsJSONReader checks struts.json.maxElements against the size of the map
being built. A JSON object that repeats the same key never grows the map,
so every pair is parsed and hashed while the limit is never reached. The
post measured about 262,000 pairs in a 2 MB body.

What the framework does with that input

- The JSON interceptor is not in any default stack; an application enables
it.
- The body is rejected as soon as it exceeds struts.json.maxLength (2 MB by
default) while being read (JSONUtil.deserializeInput).
- Within the body, the object and array readers both compare the element
limit with the collection's size (StrutsJSONReader), which the
documentation defines as the number of elements in a single JSON array or
object.
- The project reproduced the shape: a 2 MB body of repeated keys parses in
under 20 milliseconds, retains a one-element map and uses a few megabytes
of transient heap, far below what the same 2 MB can cost as nested arrays
(see the notice on the posts of 2026-10-27 and 2026-10-28).

Why this is not a vulnerability

The work and the memory are both proportionate to a bounded input
(THREAT_MODEL.md section 8.7). Which keys the element limit counts is a
documentation question, and the documentation says it counts elements of
the resulting object. Section 11a lists this kind of bounded consumption as
a known non-finding.

What the project is doing

No change to the framework follows from this report. Counting parsed pairs
instead of distinct keys is being considered as hardening.

What users should do

Nothing is required. struts.json.maxLength remains the control over
per-request cost.

References

- https://struts.apache.org/plugins/json/ (Deserialization limits)
- https://github.com/apache/struts/blob/main/THREAT_MODEL.md (sections 8.7,
11a, 13)
- https://github.com/apache/struts/blob/main/SECURITY.md

New evidence goes to [email protected]; questions about this
notice go to this list.

on behalf of the Apache Struts PMC
Ɓukasz

Reply via email to