GHSA-634p-93h9-92vh
MEDIUMghas-to-csv vulnerable to Improper Neutralization of Formula Elements in a CSV File
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
some-natalie/ghas-to-csvReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects GitHub Actions packages — download data is not available via public APIs for these ecosystems.
Description
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
defusedcsvhere
For more information
If you have any questions or comments about this advisory:
- Open an issue in this repository here
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦GitHub Actions | some-natalie/ghas-to-csv | all versions | 1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for some-natalie/ghas-to-csv. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update some-natalie/ghas-to-csv to 1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-634p-93h9-92vh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-634p-93h9-92vh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-634p-93h9-92vh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-634p-93h9-92vh in your dependencies?
O3 detects GHSA-634p-93h9-92vh across GitHub Actions dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.