Reino: Input Validation and Representation

Problemas de validação e representação da entrada são causados por metacaracteres, codificações alternativas e representações numéricas. Confiar na entrada resulta em problemas de segurança. Os problemas incluem: “Buffer Overflows”, ataques de “Cross-Site Scripting”, “SQL Injection”, entre outros.

Possible Variable Overwrite: Global Scope

Abstract

O programa invoca uma função que pode substituir as variáveis globais e pode abrir a porta para invasores.

Explanation

As funções que podem substituir as variáveis globais já inicializadas podem permitir que um invasor influencie a execução de código que depende das variáveis substituídas.
Exemplo 1: Se um invasor fornecer código mal-intencionado para str no segmento a seguir de código PHP, a chamada para mb_parse_str() poderá substituir todas as variáveis arbitrárias, incluindo first. Nesse caso, se um valor mal-intencionado que contém JavaScript sobrescrever first, o programa ficará vulnerável à criação de scripts entre sites.


<?php
    $first="User";
    ...
    $str =  $_SERVER['QUERY_STRING'];
    mb_parse_str($str);
    echo $first;
?>

References

[1] Standards Mapping - Common Weakness Enumeration CWE ID 473

[2] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-001310

[3] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data

[4] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-10 Information Input Validation (P1)

[5] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-10 Information Input Validation

[6] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.6

[7] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.6

[8] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.6

[9] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.6

[10] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4

[11] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 6.2.4

[12] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 4.2 - Critical Asset Protection

[13] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 4.2 - Critical Asset Protection, Control Objective B.3.1 - Terminal Software Attack Mitigation, Control Objective B.3.1.1 - Terminal Software Attack Mitigation

[14] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection, Control Objective B.3.1 - Terminal Software Attack Mitigation, Control Objective B.3.1.1 - Terminal Software Attack Mitigation, Control Objective C.3.2 - Web Software Attack Mitigation

[15] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002530 CAT II

[16] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002530 CAT II

desc.dataflow.php.possible_variable_overwrite_global