You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vulnerable Package issue exists @ Python-azure-powerbiembedded-6969.99.99 in branch main
This package is using dependency confusion attack
About
Dependency Confusion is a technique discovered by @alex.birsan to hijack a privately used package by registering its name (if available) on a public registry with a higher version number. This may cause artifact servers and build tools to "confuse" and use the attacker's package.
For example, consider the following private package "my-company-utils" being hosted on a private artifact server:
In case an attacker targeting "my-company-utils" package, as long as it is not occupied by someone else on the official package manager, he's free to register it. If the attacker registers it and published with a very high version number such as "v99.99.99" most likely the automatic update logic and version comparisons functions will "confuse" and prefer using the attacker's package
As an addition step of mitigation, we recommend using our open-source tool as a CI step DustiLock
Vulnerable Package issue exists @ Python-azure-powerbiembedded-6969.99.99 in branch main
This package is using dependency confusion attack
About
Dependency Confusion is a technique discovered by @alex.birsan to hijack a privately used package by registering its name (if available) on a public registry with a higher version number. This may cause artifact servers and build tools to "confuse" and use the attacker's package.
For example, consider the following private package "my-company-utils" being hosted on a private artifact server:
In case an attacker targeting "my-company-utils" package, as long as it is not occupied by someone else on the official package manager, he's free to register it. If the attacker registers it and published with a very high version number such as "v99.99.99" most likely the automatic update logic and version comparisons functions will "confuse" and prefer using the attacker's package
As an addition step of mitigation, we recommend using our open-source tool as a CI step DustiLock
Namespace: dorohayon
Repository: cxone-advanced-lab
Repository Url: https://github.com/dorohayon/cxone-advanced-lab
CxAST-Project: dorohayon/cxone-advanced-lab
CxAST platform scan: 1f20cfdb-755f-4c85-8955-8edd4bc0421c
Branch: main
Application: cxone-advanced-lab
Severity: HIGH
State: NOT_IGNORED
Status: RECURRENT
CWE: Dependency Confusion
Additional Info
The text was updated successfully, but these errors were encountered: