Progress Whatsup Gold up to 21.1.1/22.0.0 API Transaction information disclosure
|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 Progress Whatsup Gold up to 21.1.1/22.0.0 (Network Management Software). It has been classified as problematic. This affects some unknown processing of the component API Transaction Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. This is going to have an impact on confidentiality. The summary by CVE is:
In Progress Ipswitch WhatsUp Gold 21.1.0 through 21.1.1, and 22.0.0, it is possible for an authenticated user to invoke an API transaction that would allow them to read the contents of a local file.
The weakness was presented 05/12/2022. The advisory is shared at community.progress.com. This vulnerability is uniquely identified as CVE-2022-29845 since 04/27/2022. The exploitability is told to be easy. Access to the local network is required for this attack to succeed. Required for exploitation is a authentication. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
CVSSv3VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Information disclosure
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔒
Timeline04/27/2022 CVE reserved
05/12/2022 +15 days Advisory disclosed
05/12/2022 +0 days VulDB entry created
05/14/2022 +2 days VulDB last update
CVE: CVE-2022-29845 (🔒)
EntryCreated: 05/12/2022 12:46 PM
Updated: 05/14/2022 03:46 PM
Changes: (1) source_cve_nvd_summary
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!