CVE-2022-2553

The authfile directive in the booth config file is ignored, preventing use of authentication in communications from node to node. As a result, nodes that do not have the correct authentication key are not prevented from communicating with other nodes in the cluster.

Published: 2022-07-28 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-2553 is rated Moderate Risk (45.5/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.91%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-2553

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.67% 0.91% +0.24%
2 2026-04-19 0.51% 0.67% +0.16%
3 2026-04-06 — 0.51% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-2553

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 2.5 [email protected]

Weakness enumeration for CVE-2022-2553

OS Trackers for CVE-2022-2553

vendor priority summary link
debian not yet assigned CVE-2022-2553 not yet assigned priority: Debian including 1 source packages (booth), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-2553
redhat medium — https://access.redhat.com/security/cve/CVE-2022-2553
suse medium CVE-2022-2553 severity moderate: SUSE including 19 source package names (booth-1.0+20210519.bfb2f92-150400.3.3.1, booth-1.0+20220724.dce51f9-1.1, …), 23 product×package rows across 12 product lines (SUSE Liberty Linux 8, SUSE Liberty Linux 9, … (12 product lines)): Fixed 23. https://www.suse.com/security/cve/CVE-2022-2553/
ubuntu medium CVE-2022-2553 medium priority: Ubuntu including 1 source packages (booth), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 6, needs-triage 5, released 2. https://ubuntu.com/security/CVE-2022-2553

Affected software / configurations for CVE-2022-2553

Vendor Product Version Raw CPE
clusterlabs booth <= 1.0 cpe:2.3:a:clusterlabs:booth:*:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
fedoraproject fedora 35 cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
fedoraproject fedora 36 cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*

References for CVE-2022-2553

cvelogic Threat Intelligence