dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-5012

HIGH · 8.6 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 23.1.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In WhatsUp Gold versions released before 2023.1.3, there is a missing authentication vulnerability in WUGDataAccess.Credentials. This vulnerability allows unauthenticated attackers to disclose Windows Credentials stored in the product Credential Library.

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 · high confidence

This is a missing authentication vulnerability in WhatsUp Gold's WUGDataAccess.Credentials component. Unauthenticated attackers can exploit this flaw to access and disclose Windows Credentials stored in the product's Credential Library, potentially exposing sensitive authentication material.

MitigationUpgrade to WhatsUp Gold version 2023.1.3 or later to obtain the vendor patch that addresses this missing authentication check.

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
Whatsup GoldApplication
Affected:< 23.1.3

CVSS 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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WhatsUp Gold installation and version
    Check the Windows installed programs list or examine the WhatsUp Gold installation directory for a version file. Common paths: C:\Program Files\Progress\WhatsUp\ or check registry key HKLM\SOFTWARE\Progress\WhatsUp\Configuration for the InstallVersion value.
    Affected if The installed version is present and is lower than 23.1.3
  2. Identify the WUGDataAccess.Credentials component
    Inspect the WhatsUp Gold web application or API endpoints for the WUGDataAccess.Credentials service. This is typically exposed as a web service or API endpoint within the WhatsUp Gold application.
    Affected if The WUGDataAccess.Credentials component is present and responds to unauthenticated requests
  3. Verify Credential Library access
    Test access to the Credential Library feature in WhatsUp Gold without providing authentication credentials. This can be done by attempting to access the credentials endpoint directly via HTTP/HTTPS request to the WhatsUp Gold server.
    Affected if Unauthenticated access to the Credential Library returns credential data or exposes credential storage
  4. Check for exposed credential data
    Review any accessible credential storage files or database entries that the WUGDataAccess.Credentials component uses. Look for Windows Credential files or database tables containing stored credentials that may be readable without authentication.
    Affected if Credential data is retrievable without authentication credentials

A defender is affected if WhatsUp Gold version is lower than 23.1.3 and the WUGDataAccess.Credentials component is accessible without authentication, allowing exposure of stored Windows credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 23.1.3 or later
Fixed in 23.1.3
Interim mitigation

Upgrade to WhatsUp Gold version 2023.1.3 or later to obtain the vendor patch that addresses this missing authentication check.

Recommended fix High confidence

WhatsUp Gold 23.1.3 or later

  1. Upgrade WhatsUp Gold to version 23.1.3 or later to remediate the missing authentication vulnerability
  2. After upgrading, verify that the WUGDataAccess.Credentials component now requires proper authentication
  3. Review the Credential Library in WhatsUp Gold to confirm stored Windows Credentials are no longer accessible without authentication
  4. Test that legitimate authentication flows for credential access work correctly post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Whatsup Gold Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5012 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5012 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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