# CVE-2010-0624: Memory corruption in n/a

> Remote rmt servers can trigger a heap buffer overflow in GNU tar/cpio clients, potentially allowing arbitrary code execution or 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:** 12 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-0624, GHSA-27jj-5xgw-m6qw, RHSA-2010:0142, RHSA-2010:0143

## What is CVE-2010-0624?

CVE-2010-0624 is a medium-severity memory corruption vulnerability in n/a, published on 12 Mar 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in the rmt_read__ function in lib/rtapelib.c in the rmt client functionality in GNU tar before 1.23 and GNU cpio before 2.11 allows remote rmt servers to cause a denial of service (memory corruption) or possibly execute arbitrary code by sending more data than was requested, related to archive filenames that contain a : (colon) character.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2010-0624?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tar` | Red Hat:enterprise_linux:3::as | All versions | 0:1.13.25-16.RHEL3 |
| `tar-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.13.25-16.RHEL3 |
| `tar` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.13.25-16.RHEL3 |
| `tar-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.13.25-16.RHEL3 |
| `tar` | Red Hat:enterprise_linux:3::es | All versions | 0:1.13.25-16.RHEL3 |
| `tar-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.13.25-16.RHEL3 |
| `tar` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.13.25-16.RHEL3 |
| `tar-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.13.25-16.RHEL3 |
| `cpio` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5-16.el4_8.1 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5-16.el4_8.1 |
| `cpio` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5-16.el4_8.1 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5-16.el4_8.1 |
| `cpio` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5-16.el4_8.1 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5-16.el4_8.1 |
| `cpio` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.5-16.el4_8.1 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.5-16.el4_8.1 |

Products: Gnu Cpio, Gnu Tar.

## How do I fix CVE-2010-0624?

Upgrade to a fixed version.

## Is CVE-2010-0624 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-38185](https://insights.sbomify.com/CVE-2021-38185/): Integer overflow in n/a (high 7.8)
- [CVE-2010-4226](https://insights.sbomify.com/CVE-2010-4226/): Path traversal in n/a (high 7.2)
- [CVE-2019-14866](https://insights.sbomify.com/CVE-2019-14866/): Path traversal in cpio (medium 6.7)
- [CVE-2023-7216](https://insights.sbomify.com/CVE-2023-7216/): Cpio: extraction allows symlinks which enables remote command execution (medium 5.3)
- [CVE-2023-7207](https://insights.sbomify.com/CVE-2023-7207/): Path traversal in Debian cpio (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0624 and fix it if it is affected.

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

## Sources

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

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