Marek Sušický (@msusicky) profile picture

Cybersecurity, SWENG, opendata. Vše jsou striktně osobní názory.

Praha, Česká republika
Joined March 2010
Photo by Marek Sušický (@msusicky)Photo by Marek Sušický (@msusicky)Photo by Marek Sušický (@msusicky)Photo by Marek Sušický (@msusicky)Photo by Marek Sušický (@msusicky)Photo by Marek Sušický (@msusicky)Photo by Marek Sušický (@msusicky)Photo by Marek Sušický (@msusicky)Photo by Marek Sušický (@msusicky)Photo by Marek Sušický (@msusicky)
Marek Sušický retweeted
Stáhněte si XTB a začněte investovat
Link preview

1
7
1
139
2,365,679
Marek Sušický retweeted
Java4Shell: write once, RCE everywhere calif.io/java4shell
58
685
140
2,613
218,199
Máme v @sec4good objednanou verzi s Lora ;) Co vy?
Flipper One is Live on Kickstarter !!!!!!!!!!!!!!!!!!!!!!!! kickstarter.com/projects/fli…
1
302
Marek Sušický retweeted
Since the vulnerability has leaked: Calif discovered and reported Java4Shell (CVE-2026-114938). We're publishing technical details by 1 PM Pacific today, after Oracle releases a patch. Stay tuned!
19e1b44520669be6269a485a3f361de95e800e68cb6d880285f5d5f4b34bf10f
76
350
90
3,612
332,302
Marek Sušický retweeted
This is a big one. We found malicious JavaScript being served through Optimizely to some of the world's largest websites. 178 organisations affected, with everything from crypto theft and card skimming to iOS exploits. Zoom, BBC, CNN, HSBC, Salesforce, GitLab, KLM, IKEA, Equifax, Ledger. The list goes on... Full list in the post. blog.report-uri.com/worlds-l…
154
1,158
213
3,212
483,885
Tohle mi přijde jako špatný vtip. Kvůli alkoholu zakáz řízení, pak nehoda pod vlivem, stíhání kvůli zdraví zastaveno. Doufám, že se s pánem, až zase bude pít, na silnici nepotkám. (Že by vrátil ŘP nikde nepíší) novinky.cz/clanek/krimi-mili…
52
Rychlost je jen doporučení, plná čára není zeď, ono se nikomu nic nestane. Jenže to někdy nevyjde a stane se. Tresty zjevně neodrazují. Lituji pozůstalé.
Aktualně složky IZS stále zasahují u tragické dopravní nehody, ke které došlo v brzķých ranních hodinách na silnici I/50 ve směru od Bučovic. Řidič osobního auta předjížděl nakladní vozidlo a v protisměru se střetl s protijedoucím autem, jehož ridička na místě zemřela. #Jmk
1
112
Marek Sušický retweeted
*sshole is out if you run sshd on alpine, openwrt or any musl box with password auth on: update now official writeup: sshhole.com
86552c7e1e5d46882844cffabb44d454129ff22927f13797b151c9db4519d47d
188
890
446
5,448
1,574,783
Marek Sušický retweeted
Since the folks at ThreatBook developed both Artex and CyberStrikeAI, we figured we should contribute a bit to defending against and tracking AI agent attacks by sharing two feeds of instances running these agents on the public internet. Grab them if needed. Feeds: threatbook.io/hubfs/Feeds/AR… threatbook.io/hubfs/Feeds/CS…
6
63
5
276
28,011
Marek Sušický retweeted
The GRU hacked into Jared Kushner's iPhone. Dutch military intelligence (MIVD) then recruited a GRU spy who gave them access to the hacked phone. What MIVD discovered was that Kushner had access to two bank accounts --one Azerbaijani, the other Israeli --where Saudi Crown Prince Mohammed bin Salman and Emirati ruler Mohammed bin Zayed deposited money. It sounds like a slightly far-fetched episode of "Slow Horses," but it's real. And it proves just how eye-poppingly corrupt this administration was and continues to be as its "special envoy" decides the fate of tens of millions in Europe in the Middle East. Simply incredible reporting by Matthew Cole, drawn from his new book on Kushner. vanityfair.com/story/jared-k…
1,441
24,372
1,984
77,543
6,578,419
🚨 Oracle publicó hoy una alerta de seguridad para Java: CVE-2026-91403, CVSS 9.1. Está en JSSE (el TLS de Java) y es explotable por red sin credenciales. Versiones afectadas que lista: Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 y 27.0.1, y GraalVM. oracle.com/security-alerts/a…
43
584
185
2,463
270,049
Marek Sušický retweeted
While everyone’s patching PHP today, don't sleep on Node.js CVE-2026-111497 OOB write in the bundled Brotli decoder. Reachable via fetch(): a malicious server just replies Content-Encoding: br. Fixed in 26.12.1 / 24.22.1 / 22.23.4. Update.
6
29
4
141
16,479
Bude zajímat @NUKIB_CZ a @GOVCERT_CZ
Teamwork makes the dream work. The team and I @J4ck3LSyN @Archknight23 🚨 Heads-up for anyone running PHP: two critical RCE bugs, patch drops tomorrow. The PHP project has confirmed an emergency security release for two critical remote code execution vulnerabilities: CVE-2026-109618 and CVE-2026-109619, both rated CVSS v4.0 9.2. 📅 Patch lands Wednesday, Oct 21 at 14:00 UTC (9:00 AM Central). PHP has reserved the right to ship it earlier if details leak or exploitation shows up. PHP runs about 75% of the web, including WordPress, Drupal, Joomla, Laravel, Magento, and countless custom apps. If you operate a PHP server, this is your weekend-ruiner unless you act. Here's the part the big threat-intel shops aren't shouting about: No official technical details are public yet. But based on my own source-code analysis of php-src, my best assessment (moderate confidence, NOT officially confirmed) is that the vulnerable path is PHP's session.upload_progress / multipart form-data (rfc1867) handling: 🔹 Present since PHP 5.4 🔹 Enabled by default (the compiled-in default is On; the sample php.ini ships it commented out, so stock installs have it live) 🔹 Processes uploaded request data before any of your application code runs, so it's reachable pre-authentication on a default config That lines up exactly with the public breadcrumbs: "affects default installs," "every version since 5.x," "fires before user code." Treat it as a working hypothesis, not gospel. The official advisory supersedes all of this when it lands. ✅ What to do right now: 1. Inventory your PHP. Know every host and version (php -v). Anything on PHP 7.x or older won't get a fix, so plan to upgrade. 2. Apply the stopgap (best-intel, low-risk, reversible). In php.ini / .user.ini / .htaccess: session.upload_progress.enabled = Off Reload PHP-FPM or your web server. My analysis says this closes one of the two likely paths. 3. Clamp multipart uploads at the edge. The second likely path lives in the multipart parser itself, which runs for any multipart/form-data POST regardless of the setting above. If you've got a WAF or reverse proxy, tighten inspection or rate-limit multipart POSTs to endpoints that don't need uploads. This is the same network-layer mitigation the enterprise vendors are quietly deploying for their paying customers. 4. Patch the second it drops. Current stable: 8.5.11 / 8.4.26 / 8.3.35 / 8.2.34. If your hosting is managed, confirm your provider's timeline today. Why I'm posting this for free: A pre-patch mitigation shouldn't be a subscription perk. I'm a one man shop, and the orgs most likely to get burned in the gap between leak and patch are the small teams without an enterprise threat intel contract. The steps above cost nothing. Spend tonight reducing risk, not tomorrow doing incident response. I'll follow up once the official advisory publishes and confirm whether my root cause read was right. Stay patched. 🔒 #PHP #CyberSecurity #InfoSec #RCE #CVE #WordPress #Laravel #ThreatIntel #VulnerabilityManagement #AppSec
80
Marek Sušický retweeted
Teamwork makes the dream work. The team and I @J4ck3LSyN @Archknight23 🚨 Heads-up for anyone running PHP: two critical RCE bugs, patch drops tomorrow. The PHP project has confirmed an emergency security release for two critical remote code execution vulnerabilities: CVE-2026-109618 and CVE-2026-109619, both rated CVSS v4.0 9.2. 📅 Patch lands Wednesday, Oct 21 at 14:00 UTC (9:00 AM Central). PHP has reserved the right to ship it earlier if details leak or exploitation shows up. PHP runs about 75% of the web, including WordPress, Drupal, Joomla, Laravel, Magento, and countless custom apps. If you operate a PHP server, this is your weekend-ruiner unless you act. Here's the part the big threat-intel shops aren't shouting about: No official technical details are public yet. But based on my own source-code analysis of php-src, my best assessment (moderate confidence, NOT officially confirmed) is that the vulnerable path is PHP's session.upload_progress / multipart form-data (rfc1867) handling: 🔹 Present since PHP 5.4 🔹 Enabled by default (the compiled-in default is On; the sample php.ini ships it commented out, so stock installs have it live) 🔹 Processes uploaded request data before any of your application code runs, so it's reachable pre-authentication on a default config That lines up exactly with the public breadcrumbs: "affects default installs," "every version since 5.x," "fires before user code." Treat it as a working hypothesis, not gospel. The official advisory supersedes all of this when it lands. ✅ What to do right now: 1. Inventory your PHP. Know every host and version (php -v). Anything on PHP 7.x or older won't get a fix, so plan to upgrade. 2. Apply the stopgap (best-intel, low-risk, reversible). In php.ini / .user.ini / .htaccess: session.upload_progress.enabled = Off Reload PHP-FPM or your web server. My analysis says this closes one of the two likely paths. 3. Clamp multipart uploads at the edge. The second likely path lives in the multipart parser itself, which runs for any multipart/form-data POST regardless of the setting above. If you've got a WAF or reverse proxy, tighten inspection or rate-limit multipart POSTs to endpoints that don't need uploads. This is the same network-layer mitigation the enterprise vendors are quietly deploying for their paying customers. 4. Patch the second it drops. Current stable: 8.5.11 / 8.4.26 / 8.3.35 / 8.2.34. If your hosting is managed, confirm your provider's timeline today. Why I'm posting this for free: A pre-patch mitigation shouldn't be a subscription perk. I'm a one man shop, and the orgs most likely to get burned in the gap between leak and patch are the small teams without an enterprise threat intel contract. The steps above cost nothing. Spend tonight reducing risk, not tomorrow doing incident response. I'll follow up once the official advisory publishes and confirm whether my root cause read was right. Stay patched. 🔒 #PHP #CyberSecurity #InfoSec #RCE #CVE #WordPress #Laravel #ThreatIntel #VulnerabilityManagement #AppSec
This quoted post is unavailable.
24
148
41
899
270,062
Marek Sušický retweeted
patch or take offline
Full details of a remotely exploitable vulnerability in the core engine of *all* PHP versions will be released tomorrow, October 21st. If your organization has internet facing PHP applications then you need to be ready to patch the minute the update is released or *strongly* consider taking the application offline until you can: php.net/index.php#2026-10-20…
1
6
30
10,216
Multiple NGINX Flaws Let Remote Attackers Crash Servers and Execute Malicious Code Details: cybersecuritynews.com/multip… F5 has disclosed three serious security flaws in NGINX Plus and NGINX Open Source that can let remote, unauthenticated attackers crash worker processes by sending crafted HTTP requests. The flaws are tracked as CVE-2026-97205, CVE-2026-93479, and CVE-2026-15176. F5 published the three advisories on October 14, 2026, and rated every issue High at 8.1 under CVSS v3.1 and Critical at 9.2 under CVSS v4.0. The bugs do not make every NGINX server vulnerable by default because each one needs a specific software version and configuration. F5’s advisories do not report active exploitation of these three newly disclosed flaws. #cybersecuritynews
2
159
16
406
47,013