$ cscli hub list -o raw
crowdsecurity/sshd is tainted by scenarios:crowdsecurity/ssh-time-based-bf
crowdsecurity/linux is tainted by collections:crowdsecurity/sshd
crowdsecurity/linux is tainted by collections:crowdsecurity/whitelist-good-actors
crowdsecurity/whitelist-good-actors is tainted by postoverflows:crowdsecurity/rdns
Loaded: 166 parsers, 12 postoverflows, 781 scenarios, 9 contexts, 5 appsec-configs, 211 appsec-rules, 164 collections
Unmanaged items: 5 local, 7 tainted
name,status,version,description,type
crowdsecurity/apache2-logs,enabled,1.5,Parse Apache2 access and error logs,parsers
crowdsecurity/dateparse-enrich,enabled,0.2,,parsers
crowdsecurity/geoip-enrich,enabled,0.5,"Populate event with geoloc info : as, country, coords, source range.",parsers
crowdsecurity/http-logs,enabled,1.3,"Parse more Specifically HTTP logs, such as HTTP Code, HTTP path, HTTP args and if its a static ressource",parsers
crowdsecurity/mariadb-logs,enabled,0.4,Parse MariaDB logs,parsers
crowdsecurity/postfix-logs,enabled,0.9,Parse postfix logs,parsers
crowdsecurity/postscreen-logs,enabled,0.3,Parse postscreen logs,parsers
crowdsecurity/public-dns-allowlist,enabled,0.1,Allow events from public DNS servers,parsers
crowdsecurity/sshd-logs,enabled,3.1,Parse openSSH logs,parsers
crowdsecurity/sshd-success-logs,enabled,0.1,Parse successful ssh logins,parsers
crowdsecurity/syslog-logs,enabled,1.0,,parsers
crowdsecurity/whitelists,enabled,0.3,Whitelist events from private ipv4 addresses,parsers
fulljackz/pureftpd-logs,enabled,0.1,Parse pureftpd logs for bruteforce attempts,parsers
vizus/customer-whitelist,"enabled,local",,,parsers
vizus/system-whitelist,"enabled,local",,,parsers
vizus/web-auth-logs,"enabled,local",,,parsers
crowdsecurity/cdn-whitelist,enabled,0.5,Whitelist CDN providers,postoverflows
crowdsecurity/google-special-crawlers-whitelist,enabled,0.1,"Whitelist events from Google special crawlers (e.g. Google-InspectionTool, GoogleOther)",postoverflows
crowdsecurity/rdns,"enabled,tainted",?,Lookup the DNS associated to the source IP only for overflows,postoverflows
crowdsecurity/seo-bots-whitelist,enabled,0.5,Whitelist good search engine crawlers,postoverflows
crowdsecurity/apache_log4j2_cve-2021-44228,enabled,0.7,Detect cve-2021-44228 exploitation attempts,scenarios
crowdsecurity/CVE-2017-9841,enabled,0.2,Detect CVE-2017-9841 exploits,scenarios
crowdsecurity/CVE-2019-18935,enabled,0.2,Detect Telerik CVE-2019-18935 exploitation attempts,scenarios
crowdsecurity/CVE-2022-26134,enabled,0.4,Confluence - RCE (CVE-2022-26134),scenarios
crowdsecurity/CVE-2022-35914,enabled,0.2,Detect CVE-2022-35914 exploits,scenarios
crowdsecurity/CVE-2022-37042,enabled,0.2,Detect CVE-2022-37042 exploits,scenarios
crowdsecurity/CVE-2022-40684,enabled,0.3,Detect cve-2022-40684 exploitation attempts,scenarios
crowdsecurity/CVE-2022-41082,enabled,0.4,Detect CVE-2022-41082 exploits,scenarios
crowdsecurity/CVE-2022-41697,enabled,0.2,Detect CVE-2022-41697 enumeration,scenarios
crowdsecurity/CVE-2022-42889,enabled,0.3,Detect CVE-2022-42889 exploits (Text4Shell),scenarios
crowdsecurity/CVE-2022-44877,enabled,0.3,Detect CVE-2022-44877 exploits,scenarios
crowdsecurity/CVE-2022-46169,enabled,0.2,Detect CVE-2022-46169 brute forcing,scenarios
crowdsecurity/CVE-2023-22515,enabled,0.1,Detect CVE-2023-22515 exploitation,scenarios
crowdsecurity/CVE-2023-22518,enabled,0.3,Detect CVE-2023-22518 exploits,scenarios
crowdsecurity/CVE-2023-49103,enabled,0.3,Detect owncloud CVE-2023-49103 exploitation attempts,scenarios
crowdsecurity/CVE-2024-0012,enabled,0.1,Detect CVE-2024-0012 exploitation attempts,scenarios
crowdsecurity/CVE-2024-38475,enabled,0.1,Detect CVE-2024-38475 exploitation attempts,scenarios
crowdsecurity/CVE-2024-9474,enabled,0.1,Detect CVE-2024-9474 exploitation attempts,scenarios
crowdsecurity/f5-big-ip-cve-2020-5902,enabled,0.3,F5 BIG-IP TMUI - RCE (CVE-2020-5902),scenarios
crowdsecurity/fortinet-cve-2018-13379,enabled,0.4,Detect cve-2018-13379 exploitation attempts,scenarios
crowdsecurity/grafana-cve-2021-43798,enabled,0.3,Grafana - Arbitrary File Read (CVE-2021-43798),scenarios
crowdsecurity/http-admin-interface-probing,enabled,0.5,Detect generic HTTP admin interface probing,scenarios
crowdsecurity/http-backdoors-attempts,enabled,0.6,Detect attempt to common backdoors,scenarios
crowdsecurity/http-bad-user-agent,enabled,1.2,Detect usage of bad User Agent,scenarios
crowdsecurity/http-bf-wordpress_bf,enabled,0.7,Detect WordPress bruteforce on admin interface,scenarios
crowdsecurity/http-crawl-non_statics,enabled,0.7,Detect aggressive crawl on non static resources,scenarios
crowdsecurity/http-cve-2021-41773,enabled,0.3,Apache - Path Traversal (CVE-2021-41773),scenarios
crowdsecurity/http-cve-2021-42013,enabled,0.3,Apache - Path Traversal (CVE-2021-42013),scenarios
crowdsecurity/http-cve-probing,enabled,0.6,Detect generic HTTP cve probing,scenarios
crowdsecurity/http-generic-bf,enabled,0.9,Detect generic http brute force,scenarios
crowdsecurity/http-generic-test,enabled,0.2,Crowdsec Generic Test Scenario: basic HTTP trigger,scenarios
crowdsecurity/http-open-proxy,enabled,0.5,Detect scan for open proxy,scenarios
crowdsecurity/http-path-traversal-probing,enabled,0.4,Detect path traversal attempt,scenarios
crowdsecurity/http-probing,enabled,0.4,Detect site scanning/probing from a single ip,scenarios
crowdsecurity/http-sap-interface-probing,enabled,0.1,Detect generic HTTP SAP interface probing,scenarios
crowdsecurity/http-sensitive-files,enabled,0.4,"Detect attempt to access to sensitive files (.log, .db ..) or folders (.git)",scenarios
crowdsecurity/http-sqli-probing,enabled,0.4,A scenario that detects SQL injection probing with minimal false positives,scenarios
crowdsecurity/http-technology-probing,enabled,0.1,Detect HTTP technology/vendor probing,scenarios
crowdsecurity/http-wordpress-scan,enabled,0.4,Detect exploitation attempts against common WordPress endpoints,scenarios
crowdsecurity/http-wordpress_user-enum,enabled,0.3,Detect WordPress probing: authors enumeration,scenarios
crowdsecurity/http-wordpress_wpconfig,enabled,0.3,Detect WordPress probing: variations around wp-config.php by wpscan,scenarios
crowdsecurity/http-xss-probing,enabled,0.4,A scenario that detects XSS probing with minimal false positives,scenarios
crowdsecurity/jira_cve-2021-26086,enabled,0.4,Detect Atlassian Jira CVE-2021-26086 exploitation attempts,scenarios
crowdsecurity/mariadb-bf,enabled,0.2,Detect mariadb bruteforce,scenarios
crowdsecurity/netgear_rce,enabled,0.4,Detect Netgear RCE DGN1000/DGN220 exploitation attempts,scenarios
crowdsecurity/postfix-helo-rejected,enabled,0.1,Detect HELO rejections,scenarios
crowdsecurity/postfix-non-smtp-command,enabled,0.1,Detect scanning of postfix service through non-SMTP commands,scenarios
crowdsecurity/postfix-relay-denied,enabled,0.1,Detect multiple open relay attempts,scenarios
crowdsecurity/postfix-spam,enabled,0.4,Detect spammers,scenarios
crowdsecurity/pulse-secure-sslvpn-cve-2019-11510,enabled,0.4,Detect cve-2019-11510 exploitation attempts,scenarios
crowdsecurity/spring4shell_cve-2022-22965,enabled,0.3,Detect cve-2022-22965 probing,scenarios
crowdsecurity/ssh-bf,enabled,0.3,Detect ssh bruteforce,scenarios
crowdsecurity/ssh-cve-2024-6387,enabled,0.2,Detect exploitation attempt of CVE-2024-6387,scenarios
crowdsecurity/ssh-generic-test,enabled,0.2,Crowdsec Generic Test Scenario: SSH brute force trigger,scenarios
crowdsecurity/ssh-refused-conn,enabled,0.1,Detect sshd refused connections,scenarios
crowdsecurity/ssh-slow-bf,enabled,0.4,Detect slow ssh bruteforce,scenarios
crowdsecurity/ssh-time-based-bf,"enabled,tainted",?,Detect time-based ssh bruteforce attempts that evade rate limiting (with false positive reduction),scenarios
crowdsecurity/thinkphp-cve-2018-20062,enabled,0.7,Detect ThinkPHP CVE-2018-20062 exploitation attempts,scenarios
crowdsecurity/vmware-cve-2022-22954,enabled,0.3,Detect Vmware CVE-2022-22954 exploitation attempts,scenarios
crowdsecurity/vmware-vcenter-vmsa-2021-0027,enabled,0.3,Detect VMSA-2021-0027 exploitation attempts,scenarios
fulljackz/pureftpd-bf,enabled,0.2,Detect pureftpd bruteforce,scenarios
ltsich/http-w00tw00t,enabled,0.3,detect w00tw00t,scenarios
vizus/web-auth-bf,"enabled,local",,,scenarios
crowdsecurity/bf_base,enabled,0.1,,contexts
crowdsecurity/http_base,enabled,0.3,,contexts
crowdsecurity/apache2,enabled,0.2,apache2 support : parser and generic http scenarios,collections
crowdsecurity/base-http-scenarios,enabled,1.4,http common : scanners detection,collections
crowdsecurity/http-cve,enabled,3.0,Detect CVE exploitation in http logs,collections
crowdsecurity/linux,"enabled,tainted",0.4,core linux support : syslog+geoip+ssh,collections
crowdsecurity/mariadb,enabled,0.2,mariadb support : logs and brute-force scenarios,collections
crowdsecurity/postfix,enabled,0.5,postfix support : parser and spammer detection,collections
crowdsecurity/sshd,"enabled,tainted",0.9,sshd support : parser and brute-force detection,collections
crowdsecurity/whitelist-good-actors,"enabled,tainted",0.4,Good actors whitelists,collections
crowdsecurity/wordpress,enabled,0.6,wordpress: Bruteforce protection and config probing,collections
fulljackz/pureftpd,enabled,0.2,Pureftpd support : parser for brute force detection on Pureftpd,collections
vizus-web.yaml,"enabled,local",,,collections
What happened?
CrowdSec running as our central LAPI server continuously consumes memory until it reaches the configured cgroup memory limit and is killed.
Immediately after restart, CrowdSec uses approximately 180–200 MB RSS:
Memory then continuously grows. Before adding a cgroup limit, CrowdSec eventually consumed almost all available memory:
The server has 19 GiB RAM, so this caused severe memory pressure and an OOM situation.
We added:
and disabled swapping for the CrowdSec cgroup.
The limit works, but CrowdSec now reaches 4 GB approximately every 25–40 minutes, gets killed with SIGKILL, and is restarted by systemd. The cycle repeats continuously.
Example:
This only happens on the central CrowdSec/LAPI server. Approximately 32 remote CrowdSec agents connected to this server do not exhibit abnormal memory growth.
CrowdSec version:
The LAPI uses MariaDB/MySQL as its database backend.
What did you expect to happen?
CrowdSec memory usage should remain reasonably stable during normal operation.
The central LAPI should be able to run continuously without growing from approximately 190 MB to several GB and eventually being killed by the cgroup OOM mechanism.
How can we reproduce it (as minimally and precisely as possible)?
Our setup is:
level: aggregatedRelevant database configuration:
After:
memory usage starts at approximately 190 MB:
and continuously increases until the process reaches the 4 GB cgroup limit, usually within 25–40 minutes.
The behavior then repeats after every automatic restart.
Anything else we need to know?
We initially suspected CAPI/community decisions because the LAPI had approximately:
We completely disabled CAPI/community/blocklist pulling:
This did not solve the problem.
With CAPI/community sources disabled, CrowdSec still grew to:
Restarting CrowdSec immediately returned memory usage to:
Therefore, the leak does not appear to be caused by Community Blocklist/CAPI decisions.
We also tested CrowdSec 1.7.7. The memory growth was still present and that version additionally caused significantly higher CPU usage, so we returned to 1.7.8.
We also tried 1.6.6, but it was incompatible with our currently installed Hub scenarios/parsers.
The same CrowdSec setup is used on approximately 32 remote agents, none of which exhibit this memory growth. The issue appears to be specific to the server acting as the central LAPI.
Our current workaround is
MemoryMax=4G, no swap for the CrowdSec cgroup, and automatic restart after CrowdSec is killed.Crowdsec version
Details
OS version
Details
Enabled collections and parsers
Details
Acquisition config
Details
Config show
Details
Prometheus metrics
Details
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.
Details