AWS SDK 2.59.0 on Android XML Parser XpathUtils.java XpathUtils server-side request forgery
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability was found in AWS SDK 2.59.0 on Android (Android App Software). 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 with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 12/24/2022 as 3100. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-4725. Technical details are known, but no exploit is available.
Upgrading to version 2.59.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch c3e6d69422e1f0c80fe53f2d757b8df97619af2b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
CVSSv3VulDB Meta Base Score: 6.9
VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CNA Base Score: 5.5
CNA Vector (VulDB): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Server-side request forgery
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: AWS SDK 2.59.1
Timeline12/24/2022 Advisory disclosed
12/24/2022 +0 days CVE reserved
12/24/2022 +0 days VulDB entry created
01/24/2023 +31 days VulDB last update
CVE: CVE-2022-4725 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20130704
EntryCreated: 12/24/2022 08:35 AM
Updated: 01/24/2023 07:43 AM
Changes: 12/24/2022 08:35 AM (43), 12/24/2022 08:38 AM (3), 12/24/2022 02:52 PM (3), 01/24/2023 07:37 AM (2), 01/24/2023 07:43 AM (21)
Do you want to use VulDB in your project?
Use the official API to access entries easily!