Atlassian Rovo Exfiltrates Data, Bypassing Controls

135 pointsposted 6 hours ago
by hackerBanana
(promptarmor.com)

49 Comments

htrp

4 hours ago

I feel like prompt armor writes the exact same blog post for every agentic tool because they all suffer from the ignore previous instructions prompt injections.

https://www.promptarmor.com/resources/claude-cowork-exfiltra...

https://www.promptarmor.com/resources/google-antigravity-exf...

https://promptarmor.substack.com/p/data-exfiltration-from-sl...

https://www.promptarmor.com/resources/gpt-for-google-sheets-...

https://www.promptarmor.com/resources/notion-ai-unpatched-da...

https://www.promptarmor.com/resources/ramps-sheets-ai-exfilt...

https://www.promptarmor.com/resources/superhuman-ai-exfiltra...

nemomarx

3 hours ago

How could they not? If some lab had a method to make really secure guard rails or avoid prompt injection thoroughly I think they would be trumpeting it. But the basic mechanics of language models are vulnerable to this unless you can always be sure the inputs are from a safe user imo

PokestarFan

3 hours ago

If you want AI to be useful it will eventually encounter untrusted content, such as via web search. I think things like web search should probably be run on a different sandboxed AI whose task is to write a summary that is then ingested by the main agent, similar to how existing sandboxing already works, but this would diminish the usefulness quite a bit.

savanaly

3 hours ago

>I think things like web search should probably be run on a different sandboxed AI whose task is to write a summary that is then ingested by the main agent, similar to how existing sandboxing already works, but this would diminish the usefulness quite a bit.

It also wouldn't work. You would simply mindjack the outer AI and have it mindjack the inner AI in turn with its summary. Nesting AIs can't fix the malicious input problem.

santadays

3 hours ago

Just pass that through a third llm.

InsideOutSanta

an hour ago

Correct, that has been prophesied by scripture:

"Thou shalt have three layers of LLMs, no more, no less. Three shall be the number thou shalt have, and the number of the counting of the LLM layers shall be three."

s_Hogg

20 minutes ago

Four is right out

stephbook

2 hours ago

What's so hard about having the LLM tool calls scoped to the tenant? Inject "X-Scope-I" after the LLM decided on a tool call and you're done. Easiest fix ever.

_HMCB_

2 hours ago

Famous last words: easy fix.

hnlmorg

an hour ago

The Rovo MCP server manages scope credentials securely with “bring your own LLM”. Yet somehow they still fucked up with their own agent

simonw

2 hours ago

> Rovo's URL retrieval tool is insecure: there are no protections against opening a URL that has been dynamically created by the agent. Here, Rovo is manipulated to append sensitive data to an attacker's URL.

I think it was Anthropic that first introduced a pattern that completely locks this down: your URL retrieval tool should only work for URLs that have previously been typed into the conversation by a user or have been returned from a trusted tool.

If the agent itself concatenates a new URL together - with leaked data after a ? - you should block that from being fetched.

The great thing about this solution is it's deterministic. You don't need any extra AI in the max - you implement a URL fetching system that knows which sources it should check for a direct match on the URL before it makes that GET request.

devmor

a few seconds ago

Determinism is a terrifying word to people who want to believe their LLM has a little brain and can do anything they want it to.

pram

4 hours ago

I can’t get over how bad “Rovo” is. Somehow more aggressive and useless than Microsoft putting “Copilot” everywhere.

It’s objectively worse than using something like Cowork + MCP, AND they injected it into every single page on JIRA and Confluent which has made web browsing way slower while all the junk is loading.

jerf

4 hours ago

Rovo has my favorite example of AI misfeature. Just checked, it's still there in Cloud Confluence. In Edit mode for a page, you can select a range of text and a menu will pop up, with Ask Rovo being a drop down on it. There's a few good options... Improve Formatting, translation options, Make Shorter...

... but it also has Make Longer. Yes, a built-in feature to type some text in, and the use the mighty power of AI to bloat it.

Naturally, you can repeat this process several times on the same text, for your own little personal demonstration of what model collapse looks like in real time.

linster

10 minutes ago

I've tried the "Make Longer" and "Make Shorter".

When you go "Make longer" the text gets longer.

When you go "Make shorter", the text gets longer still.

