Skip to content
Fencer Vulns
high 8.8

CVE-2021-42072 json

An issue was discovered in Barrier before 2.4.0.

published 2021-11-08 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-29058

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

Summary

An issue was discovered in Barrier before 2.4.0. The barriers component (aka the server-side implementation of Barrier) does not sufficiently verify the identify of connecting clients. Clients can thus exploit weaknesses in the provided protocol to cause denial-of-service or stage further attacks that could lead to information leaks or integrity corruption.

Patch / fix

  • barrier_project barrier 2.4.0
  • barrier openSUSE Tumbleweed 2.4.0-1.1
  • barrier Package Hub 15 SP3, openSUSE Leap 15.3 2.4.0-bp153.2.3.1
  • barrier openSUSE Leap 15.2 2.4.0-lp152.3.6.1

opensuse advisories openSUSE-SU-2024:11633-1openSUSE-SU-2021:1595-1openSUSE-SU-2021:1498-1

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-2021-42072 updated cvss 8.8

barrier: server-side implementation does not sufficiently verify the identify of connecting clients

  • 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.65% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • openwall.com http://www.openwall.com/lists/oss-security/2021/11/02/4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Vulns 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.