CVE-2024-4562
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 , an SSRF vulnerability exists in Whatsup Gold's Issue exists in the HTTP Monitoring functionality. Due to the lack of proper authorization, any authenticated user can access the HTTP monitoring functionality, what leads to the Server Side Request Forgery.
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 confidenceWhatsUp Gold before 2023.1.2 contains a Server Side Request Forgery (SSRF) vulnerability in its HTTP Monitoring functionality. The issue stems from insufficient authorization controls that allow any authenticated user to access and abuse the HTTP monitoring feature to make the server request arbitrary URLs, potentially enabling internal service enumeration or pivoting.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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.
-
Determine installed WhatsUp Gold versionLocate the WhatsUp Gold installation directory and check the version information, typically found in the application itself under Help > About, or in installation logs and registry entries for the installed product.Affected if The installed version is lower than 23.1.2.
-
Verify HTTP Monitoring feature statusAccess the WhatsUp Gold admin interface and navigate to the HTTP Monitoring settings or monitors list. Check whether any HTTP monitors are configured or if the feature is enabled in the monitoring configuration.Affected if HTTP Monitoring is enabled and actively configured.
-
Review user roles with HTTP monitoring accessExamine the WhatsUp Gold user role and permission configuration. Look for which users or groups are assigned permissions that allow them to create or modify HTTP monitors.Affected if Any authenticated user (especially non-administrator accounts) has permissions to configure or trigger HTTP monitoring requests.
-
Inspect HTTP monitoring activity logsReview WhatsUp Gold logs, particularly those related to HTTP monitoring or outbound requests. Look for entries showing requests to internal IP addresses, localhost, or non-standard ports.Affected if Logs contain HTTP requests from the WhatsUp Gold server to internal resources or unusual destinations.
You are affected if your WhatsUp Gold version is below 23.1.2 AND the HTTP Monitoring feature is accessible to users who should not have that capability.
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
Upgrade WhatsUp Gold to version 2023.1.2 or later. Additionally, implement proper role-based access controls (RBAC) on the HTTP monitoring functionality to ensure only authorized users can trigger outbound HTTP requests.
23.1.2
- Upgrade WhatsUp Gold to version 23.1.2 or later to remediate the SSRF vulnerability in the HTTP Monitoring functionality
- After upgrading, verify that the HTTP Monitoring functionality works correctly
- Confirm that the fix includes proper authorization checks for the HTTP monitoring feature
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4562 — 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-4562 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