diff options
| author |   Narpat Mali <narpat.mali@windriver.com> | 2022-11-18 11:49:15 +0000 |
|---|---|---|
| committer |   Armin Kuster <akuster808@gmail.com> | 2022-11-19 11:16:48 -0500 |
| commit | a8369be5eecf8485619e018e788e04bd0efdffed (patch) | |
| tree | 617a8cfb7534a878fc8dcc8cc914e6b4e425dc7d /meta-oe/recipes-devtools/nodejs/nodejs/0002-Install-both-binaries-and-use-libdir.patch | |
| parent | 1a2cc9656da5d8728f59b6823f1d9be96ca48f61 (diff) | |
| download | meta-openembedded-contrib-a8369be5eecf8485619e018e788e04bd0efdffed.tar.gz | |
python3-oauthlib: upgrade 3.2.0 -> 3.2.2
As per CVE reference, version 3.2.1 fixes the CVE-2022-36087 issue. But after upgrading the python3-oauthlib version
to 3.2.1, observed that the vulnerable code lines are still available. The same observations were reported here in github at
https://github.com/oauthlib/oauthlib/issues/837 and found that it was a mistake during 3.2.1 release preparation and due to
which vulnerable code was still existing in 3.2.1 source code.
To fix CVE-2022-36087 issue, we need to upgrade python3-oauthlib to 3.2.2 version and here are the changelog of version 3.2.2
https://github.com/oauthlib/oauthlib/blob/v3.2.2/CHANGELOG.rst
Reference :
https://nvd.nist.gov/vuln/detail/CVE-2022-36087
Upstream fix :
https://github.com/oauthlib/oauthlib/commit/2e40b412c844ecc4673c3fa3f72181f228bdbacd
Signed-off-by: Narpat Mali <narpat.mali@windriver.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'meta-oe/recipes-devtools/nodejs/nodejs/0002-Install-both-binaries-and-use-libdir.patch')
0 files changed, 0 insertions, 0 deletions