{"id":6216,"date":"2024-11-13T13:47:53","date_gmt":"2024-11-13T19:47:53","guid":{"rendered":"https:\/\/www.darkreading.com\/cloud-security\/google-ai-platform-bugs-proprietary-enterprise-llms"},"modified":"2024-11-13T13:47:53","modified_gmt":"2024-11-13T19:47:53","slug":"google-ai-platform-bugs-leak-proprietary-enterprise-llms","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/11\/13\/google-ai-platform-bugs-leak-proprietary-enterprise-llms\/","title":{"rendered":"Google AI Platform Bugs Leak Proprietary Enterprise LLMs"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

Google has fixed two flaws in Vertex AI, its platform for custom development and deployment of <\/span>large language models (LLMs)<\/a><\/span>, that could have allowed attackers to exfiltrate proprietary enterprise models from the system. The flaw highlights once again the danger that malicious manipulation of artificial intelligence (AI) technology present for business users.<\/span><\/p>\n

Researchers at Palo Alto Networks Unit 42 discovered the flaws in Google’s Vertex AI platform, a machine learning (ML) platform that allows enterprise users to train and deploy ML models and AI applications. The platform is aimed at allowing for custom development of LLMs for use in an organization’s AI-powered applications.<\/span><\/p>\n

Specifically, the researchers discovered a privilege escalation flaw in the “custom jobs” feature of the platform, and a model exfiltration flaw in the “malicious model” feature, Unit 42 <\/span>revealed in a blog post<\/a><\/span> published on Nov. 12.<\/span><\/p>\n

___________________________________<\/span><\/p>\n

Don’t miss the upcoming free <\/span><\/span>Dark Reading Virtual Event<\/a><\/span>, “Know Your Enemy: Understanding Cybercriminals and Nation-State Threat Actors,” Nov. 14 at 11 a.m. ET. <\/span><\/span>Don’t miss sessions on understanding MITRE ATT&CK, using proactive security as a weapon, and a masterclass in incident response; and a host of top speakers like Larry Larsen from the Navy Credit Federal Union, former Kaspersky Lab analyst Costin Raiu, Ben Read of Mandiant Intelligence, Rob Lee from SANS, and Elvia Finalle from Omdia. <\/span><\/span>Register now!<\/a><\/span><\/p>\n

Related:<\/span>2 Zero-Day Bugs in Microsoft’s Nov. Update Under Active Exploit<\/a><\/p>\n

___________________________________<\/span><\/p>\n

The first bug allowed for exploitation of custom job permissions to gain unauthorized access to all data services in the project. The second could have allowed an attacker to deploy a poisoned model in Vertex AI, leading to “the exfiltration of all other fine-tuned models, posing a serious proprietary and sensitive data exfiltration attack risk,” Palo Alto Networks researchers wrote in the post.<\/span><\/p>\n

Unit 42 shared its findings with Google, and the company has “since implemented fixes to eliminate these specific issues for Vertex AI on the Google Cloud Platform (GCP),” according to the post.<\/span><\/p>\n

While the imminent threat has been mitigated, the security vulnerabilities once again demonstrate the inherent danger that occurs when LLMs are exposed and\/or <\/span>manipulated<\/a><\/span> with malicious intent, and how quickly the issue can spread, the researchers said.<\/span><\/p>\n

“This research highlights how a single <\/span>malicious model deployment<\/a><\/span> could compromise an entire AI environment,” the researchers wrote. “An attacker could use even one unverified model deployed on a production system to exfiltrate sensitive data, leading to severe model exfiltration attacks.”<\/span><\/p>\n

Related:<\/span>Amazon Employee Data Compromised in MOVEit Breach<\/a><\/p>\n

Poisoning Custom LLM Development<\/h2>\n

The key for exploiting the flaws that were discovered lies within a feature of Vertex AI called Vertex AI Pipelines, which allow users to tune their models using custom jobs, also referred to as “custom training jobs.” “These custom jobs are essentially code that runs within the pipeline and can modify models in various ways,” the researchers explained.<\/span><\/p>\n

However, while this flexibility is valuable, it also opens the door to potential exploitation, they said. In the case of the vulnerabilities, Unit 42 researchers were able to abuse permissions within what’s called a “service agent” identity of a “tenant project” \u2014 connected through the project pipeline to the “source project,” or fine-tuned AI model created within the platform. A service agent has excessive permissions to many permissions within a Vertex AI project.<\/span><\/p>\n

From this position, the researchers could either inject commands or create a custom image to create a backdoor that allowed them to gain access to the custom model development environment. They then deployed a poisoned model for testing within Vertex AI that allowed them to gain further access to steal other AI and ML models from the test project.<\/span><\/p>\n

Related:<\/span>‘GoIssue’ Cybercrime Tool Targets GitHub Developers En Masse<\/a><\/p>\n

“In summary, by deploying a malicious model, we were able to access resources in the tenant projects that allowed us to view and export all models deployed across the project,” the researchers wrote. “This includes both ML and LLM models, along with their fine-tuned adapters.”<\/span><\/p>\n

This method presents “a clear risk for a model-to-model infection scenario,” they explained. “For example, your team could unknowingly deploy a malicious model uploaded to a public repository,” the researchers wrote. “Once active, it could exfiltrate all ML and fine-tuned LLM models in the project, putting your most sensitive assets at risk.”<\/span><\/p>\n

Mitigating AI Cybersecurity Risk<\/h2>\n

Organizations are just beginning to have access to tools that can allow them to build their own in-house, custom LLM-based AI systems, and thus the <\/span>potential security risks<\/a><\/span> and solutions to mitigate them are still very much uncharted territory. However, it’s become clear that gaining <\/span>unauthorized access<\/a><\/span> to LLMs created within an organization is one surefire way to expose that organization to compromise.<\/span><\/p>\n

At this stage, key to securing any custom-built models is to limit the permissions of those in the enterprise that have access to it, the Unit 42 researchers noted. “The permissions required to deploy a model might seem harmless, but in reality, that single permission could grant access to all other models in a vulnerable project,” they wrote in the post.<\/span><\/p>\n

To protect against such risks, organizations also should implement strict controls on model deployments. A fundamental way to do this is to ensure an organization’s development or test environments are separate from its live production environment.<\/span><\/p>\n

“This separation reduces the risk of an attacker accessing potentially insecure models before they are fully vetted,” Balassiano and Shaty wrote. “Whether it comes from an internal team or a third-party repository, validating every model before deployment is vital.”<\/span><\/p>\n

Don’t miss the upcoming free <\/span><\/span>Dark Reading Virtual Event<\/a><\/span>, “Know Your Enemy: Understanding Cybercriminals and Nation-State Threat Actors,” Nov. 14 at 11 am ET.<\/span><\/span> <\/span><\/span>Don’t miss sessions on understanding MITRE ATT&CK, using proactive security as a weapon, and a masterclass in incident response; and a host of top speakers like Larry Larsen from the Navy Credit Federal Union, former Kaspersky Lab analyst Costin Raiu, Ben Read of Mandiant Intelligence, Rob Lee from SANS, and Elvia Finalle from Omdia. <\/span><\/span>Register now!<\/a><\/span><\/p>\n

Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Google has fixed two flaws in Vertex AI, its platform<\/p>\n","protected":false},"author":12,"featured_media":6217,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[809],"class_list":["post-6216","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-dark-reading"],"featured_image_urls":{"full":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?fit=1800%2C1013&ssl=1",1800,1013,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?fit=1536%2C864&ssl=1",1536,864,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?fit=1800%2C1013&ssl=1",1800,1013,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?fit=1024%2C576&ssl=1",1024,576,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?resize=825%2C575&ssl=1",825,575,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?resize=590%2C410&ssl=1",590,410,true]},"author_info":{"display_name":"Dark Reading","author_link":"https:\/\/ddi.mohflo.net\/index.php\/author\/darkreading\/"},"category_info":"Uncategorized<\/a>","tag_info":"Uncategorized","comment_count":"0","jetpack_featured_media_url":"https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/google-ai-platform-bugs-leak-proprietary-enterprise-llms.jpg?fit=1800%2C1013&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/6216","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/comments?post=6216"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/6216\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/6217"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=6216"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=6216"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=6216"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}