Improper Sandboxing in Google Apigee's JavaCallout Policy Allows for Remote Code Execution
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in Hybrid_1.11.2, Hybrid_1.12.4, Hybrid_1.13.3, Hybrid_1.14.1, OPDK_5202, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A vulnerability exists in Google Apigee's JavaCallout policy https://docs.apigee.com/api-platform/reference/policies/java-callout-policy that allows for remote code execution. It is possible for a user to write a JavaCallout that injected a malicious object into the MessageContext to execute arbitrary Java code and system commands at runtime, leading to unauthorized access to data, lateral movement within the network, and access to backend systems. The Apigee hybrid versions below have all been updated to protect from this vulnerability: • Hybrid_1.11.2+ • Hybrid_1.12.4+ • Hybrid_1.13.3+ • Hybrid_1.14.1+ • OPDK_5202+ • OPDK_5300+
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Google Cloud Apigee hybrid Javacallout policy
fixed in Hybrid_1.11.2; fixed in Hybrid_1.12.4; fixed in Hybrid_1.13.3; fixed in Hybrid_1.14.1; fixed in OPDK_5202; fixed in OPDK_5300