News for hackers. Stuff that matters.
Re:How We Rooted Copilot by 0xbadcafebee on Saturday July 26, 2025 @04:33PM (#44696749)
I have to give Microsoft props here. Most companies don't bother to lock things down well enough, but they were thorough.
Re:How We Rooted Copilot by stogot on Saturday July 26, 2025 @06:37PM (#44697453)
I would give the one engineer the credit for doing things better, not Microsoft. Microsoft overall culture of security is terrible. Look at the CISA report.
Re:How We Rooted Copilot by kenjackson on Saturday July 26, 2025 @07:32PM (#44697746)
What CISA report?
Re:How We Rooted Copilot by aspenmayer on Saturday July 26, 2025 @07:54PM (#44697843)
I’m guessing they mean this one:

https://www.cisa.gov/news-events/bulletins/sb25-167

> Microsoft--Microsoft 365 Copilot

> Description Ai command injection in M365 Copilot allows an unauthorized attacker to disclose information over a network.

> Published 2025-06-11

> CVSS Score 9.3

> Source Info CVE-2025-32711

https://www.cve.org/CVERecord?id=CVE-2025-32711

And maybe they are referring to this engineer from the linked advisory notes?

https://msrc.microsoft.com/update-guide/vulnerability/CVE-20...

> Acknowledgements

> Arantes (@es7evam on X) with Microsoft Aim Labs (Part of Aim Security)

Re:How We Rooted Copilot by NemosDemos on Saturday July 26, 2025 @11:26PM (#44698705)
Not OP, but guessing they were referencing this one:

https://www.cisa.gov/resources-tools/resources/CSRB-Review-S...

Re:How We Rooted Copilot by stogot on Sunday July 27, 2025 @08:05AM (#44700724)
Re:How We Rooted Copilot by homarp on Sunday July 27, 2025 @10:55AM (#44701768)
Re:How We Rooted Copilot by bigfatkitten on Saturday July 26, 2025 @08:31PM (#44697993)
Microsoft has islands of security excellence in what these days is a sea of mediocrity.
Re:How We Rooted Copilot by 0xbadcafebee on Saturday July 26, 2025 @09:51PM (#44698275)
Okay, so I give the team that put this together credit. Hopefully the parent company sees based on this that it's worth letting teams invest more in quality and security work, over features.
Re:How We Rooted Copilot by dudeinjapan on Sunday July 27, 2025 @02:07AM (#44699212)
We should give all the credit to the Product Manager because he told the engineers to make it secure.
Re:How We Rooted Copilot by chrz on Sunday July 27, 2025 @04:37AM (#44699811)
Lets send a thank you letter to Bill Gates
Re:How We Rooted Copilot by dudeinjapan on Sunday July 27, 2025 @07:11AM (#44700426)
I presume you mean Bill Gates Sr. because he fathered Bill Gates.
Re:How We Rooted Copilot by bravesoul2 on Sunday July 27, 2025 @04:55AM (#44699885)
I bet the container was in an isolated VM too.
Re:How We Rooted Copilot by j-krieger on Sunday July 27, 2025 @06:20AM (#44700225)
Every infra I ever worked in used this pattern to a degree. Many proxmox vm's in a kubernetes cluster.
Re:How We Rooted Copilot by silverliver on Sunday July 27, 2025 @06:54AM (#44700372)
I've seen people manually create a separate unprivileged user on the host for each VM they run, so for them the pattern becomes:

1. VM running on hypervisor as unprivileged host user

2. Container running in VM as unprivileged vm user

3. Payload running in container as unprivileged container user.

Not sure whether layered isolation is worth the increased attack surface. For normal users (not targets of state actors), it probably is.