> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/fr/cms/cups-cms-exploitation.md).

# CUPS

Notes d’exploitation de CUPS 1.6.1 pour la redirection ErrorLog, l’abus de lecture de fichiers root, la divulgation de /etc/shadow, l’escalade de privilèges locale et la récupération de fichiers sensibles.

### Exploitation de la vulnérabilité CUPS 1.6.1

{% embed url="<https://github.com/rapid7/metasploit-framework/blob/master/modules/post/multi/escalate/cups_root_file_read.rb>" %}

En utilisant **cupsctl**, modifiez le **CUPS** configuration du service pour rediriger **ErrorLog** vers un fichier sensible tel que **/etc/shadow**. Cela permet de lire le fichier en tant que root via l'interface web CUPS.

Commande pour modifier la configuration :

```bash
cupsctl ErrorLog=/etc/shadow
```

Accédez à l'interface web CUPS via le tunnel :

Cela expose le contenu de **/etc/shadow** et permet `root.txt` d'être récupéré.

<figure><img src="https://3840167291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-f0976e5fefeb3292acb77770ae8bceedd1cc81f0%2Fimage%20(1032).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hacking-notes.jord4n.pro/fr/cms/cups-cms-exploitation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.