Open Redirect
The advisory, in context
Impact
In some situations, it is possible to have open redirects where users can be redirected from your site to any other site using a specially crafted URL.
This is only the case for installations where the default Hostname Identification is used and the environment uses tenants that have force_https set to true (default: false)
Patches
Version 5.7.2 contains the relevant patches to fix this bug. Stripping the URL from special characters to prevent specially crafted URL's from being redirected to.
Workarounds
There is a simple way to work around the security issue
- Set the
force_httpsto every tenant tofalse
References
https://nvd.nist.gov/vuln/detail/CVE-2018-11784
For more information
If you have any questions or comments about this advisory:
- Contact us in Discord: https://tenancy.dev/chat
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
From 5.6.0 before 5.7.2
Fixed in 5.7.2
7 explicitly affected versions
5.6.0, 5.6.1, 5.6.2, 5.6.3, 5.6.4, 5.7.0, 5.7.1
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "5.6.0"
},
{
"fixed": "5.7.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.6.0",
"5.6.1",
"5.6.2",
"5.6.3",
"5.6.4",
"5.7.0",
"5.7.1"
]
}References
- https://github.com/tenancy/multi-tenant/security/advisories/GHSA-4r8q-gv9j-3xx6
- https://nvd.nist.gov/vuln/detail/CVE-2021-32645
- https://github.com/tenancy/multi-tenant/commit/9c837a21bccce9bcaeb90033ef200d84f0d9e164
- https://packagist.org/packages/hyn/multi-tenant
- https://webmasters.googleblog.com/2009/01/open-redirect-urls-is-your-site-being.html