HTTP: Non-Encoded Binary Detected In URLEncode Content Type
This signature detects for conformance to RFC 1738 that specifies the handling of URL-Encoded data. If a client specifies a Content-Type of URL-Encoded, any binary data - including Unicode characters - should be properly encoded. This signature will trigger on both malicious abuse of this standard as well as mis-configured clients and web applications.
mx-19.3
vmx-19.3
vsrx-19.2
srx-19.3
srx-branch-19.3
vsrx3bsd-19.2
srx-19.4
vsrx3bsd-19.4
srx-branch-19.4
vsrx-19.4
vmx-19.4
mx-19.4
srxevo-25.4
vsrx-26.2
srx-26.2
srx-branch-26.2
vsrx3bsd-26.2
mx-12.3
srx-12.3
srx-branch-12.3
vsrx-12.3