# CVE-2017-14952: Use after free in n/a

> Remote attackers can execute arbitrary code via a crafted string due to a double free vulnerability in the ICU library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-14952, GHSA-35gv-g55r-237w, MGASA-2017-0411, UBUNTU-CVE-2017-14952, USN-3458-1

## What is CVE-2017-14952?

CVE-2017-14952 is a critical use after free vulnerability in n/a, published on 16 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Double free in i18n/zonemeta.cpp in International Components for Unicode (ICU) for C/C++ through 59.1 allows remote attackers to execute arbitrary code via a crafted string, aka a "redundant UVector entry clean up function call" issue.

Weakness: CWE-415 (Double Free)

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

It affects 1 product.


Products: Icu-Project International Components for Unicode.

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

Upgrade to a fixed version.

## Is CVE-2017-14952 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18928](https://insights.sbomify.com/CVE-2018-18928/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-17484](https://insights.sbomify.com/CVE-2017-17484/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-9911](https://insights.sbomify.com/CVE-2014-9911/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-7415](https://insights.sbomify.com/CVE-2016-7415/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-6293](https://insights.sbomify.com/CVE-2016-6293/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14952 is a critical use after free vulnerability in n/a, published on 16 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14952 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-14952/ (Markdown: https://insights.sbomify.com/CVE-2017-14952/index.md)
```

## Sources

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

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