# CVE-2017-15364: ccsv Double Free vulnerability

> A double free vulnerability in the Ccsv library allows remote attackers to cause a denial of service via a crafted file.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Oct 2017
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-5gxp-c379-pj42

## What is CVE-2017-15364?

CVE-2017-15364 is a medium-severity use after free vulnerability in n/a, published on 15 Oct 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The foreach function in ext/ccsv.c in Ccsv 1.1.0 allows remote attackers to cause a denial of service (double free and application crash) or possibly have unspecified other impact via a crafted file. NOTE: This has been disputed and it is argued that this is not present in version 1.1.0.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2017-15364?

2 open source packages ship an affected version, including ccsv. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ccsv` | RubyGems | All versions to 1.1.0 | None |
| `ccsv` | RubyGems | All versions to 1.1.0 | None |

Products: Ccsv Project Ccsv.

## How do I fix CVE-2017-15364?

No fix has been published for CVE-2017-15364 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-15364 being exploited?

There is no known exploitation of CVE-2017-15364 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15364 and fix it if it is affected.

What it is: CVE-2017-15364 is a medium-severity use after free vulnerability in n/a, published on 15 Oct 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-15364 in the wild and no public exploit code.

Affected packages and fixed versions:
- ccsv (RubyGems): affected all versions up to 1.1.0; no fix listed
- ccsv (RubyGems): affected all versions up to 1.1.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-15364/ (Markdown: https://insights.sbomify.com/CVE-2017-15364/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-15364
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-15364
- OSV: https://osv.dev/vulnerability/CVE-2017-15364

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-15364/
Summaries are generated and may contain mistakes; the official description above is the record.