kali834x opened a new pull request, #801:
URL: https://github.com/apache/commons-compress/pull/801

   snappycompressorinputstream.readliterallength reads the four-byte literal 
length with byteutils.fromlittleendian and casts it straight to int, so a 
length field of 0xffffffff narrows to -1 and, after the +1 the method adds, 
becomes a zero-length literal. fill only guards against a negative literal 
size, so the zero-length literal slips through, consumes no input and emits no 
output, and read() then recurses into itself once per element until a crafted 
run of them overflows the stack with a stackoverflowerror that escapes the 
declared ioexception. reading the four-byte value as an unsigned long and 
rejecting anything that can't fit a positive int before narrowing keeps the 
check at the point of the conversion; the two- and three-byte forms can't 
overflow so they're untouched. reachable directly and through 
framedsnappycompressorinputstream, which decodes each chunk with this class.
   
   - [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.
   - [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.
   


-- 
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