Josephsurin

**Name of the Vulnerable Software and Affected Versions** Rails versions prior to 7.0.5.1 Rails versions prior to 6.1.7.4 **Description** The `redirect to` method in Rails allows provided values to contain characters which are not legal in an HTTP header value. This results in the potential for downstream services which enforce RFC compliance on HTTP response headers to remove the assigned Location header. This issue introduces the potential for a Cross-site-scripting (XSS) payload to be delivered on the now static redirection page, requiring user interaction and a Rails app configured to allow redirects to external hosts. **Recommendations** For Rails versions prior to 7.0.5.1, update to version 7.0.5.1 to resolve the issue. For Rails versions prior to 6.1.7.4, update to version 6.1.7.4 to resolve the issue. As a temporary workaround, avoid providing user-supplied URLs with arbitrary schemes to the `redirect to` method.

**Name of the Vulnerable Software and Affected Versions** Django-SES versions prior to 3.5.0 **Description** The django ses library, a mail backend for Django using AWS Simple Email Service, has a flaw in the verification of signed requests from AWS. The `SESEventWebhookView` class is intended to handle email bounces, subscriptions, etc., but the verification of the signature allowed users to specify arbitrary public certificates. **Recommendations** For versions prior to 3.5.0, update to version 3.5.0 to resolve the issue. As a temporary workaround, consider restricting access to the `SESEventWebhookView` class until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Onedev versions prior to 7.9.12 **Description** Onedev is a self-hosted Git Server with CI/CD and Kanban. The algorithm used to generate access token and password reset keys was not cryptographically secure in versions prior to 7.9.12. Existing normal users, or everyone if self-registration is allowed, may exploit this to elevate their privilege and obtain administrator permission. **Recommendations** For versions prior to 7.9.12, upgrade to version 7.9.12 to address the issue. As a temporary workaround, consider restricting self-registration and closely monitoring user activities until the upgrade is applied. There are no known workarounds for this issue other than upgrading to the fixed version.