rootvector2 opened a new pull request, #406:
URL: https://github.com/apache/commons-beanutils/pull/406

   `LongLocaleConverter.parse` narrows the parsed number with 
`result.longValue()` and never range-checks it, so a value beyond `long` range 
like `99999999999999999999` is silently clamped to `Long.MAX_VALUE` instead of 
rejected: `DecimalFormat` returns it as a `Double` (the converter does not set 
`parseBigDecimal`) and `Double.longValue()` saturates. The sibling narrowing 
locale converters `IntegerLocaleConverter`, `ByteLocaleConverter`, 
`ShortLocaleConverter` and `FloatLocaleConverter` already reject out-of-range 
input, so `LongLocaleConverter` gets the same bounds check before narrowing. 
Found while auditing the locale converter family against those sibling checks.
   
   - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
   - [ ] Read the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) if you use 
Artificial Intelligence (AI).
   - [ ] I used AI to create any part of, or all of, this pull request. Which 
AI tool was used to create this pull request, and to what extent did it 
contribute?
   - [x] Run a successful build using the default 
[Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command 
line by itself.
   - [x] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied. This may not always be possible, 
but it is a best practice.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body. Note that a maintainer may squash commits during the merge process.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to