You'd think that the original text would be the oracle for shorter(longer(original))?

edaemon

4 hours ago

Don't worry, you can use Rovo to summarize the document! That way you can get the information your coworker wanted to share but filtered through a game of teLLMephone.

perpetuallunch

3 hours ago

We’ve gone from proof-of-work to proof-of-no-work.

pan69

3 hours ago

What's even worse is that, when you do this on the description of a story or task, everytime it comes up with a slightly different format of how it's going to layout the "enhanced" description.

cucumber3732842

an hour ago

>I can’t get over how bad “Rovo” is. Somehow more aggressive and useless than Microsoft putting “Copilot” everywhere.

You're looking at it the wrong way. Think about how much better it is than the joke of a search tool that's slightly to the left of it's icon.

verdverm

4 hours ago

Have you seen the markdown agent instructions they provide in their new agentic `twg` cli? 70k tokens one average, there are more than one...

Rovo is the worse Ai I have used, I suggested they stop trying and let us have model choice. Save money and don't do things out of their skill sets

hahahaa

3 hours ago

> The victim uploads a file to Rovo that contains a hidden prompt injection

Yeah this attack is possible on all modern agentic systems.

* Access to your private data

* Exposure to untrusted content

* The ability to externally communicate in a way that could be used to steal your data

(https://simonw.substack.com/p/the-lethal-trifecta-for-ai-age...)

And blocking it wholesale reduces usefulness of the agent so it is a tradeoff.

gherkinnn

22 minutes ago

It's been over a year and the trifecta holds true. The term 'prompt injection' has been round since May 2022 [0]. No amount of "but the future will fix it" has fixed it.

These breaches will continue for as long as nobody cares about security and everybody is infected with the LLM brainworm.

0 - https://en.wikipedia.org/wiki/Prompt_injection

john_strinlai

4 hours ago

~every ai vulnerability write up boils down to "just ask it do to the thing", but with fancier terms like "indirect prompt injection".

hughw

21 minutes ago

Related: A few days ago, Jira opted everyone in by default to "Contribute in-app data to improve Atlassian apps for everyone"

ExoticPearTree

3 hours ago

Rovo is funny. It downloads everything it can do Atlassian servers for "analysis". And you're pretty much screwed if you link it to Google Docs or Sharepoint. How do I know this? "Why is an AWS IP downloading all our docs?" question I got about a month ago.

crnkofe

an hour ago

Rovo is one of those intrusive AI buttons that suddenly appeared everywhere without any warning. Its so annoying having already shitty UI get borked with features I never use. Almost as annoying as Whatsapp suddenly getting the same FOMO AI button. Its not like I need an AI agent to talk to friends and family. And a summary is something I can always generate via copy&paste into CLI chat session.

I'm still on the edge about security as an afterthought in LLMs. Given its now so easy to generate a ton of slop - why not focus on nonfunctional stuff making LLMs operate faster than thinking for X minutes and limiting exfiltration of local env secrets?

consp

4 hours ago

It's nice they force rovo now for document/version diff's. Because you need to burn down the rainforest for those. (sarcasm ... for obvious reasons)

mvdtnz

3 hours ago

> Note: This attack succeeds even if an organization has disabled web search for Rovo. This is because the web search setting fails to remove the tool for opening the search results.

Wow, great work Atlassian. The web search setting does not disable web search.

formerly_proven

5 hours ago

> Rovo's URL retrieval tool is insecure: there are no protections against opening a URL that has been dynamically created by the agent. Here, Rovo is manipulated to append sensitive data to an attacker's URL. When Rovo calls the insecure tool to open the URL, the attacker's site logs the request, including the appended sensitive data.

alexaholic

3 hours ago

Fwiw Rovo is built on top of Claude

angeldimitrov94

2 hours ago

It's kind of sad because in a shitty Jira setup, Rovo is usually the only way to make any sense of tickets. Don't ask me how I know this. Sadly I think many teams have become dependent on the tool to make sense of their dumpster fire of an Atlassian environment (usually by their own doing but anyway).

throwatdem12311

10 minutes ago

Must be nice. I couldn’t even manage to get it to write a well-formed JQL query.

khanan

5 hours ago

Atlassian has gone from a trusted enterprise-partner to a complete shit-show in just 18 months. This surprises nobody. There will be classes taught in how to fuck up a good business and Atlassian will be the prime example.

Regards, /someone who migrated 3500 users from Atlassians products recently due to their "cloud only"-bullshit.

zelphirkalt

4 hours ago

They were not trustworthy years ago already. Using Atlassian products, one has had to look out for disastrous announcements about their customer data usage way before 18 months ago, especially, if running a business inside the EU, and at least trying to adhere to data protection laws.

gherkinnn

18 minutes ago

I can't remember a time in which Atlassian was trusted.

yborg

4 hours ago

You'd have to look at their profit numbers. They have a huge captive base of customers, like Adobe it might take decades for things to get bad enough and alternatives to arise before their profitability is impacted. And the executives who benefit will have cashed out long before then.

walrus01

4 hours ago

Recently saw an example of somebody who vibe coded a tool to mass export the contents of a 'Confluence' wiki into an instance of self hosted mediawiki, preserving everything.

Mediawiki as a whole has a feature set that 95% of organizations will only scratch the surface of. There's a ridiculous number of possible plugins and customization if you have somebody who knows what they're doing with it.

The majority of companies that need an internal KB/wiki do not have as complex needs or use cases as wikipedia itself or the wikimedia foundation.

busterarm

3 hours ago

I've been at more than one company that migrated _from_ MediaWiki to Confluence. It usually boils down to "non-developers have to use this and Markdown+plugins is hard".

Turns out no matter how much better the thing is, the users have to know what they're doing more than the operators do.

hadrien01

28 minutes ago

I'm not surprised. We're trying to migrate from Jira and Confluence (because we can't have our data outside our servers), and while Jira has many alternatives, it's difficult to find worthy competitors to Confluence. They either have an awful UI/UX, or don't have as many features. We're looking at Xwiki, but simply try to have multiple users simultaneously edit a table and you'll see why everyone prefers Confluence...

walrus01

2 hours ago

visualeditor has been a thing for a long time now, no non technical user needs to ever touch markdown

https://www.mediawiki.org/wiki/VisualEditor

It's the same GUI WYSIWYG interface you get by default if editing a page on public wikipedia.

SomaticPirate

29 minutes ago

To where? Where did you convince c-suite to move to?

git-nebulous

2 hours ago

To be fair to Atlassian - their products did suck quite a bit before 18 months ago as well. Just now they still do, but with ai!

gbalduzzi

4 hours ago

I started to consider it a show show way earlier than 18 months ago. Jira is so terrible to use that it is hard to phantom how they are able to be paid for their product

mosura

4 hours ago

Jira is how it is because almost any product that grows to be that flexible will develop the same problems.

They failed to rearchitect it to something suitable for the inherent flexibility though, so it remains a disaster area, but one that is uniquely able to fit the whims of any manager that can then mandate it for everyone else.

rmunn

2 hours ago

Maybe the workflows, etc., are inherent complexity, so that any similarly-flexible product will have the same problems.

But the awful client-server architecture, where anything you do takes several seconds of waiting for the client to send who-knows-what to the server and get data back, even selecting something from a dropdown... that is absolutely just Jira. A competing product would be able to deliver much, MUCH snappier UX. Jira is just the crappiest, slowest UI that I have ever had the displeasure of being forced to work with.

mosura

2 hours ago

I invite you to write such a trivially flexible workflow system, and see what happens to the performance of your user interface.

They needed someone over there with the power to say no.

chollida1

4 hours ago

if you track their 5 year stock price you'll find the market fully agrees with you. It was $458 in 2021 and is $112 now.

The market caught on quickly that Atlassian's software fits into the group of software like Oracle or SAP that no one uses by choice and only uses because it was forced on them.

shagie

3 hours ago

> ... Many forms of issue tracking have been tried, and will be tried in this world of sin and woe. No one pretends that Jira is perfect or all-wise. Indeed, it has been said that Jira is the worst of the issue trackers except all those other forms that have been tried from time to time; but there is the broad feeling in our company that the people should track, continuously track, and that client opinion, expressed by all project management means, should shape, guide, and control the actions of management who are their masters and not their servants. ...

-- Churchill, House of Commons, 11 November 1947

automatic6131

3 hours ago

Ahh yes: "when you Rovo, you oh-no my data"