[COMPRESS-386] Consider adding sanity check to maxCodeSize in ZCompressorInputStream (original) (raw)

Log inSkip to main contentSkip to sidebar

• Dashboards

• Projects

• Issues

• Help

  • Jira Core help
  • Keyboard Shortcuts
  • About Jira
  • Jira Credits

• Log In

1. Commons Compress
2. COMPRESS-386

XMLWordPrintableJSON

Details

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: None
• Fix Version/s: 1.14
• Component/s: None

Description

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?

Attachments

Issue Links

relates to

COMPRESS-382 OutOfMemoryError from CompressorStreamFactory

• 
• Resolved

TIKA-1631 OutOfMemoryException in ZipContainerDetector

• 
• Resolved

Activity

People

Votes:

0 Vote for this issue

Watchers:

3 Start watching this issue

Dates

Created:

14/Apr/17 15:37

Updated:

25/Apr/17 18:46

Resolved:

25/Apr/17 18:46