Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

Malicious package in protractor lib dependencies #4844

Closed
IgorSasovets opened this issue Jun 5, 2018 · 7 comments
Closed

Malicious package in protractor lib dependencies #4844

IgorSasovets opened this issue Jun 5, 2018 · 7 comments

Comments

@IgorSasovets
Copy link
Contributor

Security issue

  • Node Version: 8.4.0
  • Protractor Version: 5.3.2

Hi, Team! Recently I found vulnerable package in protractor dependencies when was analyzing small protractor project using Snyk tool. I've opened issue in webdriver-js-extender repository and now waiting for response. Issue related to usage of outdated selenium-webdriver package version. They've already fixed it and replaced adm-zip(vulnerable package previously used by selenium-webdriver). Please pay attention to this.

Best regards,
Igor
screen shot 2018-06-04 at 12 31 29 pm

@IgorSasovets IgorSasovets changed the title Malicious package in protractor lib Malicious package in protractor lib dependencies Jun 5, 2018
@awarecan
Copy link

awarecan commented Jun 6, 2018

I bet this pending PR angular/webdriver-js-extender#12 will fix it.

@IgorSasovets
Copy link
Contributor Author

Hi, @awarecan ! I think so too and waiting for feedback from core team.

@Quenty
Copy link

Quenty commented Jun 26, 2018

See https://github.com/snyk/zip-slip-vulnerability for more details, this was fixed in version 0.4.9, protractor currently uses 0.4.4 and should be updated.

cthackers/adm-zip#212

@IgorSasovets
Copy link
Contributor Author

Hi, @Quenty ! Thanks for investigation) As I said, adm-zip replaced with jszip in selenium-webdriver package. So, update of webdriver-js-extender dependencies will fix this issue.

@IgorSasovets
Copy link
Contributor Author

#4882

@kylecordes
Copy link

(BTW, from the point of view of a casual follower of the project, it would feel a lot better if someone tagged as a contributor/owner were to drop a comment in about the likelihood of merging+shipping a fix to a scary sounding issue ("malicious package"!) promptly.)

@IgorSasovets
Copy link
Contributor Author

Can be closed now because of #4882.

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

No branches or pull requests

4 participants