CVE-2024-4561 json
WhatsUp Gold Server-Side Request Forgery Information Disclosure Vulnerability via FaviconController
published 2024-05-14 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-44173
- cvss
- 4.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
In WhatsUp Gold versions released before 2023.1.2 ,
a blind SSRF vulnerability exists in Whatsup Gold's FaviconController that allows an attacker to send arbitrary HTTP requests on behalf of the vulnerable server.
Patch / fix
- Progress Software Corporation WhatsUp Gold 2023.1.2
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-4561 updated cvss 4.2
whatsup: end arbitrary HTTP requests on behalf of the vulnerable server
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- Progress Software Corporation WhatsUp Gold
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
community.progress.com
/s/article/Announcing-WhatsUp-Gold-v2023-1-2
vendor-advisory
-
progress.com
/network-monitoring
product
Sources
- CVE List CVE-2024-4561
- NVD CVE-2024-4561
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.