安全速报自动同步 · 保留上游原文

【中危】probo:开放重定向风险(GHSA-x7qq-m748-8p2c)

S
KHack 安全情报
2026/7/1 发布 · 1 阅读

安全情报快照 · 风险级别:中危 · CVSS:4.7 · CVE-2026-49820 · GHSA-x7qq-m748-8p2c

先看结论

probo存在开放重定向风险,< 0.204.0 受影响,建议升级至 0.204.0。

影响范围

生态 组件 受影响版本 首个修复版本
go go.probo.inc/probo < 0.204.0 0.204.0

处置建议

优先将 go.probo.inc/probo 升级至 0.204.0 或更高版本;升级前请结合业务依赖完成兼容性验证。

上游技术详情(原文)

Impact

Probo's saferedirect package validates redirect URLs used across authentication flows (OIDC, SAML, session transfer, OAuth connectors, and trust-center magic links). The validator only inspected the second character of relative paths, so a URL like /../\evil.com passed validation because the second character is .. Go's http.Redirect normalizes this path to /\evil.com before setting the Location header. Browsers can interpret the backslash as a host separator and redirect the user to an external domain (https://evil.com), bypassing the intended same-origin restriction. This enables open-redirect phishing: an attacker can craft a continue parameter (or embed a malicious URL in a session-transfer token) that appears to originate from a trusted Probo domain but redirects victims elsewhere.

Patches

Fixed in go.probo.inc/probo by normalizing relative paths with path.Clean before validation, rejecting backslashes (including
percent-encoded %5c) anywhere in the path, and re-checking the normalized result for protocol-relative and backslash prefixes.

Self-hosted deployments should upgrade to probod v0.194.1 or later.

SaaS deployments on getprobo.com are patched.

Workarounds

No practical workaround for self-hosted installations. Upgrade to the patched release.

来源与许可

本页自动同步 GitHub Advisory Database 的公开数据,并保留上游原文供核验;不宣称原创分析。数据许可:CC-BY-4.0。

评论

还没有评论,来说两句。