Vulnerability in schroot - security update (DLA-3075-1)

schroot Updated 02 Oct 2025

Summary

18/08/2022
N/A
Yes i
Unrated
Not published

DLA-3075-1: schroot - security update. Affects schroot versions < 1.6.10-6+deb10u1. Fixed in 1.6.10-6+deb10u1. 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

Schroot is a tool that allows users to execute commands in a chroot environment. It provides a secure way to isolate processes and restrict their access to the host system. Schroot is commonly used in Linux distributions to create and manage chroot environments for various purposes, such as testing software or running untrusted applications. However, a vulnerability has been discovered in schroot that could lead to a denial of service (DoS) attack on the schroot service for all users who can start a schroot session.

Vulnerability Detail

The vulnerability in schroot is related to permissive rules on chroot or session names. This allows an attacker to create chroots or sessions with invalid names, causing a DoS on the schroot service. The issue arises from insufficient validation of user input, which can be exploited to crash the schroot service and disrupt its functionality. It is important to note that existing chroots and sessions are checked during the upgrade process, and the upgrade is aborted if any future invalid name is detected.

How To Fix

Minimum fixed version

1.6.10-6+deb10u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade schroot

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

Workaround

There is no specific workaround mentioned for this vulnerability. However, users can check for problematic sessions and chroots before upgrading by running the following command:

schroot --list --all | LC_ALL=C grep -vE '^[a-z]+:[a-zA-Z0-9][a-zA-Z0-9_.-]*'

This command will list all sessions and chroots, excluding any with invalid names. If any problematic entries are found, the provided link in the vulnerability details can be referred to for instructions on resolving the situation.

Conclusion

In conclusion, the schroot package has been found to have a vulnerability that allows for a denial of service attack. To mitigate this vulnerability, it is recommended to upgrade the schroot package to version 1.6.10-6+deb10u1 or later. Users can also check for problematic sessions and chroots before upgrading using the provided command. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for schroot →

Share this vulnerability

FAQ

Schroot is a tool that allows users to execute commands in a chroot environment. It provides a secure way to isolate processes and restrict their access to the host system.

The vulnerability in schroot can be exploited to cause a denial of service (DoS) attack on the schroot service. This can disrupt the functionality of schroot for all users who can start a schroot session.

You can check if your system is affected by running the provided command: schroot --list --all | LC_ALL=C grep -vE '^[a-z]+:[a-zA-Z0-9][a-zA-Z0-9_.-]*'. If any problematic sessions or chroots are listed, your system may be vulnerable.

To fix this vulnerability, you need to upgrade the schroot package to version 1.6.10-6+deb10u1 or later. This can be done using the package manager of your Linux distribution.

There is no specific workaround mentioned for this vulnerability. However, you can follow the provided command to check for problematic sessions and chroots before upgrading.

Related vulnerabilities

Recent vulnerabilities recorded for schroot.

How To Fix

Minimum fixed version

1.6.10-6+deb10u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade schroot

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