WhatsUp Gold: Exposure of Sensitive Information to an Unauthorized Actor
CVE-2024-5010 is a high-severity exposure of sensitive information to an unauthorized actor vulnerability in WhatsUp Gold from Progress Software, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2023.1.3 as the first without the flaw, so updating WhatsUp Gold to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 70% chance of exploitation within 30 days, which is in the top 0.61% of all scored CVEs.
Exploitation in the next 30 days is more likely than not, according to EPSS.
What to do
- Update WhatsUp Gold to 2023.1.3 or a later version.
- Read the advisory on community.progress.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Progress Software | WhatsUp Gold | 2023.1.0 up to, but not including, 2023.1.3 | 2023.1.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (progress.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
In WhatsUp Gold versions released before 2023.1.3, a vulnerability exists in the TestController functionality. A specially crafted unauthenticated HTTP request can lead to a disclosure of sensitive information.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How developers prevent this class of flaw
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
More Exposure of Sensitive Information to an Unauthorized Actor vulnerabilities (CWE-200)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- talosintelligence.com/vulnerability_reports/TALOS-2024-1933Third Party Advisory
Other references
Other vulnerabilities in WhatsUp Gold
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Recent Exposure of Sensitive Information to an Unauthorized Actor vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.5 High severity
Spotted an error? Tell us.