Skip to main content

Leading Single Code Point Emojis

This Fuzzer has 2 flavours depending on the --edgeSpacesStrategy.

Leading Single Code Point Emojis In Fields TRIM_AND_VALIDATE

ItemDescription
Full Fuzzer NameLeadingSingleCodePointEmojisInFieldsTrimValidateFuzzer
Log KeyLSCPEIF
DescriptionThis fuzzer prefixes fields with single-codepoint emojis. The expectation is that APIs will sanitize the input values, thus removing emojis and handle the request as a happy path.
Enabled by default?No. You need to supply --includeEmojis argument
Target field typesAll
Expected result when fuzzed field is required2XX
Expected result when fuzzed field is optional2XX
Expected result when fuzzed value is not matching field pattern2XX
Fuzzing logicIteratively prefixes fields with single-codepoint emojis: 👾
Conditions when this fuzzer will be skippedWhen field is a discriminator
HTTP methods that will be skippedNone
ReportingReports error if: 1. response code is 404; 2. response code is documented, but not expected; 3. any unexpected exception.

Reports warn if: 1. response code is expected and documented, but not matches response schema; 2. response code is expected, but not documented; 3. response code is 501.

Reports success if: 1. response code is expected, documented and matches response schema.

Leading Control Characters In Fields VALIDATE_AND_TRIM

ItemDescription
Full Fuzzer NameLeadingSingleCodePointEmojisInFieldsTrimValidateFuzzer
Log KeyLSCPEIF
DescriptionThis fuzzer prefixes fields with single-codepoint emojis. As the sanitization is assumed post-validation, the expectation is that APIs reject the request as invalid.
Enabled by default?No. You need to supply --includeEmojis argument
Target field typesAll
Expected result when fuzzed field is required4XX
Expected result when fuzzed field is optional4XX
Expected result when fuzzed value is not matching field pattern4XX
Fuzzing logicIteratively prefixes fields with single-codepoint emojis: 👾
Conditions when this fuzzer will be skippedWhen field is a discriminator
HTTP methods that will be skippedNone
ReportingReports error if: 1. response code is 404; 2. response code is documented, but not expected; 3. any unexpected exception.

Reports warn if: 1. response code is expected and documented, but not matches response schema; 2. response code is expected, but not documented; 3. response code is 501.

Reports success if: 1. response code is expected, documented and matches response schema.