kali834x opened a new pull request, #782: URL: https://github.com/apache/commons-compress/pull/782
**Negative band counts reach array allocation in the Pack200 decoder** The array-count overloads of `decodeBandInt`, `parseFlags` and `parseReferences` size each sub-array straight from `counts[i]` after only an upper-bound check, but count bands are decoded with signed codecs like `DELTA5`, so a crafted archive can make an element negative and turn `new int[counts[i]]` (and its `long[]`/`String[]` siblings) into a `NegativeArraySizeException` that escapes the declared `Pack200Exception` contract. The scalar `decodeBandInt(..., int)` overload already rejects `count < 0`, so this applies the same guard in the three siblings and a corrupt band surfaces as a normal `Pack200Exception`; the added `BandSetTest` case covers all three. - [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]
