Skip to content
Fencer Intel
medium 4.3

CVE-2022-2787 json

stricter rules on chroot names

published 4y ago modified 4mo ago also EUVD-2022-35028

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

Schroot before 1.6.13 had too permissive rules on chroot or session names, allowing a denial of service on the schroot service for all users that may start a schroot session.

Patch / fix

  • Debian schroot 1.6.13
  • schroot Debian 14, Debian 13, Debian 12 1.6.12-2

debian advisories DEBIAN-CVE-2022-2787

  • schroot Ubuntu 18.04 LTS 1.6.10-4ubuntu0.1
  • schroot Ubuntu 20.04 LTS 1.6.10-9ubuntu0.1
  • schroot Ubuntu 22.04 LTS 1.6.10-12ubuntu3.1
  • schroot Ubuntu Pro 16.04 LTS 1.6.10-1ubuntu3+esm1

ubuntu advisories UBUNTU-CVE-2022-2787

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-2787 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-2787 updated cvss 5.5

schroot: denial of service in schroot

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Affected products

  • Debian schroot

Classification

Weakness
  • CWE-281 Improper Preservation of Permissions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.