Disclosed weakness · no CVE recorded

Obot trailing-slash redirects could send a trusted link to an attacker’s site

Obot · Obot Platform · MCP gateway

First documented disclosure · Review checkpoint

Summary

A crafted URL on an Obot host could redirect the browser to another host.

Severity and exploitation evidence

Medium · 4.7/10 · CVSS 3.1. Severity source.

Exploitation not established: The reviewed sources establish the weakness or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The redirect target used a decoded path after removing a trailing slash, allowing encoded leading slashes, backslashes or tabs to change its interpretation.

Conditions required

A victim follows an attacker-crafted link; no account or special configuration is required.

Potential impact

Trusted-looking Obot links can lead to phishing pages. The redirect alone does not expose sessions, credentials or Obot data.

Affected versions and configurations

>= 0.15.0, <= 0.28.1.

Fix and mitigation status

0.28.2 fixes this issue.

Practical next steps

Upgrade to 0.28.2 and inspect unexpected redirect destinations before entering credentials.

Operating lesson

Normalize and escape redirect paths so they remain on the intended origin.

Evidence and limits

The complete advisory was published November 20, after the November 19 release. The maintainer assigns the CVSS score. No CVE is assigned in the reviewed advisory. Tagged production code contains the named correction. The advisory distinguishes this location from two earlier Obot open-redirect advisories. No observed victim compromise is reported.

Sources