Easy Import - Failure "zip bomb detected"

Daniel Borkowi1
Mega Sage

Hi community,

today I tried to upload a filled template via easy import. I took the template generates by ServiceNow and copied all needed data from other Excel sheets.

When I try to upload this I got this error message: "error in loading headers from the xlsx data source: Zip bomb detected! The file would exceed the max. ratio of compressed file size to the size of the expanded data. This may indicate that the file is used to inflate memory usage and thus could pose a security risk. You can adjust this limit via ZipSecureFile.setMinInflateRatio() if you need to work with files which exceed this limit. Counter: 2457884, cis.counter: 24576, ratio: 0.009998844534567132Limits: MIN_INFLATE_RATIO: 0.01"

Did someone ever had same issues? What could be the root cause? The data I copied was plain text.

 

Greets,

Daniel

 

1 ACCEPTED SOLUTION

Daniel Borkowi1
Mega Sage

Hi all I guess that someone formatted the template as table. So a lot of cells was empty which was then zipped.

 

Thanks

Daniel

View solution in original post

10 REPLIES 10

Alberto Consonn
ServiceNow Employee
ServiceNow Employee

Hi Daniel,

When using Easy Import, there are some properties you need to pay attention to, such as max import row limits (glide.import_template.row_limit) and data type restrictions.

Please do a check of this in the sys_properties.list, try to increase the limit and test again.

Hope this will fix your issue!

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

Thanks you

Cheers
Alberto

 

Thanks for your support. But this issue isn't cause by such limits. The template only contains 10 rows. The Exception is raised by an JavaScript framework used by ServiceNow for uploads. But I don't understand why this could be happen.

Brad Tilton
ServiceNow Employee
ServiceNow Employee

How many records are you trying to import? 

It also looks like there was at some point an issue around exporting currency fields that would throw that error. Does your import have any currency fields associated? If so, could you remove that column and try the import and see if you continue to get the error?

Daniel Borkowi1
Mega Sage

No no currency. It's an import for Discovery IP Range and there are only 10 Test entries. I can't see any strange data constellation.