Featured post
Poisoning Rhino, Then Waiting for the Callback
A PythonScript policy could leave an unrestricted Rhino context on an Apigee worker, and an asynchronous JavaScript httpClient callback could reuse it…
Read the researchbugs.exposed
The story behind the bug.
Security findings, taken apart and explained.
Most viewed Last 30 days
Breaking Open the Forgotten Vault
A patched PythonScript policy flaw allowed JavaScript to run outside its usual sandbox.
Read the researchMore writeups
6 postsApplication security
User Input Risks in Apigee Target URLs
What I found when request values were inserted into Apigee target URLs without validation or encoding.
Application security
Dealing with Path Parameters
How Apigee path matching and exact comparisons can disagree on separators, routing, and validation.
Application security
Beyond the Basics
Logging, caching, fault handling, and flow-variable checks for Apigee proxies.
Application security
How to Start Securing Your Proxy
Five checks I start with when reviewing an Apigee API proxy.
Writeups
Breaking the Sandbox
How access to Apigee’s internal execution context bypassed PythonScript sandbox restrictions.
Writeups
Discovering Rhino’s Blind Spot
How Java objects shared between Apigee policies bypassed Rhino’s class restrictions.