CVE-2022-29848
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 17.0.0 through 21.1.1, and 22.0.0, it is possible for an authenticated user to invoke an API transaction that would allow them to read sensitive operating-system attributes from a host that is accessible by the WhatsUp Gold system.
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 confidenceIpswitch WhatsUp Gold versions 17.0.0 through 21.1.1 and 22.0.0 contain an API endpoint that allows authenticated users to read sensitive operating-system attributes from hosts monitored by the WhatsUp Gold system. The vulnerability requires valid user credentials but permits unauthorized disclosure of system information that should not be accessible to standard users.
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>= 17.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check installed WhatsUp Gold versionLocate the WhatsUp Gold installation and identify the version number. This is typically found in the application GUI under Help > About, or in the installation directory documentation. Compare the version against the affected range: 17.0.0 through 21.1.1 and version 22.0.0.Affected if The installed version falls within 17.0.0 to 21.1.1 inclusive, or is exactly 22.0.0.
-
Verify API functionality is enabledConfirm that the WhatsUp Gold web interface and API services are running and accessible. The vulnerable API endpoint is part of the standard WhatsUp Gold web application.Affected if The WhatsUp Gold web interface and API are accessible on the network.
-
Confirm user authentication is configuredCheck that user accounts exist in WhatsUp Gold that can authenticate to the web interface or API. The vulnerability requires valid user credentials to exploit.Affected if There are active user accounts that can authenticate to WhatsUp Gold.
-
Assess network accessibility of the API endpointDetermine if the WhatsUp Gold web/API interface is reachable from network segments beyond the trusted administration network. The API endpoint can be accessed remotely if the service is exposed.Affected if The WhatsUp Gold API is accessible from network segments outside of trusted administrative hosts.
You are affected if your WhatsUp Gold version is between 17.0.0 and 21.1.1 inclusive or exactly 22.0.0, and the API interface is accessible with valid user credentials.
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 dataUpgrade WhatsUp Gold to version 22.0.1 or later which contains the security fix. Alternatively, restrict API access to only trusted users and implement network segmentation to limit which hosts the WhatsUp Gold system can access.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29848 — 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-29848 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