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

Software contains remote code execution vulnerability via insecure autoupdate mechanism #494

Open
sneak opened this issue Sep 29, 2024 · 2 comments

Comments

@sneak
Copy link

sneak commented Sep 29, 2024

Expected Behavior

The code I downloaded is the code that runs on my machine, and remote attackers cannot change it without permission.

Current Behavior

The software automatically downloads arbitrary code from a remote server without consent, and runs it, granting control of the local system to anyone who controls the update server.

The person in control of the update server can then use this remote code execution ability to download endpoint keys, message plaintexts, etc.

Possible Solution

Require affirmative consent for autoupdates, default autoupdates to off.

Steps to Reproduce

Run the bridge software.

Version Information

current: da76784

Context (Environment)

I was running the bridge in a docker container and it downloaded new unchecked code without consent which ran on the next launch.

Detailed Description

Autoupdates must be approved by the user before being installed.

Possible Implementation

Signal does it by requiring a click before replacing the code:

signalapp/Signal-Desktop#4578

@sneak
Copy link
Author

sneak commented Sep 29, 2024

Note that between this and #495 I am now convinced that the Proton developers do not respect my privacy or my rights to my own computer, and I'm going to be migrating all of my domains away from Protonmail. It's simply not worth the hassle to maintain my own Dockerfile to patch out these insane defaults.

@ashrude
Copy link

ashrude commented Oct 12, 2024

I appreciate what you're trying to do but how about instead of attacking proton and shenxn, why not focus on real issues, or next time bring it up without being so hostile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants