Reino: API Abuse

Uma API é um contrato entre quem chama e o que se chama. As formas mais comuns de abuso de API ocorrem quando o responsável pela chamada não respeita sua parte do contrato. Por exemplo, se um programa não chama chdir() após chamar chroot(), ele viola o contrato que especifica como alterar o diretório raiz ativo de forma segura. Outro bom exemplo de abuso de biblioteca é esperar que o elemento chamado retorne informações confiáveis de DNS ao responsável pela chamada. Nesse caso, o responsável pela chamada abusa a API do elemento chamado ao fazer certas suposições sobre seu comportamento (isto é, que o valor de retorno pode ser usado para fins de autenticação). A outra parte também pode violar o contrato entre quem chama e o que se chama. Por exemplo, se um programador definir SecureRandom como subclasse e retornar um valor não aleatório, o contrato será violado.

Often Misused: File Upload

Abstract

Permitir que os usuários carreguem arquivos pode permitir que os invasores injetem conteúdo perigoso ou código mal-intencionado para execução no servidor.

Explanation


HttpPostedFile posted = FileUpload.PostedFile;

Mesmo que um programa armazene arquivos carregados em um diretório não acessível na Web, os invasores ainda podem ser capazes de se aproveitar da capacidade de introduzir conteúdo mal-intencionado no ambiente do servidor para preparar outros ataques. Se o programa for suscetível a vulnerabilidades de manipulação de caminho, injeção de comando ou inclusão de arquivos perigosos, um invasor poderá carregar um arquivo com conteúdo mal-intencionado e fazer com que este seja lido ou executado pelo programa ao explorar outra vulnerabilidade.

References

[1] Alla Bezroutchko Secure file upload in PHP web applications

[2] Standards Mapping - Common Weakness Enumeration CWE ID 434

[3] Standards Mapping - Common Weakness Enumeration Top 25 2019 [16] CWE ID 434

[4] Standards Mapping - Common Weakness Enumeration Top 25 2020 [15] CWE ID 434

[5] Standards Mapping - Common Weakness Enumeration Top 25 2021 [10] CWE ID 434

[6] Standards Mapping - Common Weakness Enumeration Top 25 2022 [10] CWE ID 434

[7] Standards Mapping - Common Weakness Enumeration Top 25 2023 [10] CWE ID 434

[8] Standards Mapping - Common Weakness Enumeration Top 25 2024 [10] CWE ID 434

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

[10] Standards Mapping - FIPS200 SI

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

[12] Standards Mapping - NIST Special Publication 800-53 Revision 4 SC-18 Mobile Code (P2)

[13] Standards Mapping - NIST Special Publication 800-53 Revision 5 SC-18 Mobile Code

[14] Standards Mapping - OWASP Application Security Verification Standard 4.0 12.2.1 File Integrity Requirements (L2 L3), 12.5.2 File Download Requirements (L1 L2 L3), 13.1.5 Generic Web Service Security Verification Requirements (L2 L3)

[15] Standards Mapping - OWASP Mobile 2014 M7 Client Side Injection

[16] Standards Mapping - OWASP Top 10 2004 A6 Injection Flaws

[17] Standards Mapping - OWASP Top 10 2007 A3 Malicious File Execution

[18] Standards Mapping - OWASP Top 10 2010 A1 Injection

[19] Standards Mapping - OWASP Top 10 2013 A1 Injection

[20] Standards Mapping - OWASP Top 10 2017 A1 Injection

[21] Standards Mapping - OWASP Top 10 2021 A04 Insecure Design

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.6

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.3.1.1, Requirement 6.5.3

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.1

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.1

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.1

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.1

[28] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.1

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

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

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

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

[33] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection, Control Objective C.3.4 - Web Software Attack Mitigation

[34] Standards Mapping - SANS Top 25 2010 Insecure Interaction - CWE ID 434

[35] Standards Mapping - SANS Top 25 2011 Insecure Interaction - CWE ID 434

[36] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3510 CAT I

[37] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3510 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3510 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3510 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3510 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3510 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3510 CAT I

[43] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-003300 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-003300 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-003300 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-003300 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-003300 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-003300 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-003300 CAT II

[50] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-003300 CAT II

[51] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-003300 CAT II

[52] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-003300 CAT II

[53] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-003300 CAT II

[54] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-003300 CAT II

[55] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-003300 CAT II

[56] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-003300 CAT II

[57] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-003300 CAT II

[58] Standards Mapping - Web Application Security Consortium Version 2.00 Improper Input Handling (WASC-20)

desc.semantic.dotnet.often_misused_file_upload

Abstract

Permitir que os usuários carreguem arquivos pode permitir aos invasores injetar conteúdo perigoso ou códigos mal-intencionados para serem executados no servidor.

Explanation


@Controller
public class MyFormController {
    ...
    @RequestMapping("/test")
    public String uploadFile (org.springframework.web.multipart.MultipartFile file) {
       ...
    }    ...
}