CVE-2020-11052
Sorcery Project Sorcery vulnerability
In Sorcery before 0.15.0, there is a brute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired, protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout. This has been patched in 0.15.0.
Affected products
Sorcery. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Sorcery Project Sorcery runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7 · Patch
- github.com/Sorcery/sorcery/pull/235 · Patch
- github.com/Sorcery/sorcery/issues/231 · Third Party Advisory
- github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-11052
- cve.org/CVERecord?id=CVE-2020-11052
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.