Comment by mmsc
2 years ago
>This is such an enormous attack vector for all organizations that use GitHub that we’re introducing a new term: Cross Fork Object Reference (CFOR)
Have we stopped naming vulnerabilities cute and fuzzy names and started inventing class names instead? Does this have a logo? Has this issue been identified anywhere else?
Introducing a new vulnerability... Git Forked™!
chatgpt: Create a logo image of a fork impaling a small gnome named "code"
Much better name.
It's very formally called Cross Fork Object Reference (CFOR). But commonly known as Git Forked! (Including the exclamation mark).
Best I could come up with after thinking for a moment is "AGHAST": "Astonishing GitHub Availability (of) Source Trees".
But I'm still not entirely satisfied with the word choice.