Report: Full Disclosure mailing list, 2026-10-29,
https://seclists.org/fulldisclosure/2026/Nov/4
Disposition: VALID-HARDENING, conversion-correctness bug WW-5854
(THREAT_MODEL.md section 13)
TLP:CLEAR

In short

The report is correct: a grouped number outside the target type's range,
such as 2,147,483,648 for an Integer under an English locale, is converted
to the wrapped value instead of being rejected. It is a conversion bug, not
a vulnerability: the resulting value is one the client could have submitted
directly, and range validation is the application's validator.

What the report describes

NumberConverter parses grouped input with a locale-aware NumberFormat and
then re-parses the original grouped string with BigInteger to check the
range. BigInteger does not accept the grouping separator, the exception is
caught and the range check returns true. DefaultTypeConverter then narrows
the parsed long with a cast, which wraps. Ungrouped out-of-range input is
rejected correctly.

What the framework does with that input

- A request parameter bound to a boxed Byte, Short, Integer or Long
property goes through the parameters interceptor and the type converter;
the framework performs the conversion (NumberConverter.convertValue,
isInRange, DefaultTypeConverter.convertValue). The project reproduced the
wrap for Integer, Short and Byte and a saturation to Long.MAX_VALUE for
Long; ungrouped values and primitive targets were rejected.
- No documented range control is involved; the type conversion
documentation does not promise overflow detection.

Why this is not a vulnerability

A conversion that yields a value inside the type's range gives the client
nothing it could not submit as a plain number. The security properties the
framework defends (THREAT_MODEL.md section 8) do not include numeric
fidelity, and business-rule range checks belong to the application's
validators (section 9).

What the project is doing

WW-5854 fixes the range check to compare the parsed number with the type's
bounds, so out-of-range grouped input raises a conversion error like
ungrouped input does.

What users should do

Nothing is required. Applications that rely on a numeric range should
declare it with the range validators (for example the int range validator),
which validate the converted value.

References

- https://issues.apache.org/jira/browse/WW-5854
- https://struts.apache.org/core-developers/type-conversion.html
- https://struts.apache.org/core-developers/validation.html
- https://github.com/apache/struts/blob/main/THREAT_MODEL.md (sections 8,
9, 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