dbcve.org
OxauthApplication · Gluu

CVE-2022-36663

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to 4.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Gluu Oxauth before v4.4.1 allows attackers to execute blind SSRF (Server-Side Request Forgery) attacks via a crafted request_uri parameter.

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

Gluu Oxauth before v4.4.1 contains a blind SSRF vulnerability where the request_uri parameter is not properly validated, allowing attackers to force the server to make arbitrary HTTP requests to internal or external resources without receiving the response directly.

MitigationUpgrade to Gluu Oxauth v4.4.1 or later to remediate this vulnerability.

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
OxauthApplication
Affected:< 4.4.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify if Gluu Oxauth is deployed
    Check for the presence of the oxauth.war file in the application server deployment directory (such as /opt/gluu/jetty/oxauth/webapps/ or similar), or check if the Oxauth service is running.
    Affected if Gluu Oxauth is deployed and the oxauth.war file exists on the system.
  2. Determine the installed Oxauth version
    Locate the oxauth.war file and check its version. Common methods include: inspecting the filename if versioned, checking the MANIFEST.MF file inside the WAR archive, or accessing the Gluu Oxauth version endpoint if available (such as /oxauth/version). Compare the version number to the affected range.
    Affected if The installed version is any version prior to 4.4.1.
  3. Check if the request_uri parameter feature is enabled
    Examine the Gluu Oxauth configuration (typically stored in gluuAppliance or oxauth-config.xml) for settings related to request URI validation or OpenID Connect request object handling. Look for configuration keys related to request_uri, request_parameter, or request_object.
    Affected if The request_uri parameter handling is enabled in the Oxauth configuration and the server version is below 4.4.1.
  4. Review access logs for suspicious request_uri usage
    Search the Oxauth access logs (typically found in /opt/gluu/jetty/oxauth/logs/ or equivalent) for incoming requests containing the request_uri parameter. Look for requests to internal IP addresses (such as 127.0.0.1, 10.x.x.x, 192.168.x.x) or internal hostnames in the URI.
    Affected if There are logged requests with request_uri parameters pointing to internal resources, indicating potential exploitation attempts.

A user is affected if Gluu Oxauth is installed with a version lower than 4.4.1 and the request_uri parameter feature is accessible to unauthenticated or authenticated users.

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 4.4.1 or later
Fixed in 4.4.1
Interim mitigation

Upgrade to Gluu Oxauth v4.4.1 or later to remediate this vulnerability.

Recommended fix High confidence

Oxauth 4.4.1 or later

  1. Verify current Oxauth version using system inventory or package manager
  2. Review Oxauth 4.4.1 release notes for migration requirements and breaking changes
  3. Backup current Oxauth configuration and database
  4. Upgrade Oxauth to version 4.4.1 or later using the Gluu package manager or deployment method
  5. Verify the upgrade was successful by checking the Oxauth version
  6. Test that the request_uri parameter is now properly validated and blocks external URLs
  7. Confirm normal authentication flows still function correctly
Caveat Review Gluu 4.4.1 release notes for any configuration or migration changes before upgrading

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

Fix this in Oxauth Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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