| Message ID | 20260109141734.1596725-3-skandigraun@gmail.com |
|---|---|
| State | Under Review |
| Headers | show |
| Series | [meta-python,1/3] python3-reportlab: mark CVE-2020-28463 patched | expand |
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 9bbbc9e8c5..ad05e0ac47 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 @@ -19,3 +19,4 @@ RDEPENDS:${PN} += "\ " CVE_PRODUCT = "tweepy" +CVE_STATUS[CVE-2012-5825] = "fixed-version: The vulnerability has been fixed since v3.1.0"
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> --- meta-python/recipes-devtools/python/python3-twitter_4.16.0.bb | 1 + 1 file changed, 1 insertion(+)