#Plugin4Shell Etiketinde En Popüler Paylaşımlar

yaklaşık 20 saat önce

🧩 Plugin4Shell: el fallo que permite intercambiar plugins maliciosos en cuatro agentes de IA y que GitHub Copilot aún no ha parcheado https://t.co/CHTL3hJA1t #Plugin4Shell #IA #GitHubCopilot #Ciberseguridad #Vulnerabilidades #AgentesIA #CiberED

Tanya Janca | Shehackspurple @shehackspurple

1 gün önce

One of my favorite lessons from #Plugin4Shell has almost nothing to do with AI. **It's not enough to implement part of a security control. You need to verify the security property you're depending on.** The affected AI coding agents had a specific Git commit that a plugin was supposed to be pinned to. They asked Git to check out that commit. But they didn't verify afterward that the code they actually got WAS that commit. And I love this example because we make this kind of mistake in application security ALL THE TIME. Your framework can generate a CSRF token. Your frontend can send it. Fantastic! But if you don't correctly validate it on the server, you haven't actually completed the security control. Security controls aren't magic. They need to actually enforce the thing we think they're enforcing. 🎥 Plugin4Shell gave us a fascinating example of this, plus a reminder that AI coding plugins are now part of our software supply chain: https://t.co/wTR6AYUWhR

shehackspurple's tweet photo. One of my favorite lessons from #Plugin4Shell has almost nothing to do with AI.

**It's not enough to implement part of a security control. You need to verify the security property you're depending on.**

The affected AI coding agents had a specific Git commit that a plugin was supposed to be pinned to.

They asked Git to check out that commit.

But they didn't verify afterward that the code they actually got WAS that commit.

And I love this example because we make this kind of mistake in application security ALL THE TIME.

Your framework can generate a CSRF token.

Your frontend can send it.

Fantastic!

But if you don't correctly validate it on the server, you haven't actually completed the security control.

Security controls aren't magic. They need to actually enforce the thing we think they're enforcing.

🎥 Plugin4Shell gave us a fascinating example of this, plus a reminder that AI coding plugins are now part of our software supply chain:

https://t.co/wTR6AYUWhR

Daily CyberSecurity @Daily_CyberSec

2 gün önce

Plugin4Shell is a zero-click RCE hitting every major AI coding agent via a SHA pinning bypass. Claude Code and Codex are patched; Copilot and Gemini CLI are not. #Plugin4Shell #AIsupplychain #CodingAgents #ClaudeCode #ZeroClickRCE #SHApinning #AIsecurity https://t.co/j20QrBXzq3

397

Eduardo Jalón @EduJalonT

3 gün önce

⚠️ #Plugin4Shell: una falla deja cambiar el código de plugins "pineados" por hash en #ClaudeCode, #Codex, #Copilot y #GeminiCLI sin que el agente lo note. Parcheado en Claude Code 2.1.179+ y Codex 0.146.0+; pero Copilot y Gemini CLI siguen sin fix. 🔒

omvapt @omvapt

4 gün önce

#Plugin4Shell Lets Repository Owners Swap Pinned #Plugin Code Across Four #AI_Coding_Agents https://t.co/PGni8YCA0v

Tanya Janca | Shehackspurple @shehackspurple

5 gün önce

AI coding plugins are becoming a new part of our software supply chain. And this week we got a pretty spectacular demonstration of why that matters. 😬 Security researchers disclosed #Plugin4Shell, a vulnerability affecting several major AI coding agents. The interesting part to me isn't just the vulnerability. It's what WE can DO about it. (Spoiler: it's AppSec) If your coding agent can run plugins or skills, treat them like dependencies: → Keep your coding agent updated → Be selective about what you install → Inventory your plugins and skills → Limit what the agent can access → Keep production credentials outside its reach → Separate coding, CI/build, and production deployment identities → Monitor what the agent is actually doing AI coding plugins aren't something we need to panic about. They're software. They're dependencies. And they're becoming part of our software supply chain. Fortunately, we already know a LOT about how to secure software supply chains. :-) 🎥 I made a short video about Plugin4Shell and what developers can do to protect themselves: https://t.co/d9dk3SEDyv

shehackspurple's tweet photo. AI coding plugins are becoming a new part of our software supply chain.

And this week we got a pretty spectacular demonstration of why that matters. 😬

Security researchers disclosed #Plugin4Shell, a vulnerability affecting several major AI coding agents.

The interesting part to me isn't just the vulnerability.

It's what WE can DO about it. (Spoiler: it's AppSec)

If your coding agent can run plugins or skills, treat them like dependencies:

→ Keep your coding agent updated
→ Be selective about what you install
→ Inventory your plugins and skills
→ Limit what the agent can access
→ Keep production credentials outside its reach
→ Separate coding, CI/build, and production deployment identities
→ Monitor what the agent is actually doing

AI coding plugins aren't something we need to panic about.

They're software.

They're dependencies.

And they're becoming part of our software supply chain.

Fortunately, we already know a LOT about how to secure software supply chains. :-)

🎥 I made a short video about Plugin4Shell and what developers can do to protect themselves:

https://t.co/d9dk3SEDyv

Es Geeks @EsGeeks

5 gün önce

🚨 PLUGIN4SHELL: RCE zero-click en Claude Code, Codex, Copilot y Gemini CLI. Bypass del pinning de plugins → código malicioso llega solo en updates automáticos. Dos agentes aún sin parche. Actualiza ya o desactiva plugins. #Plugin4Shell #AIAgents #RCE

EsGeeks's tweet photo. 🚨 PLUGIN4SHELL: RCE zero-click en Claude Code, Codex, Copilot y Gemini CLI. Bypass del pinning de plugins → código malicioso llega solo en updates automáticos. Dos agentes aún sin parche.

Actualiza ya o desactiva plugins.

#Plugin4Shell #AIAgents #RCE https://t.co/esiyiIlmgy

745

Cybersecurity News Everyday

@TweetThreatNews

5 gün önce

Ransomware developer sentenced, SAP flaw under active attack, and new AI agent risks emerge as SecurityWeek also notes urgent fixes for WordPress, TP-Link, and AI coding tools. #SAP #Plugin4Shell #AIAgents https://t.co/So8DiMI6sA

288

Cybersecurity News Everyday

@TweetThreatNews

5 gün önce

Plugin4Shell is a zero-click RCE in four AI coding agents, bypassing SHA pinning to swap malicious plugin code during background updates. Two remain unpatched. #Plugin4Shell #ClaudeCode #GitHubCopilot https://t.co/tQeSoXbgdq

201

♫Why♥Not♪

@Python_s_

5 gün önce

#المحقق_NØØT 🕵️ 🚨 تحذير أمني من AIR Security كشفت الشركة عن #Plugin4Shell وهي ثغرة Zero-Click RCE تمس Claude Code وCodex وCopilot وGemini CLI وقد تسمح باستبدال إضافة موثوقة بكود خبيث دون تفاعل المستخدم حدّث Claude Code وCodex فورًا ولا دليل على استغلال فعلي حتى الآن المصدر: AIR Security urlAIR Security — Plugin4Shellhttps://t.co/HgSF87O1Cw

#Plugin4Shell Etiketinde En Popüler Paylaşımlar

Sotwe'de En Son Görülen Etiketler

Senin İçin Trendler

En Popüler Kullanıcılar