PYSEC-2024-154 json
A number of releases of ultralytics contained malicious crypto miner software.
published last yr. modified 4mo ago
- cvss
- 8.6
- version 3.1, OSV
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Ultralytics has identified a supply chain attack affecting affecting multiple versions of the ultralytics package. The compromised versions contained unauthorized code that downloaded and executed cryptocurrency mining software when instantiating YOLO models. This code was injected into the PyPI release artifacts and was not present in the public GitHub repository.
Patch / fix
- pypi ultralytics 8.3.47
- github.com/ultralytics/ultralytics#18020 pull request
- github.com/ultralytics/ultralytics#18052 pull request
- github.com/ultralytics/ultralytics#18111 pull request
- github.com/ultralytics/ultralytics/releases/tag/v8.3.48 release
Is PYSEC-2024-154 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| OSV | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | ultralytics | >=8.3.41, <8.3.47 |
8.3.47 |
References
-
github.com
/ultralytics/ultralytics/pull/18020#issuecomment-2525180194
web
-
github.com
/ultralytics/ultralytics/pull/18052
patch
-
github.com
/ultralytics/ultralytics/pull/18111
patch
-
github.com
/ultralytics/ultralytics/releases/tag/v8.3.48
patch
-
inspector.pypi.io
/project/ultralytics/8.3.41/packages/d0/99/13d92174aa6a470d348a95e31164769f2cdf77838ea3c3e3fd476285777d/ultral
evidence
-
github.com
/ultralytics/ultralytics/issues/18027
report
-
blog.yossarian.net
/2024/12/06/zizmor-ultralytics-injection
article
Sources
- OSV PYSEC-2024-154
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.