详细内容
Latest:Why You Need Account-Based Rate LimitsRead more → ✕
Click to read the latest blog post: Why You Need Account-Based Rate Limits
Autonomous Security Testing
Casco performs autonomous security testing for your web apps, APIs, infrastructure, and AI systems. Human supervision optionally available.
Casco Demo: Supervised Agentic Red Teaming for AI Agents and Apps - YouTube
Casco
9 subscribers
Casco Demo: Supervised Agentic Red Teaming for AI Agents and Apps
Casco
Search
Watch later
Share
Copy link
Info
Shopping
Tap to unmute
If playback doesn't begin shortly, try restarting your device.
More videos
More videos
You're signed out
Videos you watch may be added to the TV's watch history and influence TV recommendations. To avoid this, cancel and sign in to YouTube on your computer.
CancelConfirm
Share
Include playlist
An error occurred while retrieving sharing information. Please try again later.
0:00
0:00 / 2:01
•Live
•
Trusted byteams building the future














Fast-moving companies choose Casco over traditional pentesters
Don’t take it from us. See how real teams are using Casco to test smarter and ship faster.
“In a matter of hours, Casco was able to find critical vulnerabilities that our other pentesters couldn't find for months.”
Bryan Chappell, CEO of Scout
“In my 15 years working in cybersecurity, Casco is the first cybersecurity product that makes security testing high-quality, fast, and easy.”
Matthew Broom, Head of Security at CrewAI
“Casco is mission-critical for enterprise deals. We started the security assessment on a Friday and completed the procurement process by Monday.”
Saarth Shah, CEO of SixtyFour
Year-round security instead of once-a-year security
Make security a function of your codebase, and plan a vacation instead
Dec 31Jan 1
VulnerablePentestFix“Secure”
VS
Dec 31Jan 1
Human pentester
Vulnerable most of the time.
Casco Autonomous Security
Always monitored. Always protected
Clear findings — what to fix, and why it matters
You get full context, impact, and verification in one clear report.
Improper JWT Verification Leading to Cross-User Data Exposure in AI Claims Chat.
CRITICALCVSS 9.8
Summary
The endpoint accepts a client-supplied JWT but does not verify its signature or validate the claim against the authenticated session. An attacker can tamper the field to impersonate another user, causing the backend to fetch and feed that user’s private documents into the LLM, which then leaks sensitive data.
Business impact articulated
Impact
!Unauthorized disclosure of PII, health records, and underwriting notes.
!Violation of data-protection regulations (e.g., HIPAA).
!Significant reputational damage and potential legal liability.
Step-by-step reproduction
Reproduction
- Obtain a valid JWT for User A.
- Decode the JWT payload and change thesub claim to User B’s ID.
- Re-encode the token without resigning.
- Send a POST to/claims/chatwith the modified JWT in Authorization.
- Observe that the response (LLM summary) includes User B’s documents—confirming the backend never verified the signature or subject claim.
Recommendation
- Enforce JWT signature validation on every request using the issuer’s public key.
- Ensure thesub claim matches the authenticated user context before data retrieval.
- Implement per-user authorization checks on document fetch APIs, rejecting mismatched subjects.
- Log and alert on any failed or tampered JWT validations.
One-click Retest
Open
Retest
Onboard with our forward deployed security engineers
Expert-led onboarding tailored to your stack.
Direct line to your dedicated technical contact.
Scoped access to source code and staging environments.
Guided walkthrough of critical findings.

