Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Warn about / reject local file headers which have a data descriptor but don't use deflate compression #21

@NeRdTheNed

Description

@NeRdTheNed

Parsing just a local file header which uses a data descriptor is technically not reliable when it uses stored (uncompressed) data. A malicious actor could theoretically insert a local file header or data descriptor header at an arbitrary point to confuse parsing. Deflate compressed streams are self terminating, so they don't suffer from the same problem. If the size of an entry is only read from the central directory file header, this isn't a problem, but JVM zip parsing rejects such local file headers anyway.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions