dbcve.org
SysaidApplication

CVE-2022-22797

MEDIUM · 6.1 CVSS v3.1 Published 2022-05-12
Fix available
A fix is available. Upgrade to 22.1.50 / 22.1.64 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Sysaid – sysaid Open Redirect - An Attacker can change the redirect link at the parameter "redirectURL" from"GET" request from the url location: /CommunitySSORedirect.jsp?redirectURL=https://google.com. Unvalidated redirects and forwards are possible when a web application accepts untrusted input that could cause the web application to redirect the request to a URL contained within untrusted input. By modifying untrusted URL input to a malicious site, an attacker may successfully launch a phishing scam and steal user credentials.

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 confidence

Sysaid contains an open redirect vulnerability in the /CommunitySSORedirect.jsp endpoint. The 'redirectURL' GET parameter accepts untrusted input without validation, allowing attackers to specify arbitrary external URLs that the application will redirect users to, facilitating phishing attacks.

MitigationImplement strict allowlist-based URL validation for the redirectURL parameter, or restrict redirects to relative paths within the same domain. Reject any redirect URLs pointing to external domains or unauthorized destinations.

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
SysaidApplication
Affected:< 22.1.50< 22.1.64

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Sysaid installation
    Locate Sysaid installation directory or identify running Sysaid service on the system
    Affected if Sysaid is not installed or not present on the system
  2. Identify Sysaid version
    Check the application's version information through the admin interface, version file, or installation logs
    Affected if Unable to determine the installed version
  3. Compare version to affected ranges
    Verify if the installed version is less than 22.1.50 or falls between 22.1.50 and 22.1.64 (exclusive of 22.1.64)
    Affected if Installed version is < 22.1.50 or (>= 22.1.50 AND < 22.1.64)
  4. Verify vulnerable endpoint exists
    Check if /CommunitySSORedirect.jsp exists in the web application's deployment directory
    Affected if The endpoint file exists in the deployment

The environment is affected if Sysaid is installed with a version less than 22.1.64 AND the CommunitySSORedirect.jsp endpoint is present.

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 22.1.50 / 22.1.64 or later
Fixed in 22.1.5022.1.64
Interim mitigation

Implement strict allowlist-based URL validation for the redirectURL parameter, or restrict redirects to relative paths within the same domain. Reject any redirect URLs pointing to external domains or unauthorized destinations.

Recommended fix Moderate confidence

Sysaid 22.1.64 or later

  1. Identify the current Sysaid installation version
  2. If running a version lower than 22.1.50 or 22.1.64, download the latest Sysaid version from the official vendor
  3. Review the Sysaid release notes for version 22.1.50 or 22.1.64 for security fixes related to open redirect
  4. Upgrade the Sysaid installation to version 22.1.64 or later
  5. After upgrade, verify the /CommunitySSORedirect.jsp endpoint now validates the redirectURL parameter and rejects malicious external URLs
  6. Test that legitimate redirect URLs within the application still function correctly
Caveat Review release notes for any breaking changes between current version and 22.1.64; standard upgrade testing recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sysaid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

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