diff options
| author | Gyorgy Sarvari <skandigraun@gmail.com> | 2026-02-05 07:59:49 +0100 |
|---|---|---|
| committer | Anuj Mittal <anuj.mittal@oss.qualcomm.com> | 2026-02-19 08:20:26 +0530 |
| commit | 4ea240343937d47594a7a448c7287bc0e9795d9f (patch) | |
| tree | 19c3fd0847f87e4371481e88f83c677a8ffd329f /meta-python | |
| parent | 8742c9fac0f296d2a62c8f0f0d93b9c32feb4c97 (diff) | |
| download | meta-openembedded-4ea240343937d47594a7a448c7287bc0e9795d9f.tar.gz | |
python3-twitter: mark CVE-2012-5825 patched
Details: https://nvd.nist.gov/vuln/detail/CVE-2012-5825
The Debian bugtracker[1] indicated that the issue is tracked by
upstream in github[2] (with a difference CVE ID, but same issue),
where the vulnerability was confirmed. Later in the same github issue
the solution is confirmed: the project switched to use the requests
library, which doesn't suffer from this vulnerability.
Due to this mark the CVE as patched.
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692444
[2]: https://github.com/tweepy/tweepy/issues/279
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 3ee544e7591b36a49550a263a0ec4d64b5e490e8)
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Anuj Mittal <anuj.mittal@oss.qualcomm.com>
Diffstat (limited to 'meta-python')
| -rw-r--r-- | meta-python/recipes-devtools/python/python3-twitter_4.16.0.bb | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/meta-python/recipes-devtools/python/python3-twitter_4.16.0.bb b/meta-python/recipes-devtools/python/python3-twitter_4.16.0.bb index 54379673c0..78a2b70ab3 100644 --- a/meta-python/recipes-devtools/python/python3-twitter_4.16.0.bb +++ b/meta-python/recipes-devtools/python/python3-twitter_4.16.0.bb | |||
| @@ -17,3 +17,5 @@ RDEPENDS:${PN} += "\ | |||
| 17 | python3-requests-oauthlib \ | 17 | python3-requests-oauthlib \ |
| 18 | python3-six \ | 18 | python3-six \ |
| 19 | " | 19 | " |
| 20 | |||
| 21 | CVE_STATUS[CVE-2012-5825] = "fixed-version: The vulnerability has been fixed since v3.1.0" | ||
