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

Lodash Prototype Pollution vulnerability in version 1.12.1 #12441

Closed
thelgevold opened this issue Apr 4, 2019 · 5 comments
Closed

Lodash Prototype Pollution vulnerability in version 1.12.1 #12441

thelgevold opened this issue Apr 4, 2019 · 5 comments
Labels
Node Node.js-specific issue ThirdParty upstream problems

Comments

@thelgevold
Copy link

thelgevold commented Apr 4, 2019

The problem

Getting a lodash Prototype Pollution vulnerability reported from npm when installing version 1.12.1 of appium.

Environment

  • Appium version (or git revision) that exhibits the issue: 1.12.1
  • Last Appium version that did not exhibit the issue (if applicable):
  • Desktop OS/version used to run Appium: OSX
  • Node.js version (unless using Appium.app|exe):
  • Npm or Yarn package manager: npm
  • Mobile platform/version under test:
  • Real device or emulator/simulator:
  • Appium CLI or Appium.app|exe:

Details

Getting a lodash Moderate Prototype Pollution vulnerability when installing version 1.12.1 of appium.

Would you be able to publish a new release with an upgraded version of lodash?

If necessary, describe the problem you have been experiencing in more detail.

Link to Appium logs

Create a GIST which is a paste of your full Appium logs, and link them here.
Do NOT paste your full Appium logs here, as it will make this issue very long and hard to read!
If you are reporting a bug, always include Appium logs!

Code To Reproduce Issue [ Good To Have ]

run an npm install of appium

@mykola-mokhnach
Copy link
Collaborator

Closed as incomplete

@thelgevold
Copy link
Author

More details added. Please re-open.

@dpgraham
Copy link
Contributor

dpgraham commented Apr 5, 2019

Will need to wait on: Samsung/appium-tizen-driver#15

It's an external driver that uses it.

@mykola-mokhnach mykola-mokhnach added the ThirdParty upstream problems label Apr 8, 2019
@mykola-mokhnach
Copy link
Collaborator

I think it makes sense to track the issue in Tizen repository rather than here. We anyway cannot change nothing from our side.

@lock
Copy link

lock bot commented Apr 15, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Node Node.js-specific issue ThirdParty upstream problems
Projects
None yet
Development

No branches or pull requests

3 participants