# CVE-2022-32742: Information disclosure in samba > SMB1 write requests lacking range checks allow server memory contents to be written to files or printers, disclosing sensitive data. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Aug 2022 - **Updated:** 3 Aug 2024 - **Also known as:** ALPINE-CVE-2022-32742, ALSA-2022:7111, ALSA-2022:8317, AZL-10736, AZL-37012, CLSA-2022-1668546881, CLSA-2022-1668547929, CLSA-2026-1778604245, CLSA-2026-1779223801, DEBIAN-CVE-2022-32742, ECHO-4dac-3195-2546, GHSA-j7gp-2jqv-76gj, RHSA-2022:7056, RHSA-2022:7111, RHSA-2022:8317, RLSA-2022:7111, RLSA-2022:8317, SUSE-SU-2022:2580-1, SUSE-SU-2022:2585-1, SUSE-SU-2022:2598-1, SUSE-SU-2022:2621-1, SUSE-SU-2022:2651-1, UBUNTU-CVE-2022-32742 ## What is CVE-2022-32742? CVE-2022-32742 is a medium-severity vulnerability in Samba Samba, published on 25 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in Samba. Some SMB1 write requests were not correctly range-checked to ensure the client had sent enough data to fulfill the write, allowing server memory contents to be written into the file (or printer) instead of client-supplied data. The client cannot control the area of the server memory written to the file (or printer). Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2022-32742? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ctdb` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `libsmbclient` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `libsmbclient-devel` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `libwbclient` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `libwbclient-devel` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `python3-samba` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `python3-samba-test` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-client` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-client-libs` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-common` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-common-libs` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-common-tools` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-devel` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-krb5-printing` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-libs` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-pidl` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-test` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-test-libs` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-vfs-iouring` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-winbind` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-winbind-clients` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-winbind-krb5-locator` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-winbind-modules` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `samba-winexe` | AlmaLinux:8 | All versions | 4.15.5-10.el8_6 | | `ctdb` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `libsmbclient` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `libsmbclient-devel` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `libwbclient` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `libwbclient-devel` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `python3-samba` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `samba` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `samba-client` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `samba-client-libs` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `samba-common` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `samba-common-libs` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `samba-common-tools` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `samba-devel` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `samba-krb5-printing` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | | `samba-libs` | AlmaLinux:9 | All versions | 4.16.4-101.el9 | Products: Samba Samba. ## How do I fix CVE-2022-32742? Apply the vendor's patch. ## Is CVE-2022-32742 being exploited? There is no known exploitation of CVE-2022-32742 in the wild and no public exploit code. ## Other vulnerabilities in Samba Samba - [CVE-2012-1182](https://insights.sbomify.com/CVE-2012-1182/): Integer overflow in n/a (critical 10.0) - [CVE-2007-2446](https://insights.sbomify.com/CVE-2007-2446/): Memory corruption in n/a (critical 10.0) - [CVE-2004-0600](https://insights.sbomify.com/CVE-2004-0600/): Memory corruption in n/a (critical 10.0) - [CVE-1999-0810](https://insights.sbomify.com/CVE-1999-0810/): Denial of service in n/a (critical 10.0) - [CVE-1999-0182](https://insights.sbomify.com/CVE-1999-0182/): Memory corruption in n/a (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-32742 and fix it if it is affected. What it is: CVE-2022-32742 is a medium-severity vulnerability in Samba Samba, published on 25 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-32742 in the wild and no public exploit code. Affected product: Samba Samba. 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-32742/ (Markdown: https://insights.sbomify.com/CVE-2022-32742/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-32742 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-32742 - OSV: https://osv.dev/vulnerability/CVE-2022-32742 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-32742/ Summaries are generated and may contain mistakes; the official description above is the record.