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

Sparkle security issue #2401

Closed
Fryguy opened this issue Feb 4, 2016 · 2 comments
Closed

Sparkle security issue #2401

Fryguy opened this issue Feb 4, 2016 · 2 comments

Comments

@Fryguy
Copy link
Contributor

Fryguy commented Feb 4, 2016

See sparkle-project/Sparkle#720

All Sparkle versions older than 1.13.1 which fetch appcast or release notes over insecure HTTP connection are vulnerable to a man-in-the-middle attack that can lead to disclosure of local files or remote code execution.

Applications using Sparkle with HTTPS appcast feed URLs and HTTPS release notes links (if any) are safe.

From what I can tell, OpenEmu uses Sparkle 1.7.1, but I can't tell if it's using HTTP or HTTPS. Either way, I thought I'd raise up the issue here.

@clobber
Copy link
Member

clobber commented Feb 5, 2016

Thanks. We've used HTTPS since the beginning.

@Eitot
Copy link

Eitot commented Feb 11, 2016

@clobber: No plans to update to a newer version of Sparkle?

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

3 participants