Impact

This GitHub Action creates a CSV file without sanitizing the output of the APIs. If an alert is dismissed or any other custom field contains executable code / formulas, it might be run when an endpoint opens that CSV file in a spreadsheet program. The data flow looks like this 👇🏻

graph TD
    A(Repository) -->|developer dismissal, other data input| B(GitHub Advanced Security data)
    B -->|ghas-to-csv| C(CSV file)
    C -->|spreadsheet program| D(endpoint executes potentially malicious code)

Patches

Please use version v1 or later. That tag moves from using csv to defusedcsv to mitigate this problem.

Workarounds

There is no workaround. Please upgrade to using the latest tag, v1 (or later).

References

• CWE-1236 information from MITRE
• CSV injection information from OWASP
• CodeQL query for CWE-1236 in Python here
• PyPI site for defusedcsv here

For more information

If you have any questions or comments about this advisory:

• Open an issue in this repository here

References

• GHSA-634p-93h9-92vh
• advanced-security/ghas-to-csv#19
• advanced-security/ghas-to-csv#20
• advanced-security/ghas-to-csv@d0b5219
• https://nvd.nist.gov/vuln/detail/CVE-2022-39217