[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-mcp-flaw-expose-150-million-downloads-zh":3,"tags-mcp-flaw-expose-150-million-downloads-zh":35,"related-lang-mcp-flaw-expose-150-million-downloads-zh":44,"related-posts-mcp-flaw-expose-150-million-downloads-zh":48,"series-research-9a661983-40e4-41b3-b67b-4c9b8c8d7b9d":85},{"id":4,"title":5,"content":6,"summary":7,"source":8,"source_url":9,"author":10,"image_url":11,"keywords":12,"language":19,"translated_content":10,"views":20,"is_premium":21,"created_at":22,"updated_at":22,"cover_image":11,"published_at":23,"rewrite_status":24,"rewrite_error":10,"rewritten_from_id":25,"slug":26,"category":27,"related_article_id":28,"status":29,"google_indexed_at":30,"x_posted_at":10,"tweet_text":10,"title_rewritten_at":10,"title_original":10,"key_takeaways":31,"topic_cluster_id":10,"embedding":10,"is_canonical_seed":21},"9a661983-40e4-41b3-b67b-4c9b8c8d7b9d","MCP 漏洞恐波及 1.5 億下載","\u003Cp data-speakable=\"summary\">Ox Secu\u003Ca href=\"\u002Fnews\u002Fclarity-act-stablecoin-compromise-banks-crypto-zh\">rity\u003C\u002Fa> 指出，MCP 設計缺陷可能讓攻擊者執行指令，影響 1.5 億次下載與最高 20 萬個脆弱實例。\u003C\u002Fp>\u003Cp>這篇在講一個很麻煩的事。\u003Ca href=\"https:\u002F\u002Fmodelcontextprotocol.io\" target=\"_blank\" rel=\"noopener\">Model Context Protocol\u003C\u002Fa>，也就是 MCP，可能有設計缺陷。它不是單一套件壞掉，而是很多 AI 工具共用的連接層出事。\u003C\u002Fp>\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.oxsecurity.com\" target=\"_blank\" rel=\"noopener\">Ox Security\u003C\u002Fa> 在 2026 年 4 月 15 日公布報告。它說，這個問題可能影響 200 多個開源專案、7,000 多台公開伺服器，還有最多 20 萬個脆弱實例。講白了，這不是小洞，是一個會擴散的洞。\u003C\u002Fp>\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>指標\u003C\u002Fth>\u003Cth>報告數字\u003C\u002Fth>\u003Cth>意義\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>開源專案\u003C\u002Ftd>\u003Ctd>200+\u003C\u002Ftd>\u003Ctd>影響範圍跨多個生態系\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>下載量\u003C\u002Ftd>\u003Ctd>1.5 億\u003C\u002Ftd>\u003Ctd>代表 SDK 擴散很廣\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>公開伺服器\u003C\u002Ftd>\u003Ctd>7,000+\u003C\u002Ftd>\u003Ctd>暴露在公開網路上\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>脆弱實例\u003C\u002Ftd>\u003Ctd>最高 20 萬\u003C\u002Ftd>\u003Ctd>顯示實際風險不小\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>問題到底卡在哪裡\u003C\u002Fh2>\u003Cp>Ox Security 的說法很直接。問題出在 MCP 官方 SDK 處理 STDIO 型伺服器啟動的方式。簡單說，命令可能先跑了，錯誤訊息卻還沒來得及提醒你。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778001053269-i80g.png\" alt=\"MCP 漏洞恐波及 1.5 億下載\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>這種設計很討厭。因為一般開發流程會靠失敗訊號擋掉壞參數。結果現在變成，開發工具還在往前跑，惡意指令已經先執行。\u003C\u002Fp>\u003Cp>報告點名 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\" target=\"_blank\" rel=\"noopener\">MCP 的官方 SDK\u003C\u002Fa>，涵蓋 Python、Ty\u003Ca href=\"\u002Fnews\u002Fopenclaw-vs-hermes-wu-ceng-jia-gou-dui-bi-zh\">pe\u003C\u002Fa>Script、Java、\u003Ca href=\"\u002Ftag\u002Frust\">Rust\u003C\u002Fa>。Ox Security 也說，這可能導致任意指令執行，後果包括 API key 外洩、內部資料庫被碰、聊天紀錄被翻。\u003C\u002Fp>\u003Cul>\u003Cli>執行路徑：STDIO 介面啟動本機伺服器\u003C\u002Fli>\u003Cli>風險結果：任意指令執行\u003C\u002Fli>\u003Cli>可能外洩：資料、API key、資料庫、聊天紀錄\u003C\u002Fli>\u003Cli>受影響語言：Python、TypeScript、Java、Rust\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>為什麼這比單一漏洞更麻煩\u003C\u002Fh2>\u003Cp>這事麻煩的地方，不是技術花招本身。真正可怕的是，MCP 是連接 AI 模型和外部工具的通用層。它一旦出問題，很多產品會一起中招。\u003C\u002Fp>\u003Cp>MCP 之所以受歡迎，是因為它讓 a\u003Ca href=\"\u002Fnews\u002Fwhy-hermes-agent-belongs-on-cloud-server-zh\">gent\u003C\u002Fa> 整合變簡單。問題是，方便常常會偷走安全邊界。尤其在 AI 軟體圈，大家都在趕著上線連接器，根本沒空慢慢磨安全細節。\u003C\u002Fp>\u003Cp>這裡可以直接看出供應鏈風險。不是某一家公司的 app 寫錯而已，是標準本身的預設行為，可能把錯誤放大到整個生態系。\u003C\u002Fp>\u003Cblockquote>“We are trusting these systems with increasingly sensitive data and real-world actions. If the very protocol meant to connect AI agents is this fragile and its creators will not fix it then every company and developer building on top of it needs to treat this as an immediate wake-up call,” said Kevin Curran, professor of cybersecurity at Ulster University and IEEE senior member.\u003C\u002Fblockquote>\u003Cp>Kevin Curran 這段話講得很白。當一個協定變成很多 AI 產品的共同底座，它的安全設計就不能靠運氣。\u003C\u002Fp>\u003Cp>我覺得，這種問題最糟的地方是平常看不出來。等到真的被打，通常已經有很多服務在偷偷執行不該執行的東西了。\u003C\u002Fp>\u003Ch2>數字對比，才看得出嚴重度\u003C\u002Fh2>\u003Cp>如果只看「有漏洞」三個字，大家很容易滑過去。把數字攤開來看，事情就清楚多了。200 多個專案、1.5 億次下載、7,000 多台公開伺服器，這不是單點事故。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778001053803-x79w.png\" alt=\"MCP 漏洞恐波及 1.5 億下載\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>再加上最高 20 萬個脆弱實例，代表風險不是停在 \u003Ca href=\"\u002Ftag\u002Fgithub\">GitHub\u003C\u002Fa> README。它已經碰到真實部署環境。對開發者來說，這種規模的問題，通常不是靠一個補丁就能收尾。\u003C\u002Fp>\u003Cp>Ox Security 也說，它已經做過 30 多次 responsible disclosure，還找出 10 多個高風險或重大風險 CVE。這表示它不是第一次碰這類問題，而是在看整個 AI 工具鏈的共通風險。\u003C\u002Fp>\u003Cul>\u003Cli>Responsible disclosures：30+\u003C\u002Fli>\u003Cli>高或重大 CVE：10+\u003C\u002Fli>\u003Cli>受影響開源專案：200+\u003C\u002Fli>\u003Cli>公開伺服器：7,000+\u003C\u002Fli>\u003C\u002Ful>\u003Cp>把這些數字放一起看，MCP 的問題就很像雲端早期的設定失誤。單看一台機器沒事，放大到整批部署，就會變成維運惡夢。\u003C\u002Fp>\u003Cp>而且 MCP 的角色很敏感。它碰到檔案、資料庫、API，還有 \u003Ca href=\"\u002Ftag\u002Fagent\">agent\u003C\u002Fa> 能做的動作。這些東西一旦被串起來，攻擊者拿到的不是一個洞，而是一條路。\u003C\u002Fp>\u003Ch2>開發團隊現在該做什麼\u003C\u002Fh2>\u003Cp>如果你的團隊有在用 MCP，先別急著相信 SDK 預設值。你要檢查每一個會啟動本機程序的地方，也要看命令字串怎麼組、怎麼轉義、怎麼記錄。\u003C\u002Fp>\u003Cp>安全團隊也該盤點公開的 MCP 伺服器。哪些是直接暴露在網際網路上，哪些連到 secrets、內部資料庫、聊天紀錄，這些都要列清楚。只要 connector 能碰到敏感資料，它就該比一般 API 更嚴格。\u003C\u002Fp>\u003Cp>另外，別把「官方 SDK」四個字當護身符。很多事故都是這樣來的。大家以為官方預設最安全，結果只是大家一起相信錯了。\u003C\u002Fp>\u003Cul>\u003Cli>先查本機程序啟動點\u003C\u002Fli>\u003Cli>檢查命令字串與轉義處理\u003C\u002Fli>\u003Cli>盤點公開 MCP 伺服器\u003C\u002Fli>\u003Cli>確認是否能碰到 secrets、資料庫、聊天紀錄\u003C\u002Fli>\u003C\u002Ful>\u003Cp>對團隊來說，現在最實際的做法不是等新聞結束。是先把能跑命令的地方全掃一遍，因為這類洞通常不會自己消失。\u003C\u002Fp>\u003Cp>如果你在做 \u003Ca href=\"\u002Ftag\u002Fai-agent\">AI agent\u003C\u002Fa>，我會直接問一句：當攻擊者控制 MCP 命令字串時，什麼機制真的擋得住它？\u003C\u002Fp>\u003Ch2>這件事放回產業脈絡看\u003C\u002Fh2>\u003Cp>MCP 之所以重要，是因為它想解決一個老問題。LLM 很會講話，但它本來不會直接碰你的軟體、資料和伺服器。MCP 就是在中間補一層標準介面。\u003C\u002Fp>\u003Cp>這種標準一旦普及，風險也會一起普及。以前每家公司各做各的 connector，問題分散。現在大家往同一個 protocol 靠攏，出事時就會一起抖。\u003C\u002Fp>\u003Cp>這也是 \u003Ca href=\"\u002Ftag\u002Fai-\">AI 基礎設施\u003C\u002Fa>最現實的一面。模型再強，最後還是要接資料、接工具、接權限。只要這一層沒設計好，後面的應用再花俏都沒用。\u003C\u002Fp>\u003Cp>對台灣開發團隊來說，這種事很值得盯。很多公司正在把 LLM 接進客服、內部知識庫、工單系統，下一步就是接更多內部工具。問題不是要不要用 MCP，而是你敢不敢把它放進正式環境。\u003C\u002Fp>\u003Ch2>接下來該盯什麼\u003C\u002Fh2>\u003Cp>我會先看兩件事。第一，MCP 官方 SDK 會不會改預設行為。第二，主流框架會不會開始把命令執行改成明確 opt-in。這兩件事會直接決定風險是降下來，還是繼續被大家默默接受。\u003C\u002Fp>\u003Cp>如果你現在已經在部署 MCP，別等供應商幫你想完。先把權限縮小、把公開面收起來、把能執行命令的路徑全部列出來。這種工作很無聊，但很省命。\u003C\u002Fp>\u003Cp>說真的，這類問題最怕大家當成新聞看完就算。你今天不查，明天可能就是你的伺服器在幫別人跑指令。\u003C\u002Fp>","Ox Security 指出，MCP 設計缺陷可能影響 1.5 億次下載、200 多個開源專案，還有最高 20 萬個脆弱實例。","www.infosecurity-magazine.com","https:\u002F\u002Fwww.infosecurity-magazine.com\u002Fnews\u002Fsystemic-flaw-mcp-expose-150\u002F",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778001053269-i80g.png",[13,14,15,16,17,18],"MCP","Model Context Protocol","AI 安全","任意指令執行","供應鏈風險","Ox Security","zh",1,false,"2026-05-05T17:10:34.404983+00:00","2026-05-05T17:10:34.329+00:00","done","63564a22-9a11-48f4-a1e6-12b2998aa58c","mcp-flaw-expose-150-million-downloads-zh","research","c5b33206-47f9-4af7-babf-717ee782d2ba","published","2026-05-06T09:00:21.972+00:00",[32,33,34],"MCP 的問題不是單一套件，而是通用協定層的設計風險。","Ox Security 提到 1.5 億次下載、200 多個專案、最高 20 萬個脆弱實例。","團隊應先盤點 MCP 命令啟動點、公開伺服器與敏感資料存取權限。",[36,38,40,42,43],{"name":14,"slug":37},"model-context-protocol",{"name":13,"slug":39},"mcp",{"name":15,"slug":41},"ai-安全",{"name":17,"slug":17},{"name":16,"slug":16},{"id":28,"slug":45,"title":46,"language":47},"mcp-flaw-expose-150-million-downloads-en","MCP flaw may expose 150 million downloads","en",[49,55,61,67,73,79],{"id":50,"slug":51,"title":52,"cover_image":53,"image_url":53,"created_at":54,"category":27},"667b72b6-e821-4d68-80a1-e03340bc85f1","turboquant-seo-shift-small-sites-zh","TurboQuant 與小站 SEO 變化","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778840440690-kcw9.png","2026-05-15T10:20:27.319472+00:00",{"id":56,"slug":57,"title":58,"cover_image":59,"image_url":59,"created_at":60,"category":27},"381fb6c6-6da7-4444-831f-8c5eed8d685c","turboquant-vllm-comparison-fp8-kv-cache-zh","TurboQuant 與 FP8 實測結果","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778839867551-4v9g.png","2026-05-15T10:10:36.034569+00:00",{"id":62,"slug":63,"title":64,"cover_image":65,"image_url":65,"created_at":66,"category":27},"c15f45ee-a548-4dbf-8152-91de159c1a11","llmbda-calculus-agent-safety-rules-zh","LLMbda 演算替 AI 代理人立安全規則","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778825503412-mlbf.png","2026-05-15T06:10:34.832664+00:00",{"id":68,"slug":69,"title":70,"cover_image":71,"image_url":71,"created_at":72,"category":27},"0c02225c-d6ff-44f8-bc92-884c8921c4a3","low-complexity-beamspace-denoiser-mmwave-mimo-zh","更簡單的毫米波波束域去噪器","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778814650361-xtc2.png","2026-05-15T03:10:30.06639+00:00",{"id":74,"slug":75,"title":76,"cover_image":77,"image_url":77,"created_at":78,"category":27},"9d27f967-62cc-433f-8cdb-9300937ade13","ai-benchmark-wins-cyber-scare-defenders-zh","為什麼 AI 基準賽在資安領域的勝利，應該讓防守方警醒","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778807450006-nofx.png","2026-05-15T01:10:29.379041+00:00",{"id":80,"slug":81,"title":82,"cover_image":83,"image_url":83,"created_at":84,"category":27},"bc402dc6-5da6-46fc-9d66-d09cb215f72b","why-linux-security-needs-patch-wave-mindset-zh","為什麼 Linux 安全需要「補丁浪潮」思維","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778741449813-s2wn.png","2026-05-14T06:50:24.052583+00:00",[86,91,96,101,106,111,116,121,126,131],{"id":87,"slug":88,"title":89,"created_at":90},"f18dbadb-8c59-4723-84a4-6ad22746c77a","deepmind-bets-on-continuous-learning-ai-2026-zh","DeepMind 押注 2026 連續學習 AI","2026-03-26T08:16:02.367355+00:00",{"id":92,"slug":93,"title":94,"created_at":95},"f4a106cb-02a6-4508-8f39-9720a0a93cee","ml-papers-of-the-week-github-research-desk-zh","每週 ML 論文清單，為何紅到 GitHub","2026-03-27T01:11:39.284175+00:00",{"id":97,"slug":98,"title":99,"created_at":100},"c4f807ca-4e5f-47f1-a48c-961cf3fc44dc","ai-ml-conferences-to-watch-in-2026-zh","2026 AI 研討會投稿時程整理","2026-03-27T01:51:53.874432+00:00",{"id":102,"slug":103,"title":104,"created_at":105},"9f50561b-aebd-46ba-94a8-363198aa7091","openclaw-agents-manipulated-self-sabotage-zh","OpenClaw Agent 會自己搞砸自己","2026-03-28T03:03:18.786425+00:00",{"id":107,"slug":108,"title":109,"created_at":110},"11f22e92-7066-4978-a544-31f5f2156ec6","vega-learning-to-drive-with-natural-language-instructions-zh","Vega：使用自然語言指示進行自駕車控制","2026-03-28T14:54:04.847912+00:00",{"id":112,"slug":113,"title":114,"created_at":115},"a4c7cfec-8d0e-4fec-93cf-1b9699a530b8","drive-my-way-en-zh","Drive My Way：個性化自駕車風格的實現","2026-03-28T14:54:26.207495+00:00",{"id":117,"slug":118,"title":119,"created_at":120},"dec02f89-fd39-41ba-8e4d-11ede93a536d","training-knowledge-bases-with-writeback-rag-zh","用 WriteBack-RAG 強化知識庫提升檢索效能","2026-03-28T14:54:45.775606+00:00",{"id":122,"slug":123,"title":124,"created_at":125},"3886be5c-a137-40cc-b9e2-0bf18430c002","packforcing-efficient-long-video-generation-method-zh","PackForcing：短影片訓練也能生成長影片","2026-03-28T14:55:02.688141+00:00",{"id":127,"slug":128,"title":129,"created_at":130},"72b90667-d930-4cc9-8ced-aaa0f8968d44","pixelsmile-toward-fine-grained-facial-expression-editing-zh","PixelSmile：提升精細臉部表情編輯的新方法","2026-03-28T14:55:20.678181+00:00",{"id":132,"slug":133,"title":134,"created_at":135},"cf046742-efb2-4753-aef9-caed5da5e32e","adaptive-block-scaled-data-types-zh","IF4：神經網路量化的聰明選擇","2026-03-31T06:00:36.990273+00:00"]