CVE-2023-6595
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 WhatsUp Gold versions released before 2023.1, an API endpoint was found to be missing an authentication mechanism. It is possible for an unauthenticated attacker to enumerate ancillary credential information stored within WhatsUp Gold.
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 confidenceAn API endpoint in WhatsUp Gold versions prior to 2023.1 lacks authentication enforcement, permitting unauthenticated remote attackers to enumerate credential information stored within the application.
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< 23.1.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify WhatsUp Gold versionLocate the installed WhatsUp Gold version through the application admin interface, installed programs list, or product documentation. The version is typically visible in the product header, About section, or installation directory.Affected if The installed version is any release prior to 23.1.0
-
Verify API endpoint accessibilityAttempt to access the affected API endpoint without providing authentication credentials. This can be done using a web browser, curl, or similar HTTP client tool to send a request to the suspected endpoint.Affected if The API endpoint responds with data or accepts requests without requiring valid authentication tokens or session credentials
-
Test for credential enumerationUse the unauthenticated API endpoint to query for stored credential information. Send requests that would normally require authentication to enumerate usernames, passwords, or other stored credentials within the application.Affected if Credential data or credential-related information is returned through the API without authentication
The environment is affected if WhatsUp Gold version is below 23.1.0 and the API endpoint responds to unauthenticated requests allowing credential enumeration.
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.
dbcve · scoped23.1.0
Upgrade WhatsUp Gold to version 2023.1 or later which includes proper authentication for the affected API endpoint.
WhatsUp Gold 23.1.0 (2023.1) or later
- 1. Check the current WhatsUp Gold version by logging into the application or checking the About section in the console.
- 2. Navigate to the Progress customer portal or official download page to obtain WhatsUp Gold version 23.1.0 or later.
- 3. Follow the standard WhatsUp Gold upgrade procedure, ensuring you have a complete backup of the current configuration and database.
- 4. Apply the upgrade following Progress documentation for your specific deployment method (standalone or distributed).
- 5. After upgrade completion, verify that the API endpoint now requires authentication by attempting an unauthenticated request - it should be rejected.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6595 — 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-2023-6595 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