Live data from Hacker News

GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos

noma.security

31–40 of 228 posts

Re: GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos

#31
post #11

> Responsible Disclosure GitLost was responsibly disclosed to GitHub. Vulnerability details are shared here with their knowledge. Why does this section not have when it was fixed or GitHub acknowledge/rejected this? Did they not fix this?

This isn’t a normal software bug, it’s not fixable in the same way you can’t fix regular support staff from being tricked. The answer is you should not allow LLMs access to untrusted input and sensitive data at the same time.

Your second paragraph directly contradicts the first.

Re: GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos

#32

Why would anyone ever trust private repos on GitHub or other cloud solutions to offer any real privacy for codebases? Of course they are going to steal your code as soon as you upload it by pushing it, LLMs just enables them to obfuscate their intentional theft and let them get away with it and profit from it.

I suspect you are greatly overestimating the average organization's ability to run a Git server themselves and keep it secure, while also overestimating how evil GitHub and LLM's providers are.

Re: GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos

#33

Earlier quoted context omitted.

This isn’t a normal software bug, it’s not fixable in the same way you can’t fix regular support staff from being tricked. The answer is you should not allow LLMs access to untrusted input and sensitive data at the same time.

Your second paragraph directly contradicts the first.

Since you cannot fix information leakage from LLMs, you must remove the information so that it cannot be leaked. There is no contradiction there.

Re: GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos

#36

How is this a Github vulnerability? The researchers are the ones that grant the agent access to private repos and then ask it to answer questions in public repos.. of course this allows extracting private information? This is like setting up a normal CI job with access to secrets and running it on public PRs. If you configure GitHub to allow public code or LLM instructions to run in contexts that have access to sensi…

"How is this a Github vulnerability? The researchers are the ones that grant the agent access to private repos and then ask it to answer questions in public repos.. of course this allows extracting private information?" I think the assumption is that the permissions are scoped to the repository you're currently asking questions on, rather than your private repositories as well. I can see arguments for both sides.

But they explicitly setup the permissions this way.

Re: GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos

#37

    “Prompt injection attacks have become, to agentic AI, what SQL injections were to web applications: a systematic, category-wide vulnerability class that requires the same systematic strategies and defenses.”

???

Isn’t prompt injection far more fatal to LLMs than SQL injection is to SQL databases?

Like, the problem of SQL injection was that user input was forming part of the instruction string given to the SQL engine, and so malicious user input could include various SQL grammar terminals to end the current SQL command, followed by complete SQL commands of their own, and the engine would simply execute both commands. The fix was prepared statements: fixed/static/pre-compiled instruction strings, that can only ever perform fixed/static/pre-defined logic, and that logic can then be (more) safely applied to arbitrary user-input data.

The analogous mitigation for agents is to have fixed behaviors they can perform, such as “read repo 1” “read repo 2”, etc., and the user input is used as data to select which of these fixed behaviors to execute. But we already have this technology - it’s called a menu. The value of LLMs is specifically and intrinsically predicated on being more than a menu, while the value of SQL does not depend on being more than “pre-set logic operating on arbitrary data” - user input being part of the instruction string to SQL was incidental, for developer convenience.

Re: GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos

#38
post #12

Large corporations like Microsoft under constant pressure from investors are slapping AI onto every single product offering just so they can claim they're an AI company now. Just like what Adobe did. So yeah, that didn't end well and probably this wouldn't either. Consumers are getting tired of these half-assed AI integrations and there will be a breaking point soon.

Microsoft is a publicly traded company. Which investors are causing them to shit up GitHub with AI features nobody wants? In which venues?

Re: GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos

#40

How is this a Github vulnerability? The researchers are the ones that grant the agent access to private repos and then ask it to answer questions in public repos.. of course this allows extracting private information? This is like setting up a normal CI job with access to secrets and running it on public PRs. If you configure GitHub to allow public code or LLM instructions to run in contexts that have access to sensi…

> If you configure GitHub to allow public code or LLM instructions to run in contexts that have access to sensitive things, they will leak; that’s not GitHub’s fault, it’s yours.

Is there a way to segment access per agentic workflow, so that you can have both habe an agentic workflow that has access to sensitive data and one that has only access to public data? Is the default to set the scope to only the current repository? Does Github appropriately inform about the risk of combining an agentic workflow with access to private repository data?

If the answer to any of those questions is "no", then that's a problem.

(Classic GH Workflows are also riddled with priveledge escalation via PR-triggered workflows, but that's another topic.)

Post reply on HN