VYPR

CWE-838

Inappropriate Encoding for Output Context

BaseIncomplete

Description

The product uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component.

Hierarchy (View 1000)

Parents

Children

none

Related attack patterns (CAPEC)

CAPEC-468

CVEs mapped to this weakness (5)

  • CVE-2024-34006May 31, 2024
    risk 0.00cvss epss 0.00

    The site log report required additional encoding of event descriptions to ensure any HTML in the content is displayed in plaintext instead of being rendered.

  • CVE-2022-43407Oct 19, 2022
    risk 0.00cvss epss 0.00

    Jenkins Pipeline: Input Step Plugin 451.vf1a_a_4f405289 and earlier does not restrict or sanitize the optionally specified ID of the 'input' step, which is used for the URLs that process user interactions for the given 'input' step (proceed or abort) and is not correctly…

  • CVE-2022-43408Oct 19, 2022
    risk 0.00cvss epss 0.00

    Jenkins Pipeline: Stage View Plugin 2.26 and earlier does not correctly encode the ID of 'input' steps when using it to generate URLs to proceed or abort Pipeline builds, allowing attackers able to configure Pipelines to specify 'input' step IDs resulting in URLs that would…

  • CVE-2019-18981Nov 15, 2019
    risk 0.00cvss epss 0.01

    Pimcore before 6.2.2 lacks an Access Denied outcome for a certain scenario of an incorrect recipient ID of a notification.

  • CVE-2018-9862HigApr 9, 2018
    risk 0.00cvss 7.8epss 0.00

    util.c in runV 1.0.0 for Docker mishandles a numeric username, which allows attackers to obtain root access by leveraging the presence of an initial numeric value on an /etc/passwd line, and then issuing a "docker exec" command with that value in the -u argument, a similar issue…