title: Security Hotspot using /tmp folder
body: <p>I'm using the <code>tmp</code> folder to store some files in runtime in my AWS NodeJS Javascript lambda.</p>
  <pre><code>const ROOT_DIR = '/tmp/'; // Lambda has /tmp/ folder up to 512MB
  const filePath = ROOT_DIR + 'myFile.csv';
      const csvWriter = createCsvWriter({
          path: filePath,
          header: headers,
      });
  
      await csvWriter.writeRecords(data);
  </code></pre>
  <p>SONAR is detecting a Security Hotspot</p>
  <blockquote>
  <p>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.</p>
  <p>In the past, it has led to the following vulnerabilities:</p>
  <p>CVE-2012-2451 CVE-2015-1838 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.</p>
  <p>/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</p>
  </blockquote>
  <p>What would be the correct solution to still use the /tmp folder without this Security Hotspot?</p>