Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atlassian Rovo Exfiltrates Data, Bypassing Controls

promptarmor.com

Post reply on HN
Print view View original

141–147 of 147 posts

Re: Atlassian Rovo Exfiltrates Data, Bypassing Controls

#141

Post by mattbrewsbytes »

rightbyte wrote: post #103
kevcampb wrote: post #97

Worth reminding everyone of previous discussion when Atlassian opted-in all customers by default for their data to be used for model training. https://news.ycombinator.com/item?id=47833247 This goes live on August 17. If you haven't switched it off your company IP will be used to train their future models.

So they will harvest trade secrets from 10000s of companies and there have been no panic mass flight about this? How companies entrust SaaSs with their data is beyond insane to me. Especially since FOSS alternatives are readily available.

I've seen their ticketing software, what on earth are they going to do with any trade secrets? There are none in ticketing software or wiki's.

Also the people making decisions on their products (or any "enterprise" SaaS for that matter) aren't the ones stuck using it.

Re: Atlassian Rovo Exfiltrates Data, Bypassing Controls

#142

Post by pavel_lishin »

mattbrewsbytes wrote: post #141
rightbyte wrote: post #103

Earlier quoted context omitted.

So they will harvest trade secrets from 10000s of companies and there have been no panic mass flight about this? How companies entrust SaaSs with their data is beyond insane to me. Especially since FOSS alternatives are readily available.

I've seen their ticketing software, what on earth are they going to do with any trade secrets? There are none in ticketing software or wiki's. Also the people making decisions on their products (or any "enterprise" SaaS for that matter) aren't the ones stuck using it.

> There are none in ticketing software or wiki's.

But there might be API keys, passwords, unlisted URLs, email addresses, etc.

Re: Atlassian Rovo Exfiltrates Data, Bypassing Controls

#143

Post by rightbyte »

pavel_lishin wrote: post #142
mattbrewsbytes wrote: post #141

Earlier quoted context omitted.

I've seen their ticketing software, what on earth are they going to do with any trade secrets? There are none in ticketing software or wiki's. Also the people making decisions on their products (or any "enterprise" SaaS for that matter) aren't the ones stuck using it.

> There are none in ticketing software or wiki's. But there might be API keys, passwords, unlisted URLs, email addresses, etc.

I guess customer lists might be the most valuable data in most Jira setups. Sales data ...

Re: Atlassian Rovo Exfiltrates Data, Bypassing Controls

#144

Post by paradox460 »

pram wrote: post #5

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.

When it was new I tried something fairly easy, or so I thought

"Label all stories in the current project that contain "foo" with label "bar

It failed

Re: Atlassian Rovo Exfiltrates Data, Bypassing Controls

#145

Post by b-geuvieydbe »

sph wrote: post #104
rightbyte wrote: post #103

Earlier quoted context omitted.

So they will harvest trade secrets from 10000s of companies and there have been no panic mass flight about this? How companies entrust SaaSs with their data is beyond insane to me. Especially since FOSS alternatives are readily available.

Who cares? The employee, just looking to make rent? The CEO, all in on the dream of the AI powered future? Legal, looking forward to litigation and well-competition retainers? Atlassian itself, when it’s just one of the many companies training models on private intellectual property, and whose T&C clearly state they will be doing so? Competitors, when there will be no reasonable way to prove their code has been gener…

[dead]

Re: Atlassian Rovo Exfiltrates Data, Bypassing Controls

#146

Post by hahahaa »

gherkinnn wrote: post #47
hahahaa wrote: post #23

> 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…

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

My only warning with the trifecta is it sufficient but not necessary for an LLM attack.

All you need is the untrusted content (or more generally vulnerable content since how you feel about the content doesn't matter) leg and something you care about to be attacked.

E.g. could be as simple as a prompt injection that causes your LLM to output a prompt injection that then gets inserted somewhere else.

Or without exfiltration rm -rf /

Or a social engineering attack.

So there are other bifectas and trifectas.

Re: Atlassian Rovo Exfiltrates Data, Bypassing Controls

#147

Post by jappgar »

danudey wrote: post #132
jappgar wrote: post #105

Earlier quoted context omitted.

The truth is that most software companies don't have any secrets worth hiding. The saas industry is all about sales and deals. The market runs on access, not intelligence.

Knowing that our competitor is trying to poach one of our clients away by promising a new feature could be very useful to us. Likewise, knowing that a competitor is at risk of losing a customer because they won't implement a feature that we're willing to implement (or already have) is a qualified sales lead. All of this would be illegal if discovered in this way, presumably, but it's not entirely accurate to say that…

Usually customers are open about this kind of thing though. They play you off your competitors and vice versa.

I don't totally disagree, I just think the real secrets have nothing to do with features or dev. The secret is A is about to go bankrupt or B is facing legal trouble. These kinds of things aren't in JIRA.

Post reply on HN