# Residual access after explicit session revocation

A revoked credential or removed membership retains access beyond the product’s applicable revocation guarantee.

**Candidate CWE:** [CWE-613](https://cwe.mitre.org/data/definitions/613.html)

## Test hypothesis

Save a valid controlled session, confirm one private read, perform explicit device/session revocation, then replay that read. Test refresh credentials and existing streams independently.

## Evidence required

The old credential still produces protected data or actions after the documented revocation point. Include timestamps, expected behavior, session type, and exact retained permission.

## Rule out false positives

Browser-only logout, a public cache, documented short-lived access-token behavior, or offline UI data requires separate interpretation.

## Playbook and command references

- [Authentication, recovery, federation, and session lifecycle](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/identity-session.html) — Test registration, recovery, identity changes, invitations, SSO enforcement, and deprovisioning as one account state machine.
- [Object, function, and property authorization](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/authz-matrix.html) — Turn identities, tenants, objects, roles, and lifecycle transitions into a reproducible permission matrix.
- [REST, GraphQL, gRPC, WebSocket, and SSE permission parity](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/api-protocols.html) — Carry the same permission invariant across protocols, nested fields, streams, and alternate API versions.

[Find the associated command snippets](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/commands.html?q=Authentication%2C%20recovery%2C%20federation%2C%20and%20session%20lifecycle)

## Referenced by these target playbooks

[Web & API](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/web-api.html) · [OSS & self-hosted](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/oss.html) · [Mobile](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/mobile.html) · [Desktop & extensions](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/desktop.html) · [Cloud & containers](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/cloud.html) · [AI, agents & MCP](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/ai.html)

## Report checklist

- [ ] Capture the affected version, configuration, identities, and object ownership.
- [ ] Preserve a valid baseline and a negative control.
- [ ] Reproduce the forbidden data access, action, or state change on controlled fixtures.
- [ ] Explain the intended security rule and why the observed behavior violates it.
- [ ] State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

## Conditional ATT&CK mapping

- [T1550.004 · Use Alternate Authentication Material: Web Session Cookie](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/attack.html#T1550-004) — **Only if:** A session cookie acquired across a security boundary is accepted in another controlled client to access the represented user's protected session. **Not established by:** A missing cookie flag, reflected cookie name, or untested assumption about MFA bypass is insufficient. Ordinary cookie-based login does not demonstrate compromise.

## Primary references

- [OWASP session management](https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html)

[Back to the complete vulnerability catalog](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/vulnerabilities.html)