character-encoding-injection

Emoji-based SQL injection is prevented by replacing string concatenation with parameterized queries and enforcing byte-length validation. This skill audits source code to identify dangerous concatenation patterns and improper length checks that allow multi-byte characters to bypass input filters.

Unicode normalization bypasses input validation when applications process user-supplied text without canonicalizing multi-byte characters. This skill detects improper string truncation and normalization logic, providing actionable guidance to enforce secure coding practices against filter evasion.

Fix invalid UTF-8 sequences from string truncation by replacing character-count validation with byte-length checks. This skill identifies code where length-restricted fields incorrectly truncate multi-byte characters, guiding you to implement secure byte-length validation.

Auditing code for character encoding vulnerabilities involves scanning source directories for SQL concatenation patterns and character-length validation bugs. This skill identifies these security flaws and enforces secure coding practices by mandating parameterized queries and proper Unicode normalization.

Yes, this security audit targets web applications and backend services that process user-supplied text through concatenation or length-restricted fields. It identifies and mitigates character encoding vulnerabilities including emoji-based SQL injection and Unicode normalization bypasses.

Use byte-length validation instead of character-count checks whenever processing multi-byte Unicode characters or emojis in length-restricted fields. This skill helps identify code susceptible to memory corruption and filter evasion caused by improper character-count validation logic.