Overview
The challenge simulates Active Directory authorization: a session SID, a directory of nested group membership, a resource ACL with allow/deny ACEs, and a curator note. The goal is to determine the correct authorization receipt and submit it to POST /submit. Incorrect answers return 403 with {"ok": false}.
Prerequisites / Setup
export TARGET="<challenge URL or IP>"
The four provided files (session.json, directory.json, resource-acl.json, curator-note.txt) are read locally; no network wordlist or credentials are required beyond $TARGET/submit.
Recon
Step 1 — Confirm the submission endpoint
Goal: Verify that /submit expects a POST and observe the error response shape.
curl -i "$TARGET/submit"
HTTP/1.1 405 METHOD NOT ALLOWED
Allow: OPTIONS, POST
Incorrect answers consistently return:
{
"message": "The request could not be completed.",
"ok": false
}
with HTTP 403.
Interpretation: /submit accepts POST, and the correctness signal is ok: true versus ok: false.
Enumeration
Step 2 — Read session.json
Goal: Identify the session’s SID.
{
"objectSid": "S-1-5-21-810-920-1030-1000"
}
Interpretation: The session belongs to S-1-5-21-810-920-1030-1000.
Step 3 — Resolve nested group membership
Goal: Build the full transitive group-membership path from the session SID.
directory.json shows the chain:
S-1-5-21-810-920-1030-1000
>
S-1-5-21-810-920-1030-1013
>
S-1-5-21-810-920-1030-1027
>
S-1-5-21-810-920-1030-1046
>
S-1-5-21-810-920-1030-1068
In group-name form:
team-a4654927
>
team-0f85fe7a
>
team-b13c037b
>
team-2648700f
>
team-a4283b27
Interpretation: The session does not directly contain SID 1068; it reaches it through transitive group membership.
Step 4 — Read resource-acl.json
Goal: Identify the protected resource and its allow/deny ACEs.
{
"resource": "record-ef1b86a30b808513",
"aces": [
{
"sid": "S-1-5-21-810-920-1030-1068",
"type": "allow",
"right": "ReadProperty"
},
{
"sid": "S-1-5-21-810-920-1030-1069",
"type": "deny",
"right": "ReadProperty"
}
]
}
The effective membership path reaches S-1-5-21-810-920-1030-1068, which has ALLOW ReadProperty. SID 1069 is not in the session’s transitive membership path.
Step 5 — Interpret curator-note.txt
Goal: Understand what the receipt should encode.
curator-note.txt says:
Visitors sometimes belong to more than one committee. For the reading room, consult both the current register and the filed exception.
Mappings:
- current register →
directory.json - multiple committees / nested membership → transitive group resolution
- reading room → the protected resource
- filed exception →
resource-acl.json
Interpretation: The receipt should encode the full effective membership path leading to the authorized SID, together with the target resource.
Vulnerability Analysis
This is an authorization / access-control scenario (nested-group resolution), akin to CWE-284 (Improper Access Control) when group membership is not resolved transitively.
Exploitation
Step 6 — Determine the receipt format
Goal: Find the format accepted by /submit.
Several values and combinations were tested and returned 403:
resource
SIDs
group names
resource|SID
SID|right
SID|allow|ReadProperty
resource|SID|right
full path|resource|right
The successful format:
FULL_TRANSITIVE_SID_PATH|RESOURCE
Successful receipt:
S-1-5-21-810-920-1030-1000>S-1-5-21-810-920-1030-1013>S-1-5-21-810-920-1030-1027>S-1-5-21-810-920-1030-1046>S-1-5-21-810-920-1030-1068|record-ef1b86a30b808513
Step 7 — Submit the receipt
Goal: POST the receipt to /submit and confirm ok: true.
POST /submit
Content-Type: application/json
{
"answer": "S-1-5-21-810-920-1030-1000>S-1-5-21-810-920-1030-1013>S-1-5-21-810-920-1030-1027>S-1-5-21-810-920-1030-1046>S-1-5-21-810-920-1030-1068|record-ef1b86a30b808513"
}
Interpretation: The server accepted the receipt — the full transitive path, not just the authorized SID directly, is what the check expects.
Lessons / Takeaways
- Nested group membership must be resolved transitively; the authorized SID may be several hops from the session SID.
- The receipt encodes the entire authorization path, not just the final SID with the allow ACE.
- When obvious values fail, combine the identifying fields (full path + resource) rather than submitting each in isolation.
Mitigations
- Resolve group membership transitively before evaluating access, and enumerate both allow and deny ACEs.
- Apply least privilege: grant
ReadPropertyonly to the specific SIDs that need it, not to broad nested groups. - Audit effective access (tokenGroups-style enumeration) rather than direct membership alone.
Techniques
References
- Microsoft, “Token Groups and Nested Group Membership”: https://learn.microsoft.com/en-us/windows/win32/ad/token-groups
- CWE-284: Improper Access Control: https://cwe.mitre.org/data/definitions/284.html

