CVE-2022-4725 is a medium-severity (CVSS 5.5) Server-Side Request Forgery (SSRF) vulnerability in com.amazonaws:aws-android-sdk-mobile-client. A fix is available for com.amazonaws:aws-android-sdk-mobile-client — see the affected versions and patch details below.
AWS SDK XML Parser XpathUtils.java XpathUtils server-side request forgery
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.amazonaws:aws-android-sdk-mobile-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability was found in AWS SDK 2.59.0. It has been rated as critical. This issue affects the function XpathUtils of the file aws-android-sdk-core/src/main/java/com/amazonaws/util/XpathUtils.java of the component XML Parser. The manipulation leads to server-side request forgery. Upgrading to version 2.59.1 is able to address this issue. The name of the patch is c3e6d69422e1f0c80fe53f2d757b8df97619af2b. It is recommended to upgrade the affected component. The identifier VDB-216737 was assigned to this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.amazonaws:aws-android-sdk-mobile-client | all versions | 2.59.1com.amazonaws:aws-android-sdk-mobile-client:2.59.1 |
Affected Products
aws software development kitamazonDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.amazonaws:aws-android-sdk-mobile-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.amazonaws:aws-android-sdk-mobile-client to 2.59.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-4725 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2022-4725 in your dependencies?
Find it across Maven, including transitive dependencies.