mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,4 Tsd.
aktive Profile

#Crowdsec

0 Beiträge0 Beteiligte0 Beiträge heute

Aktualisierung: #Crowdsec und #Nextcloud
Seit der crowdsec-Version 1.5 sollten custom-yaml-Dateien unterhalb von "acquis.d" liegen => die bisherige Datei "nextcloud.yaml" wird ab sofort in /etc/crowdsec/acquis.d/setup.nextcloud.yaml erstellt:

touch /etc/crowdsec/acquis.d/setup.nextcloud.yaml
cat <<EOF >>/etc/crowdsec/acquis.d/setup.nextcloud.yaml
#Nextcloud by c-rieger.de
filenames:
- /var/log/nextcloud/nextcloud.log
labels:
type: Nextcloud
---
EOF

Ein schönes Wochenende wünscht das Team von Carsten Rieger IT-Services

c-rieger.de/nextcloud-installa

Carsten Rieger · Nextcloud Installationsanleitung - Carsten Rieger

Ich bin ja noch nicht zufrieden mit der Sicherheit auf meinem Raspberry. Ich habe den access.log mal auch mit in #Crowdsec eingebunden, bin mir aber nicht sicher, ob das bei einer Fediverse-Instanz so klug ist. Ich werde es mal beobachten.

wtf, I didn't know #crowdsec has a quota limit on the alerts on a free account. I knew you had limited blocklists, which I was fine with. But 500 alerts on a month? I blew through that on two days!

That is le suck, because I'm not shelling out $29/month for my hobby sites.

Just installed #crowdsec on my new VPS (Virtual Private Server) and happily noticed that all my 3 servers prefer #IPv6 to talk to crowdsec :)

How to install crowdsec on a RHEL10 (Red Hat Enterprise Linux) machine? Glad you ask! codeberg.org/jwildeboer/gists/

Does it work? Well, yes, in my opinion. 55k IP addresses blocked right now. On a VPS with 2GB RAM, no real performance impact.

Fortgeführter Thread

Sharing insights and taking swift action can collectively reduce the impact of these threats. This is your call to action for real-time threat intelligence and collaborative cybersecurity.

For more information, visit crowdsec.net

Want to stay ahead of the latest cyber threats? Get our weekly Threat Alert delivered straight to your inbox, along with critical threat updates and trending cybersecurity insights.

📩 Sign up now for exclusive access: contact.crowdsec.net/threat-al

🧵6/6

crowdsec.netCurated Threat Intelligence Powered by the Crowd | CrowdSecWe turn crowd-powered intelligence into tactical intelligence with actionable blocklists to maximize your SOC efficiency and reduce your costs.
Fortgeführter Thread

🛡️ How to protect your systems:
🔹 Patch: Patch your FortiWeb instance if it is publicly exposed; otherwise, remove outside access to the affected admin panel.
🔹 Preemptive blocking: Use Crowdsec CTI to block IPs exploiting CVE-2025-25257 👉 app.crowdsec.net/cti?q=cves%3A
🔹 Stay proactive: Install the Crowdsec Web Application Firewall to stay ahead of exploit attempts, with 100+ virtual patching rules available. 👉 doc.crowdsec.net/docs/next/app

🧵5/6

CrowdSec ConsoleCrowdSec Cyber Threat Intelligence | CrowdSec ConsoleLeverage Cyber Threat Intelligence (CTI) on CrowdSec Console to enhance your security strategies. Gain actionable insights to defend against emerging threats.
Fortgeführter Thread

📈 Trend analysis:
🔹 CrowdSec detected the first in-the-wild exploitation of this vulnerability on July 11th, shortly after we rolled out detection rules. Using our wayback tools, we were able to establish that there were no exploitation attempts before July 11th, confirming once again that public exploits are a key driver of vulnerability weaponization.
🔹 For CVE-2025-25257, CrowdSec has observed about 40 distinct IPs producing about 500 attack events in total. Most of these attacks occurred on Friday, July 11th, the day the exploit was publicized. The attacks on Friday were mainly due to a presumably coordinated attacker spinning up a bunch of machines on Scaleway cloud to use in a broad scanning campaign. Over the weekend, the exploit quickly lost popularity. This might be due to the fact that the exploit requires the Fabric Connector administrative interface to be publicly accessible, which is somewhat unlikely. While we cannot make predictions, CrowdSec expects exploitation signals to pick up slightly this week as vulnerability scanners start looking for vulnerable devices. However, we don’t expect the attacker volume for this vulnerability to reach that of other Fortinet-related CVEs.

🧵4/6

Fortgeführter Thread

🛠️ About the exploit:
🔹 The Fortinet FortiWeb Fabric Connector is an integration component designed to enhance application security by linking FortiWeb web application firewalls (WAFs) with other elements of the Fortinet Security Stack. It enables policy enforcement and automated threat response by leveraging intelligence gathered from FortiGate firewalls, FortiSandbox, FortiAnalyzer, and other “Fabric-enabled” devices. It is in some sense a glue product that holds an array of different Fortinet products together.
🔹 The vulnerability allows unauthenticated attackers to execute arbitrary SQL statements against the MySQL database connected to Fabric Connector. As this database runs as root per default, this attack can be chained to run arbitrary Python code on the affected machine, allowing attackers to further compromise the system. The vulnerability affects various FortiWeb versions from 7.0 to 7.6. As a workaround, the vendor recommends disabling the administrative interface to external visitors.

🧵3/6