# CVE-2022-4725: AWS SDK XML Parser XpathUtils.java XpathUtils server-side request forgery

> An attacker can exploit a server-side request forgery vulnerability in the AWS SDK XML parser to access internal resources or bypass security controls.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f5h9-qx38-2hgp

## What is CVE-2022-4725?

CVE-2022-4725 is a medium-severity server-side request forgery vulnerability in AWS SDK, published on 24 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-4725?

2 open source packages ship an affected version, including com.amazonaws:aws-android-sdk-mobile-client. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.amazonaws:aws-android-sdk-mobile-client` | Maven | All versions | 2.59.1 |
| `com.amazonaws:aws-android-sdk-mobile-client` | Maven | All versions | 2.59.1 |

Products: Amazon Aws Software Development Kit.

## How do I fix CVE-2022-4725?

Upgrade com.amazonaws:aws-android-sdk-mobile-client to 2.59.1 or later.

## Is CVE-2022-4725 being exploited?

There is no known exploitation of CVE-2022-4725 in the wild and no public exploit code.

## Other vulnerabilities in AWS SDK

- [CVE-2018-19981](https://insights.sbomify.com/CVE-2018-19981/): Information disclosure in n/a (high 7.2)
- [CVE-2026-19642](https://insights.sbomify.com/CVE-2026-19642/): Out-of-bounds write in the Base64 decoder in Amazon aws-sdk-cpp (medium 6.0)
- [CVE-2026-19643](https://insights.sbomify.com/CVE-2026-19643/): Out-of-bounds read in the Base64 decoder in Amazon aws-sdk-cpp on signed-char platforms (medium 6.0)
- [CVE-2023-51651](https://insights.sbomify.com/CVE-2023-51651/): Potential URI resolution path traversal in the AWS SDK for PHP (medium 6.0)
- [CVE-2022-2582](https://insights.sbomify.com/CVE-2022-2582/): Exposure of unencrypted plaintext hash in github.com/aws/aws-sdk-go (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4725 and fix it if it is affected.

What it is: CVE-2022-4725 is a medium-severity server-side request forgery vulnerability in AWS SDK, published on 24 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4725 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.amazonaws:aws-android-sdk-mobile-client (Maven): affected all versions; fixed in 2.59.1
- com.amazonaws:aws-android-sdk-mobile-client (Maven): affected all versions; fixed in 2.59.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4725/ (Markdown: https://insights.sbomify.com/CVE-2022-4725/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4725
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4725
- OSV: https://osv.dev/vulnerability/CVE-2022-4725

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4725/
Summaries are generated and may contain mistakes; the official description above is the record.