VYPR

CWE-176

Improper Handling of Unicode Encoding

VariantDraft

Description

The product does not properly handle when an input contains Unicode encoding.

Hierarchy (View 1000)

Parents

Children

none

Related attack patterns (CAPEC)

CAPEC-71

CVEs mapped to this weakness (30)

page 2 of 2
  • CVE-2023-41889MedSep 15, 2023
    risk 0.34cvss 5.3epss 0.01

    SHIRASAGI is a Content Management System. Prior to version 1.18.0, SHIRASAGI is vulnerable to a Post-Unicode normalization issue. This happens when a logical validation or a security check is performed before a Unicode normalization. The Unicode character equivalent of a…

  • CVE-2026-59890MedJul 8, 2026
    risk 0.33cvss 6.1epss 0.00

    setuptools is a package that allows users to download, build, install, upgrade, and uninstall Python packages. Prior to 83.0.0, FileList applied MANIFEST.in exclude, global-exclude, recursive-exclude, and prune directives by matching compiled glob patterns against on-disk file…

  • CVE-2023-31169MedAug 31, 2023
    risk 0.31cvss 4.8epss 0.00

    An Improper Handling of Unicode Encoding vulnerability in the Schweitzer Engineering Laboratories SEL-5030 acSELerator QuickSet Software could allow an attacker to embed instructions that could be executed by an authorized device operator. See Instruction Manual Appendix A…

  • CVE-2023-52081MedDec 28, 2023
    risk 0.27cvss 5.3epss 0.01

    ffcss is a CLI interface to apply and configure Firefox CSS themes. Prior to 0.2.0, the function `lookupPreprocess()` is meant to apply some transformations to a string by disabling characters in the regex `[-_ .]`. However, due to the use of late Unicode normalization of type…

  • CVE-2020-8929MedOct 19, 2020
    risk 0.27cvss 5.3epss 0.00

    A mis-handling of invalid unicode characters in the Java implementation of Tink versions prior to 1.5 allows an attacker to change the ID part of a ciphertext, which result in the creation of a second ciphertext that can decrypt to the same plaintext. This can be a problem with…

  • CVE-2022-29812LowApr 28, 2022
    risk 0.15cvss 2.3epss 0.00

    In JetBrains IntelliJ IDEA before 2022.1 notification mechanisms about using Unicode directionality formatting characters were insufficient

  • CVE-2026-35375LowApr 22, 2026
    risk 0.14cvss 3.3epss 0.00

    A logic error in the split utility of uutils coreutils causes the corruption of output filenames when provided with non-UTF-8 prefix or suffix inputs. The implementation utilizes to_string_lossy() when constructing chunk filenames, which automatically rewrites invalid byte…

  • CVE-2026-35373LowApr 22, 2026
    risk 0.14cvss 3.3epss 0.00

    A logic error in the ln utility of uutils coreutils causes the program to reject source paths containing non-UTF-8 filename bytes when using target-directory forms (e.g., ln SOURCE... DIRECTORY). While GNU ln treats filenames as raw bytes and creates the links correctly, the…

  • CVE-2026-35346LowApr 22, 2026
    risk 0.14cvss 3.3epss 0.00

    The comm utility in uutils coreutils silently corrupts data by performing lossy UTF-8 conversion on all output lines. The implementation uses String::from_utf8_lossy(), which replaces invalid UTF-8 byte sequences with the Unicode replacement character (U+FFFD). This behavior…

  • CVE-2017-20190Mar 27, 2024
    risk 0.00cvss epss 0.00

    Some Microsoft technologies as used in Windows 8 through 11 allow a temporary client-side performance degradation during processing of multiple Unicode combining characters, aka a "Zalgo text" attack. NOTE: third parties dispute whether the computational cost of interpreting…