Skip to content

Open Redirect Vulnerability in DataHub (redirect_uri)

Moderate
david-leifker published GHSA-3p57-xxv6-6wqp May 19, 2026

Package

datahub-frontend

Affected versions

<=1.4.0.3

Patched versions

None

Description

Summary

An open redirect vulnerability has been identified in the DataHub frontend /authenticate endpoint that could allow attackers to redirect users to malicious external sites.

Vulnerability Details

Root Cause

The vulnerability exists in AuthenticationController.java (line 148) where the redirect_uri query parameter is passed directly to Results.redirect() without proper validation.

Attack Vector

When the redirect URI contains triple slashes (e.g., ///google.com), URL normalization causes browsers to interpret this as a fully qualified external URL (https://google.com), bypassing intended redirect restrictions.

Example Request:

GET /authenticate?redirect_uri=///google.com HTTP/2
Host: demo.datahub.com

Impact

Attackers can craft malicious links to redirect authenticated users to phishing sites or malicious domains.

Patches

A fix has been developed and is available in the following pull request:

Users should upgrade to the patched version once released.

Workarounds

Until the patch can be applied, consider the following temporary mitigations:

  1. Web Application Firewall (WAF): Block requests to /authenticate containing redirect_uri parameters with multiple leading slashes (// or more)
  2. Reverse Proxy Rules: Implement URL filtering at the reverse proxy level to reject malformed redirect parameters
  3. User Education: Warn users to verify URLs before clicking authentication links
  4. Network Monitoring: Monitor for suspicious redirect patterns in access logs

References

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

CVE ID

No known CVE

Weaknesses

No CWEs

Credits