pip-audit fails with 2 vulnerabilities (GHSA-m6vm-8g8v-xfjh and GHSA-8849-5h85-98qw)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1k
- Avg merge
- 22h 17m
- Merged PRs (30d)
- 3
Description
Expected behaviour
When I ran
$ pip-audit -r /path/to/requirements.txt
where the requirements.txt has dependency on the latest version of opencv-python
opencv-python==4.7.0.72
, no error is supposed to be happened.
Actual behaviour
The following two errors are raised.
Name Version ID Fix Versions
------------- -------- ------------------- ------------
opencv-python 4.7.0.72 GHSA-m6vm-8g8v-xfjh
opencv-python 4.7.0.72 GHSA-8849-5h85-98qw
Steps to reproduce
$ mkdir tempdir
$ cd tempdir
$ echo "opencv-python==4.7.0.72" > requirements.txt
$ pip install pip-audit==2.5.3
$ pip-audit -r requirements.txt
Found 2 known vulnerabilities in 1 package
Name Version ID Fix Versions
------------- -------- ------------------- ------------
opencv-python 4.7.0.72 GHSA-m6vm-8g8v-xfjh
opencv-python 4.7.0.72 GHSA-8849-5h85-98qw
My environment:
$ python --version
Python 3.9.16
Issue submission checklist
- This is not a generic OpenCV usage question (looking for help for coding, other usage questions, homework etc.)
- I have read the README of this repository and understand that this repository provides only an automated build toolchain for OpenCV Python packages (there is no actual OpenCV code here)
- The issue is related to the build scripts in this repository, to the pre-built binaries or is a feature request (such as "please enable this additional dependency")
- I'm using the latest version of
opencv-python
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report with requirements.txt containing opencv-python==4.7.0.72 and pip-audit==2.5.3, using the stated Python 3.9.16 environment. Review the two vulnerability identifiers and the generated package metadata to determine whether this repository has an actionable build or release change; done requires a defined resolution for the audit result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100