Closed gdlwolf closed 1 week ago
@gdlwolf: Thanks for opening an issue, it is currently awaiting triage.
In the meantime, you can:
This is intentionally how the appsec feature is designed.
So when an appsec rule is triggered 2 things happen:
If the user triggers 2 unique appsec rules then it would trigger the scenario as they are trying different things to your server.
However if you want to block them after the first try you can simply edit this scenario on your server and change capacity
to 0.
(We don't recommend banning an IP address after the first appsec trigger as with any rule system there always a chance of false positive and you don't want to risk completely blocking yourself from your own server)
The CVE you point out happens because we have a trigger scenario and a vpatch rule for it. We don't have a trigger scenario for env access but we do have https://app.crowdsec.net/hub/author/crowdsecurity/configurations/http-sensitive-files which detects crawling.
Thank you very much.
What happened?
When using CrowdSec with AppSec enabled, I noticed that scenarios like 'crowdsecurity/vpatch-env-access' and other vpatch-related scenarios successfully detect and log alerts (visible in 'cscli alerts list'), but these detections do not result in the offending IPs being added to the iptables ipset by crowdsec-firewall-bouncer-iptables.
However, other scenarios like 'crowdsecurity/CVE-2017-9841' work as expected, with detected IPs being properly added to the iptables ipset for blocking.
What did you expect to happen?
I expected all detected malicious IPs, including those from vpatch scenarios, to be added to the iptables ipset by the bouncer, similar to how other scenarios like CVE-2017-9841 are handled.
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
No response
Crowdsec version
OS version
Enabled collections and parsers
Acquisition config
Config show
Prometheus metrics
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.