SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
PHP

PHP static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your PHP code

  • All rules 273
  • Vulnerability42
  • Bug51
  • Security Hotspot34
  • Code Smell146
 
Tags
    Impact
      Clean code attribute
        1. Server-side requests should not be vulnerable to traversing attacks

           Vulnerability
        2. Credentials should not be hard-coded

           Vulnerability
        3. Secret keys and salt values should be robust

           Vulnerability
        4. Applications should not create session cookies from untrusted input

           Vulnerability
        5. Reflection should not be vulnerable to injection attacks

           Vulnerability
        6. OS commands should not be vulnerable to argument injection attacks

           Vulnerability
        7. A new session should be created during user authentication

           Vulnerability
        8. Authorizations should be based on strong decisions

           Vulnerability
        9. Cipher algorithms should be robust

           Vulnerability
        10. Encryption algorithms should be used with secure mode and padding scheme

           Vulnerability
        11. Server hostnames should be verified during SSL/TLS connections

           Vulnerability
        12. Include expressions should not be vulnerable to injection attacks

           Vulnerability
        13. Dynamic code execution should not be vulnerable to injection attacks

           Vulnerability
        14. HTTP request redirections should not be open to forging attacks

           Vulnerability
        15. Logging should not be vulnerable to injection attacks

           Vulnerability
        16. Server-side requests should not be vulnerable to forging attacks

           Vulnerability
        17. Deserialization should not be vulnerable to injection attacks

           Vulnerability
        18. Endpoints should not be vulnerable to reflected cross-site scripting (XSS) attacks

           Vulnerability
        19. Server certificates should be verified during SSL/TLS connections

           Vulnerability
        20. LDAP connections should be authenticated

           Vulnerability
        21. Cryptographic keys should be robust

           Vulnerability
        22. Weak SSL/TLS protocols should not be used

           Vulnerability
        23. Database queries should not be vulnerable to injection attacks

           Vulnerability
        24. "file_uploads" should be disabled

           Vulnerability
        25. "enable_dl" should be disabled

           Vulnerability
        26. "session.use_trans_sid" should not be enabled

           Vulnerability
        27. "cgi.force_redirect" should be enabled

           Vulnerability
        28. "allow_url_fopen" and "allow_url_include" should be disabled

           Vulnerability
        29. "open_basedir" should limit file access

           Vulnerability
        30. Session-management cookies should not be persistent

           Vulnerability
        31. "sleep" should not be called

           Vulnerability
        32. XML parsers should not be vulnerable to XXE attacks

           Vulnerability
        33. Regular expressions should not be vulnerable to Denial of Service attacks

           Vulnerability
        34. Neither DES (Data Encryption Standard) nor DESede (3DES) should be used

           Vulnerability
        35. Cryptographic RSA algorithms should always incorporate OAEP (Optimal Asymmetric Encryption Padding)

           Vulnerability
        36. A secure password should be used when connecting to a database

           Vulnerability
        37. XPath expressions should not be vulnerable to injection attacks

           Vulnerability
        38. I/O function calls should not be vulnerable to path injection attacks

           Vulnerability
        39. LDAP queries should not be vulnerable to injection attacks

           Vulnerability
        40. OS commands should not be vulnerable to command injection attacks

           Vulnerability
        41. SHA-1 and Message-Digest hash algorithms should not be used in secure contexts

           Vulnerability
        42. Password hashing functions should use an unpredictable salt

           Vulnerability

        Server-side requests should not be vulnerable to traversing attacks

        intentionality - complete
        security
        Vulnerability
        • cwe
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        Path Traversal Server-Side Request Forgery is a sub-class of Server-Side Request Forgery (SSRF). In this type of attack, the attacker manipulates the path of the URL in the server-side request, rather than controlling the entire URL. This can lead to unauthorized access to endpoints or data by altering the request path.

        Path Traversal SSRF attacks are dangerous because they can exploit the server-side application’s ability to send requests to internal resources that are typically inaccessible to external attackers. By manipulating the path, attackers can potentially gain access to sensitive information or functionalities that should be protected.

        What is the potential impact?

        The impact of SSRF vulnerabilities can vary greatly depending on the context in which the user input is used.

        API Traversal

        In a path traversal SSRF attack, the attacker can manipulate the path of the server-side request to traverse through different endpoints of an API. This can lead to several potential impacts:

        Unauthorized access to API endpoints

        By manipulating the path of the server-side request, an attacker can potentially access API endpoints that are not intended to be publicly accessible. This could include endpoints that provide access to sensitive data or functionality. Unauthorized access to these endpoints could lead to data breaches or unauthorized actions being performed on the server.

        Manipulation of API responses

        If an attacker can manipulate the path of a server-side request to traverse to different API endpoints, they could potentially influence the responses that the server sends back. This could lead to incorrect or misleading data being returned, which could have a variety of impacts depending on the nature of the application and the data involved.

          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          10.7

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use