# CVE-2024-35235: Cupsd Listen arbitrary chmod 0140777

> Attackers can exploit a symlink in the Listen configuration to change file permissions, leading to arbitrary code execution and privilege escalation.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jun 2024
- **Updated:** 21 Feb 2025
- **Also known as:** ALPINE-CVE-2024-35235, ALSA-2024:4265, ALSA-2024:4776, AZL-42579, AZL-42592, BELL-CVE-2024-35235, CLSA-2024-1734531954, CLSA-2025-1762537123, CLSA-2025-1762537354, CLSA-2025-1762544838, DEBIAN-CVE-2024-35235, DLA-3826-1, GHSA-vvwp-mv6j-hw6f, MGASA-2024-0227, OESA-2024-1758, RHSA-2024:4265, RHSA-2024:4580, RHSA-2024:4715, RHSA-2024:4776, RHSA-2024:5644, RLSA-2024:4265, SUSE-SU-2024:2002-1, SUSE-SU-2024:2003-1, SUSE-SU-2024:2003-2, UBUNTU-CVE-2024-35235, USN-6844-1, openSUSE-SU-2024:14041-1

## What is CVE-2024-35235?

CVE-2024-35235 is a medium-severity vulnerability in Debian Debian Linux, published on 11 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. In versions 2.4.8 and earlier, when starting the cupsd server with a Listen configuration item pointing to a symbolic link, the cupsd process can be caused to perform an arbitrary chmod of the provided argument, providing world-writable access to the target. Given that cupsd is often running as root, this can result in the change of permission of any user or system files to be world writable. Given the aforementioned Ubuntu AppArmor context, on such systems this vulnerability is limited to those files modifiable by the cupsd process. In that specific case it was found to be possible to turn the configuration of the Listen argument into full control over the cupsd.conf and cups-files.conf configuration files. By later setting the User and Group arguments in cups-files.conf, and printing with a printer configured by PPD with a `FoomaticRIPCommandLine` argument, arbitrary user and group (not root) command execution could be achieved, which can further be used on Ubuntu systems to achieve full root command execution. Commit ff1f8a623e090dee8a8aadf12a6a4b25efac143d contains a patch for the issue.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-252 (Unchecked Return Value)

## Which versions are affected by CVE-2024-35235?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cups` | AlmaLinux:8 | All versions | 1:2.2.6-60.el8_10 |
| `cups-client` | AlmaLinux:8 | All versions | 1:2.2.6-60.el8_10 |
| `cups-devel` | AlmaLinux:8 | All versions | 1:2.2.6-60.el8_10 |
| `cups-filesystem` | AlmaLinux:8 | All versions | 1:2.2.6-60.el8_10 |
| `cups-ipptool` | AlmaLinux:8 | All versions | 1:2.2.6-60.el8_10 |
| `cups-libs` | AlmaLinux:8 | All versions | 1:2.2.6-60.el8_10 |
| `cups-lpd` | AlmaLinux:8 | All versions | 1:2.2.6-60.el8_10 |
| `cups` | AlmaLinux:9 | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-client` | AlmaLinux:9 | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-devel` | AlmaLinux:9 | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-filesystem` | AlmaLinux:9 | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-ipptool` | AlmaLinux:9 | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-libs` | AlmaLinux:9 | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-lpd` | AlmaLinux:9 | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-printerapp` | AlmaLinux:9 | All versions | 1:2.3.3op2-27.el9_4 |
| `cups` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-client` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-client-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-filesystem` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-ipptool` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-ipptool-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-lpd` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups-lpd-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.2.6-60.el8_10 |
| `cups` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.2.6-60.el8_10 |
| `cups-client-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.2.6-60.el8_10 |
| `cups-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.2.6-60.el8_10 |
| `cups-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.2.6-60.el8_10 |
| `cups-ipptool-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.2.6-60.el8_10 |
| `cups-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.2.6-60.el8_10 |
| `cups-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.2.6-60.el8_10 |
| `cups-lpd-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.2.6-60.el8_10 |
| `cups` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-client` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-client-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.3.3op2-27.el9_4 |
| `cups-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.3.3op2-27.el9_4 |

Products: Debian Debian Linux, Openprinting Cups.

## How do I fix CVE-2024-35235?

Apply the vendor's patch.

## Is CVE-2024-35235 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35235 exists.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35235 and fix it if it is affected.

What it is: CVE-2024-35235 is a medium-severity vulnerability in Debian Debian Linux, published on 11 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35235 exists.

Affected product: Debian Debian Linux. 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-2024-35235/ (Markdown: https://insights.sbomify.com/CVE-2024-35235/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-35235
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-35235
- OSV: https://osv.dev/vulnerability/CVE-2024-35235

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-35235/
Summaries are generated and may contain mistakes; the official description above is the record.