CVE-2024-4561
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA blind Server-Side Request Forgery (SSRF) vulnerability exists in the FaviconController component of WhatsUp Gold. This allows an attacker to make the vulnerable server send arbitrary HTTP requests to internal or external resources without the attacker seeing the direct response.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 23.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WhatsUp Gold installation and versionCheck the installed version of WhatsUp Gold. This is typically visible in the application UI under Help > About, or check the installation directory for version information. The version format appears as a release number like 23.1.xAffected if The installed version is any release prior to 23.1.2 (for example, 23.1.0, 22.x, 21.x)
-
Locate the FaviconController endpointThe vulnerable component is the FaviconController. Check if the application exposes any favicon-related endpoints. Common paths include /favicon.ico handlers or similar. Review the web application's exposed routes and endpointsAffected if The FaviconController endpoint is accessible and the application version is below 23.1.2
-
Review HTTP access logs for suspicious requestsExamine web server and application logs for any requests to FaviconController or favicon-related endpoints that originate from the server itself (127.0.0.1 or the server's own IP) making outbound HTTP requests. Look for unusual internal or external destination IPs in the logs
-
Check for unusual outbound network connectionsReview network flow data, firewall logs, or IDS/IPS alerts for outbound HTTP/HTTPS connections initiated by the WhatsUp Gold server to unusual internal or external destinations, especially connections to internal infrastructure not typically accessed by this server
You are affected if WhatsUp Gold version 23.1.2 or later is NOT installed AND the FaviconController endpoint is exposed, as indicated by version comparison against the vulnerable range.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped23.1.2
Update WhatsUp Gold to version 2023.1.2 or later to patch the vulnerability. If immediate patching is not possible, restrict network access to the FaviconController endpoint and implement outbound request filtering.
WhatsUp Gold 23.1.2 or later
- 1. Identify the current WhatsUp Gold version by navigating to the WhatsUp Gold web interface and checking the 'Help > About WhatsUp Gold' section, or checking the installation via the Programs and Features control panel.
- 2. Download WhatsUp Gold version 23.1.2 or later from the official Progress website at https://www.progress.com/whatsupgold or through the Progress Customer Portal.
- 3. Before applying the upgrade, perform a full backup of the WhatsUp Gold database and configuration files. This is typically located in the 'C:\Program Files\WhatsUp Gold\' directory and associated data directories.
- 4. Review the WhatsUp Gold upgrade documentation for version 23.1.2 to ensure all prerequisites are met, including system requirements and any migration considerations.
- 5. Apply the upgrade by running the installer with appropriate administrative privileges, following the on-screen prompts.
- 6. After upgrade completion, verify the FaviconController vulnerability is remediated by confirming the version number in 'Help > About WhatsUp Gold' shows 23.1.2 or higher.
- 7. Validate that core monitoring functions are operational post-upgrade by checking device polling, alerting, and dashboard functionality.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4561 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4561 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data