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

Bundles vulnerable copy of Expat - please update to 2.2.1 #407

Closed
hartwork opened this issue Jun 21, 2017 · 3 comments
Closed

Bundles vulnerable copy of Expat - please update to 2.2.1 #407

hartwork opened this issue Jun 21, 2017 · 3 comments

Comments

@hartwork
Copy link

Hi!

This repository bundles an outdated vulnerable copy of Expat 2.2.0. Please update your copy to version 2.2.1 with the latest security fixes. A change log with details is available at https://github.com/libexpat/libexpat/blob/master/expat/Changes. If you happen to run into compile errors, please check the post-2.2.1 commits in Git as well. Thank you!

Best

 
Sebastian

@vslavik
Copy link
Owner

vslavik commented Jun 25, 2017

Thanks, I'm well aware of the release, just as I am aware of how I used Expat (not impacted, I/O internal to Poedit, communicating with a helper CLI tool). In fact, it's no longer used in v2, I just forgot to delete it — thanks for drawing my attention to it.

P.S. You may want to improve your crawler to detect submodule references, like this one (upgrade pending acceptance or rejection of libexpat/libexpat#60).

@hartwork
Copy link
Author

My crawler so far was plain filename:xmlparse.c XML_ParserCreate using GitHub's (rather limited) own search. I'm open to better crawlers if you have ideas.
I think WinSparkle's use of Expat as a Git submodule does not show up at Expat's list of dependent repositories because it's using SourceForge for the remote URL still (while some GitHub UI places tell otherwise).
PS: I have added WinSparkle to the list of Expat users now.

@vslavik
Copy link
Owner

vslavik commented Jun 25, 2017

using GitHub's (rather limited) own search

Ah, I see.

because it's using SourceForge for the remote URL still

That's weird, not since vslavik/winsparkle@a4abbed...

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