dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-12106

HIGH · 7.5 CVSS v3.1 Published 2024-12-31
Fix available
A fix is available. Upgrade to 24.0.2 or later.
See remediation →
84/100
Remediation priority · High
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 2024.0.2, an unauthenticated attacker can configure LDAP settings.

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

In WhatsUp Gold versions before 2024.0.2, an unauthenticated attacker can access the LDAP configuration interface and modify LDAP settings such as server addresses, bind credentials, search bases, and authentication parameters. This authentication bypass allows attackers to redirect LDAP authentication to a malicious server or manipulate authentication workflows without any credentials.

MitigationUpgrade WhatsUp Gold to version 2024.0.2 or later to patch the authentication bypass. After upgrading, audit LDAP configuration settings to ensure they have not been tampered with and verify that authentication is functioning correctly.

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.0, < 24.0.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify installed WhatsUp Gold version
    Locate the WhatsUp Gold version information in the product interface, registry, or installation directory. This is typically accessible via the Help > About menu in the application or through the installation metadata.
    Affected if The installed version is 23.1.0 or higher but lower than 24.0.2
  2. Review current LDAP server configuration
    Access the LDAP configuration settings within WhatsUp Gold (typically under Administration > LDAP/Active Directory settings) and document the current LDAP server address, port, and connection parameters.
    Affected if The LDAP server address points to an unexpected or unauthorized IP address or hostname that you did not configure
  3. Inspect LDAP bind credentials
    Examine the LDAP bind account credentials configured in WhatsUp Gold, including the bind DN or username and bind password.
    Affected if The bind account credentials have been changed from your known valid values or reference an unfamiliar account
  4. Verify LDAP search base settings
    Check the LDAP search base configuration (base DN) and search filter settings used for user authentication.
    Affected if The search base or search filter has been modified to an unexpected value or points to an unrecognized directory structure
  5. Review authentication parameters
    Inspect any additional LDAP authentication parameters such as SSL/TLS settings, authentication type, or group mapping configurations.
    Affected if SSL/TLS has been disabled, authentication type changed, or group mappings point to unexpected organizational units

You are affected if WhatsUp Gold version is between 23.1.0 and 24.0.1 inclusive AND LDAP configuration settings show unexpected modifications or unauthorized values.

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 24.0.2 or later
Fixed in 24.0.2
Interim mitigation

Upgrade WhatsUp Gold to version 2024.0.2 or later to patch the authentication bypass. After upgrading, audit LDAP configuration settings to ensure they have not been tampered with and verify that authentication is functioning correctly.

Recommended fix High confidence

WhatsUp Gold 2024.0.2 or later

  1. 1. Identify the current WhatsUp Gold version by checking the application or system information
  2. 2. Navigate to the Progress website (www.progress.com) and locate the WhatsUp Gold download section
  3. 3. Download WhatsUp Gold version 2024.0.2 or later
  4. 4. Follow Progress's official upgrade documentation to apply the update
  5. 5. After upgrading, verify that LDAP settings can only be modified by authenticated users
  6. 6. Confirm the new version is running by checking the WhatsUp Gold about or version information
Caveat Review release notes for any configuration changes between your current version and 2024.0.2

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

Fix this in Whatsup Gold Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12106 — 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-12106 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