CVE-2022-43755
CVE-2022-43755 is a high-severity vulnerability in Suse Rancher with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-331.
Key facts
- Severity: High (CVSS 3.x base score 7.1)
- EPSS exploit prediction: 2% (75th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-331
- Affected product: Suse Rancher
- Published:
- Last modified:
Description
A Insufficient Entropy vulnerability in SUSE Rancher allows attackers that gained knowledge of the cattle-token to continue abusing this even after the token was renewed. This issue affects: SUSE Rancher Rancher versions prior to 2.6.10; Rancher versions prior to 2.7.1.
Frequently asked questions
- What is CVE-2022-43755?
- A Insufficient Entropy vulnerability in SUSE Rancher allows attackers that gained knowledge of the cattle-token to continue abusing this even after the token was renewed. This issue affects: SUSE Rancher Rancher versions prior to 2.6.10; Rancher versions prior to 2.7.1.
- How severe is CVE-2022-43755?
- CVE-2022-43755 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability high.
- Is CVE-2022-43755 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2022-43755?
- CVE-2022-43755 affects Suse Rancher. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2022-43755?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2022-43755 published?
- CVE-2022-43755 was published on 2023-02-07 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:suse:rancher:*:*:*:*:*:*:*:*
More vulnerabilities in Suse Rancher
- CVE-2023-22647 — Critical (CVSS 9.9): An Improper Privilege Management vulnerability in SUSE Rancher allowed standard users to leverage their existing…
- CVE-2023-22651 — Critical (CVSS 9.9): Improper Privilege Management vulnerability in SUSE Rancher allows Privilege Escalation. A failure in the update logic…
- CVE-2022-43757 — Critical (CVSS 9.9): A Cleartext Storage of Sensitive Information vulnerability in SUSE Rancher allows users on managed clusters to gain…
- CVE-2021-36783 — Critical (CVSS 9.9): A Insufficiently Protected Credentials vulnerability in SUSE Rancher allows authenticated Cluster Owners, Cluster…
- CVE-2021-36782 — Critical (CVSS 9.9): A Cleartext Storage of Sensitive Information vulnerability in SUSE Rancher allows authenticated Cluster Owners, Cluster…
- CVE-2019-11202 — Critical (CVSS 9.8): An issue was discovered that affects the following versions of Rancher: v2.0.0 through v2.0.13, v2.1.0 through v2.1.8,…
All CVEs affecting Suse Rancher →
Other CWE-331 vulnerabilities
- CVE-2020-36925 — Critical (CVSS 9.8): Arteco Web Client DVR/NVR contains a session hijacking vulnerability with insufficient session ID complexity that…
- CVE-2025-47781 — Critical (CVSS 9.8): Rallly is an open-source scheduling and collaboration tool. Versions up to and including 3.22.1 of the application…
- CVE-2024-47945 — Critical (CVSS 9.8): The devices are vulnerable to session hijacking due to insufficient entropy in its session ID generation algorithm.…
- CVE-2024-25730 — Critical (CVSS 9.8): Hitron CODA-4582 and CODA-4589 devices have default PSKs that are generated from 5-digit hex values concatenated with a…
- CVE-2023-49599 — Critical (CVSS 9.8): An insufficient entropy vulnerability exists in the salt generation functionality of WWBN AVideo dev master commit…
- CVE-2022-34294 — Critical (CVSS 9.8): totd 1.5.3 uses a fixed UDP source port in upstream queries sent to DNS resolvers. This allows DNS cache poisoning…