# CVE-2022-32746: Use after free in samba > A use-after-free flaw in Samba's AD DC audit logging allows attackers to potentially execute code or escalate privileges when modifying privileged attributes. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`) - **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-32746, ALSA-2022:7730, ALSA-2022:8318, AZL-10707, AZL-37015, AZL-45138, DEBIAN-CVE-2022-32746, ECHO-c3d7-9b4c-ea5e, GHSA-hv8p-prvv-v646, OESA-2022-1806, RHSA-2022:7730, RHSA-2022:8318, RLSA-2022:7730, RLSA-2022:8318, UBUNTU-CVE-2022-32746, openSUSE-SU-2024:12241-1 ## What is CVE-2022-32746? CVE-2022-32746 is a medium-severity use after free 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 the Samba AD LDAP server. The AD DC database audit logging module can access LDAP message values freed by a preceding database module, resulting in a use-after-free issue. This issue is only possible when modifying certain privileged attributes, such as userAccountControl. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2022-32746? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ldb-tools` | AlmaLinux:8 | All versions | 2.5.2-2.el8 | | `libldb` | AlmaLinux:8 | All versions | 2.5.2-2.el8 | | `libldb-devel` | AlmaLinux:8 | All versions | 2.5.2-2.el8 | | `python-ldb-devel-common` | AlmaLinux:8 | All versions | 2.5.2-2.el8 | | `python3-ldb` | AlmaLinux:8 | All versions | 2.5.2-2.el8 | | `python3-ldb-devel` | AlmaLinux:8 | All versions | 2.5.2-2.el8 | | `ldb-tools` | AlmaLinux:9 | All versions | 2.5.2-1.el9 | | `libldb` | AlmaLinux:9 | All versions | 2.5.2-1.el9 | | `libldb-devel` | AlmaLinux:9 | All versions | 2.5.2-1.el9 | | `python3-ldb` | AlmaLinux:9 | All versions | 2.5.2-1.el9 | | `ldb-tools` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.5.2-2.el8 | | `ldb-tools-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.5.2-2.el8 | | `libldb` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.5.2-2.el8 | | `libldb-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.5.2-2.el8 | | `libldb-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.5.2-2.el8 | | `libldb-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.5.2-2.el8 | | `python3-ldb` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.5.2-2.el8 | | `python3-ldb-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.5.2-2.el8 | | `ldb-tools-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.5.2-2.el8 | | `libldb-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.5.2-2.el8 | | `libldb-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.5.2-2.el8 | | `python-ldb-devel-common` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.5.2-2.el8 | | `python3-ldb-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.5.2-2.el8 | | `python3-ldb-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.5.2-2.el8 | | `ldb-tools` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.5.2-1.el9 | | `ldb-tools-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.5.2-1.el9 | | `libldb` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.5.2-1.el9 | | `libldb-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.5.2-1.el9 | | `libldb-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.5.2-1.el9 | | `python3-ldb` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.5.2-1.el9 | | `python3-ldb-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.5.2-1.el9 | | `ldb-tools-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.5.2-1.el9 | | `libldb-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.5.2-1.el9 | | `libldb-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.5.2-1.el9 | | `libldb-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.5.2-1.el9 | | `python3-ldb-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.5.2-1.el9 | | `libldb` | Rocky Linux:8 | All versions | 0:2.5.2-2.el8 | | `libldb` | Rocky Linux:9 | All versions | 0:2.5.2-1.el9 | | `ldb` | openSUSE:Tumbleweed | All versions | 2.5.2-1.1 | Products: Samba Samba. ## How do I fix CVE-2022-32746? Apply the vendor's patch. ## Is CVE-2022-32746 being exploited? There is no known exploitation of CVE-2022-32746 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-32746 and fix it if it is affected. What it is: CVE-2022-32746 is a medium-severity use after free 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-32746 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-32746/ (Markdown: https://insights.sbomify.com/CVE-2022-32746/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-32746 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-32746 - OSV: https://osv.dev/vulnerability/CVE-2022-32746 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-32746/ Summaries are generated and may contain mistakes; the official description above is the record.