CVE-2022-46784
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 · uneditedSquaredUp Dashboard Server SCOM edition before 5.7.1 GA allows open redirection. (The issue was originally found in 5.5.1 GA.)
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 confidenceSquaredUp Dashboard Server SCOM edition before 5.7.1 GA contains an open redirection vulnerability. The application accepts user-supplied input to determine redirect destinations without proper validation, allowing attackers to craft malicious URLs that redirect victims to arbitrary external sites. This can facilitate phishing attacks by leveraging the trusted domain of the vulnerable server.
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< 5.7.1.9085CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 SquaredUp Dashboard Server versionAccess the SquaredUp Dashboard Server web interface and navigate to the About or Settings page, or check the installation directory for version information typically found in a version file or manifestAffected if The displayed version number is less than 5.7.1.9085 (or any version before 5.7.1 GA)
-
Check product editionConfirm that the installed product is SquaredUp Dashboard Server SCOM edition specifically, as the vulnerability affects this editionAffected if The product is SquaredUp Dashboard Server SCOM edition and the version is below 5.7.1.9085
-
Verify redirect functionality exposureReview application logs or network traffic for any redirect parameters (commonly URL, redirect, or destination parameters) being passed in URLs to the SquaredUp serverAffected if Redirect parameters are observed in use and the version is below 5.7.1.9085
You are affected if SquaredUp Dashboard Server SCOM edition is installed with a version number lower than 5.7.1.9085, as the open redirection vulnerability exists in versions before 5.7.1 GA.
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 · scoped5.7.1.9085
Upgrade to SquaredUp Dashboard Server SCOM edition 5.7.1 GA or later. If immediate patching is not feasible, implement strict validation of redirect URL parameters to ensure only trusted, internal destinations are permitted.
5.7.1 GA (version 5.7.1.9085 or later)
- Backup the current SquaredUp Dashboard Server installation and database
- Download SquaredUp Dashboard Server version 5.7.1 GA (5.7.1.9085 or later) from the official vendor site
- Apply the upgrade following standard SquaredUp upgrade procedures
- Verify the upgrade was successful by accessing the Dashboard Server web interface
- Test that the open redirect vulnerability is no longer present by attempting to manipulate redirect parameters
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46784 — 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-46784 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