dbcve.org
Whatsup GoldApplication · Progress

CVE-2022-29846

MEDIUM · 5.3 CVSS v3.1 Published 2022-05-11
Fix available
A fix is available. Upgrade to after 21.1.1 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Progress Ipswitch WhatsUp Gold 16.1 through 21.1.1, and 22.0.0, it is possible for an unauthenticated attacker to obtain the WhatsUp Gold installation serial number.

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 confidence

In Progress Ipswitch WhatsUp Gold versions 16.1 through 21.1.1 and 22.0.0, an information disclosure vulnerability allows unauthenticated attackers to obtain the installation serial number via an unspecified attack vector. This pre-authentication flaw exposes sensitive license information that could facilitate further attacks or unauthorized product use.

MitigationApply the vendor-provided security patch for this vulnerability. If immediate patching is not feasible, restrict network access to the WhatsUp Gold management interface to trusted networks or VPN connections to reduce exposure from unauthenticated attackers.

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:>= 16.1, <= 21.1.1= 22.0.0

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify WhatsUp Gold installation and version
    Open Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Ipswitch\WhatsUp Gold\ or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Ipswitch\WhatsUp Gold\. Look for the 'Version' or 'ProductVersion' string value.
    Affected if The installed version falls within 16.1 through 21.1.1 or equals 22.0.0 exactly.
  2. Check alternate version location
    If registry keys are not found, locate the WhatsUp Gold installation directory (commonly C:\Program Files\Ipswitch\WhatsUp Gold\ or C:\Program Files (x86)\Ipswitch\WhatsUp Gold\) and right-click on WhatsUpGold.exe to view Properties > Details for the File Version.
    Affected if The file version matches the affected ranges listed above.
  3. Verify management interface accessibility
    From an external system or using a browser, attempt to access the WhatsUp Gold web interface at the default ports (typically 80 or 443) or the configured management URL. Confirm whether the login page loads without authentication.
    Affected if The management interface is reachable from untrusted networks without requiring credentials.
  4. Determine if serial number exposure is observable
    Since the attack vector is unspecified, monitor access logs for the WhatsUp Gold web service for unusual unauthenticated requests, particularly to endpoints that might reveal licensing or configuration information.
    Affected if Unauthenticated requests to the web interface are being logged from untrusted sources.

A user is affected if their installed WhatsUp Gold version is between 16.1 and 21.1.1 inclusive, or exactly 22.0.0, and the management interface is exposed to untrusted networks.

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 a release after 21.1.1
Interim mitigation

Apply the vendor-provided security patch for this vulnerability. If immediate patching is not feasible, restrict network access to the WhatsUp Gold management interface to trusted networks or VPN connections to reduce exposure from unauthenticated attackers.

Recommended fix Moderate confidence

WhatsUp Gold 22.1.0 or later

  1. 1. Back up your current WhatsUp Gold configuration and database before proceeding with any upgrade.
  2. 2. Download the latest WhatsUp Gold version (22.1.0 or later) from the Progress Customer Portal or official download channels.
  3. 3. Review the upgrade documentation for your current version to ensure compatibility.
  4. 4. Run the installer for the new version, following the standard upgrade procedure.
  5. 5. After upgrade, verify that the vulnerability is resolved by confirming the serial number is no longer exposed without authentication.
  6. 6. Test critical monitoring functions to ensure normal operation.
Caveat Review release notes for any feature changes between your current version and 22.x; standard upgrade risks apply including potential configuration migration needs

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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