Technology

59069 readers

3743 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

214

Data from deleted GitHub repos may not really be deleted (www.theregister.com)

submitted 3 months ago by [email protected] to c/[email protected]

28 comments fedilink hide all child comments

Researchers at Truffle Security have found, or arguably rediscovered, that data from deleted GitHub repositories (public or private) and from deleted copies (forks) of repositories isn't necessarily deleted.

Joe Leon, a security researcher with the outfit, said in an advisory on Wednesday that being able to access deleted repo data – such as APIs keys – represents a security risk. And he proposed a new term to describe the alleged vulnerability: Cross Fork Object Reference (CFOR).

"A CFOR vulnerability occurs when one repository fork can access sensitive data from another fork (including data from private and deleted forks)," Leon explained.

For example, the firm showed how one can fork a repository, commit data to it, delete the fork, and then access the supposedly deleted commit data via the original repository.

The researchers also created a repo, forked it, and showed how data not synced with the fork continues to be accessible through the fork after the original repo is deleted. You can watch that particular demo.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 53 points 3 months ago (3 children)

Oh god. That means all the spaghetti code that I ever wrote is still out there.

[–] [email protected] 4 points 3 months ago

My people!

[–] [email protected] 10 points 3 months ago (1 children)

Not only just out there. I am regenerating your spaghetti code into a new context with copilot 🧑‍✈️ Your (ai-regenerated) code will be driving our military nuclear launch code base! Congratulations!

[–] [email protected] 2 points 3 months ago (1 children)

Your (ai-regenerated) code will be driving our military nuclear launch code base!

What's so difficult about writing code that checks if you have 8 zeroes?

https://gizmodo.com/for-20-years-the-nuclear-launch-code-at-us-minuteman-si-1473483587

[–] [email protected] 1 points 3 months ago

Oh I'm just the cleaning guy, so I don't really know how to code it myself. We laid off all the developers three weeks ago.

[–] [email protected] 21 points 3 months ago (2 children)

Yup. Along with the code from huge organizations. I always thought it was funny that people put their code online, blindly trusting some random company that got gobbled up by Microsoft.

[–] [email protected] 8 points 3 months ago

Your point is valid, but many (most?) enterprises don't use a forking worlflow, so I suspect open source projects will be hit harder, sadly

[–] [email protected] 14 points 3 months ago (1 children)

Along with every private key that was accidentally committed.

[–] [email protected] 11 points 3 months ago (1 children)

Ha ha, way way back in the day when I didn’t understand how keys worked, I sent a private key to another developer when they asked for my public. They were kind enough to educate me.

[–] [email protected] -3 points 3 months ago

As a lifelong troll, I would've just generated a new pub key and made a bunch of commits as you. Then two days later, I would tell you what's up once you had time to process the confusion.