Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OVE-20221017-0001: PolyMC appears to be compromised #196460

Closed
LunNova opened this issue Oct 17, 2022 · 19 comments
Closed

OVE-20221017-0001: PolyMC appears to be compromised #196460

LunNova opened this issue Oct 17, 2022 · 19 comments
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one

Comments

@LunNova
Copy link
Member

LunNova commented Oct 17, 2022

There is a developing situation involving polymc, the package is potentially compromised.

PolyMC relies on meta files retrieved from meta.polymc.org to determine what jars (the java executable file format) to download when launching mod packs. Due to this online feature, it is not safe to continue using old versions of PolyMC if the maintainer has been compromised as these meta files could be updated to download a malicious jar.

Here is an example of one of the meta files org.quiltmc.quilt-loader/0.17.5-beta.9.json. This file does not appear to be malicious, it is just here to demonstrate how the meta system works and why this is a problem.

Situation started with this commit PolyMC/PolyMC@ccf2825 and the owner dropping all other maintainers from the repo.

I do not know for sure whether this is an account hack or "just" drama / the owner going rogue, figured it's best to open this to track the situation. In either case a maintainer suddenly removing access from all other maintainers is a bad sign.


See also:

@LunNova LunNova added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Oct 17, 2022
wozeparrot added a commit to wozeparrot/solarsys that referenced this issue Oct 17, 2022
@LunNova
Copy link
Member Author

LunNova commented Oct 17, 2022

ccing maintainers @cleverca22 @starcraft66

@Infinidoge
Copy link
Contributor

Infinidoge commented Oct 17, 2022

Some additional information from the (now former) maintainers who were removed by Lenny Lennington. These messages are from the Discord server they made (Titled PlaceholderMC), as they work to fork the project (See the PlaceholderMC org and PlaceholderMC repository
The Discord server these messages are in can be found here

From #announcements: (Message link)

LennyMcLenington (one of the founders of polymc and a maintainer), who had most of the access, went rouge. We don't know at this time if it's him or if his account was compromised
he removed all of our perms and removed us from the github org
I suggest not downloading or updating PolyMC until this situation is over
Flatpak and MPR (Ubuntu/Debian) are under my control and should be safe. Currently checking status of the other packages.
however i wouldnt open polymc even from these
ABOUT CURRENT INSTALLATIONS:
IF you turn off internet everything is safe, but if you create new instances or shit updates itself metaserver could possibly be compromised

Also CCing some of the former PolyMC maintainers, who are in the PlaceholderMC discord:
@Scrumplex, @dada513, @txtsd

@Scrumplex
Copy link
Member

Can confirm

@LunNova
Copy link
Member Author

LunNova commented Oct 17, 2022

Should we yank the package?

Is there a patch we can apply to disable the online updating features to make it safe?

@an-empty-string
Copy link
Member

an-empty-string commented Oct 17, 2022

Is there a patch we can apply to disable the online updating features to make it safe?

The meta server seems to be configurable, and information is circulating about how to use the MultiMC metaserver instead: https://gist.github.com/Earthcomputer/dc65391f84a2c19ebac6c33506fd7751 -- but this by itself is probably not a workable solution for nixpkgs, given the history here.

Not using a meta server at all doesn't appear to be an option (edit: it is, see @Infinidoge's notes below -- but I think this disables creation/editing of instances? if this is the case, maybe not good for a patch to the package), but the current full contents of the PolyMC meta server are available at https://github.com/PolyMC/meta-polymc -- anyone forking could use this + the update scripts at https://github.com/PolyMC/meta to populate a trusted meta server, it looks like.

@Infinidoge
Copy link
Contributor

To effectively disable using the metadata server, you can fill the server setting box with garbage/a dead URL. (Settings -> APIs, Metadata Server)

@samueldr
Copy link
Member

Instead of yanking, there's a meta attribute that can be used for insecure packages, the OVE link could be used I suppose. See meta.knownVulnerabilities uses.

@LunNova
Copy link
Member Author

LunNova commented Oct 17, 2022

We can make a PR after finishing up work in a few hours, I'd appreciate if someone else gets it sooner.

@starcraft66
Copy link
Member

Not using a metadata server will effectively make the launcher useless unless you already have instances created and don't intend to modify them. Since there doesn't seem to be any alternative meta-server other than the MultiMC one at the moment (afaik MultiMC is not okay with other launchers and forks using their official meta, correct me if I am wrong), I will put up a PR marking the package vulnerable for the time being.

@starcraft66
Copy link
Member

It looks like an-empty-string@9d27de8 was committed while I was typing this message, thanks.

@LunNova LunNova changed the title polymc: potentially compromised, definitely drama? OVE-20221017-0001: PolyMC appears to be compromised Oct 17, 2022
@leo60228
Copy link
Member

The other maintainers seem to have given up on regaining control and have created a new project: https://github.com/PlaceholderMC/PlaceholderMC

@leo60228
Copy link
Member

leo60228 commented Oct 17, 2022

Is there a patch we can apply to disable the online updating features to make it safe?

This would make the launcher at least mostly unusable (though it might be cached for existing users). The game and mod loaders are downloaded via the meta repository.

@TheArcaneBrony
Copy link
Contributor

as for a possible patch, the binary could be renamed and replaced with a shellscript that sed's the url out of configs

@starcraft66
Copy link
Member

Regarding PlaceholderMC: We can re-brand the package once PlaceholderMC figures out its branding and puts up a metadata server. Until then, PolyMC will installable as an insecure package or via its upstream flake. I am in contact with @Scrumplex and monitoring the situation in their discord.

@LunNova
Copy link
Member Author

LunNova commented Oct 17, 2022

Probably best to keep this open as a tracking issue until we have a replacement?

@starcraft66
Copy link
Member

@LunNova opened tracking issue #196480

@Infinidoge
Copy link
Contributor

Infinidoge commented Oct 17, 2022

The PlaceholderMC developers have created a new Metadata Server which is not compromised:
https://meta.scrumplex.rocks/v1/ (Uses this underlying repository)

@Scrumplex
Copy link
Member

The PlaceholderMC developers have created a new Metadata Server which is not compromised: https://meta.scrumplex.rocks/v1/ (Uses this underlying repository)

Can confirm!

@KaspianDev
Copy link

KaspianDev commented Nov 2, 2022

@oxalica nothing ever was compromised, just saying

Edit: Yall should stop fucking lying to yourselves. Someone having different political views doesn't mean you can post false information online about them or their projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one
Projects
None yet
Development

No branches or pull requests

9 participants