What is CVE-2022-39217?

CVE-2022-39217 is a medium-severity security vulnerability in some-natalie/ghas-to-csv (actions), affecting versions < 1. It is fixed in 1.

How severe is CVE-2022-39217?

CVE-2022-39217 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of some-natalie/ghas-to-csv are affected by CVE-2022-39217?

some-natalie/ghas-to-csv (actions) versions < 1 is affected.

Is there a fix for CVE-2022-39217?

Yes. CVE-2022-39217 is fixed in 1. Upgrade to this version or later.

Is CVE-2022-39217 exploitable, and should I be worried?

Whether CVE-2022-39217 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-39217 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-39217?

Upgrade some-natalie/ghas-to-csv to 1 or later.

CVE-2022-39217 in some-natalie/ghas-to-csv

Q: How severe is CVE-2022-39217?

CVE-2022-39217 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of some-natalie/ghas-to-csv are affected by CVE-2022-39217?

some-natalie/ghas-to-csv (actions) versions < 1 is affected.

Q: Is there a fix for CVE-2022-39217?

Yes. CVE-2022-39217 is fixed in 1. Upgrade to this version or later.

Q: Is CVE-2022-39217 exploitable, and should I be worried?

Whether CVE-2022-39217 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-39217 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-39217?

Upgrade some-natalie/ghas-to-csv to 1 or later.

Summary

ghas-to-csv vulnerable to Improper Neutralization of Formula Elements in a CSV File

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

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)

CVE-2022-39217 has a CVSS score of 5.8 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1); upgrading removes the vulnerable code path.

Affected versions

some-natalie/ghas-to-csv (< 1)

Security releases

some-natalie/ghas-to-csv → 1 (actions)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2022-39217? CVE-2022-39217 is a medium-severity security vulnerability in some-natalie/ghas-to-csv (actions), affecting versions < 1. It is fixed in 1.
How severe is CVE-2022-39217? CVE-2022-39217 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of some-natalie/ghas-to-csv are affected by CVE-2022-39217? some-natalie/ghas-to-csv (actions) versions < 1 is affected.
Is there a fix for CVE-2022-39217? Yes. CVE-2022-39217 is fixed in 1. Upgrade to this version or later.
Is CVE-2022-39217 exploitable, and should I be worried? Whether CVE-2022-39217 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-39217 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-39217? Upgrade some-natalie/ghas-to-csv to 1 or later.