CVE-2022-29847
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 Progress Ipswitch WhatsUp Gold 21.0.0 through 21.1.1, and 22.0.0, it is possible for an unauthenticated attacker to invoke an API transaction that would allow them to relay encrypted WhatsUp Gold user credentials to an arbitrary host.
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 confidenceThis is an authentication bypass/credential relay vulnerability in Progress Ipswitch WhatsUp Gold versions 21.0.0-21.1.1 and 22.0.0. An unauthenticated attacker can invoke a specific API transaction that forwards encrypted WhatsUp Gold user credentials to a host of their choosing, effectively allowing credential relay attacks.
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>= 21.0.0, <= 21.1.1= 22.0.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed WhatsUp Gold versionLocate the WhatsUp Gold installation and check the version information, typically available in the application UI under Help > About, or in the installation directory documentation. Compare your version number against the affected ranges: 21.0.0 through 21.1.1, or exactly 22.0.0.Affected if The installed version falls within 21.0.0 to 21.1.1 (inclusive) or is exactly 22.0.0.
-
Determine if API endpoints are network-accessibleIdentify the network interface(s) WhatsUp Gold is listening on. Check the web server configuration or firewall rules to determine whether the WhatsUp Gold web interface/API is accessible from untrusted network segments or the internet.Affected if The WhatsUp Gold web/API interface is exposed to untrusted networks without additional access controls.
-
Verify if the credential forwarding API is exposedInspect the available API endpoints exposed by WhatsUp Gold. The vulnerability involves a specific API transaction that forwards encrypted user credentials to an attacker-controlled host. Determine if unauthenticated access to such credential-related API endpoints is permitted.Affected if Unauthenticated API endpoints related to credential handling or forwarding are accessible without authentication.
-
Check for unusual outbound API connectionsReview network logs or proxy logs for any unexpected outbound connections from the WhatsUp Gold server to unknown external hosts, particularly connections originating from the API service that may indicate credential relay activity.Affected if Outbound API connections to untrusted or unexpected external hosts are observed originating from the WhatsUp Gold server.
A user is affected if their WhatsUp Gold installation version is 21.0.0-21.1.1 or 22.0.0 AND the API interface is accessible to unauthenticated attackers on the network.
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.
From vendor dataApply available vendor patches for WhatsUp Gold. If no patch is available, restrict network access to the WhatsUp Gold API endpoints from untrusted sources and implement additional authentication layers.
- 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-2022-29847 — 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-2022-29847 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