# CVE-2022-1615: Weak cryptography in Samba > Predictable random values in Samba due to GnuTLS failure allow attackers to bypass security mechanisms relying on randomness. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Sep 2022 - **Updated:** 3 Aug 2024 - **Also known as:** ALPINE-CVE-2022-1615, ALSA-2023:2519, ALSA-2023:2987, AZL-10864, CLSA-2023-1685630287, CLSA-2023-1685631968, DEBIAN-CVE-2022-1615, ECHO-d872-956c-3926, GHSA-hhph-6qvj-8859, OESA-2022-1905, RHSA-2023:2519, RHSA-2023:2987, SUSE-SU-2022:3270-1, SUSE-SU-2022:4014-1, UBUNTU-CVE-2022-1615 ## What is CVE-2022-1615? CVE-2022-1615 is a medium-severity vulnerability in Fedoraproject Fedora, published on 1 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In Samba, GnuTLS gnutls_rnd() can fail and give predictable random values. Weakness: CWE-330 (Use of Insufficiently Random Values) ## Which versions are affected by CVE-2022-1615? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ctdb` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `libnetapi` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `libnetapi-devel` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `libsmbclient` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `libsmbclient-devel` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `libwbclient` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `libwbclient-devel` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `python3-samba` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `python3-samba-dc` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `python3-samba-devel` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `python3-samba-test` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-client` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-client-libs` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-common` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-common-libs` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-common-tools` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-dc-libs` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-dcerpc` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-devel` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-krb5-printing` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-ldb-ldap-modules` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-libs` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-pidl` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-test` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-test-libs` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-tools` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-usershares` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-vfs-iouring` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-winbind` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-winbind-clients` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-winbind-krb5-locator` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-winbind-modules` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `samba-winexe` | AlmaLinux:8 | All versions | 4.17.5-2.el8 | | `ctdb` | AlmaLinux:9 | All versions | 4.17.5-102.el9 | | `libnetapi` | AlmaLinux:9 | All versions | 4.17.5-102.el9 | | `libnetapi-devel` | AlmaLinux:9 | All versions | 4.17.5-102.el9 | | `libsmbclient` | AlmaLinux:9 | All versions | 4.17.5-102.el9 | | `libsmbclient-devel` | AlmaLinux:9 | All versions | 4.17.5-102.el9 | | `libwbclient` | AlmaLinux:9 | All versions | 4.17.5-102.el9 | Products: Fedoraproject Fedora, Samba Samba. ## How do I fix CVE-2022-1615? Apply the vendor's patch. ## Is CVE-2022-1615 being exploited? There is no known exploitation of CVE-2022-1615 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-1615 and fix it if it is affected. What it is: CVE-2022-1615 is a medium-severity vulnerability in Fedoraproject Fedora, published on 1 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-1615 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-1615/ (Markdown: https://insights.sbomify.com/CVE-2022-1615/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1615 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1615 - OSV: https://osv.dev/vulnerability/CVE-2022-1615 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-1615/ Summaries are generated and may contain mistakes; the official description above is the record.