Out-of-bounds Write Vulnerability in cpio

cpio Updated 02 Oct 2025

Summary

19/02/2016
N/A
Yes i
Unrated
Not published

DSA-3483-1: cpio - security update. Affects cpio versions < 2.11+dfsg-0.1+deb7u2. Fixed in 2.11+dfsg-0.1+deb7u2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

cpio is a tool used for creating and extracting cpio archive files. It is commonly used in Linux distributions for packaging and distributing software. The tool allows users to create archives of files and directories, as well as extract files from existing archives. However, a vulnerability has been discovered in cpio that can lead to a denial of service (application crash) due to an out-of-bounds write.

Vulnerability Detail

The vulnerability in cpio is caused by an out-of-bounds write, which occurs when the tool attempts to write data beyond the bounds of a buffer. This can be exploited by an attacker to crash the application, potentially leading to a denial of service. The vulnerability has been assigned the CVE identifier CVE-2016-2037.

How To Fix

Minimum fixed version

2.11+dfsg-0.1+deb7u2

This is the first release that contains the fix.

sudo apt-get install --only-upgrade cpio

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading the cpio package to the fixed version.

Conclusion

The out-of-bounds write vulnerability in cpio can lead to a denial of service. It is recommended to upgrade the cpio package to the fixed version for your distribution to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for cpio →

Share this vulnerability

FAQ

cpio is a tool used for creating and extracting cpio archive files. It is commonly used in Linux distributions for packaging and distributing software.

The vulnerability can lead to a denial of service (application crash) by exploiting an out-of-bounds write in cpio.

To fix this vulnerability, you should upgrade the cpio package to the fixed version for your distribution.

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading the cpio package.

You can obtain the fixed packages from the official Debian repositories or through package management tools like apt-get.

Related vulnerabilities

Recent vulnerabilities recorded for cpio.

How To Fix

Minimum fixed version

2.11+dfsg-0.1+deb7u2

This is the first release that contains the fix.

sudo apt-get install --only-upgrade cpio

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback