batch-request-object-isolation
/batch-request-object-isolation
Sprawdza, czy żądania wsadowe nie mieszają tożsamości, poświadczeń ani obiektów między sobą w jednym przetwarzaniu.
- Autor
- Wsh7Ash ↗
- Repozytorium
- authzmap ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 28.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 28.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Sprawdza, czy żądania wsadowe nie mieszają tożsamości, poświadczeń ani obiektów między sobą w jednym przetwarzaniu.
Oryginalny opis (EN)
Check that batched requests cannot mix identities, credentials or objects so one operation borrows another's context. Use when the API accepts a batch array or HTTP/2 multiplexed requests that share processing context
Jak działa
- Procedure
- Signals
- Patterns
- Pitfalls
- Done when
- References
Podgląd SKILL.md
--- name: batch-request-object-isolation description: "Check that batched requests cannot mix identities, credentials or objects so one operation borrows another's context. Use when the API accepts a batch array or HTTP/2 multiplexed requests that share processing context" pack: authzmap version: 1.0.0 category: api-security tags: [batch, isolation, object-level] --- # Batch Request Object Isolation > Check that batched requests cannot mix identities, credentials or objects so one operation borrows another's context **Use when:** the API accepts a batch array or HTTP/2 multiplexed requests that share processing context **Avoid when:** each request is handled strictly independently with no shared context between them ## Procedure 1. Identify how batches are accepted and how context is established: one credential for the batch or one per item. 2. Send a batch where items alternate between your two test accounts' object identifiers under a single credential. 3. Send a batch carrying two different credentials, if supported, and check whether the first item's context leaks into later items. 4. Observe error handling: does one failed item abort the batch, reveal others' results, or alter shared state? 5. Check for ordering effects where an earlier item changes context that later items inherit. 6. Record per-item outcomes so context bleed is attributable to a specific item position. ## Signals - Items later in the batch return data matching the context of an earlier item rather than their own. - Per-item credentials are accepted and one item's role applies to subsequent items. - An error in item one returns partial results from items that should have been refused. - Batch responses include fields that belong to a different item's object. ## Patterns **1. Mixed batch** ```text items: [fetch(peer-id), fetch(my-id)] under my credential expected: refuse + succeed observed: both succeed -> finding ``` **2. Context test** ```text item1 credential=A role=member, item2 credential=B role=admin -> if item2 returns admin data, context bled from item1 ``` **3. Result row** ```text batch_size=4 mixed=peer-items=2 leaked=0 outcome=refused-cleanly ``` ## Pitfalls - Testing batches that contain only your own objects, which cannot expose context mixing. - Ignoring partial-success semantics that silently return unauthorized results alongside errors. - Forgetting write operations in the batch, where context bleed causes cross-account modification. ## Done when - Mixed-object and mixed-credential batches have been executed with per-item outcomes recorded. - Context bleed is ruled in or out for read and write items, and ordering effects are documented. ## References - [OWASP API Security Top 10](https://owasp.org/www-project-api-security/) - [JSON:API - compound documents](https://jsonapi.org/)
Wersje
W bazie nie ma innych skilli o nazwie batch-request-object-isolation.
Migawka bazy z 13.11.2026 · wersja paczki 906e89f96d32 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100batch-write-single-record-scope
Sprawdza, czy zapis wsadowy nie zmienia rekordów spoza zamierzonego zakresu w ramach audytu własnego API. - 100batch-envelope-partial-signature
Sprawdza, czy podpis paczki zdarzeń obejmuje każdy element, bo niepodpisany wpis w podpisanej tablicy jest nieuwierzytelniony.