Skip to content

bug(XOR Checksum): a float or negative block size cause an uncaught RangeError #2537

@HackingRepo

Description

@HackingRepo

Drag Xor Checksum and then set blocksize to a float number 1.1 or a negative on -1

as you can see an uncaught RangError look like that

XOR Checksum - RangeError in https://gchq.github.io/CyberChef/modules/Crypto.js on line 2.<br><br>Message: invalid array length

the problem again simple improper input validation and persits a lot

Direct Test Links:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions