HexBrain

Nextcloud · Report #2110945

Memcached used as RateLimiter backend is no-op

Validstatus
mediumseverity
19upvotes
12 Nov 2023disclosed

Summary

Security advisory at https://github.com/nextcloud/security-advisories/security/advisories/GHSA-xmhp-7vr4-hp63

How it was found

Summary:

When Memcached is used as backend: https://github.com/nextcloud/server/blob/c705b8fcb3de7910e67cd2ed2d2b38653f58962a/lib/private/Server.php#L787-L799

The following code block is problematic: https://github.com/nextcloud/server/blob/90104bc1c448c6da2fd3e052fca75bb3fb261c87/lib/private/Memcache/Memcached.php#L135-L139

I guess we need to check the actual cache type and use the DB backend when Memcached is used?

Impact

Any action that partly resets any cache entry will wipe rate limit attempts and future bruteforce protection (with https://github.com/nextcloud/server/pull/39870 )

This report was disclosed publicly on HackerOne and belongs to its author and the program. See the original