Uploaded image for project: 'Rules Repository'
  1. Rules Repository
  2. RSPEC-5443

Using publicly writable directories is security-sensitive

    XMLWordPrintable

    Details

    • Type: Security Hotspot Detection
    • Status: Active
    • Resolution: Unresolved
    • Message:
      Make sure publicly writable directories are used safely here.
    • Default Severity:
      Critical
    • Impact:
      High
    • Likelihood:
      Low
    • Default Quality Profiles:
      Sonar way
    • Covered Languages:
      C#, C, C++, Java, JavaScript, Objective-C, Python, VB.Net
    • Analysis Scope:
      Main Sources
    • CWE:
      CWE-377, CWE-379
    • OWASP:
      A5, A3

      Description

      Operating systems have global directories where any user has write access. Those folders are mostly used as temporary storage areas like /tmp in Linux based systems. An application manipulating files from these folders is exposed to race conditions on filenames: a malicious user can try to create a file with a predictable name before the application does. A successful attack can result in other files being accessed, modified, corrupted or deleted. This risk is even higher if the application runs with elevated permissions.

      In the past, it has led to the following vulnerabilities:

      This rule raises an issue whenever it detects a hard-coded path to a publicly writable directory like /tmp (see examples bellow). It also detects access to environment variables that point to publicly writable directories, e.g., TMP and TMPDIR.

      • /tmp
      • /var/tmp
      • /usr/tmp
      • /dev/shm
      • /dev/mqueue
      • /run/lock
      • /var/run/lock
      • /Library/Caches
      • /Users/Shared
      • /private/tmp
      • /private/var/tmp
      • \Windows\Temp
      • \Temp
      • \TMP

      Ask Yourself Whether

      • Files are read from or written into a publicly writable folder
      • The application creates files with predictable names into a publicly writable folder

      There is a risk if you answered yes to any of those questions.

      Recommended Secure Coding Practices

      • Use a dedicated sub-folder with tightly controlled permissions
      • Use secure-by-design APIs to create temporary files. Such API will make sure:
        • The generated filename is unpredictable
        • The file is readable and writable only by the creating user ID
        • The file descriptor is not inherited by child processes
        • The file will be destroyed as soon as it is closed

      See

        Attachments

          Issue Links

          1.
          Python RSPEC-5444 Language-Specification Active Unassigned
          2.
          C-Family RSPEC-6056 Language-Specification Active Unassigned
          3.
          Javascript RSPEC-6100 Language-Specification Active Unassigned
          4.
          Java RSPEC-6142 Language-Specification Active Unassigned
          5.
          C# RSPEC-6152 Language-Specification Active Unassigned
          6.
          VB.NET RSPEC-6162 Language-Specification Active Unassigned

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              pierre-loup.tristant Pierre-Loup Tristant
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: