mirror of
https://github.com/swisskyrepo/PayloadsAllTheThings
synced 2024-06-30 19:02:55 +00:00
32 lines
1.6 KiB
Markdown
32 lines
1.6 KiB
Markdown
# Dependency Confusion
|
|
|
|
> A dependency confusion attack or supply chain substitution attack occurs when a software installer script is tricked into pulling a malicious code file from a public repository instead of the intended file of the same name from an internal repository.
|
|
|
|
## Summary
|
|
|
|
* [Tools](#tools)
|
|
* [Exploit](#exploitation)
|
|
* [References](#references)
|
|
|
|
|
|
## Tools
|
|
|
|
* [Confused](https://github.com/visma-prodsec/confused)
|
|
|
|
## Exploit
|
|
|
|
Look for `npm`, `pip`, `gem` packages, the methodology is the same : you register a public package with the same name of private one used by the company and then you wait for it to be used.
|
|
|
|
### NPM example
|
|
|
|
* List all the packages (ie: package.json, composer.json, ...)
|
|
* Find the package missing from https://www.npmjs.com/
|
|
* Register and create a **public** package with the same name
|
|
* Package example : https://github.com/0xsapra/dependency-confusion-expoit
|
|
|
|
## References
|
|
|
|
* [Exploiting Dependency Confusion - 2 Jul 2021 - 0xsapra](https://0xsapra.github.io/website//Exploiting-Dependency-Confusion)
|
|
* [Dependency Confusion: How I Hacked Into Apple, Microsoft and Dozens of Other Companies - Alex Birsan - 9 Feb 2021](https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610)
|
|
* [Ways to Mitigate Risk When Using Private Package Feeds - Microsoft - 29/03/2021](https://azure.microsoft.com/en-gb/resources/3-ways-to-mitigate-risk-using-private-package-feeds/)
|
|
* [$130,000+ Learn New Hacking Technique in 2021 - Dependency Confusion - Bug Bounty Reports Explained](https://www.youtube.com/watch?v=zFHJwehpBrU ) |