# CVE-2007-4770: Memory corruption in n/a

> Out-of-bounds memory access in ICU library regex processing allows attackers to execute code or cause denial of service.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-4770, GHSA-3hvj-9j8h-vgr2

## What is CVE-2007-4770?

CVE-2007-4770 is a medium-severity memory corruption vulnerability in n/a, published on 28 Jan 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libicu in International Components for Unicode (ICU) 3.8.1 and earlier attempts to process backreferences to the nonexistent capture group zero (aka \0), which might allow context-dependent attackers to read from, or write to, out-of-bounds memory locations, related to corruption of REStackFrames.

Weakness: CWE-399

## Which versions are affected by CVE-2007-4770?

It affects 1 product.


Products: Icu-Project International Components for Unicode.

## How do I fix CVE-2007-4770?

Upgrade to a fixed version.

## Is CVE-2007-4770 being exploited?

There is no known exploitation of CVE-2007-4770 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-2017-14952](https://insights.sbomify.com/CVE-2017-14952/): Use after free 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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4770 and fix it if it is affected.

What it is: CVE-2007-4770 is a medium-severity memory corruption vulnerability in n/a, published on 28 Jan 2008. 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-2007-4770 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-2007-4770/ (Markdown: https://insights.sbomify.com/CVE-2007-4770/index.md)
```

## Sources

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

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