Upgrade potentially vulnerable libvpx

[proberts-sc]

opencv-python bundles libvpx SOs. CVE-2023-5217 identified a vulnerability in libvpx. The vulnerability was fixed in libvpx v1.13.1 released Sep 29, but the latest opencv-python 4.8.1.78 was released 2 days earlier (Sep 27), so it's possible the latest opencv-python is still bundling a vulnerable libvpx.

Request: Rebuild using updated libvpx >=1.13.1 or confirm that opencv-python 4.8.1.78 already includes libvpx >=1.13.1.

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

[dkurt]

From installed opencv-python==4.8.1.78 by pip:

$ ldd ~/venv3/lib/python3.10/site-packages/cv2/cv2.abi3.so  | grep vpx
libvpx-2c989c7f.so.8.0.0 => /home/dkurt/venv3/lib/python3.10/site-packages/cv2/../opencv_python.libs/libvpx-2c989c7f.so.8.0.0 (0x00007f95a7203000)

I cannot track any commit hash which starts from 2c989c7f. Only this user's comment which probably refers to the same version of OpenCV dependency means the same Docker image could be used for build: Nuullll/ipex-sd-docker-for-arc-gpu#16 (comment)

@asmorkalov, can you please check a build date of the image used for OpenCV from pip (x86 Linux, for example)?