You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2017/04/14 15:42:41 UTC
[jira] [Updated] (COMPRESS-386) Consider adding sanity check to
maxCodeSize in ZCompressorInputStream
[ https://issues.apache.org/jira/browse/COMPRESS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Bodewig updated COMPRESS-386:
------------------------------------
Fix Version/s: 1.14
> Consider adding sanity check to maxCodeSize in ZCompressorInputStream
> ---------------------------------------------------------------------
>
> Key: COMPRESS-386
> URL: https://issues.apache.org/jira/browse/COMPRESS-386
> Project: Commons Compress
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Minor
>
> On TIKA-1631, several users pointed out that a bad value for the 4th byte of an apparently Z compressed file can lead to an OOM.
> If possible, it would be great to parameterize ZCompressorInputStream to set a threshold. Or, if this should be kept out of COMPRESS, is there some way that we could load a threshold-checking subclass of ZCompressorInputStream via the CompressorStreamFactory?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)