this post was submitted on 01 Feb 2024
191 points (99.5% liked)

Fediverse

17450 readers
44 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] redcalcium@lemmy.institute 29 points 6 months ago (2 children)

This advisory will be edited with more details on 2024/02/15, when admins have been given some time to update, as we think any amount of detail would make it very easy to come up with an exploit.

But the commit to fix insufficient origin validation is already visible right there in the repo?

[–] losttourist@kbin.social 31 points 6 months ago (1 children)

Without a published POC there's a slightly longer window before clueless script kiddies start having a go at exploiting the vulnerability, though.

[–] fartsparkles@sh.itjust.works 6 points 6 months ago (1 children)

Script kiddies aren’t the first ones to take advantage of vulns, threat actors are.

[–] jmcs@discuss.tchncs.de 8 points 6 months ago (1 children)

That doesn't mean you shouldn't try to contain the blast radius.

[–] pelespirit@sh.itjust.works 3 points 6 months ago (1 children)

Could you explain what you're saying in common language?

[–] cypherpunks@lemmy.ml 23 points 6 months ago* (last edited 6 months ago) (2 children)

The lack of details in the advisory is only a minor impediment for a malicious person who wants to figure out how to implement their own exploit for this vulnerability. Anyone can read the patch that fixes it and figure it out.

TLDR: if you run your own instance, update it ASAP. If an instance you rely on hasn't updated yet, consider asking its admins to do so. And if they don't update it soon, you might want to reconsider your choice of instance.

[–] elvith@feddit.de 7 points 6 months ago

And if they don't update it soon, you might want to reconsider your choice of instance.

The advisory went up about 4h ago. About 3h ago, my instance admin sent out an announcement that the patch had been applied. That was before I even heard about the issue.

Nice work :)