{ "$meta": { "advisory": "PyUp.io metadata", "base_domain": "https://pyup.io", "timestamp": 1769925653 }, "10cent10": [ { "advisory": "10Cent10 is a malicious package, typosquatting. It steals Discord access tokens, passwords, and even stage dependency confusion attacks.\r\nhttps://thehackernews.com/2021/11/11-malicious-pypi-python-libraries.html", "cve": "PVE-2022-45461", "id": "pyup.io-45461", "more_info_path": "/vulnerabilities/PVE-2022-45461/45461", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "10cent11": [ { "advisory": "10Cent11 is a malicious package, typosquatting. It steals Discord access tokens, passwords, and even stage dependency confusion attacks.\r\nhttps://thehackernews.com/2021/11/11-malicious-pypi-python-libraries.html", "cve": "PVE-2022-45462", "id": "pyup.io-45462", "more_info_path": "/vulnerabilities/PVE-2022-45462/45462", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "11cent": [ { "advisory": "11Cent is a malicious package. It exfiltrates data from the host where it is installed.\r\nhttps://bertusk.medium.com/malicious-pypi-packages-found-exfiltrating-data-and-opening-reverse-shells-87d4afb5d99e", "cve": "PVE-2022-47995", "id": "pyup.io-47995", "more_info_path": "/vulnerabilities/PVE-2022-47995/47995", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "123bla": [ { "advisory": "The OpenSSF Package Analysis project identified '123bla' @ 0.0.1 (pypi) as malicious.", "cve": "PVE-2024-73967", "id": "pyup.io-73967", "more_info_path": "/vulnerabilities/PVE-2024-73967/73967", "specs": [ ">=0", "<=0" ], "v": ">=0,<=0" } ], "12cent": [ { "advisory": "12Cent is a malicious package. It exfiltrates data from the host where it is installed.\r\nhttps://bertusk.medium.com/malicious-pypi-packages-found-exfiltrating-data-and-opening-reverse-shells-87d4afb5d99e", "cve": "PVE-2022-47999", "id": "pyup.io-47999", "more_info_path": "/vulnerabilities/PVE-2022-47999/47999", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "13cent": [ { "advisory": "13Cent is a malicious package. It exfiltrates data from the host where it is installed.\r\nhttps://bertusk.medium.com/malicious-pypi-packages-found-exfiltrating-data-and-opening-reverse-shells-87d4afb5d99e", "cve": "PVE-2022-48000", "id": "pyup.io-48000", "more_info_path": "/vulnerabilities/PVE-2022-48000/48000", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "14cent": [ { "advisory": "14Cent is a malicious package. It exfiltrates data from the host where it is installed.\r\nhttps://bertusk.medium.com/malicious-pypi-packages-found-exfiltrating-data-and-opening-reverse-shells-87d4afb5d99e", "cve": "PVE-2022-48001", "id": "pyup.io-48001", "more_info_path": "/vulnerabilities/PVE-2022-48001/48001", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "15cent": [ { "advisory": "15Cent is a malicious package. It exfiltrates data from the host where it is installed.\r\nhttps://bertusk.medium.com/malicious-pypi-packages-found-exfiltrating-data-and-opening-reverse-shells-87d4afb5d99e", "cve": "PVE-2022-47996", "id": "pyup.io-47996", "more_info_path": "/vulnerabilities/PVE-2022-47996/47996", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "16cent": [ { "advisory": "16Cent is a malicious package. It exfiltrates data from the host where it is installed.\r\nhttps://bertusk.medium.com/malicious-pypi-packages-found-exfiltrating-data-and-opening-reverse-shells-87d4afb5d99e", "cve": "PVE-2022-47997", "id": "pyup.io-47997", "more_info_path": "/vulnerabilities/PVE-2022-47997/47997", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "aa-timezones": [ { "advisory": "Aa-timezones 1.12.0 updates its NPM dependency 'moment-timezone' to include security fixes.\r\nhttps://github.com/ppfeufer/aa-timezones/pull/58/commits/8f382a1a3a3f9ddd77f10fb3b1d3380e6267eab1\r\nhttps://github.com/moment/moment-timezone/security/advisories/GHSA-56x4-j7p9-fcf9", "cve": "PVE-2022-51033", "id": "pyup.io-51033", "more_info_path": "/vulnerabilities/PVE-2022-51033/51033", "specs": [ "<1.12.0" ], "v": "<1.12.0" }, { "advisory": "Aa-timezones 1.12.0 updates its NPM dependency 'moment-timezone' to include security fixes.\r\nhttps://github.com/ppfeufer/aa-timezones/pull/58/commits/8f382a1a3a3f9ddd77f10fb3b1d3380e6267eab1\r\nhttps://github.com/moment/moment-timezone/security/advisories/GHSA-v78c-4p63-2j6c", "cve": "PVE-2023-54978", "id": "pyup.io-54978", "more_info_path": "/vulnerabilities/PVE-2023-54978/54978", "specs": [ "<1.12.0" ], "v": "<1.12.0" } ], "aadhaar-py": [ { "advisory": "Aadhaar-py 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "PVE-2021-44525", "id": "pyup.io-44561", "more_info_path": "/vulnerabilities/PVE-2021-44525/44561", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Aadhaar-py 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22815", "id": "pyup.io-44607", "more_info_path": "/vulnerabilities/CVE-2022-22815/44607", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Aadhaar-py 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "PVE-2022-44524", "id": "pyup.io-44604", "more_info_path": "/vulnerabilities/PVE-2022-44524/44604", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Aadhaar-py 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22816", "id": "pyup.io-44606", "more_info_path": "/vulnerabilities/CVE-2022-22816/44606", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Aadhaar-py 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22817", "id": "pyup.io-44605", "more_info_path": "/vulnerabilities/CVE-2022-22817/44605", "specs": [ "<2.0.1" ], "v": "<2.0.1" } ], "aamiles": [ { "advisory": "The AAmiles package in PyPI v0.1.0 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.", "cve": "CVE-2022-33001", "id": "pyup.io-62691", "more_info_path": "/vulnerabilities/CVE-2022-33001/62691", "specs": [ "==0.1.0" ], "v": "==0.1.0" } ], "aba-cli-scrapper": [ { "advisory": "Aba-cli-scrapper 0.3.0 replaces its dependency 'pymysql' as a DBAPIS with 'mysqlclient' to avoid a SQLi vulnerability.", "cve": "CVE-2024-36039", "id": "pyup.io-72564", "more_info_path": "/vulnerabilities/CVE-2024-36039/72564", "specs": [ "<0.3.0" ], "v": "<0.3.0" } ], "abattlemetrics": [ { "advisory": "Affected versions of the abattlemetrics package are vulnerable to Information Disclosure due to logging sensitive HTTP request headers when handling error responses. In abattlemetrics.client._request, the code previously invoked log.exception('Response %d caused with:\\n Headers: %s\\n Params: %s', r.status, headers, params, ...), which could write secrets present in headers (such as API tokens or cookies) to log files; the fix replaces header logging with route.method and route.path only.", "cve": "PVE-2025-80900", "id": "pyup.io-80900", "more_info_path": "/vulnerabilities/PVE-2025-80900/80900", "specs": [ "<0.1.0" ], "v": "<0.1.0" } ], "abe": [ { "advisory": "Abe (aka bitcoin-abe) through 0.7.2, and 0.8pre, allows XSS in __call__ in abe.py because the PATH_INFO environment variable is mishandled during a PageNotFound exception.", "cve": "CVE-2020-11944", "id": "pyup.io-62858", "more_info_path": "/vulnerabilities/CVE-2020-11944/62858", "specs": [ "<0.7.2", "==0.8pre" ], "v": "<0.7.2,==0.8pre" } ], "abiflows": [ { "advisory": "Abiflows 0.6 includes a security patch for the function 'test_abipy_manager_from_file' in 'abiflows/fireworks/utils/tests/test_fw_utils.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/abinit/abiflows/commit/479b957c3b1abe41d85aaff2d14439605ddc5d0b#diff-5a814c49249ffdc2d551933c1bec95c4b2fe64d0619470085c5fef247fea2309", "cve": "CVE-2017-18342", "id": "pyup.io-41306", "more_info_path": "/vulnerabilities/CVE-2017-18342/41306", "specs": [ "<0.6" ], "v": "<0.6" } ], "abilian-devtools": [ { "advisory": "Abilian-devtools 0.4.4 includes a fix for a command injection vulnerability.\r\nhttps://github.com/abilian/abilian-devtools/commit/9d71b0d3b6b467589d58aacc932ca3dc7e524ce2", "cve": "PVE-2023-62205", "id": "pyup.io-62205", "more_info_path": "/vulnerabilities/PVE-2023-62205/62205", "specs": [ "<0.4.4" ], "v": "<0.4.4" } ], "abracadabra": [ { "advisory": "Abracadabra 0.0.4 updates its dependency 'notebook' to include a security fix.", "cve": "CVE-2020-26215", "id": "pyup.io-39264", "more_info_path": "/vulnerabilities/CVE-2020-26215/39264", "specs": [ "<0.0.4" ], "v": "<0.0.4" } ], "accelbyte-py-sdk": [ { "advisory": "Affected versions of accelbyte-py-sdk are potentially vulnerable to Improper Authorization (CWE-285), whereby the resolve method in accelbyte_py_sdk/core/_proto_http_request.py prematurely accepts COOKIE_AUTH and bypasses additional Basic or Bearer auth requirements.", "cve": "PVE-2025-77023", "id": "pyup.io-77023", "more_info_path": "/vulnerabilities/PVE-2025-77023/77023", "specs": [ "<0.75.0" ], "v": "<0.75.0" } ], "accesscontrol": [ { "advisory": "AccessControl 4.4, 5.8 and 6.2 include a fix for CVE-2023-41050: Python's \"format\" functionality allows someone controlling the format string to \"read\" objects accessible (recursively) via attribute access and subscription from accessible objects. Those attribute accesses and subscriptions use Python's full blown 'getattr' and 'getitem', not the policy restricted 'AccessControl' variants '_getattr_' and '_getitem_'. This can lead to critical information disclosure. 'AccessControl' already provides a safe variant for 'str.format' and denies access to 'string.Formatter'. However, 'str.format_map' is still unsafe. Affected are all users who allow untrusted users to create 'AccessControl' controlled Python code and execute it.", "cve": "CVE-2023-41050", "id": "pyup.io-60983", "more_info_path": "/vulnerabilities/CVE-2023-41050/60983", "specs": [ "<4.4", ">=5.0,<5.8", ">=6.0,<6.2" ], "v": "<4.4,>=5.0,<5.8,>=6.0,<6.2" }, { "advisory": "Accesscontrol 5.3.1 includes a fix for a race condition vulnerability.\r\nhttps://github.com/zopefoundation/AccessControl/pull/125", "cve": "PVE-2023-60951", "id": "pyup.io-60951", "more_info_path": "/vulnerabilities/PVE-2023-60951/60951", "specs": [ "<5.3.1" ], "v": "<5.3.1" }, { "advisory": "Affected versions of Accesscontrol are vulnerable to untrusted access to AccessControl.userfolder.UserFolder.data.", "cve": "PVE-2024-74011", "id": "pyup.io-74011", "more_info_path": "/vulnerabilities/PVE-2024-74011/74011", "specs": [ "<7.2" ], "v": "<7.2" }, { "advisory": "Affected versions of the AccessControl package are vulnerable to Improper Access Control due to missing permission restrictions on the data attribute in AccessControl.userfolder.UserFolder. The vulnerability exists in versions before 7.2, where the UserFolder's data property, which stores user account information, lacks proper role-based access controls and can be accessed without authentication. Anonymous users can exploit this vulnerability by directly accessing and deleting the user data maintained by UserFolder objects, causing a complete loss of authentication data that prevents any privileged users from logging in and potentially rendering the entire Zope application inaccessible for administrative functions.", "cve": "CVE-2024-51734", "id": "pyup.io-78818", "more_info_path": "/vulnerabilities/CVE-2024-51734/78818", "specs": [ "<7.2" ], "v": "<7.2" }, { "advisory": "Accesscontrol 4.3 and 5.3 include a fix for CVE-2021-32807: Remote Code Execution via unsafe classes in otherwise permitted modules .\r\nhttps://github.com/advisories/GHSA-qcx9-j53g-ccgf", "cve": "CVE-2021-32807", "id": "pyup.io-42315", "more_info_path": "/vulnerabilities/CVE-2021-32807/42315", "specs": [ ">=4.0,<4.3", ">=5.0,<5.2" ], "v": ">=4.0,<4.3,>=5.0,<5.2" } ], "acqusition": [ { "advisory": "acqusition is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/", "cve": "PVE-2021-34978", "id": "pyup.io-34978", "more_info_path": "/vulnerabilities/PVE-2021-34978/34978", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "acryl-datahub": [ { "advisory": "DataHub under 0.8.45 uses the X-DataHub-Actor HTTP header to identify the user making requests without authentication. However, this can be exploited by attackers who can manipulate the case of the header (e.g., X-DATAHUB-ACTOR), leading to potential authorization bypass and unauthorized actions. This issue, identified and reported by GitHub Security Lab, is known as GHSL-2022-079.\r\nhttps://github.com/datahub-project/datahub/security/advisories/GHSA-qgp2-qr66-j8r8", "cve": "CVE-2023-25559", "id": "pyup.io-63343", "more_info_path": "/vulnerabilities/CVE-2023-25559/63343", "specs": [ "<0.8.45" ], "v": "<0.8.45" }, { "advisory": "DataHub's AuthServiceClient, particularly versions below 0.8.45, creates JSON strings using format strings with user-controlled data. This approach lets potential attackers alter these JSON strings and forward them to the backend, causing potential misuse and authentication bypasses. This could lead to the creation of system accounts, potentially resulting in full system compromise. This vulnerability was discovered and reported by the GitHub Security lab and is being tracked under GHSL-2022-081.\r\nhttps://github.com/datahub-project/datahub/security/advisories/GHSA-7wc6-p6c4-522c", "cve": "CVE-2023-25561", "id": "pyup.io-63339", "more_info_path": "/vulnerabilities/CVE-2023-25561/63339", "specs": [ "<0.8.45" ], "v": "<0.8.45" }, { "advisory": "DataHub's AuthServiceClient, specifically versions prior to 0.8.45, creates JSON strings using format strings containing user-controlled data. This method enables potential attackers to manipulate these JSON strings and forward them to the backend, leading to potential misuse and authentication bypasses. Such misuse could result in the generation of system accounts, potentially leading to full system compromise. This vulnerability was identified and reported by the GitHub Security lab and is being tracked under GHSL-2022-080.\r\nhttps://github.com/datahub-project/datahub/security/advisories/GHSA-6rpf-5cfg-h8f3", "cve": "CVE-2023-25560", "id": "pyup.io-63340", "more_info_path": "/vulnerabilities/CVE-2023-25560/63340", "specs": [ "<0.8.45" ], "v": "<0.8.45" }, { "advisory": "In DataHub versions prior to 0.8.45, session cookies are only cleared upon new sign-ins, not during logouts. This allows potential attackers to bypass authentication checks using the AuthUtils.hasValidSessionCookie() method by using a cookie from a logged-out session. Consequently, any logged-out session cookie might be considered valid, leading to an authentication bypass. Users are advised to upgrade to version 0.8.45 to rectify this vulnerability. Currently, there are no known workarounds. This vulnerability was identified and reported by the GitHub Security lab and is being tracked under GHSL-2022-083.\r\nhttps://github.com/datahub-project/datahub/security/advisories/GHSA-3974-hxjh-m3jj\r\nhttps://github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d3/datahub-frontend/app/auth/AuthUtils.java#L78", "cve": "CVE-2023-25562", "id": "pyup.io-63338", "more_info_path": "/vulnerabilities/CVE-2023-25562/63338", "specs": [ "<0.8.45" ], "v": "<0.8.45" }, { "advisory": "DataHub under 0.8.45 frontend, acting as a proxy, is found to have a vulnerability where it doesn't properly construct URLs when forwarding data to the DataHub Metadata Store (GMS), potentially allowing external users to reroute requests from the DataHub Frontend to any host. This could enable attackers to reroute a request from the frontend proxy to any other server and return the result. The vulnerability was discovered and reported by the GitHub Security lab and is tracked as GHSL-2022-076.\r\nhttps://github.com/datahub-project/datahub/security/advisories/GHSA-5w2h-q83m-65xg", "cve": "CVE-2023-25557", "id": "pyup.io-63341", "more_info_path": "/vulnerabilities/CVE-2023-25557/63341", "specs": [ "<0.8.45" ], "v": "<0.8.45" }, { "advisory": "DataHub under 0.9.5 uses the X-DataHub-Actor HTTP header to infer the user sending requests on behalf of the frontend. However, due to case-insensitivity, an attacker could potentially exploit this by sending a header with different casing (e.g., X-DATAHUB-ACTOR), leading to potential authorization bypass. This allows any user to impersonate the system user account and perform actions on its behalf. This vulnerability, tracked as GHSL-2022-079, was discovered and reported by the GitHub Security lab.\r\nhttps://github.com/datahub-project/datahub/security/advisories/GHSA-hrwp-2q5c-86wv\r\nhttps://github.com/datahub-project/datahub/commit/2a182f484677d056730d6b4e9f0143e67368359f", "cve": "CVE-2023-25558", "id": "pyup.io-63342", "more_info_path": "/vulnerabilities/CVE-2023-25558/63342", "specs": [ "<0.9.5" ], "v": "<0.9.5" }, { "advisory": "# Missing JWT signature check (`GHSL-2022-078`)\n\nThe [`StatelessTokenService`](https://github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d3/metadata-service/auth-impl/src/main/java/com/datahub/authentication/token/StatelessTokenService.java#L30) of the DataHub metadata service (GMS) does not verify the signature of JWT tokens. This allows an attacker to connect to DataHub instances as any user if Metadata Service authentication is enabled. This vulnerability occurs because the `StatelessTokenService` of the Metadata service uses the [`parse`](https://github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d3/metadata-service/auth-impl/src/main/java/com/datahub/authentication/token/StatelessTokenService.java#L134) method of `io.jsonwebtoken.JwtParser`, which does not perform a verification of the cryptographic token signature. This means that JWTs are accepted regardless of the used algorithm.\n\n#### Impact\n\nThis issue may lead to an authentication bypass.\n\n#### Resources\n\n* [CodeQL: Missing JWT signature check](https://codeql.github.com/codeql-query-help/java/java-missing-jwt-signature-check/)", "cve": "CVE-2022-39366", "id": "pyup.io-54556", "more_info_path": "/vulnerabilities/CVE-2022-39366/54556", "specs": [ ">=0,<0.8.45" ], "v": ">=0,<0.8.45" } ], "actingweb": [ { "advisory": "Affected versions of this package are vulnerable to cross-actor authorization attacks due to improper validation of actor ownership in OAuth2 callback flows. The vulnerability exists because the OAuth2 callback did not correctly validate that the actor initiating the authorization was the same as the one completing it, allowing unauthorized access. An attacker could exploit this vulnerability to authorize access to another user's actor, potentially leading to unauthorized data access or actions on behalf of the victim.", "cve": "PVE-2025-82098", "id": "pyup.io-82098", "more_info_path": "/vulnerabilities/PVE-2025-82098/82098", "specs": [ "<3.4" ], "v": "<3.4" }, { "advisory": "Affected versions of this package are vulnerable to account hijacking due to reliance on unverified email addresses from OAuth2 providers. The vulnerability arises when OAuth2 providers return email addresses that are not verified, which could be exploited by attackers to hijack accounts by associating them with their own email addresses. An attacker could exploit this by registering an email address with the OAuth2 provider that matches a victim's email, thereby gaining unauthorized access to the victim's account.", "cve": "PVE-2025-82104", "id": "pyup.io-82104", "more_info_path": "/vulnerabilities/PVE-2025-82104/82104", "specs": [ "<3.4" ], "v": "<3.4" }, { "advisory": "Affected versions of this package are vulnerable to session fixation attacks due to improper handling of session identifiers during OAuth2 login flows. The vulnerability is present because attackers could manipulate session identifiers to trick users into logging into the attacker's session, rather than their own. An attacker could exploit this by setting a session identifier in a victim's browser, causing the victim to authenticate into the attacker's session, potentially leading to unauthorized access to sensitive information.", "cve": "PVE-2025-82105", "id": "pyup.io-82105", "more_info_path": "/vulnerabilities/PVE-2025-82105/82105", "specs": [ "<3.4" ], "v": "<3.4" }, { "advisory": "Affected versions of Actingweb are potentially vulnerable to authorization bypass due to incorrect permission-evaluator behavior that fell back to legacy ACL handling.", "cve": "PVE-2025-82910", "id": "pyup.io-82910", "more_info_path": "/vulnerabilities/PVE-2025-82910/82910", "specs": [ "<3.7.0" ], "v": "<3.7.0" }, { "advisory": "Affected versions of Actingweb are vulnerable to information disclosure due to missing permission filtering in the Properties listall endpoint.", "cve": "PVE-2025-82974", "id": "pyup.io-82974", "more_info_path": "/vulnerabilities/PVE-2025-82974/82974", "specs": [ "<3.7.0" ], "v": "<3.7.0" }, { "advisory": "Affected versions of actingweb are vulnerable to authorization bypass due to unsafe permission-override merge semantics that allowed security exclusions to be cleared.", "cve": "PVE-2025-82909", "id": "pyup.io-82909", "more_info_path": "/vulnerabilities/PVE-2025-82909/82909", "specs": [ "<3.7.1" ], "v": "<3.7.1" } ], "actinia-core": [ { "advisory": "Actinia-core 2.0.0 fixes an unsafe temporary files creation vulnerability.\r\nhttps://github.com/mundialis/actinia_core/pull/262\r\nhttps://github.com/mundialis/actinia_core/pull/256", "cve": "PVE-2022-50460", "id": "pyup.io-50460", "more_info_path": "/vulnerabilities/PVE-2022-50460/50460", "specs": [ "<2.0.0" ], "v": "<2.0.0" }, { "advisory": "Actinia-core version 4.14.0 updates its dependency from version 2.3.6 to 3.0.1 to address the security vulnerability identified as CVE-2023-46136.", "cve": "CVE-2023-46136", "id": "pyup.io-71172", "more_info_path": "/vulnerabilities/CVE-2023-46136/71172", "specs": [ "<4.14.0" ], "v": "<4.14.0" }, { "advisory": "Actinia-core version 4.14.0 updates its Flask dependency from \"Flask>=1.1.4\" to \"Flask>=3.0.0\" to address the security vulnerability identified as CVE-2023-30861.", "cve": "CVE-2023-30861", "id": "pyup.io-71176", "more_info_path": "/vulnerabilities/CVE-2023-30861/71176", "specs": [ "<4.14.0" ], "v": "<4.14.0" }, { "advisory": "Actinia-core 4.5.0 includes a fix for a path traversal vulnerability.\r\nhttps://github.com/actinia-org/actinia-core/commit/be5299efb6490c9a8b0804f185421c0828c6d126", "cve": "PVE-2023-58948", "id": "pyup.io-58948", "more_info_path": "/vulnerabilities/PVE-2023-58948/58948", "specs": [ "<4.5.0" ], "v": "<4.5.0" } ], "actinis-django-storages": [ { "advisory": "Actinis-django-storages 1.7 fixes an insecure default ACL of 'public-read' in the 'S3BotoStorage' and 'S3Boto3Storage' backends.", "cve": "PVE-2022-48499", "id": "pyup.io-48499", "more_info_path": "/vulnerabilities/PVE-2022-48499/48499", "specs": [ "<1.7" ], "v": "<1.7" } ], "actipy": [ { "advisory": "Actipy 1.1.0 updates its dependency 'numpy' requirement to '>=1.22' to include security fixes.", "cve": "CVE-2021-41496", "id": "pyup.io-51303", "more_info_path": "/vulnerabilities/CVE-2021-41496/51303", "specs": [ "<1.1.0" ], "v": "<1.1.0" }, { "advisory": "Actipy 1.1.0 updates its dependency 'numpy' requirement to '>=1.22' to include security fixes.", "cve": "CVE-2021-34141", "id": "pyup.io-51296", "more_info_path": "/vulnerabilities/CVE-2021-34141/51296", "specs": [ "<1.1.0" ], "v": "<1.1.0" } ], "adios2": [ { "advisory": "Adios2 2.9.0 fixes a race condition in OnDemand timestep and in OnDemand delivery.\r\nhttps://github.com/ornladios/ADIOS2/pull/3355/commits/9d55dad75ac09b1a6bfb3a94a054b023ced43fb9\r\nhttps://github.com/ornladios/ADIOS2/pull/3369/commits/fd8b02a72d91ac31d9beb4e68fa77a353b657bb5", "cve": "PVE-2023-62779", "id": "pyup.io-62779", "more_info_path": "/vulnerabilities/PVE-2023-62779/62779", "specs": [ "<2.9.0" ], "v": "<2.9.0" } ], "adversarial-robustness-toolbox": [ { "advisory": "Adversarial-robustness-toolbox version 1.6.1 updates its dependency \"Pillow\" to a secure version. See CVE-2021-28678.", "cve": "CVE-2021-28678", "id": "pyup.io-41782", "more_info_path": "/vulnerabilities/CVE-2021-28678/41782", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Adversarial-robustness-toolbox version 1.6.1 updates its dependency \"Pillow\" to a secure version. See CVE-2021-28675.", "cve": "CVE-2021-28675", "id": "pyup.io-41781", "more_info_path": "/vulnerabilities/CVE-2021-28675/41781", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Adversarial-robustness-toolbox version 1.7.1 updates its dependency \"Pillow\" to a secure version. See CVE-2021-34552.", "cve": "CVE-2021-34552", "id": "pyup.io-41783", "more_info_path": "/vulnerabilities/CVE-2021-34552/41783", "specs": [ "<1.7.1" ], "v": "<1.7.1" }, { "advisory": "Adversarial-robustness-toolbox version 1.8.0 updates its dependency \"Pillow\" to a secure version.", "cve": "CVE-2021-23437", "id": "pyup.io-41784", "more_info_path": "/vulnerabilities/CVE-2021-23437/41784", "specs": [ "<1.8.0" ], "v": "<1.8.0" } ], "adyen": [ { "advisory": "Adyen version 7.1.0 addresses a security vulnerability related to a timing attack in HMAC comparisons.", "cve": "PVE-2024-66853", "id": "pyup.io-66853", "more_info_path": "/vulnerabilities/PVE-2024-66853/66853", "specs": [ "<7.1.0" ], "v": "<7.1.0" } ], "aegea": [ { "advisory": "Aegea 2.2.7 updates the minimum requirement for its dependency 'paramiko' to v2.4.2 to include a security fix.", "cve": "CVE-2018-1000805", "id": "pyup.io-37611", "more_info_path": "/vulnerabilities/CVE-2018-1000805/37611", "specs": [ "<2.2.7" ], "v": "<2.2.7" } ], "aethos": [ { "advisory": "Aethos 0.3.0.1 hotfixed NLTK package in setup.py.", "cve": "PVE-2021-37721", "id": "pyup.io-37721", "more_info_path": "/vulnerabilities/PVE-2021-37721/37721", "specs": [ "<0.3.0.1" ], "v": "<0.3.0.1" } ], "afdko": [ { "advisory": "Afdko 3.0.0 includes a fix for a code execution vulnerability.\r\nhttps://github.com/adobe-type-tools/afdko/issues/780", "cve": "PVE-2023-54923", "id": "pyup.io-54923", "more_info_path": "/vulnerabilities/PVE-2023-54923/54923", "specs": [ "<3.0.0" ], "v": "<3.0.0" } ], "affinequant": [ { "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'affinequant' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.", "cve": "PVE-2024-74233", "id": "pyup.io-74233", "more_info_path": "/vulnerabilities/PVE-2024-74233/74233", "specs": [ ">=0", "<=0" ], "v": ">=0,<=0" } ], "agent-mcp-gateway": [ { "advisory": "Affected versions of agent-mcp-gateway are vulnerable to Authorization Bypass. The policy evaluation engine fails to prioritize deny rules over allow rules, leading to explicit allow permissions overriding wildcard deny policies and granting unauthorized access to restricted resources.", "cve": "PVE-2025-81356", "id": "pyup.io-81356", "more_info_path": "/vulnerabilities/PVE-2025-81356/81356", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "agenta": [ { "advisory": "Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF). The webhook and testset import endpoints fail to validate and sanitize URLs before making HTTP requests, leading to attackers being able to access internal network resources including localhost services, cloud metadata endpoints (169.254.169.254), private network ranges, and internal APIs by providing malicious URLs in webhook configurations or testset import endpoints.", "cve": "PVE-2026-84311", "id": "pyup.io-84311", "more_info_path": "/vulnerabilities/PVE-2026-84311/84311", "specs": [ "<0.77.1" ], "v": "<0.77.1" }, { "advisory": "Affected versions of this package are vulnerable to Incorrect Authorization. The testset API endpoints incorrectly check for `Permission.EDIT_EVALUATORS` instead of the appropriate testset-specific permissions (`Permission.EDIT_TESTSETS`, `Permission.VIEW_TESTSETS`), leading to unauthorized users with evaluator permissions being able to create, modify, view, and delete testsets without proper testset access rights.", "cve": "PVE-2026-84309", "id": "pyup.io-84309", "more_info_path": "/vulnerabilities/PVE-2026-84309/84309", "specs": [ "<0.77.1" ], "v": "<0.77.1" } ], "agentc": [ { "advisory": "Affected versions of this package are vulnerable to Command Injection due to unsafe rendering of Jinja templates without automatic escaping. The Jinja environment does not enable `autoescape=True`, allowing user-controlled template data to be interpreted as executable code within the shell context. This permits attackers to inject and execute arbitrary system commands through crafted template content, leading to full command execution under the application's privileges.", "cve": "PVE-2025-81931", "id": "pyup.io-81931", "more_info_path": "/vulnerabilities/PVE-2025-81931/81931", "specs": [ "<0.2.5a3" ], "v": "<0.2.5a3" }, { "advisory": "Affected versions of this package are vulnerable to Command Injection due to unsafe use of subprocess.run to invoke the default system editor during the agentc add operation. The application directly executes a user-defined or environment-influenced editor path as a shell command without validation or sanitization. This allows attackers to supply a malicious executable or alter the environment to hijack the editor invocation, resulting in arbitrary code execution.", "cve": "PVE-2025-81933", "id": "pyup.io-81933", "more_info_path": "/vulnerabilities/PVE-2025-81933/81933", "specs": [ "<0.2.5a3" ], "v": "<0.2.5a3" } ], "agentos-taskweaver": [ { "advisory": "Affected versions of the agentos-taskweaver package are vulnerable to Server-Side Request Forgery (SSRF) due to insecure container network isolation on macOS and Windows hosts when running with Docker Desktop, Containerd on Lima VM, or Podman. The TaskWeaver code interpreter starts Docker containers via a Docker client configuration that allows special \u201cmagic\u201d hostnames such as host.docker.internal, host.containers.internal, or host.lima.internal to resolve to the host\u2019s localhost, enabling user-influenced code executed by TaskWeaver to issue network requests to host-only services bound to 127.0.0.1.", "cve": "PVE-2026-85247", "id": "pyup.io-85247", "more_info_path": "/vulnerabilities/PVE-2026-85247/85247", "specs": [ "<=0.1.0" ], "v": "<=0.1.0" } ], "agentscope": [ { "advisory": "Affected versions of the agentscope package are vulnerable to Path Traversal due to insufficient sanitization of the path parameter. The `/api/file` API endpoint fails to validate or sanitize user-supplied path values, allowing directory traversal sequences to escape the intended file directory.", "cve": "CVE-2024-8438", "id": "pyup.io-76211", "more_info_path": "/vulnerabilities/CVE-2024-8438/76211", "specs": [ "<0.0.4" ], "v": "<0.0.4" }, { "advisory": "A directory traversal vulnerability exists in modelscope/agentscope. An attacker can exploit this vulnerability to read any local JSON file by sending a crafted POST request to the /read-examples endpoint.", "cve": "CVE-2024-8524", "id": "pyup.io-76208", "more_info_path": "/vulnerabilities/CVE-2024-8524/76208", "specs": [ "<0.0.4" ], "v": "<0.0.4" }, { "advisory": "A vulnerability in the RpcAgentServerLauncher class of modelscope/agentscope v0.0.6a3 allows for remote code execution (RCE) via deserialization of untrusted data using the dill library. The issue occurs in the AgentServerServicer.create_agent method, where serialized input is deserialized using dill.loads, enabling an attacker to execute arbitrary commands on the server.", "cve": "CVE-2024-8502", "id": "pyup.io-76209", "more_info_path": "/vulnerabilities/CVE-2024-8502/76209", "specs": [ "<0.0.6a3" ], "v": "<0.0.6a3" }, { "advisory": "Affected versions of Agentscope are vulnerable to Code Injection. Agentscope does not implement security measures to isolate the execution of user-provided code, which could lead to the takeover of the server running the code.", "cve": "PVE-2024-73116", "id": "pyup.io-73116", "more_info_path": "/vulnerabilities/PVE-2024-73116/73116", "specs": [ "<0.1.0" ], "v": "<0.1.0" }, { "advisory": "Affected versions of the agentscope package are vulnerable to Path Traversal due to insufficient validation of file paths in workflow operations. The save-workflow and load-workflow functionality fails to properly sanitize user-supplied file paths, allowing directory traversal sequences to access files outside the intended directory.", "cve": "CVE-2024-8551", "id": "pyup.io-76213", "more_info_path": "/vulnerabilities/CVE-2024-8551/76213", "specs": [ "<0.1.1" ], "v": "<0.1.1" }, { "advisory": "Affected versions of the agentscope package are vulnerable to Path Traversal due to improper input validation in the workflow deletion functionality. The `/delete-workflow` endpoint fails to properly validate and sanitize file path inputs, allowing directory traversal sequences to access files outside the intended workflow directory.", "cve": "CVE-2024-8537", "id": "pyup.io-76210", "more_info_path": "/vulnerabilities/CVE-2024-8537/76210", "specs": [ "<0.1.1" ], "v": "<0.1.1" }, { "advisory": "A stored cross-site scripting (XSS) vulnerability exists in modelscope/agentscope, as of the latest commit 21161fe on the main branch. The vulnerability occurs in the view for inspecting detailed run information, where a user-controllable string (run ID) is appended and rendered as HTML. This allows an attacker to execute arbitrary JavaScript code in the context of the user's browser.", "cve": "CVE-2024-8556", "id": "pyup.io-76207", "more_info_path": "/vulnerabilities/CVE-2024-8556/76207", "specs": [ "<0.1.1" ], "v": "<0.1.1" }, { "advisory": "Affected versions of the AgentScope package are vulnerable to Path Traversal due to insufficient input validation in the file download functionality. The download_file method in the rpc_agent_client component fails to properly sanitize user-supplied file paths, allowing directory traversal sequences to access files outside the intended directory. An attacker can exploit this vulnerability by sending crafted file path requests containing traversal sequences to download arbitrary files from the rpc_agent's host system, potentially exposing sensitive configuration files, credentials, or system files that could enable further attacks.", "cve": "CVE-2024-8501", "id": "pyup.io-78832", "more_info_path": "/vulnerabilities/CVE-2024-8501/78832", "specs": [ "<=0.0.4" ], "v": "<=0.0.4" }, { "advisory": "Affected versions of the AgentScope package are vulnerable to Cross-Origin Resource Sharing (CORS) misconfiguration due to insufficient origin validation. The agentscope server fails to restrict API access to trusted origins, instead accepting requests from any external domain without proper CORS header validation. An attacker can exploit this vulnerability by hosting a malicious website that makes cross-origin requests to the AgentScope API, potentially accessing sensitive data, obtaining unauthorized information, or performing actions on behalf of authenticated users without their consent.", "cve": "CVE-2024-8487", "id": "pyup.io-78830", "more_info_path": "/vulnerabilities/CVE-2024-8487/78830", "specs": [ "<=0.0.4" ], "v": "<=0.0.4" }, { "advisory": "Affected versions of the agentscope package are vulnerable to Remote Code Execution due to unsafe use of Python's eval() function. The `is_callable_expression` function in `agentscope\\web\\workstation\\workflow_utils.py` directly executes user-provided input through the line `result = eval(s)` without any sanitization or validation. An unauthenticated remote attacker can exploit this vulnerability by sending malicious Python code as input to the vulnerable function, allowing arbitrary command execution with the privileges of the application process and potentially leading to complete system compromise.", "cve": "CVE-2024-48050", "id": "pyup.io-78812", "more_info_path": "/vulnerabilities/CVE-2024-48050/78812", "specs": [ "<=0.1.0" ], "v": "<=0.1.0" }, { "advisory": "Affected versions of Agentscope are vulnerable to Code Injection. The fix for PVE-2024-73116 was incomplete. The applied black-list to filter out dangerous commands can be simply bypassed. For example, the attackers can run rm --rf (note that there are more than one space character in between the rm and -rf) to bypass the check as the blocked item only has one space in between. Moreover, the current black-list also overlooked many other dangerous commands such as netcat, the hackers can simply create a backdoor by the command nc -lvvp 6666 -e /bin/sh to enable a remote shell and then log into the victim system to run arbitrary commands as follows.", "cve": "PVE-2024-73124", "id": "pyup.io-73124", "more_info_path": "/vulnerabilities/PVE-2024-73124/73124", "specs": [ ">=0" ], "v": ">=0" } ], "agentuniverse": [ { "advisory": "Agentuniverse version 0.0.8 updates its flask dependency from ^2.2 to ^2.3.2 to address the security vulnerability identified as CVE-2023-30861.", "cve": "CVE-2023-30861", "id": "pyup.io-71400", "more_info_path": "/vulnerabilities/CVE-2023-30861/71400", "specs": [ "<0.0.8" ], "v": "<0.0.8" }, { "advisory": "Agentuniverse version 0.0.8 updates its Jinja2 dependency to version ^3.1.4, addressing the security vulnerability identified as CVE-2024-22195.", "cve": "CVE-2024-22195", "id": "pyup.io-71401", "more_info_path": "/vulnerabilities/CVE-2024-22195/71401", "specs": [ "<0.0.8" ], "v": "<0.0.8" }, { "advisory": "Agentuniverse version 0.0.8 updates its requests dependency from version ^2.31.0 to ^2.32.0 to address the security vulnerability identified as CVE-2024-35195.", "cve": "CVE-2024-35195", "id": "pyup.io-71387", "more_info_path": "/vulnerabilities/CVE-2024-35195/71387", "specs": [ "<0.0.8" ], "v": "<0.0.8" }, { "advisory": "Agentuniverse version 0.0.8 updates its langchain dependency from version 0.0.352 to 0.1.20 to address the security vulnerability identified as CVE-2024-21503.", "cve": "CVE-2024-21503", "id": "pyup.io-71402", "more_info_path": "/vulnerabilities/CVE-2024-21503/71402", "specs": [ "<0.0.8" ], "v": "<0.0.8" }, { "advisory": "Agentuniverse version 0.0.8 updates its gunicorn dependency from 21.2.0 to ^22.0.0 to address the security vulnerability identified as CVE-2024-1135.", "cve": "CVE-2024-1135", "id": "pyup.io-71403", "more_info_path": "/vulnerabilities/CVE-2024-1135/71403", "specs": [ "<0.0.8" ], "v": "<0.0.8" } ], "agixt": [ { "advisory": "Agixt 1.2.4 includes a fix for a path traversal vulnerability. \r\nhttps://github.com/Josh-XT/AGiXT/pull/673", "cve": "PVE-2023-58993", "id": "pyup.io-58993", "more_info_path": "/vulnerabilities/PVE-2023-58993/58993", "specs": [ "<1.2.4" ], "v": "<1.2.4" }, { "advisory": "Agixt version 1.5.17 fixes an issue with context injection strings, enhancing the handling of feedback and web search data. This update prevents potential vulnerabilities where maliciously crafted inputs could inject unintended commands or data into the application's context, thereby improving the security and reliability of the application's response generation.", "cve": "PVE-2024-71135", "id": "pyup.io-71135", "more_info_path": "/vulnerabilities/PVE-2024-71135/71135", "specs": [ "<1.5.17" ], "v": "<1.5.17" } ], "agno": [ { "advisory": "Affected versions of the agno package are vulnerable to Command Injection due to unsanitized interpolation of the pull request title into an inline shell script in a GitHub Actions workflow. In .github/workflows/pr-lint.yml, the run step expands the github.event.pull_request.title expression inside the script, which is evaluated before shell execution and therefore allows shell metacharacters and command substitutions to be interpreted, creating script-injection risk.", "cve": "PVE-2025-79215", "id": "pyup.io-79215", "more_info_path": "/vulnerabilities/PVE-2025-79215/79215", "specs": [ "<1.7.7" ], "v": "<1.7.7" }, { "advisory": "Affected versions of the agno package are vulnerable to Information Disclosure due to a race condition in session_state handling under high concurrency. The run and arun methods on Agent and Team accept a session_state parameter that can be written without proper synchronization, allowing the value to be assigned and persisted to the wrong session.", "cve": "CVE-2025-64168", "id": "pyup.io-81040", "more_info_path": "/vulnerabilities/CVE-2025-64168/81040", "specs": [ ">=2.0.0a1,<2.2.2" ], "v": ">=2.0.0a1,<2.2.2" } ], "agntcy-dir": [ { "advisory": "Affected versions of this package are vulnerable to Denial of Service (DoS) via Resource Exhaustion. Multiple components fail to properly manage and close resources including gRPC connections, SPIFFE sources, and streaming goroutines, leading to file descriptor exhaustion, goroutine leaks, and memory exhaustion that can crash long-running applications.", "cve": "PVE-2025-81926", "id": "pyup.io-81926", "more_info_path": "/vulnerabilities/PVE-2025-81926/81926", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Affected versions of this package are vulnerable due to Incorrect Permission Assignment for Critical Resource. The SPIRE Workload API socket mount fails to enforce read-only permissions due to missing `readOnly: true` in the volume definition, leading to unauthorized write access to the identity socket by containers. This permits potential tampering with workload attestation or unauthorized access to SPIFFE-issued credentials, compromising workload isolation and identity guarantees.", "cve": "PVE-2025-81923", "id": "pyup.io-81923", "more_info_path": "/vulnerabilities/PVE-2025-81923/81923", "specs": [ "<0.5.3" ], "v": "<0.5.3" } ], "agpt": [ { "advisory": "Affected versions of the agpt package are vulnerable to Remote Code Execution due to the missing enforcement of the block disabled flag during block execution. The /blocks/{block_id}/execute route (execute_graph_block) and the external API POST /external-api/v1/blocks/{id}/execute fetch a block by UUID and call obj.execute(...) without checking obj.disabled, allowing execution of the disabled BlockInstallationBlock which writes attacker-supplied Python to disk and runs it via __import__() (and low-privilege users can mint API keys with EXECUTE_BLOCK via POST /api-keys).", "cve": "CVE-2026-24780", "id": "pyup.io-85308", "more_info_path": "/vulnerabilities/CVE-2026-24780/85308", "specs": [ "<=0.2.2" ], "v": "<=0.2.2" }, { "advisory": "A critical vulnerability in the ShellCommandExecutor component of the Forge library and significant-gravitas/autogpt affected versions allows attackers to execute arbitrary commands on the host system. The component lacks proper security measures, enabling command injection attacks. Additionally, attackers can bypass shell command denylists by using modified paths (e.g., /bin/./whoami). This vulnerability can lead to unauthorized access, data breaches, or system compromise. Users should avoid the ShellCommandExecutor in production, implement robust sandboxing, update autogpt to the latest version, and review command execution security measures to mitigate these risks.", "cve": "CVE-2024-6091", "id": "pyup.io-73328", "more_info_path": "/vulnerabilities/CVE-2024-6091/73328", "specs": [ "<=0.5.1" ], "v": "<=0.5.1" } ], "agraph-python": [ { "advisory": "Agraph-python 101.0.1 updates urllib3 from 1.22 to 1.23 for security reasons.", "cve": "CVE-2018-20060", "id": "pyup.io-38506", "more_info_path": "/vulnerabilities/CVE-2018-20060/38506", "specs": [ "<101.0.1" ], "v": "<101.0.1" }, { "advisory": "Agraph-python 101.0.1 updates requests from 2.18.4 to 2.20.0 for security reasons.", "cve": "CVE-2018-18074", "id": "pyup.io-42708", "more_info_path": "/vulnerabilities/CVE-2018-18074/42708", "specs": [ "<101.0.1" ], "v": "<101.0.1" }, { "advisory": "Agraph-python 101.0.3 updates urllib3 to 1.24.2 for security reasons.", "cve": "CVE-2019-11324", "id": "pyup.io-37085", "more_info_path": "/vulnerabilities/CVE-2019-11324/37085", "specs": [ "<101.0.3" ], "v": "<101.0.3" } ], "ahc-tools": [ { "advisory": "Directory traversal vulnerability in eNovance eDeploy allows remote attackers to create arbitrary directories and files and consequently cause a denial of service (resource consumption) via a (dot dot) the session parameter.", "cve": "CVE-2014-3702", "id": "pyup.io-70427", "more_info_path": "/vulnerabilities/CVE-2014-3702/70427", "specs": [ "<1.6.0" ], "v": "<1.6.0" } ], "ahjo": [ { "advisory": "Ahjo 3.1.1 updates its dependency 'setuptools' to v65.5.1 to include a security fix.", "cve": "CVE-2022-40897", "id": "pyup.io-52764", "more_info_path": "/vulnerabilities/CVE-2022-40897/52764", "specs": [ "<3.1.1" ], "v": "<3.1.1" }, { "advisory": "Ahjo 3.1.5 updates its dependency 'pyodbc' to v4.0.39 to include a security fix.", "cve": "PVE-2023-54980", "id": "pyup.io-55055", "more_info_path": "/vulnerabilities/PVE-2023-54980/55055", "specs": [ "<3.1.5" ], "v": "<3.1.5" } ], "ai-data-science-team": [ { "advisory": "Affected versions of the ai-data-science-team package are vulnerable to insecure deserialization due to unsafe loading of pickle files via pandas. The ai_data_science_team.tools.data_loader.load_pickle() function calls pandas.read_pickle() on potentially user-controlled paths, which performs unrestricted pickle deserialization.", "cve": "PVE-2025-83053", "id": "pyup.io-83053", "more_info_path": "/vulnerabilities/PVE-2025-83053/83053", "specs": [ "<0.0.0.9017" ], "v": "<0.0.0.9017" } ], "ai-flow": [ { "advisory": "A vulnerability was found in flink-extended ai-flow 0.3.1. It has been declared as critical. Affected by this vulnerability is the function cloudpickle.loads of the file \\ai_flow\\cli\\commands\\workflow_command.py. The manipulation leads to deserialization. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier VDB-252205 was assigned to this vulnerability.", "cve": "CVE-2024-0960", "id": "pyup.io-66688", "more_info_path": "/vulnerabilities/CVE-2024-0960/66688", "specs": [ "<=0.3.1" ], "v": "<=0.3.1" } ], "ai-python": [ { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41220", "id": "pyup.io-43070", "more_info_path": "/vulnerabilities/CVE-2021-41220/43070", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41214", "id": "pyup.io-43055", "more_info_path": "/vulnerabilities/CVE-2021-41214/43055", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41222", "id": "pyup.io-43065", "more_info_path": "/vulnerabilities/CVE-2021-41222/43065", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41199", "id": "pyup.io-43002", "more_info_path": "/vulnerabilities/CVE-2021-41199/43002", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41207", "id": "pyup.io-43075", "more_info_path": "/vulnerabilities/CVE-2021-41207/43075", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41226", "id": "pyup.io-43057", "more_info_path": "/vulnerabilities/CVE-2021-41226/43057", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41212", "id": "pyup.io-43074", "more_info_path": "/vulnerabilities/CVE-2021-41212/43074", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41211", "id": "pyup.io-43053", "more_info_path": "/vulnerabilities/CVE-2021-41211/43053", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'pillow' to v8.3.2 to include security fixes.", "cve": "CVE-2021-34552", "id": "pyup.io-43082", "more_info_path": "/vulnerabilities/CVE-2021-34552/43082", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41198", "id": "pyup.io-43080", "more_info_path": "/vulnerabilities/CVE-2021-41198/43080", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41227", "id": "pyup.io-43058", "more_info_path": "/vulnerabilities/CVE-2021-41227/43058", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'pillow' to v8.3.2 to include security fixes.", "cve": "CVE-2021-23437", "id": "pyup.io-43083", "more_info_path": "/vulnerabilities/CVE-2021-23437/43083", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41204", "id": "pyup.io-43063", "more_info_path": "/vulnerabilities/CVE-2021-41204/43063", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41219", "id": "pyup.io-43056", "more_info_path": "/vulnerabilities/CVE-2021-41219/43056", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41200", "id": "pyup.io-43052", "more_info_path": "/vulnerabilities/CVE-2021-41200/43052", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41216", "id": "pyup.io-43068", "more_info_path": "/vulnerabilities/CVE-2021-41216/43068", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41209", "id": "pyup.io-43061", "more_info_path": "/vulnerabilities/CVE-2021-41209/43061", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41224", "id": "pyup.io-43066", "more_info_path": "/vulnerabilities/CVE-2021-41224/43066", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41203", "id": "pyup.io-43051", "more_info_path": "/vulnerabilities/CVE-2021-41203/43051", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41201", "id": "pyup.io-43077", "more_info_path": "/vulnerabilities/CVE-2021-41201/43077", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41197", "id": "pyup.io-43078", "more_info_path": "/vulnerabilities/CVE-2021-41197/43078", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41225", "id": "pyup.io-43059", "more_info_path": "/vulnerabilities/CVE-2021-41225/43059", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41221", "id": "pyup.io-43060", "more_info_path": "/vulnerabilities/CVE-2021-41221/43060", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41213", "id": "pyup.io-43062", "more_info_path": "/vulnerabilities/CVE-2021-41213/43062", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41218", "id": "pyup.io-43067", "more_info_path": "/vulnerabilities/CVE-2021-41218/43067", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41206", "id": "pyup.io-43072", "more_info_path": "/vulnerabilities/CVE-2021-41206/43072", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41196", "id": "pyup.io-43050", "more_info_path": "/vulnerabilities/CVE-2021-41196/43050", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41228", "id": "pyup.io-43064", "more_info_path": "/vulnerabilities/CVE-2021-41228/43064", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41208", "id": "pyup.io-43071", "more_info_path": "/vulnerabilities/CVE-2021-41208/43071", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41202", "id": "pyup.io-43076", "more_info_path": "/vulnerabilities/CVE-2021-41202/43076", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41217", "id": "pyup.io-43054", "more_info_path": "/vulnerabilities/CVE-2021-41217/43054", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41215", "id": "pyup.io-43069", "more_info_path": "/vulnerabilities/CVE-2021-41215/43069", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41210", "id": "pyup.io-43081", "more_info_path": "/vulnerabilities/CVE-2021-41210/43081", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41195", "id": "pyup.io-43079", "more_info_path": "/vulnerabilities/CVE-2021-41195/43079", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Ai-python 0.8.1 updates its dependency 'tensorflow' to v2.6.1 to include security fixes.", "cve": "CVE-2021-41205", "id": "pyup.io-43073", "more_info_path": "/vulnerabilities/CVE-2021-41205/43073", "specs": [ "<0.8.1" ], "v": "<0.8.1" } ], "aibrix": [ { "advisory": "Affected versions of the aibrix package are potentially vulnerable to a race condition vulnerability. This flaw may lead to a denial-of-service (DoS) impact by triggering a fatal error (\u201cconcurrent map iteration and map write\u201d) in the cache system, specifically within the debugInfo() function in pkg/cache/cache.go.", "cve": "PVE-2025-75783", "id": "pyup.io-75783", "more_info_path": "/vulnerabilities/PVE-2025-75783/75783", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "aiida": [ { "advisory": "Aiida 0.12.3 fixes a security vulnerability by upgrading `paramiko` to `2.4.2`.", "cve": "PVE-2021-37054", "id": "pyup.io-37054", "more_info_path": "/vulnerabilities/PVE-2021-37054/37054", "specs": [ "<0.12.3" ], "v": "<0.12.3" }, { "advisory": "Aiida 1.1.0 includes a fix for a code execution vulnerability in its dependency 'pyyaml'.\r\nhttps://github.com/aiidateam/aiida-core/pull/3675/commits/3a921192622c225516c8d9b0fa104cbd8201c177\r\nNOTE: \"This metapackage for AiiDA has been deprecated as of v1.0 and is no longer being maintained. If you want to install AiiDA, please install the aiida-core package instead.\"", "cve": "CVE-2017-18342", "id": "pyup.io-43428", "more_info_path": "/vulnerabilities/CVE-2017-18342/43428", "specs": [ "<1.1.0" ], "v": "<1.1.0" } ], "aiida-core": [ { "advisory": "aiida-core 0.12.3 fixes security vulnerability by upgrading `paramiko` to `2.4.2`", "cve": "PVE-2021-36956", "id": "pyup.io-36956", "more_info_path": "/vulnerabilities/PVE-2021-36956/36956", "specs": [ "<0.12.3" ], "v": "<0.12.3" }, { "advisory": "Aiida-core 1.1.0 updates its dependency 'pyyaml' to include a security fix.", "cve": "CVE-2017-18342", "id": "pyup.io-45582", "more_info_path": "/vulnerabilities/CVE-2017-18342/45582", "specs": [ "<1.1.0" ], "v": "<1.1.0" }, { "advisory": "Aiida-core before 1.6.0 adds security option to toggle POST methods on/off with the 'verdi restapi --posting/--no-posting' options (it is on by default).", "cve": "PVE-2021-40304", "id": "pyup.io-40304", "more_info_path": "/vulnerabilities/PVE-2021-40304/40304", "specs": [ "<1.6.0" ], "v": "<1.6.0" }, { "advisory": "Aiida-core 1.6.5 updates 'PyYAML' to v5.4 to fix critical security issues.", "cve": "CVE-2020-1747", "id": "pyup.io-43457", "more_info_path": "/vulnerabilities/CVE-2020-1747/43457", "specs": [ "<1.6.5" ], "v": "<1.6.5" }, { "advisory": "Aiida-core 1.6.5 updates its dependency 'pyyaml' to v5.4 to include security fixes.", "cve": "CVE-2019-20477", "id": "pyup.io-41169", "more_info_path": "/vulnerabilities/CVE-2019-20477/41169", "specs": [ "<1.6.5" ], "v": "<1.6.5" }, { "advisory": "Aiida-core 1.6.5 updates 'PyYAML' to v5.4 to fix critical security issues.", "cve": "CVE-2020-14343", "id": "pyup.io-43458", "more_info_path": "/vulnerabilities/CVE-2020-14343/43458", "specs": [ "<1.6.5" ], "v": "<1.6.5" } ], "aiidalab-widgets-base": [ { "advisory": "Affected versions of this package are vulnerable to Arbitrary File Upload. The application allows users to upload arbitrary files, such as private SSH keys, without proper restrictions, allowing attackers to upload malicious files leveraged to gain unauthorized remote access to systems or other users' accounts.", "cve": "PVE-2025-83013", "id": "pyup.io-83013", "more_info_path": "/vulnerabilities/PVE-2025-83013/83013", "specs": [ "<=2.5.0" ], "v": "<=2.5.0" } ], "ail": [ { "advisory": "Global.py in AIL framework 2.8 allows path traversal.", "cve": "CVE-2020-8545", "id": "pyup.io-70578", "more_info_path": "/vulnerabilities/CVE-2020-8545/70578", "specs": [ "<2.9" ], "v": "<2.9" } ], "aim": [ { "advisory": "Aim 1.2.13 updates its dependency 'pillow' to v6.2.2 to include security fixes.", "cve": "CVE-2020-5310", "id": "pyup.io-48607", "more_info_path": "/vulnerabilities/CVE-2020-5310/48607", "specs": [ "<1.2.13" ], "v": "<1.2.13" }, { "advisory": "Aim 1.2.13 updates its dependency 'pillow' to v6.2.2 to include security fixes.", "cve": "CVE-2020-5313", "id": "pyup.io-48615", "more_info_path": "/vulnerabilities/CVE-2020-5313/48615", "specs": [ "<1.2.13" ], "v": "<1.2.13" }, { "advisory": "Aim 1.2.13 updates its dependency 'pillow' to v6.2.2 to include security fixes.", "cve": "CVE-2020-5311", "id": "pyup.io-48613", "more_info_path": "/vulnerabilities/CVE-2020-5311/48613", "specs": [ "<1.2.13" ], "v": "<1.2.13" }, { "advisory": "Aim 1.2.13 updates its dependency 'pillow' to v6.2.2 to include security fixes.", "cve": "CVE-2020-5312", "id": "pyup.io-48614", "more_info_path": "/vulnerabilities/CVE-2020-5312/48614", "specs": [ "<1.2.13" ], "v": "<1.2.13" }, { "advisory": "A vulnerability in the runs/delete-batch endpoint of aimhubio/aim version 3.19.3 allows for arbitrary file or directory deletion through path traversal. The endpoint does not mitigate path traversal when handling user-specified run-names, which are used to specify log/metadata files for deletion. This can be exploited to delete arbitrary files or directories, potentially causing denial of service or data loss.", "cve": "CVE-2024-6483", "id": "pyup.io-76256", "more_info_path": "/vulnerabilities/CVE-2024-6483/76256", "specs": [ "<3.19.3" ], "v": "<3.19.3" }, { "advisory": "A vulnerability in aimhubio/aim version 3.19.3 allows an attacker to exploit the tarfile.extractall() function to extract the contents of a maliciously crafted tarfile to arbitrary locations on the host server. The attacker can control repo.path and run_hash to bypass directory existence checks and extract files to unintended locations, potentially overwriting critical files. This can lead to arbitrary data being written to arbitrary locations on the remote tracking server, which could be used for further attacks such as writing a new SSH key to the target server.", "cve": "CVE-2024-6829", "id": "pyup.io-76240", "more_info_path": "/vulnerabilities/CVE-2024-6829/76240", "specs": [ "<3.19.3" ], "v": "<3.19.3" }, { "advisory": "Aim before 3.2.0 runs its server only on unsafe HTTP protocol.\r\nhttps://github.com/aimhubio/aim/issues/1073", "cve": "PVE-2022-48606", "id": "pyup.io-48606", "more_info_path": "/vulnerabilities/PVE-2022-48606/48606", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "In version 3.22.0 of aimhubio/aim, the LocalFileManager._cleanup function in the aim tracking server accepts a user-specified glob-pattern for deleting files. The function does not verify that the matched files are within the directory managed by LocalFileManager, allowing a maliciously crafted glob-pattern to lead to arbitrary file deletion.", "cve": "CVE-2024-6851", "id": "pyup.io-76249", "more_info_path": "/vulnerabilities/CVE-2024-6851/76249", "specs": [ "<3.22.0" ], "v": "<3.22.0" }, { "advisory": "In version 3.23.0 of aimhubio/aim, certain methods that request data from external servers do not have set timeouts, causing the server to wait indefinitely for a response. This can lead to a denial of service, as the tracking server does not respond to other requests while waiting. The issue arises in the client used by the aim tracking server to communicate with external resources, specifically in the _run_read_instructions method and similar calls without timeouts.", "cve": "CVE-2024-8061", "id": "pyup.io-76217", "more_info_path": "/vulnerabilities/CVE-2024-8061/76217", "specs": [ "<3.23.0" ], "v": "<3.23.0" }, { "advisory": "A vulnerability in aimhubio/aim version 3.25.0 allows for a denial of service through the misuse of the sshfs-client. The tracking server, which is single-threaded, can be made unresponsive by requesting it to connect to an unresponsive socket via sshfs. The lack of an additional timeout setting in the sshfs-client causes the server to hang for a significant amount of time, preventing it from responding to other requests.", "cve": "CVE-2024-12777", "id": "pyup.io-76268", "more_info_path": "/vulnerabilities/CVE-2024-12777/76268", "specs": [ "<3.25.0" ], "v": "<3.25.0" }, { "advisory": "A vulnerability in aimhubio/aim version 3.25.0 allows for a denial of service (DoS) attack. The issue arises when a large number of tracked metrics are retrieved simultaneously from the Aim web API, causing the web server to become unresponsive. The root cause is the lack of a limit on the number of metrics that can be requested per call, combined with the server's single-threaded nature, leading to excessive resource consumption and blocking of the server.", "cve": "CVE-2024-12778", "id": "pyup.io-76253", "more_info_path": "/vulnerabilities/CVE-2024-12778/76253", "specs": [ "<3.25.0" ], "v": "<3.25.0" }, { "advisory": "Affected versions of the aim package are vulnerable to Cross-Site Request Forgery (CSRF) due to the absence of CSRF tokens and CORS protection in the dashboard. The aim dashboard fails to implement proper request validation mechanisms, allowing cross-origin requests to perform state-changing operations without verifying the request's authenticity.", "cve": "CVE-2024-2196", "id": "pyup.io-71905", "more_info_path": "/vulnerabilities/CVE-2024-2196/71905", "specs": [ "<=3.17.5" ], "v": "<=3.17.5" }, { "advisory": "Affected versions of the aimhubio/aim package are vulnerable to Cross-site Scripting (XSS) due to improper neutralization of input passed into React's dangerouslySetInnerHTML function. The logs tab in the web interface renders terminal output logs using dangerouslySetInnerHTML without sanitizing user-supplied content, enabling embedded scripts to persist in the application. An attacker can exploit this by injecting malicious script content into the logs\u2014for example, via a compromised run log\u2014which will execute in the context of any user viewing the logs tab, potentially leading to session hijacking, cookie theft, or further client-side compromise.", "cve": "CVE-2024-6578", "id": "pyup.io-78752", "more_info_path": "/vulnerabilities/CVE-2024-6578/78752", "specs": [ "<=3.19.3" ], "v": "<=3.19.3" }, { "advisory": "Affected versions of the Aim package are vulnerable to Cross-Site Request Forgery (CSRF) due to overly permissive CORS configuration. The tracking server allows cross-origin requests from all origins without proper validation, enabling unauthorized actions to be performed on behalf of authenticated users across all server endpoints. An attacker can exploit this vulnerability by hosting a malicious website that sends forged requests to the Aim tracking server, potentially chaining this with other vulnerabilities to achieve remote code execution, denial of service, or arbitrary file operations on the victim's behalf.", "cve": "CVE-2024-7760", "id": "pyup.io-78829", "more_info_path": "/vulnerabilities/CVE-2024-7760/78829", "specs": [ "<=3.22.0" ], "v": "<=3.22.0" }, { "advisory": "A critical security vulnerability affects the aimhubio aim library. The vulnerability exists in the dangerouslySetInnerHTML function of the file textbox.tsx within the Text Explorer component. Attackers can exploit this vulnerability by manipulating the query argument, leading to cross-site scripting (XSS). This allows remote execution of malicious scripts in the context of the victim's browser, potentially compromising user data or performing unauthorized actions. The vulnerability has been publicly disclosed, and exploits may exist in the wild.", "cve": "CVE-2024-8863", "id": "pyup.io-73307", "more_info_path": "/vulnerabilities/CVE-2024-8863/73307", "specs": [ "<=3.24.0" ], "v": "<=3.24.0" }, { "advisory": "In version 3.25.0 of aimhubio/aim, a denial of service vulnerability exists. By tracking a large number of Text objects and then querying them simultaneously through the web API, the Aim web server becomes unresponsive to other requests for an extended period while processing and returning these objects. This vulnerability can be exploited repeatedly, leading to a complete denial of service.", "cve": "CVE-2025-0190", "id": "pyup.io-76184", "more_info_path": "/vulnerabilities/CVE-2025-0190/76184", "specs": [ "<=3.25.0" ], "v": "<=3.25.0" }, { "advisory": "In version 3.25.0 of aimhubio/aim, the tracking server is vulnerable to a denial of service attack. The server overrides the maximum size for websocket messages, allowing very large images to be tracked. This causes the server to become unresponsive to other requests while processing the large image, leading to a denial of service condition.", "cve": "CVE-2025-0189", "id": "pyup.io-76186", "more_info_path": "/vulnerabilities/CVE-2025-0189/76186", "specs": [ "<=3.25.0" ], "v": "<=3.25.0" }, { "advisory": "A vulnerability classified as critical was found in aimhubio aim up to 3.29.1. This vulnerability affects the function RestrictedPythonQuery of the file /aim/storage/query.py of the component run_view Object Handler. The manipulation of the argument Abfrage leads to erweiterte Rechte. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.", "cve": "CVE-2025-5321", "id": "pyup.io-77694", "more_info_path": "/vulnerabilities/CVE-2025-5321/77694", "specs": [ "<=3.29.1" ], "v": "<=3.29.1" }, { "advisory": "Cross-site Scripting (XSS) in aimhubio Aim 3.28.0 allows remote attackers to execute arbitrary JavaScript in victims browsers via malicious Python code submitted to the /api/reports endpoint, which is interpreted and executed by Pyodide when the report is viewed. No sanitisation or sandbox restrictions prevent JavaScript execution via pyodide.code.run_js().", "cve": "CVE-2025-51464", "id": "pyup.io-78328", "more_info_path": "/vulnerabilities/CVE-2025-51464/78328", "specs": [ "<=3.30.0.dev20250611" ], "v": "<=3.30.0.dev20250611" }, { "advisory": "Aim is an open-source, self-hosted machine learning experiment tracking tool. Versions of Aim prior to 3.1.0 are vulnerable to a path traversal attack. By manipulating variables that reference files with \u00e2\u20ac\u0153dot-dot-slash (../)\u00e2\u20ac? sequences and its variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system including application source code or configuration and critical system files. The vulnerability issue is resolved in Aim v3.1.0.", "cve": "CVE-2021-43775", "id": "pyup.io-54444", "more_info_path": "/vulnerabilities/CVE-2021-43775/54444", "specs": [ ">=0,<3.1.0" ], "v": ">=0,<3.1.0" }, { "advisory": "Affected versions of the aim package are vulnerable to Remote Code Execution due to improper access restrictions in the run search functionality. The `/api/runs/search/run/` endpoint's run_search_api function in aim/web/api/runs/views.py fails to properly validate and restrict user access to the RunView object, allowing arbitrary code execution through the query parameter.", "cve": "CVE-2024-2195", "id": "pyup.io-71904", "more_info_path": "/vulnerabilities/CVE-2024-2195/71904", "specs": [ ">=3.0.0" ], "v": ">=3.0.0" }, { "advisory": "In version 3.22.0 of aimhubio/aim, the AimQL query language uses an outdated version of the safergetattr() function from RestrictedPython. This version does not protect against the str.formatmap() method, allowing an attacker to leak server-side secrets or potentially gain unrestricted code execution. The vulnerability arises because str.formatmap() can read arbitrary attributes of Python objects, enabling attackers to access sensitive variables such as os.environ. If an attacker can write files to a known location on the Aim server, they can use str.formatmap() to load a malicious .dll/.so file into the Python interpreter, leading to unrestricted code execution.", "cve": "CVE-2024-8238", "id": "pyup.io-76223", "more_info_path": "/vulnerabilities/CVE-2024-8238/76223", "specs": [ ">=3.0.0,<3.22.0" ], "v": ">=3.0.0,<3.22.0" }, { "advisory": "In version 3.23.0 of aimhubio/aim, the ScheduledStatusReporter object can be instantiated to run on the main thread of the tracking server, leading to the main thread being blocked indefinitely. This results in a denial of service as the tracking server becomes unable to respond to other requests.", "cve": "CVE-2024-10110", "id": "pyup.io-76298", "more_info_path": "/vulnerabilities/CVE-2024-10110/76298", "specs": [ ">=3.15.0,<3.23.0" ], "v": ">=3.15.0,<3.23.0" }, { "advisory": "A vulnerability in the LockManager.release_locks function in aimhubio/aim (commit bb76afe) allows for arbitrary file deletion through relative path traversal. The run_hash parameter, which is user-controllable, is concatenated without normalization as part of a path used to specify file deletion. This vulnerability is exposed through the Repo._close_run() method, which is accessible via the tracking server instruction API. As a result, an attacker can exploit this to delete any arbitrary file on the machine running the tracking server.", "cve": "CVE-2024-8769", "id": "pyup.io-76202", "more_info_path": "/vulnerabilities/CVE-2024-8769/76202", "specs": [ ">=3.15.0,<3.27.0" ], "v": ">=3.15.0,<3.27.0" } ], "aio-pika": [ { "advisory": "Aio-pika 9.1.5 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/mosquito/aio-pika/pull/566", "cve": "PVE-2023-59901", "id": "pyup.io-59901", "more_info_path": "/vulnerabilities/PVE-2023-59901/59901", "specs": [ "<9.1.5" ], "v": "<9.1.5" } ], "aioapns": [ { "advisory": "Certificate hostname validation in aioapns version 1.10 is enabled by default for security reasons. It can be turned off by using no_cert_validation option.", "cve": "PVE-2021-38620", "id": "pyup.io-38620", "more_info_path": "/vulnerabilities/PVE-2021-38620/38620", "specs": [ "<1.10" ], "v": "<1.10" } ], "aiobotocore": [ { "advisory": "Aiobotocore 2.9.1 fixes a race condition that was affecting the S3 Express identity cache. This race condition could occur when multiple threads attempted to read from or write to the cache simultaneously, leading to unpredictable behavior. The fix involves implementing synchronization mechanisms, specifically an asyncio lock, to ensure that only one thread can access the cache at a time.\r\nhttps://github.com/aio-libs/aiobotocore/pull/1073/commits/9097884cd8246460794157125ccd6378c3e901f8", "cve": "PVE-2024-64278", "id": "pyup.io-64278", "more_info_path": "/vulnerabilities/PVE-2024-64278/64278", "specs": [ "<2.9.1" ], "v": "<2.9.1" } ], "aiocoap": [ { "advisory": "The proxy in aiocoap 0.4a1 only creates log files when explicitly requested (18ddf8c). Also, support for secured protocols has been added.", "cve": "PVE-2021-37469", "id": "pyup.io-37469", "more_info_path": "/vulnerabilities/PVE-2021-37469/37469", "specs": [ "<0.4a1" ], "v": "<0.4a1" } ], "aiocouchdb": [ { "advisory": "aiocouchdb 0.6.0 now correctly set members for database security.", "cve": "PVE-2021-25612", "id": "pyup.io-25612", "more_info_path": "/vulnerabilities/PVE-2021-25612/25612", "specs": [ "<0.6.0" ], "v": "<0.6.0" } ], "aiocpa": [ { "advisory": "aiocpa is a Malicious Package, it is designed to steal cryptocurrency wallet data by exfiltrating sensitive information to a Telegram bot.", "cve": "PVE-2024-74373", "id": "pyup.io-74373", "more_info_path": "/vulnerabilities/PVE-2024-74373/74373", "specs": [ ">=0", "<=0" ], "v": ">=0,<=0" } ], "aiocurrencylayer": [ { "advisory": "Aiocurrencylayer version 1.0.4 updates its httpx dependency to version 0.23 or newer in response to CVE-2021-41945.\r\nhttps://github.com/home-assistant-ecosystem/aiocurrencylayer/commit/5768c17400f7d6222290f671ba3c8ba7b4c223ce", "cve": "CVE-2021-41945", "id": "pyup.io-66794", "more_info_path": "/vulnerabilities/CVE-2021-41945/66794", "specs": [ "<1.0.4" ], "v": "<1.0.4" } ], "aioftp": [ { "advisory": "The server of aioftp 0.15.0 uses explicit mapping of available commands for security reasons.", "cve": "PVE-2021-38045", "id": "pyup.io-38045", "more_info_path": "/vulnerabilities/PVE-2021-38045/38045", "specs": [ "<0.15.0" ], "v": "<0.15.0" }, { "advisory": "Affected versions of the aioftp package are vulnerable to Command Injection due to failure to reject carriage-return/line-feed (CR/LF) characters in command strings. The aioftp.Client.command method\u2014invoked by higher-level APIs such as Client.list\u2014accepted user-controlled arguments containing \u201c\\r\\n\u201d, allowing the constructed FTP line to be prematurely terminated and a second command appended.", "cve": "PVE-2025-79858", "id": "pyup.io-79858", "more_info_path": "/vulnerabilities/PVE-2025-79858/79858", "specs": [ "<0.26.3" ], "v": "<0.26.3" } ], "aiogram": [ { "advisory": "Affected versions of the aiogram package are potentially vulnerable to a timing side-channel attack due to non-constant-time HMAC signature comparison. In aiogram.utils.web_app.check_webapp_signature, the code compared calculated_hash to the supplied hash_ using == instead of hmac.compare_digest, which can leak timing information during signature verification (fixed in commit ddcedadfbde745965f7da03f5e7bcfbd31cc7614).", "cve": "PVE-2026-83706", "id": "pyup.io-83706", "more_info_path": "/vulnerabilities/PVE-2026-83706/83706", "specs": [ "<3.22.0" ], "v": "<3.22.0" } ], "aiohttp": [ { "advisory": "Aiohttp 0.16.3 fixes a directory traversal vulnerability by making changes in StaticRoute class of web_urldispatcher.py.\r\nhttps://github.com/aio-libs/aiohttp/pull/383", "cve": "PVE-2021-25613", "id": "pyup.io-25613", "more_info_path": "/vulnerabilities/PVE-2021-25613/25613", "specs": [ "<0.16.3" ], "v": "<0.16.3" }, { "advisory": "The Aiohttp 0.22.0 addresses a security concern where ClientSession was leaking cookies across different hostnames. This update introduces improved cookie management in line with RFC 6265, adding filters based on the \"Domain\" attribute of cookies. It ensures cookies without a specified \"Domain\" are shared across all requests for backward compatibility, while cookies with a specific domain are handled appropriately. The update also includes enhancements like rejecting cookies from IP addresses and handling cookies with attributes like \"Secure\", \"Path\", \"Expires\", and \"Max-Age\". \r\nhttps://github.com/aio-libs/aiohttp/commit/00169997ff69ae3d31a894bcb9ea0549713cafa6", "cve": "PVE-2024-64598", "id": "pyup.io-64598", "more_info_path": "/vulnerabilities/PVE-2024-64598/64598", "specs": [ "<0.22.0" ], "v": "<0.22.0" }, { "advisory": "AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.12.14, the Python parser is vulnerable to a request smuggling vulnerability due to not parsing trailer sections of an HTTP request. If a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or AIOHTTP_NO_EXTENSIONS is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections. Version 3.12.14 contains a patch for this issue.", "cve": "CVE-2025-53643", "id": "pyup.io-78162", "more_info_path": "/vulnerabilities/CVE-2025-53643/78162", "specs": [ "<3.12.14" ], "v": "<3.12.14" }, { "advisory": "Affected versions of the aiohttp package are vulnerable to Denial of Service (DoS) due to unbounded decompression of highly compressed HTTP request bodies when the HTTP parser auto_decompress feature is enabled.", "cve": "CVE-2025-69223", "id": "pyup.io-83955", "more_info_path": "/vulnerabilities/CVE-2025-69223/83955", "specs": [ "<3.13.3" ], "v": "<3.13.3" }, { "advisory": "Affected versions of the aiohttp package are vulnerable to Request Smuggling due to inconsistent Unicode processing of non-ASCII HTTP header values. In the pure-Python HTTP parser (used when the C extensions are not installed or when AIOHTTP_NO_EXTENSIONS is enabled), aiohttp.http_parser.parse_headers() and helpers such as _is_supported_upgrade() and HttpParser._is_chunked_te() apply .lower() to Upgrade, Transfer-Encoding, and Content-Encoding values without first enforcing ASCII-only input, allowing certain non-ASCII characters to be transformed during case-folding and creating parsing discrepancies.", "cve": "CVE-2025-69224", "id": "pyup.io-83956", "more_info_path": "/vulnerabilities/CVE-2025-69224/83956", "specs": [ "<3.13.3" ], "v": "<3.13.3" }, { "advisory": "Affected versions of the aiohttp package are vulnerable to Request Smuggling due to Unicode digit matching in the Range header parser. In aiohttp.web_request.BaseRequest.http_range, the Range header is parsed with the regular expression ^bytes=(\\d*)-(\\d*)$ via re.findall(...) without restricting \\d to ASCII, which allows non-ASCII decimal characters to be accepted as valid byte-range values.", "cve": "CVE-2025-69225", "id": "pyup.io-83957", "more_info_path": "/vulnerabilities/CVE-2025-69225/83957", "specs": [ "<3.13.3" ], "v": "<3.13.3" }, { "advisory": "Affected versions of the aiohttp package are vulnerable to Information Disclosure due to static-file path normalisation enabling inference of absolute path component existence. In aiohttp, applications that register a static route via aiohttp.web.static() may expose filesystem path information because the static handler\u2019s normalization and response behaviour lets a requester distinguish which absolute path components exist.", "cve": "CVE-2025-69226", "id": "pyup.io-83958", "more_info_path": "/vulnerabilities/CVE-2025-69226/83958", "specs": [ "<3.13.3" ], "v": "<3.13.3" }, { "advisory": "Affected versions of the aiohttp package are vulnerable to Denial of Service (DoS) due to relying on Python assert statements for malformed request handling, which are removed when interpreter optimizations are enabled. The aiohttp.web_request.Request.post() method can trigger an infinite loop in multipart POST body processing because assertions in multipart parsing paths, such as aiohttp.multipart.BodyPartReader.read_chunk() and _read_chunk_from_stream() are bypassed, preventing the code from enforcing an exit condition on invalid EOF and boundary states.", "cve": "CVE-2025-69227", "id": "pyup.io-83959", "more_info_path": "/vulnerabilities/CVE-2025-69227/83959", "specs": [ "<3.13.3" ], "v": "<3.13.3" }, { "advisory": "Affected versions of the aiohttp package are vulnerable to Denial of Service (DoS) due to improper enforcement of request size limits during multipart form parsing. The aiohttp aiohttp.web_request.Request.post() method in aiohttp/web_request.py iterates over multipart fields but (prior to the fix) resets its running byte counter per part rather than tracking the total size of the entire multipart form, allowing the aggregate payload to grow without being bounded by client_max_size.", "cve": "CVE-2025-69228", "id": "pyup.io-83967", "more_info_path": "/vulnerabilities/CVE-2025-69228/83967", "specs": [ "<3.13.3" ], "v": "<3.13.3" }, { "advisory": "Affected versions of the aiohttp package are vulnerable to Denial of Service (DoS) due to excessive blocking CPU usage when processing a large number of HTTP chunked messages. When an aiohttp server endpoint calls request.read(), the chunked body handling performs costly per-chunk processing that can consume a moderate amount of blocking CPU time (for example, around one second) when the request contains an unusually large number of chunks.", "cve": "CVE-2025-69229", "id": "pyup.io-83968", "more_info_path": "/vulnerabilities/CVE-2025-69229/83968", "specs": [ "<3.13.3" ], "v": "<3.13.3" }, { "advisory": "Affected versions of the aiohttp package are vulnerable to Denial of Service (DoS) due to excessive warning-level logging when parsing invalid Cookie headers. When server code accesses aiohttp.web_request.Request.cookies, the aiohttp._cookie_helpers.parse_cookie_header() function validates cookie names and can emit a log entry for each illegal cookie name, enabling a single request to generate a large number of warning logs.", "cve": "CVE-2025-69230", "id": "pyup.io-83969", "more_info_path": "/vulnerabilities/CVE-2025-69230/83969", "specs": [ "<3.13.3" ], "v": "<3.13.3" }, { "advisory": "Aiohttp 3.7.4 includes a fix for CVE-2021-21330: In aiohttp before version 3.7.4 there is an open redirect vulnerability. A maliciously crafted link to an aiohttp-based web-server could redirect the browser to a different website. It is caused by a bug in the 'aiohttp.web_middlewares.normalize_path_middleware' middleware. A workaround can be to avoid using 'aiohttp.web_middlewares.normalize_path_middleware' in your applications.\r\nhttps://github.com/aio-libs/aiohttp/security/advisories/GHSA-v6wp-4m6f-gcjg", "cve": "CVE-2021-21330", "id": "pyup.io-39659", "more_info_path": "/vulnerabilities/CVE-2021-21330/39659", "specs": [ "<3.7.4" ], "v": "<3.7.4" }, { "advisory": "Aiohttp 3.8.0 includes a fix for CVE-2023-47641: Affected versions of aiohttp have a security vulnerability regarding the inconsistent interpretation of the http protocol. HTTP/1.1 is a persistent protocol, if both Content-Length(CL) and Transfer-Encoding(TE) header values are present it can lead to incorrect interpretation of two entities that parse the HTTP and we can poison other sockets with this incorrect interpretation. A possible Proof-of-Concept (POC) would be a configuration with a reverse proxy(frontend) that accepts both CL and TE headers and aiohttp as backend. As aiohttp parses anything with chunked, we can pass a chunked123 as TE, the frontend entity will ignore this header and will parse Content-Length. The impact of this vulnerability is that it is possible to bypass any proxy rule, poisoning sockets to other users like passing Authentication Headers, also if it is present an Open Redirect an attacker could combine it to redirect random users to another website and log the request.\r\nhttps://github.com/aio-libs/aiohttp/security/advisories/GHSA-xx9p-xxvh-7g8j", "cve": "CVE-2023-47641", "id": "pyup.io-62327", "more_info_path": "/vulnerabilities/CVE-2023-47641/62327", "specs": [ "<3.8.0" ], "v": "<3.8.0" }, { "advisory": "Aiohttp 3.8.0 adds validation of HTTP header keys and values to prevent header injection.\r\nhttps://github.com/aio-libs/aiohttp/issues/4818", "cve": "PVE-2021-42692", "id": "pyup.io-42692", "more_info_path": "/vulnerabilities/PVE-2021-42692/42692", "specs": [ "<3.8.0" ], "v": "<3.8.0" }, { "advisory": "Aiohttp 3.8.6 updates vendored copy of 'llhttp' to v9.1.3 to include a security fix.\r\nhttps://github.com/aio-libs/aiohttp/security/advisories/GHSA-pjjw-qhg8-p2p9", "cve": "PVE-2023-61657", "id": "pyup.io-61657", "more_info_path": "/vulnerabilities/PVE-2023-61657/61657", "specs": [ "<3.8.6" ], "v": "<3.8.6" }, { "advisory": "Aiohttp 3.8.6 includes a fix for CVE-2023-47627: The HTTP parser in AIOHTTP has numerous problems with header parsing, which could lead to request smuggling. This parser is only used when AIOHTTP_NO_EXTENSIONS is enabled (or not using a prebuilt wheel).\r\nhttps://github.com/aio-libs/aiohttp/security/advisories/GHSA-gfw2-4jvh-wgfg", "cve": "CVE-2023-47627", "id": "pyup.io-62326", "more_info_path": "/vulnerabilities/CVE-2023-47627/62326", "specs": [ "<3.8.6" ], "v": "<3.8.6" }, { "advisory": "Affected versions of `aiohttp` are vulnerable to an Improper Validation vulnerability. It is possible for an attacker to modify the HTTP request (e.g. insert a new header) or even create a new HTTP request if the attacker controls the HTTP method. The vulnerability occurs only if the attacker can control the HTTP method (GET, POST etc.) of the request. If the attacker can control the HTTP version of the request it will be able to modify the request (request smuggling).", "cve": "CVE-2023-49082", "id": "pyup.io-62583", "more_info_path": "/vulnerabilities/CVE-2023-49082/62583", "specs": [ "<3.9.0" ], "v": "<3.9.0" }, { "advisory": "The aiohttp versions minor than 3.9. has a vulnerability that affects the Python HTTP parser used in the aiohttp library. It allows for minor differences in allowable character sets, which could lead to robust frame boundary matching of proxies to protect against the injection of additional requests. The vulnerability also allows \r\n exceptions during validation that aren't handled consistently with other malformed inputs.", "cve": "CVE-2024-23829", "id": "pyup.io-64644", "more_info_path": "/vulnerabilities/CVE-2024-23829/64644", "specs": [ "<3.9.1" ], "v": "<3.9.1" }, { "advisory": "Affected versions of `aiohttp` are vulnerable to an infinite loop condition. This occurs when an attacker sends a specially crafted POST (multipart/form-data) request. Upon processing, the `aiohttp` server enters an infinite loop, preventing it from processing further requests. This results in a denial-of-service (DoS) attack, allowing an attacker to stop the application from serving requests after a single request. Users are advised to upgrade to version 3.9.4 or manually apply a patch to their systems as per the linked GHSA instructions.", "cve": "CVE-2024-30251", "id": "pyup.io-71545", "more_info_path": "/vulnerabilities/CVE-2024-30251/71545", "specs": [ "<3.9.4" ], "v": "<3.9.4" }, { "advisory": "Aiohttp 3.8.5 includes a fix for CVE-2023-37276: Sending a crafted HTTP request will cause the server to misinterpret one of the HTTP header values leading to HTTP request smuggling.\r\nhttps://github.com/aio-libs/aiohttp/commit/9337fb3f2ab2b5f38d7e98a194bde6f7e3d16c40\r\nhttps://github.com/aio-libs/aiohttp/security/advisories/GHSA-45c4-8wx5-qw6w", "cve": "CVE-2023-37276", "id": "pyup.io-59725", "more_info_path": "/vulnerabilities/CVE-2023-37276/59725", "specs": [ "<=3.8.4" ], "v": "<=3.8.4" }, { "advisory": "The vulnerability lies in the improper configuration of static resource resolution when aiohttp is used as a web server. It occurs when the follow_symlinks option is enabled without proper validation, leading to directory traversal vulnerabilities. Unauthorized access to arbitrary files on the system could potentially occur. The affected versions are >1.0.5, and the issue was patched in version 3.9.2. As a workaround, it is advised to disable the follow_symlinks option outside of a restricted local development environment, especially in a server accepting requests from remote users. Using a reverse proxy server to handle static resources is also recommended.\r\nhttps://github.com/aio-libs/aiohttp/commit/1c335944d6a8b1298baf179b7c0b3069f10c514b", "cve": "CVE-2024-23334", "id": "pyup.io-64642", "more_info_path": "/vulnerabilities/CVE-2024-23334/64642", "specs": [ ">1.0.5,<3.9.2" ], "v": ">1.0.5,<3.9.2" }, { "advisory": "Affected versions of the `aiohttp` package are vulnerable to Cross-site Scripting (XSS) due to improper sanitization of user input on index pages for static file handling. The vulnerability exists because the `show_index` option, when enabled, allows unsanitized user input to be rendered directly into the HTML content of directory listings. An attacker can exploit this vulnerability by crafting a malicious URL that, when accessed, executes arbitrary JavaScript in the context of the user's browser, potentially leading to session hijacking or data theft.", "cve": "CVE-2024-27306", "id": "pyup.io-70630", "more_info_path": "/vulnerabilities/CVE-2024-27306/70630", "specs": [ ">=1.0.0,<3.9.4", ">=4.0.0a0,<=4.0.0a1" ], "v": ">=1.0.0,<3.9.4,>=4.0.0a0,<=4.0.0a1" }, { "advisory": "Affected versions of aiohttp are vulnerable to HTTP Request Smuggling (CWE-444). This vulnerability allows attackers to inject malicious HTTP messages by including line feeds (LF) in chunk extensions, potentially bypassing security controls and executing unauthorized actions. The attack vector involves sending specially crafted chunked HTTP requests to exploit the improper parsing in the HttpPayloadParser class. To mitigate, upgrade to aiohttp version which validates chunk extensions by rejecting any containing unexpected LFs, thereby preventing request smuggling attacks.", "cve": "CVE-2024-52304", "id": "pyup.io-74251", "more_info_path": "/vulnerabilities/CVE-2024-52304/74251", "specs": [ ">=2.0.0rc1,<3.10.11" ], "v": ">=2.0.0rc1,<3.10.11" }, { "advisory": "Affected versions of the `aiohttp` package are vulnerable to Improper Input Validation due to insufficient checks on the HTTP version of incoming requests. The vulnerability arises because the HTTP request handling mechanism does not adequately validate the HTTP version, allowing manipulation if controlled by an attacker. An attacker with the ability to influence the HTTP version can exploit this flaw to inject new headers or craft entirely new HTTP requests, potentially leading to unauthorized actions or data exposure.", "cve": "CVE-2023-49081", "id": "pyup.io-62582", "more_info_path": "/vulnerabilities/CVE-2023-49081/62582", "specs": [ ">=2.0.0rc1,<3.9.0", ">=4.0.0a0,<=4.0.0a1" ], "v": ">=2.0.0rc1,<3.9.0,>=4.0.0a0,<=4.0.0a1" }, { "advisory": "Affected versions of aiohttp are vulnerable to Directory Traversal (CWE-22). This allows attackers to access sensitive files outside the intended directory by exploiting symbolic links with compressed file extensions. The vulnerability exists in the FileResponse class, where stat() is used instead of lstat(), causing the server to follow symlinks when checking for compressed file variants. To mitigate, update aiohttp to include the fix or modify the code to use lstat() and ensure only regular files are served.", "cve": "CVE-2024-42367", "id": "pyup.io-74380", "more_info_path": "/vulnerabilities/CVE-2024-42367/74380", "specs": [ ">=3.10.0b1,<3.10.2" ], "v": ">=3.10.0b1,<3.10.2" }, { "advisory": "Affected versions of aiohttp are vulnerable to Middleware Cache Pollution. This vulnerability allows attackers to potentially interfere with middleware handling by exploiting cached middleware associated with system routes. The impact includes possible bypassing of security middleware or unintended access to internal routes. The attack vector involves crafting requests that target system routes, causing the middleware cache to store and reuse inappropriate middleware configurations. The vulnerable methods are _build_middlewares and the middleware caching mechanism in web_app.py. To mitigate, upgrade to aiohttp version, which prevents system routes from polluting the middleware cache by excluding SystemRoute instances from caching.", "cve": "CVE-2024-52303", "id": "pyup.io-74252", "more_info_path": "/vulnerabilities/CVE-2024-52303/74252", "specs": [ ">=3.10.6rc0,<3.10.11", ">=3.11.0b0,<3.11.0" ], "v": ">=3.10.6rc0,<3.10.11,>=3.11.0b0,<3.11.0" } ], "aiohttp-auth-autz": [ { "advisory": "Aiohttp-auth-autz before 0.2.0 isn't correctly checking the user_id in acl middleware, leading to a possible permission escalation.\r\nhttps://github.com/ilex/aiohttp_auth_autz/commit/b8bb3178786daebc828298dc0d1988b191890495", "cve": "PVE-2021-32971", "id": "pyup.io-32971", "more_info_path": "/vulnerabilities/PVE-2021-32971/32971", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "aiohttp-jinja2": [ { "advisory": "Aiohttp-jinja2 1.1.1 updates minimal supported 'Jinja2' version to 2.10.1 to include security fixes.", "cve": "CVE-2019-10906", "id": "pyup.io-44432", "more_info_path": "/vulnerabilities/CVE-2019-10906/44432", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Aiohttp-jinja2 1.1.1 updates minimal supported 'Jinja2' version to 2.10.1 to include security fixes.", "cve": "CVE-2014-1402", "id": "pyup.io-37095", "more_info_path": "/vulnerabilities/CVE-2014-1402/37095", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Aiohttp-jinja2 1.1.1 updates minimal supported 'Jinja2' version to 2.10.1 to include security fixes.", "cve": "CVE-2016-10745", "id": "pyup.io-44431", "more_info_path": "/vulnerabilities/CVE-2016-10745/44431", "specs": [ "<1.1.1" ], "v": "<1.1.1" } ], "aiohttp-proxies": [ { "advisory": "Aiohttp-proxies is a malicious package. It contains a backdoor.\r\nhttps://blog.sonatype.com/can-you-spot-this-cryptic-reverse-shell-found-in-pypi-packages", "cve": "PVE-2022-47805", "id": "pyup.io-47805", "more_info_path": "/vulnerabilities/PVE-2022-47805/47805", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "aiohttp-session": [ { "advisory": "aio-libs aiohttp-session contains a Session Fixation vulnerability in load_session function for RedisStorage (see: https://github.com/aio-libs/aiohttp-session/blob/master/aiohttp_session/redis_storage.py#L42) that can result in Session Hijacking. This attack appear to be exploitable via Any method that allows setting session cookies (?session=<>, or meta tags or script tags with Set-Cookie).", "cve": "CVE-2018-1000519", "id": "pyup.io-53986", "more_info_path": "/vulnerabilities/CVE-2018-1000519/53986", "specs": [ ">=0,<2.4.0" ], "v": ">=0,<2.4.0" }, { "advisory": "aio-libs aiohttp-session version 2.6.0 and earlier contains a Other/Unknown vulnerability in EncryptedCookieStorage and NaClCookieStorage that can result in Non-expiring sessions / Infinite lifespan. This attack appear to be exploitable via Recreation of a cookie post-expiry with the same value.", "cve": "CVE-2018-1000814", "id": "pyup.io-53989", "more_info_path": "/vulnerabilities/CVE-2018-1000814/53989", "specs": [ ">=0,<2.7.0" ], "v": ">=0,<2.7.0" } ], "aiohttp-socks4": [ { "advisory": "Aiohttp-socks4 is a malicious package, typosquatting. It installs a Trojan in your system.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick", "cve": "PVE-2022-47816", "id": "pyup.io-47816", "more_info_path": "/vulnerabilities/PVE-2022-47816/47816", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "aiohttp-socks5": [ { "advisory": "Aiohttp-socks5 is a malicious package, typosquatting. It installs a Trojan in your system.\r\nhttps://blog.sonatype.com/trojanized-pypi-package-imitates-a-popular-python-server-library", "cve": "PVE-2022-47822", "id": "pyup.io-47822", "more_info_path": "/vulnerabilities/PVE-2022-47822/47822", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "aiohttp-swagger": [ { "advisory": "Aiohttp-swagger before 1.0.15 includes a version of js-yaml that's not secure.", "cve": "PVE-2021-38483", "id": "pyup.io-38483", "more_info_path": "/vulnerabilities/PVE-2021-38483/38483", "specs": [ "<1.0.15" ], "v": "<1.0.15" } ], "aiokafka": [ { "advisory": "Aiokafka 0.4.0 includes a fix for a potential race condition vulnerability.\r\nhttps://github.com/aio-libs/aiokafka/pull/286", "cve": "PVE-2023-62410", "id": "pyup.io-62410", "more_info_path": "/vulnerabilities/PVE-2023-62410/62410", "specs": [ "<0.4.0" ], "v": "<0.4.0" } ], "aiolifx-themes": [ { "advisory": "Aiolifx-themes 0.4.1 updates its dependency 'setuptools' to v65.5.1 to include a security fix.", "cve": "CVE-2022-40897", "id": "pyup.io-52569", "more_info_path": "/vulnerabilities/CVE-2022-40897/52569", "specs": [ "<0.4.1" ], "v": "<0.4.1" } ], "aiomysql": [ { "advisory": "Affected versions of the aiomysql package are vulnerable to Information Disclosure due to failure to enforce the local_infile setting and related client capability when handling MySQL \u201cLOAD DATA LOCAL\u201d requests. The aiomysql.connect parameter and capability bit were ignored by the LOAD_LOCAL packet handler, allowing a rogue server to send a LOAD_LOCAL instruction and have aiomysql read and upload server-specified file paths despite local_infile=0.", "cve": "CVE-2025-62611", "id": "pyup.io-80588", "more_info_path": "/vulnerabilities/CVE-2025-62611/80588", "specs": [ "<0.3.0" ], "v": "<0.3.0" } ], "aiootp": [ { "advisory": "The `Opake.client` & `Opake.client_registration` methods in aiootp version 0.11.0 take an instantiated client database instead of client credentials which improves security, efficiency & usability. This change reduces the amount of exposure received by user passwords & other credentials. It also simplifies usage of the protocol by only needing to carry around a database instead of a slew of credentials, which is also faster, since the credentials are passed through the cpu & memory hard `passcrypt` function every time to open the database.", "cve": "PVE-2021-38602", "id": "pyup.io-38602", "more_info_path": "/vulnerabilities/PVE-2021-38602/38602", "specs": [ "<0.11.0" ], "v": "<0.11.0" }, { "advisory": "Aiootp 0.13.0 contains a security patch for 'xor' and 'axor' functions which define the one-time-pad cipher (they can leak <1-bit of plaintext).", "cve": "PVE-2021-39508", "id": "pyup.io-39508", "more_info_path": "/vulnerabilities/PVE-2021-39508/39508", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Aiootp 0.17.0 includes a security patch for a critical vulnerability.The HMAC verifiers on ciphertexts did not include the 'salt' or 'pid' values when deriving the HMAC. This associated data can therefore be changed to cause a party to decrypt a past ciphertext with a salt or pid of an attacker's choosing.", "cve": "PVE-2021-39534", "id": "pyup.io-39534", "more_info_path": "/vulnerabilities/PVE-2021-39534/39534", "specs": [ "<0.17.0" ], "v": "<0.17.0" }, { "advisory": "Aiootp 0.18.0 rewrites the HMAC validation procedure for all ciphers. The new StreamHMAC class ensures the user must contend with ciphertext validation even when using the *_encipher, *_decipher & *_xor Comprende generators.\r\nhttps://github.com/rmlibre/aiootp/commit/7700ed9fc7cc3255b85bef9ff2531a2ec511f5bd", "cve": "PVE-2021-40254", "id": "pyup.io-40254", "more_info_path": "/vulnerabilities/PVE-2021-40254/40254", "specs": [ "<0.18.0" ], "v": "<0.18.0" }, { "advisory": "Aiootp 0.18.1 deprecates and replaces an internal 'kdf' for saving database tags due to a vulnerability: If an adversary can get a user to reveal the value returned by the 'HMAC' method when fed the tag file's filename & the salt used for that encrypted tag, then they could deduce the decryption key for the tag.", "cve": "PVE-2021-40253", "id": "pyup.io-40253", "more_info_path": "/vulnerabilities/PVE-2021-40253/40253", "specs": [ "<0.18.1" ], "v": "<0.18.1" }, { "advisory": "Aiootp 0.19.0 includes several important security patches and other improvements.", "cve": "PVE-2021-40252", "id": "pyup.io-40252", "more_info_path": "/vulnerabilities/PVE-2021-40252/40252", "specs": [ "<0.19.0" ], "v": "<0.19.0" }, { "advisory": "Aiootp 0.19.3 removes 'map_encipher', 'map_decipher', 'amap_encipher' and 'amap_decipher' generators from the 'Chunky2048' and 'Comprende' classes due to security reasons.", "cve": "PVE-2021-40251", "id": "pyup.io-40251", "more_info_path": "/vulnerabilities/PVE-2021-40251/40251", "specs": [ "<0.19.3" ], "v": "<0.19.3" }, { "advisory": "Aiootp 0.2.0 adds ephemeral salts to the ``AsyncDatabase`` & ``Database`` file encryption procedures. This is a major security fix, as re-encryption of files with the same tag in a database with the same open key would use the same streams of key material each time, breaking encryption if two different versions of a tag file's ciphertext stored to disk were available to an adversary. The database methods ``encrypt``, ``decrypt``, ``aencrypt`` & ``adecrypt`` will now produce and decipher true one-time pad ciphertext with these ephemeral salts.", "cve": "PVE-2021-38250", "id": "pyup.io-38250", "more_info_path": "/vulnerabilities/PVE-2021-38250/38250", "specs": [ "<0.2.0" ], "v": "<0.2.0" }, { "advisory": "Aiootp 0.22.0 includes a fix for a high severity vulnerability: The top-level '(a)csprng' functions were found to be unsafe in concurrent code, leading to the possibility of producing identical outputs from distinct calls if run in quick succession from concurrently running threads & co-routines. The classification of this vulnerability is severe because: 1) users should be able to expect the output of a 64-byte cryptographically secure pseudo-random number generator to always produce unique outputs; and, 2) much of the package utilizes them to produce cryptographic material. This vulnerability does not effect users of the library which are not running it in multiple concurrent threads or co-routines.", "cve": "PVE-2023-53025", "id": "pyup.io-53025", "more_info_path": "/vulnerabilities/PVE-2023-53025/53025", "specs": [ "<0.22.0" ], "v": "<0.22.0" }, { "advisory": "The ``AsyncDatabase`` & ``Database`` in aiootp version 0.3.0 use the more secure ``afilename`` & ``filename`` methods to derive the hashmap name and encryption streams from a user-defined tag internal to their ``aencrypt`` / ``adecrypt`` / ``encrypt`` / ``decrypt`` methods, as well as, prior to them getting called. This will break past versions of databases' ability to open their files.", "cve": "PVE-2021-38256", "id": "pyup.io-38256", "more_info_path": "/vulnerabilities/PVE-2021-38256/38256", "specs": [ "<0.3.0" ], "v": "<0.3.0" }, { "advisory": "Aiootp 0.6.0 replaces several usages of ``random.randrange`` within ``randoms.py`` to calls to ``secrets.token_bytes`` which is faster & more secure.", "cve": "PVE-2021-38361", "id": "pyup.io-38361", "more_info_path": "/vulnerabilities/PVE-2021-38361/38361", "specs": [ "<0.6.0" ], "v": "<0.6.0" }, { "advisory": "Aiootp 0.8.0 fixes the test_hmac and atest_hmac functions in the keys & database classes. The new non-constant-time algorithm needs a random salt to be added before doing the secondary hmac to prevent some potential exotic forms of chosen plaintext/ciphertext attacks on the algorithm. The last version of the algorithm should not be used. \r\n\r\nAlso, the 'Keys' & 'AsyncKeys' interfaces were overhauled to remove the persistance of instance salts. They were intended to be updated by users with the 'reset' & 'areset' methods, but that cannot be guaranteed easily through the class, so it is an inappropriate interface since reusing salts for encryption is completely insecure. The instances do still maintain state of their main encryption key, & new stateful methods for key generation, like 'mnemonic' & 'table_key', have been added. The 'state' & 'astate' methods have been removed.", "cve": "PVE-2021-38381", "id": "pyup.io-38381", "more_info_path": "/vulnerabilities/PVE-2021-38381/38381", "specs": [ "<0.8.0" ], "v": "<0.8.0" }, { "advisory": "Aiootp 0.8.1 adds cryptographically secure pseudo-random values as default keys in encryption functions to safeguard against users accidentally encrypting data without specifying a key. This way, such mistakes will produce ciphertext with an unrecoverable key, instead of without a key at all.", "cve": "PVE-2021-38395", "id": "pyup.io-38395", "more_info_path": "/vulnerabilities/PVE-2021-38395/38395", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Aiootp 0.9.0 adds hmac codes to ciphertext for the following functions: 'json_encrypt', 'ajson_encrypt', 'bytes_encrypt', 'abytes_encrypt', 'Database.encrypt' & 'AsyncDatabase.aencrypt'. This change greatly increases the security of ciphertext by ensuring it hasn't been modified or tampered with maliciously. One-time pad ciphertext is maleable, so without hmac validation it can be changed to successfully allow decryption but return the wrong plaintext. These functions are the highest level abstractions of the library for encryption/decryption, which made them excellent targets for this important security update. As well, it isn't easily possible for the library to provide hmac codes for generators that produce ciphertext, because the end of a stream of ciphertext isn't known until after the results have left the scope of library code. So users will need to produce their own hmac codes for generator ciphertext unless we find an elegant solution to this issue. These functions now all return dictionaries with the associated hmac stored in the 'hmac' entry. The bytes functions formerly returned lists, now their ciphertext is available from the '\"ciphertext\"' entry. And, all database files will have an hmac attached to them now. These changes were designed to still be compatible with old ciphertexts but they'll likely be made incompatible by the v0.11.x major release.", "cve": "PVE-2021-38401", "id": "pyup.io-38401", "more_info_path": "/vulnerabilities/PVE-2021-38401/38401", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Aiootp 0.9.1 includes two security improvements:\r\n\r\n- Any falsey values for the 'salt' keyword argument in the library's 'keys', 'akeys', 'bytes_keys', 'abytes_keys', 'subkeys', & 'asubkeys' infinite keystream generators, & other functions around the library, will cause them to generate a new cryptographically secure pseudo-random value for the salt. It formerly only did this when 'salt' was 'None'. \r\n\r\n- The 'seeder' & 'aseeder' generators have been updated to introduce 512 new bits of entropy from 'secrets.token_bytes' on every iteration to ensure that the CSPRNG will produce secure outputs even if its internal state is somehow discovered. This also allows for simply calling the CSPRNG is enough, there's no longer a strong reason to pass new entropy into it manually, except to add even more entropy as desired.", "cve": "PVE-2021-38406", "id": "pyup.io-38406", "more_info_path": "/vulnerabilities/PVE-2021-38406/38406", "specs": [ "<0.9.1" ], "v": "<0.9.1" }, { "advisory": "Aiootp 0.9.2 adds 'passcrypt' & 'apasscrypt' instance methods to 'OneTimePad', 'Keys', & 'AsyncKeys' classes. They produce password hashes that are not just secured by the salt & passcrypt algorithm settings, but also by their main symmetric instance keys. This makes passwords infeasible to crack without also compromising the instance's 512-bit key.\r\n\r\nAlso, Aiootp 0.9.2 includes further improvements to the random number generator in 'randoms.py'. This made its internals less sequential and thereby raises the bar of work needed by an attacker to successfully carry out an order prediction attack.", "cve": "PVE-2021-38409", "id": "pyup.io-38409", "more_info_path": "/vulnerabilities/PVE-2021-38409/38409", "specs": [ "<0.9.2" ], "v": "<0.9.2" } ], "aiopioneer": [ { "advisory": "In version 0.1.5, aiopioneer resolves a race condition with the implementation of safe_wait_for, which enhances the handling of asynchronous tasks, especially during cancellations and event updates. \r\nhttps://github.com/crowbarz/aiopioneer/commit/f6f7ce66226825df9e039ed5f12f34812dcc4a7d", "cve": "PVE-2024-65890", "id": "pyup.io-65890", "more_info_path": "/vulnerabilities/PVE-2024-65890/65890", "specs": [ "<0.1.5" ], "v": "<0.1.5" }, { "advisory": "Aiopioneer version 0.4.3 addresses a race condition that potentially improves the reliability of the communication process by ensuring responses are queued effectively before sending a request. \r\nhttps://github.com/crowbarz/aiopioneer/commit/4a310412a3342e7a44b3d8aa1f8633c9575871fb", "cve": "PVE-2024-65889", "id": "pyup.io-65889", "more_info_path": "/vulnerabilities/PVE-2024-65889/65889", "specs": [ "<0.4.3" ], "v": "<0.4.3" } ], "aioradio": [ { "advisory": "Aioradio 0.17.9 updates 'httpx' to v0.23.0 to include a security fix.", "cve": "CVE-2021-41945", "id": "pyup.io-50342", "more_info_path": "/vulnerabilities/CVE-2021-41945/50342", "specs": [ "<0.17.9" ], "v": "<0.17.9" } ], "aiosmtpd": [ { "advisory": "aiosmtpd is a reimplementation of the Python stdlib smtpd.py based on asyncio. aiosmtpd is vulnerable to inbound SMTP smuggling. SMTP smuggling is a novel vulnerability based on not so novel interpretation differences of the SMTP protocol. By exploiting SMTP smuggling, an attacker may send smuggle/spoof e-mails with fake sender addresses, allowing advanced phishing attacks. This issue is also existed in other SMTP software like Postfix. With the right SMTP server constellation, an attacker can send spoofed e-mails to inbound/receiving aiosmtpd instances. This issue has been addressed in version 1.4.5. Users are advised to upgrade. There are no known workarounds for this vulnerability. See CVE-2024-27305.", "cve": "CVE-2024-27305", "id": "pyup.io-66968", "more_info_path": "/vulnerabilities/CVE-2024-27305/66968", "specs": [ "<1.4.5" ], "v": "<1.4.5" }, { "advisory": "aiosmptd is a reimplementation of the Python stdlib smtpd.py based on asyncio. Prior to version 1.4.6, servers based on aiosmtpd accept extra unencrypted commands after STARTTLS, treating them as if they came from inside the encrypted connection. This could be exploited by a man-in-the-middle attack. Version 1.4.6 contains a patch for the issue. See CVE-2024-34083.", "cve": "CVE-2024-34083", "id": "pyup.io-71242", "more_info_path": "/vulnerabilities/CVE-2024-34083/71242", "specs": [ "<=1.4.5" ], "v": "<=1.4.5" } ], "aiosmtplib": [ { "advisory": "Aiosmtplib 1.1.7 fixes a possible injection vulnerability (a variant of https://consensys.net/diligence/vulnerabilities/python-smtplib-multiple-crlf-injection/).", "cve": "PVE-2022-50882", "id": "pyup.io-50882", "more_info_path": "/vulnerabilities/PVE-2022-50882/50882", "specs": [ "<1.1.7" ], "v": "<1.1.7" } ], "aiosolr": [ { "advisory": "Aiosolr 3.3.2 updates its dependency 'bleach' to v3.3.0 to include a security fix.", "cve": "CVE-2021-23980", "id": "pyup.io-40299", "more_info_path": "/vulnerabilities/CVE-2021-23980/40299", "specs": [ "<3.3.2" ], "v": "<3.3.2" } ], "aiosyslogd": [ { "advisory": "Affected versions of this package are vulnerable to Cross-Site Scripting (XSS). The dynamic log message highlighter in `index.html` uses `innerHTML` to manipulate log message content without proper sanitization, leading to arbitrary JavaScript execution when malicious log messages containing HTML or script tags are displayed. An attacker can exploit this vulnerability by injecting crafted syslog messages with embedded JavaScript that executes in the browser context of users viewing the logs, enabling session hijacking, credential theft, or unauthorized actions.", "cve": "PVE-2026-84490", "id": "pyup.io-84490", "more_info_path": "/vulnerabilities/PVE-2026-84490/84490", "specs": [ "<1.0.4" ], "v": "<1.0.4" } ], "aiotoolbox": [ { "advisory": "Aiotoolbox is a malicious package. It contains a custom script in setup.py that downloads malicious and obfuscated code.\r\nhttps://inspector.pypi.io/project/aiotoolbox/1.5.2/packages/a0/9b/a3d1fdfb3036ad1bb6ee69f50eab85d042e7cd39ab24b3e8a1c0accbad1d/aiotoolbox-1.5.2.tar.gz/aiotoolbox-1.5.2/setup.py#line.60", "cve": "PVE-2023-53560", "id": "pyup.io-53560", "more_info_path": "/vulnerabilities/PVE-2023-53560/53560", "specs": [ ">=0" ], "v": ">=0" } ], "aioxmpp": [ { "advisory": "aioxmpp version 0.10.2 and earlier contains a Improper Handling of Structural Elements vulnerability in Stanza Parser, rollback during error processing, aioxmpp.xso.model.guard function that can result in Denial of Service, Other. This attack appears to be exploitable via Remote. A crafted stanza can be sent to an application which uses the vulnerable components to either inject data in a different context or cause the application to reconnect (potentially losing data). This vulnerability appears to have been fixed in 0.10.3.", "cve": "CVE-2019-1000007", "id": "pyup.io-42257", "more_info_path": "/vulnerabilities/CVE-2019-1000007/42257", "specs": [ "<=0.10.2" ], "v": "<=0.10.2" } ], "airflow": [ { "advisory": "Apache-airflow 1.8.0 includes a fix for a code execution vulnerability in PrestoHook.", "cve": "PVE-2023-99973", "id": "pyup.io-60835", "more_info_path": "/vulnerabilities/PVE-2023-99973/60835", "specs": [ "<1.8.0" ], "v": "<1.8.0" }, { "advisory": "Specific versions of Airflow are susceptible to arbitrary code execution due to unchecked user input being sent to the Python eval function, allowing for direct execution of parameters. This vulnerability enables any user with the capability to create or edit charts to potentially execute arbitrary code on the server.\r\nhttps://github.com/apache/airflow/commit/88d9b0dc96e7528c87326c8070ee276e8565545f", "cve": "PVE-2024-99818", "id": "pyup.io-65907", "more_info_path": "/vulnerabilities/PVE-2024-99818/65907", "specs": [ "<1.9.0-1" ], "v": "<1.9.0-1" } ], "airflow-duckdb": [ { "advisory": "Airflow-duckdb version 0.1.1 updates its cryptography dependency from 42.0.2 to 42.0.4 to address the security issue CVE-2024-26130, enhancing its security features.\r\nhttps://github.com/hussein-awala/airflow-duckdb/commit/bdae387e9ee2c7045091b20632a740236405e54c", "cve": "CVE-2024-26130", "id": "pyup.io-65643", "more_info_path": "/vulnerabilities/CVE-2024-26130/65643", "specs": [ "<0.1.1" ], "v": "<0.1.1" }, { "advisory": "Airflow-duckdb 0.1.2 upgrades its flask-appbuilder dependency to version 4.3.11 from 4.3.10, addressing the security vulnerability detailed in CVE-2024-25128.\r\nhttps://github.com/hussein-awala/airflow-duckdb/pull/3/commits/b779796b3e675208f7698840cc3bf0dc88e9b21e", "cve": "CVE-2024-25128", "id": "pyup.io-65717", "more_info_path": "/vulnerabilities/CVE-2024-25128/65717", "specs": [ "<0.1.2" ], "v": "<0.1.2" } ], "airunner": [ { "advisory": "Affected versions of the airunner package are vulnerable to Improper Access Control due to DarkLock network restrictions not being activated alongside the OS sandbox in the bundled facehuggershield integration.", "cve": "PVE-2025-82222", "id": "pyup.io-82222", "more_info_path": "/vulnerabilities/PVE-2025-82222/82222", "specs": [ "<5.0.4" ], "v": "<5.0.4" } ], "aisee": [ { "advisory": "Aisee upgraded PyTorch to version 2.2.0 or higher to address a security vulnerability identified as CVE-2024-31580.", "cve": "CVE-2024-31580", "id": "pyup.io-72414", "more_info_path": "/vulnerabilities/CVE-2024-31580/72414", "specs": [ "<0.1.1" ], "v": "<0.1.1" } ], "ait-core": [ { "advisory": "NASA AIT-Core v2.5.2 was discovered to use unencrypted channels to exchange data over the network, allowing attackers to execute a man-in-the-middle attack. When chained with CVE-2024-35059, the CVE in subject leads to an unauthenticated, fully remote code execution.", "cve": "CVE-2024-35061", "id": "pyup.io-71906", "more_info_path": "/vulnerabilities/CVE-2024-35061/71906", "specs": [ "<=2.5.2" ], "v": "<=2.5.2" }, { "advisory": "Affected versions of the ait-core package are vulnerable to SQL Injection due to unsanitized inputs in the `query_packets` and `insert` functions. The `query_packets` and `insert` functions accept unvalidated data that is directly incorporated into SQL queries, leading to the injection of malicious SQL statements. A remote attacker can exploit this by supplying crafted packet data to the `query_packets` or crafted payloads to the `insert` function, enabling unauthorized retrieval, modification, or deletion of database records within the ait-core context.", "cve": "CVE-2024-35056", "id": "pyup.io-78723", "more_info_path": "/vulnerabilities/CVE-2024-35056/78723", "specs": [ "<=2.5.2" ], "v": "<=2.5.2" }, { "advisory": "Affected versions of the ait-core package are vulnerable to Remote Code Execution due to the processing of crafted packets without integrity validation. The packet-handling logic in `ait-core` (notably in version 2.5.2) fails to validate or sanitize incoming packet contents, allowing arbitrary code to be executed. An attacker can exploit this by sending a maliciously crafted packet over the adjacent network, causing the ait-core process to execute attacker-controlled code with full privileges and compromising confidentiality, integrity, and availability.", "cve": "CVE-2024-35057", "id": "pyup.io-78724", "more_info_path": "/vulnerabilities/CVE-2024-35057/78724", "specs": [ "<=2.5.2" ], "v": "<=2.5.2" }, { "advisory": "Affected versions of the ait-core package are vulnerable to Remote Code Execution due to unsanitized use of eval in the API wait function. The `wait` function in `ait/core/api.py` accepts string expressions (including Python code) and evaluates them via `eval()` without validation, enabling execution of arbitrary Python code. An attacker can exploit this by supplying a crafted string to the `wait` API, causing the ait-core process to execute attacker-controlled code with the same privileges as the application.", "cve": "CVE-2024-35058", "id": "pyup.io-78721", "more_info_path": "/vulnerabilities/CVE-2024-35058/78721", "specs": [ "<=2.5.2" ], "v": "<=2.5.2" }, { "advisory": "An issue in the Pickle Python library of NASA AIT-Core allows attackers to execute arbitrary commands.", "cve": "CVE-2024-35059", "id": "pyup.io-71243", "more_info_path": "/vulnerabilities/CVE-2024-35059/71243", "specs": [ "<=2.5.2" ], "v": "<=2.5.2" }, { "advisory": "An issue in the YAML Python library of NASA AIT-Core allows attackers to execute arbitrary commands via supplying a crafted YAML file.", "cve": "CVE-2024-35060", "id": "pyup.io-71244", "more_info_path": "/vulnerabilities/CVE-2024-35060/71244", "specs": [ "<=2.5.2" ], "v": "<=2.5.2" } ], "aiutil": [ { "advisory": "Aiutil 0.71.1 includes a fix for an injection vulnerability through password input.\r\nhttps://github.com/legendu-net/aiutil/pull/333/commits/e1d016d329b39b5e799de9c2fcacb2249582863f", "cve": "PVE-2022-52477", "id": "pyup.io-52477", "more_info_path": "/vulnerabilities/PVE-2022-52477/52477", "specs": [ "<0.71.1" ], "v": "<0.71.1" } ], "ajenti": [ { "advisory": "A vulnerability has been found in ajenti 2.1.31 and classified as critical. This vulnerability affects unknown code of the component API. The manipulation leads to privilege escalation. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.1.32 is able to address this issue. The name of the patch is 7aa146b724e0e20cfee2c71ca78fafbf53a8767c. It is recommended to upgrade the affected component.", "cve": "CVE-2019-25066", "id": "pyup.io-65835", "more_info_path": "/vulnerabilities/CVE-2019-25066/65835", "specs": [ "<2.1.37" ], "v": "<2.1.37" }, { "advisory": "ajenticp (aka Ajenti Docker control panel) for Ajenti through v1.2.23.13 has XSS via a filename that is mishandled in File Manager.", "cve": "CVE-2018-18548", "id": "pyup.io-54014", "more_info_path": "/vulnerabilities/CVE-2018-18548/54014", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Cross-site scripting (XSS) vulnerability in plugins/main/content/js/ajenti.coffee in Eugene Pankov Ajenti 1.2.13 allows remote authenticated users to inject arbitrary web script or HTML via the command field in the Cron functionality.", "cve": "CVE-2014-2260", "id": "pyup.io-54081", "more_info_path": "/vulnerabilities/CVE-2014-2260/54081", "specs": [ ">=0,<1.2.14" ], "v": ">=0,<1.2.14" }, { "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in the respond_error function in routing.py in Eugene Pankov Ajenti before 1.2.21.7 allow remote attackers to inject arbitrary web script or HTML via the PATH_INFO to (1) resources.js or (2) resources.css in ajenti:static/, related to the traceback page.", "cve": "CVE-2014-4301", "id": "pyup.io-54083", "more_info_path": "/vulnerabilities/CVE-2014-4301/54083", "specs": [ ">=0,<1.2.21.7" ], "v": ">=0,<1.2.21.7" }, { "advisory": "Versions of the Ajenti server administration panel are exposed to cross-site scripting (XSS) attacks because they fail to validate user input fed into the html() jQuery function. XSS attacks manipulate a web application into accepting a request from what it believes to be a trusted source, leading to the execution of malicious scripts on the client side. These attacks exploit the injection of malicious code into web applications, which, if successful, could result in session hijacking, exposure of sensitive information, unauthorized access to privileged functions, or malware distribution. The primary defense against XSS involves escaping special characters in user inputs, thereby preventing such characters from being interpreted in a harmful context by the browser. To mitigate the risk of XSS attacks, it is recommended to sanitize data input in HTTP requests by validating, filtering, or escaping it before reflecting it back to the user. Additionally, converting special characters to their HTML or URL encoded equivalents, allowing users to disable client-side scripts, redirecting invalid requests, detecting and invalidating simultaneous logins, enforcing a Content Security Policy, and understanding the handling of embedded HTML in utilized libraries are essential practices.", "cve": "PVE-2024-99815", "id": "pyup.io-65963", "more_info_path": "/vulnerabilities/PVE-2024-99815/65963", "specs": [ ">=1.2.20.0,<1.2.22.13" ], "v": ">=1.2.20.0,<1.2.22.13" } ], "ajenti-panel": [ { "advisory": "Ajenti version version 2 contains a Insecure Permissions vulnerability in Plugins download that can result in The download of any plugins as being a normal user. This attack appear to be exploitable via By knowing how the requisition is made, and sending it as a normal user, the server, in response, downloads the plugin.", "cve": "CVE-2018-1000080", "id": "pyup.io-53978", "more_info_path": "/vulnerabilities/CVE-2018-1000080/53978", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Ajenti version version 2 contains a Input Validation vulnerability in ID string on Get-values POST request that can result in Server Crashing. This attack appear to be exploitable via An attacker can freeze te server by sending a giant string to the ID parameter ..", "cve": "CVE-2018-1000081", "id": "pyup.io-53979", "more_info_path": "/vulnerabilities/CVE-2018-1000081/53979", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Ajenti version version 2 contains a Cross ite Request Forgery (CSRF) vulnerability in the command execution panel of the tool used to manage the server. that can result in Code execution on the server . This attack appear to be exploitable via Being a CSRF, victim interaction is needed, when the victim access the infected trigger of the CSRF any code that match the victim privledges on the server can be executed..", "cve": "CVE-2018-1000082", "id": "pyup.io-53980", "more_info_path": "/vulnerabilities/CVE-2018-1000082/53980", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Ajenti version version 2 contains a Improper Error Handling vulnerability in Login JSON request that can result in The requisition leaks a path of the server. This attack appear to be exploitable via By sending a malformed JSON, the tool responds with a traceback error that leaks a path of the server.", "cve": "CVE-2018-1000083", "id": "pyup.io-53981", "more_info_path": "/vulnerabilities/CVE-2018-1000083/53981", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Ajenti version 2 contains an Information Disclosure vulnerability in Line 176 of the code source that can result in user and system enumeration as well as data from the /etc/ajenti/config.yml file. This attack appears to be exploitable via network connectivity to the web application.", "cve": "CVE-2018-1000126", "id": "pyup.io-53982", "more_info_path": "/vulnerabilities/CVE-2018-1000126/53982", "specs": [ ">=0" ], "v": ">=0" } ], "ajsonrpc": [ { "advisory": "Ajsonrpc 1.1.0 ensures server security by having the response manager return a generic ServerError without error details in case of an application exception.", "cve": "PVE-2021-39665", "id": "pyup.io-39665", "more_info_path": "/vulnerabilities/PVE-2021-39665/39665", "specs": [ "<1.1.0" ], "v": "<1.1.0" } ], "aldryn-django": [ { "advisory": "Aldryn-django 1.8.10.1 updates its dependency 'Django' to v1.8.10 to include security fixes.", "cve": "CVE-2016-2512", "id": "pyup.io-25614", "more_info_path": "/vulnerabilities/CVE-2016-2512/25614", "specs": [ "<1.8.10.1" ], "v": "<1.8.10.1" }, { "advisory": "Aldryn-django 1.8.10.1 updates its dependency 'Django' to v1.8.10 to include security fixes.", "cve": "CVE-2016-2513", "id": "pyup.io-49477", "more_info_path": "/vulnerabilities/CVE-2016-2513/49477", "specs": [ "<1.8.10.1" ], "v": "<1.8.10.1" }, { "advisory": "Aldryn-django 1.8.18.1 updates its dependency 'Django' to v1.18.18 to include security fixes.", "cve": "CVE-2017-7234", "id": "pyup.io-49478", "more_info_path": "/vulnerabilities/CVE-2017-7234/49478", "specs": [ "<1.8.18.1" ], "v": "<1.8.18.1" }, { "advisory": "Aldryn-django 1.8.18.1 updates its dependency 'Django' to v1.18.18 to include security fixes.", "cve": "CVE-2017-7233", "id": "pyup.io-34512", "more_info_path": "/vulnerabilities/CVE-2017-7233/34512", "specs": [ "<1.8.18.1" ], "v": "<1.8.18.1" }, { "advisory": "Aldryn-django 3.2.10.0 updates its dependency 'django' to v3.2.10 to include a security fix.", "cve": "CVE-2021-44420", "id": "pyup.io-45170", "more_info_path": "/vulnerabilities/CVE-2021-44420/45170", "specs": [ "<3.2.10.0" ], "v": "<3.2.10.0" }, { "advisory": "Aldryn-django 3.2.11.0 updates its dependency 'django' to v3.2.11 to include security fixes.", "cve": "CVE-2021-45452", "id": "pyup.io-45169", "more_info_path": "/vulnerabilities/CVE-2021-45452/45169", "specs": [ "<3.2.11.0" ], "v": "<3.2.11.0" }, { "advisory": "Aldryn-django 3.2.11.0 updates its dependency 'django' to v3.2.11 to include security fixes.", "cve": "CVE-2021-45116", "id": "pyup.io-45349", "more_info_path": "/vulnerabilities/CVE-2021-45116/45349", "specs": [ "<3.2.11.0" ], "v": "<3.2.11.0" }, { "advisory": "Aldryn-django 3.2.11.0 updates its dependency 'django' to v3.2.11 to include security fixes.", "cve": "CVE-2021-45115", "id": "pyup.io-45350", "more_info_path": "/vulnerabilities/CVE-2021-45115/45350", "specs": [ "<3.2.11.0" ], "v": "<3.2.11.0" }, { "advisory": "Aldryn-django 3.2.12.0 updates its dependency 'django' to v3.2.12 to include security fixes.", "cve": "CVE-2022-22818", "id": "pyup.io-45167", "more_info_path": "/vulnerabilities/CVE-2022-22818/45167", "specs": [ "<3.2.12.0" ], "v": "<3.2.12.0" }, { "advisory": "Aldryn-django 3.2.12.0 updates its dependency 'django' to v3.2.12 to include security fixes.", "cve": "CVE-2022-23833", "id": "pyup.io-45351", "more_info_path": "/vulnerabilities/CVE-2022-23833/45351", "specs": [ "<3.2.12.0" ], "v": "<3.2.12.0" }, { "advisory": "Aldryn-django 3.2.13.0 updates its dependency 'django' to v3.2.13 to include a security fix.", "cve": "CVE-2022-28346", "id": "pyup.io-61624", "more_info_path": "/vulnerabilities/CVE-2022-28346/61624", "specs": [ "<3.2.13.0" ], "v": "<3.2.13.0" }, { "advisory": "Aldryn-django 3.2.13.0 updates its dependency 'django' to v3.2.13 to include a security fix.", "cve": "CVE-2022-28347", "id": "pyup.io-61645", "more_info_path": "/vulnerabilities/CVE-2022-28347/61645", "specs": [ "<3.2.13.0" ], "v": "<3.2.13.0" }, { "advisory": "Aldryn-django 3.2.14.0 updates its dependency 'django' to v3.2.14 to include a security fix.", "cve": "CVE-2022-34265", "id": "pyup.io-61623", "more_info_path": "/vulnerabilities/CVE-2022-34265/61623", "specs": [ "<3.2.14.0" ], "v": "<3.2.14.0" }, { "advisory": "Aldryn-django 3.2.15.0 updates its dependency 'django' to v3.2.15 to include a security fix.", "cve": "CVE-2022-36359", "id": "pyup.io-61622", "more_info_path": "/vulnerabilities/CVE-2022-36359/61622", "specs": [ "<3.2.15.0" ], "v": "<3.2.15.0" }, { "advisory": "Aldryn-django 3.2.16.0 updates its dependency 'django' to v3.2.16 to include a security fix.", "cve": "CVE-2022-41323", "id": "pyup.io-61621", "more_info_path": "/vulnerabilities/CVE-2022-41323/61621", "specs": [ "<3.2.16.0" ], "v": "<3.2.16.0" }, { "advisory": "Aldryn-django 3.2.17.0 updates its dependency 'django' to v3.2.17 to include a security fix.", "cve": "CVE-2023-23969", "id": "pyup.io-61620", "more_info_path": "/vulnerabilities/CVE-2023-23969/61620", "specs": [ "<3.2.17.0" ], "v": "<3.2.17.0" }, { "advisory": "Aldryn-django 3.2.18.0 updates its dependency 'django' to v3.2.18 to include a security fix.", "cve": "CVE-2023-24580", "id": "pyup.io-61619", "more_info_path": "/vulnerabilities/CVE-2023-24580/61619", "specs": [ "<3.2.18.0" ], "v": "<3.2.18.0" }, { "advisory": "Aldryn-django 3.2.4.0 updates its dependency 'django' to v3.2.4 to include security fixes.", "cve": "CVE-2021-33203", "id": "pyup.io-45172", "more_info_path": "/vulnerabilities/CVE-2021-33203/45172", "specs": [ "<3.2.4.0" ], "v": "<3.2.4.0" }, { "advisory": "Aldryn-django 3.2.4.0 updates its dependency 'django' to v3.2.4 to include security fixes.", "cve": "CVE-2021-33571", "id": "pyup.io-45348", "more_info_path": "/vulnerabilities/CVE-2021-33571/45348", "specs": [ "<3.2.4.0" ], "v": "<3.2.4.0" }, { "advisory": "Aldryn-django 3.2.5.0 updates its dependency 'django' to v3.2.5 to include a security fix.", "cve": "CVE-2021-35042", "id": "pyup.io-45171", "more_info_path": "/vulnerabilities/CVE-2021-35042/45171", "specs": [ "<3.2.5.0" ], "v": "<3.2.5.0" }, { "advisory": "Aldryn-django 4.2.1.0 updates its Django dependency to version 4.2.1, addressing the security vulnerability CVE-2023-31047.", "cve": "CVE-2023-31047", "id": "pyup.io-65015", "more_info_path": "/vulnerabilities/CVE-2023-31047/65015", "specs": [ "<4.2.1.0" ], "v": "<4.2.1.0" }, { "advisory": "Aldryn-django 4.2.10.0 upgrades its Django dependency to 4.2.10 due to CVE-2024-24680.", "cve": "CVE-2024-24680", "id": "pyup.io-65010", "more_info_path": "/vulnerabilities/CVE-2024-24680/65010", "specs": [ "<4.2.10.0" ], "v": "<4.2.10.0" }, { "advisory": "The aldryn-django project has upgraded Django to version 4.2.11 to address CVE-2024-27351.", "cve": "CVE-2024-27351", "id": "pyup.io-75008", "more_info_path": "/vulnerabilities/CVE-2024-27351/75008", "specs": [ "<4.2.11.0" ], "v": "<4.2.11.0" }, { "advisory": "Aldryn-django 4.2.3.0 upgrades its Django dependency to 4.2.3 due to CVE-2023-36053.", "cve": "CVE-2023-36053", "id": "pyup.io-65014", "more_info_path": "/vulnerabilities/CVE-2023-36053/65014", "specs": [ "<4.2.3.0" ], "v": "<4.2.3.0" }, { "advisory": "Aldryn-django 4.2.5.0 upgrades its Django dependency to 4.2.5 due to the CVE-2023-41164.", "cve": "CVE-2023-41164", "id": "pyup.io-65013", "more_info_path": "/vulnerabilities/CVE-2023-41164/65013", "specs": [ "<4.2.5.0" ], "v": "<4.2.5.0" }, { "advisory": "Aldryn-django 4.2.6.0 upgrades its Django dependency to 4.2.6 due to the CVE-2023-43665.", "cve": "CVE-2023-43665", "id": "pyup.io-65012", "more_info_path": "/vulnerabilities/CVE-2023-43665/65012", "specs": [ "<4.2.6.0" ], "v": "<4.2.6.0" }, { "advisory": "Aldryn-django 4.2.7.0 upgrades its Django dependency to 4.2.7 due to the CVE-2023-46695.", "cve": "CVE-2023-46695", "id": "pyup.io-65011", "more_info_path": "/vulnerabilities/CVE-2023-46695/65011", "specs": [ "<4.2.7.0" ], "v": "<4.2.7.0" } ], "aleksis-core": [ { "advisory": "An access control issue in aleksis/core/util/auth_helpers.py: ClientProtectedResourceMixin of AlekSIS-Core v2.8.1 and below allows attackers to access arbitrary scopes if no allowed scopes are specifically set.\r\nhttps://edugit.org/AlekSIS/official/AlekSIS-Core/-/issues/688", "cve": "CVE-2022-29773", "id": "pyup.io-54457", "more_info_path": "/vulnerabilities/CVE-2022-29773/54457", "specs": [ ">=0,<2.9" ], "v": ">=0,<2.9" } ], "aleph-message": [ { "advisory": "Aleph-message 0.3.1 updates its dependency ''pydantic' requirement to versions '~=1.10.5' to include a security fix.", "cve": "CVE-2020-10735", "id": "pyup.io-53518", "more_info_path": "/vulnerabilities/CVE-2020-10735/53518", "specs": [ "<0.3.1" ], "v": "<0.3.1" } ], "alerta-server": [ { "advisory": "Affected versions of the `alerta` package are vulnerable to Authentication Bypass due to improper handling of empty passwords during LDAP authentication. The LDAP authentication module fails to enforce password validation, allowing users to authenticate with an empty password if the LDAP server permits unauthenticated binds. An attacker can exploit this vulnerability by providing an empty password during the login process, potentially gaining unauthorized access to the system if the LDAP server is configured to allow anonymous authorization.", "cve": "CVE-2020-26214", "id": "pyup.io-42286", "more_info_path": "/vulnerabilities/CVE-2020-26214/42286", "specs": [ ">=5.2.3,<7.5.7", ">=8.0.0,<8.1.0" ], "v": ">=5.2.3,<7.5.7,>=8.0.0,<8.1.0" }, { "advisory": "Alerta versions between v7.0.0 and v8.7.0 are susceptible to Stored Cross-Site Scripting (XSS) in the field for the full name. Administrative account takeover can occur when an admin navigates to the groups page, triggering the XSS payload and sending the authorization token to the intruder's server.", "cve": "PVE-2023-99968", "id": "pyup.io-60871", "more_info_path": "/vulnerabilities/PVE-2023-99968/60871", "specs": [ ">=7.0.0,<=8.7.0" ], "v": ">=7.0.0,<=8.7.0" } ], "alertwise": [ { "advisory": "Affected versions of Alertwise are potentially vulnerable to brute-force and credential-stuffing attacks due to insufficient login security measures. The issue stems from the lack of rate-limiting, IP tracking, and two-factor authentication in the login process, allowing attackers to attempt logins and potentially compromise user accounts repeatedly.", "cve": "PVE-2025-76095", "id": "pyup.io-76095", "more_info_path": "/vulnerabilities/PVE-2025-76095/76095", "specs": [ "<1.0.3" ], "v": "<1.0.3" } ], "alex-ber-utils": [ { "advisory": "Alex-ber-utils 0.6.3 changes the base docker image version to 0.1.0, because it has a fix for a potential security risk: Git changed to not store credentials as plain text but to keep them in memory for 1 hour.", "cve": "PVE-2021-39148", "id": "pyup.io-39148", "more_info_path": "/vulnerabilities/PVE-2021-39148/39148", "specs": [ "<0.6.3" ], "v": "<0.6.3" } ], "alexandra": [ { "advisory": "Alexandra 0.4.0 updates its dependency 'pyOpenSSL' to v17.5.0 to include security fixes.", "cve": "CVE-2018-1000807", "id": "pyup.io-49031", "more_info_path": "/vulnerabilities/CVE-2018-1000807/49031", "specs": [ "<0.4.0" ], "v": "<0.4.0" }, { "advisory": "Alexandra 0.4.0 updates its dependency 'pyOpenSSL' to v17.5.0 to include security fixes.", "cve": "CVE-2018-1000808", "id": "pyup.io-36552", "more_info_path": "/vulnerabilities/CVE-2018-1000808/36552", "specs": [ "<0.4.0" ], "v": "<0.4.0" } ], "alfred3-interact": [ { "advisory": "Alfred3-interact 0.2.4 fixes a race condition in `MatchMaker._init_member()` which apparently creates a member before its session ID is available in the database.\r\nhttps://github.com/jobrachem/alfred3-interact/commit/0e3c7e964338af72f50066475382c35778888701", "cve": "PVE-2023-62763", "id": "pyup.io-62763", "more_info_path": "/vulnerabilities/PVE-2023-62763/62763", "specs": [ "<0.2.4" ], "v": "<0.2.4" } ], "algokit": [ { "advisory": "Algokit 0.3.0 updates its dependency 'GitPython' to v3.1.30 to include a security fix.", "cve": "CVE-2022-24439", "id": "pyup.io-53440", "more_info_path": "/vulnerabilities/CVE-2022-24439/53440", "specs": [ "<0.3.0" ], "v": "<0.3.0" } ], "algorithm-toolkit": [ { "advisory": "Algorithm-toolkit 0.1.3beta resolves security issues with internal dependencies Pillow and marked.js.", "cve": "PVE-2021-39381", "id": "pyup.io-39381", "more_info_path": "/vulnerabilities/PVE-2021-39381/39381", "specs": [ "<0.1.3beta" ], "v": "<0.1.3beta" } ], "algorithmic": [ { "advisory": "Algorithmic is a malicious package. It triggers the install of W4SP Stealer in your system.", "cve": "PVE-2022-51694", "id": "pyup.io-51694", "more_info_path": "/vulnerabilities/PVE-2022-51694/51694", "specs": [ ">0" ], "v": ">0" } ], "algoseek-connector": [ { "advisory": "Algoseek-connector version 2.1.3 addresses a security vulnerability in the sqlparse library by updating from version \"^0.4.4\" to \"^0.5.0\", in response to the security advisory GHSA-2m57-hf25-phgg.", "cve": "PVE-2024-67887", "id": "pyup.io-67981", "more_info_path": "/vulnerabilities/PVE-2024-67887/67981", "specs": [ "<2.1.3" ], "v": "<2.1.3" } ], "aliyundrive-webdav": [ { "advisory": "An issue in aliyundrive-webdav affected versions allows a remote attacker to execute arbitrary code via a crafted payload to the sid parameter in the action_query_qrcode component.", "cve": "CVE-2024-29640", "id": "pyup.io-71997", "more_info_path": "/vulnerabilities/CVE-2024-29640/71997", "specs": [ "<=2.3.3" ], "v": "<=2.3.3" } ], "allennlp": [ { "advisory": "allennlp 0.6.1 upgrades flask to avoid security vulnerability.", "cve": "PVE-2021-36530", "id": "pyup.io-36530", "more_info_path": "/vulnerabilities/PVE-2021-36530/36530", "specs": [ "<0.6.1" ], "v": "<0.6.1" }, { "advisory": "Allennlp 0.9.0 includes a fix for hotflip attacks.", "cve": "PVE-2021-37901", "id": "pyup.io-37901", "more_info_path": "/vulnerabilities/PVE-2021-37901/37901", "specs": [ "<0.9.0" ], "v": "<0.9.0" } ], "allmydata-tahoe": [ { "advisory": "Allmydata-tahoe 1.1.0 removes 'localdir=/localfile=' and 't=download' operations to avoid security issues.\r\nhttps://github.com/tahoe-lafs/tahoe-lafs/commit/151f69d9b59ee76522c5ae3dad259ded752e8ad4", "cve": "PVE-2021-34432", "id": "pyup.io-34432", "more_info_path": "/vulnerabilities/PVE-2021-34432/34432", "specs": [ "<1.1.0" ], "v": "<1.1.0" }, { "advisory": "Allmydata-tahoe 1.2.0 makes the immutable-file \"ciphertext hash tree\" mandatory. Previous releases allowed the uploader to decide whether their file would have an integrity check on the ciphertext or not. A malicious uploader could use this to create a readcap that would download as one file or a different one, depending upon which shares the client fetched first, with no errors raised. There are other integrity checks on the shares themselves, preventing a storage server or other party from violating the integrity properties of the read-cap: this failure was only exploitable by the uploader who gives you a carefully constructed read-cap.\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/491", "cve": "PVE-2021-34433", "id": "pyup.io-34433", "more_info_path": "/vulnerabilities/PVE-2021-34433/34433", "specs": [ "<1.2.0" ], "v": "<1.2.0" }, { "advisory": "Allmydata-tahoe 1.4.1 fixes a timing attack due to the use of strcmp against the write-enabler and lease-renewal/cancel secrets. An attacker who could measure response-time variations of approximately 3ns against a very noisy background time of about 15ms, might be able to guess these secrets. The attack is believed to be only theoretical feasible.", "cve": "PVE-2021-34435", "id": "pyup.io-34435", "more_info_path": "/vulnerabilities/PVE-2021-34435/34435", "specs": [ "<1.4.1" ], "v": "<1.4.1" }, { "advisory": "Allmydata-tahoe 1.5.0 removes helper access to plaintext hashes.\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/722", "cve": "PVE-2021-34436", "id": "pyup.io-34436", "more_info_path": "/vulnerabilities/PVE-2021-34436/34436", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Allmydata-tahoe 1.7.0 updates its Python version dependency to 2.4.4 to include a fix for a buffer overrun in repr() in cPython.\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/1066", "cve": "CVE-2006-4980", "id": "pyup.io-34437", "more_info_path": "/vulnerabilities/CVE-2006-4980/34437", "specs": [ "<1.7.0" ], "v": "<1.7.0" }, { "advisory": "Allmydata-tahoe 1.7.1 encrypts its temporary files in the FTP frontend, protecting their contents from an attacker who is able to read the disk.", "cve": "PVE-2021-34438", "id": "pyup.io-34438", "more_info_path": "/vulnerabilities/PVE-2021-34438/34438", "specs": [ "<1.7.1" ], "v": "<1.7.1" }, { "advisory": "Allmydata-tahoe 1.8.3 includes a fix for a vulnerability that allowed deletion of shares.", "cve": "PVE-2021-34439", "id": "pyup.io-34439", "more_info_path": "/vulnerabilities/PVE-2021-34439/34439", "specs": [ "<1.8.3" ], "v": "<1.8.3" } ], "alt-model-checkpoint": [ { "advisory": "alt-model-checkpoint 1.0.1 upgrades dependencies, esp. for requests==2.20.0 security patch", "cve": "PVE-2021-36628", "id": "pyup.io-36628", "more_info_path": "/vulnerabilities/PVE-2021-36628/36628", "specs": [ "<1.0.1" ], "v": "<1.0.1" } ], "altair-recipes": [ { "advisory": "Altair-recipes 0.9.2 updates its dependency 'ipython' to v7.31.1 to include a security fix.", "cve": "CVE-2022-21699", "id": "pyup.io-45388", "more_info_path": "/vulnerabilities/CVE-2022-21699/45388", "specs": [ "<0.9.2" ], "v": "<0.9.2" } ], "altcha": [ { "advisory": "Affected versions of the ALTCHA libraries package are vulnerable to Improper Verification of Cryptographic Signature due to ambiguous semantic binding between challenge parameters and the nonce in the HMAC input. The vulnerable HMAC computation signs only the concatenation of the salt value and the nonce without clear delimiting, so a single valid proof-of-work can be reinterpreted as a different challenge payload (including a modified expires value).", "cve": "CVE-2025-68113", "id": "pyup.io-82917", "more_info_path": "/vulnerabilities/CVE-2025-68113/82917", "specs": [ "<1.0.0" ], "v": "<1.0.0" } ], "altvmasterlist": [ { "advisory": "Altvmasterlist version 3.1.0 updates its IDNA dependency from version 3.6 to 3.7 to fix a denial of service vulnerability.", "cve": "CVE-2022-45061", "id": "pyup.io-67623", "more_info_path": "/vulnerabilities/CVE-2022-45061/67623", "specs": [ "<3.1.0" ], "v": "<3.1.0" } ], "alvaro": [ { "advisory": "Alvaro 1.1.1 replaced Pickle with JSON to prevent code injection vulnerabilities.\r\nhttps://github.com/edgecase963/Alvaro/commit/d87c53359e7edde827add46a7870d4192eef0451", "cve": "PVE-2022-50145", "id": "pyup.io-50145", "more_info_path": "/vulnerabilities/PVE-2022-50145/50145", "specs": [ "<1.1.1" ], "v": "<1.1.1" } ], "amazon-braket-default-simulator": [ { "advisory": "Amazon-braket-default-simulator updates pytest version to fix CVE-2022-42969.", "cve": "CVE-2022-42969", "id": "pyup.io-75375", "more_info_path": "/vulnerabilities/CVE-2022-42969/75375", "specs": [ "<1.26.4" ], "v": "<1.26.4" } ], "amazon-product-details-scraper": [ { "advisory": "Amazon-product-details-scraper version 1.0.4 introduces a security update to enhance the validation process for host URLs, mitigating potential vulnerabilities associated with improper URL verification.\r\nhttps://github.com/ranjan-mohanty/amazon-product-details-scraper/pull/10/commits/e8491b1e13b4b9a35f6009d65b7c33d16e3cff10", "cve": "PVE-2024-66905", "id": "pyup.io-66905", "more_info_path": "/vulnerabilities/PVE-2024-66905/66905", "specs": [ "<1.0.4" ], "v": "<1.0.4" } ], "ambient-api": [ { "advisory": "Ambient-api 1.5.2 updates requirements.txt to use urllib3>=1.23 to include a security fix.", "cve": "CVE-2018-20060", "id": "pyup.io-36594", "more_info_path": "/vulnerabilities/CVE-2018-20060/36594", "specs": [ "<1.5.2" ], "v": "<1.5.2" } ], "amd-gaia": [ { "advisory": "Affected versions of this package are vulnerable to Cross-Site Scripting (XSS). The documentation site fails to properly sanitize user input before rendering it, leading to arbitrary JavaScript execution in the victims' browsers that can steal session tokens, credentials, or perform unauthorized actions on behalf of authenticated users.", "cve": "PVE-2026-83963", "id": "pyup.io-83963", "more_info_path": "/vulnerabilities/PVE-2026-83963/83963", "specs": [ "<0.15.0" ], "v": "<0.15.0" } ], "amdsmi": [ { "advisory": "Affected versions of the AMD SMI CLI are vulnerable to potential privilege escalation due to improper handling of root-required operations for process isolation and SRAM data clearing. Attackers could exploit misconfigured permissions to gain unauthorized access or manipulate GPU processes. The vulnerable functions include amdsmi_set_gpu_process_isolation and amdsmi_set_gpu_clear_sram_data. To mitigate, ensure proper configuration of permissions and restrict root access to trusted users only. This vulnerability is specific to systems where these features are enabled without adequate security measures.", "cve": "PVE-2024-73455", "id": "pyup.io-73455", "more_info_path": "/vulnerabilities/PVE-2024-73455/73455", "specs": [ "<6.1.2" ], "v": "<6.1.2" } ], "amici": [ { "advisory": "Affected versions of amici are vulnerable to race conditions (CWE-362) due to the use of shared static variables in multi-threaded contexts. An attacker could exploit this by triggering concurrent executions, leading to data corruption or unexpected behavior. The vulnerability arises from the eval_counter and root_buffer variables in solver.cpp and solver_cvodes.cpp not being thread-safe. This has been addressed by making these variables thread_local, ensuring each thread maintains its own instance and eliminating shared state.", "cve": "PVE-2024-74513", "id": "pyup.io-74513", "more_info_path": "/vulnerabilities/PVE-2024-74513/74513", "specs": [ "<0.29.0" ], "v": "<0.29.0" } ], "aml-ds-pipeline-contrib": [ { "advisory": "Aml-ds-pipeline-contrib is a malicious package, typosquatting. It aims at targeting Azure environments.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick", "cve": "PVE-2022-47809", "id": "pyup.io-47809", "more_info_path": "/vulnerabilities/PVE-2022-47809/47809", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "amodbus": [ { "advisory": "Amodbus 3.6.0 includes a fix for a potential Path Traversal vulnerability.", "cve": "PVE-2025-75724", "id": "pyup.io-75724", "more_info_path": "/vulnerabilities/PVE-2025-75724/75724", "specs": [ "<3.6.0" ], "v": "<3.6.0" } ], "amqp": [ { "advisory": "AMQP versions 0.8 to 0.9.1 (Python client) do not carry out hostname verification during tls connections, paving the way for potential Man-in-the-Middle attacks.", "cve": "PVE-2023-99972", "id": "pyup.io-60836", "more_info_path": "/vulnerabilities/PVE-2023-99972/60836", "specs": [ ">=0.8,<=0.9.1" ], "v": ">=0.8,<=0.9.1" } ], "amqplib": [ { "advisory": "AMQPlib versions 0.8 to 0.9.1 (Python client) do not carry out hostname verification during tls connections, paving the way for potential Man-in-the-Middle attacks.", "cve": "PVE-2023-99972", "id": "pyup.io-60837", "more_info_path": "/vulnerabilities/PVE-2023-99972/60837", "specs": [ ">=0.8,<=0.9.1" ], "v": ">=0.8,<=0.9.1" } ], "amqtt": [ { "advisory": "Amqtt 0.10.0 includes a security fix: If an attacker could produce a KeyError inside an authentication plugin, the authentication was accepted instead of rejected.\r\nhttps://github.com/Yakifo/amqtt/pull/68", "cve": "PVE-2023-53085", "id": "pyup.io-53085", "more_info_path": "/vulnerabilities/PVE-2023-53085/53085", "specs": [ "<0.10.0" ], "v": "<0.10.0" } ], "amsterdam": [ { "advisory": "Amsterdam 1.1 runs the suricata container with lower permissions to increase security.\r\nhttps://github.com/StamusNetworks/Amsterdam/commit/cadf11008a148919cd77da57e1d77c5a2e1092e9", "cve": "PVE-2017-47647", "id": "pyup.io-47647", "more_info_path": "/vulnerabilities/PVE-2017-47647/47647", "specs": [ "<1.1" ], "v": "<1.1" } ], "amundsen-frontend": [ { "advisory": "Amundsen-frontend 3.0.0 updates its dependency 'serialize-javascript' to v3.1.0 to include a security fix.", "cve": "CVE-2020-7660", "id": "pyup.io-39065", "more_info_path": "/vulnerabilities/CVE-2020-7660/39065", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "Amundsen-frontend 3.1.0 includes a security fix: UNEDITABLE_SCHEMAS and UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES not respected by frontend service backend.\r\nhttps://github.com/advisories/GHSA-47qg-q58v-7vrp", "cve": "PVE-2023-55102", "id": "pyup.io-55102", "more_info_path": "/vulnerabilities/PVE-2023-55102/55102", "specs": [ "<3.1.0" ], "v": "<3.1.0" } ], "analytics-zoo": [ { "advisory": "Analytics-zoo 0.11.1 updates its dependency 'log4j' to v2.17.0 to fix critical and severe vulnerabilities.\r\nhttps://github.com/intel-analytics/analytics-zoo/commit/be893d0c173563df923b54578774bd4226d0bbd9", "cve": "CVE-2021-45105", "id": "pyup.io-43746", "more_info_path": "/vulnerabilities/CVE-2021-45105/43746", "specs": [ "<0.11.1" ], "v": "<0.11.1" }, { "advisory": "Analytics-zoo 0.11.1 updates its dependency 'log4j' to v2.17.0 to fix severe vulnerabilities.\r\nhttps://github.com/intel-analytics/analytics-zoo/commit/be893d0c173563df923b54578774bd4226d0bbd9", "cve": "CVE-2021-44228", "id": "pyup.io-43615", "more_info_path": "/vulnerabilities/CVE-2021-44228/43615", "specs": [ "<0.11.1" ], "v": "<0.11.1" }, { "advisory": "Analytics-zoo 0.11.1 updates its dependency 'log4j' to v2.17.0 to fix critical and severe vulnerabilities.\r\nhttps://github.com/intel-analytics/analytics-zoo/commit/be893d0c173563df923b54578774bd4226d0bbd9", "cve": "CVE-2021-45046", "id": "pyup.io-43745", "more_info_path": "/vulnerabilities/CVE-2021-45046/43745", "specs": [ "<0.11.1" ], "v": "<0.11.1" }, { "advisory": "Analytics-zoo 0.11.2 updates its dependency 'log4j' to v2.17.1 to fix a medium severity vulnerability.\r\nhttps://github.com/intel-analytics/analytics-zoo/commit/c75cfc1076adbefa4f5fe0185bff4e7cf3f99b82", "cve": "CVE-2021-44832", "id": "pyup.io-44464", "more_info_path": "/vulnerabilities/CVE-2021-44832/44464", "specs": [ "<0.11.2" ], "v": "<0.11.2" } ], "ananta": [ { "advisory": "Affected versions of Ananta are potentially vulnerable to prefix-truncation Terrapin Attack, allowing man-in-the-middle attackers to manipulate SSH sequence numbers and truncate extension negotiation when using ChaCha20-Poly1305 or AES-CTR encryption modes. The vulnerable code is the algorithm_options[\"encryption_algs\"] list in ananta/ssh.py\u2019s retry_connect, which omits AES-GCM ciphers and falls back to susceptible modes.", "cve": "PVE-2025-77234", "id": "pyup.io-77234", "more_info_path": "/vulnerabilities/PVE-2025-77234/77234", "specs": [ "<1.1.8" ], "v": "<1.1.8" } ], "anaplan-api": [ { "advisory": "Anaplan-api 0.2.13 updates its idna dependency from version 3.6 to 3.7 to address CVE-2024-3651.", "cve": "CVE-2024-3651", "id": "pyup.io-71679", "more_info_path": "/vulnerabilities/CVE-2024-3651/71679", "specs": [ "<0.2.13" ], "v": "<0.2.13" }, { "advisory": "Anaplan-api 0.2.13 updates its cryptography dependency from version 42.0.6 to 42.0.8 to include a security fix for CVE-2024-4603.", "cve": "CVE-2024-4603", "id": "pyup.io-71674", "more_info_path": "/vulnerabilities/CVE-2024-4603/71674", "specs": [ "<0.2.13" ], "v": "<0.2.13" } ], "anchore": [ { "advisory": "In Anchore Engine version 0.7.0, a specially crafted container image manifest, fetched from a registry, can be used to trigger a shell escape flaw in the anchore engine analyzer service during an image analysis process. The image analysis operation can only be executed by an authenticated user via a valid API request to anchore engine, or if an already added image that anchore is monitoring has its manifest altered to exploit the same flaw. A successful attack can be used to execute commands that run in the analyzer environment, with the same permissions as the user that anchore engine is run as - including access to the credentials that Engine uses to access its own database which have read-write ability, as well as access to the running engien analyzer service environment. By default Anchore Engine is released and deployed as a container where the user is non-root, but if users run Engine directly or explicitly set the user to 'root' then that level of access may be gained in the execution environment where Engine runs. This issue is fixed in version 0.7.1.", "cve": "CVE-2020-11075", "id": "pyup.io-62856", "more_info_path": "/vulnerabilities/CVE-2020-11075/62856", "specs": [ "==0.7.0" ], "v": "==0.7.0" } ], "anchorecli": [ { "advisory": "In Anchore Engine version 0.7.0, a specially crafted container image manifest, fetched from a registry, can be used to trigger a shell escape flaw in the anchore engine analyzer service during an image analysis process. The image analysis operation can only be executed by an authenticated user via a valid API request to anchore engine, or if an already added image that anchore is monitoring has its manifest altered to exploit the same flaw. A successful attack can be used to execute commands that run in the analyzer environment, with the same permissions as the user that anchore engine is run as - including access to the credentials that Engine uses to access its own database which have read-write ability, as well as access to the running engien analyzer service environment. By default Anchore Engine is released and deployed as a container where the user is non-root, but if users run Engine directly or explicitly set the user to 'root' then that level of access may be gained in the execution environment where Engine runs. This issue is fixed in version 0.7.1.", "cve": "CVE-2020-11075", "id": "pyup.io-62857", "more_info_path": "/vulnerabilities/CVE-2020-11075/62857", "specs": [ "==0.7.0" ], "v": "==0.7.0" } ], "anchorpy": [ { "advisory": "Anchorpy 0.6.4 updates its dependency 'ipython' to v8.0.1 to include a security fix.", "cve": "CVE-2022-21699", "id": "pyup.io-44648", "more_info_path": "/vulnerabilities/CVE-2022-21699/44648", "specs": [ "<0.6.4" ], "v": "<0.6.4" } ], "anki": [ { "advisory": "Anki version 24.06 includes security fixes for handling shared decks. Users who download and use shared decks from untrusted authors are recommended to update to the latest version to enhance security and protect against potential vulnerabilities.", "cve": "PVE-2024-71393", "id": "pyup.io-71393", "more_info_path": "/vulnerabilities/PVE-2024-71393/71393", "specs": [ "<24.06" ], "v": "<24.06" }, { "advisory": "Affected versions of the Anki package are vulnerable to Code Injection due to improper handling of MPV functionality in flashcards. The MPV component processes user-supplied flashcard content without sufficient sanitization, enabling crafted inputs to execute arbitrary scripts. An attacker can exploit this by distributing a specially crafted flashcard to a user\u2014which the Anki application renders via MPV\u2014resulting in arbitrary code execution within the user's context, potentially leading to full system compromise.", "cve": "CVE-2024-26020", "id": "pyup.io-78749", "more_info_path": "/vulnerabilities/CVE-2024-26020/78749", "specs": [ "<24.06" ], "v": "<24.06" }, { "advisory": "Affected versions of the Anki package are vulnerable to Arbitrary File Creation due to a LaTeX blocklist bypass in the LaTeX processing functionality. The LaTeX module in Anki (\u2264 24.04) fails to enforce its blocklist properly, allowing specially crafted malicious flashcards to create arbitrary files at a fixed path. An attacker can exploit this by sharing a malicious flashcard that, when imported or rendered by Anki, creates files at predetermined locations on the user\u2019s system, potentially enabling further unwanted actions such as remote code execution.", "cve": "CVE-2024-32152", "id": "pyup.io-78753", "more_info_path": "/vulnerabilities/CVE-2024-32152/78753", "specs": [ "<24.6" ], "v": "<24.6" }, { "advisory": "Affected versions of the Anki package are vulnerable to Arbitrary File Read due to incomplete LaTeX sanitization that fails to block the `verbatim` package. The Latex handling module overlooks the `verbatim` package during sanitization, allowing specially crafted flashcards to include commands that read arbitrary files. An attacker can exploit this by sharing a malicious flashcard, which, when rendered by Anki 24.04, causes the application to read files on the user\u2019s system, potentially exposing sensitive local data.", "cve": "CVE-2024-29073", "id": "pyup.io-78755", "more_info_path": "/vulnerabilities/CVE-2024-29073/78755", "specs": [ "<24.6" ], "v": "<24.6" }, { "advisory": "Anki 24.6.1 includes a security fix for the handling of shared decks, specially important for users who make use of shared decks from untrusted authors.", "cve": "PVE-2024-71422", "id": "pyup.io-71422", "more_info_path": "/vulnerabilities/PVE-2024-71422/71422", "specs": [ "<24.6.1" ], "v": "<24.6.1" }, { "advisory": "Anki's integration with the mpv media player did not disable the use of youtube-dl (or its fork yt-dlp) by default. On Windows systems, mpv searches for yt-dlp.exe in the system's PATH, which includes the current working directory. This behaviour allowed a malicious shared deck to include a yt-dlp.exe executable in its media folder. When a user opened such a deck and attempted to play a YouTube link, mpv could inadvertently execute the malicious yt-dlp.exe, leading to arbitrary code execution.\r\n#NOTE: This vulnerability is specific to Windows operating systems due to the inclusion of the current working directory in the system PATH.", "cve": "PVE-2025-77281", "id": "pyup.io-77281", "more_info_path": "/vulnerabilities/PVE-2025-77281/77281", "specs": [ "<25.02.5" ], "v": "<25.02.5" } ], "annotator": [ { "advisory": "Annotator 0.11.2 fixes a bug that allowed authenticated users to overwrite annotations on which they did not have permissions.\r\nhttps://github.com/openannotation/annotator-store/issues/82", "cve": "PVE-2021-25615", "id": "pyup.io-25615", "more_info_path": "/vulnerabilities/PVE-2021-25615/25615", "specs": [ "<0.11.2" ], "v": "<0.11.2" } ], "anomalib": [ { "advisory": "Anomalib 0.5.0 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.", "cve": "CVE-2007-4559", "id": "pyup.io-58628", "more_info_path": "/vulnerabilities/CVE-2007-4559/58628", "specs": [ "<0.5.0" ], "v": "<0.5.0" } ], "ansible": [ { "advisory": "Ansible 1.2.1 includes a fix for CVE-2013-2233: Ansible before 1.2.1 makes it easier for remote attackers to conduct man-in-the-middle attacks by leveraging failure to cache SSH host keys.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=980821", "cve": "CVE-2013-2233", "id": "pyup.io-42921", "more_info_path": "/vulnerabilities/CVE-2013-2233/42921", "specs": [ "<1.2.1" ], "v": "<1.2.1" }, { "advisory": "Ansible 1.2.3 includes a fix for CVE-2013-4259: runner/connection_plugins/ssh.py in Ansible before 1.2.3, when using ControlPersist, allows local users to redirect a ssh session via a symlink attack on a socket file with a predictable name in /tmp/.", "cve": "CVE-2013-4259", "id": "pyup.io-42920", "more_info_path": "/vulnerabilities/CVE-2013-4259/42920", "specs": [ "<1.2.3" ], "v": "<1.2.3" }, { "advisory": "Ansible 1.2.3 includes local security fixes for predictable file locations for ControlPersist and retry file paths on shared machines on operating systems without kernel symlink/hardlink protections. See CVE-2013-4260.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=998227", "cve": "CVE-2013-4260", "id": "pyup.io-25616", "more_info_path": "/vulnerabilities/CVE-2013-4260/25616", "specs": [ "<1.2.3" ], "v": "<1.2.3" }, { "advisory": "Ansible 1.5.4 includes a fix for CVE-2014-2686: Ansible prior to 1.5.4 mishandles the evaluation of some strings.\r\nhttps://groups.google.com/forum/#!searchin/ansible-project/1.5.4/ansible-project/MUQxiKwSQDc/id6aVaawVboJ", "cve": "CVE-2014-2686", "id": "pyup.io-42919", "more_info_path": "/vulnerabilities/CVE-2014-2686/42919", "specs": [ "<1.5.4" ], "v": "<1.5.4" }, { "advisory": "Ansible 1.5.5 includes a fix for CVE-2014-4658: The vault subsystem in Ansible before 1.5.5 does not set the umask before creation or modification of a vault file, which allows local users to obtain sensitive key information by reading a file.", "cve": "CVE-2014-4658", "id": "pyup.io-25618", "more_info_path": "/vulnerabilities/CVE-2014-4658/25618", "specs": [ "<1.5.5" ], "v": "<1.5.5" }, { "advisory": "Ansible 1.5.5 includes a fix for CVE-2014-4659: Ansible before 1.5.5 sets 0644 permissions for sources.list, which might allow local users to obtain sensitive credential information in opportunistic circumstances by reading a file that uses the \"deb http://user:pass@server:port/\" format.", "cve": "CVE-2014-4659", "id": "pyup.io-42854", "more_info_path": "/vulnerabilities/CVE-2014-4659/42854", "specs": [ "<1.5.5" ], "v": "<1.5.5" }, { "advisory": "Ansible 1.5.5 includes a fix for CVE-2014-4660: Ansible before 1.5.5 constructs filenames containing user and password fields on the basis of deb lines in sources.list, which might allow local users to obtain sensitive credential information in opportunistic circumstances by leveraging existence of a file that uses the \"deb http://user:pass@server:port/\" format.\r\nhttps://www.openwall.com/lists/oss-security/2014/06/26/19", "cve": "CVE-2014-4660", "id": "pyup.io-42918", "more_info_path": "/vulnerabilities/CVE-2014-4660/42918", "specs": [ "<1.5.5" ], "v": "<1.5.5" }, { "advisory": "Ansible 1.6.4 includes a fix for CVE-2014-4678: The safe_eval function in Ansible before 1.6.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrary code via crafted instructions. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-4657.", "cve": "CVE-2014-4678", "id": "pyup.io-25619", "more_info_path": "/vulnerabilities/CVE-2014-4678/25619", "specs": [ "<1.6.4" ], "v": "<1.6.4" }, { "advisory": "Ansible 1.6.6 includes a fix for CVE-2014-3498: The user module in ansible before 1.6.6 allows remote authenticated users to execute arbitrary commands.", "cve": "CVE-2014-3498", "id": "pyup.io-25620", "more_info_path": "/vulnerabilities/CVE-2014-3498/25620", "specs": [ "<1.6.6" ], "v": "<1.6.6" }, { "advisory": "Ansible before 1.6.7 does not prevent inventory data with \"{{\" and \"lookup\" substrings, and does not prevent remote data with \"{{\" substrings, which allows remote attackers to execute arbitrary code via (1) crafted lookup('pipe') calls or (2) crafted Jinja2 data.", "cve": "CVE-2014-4966", "id": "pyup.io-42334", "more_info_path": "/vulnerabilities/CVE-2014-4966/42334", "specs": [ "<1.6.7" ], "v": "<1.6.7" }, { "advisory": "ansible 1.6.7 contains two security fixes:\r\n * Strip lookup calls out of inventory variables and clean unsafe data\r\n returned from lookup plugins (CVE-2014-4966)\r\n * Make sure vars don't insert extra parameters into module args and prevent\r\n duplicate params from superseding previous params (CVE-2014-4967)", "cve": "CVE-2014-4967", "id": "pyup.io-25621", "more_info_path": "/vulnerabilities/CVE-2014-4967/25621", "specs": [ "<1.6.7" ], "v": "<1.6.7" }, { "advisory": "Ansible 1.7.0 adds path checking for relative/escaped tar filenames in the ansible-galaxy command.", "cve": "PVE-2021-25622", "id": "pyup.io-25622", "more_info_path": "/vulnerabilities/PVE-2021-25622/25622", "specs": [ "<1.7" ], "v": "<1.7" }, { "advisory": "Ansible 1.7.0 avoids templating raw lookup strings.", "cve": "PVE-2022-45329", "id": "pyup.io-45329", "more_info_path": "/vulnerabilities/PVE-2022-45329/45329", "specs": [ "<1.7" ], "v": "<1.7" }, { "advisory": "ansible 1.7.1 contains a security fix to disallow specifying 'args:' as a string, which could allow the insertion of extra module parameters through variables.", "cve": "PVE-2021-25623", "id": "pyup.io-25623", "more_info_path": "/vulnerabilities/PVE-2021-25623/25623", "specs": [ "<1.7.1" ], "v": "<1.7.1" }, { "advisory": "ansible 1.8.3 fixes a security bug related to the default permissions set on a temporary file created when using \"ansible-vault view \".", "cve": "PVE-2021-25624", "id": "pyup.io-25624", "more_info_path": "/vulnerabilities/PVE-2021-25624/25624", "specs": [ "<1.8.3" ], "v": "<1.8.3" }, { "advisory": "Ansible 1.9.2 includes a fix for CVE-2015-6240: The chroot, jail, and zone connection plugins in Ansible before 1.9.2 allow local users to escape a restricted environment via a symlink attack.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1243468", "cve": "CVE-2015-6240", "id": "pyup.io-42917", "more_info_path": "/vulnerabilities/CVE-2015-6240/42917", "specs": [ "<1.9.2" ], "v": "<1.9.2" }, { "advisory": "Ansible before 1.9.2 does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.", "cve": "CVE-2015-3908", "id": "pyup.io-25625", "more_info_path": "/vulnerabilities/CVE-2015-3908/25625", "specs": [ "<1.9.2" ], "v": "<1.9.2" }, { "advisory": "Affected versions of the Ansible package are vulnerable to Information Disclosure due to improper redaction of sensitive credential fields in verbose log output. The community.general.keycloak_user module logs the credentials[].value parameter in plaintext when Ansible is executed with high verbosity (for example, -vvv), because this field is not marked with the no_log protection that is applied to other password parameters such as auth_password.", "cve": "CVE-2025-14010", "id": "pyup.io-82327", "more_info_path": "/vulnerabilities/CVE-2025-14010/82327", "specs": [ "<12.2.0" ], "v": "<12.2.0" }, { "advisory": "Ansible versions 2.1.4 and 2.2.1 include a fix for CVE-2016-9587: Ansible before versions 2.1.4, 2.2.1 is vulnerable to an improper input validation in Ansible's handling of data sent from client systems. An attacker with control over a client system being managed by Ansible and the ability to send facts back to the Ansible server could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges.\r\nhttps://www.exploit-db.com/exploits/41013/", "cve": "CVE-2016-9587", "id": "pyup.io-33285", "more_info_path": "/vulnerabilities/CVE-2016-9587/33285", "specs": [ "<2.1.4", ">=2.2.0,<2.2.1" ], "v": "<2.1.4,>=2.2.0,<2.2.1" }, { "advisory": "A flaw was found in Ansible Base when using the aws_ssm connection plugin as there is no namespace separation for file transfers. Files are written directly to the root bucket, making possible to have collisions when running multiple ansible processes. This issue affects mainly the service availability. This CVE affects community.aws before 1.2.1 and Ansible-build-data ships this dependency on versions before 2.10.5.", "cve": "CVE-2020-25636", "id": "pyup.io-54229", "more_info_path": "/vulnerabilities/CVE-2020-25636/54229", "specs": [ "<2.10.5" ], "v": "<2.10.5" }, { "advisory": "A flaw was found in Ansible Base when using the aws_ssm connection plugin as garbage collector is not happening after playbook run is completed. Files would remain in the bucket exposing the data. This issue affects directly data confidentiality. This CVE affects community.aws before 1.2.1 and Ansible-build-data ships this dependency on versions before 2.10.5.", "cve": "CVE-2020-25635", "id": "pyup.io-54230", "more_info_path": "/vulnerabilities/CVE-2020-25635/54230", "specs": [ "<2.10.5" ], "v": "<2.10.5" }, { "advisory": "Ansible 2.2.0 includes a fix for CVE-2016-8628: Ansible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller. An attacker with the ability to create special variables on the controller could execute arbitrary commands on Ansible clients as the user Ansible runs as.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8628", "cve": "CVE-2016-8628", "id": "pyup.io-42915", "more_info_path": "/vulnerabilities/CVE-2016-8628/42915", "specs": [ "<2.2.0" ], "v": "<2.2.0" }, { "advisory": "Ansible 2.3 includes a fix for CVE-2017-7466: Ansible before version 2.3 has an input validation vulnerability in the handling of data sent from client systems. An attacker with control over a client system being managed by Ansible, and the ability to send facts back to the Ansible server, could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7466", "cve": "CVE-2017-7466", "id": "pyup.io-42890", "more_info_path": "/vulnerabilities/CVE-2017-7466/42890", "specs": [ "<2.3" ], "v": "<2.3" }, { "advisory": "Ansible before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated. See: CVE-2017-7481.", "cve": "CVE-2017-7481", "id": "pyup.io-34941", "more_info_path": "/vulnerabilities/CVE-2017-7481/34941", "specs": [ "<2.3.1" ], "v": "<2.3.1" }, { "advisory": "Ansible 2.5.14, 2.6.11 and 2.7.5 include a fix for CVE-2018-16876: Ansible before versions 2.5.14, 2.6.11, 2.7.5 is vulnerable to a information disclosure flaw in vvv+ mode with no_log on that can lead to leakage of sensible data.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16876", "cve": "CVE-2018-16876", "id": "pyup.io-42889", "more_info_path": "/vulnerabilities/CVE-2018-16876/42889", "specs": [ "<2.5.14", ">=2.6.0a0,<2.6.11", ">=2.7.0a0,<2.7.5" ], "v": "<2.5.14,>=2.6.0a0,<2.6.11,>=2.7.0a0,<2.7.5" }, { "advisory": "Ansible versions 2.7.17, 2.8.11 and 2.9.7 include a fix for CVE-2020-1733: A race condition flaw was found in Ansible Engine when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is created in /var/tmp. This directory is created with \"umask 77 && mkdir -p \"; this operation does not fail if the directory already exists and is owned by another user. An attacker could take advantage to gain control of the become user as the target directory can be retrieved by iterating '/proc//cmdline'.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1733", "cve": "CVE-2020-1733", "id": "pyup.io-42879", "more_info_path": "/vulnerabilities/CVE-2020-1733/42879", "specs": [ "<2.7.17", ">=2.8.0a0,<2.8.11", ">=2.9.0a0,<2.9.7" ], "v": "<2.7.17,>=2.8.0a0,<2.8.11,>=2.9.0a0,<2.9.7" }, { "advisory": "Ansible versions 2.7.17, 2.8.9 and 2.9.6 include a fix for CVE-2020-1739: A flaw was found in Ansible 2.7.16 and prior, 2.8.8 and prior, and 2.9.5 and prior. When a password is set with the argument \"password\" of svn module, it is used on svn command line, disclosing to other users within the same node. An attacker could take advantage by reading the cmdline file from that particular PID on the procfs.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1739", "cve": "CVE-2020-1739", "id": "pyup.io-42871", "more_info_path": "/vulnerabilities/CVE-2020-1739/42871", "specs": [ "<2.7.17", ">=2.8.0a0,<2.8.9", ">=2.9.0a0,<2.9.6" ], "v": "<2.7.17,>=2.8.0a0,<2.8.9,>=2.9.0a0,<2.9.6" }, { "advisory": "Ansible versions 2.7.17, 2.8.9 and 2.9.6 include a fix for CVE-2020-1735: A flaw was found in the Ansible Engine when the fetch module is used. An attacker could intercept the module, inject a new path, and then choose a new destination path on the controller node. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1735", "cve": "CVE-2020-1735", "id": "pyup.io-42877", "more_info_path": "/vulnerabilities/CVE-2020-1735/42877", "specs": [ "<2.7.17", ">=2.8.0a0,<2.8.9", ">=2.9.0a0,<2.9.6" ], "v": "<2.7.17,>=2.8.0a0,<2.8.9,>=2.9.0a0,<2.9.6" }, { "advisory": "A flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3 or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot and the decryp emains when the host is switched off. The system will be vulnerable when the system is not running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted ble.", "cve": "CVE-2020-10685", "id": "pyup.io-54331", "more_info_path": "/vulnerabilities/CVE-2020-10685/54331", "specs": [ "<2.7.17", ">=2.8.0a1,<2.8.11", ">=2.9.0b1,<2.9.7" ], "v": "<2.7.17,>=2.8.0a1,<2.8.11,>=2.9.0b1,<2.9.7" }, { "advisory": "A flaw was found in the Ansible Engine, in ansible-engine affected versions, when installing packages using the dnf module. GPG signatures are ignored during installation even when disable_gpg_check is set to False, the default behaviour. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability.", "cve": "CVE-2020-14365", "id": "pyup.io-54224", "more_info_path": "/vulnerabilities/CVE-2020-14365/54224", "specs": [ "<2.8.15", ">=2.9.0b1,<2.9.13" ], "v": "<2.8.15,>=2.9.0b1,<2.9.13" }, { "advisory": "Ansible 2.9.18 includes a fix for CVE-2021-20178: A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1914774", "cve": "CVE-2021-20178", "id": "pyup.io-42858", "more_info_path": "/vulnerabilities/CVE-2021-20178/42858", "specs": [ "<2.9.18" ], "v": "<2.9.18" }, { "advisory": "An input validation vulnerability was found in Ansible's mysql_user module before 2.2.1.0, which may fail to correctly change a password in certain circumstances. Thus the previous password would still be active when it should have been changed.", "cve": "CVE-2016-8647", "id": "pyup.io-54118", "more_info_path": "/vulnerabilities/CVE-2016-8647/54118", "specs": [ ">=0,<2.2.1.0" ], "v": ">=0,<2.2.1.0" }, { "advisory": "Ansible \"User\" module leaks any data which is passed on as a parameter to ssh-keygen. This could lean in undesirable situations such as passphrases credentials passed as a parameter for the ssh-keygen executable. Showing those credentials in clear text form for every user which have access just to the process list.", "cve": "CVE-2018-16837", "id": "pyup.io-54010", "more_info_path": "/vulnerabilities/CVE-2018-16837/54010", "specs": [ ">=0,<2.5.11", ">=2.6.0a1,<2.6.9", ">=2.7.0.dev0,<2.7.1" ], "v": ">=0,<2.5.11,>=2.6.0a1,<2.6.9,>=2.7.0.dev0,<2.7.1" }, { "advisory": "In Ansible, all Ansible Engine versions up to ansible-engine 2.8.5, ansible-engine 2.7.13, ansible-engine 2.6.19, were logging at the DEBUG level which lead to a disclosure of credentials if a plugin used a library that logged credentials at the DEBUG level. This flaw does not affect Ansible modules, as those are executed in a separate process.", "cve": "CVE-2019-14846", "id": "pyup.io-54288", "more_info_path": "/vulnerabilities/CVE-2019-14846/54288", "specs": [ ">=0,<2.6.20", ">=2.7.0a0,<2.7.14", ">=2.8.0a0,<2.8.6" ], "v": ">=0,<2.6.20,>=2.7.0a0,<2.7.14,>=2.8.0a0,<2.8.6" }, { "advisory": "A flaw was found in the pipe lookup plugin of ansible. Arbitrary commands can be run, when the pipe lookup plugin uses subprocess.Popen() with shell=True, by overwriting ansible facts and the variable is not escaped by quote plugin. An attacker could take advantage and run arbitrary commands by overwriting the ansible facts.", "cve": "CVE-2020-1734", "id": "pyup.io-54189", "more_info_path": "/vulnerabilities/CVE-2020-1734/54189", "specs": [ ">=0,<2.7.17" ], "v": ">=0,<2.7.17" }, { "advisory": "A flaw was found in the Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when the ldap_attr and ldap_entry community modules are used. The issue discloses the LDAP bind password to stdout or a log file if a playbook task is written using the bind_pw in the parameters field. The highest threat from this vulnerability is data confidentiality.", "cve": "CVE-2020-1746", "id": "pyup.io-54284", "more_info_path": "/vulnerabilities/CVE-2020-1746/54284", "specs": [ ">=0,<2.7.17", ">=2.8.0a0,<2.8.11", ">=2.9.0b1,<2.9.7" ], "v": ">=0,<2.7.17,>=2.8.0a0,<2.8.11,>=2.9.0b1,<2.9.7" }, { "advisory": "A flaw was found in Ansible 2.7.17 and prior, 2.8.9 and prior, and 2.9.6 and prior when using the Extract-Zip function from the win_unzip module as the extracted file(s) are not checked if they belong to the destination folder. An attacker could take advantage of this flaw by crafting an archive anywhere in the file system, using a path traversal. This issue is fixed in 2.10.", "cve": "CVE-2020-1737", "id": "pyup.io-54191", "more_info_path": "/vulnerabilities/CVE-2020-1737/54191", "specs": [ ">=0,<2.7.17", ">=2.8.0a0,<2.8.9", ">=2.9.0b1,<2.9.6" ], "v": ">=0,<2.7.17,>=2.8.0a0,<2.8.9,>=2.9.0b1,<2.9.6" }, { "advisory": "A security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.11 and all Ansible 2.9.x versions prior to 2.9.7, when managing kubernetes using the k8s module. Sensitive parameters such as passwords and tokens are passed to kubectl from the command line, not using an environment variable or an input configuration file. This will disclose passwords and tokens from process list and no_log directive from debug module would not have any effect making these secrets being disclosed on stdout and log files.", "cve": "CVE-2020-1753", "id": "pyup.io-54240", "more_info_path": "/vulnerabilities/CVE-2020-1753/54240", "specs": [ ">=0,<2.7.18", ">=2.8.0a0,<2.8.11", ">=2.9.0b1,<2.9.7" ], "v": ">=0,<2.7.18,>=2.8.0a0,<2.8.11,>=2.9.0b1,<2.9.7" }, { "advisory": "A flaw was found in the Ansible Engine when using module_args. Tasks executed with check mode (--check-mode) do not properly neutralize sensitive data exposed in the event data. This flaw allows unauthorized users to read this data. The highest threat from this vulnerability is to confidentiality.", "cve": "CVE-2020-14332", "id": "pyup.io-54226", "more_info_path": "/vulnerabilities/CVE-2020-14332/54226", "specs": [ ">=0,<2.8.14", ">=2.9.0b1,<2.9.12" ], "v": ">=0,<2.8.14,>=2.9.0b1,<2.9.12" }, { "advisory": "A flaw was found in the use of insufficiently random values in Ansible. Two random password lookups of the same length generate the equal value as the template caching action for the same file since no re-evaluation happens. The highest threat from this vulnerability would be that all passwords are exposed at once for the file. This flaw affects Ansible Engine versions before 2.9.6.", "cve": "CVE-2020-10729", "id": "pyup.io-54283", "more_info_path": "/vulnerabilities/CVE-2020-10729/54283", "specs": [ ">=0,<2.9.6" ], "v": ">=0,<2.9.6" }, { "advisory": "Ansible 1.5.4 includes a fix for CVE-2014-4657: The safe_eval function in Ansible before 1.5.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrary code via crafted instructions.", "cve": "CVE-2014-4657", "id": "pyup.io-25617", "more_info_path": "/vulnerabilities/CVE-2014-4657/25617", "specs": [ ">=1.2,<1.5.4" ], "v": ">=1.2,<1.5.4" }, { "advisory": "Ansible 1.9.6 and 2.0.2 include a fix for CVE-2016-3096: The create_script function in the lxc_container module in Ansible before 1.9.6-1 and 2.x before 2.0.2.0 allows local users to write to arbitrary files or gain privileges via a symlink attack on (1) /opt/.lxc-attach-script, (2) the archived container in the archive_path directory, or the (3) lxc-attach-script.log or (4) lxc-attach-script.err files in the temporary directory.", "cve": "CVE-2016-3096", "id": "pyup.io-25627", "more_info_path": "/vulnerabilities/CVE-2016-3096/25627", "specs": [ ">=2.0.0.0,<2.0.2", "<1.9.6" ], "v": ">=2.0.0.0,<2.0.2,<1.9.6" }, { "advisory": "Ansible 2.1.0.0 include a security fix: Information disclosure of sensitive data in log files.", "cve": "PVE-2023-99974", "id": "pyup.io-60834", "more_info_path": "/vulnerabilities/PVE-2023-99974/60834", "specs": [ ">=2.0.0.0,<2.1.0.0" ], "v": ">=2.0.0.0,<2.1.0.0" }, { "advisory": "A vulnerability was found in Ansible engine and Ansible tower. When a module has an argument_spec with sub parameters marked as no_log, passing an invalid parameter name to the module will cause the task to fail before the no_log options in the sub parameters are processed. As a result, data in the sub parameter fields will not be masked and will be displayed if Ansible is run with increased verbosity and present in the module invocation arguments for the task.", "cve": "CVE-2019-14858", "id": "pyup.io-54153", "more_info_path": "/vulnerabilities/CVE-2019-14858/54153", "specs": [ ">=2.10.0a1,<2.10.0b1", ">=2.9.0b1,<2.9.0", ">=2.8.0a1,<2.8.6", ">=2.7.0.dev0,<2.7.14", "<2.6.20" ], "v": ">=2.10.0a1,<2.10.0b1,>=2.9.0b1,<2.9.0,>=2.8.0a1,<2.8.6,>=2.7.0.dev0,<2.7.14,<2.6.20" }, { "advisory": "A flaw was found in the Ansible Engine 2.9.18, where sensitive info is not masked by default and is not protected by the no_log feature when using the sub-option feature of the basic.py module. This flaw allows an attacker to obtain sensitive information. The highest threat from this vulnerability is to confidentiality.", "cve": "CVE-2021-20228", "id": "pyup.io-54286", "more_info_path": "/vulnerabilities/CVE-2021-20228/54286", "specs": [ ">=2.10.0a1,<2.10.7", ">=2.9.0b1,<2.9.18", ">=0,<2.8.19" ], "v": ">=2.10.0a1,<2.10.7,>=2.9.0b1,<2.9.18,>=0,<2.8.19" }, { "advisory": "Affected versions of the `ansible` package are vulnerable to Improper Output Neutralization for Logs due to insufficient sanitization of sensitive data in log outputs. The vulnerability exists in the `uri` module, where sensitive information such as keys can be inadvertently logged in both content and JSON outputs. An attacker can exploit this vulnerability by accessing the logs to obtain sensitive data, compromising the confidentiality of playbooks and potentially exposing private keys used by other users.", "cve": "CVE-2020-14330", "id": "pyup.io-54219", "more_info_path": "/vulnerabilities/CVE-2020-14330/54219", "specs": [ ">=2.4.0.0,<2.10.0" ], "v": ">=2.4.0.0,<2.10.0" }, { "advisory": "Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.", "cve": "CVE-2018-10855", "id": "pyup.io-54290", "more_info_path": "/vulnerabilities/CVE-2018-10855/54290", "specs": [ ">=2.5.0a1,<2.5.5", ">=2.4.0,<2.4.5" ], "v": ">=2.5.0a1,<2.5.5,>=2.4.0,<2.4.5" }, { "advisory": "A flaw was found in Ansible in the amazon.aws collection when using the `tower_callback` parameter from the `amazon.aws.ec2_instance` module. This flaw allows an attacker to take advantage of this issue as the module is handling the parameter insecurely, leading to the password leaking in the logs.", "cve": "CVE-2022-3697", "id": "pyup.io-54564", "more_info_path": "/vulnerabilities/CVE-2022-3697/54564", "specs": [ ">=2.5.0a1,<7.0.0" ], "v": ">=2.5.0a1,<7.0.0" }, { "advisory": "A flaw was found in ansible. ansible.cfg is read from the current working directory which can be altered to make it point to a plugin or a module path under the control of an attacker, thus allowing the attacker to execute arbitrary code.", "cve": "CVE-2018-10875", "id": "pyup.io-54289", "more_info_path": "/vulnerabilities/CVE-2018-10875/54289", "specs": [ ">=2.5a1,<2.5.6", ">=2.6a1,<2.6.1", "<2.4.6.0" ], "v": ">=2.5a1,<2.5.6,>=2.6a1,<2.6.1,<2.4.6.0" }, { "advisory": "Ansible 2.5.15, 2.6.14 and 2.7.8 include a fix for CVE-2019-3828: Ansible fetch module before versions 2.5.15, 2.6.14, 2.7.8 has a path traversal vulnerability which allows copying and overwriting files outside of the specified destination in the local Ansible controller host by not restricting an absolute path.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3828\r\nhttps://github.com/ansible/ansible/pull/52133", "cve": "CVE-2019-3828", "id": "pyup.io-42888", "more_info_path": "/vulnerabilities/CVE-2019-3828/42888", "specs": [ ">=2.6.0a0,<2.6.14", ">=2.7.0a0,<2.7.8", "<2.5.15" ], "v": ">=2.6.0a0,<2.6.14,>=2.7.0a0,<2.7.8,<2.5.15" }, { "advisory": "Affected versions of Ansible are vulnerable to CVE-2019-14856: The fix for CVE-2019-10206 was found to be incomplete for the data disclosure flaw in Ansible. Password prompts in ansible-playbook and ansible-cli tools could expose passwords with special characters as they are not properly wrapped. A password with special characters is exposed starting with the first of these special characters. The highest threat from this vulnerability is to data confidentiality.", "cve": "CVE-2019-14856", "id": "pyup.io-42884", "more_info_path": "/vulnerabilities/CVE-2019-14856/42884", "specs": [ ">=2.6.0a0,<2.6.20", ">=2.7.0a0,<2.7.14", ">=2.8.0a0,<2.8.6", ">=2.10.0a1,<2.10.0b1", ">=2.9.0b1,<2.9.0rc4" ], "v": ">=2.6.0a0,<2.6.20,>=2.7.0a0,<2.7.14,>=2.8.0a0,<2.8.6,>=2.10.0a1,<2.10.0b1,>=2.9.0b1,<2.9.0rc4" }, { "advisory": "Ansible 2.6.18, 2.7.12 and 2.8.2 include a fix for CVE-2019-10156: A flaw was discovered in the way Ansible templating was implemented in versions before 2.6.18, 2.7.12 and 2.8.2, causing the possibility of information disclosure through unexpected variable substitution. By taking advantage of unintended variable substitution the content of any variable may be disclosed.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10156", "cve": "CVE-2019-10156", "id": "pyup.io-42887", "more_info_path": "/vulnerabilities/CVE-2019-10156/42887", "specs": [ ">=2.7.0a0,<2.7.12", ">=2.8.0a1,<2.8.2", "<2.6.18" ], "v": ">=2.7.0a0,<2.7.12,>=2.8.0a1,<2.8.2,<2.6.18" }, { "advisory": "Ansible versions 2.7.15, 2.8.7 and 2.9.1 include a fix for CVE-2019-14864: Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, are not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used to send tasks results events to collectors. This would disclose and collect any sensitive data.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14864", "cve": "CVE-2019-14864", "id": "pyup.io-42882", "more_info_path": "/vulnerabilities/CVE-2019-14864/42882", "specs": [ ">=2.7.0a0,<2.7.15", ">=2.8.0a0,<2.8.7", ">=2.9.0a0,<2.9.1" ], "v": ">=2.7.0a0,<2.7.15,>=2.8.0a0,<2.8.7,>=2.9.0a0,<2.9.1" }, { "advisory": "Ansible versions 2.7.17, 2.8.9 and 2.9.6 include a fix for CVE-2020-1738: A flaw was found in Ansible Engine when the module package or service is used and the parameter 'use' is not specified. If a previous task is executed with a malicious user, the module sent can be selected by the attacker using the ansible facts file. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1738", "cve": "CVE-2020-1738", "id": "pyup.io-42873", "more_info_path": "/vulnerabilities/CVE-2020-1738/42873", "specs": [ ">=2.7.0a0,<2.7.17", ">=2.8.0a0,<2.8.9", ">=2.9.0a0,<2.9.6" ], "v": ">=2.7.0a0,<2.7.17,>=2.8.0a0,<2.8.9,>=2.9.0a0,<2.9.6" }, { "advisory": "Ansible versions 2.7.17, 2.8.9 and 2.9.6 include a fix for CVE-2020-1736: A flaw was found in Ansible Engine when a file is moved using atomic_move primitive as the file mode cannot be specified. This sets the destination files world-readable if the destination file does not exist and if the file exists, the file could be changed to have less restrictive permissions before the move. This could lead to the disclosure of sensitive data. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1736", "cve": "CVE-2020-1736", "id": "pyup.io-42875", "more_info_path": "/vulnerabilities/CVE-2020-1736/42875", "specs": [ ">=2.7.0a0,<2.7.17", ">=2.8.0a0,<2.8.9", ">=2.9.0a0,<2.9.6" ], "v": ">=2.7.0a0,<2.7.17,>=2.8.0a0,<2.8.9,>=2.9.0a0,<2.9.6" }, { "advisory": "Ansible versions 2.7.17, 2.8.9 and 2.9.6 include a fix for CVE-2020-10684: A flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.9 and 2.9.6 respectively, when using ansible_facts as a subkey of itself and promoting it to a variable when inject is enabled, overwriting the ansible_facts after the clean. An attacker could take advantage of this by altering the ansible_facts, such as ansible_hosts, users and any other key data which would lead into privilege escalation or code injection.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10684", "cve": "CVE-2020-10684", "id": "pyup.io-42864", "more_info_path": "/vulnerabilities/CVE-2020-10684/42864", "specs": [ ">=2.7.0a0,<2.7.17", ">=2.8.0a0,<2.8.9", ">=2.9.0a0,<2.9.6" ], "v": ">=2.7.0a0,<2.7.17,>=2.8.0a0,<2.8.9,>=2.9.0a0,<2.9.6" }, { "advisory": "A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS command injections. This could result in a loss of confidentiality of the system among other issues.", "cve": "CVE-2019-14905", "id": "pyup.io-54155", "more_info_path": "/vulnerabilities/CVE-2019-14905/54155", "specs": [ ">=2.7.0a1,<2.7.16", ">=2.8.0a1,<2.8.8", ">=2.9.0b1,<2.9.3" ], "v": ">=2.7.0a1,<2.7.16,>=2.8.0a1,<2.8.8,>=2.9.0b1,<2.9.3" }, { "advisory": "Execution of Ansible playbooks on Windows platforms with PowerShell ScriptBlock logging and Module logging enabled can allow for 'become' passwords to appear in EventLogs in plaintext. A local user with administrator privileges on the machine can view these logs and discover the plaintext password.", "cve": "CVE-2018-16859", "id": "pyup.io-54011", "more_info_path": "/vulnerabilities/CVE-2018-16859/54011", "specs": [ ">=2.7.0a1,<2.7.4", ">=0,<2.5.13", ">=2.6.0a1,<2.6.10" ], "v": ">=2.7.0a1,<2.7.4,>=0,<2.5.13,>=2.6.0a1,<2.6.10" }, { "advisory": "Ansible 2.8.4 includes a fix for CVE-2019-10217: A flaw was found in Ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all GCP modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running Ansible playbooks.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10217", "cve": "CVE-2019-10217", "id": "pyup.io-42885", "more_info_path": "/vulnerabilities/CVE-2019-10217/42885", "specs": [ ">=2.8.0a0,<2.8.4" ], "v": ">=2.8.0a0,<2.8.4" }, { "advisory": "Ansible 2.6.19, 2.7.13 and 2.8.4 include a fix for CVE-2019-10206: Ansible-playbook -k and Ansible cli tools, all versions 2.8.x before 2.8.4, all 2.7.x before 2.7.13 and all 2.6.x before 2.6.19, prompt passwords by expanding them from templates as they could contain special characters. Passwords should be wrapped to prevent templates trigger and exposing them.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10206", "cve": "CVE-2019-10206", "id": "pyup.io-42886", "more_info_path": "/vulnerabilities/CVE-2019-10206/42886", "specs": [ ">=2.8.0a0,<2.8.4", ">=2.7.0a0,<2.7.13", "<2.6.19" ], "v": ">=2.8.0a0,<2.8.4,>=2.7.0a0,<2.7.13,<2.6.19" }, { "advisory": "Ansible versions 2.7.16, 2.8.8 and 2.9.3 include a fix for CVE-2019-14904: A flaw was found in the solaris_zone module from the Ansible Community modules. When setting the name for the zone on the Solaris host, the zone name is checked by listing the process with the 'ps' bare command on the remote machine. An attacker could take advantage of this flaw by crafting the name of the zone and executing arbitrary commands in the remote host. Ansible Engine 2.7.15, 2.8.7, and 2.9.2 as well as previous versions are affected.", "cve": "CVE-2019-14904", "id": "pyup.io-42881", "more_info_path": "/vulnerabilities/CVE-2019-14904/42881", "specs": [ ">=2.8.0a0,<2.8.8", ">=2.9.0a0,<2.9.3", "<2.7.16" ], "v": ">=2.8.0a0,<2.8.8,>=2.9.0a0,<2.9.3,<2.7.16" }, { "advisory": "A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality.", "cve": "CVE-2021-20180", "id": "pyup.io-54426", "more_info_path": "/vulnerabilities/CVE-2021-20180/54426", "specs": [ ">=2.8.0a1,<2.8.19", ">=2.9.0b1,<2.9.18" ], "v": ">=2.8.0a1,<2.8.19,>=2.9.0b1,<2.9.18" }, { "advisory": "Affected versions of the `ansible` package are vulnerable to Information Disclosure due to improper error handling in the ansible-connection module. The vulnerability exists because the module includes sensitive information, such as user credentials, in traceback error messages when an unexpected response is received from the `set_options` function. An attacker could exploit this vulnerability by causing an error condition that triggers the traceback, thereby gaining access to confidential information without needing authentication.", "cve": "CVE-2021-3620", "id": "pyup.io-54421", "more_info_path": "/vulnerabilities/CVE-2021-3620/54421", "specs": [ ">=2.8.0a1,<2.9.27rc1" ], "v": ">=2.8.0a1,<2.9.27rc1" }, { "advisory": "An archive traversal flaw was found in all ansible-engine versions 2.9.x prior to 2.9.7, when running ansible-galaxy collection install. When extracting a collection .tar.gz file, the directory is created without sanitizing the filename. An attacker could take advantage to overwrite any file within the system.", "cve": "CVE-2020-10691", "id": "pyup.io-54172", "more_info_path": "/vulnerabilities/CVE-2020-10691/54172", "specs": [ ">=2.9.0b1,<2.9.7" ], "v": ">=2.9.0b1,<2.9.7" } ], "ansible-core": [ { "advisory": "A flaw was found in Ansible if an Ansible user sets ANSIBLE_ASYNC_DIR to a subdirectory of a world-writable directory. When this occurs, there is a race condition on the managed machine. A malicious, non-privileged account on the remote machine can exploit the race condition to access the async result data. This flaw affects Ansible Tower 3.7 and Ansible Automation Platform 1.2.", "cve": "CVE-2021-3533", "id": "pyup.io-66667", "more_info_path": "/vulnerabilities/CVE-2021-3533/66667", "specs": [ "<2.12.0b1" ], "v": "<2.12.0b1" }, { "advisory": "An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG configuration in some scenarios. It was discovered that information is still included in the output in certain tasks, such as loop items. Depending on the task, this issue may include sensitive information, such as decrypted secret values.", "cve": "CVE-2024-0690", "id": "pyup.io-66700", "more_info_path": "/vulnerabilities/CVE-2024-0690/66700", "specs": [ "<2.14.14", ">=2.15.0b1,<2.15.9", ">=2.16.0b1,<2.16.3" ], "v": "<2.14.14,>=2.15.0b1,<2.15.9,>=2.16.0b1,<2.16.3" }, { "advisory": "A security vulnerability affects Ansible, impacting the handling of sensitive information stored in Ansible Vault files. The vulnerability occurs during playbook execution when using tasks like include_vars to load vaulted variables without setting the no_log: true parameter. This flaw causes sensitive data, including passwords and API keys, to be exposed in plaintext within playbook outputs or logs. Attackers who gain access to these outputs could potentially acquire secrets, leading to unauthorized access or actions on affected systems. Users must immediately review and update their Ansible playbooks to ensure proper use of the no_log: true parameter when handling vaulted variables. Additionally, users should audit recent playbook outputs and logs for potential secret exposure.", "cve": "CVE-2024-8775", "id": "pyup.io-73302", "more_info_path": "/vulnerabilities/CVE-2024-8775/73302", "specs": [ "<2.14.18", ">=2.15.0b1,<2.15.13", ">=2.16.0b1,<2.16.13", ">=2.17.0b1,<2.17.6", ">=2.18.0b1,<2.18.0" ], "v": "<2.14.18,>=2.15.0b1,<2.15.13,>=2.16.0b1,<2.16.13,>=2.17.0b1,<2.17.6,>=2.18.0b1,<2.18.0" }, { "advisory": "Affected versions of Ansible are vulnerable to Incorrect Authorization (CWE-863). This flaw allows unprivileged users to silently create or replace any file on the system and assume ownership when a privileged user executes the user module against the unprivileged user's home directory. The attack requires the attacker to have traversal permissions on the directory containing the target file. To exploit, an attacker leverages these permissions to manipulate file contents.", "cve": "CVE-2024-9902", "id": "pyup.io-74221", "more_info_path": "/vulnerabilities/CVE-2024-9902/74221", "specs": [ "<2.14.18rc1", ">=2.15.0b1,<2.15.13rc1", ">=2.16.0b1,<2.16.13rc1", ">=2.17.0b1,<2.17.6rc1", ">=2.18.0b1,<2.18.0rc2" ], "v": "<2.14.18rc1,>=2.15.0b1,<2.15.13rc1,>=2.16.0b1,<2.16.13rc1,>=2.17.0b1,<2.17.6rc1,>=2.18.0b1,<2.18.0rc2" }, { "advisory": "Ansible-core 2.15.8 includes a fix for CVE-2023-5764: A template injection flaw was found in Ansible where a user's controller internal templating operations may remove the unsafe designation from template data. This issue could allow an attacker to use a specially crafted file to introduce code injection when supplying templating data.", "cve": "CVE-2023-5764", "id": "pyup.io-63066", "more_info_path": "/vulnerabilities/CVE-2023-5764/63066", "specs": [ "<2.15.8" ], "v": "<2.15.8" }, { "advisory": "Affected versions of Ansible-Core before the fix are vulnerable to Improper Input Validation (CWE-20). This vulnerability allows attackers to bypass content protections by exploiting the hostvars object to execute templated content, potentially leading to arbitrary code execution within playbooks. The attack vector involves crafting malicious templates that reference and execute unsafe content through hostvars in hostvars.py. Vulnerable functions include the templating methods that do not properly manage serialization with native Jinja. To mitigate, upgrade to Ansible-Core version which implements proper handling and serialization of hostvars, preventing arbitrary code execution.", "cve": "CVE-2024-11079", "id": "pyup.io-74261", "more_info_path": "/vulnerabilities/CVE-2024-11079/74261", "specs": [ "<2.18.0" ], "v": "<2.18.0" }, { "advisory": "An absolute path traversal attack exists in the Ansible automation platform. This flaw allows an attacker to craft a malicious Ansible role and make the victim execute the role. A symlink can be used to overwrite a file outside of the extraction path.", "cve": "CVE-2023-5115", "id": "pyup.io-65511", "more_info_path": "/vulnerabilities/CVE-2023-5115/65511", "specs": [ ">=0,<2.13.13rc1", ">=2.14.0,<2.14.11rc1", ">=2.15.0,<2.15.5rc1", ">=2.16.0b1,<2.16.0b2" ], "v": ">=0,<2.13.13rc1,>=2.14.0,<2.14.11rc1,>=2.15.0,<2.15.5rc1,>=2.16.0b1,<2.16.0b2" }, { "advisory": "A flaw was found in the Ansible Automation Platform. When creating a new keypair, the ec2_key module prints out the private key directly to the standard output. This flaw allows an attacker to fetch those keys from the log files, compromising the system's confidentiality, integrity, and availability.", "cve": "CVE-2023-4237", "id": "pyup.io-70895", "more_info_path": "/vulnerabilities/CVE-2023-4237/70895", "specs": [ ">=2.8.0,<=2.15.2" ], "v": ">=2.8.0,<=2.15.2" } ], "ansible-doctor": [ { "advisory": "Ansible-doctor version 4.0.0 upgrades its dependency on ansible-core from version 2.13.13 to 2.14.12, in response to the identified vulnerabilities outlined in CVE-2023-5764.", "cve": "CVE-2023-5764", "id": "pyup.io-63672", "more_info_path": "/vulnerabilities/CVE-2023-5764/63672", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "Ansible-doctor 7.0.0 updates its dependency 'ansible-core' to v2.14.18 to include a security fix.", "cve": "CVE-2024-9902", "id": "pyup.io-74092", "more_info_path": "/vulnerabilities/CVE-2024-9902/74092", "specs": [ "<7.0.0" ], "v": "<7.0.0" }, { "advisory": "Ansible-doctor has updated its dependency on ansible-core to version 2.16.14 to address the security vulnerability tracked as CVE-2024-11079.", "cve": "CVE-2024-11079", "id": "pyup.io-74509", "more_info_path": "/vulnerabilities/CVE-2024-11079/74509", "specs": [ "<7.0.1" ], "v": "<7.0.1" } ], "ansible-lint": [ { "advisory": "Affected versions of the ansible-lint package are vulnerable to insecure temporary directory usage due to a hardcoded, predictable async directory under /tmp. \r\nhttps://github.com/ansible/ansible-lint/issues/4875\r\nhttps://github.com/ansible/ansible-lint/commit/62dda96d8b28f99d7a26a8bc75f392b4103c2adf", "cve": "PVE-2026-84062", "id": "pyup.io-84062", "more_info_path": "/vulnerabilities/PVE-2026-84062/84062", "specs": [ "<26.1.0" ], "v": "<26.1.0" } ], "ansible-runner": [ { "advisory": "Ansible-runner 1.3.1 sets safer default permissions when writing job events.\r\nhttps://github.com/ansible/ansible-runner/commit/dd2e549c6aadca4fb4f2cde11f1d4dca4b98964f", "cve": "PVE-2021-36995", "id": "pyup.io-36995", "more_info_path": "/vulnerabilities/PVE-2021-36995/36995", "specs": [ "<1.3.1" ], "v": "<1.3.1" }, { "advisory": "A flaw was found in ansible-runner. An improper escaping of the shell command, while calling the ansible_runner.interface.run_command, can lead to parameters getting executed as host's shell command. A developer could unintentionally write code that gets executed in the host rather than the virtual environment.", "cve": "CVE-2021-4041", "id": "pyup.io-54468", "more_info_path": "/vulnerabilities/CVE-2021-4041/54468", "specs": [ ">=0,<2.1.0" ], "v": ">=0,<2.1.0" }, { "advisory": "A race condition flaw was found in ansible-runner, where an attacker could watch for rapid creation and deletion of a temporary directory, substitute their directory at that name, and then have access to ansible-runner's private_data_dir the next time ansible-runner made use of the private_data_dir. The highest Threat out of this flaw is to integrity and confidentiality.", "cve": "CVE-2021-3702", "id": "pyup.io-54467", "more_info_path": "/vulnerabilities/CVE-2021-3702/54467", "specs": [ ">=2.0.0,<2.1.0" ], "v": ">=2.0.0,<2.1.0" }, { "advisory": "A flaw was found in ansible-runner where the default temporary files configuration in ansible-2.0.0 are written to world R/W locations. This flaw allows an attacker to pre-create the directory, resulting in reading private information or forcing ansible-runner to write files as the legitimate user in a place they did not expect. The highest threat from this vulnerability is to confidentiality and integrity.", "cve": "CVE-2021-3701", "id": "pyup.io-54466", "more_info_path": "/vulnerabilities/CVE-2021-3701/54466", "specs": [ ">=2.0.0,<2.1.0" ], "v": ">=2.0.0,<2.1.0" } ], "ansible-tower-cli": [ { "advisory": "Ansible-tower-cli versions 2.7.17, 2.8.9 and 2.9.6 include a fix for CVE-2020-10684: A flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.9 and 2.9.6 respectively, when using ansible_facts as a subkey of itself and promoting it to a variable when inject is enabled, overwriting the ansible_facts after the clean. An attacker could take advantage of this by altering the ansible_facts, such as ansible_hosts, users and any other key data which would lead into privilege escalation or code injection.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10684", "cve": "CVE-2020-10684", "id": "pyup.io-42865", "more_info_path": "/vulnerabilities/CVE-2020-10684/42865", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Ansible-tower-cli versions 3.1.x and before use API v1, what implies the use of ansible-tower version 3.2.x or earlier. These are affected by CVE-2021-3447.", "cve": "CVE-2021-3447", "id": "pyup.io-42861", "more_info_path": "/vulnerabilities/CVE-2021-3447/42861", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Ansible-tower-cli versions 3.1.x and before use API v1, what implies the use of ansible-tower version 3.2.x or earlier. These are affected by CVE-2021-3583.", "cve": "CVE-2021-3583", "id": "pyup.io-42925", "more_info_path": "/vulnerabilities/CVE-2021-3583/42925", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Ansible-tower-cli versions 3.1.x and before use API v1, what implies the use of ansible-tower version 3.2.x or earlier. These are affected by CVE-2020-1740.", "cve": "CVE-2020-1740", "id": "pyup.io-42870", "more_info_path": "/vulnerabilities/CVE-2020-1740/42870", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Ansible-tower-cli versions 3.1.x and before use API v1, what implies the use of ansible-tower version 3.2.x or earlier. These are affected by CVE-2020-1738.", "cve": "CVE-2020-1738", "id": "pyup.io-42874", "more_info_path": "/vulnerabilities/CVE-2020-1738/42874", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Ansible-tower-cli versions 3.1.x and before use API v1, what implies the use of ansible-tower version 3.2.x or earlier. These are affected by CVE-2020-1736.", "cve": "CVE-2020-1736", "id": "pyup.io-42876", "more_info_path": "/vulnerabilities/CVE-2020-1736/42876", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Ansible-tower-cli versions 3.1.x and before use API v1, what implies the use of ansible-tower version 3.2.x or earlier. These are affected by CVE-2020-1735.", "cve": "CVE-2020-1735", "id": "pyup.io-42878", "more_info_path": "/vulnerabilities/CVE-2020-1735/42878", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Ansible-tower-cli versions 3.1.x and before use API v1, what implies the use of ansible-tower version 3.2.x or earlier. These are affected by CVE-2020-1739.", "cve": "CVE-2020-1739", "id": "pyup.io-42872", "more_info_path": "/vulnerabilities/CVE-2020-1739/42872", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Ansible-tower-cli versions 3.1.x and before use API v1, what implies the use of ansible-tower version 3.2.x or earlier. These are affected by CVE-2020-1733.", "cve": "CVE-2020-1733", "id": "pyup.io-42880", "more_info_path": "/vulnerabilities/CVE-2020-1733/42880", "specs": [ "<3.2.0" ], "v": "<3.2.0" } ], "ansible-vault": [ { "advisory": "An exploitable vulnerability exists in the yaml loading functionality of ansible-vault before 1.0.5. A specially crafted vault can execute arbitrary python commands resulting in command execution. An attacker can insert python into the vault to trigger this vulnerability.\r\nhttps://github.com/tomoh1r/ansible-vault/commit/3f8f659ef443ab870bb19f95d43543470168ae04", "cve": "CVE-2017-2809", "id": "pyup.io-35730", "more_info_path": "/vulnerabilities/CVE-2017-2809/35730", "specs": [ "<1.0.5" ], "v": "<1.0.5" } ], "ansibleguy-webui": [ { "advisory": "vansibleguy-webui is an open-source WebUI for using Ansible. Multiple forms in affected versions allowed the injection of HTML elements. These are returned to the user after executing job actions and thus evaluated by the browser.", "cve": "CVE-2024-36110", "id": "pyup.io-71998", "more_info_path": "/vulnerabilities/CVE-2024-36110/71998", "specs": [ "<0.0.21" ], "v": "<0.0.21" }, { "advisory": "Affected versions of Ansibleguy-webui are potentially vulnerable to XSS.", "cve": "PVE-2024-72284", "id": "pyup.io-72284", "more_info_path": "/vulnerabilities/PVE-2024-72284/72284", "specs": [ "<0.0.23" ], "v": "<0.0.23" } ], "ansigenome": [ { "advisory": "Ansigenome before 0.6.0 uses yaml.load() instead of yaml.safe_load(), allowing a code execution vulnerability.", "cve": "CVE-2017-18342", "id": "pyup.io-34505", "more_info_path": "/vulnerabilities/CVE-2017-18342/34505", "specs": [ "<0.6.0" ], "v": "<0.6.0" } ], "ansitoimg": [ { "advisory": "Ansitoimg 2021.0.1 updates its dependency 'pillow' to a version >= 8.1.1 to include security fixes.", "cve": "CVE-2020-35654", "id": "pyup.io-40996", "more_info_path": "/vulnerabilities/CVE-2020-35654/40996", "specs": [ "<2021.0.1" ], "v": "<2021.0.1" }, { "advisory": "Ansitoimg 2021.0.1 updates its dependency 'pillow' to a version >= 8.1.1 to include security fixes.", "cve": "CVE-2021-27921", "id": "pyup.io-40611", "more_info_path": "/vulnerabilities/CVE-2021-27921/40611", "specs": [ "<2021.0.1" ], "v": "<2021.0.1" }, { "advisory": "Ansitoimg 2021.0.1 updates its dependency 'pillow' to a version >= 8.1.1 to include security fixes.", "cve": "CVE-2021-27923", "id": "pyup.io-40993", "more_info_path": "/vulnerabilities/CVE-2021-27923/40993", "specs": [ "<2021.0.1" ], "v": "<2021.0.1" }, { "advisory": "Ansitoimg 2021.0.1 updates its dependency 'pillow' to a version >= 8.1.1 to include security fixes.", "cve": "CVE-2020-35655", "id": "pyup.io-40994", "more_info_path": "/vulnerabilities/CVE-2020-35655/40994", "specs": [ "<2021.0.1" ], "v": "<2021.0.1" }, { "advisory": "Ansitoimg 2021.0.1 updates its dependency 'pillow' to a version >= 8.1.1 to include security fixes.", "cve": "CVE-2020-35653", "id": "pyup.io-40995", "more_info_path": "/vulnerabilities/CVE-2020-35653/40995", "specs": [ "<2021.0.1" ], "v": "<2021.0.1" }, { "advisory": "Ansitoimg 2021.0.1 updates its dependency 'pillow' to a version >= 8.1.1 to include security fixes.", "cve": "CVE-2021-27922", "id": "pyup.io-40612", "more_info_path": "/vulnerabilities/CVE-2021-27922/40612", "specs": [ "<2021.0.1" ], "v": "<2021.0.1" } ], "ansys-geometry-core": [ { "advisory": "PyAnsys Geometry is a Python client library for the Ansys Geometry service and other CAD Ansys products. On file src/ansys/geometry/core/connection/product_instance.py, upon calling this method _start_program directly, users could exploit its usage to perform malicious operations on the current machine where the script is ran. This vulnerability is fixed in 0.3.3 and 0.4.12. See CVE-2024-29189.", "cve": "CVE-2024-29189", "id": "pyup.io-66973", "more_info_path": "/vulnerabilities/CVE-2024-29189/66973", "specs": [ ">=0.3.0,<0.3.3", ">=0.4.0,<0.4.12" ], "v": ">=0.3.0,<0.3.3,>=0.4.0,<0.4.12" } ], "ansys-tools-repo-sync": [ { "advisory": "Ansys-tools-repo-sync 0.1.17 updates its dependency 'urllib3' to v1.26.9 to include security fixes.", "cve": "CVE-2019-11324", "id": "pyup.io-51113", "more_info_path": "/vulnerabilities/CVE-2019-11324/51113", "specs": [ "<0.1.17" ], "v": "<0.1.17" }, { "advisory": "Ansys-tools-repo-sync 0.1.17 updates its dependency 'urllib3' to v1.26.9 to include security fixes.", "cve": "CVE-2019-11236", "id": "pyup.io-51114", "more_info_path": "/vulnerabilities/CVE-2019-11236/51114", "specs": [ "<0.1.17" ], "v": "<0.1.17" }, { "advisory": "Ansys-tools-repo-sync 0.1.17 updates its dependency 'urllib3' to v1.26.9 to include security fixes.", "cve": "CVE-2018-20060", "id": "pyup.io-51115", "more_info_path": "/vulnerabilities/CVE-2018-20060/51115", "specs": [ "<0.1.17" ], "v": "<0.1.17" }, { "advisory": "Ansys-tools-repo-sync 0.1.17 updates its dependency 'urllib3' to v1.26.9 to include security fixes.", "cve": "CVE-2020-26137", "id": "pyup.io-51112", "more_info_path": "/vulnerabilities/CVE-2020-26137/51112", "specs": [ "<0.1.17" ], "v": "<0.1.17" }, { "advisory": "Ansys-tools-repo-sync 0.1.17 updates its dependency 'urllib3' to v1.26.9 to include security fixes.", "cve": "CVE-2021-33503", "id": "pyup.io-51024", "more_info_path": "/vulnerabilities/CVE-2021-33503/51024", "specs": [ "<0.1.17" ], "v": "<0.1.17" } ], "anthropic": [ { "advisory": "Anthropic 0.3.2 updates its dependency 'certifi' to version '2023.5.7' to include a security fix.\r\nhttps://github.com/anthropics/anthropic-sdk-python/pull/51", "cve": "CVE-2022-23491", "id": "pyup.io-59254", "more_info_path": "/vulnerabilities/CVE-2022-23491/59254", "specs": [ "<0.3.2" ], "v": "<0.3.2" } ], "antilles-tools": [ { "advisory": "A dependency confusion vulnerability was reported in the Antilles open-source software prior to version 1.0.1 that could allow for remote code execution during installation due to a package listed in requirements.txt not existing in the public package index (PyPi). MITRE classifies this weakness as an Uncontrolled Search Path Element (CWE-427) in which a private package dependency may be replaced by an unauthorized package of the same name published to a well-known public repository such as PyPi. The configuration has been updated to only install components built by Antilles, removing all other public package indexes. Additionally, the antilles-tools dependency has been published to PyPi.", "cve": "CVE-2021-3840", "id": "pyup.io-54373", "more_info_path": "/vulnerabilities/CVE-2021-3840/54373", "specs": [ ">=0,<1.0.1" ], "v": ">=0,<1.0.1" } ], "anyio": [ { "advisory": "Anyio version 4.4.0 addresses a thread race condition in `_eventloop.get_asynclib()` that caused crashes when multiple event loops of the same backend were running in separate threads and simultaneously attempted to use AnyIO for the first time. This fix ensures more stable and reliable performance in multi-threaded environments.", "cve": "PVE-2024-71199", "id": "pyup.io-71199", "more_info_path": "/vulnerabilities/PVE-2024-71199/71199", "specs": [ "<4.4.0" ], "v": "<4.4.0" } ], "anymotion-sdk": [ { "advisory": "Anymotion-sdk 1.2.5 updates its dependency 'urllib3' to v1.26.5 to include a security fix.", "cve": "CVE-2021-33503", "id": "pyup.io-40842", "more_info_path": "/vulnerabilities/CVE-2021-33503/40842", "specs": [ "<1.2.5" ], "v": "<1.2.5" } ], "ao3-poster": [ { "advisory": "Ao3-poster version 0.0.7 updates its dependency 'rsa' to v4.7 to include security fixes.", "cve": "CVE-2020-25658", "id": "pyup.io-49125", "more_info_path": "/vulnerabilities/CVE-2020-25658/49125", "specs": [ "<0.0.7" ], "v": "<0.0.7" }, { "advisory": "Ao3-poster version 0.0.7 updates its dependency 'pygments' to v2.7.4 to include security fixes.", "cve": "CVE-2021-20270", "id": "pyup.io-49123", "more_info_path": "/vulnerabilities/CVE-2021-20270/49123", "specs": [ "<0.0.7" ], "v": "<0.0.7" }, { "advisory": "Ao3-poster version 0.0.7 updates its dependency 'httplib2' to v0.19.0 to include security fixes.", "cve": "CVE-2020-11078", "id": "pyup.io-49128", "more_info_path": "/vulnerabilities/CVE-2020-11078/49128", "specs": [ "<0.0.7" ], "v": "<0.0.7" }, { "advisory": "Ao3-poster version 0.0.7 updates its dependency 'jinja2' to v2.11.3 to include a security fix.", "cve": "CVE-2020-13757", "id": "pyup.io-49126", "more_info_path": "/vulnerabilities/CVE-2020-13757/49126", "specs": [ "<0.0.7" ], "v": "<0.0.7" }, { "advisory": "Ao3-poster version 0.0.7 updates its dependency 'httplib2' to v0.19.0 to include security fixes.", "cve": "CVE-2021-21240", "id": "pyup.io-49127", "more_info_path": "/vulnerabilities/CVE-2021-21240/49127", "specs": [ "<0.0.7" ], "v": "<0.0.7" }, { "advisory": "Ao3-poster version 0.0.7 updates its dependency 'jinja2' to v2.11.3 to include a security fix.", "cve": "CVE-2020-28493", "id": "pyup.io-42030", "more_info_path": "/vulnerabilities/CVE-2020-28493/42030", "specs": [ "<0.0.7" ], "v": "<0.0.7" }, { "advisory": "Ao3-poster version 0.0.7 updates its dependency 'pygments' to v2.7.4 to include security fixes.", "cve": "CVE-2021-27291", "id": "pyup.io-49124", "more_info_path": "/vulnerabilities/CVE-2021-27291/49124", "specs": [ "<0.0.7" ], "v": "<0.0.7" } ], "apache-age-python": [ { "advisory": "Apache-age-python is affected by CVE-2022-45786: There are issues with the AGE drivers for Golang and Python that enable SQL injections to occur. This impacts AGE for PostgreSQL 11 & AGE for PostgreSQL 12, all versions up-to-and-including 1.1.0, when using those drivers. The fix is to update to the latest Golang and Python drivers in addition to the latest version of AGE that is used for PostgreSQL 11 or PostgreSQL 12. The update of AGE will add a new function to enable parameterization of the cypher() function, which, in conjunction with the driver updates, will resolve this issue. Background (for those who want more information): After thoroughly researching this issue, we found that due to the nature of the cypher() function, it was not easy to parameterize the values passed into it. This enabled SQL injections, if the developer of the driver wasn't careful. The developer of the Golang and Pyton drivers didn't fully utilize parameterization, likely because of this, thus enabling SQL injections. The obvious fix to this issue is to use parameterization in the drivers for all PG SQL queries. However, parameterizing all PG queries is complicated by the fact that the cypher() function call itself cannot be parameterized directly, as it isn't a real function. At least, not the parameters that would take the graph name and cypher query. The reason the cypher() function cannot have those values parameterized is because the function is a placeholder and never actually runs. The cypher() function node, created by PG in the query tree, is transformed and replaced with a query tree for the actual cypher query during the analyze phase. The problem is that parameters - that would be passed in and that the cypher() function transform needs to be resolved - are only resolved in the execution phase, which is much later. Since the transform of the cypher() function needs to know the graph name and cypher query prior to execution, they can't be passed as parameters. The fix that we are testing right now, and are proposing to use, is to create a function that will be called prior to the execution of the cypher() function transform. This new function will allow values to be passed as parameters for the graph name and cypher query. As this command will be executed prior to the cypher() function transform, its values will be resolved. These values can then be cached for the immediately following cypher() function transform to use. As added features, the cached values will store the calling session's pid, for validation. And, the cypher() function transform will clear this cached information after function invocation, regardless of whether it was used. This method will allow the parameterizing of the cypher() function indirectly and provide a way to lock out SQL injection attacks.", "cve": "CVE-2022-45786", "id": "pyup.io-52972", "more_info_path": "/vulnerabilities/CVE-2022-45786/52972", "specs": [ ">0" ], "v": ">0" } ], "apache-airflow": [ { "advisory": "Apache-airflow 1.10.0 fixes XSS vulnerability in Variable endpoint.\r\nhttps://github.com/apache/airflow/commit/8f9bf94d82abc59336e642db64e575cee0cc5df0", "cve": "PVE-2021-36832", "id": "pyup.io-36832", "more_info_path": "/vulnerabilities/PVE-2021-36832/36832", "specs": [ "<1.10.0" ], "v": "<1.10.0" }, { "advisory": "In Apache Airflow < 1.10.12, the \"origin\" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS.", "cve": "CVE-2020-13944", "id": "pyup.io-42325", "more_info_path": "/vulnerabilities/CVE-2020-13944/42325", "specs": [ "<1.10.12" ], "v": "<1.10.12" }, { "advisory": "The \"origin\" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. This issue affects Apache Airflow versions prior to 1.10.13. This is same as CVE-2020-13944 but the implemented fix in Airflow 1.10.13 did not fix the issue completely.", "cve": "CVE-2020-17515", "id": "pyup.io-42326", "more_info_path": "/vulnerabilities/CVE-2020-17515/42326", "specs": [ "<1.10.13" ], "v": "<1.10.13" }, { "advisory": "In Apache Airflow versions prior to 1.10.13, the Charts and Query View of the old (Flask-admin based) UI were vulnerable for SSRF attack. See CVE-2020-17513.", "cve": "CVE-2020-17513", "id": "pyup.io-39282", "more_info_path": "/vulnerabilities/CVE-2020-17513/39282", "specs": [ "<1.10.13" ], "v": "<1.10.13" }, { "advisory": "Apache-airflow 1.10.14 starts using a random SECRET_KEY, as it is recommended by Flask community.\r\nhttps://github.com/apache/airflow/commit/dfa7b26ddaca80ee8fd9915ee9f6eac50fac77f6\r\nhttps://github.com/apache/airflow/commit/fe6d00a54f83468e296777d3b83b65a2ae7169ec", "cve": "PVE-2022-48307", "id": "pyup.io-48307", "more_info_path": "/vulnerabilities/PVE-2022-48307/48307", "specs": [ "<1.10.14" ], "v": "<1.10.14" }, { "advisory": "Apache-airflow 1.10.3 updates its dependency 'flask-admin' v1.5.3 to include a security fix.", "cve": "CVE-2018-16516", "id": "pyup.io-51849", "more_info_path": "/vulnerabilities/CVE-2018-16516/51849", "specs": [ "<1.10.3" ], "v": "<1.10.3" }, { "advisory": "Apache-airflow 1.10.3 updates its dependency 'gunicorn' minimum requirement to v19.5.0 to include a security fix.", "cve": "CVE-2018-1000164", "id": "pyup.io-51833", "more_info_path": "/vulnerabilities/CVE-2018-1000164/51833", "specs": [ "<1.10.3" ], "v": "<1.10.3" }, { "advisory": "Apache-airflow 1.10.3 sets HttpOnly flag to cookies by default.\r\nhttps://github.com/apache/airflow/commit/1211dddfd7167fd90575f40dd6734b0af9aec8b7", "cve": "PVE-2022-51848", "id": "pyup.io-51848", "more_info_path": "/vulnerabilities/PVE-2022-51848/51848", "specs": [ "<1.10.3" ], "v": "<1.10.3" }, { "advisory": "Apache-airflow 1.9.0a0 includes a security fix: An individual with the capacity to create or modify Charts holds the potential to run any code they desire on the Airflow server.", "cve": "PVE-2023-99964", "id": "pyup.io-60877", "more_info_path": "/vulnerabilities/PVE-2023-99964/60877", "specs": [ "<1.9.0a0" ], "v": "<1.9.0a0" }, { "advisory": "Apache-airflow 1.9.0a0 includes a security fix: When navigating to a page where the 'dag_id' parameter is specified as an HTML tag, the tag is rendered. This is because it uses the Markup tag, which subsequently marks HTML as safe. This presents cross-site scripting vulnerabilities due to the display of unsanitized user input.", "cve": "PVE-2023-99965", "id": "pyup.io-60876", "more_info_path": "/vulnerabilities/PVE-2023-99965/60876", "specs": [ "<1.9.0a0" ], "v": "<1.9.0a0" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the Docker provider integration. Therefore, it is affected by CVE-2022-38362.", "cve": "CVE-2022-38362", "id": "pyup.io-63172", "more_info_path": "/vulnerabilities/CVE-2022-38362/63172", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the Apache Hive provider integration. Therefore, it is affected by CVE-2023-25696.", "cve": "CVE-2023-25696", "id": "pyup.io-63179", "more_info_path": "/vulnerabilities/CVE-2023-25696/63179", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the Google Cloud provider integration. Therefore, it is affected by CVE-2023-25691.", "cve": "CVE-2023-25691", "id": "pyup.io-63175", "more_info_path": "/vulnerabilities/CVE-2023-25691/63175", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the Apache Spark provider integration. Therefore, it is affected by CVE-2023-40195.", "cve": "CVE-2023-40195", "id": "pyup.io-63170", "more_info_path": "/vulnerabilities/CVE-2023-40195/63170", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the Apache Spark provider integration. Therefore, it is affected by CVE-2023-28710.", "cve": "CVE-2023-28710", "id": "pyup.io-63173", "more_info_path": "/vulnerabilities/CVE-2023-28710/63173", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the Amazon provider integration. Therefore, it is affected by CVE-2023-25956.", "cve": "CVE-2023-25956", "id": "pyup.io-63177", "more_info_path": "/vulnerabilities/CVE-2023-25956/63177", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the Google Cloud Provider integration. Therefore, it is affected by CVE-2023-25692.", "cve": "CVE-2023-25692", "id": "pyup.io-63176", "more_info_path": "/vulnerabilities/CVE-2023-25692/63176", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Improper Input Validation vulnerability in the Apache Airflow Sqoop Provider. This issue affects Apache Airflow Sqoop Provider versions before 3.1.1.", "cve": "CVE-2023-25693", "id": "pyup.io-63178", "more_info_path": "/vulnerabilities/CVE-2023-25693/63178", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the Apache Hive provider integration. Therefore, it is affected by CVE-2023-28706.", "cve": "CVE-2023-28706", "id": "pyup.io-63174", "more_info_path": "/vulnerabilities/CVE-2023-28706/63174", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the JDBC provider integration. Therefore, it is affected by CVE-2023-22886.", "cve": "CVE-2023-22886", "id": "pyup.io-63171", "more_info_path": "/vulnerabilities/CVE-2023-22886/63171", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow before 2.0.0b1 bundles the code for the Apache Hive provider integration. Therefore, it is affected by CVE-2022-46421.", "cve": "CVE-2022-46421", "id": "pyup.io-63180", "more_info_path": "/vulnerabilities/CVE-2022-46421/63180", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "Apache-airflow 2.1.0rc1 updates its NPM dependency 'stylelint' to include a security fix.\r\nhttps://github.com/apache/airflow/pull/15784", "cve": "CVE-2020-7753", "id": "pyup.io-48305", "more_info_path": "/vulnerabilities/CVE-2020-7753/48305", "specs": [ "<2.1.0rc1" ], "v": "<2.1.0rc1" }, { "advisory": "Apache-airflow 2.1.1 updates NPM dependencies to fix a vulnerability in 'normalize-url' package.\r\nhttps://github.com/apache/airflow/pull/16375", "cve": "CVE-2021-33502", "id": "pyup.io-48304", "more_info_path": "/vulnerabilities/CVE-2021-33502/48304", "specs": [ "<2.1.1" ], "v": "<2.1.1" }, { "advisory": "Apache Airflow version 2.1.2 includes a fix for CVE-2021-35936: If remote logging is not used, the worker (in the case of CeleryExecutor) or the scheduler (in the case of LocalExecutor) runs a Flask logging server and is listening on a specific port and also binds on 0.0.0.0 by default. This logging server had no authentication and allows reading log files of DAG jobs. \r\nhttps://lists.apache.org/thread.html/r53d6bd7b0a66f92ddaf1313282f10fec802e71246606dd30c16536df%40%3Cusers.airflow.apache.org%3E", "cve": "CVE-2021-35936", "id": "pyup.io-41181", "more_info_path": "/vulnerabilities/CVE-2021-35936/41181", "specs": [ "<2.1.2" ], "v": "<2.1.2" }, { "advisory": "Apache Airflow, in affected versions, contains a vulnerability where a malicious provider could exploit a cross-site scripting (XSS) attack through a provider documentation link. A malicious user could inject a JavaScript URL (e.g., `javascript:prompt(document.domain)`) into the provider's metadata. If a user clicks on this crafted link, it could trigger an XSS attack. The vulnerability requires the malicious provider to be installed on the web server and the user to interact with the malicious link.", "cve": "CVE-2024-41937", "id": "pyup.io-72974", "more_info_path": "/vulnerabilities/CVE-2024-41937/72974", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Apache Airflow affected versions contain a potential security vulnerability in the initialization process. The DAGS_FOLDER was added to sys.path before importing local settings, potentially allowing execution of malicious code if an attacker had write access to the DAGS_FOLDER. The fix reorganizes the initialization sequence, ensuring DAGS_FOLDER is added to sys.path only after local settings are imported. This change mitigates the risk of unintended code execution during startup. Users are strongly advised to update to the latest version incorporating this fix, especially in environments where DAGS_FOLDER access is not strictly controlled.", "cve": "CVE-2024-45034", "id": "pyup.io-73188", "more_info_path": "/vulnerabilities/CVE-2024-45034/73188", "specs": [ "<2.10.1" ], "v": "<2.10.1" }, { "advisory": "Affected versions of Apache Airflow are vulnerable to Exposure of Sensitive Information (CWE-201). This vulnerability allows authenticated users with audit log access to view sensitive configuration variables in task logs by setting them via the CLI. The attack vector involves executing CLI commands that store sensitive variables unencrypted in audit logs within cli.py, enabling unauthorized access to critical data. To mitigate, upgrade to Airflow version which masks secrets in task logs, preventing the exposure of sensitive configuration data. Additionally, users should manually delete any previously logged secret variables from the log table.", "cve": "CVE-2024-50378", "id": "pyup.io-74262", "more_info_path": "/vulnerabilities/CVE-2024-50378/74262", "specs": [ "<2.10.3" ], "v": "<2.10.3" }, { "advisory": "Apache Airflow affected versions have a vulnerability that can expose sensitive configuration variables in task logs. This allows DAG authors to unintentionally or intentionally log such variables, enabling unauthorized users to access critical data and potentially compromising Airflow deployments. Secrets are now masked in task logs to prevent this exposure. Additionally, if secret values might have been logged and logs aren't protected, it is recommended to update those secrets.", "cve": "CVE-2024-45784", "id": "pyup.io-74259", "more_info_path": "/vulnerabilities/CVE-2024-45784/74259", "specs": [ "<2.10.3" ], "v": "<2.10.3" }, { "advisory": "Apache-airflow 2.2.5 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/apache/airflow/pull/20699", "cve": "PVE-2023-60199", "id": "pyup.io-60199", "more_info_path": "/vulnerabilities/PVE-2023-60199/60199", "specs": [ "<2.2.5" ], "v": "<2.2.5" }, { "advisory": "Apache-airflow 2.3.0 updates its NPM dependency 'tar' requirement to '>=6.1.9' to include security fixes.", "cve": "CVE-2021-37713", "id": "pyup.io-48618", "more_info_path": "/vulnerabilities/CVE-2021-37713/48618", "specs": [ "<2.3.0" ], "v": "<2.3.0" }, { "advisory": "Apache-airflow 2.3.0 updates its NPM dependency 'tar' requirement to '>=6.1.9' to include security fixes.", "cve": "CVE-2021-37701", "id": "pyup.io-48616", "more_info_path": "/vulnerabilities/CVE-2021-37701/48616", "specs": [ "<2.3.0" ], "v": "<2.3.0" }, { "advisory": "Apache-airflow 2.3.0 updates its NPM dependency 'datatables.net' to versions ^1.10.23 to include a security fix.", "cve": "CVE-2021-23445", "id": "pyup.io-48604", "more_info_path": "/vulnerabilities/CVE-2021-23445/48604", "specs": [ "<2.3.0" ], "v": "<2.3.0" }, { "advisory": "Apache-airflow 2.3.0 updates its NPM dependency 'tar' requirement to '>=6.1.9' to include security fixes.", "cve": "CVE-2021-37712", "id": "pyup.io-48617", "more_info_path": "/vulnerabilities/CVE-2021-37712/48617", "specs": [ "<2.3.0" ], "v": "<2.3.0" }, { "advisory": "Execution with Unnecessary Privileges: Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Software Foundation Apache Airflow. The \"Run Task\" feature enables authenticated user to bypass some of the restrictions put in place. It allows to execute code in the webserver context as well as allows to bypas limitation of access the user has to certain DAGs. The \"Run Task\" feature is considered dangerous and it has been removed entirely in Airflow 2.6.0. This issue affects Apache Airflow: before 2.6.0.", "cve": "CVE-2023-39508", "id": "pyup.io-65021", "more_info_path": "/vulnerabilities/CVE-2023-39508/65021", "specs": [ "<2.6.0" ], "v": "<2.6.0" }, { "advisory": "The details page for task instances in the user interface is subject to a stored XSS vulnerability. This problem pertains to Apache Airflow versions prior to 2.6.0.\r\nhttps://github.com/apache/airflow/pull/30447/commits/3d894f7a643e9319f5c48e343ac39b248dedaa9b\r\nhttps://github.com/apache/airflow/pull/30779/commits/7c566f7ef4b33175aafc4f89f94fb2096b093940", "cve": "CVE-2023-29247", "id": "pyup.io-63344", "more_info_path": "/vulnerabilities/CVE-2023-29247/63344", "specs": [ "<2.6.0" ], "v": "<2.6.0" }, { "advisory": "Affected version of Apache-airflow are vulnerable to Privilege Context Switching Error. File Task Handler should apply different permissions to log files generated by Airflow in order to handle impersonation.", "cve": "CVE-2023-25754", "id": "pyup.io-62916", "more_info_path": "/vulnerabilities/CVE-2023-25754/62916", "specs": [ "<2.6.0" ], "v": "<2.6.0" }, { "advisory": "Apache Airflow, versions before 2.6.3, has a vulnerability where an authenticated user can use crafted input to make the current request hang. It is recommended to upgrade to a version that is not affected", "cve": "PVE-2024-99900", "id": "pyup.io-64989", "more_info_path": "/vulnerabilities/PVE-2024-99900/64989", "specs": [ "<2.6.3" ], "v": "<2.6.3" }, { "advisory": "Apache Airflow, versions before 2.6.3, is affected by a vulnerability that allows an attacker to cause a service disruption by manipulating the run_id parameter. This vulnerability is considered low since it requires an authenticated user to exploit it. It is recommended to upgrade to a version that is not affected", "cve": "CVE-2023-22888", "id": "pyup.io-62891", "more_info_path": "/vulnerabilities/CVE-2023-22888/62891", "specs": [ "<2.6.3" ], "v": "<2.6.3" }, { "advisory": "Apache Airflow, versions before 2.6.3, is affected by a vulnerability that allows an attacker to perform unauthorized file access outside the intended directory structure by manipulating the run_id parameter. This vulnerability is considered low since it requires an authenticated user to exploit it. It is recommended to upgrade to a version that is not affected", "cve": "CVE-2023-22887", "id": "pyup.io-62890", "more_info_path": "/vulnerabilities/CVE-2023-22887/62890", "specs": [ "<2.6.3" ], "v": "<2.6.3" }, { "advisory": "Apache Airflow, versions before 2.6.3, is affected by a vulnerability that allows an unauthorized actor to gain access to sensitive information in Connection edit view. This vulnerability is considered low since it requires someone with access to Connection resources specifically updating the connection to exploit it. Users should upgrade to version 2.6.3 or later which has removed the vulnerability.", "cve": "PVE-2023-99911", "id": "pyup.io-62823", "more_info_path": "/vulnerabilities/PVE-2023-99911/62823", "specs": [ "<2.6.3" ], "v": "<2.6.3" }, { "advisory": "Apache Airflow affected versions have a vulnerability where an authenticated user can use crafted input to make the current request hang. It is recommended to upgrade to a version that is not affected", "cve": "CVE-2023-36543", "id": "pyup.io-71687", "more_info_path": "/vulnerabilities/CVE-2023-36543/71687", "specs": [ "<2.6.3" ], "v": "<2.6.3" }, { "advisory": "Apache Airflow affected versions are affected by a vulnerability that allows unauthorized read access to a DAG through the URL.", "cve": "CVE-2023-35908", "id": "pyup.io-71688", "more_info_path": "/vulnerabilities/CVE-2023-35908/71688", "specs": [ "<2.6.3" ], "v": "<2.6.3" }, { "advisory": "Apache Airflow affected versions are affected by a vulnerability that allows an unauthorized actor to gain access to sensitive information in Connection edit view. This vulnerability is considered low since it requires someone with access to Connection resources specifically updating the connection to exploit it.", "cve": "CVE-2022-46651", "id": "pyup.io-71689", "more_info_path": "/vulnerabilities/CVE-2022-46651/71689", "specs": [ "<2.6.3" ], "v": "<2.6.3" }, { "advisory": "Apache Airflow SMTP Provider before 1.3.0, Apache Airflow IMAP Provider before 3.3.0, and\u00a0Apache Airflow before 2.7.0 are affected by the\u00a0Validation of OpenSSL Certificate vulnerability.\r\n\r\nThe default SSL context with SSL library did not check a server's X.509\u00a0certificate.\u00a0 Instead, the code accepted any certificate, which could\u00a0result in the disclosure of mail server credentials or mail contents\u00a0when the client connects to an attacker in a MITM position.\r\n\r\nUsers are strongly advised to upgrade to Apache Airflow version 2.7.0 or newer, Apache Airflow IMAP Provider version 3.3.0 or newer, and Apache Airflow SMTP Provider version 1.3.0 or newer to mitigate the risk associated with this vulnerability", "cve": "CVE-2023-39441", "id": "pyup.io-65020", "more_info_path": "/vulnerabilities/CVE-2023-39441/65020", "specs": [ "<2.7.0" ], "v": "<2.7.0" }, { "advisory": "Apache Airflow, in versions prior to 2.7.0, contains a security vulnerability that can be exploited by an authenticated user possessing Connection edit privileges. This vulnerability allows the user to access connection information and exploit the test connection feature by sending many requests, leading to a denial of service (DoS) condition on the server. Furthermore, malicious actors can leverage this vulnerability to establish harmful connections with the server. Users of Apache Airflow are strongly advised to upgrade to version 2.7.0 or newer to mitigate the risk associated with this vulnerability. Additionally, administrators are encouraged to review and adjust user permissions to restrict access to sensitive functionalities, reducing the attack surface.", "cve": "CVE-2023-37379", "id": "pyup.io-65002", "more_info_path": "/vulnerabilities/CVE-2023-37379/65002", "specs": [ "<2.7.0" ], "v": "<2.7.0" }, { "advisory": "Apache-airflow 2.7.0 disables support for the deserialize flag by default in the 'xcomEntries' API. This was an unsafe default, as deserialization may instantiates arbitrary objects.\r\nhttps://github.com/apache/airflow/pull/32176", "cve": "PVE-2023-60962", "id": "pyup.io-60962", "more_info_path": "/vulnerabilities/PVE-2023-60962/60962", "specs": [ "<2.7.0" ], "v": "<2.7.0" }, { "advisory": "Apache-airflow 2.7.0 disables default allowing the testing of connections in UI, API and CLI for security reasons.\r\nhttps://github.com/apache/airflow/pull/32052", "cve": "PVE-2023-60952", "id": "pyup.io-60952", "more_info_path": "/vulnerabilities/PVE-2023-60952/60952", "specs": [ "<2.7.0" ], "v": "<2.7.0" }, { "advisory": "A session fixation vulnerability allows authenticated users to continue accessing Airflow webserver even after the password of the user has been reset by the admin - up until the expiry of the session of the user. Other than manually cleaning the session database (for database session backend), or changing the secure_key and restarting the webserver, there were no mechanisms to force-logout the user (and all other users with that). With this fix implemented, when using the database session backend, the existing sessions of the user are invalidated when the password of the user is reset. When using the securecookie session backend, the sessions are NOT invalidated and still require changing the secure key and restarting the webserver (and logging out all other users), but the user resetting the password is informed about it with a flash message warning displayed in the UI. Documentation is also updated explaining this behavior.", "cve": "CVE-2023-40273", "id": "pyup.io-65797", "more_info_path": "/vulnerabilities/CVE-2023-40273/65797", "specs": [ "<2.7.0" ], "v": "<2.7.0" }, { "advisory": "Apache Airflow, versions before 2.7.1, is affected by a vulnerability that allows authenticated and DAG-view authorized Users to modify some DAG run detail values when submitting notes. This could have them alter details such as configuration parameters, start date, etc. Users should upgrade to version 2.7.1 or later which has removed the vulnerability.", "cve": "CVE-2023-40611", "id": "pyup.io-65394", "more_info_path": "/vulnerabilities/CVE-2023-40611/65394", "specs": [ "<2.7.1" ], "v": "<2.7.1" }, { "advisory": "Apache Airflow, versions before 2.7.1, is affected by a vulnerability that allows authenticated\u00a0users who have access to see the task/dag in the UI, to craft a URL, which could lead to unmasking the secret configuration of the task that otherwise would be masked in the UI.", "cve": "CVE-2023-40712", "id": "pyup.io-65521", "more_info_path": "/vulnerabilities/CVE-2023-40712/65521", "specs": [ "<2.7.1" ], "v": "<2.7.1" }, { "advisory": "Apache Airflow, versions before 2.7.2, has a vulnerability that allows an authorized user who has access to read specific DAGs only, to read information about task instances in other DAGs. Users of Apache Airflow are advised to upgrade to version 2.7.2 or newer to mitigate the risk associated with this vulnerability", "cve": "CVE-2023-42663", "id": "pyup.io-65393", "more_info_path": "/vulnerabilities/CVE-2023-42663/65393", "specs": [ "<2.7.2" ], "v": "<2.7.2" }, { "advisory": "Apache Airflow, in versions prior to 2.7.2, contains a security vulnerability that allows an authenticated user with limited access to some DAGs, to craft a request that could give the user write access to various DAG resources for DAGs that the user had no access to, thus, enabling the user to clear DAGs they shouldn't. Users of Apache Airflow are strongly advised to upgrade to version 2.7.2 or newer to mitigate the risk associated with this vulnerability.", "cve": "CVE-2023-42792", "id": "pyup.io-65390", "more_info_path": "/vulnerabilities/CVE-2023-42792/65390", "specs": [ "<2.7.2" ], "v": "<2.7.2" }, { "advisory": "A security flaw in Apache Airflow allows authenticated users to view warnings and related details for all Directed Acyclic Graphs (DAGs), including those they are not permitted to see. This exposure includes DAG IDs and stack traces from import errors, posing a risk to versions of Apache Airflow before 2.7.2.", "cve": "CVE-2023-42780", "id": "pyup.io-65392", "more_info_path": "/vulnerabilities/CVE-2023-42780/65392", "specs": [ "<2.7.2" ], "v": "<2.7.2" }, { "advisory": "Apache Airflow, versions before 2.7.3, has a vulnerability that allows an authorized user who has access to read specific DAGs only, to read information about task instances in other DAGs.\u00a0 This is a different issue than CVE-2023-42663 but leading to similar outcome.\r\nUsers of Apache Airflow are advised to upgrade to version 2.7.3 or newer to mitigate the risk associated with this vulnerability.", "cve": "CVE-2023-42781", "id": "pyup.io-65391", "more_info_path": "/vulnerabilities/CVE-2023-42781/65391", "specs": [ "<2.7.3" ], "v": "<2.7.3" }, { "advisory": "Apache Airflow, versions before 2.7.3, is affected by a vulnerability that allows authenticated and DAG-view authorized Users to modify some DAG run detail values when submitting notes. This could have them alter details such as configuration parameters, start date, etc. Users should upgrade to version 2.7.3 or later which has removed the vulnerability.", "cve": "CVE-2023-47037", "id": "pyup.io-65387", "more_info_path": "/vulnerabilities/CVE-2023-47037/65387", "specs": [ "<2.7.3" ], "v": "<2.7.3" }, { "advisory": "Affected versions of Apache Airflow allow authenticated Ops and Viewers users to view all information on audit logs, including dag names and usernames they were not permitted to view.\u00a0In versions 2.8.2 and newer, Ops and Viewer users do not have audit log permission by default, they need to be explicitly granted permissions to see the logs. Only admin users have audit log permission by default.", "cve": "CVE-2024-26280", "id": "pyup.io-68489", "more_info_path": "/vulnerabilities/CVE-2024-26280/68489", "specs": [ "<2.8.2rc1" ], "v": "<2.8.2rc1" }, { "advisory": "Use of Web Browser Cache Containing Sensitive Information vulnerability in Apache Airflow. Airflow did not return \"Cache-Control\" header for dynamic content, which in case of some browsers could result in potentially storing sensitive data in local cache of the browser.", "cve": "CVE-2024-25142", "id": "pyup.io-71856", "more_info_path": "/vulnerabilities/CVE-2024-25142/71856", "specs": [ "<2.9.2" ], "v": "<2.9.2" }, { "advisory": "Affected versions of Apache Airflow have a vulnerability that allows an authenticated attacker to inject a malicious link when installing a provider.", "cve": "CVE-2024-39863", "id": "pyup.io-72254", "more_info_path": "/vulnerabilities/CVE-2024-39863/72254", "specs": [ "<2.9.3" ], "v": "<2.9.3" }, { "advisory": "Affected versions of the Apache Airflow package are vulnerable to Information Disclosure due to proxy URLs with embedded authentication information not being treated as sensitive and therefore not being masked in logs. In affected releases before 3.1.6, the Connection object\u2019s proxies and proxy fields can contain proxy credentials. When these connections are rendered or printed to log output, those credentials may be written in cleartext.", "cve": "CVE-2025-68675", "id": "pyup.io-84601", "more_info_path": "/vulnerabilities/CVE-2025-68675/84601", "specs": [ "<3.1.6" ], "v": "<3.1.6" }, { "advisory": "Apache-airflow 2.3.2 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49787", "more_info_path": "/vulnerabilities/PVE-2021-42852/49787", "specs": [ "<=2.3.2" ], "v": "<=2.3.2" }, { "advisory": "Apache-airflow 2.3.2 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49785", "more_info_path": "/vulnerabilities/PVE-2022-47833/49785", "specs": [ "<=2.3.2" ], "v": "<=2.3.2" }, { "advisory": "Apache-airflow 2.3.2 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49786", "more_info_path": "/vulnerabilities/CVE-2022-29217/49786", "specs": [ "<=2.3.2" ], "v": "<=2.3.2" }, { "advisory": "Affected versions of the apache-airflow package are vulnerable to Information Disclosure due to incorrect enforcement of access controls on sensitive Connection fields. In version 3.0.3, the Connections REST API and webserver UI exposed sensitive connection fields to principals with READ permissions, also bypassing the AIRFLOW__CORE__HIDE_SENSITIVE_VAR_CONN_FIELDS configuration option.", "cve": "CVE-2025-54831", "id": "pyup.io-79991", "more_info_path": "/vulnerabilities/CVE-2025-54831/79991", "specs": [ "==3.0.3" ], "v": "==3.0.3" }, { "advisory": "The LDAP auth backend (airflow.contrib.auth.backends.ldap_auth) prior to Apache Airflow 1.10.1 was misconfigured and contained improper checking of exceptions which disabled server certificate checking.", "cve": "CVE-2018-20245", "id": "pyup.io-54021", "more_info_path": "/vulnerabilities/CVE-2018-20245/54021", "specs": [ ">=0,<1.10.1" ], "v": ">=0,<1.10.1" }, { "advisory": "Affected versions of the Apache Airflow package are vulnerable to Missing Authentication for Critical Function due to an insecure default configuration that permits unauthenticated requests to the Experimental API. In versions before 1.10.11, the web server exposes endpoints under /api/experimental/ without enforcing an authentication backend, allowing arbitrary clients to invoke operations such as POST /api/experimental/dags//dag_runs.", "cve": "CVE-2020-13927", "id": "pyup.io-54436", "more_info_path": "/vulnerabilities/CVE-2020-13927/54436", "specs": [ ">=0,<1.10.11" ], "v": ">=0,<1.10.11" }, { "advisory": "An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attacker can connect to the broker (Redis, RabbitMQ) directly, it is possible to inject commands, resulting in the celery worker running arbitrary commands.", "cve": "CVE-2020-11981", "id": "pyup.io-54177", "more_info_path": "/vulnerabilities/CVE-2020-11981/54177", "specs": [ ">=0,<1.10.11rc1" ], "v": ">=0,<1.10.11rc1" }, { "advisory": "An issue was found in Apache Airflow versions 1.10.10 and below. It was discovered that many of the admin management screens in the new/RBAC UI handled escaping incorrectly, allowing authenticated users with appropriate permissions to create stored XSS attacks.", "cve": "CVE-2020-11983", "id": "pyup.io-54181", "more_info_path": "/vulnerabilities/CVE-2020-11983/54181", "specs": [ ">=0,<1.10.11rc1" ], "v": ">=0,<1.10.11rc1" }, { "advisory": "Apache-airflow 1.10.11rc1 includes a fix for CVE-2020-11978: A remote code/command injection vulnerability was discovered in one of the example DAGs shipped with Airflow which would allow any authenticated user to run arbitrary commands as the user running airflow worker/scheduler (depending on the executor in use). If you already have examples disabled by setting load_examples=False in the config then you are not vulnerable.", "cve": "CVE-2020-11978", "id": "pyup.io-54349", "more_info_path": "/vulnerabilities/CVE-2020-11978/54349", "specs": [ ">=0,<1.10.11rc1" ], "v": ">=0,<1.10.11rc1" }, { "advisory": "An issue was found in Apache Airflow versions 1.10.10 and below. A stored XSS vulnerability was discovered in the Chart pages of the the \"classic\" UI.", "cve": "CVE-2020-9485", "id": "pyup.io-54204", "more_info_path": "/vulnerabilities/CVE-2020-9485/54204", "specs": [ ">=0,<1.10.11rc1" ], "v": ">=0,<1.10.11rc1" }, { "advisory": "An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.", "cve": "CVE-2020-11982", "id": "pyup.io-54179", "more_info_path": "/vulnerabilities/CVE-2020-11982/54179", "specs": [ ">=0,<1.10.11rc1" ], "v": ">=0,<1.10.11rc1" }, { "advisory": "In Airflow versions prior to 1.10.13, when creating a user using airflow CLI, the password gets logged in plain text in the Log table in Airflow Metadatase. Same happened when creating a Connection with a password field.", "cve": "CVE-2020-17511", "id": "pyup.io-54253", "more_info_path": "/vulnerabilities/CVE-2020-17511/54253", "specs": [ ">=0,<1.10.13" ], "v": ">=0,<1.10.13" }, { "advisory": "Incorrect Session Validation in Apache Airflow Webserver versions prior to 1.10.14 with default config allows a malicious airflow user on site A where they log in normally, to access unauthorized Airflow Webserver on Site B through the session from Site A. This does not affect users who have changed the default value for `[webserver] secret_key` config.", "cve": "CVE-2020-17526", "id": "pyup.io-54278", "more_info_path": "/vulnerabilities/CVE-2020-17526/54278", "specs": [ ">=0,<1.10.14" ], "v": ">=0,<1.10.14" }, { "advisory": "In Apache Airflow before 1.10.2, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views.", "cve": "CVE-2018-20244", "id": "pyup.io-54020", "more_info_path": "/vulnerabilities/CVE-2018-20244/54020", "specs": [ ">=0,<1.10.2" ], "v": ">=0,<1.10.2" }, { "advisory": "A number of HTTP endpoints in the Airflow webserver (both RBAC and classic) did not have adequate protection and were vulnerable to cross-site request forgery attacks.", "cve": "CVE-2019-0229", "id": "pyup.io-54127", "more_info_path": "/vulnerabilities/CVE-2019-0229/54127", "specs": [ ">=0,<1.10.3b1" ], "v": ">=0,<1.10.3b1" }, { "advisory": "A malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views.", "cve": "CVE-2019-0216", "id": "pyup.io-54125", "more_info_path": "/vulnerabilities/CVE-2019-0216/54125", "specs": [ ">=0,<1.10.3b1" ], "v": ">=0,<1.10.3b1" }, { "advisory": "In Apache Airflow before 1.10.5 when running with the \"classic\" UI, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. The new \"RBAC\" UI is unaffected.", "cve": "CVE-2019-12398", "id": "pyup.io-54139", "more_info_path": "/vulnerabilities/CVE-2019-12398/54139", "specs": [ ">=0,<1.10.5" ], "v": ">=0,<1.10.5" }, { "advisory": "Versions of Apache Airflow prior to 1.10.5 expose a vulnerability where the Databricks operator logs API keys in plaintext during task execution. This exposure results from the operator encouraging users to input their API key into a connection's \"extra\" field, which the Databricks hook subsequently logs, leading to information exposure.\r\nhttps://github.com/apache/airflow/pull/5635/commits/89f015e6c89392b6de61dab8ab90182e6ee42b74", "cve": "PVE-2024-99796", "id": "pyup.io-66019", "more_info_path": "/vulnerabilities/PVE-2024-99796/66019", "specs": [ ">=0,<1.10.5" ], "v": ">=0,<1.10.5" }, { "advisory": "A malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. This also presented a Local File Disclosure vulnerability to any file readable by the webserver process.", "cve": "CVE-2019-12417", "id": "pyup.io-54143", "more_info_path": "/vulnerabilities/CVE-2019-12417/54143", "specs": [ ">=0,<1.10.6rc1" ], "v": ">=0,<1.10.6rc1" }, { "advisory": "It was noticed an XSS in certain 404 pages that could be exploited to perform an XSS attack. Chrome will detect this as a reflected XSS attempt and prevent the page from loading. Firefox and other browsers don't, and are vulnerable to this attack. Mitigation: The fix for this is to upgrade to Apache Airflow 1.9.0 or above.", "cve": "CVE-2017-12614", "id": "pyup.io-53928", "more_info_path": "/vulnerabilities/CVE-2017-12614/53928", "specs": [ ">=0,<1.9.0" ], "v": ">=0,<1.9.0" }, { "advisory": "In Apache Airflow 1.8.2 and earlier, a CSRF vulnerability allowed for a remote command injection on a default install of Airflow.", "cve": "CVE-2017-17835", "id": "pyup.io-53948", "more_info_path": "/vulnerabilities/CVE-2017-17835/53948", "specs": [ ">=0,<1.9.0" ], "v": ">=0,<1.9.0" }, { "advisory": "In Apache Airflow 1.8.2 and earlier, an authenticated user can execute code remotely on the Airflow webserver by creating a special object.\r\nhttps://github.com/apache/airflow/pull/2132", "cve": "CVE-2017-15720", "id": "pyup.io-53938", "more_info_path": "/vulnerabilities/CVE-2017-15720/53938", "specs": [ ">=0,<1.9.0" ], "v": ">=0,<1.9.0" }, { "advisory": "In Apache Airflow 1.8.2 and earlier, an experimental Airflow feature displayed authenticated cookies, as well as passwords to databases used by Airflow. An attacker who has limited access to airflow, whether it be via XSS or by leaving a machine unlocked can exfiltrate all credentials from the system.", "cve": "CVE-2017-17836", "id": "pyup.io-53950", "more_info_path": "/vulnerabilities/CVE-2017-17836/53950", "specs": [ ">=0,<1.9.0" ], "v": ">=0,<1.9.0" }, { "advisory": "In Apache Airflow, prior to version 2.2.4, some example DAGs did not properly sanitize user-provided params, making them susceptible to OS Command Injection from the web UI.", "cve": "CVE-2022-24288", "id": "pyup.io-54244", "more_info_path": "/vulnerabilities/CVE-2022-24288/54244", "specs": [ ">=0,<2.2.4" ], "v": ">=0,<2.2.4" }, { "advisory": "It was discovered that the \"Trigger DAG with config\" screen was susceptible to XSS attacks via the `origin` query argument. This issue affects Apache Airflow versions 2.2.3 and below.", "cve": "CVE-2021-45229", "id": "pyup.io-54261", "more_info_path": "/vulnerabilities/CVE-2021-45229/54261", "specs": [ ">=0,<2.2.4rc1" ], "v": ">=0,<2.2.4rc1" }, { "advisory": "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Apache Airflow Hive Provider, Apache Airflow allows an attacker to execute arbtrary commands in the task execution context, without write access to DAG files. This issue affects Hive Provider versions prior to 4.1.0. It also impacts any Apache Airflow versions prior to 2.3.0 in case HIve Provider is installed (Hive Provider 4.1.0 can only be installed for Airflow 2.3.0+). Note that you need to manually install the HIve Provider version 4.1.0 in order to get rid of the vulnerability on top of Airflow 2.3.0+ version that has lower version of the Hive Provider installed).", "cve": "CVE-2022-41131", "id": "pyup.io-54592", "more_info_path": "/vulnerabilities/CVE-2022-41131/54592", "specs": [ ">=0,<2.3.0" ], "v": ">=0,<2.3.0" }, { "advisory": "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Apache Airflow Pinot Provider, Apache Airflow allows an attacker to control commands executed in the task execution context, without write access to DAG files. This issue affects Apache Airflow Pinot Provider versions prior to 4.0.0. It also impacts any Apache Airflow versions prior to 2.3.0 in case Apache Airflow Pinot Provider is installed (Apache Airflow Pinot Provider 4.0.0 can only be installed for Airflow 2.3.0+). Note that you need to manually install the Pinot Provider version 4.0.0 in order to get rid of the vulnerability on top of Airflow 2.3.0+ version.", "cve": "CVE-2022-38649", "id": "pyup.io-54586", "more_info_path": "/vulnerabilities/CVE-2022-38649/54586", "specs": [ ">=0,<2.3.0" ], "v": ">=0,<2.3.0" }, { "advisory": "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Apache Airflow Spark Provider, Apache Airflow allows an attacker to read arbtrary files in the task execution context, without write access to DAG files. This issue affects Spark Provider versions prior to 4.0.0. It also impacts any Apache Airflow versions prior to 2.3.0 in case Spark Provider is installed (Spark Provider 4.0.0 can only be installed for Airflow 2.3.0+). Note that you need to manually install the Spark Provider version 4.0.0 in order to get rid of the vulnerability on top of Airflow 2.3.0+ version that has lower version of the Spark Provider installed).", "cve": "CVE-2022-40954", "id": "pyup.io-54588", "more_info_path": "/vulnerabilities/CVE-2022-40954/54588", "specs": [ ">=0,<2.3.0" ], "v": ">=0,<2.3.0" }, { "advisory": "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Apache Airflow Pig Provider, Apache Airflow allows an attacker to control commands executed in the task execution context, without write access to DAG files. This issue affects Pig Provider versions prior to 4.0.0. It also impacts any Apache Airflow versions prior to 2.3.0 in case Pig Provider is installed (Pig Provider 4.0.0 can only be installed for Airflow 2.3.0+). Note that you need to manually install the Pig Provider version 4.0.0 in order to get rid of the vulnerability on top of Airflow 2.3.0+ version.", "cve": "CVE-2022-40189", "id": "pyup.io-54587", "more_info_path": "/vulnerabilities/CVE-2022-40189/54587", "specs": [ ">=0,<2.3.0" ], "v": ">=0,<2.3.0" }, { "advisory": "A vulnerability in UI of Apache Airflow allows an attacker to view unmasked secrets in rendered template values for tasks which were not executed (for example when they were depending on past and previous instances of the task failed). This issue affects Apache Airflow prior to 2.3.1.", "cve": "CVE-2022-27949", "id": "pyup.io-54578", "more_info_path": "/vulnerabilities/CVE-2022-27949/54578", "specs": [ ">=0,<2.3.1" ], "v": ">=0,<2.3.1" }, { "advisory": "In Apache Airflow prior to 2.3.4, an insecure umask was configured for numerous Airflow components when running with the '--daemon' flag which could result in a race condition giving world-writable files in the Airflow home directory and allowing local users to expose arbitrary file contents via the webserver.", "cve": "CVE-2022-38170", "id": "pyup.io-54525", "more_info_path": "/vulnerabilities/CVE-2022-38170/54525", "specs": [ ">=0,<2.3.4" ], "v": ">=0,<2.3.4" }, { "advisory": "A vulnerability in Example Dags of Apache Airflow allows an attacker with UI access who can trigger DAGs, to execute arbitrary commands via manually provided run_id parameter. This issue affects Apache Airflow versions prior to 2.4.0.", "cve": "CVE-2022-40127", "id": "pyup.io-54577", "more_info_path": "/vulnerabilities/CVE-2022-40127/54577", "specs": [ ">=0,<2.4.0" ], "v": ">=0,<2.4.0" }, { "advisory": "In Apache Airflow, prior to version 2.4.1, deactivating a user wouldn't prevent an already authenticated user from being able to continue using the UI or API.", "cve": "CVE-2022-41672", "id": "pyup.io-54508", "more_info_path": "/vulnerabilities/CVE-2022-41672/54508", "specs": [ ">=0,<2.4.1" ], "v": ">=0,<2.4.1" }, { "advisory": "In Apache Airflow versions prior to 2.4.2, the \"Trigger DAG with config\" screen was susceptible to XSS attacks via the `origin` query argument.", "cve": "CVE-2022-43982", "id": "pyup.io-54568", "more_info_path": "/vulnerabilities/CVE-2022-43982/54568", "specs": [ ">=0,<2.4.2" ], "v": ">=0,<2.4.2" }, { "advisory": "In Apache Airflow versions prior to 2.4.2, there was an open redirect in the webserver's `/confirm` endpoint.", "cve": "CVE-2022-43985", "id": "pyup.io-54567", "more_info_path": "/vulnerabilities/CVE-2022-43985/54567", "specs": [ ">=0,<2.4.2" ], "v": ">=0,<2.4.2" }, { "advisory": "In Apache Airflow versions prior to 2.4.3, there was an open redirect in the webserver's `/login` endpoint.", "cve": "CVE-2022-45402", "id": "pyup.io-54582", "more_info_path": "/vulnerabilities/CVE-2022-45402/54582", "specs": [ ">=0,<2.4.3" ], "v": ">=0,<2.4.3" }, { "advisory": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Apache Software Foundation Apache Airflow, Apache Software Foundation Apache Airflow MySQL Provider. This issue affects Apache Airflow before 2.5.1 and Apache Airflow MySQL Provider before 4.0.0.", "cve": "CVE-2023-22884", "id": "pyup.io-54620", "more_info_path": "/vulnerabilities/CVE-2023-22884/54620", "specs": [ ">=0,<2.5.1" ], "v": ">=0,<2.5.1" }, { "advisory": "Generation of Error Message Containing Sensitive Information vulnerability in Apache Software Foundation Apache Airflow.This issue affects Apache Airflow: before 2.5.2. The traceback contains information that might be useful for a potential attacker to better target their attack (Python/Airflow version, node name). This information should not be shown if traceback is shown to unauthenticated user.", "cve": "CVE-2023-25695", "id": "pyup.io-54667", "more_info_path": "/vulnerabilities/CVE-2023-25695/54667", "specs": [ ">=0,<2.5.2" ], "v": ">=0,<2.5.2" }, { "advisory": "Apache Airflow, versions before 2.6.3, is affected by a vulnerability that allows unauthorized read access to a DAG through the URL. It is recommended to upgrade to a version that is not affected.", "cve": "PVE-2024-99905", "id": "pyup.io-64688", "more_info_path": "/vulnerabilities/PVE-2024-99905/64688", "specs": [ ">=0,<2.6.3" ], "v": ">=0,<2.6.3" }, { "advisory": "Apache Airflow, in versions before 2.8.0, contains a security vulnerability that allows an authenticated user with limited access to some DAGs, to craft a request that could give the user write access to various DAG resources for DAGs that the user had no access to, thus, enabling the user to clear DAGs they shouldn't. This is a missing fix for CVE-2023-42792 in Apache Airflow 2.7.2\u00a0Users of Apache Airflow are strongly advised to upgrade to version 2.8.0 or newer to mitigate the risk associated with this vulnerability.", "cve": "CVE-2023-48291", "id": "pyup.io-65191", "more_info_path": "/vulnerabilities/CVE-2023-48291/65191", "specs": [ ">=0,<2.8.0b1" ], "v": ">=0,<2.8.0b1" }, { "advisory": "Apache Airflow, versions before 2.8.0, is affected by a vulnerability that allows an authenticated user without the variable edit permission, to update a variable. This flaw compromises the integrity of variable management, potentially leading to unauthorized data modification.", "cve": "CVE-2023-50783", "id": "pyup.io-65201", "more_info_path": "/vulnerabilities/CVE-2023-50783/65201", "specs": [ ">=0,<2.8.0b1" ], "v": ">=0,<2.8.0b1" }, { "advisory": "Apache Airflow, versions before 2.8.1, have a vulnerability that allows an authenticated user to access the source code of a DAG to which they don't have access. This vulnerability is considered low since it requires an authenticated user to exploit it. Users are recommended to upgrade to version 2.8.1, which fixes this issue.", "cve": "CVE-2023-50944", "id": "pyup.io-65265", "more_info_path": "/vulnerabilities/CVE-2023-50944/65265", "specs": [ ">=0,<2.8.1rc1" ], "v": ">=0,<2.8.1rc1" }, { "advisory": "Apache Airflow, versions before 2.8.1, have a vulnerability that allows a potential attacker to poison the XCom data by bypassing the protection of \"enable_xcom_pickling=False\" configuration setting resulting in poisoned data after XCom deserialization. This vulnerability is considered low since it requires a DAG author to exploit it. Users are recommended to upgrade to version 2.8.1 or later, which fixes this issue.", "cve": "CVE-2023-50943", "id": "pyup.io-65264", "more_info_path": "/vulnerabilities/CVE-2023-50943/65264", "specs": [ ">=0,<2.8.1rc1" ], "v": ">=0,<2.8.1rc1" }, { "advisory": "Apache Airflow, versions before 2.8.2, has a vulnerability that allows authenticated users to view DAG code and import errors of DAGs they do not have permission to view through the API and the UI. Users of Apache Airflow are recommended to upgrade to version 2.8.2 or newer to mitigate the risk associated with this vulnerability", "cve": "CVE-2024-27906", "id": "pyup.io-68475", "more_info_path": "/vulnerabilities/CVE-2024-27906/68475", "specs": [ ">=0,<2.8.2" ], "v": ">=0,<2.8.2" }, { "advisory": "Apache-airflow 1.10.15 and 2.0.2 include a fix for CVE-2021-28359: The \"origin\" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. This issue affects Apache Airflow versions <1.10.15 in 1.x series and affects 2.0.0 and 2.0.1 and 2.x series. This is the same as CVE-2020-13944 & CVE-2020-17515 but the implemented fix did not fix the issue completely. Update to Airflow 1.10.15 or 2.0.2. Please also update your Python version to the latest available PATCH releases of the installed MINOR versions, example update to Python 3.6.13 if you are on Python 3.6. (Those contain the fix for CVE-2021-23336 https://nvd.nist.gov/vuln/detail/CVE-2021-23336).", "cve": "CVE-2021-28359", "id": "pyup.io-40341", "more_info_path": "/vulnerabilities/CVE-2021-28359/40341", "specs": [ ">=1.0.0a1,<1.10.15", ">=2.0.0a1,<2.0.2" ], "v": ">=1.0.0a1,<1.10.15,>=2.0.0a1,<2.0.2" }, { "advisory": "In Apache Airflow prior to 2.2.0. This CVE applies to a specific case where a User who has \"can_create\" permissions on DAG Runs can create Dag Runs for dags that they don't have \"edit\" permissions for.", "cve": "CVE-2021-45230", "id": "pyup.io-54733", "more_info_path": "/vulnerabilities/CVE-2021-45230/54733", "specs": [ ">=1.10.0,<2.0.0b1", ">=2.0.0,<2.2.0" ], "v": ">=1.10.0,<2.0.0b1,>=2.0.0,<2.2.0" }, { "advisory": "Insertion of Sensitive Information into Log File vulnerability in Apache Airflow Celery provider, Apache Airflow. Sensitive information logged as clear text when rediss, amqp, rpc protocols are used as Celery result backend Note: the vulnerability is about the information exposed in the logs not about accessing the logs. This issue affects Apache Airflow Celery provider: from 3.3.0 through 3.4.0; Apache Airflow: from 1.10.0 through 2.6.3. Users are recommended to upgrade Airflow Celery provider to version 3.4.1 and Apache Airlfow to version 2.7.0 which fixes the issue.", "cve": "CVE-2023-46215", "id": "pyup.io-65388", "more_info_path": "/vulnerabilities/CVE-2023-46215/65388", "specs": [ ">=1.10.0,<2.7.0" ], "v": ">=1.10.0,<2.7.0" }, { "advisory": "The lineage endpoint of the deprecated Experimental API was not protected by authentication in Airflow 2.0.0. This allowed unauthenticated users to hit that endpoint. This is low-severity issue as the attacker needs to be aware of certain parameters to pass to that endpoint and even after can just get some metadata about a DAG and a Task. This issue only affects Apache Airflow 2.0.0.", "cve": "CVE-2021-26697", "id": "pyup.io-54461", "more_info_path": "/vulnerabilities/CVE-2021-26697/54461", "specs": [ ">=2.0.0,<2.0.1" ], "v": ">=2.0.0,<2.0.1" }, { "advisory": "Improper Access Control on Configurations Endpoint for the Stable API of Apache Airflow allows users with Viewer or User role to get Airflow Configurations including sensitive information even when `[webserver] expose_config` is set to `False` in `airflow.cfg`. This allowed a privilege escalation attack. This issue affects Apache Airflow 2.0.0.", "cve": "CVE-2021-26559", "id": "pyup.io-54168", "more_info_path": "/vulnerabilities/CVE-2021-26559/54168", "specs": [ ">=2.0.0,<2.0.1" ], "v": ">=2.0.0,<2.0.1" }, { "advisory": "The variable import endpoint was not protected by authentication in Airflow >=2.0.0, <2.1.3. This allowed unauthenticated users to hit that endpoint to add/modify Airflow variables used in DAGs, potentially resulting in a denial of service, information disclosure or remote code execution. This issue affects Apache Airflow >=2.0.0, <2.1.3.", "cve": "CVE-2021-38540", "id": "pyup.io-54319", "more_info_path": "/vulnerabilities/CVE-2021-38540/54319", "specs": [ ">=2.0.0,<2.1.3" ], "v": ">=2.0.0,<2.1.3" }, { "advisory": "Example DAG: example_inlet_event_extra.py shipped with Apache Airflow version 2.10.0 has a vulnerability that allows an authenticated attacker with only DAG trigger permission to execute arbitrary commands. If you used that example as the base of your DAGs - please review if you have not copied the dangerous example; see https://github.com/apache/airflow/pull/41873 for more information. We recommend against exposing the example DAGs in your deployment. If you must expose the example DAGs, upgrade Airflow to version 2.10.1 or later.", "cve": "CVE-2024-45498", "id": "pyup.io-73187", "more_info_path": "/vulnerabilities/CVE-2024-45498/73187", "specs": [ ">=2.10.0b1,<2.10.1" ], "v": ">=2.10.0b1,<2.10.1" }, { "advisory": "In Apache Airflow versions 2.2.4 through 2.3.3, the `database` webserver session backend was susceptible to session fixation.", "cve": "CVE-2022-38054", "id": "pyup.io-54522", "more_info_path": "/vulnerabilities/CVE-2022-38054/54522", "specs": [ ">=2.2.4,<2.3.4rc1" ], "v": ">=2.2.4,<2.3.4rc1" }, { "advisory": "In Apache Airflow 2.3.0 through 2.3.4, part of a url was unnecessarily formatted, allowing for possible information extraction.", "cve": "CVE-2022-40604", "id": "pyup.io-54551", "more_info_path": "/vulnerabilities/CVE-2022-40604/54551", "specs": [ ">=2.3.0,<2.4.0b1" ], "v": ">=2.3.0,<2.4.0b1" }, { "advisory": "In Apache Airflow 2.3.0 through 2.3.4, there was an open redirect in the webserver's `/confirm` endpoint.", "cve": "CVE-2022-40754", "id": "pyup.io-54715", "more_info_path": "/vulnerabilities/CVE-2022-40754/54715", "specs": [ ">=2.3.0,<2.4.0b1" ], "v": ">=2.3.0,<2.4.0b1" }, { "advisory": "A vulnerability has been identified in versions of Airflow where, by using deferrable mode and a Kubernetes configuration file for authentication, the Airflow worker sends this configuration as an unencrypted dictionary to the triggerer, storing it in metadata. This process, coupled with certain Airflow versions, also results in the unmasked logging of the configuration dictionary in the triggerer service. Consequently, unauthorized individuals could potentially access and exploit the Kubernetes cluster using the exposed configuration details.", "cve": "CVE-2023-51702", "id": "pyup.io-65395", "more_info_path": "/vulnerabilities/CVE-2023-51702/65395", "specs": [ ">=2.3.0,<2.6.1" ], "v": ">=2.3.0,<2.6.1" }, { "advisory": "Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Airflow.This issue affects Apache Airflow from 2.4.0 to 2.7.0. Sensitive configuration information has been exposed to authenticated users with the ability to read configuration via Airflow REST API for configuration even when the expose_config option is set to non-sensitive-only. The expose_config option is False by default. It is recommended to upgrade to a version that is not affected if you set expose_config to non-sensitive-only configuration. This is a different error than CVE-2023-45348 which allows authenticated user to retrieve individual configuration values in 2.7.* by specially crafting their request (solved in 2.7.2). Users are recommended to upgrade to version 2.7.2, which fixes the issue and additionally fixes CVE-2023-45348.", "cve": "CVE-2023-46288", "id": "pyup.io-65796", "more_info_path": "/vulnerabilities/CVE-2023-46288/65796", "specs": [ ">=2.4.0,<2.7.0" ], "v": ">=2.4.0,<2.7.0" }, { "advisory": "Affected versions of Apache Airflow have a vulnerability that allows authenticated DAG authors to craft a doc_md parameter in a way that could execute arbitrary code in the scheduler context, which should be forbidden according to the Airflow Security model.", "cve": "CVE-2024-39877", "id": "pyup.io-72253", "more_info_path": "/vulnerabilities/CVE-2024-39877/72253", "specs": [ ">=2.4.0,<2.9.3" ], "v": ">=2.4.0,<2.9.3" }, { "advisory": "In Apache Airflow, some potentially sensitive values were being shown to the user in certain situations.\r\n\r\nThis vulnerability is mitigated by the fact configuration is not shown in the UI by default (only if `[webserver] expose_config` is set to `non-sensitive-only`), and not all uncensored values are actually sentitive.\r\n\r\nThis issue affects Apache Airflow: from 2.5.0 before 2.6.2. Users are recommended to update to version 2.6.2 or later.", "cve": "CVE-2023-35005", "id": "pyup.io-64198", "more_info_path": "/vulnerabilities/CVE-2023-35005/64198", "specs": [ ">=2.5.0,<2.6.2" ], "v": ">=2.5.0,<2.6.2" }, { "advisory": "Apache Airflow, versions 2.6.0 through 2.7.3 has a stored XSS vulnerability that allows a DAG author to add an unbounded and not-sanitized javascript in the parameter description field of the DAG. This Javascript can be executed on the client side of any of the user who looks at the tasks in the browser sandbox. While this issue does not allow to exit the browser sandbox or manipulation of the server-side data - more than the DAG author already has, it allows to modify what the user looking at the DAG details sees in the browser - which opens up all kinds of possibilities of misleading other users. Users of Apache Airflow are recommended to upgrade to version 2.8.0 or newer to mitigate the risk associated with this vulnerability", "cve": "CVE-2023-47265", "id": "pyup.io-65188", "more_info_path": "/vulnerabilities/CVE-2023-47265/65188", "specs": [ ">=2.6.0,<2.8.0b1" ], "v": ">=2.6.0,<2.8.0b1" }, { "advisory": "Apache Airflow, versions 2.7.0 and 2.7.1, is affected by a vulnerability that allows an authenticated user to retrieve sensitive configuration information when the \"expose_config\" option is set to \"non-sensitive-only\". The `expose_config` option is False by default. It is recommended to upgrade to a version that is not affected.", "cve": "CVE-2023-45348", "id": "pyup.io-65389", "more_info_path": "/vulnerabilities/CVE-2023-45348/65389", "specs": [ ">=2.7.0,<2.7.2" ], "v": ">=2.7.0,<2.7.2" }, { "advisory": "Apache Airflow, version 2.7.0 through 2.7.3, has a vulnerability that allows an attacker to trigger a DAG in a GET request without CSRF validation.\u00a0As a result, it was possible for a malicious website opened in the same browser - by the user who also had Airflow UI opened - to trigger the execution of DAGs without the user's consent. Users are advised to upgrade to version 2.8.0 or later which is not affected", "cve": "CVE-2023-49920", "id": "pyup.io-65198", "more_info_path": "/vulnerabilities/CVE-2023-49920/65198", "specs": [ ">=2.7.0,<2.8.0" ], "v": ">=2.7.0,<2.8.0" }, { "advisory": "Airflow versions affected versions have a vulnerability that allows an authenticated user to see sensitive provider configuration via the \"configuration\" UI page when \"non-sensitive-only\" was set as \"webserver.expose_config\" configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your \"expose_config\" configuration to False as a workaround. This is similar, but different to CVE-2023-46288 which concerned API, not UI configuration page.", "cve": "CVE-2024-31869", "id": "pyup.io-71686", "more_info_path": "/vulnerabilities/CVE-2024-31869/71686", "specs": [ ">=2.7.0b1,<2.9" ], "v": ">=2.7.0b1,<2.9" }, { "advisory": "Affected versions of Apache Airflow have a vulnerability that allows an authenticated user with limited permissions to access resources such as variables, connections, etc, from the UI which they do not have permission to access.", "cve": "CVE-2024-28746", "id": "pyup.io-71633", "more_info_path": "/vulnerabilities/CVE-2024-28746/71633", "specs": [ ">=2.8.0b1,<2.8.3rc1" ], "v": ">=2.8.0b1,<2.8.3rc1" }, { "advisory": "Affected versions of Apache Airflow are vulnerable to an improper preservation of permissions vulnerability. This issue causes the local file task handler to incorrectly set write permissions on all parent folders of the log directory, potentially exposing sensitive directories and disrupting SSH operations when logs reside in home directories. The attack vector exploits misconfigured permission settings in non-containerized deployments, especially when running as root with a restrictive umask. Mitigation involves upgrading to Apache Airflow 2.8.4, using a non-root user, or changing the file_task_handler_new_folder_permissions configuration to 0o755.", "cve": "CVE-2024-29735", "id": "pyup.io-71685", "more_info_path": "/vulnerabilities/CVE-2024-29735/71685", "specs": [ ">=2.8.2rc1,<2.8.4" ], "v": ">=2.8.2rc1,<2.8.4" }, { "advisory": "Apache Airflow affected versions have a vulnerability that allows an authenticated attacker to inject malicious data into the task instance logs.", "cve": "CVE-2024-32077", "id": "pyup.io-71634", "more_info_path": "/vulnerabilities/CVE-2024-32077/71634", "specs": [ ">=2.9.0b1,<2.9.1" ], "v": ">=2.9.0b1,<2.9.1" }, { "advisory": "Affected versions of the apache-airflow package are vulnerable to Command Injection due to a non-validated parameter in the example_dag_decorator example DAG. The example_dag_decorator accepts a user-controlled server target from the Airflow UI and incorporates it into an operating-system command on a worker without proper neutralization (CWE-78).", "cve": "CVE-2025-54941", "id": "pyup.io-80990", "more_info_path": "/vulnerabilities/CVE-2025-54941/80990", "specs": [ ">=3.0.0b4,<3.0.5" ], "v": ">=3.0.0b4,<3.0.5" }, { "advisory": "Affected versions of the apache-airflow package are vulnerable to Remote Code Execution due to the /api/v2/dagReports endpoint importing DAG files via DagBag and executing DAG Python within the API server process. The dagReports handler loads user DAGs with airflow.models.dagbag.DagBag instead of the non-executing DBDagBag, causing import-time module code from DAG files to run whenever the API server has access to the DAG directory.", "cve": "CVE-2025-62402", "id": "pyup.io-80989", "more_info_path": "/vulnerabilities/CVE-2025-62402/80989", "specs": [ ">=3.0.0b4,<3.1.1" ], "v": ">=3.0.0b4,<3.1.1" }, { "advisory": "Affected versions of the apache-airflow package are vulnerable to Improper Access Control due to missing authorization checks in the bulk create API\u2019s overwrite action for Pools, Connections, and Variables. The bulk create operation permits upsert behaviour when the overwrite flag is set, allowing modification of existing records even when the caller holds only CREATE permission and lacks UPDATE privileges.", "cve": "CVE-2025-62503", "id": "pyup.io-81133", "more_info_path": "/vulnerabilities/CVE-2025-62503/81133", "specs": [ ">=3.0.0b4,<3.1.1" ], "v": ">=3.0.0b4,<3.1.1" }, { "advisory": "Affected versions of the Apache Airflow package are vulnerable to Information Disclosure due to incomplete secret masking during rendered template field serialization. When a DAG\u2019s rendered template fields exceed the [core] max_templated_field_length limit, the Rendered Templates UI displays a truncated serialized value that was processed with a secrets masker instance that does not include user-registered mask_secret() patterns, so sensitive substrings may remain in cleartext.", "cve": "CVE-2025-68438", "id": "pyup.io-84602", "more_info_path": "/vulnerabilities/CVE-2025-68438/84602", "specs": [ ">=3.1.0,<3.1.6" ], "v": ">=3.1.0,<3.1.6" } ], "apache-airflow-backport-providers-amazon": [ { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-35936", "id": "pyup.io-49920", "more_info_path": "/vulnerabilities/CVE-2021-35936/49920", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49928", "more_info_path": "/vulnerabilities/PVE-2022-47833/49928", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49929", "more_info_path": "/vulnerabilities/CVE-2022-29217/49929", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (urllib3 == 1.25.11).", "cve": "CVE-2021-33503", "id": "pyup.io-49927", "more_info_path": "/vulnerabilities/CVE-2021-33503/49927", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2020-7753", "id": "pyup.io-49914", "more_info_path": "/vulnerabilities/CVE-2020-7753/49914", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-29621", "id": "pyup.io-49921", "more_info_path": "/vulnerabilities/CVE-2021-29621/49921", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62919", "more_info_path": "/vulnerabilities/CVE-2023-25754/62919", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-23445", "id": "pyup.io-49918", "more_info_path": "/vulnerabilities/CVE-2021-23445/49918", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-41265", "id": "pyup.io-49924", "more_info_path": "/vulnerabilities/CVE-2021-41265/49924", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-21659", "id": "pyup.io-49925", "more_info_path": "/vulnerabilities/CVE-2022-21659/49925", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-24776", "id": "pyup.io-49922", "more_info_path": "/vulnerabilities/CVE-2022-24776/49922", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (flask-caching == 1.3.3).", "cve": "CVE-2021-33026", "id": "pyup.io-49926", "more_info_path": "/vulnerabilities/CVE-2021-33026/49926", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon <=2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-33502", "id": "pyup.io-49919", "more_info_path": "/vulnerabilities/CVE-2021-33502/49919", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-32805", "id": "pyup.io-49923", "more_info_path": "/vulnerabilities/CVE-2021-32805/49923", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37713", "id": "pyup.io-49917", "more_info_path": "/vulnerabilities/CVE-2021-37713/49917", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37712", "id": "pyup.io-49916", "more_info_path": "/vulnerabilities/CVE-2021-37712/49916", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-amazon 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37701", "id": "pyup.io-49915", "more_info_path": "/vulnerabilities/CVE-2021-37701/49915", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-apache-beam": [ { "advisory": "apache-airflow-backport-providers-apache-beam 2021.3.13 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62920", "more_info_path": "/vulnerabilities/CVE-2023-25754/62920", "specs": [ "<=2021.3.13" ], "v": "<=2021.3.13" } ], "apache-airflow-backport-providers-apache-hive": [ { "advisory": "apache-airflow-backport-providers-apache-hive 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62921", "more_info_path": "/vulnerabilities/CVE-2023-25754/62921", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-apache-hive is affected by CVE-2023-28706.", "cve": "CVE-2023-28706", "id": "pyup.io-59570", "more_info_path": "/vulnerabilities/CVE-2023-28706/59570", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-apache-pinot": [ { "advisory": "apache-airflow-backport-providers-apache-pinot 2020.11.23 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62923", "more_info_path": "/vulnerabilities/CVE-2023-25754/62923", "specs": [ "<=2020.11.23" ], "v": "<=2020.11.23" } ], "apache-airflow-backport-providers-apache-spark": [ { "advisory": "Apache-airflow-backport-providers-apache-spark is affected by CVE-2023-28710.", "cve": "CVE-2023-28710", "id": "pyup.io-59572", "more_info_path": "/vulnerabilities/CVE-2023-28710/59572", "specs": [ "<4.0.1" ], "v": "<4.0.1" }, { "advisory": "Apache airflow backport providers apache spark, versions before 4.1.3, is affected by a vulnerability that allows an attacker to pass in malicious parameters when establishing a connection allowing reading files on the Airflow server.", "cve": "CVE-2023-40272", "id": "pyup.io-65223", "more_info_path": "/vulnerabilities/CVE-2023-40272/65223", "specs": [ "<4.1.3" ], "v": "<4.1.3" }, { "advisory": "Apache-airflow-backport-providers-apache-spark is affected by CVE-2023-40195: Deserialization of Untrusted Data, Inclusion of Functionality from Untrusted Control Sphere vulnerability in Apache Software Foundation Apache Airflow Spark Provider.\r\nWhen the Apache Spark provider is installed on an Airflow deployment, an Airflow user that is authorized to configure Spark hooks can effectively run arbitrary code on the Airflow node by pointing it at a malicious Spark server. Prior to version 4.1.3, this was not called out in the documentation explicitly, so it is possible that administrators provided authorizations to configure Spark hooks without taking this into account. We recommend administrators to review their configurations to make sure the authorization to configure Spark hooks is only provided to fully trusted users.\r\nhttps://airflow.apache.org/docs/apache-airflow-providers-apache-spark/4.1.3/connections/spark.html", "cve": "CVE-2023-40195", "id": "pyup.io-63167", "more_info_path": "/vulnerabilities/CVE-2023-40195/63167", "specs": [ ">=0" ], "v": ">=0" } ], "apache-airflow-backport-providers-cncf-kubernetes": [ { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-21659", "id": "pyup.io-49941", "more_info_path": "/vulnerabilities/CVE-2022-21659/49941", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49945", "more_info_path": "/vulnerabilities/PVE-2022-47833/49945", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-24776", "id": "pyup.io-49938", "more_info_path": "/vulnerabilities/CVE-2022-24776/49938", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-32805", "id": "pyup.io-49939", "more_info_path": "/vulnerabilities/CVE-2021-32805/49939", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-33502", "id": "pyup.io-49935", "more_info_path": "/vulnerabilities/CVE-2021-33502/49935", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49944", "more_info_path": "/vulnerabilities/CVE-2022-29217/49944", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-35936", "id": "pyup.io-49936", "more_info_path": "/vulnerabilities/CVE-2021-35936/49936", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (urllib3 == 1.25.11).", "cve": "CVE-2021-33503", "id": "pyup.io-49943", "more_info_path": "/vulnerabilities/CVE-2021-33503/49943", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62924", "more_info_path": "/vulnerabilities/CVE-2023-25754/62924", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-23445", "id": "pyup.io-49934", "more_info_path": "/vulnerabilities/CVE-2021-23445/49934", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-29621", "id": "pyup.io-49937", "more_info_path": "/vulnerabilities/CVE-2021-29621/49937", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-41265", "id": "pyup.io-49940", "more_info_path": "/vulnerabilities/CVE-2021-41265/49940", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (flask-caching == 1.3.3).", "cve": "CVE-2021-33026", "id": "pyup.io-49942", "more_info_path": "/vulnerabilities/CVE-2021-33026/49942", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37712", "id": "pyup.io-49932", "more_info_path": "/vulnerabilities/CVE-2021-37712/49932", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2020-7753", "id": "pyup.io-49930", "more_info_path": "/vulnerabilities/CVE-2020-7753/49930", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (kubernetes == 11.0.0).", "cve": "CVE-2020-1747", "id": "pyup.io-50010", "more_info_path": "/vulnerabilities/CVE-2020-1747/50010", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37713", "id": "pyup.io-49933", "more_info_path": "/vulnerabilities/CVE-2021-37713/49933", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-cncf-kubernetes 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37701", "id": "pyup.io-49931", "more_info_path": "/vulnerabilities/CVE-2021-37701/49931", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-databricks": [ { "advisory": "apache-airflow-backport-providers-databricks 2020.11.23 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62925", "more_info_path": "/vulnerabilities/CVE-2023-25754/62925", "specs": [ "<=2020.11.23" ], "v": "<=2020.11.23" } ], "apache-airflow-backport-providers-datadog": [ { "advisory": "apache-airflow-backport-providers-datadog 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62926", "more_info_path": "/vulnerabilities/CVE-2023-25754/62926", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-dingding": [ { "advisory": "apache-airflow-backport-providers-dingding 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62927", "more_info_path": "/vulnerabilities/CVE-2023-25754/62927", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-discord": [ { "advisory": "apache-airflow-backport-providers-discord 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62928", "more_info_path": "/vulnerabilities/CVE-2023-25754/62928", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-docker": [ { "advisory": "apache-airflow-backport-providers-docker 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62929", "more_info_path": "/vulnerabilities/CVE-2023-25754/62929", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-elasticsearch": [ { "advisory": "apache-airflow-backport-providers-elasticsearch 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62930", "more_info_path": "/vulnerabilities/CVE-2023-25754/62930", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-email": [ { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49961", "more_info_path": "/vulnerabilities/PVE-2022-47833/49961", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-24776", "id": "pyup.io-49954", "more_info_path": "/vulnerabilities/CVE-2022-24776/49954", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37712", "id": "pyup.io-49948", "more_info_path": "/vulnerabilities/CVE-2021-37712/49948", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37713", "id": "pyup.io-49949", "more_info_path": "/vulnerabilities/CVE-2021-37713/49949", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-33502", "id": "pyup.io-49951", "more_info_path": "/vulnerabilities/CVE-2021-33502/49951", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (urllib3 == 1.25.11).", "cve": "CVE-2021-33503", "id": "pyup.io-49959", "more_info_path": "/vulnerabilities/CVE-2021-33503/49959", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-35936", "id": "pyup.io-49952", "more_info_path": "/vulnerabilities/CVE-2021-35936/49952", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49960", "more_info_path": "/vulnerabilities/CVE-2022-29217/49960", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (flask-caching == 1.3.3).", "cve": "CVE-2021-33026", "id": "pyup.io-49958", "more_info_path": "/vulnerabilities/CVE-2021-33026/49958", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-21659", "id": "pyup.io-49957", "more_info_path": "/vulnerabilities/CVE-2022-21659/49957", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-41265", "id": "pyup.io-49956", "more_info_path": "/vulnerabilities/CVE-2021-41265/49956", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-29621", "id": "pyup.io-49953", "more_info_path": "/vulnerabilities/CVE-2021-29621/49953", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-23445", "id": "pyup.io-49950", "more_info_path": "/vulnerabilities/CVE-2021-23445/49950", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-32805", "id": "pyup.io-49955", "more_info_path": "/vulnerabilities/CVE-2021-32805/49955", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37701", "id": "pyup.io-49947", "more_info_path": "/vulnerabilities/CVE-2021-37701/49947", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" }, { "advisory": "Apache-airflow-backport-providers-email 2020.6.24 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2020-7753", "id": "pyup.io-49946", "more_info_path": "/vulnerabilities/CVE-2020-7753/49946", "specs": [ "<=2020.6.24" ], "v": "<=2020.6.24" } ], "apache-airflow-backport-providers-exasol": [ { "advisory": "apache-airflow-backport-providers-exasol 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62932", "more_info_path": "/vulnerabilities/CVE-2023-25754/62932", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-facebook": [ { "advisory": "apache-airflow-backport-providers-facebook 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62933", "more_info_path": "/vulnerabilities/CVE-2023-25754/62933", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-google": [ { "advisory": "apache-airflow-backport-providers-google 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62934", "more_info_path": "/vulnerabilities/CVE-2023-25754/62934", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-grpc": [ { "advisory": "apache-airflow-backport-providers-grpc 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62935", "more_info_path": "/vulnerabilities/CVE-2023-25754/62935", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-hashicorp": [ { "advisory": "apache-airflow-backport-providers-hashicorp 2021.3.23 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62936", "more_info_path": "/vulnerabilities/CVE-2023-25754/62936", "specs": [ "<=2021.3.23" ], "v": "<=2021.3.23" } ], "apache-airflow-backport-providers-jdbc": [ { "advisory": "apache-airflow-backport-providers-jdbc 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62937", "more_info_path": "/vulnerabilities/CVE-2023-25754/62937", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-jenkins": [ { "advisory": "apache-airflow-backport-providers-jenkins 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62938", "more_info_path": "/vulnerabilities/CVE-2023-25754/62938", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-jira": [ { "advisory": "apache-airflow-backport-providers-jira 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62939", "more_info_path": "/vulnerabilities/CVE-2023-25754/62939", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-microsoft-azure": [ { "advisory": "apache-airflow-backport-providers-microsoft-azure 2021.3.13 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62940", "more_info_path": "/vulnerabilities/CVE-2023-25754/62940", "specs": [ "<=2021.3.13" ], "v": "<=2021.3.13" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.13 and prior versions ship with vulnerable dependencies (flask-caching == 1.3.3).", "cve": "CVE-2021-33026", "id": "pyup.io-49974", "more_info_path": "/vulnerabilities/CVE-2021-33026/49974", "specs": [ "<=2021.3.13" ], "v": "<=2021.3.13" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49977", "more_info_path": "/vulnerabilities/PVE-2022-47833/49977", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-33502", "id": "pyup.io-49967", "more_info_path": "/vulnerabilities/CVE-2021-33502/49967", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-23445", "id": "pyup.io-49966", "more_info_path": "/vulnerabilities/CVE-2021-23445/49966", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49976", "more_info_path": "/vulnerabilities/CVE-2022-29217/49976", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-35936", "id": "pyup.io-49968", "more_info_path": "/vulnerabilities/CVE-2021-35936/49968", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2020-7753", "id": "pyup.io-49962", "more_info_path": "/vulnerabilities/CVE-2020-7753/49962", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37712", "id": "pyup.io-49964", "more_info_path": "/vulnerabilities/CVE-2021-37712/49964", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37713", "id": "pyup.io-49965", "more_info_path": "/vulnerabilities/CVE-2021-37713/49965", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-24776", "id": "pyup.io-49970", "more_info_path": "/vulnerabilities/CVE-2022-24776/49970", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-41265", "id": "pyup.io-49972", "more_info_path": "/vulnerabilities/CVE-2021-41265/49972", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-32805", "id": "pyup.io-49971", "more_info_path": "/vulnerabilities/CVE-2021-32805/49971", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-21659", "id": "pyup.io-49973", "more_info_path": "/vulnerabilities/CVE-2022-21659/49973", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (urllib3 == 1.25.11).", "cve": "CVE-2021-33503", "id": "pyup.io-49975", "more_info_path": "/vulnerabilities/CVE-2021-33503/49975", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37701", "id": "pyup.io-49963", "more_info_path": "/vulnerabilities/CVE-2021-37701/49963", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-microsoft-azure 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-29621", "id": "pyup.io-49969", "more_info_path": "/vulnerabilities/CVE-2021-29621/49969", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-microsoft-mssql": [ { "advisory": "apache-airflow-backport-providers-microsoft-mssql 2021.3.23 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62941", "more_info_path": "/vulnerabilities/CVE-2023-25754/62941", "specs": [ "<=2021.3.23" ], "v": "<=2021.3.23" } ], "apache-airflow-backport-providers-microsoft-winrm": [ { "advisory": "apache-airflow-backport-providers-microsoft-winrm 2021.3.23 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62942", "more_info_path": "/vulnerabilities/CVE-2023-25754/62942", "specs": [ "<=2021.3.23" ], "v": "<=2021.3.23" } ], "apache-airflow-backport-providers-mongo": [ { "advisory": "apache-airflow-backport-providers-mongo 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62943", "more_info_path": "/vulnerabilities/CVE-2023-25754/62943", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-mysql": [ { "advisory": "apache-airflow-backport-providers-mysql 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62944", "more_info_path": "/vulnerabilities/CVE-2023-25754/62944", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-neo4j": [ { "advisory": "apache-airflow-backport-providers-neo4j 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62945", "more_info_path": "/vulnerabilities/CVE-2023-25754/62945", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-odbc": [ { "advisory": "apache-airflow-backport-providers-odbc 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62946", "more_info_path": "/vulnerabilities/CVE-2023-25754/62946", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-openfaas": [ { "advisory": "apache-airflow-backport-providers-openfaas 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62947", "more_info_path": "/vulnerabilities/CVE-2023-25754/62947", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-opsgenie": [ { "advisory": "apache-airflow-backport-providers-opsgenie 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62948", "more_info_path": "/vulnerabilities/CVE-2023-25754/62948", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-oracle": [ { "advisory": "apache-airflow-backport-providers-oracle 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62949", "more_info_path": "/vulnerabilities/CVE-2023-25754/62949", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-pagerduty": [ { "advisory": "apache-airflow-backport-providers-pagerduty 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62950", "more_info_path": "/vulnerabilities/CVE-2023-25754/62950", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-papermill": [ { "advisory": "apache-airflow-backport-providers-papermill 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62951", "more_info_path": "/vulnerabilities/CVE-2023-25754/62951", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-plexus": [ { "advisory": "apache-airflow-backport-providers-plexus 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62952", "more_info_path": "/vulnerabilities/CVE-2023-25754/62952", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-postgres": [ { "advisory": "apache-airflow-backport-providers-postgres 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62953", "more_info_path": "/vulnerabilities/CVE-2023-25754/62953", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-presto": [ { "advisory": "apache-airflow-backport-providers-presto 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62954", "more_info_path": "/vulnerabilities/CVE-2023-25754/62954", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-qubole": [ { "advisory": "apache-airflow-backport-providers-qubole 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62955", "more_info_path": "/vulnerabilities/CVE-2023-25754/62955", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-redis": [ { "advisory": "apache-airflow-backport-providers-redis 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62957", "more_info_path": "/vulnerabilities/CVE-2023-25754/62957", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-salesforce": [ { "advisory": "apache-airflow-backport-providers-salesforce 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62958", "more_info_path": "/vulnerabilities/CVE-2023-25754/62958", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-segment": [ { "advisory": "apache-airflow-backport-providers-segment 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62959", "more_info_path": "/vulnerabilities/CVE-2023-25754/62959", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-sendgrid": [ { "advisory": "apache-airflow-backport-providers-sendgrid 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62960", "more_info_path": "/vulnerabilities/CVE-2023-25754/62960", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-sftp": [ { "advisory": "apache-airflow-backport-providers-sftp 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62961", "more_info_path": "/vulnerabilities/CVE-2023-25754/62961", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-singularity": [ { "advisory": "apache-airflow-backport-providers-singularity 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62962", "more_info_path": "/vulnerabilities/CVE-2023-25754/62962", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-slack": [ { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-32805", "id": "pyup.io-49987", "more_info_path": "/vulnerabilities/CVE-2021-32805/49987", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49993", "more_info_path": "/vulnerabilities/PVE-2022-47833/49993", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-33502", "id": "pyup.io-49983", "more_info_path": "/vulnerabilities/CVE-2021-33502/49983", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37701", "id": "pyup.io-49979", "more_info_path": "/vulnerabilities/CVE-2021-37701/49979", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62963", "more_info_path": "/vulnerabilities/CVE-2023-25754/62963", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2020-7753", "id": "pyup.io-49978", "more_info_path": "/vulnerabilities/CVE-2020-7753/49978", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49992", "more_info_path": "/vulnerabilities/CVE-2022-29217/49992", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (urllib3 == 1.25.11).", "cve": "CVE-2021-33503", "id": "pyup.io-49991", "more_info_path": "/vulnerabilities/CVE-2021-33503/49991", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-29621", "id": "pyup.io-49985", "more_info_path": "/vulnerabilities/CVE-2021-29621/49985", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-35936", "id": "pyup.io-49984", "more_info_path": "/vulnerabilities/CVE-2021-35936/49984", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-41265", "id": "pyup.io-49988", "more_info_path": "/vulnerabilities/CVE-2021-41265/49988", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-24776", "id": "pyup.io-49986", "more_info_path": "/vulnerabilities/CVE-2022-24776/49986", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (flask-caching == 1.3.3).", "cve": "CVE-2021-33026", "id": "pyup.io-49990", "more_info_path": "/vulnerabilities/CVE-2021-33026/49990", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-21659", "id": "pyup.io-49989", "more_info_path": "/vulnerabilities/CVE-2022-21659/49989", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37713", "id": "pyup.io-49981", "more_info_path": "/vulnerabilities/CVE-2021-37713/49981", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37712", "id": "pyup.io-49980", "more_info_path": "/vulnerabilities/CVE-2021-37712/49980", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-slack 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-23445", "id": "pyup.io-49982", "more_info_path": "/vulnerabilities/CVE-2021-23445/49982", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-smtp": [ { "advisory": "apache-airflow-backport-providers-smtp 2021.6.24 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62964", "more_info_path": "/vulnerabilities/CVE-2023-25754/62964", "specs": [ "<=2021.6.24" ], "v": "<=2021.6.24" } ], "apache-airflow-backport-providers-snowflake": [ { "advisory": "apache-airflow-backport-providers-snowflake 2021.3.13 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62965", "more_info_path": "/vulnerabilities/CVE-2023-25754/62965", "specs": [ "<=2021.3.13" ], "v": "<=2021.3.13" } ], "apache-airflow-backport-providers-ssh": [ { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-32805", "id": "pyup.io-50003", "more_info_path": "/vulnerabilities/CVE-2021-32805/50003", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62966", "more_info_path": "/vulnerabilities/CVE-2023-25754/62966", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-50009", "more_info_path": "/vulnerabilities/PVE-2022-47833/50009", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-33502", "id": "pyup.io-49999", "more_info_path": "/vulnerabilities/CVE-2021-33502/49999", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2020-7753", "id": "pyup.io-49994", "more_info_path": "/vulnerabilities/CVE-2020-7753/49994", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-50008", "more_info_path": "/vulnerabilities/CVE-2022-29217/50008", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (urllib3 == 1.25.11).", "cve": "CVE-2021-33503", "id": "pyup.io-50007", "more_info_path": "/vulnerabilities/CVE-2021-33503/50007", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-35936", "id": "pyup.io-50000", "more_info_path": "/vulnerabilities/CVE-2021-35936/50000", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-29621", "id": "pyup.io-50001", "more_info_path": "/vulnerabilities/CVE-2021-29621/50001", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-24776", "id": "pyup.io-50002", "more_info_path": "/vulnerabilities/CVE-2022-24776/50002", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2021-41265", "id": "pyup.io-50004", "more_info_path": "/vulnerabilities/CVE-2021-41265/50004", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (flask-appbuilder == 2.3.4).", "cve": "CVE-2022-21659", "id": "pyup.io-50005", "more_info_path": "/vulnerabilities/CVE-2022-21659/50005", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-23445", "id": "pyup.io-49998", "more_info_path": "/vulnerabilities/CVE-2021-23445/49998", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37713", "id": "pyup.io-49997", "more_info_path": "/vulnerabilities/CVE-2021-37713/49997", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (flask-caching == 1.3.3).", "cve": "CVE-2021-33026", "id": "pyup.io-50006", "more_info_path": "/vulnerabilities/CVE-2021-33026/50006", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37712", "id": "pyup.io-49996", "more_info_path": "/vulnerabilities/CVE-2021-37712/49996", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" }, { "advisory": "Apache-airflow-backport-providers-ssh 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2021-37701", "id": "pyup.io-49995", "more_info_path": "/vulnerabilities/CVE-2021-37701/49995", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-tableau": [ { "advisory": "apache-airflow-backport-providers-tableau 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62967", "more_info_path": "/vulnerabilities/CVE-2023-25754/62967", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-telegram": [ { "advisory": "apache-airflow-backport-providers-telegram 2021.3.3 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62968", "more_info_path": "/vulnerabilities/CVE-2023-25754/62968", "specs": [ "<=2021.3.3" ], "v": "<=2021.3.3" } ], "apache-airflow-backport-providers-vertica": [ { "advisory": "apache-airflow-backport-providers-vertica 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62969", "more_info_path": "/vulnerabilities/CVE-2023-25754/62969", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-yandex": [ { "advisory": "apache-airflow-backport-providers-yandex 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62970", "more_info_path": "/vulnerabilities/CVE-2023-25754/62970", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-backport-providers-zendesk": [ { "advisory": "apache-airflow-backport-providers-zendesk 2021.3.17 and prior versions ship with vulnerable dependencies (apache-airflow == 1.10.15).", "cve": "CVE-2023-25754", "id": "pyup.io-62971", "more_info_path": "/vulnerabilities/CVE-2023-25754/62971", "specs": [ "<=2021.3.17" ], "v": "<=2021.3.17" } ], "apache-airflow-providers-airbyte": [ { "advisory": "Apache-airflow-providers-airbyte 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49838", "more_info_path": "/vulnerabilities/PVE-2021-42852/49838", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-airbyte 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49836", "more_info_path": "/vulnerabilities/PVE-2022-47833/49836", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-airbyte 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49837", "more_info_path": "/vulnerabilities/CVE-2022-29217/49837", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-amazon": [ { "advisory": "Apache-airflow-providers-amazon 4.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49835", "more_info_path": "/vulnerabilities/PVE-2021-42852/49835", "specs": [ "<=4.0.0" ], "v": "<=4.0.0" }, { "advisory": "Apache-airflow-providers-amazon 4.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49834", "more_info_path": "/vulnerabilities/CVE-2022-29217/49834", "specs": [ "<=4.0.0" ], "v": "<=4.0.0" }, { "advisory": "Apache-airflow-providers-amazon 4.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49833", "more_info_path": "/vulnerabilities/PVE-2022-47833/49833", "specs": [ "<=4.0.0" ], "v": "<=4.0.0" }, { "advisory": "Generation of Error Message Containing Sensitive Information vulnerability in the Apache Airflow AWS Provider. This issue affects Apache Airflow AWS Provider versions before 7.2.1.", "cve": "CVE-2023-25956", "id": "pyup.io-54663", "more_info_path": "/vulnerabilities/CVE-2023-25956/54663", "specs": [ ">=0,<7.2.1" ], "v": ">=0,<7.2.1" } ], "apache-airflow-providers-apache-drill": [ { "advisory": "Improper Input Validation vulnerability in Apache Software Foundation Apache Airflow Drill Provider.This issue affects Apache Airflow Drill Provider: before 2.3.2.", "cve": "CVE-2023-28707", "id": "pyup.io-59573", "more_info_path": "/vulnerabilities/CVE-2023-28707/59573", "specs": [ "<2.3.2" ], "v": "<2.3.2" }, { "advisory": "Improper Input Validation vulnerability in Apache Software Foundation Apache Airflow Drill Provider. Apache Airflow Drill Provider is affected by a vulnerability that allows an attacker to pass in malicious parameters when establishing a connection with DrillHook giving an opportunity to read files on the Airflow server. This issue affects Apache Airflow Drill Provider: before 2.4.3.", "cve": "CVE-2023-39553", "id": "pyup.io-65022", "more_info_path": "/vulnerabilities/CVE-2023-39553/65022", "specs": [ "<2.4.3" ], "v": "<2.4.3" } ], "apache-airflow-providers-apache-hdfs": [ { "advisory": "In the Apache Airflow HDFS Provider, versions prior to 4.1.1, a documentation info pointed users to an install incorrect pip package. As this package name was unclaimed, in theory, an attacker could claim this package and provide code that would be executed when this package was installed. The Airflow team has since taken ownership of the package (neutralizing the risk), and fixed the doc strings in version 4.1.1.", "cve": "CVE-2023-41267", "id": "pyup.io-65529", "more_info_path": "/vulnerabilities/CVE-2023-41267/65529", "specs": [ "<4.1.1" ], "v": "<4.1.1" }, { "advisory": "Apache-airflow-providers-apache-hdfs 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49819", "more_info_path": "/vulnerabilities/CVE-2022-29217/49819", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-apache-hdfs 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49820", "more_info_path": "/vulnerabilities/PVE-2021-42852/49820", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-apache-hdfs 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49818", "more_info_path": "/vulnerabilities/PVE-2022-47833/49818", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-apache-hive": [ { "advisory": "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Apache Airflow Hive Provider, Apache Airflow allows an attacker to execute arbtrary commands in the task execution context, without write access to DAG files. This issue affects Hive Provider versions prior to 4.1.0. It also impacts any Apache Airflow versions prior to 2.3.0 in case HIve Provider is installed (Hive Provider 4.1.0 can only be installed for Airflow 2.3.0+). Note that you need to manually install the HIve Provider version 4.1.0 in order to get rid of the vulnerability on top of Airflow 2.3.0+ version that has lower version of the Hive Provider installed).", "cve": "CVE-2022-41131", "id": "pyup.io-72000", "more_info_path": "/vulnerabilities/CVE-2022-41131/72000", "specs": [ "<4.1.0" ], "v": "<4.1.0" }, { "advisory": "Improper Control of Generation of Code ('Code Injection') vulnerability in Apache Software Foundation Apache Airflow Hive Provider. This issue affects Apache Airflow Hive Provider before 6.0.0.", "cve": "CVE-2023-28706", "id": "pyup.io-59569", "more_info_path": "/vulnerabilities/CVE-2023-28706/59569", "specs": [ "<6.0.0" ], "v": "<6.0.0" }, { "advisory": "Improper Input Validation vulnerability in Apache Software Foundation Apache Airflow Hive Provider. This issue affects Apache Airflow Apache Hive Provider: before 6.1.1. Before version 6.1.1 it was possible to bypass the security check to RCE via\r\nprincipal parameter. For this to be exploited it requires access to modifying the connection details. It is recommended updating provider version to 6.1.1 in order to avoid this vulnerability.", "cve": "CVE-2023-35797", "id": "pyup.io-65023", "more_info_path": "/vulnerabilities/CVE-2023-35797/65023", "specs": [ "<6.1.1" ], "v": "<6.1.1" }, { "advisory": "Improper Input Validation vulnerability in Apache Software Foundation Apache Airflow Apache Hive Provider. The fix for CVE-2023-35797 was incomplete: the proxy_user option can also inject semicolon.", "cve": "CVE-2023-37415", "id": "pyup.io-71999", "more_info_path": "/vulnerabilities/CVE-2023-37415/71999", "specs": [ "<6.1.2" ], "v": "<6.1.2" }, { "advisory": "Improper Input Validation vulnerability in Apache Software Foundation Apache Airflow Apache Hive Provider.", "cve": "PVE-2024-99896", "id": "pyup.io-64994", "more_info_path": "/vulnerabilities/PVE-2024-99896/64994", "specs": [ "<6.1.2" ], "v": "<6.1.2" }, { "advisory": "Apache-airflow-providers-apache-hive 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49871", "more_info_path": "/vulnerabilities/PVE-2021-42852/49871", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-apache-hive 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49870", "more_info_path": "/vulnerabilities/CVE-2022-29217/49870", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-apache-hive 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49869", "more_info_path": "/vulnerabilities/PVE-2022-47833/49869", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Apache Software Foundation Apache Airflow Hive Provider. This issue affects Apache Airflow Hive Provider before 5.0.0.\r\nhttps://github.com/apache/airflow/pull/28101", "cve": "CVE-2022-46421", "id": "pyup.io-54602", "more_info_path": "/vulnerabilities/CVE-2022-46421/54602", "specs": [ ">=0,<5.0.0" ], "v": ">=0,<5.0.0" }, { "advisory": "Improper Input Validation vulnerability in the Apache Airflow Hive Provider. This issue affects Apache Airflow Hive Provider versions before 5.1.3.", "cve": "CVE-2023-25696", "id": "pyup.io-54657", "more_info_path": "/vulnerabilities/CVE-2023-25696/54657", "specs": [ ">=0,<5.1.3" ], "v": ">=0,<5.1.3" } ], "apache-airflow-providers-apache-livy": [ { "advisory": "Apache-airflow-providers-apache-livy 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49891", "more_info_path": "/vulnerabilities/CVE-2022-29217/49891", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-apache-livy 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49890", "more_info_path": "/vulnerabilities/PVE-2022-47833/49890", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-apache-livy 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49892", "more_info_path": "/vulnerabilities/PVE-2021-42852/49892", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-apache-spark": [ { "advisory": "Improper Input Validation vulnerability in Apache Software Foundation Apache Airflow Spark Provider. This issue affects Apache Airflow Spark Provider before 4.0.1.", "cve": "CVE-2023-28710", "id": "pyup.io-59571", "more_info_path": "/vulnerabilities/CVE-2023-28710/59571", "specs": [ "<4.0.1" ], "v": "<4.0.1" }, { "advisory": "Apache airflow providers apache spark is affected by a vulnerability that allows an attacker to pass in malicious parameters when establishing a connection giving an opportunity to read files on the Airflow server.", "cve": "CVE-2023-40272", "id": "pyup.io-65224", "more_info_path": "/vulnerabilities/CVE-2023-40272/65224", "specs": [ "<4.1.3" ], "v": "<4.1.3" }, { "advisory": "Apache-airflow-providers-apache-spark 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49847", "more_info_path": "/vulnerabilities/PVE-2021-42852/49847", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-apache-spark 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49846", "more_info_path": "/vulnerabilities/CVE-2022-29217/49846", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-apache-spark 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49845", "more_info_path": "/vulnerabilities/PVE-2022-47833/49845", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Deserialization of Untrusted Data, Inclusion of Functionality from Untrusted Control Sphere vulnerability in Apache Software Foundation Apache Airflow Spark Provider. When the Apache Spark provider is installed on an Airflow deployment, an Airflow user that is authorized to configure Spark hooks can effectively run arbitrary code on the Airflow node by pointing it at a malicious Spark server. Prior to version 4.1.3, this was not called out in the documentation explicitly, so it is possible that administrators provided authorizations to configure Spark hooks without taking this into account. We recommend administrators to review their configurations to make sure the authorization to configure Spark hooks is only provided to fully trusted users. To view the warning in the docs please visit https://airflow.apache.org/docs/apache-airflow-providers-apache-spark/4.1.3/connections/spark.html", "cve": "CVE-2023-40195", "id": "pyup.io-63166", "more_info_path": "/vulnerabilities/CVE-2023-40195/63166", "specs": [ ">=0" ], "v": ">=0" } ], "apache-airflow-providers-apache-sqoop": [ { "advisory": "Apache Airflow Sqoop Provider versions before 4.0.0 are affected by a vulnerability that allows an attacker pass parameters with the connections, which makes it possible to implement RCE attacks via \u2018sqoop import --connect\u2019, obtain airflow server permissions, etc. The attacker needs to be logged in and have authorization (permissions) to create/edit connections.", "cve": "CVE-2023-27604", "id": "pyup.io-64556", "more_info_path": "/vulnerabilities/CVE-2023-27604/64556", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "Improper Input Validation vulnerability in the Apache Airflow Sqoop Provider. This issue affects Apache Airflow Sqoop Provider versions before 3.1.1.\r\nhttps://github.com/apache/airflow/pull/29500", "cve": "CVE-2023-25693", "id": "pyup.io-54658", "more_info_path": "/vulnerabilities/CVE-2023-25693/54658", "specs": [ ">=0,<3.1.1" ], "v": ">=0,<3.1.1" } ], "apache-airflow-providers-celery": [ { "advisory": "Insertion of Sensitive Information into Log File vulnerability in Apache Airflow Celery provider, Apache Airflow. Sensitive information logged as clear text when rediss, amqp, rpc protocols are used as Celery result backend.\r\nNote: the vulnerability is about the information exposed in the logs not about accessing the logs.", "cve": "CVE-2023-46215", "id": "pyup.io-71726", "more_info_path": "/vulnerabilities/CVE-2023-46215/71726", "specs": [ "<3.4.1" ], "v": "<3.4.1" }, { "advisory": "Apache-airflow-providers-celery 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49857", "more_info_path": "/vulnerabilities/PVE-2022-47833/49857", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-celery 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49858", "more_info_path": "/vulnerabilities/CVE-2022-29217/49858", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-celery 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49859", "more_info_path": "/vulnerabilities/PVE-2021-42852/49859", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-cloudant": [ { "advisory": "Apache-airflow-providers-cloudant 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49843", "more_info_path": "/vulnerabilities/CVE-2022-29217/49843", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-cloudant 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49844", "more_info_path": "/vulnerabilities/PVE-2021-42852/49844", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-cloudant 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49842", "more_info_path": "/vulnerabilities/PVE-2022-47833/49842", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-cncf-kubernetes": [ { "advisory": "Arbitrary code execution in Apache Airflow CNCF Kubernetes provider allows user to change xcom sidecar image and resources via Airflow connection. In order to exploit this weakness, a user would already need elevated permissions (Op or Admin) to change the connection object in this manner.", "cve": "CVE-2023-33234", "id": "pyup.io-64194", "more_info_path": "/vulnerabilities/CVE-2023-33234/64194", "specs": [ ">=5.0.0,<7.0.0" ], "v": ">=5.0.0,<7.0.0" }, { "advisory": "A vulnerability has been identified in versions of Airflow where, by using deferrable mode and a Kubernetes configuration file for authentication, the Airflow worker sends this configuration as an unencrypted dictionary to the triggerer, storing it in metadata. This process, coupled with certain Airflow versions, also results in the unmasked logging of the configuration dictionary in the triggerer service. Consequently, unauthorized individuals could potentially access and exploit the Kubernetes cluster using the exposed configuration details.", "cve": "CVE-2023-51702", "id": "pyup.io-65396", "more_info_path": "/vulnerabilities/CVE-2023-51702/65396", "specs": [ ">=5.2.0,<7.0.0" ], "v": ">=5.2.0,<7.0.0" } ], "apache-airflow-providers-common-sql": [ { "advisory": "When using the partition clause in SQLTableCheckOperator as parameter (which was a recommended pattern), Authenticated UI User could inject arbitrary SQL command when triggering DAG exposing partition_clause to the user. This allowed the DAG Triggering user to escalate privileges to execute those arbitrary commands which they normally would not have.", "cve": "CVE-2025-30473", "id": "pyup.io-76581", "more_info_path": "/vulnerabilities/CVE-2025-30473/76581", "specs": [ "<1.24.1" ], "v": "<1.24.1" } ], "apache-airflow-providers-databricks": [ { "advisory": "Apache-airflow-providers-databricks 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49824", "more_info_path": "/vulnerabilities/PVE-2022-47833/49824", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-databricks 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49825", "more_info_path": "/vulnerabilities/CVE-2022-29217/49825", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-databricks 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49826", "more_info_path": "/vulnerabilities/PVE-2021-42852/49826", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-datadog": [ { "advisory": "Apache-airflow-providers-datadog 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49887", "more_info_path": "/vulnerabilities/PVE-2022-47833/49887", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-datadog 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49889", "more_info_path": "/vulnerabilities/PVE-2021-42852/49889", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-datadog 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49888", "more_info_path": "/vulnerabilities/CVE-2022-29217/49888", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-docker": [ { "advisory": "Apache Airflow Docker's Provider prior to 3.0.0 shipped with an example DAG that was vulnerable to (authenticated) remote code exploit of code on the Airflow worker host.\r\nhttps://hackerone.com/reports/1671140", "cve": "CVE-2022-38362", "id": "pyup.io-62534", "more_info_path": "/vulnerabilities/CVE-2022-38362/62534", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "Apache-airflow-providers-docker 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49817", "more_info_path": "/vulnerabilities/PVE-2021-42852/49817", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-docker 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49816", "more_info_path": "/vulnerabilities/CVE-2022-29217/49816", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-docker 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49815", "more_info_path": "/vulnerabilities/PVE-2022-47833/49815", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-edge3": [ { "advisory": "Affected versions of the apache-airflow-providers-edge3 package are vulnerable to Remote Code Execution due to an internal, non-public Edge3 testing API being implicitly enabled when the provider is installed and configured on Airflow 2. The Edge3 provider\u2019s \u201cEdge3 Worker RPC\u201d path exposes a normally non-public API surface in Airflow 2 that permits a DAG author to trigger code execution in the webserver context, violating the intended separation between DAG author capabilities and webserver execution.", "cve": "CVE-2025-67895", "id": "pyup.io-82919", "more_info_path": "/vulnerabilities/CVE-2025-67895/82919", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "apache-airflow-providers-fab": [ { "advisory": "When user password has been changed with admin CLI, the sessions for that user have not been cleared, leading to insufficient session expiration, thus logged users could continue to be logged in even after the password was changed. This only happened when the password was changed with CLI. The problem does not happen in case change was done with webserver thus this is different from CVE-2023-40273 which was addressed in Apache-Airflow 2.7.0", "cve": "CVE-2024-45033", "id": "pyup.io-76370", "more_info_path": "/vulnerabilities/CVE-2024-45033/76370", "specs": [ "<1.5.2" ], "v": "<1.5.2" }, { "advisory": "Affected versions of the Apache Airflow Providers FAB package are vulnerable to Insufficient Session Expiration due to improper session invalidation in the logout process. The session management logic in FAB versions 1.2.0 (for all Airflow versions) and 1.2.1 (when used with Apache Airflow 2.9.3) fails to terminate sessions properly, preventing users from successfully logging out. An attacker with access to an active session\u2014such as in a shared environment or via session fixation\u2014can continue to use that session even after logout attempts, potentially impersonating the user and maintaining high-privilege access with full confidentiality, integrity, and availability impact.", "cve": "CVE-2024-42447", "id": "pyup.io-78758", "more_info_path": "/vulnerabilities/CVE-2024-42447/78758", "specs": [ ">=1.2.0,<1.2.2" ], "v": ">=1.2.0,<1.2.2" } ], "apache-airflow-providers-ftp": [ { "advisory": "Improper Certificate Validation vulnerability in Apache Airflow FTP Provider. The FTP hook lacks complete certificate validation in FTP_TLS connections, which can potentially be leveraged. Implementing proper certificate validation by passing context=ssl.create_default_context() during FTP_TLS instantiation is used as mitigation to validate the certificates properly.", "cve": "CVE-2024-29733", "id": "pyup.io-70645", "more_info_path": "/vulnerabilities/CVE-2024-29733/70645", "specs": [ "<3.7.0" ], "v": "<3.7.0" } ], "apache-airflow-providers-google": [ { "advisory": "apache-airflow-providers-google 8.1.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49884", "more_info_path": "/vulnerabilities/PVE-2022-47833/49884", "specs": [ "<=8.1.0" ], "v": "<=8.1.0" }, { "advisory": "Apache-airflow-providers-google 8.1.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49886", "more_info_path": "/vulnerabilities/PVE-2021-42852/49886", "specs": [ "<=8.1.0" ], "v": "<=8.1.0" }, { "advisory": "Apache-airflow-providers-google 8.1.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49885", "more_info_path": "/vulnerabilities/CVE-2022-29217/49885", "specs": [ "<=8.1.0" ], "v": "<=8.1.0" }, { "advisory": "Improper Input Validation vulnerability in the Apache Airflow Google Provider. This issue affects Apache Airflow Google Provider versions before 8.10.0.", "cve": "CVE-2023-25691", "id": "pyup.io-54665", "more_info_path": "/vulnerabilities/CVE-2023-25691/54665", "specs": [ ">=0,<8.10.0" ], "v": ">=0,<8.10.0" }, { "advisory": "Improper Input Validation vulnerability in the Apache Airflow Google Provider. This issue affects Apache Airflow Google Provider versions before 8.10.0.", "cve": "CVE-2023-25692", "id": "pyup.io-54664", "more_info_path": "/vulnerabilities/CVE-2023-25692/54664", "specs": [ ">=0,<8.10.0" ], "v": ">=0,<8.10.0" } ], "apache-airflow-providers-jdbc": [ { "advisory": "Improper Input Validation vulnerability in Apache Software Foundation Apache Airflow JDBC Provider. Airflow JDBC Provider Connection\u2019s [Connection URL] parameters had no restrictions, which made it possible to implement RCE attacks via different type JDBC drivers, obtain airflow server permission. This issue affects Apache Airflow JDBC Provider: before 4.0.0.", "cve": "CVE-2023-22886", "id": "pyup.io-62889", "more_info_path": "/vulnerabilities/CVE-2023-22886/62889", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "Apache-airflow-providers-jdbc 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49878", "more_info_path": "/vulnerabilities/PVE-2022-47833/49878", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-jdbc 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49880", "more_info_path": "/vulnerabilities/PVE-2021-42852/49880", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-jdbc 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49879", "more_info_path": "/vulnerabilities/CVE-2022-29217/49879", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-jenkins": [ { "advisory": "Apache-airflow-providers-jenkins 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49814", "more_info_path": "/vulnerabilities/PVE-2021-42852/49814", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-jenkins 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49812", "more_info_path": "/vulnerabilities/PVE-2022-47833/49812", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-jenkins 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49813", "more_info_path": "/vulnerabilities/CVE-2022-29217/49813", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-jira": [ { "advisory": "Apache-airflow-providers-jira 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49854", "more_info_path": "/vulnerabilities/PVE-2022-47833/49854", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-jira 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49856", "more_info_path": "/vulnerabilities/PVE-2021-42852/49856", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-jira 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49855", "more_info_path": "/vulnerabilities/CVE-2022-29217/49855", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-microsoft-azure": [ { "advisory": "Apache-airflow-providers-microsoft-azure 4.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49875", "more_info_path": "/vulnerabilities/PVE-2022-47833/49875", "specs": [ "<=4.0.0" ], "v": "<=4.0.0" }, { "advisory": "Apache-airflow-providers-microsoft-azure 4.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49877", "more_info_path": "/vulnerabilities/PVE-2021-42852/49877", "specs": [ "<=4.0.0" ], "v": "<=4.0.0" }, { "advisory": "Apache-airflow-providers-microsoft-azure 4.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49876", "more_info_path": "/vulnerabilities/CVE-2022-29217/49876", "specs": [ "<=4.0.0" ], "v": "<=4.0.0" } ], "apache-airflow-providers-microsoft-mssql": [ { "advisory": "Input Validation vulnerability in Apache Software Foundation Apache Airflow ODBC Provider, Apache Software Foundation Apache Airflow MSSQL Provider.This\u00a0vulnerability is considered low since it requires DAG code to use `get_sqlalchemy_connection` and someone with access to connection resources specifically\u00a0updating the connection to exploit it.\r\n\r\nThis issue affects Apache Airflow ODBC Provider: before 4.0.0; Apache Airflow MSSQL Provider: before 3.4.1.\r\n\r\nIt is recommended to\u00a0upgrade to a version that is not affected", "cve": "CVE-2023-35798", "id": "pyup.io-64199", "more_info_path": "/vulnerabilities/CVE-2023-35798/64199", "specs": [ "<3.4.1" ], "v": "<3.4.1" }, { "advisory": "Apache-airflow-providers-microsoft-mssql 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49827", "more_info_path": "/vulnerabilities/PVE-2022-47833/49827", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-microsoft-mssql 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49828", "more_info_path": "/vulnerabilities/CVE-2022-29217/49828", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-microsoft-mssql 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49829", "more_info_path": "/vulnerabilities/PVE-2021-42852/49829", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-mongo": [ { "advisory": "Apache-airflow-providers-mongo 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49808", "more_info_path": "/vulnerabilities/PVE-2021-42852/49808", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-mongo 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49806", "more_info_path": "/vulnerabilities/PVE-2022-47833/49806", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-mongo 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49807", "more_info_path": "/vulnerabilities/CVE-2022-29217/49807", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "When SSL\u00a0was enabled for Mongo Hook, default settings included \"allow_insecure\" which caused that certificates were not validated. This was unexpected and undocumented.", "cve": "CVE-2024-25141", "id": "pyup.io-66701", "more_info_path": "/vulnerabilities/CVE-2024-25141/66701", "specs": [ ">=1.0.0b1,<4.0.0" ], "v": ">=1.0.0b1,<4.0.0" } ], "apache-airflow-providers-mysql": [ { "advisory": "Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Airflow MySQL Provider.", "cve": "CVE-2025-27018", "id": "pyup.io-76303", "more_info_path": "/vulnerabilities/CVE-2025-27018/76303", "specs": [ "<6.2.0" ], "v": "<6.2.0" }, { "advisory": "Apache-airflow-providers-mysql 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49830", "more_info_path": "/vulnerabilities/PVE-2022-47833/49830", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-mysql 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49831", "more_info_path": "/vulnerabilities/CVE-2022-29217/49831", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-mysql 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49832", "more_info_path": "/vulnerabilities/PVE-2021-42852/49832", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Apache Software Foundation Apache Airflow, Apache Software Foundation Apache Airflow MySQL Provider. This issue affects Apache Airflow before 2.5.1 and Apache Airflow MySQL Provider before 4.0.0.", "cve": "CVE-2023-22884", "id": "pyup.io-54621", "more_info_path": "/vulnerabilities/CVE-2023-22884/54621", "specs": [ ">=0,<4.0.0" ], "v": ">=0,<4.0.0" } ], "apache-airflow-providers-odbc": [ { "advisory": "Input Validation vulnerability in Apache Software Foundation Apache Airflow ODBC Provider, Apache Software Foundation Apache Airflow MSSQL Provider.This\u00a0vulnerability is considered low since it requires DAG code to use `get_sqlalchemy_connection` and someone with access to connection resources specifically\u00a0updating the connection to exploit it.\r\n\r\nThis issue affects Apache Airflow ODBC Provider: before 4.0.0; Apache Airflow MSSQL Provider: before 3.4.1.\r\n\r\nIt is recommended to\u00a0upgrade to a version that is not affected", "cve": "CVE-2023-35798", "id": "pyup.io-64200", "more_info_path": "/vulnerabilities/CVE-2023-35798/64200", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') vulnerability in Apache Software Foundation Apache Airflow ODBC Provider. In OdbcHook, A privilege escalation vulnerability exists in a system due to controllable ODBC driver parameters that allow the loading of arbitrary dynamic-link libraries, resulting in command execution. Starting version 4.0.0 driver can be set only from the hook constructor. This issue affects Apache Airflow ODBC Provider: before 4.0.0.", "cve": "CVE-2023-34395", "id": "pyup.io-64201", "more_info_path": "/vulnerabilities/CVE-2023-34395/64201", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "Apache-airflow-providers-odbc 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49893", "more_info_path": "/vulnerabilities/PVE-2022-47833/49893", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-odbc 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49894", "more_info_path": "/vulnerabilities/CVE-2022-29217/49894", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-odbc 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49895", "more_info_path": "/vulnerabilities/PVE-2021-42852/49895", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-oracle": [ { "advisory": "Apache-airflow-providers-oracle 3.1.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49866", "more_info_path": "/vulnerabilities/PVE-2022-47833/49866", "specs": [ "<=3.1.0" ], "v": "<=3.1.0" }, { "advisory": "Apache-airflow-providers-oracle 3.1.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49867", "more_info_path": "/vulnerabilities/CVE-2022-29217/49867", "specs": [ "<=3.1.0" ], "v": "<=3.1.0" }, { "advisory": "Apache-airflow-providers-oracle 3.1.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49868", "more_info_path": "/vulnerabilities/PVE-2021-42852/49868", "specs": [ "<=3.1.0" ], "v": "<=3.1.0" } ], "apache-airflow-providers-pagerduty": [ { "advisory": "Apache-airflow-providers-pagerduty 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49862", "more_info_path": "/vulnerabilities/PVE-2021-42852/49862", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-pagerduty 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49861", "more_info_path": "/vulnerabilities/CVE-2022-29217/49861", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-pagerduty 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49860", "more_info_path": "/vulnerabilities/PVE-2022-47833/49860", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-plexus": [ { "advisory": "Apache-airflow-providers-plexus 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49841", "more_info_path": "/vulnerabilities/PVE-2021-42852/49841", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-plexus 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49839", "more_info_path": "/vulnerabilities/PVE-2022-47833/49839", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-plexus 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49840", "more_info_path": "/vulnerabilities/CVE-2022-29217/49840", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-postgres": [ { "advisory": "Apache-airflow-providers-postgres 5.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49822", "more_info_path": "/vulnerabilities/CVE-2022-29217/49822", "specs": [ "<=5.0.0" ], "v": "<=5.0.0" }, { "advisory": "Apache-airflow-providers-postgres 5.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49821", "more_info_path": "/vulnerabilities/PVE-2022-47833/49821", "specs": [ "<=5.0.0" ], "v": "<=5.0.0" }, { "advisory": "Apache-airflow-providers-postgres 5.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49823", "more_info_path": "/vulnerabilities/PVE-2021-42852/49823", "specs": [ "<=5.0.0" ], "v": "<=5.0.0" } ], "apache-airflow-providers-presto": [ { "advisory": "Apache-airflow-providers-presto 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49863", "more_info_path": "/vulnerabilities/PVE-2022-47833/49863", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-presto 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49865", "more_info_path": "/vulnerabilities/PVE-2021-42852/49865", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-presto 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49864", "more_info_path": "/vulnerabilities/CVE-2022-29217/49864", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-redis": [ { "advisory": "Apache-airflow-providers-redis 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49873", "more_info_path": "/vulnerabilities/CVE-2022-29217/49873", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-redis 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49874", "more_info_path": "/vulnerabilities/PVE-2021-42852/49874", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-redis 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49872", "more_info_path": "/vulnerabilities/PVE-2022-47833/49872", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-sendgrid": [ { "advisory": "Apache-airflow-providers-sendgrid 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49809", "more_info_path": "/vulnerabilities/PVE-2022-47833/49809", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-sendgrid 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49810", "more_info_path": "/vulnerabilities/CVE-2022-29217/49810", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-sendgrid 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49811", "more_info_path": "/vulnerabilities/PVE-2021-42852/49811", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-sftp": [ { "advisory": "Apache-airflow-providers-sftp 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49899", "more_info_path": "/vulnerabilities/PVE-2022-47833/49899", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-sftp 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49901", "more_info_path": "/vulnerabilities/PVE-2021-42852/49901", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-sftp 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49900", "more_info_path": "/vulnerabilities/CVE-2022-29217/49900", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-slack": [ { "advisory": "Apache-airflow-providers-slack 5.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49851", "more_info_path": "/vulnerabilities/PVE-2022-47833/49851", "specs": [ "<=5.0.0" ], "v": "<=5.0.0" }, { "advisory": "Apache-airflow-providers-slack 5.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49853", "more_info_path": "/vulnerabilities/PVE-2021-42852/49853", "specs": [ "<=5.0.0" ], "v": "<=5.0.0" }, { "advisory": "Apache-airflow-providers-slack 5.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49852", "more_info_path": "/vulnerabilities/CVE-2022-29217/49852", "specs": [ "<=5.0.0" ], "v": "<=5.0.0" } ], "apache-airflow-providers-snowflake": [ { "advisory": "Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) vulnerability in Apache Airflow Providers Snowflake. Sanitation of table and stage parameters was added in CopyFromExternalStageToSnowflakeOperator to prevent SQL injection.", "cve": "CVE-2025-50213", "id": "pyup.io-77945", "more_info_path": "/vulnerabilities/CVE-2025-50213/77945", "specs": [ "<6.4.0" ], "v": "<6.4.0" }, { "advisory": "Apache-airflow-providers-snowflake 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49848", "more_info_path": "/vulnerabilities/PVE-2022-47833/49848", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-snowflake 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49850", "more_info_path": "/vulnerabilities/PVE-2021-42852/49850", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-snowflake 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49849", "more_info_path": "/vulnerabilities/CVE-2022-29217/49849", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-ssh": [ { "advisory": "Apache-airflow-providers-ssh 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49897", "more_info_path": "/vulnerabilities/CVE-2022-29217/49897", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-ssh 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49898", "more_info_path": "/vulnerabilities/PVE-2021-42852/49898", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-ssh 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49896", "more_info_path": "/vulnerabilities/PVE-2022-47833/49896", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-tableau": [ { "advisory": "Apache-airflow-providers-tableau 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49883", "more_info_path": "/vulnerabilities/PVE-2021-42852/49883", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-tableau 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49881", "more_info_path": "/vulnerabilities/PVE-2022-47833/49881", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-tableau 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49882", "more_info_path": "/vulnerabilities/CVE-2022-29217/49882", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-airflow-providers-telegram": [ { "advisory": "Apache-airflow-providers-telegram 3.0.0 and prior versions ship with vulnerable dependencies (click == 7.1.2).", "cve": "PVE-2022-47833", "id": "pyup.io-49803", "more_info_path": "/vulnerabilities/PVE-2022-47833/49803", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-telegram 3.0.0 and prior versions ship with vulnerable dependencies (wtforms == 2.3.3).", "cve": "PVE-2021-42852", "id": "pyup.io-49805", "more_info_path": "/vulnerabilities/PVE-2021-42852/49805", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" }, { "advisory": "Apache-airflow-providers-telegram 3.0.0 and prior versions ship with vulnerable dependencies (pyjwt == 1.7.1).", "cve": "CVE-2022-29217", "id": "pyup.io-49804", "more_info_path": "/vulnerabilities/CVE-2022-29217/49804", "specs": [ "<=3.0.0" ], "v": "<=3.0.0" } ], "apache-beam": [ { "advisory": "Apache-beam 2.54.0", "cve": "PVE-2023-63060", "id": "pyup.io-63060", "more_info_path": "/vulnerabilities/PVE-2023-63060/63060", "specs": [ "<2.54.0" ], "v": "<2.54.0" } ], "apache-dolphinscheduler": [ { "advisory": "Apache-dolphinscheduler 3.0.0 (Python SDK) corresponds to DolphinScheduler version 3.0.0, which is vulnerable to path traversal.", "cve": "CVE-2022-34662", "id": "pyup.io-62760", "more_info_path": "/vulnerabilities/CVE-2022-34662/62760", "specs": [ "<3.0.0" ], "v": "<3.0.0" } ], "apache-flink": [ { "advisory": "Apache-flink 1.14.2 updates its dependency 'log4j' to v2.16.0 to include security fixes.\r\nhttps://github.com/apache/flink/commit/361ce6591069b2f7317f1c181cdaf7965615415c", "cve": "CVE-2021-45046", "id": "pyup.io-43417", "more_info_path": "/vulnerabilities/CVE-2021-45046/43417", "specs": [ "<1.14.2" ], "v": "<1.14.2" }, { "advisory": "Apache-flink 1.14.2 updates its dependency 'log4j' to v2.16.0 to include security fixes.\r\nhttps://github.com/apache/flink/commit/361ce6591069b2f7317f1c181cdaf7965615415c", "cve": "CVE-2021-44228", "id": "pyup.io-43416", "more_info_path": "/vulnerabilities/CVE-2021-44228/43416", "specs": [ "<1.14.2" ], "v": "<1.14.2" }, { "advisory": "Apache-flink 1.14.3 updates its dependency 'log4j' to v2.17.1 to include security fixes.\r\nhttps://github.com/apache/flink/pull/18228/commits/f28e12599cfde7b41e341e4466fdbd2ad3604d82", "cve": "CVE-2021-44832", "id": "pyup.io-44453", "more_info_path": "/vulnerabilities/CVE-2021-44832/44453", "specs": [ "<1.14.3" ], "v": "<1.14.3" }, { "advisory": "Apache-flink 1.14.3 updates its dependency 'log4j' to v2.17.1 to include security fixes.\r\nhttps://github.com/apache/flink/pull/18228/commits/f28e12599cfde7b41e341e4466fdbd2ad3604d82", "cve": "CVE-2021-45105", "id": "pyup.io-43436", "more_info_path": "/vulnerabilities/CVE-2021-45105/43436", "specs": [ "<1.14.3" ], "v": "<1.14.3" } ], "apache-iotdb": [ { "advisory": "Apache IoTDB version 0.13.0 is vulnerable by session id attack. Users should upgrade to version 0.13.1 which addresses this issue.\r\nAlias:\r\nGHSA-g6vm-3ch8-c6jq", "cve": "CVE-2022-38369", "id": "pyup.io-62764", "more_info_path": "/vulnerabilities/CVE-2022-38369/62764", "specs": [ "<0.13.1" ], "v": "<0.13.1" }, { "advisory": "Incorrect Authorization vulnerability in Apache Software Foundation Apache IoTDB.This issue affects the iotdb-web-workbench component on 0.13.3. iotdb-web-workbench is an optional component of IoTDB, providing a web console of the database. This problem is fixed from version 0.13.4 of iotdb-web-workbench onwards.", "cve": "CVE-2023-30771", "id": "pyup.io-64184", "more_info_path": "/vulnerabilities/CVE-2023-30771/64184", "specs": [ "==0.13.3" ], "v": "==0.13.3" }, { "advisory": "Affected versions of the Apache IoTDB package are vulnerable to Information Disclosure due to improper handling of sensitive data in log files. The OpenIdAuthorizer component logs sensitive authentication information, including credentials or tokens, to system log files without proper sanitization or redaction, exposing this data to unauthorized users with access to the log files.", "cve": "CVE-2025-26864", "id": "pyup.io-78840", "more_info_path": "/vulnerabilities/CVE-2025-26864/78840", "specs": [ ">=0.10.0,<1.3.4", ">=2.0.1b0,<2.0.2" ], "v": ">=0.10.0,<1.3.4,>=2.0.1b0,<2.0.2" }, { "advisory": "Apache IoTDB version 0.12.2 to 0.12.6, 0.13.0 to 0.13.2 are vulnerable to a Denial of Service attack when accepting untrusted patterns for REGEXP queries with Java 8. Users should upgrade to 0.13.3 which addresses this issue or use a later version of Java to avoid it.\r\n\r\nAlias(es):\r\nGHSA-g6hg-4v3c-6jq7\r\nPYSEC-2022-42972", "cve": "CVE-2022-43766", "id": "pyup.io-62772", "more_info_path": "/vulnerabilities/CVE-2022-43766/62772", "specs": [ ">=0.12.2,<=0.12.6", ">=0.13.0,<=0.13.2" ], "v": ">=0.12.2,<=0.12.6,>=0.13.0,<=0.13.2" }, { "advisory": "Remote Code Execution vulnerability in Apache IoTDB.", "cve": "CVE-2023-46226", "id": "pyup.io-70407", "more_info_path": "/vulnerabilities/CVE-2023-46226/70407", "specs": [ ">=1.0.0,<1.3.0" ], "v": ">=1.0.0,<1.3.0" }, { "advisory": "Affected versions of the Apache IoTDB package are vulnerable to Remote Code Execution due to insufficient validation of User-Defined Function (UDF) registration sources. The UDF registration mechanism allows privileged users to register functions from external URIs without properly validating or restricting the source locations, enabling the loading and execution of malicious code from untrusted remote sources.", "cve": "CVE-2024-24780", "id": "pyup.io-78841", "more_info_path": "/vulnerabilities/CVE-2024-24780/78841", "specs": [ ">=1.0.0,<1.3.4" ], "v": ">=1.0.0,<1.3.4" } ], "apache-libcloud": [ { "advisory": "Apache Libcloud before 0.11.1 uses an incorrect regular expression during verification of whether the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a crafted certificate.", "cve": "CVE-2012-3446", "id": "pyup.io-25628", "more_info_path": "/vulnerabilities/CVE-2012-3446/25628", "specs": [ "<0.11.1" ], "v": "<0.11.1" }, { "advisory": "Libcloud 0.12.3 through 0.13.2 does not set the scrub_data parameter for the destroy DigitalOcean API, which allows local users to obtain sensitive information by leveraging a new VM.", "cve": "CVE-2013-6480", "id": "pyup.io-25629", "more_info_path": "/vulnerabilities/CVE-2013-6480/25629", "specs": [ "<0.13.3" ], "v": "<0.13.3" }, { "advisory": "libcloud before 0.4.1 does not verify SSL certificates for HTTPS connections, which allows remote attackers to spoof certificates and bypass intended access restrictions via a man-in-the-middle (MITM) attack.", "cve": "CVE-2010-4340", "id": "pyup.io-35343", "more_info_path": "/vulnerabilities/CVE-2010-4340/35343", "specs": [ "<0.4.1" ], "v": "<0.4.1" } ], "apache-skywalking": [ { "advisory": "This vulnerability in Apache SkyWalking affects versions before 8.1.0 with H2, MySQL, or TiDB storage and involves SQL injection risks in wildcard query cases.", "cve": "CVE-2020-13921", "id": "pyup.io-66880", "more_info_path": "/vulnerabilities/CVE-2020-13921/66880", "specs": [ ">=0,<8.1.0" ], "v": ">=0,<8.1.0" } ], "apache-submarine": [ { "advisory": "Affected versions of the Apache Submarine Commons Utils package are vulnerable to Improper Authentication due to use of a default, hard-coded secret when the `submarine.auth.default.secret` configuration is not explicitly set. The authentication mechanism in `Commons Utils` relies on this default credential, which is predictable and insecure, compromising the authentication process. A remote attacker can exploit this vulnerability over the network\u2014without any privileges or user interaction\u2014to bypass authentication and gain unauthorized access, potentially compromising confidentiality, integrity, and availability. \r\n# NOTE: This issue affects only a retired project that is no longer supported, so no fix is planned.", "cve": "CVE-2024-36264", "id": "pyup.io-78736", "more_info_path": "/vulnerabilities/CVE-2024-36264/78736", "specs": [ "<=0.8.0" ], "v": "<=0.8.0" }, { "advisory": "Affected versions of the apache-submarine package (specifically the submarine-server-core module) are vulnerable to Improper Authorization due to missing access control enforcement in the service\u2019s core operations. The submarine-server-core component fails to verify user permissions before granting access, allowing any remote actor to bypass authorization checks. A remote attacker can exploit this by sending network requests to the submarine-server-core interface, gaining unauthorized access to sensitive data and functions, resulting in both confidentiality and integrity compromise.\r\n# NOTE: This vulnerability only affects products that are no longer supported by the maintainer.", "cve": "CVE-2024-36265", "id": "pyup.io-78728", "more_info_path": "/vulnerabilities/CVE-2024-36265/78728", "specs": [ "==0.8.0" ], "v": "==0.8.0" }, { "advisory": "Apache Software Foundation Apache Submarine has a bug when serializing against yaml. The bug is caused by snakeyaml https://nvd.nist.gov/vuln/detail/CVE-2022-1471. Apache Submarine uses JAXRS to define REST endpoints. In order to handle YAML requests (using application/yaml content-type), it defines a YamlEntityProvider entity provider that will process all incoming YAML requests. In order to unmarshal the request, the readFrom method is invoked, passing the entityStream containing the user-supplied data in `submarine-server/server-core/src/main/java/org/apache/submarine/server/utils/YamlUtils.java`. We have now fixed this issue in the new version by replacing to `jackson-dataformat-yaml`. This issue affects Apache Submarine: from 0.7.0 before 0.8.0.\u00a0Users are recommended to upgrade to version 0.8.0, which fixes this issue.If using the version smaller than 0.8.0 and not want to upgrade, you can try cherry-pick PR https://github.com/apache/submarine/pull/1054 and rebuild the submart-server image to fix this.", "cve": "CVE-2023-46302", "id": "pyup.io-70898", "more_info_path": "/vulnerabilities/CVE-2023-46302/70898", "specs": [ ">=0.7.0,<0.8.0" ], "v": ">=0.7.0,<0.8.0" } ], "apache-superset": [ { "advisory": "Apache-superset 0.14.0 improves the security scheme (#1587).", "cve": "PVE-2021-39494", "id": "pyup.io-39494", "more_info_path": "/vulnerabilities/PVE-2021-39494/39494", "specs": [ "<0.14.0" ], "v": "<0.14.0" }, { "advisory": "Apache-superset version 0.17.5 adds a csrf_token api endpoint.", "cve": "PVE-2021-41794", "id": "pyup.io-41794", "more_info_path": "/vulnerabilities/PVE-2021-41794/41794", "specs": [ "<0.17.5" ], "v": "<0.17.5" }, { "advisory": "Apache-superset 0.25.0 refactors security code into SupersetSecurityManager (#4565).", "cve": "PVE-2021-39488", "id": "pyup.io-39488", "more_info_path": "/vulnerabilities/PVE-2021-39488/39488", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Apache-superset 0.28.0rc5 moves set/merge perm to security manager (#5684).", "cve": "PVE-2021-39485", "id": "pyup.io-39485", "more_info_path": "/vulnerabilities/PVE-2021-39485/39485", "specs": [ "<0.28.0rc5" ], "v": "<0.28.0rc5" }, { "advisory": "Apache-superset 0.29.0rc8 secures unsecured views and prevent regressions (#6553).", "cve": "PVE-2021-39484", "id": "pyup.io-39484", "more_info_path": "/vulnerabilities/PVE-2021-39484/39484", "specs": [ "<0.29.0rc8" ], "v": "<0.29.0rc8" }, { "advisory": "Apache-superset 0.31.0rc1 fixes dependencies with vulnerabilities (#6904).", "cve": "PVE-2021-39483", "id": "pyup.io-39483", "more_info_path": "/vulnerabilities/PVE-2021-39483/39483", "specs": [ "<0.31.0rc1" ], "v": "<0.31.0rc1" }, { "advisory": "Apache-superset 0.32.0rc1 makes it easier to redefine Alpha/Gamma (#7036) - this was a security concern. It also \r\nran 'npm audit fix' to address various vulnerabilities (#7263).", "cve": "PVE-2021-39482", "id": "pyup.io-39482", "more_info_path": "/vulnerabilities/PVE-2021-39482/39482", "specs": [ "<0.32.0rc1" ], "v": "<0.32.0rc1" }, { "advisory": "Apache-superset 0.32.0rc2.dev2 updates merge_perm and fixes the FAB method (#7355). These were both security issues.", "cve": "PVE-2021-39480", "id": "pyup.io-39480", "more_info_path": "/vulnerabilities/PVE-2021-39480/39480", "specs": [ "<0.32.0rc2.dev2" ], "v": "<0.32.0rc2.dev2" }, { "advisory": "Apache-superset 0.33.0rc1 adds Flask-Talisman (#7443) for security reasons.", "cve": "PVE-2021-39481", "id": "pyup.io-39481", "more_info_path": "/vulnerabilities/PVE-2021-39481/39481", "specs": [ "<0.33.0rc1" ], "v": "<0.33.0rc1" }, { "advisory": "Apache-superset 0.34.0 updates its dependency 'urllib3' to v1.24.3 to include security fixes.", "cve": "CVE-2019-11324", "id": "pyup.io-45812", "more_info_path": "/vulnerabilities/CVE-2019-11324/45812", "specs": [ "<0.34.0" ], "v": "<0.34.0" }, { "advisory": "Apache-superset 0.34.0 updates its dependency 'pyyaml' to v5.1 to include a security fix.", "cve": "CVE-2017-18342", "id": "pyup.io-45811", "more_info_path": "/vulnerabilities/CVE-2017-18342/45811", "specs": [ "<0.34.0" ], "v": "<0.34.0" }, { "advisory": "Apache-superset 0.34.0 updates its dependency 'jinja2' to v2.10.1 to include a security fix.", "cve": "CVE-2019-10906", "id": "pyup.io-39479", "more_info_path": "/vulnerabilities/CVE-2019-10906/39479", "specs": [ "<0.34.0" ], "v": "<0.34.0" }, { "advisory": "Apache-superset 0.34.0 updates its dependency 'urllib3' to include a security fix.", "cve": "CVE-2018-20060", "id": "pyup.io-45814", "more_info_path": "/vulnerabilities/CVE-2018-20060/45814", "specs": [ "<0.34.0" ], "v": "<0.34.0" }, { "advisory": "Apache-superset 0.35.0 adds security for restricted metrics (#8175).", "cve": "PVE-2021-39478", "id": "pyup.io-39478", "more_info_path": "/vulnerabilities/PVE-2021-39478/39478", "specs": [ "<0.35.0" ], "v": "<0.35.0" }, { "advisory": "Apache-superset 0.35.1 updates its dependency 'dompurify' to v2.0.7 to include a security fix.", "cve": "CVE-2020-26870", "id": "pyup.io-39477", "more_info_path": "/vulnerabilities/CVE-2020-26870/39477", "specs": [ "<0.35.1" ], "v": "<0.35.1" }, { "advisory": "Apache-superset 0.35.2 bumps packages with security vulnerabilities (#8573), and bumps pyarrow to 0.15.1 due to CVE-2019-12408 (#8583).", "cve": "CVE-2019-12408", "id": "pyup.io-39476", "more_info_path": "/vulnerabilities/CVE-2019-12408/39476", "specs": [ "<0.35.2" ], "v": "<0.35.2" }, { "advisory": "Apache-superset 0.36.0 filters out markdown containing XSS.\r\nhttps://github.com/apache/superset/pull/9163", "cve": "PVE-2021-39475", "id": "pyup.io-39475", "more_info_path": "/vulnerabilities/PVE-2021-39475/39475", "specs": [ "<0.36.0" ], "v": "<0.36.0" }, { "advisory": "Apache-superset 0.36.0 updates its NPM dependency 'chownr' to v1.1.1 to include a security fix.\r\nhttps://github.com/apache/superset/pull/9106/commits/788faad7f33e1b69afcee0f01c9fc7cdccb7f81f", "cve": "CVE-2017-18869", "id": "pyup.io-42732", "more_info_path": "/vulnerabilities/CVE-2017-18869/42732", "specs": [ "<0.36.0" ], "v": "<0.36.0" }, { "advisory": "Apache-superset 0.36.0 updates its NPM dependency 'serialize-javascript' to v2.1.2 to include security fixes.\r\nhttps://github.com/apache/superset/pull/9106/commits/788faad7f33e1b69afcee0f01c9fc7cdccb7f81f", "cve": "CVE-2019-16772", "id": "pyup.io-44578", "more_info_path": "/vulnerabilities/CVE-2019-16772/44578", "specs": [ "<0.36.0" ], "v": "<0.36.0" }, { "advisory": "Apache-superset 0.36.0 updates its NPM dependency 'serialize-javascript' to v2.1.2 to include security fixes.\r\nhttps://github.com/apache/superset/pull/9106/commits/788faad7f33e1b69afcee0f01c9fc7cdccb7f81f", "cve": "CVE-2019-16769", "id": "pyup.io-44577", "more_info_path": "/vulnerabilities/CVE-2019-16769/44577", "specs": [ "<0.36.0" ], "v": "<0.36.0" }, { "advisory": "Apache-superset 0.37.0 includes various security-related improvements. It fixes regression in #9689 (9705), it fixes can_access with None because it crashed on builtin roles (#10039), it renames schemas_accessible_by_user (#10030), renames access methods (#10031), it updates assert logic (#10034), and it fixes the dbs/clusters perm (#10130).", "cve": "PVE-2021-39474", "id": "pyup.io-39474", "more_info_path": "/vulnerabilities/PVE-2021-39474/39474", "specs": [ "<0.37.0" ], "v": "<0.37.0" }, { "advisory": "Apache-superset 0.37.1 disallows uuid package on jinja1 (#10794). This is a security improvement.", "cve": "PVE-2021-39473", "id": "pyup.io-39473", "more_info_path": "/vulnerabilities/PVE-2021-39473/39473", "specs": [ "<0.37.1" ], "v": "<0.37.1" }, { "advisory": "Apache-superset 0.37.1 includes a fix for CVE-2020-13948: While investigating a bug report on Apache Superset, it was determined that an authenticated user could craft requests via a number of templated text fields in the product that would allow arbitrary access to Python\u2019s 'os' package in the web application process in versions < 0.37.1. It was thus possible for an authenticated user to list and access files, environment variables, and process information. Additionally it was possible to set environment variables for the current process, create and update files in folders writable by the web process, and execute arbitrary programs accessible by the web process. All other operations available to the 'os' package in Python were also available, even if not explicitly enumerated in this CVE.", "cve": "CVE-2020-13948", "id": "pyup.io-38793", "more_info_path": "/vulnerabilities/CVE-2020-13948/38793", "specs": [ "<0.37.1" ], "v": "<0.37.1" }, { "advisory": "Apache-superset 0.9.1 improved its security: Gamma role sees only its objects, and only owners and Admins can alter objects.", "cve": "PVE-2021-38193", "id": "pyup.io-38193", "more_info_path": "/vulnerabilities/PVE-2021-38193/38193", "specs": [ "<0.9.1" ], "v": "<0.9.1" }, { "advisory": "Apache-superset 1.0.0 applies owners security validation. It was missing from the new reports API.\r\nhttps://github.com/apache/superset/pull/12035", "cve": "PVE-2021-41203", "id": "pyup.io-41203", "more_info_path": "/vulnerabilities/PVE-2021-41203/41203", "specs": [ "<1.0.0" ], "v": "<1.0.0" }, { "advisory": "Apache-superset 1.2.0 updates NPM packages for security fixes.\r\nhttps://github.com/apache/superset/pull/13367", "cve": "CVE-2020-28477", "id": "pyup.io-41791", "more_info_path": "/vulnerabilities/CVE-2020-28477/41791", "specs": [ "<1.2.0" ], "v": "<1.2.0" }, { "advisory": "Apache-superset 2.0.1 improves SafeMarkdown HTML sanitization to prevent possible attacks.\r\nhttps://github.com/apache/superset/pull/21895", "cve": "PVE-2023-52798", "id": "pyup.io-52798", "more_info_path": "/vulnerabilities/PVE-2023-52798/52798", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Apache-superset 2.0.1 disables HTML rendering in Toast by default.\r\nhttps://github.com/apache/superset/pull/21853", "cve": "PVE-2023-52807", "id": "pyup.io-52807", "more_info_path": "/vulnerabilities/PVE-2023-52807/52807", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Apache-superset 2.1.0 includes a fix for an XSS vulnerability.\r\nhttps://github.com/apache/superset/pull/21822", "cve": "PVE-2023-59076", "id": "pyup.io-59076", "more_info_path": "/vulnerabilities/PVE-2023-59076/59076", "specs": [ "<2.1.0" ], "v": "<2.1.0" }, { "advisory": "Unnecessary read permissions within the Gamma role would allow authenticated users to read configured CSS templates and annotations. This issue affects Apache Superset: before 2.1.2. Users should upgrade to version or above 2.1.2 and run `superset init` to reconstruct the Gamma role or remove `can_read` permission from the mentioned resources.", "cve": "CVE-2023-42501", "id": "pyup.io-65226", "more_info_path": "/vulnerabilities/CVE-2023-42501/65226", "specs": [ "<2.1.1" ], "v": "<2.1.1" }, { "advisory": "Improper payload validation and an improper REST API response type made it possible for an authenticated malicious actor to store malicious code in Chart's metadata, this code could get executed if a user specifically accesses a specific deprecated API endpoint.\u00a0This issue affects Apache Superset versions before 2.1.2.", "cve": "CVE-2023-43701", "id": "pyup.io-65230", "more_info_path": "/vulnerabilities/CVE-2023-43701/65230", "specs": [ "<2.1.2" ], "v": "<2.1.2" }, { "advisory": "Improper authorization check and possible privilege escalation on Apache Superset up to but excluding 2.1.2. Using the default examples database connection that allows access to both the examples schema and Apache Superset's metadata database, an attacker using a specially crafted CTE SQL statement could change data on the metadata database. This weakness could result on tampering with the authentication/authorization data.", "cve": "CVE-2023-40610", "id": "pyup.io-65225", "more_info_path": "/vulnerabilities/CVE-2023-40610/65225", "specs": [ "<2.1.2" ], "v": "<2.1.2" }, { "advisory": "Apache-superset 3.0.0 updates its dependency 'flask_caching' to v1.11.1 to include a security fix.", "cve": "CVE-2021-33026", "id": "pyup.io-61921", "more_info_path": "/vulnerabilities/CVE-2021-33026/61921", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "An authenticated attacker with update datasets permission could change a dataset link to an untrusted site by spoofing the HTTP Host header, users could be redirected to this site when clicking on that specific dataset. This issue affects Apache Superset versions before 3.0.0.", "cve": "CVE-2023-42502", "id": "pyup.io-65227", "more_info_path": "/vulnerabilities/CVE-2023-42502/65227", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "An authenticated user with read permissions on database connections metadata could potentially access sensitive information such as the connection's username. This issue affects Apache Superset before 3.0.0.", "cve": "CVE-2023-42505", "id": "pyup.io-65229", "more_info_path": "/vulnerabilities/CVE-2023-42505/65229", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "Apache-superset 3.0.0 updates its NPM dependency 'ansi-regex' to include a security fix.", "cve": "CVE-2021-3807", "id": "pyup.io-61908", "more_info_path": "/vulnerabilities/CVE-2021-3807/61908", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "An authenticated malicious user could initiate multiple concurrent requests, each requesting multiple dashboard exports, leading to a possible denial of service. This issue affects Apache Superset: before 3.0.0", "cve": "CVE-2023-42504", "id": "pyup.io-65228", "more_info_path": "/vulnerabilities/CVE-2023-42504/65228", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "A stored cross-site scripting (XSS) vulnerability exists in Apache Superset before 3.0.3.\u00a0An authenticated attacker with create/update permissions on charts or dashboards could store a script or add a specific HTML snippet that would act as a stored XSS.", "cve": "CVE-2023-49657", "id": "pyup.io-66702", "more_info_path": "/vulnerabilities/CVE-2023-49657/66702", "specs": [ "<3.0.3" ], "v": "<3.0.3" }, { "advisory": "An authenticated user could potentially access metadata for a data source they are not authorized to view by submitting a targeted REST API request.", "cve": "CVE-2024-28148", "id": "pyup.io-71839", "more_info_path": "/vulnerabilities/CVE-2024-28148/71839", "specs": [ "<3.1.2" ], "v": "<3.1.2" }, { "advisory": "An Improper Input Validation vulnerability in Apache Superset allows an authenticated attacker to establish a MariaDB connection with the local_infile option enabled. If both the MariaDB server (which has this feature disabled by default) and the local MySQL client on the web server are configured to allow local infile, the attacker can execute a specific SQL command to read files from the server and insert their contents into a MariaDB database table.", "cve": "CVE-2024-34693", "id": "pyup.io-71840", "more_info_path": "/vulnerabilities/CVE-2024-34693/71840", "specs": [ "<3.1.3", ">=4.0.0rc1,<4.0.1" ], "v": "<3.1.3,>=4.0.0rc1,<4.0.1" }, { "advisory": "An SQL Injection vulnerability in Apache Superset exists due to improper neutralization of special elements used in SQL commands. Specifically, certain engine-specific functions are not checked, which allows attackers to bypass Apache Superset's SQL authorization. To mitigate this, a new configuration key named DISALLOWED_SQL_FUNCTIONS has been introduced. This key disallows using the following PostgreSQL functions: version, query_to_xml, inet_server_addr, and inet_client_addr. Additional functions can be added to this list for increased protection.", "cve": "CVE-2024-39887", "id": "pyup.io-72252", "more_info_path": "/vulnerabilities/CVE-2024-39887/72252", "specs": [ "<4.0.2" ], "v": "<4.0.2" }, { "advisory": "Improper Authorization vulnerability in Apache Superset. On Postgres analytic databases an attacker with SQLLab access can craft a specially designed SQL DML statement that is Incorrectly identified as a read-only query, enabling its execution. Non postgres analytics database connections and postgres analytics database connections set with a readonly user (advised) are not vulnerable.", "cve": "CVE-2024-55633", "id": "pyup.io-76383", "more_info_path": "/vulnerabilities/CVE-2024-55633/76383", "specs": [ "<4.1.0" ], "v": "<4.1.0" }, { "advisory": "Generation of Error Message Containing Analytics Metadata Information in Apache Superset.", "cve": "CVE-2024-53948", "id": "pyup.io-76388", "more_info_path": "/vulnerabilities/CVE-2024-53948/76388", "specs": [ "<4.1.0" ], "v": "<4.1.0" }, { "advisory": "Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Superset. Specifically, certain engine-specific functions are not checked, which allows attackers to bypass Apache Superset's SQL authorization. This issue is a follow-up to CVE-2024-39887 with additional disallowed PostgreSQL functions now included: querytoxmlandxmlschema, tabletoxml, tabletoxmlandxmlschema.", "cve": "CVE-2024-53947", "id": "pyup.io-76390", "more_info_path": "/vulnerabilities/CVE-2024-53947/76390", "specs": [ "<4.1.0" ], "v": "<4.1.0" }, { "advisory": "Improper Authorization vulnerability in Apache Superset allows ownership takeover of dashboards, charts or datasets by authenticated users with read permissions.", "cve": "CVE-2025-27696", "id": "pyup.io-77324", "more_info_path": "/vulnerabilities/CVE-2025-27696/77324", "specs": [ "<4.1.2" ], "v": "<4.1.2" }, { "advisory": "An authenticated malicious actor using specially crafted requests could bypass row-level security configuration by injecting SQL into 'sqlExpression' fields. This allowed the execution of sub-queries to evade parsing defences, ultimately granting unauthorized access to data. This issue affects Apache Superset: before 4.1.2. Users are recommended to upgrade to version 4.1.2, which fixes the issue.", "cve": "CVE-2025-48912", "id": "pyup.io-77692", "more_info_path": "/vulnerabilities/CVE-2025-48912/77692", "specs": [ "<4.1.2rc1" ], "v": "<4.1.2rc1" }, { "advisory": "Affected versions of the Apache Superset package are vulnerable to Information Disclosure due to improper access control on query metadata. The `/chart/data` endpoint returns a query field in its API response payload when guest users access charts, exposing database schema information, including table names that should not be accessible to low-privileged users.", "cve": "CVE-2025-55673", "id": "pyup.io-78845", "more_info_path": "/vulnerabilities/CVE-2025-55673/78845", "specs": [ "<4.1.3.post1" ], "v": "<4.1.3.post1" }, { "advisory": "Affected versions of the apache\u2011superset package are vulnerable to Cross\u2011site Scripting (XSS) due to improper sanitization of chart label inputs. The chart visualization module allows an authenticated user with edit\u2011chart permissions to inject a malicious payload into a chart\u2019s column label, which is not properly sanitized and executes when the victim hovers over the chart. An attacker with such access can exploit this by crafting a chart label containing script code, triggering execution in other users\u2019 browsers upon hover and potentially leading to session hijacking or arbitrary command execution on behalf of the user.", "cve": "CVE-2025-55672", "id": "pyup.io-78711", "more_info_path": "/vulnerabilities/CVE-2025-55672/78711", "specs": [ "<5.0.0" ], "v": "<5.0.0" }, { "advisory": "Affected versions of the Apache Superset package are vulnerable to Improper Input Validation due to insufficient filtering of SQL function calls. The DISALLOWED_SQL_FUNCTIONS security feature can be bypassed by using special inline blocks in SQL queries, allowing execution of functions that should be blocked by the denylist mechanism.", "cve": "CVE-2025-55674", "id": "pyup.io-78846", "more_info_path": "/vulnerabilities/CVE-2025-55674/78846", "specs": [ "<5.0.0" ], "v": "<5.0.0" }, { "advisory": "Affected versions of the Apache\u202fSuperset package are vulnerable to Improper Authorization due to insufficient access control in endpoints that allow ownership transfer. The API endpoints for dashboards, charts, and datasets fail to enforce proper authorization checks on ownership-related attributes, enabling authenticated read\u2011permission users to manipulate ownership. An attacker who is authenticated with only read permissions can exploit this by crafting requests to these endpoints to take over ownership of dashboards, charts or datasets, compromising data integrity, confidentiality, and availability.", "cve": "CVE-2025-55675", "id": "pyup.io-78710", "more_info_path": "/vulnerabilities/CVE-2025-55675/78710", "specs": [ "<5.0.0" ], "v": "<5.0.0" }, { "advisory": "An authenticated attacker with write CSS template permissions can create a record with specific HTML tags that will not get properly escaped by the toast message displayed when a user deletes that specific CSS template record. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.", "cve": "CVE-2022-43720", "id": "pyup.io-54625", "more_info_path": "/vulnerabilities/CVE-2022-43720/54625", "specs": [ "<=1.5.2", "==2.0.0" ], "v": "<=1.5.2,==2.0.0" }, { "advisory": "A vulnerability in the SQL Alchemy connector of Apache Superset allows an authenticated user with read access to a specific database to add subqueries to the WHERE and HAVING fields referencing tables on the same database that the user should not have access to, despite the user having the feature flag \"ALLOW_ADHOC_SUBQUERY\" disabled (default value). This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.", "cve": "CVE-2022-41703", "id": "pyup.io-54626", "more_info_path": "/vulnerabilities/CVE-2022-41703/54626", "specs": [ "<=1.5.2", "==2.0.0" ], "v": "<=1.5.2,==2.0.0" }, { "advisory": "Two legacy REST API endpoints for approval and request access are vulnerable to cross site request forgery. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.", "cve": "CVE-2022-43719", "id": "pyup.io-54612", "more_info_path": "/vulnerabilities/CVE-2022-43719/54612", "specs": [ "<=1.5.2", "==2.0.0" ], "v": "<=1.5.2,==2.0.0" }, { "advisory": "Upload data forms do not correctly render user input leading to possible XSS attack vectors that can be performed by authenticated users with database connection update permissions. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.", "cve": "CVE-2022-43718", "id": "pyup.io-54611", "more_info_path": "/vulnerabilities/CVE-2022-43718/54611", "specs": [ "<=1.5.2", "==2.0.0" ], "v": "<=1.5.2,==2.0.0" }, { "advisory": "When explicitly enabling the feature flag 'DASHBOARD_CACHE' (disabled by default), the system allowed for an unauthenticated user to access dashboard configuration metadata using a REST API Get endpoint. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.", "cve": "CVE-2022-45438", "id": "pyup.io-54614", "more_info_path": "/vulnerabilities/CVE-2022-45438/54614", "specs": [ "<=1.5.2", "==2.0.0" ], "v": "<=1.5.2,==2.0.0" }, { "advisory": "Dashboard rendering does not sufficiently sanitize the content of markdown components leading to possible XSS attack vectors that can be performed by authenticated users with create dashboard permissions. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.", "cve": "CVE-2022-43717", "id": "pyup.io-54616", "more_info_path": "/vulnerabilities/CVE-2022-43717/54616", "specs": [ "<=1.5.2", "==2.0.0" ], "v": "<=1.5.2,==2.0.0" }, { "advisory": "An authenticated attacker with update datasets permission could change a dataset link to an untrusted site, users could be redirected to this site when clicking on that specific dataset. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.", "cve": "CVE-2022-43721", "id": "pyup.io-54615", "more_info_path": "/vulnerabilities/CVE-2022-43721/54615", "specs": [ "<=1.5.2", "==2.0.0" ], "v": "<=1.5.2,==2.0.0" }, { "advisory": "A malicious actor who has been authenticated and granted specific permissions in Apache Superset may use the import dataset feature in order to conduct Server-Side Request Forgery attacks and query internal resources on behalf of the server where Superset\r\nis deployed. This vulnerability exists in Apache Superset versions up to and including 2.0.1.", "cve": "CVE-2023-25504", "id": "pyup.io-62896", "more_info_path": "/vulnerabilities/CVE-2023-25504/62896", "specs": [ "<=2.0.1" ], "v": "<=2.0.1" }, { "advisory": "An authenticated user with Gamma role authorization could have access to metadata information using non trivial methods in Apache Superset up to and including 2.0.1", "cve": "CVE-2023-27525", "id": "pyup.io-62902", "more_info_path": "/vulnerabilities/CVE-2023-27525/62902", "specs": [ "<=2.0.1" ], "v": "<=2.0.1" }, { "advisory": "Session Validation attacks in Apache Superset versions up to and including 2.0.1. Installations that have not altered the default configured SECRET_KEY according to installation instructions allow for an attacker to authenticate and access unauthorized resources. This does not affect Superset administrators who have changed the default value for SECRET_KEY config.", "cve": "CVE-2023-27524", "id": "pyup.io-62900", "more_info_path": "/vulnerabilities/CVE-2023-27524/62900", "specs": [ "<=2.0.1" ], "v": "<=2.0.1" }, { "advisory": "Improper REST API permission in Apache Superset up to and including 2.1.0 allows for an authenticated Gamma users to test network connections, possible SSRF.", "cve": "CVE-2023-36388", "id": "pyup.io-64998", "more_info_path": "/vulnerabilities/CVE-2023-36388/64998", "specs": [ "<=2.1.0" ], "v": "<=2.1.0" }, { "advisory": "Apache Superset would allow for SQLite database connections to be incorrectly registered when an attacker uses alternative driver names like\u00a0sqlite+pysqlite or by using database imports. This could allow for unexpected file creation on Superset webservers. Additionally, if Apache Superset is using a SQLite database for its metadata (not advised for production use) it could result in more severe vulnerabilities related to confidentiality and integrity.\u00a0This vulnerability exists in Apache Superset versions up to and including 2.1.0.", "cve": "CVE-2023-39265", "id": "pyup.io-65000", "more_info_path": "/vulnerabilities/CVE-2023-39265/65000", "specs": [ "<=2.1.0" ], "v": "<=2.1.0" }, { "advisory": "By default, stack traces for errors were enabled, which resulted in the exposure of internal traces on REST API endpoints to users.\u00a0This vulnerability exists in Apache Superset versions up to and including 2.1.0.", "cve": "CVE-2023-39264", "id": "pyup.io-64999", "more_info_path": "/vulnerabilities/CVE-2023-39264/64999", "specs": [ "<=2.1.0" ], "v": "<=2.1.0" }, { "advisory": "A non Admin authenticated user could incorrectly create resources using the import charts feature, on Apache Superset up to and including 2.1.0.", "cve": "CVE-2023-27526", "id": "pyup.io-62904", "more_info_path": "/vulnerabilities/CVE-2023-27526/62904", "specs": [ "<=2.1.0" ], "v": "<=2.1.0" }, { "advisory": "An improper default REST API permission for Gamma users in Apache Superset up to and including 2.1.0 allows for an authenticated Gamma user to test database connections.", "cve": "CVE-2023-36387", "id": "pyup.io-65024", "more_info_path": "/vulnerabilities/CVE-2023-36387/65024", "specs": [ "<=2.1.0" ], "v": "<=2.1.0" }, { "advisory": "Improper data authorization check on Jinja templated queries in Apache Superset\u00a0up to and including 2.1.0 allows for an authenticated user to issue queries on database tables they may not have access to.", "cve": "CVE-2023-27523", "id": "pyup.io-62898", "more_info_path": "/vulnerabilities/CVE-2023-27523/62898", "specs": [ "<=2.1.0" ], "v": "<=2.1.0" }, { "advisory": "In Apache Incubator Superset before 0.31 user could query database metadata information from a database it has no access to, by using a specially crafted complex query.", "cve": "CVE-2019-12413", "id": "pyup.io-54144", "more_info_path": "/vulnerabilities/CVE-2019-12413/54144", "specs": [ ">=0,<0.31.0" ], "v": ">=0,<0.31.0" }, { "advisory": "In Apache Incubator Superset before 0.32, a user can view database names that it has no access to on a dropdown list in SQLLab.", "cve": "CVE-2019-12414", "id": "pyup.io-54140", "more_info_path": "/vulnerabilities/CVE-2019-12414/54140", "specs": [ ">=0,<0.32.0" ], "v": ">=0,<0.32.0" }, { "advisory": "Cross-site Scripting (XSS) vulnerabilities have been detected in versions of apache-superset before 0.34.0, specifically through its Markup viz feature. XSS attacks manipulate a web application to execute malicious scripts on a client's browser, performing actions usually blocked by browser security, such as hijacking user sessions or exposing sensitive information. These attacks exploit the application\u2019s failure to sufficiently sanitize, validate, or escape user input, particularly special characters in dynamic content. Different XSS attacks include Stored, Reflected, DOM-based, and Mutated types, each with unique methods of injecting harmful code. To mitigate XSS risks, implementations should include sanitizing data inputs, encoding special characters, disabling client-side scripts where possible, redirecting invalid requests, detecting simultaneous logins, enforcing Content Security Policies, and understanding the security implications of third-party library usage.\r\nhttps://github.com/apache/superset/commit/0c5db55d55471c1c61c0750733733c157551b2d8", "cve": "PVE-2024-99797", "id": "pyup.io-66018", "more_info_path": "/vulnerabilities/PVE-2024-99797/66018", "specs": [ ">=0,<0.34.0" ], "v": ">=0,<0.34.0" }, { "advisory": "Apache Superset versions before 0.34.0 are susceptible to a Cross-site Scripting (XSS) vulnerability that involves an issue through FAB list views.\r\nhttps://github.com/apache/superset/commit/b62d7e3e8eaa80e201af3141fb4fe26c39e1ff79", "cve": "PVE-2024-99800", "id": "pyup.io-66015", "more_info_path": "/vulnerabilities/PVE-2024-99800/66015", "specs": [ ">=0,<0.34.0" ], "v": ">=0,<0.34.0" }, { "advisory": "Apache-superset versions before 0.34.0 are vulnerable to Cross-site Scripting (XSS) attacks. This vulnerability arises when user descriptions containing arbitrary HTML tags are accepted without proper validation, including the creation of malicious links via the `javascript:` protocol. XSS attacks exploit these oversights to execute unauthorized code or scripts in the context of a user's session, potentially leading to session hijacking, sensitive information exposure, or malware delivery. The main defense against such attacks involves sanitizing input data to escape special characters and validating or filtering all user inputs before they are reflected to the user. Strategies such as implementing a Content Security Policy, disabling client-side scripts, and ensuring proper session management can help mitigate the risk of XSS vulnerabilities.\r\nhttps://github.com/apache/superset/commit/4ff17ffc8de30c3813a81c80cf38d89d9da7a73d", "cve": "PVE-2024-99799", "id": "pyup.io-66016", "more_info_path": "/vulnerabilities/PVE-2024-99799/66016", "specs": [ ">=0,<0.34.0" ], "v": ">=0,<0.34.0" }, { "advisory": "The vulnerability threatens the security of apache-superset before 0.35.1, arising from insecure default settings that allow unrestricted metrics.\r\nhttps://github.com/apache/superset/commit/05b67673c3fdb4c94e5af5bc2fe83f1b227d7d08", "cve": "PVE-2024-99801", "id": "pyup.io-66014", "more_info_path": "/vulnerabilities/PVE-2024-99801/66014", "specs": [ ">=0,<0.35.1" ], "v": ">=0,<0.35.1" }, { "advisory": "In the course of work on the open source project it was discovered that authenticated users running queries against Hive and Presto database engines could access information via a number of templated fields including the contents of query description metadata database, the hashed version of the authenticated users\u2019 password, and access to connection information including the plaintext password for the current connection. It would also be possible to run arbitrary methods on the database connection object for the Presto or Hive connection, allowing the user to bypass security controls internal to Superset. This vulnerability is present in every Apache Superset version < 0.37.2.", "cve": "CVE-2020-13952", "id": "pyup.io-54228", "more_info_path": "/vulnerabilities/CVE-2020-13952/54228", "specs": [ ">=0,<0.37.2" ], "v": ">=0,<0.37.2" }, { "advisory": "Apache Superset up to and including 0.38.0 allowed the creation of a Markdown component on a Dashboard page for describing chart's related information. Abusing this functionality, a malicious user could inject javascript code executing unwanted action in the context of the user's browser. The javascript code will be automatically executed (Stored XSS) when a legitimate user surfs on the dashboard page. The vulnerability is exploitable creating a div section and embedding in it a svg element with javascript code.", "cve": "CVE-2021-27907", "id": "pyup.io-54300", "more_info_path": "/vulnerabilities/CVE-2021-27907/54300", "specs": [ ">=0,<0.38.1" ], "v": ">=0,<0.38.1" }, { "advisory": "Apache Superset prior to 1.1.0 allowed for the creation of an external URL that could be malicious. By not checking user input for open redirects the URL shortener functionality would allow for a malicious user to create a short URL for a dashboard that could convince the user to click the link.", "cve": "CVE-2021-28125", "id": "pyup.io-54265", "more_info_path": "/vulnerabilities/CVE-2021-28125/54265", "specs": [ ">=0,<1.1.0" ], "v": ">=0,<1.1.0" }, { "advisory": "Apache Superset up to and including 1.1 does not sanitize titles correctly on the Explore page. This allows an attacker with Explore access to save a chart with a malicious title, injecting html (including scripts) into the page.", "cve": "CVE-2021-32609", "id": "pyup.io-54353", "more_info_path": "/vulnerabilities/CVE-2021-32609/54353", "specs": [ ">=0,<1.2.0" ], "v": ">=0,<1.2.0" }, { "advisory": "Apache Superset up to and including 1.3.0 when configured with ENABLE_TEMPLATE_PROCESSING on (disabled by default) allowed SQL injection when a malicious authenticated user sends an http request with a custom URL.", "cve": "CVE-2021-41971", "id": "pyup.io-54351", "more_info_path": "/vulnerabilities/CVE-2021-41971/54351", "specs": [ ">=0,<1.3.1" ], "v": ">=0,<1.3.1" }, { "advisory": "Improper output neutralization for Logs. A specific Apache Superset HTTP endpoint allowed for an authenticated user to forge log entries or inject malicious content into logs.", "cve": "CVE-2021-42250", "id": "pyup.io-54375", "more_info_path": "/vulnerabilities/CVE-2021-42250/54375", "specs": [ ">=0,<1.3.2" ], "v": ">=0,<1.3.2" }, { "advisory": "Apache Superset up to and including 1.3.1 allowed for database connections password leak for authenticated users. This information could be accessed in a non-trivial way.", "cve": "CVE-2021-41972", "id": "pyup.io-54371", "more_info_path": "/vulnerabilities/CVE-2021-41972/54371", "specs": [ ">=0,<1.3.2" ], "v": ">=0,<1.3.2" }, { "advisory": "Apache Superset up to and including 1.3.2 allowed for registered database connections password leak for authenticated users. This information could be accessed in a non-trivial way. Users should upgrade to Apache Superset 1.4.0 or higher.", "cve": "CVE-2021-44451", "id": "pyup.io-54171", "more_info_path": "/vulnerabilities/CVE-2021-44451/54171", "specs": [ ">=0,<1.4.0" ], "v": ">=0,<1.4.0" }, { "advisory": "Apache Superset before 1.4.2 is vulnerable to SQL injection in chart data requests. Users should update to 1.4.2 or higher which addresses this issue.", "cve": "CVE-2022-27479", "id": "pyup.io-54435", "more_info_path": "/vulnerabilities/CVE-2022-27479/54435", "specs": [ ">=0,<1.4.2" ], "v": ">=0,<1.4.2" }, { "advisory": "Apache Superset up to 1.5.1 allowed for authenticated users to access metadata information related to datasets they have no permission on. This metadata included the dataset name, columns and metrics.", "cve": "CVE-2021-37839", "id": "pyup.io-54418", "more_info_path": "/vulnerabilities/CVE-2021-37839/54418", "specs": [ ">=0,<1.5.1" ], "v": ">=0,<1.5.1" }, { "advisory": "A where_in JINJA macro allows users to specify a quote, which combined with a carefully crafted statement would allow for SQL injection in Apache Superset.This issue affects Apache Superset: before 2.1.2, from 3.0.0 before 3.0.2. Users are recommended to upgrade to version 3.0.2, which fixes the issue.", "cve": "CVE-2023-49736", "id": "pyup.io-65196", "more_info_path": "/vulnerabilities/CVE-2023-49736/65196", "specs": [ ">=0,<2.1.3", ">=3.0.0,<3.0.2" ], "v": ">=0,<2.1.3,>=3.0.0,<3.0.2" }, { "advisory": "An authenticated Gamma user has the ability to create a dashboard and add charts to it, this user would automatically become one of the owners of the charts allowing him to incorrectly have write permissions to these charts.This issue affects Apache Superset: before 2.1.2, from 3.0.0 before 3.0.2. Users are recommended to upgrade to version 3.0.2 or 2.1.3, which fixes the issue.", "cve": "CVE-2023-49734", "id": "pyup.io-65195", "more_info_path": "/vulnerabilities/CVE-2023-49734/65195", "specs": [ ">=0,<2.1.3", ">=3.0.0,<3.0.2" ], "v": ">=0,<2.1.3,>=3.0.0,<3.0.2" }, { "advisory": "Uncontrolled resource consumption can be triggered by authenticated attacker that uploads a malicious ZIP to import database, dashboards or datasets. This vulnerability exists in Apache Superset versions up to and including 2.1.2 and versions 3.0.0, 3.0.1.", "cve": "CVE-2023-46104", "id": "pyup.io-65186", "more_info_path": "/vulnerabilities/CVE-2023-46104/65186", "specs": [ ">=0,<2.1.3", ">=3.0.0,<3.0.2" ], "v": ">=0,<2.1.3,>=3.0.0,<3.0.2" }, { "advisory": "A guest user could exploit a chart data REST API and send arbitrary SQL statements that on error could leak information from the underlying analytics database.", "cve": "CVE-2024-24772", "id": "pyup.io-68496", "more_info_path": "/vulnerabilities/CVE-2024-24772/68496", "specs": [ ">=0,<3.0.4", ">=3.1.0rc1,<3.1.1" ], "v": ">=0,<3.0.4,>=3.1.0rc1,<3.1.1" }, { "advisory": "Apache Superset with custom roles that include `can write on dataset` and without all data access permissions, allows for users to create virtual datasets to data they don't have access to. These users could then use those virtual datasets to get access to unauthorized data.", "cve": "CVE-2024-24779", "id": "pyup.io-68494", "more_info_path": "/vulnerabilities/CVE-2024-24779/68494", "specs": [ ">=0,<3.0.4", ">=3.1.0rc1,<3.1.1" ], "v": ">=0,<3.0.4,>=3.1.0rc1,<3.1.1" }, { "advisory": "An authenticated user with privileges to create Alerts on Alerts & Reports has the capability to generate a specially crafted SQL statement that triggers an error on the database. This error is not properly handled by Apache Superset and may inadvertently surface in the error log of the Alert exposing possibly sensitive data.", "cve": "CVE-2024-27315", "id": "pyup.io-68480", "more_info_path": "/vulnerabilities/CVE-2024-27315/68480", "specs": [ ">=0,<3.0.4", ">=3.1.0rc1,<3.1.1" ], "v": ">=0,<3.0.4,>=3.1.0rc1,<3.1.1" }, { "advisory": "Improper parsing of nested SQL statements on SQLLab would allow authenticated users to surpass their data authorization scope.", "cve": "CVE-2024-24773", "id": "pyup.io-68495", "more_info_path": "/vulnerabilities/CVE-2024-24773/68495", "specs": [ ">=0,<3.0.4", ">=3.1.0rc1,<3.1.1" ], "v": ">=0,<3.0.4,>=3.1.0rc1,<3.1.1" }, { "advisory": "A low privilege authenticated user could import an existing dashboard or chart that they do not have access to and then modify its metadata, thereby gaining ownership of the object. However, it's important to note that access to the analytical data of these charts and dashboards would still be subject to validation based on data access privileges.", "cve": "CVE-2024-26016", "id": "pyup.io-68490", "more_info_path": "/vulnerabilities/CVE-2024-26016/68490", "specs": [ ">=0,<3.0.4", ">=3.1.0rc1,<3.1.1" ], "v": ">=0,<3.0.4,>=3.1.0rc1,<3.1.1" }, { "advisory": "An Incorrect authorisation check in SQLLab in Apache Superset versions up to and including 2.1.0. This vulnerability allows an authenticated user to query tables that they do not have proper access to within Superset. The vulnerability can be exploited by leveraging a SQL parsing vulnerability.", "cve": "CVE-2023-32672", "id": "pyup.io-64672", "more_info_path": "/vulnerabilities/CVE-2023-32672/64672", "specs": [ ">=0,<=2.1.0" ], "v": ">=0,<=2.1.0" }, { "advisory": "An information disclosure issue was found in Apache Superset 0.34.0, 0.34.1, 0.35.0, and 0.35.1. Authenticated Apache Superset users are able to retrieve other users' information, including hashed passwords, by accessing an unused and undocumented API endpoint on Apache Superset.", "cve": "CVE-2020-1932", "id": "pyup.io-54193", "more_info_path": "/vulnerabilities/CVE-2020-1932/54193", "specs": [ ">=0.34.0,<0.35.2" ], "v": ">=0.34.0,<0.35.2" }, { "advisory": "An authenticated user with specific data permissions could access database connections stored passwords by requesting a specific REST API.\u00a0This issue affects Apache Superset version 1.3.0 up to 2.0.1.", "cve": "CVE-2023-30776", "id": "pyup.io-64173", "more_info_path": "/vulnerabilities/CVE-2023-30776/64173", "specs": [ ">=1.3.0,<=2.0.1" ], "v": ">=1.3.0,<=2.0.1" }, { "advisory": "Affected versions of Apache Superset are vulnerable to remote code execution due to crafted Python object persistence. An attacker gaining write access to the Superset metadata database can persist a malicious object that leads to execution on the web backend. The attack requires significant privileges to access an internal component.\r\nhttps://lists.apache.org/thread/6qk1zscc06yogxxfgz2bh2bvz6vh9g7h", "cve": "CVE-2023-37941", "id": "pyup.io-61038", "more_info_path": "/vulnerabilities/CVE-2023-37941/61038", "specs": [ ">=1.5.0,<=2.1.0" ], "v": ">=1.5.0,<=2.1.0" }, { "advisory": "Improper Authorization vulnerability in Apache Superset when FABADDSECURITY_API is enabled (disabled by default). Allows for lower privilege users to use this API.", "cve": "CVE-2024-53949", "id": "pyup.io-76389", "more_info_path": "/vulnerabilities/CVE-2024-53949/76389", "specs": [ ">=2.0.0,<4.1.0" ], "v": ">=2.0.0,<4.1.0" } ], "apache-tvm": [ { "advisory": "Apache-tvm 0.6 updates its Maven dependency 'checkstyle' requirements to versions [8.18,) to include a security fix.", "cve": "CVE-2019-9658", "id": "pyup.io-48121", "more_info_path": "/vulnerabilities/CVE-2019-9658/48121", "specs": [ "<0.6" ], "v": "<0.6" } ], "api-client-pydantic": [ { "advisory": "Api-client-pydantic 1.1.0 updates its dependency 'urllib3' to v1.26.4 to include a security fix.", "cve": "CVE-2021-28363", "id": "pyup.io-45389", "more_info_path": "/vulnerabilities/CVE-2021-28363/45389", "specs": [ "<1.1.0" ], "v": "<1.1.0" } ], "api-res-py": [ { "advisory": "Api-res-py 0.1 contains a backdoor due to the presence of the malicious 'request' dependency.\r\nhttps://www.bleepingcomputer.com/news/security/pypi-package-keep-mistakenly-included-a-password-stealer/", "cve": "CVE-2022-31313", "id": "pyup.io-49432", "more_info_path": "/vulnerabilities/CVE-2022-31313/49432", "specs": [ "==0.1" ], "v": "==0.1" } ], "apicolor": [ { "advisory": "Apicolor is a malicious package. It uses steganography to hide and install a backdoor in your system.\r\nhttps://www.darkreading.com/threat-intelligence/malicious-pypi-package-steganography-download-malware", "cve": "PVE-2023-53271", "id": "pyup.io-53271", "more_info_path": "/vulnerabilities/PVE-2023-53271/53271", "specs": [ ">=0" ], "v": ">=0" } ], "apidev-coop": [ { "advisory": "apidev-coop is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/", "cve": "PVE-2021-34979", "id": "pyup.io-34979", "more_info_path": "/vulnerabilities/PVE-2021-34979/34979", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "apify": [ { "advisory": "Apify 2.1.4 addresses a critical bug related to WebGL injection. It was causing the system to be detected and blocked by certain fingerprinting systems with Kasada protection. This fix improves the system's compatibility with such systems, enhancing overall performance and reliability.\r\nhttps://github.com/apify/fingerprint-suite/pull/100\r\nhttps://github.com/apify/fingerprint-suite/commit/0c4d05ae0c6badc441a53578a0ecdecd933294cb", "cve": "PVE-2024-63511", "id": "pyup.io-63511", "more_info_path": "/vulnerabilities/PVE-2024-63511/63511", "specs": [ "<2.1.4" ], "v": "<2.1.4" } ], "apimatic-core": [ { "advisory": "Apimatic-core 0.2.0 updates its dependency 'setuptools' to v65.5.1 to include a security fix.", "cve": "CVE-2022-40897", "id": "pyup.io-54870", "more_info_path": "/vulnerabilities/CVE-2022-40897/54870", "specs": [ "<0.2.0" ], "v": "<0.2.0" }, { "advisory": "Apimatic-core 0.2.3 updates its dependency 'requests' to version '2.31.0' to include a fix for an Information Exposure vulnerability.\r\nhttps://github.com/apimatic/core-lib-python/pull/40", "cve": "CVE-2023-32681", "id": "pyup.io-59862", "more_info_path": "/vulnerabilities/CVE-2023-32681/59862", "specs": [ "<0.2.3" ], "v": "<0.2.3" } ], "apimatic-requests-client-adapter": [ { "advisory": "Apimatic-requests-client-adapter 0.1.4 includes its dependency 'requests' to version '2.31.0' to include a fix for an Information Exposure vulnerability.\r\nhttps://github.com/apimatic/requests-client-adapter/pull/23\r\nhttps://github.com/apimatic/requests-client-adapter/commit/c8f0b7b71e1c3826492ce3aead3b81ed097eedf4", "cve": "CVE-2023-32681", "id": "pyup.io-60290", "more_info_path": "/vulnerabilities/CVE-2023-32681/60290", "specs": [ "<0.1.4" ], "v": "<0.1.4" } ], "apimeter": [ { "advisory": "Affected versions of the httprunner package are vulnerable to Cross-site Scripting (XSS) due to missing HTML escaping in the report template when rendering response fields. In httprunner/templates/report_template.html, the branch handling the \"json\" (and previously \"text\") response fields printed {{ value }} without the | e Jinja filter, allowing attacker-controlled markup to be embedded in the generated report; the fix changes this block to render
{{ value | e }}
and adds a regression test test_html_report_xss that uses a payload containing .", "cve": "PVE-2025-80904", "id": "pyup.io-80904", "more_info_path": "/vulnerabilities/PVE-2025-80904/80904", "specs": [ "<2.0.5" ], "v": "<2.0.5" }, { "advisory": "Affected versions of the HttpRunner package are vulnerable to Command Injection due to the use of eval() on user-controllable function names in parser.get_mapping_function. In httprunner/parser.py, get_mapping_function evaluates the function_name expression via eval(function_name) and returns any callable in scope (including attributes such as os.system or callables obtained via __import__), which are then invoked by parser.LazyString during template expansion.", "cve": "PVE-2025-80903", "id": "pyup.io-80903", "more_info_path": "/vulnerabilities/PVE-2025-80903/80903", "specs": [ "<2.1.3" ], "v": "<2.1.3" } ], "apischema": [ { "advisory": "Apischema 0.17.0 deprecates arbitrary exceptions in deserialization to avoid leaking implementation details if unwanted exceptions are not properly catched.\r\nhttps://github.com/wyfo/apischema/issues/233", "cve": "PVE-2021-43741", "id": "pyup.io-43741", "more_info_path": "/vulnerabilities/PVE-2021-43741/43741", "specs": [ "<0.17.0" ], "v": "<0.17.0" } ], "apispec": [ { "advisory": "In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used with untrusted data. The load() function has been deprecated in version 5.1 and the 'UnsafeLoader' has been introduced for backward compatibility with the function.", "cve": "CVE-2017-18342", "id": "pyup.io-42246", "more_info_path": "/vulnerabilities/CVE-2017-18342/42246", "specs": [ "<1.0.0b2" ], "v": "<1.0.0b2" } ], "apkleaks": [ { "advisory": "APKLeaks is an open-source project for scanning APK file for URIs, endpoints & secrets. APKLeaks prior to v2.0.3 allows remote attackers to execute arbitrary OS commands via package name inside application manifest. An attacker could include arguments that allow unintended commands or code to be executed, allow sensitive data to be read or modified or could cause other unintended behavior through malicious package name. The problem is fixed in version v2.0.6-dev and above.", "cve": "CVE-2021-21386", "id": "pyup.io-42302", "more_info_path": "/vulnerabilities/CVE-2021-21386/42302", "specs": [ "<2.0.6" ], "v": "<2.0.6" } ], "appdaemon": [ { "advisory": "Appdaemon 3.0.4 uses yaml.Safeloader to work around a known security issue with PyYaml.", "cve": "PVE-2021-37096", "id": "pyup.io-37096", "more_info_path": "/vulnerabilities/PVE-2021-37096/37096", "specs": [ "<3.0.4" ], "v": "<3.0.4" } ], "appdaemontestframework": [ { "advisory": "Appdaemontestframework 2.0.1 updates the minimum requirement for its dependency 'requests' to >=2.20.0 to include a security fix.", "cve": "CVE-2018-18074", "id": "pyup.io-45791", "more_info_path": "/vulnerabilities/CVE-2018-18074/45791", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Appdaemontestframework 2.0.1 updates the minimum requirement for its dependency 'pyyaml' to >=4.2b1 to include a security fix.", "cve": "CVE-2017-18342", "id": "pyup.io-37908", "more_info_path": "/vulnerabilities/CVE-2017-18342/37908", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Appdaemontestframework 2.3.3 updates its dependency 'jinja2' to v2.10.1 to include a security fix.", "cve": "CVE-2019-10906", "id": "pyup.io-37907", "more_info_path": "/vulnerabilities/CVE-2019-10906/37907", "specs": [ "<2.3.3" ], "v": "<2.3.3" }, { "advisory": "Appdaemontestframework 2.3.3 updates its dependency 'typed-ast ' to v1.4.0 to include security fixes.", "cve": "CVE-2019-19274", "id": "pyup.io-44970", "more_info_path": "/vulnerabilities/CVE-2019-19274/44970", "specs": [ "<2.3.3" ], "v": "<2.3.3" }, { "advisory": "Appdaemontestframework 2.3.3 updates its dependency 'urllib3' to v1.25.3 to include security fixes.", "cve": "CVE-2019-11236", "id": "pyup.io-44969", "more_info_path": "/vulnerabilities/CVE-2019-11236/44969", "specs": [ "<2.3.3" ], "v": "<2.3.3" }, { "advisory": "Appdaemontestframework 2.3.3 updates its dependency 'urllib3' to v1.25.3 to include security fixes.", "cve": "CVE-2019-11324", "id": "pyup.io-44968", "more_info_path": "/vulnerabilities/CVE-2019-11324/44968", "specs": [ "<2.3.3" ], "v": "<2.3.3" }, { "advisory": "Appdaemontestframework 2.3.3 updates its dependency 'jinja2' to v2.10.1 to include a security fix.", "cve": "CVE-2019-19275", "id": "pyup.io-44971", "more_info_path": "/vulnerabilities/CVE-2019-19275/44971", "specs": [ "<2.3.3" ], "v": "<2.3.3" } ], "appfl": [ { "advisory": "Appfl 0.4.0 mitigates race condition vulnerabilities in its Globus Communication file system. The previous version allowed concurrent attempts by multiple clients to download the MNIST dataset and the global model to the same directories, leading to potential data corruption. This version introduces a pre-download script for the MNIST dataset and assigns unique output directories for each client, preventing simultaneous write operations to the same file and enhancing overall application robustness.\r\nhttps://github.com/APPFL/APPFL/pull/158", "cve": "PVE-2024-63217", "id": "pyup.io-63217", "more_info_path": "/vulnerabilities/PVE-2024-63217/63217", "specs": [ "<0.4.0" ], "v": "<0.4.0" } ], "apphelpers": [ { "advisory": "To secure the API access, apphelpers 0.9.2 adds the new options `groups_forbidden` and `groups_required`.", "cve": "PVE-2021-37151", "id": "pyup.io-37151", "more_info_path": "/vulnerabilities/PVE-2021-37151/37151", "specs": [ "<0.9.2" ], "v": "<0.9.2" } ], "appia": [ { "advisory": "Appia 5.3 removes the usage of hardcoded credentials in docker-compose.\r\nhttps://github.com/PlethoraChutney/Appia/commit/82c65d7dcfe1cc064abcb29980ed49e92488174a", "cve": "PVE-2022-52425", "id": "pyup.io-52425", "more_info_path": "/vulnerabilities/PVE-2022-52425/52425", "specs": [ "<5.3" ], "v": "<5.3" } ], "apprise": [ { "advisory": "Apprise is an open source library which allows you to send a notification to almost all of the most popular notification services available. In affected versions users who use Apprise granting them access to the IFTTT plugin (which just comes out of the box) are subject to a denial of service attack on an inefficient regular expression. The vulnerable regular expression is [here](https://github.com/caronc/apprise/blob/0007eade20934ddef0aba38b8f1aad980cfff253/apprise/plugins/NotifyIFTTT.py#L356-L359). The problem has been patched in release version 0.9.5.1. Users who are unable to upgrade are advised to remove `apprise/plugins/NotifyIFTTT.py` to eliminate the service.", "cve": "CVE-2021-39229", "id": "pyup.io-54335", "more_info_path": "/vulnerabilities/CVE-2021-39229/54335", "specs": [ ">=0.7.7,<0.9.5.1" ], "v": ">=0.7.7,<0.9.5.1" } ], "appwrite": [ { "advisory": "Appwrite (SDK for Python) version 0.5.0 adds support for appwrite 0.10.0. Appwrite 0.9.4 fixed a security vulnerability that exposes project ID's from other admin users.", "cve": "PVE-2021-41261", "id": "pyup.io-41261", "more_info_path": "/vulnerabilities/PVE-2021-41261/41261", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Affected versions of the appwrite (PyPI) and appwrite-cli (npm) packages are vulnerable to Information Disclosure due to hard-coded credential storage with overly permissive file permissions. The login command in the Appwrite CLI stores Appwrite user credentials in the ~/.appwrite/prefs.json file with UNIX file mode 0644, allowing any user on the local system to read sensitive information. An attacker with local access can exploit this by reading the prefs.json file to obtain user credentials, compromising the confidentiality of the Appwrite user account.", "cve": "CVE-2023-50974", "id": "pyup.io-78712", "more_info_path": "/vulnerabilities/CVE-2023-50974/78712", "specs": [ "<3.0.0" ], "v": "<3.0.0" } ], "aptdaemon": [ { "advisory": "There is no input validation on the Locale property in an apt transaction. An unprivileged user can supply a full path to a writable directory, which lets aptd read a file as root. Having a symlink in place results in an error message if the file exists, and no error otherwise. This way an unprivileged user can check for the existence of any files on the system as root.", "cve": "CVE-2020-15703", "id": "pyup.io-70576", "more_info_path": "/vulnerabilities/CVE-2020-15703/70576", "specs": [ "<=1.1.1" ], "v": "<=1.1.1" } ], "aqtinstall": [ { "advisory": "Aqtinstall 2.1.0 uses SHA-256 checksums from trusted mirrors only.\r\nhttps://github.com/miurahr/aqtinstall/pull/493", "cve": "PVE-2022-48137", "id": "pyup.io-48137", "more_info_path": "/vulnerabilities/PVE-2022-48137/48137", "specs": [ "<2.1.0" ], "v": "<2.1.0" }, { "advisory": "Aqtinstall 2.1.0rc2 uses 'defusedxml' instead of 'xml.etree.ElementTree' to avoid XXE attacks.\r\nhttps://github.com/miurahr/aqtinstall/commit/745e6a25e46411ff526387615a1db51a6ba968e0", "cve": "CVE-2013-1664", "id": "pyup.io-47852", "more_info_path": "/vulnerabilities/CVE-2013-1664/47852", "specs": [ "<2.1.0rc2" ], "v": "<2.1.0rc2" }, { "advisory": "Aqtinstall 2.1.0rc2 uses 'secrets' instead of 'random' module to generate cryptographically safe numbers.\r\nhttps://github.com/miurahr/aqtinstall/commit/745e6a25e46411ff526387615a1db51a6ba968e0", "cve": "PVE-2022-47013", "id": "pyup.io-47013", "more_info_path": "/vulnerabilities/PVE-2022-47013/47013", "specs": [ "<2.1.0rc2" ], "v": "<2.1.0rc2" }, { "advisory": "Aqtinstall 2.1.0rc2 uses 'defusedxml' instead of 'xml.etree.ElementTree' to avoid XXE attacks.\r\nhttps://github.com/miurahr/aqtinstall/commit/745e6a25e46411ff526387615a1db51a6ba968e0", "cve": "CVE-2013-1665", "id": "pyup.io-54874", "more_info_path": "/vulnerabilities/CVE-2013-1665/54874", "specs": [ "<2.1.0rc2" ], "v": "<2.1.0rc2" } ], "aquilify": [ { "advisory": "Aquilify version 1.12.0 has enhanced its CSRF middleware protection, strengthening defenses against potential security vulnerabilities.", "cve": "PVE-2024-65762", "id": "pyup.io-65762", "more_info_path": "/vulnerabilities/PVE-2024-65762/65762", "specs": [ "<1.12.0" ], "v": "<1.12.0" } ], "arcade-mcp-server": [ { "advisory": "Affected versions of the arcade-mcp-server package are vulnerable to Improper Access Control due to a hardcoded default worker secret that is accepted without validation or rotation. The ArcadeSettings.server_secret field defaults to the publicly documented value \"dev\", which is passed by create_arcade_mcp() into FastAPIWorker and then into BaseWorker._set_secret() as the HS256 signing key, causing the FastAPI auth middleware in arcade_serve/fastapi/auth.py and the core auth layer in arcade_serve/core/auth.py to trust any JWT signed with this constant secret and thereby grant access to all /worker/* HTTP endpoints.", "cve": "CVE-2025-66454", "id": "pyup.io-82237", "more_info_path": "/vulnerabilities/CVE-2025-66454/82237", "specs": [ "<1.9.1" ], "v": "<1.9.1" } ], "arches": [ { "advisory": "### Impact\nWith a carefully crafted web request, it's possible to execute certain unwanted sql statements against the database. \nAnyone running the impacted versions (<=6.1.1, 6.2.0, >=7.0.0, <=7.1.1) should upgrade as soon as possible.\n\n### Patches\nThe problem has been patched in the following versions: [6.1.2](https://pypi.org/project/arches/6.1.2/), [6.2.1](https://pypi.org/project/arches/6.2.1/), and [7.2.0](https://pypi.org/project/arches/7.2.0/)\nUsers are strongly urged to upgrade to the most recent relevant patch.\n\n### Workarounds\nThere are no workarounds.\n\n### General References \nhttps://www.w3schools.com/sql/sql_injection.asp\nhttps://en.wikipedia.org/wiki/SQL_injection\n\n### For more information\nPost any questions to the [Arches project forum](https://community.archesproject.org/).\n", "cve": "CVE-2022-41892", "id": "pyup.io-54561", "more_info_path": "/vulnerabilities/CVE-2022-41892/54561", "specs": [ ">=0,<6.1.2", ">=6.2.0,<6.2.1", ">=7.0.0,<7.2.0" ], "v": ">=0,<6.1.2,>=6.2.0,<6.2.1,>=7.0.0,<7.2.0" } ], "archi": [ { "advisory": "Archi 0.2.2 is bundled with libarchive 3.4.2. However, libarchive before version 3.4.3 is known to not be secure. See: .", "cve": "PVE-2021-37702", "id": "pyup.io-37702", "more_info_path": "/vulnerabilities/PVE-2021-37702/37702", "specs": [ "<=0.2.2" ], "v": "<=0.2.2" } ], "archinstall": [ { "advisory": "Archinstall 2.4.0.rc1 splits 'disk_layouts', 'creds' and 'conf' data into separate files to comply with security concerns when sharing user configurations publicly.", "cve": "PVE-2022-47799", "id": "pyup.io-47799", "more_info_path": "/vulnerabilities/PVE-2022-47799/47799", "specs": [ "<2.4.0.rc1" ], "v": "<2.4.0.rc1" } ], "archivebox": [ { "advisory": "Affected versions of Archivebox are vulnerable to Improper Authorization.", "cve": "PVE-2024-73588", "id": "pyup.io-73588", "more_info_path": "/vulnerabilities/PVE-2024-73588/73588", "specs": [ "<0.8.3rc" ], "v": "<0.8.3rc" }, { "advisory": "ArchiveBox is an open source self-hosted web archiving system. Any users who are using the `wget` extractor and view the content it outputs. The impact is potentially severe if you are logged in to the ArchiveBox admin site in the same browser session and view an archived malicious page designed to target your ArchiveBox instance. Malicious Javascript could potentially act using your logged-in admin credentials and add/remove/modify snapshots, add/remove/modify ArchiveBox users, and generally do anything an admin user could do. The impact is less severe for non-logged-in users, as malicious Javascript cannot *modify* any archives, but it can still *read* all the other archived content by fetching the snapshot index and iterating through it. Because all of ArchiveBox's archived content is served from the same host and port as the admin panel, when archived pages are viewed the JS executes in the same context as all the other archived pages (and the admin panel), defeating most of the browser's usual CORS/CSRF security protections and leading to this issue. A patch is being developed in https://github.com/ArchiveBox/ArchiveBox/issues/239. As a mitigation for this issue would be to disable the wget extractor by setting `archivebox config --set SAVE_WGET=False`, ensure you are always logged out, or serve only a [static HTML version](https://github.com/ArchiveBox/ArchiveBox/wiki/Publishing-Your-Archive#2-export-and-host-it-as-static-html) of your archive.", "cve": "CVE-2023-45815", "id": "pyup.io-65386", "more_info_path": "/vulnerabilities/CVE-2023-45815/65386", "specs": [ ">=0" ], "v": ">=0" } ], "archivy": [ { "advisory": "Archivy 1.0.1 includes a fix for a path traversal vulnerability.\r\nhttps://github.com/archivy/archivy/pull/201", "cve": "PVE-2023-59112", "id": "pyup.io-59112", "more_info_path": "/vulnerabilities/PVE-2023-59112/59112", "specs": [ "<1.0.1" ], "v": "<1.0.1" }, { "advisory": "Archivy 1.6.2 improves CSRF protection for delete actions.\r\nhttps://github.com/archivy/archivy/commit/796c3ae318eea183fc88c87ec5a27355b0f6a99d", "cve": "CVE-2021-4162", "id": "pyup.io-44511", "more_info_path": "/vulnerabilities/CVE-2021-4162/44511", "specs": [ "<1.6.2" ], "v": "<1.6.2" }, { "advisory": "Archivy 1.7.2 includes a fix for a path traversal vulnerability.\r\nhttps://github.com/archivy/archivy/commit/dedc5a0b214acf2a25e0300304dabb46def4eef1", "cve": "PVE-2023-59125", "id": "pyup.io-59125", "more_info_path": "/vulnerabilities/PVE-2023-59125/59125", "specs": [ "<1.7.2" ], "v": "<1.7.2" }, { "advisory": "Archivy prior to version 1.7.1 is vulnerable to open redirect.", "cve": "CVE-2022-0697", "id": "pyup.io-54269", "more_info_path": "/vulnerabilities/CVE-2022-0697/54269", "specs": [ ">=0,<1.7.1" ], "v": ">=0,<1.7.1" } ], "archmage": [ { "advisory": "Directory traversal vulnerability in arCHMage 0.2.4 allows remote attackers to write to arbitrary files via a .. (dot dot) in a CHM file.", "cve": "CVE-2015-1589", "id": "pyup.io-25630", "more_info_path": "/vulnerabilities/CVE-2015-1589/25630", "specs": [ "<0.3.1" ], "v": "<0.3.1" } ], "arcticdb": [ { "advisory": "Arcticdb 3.0.0 includes a fix for an information disclosure vulnerability: Azure and S3 write credentials are stored in plaintext.\r\nhttps://github.com/man-group/ArcticDB/issues/802", "cve": "PVE-2023-61148", "id": "pyup.io-61148", "more_info_path": "/vulnerabilities/PVE-2023-61148/61148", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "Affected versions of ArcticDB are potentially vulnerable to a race condition (CWE-362). It stems from unsynchronized Py_INCREF(Py_None) calls in functions like prefill_with_none and increment_none_refcount in python_utils.hpp.", "cve": "PVE-2025-76942", "id": "pyup.io-76942", "more_info_path": "/vulnerabilities/PVE-2025-76942/76942", "specs": [ "<5.4.0" ], "v": "<5.4.0" } ], "argilla": [ { "advisory": "Argilla 0.13.0 stops requiring its NPM dependency 'node-sass' to avoid security issues.", "cve": "CVE-2019-18797", "id": "pyup.io-52811", "more_info_path": "/vulnerabilities/CVE-2019-18797/52811", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Argilla 0.13.0 stops requiring its NPM dependency 'node-sass' to avoid security issues.", "cve": "CVE-2019-18799", "id": "pyup.io-52809", "more_info_path": "/vulnerabilities/CVE-2019-18799/52809", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Argilla 0.13.0 stops requiring its NPM dependency 'node-sass' to avoid security issues.", "cve": "CVE-2018-19827", "id": "pyup.io-52813", "more_info_path": "/vulnerabilities/CVE-2018-19827/52813", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Argilla 0.13.0 stops requiring its NPM dependency 'node-sass' to avoid security issues.", "cve": "CVE-2018-11694", "id": "pyup.io-52815", "more_info_path": "/vulnerabilities/CVE-2018-11694/52815", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Argilla 0.13.0 stops requiring its NPM dependency 'node-sass' to avoid security issues.", "cve": "CVE-2019-18798", "id": "pyup.io-52810", "more_info_path": "/vulnerabilities/CVE-2019-18798/52810", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Argilla 0.13.0 stops requiring its NPM dependency 'node-sass' to avoid security issues.", "cve": "CVE-2018-19839", "id": "pyup.io-52812", "more_info_path": "/vulnerabilities/CVE-2018-19839/52812", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Argilla 0.13.0 stops requiring its NPM dependency 'node-sass' to avoid security issues.", "cve": "CVE-2020-24025", "id": "pyup.io-52782", "more_info_path": "/vulnerabilities/CVE-2020-24025/52782", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Argilla 0.13.0 stops requiring its NPM dependency 'node-sass' to avoid security issues.", "cve": "CVE-2019-6284", "id": "pyup.io-52808", "more_info_path": "/vulnerabilities/CVE-2019-6284/52808", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Argilla 0.13.0 stops requiring its NPM dependency 'node-sass' to avoid security issues.", "cve": "CVE-2018-20822", "id": "pyup.io-52814", "more_info_path": "/vulnerabilities/CVE-2018-20822/52814", "specs": [ "<0.13.0" ], "v": "<0.13.0" } ], "argo-workflows": [ { "advisory": "Affected versions of workflow/executor/docker are vulnerable to improper error handling. The impact of this vulnerability is that errors from 'docker kill' and 'docker wait' are ignored and logged as warnings, potentially masking underlying issues. Attackers cannot exploit this directly but could mislead debugging efforts or hide termination-related issues in the containers. Vulnerable functions include Kill(). Exploitability is low due to the nature of the issue being related to error reporting rather than execution. To mitigate this, ensure proper error reporting and handle specific error cases rather than ignoring them.", "cve": "PVE-2024-63763", "id": "pyup.io-63763", "more_info_path": "/vulnerabilities/PVE-2024-63763/63763", "specs": [ "<2.6.0" ], "v": "<2.6.0" }, { "advisory": "Argo-workflows 6.4.0rc1 (Python SDK) is compatible with Argo-workflows core v3.4.0rc1, that fixes a potential XSS vulnerability.\r\nhttps://github.com/argoproj/argo-workflows/pull/8289/commits/e78b1c9b840ea89a28e03d8aa0d5f9f1629c0c86", "cve": "PVE-2022-50679", "id": "pyup.io-50679", "more_info_path": "/vulnerabilities/PVE-2022-50679/50679", "specs": [ "<6.4.0rc1" ], "v": "<6.4.0rc1" } ], "argus-overview": [ { "advisory": "Affected versions of this package are vulnerable to Path Traversal attacks. The `character_manager.py` module uses character names directly in file operations without sanitization, allowing attackers to inject directory traversal sequences into character names. An attacker can exploit this vulnerability by creating or importing characters with malicious names containing a path traversal sequence, leading to file operations being performed outside the intended character data directory, enabling unauthorized file read, write, or deletion of arbitrary files on the system.", "cve": "PVE-2026-85181", "id": "pyup.io-85181", "more_info_path": "/vulnerabilities/PVE-2026-85181/85181", "specs": [ "<2.8.5" ], "v": "<2.8.5" } ], "aries-cloudagent": [ { "advisory": "Affected versions of Aries-cloudagent are receiving unauthenticated DIDComm messages from connections in the invitation state.", "cve": "PVE-2024-72483", "id": "pyup.io-72483", "more_info_path": "/vulnerabilities/PVE-2024-72483/72483", "specs": [ "<0.11.2" ], "v": "<0.11.2" }, { "advisory": "Aries-cloudagent 0.12.0 upgrades its readthedocs-sphinx-search from 0.1.1 to 1.3.2 in response to GHSA-xgfm-fjx6-62mj: This vulnerability could have let attackers insert arbitrary HTML into search results via a crafted search query, due to inadequate escaping of user content.", "cve": "PVE-2024-67615", "id": "pyup.io-67615", "more_info_path": "/vulnerabilities/PVE-2024-67615/67615", "specs": [ "<0.12.0" ], "v": "<0.12.0" }, { "advisory": "Aries-cloudagent is affected by a Insufficient Verification of Data Authenticity vulnerability. When verifying W3C Format Verifiable Credentials using JSON-LD with Linked Data Proofs (LDP-VCs), the result of verifying the presentation 'document.proof' was not factored into the final 'verified' value ('true'/'false') on the presentation record. The flaw enables holders of W3C Format Verifiable Credentials using JSON-LD with Linked Data Proofs (LDPs) to present incorrectly constructed proofs, and allows malicious verifiers to save and replay a presentation from such holders as their own.\r\nhttps://github.com/hyperledger/aries-cloudagent-python/security/advisories/GHSA-97x9-59rv-q5pm", "cve": "CVE-2024-21669", "id": "pyup.io-64225", "more_info_path": "/vulnerabilities/CVE-2024-21669/64225", "specs": [ ">=0.11.0rc1,<0.11.0", ">=0.7.0rc0,<0.10.5" ], "v": ">=0.11.0rc1,<0.11.0,>=0.7.0rc0,<0.10.5" } ], "arjun": [ { "advisory": "Arjun 2.1.5 includes fixes for catastrophic backtracking vulnerabilities.\r\nhttps://github.com/s0md3v/Arjun/commit/0f5be57c3f82e6004f1224f9c797f2fca838493c", "cve": "PVE-2023-62351", "id": "pyup.io-62351", "more_info_path": "/vulnerabilities/PVE-2023-62351/62351", "specs": [ "<2.1.5" ], "v": "<2.1.5" } ], "arrayfire": [ { "advisory": "An issue was discovered in the arrayfire crate before 3.6.0 for Rust. Addition of the repr() attribute to an enum is mishandled, leading to memory corruption.", "cve": "CVE-2018-20998", "id": "pyup.io-54024", "more_info_path": "/vulnerabilities/CVE-2018-20998/54024", "specs": [ ">=0,<3.6.0" ], "v": ">=0,<3.6.0" } ], "arrendatools.plantillas": [ { "advisory": "Arrendatools.plantillas version 0.4.3 updates the plantilla to automatically escape content, setting autoscape to True.\r\nhttps://github.com/hokus15/ArrendaToolsPlantillas/commit/75878a8a5a2e505f8aaa7b86e2b764a42034d940", "cve": "PVE-2024-66926", "id": "pyup.io-66926", "more_info_path": "/vulnerabilities/PVE-2024-66926/66926", "specs": [ "<0.4.3" ], "v": "<0.4.3" } ], "arrnounced": [ { "advisory": "Arrnounced 0.4 replaces XML parser with defusedxml to prevent XML attacks.\r\nhttps://github.com/weannounce/arrnounced/commit/5a1d186b32162b317b1762b8602342b0b3050bda", "cve": "CVE-2013-1665", "id": "pyup.io-43754", "more_info_path": "/vulnerabilities/CVE-2013-1665/43754", "specs": [ "<0.4" ], "v": "<0.4" }, { "advisory": "Arrnounced 0.4 replaces XML parser with defusedxml to prevent XML attacks.\r\nhttps://github.com/weannounce/arrnounced/commit/5a1d186b32162b317b1762b8602342b0b3050bda", "cve": "CVE-2013-1664", "id": "pyup.io-54877", "more_info_path": "/vulnerabilities/CVE-2013-1664/54877", "specs": [ "<0.4" ], "v": "<0.4" } ], "arrow-pd-parser": [ { "advisory": "Arrow-pd-parser 1.3.0 updates its dependency 'numpy' to v1.23.1 to include security fixes.", "cve": "CVE-2021-41496", "id": "pyup.io-50592", "more_info_path": "/vulnerabilities/CVE-2021-41496/50592", "specs": [ "<1.3.0" ], "v": "<1.3.0" }, { "advisory": "Arrow-pd-parser 1.3.0 updates its dependency 'numpy' to v1.23.1 to include security fixes.", "cve": "CVE-2021-34141", "id": "pyup.io-50586", "more_info_path": "/vulnerabilities/CVE-2021-34141/50586", "specs": [ "<1.3.0" ], "v": "<1.3.0" }, { "advisory": "Arrow-pd-parser 1.3.0 updates its dependency 'numpy' to v1.23.1 to include security fixes.", "cve": "CVE-2021-41495", "id": "pyup.io-50591", "more_info_path": "/vulnerabilities/CVE-2021-41495/50591", "specs": [ "<1.3.0" ], "v": "<1.3.0" }, { "advisory": "Arrow-pd-parser 2.0.0 updates its dependency 'pyarrow' to versions \">=14.0.0\" to include a security fix.", "cve": "CVE-2023-47248", "id": "pyup.io-62350", "more_info_path": "/vulnerabilities/CVE-2023-47248/62350", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "artifact-lab-3-package-24ddbc49": [ { "advisory": "The OpenSSF Package Analysis project identified 'artifact-lab-3-package-24ddbc49' @ 0.7.0 (pypi) as malicious.", "cve": "PVE-2024-73971", "id": "pyup.io-73971", "more_info_path": "/vulnerabilities/PVE-2024-73971/73971", "specs": [ "<=0", ">=0" ], "v": "<=0,>=0" } ], "artifact-lab-3-package-3eef6c2c": [ { "advisory": "The artifact-lab-3-package-3eef6c2c has been flagged as malicious due to communication with a domain linked to unauthorized activities, potentially compromising system security. The package contains malicious code, raising concerns about its integrity. Immediate action is required to remove this package and replace it with a trusted alternative to prevent unauthorized access and safeguard sensitive information.", "cve": "PVE-2024-72964", "id": "pyup.io-72964", "more_info_path": "/vulnerabilities/PVE-2024-72964/72964", "specs": [ ">=0", "<=0" ], "v": ">=0,<=0" } ], "artifact-lab-3-package-4c04b1a2": [ { "advisory": "Artifact-lab-3-package-4c04b1a2 communicates with a domain associated with malicious activity.", "cve": "PVE-2024-73279", "id": "pyup.io-73279", "more_info_path": "/vulnerabilities/PVE-2024-73279/73279", "specs": [ ">=0", "<=0" ], "v": ">=0,<=0" } ], "aryi": [ { "advisory": "Aryi is a malicious package. It steals users' credit card numbers and Discord tokens.\r\nhttps://www.bleepingcomputer.com/news/security/pypi-packages-caught-stealing-credit-card-numbers-discord-tokens/", "cve": "PVE-2022-45478", "id": "pyup.io-45478", "more_info_path": "/vulnerabilities/PVE-2022-45478/45478", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "ascender-framework": [ { "advisory": "Affected versions of the AscenderFramework package are vulnerable to Authentication Bypass due to get_authenticated_user falling back to user ID 0 when the user claim is missing from the decoded session.", "cve": "PVE-2025-80511", "id": "pyup.io-80511", "more_info_path": "/vulnerabilities/PVE-2025-80511/80511", "specs": [ "<1.1.1" ], "v": "<1.1.1" } ], "asciidoc": [ { "advisory": "Asciidoc 8.6.6 removes the use of 'eval()' on untrusted input to disallow malicious code execution.", "cve": "PVE-2021-39514", "id": "pyup.io-39514", "more_info_path": "/vulnerabilities/PVE-2021-39514/39514", "specs": [ "<8.6.6" ], "v": "<8.6.6" } ], "asgi-csrf": [ { "advisory": "Cookie values in asgi-csrf 0.3 are now signed to prevent subdomain attacks. See also: .", "cve": "PVE-2021-38376", "id": "pyup.io-38376", "more_info_path": "/vulnerabilities/PVE-2021-38376/38376", "specs": [ "<0.3" ], "v": "<0.3" } ], "askbot": [ { "advisory": "Affected versions of the askbot package are vulnerable to Authorization Bypass Through User-Controlled Key due to an incorrect permission check in the avatar update logic. In askbot/views/avatar_views.py, the admin_or_owner_required decorator compares request.user.id to the user_id URL parameter and, when the check fails, incorrectly delegates to login_required(func), allowing any authenticated user to reach the protected avatar view path.", "cve": "CVE-2026-1213", "id": "pyup.io-85245", "more_info_path": "/vulnerabilities/CVE-2026-1213/85245", "specs": [ "<0.12.3" ], "v": "<0.12.3" }, { "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in Askbot before 0.7.49 allow remote attackers to inject arbitrary web script or HTML via vectors related to the (1) tag or (2) user search forms.", "cve": "CVE-2014-2236", "id": "pyup.io-70425", "more_info_path": "/vulnerabilities/CVE-2014-2236/70425", "specs": [ "<0.7.49" ], "v": "<0.7.49" }, { "advisory": "Cross-site scripting (XSS) vulnerability in Askbot before 0.7.49 allows remote attackers to inject arbitrary web script or HTML via vectors related to the question search form.", "cve": "CVE-2014-2235", "id": "pyup.io-70426", "more_info_path": "/vulnerabilities/CVE-2014-2235/70426", "specs": [ "<0.7.49" ], "v": "<0.7.49" } ], "aspeak": [ { "advisory": "Aspeak 6.0.0 updates its dependency 'openssl' to version '0.10.55' to include a security fix.\r\nhttps://github.com/kxxt/aspeak/pull/76\r\nhttps://github.com/kxxt/aspeak/commit/17cbe32ed4c17bc57683688390691686946a4cbc\r\nhttps://github.com/advisories/GHSA-xcf7-rvmh-g6q4", "cve": "PVE-2023-59242", "id": "pyup.io-59242", "more_info_path": "/vulnerabilities/PVE-2023-59242/59242", "specs": [ "<6.0.0" ], "v": "<6.0.0" }, { "advisory": "Aspeak 6.0.1 updates CARGO dependencies to resolve a vulnerability affecting 'atty'.\r\nhttps://github.com/advisories/GHSA-g98v-hv3f-hcfr\r\nhttps://github.com/kxxt/aspeak/issues/79", "cve": "PVE-2023-61556", "id": "pyup.io-61556", "more_info_path": "/vulnerabilities/PVE-2023-61556/61556", "specs": [ "<6.0.1" ], "v": "<6.0.1" } ], "aspen": [ { "advisory": "Aspen 0.39 fixes two security bugs related to CRLF injection - https://github.com/gratipay/security-qf35us/issues/1", "cve": "PVE-2021-36873", "id": "pyup.io-36873", "more_info_path": "/vulnerabilities/PVE-2021-36873/36873", "specs": [ "<0.39" ], "v": "<0.39" }, { "advisory": "Aspen 0.42 protects against URL redirection attacks.\r\nhttps://github.com/AspenWeb/aspen.py/commit/3c98f54b431d1325f92923144027b942bf679896", "cve": "PVE-2021-36872", "id": "pyup.io-36872", "more_info_path": "/vulnerabilities/PVE-2021-36872/36872", "specs": [ "<0.42" ], "v": "<0.42" }, { "advisory": "Directory traversal vulnerability in Aspen before 0.22 allows remote attackers to read arbitrary files via a .. (dot dot) to the default URI.", "cve": "CVE-2013-2619", "id": "pyup.io-65806", "more_info_path": "/vulnerabilities/CVE-2013-2619/65806", "specs": [ ">=0.9.18,<0.22" ], "v": ">=0.9.18,<0.22" } ], "assemblyline": [ { "advisory": "Assemblyline updates to use latest version of the Authlib library to avoid CVE-2024-37568.", "cve": "CVE-2024-37568", "id": "pyup.io-75415", "more_info_path": "/vulnerabilities/CVE-2024-37568/75415", "specs": [ "<4.5.1.dev439" ], "v": "<4.5.1.dev439" } ], "assemblyline-service-client": [ { "advisory": "Affected versions of the Assemblyline service\u2011client package are vulnerable to Arbitrary File Write (Path Traversal) due to using the SHA\u2011256 value returned by the server directly as a filename without any validation in the download_file() method of task_handler.py, leading to arbitrary file overwrite. A malicious or compromised server attacker can exploit this vulnerability by returning a path\u2011traversal payload as the SHA\u2011256 string in the JSON response, resulting in files being written to arbitrary locations, potentially enabling code execution or full system compromise.", "cve": "CVE-2025-55013", "id": "pyup.io-78386", "more_info_path": "/vulnerabilities/CVE-2025-55013/78386", "specs": [ "<4.6.0.stable11", ">=4.6.1.dev0,<4.6.1.dev138" ], "v": "<4.6.0.stable11,>=4.6.1.dev0,<4.6.1.dev138" } ], "asterix-decoder": [ { "advisory": "Croatia Control Asterix 2.8.1 (python_v0.7.2) has a heap-based buffer over-read, with additional details to be disclosed at a later date.", "cve": "CVE-2021-44144", "id": "pyup.io-54135", "more_info_path": "/vulnerabilities/CVE-2021-44144/54135", "specs": [ ">=0,<0.7.2" ], "v": ">=0,<0.7.2" } ], "asteval": [ { "advisory": "If an attacker can control the input to the asteval library, they can bypass its safety restrictions and execute arbitrary Python code within the application's context.", "cve": "PVE-2025-76353", "id": "pyup.io-76353", "more_info_path": "/vulnerabilities/PVE-2025-76353/76353", "specs": [ "<1.0.6" ], "v": "<1.0.6" }, { "advisory": "If an attacker can control the input to the asteval library, they can bypass asteval's restrictions and execute arbitrary Python code in the context of the application using the library.", "cve": "CVE-2025-24359", "id": "pyup.io-76352", "more_info_path": "/vulnerabilities/CVE-2025-24359/76352", "specs": [ "<1.0.6" ], "v": "<1.0.6" } ], "astrbot": [ { "advisory": "Astrbot fixes a potential vulnerability in `/api/chat/get_file` endpoint. by.", "cve": "PVE-2025-77656", "id": "pyup.io-77656", "more_info_path": "/vulnerabilities/PVE-2025-77656/77656", "specs": [ "<3.5.13" ], "v": "<3.5.13" }, { "advisory": "Affected versions of the AstrBot package are vulnerable to Path Traversal due to unsanitized use of a user-supplied filename when constructing a file system path. The install_plugin_upload handler at /plugin/install-upload assigns the filename from the request body directly to file_path and passes it to file.save without normalization or directory restriction, enabling resolution outside the intended location.", "cve": "CVE-2025-57698", "id": "pyup.io-81484", "more_info_path": "/vulnerabilities/CVE-2025-57698/81484", "specs": [ "<=3.5.22" ], "v": "<=3.5.22" }, { "advisory": "Affected versions of the AstrBot package are vulnerable to Path Traversal due to inadequate validation of a user-supplied image file path used by a helper routine. The entities.py::_encode_image_bs64 function opens a filesystem path taken directly from the request body and returns the file contents as a base64 string without any path normalization or directory restriction.", "cve": "CVE-2025-57697", "id": "pyup.io-81485", "more_info_path": "/vulnerabilities/CVE-2025-57697/81485", "specs": [ "<=3.5.22" ], "v": "<=3.5.22" }, { "advisory": "AstrBot is a large language model chatbot and development framework. A path traversal vulnerability present in versions 3.4.4 through 3.5.12 may lead to information disclosure, such as API keys for LLM providers, account passwords, and other sensitive data. The vulnerability has been addressed in Pull Request #1676 and is included in version 3.5.13. As a workaround, users can edit the `cmd_config.json` file to disable the dashboard feature as a temporary workaround. However, it is strongly recommended to upgrade to version v3.5.13 or later to fully resolve this issue.", "cve": "CVE-2025-48957", "id": "pyup.io-77689", "more_info_path": "/vulnerabilities/CVE-2025-48957/77689", "specs": [ ">=3.4.4,<=3.5.12" ], "v": ">=3.4.4,<=3.5.12" } ], "astrometry-net-client": [ { "advisory": "Astrometry-net-client 0.2.9 updates its dependency 'cryptography' to v38.0.3 to include security fixes.", "cve": "CVE-2022-3602", "id": "pyup.io-52051", "more_info_path": "/vulnerabilities/CVE-2022-3602/52051", "specs": [ "<0.2.9" ], "v": "<0.2.9" }, { "advisory": "Astrometry-net-client 0.2.9 updates its dependency 'cryptography' to v38.0.3 to include security fixes.", "cve": "CVE-2022-3786", "id": "pyup.io-51919", "more_info_path": "/vulnerabilities/CVE-2022-3786/51919", "specs": [ "<0.2.9" ], "v": "<0.2.9" } ], "astronomer-cosmos": [ { "advisory": "Astronomer-cosmos addresses security vulnerability by not pinning Airflow 2.10.0 in response to CVE-2024-41937.", "cve": "CVE-2024-41937", "id": "pyup.io-74686", "more_info_path": "/vulnerabilities/CVE-2024-41937/74686", "specs": [ "<1.8.0" ], "v": "<1.8.0" } ], "astropy": [ { "advisory": "Astropy 3.0.1 updates the bundled CFITSIO library to 3.430. This is to remedy a critical security vulnerability that was identified by NASA.", "cve": "CVE-2018-3847", "id": "pyup.io-48549", "more_info_path": "/vulnerabilities/CVE-2018-3847/48549", "specs": [ "<3.0.1" ], "v": "<3.0.1" }, { "advisory": "Astropy 3.0.1 updates cfitsio to v3.43: NASA CFITSIO prior to 3.43 is affected by: Buffer Overflow. The impact is: arbitrary code execution. The component is: over 40 source code files were changed. The attack vector is: remote unauthenticated attacker. The fixed version is: 3.43. NOTE: this CVE refers to the issues not covered by CVE-2018-3846, CVE-2018-3847, CVE-2018-3848, and CVE-2018-3849. One example is ftp_status in drvrnet.c mishandling a long string beginning with a '4' character.", "cve": "CVE-2019-1010060", "id": "pyup.io-70530", "more_info_path": "/vulnerabilities/CVE-2019-1010060/70530", "specs": [ "<3.0.1" ], "v": "<3.0.1" }, { "advisory": "Astropy 3.0.1 updates the bundled CFITSIO library to 3.430. This is to remedy a critical security vulnerability that was identified by NASA.", "cve": "CVE-2018-3846", "id": "pyup.io-48550", "more_info_path": "/vulnerabilities/CVE-2018-3846/48550", "specs": [ "<3.0.1" ], "v": "<3.0.1" }, { "advisory": "Astropy 3.0.1 updates the bundled CFITSIO library to 3.430. This is to remedy a critical security vulnerability that was identified by NASA.", "cve": "CVE-2018-3848", "id": "pyup.io-35810", "more_info_path": "/vulnerabilities/CVE-2018-3848/35810", "specs": [ "<3.0.1" ], "v": "<3.0.1" }, { "advisory": "Astropy 3.0.1 updates the bundled CFITSIO library to 3.430. This is to remedy a critical security vulnerability that was identified by NASA.", "cve": "CVE-2018-3849", "id": "pyup.io-48548", "more_info_path": "/vulnerabilities/CVE-2018-3849/48548", "specs": [ "<3.0.1" ], "v": "<3.0.1" }, { "advisory": "Astropy is a project for astronomy in Python that fosters interoperability between Python astronomy packages. Version 5.3.2 of the Astropy core package is vulnerable to remote code execution due to improper input validation in the `TranformGraph().to_dot_graph` function. A malicious user can provide a command or a script file as a value to the `savelayout` argument, which will be placed as the first value in a list of arguments passed to `subprocess.Popen`. Although an error will be raised, the command or script will be executed successfully. Version 5.3.3 fixes this issue. See CVE-2023-41334.", "cve": "CVE-2023-41334", "id": "pyup.io-66947", "more_info_path": "/vulnerabilities/CVE-2023-41334/66947", "specs": [ "<5.3.3" ], "v": "<5.3.3" }, { "advisory": "Astropy 5.1.1 and 5.0.5 update its JS dependency 'jquery' to v3.6.0 to include security fixes.", "cve": "CVE-2020-11022", "id": "pyup.io-52131", "more_info_path": "/vulnerabilities/CVE-2020-11022/52131", "specs": [ ">=5.1rc1,<5.1.1", "<5.0.5" ], "v": ">=5.1rc1,<5.1.1,<5.0.5" }, { "advisory": "Astropy 5.1.1 and 5.0.5 update its JS dependency 'jquery' to v3.6.0 to include security fixes.", "cve": "CVE-2020-11023", "id": "pyup.io-52172", "more_info_path": "/vulnerabilities/CVE-2020-11023/52172", "specs": [ ">=5.1rc1,<5.1.1", "<5.0.5" ], "v": ">=5.1rc1,<5.1.1,<5.0.5" } ], "async-batcher": [ { "advisory": "Async-batcher's update to a newer version of scikit-learn addresses CVE-2024-5206.", "cve": "CVE-2024-5206", "id": "pyup.io-73033", "more_info_path": "/vulnerabilities/CVE-2024-5206/73033", "specs": [ "<0.2.1" ], "v": "<0.2.1" }, { "advisory": "Async-batcher's update to a newer version of idna addresses CVE-2024-3651.", "cve": "CVE-2024-3651", "id": "pyup.io-73013", "more_info_path": "/vulnerabilities/CVE-2024-3651/73013", "specs": [ "<0.2.1" ], "v": "<0.2.1" }, { "advisory": "Async-batcher's update to a newer version of aiohttp addresses CVE-2024-27306.", "cve": "CVE-2024-27306", "id": "pyup.io-73032", "more_info_path": "/vulnerabilities/CVE-2024-27306/73032", "specs": [ "<0.2.1" ], "v": "<0.2.1" }, { "advisory": "Async-batcher's update to a newer version of setuptools addresses CVE-2024-6345.", "cve": "CVE-2024-6345", "id": "pyup.io-73034", "more_info_path": "/vulnerabilities/CVE-2024-6345/73034", "specs": [ "<0.2.1" ], "v": "<0.2.1" }, { "advisory": "Async-batcher's update to newer versions of aioboto3 and urllib3 addresses CVE-2024-37891.", "cve": "CVE-2024-37891", "id": "pyup.io-73035", "more_info_path": "/vulnerabilities/CVE-2024-37891/73035", "specs": [ "<0.2.1" ], "v": "<0.2.1" } ], "async-firebase": [ { "advisory": "Async-firebase version 3.6.2 has updated its cryptography dependency to version 42.0.4 in response to the security vulnerability identified as CVE-2023-4807.", "cve": "CVE-2023-4807", "id": "pyup.io-65746", "more_info_path": "/vulnerabilities/CVE-2023-4807/65746", "specs": [ "<3.6.2" ], "v": "<3.6.2" } ], "async-search-client": [ { "advisory": "Async-search-client 0.5.1 updates the 'pydantic' dependency from 1.8.1 to 1.8.2 to fix a security vulnerability.", "cve": "CVE-2021-29510", "id": "pyup.io-40437", "more_info_path": "/vulnerabilities/CVE-2021-29510/40437", "specs": [ "<0.5.1" ], "v": "<0.5.1" } ], "async-tkinter-loop": [ { "advisory": "Async-tkinter-loop 0.3.0 updates its dependency 'pillow' requirement to '^9.0.1' to include security fixes.", "cve": "CVE-2022-22816", "id": "pyup.io-49243", "more_info_path": "/vulnerabilities/CVE-2022-22816/49243", "specs": [ "<0.3.0" ], "v": "<0.3.0" }, { "advisory": "Async-tkinter-loop 0.3.0 updates its dependency 'pillow' requirement to '^9.0.1' to include security fixes.", "cve": "CVE-2022-22815", "id": "pyup.io-49244", "more_info_path": "/vulnerabilities/CVE-2022-22815/49244", "specs": [ "<0.3.0" ], "v": "<0.3.0" }, { "advisory": "Async-tkinter-loop 0.3.0 updates its dependency 'pillow' requirement to '^9.0.1' to include security fixes.", "cve": "CVE-2022-24303", "id": "pyup.io-49242", "more_info_path": "/vulnerabilities/CVE-2022-24303/49242", "specs": [ "<0.3.0" ], "v": "<0.3.0" }, { "advisory": "Async-tkinter-loop 0.3.0 updates its dependency 'pillow' requirement to '^9.0.1' to include security fixes.", "cve": "CVE-2022-22817", "id": "pyup.io-49245", "more_info_path": "/vulnerabilities/CVE-2022-22817/49245", "specs": [ "<0.3.0" ], "v": "<0.3.0" } ], "asyncio-proxy": [ { "advisory": "Asyncio-proxy is a malicious package. It requires 'aiotoolbox', that contains a custom script in setup.py that downloads malicious and obfuscated code.\r\nhttps://inspector.pypi.io/project/asyncio-proxy/1.2.2/packages/65/31/70c74eca514cbcce0cde8f2b42c7b534e42bad946cd9c0aa28774f982f47/asyncio-proxy-1.2.2.tar.gz/asyncio-proxy-1.2.2/asyncio_proxy.egg-info/requires.txt#line.1", "cve": "PVE-2023-53560", "id": "pyup.io-53561", "more_info_path": "/vulnerabilities/PVE-2023-53560/53561", "specs": [ ">=0" ], "v": ">=0" } ], "asyncmy": [ { "advisory": "Affected versions of the asyncmy package are vulnerable to SQL Injection due to unescaped dictionary keys being interpolated directly into SQL queries. The escape_dict function in asyncmy/asyncmy/converters.pyx only escapes dictionary values and leaves keys unchanged, so when higher-level query-building code expands a user-supplied dict into SQL fragments, attacker-controlled keys are concatenated into the SQL statement without parameterization or proper neutralization.", "cve": "CVE-2025-65896", "id": "pyup.io-82236", "more_info_path": "/vulnerabilities/CVE-2025-65896/82236", "specs": [ "<=0.2.10" ], "v": "<=0.2.10" } ], "asyncpg": [ { "advisory": "Asyncpg before 0.21.0 allows a malicious PostgreSQL server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, because of access to an uninitialized pointer in the array data decoder.", "cve": "CVE-2020-17446", "id": "pyup.io-42281", "more_info_path": "/vulnerabilities/CVE-2020-17446/42281", "specs": [ "<0.21.0" ], "v": "<0.21.0" } ], "asyncssh": [ { "advisory": "An issue in AsyncSSH v2.14.0 and earlier allows attackers to control the extension info message (RFC 8308) via a man-in-the-middle attack.", "cve": "CVE-2023-46445", "id": "pyup.io-65385", "more_info_path": "/vulnerabilities/CVE-2023-46445/65385", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "An issue in AsyncSSH v2.14.0 and earlier allows attackers to control the remote end of an SSH client session via packet injection/removal and shell emulation.", "cve": "CVE-2023-46446", "id": "pyup.io-65384", "more_info_path": "/vulnerabilities/CVE-2023-46446/65384", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms.", "cve": "CVE-2023-48795", "id": "pyup.io-65192", "more_info_path": "/vulnerabilities/CVE-2023-48795/65192", "specs": [ "<2.14.2" ], "v": "<2.14.2" }, { "advisory": "Asyncssh 2.5.0 added a configurable maximum line length when the editor is in use to avoid potential denial-of-service attacks.\r\nhttps://github.com/ronf/asyncssh/commit/d0f0725371a5082f1b88b5c23b438c0edf07846a", "cve": "PVE-2021-39350", "id": "pyup.io-39350", "more_info_path": "/vulnerabilities/PVE-2021-39350/39350", "specs": [ "<2.5.0" ], "v": "<2.5.0" }, { "advisory": "The SSH server implementation of AsyncSSH before 1.12.1 does not properly check whether authentication is completed before processing other requests. A customized SSH client can simply skip the authentication step.", "cve": "CVE-2018-7749", "id": "pyup.io-54029", "more_info_path": "/vulnerabilities/CVE-2018-7749/54029", "specs": [ ">=0,<1.12.1" ], "v": ">=0,<1.12.1" } ], "asyncua": [ { "advisory": "Asyncua 0.9.96 includes a fix for CVE-2023-26150: Improper Authentication such that it is possible to access Address Space without encryption and authentication. **Note:** This issue is a result of missing checks for services that require an active session.\r\nhttps://github.com/FreeOpcUa/opcua-asyncio/issues/1014", "cve": "CVE-2023-26150", "id": "pyup.io-61570", "more_info_path": "/vulnerabilities/CVE-2023-26150/61570", "specs": [ "<0.9.96" ], "v": "<0.9.96" }, { "advisory": "Asyncua 0.9.96 includes a fix for CVE-2022-25304: Denial of Service (DoS) due to a missing limitation on the number of received chunks - per single session or in total for all concurrent sessions. An attacker can exploit this vulnerability by sending an unlimited number of huge chunks (e.g. 2GB each) without sending the Final closing chunk.\r\nhttps://github.com/FreeOpcUa/opcua-asyncio/commit/01c7acf047887b62d979cd4373d370e72a4b9057", "cve": "CVE-2022-25304", "id": "pyup.io-50830", "more_info_path": "/vulnerabilities/CVE-2022-25304/50830", "specs": [ "<0.9.96" ], "v": "<0.9.96" }, { "advisory": "Asyncua 0.9.96 includes a fix for CVE-2023-26151: Denial of Service (DoS) such that an attacker can send a malformed packet and as a result, the server will enter into an infinite loop and consume excessive memory.\r\nhttps://github.com/FreeOpcUa/opcua-asyncio/commit/f6603daa34a93a658f0e176cb0b9ee5a6643b262", "cve": "CVE-2023-26151", "id": "pyup.io-61571", "more_info_path": "/vulnerabilities/CVE-2023-26151/61571", "specs": [ "<0.9.96" ], "v": "<0.9.96" } ], "atlasapi": [ { "advisory": "Atlasapi 2.0.5 updates its dependency 'sphinx' to v3.0.4 to include security fixes.", "cve": "CVE-2020-11023", "id": "pyup.io-51568", "more_info_path": "/vulnerabilities/CVE-2020-11023/51568", "specs": [ "<2.0.5" ], "v": "<2.0.5" }, { "advisory": "Atlasapi 2.0.5 updates its dependency 'sphinx' to v3.0.4 to include security fixes.", "cve": "CVE-2020-11022", "id": "pyup.io-51567", "more_info_path": "/vulnerabilities/CVE-2020-11022/51567", "specs": [ "<2.0.5" ], "v": "<2.0.5" }, { "advisory": "Atlasapi 2.0.5 updates its dependency 'pygments' to v2.7.4 to include security fixes.", "cve": "CVE-2021-20270", "id": "pyup.io-51548", "more_info_path": "/vulnerabilities/CVE-2021-20270/51548", "specs": [ "<2.0.5" ], "v": "<2.0.5" }, { "advisory": "Atlasapi 2.0.5 updates its dependency 'pygments' to v2.7.4 to include security fixes.", "cve": "CVE-2021-27291", "id": "pyup.io-51566", "more_info_path": "/vulnerabilities/CVE-2021-27291/51566", "specs": [ "<2.0.5" ], "v": "<2.0.5" } ], "atproto": [ { "advisory": "Atproto 0.0.30 downgrades 'sphinxext-opengraph' to avoid including vulnerable dependencies, like pillow 9.5.0.\r\nhttps://github.com/MarshalX/atproto/pull/179", "cve": "CVE-2023-4863", "id": "pyup.io-62187", "more_info_path": "/vulnerabilities/CVE-2023-4863/62187", "specs": [ "<0.0.30" ], "v": "<0.0.30" } ], "att-iot-gateway": [ { "advisory": "Att-iot-gateway before 0.4.0 uses a insecure HTTP connection.", "cve": "PVE-2021-34257", "id": "pyup.io-34257", "more_info_path": "/vulnerabilities/PVE-2021-34257/34257", "specs": [ "<0.4.0" ], "v": "<0.4.0" } ], "attackiq-sigmaiq": [ { "advisory": "Attackiq-sigmaiq pins `certifi` version to `2023.07.22` to fix CVE-2023-37920.", "cve": "CVE-2023-37920", "id": "pyup.io-76044", "more_info_path": "/vulnerabilities/CVE-2023-37920/76044", "specs": [ "<0.2.1" ], "v": "<0.2.1" } ], "attic": [ { "advisory": "attic before 0.15 does not confirm unencrypted backups with the user, which allows remote attackers with read and write privileges for the encrypted repository to obtain potentially sensitive information by changing the manifest type byte of the repository to \"unencrypted / without key file\".", "cve": "CVE-2015-4082", "id": "pyup.io-54103", "more_info_path": "/vulnerabilities/CVE-2015-4082/54103", "specs": [ ">=0,<0.15" ], "v": ">=0,<0.15" } ], "attpc-spyral": [ { "advisory": "The Attpc-spyral project has upgraded JupyterLab from version 4.1.6 to 4.2.5 to address the security vulnerability identified as CVE-2024-43805.", "cve": "CVE-2024-43805", "id": "pyup.io-73454", "more_info_path": "/vulnerabilities/CVE-2024-43805/73454", "specs": [ "<0.5.0" ], "v": "<0.5.0" } ], "aubio": [ { "advisory": "In aubio 0.4.6, a divide-by-zero error exists in the function new_aubio_source_wavread() in source_wavread.c, which may lead to DoS when playing a crafted audio file.", "cve": "CVE-2017-17054", "id": "pyup.io-53942", "more_info_path": "/vulnerabilities/CVE-2017-17054/53942", "specs": [ ">=0,<0.4.7" ], "v": ">=0,<0.4.7" }, { "advisory": "An issue was discovered in aubio 0.4.6. A SEGV signal can occur in aubio_pitch_set_unit in pitch/pitch.c, as demonstrated by aubionotes.", "cve": "CVE-2018-14522", "id": "pyup.io-54008", "more_info_path": "/vulnerabilities/CVE-2018-14522/54008", "specs": [ ">=0,<0.4.7" ], "v": ">=0,<0.4.7" }, { "advisory": "An issue was discovered in aubio 0.4.6. A buffer over-read can occur in new_aubio_pitchyinfft in pitch/pitchyinfft.c, as demonstrated by aubionotes.", "cve": "CVE-2018-14523", "id": "pyup.io-54006", "more_info_path": "/vulnerabilities/CVE-2018-14523/54006", "specs": [ ">=0,<0.4.7" ], "v": ">=0,<0.4.7" }, { "advisory": "An issue was discovered in aubio 0.4.6. A SEGV signal can occur in aubio_source_avcodec_readframe in io/source_avcodec.c, as demonstrated by aubiomfcc.", "cve": "CVE-2018-14521", "id": "pyup.io-54007", "more_info_path": "/vulnerabilities/CVE-2018-14521/54007", "specs": [ ">=0,<0.4.7" ], "v": ">=0,<0.4.7" }, { "advisory": "The swri_audio_convert function in audioconvert.c in FFmpeg libswresample through 3.0.101, as used in FFmpeg 3.4.1, aubio 0.4.6, and other products, allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted audio file.", "cve": "CVE-2017-17555", "id": "pyup.io-53945", "more_info_path": "/vulnerabilities/CVE-2017-17555/53945", "specs": [ ">=0,<0.4.7" ], "v": ">=0,<0.4.7" }, { "advisory": "A NULL pointer dereference (DoS) Vulnerability was found in the function aubio_source_avcodec_readframe in io/source_avcodec.c of aubio 0.4.6, which may lead to DoS when playing a crafted audio file.", "cve": "CVE-2017-17554", "id": "pyup.io-53944", "more_info_path": "/vulnerabilities/CVE-2017-17554/53944", "specs": [ ">=0,<0.4.7" ], "v": ">=0,<0.4.7" }, { "advisory": "aubio v0.4.0 to v0.4.8 has a Buffer Overflow in new_aubio_tempo.", "cve": "CVE-2018-19800", "id": "pyup.io-54016", "more_info_path": "/vulnerabilities/CVE-2018-19800/54016", "specs": [ ">=0.4.0,<0.4.9" ], "v": ">=0.4.0,<0.4.9" }, { "advisory": "aubio v0.4.0 to v0.4.8 has a new_aubio_onset NULL pointer dereference.", "cve": "CVE-2018-19802", "id": "pyup.io-54019", "more_info_path": "/vulnerabilities/CVE-2018-19802/54019", "specs": [ ">=0.4.0,<0.4.9" ], "v": ">=0.4.0,<0.4.9" }, { "advisory": "aubio v0.4.0 to v0.4.8 has a NULL pointer dereference in new_aubio_filterbank via invalid n_filters.", "cve": "CVE-2018-19801", "id": "pyup.io-54018", "more_info_path": "/vulnerabilities/CVE-2018-19801/54018", "specs": [ ">=0.4.0,<0.4.9" ], "v": ">=0.4.0,<0.4.9" } ], "aucmedi": [ { "advisory": "Aucmedi 0.7.2 updates its dependency 'protobuf' to v3.20.2 to include a security fix.", "cve": "CVE-2022-1941", "id": "pyup.io-51287", "more_info_path": "/vulnerabilities/CVE-2022-1941/51287", "specs": [ "<0.7.2" ], "v": "<0.7.2" }, { "advisory": "Aucmedi version 0.9.0 upgrades its Pillow dependency to version 10.2.0 from 9.3.0 in response to CVE-2023-50447.", "cve": "CVE-2023-50447", "id": "pyup.io-65619", "more_info_path": "/vulnerabilities/CVE-2023-50447/65619", "specs": [ "<0.9.0" ], "v": "<0.9.0" } ], "audaugio": [ { "advisory": "In SoX 14.4.2, there is a floating-point exception in lsx_aiffstartwrite in aiff.c in libsox.a.", "cve": "CVE-2022-31650", "id": "pyup.io-62529", "more_info_path": "/vulnerabilities/CVE-2022-31650/62529", "specs": [ "<0.0.2a0" ], "v": "<0.0.2a0" }, { "advisory": "Audagio and prior versions ship with vulnerable dependencies (SoX == 1.3.3).\r\nIn SoX 14.4.2, there is an assertion failure in rate_init in rate.c in libsox.a.\r\nhttps://github.com/BrianMargolis/AudAugio/blob/master/requirements.txt", "cve": "CVE-2022-31651", "id": "pyup.io-62530", "more_info_path": "/vulnerabilities/CVE-2022-31651/62530", "specs": [ "<0.0.2a0" ], "v": "<0.0.2a0" } ], "auditree-framework": [ { "advisory": "Auditree-framework 1.19.0 fixes minor security issues found by the 'bandit'.", "cve": "PVE-2021-40445", "id": "pyup.io-40445", "more_info_path": "/vulnerabilities/PVE-2021-40445/40445", "specs": [ "<1.19.0" ], "v": "<1.19.0" } ], "augmenty": [ { "advisory": "Augmenty 1.0.0 upgrades the dependency pydantic version from >=1.7.4,!=1.8,!=1.8.1,<1.9.0 to >=1.8.2,<1.9.0. \r\nhttps://data.safetycli.com/packages/pypi/pydantic/versions\r\nhttps://github.com/KennethEnevoldsen/augmenty/commit/34821e38d3004919922a56c04ad43450550c2591", "cve": "PVE-2023-62782", "id": "pyup.io-62782", "more_info_path": "/vulnerabilities/PVE-2023-62782/62782", "specs": [ "<1.0.0" ], "v": "<1.0.0" } ], "aumbry": [ { "advisory": "Aumbry 0.10.0 includes a security patch for the function 'parse' in 'aumbry/formats/yml.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/pyarmory/aumbry/commit/5b1cd2e4296d3cfb10a6d1bd02cd5b4ecb0f0bcd", "cve": "CVE-2017-18342", "id": "pyup.io-41307", "more_info_path": "/vulnerabilities/CVE-2017-18342/41307", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Aumbry 0.10.0 and prior uses yaml.full_load(), which is vulnerable to CVE-2020-14343.", "cve": "CVE-2020-14343", "id": "pyup.io-41759", "more_info_path": "/vulnerabilities/CVE-2020-14343/41759", "specs": [ "<=0.10.0" ], "v": "<=0.10.0" } ], "austin-tui": [ { "advisory": "Austin-tui 1.1.1 updates its dependency 'lxml' to v4.6.5 to include a security fix.", "cve": "CVE-2021-43818", "id": "pyup.io-43620", "more_info_path": "/vulnerabilities/CVE-2021-43818/43620", "specs": [ "<1.1.1" ], "v": "<1.1.1" } ], "authbwc": [ { "advisory": "Authbwc 0.1.4 fixes an issue with the way the HTTP session user permissions were loaded. This vulnerability made it possible for a user to gain the permissions of the user logged in previously. The user would have had to be sharing the same http session for this access to have been gained.", "cve": "PVE-2021-25631", "id": "pyup.io-25631", "more_info_path": "/vulnerabilities/PVE-2021-25631/25631", "specs": [ "<0.1.4" ], "v": "<0.1.4" }, { "advisory": "authbwc before 0.3.1 has a vulnerability in the password reset process that allowed users to log in when inactive.\r\nhttps://github.com/blazelibs/authbwc/commit/452f9651309ae5933d22c6f5aedf044ab7f05368", "cve": "PVE-2021-34836", "id": "pyup.io-34836", "more_info_path": "/vulnerabilities/PVE-2021-34836/34836", "specs": [ "<0.3.1" ], "v": "<0.3.1" } ], "authentication-factory": [ { "advisory": "Authentication-factory has been updated to use certifi package version 2024.7.4 to address a vulnerability identified as CVE-2024-39689.", "cve": "CVE-2024-39689", "id": "pyup.io-72218", "more_info_path": "/vulnerabilities/CVE-2024-39689/72218", "specs": [ "<0.0.5" ], "v": "<0.0.5" } ], "authlib": [ { "advisory": "Authlib 0.15.4 includes a security fix when jwt claims is None.\r\nhttps://github.com/lepture/authlib/commit/262c37268c77a5da8fae80710a93d2d65a373ab7", "cve": "PVE-2022-51634", "id": "pyup.io-51634", "more_info_path": "/vulnerabilities/PVE-2022-51634/51634", "specs": [ "<0.15.4" ], "v": "<0.15.4" }, { "advisory": "Authlib 1.1.0 includes a fix for CVE-2022-39174.\r\nhttps://github.com/lepture/authlib/commit/3a382780907226d99c09606aac78e29fe5bd3bf6", "cve": "CVE-2022-39174", "id": "pyup.io-51646", "more_info_path": "/vulnerabilities/CVE-2022-39174/51646", "specs": [ "<1.1.0" ], "v": "<1.1.0" }, { "advisory": "Authlib 1.1.0 includes a fix for CVE-2022-39175.\r\nhttps://github.com/lepture/authlib/commit/80b0808263c6ce88335532b78e62bf2522593390", "cve": "CVE-2022-39175", "id": "pyup.io-51645", "more_info_path": "/vulnerabilities/CVE-2022-39175/51645", "specs": [ "<1.1.0" ], "v": "<1.1.0" }, { "advisory": "Affected versions of Authlib have an algorithm confusion vulnerability in asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. This is similar to CVE-2022-29217 and CVE-2024-33663.", "cve": "CVE-2024-37568", "id": "pyup.io-71636", "more_info_path": "/vulnerabilities/CVE-2024-37568/71636", "specs": [ "<1.3.1" ], "v": "<1.3.1" }, { "advisory": "Affected versions of the Authlib package are vulnerable to Authentication Bypass due to improper handling of critical header parameters in JSON Web Signature tokens. The authlib.jose.JsonWebSignature.deserialize_compact() method violates RFC 7515 \"must-understand\" semantics by accepting tokens that declare unknown critical header parameters in the crit field instead of rejecting them as required by the specification. An attacker can exploit this by crafting signed tokens with critical headers that strict verifiers reject but Authlib accepts, enabling split-brain verification in mixed-language environments and potentially leading to authentication policy bypass, token replay attacks, or privilege escalation.", "cve": "CVE-2025-59420", "id": "pyup.io-79756", "more_info_path": "/vulnerabilities/CVE-2025-59420/79756", "specs": [ "<1.6.4" ], "v": "<1.6.4" }, { "advisory": "Affected versions (< 1.6.5) of the Authlib package are vulnerable to Denial of Service (DoS) due to unbounded DEFLATE decompression in JWE zip=DEF handling. In the JOSE implementation, the JWE decode path (authlib/jose/rfc7516/jwe.py) passes decryptable ciphertexts with zip=DEF to DeflateZipAlgorithm.decompress in authlib/jose/rfc7518/jwe_zips.py, which calls zlib.decompress without an output size limit, allowing tiny inputs to expand massively.", "cve": "CVE-2025-62706", "id": "pyup.io-81132", "more_info_path": "/vulnerabilities/CVE-2025-62706/81132", "specs": [ "<1.6.5" ], "v": "<1.6.5" }, { "advisory": "Affected versions of the Authlib package are vulnerable to Denial of Service due to unbounded JOSE (JWS/JWT) segment sizes. The vulnerability occurs because Authlib\u2019s util.extract_segment (for the header) and _extract_signature (for the signature) accept base64url-encoded data of arbitrary size and then fully decode and parse it without early limits.", "cve": "CVE-2025-61920", "id": "pyup.io-80401", "more_info_path": "/vulnerabilities/CVE-2025-61920/80401", "specs": [ "<1.6.5" ], "v": "<1.6.5" }, { "advisory": "Affected versions of the Authlib package are vulnerable to Cross-Site Request Forgery (CSRF) due to cache-backed OAuth state storage not being bound to the initiating user session. In authlib/integrations/base_client/framework_integration.py, FrameworkIntegration.set_state_data stores state under a cache key like _state_{app}_{state} and FrameworkIntegration.get_state_data retrieves it without validating the caller\u2019s session, allowing authorize_access_token in authlib/integrations/flask_client/apps.py (via the oauth_token parameter) to accept a state value from a different browser session.", "cve": "CVE-2025-68158", "id": "pyup.io-84339", "more_info_path": "/vulnerabilities/CVE-2025-68158/84339", "specs": [ "<1.6.6" ], "v": "<1.6.6" } ], "auto-optional": [ { "advisory": "Auto-optional 0.3.2 updates its dependency 'mkdocs' to v1.2.3 to include a security fix.", "cve": "CVE-2021-40978", "id": "pyup.io-44586", "more_info_path": "/vulnerabilities/CVE-2021-40978/44586", "specs": [ "<0.3.2" ], "v": "<0.3.2" } ], "auto-surprise": [ { "advisory": "Auto-surprise 0.1.7 updates its dependency 'jinja2' to v2.11.3 to include a security fix.", "cve": "CVE-2020-28493", "id": "pyup.io-40146", "more_info_path": "/vulnerabilities/CVE-2020-28493/40146", "specs": [ "<0.1.7" ], "v": "<0.1.7" }, { "advisory": "Auto-surprise 0.1.7 updates its dependency 'pyyaml' to v5.4 to include a security fix.", "cve": "CVE-2020-14343", "id": "pyup.io-44809", "more_info_path": "/vulnerabilities/CVE-2020-14343/44809", "specs": [ "<0.1.7" ], "v": "<0.1.7" }, { "advisory": "Auto-surprise 0.1.7 updates its dependency 'pygments' to v2.7.4 to include security fixes.", "cve": "CVE-2021-20270", "id": "pyup.io-44807", "more_info_path": "/vulnerabilities/CVE-2021-20270/44807", "specs": [ "<0.1.7" ], "v": "<0.1.7" }, { "advisory": "Auto-surprise 0.1.7 updates its dependency 'pygments' to v2.7.4 to include security fixes.", "cve": "CVE-2021-27291", "id": "pyup.io-44808", "more_info_path": "/vulnerabilities/CVE-2021-27291/44808", "specs": [ "<0.1.7" ], "v": "<0.1.7" } ], "autobahn": [ { "advisory": "In autobahn before 0.15.0 if the `allowedOrigins` websocket option was set, the resulting matching was insufficient and would allow more origins than intended.", "cve": "PVE-2021-25632", "id": "pyup.io-25632", "more_info_path": "/vulnerabilities/PVE-2021-25632/25632", "specs": [ "<0.15.0" ], "v": "<0.15.0" }, { "advisory": "Autobahn 0.6.4 fixes a security issue related to a WAMP-CRA timing attack very, very unlikely to be exploitable.\r\nhttps://github.com/advisories/GHSA-xm8r-5wh6-f46f", "cve": "PVE-2021-25633", "id": "pyup.io-25633", "more_info_path": "/vulnerabilities/PVE-2021-25633/25633", "specs": [ "<0.6.4" ], "v": "<0.6.4" }, { "advisory": "Autobahn|Python before 20.12.3 allows redirect header injection. See CVE-2020-35678.", "cve": "CVE-2020-35678", "id": "pyup.io-39363", "more_info_path": "/vulnerabilities/CVE-2020-35678/39363", "specs": [ "<20.12.3" ], "v": "<20.12.3" } ], "autocrop": [ { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-11538", "id": "pyup.io-42934", "more_info_path": "/vulnerabilities/CVE-2020-11538/42934", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-35654", "id": "pyup.io-42938", "more_info_path": "/vulnerabilities/CVE-2020-35654/42938", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-10379", "id": "pyup.io-42935", "more_info_path": "/vulnerabilities/CVE-2020-10379/42935", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-10994", "id": "pyup.io-42937", "more_info_path": "/vulnerabilities/CVE-2020-10994/42937", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-10378", "id": "pyup.io-42936", "more_info_path": "/vulnerabilities/CVE-2020-10378/42936", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-35653", "id": "pyup.io-42939", "more_info_path": "/vulnerabilities/CVE-2020-35653/42939", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-5313", "id": "pyup.io-42933", "more_info_path": "/vulnerabilities/CVE-2020-5313/42933", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-15999", "id": "pyup.io-42851", "more_info_path": "/vulnerabilities/CVE-2020-15999/42851", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-35655", "id": "pyup.io-42940", "more_info_path": "/vulnerabilities/CVE-2020-35655/42940", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Autocrop 1.1.1 updates the minimum requirement of its dependency 'pillow' to v8.1.0 to include security fixes.", "cve": "CVE-2020-5310", "id": "pyup.io-42932", "more_info_path": "/vulnerabilities/CVE-2020-5310/42932", "specs": [ "<1.1.1" ], "v": "<1.1.1" } ], "autogen": [ { "advisory": "The affected version of Autogen has a security flaw that allows code execution via code_execution_config, which is fixed by setting code_execution_config to False instead of None.", "cve": "PVE-2024-73068", "id": "pyup.io-73068", "more_info_path": "/vulnerabilities/PVE-2024-73068/73068", "specs": [ "<0.2.11" ], "v": "<0.2.11" } ], "autogluon": [ { "advisory": "Autogluon 0.4.1 updates its dependency 'pillow' minimum requirement to v9.0.1 to include security fixes.", "cve": "CVE-2022-22817", "id": "pyup.io-48597", "more_info_path": "/vulnerabilities/CVE-2022-22817/48597", "specs": [ "<0.4.1" ], "v": "<0.4.1" }, { "advisory": "The autogluon.multimodal module has a vulnerability due to the incorrect neutralization of special elements utilized in an operating system command. This issue is identified as an 'OS Command Injection'.", "cve": "PVE-2023-99929", "id": "pyup.io-61945", "more_info_path": "/vulnerabilities/PVE-2023-99929/61945", "specs": [ "<0.5.2" ], "v": "<0.5.2" }, { "advisory": "Autogluon 0.5.3 updates its dependency 'transformers' requirement to \">=4.23.0,<4.24.0\" to include security fixes.", "cve": "PVE-2022-51450", "id": "pyup.io-51940", "more_info_path": "/vulnerabilities/PVE-2022-51450/51940", "specs": [ "<0.5.3" ], "v": "<0.5.3" }, { "advisory": "Autogluon 0.5.3 updates its dependency 'transformers' requirement to \">=4.23.0,<4.24.0\" to include security fixes.", "cve": "CVE-2022-1941", "id": "pyup.io-51994", "more_info_path": "/vulnerabilities/CVE-2022-1941/51994", "specs": [ "<0.5.3" ], "v": "<0.5.3" }, { "advisory": "Autogluon 0.6.0 uses yaml.safe_load() to avoid a code execution vulnerability.\r\nhttps://github.com/autogluon/autogluon/pull/1987", "cve": "CVE-2017-18342", "id": "pyup.io-51918", "more_info_path": "/vulnerabilities/CVE-2017-18342/51918", "specs": [ "<0.6.0" ], "v": "<0.6.0" }, { "advisory": "Autogluon 0.6.1 updates its dependency 'pillow' requirement to '>=9.3.0' to include security fixes.", "cve": "CVE-2022-24303", "id": "pyup.io-52411", "more_info_path": "/vulnerabilities/CVE-2022-24303/52411", "specs": [ "<0.6.1" ], "v": "<0.6.1" }, { "advisory": "Autogluon 0.6.1 updates its dependency 'pillow' requirement to '>=9.3.0' to include security fixes.", "cve": "CVE-2022-45198", "id": "pyup.io-52534", "more_info_path": "/vulnerabilities/CVE-2022-45198/52534", "specs": [ "<0.6.1" ], "v": "<0.6.1" }, { "advisory": "Autogluon 0.6.2 updates its dependency 'torch' to v0.13.1 to include a security fix.", "cve": "CVE-2022-45907", "id": "pyup.io-52772", "more_info_path": "/vulnerabilities/CVE-2022-45907/52772", "specs": [ "<0.6.2" ], "v": "<0.6.2" }, { "advisory": "Autogluon 0.4.1 updates its dependency 'ray' minimum requirement to v1.10.0 to include security fixes.", "cve": "CVE-2021-45046", "id": "pyup.io-48622", "more_info_path": "/vulnerabilities/CVE-2021-45046/48622", "specs": [ ">=0.4.0,<0.4.1" ], "v": ">=0.4.0,<0.4.1" }, { "advisory": "Autogluon 0.4.1 updates its dependency 'ray' minimum requirement to v1.10.0 to include security fixes.", "cve": "PVE-2021-42426", "id": "pyup.io-48620", "more_info_path": "/vulnerabilities/PVE-2021-42426/48620", "specs": [ ">=0.4.0,<0.4.1" ], "v": ">=0.4.0,<0.4.1" }, { "advisory": "Autogluon 0.4.1 updates its dependency 'ray' minimum requirement to v1.10.0 to include security fixes.", "cve": "CVE-2021-44228", "id": "pyup.io-48621", "more_info_path": "/vulnerabilities/CVE-2021-44228/48621", "specs": [ ">=0.4.0,<0.4.1" ], "v": ">=0.4.0,<0.4.1" }, { "advisory": "Autogluon 0.4.1 updates its dependency 'ray' minimum requirement to v1.10.0 to include security fixes.", "cve": "CVE-2021-45105", "id": "pyup.io-48623", "more_info_path": "/vulnerabilities/CVE-2021-45105/48623", "specs": [ ">=0.4.0,<0.4.1" ], "v": ">=0.4.0,<0.4.1" }, { "advisory": "Autogluon 0.4.1 updates its dependency 'ray' minimum requirement to v1.10.0 to include security fixes.", "cve": "CVE-2021-44832", "id": "pyup.io-48624", "more_info_path": "/vulnerabilities/CVE-2021-44832/48624", "specs": [ ">=0.4.0,<0.4.1" ], "v": ">=0.4.0,<0.4.1" }, { "advisory": "Autogluon 0.5.2 and 0.4.3 use yaml.safe_load() to prevent a code injection vulnerability.\r\nhttps://github.com/awslabs/autogluon/commit/23a37e74e58d03055c84a1b89c5af6c3db296b5e", "cve": "PVE-2022-50305", "id": "pyup.io-50305", "more_info_path": "/vulnerabilities/PVE-2022-50305/50305", "specs": [ ">=0.5.0a0,<0.5.2", "<0.4.3" ], "v": ">=0.5.0a0,<0.5.2,<0.4.3" } ], "autogluon-multimodal": [ { "advisory": "The autogluon.multimodal module has a vulnerability due to the incorrect neutralization of special elements utilized in an operating system command. This issue is identified as an 'OS Command Injection'.", "cve": "PVE-2023-99930", "id": "pyup.io-61944", "more_info_path": "/vulnerabilities/PVE-2023-99930/61944", "specs": [ "<0.5.2" ], "v": "<0.5.2" } ], "autogluon.multimodal": [ { "advisory": "Autogluon.multimodal 0.4.3, 0.5.2 and 0.5.2b20220727 include a security fix: Unsafe yaml deserialization in autogluon.multimodal.\r\nhttps://github.com/autogluon/autogluon/security/advisories/GHSA-6h2x-4gjf-jc5w", "cve": "CVE-2017-18342", "id": "pyup.io-55170", "more_info_path": "/vulnerabilities/CVE-2017-18342/55170", "specs": [ ">=0.4.0,<0.4.3", ">=0.5.0,<0.5.2", ">=0.5.2b20220719,<0.5.2b20220727" ], "v": ">=0.4.0,<0.4.3,>=0.5.0,<0.5.2,>=0.5.2b20220719,<0.5.2b20220727" } ], "automationhat": [ { "advisory": "Automationhat version 0.2.0 improves thread safety by making ads1015.read() function thread-safe, particularly when \"auto_lights\" is activated. Previously, asynchronous reads from the \"update_lights\" thread interfered with main thread ADC reads, leading to random erroneous readings.", "cve": "PVE-2024-70556", "id": "pyup.io-70556", "more_info_path": "/vulnerabilities/PVE-2024-70556/70556", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "automatoes": [ { "advisory": "Automatoes 0.9.7 updates its dependency 'cryptography' to v3.4.4 to include a security fix.", "cve": "CVE-2020-36242", "id": "pyup.io-52585", "more_info_path": "/vulnerabilities/CVE-2020-36242/52585", "specs": [ "<0.9.7" ], "v": "<0.9.7" } ], "autonicer": [ { "advisory": "Autonicer 1.2.1 updates its dependency 'certifi' to v2022.12.7 to include a security fix.", "cve": "CVE-2022-23491", "id": "pyup.io-52774", "more_info_path": "/vulnerabilities/CVE-2022-23491/52774", "specs": [ "<1.2.1" ], "v": "<1.2.1" } ], "av": [ { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-27845", "id": "pyup.io-45833", "more_info_path": "/vulnerabilities/CVE-2020-27845/45833", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [wavpack].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-35738", "id": "pyup.io-45838", "more_info_path": "/vulnerabilities/CVE-2020-35738/45838", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-27841", "id": "pyup.io-45831", "more_info_path": "/vulnerabilities/CVE-2020-27841/45831", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-27842", "id": "pyup.io-45834", "more_info_path": "/vulnerabilities/CVE-2020-27842/45834", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-27823", "id": "pyup.io-45825", "more_info_path": "/vulnerabilities/CVE-2020-27823/45825", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-27814", "id": "pyup.io-45826", "more_info_path": "/vulnerabilities/CVE-2020-27814/45826", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-27824", "id": "pyup.io-45832", "more_info_path": "/vulnerabilities/CVE-2020-27824/45832", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [gnutls].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2021-20232", "id": "pyup.io-45836", "more_info_path": "/vulnerabilities/CVE-2021-20232/45836", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-8112", "id": "pyup.io-45822", "more_info_path": "/vulnerabilities/CVE-2020-8112/45822", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-6851", "id": "pyup.io-45827", "more_info_path": "/vulnerabilities/CVE-2020-6851/45827", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-27844", "id": "pyup.io-45824", "more_info_path": "/vulnerabilities/CVE-2020-27844/45824", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-15389", "id": "pyup.io-45828", "more_info_path": "/vulnerabilities/CVE-2020-15389/45828", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2019-12973", "id": "pyup.io-45830", "more_info_path": "/vulnerabilities/CVE-2019-12973/45830", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [gnutls].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2021-20231", "id": "pyup.io-45835", "more_info_path": "/vulnerabilities/CVE-2021-20231/45835", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [gmp].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2021-43618", "id": "pyup.io-45837", "more_info_path": "/vulnerabilities/CVE-2021-43618/45837", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.0.1 updates wheel components to include security fixes [openjpeg].\r\nhttps://github.com/PyAV-Org/PyAV/issues/901", "cve": "CVE-2020-27843", "id": "pyup.io-45829", "more_info_path": "/vulnerabilities/CVE-2020-27843/45829", "specs": [ "<9.0.1" ], "v": "<9.0.1" }, { "advisory": "Av 9.1.0 updates 'FFmpeg' binary wheels to fix security vulnerabilities.\r\nhttps://github.com/PyAV-Org/PyAV/commit/9cbe441d637be15d5b4b57211a7df3958c3c0a02", "cve": "CVE-2018-10393", "id": "pyup.io-47835", "more_info_path": "/vulnerabilities/CVE-2018-10393/47835", "specs": [ "<9.1.0" ], "v": "<9.1.0" }, { "advisory": "Av 9.1.0 updates 'FFmpeg' binary wheels to fix security vulnerabilities.\r\nhttps://github.com/PyAV-Org/PyAV/commit/9cbe441d637be15d5b4b57211a7df3958c3c0a02", "cve": "CVE-2022-23308", "id": "pyup.io-47836", "more_info_path": "/vulnerabilities/CVE-2022-23308/47836", "specs": [ "<9.1.0" ], "v": "<9.1.0" }, { "advisory": "Av 9.1.0 updates 'FFmpeg' binary wheels to fix security vulnerabilities.\r\nhttps://github.com/PyAV-Org/PyAV/commit/9cbe441d637be15d5b4b57211a7df3958c3c0a02", "cve": "CVE-2018-10392", "id": "pyup.io-47802", "more_info_path": "/vulnerabilities/CVE-2018-10392/47802", "specs": [ "<9.1.0" ], "v": "<9.1.0" }, { "advisory": "Av 9.1.0 updates 'FFmpeg' binary wheels to fix security vulnerabilities.\r\nhttps://github.com/PyAV-Org/PyAV/commit/9cbe441d637be15d5b4b57211a7df3958c3c0a02", "cve": "CVE-2020-26682", "id": "pyup.io-47837", "more_info_path": "/vulnerabilities/CVE-2020-26682/47837", "specs": [ "<9.1.0" ], "v": "<9.1.0" } ], "avocado-framework": [ { "advisory": "avocado-framework 0.17.0 fixes a temporary dir issue, that had potential security implications.", "cve": "PVE-2021-34679", "id": "pyup.io-34679", "more_info_path": "/vulnerabilities/PVE-2021-34679/34679", "specs": [ "<0.17.0" ], "v": "<0.17.0" }, { "advisory": "Avocado-framework version 104.0 replaces the deprecated tmpfile.mktemp function, which has been known for security vulnerabilities since Python 2.3, with the more secure tmpdir method.\r\nhttps://github.com/avocado-framework/avocado/commit/f4ffe822232bfa2a0567fb82a7b178dec0f6f371", "cve": "PVE-2024-66798", "id": "pyup.io-66798", "more_info_path": "/vulnerabilities/PVE-2024-66798/66798", "specs": [ "<104.0" ], "v": "<104.0" }, { "advisory": "Avocado-framework 37.0 allows for proper checks of host keys to avoid man-in-the-middle attacks which could lead to connecting and sending credentials to the wrong machine.", "cve": "PVE-2021-34678", "id": "pyup.io-34678", "more_info_path": "/vulnerabilities/PVE-2021-34678/34678", "specs": [ "<37.0" ], "v": "<37.0" } ], "avogadro": [ { "advisory": "Avogadro 1.97 switches to a new clang-tidy script for secure pull-request comments.\r\nhttps://github.com/OpenChemistry/avogadrolibs/pull/988", "cve": "PVE-2022-50249", "id": "pyup.io-50249", "more_info_path": "/vulnerabilities/PVE-2022-50249/50249", "specs": [ "<1.97" ], "v": "<1.97" } ], "awkward": [ { "advisory": "Awkward 0.10.1 closes a security hole and backward incompatibility in `awkward.persist.whitelist` handling.", "cve": "PVE-2021-37154", "id": "pyup.io-37154", "more_info_path": "/vulnerabilities/PVE-2021-37154/37154", "specs": [ "<0.10.1" ], "v": "<0.10.1" } ], "aworld": [ { "advisory": "A vulnerability was found in inclusionAI AWorld up to 8c257626e648d98d793dd9a1a950c2af4dd84c4e. It has been rated as critical. This issue affects the function subprocess.run/subprocess.Popen of the file AWorld/aworld/virtual_environments/terminals/shell_tool.py. The manipulation leads to os command injection. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable.", "cve": "CVE-2025-4032", "id": "pyup.io-77150", "more_info_path": "/vulnerabilities/CVE-2025-4032/77150", "specs": [ "<=0.2.1" ], "v": "<=0.2.1" } ], "aws-advanced-python-wrapper": [ { "advisory": "Affected versions of the aws-advanced-python-wrapper package are vulnerable to Privilege Escalation due to improper use of externally controlled input when selecting PostgreSQL functions to execute. In affected versions, the AWS Advanced Python Wrapper for Aurora PostgreSQL allows a low-privilege authenticated user to define a crafted PostgreSQL function that the wrapper can execute with the permissions of other Amazon RDS users, reflecting user-controlled input into which function and role are used without sufficient restriction.", "cve": "CVE-2025-12967", "id": "pyup.io-81585", "more_info_path": "/vulnerabilities/CVE-2025-12967/81585", "specs": [ "<1.4.0" ], "v": "<1.4.0" } ], "aws-analytics-reference-architecture": [ { "advisory": "Aws-analytics-reference-architecture 1.1.1 updates its dependency 'xmldom' to v0.7.0 to include a security fix.", "cve": "CVE-2021-32796", "id": "pyup.io-41196", "more_info_path": "/vulnerabilities/CVE-2021-32796/41196", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Aws-analytics-reference-architecture 1.8.8 updates its dependency 'log4j' and its references to v2.17.0 to fix critical security vulnerabilities.\r\nhttps://github.com/aws-samples/aws-analytics-reference-architecture/commit/c2c18615602c48f19be5a34dde6a8569f2fdfe0d", "cve": "CVE-2021-44228", "id": "pyup.io-43972", "more_info_path": "/vulnerabilities/CVE-2021-44228/43972", "specs": [ "<1.8.8" ], "v": "<1.8.8" }, { "advisory": "Aws-analytics-reference-architecture 1.8.8 updates its dependency 'log4j' and its references to v2.17.0 to fix critical security vulnerabilities.\r\nhttps://github.com/aws-samples/aws-analytics-reference-architecture/commit/c2c18615602c48f19be5a34dde6a8569f2fdfe0d", "cve": "CVE-2021-45105", "id": "pyup.io-44480", "more_info_path": "/vulnerabilities/CVE-2021-45105/44480", "specs": [ "<1.8.8" ], "v": "<1.8.8" }, { "advisory": "Aws-analytics-reference-architecture 1.8.8 updates its dependency 'log4j' and its references to v2.17.0 to fix critical security vulnerabilities.\r\nhttps://github.com/aws-samples/aws-analytics-reference-architecture/commit/c2c18615602c48f19be5a34dde6a8569f2fdfe0d", "cve": "CVE-2021-45046", "id": "pyup.io-44479", "more_info_path": "/vulnerabilities/CVE-2021-45046/44479", "specs": [ "<1.8.8" ], "v": "<1.8.8" }, { "advisory": "Aws-analytics-reference-architecture 2.4.1 updates its Maven dependency \"hadoop-common\" to v2.10.2 to include a security fix.", "cve": "CVE-2022-25168", "id": "pyup.io-51165", "more_info_path": "/vulnerabilities/CVE-2022-25168/51165", "specs": [ "<2.4.1" ], "v": "<2.4.1" }, { "advisory": "Aws-analytics-reference-architecture 1.14.1 and prior includes a version of 'log4j' affected by a medium severity vulnerability.", "cve": "CVE-2021-44832", "id": "pyup.io-44481", "more_info_path": "/vulnerabilities/CVE-2021-44832/44481", "specs": [ "<=1.14.1" ], "v": "<=1.14.1" } ], "aws-encryption-sdk": [ { "advisory": "Aws-encryption-sdk versions 1.9.0 and 2.2.0 improve the decryption process to handle signature and message validation vulnerabilities.\r\nhttps://github.com/aws/aws-encryption-sdk-python/security/advisories/GHSA-x5h4-9gqw-942j", "cve": "PVE-2021-41848", "id": "pyup.io-41848", "more_info_path": "/vulnerabilities/PVE-2021-41848/41848", "specs": [ "<1.9.0", ">=2.0.0,<2.2.0" ], "v": "<1.9.0,>=2.0.0,<2.2.0" }, { "advisory": "Aws-encryption-sdk 2.0.0 includes a fix for CVE-2020-8897: A weak robustness vulnerability exists in the AWS Encryption SDKs for Java, Python, C and Javalcript prior to versions 2.0.0. Due to the non-committing property of AES-GCM (and other AEAD ciphers such as AES-GCM-SIV or (X)ChaCha20Poly1305) used by the SDKs to encrypt messages, an attacker can craft a unique cyphertext which will decrypt to multiple different results, and becomes especially relevant in a multi-recipient setting.\r\nhttps://github.com/google/security-research/security/advisories/GHSA-wqgp-vphw-hphf", "cve": "CVE-2020-8897", "id": "pyup.io-39129", "more_info_path": "/vulnerabilities/CVE-2020-8897/39129", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "aws-encryption-sdk-cli": [ { "advisory": "Aws-encryption-sdk-cli 1.8.0 and 2.1.0 include a security fix: CLI does not correctly implement strict mode.\r\nhttps://github.com/advisories/GHSA-2xwp-m7mq-7q3r", "cve": "PVE-2023-55097", "id": "pyup.io-55097", "more_info_path": "/vulnerabilities/PVE-2023-55097/55097", "specs": [ "<1.8.0", ">=2.0.0,<2.1.0" ], "v": "<1.8.0,>=2.0.0,<2.1.0" }, { "advisory": "Aws-encryption-sdk-cli versions 1.9.0 and 2.2.0 address several low severity issues related to streaming signed messages and restricting processing of certain types of invalid messages. See https://github.com/aws/aws-encryption-sdk-cli/security/advisories/GHSA-89v2-g37m-g3ff", "cve": "PVE-2021-42633", "id": "pyup.io-42633", "more_info_path": "/vulnerabilities/PVE-2021-42633/42633", "specs": [ "<1.9.0", ">=2.0.0,<2.2.0" ], "v": "<1.9.0,>=2.0.0,<2.2.0" }, { "advisory": "Aws-encryption-sdk-cli 4.1.0 no longer supports Python 3.5. The mentioned Python version doesn't receive security updates anymore.", "cve": "CVE-2020-27619", "id": "pyup.io-42631", "more_info_path": "/vulnerabilities/CVE-2020-27619/42631", "specs": [ "<4.1.0" ], "v": "<4.1.0" } ], "aws-kinesis-consumer": [ { "advisory": "Aws-kinesis-consumer 1.4.0 updates its dependency 'urllib3' to v1.26.4 to include a security fix.", "cve": "CVE-2021-28363", "id": "pyup.io-47023", "more_info_path": "/vulnerabilities/CVE-2021-28363/47023", "specs": [ "<1.4.0" ], "v": "<1.4.0" }, { "advisory": "Aws-kinesis-consumer 1.4.1 updates its dependency 'urllib3' to v1.26.5 to include a security fix.", "cve": "CVE-2021-33503", "id": "pyup.io-47022", "more_info_path": "/vulnerabilities/CVE-2021-33503/47022", "specs": [ "<1.4.1" ], "v": "<1.4.1" } ], "aws-login0tool": [ { "advisory": "Aws-login0tool is a typosquatting package. It installs a trojan in your system that leaks your data.\r\nhttps://medium.com/ochrona/3-new-malicious-packages-found-on-pypi-a6bbb14b5e2", "cve": "PVE-2022-45441", "id": "pyup.io-45441", "more_info_path": "/vulnerabilities/PVE-2022-45441/45441", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "aws-parallelcluster": [ { "advisory": "Aws-parallelcluster 2.4.0 removes AWS credentials from the ``parallelcluster`` config file for a better security posture. Credentials can now be set up following the canonical procedure used for the aws cli.", "cve": "PVE-2021-37211", "id": "pyup.io-37211", "more_info_path": "/vulnerabilities/PVE-2021-37211/37211", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Aws-parallelcluster 3.1.1 limits privileges associated with IAM Policies created within the cluster.\r\nhttps://github.com/aws/aws-parallelcluster/pull/3678", "cve": "PVE-2022-44934", "id": "pyup.io-44934", "more_info_path": "/vulnerabilities/PVE-2022-44934/44934", "specs": [ "<3.1.1" ], "v": "<3.1.1" }, { "advisory": "Aws-parallelcluster 3.2.1 updates Python from 3.7.10 to 3.7.13 to include a fix for CVE-2021-3737.", "cve": "CVE-2021-3737", "id": "pyup.io-51655", "more_info_path": "/vulnerabilities/CVE-2021-3737/51655", "specs": [ "<3.2.1" ], "v": "<3.2.1" } ], "aws-parallelcluster-node": [ { "advisory": "Aws-parallelcluster-node 3.5.0 adds validators to prevent malicious string injection.\r\nhttps://github.com/aws/aws-parallelcluster-node/commit/47012a17bd053211841e5fc37922164434623689", "cve": "PVE-2023-53391", "id": "pyup.io-53391", "more_info_path": "/vulnerabilities/PVE-2023-53391/53391", "specs": [ "<3.5.0" ], "v": "<3.5.0" } ], "aws-s3-tools": [ { "advisory": "Aws-s3-tools 0.1.0 and prior use 'ujson==5.1.0', that has an unfixed vulnerability fully affecting availability.\r\nhttps://github.com/ultrajson/ultrajson/pull/504", "cve": "CVE-2021-45958", "id": "pyup.io-44797", "more_info_path": "/vulnerabilities/CVE-2021-45958/44797", "specs": [ "<=0.1.0" ], "v": "<=0.1.0" } ], "aws-sam-cli": [ { "advisory": "The AWS Serverless Application Model (SAM) CLI, an open-source tool for building and deploying serverless applications on AWS, has a vulnerability in affected versions. When using the DockerBuildArgs parameter, sensitive data specified there may be exposed in clear text via STDERR during the sam build command. This could potentially reveal secrets to unauthorized parties. AWS recommends upgrading to SAM CLI v1.122.0 or later, which includes a patch for this issue. Users should review their logs if they've used DockerBuildArgs and consider rotating any potentially exposed secrets.", "cve": "PVE-2024-73183", "id": "pyup.io-73183", "more_info_path": "/vulnerabilities/PVE-2024-73183/73183", "specs": [ "<1.122.0" ], "v": "<1.122.0" }, { "advisory": "When running the AWS Serverless Application Model Command Line Interface (SAM CLI) build process with Docker and symlinks are included in the build files, the container environment allows a user to access privileged files on the host by leveraging the elevated permissions granted to the tool. A user could leverage the elevated permissions to access restricted files via symlinks and copy them to a more permissive location on the container. Users should upgrade to v1.133.0 or newer and ensure any forked or derivative code is patched to incorporate the new fixes.", "cve": "CVE-2025-3047", "id": "pyup.io-76459", "more_info_path": "/vulnerabilities/CVE-2025-3047/76459", "specs": [ "<1.133.0" ], "v": "<1.133.0" }, { "advisory": "After completing a build with AWS Serverless Application Model Command Line Interface (SAM CLI) which include symlinks, the content of those symlinks are copied to the cache of the local workspace as regular files or directories. As a result, a user who does not have access to those symlinks outside of the Docker container would now have access via the local workspace. Users should upgrade to version 1.134.0 and ensure any forked or derivative code is patched to incorporate the new fixes. After upgrading, users must re-build their applications using the sam build --use-container to update the symlinks.", "cve": "CVE-2025-3048", "id": "pyup.io-76460", "more_info_path": "/vulnerabilities/CVE-2025-3048/76460", "specs": [ "<1.134.0" ], "v": "<1.134.0" }, { "advisory": "Aws-sam-cli 1.51.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/aws/aws-sam-cli/pull/3905", "cve": "PVE-2023-59624", "id": "pyup.io-59624", "more_info_path": "/vulnerabilities/PVE-2023-59624/59624", "specs": [ "<1.51.0" ], "v": "<1.51.0" } ], "aws-v4signer": [ { "advisory": "Aws-v4signer version 0.6 updates its dependency 'pylint' to v2.5.3 to include a security fix.", "cve": "PVE-2021-38224", "id": "pyup.io-49035", "more_info_path": "/vulnerabilities/PVE-2021-38224/49035", "specs": [ "<0.6" ], "v": "<0.6" }, { "advisory": "Aws-v4signer version 0.6 updates its dependency 'pyyaml' to v5.4 to include security fixes.", "cve": "CVE-2020-1747", "id": "pyup.io-49034", "more_info_path": "/vulnerabilities/CVE-2020-1747/49034", "specs": [ "<0.6" ], "v": "<0.6" }, { "advisory": "Aws-v4signer version 0.6 updates its dependency 'pyyaml' to v5.4 to include security fixes.", "cve": "CVE-2020-14343", "id": "pyup.io-49033", "more_info_path": "/vulnerabilities/CVE-2020-14343/49033", "specs": [ "<0.6" ], "v": "<0.6" }, { "advisory": "Aws-v4signer version 0.6 updates its dependency 'pyyaml' to v5.4 to include security fixes.", "cve": "CVE-2019-20477", "id": "pyup.io-42019", "more_info_path": "/vulnerabilities/CVE-2019-20477/42019", "specs": [ "<0.6" ], "v": "<0.6" } ], "awsapilib": [ { "advisory": "Awsapilib 0.5.1 checks if the CSRF token retrieved has no value.\r\nhttps://github.com/schubergphilis/awsapilib/commit/73008b21d6995da2bd5e533fb0ed4216ca9d505b", "cve": "PVE-2022-48281", "id": "pyup.io-48281", "more_info_path": "/vulnerabilities/PVE-2022-48281/48281", "specs": [ "<0.5.1" ], "v": "<0.5.1" } ], "awscl": [ { "advisory": "Awscl is a malicious package, pytosquatting the popular package 'awscli'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.", "cve": "PVE-2023-53219", "id": "pyup.io-53219", "more_info_path": "/vulnerabilities/PVE-2023-53219/53219", "specs": [ ">=0" ], "v": ">=0" } ], "awscli": [ { "advisory": "awscli 1.11.83 fixes a possible security issue where files could be downloaded to a directory outside the destination directory if the key contained relative paths when downloading files recursively.\r\nhttps://github.com/aws/aws-cli/commit/6080bb0b302b59149a305bfa0a6a7c92a07d1ea5", "cve": "PVE-2021-34627", "id": "pyup.io-34627", "more_info_path": "/vulnerabilities/PVE-2021-34627/34627", "specs": [ "<1.11.83" ], "v": "<1.11.83" }, { "advisory": "Awscli 1.16.213 includes a fix for a Race Condition vulnerability on Windows clients.\r\nhttps://github.com/aws/aws-cli/issues/4247", "cve": "PVE-2023-59546", "id": "pyup.io-59546", "more_info_path": "/vulnerabilities/PVE-2023-59546/59546", "specs": [ "<1.16.213" ], "v": "<1.16.213" }, { "advisory": "Awscli 1.27.90 includes a fix for a potential low-serverity ReDoS vulnerability: An attacker being able to craft a malicious nuget.config file can cause ReDoS, when a user performs Nuget or Dotnet login.\r\nhttps://github.com/aws/aws-cli/commit/68ad24c36b4e3f6936e3d1dc76fda39d2d1fe764", "cve": "PVE-2023-58911", "id": "pyup.io-58911", "more_info_path": "/vulnerabilities/PVE-2023-58911/58911", "specs": [ "<1.27.90" ], "v": "<1.27.90" } ], "awsclie": [ { "advisory": "Awsclie is a malicious package, pytosquatting the popular package 'awscli'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.", "cve": "PVE-2023-53253", "id": "pyup.io-53253", "more_info_path": "/vulnerabilities/PVE-2023-53253/53253", "specs": [ ">=0" ], "v": ">=0" } ], "awsclii": [ { "advisory": "Awsclii is a malicious package, pytosquatting the popular package 'awscli'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.", "cve": "PVE-2023-53252", "id": "pyup.io-53252", "more_info_path": "/vulnerabilities/PVE-2023-53252/53252", "specs": [ ">=0" ], "v": ">=0" } ], "awscrt": [ { "advisory": "Awscrt 0.13.5 updates modules to fix a DoS vulnerability related to OpenSSL.\r\nhttps://github.com/awslabs/aws-crt-python/commit/35650740c87eed174a2e0d7f98b8f5b8fd23848f", "cve": "CVE-2022-0778", "id": "pyup.io-46418", "more_info_path": "/vulnerabilities/CVE-2022-0778/46418", "specs": [ "<0.13.5" ], "v": "<0.13.5" }, { "advisory": "Awscrt 0.16.11 ships with AWS-LC v1.5.0, which includes fix for CVE-2023-0286.", "cve": "CVE-2023-0286", "id": "pyup.io-59059", "more_info_path": "/vulnerabilities/CVE-2023-0286/59059", "specs": [ "<0.16.11" ], "v": "<0.16.11" } ], "awsiotsdk": [ { "advisory": "Awsiotsdk 1.5.18 includes a fix for CVE-2021-40828: Connections initialized by the AWS IoT Device SDK v2 for Java (versions prior to 1.3.3), Python (versions prior to 1.5.18), C++ (versions prior to 1.12.7) and Node.js (versions prior to 1.5.1) did not verify server certificate hostname during TLS handshake when overriding Certificate Authorities (CA) in their trust stores on Windows.", "cve": "CVE-2021-40828", "id": "pyup.io-42780", "more_info_path": "/vulnerabilities/CVE-2021-40828/42780", "specs": [ "<1.5.18" ], "v": "<1.5.18" }, { "advisory": "Awsiotsdk 1.6.1 includes a fix for CVE-2021-40829: Connections initialized by the AWS IoT Device SDK v2 for Java (versions prior to 1.4.2), Python (versions prior to 1.6.1), C++ (versions prior to 1.12.7) and Node.js (versions prior to 1.5.3) did not verify server certificate hostname during TLS handshake when overriding Certificate Authorities (CA) in their trust stores on MacOS.", "cve": "CVE-2021-40829", "id": "pyup.io-42781", "more_info_path": "/vulnerabilities/CVE-2021-40829/42781", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Awsiotsdk 1.6.1 includes a fix for CVE-2021-40830: The AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on Unix systems. TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system\u2019s default trust-store. Attackers with access to a host\u2019s trust stores or able to compromise a certificate authority already in the host's trust-store (note: the attacker must also be able to spoof DNS in this case), may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The 'aws_tls_ctx_options_override_default_trust_store_*' function within the aws-c-io submodule has been updated to override the default trust-store to correct this issue.\r\nhttps://github.com/aws/aws-iot-device-sdk-python-v2", "cve": "CVE-2021-40830", "id": "pyup.io-42782", "more_info_path": "/vulnerabilities/CVE-2021-40830/42782", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Awsiotsdk 1.7.0 includes a fix for CVE-2021-40831: The AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on macOS systems. Additionally, SNI validation is also not enabled when the CA has been \u201coverridden\u201d. TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system\u2019s default trust-store. Attackers with access to a host\u2019s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The 'aws_tls_ctx_options_override_default_trust_store_*' function within the aws-c-io submodule has been updated to address this behavior.", "cve": "CVE-2021-40831", "id": "pyup.io-42783", "more_info_path": "/vulnerabilities/CVE-2021-40831/42783", "specs": [ "<1.7.0" ], "v": "<1.7.0" } ], "awsipranges": [ { "advisory": "Awsipranges 0.3.3 updates its dependency 'ipython' to v7.31.1 to include a security fix.", "cve": "CVE-2022-21699", "id": "pyup.io-44947", "more_info_path": "/vulnerabilities/CVE-2022-21699/44947", "specs": [ "<0.3.3" ], "v": "<0.3.3" }, { "advisory": "Awsipranges 0.3.3 updates its dependency 'aiohttp' to v3.7.4 to include a security fix.", "cve": "CVE-2021-21330", "id": "pyup.io-44941", "more_info_path": "/vulnerabilities/CVE-2021-21330/44941", "specs": [ "<0.3.3" ], "v": "<0.3.3" } ], "awxkit": [ { "advisory": "Awkit 4.0.0 includes a fix for CVE-2019-3869: When running Tower before 3.4.3 on OpenShift or Kubernetes, application credentials are exposed to playbook job runs via environment variables. A malicious user with the ability to write playbooks could use this to gain administrative privileges.\r\nhttps://github.com/ansible/awx/commit/2129f1208597d5c84478df48e0770e7b81b658ec", "cve": "CVE-2019-3869", "id": "pyup.io-42339", "more_info_path": "/vulnerabilities/CVE-2019-3869/42339", "specs": [ "<4.0.0" ], "v": "<4.0.0" } ], "axonflow": [ { "advisory": "Axonflow 3.0.0", "cve": "PVE-2026-83875", "id": "pyup.io-83875", "more_info_path": "/vulnerabilities/PVE-2026-83875/83875", "specs": [ "<3.0.0" ], "v": "<3.0.0" } ], "azure-cli": [ { "advisory": "Azure CLI is the command-line interface for Microsoft Azure. In versions previous to 2.40.0, Azure CLI contains a vulnerability for potential code injection. Critical scenarios are where a hosting machine runs an Azure CLI command where parameter values have been provided by an external source. The vulnerability is only applicable when the Azure CLI command is run on a Windows machine and with any version of PowerShell and when the parameter value contains the '&' or '|' symbols. If any of these prerequisites are not met, this vulnerability is not applicable. Users should upgrade to version 2.40.0 or greater to receive a a mitigation for the vulnerability.", "cve": "CVE-2022-39327", "id": "pyup.io-54575", "more_info_path": "/vulnerabilities/CVE-2022-39327/54575", "specs": [ ">=0,<2.40.0" ], "v": ">=0,<2.40.0" } ], "azure-cli-ml-preview": [ { "advisory": "Azure-cli-ml-preview is a malicious package, typosquatting. It aims at targeting Azure environments.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick", "cve": "PVE-2022-47808", "id": "pyup.io-47808", "more_info_path": "/vulnerabilities/PVE-2022-47808/47808", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "azure-cli-ml-private-preview": [ { "advisory": "Azure-cli-ml-private-preview is a malicious package, typosquatting. It aims at targeting Azure environments.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick", "cve": "PVE-2022-47810", "id": "pyup.io-47810", "more_info_path": "/vulnerabilities/PVE-2022-47810/47810", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "azure-core": [ { "advisory": "Affected versions of the azure-core package are vulnerable to Deserialization of Untrusted Data due to unsafe deserialization of attacker-supplied data. Azure Core\u2019s shared client library deserializes untrusted data received over the network without sufficiently ensuring that the resulting objects are valid and safe, which can allow for the construction of dangerous objects during the deserialization process.", "cve": "CVE-2026-21226", "id": "pyup.io-84420", "more_info_path": "/vulnerabilities/CVE-2026-21226/84420", "specs": [ "<1.38.0" ], "v": "<1.38.0" } ], "azure-functions": [ { "advisory": "Version 1.0.11184 of Azure Functions resolves a race condition in logging operations. This update ensures consistent and reliable log entries, even when multiple functions write simultaneously.\r\nhttps://github.com/Azure/azure-webjobs-sdk/pull/1319/commits/b6893d484fc77c893458ce3201a042ce7ae3d456", "cve": "PVE-2024-63814", "id": "pyup.io-63814", "more_info_path": "/vulnerabilities/PVE-2024-63814/63814", "specs": [ "<1.0.11184" ], "v": "<1.0.11184" } ], "azure-identity": [ { "advisory": "Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability.", "cve": "CVE-2024-35255", "id": "pyup.io-71690", "more_info_path": "/vulnerabilities/CVE-2024-35255/71690", "specs": [ "<1.16.1" ], "v": "<1.16.1" } ], "azure-smtp-relay": [ { "advisory": "Azure-smtp-relay version 1.0.6 has updated its aiosmtpd dependency to version 1.4.5 to address the security vulnerability identified in CVE-2024-27305.", "cve": "CVE-2024-27305", "id": "pyup.io-68073", "more_info_path": "/vulnerabilities/CVE-2024-27305/68073", "specs": [ "<1.0.6" ], "v": "<1.0.6" } ], "azureml-contrib-jupyterrun": [ { "advisory": "Azureml-contrib-jupyterrun is a malicious package, typosquatting. It aims at targeting Azure environments.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick", "cve": "PVE-2022-47806", "id": "pyup.io-47806", "more_info_path": "/vulnerabilities/PVE-2022-47806/47806", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "azureml-contrib-optimization": [ { "advisory": "Azureml-contrib-optimization is a malicious package, typosquatting. It aims at targeting Azure environments.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick", "cve": "PVE-2022-47811", "id": "pyup.io-47811", "more_info_path": "/vulnerabilities/PVE-2022-47811/47811", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "azureml-contrib-reports": [ { "advisory": "Azureml-contrib-reports is a malicious package, typosquatting. It aims at targeting Azure environments.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick", "cve": "PVE-2022-47807", "id": "pyup.io-47807", "more_info_path": "/vulnerabilities/PVE-2022-47807/47807", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "b-cfn-custom-api-key-authorizer": [ { "advisory": "B-cfn-custom-api-key-authorizer 2.0.0 hashes api secrets to avoid leaks if the database is breached.", "cve": "PVE-2022-48259", "id": "pyup.io-48259", "more_info_path": "/vulnerabilities/PVE-2022-48259/48259", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "b2": [ { "advisory": "B2 Command Line Tool is the official command line tool for the backblaze cloud storage service. Linux and Mac releases of the B2 command-line tool version 3.2.0 and below contain a key disclosure vulnerability that, in certain conditions, can be exploited by local attackers through a time-of-check-time-of-use (TOCTOU) race condition. The command line tool saves API keys (and bucket name-to-id mapping) in a local database file (`$XDG_CONFIG_HOME/b2/account_info`, `~/.b2_account_info` or a user-defined path) when `b2 authorize-account` is first run. This happens regardless of whether a valid key is provided or not. When first created, the file is world readable and is (typically a few milliseconds) later altered to be private to the user. If the directory is readable by a local attacker and the user did not yet run `b2 authorize-account` then during the brief period between file creation and permission modification, a local attacker can race to open the file and maintain a handle to it. This allows the local attacker to read the contents after the file after the sensitive information has been saved to it. Users that have not yet run `b2 authorize-account` should upgrade to B2 Command-Line Tool v3.2.1 before running it. Users that have run `b2 authorize-account` are safe if at the time of the file creation no other local users had read access to the local configuration file. Users that have run `b2 authorize-account` where the designated path could be opened by another local user should upgrade to B2 Command-Line Tool v3.2.1 and remove the database and regenerate all application keys. Note that `b2 clear-account` does not remove the database file and it should not be used to ensure that all open handles to the file are invalidated. If B2 Command-Line Tool cannot be upgraded to v3.2.1 due to a dependency conflict, a binary release can be used instead. Alternatively a new version could be installed within a virtualenv, or the permissions can be changed to prevent local users from opening the database file.", "cve": "CVE-2022-23653", "id": "pyup.io-54274", "more_info_path": "/vulnerabilities/CVE-2022-23653/54274", "specs": [ ">=0,<3.2.1" ], "v": ">=0,<3.2.1" } ], "b2sdk": [ { "advisory": "B2sdk 1.14.1 includes a fix for CVE-2022-23651: Linux and Mac releases of the SDK version 1.14.0 and below contain a key disclosure vulnerability that, in certain conditions, can be exploited by local attackers through a time-of-check-time-of-use (TOCTOU) race condition. SDK users of the SqliteAccountInfo format are vulnerable while users of the InMemoryAccountInfo format are safe. The SqliteAccountInfo saves API keys (and bucket name-to-id mapping) in a local database file ($XDG_CONFIG_HOME/b2/account_info, ~/.b2_account_info or a user-defined path). When first created, the file is world readable and is (typically a few milliseconds) later altered to be private to the user. If the directory containing the file is readable by a local attacker then during the brief period between file creation and permission modification, a local attacker can race to open the file and maintain a handle to it. This allows the local attacker to read the contents after the file after the sensitive information has been saved to it. Consumers of this SDK who rely on it to save data using SqliteAccountInfo class should upgrade to the latest version of the SDK. Those who believe a local user might have opened a handle using this race condition, should remove the affected database files and regenerate all application keys.\r\nhttps://github.com/Backblaze/b2-sdk-python/security/advisories/GHSA-p867-fxfr-ph2w", "cve": "CVE-2022-23651", "id": "pyup.io-45392", "more_info_path": "/vulnerabilities/CVE-2022-23651/45392", "specs": [ "<=1.14.0" ], "v": "<=1.14.0" } ], "babel": [ { "advisory": "Babel 2.9.1 includes a fix for CVE-2021-42771: Babel.Locale in Babel before 2.9.1 allows attackers to load arbitrary locale .dat files (containing serialized Python objects) via directory traversal, leading to code execution.\r\nhttps://github.com/python-babel/babel/pull/782", "cve": "CVE-2021-42771", "id": "pyup.io-42203", "more_info_path": "/vulnerabilities/CVE-2021-42771/42203", "specs": [ "<2.9.1" ], "v": "<2.9.1" } ], "backend-ai": [ { "advisory": "Backend.ai 19.03.0b1 supports running multiple managers on the same host by randomizing internal IPC socket addresses. This also improves the security a little.", "cve": "PVE-2021-39087", "id": "pyup.io-39087", "more_info_path": "/vulnerabilities/PVE-2021-39087/39087", "specs": [ "<19.03.0b1" ], "v": "<19.03.0b1" }, { "advisory": "Backend.ai 19.03.0rc1 supports authentication with etcd and Redis for better security.", "cve": "PVE-2021-39086", "id": "pyup.io-39086", "more_info_path": "/vulnerabilities/PVE-2021-39086/39086", "specs": [ "<19.03.0rc1" ], "v": "<19.03.0rc1" }, { "advisory": "Backend.ai 19.09.0rc4 includes image import. This is implemented on top of batch tasks, with some specialization to prevent security issues due to direct access to agent host's Docker daemon. Importing as service-port only image support will be added in future releases. Additionally, it includes a privilege escalation fix because domain-admins could run sessions on behalf of super-admins in the same domain.", "cve": "PVE-2021-38675", "id": "pyup.io-38675", "more_info_path": "/vulnerabilities/PVE-2021-38675/38675", "specs": [ "<19.09.0rc4" ], "v": "<19.09.0rc4" } ], "backend-ai-client": [ { "advisory": "Backend.ai-client version 21.09.0a1 updates its dependency 'PyYaml' to v5.4.1 to include a security fix.", "cve": "CVE-2020-14343", "id": "pyup.io-41219", "more_info_path": "/vulnerabilities/CVE-2020-14343/41219", "specs": [ "<21.09.0a1" ], "v": "<21.09.0a1" } ], "backend-ai-manager": [ { "advisory": "Backend.ai-manager 19.09.0rc4 fixes privilege escalation because domain-admins could run sessions on behalf of super-admins in the same domain. It also introduces Image import (171) - currently this is limited to import Python-based kernels only. This is implemented on top of batch tasks, with some specialization to prevent security issues due to direct access to agent host's Docker daemon. Importing as service-port only image support will be added in future releases.", "cve": "PVE-2021-37531", "id": "pyup.io-37531", "more_info_path": "/vulnerabilities/PVE-2021-37531/37531", "specs": [ "<19.09.0rc4" ], "v": "<19.09.0rc4" }, { "advisory": "Backend-ai-manager 19.09.0rc4 fixes a privilege escalation where domain-admins could run sessions on behalf of super-admins in the same domain.", "cve": "PVE-2025-76933", "id": "pyup.io-76933", "more_info_path": "/vulnerabilities/PVE-2025-76933/76933", "specs": [ "<19.09.0rc4" ], "v": "<19.09.0rc4" } ], "backend-ai-webserver": [ { "advisory": "Backend.ai-webserver 22.03.0a1 prevents too many login attempts.\r\nhttps://github.com/lablup/backend.ai-webserver/pull/29", "cve": "PVE-2022-46407", "id": "pyup.io-46407", "more_info_path": "/vulnerabilities/PVE-2022-46407/46407", "specs": [ "<22.03.0a1" ], "v": "<22.03.0a1" } ], "backend.ai": [ { "advisory": "Exposure of sensitive data in active sessions in Lablup's BackendAI allows attackers to retrieve credentials for users on the management platform.", "cve": "CVE-2025-49653", "id": "pyup.io-77682", "more_info_path": "/vulnerabilities/CVE-2025-49653/77682", "specs": [ "<=25.3.3" ], "v": "<=25.3.3" }, { "advisory": "Missing Authorization in Lablup's BackendAI allows attackers to take over all active sessions; Accessing, stealing, or altering any data accessible in the session. This vulnerability exists in all current versions of BackendAI.", "cve": "CVE-2025-49651", "id": "pyup.io-77681", "more_info_path": "/vulnerabilities/CVE-2025-49651/77681", "specs": [ "<=25.3.3" ], "v": "<=25.3.3" }, { "advisory": "Missing Authentication in the registration feature of Lablup's BackendAI allows arbitrary users to create user accounts that can access private data even when registration is disabled.", "cve": "CVE-2025-49652", "id": "pyup.io-77683", "more_info_path": "/vulnerabilities/CVE-2025-49652/77683", "specs": [ "<=25.3.3" ], "v": "<=25.3.3" } ], "backend.ai-manager": [ { "advisory": "Backend.ai-manager 21.03.0 fixes a potential vulnerability: a remote code execution risk associated with the YAML file loading process. This update introduces `yaml.safe_load()` for all YAML loader invocations.\r\nhttps://github.com/lablup/backend.ai-manager/pull/395/commits/844ef52aa6f9fa4e7aac231eedabb7fd7425f967", "cve": "PVE-2024-64058", "id": "pyup.io-64058", "more_info_path": "/vulnerabilities/PVE-2024-64058/64058", "specs": [ "<21.03.0" ], "v": "<21.03.0" } ], "badkeys": [ { "advisory": "Affected versions of the badkeys package are vulnerable to Improper Neutralization of Escape, Meta, or Control Sequences due to printing attacker-controlled key material and filenames to the console without escaping.", "cve": "CVE-2026-21439", "id": "pyup.io-83954", "more_info_path": "/vulnerabilities/CVE-2026-21439/83954", "specs": [ "<0.0.16" ], "v": "<0.0.16" } ], "baeutifulsoup4": [ { "advisory": "Baeutifulsoup4 is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.", "cve": "PVE-2022-51735", "id": "pyup.io-51735", "more_info_path": "/vulnerabilities/PVE-2022-51735/51735", "specs": [ ">0" ], "v": ">0" } ], "bakefile": [ { "advisory": "Affected versions of this package are vulnerable to Arbitrary Code Execution via Unsafe Module Loading. The `write_bakefile` function in `write_bakefile.py` accepts arbitrary Python module objects without validating that they belong to trusted sample modules, allowing attackers to pass malicious modules that can execute arbitrary code when their `__file__` attribute is accessed or content is read. An attacker can exploit this vulnerability by crafting a malicious module object with a manipulated `__file__` path pointing to sensitive files (e.g., /etc/passwd) or malicious Python code, leading to arbitrary file read, code execution, or system compromise when the bakefile is written.", "cve": "PVE-2026-84854", "id": "pyup.io-84854", "more_info_path": "/vulnerabilities/PVE-2026-84854/84854", "specs": [ "<0.0.7" ], "v": "<0.0.7" } ], "bakercm": [ { "advisory": "Bakercm 0.4.4 updates its dependency 'pycryptodome' to v3.6.6 to include a security fix.", "cve": "CVE-2018-15560", "id": "pyup.io-36651", "more_info_path": "/vulnerabilities/CVE-2018-15560/36651", "specs": [ "<0.4.4" ], "v": "<0.4.4" } ], "bandersnatch": [ { "advisory": "Bandersnatch 1.6 includes a fix for a potential race condition vulnerability.\r\nhttps://github.com/pypa/bandersnatch/commit/59ceeeef16da461861b8b4b8b6910c9c2434558e", "cve": "PVE-2023-61428", "id": "pyup.io-61428", "more_info_path": "/vulnerabilities/PVE-2023-61428/61428", "specs": [ "<1.6" ], "v": "<1.6" } ], "bandit": [ { "advisory": "Bandit 1.6.3 updates its dependency 'pyyaml' to v5.3.1 to include security fixes.", "cve": "CVE-2020-1747", "id": "pyup.io-39277", "more_info_path": "/vulnerabilities/CVE-2020-1747/39277", "specs": [ "<1.6.3" ], "v": "<1.6.3" }, { "advisory": "Bandit 1.6.3 updates its dependency 'pyyaml' to v5.3.1 to include security fixes.", "cve": "CVE-2017-18342", "id": "pyup.io-45736", "more_info_path": "/vulnerabilities/CVE-2017-18342/45736", "specs": [ "<1.6.3" ], "v": "<1.6.3" }, { "advisory": "Bandit 1.7.7 identifies the str.replace method as a potential risk for SQL injection because it can be misused in constructing SQL queries, potentially enabling the execution of arbitrary SQL code.\r\nhttps://github.com/PyCQA/bandit/pull/1044/commits/d909043ba20853c90a7cad4a5b58a180f6937bf8", "cve": "PVE-2024-64484", "id": "pyup.io-64484", "more_info_path": "/vulnerabilities/PVE-2024-64484/64484", "specs": [ "<1.7.7" ], "v": "<1.7.7" } ], "barbican": [ { "advisory": "Barbican 12.0.2, 13.0.1 and 14.0.1 include a fix for CVE-2022-3100: This issue allows an access policy bypass via a query string when accessing the API.\r\nhttps://github.com/openstack/barbican/commit/6112c302375bf3d4c27303d12beec52ce2a82a2b", "cve": "CVE-2022-3100", "id": "pyup.io-52879", "more_info_path": "/vulnerabilities/CVE-2022-3100/52879", "specs": [ "<12.0.2", ">=13.0.0.0rc1,<13.0.1", ">=14.0.0.0rc1,<14.0.1" ], "v": "<12.0.2,>=13.0.0.0rc1,<13.0.1,>=14.0.0.0rc1,<14.0.1" }, { "advisory": "Barbican 14.0.0.0rc1 includes a fix for CVE-2022-23451: An authorization flaw was found in openstack-barbican. The default policy rules for the secret metadata API allowed any authenticated user to add, modify, or delete metadata from any secret regardless of ownership. This flaw allows an attacker on the network to modify or delete protected data, causing a denial of service by consuming protected resources.\r\nhttps://github.com/openstack/barbican/commit/7d270bacbe29a90a10f1855abc3b50dac0f08022", "cve": "CVE-2022-23451", "id": "pyup.io-50929", "more_info_path": "/vulnerabilities/CVE-2022-23451/50929", "specs": [ "<14.0.0.0rc1" ], "v": "<14.0.0.0rc1" }, { "advisory": "Barbican 14.0.0.0rc1 includes a fix for CVE-2022-23452: An authorization flaw was found in openstack-barbican, where anyone with an admin role could add secrets to a different project container. This flaw allows an attacker on the network to consume protected resources and cause a denial of service.\r\nhttps://review.opendev.org/c/openstack/barbican/+/814200", "cve": "CVE-2022-23452", "id": "pyup.io-50879", "more_info_path": "/vulnerabilities/CVE-2022-23452/50879", "specs": [ "<14.0.0.0rc1" ], "v": "<14.0.0.0rc1" }, { "advisory": "Barbican 17.0.0.0rc1 and prior versions are affected by CVE-2023-1636: A vulnerability was found in OpenStack Barbican containers. This vulnerability is only applicable to deployments that utilize an all-in-one configuration. Barbican containers share the same CGROUP, USER, and NET namespace with the host system and other OpenStack services. If any service is compromised, it could gain access to the data transmitted to and from Barbican.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=2181765", "cve": "CVE-2023-1636", "id": "pyup.io-61408", "more_info_path": "/vulnerabilities/CVE-2023-1636/61408", "specs": [ "<=17.0.0.0rc1" ], "v": "<=17.0.0.0rc1" }, { "advisory": "Barbican 17.0.0.0rc1 and prior versions are affected by CVE-2023-1633: A credentials leak flaw was found in OpenStack Barbican. This flaw allows a local authenticated attacker to read the configuration file, gaining access to sensitive credentials.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=2181761", "cve": "CVE-2023-1633", "id": "pyup.io-61407", "more_info_path": "/vulnerabilities/CVE-2023-1633/61407", "specs": [ "<=17.0.0.0rc1" ], "v": "<=17.0.0.0rc1" } ], "barman": [ { "advisory": "Barman 2.11 removes the strict superuser requirement for PG 10+. As of PostgreSQL 10 it is possible to execute \r\nbackups without superuser privileges, which is actually the recommended method for security reasons. Non-superuser backups need to grant some privileges to the user used by Barman to connect to PostgreSQL, as documented in the 21-preliminary_steps.en.md section.\r\n\r\nIt also ensures each postgres connection has an empty search_path. This is the only safe option when there is no information about how secure the search path is on the target database. This is done by appending \"options=-csearch_path=\" to any conninfo string.", "cve": "PVE-2021-38502", "id": "pyup.io-38502", "more_info_path": "/vulnerabilities/PVE-2021-38502/38502", "specs": [ "<2.11" ], "v": "<2.11" } ], "bas-air-unit-network-dataset": [ { "advisory": "Bas-air-unit-network-dataset 0.3.0 updates its dependency 'certifi' to v2023.11.17 to include a security fix.", "cve": "CVE-2023-37920", "id": "pyup.io-62496", "more_info_path": "/vulnerabilities/CVE-2023-37920/62496", "specs": [ "<0.3.0" ], "v": "<0.3.0" } ], "baseplate": [ { "advisory": "Baseplate 0.19.0 includes support for fetching secrets in a secure, auditable, manner from Hashicorp Vault. A sidecar daemon manages the infrastructure-level authentication with Vault and fetches secrets to a file on disk. Helpers in Baseplate then allow your application to fetch these secrets efficiently from the sidecar daemon with some helpful conventions for versioning/key rotation. This is now the right way to get secret tokens into your application going forward. See: .", "cve": "PVE-2021-38349", "id": "pyup.io-38349", "more_info_path": "/vulnerabilities/PVE-2021-38349/38349", "specs": [ "<0.19.0" ], "v": "<0.19.0" }, { "advisory": "Authentication tokens in baseplate 0.22.0 provided by the authentication service can now be automatically propagated between services when making Thrift calls. This allows internal services to securely and accurately understand on whose behalf a given request is being made so they can decide if the requester is authorized for a particular action. The context is passed implicitly, in request headers, so no extra parameters need be added to service IDLs. Baseplate provides APIs for validating and accessing the tokens from within request context and will automatically pass upstream credentials to downstream services without extra work.", "cve": "PVE-2021-38348", "id": "pyup.io-38348", "more_info_path": "/vulnerabilities/PVE-2021-38348/38348", "specs": [ "<0.22.0" ], "v": "<0.22.0" }, { "advisory": "Baseplate 0.24.0 includes a EdgeRequestContext/AuthenticationToken unification. This isn't a new addition, but a **breaking** rework of authentication context in Baseplate. Authentication token propagation and access is now fully integrated into the edge request context. Authentication tokens are propagated inside the edge context header and the API for applications built on Baseplate is unified. See below for details on how to use this.", "cve": "PVE-2021-38347", "id": "pyup.io-38347", "more_info_path": "/vulnerabilities/PVE-2021-38347/38347", "specs": [ "<0.24.0" ], "v": "<0.24.0" }, { "advisory": "Services often need to securely store username/password pairs. Baseplate 0.30.0 has a convention for doing so called a credential secret. In addition, the sqlalchemy integration now uses this new credential type and you can expect other integrations to do so in the future. See also: .", "cve": "PVE-2021-38346", "id": "pyup.io-38346", "more_info_path": "/vulnerabilities/PVE-2021-38346/38346", "specs": [ "<0.30.0" ], "v": "<0.30.0" } ], "basicsr": [ { "advisory": "XPixelGroup BasicSR Command Injection", "cve": "CVE-2024-27763", "id": "pyup.io-76309", "more_info_path": "/vulnerabilities/CVE-2024-27763/76309", "specs": [ "<1.4.2" ], "v": "<1.4.2" } ], "basketball-reference-web-scraper": [ { "advisory": "Basketball-reference-web-scraper 4.2.2 includes upgrades the `urllib3` library to `1.25.2` due to a security vulnerability with versions less than `1.24.2`.", "cve": "PVE-2021-37123", "id": "pyup.io-37123", "more_info_path": "/vulnerabilities/PVE-2021-37123/37123", "specs": [ "<4.2.2" ], "v": "<4.2.2" }, { "advisory": "Basketball-reference-web-scraper 4.2.3 updates urllib3 to 1.24.3 to avoid a security vulnerability.", "cve": "CVE-2019-11324", "id": "pyup.io-37195", "more_info_path": "/vulnerabilities/CVE-2019-11324/37195", "specs": [ "<4.2.3" ], "v": "<4.2.3" } ], "basxconnect": [ { "advisory": "Basxconnect 0.3.54 fixes a missing CSRF token issue.\r\nhttps://github.com/basxsoftwareassociation/basxconnect/commit/6d5809b78dcf033e4f0ca30e305dd3a382f56709", "cve": "PVE-2021-42928", "id": "pyup.io-42928", "more_info_path": "/vulnerabilities/PVE-2021-42928/42928", "specs": [ "<0.3.54" ], "v": "<0.3.54" } ], "bauh": [ { "advisory": "Bauh 0.10.3 prevents command injection through the search mechanism.\r\nhttps://github.com/vinifmor/bauh/issues/266", "cve": "PVE-2022-49145", "id": "pyup.io-49145", "more_info_path": "/vulnerabilities/PVE-2022-49145/49145", "specs": [ "<0.10.3" ], "v": "<0.10.3" } ], "baybe": [ { "advisory": "Baybe 0.4.1 updates its dependency 'scipy' to v1.10.1 to include a security fix.", "cve": "CVE-2023-25399", "id": "pyup.io-62619", "more_info_path": "/vulnerabilities/CVE-2023-25399/62619", "specs": [ "<0.4.1" ], "v": "<0.4.1" }, { "advisory": "Baybe 0.8.2 has updated its onnx dependency to version 1.16.0 or newer to address the security issue CVE-2024-27318.", "cve": "CVE-2024-27318", "id": "pyup.io-66978", "more_info_path": "/vulnerabilities/CVE-2024-27318/66978", "specs": [ "<0.8.2" ], "v": "<0.8.2" } ], "bayesian-testing": [ { "advisory": "Bayesian-testing 0.2.2 updates its dependency 'ipython' to v7.32.0 to include a security fix.", "cve": "CVE-2022-21699", "id": "pyup.io-47840", "more_info_path": "/vulnerabilities/CVE-2022-21699/47840", "specs": [ "<0.2.2" ], "v": "<0.2.2" }, { "advisory": "Bayesian-testing 0.2.2 updates its dependency 'jupyter-server' to v1.16.0 to include a security fix.", "cve": "CVE-2022-24757", "id": "pyup.io-47846", "more_info_path": "/vulnerabilities/CVE-2022-24757/47846", "specs": [ "<0.2.2" ], "v": "<0.2.2" }, { "advisory": "Bayesian-testing 0.2.3 updates its dependency 'jupyter-server' to v1.18.1 to include a security fix.", "cve": "CVE-2022-29241", "id": "pyup.io-50161", "more_info_path": "/vulnerabilities/CVE-2022-29241/50161", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Bayesian-testing 0.5.5 updates its dependency 'requests' to version '2.31.0' to include a fix for an Information Exposure vulnerability.\r\nhttps://github.com/Matt52/bayesian-testing/commit/1e05416c8670426b3bc8e4386da998deaa66833e", "cve": "CVE-2023-32681", "id": "pyup.io-60524", "more_info_path": "/vulnerabilities/CVE-2023-32681/60524", "specs": [ "<0.5.5" ], "v": "<0.5.5" }, { "advisory": "Bayesian-testing 0.5.5 updates its dependency 'certifi' to version '2023.07.22' to include a fix for a vulnerability.\r\nhttps://github.com/Matt52/bayesian-testing/commit/1e05416c8670426b3bc8e4386da998deaa66833e", "cve": "CVE-2023-37920", "id": "pyup.io-60517", "more_info_path": "/vulnerabilities/CVE-2023-37920/60517", "specs": [ "<0.5.5" ], "v": "<0.5.5" }, { "advisory": "Bayesian-testing 0.5.5 updates its dependency 'pygments' to version '2.16.1' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/Matt52/bayesian-testing/commit/1e05416c8670426b3bc8e4386da998deaa66833e", "cve": "CVE-2022-40896", "id": "pyup.io-60523", "more_info_path": "/vulnerabilities/CVE-2022-40896/60523", "specs": [ "<0.5.5" ], "v": "<0.5.5" }, { "advisory": "Bayesian-testing 0.5.6 updates its dependency 'urllib3' to v2.0.7 to include a security fix.", "cve": "CVE-2023-45803", "id": "pyup.io-62261", "more_info_path": "/vulnerabilities/CVE-2023-45803/62261", "specs": [ "<0.5.6" ], "v": "<0.5.6" }, { "advisory": "Bayesian-testing version 0.6.2 updates its `idna` dependency from version 3.6 to 3.7 due to CVE-2024-3651.", "cve": "CVE-2024-3651", "id": "pyup.io-71044", "more_info_path": "/vulnerabilities/CVE-2024-3651/71044", "specs": [ "<0.6.2" ], "v": "<0.6.2" } ], "bbcode": [ { "advisory": "Bbcode 1.0.18 escapes quotes to prevent XSS.\r\nhttps://github.com/dcwatson/bbcode/issues/4\r\nhttps://github.com/dcwatson/bbcode/commit/e23f5ae9f9e42a9988a52b8b39815593c264f3ce", "cve": "PVE-2021-25634", "id": "pyup.io-25634", "more_info_path": "/vulnerabilities/PVE-2021-25634/25634", "specs": [ "<1.0.18" ], "v": "<1.0.18" }, { "advisory": "Bbcode versions before 1.0.9 are vulnerable to cross-site scripting (XSS) attacks because they fail to escape certain symbols, such as double quotes (\"), single quotes ('), commas (,), and periods (.). XSS attacks allow attackers to execute malicious scripts in users' browsers by inserting unescaped characters into web applications, which do not validate or sanitize these inputs. This can lead to a range of malicious activities, including session hijacking, exposure of sensitive information, and malware delivery. There are several types of XSS attacks, including Stored (where malicious code is stored on the server and executed when a user interacts with it), Reflected (where the user is tricked into clicking a malicious link that sends a request to a vulnerable site, which then reflects the attack back to the user), DOM-based (where the attack is delivered via client-side rendered pages), and Mutated (where injected code is modified by the browser to become malicious).\r\nhttps://github.com/dcwatson/bbcode/commit/116cb2067003e6c6f679ed3a34e9e00a97a332cf", "cve": "PVE-2024-99802", "id": "pyup.io-66013", "more_info_path": "/vulnerabilities/PVE-2024-99802/66013", "specs": [ ">=0,<1.0.9" ], "v": ">=0,<1.0.9" } ], "bbot": [ { "advisory": "Affected versions of the bbot package are vulnerable to Remote Code Execution due to insufficient sanitization of .git metadata processed by the gitdumper.py module. The gitdumper.py logic accepts target-controlled .git/config and .git/index files and, without constraining file paths or stripping dangerous hooks before invoking git checkout, allows Path Traversal and arbitrary file writes that lead to code execution.", "cve": "CVE-2025-10283", "id": "pyup.io-80318", "more_info_path": "/vulnerabilities/CVE-2025-10283/80318", "specs": [ "<2.7.0" ], "v": "<2.7.0" }, { "advisory": "Affected versions of the bbot package are vulnerable to Information Disclosure due to unsafe URL handling in the git_clone.py module that can send a user\u2019s github.com API key to non-GitHub hosts. The git_clone.py logic uses a configured GitHub API token when processing user-supplied repository URLs without validating the destination host, meaning workflows that enable modules such as github_codesearch, github_workflows, gitlab, git_clone, github_usersearch, or github_org can inadvertently transmit the secret to an attacker-controlled endpoint.", "cve": "CVE-2025-10281", "id": "pyup.io-80317", "more_info_path": "/vulnerabilities/CVE-2025-10281/80317", "specs": [ "<2.7.0" ], "v": "<2.7.0" }, { "advisory": "Affected versions of the bbot package are vulnerable to Path Traversal due to improper archive extraction logic in bbot/modules/internal/unarchive.py that can allow writes outside the intended destination directory. The handle_event method in unarchive.py derives the extraction directory from an attacker-influenced path and unpacks crafted archives without sufficient constraints, and it previously failed to abort when the destination directory already existed, enabling arbitrary file writes to unintended locations.", "cve": "CVE-2025-10284", "id": "pyup.io-80316", "more_info_path": "/vulnerabilities/CVE-2025-10284/80316", "specs": [ "<2.7.0" ], "v": "<2.7.0" }, { "advisory": "Affected versions of the bbot package are vulnerable to Information Disclosure due to improper host validation when attaching the configured \u201cgitlab\u201d API key. The gitlab.py module includes the user\u2019s \u201cgitlab\u201d token on requests to GitLab-like hosts discovered during scans without constraining the destination to gitlab.com, enabling credential transmission to arbitrary on-premise endpoints.", "cve": "CVE-2025-10282", "id": "pyup.io-80862", "more_info_path": "/vulnerabilities/CVE-2025-10282/80862", "specs": [ ">=2.7.0.6919rc0,<2.7.2" ], "v": ">=2.7.0.6919rc0,<2.7.2" } ], "bcfg2": [ { "advisory": "The server in Bcfg2 1.1.2 and earlier, and 1.2 prerelease, allows remote attackers to execute arbitrary commands via shell metacharacters in data received from a client.", "cve": "CVE-2011-3211", "id": "pyup.io-62023", "more_info_path": "/vulnerabilities/CVE-2011-3211/62023", "specs": [ "<=1.1.2", "==1.2.0pre1", "==1.2.0pre2", "==1.2.0pre3" ], "v": "<=1.1.2,==1.2.0pre1,==1.2.0pre2,==1.2.0pre3" }, { "advisory": "The Trigger plugin in bcfg2 1.2.x before 1.2.3 allows remote attackers with root access to the client to execute arbitrary commands via shell metacharacters in the UUID field to the server process (bcfg2-server).", "cve": "CVE-2012-3366", "id": "pyup.io-65836", "more_info_path": "/vulnerabilities/CVE-2012-3366/65836", "specs": [ ">=1.2,<1.2.3" ], "v": ">=1.2,<1.2.3" } ], "bcryptify": [ { "advisory": "Affected versions of bcryptify are vulnerable to Cryptographic Failure due to nonce (initialization vector) reuse in AES-GCM encryption operations. The AES-GCM implementation fails to generate unique nonces for each encryption operation, leading to catastrophic security failures where attackers can recover authentication keys, forge messages, and potentially decrypt all encrypted data by exploiting the mathematical properties of the reused nonce-key pairs.", "cve": "PVE-2025-77830", "id": "pyup.io-77830", "more_info_path": "/vulnerabilities/PVE-2025-77830/77830", "specs": [ "<1.1.2" ], "v": "<1.1.2" } ], "bdi-kit": [ { "advisory": "Bdi-kit updates its nltk requirement to >=3.9.1 to address security vulnerability CVE-2024-39705.", "cve": "CVE-2024-39705", "id": "pyup.io-75053", "more_info_path": "/vulnerabilities/CVE-2024-39705/75053", "specs": [ "<0.4.0" ], "v": "<0.4.0" } ], "beaker": [ { "advisory": "Beaker before 0.8.9 allows a sandbox escape, enabling system access and code execution. This occurs because Electron context isolation is not used, and therefore an attacker can conduct a prototype-pollution attack against the Electron internal messaging API.", "cve": "CVE-2020-12079", "id": "pyup.io-70760", "more_info_path": "/vulnerabilities/CVE-2020-12079/70760", "specs": [ "<0.8.9" ], "v": "<0.8.9" }, { "advisory": "Beaker 0.9.4 removes directory escaping characters properly from the session ID when un-signed sessions are used.\r\nhttps://github.com/bbangert/beaker/commit/ad45a77d199c46ddedf5d1aa54780b95d4bd3279", "cve": "PVE-2021-25635", "id": "pyup.io-25635", "more_info_path": "/vulnerabilities/PVE-2021-25635/25635", "specs": [ "<0.9.4" ], "v": "<0.9.4" }, { "advisory": "Beaker before 1.6.4, when using PyCrypto to encrypt sessions, uses AES in ECB cipher mode, which might allow remote attackers to obtain portions of sensitive session data via unspecified vectors.", "cve": "CVE-2012-3458", "id": "pyup.io-25636", "more_info_path": "/vulnerabilities/CVE-2012-3458/25636", "specs": [ "<1.6.4" ], "v": "<1.6.4" }, { "advisory": "Cross-site scripting (XSS) vulnerability in the edit comment dialog in bkr/server/widgets.py in Beaker 20.1 allows remote authenticated users to inject arbitrary web script or HTML via writing a crafted comment on an acked or nacked canceled job.", "cve": "CVE-2015-3162", "id": "pyup.io-70478", "more_info_path": "/vulnerabilities/CVE-2015-3162/70478", "specs": [ "<20.1" ], "v": "<20.1" }, { "advisory": "XML external entity (XXE) vulnerability in bkr/server/jobs.py in Beaker before 20.1 allows remote authenticated users to obtain sensitive information via submitting job XML to the server containing entity references which reference files from the Beaker server's file system.", "cve": "CVE-2015-3160", "id": "pyup.io-70480", "more_info_path": "/vulnerabilities/CVE-2015-3160/70480", "specs": [ "<20.1" ], "v": "<20.1" }, { "advisory": "The search bar code in bkr/server/widgets.py in Beaker before 20.1 does not escape tags in string literals when producing JSON.", "cve": "CVE-2015-3161", "id": "pyup.io-70479", "more_info_path": "/vulnerabilities/CVE-2015-3161/70479", "specs": [ "<20.1" ], "v": "<20.1" }, { "advisory": "The admin pages for power types and key types in Beaker before 20.1 do not have any access controls, which allows remote authenticated users to modify power types and key types via navigating to $BEAKER/powertypes and $BEAKER/keytypes respectively.", "cve": "CVE-2015-3163", "id": "pyup.io-70477", "more_info_path": "/vulnerabilities/CVE-2015-3163/70477", "specs": [ "<20.1" ], "v": "<20.1" }, { "advisory": "The Beaker library through 1.11.0 for Python is affected by deserialization of untrusted data, which could lead to arbitrary code execution.", "cve": "CVE-2013-7489", "id": "pyup.io-38464", "more_info_path": "/vulnerabilities/CVE-2013-7489/38464", "specs": [ "<=1.11.0" ], "v": "<=1.11.0" } ], "beancount-import": [ { "advisory": "Beancount-import version 1.4.0 has upgraded `@babel/traverse` from 7.13.0 to 7.23.3 in the frontend to address the security issue detailed in CVE-2023-45133.", "cve": "CVE-2023-45133", "id": "pyup.io-68055", "more_info_path": "/vulnerabilities/CVE-2023-45133/68055", "specs": [ "<1.4.0" ], "v": "<1.4.0" } ], "beautifulsup4": [ { "advisory": "Beautifulsup4 is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.", "cve": "PVE-2022-51736", "id": "pyup.io-51736", "more_info_path": "/vulnerabilities/PVE-2022-51736/51736", "specs": [ ">0" ], "v": ">0" } ], "beeai-framework": [ { "advisory": "Affected versions of Bee Agent Framework are vulnerable to a race condition. This vulnerability can lead to unpredictable behavior and potential data inconsistency during asynchronous event handling.", "cve": "PVE-2025-75534", "id": "pyup.io-75534", "more_info_path": "/vulnerabilities/PVE-2025-75534/75534", "specs": [ "<0.0.29" ], "v": "<0.0.29" } ], "beets": [ { "advisory": "Beets 1.6.0 sanitize filenames in image IDs in the Aura plugin.\r\nhttps://github.com/beetbox/beets/pull/4160/commits/1fad3d01aea4627af42a9b7190d6869d2b007cc4", "cve": "PVE-2021-42892", "id": "pyup.io-42892", "more_info_path": "/vulnerabilities/PVE-2021-42892/42892", "specs": [ "<1.6.0" ], "v": "<1.6.0" } ], "before-commit": [ { "advisory": "Before-commit 1.10.4 replaces 'yaml.load' with a safe alternative.\r\nhttps://github.com/before-commit/before-commit/commit/6853f4aa4c8d7e411839bacc66876baea443186a", "cve": "PVE-2022-48117", "id": "pyup.io-48117", "more_info_path": "/vulnerabilities/PVE-2022-48117/48117", "specs": [ "<1.10.4" ], "v": "<1.10.4" } ], "beginner": [ { "advisory": "The Beginner package in PyPI v0.0.2 to v0.0.4 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.", "cve": "CVE-2022-33004", "id": "pyup.io-54413", "more_info_path": "/vulnerabilities/CVE-2022-33004/54413", "specs": [ ">=0.0.2,<0.0.5" ], "v": ">=0.0.2,<0.0.5" } ], "behavex": [ { "advisory": "Affected versions of the behavex package are vulnerable to Cross-site Scripting (XSS) due to unescaped rendering of user-controllable `step.text` in the HTML report template. The Jinja2 template `behavex/outputs/jinja/main.jinja2` rendered `step.text` with the `safe` filter (instead of the escaping filter `e`), which bypassed auto-escaping and allowed arbitrary HTML/JavaScript to be injected into the `
` element.",
            "cve": "PVE-2025-79516",
            "id": "pyup.io-79516",
            "more_info_path": "/vulnerabilities/PVE-2025-79516/79516",
            "specs": [
                "<4.5.0"
            ],
            "v": "<4.5.0"
        }
    ],
    "belvo-python": [
        {
            "advisory": "Belvo-python 0.39.1 updates its dependency 'requests' to version '2.31.0' to include a fix for an Information Exposure vulnerability.\r\nhttps://github.com/belvo-finance/belvo-python/pull/177",
            "cve": "PVE-2023-60581",
            "id": "pyup.io-60581",
            "more_info_path": "/vulnerabilities/PVE-2023-60581/60581",
            "specs": [
                "<0.39.1"
            ],
            "v": "<0.39.1"
        }
    ],
    "benchexec": [
        {
            "advisory": "Benchexec 2.2 fixes a security issue. The kernel offers a keyring feature for storage of keys related to features like Kerberos and ecryptfs. Before Linux 5.2, there existed one keyring per user, and BenchExec did not prevent access from the tool inside the container to the kernel keyring of the user who started BenchExec. Now such accesses are forbidden (on all kernel versions) using seccomp (http://man7.org/linux/man-pages/man2/seccomp.2.html) if libseccomp2 (https://github.com/seccomp/libseccomp) is installed, which should be the case on any standard distribution. Note that seccomp filters do have a slight performance impact and could prevent some binaries on exotic architectures from working. In such a case please file a bug report.\r\nhttps://github.com/sosy-lab/benchexec/commit/5f043cd2d2484a75bee48efb924700c0b1ce32b4",
            "cve": "PVE-2021-42546",
            "id": "pyup.io-42546",
            "more_info_path": "/vulnerabilities/PVE-2021-42546/42546",
            "specs": [
                "<2.2"
            ],
            "v": "<2.2"
        },
        {
            "advisory": "Affected versions of BenchExec are vulnerable to a Race Condition (CWE-362). An attacker could manipulate the timing of transient unit creation, leading to inaccurate benchmarking results or denial of service. The vulnerability exists in the asynchronous StartTransientUnit method within cgroupsv2.py. Exploiting this requires precise control over systemd interactions. Mitigation involves upgrading BenchExec to the version which implements synchronous handling to eliminate the race condition.",
            "cve": "PVE-2024-74038",
            "id": "pyup.io-74038",
            "more_info_path": "/vulnerabilities/PVE-2024-74038/74038",
            "specs": [
                "<3.26"
            ],
            "v": "<3.26"
        },
        {
            "advisory": "Benchexec 2.2 fixes a security issue. Since BenchExec 2.1, the setup of the container for the tool-info module (which was added in BenchExec 1.20) could silently fail, for example if user namespaces are disabled on the system. In this case the tool-info module would be executed outside of the container. Run execution was not affected.\r\nhttps://github.com/sosy-lab/benchexec/commit/dea58cac6e066d89e3ab3e374c6472d575493d07",
            "cve": "PVE-2021-37510",
            "id": "pyup.io-37510",
            "more_info_path": "/vulnerabilities/PVE-2021-37510/37510",
            "specs": [
                "==2.1"
            ],
            "v": "==2.1"
        }
    ],
    "bento-lib": [
        {
            "advisory": "Bento-lib 3.0.1 includes security fix to prevent data leak in error messages from data structure queries by default and adds 'secure_errors' param for data structure querying methods.\r\nhttps://github.com/bento-platform/bento_lib/commit/991ee4fd406e3397435d1c8c02f1d0c48b9ec594\r\nhttps://github.com/bento-platform/bento_lib/commit/046a023abe8de0c3e13963a0c236df4f34ade244",
            "cve": "PVE-2021-41035",
            "id": "pyup.io-41035",
            "more_info_path": "/vulnerabilities/PVE-2021-41035/41035",
            "specs": [
                "<3.0.1"
            ],
            "v": "<3.0.1"
        },
        {
            "advisory": "Bento-lib 6.0.1 updates its dependency 'redis' to v4.5.4 to include security fixes.",
            "cve": "CVE-2023-28859",
            "id": "pyup.io-54854",
            "more_info_path": "/vulnerabilities/CVE-2023-28859/54854",
            "specs": [
                "<6.0.1"
            ],
            "v": "<6.0.1"
        },
        {
            "advisory": "Bento-lib 6.0.1 updates its dependency 'redis' to v4.5.4 to include security fixes.",
            "cve": "CVE-2023-28858",
            "id": "pyup.io-54855",
            "more_info_path": "/vulnerabilities/CVE-2023-28858/54855",
            "specs": [
                "<6.0.1"
            ],
            "v": "<6.0.1"
        }
    ],
    "bentoml": [
        {
            "advisory": "An insecure deserialization vulnerability exists in the BentoML framework, allowing remote code execution (RCE) by sending a specially crafted POST request. By exploiting this vulnerability, attackers can execute arbitrary commands on the server hosting the BentoML application. The vulnerability is triggered when a serialized object, crafted to execute OS commands upon deserialization, is sent to any valid BentoML endpoint. This issue poses a significant security risk, enabling attackers to compromise the server and potentially gain unauthorized access or control.",
            "cve": "CVE-2024-2912",
            "id": "pyup.io-71907",
            "more_info_path": "/vulnerabilities/CVE-2024-2912/71907",
            "specs": [
                "<1.2.5"
            ],
            "v": "<1.2.5"
        },
        {
            "advisory": "An open redirect vulnerability in bentoml/bentoml v1.3.9 allows a remote unauthenticated attacker to redirect users to arbitrary websites via a specially crafted URL. This can be exploited for phishing attacks, malware distribution, and credential theft.",
            "cve": "PVE-2025-76261",
            "id": "pyup.io-76261",
            "more_info_path": "/vulnerabilities/PVE-2025-76261/76261",
            "specs": [
                "<1.3.9"
            ],
            "v": "<1.3.9"
        },
        {
            "advisory": "Affected versions of the BentoML package are vulnerable to arbitrary file read via path traversal due to insecure user-controlled path resolution. The resolve_user_filepath() helper expanded and resolved user-supplied paths without enforcing a safe base directory (and did not block absolute, hidden, or sensitive system paths), and this was fixed by adding stricter \u201csecure\u201d validation checks.",
            "cve": "PVE-2026-85090",
            "id": "pyup.io-85090",
            "more_info_path": "/vulnerabilities/PVE-2026-85090/85090",
            "specs": [
                "<1.4.34"
            ],
            "v": "<1.4.34"
        },
        {
            "advisory": "Affected versions of the bentoml package are vulnerable to Path Traversal due to missing path containment validation when resolving user-supplied file paths in bentofile.yaml. The issue occurs when src/bentoml/_internal/utils/filesystem.py:resolve_user_filepath() and src/bentoml/_internal/bento/bento.py copy files referenced by description (file:...), docker.setup_script, docker.dockerfile_template, and conda.environment_yml after expanding and realpath-resolving attacker-controlled paths without enforcing that the resolved target remains inside the build context directory.",
            "cve": "CVE-2026-24123",
            "id": "pyup.io-85153",
            "more_info_path": "/vulnerabilities/CVE-2026-24123/85153",
            "specs": [
                "<1.4.34"
            ],
            "v": "<1.4.34"
        },
        {
            "advisory": "BentoML version v1.3.4post1 is vulnerable to a Denial of Service (DoS) attack. The vulnerability can be exploited by appending characters, such as dashes (-), to the end of a multipart boundary in an HTTP request. This causes the server to continuously process each character, leading to excessive resource consumption and rendering the service unavailable. The issue is unauthenticated and does not require any user interaction, impacting all users of the service.",
            "cve": "CVE-2024-9056",
            "id": "pyup.io-76193",
            "more_info_path": "/vulnerabilities/CVE-2024-9056/76193",
            "specs": [
                "<=1.4.5"
            ],
            "v": "<=1.4.5"
        },
        {
            "advisory": "A deserialization vulnerability exists in BentoML's runner server in bentoml/bentoml versions <=1.3.4.post1. By setting specific parameters, an attacker can execute unauthorized arbitrary code on the server, causing severe harm. The vulnerability is triggered when the args-number parameter is greater than 1, leading to automatic deserialization and arbitrary code execution.",
            "cve": "CVE-2024-9070",
            "id": "pyup.io-76191",
            "more_info_path": "/vulnerabilities/CVE-2024-9070/76191",
            "specs": [
                "<=1.4.5"
            ],
            "v": "<=1.4.5"
        },
        {
            "advisory": "A Remote Code Execution (RCE) vulnerability caused by insecure deserialization has been identified in the latest version (v1.4.2) of BentoML. It allows any unauthenticated user to execute arbitrary code on the server. It exists an unsafe code segment in serde.py. This vulnerability is fixed in 1.4.3.",
            "cve": "CVE-2025-27520",
            "id": "pyup.io-76518",
            "more_info_path": "/vulnerabilities/CVE-2025-27520/76518",
            "specs": [
                ">1.3.3,<1.4.3"
            ],
            "v": ">1.3.3,<1.4.3"
        },
        {
            "advisory": "Affected versions of the BentoML package are vulnerable to Deserialization of Untrusted Data due to unsafe pickle deserialization in the runner server request handling. The _deserialize_single_param function in src/bentoml/_internal/server/runner_app.py processes requests with specific headers (Payload-Container set to NdarrayContainer or PandasDataFrameContainer and Payload-Meta set to {\"format\": \"default\"}), leading to pickle.loads() being called on untrusted request body data without validation.",
            "cve": "CVE-2025-32375",
            "id": "pyup.io-78836",
            "more_info_path": "/vulnerabilities/CVE-2025-32375/78836",
            "specs": [
                ">=1.0.0a1,<1.4.8"
            ],
            "v": ">=1.0.0a1,<1.4.8"
        },
        {
            "advisory": "BentoML is a Python library for building online serving systems optimized for AI apps and model inference. In versions 1.4.0 until 1.4.19, the file upload processing system contains an SSRF vulnerability that allows unauthenticated remote attackers to force the server to make arbitrary HTTP requests. The vulnerability stems from the multipart form data and JSON request handlers, which automatically download files from user-provided URLs without validating whether those URLs point to internal network addresses, cloud metadata endpoints, or other restricted resources. The documentation explicitly promotes this URL-based file upload feature, making it an intended design that exposes all deployed services to SSRF attacks by default. Version 1.4.19 contains a patch for the issue.",
            "cve": "CVE-2025-54381",
            "id": "pyup.io-78599",
            "more_info_path": "/vulnerabilities/CVE-2025-54381/78599",
            "specs": [
                ">=1.4.0a1,<1.4.19"
            ],
            "v": ">=1.4.0a1,<1.4.19"
        }
    ],
    "bepasty": [
        {
            "advisory": "Bepasty 0.3.0 prevents the disclosure of locked item's metadata.\r\nhttps://github.com/bepasty/bepasty-server/commit/95e49be1b4ecbf800bd81805f37d4e42699f3d45",
            "cve": "PVE-2022-48339",
            "id": "pyup.io-48339",
            "more_info_path": "/vulnerabilities/PVE-2022-48339/48339",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Bepasty 0.3.0 forces the content-type to be text/plain and also turn the browser's sniffer off when showing potentially dangerous text/* types.\r\nhttps://github.com/bepasty/bepasty-server/commit/068fc4e1906bda3cd94705ba2907e52864f10ee3",
            "cve": "PVE-2021-25637",
            "id": "pyup.io-25637",
            "more_info_path": "/vulnerabilities/PVE-2021-25637/25637",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Bepasty 0.6.0 invalidates old client-side cookies if PERMISSIONS in config are changed. This is a security fix.\r\nhttps://github.com/bepasty/bepasty-server/commit/4d5020d9839db510a4197041dd644efa5778b40e",
            "cve": "PVE-2021-39120",
            "id": "pyup.io-39120",
            "more_info_path": "/vulnerabilities/PVE-2021-39120/39120",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "berglas": [
        {
            "advisory": "Berglas 0.2.0 no longer trusts the environment variables.",
            "cve": "PVE-2021-37340",
            "id": "pyup.io-37340",
            "more_info_path": "/vulnerabilities/PVE-2021-37340/37340",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "betty": [
        {
            "advisory": "Betty 0.3.0a1 addresses a race condition that can occur during the CPU-intensive site generation process. This update introduces safeguards to prevent the copying or serialization of App instances, which could potentially lead to data inconsistencies or other unexpected behavior.\r\nhttps://github.com/bartfeenstra/betty/pull/798/commits/660d4ecdd97f2e5c00cb18945f38cf1c871bdc1e",
            "cve": "PVE-2023-63062",
            "id": "pyup.io-63062",
            "more_info_path": "/vulnerabilities/PVE-2023-63062/63062",
            "specs": [
                "<0.3.0a1"
            ],
            "v": "<0.3.0a1"
        },
        {
            "advisory": "Betty 0.3.0a1 addresses a race condition in the locale API. It aims to ensure thread safety by avoiding shared state and using context managers to handle resources.\r\nhttps://github.com/bartfeenstra/betty/pull/958/commits/05434a10c0c886d1afad0b61b119de13b0d2959b",
            "cve": "PVE-2023-63093",
            "id": "pyup.io-63093",
            "more_info_path": "/vulnerabilities/PVE-2023-63093/63093",
            "specs": [
                "<0.3.0a1"
            ],
            "v": "<0.3.0a1"
        },
        {
            "advisory": "Affected versions of the Betty cache package are vulnerable to a Race Condition (CWE-362). This vulnerability may result in data corruption or inconsistent state when multiple coroutines access shared cache items concurrently. The issue arises in the _CacheItemLock class's release method, which no longer acquires a lock before modifying shared data. Attackers could exploit this by triggering concurrent cache operations, leading to unpredictable behavior. To mitigate this issue, reintroduce the lock in the release method to ensure proper synchronization of shared resources.",
            "cve": "PVE-2024-73610",
            "id": "pyup.io-73610",
            "more_info_path": "/vulnerabilities/PVE-2024-73610/73610",
            "specs": [
                "<0.4.0a12"
            ],
            "v": "<0.4.0a12"
        }
    ],
    "bgcflow-wrapper": [
        {
            "advisory": "Bgcflow-wrapper 0.2.5 updates its dependency on the Tox library from version \"^3.24.5\" to version \"^4.6.4\" as a part of a security update.\r\nhttps://github.com/NBChub/bgcflow_wrapper/pull/21/commits/319c772de5b1a572605a641acf6ecd8cced2deca",
            "cve": "PVE-2024-64545",
            "id": "pyup.io-64545",
            "more_info_path": "/vulnerabilities/PVE-2024-64545/64545",
            "specs": [
                "<0.2.5"
            ],
            "v": "<0.2.5"
        },
        {
            "advisory": "Bgcflow-wrapper 0.2.6 updates its dependency 'cryptography' to v41.0.3 to include a security fix.",
            "cve": "CVE-2023-3446",
            "id": "pyup.io-62425",
            "more_info_path": "/vulnerabilities/CVE-2023-3446/62425",
            "specs": [
                "<0.2.6"
            ],
            "v": "<0.2.6"
        },
        {
            "advisory": "Bgcflow-wrapper 0.3.3 updates its Snakemake dependency from the previous version range \"^7.18.2\" to a specific newer version, \"7.31.1,\" as part of a security update.\r\nhttps://github.com/NBChub/bgcflow_wrapper/pull/35/commits/30d7f96c73a0307779b9503160da50a2d9924e91",
            "cve": "PVE-2024-64544",
            "id": "pyup.io-64544",
            "more_info_path": "/vulnerabilities/PVE-2024-64544/64544",
            "specs": [
                "<0.3.3"
            ],
            "v": "<0.3.3"
        },
        {
            "advisory": "Bgcflow-wrapper 0.3.5 adjusts its dependencies by locking the version of Pulp to 2.7.0. This change was implemented to resolve an issue related to its dependency on Snakemake.\r\nhttps://github.com/snakemake/snakemake/issues/2606",
            "cve": "PVE-2024-64543",
            "id": "pyup.io-64543",
            "more_info_path": "/vulnerabilities/PVE-2024-64543/64543",
            "specs": [
                "<0.3.5"
            ],
            "v": "<0.3.5"
        }
    ],
    "bids-validator": [
        {
            "advisory": "Bids-validator 0.24.0 includes a fix for a directory traversal vulnerability.\r\nhttps://github.com/bids-standard/bids-validator/pull/368",
            "cve": "PVE-2023-59251",
            "id": "pyup.io-59251",
            "more_info_path": "/vulnerabilities/PVE-2023-59251/59251",
            "specs": [
                "<0.24.0"
            ],
            "v": "<0.24.0"
        }
    ],
    "bigchaindb": [
        {
            "advisory": "Bigchaindb 2.2.2 updates its dependency 'gunicorn' to v20.0.4 to include a security fix.",
            "cve": "CVE-2018-1000164",
            "id": "pyup.io-45782",
            "more_info_path": "/vulnerabilities/CVE-2018-1000164/45782",
            "specs": [
                "<2.2.2"
            ],
            "v": "<2.2.2"
        },
        {
            "advisory": "Bigchaindb 2.2.2 updates its dependency 'pyyaml' to v5.3.1 to include a security fix.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-45783",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/45783",
            "specs": [
                "<2.2.2"
            ],
            "v": "<2.2.2"
        }
    ],
    "bigchaindb-driver": [
        {
            "advisory": "Bigchaindb-driver 0.5.2 includes a fix for CVE-2018-10903: A flaw was found in python-cryptography versions between >=1.9.0 and <2.3. The finalize_with_tag API did not enforce a minimum tag length. If a user did not validate the input length prior to passing it to finalize_with_tag an attacker could craft an invalid payload with a shortened tag (e.g. 1 byte) such that they would have a 1 in 256 chance of passing the MAC check. GCM tag forgeries can cause key leakage.",
            "cve": "CVE-2018-10903",
            "id": "pyup.io-36427",
            "more_info_path": "/vulnerabilities/CVE-2018-10903/36427",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        }
    ],
    "bigdl": [
        {
            "advisory": "Bigdl 0.5.0 includes a fix for a Race Condition vulnerability in Spark 1.6.\r\nhttps://github.com/intel-analytics/BigDL/pull/2363",
            "cve": "PVE-2023-59598",
            "id": "pyup.io-59598",
            "more_info_path": "/vulnerabilities/PVE-2023-59598/59598",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        },
        {
            "advisory": "Bigdl 0.8.0 fixes the scala compiler security issue in 2.10 & 2.11",
            "cve": "PVE-2021-37576",
            "id": "pyup.io-37576",
            "more_info_path": "/vulnerabilities/PVE-2021-37576/37576",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        },
        {
            "advisory": "Bigdl 2.0.0 updates its Maven dependency 'http.version' to v10.1.15 to include security fixes.",
            "cve": "CVE-2021-42697",
            "id": "pyup.io-45841",
            "more_info_path": "/vulnerabilities/CVE-2021-42697/45841",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Bigdl 2.1.0 updates its Maven dependency 'protobuf-java' to v3.19.2 to include a security fix.",
            "cve": "CVE-2021-22569",
            "id": "pyup.io-51239",
            "more_info_path": "/vulnerabilities/CVE-2021-22569/51239",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Bigdl 2.1.0 updates its Maven dependency 'akka.http' to v10.1.15 to include a security fix.",
            "cve": "CVE-2021-23339",
            "id": "pyup.io-51328",
            "more_info_path": "/vulnerabilities/CVE-2021-23339/51328",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Bigdl 2.3.0 includes a fix for a SQL injection vulnerability in python/benchmark/run.py.\r\nhttps://github.com/intel-analytics/BigDL/pull/8014",
            "cve": "PVE-2023-55136",
            "id": "pyup.io-55136",
            "more_info_path": "/vulnerabilities/PVE-2023-55136/55136",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Bigdl 2.3.0 includes a security fix in its 'dlib' library: Unsafe Reflection in ModelBroadcast.scala Topology.scala.\r\nhttps://github.com/intel-analytics/BigDL/pull/7731",
            "cve": "PVE-2023-55134",
            "id": "pyup.io-55134",
            "more_info_path": "/vulnerabilities/PVE-2023-55134/55134",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Bigdl 2.3.0 includes a security fix in its 'dlib' library: Reflected XSS All Clients in TorchFile.scala.\r\nhttps://github.com/intel-analytics/BigDL/pull/7731",
            "cve": "PVE-2023-55131",
            "id": "pyup.io-55131",
            "more_info_path": "/vulnerabilities/PVE-2023-55131/55131",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Bigdl 2.3.0 includes a security fix in its 'dlib' library: Deserialization of Untrusted Data in File.scala.\r\nhttps://github.com/intel-analytics/BigDL/pull/7731",
            "cve": "PVE-2023-55135",
            "id": "pyup.io-55135",
            "more_info_path": "/vulnerabilities/PVE-2023-55135/55135",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Bigdl 2.3.0 replaces part of pickle to json to avoid a security issue.\r\nhttps://github.com/intel-analytics/BigDL/pull/8009",
            "cve": "PVE-2023-55137",
            "id": "pyup.io-55137",
            "more_info_path": "/vulnerabilities/PVE-2023-55137/55137",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Bigdl 2.3.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.\r\nhttps://github.com/intel-analytics/BigDL/pull/7717",
            "cve": "CVE-2023-0401",
            "id": "pyup.io-55138",
            "more_info_path": "/vulnerabilities/CVE-2023-0401/55138",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Bigdl 2.3.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.\r\nhttps://github.com/intel-analytics/BigDL/pull/7717",
            "cve": "CVE-2023-0286",
            "id": "pyup.io-55139",
            "more_info_path": "/vulnerabilities/CVE-2023-0286/55139",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Bigdl 2.4.0 includes a fix for a command injection vulnerability.\r\nhttps://github.com/intel-analytics/BigDL/pull/8478",
            "cve": "PVE-2023-62298",
            "id": "pyup.io-62298",
            "more_info_path": "/vulnerabilities/PVE-2023-62298/62298",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Bigdl 2.4.0 includes a fix for a Weak Encryption at Rest vulnerability.\r\nhttps://github.com/intel-analytics/BigDL/pull/8414",
            "cve": "PVE-2023-62334",
            "id": "pyup.io-62334",
            "more_info_path": "/vulnerabilities/PVE-2023-62334/62334",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Bigdl 2.4.0 updates its C dependency 'libturbojpeg' to v3.0.0 to include a security fix.\r\nhttps://github.com/intel-analytics/BigDL/pull/8413/commits/34349d2dd7408b75cdb30c365896132a51461dd8",
            "cve": "CVE-2023-2804",
            "id": "pyup.io-62335",
            "more_info_path": "/vulnerabilities/CVE-2023-2804/62335",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        }
    ],
    "bigflow": [
        {
            "advisory": "Allegro Tech BigFlow <1.6 is vulnerable to Missing SSL Certificate Validation.",
            "cve": "CVE-2023-25392",
            "id": "pyup.io-62893",
            "more_info_path": "/vulnerabilities/CVE-2023-25392/62893",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        },
        {
            "advisory": "Bigflow 1.6.0 enables vault endpoint TLS certificate verification by default to avoid MITM attacks.",
            "cve": "PVE-2023-53443",
            "id": "pyup.io-53443",
            "more_info_path": "/vulnerabilities/PVE-2023-53443/53443",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        }
    ],
    "bikeshed": [
        {
            "advisory": "Bikeshed version 3.0.0 includes a fix for CVE-2021-23423:\r\nWhen an untrusted source file containing include, include-code or include-raw block is processed, the contents of arbitrary files could be disclosed in the HTML output.\r\nhttps://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2dd",
            "cve": "CVE-2021-23423",
            "id": "pyup.io-41180",
            "more_info_path": "/vulnerabilities/CVE-2021-23423/41180",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Bikeshed version 3.0.0 includes a fix for CVE-2021-23422:\r\nWhen an untrusted source file containing Inline Tag Command metadata is processed or when an arbitrary OS command is executed, the command output would be included in the HTML output.\r\nhttps://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2dd",
            "cve": "CVE-2021-23422",
            "id": "pyup.io-41179",
            "more_info_path": "/vulnerabilities/CVE-2021-23422/41179",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        }
    ],
    "bin-collect": [
        {
            "advisory": "The bin-collection package in PyPI before v0.1 included a code execution backdoor inserted by a third party.",
            "cve": "CVE-2022-34501",
            "id": "pyup.io-70770",
            "more_info_path": "/vulnerabilities/CVE-2022-34501/70770",
            "specs": [
                "<0.1"
            ],
            "v": "<0.1"
        },
        {
            "advisory": "The bin-collect package in PyPI before v0.1 included a code execution backdoor inserted by a third party.",
            "cve": "CVE-2022-34500",
            "id": "pyup.io-70768",
            "more_info_path": "/vulnerabilities/CVE-2022-34500/70768",
            "specs": [
                "<0.1"
            ],
            "v": "<0.1"
        }
    ],
    "bin-collection": [
        {
            "advisory": "The bin-collect package in PyPI before v0.1 included a code execution backdoor inserted by a third party.",
            "cve": "CVE-2022-34500",
            "id": "pyup.io-70769",
            "more_info_path": "/vulnerabilities/CVE-2022-34500/70769",
            "specs": [
                "<0.1"
            ],
            "v": "<0.1"
        },
        {
            "advisory": "The bin-collection package in PyPI before v0.1 included a code execution backdoor inserted by a third party.",
            "cve": "CVE-2022-34501",
            "id": "pyup.io-70771",
            "more_info_path": "/vulnerabilities/CVE-2022-34501/70771",
            "specs": [
                "<0.1"
            ],
            "v": "<0.1"
        }
    ],
    "bincrafters-envy": [
        {
            "advisory": "Bincrafters-envy 0.1.3 updates its dependency 'requests' to v2.20.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36732",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36732",
            "specs": [
                "<0.1.3"
            ],
            "v": "<0.1.3"
        }
    ],
    "binderhub": [
        {
            "advisory": "### Impact\n\nA remote code execution vulnerability has been identified in BinderHub, where providing BinderHub with maliciously crafted input could execute code in the BinderHub context, with the potential to egress credentials of the BinderHub deployment, including JupyterHub API tokens, kubernetes service accounts, and docker registry credentials. This may provide the ability to manipulate images and other user created pods in the deployment, with the potential to escalate to the host depending on the underlying kubernetes configuration.\n\n### Patches\n\nPatch below, or [on GitHub](https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182.patch)\n\n```diff\nFrom 9f4043d9dddc1174920e687773f27b7933f48ab6 Mon Sep 17 00:00:00 2001\nFrom: Riccardo Castellotti \nDate: Thu, 19 Aug 2021 15:49:43 +0200\nSubject: [PATCH] Explicitly separate git-ls-remote options from positional\n arguments\n\n---\n binderhub/repoproviders.py | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/binderhub/repoproviders.py b/binderhub/repoproviders.py\nindex f33347b..5d4b87c 100755\n--- a/binderhub/repoproviders.py\n+++ b/binderhub/repoproviders.py\n@@ -484,7 +484,7 @@ class GitRepoProvider(RepoProvider):\n             self.sha1_validate(self.unresolved_ref)\n         except ValueError:\n             # The ref is a head/tag and we resolve it using `git ls-remote`\n-            command = [\"git\", \"ls-remote\", self.repo, self.unresolved_ref]\n+            command = [\"git\", \"ls-remote\", \"--\", self.repo, self.unresolved_ref]\n             result = subprocess.run(command, universal_newlines=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE)\n             if result.returncode:\n                 raise RuntimeError(\"Unable to run git ls-remote to get the `resolved_ref`: {}\".format(result.stderr))\n-- \n2.25.1\n\n```\n\n### Workarounds\n\nDisable the git repo provider by specifying the `BinderHub.repo_providers` config, e.g.:\n\n```python\nfrom binderhub.repoproviders import (GitHubRepoProvider,\n                            GitLabRepoProvider, GistRepoProvider,\n                            ZenodoProvider, FigshareProvider, HydroshareProvider,\n                            DataverseProvider)\n\nc.BinderHub.repo_providers =  {\n            'gh': GitHubRepoProvider,\n            'gist': GistRepoProvider,\n            'gl': GitLabRepoProvider,\n            'zenodo': ZenodoProvider,\n            'figshare': FigshareProvider,\n            'hydroshare': HydroshareProvider,\n            'dataverse': DataverseProvider,\n        }\n```\n\n### References\n\nCredit: Jose Carlos Luna Duran (CERN) and Riccardo Castellotti (CERN).\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@ipython.org](mailto:security@ipython.org)\n\n\nAffected functions:\nbinderhub.repoproviders.GitRepoProvider.get_resolved_ref",
            "cve": "CVE-2021-39159",
            "id": "pyup.io-54316",
            "more_info_path": "/vulnerabilities/CVE-2021-39159/54316",
            "specs": [
                ">=0,<0.2.0"
            ],
            "v": ">=0,<0.2.0"
        }
    ],
    "binpacking": [
        {
            "advisory": "Binpacking 1.5.2 removes 'pytest-runner' dependency as it poses a security risk.\r\nhttps://github.com/benmaier/binpacking/pull/27",
            "cve": "PVE-2021-43313",
            "id": "pyup.io-42945",
            "more_info_path": "/vulnerabilities/PVE-2021-43313/42945",
            "specs": [
                "<1.5.2"
            ],
            "v": "<1.5.2"
        }
    ],
    "binwalk": [
        {
            "advisory": "A vulnerability, which was classified as problematic, was found in ReFirm Labs binwalk up to 2.3.2. Affected is an unknown function of the file src/binwalk/modules/extractor.py of the component Archive Extraction Handler. The manipulation leads to symlink following. It is possible to launch the attack remotely.",
            "cve": "CVE-2021-4287",
            "id": "pyup.io-54630",
            "more_info_path": "/vulnerabilities/CVE-2021-4287/54630",
            "specs": [
                ">=0,<2.3.3"
            ],
            "v": ">=0,<2.3.3"
        },
        {
            "advisory": "Affected versions of binwalk from 2.1.2b through 2.3.3 included are vulnerable to path traversal and remote code execution. By crafting a malicious PFS filesystem file, an attacker can trigger the PFS extractor when binwalk is run in extraction mode (-e), causing files to be extracted to arbitrary locations. The vulnerability is associated with src/binwalk/plugins/unpfs.py.",
            "cve": "CVE-2022-4510",
            "id": "pyup.io-54641",
            "more_info_path": "/vulnerabilities/CVE-2022-4510/54641",
            "specs": [
                ">=2.1.2b,<=2.3.3"
            ],
            "v": ">=2.1.2b,<=2.3.3"
        }
    ],
    "biolink-model": [
        {
            "advisory": "Biolink-model 2.2.12 updates its dependency 'lxml' to v4.7.1 to include a security fix.",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-43418",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/43418",
            "specs": [
                "<2.2.12"
            ],
            "v": "<2.2.12"
        }
    ],
    "biopython": [
        {
            "advisory": "Affected versions of the biopython package are vulnerable to XML External Entity (XXE) Injection due to unrestricted resolution of external entities during Bio.Entrez XML parsing. The Bio.Entrez.DataHandler implementation (used by Bio.Entrez.read and Bio.Entrez.parse) processes attacker-influenced XML and will retrieve external DTD/XSD resources via urllib.request.urlopen (for example, in Bio/Entrez/Parser.py when local cache lookups fail), allowing untrusted DOCTYPE declarations to drive external entity resolution.",
            "cve": "CVE-2025-68463",
            "id": "pyup.io-83149",
            "more_info_path": "/vulnerabilities/CVE-2025-68463/83149",
            "specs": [
                "<=1.86"
            ],
            "v": "<=1.86"
        }
    ],
    "biothings": [
        {
            "advisory": "Biothings 0.12.3 includes a fix for a shell injection vulnerability.\r\nhttps://github.com/biothings/biothings.api/pull/301",
            "cve": "PVE-2023-62122",
            "id": "pyup.io-62122",
            "more_info_path": "/vulnerabilities/PVE-2023-62122/62122",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        }
    ],
    "birdhousebuilder-recipe-nginx": [
        {
            "advisory": "Birdhousebuilder-recipe-nginx 0.1.5 disables SSLv3 protocol to avoid known vulnerabilities.",
            "cve": "CVE-2014-3566",
            "id": "pyup.io-36135",
            "more_info_path": "/vulnerabilities/CVE-2014-3566/36135",
            "specs": [
                "<0.1.5"
            ],
            "v": "<0.1.5"
        }
    ],
    "bise-theme": [
        {
            "advisory": "bise.theme 2.4 fixes a potential XSS issue with catalogue search.",
            "cve": "PVE-2021-25639",
            "id": "pyup.io-25639",
            "more_info_path": "/vulnerabilities/PVE-2021-25639/25639",
            "specs": [
                "<2.4"
            ],
            "v": "<2.4"
        }
    ],
    "bitbot": [
        {
            "advisory": "For security reasons, REST API only listens on localhost in Bitbot 1.12.0.",
            "cve": "PVE-2021-37551",
            "id": "pyup.io-37551",
            "more_info_path": "/vulnerabilities/PVE-2021-37551/37551",
            "specs": [
                "<1.12.0"
            ],
            "v": "<1.12.0"
        }
    ],
    "bitlyshortener": [
        {
            "advisory": "A recent update has significantly reduced the quota for free token-generated links in a specific service, dropping from 1000 to 50 links per month. This reduction severely limits the utility of the service for users who rely on the free token. Consequently, maintenance for the associated package is being discontinued, even though the package will still function with the new restricted quota.",
            "cve": "PVE-2024-69617",
            "id": "pyup.io-69617",
            "more_info_path": "/vulnerabilities/PVE-2024-69617/69617",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Due to a sudden upstream breaking change by Bitly, versions of 'bitlyshortener' <0.5.0 can generate an invalid short URL when a vanity domain exists.",
            "cve": "PVE-2023-55202",
            "id": "pyup.io-55202",
            "more_info_path": "/vulnerabilities/PVE-2023-55202/55202",
            "specs": [
                ">=0,<0.5.0"
            ],
            "v": ">=0,<0.5.0"
        },
        {
            "advisory": "Due to a sudden upstream breaking change by Bitly, versions of 'bitlyshortener' <0.6.0 generate invalid short URLs. All users are affected and must update immediately. A workaround is to replace \"https://j.mp/\" in each generated short URL with \"https://bit.ly/\".\r\nhttps://github.com/impredicative/bitlyshortener/commit/b307d70bedf745305fa0dd3c5c600d8cb88d09b5",
            "cve": "PVE-2023-55204",
            "id": "pyup.io-55204",
            "more_info_path": "/vulnerabilities/PVE-2023-55204/55204",
            "specs": [
                ">=0,<0.6.0"
            ],
            "v": ">=0,<0.6.0"
        }
    ],
    "bittensor": [
        {
            "advisory": "Bittensor 3.4.3 catches precision errors in synapse forward responses that may cause probability sums to exceed permissible boundaries.\r\nhttps://github.com/opentensor/bittensor/pull/991",
            "cve": "PVE-2022-52000",
            "id": "pyup.io-52000",
            "more_info_path": "/vulnerabilities/PVE-2022-52000/52000",
            "specs": [
                "<3.4.3"
            ],
            "v": "<3.4.3"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Denial of Service vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2023-0401",
            "id": "pyup.io-59608",
            "more_info_path": "/vulnerabilities/CVE-2023-0401/59608",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Denial of Service vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2023-0216",
            "id": "pyup.io-59613",
            "more_info_path": "/vulnerabilities/CVE-2023-0216/59613",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Denial of Service vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2022-3996",
            "id": "pyup.io-59617",
            "more_info_path": "/vulnerabilities/CVE-2022-3996/59617",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix an Expected Behavior Violation vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2023-23931",
            "id": "pyup.io-59616",
            "more_info_path": "/vulnerabilities/CVE-2023-23931/59616",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Timing Attack vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2022-4304",
            "id": "pyup.io-59612",
            "more_info_path": "/vulnerabilities/CVE-2022-4304/59612",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Denial of Service vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2023-0217",
            "id": "pyup.io-59609",
            "more_info_path": "/vulnerabilities/CVE-2023-0217/59609",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Denial of Service vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2022-4203",
            "id": "pyup.io-59614",
            "more_info_path": "/vulnerabilities/CVE-2022-4203/59614",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Denial of Service vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2022-4450",
            "id": "pyup.io-59615",
            "more_info_path": "/vulnerabilities/CVE-2022-4450/59615",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Type Confusion vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2023-0286",
            "id": "pyup.io-59611",
            "more_info_path": "/vulnerabilities/CVE-2023-0286/59611",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Use After Free vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2023-0215",
            "id": "pyup.io-59610",
            "more_info_path": "/vulnerabilities/CVE-2023-0215/59610",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor 5.3.1 updates its dependency 'cryptography' to version '41.0.0' to fix a Denial of Service vulnerability.\r\nhttps://github.com/opentensor/bittensor/commit/91d13b0fa711621cbf823708d4368b1b387e42c4",
            "cve": "CVE-2023-2650",
            "id": "pyup.io-59533",
            "more_info_path": "/vulnerabilities/CVE-2023-2650/59533",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Bittensor version 6.12.0 updates its `certifi` package to versions 2023.7.22 and 2024.2.2 to address the security issues identified in CVE-2023-37920.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-70794",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/70794",
            "specs": [
                "<6.12.0"
            ],
            "v": "<6.12.0"
        },
        {
            "advisory": "Bittensor version 6.12.0 updates its cryptography library to versions 42.0.0 and 42.0.5 to address the security vulnerabilities outlined in CVE-2024-26130.",
            "cve": "CVE-2023-5363",
            "id": "pyup.io-70793",
            "more_info_path": "/vulnerabilities/CVE-2023-5363/70793",
            "specs": [
                "<6.12.0"
            ],
            "v": "<6.12.0"
        },
        {
            "advisory": "Bittensor version 6.12.0 updates FastAPI to versions 0.99.1 and 0.110.1 to address security issues highlighted in CVE-2024-24762.",
            "cve": "CVE-2024-24762",
            "id": "pyup.io-70789",
            "more_info_path": "/vulnerabilities/CVE-2024-24762/70789",
            "specs": [
                "<6.12.0"
            ],
            "v": "<6.12.0"
        },
        {
            "advisory": "Bittensor 6.4.4 upgrades its aiohttp dependency from version 3.8.5 to 3.9.0 in response to the CVE-2023-49081.\r\nhttps://github.com/opentensor/bittensor/pull/1597/commits/dc7ab6307e465a2dc110677319c58580067d13fc",
            "cve": "CVE-2023-49081",
            "id": "pyup.io-63597",
            "more_info_path": "/vulnerabilities/CVE-2023-49081/63597",
            "specs": [
                "<6.4.4"
            ],
            "v": "<6.4.4"
        },
        {
            "advisory": "Bittensor 6.4.4 upgrades its aiohttp dependency from version 3.8.5 to 3.9.0 in response to the CVE-2023-49082.\r\nhttps://github.com/opentensor/bittensor/pull/1597/commits/dc7ab6307e465a2dc110677319c58580067d13fc",
            "cve": "CVE-2023-49082",
            "id": "pyup.io-63903",
            "more_info_path": "/vulnerabilities/CVE-2023-49082/63903",
            "specs": [
                "<6.4.4"
            ],
            "v": "<6.4.4"
        }
    ],
    "biweeklybudget": [
        {
            "advisory": "Biweeklybudget 1.1.0 updates its dependency 'Flask' to v1.0.2 to include a security fix.",
            "cve": "CVE-2018-1000656",
            "id": "pyup.io-52663",
            "more_info_path": "/vulnerabilities/CVE-2018-1000656/52663",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Biweeklybudget 1.1.0 updates its dependency 'jinja2' to v2.10.3 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-52665",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/52665",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Biweeklybudget 1.1.0 updates its dependency 'SQLAlchemy' to v1.3.13 to include a security fix.",
            "cve": "CVE-2019-7548",
            "id": "pyup.io-52592",
            "more_info_path": "/vulnerabilities/CVE-2019-7548/52592",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Biweeklybudget 1.1.0 updates its dependency 'cryptography' to v2.3.1 to include a security fix.",
            "cve": "CVE-2018-10903",
            "id": "pyup.io-52664",
            "more_info_path": "/vulnerabilities/CVE-2018-10903/52664",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "bjoern": [
        {
            "advisory": "bjoern before 1.4.2 uses a insecure Django release which is vulnerable to CVE-2015-0219, see https://www.djangoproject.com/weblog/2015/jan/13/security/.",
            "cve": "CVE-2015-0219",
            "id": "pyup.io-25640",
            "more_info_path": "/vulnerabilities/CVE-2015-0219/25640",
            "specs": [
                "<1.4.2"
            ],
            "v": "<1.4.2"
        }
    ],
    "black": [
        {
            "advisory": "Affected versions of Black are vulnerable to Regular Expression Denial of Service (ReDoS) via the lines_with_leading_tabs_expanded function in the strings.py file. An attacker could exploit this vulnerability by crafting a malicious input that causes a denial of service.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-66742",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/66742",
            "specs": [
                "<24.3.0"
            ],
            "v": "<24.3.0"
        }
    ],
    "blackboard-core": [
        {
            "advisory": "Affected versions of the blackboard-core package are potentially vulnerable to arbitrary code execution due to unsafe host-level execution being reachable without a hard security gate/explicit acknowledgment.",
            "cve": "PVE-2025-83045",
            "id": "pyup.io-83045",
            "more_info_path": "/vulnerabilities/PVE-2025-83045/83045",
            "specs": [
                "<1.3.1"
            ],
            "v": "<1.3.1"
        }
    ],
    "blackboardsync": [
        {
            "advisory": "Blackboardsync 0.11.1rc.1 sets the pyqt5-qt5 version in the Pipfile and updates PyQt5 due to a security release addressing a recent cURL vulnerability. This update, specific to macOS, resolves an issue where the Pipfile.lock was not valid on other platforms, ensuring compatibility across different operating systems. The PyQt5 version is also updated in the pyproject.toml to maintain security and functionality.",
            "cve": "PVE-2024-67002",
            "id": "pyup.io-67002",
            "more_info_path": "/vulnerabilities/PVE-2024-67002/67002",
            "specs": [
                "<0.11.1rc.1"
            ],
            "v": "<0.11.1rc.1"
        },
        {
            "advisory": "Blackboardsync 0.9.8 updates its dependency 'certifi' from 2023.5.7 to 2023.7.22 to include a security fix.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-61022",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/61022",
            "specs": [
                "<0.9.8"
            ],
            "v": "<0.9.8"
        }
    ],
    "blackduck": [
        {
            "advisory": "Synopsys hub-rest-api-python (aka blackduck on PyPI) version 0.0.25 - 0.0.52 does not validate SSL certificates in certain cases. See CVE-2020-27589.",
            "cve": "CVE-2020-27589",
            "id": "pyup.io-39070",
            "more_info_path": "/vulnerabilities/CVE-2020-27589/39070",
            "specs": [
                ">=0.0.25,<=0.0.52"
            ],
            "v": ">=0.0.25,<=0.0.52"
        }
    ],
    "blackjack21": [
        {
            "advisory": "Blackjack21 3.0.0 fixes several vulnerabilities related to data validation.\r\nhttps://github.com/rahul-nanwani/blackjack21/compare/2.0.1...v3.0.0#diff-312bb1d80aad60b8051333de1b78b15004177c233da9712b4fd1799b78bdc1c3R1",
            "cve": "PVE-2022-52382",
            "id": "pyup.io-52382",
            "more_info_path": "/vulnerabilities/PVE-2022-52382/52382",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        }
    ],
    "blacksheep": [
        {
            "advisory": "Blacksheep 1.2.5 adds built-in support for anti-forgery validation to protect against Cross-Site Request Forgery (XSRF/CSRF) attacks.",
            "cve": "PVE-2022-46072",
            "id": "pyup.io-46072",
            "more_info_path": "/vulnerabilities/PVE-2022-46072/46072",
            "specs": [
                "<1.2.5"
            ],
            "v": "<1.2.5"
        },
        {
            "advisory": "Affected versions of the BlackSheep package are vulnerable to CRLF injection due to unsanitized HTTP client request components. The HTTP client\u2019s header/method/URI serialization helpers (e.g., write_header, write_request_method, write_request_uri in blacksheep/scribe.py and blacksheep/scribe.pyx) allow \\r/\\n bytes to be embedded and then written into the outbound request, enabling header/request-line injection.",
            "cve": "PVE-2026-84401",
            "id": "pyup.io-84401",
            "more_info_path": "/vulnerabilities/PVE-2026-84401/84401",
            "specs": [
                "<2.4.6"
            ],
            "v": "<2.4.6"
        },
        {
            "advisory": "Affected versions of the blacksheep package are vulnerable to CRLF Injection due to missing validation of carriage return and line feed characters in outbound HTTP request components. In BlackSheep\u2019s HTTP client, ClientSession accepts untrusted data in request fields (including headers) without consistently neutralizing \\r and \\n sequences before serializing the request onto the wire.",
            "cve": "CVE-2026-22779",
            "id": "pyup.io-84469",
            "more_info_path": "/vulnerabilities/CVE-2026-22779/84469",
            "specs": [
                "<2.4.6"
            ],
            "v": "<2.4.6"
        }
    ],
    "blask": [
        {
            "advisory": "Blask 0.2.2 fixes some vulnerabilities. See: .",
            "cve": "PVE-2021-39028",
            "id": "pyup.io-39028",
            "more_info_path": "/vulnerabilities/PVE-2021-39028/39028",
            "specs": [
                "<0.2.2"
            ],
            "v": "<0.2.2"
        }
    ],
    "blazar": [
        {
            "advisory": "An issue was discovered in OpenStack blazar-dashboard before 1.3.1, 2.0.0, and 3.0.0. A user allowed to access the Blazar dashboard in Horizon may trigger code execution on the Horizon host as the user the Horizon service runs under (because the Python eval function is used). This may result in Horizon host unauthorized access and further compromise of the Horizon service. All setups using the Horizon dashboard with the blazar-dashboard plugin are affected. See: CVE-2020-26943.",
            "cve": "CVE-2020-26943",
            "id": "pyup.io-38884",
            "more_info_path": "/vulnerabilities/CVE-2020-26943/38884",
            "specs": [
                "<1.3.1"
            ],
            "v": "<1.3.1"
        }
    ],
    "bleach": [
        {
            "advisory": "bleach 2.1 converts control characters (backspace particularly) to \"?\" preventing malicious copy-and-paste situations.\r\nhttps://github.com/mozilla/bleach/commit/5490eb633def7983c3062b5657193e4210af4a49",
            "cve": "PVE-2021-34965",
            "id": "pyup.io-34965",
            "more_info_path": "/vulnerabilities/PVE-2021-34965/34965",
            "specs": [
                "<2.1"
            ],
            "v": "<2.1"
        },
        {
            "advisory": "Bleach 3.1.2 includes a fix for CVE-2020-6816: Mutation XSS via whitelisted math or svg and RCDATA tag with strip=False.\r\nhttps://github.com/mozilla/bleach/security/advisories/GHSA-m6xf-fq7q-8743",
            "cve": "CVE-2020-6816",
            "id": "pyup.io-42298",
            "more_info_path": "/vulnerabilities/CVE-2020-6816/42298",
            "specs": [
                "<3.1.2"
            ],
            "v": "<3.1.2"
        },
        {
            "advisory": "Bleach 3.3.0 includes a fix for CVE-2021-23980: A mutation XSS affects users calling bleach.clean with all of: svg or math in the allowed tags p or br in allowed tags style, title, noscript, script, textarea, noframes, iframe, or xmp in allowed tags the keyword argument strip_comments=False Note: none of the above tags are in the default allowed tags and strip_comments defaults to True.",
            "cve": "CVE-2021-23980",
            "id": "pyup.io-51843",
            "more_info_path": "/vulnerabilities/CVE-2021-23980/51843",
            "specs": [
                "<3.3.0"
            ],
            "v": "<3.3.0"
        },
        {
            "advisory": "Bleach 3.1.4 includes a fix for CVE-2020-6817: bleach.clean behavior parsing style attributes could result in a regular expression denial of service (ReDoS). Calls to bleach.clean with an allowed tag with an allowed style attribute are vulnerable to ReDoS. For example, bleach.clean(..., attributes={'a': ['style']}).",
            "cve": "CVE-2020-6817",
            "id": "pyup.io-38107",
            "more_info_path": "/vulnerabilities/CVE-2020-6817/38107",
            "specs": [
                "<=3.1.3"
            ],
            "v": "<=3.1.3"
        },
        {
            "advisory": "bleach  2.1.3 fixes a security issue.  Attributes that have URI values weren't properly sanitized if the values contained character entities. Using character entities, it was possible to construct a URI value with a scheme that was not allowed that would slide through unsanitized.",
            "cve": "CVE-2018-7753",
            "id": "pyup.io-35792",
            "more_info_path": "/vulnerabilities/CVE-2018-7753/35792",
            "specs": [
                ">=2.1,<2.1.3"
            ],
            "v": ">=2.1,<2.1.3"
        },
        {
            "advisory": "Affected versions of the Bleach package are vulnerable to Cross-site Scripting (XSS) due to improper handling of whitelisted tags in the bleach.clean function. The vulnerability exists because the bleach.clean function allows certain raw tags, such as \"noscript\" and \"script\", to be whitelisted, which can lead to unintended HTML mutations. An attacker can exploit this by crafting malicious HTML content that includes these tags, potentially executing arbitrary scripts in the context of the user's browser session.",
            "cve": "CVE-2020-6802",
            "id": "pyup.io-42297",
            "more_info_path": "/vulnerabilities/CVE-2020-6802/42297",
            "specs": [
                ">=2.1,<3.1.1"
            ],
            "v": ">=2.1,<3.1.1"
        }
    ],
    "bleach-extras": [
        {
            "advisory": "Bleach-extras 0.0.4 requires bleach version >=3.2.1 to deal with security issues.",
            "cve": "CVE-2020-6817",
            "id": "pyup.io-38875",
            "more_info_path": "/vulnerabilities/CVE-2020-6817/38875",
            "specs": [
                "<0.0.4"
            ],
            "v": "<0.0.4"
        },
        {
            "advisory": "Bleach-extras 0.0.4 requires bleach version >=3.2.1 to deal with security issues.",
            "cve": "CVE-2020-6816",
            "id": "pyup.io-46482",
            "more_info_path": "/vulnerabilities/CVE-2020-6816/46482",
            "specs": [
                "<0.0.4"
            ],
            "v": "<0.0.4"
        },
        {
            "advisory": "Bleach-extras 0.0.4 requires bleach version >=3.2.1 to deal with security issues.",
            "cve": "CVE-2020-6802",
            "id": "pyup.io-46483",
            "more_info_path": "/vulnerabilities/CVE-2020-6802/46483",
            "specs": [
                "<0.0.4"
            ],
            "v": "<0.0.4"
        },
        {
            "advisory": "Bleach-extras 0.0.4 requires bleach version >=3.2.1 to deal with security issues.",
            "cve": "CVE-2018-7753",
            "id": "pyup.io-46484",
            "more_info_path": "/vulnerabilities/CVE-2018-7753/46484",
            "specs": [
                "<0.0.4"
            ],
            "v": "<0.0.4"
        }
    ],
    "blendernc": [
        {
            "advisory": "Blendernc 0.6.0 updates its dependency 'pillow' to v9.0.0 to include security fixes.",
            "cve": "PVE-2021-44525",
            "id": "pyup.io-50128",
            "more_info_path": "/vulnerabilities/PVE-2021-44525/50128",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Blendernc 0.6.0 updates its dependency 'pillow' to v9.0.0 to include security fixes.",
            "cve": "PVE-2022-44524",
            "id": "pyup.io-50127",
            "more_info_path": "/vulnerabilities/PVE-2022-44524/50127",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Blendernc 0.6.0 updates its dependency 'pillow' to v9.0.0 to include security fixes.",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-50126",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/50126",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Blendernc 0.6.0 updates its dependency 'pillow' to v9.0.0 to include security fixes.",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-50111",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/50111",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "blickfeld-qb2": [
        {
            "advisory": "Blickfeld-qb2 1.7 patches CVE Security.\r\nhttps://github.com/Blickfeld/blickfeld-qb2/commit/27424bcd7c69c06e7cdfa60a37c7d8534eb0dfb0",
            "cve": "PVE-2023-62984",
            "id": "pyup.io-62984",
            "more_info_path": "/vulnerabilities/PVE-2023-62984/62984",
            "specs": [
                "<1.7"
            ],
            "v": "<1.7"
        }
    ],
    "blinkpy": [
        {
            "advisory": "blinkpy 0.10.2 sets minimum required version of the requests library to 2.20.0 due to vulnerability in earlier releases.",
            "cve": "PVE-2021-36596",
            "id": "pyup.io-36596",
            "more_info_path": "/vulnerabilities/PVE-2021-36596/36596",
            "specs": [
                "<0.10.2"
            ],
            "v": "<0.10.2"
        }
    ],
    "blint": [
        {
            "advisory": "BLint is powered by LIEF. BLint 1.0.35 and versions below uses LIEF as dependency which has a CVE on its versions below 0.13.0. \r\nhttps://nvd.nist.gov/vuln/detail/CVE-2022-43171\r\nhttps://github.com/lief-project/LIEF/issues/782",
            "cve": "CVE-2022-43171",
            "id": "pyup.io-62771",
            "more_info_path": "/vulnerabilities/CVE-2022-43171/62771",
            "specs": [
                "<=1.0.35"
            ],
            "v": "<=1.0.35"
        },
        {
            "advisory": "BLint is powered by LIEF. BLint 1.0.35 and versions below uses LIEF as dependency, which has a CVE on its versions below 0.13.0. \r\nhttps://nvd.nist.gov/vuln/detail/CVE-2022-38496\r\nhttps://deps.dev/pypi/blint/1.0.35/dependencies",
            "cve": "CVE-2022-38496",
            "id": "pyup.io-62768",
            "more_info_path": "/vulnerabilities/CVE-2022-38496/62768",
            "specs": [
                "<=1.0.35"
            ],
            "v": "<=1.0.35"
        }
    ],
    "block-io": [
        {
            "advisory": "block-io 1.1.7 includes a fix for CVE-2013-7459 - https://security-tracker.debian.org/tracker/CVE-2013-7459",
            "cve": "CVE-2013-7459",
            "id": "pyup.io-36442",
            "more_info_path": "/vulnerabilities/CVE-2013-7459/36442",
            "specs": [
                "<1.1.7"
            ],
            "v": "<1.1.7"
        },
        {
            "advisory": "Block-io 1.1.9 updates its dependency 'requests' to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36712",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36712",
            "specs": [
                "<1.1.9"
            ],
            "v": "<1.1.9"
        }
    ],
    "blueice": [
        {
            "advisory": "Blueice 1.1.0 fixes a race condition that arose when parallel jobs attempted to write to the same cache file simultaneously. This update introduces the use of the atomicwrites package, ensuring atomic file writing operations. It prevents data corruption and ensures the integrity of cache files.",
            "cve": "PVE-2024-64087",
            "id": "pyup.io-64087",
            "more_info_path": "/vulnerabilities/PVE-2024-64087/64087",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "boatswain": [
        {
            "advisory": "Boatswain 1.0.4 includes a security patch for the function 'main' in 'boatswain/cli.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/NLeSC/boatswain/commit/1fc3f79b8f1f2affb407c7a147cca71c11f26d3c",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41308",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41308",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        }
    ],
    "boaviztapi": [
        {
            "advisory": "Boaviztapi bumped idna from 3.6 to 3.7 via Dependabot to address CVE-2024-3651.",
            "cve": "CVE-2024-3651",
            "id": "pyup.io-73378",
            "more_info_path": "/vulnerabilities/CVE-2024-3651/73378",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        },
        {
            "advisory": "Boaviztapi bumped certifi from 2024.2.2 to 2024.7.4 via Dependabot to address CVE-2024-39689.",
            "cve": "CVE-2024-39689",
            "id": "pyup.io-73399",
            "more_info_path": "/vulnerabilities/CVE-2024-39689/73399",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        },
        {
            "advisory": "Boaviztapi bumped requests from 2.31.0 to 2.32.2 via Dependabot to address CVE-2024-35195.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-73400",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/73400",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        }
    ],
    "bobocep": [
        {
            "advisory": "Bobocep 1.2.1 updates its pycryptodome dependency from version 3.19.0 to 3.20.0 to address CVE-2023-52323.",
            "cve": "CVE-2023-52323",
            "id": "pyup.io-71800",
            "more_info_path": "/vulnerabilities/CVE-2023-52323/71800",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        }
    ],
    "bobtemplates-cs": [
        {
            "advisory": "Bobtemplates.cs 1.6 improves default security policies for Nginx.\r\nhttps://github.com/codesyntax/bobtemplates.cs/commit/c3b00adfc1210c46c49f269a7dbd85a91435463f",
            "cve": "PVE-2022-51164",
            "id": "pyup.io-51164",
            "more_info_path": "/vulnerabilities/PVE-2022-51164/51164",
            "specs": [
                "<1.6"
            ],
            "v": "<1.6"
        }
    ],
    "bodhi": [
        {
            "advisory": "Bodhi 2.2.0 addresses CVE-2016-1000008 by disallowing the re-use of solved captchas. Additionally, the captcha is\r\nwarped to make it more difficult to solve through automation.\r\nhttps://github.com/fedora-infra/bodhi/pull/857\r\nhttps://github.com/fedora-infra/bodhi/commit/f0122855",
            "cve": "CVE-2016-1000008",
            "id": "pyup.io-34274",
            "more_info_path": "/vulnerabilities/CVE-2016-1000008/34274",
            "specs": [
                "<2.2.0"
            ],
            "v": "<2.2.0"
        },
        {
            "advisory": "Bodhi 5.6.1 fixes two reflected XSS vulnerabilities.",
            "cve": "CVE-2020-15855",
            "id": "pyup.io-48555",
            "more_info_path": "/vulnerabilities/CVE-2020-15855/48555",
            "specs": [
                "<5.6.1"
            ],
            "v": "<5.6.1"
        },
        {
            "advisory": "Bodhi 2.9.0 and lower is vulnerable to cross-site scripting resulting in code injection caused by incorrect validation of bug titles.",
            "cve": "CVE-2017-1002152",
            "id": "pyup.io-42337",
            "more_info_path": "/vulnerabilities/CVE-2017-1002152/42337",
            "specs": [
                "<=2.9.0"
            ],
            "v": "<=2.9.0"
        }
    ],
    "bodhi-server": [
        {
            "advisory": "Bodhi-server 2.2.0 addresses CVE-2016-1000008 by disallowing the re-use of solved captchas. Additionally, the captcha is warped to make it more difficult to solve through automation.\r\nSee: https://github.com/fedora-infra/bodhi/pull/857\r\nAnd: https://github.com/fedora-infra/bodhi/commit/f0122855",
            "cve": "CVE-2016-1000008",
            "id": "pyup.io-34241",
            "more_info_path": "/vulnerabilities/CVE-2016-1000008/34241",
            "specs": [
                "<2.2.0"
            ],
            "v": "<2.2.0"
        }
    ],
    "bokeh": [
        {
            "advisory": "Bokeh before 1.0.4 used a Pyyaml version that was vulnerable to CVE-2017-18342.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-36780",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/36780",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        },
        {
            "advisory": "Bokeh 1.1.0 updates its NPM dependency 'handlebars' to v4.1.0 to include a security fix.",
            "cve": "PVE-2021-37031",
            "id": "pyup.io-37031",
            "more_info_path": "/vulnerabilities/PVE-2021-37031/37031",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Bokeh 1.2.0 updates its NPM dependency 'handlebars' to v4.1.2 to include a security fix.",
            "cve": "PVE-2021-37170",
            "id": "pyup.io-37170",
            "more_info_path": "/vulnerabilities/PVE-2021-37170/37170",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        },
        {
            "advisory": "Bokeh 1.2.0 updates its NPM dependency 'js-yaml' to v3.13.1 to include a security fix.",
            "cve": "PVE-2022-45295",
            "id": "pyup.io-45295",
            "more_info_path": "/vulnerabilities/PVE-2022-45295/45295",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        },
        {
            "advisory": "Bokeh 1.2.0 updates its NPM dependency 'jquery' to v3.4.0 to include security fixes.",
            "cve": "CVE-2019-11358",
            "id": "pyup.io-45293",
            "more_info_path": "/vulnerabilities/CVE-2019-11358/45293",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        },
        {
            "advisory": "Bokeh 2.4.2 updates its dependency 'jquery-ui' to v1.13.0 to include security fixes.",
            "cve": "CVE-2021-41183",
            "id": "pyup.io-42814",
            "more_info_path": "/vulnerabilities/CVE-2021-41183/42814",
            "specs": [
                "<2.4.2"
            ],
            "v": "<2.4.2"
        },
        {
            "advisory": "Bokeh 2.4.2 updates its dependency 'jquery-ui' to v1.13.0 to include security fixes.",
            "cve": "CVE-2021-41184",
            "id": "pyup.io-42815",
            "more_info_path": "/vulnerabilities/CVE-2021-41184/42815",
            "specs": [
                "<2.4.2"
            ],
            "v": "<2.4.2"
        },
        {
            "advisory": "Bokeh 2.4.2 updates its dependency 'jquery-ui' to v1.13.0 to include security fixes.",
            "cve": "CVE-2021-41182",
            "id": "pyup.io-42772",
            "more_info_path": "/vulnerabilities/CVE-2021-41182/42772",
            "specs": [
                "<2.4.2"
            ],
            "v": "<2.4.2"
        },
        {
            "advisory": "Affected versions of the bokeh package are vulnerable to Cross-Site WebSocket Hijacking due to flawed allowlist hostname matching that permits incomplete Origin validation. The match_host function in src/bokeh/server/util.py uses zip() to compare hostname segments against allowlist patterns and fails to reject hosts that are longer than the configured pattern, allowing attacker-controlled Origins that merely start with an allowlisted host to be treated as trusted.",
            "cve": "CVE-2026-21883",
            "id": "pyup.io-83972",
            "more_info_path": "/vulnerabilities/CVE-2026-21883/83972",
            "specs": [
                "<3.8.2"
            ],
            "v": "<3.8.2"
        }
    ],
    "boneio": [
        {
            "advisory": "Affected versions of the app_black package are vulnerable to insecure transport configuration due to defaulting the Web UI/Node-RED reverse proxy to self-signed, on-demand TLS certificates.",
            "cve": "PVE-2025-83162",
            "id": "pyup.io-83162",
            "more_info_path": "/vulnerabilities/PVE-2025-83162/83162",
            "specs": [
                "<1.0.0dev16"
            ],
            "v": "<1.0.0dev16"
        }
    ],
    "bookops-worldcat": [
        {
            "advisory": "Bookops-worldcat version 0.3.5 updates its urllib3 dependency to 1.26.5, addressing security vulnerability CVE-2021-33503.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-66958",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/66958",
            "specs": [
                "<0.3.5"
            ],
            "v": "<0.3.5"
        }
    ],
    "borgbackup": [
        {
            "advisory": "Borgbackup is vulnerable to an unauthorized remote repository access vulnerability. If you used e.g. --restrict-to-path /path/client1/ (with or without trailing slash does not make a difference), it acted like a path prefix match using /path/client1 (note the missing trailing slash) - the code then also allowed working in e.g. /path/client13 or /path/client1000.\r\nhttps://github.com/borgbackup/borg/issues/1428",
            "cve": "PVE-2024-64382",
            "id": "pyup.io-64382",
            "more_info_path": "/vulnerabilities/PVE-2024-64382/64382",
            "specs": [
                "<1.0.7"
            ],
            "v": "<1.0.7"
        },
        {
            "advisory": "Borgbackup is vulnerable to a flaw in the cryptographic authentication scheme. It allowed an attacker to spoof the manifest.",
            "cve": "CVE-2016-10099",
            "id": "pyup.io-64397",
            "more_info_path": "/vulnerabilities/CVE-2016-10099/64397",
            "specs": [
                "<1.0.9"
            ],
            "v": "<1.0.9"
        },
        {
            "advisory": "Borgbackup is vulnerable to spoofing in borg check. When rebuilding the manifest (which should only be needed very rarely) duplicate archive names would be handled on a \"first come first serve\" basis, allowing an attacker to apparently replace archives.",
            "cve": "CVE-2016-10100",
            "id": "pyup.io-64398",
            "more_info_path": "/vulnerabilities/CVE-2016-10100/64398",
            "specs": [
                "<1.0.9"
            ],
            "v": "<1.0.9"
        },
        {
            "advisory": "Borgbackup is affected by a wrong permissions vulnerability. As a fix, Fuse was configured with \"default_permissions\". Without that, someone could access a mount with -o uid=1001,umask=077 as user 1000.\r\nhttps://github.com/borgbackup/borg/issues/3903",
            "cve": "PVE-2024-64380",
            "id": "pyup.io-64380",
            "more_info_path": "/vulnerabilities/PVE-2024-64380/64380",
            "specs": [
                "<1.1.9"
            ],
            "v": "<1.1.9"
        },
        {
            "advisory": "Borgbackup is affected by a archives spoofing vulnerability. A flaw in the cryptographic authentication scheme in Borg allowed an attacker to fake archives and potentially indirectly cause backup data loss in the repository.\r\nhttps://github.com/borgbackup/borg/blob/1.2.6/docs/changes.rst#pre-125-archives-spoofing-vulnerability-cve-2023-36811",
            "cve": "CVE-2023-36811",
            "id": "pyup.io-64379",
            "more_info_path": "/vulnerabilities/CVE-2023-36811/64379",
            "specs": [
                "<1.2.6"
            ],
            "v": "<1.2.6"
        },
        {
            "advisory": "Incorrect implementation of access controls allows remote users to override repository restrictions in Borg servers 1.1.x before 1.1.3.",
            "cve": "CVE-2017-15914",
            "id": "pyup.io-53939",
            "more_info_path": "/vulnerabilities/CVE-2017-15914/53939",
            "specs": [
                ">=1.1.0b1,<1.1.3"
            ],
            "v": ">=1.1.0b1,<1.1.3"
        }
    ],
    "borgmatic": [
        {
            "advisory": "Borgmatic is vulnerable to shell injection within the command hook variable/constant interpolation.\r\nhttps://github.com/borgmatic-collective/borgmatic/commit/3c22a8ec164087beb1d292dc114f78f8b6382ae2",
            "cve": "PVE-2024-64395",
            "id": "pyup.io-64395",
            "more_info_path": "/vulnerabilities/PVE-2024-64395/64395",
            "specs": [
                "<1.8.7"
            ],
            "v": "<1.8.7"
        },
        {
            "advisory": "Borgmatic is vulnerable to shell injection within the SQLite hook.\r\nhttps://github.com/borgmatic-collective/borgmatic/commit/3c22a8ec164087beb1d292dc114f78f8b6382ae2",
            "cve": "PVE-2024-64393",
            "id": "pyup.io-64393",
            "more_info_path": "/vulnerabilities/PVE-2024-64393/64393",
            "specs": [
                "<1.8.7"
            ],
            "v": "<1.8.7"
        },
        {
            "advisory": "Borgmatic is vulnerable to shell injection within the \"borgmatic borg\" action.\r\nhttps://github.com/borgmatic-collective/borgmatic/commit/3c22a8ec164087beb1d292dc114f78f8b6382ae2",
            "cve": "PVE-2024-64394",
            "id": "pyup.io-64394",
            "more_info_path": "/vulnerabilities/PVE-2024-64394/64394",
            "specs": [
                "<1.8.7"
            ],
            "v": "<1.8.7"
        },
        {
            "advisory": "Borgmatic is vulnerable to shell injection within the PostgreSQL hook.\r\nhttps://github.com/borgmatic-collective/borgmatic/commit/3c22a8ec164087beb1d292dc114f78f8b6382ae2",
            "cve": "PVE-2024-64386",
            "id": "pyup.io-64386",
            "more_info_path": "/vulnerabilities/PVE-2024-64386/64386",
            "specs": [
                "<1.8.7"
            ],
            "v": "<1.8.7"
        },
        {
            "advisory": "Borgmatic is vulnerable to shell injection within the MongoDB hook.\r\nhttps://github.com/borgmatic-collective/borgmatic/commit/3c22a8ec164087beb1d292dc114f78f8b6382ae2",
            "cve": "PVE-2024-64392",
            "id": "pyup.io-64392",
            "more_info_path": "/vulnerabilities/PVE-2024-64392/64392",
            "specs": [
                "<1.8.7"
            ],
            "v": "<1.8.7"
        },
        {
            "advisory": "Affected versions of the borgmatic package are vulnerable to Shell Injection due to insufficient sanitization of user-controlled values in command hook interpolation. The constant interpolation mechanism in command hooks fails to properly escape shell metacharacters when processing user-supplied values, allowing arbitrary command execution.",
            "cve": "PVE-2026-84591",
            "id": "pyup.io-84591",
            "more_info_path": "/vulnerabilities/PVE-2026-84591/84591",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        }
    ],
    "boss-cli": [
        {
            "advisory": "Boss-cli 1.0.0a20 updates its dependency 'requests' to v2.20.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-38521",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/38521",
            "specs": [
                "<1.0.0a20"
            ],
            "v": "<1.0.0a20"
        },
        {
            "advisory": "Boss-cli 1.0.0alpha.18 updates its dependency 'paramiko' to v2.4.1 to include a security fix.",
            "cve": "CVE-2018-7750",
            "id": "pyup.io-36543",
            "more_info_path": "/vulnerabilities/CVE-2018-7750/36543",
            "specs": [
                "<1.0.0alpha.18"
            ],
            "v": "<1.0.0alpha.18"
        },
        {
            "advisory": "Boss-cli 1.0.0beta.6 uses yaml.FullLoader for loading yaml config and upgrades the dependency pyyaml (CVE-2017-18342).",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-37129",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/37129",
            "specs": [
                "<1.0.0beta.6"
            ],
            "v": "<1.0.0beta.6"
        }
    ],
    "botaa3": [
        {
            "advisory": "Botaa3 is a malicious package, typosquatting. It creates a backdoor in your system.\r\nhttps://blog.sonatype.com/another-day-of-malware-malicious-botaa3-pypi-package",
            "cve": "PVE-2022-45424",
            "id": "pyup.io-45424",
            "more_info_path": "/vulnerabilities/PVE-2022-45424/45424",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "botframework-connector": [
        {
            "advisory": "Bot Framework SDK Information Disclosure Vulnerability.\r\nhttps://github.com/microsoft/botbuilder-python/security/advisories/GHSA-cqff-fx2x-p86v",
            "cve": "CVE-2021-1725",
            "id": "pyup.io-54255",
            "more_info_path": "/vulnerabilities/CVE-2021-1725/54255",
            "specs": [
                ">=4.7.0,<4.7.2",
                ">=4.8.0,<4.8.1",
                ">=4.9.0,<4.9.3",
                ">=4.10.0,<4.10.1"
            ],
            "v": ">=4.7.0,<4.7.2,>=4.8.0,<4.8.1,>=4.9.0,<4.9.3,>=4.10.0,<4.10.1"
        }
    ],
    "boto": [
        {
            "advisory": "Boto 2.39.0 replaces yaml.load() with yaml.safe_load() to avoid a Code Execution vulnerability.",
            "cve": "PVE-2017-47528",
            "id": "pyup.io-47528",
            "more_info_path": "/vulnerabilities/PVE-2017-47528/47528",
            "specs": [
                "<2.39.0"
            ],
            "v": "<2.39.0"
        },
        {
            "advisory": "Boto 2.9.0 disables loading of external XML entities in BotoServerErrors.\r\nhttps://github.com/jamesls/boto/commit/1ad6e6b233e9cb021269ef3ce9f8a610587e50b9",
            "cve": "PVE-2022-48018",
            "id": "pyup.io-48018",
            "more_info_path": "/vulnerabilities/PVE-2022-48018/48018",
            "specs": [
                "<2.9.0"
            ],
            "v": "<2.9.0"
        }
    ],
    "boto3": [
        {
            "advisory": "Boto3 version 1.4.5 fixes an information exposure vulnerability: The boto logger boto3.resources.action, which propagates to root logger, logs the entire uploaded bytes at INFO level.\r\nhttps://github.com/boto/boto3/issues/1017",
            "cve": "PVE-2021-41708",
            "id": "pyup.io-41708",
            "more_info_path": "/vulnerabilities/PVE-2021-41708/41708",
            "specs": [
                "<1.4.5"
            ],
            "v": "<1.4.5"
        },
        {
            "advisory": "Boto3 1.6.12 updates its dependency 'botocore' to version '1.9.12' to include a fix for a Race Condition vulnerability.",
            "cve": "PVE-2023-59547",
            "id": "pyup.io-59549",
            "more_info_path": "/vulnerabilities/PVE-2023-59547/59549",
            "specs": [
                "<1.6.12"
            ],
            "v": "<1.6.12"
        }
    ],
    "boto33": [
        {
            "advisory": "Boto33 is a malicious package, pytosquatting the popular package 'boto3'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53254",
            "id": "pyup.io-53254",
            "more_info_path": "/vulnerabilities/PVE-2023-53254/53254",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "botoa": [
        {
            "advisory": "Botoa is a malicious package, pytosquatting the popular package 'boto3'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53255",
            "id": "pyup.io-53255",
            "more_info_path": "/vulnerabilities/PVE-2023-53255/53255",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "botoa3": [
        {
            "advisory": "Botoa3 is a malicious package, pytosquatting the popular package 'boto3'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53256",
            "id": "pyup.io-53256",
            "more_info_path": "/vulnerabilities/PVE-2023-53256/53256",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "botocore": [
        {
            "advisory": "Botocore 1.9.12 includes a fix for a Race Condition vulnerability.",
            "cve": "PVE-2023-59547",
            "id": "pyup.io-59547",
            "more_info_path": "/vulnerabilities/PVE-2023-59547/59547",
            "specs": [
                "<1.9.12"
            ],
            "v": "<1.9.12"
        }
    ],
    "botoo": [
        {
            "advisory": "Botoo is a malicious package, pytosquatting the popular package 'boto3'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53257",
            "id": "pyup.io-53257",
            "more_info_path": "/vulnerabilities/PVE-2023-53257/53257",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "bottle": [
        {
            "advisory": "redirect() in bottle.py in bottle 0.12.10 doesn't filter a \"\\r\\n\" sequence, which leads to a CRLF attack, as demonstrated by a redirect(\"233\\r\\nSet-Cookie: name=salt\") call.",
            "cve": "CVE-2016-9964",
            "id": "pyup.io-25642",
            "more_info_path": "/vulnerabilities/CVE-2016-9964/25642",
            "specs": [
                "<0.12.10"
            ],
            "v": "<0.12.10"
        },
        {
            "advisory": "The package bottle from 0 and before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter. See CVE-2020-28473.",
            "cve": "CVE-2020-28473",
            "id": "pyup.io-39461",
            "more_info_path": "/vulnerabilities/CVE-2020-28473/39461",
            "specs": [
                "<0.12.19"
            ],
            "v": "<0.12.19"
        },
        {
            "advisory": "Bottle before 0.12.20 mishandles errors during early request binding.",
            "cve": "CVE-2022-31799",
            "id": "pyup.io-49258",
            "more_info_path": "/vulnerabilities/CVE-2022-31799/49258",
            "specs": [
                "<0.12.20"
            ],
            "v": "<0.12.20"
        },
        {
            "advisory": "Bottle 0.10.x before 0.10.12, 0.11.x before 0.11.7, and 0.12.x before 0.12.6 does not properly limit content types, which allows remote attackers to bypass intended access restrictions via an accepted Content-Type followed by a ; (semi-colon) and a Content-Type that would not be accepted, as demonstrated in YouCompleteMe to execute arbitrary code.",
            "cve": "CVE-2014-3137",
            "id": "pyup.io-35548",
            "more_info_path": "/vulnerabilities/CVE-2014-3137/35548",
            "specs": [
                ">=0.10,<0.10.12",
                ">=0.11,<0.11.7",
                ">=0.12,<0.12.6"
            ],
            "v": ">=0.10,<0.10.12,>=0.11,<0.11.7,>=0.12,<0.12.6"
        }
    ],
    "bounter": [
        {
            "advisory": "A null pointer reference is found within the CMS_Conservative_increment_obj function in bounter version 1.01 and 1.10, developed by RaRe-Technologies. This vulnerability allows potential attackers to initiate Denial of Service attacks through the submission of extremely large hash bucket widths.",
            "cve": "CVE-2021-41497",
            "id": "pyup.io-62664",
            "more_info_path": "/vulnerabilities/CVE-2021-41497/62664",
            "specs": [
                "==1.01",
                "==1.10"
            ],
            "v": "==1.01,==1.10"
        }
    ],
    "boussole": [
        {
            "advisory": "Boussole 1.5.0 fixes the PyYAML 'load()' deprecation warning. For a recent security issue, PyYAML has introduced a change to its ``load()`` method to be more safe. Boussole now uses the full loader mode so it does not trigger a warning anymore.",
            "cve": "PVE-2021-37147",
            "id": "pyup.io-37147",
            "more_info_path": "/vulnerabilities/PVE-2021-37147/37147",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        }
    ],
    "brasil-gov-portal": [
        {
            "advisory": "Brasil.gov.portal before 1.5.1 uses Plone <4.3.15 which is vulnerable to several XSS and redirect flaws, and a sandbox escape.",
            "cve": "CVE-2017-1000484",
            "id": "pyup.io-35086",
            "more_info_path": "/vulnerabilities/CVE-2017-1000484/35086",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        }
    ],
    "brds": [
        {
            "advisory": "Brds 0.3.0 includes a fix for a path traversal vulnerability.\r\nhttps://github.com/brahle/brds/commit/65a470df27a35d03ca4349707baa0fb0c8c6da43",
            "cve": "PVE-2023-55038",
            "id": "pyup.io-55038",
            "more_info_path": "/vulnerabilities/PVE-2023-55038/55038",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "bridgecrew": [
        {
            "advisory": "Checkov 2.0.1029 introduces a fix for a vulnerability that previously allowed security group rules in Terraform configurations to permit unrestricted ingress access from 0.0.0.0:0 to port 22, commonly used for SSH.\r\nhttps://github.com/bridgecrewio/checkov/issues/1973\r\nhttps://github.com/bridgecrewio/checkov/pull/2749",
            "cve": "PVE-2024-63921",
            "id": "pyup.io-63921",
            "more_info_path": "/vulnerabilities/PVE-2024-63921/63921",
            "specs": [
                "<2.0.1029"
            ],
            "v": "<2.0.1029"
        },
        {
            "advisory": "Bridgecrew 2.0.677 fixes unsafe regex to prevent ReDOS attacks.\r\nhttps://github.com/bridgecrewio/checkov/commit/333d3bcc6c9c178bffc37ac19422b41b665bfbc9",
            "cve": "PVE-2024-63660",
            "id": "pyup.io-63660",
            "more_info_path": "/vulnerabilities/PVE-2024-63660/63660",
            "specs": [
                "<2.0.677"
            ],
            "v": "<2.0.677"
        },
        {
            "advisory": "Bridgecrew before 2.0.26 is vulnerable to unsafe deserialization, which allows arbitrary code execution when processing a malicious terraform file.",
            "cve": "CVE-2021-3035",
            "id": "pyup.io-63934",
            "more_info_path": "/vulnerabilities/CVE-2021-3035/63934",
            "specs": [
                ">=2.0.0,<2.0.26"
            ],
            "v": ">=2.0.0,<2.0.26"
        }
    ],
    "brotli": [
        {
            "advisory": "A buffer overflow exists in the Brotli library versions prior to 1.0.8 where an attacker controlling the input length of a \"one-shot\" decompression request to a script can trigger a crash, which happens when copying over chunks of data larger than 2 GiB. It is recommended to update Brotli library to 1.0.8 or later. If one cannot update, it is recommended to use the \"streaming\" API as opposed to the \"one-shot\" API, and impose chunk size limits.",
            "cve": "CVE-2020-8927",
            "id": "pyup.io-42299",
            "more_info_path": "/vulnerabilities/CVE-2020-8927/42299",
            "specs": [
                "<1.0.8"
            ],
            "v": "<1.0.8"
        },
        {
            "advisory": "Affected versions of the brotli package are vulnerable to Denial of Service (DoS) due to unbounded memory allocation during decompression of highly compressible inputs. The Python streaming API method Decompressor.process expands its output buffer without an enforceable limit, so a crafted Brotli stream (for example, zero-filled data with an extreme compression ratio) can inflate to a massive size and exhaust memory.",
            "cve": "CVE-2025-6176",
            "id": "pyup.io-81038",
            "more_info_path": "/vulnerabilities/CVE-2025-6176/81038",
            "specs": [
                "<=1.1.0"
            ],
            "v": "<=1.1.0"
        }
    ],
    "brotli-asgi": [
        {
            "advisory": "Brotli-asgi 1.4.0 updates its dependency 'starlette' to v0.25.0 to include a security fix.",
            "cve": "CVE-2023-30798",
            "id": "pyup.io-55157",
            "more_info_path": "/vulnerabilities/CVE-2023-30798/55157",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        }
    ],
    "brotlicffi": [
        {
            "advisory": "Affected versions of the brotlicffi package before 1.2.0.0 are vulnerable to Denial of Service (DoS) due to missing limits on decompressed output size in the Decompressor.decompress() and Decompressor.process() methods. These methods feed attacker-controlled Brotli data into dynamically growing in-memory buffers without enforcing an output_buffer_limit, allowing highly compressible payloads to expand into extremely large outputs and exhaust memory resources when libbrotli inflates them.",
            "cve": "PVE-2025-81803",
            "id": "pyup.io-81803",
            "more_info_path": "/vulnerabilities/PVE-2025-81803/81803",
            "specs": [
                "<1.2.0.0"
            ],
            "v": "<1.2.0.0"
        }
    ],
    "browser-use": [
        {
            "advisory": "Affected versions of browser\u2011use are potentially vulnerable to insecure configuration (CWE\u2011693: Protection Mechanism Failure). The default settings disable_security=True and --remote-debugging-address=0.0.0.0 disable sandbox protections and expose the Chrome DevTools Protocol on all interfaces, enabling remote attackers to execute arbitrary commands or exfiltrate cross\u2011origin data via port\u00a09222 .",
            "cve": "PVE-2025-76717",
            "id": "pyup.io-76717",
            "more_info_path": "/vulnerabilities/PVE-2025-76717/76717",
            "specs": [
                "<0.1.41"
            ],
            "v": "<0.1.41"
        },
        {
            "advisory": "In browser-use (aka Browser Use) before 0.1.45, URL parsing of allowed_domains is mishandled because userinfo can be placed in the authority component.",
            "cve": "CVE-2025-47241",
            "id": "pyup.io-77047",
            "more_info_path": "/vulnerabilities/CVE-2025-47241/77047",
            "specs": [
                "<0.1.45"
            ],
            "v": "<0.1.45"
        },
        {
            "advisory": "Affected versions of browser-use are potentially vulnerable to Authorization Bypass due to inconsistent domain validation in navigation functions. The search_google and go_to_url functions fail to enforce domain restrictions by using direct page.goto() calls instead of the validated browser_session.navigate_to() method, leading to potential unauthorized access to restricted domains that should be blocked by the allowed_domains configuration.",
            "cve": "PVE-2025-77877",
            "id": "pyup.io-77877",
            "more_info_path": "/vulnerabilities/PVE-2025-77877/77877",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Affected versions of the server were vulnerable to a security misconfiguration where the debug port was exposed on all network interfaces.",
            "cve": "PVE-2025-76718",
            "id": "pyup.io-76718",
            "more_info_path": "/vulnerabilities/PVE-2025-76718/76718",
            "specs": [
                "<1.7"
            ],
            "v": "<1.7"
        }
    ],
    "brume": [
        {
            "advisory": "Brume 2.0.2 includes a security patch for the function 'load' in 'brume/config.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/flou/brume/commit/9407537a4f24521b6d009a52a77b4f6deabb0b71#diff-db395031eb85fc2c76864f9a9e13ed341de029a79e0fc76a798090f50504fb6a",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41309",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41309",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        }
    ],
    "bsblan": [
        {
            "advisory": "Bsblan 0.27 sets the DEFAULT_FLAG in config to read-only for added level of security.",
            "cve": "PVE-2021-37697",
            "id": "pyup.io-37697",
            "more_info_path": "/vulnerabilities/PVE-2021-37697/37697",
            "specs": [
                "<0.27"
            ],
            "v": "<0.27"
        }
    ],
    "bsdiff4": [
        {
            "advisory": "Bsdiff4 1.2.0 includes a fix for CVE-2020-15904: A buffer overflow in the patching routine of bsdiff4 before 1.2.0 allows an attacker to write to heap memory (beyond allocated bounds) via a crafted patch file.",
            "cve": "CVE-2020-15904",
            "id": "pyup.io-42280",
            "more_info_path": "/vulnerabilities/CVE-2020-15904/42280",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "bthome-ble": [
        {
            "advisory": "Affected versions of the bthome-ble package are potentially vulnerable to an encryption downgrade attack due to insufficient enforcement of secure encryption requirements. The BLE pairing and encryption handling logic allowed a connection to proceed with downgraded or weaker encryption settings instead of strictly requiring the expected secure mode.",
            "cve": "PVE-2025-82660",
            "id": "pyup.io-82660",
            "more_info_path": "/vulnerabilities/PVE-2025-82660/82660",
            "specs": [
                "<3.15.1"
            ],
            "v": "<3.15.1"
        }
    ],
    "bugsink": [
        {
            "advisory": "Affected versions of this package are vulnerable to Denial of Service (DOS) attacks via Brotli Decompression Bomb. The `brotli_generator` function fails to implement output buffer limiting and proper flow control when processing brotli-compressed payloads, leading to excessive memory consumption and unbounded memory allocation. An attacker can exploit this vulnerability by submitting specially crafted brotli payloads with extreme compression ratios that cause the decompressor to buffer large amounts of unprocessed data, potentially causing the application to become unresponsive or crash due to out-of-memory conditions.",
            "cve": "PVE-2026-84219",
            "id": "pyup.io-84219",
            "more_info_path": "/vulnerabilities/PVE-2026-84219/84219",
            "specs": [
                "<2.0.5"
            ],
            "v": "<2.0.5"
        },
        {
            "advisory": "Affected versions of the bugsink package are vulnerable to Denial of Service (DoS) due to unbounded decompression of attacker-controlled Brotli-compressed payloads that can exhaust server memory. In the Brotli handling logic for incoming error envelopes, Bugsink decompresses user-supplied Brotli streams before enforcing any effective limits or throttling on resource usage, allowing a single highly compressed \u201cBrotli bomb\u201d (for example, a stream containing many zeros) to expand into a very large in-memory buffer.",
            "cve": "CVE-2025-64508",
            "id": "pyup.io-81579",
            "more_info_path": "/vulnerabilities/CVE-2025-64508/81579",
            "specs": [
                "<2.0.5"
            ],
            "v": "<2.0.5"
        },
        {
            "advisory": "Affected versions of bugsink are vulnerable to Denial of Service (DoS) via Brotli Decompression Hang. The `brotli_generator` function fails to ensure forward progress during decompression by not validating that output is produced when the decompressor cannot accept more input or when draining remaining data, leading to infinite loops where the decompressor becomes stuck without producing output or finishing. An attacker can exploit this vulnerability by submitting specially crafted brotli payloads that cause the decompressor to enter a non-terminating state, potentially causing the application to  hang indefinitely and become unresponsive, exhausting worker threads or processes.",
            "cve": "PVE-2026-84218",
            "id": "pyup.io-84218",
            "more_info_path": "/vulnerabilities/PVE-2026-84218/84218",
            "specs": [
                "<2.0.6"
            ],
            "v": "<2.0.6"
        },
        {
            "advisory": "Affected versions of the bugsink package are vulnerable to Denial of Service (DoS) due to unbounded CPU consumption when decompressing attacker-controlled Brotli-compressed envelopes without enforcing progress or resource limits. In the bugsink.streams.brotli_generator function, Brotli-compressed payloads read from the reporting input stream are passed to brotli.Decompressor in a loop that can fail to terminate when the decompressor neither finishes nor produces output, allowing a single crafted envelope to keep the decompression logic busy indefinitely.",
            "cve": "CVE-2025-64509",
            "id": "pyup.io-81580",
            "more_info_path": "/vulnerabilities/CVE-2025-64509/81580",
            "specs": [
                "<2.0.6"
            ],
            "v": "<2.0.6"
        },
        {
            "advisory": "Bugsink is a self-hosted error tracking service. In versions 1.4.2 and below, 1.5.0 through 1.5.4, 1.6.0 through 1.6.3, and 1.7.0 through 1.7.3, ingestion paths construct file locations directly from untrusted event_id input without validation. A specially crafted event_id can result in paths outside the intended directory, potentially allowing file overwrite or creation in arbitrary locations. Submitting such input requires access to a valid DSN, potentially exposing them. If Bugsink runs in a container, the effect is confined to the container\u2019s filesystem. In non-containerized setups, the overwrite may affect other parts of the system accessible to that user. This is fixed in versions 1.4.3, 1.5.5, 1.6.4 and 1.7.4.",
            "cve": "CVE-2025-54433",
            "id": "pyup.io-78598",
            "more_info_path": "/vulnerabilities/CVE-2025-54433/78598",
            "specs": [
                ">=1.7.0,<1.7.4",
                ">=1.6.0,<1.6.4",
                ">=1.5.0,<1.5.5",
                "<1.4.3"
            ],
            "v": ">=1.7.0,<1.7.4,>=1.6.0,<1.6.4,>=1.5.0,<1.5.5,<1.4.3"
        }
    ],
    "buildbot": [
        {
            "advisory": "Buildbot before 1.3.0 did not use ``hmac.compare_digest()`` in GitHub hooks.\r\nhttps://github.com/buildbot/buildbot/commit/e159e4ed0a2fee9c7e41e81ae81333b0c9557256",
            "cve": "PVE-2021-36320",
            "id": "pyup.io-36320",
            "more_info_path": "/vulnerabilities/PVE-2021-36320/36320",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Buildbot 1.8.1 includes a fix for CVE-2019-7313: www/resource.py in Buildbot before 1.8.1 allows CRLF injection in the Location header of /auth/login and /auth/logout via the redirect parameter. This affects other web sites in the same domain.",
            "cve": "CVE-2019-7313",
            "id": "pyup.io-36865",
            "more_info_path": "/vulnerabilities/CVE-2019-7313/36865",
            "specs": [
                "<1.8.1"
            ],
            "v": "<1.8.1"
        },
        {
            "advisory": "Buildbot 1.8.2 and 2.3.1 fix a vulnerability in OAuth where a user-submitted authorization token was used for authentication. See: .",
            "cve": "CVE-2019-12300",
            "id": "pyup.io-37160",
            "more_info_path": "/vulnerabilities/CVE-2019-12300/37160",
            "specs": [
                "<1.8.2",
                ">=2.0.0,<2.3.1"
            ],
            "v": "<1.8.2,>=2.0.0,<2.3.1"
        },
        {
            "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in Buildbot 0.7.6 through 0.7.11p2 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, different vulnerabilities than CVE-2009-2959.",
            "cve": "CVE-2009-2967",
            "id": "pyup.io-54043",
            "more_info_path": "/vulnerabilities/CVE-2009-2967/54043",
            "specs": [
                ">=0.7.6,<0.7.12"
            ],
            "v": ">=0.7.6,<0.7.12"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in the waterfall web status view (status/web/waterfall.py) in Buildbot 0.7.6 through 0.7.11p1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.",
            "cve": "CVE-2009-2959",
            "id": "pyup.io-54042",
            "more_info_path": "/vulnerabilities/CVE-2009-2959/54042",
            "specs": [
                ">=0.7.6,<0.7.12"
            ],
            "v": ">=0.7.6,<0.7.12"
        }
    ],
    "buildstream": [
        {
            "advisory": "BuildStream affected versions are vulnerable to race conditions (CWE-362) due to unsynchronized access to the __dynamic_public attribute in element.py. This vulnerability can lead to data corruption or inconsistent application states when multiple threads access or modify __dynamic_public concurrently.",
            "cve": "PVE-2024-74558",
            "id": "pyup.io-74558",
            "more_info_path": "/vulnerabilities/PVE-2024-74558/74558",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        }
    ],
    "bullmq": [
        {
            "advisory": "Bullmq 1.14.1 addresses a race condition identified in job finish queue events. It previously led to potential data inconsistencies within the queue management system, especially under heavy load with concurrent job processing. \r\nhttps://github.com/taskforcesh/bullmq/commit/355bca5ee128bf4ff37608746f9c6f7cca580eb0",
            "cve": "PVE-2024-63935",
            "id": "pyup.io-63935",
            "more_info_path": "/vulnerabilities/PVE-2024-63935/63935",
            "specs": [
                "<1.14.1"
            ],
            "v": "<1.14.1"
        },
        {
            "advisory": "Bullmq 5.1.3 upgrades its msgpackr dependency to version ^1.10.1 from the earlier ^1.6.2, in response to the security vulnerability identified as CVE-2023-52079. \r\nhttps://github.com/taskforcesh/bullmq/commit/7ae095357fddbdaacc286cbe5782946b95160d55",
            "cve": "CVE-2023-52079",
            "id": "pyup.io-64213",
            "more_info_path": "/vulnerabilities/CVE-2023-52079/64213",
            "specs": [
                "<5.1.3"
            ],
            "v": "<5.1.3"
        }
    ],
    "bumblebee-status": [
        {
            "advisory": "Bumblebee-status 2.1.6 fixes insecure use of tempfile in modules/rss.\r\nhttps://github.com/tobi-wan-kenobi/bumblebee-status/commit/4f9553f7ea4ca9d9166980384669c451b74cd019",
            "cve": "PVE-2022-51108",
            "id": "pyup.io-51108",
            "more_info_path": "/vulnerabilities/PVE-2022-51108/51108",
            "specs": [
                "<2.1.6"
            ],
            "v": "<2.1.6"
        }
    ],
    "burl": [
        {
            "advisory": "Burl 2.0.0 workswith JWT tokens more securely.\r\nhttps://github.com/wryfi/burl/commit/664878ce9a31695456be89c8e10e8bb612074ef6",
            "cve": "PVE-2022-46419",
            "id": "pyup.io-46419",
            "more_info_path": "/vulnerabilities/PVE-2022-46419/46419",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Burl 2.0.0 updates its dependency 'django' to v2.2.25 to include security fixes.",
            "cve": "CVE-2021-33571",
            "id": "pyup.io-46497",
            "more_info_path": "/vulnerabilities/CVE-2021-33571/46497",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Burl 2.0.0 updates its dependency 'django' to v2.2.25 to include security fixes.",
            "cve": "CVE-2021-44420",
            "id": "pyup.io-46495",
            "more_info_path": "/vulnerabilities/CVE-2021-44420/46495",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Burl 2.0.0 updates its dependency 'django' to v2.2.25 to include security fixes.",
            "cve": "CVE-2021-33203",
            "id": "pyup.io-46496",
            "more_info_path": "/vulnerabilities/CVE-2021-33203/46496",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Burl 2.0.0 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-46494",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/46494",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        }
    ],
    "bustapi": [
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal and Unauthorized File Access. The static file serving functionality fails to validate requested file paths and block hidden files, leading to attackers being able to access sensitive files outside the intended directory through path traversal sequences and read configuration files or secrets stored in hidden files like .env or .git/config.",
            "cve": "PVE-2025-82459",
            "id": "pyup.io-82459",
            "more_info_path": "/vulnerabilities/PVE-2025-82459/82459",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Cross-Origin Resource Sharing (CORS) bypass. The application fails to implement CORS restrictions, leading to unauthorized cross-origin requests from malicious websites that can access sensitive user data or perform actions on behalf of authenticated users.",
            "cve": "PVE-2025-82475",
            "id": "pyup.io-82475",
            "more_info_path": "/vulnerabilities/PVE-2025-82475/82475",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "buttplug": [
        {
            "advisory": "Buttplug 0.2.1 updates its dependency 'websockets' to v10.1 to include a security fix.",
            "cve": "PVE-2022-50473",
            "id": "pyup.io-50468",
            "more_info_path": "/vulnerabilities/PVE-2022-50473/50468",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "byarse": [
        {
            "advisory": "Byarse 1.1.0 introduces 'Safe mode', which can be enabled to prevent unpickling Pickle type during deserialization. This prevents a big security vulnerability.",
            "cve": "PVE-2021-38754",
            "id": "pyup.io-38754",
            "more_info_path": "/vulnerabilities/PVE-2021-38754/38754",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "bzfs": [
        {
            "advisory": "Affected versions of Bzfs are vulnerable to Insecure Directory Permissions. Several functionalities use `os.makedirs()` to create temporary directories, which fails to set a restrictive umask, leading to overly permissive access controls that may allow unauthorized users to read or modify sensitive files.",
            "cve": "PVE-2025-81379",
            "id": "pyup.io-81379",
            "more_info_path": "/vulnerabilities/PVE-2025-81379/81379",
            "specs": [
                "<1.14.0"
            ],
            "v": "<1.14.0"
        },
        {
            "advisory": "Affected versions of Bzfs are vulnerable to Information Disclosure. The `--log-config-file` and `--log-config-var ` CLI options fail to restrict access to sensitive configuration data, leading to potential exposure of confidential information through log files.",
            "cve": "PVE-2025-81359",
            "id": "pyup.io-81359",
            "more_info_path": "/vulnerabilities/PVE-2025-81359/81359",
            "specs": [
                "<1.14.0"
            ],
            "v": "<1.14.0"
        }
    ],
    "bzip": [
        {
            "advisory": "bzip  is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/",
            "cve": "PVE-2021-34980",
            "id": "pyup.io-34980",
            "more_info_path": "/vulnerabilities/PVE-2021-34980/34980",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "bzip3": [
        {
            "advisory": "Bzip3 (python client) 0.1.2 includes bzip3 core version 1.3.0, that fixes a buffer overflow vulnerability in libsais.\r\nhttps://github.com/kspalaiologos/bzip3/commit/bfa5bf82b53715dfedf048e5859a46cf248668ff",
            "cve": "PVE-2023-58746",
            "id": "pyup.io-58746",
            "more_info_path": "/vulnerabilities/PVE-2023-58746/58746",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        },
        {
            "advisory": "Bzip3 (python client) 0.1.2 includes bzip3 core version 1.3.0, that fixes an overflow in bz3_decode_block.\r\nhttps://github.com/kspalaiologos/bzip3/commit/33b1951f153c3c5dc8ed736b9110437e1a619b7d",
            "cve": "PVE-2023-58750",
            "id": "pyup.io-58750",
            "more_info_path": "/vulnerabilities/PVE-2023-58750/58750",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "bzt": [
        {
            "advisory": "Bzt 1.16.2 updates its dependency 'jmeter' to v5.4.2 to include security fixes.\r\nhttps://github.com/Blazemeter/taurus/commit/f7fb13fed9ca4f871a3426c3c26fb3e86beb329a",
            "cve": "CVE-2021-44228",
            "id": "pyup.io-43430",
            "more_info_path": "/vulnerabilities/CVE-2021-44228/43430",
            "specs": [
                "<1.16.2"
            ],
            "v": "<1.16.2"
        },
        {
            "advisory": "Bzt 1.16.2 updates its dependency 'jmeter' to v5.4.2 to include security fixes.\r\nhttps://github.com/Blazemeter/taurus/commit/f7fb13fed9ca4f871a3426c3c26fb3e86beb329a",
            "cve": "CVE-2021-45046",
            "id": "pyup.io-43431",
            "more_info_path": "/vulnerabilities/CVE-2021-45046/43431",
            "specs": [
                "<1.16.2"
            ],
            "v": "<1.16.2"
        },
        {
            "advisory": "Bzt 1.16.4 updates its MAVEN dependency 'jmeter' to v5.4.3 to fix a log4j related vulnerability.\r\nhttps://github.com/Blazemeter/taurus/pull/1641/commits/12e7bae57abdc8eec75e01565cd92d654f062f70",
            "cve": "CVE-2021-45105",
            "id": "pyup.io-43435",
            "more_info_path": "/vulnerabilities/CVE-2021-45105/43435",
            "specs": [
                "<1.16.4"
            ],
            "v": "<1.16.4"
        },
        {
            "advisory": "Bzt 1.16.8 and prior includes a version of 'jmeter' (5.4.3) affected by a medium severity vulnerability.",
            "cve": "CVE-2021-44832",
            "id": "pyup.io-44454",
            "more_info_path": "/vulnerabilities/CVE-2021-44832/44454",
            "specs": [
                "<=1.16.8"
            ],
            "v": "<=1.16.8"
        }
    ],
    "c2cciutils": [
        {
            "advisory": "C2cciutils 1.6.0 updates its 'requests' dependency to v2.31.0 to address CVE-2023-32681.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-62110",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/62110",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        }
    ],
    "c2cgeoform": [
        {
            "advisory": "C2cgeoform 2.1.26 fixes a security issue where attachments could be directly opened in the browser, posing a risk of script execution from malicious files. This update forces attachments to be downloaded, preventing automatic execution and enhancing security. \r\nhttps://github.com/camptocamp/c2cgeoform/pull/236/commits/b4452ff1dadd2f3d45bec8bff6dbe34094ecdb93",
            "cve": "PVE-2024-63692",
            "id": "pyup.io-63692",
            "more_info_path": "/vulnerabilities/PVE-2024-63692/63692",
            "specs": [
                "<2.1.26"
            ],
            "v": "<2.1.26"
        }
    ],
    "c2cwsgiutils": [
        {
            "advisory": "C2cwsgiutils 4.0.0 updates its dependency 'pipenv' to v2020.5.28 to include security fixes.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-53015",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/53015",
            "specs": [
                "<4.0.0"
            ],
            "v": "<4.0.0"
        },
        {
            "advisory": "C2cwsgiutils 4.0.0 updates its dependency 'pipenv' to v2020.5.28 to include security fixes.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-53059",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/53059",
            "specs": [
                "<4.0.0"
            ],
            "v": "<4.0.0"
        },
        {
            "advisory": "C2cwsgiutils 4.0.0 updates its dependency 'pipenv' to v2020.5.28 to include security fixes.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-53060",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/53060",
            "specs": [
                "<4.0.0"
            ],
            "v": "<4.0.0"
        },
        {
            "advisory": "C2cwsgiutils 4.1.2 updates its dependency 'mako' to v1.2.2 to include a security fix.",
            "cve": "CVE-2022-40023",
            "id": "pyup.io-53014",
            "more_info_path": "/vulnerabilities/CVE-2022-40023/53014",
            "specs": [
                "<4.1.2"
            ],
            "v": "<4.1.2"
        },
        {
            "advisory": "C2cwsgiutils 4.1.2 updates its dependency 'lxml' to v4.6.3 to include a security fix.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-53061",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/53061",
            "specs": [
                "<4.1.2"
            ],
            "v": "<4.1.2"
        }
    ],
    "cabot": [
        {
            "advisory": "In September 2020 it was reported that all versions of the cabot package are vulnerable to Cross-site Scripting (XSS) via the Endpoint column. The latest release of cabot at that date was version 0.11.7.",
            "cve": "CVE-2020-7734",
            "id": "pyup.io-38806",
            "more_info_path": "/vulnerabilities/CVE-2020-7734/38806",
            "specs": [
                "<=0.11.7"
            ],
            "v": "<=0.11.7"
        },
        {
            "advisory": "Cross Site Scripting (XSS) vulnerability in Arachnys Cabot 0.11.12 can be exploited via the Address column.",
            "cve": "CVE-2020-25449",
            "id": "pyup.io-54248",
            "more_info_path": "/vulnerabilities/CVE-2020-25449/54248",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "cadwyn": [
        {
            "advisory": "Affected versions of the cadwyn package are vulnerable to Cross-Site Scripting (XSS) due to improper sanitization of user input (the version query parameter) in the /docs endpoint. In particular, the swagger_dashboard and redoc_dashboard methods accept a version from the request without encoding and inject it into the openapi_url, which is passed into get_swagger_ui_html, ultimately placing untrusted content inside a JavaScript string literal in the generated docs page.",
            "cve": "PVE-2025-80382",
            "id": "pyup.io-80382",
            "more_info_path": "/vulnerabilities/PVE-2025-80382/80382",
            "specs": [
                "<5.4.3"
            ],
            "v": "<5.4.3"
        },
        {
            "advisory": "Cadwyn creates production-ready community-driven modern Stripe-like API versioning in FastAPI. In versions 5.4.3 and below, the version parameter of the \"/docs\" endpoint is vulnerable to a Reflected XSS (Cross-Site Scripting) attack. This XSS would notably allow an attacker to execute JavaScript code on a user's session for any application based on Cadwyn via a one-click attack. The vulnerability has been fixed in version 5.4.4.",
            "cve": "CVE-2025-53528",
            "id": "pyup.io-78278",
            "more_info_path": "/vulnerabilities/CVE-2025-53528/78278",
            "specs": [
                "<5.4.3"
            ],
            "v": "<5.4.3"
        }
    ],
    "caffeinated-whale-cli": [
        {
            "advisory": "Affected versions of this package are vulnerable to Information Disclosure via Insecure File Permissions. The cache directory and database file creation fails to set restrictive permissions, leading to cached credentials and API keys being readable by unauthorized users on the same system.",
            "cve": "PVE-2025-81481",
            "id": "pyup.io-81481",
            "more_info_path": "/vulnerabilities/PVE-2025-81481/81481",
            "specs": [
                "<0.14.0"
            ],
            "v": "<0.14.0"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Command Injection. The unlock command fails to validate and sanitize site names and bench path inputs, leading to arbitrary command execution through the injection of shell metacharacters such as `;`, `&`, `|`, and `$`.",
            "cve": "PVE-2025-81487",
            "id": "pyup.io-81487",
            "more_info_path": "/vulnerabilities/PVE-2025-81487/81487",
            "specs": [
                "<0.14.0"
            ],
            "v": "<0.14.0"
        }
    ],
    "cai-framework": [
        {
            "advisory": "Affected versions of the cai-framework package are vulnerable to Command Injection due to improper neutralization of the host, username, and port parameters in the run_ssh_command_with_credentials function tool. The run_ssh_command_with_credentials tool constructs an sshpass shell command string and escapes only the password and command arguments, leaving host, username, and port directly interpolated into the shell command passed to run_command, which allows shell metacharacters in these fields to alter the executed command.",
            "cve": "CVE-2025-67511",
            "id": "pyup.io-82495",
            "more_info_path": "/vulnerabilities/CVE-2025-67511/82495",
            "specs": [
                "<=0.5.9"
            ],
            "v": "<=0.5.9"
        }
    ],
    "caikit": [
        {
            "advisory": "Caikit 0.20.4 updates its numpy dependency to versions between 1.22.2 and 2 to include a security fix.",
            "cve": "CVE-2021-41495",
            "id": "pyup.io-63311",
            "more_info_path": "/vulnerabilities/CVE-2021-41495/63311",
            "specs": [
                "<0.20.4"
            ],
            "v": "<0.20.4"
        }
    ],
    "cairo-lang": [
        {
            "advisory": "Cairo-lang 0.10.0 fixes a bug in 'uint256_unsigned_div_rem' which allowed a malicious prover to return a wrong result. Contracts using this function or any other function which uses it ('uint256_signed_div_rem' or 'uint256_shr' for the standard library) should be recompiled & redeployed with version >= 0.10.0.",
            "cve": "PVE-2022-50897",
            "id": "pyup.io-50897",
            "more_info_path": "/vulnerabilities/PVE-2022-50897/50897",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Cairo-lang 0.10.0pre fixes a bug in the secp signature verification code that allowed a malicious prover to ignore the value of 'v' (this does not let the prover fake a signature, but allows it to claim that a valid signature is invalid).",
            "cve": "PVE-2022-50898",
            "id": "pyup.io-50898",
            "more_info_path": "/vulnerabilities/PVE-2022-50898/50898",
            "specs": [
                "<0.10.0pre"
            ],
            "v": "<0.10.0pre"
        }
    ],
    "cairo-rs-py": [
        {
            "advisory": "Cairo-rs-py 0.2.0 includes a fix for a potential DoS vulnerability.\r\nhttps://github.com/lambdaclass/cairo-rs-py/issues/216",
            "cve": "PVE-2023-54904",
            "id": "pyup.io-54904",
            "more_info_path": "/vulnerabilities/PVE-2023-54904/54904",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "cairosvg": [
        {
            "advisory": "cairosvg 1.0.21 is a security update. CairoSVG was vulnerable to XML eXternal Entity (XXE) attacks, this release fixes this vulnerability by not resolving the XML entities anymore. The ``--unsafe`` option has been added to force the resolution of XML entities. Obviously, this option is not safe and should only be used with trusted SVG files.",
            "cve": "PVE-2021-25643",
            "id": "pyup.io-25643",
            "more_info_path": "/vulnerabilities/PVE-2021-25643/25643",
            "specs": [
                "<1.0.21"
            ],
            "v": "<1.0.21"
        },
        {
            "advisory": "Cairosvg 2.5.1 includes a fix for CVE-2021-21236: In CairoSVG before version 2.5.1, there is a regular expression denial of service (REDoS) vulnerability. When processing SVG files, the python package CairoSVG uses two regular expressions which are vulnerable to Regular Expression Denial of Service (REDoS). If an attacker provides a malicious SVG, it can make cairosvg get stuck processing the file for a very long time.",
            "cve": "CVE-2021-21236",
            "id": "pyup.io-39419",
            "more_info_path": "/vulnerabilities/CVE-2021-21236/39419",
            "specs": [
                "<2.5.1"
            ],
            "v": "<2.5.1"
        },
        {
            "advisory": "CairosSVG 2.7.0 include a fix for CVE-2023-27586: Prior to version 2.7.0, Cairo can send requests to external hosts when processing SVG files. A malicious actor could send a specially crafted SVG file that allows them to perform a server-side request forgery or denial of service. Version 2.7.0 disables CairoSVG's ability to access other files online by default.",
            "cve": "CVE-2023-27586",
            "id": "pyup.io-53750",
            "more_info_path": "/vulnerabilities/CVE-2023-27586/53750",
            "specs": [
                "<2.7.0"
            ],
            "v": "<2.7.0"
        }
    ],
    "calcwave": [
        {
            "advisory": "Calcwave 1.2.6 updates limits for modules and functions available to 'eval()' in the interpreter. This greatly improves the security and reduces the risk of accidentally calling the 'Python' function that damages your computer.\r\nhttps://github.com/zenarcher007/calcwave/commit/1d95d1861a0bf9954e95f82469f279bb3ba12d9a",
            "cve": "PVE-2021-40507",
            "id": "pyup.io-40507",
            "more_info_path": "/vulnerabilities/PVE-2021-40507/40507",
            "specs": [
                "<1.2.6"
            ],
            "v": "<1.2.6"
        }
    ],
    "calendar-view": [
        {
            "advisory": "Calendar-view 2.4.0 updates its dependency 'pillow' to include a security fix.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61595",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61595",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Calendar-view 2.4.1 upgrades its dependency on the Pillow library from version 10.0.1 to version 10.2.0. This upgrade addresses the security vulnerability identified as CVE-2023-50447.\r\nhttps://github.com/sakhnevych/calendar-view/commit/834402a42591352670bf4592e706da580a19abac",
            "cve": "CVE-2023-50447",
            "id": "pyup.io-64536",
            "more_info_path": "/vulnerabilities/CVE-2023-50447/64536",
            "specs": [
                "<2.4.1"
            ],
            "v": "<2.4.1"
        },
        {
            "advisory": "Calendar-view 2.4.2 has upgraded its Pillow dependency from version 10.2.0 to 10.3.0 to address the security issue identified in CVE-2024-28219.",
            "cve": "CVE-2024-28219",
            "id": "pyup.io-67927",
            "more_info_path": "/vulnerabilities/CVE-2024-28219/67927",
            "specs": [
                "<2.4.2"
            ],
            "v": "<2.4.2"
        }
    ],
    "calibreweb": [
        {
            "advisory": "Affected versions of cps in calibre-web are vulnerable to Generation of Error Message Containing Sensitive Information (CWE-209). This vulnerability allows attackers to obtain the names of private shelves through error messages when attempting unauthorized actions such as adding or removing books. The attack vector involves triggering these actions, resulting in logs or user-facing flash messages that include shelf.name in shelf.py. To mitigate, upgrade to the version that removes the exposure of shelf names from error messages, thereby preventing information leakage.",
            "cve": "CVE-2021-3986",
            "id": "pyup.io-74254",
            "more_info_path": "/vulnerabilities/CVE-2021-3986/74254",
            "specs": [
                "<0.6.15"
            ],
            "v": "<0.6.15"
        },
        {
            "advisory": "Affected versions of calibre-web are vulnerable to Missing Authorization (CWE-862). This vulnerability allows unauthorized users to create public shelves, potentially leading to unauthorized data exposure or manipulation. The attack vector involves exploiting the create_shelf method in shelf.py, which fails to verify user permissions before allowing shelf creation. This lack of proper access control enables attackers to perform actions beyond their intended privileges. To mitigate, upgrade to the version that implements proper permission checks in the create_shelf method, ensuring only authorized users can create public shelves.",
            "cve": "CVE-2021-3987",
            "id": "pyup.io-74255",
            "more_info_path": "/vulnerabilities/CVE-2021-3987/74255",
            "specs": [
                "<0.6.15"
            ],
            "v": "<0.6.15"
        },
        {
            "advisory": "Affected versions of cps in calibre-web are vulnerable to Cross-Site Scripting (CWE-79). This vulnerability allows attackers to inject malicious scripts through upload filename fields by exploiting the use of the .html() method to display filenames, potentially compromising user sessions or executing unauthorized actions. The attack vector involves uploading filenames containing malicious HTML or JavaScript, which are rendered unsafely in the DOM. The vulnerable methods include jQuery\u2019s .html() in edit_books.js. To mitigate, upgrade to the version which replaces .html() with .text(), ensuring safe rendering of filenames.",
            "cve": "CVE-2021-3988",
            "id": "pyup.io-74257",
            "more_info_path": "/vulnerabilities/CVE-2021-3988/74257",
            "specs": [
                "<0.6.15"
            ],
            "v": "<0.6.15"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to Improper Authorization.",
            "cve": "CVE-2022-0406",
            "id": "pyup.io-62587",
            "more_info_path": "/vulnerabilities/CVE-2022-0406/62587",
            "specs": [
                "<0.6.16"
            ],
            "v": "<0.6.16"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to Improper Access Control.",
            "cve": "CVE-2022-0405",
            "id": "pyup.io-62586",
            "more_info_path": "/vulnerabilities/CVE-2022-0405/62586",
            "specs": [
                "<0.6.16"
            ],
            "v": "<0.6.16"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to Server-Side Request Forgery (SSRF).",
            "cve": "CVE-2022-0939",
            "id": "pyup.io-62588",
            "more_info_path": "/vulnerabilities/CVE-2022-0939/62588",
            "specs": [
                "<0.6.18"
            ],
            "v": "<0.6.18"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to Server-Side Request Forgery (SSRF).",
            "cve": "CVE-2022-0990",
            "id": "pyup.io-62589",
            "more_info_path": "/vulnerabilities/CVE-2022-0990/62589",
            "specs": [
                "<0.6.18"
            ],
            "v": "<0.6.18"
        },
        {
            "advisory": "Affected versions of Calibrewebare are vulnerable to Weak Password Requirements.",
            "cve": "CVE-2023-2106",
            "id": "pyup.io-62874",
            "more_info_path": "/vulnerabilities/CVE-2023-2106/62874",
            "specs": [
                "<0.6.20"
            ],
            "v": "<0.6.20"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to Improper Restriction of Excessive Authentication Attempts.",
            "cve": "CVE-2022-2525",
            "id": "pyup.io-62623",
            "more_info_path": "/vulnerabilities/CVE-2022-2525/62623",
            "specs": [
                "<0.6.20"
            ],
            "v": "<0.6.20"
        },
        {
            "advisory": "Affected versions of calibreweb are vulnerable to sensitive information disclosure. There was a hardcoded secret key that could lead to authentication bypass.",
            "cve": "CVE-2020-12627",
            "id": "pyup.io-42274",
            "more_info_path": "/vulnerabilities/CVE-2020-12627/42274",
            "specs": [
                "<0.6.7"
            ],
            "v": "<0.6.7"
        },
        {
            "advisory": "ReDoS in strip_whitespaces() function in cps/string_helper.py in Calibre Web and Autocaliweb allows unauthenticated remote attackers to cause denial of service via specially crafted username parameter that triggers catastrophic backtracking during login. This issue affects Calibre Web: 0.6.24 (Nicolette); Autocaliweb: from 0.7.0 before 0.7.1.",
            "cve": "CVE-2025-6998",
            "id": "pyup.io-78517",
            "more_info_path": "/vulnerabilities/CVE-2025-6998/78517",
            "specs": [
                "<=0.6.24"
            ],
            "v": "<=0.6.24"
        },
        {
            "advisory": "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Calibre Web, Autocaliweb allows Blind OS Command Injection.This issue affects Calibre Web: 0.6.24 (Nicolette); Autocaliweb: from 0.7.0 before 0.7.1.",
            "cve": "CVE-2025-7404",
            "id": "pyup.io-78518",
            "more_info_path": "/vulnerabilities/CVE-2025-7404/78518",
            "specs": [
                "<=0.6.24"
            ],
            "v": "<=0.6.24"
        },
        {
            "advisory": "Affected versions of the calibreweb package are vulnerable to Stored Cross-Site Scripting (XSS) due to improper sanitization of the username field during user creation. In calibreweb versions up to and including 0.6.25, the user creation logic accepts attacker-controlled HTML/JavaScript in the username parameter, stores it without encoding, and the /ajax/listusers endpoint later reflects this stored value directly into the user list response, where it is rendered in the browser.",
            "cve": "CVE-2025-65858",
            "id": "pyup.io-82195",
            "more_info_path": "/vulnerabilities/CVE-2025-65858/82195",
            "specs": [
                "<=0.6.25"
            ],
            "v": "<=0.6.25"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to Cross-Site Request Forgery (CSRF).",
            "cve": "CVE-2021-4164",
            "id": "pyup.io-54147",
            "more_info_path": "/vulnerabilities/CVE-2021-4164/54147",
            "specs": [
                ">=0,<0.6.15"
            ],
            "v": ">=0,<0.6.15"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to Business Logic Errors.\r\nAffected functions: calibreweb.cps.shelf.check_shelf_is_unique, calibreweb.cps.shelf.create_edit_shelf.",
            "cve": "CVE-2021-4171",
            "id": "pyup.io-54146",
            "more_info_path": "/vulnerabilities/CVE-2021-4171/54146",
            "specs": [
                ">=0,<0.6.15"
            ],
            "v": ">=0,<0.6.15"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').",
            "cve": "CVE-2021-4170",
            "id": "pyup.io-54406",
            "more_info_path": "/vulnerabilities/CVE-2021-4170/54406",
            "specs": [
                ">=0,<0.6.15"
            ],
            "v": ">=0,<0.6.15"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable Incorrect Authorization.",
            "cve": "CVE-2022-0273",
            "id": "pyup.io-54235",
            "more_info_path": "/vulnerabilities/CVE-2022-0273/54235",
            "specs": [
                ">=0,<0.6.16"
            ],
            "v": ">=0,<0.6.16"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to server-side request forgery (SSRF).",
            "cve": "CVE-2022-0339",
            "id": "pyup.io-54237",
            "more_info_path": "/vulnerabilities/CVE-2022-0339/54237",
            "specs": [
                ">=0,<0.6.16"
            ],
            "v": ">=0,<0.6.16"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to cross-site scripting (XSS).",
            "cve": "CVE-2022-0352",
            "id": "pyup.io-54416",
            "more_info_path": "/vulnerabilities/CVE-2022-0352/54416",
            "specs": [
                ">=0,<0.6.16"
            ],
            "v": ">=0,<0.6.16"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to server-side request forgery (SSRF). This is due to an incomplete fix for CVE-2022-0339. The blacklist does not check for `0.0.0.0`, which would result in a payload of `0.0.0.0` resolving to `localhost`.\r\nAffected functions: calibreweb.cps.helper.save_cover_from_url.",
            "cve": "CVE-2022-0766",
            "id": "pyup.io-54414",
            "more_info_path": "/vulnerabilities/CVE-2022-0766/54414",
            "specs": [
                ">=0,<0.6.17"
            ],
            "v": ">=0,<0.6.17"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to server-side request forgery (SSRF). This is a result of incomplete SSRF protection that can be bypassed via an HTTP redirect. An HTTP server set up to respond with a 302 redirect may redirect a request to `localhost`.\r\nAffected functions:calibreweb.cps.helper.save_cover_from_url.",
            "cve": "CVE-2022-0767",
            "id": "pyup.io-54419",
            "more_info_path": "/vulnerabilities/CVE-2022-0767/54419",
            "specs": [
                ">=0,<0.6.17"
            ],
            "v": ">=0,<0.6.17"
        },
        {
            "advisory": "Affected versions of Calibreweb are vulnerable to SQL Injection in User table.",
            "cve": "CVE-2022-30765",
            "id": "pyup.io-54445",
            "more_info_path": "/vulnerabilities/CVE-2022-30765/54445",
            "specs": [
                ">=0,<0.6.18"
            ],
            "v": ">=0,<0.6.18"
        },
        {
            "advisory": "Calibreweb versions 0.6.0 to 0.6.12 are vulnerable to Stored XSS in \"Metadata\". An attacker that has access to edit the metadata information, can inject JavaScript payload in the description field. When a victim tries to open the file, XSS will be triggered.",
            "cve": "CVE-2021-25964",
            "id": "pyup.io-62667",
            "more_info_path": "/vulnerabilities/CVE-2021-25964/62667",
            "specs": [
                ">=0.6.0,<0.6.12"
            ],
            "v": ">=0.6.0,<0.6.12"
        },
        {
            "advisory": "In Calibre-web, versions 0.6.0 to 0.6.13 are vulnerable to Cross-Site Request Forgery (CSRF). By luring an authenticated user to click on a link, an attacker can create a new user role with admin privileges and attacker-controlled credentials, allowing them to take over the application.",
            "cve": "CVE-2021-25965",
            "id": "pyup.io-62672",
            "more_info_path": "/vulnerabilities/CVE-2021-25965/62672",
            "specs": [
                ">=0.6.0,<=0.6.13"
            ],
            "v": ">=0.6.0,<=0.6.13"
        },
        {
            "advisory": "In janeczku Calibre-Web affectged versions, the edit_book_comments function is vulnerable to Cross Site Scripting (XSS) due to improper sanitization performed by the clean_string function. The vulnerability arises from the way the clean_string function handles HTML sanitization.",
            "cve": "CVE-2024-39123",
            "id": "pyup.io-72283",
            "more_info_path": "/vulnerabilities/CVE-2024-39123/72283",
            "specs": [
                ">=0.6.0,<=0.6.21"
            ],
            "v": ">=0.6.0,<=0.6.21"
        }
    ],
    "callisto-core": [
        {
            "advisory": "Callisto-core 0.19.0 stops showing locals on travis.\r\nhttps://github.com/project-callisto/callisto-core/commit/0791639280dfbe742536bf9f29d3eb888d6951e9",
            "cve": "PVE-2019-45606",
            "id": "pyup.io-45606",
            "more_info_path": "/vulnerabilities/PVE-2019-45606/45606",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        },
        {
            "advisory": "Callisto-core 0.26.0 removes models that contain insecure contact information.\r\nhttps://github.com/project-callisto/callisto-core/pull/453",
            "cve": "PVE-2019-47052",
            "id": "pyup.io-47052",
            "more_info_path": "/vulnerabilities/PVE-2019-47052/47052",
            "specs": [
                "<0.26.0"
            ],
            "v": "<0.26.0"
        }
    ],
    "callosum": [
        {
            "advisory": "Callosum 0.9.4 includes a fix for a potential race condition vulnerability.\r\nhttps://github.com/lablup/callosum/pull/12",
            "cve": "PVE-2023-61189",
            "id": "pyup.io-61189",
            "more_info_path": "/vulnerabilities/PVE-2023-61189/61189",
            "specs": [
                "<0.9.4"
            ],
            "v": "<0.9.4"
        }
    ],
    "camel-ai": [
        {
            "advisory": "Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF). The websocket-server.js WebSocket browser toolkit fails to restrict CDP (Chrome DevTools Protocol) URLs to localhost addresses before fetching, leading to attackers being able to make the server connect to arbitrary internal or external hosts by providing malicious CDP URLs, enabling access to internal services and potential credential disclosure.",
            "cve": "PVE-2026-84186",
            "id": "pyup.io-84186",
            "more_info_path": "/vulnerabilities/PVE-2026-84186/84186",
            "specs": [
                "<0.2.83a4"
            ],
            "v": "<0.2.83a4"
        }
    ],
    "camply": [
        {
            "advisory": "Camply 0.24.1 updates its dependency 'requests' to v2.31.0 to include a security fix.\r\nhttps://github.com/juftin/camply/commit/4c6d371",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-58928",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/58928",
            "specs": [
                "<0.24.1"
            ],
            "v": "<0.24.1"
        },
        {
            "advisory": "Camply 0.24.1 updates its dependency 'pymdown-extensions' to v10.0.1 to include a security fix.\r\nhttps://github.com/juftin/camply/commit/4c6d371",
            "cve": "CVE-2023-32309",
            "id": "pyup.io-58938",
            "more_info_path": "/vulnerabilities/CVE-2023-32309/58938",
            "specs": [
                "<0.24.1"
            ],
            "v": "<0.24.1"
        }
    ],
    "canada-holiday": [
        {
            "advisory": "Canada-holiday 1.1.4 upgrades its black dependency to version 24.3.0, addressing the ReDoS vulnerability identified in CVE-2024-21503.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-67444",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/67444",
            "specs": [
                "<1.1.4"
            ],
            "v": "<1.1.4"
        },
        {
            "advisory": "Canada-holiday 1.1.5 updates its dependency 'setuptools' from 69.2.0 to 70.0.0 to include a security fix.",
            "cve": "CVE-2024-6345",
            "id": "pyup.io-74346",
            "more_info_path": "/vulnerabilities/CVE-2024-6345/74346",
            "specs": [
                "<1.1.5"
            ],
            "v": "<1.1.5"
        }
    ],
    "candig-server": [
        {
            "advisory": "Candig-server 0.9.0 has enhanced security through a refined data access control mechanism.",
            "cve": "PVE-2021-37219",
            "id": "pyup.io-37219",
            "more_info_path": "/vulnerabilities/PVE-2021-37219/37219",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Candig-server 0.9.2 updates its dependency 'Jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-37218",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/37218",
            "specs": [
                "<0.9.2"
            ],
            "v": "<0.9.2"
        },
        {
            "advisory": "Candig-server 1.0.2 updates 'WerkZeug' to v0.15.5 to include security fixes.",
            "cve": "CVE-2019-14806",
            "id": "pyup.io-37467",
            "more_info_path": "/vulnerabilities/CVE-2019-14806/37467",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        },
        {
            "advisory": "Candig-server 1.4.0 drops its dependency 'cryptography==2.8' to avoid security issues.",
            "cve": "CVE-2020-25659",
            "id": "pyup.io-48387",
            "more_info_path": "/vulnerabilities/CVE-2020-25659/48387",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Candig-server 1.4.0 drops its dependency 'cryptography==2.8' to avoid security issues.",
            "cve": "CVE-2020-36242",
            "id": "pyup.io-39169",
            "more_info_path": "/vulnerabilities/CVE-2020-36242/39169",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        }
    ],
    "canto-curses": [
        {
            "advisory": "canto_curses/guibase.py in Canto Curses before 0.9.0 allows remote feed servers to execute arbitrary commands via shell metacharacters in a URL in a feed.",
            "cve": "CVE-2013-7416",
            "id": "pyup.io-67960",
            "more_info_path": "/vulnerabilities/CVE-2013-7416/67960",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        }
    ],
    "canvaslms": [
        {
            "advisory": "Canvaslms 2.18 updates its dependency 'pygments' to version '2.15.1' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/dbosk/canvaslms/pull/100",
            "cve": "CVE-2022-40896",
            "id": "pyup.io-60121",
            "more_info_path": "/vulnerabilities/CVE-2022-40896/60121",
            "specs": [
                "<2.18"
            ],
            "v": "<2.18"
        },
        {
            "advisory": "Canvaslms 2.18 updates its dependency 'cryptography' to version '41.0.2' to include a fix for an Improper Certificate Validation vulnerability.\r\nhttps://github.com/dbosk/canvaslms/pull/100",
            "cve": "CVE-2023-38325",
            "id": "pyup.io-60120",
            "more_info_path": "/vulnerabilities/CVE-2023-38325/60120",
            "specs": [
                "<2.18"
            ],
            "v": "<2.18"
        },
        {
            "advisory": "Canvaslms 2.18 updates its dependency 'certifi' to version '2023.7.22' to include a fix for a vulnerability.\r\nhttps://github.com/dbosk/canvaslms/pull/100",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60108",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60108",
            "specs": [
                "<2.18"
            ],
            "v": "<2.18"
        }
    ],
    "capice": [
        {
            "advisory": "Capice 3.1.2 updates its dependency 'numpy' to v1.22.0 to include security fixes.",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-49716",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/49716",
            "specs": [
                "<3.1.2"
            ],
            "v": "<3.1.2"
        },
        {
            "advisory": "Capice 3.1.2 updates its dependency 'numpy' to v1.22.0 to include security fixes.",
            "cve": "CVE-2021-41496",
            "id": "pyup.io-49677",
            "more_info_path": "/vulnerabilities/CVE-2021-41496/49677",
            "specs": [
                "<3.1.2"
            ],
            "v": "<3.1.2"
        }
    ],
    "capirca": [
        {
            "advisory": "Capirca 2.0.9 fixes an arbitrary file read vulnerability.\r\nhttps://github.com/google/capirca/commit/78f8e7cf7e4c515fb1696621bf6c6e95faa85d5b",
            "cve": "PVE-2023-53374",
            "id": "pyup.io-53374",
            "more_info_path": "/vulnerabilities/PVE-2023-53374/53374",
            "specs": [
                "<2.0.9"
            ],
            "v": "<2.0.9"
        }
    ],
    "capstone": [
        {
            "advisory": "Affected versions of Capstone are potentially vulnerable to buffer overflow.",
            "cve": "PVE-2024-73501",
            "id": "pyup.io-73501",
            "more_info_path": "/vulnerabilities/PVE-2024-73501/73501",
            "specs": [
                "<6.0.0alpha1"
            ],
            "v": "<6.0.0alpha1"
        }
    ],
    "captchaboy": [
        {
            "advisory": "Captchaboy is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html",
            "cve": "PVE-2023-52921",
            "id": "pyup.io-52921",
            "more_info_path": "/vulnerabilities/PVE-2023-52921/52921",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "capycli": [
        {
            "advisory": "Capycli 2.4.0 updates its dependency 'idna' to v3.7 to include a security fix.",
            "cve": "CVE-2024-3651",
            "id": "pyup.io-68074",
            "more_info_path": "/vulnerabilities/CVE-2024-3651/68074",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        }
    ],
    "carla": [
        {
            "advisory": "Carla 0.9.11 includes a fix for a potential race condition vulnerability: Sorts vehicles by ID to avoid race condition in Traffic Manager.\r\nhttps://github.com/carla-simulator/carla/pull/3438",
            "cve": "PVE-2023-62323",
            "id": "pyup.io-62323",
            "more_info_path": "/vulnerabilities/PVE-2023-62323/62323",
            "specs": [
                "<0.9.11"
            ],
            "v": "<0.9.11"
        },
        {
            "advisory": "Carla 0.9.9 adds security features to the standalone OpenDRIVE mode aiming to prevent cars from falling down from the road.\r\nhttps://github.com/carla-simulator/carla/pull/2678/commits/35032c7ed47a30211869bbd2c7731215bc37b4e1",
            "cve": "PVE-2021-42713",
            "id": "pyup.io-42713",
            "more_info_path": "/vulnerabilities/PVE-2021-42713/42713",
            "specs": [
                "<0.9.9"
            ],
            "v": "<0.9.9"
        }
    ],
    "cartridge": [
        {
            "advisory": "Cartridge 0.1.1 adds 'csrf_token' to forms.\r\nhttps://github.com/stephenmcd/cartridge/commit/c8211d7a0696ccb6637dbde64375a58ed7d81e16",
            "cve": "PVE-2022-47758",
            "id": "pyup.io-47758",
            "more_info_path": "/vulnerabilities/PVE-2022-47758/47758",
            "specs": [
                "<0.1.1"
            ],
            "v": "<0.1.1"
        }
    ],
    "cartridge-braintree": [
        {
            "advisory": "Cartridge-braintree 1.2.2 updates its dependency 'Django' to v1.11.29 to include security fixes.",
            "cve": "CVE-2020-7471",
            "id": "pyup.io-40229",
            "more_info_path": "/vulnerabilities/CVE-2020-7471/40229",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Cartridge-braintree 1.2.2 updates its dependency 'Django' to v1.11.29 to include security fixes.",
            "cve": "CVE-2020-9402",
            "id": "pyup.io-49479",
            "more_info_path": "/vulnerabilities/CVE-2020-9402/49479",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        }
    ],
    "cascadev": [
        {
            "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'deepsolid' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.",
            "cve": "PVE-2024-74244",
            "id": "pyup.io-74244",
            "more_info_path": "/vulnerabilities/PVE-2024-74244/74244",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "case-utils": [
        {
            "advisory": "Case-utils is affected by an information leakage vulnerability. The vulnerability stems from a Python function, 'cdo_local_uuid.local_uuid()', and its original implementation 'case_utils.local_uuid()'.\r\nhttps://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/security/advisories/GHSA-rgrf-6mf5-m882",
            "cve": "CVE-2024-22194",
            "id": "pyup.io-64226",
            "more_info_path": "/vulnerabilities/CVE-2024-22194/64226",
            "specs": [
                "==0.5.0",
                "==0.6.0",
                "==0.7.0",
                "==0.8.0",
                "==0.9.0",
                "==0.10.0",
                "==0.11.0",
                "==0.12.0",
                "==0.13.0",
                "==0.14.0"
            ],
            "v": "==0.5.0,==0.6.0,==0.7.0,==0.8.0,==0.9.0,==0.10.0,==0.11.0,==0.12.0,==0.13.0,==0.14.0"
        }
    ],
    "cashocs": [
        {
            "advisory": "Cashocs version 2.0.0 updates its pygments dependency to version 2.7.4 from the previous 2.5.2, addressing the vulnerability identified as CVE-2021-20270.\r\nhttps://github.com/sblauth/cashocs/pull/141/commits/1fb563e91e1b4d564cb4784c7c812bf27c7e15b7",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-64944",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/64944",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Cashocs version 2.0.0 updates its setuptools dependency to version 65.5.1 from the previous 39.0.1, addressing the vulnerability identified as CVE-2022-40897.\r\nhttps://github.com/sblauth/cashocs/pull/137/commits/eb3fdc2bc65c87fb27d3622ada71c4d841a856a2",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-64817",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/64817",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Cashocs version 2.0.0 updates its pygments dependency to version 2.7.4 from the previous 2.5.2, addressing the vulnerability identified as CVE-2021-27291.\r\nhttps://github.com/sblauth/cashocs/pull/141/commits/1fb563e91e1b4d564cb4784c7c812bf27c7e15b7",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-64943",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/64943",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Cashocs version 2.1.0 updates its Pillow dependency to version 10.0.1 from the previous 9.5.0, to mitigate the security vulnerability identified as CVE-2023-4863.\r\nhttps://github.com/sblauth/cashocs/pull/345/commits/86d09b3a5a63e3fbe1a0724fcae54843064bed09",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-64981",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/64981",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Cashocs version 2.1.0 updates its Numpy dependency to 1.22.2 from the earlier version 1.21.3. This upgrade is in response to addressing the security vulnerability designated as CVE-2021-41495.\r\nhttps://github.com/sblauth/cashocs/pull/345",
            "cve": "CVE-2021-41495",
            "id": "pyup.io-64982",
            "more_info_path": "/vulnerabilities/CVE-2021-41495/64982",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Cashocs version 2.1.0 updates its Numpy dependency to 1.22.2 from the earlier version 1.21.3. This upgrade is in response to addressing the security vulnerability designated as CVE-2021-34141.\r\nhttps://github.com/sblauth/cashocs/pull/345",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-64963",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/64963",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Cashocs version 2.1.0 updates its fonttools dependency from version 4.38.0 to 4.43.0 to address the security issue identified as CVE-2023-45139.\r\nhttps://github.com/sblauth/cashocs/pull/372/commits/c15b23e743b3046b8afae8b6a0967044f163c8ce",
            "cve": "CVE-2023-45139",
            "id": "pyup.io-64980",
            "more_info_path": "/vulnerabilities/CVE-2023-45139/64980",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        }
    ],
    "cassandra-medusa": [
        {
            "advisory": "Cassandra-medusa version 0.20.0 upgrades its Pycryptodome dependency to 3.19.1 from the previous version 3.19.0, aiming to address the security concerns outlined in CVE-2023-52323.",
            "cve": "CVE-2023-52323",
            "id": "pyup.io-67422",
            "more_info_path": "/vulnerabilities/CVE-2023-52323/67422",
            "specs": [
                "<0.20.0"
            ],
            "v": "<0.20.0"
        },
        {
            "advisory": "Cassandra-medusa version 0.20.0 has upgraded its Cryptography dependency to version 42.0.2 from 35.0, in response to CVE-2023-6129.",
            "cve": "CVE-2023-6129",
            "id": "pyup.io-67139",
            "more_info_path": "/vulnerabilities/CVE-2023-6129/67139",
            "specs": [
                "<0.20.0"
            ],
            "v": "<0.20.0"
        },
        {
            "advisory": "Cassandra-medusa 0.9.1 fixes MinIO support that had unsecured access.\r\nhttps://github.com/thelastpickle/cassandra-medusa/commit/2edb8afd9e0961fb3cf390322c0f59066967de84",
            "cve": "PVE-2021-42517",
            "id": "pyup.io-42517",
            "more_info_path": "/vulnerabilities/PVE-2021-42517/42517",
            "specs": [
                "<0.9.1"
            ],
            "v": "<0.9.1"
        }
    ],
    "castle-cms": [
        {
            "advisory": "Castle-cms version 2.6.1 includes fixes for secure-login.",
            "cve": "PVE-2021-41903",
            "id": "pyup.io-41903",
            "more_info_path": "/vulnerabilities/PVE-2021-41903/41903",
            "specs": [
                "<2.6.1"
            ],
            "v": "<2.6.1"
        },
        {
            "advisory": "Castle-cms version 2.6.2 fixes default behavior that allowed access to published content inside a private container.",
            "cve": "PVE-2021-41902",
            "id": "pyup.io-41902",
            "more_info_path": "/vulnerabilities/PVE-2021-41902/41902",
            "specs": [
                "<2.6.2"
            ],
            "v": "<2.6.2"
        }
    ],
    "catboost": [
        {
            "advisory": "Catboost 0.26 updates version of 'scala' to v2.11.12 for security reasons.\r\nhttps://github.com/catboost/catboost/issues/1632",
            "cve": "CVE-2017-15288",
            "id": "pyup.io-41743",
            "more_info_path": "/vulnerabilities/CVE-2017-15288/41743",
            "specs": [
                "<0.26"
            ],
            "v": "<0.26"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'webpack' to version '5.76.0' to include a fix for a Sandbox Bypass vulnerability.\r\nhttps://github.com/catboost/catboost/commit/e132d847a527827023eb67165e11f1b05a19564f",
            "cve": "CVE-2023-28154",
            "id": "pyup.io-60751",
            "more_info_path": "/vulnerabilities/CVE-2023-28154/60751",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'json5' to version '3.3.6' to include a fix for a Prototype Pollution vulnerability.\r\nhttps://github.com/catboost/catboost/commit/c6393bf6300ecc6d8bcbd98d61927149cb205100",
            "cve": "CVE-2022-46175",
            "id": "pyup.io-60762",
            "more_info_path": "/vulnerabilities/CVE-2022-46175/60762",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'tenser' to version '5.19.2' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/28aa3945fe8664bfbf0dd1d1cd2e04f6aca398b5",
            "cve": "CVE-2022-25858",
            "id": "pyup.io-60717",
            "more_info_path": "/vulnerabilities/CVE-2022-25858/60717",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'path-parse' to version '1.0.7' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/c5384e8e53f4fee40190dd7d52ec0e1ee92a2560",
            "cve": "CVE-2021-23343",
            "id": "pyup.io-60758",
            "more_info_path": "/vulnerabilities/CVE-2021-23343/60758",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'loader-utils' to version '1.4.2' to include a fix for a Prototype Pollution vulnerability.\r\nhttps://github.com/catboost/catboost/commit/fc169568301a2f20f1329ff0680e4d68dc965485",
            "cve": "CVE-2022-37601",
            "id": "pyup.io-60754",
            "more_info_path": "/vulnerabilities/CVE-2022-37601/60754",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'tar' to version '6.1.15' to include a fix for an Arbitrary File Write vulnerability.\r\nhttps://github.com/catboost/catboost/commit/f54bd997762dede21c31022ae27b7fd5be36c925",
            "cve": "CVE-2021-37712",
            "id": "pyup.io-60747",
            "more_info_path": "/vulnerabilities/CVE-2021-37712/60747",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'semver' to version '5.7.2' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/d0183bfcf67525a3ad9f4427e23f1472ad9f588c",
            "cve": "CVE-2022-25883",
            "id": "pyup.io-60757",
            "more_info_path": "/vulnerabilities/CVE-2022-25883/60757",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'minimatch' to version '3.1.2' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/3b9820e0bfb7b9e34dbaf0403e95e0dcdc9d9ba3",
            "cve": "CVE-2022-3517",
            "id": "pyup.io-60744",
            "more_info_path": "/vulnerabilities/CVE-2022-3517/60744",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'jackson-databind' to version '2.13.4.2' to include a fix for a DoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/e88f390a4e2630c9e8a5b82cd01c053a9fd29795",
            "cve": "CVE-2020-36518",
            "id": "pyup.io-60771",
            "more_info_path": "/vulnerabilities/CVE-2020-36518/60771",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'loader-utils' to version '1.4.2' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/fc169568301a2f20f1329ff0680e4d68dc965485",
            "cve": "CVE-2022-37603",
            "id": "pyup.io-60753",
            "more_info_path": "/vulnerabilities/CVE-2022-37603/60753",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'jackson-databind' to version '2.13.4.2' to include a fix for a DoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/e88f390a4e2630c9e8a5b82cd01c053a9fd29795",
            "cve": "CVE-2022-42003",
            "id": "pyup.io-60769",
            "more_info_path": "/vulnerabilities/CVE-2022-42003/60769",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'minimist' to version '1.2.8' to include a fix for a Prototype Pollution vulnerability.\r\nhttps://github.com/catboost/catboost/commit/63b0cd67faf62ba3fcd7281044dad144f8b6ff4d",
            "cve": "CVE-2021-44906",
            "id": "pyup.io-60755",
            "more_info_path": "/vulnerabilities/CVE-2021-44906/60755",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'normalize-url' to version '4.5.1' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/44e9f5fcf515e7d3d4bc891388e679ff7bceefb9",
            "cve": "CVE-2021-33502",
            "id": "pyup.io-60764",
            "more_info_path": "/vulnerabilities/CVE-2021-33502/60764",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'tar' to version '6.1.15' to include a fix for an Arbitrary File Write vulnerability.\r\nhttps://github.com/catboost/catboost/commit/f54bd997762dede21c31022ae27b7fd5be36c925",
            "cve": "CVE-2021-37713",
            "id": "pyup.io-60748",
            "more_info_path": "/vulnerabilities/CVE-2021-37713/60748",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'tar' to version '6.1.15' to include a fix for an Arbitrary File Write vulnerability.\r\nhttps://github.com/catboost/catboost/commit/f54bd997762dede21c31022ae27b7fd5be36c925",
            "cve": "CVE-2021-37701",
            "id": "pyup.io-60746",
            "more_info_path": "/vulnerabilities/CVE-2021-37701/60746",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'junit:junit' to version '4.13.1' to include a fix for an Information Exposure vulnerability.\r\nhttps://github.com/catboost/catboost/commit/95a9dca46d21133005b3d6d66be165384ba77f2d",
            "cve": "CVE-2020-15250",
            "id": "pyup.io-60765",
            "more_info_path": "/vulnerabilities/CVE-2020-15250/60765",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'browserslist' to version '4.21.9' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/a15bfbbd2ff8d4ea56e57876e2601a6dbd9e4d37",
            "cve": "CVE-2021-23364",
            "id": "pyup.io-60756",
            "more_info_path": "/vulnerabilities/CVE-2021-23364/60756",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'http-cache-semantics' to version '4.1.1' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/d63e29198a2c5a12e7d857b2b068283298488e8d",
            "cve": "CVE-2022-25881",
            "id": "pyup.io-60745",
            "more_info_path": "/vulnerabilities/CVE-2022-25881/60745",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'snappy-java' to version '1.1.10.1' to include a fix for an Integer Overflow vulnerability.\r\nhttps://github.com/catboost/catboost/commit/b51a3b2302a1d6b1a596b406efef347c872d9a0e",
            "cve": "CVE-2023-34454",
            "id": "pyup.io-60766",
            "more_info_path": "/vulnerabilities/CVE-2023-34454/60766",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'postcss' to version '8.4.27' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/8143d912bc7364b488ae5a33e2c83e29b988420f",
            "cve": "CVE-2021-23368",
            "id": "pyup.io-60760",
            "more_info_path": "/vulnerabilities/CVE-2021-23368/60760",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'postcss' to version '8.4.27' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/8143d912bc7364b488ae5a33e2c83e29b988420f",
            "cve": "CVE-2021-23382",
            "id": "pyup.io-60759",
            "more_info_path": "/vulnerabilities/CVE-2021-23382/60759",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'tar' to version '6.1.15' to include a fix for an Arbitrary File Write vulnerability.\r\nhttps://github.com/catboost/catboost/commit/f54bd997762dede21c31022ae27b7fd5be36c925",
            "cve": "CVE-2021-32803",
            "id": "pyup.io-60749",
            "more_info_path": "/vulnerabilities/CVE-2021-32803/60749",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'guava' to version '32.0.0-jre' to include a fix for an Information Disclosure vulnerability.\r\nhttps://github.com/catboost/catboost/commit/cd66946c38a4e2acf9020de5a6f24065c9f16c2d",
            "cve": "CVE-2020-8908",
            "id": "pyup.io-60772",
            "more_info_path": "/vulnerabilities/CVE-2020-8908/60772",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'tar' to version '6.1.15' to include a fix for an Arbitrary File Write vulnerability.\r\nhttps://github.com/catboost/catboost/commit/f54bd997762dede21c31022ae27b7fd5be36c925",
            "cve": "CVE-2021-32804",
            "id": "pyup.io-60750",
            "more_info_path": "/vulnerabilities/CVE-2021-32804/60750",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'nanoid' to version '3.3.6' to include a fix for an Information Exposure vulnerability.\r\nhttps://github.com/catboost/catboost/commit/9381a56a05fc7f2b8cecc323c5b26aa60d3703f0",
            "cve": "CVE-2021-23566",
            "id": "pyup.io-60761",
            "more_info_path": "/vulnerabilities/CVE-2021-23566/60761",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'snappy-java' to version '1.1.10.1' to include a fix for an Integer Overflow vulnerability.\r\nhttps://github.com/catboost/catboost/commit/b51a3b2302a1d6b1a596b406efef347c872d9a0e",
            "cve": "CVE-2023-34453",
            "id": "pyup.io-60768",
            "more_info_path": "/vulnerabilities/CVE-2023-34453/60768",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'snappy-java' to version '1.1.10.1' to include a fix for a DoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/b51a3b2302a1d6b1a596b406efef347c872d9a0e",
            "cve": "CVE-2023-34455",
            "id": "pyup.io-60767",
            "more_info_path": "/vulnerabilities/CVE-2023-34455/60767",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its NPM dependency 'loader-utils' to version '1.4.2' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/fc169568301a2f20f1329ff0680e4d68dc965485",
            "cve": "CVE-2022-37599",
            "id": "pyup.io-60752",
            "more_info_path": "/vulnerabilities/CVE-2022-37599/60752",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'jackson-databind' to version '2.13.4.2' to include a fix for a DoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/e88f390a4e2630c9e8a5b82cd01c053a9fd29795",
            "cve": "CVE-2022-42004",
            "id": "pyup.io-60770",
            "more_info_path": "/vulnerabilities/CVE-2022-42004/60770",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Catboost 1.2.1 updates its dependency 'ansi-regex' to version '5.0.1' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/catboost/catboost/commit/7eebbf8e2fec4d2e3225e819a86c0b14dde72c52",
            "cve": "CVE-2021-3807",
            "id": "pyup.io-60763",
            "more_info_path": "/vulnerabilities/CVE-2021-3807/60763",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        }
    ],
    "catly-translate": [
        {
            "advisory": "The Catly-Translate package in PyPI v0.0.3 to v0.0.5 was discovered to contain a code execution backdoor. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.",
            "cve": "CVE-2022-34061",
            "id": "pyup.io-54425",
            "more_info_path": "/vulnerabilities/CVE-2022-34061/54425",
            "specs": [
                ">=0.0.3,<0.0.6"
            ],
            "v": ">=0.0.3,<0.0.6"
        }
    ],
    "cbapi": [
        {
            "advisory": "The underlying CbAPI connection class erroneously disabled hostname validation by default. This does *not* affect code that uses CbAPI through the public interfaces documented here; it only affects code that accesses the new  ``CbAPISessionAdapter`` class directly. This class was introduced in version 1.3.3. Regardless, it is strongly recommended that all users currently using 1.3.3 upgrade to 1.3.4.",
            "cve": "PVE-2021-34933",
            "id": "pyup.io-34933",
            "more_info_path": "/vulnerabilities/PVE-2021-34933/34933",
            "specs": [
                ">=1.3.3,<1.3.4"
            ],
            "v": ">=1.3.3,<1.3.4"
        }
    ],
    "cbor2": [
        {
            "advisory": "Cbor2 5.4.0 fixes bounds checks in C decoder.\r\nhttps://github.com/agronholm/cbor2/pull/113",
            "cve": "PVE-2023-61961",
            "id": "pyup.io-61961",
            "more_info_path": "/vulnerabilities/PVE-2023-61961/61961",
            "specs": [
                "<5.4.0"
            ],
            "v": "<5.4.0"
        },
        {
            "advisory": "Cbor2 5.6.0 fixes  issue that was causing a MemoryError when decoding large definite strings. It was due to the library attempting to allocate more memory than available, leading to a failure in memory allocation. The fix involves altering how the library manages memory allocation for large strings, thus preventing the MemoryError from being thrown and allowing the library to handle large strings correctly.\r\nhttps://github.com/agronholm/cbor2/commit/387755eacf0be35591a478d3c67fe10618a6d542",
            "cve": "PVE-2024-64281",
            "id": "pyup.io-64281",
            "more_info_path": "/vulnerabilities/PVE-2024-64281/64281",
            "specs": [
                "<5.6.0"
            ],
            "v": "<5.6.0"
        },
        {
            "advisory": "Affected versions of the cbor2 package are vulnerable to Information Disclosure due to the CBORDecoder state being reused without clearing shareable values between decode operations. In cbor2, CBORDecoder.decode_from_bytes() and the CBORDecoder.fp setter (including the C extension _CBORDecoder_set_fp and the pure-Python cbor2/_decoder.py implementation) do not reset the internal shareables list that stores tag 28 (shareable) values for later retrieval via tag 29 (sharedref), allowing those references to persist across separate messages.",
            "cve": "CVE-2025-68131",
            "id": "pyup.io-83720",
            "more_info_path": "/vulnerabilities/CVE-2025-68131/83720",
            "specs": [
                ">=3.0.0,<5.8.0"
            ],
            "v": ">=3.0.0,<5.8.0"
        },
        {
            "advisory": "Affected versions of Cbor2 are vulnerable to Buffer Overflow. An attacker can crash a service using cbor2 to parse a CBOR binary by sending a long enough object.",
            "cve": "CVE-2024-26134",
            "id": "pyup.io-66703",
            "more_info_path": "/vulnerabilities/CVE-2024-26134/66703",
            "specs": [
                ">=5.5.1,<5.6.2"
            ],
            "v": ">=5.5.1,<5.6.2"
        }
    ],
    "cbpi4": [
        {
            "advisory": "Affected versions of the cbpi4 package (CraftBeerPi 4) are vulnerable to Command Injection due to improper validation of the `logtime` GET parameter. The `downloadlog` endpoint in `cbpi/http_endpoints/http_system.py` forwards the unchecked `logtime` parameter into an `os.system` call in `cbpi/controller/system_controller.py`, enabling execution of arbitrary commands. A remote attacker can exploit this by crafting a malicious `logtime` value in a URL request to the `downloadlog` function, causing execution of attacker-controlled commands on the server.",
            "cve": "CVE-2024-3955",
            "id": "pyup.io-78720",
            "more_info_path": "/vulnerabilities/CVE-2024-3955/78720",
            "specs": [
                ">=4.0.0.58,<4.4.1.a1"
            ],
            "v": ">=4.0.0.58,<4.4.1.a1"
        }
    ],
    "ccf": [
        {
            "advisory": "Ccf 0.7 fixes a vulnerability to a possible replay attack.",
            "cve": "PVE-2021-38641",
            "id": "pyup.io-38641",
            "more_info_path": "/vulnerabilities/PVE-2021-38641/38641",
            "specs": [
                "<0.7"
            ],
            "v": "<0.7"
        },
        {
            "advisory": "Ccf 5.0.0dev7 includes a security fix: 'POST /recovery/members/{memberId}:recover' is now authenticated by COSE Sign1, making it consistent with the other 'POST' endpoints in governance, and avoiding a potential denial of service where unauthenticated and unauthorized clients could submit invalid shares repeatedly.\r\nhttps://github.com/microsoft/CCF/pull/5832",
            "cve": "PVE-2023-62328",
            "id": "pyup.io-62328",
            "more_info_path": "/vulnerabilities/PVE-2023-62328/62328",
            "specs": [
                "<5.0.0dev7"
            ],
            "v": "<5.0.0dev7"
        }
    ],
    "ccmd": [
        {
            "advisory": "Affected versions of the `ccmd` package are vulnerable to Path Traversal due to extracting release tar archives without validating member paths. The `handle_update` function opens the downloaded tarball with `tarfile.open` and previously invoked `tar.extractall()` on archive entries without normalizing and bounding member names, allowing absolute paths and parent-directory (`..`) references to escape the intended extraction directory.",
            "cve": "PVE-2025-80942",
            "id": "pyup.io-80942",
            "more_info_path": "/vulnerabilities/PVE-2025-80942/80942",
            "specs": [
                "<1.1.4"
            ],
            "v": "<1.1.4"
        }
    ],
    "cdk-ecr-deployment": [
        {
            "advisory": "Cdk-ecr-deployment 0.0.34 updates its dependency 'trim-newlines' to version '3.0.1' to include a security fix.\r\nhttps://github.com/wchaws/cdk-ecr-deployment/commit/22267948c545579788d1ed065ff2fb3b05adc863\r\nhttps://github.com/wchaws/cdk-ecr-deployment/commit/8cf3f5069e2ec1e22afe17c4025e752172be88bd",
            "cve": "CVE-2021-33623",
            "id": "pyup.io-59197",
            "more_info_path": "/vulnerabilities/CVE-2021-33623/59197",
            "specs": [
                "<0.0.34"
            ],
            "v": "<0.0.34"
        },
        {
            "advisory": "Cdk-ecr-deployment 0.0.60 updates its NPM dependency 'xmldom' to v0.7.0 to include a security fix.\r\nhttps://github.com/cdklabs/cdk-ecr-deployment/commit/7b222a9a253a9a18371c489fbb2577e90f59fc4f",
            "cve": "CVE-2021-32796",
            "id": "pyup.io-42166",
            "more_info_path": "/vulnerabilities/CVE-2021-32796/42166",
            "specs": [
                "<0.0.60"
            ],
            "v": "<0.0.60"
        },
        {
            "advisory": "Cdk-ecr-deployment 0.0.83 updates Go dependency 'runc' to include a security fix.\r\nhttps://github.com/cdklabs/cdk-ecr-deployment/pull/142/commits/2716589ed475eee2e3458a22b398a92c7b9dab72",
            "cve": "CVE-2021-30465",
            "id": "pyup.io-43005",
            "more_info_path": "/vulnerabilities/CVE-2021-30465/43005",
            "specs": [
                "<0.0.83"
            ],
            "v": "<0.0.83"
        },
        {
            "advisory": "Cdk-ecr-deployment 2.0.7 updates its GO dependency 'opencontainers/runc'  to v1.0.3 to include a security fix.\r\nhttps://github.com/cdklabs/cdk-ecr-deployment/commit/74e8412f370f4ab00be5b5a1f509c2615a874a46",
            "cve": "CVE-2021-43784",
            "id": "pyup.io-54973",
            "more_info_path": "/vulnerabilities/CVE-2021-43784/54973",
            "specs": [
                "<2.0.7"
            ],
            "v": "<2.0.7"
        },
        {
            "advisory": "Cdk-ecr-deployment 2.0.7 updates its GO dependency 'containerd'  to v1.5.9 to include a security fix.\r\nhttps://github.com/cdklabs/cdk-ecr-deployment/commit/74e8412f370f4ab00be5b5a1f509c2615a874a46",
            "cve": "CVE-2021-43816",
            "id": "pyup.io-44474",
            "more_info_path": "/vulnerabilities/CVE-2021-43816/44474",
            "specs": [
                "<2.0.7"
            ],
            "v": "<2.0.7"
        },
        {
            "advisory": "Cdk-ecr-deployment 2.1.4 fix security issue by updating 'docker/distribution' version to v2.8.0.\r\nhttps://github.com/cdklabs/cdk-ecr-deployment/commit/3ae21c155db5410002ba1a98469bee03ff5a28b7",
            "cve": "CVE-2021-3538",
            "id": "pyup.io-45103",
            "more_info_path": "/vulnerabilities/CVE-2021-3538/45103",
            "specs": [
                "<2.1.4"
            ],
            "v": "<2.1.4"
        },
        {
            "advisory": "Cdk-ecr-deployment 2.5.3 updates its dependency 'opencontainers/runc' to v1.1.2 to include a security fix.",
            "cve": "CVE-2022-29162",
            "id": "pyup.io-49117",
            "more_info_path": "/vulnerabilities/CVE-2022-29162/49117",
            "specs": [
                "<2.5.3"
            ],
            "v": "<2.5.3"
        }
    ],
    "cdk-keycloak": [
        {
            "advisory": "Cdk-keycloak 0.2.45 updates its NPM dependency 'got' to v12.5.2 to include a security fix.",
            "cve": "CVE-2022-33987",
            "id": "pyup.io-51648",
            "more_info_path": "/vulnerabilities/CVE-2022-33987/51648",
            "specs": [
                "<0.2.45"
            ],
            "v": "<0.2.45"
        }
    ],
    "cdklabs.cdk-proserve-lib": [
        {
            "advisory": "Affected versions of @cdklabs/cdk-proserve-lib are potentially vulnerable to a misconfiguration issue. This flaw may lead to insecure resource policy settings, potentially allowing unauthorized modifications and exposure of sensitive infrastructure data.",
            "cve": "PVE-2025-76452",
            "id": "pyup.io-76452",
            "more_info_path": "/vulnerabilities/PVE-2025-76452/76452",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        }
    ],
    "cdo-local-uuid": [
        {
            "advisory": "Cdo-local-uuid is affected by an information leakage vulnerability. The vulnerability stems from a Python function, 'cdo_local_uuid.local_uuid()', and its original implementation 'case_utils.local_uuid()'.\r\nhttps://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/security/advisories/GHSA-rgrf-6mf5-m882",
            "cve": "CVE-2024-22194",
            "id": "pyup.io-64285",
            "more_info_path": "/vulnerabilities/CVE-2024-22194/64285",
            "specs": [
                "==0.4.0"
            ],
            "v": "==0.4.0"
        }
    ],
    "cdsetool": [
        {
            "advisory": "Cdsetool 0.2.10 updates its `requests` dependency requirement from `<2.32.0,>=2.28.1` to `>=2.28.1,<2.33.0` due to the CVE-2024-35195.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-71099",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/71099",
            "specs": [
                "<0.2.10"
            ],
            "v": "<0.2.10"
        }
    ],
    "cedar-backup3": [
        {
            "advisory": "Cedar-backup3 version 1.10 fixes a shell-interpolation bug.",
            "cve": "PVE-2021-42010",
            "id": "pyup.io-42010",
            "more_info_path": "/vulnerabilities/PVE-2021-42010/42010",
            "specs": [
                "<1.10"
            ],
            "v": "<1.10"
        },
        {
            "advisory": "Cedar-backup3 version 1.10 stops using insecure os.popen().",
            "cve": "PVE-2022-46427",
            "id": "pyup.io-46427",
            "more_info_path": "/vulnerabilities/PVE-2022-46427/46427",
            "specs": [
                "<1.10"
            ],
            "v": "<1.10"
        }
    ],
    "ceilometer": [
        {
            "advisory": "(1) impl_db2.py and (2) impl_mongodb.py in OpenStack Ceilometer 2013.2 and earlier, when the logging level is set to INFO, logs the connection string from ceilometer.conf, which allows local users to obtain sensitive information (the DB2 or MongoDB password) by reading the log file.",
            "cve": "CVE-2013-6384",
            "id": "pyup.io-70583",
            "more_info_path": "/vulnerabilities/CVE-2013-6384/70583",
            "specs": [
                "<2013.2.1"
            ],
            "v": "<2013.2.1"
        },
        {
            "advisory": "A vulnerability was found in ceilometer before version 12.0.0.0rc1. An Information Exposure in ceilometer-agent prints sensitive configuration data to log files without DEBUG logging being activated.",
            "cve": "CVE-2019-3830",
            "id": "pyup.io-54166",
            "more_info_path": "/vulnerabilities/CVE-2019-3830/54166",
            "specs": [
                ">=0,<12.0.0.0rc1"
            ],
            "v": ">=0,<12.0.0.0rc1"
        }
    ],
    "celery": [
        {
            "advisory": "Celery 4.4.0rc5 addresses a race condition that occurred during the publishing of very large chord headers. This fix ensures that the operation is completed successfully even when dealing with such large data sets.\r\nhttps://github.com/celery/celery/pull/5850/files#diff-3a80ff45da16a11b96e26a63973d7d490187a68ddc1949e2dfd7fd090b208841",
            "cve": "PVE-2024-64270",
            "id": "pyup.io-64270",
            "more_info_path": "/vulnerabilities/PVE-2024-64270/64270",
            "specs": [
                "<4.4.0rc5"
            ],
            "v": "<4.4.0rc5"
        },
        {
            "advisory": "Celery 5.2.0 updates 'kombu' to v5.2.1, which includes dependencies updates that resolve security issues.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-42498",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/42498",
            "specs": [
                "<5.2.0"
            ],
            "v": "<5.2.0"
        },
        {
            "advisory": "Celery 5.2.2 includes a fix for CVE-2021-23727: Celery before 5.2.2. by default trusts the messages and metadata stored in backends (result stores). When reading task metadata from the backend, the data is deserialized. Given that an attacker can gain access to, or somehow manipulate the metadata within a celery backend, they could trigger a stored command injection vulnerability and potentially gain further access to the system.",
            "cve": "CVE-2021-23727",
            "id": "pyup.io-43738",
            "more_info_path": "/vulnerabilities/CVE-2021-23727/43738",
            "specs": [
                "<5.2.2"
            ],
            "v": "<5.2.2"
        },
        {
            "advisory": "Celery 2.1 and 2.2 before 2.2.8, 2.3 before 2.3.4, and 2.4 before 2.4.4 changes the effective id but not the real id during processing of the --uid and --gid arguments to celerybeat, celeryd_detach, celeryd-multi, and celeryev, which allows local users to gain privileges via vectors involving crafted code that is executed by the worker process.",
            "cve": "CVE-2011-4356",
            "id": "pyup.io-54071",
            "more_info_path": "/vulnerabilities/CVE-2011-4356/54071",
            "specs": [
                ">=2.1,<2.2.8",
                ">=2.3,<2.3.4",
                ">=2.4,<2.4.4"
            ],
            "v": ">=2.1,<2.2.8,>=2.3,<2.3.4,>=2.4,<2.4.4"
        },
        {
            "advisory": "Celery 4.0.1 includes a fix for a code execution vulnerability: The default accept_content setting was set to allow deserialization of pickled messages in Celery 4.0.0. A workaround is to configure the 4.0.0 version to explicitly only allow json serialized messages.\r\nhttps://github.com/celery/celery/blob/master/docs/sec/CELERYSA-0003.txt",
            "cve": "PVE-2021-25646",
            "id": "pyup.io-25646",
            "more_info_path": "/vulnerabilities/PVE-2021-25646/25646",
            "specs": [
                ">=4.0.0rc3,<4.0.1"
            ],
            "v": ">=4.0.0rc3,<4.0.1"
        }
    ],
    "celery-director": [
        {
            "advisory": "Celery-director 0.9.0 updates its dependency 'redis' to v4.4.4 to include security fixes.",
            "cve": "CVE-2023-28858",
            "id": "pyup.io-55267",
            "more_info_path": "/vulnerabilities/CVE-2023-28858/55267",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Celery-director 0.9.0 updates its dependency 'redis' to v4.4.4 to include security fixes.",
            "cve": "CVE-2023-28859",
            "id": "pyup.io-55276",
            "more_info_path": "/vulnerabilities/CVE-2023-28859/55276",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Celery-director 0.9.0 updates its dependency 'sentry-sdk' to v1.14.0 to include a security fix.",
            "cve": "CVE-2023-28117",
            "id": "pyup.io-55277",
            "more_info_path": "/vulnerabilities/CVE-2023-28117/55277",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        }
    ],
    "cellxgene": [
        {
            "advisory": "Cellxgene 0.12.0 updates its NPM dependency 'eslint-utils' to a version ^1.4.2 to include a security fix.",
            "cve": "CVE-2019-15657",
            "id": "pyup.io-37801",
            "more_info_path": "/vulnerabilities/CVE-2019-15657/37801",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        },
        {
            "advisory": "Cellxgene 0.12.0 updates its NPM dependency 'set-value' to v2.0.1 to include a security fix.",
            "cve": "CVE-2021-23440",
            "id": "pyup.io-44976",
            "more_info_path": "/vulnerabilities/CVE-2021-23440/44976",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        },
        {
            "advisory": "Cellxgene 0.12.0 updates its NPM dependency 'mixin-deep' to v1.3.2 to include a security fix.",
            "cve": "CVE-2019-10746",
            "id": "pyup.io-44974",
            "more_info_path": "/vulnerabilities/CVE-2019-10746/44974",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        },
        {
            "advisory": "Cellxgene 0.12.0 updates several more NPM dependencies to fix security issues.\r\nhttps://github.com/chanzuckerberg/cellxgene/commit/78a43402cb0c1beca5269b3970d4cc31615e4664",
            "cve": "PVE-2022-44977",
            "id": "pyup.io-44977",
            "more_info_path": "/vulnerabilities/PVE-2022-44977/44977",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        },
        {
            "advisory": "Cellxgene 0.12.0 stops requiring 'node-fetch' as a NPM dependency to avoid security issues.",
            "cve": "CVE-2020-15168",
            "id": "pyup.io-44975",
            "more_info_path": "/vulnerabilities/CVE-2020-15168/44975",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        },
        {
            "advisory": "Cellxgene 0.16.0 removed the `client` package that introduced security vulnerabilities.",
            "cve": "PVE-2021-38696",
            "id": "pyup.io-38696",
            "more_info_path": "/vulnerabilities/PVE-2021-38696/38696",
            "specs": [
                "<0.16.0"
            ],
            "v": "<0.16.0"
        }
    ],
    "censusdis": [
        {
            "advisory": "Censusdis version 1.1.7 updates its requests dependency from ^2.28.1 to ^2.32.0 to address the security vulnerability identified as CVE-2024-35195.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-71132",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/71132",
            "specs": [
                "<1.1.7"
            ],
            "v": "<1.1.7"
        }
    ],
    "centrifuge": [
        {
            "advisory": "centrifuge 0.3.8 includes a security fix! Please, upgrade to this version or disable access to `/dumps` location.",
            "cve": "PVE-2021-25647",
            "id": "pyup.io-25647",
            "more_info_path": "/vulnerabilities/PVE-2021-25647/25647",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        }
    ],
    "ceph-deploy": [
        {
            "advisory": "ceph-deploy before 1.5.23 uses weak permissions (644) for ceph/ceph.client.admin.keyring, which allows local users to obtain sensitive information by reading the file.",
            "cve": "CVE-2015-3010",
            "id": "pyup.io-42238",
            "more_info_path": "/vulnerabilities/CVE-2015-3010/42238",
            "specs": [
                "<1.5.23"
            ],
            "v": "<1.5.23"
        },
        {
            "advisory": "The admin command in ceph-deploy before 1.5.25 uses world-readable permissions for /etc/ceph/ceph.client.admin.keyring, which allows local users to obtain sensitive information by reading the file.",
            "cve": "CVE-2015-4053",
            "id": "pyup.io-54102",
            "more_info_path": "/vulnerabilities/CVE-2015-4053/54102",
            "specs": [
                ">=0,<1.5.23"
            ],
            "v": ">=0,<1.5.23"
        }
    ],
    "certbot": [
        {
            "advisory": "Certbot through 0.34.0 does not configure the web server so that all requests redirect to secure HTTPS access.",
            "cve": "PVE-2021-37112",
            "id": "pyup.io-37112",
            "more_info_path": "/vulnerabilities/PVE-2021-37112/37112",
            "specs": [
                "<=0.34.0"
            ],
            "v": "<=0.34.0"
        }
    ],
    "certbot-dns-duckdns": [
        {
            "advisory": "Certbot-dns-duckdns 1.3 updates its dependency 'cryptography' to latest version in the docker image, to include security fixes.",
            "cve": "CVE-2023-0216",
            "id": "pyup.io-53630",
            "more_info_path": "/vulnerabilities/CVE-2023-0216/53630",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        },
        {
            "advisory": "Certbot-dns-duckdns 1.3 updates its dependency 'cryptography' to latest version in the docker image, to include security fixes.",
            "cve": "CVE-2023-0217",
            "id": "pyup.io-53628",
            "more_info_path": "/vulnerabilities/CVE-2023-0217/53628",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        },
        {
            "advisory": "Certbot-dns-duckdns 1.3 updates its dependency 'cryptography' to latest version in the docker image, to include security fixes.",
            "cve": "CVE-2023-0401",
            "id": "pyup.io-53624",
            "more_info_path": "/vulnerabilities/CVE-2023-0401/53624",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        }
    ],
    "certbot-dns-porkbun": [
        {
            "advisory": "Certbot-dns-porkbun 0.8 updates 'cryptography' to v39.0.1 in Docker image to include security fixes.\r\nhttps://github.com/infinityofspace/certbot_dns_porkbun/commit/789959d75ef65b9e6e7fdf0651254bf18378b0a9",
            "cve": "CVE-2023-0401",
            "id": "pyup.io-53618",
            "more_info_path": "/vulnerabilities/CVE-2023-0401/53618",
            "specs": [
                "<0.8"
            ],
            "v": "<0.8"
        },
        {
            "advisory": "Certbot-dns-porkbun 0.8 updates 'cryptography' to v39.0.1 in Docker image to include security fixes.\r\nhttps://github.com/infinityofspace/certbot_dns_porkbun/commit/789959d75ef65b9e6e7fdf0651254bf18378b0a9",
            "cve": "CVE-2023-0217",
            "id": "pyup.io-53619",
            "more_info_path": "/vulnerabilities/CVE-2023-0217/53619",
            "specs": [
                "<0.8"
            ],
            "v": "<0.8"
        },
        {
            "advisory": "Certbot-dns-porkbun 0.8 updates 'cryptography' to v39.0.1 in Docker image to include security fixes.\r\nhttps://github.com/infinityofspace/certbot_dns_porkbun/commit/789959d75ef65b9e6e7fdf0651254bf18378b0a9",
            "cve": "CVE-2023-0216",
            "id": "pyup.io-53622",
            "more_info_path": "/vulnerabilities/CVE-2023-0216/53622",
            "specs": [
                "<0.8"
            ],
            "v": "<0.8"
        }
    ],
    "certif": [
        {
            "advisory": "Certif is a malicious package, pytosquatting the popular package 'certifi'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53258",
            "id": "pyup.io-53258",
            "more_info_path": "/vulnerabilities/PVE-2023-53258/53258",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "certife": [
        {
            "advisory": "Certife is a malicious package, pytosquatting the popular package 'certifi'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53259",
            "id": "pyup.io-53259",
            "more_info_path": "/vulnerabilities/PVE-2023-53259/53259",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "certifi": [
        {
            "advisory": "Certifi 2022.12.07 includes a fix for CVE-2022-23491: Certifi 2022.12.07 removes root certificates from \"TrustCor\" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-52365",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/52365",
            "specs": [
                "<2022.12.07"
            ],
            "v": "<2022.12.07"
        },
        {
            "advisory": "certifi before 2017.04.17 is vulnerable to improper certificate validation because they do not reject deprecated 1024-bit certificates, but instead only issue a warning. This vulnerability impacts the security of the package's certificate verification process.\r\nhttps://github.com/certifi/python-certifi/commit/4f35e3529c78ced74040cf5d80bf8ec4aac9a190",
            "cve": "PVE-2024-99806",
            "id": "pyup.io-65987",
            "more_info_path": "/vulnerabilities/PVE-2024-99806/65987",
            "specs": [
                ">=0,<2017.04.17"
            ],
            "v": ">=0,<2017.04.17"
        },
        {
            "advisory": "Certifi 2023.07.22 includes a fix for CVE-2023-37920: Certifi prior to version 2023.07.22 recognizes \"e-Tugra\" root certificates. e-Tugra's root certificates were subject to an investigation prompted by reporting of security issues in their systems. Certifi 2023.07.22 removes root certificates from \"e-Tugra\" from the root store.\r\nhttps://github.com/certifi/python-certifi/security/advisories/GHSA-xqr8-7jwr-rhp7",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-59956",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/59956",
            "specs": [
                ">=2015.04.28,<2023.07.22"
            ],
            "v": ">=2015.04.28,<2023.07.22"
        },
        {
            "advisory": "Certifi affected versions recognized root certificates from GLOBALTRUST. Certifi patch removes these root certificates from the root store. These certificates are being removed pursuant to an investigation that identified \"long-running and unresolved compliance issues\" and are also in the process of being removed from Mozilla's trust store.",
            "cve": "CVE-2024-39689",
            "id": "pyup.io-72083",
            "more_info_path": "/vulnerabilities/CVE-2024-39689/72083",
            "specs": [
                ">=2021.05.30,<2024.07.04"
            ],
            "v": ">=2021.05.30,<2024.07.04"
        }
    ],
    "certifie": [
        {
            "advisory": "Certifie is a malicious package, pytosquatting the popular package 'certifi'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53260",
            "id": "pyup.io-53260",
            "more_info_path": "/vulnerabilities/PVE-2023-53260/53260",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "certifiee": [
        {
            "advisory": "Certifiee is a malicious package, pytosquatting the popular package 'certifi'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53261",
            "id": "pyup.io-53261",
            "more_info_path": "/vulnerabilities/PVE-2023-53261/53261",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "cerulean": [
        {
            "advisory": "Cerulean 0.3.4 adds proper directory permissions when using mkdir().\r\nhttps://github.com/MD-Studio/cerulean/commit/388b171477f909972d5dc9043ed5fcae4369e3b7",
            "cve": "PVE-2021-36796",
            "id": "pyup.io-36796",
            "more_info_path": "/vulnerabilities/PVE-2021-36796/36796",
            "specs": [
                "<0.3.4"
            ],
            "v": "<0.3.4"
        }
    ],
    "cffconvert": [
        {
            "advisory": "Cffconvert 1.0.3 updates requests from v2.18.4 to v2.20.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36623",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36623",
            "specs": [
                "<1.0.3"
            ],
            "v": "<1.0.3"
        }
    ],
    "cfripper": [
        {
            "advisory": "Cfripper 1.14.0 updates its dependency 'pydash' to v6.0.0 to include a security fix.",
            "cve": "CVE-2023-26145",
            "id": "pyup.io-61458",
            "more_info_path": "/vulnerabilities/CVE-2023-26145/61458",
            "specs": [
                "<1.14.0"
            ],
            "v": "<1.14.0"
        }
    ],
    "cfscrape": [
        {
            "advisory": "Cfscrape 1.8.0 includes a fix for CVE-2017-7235: An issue was discovered in cloudflare-scrape 1.6.6 through 1.7.1. A malicious website owner could craft a page that executes arbitrary Python code against any cfscrape user who scrapes that website. This is fixed in 1.8.0.",
            "cve": "CVE-2017-7235",
            "id": "pyup.io-35741",
            "more_info_path": "/vulnerabilities/CVE-2017-7235/35741",
            "specs": [
                ">=1.6.6,<1.8.0"
            ],
            "v": ">=1.6.6,<1.8.0"
        }
    ],
    "cfstacks": [
        {
            "advisory": "Cfstacks 0.4.4 upgrades PyAML to 4.2b1 (or later) to fix a security vulnerability.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-38388",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/38388",
            "specs": [
                "<0.4.4"
            ],
            "v": "<0.4.4"
        },
        {
            "advisory": "Cfstacks 0.4.6 fixes potentially unsafe use of 'yaml.load()'.\r\nhttps://github.com/cfstacks/stacks/commit/faa4d8899c06de0a671d4b96471f6cad07e32f2f",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-45280",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/45280",
            "specs": [
                "<0.4.6"
            ],
            "v": "<0.4.6"
        }
    ],
    "cg": [
        {
            "advisory": "Cg 18.11.3 updates its dependency 'cryptography' to v3.3.2 to include a security fix.",
            "cve": "CVE-2020-36242",
            "id": "pyup.io-39614",
            "more_info_path": "/vulnerabilities/CVE-2020-36242/39614",
            "specs": [
                "<18.11.3"
            ],
            "v": "<18.11.3"
        },
        {
            "advisory": "Cg 26.0.4 addresses issues with certain endpoints that were only reliant on cookies for authentication, making them prone to potential attacks. The affected areas include the admin and invoice endpoints. After the update, users should experience normal operation through the order, admin, and invoice interfaces. Any attempts to exploit the CSRF vulnerability will now result in a \"Bad Request\" error. \r\nhttps://github.com/Clinical-Genomics/cg/pull/1737",
            "cve": "PVE-2024-63503",
            "id": "pyup.io-63503",
            "more_info_path": "/vulnerabilities/PVE-2024-63503/63503",
            "specs": [
                "<26.0.4"
            ],
            "v": "<26.0.4"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Open Redirect attacks due to improper validation of the Referer header. The invoices/views.py file fails to validate whether the domain specified in the Referer header is trusted before performing a redirection. This allows external domains to trigger redirects from the application without user awareness or approval.\r\nAn attacker can exploit this by crafting a request with a malicious Referer value, which the server blindly trusts. This enables redirection to attacker-controlled domains, potentially leading to phishing attacks, credential theft, or delivery of malicious content by abusing the trust users place in the application's domain.",
            "cve": "PVE-2024-71931",
            "id": "pyup.io-71931",
            "more_info_path": "/vulnerabilities/PVE-2024-71931/71931",
            "specs": [
                ">=2.9.0,<60.2.12"
            ],
            "v": ">=2.9.0,<60.2.12"
        }
    ],
    "cg-django-uaa": [
        {
            "advisory": "Cg-django-uaa 2.1.4 updates its dependency 'pyjwt' to include a security fix.",
            "cve": "CVE-2022-29217",
            "id": "pyup.io-50653",
            "more_info_path": "/vulnerabilities/CVE-2022-29217/50653",
            "specs": [
                "<2.1.4"
            ],
            "v": "<2.1.4"
        }
    ],
    "cgbeacon2": [
        {
            "advisory": "Cgbeacon2 4.3 prevents unsafe 'HTTP' connections.\r\nhttps://github.com/Clinical-Genomics/cgbeacon2/commit/614bdd7e01b19ce297b0e612e4821ed661c8f658",
            "cve": "PVE-2022-51437",
            "id": "pyup.io-51437",
            "more_info_path": "/vulnerabilities/PVE-2022-51437/51437",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        }
    ],
    "cgcloud-lib": [
        {
            "advisory": "Cgcloud-lib 1.6.0 and prior include a version of 'paramiko' (1.16.0) affected by known vulnerabilities.",
            "cve": "CVE-2022-24302",
            "id": "pyup.io-48020",
            "more_info_path": "/vulnerabilities/CVE-2022-24302/48020",
            "specs": [
                "<=1.6.0"
            ],
            "v": "<=1.6.0"
        },
        {
            "advisory": "Cgcloud-lib 1.6.0 and prior include a version of 'paramiko' (1.16.0) affected by known vulnerabilities.",
            "cve": "CVE-2018-7750",
            "id": "pyup.io-47515",
            "more_info_path": "/vulnerabilities/CVE-2018-7750/47515",
            "specs": [
                "<=1.6.0"
            ],
            "v": "<=1.6.0"
        }
    ],
    "cgroups-exporter": [
        {
            "advisory": "Cgroups-exporter 0.8.0 includes a fix for a denial of service vulnerability. \r\nhttps://github.com/mosquito/cgroups-exporter/commit/611ac2618e834135a86b1871231680759e4c37ff",
            "cve": "PVE-2023-59074",
            "id": "pyup.io-59074",
            "more_info_path": "/vulnerabilities/PVE-2023-59074/59074",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        }
    ],
    "chafa.py": [
        {
            "advisory": "Chafa.py serves as a Python wrapper for the Chafa library. The GitHub repository hpjansson/chafa, prior to version 1.12.0, contains a heap-based Buffer Overflow vulnerability. This issue has been addressed in the Chapa.py update, specifically version 1.1.0.",
            "cve": "CVE-2022-20610",
            "id": "pyup.io-63001",
            "more_info_path": "/vulnerabilities/CVE-2022-20610/63001",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "chainerrl-visualizer": [
        {
            "advisory": "Chainerrl-visualizer throughout 0.1.1 allows absolute path traversal because the Flask send_file function is used unsafely. See CVE-2022-31573.",
            "cve": "CVE-2022-31573",
            "id": "pyup.io-50085",
            "more_info_path": "/vulnerabilities/CVE-2022-31573/50085",
            "specs": [
                "<=0.1.1"
            ],
            "v": "<=0.1.1"
        }
    ],
    "chainlit": [
        {
            "advisory": "Chainlit 0.2.108 includes a fix for an improper authorization vulnerability.\r\nhttps://github.com/Chainlit/chainlit/commit/ae3fe1c3b21e3d2a7b297f6985b56a2ab0e5f784",
            "cve": "PVE-2023-58839",
            "id": "pyup.io-58839",
            "more_info_path": "/vulnerabilities/PVE-2023-58839/58839",
            "specs": [
                "<0.2.108"
            ],
            "v": "<0.2.108"
        },
        {
            "advisory": "Chainlit 0.4.1 updates its dependency 'vite' to version '4.3.9' to include a security fix.\r\nhttps://github.com/Chainlit/chainlit/commit/67bfc52445afec69d383e43208a48a80b8a9f8dc",
            "cve": "CVE-2023-34092",
            "id": "pyup.io-59120",
            "more_info_path": "/vulnerabilities/CVE-2023-34092/59120",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Chainlit 1.0.501 has updated its Starlette dependency to version \"^0.37.2\" from \"<0.33.0\" to address the security issue identified in CVE-2023-29159.",
            "cve": "CVE-2023-29159",
            "id": "pyup.io-67535",
            "more_info_path": "/vulnerabilities/CVE-2023-29159/67535",
            "specs": [
                "<1.0.501"
            ],
            "v": "<1.0.501"
        },
        {
            "advisory": "Affected versions of Chainlit are vulnerable to Unsafe Defaults. Default host configuration was 0.0.0.0, allowing connections from any external IP address. This could lead to several security vulnerabilities, such as:\r\n- Denial of Service (DoS) Attacks: Attackers can inundate the system with an overwhelming number of requests, leading to service interruptions for legitimate users by exhausting the system's resources.\r\n- Man-in-the-Middle (MitM) Attacks: The open access makes it feasible for attackers to intercept and manipulate communications between two parties covertly.",
            "cve": "PVE-2024-73234",
            "id": "pyup.io-73234",
            "more_info_path": "/vulnerabilities/PVE-2024-73234/73234",
            "specs": [
                "<1.1.404"
            ],
            "v": "<1.1.404"
        },
        {
            "advisory": "Affected versions of Chainlit are vulnerable to Path Traversal (CWE-22). This vulnerability allows attackers to read arbitrary files on the server by exploiting insufficient path validation in file-serving endpoints. Functions like `get_file`, `serve_file`, and `get_avatar` fail to properly restrict file paths, enabling attackers to access sensitive files via crafted requests containing malicious path components. Users should upgrade to the version where input validation and path restrictions are correctly implemented to mitigate this vulnerability.",
            "cve": "PVE-2024-73036",
            "id": "pyup.io-73036",
            "more_info_path": "/vulnerabilities/PVE-2024-73036/73036",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        },
        {
            "advisory": "Affected versions of the Chainlit backend are vulnerable to Missing Authorization (CWE-862). This flaw allows unauthorized users to access and retrieve session files by guessing or obtaining valid session_ids, potentially leading to data breaches. The vulnerability exists in the get_file endpoint, which lacked proper user verification. Exploitability is high if session_ids are predictable. Chainlit mitigates this issue by enforcing strict authorization checks.\r\nUPDATE: \"1.3.1 release temporarily reverts the file access security improvements from 1.3.0 to restore element functionality. The element feature currently has a known security vulnerability that could allow unauthorized access to files. We strongly recommend against using elements in production environments until the next release. A comprehensive security fix using HTTP-only cookie authentication will be implemented in an upcoming release.\"",
            "cve": "PVE-2024-73842",
            "id": "pyup.io-73842",
            "more_info_path": "/vulnerabilities/PVE-2024-73842/73842",
            "specs": [
                "<1.3.0",
                ">=2.0.dev0,<2.0.dev1",
                ">2.0.dev1",
                ">1.3.0,<2.0.dev0"
            ],
            "v": "<1.3.0,>=2.0.dev0,<2.0.dev1,>2.0.dev1,>1.3.0,<2.0.dev0"
        },
        {
            "advisory": "Affected versions of the Chainlit package are potentially vulnerable to Improper Access Control due to a missing authorization check when binding a WebSocket session to a user-supplied threadId.",
            "cve": "PVE-2025-81403",
            "id": "pyup.io-81403",
            "more_info_path": "/vulnerabilities/PVE-2025-81403/81403",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Affected versions of the chainlit package are vulnerable to arbitrary file read (path traversal) due to missing sanitization of custom thread element update payloads. The update_thread_element and delete_thread_element handlers in backend/chainlit/server.py accept untrusted ElementDict data and previously constructed elements without properly filtering attacker-controlled fields like path/url.",
            "cve": "PVE-2025-83206",
            "id": "pyup.io-83206",
            "more_info_path": "/vulnerabilities/PVE-2025-83206/83206",
            "specs": [
                "<2.9.4"
            ],
            "v": "<2.9.4"
        }
    ],
    "changedetection.io": [
        {
            "advisory": "Changedetection.io affected versions were discovered to contain a stored cross-site scripting (XSS) vulnerability on the main page. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the URL parameter under the \"Add a new change detection watch\" function.",
            "cve": "CVE-2023-24769",
            "id": "pyup.io-72001",
            "more_info_path": "/vulnerabilities/CVE-2023-24769/72001",
            "specs": [
                "<0.40.2"
            ],
            "v": "<0.40.2"
        },
        {
            "advisory": "Changedetection.io version 0.45.21 includes a security update to fix a server-side template injection vulnerability in Jinja2 that could allow remote command execution, identified as CVE-2024-32651. Additionally, it implements the use of `ImmutableSandboxedEnvironment` for validation to enhance security.",
            "cve": "CVE-2024-32651",
            "id": "pyup.io-70483",
            "more_info_path": "/vulnerabilities/CVE-2024-32651/70483",
            "specs": [
                "<0.45.21"
            ],
            "v": "<0.45.21"
        },
        {
            "advisory": "changedetection.io is a free open-source web page change detection, website watcher, restock monitor and notification service. In affected versions Input in parameter notification_urls is not processed resulting in javascript execution in the application. A reflected XSS vulnerability happens when the user input from a URL or POST data is reflected on the page without being stored, thus allowing the attacker to inject malicious content.",
            "cve": "CVE-2024-34061",
            "id": "pyup.io-71908",
            "more_info_path": "/vulnerabilities/CVE-2024-34061/71908",
            "specs": [
                "<0.45.22"
            ],
            "v": "<0.45.22"
        },
        {
            "advisory": "Changedetection.io 0.45.6 updates its dependency 'flask' to include a security fix.",
            "cve": "CVE-2023-30861",
            "id": "pyup.io-62234",
            "more_info_path": "/vulnerabilities/CVE-2023-30861/62234",
            "specs": [
                "<0.45.6"
            ],
            "v": "<0.45.6"
        },
        {
            "advisory": "Affected versions of changedetectionio are vulnerable to Path Traversal (CWE-22). This allows attackers to retrieve local system files by using crafted URLs like source:file:///etc/passwd. The vulnerability arises from improper URL validation in WebDriver\u2019s file fetching functions, enabling unauthorized file access.",
            "cve": "CVE-2024-51483",
            "id": "pyup.io-74073",
            "more_info_path": "/vulnerabilities/CVE-2024-51483/74073",
            "specs": [
                "<0.47.05"
            ],
            "v": "<0.47.05"
        },
        {
            "advisory": "Affected versions of changedetectionio are vulnerable to Path Traversal (CWE-22). The issue arises from inadequate URL validation in the URL processing functions, where file:/ URLs were not properly blocked. To exploit, an attacker can craft malicious file:/ URLs targeting the application to access sensitive local files. Mitigation involves updating to the version where the regex correctly blocks both file:// and file:/ schemes.\r\n#Note: This issue only affects instances with a webdriver enabled, and ALLOW_FILE_URI false or not defined.",
            "cve": "CVE-2024-51998",
            "id": "pyup.io-74072",
            "more_info_path": "/vulnerabilities/CVE-2024-51998/74072",
            "specs": [
                "<0.47.06"
            ],
            "v": "<0.47.06"
        },
        {
            "advisory": "Improper input validation in the application can allow attackers to perform local file read (LFR) or path traversal attacks. These vulnerabilities occur when user input is used to construct file paths without adequate sanitization or validation, allowing unauthorized access to sensitive files. Even though this has been addressed in previous patch, it was still insufficient.",
            "cve": "CVE-2024-56509",
            "id": "pyup.io-74773",
            "more_info_path": "/vulnerabilities/CVE-2024-56509/74773",
            "specs": [
                "<0.48.5"
            ],
            "v": "<0.48.5"
        },
        {
            "advisory": "Affected versions of the changedetection.io package are vulnerable to Cross-site Scripting (XSS) due to missing URL safety validation in the Watch update API. In the browser interface, changedetection.io calls the validate_url(test_url) helper, which ultimately uses the model.Watch.is_safe_url check to block unsafe schemes such as javascript:, but the Watch update API endpoint (for example, PUT /api/v1/watch/{id}) accepts attacker-controlled URL fields without invoking this validation, allowing storage of script-based URLs in Watch data.",
            "cve": "CVE-2025-62780",
            "id": "pyup.io-81578",
            "more_info_path": "/vulnerabilities/CVE-2025-62780/81578",
            "specs": [
                "<0.50.34"
            ],
            "v": "<0.50.34"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Cross-Site Scripting (XSS) due to insufficient output encoding in the watch overview functionality. Error messages from website page change detection watches fail to properly sanitize user-controlled input before rendering in the HTML response, leading to potential XSS attacks where malicious scripts can be executed in users' browsers.",
            "cve": "CVE-2025-52558",
            "id": "pyup.io-77893",
            "more_info_path": "/vulnerabilities/CVE-2025-52558/77893",
            "specs": [
                "<0.50.4"
            ],
            "v": "<0.50.4"
        },
        {
            "advisory": "Changedetection.io is vulnerable to an Incorrect Authorization vulnerability. API endpoint /api/v1/watch//history can be accessed by any unauthorized user.",
            "cve": "CVE-2024-23329",
            "id": "pyup.io-64341",
            "more_info_path": "/vulnerabilities/CVE-2024-23329/64341",
            "specs": [
                ">=0.39.14,<=0.45.12"
            ],
            "v": ">=0.39.14,<=0.45.12"
        }
    ],
    "chanjo-report": [
        {
            "advisory": "Chanjo-report 2.4.0 uses sudo insecurely, potentially allowing a local attacker to escalate privileges.\r\nhttps://github.com/robinandeer/chanjo-report/commit/bbb6ba9855b08c563764639d55bbcc0915c1dc55",
            "cve": "PVE-2022-45287",
            "id": "pyup.io-45287",
            "more_info_path": "/vulnerabilities/PVE-2022-45287/45287",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chanjo-report 2.4.0 removes a link to the \"index\" page from the report (security).",
            "cve": "PVE-2021-25648",
            "id": "pyup.io-25648",
            "more_info_path": "/vulnerabilities/PVE-2021-25648/25648",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        }
    ],
    "channels": [
        {
            "advisory": "Django channels package before 2.1.7 is vulnerable to a Denial of Service (DoS) attack due to not limiting the size of request bodies. This vulnerability specifically involves Regular Expression Denial of Service (ReDoS) attacks, whereby crafted inputs utilizing regular expressions can cause excessive backtracking by the regex engine. This process can significantly slow down the system, consuming disproportionate CPU resources to process these crafted requests, potentially making the system inaccessible to legitimate users. This issue arises from the way certain strings, when matched against specific regular expressions, can force the regex engine into a large number of computational steps, drastically increasing for strings with specific patterns, thereby enabling attackers to exploit this behavior for a DoS attack.\r\nhttps://github.com/django/channels/commit/a1ecd5ee72a538f19bdd9e8f6bb91bb8aabba5d9",
            "cve": "PVE-2024-99807",
            "id": "pyup.io-65986",
            "more_info_path": "/vulnerabilities/PVE-2024-99807/65986",
            "specs": [
                ">=0,<2.1.7"
            ],
            "v": ">=0,<2.1.7"
        },
        {
            "advisory": "Channels 3.0.3 includes a fix for CVE-2020-35681. See also: .",
            "cve": "CVE-2020-35681",
            "id": "pyup.io-39368",
            "more_info_path": "/vulnerabilities/CVE-2020-35681/39368",
            "specs": [
                ">=3.0.0,<3.0.3"
            ],
            "v": ">=3.0.0,<3.0.3"
        }
    ],
    "chaosloader": [
        {
            "advisory": "Chaosloader 1.0.0 adds secure encrypted password to travis.yml.",
            "cve": "PVE-2021-37048",
            "id": "pyup.io-37048",
            "more_info_path": "/vulnerabilities/PVE-2021-37048/37048",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "chaostoolkit": [
        {
            "advisory": "Chaostoolkit 1.14.0 updates container image to include security fixes.",
            "cve": "CVE-2022-29458",
            "id": "pyup.io-54860",
            "more_info_path": "/vulnerabilities/CVE-2022-29458/54860",
            "specs": [
                "<1.14.0"
            ],
            "v": "<1.14.0"
        },
        {
            "advisory": "Chaostoolkit 1.14.0 updates container image to include security fixes.",
            "cve": "CVE-2022-1304",
            "id": "pyup.io-54845",
            "more_info_path": "/vulnerabilities/CVE-2022-1304/54845",
            "specs": [
                "<1.14.0"
            ],
            "v": "<1.14.0"
        },
        {
            "advisory": "Chaostoolkit 1.14.0 updates container image to include security fixes.",
            "cve": "CVE-2020-16156",
            "id": "pyup.io-54865",
            "more_info_path": "/vulnerabilities/CVE-2020-16156/54865",
            "specs": [
                "<1.14.0"
            ],
            "v": "<1.14.0"
        },
        {
            "advisory": "Chaostoolkit 1.14.0 updates container image to include security fixes.",
            "cve": "CVE-2019-8457",
            "id": "pyup.io-54857",
            "more_info_path": "/vulnerabilities/CVE-2019-8457/54857",
            "specs": [
                "<1.14.0"
            ],
            "v": "<1.14.0"
        },
        {
            "advisory": "Chaostoolkit 1.14.0 updates container image to include security fixes.",
            "cve": "CVE-2021-33560",
            "id": "pyup.io-54859",
            "more_info_path": "/vulnerabilities/CVE-2021-33560/54859",
            "specs": [
                "<1.14.0"
            ],
            "v": "<1.14.0"
        }
    ],
    "charm-crypto": [
        {
            "advisory": "In Charm 0.43, any two users can collude to achieve the ability to decrypt YCT14 data.",
            "cve": "CVE-2021-37588",
            "id": "pyup.io-42318",
            "more_info_path": "/vulnerabilities/CVE-2021-37588/42318",
            "specs": [
                "==0.43"
            ],
            "v": "==0.43"
        },
        {
            "advisory": "In Charm 0.43, any single user can decrypt DAC-MACS or MA-ABE-YJ14 data.",
            "cve": "CVE-2021-37587",
            "id": "pyup.io-42317",
            "more_info_path": "/vulnerabilities/CVE-2021-37587/42317",
            "specs": [
                "==0.43"
            ],
            "v": "==0.43"
        }
    ],
    "charm-tools": [
        {
            "advisory": "Charm-tools 2.6.0 addresses security alerts from GitHub (#484).",
            "cve": "PVE-2021-37201",
            "id": "pyup.io-37201",
            "more_info_path": "/vulnerabilities/PVE-2021-37201/37201",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        }
    ],
    "charmhelpers": [
        {
            "advisory": "Charmhelpers 0.19.13 updates Keystone's config files permissions to meet security guide.\r\nhttps://github.com/juju/charm-helpers/pull/299",
            "cve": "PVE-2021-37032",
            "id": "pyup.io-37032",
            "more_info_path": "/vulnerabilities/PVE-2021-37032/37032",
            "specs": [
                "<0.19.13"
            ],
            "v": "<0.19.13"
        }
    ],
    "chartify": [
        {
            "advisory": "Chartify version 3.0.3 includes a security patch for the function '_from_yaml' in 'chartify/_core/colors.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects.\r\nhttps://github.com/spotify/chartify/commit/e9d34194b19f973b934497a1013c918bc8a98fee#diff-8238e9741da72d8460f3b7e87879bad2821fe5cfbadb42112a6a7373ee5c494a",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-41310",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/41310",
            "specs": [
                "<3.0.3"
            ],
            "v": "<3.0.3"
        },
        {
            "advisory": "Chartify 3.0.4 updates its dependency 'pillow' requirement to '>=8.4.0' to include security fixes.",
            "cve": "CVE-2019-19911",
            "id": "pyup.io-38345",
            "more_info_path": "/vulnerabilities/CVE-2019-19911/38345",
            "specs": [
                "<=3.0.3"
            ],
            "v": "<=3.0.3"
        },
        {
            "advisory": "Chartify 3.0.3 includes a version of 'pillow' (6.2.0) affected by several CVEs.",
            "cve": "CVE-2020-5312",
            "id": "pyup.io-43570",
            "more_info_path": "/vulnerabilities/CVE-2020-5312/43570",
            "specs": [
                "<=3.0.3"
            ],
            "v": "<=3.0.3"
        },
        {
            "advisory": "libImaging/FliDecode.c in Pillow before 6.2.2 has an FLI buffer overflow.",
            "cve": "CVE-2020-5313",
            "id": "pyup.io-43571",
            "more_info_path": "/vulnerabilities/CVE-2020-5313/43571",
            "specs": [
                "<=3.0.3"
            ],
            "v": "<=3.0.3"
        },
        {
            "advisory": "Chartify 3.0.3 includes a version of 'pillow' (6.2.0) affected by several CVEs.",
            "cve": "CVE-2020-5311",
            "id": "pyup.io-43569",
            "more_info_path": "/vulnerabilities/CVE-2020-5311/43569",
            "specs": [
                "<=3.0.3"
            ],
            "v": "<=3.0.3"
        },
        {
            "advisory": "libImaging/TiffDecode.c in Pillow before 6.2.2 has a TIFF decoding integer overflow, related to realloc.",
            "cve": "CVE-2020-5310",
            "id": "pyup.io-43568",
            "more_info_path": "/vulnerabilities/CVE-2020-5310/43568",
            "specs": [
                "<=3.0.3"
            ],
            "v": "<=3.0.3"
        }
    ],
    "chartmogul": [
        {
            "advisory": "Chartmogul 4.3.1 updates its urllib3 dependency from <=2.0.4 to 1.26.19 to address security concerns, including several vulnerabilities such as CVE-2023-45803.",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-71715",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/71715",
            "specs": [
                "<4.3.1"
            ],
            "v": "<4.3.1"
        },
        {
            "advisory": "Chartmogul 4.3.1 updates its urllib3 dependency from <=2.0.4 to 1.26.19 to address security concerns, including several vulnerabilities such as CVE-2023-43804.",
            "cve": "CVE-2023-43804",
            "id": "pyup.io-71724",
            "more_info_path": "/vulnerabilities/CVE-2023-43804/71724",
            "specs": [
                "<4.3.1"
            ],
            "v": "<4.3.1"
        },
        {
            "advisory": "Chartmogul 4.3.2 updates its urllib3 dependency from version 1.26.19 to 2.2.2 to address CVE-2024-37891.",
            "cve": "CVE-2024-37891",
            "id": "pyup.io-71816",
            "more_info_path": "/vulnerabilities/CVE-2024-37891/71816",
            "specs": [
                "<4.3.2"
            ],
            "v": "<4.3.2"
        }
    ],
    "chatbot-ner": [
        {
            "advisory": "Chatbot-ner 0.6.0 updates its dependency 'nltk' to v3.4.5 to include a security fix.",
            "cve": "CVE-2019-14751",
            "id": "pyup.io-43698",
            "more_info_path": "/vulnerabilities/CVE-2019-14751/43698",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Chatbot-ner 0.6.0 updates its dependency 'Django' to v1.11.27 to include security fixes.",
            "cve": "CVE-2019-14232",
            "id": "pyup.io-43695",
            "more_info_path": "/vulnerabilities/CVE-2019-14232/43695",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Chatbot-ner 0.6.0 updates its dependency 'Django' to v1.11.27 to include security fixes.",
            "cve": "CVE-2019-14233",
            "id": "pyup.io-43696",
            "more_info_path": "/vulnerabilities/CVE-2019-14233/43696",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Chatbot-ner 0.6.0 updates its dependency 'Django' to v1.11.27 to include security fixes.",
            "cve": "CVE-2019-14235",
            "id": "pyup.io-43697",
            "more_info_path": "/vulnerabilities/CVE-2019-14235/43697",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Chatbot-ner 0.6.0 updates its dependency 'Django' to v1.11.27 to include security fixes.",
            "cve": "CVE-2019-19844",
            "id": "pyup.io-43699",
            "more_info_path": "/vulnerabilities/CVE-2019-19844/43699",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Chatbot-ner 0.6.0 updates its dependency 'Django' to v1.11.26 to include security fixes.",
            "cve": "CVE-2019-14234",
            "id": "pyup.io-38515",
            "more_info_path": "/vulnerabilities/CVE-2019-14234/38515",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "chatterbot": [
        {
            "advisory": "Affected versions of the ChatterBot package are vulnerable to Denial of Service (DoS) due to improper database session and connection pool management. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls, allowing concurrent invocations to consume and exhaust the underlying SQLAlchemy connection pool rapidly. An unauthenticated attacker can exploit this by sending multiple simultaneous requests to the chatbot service, causing the application to become unresponsive and requiring a manual restart to restore functionality.",
            "cve": "CVE-2026-23842",
            "id": "pyup.io-84842",
            "more_info_path": "/vulnerabilities/CVE-2026-23842/84842",
            "specs": [
                "<1.2.11"
            ],
            "v": "<1.2.11"
        }
    ],
    "chattts": [
        {
            "advisory": "Affected versions of ChatTTS are vulnerable to Deserialization of Untrusted Data (CWE-502). This vulnerability allows arbitrary code execution due to unsafe deserialization when loading the tokenizer with torch.load. Attackers can exploit this by supplying a malicious tokenizer.pt file, leading to code execution during deserialization in the Tokenizer class's __init__ method. Exploitation requires the attacker to replace or tamper with the tokenizer.pt file. Mitigation involves updating ChatTTS to the version which replaces torch.load with the safer BertTokenizerFast.from_pretrained method. This issue is specific to Python applications using PyTorch's torch.load on untrusted data.",
            "cve": "PVE-2024-74037",
            "id": "pyup.io-74037",
            "more_info_path": "/vulnerabilities/PVE-2024-74037/74037",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "chaturbate-poller": [
        {
            "advisory": "Affected versions of Chaturbate-poller are vulnerable to Sensitive Information Exposure.",
            "cve": "PVE-2024-73683",
            "id": "pyup.io-73683",
            "more_info_path": "/vulnerabilities/PVE-2024-73683/73683",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "chazz": [
        {
            "advisory": "Chazz is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html",
            "cve": "PVE-2023-52909",
            "id": "pyup.io-52909",
            "more_info_path": "/vulnerabilities/PVE-2023-52909/52909",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "check-jsonschema": [
        {
            "advisory": "Affected versions of check-jsonschema are vulnerable to Acceptance of Extraneous Untrusted Data With Trusted Data (CWE-349). This vulnerability allows attackers to inject and process untrusted $ref schemas alongside trusted schemas, potentially leading to cache poisoning or execution of malicious schemas. The attack vector involves crafting trusted schemas that include malicious $ref URLs, which are fetched and treated as trusted without proper validation. Vulnerable methods include schema loading and caching mechanisms. Exploitability is high if attackers can influence schema contents. Mitigation involves upgrading to versions where cache filenames are securely hashed using SHA256 and implementing strict validation of fetched schemas to ensure their integrity and authenticity.",
            "cve": "CVE-2024-53848",
            "id": "pyup.io-74430",
            "more_info_path": "/vulnerabilities/CVE-2024-53848/74430",
            "specs": [
                "<0.30.0"
            ],
            "v": "<0.30.0"
        }
    ],
    "checkmk": [
        {
            "advisory": "Check_MK before 1.2.8p26 mishandles certain errors within the failed-login save feature because of a race condition, which allows remote attackers to obtain sensitive user information by reading a GUI crash report.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2017-14955",
            "id": "pyup.io-63076",
            "more_info_path": "/vulnerabilities/CVE-2017-14955/63076",
            "specs": [
                "<1.2.8p26"
            ],
            "v": "<1.2.8p26"
        },
        {
            "advisory": "Checkmk before 1.6.0p17 allows local users to obtain SYSTEM privileges via a Trojan horse shell script in the %PROGRAMDATA%\\checkmk\\agent\\local directory.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2020-24908",
            "id": "pyup.io-63081",
            "more_info_path": "/vulnerabilities/CVE-2020-24908/63081",
            "specs": [
                "<1.6.0p17"
            ],
            "v": "<1.6.0p17"
        },
        {
            "advisory": "In Checkmk before 1.6.0p29, 2.x before 2.0.0p25, and 2.1.x before 2.1.0b10, a site user can escalate to root by editing an OMD hook symlink.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-31258",
            "id": "pyup.io-63088",
            "more_info_path": "/vulnerabilities/CVE-2022-31258/63088",
            "specs": [
                "<1.6.0p29",
                ">=2.0.0p0,<2.0.0p25",
                ">=2.1.0b0,<2.1.0b10"
            ],
            "v": "<1.6.0p29,>=2.0.0p0,<2.0.0p25,>=2.1.0b0,<2.1.0b10"
        },
        {
            "advisory": "Uncontrolled Search Path Element in Checkmk Agent in Tribe29 Checkmk before 2.1.0p1, before 2.0.0p25 and before 1.6.0p29 on a Checkmk server allows the site user to escalate privileges via a manipulated unixcat executable\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-43440",
            "id": "pyup.io-63125",
            "more_info_path": "/vulnerabilities/CVE-2022-43440/63125",
            "specs": [
                "<1.6.0p29",
                ">=2.0.0p0,<2.0.0p25",
                ">=2.1.0p0,<2.1.0p1"
            ],
            "v": "<1.6.0p29,>=2.0.0p0,<2.0.0p25,>=2.1.0p0,<2.1.0p1"
        },
        {
            "advisory": "A permission issue affects users that deployed the shipped version of the Checkmk Debian package. Packages created by the agent bakery (enterprise editions only) were not affected. Using the shipped version of the agents, the maintainer scripts located at /var/lib/dpkg/info/ will be owned by the user and the group with ID 1001. If such a user exists on the system, they can change the content of these files (which are then executed by root). This leads to a local privilege escalation on the monitored host. Version 1.6 through 1.6.9p29, version 2.0 through 2.0.0p26, version 2.1 through 2.1.0p3, and version 2.2.0i1 are affected.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-33912",
            "id": "pyup.io-63082",
            "more_info_path": "/vulnerabilities/CVE-2022-33912/63082",
            "specs": [
                "<1.6.9p29",
                ">=2.0.0p0,<2.0.0p26",
                ">=2.1.0p0,<2.1.0p3",
                "==2.2.0i1"
            ],
            "v": "<1.6.9p29,>=2.0.0p0,<2.0.0p26,>=2.1.0p0,<2.1.0p3,==2.2.0i1"
        },
        {
            "advisory": "Checkmk <=2.0.0p19 contains a Cross Site Scripting (XSS) vulnerability. While creating or editing a user attribute, the Help Text is subject to HTML injection, which can be triggered for editing a user.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-24564",
            "id": "pyup.io-63077",
            "more_info_path": "/vulnerabilities/CVE-2022-24564/63077",
            "specs": [
                "<2.0.0p20"
            ],
            "v": "<2.0.0p20"
        },
        {
            "advisory": "Improper neutralization of livestatus command delimiters in the RestAPI in Checkmk < 2.0.0p36, < 2.1.0p28, and < 2.2.0b8 (beta) allows arbitrary livestatus command execution for authorized users.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-31208",
            "id": "pyup.io-63141",
            "more_info_path": "/vulnerabilities/CVE-2023-31208/63141",
            "specs": [
                "<2.0.0p36",
                ">=2.2.0b0,<2.2.0p28",
                ">=2.2.0b0,<2.2.0b8"
            ],
            "v": "<2.0.0p36,>=2.2.0b0,<2.2.0p28,>=2.2.0b0,<2.2.0b8"
        },
        {
            "advisory": "Limited Server-Side Request Forgery (SSRF) in agent-receiver in Tribe29's Checkmk <= 2.1.0p11 allows an attacker to communicate with local network restricted endpoints by use of the host registration API.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-48321",
            "id": "pyup.io-63133",
            "more_info_path": "/vulnerabilities/CVE-2022-48321/63133",
            "specs": [
                "<2.1.0p12"
            ],
            "v": "<2.1.0p12"
        },
        {
            "advisory": "Cross-site Request Forgery (CSRF) in Tribe29's Checkmk <= 2.1.0p17, Checkmk <= 2.0.0p31, and all versions of Checkmk 1.6.0 (EOL) allow an attacker to add new visual elements to multiple pages.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-48320",
            "id": "pyup.io-63126",
            "more_info_path": "/vulnerabilities/CVE-2022-48320/63126",
            "specs": [
                "<=2.0.0p31",
                ">=2.1.0p0,<2.1.0p18"
            ],
            "v": "<=2.0.0p31,>=2.1.0p0,<2.1.0p18"
        },
        {
            "advisory": "Path-Traversal in MKP storing in Tribe29 Checkmk <=2.0.0p32 and <= 2.1.0p18 allows an administrator to write mkp files to arbitrary locations via a malicious mkp file.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-4884",
            "id": "pyup.io-63083",
            "more_info_path": "/vulnerabilities/CVE-2022-4884/63083",
            "specs": [
                "<=2.0.0p32",
                ">=2.1.0p0,<=2.1.0p18"
            ],
            "v": "<=2.0.0p32,>=2.1.0p0,<=2.1.0p18"
        },
        {
            "advisory": "Improper Input Validation of LDAP user IDs in Tribe29 Checkmk allows attackers that can control LDAP user IDs to manipulate files on the server. Checkmk <= 2.1.0p19, Checkmk <= 2.0.0p32, and all versions of Checkmk 1.6.0 (EOL) are affected.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-0284",
            "id": "pyup.io-63124",
            "more_info_path": "/vulnerabilities/CVE-2023-0284/63124",
            "specs": [
                "<=2.0.0p32",
                ">=2.1.0p0,<=2.1.0p19"
            ],
            "v": "<=2.0.0p32,>=2.1.0p0,<=2.1.0p19"
        },
        {
            "advisory": "User enumeration in Checkmk <=2.2.0p4 allows an authenticated attacker to enumerate usernames.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-22359",
            "id": "pyup.io-63143",
            "more_info_path": "/vulnerabilities/CVE-2023-22359/63143",
            "specs": [
                "<=2.2.0p4"
            ],
            "v": "<=2.2.0p4"
        },
        {
            "advisory": "The web management console of CheckMK Raw Edition (versions 1.5.0 to 1.6.0) allows a misconfiguration of the web-app Dokuwiki (installed by default), which allows embedded php code. As a result, remote code execution is achieved. Successful exploitation requires access to the web management interface, either with valid credentials or with a hijacked session by a user with the role of administrator.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2021-40904",
            "id": "pyup.io-63085",
            "more_info_path": "/vulnerabilities/CVE-2021-40904/63085",
            "specs": [
                ">=1.5.0,<1.6.0"
            ],
            "v": ">=1.5.0,<1.6.0"
        },
        {
            "advisory": "CheckMK Raw Edition software (versions 1.5.0 to 1.6.0) does not sanitize the input of a web service parameter that is in an unauthenticated zone. This Reflected XSS allows an attacker to open a backdoor on the device with HTML content and interpreted by the browser (such as JavaScript or other client-side scripts) or to steal the session cookies of a user who has previously authenticated via a man in the middle. Successful exploitation requires access to the web service resource without authentication.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2021-40906",
            "id": "pyup.io-63080",
            "more_info_path": "/vulnerabilities/CVE-2021-40906/63080",
            "specs": [
                ">=1.5.0,<1.6.0p19"
            ],
            "v": ">=1.5.0,<1.6.0p19"
        },
        {
            "advisory": "The CheckMK management web console (versions 1.5.0 to 2.0.0) does not sanitise user input in various parameters of the WATO module. This allows an attacker to open a backdoor on the device with HTML content and interpreted by the browser (such as JavaScript or other client-side scripts), the XSS payload will be triggered when the user accesses some specific sections of the application. In the same sense a very dangerous potential way would be when an attacker who has the monitor role (not administrator) manages to get a stored XSS to steal the secretAutomation (for the use of the API in administrator mode) and thus be able to create another administrator user who has high privileges on the CheckMK monitoring web console. Another way is that persistent XSS allows an attacker to modify the displayed content or change the victim's information. Successful exploitation requires access to the web management interface, either with valid credentials or with a hijacked session.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2021-36563",
            "id": "pyup.io-63084",
            "more_info_path": "/vulnerabilities/CVE-2021-36563/63084",
            "specs": [
                ">=1.5.0,<=2.0.0"
            ],
            "v": ">=1.5.0,<=2.0.0"
        },
        {
            "advisory": "A stored cross site scripting (XSS) vulnerability in Checkmk 1.6.0x prior to 1.6.0p19 allows an authenticated remote attacker to inject arbitrary JavaScript via a javascript: URL in a view title.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2020-28919",
            "id": "pyup.io-63087",
            "more_info_path": "/vulnerabilities/CVE-2020-28919/63087",
            "specs": [
                ">=1.6.0p0,<1.6.0p19"
            ],
            "v": ">=1.6.0p0,<1.6.0p19"
        },
        {
            "advisory": "In Checkmk <=2.0.0p19 fixed in 2.0.0p20 and Checkmk <=1.6.0p27 fixed in 1.6.0p28, the title of a Predefined condition is not properly escaped when shown as condition, which can result in Cross Site Scripting (XSS).\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-24566",
            "id": "pyup.io-63078",
            "more_info_path": "/vulnerabilities/CVE-2022-24566/63078",
            "specs": [
                ">=2.0.0p0,<2.0.0p20",
                "<1.6.0p28"
            ],
            "v": ">=2.0.0p0,<2.0.0p20,<1.6.0p28"
        },
        {
            "advisory": "Checkmk <=2.0.0p19 Fixed in 2.0.0p20 and Checkmk <=1.6.0p27 Fixed in 1.6.0p28 are affected by a Cross Site Scripting (XSS) vulnerability. The Alias of a site was not properly escaped when shown as condition for notifications.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-24565",
            "id": "pyup.io-63079",
            "more_info_path": "/vulnerabilities/CVE-2022-24565/63079",
            "specs": [
                ">=2.0.0p0,<2.0.0p20",
                "<1.6.0p28"
            ],
            "v": ">=2.0.0p0,<2.0.0p20,<1.6.0p28"
        },
        {
            "advisory": "Broad access controls could allow site users to directly interact with the system Apache installation when providing the reverse proxy configurations for Tribe29's Checkmk <= 2.1.0p6, Checkmk <= 2.0.0p27, and all versions of Checkmk 1.6.0 (EOL) allowing an attacker to perform remote code execution with root privileges on the underlying host.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-46302",
            "id": "pyup.io-63139",
            "more_info_path": "/vulnerabilities/CVE-2022-46302/63139",
            "specs": [
                ">=2.1.0b0,<=2.1.0p6",
                "<=2.0.0p27"
            ],
            "v": ">=2.1.0b0,<=2.1.0p6,<=2.0.0p27"
        },
        {
            "advisory": "Livestatus Query Language (LQL) injection in the AuthUser HTTP query header of Tribe29's Checkmk <= 2.1.0p11, Checkmk <= 2.0.0p28, and all versions of Checkmk 1.6.0 (EOL) allows an attacker to perform direct queries to the application's core from localhost.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-47909",
            "id": "pyup.io-63127",
            "more_info_path": "/vulnerabilities/CVE-2022-47909/63127",
            "specs": [
                ">=2.1.0p0,<2.1.0p12",
                "<=2.0.0p28"
            ],
            "v": ">=2.1.0p0,<2.1.0p12,<=2.0.0p28"
        },
        {
            "advisory": "No authorization controls in the RestAPI documentation for Tribe29's Checkmk <= 2.1.0p13 and Checkmk <= 2.0.0p29 which may lead to unintended information disclosure through automatically generated user specific tags within Rest API documentation.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-48318",
            "id": "pyup.io-63128",
            "more_info_path": "/vulnerabilities/CVE-2022-48318/63128",
            "specs": [
                ">=2.1.0p0,<2.1.0p14",
                "<=2.0.0p29"
            ],
            "v": ">=2.1.0p0,<2.1.0p14,<=2.0.0p29"
        },
        {
            "advisory": "Expired sessions were not securely terminated in the RestAPI for Tribe29's Checkmk <= 2.1.0p10 and Checkmk <= 2.0.0p28 allowing an attacker to use expired session tokens when communicating with the RestAPI.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-48317",
            "id": "pyup.io-63132",
            "more_info_path": "/vulnerabilities/CVE-2022-48317/63132",
            "specs": [
                ">=2.1.0p0,<=2.1.0p10",
                "<=2.0.0p28"
            ],
            "v": ">=2.1.0p0,<=2.1.0p10,<=2.0.0p28"
        },
        {
            "advisory": "Command injection in SMS notifications in Tribe29 Checkmk <= 2.1.0p10, Checkmk <= 2.0.0p27, and Checkmk <= 1.6.0p29 allows an attacker with User Management permissions, as well as LDAP administrators in certain scenarios, to perform arbitrary commands within the context of the application's local permissions.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-46303",
            "id": "pyup.io-63129",
            "more_info_path": "/vulnerabilities/CVE-2022-46303/63129",
            "specs": [
                ">=2.1.0p0,<=2.1.0p10",
                ">=2.0.0p0,<=2.0.0p27",
                "<=1.6.0p29"
            ],
            "v": ">=2.1.0p0,<=2.1.0p10,>=2.0.0p0,<=2.0.0p27,<=1.6.0p29"
        },
        {
            "advisory": "PHP code injection in watolib auth.php and hosttags.php in Tribe29's Checkmk <= 2.1.0p10, Checkmk <= 2.0.0p27, and Checkmk <= 1.6.0p29 allows an attacker to inject and execute PHP code which will be executed upon request of the vulnerable component.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-46836",
            "id": "pyup.io-63130",
            "more_info_path": "/vulnerabilities/CVE-2022-46836/63130",
            "specs": [
                ">=2.1.0p0,<=2.1.0p10",
                ">=2.0.0p0,<=2.0.0p27",
                "<=1.6.0p29"
            ],
            "v": ">=2.1.0p0,<=2.1.0p10,>=2.0.0p0,<=2.0.0p27,<=1.6.0p29"
        },
        {
            "advisory": "Sensitive host secret disclosed in cmk-update-agent.log file in Tribe29's Checkmk <= 2.1.0p13, Checkmk <= 2.0.0p29, and all versions of Checkmk 1.6.0 (EOL) allows an attacker to gain access to the host secret through the unprotected agent updater log file.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2022-48319",
            "id": "pyup.io-63131",
            "more_info_path": "/vulnerabilities/CVE-2022-48319/63131",
            "specs": [
                ">=2.1.0p0,<=2.1.0p13",
                "<=2.0.0p29"
            ],
            "v": ">=2.1.0p0,<=2.1.0p13,<=2.0.0p29"
        },
        {
            "advisory": "HTML Email Injection in Tribe29 Checkmk <=2.1.0p23; <=2.0.0p34, and all versions of Checkmk 1.6.0 allows an authenticated attacker to inject malicious HTML into Emails\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-22288",
            "id": "pyup.io-63134",
            "more_info_path": "/vulnerabilities/CVE-2023-22288/63134",
            "specs": [
                ">=2.1.0p0,<=2.1.0p23",
                "<=2.0.0p34"
            ],
            "v": ">=2.1.0p0,<=2.1.0p23,<=2.0.0p34"
        },
        {
            "advisory": "Inappropriate error handling in Tribe29 Checkmk <= 2.1.0p25, <= 2.0.0p34, <= 2.2.0b3 (beta), and all versions of Checkmk 1.6.0 causes the symmetric encryption of agent data to fail silently and transmit the data in plaintext in certain configurations.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-1768",
            "id": "pyup.io-63135",
            "more_info_path": "/vulnerabilities/CVE-2023-1768/63135",
            "specs": [
                ">=2.1.0p0,<=2.1.0p25",
                ">=2.2.0b0,<=2.2.0b3",
                "<=2.0.0p34"
            ],
            "v": ">=2.1.0p0,<=2.1.0p25,>=2.2.0b0,<=2.2.0b3,<=2.0.0p34"
        },
        {
            "advisory": "Improper Authorization in RestAPI in Checkmk GmbH's Checkmk versions <2.1.0p28 and <2.2.0b8 allows remote authenticated users to read arbitrary host_configs.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-22348",
            "id": "pyup.io-63142",
            "more_info_path": "/vulnerabilities/CVE-2023-22348/63142",
            "specs": [
                ">=2.2.0b0,<2.2.0b8",
                "<2.1.0p28"
            ],
            "v": ">=2.2.0b0,<2.2.0b8,<2.1.0p28"
        },
        {
            "advisory": "Improper neutralization of livestatus command delimiters in ajax_search in Checkmk <= 2.0.0p39, < 2.1.0p37, and < 2.2.0p15 allows arbitrary livestatus command execution for authorized users.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-6157",
            "id": "pyup.io-63147",
            "more_info_path": "/vulnerabilities/CVE-2023-6157/63147",
            "specs": [
                ">=2.2.0b0,<2.2.0p15",
                ">=2.1.0b0,<2.1.0p37",
                "<=2.0.0p39"
            ],
            "v": ">=2.2.0b0,<2.2.0p15,>=2.1.0b0,<2.1.0p37,<=2.0.0p39"
        },
        {
            "advisory": "Improper neutralization of livestatus command delimiters in the availability timeline in Checkmk <= 2.0.0p39, < 2.1.0p37, and < 2.2.0p15 allows arbitrary livestatus command execution for authorized users.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-6156",
            "id": "pyup.io-63149",
            "more_info_path": "/vulnerabilities/CVE-2023-6156/63149",
            "specs": [
                ">=2.2.0b0,<2.2.0p15",
                ">=2.1.0b0,<2.1.0p37",
                "<=2.0.0p39"
            ],
            "v": ">=2.2.0b0,<2.2.0p15,>=2.1.0b0,<2.1.0p37,<=2.0.0p39"
        },
        {
            "advisory": "Improper Input Validation in Checkmk <2.2.0p15, <2.1.0p37, <=2.0.0p39 allows privileged attackers to cause partial denial of service in the UI via long hostnames.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-23549",
            "id": "pyup.io-63146",
            "more_info_path": "/vulnerabilities/CVE-2023-23549/63146",
            "specs": [
                ">=2.2.0b0,<2.2.0p15",
                ">=2.1.0b0,<2.1.0p37",
                "<=2.0.0p39"
            ],
            "v": ">=2.2.0b0,<2.2.0p15,>=2.1.0b0,<2.1.0p37,<=2.0.0p39"
        },
        {
            "advisory": "Cross-site Request Forgery (CSRF) in Checkmk < 2.2.0p15, < 2.1.0p37, <= 2.0.0p39 allow an authenticated attacker to delete user-messages for individual users.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-6251",
            "id": "pyup.io-63148",
            "more_info_path": "/vulnerabilities/CVE-2023-6251/63148",
            "specs": [
                ">=2.2.0b0,<2.2.0p15",
                ">=2.1.0b0,<2.1.0p37",
                "<=2.0.0p39"
            ],
            "v": ">=2.2.0b0,<2.2.0p15,>=2.1.0b0,<2.1.0p37,<=2.0.0p39"
        },
        {
            "advisory": "Improper neutralization of active check command arguments in Checkmk < 2.1.0p32, < 2.0.0p38, < 2.2.0p4 leads to arbitrary command execution for authenticated users.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-31209",
            "id": "pyup.io-63145",
            "more_info_path": "/vulnerabilities/CVE-2023-31209/63145",
            "specs": [
                ">=2.2.0b0,<2.2.0p4",
                ">=2.1.0b0,<2.1.0p32",
                "<2.0.0p38"
            ],
            "v": ">=2.2.0b0,<2.2.0p4,>=2.1.0b0,<2.1.0p32,<2.0.0p38"
        },
        {
            "advisory": "Reflected XSS in business intelligence in Checkmk <2.2.0p8, <2.1.0p32, <2.0.0p38, <=1.6.0p30.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-23548",
            "id": "pyup.io-63144",
            "more_info_path": "/vulnerabilities/CVE-2023-23548/63144",
            "specs": [
                ">=2.2.0b0,<2.2.0p8",
                ">=2.1.0b0,<2.1.0p32",
                ">=2.0.0b0,<2.0.0p38",
                "<=1.6.0p30"
            ],
            "v": ">=2.2.0b0,<2.2.0p8,>=2.1.0b0,<2.1.0p32,>=2.0.0b0,<2.0.0p38,<=1.6.0p30"
        },
        {
            "advisory": "Insufficient permission checks in the REST API in Tribe29 Checkmk <= 2.1.0p27 and <= 2.2.0b4 (beta) allow unauthorized users to schedule downtimes for any host.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-2020",
            "id": "pyup.io-63136",
            "more_info_path": "/vulnerabilities/CVE-2023-2020/63136",
            "specs": [
                ">=2.2.0b0,<=2.2.0b4",
                "<=2.1.0p27"
            ],
            "v": ">=2.2.0b0,<=2.2.0b4,<=2.1.0p27"
        },
        {
            "advisory": "Transmission of credentials within query parameters in Checkmk <= 2.1.0p26, <= 2.0.0p35, and <= 2.2.0b6 (beta) may cause the automation user's secret to be written to the site Apache access log.\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-31207",
            "id": "pyup.io-63140",
            "more_info_path": "/vulnerabilities/CVE-2023-31207/63140",
            "specs": [
                ">=2.2.0b0,<=2.2.0b6",
                ">=2.1.0p0,<=2.1.0p26",
                "<=2.0.0p35"
            ],
            "v": ">=2.2.0b0,<=2.2.0b6,>=2.1.0p0,<=2.1.0p26,<=2.0.0p35"
        },
        {
            "advisory": "Usage of user controlled LD_LIBRARY_PATH in agent in Checkmk 2.2.0p10 up to 2.2.0p16 allows malicious Checkmk site user to escalate rights via injection of malicious libraries\r\nNote: Checkmk on PyPI is a placeholder. You may download the real package from its official website (https://checkmk.com/download).",
            "cve": "CVE-2023-31210",
            "id": "pyup.io-63150",
            "more_info_path": "/vulnerabilities/CVE-2023-31210/63150",
            "specs": [
                ">=2.2.0p10,<=2.2.0p16"
            ],
            "v": ">=2.2.0p10,<=2.2.0p16"
        }
    ],
    "checkov": [
        {
            "advisory": "Bridgecrew 2.0.1029 introduces a fix for a vulnerability that previously allowed security group rules in Terraform configurations to permit unrestricted ingress access from 0.0.0.0:0 to port 22, commonly used for SSH.\r\nhttps://github.com/bridgecrewio/checkov/issues/1973\r\nhttps://github.com/bridgecrewio/checkov/pull/2749",
            "cve": "PVE-2024-63646",
            "id": "pyup.io-63646",
            "more_info_path": "/vulnerabilities/PVE-2024-63646/63646",
            "specs": [
                "<2.0.1029"
            ],
            "v": "<2.0.1029"
        },
        {
            "advisory": "Checkov 2.0.677 fixes unsafe regex to prevent ReDOS attacks.\r\nhttps://github.com/bridgecrewio/checkov/commit/333d3bcc6c9c178bffc37ac19422b41b665bfbc9",
            "cve": "PVE-2021-43446",
            "id": "pyup.io-43446",
            "more_info_path": "/vulnerabilities/PVE-2021-43446/43446",
            "specs": [
                "<2.0.677"
            ],
            "v": "<2.0.677"
        },
        {
            "advisory": "Checkov before 2.0.26 is vulnerable to unsafe deserialization, which allows arbitrary code execution when processing a malicious terraform file.",
            "cve": "CVE-2021-3035",
            "id": "pyup.io-63933",
            "more_info_path": "/vulnerabilities/CVE-2021-3035/63933",
            "specs": [
                ">=2.0.0,<2.0.26"
            ],
            "v": ">=2.0.0,<2.0.26"
        }
    ],
    "checksec-py": [
        {
            "advisory": "Checksec-py is powered by LIEF. Cchecksec-py 0.6.2 and versions below uses LIEF as dependency, which has a CVE on its versions below 0.13.0. \r\nhttps://nvd.nist.gov/vuln/detail/CVE-2022-38496\r\nhttps://deps.dev/pypi/checksec-py/0.6.2/dependencies",
            "cve": "CVE-2022-38496",
            "id": "pyup.io-62769",
            "more_info_path": "/vulnerabilities/CVE-2022-38496/62769",
            "specs": [
                "<=0.6.2"
            ],
            "v": "<=0.6.2"
        }
    ],
    "cheetah": [
        {
            "advisory": "cheetah 0.9.17rc1 removeS the use of temp files for handling imports with dynamic compilation. This removes a whole slew of issues, including a temp file security issue.",
            "cve": "PVE-2021-25649",
            "id": "pyup.io-25649",
            "more_info_path": "/vulnerabilities/PVE-2021-25649/25649",
            "specs": [
                "<0.9.17rc1"
            ],
            "v": "<0.9.17rc1"
        },
        {
            "advisory": "Cheetah 0.9.15 and 0.9.16 searches the /tmp directory for modules before using the paths in the PYTHONPATH variable, which allows local users to execute arbitrary code via a malicious module in /tmp/.",
            "cve": "CVE-2005-1632",
            "id": "pyup.io-66881",
            "more_info_path": "/vulnerabilities/CVE-2005-1632/66881",
            "specs": [
                ">=0.9.15,<=0.9.16"
            ],
            "v": ">=0.9.15,<=0.9.16"
        }
    ],
    "cheetah3": [
        {
            "advisory": "Cheetah3 version 3.2.2 replaces the outdated and insecure ``mktemp`` with ``mkstemp``.",
            "cve": "PVE-2021-37134",
            "id": "pyup.io-37134",
            "more_info_path": "/vulnerabilities/PVE-2021-37134/37134",
            "specs": [
                "<3.2.2"
            ],
            "v": "<3.2.2"
        }
    ],
    "cheroot": [
        {
            "advisory": "Cheroot 6.3.2 introduces a HTTP 400 response to a malicious 'Content-Length' in the request headers.\r\nhttps://github.com/cherrypy/cheroot/commit/040f7bf687fb2c2ae5b98d0c15de65fdb7682a30",
            "cve": "PVE-2021-39125",
            "id": "pyup.io-39125",
            "more_info_path": "/vulnerabilities/PVE-2021-39125/39125",
            "specs": [
                "<6.3.2"
            ],
            "v": "<6.3.2"
        }
    ],
    "cherrymusic": [
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in Cherry Music before 0.36.0 allows remote authenticated users to inject arbitrary web script or HTML via the playlistname field when creating a new playlist.",
            "cve": "CVE-2015-8310",
            "id": "pyup.io-42242",
            "more_info_path": "/vulnerabilities/CVE-2015-8310/42242",
            "specs": [
                "<0.36.0"
            ],
            "v": "<0.36.0"
        },
        {
            "advisory": "Directory traversal vulnerability in Cherry Music before 0.36.0 allows remote authenticated users to read arbitrary files via the \"value\" parameter to \"download.\"",
            "cve": "CVE-2015-8309",
            "id": "pyup.io-25650",
            "more_info_path": "/vulnerabilities/CVE-2015-8309/25650",
            "specs": [
                "<0.36.0"
            ],
            "v": "<0.36.0"
        }
    ],
    "cherrypy": [
        {
            "advisory": "Directory traversal vulnerability in the staticfilter component in CherryPy before 2.1.1 allows remote attackers to read arbitrary files via \"..\" sequences in unspecified vectors.",
            "cve": "CVE-2006-0847",
            "id": "pyup.io-42231",
            "more_info_path": "/vulnerabilities/CVE-2006-0847/42231",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Directory traversal vulnerability in the _get_file_path function in (1) lib/sessions.py in CherryPy 3.0.x up to 3.0.2, (2) filter/sessionfilter.py in CherryPy 2.1, and (3) filter/sessionfilter.py in CherryPy 2.x allows remote attackers to create or delete arbitrary files, and possibly read and write portions of arbitrary files, via a crafted session id in a cookie.",
            "cve": "CVE-2008-0252",
            "id": "pyup.io-54033",
            "more_info_path": "/vulnerabilities/CVE-2008-0252/54033",
            "specs": [
                ">=0,<2.1.1",
                ">=3.0,<3.0.2"
            ],
            "v": ">=0,<2.1.1,>=3.0,<3.0.2"
        }
    ],
    "chia": [
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29595",
            "id": "pyup.io-44302",
            "more_info_path": "/vulnerabilities/CVE-2021-29595/44302",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29555",
            "id": "pyup.io-44260",
            "more_info_path": "/vulnerabilities/CVE-2021-29555/44260",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29582",
            "id": "pyup.io-44289",
            "more_info_path": "/vulnerabilities/CVE-2021-29582/44289",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29609",
            "id": "pyup.io-44316",
            "more_info_path": "/vulnerabilities/CVE-2021-29609/44316",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-8177",
            "id": "pyup.io-44210",
            "more_info_path": "/vulnerabilities/CVE-2020-8177/44210",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15204",
            "id": "pyup.io-44190",
            "more_info_path": "/vulnerabilities/CVE-2020-15204/44190",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-8286",
            "id": "pyup.io-44213",
            "more_info_path": "/vulnerabilities/CVE-2020-8286/44213",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-8169",
            "id": "pyup.io-44209",
            "more_info_path": "/vulnerabilities/CVE-2020-8169/44209",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-22876",
            "id": "pyup.io-44214",
            "more_info_path": "/vulnerabilities/CVE-2021-22876/44214",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29612",
            "id": "pyup.io-44319",
            "more_info_path": "/vulnerabilities/CVE-2021-29612/44319",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29553",
            "id": "pyup.io-44258",
            "more_info_path": "/vulnerabilities/CVE-2021-29553/44258",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29561",
            "id": "pyup.io-44266",
            "more_info_path": "/vulnerabilities/CVE-2021-29561/44266",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-14155",
            "id": "pyup.io-44175",
            "more_info_path": "/vulnerabilities/CVE-2020-14155/44175",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29516",
            "id": "pyup.io-44221",
            "more_info_path": "/vulnerabilities/CVE-2021-29516/44221",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15206",
            "id": "pyup.io-44192",
            "more_info_path": "/vulnerabilities/CVE-2020-15206/44192",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29577",
            "id": "pyup.io-44284",
            "more_info_path": "/vulnerabilities/CVE-2021-29577/44284",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29601",
            "id": "pyup.io-44308",
            "more_info_path": "/vulnerabilities/CVE-2021-29601/44308",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29524",
            "id": "pyup.io-44229",
            "more_info_path": "/vulnerabilities/CVE-2021-29524/44229",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29559",
            "id": "pyup.io-44264",
            "more_info_path": "/vulnerabilities/CVE-2021-29559/44264",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37656",
            "id": "pyup.io-44348",
            "more_info_path": "/vulnerabilities/CVE-2021-37656/44348",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29544",
            "id": "pyup.io-44249",
            "more_info_path": "/vulnerabilities/CVE-2021-29544/44249",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15196",
            "id": "pyup.io-44182",
            "more_info_path": "/vulnerabilities/CVE-2020-15196/44182",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29573",
            "id": "pyup.io-44280",
            "more_info_path": "/vulnerabilities/CVE-2021-29573/44280",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29572",
            "id": "pyup.io-44279",
            "more_info_path": "/vulnerabilities/CVE-2021-29572/44279",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15203",
            "id": "pyup.io-44189",
            "more_info_path": "/vulnerabilities/CVE-2020-15203/44189",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29570",
            "id": "pyup.io-44274",
            "more_info_path": "/vulnerabilities/CVE-2021-29570/44274",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29586",
            "id": "pyup.io-44293",
            "more_info_path": "/vulnerabilities/CVE-2021-29586/44293",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29569",
            "id": "pyup.io-44275",
            "more_info_path": "/vulnerabilities/CVE-2021-29569/44275",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29611",
            "id": "pyup.io-44318",
            "more_info_path": "/vulnerabilities/CVE-2021-29611/44318",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29614",
            "id": "pyup.io-44321",
            "more_info_path": "/vulnerabilities/CVE-2021-29614/44321",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29613",
            "id": "pyup.io-44320",
            "more_info_path": "/vulnerabilities/CVE-2021-29613/44320",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29592",
            "id": "pyup.io-44299",
            "more_info_path": "/vulnerabilities/CVE-2021-29592/44299",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29560",
            "id": "pyup.io-44265",
            "more_info_path": "/vulnerabilities/CVE-2021-29560/44265",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29556",
            "id": "pyup.io-44261",
            "more_info_path": "/vulnerabilities/CVE-2021-29556/44261",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37664",
            "id": "pyup.io-44356",
            "more_info_path": "/vulnerabilities/CVE-2021-37664/44356",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29588",
            "id": "pyup.io-44295",
            "more_info_path": "/vulnerabilities/CVE-2021-29588/44295",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29606",
            "id": "pyup.io-44313",
            "more_info_path": "/vulnerabilities/CVE-2021-29606/44313",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29526",
            "id": "pyup.io-44231",
            "more_info_path": "/vulnerabilities/CVE-2021-29526/44231",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15191",
            "id": "pyup.io-44177",
            "more_info_path": "/vulnerabilities/CVE-2020-15191/44177",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37667",
            "id": "pyup.io-44359",
            "more_info_path": "/vulnerabilities/CVE-2021-37667/44359",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29608",
            "id": "pyup.io-44315",
            "more_info_path": "/vulnerabilities/CVE-2021-29608/44315",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37684",
            "id": "pyup.io-44376",
            "more_info_path": "/vulnerabilities/CVE-2021-37684/44376",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37638",
            "id": "pyup.io-44330",
            "more_info_path": "/vulnerabilities/CVE-2021-37638/44330",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-22901",
            "id": "pyup.io-44217",
            "more_info_path": "/vulnerabilities/CVE-2021-22901/44217",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-22898",
            "id": "pyup.io-44216",
            "more_info_path": "/vulnerabilities/CVE-2021-22898/44216",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29563",
            "id": "pyup.io-44268",
            "more_info_path": "/vulnerabilities/CVE-2021-29563/44268",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29562",
            "id": "pyup.io-44267",
            "more_info_path": "/vulnerabilities/CVE-2021-29562/44267",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29599",
            "id": "pyup.io-44306",
            "more_info_path": "/vulnerabilities/CVE-2021-29599/44306",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29574",
            "id": "pyup.io-44281",
            "more_info_path": "/vulnerabilities/CVE-2021-29574/44281",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29547",
            "id": "pyup.io-44252",
            "more_info_path": "/vulnerabilities/CVE-2021-29547/44252",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-26271",
            "id": "pyup.io-44208",
            "more_info_path": "/vulnerabilities/CVE-2020-26271/44208",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29523",
            "id": "pyup.io-44228",
            "more_info_path": "/vulnerabilities/CVE-2021-29523/44228",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15200",
            "id": "pyup.io-44186",
            "more_info_path": "/vulnerabilities/CVE-2020-15200/44186",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-26266",
            "id": "pyup.io-44204",
            "more_info_path": "/vulnerabilities/CVE-2020-26266/44204",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29527",
            "id": "pyup.io-44232",
            "more_info_path": "/vulnerabilities/CVE-2021-29527/44232",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29619",
            "id": "pyup.io-44326",
            "more_info_path": "/vulnerabilities/CVE-2021-29619/44326",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29603",
            "id": "pyup.io-44310",
            "more_info_path": "/vulnerabilities/CVE-2021-29603/44310",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29618",
            "id": "pyup.io-44325",
            "more_info_path": "/vulnerabilities/CVE-2021-29618/44325",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29602",
            "id": "pyup.io-44309",
            "more_info_path": "/vulnerabilities/CVE-2021-29602/44309",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29604",
            "id": "pyup.io-44311",
            "more_info_path": "/vulnerabilities/CVE-2021-29604/44311",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37689",
            "id": "pyup.io-44381",
            "more_info_path": "/vulnerabilities/CVE-2021-37689/44381",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29617",
            "id": "pyup.io-44324",
            "more_info_path": "/vulnerabilities/CVE-2021-29617/44324",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29590",
            "id": "pyup.io-44297",
            "more_info_path": "/vulnerabilities/CVE-2021-29590/44297",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29594",
            "id": "pyup.io-44301",
            "more_info_path": "/vulnerabilities/CVE-2021-29594/44301",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15210",
            "id": "pyup.io-44196",
            "more_info_path": "/vulnerabilities/CVE-2020-15210/44196",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29615",
            "id": "pyup.io-44322",
            "more_info_path": "/vulnerabilities/CVE-2021-29615/44322",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29540",
            "id": "pyup.io-44245",
            "more_info_path": "/vulnerabilities/CVE-2021-29540/44245",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29610",
            "id": "pyup.io-44317",
            "more_info_path": "/vulnerabilities/CVE-2021-29610/44317",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29593",
            "id": "pyup.io-44300",
            "more_info_path": "/vulnerabilities/CVE-2021-29593/44300",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29576",
            "id": "pyup.io-44283",
            "more_info_path": "/vulnerabilities/CVE-2021-29576/44283",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37666",
            "id": "pyup.io-44358",
            "more_info_path": "/vulnerabilities/CVE-2021-37666/44358",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29591",
            "id": "pyup.io-44298",
            "more_info_path": "/vulnerabilities/CVE-2021-29591/44298",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29533",
            "id": "pyup.io-44238",
            "more_info_path": "/vulnerabilities/CVE-2021-29533/44238",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29539",
            "id": "pyup.io-44244",
            "more_info_path": "/vulnerabilities/CVE-2021-29539/44244",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29607",
            "id": "pyup.io-44314",
            "more_info_path": "/vulnerabilities/CVE-2021-29607/44314",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29566",
            "id": "pyup.io-44271",
            "more_info_path": "/vulnerabilities/CVE-2021-29566/44271",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29616",
            "id": "pyup.io-44323",
            "more_info_path": "/vulnerabilities/CVE-2021-29616/44323",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37639",
            "id": "pyup.io-44331",
            "more_info_path": "/vulnerabilities/CVE-2021-37639/44331",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37650",
            "id": "pyup.io-44342",
            "more_info_path": "/vulnerabilities/CVE-2021-37650/44342",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37649",
            "id": "pyup.io-44341",
            "more_info_path": "/vulnerabilities/CVE-2021-37649/44341",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29600",
            "id": "pyup.io-44307",
            "more_info_path": "/vulnerabilities/CVE-2021-29600/44307",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37653",
            "id": "pyup.io-44345",
            "more_info_path": "/vulnerabilities/CVE-2021-37653/44345",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37675",
            "id": "pyup.io-44367",
            "more_info_path": "/vulnerabilities/CVE-2021-37675/44367",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15195",
            "id": "pyup.io-44181",
            "more_info_path": "/vulnerabilities/CVE-2020-15195/44181",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15213",
            "id": "pyup.io-44199",
            "more_info_path": "/vulnerabilities/CVE-2020-15213/44199",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-26267",
            "id": "pyup.io-44205",
            "more_info_path": "/vulnerabilities/CVE-2020-26267/44205",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29521",
            "id": "pyup.io-44226",
            "more_info_path": "/vulnerabilities/CVE-2021-29521/44226",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37658",
            "id": "pyup.io-44350",
            "more_info_path": "/vulnerabilities/CVE-2021-37658/44350",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37679",
            "id": "pyup.io-44371",
            "more_info_path": "/vulnerabilities/CVE-2021-37679/44371",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37680",
            "id": "pyup.io-44372",
            "more_info_path": "/vulnerabilities/CVE-2021-37680/44372",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29541",
            "id": "pyup.io-44246",
            "more_info_path": "/vulnerabilities/CVE-2021-29541/44246",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29543",
            "id": "pyup.io-44248",
            "more_info_path": "/vulnerabilities/CVE-2021-29543/44248",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29581",
            "id": "pyup.io-44288",
            "more_info_path": "/vulnerabilities/CVE-2021-29581/44288",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29598",
            "id": "pyup.io-44305",
            "more_info_path": "/vulnerabilities/CVE-2021-29598/44305",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29597",
            "id": "pyup.io-44304",
            "more_info_path": "/vulnerabilities/CVE-2021-29597/44304",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29589",
            "id": "pyup.io-44296",
            "more_info_path": "/vulnerabilities/CVE-2021-29589/44296",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29578",
            "id": "pyup.io-44285",
            "more_info_path": "/vulnerabilities/CVE-2021-29578/44285",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29587",
            "id": "pyup.io-44294",
            "more_info_path": "/vulnerabilities/CVE-2021-29587/44294",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29585",
            "id": "pyup.io-44292",
            "more_info_path": "/vulnerabilities/CVE-2021-29585/44292",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29584",
            "id": "pyup.io-44291",
            "more_info_path": "/vulnerabilities/CVE-2021-29584/44291",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15358",
            "id": "pyup.io-44203",
            "more_info_path": "/vulnerabilities/CVE-2020-15358/44203",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29583",
            "id": "pyup.io-44290",
            "more_info_path": "/vulnerabilities/CVE-2021-29583/44290",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29580",
            "id": "pyup.io-44287",
            "more_info_path": "/vulnerabilities/CVE-2021-29580/44287",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29579",
            "id": "pyup.io-44286",
            "more_info_path": "/vulnerabilities/CVE-2021-29579/44286",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15199",
            "id": "pyup.io-44185",
            "more_info_path": "/vulnerabilities/CVE-2020-15199/44185",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29571",
            "id": "pyup.io-44278",
            "more_info_path": "/vulnerabilities/CVE-2021-29571/44278",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29575",
            "id": "pyup.io-44282",
            "more_info_path": "/vulnerabilities/CVE-2021-29575/44282",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29568",
            "id": "pyup.io-44272",
            "more_info_path": "/vulnerabilities/CVE-2021-29568/44272",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2019-20838",
            "id": "pyup.io-41298",
            "more_info_path": "/vulnerabilities/CVE-2019-20838/41298",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29565",
            "id": "pyup.io-44270",
            "more_info_path": "/vulnerabilities/CVE-2021-29565/44270",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29558",
            "id": "pyup.io-44263",
            "more_info_path": "/vulnerabilities/CVE-2021-29558/44263",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29557",
            "id": "pyup.io-44262",
            "more_info_path": "/vulnerabilities/CVE-2021-29557/44262",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29548",
            "id": "pyup.io-44253",
            "more_info_path": "/vulnerabilities/CVE-2021-29548/44253",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29552",
            "id": "pyup.io-44257",
            "more_info_path": "/vulnerabilities/CVE-2021-29552/44257",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29546",
            "id": "pyup.io-44251",
            "more_info_path": "/vulnerabilities/CVE-2021-29546/44251",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29545",
            "id": "pyup.io-44250",
            "more_info_path": "/vulnerabilities/CVE-2021-29545/44250",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29549",
            "id": "pyup.io-44254",
            "more_info_path": "/vulnerabilities/CVE-2021-29549/44254",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15211",
            "id": "pyup.io-44197",
            "more_info_path": "/vulnerabilities/CVE-2020-15211/44197",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29542",
            "id": "pyup.io-44247",
            "more_info_path": "/vulnerabilities/CVE-2021-29542/44247",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29550",
            "id": "pyup.io-44255",
            "more_info_path": "/vulnerabilities/CVE-2021-29550/44255",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29536",
            "id": "pyup.io-44241",
            "more_info_path": "/vulnerabilities/CVE-2021-29536/44241",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29535",
            "id": "pyup.io-44240",
            "more_info_path": "/vulnerabilities/CVE-2021-29535/44240",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29534",
            "id": "pyup.io-44239",
            "more_info_path": "/vulnerabilities/CVE-2021-29534/44239",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37663",
            "id": "pyup.io-44355",
            "more_info_path": "/vulnerabilities/CVE-2021-37663/44355",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29532",
            "id": "pyup.io-44237",
            "more_info_path": "/vulnerabilities/CVE-2021-29532/44237",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29531",
            "id": "pyup.io-44236",
            "more_info_path": "/vulnerabilities/CVE-2021-29531/44236",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29530",
            "id": "pyup.io-44235",
            "more_info_path": "/vulnerabilities/CVE-2021-29530/44235",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29529",
            "id": "pyup.io-44234",
            "more_info_path": "/vulnerabilities/CVE-2021-29529/44234",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29528",
            "id": "pyup.io-44233",
            "more_info_path": "/vulnerabilities/CVE-2021-29528/44233",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29538",
            "id": "pyup.io-44243",
            "more_info_path": "/vulnerabilities/CVE-2021-29538/44243",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29537",
            "id": "pyup.io-44242",
            "more_info_path": "/vulnerabilities/CVE-2021-29537/44242",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29522",
            "id": "pyup.io-44227",
            "more_info_path": "/vulnerabilities/CVE-2021-29522/44227",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29520",
            "id": "pyup.io-44225",
            "more_info_path": "/vulnerabilities/CVE-2021-29520/44225",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29519",
            "id": "pyup.io-44224",
            "more_info_path": "/vulnerabilities/CVE-2021-29519/44224",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29518",
            "id": "pyup.io-44223",
            "more_info_path": "/vulnerabilities/CVE-2021-29518/44223",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29517",
            "id": "pyup.io-44222",
            "more_info_path": "/vulnerabilities/CVE-2021-29517/44222",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29515",
            "id": "pyup.io-44220",
            "more_info_path": "/vulnerabilities/CVE-2021-29515/44220",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29514",
            "id": "pyup.io-44219",
            "more_info_path": "/vulnerabilities/CVE-2021-29514/44219",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29554",
            "id": "pyup.io-44259",
            "more_info_path": "/vulnerabilities/CVE-2021-29554/44259",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29525",
            "id": "pyup.io-44230",
            "more_info_path": "/vulnerabilities/CVE-2021-29525/44230",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-8284",
            "id": "pyup.io-44212",
            "more_info_path": "/vulnerabilities/CVE-2020-8284/44212",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37691",
            "id": "pyup.io-44383",
            "more_info_path": "/vulnerabilities/CVE-2021-37691/44383",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37674",
            "id": "pyup.io-44366",
            "more_info_path": "/vulnerabilities/CVE-2021-37674/44366",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37672",
            "id": "pyup.io-44364",
            "more_info_path": "/vulnerabilities/CVE-2021-37672/44364",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37677",
            "id": "pyup.io-44369",
            "more_info_path": "/vulnerabilities/CVE-2021-37677/44369",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-26270",
            "id": "pyup.io-44207",
            "more_info_path": "/vulnerabilities/CVE-2020-26270/44207",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-26268",
            "id": "pyup.io-44206",
            "more_info_path": "/vulnerabilities/CVE-2020-26268/44206",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37670",
            "id": "pyup.io-44362",
            "more_info_path": "/vulnerabilities/CVE-2021-37670/44362",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15266",
            "id": "pyup.io-44202",
            "more_info_path": "/vulnerabilities/CVE-2020-15266/44202",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15265",
            "id": "pyup.io-44201",
            "more_info_path": "/vulnerabilities/CVE-2020-15265/44201",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15214",
            "id": "pyup.io-44200",
            "more_info_path": "/vulnerabilities/CVE-2020-15214/44200",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15212",
            "id": "pyup.io-44198",
            "more_info_path": "/vulnerabilities/CVE-2020-15212/44198",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15209",
            "id": "pyup.io-44195",
            "more_info_path": "/vulnerabilities/CVE-2020-15209/44195",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15208",
            "id": "pyup.io-44194",
            "more_info_path": "/vulnerabilities/CVE-2020-15208/44194",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15207",
            "id": "pyup.io-44193",
            "more_info_path": "/vulnerabilities/CVE-2020-15207/44193",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15205",
            "id": "pyup.io-44191",
            "more_info_path": "/vulnerabilities/CVE-2020-15205/44191",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15202",
            "id": "pyup.io-44188",
            "more_info_path": "/vulnerabilities/CVE-2020-15202/44188",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-8231",
            "id": "pyup.io-44211",
            "more_info_path": "/vulnerabilities/CVE-2020-8231/44211",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15201",
            "id": "pyup.io-44187",
            "more_info_path": "/vulnerabilities/CVE-2020-15201/44187",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15198",
            "id": "pyup.io-44184",
            "more_info_path": "/vulnerabilities/CVE-2020-15198/44184",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-22897",
            "id": "pyup.io-44215",
            "more_info_path": "/vulnerabilities/CVE-2021-22897/44215",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-13790",
            "id": "pyup.io-44174",
            "more_info_path": "/vulnerabilities/CVE-2020-13790/44174",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15197",
            "id": "pyup.io-44183",
            "more_info_path": "/vulnerabilities/CVE-2020-15197/44183",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15194",
            "id": "pyup.io-44180",
            "more_info_path": "/vulnerabilities/CVE-2020-15194/44180",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15193",
            "id": "pyup.io-44179",
            "more_info_path": "/vulnerabilities/CVE-2020-15193/44179",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15192",
            "id": "pyup.io-44178",
            "more_info_path": "/vulnerabilities/CVE-2020-15192/44178",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2020-15190",
            "id": "pyup.io-44176",
            "more_info_path": "/vulnerabilities/CVE-2020-15190/44176",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29596",
            "id": "pyup.io-44303",
            "more_info_path": "/vulnerabilities/CVE-2021-29596/44303",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29551",
            "id": "pyup.io-44256",
            "more_info_path": "/vulnerabilities/CVE-2021-29551/44256",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37678",
            "id": "pyup.io-44370",
            "more_info_path": "/vulnerabilities/CVE-2021-37678/44370",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29564",
            "id": "pyup.io-44269",
            "more_info_path": "/vulnerabilities/CVE-2021-29564/44269",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29513",
            "id": "pyup.io-44218",
            "more_info_path": "/vulnerabilities/CVE-2021-29513/44218",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37642",
            "id": "pyup.io-44334",
            "more_info_path": "/vulnerabilities/CVE-2021-37642/44334",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37690",
            "id": "pyup.io-44382",
            "more_info_path": "/vulnerabilities/CVE-2021-37690/44382",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37687",
            "id": "pyup.io-44379",
            "more_info_path": "/vulnerabilities/CVE-2021-37687/44379",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37685",
            "id": "pyup.io-44377",
            "more_info_path": "/vulnerabilities/CVE-2021-37685/44377",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37683",
            "id": "pyup.io-44375",
            "more_info_path": "/vulnerabilities/CVE-2021-37683/44375",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37682",
            "id": "pyup.io-44374",
            "more_info_path": "/vulnerabilities/CVE-2021-37682/44374",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37673",
            "id": "pyup.io-44365",
            "more_info_path": "/vulnerabilities/CVE-2021-37673/44365",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37669",
            "id": "pyup.io-44361",
            "more_info_path": "/vulnerabilities/CVE-2021-37669/44361",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37668",
            "id": "pyup.io-44360",
            "more_info_path": "/vulnerabilities/CVE-2021-37668/44360",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37665",
            "id": "pyup.io-44357",
            "more_info_path": "/vulnerabilities/CVE-2021-37665/44357",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37688",
            "id": "pyup.io-44380",
            "more_info_path": "/vulnerabilities/CVE-2021-37688/44380",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37686",
            "id": "pyup.io-44378",
            "more_info_path": "/vulnerabilities/CVE-2021-37686/44378",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37681",
            "id": "pyup.io-44373",
            "more_info_path": "/vulnerabilities/CVE-2021-37681/44373",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37676",
            "id": "pyup.io-44368",
            "more_info_path": "/vulnerabilities/CVE-2021-37676/44368",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37671",
            "id": "pyup.io-44363",
            "more_info_path": "/vulnerabilities/CVE-2021-37671/44363",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37652",
            "id": "pyup.io-44344",
            "more_info_path": "/vulnerabilities/CVE-2021-37652/44344",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37648",
            "id": "pyup.io-44340",
            "more_info_path": "/vulnerabilities/CVE-2021-37648/44340",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37662",
            "id": "pyup.io-44354",
            "more_info_path": "/vulnerabilities/CVE-2021-37662/44354",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37661",
            "id": "pyup.io-44353",
            "more_info_path": "/vulnerabilities/CVE-2021-37661/44353",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37659",
            "id": "pyup.io-44351",
            "more_info_path": "/vulnerabilities/CVE-2021-37659/44351",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37657",
            "id": "pyup.io-44349",
            "more_info_path": "/vulnerabilities/CVE-2021-37657/44349",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37655",
            "id": "pyup.io-44347",
            "more_info_path": "/vulnerabilities/CVE-2021-37655/44347",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37654",
            "id": "pyup.io-44346",
            "more_info_path": "/vulnerabilities/CVE-2021-37654/44346",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37651",
            "id": "pyup.io-44343",
            "more_info_path": "/vulnerabilities/CVE-2021-37651/44343",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37646",
            "id": "pyup.io-44338",
            "more_info_path": "/vulnerabilities/CVE-2021-37646/44338",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37645",
            "id": "pyup.io-44337",
            "more_info_path": "/vulnerabilities/CVE-2021-37645/44337",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37644",
            "id": "pyup.io-44336",
            "more_info_path": "/vulnerabilities/CVE-2021-37644/44336",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37641",
            "id": "pyup.io-44333",
            "more_info_path": "/vulnerabilities/CVE-2021-37641/44333",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37635",
            "id": "pyup.io-44327",
            "more_info_path": "/vulnerabilities/CVE-2021-37635/44327",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37647",
            "id": "pyup.io-44339",
            "more_info_path": "/vulnerabilities/CVE-2021-37647/44339",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37643",
            "id": "pyup.io-44335",
            "more_info_path": "/vulnerabilities/CVE-2021-37643/44335",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37637",
            "id": "pyup.io-44329",
            "more_info_path": "/vulnerabilities/CVE-2021-37637/44329",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37660",
            "id": "pyup.io-44352",
            "more_info_path": "/vulnerabilities/CVE-2021-37660/44352",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37640",
            "id": "pyup.io-44332",
            "more_info_path": "/vulnerabilities/CVE-2021-37640/44332",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-37636",
            "id": "pyup.io-44328",
            "more_info_path": "/vulnerabilities/CVE-2021-37636/44328",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia 2.4.0 updates Tensorflow to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-29605",
            "id": "pyup.io-44312",
            "more_info_path": "/vulnerabilities/CVE-2021-29605/44312",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23559",
            "id": "pyup.io-46849",
            "more_info_path": "/vulnerabilities/CVE-2022-23559/46849",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23562",
            "id": "pyup.io-46852",
            "more_info_path": "/vulnerabilities/CVE-2022-23562/46852",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23565",
            "id": "pyup.io-46855",
            "more_info_path": "/vulnerabilities/CVE-2022-23565/46855",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23573",
            "id": "pyup.io-46863",
            "more_info_path": "/vulnerabilities/CVE-2022-23573/46863",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23575",
            "id": "pyup.io-46865",
            "more_info_path": "/vulnerabilities/CVE-2022-23575/46865",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23591",
            "id": "pyup.io-46880",
            "more_info_path": "/vulnerabilities/CVE-2022-23591/46880",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41209",
            "id": "pyup.io-46810",
            "more_info_path": "/vulnerabilities/CVE-2021-41209/46810",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-22925",
            "id": "pyup.io-46795",
            "more_info_path": "/vulnerabilities/CVE-2021-22925/46795",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41211",
            "id": "pyup.io-46812",
            "more_info_path": "/vulnerabilities/CVE-2021-41211/46812",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-22922",
            "id": "pyup.io-46792",
            "more_info_path": "/vulnerabilities/CVE-2021-22922/46792",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-22924",
            "id": "pyup.io-46794",
            "more_info_path": "/vulnerabilities/CVE-2021-22924/46794",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41221",
            "id": "pyup.io-46822",
            "more_info_path": "/vulnerabilities/CVE-2021-41221/46822",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41196",
            "id": "pyup.io-46797",
            "more_info_path": "/vulnerabilities/CVE-2021-41196/46797",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41200",
            "id": "pyup.io-46801",
            "more_info_path": "/vulnerabilities/CVE-2021-41200/46801",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41219",
            "id": "pyup.io-46820",
            "more_info_path": "/vulnerabilities/CVE-2021-41219/46820",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23563",
            "id": "pyup.io-46853",
            "more_info_path": "/vulnerabilities/CVE-2022-23563/46853",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23583",
            "id": "pyup.io-46873",
            "more_info_path": "/vulnerabilities/CVE-2022-23583/46873",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-22923",
            "id": "pyup.io-46793",
            "more_info_path": "/vulnerabilities/CVE-2021-22923/46793",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41206",
            "id": "pyup.io-46807",
            "more_info_path": "/vulnerabilities/CVE-2021-41206/46807",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41208",
            "id": "pyup.io-46809",
            "more_info_path": "/vulnerabilities/CVE-2021-41208/46809",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41216",
            "id": "pyup.io-46817",
            "more_info_path": "/vulnerabilities/CVE-2021-41216/46817",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41203",
            "id": "pyup.io-46804",
            "more_info_path": "/vulnerabilities/CVE-2021-41203/46804",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-10531",
            "id": "pyup.io-46791",
            "more_info_path": "/vulnerabilities/CVE-2020-10531/46791",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21739",
            "id": "pyup.io-46844",
            "more_info_path": "/vulnerabilities/CVE-2022-21739/46844",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21729",
            "id": "pyup.io-46834",
            "more_info_path": "/vulnerabilities/CVE-2022-21729/46834",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23567",
            "id": "pyup.io-46857",
            "more_info_path": "/vulnerabilities/CVE-2022-23567/46857",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23569",
            "id": "pyup.io-46859",
            "more_info_path": "/vulnerabilities/CVE-2022-23569/46859",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41199",
            "id": "pyup.io-46800",
            "more_info_path": "/vulnerabilities/CVE-2021-41199/46800",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21730",
            "id": "pyup.io-46835",
            "more_info_path": "/vulnerabilities/CVE-2022-21730/46835",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41215",
            "id": "pyup.io-46816",
            "more_info_path": "/vulnerabilities/CVE-2021-41215/46816",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23595",
            "id": "pyup.io-46881",
            "more_info_path": "/vulnerabilities/CVE-2022-23595/46881",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23589",
            "id": "pyup.io-46879",
            "more_info_path": "/vulnerabilities/CVE-2022-23589/46879",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23588",
            "id": "pyup.io-46878",
            "more_info_path": "/vulnerabilities/CVE-2022-23588/46878",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23587",
            "id": "pyup.io-46877",
            "more_info_path": "/vulnerabilities/CVE-2022-23587/46877",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21740",
            "id": "pyup.io-46845",
            "more_info_path": "/vulnerabilities/CVE-2022-21740/46845",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41227",
            "id": "pyup.io-46828",
            "more_info_path": "/vulnerabilities/CVE-2021-41227/46828",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23586",
            "id": "pyup.io-46876",
            "more_info_path": "/vulnerabilities/CVE-2022-23586/46876",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23585",
            "id": "pyup.io-46875",
            "more_info_path": "/vulnerabilities/CVE-2022-23585/46875",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23584",
            "id": "pyup.io-46874",
            "more_info_path": "/vulnerabilities/CVE-2022-23584/46874",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41214",
            "id": "pyup.io-46815",
            "more_info_path": "/vulnerabilities/CVE-2021-41214/46815",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23582",
            "id": "pyup.io-46872",
            "more_info_path": "/vulnerabilities/CVE-2022-23582/46872",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23581",
            "id": "pyup.io-46871",
            "more_info_path": "/vulnerabilities/CVE-2022-23581/46871",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21738",
            "id": "pyup.io-46843",
            "more_info_path": "/vulnerabilities/CVE-2022-21738/46843",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23580",
            "id": "pyup.io-46870",
            "more_info_path": "/vulnerabilities/CVE-2022-23580/46870",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23579",
            "id": "pyup.io-46869",
            "more_info_path": "/vulnerabilities/CVE-2022-23579/46869",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21733",
            "id": "pyup.io-46838",
            "more_info_path": "/vulnerabilities/CVE-2022-21733/46838",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23578",
            "id": "pyup.io-46868",
            "more_info_path": "/vulnerabilities/CVE-2022-23578/46868",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23577",
            "id": "pyup.io-46867",
            "more_info_path": "/vulnerabilities/CVE-2022-23577/46867",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23576",
            "id": "pyup.io-46866",
            "more_info_path": "/vulnerabilities/CVE-2022-23576/46866",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23574",
            "id": "pyup.io-46864",
            "more_info_path": "/vulnerabilities/CVE-2022-23574/46864",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23571",
            "id": "pyup.io-46861",
            "more_info_path": "/vulnerabilities/CVE-2022-23571/46861",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23570",
            "id": "pyup.io-46860",
            "more_info_path": "/vulnerabilities/CVE-2022-23570/46860",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23566",
            "id": "pyup.io-46856",
            "more_info_path": "/vulnerabilities/CVE-2022-23566/46856",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23572",
            "id": "pyup.io-46862",
            "more_info_path": "/vulnerabilities/CVE-2022-23572/46862",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23564",
            "id": "pyup.io-46854",
            "more_info_path": "/vulnerabilities/CVE-2022-23564/46854",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23561",
            "id": "pyup.io-46851",
            "more_info_path": "/vulnerabilities/CVE-2022-23561/46851",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23560",
            "id": "pyup.io-46850",
            "more_info_path": "/vulnerabilities/CVE-2022-23560/46850",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23558",
            "id": "pyup.io-46848",
            "more_info_path": "/vulnerabilities/CVE-2022-23558/46848",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23557",
            "id": "pyup.io-46847",
            "more_info_path": "/vulnerabilities/CVE-2022-23557/46847",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21725",
            "id": "pyup.io-46830",
            "more_info_path": "/vulnerabilities/CVE-2022-21725/46830",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21732",
            "id": "pyup.io-46837",
            "more_info_path": "/vulnerabilities/CVE-2022-21732/46837",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21728",
            "id": "pyup.io-46833",
            "more_info_path": "/vulnerabilities/CVE-2022-21728/46833",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21737",
            "id": "pyup.io-46842",
            "more_info_path": "/vulnerabilities/CVE-2022-21737/46842",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23568",
            "id": "pyup.io-46858",
            "more_info_path": "/vulnerabilities/CVE-2022-23568/46858",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21731",
            "id": "pyup.io-46836",
            "more_info_path": "/vulnerabilities/CVE-2022-21731/46836",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21726",
            "id": "pyup.io-46831",
            "more_info_path": "/vulnerabilities/CVE-2022-21726/46831",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21741",
            "id": "pyup.io-46846",
            "more_info_path": "/vulnerabilities/CVE-2022-21741/46846",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21735",
            "id": "pyup.io-46840",
            "more_info_path": "/vulnerabilities/CVE-2022-21735/46840",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21736",
            "id": "pyup.io-46841",
            "more_info_path": "/vulnerabilities/CVE-2022-21736/46841",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21727",
            "id": "pyup.io-46832",
            "more_info_path": "/vulnerabilities/CVE-2022-21727/46832",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21734",
            "id": "pyup.io-46839",
            "more_info_path": "/vulnerabilities/CVE-2022-21734/46839",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41224",
            "id": "pyup.io-46825",
            "more_info_path": "/vulnerabilities/CVE-2021-41224/46825",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41212",
            "id": "pyup.io-46813",
            "more_info_path": "/vulnerabilities/CVE-2021-41212/46813",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41222",
            "id": "pyup.io-46823",
            "more_info_path": "/vulnerabilities/CVE-2021-41222/46823",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41198",
            "id": "pyup.io-46799",
            "more_info_path": "/vulnerabilities/CVE-2021-41198/46799",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41195",
            "id": "pyup.io-46796",
            "more_info_path": "/vulnerabilities/CVE-2021-41195/46796",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41228",
            "id": "pyup.io-46829",
            "more_info_path": "/vulnerabilities/CVE-2021-41228/46829",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41225",
            "id": "pyup.io-46826",
            "more_info_path": "/vulnerabilities/CVE-2021-41225/46826",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41217",
            "id": "pyup.io-46818",
            "more_info_path": "/vulnerabilities/CVE-2021-41217/46818",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41202",
            "id": "pyup.io-46803",
            "more_info_path": "/vulnerabilities/CVE-2021-41202/46803",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41205",
            "id": "pyup.io-46806",
            "more_info_path": "/vulnerabilities/CVE-2021-41205/46806",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41223",
            "id": "pyup.io-46824",
            "more_info_path": "/vulnerabilities/CVE-2021-41223/46824",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41210",
            "id": "pyup.io-46811",
            "more_info_path": "/vulnerabilities/CVE-2021-41210/46811",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41220",
            "id": "pyup.io-46821",
            "more_info_path": "/vulnerabilities/CVE-2021-41220/46821",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41218",
            "id": "pyup.io-46819",
            "more_info_path": "/vulnerabilities/CVE-2021-41218/46819",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41207",
            "id": "pyup.io-46808",
            "more_info_path": "/vulnerabilities/CVE-2021-41207/46808",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41213",
            "id": "pyup.io-46814",
            "more_info_path": "/vulnerabilities/CVE-2021-41213/46814",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41226",
            "id": "pyup.io-46827",
            "more_info_path": "/vulnerabilities/CVE-2021-41226/46827",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41204",
            "id": "pyup.io-46805",
            "more_info_path": "/vulnerabilities/CVE-2021-41204/46805",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41201",
            "id": "pyup.io-46802",
            "more_info_path": "/vulnerabilities/CVE-2021-41201/46802",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        },
        {
            "advisory": "Chia versions 2.5.0 and prior require as minimum dependency TensorFlow v2.6.0 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41197",
            "id": "pyup.io-46798",
            "more_info_path": "/vulnerabilities/CVE-2021-41197/46798",
            "specs": [
                "<=2.5.0"
            ],
            "v": "<=2.5.0"
        }
    ],
    "chia-blockchain": [
        {
            "advisory": "Consideration of the new consensus algorithm in chia-blockchain version 1.0beta19 resulted in a much higher security level against all attacks.",
            "cve": "PVE-2021-39444",
            "id": "pyup.io-39444",
            "more_info_path": "/vulnerabilities/PVE-2021-39444/39444",
            "specs": [
                "<1.0b19"
            ],
            "v": "<1.0b19"
        },
        {
            "advisory": "Chia-blockchain 1.0b27 updates its GUI to handle CVE-2020-28477.\r\nhttps://github.com/Chia-Network/chia-blockchain/commit/45c85c0030a9b07bd3d07fc0e7f7afc540b53009",
            "cve": "CVE-2020-28477",
            "id": "pyup.io-42341",
            "more_info_path": "/vulnerabilities/CVE-2020-28477/42341",
            "specs": [
                "<1.0b27"
            ],
            "v": "<1.0b27"
        },
        {
            "advisory": "Chia-blockchain 1.0b27 updates its dependency 'pyyaml' to v5.4.1 to include a security fix.\r\nhttps://github.com/Chia-Network/chia-blockchain/commit/c3eae20b877a85eface0d4043abb5777fad3acf4",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-42367",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/42367",
            "specs": [
                "<1.0b27"
            ],
            "v": "<1.0b27"
        },
        {
            "advisory": "Chia-blockchain 1.0beta10 includes various vulnerability fixes.",
            "cve": "PVE-2021-38700",
            "id": "pyup.io-38700",
            "more_info_path": "/vulnerabilities/PVE-2021-38700/38700",
            "specs": [
                "<1.0beta10"
            ],
            "v": "<1.0beta10"
        },
        {
            "advisory": "Node peers in chia-blockchain 1.0beta14 are gossiped between nodes with logic to keep connected nodes on disparate internet networks to partially protect from eclipse attacks.",
            "cve": "PVE-2021-38844",
            "id": "pyup.io-38844",
            "more_info_path": "/vulnerabilities/PVE-2021-38844/38844",
            "specs": [
                "<1.0beta14"
            ],
            "v": "<1.0beta14"
        },
        {
            "advisory": "Chia-blockchain 1.0beta8 removes the ability to pass in sk_seed to plotting. This increases security.",
            "cve": "PVE-2021-38582",
            "id": "pyup.io-38582",
            "more_info_path": "/vulnerabilities/PVE-2021-38582/38582",
            "specs": [
                "<1.0beta8"
            ],
            "v": "<1.0beta8"
        },
        {
            "advisory": "Chia-blockchain 1.0rc5 updates its dependency 'aiohttp' to version '3.7.4' to include a security fix.\r\nhttps://github.com/Chia-Network/chia-blockchain/commit/f0a598b1a592ce4d7a8981b1b372e75452d8ea11\r\nhttps://github.com/advisories/GHSA-v6wp-4m6f-gcjg",
            "cve": "CVE-2021-21330",
            "id": "pyup.io-59386",
            "more_info_path": "/vulnerabilities/CVE-2021-21330/59386",
            "specs": [
                "<1.0rc5"
            ],
            "v": "<1.0rc5"
        },
        {
            "advisory": "Chia-blockchain 1.0rc6 improves defense against many DDoS attacks by rate limiting for the full node.\r\nhttps://github.com/Chia-Network/chia-blockchain/pull/1259",
            "cve": "PVE-2021-39703",
            "id": "pyup.io-39703",
            "more_info_path": "/vulnerabilities/PVE-2021-39703/39703",
            "specs": [
                "<1.0rc6"
            ],
            "v": "<1.0rc6"
        },
        {
            "advisory": "Chia-blockchain 1.3.2 updates its dependency 'OpenSSL' to include a fix for a DoS vulnerability.\r\nhttps://github.com/Chia-Network/chia-blockchain/pull/10988\r\nhttps://github.com/Chia-Network/chia-blockchain/pull/10991",
            "cve": "CVE-2022-0778",
            "id": "pyup.io-59381",
            "more_info_path": "/vulnerabilities/CVE-2022-0778/59381",
            "specs": [
                "<1.3.2"
            ],
            "v": "<1.3.2"
        },
        {
            "advisory": "Chia-blockchain 1.4.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/Chia-Network/chia-blockchain/pull/11324",
            "cve": "PVE-2023-59663",
            "id": "pyup.io-59663",
            "more_info_path": "/vulnerabilities/PVE-2023-59663/59663",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Chia-blockchain 1.5.0 includes a fix for CVE-2022-36447: Tokens previously minted on the Chia blockchain using the 'CAT1' standard can be inflated in arbitrary amounts by any holder of the token. Total amount of the token can be increased as high as the malicious actor pleases. This is true for every 'CAT1' on the Chia blockchain, regardless of issuance rules. This attack is auditable on-chain, so maliciously altered coins can potentially be \"marked\" by off-chain observers as malicious.",
            "cve": "CVE-2022-36447",
            "id": "pyup.io-50737",
            "more_info_path": "/vulnerabilities/CVE-2022-36447/50737",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        },
        {
            "advisory": "Chia-blockchain 1.8.0 includes unspecified critical security updates.\r\nhttps://www.chia.net/2023/05/03/version-1-8-0-release",
            "cve": "PVE-2024-63739",
            "id": "pyup.io-63739",
            "more_info_path": "/vulnerabilities/PVE-2024-63739/63739",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        },
        {
            "advisory": "Chia-blockchain 1.8.1rc4 updates its NPM dependency 'Electron' to 22.3.7 to include security fixes.",
            "cve": "CVE-2023-2134",
            "id": "pyup.io-64105",
            "more_info_path": "/vulnerabilities/CVE-2023-2134/64105",
            "specs": [
                "<1.8.1rc4"
            ],
            "v": "<1.8.1rc4"
        },
        {
            "advisory": "Chia-blockchain 1.8.1rc4 updates its NPM dependency 'Electron' to 22.3.7 to include security fixes.",
            "cve": "CVE-2023-2136",
            "id": "pyup.io-64107",
            "more_info_path": "/vulnerabilities/CVE-2023-2136/64107",
            "specs": [
                "<1.8.1rc4"
            ],
            "v": "<1.8.1rc4"
        },
        {
            "advisory": "Chia-blockchain 1.8.1rc4 updates its NPM dependency 'Electron' to 22.3.7 to include security fixes.",
            "cve": "CVE-2023-2135",
            "id": "pyup.io-64106",
            "more_info_path": "/vulnerabilities/CVE-2023-2135/64106",
            "specs": [
                "<1.8.1rc4"
            ],
            "v": "<1.8.1rc4"
        },
        {
            "advisory": "Chia-blockchain 1.8.1rc4 updates its NPM dependency 'Electron' to 22.3.7 to include security fixes.",
            "cve": "CVE-2023-2033",
            "id": "pyup.io-63738",
            "more_info_path": "/vulnerabilities/CVE-2023-2033/63738",
            "specs": [
                "<1.8.1rc4"
            ],
            "v": "<1.8.1rc4"
        },
        {
            "advisory": "Chia-blockchain 1.8.1rc4 updates its NPM dependency 'Electron' to 22.3.7 to include security fixes.",
            "cve": "CVE-2023-2133",
            "id": "pyup.io-64104",
            "more_info_path": "/vulnerabilities/CVE-2023-2133/64104",
            "specs": [
                "<1.8.1rc4"
            ],
            "v": "<1.8.1rc4"
        },
        {
            "advisory": "Chia-blockchain 2.0.0rc4 updates its NPM dependency 'Electron' to 25.4.0 to include security fixes.\r\nhttps://github.com/Chia-Network/chia-blockchain-gui/pull/1976",
            "cve": "CVE-2023-3728",
            "id": "pyup.io-64108",
            "more_info_path": "/vulnerabilities/CVE-2023-3728/64108",
            "specs": [
                "<2.0.0rc4"
            ],
            "v": "<2.0.0rc4"
        },
        {
            "advisory": "Chia-blockchain 2.0.0rc4 updates its NPM dependency 'Electron' to 25.4.0 to include security fixes.\r\nhttps://github.com/Chia-Network/chia-blockchain-gui/pull/1976",
            "cve": "CVE-2023-3732",
            "id": "pyup.io-63735",
            "more_info_path": "/vulnerabilities/CVE-2023-3732/63735",
            "specs": [
                "<2.0.0rc4"
            ],
            "v": "<2.0.0rc4"
        },
        {
            "advisory": "Chia-blockchain 2.0.0rc4 updates its NPM dependency 'Electron' to 25.4.0 to include security fixes.\r\nhttps://github.com/Chia-Network/chia-blockchain-gui/pull/1976",
            "cve": "CVE-2023-3730",
            "id": "pyup.io-64109",
            "more_info_path": "/vulnerabilities/CVE-2023-3730/64109",
            "specs": [
                "<2.0.0rc4"
            ],
            "v": "<2.0.0rc4"
        },
        {
            "advisory": "Chia-blockchain 2.1.0 updates its NPM dependency 'Electron' to 26.2.1 to include a security fix.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-63732",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/63732",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        }
    ],
    "chiapos": [
        {
            "advisory": "Chiapos 1.0.12b3 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/Chia-Network/chiapos/pull/349",
            "cve": "PVE-2023-59535",
            "id": "pyup.io-59535",
            "more_info_path": "/vulnerabilities/PVE-2023-59535/59535",
            "specs": [
                "<1.0.12b3"
            ],
            "v": "<1.0.12b3"
        }
    ],
    "chiavdf": [
        {
            "advisory": "Chiavdf 1.0 includes a fix to prevent potential grinding attacks.\r\nhttps://github.com/Chia-Network/chiavdf/commit/2f2dc55b8c11597d0674a1f347bfbefd0efcafa3",
            "cve": "PVE-2021-39691",
            "id": "pyup.io-39691",
            "more_info_path": "/vulnerabilities/PVE-2021-39691/39691",
            "specs": [
                "<1.0"
            ],
            "v": "<1.0"
        }
    ],
    "chinaski": [
        {
            "advisory": "Chinaski 0.0.2 includes a fix for a REDoS vulnerability.\r\nhttps://github.com/w0rmr1d3r/chinaski/pull/5",
            "cve": "PVE-2023-53495",
            "id": "pyup.io-53495",
            "more_info_path": "/vulnerabilities/PVE-2023-53495/53495",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        }
    ],
    "chinilla-blockchain": [
        {
            "advisory": "Chinilla-blockchain 1.2.0 includes a fix for CVE-2022-36447, where in tokens previously minted on the Chinilla blockchain using the CAT1 standard can be inflated in arbitrary amounts by any holder of the token. Total amount of the token can be increased as high as the malicious actor pleases. This is true for every CAT1 on the Chinilla blockchain, regardless of issuance rules. This attack is auditable on-chain, so maliciously altered coins can potentially be \"marked\" by off-chain observers as malicious.",
            "cve": "CVE-2022-36447",
            "id": "pyup.io-52641",
            "more_info_path": "/vulnerabilities/CVE-2022-36447/52641",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "chipsec": [
        {
            "advisory": "Chipsec 1.11.0 updates its dependency 'flask' to versions '>=2.2.5' to include a security fix.",
            "cve": "CVE-2023-30861",
            "id": "pyup.io-58853",
            "more_info_path": "/vulnerabilities/CVE-2023-30861/58853",
            "specs": [
                "<1.11.0"
            ],
            "v": "<1.11.0"
        }
    ],
    "choochoo": [
        {
            "advisory": "Choochoo 0.40.0 updates its NPM dependency 'lodash' to 4.17.21 to include security fixes.",
            "cve": "CVE-2020-28500",
            "id": "pyup.io-49116",
            "more_info_path": "/vulnerabilities/CVE-2020-28500/49116",
            "specs": [
                "<0.40.0"
            ],
            "v": "<0.40.0"
        },
        {
            "advisory": "Choochoo 0.40.0 updates its NPM dependency 'lodash' to 4.17.21 to include security fixes.",
            "cve": "CVE-2021-23337",
            "id": "pyup.io-41273",
            "more_info_path": "/vulnerabilities/CVE-2021-23337/41273",
            "specs": [
                "<0.40.0"
            ],
            "v": "<0.40.0"
        }
    ],
    "chuanhuchatgpt": [
        {
            "advisory": "Chuanhuchatgpt is vulnerable to an unrestricted file upload vulnerability due to insufficient validation of uploaded file types in its '/upload' endpoint. Specifically, the 'handle_file_upload' function does not sanitize or validate the file extension or content type of uploaded files, allowing attackers to upload files with arbitrary extensions, including HTML files containing XSS payloads and Python files. This vulnerability could lead to stored XSS attacks and potentially result in remote code execution (RCE) on the server hosting the application. The PyPI package is a fork of the vulnerable package GaiZhenbiao/ChuanhuChatGPT.",
            "cve": "CVE-2024-5278",
            "id": "pyup.io-71785",
            "more_info_path": "/vulnerabilities/CVE-2024-5278/71785",
            "specs": [
                "<=3.2.5"
            ],
            "v": "<=3.2.5"
        },
        {
            "advisory": "A timing attack vulnerability exists in the gaizhenbiao/chuanhuchatgpt repository, specifically within the password comparison logic. The vulnerability is present in version 20240310 of the software, where passwords are compared using the '=' operator in Python. This method of comparison allows an attacker to guess passwords based on the timing of each character's comparison. The issue arises from the code segment that checks a password for a particular username, which can lead to the exposure of sensitive information to an unauthorized actor. An attacker exploiting this vulnerability could potentially guess user passwords, compromising the security of the system. The PyPI package is a fork of the vulnerable package GaiZhenbiao/ChuanhuChatGPT.",
            "cve": "CVE-2024-5124",
            "id": "pyup.io-71784",
            "more_info_path": "/vulnerabilities/CVE-2024-5124/71784",
            "specs": [
                "<=3.2.5"
            ],
            "v": "<=3.2.5"
        }
    ],
    "cif2cell": [
        {
            "advisory": "Cif2cell 1.0.12 includes a fix for a code injection vulnerability related to vectors/matrices input from the command line.\r\nhttps://github.com/torbjornbjorkman/cif2cell/commit/53341d96b7967358799f6955643bd3683dbbad9e",
            "cve": "PVE-2023-61608",
            "id": "pyup.io-61608",
            "more_info_path": "/vulnerabilities/PVE-2023-61608/61608",
            "specs": [
                "<1.0.12"
            ],
            "v": "<1.0.12"
        }
    ],
    "ciftify": [
        {
            "advisory": "Ciftify 2.3.3 includes a security patch for the function '__read_settings' in 'ciftify/utils.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/edickie/ciftify/commit/7ac66dc2efc78bae272a0e1e713c81756f780969#diff-d55ace9e33dabdeba89768d93ae8fe97cf6d2ba4936fc5ab472b7bf749270b63",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41312",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41312",
            "specs": [
                "<2.3.3"
            ],
            "v": "<2.3.3"
        }
    ],
    "cinder": [
        {
            "advisory": "Cinder versions 14.1.0, 15.2.0 and 16.1.0 include a fix for CVE-2020-10755: An insecure-credentials flaw was found in all openstack-cinder versions before openstack-cinder 14.1.0, all openstack-cinder 15.x.x versions before openstack-cinder 15.2.0 and all openstack-cinder 16.x.x versions before openstack-cinder 16.1.0. When using openstack-cinder with the Dell EMC ScaleIO or VxFlex OS backend storage driver, credentials for the entire backend are exposed in the 'connection_info' element in all Block Storage v3 Attachments API calls containing that element. This flaw enables an end-user to create a volume, make an API call to show the attachment detail information, and retrieve a username and password that may be used to connect to another user's volume. Additionally, these credentials are valid for the ScaleIO or VxFlex OS Management API.\r\nhttps://wiki.openstack.org/wiki/OSSN/OSSN-0086",
            "cve": "CVE-2020-10755",
            "id": "pyup.io-38408",
            "more_info_path": "/vulnerabilities/CVE-2020-10755/38408",
            "specs": [
                "<14.1.0",
                ">=15.0.0.0rc1,<15.2.0",
                ">=16.0.0.0b1,<16.1.0"
            ],
            "v": "<14.1.0,>=15.0.0.0rc1,<15.2.0,>=16.0.0.0b1,<16.1.0"
        },
        {
            "advisory": "Cinder 19.1.2, 20.0.2 and 21.0.0 include a fix for CVE-2022-47951: An issue was discovered in OpenStack Cinder before 19.1.2, 20.x before 20.0.2, and 21.0.0; Glance before 23.0.1, 24.x before 24.1.1, and 25.0.0; and Nova before 24.1.2, 25.x before 25.0.2, and 26.0.0. By supplying a specially created VMDK flat image that references a specific backing file path, an authenticated user may convince systems to return a copy of that file's contents from the server, resulting in unauthorized access to potentially sensitive data.\r\nhttps://security.openstack.org/ossa/OSSA-2023-002.html",
            "cve": "CVE-2022-47951",
            "id": "pyup.io-52929",
            "more_info_path": "/vulnerabilities/CVE-2022-47951/52929",
            "specs": [
                "<19.1.2",
                ">=20.0.0.0rc1,<20.0.2",
                ">=21.0.0.0rc1,<21.0.0"
            ],
            "v": "<19.1.2,>=20.0.0.0rc1,<20.0.2,>=21.0.0.0rc1,<21.0.0"
        },
        {
            "advisory": "A security flaw in affected versions of OpenStack Cinder allows arbitrary file access via custom QCOW2 external data. An authenticated user can supply a crafted QCOW2 image that references a specific data file path, convincing systems to return a copy of that file's contents from the server. This results in unauthorized access to potentially sensitive data.",
            "cve": "CVE-2024-32498",
            "id": "pyup.io-72147",
            "more_info_path": "/vulnerabilities/CVE-2024-32498/72147",
            "specs": [
                "<25.0.0.0rc1"
            ],
            "v": "<25.0.0.0rc1"
        },
        {
            "advisory": "The image parser in OpenStack Cinder 7.0.2 and 8.0.0 through 8.1.1; Glance before 11.0.1 and 12.0.0; and Nova before 12.0.4 and 13.0.0 does not properly limit qemu-img calls, which might allow attackers to cause a denial of service (memory and disk consumption) via a crafted disk image.",
            "cve": "CVE-2015-5162",
            "id": "pyup.io-35629",
            "more_info_path": "/vulnerabilities/CVE-2015-5162/35629",
            "specs": [
                "<7.0.2",
                ">=8.0.0,<8.1.1"
            ],
            "v": "<7.0.2,>=8.0.0,<8.1.1"
        },
        {
            "advisory": "OpenStack Cinder before 2014.1.5 (icehouse), 2014.2.x before 2014.2.4 (juno), and 2015.1.x before 2015.1.1 (kilo) allows remote authenticated users to read arbitrary files via a crafted qcow2 signature in an image to the upload-to-image command.",
            "cve": "CVE-2015-1851",
            "id": "pyup.io-70457",
            "more_info_path": "/vulnerabilities/CVE-2015-1851/70457",
            "specs": [
                ">2010,<2015.1.1"
            ],
            "v": ">2010,<2015.1.1"
        },
        {
            "advisory": "The OpenStack Nova (python-nova) package 1:2013.2.3-0 before 1:2013.2.3-0ubuntu1.2 and 1:2014.1-0 before 1:2014.1-0ubuntu1.2 and Openstack Cinder (python-cinder) package 1:2013.2.3-0 before 1:2013.2.3-0ubuntu1.1 and 1:2014.1-0 before 1:2014.1-0ubuntu1.1 for Ubuntu 13.10 and 14.04 LTS does not properly set the sudo configuration, which makes it easier for attackers to gain privileges by leveraging another vulnerability.",
            "cve": "CVE-2013-1068",
            "id": "pyup.io-25651",
            "more_info_path": "/vulnerabilities/CVE-2013-1068/25651",
            "specs": [
                ">=2000,<2013.2.3"
            ],
            "v": ">=2000,<2013.2.3"
        },
        {
            "advisory": "The (1) GlusterFS and (2) Linux Smbfs drivers in OpenStack Cinder before 2014.1.3 allows remote authenticated users to obtain file data from the Cinder-volume host by cloning and attaching a volume with a crafted qcow2 header.",
            "cve": "CVE-2014-3641",
            "id": "pyup.io-35566",
            "more_info_path": "/vulnerabilities/CVE-2014-3641/35566",
            "specs": [
                ">=2010,<2014.1.3"
            ],
            "v": ">=2010,<2014.1.3"
        },
        {
            "advisory": "The clear_volume function in LVMVolumeDriver driver in OpenStack Cinder 2013.1.1 through 2013.1.2 does not properly clear data when deleting a snapshot, which allows local users to obtain sensitive information via unspecified vectors.",
            "cve": "CVE-2013-4183",
            "id": "pyup.io-68017",
            "more_info_path": "/vulnerabilities/CVE-2013-4183/68017",
            "specs": [
                ">=2012,<2013.1.3"
            ],
            "v": ">=2012,<2013.1.3"
        },
        {
            "advisory": "The (1) backup (api/contrib/backups.py) and (2) volume transfer (contrib/volume_transfer.py) APIs in OpenStack Cinder Grizzly 2013.1.3 and earlier allows remote attackers to cause a denial of service (resource consumption and crash) via an XML Entity Expansion (XEE) attack. NOTE: this issue is due to an incomplete fix for CVE-2013-1664.",
            "cve": "CVE-2013-4202",
            "id": "pyup.io-68019",
            "more_info_path": "/vulnerabilities/CVE-2013-4202/68019",
            "specs": [
                ">=2012,<=2013.1.3"
            ],
            "v": ">=2012,<=2013.1.3"
        },
        {
            "advisory": "The strutils.mask_password function in the OpenStack Oslo utility library, Cinder, Nova, and Trove before 2013.2.4 and 2014.1 before 2014.1.3 does not properly mask passwords when logging commands, which allows local users to obtain passwords by reading the log.",
            "cve": "CVE-2014-7231",
            "id": "pyup.io-70430",
            "more_info_path": "/vulnerabilities/CVE-2014-7231/70430",
            "specs": [
                ">=2013.2,<2013.2.4",
                ">=2014.1,<2014.1.3"
            ],
            "v": ">=2013.2,<2013.2.4,>=2014.1,<2014.1.3"
        },
        {
            "advisory": "The processutils.execute function in OpenStack oslo-incubator, Cinder, Nova, and Trove before 2013.2.4 and 2014.1 before 2014.1.3 allows local users to obtain passwords from commands that cause a ProcessExecutionError by reading the log.",
            "cve": "CVE-2014-7230",
            "id": "pyup.io-70424",
            "more_info_path": "/vulnerabilities/CVE-2014-7230/70424",
            "specs": [
                ">=2013.2,<2013.2.4",
                ">=2014.1,<2014.1.3"
            ],
            "v": ">=2013.2,<2013.2.4,>=2014.1,<2014.1.3"
        },
        {
            "advisory": "Cinder 22.1.0, 21.3.0 and 20.3.0 include a fix for CVE-2023-2088: A flaw was found in OpenStack due to an inconsistency between Cinder and Nova. This issue can be triggered intentionally or by accident. A remote, authenticated attacker could exploit this vulnerability by detaching one of their volumes from Cinder. The highest impact is to confidentiality.",
            "cve": "CVE-2023-2088",
            "id": "pyup.io-58700",
            "more_info_path": "/vulnerabilities/CVE-2023-2088/58700",
            "specs": [
                ">=22.0.0.0rc1,<22.1.0",
                ">=21.0.0.0rc2,<21.3.0",
                "<20.3.0"
            ],
            "v": ">=22.0.0.0rc1,<22.1.0,>=21.0.0.0rc2,<21.3.0,<20.3.0"
        }
    ],
    "cipher-googlepam": [
        {
            "advisory": "Cipher.googlepam 1.5.1 does not use the same cache key for all users. Previously, when one user logged in successfully, others could not log in using their own passwords -- but the first user could use its password to log in as anyone else.",
            "cve": "PVE-2021-25652",
            "id": "pyup.io-25652",
            "more_info_path": "/vulnerabilities/PVE-2021-25652/25652",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        }
    ],
    "cipherbcrypt": [
        {
            "advisory": "Malicious package. Exfiltrated secrets to a target server.",
            "cve": "PVE-2024-72112",
            "id": "pyup.io-72112",
            "more_info_path": "/vulnerabilities/PVE-2024-72112/72112",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "circuit-maintenance-parser": [
        {
            "advisory": "Circuit-maintenance-parser 1.1.0 updates the 'Pydantic' dependency version to v1.8.2 to include a security fix.",
            "cve": "CVE-2021-29510",
            "id": "pyup.io-41103",
            "more_info_path": "/vulnerabilities/CVE-2021-29510/41103",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "circuitbreaker": [
        {
            "advisory": "Circuitbreaker 1.4.0 starts using a monotonic clock source. Using the wall clock to measure duration is vulnerable to changes in the system clock causing misbehavior - a clock accidentally set far in the future and later reset could result in the circuit breaker remaining open for a great deal longer than expected.\r\nhttps://github.com/fabfuel/circuitbreaker/commit/094946f2b1232ec2dcf1685fd84f87927791fa4a",
            "cve": "PVE-2022-50117",
            "id": "pyup.io-50117",
            "more_info_path": "/vulnerabilities/PVE-2022-50117/50117",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        }
    ],
    "circup": [
        {
            "advisory": "Circup 0.0.6 includes an unspecified security fix.",
            "cve": "PVE-2021-37936",
            "id": "pyup.io-37936",
            "more_info_path": "/vulnerabilities/PVE-2021-37936/37936",
            "specs": [
                "<0.0.6"
            ],
            "v": "<0.0.6"
        }
    ],
    "ciris-agent": [
        {
            "advisory": "Affected versions of the `CIRISAgent` package are vulnerable to SQL Injection due to the use of f-string interpolation for constructing LIMIT and OFFSET clauses in SQL queries. The vulnerable code directly embeds user-controlled `limit` and `offset` values into SQL statements using f-strings instead of parameterized queries, allowing malicious input to break out of the intended query structure. An attacker can exploit this by supplying crafted values for the limit or offset parameters to inject arbitrary SQL commands, potentially leading to unauthorized data access, data modification, or extraction of sensitive information from the database.",
            "cve": "PVE-2025-81753",
            "id": "pyup.io-81753",
            "more_info_path": "/vulnerabilities/PVE-2025-81753/81753",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Affected versions of the `CIRISAgent` package are vulnerable to Authentication Bypass due to insufficient JWT signature verification in the rate limiting mechanism. The `_extract_user_id_from_jwt()` method in `rate_limiter.py` uses `jwt.decode()` with the `verify_signature` option set to `False`, allowing the rate limiter to accept JWT tokens without validating their cryptographic signatures. An attacker can exploit this by forging JWT tokens with arbitrary user IDs to bypass per-user rate limiting controls, enabling them to exceed intended request thresholds and potentially launch Denial of Service attacks or conduct resource exhaustion attacks against the service.",
            "cve": "PVE-2025-81752",
            "id": "pyup.io-81752",
            "more_info_path": "/vulnerabilities/PVE-2025-81752/81752",
            "specs": [
                "<1.3.2"
            ],
            "v": "<1.3.2"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal. The create_env_file() and _save_setup_config() functions accept user-controlled save_path parameters without validation, allowing attackers to write configuration files to arbitrary locations on the filesystem through directory traversal sequences or absolute paths.",
            "cve": "PVE-2026-84898",
            "id": "pyup.io-84898",
            "more_info_path": "/vulnerabilities/PVE-2026-84898/84898",
            "specs": [
                "<1.8.12"
            ],
            "v": "<1.8.12"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Information Disclosure via Insecure File Permissions. The .env configuration files containing sensitive data are created with default permissions that allow other users on the system to read them, leading to exposure of credentials, API keys, and other sensitive configuration values. An attacker with local system access can exploit this vulnerability by reading world-readable or group-readable .env files to obtain authentication tokens, database passwords, or other secrets stored in clear text.",
            "cve": "PVE-2026-84907",
            "id": "pyup.io-84907",
            "more_info_path": "/vulnerabilities/PVE-2026-84907/84907",
            "specs": [
                "<1.8.12"
            ],
            "v": "<1.8.12"
        }
    ],
    "cisco-sdwan": [
        {
            "advisory": "A vulnerability in the CLI of Cisco SDWAN vManage Software could allow an authenticated, local attacker to delete arbitrary files. This vulnerability is due to improper filtering of directory traversal character sequences within system commands. An attacker with administrative privileges could exploit this vulnerability by running a system command containing directory traversal character sequences to target an arbitrary file. A successful exploit could allow the attacker to delete arbitrary files from the system, including files owned by root.",
            "cve": "CVE-2023-20098",
            "id": "pyup.io-62884",
            "more_info_path": "/vulnerabilities/CVE-2023-20098/62884",
            "specs": [
                "<20.9.1"
            ],
            "v": "<20.9.1"
        }
    ],
    "ciscosupportsdk": [
        {
            "advisory": "Ciscosupportsdk 0.2.1 updates its dependency 'authlib' to versions \"^1.2.1\" to include a security fixes.",
            "cve": "CVE-2022-39174",
            "id": "pyup.io-61453",
            "more_info_path": "/vulnerabilities/CVE-2022-39174/61453",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        },
        {
            "advisory": "Ciscosupportsdk 0.2.1 updates its dependency 'authlib' to versions \"^1.2.1\" to include a security fixes.",
            "cve": "CVE-2022-39175",
            "id": "pyup.io-61470",
            "more_info_path": "/vulnerabilities/CVE-2022-39175/61470",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "citation-graph": [
        {
            "advisory": "Citation-graph 1.2.5 removes its dependency 'setuptools' to avoid a vulnerability.",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-52763",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/52763",
            "specs": [
                "<1.2.5"
            ],
            "v": "<1.2.5"
        },
        {
            "advisory": "Citation-graph 1.2.7 updates its dependency 'ipython' to v8.11.0 to include a security fix.",
            "cve": "CVE-2023-24816",
            "id": "pyup.io-53606",
            "more_info_path": "/vulnerabilities/CVE-2023-24816/53606",
            "specs": [
                "<1.2.7"
            ],
            "v": "<1.2.7"
        }
    ],
    "citrine": [
        {
            "advisory": "Citrine 0.115.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/CitrineInformatics/citrine-python/pull/571",
            "cve": "PVE-2023-59618",
            "id": "pyup.io-59618",
            "more_info_path": "/vulnerabilities/PVE-2023-59618/59618",
            "specs": [
                "<0.115.0"
            ],
            "v": "<0.115.0"
        },
        {
            "advisory": "Citrine 2.37.1 updates its dependency 'urllib3' to include a security fix.",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-62129",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/62129",
            "specs": [
                "<2.37.1"
            ],
            "v": "<2.37.1"
        }
    ],
    "civis": [
        {
            "advisory": "Dwave-cloud-client version 0.12.0 increases the minimum required version of requests to 2.32.3 due to a security vulnerability in versions below 2.32.0, identified as CVE-2024-35195.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-71529",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/71529",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        }
    ],
    "ck": [
        {
            "advisory": "Ck 1.7.1 fixes a server vulnerability (action with ; can run various CMD commands).\r\nhttps://github.com/mlcommons/ck/commit/ac16bf54a03c1d13832f9bbef9c3cf1039583f28",
            "cve": "PVE-2021-40221",
            "id": "pyup.io-40221",
            "more_info_path": "/vulnerabilities/PVE-2021-40221/40221",
            "specs": [
                "<1.7.1"
            ],
            "v": "<1.7.1"
        }
    ],
    "ckan": [
        {
            "advisory": "ckan 1.5.1 fixes a security issue affecting CKAN v1.5 and before.",
            "cve": "PVE-2021-34556",
            "id": "pyup.io-34556",
            "more_info_path": "/vulnerabilities/PVE-2021-34556/34556",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        },
        {
            "advisory": "Ckan 1.8.1 fixes a possible XSS vulnerability on html input.\r\nhttps://github.com/ckan/ckan/pull/703",
            "cve": "PVE-2021-34558",
            "id": "pyup.io-34558",
            "more_info_path": "/vulnerabilities/PVE-2021-34558/34558",
            "specs": [
                "<1.8.1"
            ],
            "v": "<1.8.1"
        },
        {
            "advisory": "Several CKAN plugins, including XLoader, DataPusher, Resource Proxy, and ckanext-archiver, are vulnerable to SSRF attacks due to a lack of URL validation. Malicious users can exploit these plugins by creating resources with URLs that access unauthorized locations. To mitigate this, users should use an HTTP proxy, implement firewall rules, or apply custom URL validators. The latest plugin versions support the ckan.download_proxy setting.",
            "cve": "CVE-2024-43371",
            "id": "pyup.io-72975",
            "more_info_path": "/vulnerabilities/CVE-2024-43371/72975",
            "specs": [
                "<2.10.5"
            ],
            "v": "<2.10.5"
        },
        {
            "advisory": "CKAN has an XSS vector in `user` uploaded images in group/org and user profiles.",
            "cve": "CVE-2025-24372",
            "id": "pyup.io-76345",
            "more_info_path": "/vulnerabilities/CVE-2025-24372/76345",
            "specs": [
                "<2.10.7",
                ">=2.11.0,<2.11.2"
            ],
            "v": "<2.10.7,>=2.11.0,<2.11.2"
        },
        {
            "advisory": "Ckan 2.6.9, 2.7.7 and 2.8.4 fix a code injection issue in the autocomplete module. \r\nhttps://github.com/ckan/ckan/pull/5064",
            "cve": "PVE-2021-39613",
            "id": "pyup.io-39613",
            "more_info_path": "/vulnerabilities/PVE-2021-39613/39613",
            "specs": [
                "<2.6.9",
                ">=2.7.0,<2.7.7",
                ">=2.8.0,<2.8.4"
            ],
            "v": "<2.6.9,>=2.7.0,<2.7.7,>=2.8.0,<2.8.4"
        },
        {
            "advisory": "CKAN is an open-source DMS (data management system) for powering data hubs and data portals. When creating a new container based on one of the Docker images listed below, the same secret key was being used by default. If the users didn't set a custom value via environment variables in the `.env` file, that key was shared across different CKAN instances, making it easy to forge authentication requests. Users overriding the default secret key in their own `.env` file are not affected by this issue. Note that the legacy images (ckan/ckan) located in the main CKAN repo are not affected by this issue. The affected images are ckan/ckan-docker, (ckan/ckan-base images), okfn/docker-ckan (openknowledge/ckan-base and openknowledge/ckan-dev images) keitaroinc/docker-ckan (keitaro/ckan images).",
            "cve": "CVE-2023-22746",
            "id": "pyup.io-62888",
            "more_info_path": "/vulnerabilities/CVE-2023-22746/62888",
            "specs": [
                "<2.8.12",
                ">=2.9.0,<2.9.7"
            ],
            "v": "<2.8.12,>=2.9.0,<2.9.7"
        },
        {
            "advisory": "A user endpoint didn't perform filtering on an incoming parameter, which was added directly to the application log. This could lead to an attacker injecting false log entries or corrupt the log file format. Users are advised to upgrade. Users unable to upgrade should override the `/user/reset` endpoint to filter the `id` parameter in order to exclude new lines.",
            "cve": "CVE-2024-27097",
            "id": "pyup.io-71909",
            "more_info_path": "/vulnerabilities/CVE-2024-27097/71909",
            "specs": [
                "<2.9.11",
                ">=2.10.0,<2.10.4"
            ],
            "v": "<2.9.11,>=2.10.0,<2.10.4"
        },
        {
            "advisory": "CKAN is an open-source data management system for powering data hubs and data portals. Prior to versions 2.9.9 and 2.10.1, the `ckan` user (equivalent to www-data) owned code and configuration files in the docker container and the `ckan` user had the permissions to use sudo. These issues allowed for code execution or privilege escalation if an arbitrary file write bug was available. Versions 2.9.9, 2.9.9-dev, 2.10.1, and 2.10.1-dev contain a patch.",
            "cve": "CVE-2023-32696",
            "id": "pyup.io-64195",
            "more_info_path": "/vulnerabilities/CVE-2023-32696/64195",
            "specs": [
                "<2.9.9",
                "==2.10.0"
            ],
            "v": "<2.9.9,==2.10.0"
        },
        {
            "advisory": "CKAN is an open-source data management system for powering data hubs and data portals. Multiple vulnerabilities have been discovered in Ckan which may lead to remote code execution. An arbitrary file write in `resource_create` and `package_update` actions, using the `ResourceUploader` object.  Also reachable via `package_create`, `package_revise`, and `package_patch` via calls to `package_update`. Remote code execution via unsafe pickle loading, via Beaker's session store when configured to use the file session store backend. Potential DOS due to lack of a length check on the resource id. Information disclosure: A user with permission to create a resource can access any other resource on the system if they know the id, even if they don't have access to it. Resource overwrite: A user with permission to create a resource can overwrite any resource if they know the id, even if they don't have access to it. A user with permissions to create or edit a dataset can upload a resource with a specially crafted id to write the uploaded file in an arbitrary location. This can be leveraged to Remote Code Execution via Beaker's insecure pickle loading. All the above listed vulnerabilities have been fixed in CKAN 2.9.9 and CKAN 2.10.1. Users are advised to upgrade. There are no known workarounds for these issues.",
            "cve": "CVE-2023-32321",
            "id": "pyup.io-64193",
            "more_info_path": "/vulnerabilities/CVE-2023-32321/64193",
            "specs": [
                "==2.10.0",
                ">=2.9.0,<2.9.9"
            ],
            "v": "==2.10.0,>=2.9.0,<2.9.9"
        },
        {
            "advisory": "CKAN through 2.9.6 account takeovers by unauthenticated users when an existing user id is sent via an HTTP POST request. This allows a user to take over an existing account including superuser accounts.",
            "cve": "CVE-2022-43685",
            "id": "pyup.io-54589",
            "more_info_path": "/vulnerabilities/CVE-2022-43685/54589",
            "specs": [
                ">=0,<2.9.7"
            ],
            "v": ">=0,<2.9.7"
        },
        {
            "advisory": "CKAN affected versions may expose sensitive information, including internal Solr URLs and potential credentials, in error messages when connection issues occur with the Solr server. This vulnerability arises during package_search API calls, where an unsuccessful connection to Solr could result in the leaking of internal configuration details as part of the returned error message.",
            "cve": "CVE-2024-41674",
            "id": "pyup.io-72977",
            "more_info_path": "/vulnerabilities/CVE-2024-41674/72977",
            "specs": [
                ">=2.0,<2.10.5"
            ],
            "v": ">=2.0,<2.10.5"
        },
        {
            "advisory": "CKAN is an open-source data management system for powering data hubs and data portals. Starting in version 2.0.0 and prior to versions 2.9.10 and 2.10.3, when submitting a POST request to the `/dataset/new` endpoint (including either the auth cookie or the `Authorization` header) with a specially-crafted field, an attacker can create an out-of-memory error in the hosting server. To trigger this error, the attacker need to have permissions to create or edit datasets. This vulnerability has been patched in CKAN 2.10.3 and 2.9.10.",
            "cve": "CVE-2023-50248",
            "id": "pyup.io-65383",
            "more_info_path": "/vulnerabilities/CVE-2023-50248/65383",
            "specs": [
                ">=2.0,<2.9.10",
                ">=2.10.0,<2.10.3"
            ],
            "v": ">=2.0,<2.9.10,>=2.10.0,<2.10.3"
        },
        {
            "advisory": "Affected versions of the CKAN package are vulnerable to Session Fixation due to failing to regenerate the session identifier upon successful authentication when CKAN is configured to use server-side session storage. The CKAN authentication flow leaves the pre-login session token intact after login, so a session ID that was set by an attacker before authentication becomes bound to the newly authenticated context.",
            "cve": "CVE-2025-64100",
            "id": "pyup.io-80985",
            "more_info_path": "/vulnerabilities/CVE-2025-64100/80985",
            "specs": [
                ">=2.10.0,<2.10.9",
                ">=2.11.0,<2.11.4"
            ],
            "v": ">=2.10.0,<2.10.9,>=2.11.0,<2.11.4"
        },
        {
            "advisory": "Affected versions of the ckan package are vulnerable to Stored Cross-Site Scripting (XSS) due to insufficient input sanitization in the helpers.markdown_extract() helper when wrapping user-supplied content in an HTML literal. The helpers.markdown_extract() function is used to render user-provided text on dataset, resource, organization, or group pages, and because it fails to neutralize unsafe markup, attacker-controlled script can persist in fields such as a resource description.",
            "cve": "CVE-2025-54384",
            "id": "pyup.io-80981",
            "more_info_path": "/vulnerabilities/CVE-2025-54384/80981",
            "specs": [
                ">=2.11.0,<2.11.4",
                "<2.10.9"
            ],
            "v": ">=2.11.0,<2.11.4,<2.10.9"
        },
        {
            "advisory": "CKAN's datatables_view plugin affected versions are vulnerable to a Cross-Site Scripting (XSS) attack due to improper escaping of record data from the DataStore, allowing attackers to inject malicious scripts into tabular data previews. This issue was addressed by implementing proper HTML escaping of data within the plugin, ensuring that any potentially harmful content is neutralized before being rendered in the browser. As a precaution, administrators should prevent importing tabular files from untrusted sources until they have applied the patch.",
            "cve": "CVE-2024-41675",
            "id": "pyup.io-72976",
            "more_info_path": "/vulnerabilities/CVE-2024-41675/72976",
            "specs": [
                ">=2.7.0,<2.10.5"
            ],
            "v": ">=2.7.0,<2.10.5"
        },
        {
            "advisory": "In CKAN, versions 2.9.0 to 2.9.3 are affected by a stored XSS vulnerability via SVG file upload of users\u2019 profile picture. This allows low privileged application users to store malicious scripts in their profile picture. These scripts are executed in a victim\u2019s browser when they open the malicious profile picture",
            "cve": "CVE-2021-25967",
            "id": "pyup.io-54196",
            "more_info_path": "/vulnerabilities/CVE-2021-25967/54196",
            "specs": [
                ">=2.9.0,<2.9.4"
            ],
            "v": ">=2.9.0,<2.9.4"
        }
    ],
    "ckanext-dataset-reference": [
        {
            "advisory": "Ckanext-dataset-reference 2.0.2 protects against XSS attacks.\r\nhttps://github.com/TIBHannover/ckanext-Dataset-Reference/commit/ea7abc28f90991cc73becd8e67d0621f62979d6a",
            "cve": "PVE-2022-49237",
            "id": "pyup.io-49237",
            "more_info_path": "/vulnerabilities/PVE-2022-49237/49237",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        }
    ],
    "ckuehl-celery": [
        {
            "advisory": "Ckuehl-celery 4.0.2.post1 (fork of Celery) is affected by CVE-2021-23727.",
            "cve": "CVE-2021-23727",
            "id": "pyup.io-47079",
            "more_info_path": "/vulnerabilities/CVE-2021-23727/47079",
            "specs": [
                "==4.0.2.post1"
            ],
            "v": "==4.0.2.post1"
        }
    ],
    "clam": [
        {
            "advisory": "Clam 0.9.10 protects against a code injection vulnerability.\r\nhttps://github.com/proycon/clam/commit/f89ba22a3b74f0b86ce9d8190ce28b6da7331813",
            "cve": "PVE-2021-25653",
            "id": "pyup.io-25653",
            "more_info_path": "/vulnerabilities/PVE-2021-25653/25653",
            "specs": [
                "<0.9.10"
            ],
            "v": "<0.9.10"
        },
        {
            "advisory": "Clam 0.9.11 fixes a RCE vulnerability in its dispatcher.\r\nhttps://github.com/proycon/clam/commit/f89ba22a3b74f0b86ce9d8190ce28b6da7331813",
            "cve": "PVE-2021-25654",
            "id": "pyup.io-25654",
            "more_info_path": "/vulnerabilities/PVE-2021-25654/25654",
            "specs": [
                "<0.9.11"
            ],
            "v": "<0.9.11"
        }
    ],
    "clara-viz": [
        {
            "advisory": "Clara-viz 0.1.4 updates Jupyter widget Java code packages to fix vulnerabilities. This is stated by its changelog, but no changes in code were found.",
            "cve": "PVE-2022-45107",
            "id": "pyup.io-45107",
            "more_info_path": "/vulnerabilities/PVE-2022-45107/45107",
            "specs": [
                "<0.1.4"
            ],
            "v": "<0.1.4"
        },
        {
            "advisory": "Clara-viz 0.2.0 changes Jupyter widget Java code to fix vulnerabilities.",
            "cve": "PVE-2022-47823",
            "id": "pyup.io-47823",
            "more_info_path": "/vulnerabilities/PVE-2022-47823/47823",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        },
        {
            "advisory": "Clara-viz 0.2.2 avoids using unsafe unencrypted HTTP connections on widgets.\r\nhttps://github.com/NVIDIA/clara-viz/commit/d7f2731105c040b590f5d90736db1d61c63e416b",
            "cve": "PVE-2022-51460",
            "id": "pyup.io-51460",
            "more_info_path": "/vulnerabilities/PVE-2022-51460/51460",
            "specs": [
                "<0.2.2"
            ],
            "v": "<0.2.2"
        },
        {
            "advisory": "Clara-viz 0.3.0 updates Jupyter widget Java code packages to include a security fix.\r\nhttps://github.com/NVIDIA/clara-viz/pull/27",
            "cve": "CVE-2022-46175",
            "id": "pyup.io-59150",
            "more_info_path": "/vulnerabilities/CVE-2022-46175/59150",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "claude-autoapprove": [
        {
            "advisory": "Affected versions of Claude MCP were vulnerable to Cross-Site Scripting (XSS). The issue existed in the `inject_script` function.",
            "cve": "PVE-2025-76897",
            "id": "pyup.io-76897",
            "more_info_path": "/vulnerabilities/PVE-2025-76897/76897",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "claude-statusline": [
        {
            "advisory": "Affected versions of this package are vulnerable to Command Injection due to improper handling of subprocess calls. The `instance_manager.py` file uses string interpolation in subprocess calls, which allows for potential command injection. An attacker could exploit this vulnerability by injecting malicious commands into the subprocess call, leading to unauthorized command execution on the system.",
            "cve": "PVE-2025-81880",
            "id": "pyup.io-81880",
            "more_info_path": "/vulnerabilities/PVE-2025-81880/81880",
            "specs": [
                "<1.9.9"
            ],
            "v": "<1.9.9"
        }
    ],
    "claudesync": [
        {
            "advisory": "ClaudeSync addresses the cleartext storage of sensitive session keys. Affected versions stored session keys in plaintext, exposing them to potential unauthorized access. The fix introduced encryption for session keys using the user's SSH key, significantly enhancing the security of stored credentials. This change mitigates the risk of unauthorized access to user accounts in case of local system breaches.",
            "cve": "PVE-2024-73213",
            "id": "pyup.io-73213",
            "more_info_path": "/vulnerabilities/PVE-2024-73213/73213",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "cleanlab": [
        {
            "advisory": "Cleanlab project affected versions contain a security vulnerability in the deserialization process. When loading a data directory, a maliciously crafted datalab.pkl file can execute arbitrary code on the user's system. This vulnerability stems from the use of the pickle module for deserialization without proper safeguards. Attackers can exploit this flaw to compromise systems, potentially leading to data theft, system manipulation, or further malware deployment. Users should exercise extreme caution when loading data from untrusted sources, and consider updating to a patched version if available.",
            "cve": "CVE-2024-45857",
            "id": "pyup.io-73323",
            "more_info_path": "/vulnerabilities/CVE-2024-45857/73323",
            "specs": [
                ">=2.4.0"
            ],
            "v": ">=2.4.0"
        }
    ],
    "clearml": [
        {
            "advisory": "Clearml 0.17.5rc3 fixes unsafe call to set_active().\r\nhttps://github.com/allegroai/clearml/commit/b0000df575e830a81674f4e5cf3d89cf6d6441b4",
            "cve": "PVE-2022-49701",
            "id": "pyup.io-49701",
            "more_info_path": "/vulnerabilities/PVE-2022-49701/49701",
            "specs": [
                "<0.17.5rc3"
            ],
            "v": "<0.17.5rc3"
        },
        {
            "advisory": "Clearml 1.0.6rc2 fixes unsafe Google Storage delete object.\r\nhttps://github.com/allegroai/clearml/commit/6e15349b7627bee3847a39e5bdce8c988e39cb38",
            "cve": "PVE-2022-49700",
            "id": "pyup.io-49700",
            "more_info_path": "/vulnerabilities/PVE-2022-49700/49700",
            "specs": [
                "<1.0.6rc2"
            ],
            "v": "<1.0.6rc2"
        },
        {
            "advisory": "A cross-site request forgery (CSRF) vulnerability in all versions up to 1.14.1 of the api server component of Allegro AI\u2019s ClearML platform allows a remote attacker to impersonate a user by sending API requests via maliciously crafted html. Exploitation of the vulnerability allows an attacker to compromise confidential workspaces and files, leak sensitive information, and target instances of the ClearML platform within closed-off networks.",
            "cve": "CVE-2024-24593",
            "id": "pyup.io-66780",
            "more_info_path": "/vulnerabilities/CVE-2024-24593/66780",
            "specs": [
                "<1.14.1"
            ],
            "v": "<1.14.1"
        },
        {
            "advisory": "Clearml 1.4.2rc0 updates its dependency 'pyjwt' requirement to versions '>=2.4.0,<2.5.0' to include a security fix.",
            "cve": "CVE-2022-29217",
            "id": "pyup.io-49693",
            "more_info_path": "/vulnerabilities/CVE-2022-29217/49693",
            "specs": [
                "<1.4.2rc0"
            ],
            "v": "<1.4.2rc0"
        },
        {
            "advisory": "Affected versions of the ClearML package are vulnerable to Path Traversal due to incomplete validation of archive member paths and link targets in the safe_extract function. The clearml.storage.util.safe_extract routine originally computed member paths relative to the extraction directory, but did not canonicalize and constrain both member.name and member.linkname (for symbolic or hard links) to the base directory before calling tar.extractall, permitting writes outside the intended path.",
            "cve": "CVE-2025-8917",
            "id": "pyup.io-80187",
            "more_info_path": "/vulnerabilities/CVE-2025-8917/80187",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Allegro AI\u2019s open-source version of ClearML stores passwords in plaintext within the MongoDB instance, resulting in a compromised server leaking all user emails and passwords.",
            "cve": "CVE-2024-24595",
            "id": "pyup.io-66778",
            "more_info_path": "/vulnerabilities/CVE-2024-24595/66778",
            "specs": [
                "<=1.14.2"
            ],
            "v": "<=1.14.2"
        },
        {
            "advisory": "Lack of authentication in all versions of the fileserver component of Allegro AI\u2019s ClearML platform allows a remote attacker to arbitrarily access, create, modify and delete files.",
            "cve": "CVE-2024-24592",
            "id": "pyup.io-66781",
            "more_info_path": "/vulnerabilities/CVE-2024-24592/66781",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        },
        {
            "advisory": "A cross-site scripting (XSS) vulnerability in all versions of the web server component of Allegro AI\u2019s ClearML platform allows a remote attacker to execute a JavaScript payload when a user views the Debug Samples tab in the web UI.",
            "cve": "CVE-2024-24594",
            "id": "pyup.io-66779",
            "more_info_path": "/vulnerabilities/CVE-2024-24594/66779",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        },
        {
            "advisory": "Clearml version 1.14.3 introduces a hash check for pickle files to tackle CVE-2024-24590. This vulnerability allowed the deserialization of untrusted data in ClearML versions 0.17.0 and newer, potentially enabling the execution of arbitrary code through maliciously uploaded artifacts.\r\nhttps://github.com/allegroai/clearml/commit/e506831599bd8e072e5e54266abfccdfbe4be2ac",
            "cve": "CVE-2024-24590",
            "id": "pyup.io-65114",
            "more_info_path": "/vulnerabilities/CVE-2024-24590/65114",
            "specs": [
                ">=0.17.0,<1.14.3"
            ],
            "v": ">=0.17.0,<1.14.3"
        },
        {
            "advisory": "Clearml 1.14.2 fixes potential path traversal on file download.\r\nhttps://github.com/allegroai/clearml/commit/831c1394da0d99cc65b0fe060a6dfff13816efab",
            "cve": "CVE-2024-24591",
            "id": "pyup.io-65006",
            "more_info_path": "/vulnerabilities/CVE-2024-24591/65006",
            "specs": [
                ">=0.17.0,<=1.14.1"
            ],
            "v": ">=0.17.0,<=1.14.1"
        }
    ],
    "clearml-agent": [
        {
            "advisory": "Clearml-agent 1.3.0 updates its dependency 'pyjwt' requirement to '>=2.4.0,<2.5.0' to include a security fix.",
            "cve": "CVE-2022-29217",
            "id": "pyup.io-49462",
            "more_info_path": "/vulnerabilities/CVE-2022-29217/49462",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "clearml-session": [
        {
            "advisory": "Clearml-session 0.10.0 upgrades the Pillow dependency to versions >=10.0.1 due to vulnerabilities present in earlier versions.\r\nhttps://github.com/allegroai/clearml-session/commit/e6dbd13ca38c58ce2b4057ef8ad2c35cc313eeea",
            "cve": "PVE-2023-62736",
            "id": "pyup.io-62736",
            "more_info_path": "/vulnerabilities/PVE-2023-62736/62736",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Clearml-session version 0.13.0 updates its dependency on clearml to version 1.9 or higher from the previously required minimum of 1.1.5, in response to addressing the security issue identified as CVE-2024-24590.",
            "cve": "CVE-2024-24590",
            "id": "pyup.io-65935",
            "more_info_path": "/vulnerabilities/CVE-2024-24590/65935",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        }
    ],
    "clearsilver": [
        {
            "advisory": "Format string vulnerability in the p_cgi_error function in python/neo_cgi.c in the Python CGI Kit (neo_cgi) module for Clearsilver 0.10.5 and earlier allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via format string specifiers that are not properly handled when creating CGI error messages using the cgi_error API function.",
            "cve": "CVE-2011-4357",
            "id": "pyup.io-25655",
            "more_info_path": "/vulnerabilities/CVE-2011-4357/25655",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        }
    ],
    "cleo": [
        {
            "advisory": "An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the cleo PyPI package, when an attacker is able to supply arbitrary input to the Table.set_rows method\r\nhttps://github.com/python-poetry/cleo/pull/285",
            "cve": "CVE-2022-42966",
            "id": "pyup.io-54559",
            "more_info_path": "/vulnerabilities/CVE-2022-42966/54559",
            "specs": [
                ">=0,<1.0.0"
            ],
            "v": ">=0,<1.0.0"
        }
    ],
    "clevercsv": [
        {
            "advisory": "Clevercsv 0.6.2 includes a fix for a potential ReDOS vulnerability.\r\nhttps://github.com/alan-turing-institute/CleverCSV/issues/13",
            "cve": "PVE-2023-61023",
            "id": "pyup.io-61023",
            "more_info_path": "/vulnerabilities/PVE-2023-61023/61023",
            "specs": [
                "<0.6.2"
            ],
            "v": "<0.6.2"
        }
    ],
    "cli-onprem": [
        {
            "advisory": "Affected versions of the `cli-onprem` package are vulnerable to Command Injection due to use of shell-invoked subprocess calls with unvalidated input. The `calculate_sha256_manifest` and `merge_files` functions construct shell commands using the directory and pattern and execute them via `subprocess.run`, allowing shell metacharacters in those parameters to be interpreted by the shell.",
            "cve": "PVE-2025-80946",
            "id": "pyup.io-80946",
            "more_info_path": "/vulnerabilities/PVE-2025-80946/80946",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        }
    ],
    "cliboa": [
        {
            "advisory": "Cliboa 2.0.0b0 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-42681",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/42681",
            "specs": [
                "<2.0.0b0"
            ],
            "v": "<2.0.0b0"
        }
    ],
    "click": [
        {
            "advisory": "Click 8.0.0 uses 'mkstemp()' instead of the deprecated & insecure 'mktemp()'.\r\nhttps://github.com/pallets/click/issues/1752",
            "cve": "PVE-2022-47833",
            "id": "pyup.io-47833",
            "more_info_path": "/vulnerabilities/PVE-2022-47833/47833",
            "specs": [
                "<8.0.0"
            ],
            "v": "<8.0.0"
        }
    ],
    "clickhouse-driver": [
        {
            "advisory": "clickhouse-driver before 0.1.5 allows a malicious clickhouse server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, due to a buffer overflow.",
            "cve": "CVE-2020-26759",
            "id": "pyup.io-42290",
            "more_info_path": "/vulnerabilities/CVE-2020-26759/42290",
            "specs": [
                "<0.1.5"
            ],
            "v": "<0.1.5"
        }
    ],
    "clip-retrieval": [
        {
            "advisory": "Clip-retrieval 2.23.1 addresses a race condition that could lead to data corruption and inconsistent states. Previously, multiple instances of the writer function could attempt to create directories simultaneously, potentially causing conflicts and errors. This version resolves this by replacing 'mkdir' with 'makedirs', which ensures all intermediate directories are created. It also introduces a check to verify the existence of a 'work in progress' file before creation, thereby preventing race conditions.\r\nhttps://github.com/rom1504/clip-retrieval/pull/112",
            "cve": "PVE-2024-63278",
            "id": "pyup.io-63278",
            "more_info_path": "/vulnerabilities/PVE-2024-63278/63278",
            "specs": [
                "<2.23.1"
            ],
            "v": "<2.23.1"
        }
    ],
    "clipster-desktop": [
        {
            "advisory": "Clipster-desktop 0.3.0 includes various improvements to make the host more secure:\r\n* All clips are encrypted locally in the client before transmission to the server. \r\n* Server host can't decrypt clips: it never learns the users' password.\r\n* Password is not stored in cleartext anymore. Instead password hash is used.",
            "cve": "PVE-2021-39388",
            "id": "pyup.io-39388",
            "more_info_path": "/vulnerabilities/PVE-2021-39388/39388",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "cliquery": [
        {
            "advisory": "Cliquery 1.10.0 updates the 'lxml' dependency from 4.6.2 to 4.6.3 to fix a security vulnerability.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-40090",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/40090",
            "specs": [
                "<1.10.0"
            ],
            "v": "<1.10.0"
        },
        {
            "advisory": "Cliquery 1.10.1 updates its dependency 'lxml' to v4.6.5 to include a security fix.",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-45291",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/45291",
            "specs": [
                "<1.10.1"
            ],
            "v": "<1.10.1"
        },
        {
            "advisory": "Cliquery 1.9.3 updates the 'lxml' dependency from 4.3.0 to 4.6.2 to include security fixes.",
            "cve": "PVE-2021-39195",
            "id": "pyup.io-43643",
            "more_info_path": "/vulnerabilities/PVE-2021-39195/43643",
            "specs": [
                "<1.9.3"
            ],
            "v": "<1.9.3"
        },
        {
            "advisory": "Cliquery 1.9.3 updates the 'lxml' dependency from 4.3.0 to 4.6.2 to include security fixes.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-39423",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/39423",
            "specs": [
                "<1.9.3"
            ],
            "v": "<1.9.3"
        }
    ],
    "cloorama": [
        {
            "advisory": "Cloorama is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51737",
            "id": "pyup.io-51737",
            "more_info_path": "/vulnerabilities/PVE-2022-51737/51737",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "cloudlabeling": [
        {
            "advisory": "The cloudlabeling package in PyPI v0.0.1 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.",
            "cve": "CVE-2022-32999",
            "id": "pyup.io-62690",
            "more_info_path": "/vulnerabilities/CVE-2022-32999/62690",
            "specs": [
                "==0.0.1"
            ],
            "v": "==0.0.1"
        }
    ],
    "cloudtoken": [
        {
            "advisory": "Unauthenticated access to cloudtoken daemon on Linux via network from version 0.1.1 before version 0.1.24 allows attackers on the same subnet to gain temporary AWS credentials for the users' roles.",
            "cve": "CVE-2018-13390",
            "id": "pyup.io-54005",
            "more_info_path": "/vulnerabilities/CVE-2018-13390/54005",
            "specs": [
                ">=0.1.1,<0.1.24"
            ],
            "v": ">=0.1.1,<0.1.24"
        }
    ],
    "cloudvision": [
        {
            "advisory": "Cloudvision 1.13.0 updates 'cryptography' minimum version to v41.0.3 to include security fixes in bundled OpenSSL.",
            "cve": "CVE-2023-3446",
            "id": "pyup.io-61131",
            "more_info_path": "/vulnerabilities/CVE-2023-3446/61131",
            "specs": [
                "<1.13.0"
            ],
            "v": "<1.13.0"
        },
        {
            "advisory": "Cloudvision 1.13.0 updates 'cryptography' minimum version to v41.0.3 to include security fixes in bundled OpenSSL.",
            "cve": "CVE-2023-3817",
            "id": "pyup.io-61129",
            "more_info_path": "/vulnerabilities/CVE-2023-3817/61129",
            "specs": [
                "<1.13.0"
            ],
            "v": "<1.13.0"
        },
        {
            "advisory": "Cloudvision 1.13.0 updates 'cryptography' minimum version to v41.0.3 to include security fixes in bundled OpenSSL.",
            "cve": "CVE-2023-2975",
            "id": "pyup.io-61130",
            "more_info_path": "/vulnerabilities/CVE-2023-2975/61130",
            "specs": [
                "<1.13.0"
            ],
            "v": "<1.13.0"
        },
        {
            "advisory": "Cloudvision version 1.19.0 has upgraded its cryptography library to version 42.0.4. This update addresses the security vulnerability identified as CVE-2024-26130.",
            "cve": "CVE-2024-26130",
            "id": "pyup.io-66933",
            "more_info_path": "/vulnerabilities/CVE-2024-26130/66933",
            "specs": [
                "<1.19.0"
            ],
            "v": "<1.19.0"
        },
        {
            "advisory": "Cloudvision 1.8.0 updates its dependency 'wheel' to v0.38.4 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-53080",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/53080",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        }
    ],
    "cloudwatch-to-graphite": [
        {
            "advisory": "Cloudwatch-To-Graphite 0.11.0 includes a security patch for the function 'get_config' in 'leadbutt.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/crccheck/cloudwatch-to-graphite/commit/5875100c54a54a9c90cf2fe782cc3df147d32053#diff-ddb0922eafb2fa54199e50bb13de6178b1755e780387144df032f9e26512f15e",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41313",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41313",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "cloudy-with-a-chance-of-meatballs.cdk-lambda-token-authorizer-jwt": [
        {
            "advisory": "Cloudy-with-a-chance-of-meatballs.cdk-lambda-token-authorizer-jwt 0.1.11 updates NPM dependencies to include security fixes.\r\nhttps://github.com/cloudy-with-a-chance-of-meatballs/cdk-lambda-token-authorizer-jwt/pull/154",
            "cve": "PVE-2023-53078",
            "id": "pyup.io-53078",
            "more_info_path": "/vulnerabilities/PVE-2023-53078/53078",
            "specs": [
                "<0.1.11"
            ],
            "v": "<0.1.11"
        },
        {
            "advisory": "Cloudy-with-a-chance-of-meatballs.cdk-lambda-token-authorizer-jwt 0.1.12 requires the NPM dependency \"json5\": \"^2.2.2\" to include a security fix.",
            "cve": "CVE-2022-46175",
            "id": "pyup.io-53287",
            "more_info_path": "/vulnerabilities/CVE-2022-46175/53287",
            "specs": [
                "<0.1.12"
            ],
            "v": "<0.1.12"
        }
    ],
    "cloverly-python-module": [
        {
            "advisory": "Cloverly-python-module 0.2.0 adds a clear session function for security purposes.",
            "cve": "PVE-2021-41085",
            "id": "pyup.io-41085",
            "more_info_path": "/vulnerabilities/PVE-2021-41085/41085",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "cls-python": [
        {
            "advisory": "Cls-python 0.1.4 updates its dependency 'wheel' to v0.38.1 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-53365",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/53365",
            "specs": [
                "<0.1.4"
            ],
            "v": "<0.1.4"
        }
    ],
    "cmdlr": [
        {
            "advisory": "cmdlr 4.1.0 resists malicious js attack in `run_in_nodejs`",
            "cve": "PVE-2021-36854",
            "id": "pyup.io-36854",
            "more_info_path": "/vulnerabilities/PVE-2021-36854/36854",
            "specs": [
                "<4.1.0"
            ],
            "v": "<4.1.0"
        }
    ],
    "cmsis-pack-manager": [
        {
            "advisory": "Cmsis-pack-manager 0.5.1 updates its RUST dependency 'time' to v0.3.17 to include a security fix.",
            "cve": "CVE-2020-26235",
            "id": "pyup.io-52547",
            "more_info_path": "/vulnerabilities/CVE-2020-26235/52547",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        }
    ],
    "cmsplugin-filer": [
        {
            "advisory": "Cmsplugin-filer 0.10.2 includes a fix for a XSS vulnerability in 'firstof' in folder template. Users with Django>1.7 aren't affected.\r\nhttps://github.com/divio/cmsplugin-filer/pull/185",
            "cve": "PVE-2021-25656",
            "id": "pyup.io-25656",
            "more_info_path": "/vulnerabilities/PVE-2021-25656/25656",
            "specs": [
                "<0.10.2"
            ],
            "v": "<0.10.2"
        }
    ],
    "cnx-publishing": [
        {
            "advisory": "Cnx-publishing 0.17.6 updates its dependency 'urllib3' to v1.25.8 to include a security fix.",
            "cve": "CVE-2020-7212",
            "id": "pyup.io-38128",
            "more_info_path": "/vulnerabilities/CVE-2020-7212/38128",
            "specs": [
                "<0.17.6"
            ],
            "v": "<0.17.6"
        }
    ],
    "coapthon": [
        {
            "advisory": "The Serialize.deserialize() method in CoAPthon 3.1, 4.0.0, 4.0.1, and 4.0.2 mishandles certain exceptions, leading to a denial of service in applications that use this library (e.g., the standard CoAP server, CoAP client, CoAP reverse proxy, example collect CoAP server and client) when they receive crafted CoAP messages.",
            "cve": "CVE-2018-12680",
            "id": "pyup.io-42251",
            "more_info_path": "/vulnerabilities/CVE-2018-12680/42251",
            "specs": [
                "==3.1",
                "==4.0.0",
                "==4.0.1",
                "==4.0.2"
            ],
            "v": "==3.1,==4.0.0,==4.0.1,==4.0.2"
        }
    ],
    "coapthon3": [
        {
            "advisory": "The Serialize.deserialize() method in CoAPthon3 1.0 and 1.0.1 mishandles certain exceptions, leading to a denial of service in applications that use this library (e.g., the standard CoAP server, CoAP client, example collect CoAP server and client) when they receive crafted CoAP messages.",
            "cve": "CVE-2018-12679",
            "id": "pyup.io-53999",
            "more_info_path": "/vulnerabilities/CVE-2018-12679/53999",
            "specs": [
                "<=1.0.1"
            ],
            "v": "<=1.0.1"
        }
    ],
    "cobbler": [
        {
            "advisory": "The web interface (CobblerWeb) in Cobbler before 1.2.9 allows remote authenticated users to execute arbitrary Python code in cobblerd by editing a Cheetah kickstart template to import arbitrary Python modules.",
            "cve": "CVE-2008-6954",
            "id": "pyup.io-61200",
            "more_info_path": "/vulnerabilities/CVE-2008-6954/61200",
            "specs": [
                "<1.2.9"
            ],
            "v": "<1.2.9"
        },
        {
            "advisory": "Cobbler before 1.6.1 does not properly determine whether an installation has the default password, which makes it easier for attackers to obtain access by using this password.",
            "cve": "CVE-2009-5021",
            "id": "pyup.io-61243",
            "more_info_path": "/vulnerabilities/CVE-2009-5021/61243",
            "specs": [
                "<1.6.1"
            ],
            "v": "<1.6.1"
        },
        {
            "advisory": "Cobbler before 2.0.4 uses an incorrect umask value, which allows local users to have an unspecified impact by leveraging world writable permissions for files and directories.",
            "cve": "CVE-2010-4512",
            "id": "pyup.io-61742",
            "more_info_path": "/vulnerabilities/CVE-2010-4512/61742",
            "specs": [
                "<2.0.4"
            ],
            "v": "<2.0.4"
        },
        {
            "advisory": "Cobbler 2.0.7 includes a fix for CVE-2010-2235: Template_api.py in Cobbler before 2.0.7, as used in Red Hat Network Satellite Server and other products, does not disable the ability of the Cheetah template engine to execute Python statements contained in templates, which allows remote authenticated administrators to execute arbitrary code via a crafted kickstart template file, a different vulnerability than CVE-2008-6954.",
            "cve": "CVE-2010-2235",
            "id": "pyup.io-35339",
            "more_info_path": "/vulnerabilities/CVE-2010-2235/35339",
            "specs": [
                "<2.0.7"
            ],
            "v": "<2.0.7"
        },
        {
            "advisory": "Cobbler v2.1.0 resolves missing CSRF protection in web interface using Django framework.",
            "cve": "CVE-2011-4952",
            "id": "pyup.io-62096",
            "more_info_path": "/vulnerabilities/CVE-2011-4952/62096",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Cobbler 2.6.0 includes a fix for CVE-2011-4954: Cobbler has local privilege escalation via the use of insecure location for PYTHON_EGG_CACHE.\r\nhttps://github.com/cobbler/cobbler/commit/3c97edff9f8453536ae5adfe930a8b084b5e4346",
            "cve": "CVE-2011-4954",
            "id": "pyup.io-37739",
            "more_info_path": "/vulnerabilities/CVE-2011-4954/37739",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Cobbler version Verified as present in Cobbler versions 2.6.11+, but code inspection suggests at least 2.0.0+ or possibly even older versions may be vulnerable contains a Cross Site Scripting (XSS) vulnerability in cobbler-web that can result in Privilege escalation to admin.. This attack appear to be exploitable via \"network connectivity\". Sending unauthenticated JavaScript payload to the Cobbler XMLRPC API (/cobbler_api).",
            "cve": "CVE-2018-1000225",
            "id": "pyup.io-67945",
            "more_info_path": "/vulnerabilities/CVE-2018-1000225/67945",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Cobbler version Verified as present in Cobbler versions 2.6.11+, but code inspection suggests at least 2.0.0+ or possibly even older versions may be vulnerable contains a Incorrect Access Control vulnerability in XMLRPC API (/cobbler_api) that can result in Privilege escalation, data manipulation or exfiltration, LDAP credential harvesting. This attack appear to be exploitable via \"network connectivity\". Taking advantage of improper validation of security tokens in API endpoints. Please note this is a different issue than CVE-2018-10931.",
            "cve": "CVE-2018-1000226",
            "id": "pyup.io-65837",
            "more_info_path": "/vulnerabilities/CVE-2018-1000226/65837",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Cobbler 3.3.0 and 3.2.2 include a fix for CVE-2021-40324: Cobbler before 3.3.0 allows arbitrary file write operations via upload_log_data.",
            "cve": "CVE-2021-40324",
            "id": "pyup.io-45314",
            "more_info_path": "/vulnerabilities/CVE-2021-40324/45314",
            "specs": [
                "<3.2.2"
            ],
            "v": "<3.2.2"
        },
        {
            "advisory": "Cobbler 3.3.0 and 3.2.2 include a fix for CVE-2021-40323: Cobbler before 3.3.0 allows log poisoning, and resultant Remote Code Execution, via an XMLRPC method that logs to the logfile for template injection.",
            "cve": "CVE-2021-40323",
            "id": "pyup.io-45276",
            "more_info_path": "/vulnerabilities/CVE-2021-40323/45276",
            "specs": [
                "<3.2.2"
            ],
            "v": "<3.2.2"
        },
        {
            "advisory": "Cobbler before 3.3.0 allows authorization bypass for modification of settings.\r\nhttps://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a",
            "cve": "CVE-2021-40325",
            "id": "pyup.io-45315",
            "more_info_path": "/vulnerabilities/CVE-2021-40325/45315",
            "specs": [
                "<3.3.0"
            ],
            "v": "<3.3.0"
        },
        {
            "advisory": "Cobbler 3.3.0 removes get-loaders code. It is not safe to download bootloaders from unknown sources.\r\nhttps://github.com/cobbler/cobbler/pull/2572",
            "cve": "PVE-2022-45316",
            "id": "pyup.io-45316",
            "more_info_path": "/vulnerabilities/PVE-2022-45316/45316",
            "specs": [
                "<3.3.0"
            ],
            "v": "<3.3.0"
        },
        {
            "advisory": "Cobbler 3.3.1 includes a fix for CVE-2021-45083: Files in /etc/cobbler are world readable. Two of those files contain some sensitive information that can be exposed to a local user who has non-privileged access to the server. The users.digest file contains the sha2-512 digest of users in a Cobbler local installation. In the case of an easy-to-guess password, it's trivial to obtain the plaintext string. The settings.yaml file contains secrets such as the hashed default password.",
            "cve": "CVE-2021-45083",
            "id": "pyup.io-45317",
            "more_info_path": "/vulnerabilities/CVE-2021-45083/45317",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "An issue was discovered in Cobbler before 3.3.1. In the templar.py file, the function check_for_invalid_imports can allow Cheetah code to import Python modules via the \"#from MODULE import\" substring. (Only lines beginning with #import are blocked.)",
            "cve": "CVE-2021-45082",
            "id": "pyup.io-45286",
            "more_info_path": "/vulnerabilities/CVE-2021-45082/45286",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "Cobbler 3.3.1 removes testing module, which was shipping a well known username and password combination.\r\nhttps://github.com/cobbler/cobbler/pull/2908",
            "cve": "PVE-2022-45320",
            "id": "pyup.io-45320",
            "more_info_path": "/vulnerabilities/PVE-2022-45320/45320",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "Cobbler 3.3.1 validates the data before logging it to avoid log file pollution.\r\nhttps://github.com/cobbler/cobbler/pull/2911",
            "cve": "PVE-2022-45319",
            "id": "pyup.io-45319",
            "more_info_path": "/vulnerabilities/PVE-2022-45319/45319",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "Cobbler 3.3.1 stabalizes the MongoDB serializer. In mongodb serializer class, when the config file is read, there is no sanity check. If the file get somewhat corrupted, it can lead to unexpected behaviour.\r\nhttps://github.com/cobbler/cobbler/pull/2919",
            "cve": "PVE-2022-45318",
            "id": "pyup.io-45318",
            "more_info_path": "/vulnerabilities/PVE-2022-45318/45318",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "Cobbler 3.3.2 includes a fix for CVE-2022-0860: Improper Authorization in GitHub repository cobbler/cobbler prior to 3.3.2.\r\nhttps://github.com/cobbler/cobbler/security/advisories/GHSA-mcg6-h362-cmq5",
            "cve": "CVE-2022-0860",
            "id": "pyup.io-45820",
            "more_info_path": "/vulnerabilities/CVE-2022-0860/45820",
            "specs": [
                "<3.3.2"
            ],
            "v": "<3.3.2"
        },
        {
            "advisory": "The set_mgmt_parameters function in item.py in cobbler before 2.2.2 allows context-dependent attackers to execute arbitrary code via vectors related to the use of the yaml.load function instead of the yaml.safe_load function, as demonstrated using Puppet.",
            "cve": "CVE-2011-4953",
            "id": "pyup.io-62098",
            "more_info_path": "/vulnerabilities/CVE-2011-4953/62098",
            "specs": [
                "<=2.2.1"
            ],
            "v": "<=2.2.1"
        },
        {
            "advisory": "Cobbler version up to 2.8.2 is vulnerable to a command injection vulnerability in the \"add repo\" component resulting in arbitrary code execution as root user.",
            "cve": "CVE-2017-1000469",
            "id": "pyup.io-66896",
            "more_info_path": "/vulnerabilities/CVE-2017-1000469/66896",
            "specs": [
                "<=2.8.2"
            ],
            "v": "<=2.8.2"
        },
        {
            "advisory": "An issue was discovered in Cobbler through 3.3.1. Routines in several files use the HTTP protocol instead of the more secure HTTPS.",
            "cve": "CVE-2021-45081",
            "id": "pyup.io-62201",
            "more_info_path": "/vulnerabilities/CVE-2021-45081/62201",
            "specs": [
                "<=3.3.1"
            ],
            "v": "<=3.3.1"
        },
        {
            "advisory": "A flaw was found in cobbler software component version 2.6.11-1. It suffers from an invalid parameter validation vulnerability, leading the arbitrary file reading. The flaw is triggered by navigating to a vulnerable URL via cobbler-web on a default installation.",
            "cve": "CVE-2016-9605",
            "id": "pyup.io-65817",
            "more_info_path": "/vulnerabilities/CVE-2016-9605/65817",
            "specs": [
                "==2.6.11-1"
            ],
            "v": "==2.6.11-1"
        },
        {
            "advisory": "A Command Injection in action_power.py in Cobbler prior to v2.6.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the (1) username or (2) password fields to the power_system method in the xmlrpc API.",
            "cve": "CVE-2012-2395",
            "id": "pyup.io-54074",
            "more_info_path": "/vulnerabilities/CVE-2012-2395/54074",
            "specs": [
                ">=0,<2.6.0"
            ],
            "v": ">=0,<2.6.0"
        },
        {
            "advisory": "Absolute path traversal vulnerability in the web interface in Cobbler 2.4.x through 2.6.x allows remote authenticated users to read arbitrary files via the Kickstart field in a profile.",
            "cve": "CVE-2014-3225",
            "id": "pyup.io-60960",
            "more_info_path": "/vulnerabilities/CVE-2014-3225/60960",
            "specs": [
                ">=2.4.0,<=2.6.0"
            ],
            "v": ">=2.4.0,<=2.6.0"
        },
        {
            "advisory": "It was found that cobbler 2.6.x exposed all functions from its CobblerXMLRPCInterface class over XMLRPC. A remote, unauthenticated attacker could use this flaw to gain high privileges within cobbler, upload files to arbitrary location in the context of the daemon.",
            "cve": "CVE-2018-10931",
            "id": "pyup.io-53996",
            "more_info_path": "/vulnerabilities/CVE-2018-10931/53996",
            "specs": [
                ">=2.6.0,<3.0.0"
            ],
            "v": ">=2.6.0,<3.0.0"
        },
        {
            "advisory": "Affected versions of Cobbler are vulnerable to Improper Authentication. Anyone can connect to cobbler XML-RPC server with known password and make changes.",
            "cve": "CVE-2024-47533",
            "id": "pyup.io-74187",
            "more_info_path": "/vulnerabilities/CVE-2024-47533/74187",
            "specs": [
                ">=3.0.0,<3.2.3",
                ">=3.3.0,<3.3.7"
            ],
            "v": ">=3.0.0,<3.2.3,>=3.3.0,<3.3.7"
        }
    ],
    "cockroachdb": [
        {
            "advisory": "Cockroachdb 0.3.2 updates 'urllib3' to v1.25.3 to include security fixes.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-54885",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/54885",
            "specs": [
                "<0.3.2"
            ],
            "v": "<0.3.2"
        },
        {
            "advisory": "Cockroachdb 0.3.2 updates 'urllib3' to v1.25.3 to include security fixes.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-37264",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/37264",
            "specs": [
                "<0.3.2"
            ],
            "v": "<0.3.2"
        }
    ],
    "codalab": [
        {
            "advisory": "codalab before 0.2.33 was using a version of gunicorn that had security vulnerabilities.",
            "cve": "PVE-2021-36386",
            "id": "pyup.io-36386",
            "more_info_path": "/vulnerabilities/PVE-2021-36386/36386",
            "specs": [
                "<0.2.33"
            ],
            "v": "<0.2.33"
        },
        {
            "advisory": "Codalab 0.5.12 fixes a vulnerability. No description of the vulnerability was included.",
            "cve": "PVE-2021-38927",
            "id": "pyup.io-38927",
            "more_info_path": "/vulnerabilities/PVE-2021-38927/38927",
            "specs": [
                "<0.5.12"
            ],
            "v": "<0.5.12"
        },
        {
            "advisory": "Codalab 0.5.33 includes a fix for some front-end vulnerabilities (with `npm audit fix`).",
            "cve": "PVE-2021-39434",
            "id": "pyup.io-39434",
            "more_info_path": "/vulnerabilities/PVE-2021-39434/39434",
            "specs": [
                "<0.5.33"
            ],
            "v": "<0.5.33"
        }
    ],
    "code-snapshot": [
        {
            "advisory": "Code-snapshot 0.2.4 updates its dependency 'requests' minimum requirement to v2.31.0 to include a security fix.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-58812",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/58812",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        }
    ],
    "codecarbon": [
        {
            "advisory": "Affected versions of codecarbon are potentially vulnerable to improper resource cleanup. When interrupted by a SIGTERM signal, the program terminates immediately using os._exit(1), bypassing cleanup code. The issue exists in the _handle_exit method.",
            "cve": "PVE-2025-76673",
            "id": "pyup.io-76673",
            "more_info_path": "/vulnerabilities/PVE-2025-76673/76673",
            "specs": [
                "<2.8.4"
            ],
            "v": "<2.8.4"
        }
    ],
    "codechecker": [
        {
            "advisory": "Codechecker 6.18.2 includes a fix for a XSS vulnerability. To solve this problem the server will always return the escaped version of these values which can be safely rendered on the UI.\r\nhttps://github.com/Ericsson/codechecker/pull/3549",
            "cve": "PVE-2023-59888",
            "id": "pyup.io-59888",
            "more_info_path": "/vulnerabilities/PVE-2023-59888/59888",
            "specs": [
                "<6.18.2"
            ],
            "v": "<6.18.2"
        },
        {
            "advisory": "Codechecker 6.2  includes a fix for a SQL Injection vulnerability.\r\nhttps://github.com/Ericsson/codechecker/pull/1066",
            "cve": "PVE-2023-60698",
            "id": "pyup.io-60698",
            "more_info_path": "/vulnerabilities/PVE-2023-60698/60698",
            "specs": [
                "<6.2"
            ],
            "v": "<6.2"
        },
        {
            "advisory": "Zip files uploaded to the server endpoint of `CodeChecker store` are not properly sanitized. An attacker, using a path traversal attack, can load and display files on the machine of `CodeChecker server`. The vulnerable endpoint is `/Default/v6.53/CodeCheckerService@massStoreRun`. The path traversal vulnerability allows reading data on the machine of the `CodeChecker server`, with the same permission level as the `CodeChecker server`. The attack requires a user account on the `CodeChecker server`, with permission to store to a server, and view the stored report. This vulnerability has been patched in version 6.23.",
            "cve": "CVE-2023-49793",
            "id": "pyup.io-71853",
            "more_info_path": "/vulnerabilities/CVE-2023-49793/71853",
            "specs": [
                "<6.23.0"
            ],
            "v": "<6.23.0"
        },
        {
            "advisory": "Affected versions of the codechecker package are vulnerable to Authentication Bypass due to improper URL path validation in the API endpoint handling. The vulnerability occurs when API URLs end with specific strings like \"Authentication\", \"Configuration\", or \"ServerInfo\", which causes the authentication mechanism to be bypassed and grants superuser privileges to all API endpoints except the Authentication endpoint itself. An unauthenticated remote attacker can exploit this vulnerability by crafting API requests with valid CodeChecker endpoints that terminate with these specific strings, allowing them to query, add, modify, or delete products on the CodeChecker server without any authentication.",
            "cve": "CVE-2024-10081",
            "id": "pyup.io-78814",
            "more_info_path": "/vulnerabilities/CVE-2024-10081/78814",
            "specs": [
                "<6.24.2"
            ],
            "v": "<6.24.2"
        },
        {
            "advisory": "Affected versions of the codechecker package are vulnerable to Authentication Method Confusion due to improper validation of authentication sources for the built-in root user account. The vulnerability exists in versions through 6.24.1, where an auto-generated superuser account with a weakly generated username is stored in the root.user file cannot be disabled and is unconditionally granted superuser permissions regardless of the authentication service used. An attacker who can create an account on any enabled external authentication service (such as LDAP or PAM) can exploit this vulnerability by registering with the same username as the built-in root user, thereby gaining full administrative access to the CodeChecker instance and control over all functionality accessible via the web interface.",
            "cve": "CVE-2024-10082",
            "id": "pyup.io-78816",
            "more_info_path": "/vulnerabilities/CVE-2024-10082/78816",
            "specs": [
                "<6.24.2"
            ],
            "v": "<6.24.2"
        },
        {
            "advisory": "Codechecker 6.24.2 includes a fix for an endpoint parsing issue that lead to unauthorized access.",
            "cve": "PVE-2024-73768",
            "id": "pyup.io-73768",
            "more_info_path": "/vulnerabilities/PVE-2024-73768/73768",
            "specs": [
                "<6.24.2"
            ],
            "v": "<6.24.2"
        },
        {
            "advisory": "Cross-site request forgery allows an unauthenticated attacker to hijack the authentication of a logged in user, and use the web API with the same permissions.",
            "cve": "CVE-2024-53829",
            "id": "pyup.io-76356",
            "more_info_path": "/vulnerabilities/CVE-2024-53829/76356",
            "specs": [
                "<6.24.5"
            ],
            "v": "<6.24.5"
        },
        {
            "advisory": "CodeChecker versions up to 6.24.5 contain an open redirect vulnerability due to missing protections against multiple slashes after the product name in the URL's path segment. This results in bypassing protections against CVE-2021-28861, leading to the same open redirect pathway.",
            "cve": "CVE-2025-1300",
            "id": "pyup.io-76325",
            "more_info_path": "/vulnerabilities/CVE-2025-1300/76325",
            "specs": [
                "<6.24.6"
            ],
            "v": "<6.24.6"
        },
        {
            "advisory": "Affected versions of the codechecker package are vulnerable to Buffer Overflow due to unsafe copying of user-controlled strings into a fixed-size stack buffer in the internal ldlogger library executed by the CodeChecker log command. The ldlogger component, invoked by CodeChecker\u2019s log command, uses strcpy() without bounds checking to copy inputs into a 4096-byte stack-allocated buffer, allowing an overrun when given excessively long arguments. A local attacker who can pass crafted command-line parameters or environment variables to the CodeChecker log can overflow the buffer and crash the process, with limited potential for data exposure or modification within the process context.",
            "cve": "CVE-2025-40843",
            "id": "pyup.io-79853",
            "more_info_path": "/vulnerabilities/CVE-2025-40843/79853",
            "specs": [
                "<6.26.2"
            ],
            "v": "<6.26.2"
        },
        {
            "advisory": "In Ericsson CodeChecker prior to 6.18.2, a Stored Cross-site scripting (XSS) vulnerability in the comments component of the reports viewer allows remote attackers to inject arbitrary web script or HTML via the POST JSON data of the /CodeCheckerService API.",
            "cve": "CVE-2021-44217",
            "id": "pyup.io-54377",
            "more_info_path": "/vulnerabilities/CVE-2021-44217/54377",
            "specs": [
                ">=0,<6.18.2"
            ],
            "v": ">=0,<6.18.2"
        }
    ],
    "codecov": [
        {
            "advisory": "Codecov 2.0.16 includes a fix for CVE-2019-10800: Remote code execution. The vulnerability exists due to improper sanitization of \"gcov\" arguments before being provided to the \"popen\" method. A remote authenticated attacker can execute arbitrary OS commands on the target system.",
            "cve": "CVE-2019-10800",
            "id": "pyup.io-37934",
            "more_info_path": "/vulnerabilities/CVE-2019-10800/37934",
            "specs": [
                "<2.0.16"
            ],
            "v": "<2.0.16"
        },
        {
            "advisory": "Codecov 2.0.17 fixes a reported command injection vulnerability.\r\nhttps://github.com/codecov/codecov-python/commit/f2c93c7893847e50639416c1bc2e38cb375825d8",
            "cve": "PVE-2021-38075",
            "id": "pyup.io-38075",
            "more_info_path": "/vulnerabilities/PVE-2021-38075/38075",
            "specs": [
                "<2.0.17"
            ],
            "v": "<2.0.17"
        }
    ],
    "codeforcesapipy": [
        {
            "advisory": "Codeforcesapipy 2.0.8 updates the 'lxml' dependency to 4.6.3 to resolve security issues.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-40099",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/40099",
            "specs": [
                "<2.0.8"
            ],
            "v": "<2.0.8"
        }
    ],
    "codeinterpreterapi": [
        {
            "advisory": "Codeinterpreterapi 0.0.14 updates its dependency 'langchain' to include a security fix.",
            "cve": "PVE-2023-61536",
            "id": "pyup.io-61748",
            "more_info_path": "/vulnerabilities/PVE-2023-61536/61748",
            "specs": [
                "<0.0.14"
            ],
            "v": "<0.0.14"
        }
    ],
    "coderedcms": [
        {
            "advisory": "views.py in Wagtail CRX CodeRed Extensions (formerly CodeRed CMS or coderedcms) before 0.22.3 allows upward protected/..%2f..%2f path traversal when serving protected media.",
            "cve": "CVE-2021-46897",
            "id": "pyup.io-65838",
            "more_info_path": "/vulnerabilities/CVE-2021-46897/65838",
            "specs": [
                "<0.22.3"
            ],
            "v": "<0.22.3"
        }
    ],
    "codex-autorunner": [
        {
            "advisory": "Affected versions of the codex-autorunner package are vulnerable to path traversal (path injection) due to insufficient normalization and containment checks on user-supplied repository path input. The stop_session route in src/codex_autorunner/routes/sessions.py allowed absolute paths to be resolved before enforcing repo_root containment (enabling symlink traversal edge cases).\r\nhttps://github.com/Git-on-my-level/codex-autorunner/commit/e09495b7fbb32a79797a73c6b6b1039f06596788",
            "cve": "PVE-2026-85397",
            "id": "pyup.io-85397",
            "more_info_path": "/vulnerabilities/PVE-2026-85397/85397",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "cognitojwt": [
        {
            "advisory": "Cognitojwt version 1.5.0 transitions from the outdated python-jose library, which relied on the ecdsa package containing unresolved vulnerabilities, to the more frequently updated joserfc library.",
            "cve": "CVE-2024-23342",
            "id": "pyup.io-68046",
            "more_info_path": "/vulnerabilities/CVE-2024-23342/68046",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        }
    ],
    "cohen3": [
        {
            "advisory": "Cohen3 version 0.8.3 updates its dependency \"requests\" to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-42040",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/42040",
            "specs": [
                "<0.8.3"
            ],
            "v": "<0.8.3"
        },
        {
            "advisory": "Cohen3 version 0.9.1 updates its dependency \"urlib3\" to v1.24.2 to include a security fix.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-42039",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/42039",
            "specs": [
                "<0.9.1"
            ],
            "v": "<0.9.1"
        }
    ],
    "coinbasepro": [
        {
            "advisory": "Coinbasepro 0.1.0 updates requests version to >=2.20.0 to address a security vulnerability.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36975",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36975",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        }
    ],
    "coincurve": [
        {
            "advisory": "coincurve before 8.0.0 does not support the new GitHub and PyPI security requirements. \r\nBinary wheels on macOS for Python 3.5 now uses Homebrew Python for compilation due to new security requirements.",
            "cve": "PVE-2021-36299",
            "id": "pyup.io-36299",
            "more_info_path": "/vulnerabilities/PVE-2021-36299/36299",
            "specs": [
                "<8.0.0"
            ],
            "v": "<8.0.0"
        }
    ],
    "colander": [
        {
            "advisory": "In Pylons Colander through 1.6, the URL validator allows an attacker to potentially cause an infinite loop thereby causing a denial of service via an unclosed parenthesis. See CVE-2017-18361.",
            "cve": "CVE-2017-18361",
            "id": "pyup.io-42247",
            "more_info_path": "/vulnerabilities/CVE-2017-18361/42247",
            "specs": [
                "<=1.6"
            ],
            "v": "<=1.6"
        }
    ],
    "coldsweat": [
        {
            "advisory": "Coldsweat 0.10.0 updates its dependency 'requests' to version '2.20.1' to include a security fix.\r\nhttps://github.com/passiomatic/coldsweat/commit/646edf0ef75cf62c7ba009a7ce62b4b8ffae26c3",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-59432",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/59432",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Coldsweat 0.10.0 updates its dependency 'requests' to version '2.20.1' to include a security fix.\r\nhttps://github.com/passiomatic/coldsweat/commit/646edf0ef75cf62c7ba009a7ce62b4b8ffae26c3",
            "cve": "CVE-2015-2296",
            "id": "pyup.io-59448",
            "more_info_path": "/vulnerabilities/CVE-2015-2296/59448",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Coldsweat 0.10.0 updates its dependency 'requests' to version '2.20.1' to include a security fix.\r\nhttps://github.com/passiomatic/coldsweat/commit/646edf0ef75cf62c7ba009a7ce62b4b8ffae26c3",
            "cve": "CVE-2014-1829",
            "id": "pyup.io-59446",
            "more_info_path": "/vulnerabilities/CVE-2014-1829/59446",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Coldsweat 0.10.0 updates its dependency 'requests' to version '2.20.1' to include a security fix.\r\nhttps://github.com/passiomatic/coldsweat/commit/646edf0ef75cf62c7ba009a7ce62b4b8ffae26c3",
            "cve": "CVE-2014-1830",
            "id": "pyup.io-59447",
            "more_info_path": "/vulnerabilities/CVE-2014-1830/59447",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        }
    ],
    "collaborative-article-sharing": [
        {
            "advisory": "Affected versions of Collaborative-article-sharing are vulnerable to Client-side cross-site scripting.",
            "cve": "PVE-2024-74343",
            "id": "pyup.io-74343",
            "more_info_path": "/vulnerabilities/PVE-2024-74343/74343",
            "specs": [
                "<0.1.0b2"
            ],
            "v": "<0.1.0b2"
        },
        {
            "advisory": "Affected versions of Collaborative-article-sharing are vulnerable to Sensitive Information Disclosure. Flask app was run in debug mode.",
            "cve": "PVE-2024-74358",
            "id": "pyup.io-74358",
            "more_info_path": "/vulnerabilities/PVE-2024-74358/74358",
            "specs": [
                "<0.1.0b2"
            ],
            "v": "<0.1.0b2"
        }
    ],
    "collective-contact-core": [
        {
            "advisory": "Collective.contact.core 1.10 fixes a security issue related to AddContact. The vulnerability was found in its dependency Plone CMS. See CVE-2016-7138.\r\nhttps://github.com/collective/collective.contact.core/pull/25",
            "cve": "CVE-2016-7138",
            "id": "pyup.io-25657",
            "more_info_path": "/vulnerabilities/CVE-2016-7138/25657",
            "specs": [
                "<1.10"
            ],
            "v": "<1.10"
        },
        {
            "advisory": "collective-contact-core before 1.10",
            "cve": "PVE-2021-36089",
            "id": "pyup.io-36089",
            "more_info_path": "/vulnerabilities/PVE-2021-36089/36089",
            "specs": [
                "<1.10"
            ],
            "v": "<1.10"
        }
    ],
    "collective-documentviewer": [
        {
            "advisory": "Collective.documentviewer 1.5.1 fixes a security issue on file resources permissions.\r\nhttps://github.com/collective/collective.documentviewer/commit/7222b0d30b1976d3f6773553bd6948c39efcbc20",
            "cve": "PVE-2021-25658",
            "id": "pyup.io-25658",
            "more_info_path": "/vulnerabilities/PVE-2021-25658/25658",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        }
    ],
    "collective-easyform": [
        {
            "advisory": "Collective-easyform version 3.0.5 doesn't resolves entities in the modeleditor and removes processing instructions (commit #254).",
            "cve": "PVE-2021-41911",
            "id": "pyup.io-41911",
            "more_info_path": "/vulnerabilities/PVE-2021-41911/41911",
            "specs": [
                "<3.0.5"
            ],
            "v": "<3.0.5"
        },
        {
            "advisory": "The modeleditor in collective.easyform 3.0.5 no longer resolves entities, and it removes processing instructions. This increases the security.\r\nhttps://github.com/collective/collective.easyform/commit/261ea800fbe3bd650a83b1fe7558ba51bd7d0c9e",
            "cve": "PVE-2021-39144",
            "id": "pyup.io-39144",
            "more_info_path": "/vulnerabilities/PVE-2021-39144/39144",
            "specs": [
                "<3.0.5"
            ],
            "v": "<3.0.5"
        }
    ],
    "collective-js-datatables": [
        {
            "advisory": "Collective.js.datatables 4.1.1 updates Datatables to 1.10.11, due to a XSS vulnerability in 1.10.4.",
            "cve": "CVE-2015-6384",
            "id": "pyup.io-25659",
            "more_info_path": "/vulnerabilities/CVE-2015-6384/25659",
            "specs": [
                "<4.1.1"
            ],
            "v": "<4.1.1"
        },
        {
            "advisory": "An attacker can seize control of a user session by leveraging a Cross-site scripting vulnerability. This allows the unauthorized user to modify a legitimate user's password and disrupt their session.",
            "cve": "PVE-2023-99913",
            "id": "pyup.io-62008",
            "more_info_path": "/vulnerabilities/PVE-2023-99913/62008",
            "specs": [
                ">=0.0a"
            ],
            "v": ">=0.0a"
        }
    ],
    "collective-noticeboard": [
        {
            "advisory": "collective-noticeboard before 0.7.1 has a security issue, anonymous users could modify notes positions.",
            "cve": "PVE-2021-35879",
            "id": "pyup.io-35879",
            "more_info_path": "/vulnerabilities/PVE-2021-35879/35879",
            "specs": [
                "<0.7.1"
            ],
            "v": "<0.7.1"
        },
        {
            "advisory": "Collective.noticeboard 0.7.1 fixes a security issue, anonymous users could modify notes positions.",
            "cve": "PVE-2021-25660",
            "id": "pyup.io-25660",
            "more_info_path": "/vulnerabilities/PVE-2021-25660/25660",
            "specs": [
                "<0.7.1"
            ],
            "v": "<0.7.1"
        }
    ],
    "collective-portlet-twitter": [
        {
            "advisory": "Collective.portlet.twitter 1.0b3 fixes a potential XSS (arbitrary injection) issue by escaping and quoting all attributes being set on the rendered portlet.\r\nhttps://github.com/collective/collective.portlet.twitter/pull/2",
            "cve": "PVE-2021-25661",
            "id": "pyup.io-25661",
            "more_info_path": "/vulnerabilities/PVE-2021-25661/25661",
            "specs": [
                "<1.0b3"
            ],
            "v": "<1.0b3"
        }
    ],
    "collective-tablepage": [
        {
            "advisory": "collective.tablepage 0.3 fixes a security problem: data inside text cells were transformed to HTML without any check.",
            "cve": "PVE-2021-25664",
            "id": "pyup.io-25664",
            "more_info_path": "/vulnerabilities/PVE-2021-25664/25664",
            "specs": [
                "<0.3"
            ],
            "v": "<0.3"
        }
    ],
    "collective-task": [
        {
            "advisory": "Collective-task 3.0.9 includes escaping to fix a XSS vulnerability.\r\nhttps://github.com/collective/collective.task/commit/1aac7f83fa2c2b41d59ba02748912953461f3fac",
            "cve": "PVE-2022-50678",
            "id": "pyup.io-50678",
            "more_info_path": "/vulnerabilities/PVE-2022-50678/50678",
            "specs": [
                "<3.0.9"
            ],
            "v": "<3.0.9"
        }
    ],
    "collective-xmpp-chat": [
        {
            "advisory": "Collective.xmpp.chat 0.3.1 includes an update in 'converse.js' that fixes a security issue.\r\nhttps://github.com/collective/collective.xmpp.chat/commit/4b6cb3a43158f866d84c4ce803b9016aef81adfe",
            "cve": "PVE-2021-25666",
            "id": "pyup.io-25666",
            "more_info_path": "/vulnerabilities/PVE-2021-25666/25666",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "collective.contact.widget": [
        {
            "advisory": "Collective.contact.widget 1.13 escapes contact title special characters in 'term-contact' viewlet to prevent XSS vulnerabilities.",
            "cve": "PVE-2022-49566",
            "id": "pyup.io-49566",
            "more_info_path": "/vulnerabilities/PVE-2022-49566/49566",
            "specs": [
                "<1.13"
            ],
            "v": "<1.13"
        },
        {
            "advisory": "A vulnerability classified as problematic was found in collective.contact.widget up to 1.12. This vulnerability affects the function title of the file src/collective/contact/widget/widgets.py. The manipulation leads to cross site scripting. The attack can be initiated remotely.",
            "cve": "CVE-2022-4638",
            "id": "pyup.io-72004",
            "more_info_path": "/vulnerabilities/CVE-2022-4638/72004",
            "specs": [
                "<1.13"
            ],
            "v": "<1.13"
        }
    ],
    "collective.dms.basecontent": [
        {
            "advisory": "Collective.dms.basecontent 1.7 escapes special characters when rendering to avoid potential XSS vulnerabilities.\r\nhttps://github.com/collective/collective.dms.basecontent/commit/6c4d616fcc771822a14ebae5e23f3f6d96d134bd",
            "cve": "PVE-2022-49567",
            "id": "pyup.io-49567",
            "more_info_path": "/vulnerabilities/PVE-2022-49567/49567",
            "specs": [
                "<1.7"
            ],
            "v": "<1.7"
        },
        {
            "advisory": "A vulnerability, which was classified as problematic, has been found in collective.dms.basecontent affected versions. This issue affects the function renderCell of the file src/collective/dms/basecontent/browser/column.py. The manipulation leads to cross-site scripting.",
            "cve": "CVE-2022-4495",
            "id": "pyup.io-72005",
            "more_info_path": "/vulnerabilities/CVE-2022-4495/72005",
            "specs": [
                "<1.7"
            ],
            "v": "<1.7"
        }
    ],
    "collective.documentgenerator": [
        {
            "advisory": "Collective.documentgenerator 3.33 adds character escaping to avoid XSS attacks via 'TemplatesTable'.",
            "cve": "PVE-2022-49408",
            "id": "pyup.io-49408",
            "more_info_path": "/vulnerabilities/PVE-2022-49408/49408",
            "specs": [
                "<3.33"
            ],
            "v": "<3.33"
        }
    ],
    "collective.iconifiedcategory": [
        {
            "advisory": "Collective.iconifiedcategory 0.54 applies escaping to avoid code injection vulnerabilities.\r\nhttps://github.com/collective/collective.iconifiedcategory/commit/7bcd148d7649be0e1df82ec75bbc46e2925eba2d",
            "cve": "PVE-2022-49411",
            "id": "pyup.io-49411",
            "more_info_path": "/vulnerabilities/PVE-2022-49411/49411",
            "specs": [
                "<0.54"
            ],
            "v": "<0.54"
        }
    ],
    "collective.task": [
        {
            "advisory": "A vulnerability was found in collective.task affected versions. It has been classified as problematic. This affects the function renderCell/AssignedGroupColumn of the file src/collective/task/browser/table.py. The manipulation leads to cross-site scripting. It is possible to initiate the attack remotely.",
            "cve": "CVE-2022-4527",
            "id": "pyup.io-72006",
            "more_info_path": "/vulnerabilities/CVE-2022-4527/72006",
            "specs": [
                "<3.0.9"
            ],
            "v": "<3.0.9"
        }
    ],
    "collored": [
        {
            "advisory": "Collored is a malicious package, typosquatting. It installs Malware in your system.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick",
            "cve": "PVE-2022-47815",
            "id": "pyup.io-47815",
            "more_info_path": "/vulnerabilities/PVE-2022-47815/47815",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "colorsama": [
        {
            "advisory": "Colorsama is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51685",
            "id": "pyup.io-51685",
            "more_info_path": "/vulnerabilities/PVE-2022-51685/51685",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "colorslib": [
        {
            "advisory": "Colorslib is a malicious package. It installs info-stealing Malware.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-lolip0p-pypi-packages-install-info-stealing-malware",
            "cve": "PVE-2023-52924",
            "id": "pyup.io-52924",
            "more_info_path": "/vulnerabilities/PVE-2023-52924/52924",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "colorwin": [
        {
            "advisory": "Colorwin is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51683",
            "id": "pyup.io-51683",
            "more_info_path": "/vulnerabilities/PVE-2022-51683/51683",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "colossalai": [
        {
            "advisory": "Colossalai 0.1.11rc1 addresses security concerns related to subprocess handling. It specifically rectifies insecure subprocess usage by modifying the way subprocesses are invoked, enhancing the security and reliability of the code. This change is crucial for preventing potential vulnerabilities in the application's execution environment.",
            "cve": "PVE-2024-65063",
            "id": "pyup.io-65063",
            "more_info_path": "/vulnerabilities/PVE-2024-65063/65063",
            "specs": [
                "<0.1.11rc1"
            ],
            "v": "<0.1.11rc1"
        }
    ],
    "colourama": [
        {
            "advisory": "Colourama is a typosquatting package. It shows a malicious behavior, for example, it may leak your sensitive data and/or gain unauthorized persistence in your system.\r\nhttps://www.zdnet.com/article/twelve-malicious-python-libraries-found-and-removed-from-pypi/",
            "cve": "PVE-2022-45412",
            "id": "pyup.io-45412",
            "more_info_path": "/vulnerabilities/PVE-2022-45412/45412",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "cometlogger": [
        {
            "advisory": "The CometLogger package has been identified as an extensive data theft tool targeting multiple platforms. This malware steals sensitive user data including cookies, passwords, and tokens from popular services like Discord, Steam, Instagram, X, TikTok, Reddit, Twitch, Spotify, and Roblox. Users should immediately scan for and remove this package to protect their account credentials.",
            "cve": "PVE-2024-74754",
            "id": "pyup.io-74754",
            "more_info_path": "/vulnerabilities/PVE-2024-74754/74754",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "comfy-cli": [
        {
            "advisory": "Affected versions of the comfy-cli package are vulnerable to CRLF Injection due to improper neutralization of carriage return and line feed characters in configuration values written to disk. The write_config() function uses Python ConfigParser to persist user-influenced HTTP query parameter values into config.ini without stripping CRLF (and NUL) characters, allowing injected line breaks to be interpreted as additional configuration entries.",
            "cve": "CVE-2026-22777",
            "id": "pyup.io-84417",
            "more_info_path": "/vulnerabilities/CVE-2026-22777/84417",
            "specs": [
                ">=4.0.0,<=4.0.4",
                "<3.39.2"
            ],
            "v": ">=4.0.0,<=4.0.4,<3.39.2"
        }
    ],
    "commlib-py": [
        {
            "advisory": "Commlib-py 0.11.5 updates its dependency 'certifi' to include a security fix.",
            "cve": "CVE-2024-39689",
            "id": "pyup.io-73597",
            "more_info_path": "/vulnerabilities/CVE-2024-39689/73597",
            "specs": [
                "<0.11.5"
            ],
            "v": "<0.11.5"
        }
    ],
    "commondatamodel-objectmodel": [
        {
            "advisory": "Microsoft Common Data Model SDK Denial of Service Vulnerability.",
            "cve": "CVE-2023-36566",
            "id": "pyup.io-64990",
            "more_info_path": "/vulnerabilities/CVE-2023-36566/64990",
            "specs": [
                ">=0,<1.7.4"
            ],
            "v": ">=0,<1.7.4"
        }
    ],
    "commonground-api-common": [
        {
            "advisory": "Affected versions of the commonground-api-common package are vulnerable to Improper Input Validation due to vng-api-common.middleware.AuthMiddleware passing the string \"HS256\" to PyJWT\u2019s algorithms parameter instead of a list, enabling substring matching on the alg header. The middleware\u2019s JWT verification logic compares the client-supplied alg value using Python\u2019s in operator, so any alg that is a substring of \"HS256\" (for example, \"HS25\" or \"HS2\") would erroneously satisfy the allow-check, though PyJWT\u2019s explicit allow-list of supported algorithms prevents practical misuse.",
            "cve": "PVE-2024-68087",
            "id": "pyup.io-68497",
            "more_info_path": "/vulnerabilities/PVE-2024-68087/68497",
            "specs": [
                "<=1.12.1"
            ],
            "v": "<=1.12.1"
        }
    ],
    "compas": [
        {
            "advisory": "Compas 1.17.5 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.\r\nhttps://github.com/compas-dev/compas/commit/0d0f9bec24511fe5dbc77ef73ee617dc83b4420e",
            "cve": "CVE-2007-4559",
            "id": "pyup.io-61127",
            "more_info_path": "/vulnerabilities/CVE-2007-4559/61127",
            "specs": [
                "<1.17.5"
            ],
            "v": "<1.17.5"
        }
    ],
    "compliance-trestle": [
        {
            "advisory": "Compliance-trestle 0.15.0 updates its dependency 'pydantic' to 1.8.2 for an security issue.",
            "cve": "CVE-2021-29510",
            "id": "pyup.io-40566",
            "more_info_path": "/vulnerabilities/CVE-2021-29510/40566",
            "specs": [
                "<0.15.0"
            ],
            "v": "<0.15.0"
        },
        {
            "advisory": "Compliance-trestle 0.26.0 removes user names from logs.\r\nhttps://github.com/IBM/compliance-trestle/commit/4d075b89776552a1f58751674e2056ac7afac3cc",
            "cve": "PVE-2021-42185",
            "id": "pyup.io-42185",
            "more_info_path": "/vulnerabilities/PVE-2021-42185/42185",
            "specs": [
                "<0.26.0"
            ],
            "v": "<0.26.0"
        },
        {
            "advisory": "Compliance-trestle 2.4.0 updates its urllib3 dependency to version 1.26.17 due to a vulnerability (CVE-2023-43804). This vulnerability could lead to the unintentional leakage of sensitive information via HTTP redirects to a different origin if the user doesn't disable redirects explicitly. This issue has been patched in urllib3 version 1.26.17 or 2.0.5.\r\nhttps://github.com/oscal-compass/compliance-trestle/pull/1472/commits/f0ce7047d1b48cc9534b262a5844d52541400d5d",
            "cve": "CVE-2023-43804",
            "id": "pyup.io-63243",
            "more_info_path": "/vulnerabilities/CVE-2023-43804/63243",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Compliance-trestle 2.5.0 updates its cryptography dependency to version 41.0.6 due to a critical vulnerability (CVE-2023-49083). This vulnerability could lead to a NULL-pointer dereference and segfault when deserializing a PKCS7 blob/certificate, potentially causing a Denial of Service (DoS) and system instability.\r\nhttps://github.com/oscal-compass/compliance-trestle/pull/1479/commits/1ed9f5ccec1e37f625eb9253dd07f8dee994cfe4",
            "cve": "CVE-2023-49083",
            "id": "pyup.io-63242",
            "more_info_path": "/vulnerabilities/CVE-2023-49083/63242",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Compliance-trestle 2.5.0 updates its cryptography dependency to version 41.0.6 due to a vulnerability (CVE-2023-48795). This vulnerability, known as the Terrapin attack, allows remote attackers to bypass integrity checks, potentially downgrading or disabling some security features in the SSH transport protocol.\r\nhttps://github.com/oscal-compass/compliance-trestle/pull/1486/commits/5657b72a757b094777773b5e1d7849ce3b970dd1",
            "cve": "CVE-2023-48795",
            "id": "pyup.io-63247",
            "more_info_path": "/vulnerabilities/CVE-2023-48795/63247",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Compliance-trestle 2.5.1 updates its dependency 'jinja2' to v3.1.3 to include a security fix.\r\nhttps://github.com/oscal-compass/compliance-trestle/pull/1498",
            "cve": "CVE-2024-22195",
            "id": "pyup.io-64313",
            "more_info_path": "/vulnerabilities/CVE-2024-22195/64313",
            "specs": [
                "<2.5.1"
            ],
            "v": "<2.5.1"
        },
        {
            "advisory": "Compliance-trestle version 2.6.0 upgrades its cryptography library to version 42.0.0 from 41.0.6 to mitigate the security issue CVE-2023-50782.\r\nhttps://github.com/oscal-compass/compliance-trestle/pull/1509/commits/41c880a2122fc52820e6fcee6f1193fd937c0673",
            "cve": "CVE-2023-50782",
            "id": "pyup.io-65626",
            "more_info_path": "/vulnerabilities/CVE-2023-50782/65626",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Compliance-trestle 3.3.0 updates its dependency 'urllib3' from version 1.26.17 to 1.26.19 to include a security fix.",
            "cve": "CVE-2024-37891",
            "id": "pyup.io-72186",
            "more_info_path": "/vulnerabilities/CVE-2024-37891/72186",
            "specs": [
                "<3.3.0"
            ],
            "v": "<3.3.0"
        },
        {
            "advisory": "Compliance-trestle 3.3.0 updates its dependency 'Jinja2' from version 3.1.3 to 3.1.4 to include a security fix.",
            "cve": "CVE-2024-34064",
            "id": "pyup.io-72184",
            "more_info_path": "/vulnerabilities/CVE-2024-34064/72184",
            "specs": [
                "<3.3.0"
            ],
            "v": "<3.3.0"
        }
    ],
    "composer": [
        {
            "advisory": "Composer 0.13.0 updates its dependency 'pillow' to v9.0.0 in Dockerfile to include security fixes.\r\nhttps://github.com/mosaicml/composer/pull/2007",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-53694",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/53694",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Composer 0.13.0 updates its dependency 'pillow' to v9.0.0 in Dockerfile to include security fixes.\r\nhttps://github.com/mosaicml/composer/pull/2007",
            "cve": "PVE-2021-44525",
            "id": "pyup.io-53693",
            "more_info_path": "/vulnerabilities/PVE-2021-44525/53693",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Composer 0.13.0 updates its dependency 'pillow' to v9.0.0 in Dockerfile to include security fixes.\r\nhttps://github.com/mosaicml/composer/pull/2007",
            "cve": "PVE-2022-44524",
            "id": "pyup.io-53692",
            "more_info_path": "/vulnerabilities/PVE-2022-44524/53692",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Composer 0.13.0 updates its dependency 'pillow' to v9.0.0 in Dockerfile to include security fixes.\r\nhttps://github.com/mosaicml/composer/pull/2007",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-53691",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/53691",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Composer 0.13.0 updates its dependency 'pillow' to v9.0.0 in Dockerfile to include security fixes.\r\nhttps://github.com/mosaicml/composer/pull/2007",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-53687",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/53687",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Composer 0.13.0 updates its dependency 'ipython' to v8.11.0 in Dockerfile to include a security fix.\r\nhttps://github.com/mosaicml/composer/pull/2007",
            "cve": "CVE-2023-24816",
            "id": "pyup.io-53697",
            "more_info_path": "/vulnerabilities/CVE-2023-24816/53697",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Composer 0.13.0 updates its dependency 'urllib3' requirement to '>=1.26.5,<2'' in Dockerfile to include a security fix.\r\nhttps://github.com/mosaicml/composer/pull/2007",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-53696",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/53696",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Composer 0.13.0 updates its dependency 'certifi' requirement to '>=2022.12.7' in Dockerfile to include a security fix.\r\nhttps://github.com/mosaicml/composer/pull/2007",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-53695",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/53695",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Composer 0.9.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/mosaicml/composer/pull/1328",
            "cve": "PVE-2023-60601",
            "id": "pyup.io-60601",
            "more_info_path": "/vulnerabilities/PVE-2023-60601/60601",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        }
    ],
    "composio": [
        {
            "advisory": "Affected versions of the composio package are vulnerable to Path Traversal due to improper sanitization of user-controlled file path input in the _download_file_or_dir function. Within composio.server.api._download_file_or_dir, the path supplied by the client is concatenated into filesystem paths without normalization or verification that it remains under a restricted base directory, enabling traversal using sequences to access unintended locations.",
            "cve": "CVE-2025-56427",
            "id": "pyup.io-82329",
            "more_info_path": "/vulnerabilities/CVE-2025-56427/82329",
            "specs": [
                "<=0.7.20"
            ],
            "v": "<=0.7.20"
        }
    ],
    "composio-claude": [
        {
            "advisory": "Composio affected versions are vulnerable to Command Execution in composioopenai, composioclaude, and composiojulep via the handletool_calls function.",
            "cve": "CVE-2024-53526",
            "id": "pyup.io-76366",
            "more_info_path": "/vulnerabilities/CVE-2024-53526/76366",
            "specs": [
                ">=0.5.40,<0.6.9"
            ],
            "v": ">=0.5.40,<0.6.9"
        }
    ],
    "composio-core": [
        {
            "advisory": "In composiohq/composio, the mathematical_calculator endpoint uses the unsafe eval() function to perform mathematical operations. This can lead to arbitrary code execution if untrusted input is passed to the eval() function.",
            "cve": "CVE-2024-8953",
            "id": "pyup.io-76199",
            "more_info_path": "/vulnerabilities/CVE-2024-8953/76199",
            "specs": [
                "<0.5.43"
            ],
            "v": "<0.5.43"
        },
        {
            "advisory": "A Server-Side Request Forgery (SSRF) vulnerability exists in composiohq/composio, specifically in the /api/actions/execute/WEBTOOL_SCRAPE_WEBSITE_CONTENT endpoint. This vulnerability allows an attacker to read files, access AWS metadata, and interact with local services on the system.",
            "cve": "CVE-2024-8952",
            "id": "pyup.io-76201",
            "more_info_path": "/vulnerabilities/CVE-2024-8952/76201",
            "specs": [
                "<=0.4.2"
            ],
            "v": "<=0.4.2"
        },
        {
            "advisory": "A Server-Side Request Forgery (SSRF) vulnerability exists in composiohq/composio version v0.4.4. This vulnerability allows an attacker to read the contents of any file in the system by exploiting the BROWSERTOOL_GOTO_PAGE and BROWSERTOOL_GET_PAGE_DETAILS actions.",
            "cve": "CVE-2024-8955",
            "id": "pyup.io-76196",
            "more_info_path": "/vulnerabilities/CVE-2024-8955/76196",
            "specs": [
                "<=0.4.4"
            ],
            "v": "<=0.4.4"
        },
        {
            "advisory": "A security vulnerability affects the composiohq composio library. The vulnerability exists in the Calculator function of the file python/composio/tools/local/mathematical/actions/calculator.py. Attackers can exploit this vulnerability to perform code injection, potentially executing arbitrary code on the target system. This vulnerability has been publicly disclosed and exploits may exist in the wild.",
            "cve": "CVE-2024-8864",
            "id": "pyup.io-73301",
            "more_info_path": "/vulnerabilities/CVE-2024-8864/73301",
            "specs": [
                "<=0.5.6"
            ],
            "v": "<=0.5.6"
        },
        {
            "advisory": "A critical security vulnerability affects the composiohq composio library. The vulnerability exists in the path function of the file composio\\server\\api.py. Attackers can manipulate the 'file' argument to achieve path traversal, potentially accessing unauthorized files on the system. This vulnerability has been publicly disclosed and exploits may exist in the wild. The vendor has not responded to disclosure attempts, underscoring the urgency of this update. Never process file paths from untrusted sources without proper sanitization and validation.",
            "cve": "CVE-2024-8865",
            "id": "pyup.io-73299",
            "more_info_path": "/vulnerabilities/CVE-2024-8865/73299",
            "specs": [
                "<=0.5.8"
            ],
            "v": "<=0.5.8"
        }
    ],
    "composio-julep": [
        {
            "advisory": "Composio affected versions are vulnerable to Command Execution in composioopenai, composioclaude, and composiojulep via the handletool_calls function.",
            "cve": "CVE-2024-53526",
            "id": "pyup.io-76368",
            "more_info_path": "/vulnerabilities/CVE-2024-53526/76368",
            "specs": [
                ">=0.5.40,<0.6.9"
            ],
            "v": ">=0.5.40,<0.6.9"
        }
    ],
    "composio-openai": [
        {
            "advisory": "Composio affected versions are vulnerable to Command Execution in composioopenai, composioclaude, and composiojulep via the handletool_calls function.",
            "cve": "CVE-2024-53526",
            "id": "pyup.io-76367",
            "more_info_path": "/vulnerabilities/CVE-2024-53526/76367",
            "specs": [
                ">=0.5.40,<0.6.9"
            ],
            "v": ">=0.5.40,<0.6.9"
        }
    ],
    "conan": [
        {
            "advisory": "Conan 1.49.0 updates its dependency 'pyjwt' requirement to \">=2.4.0, <3.0.0\" to include a security fix.",
            "cve": "CVE-2022-29217",
            "id": "pyup.io-49249",
            "more_info_path": "/vulnerabilities/CVE-2022-29217/49249",
            "specs": [
                "<1.49.0"
            ],
            "v": "<1.49.0"
        },
        {
            "advisory": "Affected versions of the Conan package manager are vulnerable to Improper Authorization (CWE-285). The server's authorization mechanism allowed users to bypass permission checks if the package owner's username matched their own, potentially leading to unauthorized access or modification of packages. This vulnerability can be exploited by any authenticated user who owns a package, resulting in privilege escalation. The affected methods are check_read_conan, check_write_conan, and check_delete_conan in authorize.py, as well as authentication checks in file_downloader.py and file_uploader.py.",
            "cve": "PVE-2024-73937",
            "id": "pyup.io-73937",
            "more_info_path": "/vulnerabilities/PVE-2024-73937/73937",
            "specs": [
                "<2.9.0"
            ],
            "v": "<2.9.0"
        }
    ],
    "concrete-datastore": [
        {
            "advisory": "Concrete-datastore 1.22.0 adds checks to prevent unauthorized queries.\r\nhttps://github.com/Netsach/concrete-datastore/pull/69",
            "cve": "PVE-2021-39449",
            "id": "pyup.io-39449",
            "more_info_path": "/vulnerabilities/PVE-2021-39449/39449",
            "specs": [
                "<1.22.0"
            ],
            "v": "<1.22.0"
        },
        {
            "advisory": "Concrete-datastore 1.23.0 adds checks on the url_format for reset password view to avoid template injections.\r\nhttps://github.com/Netsach/concrete-datastore/commit/f852fb003da373b958623dc8fd383c7ac09f0e80",
            "cve": "PVE-2021-39709",
            "id": "pyup.io-39709",
            "more_info_path": "/vulnerabilities/PVE-2021-39709/39709",
            "specs": [
                "<1.23.0"
            ],
            "v": "<1.23.0"
        }
    ],
    "conference-scheduler-cli": [
        {
            "advisory": "In conference-scheduler-cli, a pickle.load call on imported data allows remote attackers to execute arbitrary code via a crafted .pickle file, as demonstrated by Python code that contains an os.system call.",
            "cve": "CVE-2018-14572",
            "id": "pyup.io-36425",
            "more_info_path": "/vulnerabilities/CVE-2018-14572/36425",
            "specs": [
                "<=0.10.1"
            ],
            "v": "<=0.10.1"
        }
    ],
    "confidant": [
        {
            "advisory": "Confidant 1.1.13 includes a security fix. It was discovered when adding tests after a refactor of some of the KMS authentication code that confidant wasn't properly checking the expiration of KMS auth tokens. If tokens were able to be exfiltrated from a service, they could be used indefinitely. Also, any tokens that are expired will now correctly fail to authenticate.",
            "cve": "PVE-2021-26670",
            "id": "pyup.io-26670",
            "more_info_path": "/vulnerabilities/PVE-2021-26670/26670",
            "specs": [
                "<1.1.13"
            ],
            "v": "<1.1.13"
        },
        {
            "advisory": "confidant 1.1.14 contains a security fix: While preparing for the 1.1 stable release Lyft found a KMS  authentication vulnerability in the unreleased 1.1 branch while performing an  audit of the code. The vulnerability was introduced while adding the scoped auth  key feature (for limiting authentication keys and services to specific AWS  accounts), where the key was not properly checked after decryption. This check is  an additional verification to add additional safety on-top of the IAM policy of  your KMS keys. If IAM policy allows users to use KMS keys without limits on  encryption context, a KMS key that wasn't intended to be used for auth, could be  used for auth.",
            "cve": "PVE-2021-25668",
            "id": "pyup.io-25668",
            "more_info_path": "/vulnerabilities/PVE-2021-25668/25668",
            "specs": [
                "<1.1.14"
            ],
            "v": "<1.1.14"
        },
        {
            "advisory": "Confidant 1.10.0 upgrade 'gevent' and 'greenlet' dependencies to fix CVE-2016-5180.",
            "cve": "CVE-2016-5180",
            "id": "pyup.io-38504",
            "more_info_path": "/vulnerabilities/CVE-2016-5180/38504",
            "specs": [
                "<1.10.0"
            ],
            "v": "<1.10.0"
        },
        {
            "advisory": "Confidant 1.6.0 updates python-saml to address CVE-2016-1000252.",
            "cve": "CVE-2016-1000252",
            "id": "pyup.io-38505",
            "more_info_path": "/vulnerabilities/CVE-2016-1000252/38505",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'gunicorn' to a version >=19.9.0 to include security fixes.",
            "cve": "PVE-2021-40103",
            "id": "pyup.io-45038",
            "more_info_path": "/vulnerabilities/PVE-2021-40103/45038",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'pyyaml' to v5.1.2 to include a security fix.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-45036",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/45036",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'flask' to v1.1.1 to include security fixes.",
            "cve": "CVE-2019-1010083",
            "id": "pyup.io-45033",
            "more_info_path": "/vulnerabilities/CVE-2019-1010083/45033",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "Confidant 5.0.0 updates its dependency 'jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-45039",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/45039",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "Confidant 5.0.0 updates its dependency 'werkzeug' to v0.15.6 to include a security fix.",
            "cve": "CVE-2019-14806",
            "id": "pyup.io-45043",
            "more_info_path": "/vulnerabilities/CVE-2019-14806/45043",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'lxml' to v4.4.1 to include security fixes.",
            "cve": "CVE-2018-19787",
            "id": "pyup.io-45040",
            "more_info_path": "/vulnerabilities/CVE-2018-19787/45040",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'pyopenssl' to v19.0.0 to include security fixes.",
            "cve": "CVE-2018-1000808",
            "id": "pyup.io-45032",
            "more_info_path": "/vulnerabilities/CVE-2018-1000808/45032",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'flask' to v1.1.1 to include security fixes.",
            "cve": "CVE-2018-1000656",
            "id": "pyup.io-45034",
            "more_info_path": "/vulnerabilities/CVE-2018-1000656/45034",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "Confidant 5.0.0 updates its dependency 'pyopenssl' to v19.0.0 to include security fixes.",
            "cve": "CVE-2018-1000807",
            "id": "pyup.io-37471",
            "more_info_path": "/vulnerabilities/CVE-2018-1000807/37471",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'requests' to a version >=2.22.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-45035",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/45035",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'lxml' to v4.4.1 to include security fixes.",
            "cve": "PVE-2021-39195",
            "id": "pyup.io-45041",
            "more_info_path": "/vulnerabilities/PVE-2021-39195/45041",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'gunicorn' to a version >=19.9.0 to include security fixes.",
            "cve": "CVE-2018-1000164",
            "id": "pyup.io-45037",
            "more_info_path": "/vulnerabilities/CVE-2018-1000164/45037",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "In confidant 5.0.0 updates its dependency 'python3-saml' to v1.8.0 to include a security fix.",
            "cve": "PVE-2021-39454",
            "id": "pyup.io-45042",
            "more_info_path": "/vulnerabilities/PVE-2021-39454/45042",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "Confidant 6.3.0 adds support for keeping track of when credentials should be rotated. It therefore adds three new fields to the Credential model, two of which improve the security (`last_decrypted_date` and `last_rotation_date`). The former explicitly stores when someone viewed a credential. Certain credentials can potentially be highly vulnerable and could benefit from being rotated the moment the credential pair is viewed. The latter stores when a credential was last rotated. Some credentials might need to periodically be rotated for security purposes.",
            "cve": "PVE-2021-38560",
            "id": "pyup.io-38560",
            "more_info_path": "/vulnerabilities/PVE-2021-38560/38560",
            "specs": [
                "<6.3.0"
            ],
            "v": "<6.3.0"
        },
        {
            "advisory": "Confidant fixes potential XSS from API call by enforcing strict HTTP response headers.",
            "cve": "PVE-2025-75464",
            "id": "pyup.io-75464",
            "more_info_path": "/vulnerabilities/PVE-2025-75464/75464",
            "specs": [
                "<6.6.2"
            ],
            "v": "<6.6.2"
        },
        {
            "advisory": "Confidant affected versions contain a critical Cross-Site Scripting (XSS) vulnerability affecting multiple API endpoints for credential and service operations. This stored XSS flaw enables authenticated attackers with credential creation privileges to inject malicious scripts, potentially compromising other users' sessions, stealing sensitive information, or executing unauthorized actions. Inadequate input sanitization and improper content-type headers in API responses cause this vulnerability. Developers have patched the issue by implementing robust XSS protection measures, including security headers and proper content-type settings for API responses.",
            "cve": "CVE-2024-45793",
            "id": "pyup.io-73295",
            "more_info_path": "/vulnerabilities/CVE-2024-45793/73295",
            "specs": [
                "<6.6.2"
            ],
            "v": "<6.6.2"
        }
    ],
    "confidence": [
        {
            "advisory": "Confidence before 0.4 uses unsafe 'yaml.load()' which may lead to code execution.\r\nhttps://github.com/NetherlandsForensicInstitute/confidence/commit/c94f3510aabf1d8f67e58ae0d3350c98821d296b",
            "cve": "PVE-2021-36308",
            "id": "pyup.io-36308",
            "more_info_path": "/vulnerabilities/PVE-2021-36308/36308",
            "specs": [
                "<0.4"
            ],
            "v": "<0.4"
        }
    ],
    "configframework": [
        {
            "advisory": "Configframework 4.0.1 updates its dependency 'pygments' to version '2.15.0' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/Rud356/ConfigFramework/commit/3eb83b9099fff6bf2d80bf2cd79fb3e62933fde6",
            "cve": "CVE-2022-40896",
            "id": "pyup.io-60146",
            "more_info_path": "/vulnerabilities/CVE-2022-40896/60146",
            "specs": [
                "<4.0.1"
            ],
            "v": "<4.0.1"
        }
    ],
    "configobj": [
        {
            "advisory": "The configobj package affected versions contains a Regular Expression Denial of Service (ReDoS) vulnerability in its validate function. The vulnerable regex (.+?)\\((.*)\\) allows attackers to cause denial of service using specially crafted input with nested parentheses. This issue primarily affects server-side applications using configobj for configuration parsing. The vulnerability is patched by modifying the regex to ([^\\(\\)]+?)\\((.*)\\), preventing matching of nested parentheses. \r\nNOTE: This is only exploitable in the case of a developer putting the offending value in a server side configuration file.",
            "cve": "CVE-2023-26112",
            "id": "pyup.io-54843",
            "more_info_path": "/vulnerabilities/CVE-2023-26112/54843",
            "specs": [
                "<5.0.9"
            ],
            "v": "<5.0.9"
        }
    ],
    "confire": [
        {
            "advisory": "An exploitable vulnerability exists in the YAML parsing functionality in config.py in Confire 0.2.0. Due to the user-specific configuration being loaded from \"~/.confire.yaml\" using the yaml.load function, a YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability.",
            "cve": "CVE-2017-16763",
            "id": "pyup.io-35721",
            "more_info_path": "/vulnerabilities/CVE-2017-16763/35721",
            "specs": [
                "<=0.2.0"
            ],
            "v": "<=0.2.0"
        }
    ],
    "confluent-kafka": [
        {
            "advisory": "Confluent-kafka 1.1.0 securely clears the private key data from memory after last use.",
            "cve": "PVE-2021-37508",
            "id": "pyup.io-37508",
            "more_info_path": "/vulnerabilities/PVE-2021-37508/37508",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Confluent-kafka 1.3.0 updates builtin C dependency 'lz4' to v1.9.2 to include a security fix.",
            "cve": "CVE-2019-17543",
            "id": "pyup.io-38072",
            "more_info_path": "/vulnerabilities/CVE-2019-17543/38072",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Confluent-kafka 1.4.0 fixes a security issue in the SASL SCRAM protocol handler:  If 'sasl.username' and 'sasl.password' contained characters that needed escaping, a buffer overflow and heap corruption would occur. This was protected, but too late, by an assertion.",
            "cve": "PVE-2022-48601",
            "id": "pyup.io-48601",
            "more_info_path": "/vulnerabilities/PVE-2022-48601/48601",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Confluent-kafka 1.4.0 fixes a security issue in the SASL SCRAM protocol handler the client nonce, which is expected to be a random string, was a static string.",
            "cve": "PVE-2021-38165",
            "id": "pyup.io-38165",
            "more_info_path": "/vulnerabilities/PVE-2021-38165/38165",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Confluent-kafka enhances the security of the client by removing the usage of the strcpy function. The use of strcpy can lead to security vulnerabilities, such as buffer overflows because it does not perform bounds checking. By eliminating this function, the update mitigates potential risks associated with unsafe string handling.",
            "cve": "PVE-2024-72117",
            "id": "pyup.io-72117",
            "more_info_path": "/vulnerabilities/PVE-2024-72117/72117",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        }
    ],
    "conn-check": [
        {
            "advisory": "conn-check 1.0.18 ensures pyOpenSSL is always used instead of the ssl modules, see https://urllib3.readthedocs.org/en/latest/security.htmlpyopenssl.",
            "cve": "PVE-2021-25669",
            "id": "pyup.io-25669",
            "more_info_path": "/vulnerabilities/PVE-2021-25669/25669",
            "specs": [
                "<1.0.18"
            ],
            "v": "<1.0.18"
        }
    ],
    "connect-openapi-client": [
        {
            "advisory": "Connect-openapi-client 25.4 updates its dependency 'httpx' to version '0.23.0' to include a security fix.\r\nhttps://github.com/cloudblue/connect-python-openapi-client/commit/42595a51a66f1c4832d8f38fbcdca201a0bfded2\r\nhttps://github.com/advisories/==GHSA==-h8pj-cxx2-jfg2",
            "cve": "CVE-2021-41945",
            "id": "pyup.io-59114",
            "more_info_path": "/vulnerabilities/CVE-2021-41945/59114",
            "specs": [
                "<25.4"
            ],
            "v": "<25.4"
        }
    ],
    "connect-sdk-python2": [
        {
            "advisory": "Connect-sdk-python2 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-51387",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/51387",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        },
        {
            "advisory": "Connect-sdk-python2 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-51385",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/51385",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        },
        {
            "advisory": "Connect-sdk-python2 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-51384",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/51384",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        },
        {
            "advisory": "Connect-sdk-python2 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2018-20060",
            "id": "pyup.io-51359",
            "more_info_path": "/vulnerabilities/CVE-2018-20060/51359",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        },
        {
            "advisory": "Connect-sdk-python2 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-51386",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/51386",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        }
    ],
    "connect-sdk-python3": [
        {
            "advisory": "Connect-sdk-python3 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-51381",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/51381",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        },
        {
            "advisory": "Connect-sdk-python3 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-51382",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/51382",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        },
        {
            "advisory": "Connect-sdk-python3 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-51380",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/51380",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        },
        {
            "advisory": "Connect-sdk-python3 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2018-20060",
            "id": "pyup.io-51383",
            "more_info_path": "/vulnerabilities/CVE-2018-20060/51383",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        },
        {
            "advisory": "Connect-sdk-python3 3.33.0 updates the minimum 'requests' version from 2.20.0 to 2.25.0, as earlier versions depend on a vulnerable 'urllib3' version.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-51360",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/51360",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        }
    ],
    "consoleme": [
        {
            "advisory": "Consoleme 1.2.2 includes a fix for CVE-2022-27177: A Python format string issue leading to information disclosure and potentially remote code execution in ConsoleMe for all versions prior to 1.2.2.\r\nhttps://github.com/Netflix/security-bulletins/blob/master/advisories/nflx-2022-001.md",
            "cve": "CVE-2022-27177",
            "id": "pyup.io-47925",
            "more_info_path": "/vulnerabilities/CVE-2022-27177/47925",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Netflix ConsoleMe allows Command Injection.",
            "cve": "CVE-2024-5023",
            "id": "pyup.io-71910",
            "more_info_path": "/vulnerabilities/CVE-2024-5023/71910",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        }
    ],
    "container-service-extension": [
        {
            "advisory": "Container-service-extension 1.2.5 updates kubernetes packages and docker images for both Ubuntu and Photon OS templates to include a security fix.\r\nhttps://github.com/vmware/container-service-extension/commit/d4e6bf2d546a622d9fc20deb919b20a29264e071",
            "cve": "CVE-2018-1002105",
            "id": "pyup.io-36876",
            "more_info_path": "/vulnerabilities/CVE-2018-1002105/36876",
            "specs": [
                "<1.2.5"
            ],
            "v": "<1.2.5"
        },
        {
            "advisory": "Container-service-extension 1.2.7 updates docker images to include a fix for CVE-2019-5736.\r\nhttps://github.com/vmware/container-service-extension/commit/1f03f960871afe8774541747712d4a72f6378839",
            "cve": "CVE-2019-5736",
            "id": "pyup.io-37100",
            "more_info_path": "/vulnerabilities/CVE-2019-5736/37100",
            "specs": [
                "<1.2.7"
            ],
            "v": "<1.2.7"
        },
        {
            "advisory": "Container-service-extension 2.5.0b1  updates the hardcoded_password_string: false positives and test environment password strings marked not vulnerable.",
            "cve": "PVE-2021-37529",
            "id": "pyup.io-37529",
            "more_info_path": "/vulnerabilities/PVE-2021-37529/37529",
            "specs": [
                "<2.5.0b1"
            ],
            "v": "<2.5.0b1"
        }
    ],
    "contentful": [
        {
            "advisory": "Contentful 1.11.3 updates 'requests' version due to a vulnerability found in versions '2.19' and below.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36633",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36633",
            "specs": [
                "<1.11.3"
            ],
            "v": "<1.11.3"
        },
        {
            "advisory": "Contentful through 2020-05-21 for Python allows reflected XSS, as demonstrated by the api parameter to the-example-app.py.",
            "cve": "CVE-2020-13258",
            "id": "pyup.io-38314",
            "more_info_path": "/vulnerabilities/CVE-2020-13258/38314",
            "specs": [
                "<=1.12.3"
            ],
            "v": "<=1.12.3"
        }
    ],
    "contentful-management": [
        {
            "advisory": "Contentful-management 2.5.0 updates 'requests' version due to a vulnerability found in previous versions.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36599",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36599",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        }
    ],
    "contestms": [
        {
            "advisory": "contestms 1.2.0 fixes several security bugs around an unsafe use of isolate. These won't be backported to 1.1, so make sure you update.",
            "cve": "PVE-2021-34249",
            "id": "pyup.io-34249",
            "more_info_path": "/vulnerabilities/PVE-2021-34249/34249",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        },
        {
            "advisory": "Plaintext Password vulnerability in AddAdmin.py in cms-dev/cms v1.4.rc1, allows attackers to gain sensitive information via audit logs.",
            "cve": "CVE-2020-24804",
            "id": "pyup.io-70899",
            "more_info_path": "/vulnerabilities/CVE-2020-24804/70899",
            "specs": [
                "<=1.4.rc1"
            ],
            "v": "<=1.4.rc1"
        }
    ],
    "cookie-manager": [
        {
            "advisory": "Cookie-manager 1.0.3 updates its dependency 'bleach' to v3.1.2 to include a security fix.",
            "cve": "CVE-2020-6816",
            "id": "pyup.io-38106",
            "more_info_path": "/vulnerabilities/CVE-2020-6816/38106",
            "specs": [
                "<1.0.3"
            ],
            "v": "<1.0.3"
        },
        {
            "advisory": "Cookie-manager 1.1.0 updates its dependency Bleach to include a security fix.",
            "cve": "CVE-2020-6817",
            "id": "pyup.io-38153",
            "more_info_path": "/vulnerabilities/CVE-2020-6817/38153",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Cookie-manager 1.2.1 fixes a security vulnerability discovered and patched in a dependency. See Bleach 3.3.0  for further details.",
            "cve": "PVE-2021-40165",
            "id": "pyup.io-40165",
            "more_info_path": "/vulnerabilities/PVE-2021-40165/40165",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        }
    ],
    "cookiecutter": [
        {
            "advisory": "Cookiecutter 1.1.0 sets explicitly the list of allowed hosts for security reasons.",
            "cve": "PVE-2021-37672",
            "id": "pyup.io-37672",
            "more_info_path": "/vulnerabilities/PVE-2021-37672/37672",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Cookiecutter 2.1.1 includes a fix for CVE-2022-24065: Cookiecutter before 2.1.1 is vulnerable to Command Injection via hg argument injection. When calling the cookiecutter function from Python code with the checkout parameter, it is passed to the hg checkout command in a way that additional flags can be set. The additional flags can be used to perform a command injection.",
            "cve": "CVE-2022-24065",
            "id": "pyup.io-49337",
            "more_info_path": "/vulnerabilities/CVE-2022-24065/49337",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Cookiecutter, a command-line utility for creating projects, is susceptible to a vulnerability where credentials are insufficiently protected because of insecure retrieval of the gitlab_token. This issue concerns versions of Cookiecutter and poses a risk to the security of users' credentials.",
            "cve": "PVE-2024-99814",
            "id": "pyup.io-65970",
            "more_info_path": "/vulnerabilities/PVE-2024-99814/65970",
            "specs": [
                ">=0,<0.1"
            ],
            "v": ">=0,<0.1"
        }
    ],
    "coordination-network-toolkit": [
        {
            "advisory": "Coordination-network-toolkit 1.0.2 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-40624",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/40624",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "copier": [
        {
            "advisory": "Affected versions of the Copier package are vulnerable to Path Traversal due to unsafe exposure of filesystem access methods in the Jinja template context. The package exposes pathlib.Path objects, including _copier_conf.dst_path in the Jinja context, provide unconstrained read and write methods that can be used to access files outside the intended template directory structure.",
            "cve": "CVE-2025-55201",
            "id": "pyup.io-78847",
            "more_info_path": "/vulnerabilities/CVE-2025-55201/78847",
            "specs": [
                "<9.9.1"
            ],
            "v": "<9.9.1"
        },
        {
            "advisory": "Affected versions of the Copier package are vulnerable to Path Traversal due to insufficient validation of generated file paths in templates. The package allows templates to generate files with paths constructed using the pathjoin Jinja filter and _copier_conf.sep variable, which can create relative parent paths or absolute paths that escape the intended destination directory.",
            "cve": "CVE-2025-55214",
            "id": "pyup.io-78848",
            "more_info_path": "/vulnerabilities/CVE-2025-55214/78848",
            "specs": [
                ">=7.1.0,<9.9.1"
            ],
            "v": ">=7.1.0,<9.9.1"
        }
    ],
    "copy-spotter": [
        {
            "advisory": "Copy-spotter version 0.0.1 has upgraded its nltk dependency from 3.6.3 to 3.6.6 to address the security issue identified in CVE-2021-3842.",
            "cve": "CVE-2021-3842",
            "id": "pyup.io-68082",
            "more_info_path": "/vulnerabilities/CVE-2021-3842/68082",
            "specs": [
                "<0.0.1"
            ],
            "v": "<0.0.1"
        }
    ],
    "copyparty": [
        {
            "advisory": "Copyparty 0.11.31 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/9001/copyparty/commit/a5120d4f6fe4afe91eb0e091063de6b9ba9e81e1",
            "cve": "PVE-2023-59586",
            "id": "pyup.io-59586",
            "more_info_path": "/vulnerabilities/PVE-2023-59586/59586",
            "specs": [
                "<0.11.31"
            ],
            "v": "<0.11.31"
        },
        {
            "advisory": "Copyparty 0.12.3 fixes a bug where malicious POSTs through an nginx reverse-proxy could put the connection in a bad state, causing the next legit request to fail with bad headers.",
            "cve": "PVE-2023-53478",
            "id": "pyup.io-53478",
            "more_info_path": "/vulnerabilities/PVE-2023-53478/53478",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "Copyparty 1.0.10 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/9001/copyparty/commit/8399e95bda9a43c3c68c55c948bd4696a9374c27",
            "cve": "PVE-2023-59584",
            "id": "pyup.io-59584",
            "more_info_path": "/vulnerabilities/PVE-2023-59584/59584",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Copyparty 1.0.8 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/9001/copyparty/commit/bd5cfc2f1b90c278157fd5593735703763dbaf05",
            "cve": "PVE-2023-59585",
            "id": "pyup.io-59585",
            "more_info_path": "/vulnerabilities/PVE-2023-59585/59585",
            "specs": [
                "<1.0.8"
            ],
            "v": "<1.0.8"
        },
        {
            "advisory": "By handing someone a maliciously-named file, and then tricking them into dragging the file into Copyparty's Web-UI, an attacker could execute arbitrary JavaScript with the same privileges as that user. For example, this could give unintended read access to files owned by that user. The bug is triggered by the drag-drop action itself; it is not necessary to initiate the upload. The file must be empty (zero bytes).\r\n\r\nNote: As a general-purpose web server, it is intentionally possible to upload HTML files with arbitrary JavaScript in  sequences, and users/api.py persists attacker-supplied values through PATCH /api/users/{id}.",
            "cve": "CVE-2026-22033",
            "id": "pyup.io-84357",
            "more_info_path": "/vulnerabilities/CVE-2026-22033/84357",
            "specs": [
                "<=1.22.0"
            ],
            "v": "<=1.22.0"
        },
        {
            "advisory": "Label-studio throughout 1.7.1 are vulnerable to path traversal via Nginx alias. This allows unauthenticated attackers to read all files on /label_studio/core/",
            "cve": "PVE-2023-99958",
            "id": "pyup.io-60895",
            "more_info_path": "/vulnerabilities/PVE-2023-99958/60895",
            "specs": [
                "<=1.7.1"
            ],
            "v": "<=1.7.1"
        },
        {
            "advisory": "Label-studio 1.9.2.post0 includes a fix for CVE-2023-47117: In all current versions of Label Studio prior to 1.9.2post0, the application allows users to insecurely set filters for filtering tasks. An attacker can construct a filter chain to filter tasks based on sensitive fields for all user accounts on the platform by exploiting Django's Object Relational Mapper (ORM). Since the results of query can be manipulated by the ORM filter, an attacker can leak these sensitive fields character by character. In addition, Label Studio had a hard coded secret key that an attacker can use to forge a session token of any user by exploiting this ORM Leak vulnerability to leak account password hashes.\r\nhttps://github.com/HumanSignal/label-studio/security/advisories/GHSA-6hjj-gq77-j4qw",
            "cve": "CVE-2023-47117",
            "id": "pyup.io-62286",
            "more_info_path": "/vulnerabilities/CVE-2023-47117/62286",
            "specs": [
                "==1.9.2",
                "<=1.9.2"
            ],
            "v": "==1.9.2,<=1.9.2"
        },
        {
            "advisory": "Label Studio before 0.9.1 is susceptible to an arbitrary code execution vulnerability. This issue arises from YAML deserialization attacks facilitated by unsafe loading practices.",
            "cve": "PVE-2024-99780",
            "id": "pyup.io-66057",
            "more_info_path": "/vulnerabilities/PVE-2024-99780/66057",
            "specs": [
                ">=0,<0.9.1"
            ],
            "v": ">=0,<0.9.1"
        },
        {
            "advisory": "A Server Side Request Forgery (SSRF) in the Data Import module in Heartex - Label Studio Community Edition versions 1.5.0 and earlier allows an authenticated user to access arbitrary files on the system. Furthermore, self-registration is enabled by default in these versions of Label Studio enabling a remote attacker to create a new account and then exploit the SSRF. This issue is fixed in version 1.6.0.",
            "cve": "CVE-2022-36551",
            "id": "pyup.io-54502",
            "more_info_path": "/vulnerabilities/CVE-2022-36551/54502",
            "specs": [
                ">=0,<1.6.0"
            ],
            "v": ">=0,<1.6.0"
        }
    ],
    "label-studio-converter": [
        {
            "advisory": "Label-studio-converter 0.0.43 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-50652",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/50652",
            "specs": [
                "<0.0.43"
            ],
            "v": "<0.0.43"
        },
        {
            "advisory": "Label-studio-converter 0.0.43 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-25288",
            "id": "pyup.io-50647",
            "more_info_path": "/vulnerabilities/CVE-2021-25288/50647",
            "specs": [
                "<0.0.43"
            ],
            "v": "<0.0.43"
        },
        {
            "advisory": "Label-studio-converter 0.0.43 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-50645",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/50645",
            "specs": [
                "<0.0.43"
            ],
            "v": "<0.0.43"
        },
        {
            "advisory": "Label-studio-converter 0.0.43 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-50648",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/50648",
            "specs": [
                "<0.0.43"
            ],
            "v": "<0.0.43"
        },
        {
            "advisory": "Label-studio-converter 0.0.43 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-50650",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/50650",
            "specs": [
                "<0.0.43"
            ],
            "v": "<0.0.43"
        },
        {
            "advisory": "Label-studio-converter 0.0.43 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-50651",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/50651",
            "specs": [
                "<0.0.43"
            ],
            "v": "<0.0.43"
        },
        {
            "advisory": "Label-studio-converter 0.0.43 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-25287",
            "id": "pyup.io-50646",
            "more_info_path": "/vulnerabilities/CVE-2021-25287/50646",
            "specs": [
                "<0.0.43"
            ],
            "v": "<0.0.43"
        },
        {
            "advisory": "Label-studio-converter 0.0.43 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-50644",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/50644",
            "specs": [
                "<0.0.43"
            ],
            "v": "<0.0.43"
        },
        {
            "advisory": "Label-studio-converter 0.0.43 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-50649",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/50649",
            "specs": [
                "<0.0.43"
            ],
            "v": "<0.0.43"
        },
        {
            "advisory": "Label-studio-converter 0.0.45 updates its dependency 'pillow' to v8.3.1 to include security fixes.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-51798",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/51798",
            "specs": [
                "<0.0.45"
            ],
            "v": "<0.0.45"
        }
    ],
    "label-studio-ml": [
        {
            "advisory": "A vulnerability has been found in HumanSignal label-studio-ml-backend up to 9fb7f4aa186612806af2becfb621f6ed8d9fdbaf and classified as problematic. Affected by this vulnerability is the function load of the file label-studio-ml-backend/label_studio_ml/examples/yolo/utils/neural_nets.py of the component PT File Handler. The manipulation of the argument path leads to deserialization. An attack has to be approached locally. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.",
            "cve": "CVE-2025-5173",
            "id": "pyup.io-77708",
            "more_info_path": "/vulnerabilities/CVE-2025-5173/77708",
            "specs": [
                "<=1.0.9"
            ],
            "v": "<=1.0.9"
        }
    ],
    "label-studio-sdk": [
        {
            "advisory": "A path traversal vulnerability in Label Studio SDK versions before 1.0.10 allows unauthorized file access outside the intended directory structure. Label Studio versions before 1.16.0 specified SDK versions before 1.0.10 as dependencies, and the issue was confirmed in Label Studio version 1.13.2.dev0; therefore, Label Studio users should upgrade to 1.16.0 or newer to mitigate it. The flaw exists in the VOC, COCO and YOLO export functionalities. These functions invoke a download function on the label-studio-sdk python package, which fails to validate file paths when processing image references during task exports.",
            "cve": "CVE-2025-25295",
            "id": "pyup.io-76337",
            "more_info_path": "/vulnerabilities/CVE-2025-25295/76337",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        }
    ],
    "label-studio-sso": [
        {
            "advisory": "Affected versions of label-studio-sso are vulnerable to Cross-Site Request Forgery (CSRF). The `JWTSSOSessionAuthentication`  session authentication mechanism fails to validate CSRF tokens due to an improper exemption, leading to unauthorized actions being performed on behalf of authenticated users through malicious cross-site requests.",
            "cve": "PVE-2025-81353",
            "id": "pyup.io-81353",
            "more_info_path": "/vulnerabilities/PVE-2025-81353/81353",
            "specs": [
                "<6.0.3"
            ],
            "v": "<6.0.3"
        },
        {
            "advisory": "Affected versions of Label Studio are vulnerable to Improper Access Control. The SSO token API fails to restrict user creation to pre-registered accounts, leading to unauthorized users being able to create accounts and gain access to the application through valid SSO tokens without proper authorization.",
            "cve": "PVE-2025-81351",
            "id": "pyup.io-81351",
            "more_info_path": "/vulnerabilities/PVE-2025-81351/81351",
            "specs": [
                "<6.0.8"
            ],
            "v": "<6.0.8"
        }
    ],
    "labelme2datasets": [
        {
            "advisory": "Labelme2datasets version 0.0.3 has upgraded its dependency from setuptools at least version 58.0.4 to at least version 69.5.1. This update was made in response to the security vulnerability identified in CVE-2022-40897.",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-70977",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/70977",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Labelme2datasets version 0.0.3 has upgraded its dependency scikit-learn from at least version 0.24.2 to at least version 1.4.2. This update was made in response to the security vulnerability identified in CVE-2020-28975.",
            "cve": "CVE-2020-28975",
            "id": "pyup.io-70963",
            "more_info_path": "/vulnerabilities/CVE-2020-28975/70963",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        }
    ],
    "labgrid": [
        {
            "advisory": "Labgrid 23.0.2 fixes a race condition that previously occurred in the handling of USBSDMuxDevice/USBSDWireDevice paths. This issue arose particularly during USB resets or fast replugging events. It potentially led to the incorrect assignment of control and disk paths for the USBSDMuxDevice and USBSDWireDevice, impacting their accurate and reliable operation.\r\nhttps://github.com/labgrid-project/labgrid/compare/v23.0.1...v23.0.2#diff-bc256bde0e401738303653d85da6e6a1a1a937880d1eb6f9c423a9970eb349d2",
            "cve": "PVE-2024-64091",
            "id": "pyup.io-64091",
            "more_info_path": "/vulnerabilities/PVE-2024-64091/64091",
            "specs": [
                "<23.0.2"
            ],
            "v": "<23.0.2"
        }
    ],
    "ladok3": [
        {
            "advisory": "Ladok3 4.2 updates its dependency 'requests' to version '2.31.0' to include a fix for an Information Exposure vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/685f2fca6d38960a650060b1bdd13ca88f30b13f",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-60158",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/60158",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ladok3 4.2 updates its dependency 'cryptography' to version '38.0.4' to include a fix for a Buffer Overflow vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/685f2fca6d38960a650060b1bdd13ca88f30b13f",
            "cve": "CVE-2022-3786",
            "id": "pyup.io-60137",
            "more_info_path": "/vulnerabilities/CVE-2022-3786/60137",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ladok3 4.2 updates its dependency 'certifi' to version '2023.7.22' to include a fix for a vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/685f2fca6d38960a650060b1bdd13ca88f30b13f",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-60160",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/60160",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ladok3 4.2 updates its dependency 'certifi' to version '2023.7.22' to include a fix for a vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/685f2fca6d38960a650060b1bdd13ca88f30b13f",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60159",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60159",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ladok3 4.2 updates its dependency 'cryptography' to version '38.0.4' to include a fix for a Buffer Overflow vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/685f2fca6d38960a650060b1bdd13ca88f30b13f",
            "cve": "CVE-2022-3602",
            "id": "pyup.io-60157",
            "more_info_path": "/vulnerabilities/CVE-2022-3602/60157",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ladok3 4.2 updates its dependency 'pygments' to version '2.15.1' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/685f2fca6d38960a650060b1bdd13ca88f30b13f",
            "cve": "CVE-2022-40896",
            "id": "pyup.io-60161",
            "more_info_path": "/vulnerabilities/CVE-2022-40896/60161",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for an Expected Behavior Violation vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2023-23931",
            "id": "pyup.io-60566",
            "more_info_path": "/vulnerabilities/CVE-2023-23931/60566",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for a Type Confusion vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2023-0286",
            "id": "pyup.io-60561",
            "more_info_path": "/vulnerabilities/CVE-2023-0286/60561",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for a Timing Attack vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2022-4304",
            "id": "pyup.io-60562",
            "more_info_path": "/vulnerabilities/CVE-2022-4304/60562",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for a DoS vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2022-4450",
            "id": "pyup.io-60565",
            "more_info_path": "/vulnerabilities/CVE-2022-4450/60565",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for a DoS vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2023-0217",
            "id": "pyup.io-60559",
            "more_info_path": "/vulnerabilities/CVE-2023-0217/60559",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for a Use After Free vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2023-0215",
            "id": "pyup.io-60560",
            "more_info_path": "/vulnerabilities/CVE-2023-0215/60560",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for a DoS vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2022-4203",
            "id": "pyup.io-60564",
            "more_info_path": "/vulnerabilities/CVE-2022-4203/60564",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for a DoS vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2023-0401",
            "id": "pyup.io-60528",
            "more_info_path": "/vulnerabilities/CVE-2023-0401/60528",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for a DoS vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2022-3996",
            "id": "pyup.io-60567",
            "more_info_path": "/vulnerabilities/CVE-2022-3996/60567",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Ladok3 4.3 updates its dependency 'cryptography' to version '39.0.1' to include a fix for a DoS vulnerability.\r\nhttps://github.com/dbosk/ladok3/commit/33acab13bd48e3efdcf65493364eb06bf63decd6",
            "cve": "CVE-2023-0216",
            "id": "pyup.io-60563",
            "more_info_path": "/vulnerabilities/CVE-2023-0216/60563",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        }
    ],
    "ladon": [
        {
            "advisory": "Ladon since 0.6.1 (since ebef0aae48af78c159b6fce81bc6f5e7e0ddb059) is affected by: XML External Entity (XXE). The impact is: Information Disclosure, reading files and reaching internal network endpoints. The component is: SOAP request handlers. For instance: https://bitbucket.org/jakobsg/ladon/src/42944fc012a3a48214791c120ee5619434505067/src/ladon/interfaces/soap.py#lines-688. The attack vector is: Send a specially crafted SOAP call.",
            "cve": "CVE-2019-1010268",
            "id": "pyup.io-42258",
            "more_info_path": "/vulnerabilities/CVE-2019-1010268/42258",
            "specs": [
                ">=0.6.1,<=0.9.40"
            ],
            "v": ">=0.6.1,<=0.9.40"
        }
    ],
    "ladybug-comfort": [
        {
            "advisory": "Ladybug-comfort 0.16.18 updates its dependency 'wheel' to v0.38.1 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-52877",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/52877",
            "specs": [
                "<0.16.18"
            ],
            "v": "<0.16.18"
        }
    ],
    "lagmat": [
        {
            "advisory": "Lagmat 0.3.3 updates its dependency 'numpy' to v1.19.5 to include a security fix.",
            "cve": "CVE-2019-6446",
            "id": "pyup.io-43624",
            "more_info_path": "/vulnerabilities/CVE-2019-6446/43624",
            "specs": [
                "<0.3.3"
            ],
            "v": "<0.3.3"
        }
    ],
    "laim": [
        {
            "advisory": "Affected versions of laim are vulnerable to a race condition vulnerability. This flaw may allow SMTP sessions to be initiated with elevated privileges, potentially enabling privilege escalation.",
            "cve": "PVE-2025-75988",
            "id": "pyup.io-75988",
            "more_info_path": "/vulnerabilities/PVE-2025-75988/75988",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        }
    ],
    "lambda-tools": [
        {
            "advisory": "lambda-tools before 0.1.2 used an unsafe way to load untrusted lambda definitions via `yaml.load`.",
            "cve": "PVE-2021-35209",
            "id": "pyup.io-35209",
            "more_info_path": "/vulnerabilities/PVE-2021-35209/35209",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "lambdajson": [
        {
            "advisory": "lambdajson 0.1.5 includes a security fix. Using ast.literal_eval as eval.",
            "cve": "PVE-2021-25874",
            "id": "pyup.io-25874",
            "more_info_path": "/vulnerabilities/PVE-2021-25874/25874",
            "specs": [
                "<0.1.5"
            ],
            "v": "<0.1.5"
        }
    ],
    "lander": [
        {
            "advisory": "Lander 0.1.15 updates 'requests' to 2.20.0 for security reasons.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-38375",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/38375",
            "specs": [
                "<0.1.15"
            ],
            "v": "<0.1.15"
        }
    ],
    "lando": [
        {
            "advisory": "Lando 0.11.3 adds `cluster_api_settings .ssl_ca_cert` config flag to allow secure k8s connections. See .",
            "cve": "PVE-2021-37414",
            "id": "pyup.io-37414",
            "more_info_path": "/vulnerabilities/PVE-2021-37414/37414",
            "specs": [
                "<0.11.3"
            ],
            "v": "<0.11.3"
        }
    ],
    "langbot": [
        {
            "advisory": "Affected versions of LangBot are vulnerable to Path Traversal, leading to Arbitrary File Upload. The `/api/v1/files/documents` endpoint fails to validate and sanitize file path parameters, leading to the ability for authenticated attackers to write malicious files outside the intended upload directory to arbitrary system locations.",
            "cve": "CVE-2025-59835",
            "id": "pyup.io-81363",
            "more_info_path": "/vulnerabilities/CVE-2025-59835/81363",
            "specs": [
                "<4.3.4"
            ],
            "v": "<4.3.4"
        }
    ],
    "langchain": [
        {
            "advisory": "LangChain 0.0.142 includes a fix for CVE-2023-29374: The LLMMathChain chain allows prompt injection attacks that can execute arbitrary code via the Python exec method.",
            "cve": "CVE-2023-29374",
            "id": "pyup.io-54895",
            "more_info_path": "/vulnerabilities/CVE-2023-29374/54895",
            "specs": [
                "<0.0.142"
            ],
            "v": "<0.0.142"
        },
        {
            "advisory": "An issue in Harrison Chase langchain v.0.0.194 and before allows a remote attacker to execute arbitrary code via the from_math_prompt and from_colored_object_prompt functions.",
            "cve": "CVE-2023-38896",
            "id": "pyup.io-65036",
            "more_info_path": "/vulnerabilities/CVE-2023-38896/65036",
            "specs": [
                "<0.0.236"
            ],
            "v": "<0.0.236"
        },
        {
            "advisory": "Langchain 0.0.236 includes a fix for an Arbitrary Code Execution vulnerability. The vulnerability allows a remote attacker to execute arbitrary code via the PALChain parameter in the Python exec method.\r\nhttps://github.com/langchain-ai/langchain/commit/e294ba475a355feb95003ed8f1a2b99942509a9e",
            "cve": "CVE-2023-36188",
            "id": "pyup.io-59363",
            "more_info_path": "/vulnerabilities/CVE-2023-36188/59363",
            "specs": [
                "<0.0.236"
            ],
            "v": "<0.0.236"
        },
        {
            "advisory": "Langchain 0.0.236 includes a fix for an Arbitrary Code Execution vulnerability. In affected versions, the vulnerability allows an attacker to execute arbitrary code via the Python exec calls in the PALChain.\r\nhttps://github.com/langchain-ai/langchain/commit/8ba9835b925473655914f63822775679e03ea137\r\nhttps://github.com/langchain-ai/langchain/commit/e294ba475a355feb95003ed8f1a2b99942509a9e",
            "cve": "CVE-2023-36095",
            "id": "pyup.io-60218",
            "more_info_path": "/vulnerabilities/CVE-2023-36095/60218",
            "specs": [
                "<0.0.236"
            ],
            "v": "<0.0.236"
        },
        {
            "advisory": "Affected versions of Langchain allow an attacker to execute arbitrary code via the PALChain in the python exec method. The PALChain class requires unique security considerations so it was moved langchain-experimental package and removed from langchain on version 0.0.247. The issue was attempted to be resolved several times in langchain-experimental but the fixes were found incomplete. See CVE-2023-44467, CVE-2024-27444, and CVE-2024-38459.",
            "cve": "CVE-2023-36258",
            "id": "pyup.io-59294",
            "more_info_path": "/vulnerabilities/CVE-2023-36258/59294",
            "specs": [
                "<0.0.247"
            ],
            "v": "<0.0.247"
        },
        {
            "advisory": "Langchain 0.0.247 includes a fix for CVE-2023-34541: Arbitrary code execution in load_prompt.\r\nhttps://github.com/hwchase17/langchain/issues/4849\r\nhttps://github.com/langchain-ai/langchain/pull/8425",
            "cve": "CVE-2023-34541",
            "id": "pyup.io-59347",
            "more_info_path": "/vulnerabilities/CVE-2023-34541/59347",
            "specs": [
                "<0.0.247"
            ],
            "v": "<0.0.247"
        },
        {
            "advisory": "Langchain 0.0.247 includes a fix for CVE-2023-36189: SQL injection vulnerability allows a remote attacker to obtain sensitive information via the SQLDatabaseChain component.\r\nhttps://github.com/langchain-ai/langchain/issues/5923",
            "cve": "CVE-2023-36189",
            "id": "pyup.io-60080",
            "more_info_path": "/vulnerabilities/CVE-2023-36189/60080",
            "specs": [
                "<0.0.247"
            ],
            "v": "<0.0.247"
        },
        {
            "advisory": "Langchain 0.0.306 includes a fix for a code injection vulnerability.\r\nhttps://github.com/langchain-ai/langchain/pull/11233",
            "cve": "PVE-2023-61536",
            "id": "pyup.io-61536",
            "more_info_path": "/vulnerabilities/PVE-2023-61536/61536",
            "specs": [
                "<0.0.306"
            ],
            "v": "<0.0.306"
        },
        {
            "advisory": "An issue in langchain v.0.0.171 allows a remote attacker to execute arbitrary code via the via the a json file to the load_prompt parameter. This is related to __subclasses__ or a template.",
            "cve": "CVE-2023-36281",
            "id": "pyup.io-71616",
            "more_info_path": "/vulnerabilities/CVE-2023-36281/71616",
            "specs": [
                "<0.0.312"
            ],
            "v": "<0.0.312"
        },
        {
            "advisory": "LangChain before 0.0.317 allows SSRF via document_loaders/recursive_url_loader.py because crawling can proceed from an external server to an internal server.",
            "cve": "CVE-2023-46229",
            "id": "pyup.io-65233",
            "more_info_path": "/vulnerabilities/CVE-2023-46229/65233",
            "specs": [
                "<0.0.317"
            ],
            "v": "<0.0.317"
        },
        {
            "advisory": "Affected versions of langchain allow a remote attacker to execute arbitrary code via a crafted script to the PythonAstREPLTool._run component.\r\n#NOTE: The data we include in this advisory differs from the publicly available on nvd.nist.gov. The advisory posted by the NVD indicated that versions up to and including 0.0.232 were affected. However, research by Safety CLI Cybersecurity confirms that the vulnerability remains unaddressed in all versions up to 0.0.325.",
            "cve": "CVE-2023-39659",
            "id": "pyup.io-60433",
            "more_info_path": "/vulnerabilities/CVE-2023-39659/60433",
            "specs": [
                "<0.0.325"
            ],
            "v": "<0.0.325"
        },
        {
            "advisory": "Langchain 0.0.329 includes a fix for CVE-2023-32786: Server-Side Request Forgery vulnerability.\r\nhttps://github.com/advisories/GHSA-6h8p-4hx9-w66c",
            "cve": "CVE-2023-32786",
            "id": "pyup.io-62143",
            "more_info_path": "/vulnerabilities/CVE-2023-32786/62143",
            "specs": [
                "<0.0.329"
            ],
            "v": "<0.0.329"
        },
        {
            "advisory": "Affected versions of the langchain package are vulnerable to Path Traversal due to improper limitation of a pathname to a restricted directory in the langchain.storage.file_system.LocalFileStore component. The langchain.storage.file_system.LocalFileStore.mset and mget methods derive filesystem paths from a user-supplied key without ensuring the resolved path remains within the configured root, permitting absolute paths to escape the intended directory.",
            "cve": "CVE-2024-3571",
            "id": "pyup.io-71615",
            "more_info_path": "/vulnerabilities/CVE-2024-3571/71615",
            "specs": [
                "<0.0.353"
            ],
            "v": "<0.0.353"
        },
        {
            "advisory": "Langchain version 0.1.14 addresses CVE-2024-21503, updating the \"black\" python linter from version 24.2.0 to 24.3.0. This update remedies a Regex-related denial of service vulnerability present in the earlier version.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-70875",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/70875",
            "specs": [
                "<0.1.14"
            ],
            "v": "<0.1.14"
        },
        {
            "advisory": "langchain_experimental (aka LangChain Experimental) in LangChain before 0.1.8 allows an attacker to bypass the CVE-2023-44467 fix and execute arbitrary code via the __import__, __subclasses__, __builtins__, __globals__, __getattribute__, __bases__, __mro__, or __base__ attribute in Python code. These are not prohibited by pal_chain/base.py. See CVE-2024-27444.",
            "cve": "CVE-2024-27444",
            "id": "pyup.io-65703",
            "more_info_path": "/vulnerabilities/CVE-2024-27444/65703",
            "specs": [
                "<0.1.8"
            ],
            "v": "<0.1.8"
        },
        {
            "advisory": "langchain_experimental 0.0.14 allows an attacker to bypass the CVE-2023-36258 fix and execute arbitrary code via the PALChain in the python exec method.",
            "cve": "CVE-2023-44467",
            "id": "pyup.io-71617",
            "more_info_path": "/vulnerabilities/CVE-2023-44467/71617",
            "specs": [
                "<=0.0.14"
            ],
            "v": "<=0.0.14"
        },
        {
            "advisory": "An issue in LangChain v.0.0.231 allows a remote attacker to execute arbitrary code via the prompt parameter.",
            "cve": "CVE-2023-38860",
            "id": "pyup.io-65035",
            "more_info_path": "/vulnerabilities/CVE-2023-38860/65035",
            "specs": [
                "<=0.0.231"
            ],
            "v": "<=0.0.231"
        },
        {
            "advisory": "An issue in LanChain-ai Langchain v.0.0.245 allows a remote attacker to execute arbitrary code via the evaluate function in the numexpr library.",
            "cve": "CVE-2023-39631",
            "id": "pyup.io-71618",
            "more_info_path": "/vulnerabilities/CVE-2023-39631/71618",
            "specs": [
                "<=0.0.245"
            ],
            "v": "<=0.0.245"
        },
        {
            "advisory": "An issue in langchain v.0.0.199 allows an attacker to execute arbitrary code via the PALChain in the python exec method.",
            "cve": "PVE-2024-99901",
            "id": "pyup.io-64703",
            "more_info_path": "/vulnerabilities/PVE-2024-99901/64703",
            "specs": [
                "==0.0.199"
            ],
            "v": "==0.0.199"
        },
        {
            "advisory": "SQL injection vulnerability in langchain v.0.0.64 allows a remote attacker to obtain sensitive information via the SQLDatabaseChain component.",
            "cve": "PVE-2024-99902",
            "id": "pyup.io-64702",
            "more_info_path": "/vulnerabilities/PVE-2024-99902/64702",
            "specs": [
                "==0.0.64"
            ],
            "v": "==0.0.64"
        },
        {
            "advisory": "An issue in langchain v.0.0.64 allows a remote attacker to execute arbitrary code via the PALChain parameter in the Python exec method.",
            "cve": "PVE-2024-99903",
            "id": "pyup.io-64701",
            "more_info_path": "/vulnerabilities/PVE-2024-99903/64701",
            "specs": [
                "==0.0.64"
            ],
            "v": "==0.0.64"
        },
        {
            "advisory": "Langchains 0.1.14 updates its dependency 'langchain-core' in poetry.lock to version 0.1.37 to include a fix for a XML Entity Expansion vulnerability.",
            "cve": "CVE-2024-1455",
            "id": "pyup.io-66962",
            "more_info_path": "/vulnerabilities/CVE-2024-1455/66962",
            "specs": [
                ">=0,<0.1.14"
            ],
            "v": ">=0,<0.1.14"
        },
        {
            "advisory": "Affected versions of the `Langchain` package are vulnerable to Remote Code Execution due to improper handling of user input. The `JiraAPIWrapper` component fails to adequately sanitize input before passing it to system-level commands, allowing for command injection. An attacker can exploit this by providing specially crafted input to execute arbitrary code with the permissions of the application process.",
            "cve": "CVE-2023-34540",
            "id": "pyup.io-59322",
            "more_info_path": "/vulnerabilities/CVE-2023-34540/59322",
            "specs": [
                ">=0.0.143,<0.0.225"
            ],
            "v": ">=0.0.143,<0.0.225"
        },
        {
            "advisory": "Affected versions of the LangChain package are vulnerable to Path Traversal due to improper sanitization of the path parameter in the `load_chain` call. The `load_chain` function allows user input to manipulate the final part of the path, enabling traversal outside the intended directory scope. An attacker can exploit this by crafting a path that accesses sensitive files, potentially leading to Information Disclosure of API keys or even Remote Code Execution if malicious scripts are executed.",
            "cve": "CVE-2024-28088",
            "id": "pyup.io-66051",
            "more_info_path": "/vulnerabilities/CVE-2024-28088/66051",
            "specs": [
                ">=0.0.75,<=0.0.340"
            ],
            "v": ">=0.0.75,<=0.0.340"
        }
    ],
    "langchain-chatchat": [
        {
            "advisory": "Affected versions of the langchain-chatchat package are vulnerable to Path Traversal due to the _get_file_path helper constructing file system paths directly from a user-controlled, base64-encoded file_id without validating or constraining the resulting path. The retrieve_file_content handler for the GET /v1/files/{file_id}/content endpoint decodes the file_id, passes the resulting path to _get_file_path, and then serves the file via FileResponse using os.path.join without any checks for segments or restrictions to a dedicated storage directory, allowing paths that resolve outside the intended assistant's storage tree.",
            "cve": "CVE-2025-6854",
            "id": "pyup.io-82207",
            "more_info_path": "/vulnerabilities/CVE-2025-6854/82207",
            "specs": [
                "<=0.3.1"
            ],
            "v": "<=0.3.1"
        },
        {
            "advisory": "Affected versions of the langchain-chatchat package are vulnerable to Path Traversal due to insufficient sanitization of user-supplied filenames in the /knowledge_base/upload_temp_docs endpoint. The upload_temp_docs handler calls _parse_files_in_thread, which invokes parse_file in libs/chatchat-server/chatchat/server/chat/file_chat.py to build a destination path with os.path.join(dir, file.filename) and write it to disk, allowing .. sequences in UploadFile.filename to escape the intended directory.",
            "cve": "CVE-2025-6853",
            "id": "pyup.io-81131",
            "more_info_path": "/vulnerabilities/CVE-2025-6853/81131",
            "specs": [
                "<=0.3.1.3"
            ],
            "v": "<=0.3.1.3"
        }
    ],
    "langchain-cloudflare": [
        {
            "advisory": "Affected versions of the langchain-cloudflare package are vulnerable to SQL Injection due to improper sanitization of user-controlled metadata in D1 database operations. The d1_upsert_texts and ad1_upsert_texts methods construct SQL queries using string formatting without escaping special characters, allowing nested metadata fields containing single quotes to break out of SQL string literals.",
            "cve": "PVE-2025-82732",
            "id": "pyup.io-82732",
            "more_info_path": "/vulnerabilities/PVE-2025-82732/82732",
            "specs": [
                "<0.1.11"
            ],
            "v": "<0.1.11"
        }
    ],
    "langchain-community": [
        {
            "advisory": "Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) due to a lack of proper URL validation in the RequestsToolkit component. The RequestsToolkit fails to enforce restrictions on target URLs, allowing requests to both remote internet addresses and local network addresses, leading to potential port scanning, access to local services, retrieval of cloud instance metadata, and interaction with internal network resources.",
            "cve": "CVE-2025-2828",
            "id": "pyup.io-77900",
            "more_info_path": "/vulnerabilities/CVE-2025-2828/77900",
            "specs": [
                "<0.0.28"
            ],
            "v": "<0.0.28"
        },
        {
            "advisory": "Affected versions of the langchain package are vulnerable to Deserialization of Untrusted Data due to unsafe pickle deserialization in the FAISS vector store implementation. The FAISS.deserialize_from_bytes function directly deserializes pickle data without proper validation, allowing arbitrary Python objects to be reconstructed and executed during the deserialization process.",
            "cve": "CVE-2024-5998",
            "id": "pyup.io-73298",
            "more_info_path": "/vulnerabilities/CVE-2024-5998/73298",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        },
        {
            "advisory": "Affected versions of Langchain-community are vulnerable to Denial of service in SitemapLoader Document Loader. The parse_sitemap method, responsible for parsing sitemaps and extracting URLs, lacks a mechanism to prevent infinite recursion when a sitemap URL refers to the current sitemap itself. This oversight allows for the possibility of an infinite loop, leading to a crash by exceeding the maximum recursion depth in Python. This vulnerability can be exploited to occupy server socket/port resources and crash the Python process, impacting the availability of services relying on this functionality.",
            "cve": "CVE-2024-2965",
            "id": "pyup.io-71614",
            "more_info_path": "/vulnerabilities/CVE-2024-2965/71614",
            "specs": [
                "<0.2.5"
            ],
            "v": "<0.2.5"
        },
        {
            "advisory": "A Server-Side Request Forgery (SSRF) vulnerability exists in the Web Research Retriever component of affected versions of langchain-ai/langchain. The vulnerability arises because the Web Research Retriever does not restrict requests to remote internet addresses, allowing it to reach local addresses. This flaw enables attackers to execute port scans, access local services, and in some scenarios, read instance metadata from cloud environments. The vulnerability is particularly concerning as it can be exploited to abuse the Web Explorer server as a proxy for web attacks on third parties and interact with servers in the local network, including reading their response data. This could potentially lead to arbitrary code execution, depending on the nature of the local services. The vulnerability is limited to GET requests, as POST requests are not possible, but the impact on confidentiality, integrity, and availability is significant due to the potential for stolen credentials and state-changing interactions with internal APIs.",
            "cve": "CVE-2024-3095",
            "id": "pyup.io-71924",
            "more_info_path": "/vulnerabilities/CVE-2024-3095/71924",
            "specs": [
                "<0.2.9"
            ],
            "v": "<0.2.9"
        },
        {
            "advisory": "Affected versions of the langchain-community package are vulnerable to XML External Entity (XXE) Injection due to the use of `etree.iterparse` without disabling external entity resolution. ([GitHub][1]) The `langchain_community.document_loaders.evernote` module\u2019s `EverNoteLoader` parses ENEX input with `etree.iterparse()` without a hardened XML parser, enabling expansion of external entities and unintended access to local resources.",
            "cve": "CVE-2025-6984",
            "id": "pyup.io-79462",
            "more_info_path": "/vulnerabilities/CVE-2025-6984/79462",
            "specs": [
                "<0.3.27"
            ],
            "v": "<0.3.27"
        },
        {
            "advisory": "Affected versions of langchain-ai/langchain are vulnerable to SQL injection through GraphCypherQAChain class. This vulnerability allows attackers to manipulate database queries via malicious input in prompts, potentially leading to unauthorized data access, manipulation, and cross-tenant data breaches. The vulnerability exists in the query processing logic of GraphCypherQAChain where user input is not properly sanitized. Successfully exploiting this requires access to the API endpoint.",
            "cve": "CVE-2024-8309",
            "id": "pyup.io-73959",
            "more_info_path": "/vulnerabilities/CVE-2024-8309/73959",
            "specs": [
                ">=0.2.0,<0.2.19"
            ],
            "v": ">=0.2.0,<0.2.19"
        }
    ],
    "langchain-core": [
        {
            "advisory": "Affected versions of the LangChain package are vulnerable to Path Traversal due to improper sanitization of the path parameter in the `load_chain` call. The `load_chain` function allows user input to manipulate the final part of the path, enabling traversal outside the intended directory scope. An attacker can exploit this by crafting a path that accesses sensitive files, potentially leading to Information Disclosure of API keys or even Remote Code Execution if malicious scripts are executed.",
            "cve": "CVE-2024-28088",
            "id": "pyup.io-71609",
            "more_info_path": "/vulnerabilities/CVE-2024-28088/71609",
            "specs": [
                "<0.1.30"
            ],
            "v": "<0.1.30"
        },
        {
            "advisory": "Affected versions of the langchain package are vulnerable to XML External Entity (XXE) Injection due to unrestricted XML entity expansion in the langchain_core.output_parsers.xml.XMLOutputParser component. The XMLOutputParser.parse, _transform, and _atransform implementations rely on xml.etree.ElementTree.fromstring and XMLPullParser without prohibiting entity expansion, allowing recursive entity references (Billion Laughs) to be processed.",
            "cve": "CVE-2024-1455",
            "id": "pyup.io-71610",
            "more_info_path": "/vulnerabilities/CVE-2024-1455/71610",
            "specs": [
                "<0.1.35"
            ],
            "v": "<0.1.35"
        },
        {
            "advisory": "Affected versions of the `langchain` package are vulnerable to Server-Side Request Forgery (SSRF) due to inadequate handling of external URLs in `recursive_url_loader.py`. The vulnerability exists because the preventive measure of setting the `prevent_outside` parameter to True is bypassed, allowing the crawler to interact with unauthorized servers. An attacker controlling an external server can exploit this by embedding links that appear to be internal, such as `https://example.completely.different/my_file.html`, leading the crawler to fetch and process potentially malicious files.",
            "cve": "CVE-2024-0243",
            "id": "pyup.io-71611",
            "more_info_path": "/vulnerabilities/CVE-2024-0243/71611",
            "specs": [
                ">=0.0.13rc1,<0.1.7"
            ],
            "v": ">=0.0.13rc1,<0.1.7"
        },
        {
            "advisory": "A vulnerability in langchain-core versions >=0.1.17,<0.1.53, >=0.2.0,<0.2.43, and >=0.3.0,<0.3.15 allows unauthorized users to read arbitrary files from the host file system. The issue arises from the ability to create langchaincore.prompts.ImagePromptTemplate's (and by extension langchaincore.prompts.ChatPromptTemplate's) with input variables that can read any user-specified path from the server file system. If the outputs of these prompt templates are exposed to the user, either directly or through downstream model outputs, it can lead to the exposure of sensitive information.",
            "cve": "CVE-2024-10940",
            "id": "pyup.io-76276",
            "more_info_path": "/vulnerabilities/CVE-2024-10940/76276",
            "specs": [
                ">=0.1.17,<0.1.53",
                ">=0.2.0rc1,<0.2.43",
                ">=0.3.0.dev0,<0.3.15"
            ],
            "v": ">=0.1.17,<0.1.53,>=0.2.0rc1,<0.2.43,>=0.3.0.dev0,<0.3.15"
        },
        {
            "advisory": "Affected versions of the langchain-core package are vulnerable to Deserialization of Untrusted Data due to improper escaping of user-controlled dictionaries containing the internal 'lc' serialization marker. The langchain_core.load.dumps() and langchain_core.load.dumpd() functions serialize free-form dictionaries without escaping 'lc' keys, so subsequent deserialization via langchain_core.load.load() or langchain_core.load.loads() can treat attacker-supplied structures as legitimate LangChain Serializable manifests (including \"type\": \"secret\" objects) instead of plain data.",
            "cve": "CVE-2025-68664",
            "id": "pyup.io-83246",
            "more_info_path": "/vulnerabilities/CVE-2025-68664/83246",
            "specs": [
                ">=1.0.0,<1.2.5",
                "<0.3.81"
            ],
            "v": ">=1.0.0,<1.2.5,<0.3.81"
        },
        {
            "advisory": "Affected versions of the langchain-core package are vulnerable to Template Injection due to improper neutralization of attribute access and indexing expressions in prompt templates constructed from untrusted input. The ChatPromptTemplate class and related prompt template implementations for f-string, Mustache, and Jinja2 formats allow attacker-controlled template strings such as {msg.class.name} or {{question.parse_raw}} to traverse Python object attributes and dictionary-style lookups, exposing internal properties like class metadata or globals when complex objects such as HumanMessage or other message objects are passed into the template context.",
            "cve": "CVE-2025-65106",
            "id": "pyup.io-81791",
            "more_info_path": "/vulnerabilities/CVE-2025-65106/81791",
            "specs": [
                ">=1.0.0,<=1.0.6",
                "<=0.3.79"
            ],
            "v": ">=1.0.0,<=1.0.6,<=0.3.79"
        }
    ],
    "langchain-experimental": [
        {
            "advisory": "Langchain_experimental allows an attacker to bypass the CVE-2023-36258 fix and execute arbitrary code via the PALChain in the python exec method.",
            "cve": "CVE-2023-44467",
            "id": "pyup.io-61692",
            "more_info_path": "/vulnerabilities/CVE-2023-44467/61692",
            "specs": [
                "<0.0.24"
            ],
            "v": "<0.0.24"
        },
        {
            "advisory": "Langchain-experimental (aka LangChain Experimental) allows attackers to bypass the CVE-2023-44467 fix and execute arbitrary code via the __import__, __subclasses__, __builtins__, __globals__, __getattribute__, __bases__, __mro__, or __base__ attribute in Python code. These are not prohibited by pal_chain/base.py.",
            "cve": "CVE-2024-27444",
            "id": "pyup.io-68479",
            "more_info_path": "/vulnerabilities/CVE-2024-27444/68479",
            "specs": [
                "<0.0.52"
            ],
            "v": "<0.0.52"
        },
        {
            "advisory": "Langchain-experimental (aka LangChain Experimental) before 0.0.61 provides Python REPL access without an opt-in step. \r\nNOTE: This issue exists because of an incomplete fix for CVE-2024-27444.",
            "cve": "CVE-2024-38459",
            "id": "pyup.io-71652",
            "more_info_path": "/vulnerabilities/CVE-2024-38459/71652",
            "specs": [
                "<0.0.61"
            ],
            "v": "<0.0.61"
        },
        {
            "advisory": "Affected versions of langchain-experimental are vulnerable to Arbitrary Code Execution. When retrieving values from the database, the code will attempt to call 'eval' on all values. An attacker can exploit this vulnerability and execute arbitrary python code if they can control the input prompt and the server is configured with VectorSQLDatabaseChain.",
            "cve": "CVE-2024-21513",
            "id": "pyup.io-72182",
            "more_info_path": "/vulnerabilities/CVE-2024-21513/72182",
            "specs": [
                ">=0.0.15,<0.0.21"
            ],
            "v": ">=0.0.15,<0.0.21"
        },
        {
            "advisory": "A vulnerability exists in langchain_experimental affected versions where the LLMSymbolicMathChain was introduced because it passes untrusted input directly to sympy.sympify, which uses eval() internally. This flaw allows attackers to execute arbitrary code via crafted mathematical expressions.",
            "cve": "CVE-2024-46946",
            "id": "pyup.io-73280",
            "more_info_path": "/vulnerabilities/CVE-2024-46946/73280",
            "specs": [
                ">=0.1.17"
            ],
            "v": ">=0.1.17"
        }
    ],
    "langchain-text-splitters": [
        {
            "advisory": "Affected versions of the langchain-text-splitters package are vulnerable to XML External Entity (XXE) Injection due to insecure XML parser configurations and the presence of the xslt_path parameter in the HTMLSectionSplitter component, leading to entity expansion and external resource loading. The HTMLSectionSplitter\u2019s parser instantiation failed to disable network access (no_network=True), entity resolution (resolve_entities=False), and DTD processing (load_dtd=False), and allowed users to supply arbitrary XSLT files via the xslt_path parameter.",
            "cve": "PVE-2025-78354",
            "id": "pyup.io-78354",
            "more_info_path": "/vulnerabilities/PVE-2025-78354/78354",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "Affected versions of the langchain-text-splitters package are vulnerable to XML External Entity (XXE) Injection due to unsafe XSLT parsing in the HTMLSectionSplitter class. HTMLSectionSplitter accepts attacker-controlled XSLT (formerly via the xslt_path parameter / custom stylesheet support) and invokes lxml.etree.parse() and lxml.etree.XSLT() without disabling external entity resolution or enforcing XSLTAccessControl, allowing XXE processing and document() URI reads.",
            "cve": "CVE-2025-6985",
            "id": "pyup.io-80466",
            "more_info_path": "/vulnerabilities/CVE-2025-6985/80466",
            "specs": [
                "<0.3.9"
            ],
            "v": "<0.3.9"
        }
    ],
    "langflow": [
        {
            "advisory": "Langflow 1.0.0a37 removes the unsecure and unused `/custom_component/reload` endpoint. This endpoint previously read the directory in the file system without validating the input parameter, posing a potential security risk. Since it is not used by the frontend, the decision was made to eliminate it entirely rather than implement path validation. This removal enhances the security of the application by eliminating an unnecessary vulnerability.",
            "cve": "PVE-2024-71218",
            "id": "pyup.io-71218",
            "more_info_path": "/vulnerabilities/PVE-2024-71218/71218",
            "specs": [
                "<1.0.0a37"
            ],
            "v": "<1.0.0a37"
        },
        {
            "advisory": "Affected versions of Langflow allow remote code execution if untrusted users are able to reach the \"POST /api/v1/custom_component\" endpoint and provide a Python script.",
            "cve": "CVE-2024-37014",
            "id": "pyup.io-71781",
            "more_info_path": "/vulnerabilities/CVE-2024-37014/71781",
            "specs": [
                "<1.0.15"
            ],
            "v": "<1.0.15"
        },
        {
            "advisory": "Affected versions of Langflow are vulnerable to Missing Authorization (CWE-862). The attack can be carried out by sending file upload requests to the /api/v1/files/upload endpoint with a flow_id parameter corresponding to another user's flow. The vulnerable function is upload_file in files.py, which lacked proper authorization checks to verify flow ownership. To exploit this vulnerability, an attacker needs valid authentication credentials but does not require elevated privileges. Users should update to the version of Langflow, where this issue is fixed by adding authorization checks to ensure that only flow owners can upload files to their flows.",
            "cve": "PVE-2024-73674",
            "id": "pyup.io-73674",
            "more_info_path": "/vulnerabilities/PVE-2024-73674/73674",
            "specs": [
                "<1.0.19"
            ],
            "v": "<1.0.19"
        },
        {
            "advisory": "Langflow 1.0.6 updates its langchain-experimental dependency to version 0.0.61 or later to address a security vulnerability identified as CVE-2024-38459.",
            "cve": "CVE-2024-38459",
            "id": "pyup.io-72002",
            "more_info_path": "/vulnerabilities/CVE-2024-38459/72002",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Langflow versions affected versions are susceptible to code injection in the /api/v1/validate/code endpoint. A remote and unauthenticated attacker can send crafted HTTP requests to execute arbitrary code.",
            "cve": "CVE-2025-3248",
            "id": "pyup.io-76580",
            "more_info_path": "/vulnerabilities/CVE-2025-3248/76580",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Affected versions of the langflow and langflow-base packages are vulnerable to Improper Authentication due to missing FastAPI authentication dependencies on sensitive monitoring routes. The src/backend/base/langflow/api/v1/monitor.py module defines the /api/v1/monitor/messages (get_messages), /api/v1/monitor/transactions (get_transactions), and /api/v1/monitor/messages/session/{session_id} (delete_messages_session) endpoints without dependencies=[Depends(get_current_active_user)], leaving these handlers reachable without any user identity or authorization checks.",
            "cve": "CVE-2026-21445",
            "id": "pyup.io-83855",
            "more_info_path": "/vulnerabilities/CVE-2026-21445/83855",
            "specs": [
                "<1.7.1"
            ],
            "v": "<1.7.1"
        },
        {
            "advisory": "Affected versions of the langflow package are vulnerable to Server-Side Request Forgery (SSRF) due to accepting a user-supplied URL in the API Request component without blocking localhost, private network ranges, or cloud metadata IPs. The API Request component in lfx/components/data/api_request.py only normalizes the URL via _normalize_url() and checks it with validators.url(), then issues the request with httpx.AsyncClient.request() and returns the response body in metadata[\"result\"], reachable through the flow execution endpoints /api/v1/run/{flow_id_or_name} and /api/v1/run/advanced/{flow_id_or_name}.",
            "cve": "CVE-2025-68477",
            "id": "pyup.io-83156",
            "more_info_path": "/vulnerabilities/CVE-2025-68477/83156",
            "specs": [
                "<1.7.1"
            ],
            "v": "<1.7.1"
        },
        {
            "advisory": "Affected versions of the langflow package are vulnerable to Arbitrary File Overwrite due to accepting a user-supplied filesystem path without validation. The /api/v1/flows/ create_flow handler invokes _verify_fs_path() and _save_flow_to_fs() in src/backend/base/langflow/api/v1/flows.py, which uses the request body\u2019s fs_path to create the target file and then writes Flow JSON to it with async_open(flow.fs_path, \"w\") without path normalization or allowed-directory enforcement.",
            "cve": "CVE-2025-68478",
            "id": "pyup.io-83157",
            "more_info_path": "/vulnerabilities/CVE-2025-68478/83157",
            "specs": [
                "<1.7.1"
            ],
            "v": "<1.7.1"
        },
        {
            "advisory": "Affected versions of the langflow package are vulnerable to Remote Code Execution due to insecure handling by the PythonCodeTool component. The PythonCodeTool component processes untrusted input in such a way that arbitrary Python code can be executed without proper sanitization or isolation. An attacker can exploit this via crafting inputs that cause the PythonCodeTool component to run arbitrary code, leading to full compromise of the host environment. Note: This vulnerability applies to langflow versions up to and including 1.0.12.",
            "cve": "CVE-2024-42835",
            "id": "pyup.io-78785",
            "more_info_path": "/vulnerabilities/CVE-2024-42835/78785",
            "specs": [
                "<=1.0.12"
            ],
            "v": "<=1.0.12"
        },
        {
            "advisory": "Affected versions of the langflow package are vulnerable to Remote Code Execution due to the execution of arbitrary component code on the local host without sandboxing. The core execution logic in the langflow package allows components originating from user-provided code to run directly on the local machine rather than within an isolated or sandboxed environment. An attacker who supplies a malicious component or payload can trigger execution of arbitrary code locally, potentially leading to full system compromise of confidentiality, integrity, and availability.",
            "cve": "CVE-2024-48061",
            "id": "pyup.io-78811",
            "more_info_path": "/vulnerabilities/CVE-2024-48061/78811",
            "specs": [
                "<=1.0.18"
            ],
            "v": "<=1.0.18"
        },
        {
            "advisory": "Affected versions of the langflow package are vulnerable to Regular Expression Denial of Service due to inefficient handling of user-supplied input that triggers complex regex processing. The HTTP POST Request Handler in the file `src/backend/base/langflow/interface/utils.py` accepts a `remaining_text` argument whose manipulation causes unbounded regex backtracking and excessive processing. An attacker can send crafted payloads to the HTTP POST endpoint using the `remaining_text` parameter, causing the regex evaluation to consume excessive CPU and resources, resulting in a denial of service of the langflow service.",
            "cve": "CVE-2024-9277",
            "id": "pyup.io-78763",
            "more_info_path": "/vulnerabilities/CVE-2024-9277/78763",
            "specs": [
                "<=1.0.18"
            ],
            "v": "<=1.0.18"
        },
        {
            "advisory": "Affected versions of the Langflow package are vulnerable to Privilege Escalation due to improper access controls on the internal CLI command langflow superuser. The Docker image includes a CLI binary at /app/.venv/bin/langflow that exposes the langflow superuser command, which creates new administrative users without verifying existing permissions or whether a superuser already exists, and can be invoked by authenticated users who achieve code execution through endpoints like /api/v1/validate/code.",
            "cve": "CVE-2025-57760",
            "id": "pyup.io-79074",
            "more_info_path": "/vulnerabilities/CVE-2025-57760/79074",
            "specs": [
                "<=1.5.0"
            ],
            "v": "<=1.5.0"
        }
    ],
    "langflow-base": [
        {
            "advisory": "Langflow versions affected versions are susceptible to code injection in the /api/v1/validate/code endpoint. A remote and unauthenticated attacker can send crafted HTTP requests to execute arbitrary code.",
            "cve": "CVE-2025-3248",
            "id": "pyup.io-80979",
            "more_info_path": "/vulnerabilities/CVE-2025-3248/80979",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Affected versions of the langflow and langflow-base packages are vulnerable to Improper Authentication due to missing FastAPI authentication dependencies on sensitive monitoring routes. The src/backend/base/langflow/api/v1/monitor.py module defines the /api/v1/monitor/messages (get_messages), /api/v1/monitor/transactions (get_transactions), and /api/v1/monitor/messages/session/{session_id} (delete_messages_session) endpoints without dependencies=[Depends(get_current_active_user)], leaving these handlers reachable without any user identity or authorization checks.",
            "cve": "CVE-2026-21445",
            "id": "pyup.io-83856",
            "more_info_path": "/vulnerabilities/CVE-2026-21445/83856",
            "specs": [
                "<1.7.1"
            ],
            "v": "<1.7.1"
        },
        {
            "advisory": "Affected versions of the Langflow package are vulnerable to Privilege Escalation due to improper access controls on the internal CLI command langflow superuser. The Docker image includes a CLI binary at /app/.venv/bin/langflow that exposes the langflow superuser command, which creates new administrative users without verifying existing permissions or whether a superuser already exists, and can be invoked by authenticated users who achieve code execution through endpoints like /api/v1/validate/code.",
            "cve": "CVE-2025-57760",
            "id": "pyup.io-79075",
            "more_info_path": "/vulnerabilities/CVE-2025-57760/79075",
            "specs": [
                "<=1.5.0"
            ],
            "v": "<=1.5.0"
        }
    ],
    "langfuse": [
        {
            "advisory": "Langfuse version 2.1.0 updates its nodemailer dependency to 6.9.9 from 6.9.8, prompted by security considerations.\r\nhttps://github.com/langfuse/langfuse/pull/1027",
            "cve": "PVE-2024-65269",
            "id": "pyup.io-65269",
            "more_info_path": "/vulnerabilities/PVE-2024-65269/65269",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Langfuse affected versions are vulnerable to Open Redirect (CWE-601). This vulnerability allows attackers to craft malicious URLs that can redirect users to arbitrary external websites after authentication. The impact includes potential phishing attacks and unauthorized data exposure. The attack vector involves manipulating the targetPath query parameter in the sign-in URL. The vulnerable function is the redirect logic in the Layout component. Exploitability is high as it requires minimal user interaction. The commit mitigates this by implementing strict checks to allow only relative URLs for redirection. Users should update to the latest version containing this fix.",
            "cve": "PVE-2024-73564",
            "id": "pyup.io-73564",
            "more_info_path": "/vulnerabilities/PVE-2024-73564/73564",
            "specs": [
                "<2.81.1"
            ],
            "v": "<2.81.1"
        },
        {
            "advisory": "Langfuse 2.93.5 upgrades the next-auth dependency from ^4.24.7 to ^4.24.11 to fix a security vulnerability identified as CVE-2023-48309.",
            "cve": "CVE-2023-48309",
            "id": "pyup.io-74718",
            "more_info_path": "/vulnerabilities/CVE-2023-48309/74718",
            "specs": [
                "<2.93.5"
            ],
            "v": "<2.93.5"
        },
        {
            "advisory": "Langfuse has updated the next dependency from version 14.2.15 to 14.2.21 in both ee/package.json and web/package.json due to the CVE-2024-56332.",
            "cve": "CVE-2024-56332",
            "id": "pyup.io-74956",
            "more_info_path": "/vulnerabilities/CVE-2024-56332/74956",
            "specs": [
                "<2.93.8"
            ],
            "v": "<2.93.8"
        },
        {
            "advisory": "Security Fix for Langfuse 2.95.2 | DOMPurify library upgrade to address potential XSS vulnerabilities.\r\n- Fixed Versions: 2.95.2\r\n- Affected Versions: <2.95.2\r\nThe parent\u201d is DOMPurify. it\u2019s in a JavaScript library that langfuse uses directly.",
            "cve": "PVE-2025-75620",
            "id": "pyup.io-75620",
            "more_info_path": "/vulnerabilities/PVE-2025-75620/75620",
            "specs": [
                "<2.95.2"
            ],
            "v": "<2.95.2"
        },
        {
            "advisory": "Security Fix for Langfuse 2.95.3 | Security upgrade of jsonpath-plus dependency to version 2. Package upgrade to address potential security vulnerabilities in jsonpath-plus library\r\n\r\n- Fixed Versions: 2.95.3\r\n- Affected Versions: <2.95.3\r\n\r\nParent Liberary jsonpath-plus is no in pypi",
            "cve": "PVE-2025-75618",
            "id": "pyup.io-75618",
            "more_info_path": "/vulnerabilities/PVE-2025-75618/75618",
            "specs": [
                "<2.95.3"
            ],
            "v": "<2.95.3"
        },
        {
            "advisory": "Langfuse upgrades its axios dependency to 1.8.2 due to the CVE-2025-27152.",
            "cve": "CVE-2025-27152",
            "id": "pyup.io-75964",
            "more_info_path": "/vulnerabilities/CVE-2025-27152/75964",
            "specs": [
                "<2.95.6"
            ],
            "v": "<2.95.6"
        },
        {
            "advisory": "Langfuse upgrades katex to ^0.16.21 in package.json and web/package.json for due to the CVE-2025-23207.",
            "cve": "CVE-2025-23207",
            "id": "pyup.io-75139",
            "more_info_path": "/vulnerabilities/CVE-2025-23207/75139",
            "specs": [
                "<3.13.0"
            ],
            "v": "<3.13.0"
        },
        {
            "advisory": "Affected versions of the langfuse package are vulnerable to Open Redirect due to improper validation of user-controlled redirect paths in the client-side authentication flow.",
            "cve": "PVE-2025-82116",
            "id": "pyup.io-82116",
            "more_info_path": "/vulnerabilities/PVE-2025-82116/82116",
            "specs": [
                "<3.133.0"
            ],
            "v": "<3.133.0"
        },
        {
            "advisory": "Affected versions of the langfuse package are vulnerable to server-side request forgery (SSRF) due to webhook HTTP redirects not being validated against the same hostname/IP allow/deny rules as the original webhook URL.",
            "cve": "PVE-2025-83165",
            "id": "pyup.io-83165",
            "more_info_path": "/vulnerabilities/PVE-2025-83165/83165",
            "specs": [
                "<3.142.0"
            ],
            "v": "<3.142.0"
        },
        {
            "advisory": "Affected versions of the langfuse package are vulnerable to Server-Side Request Forgery (SSRF) due to missing validation of a user-configurable PostHog base URL/hostname.",
            "cve": "PVE-2026-84393",
            "id": "pyup.io-84393",
            "more_info_path": "/vulnerabilities/PVE-2026-84393/84393",
            "specs": [
                "<3.144.0"
            ],
            "v": "<3.144.0"
        },
        {
            "advisory": "Security Fix for Langfuse 3.28.1 | Security upgrades for DOMPurify and release-it dependencies.\r\n- Fixed Versions: v3.28.1\r\n- Affected Versions: =0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "laporte-mqtt": [
        {
            "advisory": "Laporte-Mqtt 0.2.2 includes a security patch for the function 'load_config' in 'laporte_mqtt/config.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/vinklat/laporte-mqtt/commit/db24ded1c1ed0232c42bb826b9c1dc30fb925f2e",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41334",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41334",
            "specs": [
                "<0.2.2"
            ],
            "v": "<0.2.2"
        }
    ],
    "lattice": [
        {
            "advisory": "Lattice 0.1.2 replaces its dependency 'GitPython' with 'pygit2' to avoid security issues.",
            "cve": "PVE-2022-52518",
            "id": "pyup.io-52519",
            "more_info_path": "/vulnerabilities/PVE-2022-52518/52519",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        },
        {
            "advisory": "Lattice 0.1.2 replaces its dependency 'GitPython' with 'pygit2' to avoid security issues.",
            "cve": "CVE-2022-24439",
            "id": "pyup.io-52450",
            "more_info_path": "/vulnerabilities/CVE-2022-24439/52450",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "launchable": [
        {
            "advisory": "Launchable 1.38.10 includes a fix for a OS command injection vulnerability.\r\nhttps://github.com/launchableinc/cli/pull/393",
            "cve": "PVE-2023-58696",
            "id": "pyup.io-58696",
            "more_info_path": "/vulnerabilities/PVE-2023-58696/58696",
            "specs": [
                "<1.38.10"
            ],
            "v": "<1.38.10"
        }
    ],
    "launchdarkly-server-sdk": [
        {
            "advisory": "Launchdarkly-server-sdk 6.11.2 uses 'yaml.safe_load()' instead of 'yaml.load()' for YAML/JSON test data parsing to fix an arbitrary code execution vulnerability.\r\nhttps://github.com/launchdarkly/python-server-sdk/issues/136",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-43004",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/43004",
            "specs": [
                "<6.11.2"
            ],
            "v": "<6.11.2"
        },
        {
            "advisory": "Setting `verify_ssl` to `False` in the client configuration of launchdarkly-server-sdk before 6.12.2 did not have the expected effect of completely turning off SSL/TLS verification, because it still left _certificate_ verification in effect, so it would allow a totally insecure connection but reject a secure connection whose certificate had an unknown CA. This has been changed so that it will turn off certificate verification as well. This is not a recommended practice and a future version of the SDK will add a way to specify a custom certificate authority instead (to support, for instance, using the Relay Proxy with a self-signed certificate).",
            "cve": "PVE-2021-38082",
            "id": "pyup.io-38082",
            "more_info_path": "/vulnerabilities/PVE-2021-38082/38082",
            "specs": [
                "<6.12.2"
            ],
            "v": "<6.12.2"
        }
    ],
    "launchkey": [
        {
            "advisory": "Launchkey 3.9.1 updates its dependency 'jinja2' to v2.11.3 to include a security fix.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-40654",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/40654",
            "specs": [
                "<3.9.1"
            ],
            "v": "<3.9.1"
        },
        {
            "advisory": "Launchkey 4.0.1 updates its dependency 'pylint' to v2.13.0 to include a security fix.",
            "cve": "PVE-2022-45185",
            "id": "pyup.io-50758",
            "more_info_path": "/vulnerabilities/PVE-2022-45185/50758",
            "specs": [
                "<4.0.1"
            ],
            "v": "<4.0.1"
        }
    ],
    "layeredimage": [
        {
            "advisory": "Layeredimage 2021.2.1 updates its dependency 'pillow' to a version >= 8.1.1 to include security fixes.",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-40330",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/40330",
            "specs": [
                "<2021.2.1"
            ],
            "v": "<2021.2.1"
        },
        {
            "advisory": "layeredimage 2021.2.1 updates its dependency 'pillow' to versions >= 8.1.1 to imclude security fixes.",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-40329",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/40329",
            "specs": [
                "<2021.2.1"
            ],
            "v": "<2021.2.1"
        },
        {
            "advisory": "Layeredimage 2021.2.1 updates the 'Pillow' dependency >= 8.1.1 due to high severity security vulnerabilities (CVE-2020-35655).",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-40332",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/40332",
            "specs": [
                "<2021.2.1"
            ],
            "v": "<2021.2.1"
        },
        {
            "advisory": "Layeredimage 2021.2.1 updates the 'Pillow' dependency >= 8.1.1 due to high severity security vulnerabilities (CVE-2020-35654).",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-40328",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/40328",
            "specs": [
                "<2021.2.1"
            ],
            "v": "<2021.2.1"
        },
        {
            "advisory": "Layeredimage 2021.2.1 updates its dependency 'pillow' to a version >= 8.1.1 to include security fixes.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-40327",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/40327",
            "specs": [
                "<2021.2.1"
            ],
            "v": "<2021.2.1"
        },
        {
            "advisory": "Layeredimage 2021.2.1 updates its dependency 'pillow' to a version >= 8.1.1 to include security fixes.",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-40331",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/40331",
            "specs": [
                "<2021.2.1"
            ],
            "v": "<2021.2.1"
        }
    ],
    "lazuli": [
        {
            "advisory": "Lazuli 2.2.2 pins its dependency 'protobuf' to v3.20.1 to include a security fix.",
            "cve": "CVE-2021-22570",
            "id": "pyup.io-50459",
            "more_info_path": "/vulnerabilities/CVE-2021-22570/50459",
            "specs": [
                "<2.2.2"
            ],
            "v": "<2.2.2"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'jinja2' to v2.11.3 to include a security fix.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-50477",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/50477",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'urllib3' to v1.26.11 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-50479",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/50479",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'pygments' to v2.12.0 to include a security fix.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-50480",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/50480",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'nltk' to v3.7 to include security fixes.",
            "cve": "CVE-2021-3842",
            "id": "pyup.io-50483",
            "more_info_path": "/vulnerabilities/CVE-2021-3842/50483",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'nltk' to v3.7 to include security fixes.",
            "cve": "CVE-2021-43854",
            "id": "pyup.io-50484",
            "more_info_path": "/vulnerabilities/CVE-2021-43854/50484",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'urllib3' to v1.26.11 to include a security fix.",
            "cve": "CVE-2021-28363",
            "id": "pyup.io-50478",
            "more_info_path": "/vulnerabilities/CVE-2021-28363/50478",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'pygments' to v2.12.0 to include a security fix.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-50481",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/50481",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'mkdocs' to v1.3.1 to include a security fix.",
            "cve": "CVE-2021-40978",
            "id": "pyup.io-50476",
            "more_info_path": "/vulnerabilities/CVE-2021-40978/50476",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'nltk' to v3.7 to include security fixes.",
            "cve": "CVE-2021-3828",
            "id": "pyup.io-50482",
            "more_info_path": "/vulnerabilities/CVE-2021-3828/50482",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        },
        {
            "advisory": "Lazuli 2.2.3 updates its dependency 'pyyaml' to v5.4.1 to include a security fix.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-50458",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/50458",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        }
    ],
    "lazy-loading": [
        {
            "advisory": "Affected versions of the lazy-loading package are vulnerable to global namespace injection due to writing lazy-loaded module proxies into the caller\u2019s globals.",
            "cve": "PVE-2025-83223",
            "id": "pyup.io-83223",
            "more_info_path": "/vulnerabilities/PVE-2025-83223/83223",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "lbt-dragonfly": [
        {
            "advisory": "Lbt-dragonfly 0.9.404 updates its dependency 'setuptools' to v.65.5.1 to include a security fix.",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-52816",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/52816",
            "specs": [
                "<0.9.404"
            ],
            "v": "<0.9.404"
        },
        {
            "advisory": "Lbt-dragonfly 0.9.404 updates its dependency 'wheel' to v0.38.1 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-52775",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/52775",
            "specs": [
                "<0.9.404"
            ],
            "v": "<0.9.404"
        }
    ],
    "lbt-honeybee": [
        {
            "advisory": "Lbt-honeybee 0.7.125 updates its dependency 'wheel' to v0.38.1 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-53137",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/53137",
            "specs": [
                "<0.7.125"
            ],
            "v": "<0.7.125"
        },
        {
            "advisory": "Lbt-honeybee 0.7.125 updates its dependency 'setuptools' to v65.5.1 to include a security fix.",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-53265",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/53265",
            "specs": [
                "<0.7.125"
            ],
            "v": "<0.7.125"
        }
    ],
    "lc-sdk-python": [
        {
            "advisory": "Lc-sdk-python 0.3.1 updates 'httpx' dependency to v0.23.0 to include a security fix.",
            "cve": "CVE-2021-41945",
            "id": "pyup.io-49011",
            "more_info_path": "/vulnerabilities/CVE-2021-41945/49011",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "ldap3": [
        {
            "advisory": "ldap3 before 0.9.5.4 has several security issues in lazy connections.",
            "cve": "PVE-2021-25875",
            "id": "pyup.io-25875",
            "more_info_path": "/vulnerabilities/PVE-2021-25875/25875",
            "specs": [
                "<0.9.5.4"
            ],
            "v": "<0.9.5.4"
        },
        {
            "advisory": "Ldap3 2.4 includes a security fix in the rebind() method of the Connection object. A correct bind followed by a rebind with empty password completed the binding correctly.\r\nhttps://github.com/cannatag/ldap3/issues/393",
            "cve": "PVE-2021-35053",
            "id": "pyup.io-35053",
            "more_info_path": "/vulnerabilities/PVE-2021-35053/35053",
            "specs": [
                "<2.4"
            ],
            "v": "<2.4"
        }
    ],
    "ldap3-ad-leavers": [
        {
            "advisory": "Ldap3-ad-leavers 1.2.0 includes a fix for a code injection vulnerability.\r\nhttps://github.com/mervinhemaraju/ldap3-ad-leavers/commit/0e8351c3b6df679423e3cd8fa847487a55f85687",
            "cve": "PVE-2022-52390",
            "id": "pyup.io-52390",
            "more_info_path": "/vulnerabilities/PVE-2022-52390/52390",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "ldapcherry": [
        {
            "advisory": "A vulnerability, which was classified as problematic, was found in kakwa LdapCherry up to 0.x. Affected is an unknown function of the component URL Handler. The manipulation leads to cross site scripting. It is possible to launch the attack remotely.",
            "cve": "CVE-2019-25095",
            "id": "pyup.io-54645",
            "more_info_path": "/vulnerabilities/CVE-2019-25095/54645",
            "specs": [
                ">=0,<1.0.0"
            ],
            "v": ">=0,<1.0.0"
        }
    ],
    "leap-bitmask": [
        {
            "advisory": "Leap.bitmask 0.9.0 stops including 3rd party libs logs. These logs could include, for example, exported PGP private keys.\r\nhttps://github.com/leapcode/bitmask-dev/commit/fc65820f9e9a9a39434bbef3f5e9251436d9b458",
            "cve": "PVE-2017-47230",
            "id": "pyup.io-47230",
            "more_info_path": "/vulnerabilities/PVE-2017-47230/47230",
            "specs": [
                "<0.9"
            ],
            "v": "<0.9"
        }
    ],
    "learninglib": [
        {
            "advisory": "Learninglib is a malicious package, typosquatting.  It installs cryptomining malware in your system.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-pypi-packages-hijack-dev-devices-to-mine-cryptocurrency/",
            "cve": "PVE-2022-45477",
            "id": "pyup.io-45477",
            "more_info_path": "/vulnerabilities/PVE-2022-45477/45477",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "ledfx": [
        {
            "advisory": "Ledfx 2.0.70 addresses and resolves a critical issue that could cause crashes due to a race condition and the presence of empty virtual data. The race condition could potentially be exploited to cause a denial of service (DoS).",
            "cve": "PVE-2024-67135",
            "id": "pyup.io-67135",
            "more_info_path": "/vulnerabilities/PVE-2024-67135/67135",
            "specs": [
                "<2.0.70"
            ],
            "v": "<2.0.70"
        }
    ],
    "lekt": [
        {
            "advisory": "Lekt 14.0.13 updates Open EDX image version to 14.2.1, which includes a security fix for a XSS vulnerability in edx-platform.\r\nhttps://github.com/lektorium-tutor/lekt/commit/b46a7b0fa806604eddaed8646a2a8712a8508c79",
            "cve": "PVE-2022-51649",
            "id": "pyup.io-52118",
            "more_info_path": "/vulnerabilities/PVE-2022-51649/52118",
            "specs": [
                "<14.0.13"
            ],
            "v": "<14.0.13"
        },
        {
            "advisory": "Lekt 14.0.13 updates Open EDX image version to 14.2.1, which includes a security fix for a vulnerability in the xblock ajax handler.\r\nhttps://github.com/lektorium-tutor/lekt/commit/3ba53655378cbe00245354bce159d720fb2cbbd6",
            "cve": "PVE-2022-51540",
            "id": "pyup.io-52119",
            "more_info_path": "/vulnerabilities/PVE-2022-51540/52119",
            "specs": [
                "<14.0.13"
            ],
            "v": "<14.0.13"
        }
    ],
    "lektor": [
        {
            "advisory": "Lektor affected versions does not sanitize DB path traversal. Thus, shell commands might be executed via a file that is added to the templates directory, if the victim's web browser accesses an untrusted website that uses JavaScript to send requests to localhost port 5000, and the web browser is running on the same machine as the \"lektor server\" command.",
            "cve": "CVE-2024-28335",
            "id": "pyup.io-71925",
            "more_info_path": "/vulnerabilities/CVE-2024-28335/71925",
            "specs": [
                ">=0,<3.3.11",
                ">=3.4.0b1,<3.4.0b11"
            ],
            "v": ">=0,<3.3.11,>=3.4.0b1,<3.4.0b11"
        }
    ],
    "lemur": [
        {
            "advisory": "Lemur 0.1.5 includes a fix for CVE-2015-7764: Lemur 0.1.4 does not use sufficient entropy in its IV when encrypting AES in CBC mode.\r\nhttp://www.openwall.com/lists/oss-security/2015/10/20/3\r\nhttps://github.com/Netflix/lemur/issues/117\r\nhttps://github.com/kvesteri/sqlalchemy-utils/issues/166",
            "cve": "CVE-2015-7764",
            "id": "pyup.io-25876",
            "more_info_path": "/vulnerabilities/CVE-2015-7764/25876",
            "specs": [
                "<0.1.5"
            ],
            "v": "<0.1.5"
        },
        {
            "advisory": "Lemur 0.9.0 fixes three critical vulnerabilities where an authenticated user could retrieve/access unauthorized information. See also .",
            "cve": "PVE-2021-40028",
            "id": "pyup.io-40028",
            "more_info_path": "/vulnerabilities/PVE-2021-40028/40028",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Lemur 1.2.0 fixes a vulnerability where creating an authority automatically granted the selected owner role to the authority creator, which allowed users to grant themselves to arbitrary roles. The owner role is no longer auto-assigned when creating an authority.",
            "cve": "PVE-2022-44737",
            "id": "pyup.io-44737",
            "more_info_path": "/vulnerabilities/PVE-2022-44737/44737",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        },
        {
            "advisory": "Netflix Lemur before version 1.3.2 used insufficiently random values when generating default credentials. The insufficiently random values may allow an attacker to guess the credentials and gain access to resources managed by Lemur.",
            "cve": "CVE-2023-30797",
            "id": "pyup.io-64190",
            "more_info_path": "/vulnerabilities/CVE-2023-30797/64190",
            "specs": [
                "<1.3.2"
            ],
            "v": "<1.3.2"
        },
        {
            "advisory": "Lemur 1.3.2 includes a security fix for an insecure random generation vulnerability.\r\nhttps://github.com/Netflix/lemur/security/advisories/GHSA-5fqv-mpj8-h7gm",
            "cve": "PVE-2023-53505",
            "id": "pyup.io-53505",
            "more_info_path": "/vulnerabilities/PVE-2023-53505/53505",
            "specs": [
                "<1.3.2"
            ],
            "v": "<1.3.2"
        },
        {
            "advisory": "Lemur version 1.7.0 addresses a Denial of Service (DoS) security issue affecting Windows environments. This vulnerability involved the `name` parameter of the certificate POST endpoint.\r\n# This vulnerability only impacts Windows users.",
            "cve": "PVE-2024-71065",
            "id": "pyup.io-71065",
            "more_info_path": "/vulnerabilities/PVE-2024-71065/71065",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        }
    ],
    "leo": [
        {
            "advisory": "Leo Editor v6.2.1 was discovered to contain a regular expression denial of service (ReDoS) vulnerability in the component plugins/importers/dart.py.",
            "cve": "CVE-2020-23478",
            "id": "pyup.io-54337",
            "more_info_path": "/vulnerabilities/CVE-2020-23478/54337",
            "specs": [
                ">=0,<6.3"
            ],
            "v": ">=0,<6.3"
        }
    ],
    "letta": [
        {
            "advisory": "Incorrect access control in the /users endpoint of Cpacker MemGPT v0.3.17 allows attackers to access sensitive data.",
            "cve": "CVE-2024-39025",
            "id": "pyup.io-76373",
            "more_info_path": "/vulnerabilities/CVE-2024-39025/76373",
            "specs": [
                "<0.3.17"
            ],
            "v": "<0.3.17"
        },
        {
            "advisory": "Affected versions of the letta package are vulnerable to Remote Code Execution due to an insufficient sandboxing mechanism around its file upload / tool execution logic. In particular, the run_tool_from_source endpoint in letta.server.rest_api.routers.v1.tools uses Python\u2019s exec() on user-supplied code without adequately restricting or sanitizing modules, functions, or file names.",
            "cve": "PVE-2025-80293",
            "id": "pyup.io-80293",
            "more_info_path": "/vulnerabilities/PVE-2025-80293/80293",
            "specs": [
                "<0.5.3"
            ],
            "v": "<0.5.3"
        }
    ],
    "levenshtein": [
        {
            "advisory": "Levenshtein 0.12.1 fixes handling of numerous possible wraparounds in calculating the size of memory allocations; incorrect handling of which could cause denial of service or even possible remote code execution in previous versions of the library.\r\nhttps://github.com/ztane/python-Levenshtein/issues/62",
            "cve": "PVE-2022-44654",
            "id": "pyup.io-44654",
            "more_info_path": "/vulnerabilities/PVE-2022-44654/44654",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        }
    ],
    "lexoid": [
        {
            "advisory": "Lexoid fixes a security vulnerability by replacing a command injection-prone os.system() call with the safer subprocess.run() approach when converting documents to PDF on Linux systems.",
            "cve": "PVE-2025-80178",
            "id": "pyup.io-80178",
            "more_info_path": "/vulnerabilities/PVE-2025-80178/80178",
            "specs": [
                "<0.1.18"
            ],
            "v": "<0.1.18"
        }
    ],
    "lfm": [
        {
            "advisory": "Lfm 2.0 uses tempfile secure versions mkdtemp() and mkstemp().",
            "cve": "PVE-2021-34612",
            "id": "pyup.io-34612",
            "more_info_path": "/vulnerabilities/PVE-2021-34612/34612",
            "specs": [
                "<2.0"
            ],
            "v": "<2.0"
        }
    ],
    "lg-rez": [
        {
            "advisory": "Lg-rez 2.1.4 updates its dependency 'rsa' to v4.7 to include a security fix.",
            "cve": "CVE-2020-25658",
            "id": "pyup.io-42106",
            "more_info_path": "/vulnerabilities/CVE-2020-25658/42106",
            "specs": [
                "<2.1.4"
            ],
            "v": "<2.1.4"
        },
        {
            "advisory": "Lg-rez version 2.1.4 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28675",
            "id": "pyup.io-42103",
            "more_info_path": "/vulnerabilities/CVE-2021-28675/42103",
            "specs": [
                "<2.1.4"
            ],
            "v": "<2.1.4"
        },
        {
            "advisory": "Lg-rez version 2.1.4 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-42049",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/42049",
            "specs": [
                "<2.1.4"
            ],
            "v": "<2.1.4"
        },
        {
            "advisory": "Lg-rez version 2.1.4 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-42104",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/42104",
            "specs": [
                "<2.1.4"
            ],
            "v": "<2.1.4"
        },
        {
            "advisory": "Lg-rez version 2.1.4 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-42105",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/42105",
            "specs": [
                "<2.1.4"
            ],
            "v": "<2.1.4"
        }
    ],
    "lib3mf": [
        {
            "advisory": "Lib3mf version 2.0.1 and 2.1.1 resolves a security issue involving double free / use after free in the usage of libzip, identified as CVE-2021-21772.",
            "cve": "CVE-2021-21772",
            "id": "pyup.io-71396",
            "more_info_path": "/vulnerabilities/CVE-2021-21772/71396",
            "specs": [
                "<2.0.1",
                ">2.1,<2.1.1"
            ],
            "v": "<2.0.1,>2.1,<2.1.1"
        }
    ],
    "libarchive-c": [
        {
            "advisory": "Libarchive-c 4.0 includes a fix for an unsafe defaults vulnerability that could have lead to path traversal.\r\nhttps://github.com/Changaco/python-libarchive-c/commit/98c14d296a7f3ab04dd0a4c8c9c2920f88537fa7",
            "cve": "PVE-2023-59300",
            "id": "pyup.io-59300",
            "more_info_path": "/vulnerabilities/PVE-2023-59300/59300",
            "specs": [
                "<4.0"
            ],
            "v": "<4.0"
        }
    ],
    "libari": [
        {
            "advisory": "Libari is a malicious package, typosquatting. It contains a hidden backdoor which activates when installed on Linux systems.\r\nhttps://www.zdnet.com/article/malicious-python-libraries-targeting-linux-servers-removed-from-pypi/",
            "cve": "PVE-2022-45410",
            "id": "pyup.io-45410",
            "more_info_path": "/vulnerabilities/PVE-2022-45410/45410",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "libcoveweb": [
        {
            "advisory": "Affected versions of Libcoveweb are vulnerable to Denial of Service (DoS) attacks. The impact includes potential server resource exhaustion due to long-running requests. The attack vector involves submitting URLs that take an excessive amount of time to respond. The vulnerable function is the download method in SuppliedData model. Exploitability is moderate, requiring an attacker to supply a slow-responding URL. The commit mitigates this by implementing a configurable timeout for URL requests. Users should update to the latest version containing this fix. This vulnerability is specific to web applications and has a CWE identifier of CWE-400: Uncontrolled Resource Consumption.",
            "cve": "PVE-2024-73572",
            "id": "pyup.io-73572",
            "more_info_path": "/vulnerabilities/PVE-2024-73572/73572",
            "specs": [
                "<0.30.5"
            ],
            "v": "<0.30.5"
        }
    ],
    "libgenesis": [
        {
            "advisory": "Libgenesis 0.1.8 updates its dependency 'lxml' to v4.6.5 to include a security fix.",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-43379",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/43379",
            "specs": [
                "<0.1.8"
            ],
            "v": "<0.1.8"
        },
        {
            "advisory": "Libgenesis 0.1.8 updates its dependency 'lxml' minimum version to v4.6.5 to include security fixes.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-43386",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/43386",
            "specs": [
                "<0.1.8"
            ],
            "v": "<0.1.8"
        },
        {
            "advisory": "Libgenesis 0.1.8 updates its dependency 'lxml' minimum version to v4.6.5 to include security fixes.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-43385",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/43385",
            "specs": [
                "<0.1.8"
            ],
            "v": "<0.1.8"
        }
    ],
    "libhttps": [
        {
            "advisory": "Libhttps is a malicious package. It installs info-stealing Malware.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-lolip0p-pypi-packages-install-info-stealing-malware",
            "cve": "PVE-2023-52926",
            "id": "pyup.io-52926",
            "more_info_path": "/vulnerabilities/PVE-2023-52926/52926",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "libhxl": [
        {
            "advisory": "For web-security reasons, libhxl 4.21.3 blocks the fetching of datasets from localhost, *.localdomain (or any dotted quad) unless allow_local is True.",
            "cve": "PVE-2021-39450",
            "id": "pyup.io-39450",
            "more_info_path": "/vulnerabilities/PVE-2021-39450/39450",
            "specs": [
                "<4.21.3"
            ],
            "v": "<4.21.3"
        },
        {
            "advisory": "Libhxl 4.25.2 includes better sanitisation preventing HTML input.\r\nhttps://github.com/HXLStandard/libhxl-python/commit/28e54a3dafc1b61cff94d65ed019794914167b7a",
            "cve": "PVE-2022-50155",
            "id": "pyup.io-50155",
            "more_info_path": "/vulnerabilities/PVE-2022-50155/50155",
            "specs": [
                "<4.25.2"
            ],
            "v": "<4.25.2"
        }
    ],
    "libigl": [
        {
            "advisory": "Affected versions of libigl before commit 3370a3e9 are potentially vulnerable to a race condition in the dual_contouring code. This can lead to unsynchronized calls to new_vertex() that resize internal std::vector<>s outside of a mutex, resulting in potential memory corruption or application crashes. The vulnerability is triggered when using igl::dual_contouring in multi-threaded contexts.",
            "cve": "PVE-2025-77276",
            "id": "pyup.io-77276",
            "more_info_path": "/vulnerabilities/PVE-2025-77276/77276",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        }
    ],
    "libosdp": [
        {
            "advisory": "Libosdp 1.3.0 includes a fix for a CWE-1392: Use of Default Credentials.\r\nhttps://github.com/goToMain/libosdp/commit/cb918c29ca672375cc4bdcef84e2c8d21a8df3e8",
            "cve": "PVE-2023-62431",
            "id": "pyup.io-62431",
            "more_info_path": "/vulnerabilities/PVE-2023-62431/62431",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "libp2p": [
        {
            "advisory": "py-libp2p before 0.2.3 allows a peer to cause a denial of service (resource consumption) via a large RSA key.",
            "cve": "CVE-2025-29606",
            "id": "pyup.io-78160",
            "more_info_path": "/vulnerabilities/CVE-2025-29606/78160",
            "specs": [
                "<0.2.3"
            ],
            "v": "<0.2.3"
        }
    ],
    "libpesh": [
        {
            "advisory": "Libpesh is a malicious package, typosquatting. It contains a hidden backdoor which activates when installed on Linux systems.\r\nhttps://www.zdnet.com/article/malicious-python-libraries-targeting-linux-servers-removed-from-pypi/",
            "cve": "PVE-2022-45409",
            "id": "pyup.io-45409",
            "more_info_path": "/vulnerabilities/PVE-2022-45409/45409",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "libpeshka": [
        {
            "advisory": "Libpeshka is a typosquatting package. It shows a malicious behavior, for example, it may leak your sensitive data and/or gain unauthorized persistence in your system.\r\nhttps://www.zdnet.com/article/twelve-malicious-python-libraries-found-and-removed-from-pypi/",
            "cve": "PVE-2022-45415",
            "id": "pyup.io-45415",
            "more_info_path": "/vulnerabilities/PVE-2022-45415/45415",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "libpeshnx": [
        {
            "advisory": "Libpeshnx is a malicious package, typosquatting. It contains a hidden backdoor which activates when installed on Linux systems.\r\nhttps://www.zdnet.com/article/malicious-python-libraries-targeting-linux-servers-removed-from-pypi/",
            "cve": "PVE-2022-45408",
            "id": "pyup.io-45408",
            "more_info_path": "/vulnerabilities/PVE-2022-45408/45408",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "libre-chat": [
        {
            "advisory": "Affected Versions of libre_chat are vulnerable to Path Traversal (CWE-22). An attacker could manipulate the uploaded.filename to write files outside the designated directory, potentially accessing or modifying sensitive system files. This vulnerability arises from using os.path.join without proper sanitization. Versions prior to 0.0.6 are exploitable through crafted filenames. To mitigate this issue, upgrade to the latest version where werkzeug.utils.safe_join is used to securely construct file paths, preventing unauthorized directory access.",
            "cve": "CVE-2024-52787",
            "id": "pyup.io-74437",
            "more_info_path": "/vulnerabilities/CVE-2024-52787/74437",
            "specs": [
                "<=0.0.6"
            ],
            "v": "<=0.0.6"
        }
    ],
    "libre-fastapi-jwt": [
        {
            "advisory": "Libre-fastapi-jwt 0.20.3 updates its dependency 'cryptography' to version '41.0.1' to include a security fix.\r\nhttps://github.com/LibreNZ/libre-fastapi-jwt/commit/fa128ea36cf021e104f564d3c7bc3874f83461fe",
            "cve": "CVE-2023-2650",
            "id": "pyup.io-59085",
            "more_info_path": "/vulnerabilities/CVE-2023-2650/59085",
            "specs": [
                "<0.20.3"
            ],
            "v": "<0.20.3"
        }
    ],
    "libretranslate": [
        {
            "advisory": "Libretranslate 1.5.4 updates its Requests dependency from 2.28.1 to 2.31.0. This upgrade addresses the vulnerability identified as CVE-2023-32681.\r\nhttps://github.com/LibreTranslate/LibreTranslate/pull/570/commits/51341d92ade55e47d94ac2f6dd095fcc226e62d0",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-64073",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/64073",
            "specs": [
                "<1.5.4"
            ],
            "v": "<1.5.4"
        },
        {
            "advisory": "Libretranslate 1.5.4 updates its Werkzeug dependency from 2.2.2 to 2.3.8. This upgrade addresses the vulnerability identified as CVE-2023-25577.\r\nhttps://github.com/LibreTranslate/LibreTranslate/pull/570/commits/51341d92ade55e47d94ac2f6dd095fcc226e62d0",
            "cve": "CVE-2023-25577",
            "id": "pyup.io-64074",
            "more_info_path": "/vulnerabilities/CVE-2023-25577/64074",
            "specs": [
                "<1.5.4"
            ],
            "v": "<1.5.4"
        },
        {
            "advisory": "Libretranslate 1.5.4 updates its Flask dependency from 2.2.2 to 2.2.5. This upgrade addresses the vulnerability identified as CVE-2023-30861.\r\nhttps://github.com/LibreTranslate/LibreTranslate/pull/570/commits/51341d92ade55e47d94ac2f6dd095fcc226e62d0",
            "cve": "CVE-2023-30861",
            "id": "pyup.io-63742",
            "more_info_path": "/vulnerabilities/CVE-2023-30861/63742",
            "specs": [
                "<1.5.4"
            ],
            "v": "<1.5.4"
        }
    ],
    "libtaxii": [
        {
            "advisory": "libtaxii before 1.1.105 has multiple XML parsing related vulnerabilities.",
            "cve": "PVE-2021-25877",
            "id": "pyup.io-25877",
            "more_info_path": "/vulnerabilities/PVE-2021-25877/25877",
            "specs": [
                "<1.1.105"
            ],
            "v": "<1.1.105"
        },
        {
            "advisory": "Libtaxii 1.1.118 includes a fix for CVE-2020-27197:TAXII libtaxii through 1.1.117, as used in EclecticIQ OpenTAXII through 0.2.0 and other products, allows SSRF via an initial http:// substring to the parse method, even when the no_network setting is used for the XML parser. \r\nNOTE: the vendor points out that the parse method \"wraps the lxml library\" and that this may be an issue to \"raise ... to the lxml group.\"",
            "cve": "CVE-2020-27197",
            "id": "pyup.io-54231",
            "more_info_path": "/vulnerabilities/CVE-2020-27197/54231",
            "specs": [
                ">=0,<1.1.118"
            ],
            "v": ">=0,<1.1.118"
        }
    ],
    "libtmux": [
        {
            "advisory": "Libtmux 0.11.0 updates its dependency 'brotly' to versions >=1.0.9 to include a security fix.",
            "cve": "CVE-2020-8927",
            "id": "pyup.io-46485",
            "more_info_path": "/vulnerabilities/CVE-2020-8927/46485",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "libtorrent": [
        {
            "advisory": "Libtorrent 2.0.3 (the underlying core dependency of the Python bindings) fixes an integer overflow in hash_picker and properly restricts max file sizes in torrents.\r\nhttps://github.com/arvidn/libtorrent/commit/58a489332ca05303e8001c24478f27338309c858",
            "cve": "PVE-2021-43049",
            "id": "pyup.io-43049",
            "more_info_path": "/vulnerabilities/PVE-2021-43049/43049",
            "specs": [
                "<2.0.3"
            ],
            "v": "<2.0.3"
        }
    ],
    "libvcs": [
        {
            "advisory": "Libvcs before 0.11.1 is vulnerable to Command Injection via argument injection. When calling the update_repo function (when using hg), the url parameter is passed to the hg clone command. By injecting some hg options it was possible to get arbitrary command execution.",
            "cve": "CVE-2022-21187",
            "id": "pyup.io-46409",
            "more_info_path": "/vulnerabilities/CVE-2022-21187/46409",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        }
    ],
    "libyang": [
        {
            "advisory": "A stack overflow in libyang <= v1.0.225 or possibly <= 1.0.240 can cause a denial of service through function lyxml_parse_mem(). lyxml_parse_elem() function will be called recursively, which will consume stack space and lead to crash.",
            "cve": "CVE-2021-28903",
            "id": "pyup.io-62212",
            "more_info_path": "/vulnerabilities/CVE-2021-28903/62212",
            "specs": [
                "<1.0.240"
            ],
            "v": "<1.0.240"
        },
        {
            "advisory": "In function read_yin_container() in libyang <= v1.0.225 or possibly <= 1.0.240 doesn't check whether the value of retval->ext[r] is NULL. In some cases, it can be NULL, which leads to the operation of retval->ext[r]->flags that results in a crash.",
            "cve": "CVE-2021-28902",
            "id": "pyup.io-62213",
            "more_info_path": "/vulnerabilities/CVE-2021-28902/62213",
            "specs": [
                "<1.0.240"
            ],
            "v": "<1.0.240"
        }
    ],
    "licensemonitor": [
        {
            "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'licensemonitor' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.",
            "cve": "PVE-2024-74249",
            "id": "pyup.io-74249",
            "more_info_path": "/vulnerabilities/PVE-2024-74249/74249",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "licenseware": [
        {
            "advisory": "Licenseware 2.0.0 updates its dependency 'libexpat1' in the Dockerfile to include security fixes.\r\nhttps://github.com/licenseware/licenseware-sdk-v2/pull/59",
            "cve": "CVE-2022-25314",
            "id": "pyup.io-51855",
            "more_info_path": "/vulnerabilities/CVE-2022-25314/51855",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Licenseware 2.0.0 updates its dependency 'libexpat1' in the Dockerfile to include security fixes.\r\nhttps://github.com/licenseware/licenseware-sdk-v2/pull/59",
            "cve": "CVE-2022-43680",
            "id": "pyup.io-51851",
            "more_info_path": "/vulnerabilities/CVE-2022-43680/51851",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Licenseware 2.0.0 updates its dependency 'libexpat1' in the Dockerfile to include security fixes.\r\nhttps://github.com/licenseware/licenseware-sdk-v2/pull/59",
            "cve": "CVE-2022-25235",
            "id": "pyup.io-51854",
            "more_info_path": "/vulnerabilities/CVE-2022-25235/51854",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Licenseware 2.0.0 updates its dependency 'libexpat1' in the Dockerfile to include security fixes.\r\nhttps://github.com/licenseware/licenseware-sdk-v2/pull/59",
            "cve": "CVE-2022-25315",
            "id": "pyup.io-51857",
            "more_info_path": "/vulnerabilities/CVE-2022-25315/51857",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Licenseware 2.0.0 updates its dependency 'libexpat1' in the Dockerfile to include security fixes.\r\nhttps://github.com/licenseware/licenseware-sdk-v2/pull/59",
            "cve": "CVE-2022-25313",
            "id": "pyup.io-51856",
            "more_info_path": "/vulnerabilities/CVE-2022-25313/51856",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Licenseware 2.0.0 updates its dependency 'libexpat1' in the Dockerfile to include security fixes.\r\nhttps://github.com/licenseware/licenseware-sdk-v2/pull/59",
            "cve": "CVE-2022-25236",
            "id": "pyup.io-51853",
            "more_info_path": "/vulnerabilities/CVE-2022-25236/51853",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Licenseware 2.0.0 updates its dependency 'libexpat1' in the Dockerfile to include security fixes.\r\nhttps://github.com/licenseware/licenseware-sdk-v2/pull/59",
            "cve": "CVE-2022-40674",
            "id": "pyup.io-51852",
            "more_info_path": "/vulnerabilities/CVE-2022-40674/51852",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Licenseware 2.4.7 adds XSS/HTTPS security headers.\r\nhttps://github.com/licenseware/licenseware-sdk-v2/pull/310",
            "cve": "PVE-2022-52374",
            "id": "pyup.io-52374",
            "more_info_path": "/vulnerabilities/PVE-2022-52374/52374",
            "specs": [
                "<2.4.7"
            ],
            "v": "<2.4.7"
        }
    ],
    "lich": [
        {
            "advisory": "Affected versions of this package are vulnerable to Information Exposure due to improper handling of sensitive information. The vulnerability exists because the `run_act_workflow()` function in `cli/src/lich/commands/ci_utils.py` was injecting the `GITHUB_TOKEN` directly into the command line, which was then exposed in logs. An attacker with access to the logs could exploit this vulnerability to obtain the `GITHUB_TOKEN`, potentially allowing unauthorized access to GitHub repositories or actions.",
            "cve": "PVE-2026-84884",
            "id": "pyup.io-84884",
            "more_info_path": "/vulnerabilities/PVE-2026-84884/84884",
            "specs": [
                "<1.12.11"
            ],
            "v": "<1.12.11"
        }
    ],
    "lief": [
        {
            "advisory": "A heap-buffer-overflow exists in the function main located in pe_reader.c. It allows an attacker to cause code Execution.\r\nhttps://github.com/lief-project/LIEF/commit/19e06755e8ce1ecf136360a5c36cded3701ac253",
            "cve": "CVE-2021-32297",
            "id": "pyup.io-42313",
            "more_info_path": "/vulnerabilities/CVE-2021-32297/42313",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        },
        {
            "advisory": "LIEF commit 365a16a was discovered to contain a segmentation violation via the component CoreFile.tcc:69.",
            "cve": "CVE-2022-38497",
            "id": "pyup.io-54540",
            "more_info_path": "/vulnerabilities/CVE-2022-38497/54540",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "LIEF commit 365a16a was discovered to contain a heap-buffer overflow via the function print_binary at /c/macho_reader.c.",
            "cve": "CVE-2022-38495",
            "id": "pyup.io-54534",
            "more_info_path": "/vulnerabilities/CVE-2022-38495/54534",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "LIEF commit 5d1d643 was discovered to contain a segmentation violation via the function LIEF::MachO::SegmentCommand::file_offset() at /MachO/SegmentCommand.cpp.",
            "cve": "CVE-2022-38307",
            "id": "pyup.io-54538",
            "more_info_path": "/vulnerabilities/CVE-2022-38307/54538",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "A vulnerability in the LIEF::MachO::BinaryParser::init_and_parse function allows attackers to cause a denial of service (DOS) through a segmentation fault via a crafted MachO file. A [patch](https://github.com/lief-project/LIEF/commit/fde2c48986739fabd2cf9b40b9af149a89c57850) for this issue is available at commit fde2c48986739fabd2cf9b40b9af149a89c57850.",
            "cve": "CVE-2022-40922",
            "id": "pyup.io-54501",
            "more_info_path": "/vulnerabilities/CVE-2022-40922/54501",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "A bad macho file can lead LIEF::MachO::Parser::parse() to segmentation fault. That may open up for Denial of Service (Dos) attacks.\r\nhttps://github.com/lief-project/LIEF/issues/806",
            "cve": "PVE-2024-64373",
            "id": "pyup.io-64373",
            "more_info_path": "/vulnerabilities/PVE-2024-64373/64373",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "A heap buffer overflow in the LIEF::MachO::BinaryParser::parse_dyldinfo_generic_bind function allows attackers to cause a Denial of Service (DoS) via a crafted MachO file.\r\nhttps://github.com/lief-project/LIEF/issues/782\r\nhttps://github.com/lief-project/LIEF/commit/98d33929deb214caa0d91cd4ceb87ac93bac6e0b",
            "cve": "CVE-2022-43171",
            "id": "pyup.io-62770",
            "more_info_path": "/vulnerabilities/CVE-2022-43171/62770",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "A vulnerability in the LIEF::MachO::SegmentCommand::virtual_address function allows attackers to cause a denial of service (DOS) through a segmentation fault via a crafted MachO file.",
            "cve": "CVE-2022-40923",
            "id": "pyup.io-54500",
            "more_info_path": "/vulnerabilities/CVE-2022-40923/54500",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "LIEF commit 5d1d643 was discovered to contain a heap-buffer overflow in the component /core/CorePrPsInfo.tcc.",
            "cve": "CVE-2022-38306",
            "id": "pyup.io-54536",
            "more_info_path": "/vulnerabilities/CVE-2022-38306/54536",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "LIEF 0.13.0 fixes a reachable assertion abort via the component BinaryStream.hpp.\r\nhttps://github.com/lief-project/LIEF/issues/765\r\nhttps://github.com/lief-project/LIEF/commit/175c3fde3fe1e3e011d72cf0562a52034eaac43c",
            "cve": "CVE-2022-38496",
            "id": "pyup.io-62765",
            "more_info_path": "/vulnerabilities/CVE-2022-38496/62765",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Affected versions of the lief package are vulnerable to Information Disclosure due to the use of an uninitialized variable in the machd_reader.c component\u2019s name parameter. The machd_reader.c component accepts the name parameter without proper initialization, allowing leakage of potentially sensitive memory contents. A local attacker can exploit this by invoking the machd_reader functionality with a crafted name parameter, causing the LIEF package to disclose unintended information from process memory.",
            "cve": "CVE-2024-31636",
            "id": "pyup.io-78719",
            "more_info_path": "/vulnerabilities/CVE-2024-31636/78719",
            "specs": [
                "<0.15.0"
            ],
            "v": "<0.15.0"
        }
    ],
    "lifx-async": [
        {
            "advisory": "Affected versions of the `lifx-async` package are vulnerable to Race Condition due to improper synchronisation in concurrent request handling within the network module. The package fails to implement adequate locking mechanisms or atomic operations when processing simultaneous network requests, allowing multiple threads or coroutines to access and modify shared state concurrently without proper coordination. An attacker can exploit this by sending a high volume of carefully timed concurrent requests to trigger inconsistent state transitions, potentially leading to data corruption, unexpected behaviour, authentication bypass, or Denial of Service through resource exhaustion or application crashes.",
            "cve": "PVE-2025-81740",
            "id": "pyup.io-81740",
            "more_info_path": "/vulnerabilities/PVE-2025-81740/81740",
            "specs": [
                "<2.2.1"
            ],
            "v": "<2.2.1"
        }
    ],
    "lifx-control-panel": [
        {
            "advisory": "Lifx-control-panel 1.5.4 fixes a pretty major security exploit. It adds safe-scopes to all 'eval()' calls.\r\nhttps://github.com/samclane/LIFX-Control-Panel/commit/3f95fd5362b52144b44e47102ab386baa511f143",
            "cve": "PVE-2021-37424",
            "id": "pyup.io-37424",
            "more_info_path": "/vulnerabilities/PVE-2021-37424/37424",
            "specs": [
                "<1.5.4"
            ],
            "v": "<1.5.4"
        },
        {
            "advisory": "Lifx-control-panel 1.6.3 removes all 'eval()' statements for security.\r\nhttps://github.com/samclane/LIFX-Control-Panel/commit/feccb386549e25414f15b3ef4b85018d0a836125",
            "cve": "PVE-2021-37423",
            "id": "pyup.io-37423",
            "more_info_path": "/vulnerabilities/PVE-2021-37423/37423",
            "specs": [
                "<1.6.3"
            ],
            "v": "<1.6.3"
        },
        {
            "advisory": "Lifx-control-panel 1.7.6 pins its dependency 'numpy' to v1.18.1 to include security fixes.",
            "cve": "CVE-2014-1858",
            "id": "pyup.io-44966",
            "more_info_path": "/vulnerabilities/CVE-2014-1858/44966",
            "specs": [
                "<1.7.6"
            ],
            "v": "<1.7.6"
        },
        {
            "advisory": "Lifx-control-panel 1.7.6 pins its dependency 'numpy' to v1.18.1 to include security fixes.",
            "cve": "CVE-2017-12852",
            "id": "pyup.io-44965",
            "more_info_path": "/vulnerabilities/CVE-2017-12852/44965",
            "specs": [
                "<1.7.6"
            ],
            "v": "<1.7.6"
        },
        {
            "advisory": "Lifx-control-panel 1.7.6 pins its dependency 'numpy' to v1.18.1 to include security fixes.",
            "cve": "CVE-2014-1859",
            "id": "pyup.io-44964",
            "more_info_path": "/vulnerabilities/CVE-2014-1859/44964",
            "specs": [
                "<1.7.6"
            ],
            "v": "<1.7.6"
        },
        {
            "advisory": "Lifx-control-panel 1.7.6 pins its dependency 'numpy' to v1.18.1 to include security fixes.",
            "cve": "CVE-2019-6446",
            "id": "pyup.io-37853",
            "more_info_path": "/vulnerabilities/CVE-2019-6446/37853",
            "specs": [
                "<1.7.6"
            ],
            "v": "<1.7.6"
        }
    ],
    "light-the-torch": [
        {
            "advisory": "Light-the-torch 0.7.0 mitigates the risk of supply chain attacks.\r\nhttps://github.com/pmeier/light-the-torch/pull/115\r\nhttps://github.com/pmeier/light-the-torch/pull/118",
            "cve": "PVE-2023-52882",
            "id": "pyup.io-52882",
            "more_info_path": "/vulnerabilities/PVE-2023-52882/52882",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        }
    ],
    "lighteval": [
        {
            "advisory": "Bump nltlk to version = \"0.4.0.dev0\" on the lighteval package due to security vulnerability.",
            "cve": "CVE-2024-39705",
            "id": "pyup.io-73055",
            "more_info_path": "/vulnerabilities/CVE-2024-39705/73055",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "lightgbm": [
        {
            "advisory": "Affected versions of the lightgbm package are vulnerable to Remote Code Execution due to an unmitigated heap-based buffer overflow in its parsing logic. The internal data parsing routines in the lightgbm module fail to properly validate input buffer bounds, allowing excessive data to overwrite heap memory. An attacker able to supply a specially crafted input payload over the network can trigger arbitrary code execution within the lightgbm process, potentially compromising confidentiality, integrity, and availability of the host system.",
            "cve": "CVE-2024-43598",
            "id": "pyup.io-78808",
            "more_info_path": "/vulnerabilities/CVE-2024-43598/78808",
            "specs": [
                ">=1.0.0,<4.6.0"
            ],
            "v": ">=1.0.0,<4.6.0"
        }
    ],
    "lightning": [
        {
            "advisory": "Lightning 2.0.4 updates its dependency 'ipython' to version '8.14.0' to include a security fix.\r\nhttps://github.com/Lightning-AI/lightning/commit/98e1aabd0c711e508d33f599265de011ca5dfba8",
            "cve": "CVE-2023-24816",
            "id": "pyup.io-59170",
            "more_info_path": "/vulnerabilities/CVE-2023-24816/59170",
            "specs": [
                "<2.0.4"
            ],
            "v": "<2.0.4"
        },
        {
            "advisory": "Lightning 2.0.4 updates its dependency 'vite' to version '2.9.16' to include a security fix.\r\nhttps://github.com/Lightning-AI/lightning/commit/7d2a46efa9834c3bb0bc1069df0a2e3a6e855d01",
            "cve": "CVE-2022-35204",
            "id": "pyup.io-59185",
            "more_info_path": "/vulnerabilities/CVE-2022-35204/59185",
            "specs": [
                "<2.0.4"
            ],
            "v": "<2.0.4"
        },
        {
            "advisory": "Lightning 2.0.4 updates its dependency 'redis' to version '4.5.5' to include a security fix.\r\nhttps://github.com/Lightning-AI/lightning/commit/0831e138c02e492bdd384be99079d949c93b1e8e",
            "cve": "CVE-2023-28858",
            "id": "pyup.io-59186",
            "more_info_path": "/vulnerabilities/CVE-2023-28858/59186",
            "specs": [
                "<2.0.4"
            ],
            "v": "<2.0.4"
        },
        {
            "advisory": "Lightning 2.0.4 updates its dependency 'requests' to '2.31.0' to include a security fix.\r\nhttps://github.com/Lightning-AI/lightning/commit/37be44d2a3804dad52f0d4e4dcc5419bcb48391f",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-59187",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/59187",
            "specs": [
                "<2.0.4"
            ],
            "v": "<2.0.4"
        },
        {
            "advisory": "Lightning 2.0.4 updates its dependency 'vite' to version '2.9.16' to include a security fix.\r\nhttps://github.com/Lightning-AI/lightning/commit/7d2a46efa9834c3bb0bc1069df0a2e3a6e855d01",
            "cve": "CVE-2023-34092",
            "id": "pyup.io-59184",
            "more_info_path": "/vulnerabilities/CVE-2023-34092/59184",
            "specs": [
                "<2.0.4"
            ],
            "v": "<2.0.4"
        },
        {
            "advisory": "Affected versions of the PyTorch-Lightning package are vulnerable to Arbitrary File Overwrite due to improper validation during tar.gz extraction. The `/v1/runs` API endpoint in LightningApp with plugin_server enabled fails to sanitize file paths within uploaded tar.gz archives, allowing embedded files with directory traversal sequences to escape the intended extraction directory.",
            "cve": "CVE-2024-5980",
            "id": "pyup.io-72092",
            "more_info_path": "/vulnerabilities/CVE-2024-5980/72092",
            "specs": [
                "<2.3.3"
            ],
            "v": "<2.3.3"
        },
        {
            "advisory": "Affected versions of Lighting are vulnerable to remote code execution (RCE) due to improper handling of deserialized user input and mismanagement of dunder attributes by the deepdiff library. The library uses deepdiff.Delta objects to modify application state based on frontend actions. However, it is possible to bypass the intended restrictions on modifying dunder attributes, allowing an attacker to construct a serialized delta that passes the deserializer whitelist and contains dunder attributes. When processed, this can be exploited to access other modules, classes, and instances, leading to arbitrary attribute write and total RCE on any self-hosted pytorch-lightning application in its default configuration, as the delta endpoint is enabled by default.",
            "cve": "CVE-2024-5452",
            "id": "pyup.io-71939",
            "more_info_path": "/vulnerabilities/CVE-2024-5452/71939",
            "specs": [
                "<2.3.3"
            ],
            "v": "<2.3.3"
        }
    ],
    "lightrag-hku": [
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal due to insufficient validation of user-supplied filenames in file upload operations. The upload_to_input_dir() function fails to properly sanitize the file.filename parameter, leading to arbitrary file write outside the intended directory. An attacker can manipulate the filename parameter using directory traversal sequences to write files to unintended locations on the server filesystem.",
            "cve": "CVE-2025-6773",
            "id": "pyup.io-77943",
            "more_info_path": "/vulnerabilities/CVE-2025-6773/77943",
            "specs": [
                "<1.3.8"
            ],
            "v": "<1.3.8"
        }
    ],
    "lilac": [
        {
            "advisory": "Lilac 0.3.7 upgrades its pyarrow dependency to version ^13.0.0 from ^14.0.1 in response to CVE-2023-47248.\r\nhttps://github.com/lilacai/lilac/pull/1191/commits/493dd721e01019185fa62beb0c162286d24dbbbe",
            "cve": "CVE-2023-47248",
            "id": "pyup.io-65676",
            "more_info_path": "/vulnerabilities/CVE-2023-47248/65676",
            "specs": [
                "<0.3.7"
            ],
            "v": "<0.3.7"
        },
        {
            "advisory": "Lilac 0.3.7 upgrades its pillow dependency to version ^10.2.0 from ^9.3.0 in response to CVE-2023-50447.\r\nhttps://github.com/lilacai/lilac/pull/1191/commits/493dd721e01019185fa62beb0c162286d24dbbbe",
            "cve": "CVE-2023-50447",
            "id": "pyup.io-65642",
            "more_info_path": "/vulnerabilities/CVE-2023-50447/65642",
            "specs": [
                "<0.3.7"
            ],
            "v": "<0.3.7"
        }
    ],
    "lilya": [
        {
            "advisory": "Affected versions of lilya prior to 0.12.5 are potentially vulnerable to a path traversal attack (CWE-22).  The vulnerable functions were in the static file resolution logic (e.g., get_path and get_route_path in lilya/staticfiles.py).",
            "cve": "PVE-2025-75305",
            "id": "pyup.io-75305",
            "more_info_path": "/vulnerabilities/PVE-2025-75305/75305",
            "specs": [
                "<0.12.5"
            ],
            "v": "<0.12.5"
        }
    ],
    "liminal-sdk-python": [
        {
            "advisory": "Liminal-sdk-python 2024.03.0 fixes a race condition when refreshing the access token.\r\nhttps://github.com/liminal-ai-security/liminal-sdk-python/pull/66/commits/866a018f704d2947e62ab037c94771f47d14c8b0",
            "cve": "PVE-2024-66762",
            "id": "pyup.io-66762",
            "more_info_path": "/vulnerabilities/PVE-2024-66762/66762",
            "specs": [
                "<2024.03.0"
            ],
            "v": "<2024.03.0"
        },
        {
            "advisory": "Liminal-sdk-python 2024.09.0b1 updates its dependency 'cryptography' to include a security fix.",
            "cve": "CVE-2024-6119",
            "id": "pyup.io-73084",
            "more_info_path": "/vulnerabilities/CVE-2024-6119/73084",
            "specs": [
                "<2024.09.0b1"
            ],
            "v": "<2024.09.0b1"
        }
    ],
    "limnoria": [
        {
            "advisory": "Eval injection in the Math plugin of Limnoria (before 2019.11.09) and Supybot (through 2018-05-09) allows remote unprivileged attackers to disclose information or possibly have unspecified other impact via the calc and icalc IRC commands.",
            "cve": "CVE-2019-19010",
            "id": "pyup.io-42267",
            "more_info_path": "/vulnerabilities/CVE-2019-19010/42267",
            "specs": [
                "<2019.11.09"
            ],
            "v": "<2019.11.09"
        }
    ],
    "lin-cms": [
        {
            "advisory": "Cross Site Scripting (XSS) in Lin-CMS-Flask v0.1.1 allows remote attackers to execute arbitrary code by entering scripts in the 'Username' parameter of the in component 'app/api/cms/user.py' (https://github.com/TaleLin/lin-cms-flask/issues/28). See CVE-2020-18699.",
            "cve": "CVE-2020-18699",
            "id": "pyup.io-41183",
            "more_info_path": "/vulnerabilities/CVE-2020-18699/41183",
            "specs": [
                "<0.2.0b1"
            ],
            "v": "<0.2.0b1"
        },
        {
            "advisory": "Lin-CMS allows remote attackers to obtain sensitive information and/or gain privileges due to the application not invalidating a user's authentication token upon logout, which allows for replaying packets.\r\nhttps://github.com/TaleLin/lin-cms-flask/issues/30",
            "cve": "CVE-2020-18701",
            "id": "pyup.io-41184",
            "more_info_path": "/vulnerabilities/CVE-2020-18701/41184",
            "specs": [
                ">0"
            ],
            "v": ">0"
        },
        {
            "advisory": "Lin-CMS allows remote attackers to launch brute force login attempts without restriction via the 'login' function in the component 'app/api/cms/user.py'.\r\nhttps://github.com/TaleLin/lin-cms-flask/issues/27",
            "cve": "CVE-2020-18698",
            "id": "pyup.io-41182",
            "more_info_path": "/vulnerabilities/CVE-2020-18698/41182",
            "specs": [
                ">0"
            ],
            "v": ">0"
        },
        {
            "advisory": "An authentication bypass in Lin-CMS v0.2.1 allows attackers to escalate privileges to Super Administrator.",
            "cve": "CVE-2022-44244",
            "id": "pyup.io-54558",
            "more_info_path": "/vulnerabilities/CVE-2022-44244/54558",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "lin-cms-flask": [
        {
            "advisory": "Lin-CMS-flask allows remote attackers to obtain sensitive information and/or gain privileges due to the application not invalidating a user's authentication token upon logout, which allows for replaying packets.\r\nhttps://github.com/TaleLin/lin-cms-flask/issues/30",
            "cve": "CVE-2020-18701",
            "id": "pyup.io-45615",
            "more_info_path": "/vulnerabilities/CVE-2020-18701/45615",
            "specs": [
                ">0"
            ],
            "v": ">0"
        },
        {
            "advisory": "Lin-CMS-flask allows remote attackers to launch brute force login attempts without restriction via the 'login' function in the component 'app/api/cms/user.py'.\r\nhttps://github.com/TaleLin/lin-cms-flask/issues/27",
            "cve": "CVE-2020-18698",
            "id": "pyup.io-45611",
            "more_info_path": "/vulnerabilities/CVE-2020-18698/45611",
            "specs": [
                ">0"
            ],
            "v": ">0"
        },
        {
            "advisory": "Cross Site Scripting (XSS) in Lin-CMS-Flask allows remote attackers to execute arbitrary code by entering scripts in the the 'Username' parameter of the in component 'app/api/cms/user.py'.\r\nhttps://github.com/TaleLin/lin-cms-flask/issues/28",
            "cve": "CVE-2020-18699",
            "id": "pyup.io-45607",
            "more_info_path": "/vulnerabilities/CVE-2020-18699/45607",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "line-bot-sdk": [
        {
            "advisory": "Line-bot-sdk 3.2.0 updates its dependency 'aiohttp' to version '3.8.5' to include a fix for an HTTP Request Smuggling vulnerability.\r\nhttps://github.com/line/line-bot-sdk-python/pull/491",
            "cve": "CVE-2023-37276",
            "id": "pyup.io-60194",
            "more_info_path": "/vulnerabilities/CVE-2023-37276/60194",
            "specs": [
                "<3.2.0"
            ],
            "v": "<3.2.0"
        }
    ],
    "line-item-manager": [
        {
            "advisory": "Line-item-manager 0.2.2 updates its dependency 'jinja2' to v2.11.3 to include a security fix.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-40555",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/40555",
            "specs": [
                "<0.2.2"
            ],
            "v": "<0.2.2"
        },
        {
            "advisory": "Line-item-manager 0.2.2 updates its dependency 'pyyaml' requirements to >=5.4 to include a security fix.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-49006",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/49006",
            "specs": [
                "<0.2.2"
            ],
            "v": "<0.2.2"
        }
    ],
    "lingfo": [
        {
            "advisory": "Lingfo 0.2.4 updates its dependency 'gitpython' to version '3.1.32' to include a fix for a Remote Code Execution vulnerability.\r\nhttps://github.com/lingfo/lingfo/commit/4f571a7c3ded9b1775e5b741c48c49e6510b7a8f",
            "cve": "CVE-2023-40267",
            "id": "pyup.io-60413",
            "more_info_path": "/vulnerabilities/CVE-2023-40267/60413",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        }
    ],
    "linkml": [
        {
            "advisory": "Linkml 1.5.2 introduces critical security enhancements to mitigate potential code injection vulnerabilities, specifically by refining the pydanticgen/pythongen modules. These improvements address the handling of quotes and multiline descriptions in enum fields, ensuring safer processing of descriptions and preventing malicious code execution. \r\nhttps://github.com/linkml/linkml/pull/1402",
            "cve": "PVE-2024-63769",
            "id": "pyup.io-63769",
            "more_info_path": "/vulnerabilities/PVE-2024-63769/63769",
            "specs": [
                "<1.5.2"
            ],
            "v": "<1.5.2"
        }
    ],
    "linotp": [
        {
            "advisory": "KeyIdentity LinOTP before 2.10.5.3 has Incorrect Access Control (issue 1 of 2).",
            "cve": "CVE-2019-12887",
            "id": "pyup.io-54210",
            "more_info_path": "/vulnerabilities/CVE-2019-12887/54210",
            "specs": [
                ">=0,<2.11.1"
            ],
            "v": ">=0,<2.11.1"
        }
    ],
    "lintegrate": [
        {
            "advisory": "Lintegrate 0.1.11 updates its dependency 'numpy' to versions '>=1.21' to include security fixes.",
            "cve": "CVE-2021-33430",
            "id": "pyup.io-44758",
            "more_info_path": "/vulnerabilities/CVE-2021-33430/44758",
            "specs": [
                "<0.1.11"
            ],
            "v": "<0.1.11"
        },
        {
            "advisory": "Lintegrate 0.1.11 updates its dependency 'numpy' to v>=1.21 to include security fixes.",
            "cve": "CVE-2019-6446",
            "id": "pyup.io-44709",
            "more_info_path": "/vulnerabilities/CVE-2019-6446/44709",
            "specs": [
                "<0.1.11"
            ],
            "v": "<0.1.11"
        },
        {
            "advisory": "Lintegrate 0.1.11 updates its dependency 'numpy' to v>=1.21 to include security fixes.",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-44757",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/44757",
            "specs": [
                "<0.1.11"
            ],
            "v": "<0.1.11"
        },
        {
            "advisory": "Lintegrate 0.1.11 may use a vulnerable version of Numpy: >=1.21.0",
            "cve": "CVE-2021-41496",
            "id": "pyup.io-44759",
            "more_info_path": "/vulnerabilities/CVE-2021-41496/44759",
            "specs": [
                "<=0.1.11"
            ],
            "v": "<=0.1.11"
        }
    ],
    "lionagi": [
        {
            "advisory": "Lionagi 0.0.102 updates its dependency package aiohttp version from 3.8.6 to 3.9.0 to include security fixes due to the CVE-2023-49081.\r\nhttps://github.com/lion-agi/lionagi/pull/41",
            "cve": "CVE-2023-49081",
            "id": "pyup.io-62747",
            "more_info_path": "/vulnerabilities/CVE-2023-49081/62747",
            "specs": [
                "<0.0.102"
            ],
            "v": "<0.0.102"
        },
        {
            "advisory": "Lionagi 0.0.102 updates its dependency package aiohttp version from 3.8.6 to 3.9.0 to include security fixes due to the CVE-2023-49082.\r\nhttps://github.com/lion-agi/lionagi/pull/41/files\r\nhttps://nvd.nist.gov/vuln/detail/CVE-2023-49082",
            "cve": "CVE-2023-49082",
            "id": "pyup.io-62999",
            "more_info_path": "/vulnerabilities/CVE-2023-49082/62999",
            "specs": [
                "<0.0.102"
            ],
            "v": "<0.0.102"
        }
    ],
    "litdb": [
        {
            "advisory": "Affected versions of the litdb package are vulnerable to Remote Code Execution due to unsafe use of Python\u2019s eval() when parsing default values in the schema DSL. The parse_schema_dsl function in src/litdb/extract.py evaluated the user-controlled default_str via eval without validation, enabling arbitrary Python expressions to be executed during schema parsing; the fixing commit replaces eval with ast.literal_eval for safe literal parsing.",
            "cve": "PVE-2025-80971",
            "id": "pyup.io-80971",
            "more_info_path": "/vulnerabilities/PVE-2025-80971/80971",
            "specs": [
                "<2.1.9"
            ],
            "v": "<2.1.9"
        }
    ],
    "litellm": [
        {
            "advisory": "Litellm version 1.35.1.dev1 introduces a low-severity security fix by disabling demo accounts on the Admin UI. Previously, the Proxy used a hardcoded demo account with no permissions, posing a potential security risk.",
            "cve": "PVE-2024-67612",
            "id": "pyup.io-67612",
            "more_info_path": "/vulnerabilities/PVE-2024-67612/67612",
            "specs": [
                "<1.35.1.dev1"
            ],
            "v": "<1.35.1.dev1"
        },
        {
            "advisory": "Affected versions of Litellm are vulnerable to improper authorization. Users could remove files from litellm proxy server when calling  /audio/transcriptions.",
            "cve": "PVE-2024-68072",
            "id": "pyup.io-68072",
            "more_info_path": "/vulnerabilities/PVE-2024-68072/68072",
            "specs": [
                "<1.35.18"
            ],
            "v": "<1.35.18"
        },
        {
            "advisory": "Affected versions of BerriAI's litellm are vulnerable to arbitrary file deletion due to improper input validation on the `/audio/transcriptions` endpoint. An attacker can exploit this vulnerability by sending a specially crafted request that includes a file path to the server, which then deletes the specified file without proper authorization or validation. This vulnerability is present in the code where `os.remove(file.filename)` is used to delete a file, allowing any user to delete critical files on the server such as SSH keys, SQLite databases, or configuration files.",
            "cve": "CVE-2024-4888",
            "id": "pyup.io-71651",
            "more_info_path": "/vulnerabilities/CVE-2024-4888/71651",
            "specs": [
                "<1.35.18"
            ],
            "v": "<1.35.18"
        },
        {
            "advisory": "Litellm version 1.35.20.dev2 resolves an issue where users could inadvertently delete files from the Litellm proxy server when accessing the `/audio/transcriptions` endpoint.",
            "cve": "PVE-2024-69610",
            "id": "pyup.io-69610",
            "more_info_path": "/vulnerabilities/PVE-2024-69610/69610",
            "specs": [
                "<1.35.20.dev2"
            ],
            "v": "<1.35.20.dev2"
        },
        {
            "advisory": "berriai/litellm affected versions are vulnerable to improper access control in their team management functionality. This vulnerability allows attackers to perform unauthorized actions such as creating, updating, viewing, deleting, blocking, and unblocking any team, as well as adding or deleting any member to or from any teams. The vulnerability stems from insufficient access control checks in various team management endpoints, enabling attackers to exploit these functionalities without proper authorization.",
            "cve": "CVE-2024-5710",
            "id": "pyup.io-71848",
            "more_info_path": "/vulnerabilities/CVE-2024-5710/71848",
            "specs": [
                "<1.40.29"
            ],
            "v": "<1.40.29"
        },
        {
            "advisory": "Affected version of Litellm are affected by a information disclosure vulnerability. Sensitive information was logged in raw request debug logs.",
            "cve": "PVE-2024-71424",
            "id": "pyup.io-71424",
            "more_info_path": "/vulnerabilities/PVE-2024-71424/71424",
            "specs": [
                "<1.40.6"
            ],
            "v": "<1.40.6"
        },
        {
            "advisory": "Affected versions of berriai/litellm contains a Remote Code Execution (RCE) vulnerability (CWE-94) in the secret management system, particularly when using Google KMS. The litellm.get_secret() method used the eval() function unsafely on unsanitized input from environment variables, which could be manipulated through the /config/update endpoint. This allowed attackers to inject and execute arbitrary code by updating settings in proxy_server_config.yaml. The vulnerability has been addressed by replacing the unsafe eval() call with a secure client.decrypt() method for handling encrypted data.",
            "cve": "CVE-2024-4264",
            "id": "pyup.io-71722",
            "more_info_path": "/vulnerabilities/CVE-2024-4264/71722",
            "specs": [
                "<1.44.16"
            ],
            "v": "<1.44.16"
        },
        {
            "advisory": "Affected versions of berriai/litellm contain a Code Injection vulnerability (CWE-94) in the secret management system when using Google KMS. Attackers could potentially execute arbitrary code by manipulating environment variables, exploiting the use of eval() on unvalidated input. This vulnerability has been addressed by replacing eval() with a secure client.decrypt() method for handling encrypted data.",
            "cve": "CVE-2024-4889",
            "id": "pyup.io-71720",
            "more_info_path": "/vulnerabilities/CVE-2024-4889/71720",
            "specs": [
                "<1.44.16"
            ],
            "v": "<1.44.16"
        },
        {
            "advisory": "Affected versions of Litellm are vulnerable to blind SQL Injection. This vulnerability in the '/team/update' endpoint allows attackers to inject malicious SQL commands through the 'user_id' parameter, potentially leading to unauthorized access to sensitive data including API keys, user information, and tokens. The flaw stems from improper handling of user input in raw SQL queries. The patch replaces vulnerable raw SQL queries with parameterized queries using Prisma ORM, effectively preventing SQL injection attacks.",
            "cve": "CVE-2024-4890",
            "id": "pyup.io-71721",
            "more_info_path": "/vulnerabilities/CVE-2024-4890/71721",
            "specs": [
                "<1.44.17"
            ],
            "v": "<1.44.17"
        },
        {
            "advisory": "Affected versions of the litellm package are vulnerable to Information Disclosure due to improper error handling in team settings parsing. The proxy_server.py module exposes sensitive Langfuse API keys, including langfuse_secret and langfuse_public_key, in error messages when team settings parsing fails.",
            "cve": "CVE-2025-0330",
            "id": "pyup.io-76182",
            "more_info_path": "/vulnerabilities/CVE-2025-0330/76182",
            "specs": [
                "<1.52.1"
            ],
            "v": "<1.52.1"
        },
        {
            "advisory": "A vulnerability in BerriAI/litellm, as of commit 26c03c9, allows unauthenticated users to cause a Denial of Service (DoS) by exploiting the use of ast.literal_eval to parse user input. This function is not safe and is prone to DoS attacks, which can crash the litellm Python server.",
            "cve": "CVE-2024-10188",
            "id": "pyup.io-76299",
            "more_info_path": "/vulnerabilities/CVE-2024-10188/76299",
            "specs": [
                "<1.53.1.dev1"
            ],
            "v": "<1.53.1.dev1"
        },
        {
            "advisory": "LiteLLM has addressed the security vulnerability CVE-2024-22020 by updating the Node.js Docker image from version 20.11.0 to 20.18.1.",
            "cve": "CVE-2024-22020",
            "id": "pyup.io-74713",
            "more_info_path": "/vulnerabilities/CVE-2024-22020/74713",
            "specs": [
                "<1.55.8"
            ],
            "v": "<1.55.8"
        },
        {
            "advisory": "Litellm 1.56.2 updates its dependency 'cryptography' to include a security fix.",
            "cve": "CVE-2024-6119",
            "id": "pyup.io-74775",
            "more_info_path": "/vulnerabilities/CVE-2024-6119/74775",
            "specs": [
                "<1.56.2"
            ],
            "v": "<1.56.2"
        },
        {
            "advisory": "A Denial of Service (DoS) vulnerability exists in berriai/litellm version v1.44.5. This vulnerability can be exploited by appending characters, such as dashes (-), to the end of a multipart boundary in an HTTP request. The server continuously processes each character, leading to excessive resource consumption and rendering the service unavailable. The issue is unauthenticated and does not require any user interaction, impacting all users of the service.",
            "cve": "CVE-2024-8984",
            "id": "pyup.io-76200",
            "more_info_path": "/vulnerabilities/CVE-2024-8984/76200",
            "specs": [
                "<1.56.2"
            ],
            "v": "<1.56.2"
        },
        {
            "advisory": "A sensitive security token was inadvertently exposed in the Hugging Face models metadata file (CWE-200: Exposure of Sensitive Information), risking unauthorized access. Litellm fixing it by removing the token-containing entry, preventing potential misuse.",
            "cve": "PVE-2025-75075",
            "id": "pyup.io-75075",
            "more_info_path": "/vulnerabilities/PVE-2025-75075/75075",
            "specs": [
                "<1.58.4.dev1"
            ],
            "v": "<1.58.4.dev1"
        },
        {
            "advisory": "Litellm fixes a vulnerability where a user could update another user's keys.",
            "cve": "PVE-2025-75331",
            "id": "pyup.io-75331",
            "more_info_path": "/vulnerabilities/PVE-2025-75331/75331",
            "specs": [
                "<1.60.2dev1"
            ],
            "v": "<1.60.2dev1"
        },
        {
            "advisory": "Litellm 1.61.20 includes a security fix: Enforce model access restrictions on Azure OpenAI route.",
            "cve": "PVE-2025-75701",
            "id": "pyup.io-75701",
            "more_info_path": "/vulnerabilities/PVE-2025-75701/75701",
            "specs": [
                "<1.61.20"
            ],
            "v": "<1.61.20"
        },
        {
            "advisory": "Affected versions of the spend_management_endpoints.py were potentially vulnerable to SQL Injection (CWE-89). An attacker could potentially inject malicious SQL code through unsanitized input, leading to unauthorized data access or manipulation. The issue exists in the spend_management_endpoints.py.",
            "cve": "PVE-2025-76916",
            "id": "pyup.io-76916",
            "more_info_path": "/vulnerabilities/PVE-2025-76916/76916",
            "specs": [
                "<1.67.3.dev1"
            ],
            "v": "<1.67.3.dev1"
        },
        {
            "advisory": "Litellm Fixes potential SQL Injection in spend_management_endpoints.py.",
            "cve": "PVE-2025-77064",
            "id": "pyup.io-77064",
            "more_info_path": "/vulnerabilities/PVE-2025-77064/77064",
            "specs": [
                "<1.67.6.dev1"
            ],
            "v": "<1.67.6.dev1"
        },
        {
            "advisory": "Affected versions of the litellm package are vulnerable to Improper Access Control due to incomplete role-based authorization checks on management routes. The _check_proxy_admin_viewer_access function in litellm/proxy/auth/route_checks.py did not consistently block write operations for the PROXY_ADMIN_VIEW_ONLY role on endpoints such as /key/generate, /key/update, and user/team/model routes, and management_endpoints/internal_user_endpoints._update_single_user_helper lacked a can_user_call_user_update guard to restrict updates to self or PROXY_ADMIN.",
            "cve": "PVE-2025-79445",
            "id": "pyup.io-79445",
            "more_info_path": "/vulnerabilities/PVE-2025-79445/79445",
            "specs": [
                "<1.76.3.dev1"
            ],
            "v": "<1.76.3.dev1"
        },
        {
            "advisory": "Affected versions of the litellm package are vulnerable to Information Disclosure due to missing authentication on sensitive in-memory cache debug endpoints. The /memory-usage-in-mem-cache and /memory-usage-in-mem-cache-items routes in litellm/proxy/common_utils/debug_utils.py lacked the Depends(user_api_key_auth) check and were not initially listed under master_key_only_routes in litellm/proxy/_types.py, which permitted unauthenticated inspection of cache information.",
            "cve": "PVE-2025-79446",
            "id": "pyup.io-79446",
            "more_info_path": "/vulnerabilities/PVE-2025-79446/79446",
            "specs": [
                "<1.76.3.rc.1"
            ],
            "v": "<1.76.3.rc.1"
        },
        {
            "advisory": "Affected versions of the litellm package are potentially vulnerable to Information Disclosure due to the insertion of JWT SSO tokens and other credentials into info-level log messages. In litellm/proxy/management_endpoints/ui_sso.py (get_redirect_response_from_openid) and litellm/proxy/pass_through_endpoints/pass_through_endpoints.py (forward_upstream_to_client), logger.info statements recorded jwt_token and related authentication data in plaintext, a logging behaviour the project explicitly fixed and added tests for in tests/code_coverage_tests/info_log_check.py.",
            "cve": "PVE-2025-80130",
            "id": "pyup.io-80130",
            "more_info_path": "/vulnerabilities/PVE-2025-80130/80130",
            "specs": [
                "<1.77.7.rc.1"
            ],
            "v": "<1.77.7.rc.1"
        },
        {
            "advisory": "Affected versions of the litellm package before 69a464f are potentially vulnerable to Information Disclosure due to incomplete masking of Oracle Cloud Infrastructure (OCI) secret fields in responses from the /models and /v1/models endpoints. The proxy\u2019s model-listing path serializes the litellm_params structure and, before this change, remove_sensitive_info_from_deployment in proxy/common_utils/openai_endpoint_utils.py did not run SensitiveDataMasker.mask_dict on OCI-specific keys (for example key, tenancy, fingerprint, and key_file), causing those secrets to be returned unredacted.",
            "cve": "PVE-2025-80100",
            "id": "pyup.io-80100",
            "more_info_path": "/vulnerabilities/PVE-2025-80100/80100",
            "specs": [
                "<1.77.7.rc.1"
            ],
            "v": "<1.77.7.rc.1"
        },
        {
            "advisory": "Affected versions of the litellm package are vulnerable to sensitive information exposure due to improper masking of raw request headers on /health endpoint failures.",
            "cve": "PVE-2025-83104",
            "id": "pyup.io-83104",
            "more_info_path": "/vulnerabilities/PVE-2025-83104/83104",
            "specs": [
                "<1.80.10.dev.1"
            ],
            "v": "<1.80.10.dev.1"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to information disclosure due to improper handling of expired keys. The vulnerability exists because expired key plaintexts were being leaked in error responses. An attacker could exploit this vulnerability by triggering error responses that inadvertently reveal sensitive expired key information, potentially leading to unauthorized access or misuse of the disclosed keys.",
            "cve": "PVE-2026-84371",
            "id": "pyup.io-84371",
            "more_info_path": "/vulnerabilities/PVE-2026-84371/84371",
            "specs": [
                "<1.80.15.rc.1"
            ],
            "v": "<1.80.15.rc.1"
        },
        {
            "advisory": "Affected versions of the litellm package are vulnerable to Server-Side Request Forgery (SSRF) attacks due to insufficient validation of request body parameters. The api_base and base_url fields in POST /chat/completions requests are not properly restricted, allowing attackers to redirect server-side API calls to attacker-controlled domains.\r\nThis vulnerability permits malicious users to exfiltrate sensitive data\u2014including OpenAI API keys\u2014by proxying requests through untrusted endpoints. Exploitation may result in unauthorized access to third-party services, data leakage, or misuse of exposed secrets.\r\n\r\n**Advisory Correction Notice:**\r\nThe original advisory states that this vulnerability was fixed in version v1.44.8. However, following a thorough analysis, Safety\u2019s Cyber Research team has confirmed that a fix for this vulnerability is actually available in versions v1.44.9 and onwards. The fix was introduced in the following [commit](https://github.com/BerriAI/litellm/commit/ba1912afd1b19e38d3704bb156adf887f91ae1e0). This corrects the version information implied by the original advisory.",
            "cve": "CVE-2024-6587",
            "id": "pyup.io-73303",
            "more_info_path": "/vulnerabilities/CVE-2024-6587/73303",
            "specs": [
                ">=0.1.769,<1.44.9"
            ],
            "v": ">=0.1.769,<1.44.9"
        },
        {
            "advisory": "BerriAI/litellm is vulnerable to Server-Side Template Injection (SSTI) via the /completions endpoint. The vulnerability arises from the hf_chat_template method processing the chat_template parameter from the tokenizer_config.json file through the Jinja template engine without proper sanitization. Attackers can exploit this by crafting malicious tokenizer_config.json files that execute arbitrary code on the server.",
            "cve": "CVE-2024-2952",
            "id": "pyup.io-71650",
            "more_info_path": "/vulnerabilities/CVE-2024-2952/71650",
            "specs": [
                ">=0.1.805,<1.34.42",
                ">=1.35.0.dev1,<1.35.0"
            ],
            "v": ">=0.1.805,<1.34.42,>=1.35.0.dev1,<1.35.0"
        },
        {
            "advisory": "Affected versions of the litellm package are vulnerable to Remote Code Execution due to unsafe evaluation of decrypted environment variables. The `add_deployment` function in litellm versions before 1.40.16 decodes and decrypts base64-encoded values using Google KMS, then assigns them directly to `os.environ` without sanitization, enabling injection of malicious code. A remote attacker can exploit this by sending a crafted payload via the `/config/update` endpoint, triggering `get_secret` and executing arbitrary code in the litellm process with full privileges.",
            "cve": "CVE-2024-5751",
            "id": "pyup.io-78734",
            "more_info_path": "/vulnerabilities/CVE-2024-5751/78734",
            "specs": [
                ">=1.15.10,<1.40.16"
            ],
            "v": ">=1.15.10,<1.40.16"
        },
        {
            "advisory": "Affected versions of the litellm package are vulnerable to SQL Injection attacks due to improper input sanitization. The /global/spend/logs endpoint constructs an SQL query by directly concatenating the unvalidated api_key parameter into the query string without escaping or parameterization. This allows attackers to inject arbitrary SQL code by supplying specially crafted input through the api_key parameter. Successful exploitation may lead to unauthorized data access, manipulation of database contents, exposure of sensitive information, or a Denial of Service (DoS) condition.",
            "cve": "CVE-2024-5225",
            "id": "pyup.io-71723",
            "more_info_path": "/vulnerabilities/CVE-2024-5225/71723",
            "specs": [
                ">=1.28.3,<1.40.0"
            ],
            "v": ">=1.28.3,<1.40.0"
        },
        {
            "advisory": "Affected versions of the litellm package are vulnerable to Information Disclosure due to improper redaction of API keys in logging output. The litellm_logging.py file within the litellm_core_utils module attempts to mask API keys but only obfuscates the first five characters, inadvertently exposing nearly the entire key in logs.\r\nThis vulnerability can be exploited when API requests are logged by the application, leaking sensitive credentials to log files and increasing the risk of unauthorized access if the logs are accessed by an attacker or improperly secured.",
            "cve": "CVE-2024-9606",
            "id": "pyup.io-76190",
            "more_info_path": "/vulnerabilities/CVE-2024-9606/76190",
            "specs": [
                ">=1.34.33,<1.44.12"
            ],
            "v": ">=1.34.33,<1.44.12"
        },
        {
            "advisory": "BerriAI/litellm version 1.40.12 contains a vulnerability that allows remote code execution. The issue exists in the handling of the 'postcallrules' configuration, where a callback function can be added. The provided value is split at the final '.' mark, with the last part considered the function name and the remaining part appended with the '.py' extension and imported. This allows an attacker to set a system method, such as 'os.system', as a callback, enabling the execution of arbitrary commands when a chat response is processed.",
            "cve": "CVE-2024-6825",
            "id": "pyup.io-76239",
            "more_info_path": "/vulnerabilities/CVE-2024-6825/76239",
            "specs": [
                ">=1.40.3.dev2,<1.40.12"
            ],
            "v": ">=1.40.3.dev2,<1.40.12"
        },
        {
            "advisory": "An improper authorization vulnerability exists in the main-latest version of BerriAI/litellm. When a user with the role 'internal_user_viewer' logs into the application, they are provided with an overly privileged API key. This key can be used to access all the admin functionality of the application, including endpoints such as '/users/list' and '/users/get_users'. This vulnerability allows for privilege escalation within the application, enabling any account to become a PROXY ADMIN.",
            "cve": "CVE-2025-0628",
            "id": "pyup.io-76183",
            "more_info_path": "/vulnerabilities/CVE-2025-0628/76183",
            "specs": [
                ">=1.60.2,<1.61.15"
            ],
            "v": ">=1.60.2,<1.61.15"
        }
    ],
    "litestar": [
        {
            "advisory": "Affected versions of the litestar package are vulnerable to Denial of Service (DoS) due to unbounded memory allocation when parsing request bodies. The Request methods for parsing JSON, msgpack, and form-data content types use `await self.body()` to read the entire request stream into memory without implementing size limits or validation checks, while the multipart parser expects the complete request body as a single byte string by design. An attacker can exploit this vulnerability by sending extremely large requests with matching content types (such as using `curl -F \"foo==2.0.0a3,<=2.8.2"
            ],
            "v": ">=2.0.0a3,<=2.8.2"
        }
    ],
    "litestar-vite": [
        {
            "advisory": "Affected versions of the litestar-vite package are vulnerable to open redirect due to missing same-origin validation on redirect targets. The InertiaBack redirect logic trusts the Referer header and InertiaRedirect accepts a redirect_to parameter without validating that the resulting URL is same-origin/relative, which was addressed by adding a _get_redirect_url() validator in fix commit 5fbdf3248b193ea852cb4454305f8b708c9f9340.",
            "cve": "PVE-2025-83126",
            "id": "pyup.io-83126",
            "more_info_path": "/vulnerabilities/PVE-2025-83126/83126",
            "specs": [
                "<0.15.0"
            ],
            "v": "<0.15.0"
        },
        {
            "advisory": "Affected versions of the litestar-vite package are vulnerable to sensitive information exposure due to echoing request cookies into redirect responses. The redirect response classes in the Inertia integration previously passed cookies=request.cookies, causing client cookies to be reflected via response cookie handling.",
            "cve": "PVE-2025-83160",
            "id": "pyup.io-83160",
            "more_info_path": "/vulnerabilities/PVE-2025-83160/83160",
            "specs": [
                "<0.15.0"
            ],
            "v": "<0.15.0"
        }
    ],
    "lithops": [
        {
            "advisory": "Lithops 1.0.1 fixes a flask security issue. See: CVE-2018-1000656.",
            "cve": "CVE-2018-1000656",
            "id": "pyup.io-38787",
            "more_info_path": "/vulnerabilities/CVE-2018-1000656/38787",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        },
        {
            "advisory": "Lithops 1.0.19 fixes a CVE-2019-12855 security alert.",
            "cve": "CVE-2019-12855",
            "id": "pyup.io-38786",
            "more_info_path": "/vulnerabilities/CVE-2019-12855/38786",
            "specs": [
                "<1.0.19"
            ],
            "v": "<1.0.19"
        }
    ],
    "livefyre": [
        {
            "advisory": "livefyre before 2.0.3 uses a release of a transitive dependency with known security vulnerabilities  (PyJWT).",
            "cve": "PVE-2021-34170",
            "id": "pyup.io-34170",
            "more_info_path": "/vulnerabilities/PVE-2021-34170/34170",
            "specs": [
                "<2.0.3"
            ],
            "v": "<2.0.3"
        }
    ],
    "llama-agi": [
        {
            "advisory": "llama-agi 0.2.0 and prior versions ship with vulnerable dependencies (llama-index\r\n == 0.6.13).",
            "cve": "CVE-2023-39662",
            "id": "pyup.io-65040",
            "more_info_path": "/vulnerabilities/CVE-2023-39662/65040",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "llama-cpp-python": [
        {
            "advisory": "Llama-cpp-python 0.2.12 includes a fix for an Arbitrary Code Execution vulnerability.\r\nhttps://github.com/abetlen/llama-cpp-python/pull/854",
            "cve": "PVE-2023-62135",
            "id": "pyup.io-62135",
            "more_info_path": "/vulnerabilities/PVE-2023-62135/62135",
            "specs": [
                "<0.2.12"
            ],
            "v": "<0.2.12"
        },
        {
            "advisory": "Llama-cpp-python version 0.2.72 enhances security by updating all remaining Jinja chat templates to use an immutable sandbox.",
            "cve": "PVE-2024-70929",
            "id": "pyup.io-70929",
            "more_info_path": "/vulnerabilities/PVE-2024-70929/70929",
            "specs": [
                "<0.2.72"
            ],
            "v": "<0.2.72"
        },
        {
            "advisory": "Llama-cpp-python version 0.2.72 addresses a security issue by fixing a Remote Code Execution vulnerability caused by Server-Side Template Injection in Model Metadata.",
            "cve": "CVE-2024-34359",
            "id": "pyup.io-70912",
            "more_info_path": "/vulnerabilities/CVE-2024-34359/70912",
            "specs": [
                ">=0.2.30,<=0.2.71"
            ],
            "v": ">=0.2.30,<=0.2.71"
        }
    ],
    "llama-hub": [
        {
            "advisory": "The OpenAPI and ChatGPT plugin loaders in LlamaHub (aka llama-hub) before 0.0.67 allow attackers to execute arbitrary code because safe_load is not used for YAML.",
            "cve": "CVE-2024-23730",
            "id": "pyup.io-66690",
            "more_info_path": "/vulnerabilities/CVE-2024-23730/66690",
            "specs": [
                "<0.0.67"
            ],
            "v": "<0.0.67"
        }
    ],
    "llama-index": [
        {
            "advisory": "A command injection vulnerability exists in the RunGptLLM class of the llama_index library, version 0.9.47, used by the RunGpt framework from JinaAI to connect to Language Learning Models (LLMs). The vulnerability arises from the improper use of the eval function, allowing a malicious or compromised LLM hosting provider to execute arbitrary commands on the client's machine. This issue was fixed in version 0.10.13. The exploitation of this vulnerability could lead to a hosting provider gaining full control over client machines.",
            "cve": "CVE-2024-4181",
            "id": "pyup.io-71793",
            "more_info_path": "/vulnerabilities/CVE-2024-4181/71793",
            "specs": [
                "<0.10.13"
            ],
            "v": "<0.10.13"
        },
        {
            "advisory": "Affected versions of the LlamaIndex package are vulnerable to SQL Injection across multiple vector store integrations. The vulnerability affects ClickHouse, Couchbase, DeepLake, Jaguar, Lantern, Nile, OracleDB, and SingleStoreDB vector stores, where user-controlled input is not properly sanitized before being incorporated into SQL queries. \r\n\r\nA remote attacker can exploit this vulnerability by injecting malicious SQL commands through various vector store operations, particularly the delete() method, resulting in unauthorized read and write access to database content, potentially compromising data of other users in multi-tenant applications.\r\n\r\nThe vulnerability was fixed by implementing input sanitization across all affected vector stores. The fix varies by implementation: OracleDB uses a whitelist approach for allowed characters, while others implement blacklist-based filtering.",
            "cve": "CVE-2025-1793",
            "id": "pyup.io-77685",
            "more_info_path": "/vulnerabilities/CVE-2025-1793/77685",
            "specs": [
                "<0.12.28"
            ],
            "v": "<0.12.28"
        },
        {
            "advisory": "Affected versions of the llama_index package are vulnerable to SQL Injection due to improper input sanitization in the prompt processing mechanism. The default_jsonalyzer function within the JSONalyzeQueryEngine component fails to adequately validate user-supplied prompts before incorporating them into SQL queries, enabling attackers to inject malicious SQL commands through crafted prompts. An attacker can exploit this vulnerability by submitting specially crafted prompts that contain SQL injection payloads, resulting in arbitrary file creation on the server and potential Denial of Service attacks through resource exhaustion.",
            "cve": "CVE-2024-12911",
            "id": "pyup.io-76254",
            "more_info_path": "/vulnerabilities/CVE-2024-12911/76254",
            "specs": [
                "<0.12.3"
            ],
            "v": "<0.12.3"
        },
        {
            "advisory": "Affected versions of the LlamaIndex package are vulnerable to data loss through hash collisions. The `DocugamiReader` class uses MD5 hashing to generate IDs for document chunks, which leads to hash collisions when structurally distinct chunks contain identical text. This results in one chunk overwriting another, causing loss of semantically or legally important document content, breakage of parent-child chunk hierarchies, and potentially inaccurate or hallucinated responses in AI outputs. \r\n\r\nA local attacker with access to the document processing pipeline can exploit this vulnerability by crafting documents with identical text content in different structural contexts, resulting in data loss and corrupted document representations. \r\n\r\nThe vulnerability was fixed by modifying the hash generation to include additional context beyond just the text content, preventing collisions between structurally distinct chunks.",
            "cve": "CVE-2025-6211",
            "id": "pyup.io-78155",
            "more_info_path": "/vulnerabilities/CVE-2025-6211/78155",
            "specs": [
                "<0.12.41"
            ],
            "v": "<0.12.41"
        },
        {
            "advisory": "A vulnerability in the KnowledgeBaseWebReader class of the run-llama/llama_index repository, version latest, allows an attacker to cause a Denial of Service (DoS) by controlling a URL variable to contain the root URL. This leads to infinite recursive calls to the get_article_urls method, exhausting system resources and potentially crashing the application.",
            "cve": "CVE-2024-12910",
            "id": "pyup.io-76255",
            "more_info_path": "/vulnerabilities/CVE-2024-12910/76255",
            "specs": [
                "<0.12.9"
            ],
            "v": "<0.12.9"
        },
        {
            "advisory": "Affected versions of the llama_index package are vulnerable to an Insecure Temporary File due to the use of a shared, world-writable directory for NLTK data within the codebase instead of a user-specific temporary path. The vulnerability arises in the configuration of the NLTK data directory (e.g. by default in version 0.12.33 and earlier), which allows local users to overwrite, delete, or corrupt files in that directory.",
            "cve": "CVE-2025-7707",
            "id": "pyup.io-80462",
            "more_info_path": "/vulnerabilities/CVE-2025-7707/80462",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "An issue in llama_index v.0.7.13 and before allows a remote attacker to execute arbitrary code via the `exec` parameter in PandasQueryEngine function.",
            "cve": "CVE-2023-39662",
            "id": "pyup.io-65039",
            "more_info_path": "/vulnerabilities/CVE-2023-39662/65039",
            "specs": [
                "<=0.7.13"
            ],
            "v": "<=0.7.13"
        },
        {
            "advisory": "LlamaIndex (aka llama_index) through 0.9.34 allows SQL injection via the Text-to-SQL feature in NLSQLTableQueryEngine, SQLTableRetrieverQueryEngine, NLSQLRetriever, RetrieverQueryEngine, and PGVectorSQLQueryEngine. For example, an attacker might be able to delete this year's student records via \"Drop the Students table\" within English language input.",
            "cve": "CVE-2024-23751",
            "id": "pyup.io-66694",
            "more_info_path": "/vulnerabilities/CVE-2024-23751/66694",
            "specs": [
                "<=0.9.35"
            ],
            "v": "<=0.9.35"
        },
        {
            "advisory": "Affected versions of the LlamaIndex package are vulnerable to Denial of Service (DoS) due to uncontrolled recursion. The `KnowledgeBaseWebReader` class fails to properly implement the `max_depth` parameter in the `get_article_urls()` function, allowing unbounded recursive crawling of web pages. \r\n\r\nA remote attacker can exploit this vulnerability by providing a URL to a website with deeply nested or circular links, causing the function to exceed Python's recursion limit through repeated function calls, resulting in resource exhaustion and the crash of the Python process.\r\n\r\nThe vulnerability was fixed by properly implementing depth tracking and enforcement of the `max_depth` parameter to prevent recursive calls beyond the configured limit.",
            "cve": "CVE-2025-1752",
            "id": "pyup.io-77325",
            "more_info_path": "/vulnerabilities/CVE-2025-1752/77325",
            "specs": [
                ">=0.12.15,<0.12.21"
            ],
            "v": ">=0.12.15,<0.12.21"
        },
        {
            "advisory": "Affected versions of the `llama-index` package are vulnerable to Denial of Service (DoS) due to improper handling of thread termination scenarios. The LangChainLLM class's stream_complete method does not adequately manage thread termination when executing LLM predictions, as the StreamingGeneratorCallbackHandler.get_response_gen method uses a non-blocking queue.get(block=False) operation lacking timeout mechanisms. An attacker can exploit this vulnerability by providing malformed input of an incorrect type to the stream_complete method, causing the thread to terminate abnormally before _llm.predict execution, resulting in the process entering an infinite loop and becoming unresponsive.",
            "cve": "CVE-2024-12704",
            "id": "pyup.io-76267",
            "more_info_path": "/vulnerabilities/CVE-2024-12704/76267",
            "specs": [
                ">=0.6.5,<0.10.0"
            ],
            "v": ">=0.6.5,<0.10.0"
        }
    ],
    "llama-index-cli": [
        {
            "advisory": "LLama-Index CLI version v0.12.20 contains an OS command injection vulnerability. The vulnerability arises from the improper handling of the `--files` argument, which is directly passed into `os.system`. An attacker who controls the content of this argument can inject and execute arbitrary shell commands. This vulnerability can be exploited locally if the attacker has control over the CLI arguments, and remotely if a web application calls the LLama-Index CLI with a user-controlled filename. This issue can lead to arbitrary code execution on the affected system.",
            "cve": "CVE-2025-1753",
            "id": "pyup.io-77704",
            "more_info_path": "/vulnerabilities/CVE-2025-1753/77704",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        }
    ],
    "llama-index-core": [
        {
            "advisory": "Affected versions of the llama_index package are vulnerable to Command Injection due to insufficient validation in the safe_eval function within the exec_utils.py module. The safe_eval function's DunderVisitor class only checks for underscores in identifiers whilst permitting dangerous builtins like getattr and hasattr, which can be exploited to access restricted functionality and execute operating system commands.",
            "cve": "CVE-2024-3271",
            "id": "pyup.io-71792",
            "more_info_path": "/vulnerabilities/CVE-2024-3271/71792",
            "specs": [
                "<0.10.24"
            ],
            "v": "<0.10.24"
        },
        {
            "advisory": "A vulnerability was identified in the `exec_utils` class of the `llama_index` package, specifically within the `safe_eval` function, allowing for prompt injection leading to arbitrary code execution. This issue arises due to insufficient validation of input, which can be exploited to bypass method restrictions and execute unauthorized code. The vulnerability is a bypass of the previously addressed CVE-2023-39662, demonstrated through a proof of concept that creates a file on the system by exploiting the flaw.",
            "cve": "CVE-2024-3098",
            "id": "pyup.io-71653",
            "more_info_path": "/vulnerabilities/CVE-2024-3098/71653",
            "specs": [
                "<0.10.24"
            ],
            "v": "<0.10.24"
        },
        {
            "advisory": "Llama-index-core affected versions contain a vulnerability related to the use of exec() in the download_integration function. This issue allows for the potential execution of arbitrary code if an attacker can manipulate the input parameters. The vulnerability is mitigated by replacing the exec() function with a safer method using importlib.util",
            "cve": "CVE-2024-45201",
            "id": "pyup.io-72972",
            "more_info_path": "/vulnerabilities/CVE-2024-45201/72972",
            "specs": [
                "<0.10.38"
            ],
            "v": "<0.10.38"
        },
        {
            "advisory": "Affected versions of the llama_index package are vulnerable to Denial of Service due to uncontrolled recursion in the JSONReader component. The JSONReader module processes deeply nested JSON structures without implementing proper recursion depth limits, causing Python to exceed its maximum recursion depth limit during parsing operations.",
            "cve": "CVE-2025-5302",
            "id": "pyup.io-79078",
            "more_info_path": "/vulnerabilities/CVE-2025-5302/79078",
            "specs": [
                "<0.12.38"
            ],
            "v": "<0.12.38"
        },
        {
            "advisory": "Affected versions of the LlamaIndex package are vulnerable to Denial of Service (DoS) due to insufficient recursion depth handling in the JSON parser. The `load_data()` function in the `JSONReader` class fails to protect against deeply nested or circular JSON structures during data processing, allowing unbounded recursion depth. \r\n\r\nA remote attacker can exploit this vulnerability by providing a maliciously crafted JSON file with excessively nested objects or arrays, causing a stack overflow and denial of service through RecursionError exceptions.\r\n\r\nThe vulnerability was fixed by implementing exception handling that catches RecursionError during JSON processing (`except RecursionError: ') and gracefully returns an empty document list instead of crashing the application. The fix also adds a warning message to alert users when recursion limits are exceeded during JSON parsing.",
            "cve": "CVE-2025-5472",
            "id": "pyup.io-77992",
            "more_info_path": "/vulnerabilities/CVE-2025-5472/77992",
            "specs": [
                "<0.12.38"
            ],
            "v": "<0.12.38"
        },
        {
            "advisory": "Affected versions of the llama-index-core package are vulnerable to Insecure Temporary File handling due to use of a predictable, world-accessible cache directory on multi-user Linux systems. The get_cache_dir() function uses the hardcoded path /tmp/llama_index without appropriate security controls (e.g., safe permissions or exclusive creation), enabling unsafe temporary-directory usage and race conditions.",
            "cve": "CVE-2025-7647",
            "id": "pyup.io-79994",
            "more_info_path": "/vulnerabilities/CVE-2025-7647/79994",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Affected versions of the `llama-index-core` package are vulnerable to Denial of Service (DoS) due to improper handling of thread termination scenarios. The LangChainLLM class's stream_complete method does not adequately manage thread termination when executing LLM predictions, as the StreamingGeneratorCallbackHandler.get_response_gen method uses a non-blocking queue.get(block=False) operation lacking timeout mechanisms. An attacker can exploit this vulnerability by providing malformed input of an incorrect type to the stream_complete method, causing the thread to terminate abnormally before _llm.predict execution, resulting in the process entering an infinite loop and becoming unresponsive.",
            "cve": "CVE-2024-12704",
            "id": "pyup.io-79666",
            "more_info_path": "/vulnerabilities/CVE-2024-12704/79666",
            "specs": [
                ">=0.10.0,<0.12.6"
            ],
            "v": ">=0.10.0,<0.12.6"
        },
        {
            "advisory": "Affected versions of the LlamaIndex package are vulnerable to Remote Code Execution (RCE) through insecure deserialization. The `JsonPickleSerializer` class uses Python's `pickle.loads()` function without proper validation, which can execute arbitrary code when processing untrusted data. \r\n\r\nThe deserialize method attempts to deserialize data by applying `pickle.loads()` on base64-decoded input, allowing attackers to craft malicious payloads that execute arbitrary commands upon deserialization. A remote attacker can exploit this vulnerability by submitting specially crafted serialized objects, resulting in full system compromise.\r\n\r\nThe vulnerability was partially addressed by renaming the class to `PickleSerializer` and adding a prominent warning in the docstring advising users to only deserialize trusted data. However, the underlying insecure `pickle.loads()` functionality remains unchanged.",
            "cve": "CVE-2025-3108",
            "id": "pyup.io-77977",
            "more_info_path": "/vulnerabilities/CVE-2025-3108/77977",
            "specs": [
                ">=0.11.15,<=0.12.40"
            ],
            "v": ">=0.11.15,<=0.12.40"
        },
        {
            "advisory": "Affected versions of the LlamaIndex package are vulnerable to Path Traversal. The `encode_image()` function in `generic_utils.py` fails to properly validate and sanitize file path inputs, leading to unauthorized file access. \r\n\r\nAn attacker can exploit this vulnerability by manipulating the `image_path` parameter with path traversal sequences, resulting in the ability to read arbitrary files on the server, including sensitive system files.\r\n\r\nThe vulnerability was fixed in version 0.12.41 through the implementation of path validation checks. The fix adds the `is_valid_path()` and `is_valid_url()` functions to validate input paths and URLs.",
            "cve": "CVE-2025-6209",
            "id": "pyup.io-77994",
            "more_info_path": "/vulnerabilities/CVE-2025-6209/77994",
            "specs": [
                ">=0.11.23,<0.12.41"
            ],
            "v": ">=0.11.23,<0.12.41"
        }
    ],
    "llama-index-llms-rungpt": [
        {
            "advisory": "A command injection vulnerability exists in the RunGptLLM class of the llama_index library, version 0.9.47, used by the RunGpt framework from JinaAI to connect to Language Learning Models (LLMs). The vulnerability arises from the improper use of the eval function, allowing a malicious or compromised LLM hosting provider to execute arbitrary commands on the client's machine. This issue was fixed in version 0.10.13. The exploitation of this vulnerability could lead to a hosting provider gaining full control over client machines.",
            "cve": "CVE-2024-4181",
            "id": "pyup.io-71794",
            "more_info_path": "/vulnerabilities/CVE-2024-4181/71794",
            "specs": [
                "<0.1.3"
            ],
            "v": "<0.1.3"
        }
    ],
    "llama-index-packs-finchat": [
        {
            "advisory": "Affected versions of the llama-index-packs-finchat package are vulnerable to SQL Injection due to insufficient input validation in database queries. The run_sql_query function within the database_agent module fails to properly sanitize user-supplied input before incorporating it into SQL queries, allowing malicious SQL commands to be injected. An attacker can exploit this vulnerability by crafting malicious SQL payloads that leverage PostgreSQL's large object functionality to achieve remote code execution on the database server.",
            "cve": "CVE-2024-12909",
            "id": "pyup.io-76258",
            "more_info_path": "/vulnerabilities/CVE-2024-12909/76258",
            "specs": [
                "<=0.3.0"
            ],
            "v": "<=0.3.0"
        }
    ],
    "llama-index-readers-docugami": [
        {
            "advisory": "Affected versions of the Llama-index-readers-docugami\r\n package are vulnerable to data loss through hash collisions. The `DocugamiReader` class uses MD5 hashing to generate IDs for document chunks, which leads to hash collisions when structurally distinct chunks contain identical text. This results in one chunk overwriting another, causing loss of semantically or legally important document content, breakage of parent-child chunk hierarchies, and potentially inaccurate or hallucinated responses in AI outputs. \r\n\r\nA local attacker with access to the document processing pipeline can exploit this vulnerability by crafting documents with identical text content in different structural contexts, resulting in data loss and corrupted document representations. \r\n\r\nThe vulnerability was fixed by modifying the hash generation to include additional context beyond just the text content, preventing collisions between structurally distinct chunks.",
            "cve": "CVE-2025-6211",
            "id": "pyup.io-78154",
            "more_info_path": "/vulnerabilities/CVE-2025-6211/78154",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "llama-index-readers-obsidian": [
        {
            "advisory": "Affected versions of the LlamaIndex package are vulnerable to Path Traversal in the Obsidian reader component. The ObsidianReader class fails to properly sanitize file paths and validate file types when processing Obsidian vault contents, allowing access to files outside the intended vault directory. \r\n\r\nA remote attacker can exploit this vulnerability by crafting malicious file references or using hard links within the vault structure, resulting in unauthorized disclosure of sensitive system files. Additionally, the reader lacked proper boundary checks for file traversal operations, which could be exploited to access arbitrary files on the host system.\r\n\r\nThe vulnerability was fixed by implementing hardlink detection through the _is_hardlink() function that validates file link counts (st_nlink > 1) and skips processing of any hardlinks that could lead to path traversal attacks.",
            "cve": "CVE-2025-3046",
            "id": "pyup.io-77989",
            "more_info_path": "/vulnerabilities/CVE-2025-3046/77989",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Affected versions of the LlamaIndex package are vulnerable to Path Traversal through the Obsidian reader component. The reader fails to properly validate and skip hardlinks when processing Obsidian vault files, leading to potential unauthorized file access outside the intended directory. \r\n\r\nAn attacker can exploit this vulnerability by creating malicious hardlinks within an Obsidian vault that point to sensitive files outside the vault directory, resulting in the ability to read arbitrary files on the system.\r\n\r\nThe fix commit adds the `_is_hardlink()` function that checks if a file is a hardlink by comparing its number of links (st_nlink).",
            "cve": "CVE-2025-6210",
            "id": "pyup.io-77993",
            "more_info_path": "/vulnerabilities/CVE-2025-6210/77993",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        }
    ],
    "llama-index-readers-papers": [
        {
            "advisory": "Affected versions of the llama-index-readers-papers package are vulnerable to Path Traversal in the ArxivReader component. The `download_pdf()` function fails to properly sanitize filenames when saving downloaded papers from the Arxiv repository, allowing attackers to write files to arbitrary locations on the filesystem. \r\n\r\nA remote attacker can exploit this vulnerability by manipulating paper titles or metadata to include directory traversal sequences, resulting in files being saved outside the intended directory. This could lead to overwriting critical system files or placing malicious files in sensitive locations.\r\n\r\nThe vulnerability was fixed by implementing more robust filename hashing that sanitizes special characters and prevents directory traversal sequences in generated filenames.",
            "cve": "CVE-2025-3044",
            "id": "pyup.io-77987",
            "more_info_path": "/vulnerabilities/CVE-2025-3044/77987",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Affected versions of the llama-index-readers-papers package are vulnerable to Denial of Service (DoS) due to XML Entity Expansion attacks. Multiple XML parsers (PubMedReader, StripeDocsReader, and SitemapReader) use the insecure `xml.etree.ElementTree` module, which is susceptible to XML bomb attacks (also known as \"billion laughs\" attack). \r\n\r\nAn attacker can exploit this vulnerability by providing malicious XML files containing recursive entity references, leading to exponential memory consumption and system crash. The sitemap parser is particularly vulnerable as it accepts external XML input without proper validation.\r\n\r\nThe vulnerability was fixed by replacing the vulnerable `xml.etree.ElementTree` with `defusedxml`, which protects against XML entity expansion attacks by default.",
            "cve": "CVE-2025-3225",
            "id": "pyup.io-77978",
            "more_info_path": "/vulnerabilities/CVE-2025-3225/77978",
            "specs": [
                "<0.3.2"
            ],
            "v": "<0.3.2"
        }
    ],
    "llama-index-retrievers-duckdb-retriever": [
        {
            "advisory": "Affected versions of the llama-index-retrievers-duckdb-retriever package are vulnerable to SQL Injection due to improper query construction without prepared statements. The duckdb_retriever component constructs SQL queries by directly concatenating user input into query strings, allowing attackers to inject arbitrary SQL commands through malicious input parameters. An attacker can exploit this vulnerability to achieve remote code execution by injecting SQL commands that install the shellfs extension and execute system commands on the underlying host.",
            "cve": "CVE-2024-11958",
            "id": "pyup.io-78827",
            "more_info_path": "/vulnerabilities/CVE-2024-11958/78827",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "llama-stack": [
        {
            "advisory": "Llama-stack 0.1.5.1 includes a fix for a potential code injection vulnerability. Using 'eval' on server is a security risk.",
            "cve": "PVE-2025-75663",
            "id": "pyup.io-75663",
            "more_info_path": "/vulnerabilities/PVE-2025-75663/75663",
            "specs": [
                "<0.1.5.1"
            ],
            "v": "<0.1.5.1"
        },
        {
            "advisory": "Affected versions of the llama-stack package are vulnerable to Improper Input Validation due to the acceptance of unverified parameters in the resolve_ast_by_type function. The resolve_ast_by_type routine in the BFCL AST parsing utility uses caller-provided parameter values to resolve types without adequate validation, creating an unsafe code path that can influence what code is resolved and executed.",
            "cve": "CVE-2025-55178",
            "id": "pyup.io-79884",
            "more_info_path": "/vulnerabilities/CVE-2025-55178/79884",
            "specs": [
                "<0.2.20"
            ],
            "v": "<0.2.20"
        }
    ],
    "llamafactory": [
        {
            "advisory": "LLaMA-Factory is a tuning library for large language models. A remote code execution vulnerability was discovered in LLaMA-Factory versions up to and including 0.9.3 during the LLaMA-Factory training process. This vulnerability arises because the `vhead_file` is loaded without proper safeguards, allowing malicious attackers to execute arbitrary malicious code on the host system simply by passing a malicious `Checkpoint path` parameter through the `WebUI` interface. The attack is stealthy, as the victim remains unaware of the exploitation. The root cause is that the `vhead_file` argument is loaded without the secure parameter `weights_only=True`. Version 0.9.4 contains a fix for the issue.",
            "cve": "CVE-2025-53002",
            "id": "pyup.io-77974",
            "more_info_path": "/vulnerabilities/CVE-2025-53002/77974",
            "specs": [
                "<0.9.3"
            ],
            "v": "<0.9.3"
        },
        {
            "advisory": "A critical vulnerability exists in the llamafy_baichuan2.py script of the LLaMA-Factory project. The script performs insecure deserialization using torch.load() on user-supplied .bin files from an input directory. An attacker can exploit this behavior by crafting a malicious .bin file that executes arbitrary commands during deserialization.",
            "cve": "CVE-2025-46567",
            "id": "pyup.io-77152",
            "more_info_path": "/vulnerabilities/CVE-2025-46567/77152",
            "specs": [
                "<0.9.3"
            ],
            "v": "<0.9.3"
        },
        {
            "advisory": "A critical remote OS command injection vulnerability exists in Llama Factory due to improper handling of user input. The insecure use of the Popen function with `shell=True` and unsanitized input allows attackers to execute arbitrary OS commands, potentially compromising data, escalating privileges, or deploying malware. Immediate remediation involves avoiding `shell=True` in Popen and passing commands as lists to prevent malicious command execution, thereby mitigating the risk of data breaches and system disruption.",
            "cve": "CVE-2024-52803",
            "id": "pyup.io-74226",
            "more_info_path": "/vulnerabilities/CVE-2024-52803/74226",
            "specs": [
                "<=0.9.0"
            ],
            "v": "<=0.9.0"
        },
        {
            "advisory": "Affected versions of the llamafactory package are vulnerable to Server-Side Request Forgery (SSRF) and Path Traversal due to unvalidated remote URL fetching and permissive local file path handling in the Chat API. In src/llamafactory/api/chat.py, the _process_request function dereferences user-supplied image_url, video_url, and audio_url values by either reading local paths detected via os.path.isfile or issuing requests.get(url, stream=True).raw, and this logic is invoked by create_chat_completion_response and create_stream_chat_completion_response behind the public /v1/chat/completions endpoint.",
            "cve": "CVE-2025-61784",
            "id": "pyup.io-80236",
            "more_info_path": "/vulnerabilities/CVE-2025-61784/80236",
            "specs": [
                "<=0.9.3"
            ],
            "v": "<=0.9.3"
        }
    ],
    "llmswap": [
        {
            "advisory": "Affected versions of this package are vulnerable to Information Disclosure. Error handling across multiple providers fails to sanitize exception messages before returning them to users, leading to exposure of sensitive information, including API keys, credentials, and internal system details through unfiltered error responses.",
            "cve": "PVE-2025-82257",
            "id": "pyup.io-82257",
            "more_info_path": "/vulnerabilities/PVE-2025-82257/82257",
            "specs": [
                "<5.2.1"
            ],
            "v": "<5.2.1"
        }
    ],
    "lmdb": [
        {
            "advisory": "An issue was discovered in py-lmdb 0.97. For certain values of mp_flags, mdb_page_touch does not properly set up mc->mc_pg[mc->top], leading to an invalid write operation. NOTE: this outcome occurs when accessing a data.mdb file supplied by an attacker.",
            "cve": "CVE-2019-16225",
            "id": "pyup.io-54220",
            "more_info_path": "/vulnerabilities/CVE-2019-16225/54220",
            "specs": [
                ">=0,<0.98"
            ],
            "v": ">=0,<0.98"
        },
        {
            "advisory": "An issue was discovered in py-lmdb 0.97. mdb_node_del does not validate a memmove in the case of an unexpected node->mn_hi, leading to an invalid write operation. NOTE: this outcome occurs when accessing a data.mdb file supplied by an attacker.",
            "cve": "CVE-2019-16226",
            "id": "pyup.io-54160",
            "more_info_path": "/vulnerabilities/CVE-2019-16226/54160",
            "specs": [
                ">=0,<0.98"
            ],
            "v": ">=0,<0.98"
        },
        {
            "advisory": "An issue was discovered in py-lmdb 0.97. For certain values of mn_flags, mdb_cursor_set triggers a memcpy with an invalid write operation within mdb_xcursor_init1. NOTE: this outcome occurs when accessing a data.mdb file supplied by an attacker.",
            "cve": "CVE-2019-16227",
            "id": "pyup.io-54158",
            "more_info_path": "/vulnerabilities/CVE-2019-16227/54158",
            "specs": [
                ">=0,<0.98"
            ],
            "v": ">=0,<0.98"
        },
        {
            "advisory": "An issue was discovered in py-lmdb 0.97. There is a divide-by-zero error in the function mdb_env_open2 if mdb_env_read_header obtains a zero value for a certain size field. NOTE: this outcome occurs when accessing a data.mdb file supplied by an attacker.",
            "cve": "CVE-2019-16228",
            "id": "pyup.io-54159",
            "more_info_path": "/vulnerabilities/CVE-2019-16228/54159",
            "specs": [
                ">=0,<0.98"
            ],
            "v": ">=0,<0.98"
        },
        {
            "advisory": "An issue was discovered in py-lmdb 0.97. For certain values of md_flags, mdb_node_add does not properly set up a memcpy destination, leading to an invalid write operation. NOTE: this outcome occurs when accessing a data.mdb file supplied by an attacker.",
            "cve": "CVE-2019-16224",
            "id": "pyup.io-54157",
            "more_info_path": "/vulnerabilities/CVE-2019-16224/54157",
            "specs": [
                ">=0,<0.98"
            ],
            "v": ">=0,<0.98"
        }
    ],
    "lmdeploy": [
        {
            "advisory": "Lmdeploy 0.0.10 includes a fix for a potential race condition vulnerability.\r\nhttps://github.com/InternLM/lmdeploy/pull/460",
            "cve": "PVE-2023-61437",
            "id": "pyup.io-61437",
            "more_info_path": "/vulnerabilities/PVE-2023-61437/61437",
            "specs": [
                "<0.0.10"
            ],
            "v": "<0.0.10"
        },
        {
            "advisory": "Affected versions of the lmdeploy package are vulnerable to Deserialization of Untrusted Data due to the use of torch.load() without the weights_only=True security parameter when loading model checkpoint files. Multiple locations in the codebase, including the load_weight_ckpt function in lmdeploy/vl/model/utils.py and the PytorchLoader.items method in lmdeploy/turbomind/deploy/loader.py, directly call torch.load() on user-supplied .bin or .pt files, which internally uses Python's pickle module to deserialise data and can execute arbitrary code embedded in malicious model files during the unpickling process.",
            "cve": "CVE-2025-67729",
            "id": "pyup.io-83561",
            "more_info_path": "/vulnerabilities/CVE-2025-67729/83561",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "A vulnerability was found in InternLM LMDeploy in affected versions. It has been classified as critical. Affected is the function load_weight_ckpt of the file lmdeploy/lmdeploy/vl/model/utils.py of the component PT File Handler. The manipulation leads to deserialization. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used.",
            "cve": "CVE-2025-3162",
            "id": "pyup.io-76516",
            "more_info_path": "/vulnerabilities/CVE-2025-3162/76516",
            "specs": [
                "<=0.7.1"
            ],
            "v": "<=0.7.1"
        },
        {
            "advisory": "Affected versions of the LMDeploy package are vulnerable to Code Injection due to improper input handling in the documentation configuration file. The Open function in lmdeploy/docs/en/conf.py fails to properly sanitize user-controlled input before executing it, allowing arbitrary code to be injected and executed within the Python interpreter context.",
            "cve": "CVE-2025-3163",
            "id": "pyup.io-78838",
            "more_info_path": "/vulnerabilities/CVE-2025-3163/78838",
            "specs": [
                "<=0.7.1"
            ],
            "v": "<=0.7.1"
        }
    ],
    "lmnr": [
        {
            "advisory": "Affected versions of the lmnr package are potentially vulnerable to missing HTTP Security Headers. The headers() method in\u202fnext.config.js fails to define essential HTTP security headers, leading to unmitigated risks of cross\u2011site scripting (XSS), clickjacking, MIME sniffing and transport downgrade attacks.",
            "cve": "PVE-2025-78364",
            "id": "pyup.io-78364",
            "more_info_path": "/vulnerabilities/PVE-2025-78364/78364",
            "specs": [
                "<0.1.13"
            ],
            "v": "<0.1.13"
        },
        {
            "advisory": "Lmnr updates Next.js to 15.2.3 to patch CVE-2025-29927.",
            "cve": "CVE-2025-29927",
            "id": "pyup.io-76483",
            "more_info_path": "/vulnerabilities/CVE-2025-29927/76483",
            "specs": [
                "<0.1.3alpha.9"
            ],
            "v": "<0.1.3alpha.9"
        }
    ],
    "lnbits": [
        {
            "advisory": "Lnbits version 0.12.5 addresses a security issue in the `pycryptodomex` library. The dependency is updated from version 3.19.0 to 3.19.1 to resolve the vulnerability identified as CVE-2023-52323. This update ensures that the package remains secure by incorporating the necessary fixes from the updated library version.",
            "cve": "CVE-2023-52323",
            "id": "pyup.io-71115",
            "more_info_path": "/vulnerabilities/CVE-2023-52323/71115",
            "specs": [
                "<0.12.5"
            ],
            "v": "<0.12.5"
        },
        {
            "advisory": "Lnbits version 0.12.5 updates its `black` dependency from version 24.2.0 to 24.3.0 to address the security vulnerability identified as CVE-2024-21503.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-71111",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/71111",
            "specs": [
                "<0.12.5"
            ],
            "v": "<0.12.5"
        },
        {
            "advisory": "LNbits is a Lightning wallet and accounts system. Paying invoices in Eclair that do not get settled within the internal timeout (about 30s) lead to a payment being considered failed, even though it may still be in flight. This vulnerability can lead to a total loss of funds for the node backend.",
            "cve": "CVE-2024-34694",
            "id": "pyup.io-71892",
            "more_info_path": "/vulnerabilities/CVE-2024-34694/71892",
            "specs": [
                "<0.12.6"
            ],
            "v": "<0.12.6"
        },
        {
            "advisory": "A Server-Side Request Forgery (SSRF) vulnerability has been discovered in LNbits' LNURL authentication handling functionality. The vulnerability exists in the LNURL authentication callback process, where the application makes HTTP requests to user-provided callback URLs and follows redirects without proper validation. When processing LNURL authentication requests, the application accepts a callback URL parameter and makes an HTTP request to that URL using the httpx library with redirect following enabled. The application doesn't properly validate the callback URL, allowing attackers to specify internal network addresses and access internal resources. This vulnerability allows an attacker to make the application send HTTP requests to arbitrary internal network locations, potentially exposing sensitive information or accessing internal services that should not be accessible from the internet.",
            "cve": "CVE-2025-32013",
            "id": "pyup.io-76579",
            "more_info_path": "/vulnerabilities/CVE-2025-32013/76579",
            "specs": [
                "<=0.12.12"
            ],
            "v": "<=0.12.12"
        }
    ],
    "loadero-python": [
        {
            "advisory": "Loadero-python 1.3.0 updates its dependency 'jinja2' to v3.1.4 to include a security fix.",
            "cve": "CVE-2024-34064",
            "id": "pyup.io-73766",
            "more_info_path": "/vulnerabilities/CVE-2024-34064/73766",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "local-deep-research": [
        {
            "advisory": "Affected versions of the local-deep-research package are vulnerable to Improper Input Validation due to double unescaping of HTML entities in the PDF export logic. The downloadPdf function in src/local_deep_research/web/static/js/services/pdf.js decoded \u201c&\u201d before other entities, creating conditions where encoded payloads become executable markup after multiple passes; the decoding order was corrected to avoid this pitfall (related commit: 1506523e73ab1d4618bdc0e5bc4bd877344f2004).",
            "cve": "PVE-2025-79207",
            "id": "pyup.io-79207",
            "more_info_path": "/vulnerabilities/PVE-2025-79207/79207",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Affected versions of the local-deep-research package are vulnerable to Cross-site Scripting (XSS) due to incomplete HTML sanitization in the client-side PDF export pipeline. The downloadPdf function in src/local_deep_research/web/static/js/services/pdf.js attempted to strip HTML with regular expressions, which can miss malformed tags and script payloads, and was replaced with DOM-based sanitization for correctness (related commit: 1506523e73ab1d4618bdc0e5bc4bd877344f2004).",
            "cve": "PVE-2025-79206",
            "id": "pyup.io-79206",
            "more_info_path": "/vulnerabilities/PVE-2025-79206/79206",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Affected versions of the local-deep-research package are vulnerable to Cross-Site Request Forgery (CSRF) due to missing CSRF token enforcement for destructive benchmark endpoints. The benchmark_results.html client code invoked /benchmark/api/cancel/ and /benchmark/api/delete/ without including an X-CSRFToken header, leaving these state-changing routes exposed to cross-origin requests when CSRF exemptions or permissive CORS were present (related commit: 73095b498d63c6e092a1b9ca918532378d50577a).",
            "cve": "PVE-2025-79208",
            "id": "pyup.io-79208",
            "more_info_path": "/vulnerabilities/PVE-2025-79208/79208",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Affected versions of the local-deep-research package are vulnerable to Open Redirect due to trusting the next_page query parameter for post-authentication redirection. The local_deep_research.web.auth.routes.login handler parsed the URL but still used the untrusted next_page value instead of the validated parsed_url.path, enabling attacker-controlled redirect destinations (related commit: 1506523e73ab1d4618bdc0e5bc4bd877344f2004).",
            "cve": "PVE-2025-79199",
            "id": "pyup.io-79199",
            "more_info_path": "/vulnerabilities/PVE-2025-79199/79199",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Affected versions of the local-deep-research package are vulnerable to Information Disclosure due to logging sensitive configuration data in plaintext. The start_research function in local_deep_research.web.routes.research_routes and the run_research_process function in local_deep_research.web.services.research_service wrote full settings snapshots to logs instead of using a redacting logger, exposing API keys, tokens, and passwords (related commit: 10ae494b35b96edbc589ea85a903cfb4a1bc5e43).",
            "cve": "PVE-2025-79209",
            "id": "pyup.io-79209",
            "more_info_path": "/vulnerabilities/PVE-2025-79209/79209",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Affected versions of the local-deep-research package are vulnerable to Information Disclosure due to plaintext storage of sensitive data in an SQLite database. The application stores confidential information, including API key,s in a local SQLite database file without encryption or adequate documentation of this behaviour, and provides no configuration options for users to specify secure database locations.",
            "cve": "CVE-2025-57806",
            "id": "pyup.io-79205",
            "more_info_path": "/vulnerabilities/CVE-2025-57806/79205",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Affected versions of the local-deep-research package are vulnerable to Path Traversal due to unvalidated file path input in the /static/path:path route. The app_serve_static function in src/local_deep_research/web/app_factory.py and the now-removed research.serve_static endpoint in src/local_deep_research/web/routes/research_routes.py constructed filesystem paths directly from the path parameter and performed existence checks before dispatch, allowing traversal segments to influence which files are selected.",
            "cve": "PVE-2025-79198",
            "id": "pyup.io-79198",
            "more_info_path": "/vulnerabilities/PVE-2025-79198/79198",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Affected versions of the `local-deep-research` package are vulnerable to Cross-site Scripting (XSS) due to unsafe use of `innerHTML` for rendering dynamic content in multiple JavaScript components. The `showAlert()` function in `research.js`, dropdown components, and settings display logic directly inject unsanitised user-controlled or server-provided data into the DOM using innerHTML assignments, allowing malicious HTML and JavaScript code to be executed in the user's browser context. An attacker can exploit this by crafting malicious API responses or manipulating server data to include script tags or event handlers, enabling execution of arbitrary JavaScript to steal session tokens, perform unauthorised actions on behalf of the user, or redirect users to malicious sites.",
            "cve": "PVE-2025-82364",
            "id": "pyup.io-82364",
            "more_info_path": "/vulnerabilities/PVE-2025-82364/82364",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Affected versions of the local-deep-research package are vulnerable to Server-Side Request Forgery (SSRF) due to the download service making outbound HTTP requests without applying the project\u2019s SSRF validation. The issue occurs in src/local_deep_research/research_library/services/download_service.py, where _download_generic and related download paths call requests.get() directly instead of the guarded request helpers in security/safe_requests.py/security/ssrf_validator.py, and attacker-controlled URLs can be introduced via POST /api/resources/ (stored by resource_service.py:add_resource()) and later fetched via /library/api/download/.",
            "cve": "CVE-2025-67743",
            "id": "pyup.io-83244",
            "more_info_path": "/vulnerabilities/CVE-2025-67743/83244",
            "specs": [
                ">=1.3.0,<1.3.9"
            ],
            "v": ">=1.3.0,<1.3.9"
        }
    ],
    "localstack": [
        {
            "advisory": "Localstack is vulnerable to CVE-2021-32090: The dashboard component of StackLift LocalStack 0.12.6 allows attackers to inject arbitrary shell commands via the functionName parameter. After disclosure, vendor said that these threats \"are not considered a key concern since LocalStack is executed on a local machine\". There's no information about patches for these vulnerabilities.\r\nhttps://blog.sonarsource.com/hack-the-stack-with-localstack",
            "cve": "CVE-2021-32090",
            "id": "pyup.io-42835",
            "more_info_path": "/vulnerabilities/CVE-2021-32090/42835",
            "specs": [
                "<0.12.10"
            ],
            "v": "<0.12.10"
        },
        {
            "advisory": "Localstack 0.12.14 fixes CORS setup to prevent CSRF attacks.\r\nhttps://github.com/localstack/localstack/commit/809235e3079a1060dae599ce83ed06c84b0e34a5",
            "cve": "PVE-2022-52465",
            "id": "pyup.io-52465",
            "more_info_path": "/vulnerabilities/PVE-2022-52465/52465",
            "specs": [
                "<0.12.14"
            ],
            "v": "<0.12.14"
        },
        {
            "advisory": "Localstack 0.12.14 fixes CORS setup to prevent CSRF.\r\nhttps://github.com/localstack/localstack/commit/809235e3079a1060dae599ce83ed06c84b0e34a5",
            "cve": "PVE-2021-41059",
            "id": "pyup.io-41059",
            "more_info_path": "/vulnerabilities/PVE-2021-41059/41059",
            "specs": [
                "<0.12.14"
            ],
            "v": "<0.12.14"
        },
        {
            "advisory": "Localstack 0.12.15 binds Edge Service to 127.0.0.1 by default instead of to 0.0.0.0.\r\nhttps://github.com/localstack/localstack/pull/4223",
            "cve": "PVE-2021-42834",
            "id": "pyup.io-42834",
            "more_info_path": "/vulnerabilities/PVE-2021-42834/42834",
            "specs": [
                "<0.12.15"
            ],
            "v": "<0.12.15"
        },
        {
            "advisory": "Localstack 0.12.17 replaces Docker CLI commands with Docker Python SDK client to reduce the number of shell calls.\r\nhttps://github.com/localstack/localstack/pull/4442",
            "cve": "PVE-2021-42833",
            "id": "pyup.io-42833",
            "more_info_path": "/vulnerabilities/PVE-2021-42833/42833",
            "specs": [
                "<0.12.17"
            ],
            "v": "<0.12.17"
        },
        {
            "advisory": "Localstack 0.12.17 replaces Docker CLI commands with Docker Python SDK client.",
            "cve": "PVE-2022-52464",
            "id": "pyup.io-52464",
            "more_info_path": "/vulnerabilities/PVE-2022-52464/52464",
            "specs": [
                "<0.12.17"
            ],
            "v": "<0.12.17"
        },
        {
            "advisory": "Missing SSL certificate validation in localstack v2.3.2 allows attackers to eavesdrop on communications between the host and server via a man-in-the-middle attack.",
            "cve": "CVE-2023-48054",
            "id": "pyup.io-65234",
            "more_info_path": "/vulnerabilities/CVE-2023-48054/65234",
            "specs": [
                "==2.3.2"
            ],
            "v": "==2.3.2"
        },
        {
            "advisory": "Localstack is vulnerable to CVE-2021-32091: A Cross-site scripting (XSS) vulnerability exists in StackLift LocalStack 0.12.6. After disclosure, vendor said that these threats \"are not considered a key concern since LocalStack is executed on a local machine\". There's no information about patches for these vulnerabilities.\r\nhttps://blog.sonarsource.com/hack-the-stack-with-localstack",
            "cve": "CVE-2021-32091",
            "id": "pyup.io-42836",
            "more_info_path": "/vulnerabilities/CVE-2021-32091/42836",
            "specs": [
                ">0"
            ],
            "v": ">0"
        },
        {
            "advisory": "Localstack is vulnerable to Denial of Service via regular expressions (ReDoS). After disclosure, vendor said that these threats \"are not considered a key concern since LocalStack is executed on a local machine\". There's no information about patches for these vulnerabilities.\r\nhttps://blog.sonarsource.com/hack-the-stack-with-localstack",
            "cve": "PVE-2021-42837",
            "id": "pyup.io-42837",
            "more_info_path": "/vulnerabilities/PVE-2021-42837/42837",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "locopy": [
        {
            "advisory": "Locopy 0.3.8 includes a security patch for the function 'read_config_yaml' in 'locopy/utility.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/capitalone/locopy/pull/105",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41335",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41335",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "Locopy 0.5.9 updates its urllib3 dependency from version 2.0.7 to 2.2.2 to address security concerns, including CVE-2024-37891.",
            "cve": "CVE-2024-37891",
            "id": "pyup.io-71683",
            "more_info_path": "/vulnerabilities/CVE-2024-37891/71683",
            "specs": [
                "<0.5.9"
            ],
            "v": "<0.5.9"
        }
    ],
    "locust": [
        {
            "advisory": "Locust 1.3.2 includes a fix for a XSS vulnerability.\r\nhttps://github.com/locustio/locust/pull/1603/commits/0d118179709b4a60174810bae4db41d40e4c99ad",
            "cve": "PVE-2022-50450",
            "id": "pyup.io-50450",
            "more_info_path": "/vulnerabilities/PVE-2022-50450/50450",
            "specs": [
                "<1.3.2"
            ],
            "v": "<1.3.2"
        },
        {
            "advisory": "A stored cross-site scripting (XSS) vulnerability affects the Web UI in Locust before 1.3.2, if the installation violates the usage expectations by exposing this UI to outside users.",
            "cve": "CVE-2020-28364",
            "id": "pyup.io-54241",
            "more_info_path": "/vulnerabilities/CVE-2020-28364/54241",
            "specs": [
                ">=0,<1.3.2"
            ],
            "v": ">=0,<1.3.2"
        }
    ],
    "locustio": [
        {
            "advisory": "Locustio before 0.7 uses pickle, exposing to RCE.",
            "cve": "PVE-2021-25878",
            "id": "pyup.io-25878",
            "more_info_path": "/vulnerabilities/PVE-2021-25878/25878",
            "specs": [
                "<0.7"
            ],
            "v": "<0.7"
        }
    ],
    "logbesselk": [
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41221",
            "id": "pyup.io-51605",
            "more_info_path": "/vulnerabilities/CVE-2021-41221/51605",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2020-10531",
            "id": "pyup.io-51613",
            "more_info_path": "/vulnerabilities/CVE-2020-10531/51613",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41205",
            "id": "pyup.io-51589",
            "more_info_path": "/vulnerabilities/CVE-2021-41205/51589",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41220",
            "id": "pyup.io-51604",
            "more_info_path": "/vulnerabilities/CVE-2021-41220/51604",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41197",
            "id": "pyup.io-51581",
            "more_info_path": "/vulnerabilities/CVE-2021-41197/51581",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-22922",
            "id": "pyup.io-51574",
            "more_info_path": "/vulnerabilities/CVE-2021-22922/51574",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-22924",
            "id": "pyup.io-51576",
            "more_info_path": "/vulnerabilities/CVE-2021-22924/51576",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41219",
            "id": "pyup.io-51603",
            "more_info_path": "/vulnerabilities/CVE-2021-41219/51603",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41227",
            "id": "pyup.io-51611",
            "more_info_path": "/vulnerabilities/CVE-2021-41227/51611",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41201",
            "id": "pyup.io-51585",
            "more_info_path": "/vulnerabilities/CVE-2021-41201/51585",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41209",
            "id": "pyup.io-51593",
            "more_info_path": "/vulnerabilities/CVE-2021-41209/51593",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41215",
            "id": "pyup.io-51599",
            "more_info_path": "/vulnerabilities/CVE-2021-41215/51599",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41217",
            "id": "pyup.io-51601",
            "more_info_path": "/vulnerabilities/CVE-2021-41217/51601",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41214",
            "id": "pyup.io-51598",
            "more_info_path": "/vulnerabilities/CVE-2021-41214/51598",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41218",
            "id": "pyup.io-51602",
            "more_info_path": "/vulnerabilities/CVE-2021-41218/51602",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41211",
            "id": "pyup.io-51595",
            "more_info_path": "/vulnerabilities/CVE-2021-41211/51595",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-22926",
            "id": "pyup.io-51578",
            "more_info_path": "/vulnerabilities/CVE-2021-22926/51578",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41224",
            "id": "pyup.io-51608",
            "more_info_path": "/vulnerabilities/CVE-2021-41224/51608",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41228",
            "id": "pyup.io-51612",
            "more_info_path": "/vulnerabilities/CVE-2021-41228/51612",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41203",
            "id": "pyup.io-51587",
            "more_info_path": "/vulnerabilities/CVE-2021-41203/51587",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41223",
            "id": "pyup.io-51607",
            "more_info_path": "/vulnerabilities/CVE-2021-41223/51607",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41222",
            "id": "pyup.io-51606",
            "more_info_path": "/vulnerabilities/CVE-2021-41222/51606",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41200",
            "id": "pyup.io-51584",
            "more_info_path": "/vulnerabilities/CVE-2021-41200/51584",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41208",
            "id": "pyup.io-51592",
            "more_info_path": "/vulnerabilities/CVE-2021-41208/51592",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'numpy' to v1.21.5 to include a security fix.",
            "cve": "CVE-2021-33430",
            "id": "pyup.io-51528",
            "more_info_path": "/vulnerabilities/CVE-2021-33430/51528",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41212",
            "id": "pyup.io-51596",
            "more_info_path": "/vulnerabilities/CVE-2021-41212/51596",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41216",
            "id": "pyup.io-51600",
            "more_info_path": "/vulnerabilities/CVE-2021-41216/51600",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-22923",
            "id": "pyup.io-51575",
            "more_info_path": "/vulnerabilities/CVE-2021-22923/51575",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41198",
            "id": "pyup.io-51582",
            "more_info_path": "/vulnerabilities/CVE-2021-41198/51582",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41225",
            "id": "pyup.io-51609",
            "more_info_path": "/vulnerabilities/CVE-2021-41225/51609",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41226",
            "id": "pyup.io-51610",
            "more_info_path": "/vulnerabilities/CVE-2021-41226/51610",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41210",
            "id": "pyup.io-51594",
            "more_info_path": "/vulnerabilities/CVE-2021-41210/51594",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41195",
            "id": "pyup.io-51579",
            "more_info_path": "/vulnerabilities/CVE-2021-41195/51579",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41202",
            "id": "pyup.io-51586",
            "more_info_path": "/vulnerabilities/CVE-2021-41202/51586",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41196",
            "id": "pyup.io-51580",
            "more_info_path": "/vulnerabilities/CVE-2021-41196/51580",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41213",
            "id": "pyup.io-51597",
            "more_info_path": "/vulnerabilities/CVE-2021-41213/51597",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41207",
            "id": "pyup.io-51591",
            "more_info_path": "/vulnerabilities/CVE-2021-41207/51591",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41199",
            "id": "pyup.io-51583",
            "more_info_path": "/vulnerabilities/CVE-2021-41199/51583",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41206",
            "id": "pyup.io-51590",
            "more_info_path": "/vulnerabilities/CVE-2021-41206/51590",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-22925",
            "id": "pyup.io-51577",
            "more_info_path": "/vulnerabilities/CVE-2021-22925/51577",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        },
        {
            "advisory": "Logbesselk 0.8.5 updates its dependency 'tensorflow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2021-41204",
            "id": "pyup.io-51588",
            "more_info_path": "/vulnerabilities/CVE-2021-41204/51588",
            "specs": [
                "<0.8.5"
            ],
            "v": "<0.8.5"
        }
    ],
    "loggerhead": [
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in templatefunctions.py in Loggerhead before 1.18.1 allows remote authenticated users to inject arbitrary web script or HTML via a filename, which is not properly handled in a revision view.",
            "cve": "CVE-2011-0728",
            "id": "pyup.io-67952",
            "more_info_path": "/vulnerabilities/CVE-2011-0728/67952",
            "specs": [
                "<1.18.1"
            ],
            "v": "<1.18.1"
        }
    ],
    "loggingredactor": [
        {
            "advisory": "Affected versions of the loggingredactor package are vulnerable to Improper Input Validation due to incorrect type coercion of non-string values into strings during redaction. The RedactingFilter.redact method converts non-string log content using str() (for example, content_copy = isinstance(content_copy, str) and content_copy or str(content_copy)), which can change integers and booleans into strings before Python\u2019s logging performs %-style formatting such as %d.",
            "cve": "CVE-2026-22041",
            "id": "pyup.io-84032",
            "more_info_path": "/vulnerabilities/CVE-2026-22041/84032",
            "specs": [
                "<0.0.6"
            ],
            "v": "<0.0.6"
        }
    ],
    "logilab-common": [
        {
            "advisory": "The (1) extract_keys_from_pdf and (2) fill_pdf functions in pdf_ext.py in logilab-commons before 0.61.0 allows local users to overwrite arbitrary files and possibly have other unspecified impact via a symlink attack on /tmp/toto.fdf.",
            "cve": "CVE-2014-1838",
            "id": "pyup.io-35524",
            "more_info_path": "/vulnerabilities/CVE-2014-1838/35524",
            "specs": [
                "<0.61.0"
            ],
            "v": "<0.61.0"
        },
        {
            "advisory": "The Execute class in shellutils in logilab-commons before 0.61.0 uses tempfile.mktemp, which allows local users to have an unspecified impact by pre-creating the temporary file.",
            "cve": "CVE-2014-1839",
            "id": "pyup.io-35525",
            "more_info_path": "/vulnerabilities/CVE-2014-1839/35525",
            "specs": [
                "<0.61.0"
            ],
            "v": "<0.61.0"
        }
    ],
    "logprep": [
        {
            "advisory": "Logprep 7.0.0 updates its dependency 'certifi' to include a security fix.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-61802",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/61802",
            "specs": [
                "<7.0.0"
            ],
            "v": "<7.0.0"
        },
        {
            "advisory": "Logprep 7.0.0 updates its dependency 'urllib3' to include a security fix.",
            "cve": "CVE-2023-43804",
            "id": "pyup.io-61804",
            "more_info_path": "/vulnerabilities/CVE-2023-43804/61804",
            "specs": [
                "<7.0.0"
            ],
            "v": "<7.0.0"
        },
        {
            "advisory": "Logprep 7.0.0 updates its dependency 'aiohttp' to include a security fix.",
            "cve": "CVE-2023-37276",
            "id": "pyup.io-61805",
            "more_info_path": "/vulnerabilities/CVE-2023-37276/61805",
            "specs": [
                "<7.0.0"
            ],
            "v": "<7.0.0"
        }
    ],
    "loguru": [
        {
            "advisory": "Insertion of Sensitive Information into Log File in Conda loguru prior to 0.5.3.",
            "cve": "CVE-2022-0338",
            "id": "pyup.io-54272",
            "more_info_path": "/vulnerabilities/CVE-2022-0338/54272",
            "specs": [
                ">=0,<0.5.3"
            ],
            "v": ">=0,<0.5.3"
        }
    ],
    "lollms": [
        {
            "advisory": "A remote code execution vulnerability exists in the Calculate function of parisneo/lollms version 9.8. The vulnerability arises from the use of Python's eval() function to evaluate mathematical expressions within a Python sandbox that disables __builtins__ and only allows functions from the math module. This sandbox can be bypassed by loading the os module using the _frozen_importlib.BuiltinImporter class, allowing an attacker to execute arbitrary commands on the server. The issue is fixed in version 9.10.",
            "cve": "CVE-2024-6982",
            "id": "pyup.io-76246",
            "more_info_path": "/vulnerabilities/CVE-2024-6982/76246",
            "specs": [
                "<11.0.0"
            ],
            "v": "<11.0.0"
        },
        {
            "advisory": "Affected versions of the parisneo/lollms package are vulnerable to Path Traversal due to insufficient sanitization of user-controlled file path input. The `/set_personality_config` endpoint fails to restrict directory traversal when processing the configuration file parameter, allowing attackers to craft paths that escape the intended directory. An attacker can exploit this by sending specially crafted requests to `/set_personality_config` to overwrite the `configs/config.yaml` file, potentially altering settings like `force_accept_remote_access` or `turn_on_code_validation` and enabling remote code execution.",
            "cve": "CVE-2024-5824",
            "id": "pyup.io-78738",
            "more_info_path": "/vulnerabilities/CVE-2024-5824/78738",
            "specs": [
                "<9.5.0"
            ],
            "v": "<9.5.0"
        },
        {
            "advisory": "Affected versions of the lollms package are vulnerable to Path Traversal due to insufficient sanitization in the sanitize_path_from_endpoint and sanitize_path functions. The sanitize_path_from_endpoint and sanitize_path functions in lollms_core\\lollms\\security.py fail to properly neutralize user-supplied input, enabling traversal of directory paths on Windows systems. A remote attacker can exploit this by supplying crafted path input to trigger arbitrary file reading, resulting in unauthorized access to sensitive files, potential information disclosure, and even Denial of Service via inclusion of large or resource-intensive files.",
            "cve": "CVE-2024-3429",
            "id": "pyup.io-78727",
            "more_info_path": "/vulnerabilities/CVE-2024-3429/78727",
            "specs": [
                "<9.5.0"
            ],
            "v": "<9.5.0"
        },
        {
            "advisory": "Affected versions of the lollms package are vulnerable to Command Injection due to insufficient sanitization of the `name` parameter in the `/unInstall_binding` endpoint. The `unInstall_binding` function fails to perform path sanitisation on the user-supplied `name` input, enabling directory traversal and execution of a malicious `__init__.py` file. A remote attacker can exploit this by invoking the `/unInstall_binding` endpoint with a crafted `name` value that causes arbitrary code execution on the hosting system.",
            "cve": "CVE-2024-4078",
            "id": "pyup.io-78726",
            "more_info_path": "/vulnerabilities/CVE-2024-4078/78726",
            "specs": [
                "<9.5.0"
            ],
            "v": "<9.5.0"
        },
        {
            "advisory": "Affected versions of the lollms package are vulnerable to Path Traversal due to improper validation of file paths containing backslashes. The `/user_infos` endpoint does not sufficiently sanitize backslash-containing paths across Windows and Linux environments, allowing directory traversal beyond the intended scope. An attacker can exploit this by crafting requests to `/user_infos` with a path like `\\windows\\win.ini`, enabling unauthorized access to sensitive files such as environment variables, database files, or configuration files on Windows systems.",
            "cve": "CVE-2024-4881",
            "id": "pyup.io-78739",
            "more_info_path": "/vulnerabilities/CVE-2024-4881/78739",
            "specs": [
                "<9.5.0"
            ],
            "v": "<9.5.0"
        },
        {
            "advisory": "Affected versions of Lollms are vulnerable to Remote File Inclusion. Lack of path sanitization for Windows leads to LFI.",
            "cve": "CVE-2024-4315",
            "id": "pyup.io-71745",
            "more_info_path": "/vulnerabilities/CVE-2024-4315/71745",
            "specs": [
                "<9.5.0"
            ],
            "v": "<9.5.0"
        },
        {
            "advisory": "Affected versions of the lollms package are vulnerable to Path Traversal due to insufficient sanitization of the discussion_db_name parameter by the sanitize_path function. The apply_settings function fails to properly validate the discussion_db_name, allowing specially crafted values containing directory traversal sequences to manipulate file paths. A local attacker can exploit this by invoking apply_settings with a malicious discussion_db_name to write files into sensitive system directories, potentially altering system configuration or disrupting service availability.",
            "cve": "CVE-2024-6281",
            "id": "pyup.io-78748",
            "more_info_path": "/vulnerabilities/CVE-2024-6281/78748",
            "specs": [
                "<9.5.1"
            ],
            "v": "<9.5.1"
        },
        {
            "advisory": "The parisneo/lollms repository is affected by a timing attack vulnerability in the `authenticate_user` function within the `lollms_authentication.py` file. This vulnerability allows attackers to enumerate valid usernames and guess passwords incrementally by analyzing response time differences. The affected version is the latest, and the issue is resolved in version 20.1. The vulnerability arises from the use of Python's default string equality operator for password comparison, which compares characters sequentially and exits on the first mismatch, leading to variable response times based on the number of matching initial characters.",
            "cve": "CVE-2025-6386",
            "id": "pyup.io-77991",
            "more_info_path": "/vulnerabilities/CVE-2025-6386/77991",
            "specs": [
                "<=11.0.0"
            ],
            "v": "<=11.0.0"
        },
        {
            "advisory": "Affected versions of the lollms package are vulnerable to Cross-site Scripting (XSS) due to incomplete sanitization of uploaded SVG image content. The `sanitize_svg` function used in the discussion image upload functionality removes only ` and then arbitrary HTML/JavaScript.",
            "cve": "CVE-2025-66469",
            "id": "pyup.io-82411",
            "more_info_path": "/vulnerabilities/CVE-2025-66469/82411",
            "specs": [
                "<3.4.0"
            ],
            "v": "<3.4.0"
        },
        {
            "advisory": "Affected versions of the NiceGUI package before 3.4.0 are vulnerable to Path Traversal due to insufficient validation of user-supplied file paths in the App.add_media_files() handler. The App.add_media_files(url_path, local_directory) method registers a GET endpoint that accepts a {filename:path} parameter and constructs the target path as Path(local_directory) / filename without sanitizing traversal sequences or enforcing that the resolved path remains inside the configured media directory.",
            "cve": "CVE-2025-66645",
            "id": "pyup.io-82413",
            "more_info_path": "/vulnerabilities/CVE-2025-66645/82413",
            "specs": [
                "<3.4.0"
            ],
            "v": "<3.4.0"
        },
        {
            "advisory": "NiceGUI is an easy-to-use, Python-based UI framework. A local file inclusion is present in the NiceUI leaflet component when requesting resource files under the `/_nicegui/{__version__}/resources/{key}/{path:path}` route. As a result any file on the backend filesystem which the web server has access to can be read by an attacker with access to the NiceUI leaflet website. This vulnerability has been addressed in version 1.4.21. Users are advised to upgrade. There are no known workarounds for this vulnerability. See CVE-2024-32005.",
            "cve": "CVE-2024-32005",
            "id": "pyup.io-70706",
            "more_info_path": "/vulnerabilities/CVE-2024-32005/70706",
            "specs": [
                ">=1.4.20,<=1.4.6"
            ],
            "v": ">=1.4.20,<=1.4.6"
        },
        {
            "advisory": "Affected versions of the nicegui package are vulnerable to Denial of Service (DoS) due to Redis connections not being released when Redis-backed tab storage is used. The issue occurs in nicegui.client.Client.handle_disconnect and nicegui.client.Client.delete, where tab_id is cleared before the tab\u2019s RedisPersistentDict can be found and cleaned up, so the Redis client connection and pubsub subscription created per tab are left open indefinitely.",
            "cve": "CVE-2026-21874",
            "id": "pyup.io-84328",
            "more_info_path": "/vulnerabilities/CVE-2026-21874/84328",
            "specs": [
                ">=2.10.0,<3.5.0"
            ],
            "v": ">=2.10.0,<3.5.0"
        },
        {
            "advisory": "Affected versions of the nicegui package are vulnerable to Cross-site Scripting (XSS) due to unescaped URL arguments being embedded into generated JavaScript. The issue occurs when ui.navigate.history.push(url) or ui.navigate.history.replace(url) receives attacker-controlled strings and interpolates the url value into emitted JavaScript without proper escaping, allowing the payload to break out of the intended string context.",
            "cve": "CVE-2026-21871",
            "id": "pyup.io-84325",
            "more_info_path": "/vulnerabilities/CVE-2026-21871/84325",
            "specs": [
                ">=2.13.0,<3.5.0"
            ],
            "v": ">=2.13.0,<3.5.0"
        },
        {
            "advisory": "Affected versions of the nicegui package are vulnerable to Cross-site Scripting (XSS) due to unsafe JavaScript string construction when navigating sub-pages from user-provided links. Specifically, ui.sub_pages emits the sub_pages_navigate event, and SubPagesRouter._handle_navigate calls run_javascript with an f-string that interpolates self.current_path inside double quotes without escaping, allowing an attacker-controlled path to break out of the string context and inject script.",
            "cve": "CVE-2026-21872",
            "id": "pyup.io-84326",
            "more_info_path": "/vulnerabilities/CVE-2026-21872/84326",
            "specs": [
                ">=2.22.0,<3.5.0"
            ],
            "v": ">=2.22.0,<3.5.0"
        },
        {
            "advisory": "Affected versions of the nicegui package are vulnerable to Cross-site Scripting (XSS) due to unsafe handling of attacker-controlled URL fragment identifiers in the ui.sub_pages pushstate flow. The nicegui/elements/sub_pages.js pushstate listener calls handleStateEvent, which emits sub_pages_open that SubPagesRouter in nicegui/sub_pages_router.py handles via _handle_open, ultimately reaching nicegui/elements/sub_pages.py where _handle_scrolling invokes _scroll_to_fragment and builds executable JavaScript using the unescaped fragment value.",
            "cve": "CVE-2026-21873",
            "id": "pyup.io-84327",
            "more_info_path": "/vulnerabilities/CVE-2026-21873/84327",
            "specs": [
                ">=2.22.0,<3.5.0"
            ],
            "v": ">=2.22.0,<3.5.0"
        }
    ],
    "niceml": [
        {
            "advisory": "Niceml 0.11.0 upgrades the pillow version to 10.1.0 to fix the CVE-2023-4863. \r\nhttps://github.com/codecentric-oss/niceml/pull/89/commits/c36c28cc3b5721b19520057403b8241bae7a4fc8#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711L47",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-63030",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/63030",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        },
        {
            "advisory": "Niceml 0.9.0 updates its dependency 'pillow' to versions \"^10.1.0\" to include security fixes.",
            "cve": "CVE-2023-44271",
            "id": "pyup.io-62522",
            "more_info_path": "/vulnerabilities/CVE-2023-44271/62522",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        }
    ],
    "niche-vlaanderen": [
        {
            "advisory": "Niche-Vlaanderen 1.1 includes a security patch for the function 'run_config_file' in 'niche_vlaanderen/niche.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/inbo/niche_vlaanderen/commit/cc1977d54a9267adf58bffbf0c275fb2c39bcfe8#diff-e87949fbb87229b550bad3c2ea146c46e0e1dc785be97a055eb067b3b3ec874b",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41352",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41352",
            "specs": [
                "<1.1"
            ],
            "v": "<1.1"
        }
    ],
    "nicotine-plus": [
        {
            "advisory": "Nicotine-plus 1.0.0pre3 includes a fix for a DoS vulnerability.",
            "cve": "PVE-2022-50466",
            "id": "pyup.io-50466",
            "more_info_path": "/vulnerabilities/PVE-2022-50466/50466",
            "specs": [
                "<1.0.0pre3"
            ],
            "v": "<1.0.0pre3"
        },
        {
            "advisory": "Nicotine-plus 1.0.0pre4 includes a fix for a potential distributed network attack.",
            "cve": "PVE-2022-50465",
            "id": "pyup.io-50465",
            "more_info_path": "/vulnerabilities/PVE-2022-50465/50465",
            "specs": [
                "<1.0.0pre4"
            ],
            "v": "<1.0.0pre4"
        },
        {
            "advisory": "Nicotine-plus 3.2.1 fixes a crash vulnerability when receiving a download request with a malformed file path.\r\nhttps://github.com/nicotine-plus/nicotine-plus/commit/0e3e2fac27a518f0a84330f1ddf1193424522045",
            "cve": "PVE-2022-44940",
            "id": "pyup.io-44940",
            "more_info_path": "/vulnerabilities/PVE-2022-44940/44940",
            "specs": [
                ">=3.0.3,<3.2.1"
            ],
            "v": ">=3.0.3,<3.2.1"
        },
        {
            "advisory": "Denial of service (DoS) vulnerability in Nicotine+ starting with version 3.0.3 and prior to version 3.2.1 allows a user with a modified Soulseek client to crash Nicotine+ by sending a file download request with a file path containing a null character.",
            "cve": "CVE-2021-45848",
            "id": "pyup.io-54424",
            "more_info_path": "/vulnerabilities/CVE-2021-45848/54424",
            "specs": [
                ">=3.0.3,<3.2.1"
            ],
            "v": ">=3.0.3,<3.2.1"
        }
    ],
    "nidaqmx": [
        {
            "advisory": "Nidaqmx 0.5.8 updates its dependency 'urllib3' to v1.25.9 to include security fixes.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-44702",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/44702",
            "specs": [
                "<0.5.8"
            ],
            "v": "<0.5.8"
        },
        {
            "advisory": "Nidaqmx 0.5.8 updates its dependency 'urllib3' to v1.25.9 to include security fixes.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-44704",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/44704",
            "specs": [
                "<0.5.8"
            ],
            "v": "<0.5.8"
        },
        {
            "advisory": "Nidaqmx 0.5.8 updates its dependency 'urllib3' to v1.25.9 to include security fixes.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-44703",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/44703",
            "specs": [
                "<0.5.8"
            ],
            "v": "<0.5.8"
        },
        {
            "advisory": "Nidaqmx 0.5.8 updates its dependency 'requests' to v2.23.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-44701",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/44701",
            "specs": [
                "<0.5.8"
            ],
            "v": "<0.5.8"
        },
        {
            "advisory": "Nidaqmx 0.5.8 updates its dependency 'jinja2' to v2.11.2 to include security fixes.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-44700",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/44700",
            "specs": [
                "<0.5.8"
            ],
            "v": "<0.5.8"
        },
        {
            "advisory": "Nidaqmx 0.5.8 updates its dependency 'jinja2' to v2.11.2 to include security fixes.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-44662",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/44662",
            "specs": [
                "<0.5.8"
            ],
            "v": "<0.5.8"
        },
        {
            "advisory": "Nidaqmx 0.5.8 updates its dependency 'urllib3' to v1.25.9 to include security fixes.",
            "cve": "CVE-2018-20060",
            "id": "pyup.io-44705",
            "more_info_path": "/vulnerabilities/CVE-2018-20060/44705",
            "specs": [
                "<0.5.8"
            ],
            "v": "<0.5.8"
        }
    ],
    "nifcloud": [
        {
            "advisory": "Nifcloud 0.1.7 updates its dependency 'requests' to v2.20.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-37098",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/37098",
            "specs": [
                "<0.1.7"
            ],
            "v": "<0.1.7"
        }
    ],
    "nikas": [
        {
            "advisory": "Nikas 2.0.0 updates its NPM dependency 'nanoid' to v3.3.1 to include a security fix.",
            "cve": "CVE-2021-23566",
            "id": "pyup.io-48523",
            "more_info_path": "/vulnerabilities/CVE-2021-23566/48523",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nikas 2.0.2 fixes potential security problems related to  caching malicious content on installation.\r\nhttps://github.com/Nikas-Project/Server/commit/1c3c9feeeb17d5ebe9ca96e4f70f2a2092d85b8a",
            "cve": "PVE-2022-49359",
            "id": "pyup.io-49359",
            "more_info_path": "/vulnerabilities/PVE-2022-49359/49359",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        }
    ],
    "nikola": [
        {
            "advisory": "Nikola version 8.3.1 addresses a directory traversal vulnerability within its nikola auto command, which stemmed from an issue in the aiottp library detailed in CVE-2024-23334.",
            "cve": "CVE-2024-23334",
            "id": "pyup.io-70558",
            "more_info_path": "/vulnerabilities/CVE-2024-23334/70558",
            "specs": [
                "<8.3.1"
            ],
            "v": "<8.3.1"
        }
    ],
    "nimview": [
        {
            "advisory": "Nimview 0.1.2 adds a (weak) CSRF check.\r\nhttps://github.com/marcomq/nimview/commit/e91ad0e656e75703c5101834c9fa86b12c1a22bf",
            "cve": "PVE-2021-41725",
            "id": "pyup.io-41725",
            "more_info_path": "/vulnerabilities/PVE-2021-41725/41725",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "nipyapi": [
        {
            "advisory": "Nipyapi 0.16.2 updates its dependency 'lxml' minimum version to v4.6.2 to include a security fix.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-42904",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/42904",
            "specs": [
                "<0.16.2"
            ],
            "v": "<0.16.2"
        }
    ],
    "niquests": [
        {
            "advisory": "Affected versions of the niquests package are vulnerable to improper certificate validation due to missing OCSP response signature verification against the issuer public key.",
            "cve": "PVE-2025-83135",
            "id": "pyup.io-83135",
            "more_info_path": "/vulnerabilities/PVE-2025-83135/83135",
            "specs": [
                "<3.15.0"
            ],
            "v": "<3.15.0"
        }
    ],
    "nitrokeyapp": [
        {
            "advisory": "Nitrokeyapp 1.0 addresses a critical security vulnerability present in earlier versions, where passwords were stored in plaintext in memory. This flaw posed a significant risk of unauthorized data access. \r\nhttps://github.com/Nitrokey/nitrokey-app/commit/c1c00c0081083c9722ea890b1f6f3f1e5fd26bfb",
            "cve": "PVE-2024-63550",
            "id": "pyup.io-63550",
            "more_info_path": "/vulnerabilities/PVE-2024-63550/63550",
            "specs": [
                "<1.0"
            ],
            "v": "<1.0"
        }
    ],
    "njmls": [
        {
            "advisory": "Njmls 0.0.3 includes a security patch for the function 'parse_row' in 'njmls.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/AlJohri/njmls/commit/a1b9aeca58512a4cba4262dc0233a6c8a14e26ab#diff-cc30712c59b1650a88a14f9c620608aaac65c3b1e35f006486ca7ec146f7f826",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41353",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41353",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        }
    ],
    "nkocr": [
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-44823",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/44823",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-44827",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/44827",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-44822",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/44822",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-44821",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/44821",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-40152",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/40152",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-44826",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/44826",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-44829",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/44829",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-44824",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/44824",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-44830",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/44830",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-44825",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/44825",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.0 updates its dependency 'pillow' to v8.1.2 to include security fixes.",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-44828",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/44828",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Nkocr 2.0.1 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-44820",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/44820",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        },
        {
            "advisory": "Nkocr 2.0.1 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-25288",
            "id": "pyup.io-40151",
            "more_info_path": "/vulnerabilities/CVE-2021-25288/40151",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        },
        {
            "advisory": "Nkocr 2.0.1 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-44819",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/44819",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        },
        {
            "advisory": "Nkocr 2.0.1 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28675",
            "id": "pyup.io-44817",
            "more_info_path": "/vulnerabilities/CVE-2021-28675/44817",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        },
        {
            "advisory": "Nkocr 2.0.1 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-25287",
            "id": "pyup.io-44816",
            "more_info_path": "/vulnerabilities/CVE-2021-25287/44816",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        },
        {
            "advisory": "Nkocr 2.0.1 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-44818",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/44818",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        }
    ],
    "nlohmann-json": [
        {
            "advisory": "Nlohmann-json 2.0.10 fixes a vulnerability that was found in the nlohmann JSON library. This vulnerability was identified as a heap-buffer-overflow error during parsing of CBOR data. It was specifically due to an unclosed UTF-8 string of undetermined length, which led to the buffer overflow 2.\r\nhttps://github.com/nlohmann/json/commit/cf9bf2d9136a9d1c2131f83aa493bb03f36849ab",
            "cve": "PVE-2024-64942",
            "id": "pyup.io-64942",
            "more_info_path": "/vulnerabilities/PVE-2024-64942/64942",
            "specs": [
                "<2.0.10"
            ],
            "v": "<2.0.10"
        },
        {
            "advisory": "Nlohmann-json 2.0.10 fixes a vulnerability discovered during continuous fuzz testing of the nlohmann JSON library by Google's OSS-Fuzz. It was identified as a heap-buffer-overflow error during the parsing of CBOR data.\r\nhttps://github.com/nlohmann/json/commit/871cebaf84d4f896bc730a92937f8d02e09b0023",
            "cve": "PVE-2024-64808",
            "id": "pyup.io-64808",
            "more_info_path": "/vulnerabilities/PVE-2024-64808/64808",
            "specs": [
                "<2.0.10"
            ],
            "v": "<2.0.10"
        }
    ],
    "nlsq": [
        {
            "advisory": "Affected versions of the nlsq package are potentially vulnerable to denial of service (uncontrolled resource consumption) due to missing input size validation for arrays and Jacobians.",
            "cve": "PVE-2025-82914",
            "id": "pyup.io-82914",
            "more_info_path": "/vulnerabilities/PVE-2025-82914/82914",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "nltk": [
        {
            "advisory": "Nltk 3.6 includes a fix for a REDoS vulnerability.\r\nhttps://github.com/nltk/nltk/pull/2597",
            "cve": "PVE-2023-54914",
            "id": "pyup.io-54914",
            "more_info_path": "/vulnerabilities/PVE-2023-54914/54914",
            "specs": [
                "<3.6"
            ],
            "v": "<3.6"
        },
        {
            "advisory": "Nltk 3.6.5 includes a fix for CVE-2021-43854: Versions prior to 3.6.5 are vulnerable to regular expression denial of service (ReDoS) attacks. The vulnerability is present in PunktSentenceTokenizer, sent_tokenize and word_tokenize. Any users of this class, or these two functions, are vulnerable to the ReDoS attack. In short, a specifically crafted long input to any of these vulnerable functions will cause them to take a significant amount of execution time. If your program relies on any of the vulnerable functions for tokenizing unpredictable user input, it's strongly recommended upgrading to a version of NLTK without the vulnerability. For users unable to upgrade the execution time can be bounded by limiting the maximum length of an input to any of the vulnerable functions.\r\nhttps://github.com/nltk/nltk/security/advisories/GHSA-f8m6-h2c7-8h9x\r\nhttps://github.com/nltk/nltk/issues/2866",
            "cve": "CVE-2021-43854",
            "id": "pyup.io-43622",
            "more_info_path": "/vulnerabilities/CVE-2021-43854/43622",
            "specs": [
                "<3.6.5"
            ],
            "v": "<3.6.5"
        },
        {
            "advisory": "Nltk 3.8.1 includes a security fix: A reflected XSS can be achieved by creating a URL, which leads to browser hijacking and sensitive information loss.",
            "cve": "PVE-2023-99957",
            "id": "pyup.io-60896",
            "more_info_path": "/vulnerabilities/PVE-2023-99957/60896",
            "specs": [
                "<3.8.1"
            ],
            "v": "<3.8.1"
        },
        {
            "advisory": "Before version 3.8.1 of nltk, if a user opens a malicious link while the wordnet browser is active, it can result in code execution on their system. Influence from a third party to visit a link can possibly lead to remote code execution (RCE).",
            "cve": "PVE-2023-99956",
            "id": "pyup.io-60897",
            "more_info_path": "/vulnerabilities/PVE-2023-99956/60897",
            "specs": [
                "<3.8.1"
            ],
            "v": "<3.8.1"
        },
        {
            "advisory": "Affected versions of NLTK are vulnerable to Remote Code Execution if untrusted packages have pickled Python code, and the integrated data package download functionality is used. This affects, for example, averaged_perceptron_tagger and punkt.",
            "cve": "CVE-2024-39705",
            "id": "pyup.io-72089",
            "more_info_path": "/vulnerabilities/CVE-2024-39705/72089",
            "specs": [
                "<3.9"
            ],
            "v": "<3.9"
        },
        {
            "advisory": "NLTK Downloader before 3.4.5 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a (dot dot slash) in an NLTK package (ZIP archive) that is mishandled during extraction.",
            "cve": "CVE-2019-14751",
            "id": "pyup.io-54680",
            "more_info_path": "/vulnerabilities/CVE-2019-14751/54680",
            "specs": [
                ">=0,<3.4.5"
            ],
            "v": ">=0,<3.4.5"
        },
        {
            "advisory": "Nltk before 3.6.4 is vulnerable to Inefficient Regular Expression Complexity.",
            "cve": "CVE-2021-3828",
            "id": "pyup.io-54696",
            "more_info_path": "/vulnerabilities/CVE-2021-3828/54696",
            "specs": [
                ">=0,<3.6.4"
            ],
            "v": ">=0,<3.6.4"
        },
        {
            "advisory": "Nltk before 3.6.6 is vulnerable to Inefficient Regular Expression Complexity.",
            "cve": "CVE-2021-3842",
            "id": "pyup.io-54703",
            "more_info_path": "/vulnerabilities/CVE-2021-3842/54703",
            "specs": [
                ">=0,<3.6.6"
            ],
            "v": ">=0,<3.6.6"
        }
    ],
    "nmap-python": [
        {
            "advisory": "Nmap-python is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45428",
            "id": "pyup.io-45428",
            "more_info_path": "/vulnerabilities/PVE-2022-45428/45428",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "nnabla": [
        {
            "advisory": "nbla/logger.cpp in libnnabla.a in Sony Neural Network Libraries (aka nnabla) through v1.0.14 relies on the HOME environment variable, which might be untrusted.",
            "cve": "CVE-2019-10844",
            "id": "pyup.io-54132",
            "more_info_path": "/vulnerabilities/CVE-2019-10844/54132",
            "specs": [
                ">=0,<1.0.15"
            ],
            "v": ">=0,<1.0.15"
        }
    ],
    "nni": [
        {
            "advisory": "Nni 2.1 includes a fix for YAML's CVE-2020-1747.\r\nhttps://github.com/microsoft/nni/commit/0e8a9f8272affb1b41d576bc06c9eb59e763bbc3",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-40661",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/40661",
            "specs": [
                "<2.1"
            ],
            "v": "<2.1"
        },
        {
            "advisory": "A Remote Code Execution vulnerability has been detected in the Common Utilities, a Python script component of the Neural Network Intelligence (NNI) open source toolkit, impacting all versions up to 2.3rc0.",
            "cve": "CVE-2021-31200",
            "id": "pyup.io-62206",
            "more_info_path": "/vulnerabilities/CVE-2021-31200/62206",
            "specs": [
                "<2.3rc0"
            ],
            "v": "<2.3rc0"
        }
    ],
    "nobinobi-child": [
        {
            "advisory": "Nobinobi-child 0.1.3.6 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-44958",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/44958",
            "specs": [
                "<0.1.3.6"
            ],
            "v": "<0.1.3.6"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.6 updates its dependency 'django' to v3.2.0 to include a security fix.",
            "cve": "CVE-2021-28658",
            "id": "pyup.io-44961",
            "more_info_path": "/vulnerabilities/CVE-2021-28658/44961",
            "specs": [
                "<0.1.3.6"
            ],
            "v": "<0.1.3.6"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.6 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28675",
            "id": "pyup.io-40196",
            "more_info_path": "/vulnerabilities/CVE-2021-28675/40196",
            "specs": [
                "<0.1.3.6"
            ],
            "v": "<0.1.3.6"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.6 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-44960",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/44960",
            "specs": [
                "<0.1.3.6"
            ],
            "v": "<0.1.3.6"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.6 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-44959",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/44959",
            "specs": [
                "<0.1.3.6"
            ],
            "v": "<0.1.3.6"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.8 updates its dependency 'django' to v3.2.10 to include security fixes.",
            "cve": "CVE-2021-31542",
            "id": "pyup.io-40626",
            "more_info_path": "/vulnerabilities/CVE-2021-31542/40626",
            "specs": [
                "<0.1.3.8"
            ],
            "v": "<0.1.3.8"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.8 updates its dependency 'django' to v3.2.10 to include security fixes.",
            "cve": "CVE-2021-33203",
            "id": "pyup.io-49106",
            "more_info_path": "/vulnerabilities/CVE-2021-33203/49106",
            "specs": [
                "<0.1.3.8"
            ],
            "v": "<0.1.3.8"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.8 updates its dependency 'django' to v3.2.10 to include security fixes.",
            "cve": "CVE-2021-33571",
            "id": "pyup.io-49105",
            "more_info_path": "/vulnerabilities/CVE-2021-33571/49105",
            "specs": [
                "<0.1.3.8"
            ],
            "v": "<0.1.3.8"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.8 updates its dependency 'django' to v3.2.10 to include security fixes.",
            "cve": "CVE-2021-44420",
            "id": "pyup.io-49108",
            "more_info_path": "/vulnerabilities/CVE-2021-44420/49108",
            "specs": [
                "<0.1.3.8"
            ],
            "v": "<0.1.3.8"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.8 updates its dependency 'django' to v3.2.10 to include security fixes.",
            "cve": "CVE-2021-32052",
            "id": "pyup.io-49104",
            "more_info_path": "/vulnerabilities/CVE-2021-32052/49104",
            "specs": [
                "<0.1.3.8"
            ],
            "v": "<0.1.3.8"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.8 updates its dependency 'pillow' to v8.4.0 to include security fixes.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-49110",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/49110",
            "specs": [
                "<0.1.3.8"
            ],
            "v": "<0.1.3.8"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.8 updates its dependency 'pillow' to v8.4.0 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-49109",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/49109",
            "specs": [
                "<0.1.3.8"
            ],
            "v": "<0.1.3.8"
        },
        {
            "advisory": "Nobinobi-child 0.1.3.8 updates its dependency 'django' to v3.2.10 to include security fixes.",
            "cve": "CVE-2021-35042",
            "id": "pyup.io-49107",
            "more_info_path": "/vulnerabilities/CVE-2021-35042/49107",
            "specs": [
                "<0.1.3.8"
            ],
            "v": "<0.1.3.8"
        }
    ],
    "nobinobi-core": [
        {
            "advisory": "Nobinobi-core 0.1.4.3 updates underlying 'Django' dependency to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-33571",
            "id": "pyup.io-43732",
            "more_info_path": "/vulnerabilities/CVE-2021-33571/43732",
            "specs": [
                "<0.1.4.3"
            ],
            "v": "<0.1.4.3"
        },
        {
            "advisory": "Nobinobi-core 0.1.4.3 updates underlying 'Django' dependency to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-35042",
            "id": "pyup.io-43730",
            "more_info_path": "/vulnerabilities/CVE-2021-35042/43730",
            "specs": [
                "<0.1.4.3"
            ],
            "v": "<0.1.4.3"
        },
        {
            "advisory": "Nobinobi-core 0.1.4.3 updates its dependency 'Django' to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-31542",
            "id": "pyup.io-40627",
            "more_info_path": "/vulnerabilities/CVE-2021-31542/40627",
            "specs": [
                "<0.1.4.3"
            ],
            "v": "<0.1.4.3"
        },
        {
            "advisory": "Nobinobi-core 0.1.4.3 updates its dependency 'Django' to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-32052",
            "id": "pyup.io-43733",
            "more_info_path": "/vulnerabilities/CVE-2021-32052/43733",
            "specs": [
                "<0.1.4.3"
            ],
            "v": "<0.1.4.3"
        },
        {
            "advisory": "Nobinobi-core 0.1.4.3 updates underlying 'Django' dependency to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-33203",
            "id": "pyup.io-43731",
            "more_info_path": "/vulnerabilities/CVE-2021-33203/43731",
            "specs": [
                "<0.1.4.3"
            ],
            "v": "<0.1.4.3"
        }
    ],
    "nobinobi-daily-follow-up": [
        {
            "advisory": "Nobinobi-daily-follow-up 0.1.1.12 updates its dependency 'django' to v3.2.4 to include security fixes.",
            "cve": "CVE-2021-33203",
            "id": "pyup.io-49103",
            "more_info_path": "/vulnerabilities/CVE-2021-33203/49103",
            "specs": [
                "<0.1.1.12"
            ],
            "v": "<0.1.1.12"
        },
        {
            "advisory": "Nobinobi-daily-follow-up 0.1.1.12 updates its dependency 'django' to v3.2.4 to include security fixes.",
            "cve": "CVE-2021-31542",
            "id": "pyup.io-40810",
            "more_info_path": "/vulnerabilities/CVE-2021-31542/40810",
            "specs": [
                "<0.1.1.12"
            ],
            "v": "<0.1.1.12"
        },
        {
            "advisory": "Nobinobi-daily-follow-up 0.1.1.12 updates its dependency 'django' to v3.2.4 to include security fixes.",
            "cve": "CVE-2021-33571",
            "id": "pyup.io-49102",
            "more_info_path": "/vulnerabilities/CVE-2021-33571/49102",
            "specs": [
                "<0.1.1.12"
            ],
            "v": "<0.1.1.12"
        },
        {
            "advisory": "Nobinobi-daily-follow-up 0.1.1.12 updates its dependency 'django' to v3.2.4 to include security fixes.",
            "cve": "CVE-2021-32052",
            "id": "pyup.io-49101",
            "more_info_path": "/vulnerabilities/CVE-2021-32052/49101",
            "specs": [
                "<0.1.1.12"
            ],
            "v": "<0.1.1.12"
        },
        {
            "advisory": "Nobinobi-daily-follow-up 0.1.1.9 updates its dependency 'Django' to v3.2.0 to include a security fix.",
            "cve": "CVE-2021-28658",
            "id": "pyup.io-40202",
            "more_info_path": "/vulnerabilities/CVE-2021-28658/40202",
            "specs": [
                "<0.1.1.9"
            ],
            "v": "<0.1.1.9"
        }
    ],
    "nobinobi-staff": [
        {
            "advisory": "Nobinobi-staff 0.1.6.2 updates its dependency 'Django' to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-35042",
            "id": "pyup.io-43391",
            "more_info_path": "/vulnerabilities/CVE-2021-35042/43391",
            "specs": [
                "<0.1.6.2"
            ],
            "v": "<0.1.6.2"
        },
        {
            "advisory": "Nobinobi-staff 0.1.6.2 updates its dependency 'Django' to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-32052",
            "id": "pyup.io-43378",
            "more_info_path": "/vulnerabilities/CVE-2021-32052/43378",
            "specs": [
                "<0.1.6.2"
            ],
            "v": "<0.1.6.2"
        },
        {
            "advisory": "Nobinobi-staff 0.1.6.2 updates its dependency 'Django' to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-33571",
            "id": "pyup.io-43390",
            "more_info_path": "/vulnerabilities/CVE-2021-33571/43390",
            "specs": [
                "<0.1.6.2"
            ],
            "v": "<0.1.6.2"
        },
        {
            "advisory": "Nobinobi-staff 0.1.6.2 updates its dependency 'Django' to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-31542",
            "id": "pyup.io-43387",
            "more_info_path": "/vulnerabilities/CVE-2021-31542/43387",
            "specs": [
                "<0.1.6.2"
            ],
            "v": "<0.1.6.2"
        },
        {
            "advisory": "Nobinobi-staff 0.1.6.2 updates its dependency 'Django' to v3.2.7 to include security fixes.",
            "cve": "CVE-2021-33203",
            "id": "pyup.io-43389",
            "more_info_path": "/vulnerabilities/CVE-2021-33203/43389",
            "specs": [
                "<0.1.6.2"
            ],
            "v": "<0.1.6.2"
        },
        {
            "advisory": "Nobinobi-staff 0.1.6.7 updates its dependency 'Django' to v4.0 to include a security fix.",
            "cve": "CVE-2021-44420",
            "id": "pyup.io-43388",
            "more_info_path": "/vulnerabilities/CVE-2021-44420/43388",
            "specs": [
                "<0.1.6.7"
            ],
            "v": "<0.1.6.7"
        }
    ],
    "noblesse": [
        {
            "advisory": "Noblesse is a malicious package, typosquatting. \"The aforementioned package could be abused to become an entry point for more sophisticated threats, enabling the attacker to execute remote code on the target machine, amass system information, plunder credit card information and passwords auto-saved in Chrome and Edge browsers, and even steal Discord authentication tokens to impersonate the victim\".\r\nhttps://thehackernews.com/2021/07/several-malicious-typosquatted-python.html",
            "cve": "PVE-2022-45448",
            "id": "pyup.io-45448",
            "more_info_path": "/vulnerabilities/PVE-2022-45448/45448",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "noblesse2": [
        {
            "advisory": "Noblesse2 is a malicious package, typosquatting. \"The aforementioned package could be abused to become an entry point for more sophisticated threats, enabling the attacker to execute remote code on the target machine, amass system information, plunder credit card information and passwords auto-saved in Chrome and Edge browsers, and even steal Discord authentication tokens to impersonate the victim\".\r\nhttps://thehackernews.com/2021/07/several-malicious-typosquatted-python.html",
            "cve": "PVE-2022-45452",
            "id": "pyup.io-45452",
            "more_info_path": "/vulnerabilities/PVE-2022-45452/45452",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "noblessev2": [
        {
            "advisory": "Noblessev2 is a malicious package, typosquatting. \"The aforementioned package could be abused to become an entry point for more sophisticated threats, enabling the attacker to execute remote code on the target machine, amass system information, plunder credit card information and passwords auto-saved in Chrome and Edge browsers, and even steal Discord authentication tokens to impersonate the victim\".\r\nhttps://thehackernews.com/2021/07/several-malicious-typosquatted-python.html",
            "cve": "PVE-2022-45453",
            "id": "pyup.io-45453",
            "more_info_path": "/vulnerabilities/PVE-2022-45453/45453",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "noiseprotocol": [
        {
            "advisory": "Noiseprotocol 0.2.1 updates its dependency 'cryptography' to v2.1.3 to include a safe version of OpenSSL.",
            "cve": "CVE-2017-3735",
            "id": "pyup.io-35043",
            "more_info_path": "/vulnerabilities/CVE-2017-3735/35043",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        },
        {
            "advisory": "Noiseprotocol 0.2.1 updates its dependency 'cryptography' to v2.1.3 to include a safe version of OpenSSL.",
            "cve": "CVE-2017-3736",
            "id": "pyup.io-50726",
            "more_info_path": "/vulnerabilities/CVE-2017-3736/50726",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "nonebot2": [
        {
            "advisory": "nonebot2 is a cross-platform Python asynchronous chatbot framework written in Python. This security advisory pertains to a potential information leak (e.g., environment variables) in instances where developers utilize `MessageTemplate` and incorporate user-provided data into templates. The identified vulnerability has been remedied in pull request #2509 and will be included in versions released from 2.2.0. Users are strongly advised to upgrade to these patched versions to safeguard against the vulnerability. A temporary workaround involves filtering underscores before incorporating user input into the message template. See CVE-2024-21624.",
            "cve": "CVE-2024-21624",
            "id": "pyup.io-65285",
            "more_info_path": "/vulnerabilities/CVE-2024-21624/65285",
            "specs": [
                ">=2.0.0a16,<=2.1.3"
            ],
            "v": ">=2.0.0a16,<=2.1.3"
        }
    ],
    "norfair": [
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "PVE-2021-44525",
            "id": "pyup.io-45358",
            "more_info_path": "/vulnerabilities/PVE-2021-44525/45358",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "PVE-2022-44524",
            "id": "pyup.io-45376",
            "more_info_path": "/vulnerabilities/PVE-2022-44524/45376",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-45359",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/45359",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-45370",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/45370",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-45362",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/45362",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-45367",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/45367",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-25287",
            "id": "pyup.io-45366",
            "more_info_path": "/vulnerabilities/CVE-2021-25287/45366",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-45364",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/45364",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-45368",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/45368",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-45363",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/45363",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-24303",
            "id": "pyup.io-45116",
            "more_info_path": "/vulnerabilities/CVE-2022-24303/45116",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-25288",
            "id": "pyup.io-45365",
            "more_info_path": "/vulnerabilities/CVE-2021-25288/45365",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-45360",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/45360",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-22817",
            "id": "pyup.io-45357",
            "more_info_path": "/vulnerabilities/CVE-2022-22817/45357",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-45371",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/45371",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-45369",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/45369",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-45374",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/45374",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-45372",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/45372",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-45361",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/45361",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-45373",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/45373",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Norfair 0.4.0 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-45375",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/45375",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "normcap": [
        {
            "advisory": "Normcap 0.1.1 pins its dependency 'PyInstaller' to a version >=3.6 to include a security fix.",
            "cve": "CVE-2019-16784",
            "id": "pyup.io-37722",
            "more_info_path": "/vulnerabilities/CVE-2019-16784/37722",
            "specs": [
                "<0.1.1"
            ],
            "v": "<0.1.1"
        },
        {
            "advisory": "Normcap 0.1.2 updates its dependency 'Bleach' to v3.1.1 to include a security fix.",
            "cve": "CVE-2020-6802",
            "id": "pyup.io-38132",
            "more_info_path": "/vulnerabilities/CVE-2020-6802/38132",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "nornir": [
        {
            "advisory": "Nornir 3.2.0 updates its dependency 'pygments' to v2.10.0 to include security fixes.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-42767",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/42767",
            "specs": [
                "<3.2.0"
            ],
            "v": "<3.2.0"
        },
        {
            "advisory": "Nornir 3.2.0 updates its dependency 'pygments' to v2.10.0 to include a security fix.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-42704",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/42704",
            "specs": [
                "<3.2.0"
            ],
            "v": "<3.2.0"
        }
    ],
    "notable": [
        {
            "advisory": "notable 0.0.6 fixes a security regression in the new BoltDB backend.",
            "cve": "PVE-2021-34447",
            "id": "pyup.io-34447",
            "more_info_path": "/vulnerabilities/PVE-2021-34447/34447",
            "specs": [
                "<0.0.6"
            ],
            "v": "<0.0.6"
        }
    ],
    "notebok": [
        {
            "advisory": "Notebok is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51747",
            "id": "pyup.io-51747",
            "more_info_path": "/vulnerabilities/PVE-2022-51747/51747",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "notebook": [
        {
            "advisory": "Notebook 4.0.5 includes security fixes for maliciously crafted files (CVE-2015-7337).",
            "cve": "CVE-2015-7337",
            "id": "pyup.io-40398",
            "more_info_path": "/vulnerabilities/CVE-2015-7337/40398",
            "specs": [
                "<4.0.5"
            ],
            "v": "<4.0.5"
        },
        {
            "advisory": "Notebook 4.0.5 includes security fixes for maliciously crafted files (CVE-2015-6938).",
            "cve": "CVE-2015-6938",
            "id": "pyup.io-40389",
            "more_info_path": "/vulnerabilities/CVE-2015-6938/40389",
            "specs": [
                "<4.0.5"
            ],
            "v": "<4.0.5"
        },
        {
            "advisory": "Notebook 4.2.2 includes a fix for CVE-2016-6524: Untrusted LaTeX output could be added to the page in a way that could execute javascript.",
            "cve": "CVE-2016-6524",
            "id": "pyup.io-40388",
            "more_info_path": "/vulnerabilities/CVE-2016-6524/40388",
            "specs": [
                "<4.2.2"
            ],
            "v": "<4.2.2"
        },
        {
            "advisory": "Notebook 4.3.1 includes a patch for a CSRF vulnerability.\r\nhttps://github.com/jupyter/notebook/pull/1969\r\nhttps://blog.jupyter.org/security-release-jupyter-notebook-4-3-1-808e1f3bb5e2",
            "cve": "CVE-2016-9971",
            "id": "pyup.io-34645",
            "more_info_path": "/vulnerabilities/CVE-2016-9971/34645",
            "specs": [
                "<4.3.1"
            ],
            "v": "<4.3.1"
        },
        {
            "advisory": "Notebook 5.4.1 adds a security release fix (CVE-2018-8768).",
            "cve": "CVE-2018-8768",
            "id": "pyup.io-40386",
            "more_info_path": "/vulnerabilities/CVE-2018-8768/40386",
            "specs": [
                "<5.4.1"
            ],
            "v": "<5.4.1"
        },
        {
            "advisory": "Jupyter Notebook before 5.7.1 allows XSS via an untrusted notebook because nbconvert responses are considered to have the same origin as the notebook server. In other words, nbconvert endpoints can execute JavaScript with access to the server API. In notebook/nbconvert/handlers.py, NbconvertFileHandler and NbconvertPostHandler do not set a Content Security Policy to prevent this.",
            "cve": "CVE-2018-19351",
            "id": "pyup.io-42253",
            "more_info_path": "/vulnerabilities/CVE-2018-19351/42253",
            "specs": [
                "<5.7.1"
            ],
            "v": "<5.7.1"
        },
        {
            "advisory": "Jupyter Notebook before 5.7.2 allows XSS via a crafted directory name because notebook/static/tree/js/notebooklist.js handles certain URLs unsafely.",
            "cve": "CVE-2018-19352",
            "id": "pyup.io-42254",
            "more_info_path": "/vulnerabilities/CVE-2018-19352/42254",
            "specs": [
                "<5.7.2"
            ],
            "v": "<5.7.2"
        },
        {
            "advisory": "Kiwi TCMS 6.4 updates Patternfly to version 3.59.0, which deals with an XSS issue in bootstrap (CVE-2018-14041). By default session cookies will expire after 24 hours. This can now be controlled via the ``SESSION_COOKIE_AGE`` setting. See https://github.com/kiwitcms/Kiwi/issues/556.",
            "cve": "CVE-2018-14041",
            "id": "pyup.io-40385",
            "more_info_path": "/vulnerabilities/CVE-2018-14041/40385",
            "specs": [
                "<5.7.3"
            ],
            "v": "<5.7.3"
        },
        {
            "advisory": "Notebook 5.7.6 includes a fix for vulnerability (CVE-2019-9644).",
            "cve": "CVE-2019-9644",
            "id": "pyup.io-40384",
            "more_info_path": "/vulnerabilities/CVE-2019-9644/40384",
            "specs": [
                "<5.7.6"
            ],
            "v": "<5.7.6"
        },
        {
            "advisory": "Notebook 5.7.8 fixes the 'Open Redirect' vulnerability (CVE-2019-10255).",
            "cve": "CVE-2019-10255",
            "id": "pyup.io-40383",
            "more_info_path": "/vulnerabilities/CVE-2019-10255/40383",
            "specs": [
                "<5.7.8"
            ],
            "v": "<5.7.8"
        },
        {
            "advisory": "Notebook 6.0.2 updates its dependency 'JQuery' to v3.5.0 to include a security fix.",
            "cve": "CVE-2019-11358",
            "id": "pyup.io-40381",
            "more_info_path": "/vulnerabilities/CVE-2019-11358/40381",
            "specs": [
                "<6.0.2"
            ],
            "v": "<6.0.2"
        },
        {
            "advisory": "Notebook 6.1.5 fixes open redirect vulnerability 'GHSA-c7vm-f5p4-8fqh'. See: CVE-2020-26215.\r\nhttps://github.com/advisories/GHSA-c7vm-f5p4-8fqh\r\nhttps://github.com/jupyter/notebook/pull/5874",
            "cve": "CVE-2020-26215",
            "id": "pyup.io-40380",
            "more_info_path": "/vulnerabilities/CVE-2020-26215/40380",
            "specs": [
                "<6.1.5"
            ],
            "v": "<6.1.5"
        },
        {
            "advisory": "Jupyter Notebook before 5.5.0 does not use a CSP header to treat served files as belonging to a separate origin. Thus, for example, an XSS payload can be placed in an SVG document.",
            "cve": "CVE-2018-21030",
            "id": "pyup.io-54682",
            "more_info_path": "/vulnerabilities/CVE-2018-21030/54682",
            "specs": [
                ">=0,<5.5.0"
            ],
            "v": ">=0,<5.5.0"
        },
        {
            "advisory": "The Jupyter notebook is a web-based notebook environment for interactive computing. In affected versions untrusted notebook can execute code on load. Jupyter Notebook uses a deprecated version of Google Caja to sanitize user inputs. A public Caja bypass can be used to trigger an XSS when a victim opens a malicious ipynb document in Jupyter Notebook. The XSS allows an attacker to execute arbitrary code on the victim computer using Jupyter APIs.",
            "cve": "CVE-2021-32798",
            "id": "pyup.io-54689",
            "more_info_path": "/vulnerabilities/CVE-2021-32798/54689",
            "specs": [
                ">=0,<5.7.11",
                ">=6.0.0,<6.4.1"
            ],
            "v": ">=0,<5.7.11,>=6.0.0,<6.4.1"
        },
        {
            "advisory": "In Jupyter Notebook before 5.7.8, an open redirect can occur via an empty netloc. This issue exists because of an incomplete fix for CVE-2019-10255.",
            "cve": "CVE-2019-10856",
            "id": "pyup.io-54678",
            "more_info_path": "/vulnerabilities/CVE-2019-10856/54678",
            "specs": [
                ">=0,<5.7.8"
            ],
            "v": ">=0,<5.7.8"
        },
        {
            "advisory": "The Jupyter notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.9, unauthorized actors can access sensitive information from server logs. Anytime a 5xx error is triggered, the auth cookie and other header values are recorded in Jupyter server logs by default. Considering these logs do not require root access, an attacker can monitor these logs, steal sensitive auth/cookie information, and gain access to the Jupyter server. Jupyter notebook version 6.4.x contains a patch for this issue. There are currently no known workarounds.",
            "cve": "CVE-2022-24758",
            "id": "pyup.io-54713",
            "more_info_path": "/vulnerabilities/CVE-2022-24758/54713",
            "specs": [
                ">=0,<6.4.10"
            ],
            "v": ">=0,<6.4.10"
        },
        {
            "advisory": "Jupyter Notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.12, authenticated requests to the notebook server with `ContentsManager.allow_hidden = False` only prevented listing the contents of hidden directories, not accessing individual hidden files or files in hidden directories (i.e. hidden files were 'hidden' but not 'inaccessible'). This could lead to notebook configurations allowing authenticated access to files that may reasonably be expected to be disallowed. Because fully authenticated requests are required, this is of relatively low impact. But if a server's root directory contains sensitive files whose only protection from the server is being hidden (e.g. `~/.ssh` while serving $HOME), then any authenticated requests could access files if their names are guessable. Such contexts also necessarily have full access to the server and therefore execution permissions, which also generally grants access to all the same files. So this does not generally result in any privilege escalation or increase in information access, only an additional, unintended means by which the files could be accessed. Version 6.4.12 contains a patch for this issue. There are currently no known workarounds.\r\nhttps://github.com/jupyter/notebook/security/advisories/GHSA-v7vq-3x77-87vg",
            "cve": "CVE-2022-29238",
            "id": "pyup.io-54684",
            "more_info_path": "/vulnerabilities/CVE-2022-29238/54684",
            "specs": [
                ">=0,<6.4.12"
            ],
            "v": ">=0,<6.4.12"
        },
        {
            "advisory": "CVE-2024-22420 describes a vulnerability in Jupyter Notebook, where user interaction with a malicious notebook or Markdown file enables an attacker to access and act with the same permissions as the user. The flaw lies in the table of contents plugin. Jupyter Notebook v7.0.7 includes a patch for this issue. Users can manually disable the plugin as a workaround. \r\nhttps://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-4m77-cmpx-vjc4",
            "cve": "CVE-2024-22420",
            "id": "pyup.io-65183",
            "more_info_path": "/vulnerabilities/CVE-2024-22420/65183",
            "specs": [
                ">=7.0.0,<=7.0.6"
            ],
            "v": ">=7.0.0,<=7.0.6"
        },
        {
            "advisory": "CVE-2024-22421 is a vulnerability in Jupyter Notebook where clicking a malicious link could expose Authorization and XSRFToken tokens to third parties in older jupyter-server versions. Patched versions include notebook above 7.0.7. Users are advised to upgrade jupyter-server to version 2.7.2 or newer, which includes a fix for a redirect vulnerability. No other workaround has been identified. \r\nhttps://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-44cc-43rp-5947",
            "cve": "CVE-2024-22421",
            "id": "pyup.io-65182",
            "more_info_path": "/vulnerabilities/CVE-2024-22421/65182",
            "specs": [
                ">=7.0.0,<=7.0.6"
            ],
            "v": ">=7.0.0,<=7.0.6"
        },
        {
            "advisory": "Jupyter Notebook is vulnerable to HTML injection, leading to DOM Clobbering, which allows attackers to access sensitive data and perform arbitrary actions as the compromised user. This vulnerability occurs when a user opens a malicious notebook with Markdown cells or a Markdown file in JupyterLab.",
            "cve": "CVE-2024-43805",
            "id": "pyup.io-72963",
            "more_info_path": "/vulnerabilities/CVE-2024-43805/72963",
            "specs": [
                ">=7.0.0,<=7.2.1"
            ],
            "v": ">=7.0.0,<=7.2.1"
        }
    ],
    "notebook-cat": [
        {
            "advisory": "Notebook-cat versions before 1.5.0 were potentially vulnerable to path traversal attacks due to the lack os protection, which was added on the commit e9b4b.",
            "cve": "PVE-2025-77196",
            "id": "pyup.io-77196",
            "more_info_path": "/vulnerabilities/PVE-2025-77196/77196",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        }
    ],
    "notifications-python-client": [
        {
            "advisory": "notifications-python-client before 4.7.1 is vulnerable to a not further described security issue in PyJWT.",
            "cve": "PVE-2021-35116",
            "id": "pyup.io-35116",
            "more_info_path": "/vulnerabilities/PVE-2021-35116/35116",
            "specs": [
                "<4.7.1"
            ],
            "v": "<4.7.1"
        }
    ],
    "notion-database": [
        {
            "advisory": "Notion-database 1.2.2 updates its dependency 'setuptools' to v74.1.2 to include a security fix.",
            "cve": "CVE-2024-6345",
            "id": "pyup.io-73117",
            "more_info_path": "/vulnerabilities/CVE-2024-6345/73117",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        }
    ],
    "notolog": [
        {
            "advisory": "Notolog 1.0.2 updates its dependency 'cryptography' to include a security fix.",
            "cve": "CVE-2024-4603",
            "id": "pyup.io-73478",
            "more_info_path": "/vulnerabilities/CVE-2024-4603/73478",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "nova": [
        {
            "advisory": "The image parser in OpenStack Cinder 7.0.2 and 8.0.0 through 8.1.1; Glance before 11.0.1 and 12.0.0; and Nova before 12.0.4 and 13.0.0 does not properly limit qemu-img calls, which might allow attackers to cause a denial of service (memory and disk consumption) via a crafted disk image.",
            "cve": "CVE-2015-5162",
            "id": "pyup.io-53780",
            "more_info_path": "/vulnerabilities/CVE-2015-5162/53780",
            "specs": [
                "<12.0.4",
                "==13.0.0"
            ],
            "v": "<12.0.4,==13.0.0"
        },
        {
            "advisory": "In OpenStack Nova through 14.0.9, 15.x through 15.0.7, and 16.x through 16.0.2, by rebuilding an instance, an authenticated user may be able to circumvent the Filter Scheduler bypassing imposed filters (for example, the ImagePropertiesFilter or the IsolatedHostsFilter). All setups using Nova Filter Scheduler are affected. Because of the regression described in Launchpad Bug #1732947, the preferred fix is a 14.x version after 14.0.10, a 15.x version after 15.0.8, or a 16.x version after 16.0.3.",
            "cve": "CVE-2017-16239",
            "id": "pyup.io-67536",
            "more_info_path": "/vulnerabilities/CVE-2017-16239/67536",
            "specs": [
                "<14.0.9",
                ">=15.0.0,<=15.0.7",
                ">=16.0.0,<=16.0.2"
            ],
            "v": "<14.0.9,>=15.0.0,<=15.0.7,>=16.0.0,<=16.0.2"
        },
        {
            "advisory": "Nova 17.0.12, 18.2.2 and 19.0.2 include a fix for CVE-2019-14433: An issue was discovered in OpenStack Nova before 17.0.12, 18.x before 18.2.2, and 19.x before 19.0.2. If an API request from an authenticated user ends in a fault condition due to an external exception, details of the underlying environment may be leaked in the response, and could include sensitive configuration or other data.",
            "cve": "CVE-2019-14433",
            "id": "pyup.io-37361",
            "more_info_path": "/vulnerabilities/CVE-2019-14433/37361",
            "specs": [
                "<17.0.12",
                ">=18.0.0.0rc1,<18.2.2",
                ">=19.0.0.0rc1,<19.0.2"
            ],
            "v": "<17.0.12,>=18.0.0.0rc1,<18.2.2,>=19.0.0.0rc1,<19.0.2"
        },
        {
            "advisory": "An issue was discovered in OpenStack Nova before 18.2.4, 19.x before 19.1.0, and 20.x before 20.1.0. It can leak consoleauth tokens into log files. An attacker with read access to the service's logs may obtain tokens used for console access. All Nova setups using novncproxy are affected. This is related to NovaProxyRequestHandlerBase.new_websocket_client in console/websocketproxy.py. See: CVE-2015-9543.",
            "cve": "CVE-2015-9543",
            "id": "pyup.io-37903",
            "more_info_path": "/vulnerabilities/CVE-2015-9543/37903",
            "specs": [
                "<18.2.4",
                ">=20.0.0.0rc1,<20.1.0",
                ">=19.0.0.0rc1,<19.1.0"
            ],
            "v": "<18.2.4,>=20.0.0.0rc1,<20.1.0,>=19.0.0.0rc1,<19.1.0"
        },
        {
            "advisory": "An issue was discovered in Guest.migrate in virt/libvirt/guest.py in OpenStack Nova before 19.3.1, 20.x before 20.3.1, and 21.0.0. By performing a soft reboot of an instance that has previously undergone live migration, a user may gain access to destination host devices that share the same paths as host devices previously referenced by the virtual machine on the source host. This can include block devices that map to different Cinder volumes at the destination than at the source. Only deployments allowing host-based connections (for instance, root and ephemeral devices) are affected. See: CVE-2020-17376.",
            "cve": "CVE-2020-17376",
            "id": "pyup.io-38722",
            "more_info_path": "/vulnerabilities/CVE-2020-17376/38722",
            "specs": [
                "<19.3.1",
                ">=20.0.0.0rc1,<20.3.1",
                "==21.0.0"
            ],
            "v": "<19.3.1,>=20.0.0.0rc1,<20.3.1,==21.0.0"
        },
        {
            "advisory": "Nova versions 23.2.2, 24.1.2 and 25.0.2 include a fix for CVE-2022-37394: An issue was discovered in OpenStack Nova before 23.2.2, 24.x before 24.1.2, and 25.x before 25.0.2. By creating a neutron port with the direct vnic_type, creating an instance bound to that port, and then changing the vnic_type of the bound port to macvtap, an authenticated user may cause the compute service to fail to restart, resulting in a possible denial of service. Only Nova deployments configured with SR-IOV are affected.",
            "cve": "CVE-2022-37394",
            "id": "pyup.io-50455",
            "more_info_path": "/vulnerabilities/CVE-2022-37394/50455",
            "specs": [
                "<23.2.2",
                ">=24.0.0.0rc1,<24.1.2",
                ">=25.0.0.0rc1,<25.0.2"
            ],
            "v": "<23.2.2,>=24.0.0.0rc1,<24.1.2,>=25.0.0.0rc1,<25.0.2"
        },
        {
            "advisory": "Nova 24.0.0 includes a fix for CVE-2021-3654: A vulnerability was found in openstack-nova's console proxy, noVNC. By crafting a malicious URL, noVNC could be made to redirect to any desired URL.\r\nhttps://github.com/openstack/nova/commit/781612b33282ed298f742c85dab58a075c8b793e",
            "cve": "CVE-2021-3654",
            "id": "pyup.io-45513",
            "more_info_path": "/vulnerabilities/CVE-2021-3654/45513",
            "specs": [
                "<24.0.0"
            ],
            "v": "<24.0.0"
        },
        {
            "advisory": "Nova 24.1.2, 25.0.2 and 26.0.0 include a fix for CVE-2022-47951: An issue was discovered in OpenStack Cinder before 19.1.2, 20.x before 20.0.2, and 21.0.0; Glance before 23.0.1, 24.x before 24.1.1, and 25.0.0; and Nova before 24.1.2, 25.x before 25.0.2, and 26.0.0. By supplying a specially created VMDK flat image that references a specific backing file path, an authenticated user may convince systems to return a copy of that file's contents from the server, resulting in unauthorized access to potentially sensitive data.",
            "cve": "CVE-2022-47951",
            "id": "pyup.io-52932",
            "more_info_path": "/vulnerabilities/CVE-2022-47951/52932",
            "specs": [
                "<24.1.2",
                ">=25.0.0.0rc1,<25.0.2",
                ">=26.0.0.0rc1,<26.0.0"
            ],
            "v": "<24.1.2,>=25.0.0.0rc1,<25.0.2,>=26.0.0.0rc1,<26.0.0"
        },
        {
            "advisory": "Nova 27.1.0, 26.2.0 and 25.2.0 include a fix for CVE-2023-2088: A flaw was found in OpenStack due to an inconsistency between Cinder and Nova. This issue can be triggered intentionally or by accident. A remote, authenticated attacker could exploit this vulnerability by detaching one of their volumes from Cinder. The highest impact is to confidentiality.\r\nhttps://opendev.org/openstack/nova/commit/db455548a12beac1153ce04eca5e728d7b773901",
            "cve": "CVE-2023-2088",
            "id": "pyup.io-58668",
            "more_info_path": "/vulnerabilities/CVE-2023-2088/58668",
            "specs": [
                "<25.2.0",
                ">=26.0.0.0rc1,<26.2.0",
                ">=27.0.0.0rc1,<27.1.0"
            ],
            "v": "<25.2.0,>=26.0.0.0rc1,<26.2.0,>=27.0.0.0rc1,<27.1.0"
        },
        {
            "advisory": "An security flaw in affected versions of OpenStack Nova allows arbitrary file access via custom QCOW2 external data. An authenticated user can supply a crafted QCOW2 image that references a specific data file path, convincing systems to return a copy of that file's contents from the server. This results in unauthorized access to potentially sensitive data.",
            "cve": "CVE-2024-32498",
            "id": "pyup.io-72149",
            "more_info_path": "/vulnerabilities/CVE-2024-32498/72149",
            "specs": [
                "<30.0.0.0rc1"
            ],
            "v": "<30.0.0.0rc1"
        },
        {
            "advisory": "In OpenStack Nova affected versions, by supplying a raw format image that is a crafted QCOW2 image with a backing file path or VMDK flat image with a descriptor file path, an authenticated user may convince systems to return a copy of the referenced file's contents from the server, resulting in unauthorized access to potentially sensitive data. All Nova deployments are affected. NOTE: this issue exists because of an incomplete fix for CVE-2022-47951 and CVE-2024-32498.",
            "cve": "CVE-2024-40767",
            "id": "pyup.io-72371",
            "more_info_path": "/vulnerabilities/CVE-2024-40767/72371",
            "specs": [
                "<=27.4.0",
                ">=28.0.0,<=28.2.0",
                ">=29.0.0,<=29.1.0"
            ],
            "v": "<=27.4.0,>=28.0.0,<=28.2.0,>=29.0.0,<=29.1.0"
        },
        {
            "advisory": "An issue was discovered in the default FilterScheduler in OpenStack Nova 16.0.3. By repeatedly rebuilding an instance with new images, an authenticated user may consume untracked resources on a hypervisor host leading to a denial of service, aka doubled resource allocations. This regression was introduced with the fix for OSSA-2017-005 (CVE-2017-16239); however, only Nova stable/pike or later deployments with that fix applied and relying on the default FilterScheduler are affected.",
            "cve": "CVE-2017-17051",
            "id": "pyup.io-67537",
            "more_info_path": "/vulnerabilities/CVE-2017-17051/67537",
            "specs": [
                "==15.1.5",
                ">=16.0.3,<16.0.4"
            ],
            "v": "==15.1.5,>=16.0.3,<16.0.4"
        },
        {
            "advisory": "OpenStack nova base images permissions are world readable. No fixes or affected versions are known. See: CVE-2013-0326.",
            "cve": "CVE-2013-0326",
            "id": "pyup.io-37745",
            "more_info_path": "/vulnerabilities/CVE-2013-0326/37745",
            "specs": [
                ">0"
            ],
            "v": ">0"
        },
        {
            "advisory": "The \"create an instance\" API in OpenStack Compute (Nova) Folsom, Grizzly, and Havana does not properly enforce the os-flavor-access:is_public property, which allows remote authenticated users to boot arbitrary flavors by guessing the flavor id. NOTE: this issue is due to an incomplete fix for CVE-2013-2256.",
            "cve": "CVE-2013-4278",
            "id": "pyup.io-70564",
            "more_info_path": "/vulnerabilities/CVE-2013-4278/70564",
            "specs": [
                ">2010,<2013.2"
            ],
            "v": ">2010,<2013.2"
        },
        {
            "advisory": "The VMWare driver in OpenStack Compute (Nova) 2013.2 through 2013.2.2 does not properly put VMs into RESCUE status, which allows remote authenticated users to bypass the quota limit and cause a denial of service (resource consumption) by requesting the VM be put into rescue and then deleting the image.",
            "cve": "CVE-2014-2573",
            "id": "pyup.io-70460",
            "more_info_path": "/vulnerabilities/CVE-2014-2573/70460",
            "specs": [
                ">2010,<2013.2.4"
            ],
            "v": ">2010,<2013.2.4"
        },
        {
            "advisory": "The strutils.mask_password function in the OpenStack Oslo utility library, Cinder, Nova, and Trove before 2013.2.4 and 2014.1 before 2014.1.3 does not properly mask passwords when logging commands, which allows local users to obtain passwords by reading the log.",
            "cve": "CVE-2014-7231",
            "id": "pyup.io-70431",
            "more_info_path": "/vulnerabilities/CVE-2014-7231/70431",
            "specs": [
                ">2010,<=2014.1.5"
            ],
            "v": ">2010,<=2014.1.5"
        },
        {
            "advisory": "OpenStack Compute (Nova) before 2015.1.3 (kilo) and 12.0.x before 12.0.1 (liberty), when using libvirt to spawn instances and use_cow_images is set to false, allow remote authenticated users to read arbitrary files by overwriting an instance disk with a crafted image and requesting a snapshot.",
            "cve": "CVE-2015-7548",
            "id": "pyup.io-70437",
            "more_info_path": "/vulnerabilities/CVE-2015-7548/70437",
            "specs": [
                ">=12.0.0,<12.0.1",
                ">=2010,<2015.1.3"
            ],
            "v": ">=12.0.0,<12.0.1,>=2010,<2015.1.3"
        },
        {
            "advisory": "The volume_utils._parse_volume_info function in OpenStack Compute (Nova) before 2015.1.3 (kilo) and 12.0.x before 12.0.1 (liberty) includes the connection_info dictionary in the StorageError message when using the Xen backend, which might allow attackers to obtain sensitive password information by reading log files or other unspecified vectors.",
            "cve": "CVE-2015-8749",
            "id": "pyup.io-70436",
            "more_info_path": "/vulnerabilities/CVE-2015-8749/70436",
            "specs": [
                ">=12.0.0,<12.0.1",
                ">=2010,<2015.1.3"
            ],
            "v": ">=12.0.0,<12.0.1,>=2010,<2015.1.3"
        },
        {
            "advisory": "The libvirt driver in OpenStack Compute (Nova) before 2015.1.4 (kilo) and 12.0.x before 12.0.3 (liberty), when using raw storage and use_cow_images is set to false, allows remote authenticated users to read arbitrary files via a crafted qcow2 header in an ephemeral or root disk.",
            "cve": "CVE-2016-2140",
            "id": "pyup.io-70525",
            "more_info_path": "/vulnerabilities/CVE-2016-2140/70525",
            "specs": [
                ">=12.0.0,<12.0.3",
                ">=2010,<2015.1.4"
            ],
            "v": ">=12.0.0,<12.0.3,>=2010,<2015.1.4"
        },
        {
            "advisory": "An issue was discovered in exception_wrapper.py in OpenStack Nova 13.x through 13.1.3, 14.x through 14.0.4, and 15.x through 15.0.1. Legacy notification exception contexts appearing in ERROR level logs may include sensitive information such as account passwords and authorization tokens.",
            "cve": "CVE-2017-7214",
            "id": "pyup.io-67542",
            "more_info_path": "/vulnerabilities/CVE-2017-7214/67542",
            "specs": [
                ">=13.0.0,<=13.1.3",
                ">=14.0.0,<=14.0.4",
                ">=15.0.0,<=15.0.1"
            ],
            "v": ">=13.0.0,<=13.1.3,>=14.0.0,<=14.0.4,>=15.0.0,<=15.0.1"
        },
        {
            "advisory": "An issue was discovered in OpenStack Nova 15.x through 15.1.0 and 16.x through 16.1.1. By detaching and reattaching an encrypted volume, an attacker may access the underlying raw volume and corrupt the LUKS header, resulting in a denial of service attack on the compute host. (The same code error also results in data loss, but that is not a vulnerability because the user loses their own data.) All Nova setups supporting encrypted volumes are affected.",
            "cve": "CVE-2017-18191",
            "id": "pyup.io-67540",
            "more_info_path": "/vulnerabilities/CVE-2017-18191/67540",
            "specs": [
                ">=15.0.0,<=15.1.0",
                ">=16.0.0,<=16.1.1"
            ],
            "v": ">=15.0.0,<=15.1.0,>=16.0.0,<=16.1.1"
        },
        {
            "advisory": "Versions of nova before 2012.1 could expose hypervisor host files to a guest operating system when processing a maliciously constructed qcow filesystem. See: CVE-2011-3147.",
            "cve": "CVE-2011-3147",
            "id": "pyup.io-37087",
            "more_info_path": "/vulnerabilities/CVE-2011-3147/37087",
            "specs": [
                ">=2000,<2012.1"
            ],
            "v": ">=2000,<2012.1"
        },
        {
            "advisory": "OpenStack Nova before 2012.1 allows someone with access to an EC2_ACCESS_KEY (equivalent to a username) to obtain the EC2_SECRET_KEY (equivalent to a password). Exposing the EC2_ACCESS_KEY via http or tools that allow man-in-the-middle over https could allow an attacker to easily obtain the EC2_SECRET_KEY. An attacker could also presumably brute force values for EC2_ACCESS_KEY. See CVE-2011-4076.",
            "cve": "CVE-2011-4076",
            "id": "pyup.io-37736",
            "more_info_path": "/vulnerabilities/CVE-2011-4076/37736",
            "specs": [
                ">=2000,<2012.1"
            ],
            "v": ">=2000,<2012.1"
        },
        {
            "advisory": "The OpenStack Nova (python-nova) package 1:2013.2.3-0 before 1:2013.2.3-0ubuntu1.2 and 1:2014.1-0 before 1:2014.1-0ubuntu1.2 and Openstack Cinder (python-cinder) package 1:2013.2.3-0 before 1:2013.2.3-0ubuntu1.1 and 1:2014.1-0 before 1:2014.1-0ubuntu1.1 for Ubuntu 13.10 and 14.04 LTS does not properly set the sudo configuration, which makes it easier for attackers to gain privileges by leveraging another vulnerability.",
            "cve": "CVE-2013-1068",
            "id": "pyup.io-25905",
            "more_info_path": "/vulnerabilities/CVE-2013-1068/25905",
            "specs": [
                ">=2000,<2013.2.3"
            ],
            "v": ">=2000,<2013.2.3"
        },
        {
            "advisory": "The security group extension in OpenStack Compute (Nova) Grizzly 2013.1.3, Havana before havana-3, and earlier allows remote attackers to cause a denial of service (resource consumption and crash) via an XML Entity Expansion (XEE) attack. NOTE: this issue is due to an incomplete fix for CVE-2013-1664.",
            "cve": "CVE-2013-4179",
            "id": "pyup.io-35437",
            "more_info_path": "/vulnerabilities/CVE-2013-4179/35437",
            "specs": [
                ">=2010,<2013.1.3"
            ],
            "v": ">=2010,<2013.1.3"
        },
        {
            "advisory": "OpenStack Compute (Nova) before 2013.1.3 and Havana before havana-2 does not properly enforce the os-flavor-access:is_public property, which allows remote authenticated users to obtain sensitive information (flavor properties), boot arbitrary flavors, and possibly have other unspecified impacts by guessing the flavor id.",
            "cve": "CVE-2013-2256",
            "id": "pyup.io-35434",
            "more_info_path": "/vulnerabilities/CVE-2013-2256/35434",
            "specs": [
                ">=2010,<2013.1.3"
            ],
            "v": ">=2010,<2013.1.3"
        },
        {
            "advisory": "api/metadata/handler.py in OpenStack Compute (Nova) before 2013.2.4, 2014.x before 2014.1.2, and Juno before Juno-2, when proxying metadata requests through Neutron, makes it easier for remote attackers to guess instance ID signatures via a brute-force attack that relies on timing differences in responses to instance metadata requests.",
            "cve": "CVE-2014-3517",
            "id": "pyup.io-35556",
            "more_info_path": "/vulnerabilities/CVE-2014-3517/35556",
            "specs": [
                ">=2010,<2013.2.4",
                ">=2014,<2014.1.2"
            ],
            "v": ">=2010,<2013.2.4,>=2014,<2014.1.2"
        },
        {
            "advisory": "The VMWare driver in OpenStack Compute (Nova) before 2014.1.3 allows remote authenticated users to bypass the quota limit and cause a denial of service (resource consumption) by putting the VM into the rescue state, suspending it, which puts into an ERROR state, and then deleting the image. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-2573.",
            "cve": "CVE-2014-3608",
            "id": "pyup.io-35563",
            "more_info_path": "/vulnerabilities/CVE-2014-3608/35563",
            "specs": [
                ">=2010,<2014.1.3"
            ],
            "v": ">=2010,<2014.1.3"
        },
        {
            "advisory": "OpenStack Compute (Nova) before 2014.1.4, 2014.2.x before 2014.2.3, and kilo before kilo-3 does not validate the origin of websocket requests, which allows remote attackers to hijack the authentication of users for access to consoles via a crafted webpage.",
            "cve": "CVE-2015-0259",
            "id": "pyup.io-35599",
            "more_info_path": "/vulnerabilities/CVE-2015-0259/35599",
            "specs": [
                ">=2010,<2014.1.4",
                ">=2014.2,<2014.2.3"
            ],
            "v": ">=2010,<2014.1.4,>=2014.2,<2014.2.3"
        },
        {
            "advisory": "OpenStack Compute (Nova) before 2014.2.4 (juno) and 2015.1.x before 2015.1.2 (kilo) do not properly apply security group changes, which allows remote attackers to bypass intended restriction by leveraging an instance that was running when the change was made.",
            "cve": "CVE-2015-7713",
            "id": "pyup.io-35650",
            "more_info_path": "/vulnerabilities/CVE-2015-7713/35650",
            "specs": [
                ">=2010,<2014.2.4",
                ">=2015.1,<2015.1.2"
            ],
            "v": ">=2010,<2014.2.4,>=2015.1,<2015.1.2"
        },
        {
            "advisory": "OpenStack Compute (nova) before 2014.2.4 (juno) and 2015.1.x before 2015.1.2 (kilo) does not properly delete instances from compute nodes, which allows remote authenticated users to cause a denial of service (disk consumption) by deleting instances while in the resize state.",
            "cve": "CVE-2015-3280",
            "id": "pyup.io-35617",
            "more_info_path": "/vulnerabilities/CVE-2015-3280/35617",
            "specs": [
                ">=2010,<2014.2.4",
                ">=2015.1,<2015.1.2"
            ],
            "v": ">=2010,<2014.2.4,>=2015.1,<2015.1.2"
        },
        {
            "advisory": "The instance rescue mode in OpenStack Compute (Nova) 2013.2 before 2013.2.3 and Icehouse before 2014.1, when using libvirt to spawn images and use_cow_images is set to false, allows remote authenticated users to read certain compute host files by overwriting an instance disk with a crafted image.",
            "cve": "CVE-2014-0134",
            "id": "pyup.io-68020",
            "more_info_path": "/vulnerabilities/CVE-2014-0134/68020",
            "specs": [
                ">=2010.1-rc2,<2013",
                ">=2013.2,<2013.2.3",
                ">=2014,<2014.1"
            ],
            "v": ">=2010.1-rc2,<2013,>=2013.2,<2013.2.3,>=2014,<2014.1"
        },
        {
            "advisory": "The boot-from-volume feature in OpenStack Compute (Nova) Folsom and Essex, when using nova-volumes, allows remote authenticated users to boot from other users' volumes via a volume id in the block_device_mapping parameter.",
            "cve": "CVE-2013-0208",
            "id": "pyup.io-68025",
            "more_info_path": "/vulnerabilities/CVE-2013-0208/68025",
            "specs": [
                ">=2010.1-rc2,<2013.1.1"
            ],
            "v": ">=2010.1-rc2,<2013.1.1"
        },
        {
            "advisory": "Algorithmic complexity vulnerability in OpenStack Compute (Nova) before 2013.1.3 and Havana before havana-3 does not properly handle network source security group policy updates, which allows remote authenticated users to cause a denial of service (nova-network consumption) via a large number of server-creation operations, which triggers a large number of update requests.",
            "cve": "CVE-2013-4185",
            "id": "pyup.io-68029",
            "more_info_path": "/vulnerabilities/CVE-2013-4185/68029",
            "specs": [
                ">=2010.1-rc2,<2013.2.3"
            ],
            "v": ">=2010.1-rc2,<2013.2.3"
        },
        {
            "advisory": "XML injection vulnerability in account/utils.py in OpenStack Swift Folsom, Grizzly, and Havana allows attackers to trigger invalid or spoofed Swift responses via an account name.",
            "cve": "CVE-2013-2161",
            "id": "pyup.io-68030",
            "more_info_path": "/vulnerabilities/CVE-2013-2161/68030",
            "specs": [
                ">=2010.1-rc2,<2014"
            ],
            "v": ">=2010.1-rc2,<2014"
        },
        {
            "advisory": "Openstack Compute (Nova) Folsom, 2012.1, and 2011.3 does not limit the number of security group rules, which allows remote authenticated users with certain permissions to cause a denial of service (CPU and hard drive consumption) via a network request that triggers a large number of iptables rules.",
            "cve": "CVE-2012-2101",
            "id": "pyup.io-68028",
            "more_info_path": "/vulnerabilities/CVE-2012-2101/68028",
            "specs": [
                ">=2010.1-rc2,<=2012.1"
            ],
            "v": ">=2010.1-rc2,<=2012.1"
        },
        {
            "advisory": "Nova 2011.3 and Essex, when using the OpenStack API, allows remote authenticated users to bypass access restrictions for tenants of other users via an OSAPI request with a modified project_id URI parameter.",
            "cve": "CVE-2012-0030",
            "id": "pyup.io-68027",
            "more_info_path": "/vulnerabilities/CVE-2012-0030/68027",
            "specs": [
                ">=2010.1-rc2,<=2012.1.3"
            ],
            "v": ">=2010.1-rc2,<=2012.1.3"
        },
        {
            "advisory": "The Nova scheduler in OpenStack Compute (Nova) Folsom (2012.2) and Essex (2012.1), when DifferentHostFilter or SameHostFilter is enabled, allows remote authenticated users to cause a denial of service (excessive database lookup calls and server hang) via a request with many repeated IDs in the os:scheduler_hints section.",
            "cve": "CVE-2012-3371",
            "id": "pyup.io-68023",
            "more_info_path": "/vulnerabilities/CVE-2012-3371/68023",
            "specs": [
                ">=2010.1-rc2,<=2012.2"
            ],
            "v": ">=2010.1-rc2,<=2012.2"
        },
        {
            "advisory": "The (1) EC2 and (2) OS APIs in OpenStack Compute (Nova) Folsom (2012.2), Essex (2012.1), and Diablo (2011.3) do not properly check the protocol when security groups are created and the network protocol is not specified entirely in lowercase, which allows remote attackers to bypass intended access restrictions.",
            "cve": "CVE-2012-2654",
            "id": "pyup.io-68021",
            "more_info_path": "/vulnerabilities/CVE-2012-2654/68021",
            "specs": [
                ">=2010.1-rc2,<=2012.2"
            ],
            "v": ">=2010.1-rc2,<=2012.2"
        },
        {
            "advisory": "OpenStack Compute (Nova) Folsom before 2012.2.2 and Grizzly, when using libvirt and LVM backed instances, does not properly clear physical volume (PV) content when reallocating for instances, which allows attackers to obtain sensitive information by reading the memory of the previous logical volume (LV).",
            "cve": "CVE-2012-5625",
            "id": "pyup.io-68024",
            "more_info_path": "/vulnerabilities/CVE-2012-5625/68024",
            "specs": [
                ">=2010.1-rc2,<=2012.2.2"
            ],
            "v": ">=2010.1-rc2,<=2012.2.2"
        },
        {
            "advisory": "OpenStack Compute (Nova) Folsom, Grizzly, and Havana does not properly verify the virtual size of a QCOW2 image, which allows local users to cause a denial of service (host file system disk consumption) via a compressed QCOW2 image. NOTE: this issue is due to an incomplete fix for CVE-2013-2096.",
            "cve": "CVE-2013-4463",
            "id": "pyup.io-68026",
            "more_info_path": "/vulnerabilities/CVE-2013-4463/68026",
            "specs": [
                ">=2010.1-rc2,<=2013.2.4"
            ],
            "v": ">=2010.1-rc2,<=2013.2.4"
        },
        {
            "advisory": "OpenStack Compute (Nova) Essex before 2011.3 allows remote authenticated users to cause a denial of service (Nova-API log file and disk consumption) via a long server name.",
            "cve": "CVE-2012-1585",
            "id": "pyup.io-67999",
            "more_info_path": "/vulnerabilities/CVE-2012-1585/67999",
            "specs": [
                ">=2011.1,<2011.3"
            ],
            "v": ">=2011.1,<2011.3"
        },
        {
            "advisory": "Multiple directory traversal vulnerabilities in OpenStack Nova before 2011.3.1, when the EC2 API and the S3/RegisterImage image-registration method are enabled, allow remote authenticated users to overwrite arbitrary files via a crafted (1) tarball or (2) manifest.",
            "cve": "CVE-2011-4596",
            "id": "pyup.io-62097",
            "more_info_path": "/vulnerabilities/CVE-2011-4596/62097",
            "specs": [
                ">=2011.3,<2011.3.1"
            ],
            "v": ">=2011.3,<2011.3.1"
        },
        {
            "advisory": "OpenStack Compute (Nova) Grizzly, Folsom (2012.2), and Essex (2012.1) allows remote authenticated users to gain access to a VM in opportunistic circumstances by using the VNC token for a deleted VM that was bound to the same VNC port.",
            "cve": "CVE-2013-0335",
            "id": "pyup.io-67983",
            "more_info_path": "/vulnerabilities/CVE-2013-0335/67983",
            "specs": [
                ">=2012,<2013.1.g3"
            ],
            "v": ">=2012,<2013.1.g3"
        },
        {
            "advisory": "OpenStack Compute (Nova) Grizzly, Folsom (2012.2), and Essex (2012.1) does not properly implement a quota for fixed IPs, which allows remote authenticated users to cause a denial of service (resource exhaustion and failure to spawn new instances) via a large number of calls to the addFixedIp function.",
            "cve": "CVE-2013-1838",
            "id": "pyup.io-67986",
            "more_info_path": "/vulnerabilities/CVE-2013-1838/67986",
            "specs": [
                ">=2012,<=2012.2"
            ],
            "v": ">=2012,<=2012.2"
        },
        {
            "advisory": "virt/disk/api.py in OpenStack Compute (Nova) 2012.1.x before 2012.1.2 and Folsom before Folsom-3 allows remote authenticated users to overwrite arbitrary files via a symlink attack on a file in an image that uses a symlink that is only readable by root. NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-3361.",
            "cve": "CVE-2012-3447",
            "id": "pyup.io-35368",
            "more_info_path": "/vulnerabilities/CVE-2012-3447/35368",
            "specs": [
                ">=2012.1.0,<2012.1.2"
            ],
            "v": ">=2012.1.0,<2012.1.2"
        },
        {
            "advisory": "OpenStack Compute (Nova) Folsom, Grizzly, and Havana does not verify the virtual size of a QCOW2 image, which allows local users to cause a denial of service (host file system disk consumption) by creating an image with a large virtual size that does not contain a large amount of data.",
            "cve": "CVE-2013-2096",
            "id": "pyup.io-67985",
            "more_info_path": "/vulnerabilities/CVE-2013-2096/67985",
            "specs": [
                ">=2013,<2013.1.5"
            ],
            "v": ">=2013,<2013.1.5"
        },
        {
            "advisory": "Interaction error in OpenStack Nova and Neutron before Havana 2013.2.1 and icehouse-1 does not validate the instance ID of the tenant making a request, which allows remote tenants to obtain sensitive metadata by spoofing the device ID that is bound to a port, which is not properly handled by (1) api/metadata/handler.py in Nova and (2) the neutron-metadata-agent (agent/metadata/agent.py) in Neutron.",
            "cve": "CVE-2013-6419",
            "id": "pyup.io-67989",
            "more_info_path": "/vulnerabilities/CVE-2013-6419/67989",
            "specs": [
                ">=2013,<2013.2.1",
                ">=2014,<2014.1"
            ],
            "v": ">=2013,<2013.2.1,>=2014,<2014.1"
        },
        {
            "advisory": "The libvirt driver in OpenStack Compute (Nova) before 2013.2.2 and icehouse before icehouse-2 allows remote authenticated users to cause a denial of service (disk consumption) by creating and deleting instances with unique os_type settings, which triggers the creation of a new ephemeral disk backing file.",
            "cve": "CVE-2013-6437",
            "id": "pyup.io-68000",
            "more_info_path": "/vulnerabilities/CVE-2013-6437/68000",
            "specs": [
                ">=2013,<2013.2.2",
                ">=2014,<2014.1"
            ],
            "v": ">=2013,<2013.2.2,>=2014,<2014.1"
        },
        {
            "advisory": "The XenAPI backend in OpenStack Compute (Nova) Folsom, Grizzly, and Havana before 2013.2 does not properly apply security groups (1) when resizing an image or (2) during live migration, which allows remote attackers to bypass intended restrictions.",
            "cve": "CVE-2013-4497",
            "id": "pyup.io-67988",
            "more_info_path": "/vulnerabilities/CVE-2013-4497/67988",
            "specs": [
                ">=2013,<=2013.2"
            ],
            "v": ">=2013,<=2013.2"
        },
        {
            "advisory": "The Nova EC2 API security group implementation in OpenStack Compute (Nova) 2013.1 before 2013.2.4 and icehouse before icehouse-rc2 does not enforce RBAC policies for (1) add_rules, (2) remove_rules, (3) destroy, and other unspecified methods in compute/api.py when using non-default policies, which allows remote authenticated users to gain privileges via these API requests.",
            "cve": "CVE-2014-0167",
            "id": "pyup.io-35507",
            "more_info_path": "/vulnerabilities/CVE-2014-0167/35507",
            "specs": [
                ">=2013.1,<2013.2.4"
            ],
            "v": ">=2013.1,<2013.2.4"
        },
        {
            "advisory": "OpenStack Compute (Nova) Grizzly 2013.1.4, Havana 2013.2.1, and earlier uses world-writable and world-readable permissions for the temporary directory used to store live snapshots, which allows local users to read and modify live snapshots.",
            "cve": "CVE-2013-7048",
            "id": "pyup.io-68001",
            "more_info_path": "/vulnerabilities/CVE-2013-7048/68001",
            "specs": [
                ">=2013.1,<=2013.1.4",
                ">=2013.2,<=2013.2.1"
            ],
            "v": ">=2013.1,<=2013.1.4,>=2013.2,<=2013.2.1"
        },
        {
            "advisory": "The VMware driver in OpenStack Compute (Nova) before 2014.1.4 allows remote authenticated users to cause a denial of service (disk consumption) by deleting an instance in the resize state.",
            "cve": "CVE-2014-8333",
            "id": "pyup.io-70421",
            "more_info_path": "/vulnerabilities/CVE-2014-8333/70421",
            "specs": [
                ">=2014.1,<2014.1.4"
            ],
            "v": ">=2014.1,<2014.1.4"
        },
        {
            "advisory": "Race condition in the VMware driver in OpenStack Compute (Nova) before 2014.1.4 and 2014.2 before 2014.2rc1 allows remote authenticated users to access unintended consoles by spawning an instance that triggers the same VNC port to be allocated to two different instances.",
            "cve": "CVE-2014-8750",
            "id": "pyup.io-70420",
            "more_info_path": "/vulnerabilities/CVE-2014-8750/70420",
            "specs": [
                ">=2014.1,<2014.1.4"
            ],
            "v": ">=2014.1,<2014.1.4"
        },
        {
            "advisory": "OpenStack Compute (nova) 2015.1 through 2015.1.1, 2014.2.3, and earlier does not stop the migration process when the instance is deleted, which allows remote authenticated users to cause a denial of service (disk, network, and other resource consumption) by resizing and then deleting an instance.",
            "cve": "CVE-2015-3241",
            "id": "pyup.io-70419",
            "more_info_path": "/vulnerabilities/CVE-2015-3241/70419",
            "specs": [
                ">=2014.2,<=2014.2.3",
                ">=2015.1.0,<=2015.1.1"
            ],
            "v": ">=2014.2,<=2014.2.3,>=2015.1.0,<=2015.1.1"
        },
        {
            "advisory": "OpenStack Compute (Nova) before 2014.1.4 and 2014.2.x before 2014.2.1 allows remote authenticated users to cause a denial of service (CPU consumption) via an IP filter in a list active servers API request.",
            "cve": "CVE-2014-3708",
            "id": "pyup.io-35568",
            "more_info_path": "/vulnerabilities/CVE-2014-3708/35568",
            "specs": [
                ">=2014.2.0,<2014.2.1",
                ">=2010,<2014.1.4"
            ],
            "v": ">=2014.2.0,<2014.2.1,>=2010,<2014.1.4"
        }
    ],
    "nova-lxd": [
        {
            "advisory": "OpenStack Nova-LXD before 13.1.1 uses the wrong name for the veth pairs when applying Neutron security group rules for instances, which allows remote attackers to bypass intended security restrictions.",
            "cve": "CVE-2017-5936",
            "id": "pyup.io-35734",
            "more_info_path": "/vulnerabilities/CVE-2017-5936/35734",
            "specs": [
                "<13.1.1"
            ],
            "v": "<13.1.1"
        }
    ],
    "novajoin": [
        {
            "advisory": "Novajoin 1.1.1 includes a fix for CVE-2019-10138: A flaw was discovered in the python-novajoin plugin, all versions up to, excluding 1.1.1, for Red Hat OpenStack Platform. The novajoin API lacked sufficient access control, allowing any keystone authenticated user to generate FreeIPA tokens.",
            "cve": "CVE-2019-10138",
            "id": "pyup.io-37318",
            "more_info_path": "/vulnerabilities/CVE-2019-10138/37318",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "nowsys": [
        {
            "advisory": "Nowsys is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html",
            "cve": "PVE-2023-52919",
            "id": "pyup.io-52919",
            "more_info_path": "/vulnerabilities/PVE-2023-52919/52919",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "nox-poetry": [
        {
            "advisory": "Nox-poetry 0.8.2 updates its dependency 'pyyaml' to v5.4.1 to include a security fix.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-44981",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/44981",
            "specs": [
                "<0.8.2"
            ],
            "v": "<0.8.2"
        },
        {
            "advisory": "Nox-poetry 0.8.2 updates its dependency 'jinja2' to v2.11.3 to include a security fix.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-44980",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/44980",
            "specs": [
                "<0.8.2"
            ],
            "v": "<0.8.2"
        },
        {
            "advisory": "Nox-poetry 0.8.2 updates its dependency 'cryptography' to v3.4.6 to include a security fix.",
            "cve": "CVE-2020-36242",
            "id": "pyup.io-39702",
            "more_info_path": "/vulnerabilities/CVE-2020-36242/39702",
            "specs": [
                "<0.8.2"
            ],
            "v": "<0.8.2"
        },
        {
            "advisory": "Security Fix for Nox-poetry 1.2.0 | FIPS compliance issue with blake2b cryptographic function. The package was using blake2b hash function without explicitly declaring non-security usage, which could cause issues in FIPS-compliant environments",
            "cve": "PVE-2025-75625",
            "id": "pyup.io-75625",
            "more_info_path": "/vulnerabilities/PVE-2025-75625/75625",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "nsupdate": [
        {
            "advisory": "nsupdate before 0.3.0 is vulnerable to a undisclosed security issue.",
            "cve": "PVE-2021-25906",
            "id": "pyup.io-25906",
            "more_info_path": "/vulnerabilities/PVE-2021-25906/25906",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Nsupdate 0.7.0 enables Django's clickjacking protection middleware in settings.",
            "cve": "PVE-2022-45156",
            "id": "pyup.io-45156",
            "more_info_path": "/vulnerabilities/PVE-2022-45156/45156",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "nsupdate 0.8.0 fixes a security issue: abuse_blocked flag could be worked around by abuser.",
            "cve": "PVE-2021-25907",
            "id": "pyup.io-25907",
            "more_info_path": "/vulnerabilities/PVE-2021-25907/25907",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        },
        {
            "advisory": "nsupdate 0.9.1 fixes a security issue with \"related hosts\" / \"service updaters\".",
            "cve": "PVE-2021-25908",
            "id": "pyup.io-25908",
            "more_info_path": "/vulnerabilities/PVE-2021-25908/25908",
            "specs": [
                "<0.9.1"
            ],
            "v": "<0.9.1"
        },
        {
            "advisory": "A vulnerability classified as problematic has been found in nsupdate.info. This affects an unknown part of the file src/nsupdate/settings/base.py of the component CSRF Cookie Handler. The manipulation of the argument CSRF_COOKIE_HTTPONLY leads to cookie without 'httponly' flag. It is possible to initiate the attack remotely.",
            "cve": "CVE-2019-25091",
            "id": "pyup.io-71990",
            "more_info_path": "/vulnerabilities/CVE-2019-25091/71990",
            "specs": [
                "<=0.12.0"
            ],
            "v": "<=0.12.0"
        }
    ],
    "ntopng": [
        {
            "advisory": "Ntopng 3.0 includes a fix for a HTTP header injection vulnerability.\r\nhttps://github.com/ntop/ntopng/commit/9469e58f07e043da712e6d6c41244852a11bcaeb",
            "cve": "PVE-2022-52343",
            "id": "pyup.io-52343",
            "more_info_path": "/vulnerabilities/PVE-2022-52343/52343",
            "specs": [
                "<3.0"
            ],
            "v": "<3.0"
        },
        {
            "advisory": "Ntopng 3.0 hardens the code to prevent SQL injections.\r\nhttps://github.com/ntop/ntopng/commit/404bf86fd7f6228c2b5b07ad442c4faf94cb45e0",
            "cve": "PVE-2022-52336",
            "id": "pyup.io-52336",
            "more_info_path": "/vulnerabilities/PVE-2022-52336/52336",
            "specs": [
                "<3.0"
            ],
            "v": "<3.0"
        },
        {
            "advisory": "Ntopng 3.0 forces default admin password change.\r\nhttps://github.com/ntop/ntopng/commit/011b7f5cdf2fc679be892c7cc7709de71abad35c",
            "cve": "PVE-2022-52344",
            "id": "pyup.io-52344",
            "more_info_path": "/vulnerabilities/PVE-2022-52344/52344",
            "specs": [
                "<3.0"
            ],
            "v": "<3.0"
        },
        {
            "advisory": "Ntopng 3.2 changes the way host pool inc/dec are implemented to avoid race conditions.\r\nhttps://github.com/ntop/ntopng/commit/0623d2fc7dc2cd78f17a53dd532305762eec5a68",
            "cve": "PVE-2022-52363",
            "id": "pyup.io-52363",
            "more_info_path": "/vulnerabilities/PVE-2022-52363/52363",
            "specs": [
                "<3.2"
            ],
            "v": "<3.2"
        },
        {
            "advisory": "Ntopng 3.2 avoids offering unsafe SSLv3.\r\nhttps://github.com/ntop/ntopng/commit/f36a2b1dd5f49ea46d6389f16ca66b27bcba4764",
            "cve": "PVE-2022-52307",
            "id": "pyup.io-52307",
            "more_info_path": "/vulnerabilities/PVE-2022-52307/52307",
            "specs": [
                "<3.2"
            ],
            "v": "<3.2"
        },
        {
            "advisory": "Ntopng 3.8 fixes race conditions with custom categories reload.\r\nhttps://github.com/ntop/ntopng/commit/3f275417a32f00b54522a049b37f160f73dcb660",
            "cve": "PVE-2022-52364",
            "id": "pyup.io-52364",
            "more_info_path": "/vulnerabilities/PVE-2022-52364/52364",
            "specs": [
                "<3.8"
            ],
            "v": "<3.8"
        },
        {
            "advisory": "Ntopng 4.0 fixes possible stored XSS in runtime.lua.\r\nhttps://github.com/ntop/ntopng/commit/b41eeffba7c5533174d65a7f1a6366538851ba14",
            "cve": "PVE-2022-52338",
            "id": "pyup.io-52338",
            "more_info_path": "/vulnerabilities/PVE-2022-52338/52338",
            "specs": [
                "<4.0"
            ],
            "v": "<4.0"
        },
        {
            "advisory": "Ntopng 4.0 fixes possible XSS in login.lua referer param.\r\nhttps://github.com/ntop/ntopng/commit/5a67bf6e43a0fcdbba263e959e11a7f188177e09",
            "cve": "PVE-2022-52339",
            "id": "pyup.io-52339",
            "more_info_path": "/vulnerabilities/PVE-2022-52339/52339",
            "specs": [
                "<4.0"
            ],
            "v": "<4.0"
        },
        {
            "advisory": "Ntopng 4.2 fixes a heap-use-after-free vulnerability in ContinuousPing.\r\nhttps://github.com/ntop/ntopng/commit/67eb5dfdba3b2700e2e51bf68814f12d17a11e94",
            "cve": "PVE-2022-52345",
            "id": "pyup.io-52345",
            "more_info_path": "/vulnerabilities/PVE-2022-52345/52345",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ntopng 4.2 fixes CSRF vulnerabilities when POSTing JSON.\r\nhttps://github.com/ntop/ntopng/commit/db6bde4c54ade33b72167cce7856bde3cd1d2bfb",
            "cve": "PVE-2022-52337",
            "id": "pyup.io-52337",
            "more_info_path": "/vulnerabilities/PVE-2022-52337/52337",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ntopng 4.2 fixes XSS in dissected HTTP URLs, TLS certs, and DNS names.\r\nhttps://github.com/ntop/ntopng/commit/17bfc850b1b20463f97d70e6cc1f034685e979c6",
            "cve": "PVE-2022-52340",
            "id": "pyup.io-52340",
            "more_info_path": "/vulnerabilities/PVE-2022-52340/52340",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ntopng 4.2 fixes a heap-use-after-free vulnerability on HTTP dissected last_url.\r\nhttps://github.com/ntop/ntopng/commit/00c428eb1a0fda90388f06f94fd420522c441dc3",
            "cve": "PVE-2022-52306",
            "id": "pyup.io-52306",
            "more_info_path": "/vulnerabilities/PVE-2022-52306/52306",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Ntopng 5.0 fixes SSRF and stored-XSS injected with malicious SSDP responses.\r\nhttps://github.com/ntop/ntopng/commit/91db812607f5a6817d56df04f88beef0e78c18f4",
            "cve": "PVE-2022-52342",
            "id": "pyup.io-52342",
            "more_info_path": "/vulnerabilities/PVE-2022-52342/52342",
            "specs": [
                "<5.0"
            ],
            "v": "<5.0"
        },
        {
            "advisory": "Ntopng 5.0 fixes stored XSS in preferences.\r\nhttps://github.com/ntop/ntopng/commit/bb3b50443023f33d81cf30609e5c6c7f49c1b04f",
            "cve": "PVE-2022-52341",
            "id": "pyup.io-52341",
            "more_info_path": "/vulnerabilities/PVE-2022-52341/52341",
            "specs": [
                "<5.0"
            ],
            "v": "<5.0"
        }
    ],
    "nucliadb": [
        {
            "advisory": "Nucliadb 2.44.1 updates its cryptography dependency from 42.0.2 to 42.0.4 due to the CVE-2023-4807.\r\nhttps://github.com/nuclia/nucliadb/pull/1881/commits/bd2366f23f0388d1b02ced16b25e473ecf73744a",
            "cve": "CVE-2023-4807",
            "id": "pyup.io-65864",
            "more_info_path": "/vulnerabilities/CVE-2023-4807/65864",
            "specs": [
                "<2.44.1"
            ],
            "v": "<2.44.1"
        },
        {
            "advisory": "Nucliadb version 3.1.0 upgrades the idna library from version 3.6 to 3.7 to address the security issue identified in CVE-2024-3651.",
            "cve": "CVE-2024-3651",
            "id": "pyup.io-70928",
            "more_info_path": "/vulnerabilities/CVE-2024-3651/70928",
            "specs": [
                "<3.1.0"
            ],
            "v": "<3.1.0"
        },
        {
            "advisory": "Nucliadb version 3.1.0 upgrades aiohttp from version 3.9.3 to 3.9.4 in response to CVE-2024-27306.",
            "cve": "CVE-2024-27306",
            "id": "pyup.io-70910",
            "more_info_path": "/vulnerabilities/CVE-2024-27306/70910",
            "specs": [
                "<3.1.0"
            ],
            "v": "<3.1.0"
        }
    ],
    "nuclio-jupyter": [
        {
            "advisory": "Nuclio-jupyter 0.9.9 updates its dependency 'ipython' requirement to include a security fix.",
            "cve": "CVE-2023-24816",
            "id": "pyup.io-53438",
            "more_info_path": "/vulnerabilities/CVE-2023-24816/53438",
            "specs": [
                "<0.9.9"
            ],
            "v": "<0.9.9"
        }
    ],
    "nuitka": [
        {
            "advisory": "Nuitka 0.6.12 uses https URLs for downloading dependency walker, for it to be more secure.",
            "cve": "PVE-2021-39648",
            "id": "pyup.io-39648",
            "more_info_path": "/vulnerabilities/PVE-2021-39648/39648",
            "specs": [
                "<0.6.12"
            ],
            "v": "<0.6.12"
        },
        {
            "advisory": "Nuitka 0.9 includes a fix for CVE-2022-2054: Command Injection in GitHub repository nuitka/nuitka prior to 0.9.",
            "cve": "CVE-2022-2054",
            "id": "pyup.io-49630",
            "more_info_path": "/vulnerabilities/CVE-2022-2054/49630",
            "specs": [
                "<0.9"
            ],
            "v": "<0.9"
        }
    ],
    "num2words": [
        {
            "advisory": "The num2words project was compromised via a phishing attack and two new versions were uploaded to PyPI containing malicious code. The affected versions have been removed from PyPI, and users are advised to remove the affected versions from their environments.",
            "cve": "PVE-2025-78656",
            "id": "pyup.io-78656",
            "more_info_path": "/vulnerabilities/PVE-2025-78656/78656",
            "specs": [
                ">=0.5.15,<=0.5.16"
            ],
            "v": ">=0.5.15,<=0.5.16"
        }
    ],
    "numato-gpio": [
        {
            "advisory": "Numato-gpio 0.11.1 updates its gitpython dependency to version 3.1.37 from 3.1.32 in response to the security vulnerability identified as CVE-2023-41040.\r\nhttps://github.com/clssn/numato-gpio/commit/b6b05d0868029db48ee45a9da6365d156e932e13",
            "cve": "CVE-2023-41040",
            "id": "pyup.io-65768",
            "more_info_path": "/vulnerabilities/CVE-2023-41040/65768",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        }
    ],
    "numba": [
        {
            "advisory": "Numba 0.49.0 fixes a frame injection vulnerability in the dispatcher tracing path, that lead to DoS.",
            "cve": "PVE-2021-38983",
            "id": "pyup.io-38983",
            "more_info_path": "/vulnerabilities/PVE-2021-38983/38983",
            "specs": [
                "<0.49.0"
            ],
            "v": "<0.49.0"
        }
    ],
    "numpy": [
        {
            "advisory": "Numpy 1.13.2 includes a fix for CVE-2017-12852: The numpy.pad function in Numpy 1.13.1 and older versions is missing input validation. An empty list or ndarray will stick into an infinite loop, which can allow attackers to cause a DoS attack.\r\nhttps://github.com/numpy/numpy/issues/9560#issuecomment-322395292",
            "cve": "CVE-2017-12852",
            "id": "pyup.io-44720",
            "more_info_path": "/vulnerabilities/CVE-2017-12852/44720",
            "specs": [
                "<1.13.2"
            ],
            "v": "<1.13.2"
        },
        {
            "advisory": "*Disputed* Numpy 1.16.3 includes a fix for CVE-2019-6446: It uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object, as demonstrated by a numpy.load call.\r\nNOTE: Third parties dispute this issue because it is  a behavior that might have legitimate applications in (for example) loading serialized Python object arrays from trusted and authenticated  sources.\r\nhttps://github.com/numpy/numpy/commit/89b688732b37616c9d26623f81aaee1703c30ffb",
            "cve": "CVE-2019-6446",
            "id": "pyup.io-36810",
            "more_info_path": "/vulnerabilities/CVE-2019-6446/36810",
            "specs": [
                "<1.16.3"
            ],
            "v": "<1.16.3"
        },
        {
            "advisory": "Numpy 1.21.0rc1 includes a fix for CVE-2021-33430: A Buffer Overflow vulnerability in the PyArray_NewFromDescr_int function of ctors.c when specifying arrays of large dimensions (over 32) from Python code, which could let a malicious user cause a Denial of Service. \r\nNOTE: The vendor does not agree this is a vulnerability. In (very limited) circumstances a user may be able provoke the buffer overflow, the user is most likely already privileged to at least provoke denial of service by exhausting memory. Triggering this further requires the use of uncommon API (complicated structured dtypes), which is very unlikely to be available to an unprivileged user.\r\nhttps://github.com/numpy/numpy/issues/18939",
            "cve": "CVE-2021-33430",
            "id": "pyup.io-43453",
            "more_info_path": "/vulnerabilities/CVE-2021-33430/43453",
            "specs": [
                "<1.21.0rc1"
            ],
            "v": "<1.21.0rc1"
        },
        {
            "advisory": "Numpy 1.22.0 includes a fix for CVE-2021-41496: Buffer overflow in the array_from_pyobj function of fortranobject.c, which allows attackers to conduct a Denial of Service attacks by carefully constructing an array with negative values. \r\nNOTE: The vendor does not agree this is a vulnerability; the negative dimensions can only be created by an already privileged user (or internally).\r\nhttps://github.com/numpy/numpy/issues/19000",
            "cve": "CVE-2021-41496",
            "id": "pyup.io-44716",
            "more_info_path": "/vulnerabilities/CVE-2021-41496/44716",
            "specs": [
                "<1.22.0"
            ],
            "v": "<1.22.0"
        },
        {
            "advisory": "Numpy 1.22.0 includes a fix for CVE-2021-34141: An incomplete string comparison in the numpy.core component in NumPy before 1.22.0 allows attackers to trigger slightly incorrect copying by constructing specific string objects. \r\nNOTE: the vendor states that this reported code behavior is \"completely harmless.\"\r\nhttps://github.com/numpy/numpy/issues/18993",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-44717",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/44717",
            "specs": [
                "<1.22.0"
            ],
            "v": "<1.22.0"
        },
        {
            "advisory": "Numpy 1.22.2  includes a fix for CVE-2021-41495: Null Pointer Dereference vulnerability exists in numpy.sort in NumPy in the PyArray_DescrNew function due to missing return-value validation, which allows attackers to conduct DoS attacks by repetitively creating sort arrays. \r\nNOTE: While correct that validation is missing, an error can only occur due to an exhaustion of memory. If the user can exhaust memory, they are already privileged. Further, it should be practically impossible to construct an attack which can target the memory exhaustion to occur at exactly this place.\r\nNOTE2: The specs we include in this advisory differ from the publicly available on other sources. For example, the advisory posted by the NVD indicate that versions up to and including 1.19.0 are affected. However, research by Safety CLI Cybersecurity confirms that the vulnerability remained unaddressed until version 1.22.2.",
            "cve": "CVE-2021-41495",
            "id": "pyup.io-44715",
            "more_info_path": "/vulnerabilities/CVE-2021-41495/44715",
            "specs": [
                "<1.22.2"
            ],
            "v": "<1.22.2"
        },
        {
            "advisory": "Numpy 1.8.1 includes a fix for CVE-2014-1859: (1) core/tests/test_memmap.py, (2) core/tests/test_multiarray.py, (3) f2py/f2py2e.py, and (4) lib/tests/test_io.py in NumPy before 1.8.1 allow local users to write to arbitrary files via a symlink attack on a temporary file.\r\nhttps://github.com/numpy/numpy/pull/4262",
            "cve": "CVE-2014-1859",
            "id": "pyup.io-34726",
            "more_info_path": "/vulnerabilities/CVE-2014-1859/34726",
            "specs": [
                "<1.8.1"
            ],
            "v": "<1.8.1"
        },
        {
            "advisory": "Numpy 1.8.1 includes a fix for CVE-2014-1858: __init__.py in f2py in NumPy before 1.8.1 allows local users to write to arbitrary files via a symlink attack on a temporary file.\r\nhttps://github.com/numpy/numpy/commit/0bb46c1448b0d3f5453d5182a17ea7ac5854ee15",
            "cve": "CVE-2014-1858",
            "id": "pyup.io-44719",
            "more_info_path": "/vulnerabilities/CVE-2014-1858/44719",
            "specs": [
                "<1.8.1"
            ],
            "v": "<1.8.1"
        }
    ],
    "numpyro-oop": [
        {
            "advisory": "Numpyro-oop has resolved a security vulnerability in jupyterlab by updating the development dependency to version 4.2.5, addressing CVE-2024-43805.",
            "cve": "CVE-2024-43805",
            "id": "pyup.io-73390",
            "more_info_path": "/vulnerabilities/CVE-2024-43805/73390",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        }
    ],
    "nuplone": [
        {
            "advisory": "Nuplone 2.1.0 adds CSRF auth token to paste url.\r\nhttps://github.com/euphorie/NuPlone/commit/f52e70928c03d1c92c6a6d10a26e3c294d029ae7",
            "cve": "PVE-2022-49315",
            "id": "pyup.io-49315",
            "more_info_path": "/vulnerabilities/PVE-2022-49315/49315",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        }
    ],
    "nuts": [
        {
            "advisory": "Nuts 3.1.0 updates its dependency 'lxml' to version '4.6.5' to include a fix for a Cross-Site Scripting vulnerability.\r\nhttps://github.com/network-unit-testing-system/nuts/pull/56",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-60351",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/60351",
            "specs": [
                "<3.1.0"
            ],
            "v": "<3.1.0"
        }
    ],
    "nvflare": [
        {
            "advisory": "Nvflare 2.1.1 signs and loads privilege yaml file by secure content service.\r\nhttps://github.com/NVIDIA/NVFlare/pull/403/commits/1fb8369826ca342122a187af5ac572acd7bb41b0",
            "cve": "PVE-2022-49489",
            "id": "pyup.io-49489",
            "more_info_path": "/vulnerabilities/PVE-2022-49489/49489",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Nvflare 2.1.1 fixes a bug in 'ls' command that allowed path traversal attacks.\r\nhttps://github.com/NVIDIA/NVFlare/pull/682",
            "cve": "PVE-2022-49498",
            "id": "pyup.io-49498",
            "more_info_path": "/vulnerabilities/PVE-2022-49498/49498",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Nvflare 2.1.1 adds SecurityContentService for runner_process.\r\nhttps://github.com/NVIDIA/NVFlare/pull/473/files",
            "cve": "PVE-2022-49496",
            "id": "pyup.io-49496",
            "more_info_path": "/vulnerabilities/PVE-2022-49496/49496",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Nvflare 2.1.2 includes a fix for a DoS vulnerability in the admin conn.\r\nhttps://github.com/NVIDIA/NVFlare/pull/688",
            "cve": "PVE-2022-49491",
            "id": "pyup.io-49491",
            "more_info_path": "/vulnerabilities/PVE-2022-49491/49491",
            "specs": [
                "<2.1.2"
            ],
            "v": "<2.1.2"
        },
        {
            "advisory": "Nvflare 2.3.0 uses secure logging for exceptions to avoid disclosing sensitive information.\r\nhttps://github.com/NVIDIA/NVFlare/pull/1645",
            "cve": "PVE-2023-54928",
            "id": "pyup.io-54928",
            "more_info_path": "/vulnerabilities/PVE-2023-54928/54928",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Nvflare 2.4.0rc1 updates its dependency 'flask' to version '2.2.5' to include a security fix.\r\nhttps://github.com/NVIDIA/NVFlare/pull/1817/files\r\nhttps://github.com/advisories/GHSA-m2qf-hxjv-5gpq",
            "cve": "CVE-2023-30861",
            "id": "pyup.io-59210",
            "more_info_path": "/vulnerabilities/CVE-2023-30861/59210",
            "specs": [
                "<2.4.0rc1"
            ],
            "v": "<2.4.0rc1"
        },
        {
            "advisory": "Nvflare addresses a potential race condition in the PipeHandler component, where the self.pipe object could be set to None during execution, leading to uncontrolled crashes. This vulnerability could be exploited in affected versions to cause a denial of service or disrupt the application's stability. The update introduces safer handling of the self.pipe object, preventing NoneType errors and enhancing the system's robustness against such race conditions.",
            "cve": "PVE-2024-72751",
            "id": "pyup.io-72751",
            "more_info_path": "/vulnerabilities/PVE-2024-72751/72751",
            "specs": [
                "<2.4.2"
            ],
            "v": "<2.4.2"
        },
        {
            "advisory": "Nvflare has upgraded the installation dependency, Werkzeug, to version 3.0.3 to address CVE-2024-34069.",
            "cve": "CVE-2024-34069",
            "id": "pyup.io-72506",
            "more_info_path": "/vulnerabilities/CVE-2024-34069/72506",
            "specs": [
                "<2.5.0rc2"
            ],
            "v": "<2.5.0rc2"
        },
        {
            "advisory": "Certain versions of Nvflare are vulnerable to a race condition. The pipe handler has a thread for reading data from the pipe and checking the pipe status, but the pipe handler can be stopped at any time, setting the pipe object to None. This PR resolves the issue by ensuring the reading thread checks that the pipe object is not None before accessing its methods, making the thread operation safe.",
            "cve": "PVE-2024-72482",
            "id": "pyup.io-72482",
            "more_info_path": "/vulnerabilities/PVE-2024-72482/72482",
            "specs": [
                "<2.5.0rc2"
            ],
            "v": "<2.5.0rc2"
        },
        {
            "advisory": "### Impact\nNVIDIA FLARE contains a vulnerability in Admin Interface, where an un-authorized attacker can cause Allocation of Resources Without Limits or Throttling, which may lead to cause system unavailable\n\nAll versions before 2.0.16 are affected.\n\n### Patches\nThe patch will be included in nvflare==2.0.16.\n\n### Workarounds\nThe changes in commits https://github.com/NVIDIA/NVFlare/commit/93588b3a0dff9bd4568983071b74d8b420de3a6e and https://github.com/NVIDIA/NVFlare/commit/93588b3a0dff9bd4568983071b74d8b420de3a6e  can be applied to any version of the NVIDIA FLARE without any adverse effect.\n\n### Additional information\nIssue Found on: 2022.3.3\nIssue Found by: Oliver Sellwood (@Nintorac)",
            "cve": "CVE-2022-21822",
            "id": "pyup.io-54415",
            "more_info_path": "/vulnerabilities/CVE-2022-21822/54415",
            "specs": [
                ">=0,<2.0.16"
            ],
            "v": ">=0,<2.0.16"
        },
        {
            "advisory": "NVFLARE, versions prior to 2.1.2, contains a vulnerability in its utils module, where YAML files are loaded via yaml.load() instead of yaml.safe_load(). The deserialization of Untrusted Data, may allow an unprivileged network attacker to cause Remote Code Execution, Denial Of Service, and Impact to both Confidentiality and Integrity.",
            "cve": "CVE-2022-31605",
            "id": "pyup.io-54410",
            "more_info_path": "/vulnerabilities/CVE-2022-31605/54410",
            "specs": [
                ">=0,<2.1.2"
            ],
            "v": ">=0,<2.1.2"
        },
        {
            "advisory": "NVFLARE, versions prior to 2.1.2, contains a vulnerability in its PKI implementation module, where The CA credentials are transported via pickle and no safe deserialization. The deserialization of Untrusted Data may allow an unprivileged network attacker to cause Remote Code Execution, Denial Of Service, and Impact to both Confidentiality and Integrity.",
            "cve": "CVE-2022-31604",
            "id": "pyup.io-54409",
            "more_info_path": "/vulnerabilities/CVE-2022-31604/54409",
            "specs": [
                ">=0,<2.1.2"
            ],
            "v": ">=0,<2.1.2"
        },
        {
            "advisory": "Nvflare 2.1.4 includes a fix for CVE-2022-34668: Deserialization of Untrusted Data due to Pickle usage may allow an unprivileged network attacker to cause Remote Code Execution, Denial Of Service, and Impact to both Confidentiality and Integrity.\r\nhttps://github.com/NVIDIA/NVFlare/security/advisories/GHSA-6qv6-q77g-7qm6",
            "cve": "CVE-2022-34668",
            "id": "pyup.io-54069",
            "more_info_path": "/vulnerabilities/CVE-2022-34668/54069",
            "specs": [
                ">=0,<2.1.4"
            ],
            "v": ">=0,<2.1.4"
        }
    ],
    "nvidia-modulus.sym": [
        {
            "advisory": "Nvidia-modulus.sym upgrades opencv-python to address GHSA-qr4w-53vh-m672 - CVE-2023-4863.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-73444",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/73444",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Nvidia-modulus.sym upgrades notebook to resolve CVEs GHSA-9q39-rmj3-p4r2 - CVE-2024-43805.",
            "cve": "CVE-2024-43805",
            "id": "pyup.io-73436",
            "more_info_path": "/vulnerabilities/CVE-2024-43805/73436",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Nvidia-modulus.sym upgrades setuptools to fix GHSA-cx63-2mw6-8hw5 and CVE-2024-6345.",
            "cve": "CVE-2024-6345",
            "id": "pyup.io-73445",
            "more_info_path": "/vulnerabilities/CVE-2024-6345/73445",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        }
    ],
    "nvidia-physicsnemo.sym": [
        {
            "advisory": "Nvidia-physicsnemo.sym updates its notebook dependency due to the CVE-2024-43805.",
            "cve": "CVE-2024-43805",
            "id": "pyup.io-76003",
            "more_info_path": "/vulnerabilities/CVE-2024-43805/76003",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Nvidia-physicsnemo.sym updates its setuptools dependency due to the CVE-2024-6345\r\n.",
            "cve": "CVE-2024-6345",
            "id": "pyup.io-76026",
            "more_info_path": "/vulnerabilities/CVE-2024-6345/76026",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        }
    ],
    "nvidia-riva-client": [
        {
            "advisory": "Nvidia-riva-client updates setuptools to version 70 to patch security vulnerability CVE-2024-6345.",
            "cve": "CVE-2024-6345",
            "id": "pyup.io-74549",
            "more_info_path": "/vulnerabilities/CVE-2024-6345/74549",
            "specs": [
                "<2.17.0"
            ],
            "v": "<2.17.0"
        },
        {
            "advisory": "Nvidia-riva-client updates setuptools to version 70 to patch security vulnerability CVE-2022-40897.",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-74572",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/74572",
            "specs": [
                "<2.17.0"
            ],
            "v": "<2.17.0"
        }
    ],
    "nwb-conversion-tools": [
        {
            "advisory": "Nwb-conversion-tools 0.11.38 updates its dependency 'numpy' to v1.22.0 to include security fixes.",
            "cve": "CVE-2021-41496",
            "id": "pyup.io-50143",
            "more_info_path": "/vulnerabilities/CVE-2021-41496/50143",
            "specs": [
                "<0.11.38"
            ],
            "v": "<0.11.38"
        },
        {
            "advisory": "Nwb-conversion-tools 0.11.38 updates its dependency 'numpy' to v1.22.0 to include security fixes.",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-50173",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/50173",
            "specs": [
                "<0.11.38"
            ],
            "v": "<0.11.38"
        }
    ],
    "oarepo-vocabularies": [
        {
            "advisory": "Affected versions of the oarepo-vocabularies package before 2.1.14 are vulnerable to Open Redirect due to constructing redirect targets from the user-controlled request path without validation. In oarepo_vocabularies.ui.resources.vocabulary_type.resource, the create_url_rules method mapped the no-trailing-slash route to list_without_slash, and list_without_slash built a 302 Location header from request.full_path via redirect(...), allowing scheme-relative or absolute paths to be reflected into the redirect target.",
            "cve": "PVE-2025-80631",
            "id": "pyup.io-80631",
            "more_info_path": "/vulnerabilities/PVE-2025-80631/80631",
            "specs": [
                "<2.1.14"
            ],
            "v": "<2.1.14"
        }
    ],
    "oauth-pyzure": [
        {
            "advisory": "Oauth-pyzure 0.1.4 is based on OSS vulnerability reports.",
            "cve": "PVE-2021-39077",
            "id": "pyup.io-39077",
            "more_info_path": "/vulnerabilities/PVE-2021-39077/39077",
            "specs": [
                "<0.1.4"
            ],
            "v": "<0.1.4"
        }
    ],
    "oauth2": [
        {
            "advisory": "Oauth2 1.9 includes a fix for CVE-2013-4347: It was found that python-oauth2 did not properly generate random values for use in nonces. An attacker able to capture network traffic of a website using OAuth2 authentication could use this flaw to conduct replay attacks against that website.\r\nhttps://github.com/joestump/python-oauth2/commit/82dd2cdd4954cd7b8983d5d64c0dfd9072bf4650",
            "cve": "CVE-2013-4347",
            "id": "pyup.io-35463",
            "more_info_path": "/vulnerabilities/CVE-2013-4347/35463",
            "specs": [
                "<1.9"
            ],
            "v": "<1.9"
        },
        {
            "advisory": "Oauth2 is vulnerable to CVE-2013-4346: It was found that python-oauth2 did not properly verify the nonce of a signed URL. An attacker able to capture network traffic of a website using OAuth2 authentication could use this flaw to conduct replay attacks against that website.\r\nhttps://github.com/joestump/python-oauth2/issues/129",
            "cve": "CVE-2013-4346",
            "id": "pyup.io-35462",
            "more_info_path": "/vulnerabilities/CVE-2013-4346/35462",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "oauthenticator": [
        {
            "advisory": "OAuthenticator provides plugins for JupyterHub to use common OAuth providers and base classes for writing custom Authenticators with any OAuth 2.0 provider. The GoogleOAuthenticator.hosted_domain setting is intended to restrict access to JupyterHub to Google accounts within one or more verified Google organizations controlling specified domains. However, prior to the latest patch, the restriction was applied merely to Google accounts with email addresses ending in the specified domain. This meant that anyone who had ever been able to read an email associated with the domain could create such an account. This issue was highlighted by Dylan Ayrey in a blog post on December 15, 2023. A patch has been released to address this issue.",
            "cve": "CVE-2024-29033",
            "id": "pyup.io-71903",
            "more_info_path": "/vulnerabilities/CVE-2024-29033/71903",
            "specs": [
                "<16.3.0"
            ],
            "v": "<16.3.0"
        },
        {
            "advisory": "OAuthenticator is a software that integrates OAuth2 identity providers with JupyterHub. A configuration issue arises when using GlobusOAuthenticator with JupyterHub. Previously, it was possible to restrict access to users from a specific institution only. However, due to a change in JupyterHub, the allow_all setting now takes precedence over identity_provider. This means that all users are allowed to log in, regardless of the identity_provider setting, effectively ignoring this restriction.",
            "cve": "CVE-2024-37300",
            "id": "pyup.io-71902",
            "more_info_path": "/vulnerabilities/CVE-2024-37300/71902",
            "specs": [
                "<16.3.1"
            ],
            "v": "<16.3.1"
        },
        {
            "advisory": "OAuthenticator is an OAuth token library for the JupyerHub login handler. CILogonOAuthenticator is provided by the OAuthenticator package, and lets users log in to a JupyterHub via CILogon. This is primarily used to restrict a JupyterHub only to users of a given institute. The allowed_idps configuration trait of CILogonOAuthenticator is documented to be a list of domains that indicate the institutions whose users are authorized to access this JupyterHub. This authorization is validated by ensuring that the *email* field provided to us by CILogon has a *domain* that matches one of the domains listed in `allowed_idps`.If `allowed_idps` contains `berkeley.edu`, you might expect only users with valid current credentials provided by University of California, Berkeley to be able to access the JupyterHub. However, CILogonOAuthenticator does *not* verify which provider is used by the user to login, only the email address provided. So a user can login with a GitHub account that has email set to `@berkeley.edu`, and that will be treated exactly the same as someone logging in using the UC Berkeley official Identity Provider. The patch fixing this issue makes a *breaking change* in how `allowed_idps` is interpreted. It's no longer a list of domains, but configuration representing the `EntityID` of the IdPs that are allowed, picked from the [list maintained by CILogon](https://cilogon.org/idplist/). Users are advised to upgrade.",
            "cve": "CVE-2022-31027",
            "id": "pyup.io-54459",
            "more_info_path": "/vulnerabilities/CVE-2022-31027/54459",
            "specs": [
                ">=0,<15.0.0"
            ],
            "v": ">=0,<15.0.0"
        },
        {
            "advisory": "OAuthenticator is an OAuth login mechanism for JupyterHub. In oauthenticator from version 0.12.0 and before 0.12.2, the deprecated (in jupyterhub 1.2) configuration `Authenticator.whitelist`, which should be transparently mapped to `Authenticator.allowed_users` with a warning, is instead ignored by OAuthenticator classes, resulting in the same behavior as if this configuration has not been set. If this is the only mechanism of authorization restriction (i.e. no group or team restrictions in configuration) then all authenticated users will be allowed. Provider-based restrictions, including deprecated values such as `GitHubOAuthenticator.org_whitelist` are **not** affected. All users of OAuthenticator 0.12.0 and 0.12.1 with JupyterHub 1.2 (JupyterHub Helm chart 0.10.0-0.10.5) who use the `admin.whitelist.users` configuration in the jupyterhub helm chart or the `c.Authenticator.whitelist` configuration directly. Users of other deprecated configuration, e.g. `c.GitHubOAuthenticator.team_whitelist` are **not** affected. If you see a log line like this and expect a specific list of allowed usernames: \"[I 2020-11-27 16:51:54.528 JupyterHub app:1717] Not using allowed_users. Any authenticated user will be allowed.\" you are likely affected. Updating oauthenticator to 0.12.2 is recommended. A workaround is to replace the deprecated `c.Authenticator.whitelist = ...` with `c.Authenticator.allowed_users = ...`. If any users have been authorized during this time who should not have been, they must be deleted via the API or admin interface, per the referenced documentation.",
            "cve": "CVE-2020-26250",
            "id": "pyup.io-54250",
            "more_info_path": "/vulnerabilities/CVE-2020-26250/54250",
            "specs": [
                ">=0.12.0,<0.12.2"
            ],
            "v": ">=0.12.0,<0.12.2"
        },
        {
            "advisory": "An issue was discovered in Project Jupyter JupyterHub OAuthenticator 0.6.x before 0.6.2 and 0.7.x before 0.7.3. When using JupyterHub with GitLab group whitelisting for access control, group membership was not checked correctly, allowing members not in the whitelisted groups to create accounts on the Hub. (Users were not allowed to access other users' accounts, but could create their own accounts on the Hub linked to their GitLab account. GitLab authentication not using gitlab_group_whitelist is unaffected. No other Authenticators are affected.)",
            "cve": "CVE-2018-7206",
            "id": "pyup.io-54301",
            "more_info_path": "/vulnerabilities/CVE-2018-7206/54301",
            "specs": [
                ">=0.6,<0.6.2",
                ">=0.7,<0.7.3"
            ],
            "v": ">=0.6,<0.6.2,>=0.7,<0.7.3"
        }
    ],
    "oauthlib": [
        {
            "advisory": "oauthlib before 0.7.0 is not stripping client provided passwords from OAuth2 logs.\r\nhttps://github.com/oauthlib/oauthlib/commit/fef1f7987cc6298e744b7d4290e3fc9a9701831b",
            "cve": "PVE-2021-25909",
            "id": "pyup.io-25909",
            "more_info_path": "/vulnerabilities/PVE-2021-25909/25909",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "OAuthLib 3.2.1 includes a fix for CVE-2022-36087: In OAuthLib versions 3.1.1 until 3.2.1, an attacker providing malicious redirect uri can cause denial of service. An attacker can also leverage usage of 'uri_validate' functions depending where it is used. OAuthLib applications using OAuth2.0 provider support or use directly 'uri_validate' are affected by this issue. There are no known workarounds.\r\nhttps://github.com/oauthlib/oauthlib/security/advisories/GHSA-3pgj-pg6c-r5p7",
            "cve": "CVE-2022-36087",
            "id": "pyup.io-50959",
            "more_info_path": "/vulnerabilities/CVE-2022-36087/50959",
            "specs": [
                ">=3.1.1,<3.2.1"
            ],
            "v": ">=3.1.1,<3.2.1"
        }
    ],
    "obasparql": [
        {
            "advisory": "Obasparql 2.0.1 updates 'WerkZeug' to versions '>=0.15.3' to include security fixes.",
            "cve": "CVE-2019-14806",
            "id": "pyup.io-38322",
            "more_info_path": "/vulnerabilities/CVE-2019-14806/38322",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        }
    ],
    "obiba-opal": [
        {
            "advisory": "Obiba-opal 5.2.1 updates its dependency 'certifi' to version '2023.7.22' include a fix.\r\nhttps://github.com/obiba/opal-python-client/pull/35",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-59968",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/59968",
            "specs": [
                "<5.2.1"
            ],
            "v": "<5.2.1"
        }
    ],
    "obsei": [
        {
            "advisory": "Obsei 0.0.11 updates its dependency 'lxml' to v4.7.1 to include a security fix.",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-44902",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/44902",
            "specs": [
                "<0.0.11"
            ],
            "v": "<0.0.11"
        }
    ],
    "obsplus": [
        {
            "advisory": "Obsplus 0.0.6 switched from MD5 hashing to SHA256 as the latter is more secure and the computational differences were negligible.",
            "cve": "PVE-2021-38088",
            "id": "pyup.io-38088",
            "more_info_path": "/vulnerabilities/PVE-2021-38088/38088",
            "specs": [
                "<0.0.6"
            ],
            "v": "<0.0.6"
        }
    ],
    "ocean-contracts": [
        {
            "advisory": "Ocean-contracts 1.0.0a1 avoids a potential attack when using infinite approvals.\r\nhttps://github.com/oceanprotocol/contracts/issues/375",
            "cve": "PVE-2022-48122",
            "id": "pyup.io-48122",
            "more_info_path": "/vulnerabilities/PVE-2022-48122/48122",
            "specs": [
                "<1.0.0a1"
            ],
            "v": "<1.0.0a1"
        }
    ],
    "oci": [
        {
            "advisory": "Oci version 2.0.2 includes a fix for CVE-2018-10903: A flaw was found in python-cryptography versions between >=1.9.0 and <2.3. The finalize_with_tag API did not enforce a minimum tag length. If a user did not validate the input length prior to passing it to finalize_with_tag an attacker could craft an invalid payload with a shortened tag (e.g. 1 byte) such that they would have a 1 in 256 chance of passing the MAC check. GCM tag forgeries can cause key leakage.",
            "cve": "CVE-2018-10903",
            "id": "pyup.io-37415",
            "more_info_path": "/vulnerabilities/CVE-2018-10903/37415",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Oci 2.1.3 requires 'pyOpenSSL>=17.5.0' so to include a security fix.",
            "cve": "CVE-2018-1000808",
            "id": "pyup.io-36786",
            "more_info_path": "/vulnerabilities/CVE-2018-1000808/36786",
            "specs": [
                "<2.1.3"
            ],
            "v": "<2.1.3"
        },
        {
            "advisory": "Oci 2.24.1 updates its dependency 'cryptography' to v3.2.1 to include a security fix.",
            "cve": "CVE-2020-25659",
            "id": "pyup.io-39212",
            "more_info_path": "/vulnerabilities/CVE-2020-25659/39212",
            "specs": [
                "<2.24.1"
            ],
            "v": "<2.24.1"
        },
        {
            "advisory": "Oci 2.37.0 updates the 'cryptography' dependency version to 3.3.2 to address a security vulnerability.",
            "cve": "CVE-2020-36242",
            "id": "pyup.io-40377",
            "more_info_path": "/vulnerabilities/CVE-2020-36242/40377",
            "specs": [
                "<2.37.0"
            ],
            "v": "<2.37.0"
        },
        {
            "advisory": "Oci 2.90.1 updates its dependency 'Wheel' to v0.38.1 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-52863",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/52863",
            "specs": [
                "<2.90.1"
            ],
            "v": "<2.90.1"
        },
        {
            "advisory": "Oci 2.95.0 updates its dependency 'cryptography' to include a security fix.",
            "cve": "CVE-2023-23931",
            "id": "pyup.io-53764",
            "more_info_path": "/vulnerabilities/CVE-2023-23931/53764",
            "specs": [
                "<2.95.0"
            ],
            "v": "<2.95.0"
        }
    ],
    "oci-cli": [
        {
            "advisory": "Oci-cli 2.24.0 updates its dependency 'cryptography' to v3.3.2 to include a security fix.",
            "cve": "CVE-2020-36242",
            "id": "pyup.io-40255",
            "more_info_path": "/vulnerabilities/CVE-2020-36242/40255",
            "specs": [
                "<2.24.0"
            ],
            "v": "<2.24.0"
        },
        {
            "advisory": "Oci-cli 2.24.4 updates its dependency 'py' to v1.10.0 to include a security fix.",
            "cve": "CVE-2020-29651",
            "id": "pyup.io-40831",
            "more_info_path": "/vulnerabilities/CVE-2020-29651/40831",
            "specs": [
                "<2.24.4"
            ],
            "v": "<2.24.4"
        },
        {
            "advisory": "Oci-cli 2.4.11 fixes an improper file's permissions vulnerability.",
            "cve": "PVE-2021-36148",
            "id": "pyup.io-36148",
            "more_info_path": "/vulnerabilities/PVE-2021-36148/36148",
            "specs": [
                "<2.4.11"
            ],
            "v": "<2.4.11"
        },
        {
            "advisory": "Oci-cli 2.4.40 includes a fix for CVE-2018-1000808: Python Cryptographic Authority pyopenssl version Before 17.5.0 contains a CWE - 401 : Failure to Release Memory Before Removing Last Reference vulnerability in PKCS #12 Store that can result in Denial of service if memory runs low or is exhausted. This attack appear to be exploitable via Depends upon calling application, however it could be as simple as initiating a TLS connection. Anything that would cause the calling application to reload certificates from a PKCS #12 store.. This vulnerability appears to have been fixed in 17.5.0.",
            "cve": "CVE-2018-1000808",
            "id": "pyup.io-36804",
            "more_info_path": "/vulnerabilities/CVE-2018-1000808/36804",
            "specs": [
                "<2.4.40"
            ],
            "v": "<2.4.40"
        },
        {
            "advisory": "Oci-cli 2.5.9 updates its dependency 'Jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-37139",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/37139",
            "specs": [
                "<2.5.9"
            ],
            "v": "<2.5.9"
        },
        {
            "advisory": "Oci-cli 2.6.3 fixes CVE-2017-18342. In PyYAML before 4.1, the yaml.load() API could execute arbitrary code. In other words, yaml.safe_load is not used.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-37417",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/37417",
            "specs": [
                "<2.6.3"
            ],
            "v": "<2.6.3"
        }
    ],
    "ocrodjvu": [
        {
            "advisory": "Ocrodjvu 0.6.1 fixes insecure use of temporary files when using Cuneiform. \r\nhttps://bugs.debian.org/598134\r\nhttps://github.com/jwilk/ocrodjvu/commit/5e72e5472dd47817f65ba19830b01aa4f2cb50f8",
            "cve": "CVE-2010-4338",
            "id": "pyup.io-45626",
            "more_info_path": "/vulnerabilities/CVE-2010-4338/45626",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        }
    ],
    "octavia": [
        {
            "advisory": "An access-control flaw was found in the Octavia service when the cloud platform was deployed using Red Hat OpenStack Platform Director. An attacker could cause new amphorae to run based on any arbitrary image. This meant that a remote attacker could upload a new amphorae image and, if requested to spawn new amphorae, Octavia would then pick up the compromised image. See: CVE-2019-3895.",
            "cve": "CVE-2019-3895",
            "id": "pyup.io-37192",
            "more_info_path": "/vulnerabilities/CVE-2019-3895/37192",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Octavia 2.0.3 and 3.0.2 include a fix for CVE-2018-16856: In a default Red Hat Openstack Platform Director installation, openstack-octavia before versions openstack-octavia 2.0.2-5 and openstack-octavia-3.0.1-0.20181009115732 creates log files that are readable by all users. Sensitive information such as private keys can appear in these log files allowing for information exposure.",
            "cve": "CVE-2018-16856",
            "id": "pyup.io-36993",
            "more_info_path": "/vulnerabilities/CVE-2018-16856/36993",
            "specs": [
                "<2.0.2",
                ">=3.0.0.0b1,<3.0.2"
            ],
            "v": "<2.0.2,>=3.0.0.0b1,<3.0.2"
        },
        {
            "advisory": "Amphora Images in OpenStack Octavia >=0.10.0 <2.1.2, >=3.0.0 <3.2.0, >=4.0.0 <4.1.0 allows anyone with access to the management network to bypass client-certificate based authentication and retrieve information or issue configuration commands via simple HTTP requests to the Agent on port https/9443, because the cmd/agent.py gunicorn cert_reqs option is True but is supposed to be ssl.CERT_REQUIRED.",
            "cve": "CVE-2019-17134",
            "id": "pyup.io-37547",
            "more_info_path": "/vulnerabilities/CVE-2019-17134/37547",
            "specs": [
                ">=0.10.0,<2.1.2",
                ">=3.0.0,<3.2.0",
                ">=4.0.0,<4.1.0"
            ],
            "v": ">=0.10.0,<2.1.2,>=3.0.0,<3.2.0,>=4.0.0,<4.1.0"
        }
    ],
    "octobot": [
        {
            "advisory": "WebInterface in OctoBot before 0.4.4 allows remote code execution because Tentacles upload is mishandled.",
            "cve": "CVE-2021-36711",
            "id": "pyup.io-54452",
            "more_info_path": "/vulnerabilities/CVE-2021-36711/54452",
            "specs": [
                ">=0,<0.4.4"
            ],
            "v": ">=0,<0.4.4"
        }
    ],
    "octoprint": [
        {
            "advisory": "OctoPrint 1.7.3 and prior does not have rate limiting on the login page, making it possible for attackers to attempt brute force attacks. The severity of this issue is limited by OctoPrint normally running in a restricted LAN. The `devel` and `maintenance` branches of the repository have a fix that limits the rate of failed login attempts.",
            "cve": "CVE-2022-2822",
            "id": "pyup.io-54464",
            "more_info_path": "/vulnerabilities/CVE-2022-2822/54464",
            "specs": [
                "<1.10.0"
            ],
            "v": "<1.10.0"
        },
        {
            "advisory": "OctoPrint 1.10.0rc1 addresses the CVE-2024-23637. This vulnerability allowed unauthorized admins to alter the passwords of other admin accounts, potentially leading to account lockouts and loss of control over the OctoPrint instance. The update resolves this by enforcing proper authentication procedures. It is recommended that all OctoPrint administrators review their access controls to prevent potential exploitation of this vulnerability.\r\nhttps://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-5626-pw9c-hmjr",
            "cve": "CVE-2024-23637",
            "id": "pyup.io-64726",
            "more_info_path": "/vulnerabilities/CVE-2024-23637/64726",
            "specs": [
                "<1.10.0rc1"
            ],
            "v": "<1.10.0rc1"
        },
        {
            "advisory": "Affected versions of the OctoPrint package are vulnerable to Improper Authentication due to missing reauthentication requirements for sensitive API key operations. The web interface in versions up to and including 1.10.2 allows access to API key management functions in the settings without requiring users to re-enter their password, enabling retrieval, recreation, or deletion of user or global API keys through the authenticated session. An attacker who has gained temporary control over an authenticated victim's browser session can exploit this vulnerability to steal API keys for unauthorized API access or delete keys to disrupt workflows, without needing the victim's credentials.",
            "cve": "CVE-2024-51493",
            "id": "pyup.io-78813",
            "more_info_path": "/vulnerabilities/CVE-2024-51493/78813",
            "specs": [
                "<1.10.3"
            ],
            "v": "<1.10.3"
        },
        {
            "advisory": "OctoPrint provides a web interface for controlling consumer 3D printers. In versions up to and including 1.10.3, OctoPrint has a vulnerability that allows an attacker to bypass the login redirect and directly access the rendered HTML of certain frontend pages. The primary risk lies in potential future modifications to the codebase that might incorrectly rely on the vulnerable internal functions for authentication checks, leading to security vulnerabilities.",
            "cve": "CVE-2025-32788",
            "id": "pyup.io-76901",
            "more_info_path": "/vulnerabilities/CVE-2025-32788/76901",
            "specs": [
                "<1.11.0"
            ],
            "v": "<1.11.0"
        },
        {
            "advisory": "OctoPrint versions up until and including 1.11.1 contain a vulnerability that allows any unauthenticated attacker to send a manipulated broken multipart/form-data request to OctoPrint and through that make the web server component become unresponsive. The issue can be triggered by a broken multipart/form-data request lacking an end boundary to any of OctoPrint's endpoints implemented through the octoprint.server.util.tornado.UploadStorageFallbackHandler request handler. The request handler will get stuck in an endless busy loop, looking for a part of the request that will never come. As Tornado is single-threaded, that will effectively block the whole web server. The vulnerability has been patched in version 1.11.2.",
            "cve": "CVE-2025-48879",
            "id": "pyup.io-77678",
            "more_info_path": "/vulnerabilities/CVE-2025-48879/77678",
            "specs": [
                "<1.11.2"
            ],
            "v": "<1.11.2"
        },
        {
            "advisory": "OctoPrint provides a web interface for controlling consumer 3D printers. OctoPrint versions up until and including 1.11.1 contain a vulnerability that allows an attacker with the FILE_UPLOAD permission to exfiltrate files from the host that OctoPrint has read access to, by moving them into the upload folder where they then can be downloaded from. This vulnerability is fixed in 1.11.2.",
            "cve": "CVE-2025-48067",
            "id": "pyup.io-77679",
            "more_info_path": "/vulnerabilities/CVE-2025-48067/77679",
            "specs": [
                "<1.11.2"
            ],
            "v": "<1.11.2"
        },
        {
            "advisory": "Affected versions of the OctoPrint package are vulnerable to OS Command Injection due to unsanitized upload filenames being interpolated into shell commands configured in system event handlers. The `src/octoprint/events.py` module\u2019s `CommandTrigger` and `SystemEventSubscription` format handler commands with placeholders such as `{__filename}`, `{__filepath}`, `{name}` and `{path}` and\u2014in affected versions\u2014execute them via a shell (e.g., `subprocess.check_call(..., shell=True)`), which allows shell metacharacters embedded in filenames to be interpreted.",
            "cve": "CVE-2025-58180",
            "id": "pyup.io-79474",
            "more_info_path": "/vulnerabilities/CVE-2025-58180/79474",
            "specs": [
                "<1.11.3"
            ],
            "v": "<1.11.3"
        },
        {
            "advisory": "Affected versions of the octoprint package are vulnerable to Cross-site Scripting (XSS) due to insufficient sanitization of printer-supplied message content displayed in Action Command Notification and Action Command Prompt popups. The bundled plugins octoprint.plugins.action_command_notification and octoprint.plugins.action_command_prompt render firmware-provided strings into the web UI without proper HTML escaping, allowing attacker-controlled script to execute in the context of the authenticated user.",
            "cve": "CVE-2025-64187",
            "id": "pyup.io-81287",
            "more_info_path": "/vulnerabilities/CVE-2025-64187/81287",
            "specs": [
                "<1.11.4"
            ],
            "v": "<1.11.4"
        },
        {
            "advisory": "Affected versions of the OctoPrint package are vulnerable to Information Disclosure due to non-constant-time API key comparison. During API key authentication, OctoPrint\u2019s API key validation logic compares the attacker-supplied key against stored keys using a character-by-character equality check that short-circuits on the first mismatch, causing observable response-time differences based on the length of the matching prefix.",
            "cve": "CVE-2026-23892",
            "id": "pyup.io-85198",
            "more_info_path": "/vulnerabilities/CVE-2026-23892/85198",
            "specs": [
                "<1.11.6"
            ],
            "v": "<1.11.6"
        },
        {
            "advisory": "Affected versions of OctoPrint allows remote attackers to obtain sensitive information or cause a denial of service via HTTP requests on port 8081 as the default behavior. From version 1.5.0rc1 onwards, access control is enabled by default. \r\nNOTE: the vendor disputes the significance of this report because their documentation states that with \"blind port forwarding ... Putting OctoPrint onto the public internet is a terrible idea, and I really can't emphasize that enough.\"",
            "cve": "CVE-2018-16710",
            "id": "pyup.io-67596",
            "more_info_path": "/vulnerabilities/CVE-2018-16710/67596",
            "specs": [
                "<1.5.0rc1"
            ],
            "v": "<1.5.0rc1"
        },
        {
            "advisory": "Octoprint 1.8.1 fixes an XSS issue in the user/group delete confirmation.\r\nhttps://github.com/OctoPrint/OctoPrint/commit/77904a71b45e6d017cf4c7e5eb8b8d973693c146",
            "cve": "PVE-2022-49380",
            "id": "pyup.io-49380",
            "more_info_path": "/vulnerabilities/PVE-2022-49380/49380",
            "specs": [
                "<1.8.1"
            ],
            "v": "<1.8.1"
        },
        {
            "advisory": "Octoprint 1.8.2 includes a fix for a open-redirect vulnerability. The issue rises from the inadequate checking of the redirect get variable on the login page. The method used urllib to confirm if the url.scheme and url.netloc are vacant, but this approach does not cover all existing URLs. This vulnerability could potentially allow an attacker to mislead a user to a harmful domain.",
            "cve": "PVE-2023-99955",
            "id": "pyup.io-60899",
            "more_info_path": "/vulnerabilities/PVE-2023-99955/60899",
            "specs": [
                "<1.8.2"
            ],
            "v": "<1.8.2"
        },
        {
            "advisory": "Version 1.8.3 of OctoPrint addresses a security vulnerability that allowed for a Cross-Site Request Forgery (CSRF) attack combined with phishing. In this attack scenario, an admin user could be deceived into visiting a malicious website, which could then install harmful plugins on the OctoPrint server using the admin's login credentials. To mitigate this risk, the latest update has introduced stricter measures for API requests. Now, the API requires a CSRF cookie provided by the server during the initial page load, along with a CSRF header containing the same value for any API request that isn't a GET, HEAD, or OPTIONS request.\r\nhttps://github.com/OctoPrint/OctoPrint/commit/59a0c8e8d79e9d28c4a2dfbf4105f8dd580a8f04",
            "cve": "PVE-2024-64730",
            "id": "pyup.io-64730",
            "more_info_path": "/vulnerabilities/PVE-2024-64730/64730",
            "specs": [
                "<1.8.3"
            ],
            "v": "<1.8.3"
        },
        {
            "advisory": "Octoprint 1.8.3 resolves a vulnerability where a malicious admin user could upload a specially crafted language pack containing one or more symlinks to files on the OctoPrint server, which would then be contained in created backups and could thus be extracted that way. This could be used by a malicious admin user to extract files from the OctoPrint server readable by the system user the OctoPrint server is running under, including OS files outside the scope of OctoPrint. \r\nhttps://github.com/OctoPrint/OctoPrint/commit/3e3c11811e216fb371a33e28412df83f9701e5b0",
            "cve": "PVE-2024-64841",
            "id": "pyup.io-64841",
            "more_info_path": "/vulnerabilities/PVE-2024-64841/64841",
            "specs": [
                "<1.8.3"
            ],
            "v": "<1.8.3"
        },
        {
            "advisory": "Octoprint 1.9.3 fixes the CVE-2023-41047. This vulnerability allowed malicious admins to set up a specially designed GCODE script via the settings, enabling code execution during the rendering of the script. An attacker could exploit this to extract, and manipulate data managed by OctoPrint, or execute arbitrary commands with the rights of the OctoPrint process on the server system. However, GCODE files intended for printing were not affected. This vulnerability specifically impacted GCODE Scripts configured during printer connection, pause, resume, etc., accessible only by users with ADMIN permissions.\r\nhttps://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-fwfg-vprh-97ph",
            "cve": "CVE-2023-41047",
            "id": "pyup.io-64727",
            "more_info_path": "/vulnerabilities/CVE-2023-41047/64727",
            "specs": [
                "<1.9.3"
            ],
            "v": "<1.9.3"
        },
        {
            "advisory": "Affected versions of OctoPrint contain a vulnerability that allows an unauthenticated attacker to completely bypass the authentication if the `autologinLocal` option is enabled within `config.yaml`, even if they come from networks that are not configured as `localNetworks`, spoofing their IP via the `X-Forwarded-For` header. If autologin is not enabled, this vulnerability does not have any impact.. Until the patch has been applied, OctoPrint administrators who have autologin enabled on their instances should disable it and/or make the instance inaccessible from potentially hostile networks like the internet.",
            "cve": "CVE-2024-32977",
            "id": "pyup.io-71959",
            "more_info_path": "/vulnerabilities/CVE-2024-32977/71959",
            "specs": [
                "<=1.10.0"
            ],
            "v": "<=1.10.0"
        },
        {
            "advisory": "OctoPrint provides a web interface for controlling consumer 3D printers. OctoPrint versions up until and including 1.9.3 contain a vulnerability that allows malicious admins to configure or talk a victim with administrator rights into configuring a webcam snapshot URL which when tested through the \"Test\" button included in the web interface will execute JavaScript code in the victims browser when attempting to render the snapshot image. An attacker who successfully talked a victim with admin rights into performing a snapshot test with such a crafted URL could use this to retrieve or modify sensitive configuration settings, interrupt prints or otherwise interact with the OctoPrint instance in a malicious way. The vulnerability is patched in version 1.10.0rc3. OctoPrint administrators are strongly advised to thoroughly vet who has admin access to their installation and what settings they modify based on instructions by strangers.",
            "cve": "CVE-2024-28237",
            "id": "pyup.io-67597",
            "more_info_path": "/vulnerabilities/CVE-2024-28237/67597",
            "specs": [
                "<=1.9.3"
            ],
            "v": "<=1.9.3"
        },
        {
            "advisory": "The Logging subsystem in OctoPrint before 1.6.0 has incorrect access control because it attempts to manage files that are not *.log files.",
            "cve": "CVE-2021-32560",
            "id": "pyup.io-54267",
            "more_info_path": "/vulnerabilities/CVE-2021-32560/54267",
            "specs": [
                ">=0,<1.6.0"
            ],
            "v": ">=0,<1.6.0"
        },
        {
            "advisory": "OctoPrint before 1.6.0 allows XSS because API error messages include the values of input parameters.",
            "cve": "CVE-2021-32561",
            "id": "pyup.io-54268",
            "more_info_path": "/vulnerabilities/CVE-2021-32561/54268",
            "specs": [
                ">=0,<1.6.0"
            ],
            "v": ">=0,<1.6.0"
        },
        {
            "advisory": "Cross-site Scripting (XSS) - DOM in GitHub repository octoprint/octoprint prior to 1.8.0. The login endpoint allows for javascript injection which may lead to account takeover in a phishing scenario.",
            "cve": "CVE-2022-1430",
            "id": "pyup.io-54451",
            "more_info_path": "/vulnerabilities/CVE-2022-1430/54451",
            "specs": [
                ">=0,<1.8.0"
            ],
            "v": ">=0,<1.8.0"
        },
        {
            "advisory": "Cross-site Scripting (XSS) - Generic in GitHub repository octoprint/octoprint prior to 1.8.0.",
            "cve": "CVE-2022-1432",
            "id": "pyup.io-54450",
            "more_info_path": "/vulnerabilities/CVE-2022-1432/54450",
            "specs": [
                ">=0,<1.8.0"
            ],
            "v": ">=0,<1.8.0"
        },
        {
            "advisory": "OctoPrint before 1.8.0 is susceptible to Cross-site Scripting (XSS) due to Chrome interpreting URL objects from unencoded HTML tags in the web page. XSS attacks facilitate executing malicious scripts in a user's browser under the guise of a trusted application, primarily exploiting vulnerabilities through special character injection, like less than and greater than signs, that aren't properly escaped. These attacks may lead to cookie theft, session hijacking, exposure of sensitive information, privileged access exploitation, and malware delivery. XSS can manifest in various forms including stored XSS (where malicious code is stored on the server), reflected XSS (where the code is reflected off the web server following user interaction), DOM-based XSS (directed at the client side without server-side alteration), and mutated XSS (where injected code is modified by the browser). To mitigate XSS risks, best practices include sanitizing data inputs, converting special characters to HTML or URL encoded equivalents, allowing users to disable scripts, redirecting invalid requests, logging and invalidating simultaneous or suspicious logins, enforcing Content Security Policies, and understanding the security features of utilized libraries.",
            "cve": "PVE-2024-99773",
            "id": "pyup.io-66066",
            "more_info_path": "/vulnerabilities/PVE-2024-99773/66066",
            "specs": [
                ">=0,<1.8.0"
            ],
            "v": ">=0,<1.8.0"
        },
        {
            "advisory": "OctoPrint prior to 1.8.3 is vulnerable to Special Element Injection.",
            "cve": "CVE-2022-3607",
            "id": "pyup.io-54570",
            "more_info_path": "/vulnerabilities/CVE-2022-3607/54570",
            "specs": [
                ">=0,<1.8.3"
            ],
            "v": ">=0,<1.8.3"
        },
        {
            "advisory": "Improper Privilege Management in GitHub repository octoprint/octoprint prior to 1.8.3.",
            "cve": "CVE-2022-3068",
            "id": "pyup.io-54547",
            "more_info_path": "/vulnerabilities/CVE-2022-3068/54547",
            "specs": [
                ">=0,<1.8.3"
            ],
            "v": ">=0,<1.8.3"
        },
        {
            "advisory": "Unrestricted Upload of File with Dangerous Type in GitHub repository octoprint/octoprint prior to 1.8.3.",
            "cve": "CVE-2022-2872",
            "id": "pyup.io-54550",
            "more_info_path": "/vulnerabilities/CVE-2022-2872/54550",
            "specs": [
                ">=0,<1.8.3"
            ],
            "v": ">=0,<1.8.3"
        },
        {
            "advisory": "If an attacker comes into the possession of a victim's OctoPrint session cookie through whatever means, the attacker can use this cookie to authenticate as long as the victim's account exists. This issue is fixed in version 1.8.3.",
            "cve": "CVE-2022-2888",
            "id": "pyup.io-54548",
            "more_info_path": "/vulnerabilities/CVE-2022-2888/54548",
            "specs": [
                ">=0,<1.8.3"
            ],
            "v": ">=0,<1.8.3"
        },
        {
            "advisory": "Versions of OctoPrint prior to 1.8.3 did not require the current user password in order to change that users password. As a result users could be locked out of their accounts or have their accounts stolen under certain circumstances.",
            "cve": "CVE-2022-2930",
            "id": "pyup.io-54354",
            "more_info_path": "/vulnerabilities/CVE-2022-2930/54354",
            "specs": [
                ">=0,<1.8.3"
            ],
            "v": ">=0,<1.8.3"
        },
        {
            "advisory": "Affected versions of the OctoPrint package are vulnerable to Cross-site Scripting (XSS) due to missing automatic escaping in the Jinja2 template system configuration. The vulnerability exists in versions up to and including 1.10.2, where the Jinja2 templating engine does not enforce automatic escaping of user-supplied input, affecting critical components, including the login dialog and standalone application key confirmation dialog. An attacker can exploit this vulnerability by crafting malicious links containing XSS payloads and convincing victims to click them or by using a malicious application to trigger the application key workflow with specially crafted parameters, enabling the attacker to retrieve or modify sensitive configuration settings, interrupt print jobs, or perform other malicious interactions with the OctoPrint instance.",
            "cve": "CVE-2024-49377",
            "id": "pyup.io-78826",
            "more_info_path": "/vulnerabilities/CVE-2024-49377/78826",
            "specs": [
                ">=1.8.0rc1,<1.11.3"
            ],
            "v": ">=1.8.0rc1,<1.11.3"
        }
    ],
    "octoprint-nanny": [
        {
            "advisory": "Octoprint-nanny 0.10.0 sends PrintNanny Cloud API requests via forward proxy as a security measure. Cross-origin requests from OctoPrint javascript are disallowed.",
            "cve": "PVE-2022-48252",
            "id": "pyup.io-48252",
            "more_info_path": "/vulnerabilities/PVE-2022-48252/48252",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Octoprint-nanny 0.11.0 updates its dependency 'octoprint' to v1.8.1 to include a security fix.",
            "cve": "PVE-2022-49380",
            "id": "pyup.io-49379",
            "more_info_path": "/vulnerabilities/PVE-2022-49380/49379",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "octue": [
        {
            "advisory": "Octue 0.10.4 updates its dependency 'numpy' to v1.21.0 to include a security fix.",
            "cve": "CVE-2021-33430",
            "id": "pyup.io-44901",
            "more_info_path": "/vulnerabilities/CVE-2021-33430/44901",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Octue 0.43.3 updates its dependency 'werkzeug' to v2.2.3 to include security fixes.",
            "cve": "CVE-2023-23934",
            "id": "pyup.io-53404",
            "more_info_path": "/vulnerabilities/CVE-2023-23934/53404",
            "specs": [
                "<0.43.3"
            ],
            "v": "<0.43.3"
        },
        {
            "advisory": "Octue 0.43.3 updates its dependency 'werkzeug' to v2.2.3 to include security fixes.",
            "cve": "CVE-2023-25577",
            "id": "pyup.io-53405",
            "more_info_path": "/vulnerabilities/CVE-2023-25577/53405",
            "specs": [
                "<0.43.3"
            ],
            "v": "<0.43.3"
        },
        {
            "advisory": "Octue 0.46.1 updates its dependency 'flask' to v2.2.5 to include a security fix.",
            "cve": "CVE-2023-30861",
            "id": "pyup.io-58625",
            "more_info_path": "/vulnerabilities/CVE-2023-30861/58625",
            "specs": [
                "<0.46.1"
            ],
            "v": "<0.46.1"
        },
        {
            "advisory": "Octue 0.46.2 updates its dependency 'protobuf' to version '3.20.3' to include a security fix.\r\nhttps://github.com/octue/octue-sdk-python/commit/b8dc494258381edf7d70ceac98467a89e3b0ecff",
            "cve": "CVE-2022-1941",
            "id": "pyup.io-59233",
            "more_info_path": "/vulnerabilities/CVE-2022-1941/59233",
            "specs": [
                "<0.46.2"
            ],
            "v": "<0.46.2"
        },
        {
            "advisory": "Octue 0.46.2 updates its dependency 'requests' to version '2.31.0' to include a security fix.\r\nhttps://github.com/octue/octue-sdk-python/commit/b8dc494258381edf7d70ceac98467a89e3b0ecff",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-59220",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/59220",
            "specs": [
                "<0.46.2"
            ],
            "v": "<0.46.2"
        },
        {
            "advisory": "Octue version 0.54.0 updates its gunicorn dependency from version \"^20.1\" to version \"^22\" to address security concerns. This upgrade helps mitigate vulnerabilities related to chunked encoding support that could potentially lead to HTTP request smuggling attacks, initially fixed in Gunicorn 20.0.1.",
            "cve": "PVE-2021-40104",
            "id": "pyup.io-68471",
            "more_info_path": "/vulnerabilities/PVE-2021-40104/68471",
            "specs": [
                "<0.54.0"
            ],
            "v": "<0.54.0"
        }
    ],
    "odooghost": [
        {
            "advisory": "Odooghost 0.2.0 includes a security fix: Change ownership of /etc/odoo directory to odoo user.\r\nhttps://github.com/remyz17/odooghost/commit/ac616176a83f405eb4e195656e91240ccf05d360",
            "cve": "PVE-2023-61861",
            "id": "pyup.io-61861",
            "more_info_path": "/vulnerabilities/PVE-2023-61861/61861",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "oe-geoutils": [
        {
            "advisory": "Oe-geoutils 1.5.2 solves security vulnerabilities from external packages 101.",
            "cve": "PVE-2021-37666",
            "id": "pyup.io-37666",
            "more_info_path": "/vulnerabilities/PVE-2021-37666/37666",
            "specs": [
                "<1.5.2"
            ],
            "v": "<1.5.2"
        }
    ],
    "oem": [
        {
            "advisory": "Oem 0.3.0 uses 'defusedxml' to handle XML-related vulnerabilities.\r\nhttps://github.com/bradsease/oem/issues/9",
            "cve": "CVE-2013-1665",
            "id": "pyup.io-43087",
            "more_info_path": "/vulnerabilities/CVE-2013-1665/43087",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Oem 0.3.0 uses 'defusedxml' to handle XML-related vulnerabilities.\r\nhttps://github.com/bradsease/oem/issues/9",
            "cve": "CVE-2013-1664",
            "id": "pyup.io-54876",
            "more_info_path": "/vulnerabilities/CVE-2013-1664/54876",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "offline-rl-congestion-control": [
        {
            "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'offline-rl-congestion-control' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.",
            "cve": "PVE-2024-74237",
            "id": "pyup.io-74237",
            "more_info_path": "/vulnerabilities/PVE-2024-74237/74237",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "offlineimap": [
        {
            "advisory": "offlineimap before 6.3.2 does not check for SSL server certificate validation when \"ssl = yes\" option is specified which can allow man-in-the-middle attacks.",
            "cve": "CVE-2010-4532",
            "id": "pyup.io-67951",
            "more_info_path": "/vulnerabilities/CVE-2010-4532/67951",
            "specs": [
                "<6.3.2-rc1"
            ],
            "v": "<6.3.2-rc1"
        },
        {
            "advisory": "offlineimap before 6.3.4 added support for SSL server certificate validation but it is still possible to use SSL v2 protocol, which is a flawed protocol with multiple security deficiencies.",
            "cve": "CVE-2010-4533",
            "id": "pyup.io-61743",
            "more_info_path": "/vulnerabilities/CVE-2010-4533/61743",
            "specs": [
                "<6.3.4"
            ],
            "v": "<6.3.4"
        }
    ],
    "oger": [
        {
            "advisory": "Oger 1.2 fixes a code injection vulnerability involving eval().\r\nhttps://github.com/OntoGene/OGER/commit/454054dd5d44b7ebab0ec4e453e59822e3c08ca7",
            "cve": "PVE-2022-48031",
            "id": "pyup.io-48031",
            "more_info_path": "/vulnerabilities/PVE-2022-48031/48031",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        }
    ],
    "ohta": [
        {
            "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'ohta' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.",
            "cve": "PVE-2024-74242",
            "id": "pyup.io-74242",
            "more_info_path": "/vulnerabilities/PVE-2024-74242/74242",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "oic": [
        {
            "advisory": "In Python oic before version 1.2.1, there are several related cryptographic issues affecting client implementations that use the library. \r\n\r\nThe issues are: \r\n1) The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg. \r\n2) JWA `none` algorithm was allowed in all flows. \r\n3) oic.consumer.Consumer.parse_authz returns an unverified IdToken. The verification of the token was left to the discretion of the implementator. \r\n4) iat claim was not checked for sanity (i.e. it could be in the future). \r\n\r\nSee CVE-2020-26244.",
            "cve": "CVE-2020-26244",
            "id": "pyup.io-39221",
            "more_info_path": "/vulnerabilities/CVE-2020-26244/39221",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Oic before 0.11.0.0 is vulnerable to insecure encryption caused by utilizing a weak key derivation function alongside a constant initialization vector.\r\nhttps://github.com/CZ-NIC/pyoidc/commit/64665112587ef43a57cb09442dd5dd3d175f583e",
            "cve": "PVE-2024-99766",
            "id": "pyup.io-66659",
            "more_info_path": "/vulnerabilities/PVE-2024-99766/66659",
            "specs": [
                ">=0,<0.11.0.0"
            ],
            "v": ">=0,<0.11.0.0"
        }
    ],
    "oiu": [
        {
            "advisory": "Oiu is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51695",
            "id": "pyup.io-51695",
            "more_info_path": "/vulnerabilities/PVE-2022-51695/51695",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "okdata-aws": [
        {
            "advisory": "Okdata-aws version 4.1.0 has upgraded its idna dependency from version 3.3 to 3.7 in response to CVE-2024-3651.",
            "cve": "CVE-2024-3651",
            "id": "pyup.io-67943",
            "more_info_path": "/vulnerabilities/CVE-2024-3651/67943",
            "specs": [
                "<4.1.0"
            ],
            "v": "<4.1.0"
        }
    ],
    "okdata-cli": [
        {
            "advisory": "Okdata-cli version 0.12.1 updates its dependency \"urlib3\" to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-41852",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/41852",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        }
    ],
    "okdata-sdk": [
        {
            "advisory": "Okdata-sdk version 3.1.1 updates its dependency, upgrading python-keycloak to eliminate the use of python-jose. This change addresses the security vulnerability identified in CVE-2016-7036.",
            "cve": "CVE-2016-7036",
            "id": "pyup.io-67609",
            "more_info_path": "/vulnerabilities/CVE-2016-7036/67609",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        }
    ],
    "oksana": [
        {
            "advisory": "Oksana is a malicious package. It exfiltrates data from the host where it is installed.\r\nhttps://bertusk.medium.com/malicious-pypi-packages-found-exfiltrating-data-and-opening-reverse-shells-87d4afb5d99e",
            "cve": "PVE-2022-47998",
            "id": "pyup.io-47998",
            "more_info_path": "/vulnerabilities/PVE-2022-47998/47998",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "omegaml": [
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-52226",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/52226",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-52221",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/52221",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-23573",
            "id": "pyup.io-52289",
            "more_info_path": "/vulnerabilities/CVE-2022-23573/52289",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'keras' to v2.6.0rc3 to include a security fix.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-37678",
            "id": "pyup.io-52199",
            "more_info_path": "/vulnerabilities/CVE-2021-37678/52199",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pyyaml' to v5.4 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-52253",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/52253",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'jinja2' to v2.11.3 to include a security fix.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-52198",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/52198",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-15207",
            "id": "pyup.io-52273",
            "more_info_path": "/vulnerabilities/CVE-2020-15207/52273",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-10379",
            "id": "pyup.io-52248",
            "more_info_path": "/vulnerabilities/CVE-2020-10379/52248",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-41894",
            "id": "pyup.io-52297",
            "more_info_path": "/vulnerabilities/CVE-2022-41894/52297",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'numpy' to v1.22.2 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-33430",
            "id": "pyup.io-52214",
            "more_info_path": "/vulnerabilities/CVE-2021-33430/52214",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-41880",
            "id": "pyup.io-52275",
            "more_info_path": "/vulnerabilities/CVE-2022-41880/52275",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-52227",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/52227",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'scikitlearn' to v0.24.2 to include a security fix.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "PVE-2022-52255",
            "id": "pyup.io-52256",
            "more_info_path": "/vulnerabilities/PVE-2022-52255/52256",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-21730",
            "id": "pyup.io-52278",
            "more_info_path": "/vulnerabilities/CVE-2022-21730/52278",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'ipython' to v7.16.3 to include a security fix.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2022-21699",
            "id": "pyup.io-52197",
            "more_info_path": "/vulnerabilities/CVE-2022-21699/52197",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'notebook' to v6.4.12 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2019-10856",
            "id": "pyup.io-52209",
            "more_info_path": "/vulnerabilities/CVE-2019-10856/52209",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2022-22817",
            "id": "pyup.io-52235",
            "more_info_path": "/vulnerabilities/CVE-2022-22817/52235",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-10177",
            "id": "pyup.io-52244",
            "more_info_path": "/vulnerabilities/CVE-2020-10177/52244",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-11538",
            "id": "pyup.io-52245",
            "more_info_path": "/vulnerabilities/CVE-2020-11538/52245",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-10378",
            "id": "pyup.io-52247",
            "more_info_path": "/vulnerabilities/CVE-2020-10378/52247",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2019-16865",
            "id": "pyup.io-52238",
            "more_info_path": "/vulnerabilities/CVE-2019-16865/52238",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'lxml' to v4.9.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2022-2309",
            "id": "pyup.io-52203",
            "more_info_path": "/vulnerabilities/CVE-2022-2309/52203",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'joblib' from 0.13.2 to 1.2.0 to include a security fix.",
            "cve": "CVE-2022-21797",
            "id": "pyup.io-51481",
            "more_info_path": "/vulnerabilities/CVE-2022-21797/51481",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'lxml' to v4.9.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-52202",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/52202",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2022-24303",
            "id": "pyup.io-52237",
            "more_info_path": "/vulnerabilities/CVE-2022-24303/52237",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-22576",
            "id": "pyup.io-52294",
            "more_info_path": "/vulnerabilities/CVE-2022-22576/52294",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'protobuf' to v3.18.3 to include a security fix.",
            "cve": "CVE-2022-1941",
            "id": "pyup.io-51480",
            "more_info_path": "/vulnerabilities/CVE-2022-1941/51480",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-23566",
            "id": "pyup.io-52283",
            "more_info_path": "/vulnerabilities/CVE-2022-23566/52283",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'bleach' to v3.3.0 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-6816",
            "id": "pyup.io-52192",
            "more_info_path": "/vulnerabilities/CVE-2020-6816/52192",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-21726",
            "id": "pyup.io-52287",
            "more_info_path": "/vulnerabilities/CVE-2022-21726/52287",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-52222",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/52222",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'urllib3' to v1.26.5 to include security fixes.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-51479",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/51479",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-41900",
            "id": "pyup.io-52276",
            "more_info_path": "/vulnerabilities/CVE-2022-41900/52276",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-25287",
            "id": "pyup.io-52230",
            "more_info_path": "/vulnerabilities/CVE-2021-25287/52230",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2019-19911",
            "id": "pyup.io-52239",
            "more_info_path": "/vulnerabilities/CVE-2019-19911/52239",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-23558",
            "id": "pyup.io-52280",
            "more_info_path": "/vulnerabilities/CVE-2022-23558/52280",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'babel' to v2.9.1 to include a security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-42771",
            "id": "pyup.io-52194",
            "more_info_path": "/vulnerabilities/CVE-2021-42771/52194",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-52233",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/52233",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-15202",
            "id": "pyup.io-52271",
            "more_info_path": "/vulnerabilities/CVE-2020-15202/52271",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'bleach' to v3.3.0 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-6802",
            "id": "pyup.io-52191",
            "more_info_path": "/vulnerabilities/CVE-2020-6802/52191",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'notebook' to v6.4.12 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-26215",
            "id": "pyup.io-52206",
            "more_info_path": "/vulnerabilities/CVE-2020-26215/52206",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-52216",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/52216",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'lxml' to v4.9.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-52201",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/52201",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-5311",
            "id": "pyup.io-52242",
            "more_info_path": "/vulnerabilities/CVE-2020-5311/52242",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-5312",
            "id": "pyup.io-52241",
            "more_info_path": "/vulnerabilities/CVE-2020-5312/52241",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-21740",
            "id": "pyup.io-52290",
            "more_info_path": "/vulnerabilities/CVE-2022-21740/52290",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'psutil' to v5.6.7 to include a security fix.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2019-18874",
            "id": "pyup.io-52249",
            "more_info_path": "/vulnerabilities/CVE-2019-18874/52249",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-15208",
            "id": "pyup.io-52270",
            "more_info_path": "/vulnerabilities/CVE-2020-15208/52270",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'mistune' to v2.0.3 to include a security fix.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2022-34749",
            "id": "pyup.io-52204",
            "more_info_path": "/vulnerabilities/CVE-2022-34749/52204",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-21728",
            "id": "pyup.io-52284",
            "more_info_path": "/vulnerabilities/CVE-2022-21728/52284",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-23560",
            "id": "pyup.io-52279",
            "more_info_path": "/vulnerabilities/CVE-2022-23560/52279",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-35937",
            "id": "pyup.io-51482",
            "more_info_path": "/vulnerabilities/CVE-2022-35937/51482",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-10531",
            "id": "pyup.io-52281",
            "more_info_path": "/vulnerabilities/CVE-2020-10531/52281",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'notebook' to v6.4.12 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2022-29238",
            "id": "pyup.io-52211",
            "more_info_path": "/vulnerabilities/CVE-2022-29238/52211",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-23562",
            "id": "pyup.io-52291",
            "more_info_path": "/vulnerabilities/CVE-2022-23562/52291",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'bleach' to v3.3.0 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-23980",
            "id": "pyup.io-51483",
            "more_info_path": "/vulnerabilities/CVE-2021-23980/51483",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'dask' to v2021.10.0 to include a security fix.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-42343",
            "id": "pyup.io-52196",
            "more_info_path": "/vulnerabilities/CVE-2021-42343/52196",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-15195",
            "id": "pyup.io-52292",
            "more_info_path": "/vulnerabilities/CVE-2020-15195/52292",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-35939",
            "id": "pyup.io-52267",
            "more_info_path": "/vulnerabilities/CVE-2022-35939/52267",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-23574",
            "id": "pyup.io-52285",
            "more_info_path": "/vulnerabilities/CVE-2022-23574/52285",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-15212",
            "id": "pyup.io-52295",
            "more_info_path": "/vulnerabilities/CVE-2020-15212/52295",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'notebook' to v6.4.12 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-32798",
            "id": "pyup.io-52207",
            "more_info_path": "/vulnerabilities/CVE-2021-32798/52207",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-15214",
            "id": "pyup.io-52296",
            "more_info_path": "/vulnerabilities/CVE-2020-15214/52296",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-52219",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/52219",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-27778",
            "id": "pyup.io-52293",
            "more_info_path": "/vulnerabilities/CVE-2022-27778/52293",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-52218",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/52218",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'urllib3' to v1.26.5 to include security fixes.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-51459",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/51459",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pyyaml' to v5.4 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-52254",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/52254",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'notebook' to v6.4.12 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2022-24758",
            "id": "pyup.io-52210",
            "more_info_path": "/vulnerabilities/CVE-2022-24758/52210",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-52234",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/52234",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-52224",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/52224",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-23587",
            "id": "pyup.io-52269",
            "more_info_path": "/vulnerabilities/CVE-2022-23587/52269",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-23559",
            "id": "pyup.io-52286",
            "more_info_path": "/vulnerabilities/CVE-2022-23559/52286",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'notebook' to v6.4.12 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2019-10255",
            "id": "pyup.io-52208",
            "more_info_path": "/vulnerabilities/CVE-2019-10255/52208",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'lxml' to v4.9.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-52200",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/52200",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-5310",
            "id": "pyup.io-52243",
            "more_info_path": "/vulnerabilities/CVE-2020-5310/52243",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-10994",
            "id": "pyup.io-52246",
            "more_info_path": "/vulnerabilities/CVE-2020-10994/52246",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-52223",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/52223",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-13790",
            "id": "pyup.io-52277",
            "more_info_path": "/vulnerabilities/CVE-2020-13790/52277",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-52220",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/52220",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'nbconvert' to v6.3.0b0 to include a security fix.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-32862",
            "id": "pyup.io-52205",
            "more_info_path": "/vulnerabilities/CVE-2021-32862/52205",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'celery' to v5.2.2 to include a security fix.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-23727",
            "id": "pyup.io-52195",
            "more_info_path": "/vulnerabilities/CVE-2021-23727/52195",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-25288",
            "id": "pyup.io-52231",
            "more_info_path": "/vulnerabilities/CVE-2021-25288/52231",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'numpy' to v1.22.2 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-41495",
            "id": "pyup.io-52212",
            "more_info_path": "/vulnerabilities/CVE-2021-41495/52212",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-28675",
            "id": "pyup.io-52228",
            "more_info_path": "/vulnerabilities/CVE-2021-28675/52228",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-21727",
            "id": "pyup.io-52282",
            "more_info_path": "/vulnerabilities/CVE-2022-21727/52282",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-52217",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/52217",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'numpy' to v1.22.2 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-41496",
            "id": "pyup.io-52213",
            "more_info_path": "/vulnerabilities/CVE-2021-41496/52213",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-52225",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/52225",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-11656",
            "id": "pyup.io-52274",
            "more_info_path": "/vulnerabilities/CVE-2020-11656/52274",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pyyaml' to v5.4 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2019-20477",
            "id": "pyup.io-52252",
            "more_info_path": "/vulnerabilities/CVE-2019-20477/52252",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'numpy' to v1.22.2 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-52215",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/52215",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2022-23561",
            "id": "pyup.io-52288",
            "more_info_path": "/vulnerabilities/CVE-2022-23561/52288",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-52236",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/52236",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-52232",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/52232",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-52229",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/52229",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates 'tensorflow' in the docker image to v2.10.0rc3 to include several security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/248",
            "cve": "CVE-2020-15205",
            "id": "pyup.io-52272",
            "more_info_path": "/vulnerabilities/CVE-2020-15205/52272",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/273",
            "cve": "CVE-2020-5313",
            "id": "pyup.io-52240",
            "more_info_path": "/vulnerabilities/CVE-2020-5313/52240",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        },
        {
            "advisory": "Omegaml 0.15.4rc1 updates its Dockerfile dependency 'tensorflow' to v2.11.0rc1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/290",
            "cve": "CVE-2022-0529",
            "id": "pyup.io-55017",
            "more_info_path": "/vulnerabilities/CVE-2022-0529/55017",
            "specs": [
                "<0.15.4rc1"
            ],
            "v": "<0.15.4rc1"
        },
        {
            "advisory": "Omegaml 0.15.4rc1 updates its dependency 'sphinx' to v3.0.4 to include security fixes.",
            "cve": "CVE-2020-11022",
            "id": "pyup.io-55013",
            "more_info_path": "/vulnerabilities/CVE-2020-11022/55013",
            "specs": [
                "<0.15.4rc1"
            ],
            "v": "<0.15.4rc1"
        },
        {
            "advisory": "Omegaml 0.15.4rc1 updates its Dockerfile dependency 'tensorflow' to v2.11.0rc1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/290",
            "cve": "CVE-2022-3515",
            "id": "pyup.io-55016",
            "more_info_path": "/vulnerabilities/CVE-2022-3515/55016",
            "specs": [
                "<0.15.4rc1"
            ],
            "v": "<0.15.4rc1"
        },
        {
            "advisory": "Omegaml 0.15.4rc1 updates its Dockerfile dependency 'tensorflow' to v2.11.0rc1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/290",
            "cve": "CVE-2022-1304",
            "id": "pyup.io-55014",
            "more_info_path": "/vulnerabilities/CVE-2022-1304/55014",
            "specs": [
                "<0.15.4rc1"
            ],
            "v": "<0.15.4rc1"
        },
        {
            "advisory": "Omegaml 0.15.4rc1 updates its dependency 'sphinx' to v3.0.4 to include security fixes.",
            "cve": "CVE-2020-11023",
            "id": "pyup.io-55012",
            "more_info_path": "/vulnerabilities/CVE-2020-11023/55012",
            "specs": [
                "<0.15.4rc1"
            ],
            "v": "<0.15.4rc1"
        },
        {
            "advisory": "Omegaml 0.15.4rc1 updates its Dockerfile dependency 'tensorflow' to v2.11.0rc1 to include security fixes.\r\nhttps://github.com/omegaml/omegaml/pull/290",
            "cve": "CVE-2022-3116",
            "id": "pyup.io-55015",
            "more_info_path": "/vulnerabilities/CVE-2022-3116/55015",
            "specs": [
                "<0.15.4rc1"
            ],
            "v": "<0.15.4rc1"
        },
        {
            "advisory": "Omegaml 0.15.4rc1 updates its dependency 'pygments' to v2.7.4 to include security fixes.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-55011",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/55011",
            "specs": [
                "<0.15.4rc1"
            ],
            "v": "<0.15.4rc1"
        },
        {
            "advisory": "Omegaml 0.15.5 updates its dependency 'pygments' to '>=2.7.4' to include a security fix.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-62175",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/62175",
            "specs": [
                "<0.15.5"
            ],
            "v": "<0.15.5"
        }
    ],
    "omero-figure": [
        {
            "advisory": "Omero-figure 4.4.1 includes a fix for CVE-2021-41132, which also affects the related package 'OMERO.web'.\r\nhttps://www.openmicroscopy.org/security/advisories/2021-SV3",
            "cve": "CVE-2021-41132",
            "id": "pyup.io-42156",
            "more_info_path": "/vulnerabilities/CVE-2021-41132/42156",
            "specs": [
                "<4.4.1"
            ],
            "v": "<4.4.1"
        }
    ],
    "omero-web": [
        {
            "advisory": "Omero-web 5.11.0 includes a fix for CVE-2021-41132: In versions prior to 5.11.0, a variety of templates do not perform proper sanitization through HTML escaping. Due to the lack of sanitization and use of 'jQuery.html()', there are a whole of cross-site scripting possibilities with specially crafted input to a variety of fields.\r\nhttps://www.openmicroscopy.org/security/advisories/2021-SV3",
            "cve": "CVE-2021-41132",
            "id": "pyup.io-42157",
            "more_info_path": "/vulnerabilities/CVE-2021-41132/42157",
            "specs": [
                "<5.11.0"
            ],
            "v": "<5.11.0"
        },
        {
            "advisory": "Omero-web 5.20.0 updates its dependency 'django' minimum requirement to v3.2.19 to include a security fix.",
            "cve": "CVE-2023-31047",
            "id": "pyup.io-58850",
            "more_info_path": "/vulnerabilities/CVE-2023-31047/58850",
            "specs": [
                "<5.20.0"
            ],
            "v": "<5.20.0"
        },
        {
            "advisory": "Omero-web version 5.26.0 addresses a critical security vulnerability (CVE-2024-35180) by validating the JSONP callback parameter. Previously, OMERO.web endpoints with JSONP enabled, such as `/webclient/imgData/`, lacked escaping or validation for the callback parameter, which could be exploited if not properly managed. Although this vulnerability is hard to exploit in the default OMERO.web setup due to jQuery's callback name generation, it poses a significant risk for plugins using these metadata endpoints.",
            "cve": "CVE-2024-35180",
            "id": "pyup.io-71090",
            "more_info_path": "/vulnerabilities/CVE-2024-35180/71090",
            "specs": [
                "<5.26.0"
            ],
            "v": "<5.26.0"
        },
        {
            "advisory": "Affected versions of the omero-web package are vulnerable to Information Disclosure due to error-handling behaviour in the password reset flow that exposes sensitive details. In omeroweb/webadmin/views.py, the password reset handler surfaced omero.CmdError details (including exp.err and exp.err.parameters) directly in the response instead of returning a constant message, enabling user-existence leakage via the \u201cForgot Password\u201d path. An unauthenticated attacker can submit reset requests for arbitrary accounts and compare distinct responses to enumerate valid users and glean internal information, leading to privacy exposure and targeted attacks.",
            "cve": "CVE-2025-54791",
            "id": "pyup.io-78700",
            "more_info_path": "/vulnerabilities/CVE-2025-54791/78700",
            "specs": [
                "<5.29.2"
            ],
            "v": "<5.29.2"
        },
        {
            "advisory": "Affected versions of the omero-web package are vulnerable to Cross-site Scripting (XSS) due to reliance on an unpatched jQuery Form dependency for handling form submission responses. The OMERO.web form handling components invoke jQuery-form\u2019s response-processing routines to construct HTML from server responses and inject it into page DOM elements without sufficiently neutralizing user-controlled content, thereby inheriting jQuery-form\u2019s \u201cUnsafe HTML constructed from library input\u201d weakness and making XSS possible.",
            "cve": "PVE-2025-82000",
            "id": "pyup.io-82000",
            "more_info_path": "/vulnerabilities/PVE-2025-82000/82000",
            "specs": [
                "<5.29.3"
            ],
            "v": "<5.29.3"
        },
        {
            "advisory": "In OMERO 5.3.3 or earlier a user could create an OriginalFile and adjust its path such that it now points to another user's file on the underlying filesystem, then manipulate the user's data.",
            "cve": "CVE-2017-1000438",
            "id": "pyup.io-66895",
            "more_info_path": "/vulnerabilities/CVE-2017-1000438/66895",
            "specs": [
                "<5.3.4"
            ],
            "v": "<5.3.4"
        },
        {
            "advisory": "OMERO.web is open source Django-based software for managing microscopy imaging. OMERO.web before version 5.9.0 loads various information about the current user such as their id, name and the groups they are in, and these are available on the main webclient pages. This represents an information exposure vulnerability. Some additional information being loaded is not used by the webclient and is being removed in this release. This is fixed in version 5.9.0. See CVE-2021-21376.",
            "cve": "CVE-2021-21376",
            "id": "pyup.io-40088",
            "more_info_path": "/vulnerabilities/CVE-2021-21376/40088",
            "specs": [
                "<5.9.0"
            ],
            "v": "<5.9.0"
        },
        {
            "advisory": "OMERO.web is open source Django-based software for managing microscopy imaging. OMERO.web before version 5.9.0 supports redirection to a given URL after performing login or switching the group context. These URLs are not validated, allowing redirection to untrusted sites. OMERO.web 5.9.0 adds URL validation before redirecting. External URLs are not considered valid, unless specified in the omero.web.redirect_allowed_hosts setting. See CVE-2021-21377.",
            "cve": "CVE-2021-21377",
            "id": "pyup.io-40089",
            "more_info_path": "/vulnerabilities/CVE-2021-21377/40089",
            "specs": [
                "<5.9.0"
            ],
            "v": "<5.9.0"
        },
        {
            "advisory": "OMERO.web before 5.6.3 optionally allows sensitive data elements (e.g., a session key) to be passed as URL query parameters. If an attacker tricks a user into clicking a malicious link in OMERO.web, the information in the query parameters may be exposed in the Referer header seen by the target. Information in the URL path such as object IDs may also be exposed.",
            "cve": "CVE-2020-7932",
            "id": "pyup.io-54201",
            "more_info_path": "/vulnerabilities/CVE-2020-7932/54201",
            "specs": [
                ">=0,<5.6.3"
            ],
            "v": ">=0,<5.6.3"
        }
    ],
    "omise": [
        {
            "advisory": "It was found that versions of omise before 0.12.0 had a vulnerability involving the exposure of sensitive data in the logging system.",
            "cve": "PVE-2023-99954",
            "id": "pyup.io-60900",
            "more_info_path": "/vulnerabilities/PVE-2023-99954/60900",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        }
    ],
    "omni-api": [
        {
            "advisory": "Omni-api 0.4.1 includes a more secure handling of errors .\r\nhttps://github.com/hivesolutions/omni_api/commit/ae4a5179b4c8698b4b813e9ca2909fd8b299a307",
            "cve": "PVE-2022-44804",
            "id": "pyup.io-44804",
            "more_info_path": "/vulnerabilities/PVE-2022-44804/44804",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        }
    ],
    "omni-cortex": [
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal attacks. File operations fail to validate file path parameters against directory traversal sequences, leading to attackers being able to read or write arbitrary files outside the intended root directory by submitting requests containing path traversal sequences.",
            "cve": "PVE-2026-84343",
            "id": "pyup.io-84343",
            "more_info_path": "/vulnerabilities/PVE-2026-84343/84343",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Cross-Site Request Forgery (CSRF). The CORS configuration allows wildcard HTTP methods and headers, leading to malicious websites being able to make unauthorized cross-origin requests to API endpoints and perform actions on behalf of authenticated users.",
            "cve": "PVE-2026-84341",
            "id": "pyup.io-84341",
            "more_info_path": "/vulnerabilities/PVE-2026-84341/84341",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Information Disclosure. Activity logging fails to redact sensitive fields before writing to log files, leading to credentials, API tokens, passwords, and private user data being exposed in plain-text logs accessible to system administrators or attackers with log file access.",
            "cve": "PVE-2026-84340",
            "id": "pyup.io-84340",
            "more_info_path": "/vulnerabilities/PVE-2026-84340/84340",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Prompt Injection. LLM prompt construction fails to sanitize user-controlled input, leading to attackers being able to manipulate AI model responses and bypass intended system instructions through specially crafted input that alters the prompt context.",
            "cve": "PVE-2026-84342",
            "id": "pyup.io-84342",
            "more_info_path": "/vulnerabilities/PVE-2026-84342/84342",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Cross-Site Scripting (XSS). The ChatPanel and MemoryCard components fail to sanitize user input before rendering HTML content, leading to arbitrary JavaScript execution in victims' browsers that can steal session tokens, perform unauthorized actions, or exfiltrate sensitive data.",
            "cve": "PVE-2026-84234",
            "id": "pyup.io-84234",
            "more_info_path": "/vulnerabilities/PVE-2026-84234/84234",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        }
    ],
    "omnikdatalogger": [
        {
            "advisory": "Omnikdatalogger 1.10.4 uses secure connection (HTTPS) to interact with PVOutput website.\r\nhttps://github.com/jbouwh/omnikdatalogger/pull/56/commits/85eb0af91b5912295745a2ec074e71354374b8b6",
            "cve": "PVE-2021-43353",
            "id": "pyup.io-43353",
            "more_info_path": "/vulnerabilities/PVE-2021-43353/43353",
            "specs": [
                "<1.10.4"
            ],
            "v": "<1.10.4"
        }
    ],
    "omnizart": [
        {
            "advisory": "Omnizart 0.3.3 updates its dependency 'urllib3' to v1.26.4 to include a security fix.",
            "cve": "CVE-2021-28363",
            "id": "pyup.io-49099",
            "more_info_path": "/vulnerabilities/CVE-2021-28363/49099",
            "specs": [
                "<0.3.3"
            ],
            "v": "<0.3.3"
        },
        {
            "advisory": "Omnizart 0.3.3 updates its dependency 'pyyaml' to v5.4.1 to include a security fix.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-40422",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/40422",
            "specs": [
                "<0.3.3"
            ],
            "v": "<0.3.3"
        }
    ],
    "omorfi": [
        {
            "advisory": "Omorfi 0.9.9 fixes an injection vulnerability in python OOV handling.\r\nhttps://github.com/flammie/omorfi/commit/b4d7a5dba1768a7067fd6bd4e8c80cfe465556ce",
            "cve": "PVE-2022-49400",
            "id": "pyup.io-49400",
            "more_info_path": "/vulnerabilities/PVE-2022-49400/49400",
            "specs": [
                "<0.9.9"
            ],
            "v": "<0.9.9"
        }
    ],
    "oncall": [
        {
            "advisory": "LinkedIn Oncall through 1.4.0 allows reflected XSS via /query because of mishandling of the \"No results found for\" message in the search bar.",
            "cve": "CVE-2021-26722",
            "id": "pyup.io-54025",
            "more_info_path": "/vulnerabilities/CVE-2021-26722/54025",
            "specs": [
                ">=0,<1.4.1"
            ],
            "v": ">=0,<1.4.1"
        }
    ],
    "onecodex": [
        {
            "advisory": "Onecodex 0.10.0 updates its dependency 'requests' to v2.27.1 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-47994",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/47994",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Onecodex 0.9.5 includes a fix for a race condition vulnerability.\r\nhttps://github.com/onecodex/onecodex/pull/390",
            "cve": "PVE-2023-60986",
            "id": "pyup.io-60986",
            "more_info_path": "/vulnerabilities/PVE-2023-60986/60986",
            "specs": [
                "<0.9.5"
            ],
            "v": "<0.9.5"
        }
    ],
    "onefuzz": [
        {
            "advisory": "Onefuzz 1.5.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/microsoft/onefuzz/pull/204",
            "cve": "PVE-2023-59633",
            "id": "pyup.io-59633",
            "more_info_path": "/vulnerabilities/PVE-2023-59633/59633",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        },
        {
            "advisory": "Onefuzz 2.5.0 updates its Rust dependency 'rand_core' to v0.6.2 to include a security fix.\r\nhttps://github.com/microsoft/onefuzz/pull/548",
            "cve": "CVE-2021-27378",
            "id": "pyup.io-39624",
            "more_info_path": "/vulnerabilities/CVE-2021-27378/39624",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Onefuzz 2.7.0 updates its dependency 'jinja2' to v2.11.3 to include a security fix.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-39676",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/39676",
            "specs": [
                "<2.7.0"
            ],
            "v": "<2.7.0"
        },
        {
            "advisory": "Onefuzz 2.31.0 includes a fix for CVE-2021-37705: Starting with OneFuzz 2.12.0 or greater, an incomplete authorization check allows an authenticated user from any Azure Active Directory tenant to make authorized API calls to a vulnerable OneFuzz instance. To be vulnerable, a OneFuzz deployment must be both version 2.12.0 or greater and deployed with the non-default --multi_tenant_domain option. This can result in read/write access to private data such as software vulnerability and crash information, security testing tools and proprietary code and symbols. Via authorized API calls, this also enables tampering with existing data and unauthorized code execution on Azure compute resources. This issue is resolved starting in release 2.31.0, via the addition of application-level check of the bearer token's 'issuer' against an administrator-configured allowlist. As a workaround users can restrict access to the tenant of a deployed OneFuzz instance < 2.31.0 by redeploying in the default configuration, which omits the '--multi_tenant_domain' option.\r\nhttps://github.com/microsoft/onefuzz/security/advisories/GHSA-q5vh-6whw-x745",
            "cve": "CVE-2021-37705",
            "id": "pyup.io-42319",
            "more_info_path": "/vulnerabilities/CVE-2021-37705/42319",
            "specs": [
                ">=2.12.0,<2.31.0"
            ],
            "v": ">=2.12.0,<2.31.0"
        }
    ],
    "onegov-form": [
        {
            "advisory": "Onegov.form before 0.16.1 is not escaping HTML labels in the dynamic formbuilder.\r\nhttps://github.com/OneGov/onegov.form/commit/abce4e1ca620de244460f005f9d2412683552f30",
            "cve": "PVE-2021-42852",
            "id": "pyup.io-25911",
            "more_info_path": "/vulnerabilities/PVE-2021-42852/25911",
            "specs": [
                "<0.16.1"
            ],
            "v": "<0.16.1"
        }
    ],
    "onelogin-aws-assume-role": [
        {
            "advisory": "For security reasons, onelogin-aws-assume-role 1.3.0 removes the ability to provide the IP using a command line parameter and is instead able to provide the IP address at the onelogin.sdk.json file.",
            "cve": "PVE-2021-37158",
            "id": "pyup.io-37158",
            "more_info_path": "/vulnerabilities/PVE-2021-37158/37158",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "onetl": [
        {
            "advisory": "Onetl 0.10.0 includes a fix for a race condition vulnerability which could compromise availability.\r\nhttps://github.com/MobileTeleSystems/onetl/pull/189",
            "cve": "PVE-2023-62978",
            "id": "pyup.io-62978",
            "more_info_path": "/vulnerabilities/PVE-2023-62978/62978",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        }
    ],
    "onionshare-cli": [
        {
            "advisory": "hs.py in OnionShare before 0.9.1 allows local users to modify the hiddenservice by pre-creating the /tmp/onionshare directory.",
            "cve": "CVE-2016-5026",
            "id": "pyup.io-70522",
            "more_info_path": "/vulnerabilities/CVE-2016-5026/70522",
            "specs": [
                "<0.9.1"
            ],
            "v": "<0.9.1"
        },
        {
            "advisory": "The debug_mode function in web/web.py in OnionShare through 1.3.1, when --debug is enabled, uses the /tmp/onionshare_server.log pathname for logging, which might allow local users to overwrite files or obtain sensitive information by using this pathname.",
            "cve": "CVE-2018-19960",
            "id": "pyup.io-66997",
            "more_info_path": "/vulnerabilities/CVE-2018-19960/66997",
            "specs": [
                "<=1.3.1"
            ],
            "v": "<=1.3.1"
        },
        {
            "advisory": "OnionShare is an open source tool that lets you securely and anonymously share files, host websites, and chat with friends using the Tor network. In affected versions it is possible to change the username to that of another chat participant with an additional space character at the end of the name string. An adversary with access to the chat environment can use the rename feature to impersonate other participants by adding whitespace characters at the end of the username.",
            "cve": "CVE-2022-21696",
            "id": "pyup.io-54408",
            "more_info_path": "/vulnerabilities/CVE-2022-21696/54408",
            "specs": [
                ">=0,<2.5"
            ],
            "v": ">=0,<2.5"
        },
        {
            "advisory": "OnionShare is an open source tool that lets you securely and anonymously share files, host websites, and chat with friends using the Tor network. In affected versions the receive mode limits concurrent uploads to 100 per second and blocks other uploads in the same second, which can be triggered by a simple script. An adversary with access to the receive mode can block file upload for others. There is no way to block this attack in public mode due to the anonymity properties of the tor network.",
            "cve": "CVE-2022-21689",
            "id": "pyup.io-54382",
            "more_info_path": "/vulnerabilities/CVE-2022-21689/54382",
            "specs": [
                ">=0,<2.5"
            ],
            "v": ">=0,<2.5"
        },
        {
            "advisory": "OnionShare is an open source tool that lets you securely and anonymously share files, host websites, and chat with friends using the Tor network. Affected versions of the desktop application were found to be vulnerable to denial of service via an undisclosed vulnerability in the QT image parsing. Roughly 20 bytes lead to 2GB memory consumption and this can be triggered multiple times. To be abused, this vulnerability requires rendering in the history tab, so some user interaction is required. An adversary with knowledge of the Onion service address in public mode or with authentication in private mode can perform a Denial of Service attack, which quickly results in out-of-memory for the server. This requires the desktop application with rendered history, therefore the impact is only elevated. This issue has been patched in version 2.5.",
            "cve": "CVE-2022-21688",
            "id": "pyup.io-54384",
            "more_info_path": "/vulnerabilities/CVE-2022-21688/54384",
            "specs": [
                ">=0,<2.5"
            ],
            "v": ">=0,<2.5"
        },
        {
            "advisory": "OnionShare is an open source tool that lets you securely and anonymously share files, host websites, and chat with friends using the Tor network. In affected versions authenticated users (or unauthenticated in public mode) can send messages without being visible in the list of chat participants. This issue has been resolved in version 2.5.",
            "cve": "CVE-2022-21695",
            "id": "pyup.io-54394",
            "more_info_path": "/vulnerabilities/CVE-2022-21695/54394",
            "specs": [
                ">=0,<2.5"
            ],
            "v": ">=0,<2.5"
        },
        {
            "advisory": "OnionShare is an open source tool that lets you securely and anonymously share files, host websites, and chat with friends using the Tor network. The website mode of the onionshare allows to use a hardened CSP, which will block any scripts and external resources. It is not possible to configure this CSP for individual pages and therefore the security enhancement cannot be used for websites using javascript or external resources like fonts or images.",
            "cve": "CVE-2022-21694",
            "id": "pyup.io-54392",
            "more_info_path": "/vulnerabilities/CVE-2022-21694/54392",
            "specs": [
                ">=0,<2.5"
            ],
            "v": ">=0,<2.5"
        },
        {
            "advisory": "OnionShare is an open source tool that lets you securely and anonymously share files, host websites, and chat with friends using the Tor network. In affected versions anyone with access to the chat environment can write messages disguised as another chat participant.",
            "cve": "CVE-2022-21692",
            "id": "pyup.io-54380",
            "more_info_path": "/vulnerabilities/CVE-2022-21692/54380",
            "specs": [
                ">=0,<2.5"
            ],
            "v": ">=0,<2.5"
        },
        {
            "advisory": "OnionShare is an open source tool that lets you securely and anonymously share files, host websites, and chat with friends using the Tor network. In affected versions The path parameter of the requested URL is not sanitized before being passed to the QT frontend. This path is used in all components for displaying the server access history. This leads to a rendered HTML4 Subset (QT RichText editor) in the Onionshare frontend.",
            "cve": "CVE-2022-21690",
            "id": "pyup.io-54388",
            "more_info_path": "/vulnerabilities/CVE-2022-21690/54388",
            "specs": [
                ">=0,<2.5"
            ],
            "v": ">=0,<2.5"
        },
        {
            "advisory": "OnionShare is an open source tool that lets you securely and anonymously share files, host websites, and chat with friends using the Tor network. In affected versions chat participants can spoof their channel leave message, tricking others into assuming they left the chatroom.",
            "cve": "CVE-2022-21691",
            "id": "pyup.io-54386",
            "more_info_path": "/vulnerabilities/CVE-2022-21691/54386",
            "specs": [
                ">=0,<2.5"
            ],
            "v": ">=0,<2.5"
        },
        {
            "advisory": "OnionShare is an open source tool that lets you securely and anonymously share files, host websites, and chat with friends using the Tor network. In affected versions an adversary with a primitive that allows for filesystem access from the context of the Onionshare process can access sensitive files in the entire user home folder. This could lead to the leaking of sensitive data. Due to the automatic exclusion of hidden folders, the impact is reduced. This can be mitigated by usage of the flatpak release.",
            "cve": "CVE-2022-21693",
            "id": "pyup.io-54390",
            "more_info_path": "/vulnerabilities/CVE-2022-21693/54390",
            "specs": [
                ">=0,<2.5"
            ],
            "v": ">=0,<2.5"
        },
        {
            "advisory": "OnionShare 2.3 before 2.4 allows remote unauthenticated attackers to upload files on a non-public node when using the --receive functionality. ",
            "cve": "CVE-2021-41868",
            "id": "pyup.io-54344",
            "more_info_path": "/vulnerabilities/CVE-2021-41868/54344",
            "specs": [
                ">=2.3,<2.4"
            ],
            "v": ">=2.3,<2.4"
        },
        {
            "advisory": "An information disclosure vulnerability in OnionShare 2.3 before 2.4 allows remote unauthenticated attackers to retrieve the full list of participants of a non-public OnionShare node via the --chat feature. ",
            "cve": "CVE-2021-41867",
            "id": "pyup.io-54345",
            "more_info_path": "/vulnerabilities/CVE-2021-41867/54345",
            "specs": [
                ">=2.3,<2.4"
            ],
            "v": ">=2.3,<2.4"
        }
    ],
    "onixcheck": [
        {
            "advisory": "onixcheck 0.8.0 adds secured XML-Parsing via defusedxml.",
            "cve": "PVE-2021-25912",
            "id": "pyup.io-25912",
            "more_info_path": "/vulnerabilities/PVE-2021-25912/25912",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        }
    ],
    "onnx": [
        {
            "advisory": "Onnx 1.13.0 includes a fix for CVE-2022-25882: Versions of the package onnx before 1.13.0 are vulnerable to Directory Traversal as the external_data field of the tensor proto can have a path to the file which is outside the model current directory or user-provided directory.",
            "cve": "CVE-2022-25882",
            "id": "pyup.io-52928",
            "more_info_path": "/vulnerabilities/CVE-2022-25882/52928",
            "specs": [
                "<1.13.0"
            ],
            "v": "<1.13.0"
        },
        {
            "advisory": "A vulnerability in the `download_model_with_test_data` function of the onnx/onnx framework, affected versions, allows for arbitrary file overwrite due to inadequate prevention of path traversal attacks in malicious tar files. This vulnerability enables attackers to overwrite any file on the system, potentially leading to remote code execution, deletion of system, personal, or application files, thus impacting the integrity and availability of the system. The issue arises from the function's handling of tar file extraction without performing security checks on the paths within the tar file, as demonstrated by the ability to overwrite the `/home/kali/.ssh/authorized_keys` file by specifying an absolute path in the malicious tar file.",
            "cve": "CVE-2024-5187",
            "id": "pyup.io-71805",
            "more_info_path": "/vulnerabilities/CVE-2024-5187/71805",
            "specs": [
                "<1.16.2"
            ],
            "v": "<1.16.2"
        },
        {
            "advisory": "A vulnerability in the download_model function of the onnx/onnx framework, before and including version 1.16.1, allows for arbitrary file overwrite due to inadequate prevention of path traversal attacks in malicious tar files. This vulnerability can be exploited by an attacker to overwrite files in the user's directory, potentially leading to remote command execution.",
            "cve": "CVE-2024-7776",
            "id": "pyup.io-76232",
            "more_info_path": "/vulnerabilities/CVE-2024-7776/76232",
            "specs": [
                "<1.17.0"
            ],
            "v": "<1.17.0"
        },
        {
            "advisory": "Versions of the package onnx before and including 1.15.0 are vulnerable to Out-of-bounds Read as the ONNX_ASSERT and ONNX_ASSERTM functions have an off by one string copy.",
            "cve": "CVE-2024-27319",
            "id": "pyup.io-69618",
            "more_info_path": "/vulnerabilities/CVE-2024-27319/69618",
            "specs": [
                "<=1.15.0"
            ],
            "v": "<=1.15.0"
        },
        {
            "advisory": "Versions of the package onnx before and including 1.15.0 are vulnerable to Directory Traversal as the external_data field of the tensor proto can have a path to the file which is outside the model current directory or user-provided directory. The vulnerability occurs as a bypass for the patch added for CVE-2022-25882.",
            "cve": "CVE-2024-27318",
            "id": "pyup.io-65702",
            "more_info_path": "/vulnerabilities/CVE-2024-27318/65702",
            "specs": [
                "<=1.15.0"
            ],
            "v": "<=1.15.0"
        }
    ],
    "onnxruntime": [
        {
            "advisory": "Onnxruntime 1.13.1 updates 'onnx' to v1.12.1 to fix a vulnerability that allows reading of tensor_data outside the model directory.\r\nhttps://github.com/microsoft/onnxruntime/pull/12915",
            "cve": "CVE-2022-25882",
            "id": "pyup.io-53234",
            "more_info_path": "/vulnerabilities/CVE-2022-25882/53234",
            "specs": [
                "<1.13.1"
            ],
            "v": "<1.13.1"
        },
        {
            "advisory": "Onnxruntime 1.13.1 updates 'protobuf' to v3.18.3 to include a security fix.",
            "cve": "CVE-2022-1941",
            "id": "pyup.io-53249",
            "more_info_path": "/vulnerabilities/CVE-2022-1941/53249",
            "specs": [
                "<1.13.1"
            ],
            "v": "<1.13.1"
        }
    ],
    "onvif-python": [
        {
            "advisory": "Affected versions of the onvif-python package are vulnerable to XML External Entity (XXE) Injection due to parsing untrusted WS-Discovery XML with an unsafe default parser configuration.",
            "cve": "PVE-2025-80765",
            "id": "pyup.io-80765",
            "more_info_path": "/vulnerabilities/PVE-2025-80765/80765",
            "specs": [
                "<0.1.8"
            ],
            "v": "<0.1.8"
        }
    ],
    "onyxproxy": [
        {
            "advisory": "Onyxproxy is a malicious package. It harvests and exfiltrates sensitive data.\r\nhttps://blog.phylum.io/malicious-actors-use-unicode-support-in-python-to-evade-detection",
            "cve": "PVE-2023-54816",
            "id": "pyup.io-54816",
            "more_info_path": "/vulnerabilities/PVE-2023-54816/54816",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "oobabot": [
        {
            "advisory": "Oobabot 0.2.3 updates its dependency 'aiohttp' to v3.8.5 to include a security fix.",
            "cve": "CVE-2023-37276",
            "id": "pyup.io-60886",
            "more_info_path": "/vulnerabilities/CVE-2023-37276/60886",
            "specs": [
                "<0.2.3"
            ],
            "v": "<0.2.3"
        }
    ],
    "oobabot-plugin": [
        {
            "advisory": "Oobabot-plugin 0.2.0 updates its dependency 'gradio' to version '3.34.0' to include a fix for an improper input validation vulnerability.\r\nhttps://github.com/chrisrude/oobabot-plugin/commit/b41a3b9006dbb24c6c6e2a5c7c0ecbc86a741f95",
            "cve": "CVE-2023-34239",
            "id": "pyup.io-59356",
            "more_info_path": "/vulnerabilities/CVE-2023-34239/59356",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "oodt": [
        {
            "advisory": "Oodt before 0.4 is vulnerable to XSS attacks via malformed query strings.\r\nhttps://issues.apache.org/jira/browse/OODT-364\r\nhttps://github.com/apache/oodt/commit/cf6ff6b5437cee01792269cc16010e595547a64d",
            "cve": "PVE-2021-25913",
            "id": "pyup.io-25913",
            "more_info_path": "/vulnerabilities/PVE-2021-25913/25913",
            "specs": [
                "<0.4"
            ],
            "v": "<0.4"
        }
    ],
    "ooniprobe": [
        {
            "advisory": "ooniprobe before 1.0.2 is vulnerable to several undisclosed security issues.",
            "cve": "PVE-2021-25914",
            "id": "pyup.io-25914",
            "more_info_path": "/vulnerabilities/PVE-2021-25914/25914",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "opacus": [
        {
            "advisory": "Opacus 0.12.0 updates its dependency 'immer' to v8.0.1 to include a security fix.\r\nhttps://github.com/pytorch/opacus/commit/4e8c77f1fd909fcc97b752ac955f450a1e6d2f71",
            "cve": "CVE-2020-28477",
            "id": "pyup.io-42822",
            "more_info_path": "/vulnerabilities/CVE-2020-28477/42822",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        }
    ],
    "opcua": [
        {
            "advisory": "All versions of package opcua are vulnerable to Denial of Service (DoS) due to a missing limitation on the number of received chunks - per single session or in total for all concurrent sessions. An attacker can exploit this vulnerability by sending an unlimited number of huge chunks (e.g. 2GB each) without sending the Final closing chunk.",
            "cve": "CVE-2022-25304",
            "id": "pyup.io-50733",
            "more_info_path": "/vulnerabilities/CVE-2022-25304/50733",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "open-aea": [
        {
            "advisory": "Open-aea 0.5.3 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/valory-xyz/open-aea/commit/4c5efa6c2268b2f4afe030de7172132bc001036d",
            "cve": "PVE-2023-59676",
            "id": "pyup.io-59676",
            "more_info_path": "/vulnerabilities/PVE-2023-59676/59676",
            "specs": [
                "<0.5.3"
            ],
            "v": "<0.5.3"
        },
        {
            "advisory": "Open-aea 1.17.0 updates its dependency 'mistune' to v2.0.3 to include a security fix.",
            "cve": "CVE-2022-34749",
            "id": "pyup.io-50781",
            "more_info_path": "/vulnerabilities/CVE-2022-34749/50781",
            "specs": [
                "<1.17.0"
            ],
            "v": "<1.17.0"
        }
    ],
    "open-source-insights-api": [
        {
            "advisory": "Open-source-insights-api 0.1.11 updates its dependency 'certifi' to v2023.7.22 to include a security fix.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-61492",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/61492",
            "specs": [
                "<0.1.11"
            ],
            "v": "<0.1.11"
        }
    ],
    "open-web-calendar": [
        {
            "advisory": "Open-web-calendar updates certifi to versions 2023.5.7 and 2023.7.22 due to CVE-2024-39689.",
            "cve": "CVE-2024-39689",
            "id": "pyup.io-72249",
            "more_info_path": "/vulnerabilities/CVE-2024-39689/72249",
            "specs": [
                "<1.17"
            ],
            "v": "<1.17"
        },
        {
            "advisory": "Open-web-calendar version addresses a Host Header Injection vulnerability  This improvement includes the addition of ALLOWED_HOSTS settings to prevent unauthorized manipulation of the Host header. The vulnerability could allow malicious users to change or redirect the host header, potentially impacting sensitive operations such as password resets, registrations, and email functionalities.",
            "cve": "PVE-2024-72246",
            "id": "pyup.io-72246",
            "more_info_path": "/vulnerabilities/PVE-2024-72246/72246",
            "specs": [
                "<1.34"
            ],
            "v": "<1.34"
        },
        {
            "advisory": "Open-web-calendar removes CSS attacks originating from event sources by addressing HTML injection vulnerabilities. This security improvement mitigates Cross-Site Scripting (XSS) attacks that could exploit embedded ICS files. Previously, the calendar embedded ICS files without verifying their JavaScript or CSS content, posing a risk. An attacker could potentially manipulate an iframe to reload and spoof a trusted page, leading to credential theft.",
            "cve": "PVE-2024-72247",
            "id": "pyup.io-72247",
            "more_info_path": "/vulnerabilities/PVE-2024-72247/72247",
            "specs": [
                "<1.39"
            ],
            "v": "<1.39"
        },
        {
            "advisory": "Open Web Calendar affected versions are vulnerable to Cross-Site Scripting (CWE-79). Attackers could inject malicious JavaScript through unsafe URL protocols or unsanitized error messages, leading to data theft or session hijacking.",
            "cve": "PVE-2025-75167",
            "id": "pyup.io-75167",
            "more_info_path": "/vulnerabilities/PVE-2025-75167/75167",
            "specs": [
                "<1.45"
            ],
            "v": "<1.45"
        }
    ],
    "open-webui": [
        {
            "advisory": "In version v0.3.10 of open-webui/open-webui, the api/v1/utils/pdf endpoint lacks authentication mechanisms, allowing unauthenticated attackers to access the PDF generation service. This vulnerability can be exploited by sending a POST request with an excessively large payload, potentially leading to server resource exhaustion and denial of service (DoS). Additionally, unauthorized users can misuse the endpoint to generate PDFs without verification, resulting in service misuse and potential operational and financial impacts.",
            "cve": "CVE-2024-8053",
            "id": "pyup.io-76220",
            "more_info_path": "/vulnerabilities/CVE-2024-8053/76220",
            "specs": [
                "<0.3.10"
            ],
            "v": "<0.3.10"
        },
        {
            "advisory": "In version v0.3.32 of open-webui/open-webui, the application allows users to submit large payloads in the email and password fields during the sign-in process due to the lack of character length validation on these inputs. This vulnerability can lead to a Denial of Service (DoS) condition when a user submits excessively large strings, exhausting server resources such as CPU, memory, and disk space, and rendering the service unavailable for legitimate users. This makes the server susceptible to resource exhaustion attacks without requiring authentication.",
            "cve": "CVE-2024-12534",
            "id": "pyup.io-76264",
            "more_info_path": "/vulnerabilities/CVE-2024-12534/76264",
            "specs": [
                "<0.3.32"
            ],
            "v": "<0.3.32"
        },
        {
            "advisory": "In Open-webui/open-webui affected versions, the absence of authentication mechanisms allows any unauthenticated attacker to access the api/v1/utils/code/format endpoint. If a malicious actor sends a POST request with an excessively high volume of content, the server could become completely unresponsive. This could lead to severe performance issues, causing the server to become unresponsive or experience significant degradation, ultimately resulting in service interruptions for legitimate users.",
            "cve": "CVE-2024-12537",
            "id": "pyup.io-76263",
            "more_info_path": "/vulnerabilities/CVE-2024-12537/76263",
            "specs": [
                "<0.3.32"
            ],
            "v": "<0.3.32"
        },
        {
            "advisory": "A vulnerability in open-webui/open-webui versions <= 0.3.8 allows remote code execution by non-admin users via Cross-Site Request Forgery (CSRF). The application uses cookies with the SameSite attribute set to lax for authentication and lacks CSRF tokens. This allows an attacker to craft a malicious HTML that, when accessed by a victim, can modify the Python code of an existing pipeline and execute arbitrary code with the victim's privileges.",
            "cve": "CVE-2024-7806",
            "id": "pyup.io-76229",
            "more_info_path": "/vulnerabilities/CVE-2024-7806/76229",
            "specs": [
                "<0.3.33"
            ],
            "v": "<0.3.33"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Information Disclosure due to missing authorization checks on prompt retrieval endpoints. The /api/v1/prompts/ and /api/v1/prompts/command/{command_id} endpoints fail to verify whether the requesting user has administrator privileges before returning prompt data, allowing any authenticated user to enumerate and access all prompts in the system.",
            "cve": "CVE-2024-7045",
            "id": "pyup.io-76230",
            "more_info_path": "/vulnerabilities/CVE-2024-7045/76230",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Stored Cross-Site Scripting (XSS) due to insufficient input sanitization in the chat file upload functionality. The file upload feature fails to properly validate or sanitize file content before storage and subsequent display, allowing malicious JavaScript to be embedded within uploaded files. An attacker can exploit this vulnerability by uploading a file containing malicious JavaScript code and sharing the file URL or chat session with victims, causing the script to execute in the victims' browsers and potentially leading to session hijacking, data theft, or phishing attacks.",
            "cve": "CVE-2024-7044",
            "id": "pyup.io-76245",
            "more_info_path": "/vulnerabilities/CVE-2024-7044/76245",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "An improper access control vulnerability in open-webui/open-webui v0.3.8 allows an attacker to view admin details. The application does not verify whether the attacker is an administrator, allowing the attacker to directly call the /api/v1/auths/admin/details interface to retrieve the first admin (owner) details.",
            "cve": "CVE-2024-7046",
            "id": "pyup.io-76231",
            "more_info_path": "/vulnerabilities/CVE-2024-7046/76231",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Cross-Site Request Forgery (CSRF) due to using GET requests for state-changing operations. The endpoints /rag/api/v1/reset, /rag/api/v1/reset/db, /api/v1/memories/reset, and /rag/api/v1/reset/uploads perform sensitive deletion and reset operations via GET methods without CSRF protection, violating RESTful design principles.",
            "cve": "CVE-2024-7035",
            "id": "pyup.io-76234",
            "more_info_path": "/vulnerabilities/CVE-2024-7035/76234",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "In open-webui/open-webui version v0.3.8, there is an improper privilege management vulnerability. The application allows an attacker, acting as an admin, to delete other administrators via the API endpoint. This action is restricted by the user interface but can be performed through direct API calls.",
            "cve": "CVE-2024-7039",
            "id": "pyup.io-76250",
            "more_info_path": "/vulnerabilities/CVE-2024-7039/76250",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "An improper access control vulnerability in open-webui/open-webui v0.3.8 allows attackers to view and delete any files. The application does not verify whether the attacker is an administrator, allowing the attacker to directly call the GET /api/v1/files/ interface to retrieve information on all files uploaded by users, which includes the ID values. The attacker can then use the GET /api/v1/files/{fileid} interface to obtain information on any file and the DELETE /api/v1/files/{fileid} interface to delete any file.",
            "cve": "CVE-2024-7043",
            "id": "pyup.io-76247",
            "more_info_path": "/vulnerabilities/CVE-2024-7043/76247",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Arbitrary File Overwrite due to improper path handling on Windows systems. The download_model endpoint fails to properly validate file paths when processing model downloads, allowing path traversal sequences to write files outside the intended directory.",
            "cve": "CVE-2024-7033",
            "id": "pyup.io-76236",
            "more_info_path": "/vulnerabilities/CVE-2024-7033/76236",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "A vulnerability in open-webui/open-webui allows an attacker with a user-level account to perform a session fixation attack. The session cookie for all users is set with the default SameSite=Lax and does not have the Secure flag enabled, allowing the session cookie to be sent over HTTP to a cross-origin domain. An attacker can exploit this by embedding a malicious markdown image in a chat, which, when viewed by an administrator, sends the admin's session cookie to the attacker's server. This can lead to a stealthy administrator account takeover, potentially resulting in remote code execution (RCE) due to the elevated privileges of administrator accounts.",
            "cve": "CVE-2024-7053",
            "id": "pyup.io-76224",
            "more_info_path": "/vulnerabilities/CVE-2024-7053/76224",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Arbitrary File Overwrite due to improper input validation of user-supplied filenames. The /models/upload endpoint constructs file paths using file_path = f\"{UPLOAD_DIR}/{file.filename}\" without sanitizing the file.filename parameter, allowing directory traversal sequences to escape the intended upload directory. An attacker can exploit this vulnerability by crafting malicious filenames containing path traversal sequences to overwrite arbitrary files on the system, potentially modifying system binaries, configuration files, or sensitive data to achieve remote code execution.",
            "cve": "CVE-2024-7034",
            "id": "pyup.io-76243",
            "more_info_path": "/vulnerabilities/CVE-2024-7034/76243",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "The /openai/models endpoint in open-webui/open-webui version 0.3.8 is vulnerable to Server-Side Request Forgery (SSRF). An attacker can change the OpenAI URL to any URL without checks, causing the endpoint to send a request to the specified URL and return the output. This vulnerability allows the attacker to access internal services and potentially gain command execution by accessing instance secrets.",
            "cve": "CVE-2024-7959",
            "id": "pyup.io-76235",
            "more_info_path": "/vulnerabilities/CVE-2024-7959/76235",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "In version 0.3.8 of open-webui, an endpoint for converting markdown to HTML is exposed without authentication. A maliciously crafted markdown payload can cause the server to spend excessive time converting it, leading to a denial of service. The server becomes unresponsive to other requests until the conversion is complete.",
            "cve": "CVE-2024-7983",
            "id": "pyup.io-76216",
            "more_info_path": "/vulnerabilities/CVE-2024-7983/76216",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "A stored cross-site scripting (XSS) vulnerability exists in open-webui/open-webui version 0.3.8. The vulnerability is present in the /api/v1/models/add endpoint, where the model description field is improperly sanitized before being rendered in chat. This allows an attacker to inject malicious scripts that can be executed by any user, including administrators, potentially leading to arbitrary code execution.",
            "cve": "CVE-2024-7990",
            "id": "pyup.io-76222",
            "more_info_path": "/vulnerabilities/CVE-2024-7990/76222",
            "specs": [
                "<0.3.8"
            ],
            "v": "<0.3.8"
        },
        {
            "advisory": "OpenWebUI version 0.3.0 contains a vulnerability in the audio API endpoint /audio/api/v1/transcriptions that allows for arbitrary file upload. The application performs insufficient validation on the file.content_type and allows user-controlled filenames, leading to a path traversal vulnerability. This can be exploited by an authenticated user to overwrite critical files within the Docker container, potentially leading to remote code execution as the root user.",
            "cve": "CVE-2024-8060",
            "id": "pyup.io-76221",
            "more_info_path": "/vulnerabilities/CVE-2024-8060/76221",
            "specs": [
                "<0.5.17"
            ],
            "v": "<0.5.17"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Code Injection due to unsafe execution of untrusted Server-Sent Events (SSE) \u201cexecute\u201d payloads from external model servers. The Direct Connections frontend SSE handler evaluates event.data.code with a new Function() for executing events without validating the event origin or sandboxing, granting injected code full access to the browser context, including localStorage tokens.",
            "cve": "CVE-2025-64496",
            "id": "pyup.io-81483",
            "more_info_path": "/vulnerabilities/CVE-2025-64496/81483",
            "specs": [
                "<0.6.35"
            ],
            "v": "<0.6.35"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Cross-site Scripting (XSS) due to unsanitized user-controlled HTML being assigned to innerHTML when \u201cInsert Prompt as Rich Text\u201d is enabled. The replaceCommandWithText function in src/lib/components/common/RichTextInput.svelte parses prompt text with marked.parse and injects it into a temporary element via tempDiv.innerHTML without sanitization, enabling stored DOM XSS through custom prompts.",
            "cve": "CVE-2025-64495",
            "id": "pyup.io-81482",
            "more_info_path": "/vulnerabilities/CVE-2025-64495/81482",
            "specs": [
                "<0.6.35"
            ],
            "v": "<0.6.35"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Server-Side Request Forgery (SSRF) due to unvalidated arbitrary URL processing in the /api/v1/retrieval/process/web endpoint. The backend.open_webui.routers.retrieval.process_web handler passes the user-controlled form_data.url parameter directly into get_content_from_url(), which via get_loader(), get_web_loader() and YoutubeLoader() fetches the supplied URL without restrictions on private IP ranges, localhost, cloud metadata endpoints, or disallowed protocols.",
            "cve": "CVE-2025-65958",
            "id": "pyup.io-82330",
            "more_info_path": "/vulnerabilities/CVE-2025-65958/82330",
            "specs": [
                "<0.6.37"
            ],
            "v": "<0.6.37"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Cross-site Scripting (XSS) due to insecure handling of user-supplied prompts that are incorporated into the web UI context. The prompt processing mechanism does not sanitize or neutralize embedded JavaScript, allowing crafted prompts to inject persistent script code via stored user input. An attacker can exploit this by submitting a malicious prompt that executes arbitrary JavaScript when viewed in the Open WebUI interface, enabling session hijacking, content manipulation, or sensitive data theft from users\u2019 browser contexts.",
            "cve": "CVE-2024-6706",
            "id": "pyup.io-78757",
            "more_info_path": "/vulnerabilities/CVE-2024-6706/78757",
            "specs": [
                "<=0.1.105"
            ],
            "v": "<=0.1.105"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Insecure Direct Object Reference (IDOR) due to flawed decentralization in the memory update endpoint. The API endpoint `/api/v1/memories/{id}/update` in the `backend/apps/webui/routers/memories.py` module permits editing arbitrary user memories without proper authorization checks. An attacker who can access the memory update endpoint can manipulate the `{id}` parameter to modify other users\u2019 memories, leading to unauthorized integrity impact and potential data tampering across user records.",
            "cve": "CVE-2024-7041",
            "id": "pyup.io-78806",
            "more_info_path": "/vulnerabilities/CVE-2024-7041/78806",
            "specs": [
                "<=0.3.8"
            ],
            "v": "<=0.3.8"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Arbitrary File Write and Delete due to unsanitized concatenation of the user-controlled `filename` with `CACHE_DIR`. The `/api/pipelines/upload` endpoint directly appends the `file.filename` parameter to `CACHE_DIR` without validating traversal sequences or disallowed path components, enabling arbitrary filesystem operations. An attacker with access can craft a request to overwrite or delete arbitrary files on the host system, potentially leading to remote code execution or service disruption.",
            "cve": "CVE-2024-7037",
            "id": "pyup.io-78784",
            "more_info_path": "/vulnerabilities/CVE-2024-7037/78784",
            "specs": [
                "<=0.3.8"
            ],
            "v": "<=0.3.8"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Information Disclosure due to differentiated error messages that reveal file existence and directory information. The embedding model update logic in the `main.py` under the `backend/apps/rag` module performs a file existence check and returns distinct error messages depending on whether the specified model path exists or is misconfigured. An attacker with administrative access to the update feature can enumerate file names and traverse directories on the host by observing error responses, potentially exposing sensitive file system information to unauthorized parties.",
            "cve": "CVE-2024-7038",
            "id": "pyup.io-78803",
            "more_info_path": "/vulnerabilities/CVE-2024-7038/78803",
            "specs": [
                "<=0.3.8"
            ],
            "v": "<=0.3.8"
        },
        {
            "advisory": "Affected versions of the Open WebUI package are vulnerable to Denial of Service (DoS) due to improper input validation on user registration fields. The signup functionality fails to limit the size of the 'name' field input, allowing excessively large text values to be stored in the database, which causes the Admin panel to become unresponsive when attempting to render or process these oversized entries.",
            "cve": "CVE-2024-7036",
            "id": "pyup.io-78835",
            "more_info_path": "/vulnerabilities/CVE-2024-7036/78835",
            "specs": [
                "<=0.3.8"
            ],
            "v": "<=0.3.8"
        },
        {
            "advisory": "Affected versions of the open-webui package are vulnerable to Incorrect Access Control due to missing ownership checks on task cancellation requests. The /api/tasks/stop/ API endpoint in open_webui.main accepts a task identifier from the requester and unconditionally cancels the referenced task without validating that the authenticated user owns or initiated the underlying LLM job.",
            "cve": "CVE-2025-63681",
            "id": "pyup.io-82328",
            "more_info_path": "/vulnerabilities/CVE-2025-63681/82328",
            "specs": [
                "<=0.6.33"
            ],
            "v": "<=0.6.33"
        }
    ],
    "openadapt": [
        {
            "advisory": "Openadapt 0.1.0 modifies export_sql to use paramerterized queries to prevent sql injection.\r\nhttps://github.com/OpenAdaptAI/OpenAdapt/commit/9dc1850918e81648b9885dd8a1be836d5e8d95ef",
            "cve": "PVE-2023-62826",
            "id": "pyup.io-62826",
            "more_info_path": "/vulnerabilities/PVE-2023-62826/62826",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        }
    ],
    "openai-copilot": [
        {
            "advisory": "Openai-copilot 0.2.4 updates its dependency 'langchain' to v0.0.264 to include a security fix.",
            "cve": "CVE-2023-34541",
            "id": "pyup.io-61667",
            "more_info_path": "/vulnerabilities/CVE-2023-34541/61667",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        },
        {
            "advisory": "Openai-copilot 0.2.4 updates its dependency 'langchain' to v0.0.264 to include a security fix.\r\nhttps://github.com/feiskyer/openai-copilot/compare/v0.2.3...v0.2.4#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711R17",
            "cve": "CVE-2023-36189",
            "id": "pyup.io-61669",
            "more_info_path": "/vulnerabilities/CVE-2023-36189/61669",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        },
        {
            "advisory": "Openai-copilot 0.2.5 updates its dependency 'aiohttp' to v3.8.6 to include a security fix.",
            "cve": "PVE-2023-61657",
            "id": "pyup.io-61666",
            "more_info_path": "/vulnerabilities/PVE-2023-61657/61666",
            "specs": [
                "<0.2.5"
            ],
            "v": "<0.2.5"
        }
    ],
    "openai-model-registry": [
        {
            "advisory": "Affected versions of openai-model-registry are potentially vulnerable to thread safety and resource leak issues. The flaw exists in the registry cleanup routine and network request handling methods where response objects are not properly closed.",
            "cve": "PVE-2025-75982",
            "id": "pyup.io-75982",
            "more_info_path": "/vulnerabilities/PVE-2025-75982/75982",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "openapi-core": [
        {
            "advisory": "Openapi-core 0.13.0 includes a fix for CVE-2019-19844. It also introduces security validation with an API Key and support for HTTP security types.\r\nhttps://github.com/python-openapi/openapi-core/commit/745736b5c202ab9768bf4efb869934897d667647",
            "cve": "CVE-2019-19844",
            "id": "pyup.io-37894",
            "more_info_path": "/vulnerabilities/CVE-2019-19844/37894",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        }
    ],
    "openapi-pydantic": [
        {
            "advisory": "Affected versions of 'openapi-pydantic' are potentially vulnerable due to a transitive dependency on `black` versions before 24.3.0, which are susceptible to a Regular Expression Denial of Service (ReDoS) vulnerability.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-71543",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/71543",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        }
    ],
    "openapi-python-client": [
        {
            "advisory": "In openapi-python-client before version 0.5.3, there is a path traversal vulnerability. If a user generated a client using a maliciously crafted OpenAPI document, it is possible for generated files to be placed in arbitrary locations on disk. See: CVE-2020-15141.",
            "cve": "CVE-2020-15141",
            "id": "pyup.io-38690",
            "more_info_path": "/vulnerabilities/CVE-2020-15141/38690",
            "specs": [
                "<0.5.3"
            ],
            "v": "<0.5.3"
        },
        {
            "advisory": "In openapi-python-client before version 0.5.3, clients generated with a maliciously crafted OpenAPI Document can generate arbitrary Python code. Subsequent execution of this malicious client is arbitrary code execution. See: CVE-2020-15142.",
            "cve": "CVE-2020-15142",
            "id": "pyup.io-38691",
            "more_info_path": "/vulnerabilities/CVE-2020-15142/38691",
            "specs": [
                "<0.5.3"
            ],
            "v": "<0.5.3"
        }
    ],
    "openapigenerator": [
        {
            "advisory": "Openapigenerator 3.2.1 updates its dependency 'superagent' to v3.7.0 to include a security fix.",
            "cve": "CVE-2017-16129",
            "id": "pyup.io-45629",
            "more_info_path": "/vulnerabilities/CVE-2017-16129/45629",
            "specs": [
                "<3.2.1"
            ],
            "v": "<3.2.1"
        },
        {
            "advisory": "Openapigenerator 3.3.2 updates its Maven dependency 'jackson-databind' to v2.8.11.2 to include security fixes.",
            "cve": "CVE-2018-12023",
            "id": "pyup.io-45764",
            "more_info_path": "/vulnerabilities/CVE-2018-12023/45764",
            "specs": [
                "<3.3.2"
            ],
            "v": "<3.3.2"
        },
        {
            "advisory": "Openapigenerator 3.3.2 updates its Maven dependency 'jackson-databind' to v2.8.11.2 to include security fixes.",
            "cve": "CVE-2018-12022",
            "id": "pyup.io-45631",
            "more_info_path": "/vulnerabilities/CVE-2018-12022/45631",
            "specs": [
                "<3.3.2"
            ],
            "v": "<3.3.2"
        },
        {
            "advisory": "Apenapigenerator v4.0.0-beta3 updates its Maven dependency 'gradle' to v2.14.1 to fix a vulnerability.",
            "cve": "CVE-2016-6199",
            "id": "pyup.io-45602",
            "more_info_path": "/vulnerabilities/CVE-2016-6199/45602",
            "specs": [
                "<4.0.0b3"
            ],
            "v": "<4.0.0b3"
        },
        {
            "advisory": "Openapigenerator 4.0.0beta2 updates its Maven dependency 'jackson-databind' to v2.8.11.3 to include security fixes.",
            "cve": "CVE-2018-19360",
            "id": "pyup.io-45632",
            "more_info_path": "/vulnerabilities/CVE-2018-19360/45632",
            "specs": [
                "<4.0.0beta2"
            ],
            "v": "<4.0.0beta2"
        },
        {
            "advisory": "Openapigenerator 4.0.0beta2 updates its Maven dependency 'jackson-databind' to v2.8.11.3 to include security fixes.",
            "cve": "CVE-2018-19361",
            "id": "pyup.io-45762",
            "more_info_path": "/vulnerabilities/CVE-2018-19361/45762",
            "specs": [
                "<4.0.0beta2"
            ],
            "v": "<4.0.0beta2"
        },
        {
            "advisory": "Openapigenerator 4.0.0beta2 updates its Maven dependency 'jackson-databind' to v2.8.11.3 to include security fixes.",
            "cve": "CVE-2018-19362",
            "id": "pyup.io-45763",
            "more_info_path": "/vulnerabilities/CVE-2018-19362/45763",
            "specs": [
                "<4.0.0beta2"
            ],
            "v": "<4.0.0beta2"
        },
        {
            "advisory": "Openapigenerator 4.0.2 updates the babel-cli version to fix security issue.\r\nhttps://github.com/advisories/GHSA-g95f-p29q-9xw4",
            "cve": "PVE-2019-45633",
            "id": "pyup.io-45633",
            "more_info_path": "/vulnerabilities/PVE-2019-45633/45633",
            "specs": [
                "<4.0.2"
            ],
            "v": "<4.0.2"
        },
        {
            "advisory": "Openapigenerator 4.0.3 updates flow-copy-source dependency (mem) to include a security fix.\r\nhttps://github.com/OpenAPITools/openapi-generator/pull/3296",
            "cve": "PVE-2019-45634",
            "id": "pyup.io-45634",
            "more_info_path": "/vulnerabilities/PVE-2019-45634/45634",
            "specs": [
                "<4.0.3"
            ],
            "v": "<4.0.3"
        },
        {
            "advisory": "Openapigenerator 4.1.0 updates its dependency 'lodash' to versions >=4.17.13 to include a security fix.",
            "cve": "CVE-2019-10744",
            "id": "pyup.io-45635",
            "more_info_path": "/vulnerabilities/CVE-2019-10744/45635",
            "specs": [
                "<4.1.0"
            ],
            "v": "<4.1.0"
        },
        {
            "advisory": "Openapigenerator 4.1.3 updates its Maven dependency 'jackson-databind' to v2.9.10 to include security fixes.",
            "cve": "CVE-2019-14892",
            "id": "pyup.io-45760",
            "more_info_path": "/vulnerabilities/CVE-2019-14892/45760",
            "specs": [
                "<4.1.3"
            ],
            "v": "<4.1.3"
        },
        {
            "advisory": "Openapigenerator 4.1.3 updates its Maven dependency 'jackson-databind' to v2.9.10 to include security fixes.",
            "cve": "CVE-2019-17267",
            "id": "pyup.io-45636",
            "more_info_path": "/vulnerabilities/CVE-2019-17267/45636",
            "specs": [
                "<4.1.3"
            ],
            "v": "<4.1.3"
        },
        {
            "advisory": "Openapigenerator 4.1.3 updates its Maven dependency 'jackson-databind' to v2.9.10 to include security fixes.",
            "cve": "CVE-2019-16335",
            "id": "pyup.io-45758",
            "more_info_path": "/vulnerabilities/CVE-2019-16335/45758",
            "specs": [
                "<4.1.3"
            ],
            "v": "<4.1.3"
        },
        {
            "advisory": "Openapigenerator 4.1.3 updates its Maven dependency 'jackson-databind' to v2.9.10 to include security fixes.",
            "cve": "CVE-2019-14540",
            "id": "pyup.io-45761",
            "more_info_path": "/vulnerabilities/CVE-2019-14540/45761",
            "specs": [
                "<4.1.3"
            ],
            "v": "<4.1.3"
        },
        {
            "advisory": "Openapigenerator 4.1.3 updates its Maven dependency 'jackson-databind' to v2.9.10 to include security fixes.",
            "cve": "CVE-2019-14893",
            "id": "pyup.io-45759",
            "more_info_path": "/vulnerabilities/CVE-2019-14893/45759",
            "specs": [
                "<4.1.3"
            ],
            "v": "<4.1.3"
        },
        {
            "advisory": "Openapigenerator 4.2.1 updates its Maven dependency 'jackson-databind' to v2.9.10.1 to include security fixes.",
            "cve": "CVE-2019-17531",
            "id": "pyup.io-45757",
            "more_info_path": "/vulnerabilities/CVE-2019-17531/45757",
            "specs": [
                "<4.2.1"
            ],
            "v": "<4.2.1"
        },
        {
            "advisory": "Openapigenerator 4.2.1 updates its Maven dependency 'jackson-databind' to v2.9.10.1 to include security fixes.",
            "cve": "CVE-2019-16943",
            "id": "pyup.io-45756",
            "more_info_path": "/vulnerabilities/CVE-2019-16943/45756",
            "specs": [
                "<4.2.1"
            ],
            "v": "<4.2.1"
        },
        {
            "advisory": "Openapigenerator 4.2.1 updates its Maven dependency 'jackson-databind' to v2.9.10.1 to include security fixes.",
            "cve": "CVE-2019-16942",
            "id": "pyup.io-45637",
            "more_info_path": "/vulnerabilities/CVE-2019-16942/45637",
            "specs": [
                "<4.2.1"
            ],
            "v": "<4.2.1"
        },
        {
            "advisory": "Openapigenerator updates its Ruby dependency 'rake' to v13.0.1 to include a security fix.",
            "cve": "CVE-2020-8130",
            "id": "pyup.io-45638",
            "more_info_path": "/vulnerabilities/CVE-2020-8130/45638",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        }
    ],
    "openbb": [
        {
            "advisory": "Openbb 2.3.0 updates its dependency 'certifi' to v2022.12.7 to include a security fix.",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-53327",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/53327",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Openbb 2.3.0 updates its dependency 'future' to v0.18.3 to include a security fix.",
            "cve": "CVE-2022-40899",
            "id": "pyup.io-53330",
            "more_info_path": "/vulnerabilities/CVE-2022-40899/53330",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Openbb 2.3.0 updates its dependency 'gitpython' to v3.1.30 to include a security fix.",
            "cve": "CVE-2022-24439",
            "id": "pyup.io-53331",
            "more_info_path": "/vulnerabilities/CVE-2022-24439/53331",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Openbb 2.3.0 updates its dependency 'cryptography' to v39.0.0 to include security fixes.",
            "cve": "CVE-2022-3602",
            "id": "pyup.io-53329",
            "more_info_path": "/vulnerabilities/CVE-2022-3602/53329",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Openbb 2.3.0 updates its dependency 'cryptography' to v39.0.0 to include security fixes.",
            "cve": "CVE-2022-3786",
            "id": "pyup.io-53328",
            "more_info_path": "/vulnerabilities/CVE-2022-3786/53328",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Openbb 2.4.0 updates its NPM dependency 'eta' to v2.0.0 to include security fixes.",
            "cve": "CVE-2023-23630",
            "id": "pyup.io-53366",
            "more_info_path": "/vulnerabilities/CVE-2023-23630/53366",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Openbb 2.4.0 updates its NPM dependency 'eta' to v2.0.0 to include security fixes.",
            "cve": "CVE-2022-25967",
            "id": "pyup.io-53379",
            "more_info_path": "/vulnerabilities/CVE-2022-25967/53379",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Openbb version 4.2.0 updates its `aiohttp` dependency from `^3.9.0` to `^3.9.5` to address the security vulnerability identified as CVE-2024-27306. This update ensures enhanced security and stability by incorporating the necessary fixes from the newer version of the `aiohttp` library.",
            "cve": "CVE-2024-27306",
            "id": "pyup.io-71126",
            "more_info_path": "/vulnerabilities/CVE-2024-27306/71126",
            "specs": [
                "<4.2.0"
            ],
            "v": "<4.2.0"
        },
        {
            "advisory": "Openbb version 4.2.0 updates its `fastapi` dependency from `^0.104.1` to `^0.111.0` to address the security vulnerability identified as CVE-2024-24762. This update ensures the application remains secure by incorporating the necessary fixes from the newer version of the FastAPI framework.",
            "cve": "CVE-2024-24762",
            "id": "pyup.io-71141",
            "more_info_path": "/vulnerabilities/CVE-2024-24762/71141",
            "specs": [
                "<4.2.0"
            ],
            "v": "<4.2.0"
        }
    ],
    "openbrokerapi": [
        {
            "advisory": "Openbrokerapi 4.5.5 updates its dependency 'flask' to include a fix for a Use of Persistent Cookies Containing Sensitive Information vulnerability.\r\nhttps://github.com/eruvanos/openbrokerapi/commit/1057ef31830dc0a5dbcfaab2f3687a3097927f96",
            "cve": "CVE-2023-30861",
            "id": "pyup.io-60655",
            "more_info_path": "/vulnerabilities/CVE-2023-30861/60655",
            "specs": [
                "<4.5.5"
            ],
            "v": "<4.5.5"
        }
    ],
    "openc3": [
        {
            "advisory": "Affected versions of the openc3 package are vulnerable to Cross-site Scripting (XSS) due to the login functionality reflecting unsanitized user input. The login endpoint in the OpenC3 cosmos module embeds user-supplied input directly into a web response without proper output encoding or sanitization. An attacker can craft a malicious link or input that triggers script execution in a victim\u2019s browser during login, potentially facilitating session hijacking or other cross-site scripting impacts.",
            "cve": "CVE-2024-43795",
            "id": "pyup.io-78805",
            "more_info_path": "/vulnerabilities/CVE-2024-43795/78805",
            "specs": [
                "<5.19.0"
            ],
            "v": "<5.19.0"
        },
        {
            "advisory": "Affected versions of the OpenC3 COSMOS (openc3) package are vulnerable to Information Disclosure due to the clear-text storage of user passwords in web browser LocalStorage. The LocalStorage storage of `password` in the browser, without encryption or protection, exposes credentials when combined with Cross-Site Scripting (XSS) vulnerabilities in the OpenC3 COSMOS Open Source edition (not Enterprise Edition). An attacker able to exploit XSS (see GHSL-2024-128) can exfiltrate the stored plain-text `password` from LocalStorage, potentially allowing unauthorized access to user accounts and further compromise of connected embedded systems. \r\n# NOTE: This CVE only affects the Open Source edition, and not OpenC3 COSMOS Enterprise Edition.",
            "cve": "CVE-2024-47529",
            "id": "pyup.io-78783",
            "more_info_path": "/vulnerabilities/CVE-2024-47529/78783",
            "specs": [
                "<5.19.0"
            ],
            "v": "<5.19.0"
        },
        {
            "advisory": "Affected versions of the openc3 package are vulnerable to Path Traversal due to improper limitation of a pathname to a restricted directory via the `LocalMode` class's `open_local_file` method. The `ScreensController#show` endpoint in the openc3 package fails to properly validate or sanitize the file path, allowing directory traversal sequences to access arbitrary `.txt` files on the COSMOS web server. An attacker with valid authentication and sufficient permissions can exploit this by issuing requests that traverse out of the intended directory and download arbitrary text files, potentially disclosing sensitive information.  \r\n# NOTE: This CVE affects all OpenC3 COSMOS Editions",
            "cve": "CVE-2024-46977",
            "id": "pyup.io-78794",
            "more_info_path": "/vulnerabilities/CVE-2024-46977/78794",
            "specs": [
                "<5.19.0"
            ],
            "v": "<5.19.0"
        }
    ],
    "opencanary": [
        {
            "advisory": "Affected versions of the OpenCanary package are vulnerable to Improper Authorization due to execution of commands retrieved from a potentially writable configuration file. The daemon\u2019s startup logic in the OpenCanary module directly executes commands specified in its config file without verifying integrity or source authenticity. An attacker with write access to the unprivileged user-writable config file can insert malicious commands that will be executed with root privileges when the daemon starts, enabling privilege escalation and full control over the host system.",
            "cve": "CVE-2024-48911",
            "id": "pyup.io-78804",
            "more_info_path": "/vulnerabilities/CVE-2024-48911/78804",
            "specs": [
                "<0.9.5"
            ],
            "v": "<0.9.5"
        }
    ],
    "opencc": [
        {
            "advisory": "Open Chinese Convert (OpenCC) 1.0.5 allows attackers to cause a denial of service (segmentation fault) because BinaryDict::NewFromFile in BinaryDict.cpp may have out-of-bounds keyOffset and valueOffset values via a crafted .ocd file.",
            "cve": "CVE-2018-16982",
            "id": "pyup.io-54012",
            "more_info_path": "/vulnerabilities/CVE-2018-16982/54012",
            "specs": [
                ">=0,<1.1.2"
            ],
            "v": ">=0,<1.1.2"
        }
    ],
    "opencl-rt": [
        {
            "advisory": "Opencl-rt 2022.1 includes a fix for CVE-2022-26032: Uncontrolled search path element in the Intel(R) Distribution for Python programming language before version 2022.1 for Intel(R) oneAPI Toolkits may allow an authenticated user to potentially enable escalation of privilege via local access.\r\nhttps://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00674.html",
            "cve": "CVE-2022-26032",
            "id": "pyup.io-53362",
            "more_info_path": "/vulnerabilities/CVE-2022-26032/53362",
            "specs": [
                "<2022.1"
            ],
            "v": "<2022.1"
        }
    ],
    "opencv-contrib-python": [
        {
            "advisory": "OpenCV 3.0.0 has a double free issue that allows attackers to execute arbitrary code. This issue was fixed in OpenCV version 3.3.1 (corresponding to OpenCV-Python and and OpenCV-Contrib-Python 3.3.1.11).",
            "cve": "CVE-2016-1516",
            "id": "pyup.io-54365",
            "more_info_path": "/vulnerabilities/CVE-2016-1516/54365",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "In modules/imgcodecs/src/grfmt_pxm.cpp, the length of buffer AutoBuffer _src is small than expected, which will cause copy buffer overflow later. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.",
            "cve": "CVE-2017-12862",
            "id": "pyup.io-53933",
            "more_info_path": "/vulnerabilities/CVE-2017-12862/53933",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "In opencv/modules/imgcodecs/src/grfmt_pxm.cpp, function PxMDecoder::readData has an integer overflow when calculate src_pitch. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.",
            "cve": "CVE-2017-12863",
            "id": "pyup.io-53931",
            "more_info_path": "/vulnerabilities/CVE-2017-12863/53931",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "In opencv/modules/imgcodecs/src/grfmt_pxm.cpp, function ReadNumber did not checkout the input length, which lead to integer overflow. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding with OpenCV-Python version 3.3.0.9) and earlier.",
            "cve": "CVE-2017-12864",
            "id": "pyup.io-54363",
            "more_info_path": "/vulnerabilities/CVE-2017-12864/54363",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "In opencv/modules/imgcodecs/src/utils.cpp, functions FillUniColor and FillUniGray do not check the input length, which can lead to integer overflow. If the image is from remote, may lead to remote code execution or denial of service. This affects Opencv 3.3 (corresponding with OpenCV-Python 3.3.0.9) and earlier.",
            "cve": "CVE-2017-1000450",
            "id": "pyup.io-54361",
            "more_info_path": "/vulnerabilities/CVE-2017-1000450/54361",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "OpenCV (Open Source Computer Vision Library) 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds write error in the function FillColorRow1 in utils.cpp when reading an image file by using cv::imread. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-12597.",
            "cve": "CVE-2017-14136",
            "id": "pyup.io-53935",
            "more_info_path": "/vulnerabilities/CVE-2017-14136/53935",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "OpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an out-of-bounds write error in the FillColorRow8 function in utils.cpp when reading an image file by using cv::imread.",
            "cve": "CVE-2017-12605",
            "id": "pyup.io-54670",
            "more_info_path": "/vulnerabilities/CVE-2017-12605/54670",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "OpenCV 3.3.1 (corresponding with opencv-python and opencv-contrib-python 3.3.1.11) has a Buffer Overflow in the cv::PxMDecoder::readData function in grfmt_pxm.cpp, because an incorrect size value is used.",
            "cve": "CVE-2017-17760",
            "id": "pyup.io-53947",
            "more_info_path": "/vulnerabilities/CVE-2017-17760/53947",
            "specs": [
                ">=0,<3.4.0.12"
            ],
            "v": ">=0,<3.4.0.12"
        },
        {
            "advisory": "In OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer overflow happens in cv::Jpeg2KDecoder::readComponent8u in modules/imgcodecs/src/grfmt_jpeg2000.cpp when parsing a crafted image file.",
            "cve": "CVE-2018-5268",
            "id": "pyup.io-54027",
            "more_info_path": "/vulnerabilities/CVE-2018-5268/54027",
            "specs": [
                ">=0,<3.4.1.15"
            ],
            "v": ">=0,<3.4.1.15"
        },
        {
            "advisory": "In OpenCV 3.3.1 (corresponds with OpenCV-Python 3.3.1.11), an assertion failure happens in cv::RBaseStream::setPos in modules/imgcodecs/src/bitstrm.cpp because of an incorrect integer cast.",
            "cve": "CVE-2018-5269",
            "id": "pyup.io-54359",
            "more_info_path": "/vulnerabilities/CVE-2018-5269/54359",
            "specs": [
                ">=0,<3.4.1.15"
            ],
            "v": ">=0,<3.4.1.15"
        },
        {
            "advisory": "In OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer over-read exists in the function cv::HdrDecoder::checkSignature in modules/imgcodecs/src/grfmt_hdr.cpp.",
            "cve": "CVE-2017-18009",
            "id": "pyup.io-53952",
            "more_info_path": "/vulnerabilities/CVE-2017-18009/53952",
            "specs": [
                ">=0,<3.4.1.15"
            ],
            "v": ">=0,<3.4.1.15"
        },
        {
            "advisory": "An issue was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.1.26). There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp.",
            "cve": "CVE-2019-14493",
            "id": "pyup.io-54151",
            "more_info_path": "/vulnerabilities/CVE-2019-14493/54151",
            "specs": [
                ">=0,<4.1.1.26"
            ],
            "v": ">=0,<4.1.1.26"
        },
        {
            "advisory": "Opencv-contrib-python 4.8.1.78 updates its bundled dependency 'libwebp' to include a fix for a high risk vulnerability. Only mac OS X wheels on PyPI were affected.\r\nhttps://github.com/opencv/opencv-python/releases/tag/78",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62310",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62310",
            "specs": [
                ">=3.4.9.31,<4.8.1.78"
            ],
            "v": ">=3.4.9.31,<4.8.1.78"
        },
        {
            "advisory": "The OpenCV wechat_qrcode module, versions up to 4.7.0, contains a critical vulnerability affecting the DecodedBitStreamParser::decodeByteSegment function in the qrcode/decoder/decoded_bit_stream_parser.cpp file.",
            "cve": "CVE-2023-2617",
            "id": "pyup.io-63406",
            "more_info_path": "/vulnerabilities/CVE-2023-2617/63406",
            "specs": [
                ">=4.5.2,<4.8.1.78"
            ],
            "v": ">=4.5.2,<4.8.1.78"
        }
    ],
    "opencv-contrib-python-headless": [
        {
            "advisory": "An issue was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.1.26). There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp.",
            "cve": "CVE-2019-14493",
            "id": "pyup.io-54152",
            "more_info_path": "/vulnerabilities/CVE-2019-14493/54152",
            "specs": [
                ">=0,<4.1.1.26"
            ],
            "v": ">=0,<4.1.1.26"
        },
        {
            "advisory": "Opencv-contrib-python-headless 4.8.1.78 updates its bundled dependency 'libwebp' to include a fix for a high risk vulnerability. Only mac OS X wheels on PyPI were affected.\r\nhttps://github.com/opencv/opencv-python/releases/tag/78",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62311",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62311",
            "specs": [
                ">=3.4.9.31,<4.8.1.78"
            ],
            "v": ">=3.4.9.31,<4.8.1.78"
        }
    ],
    "opencv-python": [
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for CVE-2017-12600: OpenCV through 3.3 has a denial of service (CPU consumption) issue, as demonstrated by the 11-opencv-dos-cpu-exhaust test case.",
            "cve": "CVE-2017-12600",
            "id": "pyup.io-50490",
            "more_info_path": "/vulnerabilities/CVE-2017-12600/50490",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for CVE-2017-12598: OpenCV through 3.3 has an out-of-bounds read error in the cv::RBaseStream::readBlock function in modules/imgcodecs/src/bitstrm.cpp when reading an image file by using cv::imread, as demonstrated by the 8-opencv-invalid-read-fread test case.",
            "cve": "CVE-2017-12598",
            "id": "pyup.io-50494",
            "more_info_path": "/vulnerabilities/CVE-2017-12598/50494",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for  CVE-2017-12604: OpenCV through 3.3 has an out-of-bounds write error in the FillUniColor function in utils.cpp when reading an image file by using cv::imread.",
            "cve": "CVE-2017-12604",
            "id": "pyup.io-50488",
            "more_info_path": "/vulnerabilities/CVE-2017-12604/50488",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for CVE-2016-1517: OpenCV 3.0.0 allows remote attackers to cause a denial of service (segfault) via vectors involving corrupt chunks.",
            "cve": "CVE-2016-1517",
            "id": "pyup.io-50489",
            "more_info_path": "/vulnerabilities/CVE-2016-1517/50489",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for CVE-2017-12602: OpenCV through 3.3 has a denial of service (memory consumption) issue, as demonstrated by the 10-opencv-dos-memory-exhaust test case.",
            "cve": "CVE-2017-12602",
            "id": "pyup.io-50487",
            "more_info_path": "/vulnerabilities/CVE-2017-12602/50487",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for CVE-2017-12603: OpenCV through 3.3 has an invalid write in the cv::RLByteStream::getBytes function in modules/imgcodecs/src/bitstrm.cpp when reading an image file by using cv::imread, as demonstrated by the 2-opencv-heapoverflow-fseek test case.",
            "cve": "CVE-2017-12603",
            "id": "pyup.io-50492",
            "more_info_path": "/vulnerabilities/CVE-2017-12603/50492",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for CVE-2017-12597: OpenCV through 3.3 has an out-of-bounds write error in the function FillColorRow1 in utils.cpp when reading an image file by using cv::imread.",
            "cve": "CVE-2017-12597",
            "id": "pyup.io-50493",
            "more_info_path": "/vulnerabilities/CVE-2017-12597/50493",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for CVE-2017-12601: OpenCV through 3.3 has a buffer overflow in the cv::BmpDecoder::readData function in modules/imgcodecs/src/grfmt_bmp.cpp when reading an image file by using cv::imread, as demonstrated by the 4-buf-overflow-readData-memcpy test case.",
            "cve": "CVE-2017-12601",
            "id": "pyup.io-50491",
            "more_info_path": "/vulnerabilities/CVE-2017-12601/50491",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for CVE-2017-12599: OpenCV through 3.3 has an out-of-bounds read error in the function icvCvt_BGRA2BGR_8u_C4C3R when reading an image file by using cv::imread.",
            "cve": "CVE-2017-12599",
            "id": "pyup.io-50495",
            "more_info_path": "/vulnerabilities/CVE-2017-12599/50495",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.3.1.11 includes a fix for CVE-2017-12606: OpenCV through 3.3 has an out-of-bounds write error in the function FillColorRow4 in utils.cpp when reading an image file by using cv::imread.",
            "cve": "CVE-2017-12606",
            "id": "pyup.io-50496",
            "more_info_path": "/vulnerabilities/CVE-2017-12606/50496",
            "specs": [
                "<3.3.1.11"
            ],
            "v": "<3.3.1.11"
        },
        {
            "advisory": "Opencv-python 3.4.18 and 4.6.0 pin its dependency 'libpng' to v1.6.37 to include a security fix.",
            "cve": "CVE-2019-7317",
            "id": "pyup.io-49394",
            "more_info_path": "/vulnerabilities/CVE-2019-7317/49394",
            "specs": [
                "<3.4.18",
                ">=4.0.0,<4.6.0"
            ],
            "v": "<3.4.18,>=4.0.0,<4.6.0"
        },
        {
            "advisory": "Opencv-python 3.4.18 and 4.6.0 update its dependency 'openssl' to v1_1_1o to include security fixes.",
            "cve": "CVE-2022-0778",
            "id": "pyup.io-49334",
            "more_info_path": "/vulnerabilities/CVE-2022-0778/49334",
            "specs": [
                "<3.4.18",
                ">=4.0.0,<4.6.0"
            ],
            "v": "<3.4.18,>=4.0.0,<4.6.0"
        },
        {
            "advisory": "Opencv-python 3.4.18 and 4.6.0 pin its dependency 'freetype' to v2.12.1 to include a security fix.",
            "cve": "CVE-2022-27406",
            "id": "pyup.io-49395",
            "more_info_path": "/vulnerabilities/CVE-2022-27406/49395",
            "specs": [
                "<3.4.18",
                ">=4.0.0,<4.6.0"
            ],
            "v": "<3.4.18,>=4.0.0,<4.6.0"
        },
        {
            "advisory": "Opencv-python 3.4.18 and 4.6.0 update its dependency 'openssl' to v1_1_1o to include security fixes.",
            "cve": "CVE-2022-1292",
            "id": "pyup.io-49393",
            "more_info_path": "/vulnerabilities/CVE-2022-1292/49393",
            "specs": [
                "<3.4.18",
                ">=4.0.0,<4.6.0"
            ],
            "v": "<3.4.18,>=4.0.0,<4.6.0"
        },
        {
            "advisory": "Opencv-python 4.1.0.25 includes a fix for CVE-2019-19624: An out-of-bounds read was discovered in OpenCV before 4.1.1. Specifically, variable coarsest_scale is assumed to be greater than or equal to finest_scale within the calc()/ocl_calc() functions in dis_flow.cpp. However, this is not true when dealing with small images, leading to an out-of-bounds read of the heap-allocated arrays Ux and Uy.",
            "cve": "CVE-2019-19624",
            "id": "pyup.io-50497",
            "more_info_path": "/vulnerabilities/CVE-2019-19624/50497",
            "specs": [
                "<4.1.0.25"
            ],
            "v": "<4.1.0.25"
        },
        {
            "advisory": "Opencv-python 4.1.1.26 includes a fix for CVE-2019-15939: An issue was discovered in OpenCV 4.1.0. There is a divide-by-zero error in cv::HOGDescriptor::getDescriptorSize in modules/objdetect/src/hog.cpp.",
            "cve": "CVE-2019-15939",
            "id": "pyup.io-50485",
            "more_info_path": "/vulnerabilities/CVE-2019-15939/50485",
            "specs": [
                "<4.1.1.26"
            ],
            "v": "<4.1.1.26"
        },
        {
            "advisory": "Opencv-python 4.1.1.26 includes a fix for CVE-2019-9423: In opencv calls that use libpng, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges required. User interaction is not required for exploitation.",
            "cve": "CVE-2019-9423",
            "id": "pyup.io-50486",
            "more_info_path": "/vulnerabilities/CVE-2019-9423/50486",
            "specs": [
                "<4.1.1.26"
            ],
            "v": "<4.1.1.26"
        },
        {
            "advisory": "Opencv-python 4.1.2.30 includes a fix for  CVE-2019-16249: OpenCV 4.1.1 has an out-of-bounds read in hal_baseline::v_load in core/hal/intrin_sse.hpp when called from computeSSDMeanNorm in modules/video/src/dis_flow.cpp.",
            "cve": "CVE-2019-16249",
            "id": "pyup.io-50498",
            "more_info_path": "/vulnerabilities/CVE-2019-16249/50498",
            "specs": [
                "<4.1.2.30"
            ],
            "v": "<4.1.2.30"
        },
        {
            "advisory": "Opencv-python 4.7.0 updates its dependency 'OpenSSL' to v1.1.1s to include security fixes.",
            "cve": "CVE-2022-2068",
            "id": "pyup.io-52660",
            "more_info_path": "/vulnerabilities/CVE-2022-2068/52660",
            "specs": [
                "<4.7.0"
            ],
            "v": "<4.7.0"
        },
        {
            "advisory": "Opencv-python 4.7.0 updates its C dependency 'zlib' to v1.2.13 to include a security fix.",
            "cve": "CVE-2022-37434",
            "id": "pyup.io-52595",
            "more_info_path": "/vulnerabilities/CVE-2022-37434/52595",
            "specs": [
                "<4.7.0"
            ],
            "v": "<4.7.0"
        },
        {
            "advisory": "OpenCV's wechat_qrcode module, specifically versions up to 4.7.0, has a significant vulnerability affecting the DecodedBitStreamParser::decodeHanziSegment function within the qrcode/decoder/decoded_bit_stream_parser.cpp file. This vulnerability can cause a memory leak. The potential attack can be executed remotely. To rectify this issue, it's advisable to apply a patch named 2b62ff6181163eea029ed1cab11363b4996e9cd6.",
            "cve": "CVE-2023-2618",
            "id": "pyup.io-63408",
            "more_info_path": "/vulnerabilities/CVE-2023-2618/63408",
            "specs": [
                "<4.7.0"
            ],
            "v": "<4.7.0"
        },
        {
            "advisory": "Opencv-python 4.7.0 updates its C dependency 'FFmpeg' to v5.1.2 to include a security fix.",
            "cve": "CVE-2022-1475",
            "id": "pyup.io-52659",
            "more_info_path": "/vulnerabilities/CVE-2022-1475/52659",
            "specs": [
                "<4.7.0"
            ],
            "v": "<4.7.0"
        },
        {
            "advisory": "Opencv-python 4.7.0 updates its dependency 'OpenSSL' to v1.1.1s to include security fixes.",
            "cve": "CVE-2022-2097",
            "id": "pyup.io-52661",
            "more_info_path": "/vulnerabilities/CVE-2022-2097/52661",
            "specs": [
                "<4.7.0"
            ],
            "v": "<4.7.0"
        },
        {
            "advisory": "In modules/imgcodecs/src/grfmt_pxm.cpp, the length of buffer AutoBuffer _src is small than expected, which will cause copy buffer overflow later. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.",
            "cve": "CVE-2017-12862",
            "id": "pyup.io-53932",
            "more_info_path": "/vulnerabilities/CVE-2017-12862/53932",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "OpenCV (Open Source Computer Vision Library) 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds write error in the function FillColorRow1 in utils.cpp when reading an image file by using cv::imread. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-12597.",
            "cve": "CVE-2017-14136",
            "id": "pyup.io-53934",
            "more_info_path": "/vulnerabilities/CVE-2017-14136/53934",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "OpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an out-of-bounds write error in the FillColorRow8 function in utils.cpp when reading an image file by using cv::imread.",
            "cve": "CVE-2017-12605",
            "id": "pyup.io-54669",
            "more_info_path": "/vulnerabilities/CVE-2017-12605/54669",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "In opencv/modules/imgcodecs/src/grfmt_pxm.cpp, function ReadNumber did not checkout the input length, which lead to integer overflow. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding with OpenCV-Python version 3.3.0.9) and earlier.",
            "cve": "CVE-2017-12864",
            "id": "pyup.io-54362",
            "more_info_path": "/vulnerabilities/CVE-2017-12864/54362",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "In opencv/modules/imgcodecs/src/utils.cpp, functions FillUniColor and FillUniGray do not check the input length, which can lead to integer overflow. If the image is from remote, may lead to remote code execution or denial of service. This affects Opencv 3.3 (corresponding with OpenCV-Python 3.3.0.9) and earlier.",
            "cve": "CVE-2017-1000450",
            "id": "pyup.io-54360",
            "more_info_path": "/vulnerabilities/CVE-2017-1000450/54360",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "OpenCV 3.0.0 has a double free issue that allows attackers to execute arbitrary code. This issue was fixed in OpenCV version 3.3.1 (corresponding to OpenCV-Python and and OpenCV-Contrib-Python 3.3.1.11).",
            "cve": "CVE-2016-1516",
            "id": "pyup.io-54364",
            "more_info_path": "/vulnerabilities/CVE-2016-1516/54364",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "In opencv/modules/imgcodecs/src/grfmt_pxm.cpp, function PxMDecoder::readData has an integer overflow when calculate src_pitch. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.",
            "cve": "CVE-2017-12863",
            "id": "pyup.io-53930",
            "more_info_path": "/vulnerabilities/CVE-2017-12863/53930",
            "specs": [
                ">=0,<3.3.1.11"
            ],
            "v": ">=0,<3.3.1.11"
        },
        {
            "advisory": "OpenCV 3.3.1 (corresponding with opencv-python and opencv-contrib-python 3.3.1.11) has a Buffer Overflow in the cv::PxMDecoder::readData function in grfmt_pxm.cpp, because an incorrect size value is used.",
            "cve": "CVE-2017-17760",
            "id": "pyup.io-53946",
            "more_info_path": "/vulnerabilities/CVE-2017-17760/53946",
            "specs": [
                ">=0,<3.4.0.12"
            ],
            "v": ">=0,<3.4.0.12"
        },
        {
            "advisory": "In OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer over-read exists in the function cv::HdrDecoder::checkSignature in modules/imgcodecs/src/grfmt_hdr.cpp.",
            "cve": "CVE-2017-18009",
            "id": "pyup.io-53951",
            "more_info_path": "/vulnerabilities/CVE-2017-18009/53951",
            "specs": [
                ">=0,<3.4.1.15"
            ],
            "v": ">=0,<3.4.1.15"
        },
        {
            "advisory": "In OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer overflow happens in cv::Jpeg2KDecoder::readComponent8u in modules/imgcodecs/src/grfmt_jpeg2000.cpp when parsing a crafted image file.",
            "cve": "CVE-2018-5268",
            "id": "pyup.io-54026",
            "more_info_path": "/vulnerabilities/CVE-2018-5268/54026",
            "specs": [
                ">=0,<3.4.1.15"
            ],
            "v": ">=0,<3.4.1.15"
        },
        {
            "advisory": "In OpenCV 3.3.1 (corresponds with OpenCV-Python 3.3.1.11), an assertion failure happens in cv::RBaseStream::setPos in modules/imgcodecs/src/bitstrm.cpp because of an incorrect integer cast.",
            "cve": "CVE-2018-5269",
            "id": "pyup.io-54358",
            "more_info_path": "/vulnerabilities/CVE-2018-5269/54358",
            "specs": [
                ">=0,<3.4.1.15"
            ],
            "v": ">=0,<3.4.1.15"
        },
        {
            "advisory": "An issue was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.1.26). There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp.",
            "cve": "CVE-2019-14493",
            "id": "pyup.io-54149",
            "more_info_path": "/vulnerabilities/CVE-2019-14493/54149",
            "specs": [
                ">=0,<4.1.1.26"
            ],
            "v": ">=0,<4.1.1.26"
        },
        {
            "advisory": "Opencv-python 4.8.1.78 updates its bundled dependency 'libwebp' to include a fix for a high risk vulnerability. Only mac OS X wheels on PyPI were affected.\r\nhttps://github.com/opencv/opencv-python/releases/tag/78",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62308",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62308",
            "specs": [
                ">=3.4.9.31,<4.8.1.78"
            ],
            "v": ">=3.4.9.31,<4.8.1.78"
        },
        {
            "advisory": "Opencv-python 4.1.1.26 and 3.4.7.28 include a fix for CVE-2019-14491: An issue was discovered in OpenCV before 3.4.7 and 4.x before 4.1.1. There is an out of bounds read in the function cv::predictOrdered in modules/objdetect/src/cascadedetect.hpp, which leads to denial of service.",
            "cve": "CVE-2019-14491",
            "id": "pyup.io-50501",
            "more_info_path": "/vulnerabilities/CVE-2019-14491/50501",
            "specs": [
                ">=4.0.0.21,<4.1.1.26",
                "<3.4.7.28"
            ],
            "v": ">=4.0.0.21,<4.1.1.26,<3.4.7.28"
        },
        {
            "advisory": "Opencv-python 4.1.1.26 and 3.4.7.28 include a fix for CVE-2019-14492: An issue was discovered in OpenCV before 3.4.7 and 4.x before 4.1.1. There is an out of bounds read/write in the function HaarEvaluator::OptFeature::calc in modules/objdetect/src/cascadedetect.hpp, which leads to denial of service.",
            "cve": "CVE-2019-14492",
            "id": "pyup.io-50502",
            "more_info_path": "/vulnerabilities/CVE-2019-14492/50502",
            "specs": [
                ">=4.0.0.21,<4.1.1.26",
                "<3.4.7.28"
            ],
            "v": ">=4.0.0.21,<4.1.1.26,<3.4.7.28"
        },
        {
            "advisory": "Opencv-python 4.2.0.32 includes a fix for CVE-2019-5063: An exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV 4.1.0. A specially crafted XML file can cause a buffer overflow, resulting in multiple heap corruptions and potential code execution. An attacker can provide a specially crafted file to trigger this vulnerability.",
            "cve": "CVE-2019-5063",
            "id": "pyup.io-50500",
            "more_info_path": "/vulnerabilities/CVE-2019-5063/50500",
            "specs": [
                ">=4.0.0.21,<4.2.0.32"
            ],
            "v": ">=4.0.0.21,<4.2.0.32"
        },
        {
            "advisory": "Opencv-python 4.2.0.32 includes a fix for  CVE-2019-5064: An exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV, before version 4.2.0. A specially crafted JSON file can cause a buffer overflow, resulting in multiple heap corruptions and potentially code execution. An attacker can provide a specially crafted file to trigger this vulnerability.",
            "cve": "CVE-2019-5064",
            "id": "pyup.io-50499",
            "more_info_path": "/vulnerabilities/CVE-2019-5064/50499",
            "specs": [
                ">=4.0.0.21,<4.2.0.32"
            ],
            "v": ">=4.0.0.21,<4.2.0.32"
        }
    ],
    "opencv-python-headless": [
        {
            "advisory": "An issue was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.1.26). There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp.",
            "cve": "CVE-2019-14493",
            "id": "pyup.io-54150",
            "more_info_path": "/vulnerabilities/CVE-2019-14493/54150",
            "specs": [
                ">=0,<4.1.1.26"
            ],
            "v": ">=0,<4.1.1.26"
        },
        {
            "advisory": "Opencv-python-headless 4.8.1.78 updates its bundled dependency 'libwebp' to include a fix for a high risk vulnerability. Only mac OS X wheels on PyPI were affected.\r\nhttps://github.com/opencv/opencv-python/releases/tag/78",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62309",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62309",
            "specs": [
                ">=3.4.9.31,<4.8.1.78"
            ],
            "v": ">=3.4.9.31,<4.8.1.78"
        }
    ],
    "opendaq": [
        {
            "advisory": "Affected versions of the opendaq component were potentially vulnerable to improper authorization. An attacker could potentially modify the internal status dictionary, leading to unauthorized status changes. The issue existed in the `StatusContainerBase::getStatuses` function.",
            "cve": "PVE-2025-76682",
            "id": "pyup.io-76682",
            "more_info_path": "/vulnerabilities/PVE-2025-76682/76682",
            "specs": [
                "<3.19.0rc"
            ],
            "v": "<3.19.0rc"
        }
    ],
    "opendiamond": [
        {
            "advisory": "Opendiamond throughout 10.1.1 allows absolute path traversal because the Flask send_file function is used unsafely. See CVE-2022-31506.",
            "cve": "CVE-2022-31506",
            "id": "pyup.io-50018",
            "more_info_path": "/vulnerabilities/CVE-2022-31506/50018",
            "specs": [
                "<=10.1.1"
            ],
            "v": "<=10.1.1"
        }
    ],
    "opendp": [
        {
            "advisory": "Opendp 0.5.0 replaces the underlying implementation of 'make_base_laplace' and 'make_base_gaussian' to address precision-based attacks.\r\nhttps://github.com/opendp/opendp/commit/fb03d511f530c23e5fb48cd50df331d142dbef52\r\nhttps://tpdp.journalprivacyconfidentiality.org/2022/papers/HaneyDHSH22.pdf",
            "cve": "PVE-2022-50753",
            "id": "pyup.io-50753",
            "more_info_path": "/vulnerabilities/PVE-2022-50753/50753",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        },
        {
            "advisory": "Opendp 0.5.0 hardens samplers to handle some privacy violation cases.\r\nhttps://github.com/opendp/opendp/pull/481",
            "cve": "PVE-2022-50829",
            "id": "pyup.io-50829",
            "more_info_path": "/vulnerabilities/PVE-2022-50829/50829",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        }
    ],
    "opendp-smartnoise-core": [
        {
            "advisory": "Opendp-smartnoise-core 0.1.1 enables 'protect_floating_point' by default, to protect better real-valued queries.",
            "cve": "PVE-2022-44443",
            "id": "pyup.io-44443",
            "more_info_path": "/vulnerabilities/PVE-2022-44443/44443",
            "specs": [
                "<0.1.1"
            ],
            "v": "<0.1.1"
        }
    ],
    "openedx-django-wiki": [
        {
            "advisory": "Openedx-django-wiki 0.0.21 includes a fix for a XSS vulnerability.\r\nhttps://github.com/openedx/django-wiki/commit/0904b1453e19580210049dbfd96dd503fb39831e",
            "cve": "PVE-2023-61374",
            "id": "pyup.io-61374",
            "more_info_path": "/vulnerabilities/PVE-2023-61374/61374",
            "specs": [
                "<0.0.21"
            ],
            "v": "<0.0.21"
        }
    ],
    "openexr": [
        {
            "advisory": "OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In version 3.3.2, when reading a deep scanline image with a large sample count in reduceMemory mode, it is possible to crash a target application with a NULL pointer dereference in a write operation. This is fixed in version 3.3.3.",
            "cve": "CVE-2025-48073",
            "id": "pyup.io-78658",
            "more_info_path": "/vulnerabilities/CVE-2025-48073/78658",
            "specs": [
                "==3.3.2"
            ],
            "v": "==3.3.2"
        },
        {
            "advisory": "OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. Version 3.3.2 is vulnerable to a heap-based buffer overflow during a read operation due to bad pointer math when decompressing DWAA-packed scan-line EXR files with a maliciously forged chunk. This is fixed in version 3.3.3.",
            "cve": "CVE-2025-48072",
            "id": "pyup.io-78659",
            "more_info_path": "/vulnerabilities/CVE-2025-48072/78659",
            "specs": [
                "==3.3.2"
            ],
            "v": "==3.3.2"
        },
        {
            "advisory": "Affected versions of the OpenEXR package are vulnerable to Denial of Service (DoS) due to excessive memory allocations. The `readScanline()` function in `ImfCheckFile.cpp` and the `EnvmapImage::resize()` function fail to validate the dataWindow coordinates from the EXR file header, leading to unbounded loops and huge memory allocations. The vulnerability was fixed by adding validation checks to prevent large allocations when dataWindow dimensions exceed reasonable limits.",
            "cve": "CVE-2025-48074",
            "id": "pyup.io-78657",
            "more_info_path": "/vulnerabilities/CVE-2025-48074/78657",
            "specs": [
                "==3.3.2"
            ],
            "v": "==3.3.2"
        },
        {
            "advisory": "OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In versions 3.3.2 through 3.3.0, there is a heap-based buffer overflow during a write operation when decompressing ZIPS-packed deep-scan-line EXR files with a maliciously forged chunk header. This is fixed in version 3.3.3.",
            "cve": "CVE-2025-48071",
            "id": "pyup.io-78660",
            "more_info_path": "/vulnerabilities/CVE-2025-48071/78660",
            "specs": [
                ">=3.3.0,<3.3.3"
            ],
            "v": ">=3.3.0,<3.3.3"
        }
    ],
    "openfeature-sdk": [
        {
            "advisory": "Openfeature-sdk version 0.0.2 updates its wheel dependency on the python-sdk from version 0.37.1 to 0.38.0, due to security enhancements.\r\nhttps://github.com/open-feature/python-sdk/pull/37/commits/0e5f5854ec7f9db6363515c705a2e21472f16352",
            "cve": "PVE-2024-64977",
            "id": "pyup.io-64977",
            "more_info_path": "/vulnerabilities/PVE-2024-64977/64977",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        }
    ],
    "openhands": [
        {
            "advisory": "Affected versions of the OpenHands package are vulnerable to Improper Input Validation due to the acceptance of non-HTTPS redirect URIs. The redirect handling logic failed to enforce HTTPS in redirect parameters, allowing insecure HTTP endpoints to be registered and used during authentication or authorization flows.",
            "cve": "PVE-2025-80329",
            "id": "pyup.io-80329",
            "more_info_path": "/vulnerabilities/PVE-2025-80329/80329",
            "specs": [
                "<0.43.0"
            ],
            "v": "<0.43.0"
        }
    ],
    "openimis-be-api-fhir-r4": [
        {
            "advisory": "Openimis-be-api-fhir-r4 version 23.10 has upgraded its aiohttp library from version 3.8.1 to 3.8.5 to address security vulnerabilities and ensure compatibility as noted in CVE-2023-47627.",
            "cve": "CVE-2023-47627",
            "id": "pyup.io-70569",
            "more_info_path": "/vulnerabilities/CVE-2023-47627/70569",
            "specs": [
                "<23.10"
            ],
            "v": "<23.10"
        }
    ],
    "openmdao": [
        {
            "advisory": "OpenMDAO pins `jinja2` to version `>=3.1.4` to address security concerns, including CVE-2024-34064.",
            "cve": "CVE-2024-34064",
            "id": "pyup.io-72270",
            "more_info_path": "/vulnerabilities/CVE-2024-34064/72270",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        },
        {
            "advisory": "OpenMDAO pins `tqdm` to version `>=4.66.3` to address security concerns, including CVE-2024-34062.",
            "cve": "CVE-2024-34062",
            "id": "pyup.io-72279",
            "more_info_path": "/vulnerabilities/CVE-2024-34062/72279",
            "specs": [
                "<3.33.0"
            ],
            "v": "<3.33.0"
        }
    ],
    "openpyxl": [
        {
            "advisory": "Openpyxl 2.4.1 resolves external entities by default, which allows remote attackers to conduct XXE attacks via a crafted .xlsx document.",
            "cve": "CVE-2017-5992",
            "id": "pyup.io-53962",
            "more_info_path": "/vulnerabilities/CVE-2017-5992/53962",
            "specs": [
                ">=0,<2.4.1"
            ],
            "v": ">=0,<2.4.1"
        }
    ],
    "openquake-engine": [
        {
            "advisory": "Openquake.engine 3.14.0 updates its dependency 'django' to v3.2.12 to include security fixes.",
            "cve": "CVE-2021-45115",
            "id": "pyup.io-48169",
            "more_info_path": "/vulnerabilities/CVE-2021-45115/48169",
            "specs": [
                "<3.14.0"
            ],
            "v": "<3.14.0"
        },
        {
            "advisory": "Openquake.engine 3.14.0 updates its dependency 'django' to v3.2.12 to include security fixes.",
            "cve": "CVE-2021-44420",
            "id": "pyup.io-48170",
            "more_info_path": "/vulnerabilities/CVE-2021-44420/48170",
            "specs": [
                "<3.14.0"
            ],
            "v": "<3.14.0"
        },
        {
            "advisory": "Openquake.engine 3.14.0 updates its dependency 'django' to v3.2.12 to include security fixes.",
            "cve": "CVE-2021-45116",
            "id": "pyup.io-48168",
            "more_info_path": "/vulnerabilities/CVE-2021-45116/48168",
            "specs": [
                "<3.14.0"
            ],
            "v": "<3.14.0"
        },
        {
            "advisory": "Openquake.engine 3.14.0 updates its dependency 'django' to v3.2.12 to include security fixes.",
            "cve": "CVE-2021-45452",
            "id": "pyup.io-48167",
            "more_info_path": "/vulnerabilities/CVE-2021-45452/48167",
            "specs": [
                "<3.14.0"
            ],
            "v": "<3.14.0"
        },
        {
            "advisory": "Openquake.engine 3.14.0 updates its dependency 'django' to v3.2.12 to include security fixes.",
            "cve": "CVE-2022-23833",
            "id": "pyup.io-48166",
            "more_info_path": "/vulnerabilities/CVE-2022-23833/48166",
            "specs": [
                "<3.14.0"
            ],
            "v": "<3.14.0"
        },
        {
            "advisory": "Openquake.engine 3.14.0 updates its dependency 'django' to v3.2.12 to include security fixes.",
            "cve": "CVE-2022-22818",
            "id": "pyup.io-47097",
            "more_info_path": "/vulnerabilities/CVE-2022-22818/47097",
            "specs": [
                "<3.14.0"
            ],
            "v": "<3.14.0"
        }
    ],
    "opensearch-py": [
        {
            "advisory": "Opensearch-py 2.3.0 updates its dependency 'certifi' to version '2022.12.07' to include a fix for a vulnerability.\r\nhttps://github.com/opensearch-project/opensearch-py/pull/295",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-60040",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/60040",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        }
    ],
    "opensearch-py-ml": [
        {
            "advisory": "Opensearch-py-ml 1.0.0 requires 'torch>=1.13.0' to include a security fix.",
            "cve": "CVE-2022-45907",
            "id": "pyup.io-53135",
            "more_info_path": "/vulnerabilities/CVE-2022-45907/53135",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "openslides": [
        {
            "advisory": "Openslides 2.1 fixes an issue in which comments were shown for unprivileged users.\r\nhttps://github.com/OpenSlides/OpenSlides/pull/2872",
            "cve": "PVE-2021-42733",
            "id": "pyup.io-42733",
            "more_info_path": "/vulnerabilities/PVE-2021-42733/42733",
            "specs": [
                "<2.1"
            ],
            "v": "<2.1"
        },
        {
            "advisory": "Openslides 2.1 validates HTML strings from CKEditor against XSS attacks.\r\nhttps://github.com/OpenSlides/OpenSlides/pull/2896",
            "cve": "PVE-2021-34681",
            "id": "pyup.io-34681",
            "more_info_path": "/vulnerabilities/PVE-2021-34681/34681",
            "specs": [
                "<2.1"
            ],
            "v": "<2.1"
        },
        {
            "advisory": "OpenSlides is a free, Web-based presentation and assembly system for managing and projecting agenda, motions, and elections of assemblies. OpenSlides version 3.2, due to unsufficient user input validation and escaping, it is vulnerable to persistant cross-site scripting (XSS). In the web applications users can enter rich text in various places, e.g. for personal notes or in motions. These fields can be used to store arbitrary JavaScript Code that will be executed when other users read the respective text. An attacker could utilize this vulnerability be used to manipulate votes of other users, hijack the moderators session or simply disturb the meeting. The vulnerability was introduced with 6eae497abeab234418dfbd9d299e831eff86ed45 on 16.04.2020, which is first included in the 3.2 release. It has been patched in version 3.3 ( in commit f3809fc8a97ee305d721662a75f788f9e9d21938, merged in master on 20.11.2020).",
            "cve": "CVE-2020-26280",
            "id": "pyup.io-54254",
            "more_info_path": "/vulnerabilities/CVE-2020-26280/54254",
            "specs": [
                ">=0,<3.3"
            ],
            "v": ">=0,<3.3"
        }
    ],
    "openssh-key-parser": [
        {
            "advisory": "Openssh-key-parser 0.0.6 includes a fix for CVE-2022-31124: Possible leak of key's raw field if declared length is incorrect.\r\nhttps://github.com/scottcwang/openssh_key_parser/security/advisories/GHSA-hm37-9xh2-q499",
            "cve": "CVE-2022-31124",
            "id": "pyup.io-49766",
            "more_info_path": "/vulnerabilities/CVE-2022-31124/49766",
            "specs": [
                "<0.0.6"
            ],
            "v": "<0.0.6"
        }
    ],
    "openssl-encrypt": [
        {
            "advisory": "Affected versions of the OpenSSL-encrypt package are vulnerable to a cryptographic weakness due to predictable salt derivation in multi-round KDF operations. In multi_hash_password() and generate_key(), each round\u2019s salt was computed deterministically as sha256(base_salt + round_number), making multi-round hashing/KDF salts precomputable from plaintext metadata.\r\nhttps://gitlab.rm-rf.ch/world/openssl_encrypt/-/commit/1bb285c40432af0051f5c5f451760863d9874f7f",
            "cve": "PVE-2026-84049",
            "id": "pyup.io-84049",
            "more_info_path": "/vulnerabilities/PVE-2026-84049/84049",
            "specs": [
                "<1.3.4"
            ],
            "v": "<1.3.4"
        }
    ],
    "openstack-heat": [
        {
            "advisory": "Openstack-heat 20.0.0 includes a fix for CVE-2023-1625: An information leak was discovered in OpenStack heat. This issue could allow a remote, authenticated attacker to use the 'stack show' command to reveal parameters which are supposed to remain hidden. This has a low impact to the confidentiality, integrity, and availability of the system.\r\nhttps://github.com/openstack/heat/commit/a49526c278e52823080c7f3fcb72785b93fd4dcb",
            "cve": "CVE-2023-1625",
            "id": "pyup.io-61406",
            "more_info_path": "/vulnerabilities/CVE-2023-1625/61406",
            "specs": [
                "<20.0.0"
            ],
            "v": "<20.0.0"
        },
        {
            "advisory": "Affected versions of the openstack-heat package are vulnerable to Information Disclosure due to an incomplete fix for CVE-2023-1625 that persists when the hidden feature is enabled. The `stack abandon` command with `hidden=True` still exposes sensitive information because the patch intended to remediate the earlier vulnerability was not fully applied. An attacker with low-privileged network access can exploit this by invoking `stack abandon hidden=True` to retrieve confidential details, potentially breaching confidentiality within the OpenStack orchestration environment.",
            "cve": "CVE-2024-7319",
            "id": "pyup.io-78756",
            "more_info_path": "/vulnerabilities/CVE-2024-7319/78756",
            "specs": [
                "<22.0.1"
            ],
            "v": "<22.0.1"
        },
        {
            "advisory": "OpenStack Orchestration API (Heat) 2013.2 through 2013.2.3 and 2014.1, when creating the stack for a template using a provider template, allows remote authenticated users to obtain the provider template URL via the resource-type-list.",
            "cve": "CVE-2014-3801",
            "id": "pyup.io-70481",
            "more_info_path": "/vulnerabilities/CVE-2014-3801/70481",
            "specs": [
                "<5.0.0a0"
            ],
            "v": "<5.0.0a0"
        },
        {
            "advisory": "The cloudformation-compatible API in OpenStack Orchestration API (Heat) before Havana 2013.2.1 and Icehouse before icehouse-2 does not properly enforce policy rules, which allows local in-instance users to bypass intended access restrictions and (1) create a stack via the CreateStack method or (2) update a stack via the UpdateStack method.",
            "cve": "CVE-2013-6426",
            "id": "pyup.io-67978",
            "more_info_path": "/vulnerabilities/CVE-2013-6426/67978",
            "specs": [
                ">=2013,<2013.2.1"
            ],
            "v": ">=2013,<2013.2.1"
        },
        {
            "advisory": "The ReST API in OpenStack Orchestration API (Heat) before Havana 2013.2.1 and Icehouse before icehouse-2 allows remote authenticated users to bypass the tenant scoping restrictions via a modified tenant_id in the request path.",
            "cve": "CVE-2013-6428",
            "id": "pyup.io-67977",
            "more_info_path": "/vulnerabilities/CVE-2013-6428/67977",
            "specs": [
                ">=2013,<2013.2.1"
            ],
            "v": ">=2013,<2013.2.1"
        }
    ],
    "openstack-keystone": [
        {
            "advisory": "An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The EC2 API doesn't have a signature TTL check for AWS Signature V4. An attacker can sniff the Authorization header, and then use it to reissue an OpenStack token an unlimited number of times.",
            "cve": "CVE-2020-12692",
            "id": "pyup.io-45600",
            "more_info_path": "/vulnerabilities/CVE-2020-12692/45600",
            "specs": [
                "<15.0.1",
                "==16.0.0"
            ],
            "v": "<15.0.1,==16.0.0"
        },
        {
            "advisory": "An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any authenticated user can create an EC2 credential for themselves for a project that they have a specified role on, and then perform an update to the credential user and project, allowing them to masquerade as another user. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges.",
            "cve": "CVE-2020-12691",
            "id": "pyup.io-45598",
            "more_info_path": "/vulnerabilities/CVE-2020-12691/45598",
            "specs": [
                "<15.0.1",
                "==16.0.0"
            ],
            "v": "<15.0.1,==16.0.0"
        },
        {
            "advisory": "An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The list of roles provided for an OAuth1 access token is silently ignored. Thus, when an access token is used to request a keystone token, the keystone token contains every role assignment the creator had for the project. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access. See: CVE-2020-12690.",
            "cve": "CVE-2020-12690",
            "id": "pyup.io-45601",
            "more_info_path": "/vulnerabilities/CVE-2020-12690/45601",
            "specs": [
                "<15.0.1",
                "==16.0.0"
            ],
            "v": "<15.0.1,==16.0.0"
        },
        {
            "advisory": "An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any user authenticated within a limited scope (trust/oauth/application credential) can create an EC2 credential with an escalated permission, such as obtaining admin while the user is on a limited viewer role. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges.",
            "cve": "CVE-2020-12689",
            "id": "pyup.io-45599",
            "more_info_path": "/vulnerabilities/CVE-2020-12689/45599",
            "specs": [
                "<15.0.1",
                "==16.0.0"
            ],
            "v": "<15.0.1,==16.0.0"
        },
        {
            "advisory": "OpenStack Keystone 15.0.0 and 16.0.0 are affected by Data Leakage in the list credentials API. Any user with a role on a project is able to list any credentials with the /v3/credentials API when enforce_scope is false. Users with a role on a project are able to view any other users' credentials, which could (for example) leak sign-on information for Time-based One Time Passwords (TOTP). Deployments with enforce_scope set to false are affected. (There will be a slight performance impact for the list credentials API once this issue is fixed.) See: CVE-2019-19687.",
            "cve": "CVE-2019-19687",
            "id": "pyup.io-45640",
            "more_info_path": "/vulnerabilities/CVE-2019-19687/45640",
            "specs": [
                "==15.0.0",
                "==16.0.0"
            ],
            "v": "==15.0.0,==16.0.0"
        },
        {
            "advisory": "HTTPSConnections in OpenStack Keystone 2013, OpenStack Compute 2013.1, and possibly other OpenStack components, fail to validate server-side SSL certificates. See: CVE-2013-2255.",
            "cve": "CVE-2013-2255",
            "id": "pyup.io-45610",
            "more_info_path": "/vulnerabilities/CVE-2013-2255/45610",
            "specs": [
                "==2013"
            ],
            "v": "==2013"
        },
        {
            "advisory": "It is possible to remotely trigger a crash in Keystone by sending an extremely long password. When Keystone is validating the password, glibc allocates space on the stack for the entire password. If the password is long enough, stack space can be exhausted, resulting in a crash. This vulnerability is mitigated by a patch to impose a reasonable limit on password length (4 kB). Reportedly, all versions are affected. See also: CVE-2012-1572 and https://security.openstack.org/ossa/OSSA-2012-002.html.",
            "cve": "CVE-2012-1572",
            "id": "pyup.io-45619",
            "more_info_path": "/vulnerabilities/CVE-2012-1572/45619",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "openstack-magnum": [
        {
            "advisory": "OpenStack Magnum passes OpenStack credentials into the Heat templates creating its instances. While these should just be used for retrieving the instances' SSL certificates, they allow full API access, though and can be used to perform any API operation the user is authorized to perform.",
            "cve": "CVE-2016-7404",
            "id": "pyup.io-65809",
            "more_info_path": "/vulnerabilities/CVE-2016-7404/65809",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        }
    ],
    "openstef": [
        {
            "advisory": "Openstef 3.1.1 upgrades its mlflow dependency, moving from the compatible release version of approximately 1.22.0 (=1.22.0) to approximately 1.24.0 (=1.24.0), in response to the security vulnerability CVE-2023-1176.",
            "cve": "CVE-2023-1176",
            "id": "pyup.io-64039",
            "more_info_path": "/vulnerabilities/CVE-2023-1176/64039",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        }
    ],
    "opentaxii": [
        {
            "advisory": "opentaxii 0.1.11 requires recent version of `lxml` for security reasons.",
            "cve": "PVE-2021-36897",
            "id": "pyup.io-36897",
            "more_info_path": "/vulnerabilities/PVE-2021-36897/36897",
            "specs": [
                "<0.1.11"
            ],
            "v": "<0.1.11"
        }
    ],
    "opentelemetry-instrumentation": [
        {
            "advisory": "Opentelemetry-instrumentation 0.41b0 includes a fix for CVE-2023-43810: Autoinstrumentation out of the box adds the label 'http_method' that has unbound cardinality. It leads to the server's potential memory exhaustion when many malicious requests are sent. HTTP method for requests can be easily set by an attacker to be random and long. In order to be affected program has to be instrumented for HTTP handlers and does not filter any unknown HTTP methods on the level of CDN, LB, previous middleware, etc.\r\nhttps://github.com/open-telemetry/opentelemetry-python-contrib/security/advisories/GHSA-5rv5-6h4r-h22v",
            "cve": "CVE-2023-43810",
            "id": "pyup.io-61653",
            "more_info_path": "/vulnerabilities/CVE-2023-43810/61653",
            "specs": [
                "<0.41b0"
            ],
            "v": "<0.41b0"
        }
    ],
    "opentera": [
        {
            "advisory": "Opentera 1.0.9 adds missing service access checks to the Service API.\r\nhttps://github.com/introlab/opentera/commit/4aa0361f6cd3faa395df6a43755fd197677c5528",
            "cve": "PVE-2021-42960",
            "id": "pyup.io-42960",
            "more_info_path": "/vulnerabilities/PVE-2021-42960/42960",
            "specs": [
                "<1.0.9"
            ],
            "v": "<1.0.9"
        },
        {
            "advisory": "Opentera version 1.2.6 addresses a configuration issue in nginx where services using dynamically specified ports in the URL were not restricted to certain ranges. This could potentially allow attackers to access other internal ports. The update resolves this by cleaning up the nginx configuration, specifically removing settings related to external services to restrict the URL-specified port to only the necessary ranges for each service.",
            "cve": "PVE-2024-70970",
            "id": "pyup.io-70970",
            "more_info_path": "/vulnerabilities/PVE-2024-70970/70970",
            "specs": [
                "<1.2.6"
            ],
            "v": "<1.2.6"
        }
    ],
    "openvc": [
        {
            "advisory": "Openvc is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45429",
            "id": "pyup.io-45429",
            "more_info_path": "/vulnerabilities/PVE-2022-45429/45429",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "openvino": [
        {
            "advisory": "Openvino 2020.3.1 includes security and functionality bug fixes, and minor capability changes.",
            "cve": "PVE-2021-40082",
            "id": "pyup.io-40082",
            "more_info_path": "/vulnerabilities/PVE-2021-40082/40082",
            "specs": [
                "<2020.3.1"
            ],
            "v": "<2020.3.1"
        },
        {
            "advisory": "Openvino 2021.2 includes GNA related security fixes.\r\nhttps://github.com/openvinotoolkit/openvino/pull/3167",
            "cve": "PVE-2021-42847",
            "id": "pyup.io-42847",
            "more_info_path": "/vulnerabilities/PVE-2021-42847/42847",
            "specs": [
                "<2021.2"
            ],
            "v": "<2021.2"
        },
        {
            "advisory": "Openvino 2021.3 fixes segmentations faults and null pointer dereferences in the GNA that could potentially lead to a crash.\r\nhttps://github.com/openvinotoolkit/openvino/pull/4538",
            "cve": "PVE-2021-42845",
            "id": "pyup.io-42845",
            "more_info_path": "/vulnerabilities/PVE-2021-42845/42845",
            "specs": [
                "<2021.3"
            ],
            "v": "<2021.3"
        },
        {
            "advisory": "Openvino 2021.3 updates its dependency 'urllib3' minimum version to v1.25.9 to include a security fix.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-42846",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/42846",
            "specs": [
                "<2021.3"
            ],
            "v": "<2021.3"
        },
        {
            "advisory": "Openvino 2021.4.0 fixes a security issue with XML parsing.\r\nhttps://github.com/openvinotoolkit/openvino/pull/5686",
            "cve": "CVE-2013-1664",
            "id": "pyup.io-54883",
            "more_info_path": "/vulnerabilities/CVE-2013-1664/54883",
            "specs": [
                "<2021.4.0"
            ],
            "v": "<2021.4.0"
        },
        {
            "advisory": "Openvino 2021.4.0 fixes a security issue with XML parsing.\r\nhttps://github.com/openvinotoolkit/openvino/pull/5686",
            "cve": "CVE-2013-1665",
            "id": "pyup.io-42844",
            "more_info_path": "/vulnerabilities/CVE-2013-1665/42844",
            "specs": [
                "<2021.4.0"
            ],
            "v": "<2021.4.0"
        },
        {
            "advisory": "Openvino 2022.1 includes LP transformations related security fixes.\r\nhttps://github.com/openvinotoolkit/openvino/pull/8357",
            "cve": "PVE-2021-42843",
            "id": "pyup.io-42843",
            "more_info_path": "/vulnerabilities/PVE-2021-42843/42843",
            "specs": [
                "<2022.1"
            ],
            "v": "<2022.1"
        },
        {
            "advisory": "Openvino 2022.1 includes CPU related security fixes.\r\nhttps://github.com/openvinotoolkit/openvino/pull/8456",
            "cve": "PVE-2021-42842",
            "id": "pyup.io-42842",
            "more_info_path": "/vulnerabilities/PVE-2021-42842/42842",
            "specs": [
                "<2022.1"
            ],
            "v": "<2022.1"
        }
    ],
    "openvino-tensorflow": [
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29512",
            "id": "pyup.io-43120",
            "more_info_path": "/vulnerabilities/CVE-2021-29512/43120",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29576",
            "id": "pyup.io-43201",
            "more_info_path": "/vulnerabilities/CVE-2021-29576/43201",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29595",
            "id": "pyup.io-43144",
            "more_info_path": "/vulnerabilities/CVE-2021-29595/43144",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29613",
            "id": "pyup.io-43170",
            "more_info_path": "/vulnerabilities/CVE-2021-29613/43170",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37663",
            "id": "pyup.io-43221",
            "more_info_path": "/vulnerabilities/CVE-2021-37663/43221",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37657",
            "id": "pyup.io-43228",
            "more_info_path": "/vulnerabilities/CVE-2021-37657/43228",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37658",
            "id": "pyup.io-43244",
            "more_info_path": "/vulnerabilities/CVE-2021-37658/43244",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37672",
            "id": "pyup.io-43213",
            "more_info_path": "/vulnerabilities/CVE-2021-37672/43213",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-22876",
            "id": "pyup.io-43207",
            "more_info_path": "/vulnerabilities/CVE-2021-22876/43207",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29533",
            "id": "pyup.io-43121",
            "more_info_path": "/vulnerabilities/CVE-2021-29533/43121",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29594",
            "id": "pyup.io-43145",
            "more_info_path": "/vulnerabilities/CVE-2021-29594/43145",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29575",
            "id": "pyup.io-43197",
            "more_info_path": "/vulnerabilities/CVE-2021-29575/43197",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29600",
            "id": "pyup.io-43156",
            "more_info_path": "/vulnerabilities/CVE-2021-29600/43156",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37648",
            "id": "pyup.io-43258",
            "more_info_path": "/vulnerabilities/CVE-2021-37648/43258",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29591",
            "id": "pyup.io-43143",
            "more_info_path": "/vulnerabilities/CVE-2021-29591/43143",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29549",
            "id": "pyup.io-43172",
            "more_info_path": "/vulnerabilities/CVE-2021-29549/43172",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29520",
            "id": "pyup.io-43099",
            "more_info_path": "/vulnerabilities/CVE-2021-29520/43099",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29606",
            "id": "pyup.io-43162",
            "more_info_path": "/vulnerabilities/CVE-2021-29606/43162",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29574",
            "id": "pyup.io-43200",
            "more_info_path": "/vulnerabilities/CVE-2021-29574/43200",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29614",
            "id": "pyup.io-43204",
            "more_info_path": "/vulnerabilities/CVE-2021-29614/43204",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29592",
            "id": "pyup.io-43142",
            "more_info_path": "/vulnerabilities/CVE-2021-29592/43142",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29565",
            "id": "pyup.io-43188",
            "more_info_path": "/vulnerabilities/CVE-2021-29565/43188",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29605",
            "id": "pyup.io-43160",
            "more_info_path": "/vulnerabilities/CVE-2021-29605/43160",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-22897",
            "id": "pyup.io-43206",
            "more_info_path": "/vulnerabilities/CVE-2021-22897/43206",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37660",
            "id": "pyup.io-43227",
            "more_info_path": "/vulnerabilities/CVE-2021-37660/43227",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29540",
            "id": "pyup.io-43126",
            "more_info_path": "/vulnerabilities/CVE-2021-29540/43126",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29552",
            "id": "pyup.io-43177",
            "more_info_path": "/vulnerabilities/CVE-2021-29552/43177",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29523",
            "id": "pyup.io-43094",
            "more_info_path": "/vulnerabilities/CVE-2021-29523/43094",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29603",
            "id": "pyup.io-43161",
            "more_info_path": "/vulnerabilities/CVE-2021-29603/43161",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29569",
            "id": "pyup.io-43193",
            "more_info_path": "/vulnerabilities/CVE-2021-29569/43193",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29518",
            "id": "pyup.io-43189",
            "more_info_path": "/vulnerabilities/CVE-2021-29518/43189",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37647",
            "id": "pyup.io-43245",
            "more_info_path": "/vulnerabilities/CVE-2021-37647/43245",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37643",
            "id": "pyup.io-43240",
            "more_info_path": "/vulnerabilities/CVE-2021-37643/43240",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-22901",
            "id": "pyup.io-43205",
            "more_info_path": "/vulnerabilities/CVE-2021-22901/43205",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29542",
            "id": "pyup.io-43163",
            "more_info_path": "/vulnerabilities/CVE-2021-29542/43163",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37645",
            "id": "pyup.io-43208",
            "more_info_path": "/vulnerabilities/CVE-2021-37645/43208",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29590",
            "id": "pyup.io-43141",
            "more_info_path": "/vulnerabilities/CVE-2021-29590/43141",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37654",
            "id": "pyup.io-43250",
            "more_info_path": "/vulnerabilities/CVE-2021-37654/43250",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29550",
            "id": "pyup.io-43114",
            "more_info_path": "/vulnerabilities/CVE-2021-29550/43114",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37639",
            "id": "pyup.io-43251",
            "more_info_path": "/vulnerabilities/CVE-2021-37639/43251",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29567",
            "id": "pyup.io-43118",
            "more_info_path": "/vulnerabilities/CVE-2021-29567/43118",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29619",
            "id": "pyup.io-43176",
            "more_info_path": "/vulnerabilities/CVE-2021-29619/43176",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29618",
            "id": "pyup.io-43173",
            "more_info_path": "/vulnerabilities/CVE-2021-29618/43173",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2020-8286",
            "id": "pyup.io-43186",
            "more_info_path": "/vulnerabilities/CVE-2020-8286/43186",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29617",
            "id": "pyup.io-43174",
            "more_info_path": "/vulnerabilities/CVE-2021-29617/43174",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29530",
            "id": "pyup.io-43151",
            "more_info_path": "/vulnerabilities/CVE-2021-29530/43151",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37667",
            "id": "pyup.io-43243",
            "more_info_path": "/vulnerabilities/CVE-2021-37667/43243",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29607",
            "id": "pyup.io-43166",
            "more_info_path": "/vulnerabilities/CVE-2021-29607/43166",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29568",
            "id": "pyup.io-43111",
            "more_info_path": "/vulnerabilities/CVE-2021-29568/43111",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29593",
            "id": "pyup.io-43149",
            "more_info_path": "/vulnerabilities/CVE-2021-29593/43149",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29616",
            "id": "pyup.io-43104",
            "more_info_path": "/vulnerabilities/CVE-2021-29616/43104",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29611",
            "id": "pyup.io-43167",
            "more_info_path": "/vulnerabilities/CVE-2021-29611/43167",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29538",
            "id": "pyup.io-43125",
            "more_info_path": "/vulnerabilities/CVE-2021-29538/43125",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29513",
            "id": "pyup.io-43129",
            "more_info_path": "/vulnerabilities/CVE-2021-29513/43129",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29599",
            "id": "pyup.io-43155",
            "more_info_path": "/vulnerabilities/CVE-2021-29599/43155",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29604",
            "id": "pyup.io-43158",
            "more_info_path": "/vulnerabilities/CVE-2021-29604/43158",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29598",
            "id": "pyup.io-43153",
            "more_info_path": "/vulnerabilities/CVE-2021-29598/43153",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29597",
            "id": "pyup.io-43150",
            "more_info_path": "/vulnerabilities/CVE-2021-29597/43150",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29601",
            "id": "pyup.io-43159",
            "more_info_path": "/vulnerabilities/CVE-2021-29601/43159",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29558",
            "id": "pyup.io-43185",
            "more_info_path": "/vulnerabilities/CVE-2021-29558/43185",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37638",
            "id": "pyup.io-43253",
            "more_info_path": "/vulnerabilities/CVE-2021-37638/43253",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29589",
            "id": "pyup.io-43119",
            "more_info_path": "/vulnerabilities/CVE-2021-29589/43119",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29583",
            "id": "pyup.io-43137",
            "more_info_path": "/vulnerabilities/CVE-2021-29583/43137",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29579",
            "id": "pyup.io-43133",
            "more_info_path": "/vulnerabilities/CVE-2021-29579/43133",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29543",
            "id": "pyup.io-43105",
            "more_info_path": "/vulnerabilities/CVE-2021-29543/43105",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29585",
            "id": "pyup.io-43138",
            "more_info_path": "/vulnerabilities/CVE-2021-29585/43138",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37678",
            "id": "pyup.io-43261",
            "more_info_path": "/vulnerabilities/CVE-2021-37678/43261",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29609",
            "id": "pyup.io-43164",
            "more_info_path": "/vulnerabilities/CVE-2021-29609/43164",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29572",
            "id": "pyup.io-43130",
            "more_info_path": "/vulnerabilities/CVE-2021-29572/43130",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29525",
            "id": "pyup.io-43095",
            "more_info_path": "/vulnerabilities/CVE-2021-29525/43095",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29588",
            "id": "pyup.io-43140",
            "more_info_path": "/vulnerabilities/CVE-2021-29588/43140",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29528",
            "id": "pyup.io-43148",
            "more_info_path": "/vulnerabilities/CVE-2021-29528/43148",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37689",
            "id": "pyup.io-43257",
            "more_info_path": "/vulnerabilities/CVE-2021-37689/43257",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29578",
            "id": "pyup.io-43132",
            "more_info_path": "/vulnerabilities/CVE-2021-29578/43132",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37649",
            "id": "pyup.io-43247",
            "more_info_path": "/vulnerabilities/CVE-2021-37649/43247",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29519",
            "id": "pyup.io-43096",
            "more_info_path": "/vulnerabilities/CVE-2021-29519/43096",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37637",
            "id": "pyup.io-43225",
            "more_info_path": "/vulnerabilities/CVE-2021-37637/43225",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29566",
            "id": "pyup.io-43112",
            "more_info_path": "/vulnerabilities/CVE-2021-29566/43112",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29564",
            "id": "pyup.io-43100",
            "more_info_path": "/vulnerabilities/CVE-2021-29564/43100",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29563",
            "id": "pyup.io-43113",
            "more_info_path": "/vulnerabilities/CVE-2021-29563/43113",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29562",
            "id": "pyup.io-43194",
            "more_info_path": "/vulnerabilities/CVE-2021-29562/43194",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29612",
            "id": "pyup.io-43168",
            "more_info_path": "/vulnerabilities/CVE-2021-29612/43168",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37688",
            "id": "pyup.io-43237",
            "more_info_path": "/vulnerabilities/CVE-2021-37688/43237",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29559",
            "id": "pyup.io-43187",
            "more_info_path": "/vulnerabilities/CVE-2021-29559/43187",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29557",
            "id": "pyup.io-43182",
            "more_info_path": "/vulnerabilities/CVE-2021-29557/43182",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29556",
            "id": "pyup.io-43184",
            "more_info_path": "/vulnerabilities/CVE-2021-29556/43184",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29610",
            "id": "pyup.io-43109",
            "more_info_path": "/vulnerabilities/CVE-2021-29610/43109",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29573",
            "id": "pyup.io-43198",
            "more_info_path": "/vulnerabilities/CVE-2021-29573/43198",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37646",
            "id": "pyup.io-43231",
            "more_info_path": "/vulnerabilities/CVE-2021-37646/43231",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29548",
            "id": "pyup.io-43123",
            "more_info_path": "/vulnerabilities/CVE-2021-29548/43123",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37651",
            "id": "pyup.io-43241",
            "more_info_path": "/vulnerabilities/CVE-2021-37651/43241",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37656",
            "id": "pyup.io-43249",
            "more_info_path": "/vulnerabilities/CVE-2021-37656/43249",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37664",
            "id": "pyup.io-43246",
            "more_info_path": "/vulnerabilities/CVE-2021-37664/43246",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29529",
            "id": "pyup.io-43152",
            "more_info_path": "/vulnerabilities/CVE-2021-29529/43152",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29586",
            "id": "pyup.io-43139",
            "more_info_path": "/vulnerabilities/CVE-2021-29586/43139",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37641",
            "id": "pyup.io-43232",
            "more_info_path": "/vulnerabilities/CVE-2021-37641/43232",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29551",
            "id": "pyup.io-43128",
            "more_info_path": "/vulnerabilities/CVE-2021-29551/43128",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29537",
            "id": "pyup.io-43116",
            "more_info_path": "/vulnerabilities/CVE-2021-29537/43116",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29555",
            "id": "pyup.io-43180",
            "more_info_path": "/vulnerabilities/CVE-2021-29555/43180",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29553",
            "id": "pyup.io-43175",
            "more_info_path": "/vulnerabilities/CVE-2021-29553/43175",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29602",
            "id": "pyup.io-43157",
            "more_info_path": "/vulnerabilities/CVE-2021-29602/43157",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29582",
            "id": "pyup.io-43135",
            "more_info_path": "/vulnerabilities/CVE-2021-29582/43135",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37681",
            "id": "pyup.io-43223",
            "more_info_path": "/vulnerabilities/CVE-2021-37681/43223",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29596",
            "id": "pyup.io-43147",
            "more_info_path": "/vulnerabilities/CVE-2021-29596/43147",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29587",
            "id": "pyup.io-43110",
            "more_info_path": "/vulnerabilities/CVE-2021-29587/43110",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29580",
            "id": "pyup.io-43131",
            "more_info_path": "/vulnerabilities/CVE-2021-29580/43131",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29615",
            "id": "pyup.io-43171",
            "more_info_path": "/vulnerabilities/CVE-2021-29615/43171",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37665",
            "id": "pyup.io-43219",
            "more_info_path": "/vulnerabilities/CVE-2021-37665/43219",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29547",
            "id": "pyup.io-43106",
            "more_info_path": "/vulnerabilities/CVE-2021-29547/43106",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29545",
            "id": "pyup.io-43115",
            "more_info_path": "/vulnerabilities/CVE-2021-29545/43115",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29581",
            "id": "pyup.io-43134",
            "more_info_path": "/vulnerabilities/CVE-2021-29581/43134",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29561",
            "id": "pyup.io-43195",
            "more_info_path": "/vulnerabilities/CVE-2021-29561/43195",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29531",
            "id": "pyup.io-43154",
            "more_info_path": "/vulnerabilities/CVE-2021-29531/43154",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37662",
            "id": "pyup.io-43262",
            "more_info_path": "/vulnerabilities/CVE-2021-37662/43262",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29584",
            "id": "pyup.io-43136",
            "more_info_path": "/vulnerabilities/CVE-2021-29584/43136",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29534",
            "id": "pyup.io-43108",
            "more_info_path": "/vulnerabilities/CVE-2021-29534/43108",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29571",
            "id": "pyup.io-43202",
            "more_info_path": "/vulnerabilities/CVE-2021-29571/43202",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29516",
            "id": "pyup.io-43191",
            "more_info_path": "/vulnerabilities/CVE-2021-29516/43191",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29541",
            "id": "pyup.io-43165",
            "more_info_path": "/vulnerabilities/CVE-2021-29541/43165",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37673",
            "id": "pyup.io-43218",
            "more_info_path": "/vulnerabilities/CVE-2021-37673/43218",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37642",
            "id": "pyup.io-43255",
            "more_info_path": "/vulnerabilities/CVE-2021-37642/43255",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29560",
            "id": "pyup.io-43092",
            "more_info_path": "/vulnerabilities/CVE-2021-29560/43092",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29577",
            "id": "pyup.io-43203",
            "more_info_path": "/vulnerabilities/CVE-2021-29577/43203",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29570",
            "id": "pyup.io-43196",
            "more_info_path": "/vulnerabilities/CVE-2021-29570/43196",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29546",
            "id": "pyup.io-43169",
            "more_info_path": "/vulnerabilities/CVE-2021-29546/43169",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29536",
            "id": "pyup.io-43124",
            "more_info_path": "/vulnerabilities/CVE-2021-29536/43124",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29532",
            "id": "pyup.io-43103",
            "more_info_path": "/vulnerabilities/CVE-2021-29532/43103",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29527",
            "id": "pyup.io-43146",
            "more_info_path": "/vulnerabilities/CVE-2021-29527/43146",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29524",
            "id": "pyup.io-43098",
            "more_info_path": "/vulnerabilities/CVE-2021-29524/43098",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29522",
            "id": "pyup.io-43097",
            "more_info_path": "/vulnerabilities/CVE-2021-29522/43097",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29515",
            "id": "pyup.io-43199",
            "more_info_path": "/vulnerabilities/CVE-2021-29515/43199",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29514",
            "id": "pyup.io-43117",
            "more_info_path": "/vulnerabilities/CVE-2021-29514/43117",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29526",
            "id": "pyup.io-43190",
            "more_info_path": "/vulnerabilities/CVE-2021-29526/43190",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29554",
            "id": "pyup.io-43178",
            "more_info_path": "/vulnerabilities/CVE-2021-29554/43178",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37650",
            "id": "pyup.io-43236",
            "more_info_path": "/vulnerabilities/CVE-2021-37650/43236",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2020-8284",
            "id": "pyup.io-43183",
            "more_info_path": "/vulnerabilities/CVE-2020-8284/43183",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2020-8231",
            "id": "pyup.io-43181",
            "more_info_path": "/vulnerabilities/CVE-2020-8231/43181",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2020-8177",
            "id": "pyup.io-43179",
            "more_info_path": "/vulnerabilities/CVE-2020-8177/43179",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2020-8169",
            "id": "pyup.io-43102",
            "more_info_path": "/vulnerabilities/CVE-2020-8169/43102",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37679",
            "id": "pyup.io-43217",
            "more_info_path": "/vulnerabilities/CVE-2021-37679/43217",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29608",
            "id": "pyup.io-43127",
            "more_info_path": "/vulnerabilities/CVE-2021-29608/43127",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37686",
            "id": "pyup.io-43263",
            "more_info_path": "/vulnerabilities/CVE-2021-37686/43263",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37661",
            "id": "pyup.io-43226",
            "more_info_path": "/vulnerabilities/CVE-2021-37661/43226",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37670",
            "id": "pyup.io-43214",
            "more_info_path": "/vulnerabilities/CVE-2021-37670/43214",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37666",
            "id": "pyup.io-43234",
            "more_info_path": "/vulnerabilities/CVE-2021-37666/43234",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-22898",
            "id": "pyup.io-43252",
            "more_info_path": "/vulnerabilities/CVE-2021-22898/43252",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29517",
            "id": "pyup.io-43192",
            "more_info_path": "/vulnerabilities/CVE-2021-29517/43192",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37659",
            "id": "pyup.io-43235",
            "more_info_path": "/vulnerabilities/CVE-2021-37659/43235",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37652",
            "id": "pyup.io-43233",
            "more_info_path": "/vulnerabilities/CVE-2021-37652/43233",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29544",
            "id": "pyup.io-43107",
            "more_info_path": "/vulnerabilities/CVE-2021-29544/43107",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37636",
            "id": "pyup.io-43254",
            "more_info_path": "/vulnerabilities/CVE-2021-37636/43254",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29535",
            "id": "pyup.io-43122",
            "more_info_path": "/vulnerabilities/CVE-2021-29535/43122",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-29521",
            "id": "pyup.io-43101",
            "more_info_path": "/vulnerabilities/CVE-2021-29521/43101",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37669",
            "id": "pyup.io-43212",
            "more_info_path": "/vulnerabilities/CVE-2021-37669/43212",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37690",
            "id": "pyup.io-43222",
            "more_info_path": "/vulnerabilities/CVE-2021-37690/43222",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37691",
            "id": "pyup.io-43224",
            "more_info_path": "/vulnerabilities/CVE-2021-37691/43224",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37687",
            "id": "pyup.io-43209",
            "more_info_path": "/vulnerabilities/CVE-2021-37687/43209",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37685",
            "id": "pyup.io-43210",
            "more_info_path": "/vulnerabilities/CVE-2021-37685/43210",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37684",
            "id": "pyup.io-43242",
            "more_info_path": "/vulnerabilities/CVE-2021-37684/43242",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37683",
            "id": "pyup.io-43256",
            "more_info_path": "/vulnerabilities/CVE-2021-37683/43256",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37682",
            "id": "pyup.io-43230",
            "more_info_path": "/vulnerabilities/CVE-2021-37682/43230",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37674",
            "id": "pyup.io-43220",
            "more_info_path": "/vulnerabilities/CVE-2021-37674/43220",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37668",
            "id": "pyup.io-43215",
            "more_info_path": "/vulnerabilities/CVE-2021-37668/43215",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37677",
            "id": "pyup.io-43216",
            "more_info_path": "/vulnerabilities/CVE-2021-37677/43216",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37680",
            "id": "pyup.io-43259",
            "more_info_path": "/vulnerabilities/CVE-2021-37680/43259",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37676",
            "id": "pyup.io-43238",
            "more_info_path": "/vulnerabilities/CVE-2021-37676/43238",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37675",
            "id": "pyup.io-43239",
            "more_info_path": "/vulnerabilities/CVE-2021-37675/43239",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37671",
            "id": "pyup.io-43260",
            "more_info_path": "/vulnerabilities/CVE-2021-37671/43260",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37644",
            "id": "pyup.io-43211",
            "more_info_path": "/vulnerabilities/CVE-2021-37644/43211",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37635",
            "id": "pyup.io-43248",
            "more_info_path": "/vulnerabilities/CVE-2021-37635/43248",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.0 updates its dependency 'tensorflow' to v2.5.1 to include security fixes.",
            "cve": "CVE-2021-37653",
            "id": "pyup.io-43229",
            "more_info_path": "/vulnerabilities/CVE-2021-37653/43229",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.0.1 adds extra checks to fix vulnerabilities.\r\nhttps://github.com/openvinotoolkit/openvino_tensorflow/pull/199/files",
            "cve": "PVE-2021-43091",
            "id": "pyup.io-43091",
            "more_info_path": "/vulnerabilities/PVE-2021-43091/43091",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41222",
            "id": "pyup.io-43293",
            "more_info_path": "/vulnerabilities/CVE-2021-41222/43293",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41200",
            "id": "pyup.io-43280",
            "more_info_path": "/vulnerabilities/CVE-2021-41200/43280",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41207",
            "id": "pyup.io-43304",
            "more_info_path": "/vulnerabilities/CVE-2021-41207/43304",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41205",
            "id": "pyup.io-43301",
            "more_info_path": "/vulnerabilities/CVE-2021-41205/43301",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41209",
            "id": "pyup.io-43289",
            "more_info_path": "/vulnerabilities/CVE-2021-41209/43289",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41196",
            "id": "pyup.io-43277",
            "more_info_path": "/vulnerabilities/CVE-2021-41196/43277",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41226",
            "id": "pyup.io-43285",
            "more_info_path": "/vulnerabilities/CVE-2021-41226/43285",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41227",
            "id": "pyup.io-43286",
            "more_info_path": "/vulnerabilities/CVE-2021-41227/43286",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41204",
            "id": "pyup.io-43291",
            "more_info_path": "/vulnerabilities/CVE-2021-41204/43291",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41215",
            "id": "pyup.io-43297",
            "more_info_path": "/vulnerabilities/CVE-2021-41215/43297",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41219",
            "id": "pyup.io-43283",
            "more_info_path": "/vulnerabilities/CVE-2021-41219/43283",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41216",
            "id": "pyup.io-43296",
            "more_info_path": "/vulnerabilities/CVE-2021-41216/43296",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41212",
            "id": "pyup.io-43302",
            "more_info_path": "/vulnerabilities/CVE-2021-41212/43302",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41225",
            "id": "pyup.io-43287",
            "more_info_path": "/vulnerabilities/CVE-2021-41225/43287",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41224",
            "id": "pyup.io-43294",
            "more_info_path": "/vulnerabilities/CVE-2021-41224/43294",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41228",
            "id": "pyup.io-43292",
            "more_info_path": "/vulnerabilities/CVE-2021-41228/43292",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41221",
            "id": "pyup.io-43288",
            "more_info_path": "/vulnerabilities/CVE-2021-41221/43288",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41213",
            "id": "pyup.io-43290",
            "more_info_path": "/vulnerabilities/CVE-2021-41213/43290",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41218",
            "id": "pyup.io-43295",
            "more_info_path": "/vulnerabilities/CVE-2021-41218/43295",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41208",
            "id": "pyup.io-43298",
            "more_info_path": "/vulnerabilities/CVE-2021-41208/43298",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41206",
            "id": "pyup.io-43300",
            "more_info_path": "/vulnerabilities/CVE-2021-41206/43300",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41202",
            "id": "pyup.io-43305",
            "more_info_path": "/vulnerabilities/CVE-2021-41202/43305",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41214",
            "id": "pyup.io-43282",
            "more_info_path": "/vulnerabilities/CVE-2021-41214/43282",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41203",
            "id": "pyup.io-43278",
            "more_info_path": "/vulnerabilities/CVE-2021-41203/43278",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41210",
            "id": "pyup.io-43303",
            "more_info_path": "/vulnerabilities/CVE-2021-41210/43303",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41201",
            "id": "pyup.io-43306",
            "more_info_path": "/vulnerabilities/CVE-2021-41201/43306",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41199",
            "id": "pyup.io-43276",
            "more_info_path": "/vulnerabilities/CVE-2021-41199/43276",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41198",
            "id": "pyup.io-43275",
            "more_info_path": "/vulnerabilities/CVE-2021-41198/43275",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41197",
            "id": "pyup.io-43307",
            "more_info_path": "/vulnerabilities/CVE-2021-41197/43307",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41195",
            "id": "pyup.io-43090",
            "more_info_path": "/vulnerabilities/CVE-2021-41195/43090",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 1.1.0 updates its dependency 'tensorflow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41217",
            "id": "pyup.io-43281",
            "more_info_path": "/vulnerabilities/CVE-2021-41217/43281",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23562",
            "id": "pyup.io-47881",
            "more_info_path": "/vulnerabilities/CVE-2022-23562/47881",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23570",
            "id": "pyup.io-47889",
            "more_info_path": "/vulnerabilities/CVE-2022-23570/47889",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21732",
            "id": "pyup.io-47866",
            "more_info_path": "/vulnerabilities/CVE-2022-21732/47866",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23558",
            "id": "pyup.io-47877",
            "more_info_path": "/vulnerabilities/CVE-2022-23558/47877",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23588",
            "id": "pyup.io-47907",
            "more_info_path": "/vulnerabilities/CVE-2022-23588/47907",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23589",
            "id": "pyup.io-47908",
            "more_info_path": "/vulnerabilities/CVE-2022-23589/47908",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23571",
            "id": "pyup.io-47890",
            "more_info_path": "/vulnerabilities/CVE-2022-23571/47890",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23572",
            "id": "pyup.io-47891",
            "more_info_path": "/vulnerabilities/CVE-2022-23572/47891",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21726",
            "id": "pyup.io-47860",
            "more_info_path": "/vulnerabilities/CVE-2022-21726/47860",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21736",
            "id": "pyup.io-47870",
            "more_info_path": "/vulnerabilities/CVE-2022-21736/47870",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23567",
            "id": "pyup.io-47886",
            "more_info_path": "/vulnerabilities/CVE-2022-23567/47886",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23594",
            "id": "pyup.io-47911",
            "more_info_path": "/vulnerabilities/CVE-2022-23594/47911",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21737",
            "id": "pyup.io-47871",
            "more_info_path": "/vulnerabilities/CVE-2022-21737/47871",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23587",
            "id": "pyup.io-47906",
            "more_info_path": "/vulnerabilities/CVE-2022-23587/47906",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21741",
            "id": "pyup.io-47875",
            "more_info_path": "/vulnerabilities/CVE-2022-21741/47875",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23566",
            "id": "pyup.io-47885",
            "more_info_path": "/vulnerabilities/CVE-2022-23566/47885",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2020-10531",
            "id": "pyup.io-47858",
            "more_info_path": "/vulnerabilities/CVE-2020-10531/47858",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23595",
            "id": "pyup.io-47912",
            "more_info_path": "/vulnerabilities/CVE-2022-23595/47912",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23591",
            "id": "pyup.io-47910",
            "more_info_path": "/vulnerabilities/CVE-2022-23591/47910",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23590",
            "id": "pyup.io-47909",
            "more_info_path": "/vulnerabilities/CVE-2022-23590/47909",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23586",
            "id": "pyup.io-47905",
            "more_info_path": "/vulnerabilities/CVE-2022-23586/47905",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23585",
            "id": "pyup.io-47904",
            "more_info_path": "/vulnerabilities/CVE-2022-23585/47904",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23584",
            "id": "pyup.io-47903",
            "more_info_path": "/vulnerabilities/CVE-2022-23584/47903",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23583",
            "id": "pyup.io-47902",
            "more_info_path": "/vulnerabilities/CVE-2022-23583/47902",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23582",
            "id": "pyup.io-47901",
            "more_info_path": "/vulnerabilities/CVE-2022-23582/47901",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23581",
            "id": "pyup.io-47900",
            "more_info_path": "/vulnerabilities/CVE-2022-23581/47900",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23580",
            "id": "pyup.io-47899",
            "more_info_path": "/vulnerabilities/CVE-2022-23580/47899",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23579",
            "id": "pyup.io-47898",
            "more_info_path": "/vulnerabilities/CVE-2022-23579/47898",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23578",
            "id": "pyup.io-47897",
            "more_info_path": "/vulnerabilities/CVE-2022-23578/47897",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23577",
            "id": "pyup.io-47896",
            "more_info_path": "/vulnerabilities/CVE-2022-23577/47896",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23576",
            "id": "pyup.io-47895",
            "more_info_path": "/vulnerabilities/CVE-2022-23576/47895",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23575",
            "id": "pyup.io-47894",
            "more_info_path": "/vulnerabilities/CVE-2022-23575/47894",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23574",
            "id": "pyup.io-47893",
            "more_info_path": "/vulnerabilities/CVE-2022-23574/47893",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23573",
            "id": "pyup.io-47892",
            "more_info_path": "/vulnerabilities/CVE-2022-23573/47892",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23565",
            "id": "pyup.io-47884",
            "more_info_path": "/vulnerabilities/CVE-2022-23565/47884",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23564",
            "id": "pyup.io-47883",
            "more_info_path": "/vulnerabilities/CVE-2022-23564/47883",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23563",
            "id": "pyup.io-47882",
            "more_info_path": "/vulnerabilities/CVE-2022-23563/47882",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23561",
            "id": "pyup.io-47880",
            "more_info_path": "/vulnerabilities/CVE-2022-23561/47880",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23560",
            "id": "pyup.io-47879",
            "more_info_path": "/vulnerabilities/CVE-2022-23560/47879",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23559",
            "id": "pyup.io-47878",
            "more_info_path": "/vulnerabilities/CVE-2022-23559/47878",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23557",
            "id": "pyup.io-47876",
            "more_info_path": "/vulnerabilities/CVE-2022-23557/47876",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21730",
            "id": "pyup.io-47864",
            "more_info_path": "/vulnerabilities/CVE-2022-21730/47864",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21733",
            "id": "pyup.io-47867",
            "more_info_path": "/vulnerabilities/CVE-2022-21733/47867",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21739",
            "id": "pyup.io-47873",
            "more_info_path": "/vulnerabilities/CVE-2022-21739/47873",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21729",
            "id": "pyup.io-47863",
            "more_info_path": "/vulnerabilities/CVE-2022-21729/47863",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21738",
            "id": "pyup.io-47872",
            "more_info_path": "/vulnerabilities/CVE-2022-21738/47872",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21727",
            "id": "pyup.io-47861",
            "more_info_path": "/vulnerabilities/CVE-2022-21727/47861",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23568",
            "id": "pyup.io-47887",
            "more_info_path": "/vulnerabilities/CVE-2022-23568/47887",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21728",
            "id": "pyup.io-47862",
            "more_info_path": "/vulnerabilities/CVE-2022-21728/47862",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21731",
            "id": "pyup.io-47865",
            "more_info_path": "/vulnerabilities/CVE-2022-21731/47865",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21734",
            "id": "pyup.io-47868",
            "more_info_path": "/vulnerabilities/CVE-2022-21734/47868",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21740",
            "id": "pyup.io-47874",
            "more_info_path": "/vulnerabilities/CVE-2022-21740/47874",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21725",
            "id": "pyup.io-47859",
            "more_info_path": "/vulnerabilities/CVE-2022-21725/47859",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21735",
            "id": "pyup.io-47869",
            "more_info_path": "/vulnerabilities/CVE-2022-21735/47869",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.0.0 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23569",
            "id": "pyup.io-47888",
            "more_info_path": "/vulnerabilities/CVE-2022-23569/47888",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29194",
            "id": "pyup.io-50188",
            "more_info_path": "/vulnerabilities/CVE-2022-29194/50188",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-27780",
            "id": "pyup.io-50182",
            "more_info_path": "/vulnerabilities/CVE-2022-27780/50182",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-27778",
            "id": "pyup.io-50180",
            "more_info_path": "/vulnerabilities/CVE-2022-27778/50180",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-27776",
            "id": "pyup.io-50178",
            "more_info_path": "/vulnerabilities/CVE-2022-27776/50178",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-27774",
            "id": "pyup.io-50176",
            "more_info_path": "/vulnerabilities/CVE-2022-27774/50176",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-27777",
            "id": "pyup.io-50179",
            "more_info_path": "/vulnerabilities/CVE-2022-27777/50179",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29197",
            "id": "pyup.io-50191",
            "more_info_path": "/vulnerabilities/CVE-2022-29197/50191",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29195",
            "id": "pyup.io-50189",
            "more_info_path": "/vulnerabilities/CVE-2022-29195/50189",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-22576",
            "id": "pyup.io-50175",
            "more_info_path": "/vulnerabilities/CVE-2022-22576/50175",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29202",
            "id": "pyup.io-50196",
            "more_info_path": "/vulnerabilities/CVE-2022-29202/50196",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29196",
            "id": "pyup.io-50190",
            "more_info_path": "/vulnerabilities/CVE-2022-29196/50190",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29201",
            "id": "pyup.io-50195",
            "more_info_path": "/vulnerabilities/CVE-2022-29201/50195",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-27779",
            "id": "pyup.io-50181",
            "more_info_path": "/vulnerabilities/CVE-2022-27779/50181",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29204",
            "id": "pyup.io-50198",
            "more_info_path": "/vulnerabilities/CVE-2022-29204/50198",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-30115",
            "id": "pyup.io-50209",
            "more_info_path": "/vulnerabilities/CVE-2022-30115/50209",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-27782",
            "id": "pyup.io-50184",
            "more_info_path": "/vulnerabilities/CVE-2022-27782/50184",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-27781",
            "id": "pyup.io-50183",
            "more_info_path": "/vulnerabilities/CVE-2022-27781/50183",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29216",
            "id": "pyup.io-50208",
            "more_info_path": "/vulnerabilities/CVE-2022-29216/50208",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29213",
            "id": "pyup.io-50207",
            "more_info_path": "/vulnerabilities/CVE-2022-29213/50207",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29212",
            "id": "pyup.io-50206",
            "more_info_path": "/vulnerabilities/CVE-2022-29212/50206",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29211",
            "id": "pyup.io-50205",
            "more_info_path": "/vulnerabilities/CVE-2022-29211/50205",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29210",
            "id": "pyup.io-50204",
            "more_info_path": "/vulnerabilities/CVE-2022-29210/50204",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29209",
            "id": "pyup.io-50203",
            "more_info_path": "/vulnerabilities/CVE-2022-29209/50203",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29208",
            "id": "pyup.io-50202",
            "more_info_path": "/vulnerabilities/CVE-2022-29208/50202",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29206",
            "id": "pyup.io-50200",
            "more_info_path": "/vulnerabilities/CVE-2022-29206/50200",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29205",
            "id": "pyup.io-50199",
            "more_info_path": "/vulnerabilities/CVE-2022-29205/50199",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-27775",
            "id": "pyup.io-50177",
            "more_info_path": "/vulnerabilities/CVE-2022-27775/50177",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29203",
            "id": "pyup.io-50197",
            "more_info_path": "/vulnerabilities/CVE-2022-29203/50197",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29207",
            "id": "pyup.io-50201",
            "more_info_path": "/vulnerabilities/CVE-2022-29207/50201",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29200",
            "id": "pyup.io-50194",
            "more_info_path": "/vulnerabilities/CVE-2022-29200/50194",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29199",
            "id": "pyup.io-50193",
            "more_info_path": "/vulnerabilities/CVE-2022-29199/50193",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29198",
            "id": "pyup.io-50192",
            "more_info_path": "/vulnerabilities/CVE-2022-29198/50192",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29193",
            "id": "pyup.io-50187",
            "more_info_path": "/vulnerabilities/CVE-2022-29193/50187",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29192",
            "id": "pyup.io-50186",
            "more_info_path": "/vulnerabilities/CVE-2022-29192/50186",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2022-29191",
            "id": "pyup.io-50185",
            "more_info_path": "/vulnerabilities/CVE-2022-29191/50185",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Openvino-tensorflow 2.1.0 updates its dependency 'TensorFlow' to v2.9.1 to include security fixes.",
            "cve": "CVE-2018-25032",
            "id": "pyup.io-50138",
            "more_info_path": "/vulnerabilities/CVE-2018-25032/50138",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        }
    ],
    "openvisus": [
        {
            "advisory": "Openvisus 1.2.85 throughout 1.2.178 ship with a version of C library 'libwebp' which is affected by a high risk vulnerability. Only Windows wheels on PyPI were affected.\r\nhttps://inspector.pypi.io/project/openvisus/1.2.178/packages/1f/f6/c799259c9c61521db3824856f42d01cc7c6ccfd05b91b4a249f7261046a3/OpenVisus-1.2.178-cp36-none-win_amd64.whl",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62320",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62320",
            "specs": [
                ">=1.2.85,<=1.2.178"
            ],
            "v": ">=1.2.85,<=1.2.178"
        }
    ],
    "openvpn-ldap-auth": [
        {
            "advisory": "Openvpn-ldap-auth version 0.1.7 updates its dependencies to include pytest version 4.3.0 or higher to address a known security vulnerability.",
            "cve": "PVE-2024-67455",
            "id": "pyup.io-67455",
            "more_info_path": "/vulnerabilities/PVE-2024-67455/67455",
            "specs": [
                "<0.1.7"
            ],
            "v": "<0.1.7"
        }
    ],
    "openvpn-monitor": [
        {
            "advisory": "Openvpn-monitor throughout 1.1.3 is affected by CVE-2021-31606: Authorization Bypass to disconnect arbitrary clients.\r\nA fix is available in openvpn-monitor GH repository.\r\nhttps://github.com/furlongm/openvpn-monitor/commit/ddb9d31ef0ec56f578bdacf99ebe9d68455ed8ca",
            "cve": "CVE-2021-31606",
            "id": "pyup.io-54339",
            "more_info_path": "/vulnerabilities/CVE-2021-31606/54339",
            "specs": [
                "<=1.1.3"
            ],
            "v": "<=1.1.3"
        },
        {
            "advisory": "furlongm openvpn-monitor through 1.1.3 allows CSRF to disconnect an arbitrary client.",
            "cve": "CVE-2021-31604",
            "id": "pyup.io-54338",
            "more_info_path": "/vulnerabilities/CVE-2021-31604/54338",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        },
        {
            "advisory": "furlongm openvpn-monitor through 1.1.3 allows %0a command injection via the OpenVPN management interface socket. This can shut down the server via signal%20SIGTERM.",
            "cve": "CVE-2021-31605",
            "id": "pyup.io-54395",
            "more_info_path": "/vulnerabilities/CVE-2021-31605/54395",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "openwisp-controller": [
        {
            "advisory": "Openwisp-controller 0.8.4 patches security bugs in internal HTTP endpoints which allowed to obtain UUID of other organizations and other sensitive information.",
            "cve": "PVE-2022-48396",
            "id": "pyup.io-48396",
            "more_info_path": "/vulnerabilities/PVE-2022-48396/48396",
            "specs": [
                "<0.8.4"
            ],
            "v": "<0.8.4"
        }
    ],
    "openwisp-users": [
        {
            "advisory": "Openwisp-users 1.0.2 updates its dependency 'django-allauth' to v0.51.0 to include a security fix.",
            "cve": "PVE-2021-43274",
            "id": "pyup.io-49690",
            "more_info_path": "/vulnerabilities/PVE-2021-43274/49690",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "openxc": [
        {
            "advisory": "Openxc 0.14.0 updates its dependency 'requests' to v2.20.0 to include security fixes.",
            "cve": "CVE-2015-2296",
            "id": "pyup.io-41102",
            "more_info_path": "/vulnerabilities/CVE-2015-2296/41102",
            "specs": [
                "<0.14.0"
            ],
            "v": "<0.14.0"
        },
        {
            "advisory": "Openxc 0.14.0 updates its dependency 'requests' to v2.20.0 to include security fixes.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-49113",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/49113",
            "specs": [
                "<0.14.0"
            ],
            "v": "<0.14.0"
        }
    ],
    "openxlab": [
        {
            "advisory": "Openxlab 0.0.13 throughout 0.0.23 ship with a version of C library 'libwebp' which is affected by a high risk vulnerability.\r\nhttps://inspector.pypi.io/project/openxlab/0.0.23/packages/b0/5a/815beb4f6220b5165666a0dd93c240646b0dc6ccca730e5b7aa659377a00/openxlab-0.0.23.tar.gz",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62313",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62313",
            "specs": [
                ">=0.0.13,<0.0.24"
            ],
            "v": ">=0.0.13,<0.0.24"
        }
    ],
    "openzeppelin-cairo-contracts": [
        {
            "advisory": "### Impact\nThis vulnerability affects all accounts (vanilla and ethereum flavors) in the [v0.2.0 release of OpenZeppelin Contracts for Cairo](https://github.com/OpenZeppelin/cairo-contracts/releases/tag/v0.2.0), which are not whitelisted on StarkNet mainnet, so only goerli deployments of v0.2.0 accounts are affected.\n\nThis faulty behavior is not observed in [StarkNet's testing framework](https://github.com/starkware-libs/cairo-lang/blob/master/src/starkware/starknet/testing/starknet.py), so don't rely on it passing to detect this issue on custom accounts.\n\n### Patches\nThis bug has been patched in [v0.2.1](https://github.com/OpenZeppelin/cairo-contracts/releases/tag/v0.2.1).\n\n### References\nThe issue is detailed in https://github.com/OpenZeppelin/cairo-contracts/issues/386.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Contracts for Cairo repo](https://github.com/OpenZeppelin/cairo-contracts/issues/new/choose)\n* Email us at [security@openzeppelin.com](mailto:security@openzeppelin.com)\n",
            "cve": "CVE-2022-31153",
            "id": "pyup.io-54446",
            "more_info_path": "/vulnerabilities/CVE-2022-31153/54446",
            "specs": [
                ">=0,<0.2.1"
            ],
            "v": ">=0,<0.2.1"
        },
        {
            "advisory": "### Cause\n`is_valid_eth_signature` is missing a call to `finalize_keccak` after calling `verify_eth_signature`. \n\n### Impact\nAs a result, any contract using `is_valid_eth_signature` from the account library (such as the `EthAccount` preset) is vulnerable to a malicious sequencer. Specifically, the malicious sequencer would be able to bypass signature validation to impersonate an instance of these accounts.\n\n### Risk\nIn order to exploit this vulnerability, it is required to control a sequencer or prover since they're the ones executing the hints, being able to inject incorrect keccak results.\n\nToday StarkWare is the only party running both a prover or a sequencer, greatly reducing the risk of exploit.\n\n### Patches\nThe issue has been patched in 0.6.1.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Contracts for Cairo repository](https://github.com/OpenZeppelin/cairo-contracts/issues/new/choose)\n* Email us at [security@openzeppelin.com](mailto:security@openzeppelin.com)",
            "cve": "CVE-2023-23940",
            "id": "pyup.io-54627",
            "more_info_path": "/vulnerabilities/CVE-2023-23940/54627",
            "specs": [
                ">=0.2.0,<0.6.1"
            ],
            "v": ">=0.2.0,<0.6.1"
        }
    ],
    "ophyd-async": [
        {
            "advisory": "Affected versions of `ophyd_async` are vulnerable to a race condition when setting one signal and monitoring another. This issue could lead to missed signal changes or incorrect system behaviour in asynchronous environments. The vulnerability has been addressed by introducing the `set_and_wait_for_other_value` function, which ensures that monitoring starts before the signal is set, preventing race conditions.",
            "cve": "PVE-2024-73037",
            "id": "pyup.io-73037",
            "more_info_path": "/vulnerabilities/PVE-2024-73037/73037",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        }
    ],
    "ops": [
        {
            "advisory": "The ops library is a Python framework for developing and testing Kubernetes and machine charms. The issue is that ops passes the secret content as one of the args via CLI. This issue may affect any of the charms that are using: Juju (>=3.0), Juju secrets, and not correctly capturing and processing `subprocess.CalledProcessError`.",
            "cve": "CVE-2024-41129",
            "id": "pyup.io-72314",
            "more_info_path": "/vulnerabilities/CVE-2024-41129/72314",
            "specs": [
                ">=2.0.0,<2.15.0"
            ],
            "v": ">=2.0.0,<2.15.0"
        }
    ],
    "ops-cli": [
        {
            "advisory": "Ops CLI version 2.0.4 (and earlier) is affected by a Deserialization of Untrusted Data vulnerability to achieve arbitrary code execution when the checkout_repo function is called on a maliciously crafted file. An attacker can leverage this to execute arbitrary code on the victim machine.",
            "cve": "CVE-2021-40720",
            "id": "pyup.io-54350",
            "more_info_path": "/vulnerabilities/CVE-2021-40720/54350",
            "specs": [
                ">=0,<2.0.5"
            ],
            "v": ">=0,<2.0.5"
        }
    ],
    "opsml": [
        {
            "advisory": "Opsml 0.3.0 updates its dependency 'tensorflow' to v2.11.1 to include several security fixes affecting Confidentiality, Integrity and Availability.",
            "cve": "CVE-2023-27579",
            "id": "pyup.io-61336",
            "more_info_path": "/vulnerabilities/CVE-2023-27579/61336",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Opsml 0.3.0 updates its dependency 'tensorflow' to v2.11.1 to include several security fixes affecting Confidentiality, Integrity and Availability.",
            "cve": "CVE-2023-25667",
            "id": "pyup.io-61335",
            "more_info_path": "/vulnerabilities/CVE-2023-25667/61335",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Opsml 0.3.0 updates its dependency 'tensorflow' to v2.11.1 to include several security fixes affecting Confidentiality, Integrity and Availability.",
            "cve": "CVE-2023-25659",
            "id": "pyup.io-61323",
            "more_info_path": "/vulnerabilities/CVE-2023-25659/61323",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Opsml 0.3.0 updates its dependency 'tensorflow' to v2.11.1 to include several security fixes affecting Confidentiality, Integrity and Availability.",
            "cve": "CVE-2023-25669",
            "id": "pyup.io-61334",
            "more_info_path": "/vulnerabilities/CVE-2023-25669/61334",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Opsml 0.3.0 updates its dependency 'tensorflow' to v2.11.1 to include several security fixes affecting Confidentiality, Integrity and Availability.",
            "cve": "CVE-2023-25663",
            "id": "pyup.io-61333",
            "more_info_path": "/vulnerabilities/CVE-2023-25663/61333",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Opsml 0.3.0 updates its dependency 'tensorflow' to v2.11.1 to include several security fixes affecting Confidentiality, Integrity and Availability.",
            "cve": "CVE-2023-25801",
            "id": "pyup.io-61332",
            "more_info_path": "/vulnerabilities/CVE-2023-25801/61332",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "optimade": [
        {
            "advisory": "Optimade 0.16.9 updates its dependency 'Elasticsearch' to v7.16.2 to avoid any log4j related vulnerability.\r\nhttps://github.com/Materials-Consortia/optimade-python-tools/issues/1040",
            "cve": "CVE-2021-45046",
            "id": "pyup.io-44695",
            "more_info_path": "/vulnerabilities/CVE-2021-45046/44695",
            "specs": [
                "<0.16.9"
            ],
            "v": "<0.16.9"
        },
        {
            "advisory": "Optimade 0.16.9 updates its dependency 'Elasticsearch' to v7.16.2 to avoid any log4j related vulnerability.\r\nhttps://github.com/Materials-Consortia/optimade-python-tools/issues/1040",
            "cve": "CVE-2021-44228",
            "id": "pyup.io-44681",
            "more_info_path": "/vulnerabilities/CVE-2021-44228/44681",
            "specs": [
                "<0.16.9"
            ],
            "v": "<0.16.9"
        },
        {
            "advisory": "Optimade 0.16.9 updates its dependency 'Elasticsearch' to v7.16.2 to avoid any log4j related vulnerability.\r\nhttps://github.com/Materials-Consortia/optimade-python-tools/issues/1040",
            "cve": "CVE-2021-45105",
            "id": "pyup.io-44696",
            "more_info_path": "/vulnerabilities/CVE-2021-45105/44696",
            "specs": [
                "<0.16.9"
            ],
            "v": "<0.16.9"
        },
        {
            "advisory": "Optimade 0.7.0 updates its dependency 'Django' to v2.2.8 to include a security fix.",
            "cve": "CVE-2019-19118",
            "id": "pyup.io-38453",
            "more_info_path": "/vulnerabilities/CVE-2019-19118/38453",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Optimade 0.16.9 uses a version of 'Elasticsearch' (v7.16.2) affected by a log4j vulnerability.",
            "cve": "CVE-2021-44832",
            "id": "pyup.io-44697",
            "more_info_path": "/vulnerabilities/CVE-2021-44832/44697",
            "specs": [
                "<=0.16.9"
            ],
            "v": "<=0.16.9"
        }
    ],
    "optimal-congress": [
        {
            "advisory": "Optimal-congress 0.7.3 updates its dependency 'jinja2' to include a security fix.",
            "cve": "CVE-2024-22195",
            "id": "pyup.io-74562",
            "more_info_path": "/vulnerabilities/CVE-2024-22195/74562",
            "specs": [
                "<0.7.3"
            ],
            "v": "<0.7.3"
        }
    ],
    "optimizely-sdk": [
        {
            "advisory": "Optimizely-sdk 4.0.0 stops requiring PyYaml==5.2 as a dependency to resolve security vulnerabilities.\r\nhttps://github.com/optimizely/python-sdk/pull/366/files",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-44535",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/44535",
            "specs": [
                "<4.0.0"
            ],
            "v": "<4.0.0"
        },
        {
            "advisory": "Optimizely-sdk 4.0.0 stops requiring PyYaml==5.2 as a dependency to resolve security vulnerabilities.\r\nhttps://github.com/optimizely/python-sdk/pull/366/files",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-44513",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/44513",
            "specs": [
                "<4.0.0"
            ],
            "v": "<4.0.0"
        }
    ],
    "orange-spectroscopy": [
        {
            "advisory": "Orange-spectroscopy 0.6.14 removes the inclusion of https://polyfill.io/v3/polyfill.min.js?features=es6 due to a security issue. This decision is aimed at mitigating potential vulnerabilities associated with the use of external polyfill services.",
            "cve": "PVE-2024-71815",
            "id": "pyup.io-71815",
            "more_info_path": "/vulnerabilities/PVE-2024-71815/71815",
            "specs": [
                "<0.6.14"
            ],
            "v": "<0.6.14"
        }
    ],
    "orange3-bioinformatics": [
        {
            "advisory": "Orange3-bioinformatics 4.2.0 adds the Orange.widgets.credentials.CredentialManager to securely store user password.",
            "cve": "PVE-2021-38958",
            "id": "pyup.io-38958",
            "more_info_path": "/vulnerabilities/PVE-2021-38958/38958",
            "specs": [
                "<4.2.0"
            ],
            "v": "<4.2.0"
        }
    ],
    "ores": [
        {
            "advisory": "Ores 1.3.1 changes pickle for JSON as celery serializer to avoid security issues.\r\nhttps://github.com/wikimedia/ores/commit/817915caf495c031a232071c27e25cb7c7e7696d",
            "cve": "PVE-2021-43649",
            "id": "pyup.io-43649",
            "more_info_path": "/vulnerabilities/PVE-2021-43649/43649",
            "specs": [
                "<1.3.1"
            ],
            "v": "<1.3.1"
        },
        {
            "advisory": "Ores 1.3.1 updates its dependency 'pyyaml' to v4.2b4 to include a security fix.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-37949",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/37949",
            "specs": [
                "<1.3.1"
            ],
            "v": "<1.3.1"
        }
    ],
    "orjson": [
        {
            "advisory": "orjson.loads in orjson before 3.9.15 does not limit recursion for deeply nested JSON documents.",
            "cve": "CVE-2024-27454",
            "id": "pyup.io-67584",
            "more_info_path": "/vulnerabilities/CVE-2024-27454/67584",
            "specs": [
                "<3.9.15"
            ],
            "v": "<3.9.15"
        },
        {
            "advisory": "Affected versions of the orjson package are vulnerable to Denial of Service (DoS) due to missing recursion depth limits during JSON serialization. The vulnerability is in orjson.dumps, which recursively serializes deeply nested JSON-like structures without enforcing a maximum nesting depth, allowing resource consumption to grow without bound.",
            "cve": "CVE-2025-67221",
            "id": "pyup.io-84963",
            "more_info_path": "/vulnerabilities/CVE-2025-67221/84963",
            "specs": [
                "<=3.11.4"
            ],
            "v": "<=3.11.4"
        }
    ],
    "ormagic": [
        {
            "advisory": "Ormagic fixes an SQL injection vulnerability in `models.py` by updating it to use parameterized queries.",
            "cve": "PVE-2024-72481",
            "id": "pyup.io-72481",
            "more_info_path": "/vulnerabilities/PVE-2024-72481/72481",
            "specs": [
                "<0.8.1"
            ],
            "v": "<0.8.1"
        }
    ],
    "ormar": [
        {
            "advisory": "Ormar 0.10.9 updates the 'pydantic' library to fix a security vulnerability (CVE-2021-29510).",
            "cve": "CVE-2021-29510",
            "id": "pyup.io-40577",
            "more_info_path": "/vulnerabilities/CVE-2021-29510/40577",
            "specs": [
                "<0.10.9"
            ],
            "v": "<0.10.9"
        }
    ],
    "ortec-scientific-benchmarks-loadbuilding": [
        {
            "advisory": "Ortec.scientific.benchmarks.loadbuilding 1.0.1 includes a security patch for the function 'safeFindRoot' in 'ortec/scientific/benchmarks/loadbuilding/solution/read/YAMLtoThreeDsolution.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/ORTECScientificBenchmarks/ortec-scientific-benchmarks-loadbuilding/commit/81b5f1ad38bc25ddf8ce1e988cb540a8d7f43482",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41355",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41355",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        },
        {
            "advisory": "Ortec.scientific.benchmarks.loadbuilding 1.0.1 and prior uses yaml.full_load(), which is vulnerable to CVE-2020-14343.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-41757",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/41757",
            "specs": [
                "<=1.0.1"
            ],
            "v": "<=1.0.1"
        }
    ],
    "osc": [
        {
            "advisory": "Osc 0.123 is the first release that performs SSL certificate checks to prevent man-in-the-middle-attacks. Python-m2crypto is needed to make this work. Certificate checks can be turned off per server via 'sslcertck = 0' in .oscrc.",
            "cve": "PVE-2021-37874",
            "id": "pyup.io-37874",
            "more_info_path": "/vulnerabilities/PVE-2021-37874/37874",
            "specs": [
                "<0.123"
            ],
            "v": "<0.123"
        },
        {
            "advisory": "Osc 0.134 includes a security fix for the buildlog function. Terminal control characters are limited now.",
            "cve": "PVE-2021-37873",
            "id": "pyup.io-37873",
            "more_info_path": "/vulnerabilities/PVE-2021-37873/37873",
            "specs": [
                "<0.134"
            ],
            "v": "<0.134"
        },
        {
            "advisory": "Osc 0.151 fixes shell command injection via crafted _service files. See: CVE-2015-0778.",
            "cve": "CVE-2015-0778",
            "id": "pyup.io-38486",
            "more_info_path": "/vulnerabilities/CVE-2015-0778/38486",
            "specs": [
                "<0.151"
            ],
            "v": "<0.151"
        },
        {
            "advisory": "Osc 0.161 fixes potential shell injections.\r\nhttps://github.com/openSUSE/osc/commit/c9c0f8a7317678ca61cc50cdda9b24bb00e96e29",
            "cve": "PVE-2022-45136",
            "id": "pyup.io-45136",
            "more_info_path": "/vulnerabilities/PVE-2022-45136/45136",
            "specs": [
                "<0.161"
            ],
            "v": "<0.161"
        },
        {
            "advisory": "Osc 0.165.3 fixes broken TLS certificate handling. See: CVE-2019-3685.",
            "cve": "CVE-2019-3685",
            "id": "pyup.io-38485",
            "more_info_path": "/vulnerabilities/CVE-2019-3685/38485",
            "specs": [
                "<0.165.3"
            ],
            "v": "<0.165.3"
        },
        {
            "advisory": "Osc 0.169.0 checks if the filename of a downloaded file has been modified (for example by a MITM attack) to contain slashes.\r\nhttps://github.com/openSUSE/osc/commit/a79c54418baf9b9785123bd07f350f12bd729ed3",
            "cve": "PVE-2022-45135",
            "id": "pyup.io-45135",
            "more_info_path": "/vulnerabilities/PVE-2022-45135/45135",
            "specs": [
                "<0.169.0"
            ],
            "v": "<0.169.0"
        }
    ],
    "osha-oira": [
        {
            "advisory": "Osha.oira 8.1.0 fixes XSS vulnerabilities in several views.",
            "cve": "PVE-2017-47673",
            "id": "pyup.io-47673",
            "more_info_path": "/vulnerabilities/PVE-2017-47673/47673",
            "specs": [
                "<8.1.0"
            ],
            "v": "<8.1.0"
        }
    ],
    "oslo-privsep": [
        {
            "advisory": "Oslo.privsep is vulnerable to CVE-2022-38065: A privilege escalation vulnerability exists in the oslo.privsep functionality of OpenStack git master 05194e7618 and prior. Overly permissive functionality within tools leveraging this library within a container can lead increased privileges.\r\nhttps://talosintelligence.com/vulnerability_reports/TALOS-2022-1599",
            "cve": "CVE-2022-38065",
            "id": "pyup.io-52526",
            "more_info_path": "/vulnerabilities/CVE-2022-38065/52526",
            "specs": [
                "<=3.1.0"
            ],
            "v": "<=3.1.0"
        }
    ],
    "oslo-utils": [
        {
            "advisory": "Oslo-utils 4.12.1 includes a fix for CVE-2022-0718: Due to improper parsing, passwords with a double quote ( \" ) in them cause incorrect masking in debug logs, causing any part of the password after the double quote to be plaintext.",
            "cve": "CVE-2022-0718",
            "id": "pyup.io-50849",
            "more_info_path": "/vulnerabilities/CVE-2022-0718/50849",
            "specs": [
                "<4.12.1"
            ],
            "v": "<4.12.1"
        }
    ],
    "oslo.middleware": [
        {
            "advisory": "Oslo.middleware before versions 3.8.1, 3.19.1, 3.23.1 is vulnerable to an information disclosure. Software using the CatchError class could include sensitive values in a traceback's error message. System users could exploit this flaw to obtain sensitive information from OpenStack component error logs (for example, keystone tokens).",
            "cve": "CVE-2017-2592",
            "id": "pyup.io-36207",
            "more_info_path": "/vulnerabilities/CVE-2017-2592/36207",
            "specs": [
                "<3.8.1",
                ">=3.9.0,<3.19.1",
                ">=3.20.0,<3.23.1"
            ],
            "v": "<3.8.1,>=3.9.0,<3.19.1,>=3.20.0,<3.23.1"
        }
    ],
    "oss-red-flag-checker": [
        {
            "advisory": "Version 0.1.5 of Oss-red-flag-checker updates the `cryptography` package from version 42.0.2 to 42.0.4 in response to CVE-2024-26130. This upgrade addresses specific vulnerabilities identified in the earlier version of `cryptography`.",
            "cve": "CVE-2024-26130",
            "id": "pyup.io-70865",
            "more_info_path": "/vulnerabilities/CVE-2024-26130/70865",
            "specs": [
                "<0.1.5"
            ],
            "v": "<0.1.5"
        },
        {
            "advisory": "Version 0.1.5 of Oss-red-flag-checker updates the `black` package from version 23.11.0 to 24.3.0 in response to CVE-2024-21503. This upgrade addresses specific vulnerabilities identified in the earlier version of `black`.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-70864",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/70864",
            "specs": [
                "<0.1.5"
            ],
            "v": "<0.1.5"
        }
    ],
    "ostorlab": [
        {
            "advisory": "Ostorlab version 1.0.5 updates its base image to python:3.10.14-alpine3.19 from python:3.9-bullseye to address vulnerabilities, enhancing the security and reliability of the docker environment.",
            "cve": "PVE-2024-67449",
            "id": "pyup.io-67449",
            "more_info_path": "/vulnerabilities/PVE-2024-67449/67449",
            "specs": [
                "<1.0.5"
            ],
            "v": "<1.0.5"
        },
        {
            "advisory": "Enhancement to vulnerability reporting functionality only Added stack trace information to vulnerability metadata protobuf message definition to improve debugging and tracking capabilities.",
            "cve": "PVE-2025-75640",
            "id": "pyup.io-75640",
            "more_info_path": "/vulnerabilities/PVE-2025-75640/75640",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        }
    ],
    "osxcollector": [
        {
            "advisory": "An issue was discovered in Yelp OSXCollector. A maliciously crafted Universal/fat binary can evade third-party code signing checks. By not completing full inspection of the Universal/fat binary, the user of the third-party tool will believe that the code is signed by Apple, but the malicious unsigned code will execute.",
            "cve": "CVE-2018-10406",
            "id": "pyup.io-53993",
            "more_info_path": "/vulnerabilities/CVE-2018-10406/53993",
            "specs": [
                ">=0,<1.10"
            ],
            "v": ">=0,<1.10"
        }
    ],
    "osxcollector-output-filters": [
        {
            "advisory": "Osxcollector-output-filters before 1.1.1 uses yaml.load() instead of yaml.safe_load(), allowing a code execution vulnerability.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41356",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41356",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "osxphotos": [
        {
            "advisory": "Osxphotos 0.51.8 updates its dependency 'mako' to v1.2.2 to include a security fix.",
            "cve": "CVE-2022-40023",
            "id": "pyup.io-51715",
            "more_info_path": "/vulnerabilities/CVE-2022-40023/51715",
            "specs": [
                "<0.51.8"
            ],
            "v": "<0.51.8"
        },
        {
            "advisory": "Osxphotos 0.51.8 updates its dev dependency 'mistune' to v2.0.3 to include a security fix.",
            "cve": "CVE-2022-34749",
            "id": "pyup.io-51773",
            "more_info_path": "/vulnerabilities/CVE-2022-34749/51773",
            "specs": [
                "<0.51.8"
            ],
            "v": "<0.51.8"
        },
        {
            "advisory": "Osxphotos 0.56.0 updates its dependency 'setuptools' to v65.5.1 to include a security fix.",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-52817",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/52817",
            "specs": [
                "<0.56.0"
            ],
            "v": "<0.56.0"
        }
    ],
    "otio-cdl-adapter": [
        {
            "advisory": "Otio-cdl-adapter 0.8 starts using 'secure_filename' function based on werkzeug's library to ensure filnames of exported CDL's are safe and valid.\r\nhttps://github.com/josh-mission/otio-cdl-adapter/commit/130597e2c7e53147a0e66f4a9bf8d90f5fbfb6e2",
            "cve": "PVE-2023-52770",
            "id": "pyup.io-52770",
            "more_info_path": "/vulnerabilities/PVE-2023-52770/52770",
            "specs": [
                "<0.8"
            ],
            "v": "<0.8"
        }
    ],
    "otpauth": [
        {
            "advisory": "otpauth before 1.0.1 is vulnerable to timing attacks.\r\nhttps://github.com/authlib/otpauth/commit/4186a22d7daa7685b09b6e70ad0eb6ff79439f2d",
            "cve": "PVE-2021-25915",
            "id": "pyup.io-25915",
            "more_info_path": "/vulnerabilities/PVE-2021-25915/25915",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        }
    ],
    "outbit": [
        {
            "advisory": "Outbit 0.0.6 changes SSL options to be secure by default.",
            "cve": "PVE-2017-47049",
            "id": "pyup.io-47049",
            "more_info_path": "/vulnerabilities/PVE-2017-47049/47049",
            "specs": [
                "<0.0.6"
            ],
            "v": "<0.0.6"
        }
    ],
    "outlines": [
        {
            "advisory": "Outlines 0.0.35 addresses a bug encountered during JSON generation with the FSM.next_state needing to handle a specific case, improving stability and functionality. This fix enhances how the final state is managed, ensuring smoother operation and data processing. \r\nhttps://github.com/outlines-dev/outlines/pull/718",
            "cve": "PVE-2024-66040",
            "id": "pyup.io-66040",
            "more_info_path": "/vulnerabilities/PVE-2024-66040/66040",
            "specs": [
                "<0.0.35"
            ],
            "v": "<0.0.35"
        }
    ],
    "ovirt-engine-sdk-python": [
        {
            "advisory": "The python SDK before 3.1.0.6 and CLI before 3.1.0.8 for oVirt 3.1 does not check the server SSL certificate against the client keys, which allows remote attackers to spoof a server via a man-in-the-middle (MITM) attack.",
            "cve": "CVE-2012-3533",
            "id": "pyup.io-25916",
            "more_info_path": "/vulnerabilities/CVE-2012-3533/25916",
            "specs": [
                "<3.1.0.8"
            ],
            "v": "<3.1.0.8"
        },
        {
            "advisory": "ovirt-engine-sdk-python before 3.4.0.7 and 3.5.0.4 does not verify that the hostname of the remote endpoint matches the Common Name (CN) or subjectAltName as specified by its x.509 certificate in a TLS/SSL session. This could allow man-in-the-middle attackers to spoof remote endpoints via an arbitrary valid certificate.",
            "cve": "CVE-2014-0161",
            "id": "pyup.io-37754",
            "more_info_path": "/vulnerabilities/CVE-2014-0161/37754",
            "specs": [
                "<3.4.0.7",
                "==3.5.0.4"
            ],
            "v": "<3.4.0.7,==3.5.0.4"
        },
        {
            "advisory": "The REST API in overt 3.4.0 and earlier stores session IDs in HTML5 local storage, which allows remote attackers to obtain sensitive information via a crafted web page.",
            "cve": "CVE-2014-0153",
            "id": "pyup.io-67963",
            "more_info_path": "/vulnerabilities/CVE-2014-0153/67963",
            "specs": [
                "<=3.4.0"
            ],
            "v": "<=3.4.0"
        },
        {
            "advisory": "Session fixation vulnerability in the web admin interface in oVirt 3.4.0 and earlier allows remote attackers to hijack web sessions via unspecified vectors.",
            "cve": "CVE-2014-0152",
            "id": "pyup.io-70433",
            "more_info_path": "/vulnerabilities/CVE-2014-0152/70433",
            "specs": [
                "<=3.4.0"
            ],
            "v": "<=3.4.0"
        },
        {
            "advisory": "oVirt Engine before 4.0.3 does not include DWH_DB_PASSWORD in the list of keys to hide in log files, which allows local users to obtain sensitive password information by reading engine log files.",
            "cve": "CVE-2016-6341",
            "id": "pyup.io-70526",
            "more_info_path": "/vulnerabilities/CVE-2016-6341/70526",
            "specs": [
                "<=4.0.2"
            ],
            "v": "<=4.0.2"
        }
    ],
    "ovs": [
        {
            "advisory": "ovs 1.3.0 includes a fix that flow setups are now processed in a round-robin manner across ports to prevent any single client from monopolizing the CPU and conducting a denial of service attack.\r\nhttps://github.com/openvswitch/ovs/commit/17411ecf2b4d02cfced5f69e567c17673d7d4462",
            "cve": "PVE-2021-25917",
            "id": "pyup.io-25917",
            "more_info_path": "/vulnerabilities/PVE-2021-25917/25917",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "In lib/conntrack.c in the firewall implementation in Open vSwitch (OvS) 2.6.1, there is a buffer over-read while parsing malformed TCP, UDP, and IPv6 packets in the functions `extract_l3_ipv6`, `extract_l4_tcp`, and `extract_l4_udp` that can be triggered remotely.",
            "cve": "CVE-2017-9264",
            "id": "pyup.io-65812",
            "more_info_path": "/vulnerabilities/CVE-2017-9264/65812",
            "specs": [
                "<2.6.2"
            ],
            "v": "<2.6.2"
        },
        {
            "advisory": "In Open vSwitch (OvS) 2.7.0, while parsing an OFPT_QUEUE_GET_CONFIG_REPLY type OFP 1.0 message, there is a buffer over-read that is caused by an unsigned integer underflow in the function `ofputil_pull_queue_get_config_reply10` in `lib/ofp-util.c`.",
            "cve": "CVE-2017-9214",
            "id": "pyup.io-66669",
            "more_info_path": "/vulnerabilities/CVE-2017-9214/66669",
            "specs": [
                "<2.7.1"
            ],
            "v": "<2.7.1"
        },
        {
            "advisory": "In Open vSwitch (OvS) v2.7.0, there is a buffer over-read while parsing the group mod OpenFlow message sent from the controller in `lib/ofp-util.c` in the function `ofputil_pull_ofp15_group_mod`.",
            "cve": "CVE-2017-9265",
            "id": "pyup.io-65813",
            "more_info_path": "/vulnerabilities/CVE-2017-9265/65813",
            "specs": [
                "<2.7.2"
            ],
            "v": "<2.7.2"
        }
    ],
    "owlmixin": [
        {
            "advisory": "An exploitable vulnerability exists in the YAML loading functionality of util.py in OwlMixin before 2.0.0a12. A \"Load YAML\" string or file (aka load_yaml or load_yamlf) can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.",
            "cve": "CVE-2017-16618",
            "id": "pyup.io-35720",
            "more_info_path": "/vulnerabilities/CVE-2017-16618/35720",
            "specs": [
                "<2.0.0a12"
            ],
            "v": "<2.0.0a12"
        },
        {
            "advisory": "Owlmixin 6.1.1 updates its dependency 'urlllib3' to include a security fix.",
            "cve": "CVE-2023-43804",
            "id": "pyup.io-61904",
            "more_info_path": "/vulnerabilities/CVE-2023-43804/61904",
            "specs": [
                "<6.1.1"
            ],
            "v": "<6.1.1"
        },
        {
            "advisory": "Owlmixin 6.1.1 updates its dependency 'urlllib3' to include a security fix.",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-61922",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/61922",
            "specs": [
                "<6.1.1"
            ],
            "v": "<6.1.1"
        }
    ],
    "owlmoon": [
        {
            "advisory": "Owlmoon is a malicious package, typosquatting.  It steals Discord access tokens, passwords, and even stage dependency confusion attacks.\r\nhttps://thehackernews.com/2021/11/11-malicious-pypi-python-libraries.html",
            "cve": "PVE-2022-45458",
            "id": "pyup.io-45458",
            "more_info_path": "/vulnerabilities/PVE-2022-45458/45458",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "owslib": [
        {
            "advisory": "OWSLib is a Python package for client programming with Open Geospatial Consortium (OGC) web service interface standards, and their related content models. OWSLib's XML parser (which supports both 'lxml' and 'xml.etree') does not disable entity resolution, and could lead to arbitrary file reads from an attacker-controlled XML payload. This affects all XML parsing in the codebase. This issue has been addressed in version 0.28.1. The only known workaround is to patch the library manually. See 'GHSA-8h9c-r582-mggc' for details.",
            "cve": "CVE-2023-27476",
            "id": "pyup.io-53676",
            "more_info_path": "/vulnerabilities/CVE-2023-27476/53676",
            "specs": [
                "<0.28.1"
            ],
            "v": "<0.28.1"
        },
        {
            "advisory": "An XML external entity (XXE) injection in PyWPS before 4.4.5 allows an attacker to view files on the application server filesystem by assigning a path to the entity. OWSLib 0.24.1 may also be affected.",
            "cve": "CVE-2021-39371",
            "id": "pyup.io-41213",
            "more_info_path": "/vulnerabilities/CVE-2021-39371/41213",
            "specs": [
                "==0.24.1"
            ],
            "v": "==0.24.1"
        }
    ],
    "oxl-ansible-webui": [
        {
            "advisory": "A Cross-Site Scripting (XSS) vulnerability has been identified in the AnsibleGuy WebUI project. The vulnerability allows an attacker to inject arbitrary JavaScript code through user-supplied regex patterns. This injected code could be executed in the context of other users' browsers, potentially leading to session hijacking, theft of sensitive information, or other malicious actions. The vulnerability stems from insufficient input sanitization when handling and displaying regex patterns. The commit fix partially addresses this vulnerability by introducing escaping mechanisms and input validation",
            "cve": "PVE-2024-73191",
            "id": "pyup.io-73191",
            "more_info_path": "/vulnerabilities/PVE-2024-73191/73191",
            "specs": [
                "<0.0.23"
            ],
            "v": "<0.0.23"
        }
    ],
    "ozi": [
        {
            "advisory": "Ozi version 0.0.302 updates its dependency on Black to version 24.3 or higher. This adjustment is made to address the ReDoS (Regular Expression Denial of Service) vulnerability identified in CVE-2024-21503.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-67005",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/67005",
            "specs": [
                "<0.0.302"
            ],
            "v": "<0.0.302"
        }
    ],
    "packstack": [
        {
            "advisory": "Packstack 2012.2.3 includes a fix for CVE-2013-0261: (1) installer/basedefs.py and (2) modules/ospluginutils.py in PackStack allows local users to overwrite arbitrary files via a symlink attack on a temporary file with a predictable name in /tmp.\r\nhttps://opendev.org/x/packstack/commit/624d49a0e8305e6613a9637437f7cdfb8a7852e9",
            "cve": "CVE-2013-0261",
            "id": "pyup.io-52947",
            "more_info_path": "/vulnerabilities/CVE-2013-0261/52947",
            "specs": [
                ">=2011.12.0,<2012.2.3"
            ],
            "v": ">=2011.12.0,<2012.2.3"
        }
    ],
    "pacparser": [
        {
            "advisory": "Pacparser 1.4.0 fixes a possible memory overwrite vulnerability.\r\nhttps://github.com/manugarg/pacparser/commit/853e8f45607cb07b877ffd270c63dbcdd5201ad9",
            "cve": "PVE-2022-48279",
            "id": "pyup.io-48279",
            "more_info_path": "/vulnerabilities/PVE-2022-48279/48279",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "A vulnerability classified as problematic was found in pacparser up to 1.3.x. Affected by this vulnerability is the function pacparser_find_proxy of the file src/pacparser.c. The manipulation of the argument url leads to buffer overflow. Attacking locally is a requirement. Upgrading to version 1.4.0 is able to address this issue. The name of the patch is 853e8f45607cb07b877ffd270c63dbcdd5201ad9. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-215443.",
            "cve": "CVE-2019-25078",
            "id": "pyup.io-70777",
            "more_info_path": "/vulnerabilities/CVE-2019-25078/70777",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Pacparser 1.4.2 fixes a vulnerability: JavaScript Injection in pacparser_find_proxy().\r\nhttps://github.com/manugarg/pacparser/security/advisories/GHSA-62q6-v997-f7v9",
            "cve": "PVE-2023-58807",
            "id": "pyup.io-58807",
            "more_info_path": "/vulnerabilities/PVE-2023-58807/58807",
            "specs": [
                "<1.4.2"
            ],
            "v": "<1.4.2"
        },
        {
            "advisory": "pacparser_find_proxy in Pacparser before 1.4.2 allows JavaScript injection, and possibly privilege escalation, when the attacker controls the URL (which may be realistic within enterprise security products).",
            "cve": "CVE-2023-37360",
            "id": "pyup.io-64689",
            "more_info_path": "/vulnerabilities/CVE-2023-37360/64689",
            "specs": [
                "<1.4.2"
            ],
            "v": "<1.4.2"
        }
    ],
    "pact-python": [
        {
            "advisory": "Pact-python 1.3.6 includes several vulnerability fixes for Dockerfile(s).",
            "cve": "PVE-2021-40235",
            "id": "pyup.io-40235",
            "more_info_path": "/vulnerabilities/PVE-2021-40235/40235",
            "specs": [
                "<1.3.6"
            ],
            "v": "<1.3.6"
        },
        {
            "advisory": "Pact-python 1.3.7 includes important fixes for Dockerfiles (py37.Dockerfile, py38.Dockerfile, py36.Dockerfile) to reduce vulnerabilities.",
            "cve": "PVE-2021-40324",
            "id": "pyup.io-40324",
            "more_info_path": "/vulnerabilities/PVE-2021-40324/40324",
            "specs": [
                "<1.3.7"
            ],
            "v": "<1.3.7"
        },
        {
            "advisory": "Pact-python 1.7.0 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.",
            "cve": "CVE-2007-4559",
            "id": "pyup.io-53381",
            "more_info_path": "/vulnerabilities/CVE-2007-4559/53381",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Pact-python 1.7.0 updates its dependency 'wheel' to v0.38.0 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-53382",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/53382",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        }
    ],
    "pacyam": [
        {
            "advisory": "Pacyam 1.1.1 includes a security patch for the function '_yaml_block_to_dict' in 'pacyam/pacyam.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/dstarner/pacyam/commit/0640b259c0e5909c1010b6780e10b88f8fdd1c17#diff-8b9ae2192ea7474817342a2e0d103b63f28618bd1e495bc8227f711757ea91eb",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41358",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41358",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "paddlepaddle": [
        {
            "advisory": "Null pointer dereference in paddle.flip in PaddlePaddle before 2.5.0. This resulted in a runtime crash and denial of service.",
            "cve": "CVE-2023-38670",
            "id": "pyup.io-65043",
            "more_info_path": "/vulnerabilities/CVE-2023-38670/65043",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "PaddlePaddle before 2.5.0 has a command injection in fs.py. This resulted in\u00a0the ability to execute arbitrary commands on the operating system.",
            "cve": "CVE-2023-38673",
            "id": "pyup.io-65046",
            "more_info_path": "/vulnerabilities/CVE-2023-38673/65046",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "FPE in paddle.trace in PaddlePaddle before 2.5.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-38672",
            "id": "pyup.io-65045",
            "more_info_path": "/vulnerabilities/CVE-2023-38672/65045",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Use after free in paddle.diagonal in PaddlePaddle before 2.5.0. This resulted in a potentially exploitable condition.",
            "cve": "CVE-2023-38669",
            "id": "pyup.io-65042",
            "more_info_path": "/vulnerabilities/CVE-2023-38669/65042",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Heap buffer overflow in paddle.trace in PaddlePaddle before 2.5.0. This flaw can lead to a denial of service, information disclosure, or more damage is possible.",
            "cve": "CVE-2023-38671",
            "id": "pyup.io-65044",
            "more_info_path": "/vulnerabilities/CVE-2023-38671/65044",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "FPE in paddle.topk\u00a0in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-52305",
            "id": "pyup.io-70388",
            "more_info_path": "/vulnerabilities/CVE-2023-52305/70388",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "FPE in paddle.argmin and paddle.argmax\u00a0in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-52313",
            "id": "pyup.io-70383",
            "more_info_path": "/vulnerabilities/CVE-2023-52313/70383",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "FPE in paddle.nanmedian in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-38674",
            "id": "pyup.io-70395",
            "more_info_path": "/vulnerabilities/CVE-2023-38674/70395",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Nullptr in paddle.put_along_axis\u00a0in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-52303",
            "id": "pyup.io-70390",
            "more_info_path": "/vulnerabilities/CVE-2023-52303/70390",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Stack overflow in paddle.searchsorted\u00a0in PaddlePaddle before 2.6.0. This flaw can lead to a denial of service, or even more damage.",
            "cve": "CVE-2023-52304",
            "id": "pyup.io-70389",
            "more_info_path": "/vulnerabilities/CVE-2023-52304/70389",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "FPE in paddle.amin\u00a0in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-52308",
            "id": "pyup.io-70386",
            "more_info_path": "/vulnerabilities/CVE-2023-52308/70386",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "FPE in paddle.linalg.eig in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-38677",
            "id": "pyup.io-70393",
            "more_info_path": "/vulnerabilities/CVE-2023-38677/70393",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "PaddlePaddle/Paddle before 2.6.0 is susceptible to a code injection vulnerability that permits an attacker to execute arbitrary commands on the host system.",
            "cve": "CVE-2024-0521",
            "id": "pyup.io-66716",
            "more_info_path": "/vulnerabilities/CVE-2024-0521/66716",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Heap buffer overflow in paddle.repeat_interleave\u00a0in PaddlePaddle before 2.6.0. This flaw can lead to a denial of service, information disclosure, or more damage is possible.",
            "cve": "CVE-2023-52309",
            "id": "pyup.io-70385",
            "more_info_path": "/vulnerabilities/CVE-2023-52309/70385",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Nullptr dereference in paddle.crop\u00a0in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-52312",
            "id": "pyup.io-70384",
            "more_info_path": "/vulnerabilities/CVE-2023-52312/70384",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "OOB access in paddle.mode\u00a0in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-38678",
            "id": "pyup.io-70392",
            "more_info_path": "/vulnerabilities/CVE-2023-38678/70392",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Nullptr in paddle.dot\u00a0in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-38676",
            "id": "pyup.io-70394",
            "more_info_path": "/vulnerabilities/CVE-2023-38676/70394",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "FPE in paddle.lerp\u00a0in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-52306",
            "id": "pyup.io-70387",
            "more_info_path": "/vulnerabilities/CVE-2023-52306/70387",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Nullptr in paddle.nextafter\u00a0in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-52302",
            "id": "pyup.io-70391",
            "more_info_path": "/vulnerabilities/CVE-2023-52302/70391",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Command injection in IrGraph.draw in paddlepaddle/paddle affected versions.",
            "cve": "CVE-2024-0817",
            "id": "pyup.io-71835",
            "more_info_path": "/vulnerabilities/CVE-2024-0817/71835",
            "specs": [
                "<=2.6.0"
            ],
            "v": "<=2.6.0"
        },
        {
            "advisory": "Command injection in paddle.utils.download._wget_download (bypass filter) in paddlepaddle/paddle affected versions.",
            "cve": "CVE-2024-0815",
            "id": "pyup.io-71833",
            "more_info_path": "/vulnerabilities/CVE-2024-0815/71833",
            "specs": [
                "<=2.6.0"
            ],
            "v": "<=2.6.0"
        },
        {
            "advisory": "Remote code execution in paddlepaddle/paddle affected versions.",
            "cve": "CVE-2024-0917",
            "id": "pyup.io-71834",
            "more_info_path": "/vulnerabilities/CVE-2024-0917/71834",
            "specs": [
                "<=2.6.0"
            ],
            "v": "<=2.6.0"
        },
        {
            "advisory": "Arbitrary File Overwrite Via Path Traversal in paddlepaddle/paddle affected versions.",
            "cve": "CVE-2024-0818",
            "id": "pyup.io-71832",
            "more_info_path": "/vulnerabilities/CVE-2024-0818/71832",
            "specs": [
                "<=2.6.0"
            ],
            "v": "<=2.6.0"
        },
        {
            "advisory": "paddlepaddle/paddle affected versions allow arbitrary file read via paddle.vision.ops.read_file.",
            "cve": "CVE-2024-1603",
            "id": "pyup.io-71831",
            "more_info_path": "/vulnerabilities/CVE-2024-1603/71831",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        },
        {
            "advisory": "FPE in paddle.linalg.matrix_rank in PaddlePaddle before 2.6.0. This flaw can cause a runtime crash and a denial of service.",
            "cve": "CVE-2023-38675",
            "id": "pyup.io-65094",
            "more_info_path": "/vulnerabilities/CVE-2023-38675/65094",
            "specs": [
                ">=0,<2.6.0"
            ],
            "v": ">=0,<2.6.0"
        },
        {
            "advisory": "Stack overflow in paddle.linalg.lu_unpack\u00a0in PaddlePaddle before 2.6.0. This flaw can lead to a denial of service, or even more damage.",
            "cve": "CVE-2023-52307",
            "id": "pyup.io-65203",
            "more_info_path": "/vulnerabilities/CVE-2023-52307/65203",
            "specs": [
                ">=0,<2.6.0"
            ],
            "v": ">=0,<2.6.0"
        },
        {
            "advisory": "PaddlePaddle before 2.6.0 has a command injection in convert_shape_compare. This resulted in the ability to execute arbitrary commands on the operating system.",
            "cve": "CVE-2023-52314",
            "id": "pyup.io-65206",
            "more_info_path": "/vulnerabilities/CVE-2023-52314/65206",
            "specs": [
                ">=0,<2.6.0"
            ],
            "v": ">=0,<2.6.0"
        },
        {
            "advisory": "PaddlePaddle before 2.6.0 has a command injection in get_online_pass_interval. This resulted in the ability to execute arbitrary commands on the operating system.",
            "cve": "CVE-2023-52310",
            "id": "pyup.io-65204",
            "more_info_path": "/vulnerabilities/CVE-2023-52310/65204",
            "specs": [
                ">=0,<2.6.0"
            ],
            "v": ">=0,<2.6.0"
        },
        {
            "advisory": "PaddlePaddle before 2.6.0 has a command injection in _wget_download. This resulted in the ability to execute arbitrary commands on the operating system.",
            "cve": "CVE-2023-52311",
            "id": "pyup.io-65205",
            "more_info_path": "/vulnerabilities/CVE-2023-52311/65205",
            "specs": [
                ">=0,<2.6.0"
            ],
            "v": ">=0,<2.6.0"
        },
        {
            "advisory": "Out-of-bounds read in `gather_tree` in PaddlePaddle before 2.4. A [patch](https://github.com/PaddlePaddle/Paddle/commit/6712e262fc6734873cc6d5ca4f45973339a88697) is available in the `release/2.4` branch.",
            "cve": "CVE-2022-46741",
            "id": "pyup.io-54596",
            "more_info_path": "/vulnerabilities/CVE-2022-46741/54596",
            "specs": [
                ">=1.7.0.post97,<2.4.0"
            ],
            "v": ">=1.7.0.post97,<2.4.0"
        },
        {
            "advisory": "In PaddlePaddle before 2.4, paddle.audio.functional.get_window is vulnerable to code injection because it calls eval on a user-supplied winstr. This may lead to arbitrary code execution.",
            "cve": "CVE-2022-45908",
            "id": "pyup.io-54583",
            "more_info_path": "/vulnerabilities/CVE-2022-45908/54583",
            "specs": [
                ">=1.7.0.post97,<2.4.0"
            ],
            "v": ">=1.7.0.post97,<2.4.0"
        },
        {
            "advisory": "Code injection in `paddle.audio.functional.get_window` in PaddlePaddle 2.4.0-rc0 allows arbitrary code execution. A [patch](https://github.com/PaddlePaddle/Paddle/commit/26c419ca386aeae3c461faf2b828d00b48e908eb) is available on the `develop` branch of the repository and anticipated to be part of a 2.4 release.",
            "cve": "CVE-2022-46742",
            "id": "pyup.io-54595",
            "more_info_path": "/vulnerabilities/CVE-2022-46742/54595",
            "specs": [
                ">=2.4.0rc0,<2.4.0"
            ],
            "v": ">=2.4.0rc0,<2.4.0"
        }
    ],
    "pag": [
        {
            "advisory": "Pag 0.8 and prior versions use yaml.load() together with untrusted input, which could lead to malicious code execution.\r\nhttps://pagure.io/pag/blob/24fd8723a3685f175f656e8c37473fc85ed98ddf/f/pag/utils.py#_134",
            "cve": "PVE-2020-47192",
            "id": "pyup.io-47192",
            "more_info_path": "/vulnerabilities/PVE-2020-47192/47192",
            "specs": [
                "<=0.8"
            ],
            "v": "<=0.8"
        }
    ],
    "paho-mqtt": [
        {
            "advisory": "Paho-mqtt version 1.0.2 addresses a potential race condition that could occur when initiating a TLS connection and publishing simultaneously. This fix ensures that PUBLISH data is not sent prematurely and unencrypted, maintaining the intended message order and encryption for security.\r\nhttps://github.com/eclipse/paho.mqtt.python/commit/4643ecaf54f293ac2913b66d35b5e082d7a2a344",
            "cve": "PVE-2024-65106",
            "id": "pyup.io-65106",
            "more_info_path": "/vulnerabilities/PVE-2024-65106/65106",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "pain001": [
        {
            "advisory": "Affected versions of this package are vulnerable to SQL Injection. The `load_db_data.py` module fails to properly quote SQL identifiers (table and column names) in database queries, leading to SQL injection attacks when user-controlled values are used as table or column names, enabling arbitrary SQL command execution.",
            "cve": "PVE-2026-84167",
            "id": "pyup.io-84167",
            "more_info_path": "/vulnerabilities/PVE-2026-84167/84167",
            "specs": [
                "<0.0.26"
            ],
            "v": "<0.0.26"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to XML External Entity (XXE) attacks due to the use of unsafe XML parsing methods. The package uses `xml.etree.ElementTree` for XML creation and validation, which is susceptible to XXE attacks, XML bomb attacks, and other XML-based vulnerabilities. An attacker can exploit this vulnerability by crafting malicious XML data that, when processed by the application, could lead to unauthorized access to sensitive data or Denial of Service (DoS).",
            "cve": "PVE-2026-84131",
            "id": "pyup.io-84131",
            "more_info_path": "/vulnerabilities/PVE-2026-84131/84131",
            "specs": [
                "<0.0.26"
            ],
            "v": "<0.0.26"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to XML External Entity (XXE) Injection. The application uses xml.etree.ElementTree for XML parsing operations without disabling external entity processing, leading to XXE attacks, XML bomb denial of service, and unauthorized DTD retrieval when processing untrusted XML input. An attacker can exploit this vulnerability by submitting crafted XML documents containing external entity declarations that reference local files (e.g., file:///etc/passwd), remote URLs for SSRF attacks, or recursive entity definitions (billion laughs attack) that cause resource exhaustion, enabling information disclosure, server-side request forgery, or denial of service.",
            "cve": "PVE-2026-84194",
            "id": "pyup.io-84194",
            "more_info_path": "/vulnerabilities/PVE-2026-84194/84194",
            "specs": [
                "<0.0.31"
            ],
            "v": "<0.0.31"
        }
    ],
    "pakettikauppa": [
        {
            "advisory": "pakettikauppa 0.1.2 fixes Pip files and requirement files for fixing security issue in pyyaml module",
            "cve": "PVE-2021-36779",
            "id": "pyup.io-36779",
            "more_info_path": "/vulnerabilities/PVE-2021-36779/36779",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        },
        {
            "advisory": "Pakettikauppa 0.1.4 updates its dependency 'jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-45146",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/45146",
            "specs": [
                "<0.1.4"
            ],
            "v": "<0.1.4"
        },
        {
            "advisory": "Pakettikauppa 0.1.5 updates its dependency 'urllib3' to v1.24.2 to include a security fix. To get latest version, install from source: https://github.com/vilkasgroup/Pakettikauppa/blob/master/docs/installation.rst",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-45145",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/45145",
            "specs": [
                "<0.1.5"
            ],
            "v": "<0.1.5"
        }
    ],
    "palladium": [
        {
            "advisory": "Palladium 1.2.2 updates its dependency 'SQLAlchemy' to v1.3.6 to include a security fix.",
            "cve": "CVE-2019-7164",
            "id": "pyup.io-44629",
            "more_info_path": "/vulnerabilities/CVE-2019-7164/44629",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Palladium 1.2.2 updates its dependency 'jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-37378",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/37378",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Palladium 1.2.2 updates its dependency 'urllib3' to v1.25.3 to include security fixes.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-44631",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/44631",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Palladium 1.2.2 updates its dependency 'Werkzeug' to v0.15.5 to include a security fix.",
            "cve": "CVE-2019-14806",
            "id": "pyup.io-44633",
            "more_info_path": "/vulnerabilities/CVE-2019-14806/44633",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Palladium 1.2.2 updates its dependency 'SQLAlchemy' to v1.3.6 to include a security fix.",
            "cve": "CVE-2019-7548",
            "id": "pyup.io-44630",
            "more_info_path": "/vulnerabilities/CVE-2019-7548/44630",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Palladium 1.2.2 updates its dependency 'urllib3' to v1.25.3 to include security fixes.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-44632",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/44632",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Palladium 1.2.2 updates its dependency 'numpy' to v1.17.0 to include a security fix.",
            "cve": "CVE-2019-6446",
            "id": "pyup.io-44628",
            "more_info_path": "/vulnerabilities/CVE-2019-6446/44628",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "Palladium 1.2.3 updates its dependency 'urllib3' to v1.25.9 to include security fixes.",
            "cve": "CVE-2020-7212",
            "id": "pyup.io-45774",
            "more_info_path": "/vulnerabilities/CVE-2020-7212/45774",
            "specs": [
                "<1.2.3"
            ],
            "v": "<1.2.3"
        },
        {
            "advisory": "Palladium 1.2.3 updates its dependency 'urllib3' to v1.25.9 to include security fixes.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-45773",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/45773",
            "specs": [
                "<1.2.3"
            ],
            "v": "<1.2.3"
        },
        {
            "advisory": "Palladium 1.2.3 updates its dependency 'psutil' to v5.7.0 to include a security fix.",
            "cve": "CVE-2019-18874",
            "id": "pyup.io-38263",
            "more_info_path": "/vulnerabilities/CVE-2019-18874/38263",
            "specs": [
                "<1.2.3"
            ],
            "v": "<1.2.3"
        }
    ],
    "palm": [
        {
            "advisory": "Palm 2.4.1 fixes a potential security vulnerability when upgrading plugins via 'palm plugin update'.\r\nhttps://github.com/palmetto/palm-cli/commit/00da09251c2c4a80d7c908cbd60ac2ac536cca56",
            "cve": "PVE-2022-49339",
            "id": "pyup.io-49339",
            "more_info_path": "/vulnerabilities/PVE-2022-49339/49339",
            "specs": [
                "<2.4.1"
            ],
            "v": "<2.4.1"
        }
    ],
    "panda3d": [
        {
            "advisory": "Panda3d 1.9.3 fixes a race condition that could occur when multiple threads accessed and modified the '_cow_object' simultaneously. Without this fix, the '_cow_object' could become corrupted or the application could crash.\r\nhttps://github.com/panda3d/panda3d/commit/632ad5e3eff9a00503d964231fa5be68f0ee92a9",
            "cve": "PVE-2024-63331",
            "id": "pyup.io-63331",
            "more_info_path": "/vulnerabilities/PVE-2024-63331/63331",
            "specs": [
                "<1.9.3"
            ],
            "v": "<1.9.3"
        },
        {
            "advisory": "Panda3d 1.9.3 addresses a race condition that could lead to inconsistent data in the cache during concurrent operations, and potentially cause bugs or crashes in the software.\r\nhttps://github.com/panda3d/panda3d/commit/69f15258e4394f8df680f4a6a71de2cbca7bf770",
            "cve": "PVE-2024-63309",
            "id": "pyup.io-63309",
            "more_info_path": "/vulnerabilities/PVE-2024-63309/63309",
            "specs": [
                "<1.9.3"
            ],
            "v": "<1.9.3"
        }
    ],
    "pandas": [
        {
            "advisory": "Prior to version v0.16.0rc1, Pandas had a SQL injection vulnerability that could let attackers carry out any SQL commands they wished.",
            "cve": "PVE-2023-99975",
            "id": "pyup.io-60833",
            "more_info_path": "/vulnerabilities/PVE-2023-99975/60833",
            "specs": [
                "<0.16.0rc1"
            ],
            "v": "<0.16.0rc1"
        }
    ],
    "pandas-zmq": [
        {
            "advisory": "Pandas-zmq 0.0.2 adds a signature to reduce the risk of code injection.\r\nhttps://github.com/rritoch/pandas_zmq/commit/5d61bdde3788931838a8bd7a5a872c4fdd7e01bb",
            "cve": "PVE-2021-38627",
            "id": "pyup.io-38627",
            "more_info_path": "/vulnerabilities/PVE-2021-38627/38627",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        }
    ],
    "pandasai": [
        {
            "advisory": "Pandasai 0.8.1 includes a fix for a Prompt Injection vulnerability.\r\nhttps://github.com/gventuri/pandas-ai/pull/409\r\nhttps://github.com/gventuri/pandas-ai/issues/399",
            "cve": "PVE-2023-60066",
            "id": "pyup.io-60066",
            "more_info_path": "/vulnerabilities/PVE-2023-60066/60066",
            "specs": [
                "<0.8.1"
            ],
            "v": "<0.8.1"
        },
        {
            "advisory": "Affected versions of PandasAI are vulnerable to an Incomplete List of Disallowed Inputs (CWE-184). This vulnerability could allow attackers to bypass security checks and potentially execute arbitrary code or access system resources. The vulnerability exists in the check_malicious_keywords_in_query method of the BaseAgent class, which used an overly simplistic string matching approach to detect malicious keywords. An attacker could exploit this by obfuscating or creatively formatting malicious input to evade detection. To remediate, update to the version which implements a more robust regular expression-based detection method. This vulnerability affects Python implementations of PandasAI.",
            "cve": "PVE-2024-73379",
            "id": "pyup.io-73379",
            "more_info_path": "/vulnerabilities/PVE-2024-73379/73379",
            "specs": [
                "<2.2.15"
            ],
            "v": "<2.2.15"
        },
        {
            "advisory": "PandasAI uses an interactive prompt function that is vulnerable to prompt injection and run arbitrary Python code that can lead to Remote Code Execution (RCE) instead of the intended explanation of the natural language processing by the LLM. The security controls of PandasAI (2.4.3 and earlier) fail to distinguish between legitimate and malicious inputs, allowing the attackers to manipulate the system into executing untrusted code, leading to untrusted code execution (RCE), system compromise, or pivoting attacks on connected services.",
            "cve": "CVE-2024-12366",
            "id": "pyup.io-76338",
            "more_info_path": "/vulnerabilities/CVE-2024-12366/76338",
            "specs": [
                "<2.4.2"
            ],
            "v": "<2.4.2"
        },
        {
            "advisory": "GenerateSDFPipeline in synthetic_dataframe in PandasAI (aka pandas-ai) through 1.5.17 allows attackers to trigger the generation of arbitrary Python code that is executed by SDFCodeExecutor. An attacker can create a dataframe that provides an English language specification of this Python code. \r\nNOTE: the vendor previously attempted to restrict code execution in response to a separate issue, CVE-2023-39660. See CVE-2024-23752.",
            "cve": "CVE-2024-23752",
            "id": "pyup.io-64460",
            "more_info_path": "/vulnerabilities/CVE-2024-23752/64460",
            "specs": [
                "<=1.5.17"
            ],
            "v": "<=1.5.17"
        },
        {
            "advisory": "An issue in Gaberiele Venturi pandasai v.0.8.0 and before allows a remote attacker to execute arbitrary code via a crafted request to the prompt function.",
            "cve": "CVE-2023-39660",
            "id": "pyup.io-65037",
            "more_info_path": "/vulnerabilities/CVE-2023-39660/65037",
            "specs": [
                ">=0,<0.8.1"
            ],
            "v": ">=0,<0.8.1"
        },
        {
            "advisory": "An issue in pandas-ai v.0.9.1 and before allows a remote attacker to execute arbitrary code via the _is_jailbreak function.",
            "cve": "CVE-2023-39661",
            "id": "pyup.io-65038",
            "more_info_path": "/vulnerabilities/CVE-2023-39661/65038",
            "specs": [
                ">=0,<=0.8.1"
            ],
            "v": ">=0,<=0.8.1"
        }
    ],
    "pandevice": [
        {
            "advisory": "Pandevice 0.11.0 adds `uuid` params for security and NAT rules.",
            "cve": "PVE-2021-37198",
            "id": "pyup.io-37198",
            "more_info_path": "/vulnerabilities/PVE-2021-37198/37198",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "pando": [
        {
            "advisory": "Pando before 0.26 is vulnerable to CRLF injection.\r\nhttps://github.com/AspenWeb/pando.py/commit/ab126d323e0784a75f084e6683e89ae457bccd5a",
            "cve": "PVE-2021-25918",
            "id": "pyup.io-25918",
            "more_info_path": "/vulnerabilities/PVE-2021-25918/25918",
            "specs": [
                "<0.26"
            ],
            "v": "<0.26"
        },
        {
            "advisory": "pando before 0.42 is vulnerable to URL redirection attacks.",
            "cve": "PVE-2021-25919",
            "id": "pyup.io-25919",
            "more_info_path": "/vulnerabilities/PVE-2021-25919/25919",
            "specs": [
                "<0.42"
            ],
            "v": "<0.42"
        }
    ],
    "panel": [
        {
            "advisory": "Panel 0.12.0 includes a fix for a Race Condition vulnerability in the autoreload argument.\r\nhttps://github.com/holoviz/panel/issues/2531\r\nhttps://github.com/holoviz/panel/pull/2539",
            "cve": "PVE-2023-59597",
            "id": "pyup.io-59597",
            "more_info_path": "/vulnerabilities/PVE-2023-59597/59597",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        },
        {
            "advisory": "Panel 1.3.7 updates its NPM dependency 'Plotly.js' to 2.25.3 to include a security fix.",
            "cve": "CVE-2023-46308",
            "id": "pyup.io-64360",
            "more_info_path": "/vulnerabilities/CVE-2023-46308/64360",
            "specs": [
                "<1.3.7"
            ],
            "v": "<1.3.7"
        },
        {
            "advisory": "Affected versions of the panel package are vulnerable to Cross-Site Scripting (XSS) attacks due to missing HTML escaping in authentication templates. The errormessage variable in the basic_login.html template and the error/error_msg variables in the error.html template fail to escape user-controlled input, allowing arbitrary script injection.",
            "cve": "PVE-2025-78268",
            "id": "pyup.io-78268",
            "more_info_path": "/vulnerabilities/PVE-2025-78268/78268",
            "specs": [
                "<1.7.5"
            ],
            "v": "<1.7.5"
        }
    ],
    "pangres": [
        {
            "advisory": "Pangres 2.1 was released with the claim that it became completely SQL injection safe. Everything is escaped or parameterized including schema, table and column names.",
            "cve": "PVE-2021-39284",
            "id": "pyup.io-39284",
            "more_info_path": "/vulnerabilities/PVE-2021-39284/39284",
            "specs": [
                "<2.1"
            ],
            "v": "<2.1"
        }
    ],
    "panoptes-utils": [
        {
            "advisory": "Panoptes-utils 0.2.21 updates its dependency 'PyYaml' to v5.3.1 to include security fixes.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-38493",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/38493",
            "specs": [
                "<0.2.21"
            ],
            "v": "<0.2.21"
        }
    ],
    "panoramix": [
        {
            "advisory": "Panoramix (now renamed apache-superset) 0.8.0 is vulnerable to CVE-2020-13948: While investigating a bug report on Apache Superset, it was determined that an authenticated user could craft requests via a number of templated text fields in the product that would allow arbitrary access to Python\u2019s 'os' package in the web application process in versions < 0.37.1. It was thus possible for an authenticated user to list and access files, environment variables, and process information. Additionally it was possible to set environment variables for the current process, create and update files in folders writable by the web process, and execute arbitrary programs accessible by the web process. All other operations available to the 'os' package in Python were also available, even if not explicitly enumerated in this CVE.",
            "cve": "CVE-2020-13948",
            "id": "pyup.io-47508",
            "more_info_path": "/vulnerabilities/CVE-2020-13948/47508",
            "specs": [
                "<=0.8.0"
            ],
            "v": "<=0.8.0"
        }
    ],
    "panther-analysis-tool": [
        {
            "advisory": "Panther-analysis-tool version 0.45.0 has upgraded its aiohttp library to version 3.9.2 from the previous 3.8.6, addressing security concerns highlighted by CVE-2023-49082.",
            "cve": "CVE-2023-49082",
            "id": "pyup.io-67486",
            "more_info_path": "/vulnerabilities/CVE-2023-49082/67486",
            "specs": [
                "<0.45.0"
            ],
            "v": "<0.45.0"
        },
        {
            "advisory": "Panther-analysis-tool version 0.45.0 has upgraded its aiohttp library to version 3.9.2 from the previous 3.8.6, addressing security concerns highlighted by CVE-2024-23334",
            "cve": "CVE-2024-23334",
            "id": "pyup.io-67505",
            "more_info_path": "/vulnerabilities/CVE-2024-23334/67505",
            "specs": [
                "<0.45.0"
            ],
            "v": "<0.45.0"
        },
        {
            "advisory": "Panther-analysis-tool version 0.45.0 has upgraded its aiohttp library to version 3.9.2 from the previous 3.8.6, addressing security concerns highlighted by CVE-2023-49081",
            "cve": "CVE-2023-49081",
            "id": "pyup.io-67504",
            "more_info_path": "/vulnerabilities/CVE-2023-49081/67504",
            "specs": [
                "<0.45.0"
            ],
            "v": "<0.45.0"
        },
        {
            "advisory": "Panther-analysis-tool version 0.45.0 has updated its setuptools dependency to version 65.5.1 from 40.5.0, in response to the security vulnerability identified as CVE-2022-40897..",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-67507",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/67507",
            "specs": [
                "<0.45.0"
            ],
            "v": "<0.45.0"
        },
        {
            "advisory": "Panther-analysis-tool version 0.45.0 has upgraded its aiohttp library to version 3.9.2 from the previous 3.8.6, addressing security concerns highlighted by CVE-2024-23829",
            "cve": "CVE-2024-23829",
            "id": "pyup.io-67506",
            "more_info_path": "/vulnerabilities/CVE-2024-23829/67506",
            "specs": [
                "<0.45.0"
            ],
            "v": "<0.45.0"
        }
    ],
    "papermerge": [
        {
            "advisory": "Papermerge 1.5.5 includes a fix for a stored XSS vulnerability on tags.\r\nhttps://github.com/ciur/papermerge/issues/271",
            "cve": "PVE-2023-99953",
            "id": "pyup.io-60901",
            "more_info_path": "/vulnerabilities/PVE-2023-99953/60901",
            "specs": [
                "<1.5.5"
            ],
            "v": "<1.5.5"
        },
        {
            "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in Papermerge before 1.5.2 allow remote attackers to inject arbitrary web script or HTML via the rename, tag, upload, or create folder function. The payload can be in a folder, a tag, or a document's filename. If email consumption is configured in Papermerge, a malicious document can be sent by email and is automatically uploaded into the Papermerge web application. Therefore, no authentication is required to exploit XSS if email consumption is configured. Otherwise authentication is required.",
            "cve": "CVE-2020-29456",
            "id": "pyup.io-54298",
            "more_info_path": "/vulnerabilities/CVE-2020-29456/54298",
            "specs": [
                ">=1.2.0,<1.5.2"
            ],
            "v": ">=1.2.0,<1.5.2"
        }
    ],
    "papermerge-core": [
        {
            "advisory": "Papermerge-core 1.5.5 includes a fix for a stored XSS vulnerability on tags.\r\nhttps://github.com/ciur/papermerge/issues/271",
            "cve": "PVE-2023-99953",
            "id": "pyup.io-60902",
            "more_info_path": "/vulnerabilities/PVE-2023-99953/60902",
            "specs": [
                "<1.5.5"
            ],
            "v": "<1.5.5"
        },
        {
            "advisory": "Papermerge-core 2.1.0b5 includes a fix for an Insecure Direct Object Reference (IDOR) vulnerability, that allowed any user to download any file.\r\nhttps://github.com/papermerge/papermerge-core/issues/57",
            "cve": "PVE-2022-51297",
            "id": "pyup.io-51297",
            "more_info_path": "/vulnerabilities/PVE-2022-51297/51297",
            "specs": [
                "<2.1.0b5"
            ],
            "v": "<2.1.0b5"
        }
    ],
    "paradrop": [
        {
            "advisory": "Paradrop 0.10.0 supports more WiFi encryption settings, including properly supporting CCMP for better security.",
            "cve": "PVE-2021-37491",
            "id": "pyup.io-37491",
            "more_info_path": "/vulnerabilities/PVE-2021-37491/37491",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Paradrop 0.13.0 updates its dependency pyOpenSSL to v17.5.0 to include a security fix.",
            "cve": "CVE-2018-1000808",
            "id": "pyup.io-37490",
            "more_info_path": "/vulnerabilities/CVE-2018-1000808/37490",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Paradrop 0.13.0 updates its dependency requests to v2.20.1 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-42701",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/42701",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Paradrop 0.13.0 updates its dependency urllib3 to v1.24.1 to include a security fix.",
            "cve": "CVE-2018-20060",
            "id": "pyup.io-42700",
            "more_info_path": "/vulnerabilities/CVE-2018-20060/42700",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Paradrop 0.5 secures the router settings page with a login system.",
            "cve": "PVE-2021-37492",
            "id": "pyup.io-37492",
            "more_info_path": "/vulnerabilities/PVE-2021-37492/37492",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        }
    ],
    "parameterspace": [
        {
            "advisory": "Parameterspace 0.7.18 updates its dependency 'nbconvert' to v6.5.3 to include a security fix.",
            "cve": "CVE-2021-32862",
            "id": "pyup.io-50786",
            "more_info_path": "/vulnerabilities/CVE-2021-32862/50786",
            "specs": [
                "<0.7.18"
            ],
            "v": "<0.7.18"
        }
    ],
    "paramiko": [
        {
            "advisory": "transport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not properly check whether authentication is completed before processing other requests, as demonstrated by channel-open. A customized SSH client can simply skip the authentication step.",
            "cve": "CVE-2018-7750",
            "id": "pyup.io-41269",
            "more_info_path": "/vulnerabilities/CVE-2018-7750/41269",
            "specs": [
                "<1.17.6",
                ">=2.0.0,<2.0.8",
                ">=2.1.0,<2.1.5",
                ">=2.2.0,<2.2.3",
                ">=2.3.0,<2.3.2",
                "==2.4.0",
                ">=1.18.0,<1.18.5"
            ],
            "v": "<1.17.6,>=2.0.0,<2.0.8,>=2.1.0,<2.1.5,>=2.2.0,<2.2.3,>=2.3.0,<2.3.2,==2.4.0,>=1.18.0,<1.18.5"
        },
        {
            "advisory": "Paramiko 1.7.2 includes a fix for CVE-2008-0299: common.py in Paramiko 1.7.1 and earlier, when using threads or forked processes, does not properly use RandomPool, which allows one session to obtain sensitive information from another session by predicting the state of the pool.",
            "cve": "CVE-2008-0299",
            "id": "pyup.io-27486",
            "more_info_path": "/vulnerabilities/CVE-2008-0299/27486",
            "specs": [
                "<1.7.2"
            ],
            "v": "<1.7.2"
        },
        {
            "advisory": "Paramiko 3.4.0 has been released to fix vulnerabilities affecting encrypt-then-MAC digest algorithms in tandem with CBC ciphers, and ChaCha20-poly1305. The fix requires cooperation from both ends of the connection, making it effective when the remote end is OpenSSH >= 9.6 and configured to use the new \u201cstrict kex\u201d mode. For further details, refer to the official Paramiko documentation or GitHub repository.\r\nhttps://github.com/advisories/GHSA-45x7-px36-x8w8",
            "cve": "CVE-2023-48795",
            "id": "pyup.io-63227",
            "more_info_path": "/vulnerabilities/CVE-2023-48795/63227",
            "specs": [
                "<3.4.0"
            ],
            "v": "<3.4.0"
        },
        {
            "advisory": "Paramiko version 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5, 1.17.6 contains a Incorrect Access Control vulnerability in SSH server that can result in RCE. This attack appear to be exploitable via network connectivity.",
            "cve": "CVE-2018-1000805",
            "id": "pyup.io-41268",
            "more_info_path": "/vulnerabilities/CVE-2018-1000805/41268",
            "specs": [
                "==1.17.6",
                "==1.18.5",
                "==2.0.8",
                "==2.1.5",
                "==2.2.3",
                "==2.3.2",
                "==2.4.1"
            ],
            "v": "==1.17.6,==1.18.5,==2.0.8,==2.1.5,==2.2.3,==2.3.2,==2.4.1"
        },
        {
            "advisory": "In Paramiko before 2.10.1, a race condition (between creation and chmod) in the write_private_key_file function could allow unauthorized information disclosure.",
            "cve": "CVE-2022-24302",
            "id": "pyup.io-54709",
            "more_info_path": "/vulnerabilities/CVE-2022-24302/54709",
            "specs": [
                ">=0,<2.9.3",
                ">=2.10.0,<2.10.1"
            ],
            "v": ">=0,<2.9.3,>=2.10.0,<2.10.1"
        }
    ],
    "parlai": [
        {
            "advisory": "parlai is a framework for training and evaluating AI models on a variety of openly available dialogue datasets. In affected versions the package is vulnerable to YAML deserialization attack caused by unsafe loading which leads to Arbitary code execution. This security bug is patched by avoiding unsafe loader users should update to version above v1.1.0. If upgrading is not possible then users can change the Loader used to SafeLoader as a workaround. See commit 507d066ef432ea27d3e201da08009872a2f37725 for details.",
            "cve": "CVE-2021-39207",
            "id": "pyup.io-54330",
            "more_info_path": "/vulnerabilities/CVE-2021-39207/54330",
            "specs": [
                ">=0,<1.1.0"
            ],
            "v": ">=0,<1.1.0"
        },
        {
            "advisory": "Due to use of unsafe YAML deserialization logic, an attacker with the ability to modify local YAML configuration files could provide malicious input, resulting in remote code execution or similar risks. This issue affects ParlAI prior to v1.1.0.",
            "cve": "CVE-2021-24040",
            "id": "pyup.io-54328",
            "more_info_path": "/vulnerabilities/CVE-2021-24040/54328",
            "specs": [
                ">=0,<1.1.0"
            ],
            "v": ">=0,<1.1.0"
        }
    ],
    "parsita": [
        {
            "advisory": "Parsita 2.0.0 includes a fix for a ReDoS vulnerability.\r\nhttps://github.com/drhagen/parsita/pull/91/files",
            "cve": "PVE-2023-59179",
            "id": "pyup.io-59179",
            "more_info_path": "/vulnerabilities/PVE-2023-59179/59179",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        }
    ],
    "parsl": [
        {
            "advisory": "Affected versions of the parsl package are vulnerable to SQL Injection due to unsafe string formatting of SQL queries with user-supplied workflow identifiers. In parsl.monitoring.visualization.views.py, multiple route handlers interpolate the workflow_id parameter from URL routes directly into raw SQL strings (including queries executed via pandas.read_sql_query) using the Python % operator instead of parameterized queries.",
            "cve": "PVE-2026-83975",
            "id": "pyup.io-83975",
            "more_info_path": "/vulnerabilities/PVE-2026-83975/83975",
            "specs": [
                "<2026.01.05"
            ],
            "v": "<2026.01.05"
        }
    ],
    "parsons": [
        {
            "advisory": "Parsons 0.13.2 updates its dependency 'httplib2' from v0.12.0 to v0.18.0 to include a security fix.",
            "cve": "CVE-2020-11078",
            "id": "pyup.io-59058",
            "more_info_path": "/vulnerabilities/CVE-2020-11078/59058",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Parsons 0.17.2 updates its dependency 'urllib3' to v1.26.5 to include security fixes.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-59057",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/59057",
            "specs": [
                "<0.17.2"
            ],
            "v": "<0.17.2"
        },
        {
            "advisory": "Parsons 0.17.2 updates its dependency 'urllib3' to v1.26.5 to include security fixes.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-59061",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/59061",
            "specs": [
                "<0.17.2"
            ],
            "v": "<0.17.2"
        },
        {
            "advisory": "Parsons 1.0.0 updates its dependency 'joblib' to v1.2.0 to include a security fix.\r\nhttps://github.com/move-coop/parsons/pull/764/commits/ad3c0ecd431ac9b3617196d397f9e4b8f6643d7e",
            "cve": "CVE-2022-21797",
            "id": "pyup.io-59056",
            "more_info_path": "/vulnerabilities/CVE-2022-21797/59056",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "partseg": [
        {
            "advisory": "Partseg 0.14.3 cleans potential vulnerabilities.\r\nhttps://github.com/4DNucleome/PartSeg/commit/14530514e0f58efd779ab6049fbd7311b25b5652",
            "cve": "PVE-2022-50670",
            "id": "pyup.io-50670",
            "more_info_path": "/vulnerabilities/PVE-2022-50670/50670",
            "specs": [
                "<0.14.3"
            ],
            "v": "<0.14.3"
        },
        {
            "advisory": "Partseg 0.9.6 updates its dependency 'pyinstaller' to version '3.6' to fix a Local Privilege Escalation vulnerability.\r\nhttps://github.com/4DNucleome/PartSeg/commit/e3041b2e1e1a3654270fd697e007d0b98616ecb1\r\nhttps://github.com/advisories/GHSA-7fcj-pq9j-wh2r",
            "cve": "CVE-2019-16784",
            "id": "pyup.io-60279",
            "more_info_path": "/vulnerabilities/CVE-2019-16784/60279",
            "specs": [
                "<0.9.6"
            ],
            "v": "<0.9.6"
        }
    ],
    "pass-operator": [
        {
            "advisory": "Pass-operator 0.3.1 fixes a security vulnerability related to git push commands. The flaw allowed unauthorized users to execute push operations to the repository. This update enhances the authentication and authorization mechanisms, ensuring that only authorized users can perform git push operations, thereby securing the repository from unauthorized modifications.",
            "cve": "PVE-2024-71078",
            "id": "pyup.io-71078",
            "more_info_path": "/vulnerabilities/PVE-2024-71078/71078",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "passeo": [
        {
            "advisory": "Passeo 1.0.5 includes a fix for CVE-2022-23472: Versions prior to 1.0.5 rely on the python 'random' library for random value selection. The python 'random' library warns that it should not be used for security purposes due to its reliance on a non-cryptographically secure random number generator. As a result a motivated attacker may be able to guess generated passwords.\r\nhttps://github.com/ArjunSharda/Passeo/security/advisories/GHSA-mhhf-vgwh-fw9h",
            "cve": "CVE-2022-23472",
            "id": "pyup.io-52346",
            "more_info_path": "/vulnerabilities/CVE-2022-23472/52346",
            "specs": [
                "<1.0.5"
            ],
            "v": "<1.0.5"
        }
    ],
    "passlib": [
        {
            "advisory": "Passlib 1.4 disables unix_fallback\u2019s \u201cwildcard password\u201d support unless explicitly enabled by user.",
            "cve": "PVE-2021-25921",
            "id": "pyup.io-25921",
            "more_info_path": "/vulnerabilities/PVE-2021-25921/25921",
            "specs": [
                "<1.4"
            ],
            "v": "<1.4"
        }
    ],
    "password-safe-box": [
        {
            "advisory": "Password-safe-box 0.2 adds Fast Convert (which provides slightly better security than a normal hash).",
            "cve": "PVE-2021-38703",
            "id": "pyup.io-38703",
            "more_info_path": "/vulnerabilities/PVE-2021-38703/38703",
            "specs": [
                "<0.2"
            ],
            "v": "<0.2"
        }
    ],
    "paste": [
        {
            "advisory": "Paste before 0.9.5 has a security vulnerability in \"paste.urlparser\"'s StaticURLParser and PkgResourcesParser where, with some servers, you could escape the document root.",
            "cve": "PVE-2021-25922",
            "id": "pyup.io-25922",
            "more_info_path": "/vulnerabilities/PVE-2021-25922/25922",
            "specs": [
                "<0.9.5"
            ],
            "v": "<0.9.5"
        },
        {
            "advisory": "Paste before 1.1 allowed escaping root and reading files when used with 'paste.httpserver'. This does not affect other servers, and does not apply when proxying requests from Apache to  'paste.httpserver'.",
            "cve": "PVE-2021-25923",
            "id": "pyup.io-25923",
            "more_info_path": "/vulnerabilities/PVE-2021-25923/25923",
            "specs": [
                "<1.1"
            ],
            "v": "<1.1"
        },
        {
            "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in the paste.httpexceptions implementation in Paste before 1.7.4 allow remote attackers to inject arbitrary web script or HTML via vectors involving a 404 status code, related to (1) paste.urlparser.StaticURLParser, (2) paste.urlparser.PkgResourcesParser, (3) paste.urlmap.URLMap, and (4) HTTPNotFound.",
            "cve": "CVE-2010-2477",
            "id": "pyup.io-35340",
            "more_info_path": "/vulnerabilities/CVE-2010-2477/35340",
            "specs": [
                "<1.7.4"
            ],
            "v": "<1.7.4"
        }
    ],
    "pastescript": [
        {
            "advisory": "Paste Script 1.7.5 and earlier does not properly set group memberships during execution with root privileges, which might allow remote attackers to bypass intended file-access restrictions by leveraging a web application that uses the local filesystem.",
            "cve": "CVE-2012-0878",
            "id": "pyup.io-25925",
            "more_info_path": "/vulnerabilities/CVE-2012-0878/25925",
            "specs": [
                "<1.7.5"
            ],
            "v": "<1.7.5"
        }
    ],
    "pathfinder": [
        {
            "advisory": "Pathfinder 0.5.4 stops relying in Jinja2 v2.6 to avoid security issues.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-38220",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/38220",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pathfinder 0.5.4 stops relying in Jinja2 v2.6 to avoid security issues.",
            "cve": "CVE-2014-0012",
            "id": "pyup.io-46429",
            "more_info_path": "/vulnerabilities/CVE-2014-0012/46429",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pathfinder 0.5.4 stops relying in Jinja2 v2.6 to avoid security issues.",
            "cve": "CVE-2014-1402",
            "id": "pyup.io-46430",
            "more_info_path": "/vulnerabilities/CVE-2014-1402/46430",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pathfinder 0.5.4 stops relying in Jinja2 v2.6 to avoid security issues.",
            "cve": "CVE-2016-10745",
            "id": "pyup.io-46431",
            "more_info_path": "/vulnerabilities/CVE-2016-10745/46431",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        }
    ],
    "patientmatcher": [
        {
            "advisory": "Patientmatcher 3.4 removes usage of unsafe HTTP protocol.\r\nhttps://github.com/Clinical-Genomics/patientMatcher/pull/293",
            "cve": "PVE-2022-48586",
            "id": "pyup.io-48586",
            "more_info_path": "/vulnerabilities/PVE-2022-48586/48586",
            "specs": [
                "<3.4"
            ],
            "v": "<3.4"
        },
        {
            "advisory": "Patientmatcher 4.2 adds protection against CSRF and tabnabbing attacks.\r\nhttps://github.com/Clinical-Genomics/patientMatcher/pull/308",
            "cve": "PVE-2022-51176",
            "id": "pyup.io-51176",
            "more_info_path": "/vulnerabilities/PVE-2022-51176/51176",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        },
        {
            "advisory": "Patientmatcher 4.2 removes server log messages that may contain sensitive information.\r\nhttps://github.com/Clinical-Genomics/patientMatcher/commit/f44c1583d810aeb1e48eb37374e753a609d846c3",
            "cve": "PVE-2022-51171",
            "id": "pyup.io-51171",
            "more_info_path": "/vulnerabilities/PVE-2022-51171/51171",
            "specs": [
                "<4.2"
            ],
            "v": "<4.2"
        }
    ],
    "patroni": [
        {
            "advisory": "Patroni 2.0.2 uses 'hmac.compare_digest()' instead of '==' for performing the REST API authentication. The previous was vulnerable to timing attacks.",
            "cve": "PVE-2021-42998",
            "id": "pyup.io-42998",
            "more_info_path": "/vulnerabilities/PVE-2021-42998/42998",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Patroni 2.1.6 mitigates the known vector of attacks consisting in creating functions and/or operators in a public scheme with the same name and signature as corresponding objects in 'pg_catalog'.\r\nhttps://github.com/zalando/patroni/commit/4d77b444dc24924d84c6591021b3603e7a60bf64",
            "cve": "PVE-2023-52657",
            "id": "pyup.io-52657",
            "more_info_path": "/vulnerabilities/PVE-2023-52657/52657",
            "specs": [
                "<2.1.6"
            ],
            "v": "<2.1.6"
        },
        {
            "advisory": "Patroni 2.1.6 enables SSL in REST API and Postgres by default if possible.\r\nhttps://github.com/zalando/patroni/commit/49f1ccf8746b8dbb8573ee8d1971b184ceb12470",
            "cve": "PVE-2023-52658",
            "id": "pyup.io-52658",
            "more_info_path": "/vulnerabilities/PVE-2023-52658/52658",
            "specs": [
                "<2.1.6"
            ],
            "v": "<2.1.6"
        },
        {
            "advisory": "Patroni 2.1.6 prevents pg_stat_statements from recording secrets.\r\nhttps://github.com/zalando/patroni/commit/b6b220dddb3f76f93947d469274b0aa4852b85ab",
            "cve": "PVE-2022-52598",
            "id": "pyup.io-52598",
            "more_info_path": "/vulnerabilities/PVE-2022-52598/52598",
            "specs": [
                "<2.1.6"
            ],
            "v": "<2.1.6"
        }
    ],
    "paws-room-acoustics-simulator": [
        {
            "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'paws-room-acoustics-simulator' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.",
            "cve": "PVE-2024-74248",
            "id": "pyup.io-74248",
            "more_info_path": "/vulnerabilities/PVE-2024-74248/74248",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "payton": [
        {
            "advisory": "payton 0.1.4 upgrades Pillow from 7.x, since it had a security issue. This version is just for upgrading Pillow up to a secure version.",
            "cve": "PVE-2021-40214",
            "id": "pyup.io-40214",
            "more_info_path": "/vulnerabilities/PVE-2021-40214/40214",
            "specs": [
                "<0.1.4"
            ],
            "v": "<0.1.4"
        }
    ],
    "pcaspy": [
        {
            "advisory": "Pcaspy version 0.7.1 addresses a race condition in the handling of client disconnections. This update prevents server crashes previously caused by simultaneous access to shared resources during client disconnection events. \r\nhttps://github.com/paulscherrerinstitute/pcaspy/pull/49/commits/f2865472f8b5996745c6e82105eab77c1637b62b",
            "cve": "PVE-2024-66760",
            "id": "pyup.io-66760",
            "more_info_path": "/vulnerabilities/PVE-2024-66760/66760",
            "specs": [
                "<0.7.1"
            ],
            "v": "<0.7.1"
        }
    ],
    "pconf": [
        {
            "advisory": "Pconf 1.7.1 updates its dependency 'pyyaml' to v5.3.1 to include security fixes.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-44483",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/44483",
            "specs": [
                "<1.7.1"
            ],
            "v": "<1.7.1"
        },
        {
            "advisory": "Pconf 1.7.1 updates its dependency 'pyyaml' to v5.3.1 to include security fixes.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-43971",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/43971",
            "specs": [
                "<1.7.1"
            ],
            "v": "<1.7.1"
        }
    ],
    "pcp": [
        {
            "advisory": "pcp before 2.1.911 has a not further described vulnerability in pcp.spec.in.",
            "cve": "PVE-2021-25926",
            "id": "pyup.io-25926",
            "more_info_path": "/vulnerabilities/PVE-2021-25926/25926",
            "specs": [
                "<2.1.911"
            ],
            "v": "<2.1.911"
        },
        {
            "advisory": "Pcp 5.2.2 makes pmcd init NSS as read-only when using secure connections.\r\nhttps://github.com/performancecopilot/pcp/commit/c85528b1865336ad108a211a87f24132cf45d554",
            "cve": "PVE-2021-42786",
            "id": "pyup.io-42786",
            "more_info_path": "/vulnerabilities/PVE-2021-42786/42786",
            "specs": [
                "<5.2.2"
            ],
            "v": "<5.2.2"
        }
    ],
    "pcp-mcp": [
        {
            "advisory": "Affected versions of the pcp-mcp package are vulnerable to Server-Side Request Forgery (SSRF) due to missing host validation on the host parameter in MCP tools. The get_system_snapshot, get_process_top, query_metrics, and other tool functions accept an arbitrary host parameter that is passed directly to get_client_for_host() without any allowlist validation, enabling connections to arbitrary pmcd hosts through the pmproxy service.",
            "cve": "PVE-2026-84828",
            "id": "pyup.io-84828",
            "more_info_path": "/vulnerabilities/PVE-2026-84828/84828",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        }
    ],
    "pdf2zh": [
        {
            "advisory": "Affected versions of the pdf2zh package are vulnerable to Open Redirect due to insufficient validation of a user-supplied redirect target. The /gradio_api endpoint reads the file parameter and issues an HTTP 302 redirect to the provided URL without restricting the destination domain, enabling attacker-controlled external links.",
            "cve": "CVE-2025-50736",
            "id": "pyup.io-80991",
            "more_info_path": "/vulnerabilities/CVE-2025-50736/80991",
            "specs": [
                "==1.9.9"
            ],
            "v": "==1.9.9"
        }
    ],
    "pdfcropmargins": [
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-49509",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/49509",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-49516",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/49516",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-49525",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/49525",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-25287",
            "id": "pyup.io-49512",
            "more_info_path": "/vulnerabilities/CVE-2021-25287/49512",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-49508",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/49508",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-49514",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/49514",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-49521",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/49521",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-49507",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/49507",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-49442",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/49442",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-49510",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/49510",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-49515",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/49515",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-25288",
            "id": "pyup.io-49513",
            "more_info_path": "/vulnerabilities/CVE-2021-25288/49513",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-49519",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/49519",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-49522",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/49522",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 pins its dependency 'PyPDF2' to versions \">=1.27.5\" to include a security fix.",
            "cve": "CVE-2022-24859",
            "id": "pyup.io-49526",
            "more_info_path": "/vulnerabilities/CVE-2022-24859/49526",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-49517",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/49517",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-49506",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/49506",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-49518",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/49518",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-49524",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/49524",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2020-15999",
            "id": "pyup.io-49523",
            "more_info_path": "/vulnerabilities/CVE-2020-15999/49523",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-49520",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/49520",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.0.6 updates its dependency 'pillow' requirement to '>=9.0.0' to include security fixes.",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-49511",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/49511",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Pdfcropmargins 1.1.1 updates its dependency 'pillow' requirement to \">=9.3.0\" to include security fixes.",
            "cve": "CVE-2022-45198",
            "id": "pyup.io-52359",
            "more_info_path": "/vulnerabilities/CVE-2022-45198/52359",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        },
        {
            "advisory": "Pdfcropmargins 1.1.1 updates its dependency 'pillow' requirement to \">=9.3.0\" to include security fixes.",
            "cve": "CVE-2022-30595",
            "id": "pyup.io-52360",
            "more_info_path": "/vulnerabilities/CVE-2022-30595/52360",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        },
        {
            "advisory": "Pdfcropmargins 1.1.1 updates its dependency 'pillow' requirement to \">=9.3.0\" to include security fixes.",
            "cve": "CVE-2022-24303",
            "id": "pyup.io-52361",
            "more_info_path": "/vulnerabilities/CVE-2022-24303/52361",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "pdfextract": [
        {
            "advisory": "Pdfextract before 0.0.2 is using \"eval\" on filenames, leading to execution of arbitrary Python code.",
            "cve": "PVE-2021-25927",
            "id": "pyup.io-25927",
            "more_info_path": "/vulnerabilities/PVE-2021-25927/25927",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        }
    ],
    "pdfminer.six": [
        {
            "advisory": "Affected versions of the pdfminer.six package are vulnerable to Deserialization of Untrusted Data due to the CMap loader deserializing untrusted .pickle.gz files with Python\u2019s pickle. In pdfminer.cmapdb._load_data, the code calls pickle.loads on CMap data discovered via CMapDB.get_cmap from directories in the CMAP_PATH search path without validation or restriction, allowing attacker-supplied object payloads to be executed.",
            "cve": "PVE-2025-81495",
            "id": "pyup.io-81495",
            "more_info_path": "/vulnerabilities/PVE-2025-81495/81495",
            "specs": [
                "<20251107"
            ],
            "v": "<20251107"
        },
        {
            "advisory": "Affected versions of the pdfminer.six package are vulnerable to Deserialization of Untrusted Data due to the CMapDB._load_data() method invoking pickle.loads() on a PDF-controlled CMap file path. The CMapDB._load_data() routine constructs a *.pickle.gz filename from the /Encoding CMap name and joins it with a directory, but attacker-chosen or absolute paths can be resolved and the gzip content is passed directly to pickle.loads(), enabling execution of pickled objects.",
            "cve": "CVE-2025-64512",
            "id": "pyup.io-81486",
            "more_info_path": "/vulnerabilities/CVE-2025-64512/81486",
            "specs": [
                "<20251107"
            ],
            "v": "<20251107"
        }
    ],
    "pdfreader": [
        {
            "advisory": "Pdfreader 0.1.6 updates its dependency 'pillow' to a version >= 7.1.0 to include security fixes.",
            "cve": "CVE-2020-10378",
            "id": "pyup.io-43477",
            "more_info_path": "/vulnerabilities/CVE-2020-10378/43477",
            "specs": [
                "<0.1.6"
            ],
            "v": "<0.1.6"
        },
        {
            "advisory": "Pdfreader 0.1.6 updates its dependency 'pillow' to a version >= 7.1.0 to include security fixes.",
            "cve": "CVE-2020-10994",
            "id": "pyup.io-43476",
            "more_info_path": "/vulnerabilities/CVE-2020-10994/43476",
            "specs": [
                "<0.1.6"
            ],
            "v": "<0.1.6"
        },
        {
            "advisory": "Pdfreader 0.1.6 updates its dependency 'pillow' to a version >= 7.1.0 to include security fixes.",
            "cve": "CVE-2020-10379",
            "id": "pyup.io-39314",
            "more_info_path": "/vulnerabilities/CVE-2020-10379/39314",
            "specs": [
                "<0.1.6"
            ],
            "v": "<0.1.6"
        },
        {
            "advisory": "Pdfreader 0.1.6 updates its dependency 'pillow' to a version >= 7.1.0 to include security fixes.",
            "cve": "CVE-2020-11538",
            "id": "pyup.io-43475",
            "more_info_path": "/vulnerabilities/CVE-2020-11538/43475",
            "specs": [
                "<0.1.6"
            ],
            "v": "<0.1.6"
        }
    ],
    "pdh": [
        {
            "advisory": "Pdh 0.3.11 stops using root to run the container.\r\nhttps://github.com/mbovo/pdh/pull/33",
            "cve": "PVE-2023-53725",
            "id": "pyup.io-53725",
            "more_info_path": "/vulnerabilities/PVE-2023-53725/53725",
            "specs": [
                "<0.3.11"
            ],
            "v": "<0.3.11"
        }
    ],
    "pdkit": [
        {
            "advisory": "Pdkit 1.2.1 includes an unspecified security fix for included libraries.",
            "cve": "PVE-2021-37793",
            "id": "pyup.io-37793",
            "more_info_path": "/vulnerabilities/PVE-2021-37793/37793",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        }
    ],
    "pdm": [
        {
            "advisory": "Affected versions of the `pdm` package are vulnerable to Improper Input Validation due to insufficient verification of the integrity of the `pdm.lock` file. The vulnerability exists because the package does not properly validate the contents of the `pdm.lock` file, allowing it to be manipulated to misrepresent dependencies. An attacker, such as an insider or a malicious open source project, can exploit this by crafting a malicious `pdm.lock` file that appears to depend on a trusted PyPI project but actually installs a different, potentially malicious project.",
            "cve": "CVE-2023-45805",
            "id": "pyup.io-62025",
            "more_info_path": "/vulnerabilities/CVE-2023-45805/62025",
            "specs": [
                ">=1.6.0,<2.10.0"
            ],
            "v": ">=1.6.0,<2.10.0"
        }
    ],
    "pdoc": [
        {
            "advisory": "Pdoc 10.0.0 defuses insecure 'repr()' calls for all templates.\r\nhttps://github.com/mitmproxy/pdoc/commit/b14d6bc3d515d58d20c8810b79ae8f4115efaa8c",
            "cve": "PVE-2022-45022",
            "id": "pyup.io-45022",
            "more_info_path": "/vulnerabilities/PVE-2022-45022/45022",
            "specs": [
                "<10.0.0"
            ],
            "v": "<10.0.0"
        },
        {
            "advisory": "pdoc provides API Documentation for Python Projects. Documentation generated with `pdoc --math` linked to JavaScript files from polyfill.io. The polyfill.io CDN has been sold and now serves malicious code.",
            "cve": "CVE-2024-38526",
            "id": "pyup.io-71836",
            "more_info_path": "/vulnerabilities/CVE-2024-38526/71836",
            "specs": [
                "<14.5.1"
            ],
            "v": "<14.5.1"
        }
    ],
    "pds.registry-sweepers": [
        {
            "advisory": "Pds.registry-sweepers is affected by an unsafe defaults vulnerability. Default behavior was now switched to check host certs.\r\nhttps://github.com/NASA-PDS/registry-sweepers/pull/22",
            "cve": "PVE-2024-64507",
            "id": "pyup.io-64507",
            "more_info_path": "/vulnerabilities/PVE-2024-64507/64507",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "peekabooav": [
        {
            "advisory": "Peekabooav 2.1 uses the 'schema' module for input validation.\r\nhttps://github.com/scVENUS/PeekabooAV/commit/cfd84d6b507ab4862efaa13c97e188e7327c76d4",
            "cve": "PVE-2022-48282",
            "id": "pyup.io-48282",
            "more_info_path": "/vulnerabilities/PVE-2022-48282/48282",
            "specs": [
                "<2.1"
            ],
            "v": "<2.1"
        }
    ],
    "peewee": [
        {
            "advisory": "Peewee 2.10.0 removes 'AESEncryptedField'. The cryptographic implementation was unsafe.\r\nhttps://github.com/coleifer/peewee/commit/6aee106831eed8c214086a20b26f72f2abff8db5",
            "cve": "PVE-2021-34337",
            "id": "pyup.io-34337",
            "more_info_path": "/vulnerabilities/PVE-2021-34337/34337",
            "specs": [
                "<2.10.0"
            ],
            "v": "<2.10.0"
        },
        {
            "advisory": "Peewee 3.17.1 introduces enhancements to address a race condition issue by implementing stricter locking mechanisms around pool connection management.\r\nhttps://github.com/coleifer/peewee/commit/ea3fb11a9c2a4b0cd958a453dd287e408477eda5",
            "cve": "PVE-2024-64952",
            "id": "pyup.io-64952",
            "more_info_path": "/vulnerabilities/PVE-2024-64952/64952",
            "specs": [
                "<3.17.1"
            ],
            "v": "<3.17.1"
        },
        {
            "advisory": "Affected versions of the peewee package are vulnerable to Regular Expression Denial of Service (ReDoS) due to a nested-repetition regular expression used during FTS5 query validation. The FTS5Model.validate_query routine tokenizes user-supplied search strings with _quote_re.findall(query), and the quoted-string subpattern (\"(?:\\\\.|[^\"])*\" within a repeated construct) permits catastrophic backtracking on certain inputs.",
            "cve": "PVE-2025-81123",
            "id": "pyup.io-81123",
            "more_info_path": "/vulnerabilities/PVE-2025-81123/81123",
            "specs": [
                "<3.18.3"
            ],
            "v": "<3.18.3"
        }
    ],
    "peltak": [
        {
            "advisory": "Peltak 0.28.0 updates its dependency 'pygments' requirement  to \">=2.7.4\" to include security fixes.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-51468",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/51468",
            "specs": [
                "<0.28.0"
            ],
            "v": "<0.28.0"
        },
        {
            "advisory": "Peltak 0.28.0 updates its dependency 'pygments' requirement  to \">=2.7.4\" to include security fixes.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-51478",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/51478",
            "specs": [
                "<0.28.0"
            ],
            "v": "<0.28.0"
        }
    ],
    "pelutils": [
        {
            "advisory": "Pelutils version 0.6.0 makes 'log.throw' private, as it could be exploited.",
            "cve": "PVE-2021-42045",
            "id": "pyup.io-42045",
            "more_info_path": "/vulnerabilities/PVE-2021-42045/42045",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "pennylane-lightning": [
        {
            "advisory": "The pennylane-lightning repository has updated its GitHub Actions workflows to address a high-severity security vulnerability identified as GHSA-cxww-7g56-2vh6.",
            "cve": "PVE-2025-74996",
            "id": "pyup.io-74996",
            "more_info_path": "/vulnerabilities/PVE-2025-74996/74996",
            "specs": [
                "<0.39.0"
            ],
            "v": "<0.39.0"
        }
    ],
    "peppercorn": [
        {
            "advisory": "peppercorn before 0.5 is vulnerable to DoS attacks due to the use of an iterative parser rather than a recursive parser.\r\nhttps://github.com/Pylons/peppercorn/commit/d07cb55cee4f9b47b71d9fb7280aee6ab0799baf",
            "cve": "PVE-2021-25928",
            "id": "pyup.io-25928",
            "more_info_path": "/vulnerabilities/PVE-2021-25928/25928",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        }
    ],
    "peppol-py": [
        {
            "advisory": "Affected versions of the peppol-py package are vulnerable to XML External Entity (XXE) Injection due to an insecure Saxon XML parser configuration that permits external entity resolution and file system access during invoice validation. When validating XML-based invoices, the peppol-py XML processing logic invokes the Saxon-based parser with external entities enabled, allowing attacker-controlled XML documents to define external entities that the parser dereferences against local file system URIs and remote resources.",
            "cve": "CVE-2025-66371",
            "id": "pyup.io-82240",
            "more_info_path": "/vulnerabilities/CVE-2025-66371/82240",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "perceval-zulip": [
        {
            "advisory": "Perceval-zulip 0.2.0 drops support for Python < 3.7 as it arrived to End-of-Life in December 2021.\r\nhttps://github.com/vchrombie/grimoirelab-perceval-zulip/commit/328938531bb95c2407d75d94db452f5dceb73d16",
            "cve": "PVE-2021-42403",
            "id": "pyup.io-44468",
            "more_info_path": "/vulnerabilities/PVE-2021-42403/44468",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        },
        {
            "advisory": "Perceval-zulip 0.2.0 drops support for Python < 3.7 as it arrived to End-of-Life in December 2021.\r\nhttps://github.com/vchrombie/grimoirelab-perceval-zulip/commit/328938531bb95c2407d75d94db452f5dceb73d16",
            "cve": "CVE-2018-1060",
            "id": "pyup.io-44442",
            "more_info_path": "/vulnerabilities/CVE-2018-1060/44442",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        },
        {
            "advisory": "Perceval-zulip 0.2.0 drops support for Python < 3.7 as it arrived to End-of-Life in December 2021.\r\nhttps://github.com/vchrombie/grimoirelab-perceval-zulip/commit/328938531bb95c2407d75d94db452f5dceb73d16",
            "cve": "CVE-2018-1061",
            "id": "pyup.io-44467",
            "more_info_path": "/vulnerabilities/CVE-2018-1061/44467",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "perdido": [
        {
            "advisory": "The Perdido package in PyPI v0.0.1 to v0.0.2 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.",
            "cve": "CVE-2022-34054",
            "id": "pyup.io-54412",
            "more_info_path": "/vulnerabilities/CVE-2022-34054/54412",
            "specs": [
                ">=0.0.1,<0.0.3"
            ],
            "v": ">=0.0.1,<0.0.3"
        }
    ],
    "persephone": [
        {
            "advisory": "Persephone 0.4.0 updates its dependency 'nltk' to v3.4.5 to include a security fix.",
            "cve": "CVE-2019-14751",
            "id": "pyup.io-38231",
            "more_info_path": "/vulnerabilities/CVE-2019-14751/38231",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "personnummer": [
        {
            "advisory": "Personnummer 3.0.2 includes a security fix: The issue arrises from a regular expression allowing the first three digits in the last four digits of the personnummer to be 000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not 000x.\r\nhttps://github.com/advisories/GHSA-rxq3-5249-8hgg",
            "cve": "PVE-2023-55206",
            "id": "pyup.io-55206",
            "more_info_path": "/vulnerabilities/PVE-2023-55206/55206",
            "specs": [
                ">=0,<3.0.2"
            ],
            "v": ">=0,<3.0.2"
        }
    ],
    "pesapal-py": [
        {
            "advisory": "Pesapal-py 0.1.3 updates its dependency 'pygments' to version '2.15.0' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/twais/pesapal-py/commit/262a79e1f4485e08c439a230336ad806f562c9b1",
            "cve": "CVE-2022-40896",
            "id": "pyup.io-60613",
            "more_info_path": "/vulnerabilities/CVE-2022-40896/60613",
            "specs": [
                "<0.1.3"
            ],
            "v": "<0.1.3"
        },
        {
            "advisory": "Pesapal-py 0.1.3 updates its dependency 'certifi' to version '2023.7.22' to include a fix for a vulnerability.\r\nhttps://github.com/twais/pesapal-py/commit/262a79e1f4485e08c439a230336ad806f562c9b1",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60606",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60606",
            "specs": [
                "<0.1.3"
            ],
            "v": "<0.1.3"
        },
        {
            "advisory": "Pesapal-py 0.1.3 updates its dependency 'requests' to version '2.31.0' to include a fix for an Information Exposure vulnerability.\r\nhttps://github.com/twais/pesapal-py/commit/262a79e1f4485e08c439a230336ad806f562c9b1",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-60614",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/60614",
            "specs": [
                "<0.1.3"
            ],
            "v": "<0.1.3"
        }
    ],
    "petals": [
        {
            "advisory": "Petals 2.2.0 includes a fix for a race condition in MemoryCache.\r\nhttps://github.com/bigscience-workshop/petals/pull/487",
            "cve": "PVE-2023-61009",
            "id": "pyup.io-61009",
            "more_info_path": "/vulnerabilities/PVE-2023-61009/61009",
            "specs": [
                "<2.2.0"
            ],
            "v": "<2.2.0"
        }
    ],
    "petisco": [
        {
            "advisory": "Petisco 1.15.4 updates its dependency 'fastapi' to version '0.95.2' to include a security fix.\r\nhttps://github.com/alice-biometrics/petisco/pull/351",
            "cve": "CVE-2023-29159",
            "id": "pyup.io-59404",
            "more_info_path": "/vulnerabilities/CVE-2023-29159/59404",
            "specs": [
                "<1.15.4"
            ],
            "v": "<1.15.4"
        }
    ],
    "petl": [
        {
            "advisory": "Petl before 1.68, in some configurations, allows resolution of entities in an XML document.\r\nhttps://github.com/petl-developers/petl/security/advisories/GHSA-f5gc-p5m3-v347",
            "cve": "CVE-2020-29128",
            "id": "pyup.io-42292",
            "more_info_path": "/vulnerabilities/CVE-2020-29128/42292",
            "specs": [
                "<1.6.8"
            ],
            "v": "<1.6.8"
        },
        {
            "advisory": "Petl 1.7.2 updates its dependency 'lxml' to version '4.6.2' to include a fix for a XSS vulnerability.\r\nhttps://github.com/petl-developers/petl/pull/536",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-60451",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/60451",
            "specs": [
                "<1.7.2"
            ],
            "v": "<1.7.2"
        }
    ],
    "pex": [
        {
            "advisory": "pex before 0.5.6 follows links which may lead to security issues: https://rbcommons.com/s/twitter/r/293/.",
            "cve": "PVE-2021-25929",
            "id": "pyup.io-25929",
            "more_info_path": "/vulnerabilities/PVE-2021-25929/25929",
            "specs": [
                "<0.5.6"
            ],
            "v": "<0.5.6"
        },
        {
            "advisory": "Pex 0.8.0 includes a fix to refactor http handling to allow for alternate http implementations.  This adds support  for 'requests' , improving both performance and security.  For more information, read the commit notes at  and .",
            "cve": "PVE-2021-27426",
            "id": "pyup.io-27426",
            "more_info_path": "/vulnerabilities/PVE-2021-27426/27426",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        }
    ],
    "pfun": [
        {
            "advisory": "Pfun 0.12.0 updates the 'aiohttp' dependency to 3.7.4 to avoid an open redirect vulnerability.",
            "cve": "CVE-2021-21330",
            "id": "pyup.io-40141",
            "more_info_path": "/vulnerabilities/CVE-2021-21330/40141",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        }
    ],
    "pg-bulk-ingest": [
        {
            "advisory": "Pg-bulk-ingest version 0.0.45 specifically pins its localtunnel dependency to mitigate the axios vulnerability identified as CVE-2023-45857.",
            "cve": "CVE-2023-45857",
            "id": "pyup.io-65104",
            "more_info_path": "/vulnerabilities/CVE-2023-45857/65104",
            "specs": [
                "<0.0.45"
            ],
            "v": "<0.0.45"
        }
    ],
    "pg8000": [
        {
            "advisory": "Affected versions of the pg8000 package are vulnerable to SQL Injection due to improper neutralization of user-supplied list elements in the quoting routine. In pg8000 \u2264 1.31.4, the pg8000.native.literal function mishandles Python list inputs when composing SQL fragments, allowing special characters in attacker-controlled list items to be interpreted as SQL syntax rather than data.",
            "cve": "CVE-2025-61385",
            "id": "pyup.io-80861",
            "more_info_path": "/vulnerabilities/CVE-2025-61385/80861",
            "specs": [
                "<1.31.5"
            ],
            "v": "<1.31.5"
        }
    ],
    "pgadmin": [
        {
            "advisory": "Affected versions of the pgAdmin package are vulnerable to Path Traversal due to improper sanitization of session identifiers when constructing filesystem paths. The session-handling code uses `os.path.join` to concatenate the `DATA_DIR` session folder with a user-supplied session ID without enforcing a trusted base-path, leading to unsafe deserialization of pickle session files. An attacker can exploit this by supplying a crafted session identifier: on Windows, an unauthenticated attacker can deserialize remote pickle objects and achieve code execution; on POSIX/Linux, an authenticated attacker can upload malicious pickle objects that are deserialized, resulting in remote code execution.",
            "cve": "CVE-2024-2044",
            "id": "pyup.io-78715",
            "more_info_path": "/vulnerabilities/CVE-2024-2044/78715",
            "specs": [
                "<=8.3"
            ],
            "v": "<=8.3"
        }
    ],
    "pgadmin4": [
        {
            "advisory": "PgAdmin4 versions prior to v6.19 contains a directory traversal vulnerability. A user of the product may change another user's settings or alter the database.\r\n\r\nAlias:\r\nGHSA-9crj-hpxh-f6qg",
            "cve": "CVE-2023-0241",
            "id": "pyup.io-59566",
            "more_info_path": "/vulnerabilities/CVE-2023-0241/59566",
            "specs": [
                "<6.19"
            ],
            "v": "<6.19"
        },
        {
            "advisory": "A malicious, but authorised and authenticated user can construct an HTTP request using their existing CSRF token and session cookie to manually upload files to any location that the operating system user account under which pgAdmin is running has permission to write.\r\n\r\nAlias:\r\nGHSA-cr8c-972v-rmp3",
            "cve": "CVE-2022-0959",
            "id": "pyup.io-62740",
            "more_info_path": "/vulnerabilities/CVE-2022-0959/62740",
            "specs": [
                "<6.7"
            ],
            "v": "<6.7"
        },
        {
            "advisory": "A vulnerability was found in pgadmin. Users logging into pgAdmin running in server mode using LDAP authentication may be attached to another user's session if multiple connection attempts occur simultaneously.",
            "cve": "CVE-2023-1907",
            "id": "pyup.io-76364",
            "more_info_path": "/vulnerabilities/CVE-2023-1907/76364",
            "specs": [
                "<7.0"
            ],
            "v": "<7.0"
        },
        {
            "advisory": "Pgadmin4 7.7 includes a fix for CVE-2023-5002: This issue occurs when the pgAdmin server HTTP API validates the path a user selects to external PostgreSQL utilities such as pg_dump and pg_restore. Versions of pgAdmin prior to 7.6 failed to properly control the server code executed on this API, allowing an authenticated user to run arbitrary commands on the server.\r\nhttps://github.com/pgadmin-org/pgadmin4/issues/6763",
            "cve": "CVE-2023-5002",
            "id": "pyup.io-63071",
            "more_info_path": "/vulnerabilities/CVE-2023-5002/63071",
            "specs": [
                "<7.7"
            ],
            "v": "<7.7"
        },
        {
            "advisory": "Affected versions of the pgAdmin package are vulnerable to Information Disclosure due to Insufficiently Protected Credentials in the OAuth2 authentication implementation. The OAuth2 client ID and client secret are improperly exposed\u2014rendered into browser-accessible content such as client-side JavaScript or visible HTML\u2014within the authentication flow. An attacker can exploit this by accessing the OAuth2 login interface (for example, viewing page source or network requests), extracting the exposed client ID and secret, and subsequently using them to impersonate legitimate clients, retrieve user data, or gain unauthorized access to sensitive resources.",
            "cve": "CVE-2024-9014",
            "id": "pyup.io-78770",
            "more_info_path": "/vulnerabilities/CVE-2024-9014/78770",
            "specs": [
                "<8.12"
            ],
            "v": "<8.12"
        },
        {
            "advisory": "Affected versions of the pgadmin4 package are vulnerable to Improper Certificate Validation due to the LDAP authentication mechanism establishing TLS sessions without enforcing server certificate verification under common configurations. In pgAdmin 4 versions up to 9.9, the LDAP authentication flow\u2019s TLS client only validates the LDAP server certificate when a CA certificate, client certificate, and client key are all configured together, so deployments that configure only a CA or rely on default trust stores silently disable certificate checking and accept any presented server certificate.",
            "cve": "CVE-2025-12765",
            "id": "pyup.io-81586",
            "more_info_path": "/vulnerabilities/CVE-2025-12765/81586",
            "specs": [
                "<9.10"
            ],
            "v": "<9.10"
        },
        {
            "advisory": "Affected versions of the pgadmin4 package are vulnerable to Command Injection due to the use of shell=True with user-controllable file path arguments in backup and restore operations on Windows systems. In pgadmin4 versions up to 9.9, the Windows backup and restore utilities construct OS command lines using shell=True and interpolate the provided backup file path directly into the command string without properly neutralizing special characters that the Windows command shell interprets as additional commands.",
            "cve": "CVE-2025-12763",
            "id": "pyup.io-81587",
            "more_info_path": "/vulnerabilities/CVE-2025-12763/81587",
            "specs": [
                "<9.10"
            ],
            "v": "<9.10"
        },
        {
            "advisory": "Affected versions of the pgadmin4 package are vulnerable to Remote Code Execution due to improper validation of PLAIN-format SQL dump files in the restore utility when running in server mode. In affected versions, the use_sql_utility function in web/pgadmin/tools/restore/__init__.py invokes the sql utility on user-supplied PLAIN-format dump files without first checking for psql meta-commands, so lines beginning with backslash (for example \\! or \\i) are treated as executable psql directives that can trigger arbitrary command execution on the pgAdmin server host.",
            "cve": "CVE-2025-12762",
            "id": "pyup.io-81584",
            "more_info_path": "/vulnerabilities/CVE-2025-12762/81584",
            "specs": [
                "<9.10"
            ],
            "v": "<9.10"
        },
        {
            "advisory": "Affected versions of the pgadmin4 package are vulnerable to LDAP Injection resulting in Denial of Service (DoS) due to improper neutralization of special characters in the LDAP search filter used during authentication. In the LDAP authentication flow implemented in web/pgadmin/authenticate/ldap.py, the username parameter from the login form is inserted directly into the configured LDAP search filter without escaping metacharacters such as \u201c*\u201d, allowing attacker-controlled input to expand or otherwise alter the directory search operation.",
            "cve": "CVE-2025-12764",
            "id": "pyup.io-81588",
            "more_info_path": "/vulnerabilities/CVE-2025-12764/81588",
            "specs": [
                "<9.10"
            ],
            "v": "<9.10"
        },
        {
            "advisory": "Affected versions of the pgadmin4 package are vulnerable to Command Injection due to improper meta-command filtering in the restore meta-command filter when processing SQL files beginning with special byte sequences such as a UTF-8 Byte Order Mark (EF BB BF). The has_meta_commands() function in pgadmin4 scans the raw bytes of the SQL file using a regular expression that does not correctly ignore these special bytes, failing to detect meta-commands like \\\\! that can alter command execution.",
            "cve": "CVE-2025-13780",
            "id": "pyup.io-82607",
            "more_info_path": "/vulnerabilities/CVE-2025-13780/82607",
            "specs": [
                "<9.11"
            ],
            "v": "<9.11"
        },
        {
            "advisory": "Affected versions of pgadmin4 are affected by a security vulnerability with Cross-Site Scripting(XSS). If attackers execute any arbitrary HTML/JavaScript in a user's browser through query result rendering, then HTML/JavaScript runs on the browser.",
            "cve": "CVE-2025-2946",
            "id": "pyup.io-76515",
            "more_info_path": "/vulnerabilities/CVE-2025-2946/76515",
            "specs": [
                "<9.2"
            ],
            "v": "<9.2"
        },
        {
            "advisory": "Remote Code Execution security vulnerability in pgAdmin 4 (Query Tool and Cloud Deployment modules). The vulnerability is associated with the 2 POST endpoints; /sqleditor/query_tool/download, where the query_commited parameter and /cloud/deploy endpoint, where the high_availability parameter is unsafely passed to the Python eval() function, allowing arbitrary code execution.",
            "cve": "CVE-2025-2945",
            "id": "pyup.io-76514",
            "more_info_path": "/vulnerabilities/CVE-2025-2945/76514",
            "specs": [
                "<9.2"
            ],
            "v": "<9.2"
        },
        {
            "advisory": "Affected versions of the pgadmin4 package are vulnerable to Origin Validation Error due to missing Cross-Origin Opener Policy (COOP) headers in the OAuth sign-in flow. The `pgadmin.utils.security_headers.set_response_headers` function and the `web/config.py` configuration did not emit a `Cross-Origin-Opener-Policy` header for the OAuth login pages, leaving them in the same browsing context group and allowing a controlling parent window (via `window.opener`, e.g., `window.location.replace()`) to steer the OAuth handshake.",
            "cve": "CVE-2025-9636",
            "id": "pyup.io-79466",
            "more_info_path": "/vulnerabilities/CVE-2025-9636/79466",
            "specs": [
                "<9.8"
            ],
            "v": "<9.8"
        },
        {
            "advisory": "Affected versions of Pgadmin4 are vulnerable to Remote Code Execution (RCE) through the validate binary path API. This vulnerability allows attackers to execute arbitrary code on the server hosting PGAdmin, posing a severe risk to the database management system's integrity and the security of the underlying data.",
            "cve": "CVE-2024-3116",
            "id": "pyup.io-71204",
            "more_info_path": "/vulnerabilities/CVE-2024-3116/71204",
            "specs": [
                "<=8.4"
            ],
            "v": "<=8.4"
        },
        {
            "advisory": "Affected versions of Pgadmin4 are vulnerable to Cross-site Scripting (XSS) via the /settings/store API. An attacker can execute malicious script at the client end by injecting script content into the JSON response.",
            "cve": "CVE-2024-4216",
            "id": "pyup.io-71202",
            "more_info_path": "/vulnerabilities/CVE-2024-4216/71202",
            "specs": [
                "<=8.5"
            ],
            "v": "<=8.5"
        },
        {
            "advisory": "Affected versions of Pgadmin4 are vulnerable to a multi-factor authentication bypass vulnerability. This vulnerability allows an attacker with knowledge of a legitimate account\u2019s username and password may authenticate to the application and perform sensitive actions within the application, such as managing files and executing SQL queries, regardless of the account\u2019s MFA enrollment status.",
            "cve": "CVE-2024-4215",
            "id": "pyup.io-71203",
            "more_info_path": "/vulnerabilities/CVE-2024-4215/71203",
            "specs": [
                "<=8.5"
            ],
            "v": "<=8.5"
        },
        {
            "advisory": "Open redirect vulnerability in pgAdmin 4 versions prior to v6.14 allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having a user to access a specially crafted URL.",
            "cve": "CVE-2023-22298",
            "id": "pyup.io-54613",
            "more_info_path": "/vulnerabilities/CVE-2023-22298/54613",
            "specs": [
                ">=0,<6.14"
            ],
            "v": ">=0,<6.14"
        },
        {
            "advisory": "The pgAdmin server includes an HTTP API that is intended to be used to validate the path a user selects to external PostgreSQL utilities such as pg_dump and pg_restore. The utility is executed by the server to determine what PostgreSQL version it is from. Versions of pgAdmin prior to 6.17 failed to properly secure this API, which could allow an unauthenticated user to call it with a path of their choosing, such as a UNC path to a server they control on a Windows machine. This would cause an appropriately named executable in the target path to be executed by the pgAdmin server.",
            "cve": "CVE-2022-4223",
            "id": "pyup.io-54598",
            "more_info_path": "/vulnerabilities/CVE-2022-4223/54598",
            "specs": [
                ">=0,<6.17"
            ],
            "v": ">=0,<6.17"
        }
    ],
    "pgbedrock": [
        {
            "advisory": "Pgbedrock 0.4.2 includes a security patch for the function 'load_spec' in 'pgbedrock/spec_inspector.py'. It used the unsafe yaml.load() that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/Squarespace/pgbedrock/commit/a217fa419fbb88fd4949ea6db7ca2fa9869cf8e1",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41360",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41360",
            "specs": [
                "<0.4.2"
            ],
            "v": "<0.4.2"
        }
    ],
    "pghoard": [
        {
            "advisory": "A vulnerability has been discovered that could allow an attacker to acquire disk access with privileges equivalent to those of pghoard, allowing for unintended path traversal. Depending on the permissions/privileges assigned to pghoard, this could allow disclosure of sensitive information.",
            "cve": "CVE-2024-56142",
            "id": "pyup.io-76380",
            "more_info_path": "/vulnerabilities/CVE-2024-56142/76380",
            "specs": [
                "<2.6.1-rc"
            ],
            "v": "<2.6.1-rc"
        }
    ],
    "pgmq": [
        {
            "advisory": "Pgmq addresses a SQL injection.",
            "cve": "PVE-2025-79775",
            "id": "pyup.io-79775",
            "more_info_path": "/vulnerabilities/PVE-2025-79775/79775",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        }
    ],
    "pgscatalog-utils": [
        {
            "advisory": "Pgscatalog-utils version 0.5.1 upgrades its fonttools dependency to 4.49.0 from the earlier 4.42.1 in response to addressing the security vulnerability CVE-2023-45139.",
            "cve": "CVE-2023-45139",
            "id": "pyup.io-65587",
            "more_info_path": "/vulnerabilities/CVE-2023-45139/65587",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        }
    ],
    "pheonix-waitress": [
        {
            "advisory": "Pheonix-waitress 1.0.0 includes a fix for CVE-2015-0219.\r\nhttps://www.djangoproject.com/weblog/2015/jan/13/security/",
            "cve": "CVE-2015-0219",
            "id": "pyup.io-49027",
            "more_info_path": "/vulnerabilities/CVE-2015-0219/49027",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Pheonix-waitress 1.4.0 includes a fix for CVE-2019-16785: Waitress through version 1.3.1 implemented a \"MAY\" part of the RFC7230 which states: \"Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR.\" Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. \r\nhttps://github.com/Pylons/waitress/security/advisories/GHSA-pg36-wpm5-g57p",
            "cve": "CVE-2019-16785",
            "id": "pyup.io-49025",
            "more_info_path": "/vulnerabilities/CVE-2019-16785/49025",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Pheonix-waitress 1.4.2 includes a fix for CVE-2019-16789: In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure.",
            "cve": "CVE-2019-16789",
            "id": "pyup.io-49024",
            "more_info_path": "/vulnerabilities/CVE-2019-16789/49024",
            "specs": [
                "<1.4.2"
            ],
            "v": "<1.4.2"
        },
        {
            "advisory": "Pheonix-waitress 2.1.1 includes a fix for CVE-2022-24761: When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python's 'int()' to parse strings into integers, leading to '+10' to be parsed as '10'', or '0x01' to be parsed as '1', where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. A workaround is available. When deploying a proxy in front of waitress, turning on functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality.\r\nhttps://github.com/Pylons/waitress/security/advisories/GHSA-4f7p-27jc-3c36",
            "cve": "CVE-2022-24761",
            "id": "pyup.io-49021",
            "more_info_path": "/vulnerabilities/CVE-2022-24761/49021",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Pheonix-waitress 1.4.3 includes a fix for CVE-2020-5236: Catastrophic backtracking in regex allows Denial of Service.\r\nhttps://github.com/Pylons/waitress/security/advisories/GHSA-73m2-3pwg-5fgc",
            "cve": "CVE-2020-5236",
            "id": "pyup.io-49022",
            "more_info_path": "/vulnerabilities/CVE-2020-5236/49022",
            "specs": [
                "==1.4.2"
            ],
            "v": "==1.4.2"
        }
    ],
    "pheonixappapi": [
        {
            "advisory": "Affected versions of the PheonixAppAPI package are vulnerable to Information Disclosure due to visible encoding/decoding language maps embedded in the source code. The exposed encoding map resides directly within the `PheonixAppAPI` module (e.g., in the encoder decoding mapping structures), and the code fails to obfuscate or restrict access to this mapping information. A local user with access to the PheonixAppAPI codebase can view the encoding maps in plaintext, potentially aiding reverse engineering or leaking implementation details.",
            "cve": "CVE-2024-41951",
            "id": "pyup.io-78744",
            "more_info_path": "/vulnerabilities/CVE-2024-41951/78744",
            "specs": [
                "<0.2.5"
            ],
            "v": "<0.2.5"
        }
    ],
    "phileo": [
        {
            "advisory": "Phileo before 1.1 allows users to like anything and everything, which could potentially lead to security problems (ex. liking entries in permission tables, and thus seeing their content; liking administrative users and thus getting their username).\r\nhttps://github.com/pinax/pinax-likes/commit/2b906a4f85acc54c72d4a9f569da4ecf63a59eb3",
            "cve": "PVE-2021-25930",
            "id": "pyup.io-25930",
            "more_info_path": "/vulnerabilities/PVE-2021-25930/25930",
            "specs": [
                "<1.1"
            ],
            "v": "<1.1"
        }
    ],
    "phoenix-letter": [
        {
            "advisory": "Phoenix-letter 0.2.0 adds the flag '--aws-keys' to securely ask for the AWS credentials to avoid keeping sensitive information accessible in plain text. Without this flag, it falls back to the Boto3 default credential search.",
            "cve": "PVE-2021-39438",
            "id": "pyup.io-39438",
            "more_info_path": "/vulnerabilities/PVE-2021-39438/39438",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "phoenix-ws": [
        {
            "advisory": "Phoenix-ws 1.0.6 includes a security fix: All of the source code, files, and folders in 'phoenix_files/extensions/' are available to end users through a simple HTTP GET request.\r\nhttps://github.com/NovaAndrom3da/Phoenix/commit/47952180a60a94ff1dfa2e0117fca9a5052bf193",
            "cve": "PVE-2023-55195",
            "id": "pyup.io-55195",
            "more_info_path": "/vulnerabilities/PVE-2023-55195/55195",
            "specs": [
                ">=0,<1.0.6"
            ],
            "v": ">=0,<1.0.6"
        }
    ],
    "phone-gen": [
        {
            "advisory": "Phone-gen version 2.4.4 addresses a security issue where the Black library was vulnerable to Regular Expression Denial of Service (ReDoS), as identified in CVE-2024-21503.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-68048",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/68048",
            "specs": [
                "<2.4.4"
            ],
            "v": "<2.4.4"
        }
    ],
    "phonenumbers": [
        {
            "advisory": "Phonenumbers 8.3.1 contains a security improvement of the getNationalSignificantNumber function to make it more robust against malicious input.",
            "cve": "PVE-2021-39441",
            "id": "pyup.io-39441",
            "more_info_path": "/vulnerabilities/PVE-2021-39441/39441",
            "specs": [
                "<8.3.1"
            ],
            "v": "<8.3.1"
        }
    ],
    "photocrawl": [
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2020-15999",
            "id": "pyup.io-43530",
            "more_info_path": "/vulnerabilities/CVE-2020-15999/43530",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-43535",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/43535",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-43534",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/43534",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-25287",
            "id": "pyup.io-43539",
            "more_info_path": "/vulnerabilities/CVE-2021-25287/43539",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-43546",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/43546",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-43533",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/43533",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-43545",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/43545",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-43541",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/43541",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-43532",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/43532",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-43547",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/43547",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-43542",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/43542",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-43537",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/43537",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-43543",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/43543",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-43538",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/43538",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-43536",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/43536",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-43544",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/43544",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-25288",
            "id": "pyup.io-43540",
            "more_info_path": "/vulnerabilities/CVE-2021-25288/43540",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-41714",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/41714",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Photocrawl 0.3.1 updates the minimum version requirement of \"Pillow\" to 8.3.2 to include security patches.",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-43531",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/43531",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "phpgp": [
        {
            "advisory": "Affected versions of phpgp were potentially vulnerable to insufficiently protected credentials. An attacker could potentially access environment variables containing cryptographic keys and passphrases, leading to unauthorized decryption or signing of data. The issue existed in the server and CLI components. This issue is fixed in version 1.0.0. Users should ensure sensitive data is not stored in environment variables.",
            "cve": "PVE-2025-76687",
            "id": "pyup.io-76687",
            "more_info_path": "/vulnerabilities/PVE-2025-76687/76687",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "phylum": [
        {
            "advisory": "Phylum 0.17.1 sanitizes user input to guard against possible cmd injection.\r\nhttps://github.com/phylum-dev/phylum-ci/pull/144",
            "cve": "PVE-2022-51466",
            "id": "pyup.io-51466",
            "more_info_path": "/vulnerabilities/PVE-2022-51466/51466",
            "specs": [
                "<0.17.1"
            ],
            "v": "<0.17.1"
        }
    ],
    "physiofit": [
        {
            "advisory": "Physiofit 3.3.3 updates its pyarrow dependency to version ^14.0.1 in response to the security vulnerability identified as CVE-2019-12408.\r\nhttps://github.com/MetaSys-LISBP/PhysioFit/commit/187270cfc3372773785f3fe96b9616cdaf3f6d78",
            "cve": "CVE-2019-12408",
            "id": "pyup.io-65788",
            "more_info_path": "/vulnerabilities/CVE-2019-12408/65788",
            "specs": [
                "<3.3.3"
            ],
            "v": "<3.3.3"
        },
        {
            "advisory": "Physiofit 3.3.3 updates its pyarrow dependency to version ^14.0.1 in response to the security vulnerability identified as CVE-2019-12410.\r\nhttps://github.com/MetaSys-LISBP/PhysioFit/commit/187270cfc3372773785f3fe96b9616cdaf3f6d78",
            "cve": "CVE-2019-12410",
            "id": "pyup.io-65789",
            "more_info_path": "/vulnerabilities/CVE-2019-12410/65789",
            "specs": [
                "<3.3.3"
            ],
            "v": "<3.3.3"
        },
        {
            "advisory": "Physiofit 3.3.3 updates its pillow dependency to version ^10.2.0 in response to the security vulnerability identified as CVE-2023-5044.\r\nhttps://github.com/MetaSys-LISBP/PhysioFit/commit/187270cfc3372773785f3fe96b9616cdaf3f6d78",
            "cve": "CVE-2023-50447",
            "id": "pyup.io-65770",
            "more_info_path": "/vulnerabilities/CVE-2023-50447/65770",
            "specs": [
                "<3.3.3"
            ],
            "v": "<3.3.3"
        }
    ],
    "pi-mqtt-gpio": [
        {
            "advisory": "Pi-mqtt-gpio 0.5.2 updates PyYAML to include a security fix.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-39464",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/39464",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        }
    ],
    "picamerax": [
        {
            "advisory": "Picamerax version 21.9.8 upgrades its Pillow dependency to address the security vulnerability identified in CVE-2021-34552.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-66852",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/66852",
            "specs": [
                "<21.9.8"
            ],
            "v": "<21.9.8"
        }
    ],
    "picard": [
        {
            "advisory": "Picard 2.10 disables the Qt WebP plugin for Windows and macOS binary builds to mitigate the libwebp vulnerability, identified as CVE-2023-4863. This security measure addresses a critical issue within the libwebp library that could potentially lead to security breaches. By disabling the Qt WebP plugin, Picard ensures that its application is protected from exploits targeting this vulnerability.\r\n# This only affects Windows and macOS users",
            "cve": "PVE-2024-71813",
            "id": "pyup.io-71813",
            "more_info_path": "/vulnerabilities/PVE-2024-71813/71813",
            "specs": [
                "<2.10"
            ],
            "v": "<2.10"
        }
    ],
    "piccolo": [
        {
            "advisory": "Affected versions of the Piccolo package are vulnerable to Information Disclosure due to inconsistent response times in the `BaseUser.login` method. The vulnerability arises because the method returns immediately when a user does not exist, skipping the time-consuming hash comparison, which creates a noticeable timing discrepancy. An attacker can exploit this by measuring response times to determine valid usernames, potentially facilitating further attacks such as password spraying, leading to unauthorized access to user accounts.",
            "cve": "CVE-2023-41885",
            "id": "pyup.io-65350",
            "more_info_path": "/vulnerabilities/CVE-2023-41885/65350",
            "specs": [
                "<0.121.0",
                ">=1.0a1,<=1.0a2"
            ],
            "v": "<0.121.0,>=1.0a1,<=1.0a2"
        },
        {
            "advisory": "Piccolo 0.2 uses 'QueryString' internally to represent queries (instead of raw strings) to harden against SQL injection.",
            "cve": "PVE-2021-38919",
            "id": "pyup.io-38919",
            "more_info_path": "/vulnerabilities/PVE-2021-38919/38919",
            "specs": [
                "<0.2"
            ],
            "v": "<0.2"
        },
        {
            "advisory": "Piccolo 1.1.1 includes a fix for CVE-2023-47128: Prior to version 1.1.1, the handling of named transaction 'savepoints' in all database implementations is vulnerable to SQL Injection via f-strings. While the likelihood of an end developer exposing a 'savepoints' 'name' parameter to a user is highly unlikely, it would not be unheard of. If a malicious user was able to abuse this functionality they would have essentially direct access to the database and the ability to modify data to the level of permissions associated with the database user. A non exhaustive list of actions possible based on database permissions is: Read all data stored in the database, including usernames and password hashes; insert arbitrary data into the database, including modifying existing records; and gain a shell on the underlying server.\r\nhttps://github.com/piccolo-orm/piccolo/security/advisories/GHSA-xq59-7jf3-rjc6",
            "cve": "CVE-2023-47128",
            "id": "pyup.io-63181",
            "more_info_path": "/vulnerabilities/CVE-2023-47128/63181",
            "specs": [
                ">=0,<1.1.1"
            ],
            "v": ">=0,<1.1.1"
        }
    ],
    "piccolo-admin": [
        {
            "advisory": "Piccolo-admin 0.13.1 updates its NPM dependency 'dns-packet' to v1.3.4 to include a security fix.",
            "cve": "CVE-2021-23386",
            "id": "pyup.io-49111",
            "more_info_path": "/vulnerabilities/CVE-2021-23386/49111",
            "specs": [
                "<0.13.1"
            ],
            "v": "<0.13.1"
        },
        {
            "advisory": "Piccolo-admin 0.13.1 updates its NPM dependency 'ws' to v6.2.2 to include a security fix.",
            "cve": "CVE-2021-32640",
            "id": "pyup.io-40867",
            "more_info_path": "/vulnerabilities/CVE-2021-32640/40867",
            "specs": [
                "<0.13.1"
            ],
            "v": "<0.13.1"
        },
        {
            "advisory": "Piccolo-admin 0.9.1 upgrades the node requirements because of a security warning.",
            "cve": "PVE-2021-38643",
            "id": "pyup.io-38643",
            "more_info_path": "/vulnerabilities/PVE-2021-38643/38643",
            "specs": [
                "<0.9.1"
            ],
            "v": "<0.9.1"
        },
        {
            "advisory": "Piccolo Admin is an admin interface/content management system for Python, built on top of Piccolo. Piccolo's admin panel allows media files to be uploaded. As a default, SVG is an allowed file type for upload. An attacker can upload an SVG which when loaded can allow arbitrary access to the admin page. This vulnerability was patched in version 1.3.2. See CVE-2024-30248.",
            "cve": "CVE-2024-30248",
            "id": "pyup.io-70646",
            "more_info_path": "/vulnerabilities/CVE-2024-30248/70646",
            "specs": [
                "<1.3.2"
            ],
            "v": "<1.3.2"
        }
    ],
    "picklescan": [
        {
            "advisory": "Picklescan 0.0.13 includes a security fix: The way picklescan handled memo didn't look at the argument, so it was possible to have a different memo and use STACK_GLOBAL to bypass allow-list checking.\r\nhttps://github.com/mmaitre314/picklescan/issues/22",
            "cve": "PVE-2023-62974",
            "id": "pyup.io-62974",
            "more_info_path": "/vulnerabilities/PVE-2023-62974/62974",
            "specs": [
                "<0.0.13"
            ],
            "v": "<0.0.13"
        },
        {
            "advisory": "Affected versions of Picklescan are vulnerable to Reliance on Untrusted Inputs in a Security Decision. Picklescan fails to detect hidden pickle files embedded in PyTorch model archives due to its reliance on file extensions for detection. This allows an attacker to embed a secondary, malicious pickle file with a non-standard extension inside a model archive, which remains undetected by picklescan but is still loaded by PyTorch's torch.load() function. This can lead to arbitrary code execution when the model is loaded.",
            "cve": "CVE-2025-1889",
            "id": "pyup.io-75762",
            "more_info_path": "/vulnerabilities/CVE-2025-1889/75762",
            "specs": [
                "<0.0.22"
            ],
            "v": "<0.0.22"
        },
        {
            "advisory": "Affected versions of Picklescan are vulnerable to Incomplete List of Disallowed Inputs. An unsafe deserialization vulnerability in Python\u2019s pickle module allows an attacker to bypass static analysis tools like Picklescan and execute arbitrary code during deserialization. This can be exploited to run pip install and fetch a malicious package, enabling remote code execution (RCE) upon package installation.",
            "cve": "CVE-2025-1716",
            "id": "pyup.io-75734",
            "more_info_path": "/vulnerabilities/CVE-2025-1716/75734",
            "specs": [
                "<0.0.22"
            ],
            "v": "<0.0.22"
        },
        {
            "advisory": "PickleScan is vulnerable to a ZIP archive manipulation attack that causes it to crash when attempting to extract and scan PyTorch model archives. By modifying the filename in the ZIP header while keeping the original filename in the directory listing, an attacker can make PickleScan raise a BadZipFile error. However, PyTorch's more forgiving ZIP implementation still allows the model to be loaded, enabling malicious payloads to bypass detection.",
            "cve": "CVE-2025-1944",
            "id": "pyup.io-75819",
            "more_info_path": "/vulnerabilities/CVE-2025-1944/75819",
            "specs": [
                "<0.0.23"
            ],
            "v": "<0.0.23"
        },
        {
            "advisory": "PickleScan fails to detect malicious pickle files inside PyTorch model archives when certain ZIP file flag bits are modified. By flipping specific bits in the ZIP file headers, an attacker can embed malicious pickle files that remain undetected by PickleScan while still being successfully loaded by PyTorch's torch.load(). This can lead to arbitrary code execution when loading a compromised model.",
            "cve": "CVE-2025-1945",
            "id": "pyup.io-75794",
            "more_info_path": "/vulnerabilities/CVE-2025-1945/75794",
            "specs": [
                "<0.0.23"
            ],
            "v": "<0.0.23"
        },
        {
            "advisory": "An unsafe deserialization vulnerability in Python\u2019s pickle module allows an attacker to bypass static analysis tools like Picklescan and execute arbitrary code during deserialization. This can be exploited by import some built-in function in Numpy library that indrectly call some dangerous function like exec() to execute some python code as a parameter, which the attacker can import dangerous library inside like os library and execute arbitrary OS commands.",
            "cve": "PVE-2025-76529",
            "id": "pyup.io-76529",
            "more_info_path": "/vulnerabilities/PVE-2025-76529/76529",
            "specs": [
                "<0.0.25"
            ],
            "v": "<0.0.25"
        },
        {
            "advisory": "Using timeit.timeit() function, which is a built-in python library function to execute remote pickle file.",
            "cve": "PVE-2025-76533",
            "id": "pyup.io-76533",
            "more_info_path": "/vulnerabilities/PVE-2025-76533/76533",
            "specs": [
                "<0.0.25"
            ],
            "v": "<0.0.25"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Information Disclosure due to insufficient detection of malicious pickle payloads that exfiltrate data via DNS queries. The security scanner fails to detect pickle payloads that use ssl.get_server_certificate and linecache modules to read sensitive files and encode their contents as DNS subdomains, as these standard library modules are not included in picklescan's blacklist.",
            "cve": "CVE-2025-46417",
            "id": "pyup.io-76534",
            "more_info_path": "/vulnerabilities/CVE-2025-46417/76534",
            "specs": [
                "<0.0.25"
            ],
            "v": "<0.0.25"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Improper Input Validation due to an off-by-one error in the _list_globals parser for the STACK_GLOBAL opcode. In src/picklescan/scanner.py, _list_globals iterates for offset in range(1, n) and ignores the operand at index 0 and, combined with not recognizing legacy string opcodes (STRING, BINSTRING, SHORT_BINSTRING), triggers the \u201cFound \u2026 values for STACK_GLOBAL \u2026 instead of 2.\u201d path and fails to record the dangerous global reference. An unauthenticated attacker can craft a malicious pickle that places one argument at index 0 and calls os.system via STACK_GLOBAL, causing picklescan to raise and bypass its detection so the artifact appears clean, enabling distribution of payloads that may lead to arbitrary command execution when later unpickled by downstream consumers.",
            "cve": "PVE-2025-78702",
            "id": "pyup.io-78702",
            "more_info_path": "/vulnerabilities/PVE-2025-78702/78702",
            "specs": [
                "<0.0.27"
            ],
            "v": "<0.0.27"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to insufficient detection of malicious PyTorch functions in pickle files. The torch._dynamo.guards.GuardBuilder.get function can be invoked within a crafted __reduce__ method to execute arbitrary code through string evaluation, but this dangerous function is not recognised by picklescan's security scanning algorithms.",
            "cve": "PVE-2025-79068",
            "id": "pyup.io-79068",
            "more_info_path": "/vulnerabilities/PVE-2025-79068/79068",
            "specs": [
                "<0.0.28"
            ],
            "v": "<0.0.28"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to insufficient detection of malicious PyTorch functions in pickle files. The torch.utils.data.datapipes.utils.decoder.basichandlers function can be invoked within a crafted __reduce__ method to deserialise nested malicious pickle data, but this dangerous function is not recognised by picklescan's security scanning algorithms.",
            "cve": "PVE-2025-79071",
            "id": "pyup.io-79071",
            "more_info_path": "/vulnerabilities/PVE-2025-79071/79071",
            "specs": [
                "<0.0.28"
            ],
            "v": "<0.0.28"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to insufficient detection of malicious PyTorch functions in pickle files. The torch.utils.bottleneck.__main__.run_cprofile function can be used within a crafted __reduce__ method to execute arbitrary code, but this dangerous function is not flagged by picklescan's security scanning algorithms.",
            "cve": "PVE-2025-79067",
            "id": "pyup.io-79067",
            "more_info_path": "/vulnerabilities/PVE-2025-79067/79067",
            "specs": [
                "<0.0.28"
            ],
            "v": "<0.0.28"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to insufficient detection of malicious PyTorch functions in pickle files. The torch.fx.experimental.symbolic_shapes.ShapeEnv.evaluate_guards_expression function can be invoked within a crafted __reduce__ method to execute arbitrary code through expression evaluation, but this dangerous function is not recognised by picklescan's security scanning algorithms.",
            "cve": "PVE-2025-79069",
            "id": "pyup.io-79069",
            "more_info_path": "/vulnerabilities/PVE-2025-79069/79069",
            "specs": [
                "<0.0.28"
            ],
            "v": "<0.0.28"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to insufficient detection of malicious PyTorch functions in pickle files. The torch.jit.unsupported_tensor_ops.execWrapper function can be invoked within a crafted __reduce__ method to execute arbitrary Python code with provided global and local contexts, but this dangerous function is not recognised by picklescan's security scanning algorithms.",
            "cve": "PVE-2025-79072",
            "id": "pyup.io-79072",
            "more_info_path": "/vulnerabilities/PVE-2025-79072/79072",
            "specs": [
                "<0.0.28"
            ],
            "v": "<0.0.28"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to insufficient detection of malicious PyTorch functions in pickle files. The torch.utils.collect_env.run function can be invoked within a crafted __reduce__ method to execute arbitrary system commands, but this dangerous function is not recognised by picklescan's security scanning algorithms.",
            "cve": "PVE-2025-79070",
            "id": "pyup.io-79070",
            "more_info_path": "/vulnerabilities/PVE-2025-79070/79070",
            "specs": [
                "<0.0.28"
            ],
            "v": "<0.0.28"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to insufficient detection of malicious PyTorch functions in pickle files. The torch.utils._config_module.ConfigModule.load_config function can be invoked within a crafted __reduce__ method to deserialise nested malicious pickle data, but this dangerous function is not recognised by picklescan's security scanning algorithms.",
            "cve": "PVE-2025-79073",
            "id": "pyup.io-79073",
            "more_info_path": "/vulnerabilities/PVE-2025-79073/79073",
            "specs": [
                "<0.0.28"
            ],
            "v": "<0.0.28"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Protection Mechanism Failure due to extension-based dispatch in `scan_bytes` that does not fall back to standard Pickle scanning after PyTorch parsing errors. In `src/picklescan/scanner.py`, `scan_bytes` routes files with a PyTorch-related `file_ext` to `scan_pytorch` and, when parsing fails, returns an error without invoking `scan_pickle_bytes`, allowing true pickle files renamed to `.bin` or `.pt` to evade dangerous-global detection.",
            "cve": "CVE-2025-10155",
            "id": "pyup.io-79489",
            "more_info_path": "/vulnerabilities/CVE-2025-10155/79489",
            "specs": [
                "<0.0.31"
            ],
            "v": "<0.0.31"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Protection Mechanism Failure due to exact-match filtering of unsafe globals that permits bypass via subclass or submodule imports. In `src/picklescan/scanner.py`, the scanner computes `unsafe_filter = _unsafe_globals.get(g.module)` and only compares `g.module` keys, so dangerous imports within the same namespace (for example, `asyncio.unix_events._UnixSubprocessTransport`) are not matched and are misclassified as \u201csuspicious\u201d instead of \u201cdangerous.\u201d",
            "cve": "CVE-2025-10157",
            "id": "pyup.io-79487",
            "more_info_path": "/vulnerabilities/CVE-2025-10157/79487",
            "specs": [
                "<0.0.31"
            ],
            "v": "<0.0.31"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Protection Mechanism Failure due to aborting ZIP archive scans on corrupted CRC entries and returning no results. The ZIP archive scanning path, implemented using Python\u2019s `zipfile.ZipFile` and invoked via the `-p/--path` mode, raises an error on a bad CRC and fails to iterate and inspect remaining members, leaving embedded Pickle payloads unanalyzed.",
            "cve": "CVE-2025-10156",
            "id": "pyup.io-79488",
            "more_info_path": "/vulnerabilities/CVE-2025-10156/79488",
            "specs": [
                "<0.0.31"
            ],
            "v": "<0.0.31"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Arbitrary File Writing due to an incomplete blocklist that fails to prevent the use of the distutils module for file operations. While picklescan blocks open() and shutil to prevent file manipulation, the distutils.file_util.write_file function remains accessible and can be exploited through crafted pickle payloads to write arbitrary content to any file path on the system.",
            "cve": "PVE-2025-83254",
            "id": "pyup.io-83254",
            "more_info_path": "/vulnerabilities/PVE-2025-83254/83254",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to misclassification of the pty.spawn function as \"suspicious\" rather than \"dangerous\" in the unsafe globals detection system. The pty module, specifically the spawn function, is absent from picklescan's list of dangerous globals despite its ability to execute arbitrary shell commands through pseudo-terminal operations, allowing attackers to construct malicious pickle payloads that pass security scans.",
            "cve": "PVE-2025-83558",
            "id": "pyup.io-83558",
            "more_info_path": "/vulnerabilities/PVE-2025-83558/83558",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to remote code execution (RCE) due to incomplete detection of the NumPy F2PY gadget numpy.f2py.crackfortran._eval_length. The scanner logic (notably the blocklist/allowlist handling in src/picklescan/scanner.py, including _unsafe_globals and scan-result construction) fails to flag pickles whose __reduce__ returns _eval_length with attacker-controlled arguments; this is fixed by adding numpy.f2py to the unsafe globals and tightening submodule handling in commit 70c1c6.",
            "cve": "PVE-2025-83730",
            "id": "pyup.io-83730",
            "more_info_path": "/vulnerabilities/PVE-2025-83730/83730",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to remote code execution (RCE) due to missing detection of the built-in operator.methodcaller gadget. The scanner\u2019s allow/block lists (_safe_globals / _unsafe_globals) in src/picklescan/scanner.py are used to classify imported globals as safe or dangerous, but operator.methodcaller was not present in the _unsafe_globals blocklist and was added in the fix commit 70c1c6c31beb6baaf52c8db1b6c3c0e84a6f9dab.",
            "cve": "PVE-2025-83728",
            "id": "pyup.io-83728",
            "more_info_path": "/vulnerabilities/PVE-2025-83728/83728",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to remote code execution (RCE) due to incomplete detection of dangerous globals in malicious pickle payloads. The scanner logic in src/picklescan/scanner.py relies on a blocklist/allowlist of globals but fails to flag the NumPy F2PY gadget numpy.f2py.crackfortran.getlincoef when it is returned from __reduce__, allowing attacker-controlled arguments to pass scanning.",
            "cve": "PVE-2025-83731",
            "id": "pyup.io-83731",
            "more_info_path": "/vulnerabilities/PVE-2025-83731/83731",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to remote code execution (RCE) due to a missing detection of the numpy.f2py.crackfortran._eval_length pickle gadget. The scanner logic in src/picklescan/scanner.py relies on _unsafe_globals and module-resolution in _build_scan_result_from_raw_globals, but it failed to classify numpy.f2py (and its submodules) as dangerous, allowing a __reduce__ payload that returns _eval_length with attacker-controlled arguments to evade detection.",
            "cve": "PVE-2025-83732",
            "id": "pyup.io-83732",
            "more_info_path": "/vulnerabilities/PVE-2025-83732/83732",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to remote code execution due to an incomplete, unsafe-globals blocklist that can be bypassed. The scanner logic in src/picklescan/scanner.py relies on _unsafe_globals and fails to flag numpy.f2py.crackfortran.param_eval (invoked via a pickle object\u2019s __reduce__), which was addressed by adding numpy.f2py to the blocklist.",
            "cve": "PVE-2025-83737",
            "id": "pyup.io-83737",
            "more_info_path": "/vulnerabilities/PVE-2025-83737/83737",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to remote code execution (RCE) due to the missing detection of numpy.f2py.crackfortran.myeval during pickle safety scanning. The scanner\u2019s unsafe-global detection logic (block/allow-listing in src/picklescan/scanner.py) fails to flag pickle payloads that invoke numpy.f2py.crackfortran.myeval.",
            "cve": "PVE-2025-83740",
            "id": "pyup.io-83740",
            "more_info_path": "/vulnerabilities/PVE-2025-83740/83740",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to failure to detect dangerous functions within the numpy.f2py.crackfortran module that invoke eval() on arbitrary user-controlled strings. The numpy.f2py.crackfortran.getlincoef function, along with other functions in the same module such as _eval_length, accepts string parameters that are directly passed to Python's eval() function without sanitisation, enabling arbitrary code execution through expression injection.",
            "cve": "PVE-2025-83559",
            "id": "pyup.io-83559",
            "more_info_path": "/vulnerabilities/PVE-2025-83559/83559",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to an incomplete blocklist that only restricts specific functions within the pydoc and operator modules rather than blocking the entire modules.",
            "cve": "PVE-2025-83556",
            "id": "pyup.io-83556",
            "more_info_path": "/vulnerabilities/PVE-2025-83556/83556",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to an incomplete blocklist that fails to prevent the use of the ctypes module for direct system-level operations. The ctypes module provides a foreign function interface that enables loading of dynamic link libraries (DLLs), direct invocation of C functions, and manipulation of raw memory pointers, effectively bypassing all higher-level Python security restrictions.",
            "cve": "PVE-2025-83555",
            "id": "pyup.io-83555",
            "more_info_path": "/vulnerabilities/PVE-2025-83555/83555",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Remote Code Execution due to failure to detect the pty.spawn function as a dangerous operation within pickle files. The pty.spawn function, part of Python's standard pty module for pseudo-terminal operations, can spawn arbitrary shell processes and execute system commands without restriction, yet picklescan does not include it in its blocklist of dangerous functions.",
            "cve": "PVE-2025-83557",
            "id": "pyup.io-83557",
            "more_info_path": "/vulnerabilities/PVE-2025-83557/83557",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Arbitrary File Writing due to an incomplete blocklist that fails to prevent the use of the distutils module for file operations. While picklescan blocks open() and shutil to prevent file manipulation, the distutils.file_util.write_file function remains accessible and can be exploited through crafted pickle payloads to write arbitrary content to any file path on the system.",
            "cve": "PVE-2025-83560",
            "id": "pyup.io-83560",
            "more_info_path": "/vulnerabilities/PVE-2025-83560/83560",
            "specs": [
                "<0.0.33"
            ],
            "v": "<0.0.33"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to remote code execution (RCE) due to incomplete detection of dangerous pickle globals. The scanning logic in src/picklescan/scanner.py relies on the _unsafe_globals denylist to flag suspicious imports/functions but omitted the built-in _operator.attrgetter, allowing malicious pickle payloads to evade detection.",
            "cve": "PVE-2025-83729",
            "id": "pyup.io-83729",
            "more_info_path": "/vulnerabilities/PVE-2025-83729/83729",
            "specs": [
                "<0.0.34"
            ],
            "v": "<0.0.34"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Improper Input Validation due to an incomplete denylist for dangerous pickle globals. The picklescan scanning logic in src/picklescan/scanner.py fails to flag the _io.FileIO and urllib.request.urlopen call targets during pickle inspection, allowing attacker-controlled objects using __reduce__ to bypass RCE-focused keyword checks.",
            "cve": "PVE-2026-84323",
            "id": "pyup.io-84323",
            "more_info_path": "/vulnerabilities/PVE-2026-84323/84323",
            "specs": [
                "<0.0.35"
            ],
            "v": "<0.0.35"
        },
        {
            "advisory": "Affected versions of the picklescan package are vulnerable to Improper Input Validation due to incomplete detection of dangerous pickle globals. The src/picklescan/scanner.py scanning logic relies on a hard-coded DANGEROUS_GLOBALS map, but affected versions did not flag _io.FileIO or urllib.request.urlopen, allowing malicious GLOBAL references to evade detection.",
            "cve": "PVE-2026-84080",
            "id": "pyup.io-84080",
            "more_info_path": "/vulnerabilities/PVE-2026-84080/84080",
            "specs": [
                "<0.0.35"
            ],
            "v": "<0.0.35"
        }
    ],
    "piecash": [
        {
            "advisory": "Piecash has updated `pymysql` from version 0.10.1 to 1.1.1 to address CVE-2024-36039.",
            "cve": "CVE-2024-36039",
            "id": "pyup.io-72177",
            "more_info_path": "/vulnerabilities/CVE-2024-36039/72177",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Piecash has updated `requests` from version 2.24.0 to 2.32.2 to address CVE-2024-35195.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-72178",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/72178",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Piecash has updated the `idna` package from version 2.10 to 3.7 to address CVE-2024-3651.",
            "cve": "CVE-2024-3651",
            "id": "pyup.io-72161",
            "more_info_path": "/vulnerabilities/CVE-2024-3651/72161",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        }
    ],
    "pigar": [
        {
            "advisory": "Pigar 0.9.1 fixes some potential security vulnerabilities upgrading its dependency 'requests' to v2.21.0.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36904",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36904",
            "specs": [
                "<0.9.1"
            ],
            "v": "<0.9.1"
        },
        {
            "advisory": "Pigar 2.0.3 updates its dependency 'certifi' to version '2022.12.7' to include a security fix.\r\nhttps://github.com/damnever/pigar/commit/34e1e6b957ce78438ee1fbd0e5c94535ebab7179\r\nhttps://github.com/advisories/GHSA-43fp-rhv2-5gv8",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-59148",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/59148",
            "specs": [
                "<2.0.3"
            ],
            "v": "<2.0.3"
        }
    ],
    "piicatcher": [
        {
            "advisory": "Piicatcher 0.12.2 updates its dependency 'cryptography' to v3.2.1 to include a security fix.",
            "cve": "CVE-2020-25659",
            "id": "pyup.io-41165",
            "more_info_path": "/vulnerabilities/CVE-2020-25659/41165",
            "specs": [
                "<0.12.2"
            ],
            "v": "<0.12.2"
        },
        {
            "advisory": "Piicatcher 0.14.0 updates its dependency 'pydantic' to v1.7.4 to include a security fix.",
            "cve": "CVE-2021-29510",
            "id": "pyup.io-41186",
            "more_info_path": "/vulnerabilities/CVE-2021-29510/41186",
            "specs": [
                "<0.14.0"
            ],
            "v": "<0.14.0"
        },
        {
            "advisory": "Piicatcher 0.14.0 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-49114",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/49114",
            "specs": [
                "<0.14.0"
            ],
            "v": "<0.14.0"
        }
    ],
    "pikepdf": [
        {
            "advisory": "Pikepdf 1.3.0 throughout 2.9.2 allows XXE when parsing XMP metadata entries via models/metadata.py",
            "cve": "CVE-2021-29421",
            "id": "pyup.io-40137",
            "more_info_path": "/vulnerabilities/CVE-2021-29421/40137",
            "specs": [
                ">=1.3.0,<=2.9.2"
            ],
            "v": ">=1.3.0,<=2.9.2"
        }
    ],
    "pillow": [
        {
            "advisory": "Pillow 10.0.0 includes a fix for CVE-2023-44271: Denial of Service that uncontrollably allocates memory to process a given task, potentially causing a service to crash by having it run out of memory. This occurs for truetype in ImageFont when textlength in an ImageDraw instance operates on a long text argument.\r\nhttps://github.com/python-pillow/Pillow/pull/7244",
            "cve": "CVE-2023-44271",
            "id": "pyup.io-62156",
            "more_info_path": "/vulnerabilities/CVE-2023-44271/62156",
            "specs": [
                "<10.0.0"
            ],
            "v": "<10.0.0"
        },
        {
            "advisory": "Pillow is affected by an arbitrary code execution vulnerability. If an attacker has control over the keys passed to the environment argument of PIL.ImageMath.eval(), they may be able to execute arbitrary code.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/10.2.0.html",
            "cve": "CVE-2023-50447",
            "id": "pyup.io-64436",
            "more_info_path": "/vulnerabilities/CVE-2023-50447/64436",
            "specs": [
                "<10.2.0"
            ],
            "v": "<10.2.0"
        },
        {
            "advisory": "Pillow is potentially vulnerable to DoS attacks through PIL.ImageFont.ImageFont.getmask(). A decompression bomb check has also been added to the affected function.",
            "cve": "PVE-2024-64437",
            "id": "pyup.io-64437",
            "more_info_path": "/vulnerabilities/PVE-2024-64437/64437",
            "specs": [
                "<10.2.0"
            ],
            "v": "<10.2.0"
        },
        {
            "advisory": "Pillow 10.3.0 introduces a security update addressing CVE-2024-28219 by replacing certain functions with strncpy to prevent buffer overflow issues.",
            "cve": "CVE-2024-28219",
            "id": "pyup.io-67136",
            "more_info_path": "/vulnerabilities/CVE-2024-28219/67136",
            "specs": [
                "<10.3.0"
            ],
            "v": "<10.3.0"
        },
        {
            "advisory": "pillow before 2.3.1 makes insecure use of tempfile.mktemp (CVE-2014-1933).",
            "cve": "CVE-2014-1933",
            "id": "pyup.io-39580",
            "more_info_path": "/vulnerabilities/CVE-2014-1933/39580",
            "specs": [
                "<2.3.1"
            ],
            "v": "<2.3.1"
        },
        {
            "advisory": "pillow before 2.3.1 makes insecure use of tempfile.mktemp (CVE-2014-1932).",
            "cve": "CVE-2014-1932",
            "id": "pyup.io-25931",
            "more_info_path": "/vulnerabilities/CVE-2014-1932/25931",
            "specs": [
                "<2.3.1"
            ],
            "v": "<2.3.1"
        },
        {
            "advisory": "Pillow versions affected versions include a fix for CVE-2014-3589: PIL/IcnsImagePlugin.py in Python Imaging Library (PIL) and Pillow affected versions allow remote attackers to cause a denial of service via a crafted block size.\r\nhttps://github.com/python-pillow/Pillow/commit/205e056f8f9b06ed7b925cf8aa0874bc4aaf8a7d",
            "cve": "CVE-2014-3589",
            "id": "pyup.io-25932",
            "more_info_path": "/vulnerabilities/CVE-2014-3589/25932",
            "specs": [
                "<2.3.2",
                ">=2.5.0,<2.5.2"
            ],
            "v": "<2.3.2,>=2.5.0,<2.5.2"
        },
        {
            "advisory": "Pillow 2.5.0 includes a fix that prevents shell injection.\nhttps://github.com/python-pillow/Pillow/pull/731",
            "cve": "CVE-2014-3007",
            "id": "pyup.io-38907",
            "more_info_path": "/vulnerabilities/CVE-2014-3007/38907",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "pillow before 2.5.3 is vulnerable to a DoS in the Jpeg2KImagePlugin.",
            "cve": "CVE-2014-3598",
            "id": "pyup.io-25934",
            "more_info_path": "/vulnerabilities/CVE-2014-3598/25934",
            "specs": [
                "<2.5.3"
            ],
            "v": "<2.5.3"
        },
        {
            "advisory": "Pillow before 2.6.2 is vulnerable to a PNG decompression DoS (CVE-2014-9601).",
            "cve": "CVE-2014-9601",
            "id": "pyup.io-25936",
            "more_info_path": "/vulnerabilities/CVE-2014-9601/25936",
            "specs": [
                "<2.6.2"
            ],
            "v": "<2.6.2"
        },
        {
            "advisory": "Buffer overflow in the ImagingLibTiffDecode function in libImaging/TiffDecode.c in Pillow before 3.1.1 allows remote attackers to overwrite memory via a crafted TIFF file.",
            "cve": "CVE-2016-0740",
            "id": "pyup.io-33134",
            "more_info_path": "/vulnerabilities/CVE-2016-0740/33134",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        },
        {
            "advisory": "Buffer overflow in the ImagingFliDecode function in libImaging/FliDecode.c in Pillow before 3.1.1 allows remote attackers to cause a denial of service (crash) via a crafted FLI file.",
            "cve": "CVE-2016-0775",
            "id": "pyup.io-33135",
            "more_info_path": "/vulnerabilities/CVE-2016-0775/33135",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        },
        {
            "advisory": "Buffer overflow in the ImagingPcdDecode function in PcdDecode.c in Pillow before 3.1.1 and Python Imaging Library (PIL) 1.1.7 and earlier allows remote attackers to cause a denial of service (crash) via a crafted PhotoCD file.",
            "cve": "CVE-2016-2533",
            "id": "pyup.io-33136",
            "more_info_path": "/vulnerabilities/CVE-2016-2533/33136",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        },
        {
            "advisory": "Integer overflow in the ImagingResampleHorizontal function in libImaging/Resample.c in Pillow before 3.1.1 allows remote attackers to have unspecified impact via negative values of the new size, which triggers a heap-based buffer overflow.",
            "cve": "CVE-2016-4009",
            "id": "pyup.io-33137",
            "more_info_path": "/vulnerabilities/CVE-2016-4009/33137",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        },
        {
            "advisory": "pillow before 3.1.2 is vulnerable to an integer overflow in Jpeg2KEncode.c causing a buffer overflow. CVE-2016-3076.",
            "cve": "CVE-2016-3076",
            "id": "pyup.io-25943",
            "more_info_path": "/vulnerabilities/CVE-2016-3076/25943",
            "specs": [
                "<3.1.2"
            ],
            "v": "<3.1.2"
        },
        {
            "advisory": "Pillow before 3.3.2 allows context-dependent attackers to execute arbitrary code by using the \"crafted image file\" approach, related to an \"Insecure Sign Extension\" issue affecting the ImagingNew in Storage.c component.",
            "cve": "CVE-2016-9190",
            "id": "pyup.io-33138",
            "more_info_path": "/vulnerabilities/CVE-2016-9190/33138",
            "specs": [
                "<3.3.2"
            ],
            "v": "<3.3.2"
        },
        {
            "advisory": "Pillow before 3.3.2 allows context-dependent attackers to obtain sensitive information by using the \"crafted image file\" approach, related to an \"Integer Overflow\" issue affecting the Image.core.map_buffer in map.c component.",
            "cve": "CVE-2016-9189",
            "id": "pyup.io-33139",
            "more_info_path": "/vulnerabilities/CVE-2016-9189/33139",
            "specs": [
                "<3.3.2"
            ],
            "v": "<3.3.2"
        },
        {
            "advisory": "Pillow 6.2.0 includes a fix for CVE-2019-16865: An issue was discovered in Pillow before 6.2.0. When reading specially crafted invalid image files, the library can either allocate very large amounts of memory or take an extremely long period of time to process the image.",
            "cve": "CVE-2019-16865",
            "id": "pyup.io-44744",
            "more_info_path": "/vulnerabilities/CVE-2019-16865/44744",
            "specs": [
                "<6.2.0"
            ],
            "v": "<6.2.0"
        },
        {
            "advisory": "libImaging/SgiRleDecode.c in Pillow before 6.2.2 has an SGI buffer overflow.",
            "cve": "CVE-2020-5311",
            "id": "pyup.io-37780",
            "more_info_path": "/vulnerabilities/CVE-2020-5311/37780",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "libImaging/TiffDecode.c in Pillow before 6.2.2 has a TIFF decoding integer overflow, related to realloc.",
            "cve": "CVE-2020-5310",
            "id": "pyup.io-37779",
            "more_info_path": "/vulnerabilities/CVE-2020-5310/37779",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "There is a DoS vulnerability in Pillow before 6.2.2 caused by FpxImagePlugin.py calling the range function on an unvalidated 32-bit integer if the number of bands is large. On Windows running 32-bit Python, this results in an OverflowError or MemoryError due to the 2 GB limit. However, on Linux running 64-bit Python this results in the process being terminated by the OOM killer.",
            "cve": "CVE-2019-19911",
            "id": "pyup.io-37772",
            "more_info_path": "/vulnerabilities/CVE-2019-19911/37772",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "libImaging/PcxDecode.c in Pillow before 6.2.2 has a PCX P mode buffer overflow.",
            "cve": "CVE-2020-5312",
            "id": "pyup.io-37781",
            "more_info_path": "/vulnerabilities/CVE-2020-5312/37781",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "libImaging/FliDecode.c in Pillow before 6.2.2 has an FLI buffer overflow.",
            "cve": "CVE-2020-5313",
            "id": "pyup.io-37782",
            "more_info_path": "/vulnerabilities/CVE-2020-5313/37782",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "In libImaging/Jpeg2KDecode.c in Pillow before 7.1.0, there are multiple out-of-bounds reads via a crafted JP2 file.",
            "cve": "CVE-2020-10994",
            "id": "pyup.io-38451",
            "more_info_path": "/vulnerabilities/CVE-2020-10994/38451",
            "specs": [
                "<7.1.0"
            ],
            "v": "<7.1.0"
        },
        {
            "advisory": "In Pillow before 7.1.0, there are two Buffer Overflows in libImaging/TiffDecode.c.",
            "cve": "CVE-2020-10379",
            "id": "pyup.io-38450",
            "more_info_path": "/vulnerabilities/CVE-2020-10379/38450",
            "specs": [
                "<7.1.0"
            ],
            "v": "<7.1.0"
        },
        {
            "advisory": "Pillow before 7.1.0 has multiple out-of-bounds reads in libImaging/FliDecode.c.",
            "cve": "CVE-2020-10177",
            "id": "pyup.io-38448",
            "more_info_path": "/vulnerabilities/CVE-2020-10177/38448",
            "specs": [
                "<7.1.0"
            ],
            "v": "<7.1.0"
        },
        {
            "advisory": "In libImaging/PcxDecode.c in Pillow before 7.1.0, an out-of-bounds read can occur when reading PCX files where state->shuffle is instructed to read beyond state->buffer.",
            "cve": "CVE-2020-10378",
            "id": "pyup.io-38449",
            "more_info_path": "/vulnerabilities/CVE-2020-10378/38449",
            "specs": [
                "<7.1.0"
            ],
            "v": "<7.1.0"
        },
        {
            "advisory": "Pillow 8.0.1 updates 'FreeType' used in binary wheels to v2.10.4 to include a security fix.",
            "cve": "CVE-2020-15999",
            "id": "pyup.io-40264",
            "more_info_path": "/vulnerabilities/CVE-2020-15999/40264",
            "specs": [
                "<8.0.1"
            ],
            "v": "<8.0.1"
        },
        {
            "advisory": "In Pillow before 8.1.0, PcxDecode has a buffer over-read when decoding a crafted PCX file because the user-supplied stride value is trusted for buffer calculations.",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-40270",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/40270",
            "specs": [
                "<8.1.0"
            ],
            "v": "<8.1.0"
        },
        {
            "advisory": "Pillow 8.1.0 fixes TIFF OOB Write error. CVE-2020-35654 #5175.",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-40265",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/40265",
            "specs": [
                "<8.1.0"
            ],
            "v": "<8.1.0"
        },
        {
            "advisory": "Pillow 8.1.0 includes a fix for SGI Decode buffer overrun. CVE-2020-35655 #5173.",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-40271",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/40271",
            "specs": [
                "<8.1.0"
            ],
            "v": "<8.1.0"
        },
        {
            "advisory": "Pillow 8.1.1 includes a fix for CVE-2021-25290: In TiffDecode.c, there is a negative-offset memcpy with an invalid size.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-40275",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/40275",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow 8.1.1 includes a fix for CVE-2021-25291: In TiffDecode.c, there is an out-of-bounds read in TiffreadRGBATile via invalid tile boundaries.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-40272",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/40272",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow 8.1.1 includes a fix for CVE-2021-27921: Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for a BLP container, and thus an attempted memory allocation can be very large.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-40263",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/40263",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow 8.1.1 includes a fix for CVE-2021-25293: There is an out-of-bounds read in SGIRleDecode.c.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-40273",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/40273",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow 8.1.1 includes a fix for CVE-2021-25292: The PDF parser allows a regular expression DoS (ReDoS) attack via a crafted PDF file because of a catastrophic backtracking regex.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-40266",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/40266",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow 8.1.1 includes a fix for CVE-2021-27922: Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICNS container, and thus an attempted memory allocation can be very large.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-40267",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/40267",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow 8.1.1 includes a fix for CVE-2021-25289: TiffDecode has a heap-based buffer overflow when decoding crafted YCbCr files because of certain interpretation conflicts with LibTIFF in RGBA mode. NOTE: this issue exists because of an incomplete fix for CVE-2020-35654.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-40274",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/40274",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow 8.2.0 includes a fix for CVE-2021-25288: There is an out-of-bounds read in J2kDecode, in j2ku_gray_i.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-25287-cve-2021-25288-fix-oob-read-in-jpeg2kdecode",
            "cve": "CVE-2021-25288",
            "id": "pyup.io-40593",
            "more_info_path": "/vulnerabilities/CVE-2021-25288/40593",
            "specs": [
                "<8.2.0"
            ],
            "v": "<8.2.0"
        },
        {
            "advisory": "Pillow version 8.2.0 includes a fix for CVE-2021-28678: For BLP data, BlpImagePlugin did not properly check that reads (after jumping to file offsets) returned data. This could lead to a DoS where the decoder could be run a large number of times on empty data.\r\nhttps://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQHA5HAIBOYI3R6HDWCLAGFTIQP767FL/\r\nhttps://github.com/python-pillow/Pillow/pull/5377\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-28678-fix-blp-dos",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-40596",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/40596",
            "specs": [
                "<8.2.0"
            ],
            "v": "<8.2.0"
        },
        {
            "advisory": "Pillow version 8.2.0 includes a fix for CVE-2021-28676: For FLI data, FliDecode did not properly check that the block advance was non-zero, potentially leading to an infinite loop on load.\r\nhttps://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQHA5HAIBOYI3R6HDWCLAGFTIQP767FL/\r\nhttps://github.com/python-pillow/Pillow/pull/5377\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-28676-fix-fli-dos",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-40594",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/40594",
            "specs": [
                "<8.2.0"
            ],
            "v": "<8.2.0"
        },
        {
            "advisory": "Pillow 8.2.0 includes a fix for CVE-2021-25287: There is an out-of-bounds read in J2kDecode, in j2ku_graya_la.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-25287-cve-2021-25288-fix-oob-read-in-jpeg2kdecode",
            "cve": "CVE-2021-25287",
            "id": "pyup.io-40592",
            "more_info_path": "/vulnerabilities/CVE-2021-25287/40592",
            "specs": [
                "<8.2.0"
            ],
            "v": "<8.2.0"
        },
        {
            "advisory": "Pillow version 8.2.0 includes a fix for CVE-2021-28677: For EPS data, the readline implementation used in EPSImageFile has to deal with any combination of \\r and \\n as line endings. It used an accidentally quadratic method of accumulating lines while looking for a line ending. A malicious EPS file could use this to perform a DoS of Pillow in the open phase, before an image was accepted for opening.\r\nhttps://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQHA5HAIBOYI3R6HDWCLAGFTIQP767FL/\r\nhttps://github.com/python-pillow/Pillow/pull/5377\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-28677-fix-eps-dos-on-open",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-40595",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/40595",
            "specs": [
                "<8.2.0"
            ],
            "v": "<8.2.0"
        },
        {
            "advisory": "Pillow 8.3.0 includes a fix for CVE-2021-34552: Pillow through 8.2.0 and PIL (also known as Python Imaging Library) through 1.1.7 allow an attacker to pass controlled parameters directly into a convert function to trigger a buffer overflow in Convert.c\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.3.0.html#buffer-overflow\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/index.html",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-40965",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/40965",
            "specs": [
                "<8.3.0"
            ],
            "v": "<8.3.0"
        },
        {
            "advisory": "Pillow 9.0.0 ensures JpegImagePlugin stops at the end of a truncated file to avoid Denial of Service attacks.\r\nhttps://github.com/python-pillow/Pillow/pull/5921\r\nhttps://github.com/advisories/GHSA-4fx9-vc88-q2xc",
            "cve": "PVE-2022-44524",
            "id": "pyup.io-44524",
            "more_info_path": "/vulnerabilities/PVE-2022-44524/44524",
            "specs": [
                "<9.0.0"
            ],
            "v": "<9.0.0"
        },
        {
            "advisory": "Pillow 9.0.0 excludes carriage return in PDF regex to help prevent ReDoS.\r\nhttps://github.com/python-pillow/Pillow/pull/5912\r\nhttps://github.com/python-pillow/Pillow/commit/43b800d933c996226e4d7df00c33fcbe46d97363",
            "cve": "PVE-2021-44525",
            "id": "pyup.io-44525",
            "more_info_path": "/vulnerabilities/PVE-2021-44525/44525",
            "specs": [
                "<9.0.0"
            ],
            "v": "<9.0.0"
        },
        {
            "advisory": "Pillow 9.0.0 includes a fix for CVE-2022-22815: path_getbbox in path.c in Pillow before 9.0.0 improperly initializes ImagePath.Path.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/9.0.0.html#fixed-imagepath-path-array-handling",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-44485",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/44485",
            "specs": [
                "<9.0.0"
            ],
            "v": "<9.0.0"
        },
        {
            "advisory": "Pillow 9.0.0 includes a fix for CVE-2022-22816: path_getbbox in path.c in Pillow before 9.0.0 has a buffer over-read during initialization of ImagePath.Path.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/9.0.0.html#fixed-imagepath-path-array-handling",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-44486",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/44486",
            "specs": [
                "<9.0.0"
            ],
            "v": "<9.0.0"
        },
        {
            "advisory": "Pillow before 9.0.1 allows attackers to delete files because spaces in temporary pathnames are mishandled.",
            "cve": "CVE-2022-24303",
            "id": "pyup.io-45356",
            "more_info_path": "/vulnerabilities/CVE-2022-24303/45356",
            "specs": [
                "<9.0.1"
            ],
            "v": "<9.0.1"
        },
        {
            "advisory": "Pillow 9.0.1 includes a fix for CVE-2022-22817: PIL.ImageMath.eval in Pillow before 9.0.0 allows evaluation of arbitrary expressions, such as ones that use the Python exec method. A first patch was issued for version 9.0.0 but it did not prevent builtins available to lambda expressions.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/9.0.1.html#security",
            "cve": "CVE-2022-22817",
            "id": "pyup.io-44487",
            "more_info_path": "/vulnerabilities/CVE-2022-22817/44487",
            "specs": [
                "<9.0.1"
            ],
            "v": "<9.0.1"
        },
        {
            "advisory": "Pillow before 9.2.0 performs Improper Handling of Highly Compressed GIF Data (Data Amplification).",
            "cve": "CVE-2022-45198",
            "id": "pyup.io-51885",
            "more_info_path": "/vulnerabilities/CVE-2022-45198/51885",
            "specs": [
                "<9.2.0"
            ],
            "v": "<9.2.0"
        },
        {
            "advisory": "In libImaging/SgiRleDecode.c in Pillow through 7.0.0, a number of out-of-bounds reads exist in the parsing of SGI image files, a different issue than CVE-2020-5311.",
            "cve": "CVE-2020-11538",
            "id": "pyup.io-38452",
            "more_info_path": "/vulnerabilities/CVE-2020-11538/38452",
            "specs": [
                "<=7.0.0"
            ],
            "v": "<=7.0.0"
        },
        {
            "advisory": "An issue was discovered in Pillow before 8.2.0. PSDImagePlugin.PsdImageFile lacked a sanity check on the number of input layers relative to the size of the data block. This could lead to a DoS on Image.open prior to Image.load.",
            "cve": "CVE-2021-28675",
            "id": "pyup.io-54688",
            "more_info_path": "/vulnerabilities/CVE-2021-28675/54688",
            "specs": [
                ">=0,<8.2.0"
            ],
            "v": ">=0,<8.2.0"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to a Buffer Overflow when saving sufficiently large compressed DDS images (>64KB with default settings). The DDS encoding functionality fails to perform bounds checking when writing to the destination buffer, leading to a heap buffer overflow condition. This vulnerability was introduced in Pillow 11.2.0 when BCn compression support for DDS format was added.",
            "cve": "CVE-2025-48379",
            "id": "pyup.io-77942",
            "more_info_path": "/vulnerabilities/CVE-2025-48379/77942",
            "specs": [
                ">=11.2.1,<11.3.0"
            ],
            "v": ">=11.2.1,<11.3.0"
        },
        {
            "advisory": "Pillow 10.0.1 updates its C dependency 'libwebp' to 1.3.2 to include a fix for a high-risk vulnerability.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/10.0.1.html",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61489",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61489",
            "specs": [
                ">=2.5.0,<10.0.1"
            ],
            "v": ">=2.5.0,<10.0.1"
        },
        {
            "advisory": "Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICO container, and thus an attempted memory allocation can be very large.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-40268",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/40268",
            "specs": [
                ">=4.3.0,<8.1.1"
            ],
            "v": ">=4.3.0,<8.1.1"
        },
        {
            "advisory": "Pillow from 5.2.0 and before 8.3.2 is vulnerable to Regular Expression Denial of Service (ReDoS) via the getrgb function.\r\nhttps://github.com/python-pillow/Pillow/commit/9e08eb8f78fdfd2f476e1b20b7cf38683754866b\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.3.2.html",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-41271",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/41271",
            "specs": [
                ">=5.2.0,<8.3.2"
            ],
            "v": ">=5.2.0,<8.3.2"
        },
        {
            "advisory": "libImaging/TgaRleDecode.c in Pillow 9.1.0 has a heap buffer overflow in the processing of invalid TGA image files.",
            "cve": "CVE-2022-30595",
            "id": "pyup.io-49150",
            "more_info_path": "/vulnerabilities/CVE-2022-30595/49150",
            "specs": [
                ">=9.1.0,<9.1.1"
            ],
            "v": ">=9.1.0,<9.1.1"
        },
        {
            "advisory": "Pillow 9.3.0 includes a security fix: Pillow will now decode the data in its natural CMYK mode, then convert it to RGB and rearrange the channels afterwards. Trying to load the data in an incorrect mode could result in a segmentation fault.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/9.3.0.html#decode-jpeg-compressed-blp1-data-in-original-mode",
            "cve": "PVE-2023-55182",
            "id": "pyup.io-55182",
            "more_info_path": "/vulnerabilities/PVE-2023-55182/55182",
            "specs": [
                ">=9.1.0,<9.3.0"
            ],
            "v": ">=9.1.0,<9.3.0"
        },
        {
            "advisory": "Pillow before 9.3.0 allows denial of service via SAMPLESPERPIXEL.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/9.3.0.html#limit-samplesperpixel-to-avoid-runtime-dos",
            "cve": "CVE-2022-45199",
            "id": "pyup.io-51886",
            "more_info_path": "/vulnerabilities/CVE-2022-45199/51886",
            "specs": [
                ">=9.2.0,<9.3.0"
            ],
            "v": ">=9.2.0,<9.3.0"
        }
    ],
    "pillow-heif": [
        {
            "advisory": "Pillow-heif 0.6.1 fixes HEIF decoder's CVEs.",
            "cve": "CVE-2022-1253",
            "id": "pyup.io-50709",
            "more_info_path": "/vulnerabilities/CVE-2022-1253/50709",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        },
        {
            "advisory": "Pillow-heif 0.6.1 fixes HEIF decoder's CVEs.",
            "cve": "CVE-2021-35452",
            "id": "pyup.io-50718",
            "more_info_path": "/vulnerabilities/CVE-2021-35452/50718",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        },
        {
            "advisory": "Pillow-heif 0.6.1 fixes HEIF decoder's CVEs.",
            "cve": "CVE-2021-36408",
            "id": "pyup.io-50715",
            "more_info_path": "/vulnerabilities/CVE-2021-36408/50715",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        },
        {
            "advisory": "Pillow-heif 0.6.1 fixes HEIF decoder's CVEs.",
            "cve": "CVE-2021-36411",
            "id": "pyup.io-50717",
            "more_info_path": "/vulnerabilities/CVE-2021-36411/50717",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        },
        {
            "advisory": "Pillow-heif 0.6.1 fixes HEIF decoder's CVEs.",
            "cve": "CVE-2021-36410",
            "id": "pyup.io-50716",
            "more_info_path": "/vulnerabilities/CVE-2021-36410/50716",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        }
    ],
    "pillow-simd": [
        {
            "advisory": "Pillow-simd is affected by an arbitrary code execution vulnerability. If an attacker controls the keys passed to the environment argument of PIL.ImageMath.eval(), they may be able to execute arbitrary code.\r\n#Note: This CVE originates in the original package, Pillow, from which Pillow-simd is forked. However, this CVE is fixed in Pillow, but there is still no fix in Pillow-simd.",
            "cve": "CVE-2023-50447",
            "id": "pyup.io-72955",
            "more_info_path": "/vulnerabilities/CVE-2023-50447/72955",
            "specs": [
                "<10.2.0"
            ],
            "v": "<10.2.0"
        },
        {
            "advisory": "Pillow-simd is potentially vulnerable to DoS attacks through PIL.ImageFont.ImageFont.getmask().\r\n#Note: This CVE originates in the original package, Pillow, from which Pillow-simd is forked. However, this CVE is fixed in Pillow, but there is still no fix in Pillow-simd.",
            "cve": "PVE-2024-64437",
            "id": "pyup.io-73080",
            "more_info_path": "/vulnerabilities/PVE-2024-64437/73080",
            "specs": [
                "<10.2.0"
            ],
            "v": "<10.2.0"
        },
        {
            "advisory": "Pillow-simd 2.3.1 includes a fix for CVE-2014-1932: The (1) load_djpeg function in JpegImagePlugin.py, (2) Ghostscript function in EpsImagePlugin.py, (3) load function in IptcImagePlugin.py, and (4) _copy function in Image.py in Python Image Library (PIL) 1.1.7 and earlier and Pillow before 2.3.1 do not properly create temporary files, which allow local users to overwrite arbitrary files and obtain sensitive information via a symlink attack on the temporary file.",
            "cve": "CVE-2014-1932",
            "id": "pyup.io-34340",
            "more_info_path": "/vulnerabilities/CVE-2014-1932/34340",
            "specs": [
                "<2.3.1"
            ],
            "v": "<2.3.1"
        },
        {
            "advisory": "Pillow-simd 2.3.1 includes a fix for CVE-2014-1933: The (1) JpegImagePlugin.py and (2) EpsImagePlugin.py scripts in Python Image Library (PIL) 1.1.7 and earlier and Pillow before 2.3.1 uses the names of temporary files on the command line, which makes it easier for local users to conduct symlink attacks by listing the processes.",
            "cve": "CVE-2014-1933",
            "id": "pyup.io-47660",
            "more_info_path": "/vulnerabilities/CVE-2014-1933/47660",
            "specs": [
                "<2.3.1"
            ],
            "v": "<2.3.1"
        },
        {
            "advisory": "pillow-simd affected versions are vulnerable to CVE-2014-3589, a DOS in the IcnsImagePlugin.",
            "cve": "CVE-2014-3589",
            "id": "pyup.io-39576",
            "more_info_path": "/vulnerabilities/CVE-2014-3589/39576",
            "specs": [
                "<2.3.2",
                ">=2.5.0,<2.5.2"
            ],
            "v": "<2.3.2,>=2.5.0,<2.5.2"
        },
        {
            "advisory": "Pillow-simd 2.5.0 includes changes to prevent shell injection. This is related to CVE-2014-1932.\r\nhttps://github.com/uploadcare/pillow-simd/commit/cd7b45994b1b1a016a29401d7ab3faf9b7c7d054",
            "cve": "PVE-2021-43447",
            "id": "pyup.io-43447",
            "more_info_path": "/vulnerabilities/PVE-2021-43447/43447",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Pillow-simd includes a fix that prevents shell injection.",
            "cve": "CVE-2014-3007",
            "id": "pyup.io-72856",
            "more_info_path": "/vulnerabilities/CVE-2014-3007/72856",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Pillow-simd before 2.5.3 is vulnerable to CVE-2014-3598.",
            "cve": "CVE-2014-3598",
            "id": "pyup.io-25949",
            "more_info_path": "/vulnerabilities/CVE-2014-3598/25949",
            "specs": [
                "<2.5.3"
            ],
            "v": "<2.5.3"
        },
        {
            "advisory": "pillow-simd before 2.6.2 is vulnerable to a PNG decompression DoS (CVE-2014-9601).",
            "cve": "CVE-2014-9601",
            "id": "pyup.io-25951",
            "more_info_path": "/vulnerabilities/CVE-2014-9601/25951",
            "specs": [
                "<2.6.2"
            ],
            "v": "<2.6.2"
        },
        {
            "advisory": "pillow-simd before 3.1.1 is vulnerable to multiple buffer overflows in Resample.c, PcdDecode.c, FliDecode.c and TiffDecode.c.",
            "cve": "PVE-2021-25953",
            "id": "pyup.io-25953",
            "more_info_path": "/vulnerabilities/PVE-2021-25953/25953",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        },
        {
            "advisory": "Buffer overflow in the ImagingFliDecode function in libImaging/FliDecode.c in Pillow before 3.1.1 allows remote attackers to cause a denial of service (crash) via a crafted FLI file.",
            "cve": "CVE-2016-0775",
            "id": "pyup.io-42330",
            "more_info_path": "/vulnerabilities/CVE-2016-0775/42330",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        },
        {
            "advisory": "Buffer overflow in the ImagingLibTiffDecode function in libImaging/TiffDecode.c in Pillow before 3.1.1 allows remote attackers to overwrite memory via a crafted TIFF file.",
            "cve": "CVE-2016-0740",
            "id": "pyup.io-42331",
            "more_info_path": "/vulnerabilities/CVE-2016-0740/42331",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        },
        {
            "advisory": "Integer overflow in the ImagingResampleHorizontal function in libImaging/Resample.c in Pillow-simd affected versions allows remote attackers to have unspecified impact via negative values of the new size, which triggers a heap-based buffer overflow.",
            "cve": "CVE-2016-4009",
            "id": "pyup.io-72855",
            "more_info_path": "/vulnerabilities/CVE-2016-4009/72855",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        },
        {
            "advisory": "Buffer overflow in the ImagingPcdDecode function in PcdDecode.c in Pillow before 3.1.1 and Python Imaging Library (PIL) 1.1.7 and earlier allows remote attackers to cause a denial of service (crash) via a crafted PhotoCD file.",
            "cve": "CVE-2016-2533",
            "id": "pyup.io-42329",
            "more_info_path": "/vulnerabilities/CVE-2016-2533/42329",
            "specs": [
                "<3.1.1"
            ],
            "v": "<3.1.1"
        },
        {
            "advisory": "pillow-simd before 3.1.2 is vulnerable to an integer overflow in Jpeg2KEncode.c causing a buffer overflow. CVE-2016-3076.",
            "cve": "CVE-2016-3076",
            "id": "pyup.io-25954",
            "more_info_path": "/vulnerabilities/CVE-2016-3076/25954",
            "specs": [
                "<3.1.2"
            ],
            "v": "<3.1.2"
        },
        {
            "advisory": "Pillow-simd affected versions allows context-dependent attackers to execute arbitrary code by using the \"crafted image file\" approach, related to an \"Insecure Sign Extension\" issue affecting the ImagingNew in Storage.c component.",
            "cve": "CVE-2016-9190",
            "id": "pyup.io-72853",
            "more_info_path": "/vulnerabilities/CVE-2016-9190/72853",
            "specs": [
                "<3.3.2"
            ],
            "v": "<3.3.2"
        },
        {
            "advisory": "Pillow-simd affected versions allow context-dependent attackers to obtain sensitive information by using the \"crafted image file\" approach, related to an \"Integer Overflow\" issue affecting the Image.core.map_buffer in map.c component.",
            "cve": "CVE-2016-9189",
            "id": "pyup.io-72854",
            "more_info_path": "/vulnerabilities/CVE-2016-9189/72854",
            "specs": [
                "<3.3.2"
            ],
            "v": "<3.3.2"
        },
        {
            "advisory": "Pillow-simd includes a fix for CVE-2019-16865: An issue was discovered in Pillow before 6.2.0. When reading specially crafted invalid image files, the library can either allocate vast amounts of memory or take an extremely long time to process the image.",
            "cve": "CVE-2019-16865",
            "id": "pyup.io-72850",
            "more_info_path": "/vulnerabilities/CVE-2019-16865/72850",
            "specs": [
                "<6.2.0"
            ],
            "v": "<6.2.0"
        },
        {
            "advisory": "There is a DoS vulnerability in Pillow-simd affected versions caused by FpxImagePlugin.py calling the range function on an unvalidated 32-bit integer if the number of bands is large. On Windows running 32-bit Python, this results in an OverflowError or MemoryError due to the 2 GB limit. However, on Linux running 64-bit Python this results in the process being terminated by the OOM killer.",
            "cve": "CVE-2019-19911",
            "id": "pyup.io-72847",
            "more_info_path": "/vulnerabilities/CVE-2019-19911/72847",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "libImaging/FliDecode.c in Pillow-simd affected versions have an FLI buffer overflow.",
            "cve": "CVE-2020-5313",
            "id": "pyup.io-72846",
            "more_info_path": "/vulnerabilities/CVE-2020-5313/72846",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "libImaging/PcxDecode.c in Pillow-simd affected versions have a PCX P mode buffer overflow.",
            "cve": "CVE-2020-5312",
            "id": "pyup.io-72849",
            "more_info_path": "/vulnerabilities/CVE-2020-5312/72849",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "libImaging/SgiRleDecode.c in Pillow-simd affected versions have an SGI buffer overflow.",
            "cve": "CVE-2020-5311",
            "id": "pyup.io-72848",
            "more_info_path": "/vulnerabilities/CVE-2020-5311/72848",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "libImaging/TiffDecode.c in Pillow-simd affected versions have a TIFF decoding integer overflow, related to realloc.",
            "cve": "CVE-2020-5310",
            "id": "pyup.io-72845",
            "more_info_path": "/vulnerabilities/CVE-2020-5310/72845",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        },
        {
            "advisory": "In Pillow-simd affected versions, there are two Buffer Overflows in libImaging/TiffDecode.c.",
            "cve": "CVE-2020-10379",
            "id": "pyup.io-72841",
            "more_info_path": "/vulnerabilities/CVE-2020-10379/72841",
            "specs": [
                "<7.1.0"
            ],
            "v": "<7.1.0"
        },
        {
            "advisory": "In libImaging/PcxDecode.c in Pillow-simd affected versions, an out-of-bounds read can occur when reading PCX files where state->shuffle is instructed to read beyond state->buffer.",
            "cve": "CVE-2020-10378",
            "id": "pyup.io-72843",
            "more_info_path": "/vulnerabilities/CVE-2020-10378/72843",
            "specs": [
                "<7.1.0"
            ],
            "v": "<7.1.0"
        },
        {
            "advisory": "In libImaging/Jpeg2KDecode.c in Pillow-simd affected versions, there are multiple out-of-bounds reads via a crafted JP2 file.",
            "cve": "CVE-2020-10994",
            "id": "pyup.io-72840",
            "more_info_path": "/vulnerabilities/CVE-2020-10994/72840",
            "specs": [
                "<7.1.0"
            ],
            "v": "<7.1.0"
        },
        {
            "advisory": "Pillow-simd affected versions have multiple out-of-bounds reads in libImaging/FliDecode.c.",
            "cve": "CVE-2020-10177",
            "id": "pyup.io-72842",
            "more_info_path": "/vulnerabilities/CVE-2020-10177/72842",
            "specs": [
                "<7.1.0"
            ],
            "v": "<7.1.0"
        },
        {
            "advisory": "Pillow-simd includes an updated 'FreeType' used in binary wheels to v2.10.4 to include a security fix.",
            "cve": "CVE-2020-15999",
            "id": "pyup.io-72839",
            "more_info_path": "/vulnerabilities/CVE-2020-15999/72839",
            "specs": [
                "<8.0.1"
            ],
            "v": "<8.0.1"
        },
        {
            "advisory": "In Pillow-simd affected versions, PcxDecode has a buffer over-read when decoding a crafted PCX file because the user-supplied stride value is trusted for buffer calculations.",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-72837",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/72837",
            "specs": [
                "<8.1.0"
            ],
            "v": "<8.1.0"
        },
        {
            "advisory": "Pillow-simd includes a fix for SGI Decode buffer overrun.",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-72836",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/72836",
            "specs": [
                "<8.1.0"
            ],
            "v": "<8.1.0"
        },
        {
            "advisory": "Pillow-simd includes a fix for TIFF OOB Write error.",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-72838",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/72838",
            "specs": [
                "<8.1.0"
            ],
            "v": "<8.1.0"
        },
        {
            "advisory": "Affected versions of Pillow-simd, a highly optimized version of the Pillow library for x86 architecture (primarily Intel and AMD CPUs), are vulnerable to CVE-2021-25293. This vulnerability in `SGIRleDecode.c` allows an out-of-bounds read, potentially leading to memory corruption or application crashes when processing specific input.",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-72605",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/72605",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Affected versions of Pillow-simd, a highly optimized version of the Pillow library for x86 architecture (mainly Intel and AMD CPUs), are vulnerable to CVE-2021-25292. Due to catastrophic backtracking in a regular expression, this issue allows a Regular Expression Denial of Service (ReDoS) attack through the PDF parser when processing a crafted PDF file.",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-72571",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/72571",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Affected versions of Pillow-simd, a highly optimized version of the Pillow library for x86 architecture (primarily Intel and AMD CPUs), are vulnerable to CVE-2021-25291. This vulnerability, found in `TiffDecode.c`, allows an out-of-bounds read in `TiffreadRGBATile` when processing invalid tile boundaries, potentially leading to memory corruption or crashes.",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-72603",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/72603",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Affected versions of Pillow-simd, a highly optimized version of the Pillow library for x86 architecture (primarily Intel and AMD CPUs), are vulnerable to CVE-2021-25289. This issue, found in `TiffDecode`, involves a heap-based buffer overflow when decoding crafted YCbCr files due to certain interpretation conflicts with LibTIFF in RGBA mode. Notably, this vulnerability exists because of an incomplete fix for CVE-2020-35654.",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-72606",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/72606",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow-simd includes a fix for CVE-2021-27922: Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICNS container, and thus an attempted memory allocation can be huge.",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-72835",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/72835",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow-simd includes a fix for CVE-2021-27921: Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for a BLP container, and thus an attempted memory allocation can be very large.",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-72834",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/72834",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Affected versions of Pillow-simd, a highly optimized version of the Pillow library for x86 architecture (primarily Intel and AMD CPUs), are vulnerable to CVE-2021-25290. This issue, identified in `TiffDecode.c`, involves a negative-offset `memcpy` operation with an invalid size, resulting in memory corruption and potential security risks.",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-72604",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/72604",
            "specs": [
                "<8.1.1"
            ],
            "v": "<8.1.1"
        },
        {
            "advisory": "Pillow-simd includes a fix for CVE-2021-25288: There is an out-of-bounds read in J2kDecode, in j2ku_gray_i.",
            "cve": "CVE-2021-25288",
            "id": "pyup.io-72831",
            "more_info_path": "/vulnerabilities/CVE-2021-25288/72831",
            "specs": [
                "<8.2.0"
            ],
            "v": "<8.2.0"
        },
        {
            "advisory": "Pillow-simd includes a fix for CVE-2021-28677: For EPS data, the readline implementation used in EPSImageFile has to deal with any combination of \\r and \\n as line endings. It used an accidentally quadratic method of accumulating lines while looking for a line ending. A malicious EPS file could use this to perform a DoS of Pillow in the open phase, before an image was accepted for opening.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-72833",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/72833",
            "specs": [
                "<8.2.0"
            ],
            "v": "<8.2.0"
        },
        {
            "advisory": "Pillow-simd includes a fix for CVE-2021-28678: For BLP data, BlpImagePlugin did not properly check that reads (after jumping to file offsets) returned data. This could lead to a DoS where the decoder could be run many times on empty data.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-72826",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/72826",
            "specs": [
                "<8.2.0"
            ],
            "v": "<8.2.0"
        },
        {
            "advisory": "Pillow-simd includes a fix for CVE-2021-25287: There is an out-of-bounds read in J2kDecode, in j2ku_graya_la.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-25287-cve-2021-25288-fix-oob-read-in-jpeg2kdecode",
            "cve": "CVE-2021-25287",
            "id": "pyup.io-72832",
            "more_info_path": "/vulnerabilities/CVE-2021-25287/72832",
            "specs": [
                "<8.2.0"
            ],
            "v": "<8.2.0"
        },
        {
            "advisory": "Affected versions of Pillow-simd are vulnerable to a buffer overflow in `Convert.c` (CVE-2021-34552). An attacker could exploit this vulnerability by passing controlled parameters directly into the `convert` function, leading to potential memory corruption and arbitrary code execution.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-72570",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/72570",
            "specs": [
                "<8.3.0"
            ],
            "v": "<8.3.0"
        },
        {
            "advisory": "Pillow-simd fixed versions exclude carriage return in PDF regex to help prevent ReDoS.",
            "cve": "PVE-2021-44525",
            "id": "pyup.io-72862",
            "more_info_path": "/vulnerabilities/PVE-2021-44525/72862",
            "specs": [
                "<9.0.0"
            ],
            "v": "<9.0.0"
        },
        {
            "advisory": "Affected versions of Pillow-simd are vulnerable to a buffer over-read in the `path_getbbox` function within `path.c`. This issue occurs during the initialization of `ImagePath.Path`, potentially leading to unexpected behavior or crashes when handling specific image path data.",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-72569",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/72569",
            "specs": [
                "<9.0.0"
            ],
            "v": "<9.0.0"
        },
        {
            "advisory": "Affected versions of Pillow-simd are vulnerable due to improper initialization of `ImagePath.Path` in the `path_getbbox` function within `path.c`. This flaw can lead to unpredictable behaviour or potential security risks when processing image paths.",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-72601",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/72601",
            "specs": [
                "<9.0.0"
            ],
            "v": "<9.0.0"
        },
        {
            "advisory": "Pillow-simd affected versions ensures JpegImagePlugin stops at the end of a truncated file to avoid Denial of Service attacks.",
            "cve": "PVE-2022-44524",
            "id": "pyup.io-72861",
            "more_info_path": "/vulnerabilities/PVE-2022-44524/72861",
            "specs": [
                "<9.0.0"
            ],
            "v": "<9.0.0"
        },
        {
            "advisory": "Affected versions of Pillow-simd are vulnerable due to improper handling in the `PIL.ImageMath.eval` function, which allows the evaluation of arbitrary expressions, including those that utilize the Python `exec` method. An attacker could exploit this by executing arbitrary code by using a lambda expression or other malicious input.",
            "cve": "CVE-2022-22817",
            "id": "pyup.io-72602",
            "more_info_path": "/vulnerabilities/CVE-2022-22817/72602",
            "specs": [
                "<9.0.1"
            ],
            "v": "<9.0.1"
        },
        {
            "advisory": "Pillow-simd affected versions allows attackers to delete files because spaces in temporary pathnames are mishandled.",
            "cve": "CVE-2022-24303",
            "id": "pyup.io-73079",
            "more_info_path": "/vulnerabilities/CVE-2022-24303/73079",
            "specs": [
                "<9.0.1"
            ],
            "v": "<9.0.1"
        },
        {
            "advisory": "Pillow affected versions performs Improper Handling of Highly Compressed GIF Data (Data Amplification).",
            "cve": "CVE-2022-45198",
            "id": "pyup.io-72825",
            "more_info_path": "/vulnerabilities/CVE-2022-45198/72825",
            "specs": [
                "<9.2.0"
            ],
            "v": "<9.2.0"
        },
        {
            "advisory": "In libImaging/SgiRleDecode.c in Pillow-simd affected versions, a number of out-of-bounds reads exist in the parsing of SGI image files, a different issue than CVE-2020-5311.",
            "cve": "CVE-2020-11538",
            "id": "pyup.io-72844",
            "more_info_path": "/vulnerabilities/CVE-2020-11538/72844",
            "specs": [
                "<=7.0.0"
            ],
            "v": "<=7.0.0"
        },
        {
            "advisory": "Pillow-simd affected versions are vulnerable to a denial of Service that uncontrollably allocates memory to process a given task, potentially causing a service to crash by having it run out of memory. This occurs for truetype in ImageFont when textlength in an ImageDraw instance operates on a long text argument.\r\n#Note: This CVE originates in the original package, Pillow, from which Pillow-simd is forked. However, this CVE is fixed in Pillow, but there is still no fix in Pillow-simd.",
            "cve": "CVE-2023-44271",
            "id": "pyup.io-72858",
            "more_info_path": "/vulnerabilities/CVE-2023-44271/72858",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        },
        {
            "advisory": "In _imagingcms.c in Pillow-simd affected versions, a buffer overflow exists because strcpy is used instead of strncpy.\r\n#Note: This CVE originates in the original package, Pillow, from which Pillow-simd is forked. However, this CVE is fixed in Pillow, but there is still no fix in Pillow-simd.",
            "cve": "CVE-2024-28219",
            "id": "pyup.io-72857",
            "more_info_path": "/vulnerabilities/CVE-2024-28219/72857",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        },
        {
            "advisory": "An issue was discovered in Pillow-simd affected versions. PSDImagePlugin.PsdImageFile lacked a sanity check on the number of input layers relative to the size of the data block. This could lead to a DoS on Image.open before Image.load.",
            "cve": "CVE-2021-28675",
            "id": "pyup.io-72859",
            "more_info_path": "/vulnerabilities/CVE-2021-28675/72859",
            "specs": [
                ">=0,<8.2.0"
            ],
            "v": ">=0,<8.2.0"
        },
        {
            "advisory": "Pillow-simd updates its C dependency 'libwebp' to 1.3.2 to include a fix for a high-risk vulnerability.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-72953",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/72953",
            "specs": [
                ">=2.5.0,<10.0.1"
            ],
            "v": ">=2.5.0,<10.0.1"
        },
        {
            "advisory": "Pillow-simd affected versions allow attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICO container, and thus an attempted memory allocation can be huge.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-72852",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/72852",
            "specs": [
                ">=4.3.0,<8.1.1"
            ],
            "v": ">=4.3.0,<8.1.1"
        },
        {
            "advisory": "Pillow-simd affected versions are vulnerable to Regular Expression Denial of Service (ReDoS) via the getrgb function.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-72851",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/72851",
            "specs": [
                ">=5.2.0,<8.3.2"
            ],
            "v": ">=5.2.0,<8.3.2"
        },
        {
            "advisory": "Pillow-simd includes a security fix: Pillow will now decode the data in its natural CMYK mode, then convert it to RGB and rearrange the channels afterwards. Trying to load the data in an incorrect mode could result in a segmentation fault.",
            "cve": "PVE-2023-55182",
            "id": "pyup.io-72860",
            "more_info_path": "/vulnerabilities/PVE-2023-55182/72860",
            "specs": [
                ">=9.1.0,<9.3.0"
            ],
            "v": ">=9.1.0,<9.3.0"
        },
        {
            "advisory": "Pillow-simd affected versions allows denial of service via SAMPLESPERPIXEL.\r\nhttps://pillow.readthedocs.io/en/stable/releasenotes/9.3.0.html#limit-samplesperpixel-to-avoid-runtime-dos",
            "cve": "CVE-2022-45199",
            "id": "pyup.io-72824",
            "more_info_path": "/vulnerabilities/CVE-2022-45199/72824",
            "specs": [
                ">=9.2.0,<9.3.0"
            ],
            "v": ">=9.2.0,<9.3.0"
        }
    ],
    "pillwo": [
        {
            "advisory": "Pillwo is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51748",
            "id": "pyup.io-51748",
            "more_info_path": "/vulnerabilities/PVE-2022-51748/51748",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pims": [
        {
            "advisory": "Pims 0.6.1 and prior uses 'loci_tools.jar', which is affected by critical and severe vulnerabilities.\r\nhttps://github.com/soft-matter/pims/issues/400\r\nhttps://github.com/soft-matter/pims/pull/403",
            "cve": "CVE-2021-44832",
            "id": "pyup.io-44456",
            "more_info_path": "/vulnerabilities/CVE-2021-44832/44456",
            "specs": [
                "<=0.6.1"
            ],
            "v": "<=0.6.1"
        },
        {
            "advisory": "Pims 0.6.1 and prior uses 'loci_tools.jar', which is affected by critical and severe vulnerabilities.\r\nhttps://github.com/soft-matter/pims/issues/400\r\nhttps://github.com/soft-matter/pims/pull/403",
            "cve": "CVE-2021-45105",
            "id": "pyup.io-43596",
            "more_info_path": "/vulnerabilities/CVE-2021-45105/43596",
            "specs": [
                "<=0.6.1"
            ],
            "v": "<=0.6.1"
        },
        {
            "advisory": "Pims 0.6.1 and prior uses 'loci_tools.jar', which is affected by critical and severe vulnerabilities.\r\nhttps://github.com/soft-matter/pims/issues/400\r\nhttps://github.com/soft-matter/pims/pull/403",
            "cve": "CVE-2021-44228",
            "id": "pyup.io-43594",
            "more_info_path": "/vulnerabilities/CVE-2021-44228/43594",
            "specs": [
                "<=0.6.1"
            ],
            "v": "<=0.6.1"
        },
        {
            "advisory": "Pims 0.7 and prior uses 'loci_tools.jar', which is affected by critical and severe vulnerabilities.\r\nhttps://github.com/soft-matter/pims/issues/400\r\nhttps://github.com/soft-matter/pims/pull/403",
            "cve": "CVE-2021-45046",
            "id": "pyup.io-43595",
            "more_info_path": "/vulnerabilities/CVE-2021-45046/43595",
            "specs": [
                "<=0.7"
            ],
            "v": "<=0.7"
        }
    ],
    "pinax-likes": [
        {
            "advisory": "Pinax-likes before 1.1 allows users to like anything and everything, which could potentially lead to security problems (ex. liking entries in permission tables, and thus seeing their content; liking administrative users and thus getting their username).\r\nhttps://github.com/pinax/pinax-likes/commit/2b906a4f85acc54c72d4a9f569da4ecf63a59eb3",
            "cve": "PVE-2021-25955",
            "id": "pyup.io-25955",
            "more_info_path": "/vulnerabilities/PVE-2021-25955/25955",
            "specs": [
                "<1.1"
            ],
            "v": "<1.1"
        }
    ],
    "pinecone-client": [
        {
            "advisory": "Pinecone-client 2.2.2 now specifies its numpy dependency to be version 1.22.0 or higher, aiming to rectify a low-severity vulnerability identified as CVE-2021-34141.",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-67088",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/67088",
            "specs": [
                "<2.2.2"
            ],
            "v": "<2.2.2"
        },
        {
            "advisory": "Pinecone-client 2.2.2  updates its `protobuf` dependency from `3.19.3` to `~=3.19.5` to address a potential denial-of-service vector.",
            "cve": "CVE-2022-1941",
            "id": "pyup.io-67153",
            "more_info_path": "/vulnerabilities/CVE-2022-1941/67153",
            "specs": [
                "<2.2.2"
            ],
            "v": "<2.2.2"
        }
    ],
    "pinscrape": [
        {
            "advisory": "Pinscrape version 3.0.4 has upgraded the tqdm library to version 4.66.3 due to CVE-2024-34062.",
            "cve": "CVE-2024-34062",
            "id": "pyup.io-70988",
            "more_info_path": "/vulnerabilities/CVE-2024-34062/70988",
            "specs": [
                "<3.0.4"
            ],
            "v": "<3.0.4"
        }
    ],
    "pioreactor": [
        {
            "advisory": "Pioreactor 23.11.15rc0 includes a fix for a command injection vulnerability.\r\nhttps://github.com/Pioreactor/pioreactor/commit/c40d2c67a2e49c6d6a395c0789cb35711af2f70d",
            "cve": "PVE-2023-62381",
            "id": "pyup.io-62381",
            "more_info_path": "/vulnerabilities/PVE-2023-62381/62381",
            "specs": [
                "<23.11.15rc0"
            ],
            "v": "<23.11.15rc0"
        }
    ],
    "pip": [
        {
            "advisory": "pip before 1.3 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which allows man-in-the-middle attackers to execute arbitrary code via a crafted response to a \"pip install\" operation.",
            "cve": "CVE-2013-1629",
            "id": "pyup.io-33140",
            "more_info_path": "/vulnerabilities/CVE-2013-1629/33140",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        },
        {
            "advisory": "pip before 1.3 allows local users to overwrite arbitrary files via a symlink attack on a file in the /tmp/pip-build temporary directory.",
            "cve": "CVE-2013-1888",
            "id": "pyup.io-33141",
            "more_info_path": "/vulnerabilities/CVE-2013-1888/33141",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        },
        {
            "advisory": "Pip 1.4 includes a security fix related to certificate DNS wildcard matching.\r\nhttps://github.com/python/cpython/issues/62180",
            "cve": "CVE-2013-2099",
            "id": "pyup.io-25959",
            "more_info_path": "/vulnerabilities/CVE-2013-2099/25959",
            "specs": [
                "<1.4"
            ],
            "v": "<1.4"
        },
        {
            "advisory": "The mirroring support (-M, --use-mirrors) in Python Pip before 1.5 uses insecure DNS querying and authenticity checks which allows attackers to perform man-in-the-middle attacks. See CVE-2013-5123.",
            "cve": "CVE-2013-5123",
            "id": "pyup.io-37752",
            "more_info_path": "/vulnerabilities/CVE-2013-5123/37752",
            "specs": [
                "<1.5"
            ],
            "v": "<1.5"
        },
        {
            "advisory": "Versions of Pip prior to 19.2 are vulnerable to a directory traversal attack during the installation process from a URL. This vulnerability stems from improperly handling filenames in the Content-Disposition header that include path traversal sequences, potentially allowing unauthorized overwrite of critical files such as /root/.ssh/authorized_keys. The flaw is specifically found in the _download_http_url function within _internal/download.py.",
            "cve": "CVE-2019-20916",
            "id": "pyup.io-38765",
            "more_info_path": "/vulnerabilities/CVE-2019-20916/38765",
            "specs": [
                "<19.2"
            ],
            "v": "<19.2"
        },
        {
            "advisory": "A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity.",
            "cve": "CVE-2021-3572",
            "id": "pyup.io-42559",
            "more_info_path": "/vulnerabilities/CVE-2021-3572/42559",
            "specs": [
                "<21.1"
            ],
            "v": "<21.1"
        },
        {
            "advisory": "An issue was discovered in Pip (all versions) because it installs the version with the highest version number, even if the user had intended to obtain a private package from a private index. This only affects use of the --extra-index-url option, and exploitation requires that the package does not already exist in the public index (and thus the attacker can put the package there with an arbitrary version number). A warning was added about this behavior in version 21.1.\r\nNOTE: it has been reported that this is intended functionality and the user is responsible for using --extra-index-url securely.",
            "cve": "CVE-2018-20225",
            "id": "pyup.io-67599",
            "more_info_path": "/vulnerabilities/CVE-2018-20225/67599",
            "specs": [
                "<21.1"
            ],
            "v": "<21.1"
        },
        {
            "advisory": "Pip 21.1 updates its dependency 'urllib3' to v1.26.4 due to security issues.",
            "cve": "CVE-2021-28363",
            "id": "pyup.io-40291",
            "more_info_path": "/vulnerabilities/CVE-2021-28363/40291",
            "specs": [
                "<21.1"
            ],
            "v": "<21.1"
        },
        {
            "advisory": "Affected versions of Pip are vulnerable to Command Injection. When installing a package from a Mercurial VCS URL (ie \"pip install hg+...\") with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to the \"hg clone\" call (ie \"--config\"). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who aren't installing from Mercurial.",
            "cve": "CVE-2023-5752",
            "id": "pyup.io-62044",
            "more_info_path": "/vulnerabilities/CVE-2023-5752/62044",
            "specs": [
                "<23.3"
            ],
            "v": "<23.3"
        },
        {
            "advisory": "Pip solves a security vulnerability that previously allowed maliciously crafted wheel files to execute unauthorized code during installation.",
            "cve": "PVE-2025-75180",
            "id": "pyup.io-75180",
            "more_info_path": "/vulnerabilities/PVE-2025-75180/75180",
            "specs": [
                "<25.0"
            ],
            "v": "<25.0"
        },
        {
            "advisory": "Affected versions of the pip package are vulnerable to Arbitrary File Overwrite due to improper validation of symbolic link targets in the fallback tar extraction code. In src/pip/_internal/utils/unpacking.py, the _untar_without_filter routine used when the Python tarfile module lacks PEP 706 (no tarfile.data_filter) extracted symlink members with tar._extract_member without verifying that link destinations resolve under the extraction root, a check later added via the is_symlink_target_in_tar helper.",
            "cve": "CVE-2025-8869",
            "id": "pyup.io-79883",
            "more_info_path": "/vulnerabilities/CVE-2025-8869/79883",
            "specs": [
                "<25.2"
            ],
            "v": "<25.2"
        },
        {
            "advisory": "pip before 6.0 is not using a randomized and secure default build directory when possible. (CVE-2014-8991).",
            "cve": "CVE-2014-8991",
            "id": "pyup.io-25960",
            "more_info_path": "/vulnerabilities/CVE-2014-8991/25960",
            "specs": [
                "<6.0"
            ],
            "v": "<6.0"
        },
        {
            "advisory": "Pip 6.1.0 updates its bundled dependency 'requests' to 2.6.0 to include a security fix.",
            "cve": "CVE-2015-2296",
            "id": "pyup.io-25961",
            "more_info_path": "/vulnerabilities/CVE-2015-2296/25961",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        }
    ],
    "pipenv": [
        {
            "advisory": "Pipenv 2020.5.28 updates its dependency 'pyyaml' minimum requirement to v5.3.1 to include security fixes.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-45802",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/45802",
            "specs": [
                "<2020.5.28"
            ],
            "v": "<2020.5.28"
        },
        {
            "advisory": "Pipenv 2020.5.28 updates its dependency 'urllib3' to v1.25.9 to include security fixes.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-45798",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/45798",
            "specs": [
                "<2020.5.28"
            ],
            "v": "<2020.5.28"
        },
        {
            "advisory": "Pipenv 2020.5.28 updates its dependency 'urllib3' to v1.25.9 to include security fixes.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-45800",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/45800",
            "specs": [
                "<2020.5.28"
            ],
            "v": "<2020.5.28"
        },
        {
            "advisory": "Pipenv 2020.5.28 updates its dependency 'pyyaml' minimum requirement to v5.3.1 to include security fixes.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-45801",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/45801",
            "specs": [
                "<2020.5.28"
            ],
            "v": "<2020.5.28"
        },
        {
            "advisory": "Pipenv 2020.5.28 updates its dependency 'jinja2' to v2.11.2 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-38334",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/38334",
            "specs": [
                "<2020.5.28"
            ],
            "v": "<2020.5.28"
        },
        {
            "advisory": "Pipenv 2020.5.28 updates its dependency 'urllib3' to v1.25.9 to include security fixes.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-45799",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/45799",
            "specs": [
                "<2020.5.28"
            ],
            "v": "<2020.5.28"
        },
        {
            "advisory": "Pipenv 2022.1.8 includes a fix for CVE-2022-21668: Starting with version 2018.10.9 and prior to version 2022.1.8, a flaw in pipenv's parsing of requirements files allows an attacker to insert a specially crafted string inside a comment anywhere within a requirements.txt file, which will cause victims who use pipenv to install the requirements file to download dependencies from a package index server controlled by the attacker. By embedding malicious code in packages served from their malicious index server, the attacker can trigger arbitrary remote code execution (RCE) on the victims' systems. If an attacker is able to hide a malicious '--index-url' option in a requirements file that a victim installs with pipenv, the attacker can embed arbitrary malicious code in packages served from their malicious index server that will be executed on the victim's host during installation (remote code execution/RCE). When pip installs from a source distribution, any code in the setup.py is executed by the install process.\r\nhttps://github.com/pypa/pipenv/security/advisories/GHSA-qc9x-gjcv-465w",
            "cve": "CVE-2022-21668",
            "id": "pyup.io-44492",
            "more_info_path": "/vulnerabilities/CVE-2022-21668/44492",
            "specs": [
                ">=2018.10.9,<=2021.11.23"
            ],
            "v": ">=2018.10.9,<=2021.11.23"
        }
    ],
    "pipenv-setup": [
        {
            "advisory": "Pipenv-setup 3.1.4 updates its dependency 'sqlalchemy' to v1.3.0 to include a security fix.",
            "cve": "CVE-2018-19787",
            "id": "pyup.io-42763",
            "more_info_path": "/vulnerabilities/CVE-2018-19787/42763",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Pipenv-setup 3.1.4 updates its dependency 'sqlalchemy' to v1.3.0 to include a security fix.",
            "cve": "CVE-2019-7548",
            "id": "pyup.io-42760",
            "more_info_path": "/vulnerabilities/CVE-2019-7548/42760",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Pipenv-setup 3.1.4 updates its dependency 'sqlalchemy' to v1.3.0 to include a security fix.",
            "cve": "CVE-2019-7164",
            "id": "pyup.io-42742",
            "more_info_path": "/vulnerabilities/CVE-2019-7164/42742",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Pipenv-setup 3.1.4 updates its dependency 'lxml' to v4.6.3 to include a security fix.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-42761",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/42761",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Pipenv-setup 3.1.4 updates its dependency 'sqlalchemy' to v1.3.0 to include a security fix.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-42762",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/42762",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        }
    ],
    "piperider": [
        {
            "advisory": "Piperider 0.5.0rc.4\r\n# included",
            "cve": "PVE-2022-50292",
            "id": "pyup.io-50292",
            "more_info_path": "/vulnerabilities/PVE-2022-50292/50292",
            "specs": [
                "<0.5.0rc.4"
            ],
            "v": "<0.5.0rc.4"
        },
        {
            "advisory": "Piperider 0.5.0rc1 updates its NPM dependency \"nth-check\" to v2.0.1 to include a security fix.",
            "cve": "CVE-2021-3803",
            "id": "pyup.io-50270",
            "more_info_path": "/vulnerabilities/CVE-2021-3803/50270",
            "specs": [
                "<0.5.0rc1"
            ],
            "v": "<0.5.0rc1"
        }
    ],
    "pipreqs": [
        {
            "advisory": "A dependency confusion in pipreqs v0.3.0 to v0.4.11 allows attackers to execute arbitrary code via uploading a crafted PyPI package to the chosen repository server.",
            "cve": "CVE-2023-31543",
            "id": "pyup.io-65047",
            "more_info_path": "/vulnerabilities/CVE-2023-31543/65047",
            "specs": [
                ">=0.3.0,<0.4.12"
            ],
            "v": ">=0.3.0,<0.4.12"
        }
    ],
    "piqueserver": [
        {
            "advisory": "Piqueserver 1.1.0 includes fixes for potential Denial of Service vulnerabilities.\r\nhttps://github.com/piqueserver/piqueserver/pull/722",
            "cve": "PVE-2023-59290",
            "id": "pyup.io-59290",
            "more_info_path": "/vulnerabilities/PVE-2023-59290/59290",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pirate-get": [
        {
            "advisory": "pirate-get before 0.2.8 is not properly validating torrent file names.\r\n\r\n- https://github.com/vikstrous/pirate-get/issues/73",
            "cve": "PVE-2021-34168",
            "id": "pyup.io-34168",
            "more_info_path": "/vulnerabilities/PVE-2021-34168/34168",
            "specs": [
                "<0.2.8"
            ],
            "v": "<0.2.8"
        }
    ],
    "pirxcypinger": [
        {
            "advisory": "Pirxcypinger 3.2 includes a fix for preventing abuse of URLs.\r\nhttps://github.com/PirxcyFinal/PirxcyPinger/commit/bc318987c5e8bf72bf4994ff797f09acce815fba",
            "cve": "PVE-2021-42378",
            "id": "pyup.io-42378",
            "more_info_path": "/vulnerabilities/PVE-2021-42378/42378",
            "specs": [
                "<3.2"
            ],
            "v": "<3.2"
        }
    ],
    "pjrpc": [
        {
            "advisory": "Pjrpc 1.6.0 updates its dependency 'httpx' requirement to '^0.23.0' to include a security fix.",
            "cve": "CVE-2021-41945",
            "id": "pyup.io-49753",
            "more_info_path": "/vulnerabilities/CVE-2021-41945/49753",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        }
    ],
    "pkgconf": [
        {
            "advisory": "Affected versions of Pkgconf are vulnerable to buffer overflow. Variable duplication can cause unbounded string expansion due to incorrect checks in libpkgconf/tuple.c:pkgconf_tuple_parse. For example, a .pc file containing a few hundred bytes can expand to one billion bytes.",
            "cve": "CVE-2023-24056",
            "id": "pyup.io-71263",
            "more_info_path": "/vulnerabilities/CVE-2023-24056/71263",
            "specs": [
                "<1.9.4"
            ],
            "v": "<1.9.4"
        }
    ],
    "pkgcore": [
        {
            "advisory": "pkgcore 0.4.7.12 includes a security fix; force cwd to something controlled for ebuild env.  This blocks an attack detailed in glsa 200810-02; namely that an ebuild invoking python -c (which looks in cwd for modules to load) allows for an attacker to slip something in.",
            "cve": "PVE-2021-25962",
            "id": "pyup.io-25962",
            "more_info_path": "/vulnerabilities/PVE-2021-25962/25962",
            "specs": [
                "<0.4.7.12"
            ],
            "v": "<0.4.7.12"
        }
    ],
    "pkgutil": [
        {
            "advisory": "Pkgutil is a typosquatting package. It shows a malicious behavior, for example, it may leak your sensitive data and/or gain unauthorized persistence in your system.\r\nhttps://www.zdnet.com/article/twelve-malicious-python-libraries-found-and-removed-from-pypi/",
            "cve": "PVE-2022-45418",
            "id": "pyup.io-45418",
            "more_info_path": "/vulnerabilities/PVE-2022-45418/45418",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "plaid2qif": [
        {
            "advisory": "Plaid2qif 1.3.6 updates its dependency 'urllib3' to v1.26.5 to include security fixes.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-45731",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/45731",
            "specs": [
                "<1.3.6"
            ],
            "v": "<1.3.6"
        },
        {
            "advisory": "Plaid2qif 1.3.6 updates its dependency 'pygments' to v2.7.4 to include security fixes.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-45734",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/45734",
            "specs": [
                "<1.3.6"
            ],
            "v": "<1.3.6"
        },
        {
            "advisory": "Plaid2qif 1.3.6 updates its dependency 'bleach' to v3.3.0 to include a security fix.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-45735",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/45735",
            "specs": [
                "<1.3.6"
            ],
            "v": "<1.3.6"
        },
        {
            "advisory": "Plaid2qif 1.3.6 updates its dependency 'bleach' to v3.3.0 to include a security fix.",
            "cve": "CVE-2021-23980",
            "id": "pyup.io-45580",
            "more_info_path": "/vulnerabilities/CVE-2021-23980/45580",
            "specs": [
                "<1.3.6"
            ],
            "v": "<1.3.6"
        },
        {
            "advisory": "Plaid2qif 1.3.6 updates its dependency 'urllib3' to v1.26.5 to include security fixes.",
            "cve": "CVE-2021-28363",
            "id": "pyup.io-45732",
            "more_info_path": "/vulnerabilities/CVE-2021-28363/45732",
            "specs": [
                "<1.3.6"
            ],
            "v": "<1.3.6"
        },
        {
            "advisory": "Plaid2qif 1.3.6 updates its dependency 'cryptography' to v3.3.2 to include a security fix.",
            "cve": "CVE-2020-36242",
            "id": "pyup.io-45733",
            "more_info_path": "/vulnerabilities/CVE-2020-36242/45733",
            "specs": [
                "<1.3.6"
            ],
            "v": "<1.3.6"
        }
    ],
    "planai": [
        {
            "advisory": "Affected versions of planai are vulnerable to race conditions. The vulnerability is triggered under concurrent task execution. Vulnerable methods include _dispatch_notify, _dispatch_once, _notify_completed, and _task_completed. Exploitability increases with system load and concurrency. The commit fixes this by implementing consistent use of self.task_lock for shared state modifications, improving task failure tracking, and refining the dispatch loop logic. This vulnerability is specific to multi-threaded Python applications using the Dispatcher class.",
            "cve": "PVE-2024-73015",
            "id": "pyup.io-73015",
            "more_info_path": "/vulnerabilities/PVE-2024-73015/73015",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "planet": [
        {
            "advisory": "Planet 2.0.1 fixes a security issue where a secret file was being created with read access for other users on the machine.\r\nhttps://github.com/planetlabs/planet-client-python/commit/d71415a83119c5e89d7b80d5f940d162376ee3b7\r\nhttps://github.com/planetlabs/planet-client-python/security/advisories/GHSA-j5fj-rfh6-qj85",
            "cve": "CVE-2023-32303",
            "id": "pyup.io-58650",
            "more_info_path": "/vulnerabilities/CVE-2023-32303/58650",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        }
    ],
    "planetmint": [
        {
            "advisory": "Planetmint 2.4.6 updates its dependency 'requests' to v2.31.0 to include a security fix.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-58797",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/58797",
            "specs": [
                "<2.4.6"
            ],
            "v": "<2.4.6"
        }
    ],
    "planetmint-driver": [
        {
            "advisory": "Planetmint-driver 0.18.3 updates its dependency 'tornado' to version '6.3.2' to include a security fix.\r\nhttps://github.com/planetmint/planetmint-driver-python/commit/b492f3fd61f8514e82b1c0f06d64dfc21dc762d6",
            "cve": "CVE-2023-28370",
            "id": "pyup.io-59049",
            "more_info_path": "/vulnerabilities/CVE-2023-28370/59049",
            "specs": [
                "<0.18.3"
            ],
            "v": "<0.18.3"
        },
        {
            "advisory": "Planetmint-driver 0.18.3 updates its dependency 'requests' to version '2.31.0' to include a security fix.\r\nhttps://github.com/planetmint/planetmint-driver-python/commit/050332d4c4121b304af1309e95c484cc9ec71947",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-59045",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/59045",
            "specs": [
                "<0.18.3"
            ],
            "v": "<0.18.3"
        },
        {
            "advisory": "Planetmint-driver 0.5.2 updates its dependency 'cryptoconditions' because of a security vulnerability.",
            "cve": "CVE-2018-10903",
            "id": "pyup.io-44736",
            "more_info_path": "/vulnerabilities/CVE-2018-10903/44736",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        }
    ],
    "planetmint-driver-python": [
        {
            "advisory": "Planetmint-driver 0.18.3 updates its dependency 'requests' to version '2.31.0' to include a security fix.\r\nhttps://github.com/planetmint/planetmint-driver-python/commit/050332d4c4121b304af1309e95c484cc9ec71947",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-61872",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/61872",
            "specs": [
                "<0.18.3"
            ],
            "v": "<0.18.3"
        },
        {
            "advisory": "Planetmint-driver 0.18.3 updates its dependency 'tornado' to version '6.3.2' to include a security fix.\r\nhttps://github.com/planetmint/planetmint-driver-python/commit/b492f3fd61f8514e82b1c0f06d64dfc21dc762d6",
            "cve": "CVE-2023-28370",
            "id": "pyup.io-61873",
            "more_info_path": "/vulnerabilities/CVE-2023-28370/61873",
            "specs": [
                "<0.18.3"
            ],
            "v": "<0.18.3"
        },
        {
            "advisory": "Planetmint-driver-python 0.5.2 updates its dependency 'cryptogtaphy' to include a security fix.",
            "cve": "CVE-2018-10903",
            "id": "pyup.io-55041",
            "more_info_path": "/vulnerabilities/CVE-2018-10903/55041",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        }
    ],
    "platformio": [
        {
            "advisory": "platformio 4.1.0 fixes a security issue when extracting items from TAR archive - see https://github.com/platformio/platformio-core/issues/2995",
            "cve": "PVE-2021-37869",
            "id": "pyup.io-37869",
            "more_info_path": "/vulnerabilities/PVE-2021-37869/37869",
            "specs": [
                "<4.1.0"
            ],
            "v": "<4.1.0"
        },
        {
            "advisory": "Platformio 6.1.7 includes fixes for shell injection vulnerabilities when converting INO files to CPP.\r\nhttps://github.com/platformio/platformio-core/commit/15d53c95c06d03b648c18548d1cb3258338e417b",
            "cve": "PVE-2023-57527",
            "id": "pyup.io-57527",
            "more_info_path": "/vulnerabilities/PVE-2023-57527/57527",
            "specs": [
                "<6.1.7"
            ],
            "v": "<6.1.7"
        }
    ],
    "plex-mpv-shim": [
        {
            "advisory": "Plex-mpv-shim 1.10.01 upgrades to a newer MPV build for security reasons.",
            "cve": "PVE-2021-42829",
            "id": "pyup.io-42829",
            "more_info_path": "/vulnerabilities/PVE-2021-42829/42829",
            "specs": [
                "<1.10.01"
            ],
            "v": "<1.10.01"
        }
    ],
    "plexapi": [
        {
            "advisory": "Plexapi 4.3.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/pkkid/python-plexapi/pull/625",
            "cve": "PVE-2023-60087",
            "id": "pyup.io-60087",
            "more_info_path": "/vulnerabilities/PVE-2023-60087/60087",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        }
    ],
    "plomino": [
        {
            "advisory": "plomino before 1.18 has a major vulnerability in open_url (now, targeted sources must be declared safe from an local package).",
            "cve": "PVE-2021-25963",
            "id": "pyup.io-25963",
            "more_info_path": "/vulnerabilities/PVE-2021-25963/25963",
            "specs": [
                "<1.18"
            ],
            "v": "<1.18"
        },
        {
            "advisory": "plomino 1.5.3 includes a security fix: when a group has PlominoAuthors rights, members of this group are just authors on their own documents.",
            "cve": "PVE-2021-25964",
            "id": "pyup.io-25964",
            "more_info_path": "/vulnerabilities/PVE-2021-25964/25964",
            "specs": [
                "<1.5.3"
            ],
            "v": "<1.5.3"
        }
    ],
    "plone": [
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in skins/plone_templates/default_error_message.pt in Plone before 2.5.3 allows remote attackers to inject arbitrary web script or HTML via the type_name parameter to Members/ipa/createObject.",
            "cve": "CVE-2011-1340",
            "id": "pyup.io-25966",
            "more_info_path": "/vulnerabilities/CVE-2011-1340/25966",
            "specs": [
                "<2.5.3"
            ],
            "v": "<2.5.3"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in the LiveSearch module in Plone before 3.0.4 allows remote attackers to inject arbitrary web script or HTML via the Description field for search results, as demonstrated using the onerror Javascript even in an IMG tag.",
            "cve": "CVE-2008-4571",
            "id": "pyup.io-61260",
            "more_info_path": "/vulnerabilities/CVE-2008-4571/61260",
            "specs": [
                "<3.0.4"
            ],
            "v": "<3.0.4"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in PortalTransforms in Plone 2.1 through 3.3.4 before hotfix 20100612 allows remote attackers to inject arbitrary web script or HTML via the safe_html transform.",
            "cve": "CVE-2010-2422",
            "id": "pyup.io-25967",
            "more_info_path": "/vulnerabilities/CVE-2010-2422/25967",
            "specs": [
                "<3.3.4"
            ],
            "v": "<3.3.4"
        },
        {
            "advisory": "kupu_spellcheck.py in Kupu in Plone before 4.0 allows remote attackers to cause a denial of service (ZServer thread lock) via a crafted URL.",
            "cve": "CVE-2012-5496",
            "id": "pyup.io-33143",
            "more_info_path": "/vulnerabilities/CVE-2012-5496/33143",
            "specs": [
                "<4.0"
            ],
            "v": "<4.0"
        },
        {
            "advisory": "Plone 4.0.7 and 4.1.1 include a fix for CVE-2011-1948: Cross-site scripting (XSS) vulnerability in Plone 4.1 and earlier allows remote attackers to inject arbitrary web script or HTML via a crafted URL.\r\nhttps://plone.org/security/hotfix/20110531/cross-site-scripting",
            "cve": "CVE-2011-1948",
            "id": "pyup.io-25972",
            "more_info_path": "/vulnerabilities/CVE-2011-1948/25972",
            "specs": [
                "<4.0.7",
                ">=4.1a0,<=4.1"
            ],
            "v": "<4.0.7,>=4.1a0,<=4.1"
        },
        {
            "advisory": "Plone 4.1.3 and earlier computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.",
            "cve": "CVE-2011-4462",
            "id": "pyup.io-25973",
            "more_info_path": "/vulnerabilities/CVE-2011-4462/25973",
            "specs": [
                "<4.1.3"
            ],
            "v": "<4.1.3"
        },
        {
            "advisory": "ftp.py in Plone before 4.2.3 and 4.3b1 allows remote attackers to read hidden folder contents via unspecified vectors.",
            "cve": "CVE-2012-5503",
            "id": "pyup.io-25999",
            "more_info_path": "/vulnerabilities/CVE-2012-5503/25999",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone versions 4.2.3 and 4.3b1 include a fix for CVE-2012-6661, a vulnerability in its dependency \"zope\".",
            "cve": "CVE-2012-6661",
            "id": "pyup.io-42186",
            "more_info_path": "/vulnerabilities/CVE-2012-6661/42186",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5506: python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to cause a denial of service (infinite loop) via an RSS feed request for a folder the user does not have permission to access.",
            "cve": "CVE-2012-5506",
            "id": "pyup.io-35397",
            "more_info_path": "/vulnerabilities/CVE-2012-5506/35397",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "z3c.form, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote attackers to obtain the default form field values by leveraging knowledge of the form location and the element id.",
            "cve": "CVE-2012-5491",
            "id": "pyup.io-35384",
            "more_info_path": "/vulnerabilities/CVE-2012-5491/35384",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5501: at_download.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to read arbitrary BLOBs (Files and Images) stored on custom content types via a crafted URL.",
            "cve": "CVE-2012-5501",
            "id": "pyup.io-35393",
            "more_info_path": "/vulnerabilities/CVE-2012-5501/35393",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "The error pages in Plone before 4.2.3 and 4.3 before beta 1 allow remote attackers to obtain random numbers and derive the PRNG state for password resets via unspecified vectors. NOTE: this identifier was SPLIT per ADT2 due to different vulnerability types. CVE-2012-6661 was assigned for the PRNG reseeding issue in Zope.",
            "cve": "CVE-2012-5508",
            "id": "pyup.io-35398",
            "more_info_path": "/vulnerabilities/CVE-2012-5508/35398",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "uid_catalog.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to obtain metadata about hidden objects via a crafted URL.",
            "cve": "CVE-2012-5492",
            "id": "pyup.io-35385",
            "more_info_path": "/vulnerabilities/CVE-2012-5492/35385",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5487: The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.",
            "cve": "CVE-2012-5487",
            "id": "pyup.io-35381",
            "more_info_path": "/vulnerabilities/CVE-2012-5487/35381",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5499: python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to cause a denial of service (memory consumption) via a large value, related to formatColumns.",
            "cve": "CVE-2012-5499",
            "id": "pyup.io-35391",
            "more_info_path": "/vulnerabilities/CVE-2012-5499/35391",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5495: python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to \"go_back.\"",
            "cve": "CVE-2012-5495",
            "id": "pyup.io-35388",
            "more_info_path": "/vulnerabilities/CVE-2012-5495/35388",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors, related to \"{u,}translate.\"",
            "cve": "CVE-2012-5494",
            "id": "pyup.io-35387",
            "more_info_path": "/vulnerabilities/CVE-2012-5494/35387",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5500: The batch id change script (renameObjectsByPaths.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to change the titles of content items by leveraging a valid CSRF token in a crafted request.",
            "cve": "CVE-2012-5500",
            "id": "pyup.io-35392",
            "more_info_path": "/vulnerabilities/CVE-2012-5500/35392",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "gtbn.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain permissions to bypass the Python sandbox and execute arbitrary Python code via unspecified vectors.",
            "cve": "CVE-2012-5493",
            "id": "pyup.io-35386",
            "more_info_path": "/vulnerabilities/CVE-2012-5493/35386",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5504: Cross-site scripting (XSS) vulnerability in widget_traversal.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.",
            "cve": "CVE-2012-5504",
            "id": "pyup.io-35395",
            "more_info_path": "/vulnerabilities/CVE-2012-5504/35395",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5498: queryCatalog.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to bypass caching and cause a denial of service via a crafted request to a collection.",
            "cve": "CVE-2012-5498",
            "id": "pyup.io-35390",
            "more_info_path": "/vulnerabilities/CVE-2012-5498/35390",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5502: Cross-site scripting (XSS) vulnerability in safe_html.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with permissions to edit content to inject arbitrary web script or HTML via unspecified vectors.",
            "cve": "CVE-2012-5502",
            "id": "pyup.io-35394",
            "more_info_path": "/vulnerabilities/CVE-2012-5502/35394",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5488: Python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.",
            "cve": "CVE-2012-5488",
            "id": "pyup.io-35382",
            "more_info_path": "/vulnerabilities/CVE-2012-5488/35382",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5485: registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.",
            "cve": "CVE-2012-5485",
            "id": "pyup.io-35380",
            "more_info_path": "/vulnerabilities/CVE-2012-5485/35380",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in kssdevel.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.",
            "cve": "CVE-2012-5490",
            "id": "pyup.io-35383",
            "more_info_path": "/vulnerabilities/CVE-2012-5490/35383",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5497: membership_tool.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to enumerate user account names via a crafted URL.",
            "cve": "CVE-2012-5497",
            "id": "pyup.io-35389",
            "more_info_path": "/vulnerabilities/CVE-2012-5497/35389",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.2.3 and 4.3b1 include a fix for CVE-2012-5505: atat.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to read private data structures via a request for a view without a name.",
            "cve": "CVE-2012-5505",
            "id": "pyup.io-35396",
            "more_info_path": "/vulnerabilities/CVE-2012-5505/35396",
            "specs": [
                "<4.2.3",
                ">=4.3a1,<4.3b1"
            ],
            "v": "<4.2.3,>=4.3a1,<4.3b1"
        },
        {
            "advisory": "Plone 4.3 includes a fix for CVE-2012-5486: It was discovered that Plone, included as a part of luci, did not properly sanitize HTTP headers provided within certain URL requests. A remote attacker could use a specially crafted URL that, when processed, would cause the injected HTTP headers to be returned as a part of the Plone HTTP response, potentially allowing the attacker to perform other more advanced attacks.",
            "cve": "CVE-2012-5486",
            "id": "pyup.io-25996",
            "more_info_path": "/vulnerabilities/CVE-2012-5486/25996",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Plone 4.3.12 and 5.0.7 include a fix for CVE-2016-7147: Cross-site scripting (XSS) vulnerability in the manage_findResult component in the search feature in Zope ZMI in Plone before 4.3.12 and 5.x before 5.0.7 allows remote attackers to inject arbitrary web script or HTML via vectors involving double quotes, as demonstrated by the obj_ids:tokens parameter. \r\nNOTE: this vulnerability exists because of an incomplete fix for CVE-2016-7140.",
            "cve": "CVE-2016-7147",
            "id": "pyup.io-35689",
            "more_info_path": "/vulnerabilities/CVE-2016-7147/35689",
            "specs": [
                "<4.3.12",
                ">=5.0a1,<5.0.7"
            ],
            "v": "<4.3.12,>=5.0a1,<5.0.7"
        },
        {
            "advisory": "Plone 4.3.9 includes a fix for CVE-2015-7293: Multiple cross-site request forgery (CSRF) vulnerabilities in Zope Management Interface 4.3.7 and earlier, and Plone before 5.x.\r\nhttps://plone.org/security/hotfix/20151006",
            "cve": "CVE-2015-7293",
            "id": "pyup.io-35642",
            "more_info_path": "/vulnerabilities/CVE-2015-7293/35642",
            "specs": [
                "<4.3.15"
            ],
            "v": "<4.3.15"
        },
        {
            "advisory": "The official plone Docker images before version of 4.3.18-alpine (Alpine specific) contain a blank password for a root user. System using the plone docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password. See CVE-2020-35190.",
            "cve": "CVE-2020-35190",
            "id": "pyup.io-39305",
            "more_info_path": "/vulnerabilities/CVE-2020-35190/39305",
            "specs": [
                "<4.3.18"
            ],
            "v": "<4.3.18"
        },
        {
            "advisory": "Plone 5.2.5 and 4.3.20 include a fix for CVE-2021-33926: By adding an RSS feed portlet in their dashboard, a normal member could try loading the RSS feed of an internal service which is otherwise unreachable for this member.\r\nhttps://plone.org/security/hotfix/20210518/blind-ssrf-via-feedparser-accessing-an-internal-url",
            "cve": "CVE-2021-33926",
            "id": "pyup.io-53375",
            "more_info_path": "/vulnerabilities/CVE-2021-33926/53375",
            "specs": [
                "<4.3.20",
                ">=5.0a1,<5.2.5"
            ],
            "v": "<4.3.20,>=5.0a1,<5.2.5"
        },
        {
            "advisory": "There exists a vulnerability that could potentially lead to the unauthorized exposure of information of registered users.",
            "cve": "PVE-2023-99914",
            "id": "pyup.io-62007",
            "more_info_path": "/vulnerabilities/PVE-2023-99914/62007",
            "specs": [
                "<4.3.8",
                ">=5.0a1,<5.0.1"
            ],
            "v": "<4.3.8,>=5.0a1,<5.0.1"
        },
        {
            "advisory": "Plone is exposed to risks associated with reflected cross-site scripting and open redirect. These vulnerabilities can occur when an attacker manages to put a compromised version of the image_view_fullscreen page into a cache, such as Varnish.",
            "cve": "PVE-2023-99927",
            "id": "pyup.io-61947",
            "more_info_path": "/vulnerabilities/PVE-2023-99927/61947",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "Numerous cross-site request forgery vulnerabilities have been discovered within the Zope Management Interface.",
            "cve": "PVE-2023-99915",
            "id": "pyup.io-62006",
            "more_info_path": "/vulnerabilities/PVE-2023-99915/62006",
            "specs": [
                "<5.0a"
            ],
            "v": "<5.0a"
        },
        {
            "advisory": "An issue in Plone Docker Official Image 5.2.13 (5221) open-source software allows for remote code execution via improper validation of input by the HOST headers. See CVE-2024-23055.\r\nhttps://github.com/c0d3x27/CVEs/tree/main/CVE-2024-23055",
            "cve": "CVE-2024-23055",
            "id": "pyup.io-64641",
            "more_info_path": "/vulnerabilities/CVE-2024-23055/64641",
            "specs": [
                "<5.2.13"
            ],
            "v": "<5.2.13"
        },
        {
            "advisory": "The HTTP PUT and DELETE methods are enabled in the Plone official Docker version 5.2.13 (5221), allowing unauthenticated attackers to execute dangerous actions such as uploading files to the server or deleting them. See CVE-2024-23756.",
            "cve": "CVE-2024-23756",
            "id": "pyup.io-65287",
            "more_info_path": "/vulnerabilities/CVE-2024-23756/65287",
            "specs": [
                "<5.2.13"
            ],
            "v": "<5.2.13"
        },
        {
            "advisory": "Plone 5.2.2 contains Products.isurlinportal 1.1.0 with a minor security hardening fix.\r\nhttps://github.com/plone/Products.CMFPlone/commit/ec1b7994c9c4a32d24f9b3f1f5ec0d628234434e\r\nhttps://community.plone.org/t/vulnerability-fix-products-isurlinportal-1-1-0/12735",
            "cve": "PVE-2021-38990",
            "id": "pyup.io-38990",
            "more_info_path": "/vulnerabilities/PVE-2021-38990/38990",
            "specs": [
                "<5.2.2"
            ],
            "v": "<5.2.2"
        },
        {
            "advisory": "Plone before 5.2.3 allows XXE attacks via a feature that is explicitly only available to the Manager role. See CVE-2020-28734.",
            "cve": "CVE-2020-28734",
            "id": "pyup.io-39376",
            "more_info_path": "/vulnerabilities/CVE-2020-28734/39376",
            "specs": [
                "<5.2.3"
            ],
            "v": "<5.2.3"
        },
        {
            "advisory": "Plone before 5.2.3 allows SSRF attacks via the tracebacks feature (only available to the Manager role). See CVE-2020-28735.",
            "cve": "CVE-2020-28735",
            "id": "pyup.io-39377",
            "more_info_path": "/vulnerabilities/CVE-2020-28735/39377",
            "specs": [
                "<5.2.3"
            ],
            "v": "<5.2.3"
        },
        {
            "advisory": "Plone before 5.2.3 allows XXE attacks via a feature that is protected by an unapplied permission of plone.schemaeditor.ManageSchemata (therefore, only available to the Manager role). See CVE-2020-28736.",
            "cve": "CVE-2020-28736",
            "id": "pyup.io-39378",
            "more_info_path": "/vulnerabilities/CVE-2020-28736/39378",
            "specs": [
                "<5.2.3"
            ],
            "v": "<5.2.3"
        },
        {
            "advisory": "Plone CMS until version 5.2.4 has a stored Cross-Site Scripting (XSS) vulnerability in the user fullname property and the file upload functionality. The user's input data is not properly encoded when being echoed back to the user. This data can be interpreted as executable code by the browser and allows an attacker to execute JavaScript in the context of the victim's browser if the victim opens a vulnerable page containing an XSS payload.",
            "cve": "CVE-2021-3313",
            "id": "pyup.io-40528",
            "more_info_path": "/vulnerabilities/CVE-2021-3313/40528",
            "specs": [
                "<5.2.4"
            ],
            "v": "<5.2.4"
        },
        {
            "advisory": "A Cross-Frame Scripting vulnerability has been found on Plone CMS affecting versions below 6.0.5. An attacker could store a malicious URL to be opened by an administrator and execute a malicious iframe element. See CVE-2024-0669.",
            "cve": "CVE-2024-0669",
            "id": "pyup.io-64455",
            "more_info_path": "/vulnerabilities/CVE-2024-0669/64455",
            "specs": [
                "<6.0.5"
            ],
            "v": "<6.0.5"
        },
        {
            "advisory": "Multiple cross-site request forgery (CSRF) vulnerabilities in Plone CMS 3.0.5 and 3.0.6 allow remote attackers to (1) add arbitrary accounts via the join_form page and (2) change the privileges of arbitrary groups via the prefs_groups_overview page.",
            "cve": "CVE-2008-0164",
            "id": "pyup.io-67964",
            "more_info_path": "/vulnerabilities/CVE-2008-0164/67964",
            "specs": [
                "<=3.0.6"
            ],
            "v": "<=3.0.6"
        },
        {
            "advisory": "Plone CMS does not record users' authentication states, and implements the logout feature solely on the client side, which makes it easier for context-dependent attackers to reuse a logged-out session.",
            "cve": "CVE-2008-1395",
            "id": "pyup.io-67965",
            "more_info_path": "/vulnerabilities/CVE-2008-1395/67965",
            "specs": [
                "<=3.1.7"
            ],
            "v": "<=3.1.7"
        },
        {
            "advisory": "Plone CMS 3.x uses invariant data (a client username and a server secret) when calculating an HMAC-SHA1 value for an authentication cookie, which makes it easier for remote attackers to gain permanent access to an account by sniffing the network.",
            "cve": "CVE-2008-1396",
            "id": "pyup.io-67966",
            "more_info_path": "/vulnerabilities/CVE-2008-1396/67966",
            "specs": [
                "<=3.1.7"
            ],
            "v": "<=3.1.7"
        },
        {
            "advisory": "Unspecified vulnerability in (1) Zope 2.12.x before 2.12.19 and 2.13.x before 2.13.8, as used in Plone 4.x and other products, and (2) PloneHotfix20110720 for Plone 3.x allows attackers to gain privileges via unspecified vectors, related to a \"highly serious vulnerability.\" NOTE: this vulnerability exists because of an incorrect fix for CVE-2011-0720.",
            "cve": "CVE-2011-2528",
            "id": "pyup.io-25965",
            "more_info_path": "/vulnerabilities/CVE-2011-2528/25965",
            "specs": [
                "<=3.3.6",
                ">=4.0a1,<4.2"
            ],
            "v": "<=3.3.6,>=4.0a1,<4.2"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in Plone 3.3.0 through 3.3.6, 4.0.0 through 4.0.10, 4.1.0 through 4.1.6, 4.2.0 through 4.2.7, 4.3.x before 4.3.7, and 5.0rc1.",
            "cve": "CVE-2015-7316",
            "id": "pyup.io-35644",
            "more_info_path": "/vulnerabilities/CVE-2015-7316/35644",
            "specs": [
                "<=3.3.6",
                ">=4.0a1,<=4.0.10",
                ">=4.1a1,<=4.1.6",
                ">=4.2a1,<=4.2.7",
                ">=4.3a1,<4.3.7"
            ],
            "v": "<=3.3.6,>=4.0a1,<=4.0.10,>=4.1a1,<=4.1.6,>=4.2a1,<=4.2.7,>=4.3a1,<4.3.7"
        },
        {
            "advisory": "Plone through 5.2.4 allows remote authenticated managers to perform disk I/O via crafted keyword arguments to the ReStructuredText transform in a Python script.",
            "cve": "CVE-2021-33509",
            "id": "pyup.io-40534",
            "more_info_path": "/vulnerabilities/CVE-2021-33509/40534",
            "specs": [
                "<=5.2.4"
            ],
            "v": "<=5.2.4"
        },
        {
            "advisory": "Plone through 5.2.4 allows XSS via the inline_diff methods in Products.CMFDiffTool.",
            "cve": "CVE-2021-33513",
            "id": "pyup.io-40538",
            "more_info_path": "/vulnerabilities/CVE-2021-33513/40538",
            "specs": [
                "<=5.2.4"
            ],
            "v": "<=5.2.4"
        },
        {
            "advisory": "Plone though 5.2.4 allows SSRF via the lxml parser. This affects Diazo themes, Dexterity TTW schemas, and modeleditors in plone.app.theming, plone.app.dexterity, and plone.supermodel.",
            "cve": "CVE-2021-33511",
            "id": "pyup.io-40536",
            "more_info_path": "/vulnerabilities/CVE-2021-33511/40536",
            "specs": [
                "<=5.2.4"
            ],
            "v": "<=5.2.4"
        },
        {
            "advisory": "Plone through 5.2.4 allows XSS via a full name that is mishandled during rendering of the ownership tab of a content item.",
            "cve": "CVE-2021-33508",
            "id": "pyup.io-40533",
            "more_info_path": "/vulnerabilities/CVE-2021-33508/40533",
            "specs": [
                "<=5.2.4"
            ],
            "v": "<=5.2.4"
        },
        {
            "advisory": "Zope Products.CMFCore before 2.5.1 and Products.PluggableAuthService before 2.6.2, as used in Plone through 5.2.4 and other products, allow Reflected XSS.",
            "cve": "CVE-2021-33507",
            "id": "pyup.io-40821",
            "more_info_path": "/vulnerabilities/CVE-2021-33507/40821",
            "specs": [
                "<=5.2.4"
            ],
            "v": "<=5.2.4"
        },
        {
            "advisory": "Plone through 5.2.4 allows stored XSS attacks (by a Contributor) by uploading an SVG or HTML document.",
            "cve": "CVE-2021-33512",
            "id": "pyup.io-40537",
            "more_info_path": "/vulnerabilities/CVE-2021-33512/40537",
            "specs": [
                "<=5.2.4"
            ],
            "v": "<=5.2.4"
        },
        {
            "advisory": "Plone through 5.2.4 allows remote authenticated managers to conduct SSRF attacks via an event ical URL, to read one line of a file.",
            "cve": "CVE-2021-33510",
            "id": "pyup.io-40535",
            "more_info_path": "/vulnerabilities/CVE-2021-33510/40535",
            "specs": [
                "<=5.2.4"
            ],
            "v": "<=5.2.4"
        },
        {
            "advisory": "Affected versions of the Plone package are vulnerable to Information Disclosure due to incorrect access control. The traversal module fails to properly enforce permission checks when handling crafted requests, allowing unauthorized users to bypass access restrictions on hosted content. An attacker can exploit this by sending a specially crafted request to the Plone server, enabling them to view and enumerate all files stored on the website.",
            "cve": "CVE-2024-22889",
            "id": "pyup.io-78716",
            "more_info_path": "/vulnerabilities/CVE-2024-22889/78716",
            "specs": [
                "<=6.0.9"
            ],
            "v": "<=6.0.9"
        },
        {
            "advisory": "Plone 5.2.3 is affected by CVE-2021-29002: A stored cross-site scripting (XSS) vulnerability in Plone CMS 5.2.3 exists in site-controlpanel via the \"form.widgets.site_title\" parameter.\r\nhttps://www.exploit-db.com/exploits/49668",
            "cve": "CVE-2021-29002",
            "id": "pyup.io-40094",
            "more_info_path": "/vulnerabilities/CVE-2021-29002/40094",
            "specs": [
                "==5.2.3"
            ],
            "v": "==5.2.3"
        },
        {
            "advisory": "Unspecified vulnerability in Zope 2.12.x and 2.13.x, as used in Plone 4.0.x through 4.0.9, 4.1, and 4.2 through 4.2a2, allows remote attackers to execute arbitrary commands via vectors related to the p_ class in OFS/misc_.py and the use of Python modules.",
            "cve": "CVE-2011-3587",
            "id": "pyup.io-33144",
            "more_info_path": "/vulnerabilities/CVE-2011-3587/33144",
            "specs": [
                ">4,<4.2a2"
            ],
            "v": ">4,<4.2a2"
        },
        {
            "advisory": "Plone 4.x through 4.3.11 and 5.x through 5.0.6 allow remote attackers to bypass a sandbox protection mechanism and obtain sensitive information by leveraging the Python string format method.",
            "cve": "CVE-2017-5524",
            "id": "pyup.io-35733",
            "more_info_path": "/vulnerabilities/CVE-2017-5524/35733",
            "specs": [
                ">4,<=4.3.11",
                ">5,<=5.0.6"
            ],
            "v": ">4,<=4.3.11,>5,<=5.0.6"
        },
        {
            "advisory": "By linking to a specific url in Plone 2.5-5.1rc1 with a parameter, an attacker could send you to his own website. On its own this is not so bad: the attacker could more easily link directly to his own website instead. But in combination with another attack, you could be sent to the Plone login form and login, then get redirected to the specific url, and then get a second redirect to the attacker website. (The specific url can be seen by inspecting the hotfix code, but we don't want to make it too easy for attackers by spelling it out here.)",
            "cve": "CVE-2017-1000484",
            "id": "pyup.io-35704",
            "more_info_path": "/vulnerabilities/CVE-2017-1000484/35704",
            "specs": [
                ">4,<=4.3.15",
                ">=5.0,<5.1rc1"
            ],
            "v": ">4,<=4.3.15,>=5.0,<5.1rc1"
        },
        {
            "advisory": "Plone CMS before 3 places a base64 encoded form of the username and password in the __ac cookie for all user accounts, which makes it easier for remote attackers to obtain access by sniffing the network.",
            "cve": "CVE-2008-1394",
            "id": "pyup.io-65830",
            "more_info_path": "/vulnerabilities/CVE-2008-1394/65830",
            "specs": [
                ">=0,<3.0.0"
            ],
            "v": ">=0,<3.0.0"
        },
        {
            "advisory": "Plone 2.0.5, 2.1.2, and 2.5-beta1 does not restrict access to the (1) changeMemberPortrait, (2) deletePersonalPortrait, and (3) testCurrentPassword methods, which allows remote attackers to modify portraits.",
            "cve": "CVE-2006-1711",
            "id": "pyup.io-61215",
            "more_info_path": "/vulnerabilities/CVE-2006-1711/61215",
            "specs": [
                ">=2.0.5,<=2.1.2",
                ">2.0.4,<=2.5-beta1"
            ],
            "v": ">=2.0.5,<=2.1.2,>2.0.4,<=2.5-beta1"
        },
        {
            "advisory": "Plone 4.2 and 4.0.6 include a fix for CVE-2011-1949: Cross-site scripting (XSS) vulnerability in the safe_html filter in Products.PortalTransforms in Plone 2.1 through 4.1 allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors, a different vulnerability than CVE-2010-2422.\r\nhttps://plone.org/security/hotfix/20110531/persistent-xss",
            "cve": "CVE-2011-1949",
            "id": "pyup.io-25997",
            "more_info_path": "/vulnerabilities/CVE-2011-1949/25997",
            "specs": [
                ">=2.1,<4.0.6",
                ">=4.1a0,<4.2"
            ],
            "v": ">=2.1,<4.0.6,>=4.1a0,<4.2"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4189: Multiple unspecified vulnerabilities in (1) dataitems.py, (2) get.py, and (3) traverseName.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allow remote authenticated users with administrator access to a subtree to access nodes above the subtree via unknown vectors.",
            "cve": "CVE-2013-4189",
            "id": "pyup.io-35441",
            "more_info_path": "/vulnerabilities/CVE-2013-4189/35441",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4188: traverser.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote attackers with administrator privileges to cause a denial of service (infinite loop and resource consumption) via unspecified vectors related to \"retrieving information for certain resources.\"",
            "cve": "CVE-2013-4188",
            "id": "pyup.io-35440",
            "more_info_path": "/vulnerabilities/CVE-2013-4188/35440",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4196: The object manager implementation (objectmanager.py) in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 does not properly restrict access to internal methods, which allows remote attackers to obtain sensitive information via a crafted request.",
            "cve": "CVE-2013-4196",
            "id": "pyup.io-35448",
            "more_info_path": "/vulnerabilities/CVE-2013-4196/35448",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4193: typeswidget.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 does not properly enforce the immutable setting on unspecified content edit forms, which allows remote attackers to hide fields on the forms via a crafted URL.",
            "cve": "CVE-2013-4193",
            "id": "pyup.io-35445",
            "more_info_path": "/vulnerabilities/CVE-2013-4193/35445",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4195: (1) cb_decode.py and (2) linkintegrity.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allow remote authenticated users to cause a denial of service (resource consumption) via a large zip archive, which is expanded (decompressed).",
            "cve": "CVE-2013-4199",
            "id": "pyup.io-35451",
            "more_info_path": "/vulnerabilities/CVE-2013-4199/35451",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4197: member_portrait.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote authenticated users to modify or delete portraits of other users via unspecified vectors.",
            "cve": "CVE-2013-4197",
            "id": "pyup.io-35449",
            "more_info_path": "/vulnerabilities/CVE-2013-4197/35449",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4191: zip.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 does not properly enforce access restrictions when including content in a zip archive, which allows remote attackers to obtain sensitive information by reading a generated archive.",
            "cve": "CVE-2013-4191",
            "id": "pyup.io-35443",
            "more_info_path": "/vulnerabilities/CVE-2013-4191/35443",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4192: sendto.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote authenticated users to spoof emails via unspecified vectors.",
            "cve": "CVE-2013-4192",
            "id": "pyup.io-35444",
            "more_info_path": "/vulnerabilities/CVE-2013-4192/35444",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4195: Multiple open redirect vulnerabilities in (1) marmoset_patch.py, (2) publish.py, and (3) principiaredirect.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.",
            "cve": "CVE-2013-4195",
            "id": "pyup.io-35447",
            "more_info_path": "/vulnerabilities/CVE-2013-4195/35447",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "Plone 4.1, 4.2.5 and 4.3.1 include a fix for CVE-2013-4194: The WYSIWYG component (wysiwyg.py) in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote attackers to obtain sensitive information via a crafted URL, which reveals the installation path in an error message.",
            "cve": "CVE-2013-4194",
            "id": "pyup.io-35446",
            "more_info_path": "/vulnerabilities/CVE-2013-4194/35446",
            "specs": [
                ">=2.1,<4.1",
                ">=4.2a1,<4.2.5",
                ">=4.3a1,<4.3.1"
            ],
            "v": ">=2.1,<4.1,>=4.2a1,<4.2.5,>=4.3a1,<4.3.1"
        },
        {
            "advisory": "The isURLInPortal method in the URLTool class in in_portal.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 treats URLs starting with a space as a relative URL, which allows remote attackers to bypass the allow_external_login_sites filtering property, redirect users to arbitrary web sites, and conduct phishing attacks via a space before a URL in the \"next\" parameter to acl_users/credentials_cookie_auth/require_login.",
            "cve": "CVE-2013-4200",
            "id": "pyup.io-35452",
            "more_info_path": "/vulnerabilities/CVE-2013-4200/35452",
            "specs": [
                ">=2.1,<=4.1",
                ">=4.2a1,<=4.2.5",
                ">=4.3a1,<=4.3.1"
            ],
            "v": ">=2.1,<=4.1,>=4.2a1,<=4.2.5,>=4.3a1,<=4.3.1"
        },
        {
            "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in (1) spamProtect.py, (2) pts.py, and (3) request.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.",
            "cve": "CVE-2013-4190",
            "id": "pyup.io-35442",
            "more_info_path": "/vulnerabilities/CVE-2013-4190/35442",
            "specs": [
                ">=2.1,<=4.1",
                ">=4.2a1,<=4.2.5",
                ">=4.3a1,<=4.3.1"
            ],
            "v": ">=2.1,<=4.1,>=4.2a1,<=4.2.5,>=4.3a1,<=4.3.1"
        },
        {
            "advisory": "mail_password.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote authenticated users to bypass the prohibition on password changes via the forgotten password email functionality.",
            "cve": "CVE-2013-4198",
            "id": "pyup.io-35450",
            "more_info_path": "/vulnerabilities/CVE-2013-4198/35450",
            "specs": [
                ">=2.1,<=4.1",
                ">=4.2a1,<=4.2.5",
                ">=4.3a1,<=4.3.1"
            ],
            "v": ">=2.1,<=4.1,>=4.2a1,<=4.2.5,>=4.3a1,<=4.3.1"
        },
        {
            "advisory": "Unspecified vulnerability in Plone 2.5 through 4.0, as used in Conga, luci, and possibly other products, allows remote attackers to obtain administrative access, read or create arbitrary content, and change the site skin via unknown vectors.",
            "cve": "CVE-2011-0720",
            "id": "pyup.io-33142",
            "more_info_path": "/vulnerabilities/CVE-2011-0720/33142",
            "specs": [
                ">=2.5,<4.0"
            ],
            "v": ">=2.5,<4.0"
        },
        {
            "advisory": "A member of the Plone 2.5-5.1rc1 site could set javascript in the home_page property of his profile, and have this executed when a visitor click the home page link on the author page.\r\nhttps://plone.org/security/hotfix/20171128/xss-using-the-home_page-member-property",
            "cve": "CVE-2017-1000482",
            "id": "pyup.io-35702",
            "more_info_path": "/vulnerabilities/CVE-2017-1000482/35702",
            "specs": [
                ">=2.5,<=5.1rc1"
            ],
            "v": ">=2.5,<=5.1rc1"
        },
        {
            "advisory": "When you visit a page where you need to login, Plone 2.5-5.1rc1 sends you to the login form with a 'came_from' parameter set to the previous url. After you login, you get redirected to the page you tried to view before. An attacker might try to abuse this by letting you click on a specially crafted link. You would login, and get redirected to the site of the attacker, letting you think that you are still on the original Plone site. Or some javascript of the attacker could be executed. Most of these types of attacks are already blocked by Plone, using the 'isURLInPortal' check to make sure we only redirect to a page on the same Plone site. But a few more ways of tricking Plone into accepting a malicious link were discovered, and fixed with this hotfix.\r\nhttps://plone.org/security/hotfix/20171128/open-redirection-on-login-form",
            "cve": "CVE-2017-1000481",
            "id": "pyup.io-35701",
            "more_info_path": "/vulnerabilities/CVE-2017-1000481/35701",
            "specs": [
                ">=2.5,<=5.1rc1"
            ],
            "v": ">=2.5,<=5.1rc1"
        },
        {
            "advisory": "Unspecified vulnerability in the Password Reset Tool before 0.4.1 on Plone 2.5 and 2.5.1 Release Candidate allows attackers to reset the passwords of other users, related to \"an erroneous security declaration.\"",
            "cve": "CVE-2006-4247",
            "id": "pyup.io-61216",
            "more_info_path": "/vulnerabilities/CVE-2006-4247/61216",
            "specs": [
                ">=2.5.3,<=2.5.4"
            ],
            "v": ">=2.5.3,<=2.5.4"
        },
        {
            "advisory": "Unspecified vulnerability in PlonePAS in Plone 2.5 and 2.5.1, when anonymous member registration is enabled, allows an attacker to \"masquerade as a group.\"",
            "cve": "CVE-2006-4249",
            "id": "pyup.io-61217",
            "more_info_path": "/vulnerabilities/CVE-2006-4249/61217",
            "specs": [
                ">=2.5.3,<=2.5.4"
            ],
            "v": ">=2.5.3,<=2.5.4"
        },
        {
            "advisory": "Accessing private content via str.format in through-the-web templates and scripts in Plone 2.5-5.1rc1. This improves an earlier hotfix. Since the format method was introduced in Python 2.6, this part of the hotfix is only relevant for Plone 4 and 5.\r\nhttps://plone.org/security/hotfix/20171128/sandbox-escape",
            "cve": "CVE-2017-1000483",
            "id": "pyup.io-35703",
            "more_info_path": "/vulnerabilities/CVE-2017-1000483/35703",
            "specs": [
                ">=2.5a1,<=5.1rc1"
            ],
            "v": ">=2.5a1,<=5.1rc1"
        },
        {
            "advisory": "Plone CMS 3.0.5, and probably other 3.x versions, places a base64 encoded form of the username and password in the __ac cookie for the admin account, which makes it easier for remote attackers to obtain administrative privileges by sniffing the network.",
            "cve": "CVE-2008-1393",
            "id": "pyup.io-61312",
            "more_info_path": "/vulnerabilities/CVE-2008-1393/61312",
            "specs": [
                ">=3.0.5,<=3.3.6"
            ],
            "v": ">=3.0.5,<=3.3.6"
        },
        {
            "advisory": "Plone 4.3.3 includes a fix for CVE-2013-7061: Products/CMFPlone/CatalogTool.py in Plone 3.3 through 4.3.2 allows remote administrators to bypass restrictions and obtain sensitive information via an unspecified search API.",
            "cve": "CVE-2013-7061",
            "id": "pyup.io-35491",
            "more_info_path": "/vulnerabilities/CVE-2013-7061/35491",
            "specs": [
                ">=3.3,<4.3.2"
            ],
            "v": ">=3.3,<4.3.2"
        },
        {
            "advisory": "Products/CMFPlone/FactoryTool.py in Plone 3.3 through 4.3.2 allows remote attackers to obtain the installation path via vectors related to a file object for unspecified documentation which is initialized in class scope.",
            "cve": "CVE-2013-7060",
            "id": "pyup.io-35490",
            "more_info_path": "/vulnerabilities/CVE-2013-7060/35490",
            "specs": [
                ">=3.3,<=4.3.2"
            ],
            "v": ">=3.3,<=4.3.2"
        },
        {
            "advisory": "Plone 3.3 through 5.1a1 allows remote attackers to obtain information about the ID of sensitive content via unspecified vectors.",
            "cve": "CVE-2016-4042",
            "id": "pyup.io-35667",
            "more_info_path": "/vulnerabilities/CVE-2016-4042/35667",
            "specs": [
                ">=3.3,<=5.1a1"
            ],
            "v": ">=3.3,<=5.1a1"
        },
        {
            "advisory": "Plone 3.3.0 through 3.3.6 allows remote attackers to inject headers into HTTP responses.\r\nhttps://plone.org/security/hotfix/20150910/header-injection",
            "cve": "CVE-2015-7318",
            "id": "pyup.io-35646",
            "more_info_path": "/vulnerabilities/CVE-2015-7318/35646",
            "specs": [
                ">=3.3.0,<3.3.6"
            ],
            "v": ">=3.3.0,<3.3.6"
        },
        {
            "advisory": "Kupu 3.3.0 through 3.3.6, 4.0.0 through 4.0.10, 4.1.0 through 4.1.6, and 4.2.0 through 4.2.7 allows remote authenticated users to edit Kupu settings.",
            "cve": "CVE-2015-7317",
            "id": "pyup.io-65850",
            "more_info_path": "/vulnerabilities/CVE-2015-7317/65850",
            "specs": [
                ">=3.3.0,<3.3.6",
                ">=4.0.0,<4.1.0",
                ">=4.1.0,<4.1.6",
                ">=4.2.0,<4.2.7"
            ],
            "v": ">=3.3.0,<3.3.6,>=4.0.0,<4.1.0,>=4.1.0,<4.1.6,>=4.2.0,<4.2.7"
        },
        {
            "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in Zope, as used in Plone 3.3.x through 3.3.6, 4.0.x through 4.0.9, 4.1.x through 4.1.6, 4.2.x through 4.2.7, and 4.3 through 4.3.2, allow remote attackers to inject arbitrary web script or HTML via unspecified input in the (1) browser_id_manager or (2) OFS.Image method. See: CVE-2013-7062.",
            "cve": "CVE-2013-7062",
            "id": "pyup.io-37753",
            "more_info_path": "/vulnerabilities/CVE-2013-7062/37753",
            "specs": [
                ">=3.3.0,<=3.3.6",
                ">=4.0,<=4.0.9",
                ">=4.1.0,<=4.1.6",
                ">=4.2.0,<=4.2.7",
                ">=4.3,<=4.3.2"
            ],
            "v": ">=3.3.0,<=3.3.6,>=4.0,<=4.0.9,>=4.1.0,<=4.1.6,>=4.2.0,<=4.2.7,>=4.3,<=4.3.2"
        },
        {
            "advisory": "Plone 3.3.0 through 3.3.6, 4.0.0 through 4.0.10, 4.1.0 through 4.1.6, 4.2.0 through 4.2.7, 4.3.0 through 4.3.6, and 5.0rc1 allows remote attackers to add a new member to a Plone site with registration enabled, without acknowledgment of site administrator.\r\nhttps://plone.org/security/hotfix/20150910/anonymous-is-able-to-create-plone-members",
            "cve": "CVE-2015-7315",
            "id": "pyup.io-35643",
            "more_info_path": "/vulnerabilities/CVE-2015-7315/35643",
            "specs": [
                ">=3.3a1,<3.3.6",
                ">=4.0a1,<4.0.10",
                ">=4.1a1,<4.1.6",
                ">=4.2a1,<4.2.7",
                ">=4.3a1,<4.3.6"
            ],
            "v": ">=3.3a1,<3.3.6,>=4.0a1,<4.0.10,>=4.1a1,<4.1.6,>=4.2a1,<4.2.7,>=4.3a1,<4.3.6"
        },
        {
            "advisory": "Plone 3.3.6, 4.3.11 and 5.0.6 include a fix for CVE-2016-7139: Cross-site scripting (XSS) vulnerability in an unspecified page template in Plone CMS 5.x through 5.0.6, 4.x through 4.3.11, and 3.3.x through 3.3.6 allows remote attackers to inject arbitrary web script or HTML via unknown vectors.\r\nhttps://plone.org/security/hotfix/20160830/non-persistent-xss-in-plone",
            "cve": "CVE-2016-7139",
            "id": "pyup.io-35687",
            "more_info_path": "/vulnerabilities/CVE-2016-7139/35687",
            "specs": [
                ">=3.3a1,<3.3.6",
                ">=4.0a1,<4.3.11",
                ">=5.0a1,<5.0.6"
            ],
            "v": ">=3.3a1,<3.3.6,>=4.0a1,<4.3.11,>=5.0a1,<5.0.6"
        },
        {
            "advisory": "Plone 3.3.6, 4.3.11 and 5.0.6 include a fix for CVE-2016-7137: Multiple open redirect vulnerabilities in Plone CMS 5.x through 5.0.6, 4.x through 4.3.11, and 3.3.x through 3.3.6 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the referer parameter to (1) %2b%2bgroupdashboard%2b%2bplone.dashboard1%2bgroup/%2b/portlets.Actions or (2) folder/%2b%2bcontextportlets%2b%2bplone.footerportlets/%2b /portlets.Actions or the (3) came_from parameter to /login_form.",
            "cve": "CVE-2016-7137",
            "id": "pyup.io-35685",
            "more_info_path": "/vulnerabilities/CVE-2016-7137/35685",
            "specs": [
                ">=3.3a1,<3.3.6",
                ">=4.0a1,<4.3.11",
                ">=5.0a1,<5.0.6"
            ],
            "v": ">=3.3a1,<3.3.6,>=4.0a1,<4.3.11,>=5.0a1,<5.0.6"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in the URL checking infrastructure in Plone CMS 5.x through 5.0.6, 4.x through 4.3.11, and 3.3.x through 3.3.6 allows remote attackers to inject arbitrary web script or HTML via a crafted URL.",
            "cve": "CVE-2016-7138",
            "id": "pyup.io-35686",
            "more_info_path": "/vulnerabilities/CVE-2016-7138/35686",
            "specs": [
                ">=3.3a1,<=3.3.6",
                ">=4.0a1,<=4.3.11",
                ">=5.0a1,<=5.0.6"
            ],
            "v": ">=3.3a1,<=3.3.6,>=4.0a1,<=4.3.11,>=5.0a1,<=5.0.6"
        },
        {
            "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in the ZMI page in Zope2 in Plone CMS 5.x through 5.0.6, 4.x through 4.3.11, and 3.3.x through 3.3.6 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.\r\nhttps://plone.org/security/hotfix/20160830/non-persistent-xss-in-zope2",
            "cve": "CVE-2016-7140",
            "id": "pyup.io-35688",
            "more_info_path": "/vulnerabilities/CVE-2016-7140/35688",
            "specs": [
                ">=3.3a1,<=3.3.6",
                ">=4.0a1,<=4.3.11",
                ">=5.0a1,<=5.0.6"
            ],
            "v": ">=3.3a1,<=3.3.6,>=4.0a1,<=4.3.11,>=5.0a1,<=5.0.6"
        },
        {
            "advisory": "The CMFEditions component 2.x in Plone 4.0.x through 4.0.9, 4.1, and 4.2 through 4.2a2 does not prevent the KwAsAttributes classes from being publishable, which allows remote attackers to access sub-objects via unspecified vectors, a different vulnerability than CVE-2011-3587.",
            "cve": "CVE-2011-4030",
            "id": "pyup.io-33145",
            "more_info_path": "/vulnerabilities/CVE-2011-4030/33145",
            "specs": [
                ">=4,<4.2a2"
            ],
            "v": ">=4,<4.2a2"
        },
        {
            "advisory": "Plone 4.0 through 5.1a1 does not have security declarations for Dexterity content-related WebDAV requests, which allows remote attackers to gain webdav access via unspecified vectors.",
            "cve": "CVE-2016-4041",
            "id": "pyup.io-35666",
            "more_info_path": "/vulnerabilities/CVE-2016-4041/35666",
            "specs": [
                ">=4.0,<=5.1a1"
            ],
            "v": ">=4.0,<=5.1a1"
        },
        {
            "advisory": "SQL Injection in DTML or in connection objects in Plone 4.0 through 5.2.1 allows users to perform unwanted SQL queries. (This is a problem in Zope.) See: CVE-2020-7939.",
            "cve": "CVE-2020-7939",
            "id": "pyup.io-37787",
            "more_info_path": "/vulnerabilities/CVE-2020-7939/37787",
            "specs": [
                ">=4.0,<=5.2.1"
            ],
            "v": ">=4.0,<=5.2.1"
        },
        {
            "advisory": "An open redirect on the login form (and possibly other places) in Plone 4.0 through 5.2.1 allows an attacker to craft a link to a Plone Site that, when followed, and possibly after login, will redirect to an attacker's site. See: CVE-2020-7936.",
            "cve": "CVE-2020-7936",
            "id": "pyup.io-37784",
            "more_info_path": "/vulnerabilities/CVE-2020-7936/37784",
            "specs": [
                ">=4.0,<=5.2.1"
            ],
            "v": ">=4.0,<=5.2.1"
        },
        {
            "advisory": "z3c.form in Plone CMS 5.x through 5.0.6 and 4.x through 4.3.11 allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted GET request.\r\nhttps://plone.org/security/hotfix/20160830/non-persistent-xss-in-plone-forms",
            "cve": "CVE-2016-7136",
            "id": "pyup.io-35684",
            "more_info_path": "/vulnerabilities/CVE-2016-7136/35684",
            "specs": [
                ">=4.0a1,<=4.3.11",
                ">=5.0a1,<=5.0.6"
            ],
            "v": ">=4.0a1,<=4.3.11,>=5.0a1,<=5.0.6"
        },
        {
            "advisory": "Plone 4.2 and 4.0.6 include a fix for CVE-2011-1950: plone.app.users in Plone 4.0 and 4.1 allows remote authenticated users to modify the properties of arbitrary accounts via unspecified vectors, as exploited in the wild in June 2011.\r\nhttps://plone.org/security/hotfix/20110531/privilege-escalation",
            "cve": "CVE-2011-1950",
            "id": "pyup.io-25974",
            "more_info_path": "/vulnerabilities/CVE-2011-1950/25974",
            "specs": [
                ">=4.1a0,<4.2",
                "<4.0.6"
            ],
            "v": ">=4.1a0,<4.2,<4.0.6"
        },
        {
            "advisory": "Directory traversal vulnerability in Plone CMS 5.x through 5.0.6 and 4.2.x through 4.3.11 allows remote administrators to read arbitrary files via a .. (dot dot) in the path parameter in a getFile action to Plone/++theme++barceloneta/@@plone.resourceeditor.filemanager-actions.",
            "cve": "CVE-2016-7135",
            "id": "pyup.io-35683",
            "more_info_path": "/vulnerabilities/CVE-2016-7135/35683",
            "specs": [
                ">=4.2a1,<=4.3.11",
                ">=5.0a1,<=5.0.6"
            ],
            "v": ">=4.2a1,<=4.3.11,>=5.0a1,<=5.0.6"
        },
        {
            "advisory": "Missing password strength checks on some forms in Plone 4.3 through 5.2.0 allow users to set weak passwords, leading to easier cracking. See: CVE-2020-7940.",
            "cve": "CVE-2020-7940",
            "id": "pyup.io-37788",
            "more_info_path": "/vulnerabilities/CVE-2020-7940/37788",
            "specs": [
                ">=4.3,<=5.2.0"
            ],
            "v": ">=4.3,<=5.2.0"
        },
        {
            "advisory": "A privilege escalation issue in plone.app.contenttypes in Plone 4.3 through 5.2.1 allows users to PUT (overwrite) some content without needing write permission. See: CVE-2020-7941.",
            "cve": "CVE-2020-7941",
            "id": "pyup.io-36898",
            "more_info_path": "/vulnerabilities/CVE-2020-7941/36898",
            "specs": [
                ">=4.3,<=5.2.1"
            ],
            "v": ">=4.3,<=5.2.1"
        },
        {
            "advisory": "An XSS issue in the title field in Plone 5.0 through 5.2.1 allows users with a certain privilege level to insert JavaScript that will be executed when other users access the site. See: CVE-2020-7937.",
            "cve": "CVE-2020-7937",
            "id": "pyup.io-37785",
            "more_info_path": "/vulnerabilities/CVE-2020-7937/37785",
            "specs": [
                ">=5.0,<=5.2.1"
            ],
            "v": ">=5.0,<=5.2.1"
        },
        {
            "advisory": "In Plone 5.0 through 5.2.4, Editors are vulnerable to XSS in the folder contents view, if a Contributor has created a folder with a SCRIPT tag in the description field.",
            "cve": "CVE-2021-35959",
            "id": "pyup.io-40886",
            "more_info_path": "/vulnerabilities/CVE-2021-35959/40886",
            "specs": [
                ">=5.0.0,<=5.2.4"
            ],
            "v": ">=5.0.0,<=5.2.4"
        },
        {
            "advisory": "Chameleon (five.pt) in Plone 5.0rc1 through 5.1a1 allows remote authenticated users to bypass Restricted Python by leveraging permissions to create or edit templates.",
            "cve": "CVE-2016-4043",
            "id": "pyup.io-35668",
            "more_info_path": "/vulnerabilities/CVE-2016-4043/35668",
            "specs": [
                ">=5.0rc1,<=5.1a1"
            ],
            "v": ">=5.0rc1,<=5.1a1"
        },
        {
            "advisory": "plone.restapi in Plone 5.2.0 through 5.2.1 allows users with a certain privilege level to escalate their privileges up to the highest level. See: CVE-2020-7938.",
            "cve": "CVE-2020-7938",
            "id": "pyup.io-37786",
            "more_info_path": "/vulnerabilities/CVE-2020-7938/37786",
            "specs": [
                ">=5.2.0,<=5.2.1"
            ],
            "v": ">=5.2.0,<=5.2.1"
        }
    ],
    "plone-app-content": [
        {
            "advisory": "Plone.app.content 3.3.1 includes security hotfix 20160830 for folder factories redirection.",
            "cve": "CVE-2016-7137",
            "id": "pyup.io-26000",
            "more_info_path": "/vulnerabilities/CVE-2016-7137/26000",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "Plone.app.content 3.8.1 integrate the Plone20200121 hotfix to prevent XSS in title - see: https://plone.org/security/hotfix/20200121/xss-in-the-title-field-on-plone-5-0-and-higher",
            "cve": "CVE-2020-7937",
            "id": "pyup.io-38030",
            "more_info_path": "/vulnerabilities/CVE-2020-7937/38030",
            "specs": [
                "<3.8.1"
            ],
            "v": "<3.8.1"
        },
        {
            "advisory": "Plone.app.content 4.0.0a3 includes fixes for:\r\n-Stored XSS in folder contents.\r\nhttps://plone.org/security/hotfix/20210518/stored-xss-in-folder-contents\r\n-Stored XSS from user fullname and possibly other places where \"getVocabulary\" is called. This is an alternative to the \"plone.app.users\" workaround from the \"PloneHotfix20210518\" fullname fix.\r\nhttps://plone.org/security/hotfix/20210518/stored-xss-from-user-fullname\r\nSee CVE-2021-35959.",
            "cve": "CVE-2021-35959",
            "id": "pyup.io-41256",
            "more_info_path": "/vulnerabilities/CVE-2021-35959/41256",
            "specs": [
                "<4.0.0a3"
            ],
            "v": "<4.0.0a3"
        }
    ],
    "plone-app-contentlisting": [
        {
            "advisory": "Plone.app.contentlisting 1.2.5 removes docstrings from some methods to avoid publishing them.\r\nhttps://plone.org/security/hotfix/20160419/unauthorized-disclosure-of-site-content",
            "cve": "CVE-2016-4042",
            "id": "pyup.io-47289",
            "more_info_path": "/vulnerabilities/CVE-2016-4042/47289",
            "specs": [
                "<1.2.5"
            ],
            "v": "<1.2.5"
        }
    ],
    "plone-app-contentmenu": [
        {
            "advisory": "Plone.app.contentmenu  1.1.7 escapes the title of the defaultpage in the DisplayMenu. This fixes a potential XSS vulnerability.\r\nhttps://github.com/plone/plone.app.contentmenu/commit/6d7d5d51c12c82fc0eeaded0841fc57d2258e9af",
            "cve": "PVE-2021-26001",
            "id": "pyup.io-26001",
            "more_info_path": "/vulnerabilities/PVE-2021-26001/26001",
            "specs": [
                "<1.1.7"
            ],
            "v": "<1.1.7"
        },
        {
            "advisory": "Plone-app-contentmenu  1.1.7 escapes the title of the defaultpage in the DisplayMenu. This fixes a potential XSS vulnerability.\r\nhttps://github.com/plone/plone.app.contentmenu/commit/6d7d5d51c12c82fc0eeaded0841fc57d2258e9af",
            "cve": "PVE-2021-36047",
            "id": "pyup.io-36047",
            "more_info_path": "/vulnerabilities/PVE-2021-36047/36047",
            "specs": [
                "<1.1.7"
            ],
            "v": "<1.1.7"
        },
        {
            "advisory": "Plone.app.contentmenu 2.1.1 adds csrf protection to generated menu items.\r\nhttps://github.com/plone/plone.app.contentmenu/commit/623c61531243992c71a59e5280e08f32673c8cc7",
            "cve": "PVE-2022-45168",
            "id": "pyup.io-45168",
            "more_info_path": "/vulnerabilities/PVE-2022-45168/45168",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        }
    ],
    "plone-app-contenttypes": [
        {
            "advisory": "Plone.app.contenttypes 1.2.15 fixes a possible cross site scripting (XSS) attack in lead image caption.\r\nhttps://github.com/plone/plone.app.contenttypes/commit/16f2c31cada65f7c969e4d314c70d39d1db01f17",
            "cve": "PVE-2021-26002",
            "id": "pyup.io-26002",
            "more_info_path": "/vulnerabilities/PVE-2021-26002/26002",
            "specs": [
                "<1.2.15"
            ],
            "v": "<1.2.15"
        },
        {
            "advisory": "Plone.app.contenttypes 1.2.15 fixes a possible cross site scripting (XSS) attack in lead image caption.\r\nhttps://github.com/plone/plone.app.contenttypes/commit/16f2c31cada65f7c969e4d314c70d39d1db01f17",
            "cve": "PVE-2021-35870",
            "id": "pyup.io-35870",
            "more_info_path": "/vulnerabilities/PVE-2021-35870/35870",
            "specs": [
                "<1.2.15"
            ],
            "v": "<1.2.15"
        },
        {
            "advisory": "Plone-app-contenttypes version 2.1.6 includes a fix for CVE-2020-7941: A privilege escalation issue in plone.app.contenttypes in Plone 4.3 through 5.2.1 allows users to PUT (overwrite) some content without needing write permission.",
            "cve": "CVE-2020-7941",
            "id": "pyup.io-41880",
            "more_info_path": "/vulnerabilities/CVE-2020-7941/41880",
            "specs": [
                "<2.1.6"
            ],
            "v": "<2.1.6"
        },
        {
            "advisory": "Plone.app.contenttypes 3.0.0a9 and 2.2.3 include a fix for CVE-2022-23599: Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) and URL Redirection to Untrusted Site (Open Redirect).\r\nhttps://github.com/plone/plone.app.contenttypes/security/advisories/GHSA-f7qw-5fgj-247x",
            "cve": "CVE-2022-23599",
            "id": "pyup.io-44713",
            "more_info_path": "/vulnerabilities/CVE-2022-23599/44713",
            "specs": [
                "<2.2.3",
                ">=3.0.0a1,<3.0.0a9"
            ],
            "v": "<2.2.3,>=3.0.0a1,<3.0.0a9"
        }
    ],
    "plone-app-dexterity": [
        {
            "advisory": "The modeleditor in plone.app.dexterity 2.6.8 no longer resolves entities, and it removes processing instructions.",
            "cve": "PVE-2021-39143",
            "id": "pyup.io-39143",
            "more_info_path": "/vulnerabilities/PVE-2021-39143/39143",
            "specs": [
                "<2.6.8"
            ],
            "v": "<2.6.8"
        }
    ],
    "plone-app-discussion": [
        {
            "advisory": "plone-app-discussion 2.4.14 fixes a possible cross site scripting (XSS) attack on moderate comments page.",
            "cve": "PVE-2021-35864",
            "id": "pyup.io-35864",
            "more_info_path": "/vulnerabilities/PVE-2021-35864/35864",
            "specs": [
                "<2.4.14"
            ],
            "v": "<2.4.14"
        },
        {
            "advisory": "Plone.app.discussion 2.4.14 fixes a possible cross site scripting (XSS) attack on moderate comments page.\r\nhttps://github.com/plone/plone.app.discussion/commit/e1dbaef82a801c58576057564ab3689dba983c15",
            "cve": "PVE-2021-26003",
            "id": "pyup.io-26003",
            "more_info_path": "/vulnerabilities/PVE-2021-26003/26003",
            "specs": [
                "<2.4.14"
            ],
            "v": "<2.4.14"
        },
        {
            "advisory": "Plone.app.discussion 2.4.18 includes security hotfix 20160830 for redirects.",
            "cve": "CVE-2016-7137",
            "id": "pyup.io-26004",
            "more_info_path": "/vulnerabilities/CVE-2016-7137/26004",
            "specs": [
                "<2.4.18"
            ],
            "v": "<2.4.18"
        }
    ],
    "plone-app-event": [
        {
            "advisory": "Plone.app.event 3.0 fixes a possible cross site scripting (XSS) attack in location field.\r\nhttps://github.com/plone/plone.app.event/pull/233",
            "cve": "PVE-2021-26005",
            "id": "pyup.io-26005",
            "more_info_path": "/vulnerabilities/PVE-2021-26005/26005",
            "specs": [
                "<3.0"
            ],
            "v": "<3.0"
        },
        {
            "advisory": "Plone.app.event 3.0 fixes a possible cross site scripting (XSS) attack in location field.\r\nhttps://github.com/plone/plone.app.event/pull/233",
            "cve": "PVE-2021-35923",
            "id": "pyup.io-35923",
            "more_info_path": "/vulnerabilities/PVE-2021-35923/35923",
            "specs": [
                "<3.0"
            ],
            "v": "<3.0"
        },
        {
            "advisory": "Plone.app.event 3.2.10 gives a validation error in the ical importer when a 'file://' URL is used (this could be a line of attack for a hacker).",
            "cve": "PVE-2021-39140",
            "id": "pyup.io-39140",
            "more_info_path": "/vulnerabilities/PVE-2021-39140/39140",
            "specs": [
                "<3.2.10"
            ],
            "v": "<3.2.10"
        },
        {
            "advisory": "Plone.app.event 4.0.0a4 includes a fix for a server-side-request-forgery vulnerability. Now, \"file:\" protocol is not allowed in iCal url. Previously, only \"file://\" was disallowed, but this left room for relative paths.\r\nhttps://plone.org/security/hotfix/20210518/server-side-request-forgery-via-event-ical-url\r\nhttps://github.com/plone/plone.app.event/commit/70bf81822240d2808e6e9d3538586f78f4cd91bf",
            "cve": "CVE-2021-33510",
            "id": "pyup.io-41254",
            "more_info_path": "/vulnerabilities/CVE-2021-33510/41254",
            "specs": [
                "<4.0.0a4"
            ],
            "v": "<4.0.0a4"
        }
    ],
    "plone-app-layout": [
        {
            "advisory": "Plone-app-layout version 2.5.1 adds CSRF tokens automatically for contentview urls.",
            "cve": "PVE-2021-41878",
            "id": "pyup.io-41878",
            "more_info_path": "/vulnerabilities/PVE-2021-41878/41878",
            "specs": [
                "<2.5.1"
            ],
            "v": "<2.5.1"
        },
        {
            "advisory": "Plone-app-layout version 3.4.1 integrates a fix for CVE-2020-7937, which affects the core package Plone.\r\nhttps://plone.org/security/hotfix/20200121/xss-in-the-title-field-on-plone-5-0-and-higher",
            "cve": "CVE-2020-7937",
            "id": "pyup.io-41877",
            "more_info_path": "/vulnerabilities/CVE-2020-7937/41877",
            "specs": [
                "<3.4.1"
            ],
            "v": "<3.4.1"
        },
        {
            "advisory": "Plone.app.layout 4.0.0a2 includes fixes for information-exposure vulnerabilities:\r\n-Show document_byline to public if \"display_publication_date_in_byline\" in site controlpanel is active\r\n-Only show author if \"allow_anon_views_about\" in security controlpanel is active\r\n-Show \"modification_date\" if not published or \"modification_date\" is greater that \"effective_date\"",
            "cve": "PVE-2021-41704",
            "id": "pyup.io-41704",
            "more_info_path": "/vulnerabilities/PVE-2021-41704/41704",
            "specs": [
                "<4.0.0a2"
            ],
            "v": "<4.0.0a2"
        }
    ],
    "plone-app-linkintegrity": [
        {
            "advisory": "Plone-app-linkintegrity 1.0.2 includes a fix for CVE-2007-5741: Plone 2.5 through 2.5.4 and 3.0 through 3.0.2 allows remote attackers to execute arbitrary Python code via network data containing pickled objects for the (1) statusmessages or (2) linkintegrity module, which the module unpickles and executes.\r\nhttps://github.com/plone/plone.app.linkintegrity/commit/4be49548c4f1046a8204030f26a603c29f38d9dd",
            "cve": "CVE-2007-5741",
            "id": "pyup.io-36046",
            "more_info_path": "/vulnerabilities/CVE-2007-5741/36046",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "plone-app-portlets": [
        {
            "advisory": "Plone.app.portlets 5.0.0a2 and 4.4.7 include a security fix: Blind SSRF via feedparser accessing an internal URL.\r\nhttps://plone.org/security/hotfix/20210518/blind-ssrf-via-feedparser-accessing-an-internal-url\r\nhttps://github.com/plone/plone.app.portlets/pull/150",
            "cve": "PVE-2023-57538",
            "id": "pyup.io-57538",
            "more_info_path": "/vulnerabilities/PVE-2023-57538/57538",
            "specs": [
                "==5.0.0a1",
                "<4.4.7"
            ],
            "v": "==5.0.0a1,<4.4.7"
        }
    ],
    "plone-app-theming": [
        {
            "advisory": "Plone-app-theming 4.1.6 doesn't resolves entities and removes processing instructions to avoid XXE attacks.",
            "cve": "PVE-2021-41938",
            "id": "pyup.io-41938",
            "more_info_path": "/vulnerabilities/PVE-2021-41938/41938",
            "specs": [
                "<4.1.6"
            ],
            "v": "<4.1.6"
        },
        {
            "advisory": "Plone.app.theming 5.0.0a1 and 4.1.6 include a fix for CVE-2021-33511: Plone though 5.2.4 allows SSRF via the lxml parser. This affects Diazo themes, Dexterity TTW schemas, and modeleditors in plone.app.theming, plone.app.dexterity, and plone.supermodel.\r\nhttps://plone.org/security/hotfix/20210518/server-side-request-forgery-via-lxml-parser",
            "cve": "CVE-2021-33511",
            "id": "pyup.io-41937",
            "more_info_path": "/vulnerabilities/CVE-2021-33511/41937",
            "specs": [
                "<4.1.6"
            ],
            "v": "<4.1.6"
        }
    ],
    "plone-app-users": [
        {
            "advisory": "Plone-app-users before 1.0.5 does not check for permission when editing other users' profiles. This fixes http://dev.plone.org/plone/ticket/11842 and http://plone.org/products/plone/security/advisories/CVE-2011-1950.",
            "cve": "CVE-2011-1950",
            "id": "pyup.io-36096",
            "more_info_path": "/vulnerabilities/CVE-2011-1950/36096",
            "specs": [
                "<1.0.5"
            ],
            "v": "<1.0.5"
        }
    ],
    "plone-app-workflow": [
        {
            "advisory": "Plone.app.workflow 1.1.0 protects the \"sharing\" form against CSRF attacks.\r\nhttps://github.com/plone/plone.app.workflow/commit/c2e300e52bb7b3ffad03c09afb42f441d58eec15",
            "cve": "PVE-2022-52116",
            "id": "pyup.io-52116",
            "more_info_path": "/vulnerabilities/PVE-2022-52116/52116",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Plone.app.workflow 1.1.0 protects the \"sharing\" form against CSRF attacks.\r\nhttps://github.com/plone/plone.app.workflow/commit/c2e300e52bb7b3ffad03c09afb42f441d58eec15",
            "cve": "PVE-2017-47636",
            "id": "pyup.io-47636",
            "more_info_path": "/vulnerabilities/PVE-2017-47636/47636",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "plone-app-z3cform": [
        {
            "advisory": "Plone-app-z3cform version 0.5.4 makes LookupErrors no longer visible to improve security.",
            "cve": "PVE-2021-42026",
            "id": "pyup.io-42026",
            "more_info_path": "/vulnerabilities/PVE-2021-42026/42026",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        }
    ],
    "plone-dexterity": [
        {
            "advisory": "plone.dexterity 2.3.0 fixes a security issue. Attribute access to schema fields can be protected. This worked for direct schemas, but was not implemented for permissions coming from behaviors.",
            "cve": "PVE-2021-26007",
            "id": "pyup.io-26007",
            "more_info_path": "/vulnerabilities/PVE-2021-26007/26007",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        }
    ],
    "plone-memoize": [
        {
            "advisory": "Plone.memoize 1.0.3 no longer uses hash() when making cache keys. This is to avoid cache collisions, and to avoid a potential security problem where an attacker could manually craft collisions. Also, the use of hash() is no longer recommended in tests.\r\nhttps://github.com/plone/plone.memoize/commit/66648a2e9ff2932e3a1bc4b5da88160602653531",
            "cve": "PVE-2021-37107",
            "id": "pyup.io-37107",
            "more_info_path": "/vulnerabilities/PVE-2021-37107/37107",
            "specs": [
                "<1.0.3"
            ],
            "v": "<1.0.3"
        }
    ],
    "plone-mockup": [
        {
            "advisory": "Plone.mockup before 2.1.3 is vulnerable to a XSS attack in structure and relateditem pattern.\r\nhttps://github.com/plone/mockup/pull/627",
            "cve": "PVE-2021-26009",
            "id": "pyup.io-26009",
            "more_info_path": "/vulnerabilities/PVE-2021-26009/26009",
            "specs": [
                "<2.1.3"
            ],
            "v": "<2.1.3"
        }
    ],
    "plone-namedfile": [
        {
            "advisory": "Plone.namedfile 5.5.0 prevents stored XSS from file upload (svg, html) by implementing an allowlist of trusted mimetypes.\r\nhttps://github.com/plone/plone.namedfile/commit/37b9b7f29b0f804df622db9502abae28f3eccf38\r\nhttps://plone.org/security/hotfix/20210518/reflected-xss-in-various-spots",
            "cve": "CVE-2021-33507",
            "id": "pyup.io-43737",
            "more_info_path": "/vulnerabilities/CVE-2021-33507/43737",
            "specs": [
                "<5.5.0"
            ],
            "v": "<5.5.0"
        }
    ],
    "plone-openid": [
        {
            "advisory": "Plone.openid 2.0.2 uses system random when available to fix CVE-2012-5508.",
            "cve": "CVE-2012-5508",
            "id": "pyup.io-26010",
            "more_info_path": "/vulnerabilities/CVE-2012-5508/26010",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        }
    ],
    "plone-portlet-collection": [
        {
            "advisory": "Plone.portlet.collection 2.0.4 fixes a flaw that allowed users without view permissions for the collection to see the Portlet.\r\nhttps://github.com/plone/plone.portlet.collection/commit/acaef557bdd904aaccc9da71bd3febc2c28c5d19",
            "cve": "PVE-2017-47716",
            "id": "pyup.io-47716",
            "more_info_path": "/vulnerabilities/PVE-2017-47716/47716",
            "specs": [
                "<2.0.4"
            ],
            "v": "<2.0.4"
        }
    ],
    "plone-portlet-static": [
        {
            "advisory": "Plone.portlet.static 1.2 starts to ensure that text output is passed through the 'safe-html' transform to protect against malicious text.",
            "cve": "PVE-2021-40232",
            "id": "pyup.io-40232",
            "more_info_path": "/vulnerabilities/PVE-2021-40232/40232",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Plone-portlet-static version 1.2 ensures that text output is passed through the safe-html transform to protect against malicious input.",
            "cve": "PVE-2021-41932",
            "id": "pyup.io-41932",
            "more_info_path": "/vulnerabilities/PVE-2021-41932/41932",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        }
    ],
    "plone-recipe-varnish": [
        {
            "advisory": "Plone.recipe.varnish 6.0.0b1 sets as default version Varnish Cache 6.0.4. It includes several security fixes compared to Varnish Cache 5.x versions.\r\nhttps://github.com/collective/plone.recipe.varnish/pull/75/files",
            "cve": "CVE-2017-8807",
            "id": "pyup.io-44979",
            "more_info_path": "/vulnerabilities/CVE-2017-8807/44979",
            "specs": [
                "<6.0.0b1"
            ],
            "v": "<6.0.0b1"
        },
        {
            "advisory": "Plone.recipe.varnish 6.0.0b1 sets as default version Varnish Cache 6.0.4. It includes several security fixes compared to Varnish Cache 5.x versions.\r\nhttps://github.com/collective/plone.recipe.varnish/pull/75/files",
            "cve": "CVE-2019-15892",
            "id": "pyup.io-37942",
            "more_info_path": "/vulnerabilities/CVE-2019-15892/37942",
            "specs": [
                "<6.0.0b1"
            ],
            "v": "<6.0.0b1"
        }
    ],
    "plone-restapi": [
        {
            "advisory": "Some versions of Plone suffer from a stored cross-site scripting (XSS) vulnerability specifically associated with the upload and use of SVG images as user portraits. This flaw doesn't affect pages using SVG images within image tags; the vulnerability only manifests when an attacker uploads a malicious SVG file as a user portrait and then persuades another user to click a link directing to this portrait. While a remedy will be included in a forthcoming update for `plone.restapi`, which applies to certain versions of Plone, for earlier versions not supporting a specific endpoint, there's a related fix linking to a different component. To mitigate the risk temporarily, one option includes removing the portrait field from user profiles and deleting any existing portraits in the database, although this approach may be considered somewhat extreme.",
            "cve": "PVE-2024-69616",
            "id": "pyup.io-69616",
            "more_info_path": "/vulnerabilities/PVE-2024-69616/69616",
            "specs": [
                ">=8.0.0,<8.43.3"
            ],
            "v": ">=8.0.0,<8.43.3"
        }
    ],
    "plone-session": [
        {
            "advisory": "Plone.session 2.1 protects the setupSession call with the ManageUsers permission to fix a possible privilege escalation.\r\nhttps://github.com/plone/plone.session/commit/66b97c7402c10a8ab2131b69b7ba85ab7b4f9592",
            "cve": "PVE-2022-45180",
            "id": "pyup.io-45180",
            "more_info_path": "/vulnerabilities/PVE-2022-45180/45180",
            "specs": [
                "<2.1"
            ],
            "v": "<2.1"
        },
        {
            "advisory": "Plone.session 3.6.2 hardens the default timeout of session. Session timeout is now the same as in mod_auth_tkt: 2h. This follows the recommendation of the German BSI (federal office for security in the information technology).\r\nhttps://github.com/plone/plone.session/commit/0e681e60176633034fffa2418ab130c8b338eb3b",
            "cve": "PVE-2021-38207",
            "id": "pyup.io-38207",
            "more_info_path": "/vulnerabilities/PVE-2021-38207/38207",
            "specs": [
                "<3.6.2"
            ],
            "v": "<3.6.2"
        }
    ],
    "plone-supermodel": [
        {
            "advisory": "Plone.supermodel 1.6.3 no longer resolves entities in the xml parser. It also removes processing instructions. These are both security enhancements.",
            "cve": "PVE-2021-39141",
            "id": "pyup.io-39141",
            "more_info_path": "/vulnerabilities/PVE-2021-39141/39141",
            "specs": [
                "<1.6.3"
            ],
            "v": "<1.6.3"
        },
        {
            "advisory": "Plone-supermodel 1.6.3 doesn't resolves entities in the xml parser and removes processing instructions to increase security.",
            "cve": "PVE-2021-41933",
            "id": "pyup.io-41933",
            "more_info_path": "/vulnerabilities/PVE-2021-41933/41933",
            "specs": [
                "<1.6.3"
            ],
            "v": "<1.6.3"
        }
    ],
    "plone-z3cform": [
        {
            "advisory": "Plone.z3cform 0.5.9 fixes a security problem in the \"widget\" namespace.\r\nhttps://github.com/plone/plone.z3cform/commit/a4eadb65b1db0b91bbeea808fed0da8fde069f05",
            "cve": "PVE-2021-37035",
            "id": "pyup.io-37035",
            "more_info_path": "/vulnerabilities/PVE-2021-37035/37035",
            "specs": [
                "<0.5.9"
            ],
            "v": "<0.5.9"
        }
    ],
    "plone.app.discussion": [
        {
            "advisory": "Affected versions of this package are vulnerable to an authentication bypass due to improper user identity verification. The vulnerability exists because the system allows anonymous users to post comments using the usernames of registered users without proper authentication checks. An attacker can exploit this vulnerability by impersonating a registered user, potentially leading to unauthorized actions being attributed to the legitimate user.",
            "cve": "PVE-2026-84296",
            "id": "pyup.io-84296",
            "more_info_path": "/vulnerabilities/PVE-2026-84296/84296",
            "specs": [
                "<5.2.0"
            ],
            "v": "<5.2.0"
        }
    ],
    "plone.app.portlets": [
        {
            "advisory": "Plone.app.portlets 4.2.1, 3.1.5 and 2.5.6 include a fix for CVE-2016-7137: Open Redirection in Plone.\r\nhttps://github.com/plone/plone.app.portlets/pull/87",
            "cve": "CVE-2016-7137",
            "id": "pyup.io-57539",
            "more_info_path": "/vulnerabilities/CVE-2016-7137/57539",
            "specs": [
                ">=4.0.0,<4.2.1",
                ">=3.0,<3.1.5",
                "<2.5.6"
            ],
            "v": ">=4.0.0,<4.2.1,>=3.0,<3.1.5,<2.5.6"
        }
    ],
    "plone.namedfile": [
        {
            "advisory": "Plone.namedfile 5.6.1, 6.0.3, 6.1.3 and 6.2.1 include a fix for CVE-2023-41048: Stored Cross Site Scripting with SVG images.\r\nhttps://github.com/plone/plone.namedfile/security/advisories/GHSA-jj7c-jrv4-c65x",
            "cve": "CVE-2023-41048",
            "id": "pyup.io-61345",
            "more_info_path": "/vulnerabilities/CVE-2023-41048/61345",
            "specs": [
                "<5.6.1",
                ">=6.0.0a1,<6.0.3",
                ">=6.1.0a1,<6.1.3",
                ">=6.2.0a1,<6.2.1"
            ],
            "v": "<5.6.1,>=6.0.0a1,<6.0.3,>=6.1.0a1,<6.1.3,>=6.2.0a1,<6.2.1"
        }
    ],
    "plone.rest": [
        {
            "advisory": "Plone.rest allows users to use HTTP verbs such as GET, POST, PUT, DELETE, etc. in Plone. Starting in the 2.x branch and prior to versions 2.0.1 and 3.0.1, when the `++api++` traverser is accidentally used multiple times in a url, handling it takes increasingly longer, making the server less responsive. Patches are available in `plone.rest` 2.0.1 and 3.0.1.  Series 1.x is not affected. As a workaround, one may redirect `/++api++/++api++` to `/++api++` in one's frontend web server (nginx, Apache).",
            "cve": "CVE-2023-42457",
            "id": "pyup.io-61347",
            "more_info_path": "/vulnerabilities/CVE-2023-42457/61347",
            "specs": [
                ">=2.0.0a1,<2.0.1",
                "==3.0.0"
            ],
            "v": ">=2.0.0a1,<2.0.1,==3.0.0"
        }
    ],
    "plone.restapi": [
        {
            "advisory": "Plone.restapi 8.43.3 includes a fix for CVE-2023-42458: Stored Cross Site Scripting with SVG image in user portrait.\r\nhttps://github.com/plone/plone.restapi/security/advisories/GHSA-hc5c-r8m5-2gfh",
            "cve": "CVE-2023-42458",
            "id": "pyup.io-61397",
            "more_info_path": "/vulnerabilities/CVE-2023-42458/61397",
            "specs": [
                "<8.43.3"
            ],
            "v": "<8.43.3"
        }
    ],
    "plone.staticresources": [
        {
            "advisory": "Plone.staticresources 1.3.0 adds jQuery workaround for XSS vulnerability.\r\nhttps://github.com/plone/plone.staticresources/commit/bcd286de96d1f1431299f603ef273189a58db379",
            "cve": "CVE-2015-9251",
            "id": "pyup.io-49639",
            "more_info_path": "/vulnerabilities/CVE-2015-9251/49639",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "plotai": [
        {
            "advisory": "A vulnerability that could result in Remote Code Execution (RCE) has been found in PlotAI. Lack of validation of LLM-generated output allows aan ttacker to execute arbitrary Python code. PlotAI commented out vthe ulnerable line, further usage of the software requires uncommenting it and thus accepting the risk.",
            "cve": "CVE-2025-1497",
            "id": "pyup.io-76317",
            "more_info_path": "/vulnerabilities/CVE-2025-1497/76317",
            "specs": [
                "<0.0.7"
            ],
            "v": "<0.0.7"
        }
    ],
    "plotly": [
        {
            "advisory": "Plotly 1.12.6 includes Plotly.js v1.16.2, which fixes a potential XSS vulnerability in 'text' fields.\r\nhttps://github.com/plotly/plotly.js/pull/736\r\nhttps://plotly.com/chart-studio-help/security-advisories/2016-08-08-plotlyjs-xss-advisory/",
            "cve": "CVE-2017-1000006",
            "id": "pyup.io-37053",
            "more_info_path": "/vulnerabilities/CVE-2017-1000006/37053",
            "specs": [
                "<1.12.6"
            ],
            "v": "<1.12.6"
        },
        {
            "advisory": "Plotly 1.24.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/plotly/plotly.py/issues/1388",
            "cve": "PVE-2023-60359",
            "id": "pyup.io-60359",
            "more_info_path": "/vulnerabilities/PVE-2023-60359/60359",
            "specs": [
                "<1.24.0"
            ],
            "v": "<1.24.0"
        },
        {
            "advisory": "Plotly 1.9.6 includes plotly.js version 1.5.2, which contains security fixes.",
            "cve": "CVE-2015-9242",
            "id": "pyup.io-38545",
            "more_info_path": "/vulnerabilities/CVE-2015-9242/38545",
            "specs": [
                "<1.9.6"
            ],
            "v": "<1.9.6"
        },
        {
            "advisory": "Plotly 1.9.6 includes plotly.js version 1.5.2, which contains security fixes.",
            "cve": "CVE-2015-8858",
            "id": "pyup.io-45779",
            "more_info_path": "/vulnerabilities/CVE-2015-8858/45779",
            "specs": [
                "<1.9.6"
            ],
            "v": "<1.9.6"
        },
        {
            "advisory": "Plotly 2.0.7 includes Plotly.js 1.25.0, which contains a fix for an XSS vulnerability in a trace name on hover.\r\nhttps://github.com/plotly/plotly.js/pull/1307",
            "cve": "PVE-2021-37052",
            "id": "pyup.io-37052",
            "more_info_path": "/vulnerabilities/PVE-2021-37052/37052",
            "specs": [
                "<2.0.7"
            ],
            "v": "<2.0.7"
        },
        {
            "advisory": "Plotly 4.8.2 includes plotly.js version 1.54.5, which contains a security fix of a transitive dependency (ecstatic).",
            "cve": "CVE-2019-10775",
            "id": "pyup.io-38454",
            "more_info_path": "/vulnerabilities/CVE-2019-10775/38454",
            "specs": [
                "<4.8.2"
            ],
            "v": "<4.8.2"
        },
        {
            "advisory": "Plotly 4.9.0 builds Javascript extensions using Node 12 with an updated 'package-lock.json' that has many fewer security warnings.",
            "cve": "CVE-2020-7598",
            "id": "pyup.io-47987",
            "more_info_path": "/vulnerabilities/CVE-2020-7598/47987",
            "specs": [
                "<4.9.0"
            ],
            "v": "<4.9.0"
        }
    ],
    "plugwise": [
        {
            "advisory": "Plugwise 0.8.2 improves the security by switching from lxml to defusedxml.",
            "cve": "PVE-2021-39026",
            "id": "pyup.io-39026",
            "more_info_path": "/vulnerabilities/PVE-2021-39026/39026",
            "specs": [
                "<0.8.2"
            ],
            "v": "<0.8.2"
        }
    ],
    "plumi-app": [
        {
            "advisory": "Plumi.app 4.2.1 updates its dependency 'plone' to v4.0.7 to include security fixes.",
            "cve": "CVE-2011-1948",
            "id": "pyup.io-26012",
            "more_info_path": "/vulnerabilities/CVE-2011-1948/26012",
            "specs": [
                "<4.2.1"
            ],
            "v": "<4.2.1"
        },
        {
            "advisory": "Plumi.app 4.2.1 updates its dependency 'plone' to v4.0.7 to include security fixes.",
            "cve": "CVE-2011-1950",
            "id": "pyup.io-44593",
            "more_info_path": "/vulnerabilities/CVE-2011-1950/44593",
            "specs": [
                "<4.2.1"
            ],
            "v": "<4.2.1"
        },
        {
            "advisory": "Plumi.app 4.2.1 updates its dependency 'plone' to v4.0.7 to include security fixes.",
            "cve": "CVE-2011-1949",
            "id": "pyup.io-44594",
            "more_info_path": "/vulnerabilities/CVE-2011-1949/44594",
            "specs": [
                "<4.2.1"
            ],
            "v": "<4.2.1"
        },
        {
            "advisory": "Plumi.app 4.2.2 patches a serious security vulnerability affecting its dependency 'Zope'.\r\nhttps://plone.org/security/hotfix/20110622/privilege-escalation",
            "cve": "CVE-2011-2528",
            "id": "pyup.io-26013",
            "more_info_path": "/vulnerabilities/CVE-2011-2528/26013",
            "specs": [
                "<4.2.2"
            ],
            "v": "<4.2.2"
        }
    ],
    "plumpy": [
        {
            "advisory": "Plumpy 0.20.0 updates its dependency \"Pyyaml\" to a secure version (>=5.4).",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-41835",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/41835",
            "specs": [
                "<0.20.0"
            ],
            "v": "<0.20.0"
        }
    ],
    "plusminus": [
        {
            "advisory": "Plusminus 0.3.0 has been hardened against some possible attacks, using deep expression nesting or formula references.",
            "cve": "PVE-2021-38323",
            "id": "pyup.io-38323",
            "more_info_path": "/vulnerabilities/PVE-2021-38323/38323",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "pm4py": [
        {
            "advisory": "Pm4py 2.2.13.1 updates its dependency 'pillow' to v8.3.2 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-42161",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/42161",
            "specs": [
                "<2.2.13.1"
            ],
            "v": "<2.2.13.1"
        },
        {
            "advisory": "Pm4py 2.2.17.1 includes a fix for a command injection vulnerability in Data Petri Nets.\r\nhttps://github.com/pm4py/pm4py-core/commit/512c071e4990cb2f2fda523e223007256c0ec62e",
            "cve": "PVE-2021-43434",
            "id": "pyup.io-43434",
            "more_info_path": "/vulnerabilities/PVE-2021-43434/43434",
            "specs": [
                "<2.2.17.1"
            ],
            "v": "<2.2.17.1"
        },
        {
            "advisory": "Pm4py 2.2.19.1 updates its dependency 'numpy' to v1.22.2 to include security fixes.",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-44944",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/44944",
            "specs": [
                "<2.2.19.1"
            ],
            "v": "<2.2.19.1"
        },
        {
            "advisory": "Pm4py 2.2.19.1 updates its dependency 'numpy' to v1.22.2 to include security fixes.",
            "cve": "CVE-2021-41496",
            "id": "pyup.io-44945",
            "more_info_path": "/vulnerabilities/CVE-2021-41496/44945",
            "specs": [
                "<2.2.19.1"
            ],
            "v": "<2.2.19.1"
        },
        {
            "advisory": "Pm4py 2.2.19.1 updates its dependency 'numpy' to v1.22.2 to include security fixes.",
            "cve": "CVE-2021-41495",
            "id": "pyup.io-44946",
            "more_info_path": "/vulnerabilities/CVE-2021-41495/44946",
            "specs": [
                "<2.2.19.1"
            ],
            "v": "<2.2.19.1"
        },
        {
            "advisory": "Pm4py 2.2.4 updates its dependency 'lxml' to v4.6.3 to include a security fix.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-42160",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/42160",
            "specs": [
                "<2.2.4"
            ],
            "v": "<2.2.4"
        }
    ],
    "pmpo": [
        {
            "advisory": "Pmpo is a malicious package, typosquatting.\r\nhttps://blog.sonatype.com/trojanized-pypi-package-imitates-a-popular-python-server-library",
            "cve": "PVE-2022-47820",
            "id": "pyup.io-47820",
            "more_info_path": "/vulnerabilities/PVE-2022-47820/47820",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "pmr2-oauth": [
        {
            "advisory": "pmr2.oauth before 0.4.2 is vulnerable to CSRF attacks.",
            "cve": "PVE-2021-26014",
            "id": "pyup.io-26014",
            "more_info_path": "/vulnerabilities/PVE-2021-26014/26014",
            "specs": [
                "<0.4.2"
            ],
            "v": "<0.4.2"
        }
    ],
    "pmultiqc": [
        {
            "advisory": "Affected versions of the pmultiqc package are vulnerable to Command Injection due to insufficient validation of the input_type parameter. The run_pmultiqc_with_progress() function did not employ whitelist validation for the input_type parameter, allowing arbitrary values to be passed to command execution.",
            "cve": "PVE-2026-84721",
            "id": "pyup.io-84721",
            "more_info_path": "/vulnerabilities/PVE-2026-84721/84721",
            "specs": [
                "<0.0.40"
            ],
            "v": "<0.0.40"
        },
        {
            "advisory": "Affected versions of the pmultiqc package are vulnerable to Path Traversal due to insufficient validation of filenames and archive member paths. The serve_html_report() function and archive extraction functions (extract_zip(), extract_tar()) failed to validate that filenames do not contain directory traversal sequences such as .., /, or \\, allowing attackers to construct paths that escape the intended directory.",
            "cve": "PVE-2026-84843",
            "id": "pyup.io-84843",
            "more_info_path": "/vulnerabilities/PVE-2026-84843/84843",
            "specs": [
                "<0.0.40"
            ],
            "v": "<0.0.40"
        }
    ],
    "pocketsnack": [
        {
            "advisory": "Pocketsnack 3.2.1 updates its dependency 'urllib3' to v1.26.5 to include security fixes.",
            "cve": "CVE-2021-28363",
            "id": "pyup.io-51484",
            "more_info_path": "/vulnerabilities/CVE-2021-28363/51484",
            "specs": [
                "<3.2.1"
            ],
            "v": "<3.2.1"
        },
        {
            "advisory": "Pocketsnack 3.2.1 updates its dependency 'urllib3' to v1.26.5 to include security fixes.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-51455",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/51455",
            "specs": [
                "<3.2.1"
            ],
            "v": "<3.2.1"
        }
    ],
    "pod5": [
        {
            "advisory": "Pod5 0.1.19 includes a version of pod5 core that fixes a crash when uploading malicious files.\r\nhttps://github.com/nanoporetech/pod5-file-format/commit/c57e978badc670b6c918a0f8b5ebf480ba813284",
            "cve": "PVE-2023-55077",
            "id": "pyup.io-55077",
            "more_info_path": "/vulnerabilities/PVE-2023-55077/55077",
            "specs": [
                "<0.1.19"
            ],
            "v": "<0.1.19"
        }
    ],
    "podcastfy": [
        {
            "advisory": "Affected versions of Podcastfy are vulnerable to security risks by allowing image loading from local 'path' sources. This can lead to unauthorized access or injection attacks through improperly managed file paths. The vulnerability arises from loading images via local paths instead of secure URLs. To mitigate, users must update their image references to use valid 'URL's instead of 'path's.",
            "cve": "PVE-2024-74070",
            "id": "pyup.io-74070",
            "more_info_path": "/vulnerabilities/PVE-2024-74070/74070",
            "specs": [
                "<0.3.3"
            ],
            "v": "<0.3.3"
        }
    ],
    "podder-task-base": [
        {
            "advisory": "Podder-task-base 0.4.0 updates its dependency 'SQLAlchemy' to include security fixes.",
            "cve": "CVE-2019-7548",
            "id": "pyup.io-37260",
            "more_info_path": "/vulnerabilities/CVE-2019-7548/37260",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Podder-task-base 0.4.0 updates its dependency 'SQLAlchemy' to include security fixes.",
            "cve": "CVE-2019-7164",
            "id": "pyup.io-54913",
            "more_info_path": "/vulnerabilities/CVE-2019-7164/54913",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "podman": [
        {
            "advisory": "Podman 4.4.0 updates its dependency 'urllib3' to include a security fix.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-53101",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/53101",
            "specs": [
                "<4.4.0"
            ],
            "v": "<4.4.0"
        }
    ],
    "poetry": [
        {
            "advisory": "Poetry 1.1.9 includes a fix for CVE-2022-36070: To handle dependencies that come from a Git repository, Poetry executes various commands, e.g. 'git config'. These commands are being executed using the executable\u2019s name and not its absolute path. This can lead to the execution of untrusted code due to the way Windows resolves executable names to paths. Unlike Linux-based operating systems, Windows searches for the executable in the current directory first and looks in the paths that are defined in the 'PATH' environment variable afterward. This vulnerability can lead to Arbitrary Code Execution, which would lead to the takeover of the system. If a developer is exploited, the attacker could steal credentials or persist their access. If the exploit happens on a server, the attackers could use their access to attack other internal systems. Since this vulnerability requires a fair amount of user interaction, it is not as dangerous as a remotely exploitable one. However, it still puts developers at risk when dealing with untrusted files in a way they think is safe. The victim could also not protect themself by vetting any Git or Poetry config files that might be present in the directory, because the behavior is undocumented.\r\nhttps://github.com/python-poetry/poetry/security/advisories/GHSA-j4j9-7hg9-97g6",
            "cve": "CVE-2022-36070",
            "id": "pyup.io-50948",
            "more_info_path": "/vulnerabilities/CVE-2022-36070/50948",
            "specs": [
                "<1.1.9"
            ],
            "v": "<1.1.9"
        },
        {
            "advisory": "Poetry 1.1.9 includes a fix for CVE-2022-36069: When handling dependencies that come from a Git repository instead of a registry, Poetry uses various commands, such as 'git clone'. These commands are constructed using user input (e.g. the repository URL). When building the commands, Poetry correctly avoids Command Injection vulnerabilities by passing an array of arguments instead of a command string. However, there is the possibility that a user input starts with a dash ('-') and is therefore treated as an optional argument instead of a positional one. This can lead to Code Execution because some of the commands have options that can be leveraged to run arbitrary executables. If a developer is exploited, the attacker could steal credentials or persist their access. If the exploit happens on a server, the attackers could use their access to attack other internal systems. Since this vulnerability requires a fair amount of user interaction, it is not as dangerous as a remotely exploitable one. However, it still puts developers at risk when dealing with untrusted files in a way they think is safe, because the exploit still works when the victim tries to make sure nothing can happen, e.g. by vetting any Git or Poetry config files that might be present in the directory.\r\nhttps://github.com/python-poetry/poetry/security/advisories/GHSA-9xgj-fcgf-x6mw",
            "cve": "CVE-2022-36069",
            "id": "pyup.io-50947",
            "more_info_path": "/vulnerabilities/CVE-2022-36069/50947",
            "specs": [
                "<1.1.9"
            ],
            "v": "<1.1.9"
        },
        {
            "advisory": "Poetry requires virtualenv version 20.26.6 or higher to protect against potential command injection attacks when running poetry shell in untrusted projects.",
            "cve": "PVE-2024-73456",
            "id": "pyup.io-74403",
            "more_info_path": "/vulnerabilities/PVE-2024-73456/74403",
            "specs": [
                "<1.8.4"
            ],
            "v": "<1.8.4"
        },
        {
            "advisory": "Poetry 1.1.10 includes a fix for CVE-2022-26184: Poetry v1.1.9 and below was discovered to contain an untrusted search path which causes the application to behave in unexpected ways when users execute Poetry commands in a directory containing malicious content. This vulnerability occurs when the application is ran on Windows OS.\r\nhttps://github.com/python-poetry/poetry-core/pull/205/commits/fa9cb6f358ae840885c700f954317f34838caba7",
            "cve": "CVE-2022-26184",
            "id": "pyup.io-47025",
            "more_info_path": "/vulnerabilities/CVE-2022-26184/47025",
            "specs": [
                "<=1.1.9"
            ],
            "v": "<=1.1.9"
        }
    ],
    "poetry-core": [
        {
            "advisory": "When handling dependencies that come from a Git repository instead of a registry, Poetry uses various commands, such as 'git clone'. These commands are constructed using user input (e.g. the repository URL). When building the commands, Poetry correctly avoids Command Injection vulnerabilities by passing an array of arguments instead of a command string. However, there is the possibility that a user input starts with a dash ('-') and is therefore treated as an optional argument instead of a positional one. This can lead to Code Execution because some of the commands have options that can be leveraged to run arbitrary executables. If a developer is exploited, the attacker could steal credentials or persist their access. If the exploit happens on a server, the attackers could use their access to attack other internal systems. Since this vulnerability requires a fair amount of user interaction, it is not as dangerous as a remotely exploitable one. However, it still puts developers at risk when dealing with untrusted files in a way they think is safe, because the exploit still works when the victim tries to make sure nothing can happen, e.g. by vetting any Git or Poetry config files that might be present in the directory.",
            "cve": "CVE-2022-36069",
            "id": "pyup.io-71598",
            "more_info_path": "/vulnerabilities/CVE-2022-36069/71598",
            "specs": [
                "<1.1.9"
            ],
            "v": "<1.1.9"
        },
        {
            "advisory": "Poetry-core affected versions have been discovered to contain an untrusted search path, which causes the application to behave in unexpected ways when users execute Poetry commands in a directory containing malicious content. This vulnerability occurs when the application is running on Windows OS.\r\n# This only affects Windows users",
            "cve": "CVE-2022-36070",
            "id": "pyup.io-71597",
            "more_info_path": "/vulnerabilities/CVE-2022-36070/71597",
            "specs": [
                "<1.1.9"
            ],
            "v": "<1.1.9"
        }
    ],
    "poetry-plugin-check-yanked": [
        {
            "advisory": "Poetry-plugin-check-yanked 0.2.2 updates `urllib3` from version 2.2.1 to 2.2.2 to address a MODERATE severity security issue identified as CVE-2024-37891.",
            "cve": "CVE-2024-37891",
            "id": "pyup.io-71605",
            "more_info_path": "/vulnerabilities/CVE-2024-37891/71605",
            "specs": [
                "<0.2.2"
            ],
            "v": "<0.2.2"
        }
    ],
    "pokedex-py": [
        {
            "advisory": "Pokedex.py 1.1.2 updates 'requests' package to version >=2.20.0 to fix an information exposure vulnerability.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36593",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36593",
            "specs": [
                "<1.1.2"
            ],
            "v": "<1.1.2"
        }
    ],
    "polemarch": [
        {
            "advisory": "Polemarch 1.7.4 updates its dependency 'markdown2' to version '2.3.9' to include a fix for a XSS vulnerability.\r\nhttps://github.com/vstconsulting/polemarch/commit/0f4c7171447a2cdd41a9cb3c272135e5767e4309\r\nhttps://github.com/advisories/GHSA-fv3h-8x5j-pvgq",
            "cve": "CVE-2020-11888",
            "id": "pyup.io-59824",
            "more_info_path": "/vulnerabilities/CVE-2020-11888/59824",
            "specs": [
                "<1.7.4"
            ],
            "v": "<1.7.4"
        }
    ],
    "pollbot": [
        {
            "advisory": "Pollbot is open source software which \"frees its human masters from the toilsome task of polling for the state of things during the Firefox release process.\" In Pollbot before version 1.4.4 there is an open redirection vulnerability in the path of \"https://pollbot.services.mozilla.com/\". An attacker can redirect anyone to malicious sites. To Reproduce type in this URL: \"https://pollbot.services.mozilla.com//evil.com/\". Affected versions will redirect to that website when you inject a payload like \"//evil.com/\". This is fixed in version 1.4.4.",
            "cve": "CVE-2021-21354",
            "id": "pyup.io-42300",
            "more_info_path": "/vulnerabilities/CVE-2021-21354/42300",
            "specs": [
                "<1.4.4"
            ],
            "v": "<1.4.4"
        },
        {
            "advisory": "Open redirect in pollbot (pollbot.services.mozilla.com) in versions before 1.4.6",
            "cve": "CVE-2022-0637",
            "id": "pyup.io-54653",
            "more_info_path": "/vulnerabilities/CVE-2022-0637/54653",
            "specs": [
                ">=0,<1.4.6"
            ],
            "v": ">=0,<1.4.6"
        }
    ],
    "polyaxon": [
        {
            "advisory": "Polyaxon 0.4.1 updates its NPM dependency 'lodash' to v4.17.11 to include security fixes.",
            "cve": "CVE-2018-16487",
            "id": "pyup.io-49096",
            "more_info_path": "/vulnerabilities/CVE-2018-16487/49096",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Polyaxon 0.4.1 updates its NPM dependency 'bootstrap' to v3.4.1 to include a security fix.",
            "cve": "CVE-2019-8331",
            "id": "pyup.io-49097",
            "more_info_path": "/vulnerabilities/CVE-2019-8331/49097",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Polyaxon 0.4.1 updates its NPM dependency 'lodash' to v4.17.11 to include security fixes.",
            "cve": "CVE-2019-1010266",
            "id": "pyup.io-38029",
            "more_info_path": "/vulnerabilities/CVE-2019-1010266/38029",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Polyaxon 0.5.1 updates its NPM dependency 'lodash' to v4.17.14: vulnerability issue.",
            "cve": "CVE-2019-10744",
            "id": "pyup.io-38025",
            "more_info_path": "/vulnerabilities/CVE-2019-10744/38025",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Polyaxon 0.5.5 updates its dependency 'django' to v2.2.4 to include security fixes.",
            "cve": "CVE-2019-14235",
            "id": "pyup.io-45020",
            "more_info_path": "/vulnerabilities/CVE-2019-14235/45020",
            "specs": [
                "<0.5.5"
            ],
            "v": "<0.5.5"
        },
        {
            "advisory": "Polyaxon 0.5.5 updates its dependency 'django' to v2.2.4 to include security fixes.",
            "cve": "CVE-2019-14233",
            "id": "pyup.io-45018",
            "more_info_path": "/vulnerabilities/CVE-2019-14233/45018",
            "specs": [
                "<0.5.5"
            ],
            "v": "<0.5.5"
        },
        {
            "advisory": "Polyaxon 0.5.5 updates its dependency 'djangorestframework' to v3.10.1 to include a security fix.",
            "cve": "CVE-2020-25626",
            "id": "pyup.io-38023",
            "more_info_path": "/vulnerabilities/CVE-2020-25626/38023",
            "specs": [
                "<0.5.5"
            ],
            "v": "<0.5.5"
        },
        {
            "advisory": "Polyaxon 0.5.5 updates its dependency 'django' to v2.2.4 to include security fixes.",
            "cve": "CVE-2019-14232",
            "id": "pyup.io-45017",
            "more_info_path": "/vulnerabilities/CVE-2019-14232/45017",
            "specs": [
                "<0.5.5"
            ],
            "v": "<0.5.5"
        },
        {
            "advisory": "Polyaxon 0.5.5 updates its dependency 'django' to v2.2.4 to include security fixes.",
            "cve": "CVE-2019-14234",
            "id": "pyup.io-45019",
            "more_info_path": "/vulnerabilities/CVE-2019-14234/45019",
            "specs": [
                "<0.5.5"
            ],
            "v": "<0.5.5"
        },
        {
            "advisory": "Polyaxon 0.6.0 fixes some unspecified security issues.",
            "cve": "PVE-2021-38022",
            "id": "pyup.io-38022",
            "more_info_path": "/vulnerabilities/PVE-2021-38022/38022",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "polylatlib": [
        {
            "advisory": "Polylatlib version 1.0.2 updates its required Python version to ^3.9, moving from the previously required ^3.8, in response to the security issue CVE-2019-17514.\r\nhttps://github.com/RexGreenway/PolyLatLib/commit/ca181eca306b1d6c1ad3d6a87fa94878ab52a43b",
            "cve": "CVE-2019-17514",
            "id": "pyup.io-64959",
            "more_info_path": "/vulnerabilities/CVE-2019-17514/64959",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "polymatheia": [
        {
            "advisory": "Polymatheia 0.3.1 updates its dependency 'pygments' to v2.7.4 to include security fixes.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-49906",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/49906",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Polymatheia 0.3.1 updates its dependency 'lxml' to v4.6.3 to include security fixes.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-49782",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/49782",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Polymatheia 0.3.1 updates its dependency 'lxml' to v4.6.3 to include security fixes.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-49905",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/49905",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Polymatheia 0.3.1 updates its dependency 'pyyaml' to v5.4 to include a security fix.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-49908",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/49908",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Polymatheia 0.3.1 updates its dependency 'pygments' to v2.7.4 to include security fixes.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-49907",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/49907",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Polymatheia 0.3.1 updates its dependency 'jinja2' to v2.11.3 to include a security fix.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-49909",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/49909",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Polymatheia 1.0.2 updates its dependency 'certifi' to include a security fix.",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-52375",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/52375",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        },
        {
            "advisory": "Polymatheia 1.0.4 updates its dependency 'certifi' to version '2023.7.22' to include a fix for an Improper Following of a Certificate's Chain of Trust vulnerability.\r\nhttps://github.com/scmmmh/polymatheia/pull/29",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60400",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60400",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        },
        {
            "advisory": "Polymatheia 1.0.4 updates its dependency 'pygments' to version '2.15.0' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/scmmmh/polymatheia/pull/28",
            "cve": "CVE-2022-40896",
            "id": "pyup.io-60403",
            "more_info_path": "/vulnerabilities/CVE-2022-40896/60403",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        },
        {
            "advisory": "Polymatheia 1.0.4 updates its dependency 'requests' to version '2.31.0' to include a fix for an Information Exposure vulnerability.\r\nhttps://github.com/scmmmh/polymatheia/pull/27",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-60404",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/60404",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        },
        {
            "advisory": "Polymatheia version 1.0.7 has updated its urllib3 library from version 2.0.6 to 2.0.7 in response to security concerns outlined in CVE-2023-45803.",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-67879",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/67879",
            "specs": [
                "<1.0.7"
            ],
            "v": "<1.0.7"
        },
        {
            "advisory": "Polymatheia version 1.0.7 has updated its jinja2  library from version 3.1.2 to 3.1.3 in response to security concerns outlined in CVE-2024-22195.",
            "cve": "CVE-2024-22195",
            "id": "pyup.io-67882",
            "more_info_path": "/vulnerabilities/CVE-2024-22195/67882",
            "specs": [
                "<1.0.7"
            ],
            "v": "<1.0.7"
        },
        {
            "advisory": "Polymatheia version 1.0.8 has upgraded its idna library from version 3.4 to 3.7 to address security vulnerabilities detailed in CVE-2022-45061.",
            "cve": "CVE-2022-45061",
            "id": "pyup.io-67878",
            "more_info_path": "/vulnerabilities/CVE-2022-45061/67878",
            "specs": [
                "<1.0.8"
            ],
            "v": "<1.0.8"
        }
    ],
    "polyswarm-client": [
        {
            "advisory": "Polyswarm-client 2.11.7 updates its dependency 'aiohttp' to v3.7.4 to include a security fix.",
            "cve": "CVE-2021-21330",
            "id": "pyup.io-40126",
            "more_info_path": "/vulnerabilities/CVE-2021-21330/40126",
            "specs": [
                "<2.11.7"
            ],
            "v": "<2.11.7"
        }
    ],
    "poorwsgi": [
        {
            "advisory": "poorwsgi 1.0.2 includes several security related enhancements related to secret key generation.",
            "cve": "PVE-2021-26015",
            "id": "pyup.io-26015",
            "more_info_path": "/vulnerabilities/PVE-2021-26015/26015",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "pootle": [
        {
            "advisory": "Pootle 2.8.0 fixes several XSS vulnerabilities.\r\nhttps://github.com/translate/pootle/pull/4686",
            "cve": "PVE-2021-34890",
            "id": "pyup.io-34890",
            "more_info_path": "/vulnerabilities/PVE-2021-34890/34890",
            "specs": [
                "<2.8.0"
            ],
            "v": "<2.8.0"
        },
        {
            "advisory": "Pootle 2.8.0 updates its dependency 'django-allauth' to v0.28.0 to include a security fix.",
            "cve": "PVE-2021-25737",
            "id": "pyup.io-47026",
            "more_info_path": "/vulnerabilities/PVE-2021-25737/47026",
            "specs": [
                "<2.8.0"
            ],
            "v": "<2.8.0"
        },
        {
            "advisory": "Pootle 2.7.3 prevents the leak of user data.\r\nhttps://github.com/translate/pootle/commit/07839d4abe1663f890e28a6b2cc28b59148b184b",
            "cve": "PVE-2021-42747",
            "id": "pyup.io-42747",
            "more_info_path": "/vulnerabilities/PVE-2021-42747/42747",
            "specs": [
                ">=2.7.0,<2.7.3"
            ],
            "v": ">=2.7.0,<2.7.3"
        },
        {
            "advisory": "Pootle 2.7.x before 2.7.3 is affected by several XSS vulnerabilities.\r\nhttps://github.com/translate/pootle/commit/d36f91a9a3c022251d927a439a7566e57127367f\r\nhttps://github.com/translate/pootle/commit/82e6cb6c9b9468090d0b0cee81e706ee175d1e36\r\nhttps://github.com/translate/pootle/commit/7d5a80c3fdd9cf70ccb7a6966e964566c0f764ff",
            "cve": "PVE-2021-34201",
            "id": "pyup.io-34201",
            "more_info_path": "/vulnerabilities/PVE-2021-34201/34201",
            "specs": [
                ">=2.7.0,<2.7.3"
            ],
            "v": ">=2.7.0,<2.7.3"
        }
    ],
    "port-ocean": [
        {
            "advisory": "Port-ocean 0.12.4 pins 'cryptography' dependency to versions \"^43.0.1\" to include a security fix.",
            "cve": "PVE-2024-73711",
            "id": "pyup.io-73710",
            "more_info_path": "/vulnerabilities/PVE-2024-73711/73710",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Port-ocean updates its Black library dependency from 23.3.0 to 24.4.2 to patch CVE-2024-21503.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-74131",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/74131",
            "specs": [
                "<0.13.1"
            ],
            "v": "<0.13.1"
        }
    ],
    "portablemc": [
        {
            "advisory": "Portablemc 2.2.0 fixes indirectly a Log4j related vulnerability with changes on the version manifest management.\r\nhttps://github.com/mindstorm38/portablemc/issues/52",
            "cve": "CVE-2021-44228",
            "id": "pyup.io-44831",
            "more_info_path": "/vulnerabilities/CVE-2021-44228/44831",
            "specs": [
                "<2.2.0"
            ],
            "v": "<2.2.0"
        }
    ],
    "portabletab": [
        {
            "advisory": "Portabletab version 0.3.3.post1 has updated its certifi dependency from version 2022.12.7 to 2024.2 in response to CVE-2023-37920.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-67903",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/67903",
            "specs": [
                "<0.3.3.post1"
            ],
            "v": "<0.3.3.post1"
        }
    ],
    "portage": [
        {
            "advisory": "The urlopen function in pym/portage/util/_urlopen.py in Gentoo Portage 2.1.12, when using HTTPS, does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and modify binary package lists via a crafted certificate.",
            "cve": "CVE-2013-2100",
            "id": "pyup.io-67956",
            "more_info_path": "/vulnerabilities/CVE-2013-2100/67956",
            "specs": [
                "<2.1.12"
            ],
            "v": "<2.1.12"
        },
        {
            "advisory": "Gentoo Portage through 2.3.84 allows local users to place a Trojan horse plugin in the /usr/lib64/nagios/plugins directory by leveraging access to the nagios user account, because this directory is writable in between a call to emake and a call to fowners.",
            "cve": "CVE-2019-20384",
            "id": "pyup.io-70506",
            "more_info_path": "/vulnerabilities/CVE-2019-20384/70506",
            "specs": [
                "<2.3.84"
            ],
            "v": "<2.3.84"
        },
        {
            "advisory": "In Gentoo Portage before 3.0.47, there is missing PGP validation of executed code: the standalone emerge-webrsync downloads a .gpgsig file but does not perform signature verification. Unless emerge-webrsync is used, Portage is not vulnerable.",
            "cve": "CVE-2016-20021",
            "id": "pyup.io-66717",
            "more_info_path": "/vulnerabilities/CVE-2016-20021/66717",
            "specs": [
                "<3.0.47"
            ],
            "v": "<3.0.47"
        },
        {
            "advisory": "Affected versions of the Portage package are potentially vulnerable to Command Injection due to evaluating untrusted timestamp fields in a Bash arithmetic context via command substitution. The `bin/emerge-webrsync` functions `get_repository_timestamp()` and `get_snapshot_timestamp()` previously extracted the first field of `metadata/timestamp.x` without integer validation, and the `do_snapshot()` and `do_latest_snapshot()` call sites compared values using `(( snapshot_timestamp < $(get_repository_timestamp) ))`, allowing untrusted input to be parsed with command substitution.",
            "cve": "PVE-2025-79581",
            "id": "pyup.io-79581",
            "more_info_path": "/vulnerabilities/PVE-2025-79581/79581",
            "specs": [
                "<3.0.69"
            ],
            "v": "<3.0.69"
        },
        {
            "advisory": "Affected versions of the Portage package are potentially vulnerable to Improper Verification of Cryptographic Signature due to accepting a lone \u201c\\[GNUPG:] GOODSIG\u201d token when validating repository snapshot signatures. The `check_file_signature_gpg_unwrapped()` function in `emerge-webrsync` matches `gpg --status-fd` output for `\"[GNUPG:] GOODSIG\"` without requiring a trailing space and without also enforcing the presence of `VALIDSIG` and `TRUST_ULTIMATE`, which can cause outputs like `GOODSIG/VALIDSIG/TRUST_NEVER` or `TRUST_UNDEFINED` to be misinterpreted as a valid, ultimately trusted signature.",
            "cve": "PVE-2025-79568",
            "id": "pyup.io-79568",
            "more_info_path": "/vulnerabilities/PVE-2025-79568/79568",
            "specs": [
                "<3.0.69"
            ],
            "v": "<3.0.69"
        }
    ],
    "portrait-mode-video": [
        {
            "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'portrait-mode-video' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.",
            "cve": "PVE-2024-74235",
            "id": "pyup.io-74235",
            "more_info_path": "/vulnerabilities/PVE-2024-74235/74235",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "portray": [
        {
            "advisory": "Portray 1.6.0 updates the minimum version of the 'mkdocs-material' to 7.0.0 to address a security concerns in earlier versions.",
            "cve": "CVE-2020-7788",
            "id": "pyup.io-44814",
            "more_info_path": "/vulnerabilities/CVE-2020-7788/44814",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        },
        {
            "advisory": "Portray 1.6.0 updates the minimum version of the 'mkdocs-material' to 7.0.0 to address a security issue.",
            "cve": "CVE-2020-8203",
            "id": "pyup.io-40138",
            "more_info_path": "/vulnerabilities/CVE-2020-8203/40138",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        }
    ],
    "postfix-mta-sts-resolver": [
        {
            "advisory": "In postfix-mta-sts-resolver before 0.5.1, All users can receive incorrect response from daemon under rare conditions, rendering downgrade of effective STS policy.",
            "cve": "CVE-2019-16791",
            "id": "pyup.io-42264",
            "more_info_path": "/vulnerabilities/CVE-2019-16791/42264",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Postfix-mta-sts-resolver 0.6.1 hardens the container security.",
            "cve": "PVE-2021-37461",
            "id": "pyup.io-37461",
            "more_info_path": "/vulnerabilities/PVE-2021-37461/37461",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        }
    ],
    "postgraas-server": [
        {
            "advisory": "A vulnerability, which was classified as critical, was found in Blue Yonder postgraas_server up to 2.0.0b2. Affected is the function _create_pg_connection/create_postgres_db of the file postgraas_server/backends/postgres_cluster/postgres_cluster_driver.py of the component PostgreSQL Backend Handler. The manipulation leads to sql injection. Upgrading to version 2.0.0 can address this issue. The patch is identified as 7cd8d016edc74a78af0d81c948bfafbcc93c937c. It is recommended to upgrade the affected component. VDB-234246 is the identifier assigned to this vulnerability.",
            "cve": "CVE-2018-25088",
            "id": "pyup.io-65851",
            "more_info_path": "/vulnerabilities/CVE-2018-25088/65851",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        }
    ],
    "postorius": [
        {
            "advisory": "An issue was discovered in views/list.py in GNU Mailman Postorius before 1.3.5. An attacker (logged into any account) can send a crafted POST request to unsubscribe any user from a mailing list, also revealing whether that address was subscribed in the first place.",
            "cve": "CVE-2021-40347",
            "id": "pyup.io-42321",
            "more_info_path": "/vulnerabilities/CVE-2021-40347/42321",
            "specs": [
                "<1.3.5"
            ],
            "v": "<1.3.5"
        }
    ],
    "postquantum-feldman-vss": [
        {
            "advisory": "PostQuantum-Feldman-VSS, a Python library implementing Feldman's Verifiable Secret Sharing scheme with post-quantum security, was vulnerable to denial-of-service attacks in versions up to and including 0.7.6b0. This vulnerability stems from the library's reliance on the gmpy2 library for arbitrary-precision arithmetic. gmpy2, in turn, depends on the GNU Multiple Precision Arithmetic Library (GMP). GMP, by design, terminates the process when it cannot allocate memory. An attacker could exploit this by providing carefully crafted inputs that cause gmpy2 to attempt to allocate extremely large amounts of memory, leading to a crash of the Python interpreter and thus a denial of service.",
            "cve": "PVE-2025-76304",
            "id": "pyup.io-76304",
            "more_info_path": "/vulnerabilities/PVE-2025-76304/76304",
            "specs": [
                "<0.7.7b0"
            ],
            "v": "<0.7.7b0"
        },
        {
            "advisory": "Postquantum-feldman-vss addresses a potential denial-of-service vulnerability related to excessive memory allocation.",
            "cve": "PVE-2025-75996",
            "id": "pyup.io-75996",
            "more_info_path": "/vulnerabilities/PVE-2025-75996/75996",
            "specs": [
                "<0.8.0b2"
            ],
            "v": "<0.8.0b2"
        },
        {
            "advisory": "Post-Quantum Secure Feldman's Verifiable Secret Sharing has Inadequate Fault Injection Countermeasures in `secure_redundant_execution`",
            "cve": "CVE-2025-29779",
            "id": "pyup.io-76307",
            "more_info_path": "/vulnerabilities/CVE-2025-29779/76307",
            "specs": [
                "<0.8.0b2"
            ],
            "v": "<0.8.0b2"
        },
        {
            "advisory": "Post-Quantum Secure Feldman's Verifiable Secret Sharing has Timing Side-Channels in Matrix Operations",
            "cve": "CVE-2025-29780",
            "id": "pyup.io-76308",
            "more_info_path": "/vulnerabilities/CVE-2025-29780/76308",
            "specs": [
                "<0.8.0b2"
            ],
            "v": "<0.8.0b2"
        }
    ],
    "posty": [
        {
            "advisory": "Posty 2.1.0 includes a security patch for the function 'from_yaml' in 'posty/post.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/nickpegg/posty/commit/d2f3fbd15cc685c425aaa3edc4a113c4218674ef",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41365",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41365",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        }
    ],
    "pottery": [
        {
            "advisory": "Affected versions of Pottery are potentially vulnerable to information disclosure through improper exception handling. This issue primarily affects code paths that handle exceptions in Redis-like operations.",
            "cve": "PVE-2025-76051",
            "id": "pyup.io-76051",
            "more_info_path": "/vulnerabilities/PVE-2025-76051/76051",
            "specs": [
                "<4.0.0"
            ],
            "v": "<4.0.0"
        }
    ],
    "power-grid-model": [
        {
            "advisory": "Power-grid-model 1.2.50 addresses a critical security vulnerability linked to the use of regular expressions for parsing node references. It could have led to an exponential increase in computational complexity, potentially exposing the system to Denial of Service (DoS) attacks. The update discontinues the use of regex for node reference parsing and replaces it with Python functions, ensuring uniformity and readability throughout the codebase. This change significantly reduces the risk of ReDoS attacks and enhances the overall security of the system.\r\nhttps://github.com/PowerGridModel/power-grid-model-io/pull/201",
            "cve": "PVE-2024-63525",
            "id": "pyup.io-63525",
            "more_info_path": "/vulnerabilities/PVE-2024-63525/63525",
            "specs": [
                "<1.2.50"
            ],
            "v": "<1.2.50"
        }
    ],
    "power-grid-model-io": [
        {
            "advisory": "Power-grid-model-io 1.2.50 includes a fix for a potential ReDOS vulnerability.\r\nhttps://github.com/PowerGridModel/power-grid-model-io/pull/201",
            "cve": "PVE-2023-61694",
            "id": "pyup.io-61694",
            "more_info_path": "/vulnerabilities/PVE-2023-61694/61694",
            "specs": [
                "<1.2.50"
            ],
            "v": "<1.2.50"
        },
        {
            "advisory": "Affected versions of the power-grid-model-io package are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure regular expressions that permit catastrophic backtracking. The patterns defined in power_grid_model_io/utils/regex.py\u2014notably NODE_REF_RE, TRAFO_CONNECTION_RE, and TRAFO3_CONNECTION_RE\u2014were invoked via fullmatch in converters/pandapower_converter.py and functions/phase_to_phase.py, where crafted transformer-connection strings and node-reference names can induce exponential matching behaviour.",
            "cve": "PVE-2025-79433",
            "id": "pyup.io-79433",
            "more_info_path": "/vulnerabilities/PVE-2025-79433/79433",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "powergenome": [
        {
            "advisory": "Powergenome version 0.6.1 enhances SQL input handling to mitigate the risk of SQL injection attacks.",
            "cve": "PVE-2024-70869",
            "id": "pyup.io-70869",
            "more_info_path": "/vulnerabilities/PVE-2024-70869/70869",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        }
    ],
    "powerline-gitstatus": [
        {
            "advisory": "Powerline-gitstatus (aka Powerline Gitstatus) before 1.3.2 allows arbitrary code execution. Git repositories can contain per-repository configuration that changes the behavior of git, including running arbitrary commands. When using powerline-gitstatus, changing to a directory automatically runs git commands in order to display information about the current repository in the prompt. If an attacker can convince a user to change their current directory to one controlled by the attacker, such as in a shared filesystem or extracted archive, powerline-gitstatus will run arbitrary commands under the attacker's control. \r\nNOTE: this is similar to CVE-2022-20001.\r\nAffected functions: powerline_gitstatus.segments.GitStatusSegment.get_base_command",
            "cve": "CVE-2022-42906",
            "id": "pyup.io-54518",
            "more_info_path": "/vulnerabilities/CVE-2022-42906/54518",
            "specs": [
                ">=0,<1.3.2"
            ],
            "v": ">=0,<1.3.2"
        }
    ],
    "powermolecli": [
        {
            "advisory": "Powermolecli 1.0.10 updates its dependency 'certifi' to v2022.12.7 to include a security fix.",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-52579",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/52579",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Powermolecli 1.0.13 updates its dependency 'markdown-it-py' to v2.2.0 to include security fixes.",
            "cve": "CVE-2023-26303",
            "id": "pyup.io-54811",
            "more_info_path": "/vulnerabilities/CVE-2023-26303/54811",
            "specs": [
                "<1.0.13"
            ],
            "v": "<1.0.13"
        },
        {
            "advisory": "Powermolecli 1.0.13 updates its dependency 'markdown-it-py' to v2.2.0 to include security fixes.",
            "cve": "CVE-2023-26302",
            "id": "pyup.io-54752",
            "more_info_path": "/vulnerabilities/CVE-2023-26302/54752",
            "specs": [
                "<1.0.13"
            ],
            "v": "<1.0.13"
        }
    ],
    "powermolegui": [
        {
            "advisory": "Powermolegui 0.2.10 updates its dependency 'certifi' to v2022.12.7 to include a security fix.",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-52587",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/52587",
            "specs": [
                "<0.2.10"
            ],
            "v": "<0.2.10"
        },
        {
            "advisory": "Powermolegui 0.2.12 updates its dependency 'markdown-it-py' to v2.2.0 to include security fixes.",
            "cve": "CVE-2023-26303",
            "id": "pyup.io-54806",
            "more_info_path": "/vulnerabilities/CVE-2023-26303/54806",
            "specs": [
                "<0.2.12"
            ],
            "v": "<0.2.12"
        },
        {
            "advisory": "Powermolegui 0.2.12 updates its dependency 'markdown-it-py' to v2.2.0 to include security fixes.",
            "cve": "CVE-2023-26302",
            "id": "pyup.io-54804",
            "more_info_path": "/vulnerabilities/CVE-2023-26302/54804",
            "specs": [
                "<0.2.12"
            ],
            "v": "<0.2.12"
        }
    ],
    "powermolelib": [
        {
            "advisory": "Powermolelib 3.4.3 updates its dependency 'certifi' to v2022.12.7 to include a security fix.",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-52578",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/52578",
            "specs": [
                "<3.4.3"
            ],
            "v": "<3.4.3"
        },
        {
            "advisory": "Powermolelib 3.4.5 updates its dependency 'markdown-it-py' to v2.2.0 to include security fixes.",
            "cve": "CVE-2023-26302",
            "id": "pyup.io-54749",
            "more_info_path": "/vulnerabilities/CVE-2023-26302/54749",
            "specs": [
                "<3.4.5"
            ],
            "v": "<3.4.5"
        },
        {
            "advisory": "Powermolelib 3.4.5 updates its dependency 'markdown-it-py' to v2.2.0 to include security fixes.",
            "cve": "CVE-2023-26303",
            "id": "pyup.io-54812",
            "more_info_path": "/vulnerabilities/CVE-2023-26303/54812",
            "specs": [
                "<3.4.5"
            ],
            "v": "<3.4.5"
        }
    ],
    "ppgan": [
        {
            "advisory": "Ppgan 0.1.3 includes a security patch for the function 'init' in 'ppgan/apps/first_order_predictor.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/PaddlePaddle/PaddleGAN/commit/b4f066016ba664b84a55d7894e554db771995187#diff-ea93fd79db0cbeaf277ce407386f1a8a5b7446fd0955294d922165b739eb2e52",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41366",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41366",
            "specs": [
                "<0.1.3"
            ],
            "v": "<0.1.3"
        }
    ],
    "pptest": [
        {
            "advisory": "Pptest is a malicious package, typosquatting.  It steals Discord access tokens, passwords, and even stage dependency confusion attacks.\r\nhttps://thehackernews.com/2021/11/11-malicious-pypi-python-libraries.html",
            "cve": "PVE-2022-45456",
            "id": "pyup.io-45456",
            "more_info_path": "/vulnerabilities/PVE-2022-45456/45456",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "pragy-dl": [
        {
            "advisory": "Pragy-dl version 2023.07.06 introduces changes due to CVE-2023-35934: The `--add-header Cookie:` option is deprecated and automatically restricted to the domains of input URLs. Additionally, cookies passed to external downloaders are now scoped, and the `cookies` field has been added to info.json. The `http_headers.Cookie` field is now deprecated to enhance security and compliance.",
            "cve": "CVE-2023-35934",
            "id": "pyup.io-67930",
            "more_info_path": "/vulnerabilities/CVE-2023-35934/67930",
            "specs": [
                "<2023.07.06"
            ],
            "v": "<2023.07.06"
        },
        {
            "advisory": "Pragy-dl version 2023.09.24 implements security measures to prevent Remote Code Execution (RCE) when using the `--exec` option with `%q`.",
            "cve": "CVE-2023-40581",
            "id": "pyup.io-67929",
            "more_info_path": "/vulnerabilities/CVE-2023-40581/67929",
            "specs": [
                "<2023.09.24"
            ],
            "v": "<2023.09.24"
        }
    ],
    "pre-commit": [
        {
            "advisory": "Pre-commit 1.10.4 replaces 'yaml.load' with safe alternative to avoid a remote code execution vulnerability.\r\nhttps://github.com/pre-commit/pre-commit/commit/6853f4aa4c8d7e411839bacc66876baea443186a",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-42949",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/42949",
            "specs": [
                "<1.10.4"
            ],
            "v": "<1.10.4"
        }
    ],
    "prefect": [
        {
            "advisory": "Prefect 0.12.5 removes passwords from Postgres tasks' initialization methods to avoid sensitive information exposure.\r\nhttps://github.com/PrefectHQ/prefect/issues/1345",
            "cve": "PVE-2022-51811",
            "id": "pyup.io-51811",
            "more_info_path": "/vulnerabilities/PVE-2022-51811/51811",
            "specs": [
                "<0.12.5"
            ],
            "v": "<0.12.5"
        },
        {
            "advisory": "Prefect 0.12.6 removes password from Postgres tasks' initialization methods for security.",
            "cve": "PVE-2021-38663",
            "id": "pyup.io-38663",
            "more_info_path": "/vulnerabilities/PVE-2021-38663/38663",
            "specs": [
                "<0.12.6"
            ],
            "v": "<0.12.6"
        },
        {
            "advisory": "Prefect 0.14.21 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/PrefectHQ/prefect/pull/4587",
            "cve": "PVE-2023-59753",
            "id": "pyup.io-59753",
            "more_info_path": "/vulnerabilities/PVE-2023-59753/59753",
            "specs": [
                "<0.14.21"
            ],
            "v": "<0.14.21"
        },
        {
            "advisory": "Prefect 0.15.8 includes a version of Prefect UI which updates a dependency (npm:graphiql) to include a security fix.",
            "cve": "CVE-2021-41248",
            "id": "pyup.io-42952",
            "more_info_path": "/vulnerabilities/CVE-2021-41248/42952",
            "specs": [
                "<0.15.8"
            ],
            "v": "<0.15.8"
        },
        {
            "advisory": "Prefect 0.15.8 includes a Prefect Server update that bumps an upstream dependency to fix a security vulnerability. See CVE-2021-41249.",
            "cve": "CVE-2021-41249",
            "id": "pyup.io-42552",
            "more_info_path": "/vulnerabilities/CVE-2021-41249/42552",
            "specs": [
                "<0.15.8"
            ],
            "v": "<0.15.8"
        },
        {
            "advisory": "Prefect 2.11.1 include a fix for a vulnerability. This version prevents logging of credentials.\r\nhttps://github.com/PrefectHQ/prefect/commit/26b542c7826ab3d20d85dd52204c7db0e0e07678",
            "cve": "PVE-2023-60038",
            "id": "pyup.io-60038",
            "more_info_path": "/vulnerabilities/PVE-2023-60038/60038",
            "specs": [
                "<2.11.1"
            ],
            "v": "<2.11.1"
        },
        {
            "advisory": "Prefect version 2.15.0 updates its bundled starlette to mitigate a vulnerability found in python-multipart.\r\nhttps://github.com/PrefectHQ/prefect/pull/11956/commits/bb016fc65e9af0898f3d05872245c3cbe63f5c39#diff-687ab6611127b5455724a2a1c3d8faf0128af1a57cd14427007584c4028cfa4d",
            "cve": "PVE-2024-65363",
            "id": "pyup.io-65363",
            "more_info_path": "/vulnerabilities/PVE-2024-65363/65363",
            "specs": [
                "<2.15.0"
            ],
            "v": "<2.15.0"
        },
        {
            "advisory": "Prefect updates its `anyo` dependency to address a race condition in `anyo` related to a thread race condition in `_eventloop.get_asynclib()`.",
            "cve": "PVE-2024-72487",
            "id": "pyup.io-72487",
            "more_info_path": "/vulnerabilities/PVE-2024-72487/72487",
            "specs": [
                "<2.20.0"
            ],
            "v": "<2.20.0"
        },
        {
            "advisory": "Prefect affected versions have a race condition that could lead to operational inconsistencies and potential security vulnerabilities. This issue arises when multiple processes attempt to update the state of the same flow run concurrently, leading to conflicts such as duplicate flow run executions.",
            "cve": "PVE-2024-71644",
            "id": "pyup.io-71644",
            "more_info_path": "/vulnerabilities/PVE-2024-71644/71644",
            "specs": [
                "<3.0.0rc4"
            ],
            "v": "<3.0.0rc4"
        },
        {
            "advisory": "A security update has been implemented to address potential Server-Side Request Forgery (SSRF) vulnerabilities in the Prefect affected versions library. The update introduces strict URL validation for outbound requests, preventing attackers from accessing internal services or private IP addresses. The new allow_private_urls flag should be set to False in production environments unless explicitly required.",
            "cve": "PVE-2024-73210",
            "id": "pyup.io-73210",
            "more_info_path": "/vulnerabilities/PVE-2024-73210/73210",
            "specs": [
                "<3.0.2"
            ],
            "v": "<3.0.2"
        },
        {
            "advisory": "Prefect up to and including version 2.14.12 is affected by CVE-2023-6022: An attacker is able to steal secrets and potentially gain remote code execution via CSRF using the open source Prefect web server's API.\r\nhttps://github.com/PrefectHQ/prefect/issues/11380",
            "cve": "CVE-2023-6022",
            "id": "pyup.io-63067",
            "more_info_path": "/vulnerabilities/CVE-2023-6022/63067",
            "specs": [
                ">=2.0a1,<2.14.12"
            ],
            "v": ">=2.0a1,<2.14.12"
        },
        {
            "advisory": "Affected versions of the `prefecthq/prefect` package are vulnerable to Information Disclosure due to a CORS misconfiguration. The vulnerability arises because the CORS policy improperly allows requests from unauthorized domains, which can access sensitive endpoints. An attacker can exploit this by crafting requests from a malicious domain, potentially leading to unauthorized access to sensitive data, data leaks, and compromise of data integrity.",
            "cve": "CVE-2024-8183",
            "id": "pyup.io-76214",
            "more_info_path": "/vulnerabilities/CVE-2024-8183/76214",
            "specs": [
                ">=2.0a1,<2.20.17",
                ">=3.0.0rc1,<3.0.3"
            ],
            "v": ">=2.0a1,<2.20.17,>=3.0.0rc1,<3.0.3"
        }
    ],
    "prefect-azure": [
        {
            "advisory": "Prefect-azure 0.2.3 uses secure ACI environment variable for PREFECT_API_KEY to avoid a sensitive information disclosure vulnerability.\r\nhttps://github.com/PrefectHQ/prefect-azure/pull/57",
            "cve": "PVE-2022-52186",
            "id": "pyup.io-52186",
            "more_info_path": "/vulnerabilities/PVE-2022-52186/52186",
            "specs": [
                "<0.2.3"
            ],
            "v": "<0.2.3"
        }
    ],
    "prelude-parser": [
        {
            "advisory": "Prelude-parser 0.11.1 updates its Rust dependency 'PyO3' to v0.22.4 to include a security fix.",
            "cve": "PVE-2024-73689",
            "id": "pyup.io-73689",
            "more_info_path": "/vulnerabilities/PVE-2024-73689/73689",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        }
    ],
    "preqs": [
        {
            "advisory": "Affected versions of preqs are vulnerable to Path Traversal (CWE-22). This vulnerability allows attackers to manipulate the PATH argument to traverse directories using \"..\", potentially accessing or modifying unintended file system locations. The attack vector involves providing a specially crafted PATH containing \"..\" to exploit the lack of path sanitization in the ArgParser._sanitise_path method. While exploitation is limited to local environments, it can lead to unauthorized file system access. Users should upgrade to preqs version 0.1.0b4 or later, which includes proper path sanitization to prevent such attacks.",
            "cve": "PVE-2024-74132",
            "id": "pyup.io-74132",
            "more_info_path": "/vulnerabilities/PVE-2024-74132/74132",
            "specs": [
                "<0.1.0b4"
            ],
            "v": "<0.1.0b4"
        }
    ],
    "press": [
        {
            "advisory": "Press 0.5.8 includes a fix for the function 'configuration_from_yaml' in 'press/configuration/util.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load(). \r\nhttps://github.com/jr0d/press/commit/c641f54ed39d1c3a335cd967954760ede9454052#diff-482d133cd7fc1e6dde3facc3af875192a5f8397fa3054ff21956c05e1138f26f",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41367",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41367",
            "specs": [
                "<0.5.8"
            ],
            "v": "<0.5.8"
        }
    ],
    "pretalx": [
        {
            "advisory": "pretalx 2.3.1 before 2.3.2 allows path traversal in HTML export (a non-default feature). Users were able to upload crafted HTML documents that trigger the reading of arbitrary files.",
            "cve": "CVE-2023-28459",
            "id": "pyup.io-62907",
            "more_info_path": "/vulnerabilities/CVE-2023-28459/62907",
            "specs": [
                "<2.3.2"
            ],
            "v": "<2.3.2"
        },
        {
            "advisory": "Pretalx 2.3.2 includes a fix for a Path Traversal vulnerability.\r\nhttps://github.com/pretalx/pretalx/commit/1f58cdd6b200db2418991928936e4dfcdd3d882e",
            "cve": "PVE-2023-60818",
            "id": "pyup.io-60818",
            "more_info_path": "/vulnerabilities/PVE-2023-60818/60818",
            "specs": [
                "<2.3.2"
            ],
            "v": "<2.3.2"
        },
        {
            "advisory": "pretalx 2.3.1 before 2.3.2 allows path traversal in HTML export (a non-default feature). Organizers can trigger the overwriting (with the standard pretalx 404 page content) of an arbitrary file.",
            "cve": "CVE-2023-28458",
            "id": "pyup.io-62906",
            "more_info_path": "/vulnerabilities/CVE-2023-28458/62906",
            "specs": [
                "<2.3.2"
            ],
            "v": "<2.3.2"
        }
    ],
    "pretaweb.healthcheck": [
        {
            "advisory": "Pretaweb.healthcheck before 1.0 is vulnerable to DoS attacks.",
            "cve": "PVE-2021-26016",
            "id": "pyup.io-26016",
            "more_info_path": "/vulnerabilities/PVE-2021-26016/26016",
            "specs": [
                "<1.0"
            ],
            "v": "<1.0"
        }
    ],
    "pretix": [
        {
            "advisory": "pretix before 2024.1.1 mishandles file validation.",
            "cve": "CVE-2024-27447",
            "id": "pyup.io-68476",
            "more_info_path": "/vulnerabilities/CVE-2024-27447/68476",
            "specs": [
                "<2024.1.1"
            ],
            "v": "<2024.1.1"
        },
        {
            "advisory": "Stored XSS vulnerabilities in the organizer and event settings of Pretix affected versions allowed malicious event organizers to inject HTML tags into email previews on the settings page. The fix introduced proper escaping of placeholders and dynamic content using Django's `escape` function, mitigating the risk of Cross-Site Scripting (XSS) attacks. While the default Content Security Policy (CSP) of Pretix prevents the execution of attacker-provided scripts, making exploitation unlikely, this vulnerability could still be dangerous if combined with a CSP bypass, potentially allowing impersonation of other organizers or staff users.",
            "cve": "CVE-2024-8113",
            "id": "pyup.io-72971",
            "more_info_path": "/vulnerabilities/CVE-2024-8113/72971",
            "specs": [
                "<2024.7.1"
            ],
            "v": "<2024.7.1"
        },
        {
            "advisory": "pretix before 2023.7.2 allows Pillow to parse EPS files.",
            "cve": "CVE-2023-44464",
            "id": "pyup.io-65348",
            "more_info_path": "/vulnerabilities/CVE-2023-44464/65348",
            "specs": [
                "<4.20.4",
                ">=2023.6.0,<2023.6.3",
                ">=2023.7.0,<2023.7.2"
            ],
            "v": "<4.20.4,>=2023.6.0,<2023.6.3,>=2023.7.0,<2023.7.2"
        },
        {
            "advisory": "An issue was discovered in pretix before 2023.7.1. Incorrect parsing of configuration files causes the application to trust unchecked X-Forwarded-For headers even though it has not been configured to do so. This can lead to IP address spoofing by users of the application.",
            "cve": "CVE-2023-44463",
            "id": "pyup.io-65349",
            "more_info_path": "/vulnerabilities/CVE-2023-44463/65349",
            "specs": [
                ">=3.0.0,<4.20.2.post1",
                ">=2023.6.0,<2023.6.1",
                ">=2023.7.0,<2023.7.1"
            ],
            "v": ">=3.0.0,<4.20.2.post1,>=2023.6.0,<2023.6.1,>=2023.7.0,<2023.7.1"
        },
        {
            "advisory": "rami.io pretix before 4.17.1 allows OAuth application authorization from a logged-out session. The fixed versions are 4.15.1, 4.16.1, and 4.17.1.",
            "cve": "CVE-2023-27891",
            "id": "pyup.io-54666",
            "more_info_path": "/vulnerabilities/CVE-2023-27891/54666",
            "specs": [
                ">=4.17.0,<4.17.1",
                ">=4.16.0,<4.16.1",
                ">=0,<4.15.1"
            ],
            "v": ">=4.17.0,<4.17.1,>=4.16.0,<4.16.1,>=0,<4.15.1"
        }
    ],
    "pretzelai": [
        {
            "advisory": "Pretzelai version 4.1.0b2 is impacted by CVE-2024-22421, which affects JupyterLab, the original package from which Pretzelai is forked. This vulnerability can expose Authorization and XSRFToken tokens to a third party if users click on a malicious link while using an older version of jupyter-server.",
            "cve": "CVE-2024-22421",
            "id": "pyup.io-71067",
            "more_info_path": "/vulnerabilities/CVE-2024-22421/71067",
            "specs": [
                "<4.1.0b2"
            ],
            "v": "<4.1.0b2"
        }
    ],
    "pridepy": [
        {
            "advisory": "Pridepy 0.0.3 updates its dependency 'requests' to include a security fix.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-73503",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/73503",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        }
    ],
    "primerdriver": [
        {
            "advisory": "Primerdriver 1.1.1 updates its NPM dependency 'lodash' to v4.17.19 to include a security fix.\r\nhttps://hackerone.com/reports/864701",
            "cve": "PVE-2023-54889",
            "id": "pyup.io-54889",
            "more_info_path": "/vulnerabilities/PVE-2023-54889/54889",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        },
        {
            "advisory": "Primerdriver 1.1.1 updates its NPM dependency \"serialize-javascript\" to \"^3.0.0\" to include a security fix.",
            "cve": "CVE-2020-7660",
            "id": "pyup.io-54891",
            "more_info_path": "/vulnerabilities/CVE-2020-7660/54891",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "priority": [
        {
            "advisory": "Priority 1.2.0 includes a fix for CVE-2016-6580: A HTTP/2 implementation built using any version of the python priority library prior to version 1.2.0 could be targeted by a malicious peer by having that peer assign priority information for every possible HTTP/2 stream ID. The priority tree would happily continue to store the priority information for each stream, and would therefore allocate unbounded amounts of memory. Attempting to actually use a tree like this would also cause extremely high CPU usage to maintain the tree.",
            "cve": "CVE-2016-6580",
            "id": "pyup.io-42335",
            "more_info_path": "/vulnerabilities/CVE-2016-6580/42335",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "prisma": [
        {
            "advisory": "Prisma 0.6.5 types raw queries as LiteralString to prevent SQLi attacks.\r\nhttps://github.com/RobertCraigie/prisma-client-py/commit/18e68b79f0b376c017c67770d349341bb8902e1a",
            "cve": "PVE-2022-48515",
            "id": "pyup.io-48515",
            "more_info_path": "/vulnerabilities/PVE-2022-48515/48515",
            "specs": [
                "<0.6.5"
            ],
            "v": "<0.6.5"
        },
        {
            "advisory": "Prisma 0.7.1 (Python client) includes by default Prisma 3.13.0 binaries. They include a NPM dependency (undici), which has known vulnerabilities.\r\nhttps://github.com/RobertCraigie/prisma-client-py/blob/b12ab3a7bf7af5360ff5ba479f43a6b5e5adfdd8/src/prisma/_config.py#L30\r\nhttps://github.com/prisma/prisma/commit/6146d3df111e6c33353bae2d8005387f197017fd",
            "cve": "CVE-2022-32210",
            "id": "pyup.io-51300",
            "more_info_path": "/vulnerabilities/CVE-2022-32210/51300",
            "specs": [
                "<=0.7.1"
            ],
            "v": "<=0.7.1"
        }
    ],
    "prisma-cloud-pipeline": [
        {
            "advisory": "Prisma-cloud-pipeline 0.1.3 updates pyyaml to v5.4.1 to include a security fix.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-39686",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/39686",
            "specs": [
                "<0.1.3"
            ],
            "v": "<0.1.3"
        }
    ],
    "privacyidea": [
        {
            "advisory": "Privacyidea 3.4.1 uses a secure way to compare strings to avoid theoretical side channel attacks.",
            "cve": "PVE-2021-39341",
            "id": "pyup.io-39341",
            "more_info_path": "/vulnerabilities/PVE-2021-39341/39341",
            "specs": [
                "<3.4.1"
            ],
            "v": "<3.4.1"
        },
        {
            "advisory": "Privacyidea 3.6 includes more secure configuration defaults.\r\nhttps://github.com/privacyidea/privacyidea/issues/2408",
            "cve": "PVE-2021-40970",
            "id": "pyup.io-40970",
            "more_info_path": "/vulnerabilities/PVE-2021-40970/40970",
            "specs": [
                "<3.6"
            ],
            "v": "<3.6"
        },
        {
            "advisory": "Privacyidea 3.7dev4 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-24303",
            "id": "pyup.io-47855",
            "more_info_path": "/vulnerabilities/CVE-2022-24303/47855",
            "specs": [
                "<3.7dev4"
            ],
            "v": "<3.7dev4"
        },
        {
            "advisory": "Privacyidea 3.9 includes a fix for a Use of Cryptographically Weak Pseudo-Random Number Generator vulnerability.\r\nhttps://github.com/privacyidea/privacyidea/pull/3649",
            "cve": "PVE-2023-61122",
            "id": "pyup.io-61122",
            "more_info_path": "/vulnerabilities/PVE-2023-61122/61122",
            "specs": [
                "<3.9"
            ],
            "v": "<3.9"
        },
        {
            "advisory": "privacyIDEA version 2.23.1 and earlier contains a Improper Input Validation vulnerability in token validation api that can result in Denial-of-Service. This attack appear to be exploitable via http request with user=&pass= to /validate/check url. This vulnerability appears to have been fixed in 2.23.2.",
            "cve": "CVE-2018-1000809",
            "id": "pyup.io-53988",
            "more_info_path": "/vulnerabilities/CVE-2018-1000809/53988",
            "specs": [
                ">=0,<2.23.2"
            ],
            "v": ">=0,<2.23.2"
        }
    ],
    "procrastinate": [
        {
            "advisory": "Procrastinate 0.11.0 addresses a database race condition vulnerability, where tasks with identical locks were executed in an incorrect sequence. It poses a risk in scenarios requiring strict task execution orders, potentially leading to data inconsistencies and operational disruptions. \r\nhttps://github.com/procrastinate-org/procrastinate/issues/212\r\nhttps://github.com/procrastinate-org/procrastinate/pull/231",
            "cve": "PVE-2024-63785",
            "id": "pyup.io-63785",
            "more_info_path": "/vulnerabilities/PVE-2024-63785/63785",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        },
        {
            "advisory": "Procrastinate 0.3.0 resolves a database race condition, where jobs with the same lock executed simultaneously led to order discrepancies. It introduces crucial changes to how locks are handled, ensuring consistent execution order of tasks. \r\nhttps://github.com/procrastinate-org/procrastinate/issues/103\r\nhttps://github.com/procrastinate-org/procrastinate/pull/104/",
            "cve": "PVE-2024-63786",
            "id": "pyup.io-63786",
            "more_info_path": "/vulnerabilities/PVE-2024-63786/63786",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "products-atcontenttypes": [
        {
            "advisory": "Products.atcontenttypes 0.2 fixes security of HistoryAwareMixin.",
            "cve": "PVE-2022-48116",
            "id": "pyup.io-48116",
            "more_info_path": "/vulnerabilities/PVE-2022-48116/48116",
            "specs": [
                "<0.2"
            ],
            "v": "<0.2"
        },
        {
            "advisory": "Products.atcontenttypes 1.2.0 fixes a wrong permissions vulnerability.\r\nhttps://github.com/plone/Products.ATContentTypes/commit/ab2ca8a377aeaac7d37acff05e64b4ca26b82663",
            "cve": "PVE-2017-47382",
            "id": "pyup.io-47382",
            "more_info_path": "/vulnerabilities/PVE-2017-47382/47382",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        },
        {
            "advisory": "Products.atcontenttypes 1.2.0 corrects wrong security settings.\r\nhttps://github.com/plone/Products.ATContentTypes/commit/99ec55c2a07a6cec8fa9b6b00e7e078c088ddbce",
            "cve": "PVE-2017-47381",
            "id": "pyup.io-47381",
            "more_info_path": "/vulnerabilities/PVE-2017-47381/47381",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        },
        {
            "advisory": "Products-atcontenttypes 2.1.10 makes sure ATTopic.queryCatalog cannot be published to fix CVE-2012-5498.",
            "cve": "CVE-2012-5498",
            "id": "pyup.io-47383",
            "more_info_path": "/vulnerabilities/CVE-2012-5498/47383",
            "specs": [
                "<2.1.10"
            ],
            "v": "<2.1.10"
        },
        {
            "advisory": "Products.ATContentTypes are the core content types for Plone 2.1 - 4.3. Versions of Plone that are dependent on Products.ATContentTypes prior to version 3.0.6 are vulnerable to reflected cross site scripting and open redirect when an attacker can get a compromised version of the image_view_fullscreen page in a cache, for example in Varnish. The technique is known as cache poisoning. Any later visitor can get redirected when clicking on a link on this page. Usually only anonymous users are affected, but this depends on the user's cache settings. Version 3.0.6 of Products.ATContentTypes has been released with a fix. This version works on Plone 5.2, Python 2 only. As a workaround, make sure the image_view_fullscreen page is not stored in the cache. More information about the vulnerability and cvmitigation measures is available in the GitHub Security Advisory.",
            "cve": "CVE-2022-23599",
            "id": "pyup.io-47384",
            "more_info_path": "/vulnerabilities/CVE-2022-23599/47384",
            "specs": [
                "<3.0.6"
            ],
            "v": "<3.0.6"
        }
    ],
    "products-btreefolder2": [
        {
            "advisory": "Products-btreefolder2 version 2.13.4 includes a security declaration for 'BTreeFolder2Base.hasObject' method.",
            "cve": "PVE-2021-42029",
            "id": "pyup.io-42029",
            "more_info_path": "/vulnerabilities/PVE-2021-42029/42029",
            "specs": [
                "<2.13.4"
            ],
            "v": "<2.13.4"
        }
    ],
    "products-cmfcontentpanels": [
        {
            "advisory": "products.cmfcontentpanels before 1.4.1 has two not disclosed security issues.",
            "cve": "PVE-2021-26020",
            "id": "pyup.io-26020",
            "more_info_path": "/vulnerabilities/PVE-2021-26020/26020",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        }
    ],
    "products-cmfcore": [
        {
            "advisory": "Products.cmfcore before 2.1.0beta2 has a vulnerability because it includes the Zope dependency version <2.10.2, which has an injection vulnerability. See: CVE-2007-0240.",
            "cve": "CVE-2007-0240",
            "id": "pyup.io-35820",
            "more_info_path": "/vulnerabilities/CVE-2007-0240/35820",
            "specs": [
                "<2.1.0beta2"
            ],
            "v": "<2.1.0beta2"
        },
        {
            "advisory": "Products.cmfcore 2.3.0beta tightens the security for anonymous test user.",
            "cve": "PVE-2021-35818",
            "id": "pyup.io-35818",
            "more_info_path": "/vulnerabilities/PVE-2021-35818/35818",
            "specs": [
                "<2.3.0beta"
            ],
            "v": "<2.3.0beta"
        }
    ],
    "products-cmfdifftool": [
        {
            "advisory": "Products.cmfdifftool 3.3.3 includes a fix for a XSS vulnerability.\r\nhttps://plone.org/security/hotfix/20210518/xss-vulnerability-in-cmfdifftool",
            "cve": "PVE-2017-47577",
            "id": "pyup.io-47577",
            "more_info_path": "/vulnerabilities/PVE-2017-47577/47577",
            "specs": [
                "<3.3.3"
            ],
            "v": "<3.3.3"
        }
    ],
    "products-cmfformcontroller": [
        {
            "advisory": "Products.cmfformcontroller 3.1.3 applies security hotfix 20160830 for redirect_to. This action refuses to redirect to unknown external sites.\r\nhttps://plone.org/security/hotfix/20160830/open-redirection-in-plone",
            "cve": "CVE-2016-7137",
            "id": "pyup.io-47222",
            "more_info_path": "/vulnerabilities/CVE-2016-7137/47222",
            "specs": [
                "<3.1.3"
            ],
            "v": "<3.1.3"
        }
    ],
    "products-cmfplomino": [
        {
            "advisory": "Products.cmfplomino 1.13.1 escapes usernames and passwords to avoid injection attacks.\r\nhttps://github.com/plomino/Plomino/commit/2bde844b94b019d0938e43e3123540a10fd7bd60",
            "cve": "PVE-2017-47686",
            "id": "pyup.io-47686",
            "more_info_path": "/vulnerabilities/PVE-2017-47686/47686",
            "specs": [
                "<1.13.1"
            ],
            "v": "<1.13.1"
        },
        {
            "advisory": "Products.cmfplomino 1.18 doesn't allows to access anything with open_url unless the requested domain is declared by a IPlominoSafeDomains utility.\r\nhttps://github.com/plomino/Plomino/commit/e19415606762370337dfafd7752dba8d685e87a3",
            "cve": "PVE-2017-47684",
            "id": "pyup.io-47684",
            "more_info_path": "/vulnerabilities/PVE-2017-47684/47684",
            "specs": [
                "<1.18"
            ],
            "v": "<1.18"
        }
    ],
    "products-cmfplone": [
        {
            "advisory": "Products-cmfplone 4.3.10 and 5.0.5 include a minor fix for an information disclosure vulnerability.\r\nhttps://plone.org/news-and-events/news/2016/minor-plone-security-fixes",
            "cve": "PVE-2023-53489",
            "id": "pyup.io-53489",
            "more_info_path": "/vulnerabilities/PVE-2023-53489/53489",
            "specs": [
                "<4.3.10",
                ">=5.0a1,<5.0.5"
            ],
            "v": "<4.3.10,>=5.0a1,<5.0.5"
        },
        {
            "advisory": "Products.cmfplone versions 4.3.20, 5.1.7, 5.2.5 and 6.0.0a1.dev0 include a fix for CVE-2020-7940: Missing password strength checks on some forms in Plone 4.3 through 5.2.0 allow users to set weak passwords, leading to easier cracking.",
            "cve": "CVE-2020-7940",
            "id": "pyup.io-41959",
            "more_info_path": "/vulnerabilities/CVE-2020-7940/41959",
            "specs": [
                "<4.3.20",
                ">=5.0a1,<5.1.7",
                ">=5.2a1,<5.2.5"
            ],
            "v": "<4.3.20,>=5.0a1,<5.1.7,>=5.2a1,<5.2.5"
        },
        {
            "advisory": "Products.cmfplone versions 4.3.20, 5.1.7, 5.2.5 and 6.0.0a1.dev0 include a fix for CVE-2020-7936: An open redirect on the login form (and possibly other places) in Plone 4.0 through 5.2.1 allows an attacker to craft a link to a Plone Site that, when followed, and possibly after login, will redirect to an attacker's site.",
            "cve": "CVE-2020-7936",
            "id": "pyup.io-41842",
            "more_info_path": "/vulnerabilities/CVE-2020-7936/41842",
            "specs": [
                "<4.3.20",
                ">=5.0a1,<5.1.7",
                ">=5.2a1,<5.2.5"
            ],
            "v": "<4.3.20,>=5.0a1,<5.1.7,>=5.2a1,<5.2.5"
        },
        {
            "advisory": "Plone is exposed to risks associated with reflected cross-site scripting and open redirect. These vulnerabilities can occur when an attacker manages to put a compromised version of the image_view_fullscreen page into a cache, such as Varnish.",
            "cve": "PVE-2023-99928",
            "id": "pyup.io-61946",
            "more_info_path": "/vulnerabilities/PVE-2023-99928/61946",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "Products.ATContentTypes are the core content types for Plone 2.1 - 4.3. Versions of Plone that are dependent on Products.ATContentTypes prior to version 3.0.6 are vulnerable to reflected cross site scripting and open redirect when an attacker can get a compromised version of the image_view_fullscreen page in a cache, for example in Varnish. The technique is known as cache poisoning. Any later visitor can get redirected when clicking on a link on this page. Usually only anonymous users are affected, but this depends on the user's cache settings. Version 3.0.6 of Products.ATContentTypes has been released with a fix. This version works on Plone 5.2, Python 2 only. As a workaround, make sure the image_view_fullscreen page is not stored in the cache. More information about the vulnerability and cvmitigation measures is available in the GitHub Security Advisory.",
            "cve": "CVE-2022-23599",
            "id": "pyup.io-53491",
            "more_info_path": "/vulnerabilities/CVE-2022-23599/53491",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "Several cross-site request forgery vulnerabilities have been identified in the Zope Management Interface.",
            "cve": "PVE-2023-99916",
            "id": "pyup.io-62005",
            "more_info_path": "/vulnerabilities/PVE-2023-99916/62005",
            "specs": [
                "<5.0a"
            ],
            "v": "<5.0a"
        },
        {
            "advisory": "In Products.CMFPlone before 5.1b1, it's possible to access private content via str.format in through-the-web templates and scripts.",
            "cve": "CVE-2017-1000483",
            "id": "pyup.io-32997",
            "more_info_path": "/vulnerabilities/CVE-2017-1000483/32997",
            "specs": [
                "<5.1b1"
            ],
            "v": "<5.1b1"
        },
        {
            "advisory": "Products.cmfplone 5.2.5 includes a fix for CVE-2021-32633, vulnerability that affected 'Zope' dependency.",
            "cve": "CVE-2021-32633",
            "id": "pyup.io-41960",
            "more_info_path": "/vulnerabilities/CVE-2021-32633/41960",
            "specs": [
                "<5.2.5"
            ],
            "v": "<5.2.5"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in Plone 3.3.0 through 3.3.6, 4.0.0 through 4.0.10, 4.1.0 through 4.1.6, 4.2.0 through 4.2.7, 4.3.x before 4.3.7, and 5.0rc1.",
            "cve": "CVE-2015-7316",
            "id": "pyup.io-53488",
            "more_info_path": "/vulnerabilities/CVE-2015-7316/53488",
            "specs": [
                "<=3.3.6",
                ">=4.0a1,<=4.0.10",
                ">=4.1a1,<=4.1.6",
                ">=4.2a1,<=4.2.7",
                ">=4.3a1,<4.3.7"
            ],
            "v": "<=3.3.6,>=4.0a1,<=4.0.10,>=4.1a1,<=4.1.6,>=4.2a1,<=4.2.7,>=4.3a1,<4.3.7"
        },
        {
            "advisory": "Products.cmfplone versions 5.2.5 and 6.0.0a1.dev0 integrates a fix for CVE-2021-33507: Zope Products.CMFCore before 2.5.1 and Products.PluggableAuthService before 2.6.2, as used in Plone through 5.2.4 and other products, allow Reflected XSS.\r\nhttps://plone.org/security/hotfix/20210518/reflected-xss-in-various-spots",
            "cve": "CVE-2021-33507",
            "id": "pyup.io-41961",
            "more_info_path": "/vulnerabilities/CVE-2021-33507/41961",
            "specs": [
                ">5.2.5,<6.0.0a1.dev0",
                "<5.2.5"
            ],
            "v": ">5.2.5,<6.0.0a1.dev0,<5.2.5"
        },
        {
            "advisory": "Products-cmfplone 4.3.3 includes a fix for CVE-2013-7061: Products/CMFPlone/CatalogTool.py in Plone 3.3 through 4.3.2 allows remote administrators to bypass restrictions and obtain sensitive information via an unspecified search API.",
            "cve": "CVE-2013-7061",
            "id": "pyup.io-53486",
            "more_info_path": "/vulnerabilities/CVE-2013-7061/53486",
            "specs": [
                ">=3.3,<4.3.2"
            ],
            "v": ">=3.3,<4.3.2"
        },
        {
            "advisory": "Products/CMFPlone/FactoryTool.py in Plone 3.3 through 4.3.2 allows remote attackers to obtain the installation path via vectors related to a file object for unspecified documentation which is initialized in class scope.",
            "cve": "CVE-2013-7060",
            "id": "pyup.io-53487",
            "more_info_path": "/vulnerabilities/CVE-2013-7060/53487",
            "specs": [
                ">=3.3,<=4.3.2"
            ],
            "v": ">=3.3,<=4.3.2"
        },
        {
            "advisory": "Products-cmfplone 5.0.5 includes a minor fix for a XSS vulnerability in any field that uses the select2 pattern.\r\nhttps://plone.org/news-and-events/news/2016/minor-plone-security-fixes",
            "cve": "PVE-2023-53490",
            "id": "pyup.io-53490",
            "more_info_path": "/vulnerabilities/PVE-2023-53490/53490",
            "specs": [
                ">=5.0a1,<5.0.5"
            ],
            "v": ">=5.0a1,<5.0.5"
        }
    ],
    "products-cmfquickinstallertool": [
        {
            "advisory": "Products.cmfquickinstallertool before 3.0.14 is vulnerable to several cross site scripting (XSS) attacks.\r\nhttps://github.com/plone/Products.CMFQuickInstallerTool/commit/1cd430b74353ac023493e2dd19613a2e390c451d",
            "cve": "CVE-2016-7138",
            "id": "pyup.io-26021",
            "more_info_path": "/vulnerabilities/CVE-2016-7138/26021",
            "specs": [
                "<3.0.14"
            ],
            "v": "<3.0.14"
        }
    ],
    "products-cmfuid": [
        {
            "advisory": "Products.cmfuid before 2.1.0beta2 has a vulnerability because it includes the Zope dependency version <2.10.2, which has an injection vulnerability. See: CVE-2007-0240.",
            "cve": "CVE-2007-0240",
            "id": "pyup.io-36300",
            "more_info_path": "/vulnerabilities/CVE-2007-0240/36300",
            "specs": [
                "<2.1.0beta2"
            ],
            "v": "<2.1.0beta2"
        }
    ],
    "products-dcworkflow": [
        {
            "advisory": "Products.dcworkflow before 2.1.0beta2 has a vulnerability because it includes the Zope dependency version <2.10.2, which has an injection vulnerability. See: CVE-2007-0240.",
            "cve": "CVE-2007-0240",
            "id": "pyup.io-38035",
            "more_info_path": "/vulnerabilities/CVE-2007-0240/38035",
            "specs": [
                "<2.1.0beta2"
            ],
            "v": "<2.1.0beta2"
        }
    ],
    "products-genericsetup": [
        {
            "advisory": "Products.genericsetup 2.1.1 includes a fix for CVE-2021-21360: Products.GenericSetup is a mini-framework for expressing the configured state of a Zope Site as a set of filesystem artifacts. In Products.GenericSetup before version 2.1.1 there is an information disclosure vulnerability - anonymous visitors may view log and snapshot files generated by the Generic Setup Tool. Depending on how you have installed Products.GenericSetup, you should change the buildout version pin to 2.1.1 and re-run the buildout, or if you used pip simply do pip install \"Products.GenericSetup>=2.1.1\".\r\nhttps://github.com/zopefoundation/Products.GenericSetup/security/advisories/GHSA-jff3-mwp3-f8cw",
            "cve": "CVE-2021-21360",
            "id": "pyup.io-39685",
            "more_info_path": "/vulnerabilities/CVE-2021-21360/39685",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        }
    ],
    "products-isurlinportal": [
        {
            "advisory": "Products.isurlinportal version 1.2.0 includes a fix for CVE-2021-32806: Versions of products.isurlinportal prior to 1.2.0 have an open redirect vulnerability. Various parts of Plone use the 'is url in portal' check for security, mostly to see if it is safe to redirect to a url. A url like \"https://example.org\" is not in the portal. The url \"https:example.org\" without slashes is considered to be in the portal. When redirecting, some browsers go to \"https://example.org\", others give an error.\r\nAttackers may use this to redirect victims to their site, especially as part of a phishing attack.\r\nhttps://github.com/plone/Products.isurlinportal/security/advisories/GHSA-q3m9-9fj2-mfwr\r\nhttps://github.com/plone/Products.isurlinportal/commit/d4fd34990d18adf05a10dc5e2bb4b066798280ba",
            "cve": "CVE-2021-32806",
            "id": "pyup.io-41068",
            "more_info_path": "/vulnerabilities/CVE-2021-32806/41068",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "products-ldapuserfolder": [
        {
            "advisory": "The authenticate function in LDAPUserFolder/LDAPUserFolder.py in zope-ldapuserfolder 2.9-1 does not verify the password for the emergency account, which allows remote attackers to gain privileges.",
            "cve": "PVE-2021-33148",
            "id": "pyup.io-33148",
            "more_info_path": "/vulnerabilities/PVE-2021-33148/33148",
            "specs": [
                "<2.19"
            ],
            "v": "<2.19"
        },
        {
            "advisory": "Products.ldapuserfolder version 2.20 includes a fix for CVE-2010-2944: The authenticate function in LDAPUserFolder/LDAPUserFolder.py in zope-ldapuserfolder 2.9-1 does not verify the password for the emergency account, which allows remote attackers to gain privileges.\r\nhttps://github.com/dataflake/Products.LDAPUserFolder/commit/246257dbe5f73a6fd3c3e597814038977004cdd7",
            "cve": "CVE-2010-2944",
            "id": "pyup.io-26023",
            "more_info_path": "/vulnerabilities/CVE-2010-2944/26023",
            "specs": [
                "<2.20"
            ],
            "v": "<2.20"
        },
        {
            "advisory": "Products.ldapuserfolder 2.24 changes to a more secure behavior of LDAPDelegate. When using a user from the Zope security machinery for the purpose of finding a suitable bind DN and password for connecting to a LDAP server, discard it when it's not been created as the result of a real login and thus has an invalid password.\r\nhttps://bugs.launchpad.net/bugs/1060112",
            "cve": "PVE-2022-45134",
            "id": "pyup.io-45134",
            "more_info_path": "/vulnerabilities/PVE-2022-45134/45134",
            "specs": [
                "<2.24"
            ],
            "v": "<2.24"
        }
    ],
    "products-linguaplone": [
        {
            "advisory": "Products.linguaplone 4.0 fixes a possible XSS security issue in the 'translationbrowser_popup' caused by displaying unfiltered content from the 'Description' string field as HTML.",
            "cve": "PVE-2017-47611",
            "id": "pyup.io-47611",
            "more_info_path": "/vulnerabilities/PVE-2017-47611/47611",
            "specs": [
                "<4.0"
            ],
            "v": "<4.0"
        }
    ],
    "products-passwordresettool": [
        {
            "advisory": "Products-passwordresettool 2.0.10 uses system random when available to fix CVE-2012-5508.",
            "cve": "CVE-2012-5508",
            "id": "pyup.io-47260",
            "more_info_path": "/vulnerabilities/CVE-2012-5508/47260",
            "specs": [
                "<2.0.10"
            ],
            "v": "<2.0.10"
        },
        {
            "advisory": "Products-passwordresettool 2.0.6 includes a security fix for a XSS vulnerability, CVE-2011-1948.",
            "cve": "CVE-2011-1948",
            "id": "pyup.io-47259",
            "more_info_path": "/vulnerabilities/CVE-2011-1948/47259",
            "specs": [
                "<2.0.6"
            ],
            "v": "<2.0.6"
        }
    ],
    "products-ploneformgen": [
        {
            "advisory": "Products.ploneformgen 1.7.19 and 1.8.1 include a fix for a XSS vulnerability that could be exploited by users with the ability to create forms.\r\nhttps://github.com/smcmahon/Products.PloneFormGen/commit/b9590e5573660ee6b8d151430ca2b459f05388ca",
            "cve": "PVE-2021-26024",
            "id": "pyup.io-26024",
            "more_info_path": "/vulnerabilities/PVE-2021-26024/26024",
            "specs": [
                "<1.7.19",
                ">=1.8.0.alpha1,<1.8.1"
            ],
            "v": "<1.7.19,>=1.8.0.alpha1,<1.8.1"
        },
        {
            "advisory": "Products-ploneformgen 1.7.19 and 1.8.1 include a fix for a XSS vulnerability that could be exploited by users with the ability to create forms.\r\nhttps://github.com/smcmahon/Products.PloneFormGen/commit/b9590e5573660ee6b8d151430ca2b459f05388ca",
            "cve": "PVE-2021-35878",
            "id": "pyup.io-35878",
            "more_info_path": "/vulnerabilities/PVE-2021-35878/35878",
            "specs": [
                "<1.8.1"
            ],
            "v": "<1.8.1"
        }
    ],
    "products-plonepas": [
        {
            "advisory": "Products-plonepas 3.9 fixes the cookie plugin's login handler to not trust the username from the request. Instead, now it's used the login name of the currently authenticated user. This fixes CVE-2009-0662.",
            "cve": "CVE-2009-0662",
            "id": "pyup.io-35982",
            "more_info_path": "/vulnerabilities/CVE-2009-0662/35982",
            "specs": [
                "<3.9"
            ],
            "v": "<3.9"
        },
        {
            "advisory": "Products.plonepas 4.0.6 fixes missing and broken security declarations.\r\nhttps://github.com/plone/Products.PlonePAS/commit/4ceb5c38671eac9e32e19743ec377870aa153c7b",
            "cve": "PVE-2022-48151",
            "id": "pyup.io-48151",
            "more_info_path": "/vulnerabilities/PVE-2022-48151/48151",
            "specs": [
                "<4.0.6"
            ],
            "v": "<4.0.6"
        },
        {
            "advisory": "Products.plonepas 5.0.5 includes a fix for an unauthorized disclosure of registered user information vulnerability.\r\nhttps://plone.org/security/hotfix/20151208/unauthorized-disclosure-of-registered-user-information",
            "cve": "PVE-2022-48150",
            "id": "pyup.io-48150",
            "more_info_path": "/vulnerabilities/PVE-2022-48150/48150",
            "specs": [
                "<5.0.5"
            ],
            "v": "<5.0.5"
        },
        {
            "advisory": "Products.plonepas 6.0.0 reports home_page as empty when it is suspicious to fix CVE-2017-1000482.\r\nhttps://plone.org/security/hotfix/20171128/xss-using-the-home_page-member-property",
            "cve": "CVE-2017-1000482",
            "id": "pyup.io-47249",
            "more_info_path": "/vulnerabilities/CVE-2017-1000482/47249",
            "specs": [
                "<6.0.0"
            ],
            "v": "<6.0.0"
        }
    ],
    "products-pluggableauthservice": [
        {
            "advisory": "Products.PluggableAuthService 2.6.0 includes a fix for CVE-2021-21336: In Products.PluggableAuthService before version 2.6.0 there is an information disclosure vulnerability - everyone can list the names of roles defined in the ZODB Role Manager plugin if the site uses this plugin.",
            "cve": "CVE-2021-21336",
            "id": "pyup.io-39681",
            "more_info_path": "/vulnerabilities/CVE-2021-21336/39681",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Products.pluggableauthservice 2.6.1 includes a fix for CVE-2021-21337: In Products.PluggableAuthService before version 2.6.1 there is an open redirect vulnerability. A maliciously crafted link to the login form and login functionality could redirect the browser to a different website. Depending on how you have installed Products.PluggableAuthService, you should change the buildout version pin to '2.6.1' and re-run the buildout, or if you used 'pip' simply do 'pip install \"Products.PluggableAuthService>=2.6.1\"'.\r\nhttps://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p44j-xrqg-4xrr",
            "cve": "CVE-2021-21337",
            "id": "pyup.io-39682",
            "more_info_path": "/vulnerabilities/CVE-2021-21337/39682",
            "specs": [
                "<2.6.1"
            ],
            "v": "<2.6.1"
        },
        {
            "advisory": "Zope Products.CMFCore before 2.5.1 and Products.PluggableAuthService before 2.6.2, as used in Plone through 5.2.4 and other products, allow Reflected XSS.",
            "cve": "CVE-2021-33507",
            "id": "pyup.io-39695",
            "more_info_path": "/vulnerabilities/CVE-2021-33507/39695",
            "specs": [
                "<2.6.2"
            ],
            "v": "<2.6.2"
        },
        {
            "advisory": "Products.pluggableauthservice 2.6.3 fixes CSRF token access for tigher TAL path expression security in Zope 5.2.1.",
            "cve": "PVE-2021-40631",
            "id": "pyup.io-40631",
            "more_info_path": "/vulnerabilities/PVE-2021-40631/40631",
            "specs": [
                "<2.6.3"
            ],
            "v": "<2.6.3"
        }
    ],
    "products-poi": [
        {
            "advisory": "products.poi before 2.2.3 allows anonymous users to see issues inside private folders.",
            "cve": "PVE-2021-26027",
            "id": "pyup.io-26027",
            "more_info_path": "/vulnerabilities/PVE-2021-26027/26027",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        }
    ],
    "products-zopetree": [
        {
            "advisory": "Products-zopetree 1.3 fixes a security hole in the tree state decompressing mechanism. Previous versions were vulnerable to a denial of service attack using large tree states.",
            "cve": "PVE-2021-37726",
            "id": "pyup.io-37726",
            "more_info_path": "/vulnerabilities/PVE-2021-37726/37726",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        }
    ],
    "products-zopeversioncontrol": [
        {
            "advisory": "Products.zopeversioncontrol 1.1.3 adds missing security declarations.\r\nhttps://github.com/zopefoundation/Products.ZopeVersionControl/commit/4f862cbcd5fcf76b53c863fcedb1157a7af17720",
            "cve": "PVE-2022-50120",
            "id": "pyup.io-50120",
            "more_info_path": "/vulnerabilities/PVE-2022-50120/50120",
            "specs": [
                "<1.1.3"
            ],
            "v": "<1.1.3"
        }
    ],
    "products.cmfcore": [
        {
            "advisory": "Products.CMFCore 3.2 includes a fix for a denial of service vulnerability: The use of Python's marshal module to handle unchecked input in a public method on PortalFolder objects can lead to an unauthenticated denial of service and a crash situation.\r\nhttps://github.com/zopefoundation/Products.CMFCore/security/advisories/GHSA-4hpj-8rhv-9x87\r\nhttps://github.com/zopefoundation/Products.CMFCore/commit/40f03f43a60f28ca9485c8ef429efef729be54e5",
            "cve": "CVE-2023-36814",
            "id": "pyup.io-59295",
            "more_info_path": "/vulnerabilities/CVE-2023-36814/59295",
            "specs": [
                "<3.2"
            ],
            "v": "<3.2"
        }
    ],
    "products.cmfdifftool": [
        {
            "advisory": "Products.cmfdifftool 3.3.3 includes a fix for a XSS vulnerability.\r\nhttps://plone.org/security/hotfix/20210518/xss-vulnerability-in-cmfdifftool",
            "cve": "CVE-2021-33513",
            "id": "pyup.io-53661",
            "more_info_path": "/vulnerabilities/CVE-2021-33513/53661",
            "specs": [
                "<3.3.3"
            ],
            "v": "<3.3.3"
        }
    ],
    "products.formulator": [
        {
            "advisory": "Products.formulator 0.9.2 adds missing security declarations.",
            "cve": "PVE-2022-49453",
            "id": "pyup.io-49453",
            "more_info_path": "/vulnerabilities/PVE-2022-49453/49453",
            "specs": [
                "<0.9.2"
            ],
            "v": "<0.9.2"
        }
    ],
    "products.pluggableauthservice": [
        {
            "advisory": "Affected versions of this package are vulnerable to Session Fixation. The session authentication helper fails to clear session data during login by default, leading to attackers being able to hijack user sessions by forcing victims to authenticate with a pre-established session identifier.",
            "cve": "PVE-2025-81661",
            "id": "pyup.io-81661",
            "more_info_path": "/vulnerabilities/PVE-2025-81661/81661",
            "specs": [
                "<4.0"
            ],
            "v": "<4.0"
        }
    ],
    "products.sqlalchemyda": [
        {
            "advisory": "SQLAlchemyDA is a generic database adapter for ZSQL methods. A vulnerability found in versions prior to 2.2 allows unauthenticated execution of arbitrary SQL statements on the database to which the SQLAlchemyDA instance is connected. All users are affected. The problem has been patched in version 2.2. There is no workaround for the problem. See CVE-2024-24811.",
            "cve": "CVE-2024-24811",
            "id": "pyup.io-65295",
            "more_info_path": "/vulnerabilities/CVE-2024-24811/65295",
            "specs": [
                "<2.2"
            ],
            "v": "<2.2"
        }
    ],
    "project-lighter": [
        {
            "advisory": "Project-lighter 0.0.2 updates its dependency 'jinja2' to v3.1.3 to include a security fix.",
            "cve": "CVE-2024-22195",
            "id": "pyup.io-71756",
            "more_info_path": "/vulnerabilities/CVE-2024-22195/71756",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        }
    ],
    "project-manager": [
        {
            "advisory": "Project-Manager version 0.2.0 includes a fix for the function 'load_config' in 'project_manager/utils.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/kpj/project_manager/commit/07aef0e023f07563ae9141674e1de3508e178358#diff-03ec8dd0ad6683512ebfb1545fbf01618075f2118c80cc4878cd76ff5bf26aeb",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41371",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41371",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        },
        {
            "advisory": "Project-manager 0.2.0 and prior uses yaml.full_load(), which is vulnerable to CVE-2020-14343.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-41756",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/41756",
            "specs": [
                "<=0.2.0"
            ],
            "v": "<=0.2.0"
        }
    ],
    "projen": [
        {
            "advisory": "Projen 0.3.1 addresses a security issue with its NPM dependency 'standard-version' v8.0.1.\r\nhttps://github.com/projen/projen/commit/722ed05ace94270bff0cb93a38948c1a2c7c9142\r\nhttps://github.com/conventional-changelog/standard-version/security/advisories/GHSA-7xcx-6wjh-7xp2",
            "cve": "PVE-2021-39416",
            "id": "pyup.io-39416",
            "more_info_path": "/vulnerabilities/PVE-2021-39416/39416",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Projen 0.36.4 updates its dependency 'eslint' and '8' to fix a ReDoS vulnerability.\r\nhttps://github.com/projen/projen/pull/1281\r\nhttps://github.com/projen/projen/commit/231e6af1077a29942e7bbd721498021df6f58185\r\nhttps://github.com/advisories/GHSA-93q8-gq69-wqmw",
            "cve": "CVE-2021-3807",
            "id": "pyup.io-59359",
            "more_info_path": "/vulnerabilities/CVE-2021-3807/59359",
            "specs": [
                "<0.36.4"
            ],
            "v": "<0.36.4"
        },
        {
            "advisory": "`projen` is a project generation tool that synthesizes project configuration files such as `package.json`, `tsconfig.json`, `.gitignore`, GitHub Workflows, `eslint`, `jest`, and more, from a well-typed definition written in JavaScript. Users of projen's `NodeProject` project type (including any project type derived from it) include a `.github/workflows/rebuild-bot.yml` workflow that may allow any GitHub user to trigger execution of un-trusted code in the context of the main repository (as opposed to that of a fork). In some situations, such untrusted code may potentially be able to commit to the main repository. The rebuild-bot workflow is triggered by comments including `@projen rebuild` on pull-request to trigger a re-build of the projen project, and updating the pull request with the updated files. This workflow is triggered by an `issue_comment` event, and thus always executes with a `GITHUB_TOKEN` belonging to the repository into which the pull-request is made (this is in contrast with workflows triggered by `pull_request` events, which always execute with a `GITHUB_TOKEN` belonging to the repository from which the pull-request is made). Repositories that do not have branch protection configured on their default branch (typically `main` or `master`) could possibly allow an untrusted user to gain access to secrets configured on the repository (such as NPM tokens, etc). Branch protection prohibits this escalation, as the managed `GITHUB_TOKEN` would not be able to modify the contents of a protected branch and affected workflows must be defined on the default branch.",
            "cve": "CVE-2021-21423",
            "id": "pyup.io-54303",
            "more_info_path": "/vulnerabilities/CVE-2021-21423/54303",
            "specs": [
                ">=0,<0.16.41"
            ],
            "v": ">=0,<0.16.41"
        }
    ],
    "prometheus-pve-sd": [
        {
            "advisory": "Prometheus-pve-sd 2.5.18 updates its dependency 'requests' to v2.31.0 to include a security fix.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-58830",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/58830",
            "specs": [
                "<2.5.18"
            ],
            "v": "<2.5.18"
        }
    ],
    "prompt-toolkit": [
        {
            "advisory": "Prompt-toolkit 3.0.13 fixes a race condition in `ThreadedHistory` which could lead to a deadlock. \r\nhttps://github.com/prompt-toolkit/python-prompt-toolkit/commit/99092a8c6d4b411645ac4b84d504e5226e7eebb8#diff-48c0ff10dc3990285d19b3f54e6bfec763089ba1229dc6f9e88463a1046adad7R163",
            "cve": "PVE-2023-62817",
            "id": "pyup.io-62817",
            "more_info_path": "/vulnerabilities/PVE-2023-62817/62817",
            "specs": [
                "<3.0.13"
            ],
            "v": "<3.0.13"
        }
    ],
    "promptflow-core": [
        {
            "advisory": "Improper isolation or compartmentalization in Azure PromptFlow allows an unauthorized attacker to execute code over a network.",
            "cve": "CVE-2025-24986",
            "id": "pyup.io-76314",
            "more_info_path": "/vulnerabilities/CVE-2025-24986/76314",
            "specs": [
                "<1.17.2"
            ],
            "v": "<1.17.2"
        }
    ],
    "promptflow-tools": [
        {
            "advisory": "Improper isolation or compartmentalization in Azure PromptFlow allows an unauthorized attacker to execute code over a network.",
            "cve": "CVE-2025-24986",
            "id": "pyup.io-76313",
            "more_info_path": "/vulnerabilities/CVE-2025-24986/76313",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        }
    ],
    "promptfoo": [
        {
            "advisory": "Affected versions of this package are vulnerable to information disclosure due to improper handling of target output settings. The vulnerability exists because the `excludeTargetOutputFromAgenticAttackGeneration` setting was not respected in certain strategies, leading to potential leaks of target output when organization privacy settings are enabled. An attacker could exploit this vulnerability to access sensitive target output data that should have been excluded, potentially leading to unauthorized information disclosure.",
            "cve": "PVE-2026-83889",
            "id": "pyup.io-83889",
            "more_info_path": "/vulnerabilities/PVE-2026-83889/83889",
            "specs": [
                "<0.119.11"
            ],
            "v": "<0.119.11"
        }
    ],
    "promql-http-api": [
        {
            "advisory": "Promql-http-api 0.3.1 updates its dependency 'certifi' to version '2023.7.22' to include a fix for a Improper Following of a Certificate's Chain of Trust vulnerability.\r\nhttps://github.com/nir-arad/promql-http-api/commit/c02b5c36478fef347de8ac9f954e5d22257565bb",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60282",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60282",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "prosper-api": [
        {
            "advisory": "Prosper-api 0.6.7 updates its dependency 'cryptography' to v41.0.7 to include a security fix.",
            "cve": "CVE-2023-49083",
            "id": "pyup.io-62540",
            "more_info_path": "/vulnerabilities/CVE-2023-49083/62540",
            "specs": [
                "<0.6.7"
            ],
            "v": "<0.6.7"
        }
    ],
    "prosper-bot": [
        {
            "advisory": "Prosper-bot 0.1.17 updates its dependency 'cryptography' to include a security fix.",
            "cve": "CVE-2023-49083",
            "id": "pyup.io-62581",
            "more_info_path": "/vulnerabilities/CVE-2023-49083/62581",
            "specs": [
                "<0.1.17"
            ],
            "v": "<0.1.17"
        }
    ],
    "proteus": [
        {
            "advisory": "An XML Entity Expansion (XEE) issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. An unauthenticated user can send a crafted XML-RPC message to consume all the resources of the server.",
            "cve": "CVE-2022-26662",
            "id": "pyup.io-54403",
            "more_info_path": "/vulnerabilities/CVE-2022-26662/54403",
            "specs": [
                ">=5.0.0,<5.0.12",
                ">=6.0.0,<6.0.5",
                ">=6.1.0,<6.2.2"
            ],
            "v": ">=5.0.0,<5.0.12,>=6.0.0,<6.0.5,>=6.1.0,<6.2.2"
        },
        {
            "advisory": "An XXE issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. An authenticated user can make the server parse a crafted XML SEPA file to access arbitrary files on the system.",
            "cve": "CVE-2022-26661",
            "id": "pyup.io-54405",
            "more_info_path": "/vulnerabilities/CVE-2022-26661/54405",
            "specs": [
                ">=5.0.0,<5.0.12",
                ">=6.0.0,<6.0.5",
                ">=6.1.0,<6.2.2"
            ],
            "v": ">=5.0.0,<5.0.12,>=6.0.0,<6.0.5,>=6.1.0,<6.2.2"
        }
    ],
    "protobuf": [
        {
            "advisory": "Protobuf 3.15.0 includes a fix for CVE-2021-22570: Nullptr dereference when a null char is present in a proto symbol. The symbol is parsed incorrectly, leading to an unchecked call into the proto file's name during generation of the resulting error message. Since the symbol is incorrectly parsed, the file is nullptr.",
            "cve": "CVE-2021-22570",
            "id": "pyup.io-50474",
            "more_info_path": "/vulnerabilities/CVE-2021-22570/50474",
            "specs": [
                "<3.15.0"
            ],
            "v": "<3.15.0"
        },
        {
            "advisory": "Protobuf 3.18.3, 3.19.5, 3.20.2 and 4.21.6 include a fix for CVE-2022-1941: A parsing vulnerability for the MessageSet type in the ProtocolBuffers versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 3.21.5 for protobuf-cpp, and versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 4.21.5 for protobuf-python can lead to out of memory failures. A specially crafted message with multiple key-value per elements creates parsing issues, and can lead to a Denial of Service against services receiving unsanitized input.\r\nhttps://github.com/protocolbuffers/protobuf/security/advisories/GHSA-8gq9-2x98-w8hf",
            "cve": "CVE-2022-1941",
            "id": "pyup.io-51167",
            "more_info_path": "/vulnerabilities/CVE-2022-1941/51167",
            "specs": [
                "<3.18.3",
                ">=3.19.0rc0,<3.19.5",
                ">=3.20.0rc0,<3.20.2",
                ">=4.0.0rc0,<4.21.6"
            ],
            "v": "<3.18.3,>=3.19.0rc0,<3.19.5,>=3.20.0rc0,<3.20.2,>=4.0.0rc0,<4.21.6"
        },
        {
            "advisory": "Protobuf 3.4.0 includes a fix for CVE-2015-5237: Integer overflow in serialization.\r\nhttps://github.com/protocolbuffers/protobuf/issues/760",
            "cve": "CVE-2015-5237",
            "id": "pyup.io-50475",
            "more_info_path": "/vulnerabilities/CVE-2015-5237/50475",
            "specs": [
                "<3.4.0"
            ],
            "v": "<3.4.0"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to a potential Denial of Service (DoS) attack due to unbounded recursion when parsing untrusted Protocol Buffers data. The pure-Python implementation fails to enforce recursion depth limits when processing recursive groups, recursive messages, or a series of SGROUP tags, leading to stack overflow conditions that can crash the application by exceeding Python's recursion limit.",
            "cve": "CVE-2025-4565",
            "id": "pyup.io-77740",
            "more_info_path": "/vulnerabilities/CVE-2025-4565/77740",
            "specs": [
                "<4.25.8",
                ">=5.26.0rc1,<5.29.5",
                ">=6.30.0rc1,<6.31.1"
            ],
            "v": "<4.25.8,>=5.26.0rc1,<5.29.5,>=6.30.0rc1,<6.31.1"
        },
        {
            "advisory": "Affected versions of the protobuf package are vulnerable to Denial of Service (DoS) due to missing recursion depth accounting that allows the max_recursion_depth limit to be bypassed. The google.protobuf.json_format.ParseDict() parser fails to increment or enforce max_recursion_depth when traversing nested google.protobuf.Any messages in its internal Any-handling logic, allowing attacker-controlled JSON to recurse far deeper than intended.",
            "cve": "CVE-2026-0994",
            "id": "pyup.io-85151",
            "more_info_path": "/vulnerabilities/CVE-2026-0994/85151",
            "specs": [
                "<=6.33.4"
            ],
            "v": "<=6.33.4"
        }
    ],
    "proxy-py": [
        {
            "advisory": "before_upstream_connection in AuthPlugin in http/proxy/auth.py in proxy.py before 2.3.1 accepts incorrect Proxy-Authorization header data because of a boolean confusion (and versus or).",
            "cve": "CVE-2021-3116",
            "id": "pyup.io-42312",
            "more_info_path": "/vulnerabilities/CVE-2021-3116/42312",
            "specs": [
                "<2.3.1"
            ],
            "v": "<2.3.1"
        }
    ],
    "proxy-randomizer": [
        {
            "advisory": "Proxy-randomizer 1.3.4 updates its dependency 'wheel' to v0.38.1 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-52630",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/52630",
            "specs": [
                "<1.3.4"
            ],
            "v": "<1.3.4"
        }
    ],
    "proxybooster": [
        {
            "advisory": "Proxybooster is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html",
            "cve": "PVE-2023-52922",
            "id": "pyup.io-52922",
            "more_info_path": "/vulnerabilities/PVE-2023-52922/52922",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "proxygeneratorbil": [
        {
            "advisory": "Proxygeneratorbil is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html",
            "cve": "PVE-2023-52911",
            "id": "pyup.io-52911",
            "more_info_path": "/vulnerabilities/PVE-2023-52911/52911",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "proxystore": [
        {
            "advisory": "Proxystore 0.4.1 updates its dependency 'cryptography' to include a security fix.",
            "cve": "CVE-2023-23931",
            "id": "pyup.io-61467",
            "more_info_path": "/vulnerabilities/CVE-2023-23931/61467",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        }
    ],
    "psd-tools": [
        {
            "advisory": "Security Fix for Psd-tools 1.10.6 | Security update to Pillow dependency to address potential vulnerabilities. Update to the Pillow image processing library dependency to address security concerns. No specific vulnerability details provided in changelog.",
            "cve": "PVE-2025-75611",
            "id": "pyup.io-75611",
            "more_info_path": "/vulnerabilities/PVE-2025-75611/75611",
            "specs": [
                "<1.10.6"
            ],
            "v": "<1.10.6"
        },
        {
            "advisory": "Psd-tools 1.9.18 includes a version of 'pillow' vulnerable to several CVEs.",
            "cve": "CVE-2020-5311",
            "id": "pyup.io-43469",
            "more_info_path": "/vulnerabilities/CVE-2020-5311/43469",
            "specs": [
                "<=1.9.18"
            ],
            "v": "<=1.9.18"
        },
        {
            "advisory": "libImaging/TiffDecode.c in Pillow before 6.2.2 has a TIFF decoding integer overflow, related to realloc.",
            "cve": "CVE-2020-5310",
            "id": "pyup.io-43468",
            "more_info_path": "/vulnerabilities/CVE-2020-5310/43468",
            "specs": [
                "<=1.9.18"
            ],
            "v": "<=1.9.18"
        },
        {
            "advisory": "Psd-tools 1.9.18 includes a version of 'pillow' vulnerable to several CVEs.",
            "cve": "CVE-2020-5312",
            "id": "pyup.io-43470",
            "more_info_path": "/vulnerabilities/CVE-2020-5312/43470",
            "specs": [
                "<=1.9.18"
            ],
            "v": "<=1.9.18"
        },
        {
            "advisory": "libImaging/FliDecode.c in Pillow before 6.2.2 has an FLI buffer overflow.",
            "cve": "CVE-2020-5313",
            "id": "pyup.io-43471",
            "more_info_path": "/vulnerabilities/CVE-2020-5313/43471",
            "specs": [
                "<=1.9.18"
            ],
            "v": "<=1.9.18"
        },
        {
            "advisory": "Psd-tools 1.9.24 may include a version of pillow that has known vulnerabilities (6.2.2).",
            "cve": "CVE-2019-19911",
            "id": "pyup.io-38525",
            "more_info_path": "/vulnerabilities/CVE-2019-19911/38525",
            "specs": [
                "<=1.9.24"
            ],
            "v": "<=1.9.24"
        },
        {
            "advisory": "Psd-tools 1.9.4 includes a fix for CVE-2020-10571: An issue was discovered in psd-tools before 1.9.4. The Cython implementation of RLE decoding did not check for malicious data.",
            "cve": "CVE-2020-10571",
            "id": "pyup.io-37654",
            "more_info_path": "/vulnerabilities/CVE-2020-10571/37654",
            "specs": [
                ">=1.8.37,<=1.9.3"
            ],
            "v": ">=1.8.37,<=1.9.3"
        }
    ],
    "psd-tools3": [
        {
            "advisory": "Psd-tools3 1.9.1 updates its dependency \"pillow\" to v8.3.2 to include security fixes.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-43549",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/43549",
            "specs": [
                "<1.9.1"
            ],
            "v": "<1.9.1"
        },
        {
            "advisory": "Psd-tools3 1.9.1 updates its dependency \"pillow\" to v8.3.2 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-43548",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/43548",
            "specs": [
                "<1.9.1"
            ],
            "v": "<1.9.1"
        }
    ],
    "psiturk": [
        {
            "advisory": "Psiturk 3.2.1 fixes a SSTI (server side template injection) vulnerability in ad and consent pages.\r\nhttps://github.com/NYUCCL/psiTurk/pull/517",
            "cve": "PVE-2022-45491",
            "id": "pyup.io-45491",
            "more_info_path": "/vulnerabilities/PVE-2022-45491/45491",
            "specs": [
                "<3.2.1"
            ],
            "v": "<3.2.1"
        },
        {
            "advisory": "A vulnerability has been found in NYUCCL psiTurk up to 3.2.0 and classified as critical. This vulnerability affects unknown code of the file psiturk/experiment.py. The manipulation of the argument mode leads to improper neutralization of special elements used in a template engine. The exploit has been disclosed to the public and may be used.",
            "cve": "CVE-2021-4315",
            "id": "pyup.io-54648",
            "more_info_path": "/vulnerabilities/CVE-2021-4315/54648",
            "specs": [
                ">=0,<3.2.1"
            ],
            "v": ">=0,<3.2.1"
        }
    ],
    "psiz": [
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15210",
            "id": "pyup.io-44002",
            "more_info_path": "/vulnerabilities/CVE-2020-15210/44002",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15195",
            "id": "pyup.io-43984",
            "more_info_path": "/vulnerabilities/CVE-2020-15195/43984",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15198",
            "id": "pyup.io-43997",
            "more_info_path": "/vulnerabilities/CVE-2020-15198/43997",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15190",
            "id": "pyup.io-43986",
            "more_info_path": "/vulnerabilities/CVE-2020-15190/43986",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15200",
            "id": "pyup.io-43999",
            "more_info_path": "/vulnerabilities/CVE-2020-15200/43999",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15209",
            "id": "pyup.io-43983",
            "more_info_path": "/vulnerabilities/CVE-2020-15209/43983",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15358",
            "id": "pyup.io-43992",
            "more_info_path": "/vulnerabilities/CVE-2020-15358/43992",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15193",
            "id": "pyup.io-43995",
            "more_info_path": "/vulnerabilities/CVE-2020-15193/43995",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15208",
            "id": "pyup.io-43982",
            "more_info_path": "/vulnerabilities/CVE-2020-15208/43982",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15203",
            "id": "pyup.io-43987",
            "more_info_path": "/vulnerabilities/CVE-2020-15203/43987",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15214",
            "id": "pyup.io-43991",
            "more_info_path": "/vulnerabilities/CVE-2020-15214/43991",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15213",
            "id": "pyup.io-44001",
            "more_info_path": "/vulnerabilities/CVE-2020-15213/44001",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15212",
            "id": "pyup.io-43988",
            "more_info_path": "/vulnerabilities/CVE-2020-15212/43988",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15192",
            "id": "pyup.io-43994",
            "more_info_path": "/vulnerabilities/CVE-2020-15192/43994",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15207",
            "id": "pyup.io-43985",
            "more_info_path": "/vulnerabilities/CVE-2020-15207/43985",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15202",
            "id": "pyup.io-43980",
            "more_info_path": "/vulnerabilities/CVE-2020-15202/43980",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15201",
            "id": "pyup.io-44000",
            "more_info_path": "/vulnerabilities/CVE-2020-15201/44000",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15197",
            "id": "pyup.io-43989",
            "more_info_path": "/vulnerabilities/CVE-2020-15197/43989",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15204",
            "id": "pyup.io-43978",
            "more_info_path": "/vulnerabilities/CVE-2020-15204/43978",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15194",
            "id": "pyup.io-43990",
            "more_info_path": "/vulnerabilities/CVE-2020-15194/43990",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15211",
            "id": "pyup.io-40498",
            "more_info_path": "/vulnerabilities/CVE-2020-15211/40498",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15191",
            "id": "pyup.io-43993",
            "more_info_path": "/vulnerabilities/CVE-2020-15191/43993",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15206",
            "id": "pyup.io-43981",
            "more_info_path": "/vulnerabilities/CVE-2020-15206/43981",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15205",
            "id": "pyup.io-43979",
            "more_info_path": "/vulnerabilities/CVE-2020-15205/43979",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15199",
            "id": "pyup.io-43998",
            "more_info_path": "/vulnerabilities/CVE-2020-15199/43998",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.4.1 updates the 'TensorFlow' requirement to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15196",
            "id": "pyup.io-43996",
            "more_info_path": "/vulnerabilities/CVE-2020-15196/43996",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37667",
            "id": "pyup.io-48086",
            "more_info_path": "/vulnerabilities/CVE-2021-37667/48086",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37668",
            "id": "pyup.io-48087",
            "more_info_path": "/vulnerabilities/CVE-2021-37668/48087",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37650",
            "id": "pyup.io-48070",
            "more_info_path": "/vulnerabilities/CVE-2021-37650/48070",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37660",
            "id": "pyup.io-48079",
            "more_info_path": "/vulnerabilities/CVE-2021-37660/48079",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37635",
            "id": "pyup.io-48055",
            "more_info_path": "/vulnerabilities/CVE-2021-37635/48055",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37637",
            "id": "pyup.io-48057",
            "more_info_path": "/vulnerabilities/CVE-2021-37637/48057",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37680",
            "id": "pyup.io-48098",
            "more_info_path": "/vulnerabilities/CVE-2021-37680/48098",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37649",
            "id": "pyup.io-48069",
            "more_info_path": "/vulnerabilities/CVE-2021-37649/48069",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37677",
            "id": "pyup.io-48095",
            "more_info_path": "/vulnerabilities/CVE-2021-37677/48095",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37673",
            "id": "pyup.io-48091",
            "more_info_path": "/vulnerabilities/CVE-2021-37673/48091",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37655",
            "id": "pyup.io-48074",
            "more_info_path": "/vulnerabilities/CVE-2021-37655/48074",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37658",
            "id": "pyup.io-48077",
            "more_info_path": "/vulnerabilities/CVE-2021-37658/48077",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37686",
            "id": "pyup.io-48104",
            "more_info_path": "/vulnerabilities/CVE-2021-37686/48104",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37656",
            "id": "pyup.io-48075",
            "more_info_path": "/vulnerabilities/CVE-2021-37656/48075",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-22898",
            "id": "pyup.io-48053",
            "more_info_path": "/vulnerabilities/CVE-2021-22898/48053",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37645",
            "id": "pyup.io-48065",
            "more_info_path": "/vulnerabilities/CVE-2021-37645/48065",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37646",
            "id": "pyup.io-48066",
            "more_info_path": "/vulnerabilities/CVE-2021-37646/48066",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37652",
            "id": "pyup.io-48071",
            "more_info_path": "/vulnerabilities/CVE-2021-37652/48071",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37670",
            "id": "pyup.io-48089",
            "more_info_path": "/vulnerabilities/CVE-2021-37670/48089",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37669",
            "id": "pyup.io-48088",
            "more_info_path": "/vulnerabilities/CVE-2021-37669/48088",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37690",
            "id": "pyup.io-48108",
            "more_info_path": "/vulnerabilities/CVE-2021-37690/48108",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37674",
            "id": "pyup.io-48092",
            "more_info_path": "/vulnerabilities/CVE-2021-37674/48092",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37689",
            "id": "pyup.io-48107",
            "more_info_path": "/vulnerabilities/CVE-2021-37689/48107",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-22901",
            "id": "pyup.io-48054",
            "more_info_path": "/vulnerabilities/CVE-2021-22901/48054",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37682",
            "id": "pyup.io-48100",
            "more_info_path": "/vulnerabilities/CVE-2021-37682/48100",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37687",
            "id": "pyup.io-48105",
            "more_info_path": "/vulnerabilities/CVE-2021-37687/48105",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37684",
            "id": "pyup.io-48102",
            "more_info_path": "/vulnerabilities/CVE-2021-37684/48102",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37657",
            "id": "pyup.io-48076",
            "more_info_path": "/vulnerabilities/CVE-2021-37657/48076",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37654",
            "id": "pyup.io-48073",
            "more_info_path": "/vulnerabilities/CVE-2021-37654/48073",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37678",
            "id": "pyup.io-48096",
            "more_info_path": "/vulnerabilities/CVE-2021-37678/48096",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37672",
            "id": "pyup.io-48090",
            "more_info_path": "/vulnerabilities/CVE-2021-37672/48090",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37685",
            "id": "pyup.io-48103",
            "more_info_path": "/vulnerabilities/CVE-2021-37685/48103",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37683",
            "id": "pyup.io-48101",
            "more_info_path": "/vulnerabilities/CVE-2021-37683/48101",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37679",
            "id": "pyup.io-48097",
            "more_info_path": "/vulnerabilities/CVE-2021-37679/48097",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37665",
            "id": "pyup.io-48084",
            "more_info_path": "/vulnerabilities/CVE-2021-37665/48084",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37663",
            "id": "pyup.io-48082",
            "more_info_path": "/vulnerabilities/CVE-2021-37663/48082",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37688",
            "id": "pyup.io-48106",
            "more_info_path": "/vulnerabilities/CVE-2021-37688/48106",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37691",
            "id": "pyup.io-48109",
            "more_info_path": "/vulnerabilities/CVE-2021-37691/48109",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37681",
            "id": "pyup.io-48099",
            "more_info_path": "/vulnerabilities/CVE-2021-37681/48099",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37676",
            "id": "pyup.io-48094",
            "more_info_path": "/vulnerabilities/CVE-2021-37676/48094",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37675",
            "id": "pyup.io-48093",
            "more_info_path": "/vulnerabilities/CVE-2021-37675/48093",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37666",
            "id": "pyup.io-48085",
            "more_info_path": "/vulnerabilities/CVE-2021-37666/48085",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37648",
            "id": "pyup.io-48068",
            "more_info_path": "/vulnerabilities/CVE-2021-37648/48068",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37664",
            "id": "pyup.io-48083",
            "more_info_path": "/vulnerabilities/CVE-2021-37664/48083",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37662",
            "id": "pyup.io-48081",
            "more_info_path": "/vulnerabilities/CVE-2021-37662/48081",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37661",
            "id": "pyup.io-48080",
            "more_info_path": "/vulnerabilities/CVE-2021-37661/48080",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37659",
            "id": "pyup.io-48078",
            "more_info_path": "/vulnerabilities/CVE-2021-37659/48078",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37644",
            "id": "pyup.io-48064",
            "more_info_path": "/vulnerabilities/CVE-2021-37644/48064",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37641",
            "id": "pyup.io-48061",
            "more_info_path": "/vulnerabilities/CVE-2021-37641/48061",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37647",
            "id": "pyup.io-48067",
            "more_info_path": "/vulnerabilities/CVE-2021-37647/48067",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37643",
            "id": "pyup.io-48063",
            "more_info_path": "/vulnerabilities/CVE-2021-37643/48063",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37639",
            "id": "pyup.io-48060",
            "more_info_path": "/vulnerabilities/CVE-2021-37639/48060",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37653",
            "id": "pyup.io-48072",
            "more_info_path": "/vulnerabilities/CVE-2021-37653/48072",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37642",
            "id": "pyup.io-48062",
            "more_info_path": "/vulnerabilities/CVE-2021-37642/48062",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37636",
            "id": "pyup.io-48056",
            "more_info_path": "/vulnerabilities/CVE-2021-37636/48056",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include security fixes.",
            "cve": "CVE-2021-22897",
            "id": "pyup.io-48052",
            "more_info_path": "/vulnerabilities/CVE-2021-22897/48052",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-37638",
            "id": "pyup.io-48059",
            "more_info_path": "/vulnerabilities/CVE-2021-37638/48059",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Psiz 0.6.0 updates its dependency 'TensorFlow' minimum requirement to v2.4.3 to include a security fixes.",
            "cve": "CVE-2021-22876",
            "id": "pyup.io-48045",
            "more_info_path": "/vulnerabilities/CVE-2021-22876/48045",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "psutil": [
        {
            "advisory": "Psutil 0.5.1 includes a fix for a potential race condition vulnerability.\r\nhttps://github.com/giampaolo/psutil/commit/163f29d25f4c5d573fbd436e658829afe95bc1d9",
            "cve": "PVE-2023-61842",
            "id": "pyup.io-61842",
            "more_info_path": "/vulnerabilities/PVE-2023-61842/61842",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.",
            "cve": "CVE-2019-18874",
            "id": "pyup.io-37765",
            "more_info_path": "/vulnerabilities/CVE-2019-18874/37765",
            "specs": [
                "<=5.6.5"
            ],
            "v": "<=5.6.5"
        }
    ],
    "psycopg": [
        {
            "advisory": "Psycopg 3.0.4 updates its dependency 'libpq' to at least v14.1 to include a  security fix.",
            "cve": "CVE-2021-23214",
            "id": "pyup.io-42693",
            "more_info_path": "/vulnerabilities/CVE-2021-23214/42693",
            "specs": [
                "<3.0.4"
            ],
            "v": "<3.0.4"
        }
    ],
    "ptah": [
        {
            "advisory": "ptah before 0.3.3 is vulnerable to a undisclosed attack.",
            "cve": "PVE-2021-26028",
            "id": "pyup.io-26028",
            "more_info_path": "/vulnerabilities/PVE-2021-26028/26028",
            "specs": [
                "<0.3.3"
            ],
            "v": "<0.3.3"
        }
    ],
    "ptpython": [
        {
            "advisory": "Ptpython 3.0.17 fixes race condition during retrieval of signatures.\r\nhttps://github.com/prompt-toolkit/ptpython/commit/7d116e84909d13832935ab4132eabfe316d26b74",
            "cve": "PVE-2023-62830",
            "id": "pyup.io-62830",
            "more_info_path": "/vulnerabilities/PVE-2023-62830/62830",
            "specs": [
                "<3.0.17"
            ],
            "v": "<3.0.17"
        }
    ],
    "pubnub": [
        {
            "advisory": "Several versions of the PubNub package, including those before 7.4.0, 6.19.0, 7.3.0, 6.1.0, 5.3.0, 0.4.0, and others, are vulnerable to Insufficient Entropy via the getKey function. This is due to an inefficient implementation of the AES-256-CBC cryptographic algorithm. The encrypt function is less secure when hex encoding and trimming are applied, leaving half of the bits in the key always the same for every encoded message or file. To exploit this vulnerability, the attacker needs to invest resources in preparing the attack and brute-force the encryption.",
            "cve": "CVE-2023-26154",
            "id": "pyup.io-62696",
            "more_info_path": "/vulnerabilities/CVE-2023-26154/62696",
            "specs": [
                "<0.4.0",
                ">=3.6.4,<4.3.0",
                ">=4.3.1,<5.2.0",
                ">=6.0.0,<6.1.0",
                ">=6.2.0,<6.19.0",
                ">=7.0.0,<7.3.0",
                ">=7.3.1,<7.4.0"
            ],
            "v": "<0.4.0,>=3.6.4,<4.3.0,>=4.3.1,<5.2.0,>=6.0.0,<6.1.0,>=6.2.0,<6.19.0,>=7.0.0,<7.3.0,>=7.3.1,<7.4.0"
        }
    ],
    "pubtools-quay": [
        {
            "advisory": "Pubtools-quay 0.11.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/release-engineering/pubtools-quay/pull/163\r\nhttps://github.com/release-engineering/pubtools-quay/commit/65a27c4f1dee8158da528f644a2dd10625574727",
            "cve": "PVE-2023-60119",
            "id": "pyup.io-60119",
            "more_info_path": "/vulnerabilities/PVE-2023-60119/60119",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "puccini": [
        {
            "advisory": "Puccini 0.3 improves file output security.\r\nhttps://github.com/tliron/puccini/commit/c4181c99e1cff240bc3f8e0fdec0108188554bf5",
            "cve": "PVE-2021-40026",
            "id": "pyup.io-40026",
            "more_info_path": "/vulnerabilities/PVE-2021-40026/40026",
            "specs": [
                "<0.3"
            ],
            "v": "<0.3"
        }
    ],
    "puffioner131": [
        {
            "advisory": "The puffioner131 package on PyPI has been identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain linked to malicious activity, posing significant security risks. Users who have installed this package may be vulnerable to unauthorized access or other harmful consequences.",
            "cve": "PVE-2024-72978",
            "id": "pyup.io-72978",
            "more_info_path": "/vulnerabilities/PVE-2024-72978/72978",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "pulp-ansible": [
        {
            "advisory": "Pulp-ansible 0.15.0 includes a fix for CVE-2022-3644: The collection remote for pulp_ansible stores tokens in plaintext instead of using pulp's encrypted field and exposes them in read/write mode via the API () instead of marking it as write only.\r\nhttps://github.com/pulp/pulp_ansible/pull/1222",
            "cve": "CVE-2022-3644",
            "id": "pyup.io-54557",
            "more_info_path": "/vulnerabilities/CVE-2022-3644/54557",
            "specs": [
                ">=0,<0.15.0"
            ],
            "v": ">=0,<0.15.0"
        }
    ],
    "pulp-container": [
        {
            "advisory": "Pulp-container version 2.19.0 eliminates the ecdsa dependency due to its vulnerability to Minerva timing attacks, as identified in CVE-2024-23342.\r\nhttps://github.com/pulp/pulp_container/commit/59e06e591bd3e621401d83f417fd3fa2ecadbf0a",
            "cve": "CVE-2024-23342",
            "id": "pyup.io-66830",
            "more_info_path": "/vulnerabilities/CVE-2024-23342/66830",
            "specs": [
                "<2.19.0"
            ],
            "v": "<2.19.0"
        },
        {
            "advisory": "Pulp-container 2.14.7 and 2.15.2 include a fix for a Broken Access Control vulnerability that allows users to mount blobs without having read access to the \"from\" repository.\r\nhttps://github.com/pulp/pulp_container/issues/1286",
            "cve": "PVE-2023-60144",
            "id": "pyup.io-60144",
            "more_info_path": "/vulnerabilities/PVE-2023-60144/60144",
            "specs": [
                ">=2.15.0,<2.15.2",
                "<2.14.7"
            ],
            "v": ">=2.15.0,<2.15.2,<2.14.7"
        }
    ],
    "pulpcore": [
        {
            "advisory": "Pulpcore 3.11.0 adds the 'ALLOWED_CONTENT_CHECKSUMS' setting to remove 'md5' and 'sha1' since they are not secure. Now, by default, the 'ALLOWED_CONTENT_CHECKSUMS' contain 'sha224', 'sha256', 'sha384', and 'sha512'.",
            "cve": "PVE-2021-40315",
            "id": "pyup.io-40315",
            "more_info_path": "/vulnerabilities/PVE-2021-40315/40315",
            "specs": [
                "<3.11.0"
            ],
            "v": "<3.11.0"
        },
        {
            "advisory": "Pulpcore 3.14.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/pulp/pulpcore/pull/1425",
            "cve": "PVE-2023-59695",
            "id": "pyup.io-59695",
            "more_info_path": "/vulnerabilities/PVE-2023-59695/59695",
            "specs": [
                "<3.14.0"
            ],
            "v": "<3.14.0"
        },
        {
            "advisory": "Pulpcore 3.16.6 updates its dependency 'aiohttp' to v3.8.1 to include a security fix.",
            "cve": "PVE-2021-42692",
            "id": "pyup.io-47783",
            "more_info_path": "/vulnerabilities/PVE-2021-42692/47783",
            "specs": [
                "<3.16.6"
            ],
            "v": "<3.16.6"
        },
        {
            "advisory": "Pulpcore 3.24.0 includes a fix for a Race Condition vulnerability. When two or more processes try to create the same content only one can call the \"create\" successfully so the other one needs to attempt the \"retrieve\" a second time.\r\nhttps://github.com/pulp/pulpcore/pull/3756",
            "cve": "PVE-2023-59694",
            "id": "pyup.io-59694",
            "more_info_path": "/vulnerabilities/PVE-2023-59694/59694",
            "specs": [
                "<3.24.0"
            ],
            "v": "<3.24.0"
        },
        {
            "advisory": "Pulpcore 3.6.0 includes a fix for a denial of service vulnerability. \r\nhttps://github.com/pulp/pulpcore/pull/763",
            "cve": "PVE-2023-59043",
            "id": "pyup.io-59043",
            "more_info_path": "/vulnerabilities/PVE-2023-59043/59043",
            "specs": [
                "<3.6.0"
            ],
            "v": "<3.6.0"
        },
        {
            "advisory": "pulp 2.16.x and possibly older is vulnerable to an improper path parsing. A malicious user or a malicious iso feed repository can write to locations accessible to the 'apache' user. This may lead to overwrite of published content on other iso repositories.",
            "cve": "CVE-2018-10917",
            "id": "pyup.io-67600",
            "more_info_path": "/vulnerabilities/CVE-2018-10917/67600",
            "specs": [
                "<=2.16"
            ],
            "v": "<=2.16"
        },
        {
            "advisory": "Pulpcore before 3.15.0 is susceptible to insecure encryption due to utilizing the blake2s hash function for generating a 64-bit lock identifier from UUID. The exploit maturity for this vulnerability is currently unproven.\r\nhttps://github.com/pulp/pulpcore/commit/1d77e5cdf4d03b7edff34f4fc3b60a2f70df3e88",
            "cve": "PVE-2024-99767",
            "id": "pyup.io-66658",
            "more_info_path": "/vulnerabilities/PVE-2024-99767/66658",
            "specs": [
                ">=0,<3.15.0"
            ],
            "v": ">=0,<3.15.0"
        },
        {
            "advisory": "Pulpcore fixed an issue where RBAC permissions were incorrectly assigned during task-based object creation. In Pulp, the `AutoAddObjPermsMixin` assigns permissions to the oldest user with task permissions instead of the actual task initiator. This resulted in the wrong user receiving permissions, leaving the creating user with none.",
            "cve": "CVE-2024-7143",
            "id": "pyup.io-72596",
            "more_info_path": "/vulnerabilities/CVE-2024-7143/72596",
            "specs": [
                ">=3.28,<3.28.32",
                ">=3.39,<3.39.20",
                ">=3.49,<3.49.17",
                ">=3.57.0,<3.57.1",
                ">=3.22,<3.22.30",
                "<3.21.33"
            ],
            "v": ">=3.28,<3.28.32,>=3.39,<3.39.20,>=3.49,<3.49.17,>=3.57.0,<3.57.1,>=3.22,<3.22.30,<3.21.33"
        }
    ],
    "pulsar-client": [
        {
            "advisory": "Pulsar-client 2.7.5, 2.8.4, 2.9.3 and 2.10.2 include a fix for CVE-2022-33684: The Apache Pulsar C++ Client does not verify peer TLS certificates when making HTTPS calls for the OAuth2.0 Client Credential Flow, even when tlsAllowInsecureConnection is disabled via configuration. This vulnerability allows an attacker to perform a man in the middle attack and intercept and/or modify the GET request that is sent to the ClientCredentialFlow 'issuer url'. The intercepted credentials can be used to acquire authentication data from the OAuth2.0 server to then authenticate with an Apache Pulsar cluster. An attacker can only take advantage of this vulnerability by taking control of a machine 'between' the client and the server. The attacker must then actively manipulate traffic to perform the attack. Apache Pulsar Python Client wraps the C++ client, so it is also vulnerable in the same way. This issue affects Apache Pulsar C++ Client and Python Client versions 2.7.0 to 2.7.4; 2.8.0 to 2.8.3; 2.9.0 to 2.9.2; 2.10.0 to 2.10.1; 2.6.4 and earlier. Any users running affected versions of the C++ Client or the Python Client should rotate vulnerable OAuth2.0 credentials, including client_id and client_secret.",
            "cve": "CVE-2022-33684",
            "id": "pyup.io-51700",
            "more_info_path": "/vulnerabilities/CVE-2022-33684/51700",
            "specs": [
                "<2.7.5",
                ">=2.8.0,<2.8.4",
                ">=2.9.0,<2.9.3",
                ">=2.10.0,<2.10.2"
            ],
            "v": "<2.7.5,>=2.8.0,<2.8.4,>=2.9.0,<2.9.3,>=2.10.0,<2.10.2"
        }
    ],
    "pulumi-aws": [
        {
            "advisory": "Pulumi-aws 5.34.0 updates its GO dependency 'golang.org/x/sys' to v0.6.0 to include a security fix.",
            "cve": "CVE-2022-29526",
            "id": "pyup.io-54810",
            "more_info_path": "/vulnerabilities/CVE-2022-29526/54810",
            "specs": [
                "<5.34.0"
            ],
            "v": "<5.34.0"
        },
        {
            "advisory": "Pulumi-aws 5.34.0 updates its GO dependency 'golang.org/x/crypto' to v0.7.0 to include a security fix.",
            "cve": "CVE-2022-27191",
            "id": "pyup.io-54769",
            "more_info_path": "/vulnerabilities/CVE-2022-27191/54769",
            "specs": [
                "<5.34.0"
            ],
            "v": "<5.34.0"
        }
    ],
    "pulumi-azuread": [
        {
            "advisory": "Pulumi-azuread 5.34.1 updates its GO dependency 'goutils' to v1.1.1 to include a security fix.",
            "cve": "CVE-2021-4238",
            "id": "pyup.io-53300",
            "more_info_path": "/vulnerabilities/CVE-2021-4238/53300",
            "specs": [
                "<5.34.1"
            ],
            "v": "<5.34.1"
        }
    ],
    "pulumi-gcp": [
        {
            "advisory": "Pulumi-gcp 6.53.0 updates its GO dependency 'gogo/protobuf' to v1.3.2 to include a security fix.",
            "cve": "CVE-2021-3121",
            "id": "pyup.io-54888",
            "more_info_path": "/vulnerabilities/CVE-2021-3121/54888",
            "specs": [
                "<6.53.0"
            ],
            "v": "<6.53.0"
        }
    ],
    "pulumi-kubernetes": [
        {
            "advisory": "Pulumi-kubernetes 2.6.0 updates its dependency 'pyyaml' minimum version to v5.3.1 to include security fixes.",
            "cve": "CVE-2019-20477",
            "id": "pyup.io-38772",
            "more_info_path": "/vulnerabilities/CVE-2019-20477/38772",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        },
        {
            "advisory": "Affected versions of the pulumi/pulumi-kubernetes are potentially vulnerable to a race condition in the deletion await logic. This timing flaw can significantly delay resource deletion, potentially leading to denial-of-service conditions or resource exhaustion if an attacker manipulates deletion order via rapid API calls",
            "cve": "PVE-2025-75908",
            "id": "pyup.io-75908",
            "more_info_path": "/vulnerabilities/PVE-2025-75908/75908",
            "specs": [
                "<4.22.0"
            ],
            "v": "<4.22.0"
        }
    ],
    "pulumi-policy": [
        {
            "advisory": "Pulumi-policy 1.6.0 updates its dependency 'protobufjs' to version '6.11.3' to include a security fix.\r\nhttps://github.com/pulumi/pulumi-policy/commit/adc5196b8519a7a2647254e51aac878588824086",
            "cve": "CVE-2022-25878",
            "id": "pyup.io-59240",
            "more_info_path": "/vulnerabilities/CVE-2022-25878/59240",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        }
    ],
    "puncia": [
        {
            "advisory": "Affected versions of Puncia are vulnerable to Cleartext Transmission of Sensitive Information. API_URLS is utilizing HTTP instead of HTTPS for communication that can lead to issues like Eavesdropping, Data Tampering, Unauthorized Data Access & MITM Attacks.",
            "cve": "CVE-2024-41124",
            "id": "pyup.io-72265",
            "more_info_path": "/vulnerabilities/CVE-2024-41124/72265",
            "specs": [
                "<0.21"
            ],
            "v": "<0.21"
        }
    ],
    "puput": [
        {
            "advisory": "Puput 1.0.4 updates the Django version to greater than 2.1.6 to fix security issues.",
            "cve": "CVE-2018-14574",
            "id": "pyup.io-43663",
            "more_info_path": "/vulnerabilities/CVE-2018-14574/43663",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        },
        {
            "advisory": "Puput 1.0.4 updates the Django version to greater than 2.1.6 to fix security issues.",
            "cve": "CVE-2019-6975",
            "id": "pyup.io-37153",
            "more_info_path": "/vulnerabilities/CVE-2019-6975/37153",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        },
        {
            "advisory": "Puput 1.0.4 updates the Django version to greater than 2.1.6 to fix security issues.",
            "cve": "CVE-2018-7537",
            "id": "pyup.io-43664",
            "more_info_path": "/vulnerabilities/CVE-2018-7537/43664",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        },
        {
            "advisory": "Puput 1.0.4 updates the Django version to greater than 2.1.6 to fix security issues.",
            "cve": "CVE-2019-3498",
            "id": "pyup.io-43662",
            "more_info_path": "/vulnerabilities/CVE-2019-3498/43662",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        }
    ],
    "pupyl": [
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15358",
            "id": "pyup.io-45016",
            "more_info_path": "/vulnerabilities/CVE-2020-15358/45016",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15194",
            "id": "pyup.io-44995",
            "more_info_path": "/vulnerabilities/CVE-2020-15194/44995",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15210",
            "id": "pyup.io-45011",
            "more_info_path": "/vulnerabilities/CVE-2020-15210/45011",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15195",
            "id": "pyup.io-44996",
            "more_info_path": "/vulnerabilities/CVE-2020-15195/44996",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15197",
            "id": "pyup.io-44998",
            "more_info_path": "/vulnerabilities/CVE-2020-15197/44998",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15196",
            "id": "pyup.io-44997",
            "more_info_path": "/vulnerabilities/CVE-2020-15196/44997",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15198",
            "id": "pyup.io-44999",
            "more_info_path": "/vulnerabilities/CVE-2020-15198/44999",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15205",
            "id": "pyup.io-45006",
            "more_info_path": "/vulnerabilities/CVE-2020-15205/45006",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15191",
            "id": "pyup.io-44992",
            "more_info_path": "/vulnerabilities/CVE-2020-15191/44992",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15213",
            "id": "pyup.io-45014",
            "more_info_path": "/vulnerabilities/CVE-2020-15213/45014",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15203",
            "id": "pyup.io-45004",
            "more_info_path": "/vulnerabilities/CVE-2020-15203/45004",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15212",
            "id": "pyup.io-45013",
            "more_info_path": "/vulnerabilities/CVE-2020-15212/45013",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15211",
            "id": "pyup.io-45012",
            "more_info_path": "/vulnerabilities/CVE-2020-15211/45012",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15209",
            "id": "pyup.io-45010",
            "more_info_path": "/vulnerabilities/CVE-2020-15209/45010",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15214",
            "id": "pyup.io-45015",
            "more_info_path": "/vulnerabilities/CVE-2020-15214/45015",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15207",
            "id": "pyup.io-45008",
            "more_info_path": "/vulnerabilities/CVE-2020-15207/45008",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15206",
            "id": "pyup.io-45007",
            "more_info_path": "/vulnerabilities/CVE-2020-15206/45007",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15204",
            "id": "pyup.io-45005",
            "more_info_path": "/vulnerabilities/CVE-2020-15204/45005",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15201",
            "id": "pyup.io-45002",
            "more_info_path": "/vulnerabilities/CVE-2020-15201/45002",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15200",
            "id": "pyup.io-45001",
            "more_info_path": "/vulnerabilities/CVE-2020-15200/45001",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15199",
            "id": "pyup.io-45000",
            "more_info_path": "/vulnerabilities/CVE-2020-15199/45000",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15193",
            "id": "pyup.io-44994",
            "more_info_path": "/vulnerabilities/CVE-2020-15193/44994",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15192",
            "id": "pyup.io-44993",
            "more_info_path": "/vulnerabilities/CVE-2020-15192/44993",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15190",
            "id": "pyup.io-39208",
            "more_info_path": "/vulnerabilities/CVE-2020-15190/39208",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15208",
            "id": "pyup.io-45009",
            "more_info_path": "/vulnerabilities/CVE-2020-15208/45009",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.4 updates its dependency 'tensorflow' to v2.3.1 to include security fixes.",
            "cve": "CVE-2020-15202",
            "id": "pyup.io-45003",
            "more_info_path": "/vulnerabilities/CVE-2020-15202/45003",
            "specs": [
                "<0.10.4"
            ],
            "v": "<0.10.4"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-26267",
            "id": "pyup.io-39392",
            "more_info_path": "/vulnerabilities/CVE-2020-26267/39392",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2019-20838",
            "id": "pyup.io-44986",
            "more_info_path": "/vulnerabilities/CVE-2019-20838/44986",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-13790",
            "id": "pyup.io-44989",
            "more_info_path": "/vulnerabilities/CVE-2020-13790/44989",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-26268",
            "id": "pyup.io-44982",
            "more_info_path": "/vulnerabilities/CVE-2020-26268/44982",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-26271",
            "id": "pyup.io-44984",
            "more_info_path": "/vulnerabilities/CVE-2020-26271/44984",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-15266",
            "id": "pyup.io-44991",
            "more_info_path": "/vulnerabilities/CVE-2020-15266/44991",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-15265",
            "id": "pyup.io-44990",
            "more_info_path": "/vulnerabilities/CVE-2020-15265/44990",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-15250",
            "id": "pyup.io-44987",
            "more_info_path": "/vulnerabilities/CVE-2020-15250/44987",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-26270",
            "id": "pyup.io-44983",
            "more_info_path": "/vulnerabilities/CVE-2020-26270/44983",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-14155",
            "id": "pyup.io-44988",
            "more_info_path": "/vulnerabilities/CVE-2020-14155/44988",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl 0.10.5 updates its dependency 'tensorflow' to v2.4.0 to include security fixes.",
            "cve": "CVE-2020-26266",
            "id": "pyup.io-44985",
            "more_info_path": "/vulnerabilities/CVE-2020-26266/44985",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Pupyl before 0.10.6 includes Tensorflow 2.3.1 which has security issues (see issue 73) and should therefore be upgraded to 2.4.0. However, the last version of Tensorflow has issues on its compilation (see Tensorflow issue 45744), and hence must be downgraded to ensure that the library still works.",
            "cve": "PVE-2021-39400",
            "id": "pyup.io-39400",
            "more_info_path": "/vulnerabilities/PVE-2021-39400/39400",
            "specs": [
                "<0.10.6"
            ],
            "v": "<0.10.6"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2020-8231",
            "id": "pyup.io-43947",
            "more_info_path": "/vulnerabilities/CVE-2020-8231/43947",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29594",
            "id": "pyup.io-43909",
            "more_info_path": "/vulnerabilities/CVE-2021-29594/43909",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29607",
            "id": "pyup.io-43930",
            "more_info_path": "/vulnerabilities/CVE-2021-29607/43930",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29604",
            "id": "pyup.io-43922",
            "more_info_path": "/vulnerabilities/CVE-2021-29604/43922",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2020-8169",
            "id": "pyup.io-43864",
            "more_info_path": "/vulnerabilities/CVE-2020-8169/43864",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29613",
            "id": "pyup.io-43934",
            "more_info_path": "/vulnerabilities/CVE-2021-29613/43934",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29581",
            "id": "pyup.io-43898",
            "more_info_path": "/vulnerabilities/CVE-2021-29581/43898",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29552",
            "id": "pyup.io-43940",
            "more_info_path": "/vulnerabilities/CVE-2021-29552/43940",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29575",
            "id": "pyup.io-43961",
            "more_info_path": "/vulnerabilities/CVE-2021-29575/43961",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29577",
            "id": "pyup.io-43967",
            "more_info_path": "/vulnerabilities/CVE-2021-29577/43967",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29557",
            "id": "pyup.io-43945",
            "more_info_path": "/vulnerabilities/CVE-2021-29557/43945",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29567",
            "id": "pyup.io-43881",
            "more_info_path": "/vulnerabilities/CVE-2021-29567/43881",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29600",
            "id": "pyup.io-43920",
            "more_info_path": "/vulnerabilities/CVE-2021-29600/43920",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29549",
            "id": "pyup.io-43936",
            "more_info_path": "/vulnerabilities/CVE-2021-29549/43936",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29610",
            "id": "pyup.io-43871",
            "more_info_path": "/vulnerabilities/CVE-2021-29610/43871",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29541",
            "id": "pyup.io-43928",
            "more_info_path": "/vulnerabilities/CVE-2021-29541/43928",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29522",
            "id": "pyup.io-43859",
            "more_info_path": "/vulnerabilities/CVE-2021-29522/43859",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29591",
            "id": "pyup.io-43907",
            "more_info_path": "/vulnerabilities/CVE-2021-29591/43907",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29525",
            "id": "pyup.io-43857",
            "more_info_path": "/vulnerabilities/CVE-2021-29525/43857",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29527",
            "id": "pyup.io-43910",
            "more_info_path": "/vulnerabilities/CVE-2021-29527/43910",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29605",
            "id": "pyup.io-43924",
            "more_info_path": "/vulnerabilities/CVE-2021-29605/43924",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29562",
            "id": "pyup.io-43958",
            "more_info_path": "/vulnerabilities/CVE-2021-29562/43958",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29554",
            "id": "pyup.io-43942",
            "more_info_path": "/vulnerabilities/CVE-2021-29554/43942",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29603",
            "id": "pyup.io-43925",
            "more_info_path": "/vulnerabilities/CVE-2021-29603/43925",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29568",
            "id": "pyup.io-43873",
            "more_info_path": "/vulnerabilities/CVE-2021-29568/43873",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29618",
            "id": "pyup.io-43937",
            "more_info_path": "/vulnerabilities/CVE-2021-29618/43937",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29593",
            "id": "pyup.io-43913",
            "more_info_path": "/vulnerabilities/CVE-2021-29593/43913",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29540",
            "id": "pyup.io-43889",
            "more_info_path": "/vulnerabilities/CVE-2021-29540/43889",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29524",
            "id": "pyup.io-43860",
            "more_info_path": "/vulnerabilities/CVE-2021-29524/43860",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2020-8284",
            "id": "pyup.io-43946",
            "more_info_path": "/vulnerabilities/CVE-2020-8284/43946",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29598",
            "id": "pyup.io-43917",
            "more_info_path": "/vulnerabilities/CVE-2021-29598/43917",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29529",
            "id": "pyup.io-43916",
            "more_info_path": "/vulnerabilities/CVE-2021-29529/43916",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29586",
            "id": "pyup.io-43903",
            "more_info_path": "/vulnerabilities/CVE-2021-29586/43903",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29611",
            "id": "pyup.io-43931",
            "more_info_path": "/vulnerabilities/CVE-2021-29611/43931",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29551",
            "id": "pyup.io-43891",
            "more_info_path": "/vulnerabilities/CVE-2021-29551/43891",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29528",
            "id": "pyup.io-43912",
            "more_info_path": "/vulnerabilities/CVE-2021-29528/43912",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29592",
            "id": "pyup.io-43906",
            "more_info_path": "/vulnerabilities/CVE-2021-29592/43906",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29616",
            "id": "pyup.io-43866",
            "more_info_path": "/vulnerabilities/CVE-2021-29616/43866",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29609",
            "id": "pyup.io-43929",
            "more_info_path": "/vulnerabilities/CVE-2021-29609/43929",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29582",
            "id": "pyup.io-43899",
            "more_info_path": "/vulnerabilities/CVE-2021-29582/43899",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29597",
            "id": "pyup.io-43914",
            "more_info_path": "/vulnerabilities/CVE-2021-29597/43914",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29513",
            "id": "pyup.io-43892",
            "more_info_path": "/vulnerabilities/CVE-2021-29513/43892",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29587",
            "id": "pyup.io-43872",
            "more_info_path": "/vulnerabilities/CVE-2021-29587/43872",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29585",
            "id": "pyup.io-43902",
            "more_info_path": "/vulnerabilities/CVE-2021-29585/43902",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29584",
            "id": "pyup.io-43900",
            "more_info_path": "/vulnerabilities/CVE-2021-29584/43900",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29608",
            "id": "pyup.io-43890",
            "more_info_path": "/vulnerabilities/CVE-2021-29608/43890",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29530",
            "id": "pyup.io-43915",
            "more_info_path": "/vulnerabilities/CVE-2021-29530/43915",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29578",
            "id": "pyup.io-43895",
            "more_info_path": "/vulnerabilities/CVE-2021-29578/43895",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29571",
            "id": "pyup.io-43966",
            "more_info_path": "/vulnerabilities/CVE-2021-29571/43966",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29572",
            "id": "pyup.io-43893",
            "more_info_path": "/vulnerabilities/CVE-2021-29572/43893",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29573",
            "id": "pyup.io-43962",
            "more_info_path": "/vulnerabilities/CVE-2021-29573/43962",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29570",
            "id": "pyup.io-43960",
            "more_info_path": "/vulnerabilities/CVE-2021-29570/43960",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29514",
            "id": "pyup.io-43880",
            "more_info_path": "/vulnerabilities/CVE-2021-29514/43880",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2020-8177",
            "id": "pyup.io-43943",
            "more_info_path": "/vulnerabilities/CVE-2020-8177/43943",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29566",
            "id": "pyup.io-43874",
            "more_info_path": "/vulnerabilities/CVE-2021-29566/43874",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29561",
            "id": "pyup.io-43959",
            "more_info_path": "/vulnerabilities/CVE-2021-29561/43959",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29556",
            "id": "pyup.io-43948",
            "more_info_path": "/vulnerabilities/CVE-2021-29556/43948",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29548",
            "id": "pyup.io-43886",
            "more_info_path": "/vulnerabilities/CVE-2021-29548/43886",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29545",
            "id": "pyup.io-43878",
            "more_info_path": "/vulnerabilities/CVE-2021-29545/43878",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29547",
            "id": "pyup.io-43868",
            "more_info_path": "/vulnerabilities/CVE-2021-29547/43868",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29546",
            "id": "pyup.io-43933",
            "more_info_path": "/vulnerabilities/CVE-2021-29546/43933",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29550",
            "id": "pyup.io-43877",
            "more_info_path": "/vulnerabilities/CVE-2021-29550/43877",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29543",
            "id": "pyup.io-43867",
            "more_info_path": "/vulnerabilities/CVE-2021-29543/43867",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29542",
            "id": "pyup.io-43927",
            "more_info_path": "/vulnerabilities/CVE-2021-29542/43927",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29614",
            "id": "pyup.io-43968",
            "more_info_path": "/vulnerabilities/CVE-2021-29614/43968",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29539",
            "id": "pyup.io-40931",
            "more_info_path": "/vulnerabilities/CVE-2021-29539/40931",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29537",
            "id": "pyup.io-43879",
            "more_info_path": "/vulnerabilities/CVE-2021-29537/43879",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29536",
            "id": "pyup.io-43887",
            "more_info_path": "/vulnerabilities/CVE-2021-29536/43887",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29535",
            "id": "pyup.io-43885",
            "more_info_path": "/vulnerabilities/CVE-2021-29535/43885",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29531",
            "id": "pyup.io-43918",
            "more_info_path": "/vulnerabilities/CVE-2021-29531/43918",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29534",
            "id": "pyup.io-43870",
            "more_info_path": "/vulnerabilities/CVE-2021-29534/43870",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29521",
            "id": "pyup.io-43863",
            "more_info_path": "/vulnerabilities/CVE-2021-29521/43863",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29518",
            "id": "pyup.io-43953",
            "more_info_path": "/vulnerabilities/CVE-2021-29518/43953",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29517",
            "id": "pyup.io-43956",
            "more_info_path": "/vulnerabilities/CVE-2021-29517/43956",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29516",
            "id": "pyup.io-43955",
            "more_info_path": "/vulnerabilities/CVE-2021-29516/43955",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29515",
            "id": "pyup.io-43963",
            "more_info_path": "/vulnerabilities/CVE-2021-29515/43963",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29526",
            "id": "pyup.io-43954",
            "more_info_path": "/vulnerabilities/CVE-2021-29526/43954",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29512",
            "id": "pyup.io-43883",
            "more_info_path": "/vulnerabilities/CVE-2021-29512/43883",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29615",
            "id": "pyup.io-43935",
            "more_info_path": "/vulnerabilities/CVE-2021-29615/43935",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29619",
            "id": "pyup.io-43941",
            "more_info_path": "/vulnerabilities/CVE-2021-29619/43941",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29519",
            "id": "pyup.io-43858",
            "more_info_path": "/vulnerabilities/CVE-2021-29519/43858",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29576",
            "id": "pyup.io-43965",
            "more_info_path": "/vulnerabilities/CVE-2021-29576/43965",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29606",
            "id": "pyup.io-43926",
            "more_info_path": "/vulnerabilities/CVE-2021-29606/43926",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29580",
            "id": "pyup.io-43894",
            "more_info_path": "/vulnerabilities/CVE-2021-29580/43894",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29601",
            "id": "pyup.io-43923",
            "more_info_path": "/vulnerabilities/CVE-2021-29601/43923",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29574",
            "id": "pyup.io-43964",
            "more_info_path": "/vulnerabilities/CVE-2021-29574/43964",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29588",
            "id": "pyup.io-43904",
            "more_info_path": "/vulnerabilities/CVE-2021-29588/43904",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29583",
            "id": "pyup.io-43901",
            "more_info_path": "/vulnerabilities/CVE-2021-29583/43901",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29579",
            "id": "pyup.io-43896",
            "more_info_path": "/vulnerabilities/CVE-2021-29579/43896",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29532",
            "id": "pyup.io-43865",
            "more_info_path": "/vulnerabilities/CVE-2021-29532/43865",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29590",
            "id": "pyup.io-43905",
            "more_info_path": "/vulnerabilities/CVE-2021-29590/43905",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29553",
            "id": "pyup.io-43939",
            "more_info_path": "/vulnerabilities/CVE-2021-29553/43939",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29563",
            "id": "pyup.io-43875",
            "more_info_path": "/vulnerabilities/CVE-2021-29563/43875",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2020-8285",
            "id": "pyup.io-43969",
            "more_info_path": "/vulnerabilities/CVE-2020-8285/43969",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29538",
            "id": "pyup.io-43888",
            "more_info_path": "/vulnerabilities/CVE-2021-29538/43888",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29595",
            "id": "pyup.io-43908",
            "more_info_path": "/vulnerabilities/CVE-2021-29595/43908",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29533",
            "id": "pyup.io-43884",
            "more_info_path": "/vulnerabilities/CVE-2021-29533/43884",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29558",
            "id": "pyup.io-43949",
            "more_info_path": "/vulnerabilities/CVE-2021-29558/43949",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29564",
            "id": "pyup.io-43862",
            "more_info_path": "/vulnerabilities/CVE-2021-29564/43862",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29602",
            "id": "pyup.io-43921",
            "more_info_path": "/vulnerabilities/CVE-2021-29602/43921",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29559",
            "id": "pyup.io-43950",
            "more_info_path": "/vulnerabilities/CVE-2021-29559/43950",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29565",
            "id": "pyup.io-43952",
            "more_info_path": "/vulnerabilities/CVE-2021-29565/43952",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29555",
            "id": "pyup.io-43944",
            "more_info_path": "/vulnerabilities/CVE-2021-29555/43944",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29520",
            "id": "pyup.io-43861",
            "more_info_path": "/vulnerabilities/CVE-2021-29520/43861",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29589",
            "id": "pyup.io-43882",
            "more_info_path": "/vulnerabilities/CVE-2021-29589/43882",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29612",
            "id": "pyup.io-43932",
            "more_info_path": "/vulnerabilities/CVE-2021-29612/43932",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29523",
            "id": "pyup.io-43856",
            "more_info_path": "/vulnerabilities/CVE-2021-29523/43856",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29599",
            "id": "pyup.io-43919",
            "more_info_path": "/vulnerabilities/CVE-2021-29599/43919",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2021-29560",
            "id": "pyup.io-43876",
            "more_info_path": "/vulnerabilities/CVE-2021-29560/43876",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29617",
            "id": "pyup.io-43938",
            "more_info_path": "/vulnerabilities/CVE-2021-29617/43938",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29569",
            "id": "pyup.io-43957",
            "more_info_path": "/vulnerabilities/CVE-2021-29569/43957",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes.",
            "cve": "CVE-2020-8286",
            "id": "pyup.io-43951",
            "more_info_path": "/vulnerabilities/CVE-2020-8286/43951",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29544",
            "id": "pyup.io-43869",
            "more_info_path": "/vulnerabilities/CVE-2021-29544/43869",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.11.1 updates 'Tensorflow' to v2.5.0 to include security fixes",
            "cve": "CVE-2021-29596",
            "id": "pyup.io-43911",
            "more_info_path": "/vulnerabilities/CVE-2021-29596/43911",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37690",
            "id": "pyup.io-46297",
            "more_info_path": "/vulnerabilities/CVE-2021-37690/46297",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37670",
            "id": "pyup.io-46277",
            "more_info_path": "/vulnerabilities/CVE-2021-37670/46277",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37680",
            "id": "pyup.io-46287",
            "more_info_path": "/vulnerabilities/CVE-2021-37680/46287",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37664",
            "id": "pyup.io-46271",
            "more_info_path": "/vulnerabilities/CVE-2021-37664/46271",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-22876",
            "id": "pyup.io-46238",
            "more_info_path": "/vulnerabilities/CVE-2021-22876/46238",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37638",
            "id": "pyup.io-46245",
            "more_info_path": "/vulnerabilities/CVE-2021-37638/46245",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37650",
            "id": "pyup.io-46257",
            "more_info_path": "/vulnerabilities/CVE-2021-37650/46257",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37651",
            "id": "pyup.io-46258",
            "more_info_path": "/vulnerabilities/CVE-2021-37651/46258",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37662",
            "id": "pyup.io-46269",
            "more_info_path": "/vulnerabilities/CVE-2021-37662/46269",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37643",
            "id": "pyup.io-46250",
            "more_info_path": "/vulnerabilities/CVE-2021-37643/46250",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37686",
            "id": "pyup.io-46293",
            "more_info_path": "/vulnerabilities/CVE-2021-37686/46293",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37682",
            "id": "pyup.io-46289",
            "more_info_path": "/vulnerabilities/CVE-2021-37682/46289",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37635",
            "id": "pyup.io-46242",
            "more_info_path": "/vulnerabilities/CVE-2021-37635/46242",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37654",
            "id": "pyup.io-46261",
            "more_info_path": "/vulnerabilities/CVE-2021-37654/46261",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37646",
            "id": "pyup.io-46253",
            "more_info_path": "/vulnerabilities/CVE-2021-37646/46253",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37679",
            "id": "pyup.io-46286",
            "more_info_path": "/vulnerabilities/CVE-2021-37679/46286",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37684",
            "id": "pyup.io-46291",
            "more_info_path": "/vulnerabilities/CVE-2021-37684/46291",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37687",
            "id": "pyup.io-46294",
            "more_info_path": "/vulnerabilities/CVE-2021-37687/46294",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37666",
            "id": "pyup.io-46273",
            "more_info_path": "/vulnerabilities/CVE-2021-37666/46273",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37691",
            "id": "pyup.io-46298",
            "more_info_path": "/vulnerabilities/CVE-2021-37691/46298",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37660",
            "id": "pyup.io-46267",
            "more_info_path": "/vulnerabilities/CVE-2021-37660/46267",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37661",
            "id": "pyup.io-46268",
            "more_info_path": "/vulnerabilities/CVE-2021-37661/46268",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37671",
            "id": "pyup.io-46278",
            "more_info_path": "/vulnerabilities/CVE-2021-37671/46278",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37647",
            "id": "pyup.io-46254",
            "more_info_path": "/vulnerabilities/CVE-2021-37647/46254",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37676",
            "id": "pyup.io-46283",
            "more_info_path": "/vulnerabilities/CVE-2021-37676/46283",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37652",
            "id": "pyup.io-46259",
            "more_info_path": "/vulnerabilities/CVE-2021-37652/46259",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37668",
            "id": "pyup.io-46275",
            "more_info_path": "/vulnerabilities/CVE-2021-37668/46275",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37665",
            "id": "pyup.io-46272",
            "more_info_path": "/vulnerabilities/CVE-2021-37665/46272",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37683",
            "id": "pyup.io-46290",
            "more_info_path": "/vulnerabilities/CVE-2021-37683/46290",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37642",
            "id": "pyup.io-46249",
            "more_info_path": "/vulnerabilities/CVE-2021-37642/46249",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-22901",
            "id": "pyup.io-46241",
            "more_info_path": "/vulnerabilities/CVE-2021-22901/46241",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37653",
            "id": "pyup.io-46260",
            "more_info_path": "/vulnerabilities/CVE-2021-37653/46260",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-22898",
            "id": "pyup.io-46240",
            "more_info_path": "/vulnerabilities/CVE-2021-22898/46240",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-22897",
            "id": "pyup.io-46239",
            "more_info_path": "/vulnerabilities/CVE-2021-22897/46239",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37688",
            "id": "pyup.io-46295",
            "more_info_path": "/vulnerabilities/CVE-2021-37688/46295",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37672",
            "id": "pyup.io-46279",
            "more_info_path": "/vulnerabilities/CVE-2021-37672/46279",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37659",
            "id": "pyup.io-46266",
            "more_info_path": "/vulnerabilities/CVE-2021-37659/46266",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37673",
            "id": "pyup.io-46280",
            "more_info_path": "/vulnerabilities/CVE-2021-37673/46280",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37675",
            "id": "pyup.io-46282",
            "more_info_path": "/vulnerabilities/CVE-2021-37675/46282",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37649",
            "id": "pyup.io-46256",
            "more_info_path": "/vulnerabilities/CVE-2021-37649/46256",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37692",
            "id": "pyup.io-46299",
            "more_info_path": "/vulnerabilities/CVE-2021-37692/46299",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37658",
            "id": "pyup.io-46265",
            "more_info_path": "/vulnerabilities/CVE-2021-37658/46265",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37685",
            "id": "pyup.io-46292",
            "more_info_path": "/vulnerabilities/CVE-2021-37685/46292",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37678",
            "id": "pyup.io-46285",
            "more_info_path": "/vulnerabilities/CVE-2021-37678/46285",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37677",
            "id": "pyup.io-46284",
            "more_info_path": "/vulnerabilities/CVE-2021-37677/46284",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37674",
            "id": "pyup.io-46281",
            "more_info_path": "/vulnerabilities/CVE-2021-37674/46281",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37663",
            "id": "pyup.io-46270",
            "more_info_path": "/vulnerabilities/CVE-2021-37663/46270",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37689",
            "id": "pyup.io-46296",
            "more_info_path": "/vulnerabilities/CVE-2021-37689/46296",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37681",
            "id": "pyup.io-46288",
            "more_info_path": "/vulnerabilities/CVE-2021-37681/46288",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37667",
            "id": "pyup.io-46274",
            "more_info_path": "/vulnerabilities/CVE-2021-37667/46274",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37648",
            "id": "pyup.io-46255",
            "more_info_path": "/vulnerabilities/CVE-2021-37648/46255",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37657",
            "id": "pyup.io-46264",
            "more_info_path": "/vulnerabilities/CVE-2021-37657/46264",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37656",
            "id": "pyup.io-46263",
            "more_info_path": "/vulnerabilities/CVE-2021-37656/46263",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37645",
            "id": "pyup.io-46252",
            "more_info_path": "/vulnerabilities/CVE-2021-37645/46252",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37644",
            "id": "pyup.io-46251",
            "more_info_path": "/vulnerabilities/CVE-2021-37644/46251",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37641",
            "id": "pyup.io-46248",
            "more_info_path": "/vulnerabilities/CVE-2021-37641/46248",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37639",
            "id": "pyup.io-46246",
            "more_info_path": "/vulnerabilities/CVE-2021-37639/46246",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37637",
            "id": "pyup.io-46244",
            "more_info_path": "/vulnerabilities/CVE-2021-37637/46244",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37640",
            "id": "pyup.io-46247",
            "more_info_path": "/vulnerabilities/CVE-2021-37640/46247",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37636",
            "id": "pyup.io-46243",
            "more_info_path": "/vulnerabilities/CVE-2021-37636/46243",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37669",
            "id": "pyup.io-46276",
            "more_info_path": "/vulnerabilities/CVE-2021-37669/46276",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.1 updates its dependency 'TensorFlow' to v2.6.0 to include security fixes.",
            "cve": "CVE-2021-37655",
            "id": "pyup.io-46262",
            "more_info_path": "/vulnerabilities/CVE-2021-37655/46262",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-22924",
            "id": "pyup.io-46303",
            "more_info_path": "/vulnerabilities/CVE-2021-22924/46303",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41225",
            "id": "pyup.io-46336",
            "more_info_path": "/vulnerabilities/CVE-2021-41225/46336",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-22923",
            "id": "pyup.io-46302",
            "more_info_path": "/vulnerabilities/CVE-2021-22923/46302",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41226",
            "id": "pyup.io-46337",
            "more_info_path": "/vulnerabilities/CVE-2021-41226/46337",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41212",
            "id": "pyup.io-46323",
            "more_info_path": "/vulnerabilities/CVE-2021-41212/46323",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41216",
            "id": "pyup.io-46327",
            "more_info_path": "/vulnerabilities/CVE-2021-41216/46327",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41200",
            "id": "pyup.io-46311",
            "more_info_path": "/vulnerabilities/CVE-2021-41200/46311",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41196",
            "id": "pyup.io-46307",
            "more_info_path": "/vulnerabilities/CVE-2021-41196/46307",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41203",
            "id": "pyup.io-46314",
            "more_info_path": "/vulnerabilities/CVE-2021-41203/46314",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41205",
            "id": "pyup.io-46316",
            "more_info_path": "/vulnerabilities/CVE-2021-41205/46316",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41204",
            "id": "pyup.io-46315",
            "more_info_path": "/vulnerabilities/CVE-2021-41204/46315",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41208",
            "id": "pyup.io-46319",
            "more_info_path": "/vulnerabilities/CVE-2021-41208/46319",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41206",
            "id": "pyup.io-46317",
            "more_info_path": "/vulnerabilities/CVE-2021-41206/46317",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-22925",
            "id": "pyup.io-46304",
            "more_info_path": "/vulnerabilities/CVE-2021-22925/46304",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41213",
            "id": "pyup.io-46324",
            "more_info_path": "/vulnerabilities/CVE-2021-41213/46324",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41210",
            "id": "pyup.io-46321",
            "more_info_path": "/vulnerabilities/CVE-2021-41210/46321",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41221",
            "id": "pyup.io-46332",
            "more_info_path": "/vulnerabilities/CVE-2021-41221/46332",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41219",
            "id": "pyup.io-46330",
            "more_info_path": "/vulnerabilities/CVE-2021-41219/46330",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41209",
            "id": "pyup.io-46320",
            "more_info_path": "/vulnerabilities/CVE-2021-41209/46320",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41228",
            "id": "pyup.io-46339",
            "more_info_path": "/vulnerabilities/CVE-2021-41228/46339",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-22922",
            "id": "pyup.io-46300",
            "more_info_path": "/vulnerabilities/CVE-2021-22922/46300",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41214",
            "id": "pyup.io-46325",
            "more_info_path": "/vulnerabilities/CVE-2021-41214/46325",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-22926",
            "id": "pyup.io-46305",
            "more_info_path": "/vulnerabilities/CVE-2021-22926/46305",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41223",
            "id": "pyup.io-46334",
            "more_info_path": "/vulnerabilities/CVE-2021-41223/46334",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41224",
            "id": "pyup.io-46335",
            "more_info_path": "/vulnerabilities/CVE-2021-41224/46335",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41211",
            "id": "pyup.io-46322",
            "more_info_path": "/vulnerabilities/CVE-2021-41211/46322",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41201",
            "id": "pyup.io-46312",
            "more_info_path": "/vulnerabilities/CVE-2021-41201/46312",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41197",
            "id": "pyup.io-46308",
            "more_info_path": "/vulnerabilities/CVE-2021-41197/46308",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41195",
            "id": "pyup.io-46306",
            "more_info_path": "/vulnerabilities/CVE-2021-41195/46306",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41207",
            "id": "pyup.io-46318",
            "more_info_path": "/vulnerabilities/CVE-2021-41207/46318",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41227",
            "id": "pyup.io-46338",
            "more_info_path": "/vulnerabilities/CVE-2021-41227/46338",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41220",
            "id": "pyup.io-46331",
            "more_info_path": "/vulnerabilities/CVE-2021-41220/46331",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41202",
            "id": "pyup.io-46313",
            "more_info_path": "/vulnerabilities/CVE-2021-41202/46313",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41218",
            "id": "pyup.io-46329",
            "more_info_path": "/vulnerabilities/CVE-2021-41218/46329",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41217",
            "id": "pyup.io-46328",
            "more_info_path": "/vulnerabilities/CVE-2021-41217/46328",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41215",
            "id": "pyup.io-46326",
            "more_info_path": "/vulnerabilities/CVE-2021-41215/46326",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41199",
            "id": "pyup.io-46310",
            "more_info_path": "/vulnerabilities/CVE-2021-41199/46310",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41198",
            "id": "pyup.io-46309",
            "more_info_path": "/vulnerabilities/CVE-2021-41198/46309",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.12.4 updates its dependency 'TensorFlow' to v2.6.1 to include security fixes.",
            "cve": "CVE-2021-41222",
            "id": "pyup.io-46333",
            "more_info_path": "/vulnerabilities/CVE-2021-41222/46333",
            "specs": [
                "<0.12.4"
            ],
            "v": "<0.12.4"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23569",
            "id": "pyup.io-46370",
            "more_info_path": "/vulnerabilities/CVE-2022-23569/46370",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23558",
            "id": "pyup.io-46359",
            "more_info_path": "/vulnerabilities/CVE-2022-23558/46359",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21732",
            "id": "pyup.io-46348",
            "more_info_path": "/vulnerabilities/CVE-2022-21732/46348",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23578",
            "id": "pyup.io-46379",
            "more_info_path": "/vulnerabilities/CVE-2022-23578/46379",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2020-10531",
            "id": "pyup.io-46340",
            "more_info_path": "/vulnerabilities/CVE-2020-10531/46340",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21736",
            "id": "pyup.io-46352",
            "more_info_path": "/vulnerabilities/CVE-2022-21736/46352",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23566",
            "id": "pyup.io-46367",
            "more_info_path": "/vulnerabilities/CVE-2022-23566/46367",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23593",
            "id": "pyup.io-46394",
            "more_info_path": "/vulnerabilities/CVE-2022-23593/46394",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23577",
            "id": "pyup.io-46378",
            "more_info_path": "/vulnerabilities/CVE-2022-23577/46378",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21734",
            "id": "pyup.io-46350",
            "more_info_path": "/vulnerabilities/CVE-2022-21734/46350",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23587",
            "id": "pyup.io-46388",
            "more_info_path": "/vulnerabilities/CVE-2022-23587/46388",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23575",
            "id": "pyup.io-46376",
            "more_info_path": "/vulnerabilities/CVE-2022-23575/46376",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23560",
            "id": "pyup.io-46361",
            "more_info_path": "/vulnerabilities/CVE-2022-23560/46361",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23588",
            "id": "pyup.io-46389",
            "more_info_path": "/vulnerabilities/CVE-2022-23588/46389",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23579",
            "id": "pyup.io-46380",
            "more_info_path": "/vulnerabilities/CVE-2022-23579/46380",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23561",
            "id": "pyup.io-46362",
            "more_info_path": "/vulnerabilities/CVE-2022-23561/46362",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23570",
            "id": "pyup.io-46371",
            "more_info_path": "/vulnerabilities/CVE-2022-23570/46371",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21739",
            "id": "pyup.io-46355",
            "more_info_path": "/vulnerabilities/CVE-2022-21739/46355",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23580",
            "id": "pyup.io-46381",
            "more_info_path": "/vulnerabilities/CVE-2022-23580/46381",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23564",
            "id": "pyup.io-46365",
            "more_info_path": "/vulnerabilities/CVE-2022-23564/46365",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23595",
            "id": "pyup.io-46396",
            "more_info_path": "/vulnerabilities/CVE-2022-23595/46396",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21740",
            "id": "pyup.io-46356",
            "more_info_path": "/vulnerabilities/CVE-2022-21740/46356",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21733",
            "id": "pyup.io-46349",
            "more_info_path": "/vulnerabilities/CVE-2022-21733/46349",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21741",
            "id": "pyup.io-46357",
            "more_info_path": "/vulnerabilities/CVE-2022-21741/46357",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23594",
            "id": "pyup.io-46395",
            "more_info_path": "/vulnerabilities/CVE-2022-23594/46395",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23592",
            "id": "pyup.io-46393",
            "more_info_path": "/vulnerabilities/CVE-2022-23592/46393",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23591",
            "id": "pyup.io-46392",
            "more_info_path": "/vulnerabilities/CVE-2022-23591/46392",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23590",
            "id": "pyup.io-46391",
            "more_info_path": "/vulnerabilities/CVE-2022-23590/46391",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23589",
            "id": "pyup.io-46390",
            "more_info_path": "/vulnerabilities/CVE-2022-23589/46390",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23586",
            "id": "pyup.io-46387",
            "more_info_path": "/vulnerabilities/CVE-2022-23586/46387",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23585",
            "id": "pyup.io-46386",
            "more_info_path": "/vulnerabilities/CVE-2022-23585/46386",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23584",
            "id": "pyup.io-46385",
            "more_info_path": "/vulnerabilities/CVE-2022-23584/46385",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23583",
            "id": "pyup.io-46384",
            "more_info_path": "/vulnerabilities/CVE-2022-23583/46384",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23582",
            "id": "pyup.io-46383",
            "more_info_path": "/vulnerabilities/CVE-2022-23582/46383",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23581",
            "id": "pyup.io-46382",
            "more_info_path": "/vulnerabilities/CVE-2022-23581/46382",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23576",
            "id": "pyup.io-46377",
            "more_info_path": "/vulnerabilities/CVE-2022-23576/46377",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23573",
            "id": "pyup.io-46374",
            "more_info_path": "/vulnerabilities/CVE-2022-23573/46374",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23572",
            "id": "pyup.io-46373",
            "more_info_path": "/vulnerabilities/CVE-2022-23572/46373",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23574",
            "id": "pyup.io-46375",
            "more_info_path": "/vulnerabilities/CVE-2022-23574/46375",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23565",
            "id": "pyup.io-46366",
            "more_info_path": "/vulnerabilities/CVE-2022-23565/46366",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23571",
            "id": "pyup.io-46372",
            "more_info_path": "/vulnerabilities/CVE-2022-23571/46372",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23563",
            "id": "pyup.io-46364",
            "more_info_path": "/vulnerabilities/CVE-2022-23563/46364",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23562",
            "id": "pyup.io-46363",
            "more_info_path": "/vulnerabilities/CVE-2022-23562/46363",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23559",
            "id": "pyup.io-46360",
            "more_info_path": "/vulnerabilities/CVE-2022-23559/46360",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23557",
            "id": "pyup.io-46358",
            "more_info_path": "/vulnerabilities/CVE-2022-23557/46358",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21729",
            "id": "pyup.io-46345",
            "more_info_path": "/vulnerabilities/CVE-2022-21729/46345",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23567",
            "id": "pyup.io-46368",
            "more_info_path": "/vulnerabilities/CVE-2022-23567/46368",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21727",
            "id": "pyup.io-46343",
            "more_info_path": "/vulnerabilities/CVE-2022-21727/46343",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21728",
            "id": "pyup.io-46344",
            "more_info_path": "/vulnerabilities/CVE-2022-21728/46344",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21726",
            "id": "pyup.io-46342",
            "more_info_path": "/vulnerabilities/CVE-2022-21726/46342",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21738",
            "id": "pyup.io-46354",
            "more_info_path": "/vulnerabilities/CVE-2022-21738/46354",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21735",
            "id": "pyup.io-46351",
            "more_info_path": "/vulnerabilities/CVE-2022-21735/46351",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21731",
            "id": "pyup.io-46347",
            "more_info_path": "/vulnerabilities/CVE-2022-21731/46347",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-23568",
            "id": "pyup.io-46369",
            "more_info_path": "/vulnerabilities/CVE-2022-23568/46369",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21730",
            "id": "pyup.io-46346",
            "more_info_path": "/vulnerabilities/CVE-2022-21730/46346",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21737",
            "id": "pyup.io-46353",
            "more_info_path": "/vulnerabilities/CVE-2022-21737/46353",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        },
        {
            "advisory": "Pupyl 0.13.2 updates its dependency 'TensorFlow' to v2.8.0 to include security fixes.",
            "cve": "CVE-2022-21725",
            "id": "pyup.io-46341",
            "more_info_path": "/vulnerabilities/CVE-2022-21725/46341",
            "specs": [
                "<0.13.2"
            ],
            "v": "<0.13.2"
        }
    ],
    "purdy": [
        {
            "advisory": "Purdy 1.8.0 updates minimum dependency version for 'Pygments' to v2.9.1 to include security fixes.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-49030",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/49030",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        },
        {
            "advisory": "Purdy 1.8.0 updates minimum dependency version for 'Pygments' to v2.9.1 to include security fixes.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-40435",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/40435",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        }
    ],
    "pushradar": [
        {
            "advisory": "Pushradar 3.0.0alpha.2 includes a patch to make the channel authentication more secure.",
            "cve": "PVE-2021-39630",
            "id": "pyup.io-39630",
            "more_info_path": "/vulnerabilities/PVE-2021-39630/39630",
            "specs": [
                "<3.0.0alpha.2",
                "<3.0.0a2"
            ],
            "v": "<3.0.0alpha.2,<3.0.0a2"
        }
    ],
    "pvops": [
        {
            "advisory": "Pvops 0.4.0 starts requiring 'nltk>=3.9.1' to include a security fix.",
            "cve": "CVE-2024-39705",
            "id": "pyup.io-73875",
            "more_info_path": "/vulnerabilities/CVE-2024-39705/73875",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "pwd": [
        {
            "advisory": "pwd  is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/",
            "cve": "PVE-2021-34983",
            "id": "pyup.io-34983",
            "more_info_path": "/vulnerabilities/PVE-2021-34983/34983",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "pwdsphinx": [
        {
            "advisory": "Pwdsphinx 0.5 uses a new protocol to execute mgt functions. The previous protocol had a number of security issues.",
            "cve": "PVE-2022-44893",
            "id": "pyup.io-44893",
            "more_info_path": "/vulnerabilities/PVE-2022-44893/44893",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        }
    ],
    "pwman3": [
        {
            "advisory": "pwman3 before 0.4.0 uses cPickle.loads and cPickle.dumps.",
            "cve": "PVE-2021-26029",
            "id": "pyup.io-26029",
            "more_info_path": "/vulnerabilities/PVE-2021-26029/26029",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "pwntools": [
        {
            "advisory": "The shellcraft generator in pwntools before 4.3.1 is vulnerable to Server-Side Template Injection (SSTI), which can lead to remote code execution. See CVE-2020-28468.",
            "cve": "CVE-2020-28468",
            "id": "pyup.io-39426",
            "more_info_path": "/vulnerabilities/CVE-2020-28468/39426",
            "specs": [
                "<4.3.1"
            ],
            "v": "<4.3.1"
        }
    ],
    "py": [
        {
            "advisory": "** DISPUTED ** Py throughout 1.11.0 allows remote attackers to conduct a ReDoS (Regular expression Denial of Service) attack via a Subversion repository with crafted info data because the InfoSvnCommand argument is mishandled.\r\nhttps://github.com/pytest-dev/py/issues/287",
            "cve": "CVE-2022-42969",
            "id": "pyup.io-51457",
            "more_info_path": "/vulnerabilities/CVE-2022-42969/51457",
            "specs": [
                "<=1.11.0"
            ],
            "v": "<=1.11.0"
        },
        {
            "advisory": "Py 1.10.0 includes a fix for CVE-2020-29651: A denial of service via regular expression in the py.path.svnwc component of py (aka python-py) through 1.9.0 could be used by attackers to cause a compute-time denial of service attack by supplying malicious input to the blame functionality.",
            "cve": "CVE-2020-29651",
            "id": "pyup.io-39253",
            "more_info_path": "/vulnerabilities/CVE-2020-29651/39253",
            "specs": [
                "<=1.9.0"
            ],
            "v": "<=1.9.0"
        }
    ],
    "py-bcrypt": [
        {
            "advisory": "The py-bcrypt module before 0.3 for Python does not properly handle concurrent memory access, which allows attackers to bypass authentication via multiple authentication requests, which trigger the password hash to be overwritten. See: CVE-2013-1895.",
            "cve": "CVE-2013-1895",
            "id": "pyup.io-37747",
            "more_info_path": "/vulnerabilities/CVE-2013-1895/37747",
            "specs": [
                "<0.3"
            ],
            "v": "<0.3"
        }
    ],
    "py-ci": [
        {
            "advisory": "Py-ci 0.5.2 upgrades versions of requests and jinja2 due to security alerts. See: .",
            "cve": "PVE-2021-37333",
            "id": "pyup.io-37333",
            "more_info_path": "/vulnerabilities/PVE-2021-37333/37333",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        }
    ],
    "py-cord": [
        {
            "advisory": "Py-cord 2.0.1 includes a fix for CVE-2022-36024: This issue allows users to be able to remotely shutdown the bot running on py-cord, via adding it to a discord server with the 'application.commands' scope but not the 'bot' scope - then executing a command in that server. Currently, it appears that all public bots that use slash commands are affected.\r\nhttps://github.com/Pycord-Development/pycord/security/advisories/GHSA-qmhj-m29v-gvmr",
            "cve": "CVE-2022-36024",
            "id": "pyup.io-50675",
            "more_info_path": "/vulnerabilities/CVE-2022-36024/50675",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        }
    ],
    "py-espeak-ng": [
        {
            "advisory": "py-espeak-ng 1.49.0 fixes many logic and security issues reported by clang scan-build, Coverity and msvc /analyze.",
            "cve": "PVE-2021-36322",
            "id": "pyup.io-36322",
            "more_info_path": "/vulnerabilities/PVE-2021-36322/36322",
            "specs": [
                "<1.49.0"
            ],
            "v": "<1.49.0"
        }
    ],
    "py-evm": [
        {
            "advisory": "Py-EVM v0.2.0-alpha.33 allows attackers to make a vm.execute_bytecode call that triggers computation._stack.values with '\"stack\": [100, 100, 0]' where b'\\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to \"smart contracts can be executed indefinitely without gas being paid.\"",
            "cve": "CVE-2018-18920",
            "id": "pyup.io-42252",
            "more_info_path": "/vulnerabilities/CVE-2018-18920/42252",
            "specs": [
                "<0.2.0a33"
            ],
            "v": "<0.2.0a33"
        }
    ],
    "py-geth": [
        {
            "advisory": "Py-geth 3.10.0 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.",
            "cve": "CVE-2007-4559",
            "id": "pyup.io-51543",
            "more_info_path": "/vulnerabilities/CVE-2007-4559/51543",
            "specs": [
                "<3.10.0"
            ],
            "v": "<3.10.0"
        }
    ],
    "py-gfm": [
        {
            "advisory": "Py-gfm version 0.28.3.gfm.12 includes various security and bug fixes.",
            "cve": "PVE-2021-38621",
            "id": "pyup.io-38621",
            "more_info_path": "/vulnerabilities/PVE-2021-38621/38621",
            "specs": [
                "<0.28.3.gfm.12"
            ],
            "v": "<0.28.3.gfm.12"
        }
    ],
    "py-manage-nginx": [
        {
            "advisory": "Py-manage-nginx fixes a zip archive extraction traversal vulnerability.",
            "cve": "PVE-2025-79915",
            "id": "pyup.io-79915",
            "more_info_path": "/vulnerabilities/PVE-2025-79915/79915",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "py-mini-racer": [
        {
            "advisory": "A heap overflow in Sqreen PyMiniRacer (aka Python Mini Racer) before 0.3.0 allows remote attackers to potentially exploit heap corruption.",
            "cve": "CVE-2020-25489",
            "id": "pyup.io-42285",
            "more_info_path": "/vulnerabilities/CVE-2020-25489/42285",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "py-ms": [
        {
            "advisory": "py-ms 1.0.1 replaces Jaeger with Lightstep - improved security.",
            "cve": "PVE-2021-36875",
            "id": "pyup.io-36875",
            "more_info_path": "/vulnerabilities/PVE-2021-36875/36875",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        },
        {
            "advisory": "Py-ms version 2.8.0 updates its anyconfig dependency from \"anyconfig>=0.9.11\" to \"anyconfig>=0.10.0\" to address a security issue related to unsafe loading in PyYAML.",
            "cve": "PVE-2024-71186",
            "id": "pyup.io-71186",
            "more_info_path": "/vulnerabilities/PVE-2024-71186/71186",
            "specs": [
                "<2.8.0"
            ],
            "v": "<2.8.0"
        }
    ],
    "py-pure-client": [
        {
            "advisory": "Py-pure-client 1.27.0 updates its dependency 'pyjwt' to version '2.4.0' to include a fix for a Use of a Broken or Risky Cryptographic Algorithm vulnerability.\r\nhttps://github.com/PureStorage-OpenConnect/py-pure-client/commit/02a2f9d12b76ecbd57a951b9bedbe0cd77ba08ab",
            "cve": "CVE-2022-29217",
            "id": "pyup.io-59995",
            "more_info_path": "/vulnerabilities/CVE-2022-29217/59995",
            "specs": [
                "<1.27.0"
            ],
            "v": "<1.27.0"
        },
        {
            "advisory": "Py-pure-client 2.29 and prior versions ship with vulnerable dependencies (urllib3 >= 1.26.17).",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-63006",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/63006",
            "specs": [
                "<2.29"
            ],
            "v": "<2.29"
        }
    ],
    "py-quantaq": [
        {
            "advisory": "Py-quantaq 1.2.0a0 updates its dependency 'urllib3' to v1.26.12 to include security fixes.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-50893",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/50893",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Py-quantaq 1.2.0a0 updates its dependency 'urllib3' to v1.26.12 to include security fixes.",
            "cve": "CVE-2018-20060",
            "id": "pyup.io-50902",
            "more_info_path": "/vulnerabilities/CVE-2018-20060/50902",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Py-quantaq 1.2.0a0 updates its dependency 'numpy' to v1.23.2 to include security fixes.",
            "cve": "CVE-2021-41496",
            "id": "pyup.io-50904",
            "more_info_path": "/vulnerabilities/CVE-2021-41496/50904",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Py-quantaq 1.2.0a0 updates its dependency 'numpy' to v1.23.2 to include security fixes.",
            "cve": "CVE-2021-33430",
            "id": "pyup.io-50903",
            "more_info_path": "/vulnerabilities/CVE-2021-33430/50903",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Py-quantaq 1.2.0a0 updates its dependency 'numpy' to v1.23.2 to include security fixes.",
            "cve": "CVE-2021-41495",
            "id": "pyup.io-50905",
            "more_info_path": "/vulnerabilities/CVE-2021-41495/50905",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Py-quantaq 1.2.0a0 updates its dependency 'urllib3' to v1.26.12 to include security fixes.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-50900",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/50900",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Py-quantaq 1.2.0a0 updates its dependency 'urllib3' to v1.26.12 to include security fixes.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-50901",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/50901",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Py-quantaq 1.2.0a0 updates its dependency 'numpy' to v1.23.2 to include security fixes.",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-50906",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/50906",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Py-quantaq 1.3.0 updates its dependency 'urllib3' to v1.26.12 to include security fixes.",
            "cve": "CVE-2018-25091",
            "id": "pyup.io-62528",
            "more_info_path": "/vulnerabilities/CVE-2018-25091/62528",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Py-quantaq 1.3.0 updates its dependency 'urllib3' to v1.26.12 to include security fixes.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-62557",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/62557",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "py-rate": [
        {
            "advisory": "The luigi functionality before py-rate 0.3.0 was reported as vulnerable.",
            "cve": "PVE-2021-37312",
            "id": "pyup.io-37312",
            "more_info_path": "/vulnerabilities/PVE-2021-37312/37312",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "py-scdb": [
        {
            "advisory": "Py-scdb 0.1.1 updates its CARGO dependency 'clokwerk' to v0.4.0 to include a fix for a transitive vulnerability in 'time' package.",
            "cve": "CVE-2020-26235",
            "id": "pyup.io-52791",
            "more_info_path": "/vulnerabilities/CVE-2020-26235/52791",
            "specs": [
                "<0.1.1"
            ],
            "v": "<0.1.1"
        }
    ],
    "py-serializable": [
        {
            "advisory": "Py-serializable 0.11.1 uses defusedxml to prevent XXE attacks.\r\nhttps://github.com/madpah/serializable/pull/5",
            "cve": "PVE-2023-53541",
            "id": "pyup.io-53541",
            "more_info_path": "/vulnerabilities/PVE-2023-53541/53541",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        }
    ],
    "py-steamcmd-wrapper": [
        {
            "advisory": "Py-steamcmd-wrapper 1.0.6 includes a security fix for the 'urllib3' underlying dependency.\r\nhttps://github.com/wmellema/Py-SteamCMD-Wrapper/commit/8ee7e1144b9df570547a294638efcec464adb342",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-40780",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/40780",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        }
    ],
    "py-swagger-ui": [
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses versions of 'swagger-ui' (2.2.10, 3.52.0) with potential transitive vulnerabilities.\r\nhttps://github.com/swagger-api/swagger-ui/commit/31626145c08e75b1d765975ca6e5616fe721e03d",
            "cve": "PVE-2023-52705",
            "id": "pyup.io-52705",
            "more_info_path": "/vulnerabilities/PVE-2023-52705/52705",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses versions of 'swagger-ui' (2.2.10, 3.52.0) with a known docker image Node.js vulnerability.\r\nhttps://github.com/swagger-api/swagger-ui/commit/325909fb6a87a2022487be7a58c41f5857fdf761",
            "cve": "PVE-2023-52704",
            "id": "pyup.io-52704",
            "more_info_path": "/vulnerabilities/PVE-2023-52704/52704",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with a potential transitive vulnerability.\r\nhttps://github.com/swagger-api/swagger-ui/commit/5628ff02f4da4fcc77aaf808466be9550bef2cbe",
            "cve": "CVE-2018-20834",
            "id": "pyup.io-52713",
            "more_info_path": "/vulnerabilities/CVE-2018-20834/52713",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with a known XSS vulnerability.\r\nhttps://github.com/swagger-api/swagger-ui/commit/1e184e8e218676278c83e60a45846c199ce3d15e",
            "cve": "PVE-2023-52714",
            "id": "pyup.io-52714",
            "more_info_path": "/vulnerabilities/PVE-2023-52714/52714",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses versions of 'swagger-ui' (2.2.10, 3.52.0) with a potential transitive vulnerability.\r\nhttps://github.com/swagger-api/swagger-ui/commit/6c417e490185cb6c0e8855d642f9666d5e6f9bf0",
            "cve": "PVE-2023-52698",
            "id": "pyup.io-52698",
            "more_info_path": "/vulnerabilities/PVE-2023-52698/52698",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses versions of 'swagger-ui' (2.2.10, 3.52.0) with potential transitive vulnerabilities.\r\nhttps://github.com/swagger-api/swagger-ui/commit/5029b815602dcfa87cc422031a75260c6e7a9ed4",
            "cve": "PVE-2023-52703",
            "id": "pyup.io-52703",
            "more_info_path": "/vulnerabilities/PVE-2023-52703/52703",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with potential transitive vulnerabilities.\r\nhttps://github.com/swagger-api/swagger-ui/compare/v3.37.2...v3.38.0",
            "cve": "PVE-2023-52707",
            "id": "pyup.io-52707",
            "more_info_path": "/vulnerabilities/PVE-2023-52707/52707",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with a potential transitive vulnerability.\r\nhttps://github.com/swagger-api/swagger-ui/commit/a26bb9284de375e338987b13ad7a1270372e245c",
            "cve": "PVE-2023-52708",
            "id": "pyup.io-52708",
            "more_info_path": "/vulnerabilities/PVE-2023-52708/52708",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with a potential transitive vulnerability.\r\nhttps://github.com/swagger-api/swagger-ui/commit/9e294fbab55a7c4974d7a8eb56534f39ec3a9f63",
            "cve": "PVE-2023-52709",
            "id": "pyup.io-52709",
            "more_info_path": "/vulnerabilities/PVE-2023-52709/52709",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with a potential vulnerability in the Markdown renderer.\r\nhttps://github.com/swagger-api/swagger-ui/commit/a616cb471d31f04a28d185aeb1bcb83637afc3cf",
            "cve": "PVE-2023-52710",
            "id": "pyup.io-52710",
            "more_info_path": "/vulnerabilities/PVE-2023-52710/52710",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with a known vulnerability in anchor tags.\r\nhttps://github.com/swagger-api/swagger-ui/pull/4789",
            "cve": "PVE-2023-52717",
            "id": "pyup.io-52717",
            "more_info_path": "/vulnerabilities/PVE-2023-52717/52717",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with a potential transitive vulnerability.\r\nhttps://github.com/swagger-api/swagger-ui/commit/558d054986d58b029e5ac2db5f350219ef4d578b",
            "cve": "PVE-2023-52718",
            "id": "pyup.io-52718",
            "more_info_path": "/vulnerabilities/PVE-2023-52718/52718",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with a known XSS vulnerability.\r\nhttps://github.com/swagger-api/swagger-ui/commit/afa615e01dc7f6724d20a11abfe1fcdf8f6ecd57",
            "cve": "PVE-2023-52721",
            "id": "pyup.io-52721",
            "more_info_path": "/vulnerabilities/PVE-2023-52721/52721",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses versions of 'swagger-ui' (2.2.10, 3.52.0) that expose hostnames to build fragments.\r\nhttps://github.com/swagger-api/swagger-ui/pull/7491",
            "cve": "PVE-2023-52735",
            "id": "pyup.io-52735",
            "more_info_path": "/vulnerabilities/PVE-2023-52735/52735",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses versions of 'swagger-ui' (2.2.10, 3.52.0) with a known vulnerability: including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.\r\nhttps://github.com/swagger-api/swagger-ui/security/advisories/GHSA-qrmm-w75w-3wpx",
            "cve": "CVE-2018-25031",
            "id": "pyup.io-52736",
            "more_info_path": "/vulnerabilities/CVE-2018-25031/52736",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses a version of 'swagger-ui' (2.2.10) with a known CSS vulnerability.",
            "cve": "CVE-2019-17495",
            "id": "pyup.io-52712",
            "more_info_path": "/vulnerabilities/CVE-2019-17495/52712",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Py-swagger-ui before 1.1.0 uses versions of 'swagger-ui' (2.2.10, 3.52.0) with a known vulnerability: including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.\r\nhttps://github.com/swagger-api/swagger-ui/security/advisories/GHSA-qrmm-w75w-3wpx",
            "cve": "CVE-2021-46708",
            "id": "pyup.io-52699",
            "more_info_path": "/vulnerabilities/CVE-2021-46708/52699",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "py-trello-api": [
        {
            "advisory": "Py-trello-api 0.4.2 introduces an optional PyOpenSSL import for versions of Python older than 2.7.9 and 3.2, aiming to address security concerns related to OpenSSL as highlighted by CVE-2023-6129.",
            "cve": "CVE-2023-6129",
            "id": "pyup.io-67416",
            "more_info_path": "/vulnerabilities/CVE-2023-6129/67416",
            "specs": [
                "<0.4.2"
            ],
            "v": "<0.4.2"
        }
    ],
    "py-xml": [
        {
            "advisory": "py-xml v1.0 was discovered to contain an XML External Entity Injection (XXE) vulnerability which allows attackers to execute arbitrary code via a crafted XML file.",
            "cve": "CVE-2020-26709",
            "id": "pyup.io-65852",
            "more_info_path": "/vulnerabilities/CVE-2020-26709/65852",
            "specs": [
                "<=1.0"
            ],
            "v": "<=1.0"
        }
    ],
    "py2play": [
        {
            "advisory": "Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles and executes.",
            "cve": "CVE-2005-2875",
            "id": "pyup.io-66882",
            "more_info_path": "/vulnerabilities/CVE-2005-2875/66882",
            "specs": [
                ">=0,<=0.1.8"
            ],
            "v": ">=0,<=0.1.8"
        }
    ],
    "py2sambvca": [
        {
            "advisory": "Py2sambvca 1.3.1 fixes a possible directory traversal vulnerability.\r\nhttps://github.com/JacksonBurns/py2sambvca/issues/17",
            "cve": "PVE-2022-49573",
            "id": "pyup.io-49573",
            "more_info_path": "/vulnerabilities/PVE-2022-49573/49573",
            "specs": [
                "<1.3.1"
            ],
            "v": "<1.3.1"
        }
    ],
    "py3web": [
        {
            "advisory": "Py3web before 0.21 isn't checking for bad characters in headers.",
            "cve": "PVE-2017-45642",
            "id": "pyup.io-45642",
            "more_info_path": "/vulnerabilities/PVE-2017-45642/45642",
            "specs": [
                "<0.21"
            ],
            "v": "<0.21"
        }
    ],
    "py42": [
        {
            "advisory": "Py42 drops support for Python versions 2.7 and 3.5, that no longer receive security updates.",
            "cve": "CVE-2020-27619",
            "id": "pyup.io-43361",
            "more_info_path": "/vulnerabilities/CVE-2020-27619/43361",
            "specs": [
                "<1.17.0"
            ],
            "v": "<1.17.0"
        },
        {
            "advisory": "Py42 drops support for Python versions 2.7 and 3.5, that no longer receive security updates.",
            "cve": "CVE-2021-23336",
            "id": "pyup.io-42125",
            "more_info_path": "/vulnerabilities/CVE-2021-23336/42125",
            "specs": [
                "<1.17.0"
            ],
            "v": "<1.17.0"
        },
        {
            "advisory": "Py42 1.17.0 drops support for Python versions 2.7 and 3.5, that no longer receive security updates.",
            "cve": "CVE-2019-20907",
            "id": "pyup.io-43360",
            "more_info_path": "/vulnerabilities/CVE-2019-20907/43360",
            "specs": [
                "<1.17.0"
            ],
            "v": "<1.17.0"
        },
        {
            "advisory": "Py42 drops support for Python versions 2.7 and 3.5, that no longer receive security updates.",
            "cve": "CVE-2021-3177",
            "id": "pyup.io-43359",
            "more_info_path": "/vulnerabilities/CVE-2021-3177/43359",
            "specs": [
                "<1.17.0"
            ],
            "v": "<1.17.0"
        },
        {
            "advisory": "Py42 1.17.0 drops support for Python versions 2.7 and 3.5, that no longer receive security updates.",
            "cve": "CVE-2021-3737",
            "id": "pyup.io-43362",
            "more_info_path": "/vulnerabilities/CVE-2021-3737/43362",
            "specs": [
                "<1.17.0"
            ],
            "v": "<1.17.0"
        },
        {
            "advisory": "Py42 version 1.5.1 no longer logs the http requests headers in debug output.",
            "cve": "PVE-2021-42133",
            "id": "pyup.io-42133",
            "more_info_path": "/vulnerabilities/PVE-2021-42133/42133",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        }
    ],
    "py4sync": [
        {
            "advisory": "Py4sync is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html",
            "cve": "PVE-2023-52916",
            "id": "pyup.io-52916",
            "more_info_path": "/vulnerabilities/PVE-2023-52916/52916",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "py7zr": [
        {
            "advisory": "Py7zr 0.17.3 protects against directory traversal attacks by checking file paths in ArchiveFile.\r\nhttps://github.com/miurahr/py7zr/commit/2cb066688b05ee7427f236fd35f5598112e9d501",
            "cve": "PVE-2022-44652",
            "id": "pyup.io-44652",
            "more_info_path": "/vulnerabilities/PVE-2022-44652/44652",
            "specs": [
                "<0.17.3"
            ],
            "v": "<0.17.3"
        },
        {
            "advisory": "Py7zr 0.20.1 adds protection against path traversal attacks.\r\nhttps://github.com/miurahr/py7zr/commit/1bb43f17515c7f69673a1c88ab9cc72a7bbef406",
            "cve": "PVE-2022-51631",
            "id": "pyup.io-51631",
            "more_info_path": "/vulnerabilities/PVE-2022-51631/51631",
            "specs": [
                "<0.20.1"
            ],
            "v": "<0.20.1"
        },
        {
            "advisory": "Py7zr fixes a bug related to symbolic link operations in a multi-threading environment. Previously, when Py7zr operated on symbolic links with the context of changing the working directory, it caused errors in file operations for other threads. This issue was particularly problematic in multi-threaded applications, where simultaneous file operations could lead to conflicts and errors.",
            "cve": "PVE-2024-71884",
            "id": "pyup.io-71884",
            "more_info_path": "/vulnerabilities/PVE-2024-71884/71884",
            "specs": [
                "<0.6"
            ],
            "v": "<0.6"
        },
        {
            "advisory": "Py7zr 0.6b5 includes a fix for a CWE-214: Invocation of Process Using Visible Sensitive Information.\r\nhttps://github.com/miurahr/py7zr/issues/59",
            "cve": "PVE-2023-62184",
            "id": "pyup.io-62184",
            "more_info_path": "/vulnerabilities/PVE-2023-62184/62184",
            "specs": [
                "<0.6b5"
            ],
            "v": "<0.6b5"
        },
        {
            "advisory": "Py7zr 0.20.1 includes a fix for CVE-2022-44900: A directory traversal vulnerability in the SevenZipFile.extractall() function of the python library py7zr v0.20.0 and earlier allows attackers to write arbitrary files via extracting a crafted 7z file.",
            "cve": "CVE-2022-44900",
            "id": "pyup.io-52349",
            "more_info_path": "/vulnerabilities/CVE-2022-44900/52349",
            "specs": [
                "<=0.20.0"
            ],
            "v": "<=0.20.0"
        }
    ],
    "pyamf": [
        {
            "advisory": "XML external entity (XXE) vulnerability in PyAMF before 0.8.0 allows remote attackers to cause a denial of service or read arbitrary files via a crafted Action Message Format (AMF) payload.",
            "cve": "CVE-2015-8549",
            "id": "pyup.io-54676",
            "more_info_path": "/vulnerabilities/CVE-2015-8549/54676",
            "specs": [
                ">=0,<0.8.0"
            ],
            "v": ">=0,<0.8.0"
        }
    ],
    "pyanchor": [
        {
            "advisory": "Pyanchor version 0.5.1 updates its dependency 'lxml' to v4.6.3 to include security fixes.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-41900",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/41900",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Pyanchor version 0.5.1 updates its dependency 'py' to v1.10.0 to include a security fix.",
            "cve": "CVE-2020-29651",
            "id": "pyup.io-49121",
            "more_info_path": "/vulnerabilities/CVE-2020-29651/49121",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Pyanchor version 0.5.1 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-49122",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/49122",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Pyanchor version 0.5.1 updates its dependency 'lxml' to v4.6.3 to include security fixes.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-49120",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/49120",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Pyanchor 0.6.0 updates its dependency 'lxml' to v4.6.5 to include a security fix.",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-49789",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/49789",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "pyanxdns": [
        {
            "advisory": "Pyanxdns 0.2.5 and prior contain a backdoor due to the presence of the malicious 'request' dependency.\r\nhttps://www.bleepingcomputer.com/news/security/pypi-package-keep-mistakenly-included-a-password-stealer/",
            "cve": "CVE-2022-30882",
            "id": "pyup.io-49431",
            "more_info_path": "/vulnerabilities/CVE-2022-30882/49431",
            "specs": [
                "<0.2.5"
            ],
            "v": "<0.2.5"
        }
    ],
    "pyanyapi": [
        {
            "advisory": "An exploitable vulnerability exists in the YAML parsing functionality in the YAMLParser method in Interfaces.py in PyAnyAPI before 0.6.1. A YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.",
            "cve": "CVE-2017-16616",
            "id": "pyup.io-35719",
            "more_info_path": "/vulnerabilities/CVE-2017-16616/35719",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        }
    ],
    "pyapp": [
        {
            "advisory": "From pyapp version 4.5.0, TLS 1.2 is required by default for HTTPS connections to fetch remote configuration.",
            "cve": "PVE-2021-41227",
            "id": "pyup.io-41227",
            "more_info_path": "/vulnerabilities/PVE-2021-41227/41227",
            "specs": [
                "<4.5.0"
            ],
            "v": "<4.5.0"
        }
    ],
    "pyarchery": [
        {
            "advisory": "In Archery before 1.3, inserting an XSS payload into a project name (either by creating a new project or editing an existing one) will result in stored XSS on the vulnerability-scan scheduling page.",
            "cve": "CVE-2019-20008",
            "id": "pyup.io-54165",
            "more_info_path": "/vulnerabilities/CVE-2019-20008/54165",
            "specs": [
                ">=0,<1.3.0"
            ],
            "v": ">=0,<1.3.0"
        }
    ],
    "pyarmor": [
        {
            "advisory": "pyarmor 5.1.2 Improves the security of PyArmor self",
            "cve": "PVE-2021-36853",
            "id": "pyup.io-36853",
            "more_info_path": "/vulnerabilities/PVE-2021-36853/36853",
            "specs": [
                "<5.1.2"
            ],
            "v": "<5.1.2"
        },
        {
            "advisory": "Pyarmor version 6.3.0 refines its algorithm to improve security:\r\n- Default cross protection code\r\n- Runtime files, removes 'license.lic' and 'pytransform.key'\r\n- Pack command\r\n- Obfuscating process for cross platforms\r\n- Adds common option '--boot' for special cross platform obfuscating",
            "cve": "PVE-2021-41844",
            "id": "pyup.io-41844",
            "more_info_path": "/vulnerabilities/PVE-2021-41844/41844",
            "specs": [
                "<6.3.0"
            ],
            "v": "<6.3.0"
        },
        {
            "advisory": "Pyarmor 6.3.4 improves the security of core dynamic libraries.",
            "cve": "PVE-2021-41843",
            "id": "pyup.io-41843",
            "more_info_path": "/vulnerabilities/PVE-2021-41843/41843",
            "specs": [
                "<6.3.4"
            ],
            "v": "<6.3.4"
        },
        {
            "advisory": "Pyarmor version 6.4.0 improves the security of restrict mode.",
            "cve": "PVE-2021-41841",
            "id": "pyup.io-41841",
            "more_info_path": "/vulnerabilities/PVE-2021-41841/41841",
            "specs": [
                "<6.4.0"
            ],
            "v": "<6.4.0"
        },
        {
            "advisory": "Pyarmor version 6.6.2 improves the security of restrict mode and 'assert_armored' for super mode.",
            "cve": "PVE-2021-41839",
            "id": "pyup.io-41839",
            "more_info_path": "/vulnerabilities/PVE-2021-41839/41839",
            "specs": [
                "<6.6.2"
            ],
            "v": "<6.6.2"
        },
        {
            "advisory": "Pyarmor 6.7.0 improves the security of 'check_armored' for super mode (only for the purchased version).",
            "cve": "PVE-2021-41838",
            "id": "pyup.io-41838",
            "more_info_path": "/vulnerabilities/PVE-2021-41838/41838",
            "specs": [
                "<6.7.0"
            ],
            "v": "<6.7.0"
        }
    ],
    "pyarrow": [
        {
            "advisory": "While investigating UBSAN errors in https://github.com/apache/arrow/pull/5365 it was discovered Apache Arrow versions 0.12.0 to 0.14.1 left memory Array data uninitialized when reading RLE null data from parquet. This affected the C++, Python, Ruby and R implementations. The uninitialized memory could potentially be shared if are transmitted over the wire (for instance with Flight) or persisted in the streaming IPC and file formats.",
            "cve": "CVE-2019-12410",
            "id": "pyup.io-37761",
            "more_info_path": "/vulnerabilities/CVE-2019-12410/37761",
            "specs": [
                ">=0.12.0,<=0.14.1"
            ],
            "v": ">=0.12.0,<=0.14.1"
        },
        {
            "advisory": "It was discovered that the C++ implementation (which underlies the R, Python and Ruby implementations) of Apache Arrow 0.14.0 to 0.14.1 had a uninitialized memory bug when building arrays with null values in some cases. This can lead to uninitialized memory being unintentionally shared if Arrow Arrays are transmitted over the wire (for instance with Flight) or persisted in the streaming IPC and file formats.",
            "cve": "CVE-2019-12408",
            "id": "pyup.io-37760",
            "more_info_path": "/vulnerabilities/CVE-2019-12408/37760",
            "specs": [
                ">=0.14.0,<=0.14.1"
            ],
            "v": ">=0.14.0,<=0.14.1"
        },
        {
            "advisory": "Deserialization of untrusted data in IPC and Parquet readers in PyArrow versions 0.14.0 to 14.0.0 allows arbitrary code execution. An application is vulnerable if it reads Arrow IPC, Feather or Parquet data from untrusted sources (for example user-supplied input files). This vulnerability only affects PyArrow, not other Apache Arrow implementations or bindings. It is recommended that users of PyArrow upgrade to 14.0.1. Similarly, it is recommended that downstream libraries upgrade their dependency requirements to PyArrow 14.0.1 or later. PyPI packages are already available, and we hope that conda-forge packages will be available soon. If it is not possible to upgrade, we provide a separate package `pyarrow-hotfix` that disables the vulnerability on older PyArrow versions. See  https://pypi.org/project/pyarrow-hotfix/  for instructions.",
            "cve": "CVE-2023-47248",
            "id": "pyup.io-65501",
            "more_info_path": "/vulnerabilities/CVE-2023-47248/65501",
            "specs": [
                ">=0.14.0,<=14.0.0"
            ],
            "v": ">=0.14.0,<=14.0.0"
        }
    ],
    "pyasn1": [
        {
            "advisory": "Affected versions of the pyasn1 package are vulnerable to Denial of Service (DoS) due to unbounded decoding of malformed RELATIVE-OID values with excessive continuation octets. In pyasn1/codec/ber/decoder.py, the BER decoder logic is used by pyasn1.codec.ber.decoder.decode() grows the RELATIVE-OID/OBJECT IDENTIFIER value via the reloid += ((subId << 7) + nextSubId,) accumulation without enforcing a reasonable limit on the number of continuation octets or the resulting object size, which can trigger memory exhaustion during parsing.",
            "cve": "CVE-2026-23490",
            "id": "pyup.io-84605",
            "more_info_path": "/vulnerabilities/CVE-2026-23490/84605",
            "specs": [
                "==0.6.1"
            ],
            "v": "==0.6.1"
        }
    ],
    "pyautogiu": [
        {
            "advisory": "Pyautogiu is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51749",
            "id": "pyup.io-51749",
            "more_info_path": "/vulnerabilities/PVE-2022-51749/51749",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pyav": [
        {
            "advisory": "Pyav 9.0.1 updates bundled binary wheels to fix vulnerabilities in dependencies openjpeg, ffmpeg, gnutls, libgmp and wavpack.\r\nhttps://github.com/PyAV-Org/PyAV/issues/901",
            "cve": "PVE-2023-61575",
            "id": "pyup.io-61575",
            "more_info_path": "/vulnerabilities/PVE-2023-61575/61575",
            "specs": [
                "<9.0.1"
            ],
            "v": "<9.0.1"
        },
        {
            "advisory": "Pyav 9.1.0 updates bundled binary wheels to fix vulnerabilities in dependencies vorbis, libass and libxml2.\r\nhttps://github.com/PyAV-Org/PyAV/issues/921",
            "cve": "PVE-2023-61574",
            "id": "pyup.io-61574",
            "more_info_path": "/vulnerabilities/PVE-2023-61574/61574",
            "specs": [
                "<9.1.0"
            ],
            "v": "<9.1.0"
        }
    ],
    "pyb-utils": [
        {
            "advisory": "Pyb-utils 1.3.1 updates its dependency 'pillow' to v10.0.1 to include a security fix.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61614",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61614",
            "specs": [
                "<1.3.1"
            ],
            "v": "<1.3.1"
        }
    ],
    "pybald": [
        {
            "advisory": "Pybald 0.5.6 updates its dependency 'SQLAlachemy' to v1.3.3 to include a security fix.",
            "cve": "CVE-2019-7548",
            "id": "pyup.io-42486",
            "more_info_path": "/vulnerabilities/CVE-2019-7548/42486",
            "specs": [
                "<0.5.6"
            ],
            "v": "<0.5.6"
        },
        {
            "advisory": "Pybald 0.5.6 updates its dependency 'SQLAlachemy' to v1.3.3 to include a security fix.",
            "cve": "CVE-2019-7164",
            "id": "pyup.io-37104",
            "more_info_path": "/vulnerabilities/CVE-2019-7164/37104",
            "specs": [
                "<0.5.6"
            ],
            "v": "<0.5.6"
        }
    ],
    "pybb": [
        {
            "advisory": "benjjvi/PyBB is an open source bulletin board. Prior to commit dcaeccd37198ecd3e41ea766d1099354b60d69c2, benjjvi/PyBB is vulnerable to SQL Injection. This vulnerability has been fixed as of commit dcaeccd37198ecd3e41ea766d1099354b60d69c2. As a workaround, a user may be able to update the software manually to avoid this problem by sanitizing user queries to `BulletinDatabaseModule.py`.",
            "cve": "CVE-2023-34249",
            "id": "pyup.io-64673",
            "more_info_path": "/vulnerabilities/CVE-2023-34249/64673",
            "specs": [
                "<=0.1.0"
            ],
            "v": "<=0.1.0"
        }
    ],
    "pybeerxml": [
        {
            "advisory": "Pybeerxml 1.0.8 updates its dependency 'bleach' to v3.1.4 to include security fixes.",
            "cve": "CVE-2020-6816",
            "id": "pyup.io-48325",
            "more_info_path": "/vulnerabilities/CVE-2020-6816/48325",
            "specs": [
                "<1.0.8"
            ],
            "v": "<1.0.8"
        },
        {
            "advisory": "Pybeerxml 1.0.8 updates its dependency 'bleach' to v3.1.4 to include security fixes.",
            "cve": "CVE-2020-6817",
            "id": "pyup.io-48324",
            "more_info_path": "/vulnerabilities/CVE-2020-6817/48324",
            "specs": [
                "<1.0.8"
            ],
            "v": "<1.0.8"
        },
        {
            "advisory": "Pybeerxml 1.0.8 updates its dependency 'urllib3' to v1.24.2 to include a security fix.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-38251",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/38251",
            "specs": [
                "<1.0.8"
            ],
            "v": "<1.0.8"
        },
        {
            "advisory": "Pybeerxml 1.0.8 updates its dependency 'bleach' to v3.1.4 to include security fixes.",
            "cve": "CVE-2020-6802",
            "id": "pyup.io-48326",
            "more_info_path": "/vulnerabilities/CVE-2020-6802/48326",
            "specs": [
                "<1.0.8"
            ],
            "v": "<1.0.8"
        }
    ],
    "pybible-cli": [
        {
            "advisory": "Version 1.1.2: Bible pickle files have been replaced by JSON files for better performance and security.",
            "cve": "PVE-2021-38043",
            "id": "pyup.io-38043",
            "more_info_path": "/vulnerabilities/PVE-2021-38043/38043",
            "specs": [
                "<1.1.2"
            ],
            "v": "<1.1.2"
        }
    ],
    "pybit-proxy": [
        {
            "advisory": "Pybit-proxy 2.2.2rc1 includes a fix for a bug where, upon WSS disconnection, pybit rapidly tries to re-establish the connection, which results in being banned by the CDN for malicious activity\r\nhttps://github.com/bybit-exchange/pybit/commit/6220d7e99716dad175c877ffde23aebeef2b3979",
            "cve": "PVE-2023-62663",
            "id": "pyup.io-62663",
            "more_info_path": "/vulnerabilities/PVE-2023-62663/62663",
            "specs": [
                "<2.2.2rc1"
            ],
            "v": "<2.2.2rc1"
        }
    ],
    "pybluemonday": [
        {
            "advisory": "Pybluemonday 0.0.10 updates its GO dependency 'bluemonday' to version '1.0.23' to fix a vulnerability.\r\nhttps://github.com/ColdHeat/pybluemonday/pull/36",
            "cve": "PVE-2023-59604",
            "id": "pyup.io-59604",
            "more_info_path": "/vulnerabilities/PVE-2023-59604/59604",
            "specs": [
                "<0.0.10"
            ],
            "v": "<0.0.10"
        },
        {
            "advisory": "Pybluemonday 0.0.8 includes a fix for CVE-2021-42576: The bluemonday sanitizer before 1.0.16 for Go, and before 0.0.8 for Python (in pybluemonday), does not properly enforce policies associated with the SELECT, STYLE, and OPTION elements.\r\nhttps://docs.google.com/document/d/11SoX296sMS0XoQiQbpxc5pNxSdbJKDJkm5BDv0zrX50",
            "cve": "CVE-2021-42576",
            "id": "pyup.io-42176",
            "more_info_path": "/vulnerabilities/CVE-2021-42576/42176",
            "specs": [
                "<0.0.8"
            ],
            "v": "<0.0.8"
        }
    ],
    "pyboolector": [
        {
            "advisory": "In parser/btorsmt2.c in Boolector 3.0.0, opening a specially crafted input file leads to a use after free in get_failed_assumptions or btor_delete.\r\nhttps://github.com/Boolector/boolector/commit/8d979d02e0482c7137c9f3a34e6d430dbfd1f5c5",
            "cve": "CVE-2019-7560",
            "id": "pyup.io-42269",
            "more_info_path": "/vulnerabilities/CVE-2019-7560/42269",
            "specs": [
                "<3.1.0"
            ],
            "v": "<3.1.0"
        }
    ],
    "pybotx": [
        {
            "advisory": "Pybotx 0.55.3 updates its dependency 'requests' to v2.31.0 to include a security fix.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-58908",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/58908",
            "specs": [
                "<0.55.3"
            ],
            "v": "<0.55.3"
        },
        {
            "advisory": "Pybotx 0.55.3 updates its dependency 'fastapy' to v0.95.2 to include a security fix.",
            "cve": "PVE-2023-58713",
            "id": "pyup.io-58906",
            "more_info_path": "/vulnerabilities/PVE-2023-58713/58906",
            "specs": [
                "<0.55.3"
            ],
            "v": "<0.55.3"
        }
    ],
    "pyca": [
        {
            "advisory": "Pyca 3.3 includes a configurable, random delay for ingests to avoid accidental DDoS  attacks.",
            "cve": "PVE-2021-39215",
            "id": "pyup.io-39215",
            "more_info_path": "/vulnerabilities/PVE-2021-39215/39215",
            "specs": [
                "<3.3"
            ],
            "v": "<3.3"
        }
    ],
    "pycape": [
        {
            "advisory": "Pycape 3.0.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.",
            "cve": "CVE-2022-4203",
            "id": "pyup.io-53121",
            "more_info_path": "/vulnerabilities/CVE-2022-4203/53121",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Pycape 3.0.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.",
            "cve": "CVE-2022-3996",
            "id": "pyup.io-53124",
            "more_info_path": "/vulnerabilities/CVE-2022-3996/53124",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Pycape 3.0.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.",
            "cve": "CVE-2022-4450",
            "id": "pyup.io-53122",
            "more_info_path": "/vulnerabilities/CVE-2022-4450/53122",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Pycape 3.0.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.",
            "cve": "CVE-2022-4304",
            "id": "pyup.io-53119",
            "more_info_path": "/vulnerabilities/CVE-2022-4304/53119",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Pycape 3.0.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.",
            "cve": "CVE-2023-23931",
            "id": "pyup.io-53123",
            "more_info_path": "/vulnerabilities/CVE-2023-23931/53123",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Pycape 3.0.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.",
            "cve": "CVE-2023-0215",
            "id": "pyup.io-53067",
            "more_info_path": "/vulnerabilities/CVE-2023-0215/53067",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Pycape 3.0.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.",
            "cve": "CVE-2023-0286",
            "id": "pyup.io-53118",
            "more_info_path": "/vulnerabilities/CVE-2023-0286/53118",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Pycape 3.0.0 updates its dependency 'cryptography' to v39.0.1 to include security fixes.",
            "cve": "CVE-2023-0216",
            "id": "pyup.io-53120",
            "more_info_path": "/vulnerabilities/CVE-2023-0216/53120",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        }
    ],
    "pycapnp": [
        {
            "advisory": "Pycapnp 0.5.5 updates its dependency libcapnp to version '0.5.1.2' to include a fix for an Uncontrolled Resource Consumption vulnerability.\r\nhttps://github.com/capnproto/pycapnp/commit/2027bac43493fe4fa8bdfcf8a80ef67a3bdb085d",
            "cve": "CVE-2015-2313",
            "id": "pyup.io-26030",
            "more_info_path": "/vulnerabilities/CVE-2015-2313/26030",
            "specs": [
                "<0.5.5"
            ],
            "v": "<0.5.5"
        }
    ],
    "pycapnp-async": [
        {
            "advisory": "Pycapnp-async 0.5.4 updates the bundled C++ libcapnp to v0.5.1.1 security release.",
            "cve": "CVE-2015-2311",
            "id": "pyup.io-49051",
            "more_info_path": "/vulnerabilities/CVE-2015-2311/49051",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pycapnp-async 0.5.4 updates the bundled C++ libcapnp to v0.5.1.1 security release.",
            "cve": "CVE-2015-2310",
            "id": "pyup.io-37586",
            "more_info_path": "/vulnerabilities/CVE-2015-2310/37586",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pycapnp-async 0.5.4 updates the bundled C++ libcapnp to v0.5.1.1 security release.",
            "cve": "CVE-2015-2312",
            "id": "pyup.io-49052",
            "more_info_path": "/vulnerabilities/CVE-2015-2312/49052",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pycapnp-async 0.5.5 updates the bundled C++ libcapnp to v0.5.1.2 security release.",
            "cve": "CVE-2015-2313",
            "id": "pyup.io-37585",
            "more_info_path": "/vulnerabilities/CVE-2015-2313/37585",
            "specs": [
                "<0.5.5"
            ],
            "v": "<0.5.5"
        }
    ],
    "pycaption": [
        {
            "advisory": "Pycaption 2.1.0 updates its dependency 'lxml' requirement to '>=4.9.1' to include a security fix.",
            "cve": "CVE-2022-2309",
            "id": "pyup.io-50934",
            "more_info_path": "/vulnerabilities/CVE-2022-2309/50934",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        }
    ],
    "pycares": [
        {
            "advisory": "Pycares before 2.1.1 is vulnerable to CVE-2016-5180.\r\nhttps://github.com/saghul/pycares/commit/0115c819d9ed876999c4f116f8b155ec503e57bc",
            "cve": "CVE-2016-5180",
            "id": "pyup.io-26031",
            "more_info_path": "/vulnerabilities/CVE-2016-5180/26031",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Use-After-Free attacks due to a race condition between Python's garbage collector and c-ares callback execution during Channel object destruction. The Channel object's __del__() method fails to properly synchronize with pending DNS queries, leading to premature destruction of callback references stored via ffi.new_handle() while c-ares is still executing post-callback cleanup code.",
            "cve": "PVE-2025-77741",
            "id": "pyup.io-77741",
            "more_info_path": "/vulnerabilities/PVE-2025-77741/77741",
            "specs": [
                "<4.9.0"
            ],
            "v": "<4.9.0"
        },
        {
            "advisory": "Pycares versions < 4.2.0 are affected by CVE-2021-3672: Improper Neutralization of Null Byte or NUL Character.\r\nhttps://github.com/saghul/pycares/security/advisories/GHSA-c58j-88f5-h53f",
            "cve": "CVE-2021-3672",
            "id": "pyup.io-55194",
            "more_info_path": "/vulnerabilities/CVE-2021-3672/55194",
            "specs": [
                ">=0,<4.2.0"
            ],
            "v": ">=0,<4.2.0"
        }
    ],
    "pyccel": [
        {
            "advisory": "Pyccel version 1.9.0 addresses a race condition issue within its `ndarrays` folder handling during the compilation process on macOS, enhancing the stability and reliability of the compilation.\r\n#Note: It only affects macOS users.\r\nhttps://github.com/pyccel/pyccel/pull/1445",
            "cve": "PVE-2024-65275",
            "id": "pyup.io-65275",
            "more_info_path": "/vulnerabilities/PVE-2024-65275/65275",
            "specs": [
                "<1.9.0"
            ],
            "v": "<1.9.0"
        }
    ],
    "pycel": [
        {
            "advisory": "Affected versions of the LMDeploy package are vulnerable to Code Injection due to improper input handling in the documentation configuration file. The Open function in lmdeploy/docs/en/conf.py fails to properly sanitize user-controlled input before executing it, allowing arbitrary code to be injected and executed within the Python interpreter context.",
            "cve": "CVE-2024-53924",
            "id": "pyup.io-78839",
            "more_info_path": "/vulnerabilities/CVE-2024-53924/78839",
            "specs": [
                "<=1.0b30"
            ],
            "v": "<=1.0b30"
        }
    ],
    "pycfmodel": [
        {
            "advisory": "Pycfmodel 1.0.1 updates its dependency 'certifi' to include a security fix.",
            "cve": "CVE-2024-39689",
            "id": "pyup.io-75693",
            "more_info_path": "/vulnerabilities/CVE-2024-39689/75693",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        }
    ],
    "pycln": [
        {
            "advisory": "Pycln 0.0.1alpha.3 mentions: \"C wrapped modules import star expanding related vulnerability by hadialqattan\"",
            "cve": "PVE-2021-38857",
            "id": "pyup.io-38857",
            "more_info_path": "/vulnerabilities/PVE-2021-38857/38857",
            "specs": [
                "<0.0.1alpha.3"
            ],
            "v": "<0.0.1alpha.3"
        }
    ],
    "pycmarkgfm": [
        {
            "advisory": "Pycmarkgfm 1.2.0 and prior versions rely on 'cmark-gfm' v0.29.0.gfm.6, which is vulnerable to a polynomial time complexity issue.\r\nhttps://github.com/zopieux/pycmarkgfm/blob/2c31829e37b9d9be26d442e4a3cc0bbcdc9670a8/generated/cmark-gfm_version.h#L5",
            "cve": "CVE-2023-26485",
            "id": "pyup.io-54814",
            "more_info_path": "/vulnerabilities/CVE-2023-26485/54814",
            "specs": [
                "<=1.2.0"
            ],
            "v": "<=1.2.0"
        }
    ],
    "pycolmap": [
        {
            "advisory": "Pycolmap 0.4.0 and prior releases ship with a version of C library 'libwebp' which is affected by a high risk vulnerability.\r\nhttps://inspector.pypi.io/project/pycolmap/0.4.0/packages/4b/bb/90fb7e73617694c411c95f48dd51125f4eb6fa7baf16164ac730bd494809/pycolmap-0.4.0-cp310-cp310-manylinux2014_x86_64.whl",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61942",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61942",
            "specs": [
                ">=0.2.0,<=0.4.0"
            ],
            "v": ">=0.2.0,<=0.4.0"
        }
    ],
    "pycolorz": [
        {
            "advisory": "Pycolorz is a malicious package. It downloads and executes obfuscated code.\r\nhttps://inspector.pypi.io/project/pycolorz/0.0.6/packages/5c/3e/2db21b0e3f13f8930798b5e94a3018a76ce310eba4aeebfb5eed82f75880/pycolorz-0.0.6.tar.gz/pycolorz-0.0.6/setup.py#line.29",
            "cve": "PVE-2023-53562",
            "id": "pyup.io-53562",
            "more_info_path": "/vulnerabilities/PVE-2023-53562/53562",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "pyconau-funtimes": [
        {
            "advisory": "Pyconau-funtimes is a typosquatting package. It shows a malicious behavior, for example, it may leak your sensitive data and/or gain unauthorized persistence in your system.\r\nhttps://www.zdnet.com/article/twelve-malicious-python-libraries-found-and-removed-from-pypi/",
            "cve": "PVE-2022-45423",
            "id": "pyup.io-45423",
            "more_info_path": "/vulnerabilities/PVE-2022-45423/45423",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "pyconll": [
        {
            "advisory": "Pyconll 1.1.0 updates 'requests' dependency to v2.20.0 due to a security flaw.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36647",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36647",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "pyconll before 1.1.2 the ``requests`` version used in ``requirements.txt`` was insecure.",
            "cve": "PVE-2021-36763",
            "id": "pyup.io-36763",
            "more_info_path": "/vulnerabilities/PVE-2021-36763/36763",
            "specs": [
                "<1.1.2"
            ],
            "v": "<1.1.2"
        }
    ],
    "pycontw-report-generator": [
        {
            "advisory": "Pycontw-Report-Generator version 1.5.0 includes a fix for the function 'read_yaml' in 'report_generator/io/yaml.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/pycontw/pycontw-postevent-report-generator/commit/f872f9f207e7a6f14e04ff77ca49922c6a0839b4",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41372",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41372",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        }
    ],
    "pycookiecheat": [
        {
            "advisory": "Pycookiecheat 0.2.0 makes SQL query more secure by avoiding string formatting.",
            "cve": "PVE-2021-26729",
            "id": "pyup.io-26729",
            "more_info_path": "/vulnerabilities/PVE-2021-26729/26729",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        },
        {
            "advisory": "Pycookiecheat 0.4.5 went back to using cryptography due to CVE-2013-7459.",
            "cve": "CVE-2013-7459",
            "id": "pyup.io-37543",
            "more_info_path": "/vulnerabilities/CVE-2013-7459/37543",
            "specs": [
                "<0.4.5"
            ],
            "v": "<0.4.5"
        }
    ],
    "pycrowdtangle": [
        {
            "advisory": "The PyCrowdTangle package in PyPI before v0.0.1 included a code execution backdoor inserted by a third party.",
            "cve": "CVE-2022-34981",
            "id": "pyup.io-54454",
            "more_info_path": "/vulnerabilities/CVE-2022-34981/54454",
            "specs": [
                ">=0.0.1,<0.0.3"
            ],
            "v": ">=0.0.1,<0.0.3"
        }
    ],
    "pycrtsh": [
        {
            "advisory": "Pycrtsh 0.3.4 upgrades the 'lxml' dependency from 4.5.1 to 4.6.2 following a security bug.",
            "cve": "PVE-2021-40087",
            "id": "pyup.io-40087",
            "more_info_path": "/vulnerabilities/PVE-2021-40087/40087",
            "specs": [
                "<0.3.4"
            ],
            "v": "<0.3.4"
        }
    ],
    "pycryptex": [
        {
            "advisory": "Pycryptex 0.5.0 adds new config keys (***secure-deletion*** and ***secure-deletion-passes***) to set securely deletion of clear files in encryption operations.",
            "cve": "PVE-2021-39109",
            "id": "pyup.io-39109",
            "more_info_path": "/vulnerabilities/PVE-2021-39109/39109",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        }
    ],
    "pycrypto": [
        {
            "advisory": "Pycrypto version 2.6 includes a fix for CVE-2012-2417: PyCrypto before 2.6 does not produce appropriate prime numbers when using an ElGamal scheme to generate a key, which reduces the signature space or public key space and makes it easier for attackers to conduct brute force attacks to obtain the private key.\r\nhttps://github.com/Legrandin/pycrypto/commit/9f912f13df99ad3421eff360d6a62d7dbec755c2",
            "cve": "CVE-2012-2417",
            "id": "pyup.io-26032",
            "more_info_path": "/vulnerabilities/CVE-2012-2417/26032",
            "specs": [
                "<2.6"
            ],
            "v": "<2.6"
        },
        {
            "advisory": "The Crypto.Random.atfork function in PyCrypto before 2.6.1 does not properly reseed the pseudo-random number generator (PRNG) before allowing a child process to access it, which makes it easier for context-dependent attackers to obtain sensitive information by leveraging a race condition in which a child process is created and accesses the PRNG within the same rate-limit period as another process.",
            "cve": "CVE-2013-1445",
            "id": "pyup.io-33150",
            "more_info_path": "/vulnerabilities/CVE-2013-1445/33150",
            "specs": [
                "<2.6.1"
            ],
            "v": "<2.6.1"
        },
        {
            "advisory": "lib/Crypto/PublicKey/ElGamal.py in PyCrypto through 2.6.1 generates weak ElGamal key parameters, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for PyCrypto's ElGamal implementation.",
            "cve": "CVE-2018-6594",
            "id": "pyup.io-35765",
            "more_info_path": "/vulnerabilities/CVE-2018-6594/35765",
            "specs": [
                "<2.6.1"
            ],
            "v": "<2.6.1"
        },
        {
            "advisory": "Heap-based buffer overflow in the ALGnew function in block_templace.c in Python Cryptography Toolkit (aka pycrypto) 2.6.1 allows remote attackers to execute arbitrary code as demonstrated by a crafted iv parameter to cryptmsg.py.",
            "cve": "CVE-2013-7459",
            "id": "pyup.io-35015",
            "more_info_path": "/vulnerabilities/CVE-2013-7459/35015",
            "specs": [
                "<=2.6.1"
            ],
            "v": "<=2.6.1"
        }
    ],
    "pycryptodome": [
        {
            "advisory": "Pycryptodome 3.10.3 improves robustness of PKCS1v1.5 decryption against timing attacks.\r\nhttps://github.com/Legrandin/pycryptodome/commit/853054937e29e6cd3dc61228be1dc768b688460b",
            "cve": "PVE-2021-41775",
            "id": "pyup.io-41775",
            "more_info_path": "/vulnerabilities/PVE-2021-41775/41775",
            "specs": [
                "<3.10.3"
            ],
            "v": "<3.10.3"
        },
        {
            "advisory": "Pycryptodome version 3.11.0 includes a fix for the DSA construction algorithm. Modulus \"p\" primality check wasn't working.\r\nhttps://github.com/Legrandin/pycryptodome/pull/557/commits/183f8d1c7a5e145e78b86fb54da7e327a277d9c6",
            "cve": "PVE-2021-42084",
            "id": "pyup.io-42084",
            "more_info_path": "/vulnerabilities/PVE-2021-42084/42084",
            "specs": [
                "<3.11.0"
            ],
            "v": "<3.11.0"
        },
        {
            "advisory": "Pycryptodome 3.20.0 addresses a vulnerability in the OAEP decryption process, which previously had a side-channel leakage issue. This vulnerability could potentially be exploited through a Manger attack, a type of cryptographic attack. The resolution of this issue enhances the security of the library, especially in its handling of OAEP decryption.\r\nhttps://github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd",
            "cve": "PVE-2024-63680",
            "id": "pyup.io-63680",
            "more_info_path": "/vulnerabilities/PVE-2024-63680/63680",
            "specs": [
                "<3.20.0"
            ],
            "v": "<3.20.0"
        },
        {
            "advisory": "Pycryptodome 3.4.4 removes implementation of deprecated and unsafe PGP \"quick check\".\r\nhttps://github.com/Legrandin/pycryptodome/commit/f80debf2d26cfd7f30dae95f2b2a893d3a34ee8c",
            "cve": "PVE-2022-50730",
            "id": "pyup.io-50730",
            "more_info_path": "/vulnerabilities/PVE-2022-50730/50730",
            "specs": [
                "<3.4.4"
            ],
            "v": "<3.4.4"
        },
        {
            "advisory": "Pycryptodome before 3.6.6 has a vulnerability on AESNI ECB with payloads smaller than 16 bytes.",
            "cve": "CVE-2018-15560",
            "id": "pyup.io-36384",
            "more_info_path": "/vulnerabilities/CVE-2018-15560/36384",
            "specs": [
                "<3.6.6"
            ],
            "v": "<3.6.6"
        },
        {
            "advisory": "PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.",
            "cve": "CVE-2023-52323",
            "id": "pyup.io-65207",
            "more_info_path": "/vulnerabilities/CVE-2023-52323/65207",
            "specs": [
                ">=0,<3.19.1"
            ],
            "v": ">=0,<3.19.1"
        }
    ],
    "pycryptodomex": [
        {
            "advisory": "Pycryptodomex 3.10.3 improves robustness of PKCS1v1.5 decryption against timing attacks.\r\nhttps://github.com/Legrandin/pycryptodome/commit/853054937e29e6cd3dc61228be1dc768b688460b",
            "cve": "PVE-2021-41775",
            "id": "pyup.io-48152",
            "more_info_path": "/vulnerabilities/PVE-2021-41775/48152",
            "specs": [
                "<3.10.3"
            ],
            "v": "<3.10.3"
        },
        {
            "advisory": "Pycryptodomex 3.11.0 includes a fix for the DSA construction algorithm. Modulus \"p\" primality check wasn't working.\r\nhttps://github.com/Legrandin/pycryptodome/pull/557/commits/183f8d1c7a5e145e78b86fb54da7e327a277d9c6",
            "cve": "PVE-2021-42084",
            "id": "pyup.io-47201",
            "more_info_path": "/vulnerabilities/PVE-2021-42084/47201",
            "specs": [
                "<3.11.0"
            ],
            "v": "<3.11.0"
        },
        {
            "advisory": "Pycryptodomex 3.4.4 removes implementation of deprecated and unsafe PGP \"quick check\".\r\nhttps://github.com/Legrandin/pycryptodome/commit/f80debf2d26cfd7f30dae95f2b2a893d3a34ee8c",
            "cve": "PVE-2022-50730",
            "id": "pyup.io-50731",
            "more_info_path": "/vulnerabilities/PVE-2022-50730/50731",
            "specs": [
                "<3.4.4"
            ],
            "v": "<3.4.4"
        },
        {
            "advisory": "Pycryptodomex before 3.6.6 has a vulnerability on AESNI ECB with payloads smaller than 16 bytes.",
            "cve": "CVE-2018-15560",
            "id": "pyup.io-48153",
            "more_info_path": "/vulnerabilities/CVE-2018-15560/48153",
            "specs": [
                "<3.6.6"
            ],
            "v": "<3.6.6"
        },
        {
            "advisory": "PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.",
            "cve": "CVE-2023-52323",
            "id": "pyup.io-65208",
            "more_info_path": "/vulnerabilities/CVE-2023-52323/65208",
            "specs": [
                ">=0,<3.19.1"
            ],
            "v": ">=0,<3.19.1"
        }
    ],
    "pycsw": [
        {
            "advisory": "A SQL injection vulnerability in pycsw all versions before 2.0.2, 1.10.5 and 1.8.6 that leads to read and extract of any data from any table in the pycsw database that the database user has access to. Also on PostgreSQL (at least) it is possible to perform updates/inserts/deletes and database modifications to any table the database user has access to.",
            "cve": "CVE-2016-8640",
            "id": "pyup.io-36365",
            "more_info_path": "/vulnerabilities/CVE-2016-8640/36365",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        }
    ],
    "pycurl": [
        {
            "advisory": "Pycurl 7.45.5 builds wheels with curl 8.12.1 to include security fixes.",
            "cve": "CVE-2025-0167",
            "id": "pyup.io-75761",
            "more_info_path": "/vulnerabilities/CVE-2025-0167/75761",
            "specs": [
                "<7.45.5"
            ],
            "v": "<7.45.5"
        },
        {
            "advisory": "Pycurl 7.45.5 builds wheels with curl 8.12.1 to include security fixes.",
            "cve": "CVE-2025-0665",
            "id": "pyup.io-75760",
            "more_info_path": "/vulnerabilities/CVE-2025-0665/75760",
            "specs": [
                "<7.45.5"
            ],
            "v": "<7.45.5"
        },
        {
            "advisory": "Pycurl 7.45.5 builds wheels with curl 8.12.1 to include security fixes.",
            "cve": "CVE-2025-0725",
            "id": "pyup.io-75752",
            "more_info_path": "/vulnerabilities/CVE-2025-0725/75752",
            "specs": [
                "<7.45.5"
            ],
            "v": "<7.45.5"
        }
    ],
    "pydaisy": [
        {
            "advisory": "Pydaisy version 0.2.4 includes a security patch for the function 'run' in 'pydaisy/Daisy.py'. It contained an OS injection vulnerability: subprocess call with shell=True.\r\nhttps://github.com/JacobGudbjerg/PyDaisy/commit/dda90389c71825a032309a248d0db2fefed12b49#diff-12d1b472f9ba3e2c87d6f76c94a5fc08346bfbc131abfdf1ab4181680cb41c7e",
            "cve": "PVE-2021-41373",
            "id": "pyup.io-41373",
            "more_info_path": "/vulnerabilities/PVE-2021-41373/41373",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        }
    ],
    "pydal": [
        {
            "advisory": "pydal before 15.02.27 has a security flaw which could lead to db password storing in cache.\r\nhttps://github.com/web2py/pydal/commit/85b4911ebda688d85a6ada5835ea73ea6c4fea09",
            "cve": "PVE-2021-33022",
            "id": "pyup.io-33022",
            "more_info_path": "/vulnerabilities/PVE-2021-33022/33022",
            "specs": [
                "<15.02.27"
            ],
            "v": "<15.02.27"
        }
    ],
    "pydantic": [
        {
            "advisory": "Pydantic 1.10.13 and 2.4.0 include a fix for a regular expression denial of service vulnerability (REDoS).\r\nhttps://github.com/pydantic/pydantic/pull/7360\r\nhttps://github.com/pydantic/pydantic/pull/7673",
            "cve": "PVE-2023-61416",
            "id": "pyup.io-61416",
            "more_info_path": "/vulnerabilities/PVE-2023-61416/61416",
            "specs": [
                "<1.10.13",
                ">=2.0a1,<2.4.0"
            ],
            "v": "<1.10.13,>=2.0a1,<2.4.0"
        },
        {
            "advisory": "Pydantic 1.10.2 prevents long strings as int inputs to fix CVE-2020-10735.\r\nhttps://github.com/pydantic/pydantic/commit/eccd85e4d012e70ffbd81f379179da900d4621c5",
            "cve": "CVE-2020-10735",
            "id": "pyup.io-50916",
            "more_info_path": "/vulnerabilities/CVE-2020-10735/50916",
            "specs": [
                "<1.10.2"
            ],
            "v": "<1.10.2"
        },
        {
            "advisory": "Pydantic 1.8.2, 1.7.4 and 1.6.2 include a fix for CVE-2021-29510: In affected versions of Pydantic passing either `'infinity'`, `'inf'` or `float('inf')` (or their negatives) to `datetime` or `date` fields causes validation to run forever with 100% CPU usage (on one CPU). Pydantic has been patched with fixes available in the following versions: v1.8.2, v1.7.4, v1.6.2. All these versions are available on pypi(https://pypi.org/project/pydantic/#history), and will be available on conda-forge(https://anaconda.org/conda-forge/pydantic) soon. See the changelog(https://pydantic-docs.helpmanual.io/) for details. If you absolutely can't upgrade, you can work around this risk using a validator(https://pydantic-docs.helpmanual.io/usage/validators/) to catch these values. This is not an ideal solution (in particular you'll need a slightly different function for datetimes), instead of a hack like this you should upgrade pydantic. If you are not using v1.8.x, v1.7.x or v1.6.x and are unable to upgrade to a fixed version of pydantic, please create an issue at https://github.com/samuelcolvin/pydantic/issues requesting a back-port, and we will endeavour to release a patch for earlier versions of pydantic.",
            "cve": "CVE-2021-29510",
            "id": "pyup.io-40440",
            "more_info_path": "/vulnerabilities/CVE-2021-29510/40440",
            "specs": [
                ">=1.8.0a1,<1.8.2",
                ">=1.7.0a0,<1.7.4",
                "<1.6.2"
            ],
            "v": ">=1.8.0a1,<1.8.2,>=1.7.0a0,<1.7.4,<1.6.2"
        },
        {
            "advisory": "Regular expression denial of service in Pydanic affected versions allows remote attackers to cause denial of service via a crafted email string.",
            "cve": "CVE-2024-3772",
            "id": "pyup.io-71590",
            "more_info_path": "/vulnerabilities/CVE-2024-3772/71590",
            "specs": [
                ">=2.0.0,<2.4.0",
                "<1.10.13"
            ],
            "v": ">=2.0.0,<2.4.0,<1.10.13"
        }
    ],
    "pydantic-ssm-settings": [
        {
            "advisory": "Pydantic-ssm-settings 0.2.3 updates its dependency 'pywin32' to v301 to include a security fix.",
            "cve": "CVE-2021-32559",
            "id": "pyup.io-49575",
            "more_info_path": "/vulnerabilities/CVE-2021-32559/49575",
            "specs": [
                "<0.2.3"
            ],
            "v": "<0.2.3"
        }
    ],
    "pydash": [
        {
            "advisory": "Pydash 6.0.0 includes a fix for CVE-2023-26145: Code Injection.\r\nhttps://gist.github.com/CalumHutton/45d33e9ea55bf4953b3b31c84703dfca",
            "cve": "CVE-2023-26145",
            "id": "pyup.io-61469",
            "more_info_path": "/vulnerabilities/CVE-2023-26145/61469",
            "specs": [
                "<6.0.0"
            ],
            "v": "<6.0.0"
        }
    ],
    "pydbtools": [
        {
            "advisory": "Pydbtools 5.3.0 updates its dependency 'numpy' to v1.23.1 to include security fixes.",
            "cve": "CVE-2021-41496",
            "id": "pyup.io-50124",
            "more_info_path": "/vulnerabilities/CVE-2021-41496/50124",
            "specs": [
                "<5.3.0"
            ],
            "v": "<5.3.0"
        },
        {
            "advisory": "Pydbtools 5.3.0 updates its dependency 'numpy' to v1.23.1 to include security fixes.",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-50121",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/50121",
            "specs": [
                "<5.3.0"
            ],
            "v": "<5.3.0"
        },
        {
            "advisory": "Pydbtools 5.3.0 updates its dependency 'numpy' to v1.23.1 to include security fixes.",
            "cve": "CVE-2021-41495",
            "id": "pyup.io-50125",
            "more_info_path": "/vulnerabilities/CVE-2021-41495/50125",
            "specs": [
                "<5.3.0"
            ],
            "v": "<5.3.0"
        }
    ],
    "pydest": [
        {
            "advisory": "Pydest 0.6.1 updates its dependency 'aiohttp' to v3.8.1 to include a security fix.",
            "cve": "PVE-2021-42692",
            "id": "pyup.io-49650",
            "more_info_path": "/vulnerabilities/PVE-2021-42692/49650",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        }
    ],
    "pydotz": [
        {
            "advisory": "pydotz 1.2.0 no longer has paths hard-coded due to security and privacy issues",
            "cve": "PVE-2021-37972",
            "id": "pyup.io-37972",
            "more_info_path": "/vulnerabilities/PVE-2021-37972/37972",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "pydov": [
        {
            "advisory": "Pydov 2.2.3 disables XML entity resolution when using lxml's XMLParser to prevent XXE attacks.\r\nhttps://github.com/DOV-Vlaanderen/pydov/pull/377",
            "cve": "PVE-2023-54868",
            "id": "pyup.io-54868",
            "more_info_path": "/vulnerabilities/PVE-2023-54868/54868",
            "specs": [
                "<2.2.3"
            ],
            "v": "<2.2.3"
        }
    ],
    "pydprotect": [
        {
            "advisory": "Pydprotect is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51677",
            "id": "pyup.io-51677",
            "more_info_path": "/vulnerabilities/PVE-2022-51677/51677",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pydrive2": [
        {
            "advisory": "PyDrive2, a Python wrapper for Google Drive API V2, has a vulnerability (CVE-2023-49297) due to unsafe YAML deserialization, which could lead to arbitrary code execution from a malicious YAML file in the same directory or loaded via LoadSettingsFile. The issue was fixed in release version 1.16.2 (commit c57355dc). Users should update to this version or later.\r\nhttps://github.com/iterative/PyDrive2/commit/c57355dc2033ad90b7050d681b2c3ba548ff0004",
            "cve": "CVE-2023-49297",
            "id": "pyup.io-62689",
            "more_info_path": "/vulnerabilities/CVE-2023-49297/62689",
            "specs": [
                "<=1.16.2"
            ],
            "v": "<=1.16.2"
        }
    ],
    "pyenv": [
        {
            "advisory": "Pyenv 1.2.24 throughout 2.3.2 allows local users to gain privileges via a .python-version file in the current working directory. An attacker can craft a Python version string in .python-version to execute shims under their control. Shims are executables that pass a command along to a specific version of pyenv. The version string is used to construct the path to the command, and there is no validation of whether the version specified is a valid version. Thus, relative path traversal can occur.",
            "cve": "CVE-2022-35861",
            "id": "pyup.io-50213",
            "more_info_path": "/vulnerabilities/CVE-2022-35861/50213",
            "specs": [
                ">=1.2.24,<=2.3.2"
            ],
            "v": ">=1.2.24,<=2.3.2"
        }
    ],
    "pyesasky": [
        {
            "advisory": "The pyesasky for python, as distributed on PyPI, included a code-execution backdoor inserted by a third party. The affected versions are 1.2.0-1.4.2.\r\nhttps://github.com/esdc-esac-esa-int/pyesasky/issues/39",
            "cve": "CVE-2022-30885",
            "id": "pyup.io-50152",
            "more_info_path": "/vulnerabilities/CVE-2022-30885/50152",
            "specs": [
                "<1.4.3"
            ],
            "v": "<1.4.3"
        }
    ],
    "pyexasol": [
        {
            "advisory": "Pyexasol 0.23.3 enables SSL certificate verification only when used with 'access_token' or 'refresh_token' connection options, to protect from MITM attacks.",
            "cve": "PVE-2021-42997",
            "id": "pyup.io-42997",
            "more_info_path": "/vulnerabilities/PVE-2021-42997/42997",
            "specs": [
                "<0.23.3"
            ],
            "v": "<0.23.3"
        }
    ],
    "pyfda": [
        {
            "advisory": "Pyfda 0.3.0 fixes an error when trying to load `*.npz` files: `numpy.load()` requires `allow_pickle = True`  since version 1.16.3 for security reasons.",
            "cve": "PVE-2021-38164",
            "id": "pyup.io-38164",
            "more_info_path": "/vulnerabilities/PVE-2021-38164/38164",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "pyfftw": [
        {
            "advisory": "Affected versions of pyfftw are vulnerable to race conditions (CWE-362) due to improper synchronization when accessing shared resources. This can lead to memory corruption or unexpected behavior when used in multithreaded environments. The vulnerability arises from unsynchronized access to FFTW plan destruction and shared cache keys. An attacker could exploit this by inducing concurrent operations, potentially causing application crashes or arbitrary code execution. To mitigate this issue, update to the version where thread identifiers are included in cache keys and plan destruction is properly synchronized using locks.",
            "cve": "PVE-2024-74056",
            "id": "pyup.io-74056",
            "more_info_path": "/vulnerabilities/PVE-2024-74056/74056",
            "specs": [
                "<0.14.0"
            ],
            "v": "<0.14.0"
        }
    ],
    "pyforce": [
        {
            "advisory": "Pyforce 1.8.0 fixes an external entitiy injection (XXE) vulnerability.\r\nhttps://github.com/salesforce-python-client/pyforce/pull/35",
            "cve": "CVE-2013-1665",
            "id": "pyup.io-38058",
            "more_info_path": "/vulnerabilities/CVE-2013-1665/38058",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        },
        {
            "advisory": "Pyforce 1.8.0 fixes an external entitiy injection (XXE) vulnerability.\r\nhttps://github.com/salesforce-python-client/pyforce/pull/35",
            "cve": "CVE-2013-1664",
            "id": "pyup.io-54882",
            "more_info_path": "/vulnerabilities/CVE-2013-1664/54882",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        }
    ],
    "pyfory": [
        {
            "advisory": "Affected versions of the pyfory and legacy pyfury packages are vulnerable to Deserialization of Untrusted Data due to a pickle-based fallback deserialiser that can be selected for untrusted inputs. The deserialisation logic permits a crafted stream to force the pickle fallback and invoke pickle.loads on attacker-controlled bytes, enabling execution of pickle opcodes during object reconstruction.",
            "cve": "CVE-2025-61622",
            "id": "pyup.io-80046",
            "more_info_path": "/vulnerabilities/CVE-2025-61622/80046",
            "specs": [
                ">=0.12.0,<0.12.3"
            ],
            "v": ">=0.12.0,<0.12.3"
        }
    ],
    "pyfribidi": [
        {
            "advisory": "Buffer overflow in the fribidi_utf8_to_unicode function in PyFriBidi before 0.11.0 allows remote attackers to cause a denial of service (application crash) via a 4-byte utf-8 sequence.",
            "cve": "CVE-2012-1176",
            "id": "pyup.io-42235",
            "more_info_path": "/vulnerabilities/CVE-2012-1176/42235",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "pyfrost": [
        {
            "advisory": "Pyfrost 0.2.1 updates its dependency 'bleach' to v3.1.4 to include a security fix.",
            "cve": "CVE-2020-6817",
            "id": "pyup.io-38192",
            "more_info_path": "/vulnerabilities/CVE-2020-6817/38192",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "pyftpdlib": [
        {
            "advisory": "Pyftpdlib before 0.3.0 has a path traversal vulnerability in case of symbolic links escaping user's home directory.",
            "cve": "CVE-2008-7262",
            "id": "pyup.io-26036",
            "more_info_path": "/vulnerabilities/CVE-2008-7262/26036",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        },
        {
            "advisory": "Race condition in the FTPHandler class in ftpserver.py in pyftpdlib before 0.5.1 allows remote attackers to cause a denial of service (daemon outage) by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected return value of None, a different vulnerability than CVE-2010-3494.",
            "cve": "CVE-2009-5010",
            "id": "pyup.io-26037",
            "more_info_path": "/vulnerabilities/CVE-2009-5010/26037",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Race condition in the FTPHandler class in ftpserver.py in pyftpdlib before 0.5.2 allows remote attackers to cause a denial of service (daemon outage) by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected value of None for the address, or an ECONNABORTED, EAGAIN, or EWOULDBLOCK error, a related issue to CVE-2010-3492.",
            "cve": "CVE-2010-3494",
            "id": "pyup.io-26038",
            "more_info_path": "/vulnerabilities/CVE-2010-3494/26038",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        },
        {
            "advisory": "Pyftpdlib 0.6.0 includes a fix for a path traversal vulnerability.\r\nhttps://github.com/giampaolo/pyftpdlib/commit/07cdcdb7f05ee465dcdcbe7f885c30c002dbaf0e",
            "cve": "PVE-2023-61529",
            "id": "pyup.io-61529",
            "more_info_path": "/vulnerabilities/PVE-2023-61529/61529",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Pyftpdlib 1.5.2 improves SSL security by changing and disabling vulnerable defaults.\r\nhttps://github.com/giampaolo/pyftpdlib/commit/a889c8ecca6a2b0fd030985386cc3284eca5e7fb",
            "cve": "PVE-2021-34345",
            "id": "pyup.io-34345",
            "more_info_path": "/vulnerabilities/PVE-2021-34345/34345",
            "specs": [
                "<1.5.2"
            ],
            "v": "<1.5.2"
        },
        {
            "advisory": "pyftpdlib before 0.1.1 does not choose a random value for the port associated with the PASV command, which makes it easier for remote attackers to obtain potentially sensitive information about the number of in-progress data connections by reading the response to this command.",
            "cve": "CVE-2007-6738",
            "id": "pyup.io-53972",
            "more_info_path": "/vulnerabilities/CVE-2007-6738/53972",
            "specs": [
                ">=0,<0.1.1"
            ],
            "v": ">=0,<0.1.1"
        },
        {
            "advisory": "The ftp_PORT function in FTPServer.py in pyftpdlib before 0.2.0 does not prevent TCP connections to privileged ports if the destination IP address matches the source IP address of the connection from the FTP client, which might allow remote authenticated users to conduct FTP bounce attacks via crafted FTP data, as demonstrated by an FTP bounce attack against a NAT server, a related issue to CVE-1999-0017.",
            "cve": "CVE-2007-6741",
            "id": "pyup.io-53975",
            "more_info_path": "/vulnerabilities/CVE-2007-6741/53975",
            "specs": [
                ">=0,<0.2.0"
            ],
            "v": ">=0,<0.2.0"
        },
        {
            "advisory": "FTPServer.py in pyftpdlib before 0.2.0 does not increment the attempted_logins count for a USER command that specifies an invalid username, which makes it easier for remote attackers to obtain access via a brute-force attack.",
            "cve": "CVE-2007-6737",
            "id": "pyup.io-53971",
            "more_info_path": "/vulnerabilities/CVE-2007-6737/53971",
            "specs": [
                ">=0,<0.2.0"
            ],
            "v": ">=0,<0.2.0"
        },
        {
            "advisory": "FTPServer.py in pyftpdlib before 0.2.0 allows remote attackers to cause a denial of service via a long command.",
            "cve": "CVE-2007-6739",
            "id": "pyup.io-53973",
            "more_info_path": "/vulnerabilities/CVE-2007-6739/53973",
            "specs": [
                ">=0,<0.2.0"
            ],
            "v": ">=0,<0.2.0"
        },
        {
            "advisory": "Multiple directory traversal vulnerabilities in FTPServer.py in pyftpdlib before 0.2.0 allow remote authenticated users to access arbitrary files and directories via a .. (dot dot) in a (1) LIST, (2) STOR, or (3) RETR command.",
            "cve": "CVE-2007-6736",
            "id": "pyup.io-53970",
            "more_info_path": "/vulnerabilities/CVE-2007-6736/53970",
            "specs": [
                ">=0,<0.2.0"
            ],
            "v": ">=0,<0.2.0"
        },
        {
            "advisory": "The ftp_STOU function in FTPServer.py in pyftpdlib before 0.2.0 does not limit the number of attempts to discover a unique filename, which might allow remote authenticated users to cause a denial of service via a STOU command.",
            "cve": "CVE-2007-6740",
            "id": "pyup.io-53974",
            "more_info_path": "/vulnerabilities/CVE-2007-6740/53974",
            "specs": [
                ">=0,<0.2.0"
            ],
            "v": ">=0,<0.2.0"
        },
        {
            "advisory": "The ftp_QUIT function in ftpserver.py in pyftpdlib before 0.5.0 allows remote authenticated users to cause a denial of service (file descriptor exhaustion and daemon outage) by sending a QUIT command during a disallowed data-transfer attempt.",
            "cve": "CVE-2008-7264",
            "id": "pyup.io-54040",
            "more_info_path": "/vulnerabilities/CVE-2008-7264/54040",
            "specs": [
                ">=0,<0.5.0"
            ],
            "v": ">=0,<0.5.0"
        },
        {
            "advisory": "ftpserver.py in pyftpdlib before 0.5.0 does not delay its response after receiving an invalid login attempt, which makes it easier for remote attackers to obtain access via a brute-force attack.",
            "cve": "CVE-2008-7263",
            "id": "pyup.io-54039",
            "more_info_path": "/vulnerabilities/CVE-2008-7263/54039",
            "specs": [
                ">=0,<0.5.0"
            ],
            "v": ">=0,<0.5.0"
        },
        {
            "advisory": "Race condition in the FTPHandler class in ftpserver.py in pyftpdlib before 0.5.2 allows remote attackers to cause a denial of service (daemon outage) by establishing and then immediately closing a TCP connection, leading to the getpeername function having an ENOTCONN error, a different vulnerability than CVE-2010-3494.",
            "cve": "CVE-2009-5011",
            "id": "pyup.io-54045",
            "more_info_path": "/vulnerabilities/CVE-2009-5011/54045",
            "specs": [
                ">=0,<0.5.2"
            ],
            "v": ">=0,<0.5.2"
        },
        {
            "advisory": "Memory leak in the on_dtp_close function in ftpserver.py in pyftpdlib before 0.5.2 allows remote authenticated users to cause a denial of service (memory consumption) by sending a QUIT command during a data transfer.",
            "cve": "CVE-2009-5013",
            "id": "pyup.io-54047",
            "more_info_path": "/vulnerabilities/CVE-2009-5013/54047",
            "specs": [
                ">=0,<0.5.2"
            ],
            "v": ">=0,<0.5.2"
        },
        {
            "advisory": "ftpserver.py in pyftpdlib before 0.5.2 does not require the l permission for the MLST command, which allows remote authenticated users to bypass intended access restrictions and list the root directory via an FTP session.",
            "cve": "CVE-2009-5012",
            "id": "pyup.io-54046",
            "more_info_path": "/vulnerabilities/CVE-2009-5012/54046",
            "specs": [
                ">=0,<0.5.2"
            ],
            "v": ">=0,<0.5.2"
        }
    ],
    "pyftpdlib-ustcblog": [
        {
            "advisory": "Pyftpdlib-ustcblog 1.4.1 uses vulnerable defaults (SSLv2, SSLv3 and SSL_COMPRESSION).",
            "cve": "PVE-2017-47392",
            "id": "pyup.io-47392",
            "more_info_path": "/vulnerabilities/PVE-2017-47392/47392",
            "specs": [
                "==1.4.1"
            ],
            "v": "==1.4.1"
        }
    ],
    "pyfulmen": [
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal attacks. The zip extraction process fails to implement path traversal protection (Zip Slip), decompression bomb detection (Zip Bomb), and symlink validation, leading to arbitrary file write outside the intended directory, resource exhaustion through extreme compression ratios, and symlink-based file overwrites.",
            "cve": "PVE-2025-82087",
            "id": "pyup.io-82087",
            "more_info_path": "/vulnerabilities/PVE-2025-82087/82087",
            "specs": [
                "<0.1.11"
            ],
            "v": "<0.1.11"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal attacks. The path validation logic fails to detect directory traversal sequences by checking for `..` after calling `os.path.normpath()`, leading to traversal attempts being hidden by path normalization and allowing attackers to access files outside the intended directory.",
            "cve": "PVE-2025-82090",
            "id": "pyup.io-82090",
            "more_info_path": "/vulnerabilities/PVE-2025-82090/82090",
            "specs": [
                "<0.1.3"
            ],
            "v": "<0.1.3"
        }
    ],
    "pyfury": [
        {
            "advisory": "Affected versions of the pyfory and legacy pyfury packages are vulnerable to Deserialization of Untrusted Data due to a pickle-based fallback deserialiser that can be selected for untrusted inputs. The deserialisation logic permits a crafted stream to force the pickle fallback and invoke pickle.loads on attacker-controlled bytes, enabling execution of pickle opcodes during object reconstruction.",
            "cve": "CVE-2025-61622",
            "id": "pyup.io-80045",
            "more_info_path": "/vulnerabilities/CVE-2025-61622/80045",
            "specs": [
                ">=0.1.0,<=0.10.3"
            ],
            "v": ">=0.1.0,<=0.10.3"
        }
    ],
    "pyg90alarm": [
        {
            "advisory": "Pyg90alarm 1.11.0 updates its requests dependency from version 2.31.0 to 2.32.0 to address CVE-2024-35195.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-71732",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/71732",
            "specs": [
                "<1.11.0"
            ],
            "v": "<1.11.0"
        },
        {
            "advisory": "Pyg90alarm 1.6.1 updates its dependency 'pygments' to v2.7.4 to include a security fix.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-51570",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/51570",
            "specs": [
                "<1.6.1"
            ],
            "v": "<1.6.1"
        },
        {
            "advisory": "Pyg90alarm 1.6.1 updates its dependency 'sphinx' to v3.0.4 to include a security fix.",
            "cve": "CVE-2020-11023",
            "id": "pyup.io-51569",
            "more_info_path": "/vulnerabilities/CVE-2020-11023/51569",
            "specs": [
                "<1.6.1"
            ],
            "v": "<1.6.1"
        },
        {
            "advisory": "Pyg90alarm 1.6.1 updates its dependency 'pygments' to v2.7.4 to include a security fix.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-51571",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/51571",
            "specs": [
                "<1.6.1"
            ],
            "v": "<1.6.1"
        },
        {
            "advisory": "Pyg90alarm 1.6.1 updates its dependency 'sphinx' to v3.0.4 to include a security fix.",
            "cve": "CVE-2020-11022",
            "id": "pyup.io-51546",
            "more_info_path": "/vulnerabilities/CVE-2020-11022/51546",
            "specs": [
                "<1.6.1"
            ],
            "v": "<1.6.1"
        }
    ],
    "pygaem": [
        {
            "advisory": "Pygaem is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51750",
            "id": "pyup.io-51750",
            "more_info_path": "/vulnerabilities/PVE-2022-51750/51750",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pygame": [
        {
            "advisory": "Pygame 2.5.2 updates its C dependency 'libwebp' to v1.3.2 to include a fix for a high-risk vulnerability.\r\nhttps://github.com/pygame/pygame/commit/94d6c94eae1df106909ca61c18224849cd1f042e",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61494",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61494",
            "specs": [
                "<2.5.2"
            ],
            "v": "<2.5.2"
        },
        {
            "advisory": "Affected versions of pygame are vulnerable to a file squatting vulnerability (CWE-377). This vulnerability could allow an attacker to manipulate temporary files, potentially leading to unauthorized data access or corruption. The vulnerability arises from the use of tempfile.mktemp(), which creates a race condition. The patch mitigates this issue by using tempfile.NamedTemporaryFile(delete=False), which securely creates temporary files. Users should ensure that temporary files are not reopened by name in an unsafe manner to avoid potential exploitation. This advisory is relevant for Python versions prior to the introduction of safer temporary file handling practices.",
            "cve": "PVE-2024-73475",
            "id": "pyup.io-73475",
            "more_info_path": "/vulnerabilities/PVE-2024-73475/73475",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        }
    ],
    "pygame-ce": [
        {
            "advisory": "Pygame-ce 2.4.0.dev2 updates its C dependency 'libwebp' to v1.3.2 to include a fix for a high risk vulnerability.\r\nhttps://github.com/pygame-community/pygame-ce/commit/eb87abe40348b8d114d8e7040bcd6fb25d8bd66e",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61918",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61918",
            "specs": [
                "<2.4.0.dev2"
            ],
            "v": "<2.4.0.dev2"
        }
    ],
    "pygenesis-django": [
        {
            "advisory": "Pygenesis-django 0.1.1alpha updates its dependency 'django' to v5.1 to include a fix for a SQLi vulnerability.",
            "cve": "CVE-2024-42005",
            "id": "pyup.io-72579",
            "more_info_path": "/vulnerabilities/CVE-2024-42005/72579",
            "specs": [
                "<0.1.1alpha"
            ],
            "v": "<0.1.1alpha"
        }
    ],
    "pyglove": [
        {
            "advisory": "Pyglove 0.1.1 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/google/pyglove/pull/52",
            "cve": "PVE-2023-59575",
            "id": "pyup.io-59575",
            "more_info_path": "/vulnerabilities/PVE-2023-59575/59575",
            "specs": [
                "<0.1.1"
            ],
            "v": "<0.1.1"
        }
    ],
    "pygments": [
        {
            "advisory": "Pygments 2.15.0 includes a fix for CVE-2022-40896: The regular expressions used when parsing Smithy, SQL/SQL+Jinja, and Java properties files were discovered to be vulnerable. As a result, pygmentizing a maliciously-crafted file of these kinds would have resulted in high resources consumption or crashing of the application.\r\nhttps://pyup.io/posts/pyup-discovers-redos-vulnerabilities-in-top-python-packages-part-2",
            "cve": "CVE-2022-40896",
            "id": "pyup.io-58910",
            "more_info_path": "/vulnerabilities/CVE-2022-40896/58910",
            "specs": [
                "<2.15.0"
            ],
            "v": "<2.15.0"
        },
        {
            "advisory": "Pygments 2.7.4 includes a fix for CVE-2021-27291: In pygments 1.1+, fixed in 2.7.4, the lexers used to parse programming languages rely heavily on regular expressions. Some of the regular expressions have exponential or cubic worst-case complexity and are vulnerable to ReDoS. By crafting malicious input, an attacker can cause a denial of service.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-50886",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/50886",
            "specs": [
                ">=1.1,<2.7.4"
            ],
            "v": ">=1.1,<2.7.4"
        },
        {
            "advisory": "Pygments 2.1 includes a fix for CVE-2015-8557: The FontManager._get_nix_font_path function in formatters/img.py in pygments 1.2.2 through 2.0.2 allows remote attackers to execute arbitrary commands via shell metacharacters in a font name.",
            "cve": "CVE-2015-8557",
            "id": "pyup.io-50887",
            "more_info_path": "/vulnerabilities/CVE-2015-8557/50887",
            "specs": [
                ">=1.2.2,<2.1"
            ],
            "v": ">=1.2.2,<2.1"
        },
        {
            "advisory": "Pygments 2.7.4 includes a fix for CVE-2021-20270: An infinite loop in SMLLexer in Pygments versions 1.5 to 2.7.3 may lead to denial of service when performing syntax highlighting of a Standard ML (SML) source file, as demonstrated by input that only contains the \"exception\" keyword.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-50885",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/50885",
            "specs": [
                ">=1.5,<2.7.4"
            ],
            "v": ">=1.5,<2.7.4"
        }
    ],
    "pygments-promql": [
        {
            "advisory": "Pygments-promql 0.0.8 updates its dependency 'pillow' to v9.0.0 to include a security fix.",
            "cve": "CVE-2022-22817",
            "id": "pyup.io-62172",
            "more_info_path": "/vulnerabilities/CVE-2022-22817/62172",
            "specs": [
                "<0.0.8"
            ],
            "v": "<0.0.8"
        },
        {
            "advisory": "Pygments-promql 0.1.0 updates its dependency 'pillow' to v10.0.1 to include a security fix.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62171",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62171",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        }
    ],
    "pygqlc": [
        {
            "advisory": "Pygqlc 3.0.1 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/valiot/pygqlc/commit/2766910edf3a82624b7bccf3777f95d69285cfb7\r\nhttps://github.com/valiot/pygqlc/commit/e4a7ea0bb94388196fd627af692424150ad25c86",
            "cve": "PVE-2023-59551",
            "id": "pyup.io-59551",
            "more_info_path": "/vulnerabilities/PVE-2023-59551/59551",
            "specs": [
                "<3.0.1"
            ],
            "v": "<3.0.1"
        },
        {
            "advisory": "Pygqlc 3.1.4 updates its dependency 'certifi' to version '2023.7.22' to include a fix for an Improper Following of a Certificate's Chain of Trust vulnerability.\r\nhttps://github.com/valiot/pygqlc/commit/091793fed86194b10cd908c22f837f4f3cf7f7eb",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60488",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60488",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        }
    ],
    "pygresql": [
        {
            "advisory": "The pygresql module 3.8.1 and 4.0 for Python does not properly support the PQescapeStringConn function, which might allow remote attackers to leverage escaping issues involving multibyte character encodings.",
            "cve": "CVE-2009-2940",
            "id": "pyup.io-26039",
            "more_info_path": "/vulnerabilities/CVE-2009-2940/26039",
            "specs": [
                "<4.0"
            ],
            "v": "<4.0"
        }
    ],
    "pyhanko": [
        {
            "advisory": "Pyhanko 0.3.0 no longer uses the homegrown 'RC4' class, which is not secure.\r\nhttps://github.com/MatthiasValvekens/pyHanko/commit/cd7cd319105a7e2438d9d2d0b109b2fb88b7bbe4",
            "cve": "PVE-2021-40478",
            "id": "pyup.io-40478",
            "more_info_path": "/vulnerabilities/PVE-2021-40478/40478",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "pyhf": [
        {
            "advisory": "Pyhf 0.6.2 starts to use PyYAML's 'safe_load' for better security.",
            "cve": "PVE-2021-40822",
            "id": "pyup.io-40822",
            "more_info_path": "/vulnerabilities/PVE-2021-40822/40822",
            "specs": [
                "<0.6.2"
            ],
            "v": "<0.6.2"
        }
    ],
    "pyhints": [
        {
            "advisory": "Pyhints is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51699",
            "id": "pyup.io-51699",
            "more_info_path": "/vulnerabilities/PVE-2022-51699/51699",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pyhtml2pdf": [
        {
            "advisory": "Pyhtml2pdf version 0.0.6 allows an external attacker to remotely obtain arbitrary local files. This is possible because the application does not validate the HTML content entered by the user.",
            "cve": "CVE-2024-1647",
            "id": "pyup.io-66689",
            "more_info_path": "/vulnerabilities/CVE-2024-1647/66689",
            "specs": [
                "<=0.0.6"
            ],
            "v": "<=0.0.6"
        }
    ],
    "pyinaturalist": [
        {
            "advisory": "Pyinaturalist 0.7.0 updates its dependency 'jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-37127",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/37127",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Pyinaturalist 0.7.0 updates its dependency 'urllib3' to v1.24.2 to include a security fix.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-49091",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/49091",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        }
    ],
    "pyinstaller": [
        {
            "advisory": "Pyinstaller 3.5 updates the bundled zlib library to version 1.2.11 to address vulnerabilities.",
            "cve": "CVE-2016-9842",
            "id": "pyup.io-45788",
            "more_info_path": "/vulnerabilities/CVE-2016-9842/45788",
            "specs": [
                "<3.5"
            ],
            "v": "<3.5"
        },
        {
            "advisory": "Pyinstaller 3.5 updates the bundled zlib library to version 1.2.11 to address vulnerabilities.",
            "cve": "CVE-2016-9843",
            "id": "pyup.io-45789",
            "more_info_path": "/vulnerabilities/CVE-2016-9843/45789",
            "specs": [
                "<3.5"
            ],
            "v": "<3.5"
        },
        {
            "advisory": "Pyinstaller 3.5 updates the bundled zlib library to version 1.2.11 to address vulnerabilities.",
            "cve": "CVE-2016-9841",
            "id": "pyup.io-45787",
            "more_info_path": "/vulnerabilities/CVE-2016-9841/45787",
            "specs": [
                "<3.5"
            ],
            "v": "<3.5"
        },
        {
            "advisory": "Pyinstaller 3.5 updates the bundled zlib library to version 1.2.11 to address vulnerabilities.",
            "cve": "CVE-2016-9840",
            "id": "pyup.io-39153",
            "more_info_path": "/vulnerabilities/CVE-2016-9840/39153",
            "specs": [
                "<3.5"
            ],
            "v": "<3.5"
        },
        {
            "advisory": "Pyinstaller 3.6 includes a fix for CVE-2019-16784: Local Privilege Escalation caused by insecure directory permissions of sys._MEIPATH. This security bug affects all Windows software frozen by PyInstaller in \"onefile\" mode. While PyInstaller itself was not vulnerable, all Windows software frozen by PyInstaller in \"onefile\" mode is vulnerable.",
            "cve": "CVE-2019-16784",
            "id": "pyup.io-37676",
            "more_info_path": "/vulnerabilities/CVE-2019-16784/37676",
            "specs": [
                "<3.6"
            ],
            "v": "<3.6"
        },
        {
            "advisory": "PyInstaller bundles a Python application and all its dependencies into a single package. A PyInstaller built application, elevated as a privileged process, may be tricked by an unprivileged attacker into deleting files the unprivileged user does not otherwise have access to. A user is affected if **all** the following are satisfied: 1. The user runs an application containing either `matplotlib` or `win32com`. 2. The application is ran as administrator (or at least a user with higher privileges than the attacker). 3. The user's temporary directory is not locked to that specific user (most likely due to `TMP`/`TEMP` environment variables pointing to an unprotected, arbitrary, non default location). Either: A. The attacker is able to very carefully time the replacement of a temporary file with a symlink. This switch must occur exactly between `shutil.rmtree()`'s builtin symlink check and the deletion itself B: The application was built with Python 3.7.x or earlier which has no protection against Directory Junctions links. The vulnerability has been addressed in PR #7827 which corresponds to `pyinstaller >= 5.13.1`. Users are advised to upgrade. There are no known workarounds for this vulnerability.",
            "cve": "CVE-2023-49797",
            "id": "pyup.io-65347",
            "more_info_path": "/vulnerabilities/CVE-2023-49797/65347",
            "specs": [
                "<5.13.1"
            ],
            "v": "<5.13.1"
        },
        {
            "advisory": "PyInstaller 5.8.0 addresses a race condition in environment modification done by the multiprocessing runtime hook when multiple threads are used concurrently. This issue particularly affects the \"spawn\" method of multiprocessing, which is not thread-safe on Linux.\r\n# This only affects Linux users",
            "cve": "PVE-2024-72042",
            "id": "pyup.io-72042",
            "more_info_path": "/vulnerabilities/PVE-2024-72042/72042",
            "specs": [
                "<5.8.0"
            ],
            "v": "<5.8.0"
        },
        {
            "advisory": "Affected versions of the PyInstaller package are vulnerable to Code Injection due to unsafe module search-path manipulation during the bootstrap of frozen applications. The PyInstaller loader\u2019s bootstrap script (`pyiboot01_bootstrap.py`) appends a transient entry to `sys.path` and, while that untrusted element remains present, attempts to import the optional bytecode-decryption module `pyimod00_crypto_key`, enabling resolution from an attacker-controlled neighbouring directory or ZIP whose name matches the bootloader\u2019s PYZ location marker in builds without the `--key` feature.",
            "cve": "CVE-2025-59042",
            "id": "pyup.io-79491",
            "more_info_path": "/vulnerabilities/CVE-2025-59042/79491",
            "specs": [
                "<6.0.0"
            ],
            "v": "<6.0.0"
        }
    ],
    "pyiron-base": [
        {
            "advisory": "Pyiron-base 0.5.2 includes a fix for a Race Condition vulnerability. \r\nhttps://github.com/pyiron/pyiron_base/commit/cd7bb0bd62919530ed971aa0bff832fdc0e9751a",
            "cve": "PVE-2023-59574",
            "id": "pyup.io-59574",
            "more_info_path": "/vulnerabilities/PVE-2023-59574/59574",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        }
    ],
    "pyjellyfish": [
        {
            "advisory": "Pyjellyfish 1.1.0 addresses a path traversal vulnerability in the tarfile module's extract and extractall functions. This flaw could let remote attackers with user assistance overwrite arbitrary files using a directory traversal sequence in TAR archive filenames. This issue is akin to CVE-2001-1267 but specifically patched in this version to enhance security.\r\nhttps://github.com/iric-soft/pyJellyfish/pull/1",
            "cve": "CVE-2007-4559",
            "id": "pyup.io-60118",
            "more_info_path": "/vulnerabilities/CVE-2007-4559/60118",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pyjwt": [
        {
            "advisory": "Pyjwt 1.0.0 includes a security fix: 'alg=None' header could bypass signature verification.\r\nhttps://github.com/jpadilla/pyjwt/pull/109",
            "cve": "PVE-2021-39458",
            "id": "pyup.io-39458",
            "more_info_path": "/vulnerabilities/PVE-2021-39458/39458",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch.",
            "cve": "CVE-2017-11424",
            "id": "pyup.io-35014",
            "more_info_path": "/vulnerabilities/CVE-2017-11424/35014",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        },
        {
            "advisory": "Affected versions of pyjwt are vulnerable to Partial Comparison (CWE-187). This flaw allows attackers to bypass issuer (iss) verification by providing partial matches, potentially granting unauthorized access. The vulnerability arises in the decode method of api_jwt.py, where issuer validation incorrectly treats strings as sequences, leading to partial matches (e.g., \"abc\" being accepted for \"__abc__\"). Exploiting this requires crafting JWTs with partially matching iss claims, which is straightforward.",
            "cve": "CVE-2024-53861",
            "id": "pyup.io-74429",
            "more_info_path": "/vulnerabilities/CVE-2024-53861/74429",
            "specs": [
                "==2.10.0"
            ],
            "v": "==2.10.0"
        },
        {
            "advisory": "PyJWT 2.4.0 includes a fix for CVE-2022-29217: An attacker submitting the JWT token can choose the used signing algorithm. The PyJWT library requires that the application chooses what algorithms are supported. The application can specify 'jwt.algorithms.get_default_algorithms()' to get support for all algorithms, or specify a single algorithm. The issue is not that big as 'algorithms=jwt.algorithms.get_default_algorithms()' has to be used. As a workaround, always be explicit with the algorithms that are accepted and expected when decoding.",
            "cve": "CVE-2022-29217",
            "id": "pyup.io-48542",
            "more_info_path": "/vulnerabilities/CVE-2022-29217/48542",
            "specs": [
                ">=1.5.0,<2.4.0"
            ],
            "v": ">=1.5.0,<2.4.0"
        }
    ],
    "pykarotz": [
        {
            "advisory": "Pykarotz is used together with Electronic Arts Karotz Smart Rabbit, which allows Python module hijacking. See: .",
            "cve": "CVE-2013-4867",
            "id": "pyup.io-37751",
            "more_info_path": "/vulnerabilities/CVE-2013-4867/37751",
            "specs": [
                "==0.2"
            ],
            "v": "==0.2"
        }
    ],
    "pykechain": [
        {
            "advisory": "Pykechain 2.5.4 updates security advisory to install requests package later than 2.20.0 (CVE-2018-18074).",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36937",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36937",
            "specs": [
                "<2.5.4"
            ],
            "v": "<2.5.4"
        }
    ],
    "pykmip": [
        {
            "advisory": "OpenKMIP PyKMIP version All versions before 0.8.0 contains a CWE 399: Resource Management Errors (similar issue to CVE-2015-5262) vulnerability in PyKMIP server that can result in DOS: the server can be made unavailable by one or more clients opening all of the available sockets. This attack appear to be exploitable via A client or clients open sockets with the server and then never close them. This vulnerability appears to have been fixed in 0.8.0.",
            "cve": "CVE-2018-1000872",
            "id": "pyup.io-42250",
            "more_info_path": "/vulnerabilities/CVE-2018-1000872/42250",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        }
    ],
    "pylabnet": [
        {
            "advisory": "Servers in pylabnet before version 0.3.0 were not secure by default.",
            "cve": "PVE-2021-38667",
            "id": "pyup.io-38667",
            "more_info_path": "/vulnerabilities/PVE-2021-38667/38667",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "pyldap": [
        {
            "advisory": "Pyldap before 2.0.0pre05 is using an insecure transitive dependency which is not in PyPI (ldapurl). No further information was found on this old vulnerability.",
            "cve": "PVE-2021-26041",
            "id": "pyup.io-26041",
            "more_info_path": "/vulnerabilities/PVE-2021-26041/26041",
            "specs": [
                "<2.0.0pre05"
            ],
            "v": "<2.0.0pre05"
        }
    ],
    "pylint": [
        {
            "advisory": "Pylint 2.13.0 fixes a crash when using the doc_params extension.\r\nhttps://github.com/PyCQA/pylint/issues/5322",
            "cve": "PVE-2022-45185",
            "id": "pyup.io-45185",
            "more_info_path": "/vulnerabilities/PVE-2022-45185/45185",
            "specs": [
                "<2.13.0"
            ],
            "v": "<2.13.0"
        },
        {
            "advisory": "Pylint 2.5.0 no longer allows ``python -m pylint ...`` to import user code. Previously, it added the current working directory as the first element of ``sys.path``. This opened up a potential security hole where ``pylint`` would import user level code as long as that code resided in modules having the same name as stdlib or pylint's own modules.",
            "cve": "PVE-2021-38224",
            "id": "pyup.io-38224",
            "more_info_path": "/vulnerabilities/PVE-2021-38224/38224",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Pylint 2.7.0 includes a fix for vulnerable regular expressions in 'pyreverse'.\r\nhttps://github.com/pylint-dev/pylint/commit/5405dd5115d598fa69e49538d50ec79202b1b52e",
            "cve": "PVE-2021-39621",
            "id": "pyup.io-39621",
            "more_info_path": "/vulnerabilities/PVE-2021-39621/39621",
            "specs": [
                "<2.7.0"
            ],
            "v": "<2.7.0"
        },
        {
            "advisory": "Pylint before 2.6.1 is susceptible to a Regular Expression Denial of Service (ReDoS) vulnerability due to issues in its pyreverse component. This issue arises from certain regular expressions in pyreverse that can be exploited by causing catastrophic backtracking, significantly slowing down the service by forcing it to take a disproportionate amount of time to process inputs. This vulnerability allows attackers to use specially crafted inputs that increase the processing time exponentially, potentially leading to a service becoming inaccessible to legitimate users.\r\nhttps://github.com/pylint-dev/pylint/commit/5405dd5115d598fa69e49538d50ec79202b1b52e",
            "cve": "PVE-2024-99772",
            "id": "pyup.io-66067",
            "more_info_path": "/vulnerabilities/PVE-2024-99772/66067",
            "specs": [
                ">=0,<2.6.1"
            ],
            "v": ">=0,<2.6.1"
        }
    ],
    "pylivetrader": [
        {
            "advisory": "Pylivetrader 0.2.0 changes the yaml config loading to use the safe loading. This is a security fix.",
            "cve": "PVE-2021-38294",
            "id": "pyup.io-38294",
            "more_info_path": "/vulnerabilities/PVE-2021-38294/38294",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "pyload": [
        {
            "advisory": "Affected versions of pyload are vulnerable to Open Redirection (CWE-601). This vulnerability allows attackers to redirect users to malicious sites by exploiting the improper handling of the next parameter in the login functionality. The attack vector involves crafting URLs with malicious next parameters, leading users to phishing or harmful websites. Vulnerable functions include login in app_blueprint.py and get_redirect_url in helpers.py. To mitigate, upgrade to pyload version which implements proper validation and handling of redirect URLs, preventing unauthorized redirections.",
            "cve": "CVE-2024-24808",
            "id": "pyup.io-74258",
            "more_info_path": "/vulnerabilities/CVE-2024-24808/74258",
            "specs": [
                "<0.5.0b3"
            ],
            "v": "<0.5.0b3"
        },
        {
            "advisory": "pyload is an open-source Download Manager written in pure Python. An authenticated user can change the download folder and upload a crafted template to the specified folder lead to remote code execution. There is no fix available at the time of publication. See CVE-2024-32880.",
            "cve": "CVE-2024-32880",
            "id": "pyup.io-70714",
            "more_info_path": "/vulnerabilities/CVE-2024-32880/70714",
            "specs": [
                "<=5.0"
            ],
            "v": "<=5.0"
        }
    ],
    "pyload-ng": [
        {
            "advisory": "An unsafe JavaScript evaluation vulnerability in pyLoad\u2019s CAPTCHA processing code allows unauthenticated remote attackers to execute arbitrary code in the client browser and potentially the backend server. Exploitation requires no user interaction or authentication and can result in session hijacking, credential theft, and full system rce.",
            "cve": "CVE-2025-53890",
            "id": "pyup.io-78158",
            "more_info_path": "/vulnerabilities/CVE-2025-53890/78158",
            "specs": [
                "<0.20"
            ],
            "v": "<0.20"
        },
        {
            "advisory": "Pyload-ng 0.5.0b3.dev31 includes a fix for CVE-2023-0297: Code Injection in GitHub repository pyload/pyload prior to 0.5.0b3.dev31.",
            "cve": "CVE-2023-0297",
            "id": "pyup.io-53432",
            "more_info_path": "/vulnerabilities/CVE-2023-0297/53432",
            "specs": [
                "<0.5.0b3.dev31"
            ],
            "v": "<0.5.0b3.dev31"
        },
        {
            "advisory": "Pyload-ng versions before 0.5.0b3.dev77 are vulnerable to Unauthenticated Flask Configuration Leakage. Any unauthenticated user can browse to a specific URL to expose the Flask config, including the 'SECRET_KEY' variable.",
            "cve": "CVE-2024-21644",
            "id": "pyup.io-63601",
            "more_info_path": "/vulnerabilities/CVE-2024-21644/63601",
            "specs": [
                "<0.5.0b3.dev77"
            ],
            "v": "<0.5.0b3.dev77"
        },
        {
            "advisory": "Pyload-ng versions before 0.5.0b3.dev77 are vulnerable to Log Injection, allowing any unauthenticated actor to inject arbitrary messages into the logs gathered by 'pyload'. Forged or otherwise, corrupted log files can be used to cover an attacker\u2019s tracks or even to implicate another party in the commission of a malicious act.",
            "cve": "CVE-2024-21645",
            "id": "pyup.io-63602",
            "more_info_path": "/vulnerabilities/CVE-2024-21645/63602",
            "specs": [
                "<0.5.0b3.dev77"
            ],
            "v": "<0.5.0b3.dev77"
        },
        {
            "advisory": "The pyload API, which supports making API calls through GET requests, was vulnerable to significant security risks due to the session cookie not being set to SameSite: strict. This vulnerability exposed the library to potential Cross-Site Request Forgery (CSRF) attacks, enabling unauthenticated users to make any API call through such an attack. This security concern has been resolved in the release 0.5.0b3.dev78.\r\nhttps://github.com/pyload/pyload/security/advisories/GHSA-pgpj-v85q-h5fm",
            "cve": "CVE-2024-22416",
            "id": "pyup.io-64457",
            "more_info_path": "/vulnerabilities/CVE-2024-22416/64457",
            "specs": [
                "<0.5.0b3.dev77"
            ],
            "v": "<0.5.0b3.dev77"
        },
        {
            "advisory": "An authenticated user can change the download folder and upload a crafted template to the specified folder, leading to remote code execution.\r\n### References\r\nhttps://github.com/pyload/pyload/commit/249c41bd427fde87715e24a5fa3e7d5d63ae3312",
            "cve": "CVE-2024-32880",
            "id": "pyup.io-71929",
            "more_info_path": "/vulnerabilities/CVE-2024-32880/71929",
            "specs": [
                "<0.5.0b3.dev85"
            ],
            "v": "<0.5.0b3.dev85"
        },
        {
            "advisory": "Affected versions of pyLoad are vulnerable to path traversal via the storage_folder configuration setting. This vulnerability allows attackers to write files to arbitrary locations by manipulating the storage_folder path, potentially leading to arbitrary file writes and code execution. The vulnerability exists in the Core.init and Api.set_config_value functions where storage paths aren't properly validated. Attackers with access to configuration settings can exploit this through the web interface. Users should update to the version which implements proper path validation and restriction checks.",
            "cve": "CVE-2024-47821",
            "id": "pyup.io-73964",
            "more_info_path": "/vulnerabilities/CVE-2024-47821/73964",
            "specs": [
                "<0.5.0b3.dev87"
            ],
            "v": "<0.5.0b3.dev87"
        },
        {
            "advisory": "Affected versions of the pyLoad-ng package are vulnerable to Path Traversal due to insufficient sanitization of the package parameter in the CNL blueprint. The /addcrypted endpoint in src/pyload/webui/app/blueprints/cnl_blueprint.py constructs file paths using user-supplied input without properly validating directory traversal sequences, only removing forward slashes, backslashes, and colons while leaving path traversal patterns intact. An unauthenticated attacker can exploit this vulnerability by sending a specially crafted POST request with a malicious package parameter containing directory traversal sequences to write arbitrary files to the system, including cron jobs or systemd services, achieving remote code execution as root.",
            "cve": "CVE-2025-54802",
            "id": "pyup.io-78689",
            "more_info_path": "/vulnerabilities/CVE-2025-54802/78689",
            "specs": [
                "<0.5.0b3.dev90"
            ],
            "v": "<0.5.0b3.dev90"
        },
        {
            "advisory": "Affected versions of the pyload-ng package are vulnerable to Code Injection due to unsanitized parameters in the Captcha script handler and the Click'N'Load (CNL) blueprint of the web interface. The CNL /flash/addcrypted2 endpoint and related handlers accept user-controlled fields such as the jk and package parameters and propagate them into the UI without proper validation or encoding, enabling attacker-supplied JavaScript to be injected and executed in the client browser.",
            "cve": "CVE-2025-61773",
            "id": "pyup.io-80314",
            "more_info_path": "/vulnerabilities/CVE-2025-61773/80314",
            "specs": [
                "<0.5.0b3.dev91"
            ],
            "v": "<0.5.0b3.dev91"
        },
        {
            "advisory": "Affected versions of the pyload-ng package are vulnerable to SQL Injection due to unsanitized concatenation of user-controlled input into a database query. The /json/add_package API path propagates the add_links parameter to src/pyload/core/database/file_database.py:update_link_info, which constructs a comma-separated list of URLs and interpolates it directly into SELECT id FROM links WHERE url IN ('{statuses}') rather than using parameterised placeholders, allowing crafted values to alter the SQL syntax. An authenticated attacker can send a POST request to /json/add_package with a malicious add_links value that terminates the string literal and injects arbitrary SQL, enabling modification or deletion of database records and causing data loss and service disruption in pyload-ng.",
            "cve": "CVE-2025-55156",
            "id": "pyup.io-78703",
            "more_info_path": "/vulnerabilities/CVE-2025-55156/78703",
            "specs": [
                "<0.5.0b3.dev91"
            ],
            "v": "<0.5.0b3.dev91"
        },
        {
            "advisory": "Affected versions of the pyLoad package are vulnerable to Denial of Service (DoS) attacks due to insufficient validation of JavaScript code in the Click'n'Load (CNL) Blueprint handler. The `/flash/addcrypted2` endpoint accepts a `jk` parameter containing JavaScript code that is directly passed to the `eval_js()` function, which executes it through either `dukpy.evaljs()` or `js2py.eval_js()` without any timeout or resource limitations.",
            "cve": "CVE-2025-57751",
            "id": "pyup.io-79030",
            "more_info_path": "/vulnerabilities/CVE-2025-57751/79030",
            "specs": [
                "<0.5.0b3.dev92"
            ],
            "v": "<0.5.0b3.dev92"
        },
        {
            "advisory": "pyLoad is an open-source Download Manager written in pure Python. There is an open redirect vulnerability due to incorrect validation of input values when redirecting users after login. pyLoad is validating URLs via the `get_redirect_url` function when redirecting users at login. This vulnerability has been patched with commit fe94451. See CVE-2024-24808.",
            "cve": "CVE-2024-24808",
            "id": "pyup.io-65294",
            "more_info_path": "/vulnerabilities/CVE-2024-24808/65294",
            "specs": [
                "<=0.5.0"
            ],
            "v": "<=0.5.0"
        },
        {
            "advisory": "pyLoad 0.5.0 is vulnerable to Unrestricted File Upload.",
            "cve": "CVE-2023-47890",
            "id": "pyup.io-65258",
            "more_info_path": "/vulnerabilities/CVE-2023-47890/65258",
            "specs": [
                "<=0.5.0"
            ],
            "v": "<=0.5.0"
        },
        {
            "advisory": "Affected versions of the pyload-ng package are vulnerable to Code Injection due to improper control of code generation via a JS2PY sandbox escape in the handling of input passed to the `/flash/addcrypted2` API endpoint. The `/flash/addcrypted2` endpoint uses js2py\u2014which suffers from a sandbox escape via CVE-2024-28397\u2014and the endpoint\u2019s localhost restriction can be bypassed using crafted HTTP headers, allowing execution of arbitrary shell commands within the code evaluation context. An attacker can send a request containing a shell command to the `/flash/addcrypted2` endpoint (even remotely by spoofing headers), resulting in remote code execution on the server, with high confidentiality, integrity, and availability impact.",
            "cve": "CVE-2024-39205",
            "id": "pyup.io-78773",
            "more_info_path": "/vulnerabilities/CVE-2024-39205/78773",
            "specs": [
                "<=0.5.0b3.dev85"
            ],
            "v": "<=0.5.0b3.dev85"
        },
        {
            "advisory": "Any unauthenticated attacker can bypass the localhost restrictions posed by the application and utilize this to create arbitrary packages.",
            "cve": "CVE-2025-7346",
            "id": "pyup.io-77997",
            "more_info_path": "/vulnerabilities/CVE-2025-7346/77997",
            "specs": [
                "<=0.5.0b3.dev88"
            ],
            "v": "<=0.5.0b3.dev88"
        },
        {
            "advisory": "Affected versions of the pyload package are vulnerable to Log Injection. The `/json/add_package` API endpoint fails to properly escape newline characters in package names, leading to arbitrary log entry injection. A user with add packages permission can exploit this vulnerability by crafting a package name containing newline characters and malicious log entries, resulting in corrupted log files that can be used to cover an attacker's tracks or implicate other parties in malicious acts.",
            "cve": "PVE-2025-78597",
            "id": "pyup.io-78597",
            "more_info_path": "/vulnerabilities/PVE-2025-78597/78597",
            "specs": [
                "<=0.5.0b3.dev89"
            ],
            "v": "<=0.5.0b3.dev89"
        },
        {
            "advisory": "pyLoad is a free and open-source Download Manager written in pure Python. In version 0.5.0b3.dev89, an authenticated path traversal vulnerability exists in the /json/upload endpoint of pyLoad. By manipulating the filename of an uploaded file, an attacker can traverse out of the intended upload directory, allowing them to write arbitrary files to any location on the system accessible to the pyLoad process. This may lead to: Remote Code Execution (RCE), local privilege escalation, system-wide compromise, persistence, and backdoors. This is fixed in version 0.5.0b3.dev90.",
            "cve": "CVE-2025-54140",
            "id": "pyup.io-78330",
            "more_info_path": "/vulnerabilities/CVE-2025-54140/78330",
            "specs": [
                "==0.5.0b3.dev89"
            ],
            "v": "==0.5.0b3.dev89"
        },
        {
            "advisory": "Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository pyload/pyload prior to 0.5.0b3.dev32. The Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the user agent to send those cookies in plaintext over an HTTP session. This issue is patched in version 0.5.0b3.dev32.",
            "cve": "CVE-2023-0055",
            "id": "pyup.io-54642",
            "more_info_path": "/vulnerabilities/CVE-2023-0055/54642",
            "specs": [
                ">=0,<0.5.0b3.dev32"
            ],
            "v": ">=0,<0.5.0b3.dev32"
        },
        {
            "advisory": "Improper Restriction of Rendered UI Layers or Frames in GitHub repository pyload/pyload prior to 0.5.0b3.dev33.",
            "cve": "CVE-2023-0057",
            "id": "pyup.io-54643",
            "more_info_path": "/vulnerabilities/CVE-2023-0057/54643",
            "specs": [
                ">=0,<0.5.0b3.dev33"
            ],
            "v": ">=0,<0.5.0b3.dev33"
        },
        {
            "advisory": "Pyload 0.5.0b3.dev35 has an Insufficient Session Expiration vulnerability. A patch is available and anticipated to be part of version 0.5.0b3.dev36.",
            "cve": "CVE-2023-0227",
            "id": "pyup.io-54610",
            "more_info_path": "/vulnerabilities/CVE-2023-0227/54610",
            "specs": [
                ">=0,<0.5.0b3.dev36"
            ],
            "v": ">=0,<0.5.0b3.dev36"
        },
        {
            "advisory": "Improper Input Validation in GitHub repository pyload/pyload prior to 0.5.0b3.dev40.",
            "cve": "CVE-2023-0434",
            "id": "pyup.io-54619",
            "more_info_path": "/vulnerabilities/CVE-2023-0434/54619",
            "specs": [
                ">=0,<0.5.0b3.dev40"
            ],
            "v": ">=0,<0.5.0b3.dev40"
        },
        {
            "advisory": "Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in mootools-more 1.6.0 allows a malicious user to inject properties into Object.prototype.",
            "cve": "CVE-2021-20088",
            "id": "pyup.io-65843",
            "more_info_path": "/vulnerabilities/CVE-2021-20088/65843",
            "specs": [
                ">=0,<0.5.0b3.dev41"
            ],
            "v": ">=0,<0.5.0b3.dev41"
        },
        {
            "advisory": "Excessive Attack Surface in GitHub repository pyload/pyload prior to 0.5.0b3.dev41.",
            "cve": "CVE-2023-0435",
            "id": "pyup.io-54622",
            "more_info_path": "/vulnerabilities/CVE-2023-0435/54622",
            "specs": [
                ">=0,<0.5.0b3.dev41"
            ],
            "v": ">=0,<0.5.0b3.dev41"
        },
        {
            "advisory": "Cross-site Scripting (XSS) - Stored in GitHub repository pyload/pyload prior to 0.5.0b3.dev42.",
            "cve": "CVE-2023-0488",
            "id": "pyup.io-54629",
            "more_info_path": "/vulnerabilities/CVE-2023-0488/54629",
            "specs": [
                ">=0,<0.5.0b3.dev42"
            ],
            "v": ">=0,<0.5.0b3.dev42"
        },
        {
            "advisory": "Improper Certificate Validation in GitHub repository pyload/pyload prior to 0.5.0b3.dev44.",
            "cve": "CVE-2023-0509",
            "id": "pyup.io-54646",
            "more_info_path": "/vulnerabilities/CVE-2023-0509/54646",
            "specs": [
                ">=0,<0.5.0b3.dev44"
            ],
            "v": ">=0,<0.5.0b3.dev44"
        }
    ],
    "pylons": [
        {
            "advisory": "pylons before 0.9.6.1 allows to access private controller methods to be accessed from the outside.",
            "cve": "PVE-2021-26042",
            "id": "pyup.io-26042",
            "more_info_path": "/vulnerabilities/PVE-2021-26042/26042",
            "specs": [
                "<0.9.6.1"
            ],
            "v": "<0.9.6.1"
        },
        {
            "advisory": "Pylons before 0.9.7 is vulnerable to a XSS attack on the default error page.\r\nhttps://github.com/Pylons/pylons/commit/b8f6bad8c7b88f93f759a933d88a765ac3f9c41a",
            "cve": "PVE-2021-26043",
            "id": "pyup.io-26043",
            "more_info_path": "/vulnerabilities/PVE-2021-26043/26043",
            "specs": [
                "<0.9.7"
            ],
            "v": "<0.9.7"
        },
        {
            "advisory": "Pylons 1.0.1rc1 fixes signed cookies by using standard base64 alphabet, and prevents timing attacks on signature comparison.\r\nhttps://github.com/Pylons/pylons/commit/054b43a46acfd3832de7c257d6c65805e7115169",
            "cve": "PVE-2021-26045",
            "id": "pyup.io-26045",
            "more_info_path": "/vulnerabilities/PVE-2021-26045/26045",
            "specs": [
                "<1.0.1rc1"
            ],
            "v": "<1.0.1rc1"
        },
        {
            "advisory": "Pylons 1.0.2 removes \"Post Traceback\" which was a possible XSS vector with prior versions of WebError.\r\nhttps://github.com/Pylons/pylons/commit/1955c15f564e4170b2376f4b64aed8dcdf4dfa88",
            "cve": "PVE-2021-26046",
            "id": "pyup.io-26046",
            "more_info_path": "/vulnerabilities/PVE-2021-26046/26046",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "pyloot": [
        {
            "advisory": "Pyloot 0.0.6 updates its NPM dependency 'elliptic' to v6.5.3 to include a security fix.",
            "cve": "CVE-2020-13822",
            "id": "pyup.io-40798",
            "more_info_path": "/vulnerabilities/CVE-2020-13822/40798",
            "specs": [
                "<0.0.6"
            ],
            "v": "<0.0.6"
        },
        {
            "advisory": "Pyloot 0.1.0 updates its NPM dependency 'ansi-regex' to v5.0.1 to include a security fix.",
            "cve": "CVE-2021-3807",
            "id": "pyup.io-52332",
            "more_info_path": "/vulnerabilities/CVE-2021-3807/52332",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        },
        {
            "advisory": "Pyloot 0.1.0 updates its NPM dependency 'qs' to v6.11.0 to include a security fix.",
            "cve": "CVE-2022-24999",
            "id": "pyup.io-52334",
            "more_info_path": "/vulnerabilities/CVE-2022-24999/52334",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        },
        {
            "advisory": "Pyloot 0.1.0 updates its NPM dependency 'ajv' to v6.12.6 to include a security fix.",
            "cve": "CVE-2020-15366",
            "id": "pyup.io-52316",
            "more_info_path": "/vulnerabilities/CVE-2020-15366/52316",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        }
    ],
    "pylsr": [
        {
            "advisory": "Pylsr 2021 updates its dependency \"pillow\" to a version >= 8.1.1 to include security fixes.",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-41733",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/41733",
            "specs": [
                "<2021"
            ],
            "v": "<2021"
        },
        {
            "advisory": "Pylsr 2021 updates its dependency \"pillow\" to a secure version. See: CVE-2020-35653.",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-41734",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/41734",
            "specs": [
                "<2021"
            ],
            "v": "<2021"
        },
        {
            "advisory": "Pylsr 2021 updates its dependency \"pillow\" to a version >= 8.1.1 to include security fixes.",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-41737",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/41737",
            "specs": [
                "<2021"
            ],
            "v": "<2021"
        },
        {
            "advisory": "Pylsr 2021 updates its dependency \"pillow\" to a version >= 8.1.1 to include security fixes.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-41299",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/41299",
            "specs": [
                "<2021"
            ],
            "v": "<2021"
        },
        {
            "advisory": "Pylsr 2021 updates its dependency \"pillow\" to a version >= 8.1.1 to include security fixes.",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-41735",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/41735",
            "specs": [
                "<2021"
            ],
            "v": "<2021"
        },
        {
            "advisory": "Pylsr 2021 updates its dependency \"pillow\" to a version >= 8.1.1 to include security fixes.",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-41736",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/41736",
            "specs": [
                "<2021"
            ],
            "v": "<2021"
        }
    ],
    "pymafka": [
        {
            "advisory": "Pymafka is a malicious package, pytosquatting. It opens a backdoor in victim's system.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-pypi-package-opens-backdoors-on-windows-linux-and-macs/",
            "cve": "PVE-2022-49433",
            "id": "pyup.io-49433",
            "more_info_path": "/vulnerabilities/PVE-2022-49433/49433",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pymatgen": [
        {
            "advisory": "Pymatgen 2024.2.20 addresses a critical vulnerability, CVE-2024-23346, allowing arbitrary code execution via a malicious CIF file. This issue stems from the insecure use of eval() in processing CIF file content, potentially leading to system compromise if exploited.\r\nhttps://github.com/materialsproject/pymatgen/security/advisories/GHSA-vgv8-5cpj-qj2f",
            "cve": "CVE-2022-42964",
            "id": "pyup.io-65638",
            "more_info_path": "/vulnerabilities/CVE-2022-42964/65638",
            "specs": [
                "<2024.2.20"
            ],
            "v": "<2024.2.20"
        },
        {
            "advisory": "Affected versions of the `pymatgen` package are vulnerable to Remote Code Execution due to the insecure use of the `eval()` function. The `JonesFaithfulTransformation.from_transformation_str()` method processes input using `eval()`, which can execute arbitrary code if the input is untrusted. An attacker can exploit this vulnerability by supplying a maliciously crafted string to the method, leading to the execution of arbitrary commands on the host system.",
            "cve": "CVE-2024-23346",
            "id": "pyup.io-65694",
            "more_info_path": "/vulnerabilities/CVE-2024-23346/65694",
            "specs": [
                ">=2017.06.08,<2024.2.20"
            ],
            "v": ">=2017.06.08,<2024.2.20"
        }
    ],
    "pymdown-extensions": [
        {
            "advisory": "Affected versions of the pymdown-extensions package are vulnerable to Regular Expression Denial of Service (ReDoS) due to an overly permissive regular expression that treats . as \u201cany character\u201d instead of a literal dot. The pymdownx.blocks.caption module\u2019s figure caption parsing uses the RE_FIG_NUM pattern (r'^(\\^)?([1-9][0-9]*(?:.[1-9][0-9]*)*)(?= |$)'), which can exhibit excessive backtracking on certain long inputs.",
            "cve": "CVE-2025-68142",
            "id": "pyup.io-82918",
            "more_info_path": "/vulnerabilities/CVE-2025-68142/82918",
            "specs": [
                "<10.16.1"
            ],
            "v": "<10.16.1"
        },
        {
            "advisory": "Pymdown-extensions 10.0 includes a fix for CVE-2023-32309: In affected versions an arbitrary file read is possible when using include file syntax. Any readable file on the host where the plugin is executing may have its content exposed. This can impact any use of Snippets that exposes the use of Snippets to external users. Users unable to upgrade may restrict relative paths by filtering input.\r\nhttps://github.com/facelessuser/pymdown-extensions/security/advisories/GHSA-jh85-wwv9-24hv",
            "cve": "CVE-2023-32309",
            "id": "pyup.io-58710",
            "more_info_path": "/vulnerabilities/CVE-2023-32309/58710",
            "specs": [
                ">=1.5,<10.0"
            ],
            "v": ">=1.5,<10.0"
        }
    ],
    "pymedusa": [
        {
            "advisory": "pymedusa is an automatic video library manager for TV Shows. In versions prior 1.0.12 an attacker with access to the web interface can update the git executable path in /config/general/ > advanced settings with arbitrary OS commands. An attacker may exploit this vulnerability to take execute arbitrary OS commands as the user running the pymedusa program. Users are advised to upgrade. There are no known workarounds for this vulnerability.",
            "cve": "CVE-2023-28627",
            "id": "pyup.io-62908",
            "more_info_path": "/vulnerabilities/CVE-2023-28627/62908",
            "specs": [
                "<1.0.12"
            ],
            "v": "<1.0.12"
        }
    ],
    "pymemcache": [
        {
            "advisory": "Pymemcache 1.3.7 fixes an injection vulnerability.\r\nhttps://github.com/pinterest/pymemcache/commit/feec79d7385a529e1ef79675b8c4daa4078d7398",
            "cve": "PVE-2021-26047",
            "id": "pyup.io-26047",
            "more_info_path": "/vulnerabilities/PVE-2021-26047/26047",
            "specs": [
                "<1.3.7"
            ],
            "v": "<1.3.7"
        }
    ],
    "pyminiracer": [
        {
            "advisory": "A heap overflow in Sqreen PyMiniRacer (aka Python Mini Racer) before 0.3.0 allows remote attackers to potentially exploit heap corruption. See: CVE-2020-25489.",
            "cve": "CVE-2020-25489",
            "id": "pyup.io-45596",
            "more_info_path": "/vulnerabilities/CVE-2020-25489/45596",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "pyminizip": [
        {
            "advisory": "Pyminizip 0.2.6 and prior versions are vulnerable to CVE-2023-45853: MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. Pyminizip is also vulnerable because it bundles an affected zlib version, and exposes the affected MiniZip code through its compress API.",
            "cve": "CVE-2023-45853",
            "id": "pyup.io-62980",
            "more_info_path": "/vulnerabilities/CVE-2023-45853/62980",
            "specs": [
                "<=0.2.6"
            ],
            "v": "<=0.2.6"
        },
        {
            "advisory": "Pyminizip 0.2.6 and prior versions include a vulnerable version of zlib (1.2.11).",
            "cve": "CVE-2018-25032",
            "id": "pyup.io-49913",
            "more_info_path": "/vulnerabilities/CVE-2018-25032/49913",
            "specs": [
                "<=0.2.6"
            ],
            "v": "<=0.2.6"
        }
    ],
    "pymisp": [
        {
            "advisory": "Pymisp 2.4.106 updates its dependency 'urllib3' to include a security fix.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-37292",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/37292",
            "specs": [
                "<2.4.106"
            ],
            "v": "<2.4.106"
        },
        {
            "advisory": "Pymisp v2.4.67 includes a security fix: do not try to load any valid path as a MISP Event.\r\n\r\nThe MISP Event loader was trying to open any string passed as parameter if is an existing file path. Anything that isn't a valid MISP event would raise an exception, but I can see it used for malicious purposes.\r\n\r\n`load_file` will do the same, but the user can decide if it is safe to  use.",
            "cve": "PVE-2021-38507",
            "id": "pyup.io-38507",
            "more_info_path": "/vulnerabilities/PVE-2021-38507/38507",
            "specs": [
                "<2.4.67"
            ],
            "v": "<2.4.67"
        }
    ],
    "pymls": [
        {
            "advisory": "Pymls 1.4.10 fixes the Github-reported security issues in requirements.txt and bumps PyYAML version in setup for security reasons (CVE-2017-18342).",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-37193",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/37193",
            "specs": [
                "<1.4.10"
            ],
            "v": "<1.4.10"
        }
    ],
    "pymobiledevice3": [
        {
            "advisory": "Affected versions of the pymobiledevice3 package are vulnerable to Arbitrary Code Execution due to the use of the insecure eval() function to process user-supplied input in the CLI. The lockdown set and accessibility settings set CLI commands directly pass user-provided value arguments to Python's eval() function without sanitization, allowing execution of arbitrary Python code.",
            "cve": "PVE-2026-84792",
            "id": "pyup.io-84792",
            "more_info_path": "/vulnerabilities/PVE-2026-84792/84792",
            "specs": [
                "<7.2.1"
            ],
            "v": "<7.2.1"
        }
    ],
    "pymodbus": [
        {
            "advisory": "Pymodbus 3.6.0 it is a fix for a path traversal vulnerability.\r\nhttps://github.com/pymodbus-dev/pymodbus/pull/1855",
            "cve": "PVE-2023-62733",
            "id": "pyup.io-62733",
            "more_info_path": "/vulnerabilities/PVE-2023-62733/62733",
            "specs": [
                "<3.6.0"
            ],
            "v": "<3.6.0"
        }
    ],
    "pymodbustcp": [
        {
            "advisory": "Pymodbustcp 0.0.5 secures frame size before struct.unpack invocation.\r\nhttps://github.com/sourceperl/pyModbusTCP/commit/19f3f4b101a71ad171e4fd12731aa6d88845dd73",
            "cve": "PVE-2017-47061",
            "id": "pyup.io-47061",
            "more_info_path": "/vulnerabilities/PVE-2017-47061/47061",
            "specs": [
                "<0.0.5"
            ],
            "v": "<0.0.5"
        }
    ],
    "pymongo": [
        {
            "advisory": "Pymongo 2.5.2 includes a fix for CVE-2013-2132: null pointer when decoding invalid DBRef.\r\nhttps://github.com/mongodb/mongo-python-driver/commit/a060c15ef87e0f0e72974c7c0e57fe811bbd06a2",
            "cve": "CVE-2013-2132",
            "id": "pyup.io-35429",
            "more_info_path": "/vulnerabilities/CVE-2013-2132/35429",
            "specs": [
                "<2.5.2"
            ],
            "v": "<2.5.2"
        },
        {
            "advisory": "Versions of the package pymongo before 4.6.3 are vulnerable to Out-of-bounds Read in the bson module. Using the crafted payload the attacker could force the parser to deserialize unmanaged memory. The parser tries to interpret bytes next to buffer and throws an exception with string. If the following bytes are not printable UTF-8 the parser throws an exception with a single byte.",
            "cve": "CVE-2024-5629",
            "id": "pyup.io-70626",
            "more_info_path": "/vulnerabilities/CVE-2024-5629/70626",
            "specs": [
                "<4.6.3"
            ],
            "v": "<4.6.3"
        }
    ],
    "pymysql": [
        {
            "advisory": "PyMySQL 1.1.1 addresses CVE-2024-36039, a critical SQL injection vulnerability present in versions up to 1.1.0. This vulnerability occurs when the library is used with untrusted JSON input because keys are not properly escaped by escape_dict, allowing attackers to inject malicious SQL queries.",
            "cve": "CVE-2024-36039",
            "id": "pyup.io-71083",
            "more_info_path": "/vulnerabilities/CVE-2024-36039/71083",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "pynecone": [
        {
            "advisory": "Pynecone 0.1.13 includes a fix for a Race Condition vulnerability in the websocket.\r\nhttps://github.com/reflex-dev/reflex/pull/261",
            "cve": "PVE-2023-59560",
            "id": "pyup.io-59560",
            "more_info_path": "/vulnerabilities/PVE-2023-59560/59560",
            "specs": [
                "<0.1.13"
            ],
            "v": "<0.1.13"
        },
        {
            "advisory": "Pynecone 0.1.33 updates its dependency 'fastapi' to version '0.96.0' to include a fix for an Improper Input Validation vulnerability.\r\nhttps://github.com/reflex-dev/reflex/pull/1172",
            "cve": "CVE-2023-29159",
            "id": "pyup.io-59559",
            "more_info_path": "/vulnerabilities/CVE-2023-29159/59559",
            "specs": [
                "<0.1.33"
            ],
            "v": "<0.1.33"
        }
    ],
    "pyngo": [
        {
            "advisory": "Pyngo 1.3.0 changes a requirement to \"django<4\" to include a security fix.",
            "cve": "CVE-2022-34265",
            "id": "pyup.io-49742",
            "more_info_path": "/vulnerabilities/CVE-2022-34265/49742",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "pyninja": [
        {
            "advisory": "Pyninja 0.0.4 adds HTTP basic authentication for the monitoring page.",
            "cve": "PVE-2024-73101",
            "id": "pyup.io-73101",
            "more_info_path": "/vulnerabilities/PVE-2024-73101/73101",
            "specs": [
                "<0.0.4"
            ],
            "v": "<0.0.4"
        },
        {
            "advisory": "Affected versions of Pyninja are potentially vulnerable to shell injection.",
            "cve": "PVE-2024-73106",
            "id": "pyup.io-73106",
            "more_info_path": "/vulnerabilities/PVE-2024-73106/73106",
            "specs": [
                "<0.0.4"
            ],
            "v": "<0.0.4"
        },
        {
            "advisory": "Affected versions of Pyninja are vulnerable to improper authorization. Access to the '/monitor' page was allowed without authentication. This page may expose sensitive information, including personally identifiable information (PII).",
            "cve": "PVE-2024-74788",
            "id": "pyup.io-74788",
            "more_info_path": "/vulnerabilities/PVE-2024-74788/74788",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pynitrokey": [
        {
            "advisory": "Pynitrokey 0.4.39 upgrades its cryptography dependency, moving from version range >=3.4.4,<37 to a new range of >=39.0.1,<39.1. This update addresses the security vulnerability identified in CVE-2023-23931.",
            "cve": "CVE-2023-23931",
            "id": "pyup.io-64461",
            "more_info_path": "/vulnerabilities/CVE-2023-23931/64461",
            "specs": [
                "<0.4.39"
            ],
            "v": "<0.4.39"
        }
    ],
    "pynoorm": [
        {
            "advisory": "Pynoorm 0.4.2 updates PyYaml to 4.2b4 to fix a security vulnerability.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-36789",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/36789",
            "specs": [
                "<0.4.2"
            ],
            "v": "<0.4.2"
        }
    ],
    "pynps": [
        {
            "advisory": "Pynps 1.2.0 removes support for search after updating database for security reasons.",
            "cve": "PVE-2021-37724",
            "id": "pyup.io-37724",
            "more_info_path": "/vulnerabilities/PVE-2021-37724/37724",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "pyo": [
        {
            "advisory": "The Pyo software up to and inclusive of version 1.03 has been found to exhibit a buffer overflow problem within the Server_jack_init function. This flaw could enable attackers to carry out Denial of Service attacks by establishing an overly lengthy server name.",
            "cve": "CVE-2021-41498",
            "id": "pyup.io-62712",
            "more_info_path": "/vulnerabilities/CVE-2021-41498/62712",
            "specs": [
                "<=1.03"
            ],
            "v": "<=1.03"
        },
        {
            "advisory": "Buffer Overflow Vulnerability exists in ajaxsoundstudio.com in Pyo < 1.03 in the Server_debug function, which allows remote attackers to conduct DoS attacks by deliberately passing on an overlong audio file name.",
            "cve": "CVE-2021-41499",
            "id": "pyup.io-54292",
            "more_info_path": "/vulnerabilities/CVE-2021-41499/54292",
            "specs": [
                ">=0,<1.0.3"
            ],
            "v": ">=0,<1.0.3"
        }
    ],
    "pyodb": [
        {
            "advisory": "Pyodb 0.1.2 updates its dependency 'tornado' to v6.3.2 to include a security fix.",
            "cve": "CVE-2023-28370",
            "id": "pyup.io-58814",
            "more_info_path": "/vulnerabilities/CVE-2023-28370/58814",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "pyodbc": [
        {
            "advisory": "Pyodbc 4.0.36 includes a security fix: Fetching a decimal greater than 100 digits would cause a buffer overflow.\r\nhttps://github.com/mkleehammer/pyodbc/commit/6b107a2bcaf7379e5ba182007b6ecae1bc2fc931",
            "cve": "PVE-2023-54980",
            "id": "pyup.io-54980",
            "more_info_path": "/vulnerabilities/PVE-2023-54980/54980",
            "specs": [
                "<4.0.36"
            ],
            "v": "<4.0.36"
        }
    ],
    "pyoes": [
        {
            "advisory": "Pyoes 0.9.0 updates its dependency 'jinja2' to 2.10.1 to include security fixes.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-49090",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/49090",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Pyoes 0.9.0 updates its dependency 'pyramid' to 1.10.4 to include security fixes.",
            "cve": "PVE-2021-32203",
            "id": "pyup.io-49088",
            "more_info_path": "/vulnerabilities/PVE-2021-32203/49088",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Pyoes 0.9.0 updates its dependency 'pyramid' to 1.10.4 to include security fixes.",
            "cve": "PVE-2022-48337",
            "id": "pyup.io-37254",
            "more_info_path": "/vulnerabilities/PVE-2022-48337/37254",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Pyoes 0.9.0 updates its dependency 'jinja2' to 2.10.1 to include security fixes.",
            "cve": "CVE-2016-10745",
            "id": "pyup.io-49089",
            "more_info_path": "/vulnerabilities/CVE-2016-10745/49089",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Pyoes 0.9.0 updates its dependency 'pyramid' to 1.10.4 to include security fixes.",
            "cve": "CVE-2014-4671",
            "id": "pyup.io-49087",
            "more_info_path": "/vulnerabilities/CVE-2014-4671/49087",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        }
    ],
    "pyogrio": [
        {
            "advisory": "Pyogrio 0.7.2 and prior releases for Windows ship with a version of 'libcurl' (8.2.1) that has a high-severity vulnerability.",
            "cve": "CVE-2023-38545",
            "id": "pyup.io-61775",
            "more_info_path": "/vulnerabilities/CVE-2023-38545/61775",
            "specs": [
                "<=0.7.2"
            ],
            "v": "<=0.7.2"
        }
    ],
    "pyopenssl": [
        {
            "advisory": "The X509Extension in pyOpenSSL before 0.13.1 does not properly handle a '\\0' character in a domain name in the Subject Alternative Name field of an X.509 certificate, which allows man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority.",
            "cve": "CVE-2013-4314",
            "id": "pyup.io-35460",
            "more_info_path": "/vulnerabilities/CVE-2013-4314/35460",
            "specs": [
                "<0.13.1"
            ],
            "v": "<0.13.1"
        },
        {
            "advisory": "Pyopenssl 17.5.0 includes a fix for CVE-2018-1000808: Failure to Release Memory Before Removing Last Reference vulnerability in PKCS #12 store that can result in denial-of-service if memory runs low or is exhausted. This attack appears to be exploitable via Depends upon calling application, however it could be as simple as initiating a TLS connection. Anything that would cause the calling application to reload certificates from a PKCS #12 store.\r\n#NOTE: The data we include in this advisory differs from the publicly available on nvd.nist.gov. 'cryptography' dependency was introduced in release 0.14a2.",
            "cve": "CVE-2018-1000808",
            "id": "pyup.io-36534",
            "more_info_path": "/vulnerabilities/CVE-2018-1000808/36534",
            "specs": [
                ">=0.14,<17.5.0"
            ],
            "v": ">=0.14,<17.5.0"
        },
        {
            "advisory": "Pyopenssl 17.5.0 includes a fix for CVE-2018-1000807: Use After Free vulnerability in X509 object handling that can possibly lead to denial of service or remote code execution. This attack appears to be exploitable via 'Depends' on the calling application and if it retains a reference to the memory.\r\n#NOTE: The data we include in this advisory differs from the publicly available on nvd.nist.gov. 'cryptography' dependency was introduced in release 0.14a2.",
            "cve": "CVE-2018-1000807",
            "id": "pyup.io-36533",
            "more_info_path": "/vulnerabilities/CVE-2018-1000807/36533",
            "specs": [
                ">=0.14,<17.5.0"
            ],
            "v": ">=0.14,<17.5.0"
        }
    ],
    "pyoracleclient": [
        {
            "advisory": "Pyoracleclient versions before 0.2.5 use unsafe \"os.system\" in \"pyoracleclient/pyoracleclient.py\". Under non-trusted input, it could lead to OS injection.\r\nhttps://github.com/LucaMingarelli/PyOracleClient/commit/dd8f5ad3d2221b8d64862580b59abb17b1404ee3#diff-59c9491d71372f3c5b850f3242b32a6f54e8354e83f26179dc85be05e00fbe21",
            "cve": "PVE-2021-41761",
            "id": "pyup.io-41761",
            "more_info_path": "/vulnerabilities/PVE-2021-41761/41761",
            "specs": [
                "<0.2.5"
            ],
            "v": "<0.2.5"
        }
    ],
    "pyorient": [
        {
            "advisory": "Pyorient 1.4.9 fixes a SQL injection vulnerability.\r\nhttps://github.com/mogui/pyorient/pull/182",
            "cve": "PVE-2021-34150",
            "id": "pyup.io-34150",
            "more_info_path": "/vulnerabilities/PVE-2021-34150/34150",
            "specs": [
                "<1.4.9"
            ],
            "v": "<1.4.9"
        },
        {
            "advisory": "A vulnerability has been detected in pyorient before 1.4.7, an Orientdb driver for Python, where SQL Injection allows an attacker to alter the WHERE clause in a query, leading to unexpected results.\r\nhttps://github.com/mogui/pyorient/pull/172/commits/f1840d6deff8e97ffd4d7a0b3842fee09e8911f7",
            "cve": "PVE-2024-99768",
            "id": "pyup.io-66657",
            "more_info_path": "/vulnerabilities/PVE-2024-99768/66657",
            "specs": [
                ">=0,<1.4.7"
            ],
            "v": ">=0,<1.4.7"
        }
    ],
    "pyowm": [
        {
            "advisory": "pyowm 2.10 upgrades version for dependencies `requests` and `urllib3` as known security issues were raised for them.",
            "cve": "PVE-2021-36750",
            "id": "pyup.io-36750",
            "more_info_path": "/vulnerabilities/PVE-2021-36750/36750",
            "specs": [
                "<2.10"
            ],
            "v": "<2.10"
        }
    ],
    "pypdf": [
        {
            "advisory": "Affected versions of the pypdf package are vulnerable to Denial of Service (DoS) due to unbounded decompression of FlateDecode-encoded streams that can exhaust memory. The `pypdf.filters.decompress` function used by the `FlateDecode` filter, invoked by `PdfReader` when parsing cross-reference streams via `_reader._read_pdf15_xref_stream` and when accessing other content streams, failed to enforce a maximum decompressed output length. An attacker can exploit this by providing a crafted PDF whose cross-reference stream chains FlateDecode filters so that simply opening the file with `PdfReader` triggers excessive memory allocation, leading to process termination or service unavailability without authentication.",
            "cve": "CVE-2025-55197",
            "id": "pyup.io-78709",
            "more_info_path": "/vulnerabilities/CVE-2025-55197/78709",
            "specs": [
                "<6.0.0"
            ],
            "v": "<6.0.0"
        },
        {
            "advisory": "Affected versions of the pypdf package are vulnerable to Denial of Service (DoS) due to an infinite loop in the DCTDecode inline image parser when the end-of-image marker is missing. The extract_inline_DCT function in pypdf/generic/_image_inline.py reads bytes from an inline DCT image while parsing a page\u2019s content stream and, for malformed JPEG data lacking the 0xFFD9 EOI marker, fails to reach a termination condition, permitting unbounded iteration.",
            "cve": "CVE-2025-62707",
            "id": "pyup.io-80589",
            "more_info_path": "/vulnerabilities/CVE-2025-62707/80589",
            "specs": [
                "<6.1.3"
            ],
            "v": "<6.1.3"
        },
        {
            "advisory": "Affected versions of the pypdf package are vulnerable to Denial of Service (DoS) due to unbounded decompression of LZWDecode streams in page content that lack an enforced output-size limit. The LZWDecode filter path in pypdf/filters.py invoked _LzwCodec.decode from pypdf/_codecs/_codecs.py without bounding the decompressed output, permitting extremely high expansion ratios during decode() and uncontrolled memory allocation.",
            "cve": "CVE-2025-62708",
            "id": "pyup.io-80590",
            "more_info_path": "/vulnerabilities/CVE-2025-62708/80590",
            "specs": [
                "<6.1.3"
            ],
            "v": "<6.1.3"
        },
        {
            "advisory": "Affected versions of the pypdf package are vulnerable to Denial of Service (DoS) due to insufficient limiting of memory usage when decoding LZWDecode content streams. The pypdf.filters LZWDecode implementation allows attacker-controlled page content streams to be decompressed without an effective maximum output size, so a single highly compressed stream can expand to roughly 1 GB of in-memory data during parsing.",
            "cve": "CVE-2025-66019",
            "id": "pyup.io-81877",
            "more_info_path": "/vulnerabilities/CVE-2025-66019/81877",
            "specs": [
                "<6.4.0"
            ],
            "v": "<6.4.0"
        },
        {
            "advisory": "Affected versions of the pypdf package are vulnerable to Denial of Service (DoS) due to inefficient cross-reference table rebuilding when handling malformed startxref data in non-strict mode. In pypdf._reader.PdfReader._rebuild_xref_table(), the non-strict recovery path scans the entire PDF buffer with a re.finditer() pattern to rediscover obj markers, which can take excessively long on inputs dominated by whitespace.",
            "cve": "CVE-2026-22691",
            "id": "pyup.io-84345",
            "more_info_path": "/vulnerabilities/CVE-2026-22691/84345",
            "specs": [
                "<6.6.0"
            ],
            "v": "<6.6.0"
        },
        {
            "advisory": "Affected versions of the pypdf package are vulnerable to Denial of Service (DoS) due to unbounded Root-object recovery work driven by an attacker-controlled /Size trailer value when /Root is missing in non-strict mode. In pypdf\u2019s PdfReader non-strict parsing path, omitting the trailer /Root entry while setting a huge/Size causes the reader to attempt to access object numbers up to the /Size limit (mitigated in later versions via the root_object_recovery_limit control), resulting in potentially long runtimes on invalid PDFs.",
            "cve": "CVE-2026-22690",
            "id": "pyup.io-84344",
            "more_info_path": "/vulnerabilities/CVE-2026-22690/84344",
            "specs": [
                "<6.6.0"
            ],
            "v": "<6.6.0"
        },
        {
            "advisory": "Affected versions of the pypdf package are vulnerable to Denial of Service (DoS) due to missing cycle detection when traversing PDF outlines/bookmarks. The PdfReader.outline property calls _get_outline() in pypdf/_doc_common.py, which iterates through outline nodes (including /Next and nested /First entries) without reliably tracking visited nodes, allowing a crafted cyclic outline structure to trigger an infinite loop.",
            "cve": "CVE-2026-24688",
            "id": "pyup.io-85196",
            "more_info_path": "/vulnerabilities/CVE-2026-24688/85196",
            "specs": [
                "<6.6.2"
            ],
            "v": "<6.6.2"
        },
        {
            "advisory": "Pypdf 3.9.0 includes a fix for CVE-2023-36464: In affected versions an attacker may craft a PDF which leads to an infinite loop if '__parse_content_stream' is executed. That is, for example, the case if the user extracted text from such a PDF. This issue was introduced in pull request #969 and resolved in pull request #1828. Users unable to upgrade may modify the line 'while peek not in (b\"\\r\", b\"\\n\")' in 'pypdf/generic/_data_structures.py' to 'while peek not in (b\"\\r\", b\"\\n\", b\"\")'.\r\nhttps://github.com/py-pdf/pypdf/pull/1828\r\nhttps://github.com/py-pdf/pypdf/security/advisories/GHSA-4vvm-4w3v-6mr8",
            "cve": "CVE-2023-36464",
            "id": "pyup.io-59231",
            "more_info_path": "/vulnerabilities/CVE-2023-36464/59231",
            "specs": [
                "<=3.8.1"
            ],
            "v": "<=3.8.1"
        },
        {
            "advisory": "Pypdf 3.17.0 includes a fix for CVE-2023-46250: An attacker who uses a vulnerability present in versions 3.7.0 through 3.16.4 can craft a PDF which leads to an infinite loop. This infinite loop blocks the current process and can utilize a single core of the CPU by 100%. It does not affect memory usage. That is, for example, the case when the pypdf-user manipulates an incoming malicious PDF e.g. by merging it with another PDF or by adding annotations. As a workaround, apply the patch manually by modifying 'pypdf/generic/_data_structures.py'.\r\nhttps://github.com/py-pdf/pypdf/security/advisories/GHSA-wjcc-cq79-p63f",
            "cve": "CVE-2023-46250",
            "id": "pyup.io-62123",
            "more_info_path": "/vulnerabilities/CVE-2023-46250/62123",
            "specs": [
                ">=3.7.0,<=3.16.4"
            ],
            "v": ">=3.7.0,<=3.16.4"
        }
    ],
    "pypdf-table-extraction": [
        {
            "advisory": "Pypdf-table-extraction 0.0.2 includes a fix for a potential shell injection vulnerability.",
            "cve": "PVE-2024-74101",
            "id": "pyup.io-74101",
            "more_info_path": "/vulnerabilities/PVE-2024-74101/74101",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        }
    ],
    "pypdf2": [
        {
            "advisory": "Pypdf2 2.10.6 fixes a potential DoS vulnerability.\r\nhttps://github.com/py-pdf/pypdf/pull/1331",
            "cve": "PVE-2022-52548",
            "id": "pyup.io-52548",
            "more_info_path": "/vulnerabilities/PVE-2022-52548/52548",
            "specs": [
                "<2.10.6"
            ],
            "v": "<2.10.6"
        },
        {
            "advisory": "PyPDF2 1.27.5 includes a fix for CVE-2022-24859: In versions prior to 1.27.5 an attacker can craft a PDF which leads to an infinite loop if PyPDF2 code attempts to get the content stream. The reason is that the last while-loop in 'ContentStream._readInlineImage' only terminates when it finds the 'EI' token, but never actually checks if the stream has already ended. Users unable to upgrade should validate PDFs prior to iterating over their content stream.\r\nhttps://github.com/py-pdf/PyPDF2/security/advisories/GHSA-xcjx-m2pj-8g79",
            "cve": "CVE-2022-24859",
            "id": "pyup.io-48186",
            "more_info_path": "/vulnerabilities/CVE-2022-24859/48186",
            "specs": [
                "<=1.27.4"
            ],
            "v": "<=1.27.4"
        },
        {
            "advisory": "Pypdf2 1.27.9 includes a fix for CVE-2023-36810: An attacker who uses this vulnerability can craft a PDF which leads to unexpected long runtime. This quadratic runtime blocks the current process and can utilize a single core of the CPU by 100%. It does not affect memory usage.\r\nhttps://github.com/py-pdf/pypdf/security/advisories/GHSA-jrm6-h9cq-8gqw",
            "cve": "CVE-2023-36810",
            "id": "pyup.io-59256",
            "more_info_path": "/vulnerabilities/CVE-2023-36810/59256",
            "specs": [
                "<=1.27.8"
            ],
            "v": "<=1.27.8"
        },
        {
            "advisory": "PyPDF2 2.10.6 includes a fix for a Denial of Service vulnerability: In version 2.10.5 an attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This infinite loop blocks the current process and can utilize a single core of the CPU by 100%. It does not affect memory usage. That is, for example, the case if the user extracted metadata from such a malformed PDF. Versions prior to 2.10.5 throw an error, but do not hang forever.\r\nhttps://github.com/py-pdf/pypdf/pull/1331\r\nhttps://github.com/advisories/GHSA-hm9v-vj3r-r55m",
            "cve": "CVE-2023-36807",
            "id": "pyup.io-59255",
            "more_info_path": "/vulnerabilities/CVE-2023-36807/59255",
            "specs": [
                "==2.10.5"
            ],
            "v": "==2.10.5"
        },
        {
            "advisory": "Pypdf2 is vulnerable to CVE-2023-36464: An attacker may craft a PDF which leads to an infinite loop if '__parse_content_stream' is executed. That is, for example, the case if the user extracted text from such a PDF. Users may modify the line 'while peek not in (b\"\\r\", b\"\\n\")' in 'pypdf/generic/_data_structures.py' to 'while peek not in (b\"\\r\", b\"\\n\", b\"\")' as a workaround.\r\nhttps://github.com/py-pdf/pypdf/pull/1828\r\nhttps://github.com/py-pdf/pypdf/security/advisories/GHSA-4vvm-4w3v-6mr8",
            "cve": "CVE-2023-36464",
            "id": "pyup.io-59234",
            "more_info_path": "/vulnerabilities/CVE-2023-36464/59234",
            "specs": [
                ">=2.2.0,<=3.0.1"
            ],
            "v": ">=2.2.0,<=3.0.1"
        }
    ],
    "pypdfium2": [
        {
            "advisory": "Pypdfium2 3.9.0 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.",
            "cve": "CVE-2007-4559",
            "id": "pyup.io-51974",
            "more_info_path": "/vulnerabilities/CVE-2007-4559/51974",
            "specs": [
                "<3.9.0"
            ],
            "v": "<3.9.0"
        }
    ],
    "pyphi": [
        {
            "advisory": "Pyphi 1.2.0 includes a security patch for the function 'load_file' in 'pyphi/conf.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/wmayner/pyphi/commit/494023f9eec4a17a8ab3f70c04fc314ecb7de777#diff-d4ca6ddd6df63ee73ec2ce90f8982e22cb4aa8833367feea781224d2f9a54dcc",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41375",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41375",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        }
    ],
    "pypickle": [
        {
            "advisory": "A vulnerability was found in erdogant pypickle up to 1.1.5 and classified as problematic. Affected by this issue is the function load of the file pypickle/pypickle.py. The manipulation leads to deserialization. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The patch is identified as 14b4cae704a0bb4eb6723e238f25382d847a1917. It is recommended to upgrade the affected component.",
            "cve": "CVE-2025-5174",
            "id": "pyup.io-77706",
            "more_info_path": "/vulnerabilities/CVE-2025-5174/77706",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "A vulnerability was found in erdogant pypickle up to 1.1.5. It has been classified as critical. This affects the function Save of the file pypickle/pypickle.py. The manipulation leads to improper authorization. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The patch is named 14b4cae704a0bb4eb6723e238f25382d847a1917. It is recommended to upgrade the affected component.",
            "cve": "CVE-2025-5175",
            "id": "pyup.io-77707",
            "more_info_path": "/vulnerabilities/CVE-2025-5175/77707",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        }
    ],
    "pypicloud": [
        {
            "advisory": "Pypicloud before 0.2.2 doesn't validate passwords always.\r\nhttps://github.com/stevearc/pypicloud/commit/001e8a5ba86ceff0e212ffa1436801ff6d9293ce",
            "cve": "PVE-2021-26048",
            "id": "pyup.io-26048",
            "more_info_path": "/vulnerabilities/PVE-2021-26048/26048",
            "specs": [
                "<0.2.2"
            ],
            "v": "<0.2.2"
        },
        {
            "advisory": "Pypicloud 1.2.1 updates its NPM dependency 'underscore' to v1.13.1 to include a security fix.",
            "cve": "CVE-2021-23358",
            "id": "pyup.io-52662",
            "more_info_path": "/vulnerabilities/CVE-2021-23358/52662",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Pypicloud 1.2.1 includes a fix for a XSS vulnerability from HTML injected in package name.\r\nhttps://github.com/stevearc/pypicloud/commit/33d6ea1012056f230d196d493fe4fa663baf7e2d",
            "cve": "PVE-2022-52594",
            "id": "pyup.io-52594",
            "more_info_path": "/vulnerabilities/PVE-2022-52594/52594",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        }
    ],
    "pypinksign": [
        {
            "advisory": "PyPinkSign v0.5.1 uses a non-random or static IV for Cipher Block Chaining (CBC) mode in AES encryption. This vulnerability can lead to the disclosure of information and communications.",
            "cve": "CVE-2023-48056",
            "id": "pyup.io-65190",
            "more_info_path": "/vulnerabilities/CVE-2023-48056/65190",
            "specs": [
                ">=0,<=0.5.1"
            ],
            "v": ">=0,<=0.5.1"
        }
    ],
    "pypiserver": [
        {
            "advisory": "Pypiserver before 1.1.7 is vulnerable to XSS attacks.\r\nhttps://github.com/pypiserver/pypiserver/issues/77\r\nhttps://github.com/pypiserver/pypiserver/pull/78",
            "cve": "PVE-2021-26049",
            "id": "pyup.io-26049",
            "more_info_path": "/vulnerabilities/PVE-2021-26049/26049",
            "specs": [
                "<1.1.7"
            ],
            "v": "<1.1.7"
        },
        {
            "advisory": "Pypiserver 1.2.6 includes a fix for CVE-2019-6802: CRLF Injection in pypiserver 1.2.5 and below allows attackers to set arbitrary HTTP headers and possibly conduct XSS attacks via a %0d%0a in a URI.\r\nhttps://github.com/pypiserver/pypiserver/commit/1375a67c55a9b8d4619df30d2a1c0b239d7357e6",
            "cve": "CVE-2019-6802",
            "id": "pyup.io-42268",
            "more_info_path": "/vulnerabilities/CVE-2019-6802/42268",
            "specs": [
                "<=1.2.5"
            ],
            "v": "<=1.2.5"
        }
    ],
    "pyplanet": [
        {
            "advisory": "pyplanet 0.6.2 - security: Upgraded library to solve security issues (requests library).",
            "cve": "PVE-2021-36666",
            "id": "pyup.io-36666",
            "more_info_path": "/vulnerabilities/PVE-2021-36666/36666",
            "specs": [
                "<0.6.2"
            ],
            "v": "<0.6.2"
        },
        {
            "advisory": "Pyplanet 0.7.0 updates its dependency 'jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-37476",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/37476",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Pyplanet 0.7.0 updates its dependency 'pyyaml' to v5.1.2 to include a security fix.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-49095",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/49095",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Pyplanet 0.7.0 updates its dependency 'urllib3' to v1.25.3 to include security fixes.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-49093",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/49093",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Pyplanet 0.7.0 updates its dependency 'urllib3' to v1.25.3 to include security fixes.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-49092",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/49092",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Pyplanet 0.7.0 updates its dependency 'numpy' to v1.17.2 to include a security fix.",
            "cve": "CVE-2019-6446",
            "id": "pyup.io-49094",
            "more_info_path": "/vulnerabilities/CVE-2019-6446/49094",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        }
    ],
    "pypolicyd-spf": [
        {
            "advisory": "OpenDMARC through 1.3.2 and 1.4.x, when used with pypolicyd-spf 2.0.2, allows attacks that bypass SPF and DMARC authentication in situations where the HELO field is inconsistent with the MAIL FROM field.",
            "cve": "CVE-2019-20790",
            "id": "pyup.io-70574",
            "more_info_path": "/vulnerabilities/CVE-2019-20790/70574",
            "specs": [
                "<=2.0.2"
            ],
            "v": "<=2.0.2"
        }
    ],
    "pypop-genomics": [
        {
            "advisory": "A vulnerability in PyPop before 1.0.2 involves improper function calls, such as missing or incorrectly typed arguments, and the use of redundant null pointers. Users are advised to upgrade their installation to mitigate the vulnerability, following specific upgrade instructions. There are no alternative workarounds mentioned for this issue.",
            "cve": "PVE-2024-68473",
            "id": "pyup.io-68473",
            "more_info_path": "/vulnerabilities/PVE-2024-68473/68473",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "pypostalcode": [
        {
            "advisory": "Pypostalcode 0.3.5 fixes an SQL injection vulnerability (passing user input FSA codes could delete your FSA code database).\r\nhttps://github.com/inkjet/pypostalcode/commit/fccd60a84e8dcd8d7d6b7480ed19d05f969e7190",
            "cve": "PVE-2021-40033",
            "id": "pyup.io-40033",
            "more_info_path": "/vulnerabilities/PVE-2021-40033/40033",
            "specs": [
                "<0.3.5"
            ],
            "v": "<0.3.5"
        }
    ],
    "pypqc": [
        {
            "advisory": "An attacker capable of submitting numerous ciphertexts to a single private key and obtaining real-time responses can exploit a vulnerability, known as KyberSlash, to recover the private key. This issue affects select versions of PyPQC and is addressed in version 0.0.6.1 onwards. There are no workarounds for this vulnerability; however, updating from 0.0.6 to 0.0.6.1 is advised as it is intended to be a simple drop-in replacement without known breaking changes.",
            "cve": "PVE-2024-68093",
            "id": "pyup.io-68093",
            "more_info_path": "/vulnerabilities/PVE-2024-68093/68093",
            "specs": [
                "<0.0.6.1"
            ],
            "v": "<0.0.6.1"
        }
    ],
    "pyproj": [
        {
            "advisory": "Pyproj 3.6.1 updates its bundled dependency 'libwebp' to include a fix for a high risk vulnerability. Only mac OS X wheels on PyPI were affected.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62312",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62312",
            "specs": [
                ">=2.6.1,<3.6.1"
            ],
            "v": ">=2.6.1,<3.6.1"
        }
    ],
    "pyprt": [
        {
            "advisory": "Pyprt 1.4.0 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-25287",
            "id": "pyup.io-43018",
            "more_info_path": "/vulnerabilities/CVE-2021-25287/43018",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Pyprt 1.4.0 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28675",
            "id": "pyup.io-43020",
            "more_info_path": "/vulnerabilities/CVE-2021-28675/43020",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Pyprt 1.4.0 updates its dependency 'pywin32' to v301 to include a security fix.",
            "cve": "CVE-2021-32559",
            "id": "pyup.io-43022",
            "more_info_path": "/vulnerabilities/CVE-2021-32559/43022",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Pyprt 1.4.0 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-43019",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/43019",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Pyprt 1.4.0 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-41220",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/41220",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Pyprt 1.4.0 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-25288",
            "id": "pyup.io-43017",
            "more_info_path": "/vulnerabilities/CVE-2021-25288/43017",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Pyprt 1.4.0 updates its dependency 'pillow' to v8.2.0 to include security fixes.",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-43021",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/43021",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Pyprt 1.5.0 updates its dependency 'pillow' to v8.3.2 to include security fixes.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-44490",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/44490",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        },
        {
            "advisory": "Pyprt 1.5.0 updates its dependency 'jupyterlab' to v3.0.17 to include a security fix.",
            "cve": "CVE-2021-32797",
            "id": "pyup.io-44556",
            "more_info_path": "/vulnerabilities/CVE-2021-32797/44556",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        },
        {
            "advisory": "Pyprt 1.5.0 updates its dependency 'notebook' to v6.4.1 to include a security fix.",
            "cve": "CVE-2021-32798",
            "id": "pyup.io-44557",
            "more_info_path": "/vulnerabilities/CVE-2021-32798/44557",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        },
        {
            "advisory": "Pyprt 1.5.0 updates its dependency 'pillow' to v8.3.2 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-44554",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/44554",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        }
    ],
    "pyptext": [
        {
            "advisory": "Pyptext is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51680",
            "id": "pyup.io-51680",
            "more_info_path": "/vulnerabilities/PVE-2022-51680/51680",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pypx800v5": [
        {
            "advisory": "Pypx800v5 version 1.2.1 updates its `aiohttp` dependency from 3.9.3 to 3.9.5 to address several security vulnerabilities, including CVE-2024-27306. This update ensures the application remains secure by incorporating the necessary fixes provided in the latest version of the `aiohttp` library.",
            "cve": "CVE-2024-30251",
            "id": "pyup.io-71177",
            "more_info_path": "/vulnerabilities/CVE-2024-30251/71177",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Pypx800v5 version 1.2.1 updates its `requests` dependency from 2.31.0 to 2.32.2 to address multiple security vulnerabilities, including CVE-2024-35195. This update ensures the application is protected against known issues in the older version of the `requests` library.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-71169",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/71169",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        }
    ],
    "pypxe": [
        {
            "advisory": "Affected versions of the PyPXE package are vulnerable to Buffer Overflow due to improper packet length validation in the `tftp` module. The `handle` function in the `tftp` module attempts to unpack the opcode using `struct.unpack('!H', self.message[:2])` without verifying that the packet length is at least two bytes, which can lead to buffer overflow. A remote attacker can exploit this by sending a specially crafted undersized packet to the PyPXE `tftp` handle function, causing the TFTP component to crash and resulting in a Denial of Service.",
            "cve": "CVE-2023-46960",
            "id": "pyup.io-78717",
            "more_info_path": "/vulnerabilities/CVE-2023-46960/78717",
            "specs": [
                "<=1.8.4"
            ],
            "v": "<=1.8.4"
        }
    ],
    "pyqlib": [
        {
            "advisory": "This affects all versions of package pyqlib. The workflow function in cli part of pyqlib was using an unsafe YAML load function. See CVE-2021-23338.",
            "cve": "CVE-2021-23338",
            "id": "pyup.io-40060",
            "more_info_path": "/vulnerabilities/CVE-2021-23338/40060",
            "specs": [
                ">=0.0.0"
            ],
            "v": ">=0.0.0"
        }
    ],
    "pyquokka": [
        {
            "advisory": "Affected versions of the pyquokka package are vulnerable to Deserialization of Untrusted Data due to unsafe use of pickle.loads on client-supplied Flight action bodies. The FlightServer.do_action method in pyquokka/flight.py (line 283) deserializes unvalidated data, with additional unsafe use of pickle.loads in cache_garbage_collect, do_put, and do_get, enabling arbitrary object construction.",
            "cve": "CVE-2025-62515",
            "id": "pyup.io-80471",
            "more_info_path": "/vulnerabilities/CVE-2025-62515/80471",
            "specs": [
                "<=0.3.1"
            ],
            "v": "<=0.3.1"
        }
    ],
    "pyr2": [
        {
            "advisory": "Pyr2 includes as submodule radare2 prior to 5.6.4. which is vulnerable to CVE-2022-0676.",
            "cve": "CVE-2022-0676",
            "id": "pyup.io-62862",
            "more_info_path": "/vulnerabilities/CVE-2022-0676/62862",
            "specs": [
                "<5.6.4"
            ],
            "v": "<5.6.4"
        },
        {
            "advisory": "Pyr2 includes as submodule radare2 prior to 5.6.4. which is vulnerable to CVE-2022-0713.",
            "cve": "CVE-2022-0713",
            "id": "pyup.io-62863",
            "more_info_path": "/vulnerabilities/CVE-2022-0713/62863",
            "specs": [
                "<5.6.4"
            ],
            "v": "<5.6.4"
        },
        {
            "advisory": "Pyr2 includes as submodule radare2 below 5.6.4. which is vulnerable to CVE-2022-0712.",
            "cve": "CVE-2022-0712",
            "id": "pyup.io-62861",
            "more_info_path": "/vulnerabilities/CVE-2022-0712/62861",
            "specs": [
                "<5.6.4"
            ],
            "v": "<5.6.4"
        },
        {
            "advisory": "Pyr2 includes as submodule radare2 prior to 5.6.8. which is vulnerable to CVE-2022-1207.",
            "cve": "CVE-2022-1207",
            "id": "pyup.io-62860",
            "more_info_path": "/vulnerabilities/CVE-2022-1207/62860",
            "specs": [
                "<5.6.8"
            ],
            "v": "<5.6.8"
        },
        {
            "advisory": "Pyr2 includes as submodule radare2 version 4.5.1, which is vulnerable to CVE-2023-27114.",
            "cve": "CVE-2023-27114",
            "id": "pyup.io-59508",
            "more_info_path": "/vulnerabilities/CVE-2023-27114/59508",
            "specs": [
                "<=2.0.0"
            ],
            "v": "<=2.0.0"
        },
        {
            "advisory": "Pyr2 includes as submodule radare2 version 4.5.1, which is vulnerable to CVE-2023-0302.",
            "cve": "CVE-2023-0302",
            "id": "pyup.io-59510",
            "more_info_path": "/vulnerabilities/CVE-2023-0302/59510",
            "specs": [
                "<=2.0.0"
            ],
            "v": "<=2.0.0"
        },
        {
            "advisory": "Pyr2 includes as submodule radare2 version 4.5.1, which is vulnerable to CVE-2023-1605.",
            "cve": "CVE-2023-1605",
            "id": "pyup.io-59512",
            "more_info_path": "/vulnerabilities/CVE-2023-1605/59512",
            "specs": [
                "<=2.0.0"
            ],
            "v": "<=2.0.0"
        }
    ],
    "pyrad": [
        {
            "advisory": "Pyrad before 0.6 isn't handling timeouts in client module correctly, leading to a potential denial of service.",
            "cve": "PVE-2021-26050",
            "id": "pyup.io-26050",
            "more_info_path": "/vulnerabilities/PVE-2021-26050/26050",
            "specs": [
                "<0.6"
            ],
            "v": "<0.6"
        },
        {
            "advisory": "The CreateID function in packet.py in pyrad before 2.1 uses sequential packet IDs, which makes it easier for remote attackers to spoof packets by predicting the next ID, a different vulnerability than CVE-2013-0294.",
            "cve": "CVE-2013-0342",
            "id": "pyup.io-42236",
            "more_info_path": "/vulnerabilities/CVE-2013-0342/42236",
            "specs": [
                "<2.1"
            ],
            "v": "<2.1"
        },
        {
            "advisory": "packet.py in pyrad before 2.1 uses weak random numbers to generate RADIUS authenticators and hash passwords, which makes it easier for remote attackers to obtain sensitive information via a brute force attack.",
            "cve": "CVE-2013-0294",
            "id": "pyup.io-54055",
            "more_info_path": "/vulnerabilities/CVE-2013-0294/54055",
            "specs": [
                ">=0,<2.1"
            ],
            "v": ">=0,<2.1"
        }
    ],
    "pyradiomics": [
        {
            "advisory": "Pyradiomics before 1.1.1 used 'eval' which is not secure.\r\nhttps://github.com/AIM-Harvard/pyradiomics/commit/d14e4064580f35f37bc53807246b72d8b451af31",
            "cve": "PVE-2021-36302",
            "id": "pyup.io-36302",
            "more_info_path": "/vulnerabilities/PVE-2021-36302/36302",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "pyradiomics-cuda": [
        {
            "advisory": "Affected versions of the project were potentially vulnerable to Integer Overflow. An attacker could potentially exploit this by providing input that causes an overflow, leading to incorrect memory access or manipulation.",
            "cve": "PVE-2025-76759",
            "id": "pyup.io-76759",
            "more_info_path": "/vulnerabilities/PVE-2025-76759/76759",
            "specs": [
                "<3.0"
            ],
            "v": "<3.0"
        },
        {
            "advisory": "Affected versions of the project were potentially vulnerable to Insecure Deserialization. An attacker could potentially provide a malicious YAML payload leading to remote code execution. This issue is fixed in the current commit by using `yaml.safe_load()` instead of `yaml.load()`.",
            "cve": "PVE-2025-76784",
            "id": "pyup.io-76784",
            "more_info_path": "/vulnerabilities/PVE-2025-76784/76784",
            "specs": [
                "<3.0"
            ],
            "v": "<3.0"
        },
        {
            "advisory": "Affected versions of the texture classes were vulnerable to integer overflow. The issue existed in the indexing logic of texture classes. This issue is fixed in the latest commit by replacing `int` with `size_t` and `intptr_t` for safer indexing operations.",
            "cve": "PVE-2025-76785",
            "id": "pyup.io-76785",
            "more_info_path": "/vulnerabilities/PVE-2025-76785/76785",
            "specs": [
                "<3.0"
            ],
            "v": "<3.0"
        }
    ],
    "pyrage": [
        {
            "advisory": "Pyrage uses the Rust age crate for its underlying operations, and age is vulnerable to GHSA-4fg7-vxc8-qx5w.",
            "cve": "CVE-2024-56327",
            "id": "pyup.io-76379",
            "more_info_path": "/vulnerabilities/CVE-2024-56327/76379",
            "specs": [
                "<1.2.3"
            ],
            "v": "<1.2.3"
        }
    ],
    "pyramid": [
        {
            "advisory": "Pyramid 0.4.2 changes the default paster template generator to use ``Paste#http`` server rather than ``PasteScript#cherrpy`` server.  The cherrypy server has a  security risk in it when ``REMOTE_USER`` is trusted by the downstream application.",
            "cve": "PVE-2021-32184",
            "id": "pyup.io-32184",
            "more_info_path": "/vulnerabilities/PVE-2021-32184/32184",
            "specs": [
                "<0.4.2"
            ],
            "v": "<0.4.2"
        },
        {
            "advisory": "In pyramid before 1.0a3, the pylons_* paster template used the same string (``your_app_secret_string``) for the ``session.secret`` setting in the generated ``development.ini``.  This was a security risk if left unchanged in a project that used one of the templates to produce production applications.  It now uses a randomly generated string.\r\nhttps://github.com/Pylons/pyramid/commit/7bd14cbfb396bdb1e892ef0b9d51619c78ae368f",
            "cve": "PVE-2021-32685",
            "id": "pyup.io-32685",
            "more_info_path": "/vulnerabilities/PVE-2021-32685/32685",
            "specs": [
                "<1.0a3"
            ],
            "v": "<1.0a3"
        },
        {
            "advisory": "The default Mako renderer in pyramid 1.1a1 is configured to escape all HTML in expression tags. This is intended to help prevent XSS attacks caused by rendering unsanitized input from users. To revert this behavior in user's templates, they need to filter the expression through the 'n' filter. For example, ${ myhtml | n }. See .",
            "cve": "PVE-2021-32194",
            "id": "pyup.io-32194",
            "more_info_path": "/vulnerabilities/PVE-2021-32194/32194",
            "specs": [
                "<1.1a1"
            ],
            "v": "<1.1a1"
        },
        {
            "advisory": "The AuthTktAuthenticationPolicy in pyramid before 1.3a1 did not use a timing-attack-aware string comparator.  See https://github.com/Pylons/pyramid/pull/320 for more info.",
            "cve": "PVE-2021-32688",
            "id": "pyup.io-32688",
            "more_info_path": "/vulnerabilities/PVE-2021-32688/32688",
            "specs": [
                "<1.3a1"
            ],
            "v": "<1.3a1"
        },
        {
            "advisory": "In pyramid 1.4a4 the ``pyramid.authentication.AuthTktAuthenticationPolicy`` has been updated to support newer hashing algorithms such as ``sha512``. Existing applications should consider updating if possible for improved security over the default md5 hashing.",
            "cve": "PVE-2021-32201",
            "id": "pyup.io-32201",
            "more_info_path": "/vulnerabilities/PVE-2021-32201/32201",
            "specs": [
                "<1.4a4"
            ],
            "v": "<1.4a4"
        },
        {
            "advisory": "Pyramid 1.6a1 prevents timing attacks in 'AuthTktCookieHelper' and 'SignedCookieSessionFactory' classes by using the stdlib's 'hmac.compare_digest' if it is available (such as in Python 2.7.7+ and 3.3+). \r\nhttps://github.com/Pylons/pyramid/pull/1457",
            "cve": "PVE-2021-32203",
            "id": "pyup.io-32203",
            "more_info_path": "/vulnerabilities/PVE-2021-32203/32203",
            "specs": [
                "<1.6a1"
            ],
            "v": "<1.6a1"
        },
        {
            "advisory": "Pyramid 1.6a1 prevents timing attacks against CSRF tokens.\r\nhttps://github.com/Pylons/pyramid/pull/1574",
            "cve": "PVE-2022-48337",
            "id": "pyup.io-48337",
            "more_info_path": "/vulnerabilities/PVE-2022-48337/48337",
            "specs": [
                "<1.6a1"
            ],
            "v": "<1.6a1"
        },
        {
            "advisory": "pyramid before 1.6a2 isn't sanitising JSONP callbacks correctly, see CVE-2014-4671.\r\nhttps://github.com/Pylons/pyramid/commit/67efda77a878450c217b90370e1a47e2d35d772a",
            "cve": "CVE-2014-4671",
            "id": "pyup.io-32204",
            "more_info_path": "/vulnerabilities/CVE-2014-4671/32204",
            "specs": [
                "<1.6a2"
            ],
            "v": "<1.6a2"
        },
        {
            "advisory": "Pyramid 2.0.2 includes a fix for CVE-2023-40587: A path traversal vulnerability in Pyramid versions 2.0.0 and 2.0.1 impacts users of Python 3.11 that are using a Pyramid static view with a full filesystem path and have a 'index.html' file that is located exactly one directory above the location of the static view's file system path. No further path traversal exists, and the only file that could be disclosed accidentally is 'index.html'. Pyramid version 2.0.2 rejects any path that contains a null-byte out of caution. While valid in directory/file names, we would strongly consider it a mistake to use null-bytes in naming files/directories. Secondly, Python 3.11, and 3.12 has fixed the underlying issue in 'os.path.normpath' to no longer truncate on the first '0x00' found, returning the behavior to pre-3.11 Python. Fixes will be available in:Python 3.12.0rc2 and 3.11.5. Some workarounds are available. Use a version of Python 3 that is not affected, downgrade to Python 3.10 series temporarily, or wait until Python 3.11.5 is released and upgrade to the latest version of Python 3.11 series.\r\nhttps://github.com/Pylons/pyramid/security/advisories/GHSA-j8g2-6fc7-q8f8",
            "cve": "CVE-2023-40587",
            "id": "pyup.io-60688",
            "more_info_path": "/vulnerabilities/CVE-2023-40587/60688",
            "specs": [
                ">=2.0a0,<2.0.2"
            ],
            "v": ">=2.0a0,<2.0.2"
        }
    ],
    "pyramid-formencode-classic": [
        {
            "advisory": "Pyramid-formencode-classic 0.0.9 includes a fix for a CSRF vulnerability. Prior to version 0.0.9, the packages were not using CSRF tokens in the requests.\r\nhttps://github.com/jvanasco/pyramid_formencode_classic/commit/08847c80e312543c2b7408c37acb32c3d4636796",
            "cve": "PVE-2023-59985",
            "id": "pyup.io-59985",
            "more_info_path": "/vulnerabilities/PVE-2023-59985/59985",
            "specs": [
                "<0.0.9"
            ],
            "v": "<0.0.9"
        }
    ],
    "pyramid-fullauth": [
        {
            "advisory": "Pyramid-fullauth 1.0.0 updates its dependency 'SQLAlchemy' to be at least version 1.3.0 to include security fixes.",
            "cve": "CVE-2019-7548",
            "id": "pyup.io-52577",
            "more_info_path": "/vulnerabilities/CVE-2019-7548/52577",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Pyramid-fullauth 1.0.0 updates its dependency 'SQLAlchemy' to be at least version 1.3.0 to include security fixes.",
            "cve": "CVE-2019-7164",
            "id": "pyup.io-52562",
            "more_info_path": "/vulnerabilities/CVE-2019-7164/52562",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "pyramid-ldap3": [
        {
            "advisory": "Pyramid-ldap3 version 0.3.2 properly escapes the login value in the search filter in the authenticate() method: In previous versions, although the bind test in the second stage of the method ensured the proper password was passed, that was exploitable by login with a different user name like 'foo*' instead of 'foobar'.\r\nhttps://github.com/Cito/pyramid_ldap3/commit/0d58fd0e098cb32f6603ce2f2e3ae0d0497a5d2c",
            "cve": "PVE-2021-42086",
            "id": "pyup.io-42086",
            "more_info_path": "/vulnerabilities/PVE-2021-42086/42086",
            "specs": [
                "<0.3.2"
            ],
            "v": "<0.3.2"
        }
    ],
    "pyramid-odesk": [
        {
            "advisory": "pyramid-odesk before 1.1.2 performs logins and logouts through GET and is vulnerable to CSRF attacks.",
            "cve": "PVE-2021-26051",
            "id": "pyup.io-26051",
            "more_info_path": "/vulnerabilities/PVE-2021-26051/26051",
            "specs": [
                "<1.1.2"
            ],
            "v": "<1.1.2"
        }
    ],
    "pyramid-openapi3": [
        {
            "advisory": "Pyramid-openapi3 0.14 updates its NPM dependency 'Swagger UI' to v4.10.3 to include security fixes.",
            "cve": "CVE-2021-46708",
            "id": "pyup.io-48490",
            "more_info_path": "/vulnerabilities/CVE-2021-46708/48490",
            "specs": [
                "<0.14"
            ],
            "v": "<0.14"
        },
        {
            "advisory": "Pyramid-openapi3 0.14 updates its NPM dependency 'Swagger UI' to v4.10.3 to include security fixes.",
            "cve": "CVE-2019-17495",
            "id": "pyup.io-48491",
            "more_info_path": "/vulnerabilities/CVE-2019-17495/48491",
            "specs": [
                "<0.14"
            ],
            "v": "<0.14"
        },
        {
            "advisory": "Pyramid-openapi3 0.14 updates its NPM dependency 'Swagger UI' to v4.10.3 to include security fixes.",
            "cve": "CVE-2018-25031",
            "id": "pyup.io-48487",
            "more_info_path": "/vulnerabilities/CVE-2018-25031/48487",
            "specs": [
                "<0.14"
            ],
            "v": "<0.14"
        }
    ],
    "pyramid-weblayer": [
        {
            "advisory": "pyramid-weblayer before 0.12 does not protect AJAX requests through the CSRF machinery.",
            "cve": "PVE-2021-26052",
            "id": "pyup.io-26052",
            "more_info_path": "/vulnerabilities/PVE-2021-26052/26052",
            "specs": [
                "<0.12"
            ],
            "v": "<0.12"
        }
    ],
    "pyrit": [
        {
            "advisory": "Pyrit version 0.1.0 has upgraded its notebook dependency to version 7.0.7 in response to the security issue outlined in CVE-2024-22421.",
            "cve": "CVE-2024-22421",
            "id": "pyup.io-66903",
            "more_info_path": "/vulnerabilities/CVE-2024-22421/66903",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        },
        {
            "advisory": "Pyrit version 0.1.0 has upgraded its notebook dependency to version 7.0.7 in response to the security issue outlined in CVE-2024-22420.\r\nhttps://github.com/Azure/PyRIT/pull/26/commits/e9322551a6842f73e6e232b469579374d2915290",
            "cve": "CVE-2024-22420",
            "id": "pyup.io-66865",
            "more_info_path": "/vulnerabilities/CVE-2024-22420/66865",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        }
    ],
    "pyro": [
        {
            "advisory": "pyro before 3.15 unsafely handles pid files in temporary directory locations and opening the pid file as root. An attacker can use this flaw to overwrite arbitrary files via symlinks.",
            "cve": "CVE-2011-2765",
            "id": "pyup.io-36385",
            "more_info_path": "/vulnerabilities/CVE-2011-2765/36385",
            "specs": [
                "<3.15"
            ],
            "v": "<3.15"
        }
    ],
    "pyro4": [
        {
            "advisory": "Pyro4 4.44 secures HMAC comparison code against timing attacks.",
            "cve": "PVE-2021-34514",
            "id": "pyup.io-34514",
            "more_info_path": "/vulnerabilities/PVE-2021-34514/34514",
            "specs": [
                "<4.44"
            ],
            "v": "<4.44"
        },
        {
            "advisory": "Pyro4 4.46 changes REQUIRE_EXPOSE to True to avoid everything being exposed by default via Pyro.\r\nhttps://github.com/irmen/Pyro4/commit/087cbf6829aa3fb4d05011ed1261c34ca5d7aa26",
            "cve": "PVE-2021-34515",
            "id": "pyup.io-34515",
            "more_info_path": "/vulnerabilities/PVE-2021-34515/34515",
            "specs": [
                "<4.46"
            ],
            "v": "<4.46"
        },
        {
            "advisory": "Pyro4 version 4.72 deprecates the -k command line option to supply a HMAC encryption key for the name server, nsc, echoserver, flameserver and httpgateway tools (and prints a warning if used). That's because the key used is plainly visible. For proper security, use Pyro's 2-way SSL feature. Alternatively, you can set the HMAC key in the (new) environment variable PYRO_HMAC_KEY if you have to use it before launching the aforementioned tools.\r\nhttps://github.com/irmen/Pyro4/commit/a9544e05ff175201187ff1530364dd4d77ee0d3d",
            "cve": "PVE-2021-41894",
            "id": "pyup.io-41894",
            "more_info_path": "/vulnerabilities/PVE-2021-41894/41894",
            "specs": [
                "<4.72"
            ],
            "v": "<4.72"
        }
    ],
    "pyrofork": [
        {
            "advisory": "Affected versions of the pyrofork package are vulnerable to Path Traversal due to improper sanitization of attacker-controlled filenames in the download_media method. The download_media method falls back to using the Telegram-controlled media.file_name from DocumentAttributeFilename when no custom filename is provided and combines it with a base directory using os.path.split, os.path.join, and os.path.abspath without stripping dot-dot-dash sequences or absolute paths, allowing temp_file_path to resolve outside the intended download directory.",
            "cve": "CVE-2025-67720",
            "id": "pyup.io-82504",
            "more_info_path": "/vulnerabilities/CVE-2025-67720/82504",
            "specs": [
                "<2.3.69"
            ],
            "v": "<2.3.69"
        }
    ],
    "pyrologin": [
        {
            "advisory": "Pyrologin is a malicious package. It installs information-stealing and RAT (remote access trojan) Malware while using Cloudflare Tunnel to bypass firewall restrictions for remote access.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-pypi-packages-create-cloudflare-tunnels-to-bypass-firewalls",
            "cve": "PVE-2023-52934",
            "id": "pyup.io-52934",
            "more_info_path": "/vulnerabilities/PVE-2023-52934/52934",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "pyrotools": [
        {
            "advisory": "Pyrotools 1.0.1 updates its dependency 'urllib3' to v1.24.2 to include a security fix.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-37086",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/37086",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        }
    ],
    "pysam": [
        {
            "advisory": "pysam  0.11.2 wraps htslib/samtools/bcfools versions 1.4.1 in response to a security fix in these libraries",
            "cve": "PVE-2021-34332",
            "id": "pyup.io-34332",
            "more_info_path": "/vulnerabilities/PVE-2021-34332/34332",
            "specs": [
                "<0.11.2"
            ],
            "v": "<0.11.2"
        }
    ],
    "pysaml2": [
        {
            "advisory": "PySAML2 allows remote attackers to conduct XML external entity (XXE) attacks via a crafted SAML XML request or response.",
            "cve": "CVE-2016-10127",
            "id": "pyup.io-35659",
            "more_info_path": "/vulnerabilities/CVE-2016-10127/35659",
            "specs": [
                "<4.4.0"
            ],
            "v": "<4.4.0"
        },
        {
            "advisory": "XML External Entity (XXE) vulnerability in PySAML2 4.4.0 and earlier allows remote attackers to read arbitrary files via a crafted SAML XML request or response.",
            "cve": "CVE-2016-10149",
            "id": "pyup.io-35660",
            "more_info_path": "/vulnerabilities/CVE-2016-10149/35660",
            "specs": [
                "<4.4.0"
            ],
            "v": "<4.4.0"
        },
        {
            "advisory": "PySAML2 before 5.0.0 does not check that the signature in a SAML document is enveloped and thus signature wrapping is effective, i.e., it is affected by XML Signature Wrapping (XSW). The signature information and the node/object that is signed can be in different places and thus the signature verification will succeed, but the wrong data will be used. This specifically affects the verification of assertion that have been signed.",
            "cve": "CVE-2020-5390",
            "id": "pyup.io-37783",
            "more_info_path": "/vulnerabilities/CVE-2020-5390/37783",
            "specs": [
                "<5.0.0"
            ],
            "v": "<5.0.0"
        },
        {
            "advisory": "PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. Users of pysaml2 that use the default CryptoBackendXmlSec1 backend and need to verify signed SAML documents are impacted. PySAML2 does not ensure that a signed SAML document is correctly signed. The default CryptoBackendXmlSec1 backend is using the xmlsec1 binary to verify the signature of signed SAML documents, but by default xmlsec1 accepts any type of key found within the given document. xmlsec1 needs to be configured explicitly to only use only _x509 certificates_ for the verification process of the SAML document signature. This is fixed in PySAML2 6.5.0. See CVE-2021-21239.",
            "cve": "CVE-2021-21239",
            "id": "pyup.io-39498",
            "more_info_path": "/vulnerabilities/CVE-2021-21239/39498",
            "specs": [
                "<6.5.0"
            ],
            "v": "<6.5.0"
        },
        {
            "advisory": "PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0. See CVE-2021-21238.",
            "cve": "CVE-2021-21238",
            "id": "pyup.io-39497",
            "more_info_path": "/vulnerabilities/CVE-2021-21238/39497",
            "specs": [
                "<6.5.0"
            ],
            "v": "<6.5.0"
        },
        {
            "advisory": "pysaml2 version 4.4.0 and older accept any password when run with python optimizations enabled. This allows attackers to log in as any user without knowing their password.",
            "cve": "CVE-2017-1000433",
            "id": "pyup.io-35700",
            "more_info_path": "/vulnerabilities/CVE-2017-1000433/35700",
            "specs": [
                "<=4.4.0"
            ],
            "v": "<=4.4.0"
        },
        {
            "advisory": "Python package pysaml2 version 4.4.0 and earlier reuses the initialization vector across encryptions in the IDP server, resulting in weak encryption of data.",
            "cve": "CVE-2017-1000246",
            "id": "pyup.io-35699",
            "more_info_path": "/vulnerabilities/CVE-2017-1000246/35699",
            "specs": [
                "<=4.4.0"
            ],
            "v": "<=4.4.0"
        },
        {
            "advisory": "Pysaml2 below 2.1.0 leads to information exposure in specific versions.\r\nhttps://github.com/IdentityPython/pysaml2/commit/58400479eeae275f15676f1a66767c95704809cc",
            "cve": "PVE-2024-99770",
            "id": "pyup.io-66653",
            "more_info_path": "/vulnerabilities/PVE-2024-99770/66653",
            "specs": [
                ">=0,<2.1.0"
            ],
            "v": ">=0,<2.1.0"
        },
        {
            "advisory": "Pysaml2 before 2.3.0 is susceptible to an Access Restriction Bypass vulnerability. This flaw undermines security controls, potentially allowing unauthorized access to restricted resources. Users should review their system configurations and follow recommended security practices to mitigate exposure to this vulnerability.\r\nhttps://github.com/IdentityPython/pysaml2/commit/d21ac9a70bce0535a2f3cc3a621452ad9d0681d6",
            "cve": "PVE-2024-99769",
            "id": "pyup.io-66654",
            "more_info_path": "/vulnerabilities/PVE-2024-99769/66654",
            "specs": [
                ">=0,<2.3.0"
            ],
            "v": ">=0,<2.3.0"
        }
    ],
    "pysandbox": [
        {
            "advisory": "pysandbox before 1.0.2 allows access to several dict methods.",
            "cve": "PVE-2021-26053",
            "id": "pyup.io-26053",
            "more_info_path": "/vulnerabilities/PVE-2021-26053/26053",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        },
        {
            "advisory": "pysandbox before 1.0.3 allows access to dict.__init__().",
            "cve": "PVE-2021-26054",
            "id": "pyup.io-26054",
            "more_info_path": "/vulnerabilities/PVE-2021-26054/26054",
            "specs": [
                "<1.0.3"
            ],
            "v": "<1.0.3"
        },
        {
            "advisory": "pysandbox before 1.5 has several security vulnerabilities.",
            "cve": "PVE-2021-26055",
            "id": "pyup.io-26055",
            "more_info_path": "/vulnerabilities/PVE-2021-26055/26055",
            "specs": [
                "<1.5"
            ],
            "v": "<1.5"
        },
        {
            "advisory": "pysandbox before 1.6 isn't setting __builtins__ to readonly when execute() is used.",
            "cve": "PVE-2021-26056",
            "id": "pyup.io-26056",
            "more_info_path": "/vulnerabilities/PVE-2021-26056/26056",
            "specs": [
                "<1.6"
            ],
            "v": "<1.6"
        }
    ],
    "pysbd": [
        {
            "advisory": "Pysbd 0.3.0rc includes an upgrade of bleach to address a security vulnerability.",
            "cve": "PVE-2021-38404",
            "id": "pyup.io-38404",
            "more_info_path": "/vulnerabilities/PVE-2021-38404/38404",
            "specs": [
                "<0.3.0rc"
            ],
            "v": "<0.3.0rc"
        }
    ],
    "pyserini": [
        {
            "advisory": "Pyserini 0.11.0.0 and prior includes a version of Anserini affected by critical and severe vulnerabilities, related to log4j.",
            "cve": "CVE-2021-44832",
            "id": "pyup.io-44462",
            "more_info_path": "/vulnerabilities/CVE-2021-44832/44462",
            "specs": [
                "<=0.11.0.0"
            ],
            "v": "<=0.11.0.0"
        },
        {
            "advisory": "Pyserini 0.11.0.0 and prior includes a version of Anserini affected by critical and severe vulnerabilities, related to log4j.",
            "cve": "CVE-2021-45046",
            "id": "pyup.io-43607",
            "more_info_path": "/vulnerabilities/CVE-2021-45046/43607",
            "specs": [
                "<=0.11.0.0"
            ],
            "v": "<=0.11.0.0"
        },
        {
            "advisory": "Pyserini 0.11.0.0 and prior includes a version of Anserini affected by critical and severe vulnerabilities, related to log4j.",
            "cve": "CVE-2021-45105",
            "id": "pyup.io-43608",
            "more_info_path": "/vulnerabilities/CVE-2021-45105/43608",
            "specs": [
                "<=0.11.0.0"
            ],
            "v": "<=0.11.0.0"
        },
        {
            "advisory": "Pyserini 0.11.0.0 and prior includes a version of Anserini affected by critical and severe vulnerabilities, related to log4j.",
            "cve": "CVE-2021-44228",
            "id": "pyup.io-43606",
            "more_info_path": "/vulnerabilities/CVE-2021-44228/43606",
            "specs": [
                "<=0.11.0.0"
            ],
            "v": "<=0.11.0.0"
        }
    ],
    "pyshop": [
        {
            "advisory": "pyshop before 0.7.1 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which allows man-in-the-middle attackers to execute arbitrary code via a crafted response to a download operation.",
            "cve": "CVE-2013-1630",
            "id": "pyup.io-26057",
            "more_info_path": "/vulnerabilities/CVE-2013-1630/26057",
            "specs": [
                "<0.7.1"
            ],
            "v": "<0.7.1"
        }
    ],
    "pysigma": [
        {
            "advisory": "Pysigma 0.10.0 updates its dependency 'certifi' to version \"2023.7.22\" to include a security fix.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60909",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60909",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        }
    ],
    "pysigma-backend-kusto": [
        {
            "advisory": "Pysigma-backend-kusto 0.2.1 pins its dependency 'certifi' to v2023.07.22 to include a security fix.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-73105",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/73105",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "pysigma-backend-microsoft365defender": [
        {
            "advisory": "Pysigma-backend-microsoft365defender 0.2.1 pins 'certifi' version to '2023.07.22' to include a security fix.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-62167",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/62167",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "pysipfenn": [
        {
            "advisory": "Pysipfenn version 0.15.1 now mandates pymatgen version 2024.2.20, addressing a critical security flaw in pymatgen.io as per CVE-2022-42964. \r\nhttps://github.com/PhasesResearchLab/pySIPFENN/commit/89131bf789c0f8ee4ed33eaa839d34bcc2c10be5",
            "cve": "CVE-2022-42964",
            "id": "pyup.io-66009",
            "more_info_path": "/vulnerabilities/CVE-2022-42964/66009",
            "specs": [
                "<0.15.1"
            ],
            "v": "<0.15.1"
        }
    ],
    "pyslyte": [
        {
            "advisory": "Pyslyte is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51691",
            "id": "pyup.io-51691",
            "more_info_path": "/vulnerabilities/PVE-2022-51691/51691",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pysmf": [
        {
            "advisory": "The LDAP backend in OpenStack Identity (Keystone) Grizzly and Havana, when removing a role on a tenant for a user who does not have that role, adds the role to the user, which allows local users to gain privileges.",
            "cve": "CVE-2013-4477",
            "id": "pyup.io-61065",
            "more_info_path": "/vulnerabilities/CVE-2013-4477/61065",
            "specs": [
                "<=2013.2.1"
            ],
            "v": "<=2013.2.1"
        }
    ],
    "pysna": [
        {
            "advisory": "Pysna 0.1.3 updates its dependency 'certifi' to version '2023.07.22' to include a fix for a vulnerability.\r\nhttps://github.com/mathun3003/PySNA/commit/1aebdbf4806175723970187f57c09e4b1f7caf72",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60507",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60507",
            "specs": [
                "<0.1.3"
            ],
            "v": "<0.1.3"
        }
    ],
    "pysnc": [
        {
            "advisory": "Pysnc version 1.1.6 has updated its urllib3 dependency to version \"^2.0.7\" in response to security vulnerability CVE-2023-45803.",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-67143",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/67143",
            "specs": [
                "<1.1.6"
            ],
            "v": "<1.1.6"
        },
        {
            "advisory": "Pysnc version 1.1.6 upgrades its pip requirement to \"^23.3.1\" to address the security concerns outlined in CVE-2023-5752.",
            "cve": "CVE-2023-5752",
            "id": "pyup.io-66998",
            "more_info_path": "/vulnerabilities/CVE-2023-5752/66998",
            "specs": [
                "<1.1.6"
            ],
            "v": "<1.1.6"
        }
    ],
    "pysnyk": [
        {
            "advisory": "Pysnyk 0.7.0 updates its dependency 'urllib3' to v1.26.8 to include security fixes.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-45527",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/45527",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Pysnyk 0.7.0 updates its dependency 'urllib3' to v1.26.8 to include security fixes.",
            "cve": "CVE-2021-28363",
            "id": "pyup.io-45523",
            "more_info_path": "/vulnerabilities/CVE-2021-28363/45523",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        }
    ],
    "pysodium": [
        {
            "advisory": "Pysodium 0.7.17 fixes the maximum message size that was a value larger than what is considered secure which could potentially lead to a buffer overflow attack.\r\nhttps://github.com/stef/pysodium/commit/8d2c6d897b0fc6e20470d8e554679a5b693ae4e4",
            "cve": "PVE-2023-62827",
            "id": "pyup.io-62827",
            "more_info_path": "/vulnerabilities/PVE-2023-62827/62827",
            "specs": [
                "<0.7.17"
            ],
            "v": "<0.7.17"
        }
    ],
    "pyspark": [
        {
            "advisory": "Prior to Spark 2.3.3, in certain situations Spark would write user data to local disk unencrypted, even if spark.io.encryption.enabled=true. This includes cached blocks that are fetched to disk (controlled by spark.maxRemoteBlockSizeFetchToMem); in SparkR, using parallelize; in Pyspark, using broadcast and parallelize; and use of python udfs.",
            "cve": "CVE-2019-10099",
            "id": "pyup.io-37352",
            "more_info_path": "/vulnerabilities/CVE-2019-10099/37352",
            "specs": [
                "<2.3.3"
            ],
            "v": "<2.3.3"
        },
        {
            "advisory": "Affected versions of the Apache Spark package are vulnerable to Improper Input Validation due to insufficient restrictions on classpath configurations. The vulnerability exists because applications can specify arbitrary configuration-related classes on the classpath, circumventing the intended privilege limitations imposed by the 'proxy-user' setting. An attacker can exploit this by submitting a malicious application that includes custom classpath entries, allowing execution of code with the privileges of the submitting user rather than the restricted proxy-user, potentially compromising system security.",
            "cve": "CVE-2023-22946",
            "id": "pyup.io-62892",
            "more_info_path": "/vulnerabilities/CVE-2023-22946/62892",
            "specs": [
                "<3.3.3"
            ],
            "v": "<3.3.3"
        },
        {
            "advisory": "** UNSUPPORTED WHEN ASSIGNED ** The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is currently running as. This issue was disclosed earlier as CVE-2022-33891, but incorrectly claimed version 3.1.3 (which has since gone EOL) would not be affected. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. Users are recommended to upgrade to a supported version of Apache Spark, such as version 3.4.0.",
            "cve": "CVE-2023-32007",
            "id": "pyup.io-64192",
            "more_info_path": "/vulnerabilities/CVE-2023-32007/64192",
            "specs": [
                "<=3.0.3",
                ">=3.1.1,<=3.1.3",
                ">=3.2.0,<=3.2.1"
            ],
            "v": "<=3.0.3,>=3.1.1,<=3.1.3,>=3.2.0,<=3.2.1"
        },
        {
            "advisory": "In Apache Spark 2.1.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, it's possible for a malicious user to construct a URL pointing to a Spark cluster's UI's job and stage info pages, and if a user can be tricked into accessing the URL, can be used to cause script to execute and expose information from the user's view of the Spark UI. While some browsers like recent versions of Chrome and Safari are able to block this type of attack, current versions of Firefox (and possibly others) do not.",
            "cve": "CVE-2018-8024",
            "id": "pyup.io-65849",
            "more_info_path": "/vulnerabilities/CVE-2018-8024/65849",
            "specs": [
                "==2.3.0",
                ">=2.1.0,<2.1.3",
                ">=2.2.0,<2.2.2"
            ],
            "v": "==2.3.0,>=2.1.0,<2.1.3,>=2.2.0,<2.2.2"
        },
        {
            "advisory": "In Apache Spark before 2.2.0, it is possible for an attacker to take advantage of a user's trust in the server to trick them into visiting a link that points to a shared Spark cluster and submits data including MHTML to the Spark master, or history server. This data, which could contain a script, would then be reflected back to the user and could be evaluated and executed by MS Windows-based clients. It is not an attack on Spark itself, but on the user, who may then execute the script inadvertently when viewing elements of the Spark web UIs.",
            "cve": "CVE-2017-7678",
            "id": "pyup.io-65848",
            "more_info_path": "/vulnerabilities/CVE-2017-7678/65848",
            "specs": [
                ">=0,<2.2.0"
            ],
            "v": ">=0,<2.2.0"
        },
        {
            "advisory": "In Apache Spark 2.4.5 and earlier, a standalone resource manager's master may be configured to require authentication (spark.authenticate) via a shared secret. When enabled, however, a specially-crafted RPC to the master can succeed in starting an application's resources on the Spark cluster, even without the shared key. This can be leveraged to execute shell commands on the host machine. This does not affect Spark clusters using other resource managers (YARN, Mesos, etc).",
            "cve": "CVE-2020-9480",
            "id": "pyup.io-54302",
            "more_info_path": "/vulnerabilities/CVE-2020-9480/54302",
            "specs": [
                ">=0,<2.4.6"
            ],
            "v": ">=0,<2.4.6"
        },
        {
            "advisory": "Apache Spark supports end-to-end encryption of RPC connections via \"spark.authenticate\" and \"spark.network.crypto.enabled\". In versions 3.1.2 and earlier, it uses a bespoke mutual authentication protocol that allows for full encryption key recovery. After an initial interactive attack, this would allow someone to decrypt plaintext traffic offline. Note that this does not affect security mechanisms controlled by \"spark.authenticate.enableSaslEncryption\", \"spark.io.encryption.enabled\", \"spark.ssl\", \"spark.ui.strictTransportSecurity\". Update to Apache Spark 3.1.3 or later",
            "cve": "CVE-2021-38296",
            "id": "pyup.io-54370",
            "more_info_path": "/vulnerabilities/CVE-2021-38296/54370",
            "specs": [
                ">=0,<3.1.3"
            ],
            "v": ">=0,<3.1.3"
        },
        {
            "advisory": "Pyspark before 3.1.3, equal or above 3.2.0 and below 3.2.2 are vulnerable to arbitrary command execution. This vulnerability stems from a flaw in the Utils.unpack method, where a filename controlled by a malicious user is not properly escaped by Hadoop's unTar function before it is passed to a shell command.\r\nhttps://github.com/apache/spark/pull/35946/commits/7b16ba4ab792f6e63f4f1ad0ec5bba245a01a721",
            "cve": "PVE-2024-99771",
            "id": "pyup.io-66652",
            "more_info_path": "/vulnerabilities/PVE-2024-99771/66652",
            "specs": [
                ">=0,<3.1.3",
                ">=3.2.0,<3.2.2"
            ],
            "v": ">=0,<3.1.3,>=3.2.0,<3.2.2"
        },
        {
            "advisory": "A stored cross-site scripting (XSS) vulnerability in Apache Spark 3.2.1 and earlier, and 3.3.0, allows remote attackers to execute arbitrary JavaScript in the web browser of a user, by including a malicious payload into the logs which would be returned in logs rendered in the UI.",
            "cve": "CVE-2022-31777",
            "id": "pyup.io-54576",
            "more_info_path": "/vulnerabilities/CVE-2022-31777/54576",
            "specs": [
                ">=0,<3.2.2"
            ],
            "v": ">=0,<3.2.2"
        },
        {
            "advisory": "In Apache Spark 1.6.0 until 2.1.1, the launcher API performs unsafe deserialization of data received by its socket. This makes applications launched programmatically using the launcher API potentially vulnerable to arbitrary code execution by an attacker with access to any user account on the local machine. It does not affect apps run by spark-submit or spark-shell. The attacker would be able to execute code as the user that ran the Spark application. Users are encouraged to update to version 2.2.0 or later.",
            "cve": "CVE-2017-12612",
            "id": "pyup.io-65847",
            "more_info_path": "/vulnerabilities/CVE-2017-12612/65847",
            "specs": [
                ">=1.6.0,<2.1.2"
            ],
            "v": ">=1.6.0,<2.1.2"
        },
        {
            "advisory": "In Apache Spark 1.0.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, when using PySpark or SparkR, it's possible for a different local user to connect to the Spark application and impersonate the user running the Spark application.",
            "cve": "CVE-2018-1334",
            "id": "pyup.io-54001",
            "more_info_path": "/vulnerabilities/CVE-2018-1334/54001",
            "specs": [
                ">=2.2.0,<2.2.2",
                ">=0,<2.1.3"
            ],
            "v": ">=2.2.0,<2.2.2,>=0,<2.1.3"
        },
        {
            "advisory": "When using PySpark , it's possible for a different local user to connect to the Spark application and impersonate the user running the Spark application. This affects versions 1.x, 2.0.x, 2.1.x, 2.2.0 to 2.2.2, and 2.3.0 to 2.3.1.",
            "cve": "CVE-2018-11760",
            "id": "pyup.io-53997",
            "more_info_path": "/vulnerabilities/CVE-2018-11760/53997",
            "specs": [
                ">=2.3.0,<2.3.2",
                ">=1.0.2,<2.2.3"
            ],
            "v": ">=2.3.0,<2.3.2,>=1.0.2,<2.2.3"
        }
    ],
    "pyspeedinsights": [
        {
            "advisory": "Pyspeedinsights 0.3.2 updates its dependency 'requests' to version '2.31.0' to include a security fix.\r\nhttps://github.com/wjh18/pyspeedinsights/commit/3fe8d3b68097b5b83630d1e844b06d10931954c1",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-59304",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/59304",
            "specs": [
                "<0.3.2"
            ],
            "v": "<0.3.2"
        }
    ],
    "pyspf": [
        {
            "advisory": "Pyspf 2.0.1 prevents cache poisoning attacks and malformed RR attacks.\r\nhttps://github.com/sdgathman/pyspf/commit/5f5d4b081c41963e84083590faa41fa0f90877fa",
            "cve": "PVE-2021-37431",
            "id": "pyup.io-37431",
            "more_info_path": "/vulnerabilities/PVE-2021-37431/37431",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        }
    ],
    "pyspi": [
        {
            "advisory": "Pyspi version 0.4.1 updates its Torch dependency from version 1.10.0 to 1.13.1 to address the security vulnerability identified as CVE-2022-45907.\r\nhttps://github.com/DynamicsAndNeuralSystems/pyspi/commit/3b14ea11f4c43f2775beb8c701aaf827c230401d",
            "cve": "CVE-2022-45907",
            "id": "pyup.io-66029",
            "more_info_path": "/vulnerabilities/CVE-2022-45907/66029",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        },
        {
            "advisory": "Pyspi version 0.4.2 updates its Scikit-learn dependency to version 1.0.1 from 0.24.1 in response to security concerns highlighted by CVE-2020-28975.",
            "cve": "CVE-2020-28975",
            "id": "pyup.io-66028",
            "more_info_path": "/vulnerabilities/CVE-2020-28975/66028",
            "specs": [
                "<0.4.2"
            ],
            "v": "<0.4.2"
        }
    ],
    "pyspider": [
        {
            "advisory": "Binux pyspider up to v0.3.10 was discovered to contain a Cross-Site Request Forgery (CSRF) via the Flask endpoints.",
            "cve": "CVE-2024-39163",
            "id": "pyup.io-76391",
            "more_info_path": "/vulnerabilities/CVE-2024-39163/76391",
            "specs": [
                "<0.3.10"
            ],
            "v": "<0.3.10"
        },
        {
            "advisory": "Affected versions of Pyspider are vulnerable to Reflected Cross-Site Scripting (XSS) and Cross-Site Request Forgery (CSRF). These issues allow attackers to execute arbitrary code on the host by exploiting unsanitized input in the /update endpoint and leveraging Basic HTTP Authentication without CSRF protection. An attacker can manipulate authenticated users into visiting a malicious site, leading to code execution. To mitigate, disable the WebUI or implement proper input sanitization and CSRF tokens",
            "cve": "CVE-2024-39162",
            "id": "pyup.io-74431",
            "more_info_path": "/vulnerabilities/CVE-2024-39162/74431",
            "specs": [
                "<=0.3.10"
            ],
            "v": "<=0.3.10"
        }
    ],
    "pyspur": [
        {
            "advisory": "Affected versions of this package are vulnerable to Template Injection due to improper neutralization of special elements in template engines. The SingleLLMCallNode function in the Jinja2 Template Handler fails to properly sanitize the user_message parameter before processing it through the template engine, leading to potential remote code execution through template injection attacks.",
            "cve": "CVE-2025-6518",
            "id": "pyup.io-77903",
            "more_info_path": "/vulnerabilities/CVE-2025-6518/77903",
            "specs": [
                "<=0.1.18"
            ],
            "v": "<=0.1.18"
        }
    ],
    "pysstv": [
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2020-10994",
            "id": "pyup.io-43567",
            "more_info_path": "/vulnerabilities/CVE-2020-10994/43567",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-43559",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/43559",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2020-15999",
            "id": "pyup.io-43565",
            "more_info_path": "/vulnerabilities/CVE-2020-15999/43565",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2020-11538",
            "id": "pyup.io-43566",
            "more_info_path": "/vulnerabilities/CVE-2020-11538/43566",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-43555",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/43555",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-43558",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/43558",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-43563",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/43563",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-43561",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/43561",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-43556",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/43556",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-40228",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/40228",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-43557",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/43557",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-43560",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/43560",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-43562",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/43562",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv 0.5 updates its dependency 'pillow' from 4.3.0 to 8.1.1 to include security fixes.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-43564",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/43564",
            "specs": [
                "<0.5"
            ],
            "v": "<0.5"
        },
        {
            "advisory": "Pysstv version 0.5.2 updates its dependency \"Pillow\" to include a fix for CVE-2021-28677.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-41958",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/41958",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        },
        {
            "advisory": "Pysstv version 0.5.2 updates its dependency \"Pillow\" to 8.2.0 to include a fix for CVE-2021-28676.\r\nhttps://github.com/dnet/pySSTV/pull/25/commits/681147969fdde490f45aa81dab972107e003dce7",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-41957",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/41957",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        },
        {
            "advisory": "Pysstv version 0.5.2 updates its dependency \"Pillow\" to include a fix for CVE-2021-28675.",
            "cve": "CVE-2021-28675",
            "id": "pyup.io-41956",
            "more_info_path": "/vulnerabilities/CVE-2021-28675/41956",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        },
        {
            "advisory": "Pysstv version 0.5.2 updates its dependency \"Pillow\" to include a fix for CVE-2021-28678.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-41845",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/41845",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        },
        {
            "advisory": "Pysstv 0.5.3 updates its dependency 'Pillow' to v8.3.2 to include security fixes.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-44528",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/44528",
            "specs": [
                "<0.5.3"
            ],
            "v": "<0.5.3"
        },
        {
            "advisory": "Pysstv 0.5.3 updates its dependency 'Pillow' to v8.3.2 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-44520",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/44520",
            "specs": [
                "<0.5.3"
            ],
            "v": "<0.5.3"
        },
        {
            "advisory": "Pysstv 0.5.4 updates its dependency 'Pillow' to v9.0.0 to include security fixes.",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-44533",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/44533",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pysstv 0.5.4 updates its dependency 'Pillow' to v9.0.0 to include security fixes.",
            "cve": "CVE-2022-22817",
            "id": "pyup.io-44531",
            "more_info_path": "/vulnerabilities/CVE-2022-22817/44531",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pysstv 0.5.4 updates its dependency 'Pillow' to v9.0.0 to include security fixes.",
            "cve": "PVE-2021-44525",
            "id": "pyup.io-44530",
            "more_info_path": "/vulnerabilities/PVE-2021-44525/44530",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pysstv 0.5.4 updates its dependency 'Pillow' to v9.0.0 to include security fixes.",
            "cve": "PVE-2022-44524",
            "id": "pyup.io-44519",
            "more_info_path": "/vulnerabilities/PVE-2022-44524/44519",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pysstv 0.5.4 updates its dependency 'Pillow' to v9.0.0 to include security fixes.",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-44532",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/44532",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Pysstv 0.5.5 updates its dependency 'pillow' to v10.0.1 to include security fixes.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62186",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62186",
            "specs": [
                "<0.5.5"
            ],
            "v": "<0.5.5"
        },
        {
            "advisory": "Pysstv 0.5.5 updates its dependency 'pillow' to v10.0.1 to include security fixes.",
            "cve": "CVE-2023-44271",
            "id": "pyup.io-62204",
            "more_info_path": "/vulnerabilities/CVE-2023-44271/62204",
            "specs": [
                "<0.5.5"
            ],
            "v": "<0.5.5"
        }
    ],
    "pystache": [
        {
            "advisory": "Pystache 0.5.4-2 fixes insecure HTTP urls.\r\nhttps://github.com/sarnold/pystache/commit/5b482af8122f529859d0d0cfbb6b2d345458e166",
            "cve": "PVE-2021-43093",
            "id": "pyup.io-43093",
            "more_info_path": "/vulnerabilities/PVE-2021-43093/43093",
            "specs": [
                "<0.5.4-2"
            ],
            "v": "<0.5.4-2"
        }
    ],
    "pysteps": [
        {
            "advisory": "Pysteps 1.6.0 drops support for Python 3.6 as it arrived to end-of-life and don't receive security updates anymore.",
            "cve": "CVE-2020-10735",
            "id": "pyup.io-45285",
            "more_info_path": "/vulnerabilities/CVE-2020-10735/45285",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        }
    ],
    "pyston": [
        {
            "advisory": "Pyston 2.3.1 includes a fix coming from Python 3.8.12 release: multiple CRLF injection vulnerabilities in smtplib.",
            "cve": "PVE-2021-42379",
            "id": "pyup.io-51244",
            "more_info_path": "/vulnerabilities/PVE-2021-42379/51244",
            "specs": [
                "<2.3.1"
            ],
            "v": "<2.3.1"
        },
        {
            "advisory": "Pyston 2.3.1 includes a fix coming from Python 3.8.12 release: IP addresses access control bypass.",
            "cve": "CVE-2021-29921",
            "id": "pyup.io-51325",
            "more_info_path": "/vulnerabilities/CVE-2021-29921/51325",
            "specs": [
                "<2.3.1"
            ],
            "v": "<2.3.1"
        }
    ],
    "pystyle": [
        {
            "advisory": "Pystyle is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51692",
            "id": "pyup.io-51692",
            "more_info_path": "/vulnerabilities/PVE-2022-51692/51692",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pystyte": [
        {
            "advisory": "Pystyte is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51690",
            "id": "pyup.io-51690",
            "more_info_path": "/vulnerabilities/PVE-2022-51690/51690",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pysys-java": [
        {
            "advisory": "Pysys-java 0.1 and prior includes a version of 'log4j-core' affected by critical and severe vulnerabilities.\r\nhttps://github.com/ben-spiller/pysysjava/pull/14",
            "cve": "CVE-2021-45046",
            "id": "pyup.io-43601",
            "more_info_path": "/vulnerabilities/CVE-2021-45046/43601",
            "specs": [
                "<=0.1"
            ],
            "v": "<=0.1"
        },
        {
            "advisory": "Pysys-java 0.1 and prior includes a version of 'log4j-core' affected by critical and severe vulnerabilities.\r\nhttps://github.com/ben-spiller/pysysjava/pull/14",
            "cve": "CVE-2021-45105",
            "id": "pyup.io-43602",
            "more_info_path": "/vulnerabilities/CVE-2021-45105/43602",
            "specs": [
                "<=0.1"
            ],
            "v": "<=0.1"
        },
        {
            "advisory": "Pysys-java 0.1 and prior includes a version of 'log4j-core' affected by critical and severe vulnerabilities.\r\nhttps://github.com/ben-spiller/pysysjava/pull/14",
            "cve": "CVE-2021-44832",
            "id": "pyup.io-44461",
            "more_info_path": "/vulnerabilities/CVE-2021-44832/44461",
            "specs": [
                "<=0.1"
            ],
            "v": "<=0.1"
        },
        {
            "advisory": "Pysys-java 0.1 and prior includes a version of 'log4j-core' affected by critical and severe vulnerabilities.\r\nhttps://github.com/ben-spiller/pysysjava/pull/14",
            "cve": "CVE-2021-44228",
            "id": "pyup.io-43600",
            "more_info_path": "/vulnerabilities/CVE-2021-44228/43600",
            "specs": [
                "<=0.1"
            ],
            "v": "<=0.1"
        }
    ],
    "pytablewriter": [
        {
            "advisory": "Pytablewriter 0.47.0 prevents xslx formula injection.\r\nhttps://github.com/thombashi/pytablewriter/issues/20",
            "cve": "PVE-2021-41000",
            "id": "pyup.io-41000",
            "more_info_path": "/vulnerabilities/PVE-2021-41000/41000",
            "specs": [
                "<0.47.0"
            ],
            "v": "<0.47.0"
        }
    ],
    "pytagora": [
        {
            "advisory": "Pytagora is a malicious package, typosquatting. \"The aforementioned package could be abused to become an entry point for more sophisticated threats, enabling the attacker to execute remote code on the target machine, amass system information, plunder credit card information and passwords auto-saved in Chrome and Edge browsers, and even steal Discord authentication tokens to impersonate the victim\".\r\nhttps://thehackernews.com/2021/07/several-malicious-typosquatted-python.html",
            "cve": "PVE-2022-45446",
            "id": "pyup.io-45446",
            "more_info_path": "/vulnerabilities/PVE-2022-45446/45446",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "pytagora2": [
        {
            "advisory": "Pytagora2 is a malicious package, typosquatting. \"The aforementioned package could be abused to become an entry point for more sophisticated threats, enabling the attacker to execute remote code on the target machine, amass system information, plunder credit card information and passwords auto-saved in Chrome and Edge browsers, and even steal Discord authentication tokens to impersonate the victim\".\r\nhttps://thehackernews.com/2021/07/several-malicious-typosquatted-python.html",
            "cve": "PVE-2022-45447",
            "id": "pyup.io-45447",
            "more_info_path": "/vulnerabilities/PVE-2022-45447/45447",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "pytask-latex": [
        {
            "advisory": "Pytask-latex 0.0.7 ensures that 'outputdirectory' is relative to the latex document to address security problems.\r\nhttps://github.com/pytask-dev/pytask-latex/commit/634d70d0807c118cba2b2119122591c7988a1469",
            "cve": "PVE-2021-39658",
            "id": "pyup.io-39658",
            "more_info_path": "/vulnerabilities/PVE-2021-39658/39658",
            "specs": [
                "<0.0.7"
            ],
            "v": "<0.0.7"
        }
    ],
    "pytest-aoc": [
        {
            "advisory": "pytest-aoc 1.2a6 removes security misfeature: no cookies inside setup.cfg.",
            "cve": "PVE-2021-37267",
            "id": "pyup.io-37267",
            "more_info_path": "/vulnerabilities/PVE-2021-37267/37267",
            "specs": [
                "<1.2a6"
            ],
            "v": "<1.2a6"
        }
    ],
    "pytest-celery": [
        {
            "advisory": "Pytest-celery updated the `idna` dependency from version 3.6 to 3.7 to address the CVE-2024-3651 vulnerability.",
            "cve": "CVE-2024-3651",
            "id": "pyup.io-72234",
            "more_info_path": "/vulnerabilities/CVE-2024-3651/72234",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        }
    ],
    "pytest-cov": [
        {
            "advisory": "Pytest-cov 2.0.0 resolves a race condition issue experienced when utilizing xdist, where multiple workers attempted to combine files simultaneously, leading to potential conflicts. This update ensures coverage data isn't combined by the workers, mitigating the risk of race conditions due to the non-atomic nature of the combining process.",
            "cve": "PVE-2024-66922",
            "id": "pyup.io-66922",
            "more_info_path": "/vulnerabilities/PVE-2024-66922/66922",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        }
    ],
    "pytest-devpi-server": [
        {
            "advisory": "Pytest-devpi-server 1.1.0 changes default behavior of workspace.run() to not use a subshell for security reasons.\r\nhttps://github.com/man-group/pytest-plugins/commit/ea6072a461edde63c07f7b7f4a4daffdc09fb116",
            "cve": "PVE-2021-26059",
            "id": "pyup.io-26059",
            "more_info_path": "/vulnerabilities/PVE-2021-26059/26059",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pytest-git": [
        {
            "advisory": "Pytest-git 1.1.0 changes default behavior of workspace.run() to not use a subshell for security reasons.\r\nhttps://github.com/man-group/pytest-plugins/commit/ea6072a461edde63c07f7b7f4a4daffdc09fb116",
            "cve": "PVE-2021-26060",
            "id": "pyup.io-26060",
            "more_info_path": "/vulnerabilities/PVE-2021-26060/26060",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pytest-httpserver": [
        {
            "advisory": "Pytest-httpserver 1.0.2 drops support for Python 3.4 and 3.5. These versions arrived to EOL and don't receive security fixes anymore.",
            "cve": "CVE-2021-3737",
            "id": "pyup.io-43450",
            "more_info_path": "/vulnerabilities/CVE-2021-3737/43450",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        },
        {
            "advisory": "Pytest-httpserver 1.0.2 drops support for Python 3.4 and 3.5. These versions arrived to EOL and don't receive security fixes anymore.",
            "cve": "CVE-2021-3177",
            "id": "pyup.io-43452",
            "more_info_path": "/vulnerabilities/CVE-2021-3177/43452",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        },
        {
            "advisory": "Pytest-httpserver 1.0.2 drops support for Python 3.4 and 3.5. These versions arrived to EOL and don't receive security fixes anymore.",
            "cve": "CVE-2020-27619",
            "id": "pyup.io-43407",
            "more_info_path": "/vulnerabilities/CVE-2020-27619/43407",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        },
        {
            "advisory": "Pytest-httpserver 1.0.2 drops support for Python 3.4 and 3.5. These versions arrived to EOL and don't receive security fixes anymore.",
            "cve": "CVE-2019-20907",
            "id": "pyup.io-43451",
            "more_info_path": "/vulnerabilities/CVE-2019-20907/43451",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "pytest-profiling": [
        {
            "advisory": "pytest-profiling before 1.1.0  uses a subshell in workspace.run.",
            "cve": "PVE-2021-26061",
            "id": "pyup.io-26061",
            "more_info_path": "/vulnerabilities/PVE-2021-26061/26061",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pytest-qt-app": [
        {
            "advisory": "Pytest-qt-app 1.1.0  fixes a code injection vulnerability by using 'shell=False' in default workspace.\r\nhttps://github.com/man-group/pytest-plugins/commit/ea6072a461edde63c07f7b7f4a4daffdc09fb116",
            "cve": "PVE-2021-26062",
            "id": "pyup.io-26062",
            "more_info_path": "/vulnerabilities/PVE-2021-26062/26062",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pytest-runner": [
        {
            "advisory": "Pytest-runner depends on deprecated features of setuptools and relies on features that break security mechanisms in pip. For example \u2018setup_requires\u2019 and \u2018tests_require\u2019 bypass pip --require-hashes. See also pypa/setuptools#1684.\r\nIt is recommended that you:\r\n- Remove 'pytest-runner' from your setup_requires, preferably removing the setup_requires option.\r\n- Remove 'pytest' and any other testing requirements from tests_require, preferably removing the tests_requires option.\r\n- Select a tool to bootstrap and then run tests such as tox.\r\nhttps://github.com/pytest-dev/pytest-runner/blob/289a77b179535d8137118e3b8591d9e727130d6d/README.rst",
            "cve": "PVE-2021-43313",
            "id": "pyup.io-43313",
            "more_info_path": "/vulnerabilities/PVE-2021-43313/43313",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pytest-server-fixtures": [
        {
            "advisory": "Pytest-server-fixtures 1.1.0 changes default behavior of workspace.run() to not use a subshell for security reasons.\r\nhttps://github.com/man-group/pytest-plugins/commit/ea6072a461edde63c07f7b7f4a4daffdc09fb116",
            "cve": "PVE-2021-26063",
            "id": "pyup.io-26063",
            "more_info_path": "/vulnerabilities/PVE-2021-26063/26063",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pytest-shutil": [
        {
            "advisory": "pytest-shutil before 1.1.0  uses a subshell in workspace.run.",
            "cve": "PVE-2021-26064",
            "id": "pyup.io-26064",
            "more_info_path": "/vulnerabilities/PVE-2021-26064/26064",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pytest-socket": [
        {
            "advisory": "Pytest-socket 0.7.0 updates its dependency on the Starlette library from version \"^0.26.1\" to \"^0.27.0\". This change addresses the security vulnerability CVE-2023-29159.\r\nhttps://github.com/miketheman/pytest-socket/pull/219/commits/8d8bd41e56895a9114bce2ea93fb5b6fa6d2e123",
            "cve": "CVE-2023-29159",
            "id": "pyup.io-64593",
            "more_info_path": "/vulnerabilities/CVE-2023-29159/64593",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        }
    ],
    "pytest-verbose-parametrize": [
        {
            "advisory": "pytest-verbose-parametrize before 1.1.0 uses a subshell in workspace.run.",
            "cve": "PVE-2021-26065",
            "id": "pyup.io-26065",
            "more_info_path": "/vulnerabilities/PVE-2021-26065/26065",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "pytest-xdist": [
        {
            "advisory": "Pytest-xdist 1.2 includes a fix for a potential race condition vulnerability when simultanous pickling/unpickling.\r\nhttps://github.com/pytest-dev/pytest-xdist/commit/45f7787fe28c36d7699e69a62b0c6ba42fcf1d20",
            "cve": "PVE-2023-62251",
            "id": "pyup.io-62251",
            "more_info_path": "/vulnerabilities/PVE-2023-62251/62251",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytest-xdist 1.6 includes a fix for a potential race condition vulnerability in looponfail mode where a concurrent file removal could cause a crash.",
            "cve": "PVE-2023-62250",
            "id": "pyup.io-62250",
            "more_info_path": "/vulnerabilities/PVE-2023-62250/62250",
            "specs": [
                "<1.6"
            ],
            "v": "<1.6"
        }
    ],
    "pytest-yamltree": [
        {
            "advisory": "Pytest-Yamltree 0.1.2 includes a security patch for the function 'init' in 'pytest_yamltree.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/MarSoft/pytest-yamltree/commit/d94031f134ab5803958aa8f33f965a30a241cf4b",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41376",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41376",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "python": [
        {
            "advisory": "A vulnerability classified as problematic was found in Python 2.7.13. This vulnerability affects unknown code of the component pgAdmin4. The manipulation leads to uncontrolled search path. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.",
            "cve": "CVE-2017-20052",
            "id": "pyup.io-49455",
            "more_info_path": "/vulnerabilities/CVE-2017-20052/49455",
            "specs": [
                "<2.17.14"
            ],
            "v": "<2.17.14"
        },
        {
            "advisory": "In libexpat before 2.2.8, crafted XML input could fool the parser into changing from DTD parsing to document parsing too early; a consecutive call to XML_GetCurrentLineNumber (or XML_GetCurrentColumnNumber) then resulted in a heap-based buffer over-read.",
            "cve": "CVE-2019-15903",
            "id": "pyup.io-70596",
            "more_info_path": "/vulnerabilities/CVE-2019-15903/70596",
            "specs": [
                "<2.2.8"
            ],
            "v": "<2.2.8"
        },
        {
            "advisory": "Python versions 2.4.6 and 2.5.2 include a fix for CVE-2008-5031: Multiple integer overflows in Python 2.2.3 through 2.5.1, and 2.6, allow context-dependent attackers to have an unknown impact via a large integer value in the tabsize argument to the expandtabs method, as implemented by (1) the string_expandtabs function in Objects/stringobject.c and (2) the unicode_expandtabs function in Objects/unicodeobject.c.  NOTE: this vulnerability reportedly exists because of an incomplete fix for CVE-2008-2315.\r\nhttps://bugs.python.org/issue4469",
            "cve": "CVE-2008-5031",
            "id": "pyup.io-45659",
            "more_info_path": "/vulnerabilities/CVE-2008-5031/45659",
            "specs": [
                "<2.4.6",
                ">=2.5.0a0,<2.5.2"
            ],
            "v": "<2.4.6,>=2.5.0a0,<2.5.2"
        },
        {
            "advisory": "Integer signedness error in the zlib extension module in Python 2.5.2 and earlier allows remote attackers to execute arbitrary code via a negative signed integer, which triggers insufficient memory allocation and a buffer overflow.",
            "cve": "CVE-2008-1721",
            "id": "pyup.io-45618",
            "more_info_path": "/vulnerabilities/CVE-2008-1721/45618",
            "specs": [
                "<2.5.2"
            ],
            "v": "<2.5.2"
        },
        {
            "advisory": "Python 2.5.2 and earlier allows context-dependent attackers to execute arbitrary code via multiple vectors that cause a negative size value to be provided to the PyString_FromStringAndSize function, which allocates less memory than expected when assert() is disabled and triggers a buffer overflow.",
            "cve": "CVE-2008-1887",
            "id": "pyup.io-45643",
            "more_info_path": "/vulnerabilities/CVE-2008-1887/45643",
            "specs": [
                "<2.5.2"
            ],
            "v": "<2.5.2"
        },
        {
            "advisory": "Multiple integer overflows in imageop.c in Python before 2.5.3 allow context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via crafted images that trigger heap-based buffer overflows.  NOTE: this issue is due to an incomplete fix for CVE-2007-4965.",
            "cve": "CVE-2008-1679",
            "id": "pyup.io-45625",
            "more_info_path": "/vulnerabilities/CVE-2008-1679/45625",
            "specs": [
                "<2.5.3"
            ],
            "v": "<2.5.3"
        },
        {
            "advisory": "Python versions 2.5.5, 2.6.4 and 3.1 include a fix for CVE-2011-1015: The is_cgi method in CGIHTTPServer.py in the CGIHTTPServer module in Python 2.5, 2.6, and 3.0 allows remote attackers to read script source code via an HTTP GET request that lacks a / (slash) character at the beginning of the URI.\r\nhttps://bugs.python.org/issue2254",
            "cve": "CVE-2011-1015",
            "id": "pyup.io-45660",
            "more_info_path": "/vulnerabilities/CVE-2011-1015/45660",
            "specs": [
                "<2.5.5",
                ">=2.6.0a0,<2.6.4",
                ">=3.0.0a0,<3.1"
            ],
            "v": "<2.5.5,>=2.6.0a0,<2.6.4,>=3.0.0a0,<3.1"
        },
        {
            "advisory": "Multiple buffer overflows in the RLE decoder in the rgbimg module in Python 2.5 allow remote attackers to have an unspecified impact via an image file containing crafted data that triggers improper processing within the (1) longimagedata or (2) expandrow function. See CVE-2010-1450.",
            "cve": "CVE-2010-1450",
            "id": "pyup.io-45624",
            "more_info_path": "/vulnerabilities/CVE-2010-1450/45624",
            "specs": [
                "<2.6"
            ],
            "v": "<2.6"
        },
        {
            "advisory": "Integer overflow in rgbimgmodule.c in the rgbimg module in Python 2.5 allows remote attackers to have an unspecified impact via a large image that triggers a buffer overflow. NOTE: this vulnerability exists because of an incomplete fix for CVE-2008-3143.12.",
            "cve": "CVE-2010-1449",
            "id": "pyup.io-45616",
            "more_info_path": "/vulnerabilities/CVE-2010-1449/45616",
            "specs": [
                "<2.6"
            ],
            "v": "<2.6"
        },
        {
            "advisory": "Buffer underflow in the rgbimg module in Python 2.5 allows remote attackers to cause a denial of service (application crash) via a large ZSIZE value in a black-and-white (aka B/W) RGB image that triggers an invalid pointer dereference. See CVE-2009-4134.",
            "cve": "CVE-2009-4134",
            "id": "pyup.io-45605",
            "more_info_path": "/vulnerabilities/CVE-2009-4134/45605",
            "specs": [
                "<2.6"
            ],
            "v": "<2.6"
        },
        {
            "advisory": "Buffer overflow in the repr function in Python 2.3 through 2.6 before 20060822 allows context-dependent attackers to cause a denial of service and possibly execute arbitrary code via crafted wide character UTF-32/UCS-4 strings to certain scripts.",
            "cve": "CVE-2006-4980",
            "id": "pyup.io-54917",
            "more_info_path": "/vulnerabilities/CVE-2006-4980/54917",
            "specs": [
                "<2.6.6"
            ],
            "v": "<2.6.6"
        },
        {
            "advisory": "Python versions 2.6.6, 2.7.0, 3.1.3 and 3.2.0 include a fix for CVE-2010-1634: Multiple integer overflows in audioop.c in the audioop module in Python 2.6, 2.7, 3.1, and 3.2 allow context-dependent attackers to cause a denial of service (application crash) via a large fragment, as demonstrated by a call to audioop.lin2lin with a long string in the first argument, leading to a buffer overflow.  NOTE: this vulnerability exists because of an incorrect fix for CVE-2008-3143.\r\nhttps://bugs.python.org/issue8674",
            "cve": "CVE-2010-1634",
            "id": "pyup.io-45661",
            "more_info_path": "/vulnerabilities/CVE-2010-1634/45661",
            "specs": [
                "<2.6.6",
                ">=2.7.0a0,<2.7.0",
                ">=3.0.0a0,<3.1.3",
                ">=3.2.0a0,<3.2.0"
            ],
            "v": "<2.6.6,>=2.7.0a0,<2.7.0,>=3.0.0a0,<3.1.3,>=3.2.0a0,<3.2.0"
        },
        {
            "advisory": "Python versions 2.6.6, 2.7.0, 3.1.3 and 3.2.0 include a fix for CVE-2010-1634: The audioop module in Python 2.7 and 3.2 does not verify the relationships between size arguments and byte string lengths, which allows context-dependent attackers to cause a denial of service (memory corruption and application crash) via crafted arguments, as demonstrated by a call to audioop.reverse with a one-byte string, a different vulnerability than CVE-2010-1634.\r\nhttps://bugs.python.org/issue7673",
            "cve": "CVE-2010-2089",
            "id": "pyup.io-45662",
            "more_info_path": "/vulnerabilities/CVE-2010-2089/45662",
            "specs": [
                "<2.6.6",
                ">=2.7.0a0,<2.7.0",
                ">=3.0.0a0,<3.1.3",
                ">=3.2.0a0,<3.2.0"
            ],
            "v": "<2.6.6,>=2.7.0a0,<2.7.0,>=3.0.0a0,<3.1.3,>=3.2.0a0,<3.2.0"
        },
        {
            "advisory": "Python version 2.6.7, 2.7.2, 3.1.4 and 3.2.0 include a fix for CVE-2010-3493: Multiple race conditions in smtpd.py in the smtpd module in Python 2.6, 2.7, 3.1, and 3.2 alpha allow remote attackers to cause a denial of service (daemon outage) by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected return value of None, an unexpected value of None for the address, or an ECONNABORTED, EAGAIN, or EWOULDBLOCK error, or the getpeername function having an ENOTCONN error, a related issue to CVE-2010-3492.\r\nhttps://bugs.python.org/issue9129",
            "cve": "CVE-2010-3493",
            "id": "pyup.io-45655",
            "more_info_path": "/vulnerabilities/CVE-2010-3493/45655",
            "specs": [
                "<2.6.7",
                ">=2.7.0a0,<2.7.2",
                ">=3.0.0a0,<3.1.4",
                ">=3.2.0a0,<3.2.0"
            ],
            "v": "<2.6.7,>=2.7.0a0,<2.7.2,>=3.0.0a0,<3.1.4,>=3.2.0a0,<3.2.0"
        },
        {
            "advisory": "Python versions 2.6.9, 2.7.7, 3.2.6, 3.3.6 and 3.4.1 include a fix for CVE-2013-4238: The ssl.match_hostname function in the SSL module in Python 2.6 through 3.4 does not properly handle a '\\0' character in a domain name in the Subject Alternative Name field of an X.509 certificate, which allows man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority, a related issue to CVE-2009-2408.\r\nhttps://bugs.python.org/issue18709",
            "cve": "CVE-2013-4238",
            "id": "pyup.io-45663",
            "more_info_path": "/vulnerabilities/CVE-2013-4238/45663",
            "specs": [
                "<2.6.9",
                ">=2.7.0a0,<2.7.7",
                ">=3.2.0a0,<3.2.6",
                ">=3.3.0a0,<3.3.6",
                ">=3.4.0a0,<3.4.1"
            ],
            "v": "<2.6.9,>=2.7.0a0,<2.7.7,>=3.2.0a0,<3.2.6,>=3.3.0a0,<3.3.6,>=3.4.0a0,<3.4.1"
        },
        {
            "advisory": "Python versions 2.7.10, 3.3.7 and 3.4.4 include a fix for CVE-2016-5699: CRLF injection vulnerability in the HTTPConnection.putheader function in urllib2 and urllib in CPython (aka Python) before 2.7.10 and 3.x before 3.4.4 allows remote attackers to inject arbitrary HTTP headers via CRLF sequences in a URL.\r\nhttps://bugs.python.org/issue22928",
            "cve": "CVE-2016-5699",
            "id": "pyup.io-45664",
            "more_info_path": "/vulnerabilities/CVE-2016-5699/45664",
            "specs": [
                "<2.7.10",
                ">=3.0.0a0,<3.3.7",
                ">=3.4.0a0,<3.4.4"
            ],
            "v": "<2.7.10,>=3.0.0a0,<3.3.7,>=3.4.0a0,<3.4.4"
        },
        {
            "advisory": "The smtplib library in CPython (aka Python) before 2.7.12, 3.x before 3.4.5, and 3.5.x before 3.5.2 does not return an error when StartTLS fails, which might allow man-in-the-middle attackers to bypass the TLS protections by leveraging a network position between the client and the registry to block the StartTLS command, aka a \"StartTLS stripping attack.\" See CVE-2016-0772.",
            "cve": "CVE-2016-0772",
            "id": "pyup.io-45720",
            "more_info_path": "/vulnerabilities/CVE-2016-0772/45720",
            "specs": [
                "<2.7.12",
                ">=3.0,<3.4.5",
                ">=3.5,<3.5.2"
            ],
            "v": "<2.7.12,>=3.0,<3.4.5,>=3.5,<3.5.2"
        },
        {
            "advisory": "Integer overflow in the get_data function in zipimport.c in CPython (aka Python) before 2.7.12, 3.x before 3.4.5, and 3.5.x before 3.5.2 allows remote attackers to have unspecified impact via a negative data size value, which triggers a heap-based buffer overflow. See CVE-2016-5636.",
            "cve": "CVE-2016-5636",
            "id": "pyup.io-45617",
            "more_info_path": "/vulnerabilities/CVE-2016-5636/45617",
            "specs": [
                "<2.7.12",
                ">=3.0,<3.4.5",
                ">=3.5,<3.5.2"
            ],
            "v": "<2.7.12,>=3.0,<3.4.5,>=3.5,<3.5.2"
        },
        {
            "advisory": "Python versions 2.7.13, 3.3.7, 3.4.6 and 3.5.3 fix an arbitrary code execution in gettext.c2py().\r\nhttps://python-security.readthedocs.io/vuln/gettext-c2py.html",
            "cve": "PVE-2021-42408",
            "id": "pyup.io-45665",
            "more_info_path": "/vulnerabilities/PVE-2021-42408/45665",
            "specs": [
                "<2.7.13",
                ">=3.0.0a0,<3.3.7",
                ">=3.4.0a0,<3.4.6",
                ">=3.5.0a0,<3.5.3"
            ],
            "v": "<2.7.13,>=3.0.0a0,<3.3.7,>=3.4.0a0,<3.4.6,>=3.5.0a0,<3.5.3"
        },
        {
            "advisory": "Python versions 2.7.13, 3.3.7, 3.4.6 and 3.5.3 include a fix for CVE-2016-1000110: The CGIHandler class in Python does not protect against the HTTP_PROXY variable name clash in a CGI script, which could allow a remote attacker to redirect HTTP requests.\r\nhttps://bugs.python.org/issue27568",
            "cve": "CVE-2016-1000110",
            "id": "pyup.io-45666",
            "more_info_path": "/vulnerabilities/CVE-2016-1000110/45666",
            "specs": [
                "<2.7.13",
                ">=3.0.0a0,<3.3.7",
                ">=3.4.0a0,<3.4.6",
                ">=3.5.0a0,<3.5.3"
            ],
            "v": "<2.7.13,>=3.0.0a0,<3.3.7,>=3.4.0a0,<3.4.6,>=3.5.0a0,<3.5.3"
        },
        {
            "advisory": "Python versions 2.7.14, 3.3.7, 3.4.7, 3.5.4 and 3.6.2 update modules/expat to libexpat 2.2.1 to include security fixes.\r\nhttps://bugs.python.org/issue29591",
            "cve": "CVE-2012-6702",
            "id": "pyup.io-45670",
            "more_info_path": "/vulnerabilities/CVE-2012-6702/45670",
            "specs": [
                "<2.7.14",
                ">=3.0.0a0,<3.3.7",
                ">=3.4.0a0,<3.4.7",
                ">=3.5.0a0,<3.5.4",
                ">=3.6.0a0,<3.6.2"
            ],
            "v": "<2.7.14,>=3.0.0a0,<3.3.7,>=3.4.0a0,<3.4.7,>=3.5.0a0,<3.5.4,>=3.6.0a0,<3.6.2"
        },
        {
            "advisory": "Python versions 2.7.14, 3.3.7, 3.4.7, 3.5.4 and 3.6.2 update modules/expat to libexpat 2.2.1 to include security fixes.\r\nhttps://bugs.python.org/issue29591",
            "cve": "CVE-2016-4472",
            "id": "pyup.io-45668",
            "more_info_path": "/vulnerabilities/CVE-2016-4472/45668",
            "specs": [
                "<2.7.14",
                ">=3.0.0a0,<3.3.7",
                ">=3.4.0a0,<3.4.7",
                ">=3.5.0a0,<3.5.4",
                ">=3.6.0a0,<3.6.2"
            ],
            "v": "<2.7.14,>=3.0.0a0,<3.3.7,>=3.4.0a0,<3.4.7,>=3.5.0a0,<3.5.4,>=3.6.0a0,<3.6.2"
        },
        {
            "advisory": "Python versions 2.7.14, 3.3.7, 3.4.7, 3.5.4 and 3.6.2 update modules/expat to libexpat 2.2.1 to include security fixes.\r\nhttps://bugs.python.org/issue29591",
            "cve": "CVE-2016-0718",
            "id": "pyup.io-45667",
            "more_info_path": "/vulnerabilities/CVE-2016-0718/45667",
            "specs": [
                "<2.7.14",
                ">=3.0.0a0,<3.3.7",
                ">=3.4.0a0,<3.4.7",
                ">=3.5.0a0,<3.5.4",
                ">=3.6.0a0,<3.6.2"
            ],
            "v": "<2.7.14,>=3.0.0a0,<3.3.7,>=3.4.0a0,<3.4.7,>=3.5.0a0,<3.5.4,>=3.6.0a0,<3.6.2"
        },
        {
            "advisory": "Python versions 2.7.14, 3.3.7, 3.4.7, 3.5.4 and 3.6.2 update modules/expat to libexpat 2.2.1 to include security fixes.\r\nhttps://bugs.python.org/issue29591",
            "cve": "CVE-2016-5300",
            "id": "pyup.io-45669",
            "more_info_path": "/vulnerabilities/CVE-2016-5300/45669",
            "specs": [
                "<2.7.14",
                ">=3.0.0a0,<3.3.7",
                ">=3.4.0a0,<3.4.7",
                ">=3.5.0a0,<3.5.4",
                ">=3.6.0a0,<3.6.2"
            ],
            "v": "<2.7.14,>=3.0.0a0,<3.3.7,>=3.4.0a0,<3.4.7,>=3.5.0a0,<3.5.4,>=3.6.0a0,<3.6.2"
        },
        {
            "advisory": "Python versions 2.7.14, 3.3.7, 3.4.7, 3.5.4 and 3.6.3 fix ftplib.FTP.putline() to throw an error for a illegal command, as a remote attacker could attack by using newline characters. This issue is similar to CVE-2017-3533.\r\nhttps://bugs.python.org/issue30119",
            "cve": "PVE-2021-42403",
            "id": "pyup.io-45671",
            "more_info_path": "/vulnerabilities/PVE-2021-42403/45671",
            "specs": [
                "<2.7.14",
                ">=3.0.0a0,<3.3.7",
                ">=3.4.0a0,<3.4.7",
                ">=3.5.0a0,<3.5.4",
                ">=3.6.0a0,<3.6.3"
            ],
            "v": "<2.7.14,>=3.0.0a0,<3.3.7,>=3.4.0a0,<3.4.7,>=3.5.0a0,<3.5.4,>=3.6.0a0,<3.6.3"
        },
        {
            "advisory": "Python versions 2.7.14, 3.4.7 and 3.5.4 update its dependency 'zlib' to v1.2.11 to include security fixes.\r\nhttps://bugs.python.org/issue29169",
            "cve": "CVE-2016-9840",
            "id": "pyup.io-45672",
            "more_info_path": "/vulnerabilities/CVE-2016-9840/45672",
            "specs": [
                "<2.7.14",
                ">=3.0.0a0,<3.4.7",
                ">=3.5.0a0,<3.5.4"
            ],
            "v": "<2.7.14,>=3.0.0a0,<3.4.7,>=3.5.0a0,<3.5.4"
        },
        {
            "advisory": "Python versions 2.7.14, 3.4.7 and 3.5.4 update its dependency 'zlib' to v1.2.11 to include security fixes.\r\nhttps://bugs.python.org/issue29169",
            "cve": "CVE-2016-9842",
            "id": "pyup.io-45674",
            "more_info_path": "/vulnerabilities/CVE-2016-9842/45674",
            "specs": [
                "<2.7.14",
                ">=3.0.0a0,<3.4.7",
                ">=3.5.0a0,<3.5.4"
            ],
            "v": "<2.7.14,>=3.0.0a0,<3.4.7,>=3.5.0a0,<3.5.4"
        },
        {
            "advisory": "Python versions 2.7.14, 3.4.7 and 3.5.4 update its dependency 'zlib' to v1.2.11 to include security fixes.\r\nhttps://bugs.python.org/issue29169",
            "cve": "CVE-2016-9841",
            "id": "pyup.io-45673",
            "more_info_path": "/vulnerabilities/CVE-2016-9841/45673",
            "specs": [
                "<2.7.14",
                ">=3.0.0a0,<3.4.7",
                ">=3.5.0a0,<3.5.4"
            ],
            "v": "<2.7.14,>=3.0.0a0,<3.4.7,>=3.5.0a0,<3.5.4"
        },
        {
            "advisory": "Python versions 2.7.14, 3.4.8 and 3.5.5 include a fix for CVE-2017-1000158: Integer overflow in the PyString_DecodeEscape function in stringobject.c, resulting in heap-based buffer overflow (and possible arbitrary code execution).\r\nhttps://bugs.python.org/issue30657",
            "cve": "CVE-2017-1000158",
            "id": "pyup.io-45675",
            "more_info_path": "/vulnerabilities/CVE-2017-1000158/45675",
            "specs": [
                "<2.7.14",
                ">=3.5.0a0,<3.5.5",
                ">=3.0.0a0,<3.4.8"
            ],
            "v": "<2.7.14,>=3.5.0a0,<3.5.5,>=3.0.0a0,<3.4.8"
        },
        {
            "advisory": "Python 2.7.15 includes a fix for CVE-2018-1000030: Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Python versions prior to 2.7.14 may also be vulnerable and it appears that Python 2.7.17 and prior may also be vulnerable however this has not been confirmed. The vulnerability lies when multiply threads are handling large amounts of data. In both cases there is essentially a race condition that occurs. For the Heap-Buffer-Overflow, Thread 2 is creating the size for a buffer, but Thread1 is already writing to the buffer without knowing how much to write. So when a large amount of data is being processed, it is very easy to cause memory corruption using a Heap-Buffer-Overflow. As for the Use-After-Free, Thread3->Malloc->Thread1->Free's->Thread2-Re-uses-Free'd Memory. The PSRT has stated that this is not a security vulnerability due to the fact that the attacker must be able to run code, however in some situations, such as function as a service, this vulnerability can potentially be used by an attacker to violate a trust boundary, as such the DWF feels this issue deserves a CVE.\r\nhttps://bugs.python.org/issue31530",
            "cve": "CVE-2018-1000030",
            "id": "pyup.io-45645",
            "more_info_path": "/vulnerabilities/CVE-2018-1000030/45645",
            "specs": [
                "<2.7.15"
            ],
            "v": "<2.7.15"
        },
        {
            "advisory": "Python before versions 2.7.15, 3.4.9, 3.5.6, 3.6.5 and 3.7.0 is vulnerable to catastrophic backtracking in the difflib.IS_LINE_JUNK method. An attacker could use this flaw to cause denial of service. See CVE-2018-1061.\r\nhttps://bugs.python.org/issue32981",
            "cve": "CVE-2018-1061",
            "id": "pyup.io-45653",
            "more_info_path": "/vulnerabilities/CVE-2018-1061/45653",
            "specs": [
                "<2.7.15",
                ">=3.0.0a0,<3.4.9",
                ">=3.5.0a0,<3.5.6",
                ">=3.6.0a0,<3.6.5",
                ">=3.7.0a0,<3.7.0"
            ],
            "v": "<2.7.15,>=3.0.0a0,<3.4.9,>=3.5.0a0,<3.5.6,>=3.6.0a0,<3.6.5,>=3.7.0a0,<3.7.0"
        },
        {
            "advisory": "Python before versions 2.7.15, 3.4.9, 3.5.6rc1, 3.6.5rc1 and 3.7.0 is vulnerable to catastrophic backtracking in pop3lib's apop() method. An attacker could use this flaw to cause denial of service.",
            "cve": "CVE-2018-1060",
            "id": "pyup.io-45654",
            "more_info_path": "/vulnerabilities/CVE-2018-1060/45654",
            "specs": [
                "<2.7.15",
                ">=3.0.0a0,<3.4.9",
                ">=3.5.0a0,<3.5.6rc1",
                ">=3.6.0a0,<3.6.5rc1",
                ">=3.7.0a0,<3.7.0"
            ],
            "v": "<2.7.15,>=3.0.0a0,<3.4.9,>=3.5.0a0,<3.5.6rc1,>=3.6.0a0,<3.6.5rc1,>=3.7.0a0,<3.7.0"
        },
        {
            "advisory": "Python 2.7.16 includes a fix for CVE-2018-1000802: Python Software Foundation Python (CPython) version 2.7 contains a CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in shutil module (make_archive function) that can result in Denial of service or Information gain via injection of arbitrary files on the system or entire drive. This attack appear to be exploitable via Passage of unfiltered user input to the function.\r\nhttps://bugs.python.org/issue34540",
            "cve": "CVE-2018-1000802",
            "id": "pyup.io-45646",
            "more_info_path": "/vulnerabilities/CVE-2018-1000802/45646",
            "specs": [
                "<2.7.16"
            ],
            "v": "<2.7.16"
        },
        {
            "advisory": "Python versions 2.7.16, 3.4.10, 3.5.7, 3.6.7 and 3.7.1 include a fix for CVE-2018-14647: Python's elementtree C accelerator failed to initialise Expat's hash salt during initialization. This could make it easy to conduct denial of service attacks against Expat by constructing an XML document that would cause pathological hash collisions in Expat's internal data structures, consuming large amounts CPU and RAM.\r\nhttps://bugs.python.org/issue34623",
            "cve": "CVE-2018-14647",
            "id": "pyup.io-45677",
            "more_info_path": "/vulnerabilities/CVE-2018-14647/45677",
            "specs": [
                "<2.7.16",
                ">=3.0.0a0,<3.4.10",
                ">=3.5.0a0,<3.5.7",
                ">=3.6.0a0,<3.6.7",
                ">=3.7.0a0,<3.7.1"
            ],
            "v": "<2.7.16,>=3.0.0a0,<3.4.10,>=3.5.0a0,<3.5.7,>=3.6.0a0,<3.6.7,>=3.7.0a0,<3.7.1"
        },
        {
            "advisory": "Python versions 2.7.16, 3.4.10, 3.5.7, 3.6.7, 3.7.1 and 3.8.0 include a fix for CVE-2019-17514: Library/glob.html in the Python 2 and 3 documentation before 2016 has potentially misleading information about whether sorting occurs, as demonstrated by irreproducible cancer-research results. NOTE: the effects of this documentation cross application domains, and thus it is likely that security-relevant code elsewhere is affected. This issue is not a Python implementation bug, and there are no reports that NMR researchers were specifically relying on library/glob.html. In other words, because the older documentation stated \"finds all the pathnames matching a specified pattern according to the rules used by the Unix shell,\" one might have incorrectly inferred that the sorting that occurs in a Unix shell also occurred for glob.glob. There is a workaround in newer versions of Willoughby nmr-data_compilation-p2.py and nmr-data_compilation-p3.py, which call sort() directly.\r\nhttps://bugs.python.org/issue33275\r\nhttps://www.vice.com/en/article/zmjwda/a-code-glitch-may-have-caused-errors-in-more-than-100-published-studies",
            "cve": "CVE-2019-17514",
            "id": "pyup.io-45678",
            "more_info_path": "/vulnerabilities/CVE-2019-17514/45678",
            "specs": [
                "<2.7.16",
                ">=3.0.0a0,<3.4.10",
                ">=3.5.0a0,<3.5.7",
                ">=3.6.0a0,<3.6.7",
                ">=3.7.0a0,<3.7.1",
                ">=3.8.0a0,<3.8.0"
            ],
            "v": "<2.7.16,>=3.0.0a0,<3.4.10,>=3.5.0a0,<3.5.7,>=3.6.0a0,<3.6.7,>=3.7.0a0,<3.7.1,>=3.8.0a0,<3.8.0"
        },
        {
            "advisory": "Python versions 2.7.16, 3.4.10, 3.5.7, 3.6.9 and 3.7.3 include a fix for CVE-2019-5010: An exploitable denial-of-service vulnerability exists in the X509 certificate parser of Python.org Python 2.7.11 / 3.6.6. A specially crafted X509 certificate can cause a NULL pointer dereference, resulting in a denial of service. An attacker can initiate or accept TLS connections using crafted certificates to trigger this vulnerability.\r\nhttps://bugs.python.org/issue35746",
            "cve": "CVE-2019-5010",
            "id": "pyup.io-45680",
            "more_info_path": "/vulnerabilities/CVE-2019-5010/45680",
            "specs": [
                "<2.7.16",
                ">=3.0.0a0,<3.4.10",
                ">=3.5.0a0,<3.5.7",
                ">=3.6.0a0,<3.6.9",
                ">=3.7.0a0,<3.7.3"
            ],
            "v": "<2.7.16,>=3.0.0a0,<3.4.10,>=3.5.0a0,<3.5.7,>=3.6.0a0,<3.6.9,>=3.7.0a0,<3.7.3"
        },
        {
            "advisory": "Python versions 2.7.16, 3.4.10, 3.5.7, 3.6.9 and 3.7.3 include a fix for CVE-2018-20852: http.cookiejar.DefaultPolicy.domain_return_ok in Lib/http/cookiejar.py in Python before 3.7.3 does not correctly validate the domain: it can be tricked into sending existing cookies to the wrong server. An attacker may abuse this flaw by using a server with a hostname that has another valid hostname as a suffix (e.g., pythonicexample.com to steal cookies for example.com). When a program uses http.cookiejar.DefaultPolicy and tries to do an HTTP connection to an attacker-controlled server, existing cookies can be leaked to the attacker.\r\nhttps://bugs.python.org/issue35121",
            "cve": "CVE-2018-20852",
            "id": "pyup.io-45679",
            "more_info_path": "/vulnerabilities/CVE-2018-20852/45679",
            "specs": [
                "<2.7.16",
                ">=3.0.0a0,<3.4.10",
                ">=3.5.0a0,<3.5.7",
                ">=3.6.0a0,<3.6.9",
                ">=3.7.0a0,<3.7.3"
            ],
            "v": "<2.7.16,>=3.0.0a0,<3.4.10,>=3.5.0a0,<3.5.7,>=3.6.0a0,<3.6.9,>=3.7.0a0,<3.7.3"
        },
        {
            "advisory": "Python versions 2.7.17, 3.5.10, 3.6.10 and 3.7.5 include a fix for CVE-2019-16935: The documentation XML-RPC server in Python through 2.7.16, 3.x through 3.6.9, and 3.7.x through 3.7.4 has XSS via the server_title field. This occurs in Lib/DocXMLRPCServer.py in Python 2.x, and in Lib/xmlrpc/server.py in Python 3.x. If set_server_title is called with untrusted input, arbitrary JavaScript can be delivered to clients that visit the http URL for this server.\r\nhttps://bugs.python.org/issue38243",
            "cve": "CVE-2019-16935",
            "id": "pyup.io-45681",
            "more_info_path": "/vulnerabilities/CVE-2019-16935/45681",
            "specs": [
                "<2.7.17",
                ">=3.0.0a0,<3.5.10",
                ">=3.6.0a0,<3.6.10",
                ">=3.7.0a0,<3.7.5"
            ],
            "v": "<2.7.17,>=3.0.0a0,<3.5.10,>=3.6.0a0,<3.6.10,>=3.7.0a0,<3.7.5"
        },
        {
            "advisory": "Python versions 2.7.17, 3.5.7, 3.6.9 and 3.7.3 include a fix for CVE-2019-9636: Python 2.7.x through 2.7.16 and 3.x through 3.7.2 is affected by Improper Handling of Unicode Encoding (with an incorrect netloc) during NFKC normalization. The impact is information disclosure (credentials, cookies, etc. that are cached against a given hostname). The affected components are urllib.parse.urlsplit and urllib.parse.urlparse. The attack vector is a specially crafted URL that could be incorrectly parsed to locate cookies or authentication data and send that information to a different host.\r\nhttps://bugs.python.org/issue36216",
            "cve": "CVE-2019-9636",
            "id": "pyup.io-45682",
            "more_info_path": "/vulnerabilities/CVE-2019-9636/45682",
            "specs": [
                "<2.7.17",
                ">=3.0.0a0,<3.5.7",
                ">=3.6.0a0,<3.6.9",
                ">=3.7.0a0,<3.7.3"
            ],
            "v": "<2.7.17,>=3.0.0a0,<3.5.7,>=3.6.0a0,<3.6.9,>=3.7.0a0,<3.7.3"
        },
        {
            "advisory": "Python versions 3.8.0b2, 3.7.4, 3.6.10, 3.5.8 and 2.7.17 include a fix for CVE-2019-10160: A security regression of CVE-2019-9636 was discovered in python since commit d537ab0ff9767ef024f26246899728f0116b1ec3 affecting versions 2.7, 3.5, 3.6, 3.7 and from v3.8.0a4 through v3.8.0b1, which still allows an attacker to exploit CVE-2019-9636 by abusing the user and password parts of a URL. When an application parses user-supplied URLs to store cookies, authentication credentials, or other kind of information, it is possible for an attacker to provide specially crafted URLs to make the application locate host-related information (e.g. cookies, authentication data) and send them to a different host than where it should, unlike if the URLs had been correctly parsed. The result of an attack may vary based on the application.\r\nhttps://bugs.python.org/issue36742",
            "cve": "CVE-2019-10160",
            "id": "pyup.io-45708",
            "more_info_path": "/vulnerabilities/CVE-2019-10160/45708",
            "specs": [
                "<2.7.17",
                ">=3.0.0a0,<3.5.8",
                ">=3.6.0a0,<3.6.10",
                ">=3.7.0a0,<3.7.4",
                ">=3.8.0a0,<3.8.0b2"
            ],
            "v": "<2.7.17,>=3.0.0a0,<3.5.8,>=3.6.0a0,<3.6.10,>=3.7.0a0,<3.7.4,>=3.8.0a0,<3.8.0b2"
        },
        {
            "advisory": "Python versions 2.7.17, 3.5.8, 3.6.10 and 3.7.5 include a fix for CVE-2019-9948: Urllib in Python 2.x through 2.7.16 supports the local_file: scheme, which makes it easier for remote attackers to bypass protection mechanisms that blacklist file: URIs, as demonstrated by triggering a urllib.urlopen('local_file:///etc/passwd') call. The issue was also found to be present in Python 3 when using URLopener class.\r\nhttps://bugs.python.org/issue35907",
            "cve": "CVE-2019-9948",
            "id": "pyup.io-45684",
            "more_info_path": "/vulnerabilities/CVE-2019-9948/45684",
            "specs": [
                "<2.7.17",
                ">=3.0.0a0,<3.5.8",
                ">=3.6.0a0,<3.6.10",
                ">=3.7.0a0,<3.7.5"
            ],
            "v": "<2.7.17,>=3.0.0a0,<3.5.8,>=3.6.0a0,<3.6.10,>=3.7.0a0,<3.7.5"
        },
        {
            "advisory": "An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \\r\\n (specifically in the query string after a ? character) followed by an HTTP header or a Redis command.",
            "cve": "CVE-2019-9740",
            "id": "pyup.io-45685",
            "more_info_path": "/vulnerabilities/CVE-2019-9740/45685",
            "specs": [
                "<2.7.17",
                ">=3.0.0a0,<3.5.8",
                ">=3.6.0a0,<3.6.9",
                ">=3.7.0a0,<3.7.4"
            ],
            "v": "<2.7.17,>=3.0.0a0,<3.5.8,>=3.6.0a0,<3.6.9,>=3.7.0a0,<3.7.4"
        },
        {
            "advisory": "Python versions 2.7.17, 3.5.8, 3.6.9 and 3.7.4 include a fix for CVE-2019-9947: An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \\r\\n (specifically in the path component of a URL that lacks a ? character) followed by an HTTP header or a Redis command. This is similar to the CVE-2019-9740 query string issue.\r\nhttps://bugs.python.org/issue35906",
            "cve": "CVE-2019-9947",
            "id": "pyup.io-45686",
            "more_info_path": "/vulnerabilities/CVE-2019-9947/45686",
            "specs": [
                "<2.7.17",
                ">=3.0.0a0,<3.5.8",
                ">=3.6.0a0,<3.6.9",
                ">=3.7.0a0,<3.7.4"
            ],
            "v": "<2.7.17,>=3.0.0a0,<3.5.8,>=3.6.0a0,<3.6.9,>=3.7.0a0,<3.7.4"
        },
        {
            "advisory": "Python 2.7.18rc1, 3.5.10rc1, 3.6.11rc1, 3.7.8rc1 and 3.8.3rc1 include a fix for CVE-2019-18348: An issue was discovered in urllib2 in Python 2.x through 2.7.17 and urllib in Python 3.x through 3.8.0. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \\r\\n (specifically in the host component of a URL) followed by an HTTP header. This is similar to the CVE-2019-9740 query string issue and the CVE-2019-9947 path string issue. (This is not exploitable when glibc has CVE-2016-10739 fixed.).\r\nhttps://bugs.python.org/issue30458#msg347282",
            "cve": "CVE-2019-18348",
            "id": "pyup.io-45647",
            "more_info_path": "/vulnerabilities/CVE-2019-18348/45647",
            "specs": [
                "<2.7.18rc1",
                ">=3.0.0a0,<3.5.10rc1",
                ">=3.6.0a0,<3.6.11rc1",
                ">=3.7.0a0,<3.7.8rc1",
                ">=3.8.0a0,<3.8.3rc1"
            ],
            "v": "<2.7.18rc1,>=3.0.0a0,<3.5.10rc1,>=3.6.0a0,<3.6.11rc1,>=3.7.0a0,<3.7.8rc1,>=3.8.0a0,<3.8.3rc1"
        },
        {
            "advisory": "BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.",
            "cve": "CVE-2019-12900",
            "id": "pyup.io-70532",
            "more_info_path": "/vulnerabilities/CVE-2019-12900/70532",
            "specs": [
                "<2.7.18rc1",
                ">=3.0.0a0,<3.5.10rc1",
                ">=3.6.0a0,<3.6.11rc1",
                ">=3.7.0a0,<3.7.8rc1",
                ">=3.8.0a0,<3.8.3rc1"
            ],
            "v": "<2.7.18rc1,>=3.0.0a0,<3.5.10rc1,>=3.6.0a0,<3.6.11rc1,>=3.7.0a0,<3.7.8rc1,>=3.8.0a0,<3.8.3rc1"
        },
        {
            "advisory": "The urllib and urllib2 modules in Python 2.x before 2.7.2 and 3.x before 3.2.1 process Location headers that specify redirection to file: URLs, which makes it easier for remote attackers to obtain sensitive information or cause a denial of service (resource consumption) via a crafted URL, as demonstrated by the file:///etc/passwd and file:///dev/zero URLs. See CVE-2011-1521.",
            "cve": "CVE-2011-1521",
            "id": "pyup.io-45721",
            "more_info_path": "/vulnerabilities/CVE-2011-1521/45721",
            "specs": [
                "<2.7.2",
                ">=3.0.0a0,<3.2.1"
            ],
            "v": "<2.7.2,>=3.0.0a0,<3.2.1"
        },
        {
            "advisory": "Python versions 2.7.3 and 3.1.5 include a fix for CVE-2010-3492: The asyncore module in Python before 3.2 does not properly handle unsuccessful calls to the accept function, and does not have accompanying documentation describing how daemon applications should handle unsuccessful calls to the accept function, which makes it easier for remote attackers to conduct denial of service attacks that terminate these applications via network connections.\r\nhttps://bugs.python.org/issue6706",
            "cve": "CVE-2010-3492",
            "id": "pyup.io-45687",
            "more_info_path": "/vulnerabilities/CVE-2010-3492/45687",
            "specs": [
                "<2.7.3",
                ">=3.0.0a0,<3.1.5"
            ],
            "v": "<2.7.3,>=3.0.0a0,<3.1.5"
        },
        {
            "advisory": "Python versions 2.7.7, 3.1.5, 3.2.6, 3.3.4 and 3.4.0 include a fix for CVE-2014-1912: Buffer overflow in the socket.recvfrom_into function in Modules/socketmodule.c in Python 2.5 before 2.7.7, 3.x before 3.3.4, and 3.4.x before 3.4rc1 allows remote attackers to execute arbitrary code via a crafted string.\r\nhttps://bugs.python.org/issue20246",
            "cve": "CVE-2014-1912",
            "id": "pyup.io-45688",
            "more_info_path": "/vulnerabilities/CVE-2014-1912/45688",
            "specs": [
                "<2.7.7",
                ">=3.0.0a0,<3.1.5",
                ">=3.2.0a0,<3.2.6",
                ">=3.3.0a0,<3.3.4",
                ">=3.4.0a0,<3.4.0"
            ],
            "v": "<2.7.7,>=3.0.0a0,<3.1.5,>=3.2.0a0,<3.2.6,>=3.3.0a0,<3.3.4,>=3.4.0a0,<3.4.0"
        },
        {
            "advisory": "Python versions 2.7.7, 3.2.6, 3.3.6, 3.4.2 and 3.5.0 include a fix for CVE-2014-4616: Array index error in the scanstring function in the _json module in Python 2.7 through 3.5 and simplejson before 2.6.1 allows context-dependent attackers to read arbitrary process memory via a negative index value in the idx argument to the raw_decode function.\r\nhttps://bugs.python.org/issue21529",
            "cve": "CVE-2014-4616",
            "id": "pyup.io-45689",
            "more_info_path": "/vulnerabilities/CVE-2014-4616/45689",
            "specs": [
                "<2.7.7",
                ">=3.0.0a0,<3.2.6",
                ">=3.3.0a0,<3.3.6",
                ">=3.4.0a0,<3.4.2",
                ">=3.5.0a0,<3.5.0"
            ],
            "v": "<2.7.7,>=3.0.0a0,<3.2.6,>=3.3.0a0,<3.3.6,>=3.4.0a0,<3.4.2,>=3.5.0a0,<3.5.0"
        },
        {
            "advisory": "Python 2.7.8 includes a fix for CVE-2014-7185: Integer overflow in bufferobject.c in Python before 2.7.8 allows context-dependent attackers to obtain sensitive information from process memory via a large size and offset in a \"buffer\" function.\r\nhttps://bugs.python.org/issue21831",
            "cve": "CVE-2014-7185",
            "id": "pyup.io-45648",
            "more_info_path": "/vulnerabilities/CVE-2014-7185/45648",
            "specs": [
                "<2.7.8"
            ],
            "v": "<2.7.8"
        },
        {
            "advisory": "Python versions 2.7.8, 3.2.6, 3.3.6 and 3.4.2 include a fix for CVE-2014-4650: The CGIHTTPServer module in Python 2.7.5 and 3.3.4 (possible in others too) does not properly handle URLs in which URL encoding is used for path separators, which allows remote attackers to read script source code or conduct directory traversal attacks and execute unintended code via a crafted character sequence, as demonstrated by a %2f separator.\r\nhttps://bugs.python.org/issue21766",
            "cve": "CVE-2014-4650",
            "id": "pyup.io-45690",
            "more_info_path": "/vulnerabilities/CVE-2014-4650/45690",
            "specs": [
                "<2.7.8",
                ">=3.0.0a0,<3.2.6",
                ">=3.3.0a0,<3.3.6",
                ">=3.4.0a0,<3.4.2"
            ],
            "v": "<2.7.8,>=3.0.0a0,<3.2.6,>=3.3.0a0,<3.3.6,>=3.4.0a0,<3.4.2"
        },
        {
            "advisory": "Python versions 2.7.9, 3.2.6, 3.3.7 and 3.4.3 include a fix for CVE-2013-1752: Smtplib and ftplib unlimited read. This issue was initially assigned a CVE but it was rejected due to the patch not working for some OSes (now fixed).\r\nhttps://bugs.python.org/issue16039\r\nhttps://python-security.readthedocs.io/vuln/ftplib-unlimited-read.html\r\nhttps://python-security.readthedocs.io/vuln/smtplib-unlimited-read.html",
            "cve": "CVE-2013-1752",
            "id": "pyup.io-45676",
            "more_info_path": "/vulnerabilities/CVE-2013-1752/45676",
            "specs": [
                "<2.7.9",
                ">=3.0.0a0,<3.2.6",
                ">=3.3.0a0,<3.3.7",
                ">=3.4.0a0,<3.4.3"
            ],
            "v": "<2.7.9,>=3.0.0a0,<3.2.6,>=3.3.0a0,<3.3.7,>=3.4.0a0,<3.4.3"
        },
        {
            "advisory": "Python version 2.7.9 and 3.3.3 include a fix for CVE-2013-7440: The ssl.match_hostname function in CPython (aka Python) before 2.7.9 and 3.x before 3.3.3 does not properly handle wildcards in hostnames, which might allow man-in-the-middle attackers to spoof servers via a crafted certificate.\r\nhttps://bugs.python.org/issue17997",
            "cve": "CVE-2013-7440",
            "id": "pyup.io-45656",
            "more_info_path": "/vulnerabilities/CVE-2013-7440/45656",
            "specs": [
                "<2.7.9",
                ">=3.0.0a0,<3.3.3"
            ],
            "v": "<2.7.9,>=3.0.0a0,<3.3.3"
        },
        {
            "advisory": "Python versions 2.7.9 and 3.4.3 include a fix for CVE-2014-9365: The HTTP clients in the (1) httplib, (2) urllib, (3) urllib2, and (4) xmlrpclib libraries in CPython (aka Python) 2.x before 2.7.9 and 3.x before 3.4.3, when accessing an HTTPS URL, do not (a) check the certificate against a trust store or verify that the server hostname matches a domain name in the subject's (b) Common Name or (c) subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.\r\nhttps://bugs.python.org/issue22417",
            "cve": "CVE-2014-9365",
            "id": "pyup.io-45691",
            "more_info_path": "/vulnerabilities/CVE-2014-9365/45691",
            "specs": [
                "<2.7.9",
                ">=3.0.0a0,<3.4.3"
            ],
            "v": "<2.7.9,>=3.0.0a0,<3.4.3"
        },
        {
            "advisory": "Python versions 2.7.9, 3.2.6, 3.3.6 and 3.4.3 include a fix for CVE-2013-1753: The gzip_decode function in the xmlrpc client library in Python 3.4 and earlier allows remote attackers to cause a denial of service (memory consumption) via a crafted HTTP request.\r\nhttps://bugs.python.org/issue16043",
            "cve": "CVE-2013-1753",
            "id": "pyup.io-45692",
            "more_info_path": "/vulnerabilities/CVE-2013-1753/45692",
            "specs": [
                "<2.7.9",
                ">=3.2.0a0,<3.2.6",
                ">=3.3.0a0,<3.3.6",
                ">=3.4.0a0,<3.4.3"
            ],
            "v": "<2.7.9,>=3.2.0a0,<3.2.6,>=3.3.0a0,<3.3.6,>=3.4.0a0,<3.4.3"
        },
        {
            "advisory": "A defect was discovered in the Python \u201cssl\u201d module where there is a memory race condition with the ssl.SSLContext methods \u201ccert_store_stats()\u201d and \u201cget_ca_certs()\u201d. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured.",
            "cve": "CVE-2024-0397",
            "id": "pyup.io-71775",
            "more_info_path": "/vulnerabilities/CVE-2024-0397/71775",
            "specs": [
                "<3.10.14",
                ">=3.11.0a0,<3.11.9",
                ">=3.12.0a0,<3.12.3",
                ">=3.13.0a0,<3.13.0a5"
            ],
            "v": "<3.10.14,>=3.11.0a0,<3.11.9,>=3.12.0a0,<3.12.3,>=3.13.0a0,<3.13.0a5"
        },
        {
            "advisory": "An issue was found in CPython 3.12.0 `subprocess` module on POSIX platforms. The issue was fixed in CPython 3.12.1 and does not affect other stable releases. When using the `extra_groups=` parameter with an empty list as a value (ie `extra_groups=[]`) the logic regressed to not call `setgroups(0, NULL)` before calling `exec()`, thus not dropping the original processes' groups before starting the new process. There is no issue when the parameter isn't used or when any value is used besides an empty list. This issue only impacts CPython processes run with sufficient privilege to make the `setgroups` system call (typically `root`).",
            "cve": "CVE-2023-6507",
            "id": "pyup.io-70382",
            "more_info_path": "/vulnerabilities/CVE-2023-6507/70382",
            "specs": [
                "<3.12.1"
            ],
            "v": "<3.12.1"
        },
        {
            "advisory": "Python version 3.4 includes a fix for CVE-2013-7040: Python before 3.4 only uses the last eight bits of the prefix to randomize hash values, which causes it to compute hash values without restricting the ability to trigger hash collisions predictably and makes it easier for context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-1150.\r\nhttps://bugs.python.org/issue14621",
            "cve": "CVE-2013-7040",
            "id": "pyup.io-45657",
            "more_info_path": "/vulnerabilities/CVE-2013-7040/45657",
            "specs": [
                "<3.4.0"
            ],
            "v": "<3.4.0"
        },
        {
            "advisory": "Python versions 3.9.0a6, 3.8.4, 3.7.8, 3.6.11, and 3.5.10 disallow CR or LF in email.headerregistry.Address arguments to guard against header injection attacks.\r\nhttps://bugs.python.org/issue39073",
            "cve": "PVE-2021-42386",
            "id": "pyup.io-45709",
            "more_info_path": "/vulnerabilities/PVE-2021-42386/45709",
            "specs": [
                "<3.5.10",
                ">=3.6.0a0,<3.6.11",
                ">=3.7.0a0,<3.7.8",
                ">=3.8.0a0,<3.8.4",
                ">=3.9.0a0,<3.9.0a6"
            ],
            "v": "<3.5.10,>=3.6.0a0,<3.6.11,>=3.7.0a0,<3.7.8,>=3.8.0a0,<3.8.4,>=3.9.0a0,<3.9.0a6"
        },
        {
            "advisory": "Python 3.5.10, 3.6.12, 3.7.9, 3.8.4 and 3.9.0 include a fix for CVE-2020-15523: A Trojan horse python3.dll might be used in cases where CPython is embedded in a native application. This occurs because python3X.dll may use an invalid search path for python3.dll loading (after Py_SetPath has been used). \r\n#NOTE: This vulnerability affects only users of Windows.\r\n#NOTE2: this issue CANNOT occur when using python.exe from a standard (non-embedded) Python installation on Windows.\r\nhttps://python-security.readthedocs.io/vuln/pysetpath-python-dll-path.html",
            "cve": "CVE-2020-15523",
            "id": "pyup.io-38490",
            "more_info_path": "/vulnerabilities/CVE-2020-15523/38490",
            "specs": [
                "<3.5.10",
                ">=3.6.0a0,<3.6.12",
                ">=3.7.0a0,<3.7.9",
                ">=3.8.0a0,<3.8.4",
                ">=3.9.0a0,<3.9.0"
            ],
            "v": "<3.5.10,>=3.6.0a0,<3.6.12,>=3.7.0a0,<3.7.9,>=3.8.0a0,<3.8.4,>=3.9.0a0,<3.9.0"
        },
        {
            "advisory": "http.client in Python 3.x before 3.5.10, 3.6.x before 3.6.12, 3.7.x before 3.7.9, and 3.8.x before 3.8.5 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of HTTPConnection.request.",
            "cve": "CVE-2020-26116",
            "id": "pyup.io-45697",
            "more_info_path": "/vulnerabilities/CVE-2020-26116/45697",
            "specs": [
                "<3.5.10",
                ">=3.6.0a0,<3.6.12",
                ">=3.7.0a0,<3.7.9",
                ">=3.8.0a0,<3.8.5",
                ">=3.9.0a0,<3.9.0b5"
            ],
            "v": "<3.5.10,>=3.6.0a0,<3.6.12,>=3.7.0a0,<3.7.9,>=3.8.0a0,<3.8.5,>=3.9.0a0,<3.9.0b5"
        },
        {
            "advisory": "In Lib/tarfile.py in Python through 3.8.3, an attacker is able to craft a TAR archive leading to an infinite loop when opened by tarfile.open, because _proc_pax lacks header validation.",
            "cve": "CVE-2019-20907",
            "id": "pyup.io-45650",
            "more_info_path": "/vulnerabilities/CVE-2019-20907/45650",
            "specs": [
                "<3.5.10",
                ">=3.6.0a0,<3.6.15",
                ">=3.7.0a0,<3.7.9",
                ">=3.8.0a0,<3.8.4"
            ],
            "v": "<3.5.10,>=3.6.0a0,<3.6.15,>=3.7.0a0,<3.7.9,>=3.8.0a0,<3.8.4"
        },
        {
            "advisory": "Python versions 3.5.10rc1, 3.6.12, 3.7.9, 3.8.4 and 3.9.0b4 include a fix for CVE-2020-14422: Lib/ipaddress.py in Python through 3.8.3 improperly computes hash values in the IPv4Interface and IPv6Interface classes, which might allow a remote attacker to cause a denial of service if an application is affected by the performance of a dictionary containing IPv4Interface or IPv6Interface objects, and this attacker can cause many dictionary entries to be created.\r\nhttps://bugs.python.org/issue41004",
            "cve": "CVE-2020-14422",
            "id": "pyup.io-45698",
            "more_info_path": "/vulnerabilities/CVE-2020-14422/45698",
            "specs": [
                "<3.5.10rc1",
                ">=3.6.0a0,<3.6.12",
                ">=3.7.0a0,<3.7.9",
                ">=3.8.0a0,<3.8.4",
                ">=3.9.0a0,<3.9.0b4"
            ],
            "v": "<3.5.10rc1,>=3.6.0a0,<3.6.12,>=3.7.0a0,<3.7.9,>=3.8.0a0,<3.8.4,>=3.9.0a0,<3.9.0b4"
        },
        {
            "advisory": "Python versions 3.6.10, 3.7.5 and 3.8.0 fix an infinite loop with short maximum line lengths in EmailPolicy.\r\nhttps://bugs.python.org/issue36564",
            "cve": "PVE-2021-42390",
            "id": "pyup.io-45699",
            "more_info_path": "/vulnerabilities/PVE-2021-42390/45699",
            "specs": [
                "<3.6.10",
                ">=3.7.0a0,<3.7.5",
                ">=3.8.0a0,<3.8.0"
            ],
            "v": "<3.6.10,>=3.7.0a0,<3.7.5,>=3.8.0a0,<3.8.0"
        },
        {
            "advisory": "Python versions 3.6.10, 3.7.6 and 3.8.1 fix loop.create_datagram_endpoint()'s usage of SO_REUSEADDR that allowed  by default multiple processes to bind the same port.\r\nhttps://bugs.python.org/issue37228",
            "cve": "PVE-2021-42387",
            "id": "pyup.io-45700",
            "more_info_path": "/vulnerabilities/PVE-2021-42387/45700",
            "specs": [
                "<3.6.10",
                ">=3.7.0a0,<3.7.6",
                ">=3.8.0a0,<3.8.1"
            ],
            "v": "<3.6.10,>=3.7.0a0,<3.7.6,>=3.8.0a0,<3.8.1"
        },
        {
            "advisory": "Python 3.6.11, 3.7.7 and 3.8.2 include a fix for CVE-2022-48560: Use After Free vulnerability via heappushpop in heapq.\r\nhttps://bugs.python.org/issue39421",
            "cve": "CVE-2022-48560",
            "id": "pyup.io-60628",
            "more_info_path": "/vulnerabilities/CVE-2022-48560/60628",
            "specs": [
                "<3.6.11",
                ">=3.7.0a1,<3.7.7",
                ">=3.8.0a1,<3.8.2",
                ">=3.9.0a1,<3.9.0a3"
            ],
            "v": "<3.6.11,>=3.7.0a1,<3.7.7,>=3.8.0a1,<3.8.2,>=3.9.0a1,<3.9.0a3"
        },
        {
            "advisory": "Python versions 3.6.13, 3.7.10, 3.8.7, 3.9.2 and 3.10.0a4 use CRYPTO_memcmp() for compare_digest to try harder to be constant-time.\r\nhttps://bugs.python.org/issue40791",
            "cve": "PVE-2021-42385",
            "id": "pyup.io-45702",
            "more_info_path": "/vulnerabilities/PVE-2021-42385/45702",
            "specs": [
                "<3.6.13",
                ">=3.7.0a0,<3.7.10",
                ">=3.8.0a0,<3.8.7",
                ">=3.9.0a0,<3.9.2",
                ">=3.10.0a0,<3.10.0a4"
            ],
            "v": "<3.6.13,>=3.7.0a0,<3.7.10,>=3.8.0a0,<3.8.7,>=3.9.0a0,<3.9.2,>=3.10.0a0,<3.10.0a4"
        },
        {
            "advisory": "Python versions 3.6.14, 3.7.11, 3.8.10, 3.9.5 and 3.10.0 include a fix for CVE-2021-3733: There's a flaw in urllib's AbstractBasicAuthHandler class. An attacker who controls a malicious HTTP server that an HTTP client (such as web browser) connects to, could trigger a Regular Expression Denial of Service (ReDOS) during an authentication request with a specially crafted payload that is sent by the server to the client.\r\nhttps://python-security.readthedocs.io/vuln/urllib-basic-auth-regex2.html",
            "cve": "CVE-2021-3733",
            "id": "pyup.io-45815",
            "more_info_path": "/vulnerabilities/CVE-2021-3733/45815",
            "specs": [
                "<3.6.14",
                ">=3.7.0a0,<3.7.11",
                ">=3.8.0a0,<3.8.10",
                ">=3.9.0a0,<3.9.5",
                ">=3.10.0a0,<3.10.0"
            ],
            "v": "<3.6.14,>=3.7.0a0,<3.7.11,>=3.8.0a0,<3.8.10,>=3.9.0a0,<3.9.5,>=3.10.0a0,<3.10.0"
        },
        {
            "advisory": "Python versions 3.10.0b1, 3.9.5, 3.8.11, 3.7.11 and 3.6.14 include a fix for CVE-2022-0391: A flaw was found in Python, specifically within the urllib.parse module. The issue involves how the urlparse method does not sanitize input and allows characters like '\\r' and '\\n' in the URL path. This flaw allows an attacker to input a crafted URL, leading to injection attacks.\r\nhttps://bugs.python.org/issue43882",
            "cve": "CVE-2022-0391",
            "id": "pyup.io-45247",
            "more_info_path": "/vulnerabilities/CVE-2022-0391/45247",
            "specs": [
                "<3.6.14",
                ">=3.7.0a0,<3.7.11",
                ">=3.8.0a0,<3.8.11",
                ">=3.9.0a0,<3.9.5",
                ">=3.10.0a0,<3.10.0b1"
            ],
            "v": "<3.6.14,>=3.7.0a0,<3.7.11,>=3.8.0a0,<3.8.11,>=3.9.0a0,<3.9.5,>=3.10.0a0,<3.10.0b1"
        },
        {
            "advisory": "A flaw was found in python. An improperly handled HTTP response in the HTTP client code of python may allow a remote attacker, who controls the HTTP server, to make the client script enter an infinite loop, consuming CPU time. The highest threat from this vulnerability is to system availability.",
            "cve": "CVE-2021-3737",
            "id": "pyup.io-45703",
            "more_info_path": "/vulnerabilities/CVE-2021-3737/45703",
            "specs": [
                "<3.6.14",
                ">=3.7.0a0,<3.7.11",
                ">=3.8.0a0,<3.8.11",
                ">=3.9.0a0,<3.9.6",
                ">=3.10.0a0,<3.10.0b2"
            ],
            "v": "<3.6.14,>=3.7.0a0,<3.7.11,>=3.8.0a0,<3.8.11,>=3.9.0a0,<3.9.6,>=3.10.0a0,<3.10.0b2"
        },
        {
            "advisory": "Python 3.6.14, 3.7.11, 3.8.9 and 3.9.3 include a fix for CVE-2021-4189: The issue is how the FTP client trusts the host from the PASV response by default. This flaw allows an attacker to set up a malicious FTP server that can trick FTP clients into connecting back to a given IP address and port. This vulnerability could lead to FTP client scanning ports, which otherwise would not have been possible.\r\nhttps://python-security.readthedocs.io/vuln/ftplib-pasv.html",
            "cve": "CVE-2021-4189",
            "id": "pyup.io-50765",
            "more_info_path": "/vulnerabilities/CVE-2021-4189/50765",
            "specs": [
                "<3.6.14",
                ">=3.7.0a0,<3.7.11",
                ">=3.8.0a0,<3.8.9",
                ">=3.9.0a0,<3.9.3"
            ],
            "v": "<3.6.14,>=3.7.0a0,<3.7.11,>=3.8.0a0,<3.8.9,>=3.9.0a0,<3.9.3"
        },
        {
            "advisory": "Python versions 3.6.15, 3.7.12, 3.8.12, 3.9.7 and 3.10.0rc2 fix multiple CRLF injection vulnerabilities in smtplib.\r\nhttps://bugs.python.org/issue43124",
            "cve": "PVE-2021-42379",
            "id": "pyup.io-45705",
            "more_info_path": "/vulnerabilities/PVE-2021-42379/45705",
            "specs": [
                "<3.6.15",
                ">=3.7.0a0,<3.7.12",
                ">=3.8.0a0,<3.8.12",
                ">=3.9.0a0,<3.9.7",
                ">=3.10.0a0,<3.10.0rc2"
            ],
            "v": "<3.6.15,>=3.7.0a0,<3.7.12,>=3.8.0a0,<3.8.12,>=3.9.0a0,<3.9.7,>=3.10.0a0,<3.10.0rc2"
        },
        {
            "advisory": "An integer overflow during the parsing of XML using the Expat library. This vulnerability affects Firefox < 50.",
            "cve": "CVE-2016-9063",
            "id": "pyup.io-70521",
            "more_info_path": "/vulnerabilities/CVE-2016-9063/70521",
            "specs": [
                "<3.6.2"
            ],
            "v": "<3.6.2"
        },
        {
            "advisory": "Python versions 3.6.7 and 3.7.1 disable external entities in SAX parser to patch XML vulnerabilities.\r\nhttps://bugs.python.org/issue17239",
            "cve": "PVE-2021-42398",
            "id": "pyup.io-45706",
            "more_info_path": "/vulnerabilities/PVE-2021-42398/45706",
            "specs": [
                "<3.6.7",
                ">=3.7.0a0,<3.7.1"
            ],
            "v": "<3.6.7,>=3.7.0a0,<3.7.1"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-25314",
            "id": "pyup.io-51860",
            "more_info_path": "/vulnerabilities/CVE-2022-25314/51860",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-22825",
            "id": "pyup.io-51869",
            "more_info_path": "/vulnerabilities/CVE-2022-22825/51869",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-22827",
            "id": "pyup.io-51867",
            "more_info_path": "/vulnerabilities/CVE-2022-22827/51867",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-22826",
            "id": "pyup.io-51868",
            "more_info_path": "/vulnerabilities/CVE-2022-22826/51868",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-22824",
            "id": "pyup.io-51870",
            "more_info_path": "/vulnerabilities/CVE-2022-22824/51870",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-22823",
            "id": "pyup.io-51871",
            "more_info_path": "/vulnerabilities/CVE-2022-22823/51871",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2021-46143",
            "id": "pyup.io-51873",
            "more_info_path": "/vulnerabilities/CVE-2021-46143/51873",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-25236",
            "id": "pyup.io-51864",
            "more_info_path": "/vulnerabilities/CVE-2022-25236/51864",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-25313",
            "id": "pyup.io-51858",
            "more_info_path": "/vulnerabilities/CVE-2022-25313/51858",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-23990",
            "id": "pyup.io-51865",
            "more_info_path": "/vulnerabilities/CVE-2022-23990/51865",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-22822",
            "id": "pyup.io-51872",
            "more_info_path": "/vulnerabilities/CVE-2022-22822/51872",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2021-45960",
            "id": "pyup.io-51874",
            "more_info_path": "/vulnerabilities/CVE-2021-45960/51874",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "In Python before 3.10.3 on Windows, local users can gain privileges because the search path is inadequately secured. The installer may allow a local attacker to add user-writable directories to the system search path. To exploit, an administrator must have installed Python for all users and enabled PATH entries. A non-administrative user can trigger a repair that incorrectly adds user-writable paths into PATH, enabling search-path hijacking of other users and system services. This affects Python (CPython) through 3.7.12, 3.8.x through 3.8.12, 3.9.x through 3.9.10, and 3.10.x through 3.10.2.",
            "cve": "CVE-2022-26488",
            "id": "pyup.io-45817",
            "more_info_path": "/vulnerabilities/CVE-2022-26488/45817",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-25235",
            "id": "pyup.io-51862",
            "more_info_path": "/vulnerabilities/CVE-2022-25235/51862",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-23852",
            "id": "pyup.io-51866",
            "more_info_path": "/vulnerabilities/CVE-2022-23852/51866",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.13, 3.8.13, 3.9.11 and 3.10.3 update bundled libexpat version to v2.4.6 to include security fixes.",
            "cve": "CVE-2022-25315",
            "id": "pyup.io-51861",
            "more_info_path": "/vulnerabilities/CVE-2022-25315/51861",
            "specs": [
                "<3.7.13",
                ">=3.8.0a0,<3.8.13",
                ">=3.9.0a0,<3.9.11",
                ">=3.10.0a0,<3.10.3"
            ],
            "v": "<3.7.13,>=3.8.0a0,<3.8.13,>=3.9.0a0,<3.9.11,>=3.10.0a0,<3.10.3"
        },
        {
            "advisory": "Python 3.7.14, 3.8.14, 3.9.14 and 3.10.6 include a fix for CVE-2021-28861: Python 3.x through 3.10 has an open redirection vulnerability in lib/http/server.py due to no protection against multiple (/) at the beginning of URI path which may lead to information disclosure. \r\nNOTE: this is disputed by a third party because the http.server.html documentation page states \"Warning: http.server is not recommended for production. It only implements basic security checks.\"",
            "cve": "CVE-2021-28861",
            "id": "pyup.io-50732",
            "more_info_path": "/vulnerabilities/CVE-2021-28861/50732",
            "specs": [
                "<3.7.14",
                ">=3.8.0a0,<3.8.14",
                ">=3.9.0a0,<3.9.14",
                ">=3.10.0a0,<3.10.6"
            ],
            "v": "<3.7.14,>=3.8.0a0,<3.8.14,>=3.9.0a0,<3.9.14,>=3.10.0a0,<3.10.6"
        },
        {
            "advisory": "A flaw was found in python. In algorithms with quadratic time complexity using non-binary bases, when using int(\"text\"), a system could take 50ms to parse an int string with 100,000 digits and 5s for 1,000,000 digits (float, decimal, int.from_bytes(), and int() for binary bases 2, 4, 8, 16, and 32 are not affected). The highest threat from this vulnerability is to system availability.",
            "cve": "CVE-2020-10735",
            "id": "pyup.io-50958",
            "more_info_path": "/vulnerabilities/CVE-2020-10735/50958",
            "specs": [
                "<3.7.14",
                ">=3.8.0a0,<3.8.14",
                ">=3.9.0a0,<3.9.14",
                ">=3.10.0a0,<3.10.7",
                ">=3.11.0a0,<3.11.0rc1"
            ],
            "v": "<3.7.14,>=3.8.0a0,<3.8.14,>=3.9.0a0,<3.9.14,>=3.10.0a0,<3.10.7,>=3.11.0a0,<3.11.0rc1"
        },
        {
            "advisory": "Python 3.7.15, 3.8.15, 3.9.15 and 3.10.8 update bundled 'libexpat' version to v2.4.9 to include a security fix.",
            "cve": "CVE-2022-40674",
            "id": "pyup.io-51863",
            "more_info_path": "/vulnerabilities/CVE-2022-40674/51863",
            "specs": [
                "<3.7.15",
                ">=3.8.0a0,<3.8.15",
                ">=3.9.0a0,<3.9.15",
                ">=3.10.0a0,<3.10.8"
            ],
            "v": "<3.7.15,>=3.8.0a0,<3.8.15,>=3.9.0a0,<3.9.15,>=3.10.0a0,<3.10.8"
        },
        {
            "advisory": "Python 3.7.16, 3.8.16, 3.9.16 and 3.10.9 include a fix for CVE-2022-37454: Buffer overflow in the _sha3 module.\r\nhttps://python-security.readthedocs.io/vuln/sha3-buffer-overflow.html",
            "cve": "CVE-2022-37454",
            "id": "pyup.io-51647",
            "more_info_path": "/vulnerabilities/CVE-2022-37454/51647",
            "specs": [
                "<3.7.16",
                ">=3.8.0a0,<3.8.16",
                ">=3.9.0a0,<3.9.16",
                ">=3.10.0a0,<3.10.9"
            ],
            "v": "<3.7.16,>=3.8.0a0,<3.8.16,>=3.9.0a0,<3.9.16,>=3.10.0a0,<3.10.9"
        },
        {
            "advisory": "Python 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16 include a fix for CVE-2022-45061: An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302.\r\nhttps://github.com/python/cpython/issues/98433\r\nhttps://python-security.readthedocs.io/vuln/slow-idna-large-strings.html",
            "cve": "CVE-2022-45061",
            "id": "pyup.io-51789",
            "more_info_path": "/vulnerabilities/CVE-2022-45061/51789",
            "specs": [
                "<3.7.16",
                ">=3.8.0a0,<3.8.16",
                ">=3.9.0a0,<3.9.16",
                ">=3.10.0a0,<3.10.9",
                ">=3.11.0a0,<3.11.1"
            ],
            "v": "<3.7.16,>=3.8.0a0,<3.8.16,>=3.9.0a0,<3.9.16,>=3.10.0a0,<3.10.9,>=3.11.0a0,<3.11.1"
        },
        {
            "advisory": "Lib/zipfile.py in Python allows remote attackers to cause a denial of service (resource consumption) via a ZIP bomb.\r\nhttps://bugs.python.org/issue36260",
            "cve": "CVE-2019-9674",
            "id": "pyup.io-45621",
            "more_info_path": "/vulnerabilities/CVE-2019-9674/45621",
            "specs": [
                "<3.7.2"
            ],
            "v": "<3.7.2"
        },
        {
            "advisory": "In difflib module, table header in output of difflib.HtmlDiff.make_table is not escaped and can be rendered as code in the browser, leading potentially to XSS.\r\nhttps://bugs.python.org/issue35603\r\nhttps://github.com/python/cpython/commit/44e36e80456dabaeb59c6e2a93e0c1322bfeb179",
            "cve": "PVE-2021-42393",
            "id": "pyup.io-45612",
            "more_info_path": "/vulnerabilities/PVE-2021-42393/45612",
            "specs": [
                "<3.8"
            ],
            "v": "<3.8"
        },
        {
            "advisory": "The \u201cipaddress\u201d module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as \u201cglobally reachable\u201d or \u201cprivate\u201d. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn\u2019t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.",
            "cve": "CVE-2024-4032",
            "id": "pyup.io-71783",
            "more_info_path": "/vulnerabilities/CVE-2024-4032/71783",
            "specs": [
                "<3.8.20",
                ">=3.9.0a0,<3.9.20",
                ">=3.10.0a0,<3.10.15",
                ">=3.11.0a0,<3.11.10",
                ">=3.12.0a0,<3.12.4",
                ">=3.13.0a0,<3.13.0a6"
            ],
            "v": "<3.8.20,>=3.9.0a0,<3.9.20,>=3.10.0a0,<3.10.15,>=3.11.0a0,<3.11.10,>=3.12.0a0,<3.12.4,>=3.13.0a0,<3.13.0a6"
        },
        {
            "advisory": "Python 3.9.16, 3.10.9 and 3.11.0 include a fix for CVE-2022-42919: Python 3.9.x and 3.10.x through 3.10.8 on Linux allows local privilege escalation in a non-default configuration. The Python multiprocessing library, when used with the forkserver start method on Linux, allows pickles to be deserialized from any user in the same machine local network namespace, which in many system configurations means any user on the same machine. Pickles can execute arbitrary code. Thus, this allows for local user privilege escalation to the user that any forkserver process is running as. Setting multiprocessing.util.abstract_sockets_supported to False is a workaround. The forkserver start method for multiprocessing is not the default start method. This issue is Linux specific because only Linux supports abstract namespace sockets. CPython before 3.9 does not make use of Linux abstract namespace sockets by default. Support for users manually specifying an abstract namespace socket was added as a bugfix in 3.7.8 and 3.8.3, but users would need to make specific uncommon API calls in order to do that in CPython before 3.9.\r\nhttps://github.com/python/cpython/issues/97514",
            "cve": "CVE-2022-42919",
            "id": "pyup.io-51714",
            "more_info_path": "/vulnerabilities/CVE-2022-42919/51714",
            "specs": [
                "<3.9.16",
                ">=3.10.0a0,<3.10.9",
                ">=3.11.0a0,<3.11.0"
            ],
            "v": "<3.9.16,>=3.10.0a0,<3.10.9,>=3.11.0a0,<3.11.0"
        },
        {
            "advisory": "os._execvpe from os.py in Python 2.2.1 and earlier creates temporary files with predictable names, which could allow local users to execute arbitrary code via a symlink attack.",
            "cve": "CVE-2002-1119",
            "id": "pyup.io-61221",
            "more_info_path": "/vulnerabilities/CVE-2002-1119/61221",
            "specs": [
                "<=2.2.1"
            ],
            "v": "<=2.2.1"
        },
        {
            "advisory": "Multiple integer overflows in Python before 2.5.2 might allow context-dependent attackers to have an unknown impact via vectors related to (1) Include/pymem.h; (2) _csv.c, (3) _struct.c, (4) arraymodule.c, (5) audioop.c, (6) binascii.c, (7) cPickle.c, (8) cStringIO.c, (9) cjkcodecs/multibytecodec.c, (10) datetimemodule.c, (11) md5.c, (12) rgbimgmodule.c, and (13) stropmodule.c in Modules/; (14) bufferobject.c, (15) listobject.c, and (16) obmalloc.c in Objects/; (17) Parser/node.c; and (18) asdl.c, (19) ast.c, (20) bltinmodule.c, and (21) compile.c in Python/, as addressed by \"checks for integer overflows, contributed by Google.\"",
            "cve": "CVE-2008-3143",
            "id": "pyup.io-61293",
            "more_info_path": "/vulnerabilities/CVE-2008-3143/61293",
            "specs": [
                "<=2.5.2"
            ],
            "v": "<=2.5.2"
        },
        {
            "advisory": "Multiple buffer overflows in Python 2.5.2 and earlier on 32bit platforms allow context-dependent attackers to cause a denial of service (crash) or have unspecified other impact via a long string that leads to incorrect memory allocation during Unicode string processing, related to the unicode_resize function and the PyMem_RESIZE macro.",
            "cve": "CVE-2008-3142",
            "id": "pyup.io-61290",
            "more_info_path": "/vulnerabilities/CVE-2008-3142/61290",
            "specs": [
                "<=2.5.2"
            ],
            "v": "<=2.5.2"
        },
        {
            "advisory": "Multiple integer overflows in Python 2.5.2 and earlier allow context-dependent attackers to have an unknown impact via vectors related to the (1) stringobject, (2) unicodeobject, (3) bufferobject, (4) longobject, (5) tupleobject, (6) stropmodule, (7) gcmodule, and (8) mmapmodule modules.  NOTE: The expandtabs integer overflows in stringobject and unicodeobject in 2.5.2 are covered by CVE-2008-5031.",
            "cve": "CVE-2008-2315",
            "id": "pyup.io-61294",
            "more_info_path": "/vulnerabilities/CVE-2008-2315/61294",
            "specs": [
                "<=2.5.2"
            ],
            "v": "<=2.5.2"
        },
        {
            "advisory": "Multiple integer overflows in the PyOS_vsnprintf function in Python/mysnprintf.c in Python 2.5.2 and earlier allow context-dependent attackers to cause a denial of service (memory corruption) or have unspecified other impact via crafted input to string formatting operations.  NOTE: the handling of certain integer values is also affected by related integer underflows and an off-by-one error.",
            "cve": "CVE-2008-3144",
            "id": "pyup.io-61292",
            "more_info_path": "/vulnerabilities/CVE-2008-3144/61292",
            "specs": [
                "<=2.5.2"
            ],
            "v": "<=2.5.2"
        },
        {
            "advisory": "Untrusted search path vulnerability in the PySys_SetArgv API function in Python 2.6 and earlier, and possibly later versions, prepends an empty string to sys.path when the argv[0] argument does not contain a path separator, which might allow local users to execute arbitrary code via a Trojan horse Python file in the current working directory.",
            "cve": "CVE-2008-5983",
            "id": "pyup.io-61224",
            "more_info_path": "/vulnerabilities/CVE-2008-5983/61224",
            "specs": [
                "<=2.6.6",
                ">=3.1.0,<3.1.3"
            ],
            "v": "<=2.6.6,>=3.1.0,<3.1.3"
        },
        {
            "advisory": "The MSI installer for Python through 2.7.16 on Windows defaults to the C:\\Python27 directory, which makes it easier for local users to deploy Trojan horse code: a privilege escalation vulnerability. This issue also affects old 3.x releases before 3.5.\r\nNOTE: the vendor's position is that it is the user's responsibility to ensure C:\\Python27 access control or choose a different directory because backwards compatibility requires that C:\\Python27 remain the default for 2.7.x.",
            "cve": "CVE-2019-13404",
            "id": "pyup.io-70573",
            "more_info_path": "/vulnerabilities/CVE-2019-13404/70573",
            "specs": [
                "<=2.7.16",
                ">=3.0.0,<3.5.0"
            ],
            "v": "<=2.7.16,>=3.0.0,<3.5.0"
        },
        {
            "advisory": "Untrusted search path vulnerability in python.exe in Python through 3.5.0 on Windows allows local users to gain privileges via a Trojan horse readline.pyd file in the current working directory.  NOTE: the vendor says \"It was determined that this is a longtime behavior of Python that cannot really be altered at this point.\"",
            "cve": "CVE-2015-5652",
            "id": "pyup.io-70413",
            "more_info_path": "/vulnerabilities/CVE-2015-5652/70413",
            "specs": [
                "<=3.5.0"
            ],
            "v": "<=3.5.0"
        },
        {
            "advisory": "Stack-based buffer overflow in the file_compress function in minigzip (Modules/zlib) in Python 2.5 allows context-dependent attackers to execute arbitrary code via a long file argument.",
            "cve": "CVE-2007-1657",
            "id": "pyup.io-61222",
            "more_info_path": "/vulnerabilities/CVE-2007-1657/61222",
            "specs": [
                "==2.5"
            ],
            "v": "==2.5"
        },
        {
            "advisory": "Python 3.12.0a7, as downloaded from Github repository after commit 13f942ac16ef53d2c7add6f299eddcaf9ad0dda5, was discovered to contain a heap use-after-free via the function ascii_decode at /Objects/unicodeobject.c.\r\nhttps://github.com/python/cpython/issues/103824",
            "cve": "CVE-2023-33595",
            "id": "pyup.io-58960",
            "more_info_path": "/vulnerabilities/CVE-2023-33595/58960",
            "specs": [
                "==3.12.0a7"
            ],
            "v": "==3.12.0a7"
        },
        {
            "advisory": "Python Software Foundation CPython version From 3.2 until 3.6.4 on Windows contains a Buffer Overflow vulnerability in os.symlink() function on Windows that can result in Arbitrary code execution, likely escalation of privilege. This attack appears to be exploitable via a python script that creates a symlink with an attacker controlled name or location. This vulnerability appears to have been fixed in 3.7.0 and 3.6.5.",
            "cve": "CVE-2018-1000117",
            "id": "pyup.io-70750",
            "more_info_path": "/vulnerabilities/CVE-2018-1000117/70750",
            "specs": [
                "==3.7.0",
                ">=3.2.0,<3.4.9",
                ">=3.5.0,<3.5.6",
                ">=3.6.0,<3.6.5"
            ],
            "v": "==3.7.0,>=3.2.0,<3.4.9,>=3.5.0,<3.5.6,>=3.6.0,<3.6.5"
        },
        {
            "advisory": "This is a dummy vulnerability only.",
            "cve": "CVE-2023-0593",
            "id": "pyup.io-63025",
            "more_info_path": "/vulnerabilities/CVE-2023-0593/63025",
            "specs": [
                ">201.1.1"
            ],
            "v": ">201.1.1"
        },
        {
            "advisory": "The e-mail module of Python 0 - 2.7.18, 3.x - 3.11 incorrectly parses e-mail addresses that contain a special character. This vulnerability allows attackers to send messages from e-mail addresses that would otherwise be rejected.\r\nhttps://github.com/python/cpython/issues/102988\r\nhttps://python-security.readthedocs.io/vuln/email-parseaddr-realname.html",
            "cve": "CVE-2023-27043",
            "id": "pyup.io-55080",
            "more_info_path": "/vulnerabilities/CVE-2023-27043/55080",
            "specs": [
                ">3.0,<3.11.3",
                "<2.7.18"
            ],
            "v": ">3.0,<3.11.3,<2.7.18"
        },
        {
            "advisory": "Multiple integer overflows in imageop.c in the imageop module in Python 1.5.2 through 2.5.1 allow context-dependent attackers to break out of the Python VM and execute arbitrary code via large integer values in certain arguments to the crop function, leading to a buffer overflow, a different vulnerability than CVE-2007-4965 and CVE-2008-1679.",
            "cve": "CVE-2008-4864",
            "id": "pyup.io-61291",
            "more_info_path": "/vulnerabilities/CVE-2008-4864/61291",
            "specs": [
                ">=1.5.2,<2.5.3"
            ],
            "v": ">=1.5.2,<2.5.3"
        },
        {
            "advisory": "Multiple integer overflows in the imageop module in Python 2.5.1 and earlier allow context-dependent attackers to cause a denial of service (application crash) and possibly obtain sensitive information (memory contents) via crafted arguments to (1) the tovideo method, and unspecified other vectors related to (2) imageop.c, (3) rbgimgmodule.c, and other files, which trigger heap-based buffer overflows.",
            "cve": "CVE-2007-4965",
            "id": "pyup.io-61261",
            "more_info_path": "/vulnerabilities/CVE-2007-4965/61261",
            "specs": [
                ">=1.5.2,<=2.5.1"
            ],
            "v": ">=1.5.2,<=2.5.1"
        },
        {
            "advisory": "Integer overflow in _hashopenssl.c in the hashlib module in Python 2.5.2 and earlier might allow context-dependent attackers to defeat cryptographic digests, related to \"partial hashlib hashing of data exceeding 4GB.\"",
            "cve": "CVE-2008-2316",
            "id": "pyup.io-61223",
            "more_info_path": "/vulnerabilities/CVE-2008-2316/61223",
            "specs": [
                ">=1.5.2,<=2.5.2"
            ],
            "v": ">=1.5.2,<=2.5.2"
        },
        {
            "advisory": "The SimpleXMLRPCServer library module in Python 2.2, 2.3 before 2.3.5, and 2.4, when used by XML-RPC servers that use the register_instance method to register an object without a _dispatch method, allows remote attackers to read or modify globals of the associated module, and possibly execute arbitrary code, via dotted attributes.",
            "cve": "CVE-2005-0089",
            "id": "pyup.io-61218",
            "more_info_path": "/vulnerabilities/CVE-2005-0089/61218",
            "specs": [
                ">=2.2,<2.3.5",
                ">2.3.5,<=2.4"
            ],
            "v": ">=2.2,<2.3.5,>2.3.5,<=2.4"
        },
        {
            "advisory": "Buffer overflow in the getaddrinfo function in Python 2.2 before 2.2.2, when IPv6 support is disabled, allows remote attackers to execute arbitrary code via an IPv6 address that is obtained using DNS.",
            "cve": "CVE-2004-0150",
            "id": "pyup.io-61219",
            "more_info_path": "/vulnerabilities/CVE-2004-0150/61219",
            "specs": [
                ">=2.2,<=2.2.1"
            ],
            "v": ">=2.2,<=2.2.1"
        },
        {
            "advisory": "Stack-based buffer overflow in Python 2.4.2 and earlier, running on Linux 2.6.12.5 under gcc 4.0.3 with libc 2.3.5, allows local users to cause a \"stack overflow,\" and possibly gain privileges, by running a script from a current working directory that has a long name, related to the realpath function.  NOTE: this might not be a vulnerability. However, the fact that it appears in a programming language interpreter could mean that some applications are affected, although attack scenarios might be limited because the attacker might already need to cross privilege boundaries to cause an exploitable program to be placed in a directory with a long name; or, depending on the method that Python uses to determine the current working directory, setuid applications might be affected.",
            "cve": "CVE-2006-1542",
            "id": "pyup.io-61220",
            "more_info_path": "/vulnerabilities/CVE-2006-1542/61220",
            "specs": [
                ">=2.4,<=2.4.2"
            ],
            "v": ">=2.4,<=2.4.2"
        },
        {
            "advisory": "Off-by-one error in the PyLocale_strxfrm function in Modules/_localemodule.c for Python 2.4 and 2.5 causes an incorrect buffer size to be used for the strxfrm function, which allows context-dependent attackers to read portions of memory via unknown manipulations that trigger a buffer over-read due to missing null termination.",
            "cve": "CVE-2007-2052",
            "id": "pyup.io-61295",
            "more_info_path": "/vulnerabilities/CVE-2007-2052/61295",
            "specs": [
                ">=2.4,<=2.5"
            ],
            "v": ">=2.4,<=2.5"
        },
        {
            "advisory": "Python 2.5.6c1, 2.6.7rc2, 2.7.2, 3.2.4 and 3.3.1 include a fix for CVE-2011-4940: The list_directory function in Lib/SimpleHTTPServer.py in SimpleHTTPServer in Python before 2.5.6c1, 2.6.x before 2.6.7 rc2, and 2.7.x before 2.7.2 does not place a charset parameter in the Content-Type HTTP header, which makes it easier for remote attackers to conduct cross-site scripting (XSS) attacks against Internet Explorer 7 via UTF-7 encoding.\r\nhttps://python-security.readthedocs.io/vuln/simplehttpserver-utf-7.html",
            "cve": "CVE-2011-4940",
            "id": "pyup.io-45718",
            "more_info_path": "/vulnerabilities/CVE-2011-4940/45718",
            "specs": [
                ">=2.6,<2.6.7",
                "<2.5.6c1",
                ">=2.7,<2.7.2",
                ">=3.0.0a0,<3.2.4",
                ">=3.3.0a0,<3.3.1"
            ],
            "v": ">=2.6,<2.6.7,<2.5.6c1,>=2.7,<2.7.2,>=3.0.0a0,<3.2.4,>=3.3.0a0,<3.3.1"
        },
        {
            "advisory": "The XML parser (xmlparse.c) in expat before 2.1.0 computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via an XML file with many identifiers with the same value.",
            "cve": "CVE-2012-0876",
            "id": "pyup.io-70616",
            "more_info_path": "/vulnerabilities/CVE-2012-0876/70616",
            "specs": [
                ">=2.6.0,<2.6.8",
                ">=2.7.0,<2.7.3",
                ">=3.1.0,<3.1.5",
                ">=3.2.0,<3.2.3"
            ],
            "v": ">=2.6.0,<2.6.8,>=2.7.0,<2.7.3,>=3.1.0,<3.1.5,>=3.2.0,<3.2.3"
        },
        {
            "advisory": "Python 2.6 through 3.2 creates ~/.pypirc with world-readable permissions before changing them after data has been written, which introduces a race condition that allows local users to obtain a username and password by reading this file. See CVE-2011-4944.",
            "cve": "CVE-2011-4944",
            "id": "pyup.io-45644",
            "more_info_path": "/vulnerabilities/CVE-2011-4944/45644",
            "specs": [
                ">=2.6.0a0,<2.7.3",
                ">=3.0.0a0,<3.3"
            ],
            "v": ">=2.6.0a0,<2.7.3,>=3.0.0a0,<3.3"
        },
        {
            "advisory": "Python before 2.6.8, 2.7.x before 2.7.3, 3.x before 3.1.5, and 3.2.x before 3.2.3 computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. See CVE-2012-1150.",
            "cve": "CVE-2012-1150",
            "id": "pyup.io-45652",
            "more_info_path": "/vulnerabilities/CVE-2012-1150/45652",
            "specs": [
                ">=2.7,<2.7.3",
                ">=3.0,<3.1.5",
                ">=3.2,<3.2.3",
                "<2.6.8"
            ],
            "v": ">=2.7,<2.7.3,>=3.0,<3.1.5,>=3.2,<3.2.3,<2.6.8"
        },
        {
            "advisory": "SimpleXMLRPCServer.py in SimpleXMLRPCServer in Python before 2.6.8, 2.7.x before 2.7.3, 3.x before 3.1.5, and 3.2.x before 3.2.3 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via an XML-RPC POST request that contains a smaller amount of data than specified by the Content-Length header. See CVE-2012-0845.",
            "cve": "CVE-2012-0845",
            "id": "pyup.io-45710",
            "more_info_path": "/vulnerabilities/CVE-2012-0845/45710",
            "specs": [
                ">=2.7,<2.7.3",
                ">=3.2,<3.2.3",
                ">=3.1,<3.1.5",
                "<2.6.8"
            ],
            "v": ">=2.7,<2.7.3,>=3.2,<3.2.3,>=3.1,<3.1.5,<2.6.8"
        },
        {
            "advisory": "Multiple integer overflows in the XML_GetBuffer function in Expat through 2.1.0, as used in Google Chrome before 44.0.2403.89 and other products, allow remote attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact via crafted XML data, a related issue to CVE-2015-2716.",
            "cve": "CVE-2015-1283",
            "id": "pyup.io-70615",
            "more_info_path": "/vulnerabilities/CVE-2015-1283/70615",
            "specs": [
                ">=2.7.0,<2.7.12",
                ">=3.3.0,<3.3.7",
                ">=3.4.0,<3.4.5",
                ">=3.5.0,<3.5.2"
            ],
            "v": ">=2.7.0,<2.7.12,>=3.3.0,<3.3.7,>=3.4.0,<3.4.5,>=3.5.0,<3.5.2"
        },
        {
            "advisory": "XML External Entity vulnerability in libexpat 2.2.0 and earlier (Expat XML Parser Library) allows attackers to put the parser in an infinite loop using a malformed external entity definition from an external DTD.",
            "cve": "CVE-2017-9233",
            "id": "pyup.io-70736",
            "more_info_path": "/vulnerabilities/CVE-2017-9233/70736",
            "specs": [
                ">=2.7.0,<2.7.15",
                ">=3.3.0,<3.3.7",
                ">=3.4.0,<3.4.7",
                ">=3.5.0,<3.5.4",
                ">=3.6.0,<3.6.2"
            ],
            "v": ">=2.7.0,<2.7.15,>=3.3.0,<3.3.7,>=3.4.0,<3.4.7,>=3.5.0,<3.5.4,>=3.6.0,<3.6.2"
        },
        {
            "advisory": "OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCipherSpec messages, which allows man-in-the-middle attackers to trigger use of a zero-length master key in certain OpenSSL-to-OpenSSL communications, and consequently hijack sessions or obtain sensitive information, via a crafted TLS handshake, aka the \"CCS Injection\" vulnerability.",
            "cve": "CVE-2014-0224",
            "id": "pyup.io-70622",
            "more_info_path": "/vulnerabilities/CVE-2014-0224/70622",
            "specs": [
                ">=2.7.0,<2.7.8",
                ">=3.4.0,<3.4.2"
            ],
            "v": ">=2.7.0,<2.7.8,>=3.4.0,<3.4.2"
        },
        {
            "advisory": "Python 3.3.4rc1 includes a fix for CVE-2013-7338: Python before 3.3.4 RC1 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a file size value larger than the size of the zip file to the (1) ZipExtFile.read, (2) ZipExtFile.read(n), (3) ZipExtFile.readlines, (4) ZipFile.extract, or (5) ZipFile.extractall function.\r\nhttps://bugs.python.org/issue20078",
            "cve": "CVE-2013-7338",
            "id": "pyup.io-45649",
            "more_info_path": "/vulnerabilities/CVE-2013-7338/45649",
            "specs": [
                ">=3.0.0a0,<3.3.4rc1"
            ],
            "v": ">=3.0.0a0,<3.3.4rc1"
        },
        {
            "advisory": "Python versions 3.4.10, 3.5.7, 3.6.7 and 3.7.1 include a fix for CVE-2018-20406: Modules/_pickle.c in Python before 3.7.1 has an integer overflow via a large LONG_BINPUT value that is mishandled during a \"resize to twice the size\" attempt. This issue might cause memory exhaustion, but is only relevant if the pickle format is used for serializing tens or hundreds of gigabytes of data.\r\nhttps://bugs.python.org/issue34656",
            "cve": "CVE-2018-20406",
            "id": "pyup.io-45695",
            "more_info_path": "/vulnerabilities/CVE-2018-20406/45695",
            "specs": [
                ">=3.0.0a0,<3.4.10",
                ">=3.5.0a0,<3.5.7",
                ">=3.6.0a0,<3.6.7",
                ">=3.7.0a0,<3.7.1"
            ],
            "v": ">=3.0.0a0,<3.4.10,>=3.5.0a0,<3.5.7,>=3.6.0a0,<3.6.7,>=3.7.0a0,<3.7.1"
        },
        {
            "advisory": "Python versions 2.7.17, 3.5.8, 3.6.10 and 3.7.5 include a fix for CVE-2019-16056: An issue was discovered in Python through 2.7.16, 3.x through 3.5.7, 3.6.x through 3.6.9, and 3.7.x through 3.7.4. The email module wrongly parses email addresses that contain multiple @ characters. An application that uses the email module and implements some kind of checks on the From/To headers of a message could be tricked into accepting an email address that should be denied. An attack may be the same as in CVE-2019-11340; however, this CVE applies to Python more generally.\r\nhttps://bugs.python.org/issue34155",
            "cve": "CVE-2019-16056",
            "id": "pyup.io-45683",
            "more_info_path": "/vulnerabilities/CVE-2019-16056/45683",
            "specs": [
                ">=3.0.0a0,<3.5.8",
                ">=3.6.0a0,<3.6.10",
                ">=3.7.0a0,<3.7.5",
                "<2.7.17"
            ],
            "v": ">=3.0.0a0,<3.5.8,>=3.6.0a0,<3.6.10,>=3.7.0a0,<3.7.5,<2.7.17"
        },
        {
            "advisory": "Python 3.6.13, 3.7.10, 3.8.7, 3.9.1 and 3.10.0a2 include a fix for CVE-2020-27619: In Python 3 through 3.9.0, the Lib/test/multibytecodec_support.py CJK codec tests call eval() on content retrieved via HTTP.\r\nhttps://python-security.readthedocs.io/vuln/cjk-codec-download-eval.html",
            "cve": "CVE-2020-27619",
            "id": "pyup.io-45701",
            "more_info_path": "/vulnerabilities/CVE-2020-27619/45701",
            "specs": [
                ">=3.0.0a0,<3.6.13",
                ">=3.7.0a0,<3.7.10",
                ">=3.8.0a0,<3.8.7",
                ">=3.9.0a0,<3.9.1",
                ">=3.10.0a0,<3.10.0a2"
            ],
            "v": ">=3.0.0a0,<3.6.13,>=3.7.0a0,<3.7.10,>=3.8.0a0,<3.8.7,>=3.9.0a0,<3.9.1,>=3.10.0a0,<3.10.0a2"
        },
        {
            "advisory": "The utf-16 decoder in Python 3.1 through 3.3 does not update the aligned_end variable after calling the unicode_decode_call_errorhandler function, which allows remote attackers to obtain sensitive information (process memory) or cause a denial of service (memory corruption and crash) via unspecified vectors.",
            "cve": "CVE-2012-2135",
            "id": "pyup.io-45722",
            "more_info_path": "/vulnerabilities/CVE-2012-2135/45722",
            "specs": [
                ">=3.1,<3.4"
            ],
            "v": ">=3.1,<3.4"
        },
        {
            "advisory": "Use-after-free vulnerability in bzip2recover in bzip2 1.0.6 allows remote attackers to cause a denial of service (crash) via a crafted bzip2 file, related to block ends set to before the start of the block.",
            "cve": "CVE-2016-3189",
            "id": "pyup.io-70617",
            "more_info_path": "/vulnerabilities/CVE-2016-3189/70617",
            "specs": [
                ">=3.10.0,<3.10.3",
                ">=3.7.0,<3.7.13",
                ">=3.8.0,<3.8.13",
                ">=3.9.0,<3.9.11"
            ],
            "v": ">=3.10.0,<3.10.3,>=3.7.0,<3.7.13,>=3.8.0,<3.8.13,>=3.9.0,<3.9.11"
        },
        {
            "advisory": "Python 3.8.12, 3.9.5 and 3.10.0 include a fix for CVE-2021-29921: In Python before 3.9.5, the ipaddress library mishandles leading zero characters in the octets of an IP address string. This (in some situations) allows attackers to bypass access control that is based on IP addresses.\r\nhttps://python-security.readthedocs.io/vuln/ipaddress-ipv4-leading-zeros.html",
            "cve": "CVE-2021-29921",
            "id": "pyup.io-45614",
            "more_info_path": "/vulnerabilities/CVE-2021-29921/45614",
            "specs": [
                ">=3.10.0a0,<3.10.0",
                ">=3.9.0a0,<3.9.5",
                ">=3.8.0a0,<3.8.12"
            ],
            "v": ">=3.10.0a0,<3.10.0,>=3.9.0a0,<3.9.5,>=3.8.0a0,<3.8.12"
        },
        {
            "advisory": "Python 3.7.17, 3.8.17, 3.9.17, 3.10.12 and 3.11.4 include a fix for CVE-2023-24329: An issue in the urllib.parse component of Python before 3.11.4 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters.\r\nhttps://github.com/python/cpython/issues/102153\r\nhttps://pointernull.com/security/python-url-parse-problem.html",
            "cve": "CVE-2023-24329",
            "id": "pyup.io-53376",
            "more_info_path": "/vulnerabilities/CVE-2023-24329/53376",
            "specs": [
                ">=3.10.0a0,<3.10.12",
                ">=3.11.0a0,<3.11.4",
                ">=3.9.0a0,<3.9.17",
                ">=3.8.0a0,<3.8.17",
                "<3.7.17"
            ],
            "v": ">=3.10.0a0,<3.10.12,>=3.11.0a0,<3.11.4,>=3.9.0a0,<3.9.17,>=3.8.0a0,<3.8.17,<3.7.17"
        },
        {
            "advisory": "An issue was found in the CPython `tempfile.TemporaryDirectory` class affecting versions 3.12.1, 3.11.7, 3.10.13, 3.9.18, and 3.8.18 and prior. The tempfile.TemporaryDirectory class would dereference symlinks during cleanup of permissions-related errors. This means users which can run privileged programs are potentially able to modify permissions of files referenced by symlinks in some circumstances.",
            "cve": "CVE-2023-6597",
            "id": "pyup.io-66949",
            "more_info_path": "/vulnerabilities/CVE-2023-6597/66949",
            "specs": [
                ">=3.10.0a1,<=3.10.13",
                ">=3.9.0a1,<=3.9.18",
                ">=0,<=3.8.18",
                ">=3.12.0a1,<3.12.2",
                ">=3.11.0a1,<3.11.8"
            ],
            "v": ">=3.10.0a1,<=3.10.13,>=3.9.0a1,<=3.9.18,>=0,<=3.8.18,>=3.12.0a1,<3.12.2,>=3.11.0a1,<3.11.8"
        },
        {
            "advisory": "An issue was found in the CPython `zipfile` module affecting versions 3.12.1, 3.11.7, 3.10.13, 3.9.18, and 3.8.18 and prior. The zipfile module is vulnerable to \u201cquoted-overlap\u201d zip-bombs which exploit the zip format to create a zip-bomb with a high compression ratio. The fixed versions of CPython makes the zipfile module reject zip archives which overlap entries in the archive.",
            "cve": "CVE-2024-0450",
            "id": "pyup.io-66951",
            "more_info_path": "/vulnerabilities/CVE-2024-0450/66951",
            "specs": [
                ">=3.10.0a1,<=3.10.13",
                ">=3.9.0a1,<=3.9.18",
                ">=0,<=3.8.18",
                ">=3.12.0a1,<3.12.2",
                ">=3.11.0a1,<3.11.8"
            ],
            "v": ">=3.10.0a1,<=3.10.13,>=3.9.0a1,<=3.9.18,>=0,<=3.8.18,>=3.12.0a1,<3.12.2,>=3.11.0a1,<3.11.8"
        },
        {
            "advisory": "Python 3.7.16, 3.8.16, 3.9.16, 3.10.6 and 3.11.0b4 include a fix for CVE-2015-20107: The mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments).\r\nhttps://python-security.readthedocs.io/vuln/mailcap-shell-injection.html",
            "cve": "CVE-2015-20107",
            "id": "pyup.io-48131",
            "more_info_path": "/vulnerabilities/CVE-2015-20107/48131",
            "specs": [
                ">=3.11.0a0,<3.11.0b4",
                "<3.7.16",
                ">=3.8.0a0,<3.8.16",
                ">=3.9.0a0,<3.9.16",
                ">=3.10.0a0,<3.10.6"
            ],
            "v": ">=3.11.0a0,<3.11.0b4,<3.7.16,>=3.8.0a0,<3.8.16,>=3.9.0a0,<3.9.16,>=3.10.0a0,<3.10.6"
        },
        {
            "advisory": "An issue was discovered in Python 3.11 through 3.11.4. If a path containing '\\0' bytes is passed to os.path.normpath(), the path will be truncated unexpectedly at the first '\\0' byte. There are plausible cases in which an application would have rejected a filename for security reasons in Python 3.10.x or earlier, but that filename is no longer rejected in Python 3.11.x.\r\nhttps://github.com/python/cpython/issues/106242\r\nhttps://github.com/advisories/GHSA-65fx-pmw6-rcfm",
            "cve": "CVE-2023-41105",
            "id": "pyup.io-60640",
            "more_info_path": "/vulnerabilities/CVE-2023-41105/60640",
            "specs": [
                ">=3.11.0a1,<3.11.4"
            ],
            "v": ">=3.11.0a1,<3.11.4"
        },
        {
            "advisory": "Python 3.8.18, 3.9.18, 3.10.13, 3.11.5 and 3.12.0rc2 include a fix for CVE-2023-40217: It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as \"not connected\" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.\r\nhttps://github.com/python/cpython/issues/108310\r\nhttps://mail.python.org/archives/list/security-announce@python.org/thread/PEPLII27KYHLF4AK3ZQGKYNCRERG4YXY",
            "cve": "CVE-2023-40217",
            "id": "pyup.io-60680",
            "more_info_path": "/vulnerabilities/CVE-2023-40217/60680",
            "specs": [
                ">=3.12.0a1,<=3.12.0rc1",
                ">=3.11.0a1,<3.11.5",
                ">=3.10.0a1,<3.10.13",
                ">=3.9.0a1,<3.9.18",
                "<3.8.18"
            ],
            "v": ">=3.12.0a1,<=3.12.0rc1,>=3.11.0a1,<3.11.5,>=3.10.0a1,<3.10.13,>=3.9.0a1,<3.9.18,<3.8.18"
        },
        {
            "advisory": "Python versions 3.2.5, 3.3.6, 3.4.2 and 3.5.0 include a fix for CVE-2014-2667: Race condition in the _get_masked_mode function in Lib/os.py in Python 3.2 through 3.5, when exist_ok is set to true and multiple threads are used, might allow local users to bypass intended file permissions by leveraging a separate application vulnerability before the umask has been set to the expected value.\r\nhttps://bugs.python.org/issue21082",
            "cve": "CVE-2014-2667",
            "id": "pyup.io-45694",
            "more_info_path": "/vulnerabilities/CVE-2014-2667/45694",
            "specs": [
                ">=3.2.0a0,<3.2.5",
                ">=3.3.0a0,<3.3.6",
                ">=3.4.0a0,<3.4.2",
                ">=3.5.0a0,<3.5.0"
            ],
            "v": ">=3.2.0a0,<3.2.5,>=3.3.0a0,<3.3.6,>=3.4.0a0,<3.4.2,>=3.5.0a0,<3.5.0"
        },
        {
            "advisory": "Algorithmic complexity vulnerability in the ssl.match_hostname function in Python 3.2.x, 3.3.x, and earlier, and unspecified versions of python-backports-ssl_match_hostname as used for older Python versions, allows remote attackers to cause a denial of service (CPU consumption) via multiple wildcard characters in the common name in a certificate.",
            "cve": "CVE-2013-2099",
            "id": "pyup.io-45693",
            "more_info_path": "/vulnerabilities/CVE-2013-2099/45693",
            "specs": [
                ">=3.3.0a0,<3.3.3",
                "<3.2.6"
            ],
            "v": ">=3.3.0a0,<3.3.3,<3.2.6"
        },
        {
            "advisory": "Python 3.4.7 and 3.5.3 remove 3DES from SSL default ciphers list, as it is vulnerable to CVE-2016-2183: The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted session, as demonstrated by an HTTPS session using Triple DES in CBC mode, aka a \"Sweet32\" attack.\r\nhttps://github.com/vstinner/cpython/commit/03d13c0cbfe912eb0f9b9a02987b9e569f25fe19",
            "cve": "CVE-2016-2183",
            "id": "pyup.io-45716",
            "more_info_path": "/vulnerabilities/CVE-2016-2183/45716",
            "specs": [
                ">=3.5.0a0,<3.5.3",
                "<3.4.7"
            ],
            "v": ">=3.5.0a0,<3.5.3,<3.4.7"
        },
        {
            "advisory": "Python versions 3.6.13, 3.7.10, 3.8.9, 3.9.3 and 3.10.0a7 include a fix for CVE-2021-3426: There's a flaw in Python 3's pydoc. A local or adjacent attacker who discovers or is able to convince another local or adjacent user to start a pydoc server could access the server and use it to disclose sensitive information belonging to the other user that they would not normally be able to access. The highest risk of this flaw is to data confidentiality.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1935913\r\nhttps://bugs.python.org/issue42988",
            "cve": "CVE-2021-3426",
            "id": "pyup.io-45723",
            "more_info_path": "/vulnerabilities/CVE-2021-3426/45723",
            "specs": [
                ">=3.6.0,<3.6.13",
                ">=3.7.0,<3.7.10",
                ">=3.8.0,<3.8.9",
                ">=3.9.0,<3.9.3",
                ">=3.10.0a0,<3.10.0a7"
            ],
            "v": ">=3.6.0,<3.6.13,>=3.7.0,<3.7.10,>=3.8.0,<3.8.9,>=3.9.0,<3.9.3,>=3.10.0a0,<3.10.0a7"
        },
        {
            "advisory": "expat 2.1.0 and earlier does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE.",
            "cve": "CVE-2013-0340",
            "id": "pyup.io-70601",
            "more_info_path": "/vulnerabilities/CVE-2013-0340/70601",
            "specs": [
                ">=3.6.0,<3.6.15",
                ">=3.7.0,<3.7.12",
                ">=3.8.0,<3.8.12",
                ">=3.9.0,<3.9.7"
            ],
            "v": ">=3.6.0,<3.6.15,>=3.7.0,<3.7.12,>=3.8.0,<3.8.12,>=3.9.0,<3.9.7"
        },
        {
            "advisory": "In Python (CPython) 3.6 through 3.6.10, 3.7 through 3.7.6, and 3.8 through 3.8.1, an insecure dependency load upon launch on Windows 7 may result in an attacker's copy of api-ms-win-core-path-l1-1-0.dll being loaded and used instead of the system's copy. Windows 8 and later are unaffected.",
            "cve": "CVE-2020-8315",
            "id": "pyup.io-70586",
            "more_info_path": "/vulnerabilities/CVE-2020-8315/70586",
            "specs": [
                ">=3.6.0,<=3.6.10",
                ">=3.7.0,<=3.7.6",
                ">=3.8.0,<=3.8.1"
            ],
            "v": ">=3.6.0,<=3.6.10,>=3.7.0,<=3.7.6,>=3.8.0,<=3.8.1"
        },
        {
            "advisory": "Python 2.7 through 2.7.17, 3.5 through 3.5.9, 3.6 through 3.6.10, 3.7 through 3.7.6, and 3.8 through 3.8.1 allows an HTTP server to conduct Regular Expression Denial of Service (ReDoS) attacks against a client because of urllib.request.AbstractBasicAuthHandler catastrophic backtracking.",
            "cve": "CVE-2020-8492",
            "id": "pyup.io-45696",
            "more_info_path": "/vulnerabilities/CVE-2020-8492/45696",
            "specs": [
                ">=3.6.0a0,<3.6.11",
                ">=3.7.0a0,<3.7.7",
                ">=3.8.0a0,<3.8.2",
                ">=3.9.0a0,<3.9.0a6",
                "<2.7.17",
                ">=3.0.0a0,<3.5.10"
            ],
            "v": ">=3.6.0a0,<3.6.11,>=3.7.0a0,<3.7.7,>=3.8.0a0,<3.8.2,>=3.9.0a0,<3.9.0a6,<2.7.17,>=3.0.0a0,<3.5.10"
        },
        {
            "advisory": "Python versions 3.6.13, 3.7.10, 3.8.8 and 3.9.2 include a fix for CVE-2021-23336: The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to Web Cache Poisoning via urllib.parse.parse_qsl and urllib.parse.parse_qs by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter.\r\nhttps://bugs.python.org/issue42967\r\nhttps://github.com/python/cpython/pull/24297",
            "cve": "CVE-2021-23336",
            "id": "pyup.io-45719",
            "more_info_path": "/vulnerabilities/CVE-2021-23336/45719",
            "specs": [
                ">=3.7.0,<3.7.10",
                ">=3.8.0,<3.8.8",
                ">=3.9.0,<3.9.2",
                "<3.6.13"
            ],
            "v": ">=3.7.0,<3.7.10,>=3.8.0,<3.8.8,>=3.9.0,<3.9.2,<3.6.13"
        },
        {
            "advisory": "Python 3.x through 3.9.1 has a buffer overflow in PyCArg_repr in _ctypes/callproc.c, which may lead to remote code execution in certain Python applications that accept floating-point numbers as untrusted input, as demonstrated by a 1e300 argument to c_double.from_param. This occurs because sprintf is used unsafely.",
            "cve": "CVE-2021-3177",
            "id": "pyup.io-45651",
            "more_info_path": "/vulnerabilities/CVE-2021-3177/45651",
            "specs": [
                ">=3.7.0,<3.7.10",
                ">=3.8.0,<3.8.8",
                ">=3.9.0,<3.9.2",
                ">=3.0.0a0,<3.6.13"
            ],
            "v": ">=3.7.0,<3.7.10,>=3.8.0,<3.8.8,>=3.9.0,<3.9.2,>=3.0.0a0,<3.6.13"
        },
        {
            "advisory": "In Python 3.8.4, sys.path restrictions specified in a python38._pth file are ignored, allowing code to be loaded from arbitrary locations. The ._pth file (e.g., the python._pth file) is not affected.",
            "cve": "CVE-2020-15801",
            "id": "pyup.io-70751",
            "more_info_path": "/vulnerabilities/CVE-2020-15801/70751",
            "specs": [
                ">=3.7.0,<3.7.9",
                ">=3.8.0,<3.8.5"
            ],
            "v": ">=3.7.0,<3.7.9,>=3.8.0,<3.8.5"
        },
        {
            "advisory": "Python version 3.7.0b3 hardens ssl module against CVE-2018-8970.\r\nhttps://bugs.python.org/issue33136",
            "cve": "CVE-2018-8970",
            "id": "pyup.io-45658",
            "more_info_path": "/vulnerabilities/CVE-2018-8970/45658",
            "specs": [
                ">=3.7.0a0,<3.7.0b3"
            ],
            "v": ">=3.7.0a0,<3.7.0b3"
        },
        {
            "advisory": "Python 3.6.13, 3.7.10, 3.8.7 and 3.9.1 include a fix for CVE-2022-48565: XML External Entity vulnerability. The plistlib module no longer accepts entity declarations in XML plist files to avoid XML vulnerabilities.\r\nhttps://bugs.python.org/issue42051",
            "cve": "CVE-2022-48565",
            "id": "pyup.io-60630",
            "more_info_path": "/vulnerabilities/CVE-2022-48565/60630",
            "specs": [
                ">=3.7.0a1,<3.7.10",
                "==3.10.0a1",
                "<3.6.13",
                ">=3.8.0a1,<3.8.7",
                ">=3.9.0a1,<3.9.1"
            ],
            "v": ">=3.7.0a1,<3.7.10,==3.10.0a1,<3.6.13,>=3.8.0a1,<3.8.7,>=3.9.0a1,<3.9.1"
        },
        {
            "advisory": "Python 3.6.13, 3.7.10, 3.8.7, 3.9.1 and 3.10.0a3 include a fix for CVE-2022-48566: Observable Timing Discrepancy vulnerability in compare_digest in Lib/hmac.py. The fix includes constant-time-defeating optimizations were possible in the accumulator variable in hmac.compare_digest.\r\nhttps://bugs.python.org/issue40791",
            "cve": "CVE-2022-48566",
            "id": "pyup.io-60631",
            "more_info_path": "/vulnerabilities/CVE-2022-48566/60631",
            "specs": [
                ">=3.7.0a1,<3.7.10",
                ">=3.10.0a1,<3.10.0a3",
                ">=3.8.0a1,<3.8.7",
                ">=3.9.0a1,<3.9.1",
                "<3.6.13"
            ],
            "v": ">=3.7.0a1,<3.7.10,>=3.10.0a1,<3.10.0a3,>=3.8.0a1,<3.8.7,>=3.9.0a1,<3.9.1,<3.6.13"
        },
        {
            "advisory": "Python 3.6.13, 3.7.10, 3.8.7 and 3.9.1 include a fix for CVE-2022-48564: read_ints in plistlib.py in Python is vulnerable to a potential DoS attack via CPU and RAM exhaustion when processing malformed Apple Property List files in binary format.\r\nhttps://bugs.python.org/issue42103",
            "cve": "CVE-2022-48564",
            "id": "pyup.io-60629",
            "more_info_path": "/vulnerabilities/CVE-2022-48564/60629",
            "specs": [
                ">=3.7.0a1,<3.7.10",
                ">=3.8.0a1,<3.8.7rc1",
                ">=3.9.0a1,<3.9.1rc1",
                "==3.10.0a1",
                ">=3.4.0a1,<3.6.13"
            ],
            "v": ">=3.7.0a1,<3.7.10,>=3.8.0a1,<3.8.7rc1,>=3.9.0a1,<3.9.1rc1,==3.10.0a1,>=3.4.0a1,<3.6.13"
        },
        {
            "advisory": "Python versions 3.7.4 and 3.8.0 includes a fix for ssl.match_hostname() ignoring extra strings after whitespace in IPv4 address.\r\nhttps://python-security.readthedocs.io/vuln/ssl-match_hostname-ipv4-trailing.html",
            "cve": "PVE-2021-42391",
            "id": "pyup.io-45707",
            "more_info_path": "/vulnerabilities/PVE-2021-42391/45707",
            "specs": [
                ">=3.8.0a0,<3.8.0",
                ">=3.7.0a0,<3.7.4"
            ],
            "v": ">=3.8.0a0,<3.8.0,>=3.7.0a0,<3.7.4"
        }
    ],
    "python-a2a": [
        {
            "advisory": "A vulnerability classified as critical has been found in themanojdesai python-a2a up to 0.5.5. Affected is the function create_workflow of the file python_a2a/agent_flow/server/api.py. The manipulation leads to path traversal. Upgrading to version 0.5.6 is able to address this issue. It is recommended to upgrade the affected component.",
            "cve": "CVE-2025-6167",
            "id": "pyup.io-77742",
            "more_info_path": "/vulnerabilities/CVE-2025-6167/77742",
            "specs": [
                "<0.5.6"
            ],
            "v": "<0.5.6"
        }
    ],
    "python-amazon-ad-api": [
        {
            "advisory": "Python-amazon-ad-api 0.5.1 includes a security fix that could lead the application to crash.\r\nhttps://github.com/denisneuf/python-amazon-ad-api/pull/172",
            "cve": "PVE-2023-61860",
            "id": "pyup.io-61860",
            "more_info_path": "/vulnerabilities/PVE-2023-61860/61860",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        }
    ],
    "python-apt": [
        {
            "advisory": "Python-apt up to and including version 0.7.8 is vulnerable to CVE-2019-15796: Python-apt doesn't check if hashes are signed in 'Version.fetch_binary()' and 'Version.fetch_source()' of apt/package.py or in '_fetch_archives()' of apt/cache.py in version 1.9.3ubuntu2 and earlier. This allows downloads from unsigned repositories which shouldn't be allowed and has been fixed in verisions 1.9.5, 1.9.0ubuntu1.2, 1.6.5ubuntu0.1, 1.1.0~beta1ubuntu0.16.04.7, 0.9.3.5ubuntu3+esm2, and 0.8.3ubuntu7.5.\r\nhttps://ubuntu.com/security/notices/USN-4247-1",
            "cve": "CVE-2019-15795",
            "id": "pyup.io-62666",
            "more_info_path": "/vulnerabilities/CVE-2019-15795/62666",
            "specs": [
                "<=0.7.8"
            ],
            "v": "<=0.7.8"
        },
        {
            "advisory": "Python-apt up to and including version 0.7.8 is vulnerable to CVE-2019-15796: Python-apt doesn't check if hashes are signed in 'Version.fetch_binary()' and 'Version.fetch_source()' of apt/package.py or in '_fetch_archives()' of apt/cache.py in version 1.9.3ubuntu2 and earlier. This allows downloads from unsigned repositories which shouldn't be allowed and has been fixed in verisions 1.9.5, 1.9.0ubuntu1.2, 1.6.5ubuntu0.1, 1.1.0~beta1ubuntu0.16.04.7, 0.9.3.5ubuntu3+esm2, and 0.8.3ubuntu7.5.\r\nhttps://ubuntu.com/security/notices/USN-4247-1",
            "cve": "CVE-2019-15796",
            "id": "pyup.io-38109",
            "more_info_path": "/vulnerabilities/CVE-2019-15796/38109",
            "specs": [
                "<=0.7.8"
            ],
            "v": "<=0.7.8"
        }
    ],
    "python-augeas": [
        {
            "advisory": "python-augeas before 1.0.0 is vulnerable to cross-mountpoint and symlink attacks.",
            "cve": "PVE-2021-26077",
            "id": "pyup.io-26077",
            "more_info_path": "/vulnerabilities/PVE-2021-26077/26077",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "The transform_save function in transform.c in Augeas before 1.0.0 allows local users to overwrite arbitrary files and obtain sensitive information via a symlink attack on a .augnew file.",
            "cve": "CVE-2012-0786",
            "id": "pyup.io-42332",
            "more_info_path": "/vulnerabilities/CVE-2012-0786/42332",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "The clone_file function in transfer.c in Augeas before 1.0.0, when copy_if_rename_fails is set and EXDEV or EBUSY is returned by the rename function, allows local users to overwrite arbitrary files and obtain sensitive information via a bind mount on the (1) .augsave or (2) destination file when using the backup save option, or (3) .augnew file when using the newfile save option.",
            "cve": "CVE-2012-0787",
            "id": "pyup.io-42333",
            "more_info_path": "/vulnerabilities/CVE-2012-0787/42333",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "python-base-app": [
        {
            "advisory": "Python-base-app version 0.2.25 adds improved HTTP header options.",
            "cve": "PVE-2021-41821",
            "id": "pyup.io-41821",
            "more_info_path": "/vulnerabilities/PVE-2021-41821/41821",
            "specs": [
                "<0.2.25"
            ],
            "v": "<0.2.25"
        }
    ],
    "python-bitvavo-api": [
        {
            "advisory": "Python-bitvavo-api version 1.4.2 updates its requests dependency from 'requests==2.31.0' to 'requests>=2.31.0,<3.0.0' to address vulnerabilities such as CVE-2023-32681.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-71295",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/71295",
            "specs": [
                "<1.4.2"
            ],
            "v": "<1.4.2"
        }
    ],
    "python-bugzilla": [
        {
            "advisory": "python-bugzilla before 0.9.0 does not validate X.509 certificates, which allows man-in-the-middle attackers to spoof Bugzilla servers via a crafted certificate.",
            "cve": "CVE-2013-2191",
            "id": "pyup.io-35432",
            "more_info_path": "/vulnerabilities/CVE-2013-2191/35432",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        }
    ],
    "python-cjson": [
        {
            "advisory": "Dan Pascu python-cjson 1.0.5 does not properly handle a ['/'] argument to cjson.encode, which makes it easier for remote attackers to conduct certain cross-site scripting (XSS) attacks involving Firefox and the end tag of a SCRIPT element.",
            "cve": "CVE-2009-4924",
            "id": "pyup.io-33160",
            "more_info_path": "/vulnerabilities/CVE-2009-4924/33160",
            "specs": [
                "<1.0.5"
            ],
            "v": "<1.0.5"
        },
        {
            "advisory": "Buffer overflow in Dan Pascu python-cjson 1.0.5, when UCS-4 encoding is enabled, allows context-dependent attackers to cause a denial of service (application crash) or possibly have unspecified other impact via vectors involving crafted Unicode input to the cjson.encode function.",
            "cve": "CVE-2010-1666",
            "id": "pyup.io-33161",
            "more_info_path": "/vulnerabilities/CVE-2010-1666/33161",
            "specs": [
                "<1.0.5"
            ],
            "v": "<1.0.5"
        }
    ],
    "python-clu": [
        {
            "advisory": "Python-clu 0.5.1 removes an unsafe requirement (Django==2.2.5).",
            "cve": "CVE-2019-19118",
            "id": "pyup.io-37800",
            "more_info_path": "/vulnerabilities/CVE-2019-19118/37800",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        }
    ],
    "python-coveralls": [
        {
            "advisory": "Python-Coveralls 2.9.3 includes a security patch for the function 'parse_args' in 'coveralls/init.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load(). \r\nhttps://github.com/z4r/python-coveralls/commit/cb798698f3d6ef120e6d6ff87d4d4a0e239d8c85#diff-82a6c0a53e21b94154c2c4ec0c9c76370e6e9d4305c551b8e70c82add2030db1",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41377",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41377",
            "specs": [
                "<2.9.3"
            ],
            "v": "<2.9.3"
        }
    ],
    "python-dateuti": [
        {
            "advisory": "Python-dateuti is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51752",
            "id": "pyup.io-51752",
            "more_info_path": "/vulnerabilities/PVE-2022-51752/51752",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "python-dbusmock": [
        {
            "advisory": "Affected versions of the python-dbusmock package are vulnerable to Improper Input Validation. The AddTemplate() D-Bus method and the DBusTestCase.spawn_server_template() Python method fail to prevent execution of malicious .pyc files when loading templates from arbitrary paths. This allows attackers to execute arbitrary code with the user's privileges by placing a crafted .pyc file in a world-writable directory such as /tmp and tricking the user into loading the template from that location.",
            "cve": "CVE-2015-1326",
            "id": "pyup.io-37088",
            "more_info_path": "/vulnerabilities/CVE-2015-1326/37088",
            "specs": [
                ">=0.6,<0.15.1"
            ],
            "v": ">=0.6,<0.15.1"
        }
    ],
    "python-docx": [
        {
            "advisory": "Python-docx 0.8.6 includes a fix for CVE-2016-5851: context-dependent attackers were able to conduct XML External Entity (XXE) attacks via a crafted document.",
            "cve": "CVE-2016-5851",
            "id": "pyup.io-26081",
            "more_info_path": "/vulnerabilities/CVE-2016-5851/26081",
            "specs": [
                "<0.8.6"
            ],
            "v": "<0.8.6"
        }
    ],
    "python-engineio": [
        {
            "advisory": "Python-engineio 3.5.2 removes a security alert in the requirements.",
            "cve": "PVE-2021-37168",
            "id": "pyup.io-37168",
            "more_info_path": "/vulnerabilities/PVE-2021-37168/37168",
            "specs": [
                "<3.5.2"
            ],
            "v": "<3.5.2"
        },
        {
            "advisory": "Python-engineio 3.9.0 includes a fix for CVE-2019-13611: An issue was discovered in python-engineio through 3.8.2. There is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability that allows attackers to make WebSocket connections to a server by using a victim's credentials, because the Origin header is not restricted.",
            "cve": "CVE-2019-13611",
            "id": "pyup.io-37288",
            "more_info_path": "/vulnerabilities/CVE-2019-13611/37288",
            "specs": [
                "<3.9.0"
            ],
            "v": "<3.9.0"
        }
    ],
    "python-engineio-v3": [
        {
            "advisory": "Affected versions of Python-engineio are vulnerable to Cross-Site WebSocket Hijacking (CSWSH), that allows attackers to make WebSocket connections to a server by using a victim's credentials, because the Origin header is not restricted.",
            "cve": "CVE-2019-13611",
            "id": "pyup.io-72870",
            "more_info_path": "/vulnerabilities/CVE-2019-13611/72870",
            "specs": [
                "<3.9.0"
            ],
            "v": "<3.9.0"
        }
    ],
    "python-exiv2": [
        {
            "advisory": "A stack out of bounds read vulnerability exists in Exiv2 library 0.26 within the webp parser.",
            "cve": "CVE-2017-1000126",
            "id": "pyup.io-66888",
            "more_info_path": "/vulnerabilities/CVE-2017-1000126/66888",
            "specs": [
                "==0.26"
            ],
            "v": "==0.26"
        },
        {
            "advisory": "Exiv2 0.26 contains a heap buffer overflow in tiff parser.",
            "cve": "CVE-2017-1000127",
            "id": "pyup.io-66891",
            "more_info_path": "/vulnerabilities/CVE-2017-1000127/66891",
            "specs": [
                "==0.26"
            ],
            "v": "==0.26"
        },
        {
            "advisory": "Exiv2 0.26 contains a stack out of bounds read in JPEG2000 parser.",
            "cve": "CVE-2017-1000128",
            "id": "pyup.io-66894",
            "more_info_path": "/vulnerabilities/CVE-2017-1000128/66894",
            "specs": [
                "==0.26"
            ],
            "v": "==0.26"
        }
    ],
    "python-fedora": [
        {
            "advisory": "Python-fedora 0.3.26 fixes faswho auth plugin to set session cookies as secure and httponly and sets the Django session cookies httponly.",
            "cve": "PVE-2021-34408",
            "id": "pyup.io-34408",
            "more_info_path": "/vulnerabilities/PVE-2021-34408/34408",
            "specs": [
                "<0.3.26"
            ],
            "v": "<0.3.26"
        },
        {
            "advisory": "Python-fedora 0.8.0 and lower is vulnerable to an open redirect resulting in loss of CSRF protection.",
            "cve": "CVE-2017-1002150",
            "id": "pyup.io-35705",
            "more_info_path": "/vulnerabilities/CVE-2017-1002150/35705",
            "specs": [
                "<=0.8.0"
            ],
            "v": "<=0.8.0"
        }
    ],
    "python-flask": [
        {
            "advisory": "Python-flask is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51753",
            "id": "pyup.io-51753",
            "more_info_path": "/vulnerabilities/PVE-2022-51753/51753",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "python-for-android": [
        {
            "advisory": "Python-for-android 0.5.3 recognizes Password fields as secure passwords to avoid keyboards \"remembering\" these passwords in their dictionaries.\r\nhttps://github.com/kivy/python-for-android/issues/138",
            "cve": "PVE-2022-46073",
            "id": "pyup.io-46073",
            "more_info_path": "/vulnerabilities/PVE-2022-46073/46073",
            "specs": [
                "<0.5.3"
            ],
            "v": "<0.5.3"
        },
        {
            "advisory": "Python-for-android 2021.09.05 updates its NPM dependency 'grunt' to versions '>=1.3.0' to include a security fix.",
            "cve": "CVE-2020-7729",
            "id": "pyup.io-58762",
            "more_info_path": "/vulnerabilities/CVE-2020-7729/58762",
            "specs": [
                "<2021.09.05"
            ],
            "v": "<2021.09.05"
        }
    ],
    "python-framework": [
        {
            "advisory": "Python-framework 0.3.69 avoids attacks that could arrive from specifying custom requestHeaders.\r\nhttps://github.com/SamuelJansen/python-framework/commit/c674433a8ec729fb093bf57e4e5f589931d64406",
            "cve": "PVE-2022-48257",
            "id": "pyup.io-48257",
            "more_info_path": "/vulnerabilities/PVE-2022-48257/48257",
            "specs": [
                "<0.3.69"
            ],
            "v": "<0.3.69"
        }
    ],
    "python-ftp": [
        {
            "advisory": "Python-ftp is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45430",
            "id": "pyup.io-45430",
            "more_info_path": "/vulnerabilities/PVE-2022-45430/45430",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "python-gitlab": [
        {
            "advisory": "Python-gitlab 2.0.0 updates its dependency 'requests' to versions '>=2.22.0' to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-62152",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/62152",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Python-gitlab 4.0.0 updates its dependency 'requests' to include a security fix.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-62151",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/62151",
            "specs": [
                "<4.0.0"
            ],
            "v": "<4.0.0"
        },
        {
            "advisory": "Python-gitlab 4.4.0 updates its dependency on Jinja2, moving from version 3.1.2 to 3.1.3, in response to the security vulnerability identified as CVE-2024-22195.",
            "cve": "CVE-2024-22195",
            "id": "pyup.io-64121",
            "more_info_path": "/vulnerabilities/CVE-2024-22195/64121",
            "specs": [
                "<4.4.0"
            ],
            "v": "<4.4.0"
        },
        {
            "advisory": "Python-gitlab version 4.5.0 updates its dependency on the `black` package from version 24.2.0 to 24.3.0 in response to CVE-2024-21503.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-70993",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/70993",
            "specs": [
                "<4.5.0"
            ],
            "v": "<4.5.0"
        },
        {
            "advisory": "Python-gitlab version 4.6.0 updates its requests dependency from 2.31.0 to 2.32.0 to address the security vulnerability identified as CVE-2024-35195.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-71219",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/71219",
            "specs": [
                "<4.6.0"
            ],
            "v": "<4.6.0"
        },
        {
            "advisory": "The Python-gitlab package has updated its Jinja2 dependency to version 3.1.5 to address a critical security vulnerability identified as CVE-2024-56326.",
            "cve": "CVE-2024-56326",
            "id": "pyup.io-74857",
            "more_info_path": "/vulnerabilities/CVE-2024-56326/74857",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "The Python-gitlab package has updated its Jinja2 dependency to version 3.1.5 to address a critical security vulnerability identified as CVE-2024-56201.",
            "cve": "CVE-2024-56201",
            "id": "pyup.io-74885",
            "more_info_path": "/vulnerabilities/CVE-2024-56201/74885",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        }
    ],
    "python-glanceclient": [
        {
            "advisory": "The Python client library for Glance (python-glanceclient) before 0.10.0 does not properly check the preverify_ok value, which prevents the server hostname from being verified with a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate and allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.",
            "cve": "CVE-2013-4111",
            "id": "pyup.io-35435",
            "more_info_path": "/vulnerabilities/CVE-2013-4111/35435",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        }
    ],
    "python-gnupg": [
        {
            "advisory": "Python-gnupg before 0.3.5 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in unspecified vectors.",
            "cve": "CVE-2013-7323",
            "id": "pyup.io-35493",
            "more_info_path": "/vulnerabilities/CVE-2013-7323/35493",
            "specs": [
                "<0.3.5"
            ],
            "v": "<0.3.5"
        },
        {
            "advisory": "Python-gnupg 0.3.6 includes a fix for CVE-2014-1928: The shell_quote function in python-gnupg 0.3.5 does not properly escape characters, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using \"\\\" (backslash) characters to form multi-command sequences, a different vulnerability than CVE-2014-1927. \r\nNOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.",
            "cve": "CVE-2014-1928",
            "id": "pyup.io-52944",
            "more_info_path": "/vulnerabilities/CVE-2014-1928/52944",
            "specs": [
                "<0.3.6"
            ],
            "v": "<0.3.6"
        },
        {
            "advisory": "Python-gnupg 0.4.3 allows context-dependent attackers to trick gnupg to decrypt other ciphertext than intended. To perform the attack, the passphrase to gnupg must be controlled by the adversary and the ciphertext should be trusted.\r\nhttps://blog.hackeriet.no/cve-2019-6690-python-gnupg-vulnerability",
            "cve": "CVE-2019-6690",
            "id": "pyup.io-36964",
            "more_info_path": "/vulnerabilities/CVE-2019-6690/36964",
            "specs": [
                "<0.4.3"
            ],
            "v": "<0.4.3"
        },
        {
            "advisory": "The shell_quote function in python-gnupg 0.3.5 does not properly quote strings, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using \"$(\" command-substitution sequences, a different vulnerability than CVE-2014-1928.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.",
            "cve": "CVE-2014-1927",
            "id": "pyup.io-35533",
            "more_info_path": "/vulnerabilities/CVE-2014-1927/35533",
            "specs": [
                "==0.3.5"
            ],
            "v": "==0.3.5"
        },
        {
            "advisory": "Python-gnupg 0.3.5 and 0.3.6 allows context-dependent attackers to have an unspecified impact via vectors related to \"option injection through positional arguments.\" NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.\r\nhttps://seclists.org/oss-sec/2014/q1/335",
            "cve": "CVE-2014-1929",
            "id": "pyup.io-52943",
            "more_info_path": "/vulnerabilities/CVE-2014-1929/52943",
            "specs": [
                "==0.3.5",
                "==0.3.6"
            ],
            "v": "==0.3.5,==0.3.6"
        }
    ],
    "python-homewizard-energy": [
        {
            "advisory": "Python-homewizard-energy 2.1.2 updates its dependency 'urllib3' to include a security fix.",
            "cve": "CVE-2023-43804",
            "id": "pyup.io-61779",
            "more_info_path": "/vulnerabilities/CVE-2023-43804/61779",
            "specs": [
                "<2.1.2"
            ],
            "v": "<2.1.2"
        },
        {
            "advisory": "Python-homewizard-energy 2.1.2 updates its dependency 'gitpython' to include a security fix.",
            "cve": "CVE-2023-40590",
            "id": "pyup.io-61780",
            "more_info_path": "/vulnerabilities/CVE-2023-40590/61780",
            "specs": [
                "<2.1.2"
            ],
            "v": "<2.1.2"
        },
        {
            "advisory": "Python-homewizard-energy 2.1.2 updates its dependency 'gitpython' to include a security fix.",
            "cve": "CVE-2023-41040",
            "id": "pyup.io-61751",
            "more_info_path": "/vulnerabilities/CVE-2023-41040/61751",
            "specs": [
                "<2.1.2"
            ],
            "v": "<2.1.2"
        }
    ],
    "python-hugo": [
        {
            "advisory": "Python-hugo 0.114.0 fixes the upstream Go templates bug with reversed key/value assignment, in response to the identified CVE-2023-24538 vulnerability. \r\nhttps://github.com/gohugoio/hugo/commit/ee359df172ece11989e9b1bf35c2d376f2608ac6",
            "cve": "CVE-2023-24538",
            "id": "pyup.io-63266",
            "more_info_path": "/vulnerabilities/CVE-2023-24538/63266",
            "specs": [
                "<0.114.0"
            ],
            "v": "<0.114.0"
        },
        {
            "advisory": "Python-hugo 0.119.0 upgrades its dependency Go to version 1.21.1, in response to the identified CVE-2023-39318 vulnerability. \r\nhttps://github.com/gohugoio/hugo/commit/1e9b87f7602711fcf84069e03bbae6e0c08f73d1",
            "cve": "CVE-2023-39318",
            "id": "pyup.io-63262",
            "more_info_path": "/vulnerabilities/CVE-2023-39318/63262",
            "specs": [
                "<0.119.0"
            ],
            "v": "<0.119.0"
        },
        {
            "advisory": "Python-hugo 0.120.4 updates its dependency Go to version 1.21.4, as a response to a previously identified security issue concerning the insecure parsing of Windows paths  in Go versions above 1.21.4\r\n#Note: This only affect Windows Users\r\nhttps://github.com/golang/go/issues/63715\r\nhttps://github.com/gohugoio/hugo/commit/9315a2d2c424e41850b642c80c08b898f85bf991",
            "cve": "PVE-2024-63260",
            "id": "pyup.io-63260",
            "more_info_path": "/vulnerabilities/PVE-2024-63260/63260",
            "specs": [
                "<0.120.4"
            ],
            "v": "<0.120.4"
        },
        {
            "advisory": "Python-hugo 0.121.0 updates its dependency libwebp from version v1.2.4 to v1.3.2, in response to the identified CVE-2023-1999 vulnerability.\r\nhttps://github.com/gohugoio/hugo/commit/4fb40ee873415e3147cccb9f2ae43267198a41fe",
            "cve": "CVE-2023-1999",
            "id": "pyup.io-63259",
            "more_info_path": "/vulnerabilities/CVE-2023-1999/63259",
            "specs": [
                "<0.121.0"
            ],
            "v": "<0.121.0"
        },
        {
            "advisory": "Python-hugo 0.81.0 fixes a race condition in text template baseof that could potentially lead to data corruption, access control bypass, denial of service (DoS), deadlocks, thread blocks, and resource starvation in certain situations.\r\nhttps://github.com/gohugoio/hugo/issues/8110\r\nhttps://github.com/gohugoio/hugo/commit/241b7483ea954653512d4895ad6bacf79ee26ddcac",
            "cve": "PVE-2024-63275",
            "id": "pyup.io-63275",
            "more_info_path": "/vulnerabilities/PVE-2024-63275/63275",
            "specs": [
                "<0.81.0"
            ],
            "v": "<0.81.0"
        }
    ],
    "python-incidentio-client": [
        {
            "advisory": "Python-incidentio-client 0.10.0 updates its dependency 'httpx' to version '0.23.0' to include a fix for an Improper Input Validation vulnerability.\r\nhttps://github.com/expobrain/python-incidentio-client/commit/3170dc08b80f82d729164d24fc36e2989ac0f6d0\r\nhttps://github.com/advisories/GHSA-h8pj-cxx2-jfg2",
            "cve": "CVE-2021-41945",
            "id": "pyup.io-59518",
            "more_info_path": "/vulnerabilities/CVE-2021-41945/59518",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        }
    ],
    "python-jose": [
        {
            "advisory": "python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time comparison for HMAC keys.",
            "cve": "CVE-2016-7036",
            "id": "pyup.io-35682",
            "more_info_path": "/vulnerabilities/CVE-2016-7036/35682",
            "specs": [
                "<1.3.2"
            ],
            "v": "<1.3.2"
        },
        {
            "advisory": "Affected versions of Python-jose allow attackers to cause a denial of service (resource consumption) during a decode via a crafted JSON Web Encryption (JWE) token with a high compression ratio, aka a \"JWT bomb.\" This is similar to CVE-2024-21319.",
            "cve": "CVE-2024-33664",
            "id": "pyup.io-70716",
            "more_info_path": "/vulnerabilities/CVE-2024-33664/70716",
            "specs": [
                "<3.4.0"
            ],
            "v": "<3.4.0"
        },
        {
            "advisory": "Affected versions of Python-jose have a algorithm confusion vulnerability with OpenSSH ECDSA keys and other key formats. This is similar to CVE-2022-29217.",
            "cve": "CVE-2024-33663",
            "id": "pyup.io-70715",
            "more_info_path": "/vulnerabilities/CVE-2024-33663/70715",
            "specs": [
                "<3.4.0"
            ],
            "v": "<3.4.0"
        }
    ],
    "python-jsonlogic": [
        {
            "advisory": "Python-jsonlogic version 2.0.1 addresses a security issue where the operations object was vulnerable to exploitation, allowing the execution of arbitrary code.\r\nhttps://security.snyk.io/vuln/SNYK-JS-JSONLOGICJS-674308",
            "cve": "PVE-2024-66041",
            "id": "pyup.io-66041",
            "more_info_path": "/vulnerabilities/PVE-2024-66041/66041",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        }
    ],
    "python-jss": [
        {
            "advisory": "Python-jss 2.1.0 updates its dependency 'urllib3' to v1.24.2 to mitigate a vulnerability.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-38564",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/38564",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        }
    ],
    "python-jwt": [
        {
            "advisory": "Python-jwt 1.0.0 includes fixes for a security vulnerability where 'alg=None' header could bypass signature verification.\r\nhttps://github.com/jpadilla/pyjwt/pull/109\r\nhttps://github.com/jpadilla/pyjwt/pull/110",
            "cve": "PVE-2021-42355",
            "id": "pyup.io-42355",
            "more_info_path": "/vulnerabilities/PVE-2021-42355/42355",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Python-jwt 3.3.4 includes a fix for CVE-2022-39227: Versions prior to 3.3.4 are subject to Authentication Bypass by Spoofing, resulting in identity spoofing, session hijacking or authentication bypass. An attacker who obtains a JWT can arbitrarily forge its contents without knowing the secret key. Depending on the application, this may for example enable the attacker to spoof other user's identities, hijack their sessions, or bypass authentication. There are no known workarounds.",
            "cve": "CVE-2022-39227",
            "id": "pyup.io-51174",
            "more_info_path": "/vulnerabilities/CVE-2022-39227/51174",
            "specs": [
                "<3.3.4"
            ],
            "v": "<3.3.4"
        }
    ],
    "python-keystoneclient": [
        {
            "advisory": "Python-keystoneclient versions 0.11.0 and 1.2.0 include a fix for CVE-2014-7144: OpenStack keystonemiddleware (formerly python-keystoneclient) 0.x before 0.11.0 and 1.x before 1.2.0 disables certification verification when the \"insecure\" option is set in a paste configuration (paste.ini) file regardless of the value, which allows remote attackers to conduct man-in-the-middle attacks via a crafted certificate.\r\nhttp://www.openwall.com/lists/oss-security/2014/09/25/51\r\nhttps://bugs.launchpad.net/python-keystoneclient/+bug/1353315\r\nhttp://rhn.redhat.com/errata/RHSA-2014-1783.html\r\nhttp://rhn.redhat.com/errata/RHSA-2014-1784.html\r\nhttp://rhn.redhat.com/errata/RHSA-2015-0020.html\r\nhttp://www.ubuntu.com/usn/USN-2705-1\r\nhttp://www.securityfocus.com/bid/69864\r\nhttp://secunia.com/advisories/62709",
            "cve": "CVE-2014-7144",
            "id": "pyup.io-35582",
            "more_info_path": "/vulnerabilities/CVE-2014-7144/35582",
            "specs": [
                "<0.11.0",
                ">=1.0.0,<1.2.0"
            ],
            "v": "<0.11.0,>=1.0.0,<1.2.0"
        },
        {
            "advisory": "keystone/middleware/auth_token.py in OpenStack Nova Folsom, Grizzly, and Havana uses an insecure temporary directory for storing signing certificates, which allows local users to spoof servers by pre-creating this directory, which is reused by Nova, as demonstrated using /tmp/keystone-signing-nova on Fedora.",
            "cve": "CVE-2013-2030",
            "id": "pyup.io-66670",
            "more_info_path": "/vulnerabilities/CVE-2013-2030/66670",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        },
        {
            "advisory": "Python-keystoneclient 0.2.4 includes a fix for CVE-2013-2104: python-keystoneclient before 0.2.4, as used in OpenStack Keystone (Folsom), does not properly check expiry for PKI tokens, which allows remote authenticated users to (1) retain use of a token after it has expired, or (2) use a revoked token once it expires.\r\nhttps://bugs.launchpad.net/python-keystoneclient/+bug/1179615",
            "cve": "CVE-2013-2104",
            "id": "pyup.io-35427",
            "more_info_path": "/vulnerabilities/CVE-2013-2104/35427",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        },
        {
            "advisory": "Python-keystoneclient 0.2.4 includes a fix for CVE-2013-2013: The user-password-update command in python-keystoneclient before 0.2.4 accepts the new password in the --password argument, which allows local users to obtain sensitive information by listing the process.\r\nhttps://bugs.launchpad.net/python-keystoneclient/+bug/938315",
            "cve": "CVE-2013-2013",
            "id": "pyup.io-35420",
            "more_info_path": "/vulnerabilities/CVE-2013-2013/35420",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        },
        {
            "advisory": "The auth_token middleware in the OpenStack Python client library for Keystone (aka python-keystoneclient) before 0.7.0 does not properly retrieve user tokens from memcache, which allows remote authenticated users to gain privileges in opportunistic circumstances via a large number of requests, related to an \"interaction between eventlet and python-memcached.\"",
            "cve": "CVE-2014-0105",
            "id": "pyup.io-35503",
            "more_info_path": "/vulnerabilities/CVE-2014-0105/35503",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Python-keystoneclient 1.4.0 includes a fix for CVE-2015-1852: The s3_token middleware in OpenStack keystonemiddleware before 1.6.0 and python-keystoneclient before 1.4.0 disables certification verification when the \"insecure\" option is set in a paste configuration (paste.ini) file regardless of the value, which allows remote attackers to conduct man-in-the-middle attacks via a crafted certificate, a different vulnerability than CVE-2014-7144.",
            "cve": "CVE-2015-1852",
            "id": "pyup.io-26082",
            "more_info_path": "/vulnerabilities/CVE-2015-1852/26082",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "The identity service in OpenStack Identity (Keystone) before 2015.1.3 (Kilo) and 8.0.x before 8.0.2 (Liberty) and keystonemiddleware (formerly python-keystoneclient) before 1.5.4 (Kilo) and Liberty before 2.3.3 does not properly invalidate authorization tokens when using the PKI or PKIZ token providers, which allows remote authenticated users to bypass intended access restrictions and gain access to cloud resources by manipulating byte fields within a revoked token.",
            "cve": "CVE-2015-7546",
            "id": "pyup.io-26083",
            "more_info_path": "/vulnerabilities/CVE-2015-7546/26083",
            "specs": [
                "<1.5.4",
                ">=2.0,<2.3.3"
            ],
            "v": "<1.5.4,>=2.0,<2.3.3"
        },
        {
            "advisory": "Python-keystoneclient is affected by CVE-2022-2447: A flaw was found in OpenStack. The application credential tokens can be used even after they have expired. This flaw allows an authenticated remote attacker to obtain access despite the defender's efforts to remove access.\r\nhttps://access.redhat.com/security/cve/CVE-2022-2447\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=2105419",
            "cve": "CVE-2022-2447",
            "id": "pyup.io-50880",
            "more_info_path": "/vulnerabilities/CVE-2022-2447/50880",
            "specs": [
                "<=5.0.1"
            ],
            "v": "<=5.0.1"
        },
        {
            "advisory": "Python-keystoneclient 0.3.0 includes a fix for CVE-2013-2167: Middleware memcache encryption and signing bypass.",
            "cve": "CVE-2013-2167",
            "id": "pyup.io-37749",
            "more_info_path": "/vulnerabilities/CVE-2013-2167/37749",
            "specs": [
                ">=0.2.3,<=0.2.5"
            ],
            "v": ">=0.2.3,<=0.2.5"
        },
        {
            "advisory": "Python-keystoneclient 0.3.0 includes a fix for CVE-2013-2166: Middleware memcache encryption and signing bypass.",
            "cve": "CVE-2013-2166",
            "id": "pyup.io-37748",
            "more_info_path": "/vulnerabilities/CVE-2013-2166/37748",
            "specs": [
                ">=0.2.3,<=0.2.5"
            ],
            "v": ">=0.2.3,<=0.2.5"
        }
    ],
    "python-kraken-sdk": [
        {
            "advisory": "Python-kraken-sdk 0.7.1 secures protected and private properties and methods.\r\nhttps://github.com/btschwertfeger/Python-Kraken-SDK/pull/26/commits/d4e14e457a6e34e530472db7a734a01e1534e329",
            "cve": "PVE-2022-52052",
            "id": "pyup.io-52052",
            "more_info_path": "/vulnerabilities/PVE-2022-52052/52052",
            "specs": [
                "<0.7.1"
            ],
            "v": "<0.7.1"
        }
    ],
    "python-ldap": [
        {
            "advisory": "Python-ldap 3.4.0 includes a fix for CVE-2021-46823: versions before 3.4.0 are vulnerable to a denial of service when ldap.schema is used for untrusted schema definitions, because of a regular expression denial of service (ReDoS) flaw in the LDAP schema parser. By sending crafted regex input, a remote authenticated attacker could exploit this vulnerability to cause a denial of service condition.\r\nhttps://github.com/python-ldap/python-ldap/security/advisories/GHSA-r8wq-qrxc-hmcm",
            "cve": "CVE-2021-46823",
            "id": "pyup.io-49493",
            "more_info_path": "/vulnerabilities/CVE-2021-46823/49493",
            "specs": [
                "<3.4.0"
            ],
            "v": "<3.4.0"
        },
        {
            "advisory": "Affected versions of the python-ldap package are vulnerable to LDAP Injection / Sanitization Bypass due to improper type checking in the ldap.filter.escape_filter_chars method when handling non-string types. The vulnerability arises because when assertion_value is provided as a list or dict and escape_mode=1 is used, the method bypasses escaping logic and returns raw input containing special characters.",
            "cve": "CVE-2025-61911",
            "id": "pyup.io-80402",
            "more_info_path": "/vulnerabilities/CVE-2025-61911/80402",
            "specs": [
                "<3.4.5"
            ],
            "v": "<3.4.5"
        },
        {
            "advisory": "Affected versions of the python-ldap package are vulnerable to Improper Encoding or Escaping of Output / Improper Null Termination due to incorrect handling of the NUL (0x00) character in ldap.dn.escape_dn_chars(). The function currently replaces \\x00 by a backslash plus a literal NUL (i.e. \\\\\\x00) instead of the RFC 4514\u2013compliant \\00, causing Python strings with embedded NULs that lead to client\u2010side failures or exceptions.",
            "cve": "CVE-2025-61912",
            "id": "pyup.io-80407",
            "more_info_path": "/vulnerabilities/CVE-2025-61912/80407",
            "specs": [
                "<3.4.5"
            ],
            "v": "<3.4.5"
        }
    ],
    "python-levenshtein": [
        {
            "advisory": "Python-levenshtein 0.12.1 fixes handling of numerous possible wraparounds in calculating the size of memory allocations. Incorrect handling of which could cause denial of service or even possible remote code execution in previous versions of the library.",
            "cve": "PVE-2022-51245",
            "id": "pyup.io-51245",
            "more_info_path": "/vulnerabilities/PVE-2022-51245/51245",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        }
    ],
    "python-libarchive": [
        {
            "advisory": "Python-libarchive through 4.2.1 allows directory traversal (to create files) in the extract in zip.py for ZipFile.extractall and ZipFile.extract.",
            "cve": "CVE-2024-55587",
            "id": "pyup.io-76384",
            "more_info_path": "/vulnerabilities/CVE-2024-55587/76384",
            "specs": [
                "<4.2.1"
            ],
            "v": "<4.2.1"
        }
    ],
    "python-libnmap": [
        {
            "advisory": "Python-libnmap 0.7.2 adds unittest for defusedxml to fix billionlaugh and external entities security issues. It also includes a fix for security issue on XXE (XML External Entities). See: CVE-2019-1010017.",
            "cve": "CVE-2019-1010017",
            "id": "pyup.io-39304",
            "more_info_path": "/vulnerabilities/CVE-2019-1010017/39304",
            "specs": [
                "<0.7.2"
            ],
            "v": "<0.7.2"
        },
        {
            "advisory": "In python-libnmap through 0.7.2, remote command execution can occur, if used in a client application that does not validate arguments. \r\nNOTE: the vendor believes it would be unrealistic for an application to call NmapProcess with arguments taken from input data that arrived over an untrusted network, and thus the CVSS score corresponds to an unrealistic use case. None of the NmapProcess documentation implies that this is an expected use case.",
            "cve": "CVE-2022-30284",
            "id": "pyup.io-49148",
            "more_info_path": "/vulnerabilities/CVE-2022-30284/49148",
            "specs": [
                "<=0.7.2"
            ],
            "v": "<=0.7.2"
        }
    ],
    "python-libtorrent": [
        {
            "advisory": "python-libtorrent before 1.0.6 has several undisclosed vulnerabilities related to uTP.",
            "cve": "PVE-2021-26084",
            "id": "pyup.io-26084",
            "more_info_path": "/vulnerabilities/PVE-2021-26084/26084",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        }
    ],
    "python-mf-data": [
        {
            "advisory": "Python-mf-data 0.2.6 updates its dependency 'mako' to v1.2.2 to include a security fix.",
            "cve": "CVE-2022-40023",
            "id": "pyup.io-51453",
            "more_info_path": "/vulnerabilities/CVE-2022-40023/51453",
            "specs": [
                "<0.2.6"
            ],
            "v": "<0.2.6"
        }
    ],
    "python-mistralclient": [
        {
            "advisory": "Affected versions of the python-mistralclient package are vulnerable to Local File Inclusion due to double-loading of workbook definition inputs that allow user-supplied values to be treated as local file paths on the server. When the mistraldashboard.api.workbook_validate helper passes the definition argument to mistralclient.api.v2.workbooks.validate, the python-mistralclient library may interpret a string that already contains workbook contents as a filesystem path, read the referenced file on the Mistral host, and include its raw contents in the validation error response returned to the dashboard.",
            "cve": "CVE-2021-4472",
            "id": "pyup.io-82235",
            "more_info_path": "/vulnerabilities/CVE-2021-4472/82235",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        }
    ],
    "python-mongo": [
        {
            "advisory": "Python-mongo is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45432",
            "id": "pyup.io-45432",
            "more_info_path": "/vulnerabilities/PVE-2022-45432/45432",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "python-ms": [
        {
            "advisory": "Python-ms 1.1.0 includes a fix for a ReDoS vulnerability.\r\nhttps://github.com/Diapolo10/python-ms/commit/441c027b631d6652ccac09d358b77c061ebedc99",
            "cve": "PVE-2023-58825",
            "id": "pyup.io-58825",
            "more_info_path": "/vulnerabilities/PVE-2023-58825/58825",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "python-multipart": [
        {
            "advisory": "Affected versions of python-multipart are vulnerable to Allocation of Resources Without Limits or Throttling (CWE-770). An attacker can send specially crafted multipart/form-data requests containing excessive CR (\\r) or LF (\\n) characters before the first boundary or after the last boundary. This can lead to uncontrolled CPU usage and high memory consumption, causing the processing thread or event loop in ASGI applications to stall, resulting in a denial of service (DoS). The vulnerability exists in the MultipartParser's handling of line breaks around boundaries, where it processes each CRLF byte individually and logs warnings for each occurrence. To exploit this, an attacker simply needs to send large amounts of malformed multipart data with numerous CRLF characters. Upgrading to version 0.0.19 resolves this issue by preventing excessive resource allocation and logging when CRLF bytes are present.",
            "cve": "CVE-2024-53981",
            "id": "pyup.io-74427",
            "more_info_path": "/vulnerabilities/CVE-2024-53981/74427",
            "specs": [
                "<0.0.18"
            ],
            "v": "<0.0.18"
        },
        {
            "advisory": "Affected versions of the python-multipart package are vulnerable to Path Traversal due to unsafe filesystem path construction when preserving user-supplied upload filenames. When UPLOAD_DIR is configured and UPLOAD_KEEP_FILENAME=True, the upload-to-disk code builds the destination path with os.path.join(file_dir, fname) after the upload exceeds MAX_MEMORY_FILE_SIZE, allowing absolute-path filenames (for example, those starting with /) to override the intended base directory.",
            "cve": "CVE-2026-24486",
            "id": "pyup.io-85155",
            "more_info_path": "/vulnerabilities/CVE-2026-24486/85155",
            "specs": [
                "<0.0.22"
            ],
            "v": "<0.0.22"
        },
        {
            "advisory": "A vulnerability in versions of python-multipart before 0.0.7 involves a Regular Expression Denial of Service (ReDoS) triggered by custom Content-Type headers. This issue allows an attacker to cause a significant consumption of system resources while processing such headers, effectively preventing the processing of other requests. This ReDoS vulnerability stems from the way regular expressions evaluate certain input patterns, which can lead to extensive backtracking, thereby causing the application to slow down significantly, consuming a disproportionate amount of CPU time and facilitating a denial of service condition.",
            "cve": "PVE-2024-99762",
            "id": "pyup.io-66706",
            "more_info_path": "/vulnerabilities/PVE-2024-99762/66706",
            "specs": [
                ">=0,<0.0.7"
            ],
            "v": ">=0,<0.0.7"
        }
    ],
    "python-muranoclient": [
        {
            "advisory": "OpenStack Murano before 1.0.3 (liberty) and 2.x before 2.0.1 (mitaka), Murano-dashboard before 1.0.3 (liberty) and 2.x before 2.0.1 (mitaka), and python-muranoclient before 0.7.3 (liberty) and 0.8.x before 0.8.5 (mitaka) improperly use loaders inherited from yaml.Loader when parsing MuranoPL and UI files, which allows remote attackers to create arbitrary Python objects and execute arbitrary code via crafted extended YAML tags in UI definitions in packages.",
            "cve": "CVE-2016-4972",
            "id": "pyup.io-26085",
            "more_info_path": "/vulnerabilities/CVE-2016-4972/26085",
            "specs": [
                "<0.7.3",
                ">=0.8,<0.8.5"
            ],
            "v": "<0.7.3,>=0.8,<0.8.5"
        }
    ],
    "python-mysql": [
        {
            "advisory": "Python-mysql is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45433",
            "id": "pyup.io-45433",
            "more_info_path": "/vulnerabilities/PVE-2022-45433/45433",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "python-mysqldb": [
        {
            "advisory": "Python-mysqldb is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45434",
            "id": "pyup.io-45434",
            "more_info_path": "/vulnerabilities/PVE-2022-45434/45434",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "python-ndev-blizzardapi": [
        {
            "advisory": "Python-ndev-blizzardapi version 0.1.2 has been upgraded to Python 3.12 and includes minor security adjustments in response to CVE-2023-40217.",
            "cve": "CVE-2023-40217",
            "id": "pyup.io-70410",
            "more_info_path": "/vulnerabilities/CVE-2023-40217/70410",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "python-nomad": [
        {
            "advisory": "Python-nomad 1.0.1 updates 'requests` to v2.20.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36602",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36602",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        }
    ],
    "python-opencv": [
        {
            "advisory": "Python-opencv isn't in PyPI. The package you may be looking for is \"opencv-python\".",
            "cve": "PVE-2022-50757",
            "id": "pyup.io-50757",
            "more_info_path": "/vulnerabilities/PVE-2022-50757/50757",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "python-openflow": [
        {
            "advisory": "python-openflow 2016.1.a1 fixes a undisclosed security vulnerability.",
            "cve": "PVE-2021-33282",
            "id": "pyup.io-33282",
            "more_info_path": "/vulnerabilities/PVE-2021-33282/33282",
            "specs": [
                "<2016.1.a1"
            ],
            "v": "<2016.1.a1"
        },
        {
            "advisory": "Python-openflow 2019.1b3 updates its dependency 'urllib3' to v1.24.2 to include a security fix.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-44962",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/44962",
            "specs": [
                "<2019.1b3"
            ],
            "v": "<2019.1b3"
        },
        {
            "advisory": "Python-openflow 2019.1b3 updates its dependency 'jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-37224",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/37224",
            "specs": [
                "<2019.1b3"
            ],
            "v": "<2019.1b3"
        }
    ],
    "python-openssl": [
        {
            "advisory": "Python-openssl is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45435",
            "id": "pyup.io-45435",
            "more_info_path": "/vulnerabilities/PVE-2022-45435/45435",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "python-openstackclient": [
        {
            "advisory": "Affected versions of the python-openstackclient package are vulnerable to Improper Input Validation due to deletion logic not correctly handling non-existent access rules. The deletion routines in the access rules module perform a delete operation when a user attempts to remove a non-existing access rule, which inadvertently deletes other existing rules not associated with the specified application credentials. An attacker with low privileges who attempts to delete a non-existent access rule can unintentionally cause the removal of unrelated access rules, leading to unintended integrity impact and potential disruption of access controls.",
            "cve": "CVE-2023-6110",
            "id": "pyup.io-78809",
            "more_info_path": "/vulnerabilities/CVE-2023-6110/78809",
            "specs": [
                "<6.3.0"
            ],
            "v": "<6.3.0"
        }
    ],
    "python-openzwave": [
        {
            "advisory": "Python-openzwave version 0.4.19 includes a security patch for the function 'update_ozw_config' in 'openzwave/controller.py'. Previous versions contained an OS injection vulnerability: unsafe use of os.system().\r\nhttps://github.com/OpenZWave/python-openzwave/commit/3ef3e4b2c68052cc1973e0bbf080048247c3aa89#diff-c804949ef4a7ac8d06368ac70d26e88b719a6e8affe926716e2ae02a24896326",
            "cve": "PVE-2021-41378",
            "id": "pyup.io-41378",
            "more_info_path": "/vulnerabilities/PVE-2021-41378/41378",
            "specs": [
                "<0.4.19"
            ],
            "v": "<0.4.19"
        }
    ],
    "python-otr": [
        {
            "advisory": "python-otr before 1.1.0 is vulnerable to man-in-the-middle attacks as it allows to restart the protocol.\r\nhttps://github.com/AGProjects/python-otr/commit/8f3e291b172bb97272be077c67bce430dababcdb",
            "cve": "PVE-2021-26086",
            "id": "pyup.io-26086",
            "more_info_path": "/vulnerabilities/PVE-2021-26086/26086",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "python-pptx": [
        {
            "advisory": "python-pptx before 0.6.12 used a vulnerable version of Pillow.",
            "cve": "PVE-2021-36382",
            "id": "pyup.io-36382",
            "more_info_path": "/vulnerabilities/PVE-2021-36382/36382",
            "specs": [
                "<0.6.12"
            ],
            "v": "<0.6.12"
        },
        {
            "advisory": "Python-pptx 0.6.23 removes '<=9.5.0' constraint for 'pillow' to include security fixes.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62149",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62149",
            "specs": [
                "<0.6.23"
            ],
            "v": "<0.6.23"
        }
    ],
    "python-pycraft": [
        {
            "advisory": "Python-pycraft 0.8 doesn't attempts to get an internet connection in game, due to privacy, performance and security concerns.",
            "cve": "PVE-2021-42479",
            "id": "pyup.io-42479",
            "more_info_path": "/vulnerabilities/PVE-2021-42479/42479",
            "specs": [
                "<0.8"
            ],
            "v": "<0.8"
        }
    ],
    "python-rapidjson": [
        {
            "advisory": "Python-rapidjson 1.15 now enforces the recursion limit during parsing to mitigate potential vulnerabilities, specifically addressing the concerns outlined in CVE-2024-27454.",
            "cve": "CVE-2024-27454",
            "id": "pyup.io-65707",
            "more_info_path": "/vulnerabilities/CVE-2024-27454/65707",
            "specs": [
                "<1.15"
            ],
            "v": "<1.15"
        }
    ],
    "python-saml": [
        {
            "advisory": "Python-saml 2.11.0 sets sha256 and rsa-sha256 as default algorithms.\r\nhttps://github.com/onelogin/python-saml/commit/8f76c85756c252d9c845eb268f2111d9d7a53b97",
            "cve": "PVE-2022-44711",
            "id": "pyup.io-44711",
            "more_info_path": "/vulnerabilities/PVE-2022-44711/44711",
            "specs": [
                "<2.11.0"
            ],
            "v": "<2.11.0"
        },
        {
            "advisory": "Python-saml 2.11.0 updates its dependency 'lxml' requirement to \">=4.7.1\" to include security fixes.",
            "cve": "PVE-2021-39195",
            "id": "pyup.io-50743",
            "more_info_path": "/vulnerabilities/PVE-2021-39195/50743",
            "specs": [
                "<2.11.0"
            ],
            "v": "<2.11.0"
        },
        {
            "advisory": "Python-saml 2.11.0 updates its dependency 'lxml' requirement to \">=4.7.1\" to include security fixes.",
            "cve": "CVE-2018-19787",
            "id": "pyup.io-50742",
            "more_info_path": "/vulnerabilities/CVE-2018-19787/50742",
            "specs": [
                "<2.11.0"
            ],
            "v": "<2.11.0"
        },
        {
            "advisory": "Python-saml 2.11.0 updates its dependency 'lxml' requirement to \">=4.7.1\" to include security fixes.",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-50746",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/50746",
            "specs": [
                "<2.11.0"
            ],
            "v": "<2.11.0"
        },
        {
            "advisory": "Python-saml 2.11.0 updates its dependency 'lxml' requirement to \">=4.7.1\" to include security fixes.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-50745",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/50745",
            "specs": [
                "<2.11.0"
            ],
            "v": "<2.11.0"
        },
        {
            "advisory": "Python-saml 2.11.0 updates its dependency 'lxml' requirement to \">=4.7.1\" to include security fixes.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-50744",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/50744",
            "specs": [
                "<2.11.0"
            ],
            "v": "<2.11.0"
        },
        {
            "advisory": "Python-saml 2.2.0 includes several fixes to prevent Signature Wrapping attacks.\r\nhttps://github.com/onelogin/python-saml/commit/aeb25be9aff1313ec87c2f9b19687fb76088813f",
            "cve": "CVE-2016-1000252",
            "id": "pyup.io-26087",
            "more_info_path": "/vulnerabilities/CVE-2016-1000252/26087",
            "specs": [
                "<2.2.0"
            ],
            "v": "<2.2.0"
        },
        {
            "advisory": "Python-saml 2.3.0 replaces etree.tostring  with the sanitized call provided by defusedxml, to prevent XXE attacks.\r\nhttps://github.com/onelogin/python-saml/commit/0799719409282c77672b846004cf9da2cb8de942",
            "cve": "CVE-2017-11427",
            "id": "pyup.io-50738",
            "more_info_path": "/vulnerabilities/CVE-2017-11427/50738",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Python-saml 2.5.0 includes security improvements to prevent XPath injection.\r\nhttps://github.com/SAML-Toolkits/python3-saml/commit/61eacb44d5789bd96edd11309a2bcae66e0d725f\r\nhttps://github.com/SAML-Toolkits/python-saml/commit/c2e8b095e1af5fe665d5128dfb4ed53e21e92ad8",
            "cve": "PVE-2021-39452",
            "id": "pyup.io-39452",
            "more_info_path": "/vulnerabilities/PVE-2021-39452/39452",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Python-saml 2.7.0 sets to True the default value for 'strict' setting to improve validation.\r\nhttps://github.com/onelogin/python-saml/commit/8bb4901efa89435466d0087f66efbb5c3f053f44",
            "cve": "PVE-2022-50739",
            "id": "pyup.io-50739",
            "more_info_path": "/vulnerabilities/PVE-2022-50739/50739",
            "specs": [
                "<2.7.0"
            ],
            "v": "<2.7.0"
        }
    ],
    "python-scciclient": [
        {
            "advisory": "Python-scciclient 0.12.0 includes a fix for CVE-2022-2996: A flaw was found in the python-scciclient when making an HTTPS connection to a server where the server's certificate would not be verified. This issue opens up the connection to possible Man-in-the-middle (MITM) attacks.",
            "cve": "CVE-2022-2996",
            "id": "pyup.io-50881",
            "more_info_path": "/vulnerabilities/CVE-2022-2996/50881",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        }
    ],
    "python-secrets": [
        {
            "advisory": "Python-secrets 0.9.1 adds ``six`` for securing ``input`` call.",
            "cve": "PVE-2021-37582",
            "id": "pyup.io-37582",
            "more_info_path": "/vulnerabilities/PVE-2021-37582/37582",
            "specs": [
                "<0.9.1"
            ],
            "v": "<0.9.1"
        },
        {
            "advisory": "Python-secrets before 19.10.0 adds control of umask for better file perm security.",
            "cve": "PVE-2021-37583",
            "id": "pyup.io-37583",
            "more_info_path": "/vulnerabilities/PVE-2021-37583/37583",
            "specs": [
                "<19.10.0"
            ],
            "v": "<19.10.0"
        },
        {
            "advisory": "Python-secrets 19.12.0 addresses security issue per \"Your xkcd passwords are pwned\" article.\r\nhttps://www.unix-ninja.com/p/your_xkcd_passwords_are_pwned",
            "cve": "PVE-2021-41720",
            "id": "pyup.io-41720",
            "more_info_path": "/vulnerabilities/PVE-2021-41720/41720",
            "specs": [
                "<19.12.0"
            ],
            "v": "<19.12.0"
        },
        {
            "advisory": "Python-secrets 19.8.0 tightens permissions on cloned environments/groups.\r\nhttps://github.com/davedittrich/python_secrets/commit/db39d50cabaa4fe9470b96ec8b8b931cf388e647",
            "cve": "PVE-2021-37401",
            "id": "pyup.io-37401",
            "more_info_path": "/vulnerabilities/PVE-2021-37401/37401",
            "specs": [
                "<19.8.0"
            ],
            "v": "<19.8.0"
        },
        {
            "advisory": "Python-secrets 19.8.3 ensures more secure permissions.\r\nhttps://github.com/davedittrich/python_secrets/commit/4cfa6d8d7f809d823de784dac2ddad4341d0e3f6",
            "cve": "PVE-2021-37421",
            "id": "pyup.io-37421",
            "more_info_path": "/vulnerabilities/PVE-2021-37421/37421",
            "specs": [
                "<19.8.3"
            ],
            "v": "<19.8.3"
        },
        {
            "advisory": "Python-secrets 21.6.0 switches to a more secure random number generator.",
            "cve": "PVE-2021-41719",
            "id": "pyup.io-41719",
            "more_info_path": "/vulnerabilities/PVE-2021-41719/41719",
            "specs": [
                "<21.6.0"
            ],
            "v": "<21.6.0"
        }
    ],
    "python-semantic-release": [
        {
            "advisory": "Affected versions of the python-semantic-release package are vulnerable to Command Injection due to unsanitized use of the `root_options` action input in the GitHub Action\u2019s `action.sh` script. The `action.sh` script previously built the release command with `eval \"/psr/.venv/bin/semantic-release $INPUT_ROOT_OPTIONS version ${ARGS[*]}\"`, so shell metacharacters in the `root_options` value defined in `action.yml` were interpreted and executed by the shell.",
            "cve": "PVE-2025-79317",
            "id": "pyup.io-79317",
            "more_info_path": "/vulnerabilities/PVE-2025-79317/79317",
            "specs": [
                "<10.0.0"
            ],
            "v": "<10.0.0"
        },
        {
            "advisory": "Versions of Python-semantic-release prior to 9.4.2 are capable of establishing HTTP connections if so configured, potentially exposing the connection to security risks due .",
            "cve": "PVE-2024-67892",
            "id": "pyup.io-67892",
            "more_info_path": "/vulnerabilities/PVE-2024-67892/67892",
            "specs": [
                "<9.4.2"
            ],
            "v": "<9.4.2"
        },
        {
            "advisory": "Python-semantic-release affected versions contain a path traversal vulnerability affecting Windows systems. The issue is located in the RuntimeContext class of semantic_release/cli/config.py, stems from improper path resolution when handling changelog files and template directories. This could allow attackers to access or modify files outside the intended repository directory. The vulnerability arises from using Path.resolve() without Path.absolute(), which may return relative paths on Windows for non-existent directories, potentially bypassing security checks. \r\n#NOTE: This only affects Windows users.",
            "cve": "PVE-2024-72981",
            "id": "pyup.io-72981",
            "more_info_path": "/vulnerabilities/PVE-2024-72981/72981",
            "specs": [
                "<9.8.8"
            ],
            "v": "<9.8.8"
        }
    ],
    "python-smooch": [
        {
            "advisory": "Python-smooch 1.0.4 updates 'requests' to resolve a potential vulnerability in HTTP connections handling.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36604",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36604",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        }
    ],
    "python-socketio": [
        {
            "advisory": "Affected versions of Python-socketio are vulnerable to Cross-Site WebSocket Hijacking (CSWSH), that allows attackers to make WebSocket connections to a server by using a victim's credentials, because the Origin header is not restricted.",
            "cve": "CVE-2019-13611",
            "id": "pyup.io-37308",
            "more_info_path": "/vulnerabilities/CVE-2019-13611/37308",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        },
        {
            "advisory": "Affected versions of the python-socketio package are vulnerable to Deserialization of Untrusted Data due to unsafe use of pickle when decoding inter-server messages from a shared message queue. In multi-server configurations that use a queue backend (e.g., Redis) for internal communications, the Pub/Sub path deserializes queue messages with pickle.loads() without validating trust or content, enabling execution via crafted __reduce__ payloads.",
            "cve": "CVE-2025-61765",
            "id": "pyup.io-80185",
            "more_info_path": "/vulnerabilities/CVE-2025-61765/80185",
            "specs": [
                ">=0.8.0,<5.14.0"
            ],
            "v": ">=0.8.0,<5.14.0"
        }
    ],
    "python-socketio-v4": [
        {
            "advisory": "Affected versions of Python-socketio-v4 are vulnerable to Cross-Site WebSocket Hijacking (CSWSH), that allows attackers to make WebSocket connections to a server by using a victim's credentials, because the Origin header is not restricted.",
            "cve": "CVE-2019-13611",
            "id": "pyup.io-72872",
            "more_info_path": "/vulnerabilities/CVE-2019-13611/72872",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        }
    ],
    "python-sql": [
        {
            "advisory": "A vulnerability was found in python-sql where unary operators do not escape non-Expression (like And and Or), which makes any system exposing those vulnerable to an SQL injection attack.",
            "cve": "CVE-2024-9774",
            "id": "pyup.io-76375",
            "more_info_path": "/vulnerabilities/CVE-2024-9774/76375",
            "specs": [
                "<1.5.2"
            ],
            "v": "<1.5.2"
        }
    ],
    "python-sqlite": [
        {
            "advisory": "Python-sqlite is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45436",
            "id": "pyup.io-45436",
            "more_info_path": "/vulnerabilities/PVE-2022-45436/45436",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "python-tutum": [
        {
            "advisory": "Python-tutum 0.14.2 avoids reconnecting when not authorized.\r\nhttps://github.com/tutumcloud/python-tutum/commit/0977801be213a95738568d444e01d448ce59c36f",
            "cve": "PVE-2021-34687",
            "id": "pyup.io-34687",
            "more_info_path": "/vulnerabilities/PVE-2021-34687/34687",
            "specs": [
                "<0.14.2"
            ],
            "v": "<0.14.2"
        }
    ],
    "python-urbandict": [
        {
            "advisory": "Python-urbandict 0.3.10 updates its certifi dependency from version 2024.6.2 to 2024.7.4 to address a security vulnerability identified as CVE-2024-39689.",
            "cve": "CVE-2024-39689",
            "id": "pyup.io-72052",
            "more_info_path": "/vulnerabilities/CVE-2024-39689/72052",
            "specs": [
                "<0.3.10"
            ],
            "v": "<0.3.10"
        },
        {
            "advisory": "Python-urbandict updates its `urllib3` dependency from version 2.2.1 to 2.2.2 to address security concerns, including CVE-2024-37891.",
            "cve": "CVE-2024-37891",
            "id": "pyup.io-71738",
            "more_info_path": "/vulnerabilities/CVE-2024-37891/71738",
            "specs": [
                "<0.3.9"
            ],
            "v": "<0.3.9"
        }
    ],
    "python-zeep": [
        {
            "advisory": "python-zeep 0.4.0 adds defusedxml module for XML security issues.",
            "cve": "PVE-2021-36504",
            "id": "pyup.io-36504",
            "more_info_path": "/vulnerabilities/PVE-2021-36504/36504",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "python3-dateutil": [
        {
            "advisory": "Python3-dateutil is a malicious package, typosquatting. It steals SSH and GPG keys from the projects of infected developers.\r\nhttps://www.zdnet.com/article/two-malicious-python-libraries-removed-from-pypi/",
            "cve": "PVE-2022-45411",
            "id": "pyup.io-45411",
            "more_info_path": "/vulnerabilities/PVE-2022-45411/45411",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "python3-flask": [
        {
            "advisory": "Python3-flask is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51754",
            "id": "pyup.io-51754",
            "more_info_path": "/vulnerabilities/PVE-2022-51754/51754",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "python3-ldap": [
        {
            "advisory": "python3-ldap before 0.9.5.4 has a security issue in lazy connections.",
            "cve": "PVE-2021-26089",
            "id": "pyup.io-26089",
            "more_info_path": "/vulnerabilities/PVE-2021-26089/26089",
            "specs": [
                "<0.9.5.4"
            ],
            "v": "<0.9.5.4"
        },
        {
            "advisory": "Python3-ldap 2.4 includes a security fix in the rebind() method of the Connection object.",
            "cve": "PVE-2017-47542",
            "id": "pyup.io-47542",
            "more_info_path": "/vulnerabilities/PVE-2017-47542/47542",
            "specs": [
                "<2.4"
            ],
            "v": "<2.4"
        }
    ],
    "python3-saml": [
        {
            "advisory": "Python3-saml 1.13.0 sets sha256 and rsa-sha256 as default algorithms.\r\nhttps://github.com/onelogin/python3-saml/pull/296",
            "cve": "PVE-2022-44711",
            "id": "pyup.io-50740",
            "more_info_path": "/vulnerabilities/PVE-2022-44711/50740",
            "specs": [
                "<1.13.0"
            ],
            "v": "<1.13.0"
        },
        {
            "advisory": "Python3-saml 1.13.0 updates its dependency 'lxml' to v4.7.0 to include security fixes.",
            "cve": "CVE-2018-19787",
            "id": "pyup.io-44718",
            "more_info_path": "/vulnerabilities/CVE-2018-19787/44718",
            "specs": [
                "<1.13.0"
            ],
            "v": "<1.13.0"
        },
        {
            "advisory": "Python3-saml 1.13.0 updates its dependency 'lxml' to v4.7.0 to include security fixes.",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-44754",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/44754",
            "specs": [
                "<1.13.0"
            ],
            "v": "<1.13.0"
        },
        {
            "advisory": "Python3-saml 1.13.0 updates its dependency 'lxml' to v4.7.0 to include security fixes.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-44755",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/44755",
            "specs": [
                "<1.13.0"
            ],
            "v": "<1.13.0"
        },
        {
            "advisory": "Python3-saml 1.13.0 updates its dependency 'lxml' to v4.7.0 to include security fixes.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-44756",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/44756",
            "specs": [
                "<1.13.0"
            ],
            "v": "<1.13.0"
        },
        {
            "advisory": "Python3-saml 1.2.1 includes several fixes to prevent Signature Wrapping attacks.\r\nhttps://github.com/onelogin/python3-saml/pull/30",
            "cve": "PVE-2021-26087",
            "id": "pyup.io-26090",
            "more_info_path": "/vulnerabilities/PVE-2021-26087/26090",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Multiple SAML libraries may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.",
            "cve": "CVE-2017-11427",
            "id": "pyup.io-35780",
            "more_info_path": "/vulnerabilities/CVE-2017-11427/35780",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Python3-saml 1.5.0 contains security improvements to prevent XPath injection. It also disables DTD on the fromstring defusedxml method.\r\nhttps://github.com/SAML-Toolkits/python3-saml/commit/61eacb44d5789bd96edd11309a2bcae66e0d725f\r\nhttps://github.com/SAML-Toolkits/python-saml/commit/c2e8b095e1af5fe665d5128dfb4ed53e21e92ad8",
            "cve": "PVE-2021-39454",
            "id": "pyup.io-39454",
            "more_info_path": "/vulnerabilities/PVE-2021-39454/39454",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        },
        {
            "advisory": "Python3-saml 1.8.0 sets to True the default value for 'strict' setting to improve validation. When strict is True, then the Python Toolkit will reject unsigned or unencrypted messages if it expects them to be signed or encrypted. Also it will reject the messages if the SAML standard is not strictly followed. Destination, NameId, Conditions ... are validated too.\r\nhttps://github.com/SAML-Toolkits/python3-saml/commit/b7ae95132f35a5b649c546bb79442422aff3073a",
            "cve": "PVE-2022-50739",
            "id": "pyup.io-50741",
            "more_info_path": "/vulnerabilities/PVE-2022-50739/50741",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        }
    ],
    "pythonkafka": [
        {
            "advisory": "Pythonkafka is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45431",
            "id": "pyup.io-45431",
            "more_info_path": "/vulnerabilities/PVE-2022-45431/45431",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "pythonmysequel": [
        {
            "advisory": "Pythonmysequel 0.2.0 adds SQL injection protection.",
            "cve": "PVE-2021-41232",
            "id": "pyup.io-41232",
            "more_info_path": "/vulnerabilities/PVE-2021-41232/41232",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "pythonstyles": [
        {
            "advisory": "Pythonstyles is a malicious package. It installs information-stealing and RAT (remote access trojan) Malware while using Cloudflare Tunnel to bypass firewall restrictions for remote access.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-pypi-packages-create-cloudflare-tunnels-to-bypass-firewalls",
            "cve": "PVE-2023-52939",
            "id": "pyup.io-52939",
            "more_info_path": "/vulnerabilities/PVE-2023-52939/52939",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "pytket-quantinuum": [
        {
            "advisory": "Pytket-quantinuum 0.3.1 updates its dependency 'pyjwt' to v2.4 to include a security fix.",
            "cve": "CVE-2022-29217",
            "id": "pyup.io-51341",
            "more_info_path": "/vulnerabilities/CVE-2022-29217/51341",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "pytoileur": [
        {
            "advisory": "The Pytoileur package is identified as malicious, designed to steal cryptocurrency from users. It conceals code that downloads and installs trojanized Windows binaries, which are capable of conducting surveillance activities. Users are advised to avoid this package and check their systems if they have installed it.",
            "cve": "PVE-2024-71364",
            "id": "pyup.io-71364",
            "more_info_path": "/vulnerabilities/PVE-2024-71364/71364",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "pytoolbox": [
        {
            "advisory": "Pytoolbox 14.0.0 includes a security patch for the function 'load_metadata' in 'pytoolbox/juju.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/davidfischer-ch/pytoolbox/commit/748250794514681c0ef8725047a5da4dd9d8a7fd#diff-70bec318e5ce058eed29fb35ad6b97d24ece119b0a51b7f1cdb5a064a4bf5b6b",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41379",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41379",
            "specs": [
                "<14.0.0"
            ],
            "v": "<14.0.0"
        }
    ],
    "pytorch": [
        {
            "advisory": "Affected versions of the PyTorch package are vulnerable to Remote Code Execution due to improper validation of untrusted checkpoint deserialization in the weights_only unpickler. When torch.load(..., weights_only=True) processes a .pth checkpoint, the weights_only unpickler fails to correctly validate pickle opcodes (including SETITEM/SETITEMS applied to non-dictionary types) and storage metadata (including mismatched declared element counts versus archive data), which can result in heap memory corruption.",
            "cve": "CVE-2026-24747",
            "id": "pyup.io-85246",
            "more_info_path": "/vulnerabilities/CVE-2026-24747/85246",
            "specs": [
                "<2.10.0"
            ],
            "v": "<2.10.0"
        }
    ],
    "pytorch-ie": [
        {
            "advisory": "Pytorch-ie 0.13.0 updates its dependency 'gitpython' to v3.1.30 to include a security fix.",
            "cve": "CVE-2022-24439",
            "id": "pyup.io-53509",
            "more_info_path": "/vulnerabilities/CVE-2022-24439/53509",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        }
    ],
    "pytorch-lattice": [
        {
            "advisory": "Pytorch-lattice version 0.2.0 updates its Pillow dependency to versions >=10.2 and <11.0 to address security concerns highlighted by CVE-2023-44271.\r\nhttps://github.com/willbakst/pytorch-lattice/pull/14/commits/a310f10cb11b57c1b1c0ac6583b47218128bef90",
            "cve": "CVE-2023-44271",
            "id": "pyup.io-65330",
            "more_info_path": "/vulnerabilities/CVE-2023-44271/65330",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "pytorch-lightning": [
        {
            "advisory": "Pytorch-lightning 0.9.0 fixes a shell injection vulnerability in a subprocess call.\r\nhttps://github.com/Lightning-AI/pytorch-lightning/pull/2786",
            "cve": "PVE-2021-38707",
            "id": "pyup.io-38707",
            "more_info_path": "/vulnerabilities/PVE-2021-38707/38707",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        },
        {
            "advisory": "Pytorch-lightning 1.6.0 updates its dependency 'pyyaml' to v5.4 and uses yaml.safe_load() to fix code execution vulnerabilities.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-43752",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/43752",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        },
        {
            "advisory": "Pytorch-lightning 1.6.0 updates its dependency 'pyyaml' to v5.4 and uses yaml.safe_load() to fix code execution vulnerabilities.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-43581",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/43581",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        },
        {
            "advisory": "Affected versions of the PyTorch Lightning package are vulnerable to Denial of Service (DoS) due to improper validation of state values. The `/api/v1/state` endpoint in the LightningApp component fails to properly handle unexpected state values in POST requests, causing the server process to crash.",
            "cve": "CVE-2024-8020",
            "id": "pyup.io-76219",
            "more_info_path": "/vulnerabilities/CVE-2024-8020/76219",
            "specs": [
                "<2.3.2"
            ],
            "v": "<2.3.2"
        },
        {
            "advisory": "Affected versions of the PyTorch-Lightning package are vulnerable to Path Traversal due to insufficient validation of user-supplied filenames. The `/api/v1/upload_file/` endpoint in the LightningApp component on Windows hosts fails to sanitize the filename parameter, allowing directory traversal sequences to escape the intended upload directory.",
            "cve": "CVE-2024-8019",
            "id": "pyup.io-76225",
            "more_info_path": "/vulnerabilities/CVE-2024-8019/76225",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "PyTorch Lightning version 1.5.10 and prior is vulnerable to code injection. An attacker could execute commands on the target OS running the operating system by setting the `PL_TRAINER_GPUS` when using the `Trainer` module. A [patch](https://github.com/pytorchlightning/pytorch-lightning/commit/8b7a12c52e52a06408e9231647839ddb4665e8ae) is included in the `1.6.0` release.\r\nAffected functions:\r\npytorch_lightning.utilities.argparse.parse_env_variables",
            "cve": "CVE-2022-0845",
            "id": "pyup.io-54685",
            "more_info_path": "/vulnerabilities/CVE-2022-0845/54685",
            "specs": [
                ">=0,<1.6.0"
            ],
            "v": ">=0,<1.6.0"
        },
        {
            "advisory": "Pytorch-lightning before 1.6.0 is vulnerable to Deserialization of Untrusted Data.",
            "cve": "CVE-2021-4118",
            "id": "pyup.io-54698",
            "more_info_path": "/vulnerabilities/CVE-2021-4118/54698",
            "specs": [
                ">=0,<1.6.0"
            ],
            "v": ">=0,<1.6.0"
        }
    ],
    "pytorch-models": [
        {
            "advisory": "Pytorch-Models 0.2.8 includes a security patch for the function 'load_yaml' in 'torchmodels/utils.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/kaniblu/pytorch-models/commit/a50ef66ecc3de498e0856489d801c61417188f7b",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41380",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41380",
            "specs": [
                "<0.2.8"
            ],
            "v": "<0.2.8"
        }
    ],
    "pytorhc": [
        {
            "advisory": "Pytorhc is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51751",
            "id": "pyup.io-51751",
            "more_info_path": "/vulnerabilities/PVE-2022-51751/51751",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pytoxo": [
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'notebook' to v6.4.10 to include security fixes.",
            "cve": "CVE-2021-32798",
            "id": "pyup.io-48191",
            "more_info_path": "/vulnerabilities/CVE-2021-32798/48191",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "PVE-2021-44525",
            "id": "pyup.io-48201",
            "more_info_path": "/vulnerabilities/PVE-2021-44525/48201",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "PVE-2022-44524",
            "id": "pyup.io-48202",
            "more_info_path": "/vulnerabilities/PVE-2022-44524/48202",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-48205",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/48205",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-48206",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/48206",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-24303",
            "id": "pyup.io-48199",
            "more_info_path": "/vulnerabilities/CVE-2022-24303/48199",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'iPython' to v7.31.1 to include a security fix.",
            "cve": "CVE-2022-21699",
            "id": "pyup.io-48208",
            "more_info_path": "/vulnerabilities/CVE-2022-21699/48208",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-22817",
            "id": "pyup.io-48200",
            "more_info_path": "/vulnerabilities/CVE-2022-22817/48200",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-48204",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/48204",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'notebook' to v6.4.10 to include security fixes.",
            "cve": "CVE-2022-24758",
            "id": "pyup.io-48198",
            "more_info_path": "/vulnerabilities/CVE-2022-24758/48198",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Pytoxo 1.2 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-48207",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/48207",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        }
    ],
    "pytrackdat": [
        {
            "advisory": "Pytrackdat 0.2.0 validates the security of the administrator passwords.",
            "cve": "PVE-2021-37141",
            "id": "pyup.io-37141",
            "more_info_path": "/vulnerabilities/PVE-2021-37141/37141",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "pytsite": [
        {
            "advisory": "pytsite before 1.2 has a critical web login security issue.",
            "cve": "PVE-2021-34825",
            "id": "pyup.io-34825",
            "more_info_path": "/vulnerabilities/PVE-2021-34825/34825",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        }
    ],
    "pyttman": [
        {
            "advisory": "Pyttman version 1.1.7 makes clients to not start in parallel when using Threading due to issues with security and runtime on unix and linux based systems.",
            "cve": "PVE-2021-41969",
            "id": "pyup.io-41969",
            "more_info_path": "/vulnerabilities/PVE-2021-41969/41969",
            "specs": [
                "<1.1.7"
            ],
            "v": "<1.1.7"
        }
    ],
    "pyu4v": [
        {
            "advisory": "Pyu4v 9.1.2.0 introduced the option to create a secure snapshot by means of `create_storage_group_snapshot`.",
            "cve": "PVE-2021-37914",
            "id": "pyup.io-37914",
            "more_info_path": "/vulnerabilities/PVE-2021-37914/37914",
            "specs": [
                "<9.1.2.0"
            ],
            "v": "<9.1.2.0"
        }
    ],
    "pyupdater": [
        {
            "advisory": "pyupdater before 0.20.0 is vulnerable to session fixation attacks and potentially cookie stealing.",
            "cve": "PVE-2021-26092",
            "id": "pyup.io-26092",
            "more_info_path": "/vulnerabilities/PVE-2021-26092/26092",
            "specs": [
                "<0.20.0"
            ],
            "v": "<0.20.0"
        }
    ],
    "pyurllib": [
        {
            "advisory": "Pyurllib is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51693",
            "id": "pyup.io-51693",
            "more_info_path": "/vulnerabilities/PVE-2022-51693/51693",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pyvbmc": [
        {
            "advisory": "Updated the actions/download-artifact in Pyvbmc from actions/download-artifact@v3 to actions/download-artifact@v4 to address CVE-2024-42471.",
            "cve": "CVE-2024-42471",
            "id": "pyup.io-73373",
            "more_info_path": "/vulnerabilities/CVE-2024-42471/73373",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        }
    ],
    "pyvcloud": [
        {
            "advisory": "Pyvcloud 20.0.0 fixes CVE-2017-18342: Replace yaml.load() with yaml.safe_load()",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-36809",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/36809",
            "specs": [
                "<20.0.0"
            ],
            "v": "<20.0.0"
        }
    ],
    "pywa": [
        {
            "advisory": "Affected versions of the pywa package are vulnerable to Cross-site Scripting (XSS) due to reflecting untrusted input in webhook responses using an HTML content type. The Flask and FastAPI routes pywa_challenge and pywa_webhook in pywa/server.py and pywa_async/server.py return the values from webhook_challenge_handler and webhook_update_handler directly in the HTTP body without enforcing a safe content type or setting X-Content-Type-Options, allowing script markup supplied via the hub.challenge parameter to be interpreted by browsers.",
            "cve": "PVE-2025-79025",
            "id": "pyup.io-79025",
            "more_info_path": "/vulnerabilities/PVE-2025-79025/79025",
            "specs": [
                "<3.0.0rc.1"
            ],
            "v": "<3.0.0rc.1"
        }
    ],
    "pywasm3": [
        {
            "advisory": "Affected versions of the wasm3 package are vulnerable to Uncontrolled Memory Allocation due to improper memory management in the Read_utf8 function. The Read_utf8 function at commit 139076a fails to properly release allocated memory after processing UTF-8 encoded strings, resulting in a memory leak during string parsing operations. An attacker can exploit this vulnerability by repeatedly triggering the Read_utf8 function with crafted UTF-8 input strings, causing continuous memory consumption that eventually leads to resource exhaustion and potential denial of service of the WebAssembly runtime environment.",
            "cve": "CVE-2024-27529",
            "id": "pyup.io-78815",
            "more_info_path": "/vulnerabilities/CVE-2024-27529/78815",
            "specs": [
                "<=0.5.0"
            ],
            "v": "<=0.5.0"
        },
        {
            "advisory": "WASM3 v0.5.0 was discovered to contain a segmentation fault via the component op_Select_i32_srs in wasm3/source/m3_exec.h.\r\nhttps://github.com/wasm3/wasm3/issues/379",
            "cve": "CVE-2022-39974",
            "id": "pyup.io-54543",
            "more_info_path": "/vulnerabilities/CVE-2022-39974/54543",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        },
        {
            "advisory": "WASM3 v0.5.0 was discovered to contain a heap overflow via the component /wabt/bin/poc.wasm.",
            "cve": "CVE-2022-28990",
            "id": "pyup.io-54453",
            "more_info_path": "/vulnerabilities/CVE-2022-28990/54453",
            "specs": [
                ">=0,<=0.5.0"
            ],
            "v": ">=0,<=0.5.0"
        }
    ],
    "pywb": [
        {
            "advisory": "Webrecorder pywb before 2.6.0 allows XSS because it does not ensure that Jinja2 templates are autoescaped.",
            "cve": "CVE-2021-39286",
            "id": "pyup.io-42320",
            "more_info_path": "/vulnerabilities/CVE-2021-39286/42320",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        }
    ],
    "pywbem": [
        {
            "advisory": "Pywbem 0.13.0 updates its dependency 'html5lib' to v0.999999999 to include security fixes.",
            "cve": "CVE-2016-9910",
            "id": "pyup.io-44954",
            "more_info_path": "/vulnerabilities/CVE-2016-9910/44954",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Pywbem 0.13.0 updates its dependency 'html5lib' to v0.999999999 to include security fixes.",
            "cve": "CVE-2016-9909",
            "id": "pyup.io-44953",
            "more_info_path": "/vulnerabilities/CVE-2016-9909/44953",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Pywbem 0.13.0 updates its dependency 'mistune' to v0.8.1 to include security fixes.",
            "cve": "CVE-2017-15612",
            "id": "pyup.io-44956",
            "more_info_path": "/vulnerabilities/CVE-2017-15612/44956",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Pywbem 0.13.0 updates its dependency 'mistune' to v0.8.1 to include security fixes.",
            "cve": "CVE-2017-16876",
            "id": "pyup.io-44955",
            "more_info_path": "/vulnerabilities/CVE-2017-16876/44955",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Pywbem 0.14.3 updates its dependency 'requests' to v2.20.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-38444",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/38444",
            "specs": [
                "<0.14.3"
            ],
            "v": "<0.14.3"
        },
        {
            "advisory": "Pywbem 0.14.3 updates its dependency 'bleach' to v2.1.4 to include a security fix.",
            "cve": "CVE-2018-7753",
            "id": "pyup.io-42686",
            "more_info_path": "/vulnerabilities/CVE-2018-7753/42686",
            "specs": [
                "<0.14.3"
            ],
            "v": "<0.14.3"
        },
        {
            "advisory": "Pywbem 0.14.3 updates its dependency 'urllib3' to v1.23 to include a security fix.",
            "cve": "CVE-2018-20060",
            "id": "pyup.io-42685",
            "more_info_path": "/vulnerabilities/CVE-2018-20060/42685",
            "specs": [
                "<0.14.3"
            ],
            "v": "<0.14.3"
        },
        {
            "advisory": "Pywbem 0.17.0 changes the HTTPS support of `pywbem.WBEMListener` from using the deprecated `ssl.wrap_socket()` function to using the `ssl.SSLContext` class that was introduced in Python 2.7.9. This causes more secure SSL settings to be used. On Python versions before 2.7.9, pywbem will continue to use the deprecated `ssl.wrap_socket()` function.",
            "cve": "PVE-2021-38576",
            "id": "pyup.io-38576",
            "more_info_path": "/vulnerabilities/PVE-2021-38576/38576",
            "specs": [
                "<0.17.0"
            ],
            "v": "<0.17.0"
        },
        {
            "advisory": "Pywbem 1.2.0.dev1 updates its dependency 'bleach' to include a security fix.\r\nNote that this package is only needed for test and development of pywbem.",
            "cve": "CVE-2020-6817",
            "id": "pyup.io-42725",
            "more_info_path": "/vulnerabilities/CVE-2020-6817/42725",
            "specs": [
                "<1.2.0.dev1"
            ],
            "v": "<1.2.0.dev1"
        },
        {
            "advisory": "Pywbem 1.2.0.dev1 updates its dependency 'lxml' to v4.6.2 to include a security fix.\r\nNote that this package is only needed for test and development of pywbem.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-42724",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/42724",
            "specs": [
                "<1.2.0.dev1"
            ],
            "v": "<1.2.0.dev1"
        },
        {
            "advisory": "Pywbem 1.2.0.dev1 updates its dependency 'urllib3' to include a security fix.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-39383",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/39383",
            "specs": [
                "<1.2.0.dev1"
            ],
            "v": "<1.2.0.dev1"
        },
        {
            "advisory": "Pywbem 1.2.0.dev1 updates the minimum requirements for its dependency 'typed-ast' to include a security fix.\r\nNote that this package is only needed for test and development of pywbem.",
            "cve": "CVE-2019-19275",
            "id": "pyup.io-42726",
            "more_info_path": "/vulnerabilities/CVE-2019-19275/42726",
            "specs": [
                "<1.2.0.dev1"
            ],
            "v": "<1.2.0.dev1"
        },
        {
            "advisory": "PyWBEM 0.7 and earlier does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.",
            "cve": "CVE-2013-6444",
            "id": "pyup.io-54065",
            "more_info_path": "/vulnerabilities/CVE-2013-6444/54065",
            "specs": [
                ">=0,<0.8.1"
            ],
            "v": ">=0,<0.8.1"
        },
        {
            "advisory": "PyWBEM 0.7 and earlier uses a separate connection to validate X.509 certificates, which allows man-in-the-middle attackers to spoof a peer via an arbitrary certificate.",
            "cve": "CVE-2013-6418",
            "id": "pyup.io-54064",
            "more_info_path": "/vulnerabilities/CVE-2013-6418/54064",
            "specs": [
                ">=0,<0.8.1"
            ],
            "v": ">=0,<0.8.1"
        }
    ],
    "pywbemtools": [
        {
            "advisory": "Pywbemtools 0.6.0 updates its dependency 'urllib3' to v1.24.2 to include a security fix.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-38169",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/38169",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "pywebdav": [
        {
            "advisory": "Multiple SQL injection vulnerabilities in the get_userinfo method in the MySQLAuthHandler class in DAVServer/mysqlauth.py in PyWebDAV before 0.9.4.1 allow remote attackers to execute arbitrary SQL commands via the (1) user or (2) pw argument.  NOTE: some of these details are obtained from third party information.",
            "cve": "CVE-2011-0432",
            "id": "pyup.io-42234",
            "more_info_path": "/vulnerabilities/CVE-2011-0432/42234",
            "specs": [
                "<0.9.4.1"
            ],
            "v": "<0.9.4.1"
        }
    ],
    "pywebsite": [
        {
            "advisory": "pywebsite 0.1.14pre's signed_url  method is now (more) immune to VS timing attacks.",
            "cve": "PVE-2021-26094",
            "id": "pyup.io-26094",
            "more_info_path": "/vulnerabilities/PVE-2021-26094/26094",
            "specs": [
                "<0.1.14pre"
            ],
            "v": "<0.1.14pre"
        },
        {
            "advisory": "Pywebsite 0.1.24 fixes possible SQL injection if an unsafe table name is used.",
            "cve": "PVE-2021-26817",
            "id": "pyup.io-26817",
            "more_info_path": "/vulnerabilities/PVE-2021-26817/26817",
            "specs": [
                "<0.1.24"
            ],
            "v": "<0.1.24"
        },
        {
            "advisory": "pywebsite before 0.1.9pre is vulnerable to length extension attacks, and value equivalence attacks.",
            "cve": "PVE-2021-26095",
            "id": "pyup.io-26095",
            "more_info_path": "/vulnerabilities/PVE-2021-26095/26095",
            "specs": [
                "<0.1.9pre"
            ],
            "v": "<0.1.9pre"
        },
        {
            "advisory": "A timing attack vulnerability has been detected in specific versions of pywebsite, a tool used for creating websites with Python. This vulnerability could potentially compromise security by allowing attackers to infer sensitive information based on the time it takes for the system to respond.",
            "cve": "PVE-2024-99894",
            "id": "pyup.io-65525",
            "more_info_path": "/vulnerabilities/PVE-2024-99894/65525",
            "specs": [
                ">=0,<0.1.14pre"
            ],
            "v": ">=0,<0.1.14pre"
        }
    ],
    "pywebtransport": [
        {
            "advisory": "Affected versions of the pywebtransport package are vulnerable to a memory exhaustion denial-of-service due to missing HTTP/3 capsule size limits. The protocol engine\u2019s capsule parsing/handling path in the _protocol module accepts attacker-controlled capsule payloads without enforcing a maximum size, and the configuration surface previously did not provide a mandatory max_capsule_size guardrail.",
            "cve": "PVE-2026-83808",
            "id": "pyup.io-83808",
            "more_info_path": "/vulnerabilities/PVE-2026-83808/83808",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        }
    ],
    "pywikibot": [
        {
            "advisory": "Affected versions of the pywikibot package are vulnerable to Remote Code Execution due to the use of eval() on password file entries in the pywikibot.login.readPassword method. The readPassword method in the pywikibot.login module evaluated each non-empty, non-comment line from the configured password file (historically user-password.py) with Python\u2019s eval function, without restricting the allowed syntax, so arbitrary expressions from that file ran directly in the pywikibot process before this was changed to ast.literal_eval and additional sanity checks were added.",
            "cve": "PVE-2025-81856",
            "id": "pyup.io-81856",
            "more_info_path": "/vulnerabilities/PVE-2025-81856/81856",
            "specs": [
                "<10.7.1"
            ],
            "v": "<10.7.1"
        },
        {
            "advisory": "Pywikibot 3.0.20170403 includes a fix for catastrophic backtracking vulnerability.",
            "cve": "PVE-2023-59310",
            "id": "pyup.io-59310",
            "more_info_path": "/vulnerabilities/PVE-2023-59310/59310",
            "specs": [
                "<3.0.20170403"
            ],
            "v": "<3.0.20170403"
        },
        {
            "advisory": "Pywikibot 3.0.20181203 require requests version 2.20.0 or later for security reasons.",
            "cve": "PVE-2021-38151",
            "id": "pyup.io-38151",
            "more_info_path": "/vulnerabilities/PVE-2021-38151/38151",
            "specs": [
                "<3.0.20181203"
            ],
            "v": "<3.0.20181203"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2020-35654",
            "id": "pyup.io-46447",
            "more_info_path": "/vulnerabilities/CVE-2020-35654/46447",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2020-35655",
            "id": "pyup.io-46448",
            "more_info_path": "/vulnerabilities/CVE-2020-35655/46448",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2020-10378",
            "id": "pyup.io-46437",
            "more_info_path": "/vulnerabilities/CVE-2020-10378/46437",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-46438",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/46438",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2020-11538",
            "id": "pyup.io-46450",
            "more_info_path": "/vulnerabilities/CVE-2020-11538/46450",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2021-27923",
            "id": "pyup.io-46451",
            "more_info_path": "/vulnerabilities/CVE-2021-27923/46451",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2021-27921",
            "id": "pyup.io-46443",
            "more_info_path": "/vulnerabilities/CVE-2021-27921/46443",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-46439",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/46439",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2020-10994",
            "id": "pyup.io-46449",
            "more_info_path": "/vulnerabilities/CVE-2020-10994/46449",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-46440",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/46440",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2020-10379",
            "id": "pyup.io-40579",
            "more_info_path": "/vulnerabilities/CVE-2020-10379/40579",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2020-35653",
            "id": "pyup.io-46446",
            "more_info_path": "/vulnerabilities/CVE-2020-35653/46446",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-46442",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/46442",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2021-27922",
            "id": "pyup.io-46444",
            "more_info_path": "/vulnerabilities/CVE-2021-27922/46444",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-46452",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/46452",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Pywikibot 6.1.0 updates its dependency 'Pillow' to versions >=8.1.1 to include security fixes.",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-46441",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/46441",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        }
    ],
    "pywin32": [
        {
            "advisory": "An integer overflow exists in pywin32 prior to version b301 when adding an access control entry (ACE) to an access control list (ACL) that would cause the size to be greater than 65535 bytes. An attacker who successfully exploited this vulnerability could crash the vulnerable process.",
            "cve": "CVE-2021-32559",
            "id": "pyup.io-54687",
            "more_info_path": "/vulnerabilities/CVE-2021-32559/54687",
            "specs": [
                ">=0,<301"
            ],
            "v": ">=0,<301"
        }
    ],
    "pywps": [
        {
            "advisory": "An XML external entity (XXE) injection in PyWPS before 4.4.5 allows an attacker to view files on the application server filesystem by assigning a path to the entity. OWSLib 0.24.1 may also be affected.",
            "cve": "CVE-2021-39371",
            "id": "pyup.io-41208",
            "more_info_path": "/vulnerabilities/CVE-2021-39371/41208",
            "specs": [
                "<4.4.5"
            ],
            "v": "<4.4.5"
        }
    ],
    "pywren-ibm-cloud": [
        {
            "advisory": "Pywren-ibm-cloud 1.0.1 fixes flask security issues (a dependency). See CVE-2018-1000656.",
            "cve": "CVE-2018-1000656",
            "id": "pyup.io-37480",
            "more_info_path": "/vulnerabilities/CVE-2018-1000656/37480",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        },
        {
            "advisory": "Pywren-ibm-cloud 1.0.19 fixes the CVE-2019-12855 security alert.",
            "cve": "CVE-2019-12855",
            "id": "pyup.io-37479",
            "more_info_path": "/vulnerabilities/CVE-2019-12855/37479",
            "specs": [
                "<1.0.19"
            ],
            "v": "<1.0.19"
        }
    ],
    "pywry": [
        {
            "advisory": "Pywry 0.6.2 updates its C dependency 'libwebp' to include a fix for a high-risk vulnerability.\r\nhttps://github.com/OpenBB-finance/pywry/pull/99",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61928",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61928",
            "specs": [
                "<0.6.2"
            ],
            "v": "<0.6.2"
        }
    ],
    "pyxdsm": [
        {
            "advisory": "Pyxdsm version 2.2.0 includes a security patch for the function '_write_tikz' in 'pyxdsm/matrix_eqn.py'. It contained an OS injection vulnerability: unsafe use of os.system().\r\nhttps://github.com/mdolab/pyXDSM/commit/9c59eb6764e64907c7c103f15bb3dee109ea24a7#diff-9489c2e554d0f234b6dd3212dafdbdd069df6e93d4046ece0921f04bacc15b70",
            "cve": "PVE-2021-41381",
            "id": "pyup.io-41381",
            "more_info_path": "/vulnerabilities/PVE-2021-41381/41381",
            "specs": [
                "<2.2.0"
            ],
            "v": "<2.2.0"
        }
    ],
    "pyxmlsecurity": [
        {
            "advisory": "Pyxmlsecurity 0.9 protects against wrapping attacks.\r\nhttps://github.com/leifj/pyXMLSecurity/commit/3fe6c3b56e1404121887f74a0db196cc19c011fa",
            "cve": "PVE-2021-26096",
            "id": "pyup.io-26096",
            "more_info_path": "/vulnerabilities/PVE-2021-26096/26096",
            "specs": [
                "<0.9"
            ],
            "v": "<0.9"
        },
        {
            "advisory": "Various versions of pyxmlsecurity are susceptible to an XML Signature Wrapping vulnerability when using the verify function. This flaw could compromise the integrity of XML documents by enabling unauthorized modifications.",
            "cve": "PVE-2024-99893",
            "id": "pyup.io-65526",
            "more_info_path": "/vulnerabilities/PVE-2024-99893/65526",
            "specs": [
                ">=0.7,<0.9"
            ],
            "v": ">=0.7,<0.9"
        }
    ],
    "pyxnat": [
        {
            "advisory": "Pyxnat 1.1.0.0 updates its dependency 'lxml' to version 4.3.2 to include security fixes.",
            "cve": "CVE-2018-19787",
            "id": "pyup.io-48332",
            "more_info_path": "/vulnerabilities/CVE-2018-19787/48332",
            "specs": [
                "<1.1.0.0"
            ],
            "v": "<1.1.0.0"
        },
        {
            "advisory": "Pyxnat 1.1.0.0 updates its dependency 'requests' to versions >=2.20 to include security fixes.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-37196",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/37196",
            "specs": [
                "<1.1.0.0"
            ],
            "v": "<1.1.0.0"
        },
        {
            "advisory": "Pyxnat 1.1.0.0 updates its dependency 'requests' to versions >=2.20 to include security fixes.",
            "cve": "CVE-2015-2296",
            "id": "pyup.io-48329",
            "more_info_path": "/vulnerabilities/CVE-2015-2296/48329",
            "specs": [
                "<1.1.0.0"
            ],
            "v": "<1.1.0.0"
        },
        {
            "advisory": "Pyxnat 1.1.0.0 updates its dependency 'requests' to versions >=2.20 to include security fixes.",
            "cve": "CVE-2014-1829",
            "id": "pyup.io-48331",
            "more_info_path": "/vulnerabilities/CVE-2014-1829/48331",
            "specs": [
                "<1.1.0.0"
            ],
            "v": "<1.1.0.0"
        },
        {
            "advisory": "Pyxnat 1.1.0.0 updates its dependency 'lxml' to version 4.3.2 to include security fixes.",
            "cve": "CVE-2014-3146",
            "id": "pyup.io-48333",
            "more_info_path": "/vulnerabilities/CVE-2014-3146/48333",
            "specs": [
                "<1.1.0.0"
            ],
            "v": "<1.1.0.0"
        },
        {
            "advisory": "Pyxnat 1.1.0.0 updates its dependency 'requests' to versions >=2.20 to include security fixes.",
            "cve": "CVE-2014-1830",
            "id": "pyup.io-48330",
            "more_info_path": "/vulnerabilities/CVE-2014-1830/48330",
            "specs": [
                "<1.1.0.0"
            ],
            "v": "<1.1.0.0"
        }
    ],
    "pyyalm": [
        {
            "advisory": "Pyyalm is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51755",
            "id": "pyup.io-51755",
            "more_info_path": "/vulnerabilities/PVE-2022-51755/51755",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "pyyaml": [
        {
            "advisory": "Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-36333",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/36333",
            "specs": [
                "<4"
            ],
            "v": "<4"
        },
        {
            "advisory": "Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-38100",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/38100",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        },
        {
            "advisory": "Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1860466",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-39611",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/39611",
            "specs": [
                "<5.4"
            ],
            "v": "<5.4"
        },
        {
            "advisory": "PyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all functions because of a class deserialization issue, e.g., Popen is a class in the subprocess module. See CVE-2019-20477. NOTE: this issue exists because of an incomplete fix for CVE-2017-18342.",
            "cve": "CVE-2019-20477",
            "id": "pyup.io-38639",
            "more_info_path": "/vulnerabilities/CVE-2019-20477/38639",
            "specs": [
                ">=5.1,<=5.1.2"
            ],
            "v": ">=5.1,<=5.1.2"
        }
    ],
    "pyyaml-ft": [
        {
            "advisory": "A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-76952",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/76952",
            "specs": [
                "<5.3.1"
            ],
            "v": "<5.3.1"
        }
    ],
    "pyzkaccess": [
        {
            "advisory": "Affected versions of Pyzkaccess are vulnerable to information disclosure. Connection strings are print in exception messages.",
            "cve": "PVE-2024-74093",
            "id": "pyup.io-74093",
            "more_info_path": "/vulnerabilities/PVE-2024-74093/74093",
            "specs": [
                "<1.1"
            ],
            "v": "<1.1"
        }
    ],
    "qctrl-open-controls": [
        {
            "advisory": "Qctrl-open-controls 8.5.0 updates its dependency 'pillow' to v8.4.0 to include security fixes.",
            "cve": "CVE-2021-34552",
            "id": "pyup.io-42816",
            "more_info_path": "/vulnerabilities/CVE-2021-34552/42816",
            "specs": [
                "<8.5.0"
            ],
            "v": "<8.5.0"
        },
        {
            "advisory": "Qctrl-open-controls 8.5.0 updates its dependency 'pillow' to v8.4.0 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-42694",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/42694",
            "specs": [
                "<8.5.0"
            ],
            "v": "<8.5.0"
        }
    ],
    "qdrant-client": [
        {
            "advisory": "qdrant/qdrant version 1.9.0-dev is vulnerable to arbitrary file read and write during the snapshot recovery process. Attackers can exploit this vulnerability by manipulating snapshot files to include symlinks, leading to arbitrary file read by adding a symlink that points to a desired file on the filesystem and arbitrary file write by including a symlink and a payload file in the snapshot's directory structure. This vulnerability allows for the reading and writing of arbitrary files on the server, which could potentially lead to a full takeover of the system.",
            "cve": "CVE-2024-3829",
            "id": "pyup.io-71846",
            "more_info_path": "/vulnerabilities/CVE-2024-3829/71846",
            "specs": [
                "<1.9.0"
            ],
            "v": "<1.9.0"
        }
    ],
    "qi": [
        {
            "advisory": "Qi 2.0.0 includes sets libqi version to '1.8.3', that prevents Man-in-the-Middle TLS Protocol Downgrade attacks.\r\nhttps://github.com/aldebaran/libqi-python/commit/9f204b174b04b6bb0cccf4ddb48dc8c1cf6bcb4e\r\nhttps://github.com/aldebaran/libqi/commit/4cf5aa7b1da686890b46954909b80e04a3f325f2",
            "cve": "PVE-2023-52952",
            "id": "pyup.io-52952",
            "more_info_path": "/vulnerabilities/PVE-2023-52952/52952",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        }
    ],
    "qi-jabberhelpdesk": [
        {
            "advisory": "qi-jabberhelpdesk  0.30 includes unspecified security fixes, some vulnerable xml-rpc calls fixed. [ggozad]",
            "cve": "PVE-2021-36052",
            "id": "pyup.io-36052",
            "more_info_path": "/vulnerabilities/PVE-2021-36052/36052",
            "specs": [
                "<0.30"
            ],
            "v": "<0.30"
        },
        {
            "advisory": "qi.jabberhelpdesk before 0.30 has several undisclosed vulnerabilities in xml-rpc calls.",
            "cve": "PVE-2021-26097",
            "id": "pyup.io-26097",
            "more_info_path": "/vulnerabilities/PVE-2021-26097/26097",
            "specs": [
                "<0.30"
            ],
            "v": "<0.30"
        }
    ],
    "qiling": [
        {
            "advisory": "Qiling 1.4.4 increases host security around filesystem access.\r\nhttps://github.com/qilingframework/qiling/pull/1195/commits/8031d01ea13cfdde1209412e4c4516f58c823619",
            "cve": "PVE-2022-51179",
            "id": "pyup.io-51179",
            "more_info_path": "/vulnerabilities/PVE-2022-51179/51179",
            "specs": [
                "<1.4.4"
            ],
            "v": "<1.4.4"
        },
        {
            "advisory": "Qiling 1.4.4 includes safer path semantics to avoid path traversal attacks.\r\nhttps://github.com/qilingframework/qiling/pull/1182/commits/3c3b6347eb96d9501da494da3e64a7fed60178a0",
            "cve": "PVE-2022-51232",
            "id": "pyup.io-51232",
            "more_info_path": "/vulnerabilities/PVE-2022-51232/51232",
            "specs": [
                "<1.4.4"
            ],
            "v": "<1.4.4"
        }
    ],
    "qiskit": [
        {
            "advisory": "A maliciously crafted QPY file containing can potentially execute arbitrary-code embedded in the payload without privilege escalation when deserializing QPY formats < 13. A python process calling Qiskit's qiskit.qpy.load() function could potentially execute any arbitrary Python code embedded in the correct place in the binary file as part of a specially constructed payload.",
            "cve": "CVE-2025-2000",
            "id": "pyup.io-76306",
            "more_info_path": "/vulnerabilities/CVE-2025-2000/76306",
            "specs": [
                ">=0.18.0,<1.4.1",
                ">=2.0.0rc1,<2.0.0rc2"
            ],
            "v": ">=0.18.0,<1.4.1,>=2.0.0rc1,<2.0.0rc2"
        },
        {
            "advisory": "A maliciously crafted QPY file containing a malformed symengine serialization stream as part of the larger QPY serialization of a ParameterExpression object can cause a segfault within the symengine library, allowing an attacker to terminate the hosting process deserializing the QPY payload.",
            "cve": "CVE-2025-1403",
            "id": "pyup.io-76331",
            "more_info_path": "/vulnerabilities/CVE-2025-1403/76331",
            "specs": [
                ">=0.45.0,<1.3.0"
            ],
            "v": ">=0.45.0,<1.3.0"
        }
    ],
    "qiskit-ibm-runtime": [
        {
            "advisory": "A vulnerability has been identified in qiskit_ibm_runtime.RuntimeDecoder where deserializing JSON data can lead to arbitrary code execution. The RuntimeDecoder is intended to deserialize JSON strings that contain various special types encoded via RuntimeEncoder. However, an attacker can craft a malicious payload that causes the decoder to spawn a subprocess and execute arbitrary code.",
            "cve": "CVE-2024-29032",
            "id": "pyup.io-71930",
            "more_info_path": "/vulnerabilities/CVE-2024-29032/71930",
            "specs": [
                ">=0.1.0,<0.21.2"
            ],
            "v": ">=0.1.0,<0.21.2"
        },
        {
            "advisory": "An eval() method exists Options._get_program_inputs. This is bad in any case, but especially bad because Options are also used server side, so this has the potential to expose arbitrary code injection in runtime containers, now or at a later time.",
            "cve": "PVE-2024-71989",
            "id": "pyup.io-71989",
            "more_info_path": "/vulnerabilities/PVE-2024-71989/71989",
            "specs": [
                ">=0.11.0,<0.11.1"
            ],
            "v": ">=0.11.0,<0.11.1"
        }
    ],
    "qiskit-terra": [
        {
            "advisory": "A maliciously crafted QPY file containing can potentially execute arbitrary-code embedded in the payload without privilege escalation when deserializing QPY formats < 13. A python process calling Qiskit's qiskit.qpy.load() function could potentially execute any arbitrary Python code embedded in the correct place in the binary file as part of a specially constructed payload.",
            "cve": "CVE-2025-2000",
            "id": "pyup.io-76305",
            "more_info_path": "/vulnerabilities/CVE-2025-2000/76305",
            "specs": [
                ">=0.18.0,<0.46.3"
            ],
            "v": ">=0.18.0,<0.46.3"
        },
        {
            "advisory": "A maliciously crafted QPY file containing a malformed symengine serialization stream as part of the larger QPY serialization of a ParameterExpression object can cause a segfault within the symengine library, allowing an attacker to terminate the hosting process deserializing the QPY payload.",
            "cve": "CVE-2025-1403",
            "id": "pyup.io-76332",
            "more_info_path": "/vulnerabilities/CVE-2025-1403/76332",
            "specs": [
                ">=0.45.0,<0.46.3"
            ],
            "v": ">=0.45.0,<0.46.3"
        }
    ],
    "qlib": [
        {
            "advisory": "This affects all versions of package qlib. The workflow function in cli part of qlib was using an unsafe YAML load function. See CVE-2021-23338.",
            "cve": "CVE-2021-23338",
            "id": "pyup.io-39620",
            "more_info_path": "/vulnerabilities/CVE-2021-23338/39620",
            "specs": [
                ">=0.0.0"
            ],
            "v": ">=0.0.0"
        }
    ],
    "qmp": [
        {
            "advisory": "qemu-kvm before 0.11.0 disables VNC authentication when the password is cleared, which allows remote attackers to bypass authentication and establish VNC sessions.",
            "cve": "CVE-2011-0011",
            "id": "pyup.io-62103",
            "more_info_path": "/vulnerabilities/CVE-2011-0011/62103",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "qne-adk": [
        {
            "advisory": "Qne-adk 0.3.0 includes a fix for CVE-2007-4559, a path traversal vulnerability.\r\nhttps://github.com/QuTech-Delft/qne-adk/commit/75f978c2c976cb59181b7741d2be623e9265636a",
            "cve": "PVE-2023-53018",
            "id": "pyup.io-53018",
            "more_info_path": "/vulnerabilities/PVE-2023-53018/53018",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "qoqo-aqt": [
        {
            "advisory": "Qoqo-aqt 0.6.2 updates its CARGO dependency 'openssl' to v0.10.48 to include security fixes.\r\nhttps://rustsec.org/advisories/RUSTSEC-2023-0022.html",
            "cve": "PVE-2023-54745",
            "id": "pyup.io-54745",
            "more_info_path": "/vulnerabilities/PVE-2023-54745/54745",
            "specs": [
                "<0.6.2"
            ],
            "v": "<0.6.2"
        },
        {
            "advisory": "Qoqo-aqt 0.6.2 updates its CARGO dependency 'openssl' to v0.10.48 to include security fixes.\r\nhttps://rustsec.org/advisories/RUSTSEC-2023-0024.html",
            "cve": "PVE-2023-54747",
            "id": "pyup.io-54747",
            "more_info_path": "/vulnerabilities/PVE-2023-54747/54747",
            "specs": [
                "<0.6.2"
            ],
            "v": "<0.6.2"
        },
        {
            "advisory": "Qoqo-aqt 0.6.2 updates its CARGO dependency 'openssl' to v0.10.48 to include security fixes.\r\nhttps://rustsec.org/advisories/RUSTSEC-2023-0023.html",
            "cve": "PVE-2023-54746",
            "id": "pyup.io-54746",
            "more_info_path": "/vulnerabilities/PVE-2023-54746/54746",
            "specs": [
                "<0.6.2"
            ],
            "v": "<0.6.2"
        }
    ],
    "qoqo-qryd": [
        {
            "advisory": "Qoqo-qryd 0.15.1 has updated its h2 dependency to version 0.3.26 from 0.3.24 to address a Denial of Service (DoS) vulnerability identified in versions older than 0.3.24.",
            "cve": "PVE-2024-67534",
            "id": "pyup.io-67534",
            "more_info_path": "/vulnerabilities/PVE-2024-67534/67534",
            "specs": [
                "<0.15.1"
            ],
            "v": "<0.15.1"
        },
        {
            "advisory": "Qoqo-qryd 0.8.4 updates its CARGO dependency 'openssl' to v0.10.48 to include security fixes.\r\nhttps://rustsec.org/advisories/RUSTSEC-2023-0024.html",
            "cve": "PVE-2023-53900",
            "id": "pyup.io-53900",
            "more_info_path": "/vulnerabilities/PVE-2023-53900/53900",
            "specs": [
                "<0.8.4"
            ],
            "v": "<0.8.4"
        },
        {
            "advisory": "Qoqo-qryd 0.8.4 updates its CARGO dependency 'openssl' to v0.10.48 to include security fixes.\r\nhttps://rustsec.org/advisories/RUSTSEC-2023-0022.html",
            "cve": "PVE-2023-53881",
            "id": "pyup.io-53881",
            "more_info_path": "/vulnerabilities/PVE-2023-53881/53881",
            "specs": [
                "<0.8.4"
            ],
            "v": "<0.8.4"
        },
        {
            "advisory": "Qoqo-qryd 0.8.4 updates its CARGO dependency 'openssl' to v0.10.48 to include security fixes.\r\nhttps://rustsec.org/advisories/RUSTSEC-2023-0023.html",
            "cve": "PVE-2023-53901",
            "id": "pyup.io-53901",
            "more_info_path": "/vulnerabilities/PVE-2023-53901/53901",
            "specs": [
                "<0.8.4"
            ],
            "v": "<0.8.4"
        }
    ],
    "qpid-python": [
        {
            "advisory": "Apache Qpid before 0.16 does not properly verify credentials during the joining of a cluster, which allows remote attackers to obtain access to the messaging functionality and job functionality of a cluster by leveraging knowledge of a cluster-username.",
            "cve": "CVE-2011-3620",
            "id": "pyup.io-62094",
            "more_info_path": "/vulnerabilities/CVE-2011-3620/62094",
            "specs": [
                "<0.16"
            ],
            "v": "<0.16"
        },
        {
            "advisory": "Qpid-python 0.22 includes a fix for CVE-2013-1909: The Python client in Apache Qpid before 0.22 does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.\r\nhttps://issues.apache.org/jira/browse/QPID-4918",
            "cve": "CVE-2013-1909",
            "id": "pyup.io-35417",
            "more_info_path": "/vulnerabilities/CVE-2013-1909/35417",
            "specs": [
                "<0.22"
            ],
            "v": "<0.22"
        },
        {
            "advisory": "sys/ssl/SslSocket.cpp in qpidd in Apache Qpid, as used in Red Hat Enterprise MRG before 1.2.2 and other products, when SSL is enabled, allows remote attackers to cause a denial of service (daemon outage) by connecting to the SSL port but not participating in an SSL handshake.",
            "cve": "CVE-2010-3083",
            "id": "pyup.io-61705",
            "more_info_path": "/vulnerabilities/CVE-2010-3083/61705",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        },
        {
            "advisory": "A vulnerability has been identified in specific versions of qpid_python, where SSL or TLS connections do not automatically verify the server's hostname due to default settings. This oversight could allow an attacker to perform Man-in-the-Middle attacks by establishing connections without proper verification.",
            "cve": "PVE-2024-99892",
            "id": "pyup.io-65527",
            "more_info_path": "/vulnerabilities/PVE-2024-99892/65527",
            "specs": [
                ">=0.20,<1.35.0"
            ],
            "v": ">=0.20,<1.35.0"
        }
    ],
    "quandl-fund-xlsx": [
        {
            "advisory": "quandl-fund-xlsx 0.2.1  - Minor security fix, requests version now >=2.20.0",
            "cve": "PVE-2021-36655",
            "id": "pyup.io-36655",
            "more_info_path": "/vulnerabilities/PVE-2021-36655/36655",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "quantities": [
        {
            "advisory": "A vulnerability in the quantities library\u2019s UnitRegistry class allows arbitrary code execution due to the insecure use of eval in the __getitem__ method. Malicious input could exploit this flaw, leading to potential system compromise. The issue is mitigated by introducing checks to block harmful code execution.",
            "cve": "PVE-2024-72822",
            "id": "pyup.io-72822",
            "more_info_path": "/vulnerabilities/PVE-2024-72822/72822",
            "specs": [
                "<0.16.0"
            ],
            "v": "<0.16.0"
        }
    ],
    "quark": [
        {
            "advisory": "comelz Quark before 2019-03-26 allows directory traversal to locations outside of the project directory.",
            "cve": "CVE-2019-15520",
            "id": "pyup.io-70504",
            "more_info_path": "/vulnerabilities/CVE-2019-15520/70504",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "quart": [
        {
            "advisory": "Affected versions of Quart are vulnerable to possible resource exhaustion when parsing file data in forms.",
            "cve": "CVE-2024-49767",
            "id": "pyup.io-73878",
            "more_info_path": "/vulnerabilities/CVE-2024-49767/73878",
            "specs": [
                "<0.19.7"
            ],
            "v": "<0.19.7"
        },
        {
            "advisory": "Quart 0.4.0 allows the request to be limited to prevent DOS attacks.",
            "cve": "PVE-2021-39235",
            "id": "pyup.io-39235",
            "more_info_path": "/vulnerabilities/PVE-2021-39235/39235",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Quart 0.5.0 refactors to mitigate DOS attacks.",
            "cve": "PVE-2021-39234",
            "id": "pyup.io-39234",
            "more_info_path": "/vulnerabilities/PVE-2021-39234/39234",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        },
        {
            "advisory": "Quart, a Python ASGI web microframework, is exposed to Denial of Service (DoS) attacks due to vulnerabilities present in certain versions. These attacks can lead to the server being overloaded and becoming inaccessible to legitimate users, without necessarily breaching security or extracting data. DoS attacks, including the high-volume Distributed Denial of Service (DDoS) varieties, exploit a flaw to exhaust server resources through methods such as sending crafted requests that significantly increase CPU or Memory consumption or cause the system to crash. This vulnerability can be unintentionally triggered by high traffic to resource-intensive routes or can be maliciously exploited to render services unavailable.",
            "cve": "PVE-2024-99891",
            "id": "pyup.io-65528",
            "more_info_path": "/vulnerabilities/PVE-2024-99891/65528",
            "specs": [
                ">=0,<0.5.0"
            ],
            "v": ">=0,<0.5.0"
        }
    ],
    "quasar": [
        {
            "advisory": "Quasar 0.6.14 removes the inclusion of https://polyfill.io/v3/polyfill.min.js?features=es6 due to a security issue.",
            "cve": "PVE-2024-71817",
            "id": "pyup.io-71817",
            "more_info_path": "/vulnerabilities/PVE-2024-71817/71817",
            "specs": [
                "<0.6.14"
            ],
            "v": "<0.6.14"
        }
    ],
    "querycommander": [
        {
            "advisory": "Querycommander addresses a vulnerability affecting AWS Lambda deployments. Affected versions potentially exposed user data across sessions due to improper caching. This update resolves the issue and introduces enhanced security measures, including improved tokenization and connection handling. All users, especially those utilizing AWS Lambda, are strongly advised to upgrade immediately to v0.9.1 or later. The update also includes new database/schema access control features and various performance improvements.",
            "cve": "PVE-2024-73014",
            "id": "pyup.io-73014",
            "more_info_path": "/vulnerabilities/PVE-2024-73014/73014",
            "specs": [
                "<0.9.1"
            ],
            "v": "<0.9.1"
        }
    ],
    "querynator": [
        {
            "advisory": "Querynator updated requests to version 2.31.0 due to moderate vulnerability CVE-2023-32681.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-73675",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/73675",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Querynator updated black to version 24.3.0 due to moderate vulnerability CVE-2024-21503.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-73662",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/73662",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Querynator updated requests to version 2.31.0 due to moderate vulnerability CVE-2024-35195.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-73676",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/73676",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "quickscale": [
        {
            "advisory": "Affected versions of QuickScale were potentially vulnerable to improper access control. An attacker could potentially exploit root access to PostgreSQL, leading to unauthorized data access or modification. The vulnerability existed in the PostgreSQL configuration. This issue is fixed in v0.5.1. Users should ensure that database access is restricted to non-root users to enhance security.",
            "cve": "PVE-2025-76689",
            "id": "pyup.io-76689",
            "more_info_path": "/vulnerabilities/PVE-2025-76689/76689",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        }
    ],
    "quilt": [
        {
            "advisory": "Quilt 2.9.14 updates urllib3 version to v.1.24 to include a security patch.",
            "cve": "CVE-2018-20060",
            "id": "pyup.io-36749",
            "more_info_path": "/vulnerabilities/CVE-2018-20060/36749",
            "specs": [
                "<2.9.14"
            ],
            "v": "<2.9.14"
        },
        {
            "advisory": "Quilt 2.9.14 updates Flask version to v.0.12.3 to include security fixes.",
            "cve": "CVE-2018-1000656",
            "id": "pyup.io-43011",
            "more_info_path": "/vulnerabilities/CVE-2018-1000656/43011",
            "specs": [
                "<2.9.14"
            ],
            "v": "<2.9.14"
        },
        {
            "advisory": "Quilt 2.9.14 updates Flask version to v.0.12.3 to include security fixes.",
            "cve": "CVE-2019-1010083",
            "id": "pyup.io-43010",
            "more_info_path": "/vulnerabilities/CVE-2019-1010083/43010",
            "specs": [
                "<2.9.14"
            ],
            "v": "<2.9.14"
        },
        {
            "advisory": "Quilt 3.1.13 updates its dependency 'bleach' to v3.1.4 to include security fixes.",
            "cve": "CVE-2020-6817",
            "id": "pyup.io-45132",
            "more_info_path": "/vulnerabilities/CVE-2020-6817/45132",
            "specs": [
                "<3.1.13"
            ],
            "v": "<3.1.13"
        },
        {
            "advisory": "Quilt 3.1.13 updates its dependency 'bleach' to v3.1.4 to include security fixes.",
            "cve": "CVE-2020-6816",
            "id": "pyup.io-45352",
            "more_info_path": "/vulnerabilities/CVE-2020-6816/45352",
            "specs": [
                "<3.1.13"
            ],
            "v": "<3.1.13"
        },
        {
            "advisory": "Quilt 3.1.13 updates its dependency 'bleach' to v3.1.4 to include security fixes.",
            "cve": "CVE-2020-6802",
            "id": "pyup.io-45353",
            "more_info_path": "/vulnerabilities/CVE-2020-6802/45353",
            "specs": [
                "<3.1.13"
            ],
            "v": "<3.1.13"
        },
        {
            "advisory": "Quilt 3.1.13 updates its NPM dependency 'minimist' to v1.2.5 to include a security fix.",
            "cve": "CVE-2020-7598",
            "id": "pyup.io-45354",
            "more_info_path": "/vulnerabilities/CVE-2020-7598/45354",
            "specs": [
                "<3.1.13"
            ],
            "v": "<3.1.13"
        }
    ],
    "quintagroup-seoptimizer": [
        {
            "advisory": "Quintagroup-seoptimizer 3.0.4 fixes a security issue in the SEO Property action and view.\r\nhttps://github.com/quintagroup/quintagroup.seoptimizer/commit/910cb61aea52e102541ade8456f28209564824ed",
            "cve": "PVE-2021-36006",
            "id": "pyup.io-36006",
            "more_info_path": "/vulnerabilities/PVE-2021-36006/36006",
            "specs": [
                "<3.0.4"
            ],
            "v": "<3.0.4"
        }
    ],
    "quivr-core": [
        {
            "advisory": "A Denial of Service (DoS) vulnerability in the file upload feature of stangirard/quivr v0.0.298 allows unauthenticated attackers to cause excessive resource consumption by appending characters to the end of a multipart boundary in an HTTP request. This leads to the server continuously processing each character, rendering the service unavailable and impacting all users.",
            "cve": "CVE-2024-9229",
            "id": "pyup.io-76194",
            "more_info_path": "/vulnerabilities/CVE-2024-9229/76194",
            "specs": [
                "<=0.0.14"
            ],
            "v": "<=0.0.14"
        }
    ],
    "quokka": [
        {
            "advisory": "XML External Entities (XXE) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the component 'quokka/core/content/views.py'.",
            "cve": "CVE-2020-18705",
            "id": "pyup.io-42284",
            "more_info_path": "/vulnerabilities/CVE-2020-18705/42284",
            "specs": [
                "==0.4.0"
            ],
            "v": "==0.4.0"
        },
        {
            "advisory": "Cross Site Scripting (XSS) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the 'Username' parameter in the component 'quokka/admin/actions.py'.",
            "cve": "CVE-2020-18702",
            "id": "pyup.io-42282",
            "more_info_path": "/vulnerabilities/CVE-2020-18702/42282",
            "specs": [
                "==0.4.0"
            ],
            "v": "==0.4.0"
        },
        {
            "advisory": "XML External Entities (XXE) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the component 'quokka/utils/atom.py'.",
            "cve": "CVE-2020-18703",
            "id": "pyup.io-42283",
            "more_info_path": "/vulnerabilities/CVE-2020-18703/42283",
            "specs": [
                "==0.4.0"
            ],
            "v": "==0.4.0"
        }
    ],
    "qurro": [
        {
            "advisory": "The text boxes in qurro 0.4.0 describing the currently-selected numerator / denominator features are now \"read-only\" (you can't edit them while using Qurro). This should remove any vulnerability to accidental edits of these text boxes.",
            "cve": "PVE-2021-37374",
            "id": "pyup.io-37374",
            "more_info_path": "/vulnerabilities/PVE-2021-37374/37374",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "qutebrowser": [
        {
            "advisory": "Qutebrowser 0.1.4 disables insecure SSL ciphers (< 128bit) for Qt 5.2. This is an issue only for the users of Ubuntu Trusty.",
            "cve": "PVE-2021-34577",
            "id": "pyup.io-34577",
            "more_info_path": "/vulnerabilities/PVE-2021-34577/34577",
            "specs": [
                "<0.1.4"
            ],
            "v": "<0.1.4"
        },
        {
            "advisory": "Qutebrowser 1.0.3 ships with PyQt 5.9.1 and Qt 5.9.2 which includes security fixes from Chromium up to version 61.0.3163.79.",
            "cve": "PVE-2021-35044",
            "id": "pyup.io-35044",
            "more_info_path": "/vulnerabilities/PVE-2021-35044/35044",
            "specs": [
                "<1.0.3"
            ],
            "v": "<1.0.3"
        },
        {
            "advisory": "Qutebrowser 1.1.2 ships with Qt 5.10.1 which includes security fixes from Chromium up to version 64.0.3282.140.",
            "cve": "PVE-2021-35786",
            "id": "pyup.io-35786",
            "more_info_path": "/vulnerabilities/PVE-2021-35786/35786",
            "specs": [
                "<1.1.2"
            ],
            "v": "<1.1.2"
        },
        {
            "advisory": "Qutebrowser 1.10.0 Windows and macOS releases ship with Qt/QtWebEngine 5.14.1, which are based on Chromium 77.0.3865.129 with security fixes up to Chromium 79.0.3945.117.\r\n#NOTE: This vulnerability affects only users of MacOS and Windows.\r\nhttps://github.com/qutebrowser/qutebrowser/commit/7dfb403478d7a1f27ffcd50263f1e9a43298a0dd",
            "cve": "CVE-2020-6377",
            "id": "pyup.io-37811",
            "more_info_path": "/vulnerabilities/CVE-2020-6377/37811",
            "specs": [
                "<1.10.0"
            ],
            "v": "<1.10.0"
        },
        {
            "advisory": "Qutebrowser 1.11.1 includes a fix for CVE-2020-11054:  After a certificate error was overridden by the user, qutebrowser displays the URL as yellow ('colors.statusbar.url.warn.fg'). However, when the affected website was subsequently loaded again, the URL was mistakenly displayed as green ('colors.statusbar.url.success_https'). While the user already has seen a certificate error prompt at this point (or set 'content.ssl_strict' to 'false' which is not recommended), this could still provide a false sense of security.",
            "cve": "CVE-2020-11054",
            "id": "pyup.io-38266",
            "more_info_path": "/vulnerabilities/CVE-2020-11054/38266",
            "specs": [
                "<1.11.1"
            ],
            "v": "<1.11.1"
        },
        {
            "advisory": "Qutebrowser 1.12.0 Windows and macOS releases ship 'Qt' 5.15, which is based on Chromium 80.0.3987.163 with security fixes up to 81.0.4044.138.\r\n#NOTE: This vulnerability affects only users of MacOS and Windows.\r\nhttps://github.com/qutebrowser/qutebrowser/commit/2a42f3a8c27aa036f4af08ef6f3108bbe80a3bcb",
            "cve": "CVE-2020-6464",
            "id": "pyup.io-38447",
            "more_info_path": "/vulnerabilities/CVE-2020-6464/38447",
            "specs": [
                "<1.12.0"
            ],
            "v": "<1.12.0"
        },
        {
            "advisory": "Qutebrowser 1.12.0 Windows and macOS releases ship 'Qt' 5.15, which is based on Chromium 80.0.3987.163 with security fixes up to 81.0.4044.138.\r\n#NOTE: This vulnerability affects only users of MacOS and Windows.\r\nhttps://github.com/qutebrowser/qutebrowser/commit/2a42f3a8c27aa036f4af08ef6f3108bbe80a3bcb",
            "cve": "CVE-2020-6831",
            "id": "pyup.io-62670",
            "more_info_path": "/vulnerabilities/CVE-2020-6831/62670",
            "specs": [
                "<1.12.0"
            ],
            "v": "<1.12.0"
        },
        {
            "advisory": "Qutebrowser 1.14.1 Windows and macOS releases ship 'Qt' v5.15.2, which is based on Chromium 83.0.4103.122 with security fixes up to 86.0.4240.183. This includes CVE-2020-15999 in the bundled freetype library, which is known to be exploited in the wild.\r\n#NOTE: This vulnerability affects only users of MacOS and Windows.",
            "cve": "CVE-2020-15999",
            "id": "pyup.io-39227",
            "more_info_path": "/vulnerabilities/CVE-2020-15999/39227",
            "specs": [
                "<1.14.1"
            ],
            "v": "<1.14.1"
        },
        {
            "advisory": "In qutebrowser 1.3.0, support for JavaScript Shared Web Workers has been disabled on Qt versions older than 5.11 because of security issues in Chromium. You can get the same effect in earlier versions via `:set qt.args ['disable-shared-workers']`. An equivalent workaround is also contained in Qt 5.9.5 and 5.10.1.",
            "cve": "PVE-2021-36929",
            "id": "pyup.io-36929",
            "more_info_path": "/vulnerabilities/PVE-2021-36929/36929",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "In qutebrowser 1.3.3, an XSS vulnerability on the `qute://history` page allowed websites to inject HTML into the page via a crafted title tag. This could allow them to steal your browsing history. If you're currently unable to upgrade, avoid using `:history`. See CVE-2018-1000559.",
            "cve": "CVE-2018-1000559",
            "id": "pyup.io-37812",
            "more_info_path": "/vulnerabilities/CVE-2018-1000559/37812",
            "specs": [
                "<1.3.3"
            ],
            "v": "<1.3.3"
        },
        {
            "advisory": "Qutebrowser 1.4.0 ships with Qt 5.11.1 in the macOS and Windows releases, which are based on Chromium 65.0.3325.151 with security fixes up to Chromium 67.0.3396.87. The security fix in v1.3.3 caused URLs with ampersands (`www.example.com?one=1&two=2`) to send the wrong arguments when clicked on the `qute://history` page.",
            "cve": "PVE-2021-36294",
            "id": "pyup.io-36294",
            "more_info_path": "/vulnerabilities/PVE-2021-36294/36294",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Qutebrowser 1.4.1 fixes the CSRF issue on the qute://settings page, leading to possible arbitrary code execution. See https://github.com/qutebrowser/qutebrowser/issues/4060 and CVE-2018-10895.",
            "cve": "CVE-2018-10895",
            "id": "pyup.io-36970",
            "more_info_path": "/vulnerabilities/CVE-2018-10895/36970",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        },
        {
            "advisory": "Qutebrowser 1.5.0 ships with Python 3.7, PyQt 5.11.3 and Qt 5.11.2. QtWebEngine includes security fixes up to Chromium 68.0.3440.75 and various other fixes.",
            "cve": "PVE-2021-36521",
            "id": "pyup.io-36521",
            "more_info_path": "/vulnerabilities/PVE-2021-36521/36521",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        },
        {
            "advisory": "Qutebrowser 1.6.0 ships with Qt 5.12.1 which is based on Chromium 69.0.3497.128 with security fixes up to 71.0.3578.94.",
            "cve": "PVE-2021-36199",
            "id": "pyup.io-36199",
            "more_info_path": "/vulnerabilities/PVE-2021-36199/36199",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        },
        {
            "advisory": "Qutebrowser 1.6.1 ships with Qt 5.12.2 in the macOS and Windows releases, which includes security fixes up to Chromium 72.0.3626.121 (including CVE-2019-5786 which is known to be exploited in the wild).",
            "cve": "CVE-2019-5786",
            "id": "pyup.io-36280",
            "more_info_path": "/vulnerabilities/CVE-2019-5786/36280",
            "specs": [
                "<1.6.1"
            ],
            "v": "<1.6.1"
        },
        {
            "advisory": "Qutebrowser 1.6.2 ships with Qt 5.12.3 in the macOS and Windows releases, which includes security fixes up to Chromium 73.0.3683.75.",
            "cve": "PVE-2021-37120",
            "id": "pyup.io-37120",
            "more_info_path": "/vulnerabilities/PVE-2021-37120/37120",
            "specs": [
                "<1.6.2"
            ],
            "v": "<1.6.2"
        },
        {
            "advisory": "Qutebrowser 1.7.0 ships with Qt 5.12.4 in the macOS and Windows releases, which includes security fixes up to Chromium 74.0.3729.157.",
            "cve": "PVE-2021-37507",
            "id": "pyup.io-37507",
            "more_info_path": "/vulnerabilities/PVE-2021-37507/37507",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Qutebrowser 1.8.0 ships with Qt 5.13.0 and QtWebEngine 5.13.1 in the macOS releases (based on Chromium 73.0.3683.105), and Qt/QtWebEngine 5.12.5 in the Windows release (based on Chromium 69.0.3497.128), which both include security fixes up to Chromium 76.0.3809.87.",
            "cve": "PVE-2021-37506",
            "id": "pyup.io-37506",
            "more_info_path": "/vulnerabilities/PVE-2021-37506/37506",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        },
        {
            "advisory": "Qutebrowser 1.8.1 ships with Qt/QtWebEngine 5.12.5 in the macOS and Windows releases, which are based on Chromium 69.0.3497.128 with security fixes up to Chromium 76.0.3809.87.",
            "cve": "PVE-2021-37511",
            "id": "pyup.io-37511",
            "more_info_path": "/vulnerabilities/PVE-2021-37511/37511",
            "specs": [
                "<1.8.1"
            ],
            "v": "<1.8.1"
        },
        {
            "advisory": "Qutebrowser 1.8.2 ships with Qt 5.12.6 in the macOS and Windows releases, which includes security fixes up to Chromium 77.0.3865.120, plus a security fix for CVE-2019-13720 from Chromium 78.\r\n#NOTE: This vulnerability affects only users of MacOS and Windows.",
            "cve": "CVE-2019-13720",
            "id": "pyup.io-36433",
            "more_info_path": "/vulnerabilities/CVE-2019-13720/36433",
            "specs": [
                "<1.8.2"
            ],
            "v": "<1.8.2"
        },
        {
            "advisory": "Qutebrowser 2.4.0 fixes an arbitrary command execution vulnerability on Windows OS via URL handler.\r\nhttps://github.com/qutebrowser/qutebrowser/security/advisories/GHSA-vw27-fwjf-5qxm",
            "cve": "CVE-2021-41146",
            "id": "pyup.io-49013",
            "more_info_path": "/vulnerabilities/CVE-2021-41146/49013",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Qutebrowser 2.5.0 adds a workaround to a Qt issue causing ':spawn' to run executables from the current directory if no system-wide executable was found. The main security impact of this bug is in tools like text editors, which are often executed in untrusted directories and might attempt to run auxiliary tools automatically.",
            "cve": "CVE-2022-25255",
            "id": "pyup.io-49012",
            "more_info_path": "/vulnerabilities/CVE-2022-25255/49012",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Qutebrowser 2.3.1 updates the workaround for Google Account log in claiming that previously used browser isn't secure.\r\nhttps://github.com/qutebrowser/qutebrowser/commit/28a80dac0125cab5fc7dc7374d2c39e7bd8b93bd",
            "cve": "PVE-2022-49014",
            "id": "pyup.io-49014",
            "more_info_path": "/vulnerabilities/PVE-2022-49014/49014",
            "specs": [
                ">=1.14.0,<2.3.1"
            ],
            "v": ">=1.14.0,<2.3.1"
        }
    ],
    "qweb": [
        {
            "advisory": "Qweb 3.0.0 updates the dependency opencv-python from 4.8.0.74 to 4.8.1.78 to include security fixes for the CVE-2023-4863.\r\nhttps://github.com/qentinelqi/qweb/compare/v2.2.3...v3.0.0#diff-4d7c51b1efe9043e44439a949dfd92e5827321b34082903477fd04876edb7552L10",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-63054",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/63054",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Qweb 3.0.0 updates the dependency pillow from 9.5.0 to '>=10.0.1,<11' to include security fixes for the CVE-2023-44271.\r\nhttps://github.com/qentinelqi/qweb/compare/v2.2.3...v3.0.0#diff-4d7c51b1efe9043e44439a949dfd92e5827321b34082903477fd04876edb7552L3",
            "cve": "CVE-2023-44271",
            "id": "pyup.io-63092",
            "more_info_path": "/vulnerabilities/CVE-2023-44271/63092",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Qweb 3.2.1 updates its Pillow dependency range to \">=10.3.0,<11\" from \">=10.0.2,<11\" to address security concerns highlighted by CVE-2024-28219.",
            "cve": "CVE-2024-28219",
            "id": "pyup.io-67531",
            "more_info_path": "/vulnerabilities/CVE-2024-28219/67531",
            "specs": [
                "<3.2.1"
            ],
            "v": "<3.2.1"
        },
        {
            "advisory": "Qweb 3.3.2 updates its minimum allowed version of requests from 2.31.0 to 2.32.0 due to security concerns, including CVE-2024-35195.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-71675",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/71675",
            "specs": [
                "<3.3.2"
            ],
            "v": "<3.3.2"
        }
    ],
    "r2connect": [
        {
            "advisory": "R2connect 1.1.2 upgrades the dependency urllib3 from `2.0.6` to `2.0.7` to patch information exposure vulnerability from the CVE-2023-45803.\r\nhttps://github.com/mo-awais/r2connect/commit/c29c98933223ed42b05ec74b73d75242ad13cfff",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-63153",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/63153",
            "specs": [
                "<1.1.2"
            ],
            "v": "<1.1.2"
        }
    ],
    "r2libr": [
        {
            "advisory": "R2libr includes as submodule radare2 version 5.7.9, which is vulnerable to CVE-2023-27114.",
            "cve": "CVE-2023-27114",
            "id": "pyup.io-59509",
            "more_info_path": "/vulnerabilities/CVE-2023-27114/59509",
            "specs": [
                "<=5.7.4"
            ],
            "v": "<=5.7.4"
        },
        {
            "advisory": "R2libr includes as submodule radare2 version 5.7.9, which is vulnerable to CVE-2023-0302.",
            "cve": "CVE-2023-0302",
            "id": "pyup.io-59511",
            "more_info_path": "/vulnerabilities/CVE-2023-0302/59511",
            "specs": [
                "<=5.7.4"
            ],
            "v": "<=5.7.4"
        },
        {
            "advisory": "R2libr includes as submodule radare2 version 5.7.9, which is vulnerable to CVE-2023-1605.",
            "cve": "CVE-2023-1605",
            "id": "pyup.io-59513",
            "more_info_path": "/vulnerabilities/CVE-2023-1605/59513",
            "specs": [
                "<=5.7.4"
            ],
            "v": "<=5.7.4"
        }
    ],
    "radicale": [
        {
            "advisory": "Radicale before 1.1.2 is vulnerable to bruteforce attacks when using the htpasswd authentication method. See CVE-2017-8342.",
            "cve": "CVE-2017-8342",
            "id": "pyup.io-33323",
            "more_info_path": "/vulnerabilities/CVE-2017-8342/33323",
            "specs": [
                "<1.1.2"
            ],
            "v": "<1.1.2"
        },
        {
            "advisory": "Radicale 3.0.0 introduces protections against XML DOS attacks by only processing XML content from authenticated users.\r\nhttps://github.com/Kozea/Radicale/commit/e11661ff3ebdeda35c024041c124b0824f1682b0",
            "cve": "PVE-2024-66771",
            "id": "pyup.io-66771",
            "more_info_path": "/vulnerabilities/PVE-2024-66771/66771",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "The filesystem storage backend in Radicale before 1.1 on Windows allows remote attackers to read or write to arbitrary files via a crafted path, as demonstrated by /c:/file/ignore.",
            "cve": "CVE-2016-1505",
            "id": "pyup.io-65853",
            "more_info_path": "/vulnerabilities/CVE-2016-1505/65853",
            "specs": [
                "<=1.0.1"
            ],
            "v": "<=1.0.1"
        },
        {
            "advisory": "The multifilesystem storage backend in Radicale before 1.1 allows remote attackers to read or write to arbitrary files via a crafted component name.",
            "cve": "CVE-2015-8747",
            "id": "pyup.io-54108",
            "more_info_path": "/vulnerabilities/CVE-2015-8747/54108",
            "specs": [
                ">=0,<1.1"
            ],
            "v": ">=0,<1.1"
        },
        {
            "advisory": "Radicale before 1.1 allows remote authenticated users to bypass owner_write and owner_only limitations via regex metacharacters in the user name, as demonstrated by \".*\".",
            "cve": "CVE-2015-8748",
            "id": "pyup.io-54109",
            "more_info_path": "/vulnerabilities/CVE-2015-8748/54109",
            "specs": [
                ">=0,<1.1"
            ],
            "v": ">=0,<1.1"
        }
    ],
    "rafcon": [
        {
            "advisory": "The Rafcon update to version 0.14.7 addresses a race condition, ensuring that the 'result' and 'exception_info' global variables are now thread-safe, enhancing stability and reliability in concurrent environments.\r\nhttps://github.com/DLR-RM/RAFCON/commit/766490da8e2af471c1cd9c5126e4ff343c3d5ccf",
            "cve": "PVE-2024-65977",
            "id": "pyup.io-65977",
            "more_info_path": "/vulnerabilities/PVE-2024-65977/65977",
            "specs": [
                "<0.14.7"
            ],
            "v": "<0.14.7"
        }
    ],
    "raiden": [
        {
            "advisory": "Raiden 0.10.0 fixes a security issue where an attacker could eavesdrop Matrix communications between two nodes in private rooms.",
            "cve": "PVE-2021-37316",
            "id": "pyup.io-37316",
            "more_info_path": "/vulnerabilities/PVE-2021-37316/37316",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Raiden 0.4.1 prevents DOS attacks and race conditions that caused client crashes.\r\nhttps://github.com/raiden-network/raiden/pull/1869",
            "cve": "PVE-2021-38520",
            "id": "pyup.io-38520",
            "more_info_path": "/vulnerabilities/PVE-2021-38520/38520",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        }
    ],
    "raiden-services": [
        {
            "advisory": "In raiden-services before 0.2.0, the Monitoring Service database was vulnerable to timing-based Monitoring Request injection.\r\nhttps://github.com/raiden-network/raiden-services/issues/418",
            "cve": "PVE-2021-37317",
            "id": "pyup.io-37317",
            "more_info_path": "/vulnerabilities/PVE-2021-37317/37317",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "ramalama": [
        {
            "advisory": "Affected versions of RamaLama (< 0.8.2) are potentially vulnerable to uncontrolled search-path injection (CWE-427). The deprecated bin/ramalama launcher prepends /usr/local/lib/python*/site-packages to sys.path, letting attacker-supplied or stale modules in that user-writable directory run before trusted code. A local user who can write to /usr/local\u2014common on multi-user Homebrew macOS systems\u2014can gain arbitrary code execution, privilege escalation or container escape when any victim starts the CLI. The vulnerable helper is add_site_packages_to_syspath() in the removed launcher. Remediation: upgrade to v0.8.2 (commit a9f5238082e) or back-port the new console_scripts entry point; alternatively, run RamaLama inside a virtual-env with global site-packages disabled.",
            "cve": "PVE-2025-77226",
            "id": "pyup.io-77226",
            "more_info_path": "/vulnerabilities/PVE-2025-77226/77226",
            "specs": [
                "<0.8.3"
            ],
            "v": "<0.8.3"
        }
    ],
    "ramlwrap": [
        {
            "advisory": "Ramlwrap 2.2.2 updates PyYAML to v5.1 to include a security fix.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-38298",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/38298",
            "specs": [
                "<2.2.2"
            ],
            "v": "<2.2.2"
        }
    ],
    "randomtime": [
        {
            "advisory": "Randomtime is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html",
            "cve": "PVE-2023-52910",
            "id": "pyup.io-52910",
            "more_info_path": "/vulnerabilities/PVE-2023-52910/52910",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "rapid-router": [
        {
            "advisory": "Affected versions of Rapid Router are potentially vulnerable to unauthorized access due to missing admin authentication on API endpoints. The attack vector involves direct API requests to endpoints (e.g., decor_list, level_list) without proper login verification.",
            "cve": "PVE-2025-75983",
            "id": "pyup.io-75983",
            "more_info_path": "/vulnerabilities/PVE-2025-75983/75983",
            "specs": [
                "<2.3.8"
            ],
            "v": "<2.3.8"
        }
    ],
    "rapidtide": [
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-26268",
            "id": "pyup.io-48381",
            "more_info_path": "/vulnerabilities/CVE-2020-26268/48381",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-19646",
            "id": "pyup.io-48350",
            "more_info_path": "/vulnerabilities/CVE-2019-19646/48350",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15202",
            "id": "pyup.io-48367",
            "more_info_path": "/vulnerabilities/CVE-2020-15202/48367",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2018-17190",
            "id": "pyup.io-48341",
            "more_info_path": "/vulnerabilities/CVE-2018-17190/48341",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-14155",
            "id": "pyup.io-48363",
            "more_info_path": "/vulnerabilities/CVE-2020-14155/48363",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-16168",
            "id": "pyup.io-48347",
            "more_info_path": "/vulnerabilities/CVE-2019-16168/48347",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-19880",
            "id": "pyup.io-48351",
            "more_info_path": "/vulnerabilities/CVE-2019-19880/48351",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-26270",
            "id": "pyup.io-48382",
            "more_info_path": "/vulnerabilities/CVE-2020-26270/48382",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-10099",
            "id": "pyup.io-48344",
            "more_info_path": "/vulnerabilities/CVE-2019-10099/48344",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-19645",
            "id": "pyup.io-48349",
            "more_info_path": "/vulnerabilities/CVE-2019-19645/48349",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-13630",
            "id": "pyup.io-48359",
            "more_info_path": "/vulnerabilities/CVE-2020-13630/48359",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-11656",
            "id": "pyup.io-48356",
            "more_info_path": "/vulnerabilities/CVE-2020-11656/48356",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-11655",
            "id": "pyup.io-48355",
            "more_info_path": "/vulnerabilities/CVE-2020-11655/48355",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2018-20330",
            "id": "pyup.io-48343",
            "more_info_path": "/vulnerabilities/CVE-2018-20330/48343",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-5481",
            "id": "pyup.io-48353",
            "more_info_path": "/vulnerabilities/CVE-2019-5481/48353",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-13871",
            "id": "pyup.io-48362",
            "more_info_path": "/vulnerabilities/CVE-2020-13871/48362",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15195",
            "id": "pyup.io-48366",
            "more_info_path": "/vulnerabilities/CVE-2020-15195/48366",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-19244",
            "id": "pyup.io-48348",
            "more_info_path": "/vulnerabilities/CVE-2019-19244/48348",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15210",
            "id": "pyup.io-48375",
            "more_info_path": "/vulnerabilities/CVE-2020-15210/48375",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2018-11770",
            "id": "pyup.io-40991",
            "more_info_path": "/vulnerabilities/CVE-2018-11770/40991",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15207",
            "id": "pyup.io-48372",
            "more_info_path": "/vulnerabilities/CVE-2020-15207/48372",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-5215",
            "id": "pyup.io-48384",
            "more_info_path": "/vulnerabilities/CVE-2020-5215/48384",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15209",
            "id": "pyup.io-48374",
            "more_info_path": "/vulnerabilities/CVE-2020-15209/48374",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15250",
            "id": "pyup.io-48377",
            "more_info_path": "/vulnerabilities/CVE-2020-15250/48377",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-13631",
            "id": "pyup.io-48360",
            "more_info_path": "/vulnerabilities/CVE-2020-13631/48360",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15206",
            "id": "pyup.io-48371",
            "more_info_path": "/vulnerabilities/CVE-2020-15206/48371",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15208",
            "id": "pyup.io-48373",
            "more_info_path": "/vulnerabilities/CVE-2020-15208/48373",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2018-19664",
            "id": "pyup.io-48342",
            "more_info_path": "/vulnerabilities/CVE-2018-19664/48342",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-26267",
            "id": "pyup.io-48380",
            "more_info_path": "/vulnerabilities/CVE-2020-26267/48380",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15190",
            "id": "pyup.io-48364",
            "more_info_path": "/vulnerabilities/CVE-2020-15190/48364",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-5482",
            "id": "pyup.io-48354",
            "more_info_path": "/vulnerabilities/CVE-2019-5482/48354",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-13434",
            "id": "pyup.io-48357",
            "more_info_path": "/vulnerabilities/CVE-2020-13434/48357",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15203",
            "id": "pyup.io-48368",
            "more_info_path": "/vulnerabilities/CVE-2020-15203/48368",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-26266",
            "id": "pyup.io-48379",
            "more_info_path": "/vulnerabilities/CVE-2020-26266/48379",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-13790",
            "id": "pyup.io-48361",
            "more_info_path": "/vulnerabilities/CVE-2020-13790/48361",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-9327",
            "id": "pyup.io-48385",
            "more_info_path": "/vulnerabilities/CVE-2020-9327/48385",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15204",
            "id": "pyup.io-48369",
            "more_info_path": "/vulnerabilities/CVE-2020-15204/48369",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-20838",
            "id": "pyup.io-48352",
            "more_info_path": "/vulnerabilities/CVE-2019-20838/48352",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2019-13960",
            "id": "pyup.io-48345",
            "more_info_path": "/vulnerabilities/CVE-2019-13960/48345",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15358",
            "id": "pyup.io-48378",
            "more_info_path": "/vulnerabilities/CVE-2020-15358/48378",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15211",
            "id": "pyup.io-48376",
            "more_info_path": "/vulnerabilities/CVE-2020-15211/48376",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15194",
            "id": "pyup.io-48365",
            "more_info_path": "/vulnerabilities/CVE-2020-15194/48365",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-13435",
            "id": "pyup.io-48358",
            "more_info_path": "/vulnerabilities/CVE-2020-13435/48358",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.0.2 starts to require the 'Tensorflow' 2.4.0 or above to address security issues.",
            "cve": "CVE-2020-15205",
            "id": "pyup.io-48370",
            "more_info_path": "/vulnerabilities/CVE-2020-15205/48370",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Rapidtide 2.6.5 updates its dependency 'urllib3' to v2.0.6 to include a security fix.",
            "cve": "CVE-2023-43804",
            "id": "pyup.io-61598",
            "more_info_path": "/vulnerabilities/CVE-2023-43804/61598",
            "specs": [
                "<2.6.5"
            ],
            "v": "<2.6.5"
        },
        {
            "advisory": "Rapidtide 2.6.5 updates its dependency 'pillow' to v10.0.1 to include a security fix.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61647",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61647",
            "specs": [
                "<2.6.5"
            ],
            "v": "<2.6.5"
        },
        {
            "advisory": "Rapidtide 2.7.5 updates its dependency on Jinja2, moving from version 3.1.2 to 3.1.3, in response to the security vulnerability identified as CVE-2024-22195.\r\nhttps://github.com/bbfrederick/rapidtide/commit/8ef1d37b15f96a739582781123e3ee239d0d0b18",
            "cve": "CVE-2024-22195",
            "id": "pyup.io-64094",
            "more_info_path": "/vulnerabilities/CVE-2024-22195/64094",
            "specs": [
                "<2.7.5"
            ],
            "v": "<2.7.5"
        },
        {
            "advisory": "Rapidtide 2.2.5 and prior may use a version of TensorFlow (2.4.0) affected by known vulnerabilities.",
            "cve": "CVE-2020-26271",
            "id": "pyup.io-48386",
            "more_info_path": "/vulnerabilities/CVE-2020-26271/48386",
            "specs": [
                "<=2.2.5"
            ],
            "v": "<=2.2.5"
        }
    ],
    "rapidyaml": [
        {
            "advisory": "Affected versions of rapidyaml are vulnerable to a stack overflow due to a missing maximum tree depth check in emitter functions. This flaw allows attackers to supply deeply nested YAML inputs, potentially causing crashes and denial-of-service. Vulnerable emitter functions lack bounds checking, making exploitation straightforward. Mitigation involves upgrading to a patched version that introduces an EmitOptions structure with a default maximum depth of 64. This vulnerability is specific to the rapidyaml C++ implementation.",
            "cve": "PVE-2025-75467",
            "id": "pyup.io-75467",
            "more_info_path": "/vulnerabilities/PVE-2025-75467/75467",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        }
    ],
    "rasa": [
        {
            "advisory": "Rasa 1.10.0 updates the pyyaml dependency to 5.3.1 to fix CVE-2020-1747.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-38230",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/38230",
            "specs": [
                "<1.10.0"
            ],
            "v": "<1.10.0"
        },
        {
            "advisory": "The slack connector in rasa 2.1.0 changes the configuration for 'slack_signing_secret' to make the connector more secure (issue 7204). The configuration value needs to be added to your 'credentials.yml' if you are using the slack connector.",
            "cve": "PVE-2021-39308",
            "id": "pyup.io-39308",
            "more_info_path": "/vulnerabilities/PVE-2021-39308/39308",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        },
        {
            "advisory": "Rasa 2.8.10 includes a fix for CVE-2021-41127: In affected versions, a vulnerability exists in the functionality that loads a trained model 'tar.gz' file which allows a malicious actor to craft a 'model.tar.gz' file which can overwrite or replace bot files in the bot directory. Users unable to update should ensure that untrusted model files are not uploaded and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.\r\nhttps://github.com/RasaHQ/rasa/pull/9852",
            "cve": "CVE-2021-41127",
            "id": "pyup.io-42810",
            "more_info_path": "/vulnerabilities/CVE-2021-41127/42810",
            "specs": [
                "<2.8.10"
            ],
            "v": "<2.8.10"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41205",
            "id": "pyup.io-46935",
            "more_info_path": "/vulnerabilities/CVE-2021-41205/46935",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41210",
            "id": "pyup.io-46940",
            "more_info_path": "/vulnerabilities/CVE-2021-41210/46940",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41217",
            "id": "pyup.io-46947",
            "more_info_path": "/vulnerabilities/CVE-2021-41217/46947",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41211",
            "id": "pyup.io-46941",
            "more_info_path": "/vulnerabilities/CVE-2021-41211/46941",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41200",
            "id": "pyup.io-46930",
            "more_info_path": "/vulnerabilities/CVE-2021-41200/46930",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41212",
            "id": "pyup.io-46942",
            "more_info_path": "/vulnerabilities/CVE-2021-41212/46942",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41204",
            "id": "pyup.io-46934",
            "more_info_path": "/vulnerabilities/CVE-2021-41204/46934",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41219",
            "id": "pyup.io-46949",
            "more_info_path": "/vulnerabilities/CVE-2021-41219/46949",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41220",
            "id": "pyup.io-46950",
            "more_info_path": "/vulnerabilities/CVE-2021-41220/46950",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41224",
            "id": "pyup.io-46954",
            "more_info_path": "/vulnerabilities/CVE-2021-41224/46954",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41195",
            "id": "pyup.io-46925",
            "more_info_path": "/vulnerabilities/CVE-2021-41195/46925",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41213",
            "id": "pyup.io-46943",
            "more_info_path": "/vulnerabilities/CVE-2021-41213/46943",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41223",
            "id": "pyup.io-46953",
            "more_info_path": "/vulnerabilities/CVE-2021-41223/46953",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41228",
            "id": "pyup.io-46958",
            "more_info_path": "/vulnerabilities/CVE-2021-41228/46958",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41227",
            "id": "pyup.io-46957",
            "more_info_path": "/vulnerabilities/CVE-2021-41227/46957",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41225",
            "id": "pyup.io-46955",
            "more_info_path": "/vulnerabilities/CVE-2021-41225/46955",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41221",
            "id": "pyup.io-46951",
            "more_info_path": "/vulnerabilities/CVE-2021-41221/46951",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41218",
            "id": "pyup.io-46948",
            "more_info_path": "/vulnerabilities/CVE-2021-41218/46948",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41209",
            "id": "pyup.io-46939",
            "more_info_path": "/vulnerabilities/CVE-2021-41209/46939",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41207",
            "id": "pyup.io-46937",
            "more_info_path": "/vulnerabilities/CVE-2021-41207/46937",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41202",
            "id": "pyup.io-46932",
            "more_info_path": "/vulnerabilities/CVE-2021-41202/46932",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41215",
            "id": "pyup.io-46945",
            "more_info_path": "/vulnerabilities/CVE-2021-41215/46945",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41203",
            "id": "pyup.io-46933",
            "more_info_path": "/vulnerabilities/CVE-2021-41203/46933",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41199",
            "id": "pyup.io-46929",
            "more_info_path": "/vulnerabilities/CVE-2021-41199/46929",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-22925",
            "id": "pyup.io-46923",
            "more_info_path": "/vulnerabilities/CVE-2021-22925/46923",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-22923",
            "id": "pyup.io-46921",
            "more_info_path": "/vulnerabilities/CVE-2021-22923/46921",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41197",
            "id": "pyup.io-46927",
            "more_info_path": "/vulnerabilities/CVE-2021-41197/46927",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-22924",
            "id": "pyup.io-46922",
            "more_info_path": "/vulnerabilities/CVE-2021-22924/46922",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-22922",
            "id": "pyup.io-46882",
            "more_info_path": "/vulnerabilities/CVE-2021-22922/46882",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41206",
            "id": "pyup.io-46936",
            "more_info_path": "/vulnerabilities/CVE-2021-41206/46936",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41196",
            "id": "pyup.io-46926",
            "more_info_path": "/vulnerabilities/CVE-2021-41196/46926",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41208",
            "id": "pyup.io-46938",
            "more_info_path": "/vulnerabilities/CVE-2021-41208/46938",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41198",
            "id": "pyup.io-46928",
            "more_info_path": "/vulnerabilities/CVE-2021-41198/46928",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41226",
            "id": "pyup.io-46956",
            "more_info_path": "/vulnerabilities/CVE-2021-41226/46956",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41222",
            "id": "pyup.io-46952",
            "more_info_path": "/vulnerabilities/CVE-2021-41222/46952",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41216",
            "id": "pyup.io-46946",
            "more_info_path": "/vulnerabilities/CVE-2021-41216/46946",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41214",
            "id": "pyup.io-46944",
            "more_info_path": "/vulnerabilities/CVE-2021-41214/46944",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-41201",
            "id": "pyup.io-46931",
            "more_info_path": "/vulnerabilities/CVE-2021-41201/46931",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.13 and 3.0.0rc2 update its dependency 'Tensorflow' to v2.6.2 and v2.6.1 respectively to include security fixes.",
            "cve": "CVE-2021-22926",
            "id": "pyup.io-46924",
            "more_info_path": "/vulnerabilities/CVE-2021-22926/46924",
            "specs": [
                "<2.8.13",
                ">=3.0.0rc1,<3.0.0rc2"
            ],
            "v": "<2.8.13,>=3.0.0rc1,<3.0.0rc2"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37652",
            "id": "pyup.io-44032",
            "more_info_path": "/vulnerabilities/CVE-2021-37652/44032",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37644",
            "id": "pyup.io-44010",
            "more_info_path": "/vulnerabilities/CVE-2021-37644/44010",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37678",
            "id": "pyup.io-44060",
            "more_info_path": "/vulnerabilities/CVE-2021-37678/44060",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37690",
            "id": "pyup.io-44020",
            "more_info_path": "/vulnerabilities/CVE-2021-37690/44020",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37676",
            "id": "pyup.io-44037",
            "more_info_path": "/vulnerabilities/CVE-2021-37676/44037",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37641",
            "id": "pyup.io-44030",
            "more_info_path": "/vulnerabilities/CVE-2021-37641/44030",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37645",
            "id": "pyup.io-44006",
            "more_info_path": "/vulnerabilities/CVE-2021-37645/44006",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37659",
            "id": "pyup.io-44034",
            "more_info_path": "/vulnerabilities/CVE-2021-37659/44034",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37637",
            "id": "pyup.io-44023",
            "more_info_path": "/vulnerabilities/CVE-2021-37637/44023",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37646",
            "id": "pyup.io-44029",
            "more_info_path": "/vulnerabilities/CVE-2021-37646/44029",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-22898",
            "id": "pyup.io-44051",
            "more_info_path": "/vulnerabilities/CVE-2021-22898/44051",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37685",
            "id": "pyup.io-44008",
            "more_info_path": "/vulnerabilities/CVE-2021-37685/44008",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37689",
            "id": "pyup.io-44056",
            "more_info_path": "/vulnerabilities/CVE-2021-37689/44056",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37651",
            "id": "pyup.io-44040",
            "more_info_path": "/vulnerabilities/CVE-2021-37651/44040",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37665",
            "id": "pyup.io-44017",
            "more_info_path": "/vulnerabilities/CVE-2021-37665/44017",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37688",
            "id": "pyup.io-44036",
            "more_info_path": "/vulnerabilities/CVE-2021-37688/44036",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37681",
            "id": "pyup.io-44021",
            "more_info_path": "/vulnerabilities/CVE-2021-37681/44021",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37664",
            "id": "pyup.io-44045",
            "more_info_path": "/vulnerabilities/CVE-2021-37664/44045",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37662",
            "id": "pyup.io-44031",
            "more_info_path": "/vulnerabilities/CVE-2021-37662/44031",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37661",
            "id": "pyup.io-44024",
            "more_info_path": "/vulnerabilities/CVE-2021-37661/44024",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37654",
            "id": "pyup.io-44049",
            "more_info_path": "/vulnerabilities/CVE-2021-37654/44049",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37639",
            "id": "pyup.io-44050",
            "more_info_path": "/vulnerabilities/CVE-2021-37639/44050",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37642",
            "id": "pyup.io-44054",
            "more_info_path": "/vulnerabilities/CVE-2021-37642/44054",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37636",
            "id": "pyup.io-44053",
            "more_info_path": "/vulnerabilities/CVE-2021-37636/44053",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37669",
            "id": "pyup.io-44011",
            "more_info_path": "/vulnerabilities/CVE-2021-37669/44011",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37680",
            "id": "pyup.io-44058",
            "more_info_path": "/vulnerabilities/CVE-2021-37680/44058",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37687",
            "id": "pyup.io-44007",
            "more_info_path": "/vulnerabilities/CVE-2021-37687/44007",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-22901",
            "id": "pyup.io-44003",
            "more_info_path": "/vulnerabilities/CVE-2021-22901/44003",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37675",
            "id": "pyup.io-44038",
            "more_info_path": "/vulnerabilities/CVE-2021-37675/44038",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37670",
            "id": "pyup.io-44013",
            "more_info_path": "/vulnerabilities/CVE-2021-37670/44013",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37666",
            "id": "pyup.io-44033",
            "more_info_path": "/vulnerabilities/CVE-2021-37666/44033",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-22897",
            "id": "pyup.io-44004",
            "more_info_path": "/vulnerabilities/CVE-2021-22897/44004",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37677",
            "id": "pyup.io-44014",
            "more_info_path": "/vulnerabilities/CVE-2021-37677/44014",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37686",
            "id": "pyup.io-41286",
            "more_info_path": "/vulnerabilities/CVE-2021-37686/41286",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37647",
            "id": "pyup.io-44044",
            "more_info_path": "/vulnerabilities/CVE-2021-37647/44044",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37683",
            "id": "pyup.io-44055",
            "more_info_path": "/vulnerabilities/CVE-2021-37683/44055",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37671",
            "id": "pyup.io-44059",
            "more_info_path": "/vulnerabilities/CVE-2021-37671/44059",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37648",
            "id": "pyup.io-44057",
            "more_info_path": "/vulnerabilities/CVE-2021-37648/44057",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37655",
            "id": "pyup.io-44009",
            "more_info_path": "/vulnerabilities/CVE-2021-37655/44009",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37682",
            "id": "pyup.io-44028",
            "more_info_path": "/vulnerabilities/CVE-2021-37682/44028",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37673",
            "id": "pyup.io-44016",
            "more_info_path": "/vulnerabilities/CVE-2021-37673/44016",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37691",
            "id": "pyup.io-44022",
            "more_info_path": "/vulnerabilities/CVE-2021-37691/44022",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37679",
            "id": "pyup.io-44015",
            "more_info_path": "/vulnerabilities/CVE-2021-37679/44015",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37643",
            "id": "pyup.io-44039",
            "more_info_path": "/vulnerabilities/CVE-2021-37643/44039",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37667",
            "id": "pyup.io-44042",
            "more_info_path": "/vulnerabilities/CVE-2021-37667/44042",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37684",
            "id": "pyup.io-44041",
            "more_info_path": "/vulnerabilities/CVE-2021-37684/44041",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37663",
            "id": "pyup.io-44019",
            "more_info_path": "/vulnerabilities/CVE-2021-37663/44019",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37658",
            "id": "pyup.io-44043",
            "more_info_path": "/vulnerabilities/CVE-2021-37658/44043",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37674",
            "id": "pyup.io-44018",
            "more_info_path": "/vulnerabilities/CVE-2021-37674/44018",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37635",
            "id": "pyup.io-44047",
            "more_info_path": "/vulnerabilities/CVE-2021-37635/44047",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37638",
            "id": "pyup.io-44052",
            "more_info_path": "/vulnerabilities/CVE-2021-37638/44052",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37649",
            "id": "pyup.io-44046",
            "more_info_path": "/vulnerabilities/CVE-2021-37649/44046",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37660",
            "id": "pyup.io-44025",
            "more_info_path": "/vulnerabilities/CVE-2021-37660/44025",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37657",
            "id": "pyup.io-44026",
            "more_info_path": "/vulnerabilities/CVE-2021-37657/44026",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37656",
            "id": "pyup.io-44048",
            "more_info_path": "/vulnerabilities/CVE-2021-37656/44048",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37650",
            "id": "pyup.io-44035",
            "more_info_path": "/vulnerabilities/CVE-2021-37650/44035",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37653",
            "id": "pyup.io-44027",
            "more_info_path": "/vulnerabilities/CVE-2021-37653/44027",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-22876",
            "id": "pyup.io-44005",
            "more_info_path": "/vulnerabilities/CVE-2021-22876/44005",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.5 updates tensorflow to v2.3.4 to address security vulnerabilities.",
            "cve": "CVE-2021-37672",
            "id": "pyup.io-44012",
            "more_info_path": "/vulnerabilities/CVE-2021-37672/44012",
            "specs": [
                "<2.8.5"
            ],
            "v": "<2.8.5"
        },
        {
            "advisory": "Rasa 2.8.9 updates its dependency 'tensorflow' to v2.6 to include several security fixes.",
            "cve": "CVE-2020-15266",
            "id": "pyup.io-42671",
            "more_info_path": "/vulnerabilities/CVE-2020-15266/42671",
            "specs": [
                "<2.8.9"
            ],
            "v": "<2.8.9"
        },
        {
            "advisory": "Rasa 2.8.9 updates its dependency 'tensorflow' to v2.6 to include several security fixes.\r\nhttps://github.com/RasaHQ/rasa/commit/c57dbd466dc153126f1486aafb60b8f19fb911e4",
            "cve": "CVE-2020-15265",
            "id": "pyup.io-42670",
            "more_info_path": "/vulnerabilities/CVE-2020-15265/42670",
            "specs": [
                "<2.8.9"
            ],
            "v": "<2.8.9"
        },
        {
            "advisory": "Rasa 3.0.0 includes a version of 'rasa-sdk' that updates its dependency 'websockets' to v9.1 to include a security fix.\r\nhttps://github.com/RasaHQ/rasa-sdk/issues/500",
            "cve": "CVE-2021-33880",
            "id": "pyup.io-42811",
            "more_info_path": "/vulnerabilities/CVE-2021-33880/42811",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Rasa 3.0.0 includes a version of 'rasa-sdk' that drops support for Python 3.6, as it is arriving to end of life on Dec 23rd 2021.\r\nhttps://github.com/rasahq/rasa/issues/8569",
            "cve": "CVE-2022-26488",
            "id": "pyup.io-42804",
            "more_info_path": "/vulnerabilities/CVE-2022-26488/42804",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        },
        {
            "advisory": "Rasa 3.0.11 and 3.1.4 update its dependency 'pillow' to v9.1.1 to include a security fix.",
            "cve": "CVE-2022-30595",
            "id": "pyup.io-49590",
            "more_info_path": "/vulnerabilities/CVE-2022-30595/49590",
            "specs": [
                "<3.0.11",
                ">=3.1.0,<3.1.4"
            ],
            "v": "<3.0.11,>=3.1.0,<3.1.4"
        },
        {
            "advisory": "Rasa 3.0.11 and 3.1.4 update its dependency 'ujson' to v5.3.0 to include a security fix.",
            "cve": "CVE-2021-45958",
            "id": "pyup.io-49582",
            "more_info_path": "/vulnerabilities/CVE-2021-45958/49582",
            "specs": [
                "<3.0.11",
                ">=3.1.0,<3.1.4"
            ],
            "v": "<3.0.11,>=3.1.0,<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-27778",
            "id": "pyup.io-49595",
            "more_info_path": "/vulnerabilities/CVE-2022-27778/49595",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-27776",
            "id": "pyup.io-49594",
            "more_info_path": "/vulnerabilities/CVE-2022-27776/49594",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-27775",
            "id": "pyup.io-49593",
            "more_info_path": "/vulnerabilities/CVE-2022-27775/49593",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-27780",
            "id": "pyup.io-49597",
            "more_info_path": "/vulnerabilities/CVE-2022-27780/49597",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-27782",
            "id": "pyup.io-49599",
            "more_info_path": "/vulnerabilities/CVE-2022-27782/49599",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-27781",
            "id": "pyup.io-49598",
            "more_info_path": "/vulnerabilities/CVE-2022-27781/49598",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29213",
            "id": "pyup.io-49621",
            "more_info_path": "/vulnerabilities/CVE-2022-29213/49621",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29203",
            "id": "pyup.io-49612",
            "more_info_path": "/vulnerabilities/CVE-2022-29203/49612",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29202",
            "id": "pyup.io-49611",
            "more_info_path": "/vulnerabilities/CVE-2022-29202/49611",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29197",
            "id": "pyup.io-49606",
            "more_info_path": "/vulnerabilities/CVE-2022-29197/49606",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29200",
            "id": "pyup.io-49609",
            "more_info_path": "/vulnerabilities/CVE-2022-29200/49609",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29199",
            "id": "pyup.io-49608",
            "more_info_path": "/vulnerabilities/CVE-2022-29199/49608",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29196",
            "id": "pyup.io-49605",
            "more_info_path": "/vulnerabilities/CVE-2022-29196/49605",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29193",
            "id": "pyup.io-49602",
            "more_info_path": "/vulnerabilities/CVE-2022-29193/49602",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29192",
            "id": "pyup.io-49601",
            "more_info_path": "/vulnerabilities/CVE-2022-29192/49601",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29191",
            "id": "pyup.io-49600",
            "more_info_path": "/vulnerabilities/CVE-2022-29191/49600",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-27774",
            "id": "pyup.io-49592",
            "more_info_path": "/vulnerabilities/CVE-2022-27774/49592",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29216",
            "id": "pyup.io-49622",
            "more_info_path": "/vulnerabilities/CVE-2022-29216/49622",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29205",
            "id": "pyup.io-49614",
            "more_info_path": "/vulnerabilities/CVE-2022-29205/49614",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-22576",
            "id": "pyup.io-49591",
            "more_info_path": "/vulnerabilities/CVE-2022-22576/49591",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29212",
            "id": "pyup.io-49620",
            "more_info_path": "/vulnerabilities/CVE-2022-29212/49620",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29204",
            "id": "pyup.io-49613",
            "more_info_path": "/vulnerabilities/CVE-2022-29204/49613",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-27779",
            "id": "pyup.io-49596",
            "more_info_path": "/vulnerabilities/CVE-2022-27779/49596",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-30115",
            "id": "pyup.io-49623",
            "more_info_path": "/vulnerabilities/CVE-2022-30115/49623",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29211",
            "id": "pyup.io-49619",
            "more_info_path": "/vulnerabilities/CVE-2022-29211/49619",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29209",
            "id": "pyup.io-49618",
            "more_info_path": "/vulnerabilities/CVE-2022-29209/49618",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29206",
            "id": "pyup.io-49615",
            "more_info_path": "/vulnerabilities/CVE-2022-29206/49615",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29201",
            "id": "pyup.io-49610",
            "more_info_path": "/vulnerabilities/CVE-2022-29201/49610",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29207",
            "id": "pyup.io-49616",
            "more_info_path": "/vulnerabilities/CVE-2022-29207/49616",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29208",
            "id": "pyup.io-49617",
            "more_info_path": "/vulnerabilities/CVE-2022-29208/49617",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29198",
            "id": "pyup.io-49607",
            "more_info_path": "/vulnerabilities/CVE-2022-29198/49607",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29195",
            "id": "pyup.io-49604",
            "more_info_path": "/vulnerabilities/CVE-2022-29195/49604",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2022-29194",
            "id": "pyup.io-49603",
            "more_info_path": "/vulnerabilities/CVE-2022-29194/49603",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.1.4 updates its dependency 'tensorflow' to v2.7.3 to include security fixes.",
            "cve": "CVE-2018-25032",
            "id": "pyup.io-49581",
            "more_info_path": "/vulnerabilities/CVE-2018-25032/49581",
            "specs": [
                "<3.1.4"
            ],
            "v": "<3.1.4"
        },
        {
            "advisory": "Rasa 3.3.1 updates its dependency 'numpy' to v1.23.4 to include security fixes.",
            "cve": "CVE-2021-41495",
            "id": "pyup.io-51806",
            "more_info_path": "/vulnerabilities/CVE-2021-41495/51806",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "Rasa 3.3.1 updates its dependency 'numpy' to v1.23.4 to include security fixes.",
            "cve": "CVE-2021-34141",
            "id": "pyup.io-51877",
            "more_info_path": "/vulnerabilities/CVE-2021-34141/51877",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "Rasa 3.3.1 updates its dependency 'numpy' to v1.23.4 to include security fixes.",
            "cve": "CVE-2021-41496",
            "id": "pyup.io-51879",
            "more_info_path": "/vulnerabilities/CVE-2021-41496/51879",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "Rasa 3.3.1 updates its dependency 'numpy' to v1.23.4 to include security fixes.",
            "cve": "CVE-2021-33430",
            "id": "pyup.io-51878",
            "more_info_path": "/vulnerabilities/CVE-2021-33430/51878",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        },
        {
            "advisory": "Rasa 3.5.6 includes a fix for a ReDoS vulnerability in Slack connector.\r\nhttps://github.com/rasahq/rasa/issues/12280",
            "cve": "PVE-2023-58646",
            "id": "pyup.io-58646",
            "more_info_path": "/vulnerabilities/PVE-2023-58646/58646",
            "specs": [
                "<3.5.6"
            ],
            "v": "<3.5.6"
        },
        {
            "advisory": "Rasa 3.6.12 updates its dependency 'pillow' to include a fix for a high-risk vulnerability affecting libwebp.",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61703",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61703",
            "specs": [
                "<3.6.12"
            ],
            "v": "<3.6.12"
        },
        {
            "advisory": "A vulnerability has been identified in Rasa Pro and Rasa Open Source that enables an attacker who can load a maliciously crafted model remotely into a Rasa instance to achieve Remote Code Execution. The prerequisites for this are: - The HTTP API must be enabled on the Rasa instance eg with --enable-api. This is not the default configuration. - For unauthenticated RCE to be exploitable, the user must not have configured any authentication or other security controls recommended in our documentation. - For authenticated RCE, the attacker must possess a valid authentication token or JWT to interact with the Rasa API.",
            "cve": "CVE-2024-49375",
            "id": "pyup.io-76362",
            "more_info_path": "/vulnerabilities/CVE-2024-49375/76362",
            "specs": [
                "<3.6.21"
            ],
            "v": "<3.6.21"
        },
        {
            "advisory": "Rasa 3.6.6 updates its dependency 'wheel' to include a fix for ReDoS vulnerability.\r\nhttps://github.com/rasahq/rasa/issues/12755",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-60657",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/60657",
            "specs": [
                "<3.6.6"
            ],
            "v": "<3.6.6"
        },
        {
            "advisory": "Rasa 3.6.6 updates its dependency 'setuptools' to include a fix for ReDoS vulnerability.\r\nhttps://github.com/rasahq/rasa/issues/12755",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-60644",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/60644",
            "specs": [
                "<3.6.6"
            ],
            "v": "<3.6.6"
        },
        {
            "advisory": "Rasa 3.6.7 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a vulnerability.\r\nhttps://github.com/RasaHQ/rasa/pull/12768",
            "cve": "PVE-2023-60809",
            "id": "pyup.io-60809",
            "more_info_path": "/vulnerabilities/PVE-2023-60809/60809",
            "specs": [
                "<3.6.7"
            ],
            "v": "<3.6.7"
        },
        {
            "advisory": "Rasa 3.6.7 updates its dependency 'scipy' to version '1.10.1' to include a fix for a DoS vulnerability.",
            "cve": "CVE-2023-25399",
            "id": "pyup.io-60811",
            "more_info_path": "/vulnerabilities/CVE-2023-25399/60811",
            "specs": [
                "<3.6.7"
            ],
            "v": "<3.6.7"
        },
        {
            "advisory": "Rasa 3.6.7 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a vulnerability.\r\nhttps://github.com/RasaHQ/rasa/pull/12768",
            "cve": "CVE-2023-38325",
            "id": "pyup.io-60810",
            "more_info_path": "/vulnerabilities/CVE-2023-38325/60810",
            "specs": [
                "<3.6.7"
            ],
            "v": "<3.6.7"
        },
        {
            "advisory": "Rasa 3.6.7 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a DoS vulnerability.\r\nhttps://github.com/RasaHQ/rasa/pull/12768",
            "cve": "CVE-2023-3446",
            "id": "pyup.io-60808",
            "more_info_path": "/vulnerabilities/CVE-2023-3446/60808",
            "specs": [
                "<3.6.7"
            ],
            "v": "<3.6.7"
        },
        {
            "advisory": "Rasa 3.6.7 updates its dependency 'certifi' to version '2023.7.22' to include a fix for a vulnerability.\r\nhttps://github.com/RasaHQ/rasa/pull/12768",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60788",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60788",
            "specs": [
                "<3.6.7"
            ],
            "v": "<3.6.7"
        },
        {
            "advisory": "Rasa 3.6.7 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a DoS vulnerability.\r\nhttps://github.com/RasaHQ/rasa/pull/12768",
            "cve": "CVE-2023-3817",
            "id": "pyup.io-60807",
            "more_info_path": "/vulnerabilities/CVE-2023-3817/60807",
            "specs": [
                "<3.6.7"
            ],
            "v": "<3.6.7"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23589",
            "id": "pyup.io-47009",
            "more_info_path": "/vulnerabilities/CVE-2022-23589/47009",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23566",
            "id": "pyup.io-46986",
            "more_info_path": "/vulnerabilities/CVE-2022-23566/46986",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23558",
            "id": "pyup.io-46978",
            "more_info_path": "/vulnerabilities/CVE-2022-23558/46978",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23564",
            "id": "pyup.io-46984",
            "more_info_path": "/vulnerabilities/CVE-2022-23564/46984",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21732",
            "id": "pyup.io-46967",
            "more_info_path": "/vulnerabilities/CVE-2022-21732/46967",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23588",
            "id": "pyup.io-47008",
            "more_info_path": "/vulnerabilities/CVE-2022-23588/47008",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23587",
            "id": "pyup.io-47007",
            "more_info_path": "/vulnerabilities/CVE-2022-23587/47007",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23586",
            "id": "pyup.io-47006",
            "more_info_path": "/vulnerabilities/CVE-2022-23586/47006",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23584",
            "id": "pyup.io-47004",
            "more_info_path": "/vulnerabilities/CVE-2022-23584/47004",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23579",
            "id": "pyup.io-46999",
            "more_info_path": "/vulnerabilities/CVE-2022-23579/46999",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23578",
            "id": "pyup.io-46998",
            "more_info_path": "/vulnerabilities/CVE-2022-23578/46998",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23577",
            "id": "pyup.io-46997",
            "more_info_path": "/vulnerabilities/CVE-2022-23577/46997",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23575",
            "id": "pyup.io-46995",
            "more_info_path": "/vulnerabilities/CVE-2022-23575/46995",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23574",
            "id": "pyup.io-46994",
            "more_info_path": "/vulnerabilities/CVE-2022-23574/46994",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23573",
            "id": "pyup.io-46993",
            "more_info_path": "/vulnerabilities/CVE-2022-23573/46993",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23572",
            "id": "pyup.io-46992",
            "more_info_path": "/vulnerabilities/CVE-2022-23572/46992",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23565",
            "id": "pyup.io-46985",
            "more_info_path": "/vulnerabilities/CVE-2022-23565/46985",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23561",
            "id": "pyup.io-46981",
            "more_info_path": "/vulnerabilities/CVE-2022-23561/46981",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23567",
            "id": "pyup.io-46987",
            "more_info_path": "/vulnerabilities/CVE-2022-23567/46987",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23591",
            "id": "pyup.io-47010",
            "more_info_path": "/vulnerabilities/CVE-2022-23591/47010",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23576",
            "id": "pyup.io-46996",
            "more_info_path": "/vulnerabilities/CVE-2022-23576/46996",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23562",
            "id": "pyup.io-46982",
            "more_info_path": "/vulnerabilities/CVE-2022-23562/46982",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2020-10531",
            "id": "pyup.io-46959",
            "more_info_path": "/vulnerabilities/CVE-2020-10531/46959",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23570",
            "id": "pyup.io-46990",
            "more_info_path": "/vulnerabilities/CVE-2022-23570/46990",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23582",
            "id": "pyup.io-47002",
            "more_info_path": "/vulnerabilities/CVE-2022-23582/47002",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23595",
            "id": "pyup.io-47011",
            "more_info_path": "/vulnerabilities/CVE-2022-23595/47011",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23585",
            "id": "pyup.io-47005",
            "more_info_path": "/vulnerabilities/CVE-2022-23585/47005",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23583",
            "id": "pyup.io-47003",
            "more_info_path": "/vulnerabilities/CVE-2022-23583/47003",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23581",
            "id": "pyup.io-47001",
            "more_info_path": "/vulnerabilities/CVE-2022-23581/47001",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23580",
            "id": "pyup.io-47000",
            "more_info_path": "/vulnerabilities/CVE-2022-23580/47000",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23571",
            "id": "pyup.io-46991",
            "more_info_path": "/vulnerabilities/CVE-2022-23571/46991",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23563",
            "id": "pyup.io-46983",
            "more_info_path": "/vulnerabilities/CVE-2022-23563/46983",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23560",
            "id": "pyup.io-46980",
            "more_info_path": "/vulnerabilities/CVE-2022-23560/46980",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23557",
            "id": "pyup.io-46977",
            "more_info_path": "/vulnerabilities/CVE-2022-23557/46977",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23559",
            "id": "pyup.io-46979",
            "more_info_path": "/vulnerabilities/CVE-2022-23559/46979",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21728",
            "id": "pyup.io-46963",
            "more_info_path": "/vulnerabilities/CVE-2022-21728/46963",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21731",
            "id": "pyup.io-46966",
            "more_info_path": "/vulnerabilities/CVE-2022-21731/46966",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21730",
            "id": "pyup.io-46965",
            "more_info_path": "/vulnerabilities/CVE-2022-21730/46965",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21738",
            "id": "pyup.io-46973",
            "more_info_path": "/vulnerabilities/CVE-2022-21738/46973",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21737",
            "id": "pyup.io-46972",
            "more_info_path": "/vulnerabilities/CVE-2022-21737/46972",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21734",
            "id": "pyup.io-46969",
            "more_info_path": "/vulnerabilities/CVE-2022-21734/46969",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21733",
            "id": "pyup.io-46968",
            "more_info_path": "/vulnerabilities/CVE-2022-21733/46968",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21726",
            "id": "pyup.io-46961",
            "more_info_path": "/vulnerabilities/CVE-2022-21726/46961",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21729",
            "id": "pyup.io-46964",
            "more_info_path": "/vulnerabilities/CVE-2022-21729/46964",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21740",
            "id": "pyup.io-46975",
            "more_info_path": "/vulnerabilities/CVE-2022-21740/46975",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23569",
            "id": "pyup.io-46989",
            "more_info_path": "/vulnerabilities/CVE-2022-23569/46989",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21735",
            "id": "pyup.io-46970",
            "more_info_path": "/vulnerabilities/CVE-2022-21735/46970",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21725",
            "id": "pyup.io-46960",
            "more_info_path": "/vulnerabilities/CVE-2022-21725/46960",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21739",
            "id": "pyup.io-46974",
            "more_info_path": "/vulnerabilities/CVE-2022-21739/46974",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21741",
            "id": "pyup.io-46976",
            "more_info_path": "/vulnerabilities/CVE-2022-21741/46976",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-23568",
            "id": "pyup.io-46988",
            "more_info_path": "/vulnerabilities/CVE-2022-23568/46988",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21736",
            "id": "pyup.io-46971",
            "more_info_path": "/vulnerabilities/CVE-2022-21736/46971",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        },
        {
            "advisory": "Rasa 3.0.x <= 3.0.9 and <=2.8.26 require versions of TensorFlow (2.6.1/2.6.2) that have known vulnerabilities.",
            "cve": "CVE-2022-21727",
            "id": "pyup.io-46962",
            "more_info_path": "/vulnerabilities/CVE-2022-21727/46962",
            "specs": [
                "<=2.8.26",
                ">=3.0.0rc1,<=3.0.9"
            ],
            "v": "<=2.8.26,>=3.0.0rc1,<=3.0.9"
        }
    ],
    "rasa-pro": [
        {
            "advisory": "A vulnerability has been identified in Rasa Pro and Rasa Open Source that enables an attacker who can load a maliciously crafted model remotely into a Rasa instance to achieve Remote Code Execution. The prerequisites for this are: - The HTTP API must be enabled on the Rasa instance eg with --enable-api. This is not the default configuration. - For unauthenticated RCE to be exploitable, the user must not have configured any authentication or other security controls recommended in our documentation. - For authenticated RCE, the attacker must possess a valid authentication token or JWT to interact with the Rasa API.",
            "cve": "CVE-2024-49375",
            "id": "pyup.io-76361",
            "more_info_path": "/vulnerabilities/CVE-2024-49375/76361",
            "specs": [
                "<3.8.18",
                ">=3.9.0,<3.9.16",
                ">=3.10.0,<3.10.12"
            ],
            "v": "<3.8.18,>=3.9.0,<3.9.16,>=3.10.0,<3.10.12"
        },
        {
            "advisory": "Rasa Pro is a framework for building scalable, dynamic conversational AI assistants that integrate large language models (LLMs). A vulnerability has been identified in Rasa Pro where voice connectors in Rasa Pro do not properly implement authentication even when a token is configured in the credentials.yml file. This could allow an attacker to submit voice data to the Rasa Pro assistant from an unauthenticated source. This issue has been patched for audiocodes, audiocodes_stream, and genesys connectors in affected versions.",
            "cve": "CVE-2025-32377",
            "id": "pyup.io-76770",
            "more_info_path": "/vulnerabilities/CVE-2025-32377/76770",
            "specs": [
                ">=3.12.0,<=3.12.5",
                ">=3.11.0,<=3.11.6",
                ">=3.10.0,<=3.10.18",
                "<=3.9.17"
            ],
            "v": ">=3.12.0,<=3.12.5,>=3.11.0,<=3.11.6,>=3.10.0,<=3.10.18,<=3.9.17"
        }
    ],
    "rasa-sdk": [
        {
            "advisory": "Rasa 1.10.0 updates 'pyyaml' dependency to 5.3.1 to fix CVE-2020-1747.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-38229",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/38229",
            "specs": [
                "<1.10.0"
            ],
            "v": "<1.10.0"
        },
        {
            "advisory": "Rasa-sdk 3.6.2 updates its dependency 'wheel' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/RasaHQ/rasa-sdk/pull/1026",
            "cve": "PVE-2023-60638",
            "id": "pyup.io-60638",
            "more_info_path": "/vulnerabilities/PVE-2023-60638/60638",
            "specs": [
                "<3.6.2"
            ],
            "v": "<3.6.2"
        },
        {
            "advisory": "Rasa-sdk 3.6.2 updates its dependency 'wheel' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/RasaHQ/rasa-sdk/pull/1026",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-60643",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/60643",
            "specs": [
                "<3.6.2"
            ],
            "v": "<3.6.2"
        }
    ],
    "rasterio": [
        {
            "advisory": "Rasterio 1.3.0 updates its C dependency 'hdf5' to include security fixes.\r\nhttps://github.com/rasterio/rasterio-wheels/issues/81",
            "cve": "CVE-2020-10812",
            "id": "pyup.io-51987",
            "more_info_path": "/vulnerabilities/CVE-2020-10812/51987",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Rasterio 1.3.0 updates its C dependency 'hdf5' to include security fixes.\r\nhttps://github.com/rasterio/rasterio-wheels/issues/81",
            "cve": "CVE-2020-10809",
            "id": "pyup.io-51988",
            "more_info_path": "/vulnerabilities/CVE-2020-10809/51988",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Rasterio 1.3.0 updates its C dependency 'hdf5' to include security fixes.\r\nhttps://github.com/rasterio/rasterio-wheels/issues/81",
            "cve": "CVE-2020-10810",
            "id": "pyup.io-51986",
            "more_info_path": "/vulnerabilities/CVE-2020-10810/51986",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Rasterio 1.3.0 updates its C dependency 'hdf5' to include security fixes.\r\nhttps://github.com/rasterio/rasterio-wheels/issues/81",
            "cve": "CVE-2020-10811",
            "id": "pyup.io-51985",
            "more_info_path": "/vulnerabilities/CVE-2020-10811/51985",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Rasterio 1.3.0 updates its C dependency 'json-c' to include a security fix.\r\nhttps://github.com/rasterio/rasterio-wheels/issues/81",
            "cve": "CVE-2020-12762",
            "id": "pyup.io-51989",
            "more_info_path": "/vulnerabilities/CVE-2020-12762/51989",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        },
        {
            "advisory": "Rasterio 1.3.8.post2 updates its bundled dependency 'libcurl' to v8.4.0 to include a security fix.",
            "cve": "CVE-2023-38545",
            "id": "pyup.io-61769",
            "more_info_path": "/vulnerabilities/CVE-2023-38545/61769",
            "specs": [
                "<1.3.8.post2"
            ],
            "v": "<1.3.8.post2"
        },
        {
            "advisory": "Rasterio 1.3.8.post2 updates its bundled dependency 'libcurl' to v8.4.0 to include a security fix.\r\nhttps://github.com/rasterio/rasterio-wheels/issues/112",
            "cve": "CVE-2023-38546",
            "id": "pyup.io-61770",
            "more_info_path": "/vulnerabilities/CVE-2023-38546/61770",
            "specs": [
                "<1.3.8.post2"
            ],
            "v": "<1.3.8.post2"
        },
        {
            "advisory": "Rasterio 1.3.8.post1 updates its C dependency 'libwebp' to v1.3.2 to include a fix for a high-risk vulnerability.\r\nhttps://github.com/rasterio/rasterio/discussions/2924",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-61493",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/61493",
            "specs": [
                ">=1.0a1,<1.3.8.post1"
            ],
            "v": ">=1.0a1,<1.3.8.post1"
        }
    ],
    "rauth": [
        {
            "advisory": "rauth before 0.7.0 isn't using a secure random number generator.",
            "cve": "PVE-2021-26099",
            "id": "pyup.io-26099",
            "more_info_path": "/vulnerabilities/PVE-2021-26099/26099",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        }
    ],
    "ravenpy": [
        {
            "advisory": "Ravenpy 0.9.0 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.",
            "cve": "CVE-2007-4559",
            "id": "pyup.io-51541",
            "more_info_path": "/vulnerabilities/CVE-2007-4559/51541",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        }
    ],
    "raxe": [
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal attacks due to improper validation of file paths. The package fails to correctly sanitize file paths in tarball archives, allowing for directory traversal attacks. An attacker can exploit this vulnerability by crafting a malicious tarball that, when extracted, writes files to arbitrary locations on the filesystem, potentially leading to unauthorized access or modification of sensitive files.",
            "cve": "PVE-2025-83638",
            "id": "pyup.io-83638",
            "more_info_path": "/vulnerabilities/PVE-2025-83638/83638",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to inefficient pattern matching. Certain regular expressions used in pattern matching can be exploited to cause excessive backtracking. An attacker can exploit this vulnerability by providing specially crafted input that triggers the inefficient pattern, leading to a denial of service by consuming excessive CPU resources.",
            "cve": "PVE-2025-83617",
            "id": "pyup.io-83617",
            "more_info_path": "/vulnerabilities/PVE-2025-83617/83617",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "ray": [
        {
            "advisory": "Ray 1.10.0 updates its dependency 'log4j' to v2.17.1 to include a security fix.",
            "cve": "CVE-2021-44832",
            "id": "pyup.io-44466",
            "more_info_path": "/vulnerabilities/CVE-2021-44832/44466",
            "specs": [
                "<1.10.0"
            ],
            "v": "<1.10.0"
        },
        {
            "advisory": "Ray 1.8.0 fixes a race condition for the stats_fn when using multi-gpu. That caused an issue for any algorithm in which the loss function stores values as members in the policy for later retrieval.\r\nhttps://github.com/ray-project/ray/issues/18812",
            "cve": "PVE-2021-42426",
            "id": "pyup.io-42426",
            "more_info_path": "/vulnerabilities/PVE-2021-42426/42426",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        },
        {
            "advisory": "Ray 1.9.1 updates its dependency 'log4j' to v2.16.0 to include security fixes.\r\nhttps://github.com/ray-project/ray/commit/2cdbf974ea63caf4323aacbccaef2394a14a8562",
            "cve": "CVE-2021-45046",
            "id": "pyup.io-43415",
            "more_info_path": "/vulnerabilities/CVE-2021-45046/43415",
            "specs": [
                "<1.9.1"
            ],
            "v": "<1.9.1"
        },
        {
            "advisory": "Ray 1.9.1 updates its dependency 'log4j' to v2.16.0 to include security fixes.\r\nhttps://github.com/ray-project/ray/commit/2cdbf974ea63caf4323aacbccaef2394a14a8562",
            "cve": "CVE-2021-44228",
            "id": "pyup.io-43413",
            "more_info_path": "/vulnerabilities/CVE-2021-44228/43413",
            "specs": [
                "<1.9.1"
            ],
            "v": "<1.9.1"
        },
        {
            "advisory": "Ray 1.9.2 updates its dependency 'log4j' to v2.17.0 to include a security fix.",
            "cve": "CVE-2021-45105",
            "id": "pyup.io-43437",
            "more_info_path": "/vulnerabilities/CVE-2021-45105/43437",
            "specs": [
                "<1.9.2"
            ],
            "v": "<1.9.2"
        },
        {
            "advisory": "Ray version 2.11.0 includes a fix for a race condition issue that occurred during the creation of actors in multi-threaded environments.",
            "cve": "PVE-2024-70485",
            "id": "pyup.io-70485",
            "more_info_path": "/vulnerabilities/PVE-2024-70485/70485",
            "specs": [
                "<2.11.0"
            ],
            "v": "<2.11.0"
        },
        {
            "advisory": "Versions of the package ray before 2.43.0 are vulnerable to Insertion of Sensitive Information into Log File where the redis password is being logged in the standard logging. If the redis password is passed as an argument, it will be logged and could potentially leak the password.",
            "cve": "CVE-2025-1979",
            "id": "pyup.io-76318",
            "more_info_path": "/vulnerabilities/CVE-2025-1979/76318",
            "specs": [
                "<2.43.0"
            ],
            "v": "<2.43.0"
        },
        {
            "advisory": "Affected versions of the ray package are vulnerable to Remote Code Execution (RCE) due to unauthenticated job submission endpoints and weak User-Agent-based browser request filtering that can be bypassed via DNS rebinding. The /api/jobs and /api/job_agent/jobs/ endpoints on the Ray dashboard accept arbitrary shell command strings in the entrypoint field without authentication or CSRF protections, while the is_browser_request and browsers_no_post_put_middleware helpers incorrectly assume that browser fetch calls cannot change the User-Agent header, allowing Firefox and Safari to bypass the \u201cbrowser request\u201d checks once a DNS rebinding attack has shifted the hostname to a local or internal Ray instance.",
            "cve": "CVE-2025-62593",
            "id": "pyup.io-82002",
            "more_info_path": "/vulnerabilities/CVE-2025-62593/82002",
            "specs": [
                "<2.52.0"
            ],
            "v": "<2.52.0"
        },
        {
            "advisory": "Ray 2.8.1 includes a fix for CVE-2023-6019: A command injection exists in Ray's cpu_profile URL parameter allowing attackers to execute os commands on the system running the ray dashboard remotely without authentication.\r\nhttps://www.anyscale.com/blog/update-on-ray-cves-cve-2023-6019-cve-2023-6020-cve-2023-6021-cve-2023-48022-cve-2023-48023",
            "cve": "CVE-2023-6019",
            "id": "pyup.io-62632",
            "more_info_path": "/vulnerabilities/CVE-2023-6019/62632",
            "specs": [
                "<2.8.1"
            ],
            "v": "<2.8.1"
        },
        {
            "advisory": "Ray 2.8.1 includes a fix for CVE-2023-48023: Anyscale Ray 2.6.3 and 2.8.0 allows SSRF through /log_proxy. \r\nNOTE: the vendor's position is that this report is irrelevant because Ray, as stated in its documentation, is not intended for use outside of a strictly controlled network environment",
            "cve": "CVE-2023-48023",
            "id": "pyup.io-62651",
            "more_info_path": "/vulnerabilities/CVE-2023-48023/62651",
            "specs": [
                "<2.8.1"
            ],
            "v": "<2.8.1"
        },
        {
            "advisory": "Ray 2.8.1 includes a fix for CVE-2023-6021: LFI in Ray's log API endpoint allows attackers to read any file on the server without authentication.\r\nhttps://www.anyscale.com/blog/update-on-ray-cves-cve-2023-6019-cve-2023-6020-cve-2023-6021-cve-2023-48022-cve-2023-48023",
            "cve": "CVE-2023-6021",
            "id": "pyup.io-62650",
            "more_info_path": "/vulnerabilities/CVE-2023-6021/62650",
            "specs": [
                "<2.8.1"
            ],
            "v": "<2.8.1"
        },
        {
            "advisory": "Ray 2.8.1 includes a fix for CVE-2023-6020: LFI in Ray's /static/ directory allows attackers to read any file on the server without authentication.\r\nhttps://www.anyscale.com/blog/update-on-ray-cves-cve-2023-6019-cve-2023-6020-cve-2023-6021-cve-2023-48022-cve-2023-48023",
            "cve": "CVE-2023-6020",
            "id": "pyup.io-62649",
            "more_info_path": "/vulnerabilities/CVE-2023-6020/62649",
            "specs": [
                "<2.8.1"
            ],
            "v": "<2.8.1"
        },
        {
            "advisory": "Ray 2.9.0 upgrades grpc from 1.50.2 to 1.57.1 to include security patches.\r\nhttps://github.com/ray-project/ray/pull/39090",
            "cve": "PVE-2023-63050",
            "id": "pyup.io-63050",
            "more_info_path": "/vulnerabilities/PVE-2023-63050/63050",
            "specs": [
                "<2.9.0"
            ],
            "v": "<2.9.0"
        },
        {
            "advisory": "Affected versions of the ray package are vulnerable to Remote Code Execution due to an insecure default configuration that leaves token-based authentication for Ray management interfaces disabled unless explicitly turned on. In versions up to and including 2.52.0, the Ray dashboard and Jobs API endpoints are exposed in an unauthenticated state when RAY_AUTH_MODE is not set to token, so job submission and cluster management requests are accepted without verifying any authentication token, reflecting the weaknesses described by CWE-304 (Missing Critical Step in Authentication) and CWE-1188 (Insecure Default Initialization of Resource).\r\n# NOTE: The vendor plans to enable token authentication by default in a future release. They recommend enabling token authentication to protect your cluster from unauthorized access.",
            "cve": "CVE-2025-34351",
            "id": "pyup.io-82201",
            "more_info_path": "/vulnerabilities/CVE-2025-34351/82201",
            "specs": [
                "<=2.52.0"
            ],
            "v": "<=2.52.0"
        },
        {
            "advisory": "*DISPUTED* Ray allows a remote attacker to execute arbitrary code via the job submission API. In the default configuration, Ray does not enforce authentication. As a result, attackers may freely submit jobs, delete existing jobs, retrieve sensitive information, and exploit the other vulnerabilities described in this advisory. While the Ray documentation included an optional mutual TLS authentication mode, Ray does not appear to support an authorization model. In other words, even if a Ray administrator explicitly enabled TLS authentication, they would be unable to grant users different permissions, such as read-only access to the Ray Dashboard.\r\nThe most direct method of exploitation discovered is to submit arbitrary operating system commands for execution via the job submission API using a raw HTTP request or the Ray Jobs Python SDK. These do not require authentication in the default configuration, and are accessible remotely to any system with access to the Ray Dashboard (TCP port 8265 by default).\r\nNOTE: The vendor's position is that this report is irrelevant because Ray, as stated in its documentation, is not intended for use outside of a strictly controlled network environment.\r\nNOTE2: This flaw has been under active exploitation in the wild and it was baptized 'ShadowRay'.",
            "cve": "CVE-2023-48022",
            "id": "pyup.io-65189",
            "more_info_path": "/vulnerabilities/CVE-2023-48022/65189",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "ray-on-aml": [
        {
            "advisory": "Ray-on-aml 0.0.4 updates its dependency 'ray' to v1.9.1 to include security fixes.",
            "cve": "CVE-2021-44228",
            "id": "pyup.io-43977",
            "more_info_path": "/vulnerabilities/CVE-2021-44228/43977",
            "specs": [
                "<0.0.4"
            ],
            "v": "<0.0.4"
        },
        {
            "advisory": "Ray-on-aml 0.0.4 updates its dependency 'ray' to v1.9.1 to include security fixes.",
            "cve": "CVE-2021-45046",
            "id": "pyup.io-44476",
            "more_info_path": "/vulnerabilities/CVE-2021-45046/44476",
            "specs": [
                "<0.0.4"
            ],
            "v": "<0.0.4"
        },
        {
            "advisory": "Ray-on-aml 0.0.7 updates its dependency 'ray' to v1.9.2 to include a security fix.\r\nhttps://github.com/james-tn/ray-on-aml/commit/5f72098d01c3f8527a0fa2963f265b3edbb9b6ea",
            "cve": "CVE-2021-45105",
            "id": "pyup.io-44477",
            "more_info_path": "/vulnerabilities/CVE-2021-45105/44477",
            "specs": [
                "<0.0.7"
            ],
            "v": "<0.0.7"
        },
        {
            "advisory": "Ray-on-aml 0.1.5 updates its dependency 'ray' to v1.10.0 to include a security fix.",
            "cve": "CVE-2021-44832",
            "id": "pyup.io-44478",
            "more_info_path": "/vulnerabilities/CVE-2021-44832/44478",
            "specs": [
                "<0.1.5"
            ],
            "v": "<0.1.5"
        }
    ],
    "raylib": [
        {
            "advisory": "Raylib 1.1.1 adds a security check if a file doesn't exist - [textures]",
            "cve": "PVE-2021-37166",
            "id": "pyup.io-37166",
            "more_info_path": "/vulnerabilities/PVE-2021-37166/37166",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        },
        {
            "advisory": "Raylib 1.2 adds a security check in case deployed vertex excess buffer size - [rlgl]",
            "cve": "PVE-2021-37165",
            "id": "pyup.io-37165",
            "more_info_path": "/vulnerabilities/PVE-2021-37165/37165",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        }
    ],
    "razo": [
        {
            "advisory": "Razo 19.0.0 adds security for root password.",
            "cve": "PVE-2022-48489",
            "id": "pyup.io-48489",
            "more_info_path": "/vulnerabilities/PVE-2022-48489/48489",
            "specs": [
                "<19.0.0"
            ],
            "v": "<19.0.0"
        }
    ],
    "rbtools": [
        {
            "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in the commenting system in Review Board before 1.5.7 and 1.6.x before 1.6.3 allow remote attackers to inject arbitrary web script or HTML via vectors involving the (1) diff viewer or (2) screenshot component.",
            "cve": "CVE-2011-4312",
            "id": "pyup.io-62095",
            "more_info_path": "/vulnerabilities/CVE-2011-4312/62095",
            "specs": [
                "<1.5.7",
                ">=1.6.0,<1.6.3"
            ],
            "v": "<1.5.7,>=1.6.0,<1.6.3"
        }
    ],
    "rdflib": [
        {
            "advisory": "Rdflib 4.0 includes validation for URIRefs and Literal language tags on construction to avoiding some \"RDF-injection\" issues.\r\nhttps://github.com/RDFLib/rdflib/issues/266",
            "cve": "PVE-2021-41014",
            "id": "pyup.io-41014",
            "more_info_path": "/vulnerabilities/PVE-2021-41014/41014",
            "specs": [
                "<4.0"
            ],
            "v": "<4.0"
        }
    ],
    "rdiff-backup": [
        {
            "advisory": "Version 0.5.0 increased rdiff-backup's security by using popen2.Popen3 and os.spawnvp instead of os.popen and os.system.",
            "cve": "PVE-2021-38068",
            "id": "pyup.io-38068",
            "more_info_path": "/vulnerabilities/PVE-2021-38068/38068",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        },
        {
            "advisory": "Rdiff-backup 0.9.3 adds some security features to the protocol, so rdiff-backup will now only allow commands from remote connections.  The extra security will be enabled automatically on the client (it knows what to expect), but\r\nthe extra switches --restrict, --restrict-update-only, and --restrict-read-only have been added for use with --server.",
            "cve": "PVE-2021-38067",
            "id": "pyup.io-38067",
            "more_info_path": "/vulnerabilities/PVE-2021-38067/38067",
            "specs": [
                "<0.9.3"
            ],
            "v": "<0.9.3"
        },
        {
            "advisory": "Rdiff-backup 1.0.2 includes a fix for a spurious security violation from --create-full-path and a fix for bug 14545 which was introduced in version 1.0.1:  Quoting caused a spurious security violation.",
            "cve": "PVE-2021-38064",
            "id": "pyup.io-38064",
            "more_info_path": "/vulnerabilities/PVE-2021-38064/38064",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        },
        {
            "advisory": "Rdiff-backup 1.1.6 fixes a security violation when restoring from a remote repository.",
            "cve": "PVE-2021-38063",
            "id": "pyup.io-38063",
            "more_info_path": "/vulnerabilities/PVE-2021-38063/38063",
            "specs": [
                "<1.1.6"
            ],
            "v": "<1.1.6"
        }
    ],
    "rdiffweb": [
        {
            "advisory": "Rdiffweb versions prior to 2.3.7 are vulnerable to Cross-Site Request Forgery (CSRF).",
            "cve": "PVE-2023-99952",
            "id": "pyup.io-60910",
            "more_info_path": "/vulnerabilities/PVE-2023-99952/60910",
            "specs": [
                "<2.3.7"
            ],
            "v": "<2.3.7"
        },
        {
            "advisory": "Rdiffweb prior to version 2.4.4 is vulnerable to potential brute-force password attacks due to a weak IP detection mechanism in the login API. Under usual circumstances, the user's IP address should be blocked after five unsuccessful login attempts. However, a loophole in the system can be exploited using the X-Forwarded-For header, enabling attackers to bypass IP detection and carry out a brute-force attack to crack the password.",
            "cve": "PVE-2023-99951",
            "id": "pyup.io-60911",
            "more_info_path": "/vulnerabilities/PVE-2023-99951/60911",
            "specs": [
                "<2.4.4"
            ],
            "v": "<2.4.4"
        },
        {
            "advisory": "Rdiffweb 2.5.0a2 includes a fix for an open redirect vulnerability: This flaw allows attackers to reroute users to any website of their choice, potentially enabling phishing attacks.",
            "cve": "PVE-2023-99950",
            "id": "pyup.io-60912",
            "more_info_path": "/vulnerabilities/PVE-2023-99950/60912",
            "specs": [
                "<2.5.0a2"
            ],
            "v": "<2.5.0a2"
        },
        {
            "advisory": "Allocation of Resources Without Limits or Throttling in GitHub repository ikus060/rdiffweb prior to 2.8.0.",
            "cve": "CVE-2023-4138",
            "id": "pyup.io-65256",
            "more_info_path": "/vulnerabilities/CVE-2023-4138/65256",
            "specs": [
                "<2.8.1"
            ],
            "v": "<2.8.1"
        },
        {
            "advisory": "Rdiffweb 2.8.4 includes a fix for CVE-2023-5289: Allocation of Resources Without Limits or Throttling.\r\nhttps://github.com/ikus060/rdiffweb/commit/06f89b43469aae70e8833e55192721523f86c5a2",
            "cve": "CVE-2023-5289",
            "id": "pyup.io-63072",
            "more_info_path": "/vulnerabilities/CVE-2023-5289/63072",
            "specs": [
                "<2.8.4"
            ],
            "v": "<2.8.4"
        },
        {
            "advisory": "Improper Restriction of Rendered UI Layers or Frames in GitHub repository ikus060/rdiffweb prior to 2.4.1.",
            "cve": "CVE-2022-3167",
            "id": "pyup.io-54530",
            "more_info_path": "/vulnerabilities/CVE-2022-3167/54530",
            "specs": [
                ">=0,<2.4.1"
            ],
            "v": ">=0,<2.4.1"
        },
        {
            "advisory": "rdiffweb prior to 2.4.10 is vulnerable to Path Traversal. Version 2.4.10 contains a patch.",
            "cve": "CVE-2022-3389",
            "id": "pyup.io-54504",
            "more_info_path": "/vulnerabilities/CVE-2022-3389/54504",
            "specs": [
                ">=0,<2.4.10"
            ],
            "v": ">=0,<2.4.10"
        },
        {
            "advisory": "Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository ikus060/rdiffweb prior to 2.4.2.",
            "cve": "CVE-2022-3174",
            "id": "pyup.io-54513",
            "more_info_path": "/vulnerabilities/CVE-2022-3174/54513",
            "specs": [
                ">=0,<2.4.2"
            ],
            "v": ">=0,<2.4.2"
        },
        {
            "advisory": "Missing Custom Error Page in GitHub repository ikus060/rdiffweb prior to 2.4.2.",
            "cve": "CVE-2022-3175",
            "id": "pyup.io-54515",
            "more_info_path": "/vulnerabilities/CVE-2022-3175/54515",
            "specs": [
                ">=0,<2.4.2"
            ],
            "v": ">=0,<2.4.2"
        },
        {
            "advisory": "Weak Password Requirements in GitHub repository ikus060/rdiffweb prior to 2.4.2.",
            "cve": "CVE-2022-3179",
            "id": "pyup.io-54517",
            "more_info_path": "/vulnerabilities/CVE-2022-3179/54517",
            "specs": [
                ">=0,<2.4.2"
            ],
            "v": ">=0,<2.4.2"
        },
        {
            "advisory": "rdiffweb prior to 2.4.3 is vulnerable to Cross-Site Request Forgery (CSRF). While adding SSH public keys to the profile, the server accepts the GET request, which results in adding an SSH public key to the profile and leads to unauthorized access to the system and backups. Version 2.4.3 contains a patch for this issue.",
            "cve": "CVE-2022-3221",
            "id": "pyup.io-54473",
            "more_info_path": "/vulnerabilities/CVE-2022-3221/54473",
            "specs": [
                ">=0,<2.4.3"
            ],
            "v": ">=0,<2.4.3"
        },
        {
            "advisory": "rdiffweb prior to 2.4.5 is vulnerable to Cross-Site Request Forgery (CSRF). An attacker exploiting this vulnerability can use it to delete repositories and users.",
            "cve": "CVE-2022-3232",
            "id": "pyup.io-54544",
            "more_info_path": "/vulnerabilities/CVE-2022-3232/54544",
            "specs": [
                ">=0,<2.4.5"
            ],
            "v": ">=0,<2.4.5"
        },
        {
            "advisory": "In rdiffweb prior to version 2.4.6, the `cookie` session_id does not have a secure attribute when the URL is invalid. Version 2.4.6 contains a fix for the issue.",
            "cve": "CVE-2022-3250",
            "id": "pyup.io-54491",
            "more_info_path": "/vulnerabilities/CVE-2022-3250/54491",
            "specs": [
                ">=0,<2.4.6"
            ],
            "v": ">=0,<2.4.6"
        },
        {
            "advisory": "rdiffweb prior to 2.4.6 is vulnerable to cross-site request forgery on the repository settings. A malicious user can change the settings of a repository by sending a URL to the victim. This issue is fixed in version 2.4.6.\n\n",
            "cve": "CVE-2022-3267",
            "id": "pyup.io-54494",
            "more_info_path": "/vulnerabilities/CVE-2022-3267/54494",
            "specs": [
                ">=0,<2.4.6"
            ],
            "v": ">=0,<2.4.6"
        },
        {
            "advisory": "Session Fixation in GitHub repository ikus060/rdiffweb prior to 2.4.7.",
            "cve": "CVE-2022-3269",
            "id": "pyup.io-54555",
            "more_info_path": "/vulnerabilities/CVE-2022-3269/54555",
            "specs": [
                ">=0,<2.4.7"
            ],
            "v": ">=0,<2.4.7"
        },
        {
            "advisory": "rdiffwen prior to version 2.4.7 is vulnerable to Cross-Site Request Forgery (CSRF). An attacker can change a user's email ID. Version 2.4.7 has a fix for this issue.",
            "cve": "CVE-2022-3274",
            "id": "pyup.io-54479",
            "more_info_path": "/vulnerabilities/CVE-2022-3274/54479",
            "specs": [
                ">=0,<2.4.7"
            ],
            "v": ">=0,<2.4.7"
        },
        {
            "advisory": "rdiffweb prior to 2.4.8 has no limit in length of root directory names. Allowing users to enter long strings may result in a DOS attack or memory corruption. Version 2.4.8 defines a field limit for username, email, and root directory.",
            "cve": "CVE-2022-3295",
            "id": "pyup.io-54477",
            "more_info_path": "/vulnerabilities/CVE-2022-3295/54477",
            "specs": [
                ">=0,<2.4.8"
            ],
            "v": ">=0,<2.4.8"
        },
        {
            "advisory": "rdiffweb prior to 2.4.8 is vulnerable to a potential Dos attack via an unlimited length \"username\" field. This can result in excess memory consumption, or memory corruption, leading to a Denial of Service (DoS). This issue is patched in version 2.4.8. There are no known workarounds.",
            "cve": "CVE-2022-3290",
            "id": "pyup.io-54481",
            "more_info_path": "/vulnerabilities/CVE-2022-3290/54481",
            "specs": [
                ">=0,<2.4.8"
            ],
            "v": ">=0,<2.4.8"
        },
        {
            "advisory": "rdiffweb prior to 2.4.8 does not validate email length, allowing users to insert an email longer than 255 characters. If a user signs up with an email with a length of 1 million or more characters and logs in, withdraws, or changes their email, the server may cause denial of service due to overload. Version 2.4.8 sets length limits for username, email, and root directory.",
            "cve": "CVE-2022-3272",
            "id": "pyup.io-54483",
            "more_info_path": "/vulnerabilities/CVE-2022-3272/54483",
            "specs": [
                ">=0,<2.4.8"
            ],
            "v": ">=0,<2.4.8"
        },
        {
            "advisory": "rdiffweb prior to 2.4.8 is vulnerable to a potential Dos attack via an unlimited length \"title\" field when adding an SSH key.\nThis can result in excess memory consumption, leading to a Denial of Service (DoS). This issue is patched in version 2.4.8. There are no known workarounds.",
            "cve": "CVE-2022-3298",
            "id": "pyup.io-54485",
            "more_info_path": "/vulnerabilities/CVE-2022-3298/54485",
            "specs": [
                ">=0,<2.4.8"
            ],
            "v": ">=0,<2.4.8"
        },
        {
            "advisory": "rdiffweb prior to version 2.4.8 is vulnerable to Improper Cleanup on Thrown Exception. This could allow an attacker to display a message of their choice onto a web page. Version 2.4.8 contains a fix for this issue.",
            "cve": "CVE-2022-3301",
            "id": "pyup.io-54475",
            "more_info_path": "/vulnerabilities/CVE-2022-3301/54475",
            "specs": [
                ">=0,<2.4.8"
            ],
            "v": ">=0,<2.4.8"
        },
        {
            "advisory": "ikus060/rdiffweb prior to 2.4.9 allows a user to set there password to all spaces. While rdiffweb has a password policy requiring passwords to be between 8 and 128 characters, it does not validate the password entropy, allowing users to bypass password complexity requirements with weak passwords. This issue has been fixed in version 2.4.9. No workarounds are known to exist.",
            "cve": "CVE-2022-3326",
            "id": "pyup.io-54489",
            "more_info_path": "/vulnerabilities/CVE-2022-3326/54489",
            "specs": [
                ">=0,<2.4.9"
            ],
            "v": ">=0,<2.4.9"
        },
        {
            "advisory": "rdiffweb prior to version 2.4.9 is vulnerable to Use of Cache Containing Sensitive Information. Due to improper cache control, an attacker can view sensitive information even if they are not logged into an account. Version 2.4.9 contains a patch for this issue.",
            "cve": "CVE-2022-3292",
            "id": "pyup.io-54487",
            "more_info_path": "/vulnerabilities/CVE-2022-3292/54487",
            "specs": [
                ">=0,<2.4.9"
            ],
            "v": ">=0,<2.4.9"
        },
        {
            "advisory": "rdiffweb prior to 2.5.0a4 allows users to set their new password to be the same as the old password during a password reset. Version 2.5.0a4 enforces a password policy in which a new password cannot be the same as the old one.",
            "cve": "CVE-2022-3376",
            "id": "pyup.io-54507",
            "more_info_path": "/vulnerabilities/CVE-2022-3376/54507",
            "specs": [
                ">=0,<2.5.0"
            ],
            "v": ">=0,<2.5.0"
        },
        {
            "advisory": "rdiffweb prior to 2.5.0a4 does not have a rate limit to prevent attackers attempting brute force attacks to guess passwords. Version 2.5.0a4 limits the number of incorrect password attempts.",
            "cve": "CVE-2022-3273",
            "id": "pyup.io-54506",
            "more_info_path": "/vulnerabilities/CVE-2022-3273/54506",
            "specs": [
                ">=0,<2.5.0"
            ],
            "v": ">=0,<2.5.0"
        },
        {
            "advisory": "Allocation of Resources Without Limits or Throttling in GitHub repository ikus060/rdiffweb prior to 2.5.0.",
            "cve": "CVE-2022-3456",
            "id": "pyup.io-54520",
            "more_info_path": "/vulnerabilities/CVE-2022-3456/54520",
            "specs": [
                ">=0,<2.5.0"
            ],
            "v": ">=0,<2.5.0"
        },
        {
            "advisory": "Allocation of Resources Without Limits or Throttling in GitHub repository ikus060/rdiffweb prior to 2.5.0. ",
            "cve": "CVE-2022-3439",
            "id": "pyup.io-54521",
            "more_info_path": "/vulnerabilities/CVE-2022-3439/54521",
            "specs": [
                ">=0,<2.5.0"
            ],
            "v": ">=0,<2.5.0"
        },
        {
            "advisory": "Missing Authentication for Critical Function in GitHub repository ikus060/rdiffweb prior to 2.5.0.",
            "cve": "CVE-2022-3327",
            "id": "pyup.io-54572",
            "more_info_path": "/vulnerabilities/CVE-2022-3327/54572",
            "specs": [
                ">=0,<2.5.0"
            ],
            "v": ">=0,<2.5.0"
        },
        {
            "advisory": "Insufficient Session Expiration in GitHub repository ikus060/rdiffweb prior to 2.5.0.",
            "cve": "CVE-2022-3362",
            "id": "pyup.io-54584",
            "more_info_path": "/vulnerabilities/CVE-2022-3362/54584",
            "specs": [
                ">=0,<2.5.0"
            ],
            "v": ">=0,<2.5.0"
        },
        {
            "advisory": "rdiffweb prior to 2.5.0a3 does not validate email length, allowing users to insert an email longer than 255 characters. If a user signs up with an email with a length of 1 million or more characters and logs in, withdraws, or changes their email, the server may cause denial of service due to overload. ",
            "cve": "CVE-2022-3364",
            "id": "pyup.io-54496",
            "more_info_path": "/vulnerabilities/CVE-2022-3364/54496",
            "specs": [
                ">=0,<2.5.0a3"
            ],
            "v": ">=0,<2.5.0a3"
        },
        {
            "advisory": "rdiffweb prior to 2.5.0a3 is vulnerable to Allocation of Resources Without Limits or Throttling. A lack of limit in the length of the `Token name` parameter can result in denial of service or memory corruption. Version 2.5.0a3 fixes this issue.",
            "cve": "CVE-2022-3371",
            "id": "pyup.io-54498",
            "more_info_path": "/vulnerabilities/CVE-2022-3371/54498",
            "specs": [
                ">=0,<2.5.0a3"
            ],
            "v": ">=0,<2.5.0a3"
        },
        {
            "advisory": "A lack of user input validation leads to an open redirect vulnerability in rdiffweb prior to 2.5.0a4.",
            "cve": "CVE-2022-3438",
            "id": "pyup.io-54511",
            "more_info_path": "/vulnerabilities/CVE-2022-3438/54511",
            "specs": [
                ">=0,<2.5.0a4"
            ],
            "v": ">=0,<2.5.0a4"
        },
        {
            "advisory": "ikus060/rdiffweb prior to 2.5.0a5 did not enforce origin validation in web traffic. Users are advised to upgrade to version 2.5.0a5.",
            "cve": "CVE-2022-3457",
            "id": "pyup.io-54519",
            "more_info_path": "/vulnerabilities/CVE-2022-3457/54519",
            "specs": [
                ">=0,<2.5.0a5"
            ],
            "v": ">=0,<2.5.0a5"
        },
        {
            "advisory": "Missing Authentication for Critical Function in GitHub repository ikus060/rdiffweb prior to 2.5.0a6.",
            "cve": "CVE-2022-4018",
            "id": "pyup.io-54585",
            "more_info_path": "/vulnerabilities/CVE-2022-4018/54585",
            "specs": [
                ">=0,<2.5.0a6"
            ],
            "v": ">=0,<2.5.0a6"
        },
        {
            "advisory": "Business Logic Errors in GitHub repository ikus060/rdiffweb prior to 2.5.0a7.",
            "cve": "CVE-2022-3363",
            "id": "pyup.io-54565",
            "more_info_path": "/vulnerabilities/CVE-2022-3363/54565",
            "specs": [
                ">=0,<2.5.0a7"
            ],
            "v": ">=0,<2.5.0a7"
        },
        {
            "advisory": "Unauthorized access to settings update, logs , history, delete etc in GitHub repository ikus060/rdiffweb prior to 2.5.2.",
            "cve": "CVE-2022-4314",
            "id": "pyup.io-54580",
            "more_info_path": "/vulnerabilities/CVE-2022-4314/54580",
            "specs": [
                ">=0,<2.5.2"
            ],
            "v": ">=0,<2.5.2"
        },
        {
            "advisory": "rdiffweb prior to version 2.5.4 is vulnerable to Cross-Site Request Forgery (CSRF).",
            "cve": "CVE-2022-4646",
            "id": "pyup.io-54603",
            "more_info_path": "/vulnerabilities/CVE-2022-4646/54603",
            "specs": [
                ">=0,<2.5.4"
            ],
            "v": ">=0,<2.5.4"
        },
        {
            "advisory": "rdiffweb prior to version 2.5.4 has an Open Redirect vulnerability.",
            "cve": "CVE-2022-4644",
            "id": "pyup.io-54604",
            "more_info_path": "/vulnerabilities/CVE-2022-4644/54604",
            "specs": [
                ">=0,<2.5.4"
            ],
            "v": ">=0,<2.5.4"
        },
        {
            "advisory": "Improper Access Control in GitHub repository ikus060/rdiffweb prior to 2.5.5.",
            "cve": "CVE-2022-4724",
            "id": "pyup.io-54639",
            "more_info_path": "/vulnerabilities/CVE-2022-4724/54639",
            "specs": [
                ">=0,<2.5.5"
            ],
            "v": ">=0,<2.5.5"
        },
        {
            "advisory": "Open Redirect in GitHub repository ikus060/rdiffweb prior to 2.5.5.",
            "cve": "CVE-2022-4720",
            "id": "pyup.io-54634",
            "more_info_path": "/vulnerabilities/CVE-2022-4720/54634",
            "specs": [
                ">=0,<2.5.5"
            ],
            "v": ">=0,<2.5.5"
        },
        {
            "advisory": "Authentication Bypass by Primary Weakness in GitHub repository ikus060/rdiffweb prior to 2.5.5.",
            "cve": "CVE-2022-4722",
            "id": "pyup.io-54632",
            "more_info_path": "/vulnerabilities/CVE-2022-4722/54632",
            "specs": [
                ">=0,<2.5.5"
            ],
            "v": ">=0,<2.5.5"
        },
        {
            "advisory": "In rdiffweb prior to 2.5.5, lack of sanitisation of characters in SSH key name could allow attacker to inject a hyperlink injection that could allow attacker to redirect victim to malicious websites.",
            "cve": "CVE-2022-4721",
            "id": "pyup.io-54633",
            "more_info_path": "/vulnerabilities/CVE-2022-4721/54633",
            "specs": [
                ">=0,<2.5.5"
            ],
            "v": ">=0,<2.5.5"
        },
        {
            "advisory": "rdiffweb prior to 2.5.5 has no rate limit on the \"resend email feature\" while enable or disable 2FA from `/prefs/mfa` endpoint .",
            "cve": "CVE-2022-4723",
            "id": "pyup.io-54631",
            "more_info_path": "/vulnerabilities/CVE-2022-4723/54631",
            "specs": [
                ">=0,<2.5.5"
            ],
            "v": ">=0,<2.5.5"
        },
        {
            "advisory": "Business Logic Errors in GitHub repository ikus060/rdiffweb prior to 2.5.5.",
            "cve": "CVE-2022-4719",
            "id": "pyup.io-54635",
            "more_info_path": "/vulnerabilities/CVE-2022-4719/54635",
            "specs": [
                ">=0,<2.5.5"
            ],
            "v": ">=0,<2.5.5"
        },
        {
            "advisory": "Affected versions of the rdiffweb package are vulnerable to Cross-Site Request Forgery (CSRF) due to missing CSRF validation on the user notification settings handler. In rdiffweb/controller/pref_notification.py, the render_prefs_panel method processes the action=set_notification_info operation without enforcing a CSRF token and\u2014before the fix\u2014would accept state-changing requests over GET to /prefs/notification, allowing cross-origin requests to toggle notification preferences.",
            "cve": "CVE-2022-3233",
            "id": "pyup.io-54552",
            "more_info_path": "/vulnerabilities/CVE-2022-3233/54552",
            "specs": [
                ">=0.9.2.dev1,<2.4.6"
            ],
            "v": ">=0.9.2.dev1,<2.4.6"
        }
    ],
    "rdmo": [
        {
            "advisory": "Rdmo 1.6 replaces package csv by defusedcsv to prevent csv injection vulnerabilities.",
            "cve": "PVE-2021-42956",
            "id": "pyup.io-42956",
            "more_info_path": "/vulnerabilities/PVE-2021-42956/42956",
            "specs": [
                "<1.6"
            ],
            "v": "<1.6"
        }
    ],
    "rdquests": [
        {
            "advisory": "Rdquests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52888",
            "id": "pyup.io-52888",
            "more_info_path": "/vulnerabilities/PVE-2023-52888/52888",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "rdsai-cli": [
        {
            "advisory": "Affected versions of the rdsai-cli package are potentially vulnerable to insecure storage of sensitive information due to local credential persistence in a user-readable configuration file.",
            "cve": "PVE-2025-82901",
            "id": "pyup.io-82901",
            "more_info_path": "/vulnerabilities/PVE-2025-82901/82901",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "reacnetgenerator": [
        {
            "advisory": "Reacnetgenerator 1.4.59 updates its NPM dependency 'lodash' to include a security fix.",
            "cve": "CVE-2018-3721",
            "id": "pyup.io-51859",
            "more_info_path": "/vulnerabilities/CVE-2018-3721/51859",
            "specs": [
                "<1.4.59"
            ],
            "v": "<1.4.59"
        }
    ],
    "reactpy-django": [
        {
            "advisory": "Reactpy-django 0.0.2 includes a critical update that addresses a previously identified potential directory traversal vulnerability in the IDOM web modules URL.\r\nhttps://github.com/reactive-python/reactpy-django/compare/0.0.1...0.0.2",
            "cve": "PVE-2024-63677",
            "id": "pyup.io-63677",
            "more_info_path": "/vulnerabilities/PVE-2024-63677/63677",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        }
    ],
    "readalongs": [
        {
            "advisory": "Readalongs 1.0.20230224 includes fixes for XML external entity expansion vulnerabilities.\r\nhttps://github.com/ReadAlongs/Studio/commit/d0c57f3b771305e9ff181192a7019ba9a1ae07c2",
            "cve": "PVE-2023-53464",
            "id": "pyup.io-53464",
            "more_info_path": "/vulnerabilities/PVE-2023-53464/53464",
            "specs": [
                "<1.0.20230224"
            ],
            "v": "<1.0.20230224"
        }
    ],
    "readmeai": [
        {
            "advisory": "Readmeai 0.1.2 includes a security fix: removing the subprocess module. In the original implementation, if the desired executable path is not fully qualified relative to the filesystem root then this may present a potential security risk.\r\nhttps://github.com/eli64s/readme-ai/pull/53",
            "cve": "PVE-2023-61425",
            "id": "pyup.io-61425",
            "more_info_path": "/vulnerabilities/PVE-2023-61425/61425",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        },
        {
            "advisory": "Readmeai 0.3.16 updates its dependency 'gitpython' to v3.1.35 to include a security fix.",
            "cve": "CVE-2023-40590",
            "id": "pyup.io-61146",
            "more_info_path": "/vulnerabilities/CVE-2023-40590/61146",
            "specs": [
                "<0.3.16"
            ],
            "v": "<0.3.16"
        },
        {
            "advisory": "Readmeai 0.3.17 updates its dependency 'gitpython' to v3.1.36 to include a security fix.",
            "cve": "CVE-2023-41040",
            "id": "pyup.io-61297",
            "more_info_path": "/vulnerabilities/CVE-2023-41040/61297",
            "specs": [
                "<0.3.17"
            ],
            "v": "<0.3.17"
        }
    ],
    "readsettings": [
        {
            "advisory": "Readsettings 3.3.1 replaces `yaml.load` with the more secure, `yaml.safe_load`.",
            "cve": "PVE-2021-37027",
            "id": "pyup.io-37027",
            "more_info_path": "/vulnerabilities/PVE-2021-37027/37027",
            "specs": [
                "<3.3.1"
            ],
            "v": "<3.3.1"
        }
    ],
    "readthedocs-sphinx-search": [
        {
            "advisory": "Versions of readthedocs-sphinx-search extension are exposed to Cross-site Scripting (XSS) attacks, which allow attackers to insert arbitrary HTML or script commands into search results by exploiting documents from untrusted sources. This vulnerability could enable execution of unauthorized scripts or altering displayed content to the user.",
            "cve": "PVE-2024-99890",
            "id": "pyup.io-65530",
            "more_info_path": "/vulnerabilities/PVE-2024-99890/65530",
            "specs": [
                ">=0,<0.3.2"
            ],
            "v": ">=0,<0.3.2"
        }
    ],
    "readwrite": [
        {
            "advisory": "Readwrite 0.3.5 fixes a race condition where the global registry could have been `add_default()` twice.\r\nhttps://github.com/crunchdao/readwrite/commit/c9d688d3cd82c4fb64ce889c93a7b71bf3a12f89",
            "cve": "PVE-2023-63019",
            "id": "pyup.io-63019",
            "more_info_path": "/vulnerabilities/PVE-2023-63019/63019",
            "specs": [
                "<0.3.5"
            ],
            "v": "<0.3.5"
        }
    ],
    "realcugan-ncnn-vulkan-python": [
        {
            "advisory": "Realcugan-ncnn-vulkan-python 1.0.2 and prior releases ship with a version of C library 'libwebp' which is affected by a high risk vulnerability.\r\nhttps://inspector.pypi.io/project/realcugan-ncnn-vulkan-python/1.0.2/packages/64/8f/a97b3fac5e2123e4652a122f1df50846e4721056964003890edc20f24fbf/realcugan-ncnn-vulkan-python-1.0.2.tar.gz/realcugan-ncnn-vulkan-python-1.0.2/realcugan_ncnn_vulkan_python/realcugan-ncnn-vulkan/src/libwebp/ChangeLog",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62306",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62306",
            "specs": [
                "<=1.0.2"
            ],
            "v": "<=1.0.2"
        }
    ],
    "reallysimpledb": [
        {
            "advisory": "Reallysimpledb 1.2 fixes possible SQL injection vector through string-based query construction.\r\nhttps://github.com/truethari/ReallySimpleDB/commit/918cba5fcea7ca5a95647e3d47f744bb9dfc3704",
            "cve": "PVE-2022-45489",
            "id": "pyup.io-45489",
            "more_info_path": "/vulnerabilities/PVE-2022-45489/45489",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        }
    ],
    "realsr-ncnn-vulkan-python": [
        {
            "advisory": "Realsr-ncnn-vulkan-python 1.0.2 throughout 1.0.6 ship with a version of C library 'libwebp' which is affected by a high risk vulnerability.\r\nhttps://inspector.pypi.io/project/realsr-ncnn-vulkan-python/1.0.6/packages/75/17/03e75d9498a43e9770a3043cc8b587e868bf6d4f2a60fda3305ffac8b2b5/realsr-ncnn-vulkan-python-1.0.6.tar.gz/realsr-ncnn-vulkan-python-1.0.6/realsr_ncnn_vulkan_python/realsr-ncnn-vulkan/src/libwebp/ChangeLog",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62303",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62303",
            "specs": [
                ">1.0.1,<=1.0.6"
            ],
            "v": ">1.0.1,<=1.0.6"
        }
    ],
    "reana-server": [
        {
            "advisory": "Reana-server 0.6.0 improves security by allowing requests only with 'REANA_URL' in the host header, avoiding host header injection attacks.",
            "cve": "PVE-2022-45384",
            "id": "pyup.io-45384",
            "more_info_path": "/vulnerabilities/PVE-2022-45384/45384",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "reauests": [
        {
            "advisory": "Reauests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52887",
            "id": "pyup.io-52887",
            "more_info_path": "/vulnerabilities/PVE-2023-52887/52887",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "recline": [
        {
            "advisory": "Recline 2022.5 updates its dependency 'urllib3' to v1.26.9 to include security fixes.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-58793",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/58793",
            "specs": [
                "<2022.5"
            ],
            "v": "<2022.5"
        },
        {
            "advisory": "Recline 2022.5 updates its dependency 'urllib3' to v1.26.9 to include security fixes.",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-58794",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/58794",
            "specs": [
                "<2022.5"
            ],
            "v": "<2022.5"
        },
        {
            "advisory": "Recline 2022.5 updates its dependency 'urllib3' to v1.26.9 to include security fixes.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-58795",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/58795",
            "specs": [
                "<2022.5"
            ],
            "v": "<2022.5"
        },
        {
            "advisory": "Recline 2022.5 updates its dependency 'urllib3' to v1.26.9 to include security fixes.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-58796",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/58796",
            "specs": [
                "<2022.5"
            ],
            "v": "<2022.5"
        },
        {
            "advisory": "Recline 2023.2 updates its dependency 'certifi' to include a security fix.",
            "cve": "CVE-2022-23491",
            "id": "pyup.io-58792",
            "more_info_path": "/vulnerabilities/CVE-2022-23491/58792",
            "specs": [
                "<2023.2"
            ],
            "v": "<2023.2"
        },
        {
            "advisory": "Recline 2023.5 updates its dependency 'requests' to include a security fix.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-58774",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/58774",
            "specs": [
                "<2023.5"
            ],
            "v": "<2023.5"
        }
    ],
    "recommender-xblock": [
        {
            "advisory": "Recommender before 1.3.1 allows XSS.",
            "cve": "CVE-2018-20858",
            "id": "pyup.io-54022",
            "more_info_path": "/vulnerabilities/CVE-2018-20858/54022",
            "specs": [
                ">=0,<1.3.1"
            ],
            "v": ">=0,<1.3.1"
        }
    ],
    "records-mover": [
        {
            "advisory": "Affected versions of the records-mover package are vulnerable to SQL Injection due to improper neutralization of attacker-influenced input in SQL construction. The Table Object Handler component contains an unknown function that builds downstream SQL using values derived from a Table object without sufficient sanitization or parameterization, enabling injected SQL to be interpreted by the database engine.",
            "cve": "CVE-2023-7333",
            "id": "pyup.io-84321",
            "more_info_path": "/vulnerabilities/CVE-2023-7333/84321",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        }
    ],
    "recurly": [
        {
            "advisory": "The Recurly Client Python Library before 2.0.5, 2.1.16, 2.2.22, 2.3.1, 2.4.5, 2.5.1, 2.6.2 is vulnerable to a Server-Side Request Forgery vulnerability in the \"Resource.get\" method that could result in compromise of API keys or other critical resources.",
            "cve": "CVE-2017-0906",
            "id": "pyup.io-35697",
            "more_info_path": "/vulnerabilities/CVE-2017-0906/35697",
            "specs": [
                "<=2.6.2"
            ],
            "v": "<=2.6.2"
        }
    ],
    "red-dashboard": [
        {
            "advisory": "Red Discord Bot Dashboard is an easy-to-use interactive web dashboard to control your Redbot. In Red Discord Bot before version 0.1.7a an RCE exploit has been discovered. This exploit allows Discord users with specially crafted Server names and Usernames/Nicknames to inject code into the webserver front-end code. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information. This high severity exploit has been fixed on version 0.1.7a. There are no workarounds, bot owners must upgrade their relevant packages (Dashboard module and Dashboard webserver) in order to patch this issue.",
            "cve": "CVE-2020-26249",
            "id": "pyup.io-42287",
            "more_info_path": "/vulnerabilities/CVE-2020-26249/42287",
            "specs": [
                "<0.1.7a0"
            ],
            "v": "<0.1.7a0"
        }
    ],
    "red-discordbot": [
        {
            "advisory": "Red-discordbot 3.0.0rc3 addresses a race condition issue, ensuring stability by preventing changes to dictionaries during serialization, thus safeguarding against data corruption or errors during this process.",
            "cve": "PVE-2024-67132",
            "id": "pyup.io-67132",
            "more_info_path": "/vulnerabilities/PVE-2024-67132/67132",
            "specs": [
                "<3.0.0rc3"
            ],
            "v": "<3.0.0rc3"
        },
        {
            "advisory": "Red-discordbot 3.3.9 updates ensure that neither global nor server rules restrict guild owners from using commands to modify server rules. While bot owners retain the ability to disable any command in the Permissions cog using [p]command disable, this change prioritizes access for guild owners, maintaining command functionality and administrative control.",
            "cve": "PVE-2024-67130",
            "id": "pyup.io-67130",
            "more_info_path": "/vulnerabilities/PVE-2024-67130/67130",
            "specs": [
                "<3.3.9"
            ],
            "v": "<3.3.9"
        },
        {
            "advisory": "### Impact\nA RCE exploit has been discovered in the Trivia module: this exploit allows Discord users with specifically crafted usernames to inject code into the Trivia module's leaderboard command. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.\n\n### Patches\nThis critical exploit has been fixed on version 3.3.11.\n\n### Workarounds\nUnloading the Trivia module with ``unload trivia`` can render this exploit not accessible. We still highly recommend updating to 3.3.11 to completely patch this issue.\n\n### References\nhttps://github.com/Cog-Creators/Red-DiscordBot/pull/4175\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-DiscordBot](https://github.com/Cog-Creators/Red-DiscordBot)\n* Over on our [Discord server](https://discord.gg/red)",
            "cve": "CVE-2020-15140",
            "id": "pyup.io-54207",
            "more_info_path": "/vulnerabilities/CVE-2020-15140/54207",
            "specs": [
                ">=0,<3.3.11"
            ],
            "v": ">=0,<3.3.11"
        },
        {
            "advisory": "### Impact\nA RCE exploit has been discovered in the Streams module: this exploit allows Discord users with specifically crafted \"going live\" messages to inject code into the Streams module's going live message. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.\n\n### Patches\nThis critical exploit has been fixed on version ``3.3.12`` & ``3.4``.\n\n### Workarounds\nUnloading the Streams module with ``unload streams`` can render this exploit not accessible. We still highly recommend updating to ``3.3.12`` or ``3.4`` to completely patch this issue.\n\n### References\n* https://github.com/Cog-Creators/Red-DiscordBot/pull/4183\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-DiscordBot](https://github.com/Cog-Creators/Red-DiscordBot)\n* Over on our [Discord server](https://discord.gg/red)",
            "cve": "CVE-2020-15147",
            "id": "pyup.io-54376",
            "more_info_path": "/vulnerabilities/CVE-2020-15147/54376",
            "specs": [
                ">=0,<3.3.12"
            ],
            "v": ">=0,<3.3.12"
        },
        {
            "advisory": "Red Discord Bot before version 3.4.1 has an unauthorized privilege escalation exploit in the Mod module. This exploit allows Discord users with a high privilege level within the guild to bypass hierarchy checks when the application is in a specific condition that is beyond that user's control. By abusing this exploit, it is possible to perform destructive actions within the guild the user has high privileges in. This exploit has been fixed in version 3.4.1. As a workaround, unloading the Mod module with unload mod or, disabling the massban command with command disable global massban can render this exploit not accessible. We still highly recommend updating to 3.4.1 to completely patch this issue.",
            "cve": "CVE-2020-15278",
            "id": "pyup.io-54296",
            "more_info_path": "/vulnerabilities/CVE-2020-15278/54296",
            "specs": [
                ">=0,<3.4.1"
            ],
            "v": ">=0,<3.4.1"
        },
        {
            "advisory": "A bug in Red's Core API affects the @commands.can_manage_channel() command permission check. This bug may authorize a user to execute a command even if they do not have the permissions to manage a channel, if additional permission controls are not in place. Core commands and core cogs are unaffected by this issue. At the time of this advisory, the maintainers are not aware of any public 3rd-party cogs utilizing this API. The following command permission checks are unaffected: @commands.mod_or_can_manage_channel(), @commands.admin_or_can_manage_channel(), and @commands.guildowner_or_can_manage_channel().",
            "cve": "CVE-2024-39905",
            "id": "pyup.io-72135",
            "more_info_path": "/vulnerabilities/CVE-2024-39905/72135",
            "specs": [
                ">=3.5.0,<3.5.10"
            ],
            "v": ">=3.5.0,<3.5.10"
        }
    ],
    "reddit-experiments": [
        {
            "advisory": "Reddit-experiments version 1.9.0 updates its gevent dependency from 21.12.0 to 23.9.0 to address the security vulnerability identified as CVE-2023-41419.",
            "cve": "CVE-2023-41419",
            "id": "pyup.io-71491",
            "more_info_path": "/vulnerabilities/CVE-2023-41419/71491",
            "specs": [
                "<1.9.0"
            ],
            "v": "<1.9.0"
        }
    ],
    "redis": [
        {
            "advisory": "An Off-by-one flaw was found in Redis. Affected versions leave a connection open after canceling an async Redis command at an inopportune time, and can send response data to the client of an unrelated request in an off-by-one manner. \r\nNOTE: this CVE Record was initially created in response to reports about ChatGPT, however, please see CVE-2023-28859 about addressing data leakage across AsyncIO connections in general.",
            "cve": "CVE-2023-28858",
            "id": "pyup.io-53868",
            "more_info_path": "/vulnerabilities/CVE-2023-28858/53868",
            "specs": [
                ">=4.5.0,<4.5.3",
                ">=4.4.0rc1,<4.4.3",
                ">=4.2.0rc1,<4.3.6"
            ],
            "v": ">=4.5.0,<4.5.3,>=4.4.0rc1,<4.4.3,>=4.2.0rc1,<4.3.6"
        },
        {
            "advisory": "Redis 4.4.4 and 4.5.4 include a fix for CVE-2023-28859: Redis-py before 4.4.4 and 4.5.x before 4.5.4 leaves a connection open after canceling an async Redis command at an inopportune time, and can send response data to the client of an unrelated request. (This could, for example, happen for a non-pipeline operation.) NOTE: the solutions for CVE-2023-28859 address data leakage across AsyncIO connections in general.\r\nhttps://github.com/advisories/GHSA-8fww-64cx-x8p5",
            "cve": "CVE-2023-28859",
            "id": "pyup.io-53869",
            "more_info_path": "/vulnerabilities/CVE-2023-28859/53869",
            "specs": [
                ">=4.5.0,<4.5.4",
                ">=4.2.0rc1,<4.4.4"
            ],
            "v": ">=4.5.0,<4.5.4,>=4.2.0rc1,<4.4.4"
        }
    ],
    "redis-dict": [
        {
            "advisory": "Redis-dict 2.0.2 updates its dependency 'redis' to v4.5.4 to include a security fix.",
            "cve": "CVE-2023-28859",
            "id": "pyup.io-54797",
            "more_info_path": "/vulnerabilities/CVE-2023-28859/54797",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        },
        {
            "advisory": "Redis-dict 2.3.0 updates its dependency on Cryptography, moving to 41.0.4, in response to the security vulnerability identified as CVE-2023-4807.\r\nhttps://github.com/Attumm/redis-dict/commit/df6f2b89d60ea5c59e564ebf2209e1f166fb1892",
            "cve": "CVE-2023-4807",
            "id": "pyup.io-64093",
            "more_info_path": "/vulnerabilities/CVE-2023-4807/64093",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        }
    ],
    "redisgraph": [
        {
            "advisory": "RedisGraph 2.x through 2.2.11 has a NULL Pointer Dereference that leads to a server crash because it mishandles an unquoted string, such as an alias that has not yet been introduced.",
            "cve": "CVE-2020-35668",
            "id": "pyup.io-70592",
            "more_info_path": "/vulnerabilities/CVE-2020-35668/70592",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Buffer Overflow vulnerability in Redis RedisGraph v.2.x through v.2.12.8 and fixed in v.2.12.9 allows an attacker to execute arbitrary code via the code logic after valid authentication.",
            "cve": "CVE-2023-47004",
            "id": "pyup.io-65257",
            "more_info_path": "/vulnerabilities/CVE-2023-47004/65257",
            "specs": [
                ">=2.0.0,<2.12.9"
            ],
            "v": ">=2.0.0,<2.12.9"
        }
    ],
    "redisvl": [
        {
            "advisory": "Redisvl updates cryptography from 43.0.3 to 44.0.1 due to the CVE-2024-12797.",
            "cve": "CVE-2024-12797",
            "id": "pyup.io-75563",
            "more_info_path": "/vulnerabilities/CVE-2024-12797/75563",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "rediswrapper": [
        {
            "advisory": "Uncontrolled deserialization of a pickled object in models.py in Frost Ming rediswrapper (aka Redis Wrapper) before 0.3.0 allows attackers to execute arbitrary scripts.",
            "cve": "CVE-2019-17206",
            "id": "pyup.io-42266",
            "more_info_path": "/vulnerabilities/CVE-2019-17206/42266",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "redmine-mcp-server": [
        {
            "advisory": "Affected versions of the redmine-mcp-server package are vulnerable to Path Traversal due to improper path normalization and missing directory-boundary enforcement in the attachment download logic. In src/redmine_mcp_server/file_manager.py, paths derived from user-influenced attachment names were joined to the ATTACHMENTS_DIR and later exposed by the /files/{file_id} HTTP handler without canonical resolution or verification that the final path remained inside the configured storage directory.",
            "cve": "PVE-2025-79812",
            "id": "pyup.io-79812",
            "more_info_path": "/vulnerabilities/PVE-2025-79812/79812",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "redshift-connector": [
        {
            "advisory": "When the Amazon Redshift Python Connector is configured with the BrowserAzureOAuth2CredentialsProvider plugin, the driver skips the SSL certificate validation step for the Identity Provider. An insecure connection could allow an actor to intercept the token exchange process and retrieve an access token. This issue has been addressed in driver version 2.1.7. Users should upgrade to address this issue and ensure any forked or derivative code is patched to incorporate the new fixes.",
            "cve": "CVE-2025-5279",
            "id": "pyup.io-77703",
            "more_info_path": "/vulnerabilities/CVE-2025-5279/77703",
            "specs": [
                ">=2.0.872,<=2.1.6"
            ],
            "v": ">=2.0.872,<=2.1.6"
        },
        {
            "advisory": "A SQL injection in the Amazon Redshift Python Connector in version 2.1.4 allows a user to gain escalated privileges via schema injection in the getschemas, gettables, or get_columns Metadata APIs. Users should upgrade to driver version 2.1.5 or revert to driver version 2.1.3.",
            "cve": "CVE-2024-12745",
            "id": "pyup.io-76376",
            "more_info_path": "/vulnerabilities/CVE-2024-12745/76376",
            "specs": [
                ">=2.1.4,<2.1.5"
            ],
            "v": ">=2.1.4,<2.1.5"
        }
    ],
    "reduests": [
        {
            "advisory": "Reduests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52891",
            "id": "pyup.io-52891",
            "more_info_path": "/vulnerabilities/PVE-2023-52891/52891",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "redvox": [
        {
            "advisory": "Redvox updates its pyarrow dependency from version 11.0.0 to 14.0.1 to address a security vulnerability identified as CVE-2023-47248.",
            "cve": "CVE-2023-47248",
            "id": "pyup.io-72116",
            "more_info_path": "/vulnerabilities/CVE-2023-47248/72116",
            "specs": [
                "<3.8.1"
            ],
            "v": "<3.8.1"
        }
    ],
    "reeuests": [
        {
            "advisory": "Reeuests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52892",
            "id": "pyup.io-52892",
            "more_info_path": "/vulnerabilities/PVE-2023-52892/52892",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "refitt": [
        {
            "advisory": "Refitt 0.16.5 updates its dependency 'click' to v8.0.1 to include a security fix.",
            "cve": "PVE-2022-47833",
            "id": "pyup.io-40815",
            "more_info_path": "/vulnerabilities/PVE-2022-47833/40815",
            "specs": [
                "<0.16.5"
            ],
            "v": "<0.16.5"
        },
        {
            "advisory": "Refitt 0.16.5 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-49112",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/49112",
            "specs": [
                "<0.16.5"
            ],
            "v": "<0.16.5"
        }
    ],
    "reflex": [
        {
            "advisory": "Reflex 0.1.13 includes a fix for a Race Condition vulnerability in the websocket.\r\nhttps://github.com/reflex-dev/reflex/pull/261",
            "cve": "PVE-2023-59560",
            "id": "pyup.io-59874",
            "more_info_path": "/vulnerabilities/PVE-2023-59560/59874",
            "specs": [
                "<0.1.13"
            ],
            "v": "<0.1.13"
        },
        {
            "advisory": "Reflex 0.1.33 updates its dependency 'fastapi' to version '0.96.0' to include a fix for an Improper Input Validation vulnerability.\r\nhttps://github.com/reflex-dev/reflex/pull/1172",
            "cve": "CVE-2023-29159",
            "id": "pyup.io-59875",
            "more_info_path": "/vulnerabilities/CVE-2023-29159/59875",
            "specs": [
                "<0.1.33"
            ],
            "v": "<0.1.33"
        },
        {
            "advisory": "Reflex 0.5.0 updates its gunicorn dependency from 21.2.0 to 22.0.0 in response to CVE-2024-1135.",
            "cve": "CVE-2024-1135",
            "id": "pyup.io-70983",
            "more_info_path": "/vulnerabilities/CVE-2024-1135/70983",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        },
        {
            "advisory": "Affected versions of the reflex package are vulnerable to Open Redirect due to assigning the user-controlled redirect_to query parameter directly to a client-side link that is automatically clicked on the /auth-codespace page. In reflex/utils/codespaces.py, the /auth-codespace route (registered when a GitHub Codespaces environment is detected) sets a.href from redirect_to without origin/scheme validation or a whitelist and immediately triggers navigation, providing no server-side path enforcement.",
            "cve": "CVE-2025-62379",
            "id": "pyup.io-80465",
            "more_info_path": "/vulnerabilities/CVE-2025-62379/80465",
            "specs": [
                ">=0.5.4,<=0.8.14"
            ],
            "v": ">=0.5.4,<=0.8.14"
        }
    ],
    "refuel-autolabel": [
        {
            "advisory": "The Refuel Autolabel library affected versions contain an arbitrary code execution vulnerability in its classification task handler. When processing CSV files for these tasks, the library uses an unsafe eval() function to interpret values enclosed in square brackets. Attackers can exploit this vulnerability by crafting malicious CSV files containing Python code within these brackets. Upon processing such a file, the library will execute the embedded code, potentially compromising the system. Users should exercise extreme caution when handling external CSV files and avoid using this feature until the developers patch the vulnerability.",
            "cve": "CVE-2024-27320",
            "id": "pyup.io-73325",
            "more_info_path": "/vulnerabilities/CVE-2024-27320/73325",
            "specs": [
                ">=0.0.8"
            ],
            "v": ">=0.0.8"
        },
        {
            "advisory": "The Refuel Autolabel library affected versions contain a critical arbitrary code execution vulnerability in its multilabel classification task handler. When processing CSV files for these tasks, the library uses an unsafe eval() function to interpret the contents of square bracket-enclosed values. Attackers can exploit this vulnerability by crafting malicious CSV files containing Python code within these brackets. Upon processing such a file, the library will execute the embedded code, potentially compromising the system. Users should exercise extreme caution when handling external CSV files and avoid using this feature until the developers patch the vulnerability.",
            "cve": "CVE-2024-27321",
            "id": "pyup.io-73324",
            "more_info_path": "/vulnerabilities/CVE-2024-27321/73324",
            "specs": [
                ">=0.0.8"
            ],
            "v": ">=0.0.8"
        }
    ],
    "regex": [
        {
            "advisory": "Regex 2018.11.22 includes a fix for a Catastrophic Backtracking vulnerability.\r\nhttps://github.com/mrabarnett/mrab-regex/issues/304",
            "cve": "PVE-2023-60277",
            "id": "pyup.io-60277",
            "more_info_path": "/vulnerabilities/PVE-2023-60277/60277",
            "specs": [
                "<2018.11.22"
            ],
            "v": "<2018.11.22"
        },
        {
            "advisory": "Affected versions of this package are potentially vulnerable to Regular Expression Denial of Service (ReDoS) due to catastrophic backtracking in the V1 engine when processing patterns that combine full\u2011casefolding with the [\\s\\S]* quantifier. The engine\u2019s AnyAll node fails to prevent nested quantifier backtracking, leading to infinite loops and CPU exhaustion.",
            "cve": "PVE-2025-78558",
            "id": "pyup.io-78558",
            "more_info_path": "/vulnerabilities/PVE-2025-78558/78558",
            "specs": [
                "<2025.2.10"
            ],
            "v": "<2025.2.10"
        }
    ],
    "regex4ocr": [
        {
            "advisory": "Regex4ocr version 1.0.2 updates its dependency \"Pyyaml\" to v4.2b1 to include security fixes.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-42018",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/42018",
            "specs": [
                "<1.0.2"
            ],
            "v": "<1.0.2"
        }
    ],
    "rejected": [
        {
            "advisory": "Rejected 3.20.7 updates its dependency 'pyyaml' to v5.3.1 to include security fixes.\r\nhttps://github.com/gmr/rejected/commit/3d0d600f2fec041d84f0255af51c8b46ea98815b",
            "cve": "CVE-2019-20477",
            "id": "pyup.io-44584",
            "more_info_path": "/vulnerabilities/CVE-2019-20477/44584",
            "specs": [
                "<3.20.7"
            ],
            "v": "<3.20.7"
        },
        {
            "advisory": "Rejected 3.20.7 updates its dependency 'pyyaml' to v5.3.1 to include security fixes.\r\nhttps://github.com/gmr/rejected/commit/3d0d600f2fec041d84f0255af51c8b46ea98815b",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-42627",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/42627",
            "specs": [
                "<3.20.7"
            ],
            "v": "<3.20.7"
        }
    ],
    "rekall": [
        {
            "advisory": "Rekall 1.7.2rc1 and prior uses a version of 'pycryptodome' with known vulnerabilities.",
            "cve": "CVE-2018-15560",
            "id": "pyup.io-48149",
            "more_info_path": "/vulnerabilities/CVE-2018-15560/48149",
            "specs": [
                "<=1.7.2rc1"
            ],
            "v": "<=1.7.2rc1"
        },
        {
            "advisory": "Rekall 1.7.2rc1 and prior uses a version of 'requests' with known vulnerabilities.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-47328",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/47328",
            "specs": [
                "<=1.7.2rc1"
            ],
            "v": "<=1.7.2rc1"
        },
        {
            "advisory": "Rekall 1.7.2rc1 and prior uses a version of 'httplib2' with known vulnerabilities.",
            "cve": "CVE-2020-11078",
            "id": "pyup.io-48148",
            "more_info_path": "/vulnerabilities/CVE-2020-11078/48148",
            "specs": [
                "<=1.7.2rc1"
            ],
            "v": "<=1.7.2rc1"
        },
        {
            "advisory": "Rekall 1.7.2rc1 and prior uses a version of 'httplib2' with known vulnerabilities.",
            "cve": "CVE-2021-21240",
            "id": "pyup.io-48147",
            "more_info_path": "/vulnerabilities/CVE-2021-21240/48147",
            "specs": [
                "<=1.7.2rc1"
            ],
            "v": "<=1.7.2rc1"
        }
    ],
    "relstorage": [
        {
            "advisory": "Relstorage 3.0a11 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/zodb/relstorage/issues/325\r\nhttps://github.com/zodb/relstorage/pull/348",
            "cve": "PVE-2023-59580",
            "id": "pyup.io-59580",
            "more_info_path": "/vulnerabilities/PVE-2023-59580/59580",
            "specs": [
                "<3.0a11"
            ],
            "v": "<3.0a11"
        },
        {
            "advisory": "Relstorage 3.0a3 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/zodb/relstorage/issues/219\r\nhttps://github.com/zodb/relstorage/pull/257",
            "cve": "PVE-2023-59582",
            "id": "pyup.io-59582",
            "more_info_path": "/vulnerabilities/PVE-2023-59582/59582",
            "specs": [
                "<3.0a3"
            ],
            "v": "<3.0a3"
        },
        {
            "advisory": "Relstorage 3.0a7 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/zodb/relstorage/issues/283\r\nhttps://github.com/zodb/relstorage/pull/295",
            "cve": "PVE-2023-59581",
            "id": "pyup.io-59581",
            "more_info_path": "/vulnerabilities/PVE-2023-59581/59581",
            "specs": [
                "<3.0a7"
            ],
            "v": "<3.0a7"
        }
    ],
    "remarshal": [
        {
            "advisory": "Remarshal 0.17.1 prevents a billion laughs attack carried out with YAML anchors.\r\nhttps://github.com/remarshal-project/remarshal/commit/fd6ac799a02f533c3fc243b49cdd6d21aa7ee494",
            "cve": "PVE-2023-60980",
            "id": "pyup.io-60980",
            "more_info_path": "/vulnerabilities/PVE-2023-60980/60980",
            "specs": [
                "<0.17.1"
            ],
            "v": "<0.17.1"
        },
        {
            "advisory": "Remarshal prior to v0.17.1 expands YAML alias nodes unlimitedly, hence Remarshal is vulnerable to Billion Laughs Attack. Processing untrusted YAML files may cause a denial-of-service (DoS) condition.",
            "cve": "CVE-2023-47163",
            "id": "pyup.io-65187",
            "more_info_path": "/vulnerabilities/CVE-2023-47163/65187",
            "specs": [
                ">=0,<0.17.1"
            ],
            "v": ">=0,<0.17.1"
        }
    ],
    "rembg": [
        {
            "advisory": "Rembg is a tool to remove images background. In Rembg 2.0.57 and earlier, the CORS middleware is set up incorrectly. All origins are reflected, which allows any website to send cross-site requests to the rembg server and thus query any API. Even if authentication were to be enabled, allow_credentials is set to True, which would allow any website to send authenticated cross-site requests.",
            "cve": "CVE-2025-25302",
            "id": "pyup.io-76310",
            "more_info_path": "/vulnerabilities/CVE-2025-25302/76310",
            "specs": [
                "<2.0.57"
            ],
            "v": "<2.0.57"
        },
        {
            "advisory": "Rembg is a tool to remove images background. In Rembg 2.0.57 and earlier, the /api/remove endpoint takes a URL query parameter that allows an image to be fetched, processed and returned. An attacker may be able to query this endpoint to view pictures hosted on the internal network of the rembg server. This issue may lead to Information Disclosure.",
            "cve": "CVE-2025-25301",
            "id": "pyup.io-76311",
            "more_info_path": "/vulnerabilities/CVE-2025-25301/76311",
            "specs": [
                "<2.0.57"
            ],
            "v": "<2.0.57"
        }
    ],
    "renate": [
        {
            "advisory": "Renate 0.5.1 upgrades its Pillow dependency, moving from version range >=9.0, <10.1.1 to a new range of >=10.2, <10.2.1. This update addresses the security vulnerability identified in CVE-2023-44271.",
            "cve": "CVE-2023-44271",
            "id": "pyup.io-64452",
            "more_info_path": "/vulnerabilities/CVE-2023-44271/64452",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Renate 0.5.2 updates its sagemaker dependency to sagemaker>=2.218.0, <2.224.3 to address a security vulnerability identified as CVE-2024-34072.",
            "cve": "CVE-2024-34072",
            "id": "pyup.io-71942",
            "more_info_path": "/vulnerabilities/CVE-2024-34072/71942",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        },
        {
            "advisory": "Renate 0.5.2 updates its requests dependency to requests>=2.32.0, <2.32.4 to address security vulnerabilities, including CVE-2023-32681.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-71971",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/71971",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        },
        {
            "advisory": "Renate 0.5.2 updates its Pillow dependency to Pillow>=10.3.0, <10.4.1 to address security vulnerabilities, including CVE-2024-28219.",
            "cve": "CVE-2024-28219",
            "id": "pyup.io-71972",
            "more_info_path": "/vulnerabilities/CVE-2024-28219/71972",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        }
    ],
    "rencode": [
        {
            "advisory": "The rencode package through 1.0.6 for Python allows an infinite loop in typecode decoding (such as via ;\\x2f\\x7f), enabling a remote attack that consumes CPU and memory.\r\nhttps://seclists.org/fulldisclosure/2021/Sep/16",
            "cve": "CVE-2021-40839",
            "id": "pyup.io-41290",
            "more_info_path": "/vulnerabilities/CVE-2021-40839/41290",
            "specs": [
                "<=1.0.6"
            ],
            "v": "<=1.0.6"
        }
    ],
    "renderj2": [
        {
            "advisory": "Renderj2 version 1.1.1 includes a security patch for the function 'cmd' in 'renderj2/renderj2.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/mypaceshun/renderj2/commit/307fbb7d4225d77006170234d9285d2d78202833",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41382",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41382",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "rendertron": [
        {
            "advisory": "Rendertron 3.0.0 fixes a security issue with AppEngine deployments.",
            "cve": "PVE-2021-38571",
            "id": "pyup.io-38571",
            "more_info_path": "/vulnerabilities/PVE-2021-38571/38571",
            "specs": [
                "<3.0.0"
            ],
            "v": "<3.0.0"
        }
    ],
    "renku": [
        {
            "advisory": "Renku version 0.4.0 fixes CVE-2017-18342.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-38552",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/38552",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Renku 0.6.0 updates its Werkzeug dependency to version 0.15.5 from the previous 0.12, in response to the security vulnerability CVE-2019-14322.\r\nhttps://github.com/SwissDataScienceCenter/renku-python/pull/633/commits/d349d70939feff4e2797ac99b07f1cb633b37596",
            "cve": "CVE-2019-14322",
            "id": "pyup.io-64208",
            "more_info_path": "/vulnerabilities/CVE-2019-14322/64208",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Renku 0.6.0 updates its dependency 'werkzeug' to a version >=0.15.5 to include a security fix.",
            "cve": "CVE-2019-14806",
            "id": "pyup.io-37548",
            "more_info_path": "/vulnerabilities/CVE-2019-14806/37548",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Renku 1.0.6 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "PVE-2021-44525",
            "id": "pyup.io-45379",
            "more_info_path": "/vulnerabilities/PVE-2021-44525/45379",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Renku 1.0.6 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "PVE-2022-44524",
            "id": "pyup.io-45380",
            "more_info_path": "/vulnerabilities/PVE-2022-44524/45380",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Renku 1.0.6 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-24303",
            "id": "pyup.io-45112",
            "more_info_path": "/vulnerabilities/CVE-2022-24303/45112",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Renku 1.0.6 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-22817",
            "id": "pyup.io-45378",
            "more_info_path": "/vulnerabilities/CVE-2022-22817/45378",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Renku 1.0.6 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-22816",
            "id": "pyup.io-45381",
            "more_info_path": "/vulnerabilities/CVE-2022-22816/45381",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Renku 1.0.6 updates its dependency 'pillow' to v9.0.1 to include security fixes.",
            "cve": "CVE-2022-22815",
            "id": "pyup.io-45382",
            "more_info_path": "/vulnerabilities/CVE-2022-22815/45382",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Renku 1.11.0 resolves high severity XSS (Cross-Site Scripting) vulnerabilities that previously permitted the injection and execution of malicious scripts within the application's web interface.\r\nhttps://github.com/SwissDataScienceCenter/renku-python/pull/3234/commits/a47aedf7bd147c4999a91bcf7489ade3542b39ad",
            "cve": "PVE-2024-64209",
            "id": "pyup.io-64209",
            "more_info_path": "/vulnerabilities/PVE-2024-64209/64209",
            "specs": [
                "<1.11.0"
            ],
            "v": "<1.11.0"
        },
        {
            "advisory": "Renku 2.0.0 resolves high severity XSS (Cross-Site Scripting) vulnerabilities that previously permitted the injection and execution of malicious scripts within the application's web interface.\r\nhttps://github.com/SwissDataScienceCenter/renku-python/pull/3234/commits/a47aedf7bd147c4999a91bcf7489ade3542b39ad",
            "cve": "PVE-2024-64210",
            "id": "pyup.io-64210",
            "more_info_path": "/vulnerabilities/PVE-2024-64210/64210",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        }
    ],
    "rentry.py": [
        {
            "advisory": "Security Fix for Rentry.py 0.2.6 | CSRF token synchronization issue leading to request failures. When use_session=False, the CSRF token in the payload was being accessed before refresh, causing token mismatch between payload and cookies, resulting in 403 errors",
            "cve": "PVE-2025-75615",
            "id": "pyup.io-75615",
            "more_info_path": "/vulnerabilities/PVE-2025-75615/75615",
            "specs": [
                "<0.2.6"
            ],
            "v": "<0.2.6"
        }
    ],
    "repairwheel": [
        {
            "advisory": "Repairwheel 0.2.6 vendors 'auditwheel' from unreleased commit to include a fix for a ReDOS vulnerability.\r\nhttps://github.com/jvolkman/repairwheel/pull/17",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-61777",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/61777",
            "specs": [
                "<0.2.6"
            ],
            "v": "<0.2.6"
        }
    ],
    "replicate": [
        {
            "advisory": "Affected versions of this package are potentially vulnerable to Race Condition attacks. The StreamRedirector component fails to properly synchronize concurrent stream operations, leading to potential data corruption, output mixing between different model predictions, and information leakage in multi-user environments.",
            "cve": "PVE-2025-77595",
            "id": "pyup.io-77595",
            "more_info_path": "/vulnerabilities/PVE-2025-77595/77595",
            "specs": [
                "<0.9.12"
            ],
            "v": "<0.9.12"
        }
    ],
    "repobee": [
        {
            "advisory": "Repobee 0.4.0 adds a strict security policy to prevent malicious code from executing.",
            "cve": "PVE-2021-38523",
            "id": "pyup.io-38523",
            "more_info_path": "/vulnerabilities/PVE-2021-38523/38523",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Repobee 1.3.2 uses git pull instead of git clone. This is a security update.\r\nhttps://github.com/repobee/repobee/pull/176",
            "cve": "PVE-2021-38522",
            "id": "pyup.io-38522",
            "more_info_path": "/vulnerabilities/PVE-2021-38522/38522",
            "specs": [
                "<1.3.2"
            ],
            "v": "<1.3.2"
        },
        {
            "advisory": "Repobee 2.0.2 includes a fix that filters out secure token from `show-config` command output [92aa5cf08cc08d2647a9f22bb6ff120cd5a88360].",
            "cve": "PVE-2021-37383",
            "id": "pyup.io-37383",
            "more_info_path": "/vulnerabilities/PVE-2021-37383/37383",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        }
    ],
    "repobee-junit4": [
        {
            "advisory": "Repobee-junit4 version 0.4.0 adds a strict security policy to prevent malicious code from executing.\r\nhttps://github.com/repobee/repobee-junit4/commit/eaa14a6642eea7cb71d27d8003a8cc1de1ea6406",
            "cve": "PVE-2021-42041",
            "id": "pyup.io-42041",
            "more_info_path": "/vulnerabilities/PVE-2021-42041/42041",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "repomate-junit4": [
        {
            "advisory": "Repomate-junit4 version 0.4.0 adds a strict security policy to prevent malicious code from executing.\r\nhttps://github.com/repobee/repobee-junit4/commit/eaa14a6642eea7cb71d27d8003a8cc1de1ea6406",
            "cve": "PVE-2021-42032",
            "id": "pyup.io-42032",
            "more_info_path": "/vulnerabilities/PVE-2021-42032/42032",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "repomix": [
        {
            "advisory": "Repomix has upgraded the micromatch package from version 4.0.7 to 4.0.8. This update includes a critical security fix addressing CVE-2024-4067.",
            "cve": "CVE-2024-4067",
            "id": "pyup.io-74762",
            "more_info_path": "/vulnerabilities/CVE-2024-4067/74762",
            "specs": [
                "<0.1.29"
            ],
            "v": "<0.1.29"
        }
    ],
    "repopack": [
        {
            "advisory": "Repopack has updated `micromatch` from version 4.0.7 to 4.0.8, addressing a critical security vulnerability CVE-2024-4067.",
            "cve": "CVE-2024-4067",
            "id": "pyup.io-72816",
            "more_info_path": "/vulnerabilities/CVE-2024-4067/72816",
            "specs": [
                "<0.1.29"
            ],
            "v": "<0.1.29"
        }
    ],
    "reportlab": [
        {
            "advisory": "ReportLab 3.5.31 includes a fix for CVE-2019-19450: Paraparser in ReportLab before 3.5.31 allows remote code execution because start_unichar in paraparser.py evaluates untrusted user input in a unichar element in a crafted XML document with '=0,<3.5.55"
            ],
            "v": ">=0,<3.5.55"
        }
    ],
    "repoze-who": [
        {
            "advisory": "Repoze.who 2.0a4 fixes 'auth_tkt' plugin to add \"secure\" and \"HttpOnly\" to cookies when  configured with 'secure=True'. These attributes prevent the browser from sending cookies over insecure channels, which could expose to different attacks like XSS.",
            "cve": "PVE-2017-47623",
            "id": "pyup.io-47623",
            "more_info_path": "/vulnerabilities/PVE-2017-47623/47623",
            "specs": [
                "<2.0a4"
            ],
            "v": "<2.0a4"
        },
        {
            "advisory": "Repoze.who 2.0b1 includes a fix to prevent timing-based attacks against htpasswd.\r\nhttps://github.com/repoze/repoze.who/commit/f8ef8169680239824eb5fb11c7ce5a54938aed1c",
            "cve": "PVE-2017-47624",
            "id": "pyup.io-47624",
            "more_info_path": "/vulnerabilities/PVE-2017-47624/47624",
            "specs": [
                "<2.0b1"
            ],
            "v": "<2.0b1"
        }
    ],
    "reprozip": [
        {
            "advisory": "Reprozip 1.2 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.",
            "cve": "CVE-2007-4559",
            "id": "pyup.io-53007",
            "more_info_path": "/vulnerabilities/CVE-2007-4559/53007",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        }
    ],
    "reqhests": [
        {
            "advisory": "Reqhests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52893",
            "id": "pyup.io-52893",
            "more_info_path": "/vulnerabilities/PVE-2023-52893/52893",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "reqkests": [
        {
            "advisory": "Reqkests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52894",
            "id": "pyup.io-52894",
            "more_info_path": "/vulnerabilities/PVE-2023-52894/52894",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "reqmgr2": [
        {
            "advisory": "WMAgent v1.3.3rc2 and 1.3.3rc1, reqmgr2 1.4.1rc5 and 1.4.0rc2, reqmon 1.4.1rc5, and global-workqueue 1.4.1rc5 allows attackers to execute arbitrary code via a crafted dbs-client package.",
            "cve": "CVE-2022-34558",
            "id": "pyup.io-54121",
            "more_info_path": "/vulnerabilities/CVE-2022-34558/54121",
            "specs": [
                ">=1.4.0rc2,<2.0.4"
            ],
            "v": ">=1.4.0rc2,<2.0.4"
        }
    ],
    "reqmon": [
        {
            "advisory": "WMAgent v1.3.3rc2 and 1.3.3rc1, reqmgr2 1.4.1rc5 and 1.4.0rc2, reqmon 1.4.1rc5, and global-workqueue 1.4.1rc5 allows attackers to execute arbitrary code via a crafted dbs-client package.",
            "cve": "CVE-2022-34558",
            "id": "pyup.io-54122",
            "more_info_path": "/vulnerabilities/CVE-2022-34558/54122",
            "specs": [
                ">=1.4.1rc5,<2.0.4"
            ],
            "v": ">=1.4.1rc5,<2.0.4"
        }
    ],
    "requesfs": [
        {
            "advisory": "Requesfs is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52895",
            "id": "pyup.io-52895",
            "more_info_path": "/vulnerabilities/PVE-2023-52895/52895",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "requesocks": [
        {
            "advisory": "Requesocks (a fork of requests package, working with socks proxy) is vulnerable to CVE-2018-18074.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-34110",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/34110",
            "specs": [
                "==0.10.8"
            ],
            "v": "==0.10.8"
        },
        {
            "advisory": "Requesocks (a fork of requests package, working with socks proxy) is vulnerable to CVE-2014-1829.",
            "cve": "CVE-2014-1829",
            "id": "pyup.io-52940",
            "more_info_path": "/vulnerabilities/CVE-2014-1829/52940",
            "specs": [
                "==0.10.8"
            ],
            "v": "==0.10.8"
        },
        {
            "advisory": "Requesocks (a fork of requests package, working with socks proxy) is vulnerable to CVE-2014-1830.",
            "cve": "CVE-2014-1830",
            "id": "pyup.io-52941",
            "more_info_path": "/vulnerabilities/CVE-2014-1830/52941",
            "specs": [
                "==0.10.8"
            ],
            "v": "==0.10.8"
        }
    ],
    "request-request": [
        {
            "advisory": "Request.request is a malicious package, typosquatting.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick",
            "cve": "PVE-2022-47817",
            "id": "pyup.io-47817",
            "more_info_path": "/vulnerabilities/PVE-2022-47817/47817",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "requesta": [
        {
            "advisory": "Requesta is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52896",
            "id": "pyup.io-52896",
            "more_info_path": "/vulnerabilities/PVE-2023-52896/52896",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "requeste": [
        {
            "advisory": "Requeste is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52897",
            "id": "pyup.io-52897",
            "more_info_path": "/vulnerabilities/PVE-2023-52897/52897",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "requestn": [
        {
            "advisory": "An attacker published a malicious Python package to the PyPI registry named \"requestn,\" which closely resembles the popular \"requests\" library. This package was designed to exfiltrate a victim's files to a remote Telegram server.",
            "cve": "PVE-2024-71487",
            "id": "pyup.io-71487",
            "more_info_path": "/vulnerabilities/PVE-2024-71487/71487",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "requests": [
        {
            "advisory": "Specific versions of Requests are susceptible to a Denial of Service (DoS) attack. This vulnerability is triggered when an incorrect password is sent in a digest authentication request, causing the library to indefinitely retry the request. Such behavior can be exploited by an attacker to send numerous requests, leading to a service outage by overwhelming the system's resources.",
            "cve": "PVE-2024-99889",
            "id": "pyup.io-65531",
            "more_info_path": "/vulnerabilities/PVE-2024-99889/65531",
            "specs": [
                "<0.13.4"
            ],
            "v": "<0.13.4"
        },
        {
            "advisory": "Requests before 2.3.0 exposes Authorization or Proxy-Authorization headers on redirect. See: CVE-2014-1829.",
            "cve": "CVE-2014-1829",
            "id": "pyup.io-26101",
            "more_info_path": "/vulnerabilities/CVE-2014-1829/26101",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Requests before 2.3.0 exposes Authorization or Proxy-Authorization headers on redirect. This fixes CVE-2014-1830.",
            "cve": "CVE-2014-1830",
            "id": "pyup.io-39575",
            "more_info_path": "/vulnerabilities/CVE-2014-1830/39575",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-71064",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/71064",
            "specs": [
                "<2.32.2"
            ],
            "v": "<2.32.2"
        },
        {
            "advisory": "Requests is an HTTP library. Due to a URL parsing issue, Requests releases prior to 2.32.4 may leak .netrc credentials to third parties for specific maliciously-crafted URLs. Users should upgrade to version 2.32.4 to receive a fix. For older versions of Requests, use of the .netrc file can be disabled with `trust_env=False` on one's Requests Session.",
            "cve": "CVE-2024-47081",
            "id": "pyup.io-77680",
            "more_info_path": "/vulnerabilities/CVE-2024-47081/77680",
            "specs": [
                "<2.32.4"
            ],
            "v": "<2.32.4"
        },
        {
            "advisory": "Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36546",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36546",
            "specs": [
                "<=2.19.1"
            ],
            "v": "<=2.19.1"
        },
        {
            "advisory": "The resolve_redirects function in sessions.py in requests 2.1.0 through 2.5.3 allows remote attackers to conduct session fixation attacks via a cookie without a host value in a redirect.",
            "cve": "CVE-2015-2296",
            "id": "pyup.io-26103",
            "more_info_path": "/vulnerabilities/CVE-2015-2296/26103",
            "specs": [
                ">=2.1,<=2.5.3"
            ],
            "v": ">=2.1,<=2.5.3"
        },
        {
            "advisory": "Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-58755",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/58755",
            "specs": [
                ">=2.3.0,<2.31.0"
            ],
            "v": ">=2.3.0,<2.31.0"
        }
    ],
    "requests-cache": [
        {
            "advisory": "Requests-cache 0.6.0 includes a fix for a code execution vulnerability.\r\nhttps://github.com/requests-cache/requests-cache/issues/105",
            "cve": "PVE-2021-40100",
            "id": "pyup.io-40100",
            "more_info_path": "/vulnerabilities/PVE-2021-40100/40100",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Some versions of requests-cache are susceptible to arbitrary code execution when interfacing with a Redis cache that has write permissions. This vulnerability allows attackers to execute arbitrary code by inserting a malicious payload into the cache. The attack involves exploiting the way requests-cache interacts with Redis, demonstrating that the cache contents can be manipulated to achieve code execution upon access. Users should consider the security configurations of their Redis setups and assess the risk associated with writable cache data stores to mitigate potential exploitation.",
            "cve": "PVE-2024-99888",
            "id": "pyup.io-65532",
            "more_info_path": "/vulnerabilities/PVE-2024-99888/65532",
            "specs": [
                ">=0,<0.6.0.dev1"
            ],
            "v": ">=0,<0.6.0.dev1"
        }
    ],
    "requests-doh": [
        {
            "advisory": "In version 0.3.1 of Requests-doh, the dependency on the requests library has been updated from version 2.28.2 to 2.31.0, as a measure to address CVE-2023-3268.\r\nhttps://github.com/mansuf/requests-doh/commit/84a9c708c0ac0f68797e1241eed0cccacfb5d92a",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-64444",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/64444",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        },
        {
            "advisory": "Requests-doh 1.0.0 updates its dependency 'dnspython' to v2.6.1 to include a security fix.",
            "cve": "CVE-2023-29483",
            "id": "pyup.io-73107",
            "more_info_path": "/vulnerabilities/CVE-2023-29483/73107",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Requests-doh 1.0.0 updates its dependency 'requests' to v2.32.3 to include a security fix.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-73100",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/73100",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "requests-httpx": [
        {
            "advisory": "Requests-httpx is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51684",
            "id": "pyup.io-51684",
            "more_info_path": "/vulnerabilities/PVE-2022-51684/51684",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "requests-kerberos": [
        {
            "advisory": "Python-requests-Kerberos through 0.5 does not handle mutual authentication correctly. See: CVE-2014-8650 and .",
            "cve": "CVE-2014-8650",
            "id": "pyup.io-37758",
            "more_info_path": "/vulnerabilities/CVE-2014-8650/37758",
            "specs": [
                "<=0.5"
            ],
            "v": "<=0.5"
        },
        {
            "advisory": "Versions of requests-kerberos are susceptible to a Regular Expression Denial of Service (ReDoS) attack. The vulnerability is triggered by a specific part of a regular expression within the kerberos_._negotiate_value function, where repeating a comma in a string matched against this expression leads to severe processing delays. This issue exemplifies how crafted inputs can exploit the nature of regular expression evaluations, causing catastrophic backtracking and significantly degrading performance, potentially to the point of a service denial by exhausting CPU resources.",
            "cve": "PVE-2024-99887",
            "id": "pyup.io-65533",
            "more_info_path": "/vulnerabilities/PVE-2024-99887/65533",
            "specs": [
                ">=0,<0.13.0rc1"
            ],
            "v": ">=0,<0.13.0rc1"
        }
    ],
    "requests-netdna": [
        {
            "advisory": "Requests-netdna (kennethreitz/requests fork) 0.13.6 and prior are vulnerable to CVE-2014-1829.",
            "cve": "CVE-2014-1829",
            "id": "pyup.io-47538",
            "more_info_path": "/vulnerabilities/CVE-2014-1829/47538",
            "specs": [
                "<=0.13.6"
            ],
            "v": "<=0.13.6"
        },
        {
            "advisory": "Requests-netdna (kennethreitz/requests fork) 0.13.6 and prior are vulnerable to CVE-2014-1830.",
            "cve": "CVE-2014-1830",
            "id": "pyup.io-48017",
            "more_info_path": "/vulnerabilities/CVE-2014-1830/48017",
            "specs": [
                "<=0.13.6"
            ],
            "v": "<=0.13.6"
        }
    ],
    "requests-xml": [
        {
            "advisory": "requests-xml v0.2.3 was discovered to contain an XML External Entity Injection (XXE) vulnerability which allows attackers to execute arbitrary code via a crafted XML file.",
            "cve": "CVE-2020-26708",
            "id": "pyup.io-65854",
            "more_info_path": "/vulnerabilities/CVE-2020-26708/65854",
            "specs": [
                "<=0.2.3"
            ],
            "v": "<=0.2.3"
        }
    ],
    "requestw": [
        {
            "advisory": "Requestw is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52898",
            "id": "pyup.io-52898",
            "more_info_path": "/vulnerabilities/PVE-2023-52898/52898",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "requfsts": [
        {
            "advisory": "Requfsts is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52899",
            "id": "pyup.io-52899",
            "more_info_path": "/vulnerabilities/PVE-2023-52899/52899",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "resilient": [
        {
            "advisory": "IBM Resilient OnPrem 38.2 could allow a privileged user to inject malicious commands through Python3 scripting. IBM X-Force ID: 185503. See CVE-2020-4636.",
            "cve": "CVE-2020-4636",
            "id": "pyup.io-38888",
            "more_info_path": "/vulnerabilities/CVE-2020-4636/38888",
            "specs": [
                ">=38,<39"
            ],
            "v": ">=38,<39"
        }
    ],
    "resolwe": [
        {
            "advisory": "Resolwe version 39.0.0 requires Jinja >= 3.1.3 to address the security vulnerability identified as CVE-2024-22195.",
            "cve": "CVE-2024-22195",
            "id": "pyup.io-71456",
            "more_info_path": "/vulnerabilities/CVE-2024-22195/71456",
            "specs": [
                "<39.0.0"
            ],
            "v": "<39.0.0"
        }
    ],
    "resonate-sdk": [
        {
            "advisory": "Affected versions of the resonate-sdk-py package are vulnerable to a race condition in the top-level code, leading to unpredictable behavior during concurrent operations. This can result in data inconsistencies or application crashes. The vulnerability arises from improper synchronization mechanisms in the codebase. The issue is addressed in 0.4.1, which removes the race condition by implementing appropriate locking mechanisms.",
            "cve": "PVE-2025-74975",
            "id": "pyup.io-74975",
            "more_info_path": "/vulnerabilities/PVE-2025-74975/74975",
            "specs": [
                "<0.4.1"
            ],
            "v": "<0.4.1"
        }
    ],
    "responsibleai": [
        {
            "advisory": "Responsibleai 0.18.0 updates its NPM dependency 'moment' to v2.29.2 to include a security fix.",
            "cve": "CVE-2022-24785",
            "id": "pyup.io-48231",
            "more_info_path": "/vulnerabilities/CVE-2022-24785/48231",
            "specs": [
                "<0.18.0"
            ],
            "v": "<0.18.0"
        },
        {
            "advisory": "Responsibleai 0.18.0 updates its NPM dependency 'minimist' to v1.2.6 to include a security fix.",
            "cve": "CVE-2021-44906",
            "id": "pyup.io-48222",
            "more_info_path": "/vulnerabilities/CVE-2021-44906/48222",
            "specs": [
                "<0.18.0"
            ],
            "v": "<0.18.0"
        }
    ],
    "responsibly": [
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'notebook' to versions >=5.7.8 to include security fixes.",
            "cve": "CVE-2016-6524",
            "id": "pyup.io-45266",
            "more_info_path": "/vulnerabilities/CVE-2016-6524/45266",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'notebook' to versions >=5.7.8 to include security fixes.",
            "cve": "CVE-2018-19352",
            "id": "pyup.io-45264",
            "more_info_path": "/vulnerabilities/CVE-2018-19352/45264",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'notebook' to versions >=5.7.8 to include security fixes.",
            "cve": "CVE-2019-10856",
            "id": "pyup.io-45261",
            "more_info_path": "/vulnerabilities/CVE-2019-10856/45261",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'requests' to versions >=2.20.0 to include security fixes.",
            "cve": "CVE-2013-2099",
            "id": "pyup.io-45271",
            "more_info_path": "/vulnerabilities/CVE-2013-2099/45271",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'requests' to versions >=2.20.0 to include security fixes.",
            "cve": "CVE-2015-2296",
            "id": "pyup.io-45268",
            "more_info_path": "/vulnerabilities/CVE-2015-2296/45268",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'requests' to versions >=2.20.0 to include security fixes.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-45267",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/45267",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'notebook' to versions >=5.7.8 to include security fixes.",
            "cve": "CVE-2018-19351",
            "id": "pyup.io-45265",
            "more_info_path": "/vulnerabilities/CVE-2018-19351/45265",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'notebook' to versions >=5.7.8 to include security fixes.",
            "cve": "CVE-2018-8768",
            "id": "pyup.io-45260",
            "more_info_path": "/vulnerabilities/CVE-2018-8768/45260",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'notebook' to versions >=5.7.8 to include security fixes.",
            "cve": "CVE-2018-21030",
            "id": "pyup.io-45259",
            "more_info_path": "/vulnerabilities/CVE-2018-21030/45259",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'notebook' to versions >=5.7.8 to include security fixes.",
            "cve": "CVE-2019-10255",
            "id": "pyup.io-45262",
            "more_info_path": "/vulnerabilities/CVE-2019-10255/45262",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'requests' to versions >=2.20.0 to include security fixes.",
            "cve": "CVE-2014-1830",
            "id": "pyup.io-45269",
            "more_info_path": "/vulnerabilities/CVE-2014-1830/45269",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'notebook' to versions >=5.7.8 to include security fixes.",
            "cve": "CVE-2019-9644",
            "id": "pyup.io-45263",
            "more_info_path": "/vulnerabilities/CVE-2019-9644/45263",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 updates its dependency 'jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-37335",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/37335",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        },
        {
            "advisory": "Responsibly 0.0.3 pins its dependency 'requests' to versions >=2.20.0 to include security fixes.",
            "cve": "CVE-2014-1829",
            "id": "pyup.io-45270",
            "more_info_path": "/vulnerabilities/CVE-2014-1829/45270",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        }
    ],
    "restauth": [
        {
            "advisory": "restauth before 0.6.3 did not verify passwords for services when using SECURE_CACHE = True.",
            "cve": "PVE-2021-26105",
            "id": "pyup.io-26105",
            "more_info_path": "/vulnerabilities/PVE-2021-26105/26105",
            "specs": [
                "<0.6.3"
            ],
            "v": "<0.6.3"
        },
        {
            "advisory": "Various versions of RestAuth are susceptible to an Authentication Bypass issue due to the default configuration setting SECURE_CACHE to False, resulting in passwords not being verified.",
            "cve": "PVE-2024-99886",
            "id": "pyup.io-65534",
            "more_info_path": "/vulnerabilities/PVE-2024-99886/65534",
            "specs": [
                ">=0.6.1,<0.6.3"
            ],
            "v": ">=0.6.1,<0.6.3"
        }
    ],
    "restful-client2": [
        {
            "advisory": "Restful-client2 1.0.0 enables SSL verification by default.\r\nhttps://github.com/johnbrandborg/restful-client2/commit/6b359a709cf40212b99f2001c639210a12e575f7",
            "cve": "PVE-2023-61675",
            "id": "pyup.io-61675",
            "more_info_path": "/vulnerabilities/PVE-2023-61675/61675",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "restkit": [
        {
            "advisory": "Restkit allows man-in-the-middle attackers to spoof TLS servers by leveraging use of the ssl.wrap_socket function in Python with the default CERT_NONE value for the cert_reqs argument.",
            "cve": "CVE-2015-2674",
            "id": "pyup.io-35609",
            "more_info_path": "/vulnerabilities/CVE-2015-2674/35609",
            "specs": [
                "<=4.2.2"
            ],
            "v": "<=4.2.2"
        }
    ],
    "restrictedpython": [
        {
            "advisory": "Restrictedpython 4.0 ships with a default implementation for ``_getattr_`` which prevents from using the ``format()`` method on str/unicode as it is not safe. See .\r\n\r\n **Caution:** If you do not already have secured the access to this ``format()`` method in your ``_getattr_`` implementation use ``RestrictedPython.Guards.safer_getattr()`` in your implementation to benefit from this fix.",
            "cve": "PVE-2021-37433",
            "id": "pyup.io-37433",
            "more_info_path": "/vulnerabilities/PVE-2021-37433/37433",
            "specs": [
                "<4.0"
            ],
            "v": "<4.0"
        },
        {
            "advisory": "Restrictedpython 6.1 and 5.3 include a fix for CVE-2023-37271: Arbitrary code execution via stack frame sandbox escape.\r\nhttps://github.com/zopefoundation/RestrictedPython/security/advisories/GHSA-wqc8-x2pr-7jqh",
            "cve": "CVE-2023-37271",
            "id": "pyup.io-59430",
            "more_info_path": "/vulnerabilities/CVE-2023-37271/59430",
            "specs": [
                "<5.3",
                ">=6.0a1.dev0,<6.1"
            ],
            "v": "<5.3,>=6.0a1.dev0,<6.1"
        },
        {
            "advisory": "RestrictedPython 6.2 and 5.4 include a fix for an Information Disclosure vulnerability. Python's \"format\" functionality allows someone controlling the format string to \"read\" all objects accessible through recursive attribute lookup and subscription from objects he can access. This can lead to critical information disclosure. With 'RestrictedPython', the format functionality is available via the 'format' and 'format_map' methods of 'str' (and 'Unicode') and via 'string.Formatter'.\r\nhttps://github.com/advisories/GHSA-xjw2-6jm9-rf67",
            "cve": "CVE-2023-41039",
            "id": "pyup.io-60840",
            "more_info_path": "/vulnerabilities/CVE-2023-41039/60840",
            "specs": [
                "<5.4",
                ">=6.0,<6.2"
            ],
            "v": "<5.4,>=6.0,<6.2"
        },
        {
            "advisory": "Affected versions of the RestrictedPython package are vulnerable to Information Disclosure due to inadvertent exposure of sensitive attributes via the `AttributeError.obj` property and the inclusion of the `string` module in the restricted built-ins. The `AttributeError.obj` attribute and the `string` module are accessible through the restricted execution environment because they are included in `RestrictedPython.Utilities.utility_builtins`, enabling protected internal objects to be referenced indirectly. An attacker can exploit this by crafting code that triggers an `AttributeError`, then inspecting `AttributeError.obj` or importing and using the `string` module within the restricted environment to access sensitive information, resulting in unintended exposure of protected data.",
            "cve": "CVE-2024-47532",
            "id": "pyup.io-78764",
            "more_info_path": "/vulnerabilities/CVE-2024-47532/78764",
            "specs": [
                "<7.3"
            ],
            "v": "<7.3"
        },
        {
            "advisory": "Via a type confusion bug in the CPython interpreter when using try/except* RestrictedPython could be bypassed. We believe this should be fixed upstream in Python itself until that we remove support for try/except* from RestrictedPython. (It has been fixed for some Python versions.)",
            "cve": "CVE-2025-22153",
            "id": "pyup.io-76354",
            "more_info_path": "/vulnerabilities/CVE-2025-22153/76354",
            "specs": [
                ">=6.0,<8.0"
            ],
            "v": ">=6.0,<8.0"
        }
    ],
    "restview": [
        {
            "advisory": "restview before 2.8.1 isn't properly checking the host header in HTTP requests, leading to possible DNS rebinding attacks. More info: https://github.com/mgedmin/restview/issues/51",
            "cve": "PVE-2021-35166",
            "id": "pyup.io-35166",
            "more_info_path": "/vulnerabilities/PVE-2021-35166/35166",
            "specs": [
                "<2.8.1"
            ],
            "v": "<2.8.1"
        },
        {
            "advisory": "A vulnerability threatens the security of selected versions of restview, a ReStructuredText viewer, due to a susceptibility to DNS rebinding attacks. This flaw stems from an inadequate verification of the host header in HTTP requests.",
            "cve": "PVE-2024-99885",
            "id": "pyup.io-65535",
            "more_info_path": "/vulnerabilities/PVE-2024-99885/65535",
            "specs": [
                ">=0,<2.8.1"
            ],
            "v": ">=0,<2.8.1"
        }
    ],
    "resuests": [
        {
            "advisory": "Resuests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52900",
            "id": "pyup.io-52900",
            "more_info_path": "/vulnerabilities/PVE-2023-52900/52900",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "rethinkdb": [
        {
            "advisory": "Rethinkdb 2.0.2 fixes a XSS vulnerability in the HTTP admin interface.",
            "cve": "PVE-2021-34518",
            "id": "pyup.io-34518",
            "more_info_path": "/vulnerabilities/PVE-2021-34518/34518",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        }
    ],
    "reversi42": [
        {
            "advisory": "Affected versions of this package are vulnerable to Insecure Temporary File Handling. The application fails to use platform-appropriate temporary directories by hardcoding /tmp paths, leading to potential unauthorized access to temporary files on systems where /tmp has insecure permissions or does not exist.",
            "cve": "PVE-2025-81642",
            "id": "pyup.io-81642",
            "more_info_path": "/vulnerabilities/PVE-2025-81642/81642",
            "specs": [
                "<6.2.2"
            ],
            "v": "<6.2.2"
        }
    ],
    "revibe": [
        {
            "advisory": "Affected versions of this package are vulnerable to command injection due to improper handling of user inputs in GitHub Action prompts. The prompt handling mechanism does not adequately sanitize inputs, allowing for arbitrary command execution. An attacker can exploit this vulnerability by crafting a malicious input that, when processed by the GitHub Action, executes unintended commands, potentially compromising the system.",
            "cve": "PVE-2025-83603",
            "id": "pyup.io-83603",
            "more_info_path": "/vulnerabilities/PVE-2025-83603/83603",
            "specs": [
                "<0.1.1.3"
            ],
            "v": "<0.1.1.3"
        }
    ],
    "reviewboard": [
        {
            "advisory": "A Cross-Site Scripting (XSS) vulnerability exists within Review Board versions 3.0.20 and 4.0 RC1 and earlier. An authenticated attacker may inject malicious Javascript code when using Markdown editing within the application which remains persistent.",
            "cve": "CVE-2021-31330",
            "id": "pyup.io-62683",
            "more_info_path": "/vulnerabilities/CVE-2021-31330/62683",
            "specs": [
                "<=3.0.20",
                ">3.0.25,<=4.0rc1"
            ],
            "v": "<=3.0.20,>3.0.25,<=4.0rc1"
        },
        {
            "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in Review Board 1.6.x before 1.6.21 and 1.7.x before 1.7.17 allow remote attackers to inject arbitrary web script or HTML via the (1) Branch field or (2) caption of an uploaded file.",
            "cve": "CVE-2013-4519",
            "id": "pyup.io-67967",
            "more_info_path": "/vulnerabilities/CVE-2013-4519/67967",
            "specs": [
                ">=1.6,<1.6.21",
                ">=1.7,<1.7.17"
            ],
            "v": ">=1.6,<1.6.21,>=1.7,<1.7.17"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in the Submitters list in Review Board 1.6.x before 1.6.18 and 1.7.x before 1.7.12 allows remote attackers to inject arbitrary web script or HTML via a user full name.",
            "cve": "CVE-2013-4795",
            "id": "pyup.io-67969",
            "more_info_path": "/vulnerabilities/CVE-2013-4795/67969",
            "specs": [
                ">=1.6,<1.6.21",
                ">=1.7,<1.7.17"
            ],
            "v": ">=1.6,<1.6.21,>=1.7,<1.7.17"
        }
    ],
    "rewuests": [
        {
            "advisory": "Rewuests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52901",
            "id": "pyup.io-52901",
            "more_info_path": "/vulnerabilities/PVE-2023-52901/52901",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "rez": [
        {
            "advisory": "Rez 2.100.1 fixes an insecure usage of tempfile.mktemp() vulnerability.\r\nhttps://github.com/nerdvegas/rez/pull/1165/commits/7008594bef61c0061f3fc4ce2363d83681a88663",
            "cve": "PVE-2021-43088",
            "id": "pyup.io-43088",
            "more_info_path": "/vulnerabilities/PVE-2021-43088/43088",
            "specs": [
                "<2.100.1"
            ],
            "v": "<2.100.1"
        }
    ],
    "rfc3161-client": [
        {
            "advisory": "RFC3161-client 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR's embedded certificates up to the trusted root(s), but fails to verify the TSR's own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce any TSR signature so long as the embedded leaf chains up to some root TSA.",
            "cve": "CVE-2025-52556",
            "id": "pyup.io-77746",
            "more_info_path": "/vulnerabilities/CVE-2025-52556/77746",
            "specs": [
                "<1.0.3"
            ],
            "v": "<1.0.3"
        }
    ],
    "rfquests": [
        {
            "advisory": "Rfquests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52902",
            "id": "pyup.io-52902",
            "more_info_path": "/vulnerabilities/PVE-2023-52902/52902",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "rhodecode": [
        {
            "advisory": "RhodeCode before 2.2.7 and Kallithea 0.1 allows remote authenticated users to obtain API keys and other sensitive information via the get_repo API method.",
            "cve": "CVE-2015-0260",
            "id": "pyup.io-54092",
            "more_info_path": "/vulnerabilities/CVE-2015-0260/54092",
            "specs": [
                ">=0,<2.2.7"
            ],
            "v": ">=0,<2.2.7"
        },
        {
            "advisory": "RhodeCode before 2.2.7 allows remote authenticated users to obtain API keys and other sensitive information via the (1) update_repo, (2) get_locks, or (3) get_user_groups API method.",
            "cve": "CVE-2015-1613",
            "id": "pyup.io-54097",
            "more_info_path": "/vulnerabilities/CVE-2015-1613/54097",
            "specs": [
                ">=0,<2.2.7"
            ],
            "v": ">=0,<2.2.7"
        }
    ],
    "richie": [
        {
            "advisory": "Richie 1.5.1 updates its NPM dependency 'lodash' to v4.17.14 to include a security fix.",
            "cve": "CVE-2019-10744",
            "id": "pyup.io-64306",
            "more_info_path": "/vulnerabilities/CVE-2019-10744/64306",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        },
        {
            "advisory": "Richie 1.5.1 updates its NPM dependency 'handlebars' to v4.1.2 to include a security fix.\r\nhttps://github.com/advisories/GHSA-q42p-pg8m-cqh6",
            "cve": "PVE-2024-64439",
            "id": "pyup.io-64439",
            "more_info_path": "/vulnerabilities/PVE-2024-64439/64439",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        }
    ],
    "ricloud": [
        {
            "advisory": "Ricloud 2.3.8 updates 'requests' in requirements to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-36723",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/36723",
            "specs": [
                "<2.3.8"
            ],
            "v": "<2.3.8"
        }
    ],
    "rife-ncnn-vulkan-python": [
        {
            "advisory": "Rife-ncnn-vulkan-python 1.2.1 and prior releases ship with a version of C library 'libwebp' which is affected by a high risk vulnerability.\r\nhttps://inspector.pypi.io/project/rife-ncnn-vulkan-python/1.2.1/packages/7d/eb/95529e003ac6a7de01d10601957320ee6af1fcd6195b762269e81b730fde/rife-ncnn-vulkan-python-1.2.1.tar.gz/rife-ncnn-vulkan-python-1.2.1/rife_ncnn_vulkan_python/rife-ncnn-vulkan/src/libwebp/ChangeLog",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62304",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62304",
            "specs": [
                "<=1.2.1"
            ],
            "v": "<=1.2.1"
        }
    ],
    "rinzler": [
        {
            "advisory": "rinzler 2.0.5 includes a PyYAML vulnerability correction",
            "cve": "PVE-2021-36895",
            "id": "pyup.io-36895",
            "more_info_path": "/vulnerabilities/PVE-2021-36895/36895",
            "specs": [
                "<2.0.5"
            ],
            "v": "<2.0.5"
        }
    ],
    "ripgrep": [
        {
            "advisory": "Affected versions of Ripgrep are affected by a CRITICAL vulnerability. Ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.",
            "cve": "CVE-2021-3013",
            "id": "pyup.io-72575",
            "more_info_path": "/vulnerabilities/CVE-2021-3013/72575",
            "specs": [
                "<13.0.0"
            ],
            "v": "<13.0.0"
        }
    ],
    "risingwave": [
        {
            "advisory": "Risingwave 0.1.10 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/risingwavelabs/risingwave/pull/3651",
            "cve": "PVE-2023-60165",
            "id": "pyup.io-60165",
            "more_info_path": "/vulnerabilities/PVE-2023-60165/60165",
            "specs": [
                "<0.1.10"
            ],
            "v": "<0.1.10"
        }
    ],
    "river-admin": [
        {
            "advisory": "River-admin 0.5.2 fixes a vulnerability issue with `serialize-javascript` dependency.",
            "cve": "PVE-2021-37698",
            "id": "pyup.io-37698",
            "more_info_path": "/vulnerabilities/PVE-2021-37698/37698",
            "specs": [
                "<0.5.2"
            ],
            "v": "<0.5.2"
        }
    ],
    "rkrizzle": [
        {
            "advisory": "Rkrizzle 2.6.0 includes a fix for CVE-2015-2296: The resolve_redirects function in sessions.py in rkrizzle (as it is a fork of requests library) 2.1.0 throughout 2.5.3 allows remote attackers to conduct session fixation attacks via a cookie without a host value in a redirect.",
            "cve": "CVE-2015-2296",
            "id": "pyup.io-34474",
            "more_info_path": "/vulnerabilities/CVE-2015-2296/34474",
            "specs": [
                ">=2.1.0,<2.6.0"
            ],
            "v": ">=2.1.0,<2.6.0"
        }
    ],
    "rmapy": [
        {
            "advisory": "Rmapy 0.2.4 updates Jinja2 to v2.11.3 to include a security fix.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-40057",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/40057",
            "specs": [
                "<0.2.4"
            ],
            "v": "<0.2.4"
        }
    ],
    "rnalysis": [
        {
            "advisory": "Rnalysis 1.3.6 updates its dependency 'pip' to v19.2 to include a security fix.",
            "cve": "CVE-2019-20916",
            "id": "pyup.io-40801",
            "more_info_path": "/vulnerabilities/CVE-2019-20916/40801",
            "specs": [
                "<1.3.6"
            ],
            "v": "<1.3.6"
        }
    ],
    "rnc": [
        {
            "advisory": "Rnc 0.6.5 updates its dependency 'lxml' to v4.6.3 to include a security fix.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-49115",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/49115",
            "specs": [
                "<0.6.5"
            ],
            "v": "<0.6.5"
        },
        {
            "advisory": "Rnc 0.6.5 updates its dependency 'aiohttp' to v3.7.4 to include a security fix.",
            "cve": "CVE-2021-21330",
            "id": "pyup.io-41204",
            "more_info_path": "/vulnerabilities/CVE-2021-21330/41204",
            "specs": [
                "<0.6.5"
            ],
            "v": "<0.6.5"
        }
    ],
    "rngatherd": [
        {
            "advisory": "Rngatherd 2.0 matches version 2 of RandPi which uses a more secure protocol. IVs are not reused anymore and the client sends a nonce to prevent replay-attacks.",
            "cve": "PVE-2021-34576",
            "id": "pyup.io-34576",
            "more_info_path": "/vulnerabilities/PVE-2021-34576/34576",
            "specs": [
                "<2.0"
            ],
            "v": "<2.0"
        }
    ],
    "rns": [
        {
            "advisory": "Rns 0.0.8 inlcudes a fix for a Race Condition vulnerability.\r\nhttps://github.com/acehoss/rnsh/commit/27664df0b315d15699d956ae2b3af8e65a6b438e",
            "cve": "PVE-2023-60402",
            "id": "pyup.io-60402",
            "more_info_path": "/vulnerabilities/PVE-2023-60402/60402",
            "specs": [
                "<0.0.8"
            ],
            "v": "<0.0.8"
        }
    ],
    "robomaster": [
        {
            "advisory": "Robomaster 0.1.1.44 and 0.1.1.61 ship with a version of C library 'libwebp' which is affected by a high risk vulnerability. Only mac OS X wheels on PyPI were affected.\r\nhttps://inspector.pypi.io/project/robomaster/0.1.1.61/packages/bf/bf/56b4b4f971f001e9753c52a35a58ecf8fae7ca2c28fc124f5a51ba7d3ff5/robomaster-0.1.1.61-cp36-cp36m-macosx_10_13_x86_64.whl",
            "cve": "CVE-2023-4863",
            "id": "pyup.io-62321",
            "more_info_path": "/vulnerabilities/CVE-2023-4863/62321",
            "specs": [
                "==0.1.1.44",
                "==0.1.1.61"
            ],
            "v": "==0.1.1.44,==0.1.1.61"
        }
    ],
    "robotframework-browser": [
        {
            "advisory": "Robotframework-browser 14.2.0 updates its dependency 'protobuf' to v4.21.9 to include a security fix.",
            "cve": "CVE-2022-1941",
            "id": "pyup.io-51550",
            "more_info_path": "/vulnerabilities/CVE-2022-1941/51550",
            "specs": [
                "<14.2.0"
            ],
            "v": "<14.2.0"
        }
    ],
    "robotframework-openapi-libcore": [
        {
            "advisory": "Robotframework-openapi-libcore 1.9.1 updates its dependency 'requests' to v2.31.0 to include a security fix.\r\nhttps://github.com/MarketSquare/robotframework-openapi-libcore/commit/dc8cb2ec97951c9e3a15a509b2a17c835114efcf",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-59149",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/59149",
            "specs": [
                "<1.9.1"
            ],
            "v": "<1.9.1"
        }
    ],
    "robotframework-templateddata": [
        {
            "advisory": "Robotframework-templateddata 1.4.0 escapes HTML and XML files by default to avoid XSS attacks.",
            "cve": "PVE-2023-55151",
            "id": "pyup.io-55151",
            "more_info_path": "/vulnerabilities/PVE-2023-55151/55151",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        }
    ],
    "robotraconteur": [
        {
            "advisory": "robotraconteur 0.9.0 changes: The `LocalTransport` file handle locations have been moved for increased security",
            "cve": "PVE-2021-37221",
            "id": "pyup.io-37221",
            "more_info_path": "/vulnerabilities/PVE-2021-37221/37221",
            "specs": [
                "<0.9.0"
            ],
            "v": "<0.9.0"
        }
    ],
    "robyn-rate-limits": [
        {
            "advisory": "Robyn-rate-limits 0.2.0 updates its dependency 'urllib3' to include a security fix.",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-62128",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/62128",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "rocketlogger": [
        {
            "advisory": "Rocketlogger 2.1.1 updates its dependency 'json5' to version '2.2.3' to fix a Prototype Pollution vulnerability.\r\nhttps://github.com/ETHZ-TEC/RocketLogger/commit/3d017bb8d91f3fadcb7b9cf7038510cc5ec41ce5",
            "cve": "CVE-2022-46175",
            "id": "pyup.io-59489",
            "more_info_path": "/vulnerabilities/CVE-2022-46175/59489",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Rocketlogger 2.1.1 updates its dependency 'nunjucks' to version '3.2.4' to fix a Cross-site Scripting vulnerability.\r\nhttps://github.com/ETHZ-TEC/RocketLogger/commit/3d017bb8d91f3fadcb7b9cf7038510cc5ec41ce5",
            "cve": "PVE-2023-59476",
            "id": "pyup.io-59476",
            "more_info_path": "/vulnerabilities/PVE-2023-59476/59476",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Rocketlogger 2.1.1 updates its dependency 'engine.io' to version '6.4.2' to fix an Uncaught Exception vulnerability.\r\nhttps://github.com/ETHZ-TEC/RocketLogger/commit/3d017bb8d91f3fadcb7b9cf7038510cc5ec41ce5",
            "cve": "CVE-2023-31125",
            "id": "pyup.io-59490",
            "more_info_path": "/vulnerabilities/CVE-2023-31125/59490",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Rocketlogger 2.1.2 updates its dependency 'semver' to version '7.5.4' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/ETHZ-TEC/RocketLogger/commit/6142c0e8d2bb6bcba2409f4a48ffaa2952d6d99f",
            "cve": "CVE-2022-25883",
            "id": "pyup.io-60131",
            "more_info_path": "/vulnerabilities/CVE-2022-25883/60131",
            "specs": [
                "<2.1.2"
            ],
            "v": "<2.1.2"
        }
    ],
    "rockhopper": [
        {
            "advisory": "Rockhopper 0.2.0 fixes a potential security exploit in RaggedArray.loads(buffer, ldtype=np.uint64).\r\nhttps://github.com/bwoodsend/rockhopper/commit/1a15fad5e06ae693eb9b8908363d2c8ef455104e",
            "cve": "PVE-2022-49718",
            "id": "pyup.io-49718",
            "more_info_path": "/vulnerabilities/PVE-2022-49718/49718",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        },
        {
            "advisory": "A vulnerability, which was classified as critical, has been found in bwoodsend rockhopper affected versions. Affected by this issue is the function count_rows of the file rockhopper/src/ragged_array.c of the component Binary Parser. The manipulation of the argument raw leads to buffer overflow. Local access is required to approach this attack.",
            "cve": "CVE-2022-4969",
            "id": "pyup.io-71928",
            "more_info_path": "/vulnerabilities/CVE-2022-4969/71928",
            "specs": [
                "<=0.1.2"
            ],
            "v": "<=0.1.2"
        }
    ],
    "rococo": [
        {
            "advisory": "Affected versions of the rococo package are vulnerable to SQL Injection due to unsanitized use of user-supplied pagination values in LIMIT and OFFSET clauses within the database adapter query builders. The MySQLAdapter.get_many, PostgresqlAdapter.get_many, and SurrealDBAdapter.get_one/get_many methods interpolate the limit and offset arguments directly into the SQL string using f-strings (for example, query += f\" LIMIT {limit}\" and query += f\" OFFSET {offset}\") instead of binding them as typed parameters, allowing arbitrary SQL fragments to be injected in those positions.",
            "cve": "PVE-2025-82229",
            "id": "pyup.io-82229",
            "more_info_path": "/vulnerabilities/PVE-2025-82229/82229",
            "specs": [
                "<1.1.11"
            ],
            "v": "<1.1.11"
        }
    ],
    "rokuecp": [
        {
            "advisory": "Rokuecp version 0.19.3 upgrades the dependency \"black\" from 24.2.0 to 24.3.0 in response to CVE-2024-21503, addressing a Regex-related denial of service vulnerability.",
            "cve": "CVE-2024-21503",
            "id": "pyup.io-70878",
            "more_info_path": "/vulnerabilities/CVE-2024-21503/70878",
            "specs": [
                "<0.19.3"
            ],
            "v": "<0.19.3"
        }
    ],
    "rolls-blockchain": [
        {
            "advisory": "Rolls-blockchain 1.0beta14 adds peers gossiping to partially protect from eclipse attacks.\r\nhttps://github.com/strandedathome/rolls-blockchain/commit/5b17e1cf237247c767173c7c6f08ba70a22449b3",
            "cve": "PVE-2022-44616",
            "id": "pyup.io-44616",
            "more_info_path": "/vulnerabilities/PVE-2022-44616/44616",
            "specs": [
                "<1.0beta14"
            ],
            "v": "<1.0beta14"
        },
        {
            "advisory": "Rolls-blockchain 1.0beta6 updates its dependency 'pyyaml' to v5.3.1 to include a security fix.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-44620",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/44620",
            "specs": [
                "<1.0beta6"
            ],
            "v": "<1.0beta6"
        },
        {
            "advisory": "Rolls-blockchain 1.0rc5 updates its dependency 'aiohttp' to v3.7.4 to include a security fix.",
            "cve": "CVE-2021-21330",
            "id": "pyup.io-44614",
            "more_info_path": "/vulnerabilities/CVE-2021-21330/44614",
            "specs": [
                "<1.0rc5"
            ],
            "v": "<1.0rc5"
        },
        {
            "advisory": "Rolls-blockchain 1.0rc6 implements rate limiting for full node to better defend against DDOS attacks.",
            "cve": "PVE-2022-44641",
            "id": "pyup.io-44641",
            "more_info_path": "/vulnerabilities/PVE-2022-44641/44641",
            "specs": [
                "<1.0rc6"
            ],
            "v": "<1.0rc6"
        },
        {
            "advisory": "Rolls-blockchain 1.0rc6 changes 'rolls keys add' to take secret words a prompt on the command line or stdin instead of command line arguments to avoid leaking them in logs.",
            "cve": "PVE-2022-44613",
            "id": "pyup.io-44613",
            "more_info_path": "/vulnerabilities/PVE-2022-44613/44613",
            "specs": [
                "<1.0rc6"
            ],
            "v": "<1.0rc6"
        },
        {
            "advisory": "Rolls-blockchain 1.1.3 mitigates 1-3 byte dust attacks.",
            "cve": "PVE-2022-44612",
            "id": "pyup.io-44612",
            "more_info_path": "/vulnerabilities/PVE-2022-44612/44612",
            "specs": [
                "<1.1.3"
            ],
            "v": "<1.1.3"
        }
    ],
    "rom": [
        {
            "advisory": "Rom 0.37.3 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/josiahcarlson/rom/commit/d4fef79fef2baf8e2c35dc90356bc50a0e6b65ee",
            "cve": "PVE-2023-59656",
            "id": "pyup.io-59656",
            "more_info_path": "/vulnerabilities/PVE-2023-59656/59656",
            "specs": [
                "<0.37.3"
            ],
            "v": "<0.37.3"
        }
    ],
    "rondolu-yt-concate": [
        {
            "advisory": "The Rondolu-YT-Concate package in PyPI v0.1.0 was discovered to contain a code execution backdoor. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.",
            "cve": "CVE-2022-34065",
            "id": "pyup.io-62704",
            "more_info_path": "/vulnerabilities/CVE-2022-34065/62704",
            "specs": [
                "==0.1.0"
            ],
            "v": "==0.1.0"
        }
    ],
    "root2hdf5": [
        {
            "advisory": "Root2hdf5 version 0.1.5 updates its tqdm dependency from 4.62.3 to 4.66.3 to address the security vulnerability identified as CVE-2024-34062.",
            "cve": "CVE-2024-34062",
            "id": "pyup.io-71346",
            "more_info_path": "/vulnerabilities/CVE-2024-34062/71346",
            "specs": [
                "<0.1.5"
            ],
            "v": "<0.1.5"
        }
    ],
    "rootinteractive": [
        {
            "advisory": "The RootInteractive package in PyPI v0.0.5 to v0.0.19b0 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.",
            "cve": "CVE-2022-32997",
            "id": "pyup.io-54221",
            "more_info_path": "/vulnerabilities/CVE-2022-32997/54221",
            "specs": [
                ">=0.0.5,<0.0.19"
            ],
            "v": ">=0.0.5,<0.0.19"
        }
    ],
    "rope": [
        {
            "advisory": "base/oi/doa.py in the Rope library in CPython (aka Python) allows remote attackers to execute arbitrary code by leveraging an unsafe call to pickle.load.",
            "cve": "CVE-2014-3539",
            "id": "pyup.io-36155",
            "more_info_path": "/vulnerabilities/CVE-2014-3539/36155",
            "specs": [
                "<0.10"
            ],
            "v": "<0.10"
        }
    ],
    "rosdep": [
        {
            "advisory": "Rosdep 0.15.2 migrates to yaml.safe_load() to avoid a RCE vulnerability.",
            "cve": "PVE-2021-39115",
            "id": "pyup.io-39115",
            "more_info_path": "/vulnerabilities/PVE-2021-39115/39115",
            "specs": [
                "<0.15.2"
            ],
            "v": "<0.15.2"
        }
    ],
    "rotten-tomatoes-cli": [
        {
            "advisory": "Rotten-tomatoes-cli 0.0.2 updates its dependency 'urllib3' to >=1.24.2 to include a security fix.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-42550",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/42550",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        },
        {
            "advisory": "Rotten-tomatoes-cli 0.0.2 updates its dependency 'requests' to >=2.20.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-42549",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/42549",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        },
        {
            "advisory": "Rotten-tomatoes-cli 0.0.2 updates its dependency 'pyyaml' to >=v4.2b1 to include a security fix.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-37315",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/37315",
            "specs": [
                "<0.0.2"
            ],
            "v": "<0.0.2"
        }
    ],
    "roundup": [
        {
            "advisory": "Roundup 0.6.0b4 includes a fix for a XSS vulnerability.\r\nhttps://github.com/roundup-tracker/roundup/commit/e4a893248de986ae5d4217a5ba5af3d10b8f9b01",
            "cve": "PVE-2023-58882",
            "id": "pyup.io-58882",
            "more_info_path": "/vulnerabilities/PVE-2023-58882/58882",
            "specs": [
                "<0.6.0b4"
            ],
            "v": "<0.6.0b4"
        },
        {
            "advisory": "Roundup 1.4.11 includes a security fix: If user hasn't permission on a message (notably files and content properties) and is on the nosy list, the content was sent via email.\r\nhttps://github.com/roundup-tracker/roundup/commit/52c63c89e34bb377f86b5efe51891491209ceb75",
            "cve": "PVE-2023-58871",
            "id": "pyup.io-58871",
            "more_info_path": "/vulnerabilities/PVE-2023-58871/58871",
            "specs": [
                "<1.4.11"
            ],
            "v": "<1.4.11"
        },
        {
            "advisory": "Roundup 1.4.11 includes a fix for a privileges escalation vulnerability.\r\nhttps://github.com/roundup-tracker/roundup/commit/30a43e13e15d43f2adfa6888d67cd08696fdfeb3",
            "cve": "PVE-2023-58891",
            "id": "pyup.io-58891",
            "more_info_path": "/vulnerabilities/PVE-2023-58891/58891",
            "specs": [
                "<1.4.11"
            ],
            "v": "<1.4.11"
        },
        {
            "advisory": "Roundup 1.4.17 includes a security fix: An user which didn't have access to a property could deduce its content by crafting a clever search, group or sort query.\r\nhttps://github.com/roundup-tracker/roundup/commit/b267853ddf7983c32bc0ada39a11eed0230903b6",
            "cve": "PVE-2023-58870",
            "id": "pyup.io-58870",
            "more_info_path": "/vulnerabilities/PVE-2023-58870/58870",
            "specs": [
                "<1.4.17"
            ],
            "v": "<1.4.17"
        },
        {
            "advisory": "Roundup 1.4.17 includes a fix for an unsafe password handling vulnerability.\r\nhttps://issues.roundup-tracker.org/issue2550688",
            "cve": "PVE-2023-58892",
            "id": "pyup.io-58892",
            "more_info_path": "/vulnerabilities/PVE-2023-58892/58892",
            "specs": [
                "<1.4.17"
            ],
            "v": "<1.4.17"
        },
        {
            "advisory": "Multiple cross-site scripting (XSS) vulnerabilities in Roundup before 1.4.20 allow remote attackers to inject arbitrary web script or HTML via the (1) @ok_message or (2) @error_message parameter to issue*. See: CVE-2012-6133.",
            "cve": "CVE-2012-6133",
            "id": "pyup.io-37744",
            "more_info_path": "/vulnerabilities/CVE-2012-6133/37744",
            "specs": [
                "<1.4.20"
            ],
            "v": "<1.4.20"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in cgi/client.py in Roundup before 1.4.20 allows remote attackers to inject arbitrary web script or HTML via the @action parameter to support/issue1.",
            "cve": "CVE-2012-6131",
            "id": "pyup.io-33163",
            "more_info_path": "/vulnerabilities/CVE-2012-6131/33163",
            "specs": [
                "<1.4.20"
            ],
            "v": "<1.4.20"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in the history display in Roundup before 1.4.20 allows remote attackers to inject arbitrary web script or HTML via a username, related to generating a link.",
            "cve": "CVE-2012-6130",
            "id": "pyup.io-33162",
            "more_info_path": "/vulnerabilities/CVE-2012-6130/33162",
            "specs": [
                "<1.4.20"
            ],
            "v": "<1.4.20"
        },
        {
            "advisory": "Roundup 1.4.7 disables serving uploaded HTML files content as HTML by default.\r\nhttps://github.com/roundup-tracker/roundup/commit/27ef29f1a64e89ebd4c5a99838a575ad3d44f993",
            "cve": "PVE-2023-58872",
            "id": "pyup.io-58872",
            "more_info_path": "/vulnerabilities/PVE-2023-58872/58872",
            "specs": [
                "<1.4.7"
            ],
            "v": "<1.4.7"
        },
        {
            "advisory": "Roundup 1.4.7 fixes improper permissions vulnerabilities.\r\nhttps://github.com/roundup-tracker/roundup/commit/27ef29f1a64e89ebd4c5a99838a575ad3d44f993",
            "cve": "PVE-2023-58890",
            "id": "pyup.io-58890",
            "more_info_path": "/vulnerabilities/PVE-2023-58890/58890",
            "specs": [
                "<1.4.7"
            ],
            "v": "<1.4.7"
        },
        {
            "advisory": "Roundup 1.5.1 includes a security fix: HTML attachments should not be served as text/html.\r\nhttps://issues.roundup-tracker.org/issue2550848",
            "cve": "PVE-2023-58893",
            "id": "pyup.io-58893",
            "more_info_path": "/vulnerabilities/PVE-2023-58893/58893",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        },
        {
            "advisory": "Roundup 1.5.1 includes a fix for a XSS vulnerability.\r\nhttps://issues.roundup-tracker.org/issue2550817",
            "cve": "PVE-2023-58867",
            "id": "pyup.io-58867",
            "more_info_path": "/vulnerabilities/PVE-2023-58867/58867",
            "specs": [
                "<1.5.1"
            ],
            "v": "<1.5.1"
        },
        {
            "advisory": "Roundup 1.6.0 includes a security fix: XSS on 404 page.\r\nhttps://issues.roundup-tracker.org/issue2551035",
            "cve": "PVE-2023-58894",
            "id": "pyup.io-58894",
            "more_info_path": "/vulnerabilities/PVE-2023-58894/58894",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        },
        {
            "advisory": "Roundup 1.6.0 includes a security fix: Inadequate CSRF protection.\r\nhttps://issues.roundup-tracker.org/issue2550690",
            "cve": "PVE-2023-58866",
            "id": "pyup.io-58866",
            "more_info_path": "/vulnerabilities/PVE-2023-58866/58866",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        },
        {
            "advisory": "Roundup 2.1.0b1 includes a fix for a timing attack vulnerability.\r\nhttps://github.com/roundup-tracker/roundup/commit/7c8deb493be61f66b65b0ac0e6edba2627fbd017",
            "cve": "PVE-2023-58899",
            "id": "pyup.io-58899",
            "more_info_path": "/vulnerabilities/PVE-2023-58899/58899",
            "specs": [
                "<2.1.0b1"
            ],
            "v": "<2.1.0b1"
        },
        {
            "advisory": "Roundup 2.1.0b1 updates its dependency 'jquery' to v3.5.1 to include security fixes.\r\nhttps://issues.roundup-tracker.org/issue2551100\r\nhttps://github.com/roundup-tracker/roundup/commit/ac9b7768dc99b5951f5b1b42b0b4d10696d5e7c1",
            "cve": "CVE-2015-9251",
            "id": "pyup.io-58896",
            "more_info_path": "/vulnerabilities/CVE-2015-9251/58896",
            "specs": [
                "<2.1.0b1"
            ],
            "v": "<2.1.0b1"
        },
        {
            "advisory": "Roundup 2.1.0b1 updates its dependency 'jquery' to v3.5.1 to include security fixes.\r\nhttps://issues.roundup-tracker.org/issue2551100\r\nhttps://github.com/roundup-tracker/roundup/commit/ac9b7768dc99b5951f5b1b42b0b4d10696d5e7c1",
            "cve": "CVE-2012-6708",
            "id": "pyup.io-58897",
            "more_info_path": "/vulnerabilities/CVE-2012-6708/58897",
            "specs": [
                "<2.1.0b1"
            ],
            "v": "<2.1.0b1"
        },
        {
            "advisory": "Roundup 2.1.0b1 updates its dependency 'jquery' to v3.5.1 to include security fixes.\r\nhttps://issues.roundup-tracker.org/issue2551100\r\nhttps://github.com/roundup-tracker/roundup/commit/ac9b7768dc99b5951f5b1b42b0b4d10696d5e7c1",
            "cve": "CVE-2011-4969",
            "id": "pyup.io-58898",
            "more_info_path": "/vulnerabilities/CVE-2011-4969/58898",
            "specs": [
                "<2.1.0b1"
            ],
            "v": "<2.1.0b1"
        },
        {
            "advisory": "Roundup 2.1.0b1 updates its dependency 'jquery' to v3.5.1 to include security fixes.\r\nhttps://issues.roundup-tracker.org/issue2551100\r\nhttps://github.com/roundup-tracker/roundup/commit/ac9b7768dc99b5951f5b1b42b0b4d10696d5e7c1",
            "cve": "CVE-2020-7656",
            "id": "pyup.io-58895",
            "more_info_path": "/vulnerabilities/CVE-2020-7656/58895",
            "specs": [
                "<2.1.0b1"
            ],
            "v": "<2.1.0b1"
        },
        {
            "advisory": "Roundup 2.1.0b1 updates its dependency 'jquery' to v3.5.1 to include security fixes.\r\nhttps://issues.roundup-tracker.org/issue2551100\r\nhttps://github.com/roundup-tracker/roundup/commit/ac9b7768dc99b5951f5b1b42b0b4d10696d5e7c1",
            "cve": "CVE-2019-11358",
            "id": "pyup.io-58863",
            "more_info_path": "/vulnerabilities/CVE-2019-11358/58863",
            "specs": [
                "<2.1.0b1"
            ],
            "v": "<2.1.0b1"
        },
        {
            "advisory": "Roundup 2.3.0b2 stops adding 'Access-Control-Allow-Credentials' header when using REST, to prevent an unauthorized third party website from using a user's credentials to access information in the tracker that is not publicly available.\r\nhttps://github.com/roundup-tracker/roundup/commit/5220f36fec484801c8fe2a206973da87aecf59d4",
            "cve": "PVE-2023-58862",
            "id": "pyup.io-58862",
            "more_info_path": "/vulnerabilities/PVE-2023-58862/58862",
            "specs": [
                "<2.3.0b2"
            ],
            "v": "<2.3.0b2"
        },
        {
            "advisory": "Roundup affected versions allow XSS via JavaScript in PDF, XML, and SVG documents.",
            "cve": "CVE-2024-39126",
            "id": "pyup.io-72258",
            "more_info_path": "/vulnerabilities/CVE-2024-39126/72258",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "In affected versions of Roundup, classhelpers (_generic.help.html) allows XSS.",
            "cve": "CVE-2024-39124",
            "id": "pyup.io-72259",
            "more_info_path": "/vulnerabilities/CVE-2024-39124/72259",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Roundup affected versions allow XSS via a SCRIPT element in an HTTP Referer header.",
            "cve": "CVE-2024-39125",
            "id": "pyup.io-72257",
            "more_info_path": "/vulnerabilities/CVE-2024-39125/72257",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "In Roundup before 2.5.0, XSS can occur via interaction between URLs and issue tracker templates (devel and responsive).",
            "cve": "CVE-2025-53865",
            "id": "pyup.io-78159",
            "more_info_path": "/vulnerabilities/CVE-2025-53865/78159",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        },
        {
            "advisory": "Directory traversal vulnerability in Roundup 0.6.4 and earlier allows remote attackers to view arbitrary files via .. (dot dot) sequences in an @@ command in an HTTP GET request.",
            "cve": "CVE-2004-1444",
            "id": "pyup.io-61226",
            "more_info_path": "/vulnerabilities/CVE-2004-1444/61226",
            "specs": [
                "<=0.6.4"
            ],
            "v": "<=0.6.4"
        },
        {
            "advisory": "Roundup 1.6 allows XSS via the URI because frontends/roundup.cgi and roundup/cgi/wsgi_handler.py mishandle 404 errors. See: CVE-2019-10904.",
            "cve": "CVE-2019-10904",
            "id": "pyup.io-37025",
            "more_info_path": "/vulnerabilities/CVE-2019-10904/37025",
            "specs": [
                "==1.6"
            ],
            "v": "==1.6"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in cgi/client.py in Roundup before 1.4.14 allows remote attackers to inject arbitrary web script or HTML via the template argument to the /issue program.",
            "cve": "CVE-2010-2491",
            "id": "pyup.io-54052",
            "more_info_path": "/vulnerabilities/CVE-2010-2491/54052",
            "specs": [
                ">=0,<1.4.14"
            ],
            "v": ">=0,<1.4.14"
        },
        {
            "advisory": "Cross-site scripting (XSS) vulnerability in Roundup before 1.4.20 allows remote attackers to inject arbitrary web script or HTML via the otk parameter.",
            "cve": "CVE-2012-6132",
            "id": "pyup.io-54079",
            "more_info_path": "/vulnerabilities/CVE-2012-6132/54079",
            "specs": [
                ">=0,<1.4.20"
            ],
            "v": ">=0,<1.4.20"
        },
        {
            "advisory": "Multiple unspecified vulnerabilities in Roundup before 1.4.4 have unknown impact and attack vectors, some of which may be related to cross-site scripting (XSS).",
            "cve": "CVE-2008-1474",
            "id": "pyup.io-54034",
            "more_info_path": "/vulnerabilities/CVE-2008-1474/54034",
            "specs": [
                ">=0,<1.4.4"
            ],
            "v": ">=0,<1.4.4"
        },
        {
            "advisory": "The xml-rpc server in Roundup 1.4.4 does not check property permissions, which allows attackers to bypass restrictions and edit or read restricted properties via the (1) list, (2) display, and (3) set methods.",
            "cve": "CVE-2008-1475",
            "id": "pyup.io-54035",
            "more_info_path": "/vulnerabilities/CVE-2008-1475/54035",
            "specs": [
                ">=0,<1.4.5"
            ],
            "v": ">=0,<1.4.5"
        },
        {
            "advisory": "schema.py in Roundup before 1.5.1 does not properly limit attributes included in default user permissions, which might allow remote authenticated users to obtain sensitive user information by viewing user details.",
            "cve": "CVE-2014-6276",
            "id": "pyup.io-54086",
            "more_info_path": "/vulnerabilities/CVE-2014-6276/54086",
            "specs": [
                ">=0,<1.5.1"
            ],
            "v": ">=0,<1.5.1"
        }
    ],
    "rozetka-api": [
        {
            "advisory": "Rozetka-api 1.1.6 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a vulnerability.\r\nhttps://github.com/ALERTua/rozetka_api/commit/ec51dcf627aa00cf67e40b89793a6b0a39615a5a",
            "cve": "CVE-2023-38325",
            "id": "pyup.io-60501",
            "more_info_path": "/vulnerabilities/CVE-2023-38325/60501",
            "specs": [
                "<1.1.6"
            ],
            "v": "<1.1.6"
        },
        {
            "advisory": "Rozetka-api 1.1.6 updates its dependency 'certifi' to version '2023.7.22' to include a fix for an Improper Following of a Certificate's Chain of Trust vulnerability.\r\nhttps://github.com/ALERTua/rozetka_api/commit/ec51dcf627aa00cf67e40b89793a6b0a39615a5a",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60497",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60497",
            "specs": [
                "<1.1.6"
            ],
            "v": "<1.1.6"
        },
        {
            "advisory": "Rozetka-api 1.1.6 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a vulnerability.\r\nhttps://github.com/ALERTua/rozetka_api/commit/ec51dcf627aa00cf67e40b89793a6b0a39615a5a",
            "cve": "CVE-2023-2975",
            "id": "pyup.io-60500",
            "more_info_path": "/vulnerabilities/CVE-2023-2975/60500",
            "specs": [
                "<1.1.6"
            ],
            "v": "<1.1.6"
        },
        {
            "advisory": "Rozetka-api 1.1.6 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a DoS vulnerability.\r\nhttps://github.com/ALERTua/rozetka_api/commit/ec51dcf627aa00cf67e40b89793a6b0a39615a5a",
            "cve": "CVE-2023-3446",
            "id": "pyup.io-60499",
            "more_info_path": "/vulnerabilities/CVE-2023-3446/60499",
            "specs": [
                "<1.1.6"
            ],
            "v": "<1.1.6"
        },
        {
            "advisory": "Rozetka-api 1.1.6 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a DoS vulnerability.\r\nhttps://github.com/ALERTua/rozetka_api/commit/ec51dcf627aa00cf67e40b89793a6b0a39615a5a",
            "cve": "CVE-2023-3817",
            "id": "pyup.io-60498",
            "more_info_path": "/vulnerabilities/CVE-2023-3817/60498",
            "specs": [
                "<1.1.6"
            ],
            "v": "<1.1.6"
        },
        {
            "advisory": "Rozetka-api 1.1.6 updates its dependency 'aiohttp' to version '3.8.5' to include a fix for an HTTP Request Smuggling vulnerability.\r\nhttps://github.com/ALERTua/rozetka_api/commit/ec51dcf627aa00cf67e40b89793a6b0a39615a5a",
            "cve": "CVE-2023-37276",
            "id": "pyup.io-60495",
            "more_info_path": "/vulnerabilities/CVE-2023-37276/60495",
            "specs": [
                "<1.1.6"
            ],
            "v": "<1.1.6"
        }
    ],
    "rpc-py": [
        {
            "advisory": "Rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the \"serializer: pickle\" HTTP header is sent. In other words, although JSON (not Pickle) is the default data format, an unauthenticated client can cause the data to be processed with unpickle. \r\nA fix for this issue is on master branch of the project's Github repository.\r\nhttps://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd",
            "cve": "CVE-2022-35411",
            "id": "pyup.io-54433",
            "more_info_path": "/vulnerabilities/CVE-2022-35411/54433",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "rpc4django": [
        {
            "advisory": "rpc4django before 0.2.3 is vulnerable to billion laughs denial of service attack.",
            "cve": "PVE-2021-26108",
            "id": "pyup.io-26108",
            "more_info_path": "/vulnerabilities/PVE-2021-26108/26108",
            "specs": [
                "<0.2.3"
            ],
            "v": "<0.2.3"
        },
        {
            "advisory": "A Denial of Service (DoS) vulnerability has been identified in selected versions of rpc4django, stemming from its handling of XMLRPC requests through the xml.dom.minidom.parseString() function. Malicious XML payloads can lead to high memory consumption, commonly referred to as the billion laughs attack, effectively rendering the service unavailable to legitimate users without targeting its security directly. This vulnerability illustrates the broader category of DoS attacks, focused on incapacitating web services by overwhelming them with a substantial load, thereby denying access to intended users.",
            "cve": "PVE-2024-99883",
            "id": "pyup.io-65536",
            "more_info_path": "/vulnerabilities/PVE-2024-99883/65536",
            "specs": [
                ">=0.1.8,<0.2.3"
            ],
            "v": ">=0.1.8,<0.2.3"
        }
    ],
    "rply": [
        {
            "advisory": "The parser cache functionality in parsergenerator.py in RPLY (aka python-rply) before 0.7.1 allows local users to spoof cache data by pre-creating a temporary rply-*.json file with a predictable name.",
            "cve": "CVE-2014-1604",
            "id": "pyup.io-35520",
            "more_info_path": "/vulnerabilities/CVE-2014-1604/35520",
            "specs": [
                "<0.7.1"
            ],
            "v": "<0.7.1"
        },
        {
            "advisory": "python-rply before 0.7.4 insecurely creates temporary files. See: CVE-2014-1938.",
            "cve": "CVE-2014-1938",
            "id": "pyup.io-37755",
            "more_info_path": "/vulnerabilities/CVE-2014-1938/37755",
            "specs": [
                "<0.7.4"
            ],
            "v": "<0.7.4"
        }
    ],
    "rpy2-arrow": [
        {
            "advisory": "Rpy2-arrow 0.1.2 updates its R dependency 'arrow' to versions '>=17.0' to include a security fix.",
            "cve": "CVE-2024-52338",
            "id": "pyup.io-74347",
            "more_info_path": "/vulnerabilities/CVE-2024-52338/74347",
            "specs": [
                "<0.1.2"
            ],
            "v": "<0.1.2"
        }
    ],
    "rpyc": [
        {
            "advisory": "Rpyc 4.1.2 includes a fix for CVE-2019-16328: a remote attacker can dynamically modify object attributes to construct a remote procedure call that executes code for an RPyC service with default configuration settings.",
            "cve": "CVE-2019-16328",
            "id": "pyup.io-37525",
            "more_info_path": "/vulnerabilities/CVE-2019-16328/37525",
            "specs": [
                "<4.1.2"
            ],
            "v": "<4.1.2"
        },
        {
            "advisory": "Rpyc 5.2.1 addresses a race condition related to remote multithreading that could stall the client during concurrent operations. The fix likely improves thread handling and synchronization to ensure smoother execution of remote procedures.\r\nhttps://github.com/tomerfiliba-org/rpyc/pull/531",
            "cve": "PVE-2024-65645",
            "id": "pyup.io-65645",
            "more_info_path": "/vulnerabilities/PVE-2024-65645/65645",
            "specs": [
                "<5.2.1"
            ],
            "v": "<5.2.1"
        },
        {
            "advisory": "Rpyc version 6.0.0 addresses a security vulnerability that could lead to remote code execution (RCE). The update, while enhancing security, may break compatibility for applications dependent on the __array__ attribute, notably used by numpy. This specific RCE risk is present when the server-side invokes the __array__ attribute, such as through np.array(x), making it critical for scenarios where untrusted input is processed.\r\nhttps://github.com/tomerfiliba-org/rpyc/commit/bba1d3562e6f9f1256ec64048cc23001c0bb7516",
            "cve": "PVE-2024-65644",
            "id": "pyup.io-65644",
            "more_info_path": "/vulnerabilities/PVE-2024-65644/65644",
            "specs": [
                "<6.0.0"
            ],
            "v": "<6.0.0"
        },
        {
            "advisory": "Affected versions of the rpyc package are vulnerable to Remote Code Execution due to a missing security check on the `__array__` attribute. The package\u2019s `NetrefClass` constructs the `__array__` method such that when a server-side method calls `np.array(client_netref)`, an attacker-supplied object can subvert this by defining a crafted `__array__`, enabling execution of arbitrary code. An attacker can exploit this by sending a malicious object via RPyC that leverages the `__array__` attribute during a `numpy.array(...)` call on the server, resulting in remote code execution in the context of the RPyC server process.",
            "cve": "CVE-2024-27758",
            "id": "pyup.io-78714",
            "more_info_path": "/vulnerabilities/CVE-2024-27758/78714",
            "specs": [
                ">=4.00,<6.0.0"
            ],
            "v": ">=4.00,<6.0.0"
        }
    ],
    "rq": [
        {
            "advisory": "Rq 0.7.1 resolves a race condition that prevented the proper setting of job statuses under high-load conditions, ensuring accurate status updates and job management.\r\nhttps://github.com/rq/rq/pull/742",
            "cve": "PVE-2024-65651",
            "id": "pyup.io-65651",
            "more_info_path": "/vulnerabilities/PVE-2024-65651/65651",
            "specs": [
                "<0.7.1"
            ],
            "v": "<0.7.1"
        }
    ],
    "rqeuests": [
        {
            "advisory": "Rqeuests is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51756",
            "id": "pyup.io-51756",
            "more_info_path": "/vulnerabilities/PVE-2022-51756/51756",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "rrquests": [
        {
            "advisory": "Rrquests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52903",
            "id": "pyup.io-52903",
            "more_info_path": "/vulnerabilities/PVE-2023-52903/52903",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "rs-django-jet": [
        {
            "advisory": "Rs-django-jet 1.0.4 fixes security issue with accessing model_lookup_view (when using RelatedFieldAjaxListFilter) without permissions.\r\nhttps://github.com/reckonsys/rs-django-jet/commit/734f3521d8290f6162847ad0b5c33d8ab5e119a9",
            "cve": "PVE-2021-36903",
            "id": "pyup.io-36903",
            "more_info_path": "/vulnerabilities/PVE-2021-36903/36903",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        }
    ],
    "rsa": [
        {
            "advisory": "Rsa 2.0 includes a security fix: Make sure p and q are different and phi_n is not divisible by 256. Any of the previous conditions would make breaking encryption trivial.\r\nhttps://github.com/sybrenstuvel/python-rsa/commit/f2fec9090cc4220e12b9b6f3102114bcc6aa9575",
            "cve": "PVE-2021-26109",
            "id": "pyup.io-26109",
            "more_info_path": "/vulnerabilities/PVE-2021-26109/26109",
            "specs": [
                "<2.0"
            ],
            "v": "<2.0"
        },
        {
            "advisory": "The verify function in the RSA package for Python (Python-RSA) before 3.3 allows attackers to spoof signatures with a small public exponent via crafted signature padding, aka a BERserk attack.",
            "cve": "CVE-2016-1494",
            "id": "pyup.io-33164",
            "more_info_path": "/vulnerabilities/CVE-2016-1494/33164",
            "specs": [
                "<3.3"
            ],
            "v": "<3.3"
        },
        {
            "advisory": "Rsa before 3.4 is vulnerable to timing attacks.\r\nhttps://github.com/sybrenstuvel/python-rsa/issues/19",
            "cve": "PVE-2021-26112",
            "id": "pyup.io-26112",
            "more_info_path": "/vulnerabilities/PVE-2021-26112/26112",
            "specs": [
                "<3.4"
            ],
            "v": "<3.4"
        },
        {
            "advisory": "Rsa 4.3 includes a fix for CVE-2020-13757: Python-RSA before 4.3 ignores leading '\\0' bytes during decryption of ciphertext. This could conceivably have a security-relevant impact, e.g., by helping an attacker to infer that an application uses Python-RSA, or if the length of accepted ciphertext affects application behavior (such as by causing excessive memory allocation).",
            "cve": "CVE-2020-13757",
            "id": "pyup.io-38414",
            "more_info_path": "/vulnerabilities/CVE-2020-13757/38414",
            "specs": [
                "<4.3"
            ],
            "v": "<4.3"
        },
        {
            "advisory": "Rsa 4.7 includes a fix for CVE-2020-25658: It was found that python-rsa is vulnerable to Bleichenbacher timing attacks. An attacker can use this flaw via the RSA decryption API to decrypt parts of the cipher text encrypted with RSA.",
            "cve": "CVE-2020-25658",
            "id": "pyup.io-39105",
            "more_info_path": "/vulnerabilities/CVE-2020-25658/39105",
            "specs": [
                ">=2.1,<4.7"
            ],
            "v": ">=2.1,<4.7"
        },
        {
            "advisory": "Specific versions of a Pure-Python RSA implementation are susceptible to an Authentication Bypass vulnerability. This flaw arises because the implementation does not use authentication encryption or Message Authentication Codes (MACs) to validate messages before decrypting them with a public key. This weakness potentially allows unauthorized access or information disclosure.",
            "cve": "PVE-2024-99882",
            "id": "pyup.io-65537",
            "more_info_path": "/vulnerabilities/PVE-2024-99882/65537",
            "specs": [
                ">=3.0,<3.4"
            ],
            "v": ">=3.0,<3.4"
        }
    ],
    "rsanic": [
        {
            "advisory": "rsanic before 0.2.2 is vulnerable to XSS attacks.",
            "cve": "PVE-2021-33007",
            "id": "pyup.io-33007",
            "more_info_path": "/vulnerabilities/PVE-2021-33007/33007",
            "specs": [
                "<0.2.2"
            ],
            "v": "<0.2.2"
        },
        {
            "advisory": "Versions of rsanic, a Python 3 based micro framework, are susceptible to Cross-site Scripting (XSS) attacks due to the autoescape option being disabled in the Jinja configuration. XSS attacks enable attackers to inject malicious content into web applications, tricking the application into delivering this content as if it were from a trusted source. This can lead to actions such as stealing cookies, hijacking user sessions, exposing sensitive information, enabling unauthorized access, and delivering malware. The vulnerability can manifest in several forms, including Stored, Reflected, DOM-based, and Mutated XSS, each with unique attack vectors ranging from inserting malicious links directly into applications to manipulating web pages in the client's browser.",
            "cve": "PVE-2024-99881",
            "id": "pyup.io-65538",
            "more_info_path": "/vulnerabilities/PVE-2024-99881/65538",
            "specs": [
                ">=0,<0.2.2"
            ],
            "v": ">=0,<0.2.2"
        }
    ],
    "rsconnect-jupyter": [
        {
            "advisory": "In addition to disabling TLS checking entirely, users in rsconnect-jupyter 1.3.0 have the option of uploading their own self-signed certificate bundle as a more secure TLS alternative.",
            "cve": "PVE-2021-38119",
            "id": "pyup.io-38119",
            "more_info_path": "/vulnerabilities/PVE-2021-38119/38119",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "rss2email": [
        {
            "advisory": "Rss2email 3.10 fixes SMTP security issues.",
            "cve": "PVE-2021-37430",
            "id": "pyup.io-37430",
            "more_info_path": "/vulnerabilities/PVE-2021-37430/37430",
            "specs": [
                "<3.10"
            ],
            "v": "<3.10"
        }
    ],
    "rtc-tools": [
        {
            "advisory": "Affected versions of the project are potentially vulnerable to XML External Entity (XXE) attacks. An attacker could potentially exploit this by providing malicious XML input, leading to unauthorized file access or network requests.",
            "cve": "PVE-2025-76765",
            "id": "pyup.io-76765",
            "more_info_path": "/vulnerabilities/PVE-2025-76765/76765",
            "specs": [
                "<2.7.0a1"
            ],
            "v": "<2.7.0a1"
        },
        {
            "advisory": "Affected versions of rtc-tools Csv_lookup_table_mixin were potentially vulnerable to insecure deserialization. An attacker could potentially execute arbitrary code by exploiting the deserialization of untrusted data, leading to a full server compromise. The issue existed in the caching mechanism using the `pickle` module.",
            "cve": "PVE-2025-76722",
            "id": "pyup.io-76722",
            "more_info_path": "/vulnerabilities/PVE-2025-76722/76722",
            "specs": [
                "<2.7.0a1"
            ],
            "v": "<2.7.0a1"
        }
    ],
    "rtslib-fb": [
        {
            "advisory": "Rtslib-fb 2.1.73 includes a fix for CVE-2020-14019.",
            "cve": "CVE-2020-14019",
            "id": "pyup.io-38468",
            "more_info_path": "/vulnerabilities/CVE-2020-14019/38468",
            "specs": [
                "<2.1.73"
            ],
            "v": "<2.1.73"
        }
    ],
    "rtv": [
        {
            "advisory": "rtv before 1.12.1 has a security vulnerability where malicious URLs could inject python code.",
            "cve": "PVE-2021-26113",
            "id": "pyup.io-26113",
            "more_info_path": "/vulnerabilities/PVE-2021-26113/26113",
            "specs": [
                "<1.12.1"
            ],
            "v": "<1.12.1"
        },
        {
            "advisory": "scripts/inspect_webbrowser.py in Reddit Terminal Viewer (RTV) 1.19.0 does not validate strings before launching the program specified by the BROWSER environment variable, which might allow remote attackers to conduct argument-injection attacks via a crafted URL.",
            "cve": "CVE-2017-17516",
            "id": "pyup.io-67430",
            "more_info_path": "/vulnerabilities/CVE-2017-17516/67430",
            "specs": [
                "<=1.19.0"
            ],
            "v": "<=1.19.0"
        },
        {
            "advisory": "Versions of rtv, a terminal viewer for Reddit, are susceptible to arbitrary code execution attacks. This vulnerability allows attackers to execute code arbitrarily on the system hosting the affected software.",
            "cve": "PVE-2024-99880",
            "id": "pyup.io-65539",
            "more_info_path": "/vulnerabilities/PVE-2024-99880/65539",
            "specs": [
                ">=0,<1.12.1"
            ],
            "v": ">=0,<1.12.1"
        }
    ],
    "ruamel-yaml": [
        {
            "advisory": "In ruamel.yaml through 0.16.7, the load method allows remote code execution if the application calls this method with an untrusted argument. In other words, this issue affects developers who are unaware of the need to use methods such as safe_load in these use cases.",
            "cve": "CVE-2019-20478",
            "id": "pyup.io-70598",
            "more_info_path": "/vulnerabilities/CVE-2019-20478/70598",
            "specs": [
                "<0.16.7"
            ],
            "v": "<0.16.7"
        }
    ],
    "rubicon-ml": [
        {
            "advisory": "Rubicon-ml 0.2.6 includes a fix to address a whitesource vulnerability.",
            "cve": "PVE-2021-41017",
            "id": "pyup.io-41017",
            "more_info_path": "/vulnerabilities/PVE-2021-41017/41017",
            "specs": [
                "<0.2.6"
            ],
            "v": "<0.2.6"
        }
    ],
    "rubrix": [
        {
            "advisory": "Rubrix 0.13.0 replaces vulnerable 'node-sass' v3.5.5 with 'sass' package.",
            "cve": "CVE-2019-6284",
            "id": "pyup.io-47842",
            "more_info_path": "/vulnerabilities/CVE-2019-6284/47842",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Rubrix 0.13.0 replaces vulnerable 'node-sass' v3.5.5 with 'sass' package.",
            "cve": "CVE-2019-18799",
            "id": "pyup.io-47843",
            "more_info_path": "/vulnerabilities/CVE-2019-18799/47843",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Rubrix 0.13.0 replaces vulnerable 'node-sass' v3.5.5 with 'sass' package.",
            "cve": "CVE-2018-19827",
            "id": "pyup.io-47841",
            "more_info_path": "/vulnerabilities/CVE-2018-19827/47841",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Rubrix 0.13.0 replaces vulnerable 'node-sass' v3.5.5 with 'sass' package.",
            "cve": "CVE-2020-24025",
            "id": "pyup.io-47838",
            "more_info_path": "/vulnerabilities/CVE-2020-24025/47838",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Rubrix 0.13.0 replaces vulnerable 'node-sass' v3.5.5 with 'sass' package.",
            "cve": "CVE-2019-18798",
            "id": "pyup.io-47845",
            "more_info_path": "/vulnerabilities/CVE-2019-18798/47845",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Rubrix 0.13.0 replaces vulnerable 'node-sass' v3.5.5 with 'sass' package.",
            "cve": "CVE-2019-18797",
            "id": "pyup.io-47844",
            "more_info_path": "/vulnerabilities/CVE-2019-18797/47844",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Rubrix 0.7.0 fixes a wrong email user validation regex.\r\nhttps://github.com/recognai/rubrix/commit/425e6e292d7f6f49bed098d88510912968d8e59f",
            "cve": "PVE-2021-42907",
            "id": "pyup.io-42907",
            "more_info_path": "/vulnerabilities/PVE-2021-42907/42907",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Rubrix 0.8.0 avoids an infinite loop when dataset is loading.\r\nhttps://github.com/recognai/rubrix/commit/ac0b90cc2fab604a1bdde34b624c71fb0790dd0a",
            "cve": "PVE-2022-44504",
            "id": "pyup.io-44504",
            "more_info_path": "/vulnerabilities/PVE-2022-44504/44504",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        }
    ],
    "rucio": [
        {
            "advisory": "Rucio 1.19.0.post2 upgrades its Paramiko dependency from version 2.4.1 to 2.4.2, addressing the security vulnerability CVE-2018-1000805.\r\nhttps://github.com/rucio/rucio/pull/1649/commits/0077bb6c80f5f8e49e47294375b41e6af051fc0b",
            "cve": "CVE-2018-1000805",
            "id": "pyup.io-64144",
            "more_info_path": "/vulnerabilities/CVE-2018-1000805/64144",
            "specs": [
                "<1.19.0.post2"
            ],
            "v": "<1.19.0.post2"
        },
        {
            "advisory": "Rucio 1.20.0 has updated its urllib3 dependency, moving from the previous version range of >=1.23,<1.24 to a new range of 2.20.0,<2.22.0. This change is a response to the security vulnerability identified as CVE-2019-11324.\r\nhttps://github.com/rucio/rucio/pull/2506/commits/15b73d85776c07e51ecc4fd0481638228532fc2b",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-64262",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/64262",
            "specs": [
                "<1.20.0"
            ],
            "v": "<1.20.0"
        },
        {
            "advisory": "Rucio 1.20.0 updates its SQLAlchemy dependency from version 1.2.16 to 1.3.3, in response to the security vulnerability identified as CVE-2019-7164.\r\nhttps://github.com/rucio/rucio/commit/122fd9cdc59c2e3e058a2b4fecef328d4d80029b",
            "cve": "CVE-2019-7164",
            "id": "pyup.io-64142",
            "more_info_path": "/vulnerabilities/CVE-2019-7164/64142",
            "specs": [
                "<1.20.0"
            ],
            "v": "<1.20.0"
        },
        {
            "advisory": "Rucio upgrades its paramiko dependency to include a fix for CVE-2022-24302.",
            "cve": "CVE-2022-24302",
            "id": "pyup.io-64133",
            "more_info_path": "/vulnerabilities/CVE-2022-24302/64133",
            "specs": [
                "<1.23.19",
                ">=1.24.0rc1,<1.26.12",
                ">=1.27.0rc1,<1.28.1"
            ],
            "v": "<1.23.19,>=1.24.0rc1,<1.26.12,>=1.27.0rc1,<1.28.1"
        }
    ],
    "rucio-webui": [
        {
            "advisory": "Rucio-webui 1.26.7 includes a security fix: Potentially leak of the contents of cookies to other sessions within a wsgi container. Impact is that Rucio authentication tokens are leaked to other users accessing the 'webui' within a close timeframe, thus allowing users to access the `webui` with the leaked authentication token. Privileges are therefore also escalated. Rucio server / daemons are not affected by this issue, it is isolated to the webui.\r\nhttps://github.com/rucio/rucio/issues/4928",
            "cve": "PVE-2023-55207",
            "id": "pyup.io-55207",
            "more_info_path": "/vulnerabilities/PVE-2023-55207/55207",
            "specs": [
                ">=1.26.0,<1.26.7"
            ],
            "v": ">=1.26.0,<1.26.7"
        }
    ],
    "ruffruffs": [
        {
            "advisory": "ruffruffs 2.6.0 fixes handling of cookies on redirect. Previously a cookie without a host value set would use the hostname for the redirected URL exposing requests users to session fixation attacks and potentially cookie stealing.",
            "cve": "CVE-2015-2296",
            "id": "pyup.io-26116",
            "more_info_path": "/vulnerabilities/CVE-2015-2296/26116",
            "specs": [
                "<2.6.0"
            ],
            "v": "<2.6.0"
        }
    ],
    "rumdl": [
        {
            "advisory": "Affected versions of the `rumdl` package are vulnerable to Regular Expression Denial of Service (ReDoS) due to inefficient regex patterns with unbounded backtracking in link and image parsing logic. The regex patterns in `lint_context.rs` allow the regex engine to perform exponential backtracking when processing specially crafted inputs with nested or repetitive link and image syntax. An attacker can exploit this by submitting malicious Markdown files containing pathological input patterns designed to trigger catastrophic backtracking, causing the parser to consume excessive CPU resources and time, effectively rendering the service unresponsive or causing Denial of Service for legitimate users.",
            "cve": "PVE-2025-81679",
            "id": "pyup.io-81679",
            "more_info_path": "/vulnerabilities/PVE-2025-81679/81679",
            "specs": [
                "<0.0.179"
            ],
            "v": "<0.0.179"
        }
    ],
    "runway": [
        {
            "advisory": "Runway 1.16.0 has enhanced security via nonce signing (Static Site AuthEdge).",
            "cve": "PVE-2021-39085",
            "id": "pyup.io-39085",
            "more_info_path": "/vulnerabilities/PVE-2021-39085/39085",
            "specs": [
                "<1.16.0"
            ],
            "v": "<1.16.0"
        },
        {
            "advisory": "Runway 2.5.0 updates its dependency 'pipenv' to v2022.1.8 to include a security fix.",
            "cve": "CVE-2022-21668",
            "id": "pyup.io-44558",
            "more_info_path": "/vulnerabilities/CVE-2022-21668/44558",
            "specs": [
                "<2.5.0"
            ],
            "v": "<2.5.0"
        }
    ],
    "rwquests": [
        {
            "advisory": "Rwquests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html",
            "cve": "PVE-2023-52904",
            "id": "pyup.io-52904",
            "more_info_path": "/vulnerabilities/PVE-2023-52904/52904",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "rwslib": [
        {
            "advisory": "Rwslib 1.2.10 updates its dependency 'certifi' to v2023.7.22 to include a security fix.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-62188",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/62188",
            "specs": [
                "<1.2.10"
            ],
            "v": "<1.2.10"
        }
    ],
    "rxiv-maker": [
        {
            "advisory": "Affected versions of the rxiv-maker package are vulnerable to Command Injection due to improper handling of shell commands. The `upgrade` command previously used `shell=True`, which allowed for potential shell injection vulnerabilities. An attacker could exploit this vulnerability by injecting malicious shell commands into the upgrade process, potentially executing arbitrary code on the user's system.",
            "cve": "PVE-2025-81663",
            "id": "pyup.io-81663",
            "more_info_path": "/vulnerabilities/PVE-2025-81663/81663",
            "specs": [
                "<1.8.9"
            ],
            "v": "<1.8.9"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal. The GitHub name validation fails to sanitize path separators, special characters, and null bytes in user input, leading to attackers being able to access files outside the intended directory through crafted GitHub names containing traversal sequences or null byte injection.",
            "cve": "PVE-2025-81662",
            "id": "pyup.io-81662",
            "more_info_path": "/vulnerabilities/PVE-2025-81662/81662",
            "specs": [
                "<1.9.0"
            ],
            "v": "<1.9.0"
        }
    ],
    "ryu": [
        {
            "advisory": "An issue was discovered in OFPQueueGetConfigReply in parser.py in Faucet SDN Ryu version 4.34, allows remote attackers to cause a denial of service (DoS) (infinite loop).",
            "cve": "CVE-2020-35141",
            "id": "pyup.io-65856",
            "more_info_path": "/vulnerabilities/CVE-2020-35141/65856",
            "specs": [
                "<=4.34"
            ],
            "v": "<=4.34"
        },
        {
            "advisory": "An issue was discovered in OFPBundleCtrlMsg in parser.py in Faucet SDN Ryu version 4.34, allows remote attackers to cause a denial of service (DoS) (infinite loop).",
            "cve": "CVE-2020-35139",
            "id": "pyup.io-65855",
            "more_info_path": "/vulnerabilities/CVE-2020-35139/65855",
            "specs": [
                "<=4.34"
            ],
            "v": "<=4.34"
        },
        {
            "advisory": "Faucet SDN Ryu has a vulnerability in the OFPBucket parser located in parser.py. Affected versions allow attackers to cause a denial of service (infinite loop) by setting action.len to 0. This vulnerability can be exploited to disrupt normal operations and make the system unresponsive.",
            "cve": "CVE-2024-34484",
            "id": "pyup.io-72154",
            "more_info_path": "/vulnerabilities/CVE-2024-34484/72154",
            "specs": [
                "<=4.34"
            ],
            "v": "<=4.34"
        },
        {
            "advisory": "Faucet SDN Ryu has a vulnerability in the OFPPacketQueue parser located in parser.py. Affected versions allow attackers to cause a denial of service (infinite loop) by setting OFPQueueProp.len to 0. This vulnerability can be exploited to disrupt normal operations and make the system unresponsive.",
            "cve": "CVE-2024-34486",
            "id": "pyup.io-72152",
            "more_info_path": "/vulnerabilities/CVE-2024-34486/72152",
            "specs": [
                "<=4.34"
            ],
            "v": "<=4.34"
        },
        {
            "advisory": "Affected versions of the ryu package are vulnerable to Denial of Service due to an infinite loop caused by a zero-length condition in the OFPMultipartReply parser. The `OFPMultipartReply` function in `parser.py` fails to handle `b.length` being zero, resulting in an unreachable exit condition that leads to infinite looping. A remote attacker can exploit this by sending a specially crafted OpenFlow multipart reply packet with `b.length` set to zero, causing the Ryu controller to become unresponsive and degrade network service availability.",
            "cve": "CVE-2024-34488",
            "id": "pyup.io-78722",
            "more_info_path": "/vulnerabilities/CVE-2024-34488/78722",
            "specs": [
                "<=4.34"
            ],
            "v": "<=4.34"
        },
        {
            "advisory": "Affected versions of the Ryu package are vulnerable to Denial of Service due to an infinite loop caused by an unreachable exit condition in the OFPMatch parser. The parser.py file\u2019s OFPMatch component in Ryu version 4.34 fails to properly terminate parsing of specially crafted OpenFlow messages, leading to a loop that never exits. A remote attacker can exploit this by sending a malformed OpenFlow packet to the Ryu controller, causing unbounded processing and rendering the controller unresponsive.",
            "cve": "CVE-2024-28732",
            "id": "pyup.io-78718",
            "more_info_path": "/vulnerabilities/CVE-2024-28732/78718",
            "specs": [
                "<=4.34"
            ],
            "v": "<=4.34"
        },
        {
            "advisory": "Affected versions of the Ryu package are vulnerable to Denial of Service due to an infinite loop caused by improper handling of a zero-length `inst.length` value. The `OFPFlowStats` class in `parser.py` fails to handle `inst.length` being zero, resulting in an unreachable exit condition and non-terminating loop in Ryu version 4.34. A remote attacker can exploit this by sending a specially crafted OpenFlow packet with `inst.length` set to zero, causing the Ryu controller to become unresponsive and disrupting network operations.",
            "cve": "CVE-2024-34487",
            "id": "pyup.io-78725",
            "more_info_path": "/vulnerabilities/CVE-2024-34487/78725",
            "specs": [
                "<=4.34"
            ],
            "v": "<=4.34"
        },
        {
            "advisory": "Faucet SDN Ryu has a vulnerability in the OFPHello parser located in parser.py. Affected versions allow attackers to cause a denial of service (infinite loop) by setting length=0. This vulnerability can be exploited to disrupt normal operations and render the system unresponsive.",
            "cve": "CVE-2024-34489",
            "id": "pyup.io-72153",
            "more_info_path": "/vulnerabilities/CVE-2024-34489/72153",
            "specs": [
                "<=4.34"
            ],
            "v": "<=4.34"
        },
        {
            "advisory": "Faucet SDN Ryu has a vulnerability in the OFPGroupDescStats parser located in parser.py. Affected versions allow attackers to cause a denial of service (infinite loop) by setting OFPBucket.len to 0. This vulnerability can be exploited to disrupt normal operations and make the system unresponsive.",
            "cve": "CVE-2024-34483",
            "id": "pyup.io-72151",
            "more_info_path": "/vulnerabilities/CVE-2024-34483/72151",
            "specs": [
                "<=4.34"
            ],
            "v": "<=4.34"
        }
    ],
    "s3scanner": [
        {
            "advisory": "S3scanner 2.0.2 includes a fix for CVE-2021-32061: S3Scanner before 2.0.2 allows Directory Traversal via a crafted bucket, as demonstrated by a ../ substring in a ListBucketResult element.\r\nhttps://github.com/sa7mon/S3Scanner/issues/122",
            "cve": "CVE-2021-32061",
            "id": "pyup.io-42898",
            "more_info_path": "/vulnerabilities/CVE-2021-32061/42898",
            "specs": [
                "<2.0.2"
            ],
            "v": "<2.0.2"
        }
    ],
    "s3transfere": [
        {
            "advisory": "S3transfere is a malicious package, pytosquatting the popular package 's3transfer'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53262",
            "id": "pyup.io-53262",
            "more_info_path": "/vulnerabilities/PVE-2023-53262/53262",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "s3transferr": [
        {
            "advisory": "S3transferr is a malicious package, pytosquatting the popular package 's3transfer'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53263",
            "id": "pyup.io-53263",
            "more_info_path": "/vulnerabilities/PVE-2023-53263/53263",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "s3transferss": [
        {
            "advisory": "S3transferss is a malicious package, pytosquatting the popular package 's3transfer'. It contains a base64 encoded payload in '__init__.py' file that retrieves your current username, platform and IP information.",
            "cve": "PVE-2023-53264",
            "id": "pyup.io-53264",
            "more_info_path": "/vulnerabilities/PVE-2023-53264/53264",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "s4": [
        {
            "advisory": "S4 0.4.2 upgrades boto3 to minimum requirement to fix a vulnerability in a urllib3 dependency.",
            "cve": "PVE-2021-37119",
            "id": "pyup.io-37119",
            "more_info_path": "/vulnerabilities/PVE-2021-37119/37119",
            "specs": [
                "<0.4.2"
            ],
            "v": "<0.4.2"
        }
    ],
    "saes": [
        {
            "advisory": "Saes 1.3.2 updates its dependency 'jinja2' to include a security fix.",
            "cve": "CVE-2025-27516",
            "id": "pyup.io-75737",
            "more_info_path": "/vulnerabilities/CVE-2025-27516/75737",
            "specs": [
                "<1.3.2"
            ],
            "v": "<1.3.2"
        }
    ],
    "safecmd": [
        {
            "advisory": "Affected versions of the safecmd package are vulnerable to path traversal due to improper normalization of output redirect destinations before allowlist matching.",
            "cve": "PVE-2026-85051",
            "id": "pyup.io-85051",
            "more_info_path": "/vulnerabilities/PVE-2026-85051/85051",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        }
    ],
    "safety": [
        {
            "advisory": "Safety 1.8.4 updates its dependency 'cryptography' to v2.3 to include security fixes.",
            "cve": "CVE-2017-3735",
            "id": "pyup.io-50749",
            "more_info_path": "/vulnerabilities/CVE-2017-3735/50749",
            "specs": [
                "<1.8.4"
            ],
            "v": "<1.8.4"
        },
        {
            "advisory": "Safety 1.8.4 updates its dependency 'cryptography' to v2.3 to include security fixes.",
            "cve": "CVE-2018-10903",
            "id": "pyup.io-36367",
            "more_info_path": "/vulnerabilities/CVE-2018-10903/36367",
            "specs": [
                "<1.8.4"
            ],
            "v": "<1.8.4"
        },
        {
            "advisory": "Safety 1.8.4 updates its dependency 'cryptography' to v2.3 to include security fixes.",
            "cve": "CVE-2017-3736",
            "id": "pyup.io-50750",
            "more_info_path": "/vulnerabilities/CVE-2017-3736/50750",
            "specs": [
                "<1.8.4"
            ],
            "v": "<1.8.4"
        },
        {
            "advisory": "Safety 2.2.0 updates its dependency 'dparse' to include a security fix.",
            "cve": "CVE-2022-39280",
            "id": "pyup.io-51358",
            "more_info_path": "/vulnerabilities/CVE-2022-39280/51358",
            "specs": [
                "<2.2.0"
            ],
            "v": "<2.2.0"
        },
        {
            "advisory": "The command-line \"safety\" package for Python has a potential security issue. There are two Python characteristics that allow malicious code to \u201cpoison-pill\u201d command-line Safety package detection routines by disguising, or obfuscating, other malicious or non-secure packages. This vulnerability is considered to be of low severity because the attack makes use of an existing Python condition, not the Safety tool itself. This can happen if: You are running Safety in a Python environment that you don\u2019t trust. You are running Safety from the same Python environment where you have your dependencies installed. Dependency packages are being installed arbitrarily or without proper verification. Users can mitigate this issue by doing any of the following: Perform a static analysis by installing Docker and running the Safety Docker image: $ docker run --rm -it pyupio/safety check -r requirements.txt Run Safety against a static dependencies list, such as the requirements.txt file, in a separate, clean Python environment. Run Safety from a Continuous Integration pipeline. Use PyUp.io, which runs Safety in a controlled environment and checks Python for dependencies without any need to install them. Use PyUp's Online Requirements Checker.",
            "cve": "CVE-2020-5252",
            "id": "pyup.io-42296",
            "more_info_path": "/vulnerabilities/CVE-2020-5252/42296",
            "specs": [
                "<=1.8.6"
            ],
            "v": "<=1.8.6"
        }
    ],
    "safeurl-python": [
        {
            "advisory": "Safeurl-python 1.2 includes a fix for CVE-2023-24622: isInList in the safeurl-python package before 1.2 for Python has an insufficiently restrictive regular expression for external domains, leading to SSRF.\r\nhttps://github.com/IncludeSecurity/safeurl-python/security/advisories/GHSA-jgh8-vchw-q3g7",
            "cve": "CVE-2023-24622",
            "id": "pyup.io-52933",
            "more_info_path": "/vulnerabilities/CVE-2023-24622/52933",
            "specs": [
                "<1.2"
            ],
            "v": "<1.2"
        },
        {
            "advisory": "Versions of the safeurl-python library are susceptible to an Access Control Bypass vulnerability because they fail to block fully qualified domain names (FQDNs). This flaw allows attackers to bypass hostname blacklists by appending a dot to the end of the blacklisted hostname, potentially leading to server-side request forgery (SSRF) incidents.",
            "cve": "PVE-2024-99878",
            "id": "pyup.io-65542",
            "more_info_path": "/vulnerabilities/PVE-2024-99878/65542",
            "specs": [
                ">=0,<1.3"
            ],
            "v": ">=0,<1.3"
        }
    ],
    "sagemaker": [
        {
            "advisory": "Sagemaker 2.111.0 updates its dependency 'apache-airflow' to v2.4.0 to include a security fix.",
            "cve": "CVE-2022-40754",
            "id": "pyup.io-51357",
            "more_info_path": "/vulnerabilities/CVE-2022-40754/51357",
            "specs": [
                "<2.111.0"
            ],
            "v": "<2.111.0"
        },
        {
            "advisory": "sagemaker-python-sdk is a library for training and deploying machine learning models on Amazon SageMaker. The sagemaker.base_deserializers.NumpyDeserializer module before v2.218.0 allows potentially unsafe deserialization when untrusted data is passed as pickled object arrays. This consequently may allow an unprivileged third party to cause remote code execution, denial of service, affecting both confidentiality and integrity. Users are advised to upgrade to version 2.218.0. Users unable to upgrade should not pass pickled numpy object arrays which originated from an untrusted source, or that could have been tampered with. Only pass pickled numpy object arrays from trusted sources.",
            "cve": "CVE-2024-34072",
            "id": "pyup.io-71631",
            "more_info_path": "/vulnerabilities/CVE-2024-34072/71631",
            "specs": [
                "<2.218.0"
            ],
            "v": "<2.218.0"
        },
        {
            "advisory": "A vulnerability in the SageMaker Workflow component of aws/sagemaker-python-sdk allows for the possibility of MD5 hash collisions in all versions. This can lead to workflows being inadvertently replaced due to the reuse of results from different configurations that produce the same MD5 hash. This issue can cause integrity problems within the pipeline, potentially leading to erroneous processing outcomes.",
            "cve": "CVE-2025-0508",
            "id": "pyup.io-76180",
            "more_info_path": "/vulnerabilities/CVE-2025-0508/76180",
            "specs": [
                "<2.237.3"
            ],
            "v": "<2.237.3"
        },
        {
            "advisory": "Affected versions of the sagemaker package are vulnerable to OS Command Injection due to improper handling of the `requirements_path` parameter. The `capture_dependencies` function in the `sagemaker.serve.save_retrive.version_1_0_0.save.utils` module executes system commands based on user input without adequate validation or sanitization. An attacker can exploit this by supplying a malicious command as the \"requirements_path\" parameter, potentially leading to Remote Code Execution, Denial of Service, and compromising both confidentiality and integrity.",
            "cve": "CVE-2024-34073",
            "id": "pyup.io-71630",
            "more_info_path": "/vulnerabilities/CVE-2024-34073/71630",
            "specs": [
                ">=2.199.0,<2.214.3"
            ],
            "v": ">=2.199.0,<2.214.3"
        }
    ],
    "sagemaker-containers": [
        {
            "advisory": "Sagemaker-containers 2.8.2 updates its dependency 'psutil' to v5.6.7 to include a security fix.",
            "cve": "CVE-2019-18874",
            "id": "pyup.io-38087",
            "more_info_path": "/vulnerabilities/CVE-2019-18874/38087",
            "specs": [
                "<2.8.2"
            ],
            "v": "<2.8.2"
        }
    ],
    "sagemaker-python-sdk": [
        {
            "advisory": "sagemaker-python-sdk is a library for training and deploying machine learning models on Amazon SageMaker. In affected versions the capture_dependencies function in `sagemaker.serve.save_retrive.version_1_0_0.save.utils` module allows for potentially unsafe Operating System (OS) Command Injection if inappropriate command is passed as the \u201crequirements_path\u201d parameter. This consequently may allow an unprivileged third party to cause remote code execution, denial of service, affecting both confidentiality and integrity. This issue has been addressed in version 2.214.3. Users are advised to upgrade. Users unable to upgrade should not override the \u201crequirements_path\u201d parameter of capture_dependencies function in `sagemaker.serve.save_retrive.version_1_0_0.save.utils`, and instead use the default value. See CVE-2024-34073.",
            "cve": "CVE-2024-34073",
            "id": "pyup.io-71241",
            "more_info_path": "/vulnerabilities/CVE-2024-34073/71241",
            "specs": [
                "<2.214.3"
            ],
            "v": "<2.214.3"
        },
        {
            "advisory": "sagemaker-python-sdk is a library for training and deploying machine learning models on Amazon SageMaker. The sagemaker.base_deserializers.NumpyDeserializer module before v2.218.0 allows potentially unsafe deserialization when untrusted data is passed as pickled object arrays. This consequently may allow an unprivileged third party to cause remote code execution, denial of service, affecting both confidentiality and integrity. Users are advised to upgrade to version 2.218.0. Users unable to upgrade should not pass pickled numpy object arrays which originated from an untrusted source, or that could have been tampered with. Only pass pickled numpy object arrays from trusted sources.",
            "cve": "CVE-2024-34072",
            "id": "pyup.io-71632",
            "more_info_path": "/vulnerabilities/CVE-2024-34072/71632",
            "specs": [
                "<2.218.0"
            ],
            "v": "<2.218.0"
        }
    ],
    "sagemaker-pytorch-inference": [
        {
            "advisory": "Sagemaker-pytorch-inference 1.4.1 updates its dependency 'pillow' to v7.1.0 to include security fixes.",
            "cve": "CVE-2019-19911",
            "id": "pyup.io-45797",
            "more_info_path": "/vulnerabilities/CVE-2019-19911/45797",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        },
        {
            "advisory": "Sagemaker-pytorch-inference 1.4.1 updates its dependency 'pillow' to v7.1.0 to include security fixes.",
            "cve": "CVE-2020-11538",
            "id": "pyup.io-45792",
            "more_info_path": "/vulnerabilities/CVE-2020-11538/45792",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        },
        {
            "advisory": "Sagemaker-pytorch-inference 1.4.1 updates its dependency 'pillow' to v7.1.0 to include security fixes.",
            "cve": "CVE-2020-5313",
            "id": "pyup.io-45796",
            "more_info_path": "/vulnerabilities/CVE-2020-5313/45796",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        },
        {
            "advisory": "Sagemaker-pytorch-inference 1.4.1 updates its dependency 'pillow' to v7.1.0 to include security fixes.",
            "cve": "CVE-2020-5312",
            "id": "pyup.io-45795",
            "more_info_path": "/vulnerabilities/CVE-2020-5312/45795",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        },
        {
            "advisory": "Sagemaker-pytorch-inference 1.4.1 updates its dependency 'pillow' to v7.1.0 to include security fixes.",
            "cve": "CVE-2020-10994",
            "id": "pyup.io-40029",
            "more_info_path": "/vulnerabilities/CVE-2020-10994/40029",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        },
        {
            "advisory": "Sagemaker-pytorch-inference 1.4.1 updates its dependency 'pillow' to v7.1.0 to include security fixes.",
            "cve": "CVE-2020-5311",
            "id": "pyup.io-45794",
            "more_info_path": "/vulnerabilities/CVE-2020-5311/45794",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        },
        {
            "advisory": "Sagemaker-pytorch-inference 1.4.1 updates its dependency 'pillow' to v7.1.0 to include security fixes.",
            "cve": "CVE-2020-5310",
            "id": "pyup.io-45793",
            "more_info_path": "/vulnerabilities/CVE-2020-5310/45793",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        }
    ],
    "sagemaker-training": [
        {
            "advisory": "Sagemaker-training affected versions prior may inadvertently expose sensitive information in log files. The vulnerability stems from detailed logging of module installation commands, potentially revealing package names, versions, or custom flags that could include sensitive data. This exposure risk is particularly concerning if installation processes involve tokens or credentials. The patch removes verbose logging in the install and install_requirements functions, significantly reducing the risk of accidental information disclosure.",
            "cve": "PVE-2024-73184",
            "id": "pyup.io-73184",
            "more_info_path": "/vulnerabilities/PVE-2024-73184/73184",
            "specs": [
                ">=4.7.0,<4.8.0"
            ],
            "v": ">=4.7.0,<4.8.0"
        }
    ],
    "sagemath": [
        {
            "advisory": "SageMath FlintQS 1.0 relies on pathnames under TMPDIR (typically world-writable), which (for example) allows a local user to overwrite files with the privileges of a different user (who is running FlintQS).",
            "cve": "CVE-2023-29465",
            "id": "pyup.io-70902",
            "more_info_path": "/vulnerabilities/CVE-2023-29465/70902",
            "specs": [
                "<=1.0"
            ],
            "v": "<=1.0"
        }
    ],
    "saleor": [
        {
            "advisory": "In Saleor Storefront before version 2.10.3, request data used to authenticate customers was inadvertently cached in the browser's local storage mechanism, including credentials. A malicious user with direct access to the browser could extract the email and password. In versions prior to 2.10.0 persisted the cache even after the user logged out. This is fixed in version 2.10.3. A workaround is to manually clear application data (browser's local storage) after logging into Saleor Storefront.",
            "cve": "CVE-2020-15085",
            "id": "pyup.io-70595",
            "more_info_path": "/vulnerabilities/CVE-2020-15085/70595",
            "specs": [
                "<2.10.3"
            ],
            "v": "<2.10.3"
        },
        {
            "advisory": "Saleor Issue was introduced by merge commit: e1b01bad0703afd08d297ed3f1f472248312cc9c. This commit was released as part of 2.0.0 release is affected by: Incorrect Access Control. The impact is: Important. The component is: ProductVariant type in GraphQL API. The attack vector is: Unauthenticated user can access the GraphQL API (which is by default publicly exposed under `/graphql/` URL) and fetch products data which may include admin-restricted shop's revenue data. The fixed version is: 2.3.1.",
            "cve": "CVE-2019-1010304",
            "id": "pyup.io-70594",
            "more_info_path": "/vulnerabilities/CVE-2019-1010304/70594",
            "specs": [
                "<2.3.1"
            ],
            "v": "<2.3.1"
        },
        {
            "advisory": "Saleor 3.7.17, 3.6.18, 3.5.23, 3.4.24, 3.3.26, 3.2.14 and 3.1.24 include a fix for CVE-2022-39275: Improper object type validation in mutations leading to unauthorized access.\r\nSafe versions aren't in PyPi but on Saleor Github repository.\r\nhttps://github.com/saleor/saleor/security/advisories/GHSA-xhq8-8c5v-w8ff",
            "cve": "CVE-2022-39275",
            "id": "pyup.io-53540",
            "more_info_path": "/vulnerabilities/CVE-2022-39275/53540",
            "specs": [
                "<3.1.24",
                ">=3.2.0a0,<3.2.14",
                ">=3.3.0a0,<3.3.26",
                ">=3.4.0a0,<3.4.24",
                ">=3.5.0a0,<3.5.23",
                ">=3.6.0a0,<3.6.18",
                ">=3.7.0a0,<3.7.17"
            ],
            "v": "<3.1.24,>=3.2.0a0,<3.2.14,>=3.3.0a0,<3.3.26,>=3.4.0a0,<3.4.24,>=3.5.0a0,<3.5.23,>=3.6.0a0,<3.6.18,>=3.7.0a0,<3.7.17"
        },
        {
            "advisory": "Missing Authorization in GitHub repository saleor/saleor prior to 3.1.2.",
            "cve": "CVE-2022-0932",
            "id": "pyup.io-54411",
            "more_info_path": "/vulnerabilities/CVE-2022-0932/54411",
            "specs": [
                ">=0,<3.1.2"
            ],
            "v": ">=0,<3.1.2"
        },
        {
            "advisory": "An issue was discovered in Mirumee Saleor 2.x before 2.9.1. Incorrect access control in the checkoutCustomerAttach mutations allows attackers to attach their checkouts to any user ID and consequently leak user data (e.g., name, address, and previous orders of any other customer).",
            "cve": "CVE-2020-7964",
            "id": "pyup.io-54202",
            "more_info_path": "/vulnerabilities/CVE-2020-7964/54202",
            "specs": [
                ">=2.0.0,<2.9.1"
            ],
            "v": ">=2.0.0,<2.9.1"
        },
        {
            "advisory": "Saleor 3.1.48, 3.7.59, 3.8.30, 3.9.27, 3.10.14 and 3.11.12 include a fix for CVE-2023-26052: Some internal Python exceptions are not handled properly and thus are returned in API as error messages. Some messages might contain sensitive information like infrastructure details in unauthenticated requests.\r\nSafe versions aren't in PyPi but on Saleor Github repository.\r\nhttps://github.com/saleor/saleor/security/advisories/GHSA-3hvj-3cg9-v242",
            "cve": "CVE-2023-26052",
            "id": "pyup.io-53529",
            "more_info_path": "/vulnerabilities/CVE-2023-26052/53529",
            "specs": [
                ">=2.0.0,<3.1.48",
                ">=3.2.0a0,<3.7.59",
                ">=3.8.0a0,<3.8.30",
                ">=3.9.0a0,<3.9.27",
                ">=3.10.0a0,<3.10.14",
                ">=3.11.0a0,<3.11.12"
            ],
            "v": ">=2.0.0,<3.1.48,>=3.2.0a0,<3.7.59,>=3.8.0a0,<3.8.30,>=3.9.0a0,<3.9.27,>=3.10.0a0,<3.10.14,>=3.11.0a0,<3.11.12"
        },
        {
            "advisory": "Saleor 3.1.48, 3.7.59, 3.8.30, 3.9.27, 3.10.14 and 3.11.12 include a fix for CVE-2023-26051: Some internal Python exceptions are not handled properly and thus are returned in API as error messages. Some messages might contain sensitive information like user email address in staff-authenticated requests.\r\nSafe versions aren't in PyPi but on Saleor Github repository.\r\nhttps://github.com/saleor/saleor/security/advisories/GHSA-r8qr-wwg3-2r85",
            "cve": "CVE-2023-26051",
            "id": "pyup.io-53528",
            "more_info_path": "/vulnerabilities/CVE-2023-26051/53528",
            "specs": [
                ">=2.0.0,<3.1.48",
                ">=3.2.0a0,<3.7.59",
                ">=3.8.0a0,<3.8.30",
                ">=3.9.0a0,<3.9.27",
                ">=3.10.0a0,<3.10.14",
                ">=3.11.0a0,<3.11.12"
            ],
            "v": ">=2.0.0,<3.1.48,>=3.2.0a0,<3.7.59,>=3.8.0a0,<3.8.30,>=3.9.0a0,<3.9.27,>=3.10.0a0,<3.10.14,>=3.11.0a0,<3.11.12"
        },
        {
            "advisory": "Saleor Core is a composable, headless commerce API. Saleor's `validate_hmac_signature` function is vulnerable to timing attacks. Malicious users could abuse this vulnerability on Saleor deployments having the Adyen plugin enabled in order to determine the secret key and forge fake events, this could affect the database integrity such as marking an order as paid when it is not. This issue has been patched in versions 3.7.68, 3.8.40, 3.9.49, 3.10.36, 3.11.35, 3.12.25, and 3.13.16.",
            "cve": "CVE-2023-32694",
            "id": "pyup.io-64196",
            "more_info_path": "/vulnerabilities/CVE-2023-32694/64196",
            "specs": [
                ">=2.11.0,<3.7.68",
                ">=3.10.0,<3.10.36",
                ">=3.11.0,<3.11.35",
                ">=3.12.0,<3.12.25",
                ">=3.13.0,<3.13.16",
                ">=3.8.0,<3.8.40",
                ">=3.9.0,<3.9.49"
            ],
            "v": ">=2.11.0,<3.7.68,>=3.10.0,<3.10.36,>=3.11.0,<3.11.35,>=3.12.0,<3.12.25,>=3.13.0,<3.13.16,>=3.8.0,<3.8.40,>=3.9.0,<3.9.49"
        },
        {
            "advisory": "In Mirumee Saleor 2.7.0 (fixed in 2.8.0), CSRF protection middleware was accidentally disabled, which allowed attackers to send a POST request without a valid CSRF token and be accepted by the server.",
            "cve": "CVE-2019-13594",
            "id": "pyup.io-70563",
            "more_info_path": "/vulnerabilities/CVE-2019-13594/70563",
            "specs": [
                ">=2.7.0,<2.8.0"
            ],
            "v": ">=2.7.0,<2.8.0"
        },
        {
            "advisory": "Saleor is an e-commerce platform that serves high-volume companies. When using `Pickup: Local stock only` click-and-collect as a delivery method in specific conditions the customer could overwrite the warehouse address with its own, which exposes its address as click-and-collect address.",
            "cve": "CVE-2024-29888",
            "id": "pyup.io-71943",
            "more_info_path": "/vulnerabilities/CVE-2024-29888/71943",
            "specs": [
                ">=3.14.56,<3.14.61",
                ">=3.15.31,<3.15.37",
                ">=3.16.27,<3.16.34",
                ">=3.17.25,<3.17.32",
                ">=3.18.19,<3.18.28",
                ">=3.19.5,<3.19.15"
            ],
            "v": ">=3.14.56,<3.14.61,>=3.15.31,<3.15.37,>=3.16.27,<3.16.34,>=3.17.25,<3.17.32,>=3.18.19,<3.18.28,>=3.19.5,<3.19.15"
        }
    ],
    "salt": [
        {
            "advisory": "SaltStack RSA Key Generation allows remote users to decrypt communications",
            "cve": "CVE-2013-2228",
            "id": "pyup.io-67957",
            "more_info_path": "/vulnerabilities/CVE-2013-2228/67957",
            "specs": [
                "<0.15.0"
            ],
            "v": "<0.15.0"
        },
        {
            "advisory": "In SaltStack Salt before 3002.5, authentication to VMware vcenter, vsphere, and esxi servers (in the vmware.py files) does not always validate the SSL/TLS certificate. Several Salt versions were patched. See: https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/",
            "cve": "CVE-2020-28972",
            "id": "pyup.io-41944",
            "more_info_path": "/vulnerabilities/CVE-2020-28972/41944",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "An issue was discovered in SaltStack Salt before 3002.5 identified as CVE-2021-25284: salt.modules.cmdmod can log credentials to the info or error log level.\r\nhttps://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25",
            "cve": "CVE-2021-25284",
            "id": "pyup.io-41949",
            "more_info_path": "/vulnerabilities/CVE-2021-25284/41949",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "In SaltStack Salt before 3002.5, when authenticating to services using certain modules, the SSL certificate is not always validated. Several Salt versions were patched. See: https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/",
            "cve": "CVE-2020-35662",
            "id": "pyup.io-41945",
            "more_info_path": "/vulnerabilities/CVE-2020-35662/41945",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "An issue was discovered in through SaltStack Salt before 3002.5. The jinja renderer does not protect against server side template injection attacks. Several Salt versions were patched. See: https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/",
            "cve": "CVE-2021-25283",
            "id": "pyup.io-41948",
            "more_info_path": "/vulnerabilities/CVE-2021-25283/41948",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "An issue was discovered in SaltStack Salt before 3002.5. The minion's restartcheck is vulnerable to command injection via a crafted process name. This allows for a local privilege escalation by any user able to create a files on the minion in a non-blacklisted directory. Several Salt versions were patched. \r\nhttps://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25",
            "cve": "CVE-2020-28243",
            "id": "pyup.io-41929",
            "more_info_path": "/vulnerabilities/CVE-2020-28243/41929",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. They might be used to run command against the salt master or minions. Several Salt versions were patched. See: https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/",
            "cve": "CVE-2021-3144",
            "id": "pyup.io-41950",
            "more_info_path": "/vulnerabilities/CVE-2021-3144/41950",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py. Several Salt versions were patched. See: https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/",
            "cve": "CVE-2021-3148",
            "id": "pyup.io-41951",
            "more_info_path": "/vulnerabilities/CVE-2021-3148/41951",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "Salt versions 3002.5, 3001.4, 3000.6, 2019.2.8, 2019.2.5, 2018.3.5, 2017.7.8, 2016.11.10, 2016.11.6, 2016.11.5, 2016.11.3, 2016.3.8, 2016.3.6, 2016.3.4, 2015.8.13 and 2015.8.10 include a fix for CVE-2021-3197: An issue was discovered in SaltStack Salt before 3002.5. The salt-api's ssh client is vulnerable to a shell injection by including ProxyCommand in an argument, or via ssh_options provided in an API request.\r\nhttps://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/",
            "cve": "CVE-2021-3197",
            "id": "pyup.io-41952",
            "more_info_path": "/vulnerabilities/CVE-2021-3197/41952",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "An issue was discovered in through SaltStack Salt before 3002.5, identified as CVE-2021-25282: The salt.wheel.pillar_roots.write method is vulnerable to directory traversal. Several Salt versions were patched. https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25",
            "cve": "CVE-2021-25282",
            "id": "pyup.io-41947",
            "more_info_path": "/vulnerabilities/CVE-2021-25282/41947",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "An issue was discovered in through SaltStack Salt before 3002.5. Salt-api does not honor eauth credentials for the wheel_async client. Thus, an attacker can remotely run any wheel modules on the master. Several Salt versions were patched. See: https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/",
            "cve": "CVE-2021-25281",
            "id": "pyup.io-41946",
            "more_info_path": "/vulnerabilities/CVE-2021-25281/41946",
            "specs": [
                "<2015.8.10",
                ">=2015.8.11,<2015.8.13",
                ">=2016.3.0rc0,<2016.3.4",
                "==2016.3.5",
                "==2016.3.7",
                ">=2016.3.9,<2016.11.3",
                "==2016.11.4",
                ">=2016.11.7,<2016.11.10",
                ">=2017.5.0,<2017.7.8",
                ">=2018.2.0,<=2018.3.5",
                ">=2019.2.0rc0,<2019.2.5",
                ">=2019.2.6,<2019.2.8",
                ">=3000.0.0rc0,<3000.6",
                ">=3001rc1,<3001.4",
                ">=3002rc0,<3002.5"
            ],
            "v": "<2015.8.10,>=2015.8.11,<2015.8.13,>=2016.3.0rc0,<2016.3.4,==2016.3.5,==2016.3.7,>=2016.3.9,<2016.11.3,==2016.11.4,>=2016.11.7,<2016.11.10,>=2017.5.0,<2017.7.8,>=2018.2.0,<=2018.3.5,>=2019.2.0rc0,<2019.2.5,>=2019.2.6,<2019.2.8,>=3000.0.0rc0,<3000.6,>=3001rc1,<3001.4,>=3002rc0,<3002.5"
        },
        {
            "advisory": "Salt 3000.4 prevents creating world-readable private keys with the TLS execution module (cve-2020-17490).",
            "cve": "CVE-2020-17490",
            "id": "pyup.io-39574",
            "more_info_path": "/vulnerabilities/CVE-2020-17490/39574",
            "specs": [
                "<3000.4"
            ],
            "v": "<3000.4"
        },
        {
            "advisory": "Salt 3001.1 updates PyYAML for security reasons. Additionally, psutil was updated due to CVE-2019-18874.",
            "cve": "CVE-2019-18874",
            "id": "pyup.io-38668",
            "more_info_path": "/vulnerabilities/CVE-2019-18874/38668",
            "specs": [
                "<3001.1"
            ],
            "v": "<3001.1"
        },
        {
            "advisory": "Salt 3003.3, 3002.7 and 3001.8 include a fix for CVE-2021-21996: An issue was discovered in SaltStack Salt before 3003.3. A user who has control of the source, and source_hash URLs can gain full file system access as root on a salt minion.\r\nhttps://saltproject.io/security_announcements/salt-security-advisory-2021-sep-02/",
            "cve": "CVE-2021-21996",
            "id": "pyup.io-41953",
            "more_info_path": "/vulnerabilities/CVE-2021-21996/41953",
            "specs": [
                "<3001.8",
                ">3001.8,<3002.7",
                ">3002.7,<3003.3"
            ],
            "v": "<3001.8,>3001.8,<3002.7,>3002.7,<3003.3"
        },
        {
            "advisory": "An authentication flaw (CWE-287) has been discovered in SUSE Linux Enterprise Server 15 SP 3 and openSUSE Tumbleweed. This vulnerability allows local attackers to run arbitrary code through salt without requiring valid credentials. Affected are SUSE Linux Enterprise Server 15 SP 3 salt versions before 3002.2-3 and openSUSE Tumbleweed salt version 3002.2-2.1 and previous versions.",
            "cve": "CVE-2021-25315",
            "id": "pyup.io-62641",
            "more_info_path": "/vulnerabilities/CVE-2021-25315/62641",
            "specs": [
                "<3002.2"
            ],
            "v": "<3002.2"
        },
        {
            "advisory": "Salt versions 3002.7 and 3003.3 include a fix for CVE-2021-22004: An issue was discovered in SaltStack Salt before 3003.3. The salt minion installer will accept and use a minion config file at C:\\salt\\conf if that file is in place before the installer is run. This allows for a malicious actor to subvert the proper behaviour of the given minion software.",
            "cve": "CVE-2021-22004",
            "id": "pyup.io-41922",
            "more_info_path": "/vulnerabilities/CVE-2021-22004/41922",
            "specs": [
                "<3002.7",
                ">3002.7,<3003.3"
            ],
            "v": "<3002.7,>3002.7,<3003.3"
        },
        {
            "advisory": "Salt 3002.8, 3003.4 and 3004.1 include a fix for CVE-2022-22941: When configured as a Master-of-Masters, with a publisher_acl, if a user configured in the publisher_acl targets any minion connected to the Syndic, the Salt Master incorrectly interpreted no valid targets as valid, allowing configured users to target any of the minions connected to the syndic with their configured commands. This requires a syndic master combined with publisher_acl configured on the Master-of-Masters, allowing users specified in the publisher_acl to bypass permissions, publishing authorized commands to any configured minion.",
            "cve": "CVE-2022-22941",
            "id": "pyup.io-49628",
            "more_info_path": "/vulnerabilities/CVE-2022-22941/49628",
            "specs": [
                "<3002.8",
                ">=3003rc0,<3003.4",
                ">=3004rc0,<3004.1"
            ],
            "v": "<3002.8,>=3003rc0,<3003.4,>=3004rc0,<3004.1"
        },
        {
            "advisory": "Salt 3002.8, 3003.4 and 3004.1 include a fix for CVE-2022-22936: Job publishes and file server replies are susceptible to replay attacks, which can result in an attacker replaying job publishes causing minions to run old jobs. File server replies can also be re-played. A sufficient craft attacker could gain root access on minion under certain scenarios.",
            "cve": "CVE-2022-22936",
            "id": "pyup.io-49627",
            "more_info_path": "/vulnerabilities/CVE-2022-22936/49627",
            "specs": [
                "<3002.8",
                ">=3003rc0,<3003.4",
                ">=3004rc0,<3004.1"
            ],
            "v": "<3002.8,>=3003rc0,<3003.4,>=3004rc0,<3004.1"
        },
        {
            "advisory": "Salt 3002.8, 3003.4 and 3004.1 include a fix for CVE-2022-22935: A minion authentication denial of service can cause a MITM attacker to force a minion process to stop by impersonating a master.",
            "cve": "CVE-2022-22935",
            "id": "pyup.io-49626",
            "more_info_path": "/vulnerabilities/CVE-2022-22935/49626",
            "specs": [
                "<3002.8",
                ">=3003rc0,<3003.4",
                ">=3004rc0,<3004.1"
            ],
            "v": "<3002.8,>=3003rc0,<3003.4,>=3004rc0,<3004.1"
        },
        {
            "advisory": "Salt 3002.8, 3003.4 and 3004.1 include a fix for CVE-2022-22934: Salt Masters do not sign pillar data with the minion\u2019s public key, which can result in attackers substituting arbitrary pillar data.",
            "cve": "CVE-2022-22934",
            "id": "pyup.io-49570",
            "more_info_path": "/vulnerabilities/CVE-2022-22934/49570",
            "specs": [
                "<3002.8",
                ">=3003rc0,<3003.4",
                ">=3004rc0,<3004.1"
            ],
            "v": "<3002.8,>=3003rc0,<3003.4,>=3004rc0,<3004.1"
        },
        {
            "advisory": "Salt 3002.9, 3003.5 and 3004.2 include a fix for CVE-2022-22967: PAM auth fails to reject locked accounts, which allows a previously authorized user whose account is locked still run Salt commands when their account is locked. This affects both local shell accounts with an active session and salt-api users that authenticate via PAM eauth.",
            "cve": "CVE-2022-22967",
            "id": "pyup.io-50224",
            "more_info_path": "/vulnerabilities/CVE-2022-22967/50224",
            "specs": [
                "<3002.9",
                ">=3003rc1,<3003.5",
                ">=3004rc1,<3004.2"
            ],
            "v": "<3002.9,>=3003rc1,<3003.5,>=3004rc1,<3004.2"
        },
        {
            "advisory": "Salt 3003.2 updates its dependency \"ipaddress\" to 3.9.5 to include security fixes.",
            "cve": "CVE-2021-29921",
            "id": "pyup.io-41921",
            "more_info_path": "/vulnerabilities/CVE-2021-29921/41921",
            "specs": [
                "<3003.2"
            ],
            "v": "<3003.2"
        },
        {
            "advisory": "Salt 3004.1 and 3003.4 fix a denial of service vulnerability in junos ifconfig output parsing.\r\nhttps://github.com/saltstack/salt/commit/76215a6242834ecdcc9e498dd61e9d1702facb49",
            "cve": "PVE-2022-49629",
            "id": "pyup.io-49629",
            "more_info_path": "/vulnerabilities/PVE-2022-49629/49629",
            "specs": [
                "<3003.4",
                ">=3004rc1,<3004.1"
            ],
            "v": "<3003.4,>=3004rc1,<3004.1"
        },
        {
            "advisory": "Salt masters prior to 3005.2 or 3006.2 contain a DOS in minion return. After receiving several bad packets on the request server equal to the number of worker threads, the master will become unresponsive to return requests until restarted.",
            "cve": "CVE-2023-20897",
            "id": "pyup.io-61043",
            "more_info_path": "/vulnerabilities/CVE-2023-20897/61043",
            "specs": [
                "<3005.2",
                ">=3006.0rc1,<3006.2"
            ],
            "v": "<3005.2,>=3006.0rc1,<3006.2"
        },
        {
            "advisory": "Salt 3005.2 and 3006.2 update its dependency 'cryptography' to v41.0.3 to include security fixes.",
            "cve": "CVE-2023-3446",
            "id": "pyup.io-61047",
            "more_info_path": "/vulnerabilities/CVE-2023-3446/61047",
            "specs": [
                "<3005.2",
                ">=3006.0rc1,<3006.2"
            ],
            "v": "<3005.2,>=3006.0rc1,<3006.2"
        },
        {
            "advisory": "Salt 3005.2 and 3006.2 update its dependency 'certifi' to v2023.07.22 to include a security fix.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-61048",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/61048",
            "specs": [
                "<3005.2",
                ">=3006.0rc1,<3006.2"
            ],
            "v": "<3005.2,>=3006.0rc1,<3006.2"
        },
        {
            "advisory": "Salt 3005.2 and 3006.2 include a fix for CVE-2023-20898: Git Providers can read from the wrong environment because they get the same cache directory base name in Salt masters prior to 3005.2 or 3006.2. Anything that uses Git Providers with different environments can get garbage data or the wrong data, which can lead to wrongful data disclosure, wrongful executions, data corruption and/or crash.\r\nhttps://saltproject.io/security-announcements/2023-08-10-advisory",
            "cve": "CVE-2023-20898",
            "id": "pyup.io-61045",
            "more_info_path": "/vulnerabilities/CVE-2023-20898/61045",
            "specs": [
                "<3005.2",
                ">=3006.0rc1,<3006.2"
            ],
            "v": "<3005.2,>=3006.0rc1,<3006.2"
        },
        {
            "advisory": "Salt 3005.2 and 3006.2 update its dependency 'requests' to v2.31.0 to include a security fix.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-61046",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/61046",
            "specs": [
                "<3005.2",
                ">=3006.0rc1,<3006.2"
            ],
            "v": "<3005.2,>=3006.0rc1,<3006.2"
        },
        {
            "advisory": "Salt 3005.3 updates gitpython to >=3.1.35 due to https://github.com/advisories/GHSA-wfm5-v35h-vwf4 and https://github.com/advisories/GHSA-cwvm-v4w8-q58c (#65167)",
            "cve": "PVE-2023-62053",
            "id": "pyup.io-62053",
            "more_info_path": "/vulnerabilities/PVE-2023-62053/62053",
            "specs": [
                "<3005.3"
            ],
            "v": "<3005.3"
        },
        {
            "advisory": "Salt 3005.4 fixes CVE2023-34049 to avoid impacting salt-ssg users using the pre-flight option and upgrades dependencies affected by vulnerabilities.\r\nhttps://github.com/saltstack/salt/commit/8ed7bad4f8b9439ad2fbb86a22d120fb2fa592ce\r\nhttps://github.com/saltstack/salt/blob/master/CHANGELOG.md#30054-2023-10-16",
            "cve": "PVE-2023-62825",
            "id": "pyup.io-62825",
            "more_info_path": "/vulnerabilities/PVE-2023-62825/62825",
            "specs": [
                "<3005.4"
            ],
            "v": "<3005.4"
        },
        {
            "advisory": "Affected versions of Salt are vulnerable to a Path Traversal vulnerability. A specially crafted URL can be created which leads to a directory traversal in the salt file server. A malicious user can read an arbitrary file from a Salt master\u2019s filesystem.",
            "cve": "CVE-2024-22232",
            "id": "pyup.io-65958",
            "more_info_path": "/vulnerabilities/CVE-2024-22232/65958",
            "specs": [
                "<3005.5",
                ">=3006.0rc1,<3006.6"
            ],
            "v": "<3005.5,>=3006.0rc1,<3006.6"
        },
        {
            "advisory": "Syndic cache directory creation is vulnerable to a directory traversal attack in salt project which can lead a malicious attacker to create an arbitrary directory on a Salt master.",
            "cve": "CVE-2024-22231",
            "id": "pyup.io-65902",
            "more_info_path": "/vulnerabilities/CVE-2024-22231/65902",
            "specs": [
                "<3005.5",
                ">=3006.0rc1,<3006.6"
            ],
            "v": "<3005.5,>=3006.0rc1,<3006.6"
        },
        {
            "advisory": "Salt 3006.0rc3 updates its dependency 'cryptography' to versions '>=39.0.1' to include security fixes.",
            "cve": "CVE-2023-23931",
            "id": "pyup.io-55067",
            "more_info_path": "/vulnerabilities/CVE-2023-23931/55067",
            "specs": [
                "<3006.0rc3"
            ],
            "v": "<3006.0rc3"
        },
        {
            "advisory": "Salt 3006.0rc3 updates its dependency 'markdown-it-py' to v2.2.0 to include security fixes.",
            "cve": "CVE-2023-26302",
            "id": "pyup.io-55068",
            "more_info_path": "/vulnerabilities/CVE-2023-26302/55068",
            "specs": [
                "<3006.0rc3"
            ],
            "v": "<3006.0rc3"
        },
        {
            "advisory": "Salt 3006.0rc3 updates its dependency 'markdown-it-py' to v2.2.0 to include security fixes.",
            "cve": "CVE-2023-26303",
            "id": "pyup.io-55069",
            "more_info_path": "/vulnerabilities/CVE-2023-26303/55069",
            "specs": [
                "<3006.0rc3"
            ],
            "v": "<3006.0rc3"
        },
        {
            "advisory": "Salt 3006.0rc3 updates its dependency 'cryptography' to versions '>=39.0.1' to include security fixes.",
            "cve": "CVE-2023-0286",
            "id": "pyup.io-55066",
            "more_info_path": "/vulnerabilities/CVE-2023-0286/55066",
            "specs": [
                "<3006.0rc3"
            ],
            "v": "<3006.0rc3"
        },
        {
            "advisory": "Salt 3006.4 fixes CVE-2023-34049 to avoid impacting salt-ssg users using the pre-flight option and upgrades dependencies affected by vulnerabilities.\r\nhttps://github.com/saltstack/salt/commit/7a14112f2a16ce70e3c3e1862c92e37af5f2c7a4\r\nhttps://github.com/saltstack/salt/blob/master/CHANGELOG.md#30064-2023-10-16",
            "cve": "PVE-2023-62824",
            "id": "pyup.io-62824",
            "more_info_path": "/vulnerabilities/PVE-2023-62824/62824",
            "specs": [
                "<3006.4"
            ],
            "v": "<3006.4"
        },
        {
            "advisory": "Salt 3006.6 upgrades its pycryptodome library to version 3.19.1 as a security measure in response to CVE-2023-52323.",
            "cve": "CVE-2023-52323",
            "id": "pyup.io-65901",
            "more_info_path": "/vulnerabilities/CVE-2023-52323/65901",
            "specs": [
                "<3006.6"
            ],
            "v": "<3006.6"
        },
        {
            "advisory": "Salt 3006.6 upgrades its gitpython library to version 3.1.41 as a security measure in response to CVE-2024-22190.",
            "cve": "CVE-2024-22190",
            "id": "pyup.io-65956",
            "more_info_path": "/vulnerabilities/CVE-2024-22190/65956",
            "specs": [
                "<3006.6"
            ],
            "v": "<3006.6"
        },
        {
            "advisory": "Salt 3006.6 upgrades its jinja2 library to version 3.1.3 as a security measure in response to CVE-2023-52323.",
            "cve": "CVE-2024-22195",
            "id": "pyup.io-65957",
            "more_info_path": "/vulnerabilities/CVE-2024-22195/65957",
            "specs": [
                "<3006.6"
            ],
            "v": "<3006.6"
        },
        {
            "advisory": "Salt version 3006.7 upgrades its cryptography library to version 42.0.3 as a security measure in response to CVE-2023-50782.",
            "cve": "CVE-2023-50782",
            "id": "pyup.io-65900",
            "more_info_path": "/vulnerabilities/CVE-2023-50782/65900",
            "specs": [
                "<3006.7"
            ],
            "v": "<3006.7"
        },
        {
            "advisory": "Salt version 3006.8 upgrades its cryptography dependency to version 42.0.5 to address several security issues, including CVE-2024-26130.",
            "cve": "PVE-2024-71128",
            "id": "pyup.io-71128",
            "more_info_path": "/vulnerabilities/PVE-2024-71128/71128",
            "specs": [
                "<3006.8"
            ],
            "v": "<3006.8"
        },
        {
            "advisory": "Salt version 3006.8 upgrades its cryptography dependency to version 42.0.5 to address several security issues, including  CVE-2024-0727.",
            "cve": "CVE-2024-0727",
            "id": "pyup.io-71143",
            "more_info_path": "/vulnerabilities/CVE-2024-0727/71143",
            "specs": [
                "<3006.8"
            ],
            "v": "<3006.8"
        },
        {
            "advisory": "Salt version 3006.8 updates its aiohttp dependency to version 3.9.4 to address the security vulnerability identified as CVE-2024-27306.",
            "cve": "CVE-2024-27306",
            "id": "pyup.io-71145",
            "more_info_path": "/vulnerabilities/CVE-2024-27306/71145",
            "specs": [
                "<3006.8"
            ],
            "v": "<3006.8"
        },
        {
            "advisory": "Salt version 3006.8 updates its 'idna' dependency to version 3.7 to address the security vulnerability identified as CVE-2024-3651.",
            "cve": "CVE-2024-3651",
            "id": "pyup.io-71144",
            "more_info_path": "/vulnerabilities/CVE-2024-3651/71144",
            "specs": [
                "<3006.8"
            ],
            "v": "<3006.8"
        },
        {
            "advisory": "Salt version 3006.8 upgrades its cryptography dependency to version 42.0.5 to address several security issues, including CVE-2024-26130.",
            "cve": "CVE-2024-26130",
            "id": "pyup.io-71142",
            "more_info_path": "/vulnerabilities/CVE-2024-26130/71142",
            "specs": [
                "<3006.8"
            ],
            "v": "<3006.8"
        },
        {
            "advisory": "Salt bumps to werkzeug 3.0.3 due to the CVE-2024-34069.",
            "cve": "CVE-2024-34069",
            "id": "pyup.io-76007",
            "more_info_path": "/vulnerabilities/CVE-2024-34069/76007",
            "specs": [
                "<3006.9"
            ],
            "v": "<3006.9"
        },
        {
            "advisory": "Salt version 3007.0 updates its Tornado library to version 6.3.3 or higher in response to the security advisory GHSA-qppv-j76h-2rpx.",
            "cve": "PVE-2024-70600",
            "id": "pyup.io-70600",
            "more_info_path": "/vulnerabilities/PVE-2024-70600/70600",
            "specs": [
                "<3007.0"
            ],
            "v": "<3007.0"
        },
        {
            "advisory": "Salt version 3007.0rc1 has updated its GitPython dependency to version 3.1.35 or higher in response to CVE-2023-41040\r\nhttps://github.com/saltstack/salt/pull/65137/commits/aaf493adba19ab96c5985eba6d8d471dd011115d",
            "cve": "CVE-2023-41040",
            "id": "pyup.io-65952",
            "more_info_path": "/vulnerabilities/CVE-2023-41040/65952",
            "specs": [
                "<3007.0rc1"
            ],
            "v": "<3007.0rc1"
        },
        {
            "advisory": "Salt version 3007.0rc1 has updated its GitPython dependency to version 3.1.35 or higher in response to CVE-2023-40590\r\nhttps://github.com/saltstack/salt/pull/65137/commits/aaf493adba19ab96c5985eba6d8d471dd011115d",
            "cve": "CVE-2023-40590",
            "id": "pyup.io-65951",
            "more_info_path": "/vulnerabilities/CVE-2023-40590/65951",
            "specs": [
                "<3007.0rc1"
            ],
            "v": "<3007.0rc1"
        },
        {
            "advisory": "In SaltStack Salt through 3002, salt-netapi improperly validates eauth credentials and tokens. A user can bypass authentication and invoke Salt SSH. See CVE-2020-25592.",
            "cve": "CVE-2020-25592",
            "id": "pyup.io-39571",
            "more_info_path": "/vulnerabilities/CVE-2020-25592/39571",
            "specs": [
                "<=3002"
            ],
            "v": "<=3002"
        },
        {
            "advisory": "Salt (aka SaltStack) before 0.15.0 through 0.17.0 allows remote authenticated minions to impersonate arbitrary minions via a crafted minion with a valid key.",
            "cve": "CVE-2013-4439",
            "id": "pyup.io-54060",
            "more_info_path": "/vulnerabilities/CVE-2013-4439/54060",
            "specs": [
                ">=0,<0.17.1"
            ],
            "v": ">=0,<0.17.1"
        },
        {
            "advisory": "Salt (aka SaltStack) before 0.17.1 allows remote attackers to execute arbitrary YAML code via unspecified vectors.  NOTE: the vendor states that this might not be a vulnerability because the YAML to be loaded has already been determined to be safe.",
            "cve": "CVE-2013-4438",
            "id": "pyup.io-54059",
            "more_info_path": "/vulnerabilities/CVE-2013-4438/54059",
            "specs": [
                ">=0,<0.17.1"
            ],
            "v": ">=0,<0.17.1"
        },
        {
            "advisory": "Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.",
            "cve": "CVE-2014-3563",
            "id": "pyup.io-54082",
            "more_info_path": "/vulnerabilities/CVE-2014-3563/54082",
            "specs": [
                ">=0,<2014.1.10"
            ],
            "v": ">=0,<2014.1.10"
        },
        {
            "advisory": "modules/serverdensity_device.py in SaltStack before 2014.7.4 does not properly handle files in /tmp.",
            "cve": "CVE-2015-1838",
            "id": "pyup.io-54098",
            "more_info_path": "/vulnerabilities/CVE-2015-1838/54098",
            "specs": [
                ">=0,<2014.7.4"
            ],
            "v": ">=0,<2014.7.4"
        },
        {
            "advisory": "modules/chef.py in SaltStack before 2014.7.4 does not properly handle files in /tmp.",
            "cve": "CVE-2015-1839",
            "id": "pyup.io-54099",
            "more_info_path": "/vulnerabilities/CVE-2015-1839/54099",
            "specs": [
                ">=0,<2014.7.4"
            ],
            "v": ">=0,<2014.7.4"
        },
        {
            "advisory": "Salt before 2014.7.6 does not verify certificates when connecting via the aliyun, proxmox, and splunk modules.",
            "cve": "CVE-2015-4017",
            "id": "pyup.io-54101",
            "more_info_path": "/vulnerabilities/CVE-2015-4017/54101",
            "specs": [
                ">=0,<2014.7.6"
            ],
            "v": ">=0,<2014.7.6"
        },
        {
            "advisory": "Salt before 2015.5.10 and 2015.8.x before 2015.8.8, when PAM external authentication is enabled, allows attackers to bypass the configured authentication service by passing an alternate service with a command sent to LocalClient.",
            "cve": "CVE-2016-3176",
            "id": "pyup.io-54116",
            "more_info_path": "/vulnerabilities/CVE-2016-3176/54116",
            "specs": [
                ">=0,<2015.5.10",
                ">=2015.8,<2015.8.8"
            ],
            "v": ">=0,<2015.5.10,>=2015.8,<2015.8.8"
        },
        {
            "advisory": "salt before 2015.5.5 leaks git usernames and passwords to the log.",
            "cve": "CVE-2015-6918",
            "id": "pyup.io-54105",
            "more_info_path": "/vulnerabilities/CVE-2015-6918/54105",
            "specs": [
                ">=0,<2015.5.5"
            ],
            "v": ">=0,<2015.5.5"
        },
        {
            "advisory": "Salt before 2015.8.11 allows deleted minions to read or write to minions with the same id, related to caching.",
            "cve": "CVE-2016-9639",
            "id": "pyup.io-54119",
            "more_info_path": "/vulnerabilities/CVE-2016-9639/54119",
            "specs": [
                ">=0,<2015.8.11"
            ],
            "v": ">=0,<2015.8.11"
        },
        {
            "advisory": "When using the local_batch client from salt-api in SaltStack Salt before 2015.8.13, 2016.3.x before 2016.3.5, and 2016.11.x before 2016.11.2, external authentication is not respected, enabling all authentication to be bypassed.",
            "cve": "CVE-2017-5192",
            "id": "pyup.io-53956",
            "more_info_path": "/vulnerabilities/CVE-2017-5192/53956",
            "specs": [
                ">=0,<2015.8.13",
                ">=2016.3,<2016.3.5",
                ">=2016.11,<2016.11.2"
            ],
            "v": ">=0,<2015.8.13,>=2016.3,<2016.3.5,>=2016.11,<2016.11.2"
        },
        {
            "advisory": "Salt-api in SaltStack Salt before 2015.8.13, 2016.3.x before 2016.3.5, and 2016.11.x before 2016.11.2 allows arbitrary command execution on a salt-master via Salt's ssh_client.",
            "cve": "CVE-2017-5200",
            "id": "pyup.io-53957",
            "more_info_path": "/vulnerabilities/CVE-2017-5200/53957",
            "specs": [
                ">=0,<2015.8.13",
                ">=2016.3,<2016.3.5",
                ">=2016.11,<2016.11.2"
            ],
            "v": ">=0,<2015.8.13,>=2016.3,<2016.3.5,>=2016.11,<2016.11.2"
        },
        {
            "advisory": "The state.sls function in Salt before 2015.8.3 uses weak permissions on the cache data, which allows local users to obtain sensitive information by reading the file.",
            "cve": "CVE-2015-8034",
            "id": "pyup.io-54107",
            "more_info_path": "/vulnerabilities/CVE-2015-8034/54107",
            "specs": [
                ">=0,<2015.8.3"
            ],
            "v": ">=0,<2015.8.3"
        },
        {
            "advisory": "Directory traversal vulnerability in minion id validation in SaltStack Salt before 2016.11.7 and 2017.7.x before 2017.7.1 allows remote minions with incorrect credentials to authenticate to a master via a crafted minion ID.",
            "cve": "CVE-2017-12791",
            "id": "pyup.io-53929",
            "more_info_path": "/vulnerabilities/CVE-2017-12791/53929",
            "specs": [
                ">=0,<2016.11.7",
                ">=2017.7,<2017.7.1"
            ],
            "v": ">=0,<2016.11.7,>=2017.7,<2017.7.1"
        },
        {
            "advisory": "In SaltStack Salt before 2016.3.6, compromised salt-minions can impersonate the salt-master.",
            "cve": "CVE-2017-7893",
            "id": "pyup.io-53963",
            "more_info_path": "/vulnerabilities/CVE-2017-7893/53963",
            "specs": [
                ">=0,<2016.3.6"
            ],
            "v": ">=0,<2016.3.6"
        },
        {
            "advisory": "SaltStack Salt before 2016.3.8, 2016.11.x before 2016.11.8, and 2017.7.x before 2017.7.2 allows remote attackers to cause a denial of service via a crafted authentication request.",
            "cve": "CVE-2017-14696",
            "id": "pyup.io-53937",
            "more_info_path": "/vulnerabilities/CVE-2017-14696/53937",
            "specs": [
                ">=0,<2016.3.8",
                ">=2016.11,<2016.11.8",
                ">=2017.7,<2017.7.2"
            ],
            "v": ">=0,<2016.3.8,>=2016.11,<2016.11.8,>=2017.7,<2017.7.2"
        },
        {
            "advisory": "Directory traversal vulnerability in minion id validation in SaltStack Salt before 2016.3.8, 2016.11.x before 2016.11.8, and 2017.7.x before 2017.7.2 allows remote minions with incorrect credentials to authenticate to a master via a crafted minion ID.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-12791.",
            "cve": "CVE-2017-14695",
            "id": "pyup.io-53936",
            "more_info_path": "/vulnerabilities/CVE-2017-14695/53936",
            "specs": [
                ">=0,<2016.3.8",
                ">=2016.11,<2016.11.8",
                ">=2017.7,<2017.7.2"
            ],
            "v": ">=0,<2016.3.8,>=2016.11,<2016.11.8,>=2017.7,<2017.7.2"
        },
        {
            "advisory": "Directory Traversal vulnerability in salt-api in SaltStack Salt before 2017.7.8 and 2018.3.x before 2018.3.3 allows remote attackers to determine which files exist on the server.",
            "cve": "CVE-2018-15750",
            "id": "pyup.io-54205",
            "more_info_path": "/vulnerabilities/CVE-2018-15750/54205",
            "specs": [
                ">=0,<2017.7.8",
                ">=2018.3.0,<2018.3.3"
            ],
            "v": ">=0,<2017.7.8,>=2018.3.0,<2018.3.3"
        },
        {
            "advisory": "SaltStack Salt 2018.3, 2019.2 is affected by: SQL Injection. The impact is: An attacker could escalate privileges on MySQL server deployed by cloud provider. It leads to RCE. The affected component is: The mysql.user_chpass function from the MySQL module for Salt. The attack vector is: specially crafted password string. The fixed version is: 2018.3.4.",
            "cve": "CVE-2019-1010259",
            "id": "pyup.io-54128",
            "more_info_path": "/vulnerabilities/CVE-2019-1010259/54128",
            "specs": [
                ">=0,<2018.3.4"
            ],
            "v": ">=0,<2018.3.4"
        },
        {
            "advisory": "In SaltStack Salt through 2019.2.0, the salt-api NET API with the ssh client enabled is vulnerable to command injection. This allows an unauthenticated attacker with network access to the API endpoint to execute arbitrary code on the salt-api host.",
            "cve": "CVE-2019-17361",
            "id": "pyup.io-54206",
            "more_info_path": "/vulnerabilities/CVE-2019-17361/54206",
            "specs": [
                ">=0,<2019.2.1"
            ],
            "v": ">=0,<2019.2.1"
        },
        {
            "advisory": "An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class allows access to some methods that improperly sanitize paths. These methods allow arbitrary directory access to authenticated users.",
            "cve": "CVE-2020-11652",
            "id": "pyup.io-54173",
            "more_info_path": "/vulnerabilities/CVE-2020-11652/54173",
            "specs": [
                ">=0,<2019.2.4",
                ">=3000,<3000.2"
            ],
            "v": ">=0,<2019.2.4,>=3000,<3000.2"
        },
        {
            "advisory": "An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class does not properly validate method calls. This allows a remote user to access some methods without authentication. These methods can be used to retrieve user tokens from the salt master and/or run arbitrary commands on salt minions.",
            "cve": "CVE-2020-11651",
            "id": "pyup.io-54437",
            "more_info_path": "/vulnerabilities/CVE-2020-11651/54437",
            "specs": [
                ">=0,<2019.2.4",
                ">=3000,<3000.2"
            ],
            "v": ">=0,<2019.2.4,>=3000,<3000.2"
        },
        {
            "advisory": "A vulnerability in Salt-SSH before 3005.4 and 3006.4 arises from the pre-flight option copying scripts to a target at a predictable path. This flaw enables an attacker with access to the target virtual machine (VM) and knowledge of the script's path to execute their own script under the privileges of the Salt-SSH user.",
            "cve": "CVE-2023-34049",
            "id": "pyup.io-66718",
            "more_info_path": "/vulnerabilities/CVE-2023-34049/66718",
            "specs": [
                ">=0,<3005.4",
                ">=3006.0rc1,<3006.4"
            ],
            "v": ">=0,<3005.4,>=3006.0rc1,<3006.4"
        },
        {
            "advisory": "The salt master in Salt (aka SaltStack) 0.11.0 through 0.17.0 does not properly drop group privileges, which makes it easier for remote attackers to gain privileges.",
            "cve": "CVE-2013-6617",
            "id": "pyup.io-54066",
            "more_info_path": "/vulnerabilities/CVE-2013-6617/54066",
            "specs": [
                ">=0.11.0,<0.17.1"
            ],
            "v": ">=0.11.0,<0.17.1"
        },
        {
            "advisory": "Salt (aka SaltStack) 0.15.0 through 0.17.0 allows remote authenticated users who are using external authentication or client ACL to execute restricted routines by embedding the routine in another routine.",
            "cve": "CVE-2013-4435",
            "id": "pyup.io-54061",
            "more_info_path": "/vulnerabilities/CVE-2013-4435/54061",
            "specs": [
                ">=0.15.0,<0.17.1"
            ],
            "v": ">=0.15.0,<0.17.1"
        },
        {
            "advisory": "Unspecified vulnerability in salt-ssh in Salt (aka SaltStack) 0.17.0 has unspecified impact and vectors related to \"insecure Usage of /tmp.\"",
            "cve": "CVE-2013-4437",
            "id": "pyup.io-54213",
            "more_info_path": "/vulnerabilities/CVE-2013-4437/54213",
            "specs": [
                ">=0.17.0,<0.17.1"
            ],
            "v": ">=0.17.0,<0.17.1"
        },
        {
            "advisory": "The default configuration for salt-ssh in Salt (aka SaltStack) 0.17.0 does not validate the SSH host key of requests, which allows remote attackers to have unspecified impact via a man-in-the-middle (MITM) attack.",
            "cve": "CVE-2013-4436",
            "id": "pyup.io-54058",
            "more_info_path": "/vulnerabilities/CVE-2013-4436/54058",
            "specs": [
                ">=0.17.0,<0.17.1"
            ],
            "v": ">=0.17.0,<0.17.1"
        },
        {
            "advisory": "win_useradd, salt-cloud and the Linode driver in salt 2015.5.x before 2015.5.6, and 2015.8.x before 2015.8.1 leak password information in debug logs.",
            "cve": "CVE-2015-6941",
            "id": "pyup.io-54106",
            "more_info_path": "/vulnerabilities/CVE-2015-6941/54106",
            "specs": [
                ">=2015.5,<2015.5.6",
                ">=2015.8,<2015.8.1"
            ],
            "v": ">=2015.5,<2015.5.6,>=2015.8,<2015.8.1"
        },
        {
            "advisory": "Salt 2015.8.x before 2015.8.4 does not properly handle clear messages on the minion, which allows man-in-the-middle attackers to execute arbitrary code by inserting packets into the minion-master data stream.",
            "cve": "CVE-2016-1866",
            "id": "pyup.io-54112",
            "more_info_path": "/vulnerabilities/CVE-2016-1866/54112",
            "specs": [
                ">=2015.8,<2015.8.4"
            ],
            "v": ">=2015.8,<2015.8.4"
        },
        {
            "advisory": "The salt-ssh minion code in SaltStack Salt 2016.11 before 2016.11.4 copied over configuration from the Salt Master without adjusting permissions, which might leak credentials to local attackers on configured minions (clients).",
            "cve": "CVE-2017-8109",
            "id": "pyup.io-53964",
            "more_info_path": "/vulnerabilities/CVE-2017-8109/53964",
            "specs": [
                ">=2016.11,<2016.11.4"
            ],
            "v": ">=2016.11,<2016.11.4"
        },
        {
            "advisory": "Salt 3002.7 includes a fix for CVE-2021-31607: In SaltStack Salt 2016.9 through 3002.6, a command injection vulnerability exists in the snapper module that allows for local privilege escalation on a minion. The attack requires that a file is created with a pathname that is backed up by snapper, and that the master calls the snapper.diff function (which executes popen unsafely).\r\nhttps://sec.stealthcopter.com/saltstack-snapper-minion-privledge-escaltion/",
            "cve": "CVE-2021-31607",
            "id": "pyup.io-41925",
            "more_info_path": "/vulnerabilities/CVE-2021-31607/41925",
            "specs": [
                ">=2016.9,<=3002.6"
            ],
            "v": ">=2016.9,<=3002.6"
        },
        {
            "advisory": "SaltStack Salt before 2017.7.8 and 2018.3.x before 2018.3.3 allow remote attackers to bypass authentication and execute arbitrary commands via salt-api(netapi).",
            "cve": "CVE-2018-15751",
            "id": "pyup.io-54009",
            "more_info_path": "/vulnerabilities/CVE-2018-15751/54009",
            "specs": [
                ">=2018.3.0,<2018.3.3",
                ">=0,<2017.7.8"
            ],
            "v": ">=2018.3.0,<2018.3.3,>=0,<2017.7.8"
        },
        {
            "advisory": "An issue was discovered in SaltStack Salt affected versions. With the SSH client enabled, sending crafted web requests to the Salt API can result in shell injection.",
            "cve": "CVE-2020-16846",
            "id": "pyup.io-39159",
            "more_info_path": "/vulnerabilities/CVE-2020-16846/39159",
            "specs": [
                ">=3002rc1,<3002.1",
                ">=3001rc1,<3001.2",
                "<3000.4"
            ],
            "v": ">=3002rc1,<3002.1,>=3001rc1,<3001.2,<3000.4"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Authorization Bypass due to insufficient access control validation in the minion event bus system. The event bus authorization mechanism fails to properly validate minion identity and permissions when processing event messages, leading to cross-minion command execution attacks.",
            "cve": "CVE-2025-22236",
            "id": "pyup.io-77731",
            "more_info_path": "/vulnerabilities/CVE-2025-22236/77731",
            "specs": [
                ">=3006.0rc1,<3006.12",
                ">=3007.0rc1,<3007.4"
            ],
            "v": ">=3006.0rc1,<3006.12,>=3007.0rc1,<3007.4"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Event Injection due to insufficient validation of event data in the _minion_event method. The Salt Master's event handling system fails to properly validate and sanitize events submitted by authorized minions before publishing them to the master's event bus, leading to arbitrary event injection attacks.",
            "cve": "CVE-2025-22239",
            "id": "pyup.io-77733",
            "more_info_path": "/vulnerabilities/CVE-2025-22239/77733",
            "specs": [
                ">=3006.0rc1,<3006.12",
                ">=3007.0rc1,<3007.4"
            ],
            "v": ">=3006.0rc1,<3006.12,>=3007.0rc1,<3007.4"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal due to insufficient path validation in the minion file cache creation process. The save_minions() function in the local_cache module fails to properly validate minion identifiers before using them to construct file paths, leading to arbitrary file creation or overwrite attacks outside the intended cache directory.",
            "cve": "CVE-2025-22238",
            "id": "pyup.io-77730",
            "more_info_path": "/vulnerabilities/CVE-2025-22238/77730",
            "specs": [
                ">=3006.0rc1,<3006.12",
                ">=3007.0rc1,<3007.4"
            ],
            "v": ">=3006.0rc1,<3006.12,>=3007.0rc1,<3007.4"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Authentication Bypass due to improper PKI authentication verification in the salt.auth.pki module. The PKI authentication mechanism fails to properly verify that callers possess the corresponding private key for their presented public certificate, leading to authentication bypass attacks.",
            "cve": "CVE-2024-38825",
            "id": "pyup.io-77735",
            "more_info_path": "/vulnerabilities/CVE-2024-38825/77735",
            "specs": [
                ">=3006.0rc1,<3006.12",
                ">=3007.0rc1,<3007.4"
            ],
            "v": ">=3006.0rc1,<3006.12,>=3007.0rc1,<3007.4"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Command Injection due to insufficient input validation in the on-demand pillar functionality. The pillar processing system fails to properly sanitize Git URL inputs provided by minions when dynamically fetching external pillar data, leading to arbitrary command execution on the Salt Master. An attacker with access to a minion key can exploit this vulnerability by crafting malicious Git URLs containing command injection payloads that are executed when the master processes the on-demand pillar request.",
            "cve": "CVE-2025-22237",
            "id": "pyup.io-77732",
            "more_info_path": "/vulnerabilities/CVE-2025-22237/77732",
            "specs": [
                ">=3006.0rc1,<3006.12",
                ">=3007.0rc1,<3007.4"
            ],
            "v": ">=3006.0rc1,<3006.12,>=3007.0rc1,<3007.4"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal due to insufficient input validation in the GitFS class. The find_file() method fails to properly validate the tgt_env parameter before using it with os.path.join() to construct file paths, leading to arbitrary directory creation or file deletion attacks. An attacker can exploit this vulnerability by providing malicious path traversal sequences in the tgt_env variable, allowing them to access or delete files outside the intended directory structure with the same privileges as the Salt Master process.",
            "cve": "CVE-2025-22240",
            "id": "pyup.io-77729",
            "more_info_path": "/vulnerabilities/CVE-2025-22240/77729",
            "specs": [
                ">=3006.0rc1,<3006.12",
                ">=3007.0rc1,<3007.4"
            ],
            "v": ">=3006.0rc1,<3006.12,>=3007.0rc1,<3007.4"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal due to insufficient input validation in the VirtKey class when processing on-demand pillar requests. The VirtKey class fails to properly validate user-controlled input when constructing paths to the PKI directory, leading to arbitrary file creation or overwrite attacks.",
            "cve": "CVE-2025-22241",
            "id": "pyup.io-77734",
            "more_info_path": "/vulnerabilities/CVE-2025-22241/77734",
            "specs": [
                ">=3007.0rc1,<3007.4",
                ">=3006.0rc1,<3006.12"
            ],
            "v": ">=3007.0rc1,<3007.4,>=3006.0rc1,<3006.12"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Path Traversal due to insufficient path validation in the recv_file method. The file receiving functionality fails to properly sanitize and validate file paths provided by minions before writing files to the master cache directory, leading to arbitrary file write attacks outside the intended cache location.",
            "cve": "CVE-2024-38824",
            "id": "pyup.io-77737",
            "more_info_path": "/vulnerabilities/CVE-2024-38824/77737",
            "specs": [
                ">=3007.0rc1,<3007.4",
                ">=3006.0rc1,<3006.12"
            ],
            "v": ">=3007.0rc1,<3007.4,>=3006.0rc1,<3006.12"
        },
        {
            "advisory": "Affected versions of this package are vulnerable to Denial of Service due to insufficient input validation in the pub_ret method exposed to all minions. The pub_ret method fails to properly sanitize the jid (Job ID) parameter before using it to construct file paths for read operations, leading to worker process denial of service attacks. An attacker with access to a valid minion key can exploit this vulnerability by providing malicious jid values that cause the master to attempt file read operations on problematic filesystem locations, such as pipe nodes in the /proc filesystem or other special files that will block indefinitely or consume excessive resources.",
            "cve": "CVE-2025-22242",
            "id": "pyup.io-77736",
            "more_info_path": "/vulnerabilities/CVE-2025-22242/77736",
            "specs": [
                ">=3007.0rc1,<3007.4",
                ">=3006.0rc1,<3006.12"
            ],
            "v": ">=3007.0rc1,<3007.4,>=3006.0rc1,<3006.12"
        }
    ],
    "salted": [
        {
            "advisory": "Salted 0.5.4 requires lxml version >= 4.6.2 as it fixes a vulnerability and works with Python 3.9.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-39320",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/39320",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        }
    ],
    "sample-helper-aws-appconfig": [
        {
            "advisory": "Sample-helper-aws-appconfig 2.1.2 updates its urllib3 dependency from version 1.26.18 to 1.26.19 to address security concerns such as CVE-2023-45803.",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-71622",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/71622",
            "specs": [
                "<2.1.2"
            ],
            "v": "<2.1.2"
        }
    ],
    "sanic": [
        {
            "advisory": "Sanic 0.5.1 addresses a vulnerability that allowed for directory traversal through improperly handled static file URIs. This issue, identified in the sanic/sanic/static.py file, made it possible for attackers to access arbitrary files on the server via URL encoding.",
            "cve": "PVE-2024-63561",
            "id": "pyup.io-63561",
            "more_info_path": "/vulnerabilities/PVE-2024-63561/63561",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Sanic version 0.8.0 fixes a vulnerability that allows users to inject code into redirected URLs.\r\nhttps://github.com/sanic-org/sanic/pull/1260",
            "cve": "PVE-2021-42108",
            "id": "pyup.io-42108",
            "more_info_path": "/vulnerabilities/PVE-2021-42108/42108",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        },
        {
            "advisory": "Sanic versions before 19.9.0 had unsafe default settings. From 19.9.0 onwards, proxy settings must be set manually and support for negative PROXIES_COUNT has been removed.\r\nhttps://github.com/sanic-org/sanic/pull/1638",
            "cve": "PVE-2021-42109",
            "id": "pyup.io-42109",
            "more_info_path": "/vulnerabilities/PVE-2021-42109/42109",
            "specs": [
                "<19.9.0"
            ],
            "v": "<19.9.0"
        },
        {
            "advisory": "Sanic 22.6.1, 21.12.2 and 20.12.7 include a fix for CVE-2022-35920: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').\r\nhttps://github.com/sanic-org/sanic/security/advisories/GHSA-8cw9-5hmv-77w6",
            "cve": "CVE-2022-35920",
            "id": "pyup.io-50438",
            "more_info_path": "/vulnerabilities/CVE-2022-35920/50438",
            "specs": [
                "<20.12.7",
                ">=21.3.0,<21.12.2",
                ">=22.3.0,<22.6.1"
            ],
            "v": "<20.12.7,>=21.3.0,<21.12.2,>=22.3.0,<22.6.1"
        },
        {
            "advisory": "Sanic before 0.5.1 allows reading arbitrary files with directory traversal, as demonstrated by the substring.",
            "cve": "CVE-2017-16762",
            "id": "pyup.io-53941",
            "more_info_path": "/vulnerabilities/CVE-2017-16762/53941",
            "specs": [
                ">=0,<0.5.1"
            ],
            "v": ">=0,<0.5.1"
        },
        {
            "advisory": "Sanic v20.12 officially supports Python versions 3.6, 3.7, 3.8, and 3.9. However, if you accidentally run it with version 3.10 (**which is not supported by Sanic 20.12**), your server is prone to crashing on an incoming web request.\r\nhttps://github.com/sanic-org/sanic/security/advisories/GHSA-7p79-6x2v-5h88",
            "cve": "PVE-2023-55191",
            "id": "pyup.io-55191",
            "more_info_path": "/vulnerabilities/PVE-2023-55191/55191",
            "specs": [
                ">=0.1.7,<20.12.6"
            ],
            "v": ">=0.1.7,<20.12.6"
        }
    ],
    "sanic-ext": [
        {
            "advisory": "The official compatibility of Sanic includes Python versions 3.6, 3.7, 3.8, and 3.9, but not version 3.10. Mistakenly running it with Python 3.10 can potentially cause your server to crash upon receiving a web request.",
            "cve": "PVE-2023-99923",
            "id": "pyup.io-61984",
            "more_info_path": "/vulnerabilities/PVE-2023-99923/61984",
            "specs": [
                ">=0.1.7,<20.12.6"
            ],
            "v": ">=0.1.7,<20.12.6"
        }
    ],
    "sanic-oauthlib": [
        {
            "advisory": "Sanic-oauthlib 0.5.0 mentions \"**Security bug** for access token via `#92`\". No other information was provided.",
            "cve": "PVE-2021-38524",
            "id": "pyup.io-38524",
            "more_info_path": "/vulnerabilities/PVE-2021-38524/38524",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        },
        {
            "advisory": "Sanic-oauthlib 0.9.1 improves security in a not further specified way.",
            "cve": "PVE-2021-37397",
            "id": "pyup.io-37397",
            "more_info_path": "/vulnerabilities/PVE-2021-37397/37397",
            "specs": [
                "<0.9.1"
            ],
            "v": "<0.9.1"
        }
    ],
    "sanic-security": [
        {
            "advisory": "Sanic-security version 0.6.8.1 updates its dependency \"cryptography\" to v3.3.2 to include a security fix.",
            "cve": "CVE-2020-36242",
            "id": "pyup.io-41803",
            "more_info_path": "/vulnerabilities/CVE-2020-36242/41803",
            "specs": [
                "<0.6.8.1"
            ],
            "v": "<0.6.8.1"
        },
        {
            "advisory": "Sanic-security 0.8.0 updates its dependency \"pillow\" to v8.1.1 to include security fixes.",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-42110",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/42110",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        },
        {
            "advisory": "Sanic-security 0.8.0 updates its dependency \"pillow\" to v8.1.1 to include security fixes.",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-42112",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/42112",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        },
        {
            "advisory": "Sanic-security 0.8.0 updates its dependency \"pillow\" to v8.1.1 to include security fixes.",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-42111",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/42111",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        },
        {
            "advisory": "Sanic-security 0.8.0 updates its dependency \"pillow\" to v8.1.1 to include security fixes.",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-42113",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/42113",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        },
        {
            "advisory": "Sanic-security 0.8.0 updates its dependency \"pillow\" to v8.1.1 to include security fixes.",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-42114",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/42114",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        }
    ],
    "sap-xssec": [
        {
            "advisory": "Sap-xssec 4.1.0 includes a fix for CVE-2023-50423: Versions <4.1.0 allow under certain conditions an escalation of privileges. On successful exploitation, an unauthenticated attacker can obtain arbitrary permissions within the application.",
            "cve": "CVE-2023-50423",
            "id": "pyup.io-62821",
            "more_info_path": "/vulnerabilities/CVE-2023-50423/62821",
            "specs": [
                "<4.1.0"
            ],
            "v": "<4.1.0"
        }
    ],
    "sapsan": [
        {
            "advisory": "Sapsan 0.4.0 includes updated requirements (notebook >= 6.4.3) that fixes security vulnerabilities.",
            "cve": "CVE-2021-32798",
            "id": "pyup.io-41230",
            "more_info_path": "/vulnerabilities/CVE-2021-32798/41230",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "saspy": [
        {
            "advisory": "Saspy version 3.7.3 has upgraded log4j.jar (included in the Java IOM client) to version 2.12 because version 1.2 raised flags on some security scans.",
            "cve": "PVE-2021-41098",
            "id": "pyup.io-41098",
            "more_info_path": "/vulnerabilities/PVE-2021-41098/41098",
            "specs": [
                "<3.7.3"
            ],
            "v": "<3.7.3"
        },
        {
            "advisory": "Saspy 4.4.1 includes a fix in the IOM access method.\r\nhttps://github.com/sassoftware/saspy/commit/227c824df1aca1b6023cf7a6f15f7b1028877a0d",
            "cve": "PVE-2022-52149",
            "id": "pyup.io-52149",
            "more_info_path": "/vulnerabilities/PVE-2022-52149/52149",
            "specs": [
                "<4.4.1"
            ],
            "v": "<4.4.1"
        }
    ],
    "satosa": [
        {
            "advisory": "Satosa 0.6.1 switches dependencies from 'pycrypto' to 'pycryptodome' for security reasons.",
            "cve": "CVE-2018-6594",
            "id": "pyup.io-34714",
            "more_info_path": "/vulnerabilities/CVE-2018-6594/34714",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        },
        {
            "advisory": "Satosa 6.1.0 includes a fix for CVE-2020-5390: Improper Verification of Cryptographic Signature in PySAML2.\r\nhttps://github.com/IdentityPython/SATOSA/commit/7f93dcf95ce7228844a1f6d8969eea2164052e5c\r\nhttps://github.com/advisories/GHSA-qf7v-8hj3-4xw7",
            "cve": "CVE-2020-5390",
            "id": "pyup.io-58996",
            "more_info_path": "/vulnerabilities/CVE-2020-5390/58996",
            "specs": [
                "<6.1.0"
            ],
            "v": "<6.1.0"
        },
        {
            "advisory": "Satosa 7.0.2 includes a fix for CVE-2021-21238: SAML XML Signature wrapping in PySAML2.\r\nhttps://github.com/IdentityPython/SATOSA/commit/21bdada3509c7d53db131a5f8944c563934ba290\r\nhttps://github.com/advisories/GHSA-f4g9-h89h-jgv9",
            "cve": "CVE-2021-21238",
            "id": "pyup.io-58992",
            "more_info_path": "/vulnerabilities/CVE-2021-21238/58992",
            "specs": [
                "<7.0.2"
            ],
            "v": "<7.0.2"
        },
        {
            "advisory": "Satosa 7.0.2 includes a fix for CVE-2021-21239: Improper Verification of Cryptographic Signature in PySAML2.\r\nhttps://github.com/IdentityPython/SATOSA/commit/21bdada3509c7d53db131a5f8944c563934ba290\r\nhttps://github.com/advisories/GHSA-5p3x-r448-pc62",
            "cve": "CVE-2021-21239",
            "id": "pyup.io-58997",
            "more_info_path": "/vulnerabilities/CVE-2021-21239/58997",
            "specs": [
                "<7.0.2"
            ],
            "v": "<7.0.2"
        }
    ],
    "saywh11222": [
        {
            "advisory": "The OpenSSF Package Analysis project has flagged the 'saywh11222' package on PyPI as malicious. This determination is based on the package's communication with a domain linked to malicious activities.",
            "cve": "PVE-2024-73492",
            "id": "pyup.io-73492",
            "more_info_path": "/vulnerabilities/PVE-2024-73492/73492",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "saywh222": [
        {
            "advisory": "The OpenSSF Package Analysis project has flagged the 'saywh222' package on PyPI as malicious. This determination is based on the package's communication with a domain linked to malicious activities.",
            "cve": "PVE-2024-73490",
            "id": "pyup.io-73490",
            "more_info_path": "/vulnerabilities/PVE-2024-73490/73490",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "saywhu": [
        {
            "advisory": "The OpenSSF Package Analysis project has flagged the 'saywhu' package on PyPI as malicious. This determination is based on the package's communication with a domain linked to malicious activities.",
            "cve": "PVE-2024-73491",
            "id": "pyup.io-73491",
            "more_info_path": "/vulnerabilities/PVE-2024-73491/73491",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "sbp": [
        {
            "advisory": "Sbp 2.4.2 updates its NPM dependency 'mocha' to fix a transitive vulnerability in 'growl' package.",
            "cve": "CVE-2017-16042",
            "id": "pyup.io-36695",
            "more_info_path": "/vulnerabilities/CVE-2017-16042/36695",
            "specs": [
                "<2.4.2"
            ],
            "v": "<2.4.2"
        },
        {
            "advisory": "Sbp v2.6.5 pins minor rev versions, security fix for requests - see: https://github.com/swift-nav/libsbp/pull/709",
            "cve": "PVE-2021-36662",
            "id": "pyup.io-36662",
            "more_info_path": "/vulnerabilities/PVE-2021-36662/36662",
            "specs": [
                "<2.6.5"
            ],
            "v": "<2.6.5"
        },
        {
            "advisory": "Sbp 2.7.0 updates requests to resolve security issue (https://github.com/swift-nav/libsbp/pull/708).",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-37937",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/37937",
            "specs": [
                "<2.7.0"
            ],
            "v": "<2.7.0"
        },
        {
            "advisory": "Sbp 3.1.1 fixes a JavaScript security warning. See: .",
            "cve": "PVE-2021-38393",
            "id": "pyup.io-38393",
            "more_info_path": "/vulnerabilities/PVE-2021-38393/38393",
            "specs": [
                "<2.8.0"
            ],
            "v": "<2.8.0"
        },
        {
            "advisory": "Sbp 2.8.0 updates its dependency 'minimist' to version '1.2.5' to include a fix for a Prototype Pollution vulnerability.\r\nhttps://github.com/swift-nav/libsbp/pull/791",
            "cve": "CVE-2020-7598",
            "id": "pyup.io-60389",
            "more_info_path": "/vulnerabilities/CVE-2020-7598/60389",
            "specs": [
                "<2.8.0"
            ],
            "v": "<2.8.0"
        }
    ],
    "sbpy": [
        {
            "advisory": "Sbpy now requires `astropy` version 5.3.3 or higher to mitigate CVE-2023-41334.",
            "cve": "CVE-2023-41334",
            "id": "pyup.io-72899",
            "more_info_path": "/vulnerabilities/CVE-2023-41334/72899",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        }
    ],
    "scalecodec": [
        {
            "advisory": "Scalecodec version 1.2.9 removes the py library from its dependencies to address the security vulnerability identified as CVE-2022-42969.",
            "cve": "CVE-2022-42969",
            "id": "pyup.io-71283",
            "more_info_path": "/vulnerabilities/CVE-2022-42969/71283",
            "specs": [
                "<1.2.9"
            ],
            "v": "<1.2.9"
        }
    ],
    "scalyr-agent-2": [
        {
            "advisory": "Scalyr-agent-2 version 2.1.10 includes a fix for CVE-2020-24715: The Scalyr Agent before 2.1.10 has Missing SSL Certificate Validation because, in some circumstances, native Python code is used that lacks a comparison of the hostname to commonName and subjectAltName.",
            "cve": "CVE-2020-24715",
            "id": "pyup.io-38807",
            "more_info_path": "/vulnerabilities/CVE-2020-24715/38807",
            "specs": [
                "<2.1.10"
            ],
            "v": "<2.1.10"
        },
        {
            "advisory": "The Scalyr Agent before 2.1.10 has Missing SSL Certificate Validation because, in some circumstances, the openssl binary is called without the -verify_hostname option.",
            "cve": "CVE-2020-24714",
            "id": "pyup.io-54218",
            "more_info_path": "/vulnerabilities/CVE-2020-24714/54218",
            "specs": [
                ">=0,<2.1.10"
            ],
            "v": ">=0,<2.1.10"
        }
    ],
    "scancode-toolkit": [
        {
            "advisory": "Scancode-toolkit 21.2.9 updates its dependency 'lxml' to v4.6.2 to include a security fix.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-48402",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/48402",
            "specs": [
                "<21.2.9"
            ],
            "v": "<21.2.9"
        },
        {
            "advisory": "Scancode-toolkit 21.3.30 updates its dependency 'pyyaml' to v5.4.1 to include security fixes.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-48440",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/48440",
            "specs": [
                "<21.3.30"
            ],
            "v": "<21.3.30"
        },
        {
            "advisory": "Scancode-toolkit 21.3.30 updates its dependency 'pyyaml' to v5.4.1 to include security fixes.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-48439",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/48439",
            "specs": [
                "<21.3.30"
            ],
            "v": "<21.3.30"
        },
        {
            "advisory": "Scancode-toolkit 21.3.30 updates its dependency 'urllib3' to v1.26.4 to include a security fix.",
            "cve": "CVE-2021-28363",
            "id": "pyup.io-48441",
            "more_info_path": "/vulnerabilities/CVE-2021-28363/48441",
            "specs": [
                "<21.3.30"
            ],
            "v": "<21.3.30"
        },
        {
            "advisory": "Scancode-toolkit 21.3.30 updates its dependency 'pyyaml' to v5.4.1 to include security fixes.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-48401",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/48401",
            "specs": [
                "<21.3.30"
            ],
            "v": "<21.3.30"
        },
        {
            "advisory": "Scancode-toolkit 21.6.7 updates its dependency 'pygments' to v2.9.0 to include security fixes.",
            "cve": "CVE-2021-20270",
            "id": "pyup.io-48400",
            "more_info_path": "/vulnerabilities/CVE-2021-20270/48400",
            "specs": [
                "<21.6.7"
            ],
            "v": "<21.6.7"
        },
        {
            "advisory": "Scancode-toolkit 21.6.7 updates its dependency 'pygments' to v2.9.0 to include security fixes.",
            "cve": "CVE-2021-27291",
            "id": "pyup.io-48442",
            "more_info_path": "/vulnerabilities/CVE-2021-27291/48442",
            "specs": [
                "<21.6.7"
            ],
            "v": "<21.6.7"
        },
        {
            "advisory": "Scancode-toolkit 21.6.7 updates its dependency 'jinja2' to v3.0.1 to include security fixes.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-48445",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/48445",
            "specs": [
                "<21.6.7"
            ],
            "v": "<21.6.7"
        },
        {
            "advisory": "Scancode-toolkit 21.6.7 updates its dependency 'lxml' to v4.6.3 to include a security fix.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-48443",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/48443",
            "specs": [
                "<21.6.7"
            ],
            "v": "<21.6.7"
        },
        {
            "advisory": "Scancode-toolkit 21.6.7 dropped its dependency 'pycryptodrome', as it was not longer used and imposed a security threat.",
            "cve": "CVE-2018-15560",
            "id": "pyup.io-48447",
            "more_info_path": "/vulnerabilities/CVE-2018-15560/48447",
            "specs": [
                "<21.6.7"
            ],
            "v": "<21.6.7"
        },
        {
            "advisory": "Scancode-toolkit 21.6.7 updates its dependency 'nltk' to v3.6.2 to include a security fix.",
            "cve": "CVE-2019-14751",
            "id": "pyup.io-48444",
            "more_info_path": "/vulnerabilities/CVE-2019-14751/48444",
            "specs": [
                "<21.6.7"
            ],
            "v": "<21.6.7"
        },
        {
            "advisory": "Scancode-toolkit 21.6.7 updates its dependency 'jinja2' to v3.0.1 to include security fixes.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-48446",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/48446",
            "specs": [
                "<21.6.7"
            ],
            "v": "<21.6.7"
        },
        {
            "advisory": "Scancode-toolkit 31.0.0b1 updates its dependency 'lxml' to 4.7.1 to include a security fix.",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-48584",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/48584",
            "specs": [
                "<31.0.0b1"
            ],
            "v": "<31.0.0b1"
        },
        {
            "advisory": "Scancode-toolkit 31.0.0b1 switches to a different PyPI parser to include a security fix.\r\nhttps://github.com/nexB/scancode-toolkit/commit/d06bbeae81c5d6e3727cbe86f8d6c3d299e2ca66",
            "cve": "CVE-2022-39280",
            "id": "pyup.io-48585",
            "more_info_path": "/vulnerabilities/CVE-2022-39280/48585",
            "specs": [
                "<31.0.0b1"
            ],
            "v": "<31.0.0b1"
        }
    ],
    "scancodeio": [
        {
            "advisory": "Scancodeio 32.5.1 includes a fix for a Command Injection vulnerability in the fetch process of the Docker image.\r\nhttps://github.com/nexB/scancode.io/security/advisories/GHSA-2ggp-cmvm-f62f",
            "cve": "CVE-2023-39523",
            "id": "pyup.io-60251",
            "more_info_path": "/vulnerabilities/CVE-2023-39523/60251",
            "specs": [
                "<32.5.1"
            ],
            "v": "<32.5.1"
        },
        {
            "advisory": "Scancodeio 32.5.2 includes a security fix: Reflected Cross-Site Scripting (XSS) in license endpoint.\r\nhttps://github.com/nexB/scancode.io/security/advisories/GHSA-6xcx-gx7r-rccj",
            "cve": "CVE-2023-40024",
            "id": "pyup.io-60379",
            "more_info_path": "/vulnerabilities/CVE-2023-40024/60379",
            "specs": [
                "<32.5.2"
            ],
            "v": "<32.5.2"
        },
        {
            "advisory": "Scancodeio 34.4.0 updates its dependency 'gunicorn' to v22.0.0 to include a security fix.",
            "cve": "CVE-2024-1135",
            "id": "pyup.io-68075",
            "more_info_path": "/vulnerabilities/CVE-2024-1135/68075",
            "specs": [
                "<34.4.0"
            ],
            "v": "<34.4.0"
        },
        {
            "advisory": "ScanCodeIO 34.8.1 upgrades Django to 5.1.1 and related dependencies for CVE-2024-45230.",
            "cve": "CVE-2024-45230",
            "id": "pyup.io-73075",
            "more_info_path": "/vulnerabilities/CVE-2024-45230/73075",
            "specs": [
                "<34.8.1"
            ],
            "v": "<34.8.1"
        },
        {
            "advisory": "ScanCodeIO 34.8.1 upgrades Django to 5.1.1 and related dependencies for CVE-2024-45231.",
            "cve": "CVE-2024-45231",
            "id": "pyup.io-73081",
            "more_info_path": "/vulnerabilities/CVE-2024-45231/73081",
            "specs": [
                "<34.8.1"
            ],
            "v": "<34.8.1"
        }
    ],
    "scandeval": [
        {
            "advisory": "Scandeval 12.3.0 enhances its outlines dependency to versions >=0.0.36,<0.1 to resolve a race condition encountered in NER dataset evaluations and integrates with the transformers library, replacing the previously hardcoded setup. This update streamlines integration and improves evaluation processes.\r\nhttps://github.com/ScandEval/ScandEval/commit/a1decdc084a924560823c62148fe7600f1b35f5a",
            "cve": "PVE-2024-66052",
            "id": "pyup.io-66052",
            "more_info_path": "/vulnerabilities/PVE-2024-66052/66052",
            "specs": [
                "<12.3.0"
            ],
            "v": "<12.3.0"
        }
    ],
    "scapy": [
        {
            "advisory": "Scapy 2.4.1 includes a fix for CVE-2019-1010142: Denial of Service. The impact is infinite loop, resource consumption and program unresponsive. The component affected component is '_RADIUSAttrPacketListField.getfield(self..)'. The attack vector is over the network or a malicious pcap.\r\nhttps://github.com/secdev/scapy/pull/1409/commits/0d7ae2b039f650a40e511d09eb961c782da025d9",
            "cve": "CVE-2019-1010142",
            "id": "pyup.io-37341",
            "more_info_path": "/vulnerabilities/CVE-2019-1010142/37341",
            "specs": [
                "<2.4.1"
            ],
            "v": "<2.4.1"
        },
        {
            "advisory": "Affected versions of the scapy package are vulnerable to Deserialization of Untrusted Data due to the session-loading feature deserializing gzip-compressed pickle files without validation. The load_session logic in scapy/main.py invokes pickle.load() on a user-provided .pkl.gz specified via the -s command-line option (or conf.session) without restricting object types, allowing attacker-controlled __reduce__() methods to execute during deserialization.",
            "cve": "PVE-2025-80587",
            "id": "pyup.io-80587",
            "more_info_path": "/vulnerabilities/PVE-2025-80587/80587",
            "specs": [
                "<=2.6.1"
            ],
            "v": "<=2.6.1"
        }
    ],
    "scarletio": [
        {
            "advisory": "Scarletio 1.0.33 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/HuyaneMatsu/scarletio/commit/9a1498a96cd5def8ad668ac76f1049df1329fd38",
            "cve": "PVE-2023-60055",
            "id": "pyup.io-60055",
            "more_info_path": "/vulnerabilities/PVE-2023-60055/60055",
            "specs": [
                "<1.0.33"
            ],
            "v": "<1.0.33"
        }
    ],
    "scenepic": [
        {
            "advisory": "Scenepic 1.0.8 updates its NPM dependency 'minimist' to v1.2.6 to include a security fix.",
            "cve": "CVE-2021-44906",
            "id": "pyup.io-49757",
            "more_info_path": "/vulnerabilities/CVE-2021-44906/49757",
            "specs": [
                "<1.0.8"
            ],
            "v": "<1.0.8"
        }
    ],
    "sceptre": [
        {
            "advisory": "Sceptre 2.3.0 fixes a XSS vulnerability.\r\nhttps://github.com/Sceptre/sceptre/commit/6d4124bdc9d4d5277c3f5cdc5eb7d6db9696b667",
            "cve": "PVE-2021-37821",
            "id": "pyup.io-37821",
            "more_info_path": "/vulnerabilities/PVE-2021-37821/37821",
            "specs": [
                "<2.3.0"
            ],
            "v": "<2.3.0"
        },
        {
            "advisory": "Sceptre 3.3.0 updates its dependency 'setuptools' to v65.5.1 to include a security fix.",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-53273",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/53273",
            "specs": [
                "<3.3.0"
            ],
            "v": "<3.3.0"
        },
        {
            "advisory": "Sceptre 3.3.0 updates its dependency 'wheel' to v0.38.1 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-53270",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/53270",
            "specs": [
                "<3.3.0"
            ],
            "v": "<3.3.0"
        }
    ],
    "schema-salad": [
        {
            "advisory": "Schema-salad 8.3.20221209165047 stops using its NPM dependency 'mistune' 0.8.x for HTML generation to avoid a vulnerability.",
            "cve": "CVE-2022-34749",
            "id": "pyup.io-52752",
            "more_info_path": "/vulnerabilities/CVE-2022-34749/52752",
            "specs": [
                "<8.3.20221209165047"
            ],
            "v": "<8.3.20221209165047"
        }
    ],
    "schemachange": [
        {
            "advisory": "Schemachange 3.3.2 configures Jinja to escape inputs to templates (using autoescape=True). This helps protect rendered templates against XSS and other vulnerabilities.\r\nhttps://github.com/Snowflake-Labs/schemachange/commit/f006a4c550365f872fad396e87b797114eb1dc5d",
            "cve": "PVE-2021-42518",
            "id": "pyup.io-42518",
            "more_info_path": "/vulnerabilities/PVE-2021-42518/42518",
            "specs": [
                "<3.3.2"
            ],
            "v": "<3.3.2"
        }
    ],
    "schemathesis": [
        {
            "advisory": "Schemathesis 3.18.4 updates its dependency 'werkzeug' to version '2.3.7' to include a fix for an Access Restriction Bypass vulnerability.\r\nhttps://github.com/schemathesis/schemathesis/pull/1696",
            "cve": "CVE-2023-23934",
            "id": "pyup.io-60397",
            "more_info_path": "/vulnerabilities/CVE-2023-23934/60397",
            "specs": [
                "<3.18.4"
            ],
            "v": "<3.18.4"
        },
        {
            "advisory": "Schemathesis 3.18.4 updates its dependency 'werkzeug' to version '2.3.7' to include a fix for a Denial of Service vulnerability.\r\nhttps://github.com/schemathesis/schemathesis/pull/1696",
            "cve": "CVE-2023-25577",
            "id": "pyup.io-60382",
            "more_info_path": "/vulnerabilities/CVE-2023-25577/60382",
            "specs": [
                "<3.18.4"
            ],
            "v": "<3.18.4"
        }
    ],
    "schug": [
        {
            "advisory": "Schug version 1.6 updates its `gunicorn` dependency from ^20.1.0 to 22.0.0 to address the security vulnerability identified as CVE-2024-1135.",
            "cve": "CVE-2024-1135",
            "id": "pyup.io-71480",
            "more_info_path": "/vulnerabilities/CVE-2024-1135/71480",
            "specs": [
                "<1.6"
            ],
            "v": "<1.6"
        }
    ],
    "scikit-learn": [
        {
            "advisory": "Scikit-learn 0.24.2 includes a fix for a ReDoS vulnerability.\r\nhttps://github.com/scikit-learn/scikit-learn/issues/19522",
            "cve": "PVE-2022-52255",
            "id": "pyup.io-52255",
            "more_info_path": "/vulnerabilities/PVE-2022-52255/52255",
            "specs": [
                "<0.24.2"
            ],
            "v": "<0.24.2"
        },
        {
            "advisory": "* Disputed * Scikit-learn 1.1.0rc1 includes a fix for CVE-2020-28975: svm_predict_values in svm.cpp in Libsvm v324, as used in scikit-learn and other products, allows attackers to cause a denial of service (segmentation fault) via a crafted model SVM (introduced via pickle, json, or any other model permanence standard) with a large value in the _n_support array. \r\nNOTE: the scikit-learn vendor's position is that the behavior can only occur if the library's API is violated by an application that changes a private attribute.",
            "cve": "CVE-2020-28975",
            "id": "pyup.io-54297",
            "more_info_path": "/vulnerabilities/CVE-2020-28975/54297",
            "specs": [
                "<1.1.0rc1"
            ],
            "v": "<1.1.0rc1"
        },
        {
            "advisory": "A sensitive data leakage vulnerability was identified in affected versions of scikit-learn TfidfVectorizer. The vulnerability arises from the unexpected storage of all tokens present in the training data within the `stop_words_` attribute, rather than only storing the subset of tokens required for the TF-IDF technique to function. This behavior leads to the potential leakage of sensitive information, as the `stop_words_` attribute could contain tokens that were meant to be discarded and not stored, such as passwords or keys. The impact of this vulnerability varies based on the nature of the data being processed by the vectorizer.",
            "cve": "CVE-2024-5206",
            "id": "pyup.io-71596",
            "more_info_path": "/vulnerabilities/CVE-2024-5206/71596",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        }
    ],
    "scikit-network": [
        {
            "advisory": "Scikit-network 0.29.0 updates its dependency 'ipython' to v8.10.0 to include a security fix.",
            "cve": "CVE-2023-24816",
            "id": "pyup.io-54748",
            "more_info_path": "/vulnerabilities/CVE-2023-24816/54748",
            "specs": [
                "<0.29.0"
            ],
            "v": "<0.29.0"
        },
        {
            "advisory": "Scikit-network 0.29.0 updates its dependency 'wheel' to v0.38.4 to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-54736",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/54736",
            "specs": [
                "<0.29.0"
            ],
            "v": "<0.29.0"
        }
    ],
    "scikit-rmt": [
        {
            "advisory": "Scikit-rmt 0.7.0 updates its dependency 'scipy' to version '1.11.1' to include a security fix.\r\nhttps://github.com/AlejandroSantorum/scikit-rmt/commit/ced51769bf275174be271af820c196df7a6144fc",
            "cve": "CVE-2023-25399",
            "id": "pyup.io-59400",
            "more_info_path": "/vulnerabilities/CVE-2023-25399/59400",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        }
    ],
    "scio-pypi": [
        {
            "advisory": "Affected versions of the scio package are vulnerable to Deserialization of Untrusted Data due to vulnerable PyTorch torch.load behaviour that performs unsafe deserialization even when weights_only=True. In scio \u2264 1.0.0 the dependency constraints permit installing torch \u2264 2.5.1, and in those versions loading a checkpoint via torch.load can execute attacker-controlled Python during deserialization, making scio transitively exposed to Remote Code Execution.",
            "cve": "PVE-2025-80313",
            "id": "pyup.io-80313",
            "more_info_path": "/vulnerabilities/PVE-2025-80313/80313",
            "specs": [
                "<=1.0.0"
            ],
            "v": "<=1.0.0"
        }
    ],
    "scipp": [
        {
            "advisory": "Scipp 0.15.0 updates its dependency 'notebook' to v6.4.12 to include a security fix.",
            "cve": "CVE-2022-29238",
            "id": "pyup.io-50232",
            "more_info_path": "/vulnerabilities/CVE-2022-29238/50232",
            "specs": [
                "<0.15.0"
            ],
            "v": "<0.15.0"
        }
    ],
    "scipy": [
        {
            "advisory": "The scipy.weave component in SciPy before 0.12.1 creates insecure temporary directories.",
            "cve": "CVE-2013-4251",
            "id": "pyup.io-54057",
            "more_info_path": "/vulnerabilities/CVE-2013-4251/54057",
            "specs": [
                ">=0,<0.12.1"
            ],
            "v": ">=0,<0.12.1"
        }
    ],
    "scml": [
        {
            "advisory": "Scml 0.5.1 pins a transitive dependency (mistune>=2.0.1) to include a fix for an XSS vulnerability.",
            "cve": "CVE-2017-16876",
            "id": "pyup.io-45819",
            "more_info_path": "/vulnerabilities/CVE-2017-16876/45819",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Scml 0.5.1 pins a transitive dependency (ipython>=7.16.3) to include a security fix.",
            "cve": "CVE-2022-21699",
            "id": "pyup.io-45839",
            "more_info_path": "/vulnerabilities/CVE-2022-21699/45839",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        }
    ],
    "scons": [
        {
            "advisory": "Scons 4.0.0 converts the remaining uses of an insecure/deprecated mktemp method.",
            "cve": "PVE-2021-38489",
            "id": "pyup.io-38489",
            "more_info_path": "/vulnerabilities/PVE-2021-38489/38489",
            "specs": [
                "<4.0.0"
            ],
            "v": "<4.0.0"
        }
    ],
    "scoptrial": [
        {
            "advisory": "The Scoptrial package in PyPI version v0.0.5 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.",
            "cve": "CVE-2022-34057",
            "id": "pyup.io-62701",
            "more_info_path": "/vulnerabilities/CVE-2022-34057/62701",
            "specs": [
                "==0.0.5"
            ],
            "v": "==0.0.5"
        }
    ],
    "scout-browser": [
        {
            "advisory": "Scout is a Variant Call Format (VCF) visualization interface. The Pypi package `scout-browser` is vulnerable to path traversal due to `send_file` call in versions prior to 4.52.",
            "cve": "CVE-2022-1554",
            "id": "pyup.io-54438",
            "more_info_path": "/vulnerabilities/CVE-2022-1554/54438",
            "specs": [
                ">=0,<4.52"
            ],
            "v": ">=0,<4.52"
        },
        {
            "advisory": "Pypi package scout-browser (GitHub repository clinical-genomics/scout) prior to v4.52 is vulnerable to server-side request forgery. An attacker could make the application perform arbitrary requests to steal cookies, request access to private areas, or lead to cross-site scripting.",
            "cve": "CVE-2022-1592",
            "id": "pyup.io-53953",
            "more_info_path": "/vulnerabilities/CVE-2022-1592/53953",
            "specs": [
                ">=0,<4.52"
            ],
            "v": ">=0,<4.52"
        }
    ],
    "scoutsuite": [
        {
            "advisory": "Scoutsuite 5.11.0 fixes a DOM XSS.\r\nhttps://github.com/nccgroup/ScoutSuite/commit/1b72ab61ec3062b833f8c046e6f57fd64fe24274",
            "cve": "PVE-2022-48004",
            "id": "pyup.io-48004",
            "more_info_path": "/vulnerabilities/PVE-2022-48004/48004",
            "specs": [
                "<5.11.0"
            ],
            "v": "<5.11.0"
        }
    ],
    "scrape": [
        {
            "advisory": "Scrape 0.10.2 updates the 'lxml' dependency from 4.3.0 to 4.6.2 to include security fixes.",
            "cve": "PVE-2021-39195",
            "id": "pyup.io-43644",
            "more_info_path": "/vulnerabilities/PVE-2021-39195/43644",
            "specs": [
                "<0.10.2"
            ],
            "v": "<0.10.2"
        },
        {
            "advisory": "Scrape 0.10.2 updates the 'lxml' dependency from 4.3.0 to 4.6.2 to include security fixes.",
            "cve": "CVE-2020-27783",
            "id": "pyup.io-39424",
            "more_info_path": "/vulnerabilities/CVE-2020-27783/39424",
            "specs": [
                "<0.10.2"
            ],
            "v": "<0.10.2"
        },
        {
            "advisory": "Scrape 0.11.1 updates its dependency 'lxml' to v4.6.3 to include a security fix.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-45186",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/45186",
            "specs": [
                "<0.11.1"
            ],
            "v": "<0.11.1"
        },
        {
            "advisory": "Scrape 0.11.2 updates its dependency 'lxml' to v4.6.5 to include a security fix.",
            "cve": "CVE-2021-43818",
            "id": "pyup.io-45290",
            "more_info_path": "/vulnerabilities/CVE-2021-43818/45290",
            "specs": [
                "<0.11.2"
            ],
            "v": "<0.11.2"
        }
    ],
    "scrappo": [
        {
            "advisory": "Scrappo 1.1.1 updates its dependency 'requests' minimum requirement to 2.31.0 to include a security fix.",
            "cve": "CVE-2023-32681",
            "id": "pyup.io-58799",
            "more_info_path": "/vulnerabilities/CVE-2023-32681/58799",
            "specs": [
                "<1.1.1"
            ],
            "v": "<1.1.1"
        }
    ],
    "scrapy": [
        {
            "advisory": "Scrapy versions 1.8.1 and 2.5.1 include a fix for CVE-2021-41125: If you use \"HttpAuthMiddleware\" (i.e. the \"http_user\" and \"http_pass\" spider attributes) for HTTP authentication, all requests will expose your credentials to the request target. This includes requests generated by Scrapy components, such as \"robots.txt\" requests sent by Scrapy when the \"ROBOTSTXT_OBEY\" setting is set to \"True\", or as requests reached through redirects. It's advised upgrading and using the new \"http_auth_domain\" spider attribute to control which domains are allowed to receive the configured HTTP authentication credentials. If you cannot upgrade to a secure version, set your HTTP authentication credentials on a per-request basis, using for example the \"w3lib.http.basic_auth_header\" function to convert your credentials into a value that you can assign to the \"Authorization\" header of your request, instead of defining them globally using \"HttpAuthMiddleware\".\r\nhttps://github.com/scrapy/scrapy/security/advisories/GHSA-jwqp-28gf-p498\r\nhttp://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth\r\nhttps://github.com/scrapy/scrapy/commit/b01d69a1bf48060daec8f751368622352d8b85a6\r\nhttps://w3lib.readthedocs.io/en/latest/w3lib.html#w3lib.http.basic_auth_header",
            "cve": "CVE-2021-41125",
            "id": "pyup.io-42057",
            "more_info_path": "/vulnerabilities/CVE-2021-41125/42057",
            "specs": [
                "<1.8.1",
                ">=2.0.0,<2.5.1"
            ],
            "v": "<1.8.1,>=2.0.0,<2.5.1"
        },
        {
            "advisory": "Scrapy versions 1.8.2 and 2.6.0 include a fix for CVE-2022-0577: Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository scrapy/scrapy prior to 2.6.1.\r\nhttps://github.com/advisories/GHSA-cjvr-mfj7-j4j8",
            "cve": "CVE-2022-0577",
            "id": "pyup.io-46423",
            "more_info_path": "/vulnerabilities/CVE-2022-0577/46423",
            "specs": [
                "<1.8.2",
                ">=2.0.0,<2.6.0"
            ],
            "v": "<1.8.2,>=2.0.0,<2.6.0"
        },
        {
            "advisory": "Scrapy 1.8.3 and 2.6.2 fix a security issue: Credentials of one proxy may be sent to another.\r\nhttps://github.com/scrapy/scrapy/security/advisories/GHSA-9x8m-2xpf-crp3",
            "cve": "PVE-2023-55177",
            "id": "pyup.io-55177",
            "more_info_path": "/vulnerabilities/PVE-2023-55177/55177",
            "specs": [
                "<1.8.3",
                ">=2.0.0,<2.6.2"
            ],
            "v": "<1.8.3,>=2.0.0,<2.6.2"
        },
        {
            "advisory": "Scrapy's redirect middleware improperly retains the `Authorization` header when redirecting requests to a different domain, leading to potential credential leakage. This occurs when an initial request with an `Authorization` header is redirected by a server to another domain, contrary to recommendations that suggest such headers should be dropped during cross-domain redirects. The vulnerability has been detected in versions of Scrapy. Users unable to upgrade to newer versions should avoid using the `Authorization` header or implement workarounds like disabling redirects for certain requests or ensuring the trustworthiness of redirect destinations to prevent credentials from being exposed to unintended third parties.",
            "cve": "PVE-2024-68088",
            "id": "pyup.io-68088",
            "more_info_path": "/vulnerabilities/PVE-2024-68088/68088",
            "specs": [
                "<1.8.4",
                ">=2,<2.11.1"
            ],
            "v": "<1.8.4,>=2,<2.11.1"
        },
        {
            "advisory": "In scrapy/scrapy, an issue was identified where the Authorization header is not removed during redirects that only change the scheme (e.g., HTTPS to HTTP) but remain within the same domain. This behavior contravenes the Fetch standard, which mandates the removal of Authorization headers in cross-origin requests when the scheme, host, or port changes. Consequently, when a redirect downgrades from HTTPS to HTTP, the Authorization header may be inadvertently exposed in plaintext, leading to potential sensitive information disclosure to unauthorized actors. The flaw is located in the _build_redirect_request function of the redirect middleware.",
            "cve": "CVE-2024-1968",
            "id": "pyup.io-71640",
            "more_info_path": "/vulnerabilities/CVE-2024-1968/71640",
            "specs": [
                "<2.11.2"
            ],
            "v": "<2.11.2"
        },
        {
            "advisory": "When using system proxy settings specific to HTTP (http://) or HTTPS (https://) URLs, Scrapy did not correctly handle scheme changes during redirects. For instance, an HTTP request would use the HTTP proxy, but if redirected to an HTTPS URL, the HTTPS request would continue using the HTTP proxy instead of switching to the HTTPS proxy. This issue also occurred in reverse. This misconfiguration poses a security risk, especially if different proxies are configured for HTTP and HTTPS for security reasons. For example, you might not want one proxy provider to be aware of the URLs visited by another.",
            "cve": "PVE-2024-71987",
            "id": "pyup.io-71987",
            "more_info_path": "/vulnerabilities/PVE-2024-71987/71987",
            "specs": [
                "<2.11.2"
            ],
            "v": "<2.11.2"
        },
        {
            "advisory": "Scrapy previously followed redirects regardless of the URL protocol, allowing redirects for `data://`, `file://`, `ftp://`, `s3://`, and any other scheme defined in the `DOWNLOAD_HANDLERS` setting. However, HTTP redirects should only work between URLs that use the `http://` or `https://` schemes.",
            "cve": "PVE-2024-71988",
            "id": "pyup.io-71988",
            "more_info_path": "/vulnerabilities/PVE-2024-71988/71988",
            "specs": [
                "<2.11.2"
            ],
            "v": "<2.11.2"
        },
        {
            "advisory": "Scrapy, a web crawling framework, is susceptible to an XML External Entity (XXE) Injection vulnerability involving a limited set of versions. This vulnerability specifically arises within the sitemap reader component, where parsing XML input allows for external entities to be specified. Exploits could enable attackers to disclose sensitive local files or data, such as passwords, by using external entities within the XML document to access local or remote content. This could potentially compromise data confidentiality or lead to a Denial of Service by overwhelming resources with requests.",
            "cve": "PVE-2024-99877",
            "id": "pyup.io-65543",
            "more_info_path": "/vulnerabilities/PVE-2024-99877/65543",
            "specs": [
                ">=0,<0.24.0"
            ],
            "v": ">=0,<0.24.0"
        },
        {
            "advisory": "Scrapy 1.8.2 and 2.6.0 include a security fix: Responses from domain names whose public domain name suffix contains 1 or more periods (e.g. responses from 'example.co.uk', given its public domain name suffix is co.uk') are able to set cookies that are included in requests to any other domain sharing the same domain name suffix.\r\nThe only workaround for unpatched versions of Scrapy is to disable cookies altogether or limit target domains to a subset that does not include domain names with one of the public domain suffixes affected (those with 1 or more periods).",
            "cve": "PVE-2023-55200",
            "id": "pyup.io-55200",
            "more_info_path": "/vulnerabilities/PVE-2023-55200/55200",
            "specs": [
                ">=0,<1.8.2",
                ">=2.0.0,<2.6.0"
            ],
            "v": ">=0,<1.8.2,>=2.0.0,<2.6.0"
        },
        {
            "advisory": "The scrapy/scrapy project is vulnerable to XML External Entity (XXE) attacks due to the use of lxml.etree.fromstring for parsing untrusted XML data without proper validation. This vulnerability allows attackers to perform denial of service attacks, access local files, generate network connections, or circumvent firewalls by submitting specially crafted XML data.",
            "cve": "CVE-2024-3572",
            "id": "pyup.io-66736",
            "more_info_path": "/vulnerabilities/CVE-2024-3572/66736",
            "specs": [
                ">=0,<1.8.4",
                ">=2.0.0,<2.11.1"
            ],
            "v": ">=0,<1.8.4,>=2.0.0,<2.11.1"
        },
        {
            "advisory": "Affected versions earlier 1.8.4 and\u200b 2.11.1 of Scrapy are vulnerable to a Regular Expression Denial of Service (ReDoS) attack, particularly through the XMLFeedSpider class or any subclass that leverages the default node iterator iternodes, as well as through direct uses of the scrapy.utils.iterators.xmliter function. This vulnerability allows an attacker to trigger excessive CPU and memory usage by sending a malicious response, effectively leading to denial of service. Mitigation strategies include changing the node iterator for XMLFeedSpider to xml or html, and for functions like open_in_browser, reviewing response content for potential ReDoS attacks or manually setting the base tag before usage is advised.",
            "cve": "PVE-2024-99757",
            "id": "pyup.io-66738",
            "more_info_path": "/vulnerabilities/PVE-2024-99757/66738",
            "specs": [
                ">=0,<1.8.4",
                ">=2.0.0,<2.11.1"
            ],
            "v": ">=0,<1.8.4,>=2.0.0,<2.11.1"
        },
        {
            "advisory": "Scrapy is vulnerable to CVE-2017-14158: Scrapy allows remote attackers to cause a denial of service (memory consumption) via large files because arbitrarily many files are read into memory, which is especially problematic if the files are then individually written in a separate thread to a slow storage resource, as demonstrated by interaction between dataReceived (in core/downloader/handlers/http11.py) and S3FilesStore.",
            "cve": "CVE-2017-14158",
            "id": "pyup.io-54672",
            "more_info_path": "/vulnerabilities/CVE-2017-14158/54672",
            "specs": [
                ">=0.7"
            ],
            "v": ">=0.7"
        },
        {
            "advisory": "In scrapy/scrapy, an issue was identified where the Authorization header, containing credentials for server authentication, is leaked to a third-party site during a cross-domain redirect. This vulnerability arises from the failure to remove the Authorization header when redirecting across domains. The exposure of the Authorization header to unauthorized actors could potentially allow for account hijacking.",
            "cve": "CVE-2024-3574",
            "id": "pyup.io-71642",
            "more_info_path": "/vulnerabilities/CVE-2024-3574/71642",
            "specs": [
                ">=2,<2.11.1",
                "<1.8.4"
            ],
            "v": ">=2,<2.11.1,<1.8.4"
        },
        {
            "advisory": "A Regular Expression Denial of Service (ReDoS) vulnerability exists in the XMLFeedSpider class of the scrapy/scrapy project, specifically in the parsing of XML content. By crafting malicious XML content that exploits inefficient regular expression complexity used in the parsing process, an attacker can cause a denial-of-service (DoS) condition. This vulnerability allows for the system to hang and consume significant resources, potentially rendering services that utilize Scrapy for XML processing unresponsive.",
            "cve": "CVE-2024-1892",
            "id": "pyup.io-71643",
            "more_info_path": "/vulnerabilities/CVE-2024-1892/71643",
            "specs": [
                ">=2,<2.11.1",
                "<1.8.4"
            ],
            "v": ">=2,<2.11.1,<1.8.4"
        },
        {
            "advisory": "When utilizing the built-in HTTP proxy downloader middleware in Scrapy, if a request is processed with proxy credentials included, the middleware sets a Proxy-Authentication header unless it's already present. However, issues arise with third-party proxy-rotation middleware, which may update the proxy metadata for each request without clearing the previous Proxy-Authentication header. This mismatch can lead to proxy credentials being sent to an unintended proxy. Especially problematic during request retries and redirects, this error could expose sensitive proxy credentials if different proxies require them. Users leveraging third-party proxy-rotation middleware need to ensure these are patched alongside Scrapy to prevent data leaks.",
            "cve": "PVE-2024-70412",
            "id": "pyup.io-70412",
            "more_info_path": "/vulnerabilities/PVE-2024-70412/70412",
            "specs": [
                ">=2,<2.6.2",
                "<1.8.3"
            ],
            "v": ">=2,<2.6.2,<1.8.3"
        }
    ],
    "scrapy-splash": [
        {
            "advisory": "Scrapy-splash is a library which provides Scrapy and JavaScript integration. In affected versions users who use [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth) (i.e. the `http_user` and `http_pass` spider attributes) for Splash authentication will have any non-Splash request expose your credentials to the request target. This includes `robots.txt` requests sent by Scrapy when the `ROBOTSTXT_OBEY` setting is set to `True`. Upgrade to scrapy-splash 0.8.0 and use the new `SPLASH_USER` and `SPLASH_PASS` settings instead to set your Splash authentication credentials safely. If you cannot upgrade, set your Splash request credentials on a per-request basis, [using the `splash_headers` request parameter](https://github.com/scrapy-plugins/scrapy-splash/tree/0.8.x#http-basic-auth), instead of defining them globally using the [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth). Alternatively, make sure all your requests go through Splash. That includes disabling the [robots.txt middleware](https://docs.scrapy.org/en/latest/topics/downloader-middleware.html#topics-dlmw-robots).",
            "cve": "CVE-2021-41124",
            "id": "pyup.io-54700",
            "more_info_path": "/vulnerabilities/CVE-2021-41124/54700",
            "specs": [
                ">=0,<0.8.0"
            ],
            "v": ">=0,<0.8.0"
        }
    ],
    "scrapy-zyte-api": [
        {
            "advisory": "Affected versions of scrapy-zyte-api are vulnerable to a Race Condition leading to Uncontrolled Resource Consumption (CWE-400). This vulnerability allows the crawler to exceed the configured maximum number of Zyte API requests due to inconsistent tracking under concurrent conditions. An attacker could exploit this by rapidly sending multiple requests, potentially leading to higher resource usage or unexpected costs. The vulnerability exists in the _max_requests_reached method of scrapy_zyte_api/_middlewares.py. Users should update to the version which fixes the issue by implementing an atomic request counter.",
            "cve": "PVE-2024-73843",
            "id": "pyup.io-73843",
            "more_info_path": "/vulnerabilities/PVE-2024-73843/73843",
            "specs": [
                "<0.25.0"
            ],
            "v": "<0.25.0"
        }
    ],
    "scrapydd": [
        {
            "advisory": "Scrapydd 0.6.3 enhances the security by adding protection against cross-site request forgery.",
            "cve": "PVE-2021-37457",
            "id": "pyup.io-37457",
            "more_info_path": "/vulnerabilities/PVE-2021-37457/37457",
            "specs": [
                "<0.6.3"
            ],
            "v": "<0.6.3"
        }
    ],
    "scu-captcha": [
        {
            "advisory": "The scu-captcha package in PyPI v0.0.1 to v0.0.4 included a code execution backdoor inserted by a third party.",
            "cve": "CVE-2022-34983",
            "id": "pyup.io-62708",
            "more_info_path": "/vulnerabilities/CVE-2022-34983/62708",
            "specs": [
                ">=0.0.1,<=0.0.4"
            ],
            "v": ">=0.0.1,<=0.0.4"
        }
    ],
    "scvae": [
        {
            "advisory": "Scvae 2.1.1 updates TensorFlow to v1.15.2 to include security fixes.",
            "cve": "CVE-2019-16168",
            "id": "pyup.io-43825",
            "more_info_path": "/vulnerabilities/CVE-2019-16168/43825",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Scvae 2.1.1 updates TensorFlow to v1.15.2 to include security fixes.",
            "cve": "CVE-2019-19646",
            "id": "pyup.io-37932",
            "more_info_path": "/vulnerabilities/CVE-2019-19646/37932",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Scvae 2.1.1 updates TensorFlow to v1.15.2 to include security fixes.",
            "cve": "CVE-2019-5481",
            "id": "pyup.io-43824",
            "more_info_path": "/vulnerabilities/CVE-2019-5481/43824",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Scvae 2.1.1 updates TensorFlow to v1.15.2 to include security fixes.",
            "cve": "CVE-2019-5482",
            "id": "pyup.io-43827",
            "more_info_path": "/vulnerabilities/CVE-2019-5482/43827",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Scvae 2.1.1 updates TensorFlow to v1.15.2 to include security fixes.",
            "cve": "CVE-2020-5215",
            "id": "pyup.io-43826",
            "more_info_path": "/vulnerabilities/CVE-2020-5215/43826",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23568",
            "id": "pyup.io-46767",
            "more_info_path": "/vulnerabilities/CVE-2022-23568/46767",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23577",
            "id": "pyup.io-46776",
            "more_info_path": "/vulnerabilities/CVE-2022-23577/46776",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-11656",
            "id": "pyup.io-46670",
            "more_info_path": "/vulnerabilities/CVE-2020-11656/46670",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2019-10099",
            "id": "pyup.io-46661",
            "more_info_path": "/vulnerabilities/CVE-2019-10099/46661",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23570",
            "id": "pyup.io-46769",
            "more_info_path": "/vulnerabilities/CVE-2022-23570/46769",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23580",
            "id": "pyup.io-46779",
            "more_info_path": "/vulnerabilities/CVE-2022-23580/46779",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41205",
            "id": "pyup.io-46716",
            "more_info_path": "/vulnerabilities/CVE-2021-41205/46716",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41226",
            "id": "pyup.io-46736",
            "more_info_path": "/vulnerabilities/CVE-2021-41226/46736",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21725",
            "id": "pyup.io-46739",
            "more_info_path": "/vulnerabilities/CVE-2022-21725/46739",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21727",
            "id": "pyup.io-46741",
            "more_info_path": "/vulnerabilities/CVE-2022-21727/46741",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23558",
            "id": "pyup.io-46757",
            "more_info_path": "/vulnerabilities/CVE-2022-23558/46757",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23559",
            "id": "pyup.io-46758",
            "more_info_path": "/vulnerabilities/CVE-2022-23559/46758",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23564",
            "id": "pyup.io-46763",
            "more_info_path": "/vulnerabilities/CVE-2022-23564/46763",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23563",
            "id": "pyup.io-46762",
            "more_info_path": "/vulnerabilities/CVE-2022-23563/46762",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23565",
            "id": "pyup.io-46764",
            "more_info_path": "/vulnerabilities/CVE-2022-23565/46764",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23576",
            "id": "pyup.io-46775",
            "more_info_path": "/vulnerabilities/CVE-2022-23576/46775",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23581",
            "id": "pyup.io-46780",
            "more_info_path": "/vulnerabilities/CVE-2022-23581/46780",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23584",
            "id": "pyup.io-46783",
            "more_info_path": "/vulnerabilities/CVE-2022-23584/46783",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-11655",
            "id": "pyup.io-46669",
            "more_info_path": "/vulnerabilities/CVE-2020-11655/46669",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23586",
            "id": "pyup.io-46785",
            "more_info_path": "/vulnerabilities/CVE-2022-23586/46785",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23595",
            "id": "pyup.io-46790",
            "more_info_path": "/vulnerabilities/CVE-2022-23595/46790",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41225",
            "id": "pyup.io-46735",
            "more_info_path": "/vulnerabilities/CVE-2021-41225/46735",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21734",
            "id": "pyup.io-46748",
            "more_info_path": "/vulnerabilities/CVE-2022-21734/46748",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23569",
            "id": "pyup.io-46768",
            "more_info_path": "/vulnerabilities/CVE-2022-23569/46768",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23566",
            "id": "pyup.io-46765",
            "more_info_path": "/vulnerabilities/CVE-2022-23566/46765",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23574",
            "id": "pyup.io-46773",
            "more_info_path": "/vulnerabilities/CVE-2022-23574/46773",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41216",
            "id": "pyup.io-46727",
            "more_info_path": "/vulnerabilities/CVE-2021-41216/46727",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41223",
            "id": "pyup.io-46733",
            "more_info_path": "/vulnerabilities/CVE-2021-41223/46733",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2018-20330",
            "id": "pyup.io-46660",
            "more_info_path": "/vulnerabilities/CVE-2018-20330/46660",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2019-19244",
            "id": "pyup.io-46664",
            "more_info_path": "/vulnerabilities/CVE-2019-19244/46664",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2019-19645",
            "id": "pyup.io-46665",
            "more_info_path": "/vulnerabilities/CVE-2019-19645/46665",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2019-19880",
            "id": "pyup.io-46666",
            "more_info_path": "/vulnerabilities/CVE-2019-19880/46666",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2019-20838",
            "id": "pyup.io-46667",
            "more_info_path": "/vulnerabilities/CVE-2019-20838/46667",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-9327",
            "id": "pyup.io-46700",
            "more_info_path": "/vulnerabilities/CVE-2020-9327/46700",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2018-19664",
            "id": "pyup.io-46659",
            "more_info_path": "/vulnerabilities/CVE-2018-19664/46659",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15195",
            "id": "pyup.io-46680",
            "more_info_path": "/vulnerabilities/CVE-2020-15195/46680",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15204",
            "id": "pyup.io-46683",
            "more_info_path": "/vulnerabilities/CVE-2020-15204/46683",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41222",
            "id": "pyup.io-46732",
            "more_info_path": "/vulnerabilities/CVE-2021-41222/46732",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-26270",
            "id": "pyup.io-46698",
            "more_info_path": "/vulnerabilities/CVE-2020-26270/46698",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15205",
            "id": "pyup.io-46684",
            "more_info_path": "/vulnerabilities/CVE-2020-15205/46684",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15203",
            "id": "pyup.io-46682",
            "more_info_path": "/vulnerabilities/CVE-2020-15203/46682",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15210",
            "id": "pyup.io-46689",
            "more_info_path": "/vulnerabilities/CVE-2020-15210/46689",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23572",
            "id": "pyup.io-46771",
            "more_info_path": "/vulnerabilities/CVE-2022-23572/46771",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15207",
            "id": "pyup.io-46686",
            "more_info_path": "/vulnerabilities/CVE-2020-15207/46686",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41228",
            "id": "pyup.io-46738",
            "more_info_path": "/vulnerabilities/CVE-2021-41228/46738",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2018-17190",
            "id": "pyup.io-46658",
            "more_info_path": "/vulnerabilities/CVE-2018-17190/46658",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-22923",
            "id": "pyup.io-46702",
            "more_info_path": "/vulnerabilities/CVE-2021-22923/46702",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-22922",
            "id": "pyup.io-46701",
            "more_info_path": "/vulnerabilities/CVE-2021-22922/46701",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41197",
            "id": "pyup.io-46708",
            "more_info_path": "/vulnerabilities/CVE-2021-41197/46708",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41207",
            "id": "pyup.io-46718",
            "more_info_path": "/vulnerabilities/CVE-2021-41207/46718",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41209",
            "id": "pyup.io-46720",
            "more_info_path": "/vulnerabilities/CVE-2021-41209/46720",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41213",
            "id": "pyup.io-46724",
            "more_info_path": "/vulnerabilities/CVE-2021-41213/46724",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41217",
            "id": "pyup.io-46728",
            "more_info_path": "/vulnerabilities/CVE-2021-41217/46728",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41221",
            "id": "pyup.io-46731",
            "more_info_path": "/vulnerabilities/CVE-2021-41221/46731",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41224",
            "id": "pyup.io-46734",
            "more_info_path": "/vulnerabilities/CVE-2021-41224/46734",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-26271",
            "id": "pyup.io-46699",
            "more_info_path": "/vulnerabilities/CVE-2020-26271/46699",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-26267",
            "id": "pyup.io-46696",
            "more_info_path": "/vulnerabilities/CVE-2020-26267/46696",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41212",
            "id": "pyup.io-46723",
            "more_info_path": "/vulnerabilities/CVE-2021-41212/46723",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-10531",
            "id": "pyup.io-46668",
            "more_info_path": "/vulnerabilities/CVE-2020-10531/46668",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41195",
            "id": "pyup.io-46706",
            "more_info_path": "/vulnerabilities/CVE-2021-41195/46706",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41201",
            "id": "pyup.io-46712",
            "more_info_path": "/vulnerabilities/CVE-2021-41201/46712",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41227",
            "id": "pyup.io-46737",
            "more_info_path": "/vulnerabilities/CVE-2021-41227/46737",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41200",
            "id": "pyup.io-46711",
            "more_info_path": "/vulnerabilities/CVE-2021-41200/46711",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15358",
            "id": "pyup.io-46694",
            "more_info_path": "/vulnerabilities/CVE-2020-15358/46694",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41202",
            "id": "pyup.io-46713",
            "more_info_path": "/vulnerabilities/CVE-2021-41202/46713",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21729",
            "id": "pyup.io-46743",
            "more_info_path": "/vulnerabilities/CVE-2022-21729/46743",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-13631",
            "id": "pyup.io-46674",
            "more_info_path": "/vulnerabilities/CVE-2020-13631/46674",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-26266",
            "id": "pyup.io-46695",
            "more_info_path": "/vulnerabilities/CVE-2020-26266/46695",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41211",
            "id": "pyup.io-46722",
            "more_info_path": "/vulnerabilities/CVE-2021-41211/46722",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41196",
            "id": "pyup.io-46707",
            "more_info_path": "/vulnerabilities/CVE-2021-41196/46707",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2019-13960",
            "id": "pyup.io-46662",
            "more_info_path": "/vulnerabilities/CVE-2019-13960/46662",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41199",
            "id": "pyup.io-46710",
            "more_info_path": "/vulnerabilities/CVE-2021-41199/46710",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23591",
            "id": "pyup.io-46789",
            "more_info_path": "/vulnerabilities/CVE-2022-23591/46789",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-13434",
            "id": "pyup.io-46671",
            "more_info_path": "/vulnerabilities/CVE-2020-13434/46671",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23589",
            "id": "pyup.io-46788",
            "more_info_path": "/vulnerabilities/CVE-2022-23589/46788",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23588",
            "id": "pyup.io-46787",
            "more_info_path": "/vulnerabilities/CVE-2022-23588/46787",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23587",
            "id": "pyup.io-46786",
            "more_info_path": "/vulnerabilities/CVE-2022-23587/46786",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23585",
            "id": "pyup.io-46784",
            "more_info_path": "/vulnerabilities/CVE-2022-23585/46784",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23583",
            "id": "pyup.io-46782",
            "more_info_path": "/vulnerabilities/CVE-2022-23583/46782",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23582",
            "id": "pyup.io-46781",
            "more_info_path": "/vulnerabilities/CVE-2022-23582/46781",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23579",
            "id": "pyup.io-46778",
            "more_info_path": "/vulnerabilities/CVE-2022-23579/46778",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23578",
            "id": "pyup.io-46777",
            "more_info_path": "/vulnerabilities/CVE-2022-23578/46777",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2018-11770",
            "id": "pyup.io-46657",
            "more_info_path": "/vulnerabilities/CVE-2018-11770/46657",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23575",
            "id": "pyup.io-46774",
            "more_info_path": "/vulnerabilities/CVE-2022-23575/46774",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23573",
            "id": "pyup.io-46772",
            "more_info_path": "/vulnerabilities/CVE-2022-23573/46772",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23571",
            "id": "pyup.io-46770",
            "more_info_path": "/vulnerabilities/CVE-2022-23571/46770",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23562",
            "id": "pyup.io-46761",
            "more_info_path": "/vulnerabilities/CVE-2022-23562/46761",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23561",
            "id": "pyup.io-46760",
            "more_info_path": "/vulnerabilities/CVE-2022-23561/46760",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23560",
            "id": "pyup.io-46759",
            "more_info_path": "/vulnerabilities/CVE-2022-23560/46759",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23557",
            "id": "pyup.io-46756",
            "more_info_path": "/vulnerabilities/CVE-2022-23557/46756",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21737",
            "id": "pyup.io-46751",
            "more_info_path": "/vulnerabilities/CVE-2022-21737/46751",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-22926",
            "id": "pyup.io-46705",
            "more_info_path": "/vulnerabilities/CVE-2021-22926/46705",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21736",
            "id": "pyup.io-46750",
            "more_info_path": "/vulnerabilities/CVE-2022-21736/46750",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21732",
            "id": "pyup.io-46746",
            "more_info_path": "/vulnerabilities/CVE-2022-21732/46746",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21728",
            "id": "pyup.io-46742",
            "more_info_path": "/vulnerabilities/CVE-2022-21728/46742",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21731",
            "id": "pyup.io-46745",
            "more_info_path": "/vulnerabilities/CVE-2022-21731/46745",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21733",
            "id": "pyup.io-46747",
            "more_info_path": "/vulnerabilities/CVE-2022-21733/46747",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21738",
            "id": "pyup.io-46752",
            "more_info_path": "/vulnerabilities/CVE-2022-21738/46752",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21726",
            "id": "pyup.io-46740",
            "more_info_path": "/vulnerabilities/CVE-2022-21726/46740",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-23567",
            "id": "pyup.io-46766",
            "more_info_path": "/vulnerabilities/CVE-2022-23567/46766",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15194",
            "id": "pyup.io-46679",
            "more_info_path": "/vulnerabilities/CVE-2020-15194/46679",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41214",
            "id": "pyup.io-46725",
            "more_info_path": "/vulnerabilities/CVE-2021-41214/46725",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15211",
            "id": "pyup.io-46690",
            "more_info_path": "/vulnerabilities/CVE-2020-15211/46690",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-13871",
            "id": "pyup.io-46676",
            "more_info_path": "/vulnerabilities/CVE-2020-13871/46676",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-13435",
            "id": "pyup.io-46672",
            "more_info_path": "/vulnerabilities/CVE-2020-13435/46672",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15265",
            "id": "pyup.io-46692",
            "more_info_path": "/vulnerabilities/CVE-2020-15265/46692",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15250",
            "id": "pyup.io-46691",
            "more_info_path": "/vulnerabilities/CVE-2020-15250/46691",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-14155",
            "id": "pyup.io-46677",
            "more_info_path": "/vulnerabilities/CVE-2020-14155/46677",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15209",
            "id": "pyup.io-46688",
            "more_info_path": "/vulnerabilities/CVE-2020-15209/46688",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15208",
            "id": "pyup.io-46687",
            "more_info_path": "/vulnerabilities/CVE-2020-15208/46687",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-26268",
            "id": "pyup.io-46697",
            "more_info_path": "/vulnerabilities/CVE-2020-26268/46697",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-22925",
            "id": "pyup.io-46704",
            "more_info_path": "/vulnerabilities/CVE-2021-22925/46704",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15206",
            "id": "pyup.io-46685",
            "more_info_path": "/vulnerabilities/CVE-2020-15206/46685",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15266",
            "id": "pyup.io-46693",
            "more_info_path": "/vulnerabilities/CVE-2020-15266/46693",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15202",
            "id": "pyup.io-46681",
            "more_info_path": "/vulnerabilities/CVE-2020-15202/46681",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41198",
            "id": "pyup.io-46709",
            "more_info_path": "/vulnerabilities/CVE-2021-41198/46709",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-15190",
            "id": "pyup.io-46678",
            "more_info_path": "/vulnerabilities/CVE-2020-15190/46678",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41203",
            "id": "pyup.io-46714",
            "more_info_path": "/vulnerabilities/CVE-2021-41203/46714",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-13630",
            "id": "pyup.io-46673",
            "more_info_path": "/vulnerabilities/CVE-2020-13630/46673",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21741",
            "id": "pyup.io-46755",
            "more_info_path": "/vulnerabilities/CVE-2022-21741/46755",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2020-13790",
            "id": "pyup.io-46675",
            "more_info_path": "/vulnerabilities/CVE-2020-13790/46675",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21740",
            "id": "pyup.io-46754",
            "more_info_path": "/vulnerabilities/CVE-2022-21740/46754",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41218",
            "id": "pyup.io-46729",
            "more_info_path": "/vulnerabilities/CVE-2021-41218/46729",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21739",
            "id": "pyup.io-46753",
            "more_info_path": "/vulnerabilities/CVE-2022-21739/46753",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41204",
            "id": "pyup.io-46715",
            "more_info_path": "/vulnerabilities/CVE-2021-41204/46715",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41208",
            "id": "pyup.io-46719",
            "more_info_path": "/vulnerabilities/CVE-2021-41208/46719",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41210",
            "id": "pyup.io-46721",
            "more_info_path": "/vulnerabilities/CVE-2021-41210/46721",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41206",
            "id": "pyup.io-46717",
            "more_info_path": "/vulnerabilities/CVE-2021-41206/46717",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-22924",
            "id": "pyup.io-46703",
            "more_info_path": "/vulnerabilities/CVE-2021-22924/46703",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21735",
            "id": "pyup.io-46749",
            "more_info_path": "/vulnerabilities/CVE-2022-21735/46749",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41219",
            "id": "pyup.io-46730",
            "more_info_path": "/vulnerabilities/CVE-2021-41219/46730",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2021-41215",
            "id": "pyup.io-46726",
            "more_info_path": "/vulnerabilities/CVE-2021-41215/46726",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        },
        {
            "advisory": "Scvae versions 2.1.4 and prior require as minimum dependency TensorFlow v1.15.2 or lower, that have several known vulnerabilities.",
            "cve": "CVE-2022-21730",
            "id": "pyup.io-46744",
            "more_info_path": "/vulnerabilities/CVE-2022-21730/46744",
            "specs": [
                "<=2.1.4"
            ],
            "v": "<=2.1.4"
        }
    ],
    "sdc-cryptography": [
        {
            "advisory": "Sdc-cryptography 1.0.0 updates its dependency 'cryptography' to v3.4.5 to include security fixes.",
            "cve": "CVE-2020-25659",
            "id": "pyup.io-43412",
            "more_info_path": "/vulnerabilities/CVE-2020-25659/43412",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "sdcclient": [
        {
            "advisory": "Sdcclient 0.7.0 adds support for secure commands audit.",
            "cve": "PVE-2021-37050",
            "id": "pyup.io-37050",
            "more_info_path": "/vulnerabilities/PVE-2021-37050/37050",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        }
    ],
    "sdcvalidator": [
        {
            "advisory": "Sdcvalidator 4.0.6",
            "cve": "PVE-2026-85037",
            "id": "pyup.io-85037",
            "more_info_path": "/vulnerabilities/PVE-2026-85037/85037",
            "specs": [
                "<4.0.6"
            ],
            "v": "<4.0.6"
        }
    ],
    "sdk-cli-v2": [
        {
            "advisory": "Sdk-cli-v2 is a malicious package, typosquatting. It aims at targeting Azure environments.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick",
            "cve": "PVE-2022-47813",
            "id": "pyup.io-47813",
            "more_info_path": "/vulnerabilities/PVE-2022-47813/47813",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "sdk-cli-v2-public": [
        {
            "advisory": "Sdk-cli-v2-public is a malicious package, typosquatting. It aims at targeting Azure environments.\r\nhttps://blog.sonatype.com/careful-out-there-open-source-attacks-continue-to-be-on-the-uptick",
            "cve": "PVE-2022-47812",
            "id": "pyup.io-47812",
            "more_info_path": "/vulnerabilities/PVE-2022-47812/47812",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "searchor": [
        {
            "advisory": "main.py in Searchor before 2.4.2 uses eval on CLI input, which may cause unexpected code execution.",
            "cve": "CVE-2023-43364",
            "id": "pyup.io-65255",
            "more_info_path": "/vulnerabilities/CVE-2023-43364/65255",
            "specs": [
                "<2.4.2"
            ],
            "v": "<2.4.2"
        },
        {
            "advisory": "Searchor 2.4.3 includes a fix for a code execution vulnerability.\r\nhttps://github.com/ArjunSharda/Searchor/pull/130",
            "cve": "PVE-2022-51846",
            "id": "pyup.io-51846",
            "more_info_path": "/vulnerabilities/PVE-2022-51846/51846",
            "specs": [
                "<2.4.3"
            ],
            "v": "<2.4.3"
        }
    ],
    "secbg": [
        {
            "advisory": "Secbg is a malicious package. It contains a backdoor.\r\nhttps://blog.sonatype.com/can-you-spot-this-cryptic-reverse-shell-found-in-pypi-packages",
            "cve": "PVE-2022-47803",
            "id": "pyup.io-47803",
            "more_info_path": "/vulnerabilities/PVE-2022-47803/47803",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "secretflow": [
        {
            "advisory": "Secretflow 0.6.7 uses a \"more secure\" random. No further information was found in the Github repository.",
            "cve": "PVE-2022-49725",
            "id": "pyup.io-49725",
            "more_info_path": "/vulnerabilities/PVE-2022-49725/49725",
            "specs": [
                "<0.6.7"
            ],
            "v": "<0.6.7"
        },
        {
            "advisory": "Secretflow 0.7.10 fixes a vulnerability in quantile.\r\nhttps://github.com/secretflow/secretflow/commit/c59f45b86fd3a02c15396643ebfaab772747004d",
            "cve": "PVE-2022-51917",
            "id": "pyup.io-51917",
            "more_info_path": "/vulnerabilities/PVE-2022-51917/51917",
            "specs": [
                "<0.7.10"
            ],
            "v": "<0.7.10"
        },
        {
            "advisory": "Secretflow 0.7.18b5 updates its dependency 'protobuf' to v3.19.6 to include a security fix.",
            "cve": "CVE-2022-1941",
            "id": "pyup.io-53872",
            "more_info_path": "/vulnerabilities/CVE-2022-1941/53872",
            "specs": [
                "<0.7.18b5"
            ],
            "v": "<0.7.18b5"
        },
        {
            "advisory": "Secretflow 0.7.18b5 requires 'wheel>=0.38.1' to include a security fix.",
            "cve": "CVE-2022-40898",
            "id": "pyup.io-53873",
            "more_info_path": "/vulnerabilities/CVE-2022-40898/53873",
            "specs": [
                "<0.7.18b5"
            ],
            "v": "<0.7.18b5"
        },
        {
            "advisory": "Secretflow 0.7.18b5 requires 'onnx' v1.13.1 to include a security fix.",
            "cve": "CVE-2022-25882",
            "id": "pyup.io-53784",
            "more_info_path": "/vulnerabilities/CVE-2022-25882/53784",
            "specs": [
                "<0.7.18b5"
            ],
            "v": "<0.7.18b5"
        }
    ],
    "secrets2env": [
        {
            "advisory": "Secrets2env 0.1.4 includes a security patch for the function 'init' in 'secrets2env.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/eguven/secrets2env/commit/d6c98573d8d2e2296720b6e2298d5db47a17b2d7",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41383",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41383",
            "specs": [
                "<0.1.4"
            ],
            "v": "<0.1.4"
        }
    ],
    "secrevtwo": [
        {
            "advisory": "Secrevtwo is a malicious package. It contains a backdoor.\r\nhttps://blog.sonatype.com/can-you-spot-this-cryptic-reverse-shell-found-in-pypi-packages",
            "cve": "PVE-2022-47804",
            "id": "pyup.io-47804",
            "more_info_path": "/vulnerabilities/PVE-2022-47804/47804",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "secsend": [
        {
            "advisory": "Secsend 1.1.0 enhances security by updating semver to version 7.6.0 due to CVE-2023-2613.",
            "cve": "CVE-2022-25883",
            "id": "pyup.io-67154",
            "more_info_path": "/vulnerabilities/CVE-2022-25883/67154",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "Secsend 1.1.0 updates the NPM package word-wrap to version 1.2.5 to address CVE-2023-26115.",
            "cve": "CVE-2023-26115",
            "id": "pyup.io-67140",
            "more_info_path": "/vulnerabilities/CVE-2023-26115/67140",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        }
    ],
    "securesystemslib": [
        {
            "advisory": "Securesystemslib 0.20.1 drops support for Python 2.7, as it arrived to EOL in January 2020.",
            "cve": "CVE-2021-23336",
            "id": "pyup.io-44929",
            "more_info_path": "/vulnerabilities/CVE-2021-23336/44929",
            "specs": [
                "<0.20.1"
            ],
            "v": "<0.20.1"
        }
    ],
    "security-monkey": [
        {
            "advisory": "Netflix Security Monkey before 0.8.0 has an Open Redirect. The logout functionality accepted the \"next\" parameter which then redirects to any domain irrespective of the Host header.",
            "cve": "CVE-2017-7266",
            "id": "pyup.io-42248",
            "more_info_path": "/vulnerabilities/CVE-2017-7266/42248",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        }
    ],
    "seed-auth-api": [
        {
            "advisory": "Seed-auth-api 0.9.3 includes upgrades of dependencies with security vulnerabilities.",
            "cve": "PVE-2021-37441",
            "id": "pyup.io-37441",
            "more_info_path": "/vulnerabilities/PVE-2021-37441/37441",
            "specs": [
                "<0.9.3"
            ],
            "v": "<0.9.3"
        }
    ],
    "seed-control-interface": [
        {
            "advisory": "Seed-control-interface-service 0.9.16 includes upgrades of dependencies with security vulnerabilities.",
            "cve": "PVE-2021-37440",
            "id": "pyup.io-37440",
            "more_info_path": "/vulnerabilities/PVE-2021-37440/37440",
            "specs": [
                "<0.9.16"
            ],
            "v": "<0.9.16"
        },
        {
            "advisory": "Seed-control-interface version 0.9.18 updates its dependency \"Django\" to 2.2.8 to include a security fix.",
            "cve": "CVE-2019-19118",
            "id": "pyup.io-41874",
            "more_info_path": "/vulnerabilities/CVE-2019-19118/41874",
            "specs": [
                "<0.9.18"
            ],
            "v": "<0.9.18"
        }
    ],
    "seed-control-interface-service": [
        {
            "advisory": "Seed-control-interface-service 0.9.6 includes upgrades of dependencies with security vulnerabilities.",
            "cve": "PVE-2021-37442",
            "id": "pyup.io-37442",
            "more_info_path": "/vulnerabilities/PVE-2021-37442/37442",
            "specs": [
                "<0.9.6"
            ],
            "v": "<0.9.6"
        }
    ],
    "seed-farmer": [
        {
            "advisory": "Seed-farmer 2.10.3 updates its dependency 'certifi' to versions ~=2023.7.22 to include a security fix.",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-61385",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/61385",
            "specs": [
                "<2.10.3"
            ],
            "v": "<2.10.3"
        },
        {
            "advisory": "Seed-farmer 2.10.4 updates its dependency 'urllib3' to include a security fix.",
            "cve": "CVE-2023-45803",
            "id": "pyup.io-61993",
            "more_info_path": "/vulnerabilities/CVE-2023-45803/61993",
            "specs": [
                "<2.10.4"
            ],
            "v": "<2.10.4"
        }
    ],
    "seed-identity-store": [
        {
            "advisory": "Seed-identity-store 0.10.2 includes upgrades of dependencies with security vulnerabilities.",
            "cve": "PVE-2021-37437",
            "id": "pyup.io-37437",
            "more_info_path": "/vulnerabilities/PVE-2021-37437/37437",
            "specs": [
                "<0.10.2"
            ],
            "v": "<0.10.2"
        }
    ],
    "seed-message-sender": [
        {
            "advisory": "Seed-message-sender 0.10.9 includes upgrades of dependencies with security vulnerabilities.",
            "cve": "PVE-2021-37436",
            "id": "pyup.io-37436",
            "more_info_path": "/vulnerabilities/PVE-2021-37436/37436",
            "specs": [
                "<0.10.9"
            ],
            "v": "<0.10.9"
        }
    ],
    "seed-scheduler": [
        {
            "advisory": "Seed-scheduler 0.10.2 includes upgrades of dependencies with security vulnerabilities.",
            "cve": "PVE-2021-37439",
            "id": "pyup.io-37439",
            "more_info_path": "/vulnerabilities/PVE-2021-37439/37439",
            "specs": [
                "<0.10.2"
            ],
            "v": "<0.10.2"
        }
    ],
    "seed-stage-based-messaging": [
        {
            "advisory": "seed-stage-based-messaging 0.11.0 upgrades requests to fix security vulnerability",
            "cve": "PVE-2021-36653",
            "id": "pyup.io-36653",
            "more_info_path": "/vulnerabilities/PVE-2021-36653/36653",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        },
        {
            "advisory": "Seed-stage-based-messaging 0.13.0 includes upgrades of dependencies with security vulnerabilities.",
            "cve": "PVE-2021-37438",
            "id": "pyup.io-37438",
            "more_info_path": "/vulnerabilities/PVE-2021-37438/37438",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        }
    ],
    "segmentationmetrics": [
        {
            "advisory": "Segmentationmetrics 1.0.1 updates its dependency 'scipy' to v1.11.2 to include a security fix.",
            "cve": "CVE-2023-25399",
            "id": "pyup.io-60977",
            "more_info_path": "/vulnerabilities/CVE-2023-25399/60977",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        }
    ],
    "seismic-rna": [
        {
            "advisory": "Security Fix for Seismic-rna 0.24.0 | Upgrade from MD5 to SHA-512 for file checksums to address cryptographic weakness.\r\n\r\nUpgrade to version 0.24.0 or higher.\r\nIf you relied on MD5-based file checksums in older versions, you should regenerate or verify them with SHA-512.\r\n\r\n- Fixed Versions: 0.24.0\r\n- Affected Versions: v0.23.1 to v0.24.0",
            "cve": "PVE-2025-75585",
            "id": "pyup.io-75585",
            "more_info_path": "/vulnerabilities/PVE-2025-75585/75585",
            "specs": [
                "<0.24.0"
            ],
            "v": "<0.24.0"
        }
    ],
    "seismic-zfp": [
        {
            "advisory": "Seismic-zfp version 0.3.2 has been updated to enhance security by upgrading its fonttools dependency from 4.38.0 to 4.43.0. This update addresses the vulnerability identified as CVE-2023-45139.",
            "cve": "CVE-2023-45139",
            "id": "pyup.io-71183",
            "more_info_path": "/vulnerabilities/CVE-2023-45139/71183",
            "specs": [
                "<0.3.2"
            ],
            "v": "<0.3.2"
        },
        {
            "advisory": "Seismic-zfp version 0.3.2 has been updated to enhance security by upgrading its numpy dependency from version 1.21.3 to 1.22.2. This update addresses the vulnerability identified as CVE-2021-41495.",
            "cve": "CVE-2021-41495",
            "id": "pyup.io-71163",
            "more_info_path": "/vulnerabilities/CVE-2021-41495/71163",
            "specs": [
                "<0.3.2"
            ],
            "v": "<0.3.2"
        },
        {
            "advisory": "Seismic-zfp version 0.3.2 updates its requests dependency from 2.31.0 to 2.32.0. This update addresses several CVEs, including CVE-2024-35195, ensuring the application is protected against vulnerabilities present in the older version.",
            "cve": "CVE-2024-35195",
            "id": "pyup.io-71182",
            "more_info_path": "/vulnerabilities/CVE-2024-35195/71182",
            "specs": [
                "<0.3.2"
            ],
            "v": "<0.3.2"
        }
    ],
    "seldon-core": [
        {
            "advisory": "Seldon-core 1.0.1 updates its dependency 'pillow' from 6.2.0 to 7.0.0 to include security fixes.",
            "cve": "CVE-2019-19911",
            "id": "pyup.io-43554",
            "more_info_path": "/vulnerabilities/CVE-2019-19911/43554",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        },
        {
            "advisory": "Seldon-core 1.0.1 updates its dependency 'pillow' from 6.2.0 to 7.0.0 to include security fixes.",
            "cve": "CVE-2020-5311",
            "id": "pyup.io-43551",
            "more_info_path": "/vulnerabilities/CVE-2020-5311/43551",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        },
        {
            "advisory": "Seldon-core 1.0.1 updates its dependency 'pillow' from 6.2.0 to 7.0.0 to include security fixes.",
            "cve": "CVE-2020-5313",
            "id": "pyup.io-43553",
            "more_info_path": "/vulnerabilities/CVE-2020-5313/43553",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        },
        {
            "advisory": "Seldon-core 1.0.1 updates its dependency 'pillow' from 6.2.0 to 7.0.0 to include security fixes.",
            "cve": "CVE-2020-5312",
            "id": "pyup.io-43552",
            "more_info_path": "/vulnerabilities/CVE-2020-5312/43552",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        },
        {
            "advisory": "Seldon-core 1.6.0 uses yaml.safe_load() instead of yaml.load() to avoid a potential code execution vulnerability.",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-40781",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/40781",
            "specs": [
                "<1.6.0"
            ],
            "v": "<1.6.0"
        },
        {
            "advisory": "Seldon-core 1.7.0 addresses CVEs for Redhat Python based images.\r\nhttps://github.com/SeldonIO/seldon-core/pull/2977",
            "cve": "CVE-2020-8265",
            "id": "pyup.io-45332",
            "more_info_path": "/vulnerabilities/CVE-2020-8265/45332",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Seldon-core 1.7.0 addresses CVEs for Redhat Python based images.\r\nhttps://github.com/SeldonIO/seldon-core/pull/2977",
            "cve": "CVE-2020-7788",
            "id": "pyup.io-45341",
            "more_info_path": "/vulnerabilities/CVE-2020-7788/45341",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Seldon-core 1.7.0 addresses CVEs from Python base Image.\r\nhttps://github.com/SeldonIO/seldon-core/pull/2970",
            "cve": "CVE-2020-26137",
            "id": "pyup.io-45344",
            "more_info_path": "/vulnerabilities/CVE-2020-26137/45344",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Seldon-core 1.7.0 addresses CVEs from Python base Image.\r\nhttps://github.com/SeldonIO/seldon-core/pull/2970",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-45345",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/45345",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Seldon-core 1.7.0 addresses CVEs for Redhat Python based images.\r\nhttps://github.com/SeldonIO/seldon-core/pull/2977",
            "cve": "CVE-2020-8287",
            "id": "pyup.io-45342",
            "more_info_path": "/vulnerabilities/CVE-2020-8287/45342",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Seldon-core 1.7.0 addresses CVEs for Redhat Python based images.\r\nhttps://github.com/SeldonIO/seldon-core/pull/2977",
            "cve": "CVE-2020-8116",
            "id": "pyup.io-45340",
            "more_info_path": "/vulnerabilities/CVE-2020-8116/45340",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Seldon-core 1.7.0 addresses CVEs from Python base Image.\r\nhttps://github.com/SeldonIO/seldon-core/pull/2970",
            "cve": "CVE-2020-1971",
            "id": "pyup.io-45346",
            "more_info_path": "/vulnerabilities/CVE-2020-1971/45346",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        },
        {
            "advisory": "Affected versions of seldon-core are vulnerable to Cross-site Scripting (XSS) because they fail to escape response headers properly.",
            "cve": "PVE-2024-99876",
            "id": "pyup.io-65544",
            "more_info_path": "/vulnerabilities/PVE-2024-99876/65544",
            "specs": [
                ">=0,<1.2.0"
            ],
            "v": ">=0,<1.2.0"
        }
    ],
    "selenible": [
        {
            "advisory": "Selenible version 0.0.4 includes a security patch for the function 'Base_var_from' in 'selenible/modules/ctrl.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load(). \r\nhttps://github.com/wtnb75/selenible/commit/4e53114278475d94dd0c98fd6dbf41806b2c1c98",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41392",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41392",
            "specs": [
                "<0.0.4"
            ],
            "v": "<0.0.4"
        }
    ],
    "selenium": [
        {
            "advisory": "Selenium 4.15.1 (Python bindings) include a fix for CVE-2023-5590: NULL Pointer Dereference.\r\nhttps://github.com/seleniumhq/selenium/commit/023a0d52f106321838ab1c0997e76693f4dcbdf6",
            "cve": "CVE-2023-5590",
            "id": "pyup.io-63073",
            "more_info_path": "/vulnerabilities/CVE-2023-5590/63073",
            "specs": [
                ">=0,<4.15.1"
            ],
            "v": ">=0,<4.15.1"
        }
    ],
    "selenium-duration-50ms": [
        {
            "advisory": "Selenium 4.15.1 (Python bindings) include a fix for CVE-2023-5590: NULL Pointer Dereference.\r\nhttps://github.com/seleniumhq/selenium/commit/023a0d52f106321838ab1c0997e76693f4dcbdf6",
            "cve": "CVE-2023-5590",
            "id": "pyup.io-63074",
            "more_info_path": "/vulnerabilities/CVE-2023-5590/63074",
            "specs": [
                ">=0,<4.15.1"
            ],
            "v": ">=0,<4.15.1"
        }
    ],
    "selenium-wire": [
        {
            "advisory": "Selenium-wire 1.2.1 uses SHA256 digest when creating site certificates to fix Chrome HSTS security errors.",
            "cve": "PVE-2021-38396",
            "id": "pyup.io-38396",
            "more_info_path": "/vulnerabilities/PVE-2021-38396/38396",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        }
    ],
    "semantic-copycat-binarysniffer": [
        {
            "advisory": "Affected versions of the semantic-copycat-binarysniffer package are potentially vulnerable to Deserialization of Untrusted Data due to the pickle extractor omitting the validate_safe_unpickle() security check before loading user-supplied pickle content.",
            "cve": "PVE-2025-80681",
            "id": "pyup.io-80681",
            "more_info_path": "/vulnerabilities/PVE-2025-80681/80681",
            "specs": [
                "<1.10.5"
            ],
            "v": "<1.10.5"
        }
    ],
    "semgrep": [
        {
            "advisory": "Semgrep 1.25.0 includes a fix for CVE-2023-32758: Giturlparse (aka git-url-parse) through 1.2.2, as used in Semgrep 1.5.2 through 1.24.1, is vulnerable to ReDoS (Regular Expression Denial of Service) if parsing untrusted URLs. This might be relevant if Semgrep is analyzing an untrusted package (for example, to check whether it accesses any Git repository at an http:// URL), and that package's author placed a ReDoS attack payload in a URL used by the package.",
            "cve": "CVE-2023-32758",
            "id": "pyup.io-58941",
            "more_info_path": "/vulnerabilities/CVE-2023-32758/58941",
            "specs": [
                ">=1.5.2,<1.25.0"
            ],
            "v": ">=1.5.2,<1.25.0"
        }
    ],
    "seml": [
        {
            "advisory": "In Seml versions before 0.3.5, a potential vulnerability exists related to the creation of temporary directories. The changelog for version 0.3.5 mentions the use of UUIDs to fix race conditions during temporary directory creation.\r\nhttps://github.com/TUM-DAML/seml/commit/d52bf495fd4d3ce1de4644b9a8d70de1615d21c6",
            "cve": "PVE-2023-62086",
            "id": "pyup.io-62086",
            "more_info_path": "/vulnerabilities/PVE-2023-62086/62086",
            "specs": [
                "<0.3.5"
            ],
            "v": "<0.3.5"
        }
    ],
    "semversioner": [
        {
            "advisory": "Semversioner 0.13.0 updates its dependency 'jinja2' to v2.11.3 to include a security fix.",
            "cve": "CVE-2020-28493",
            "id": "pyup.io-40118",
            "more_info_path": "/vulnerabilities/CVE-2020-28493/40118",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        }
    ],
    "senaite-core": [
        {
            "advisory": "Senaite-core version 1.3.0 prevents users without privileges to create reports.\r\nhttps://github.com/senaite/senaite.core/issues/896",
            "cve": "PVE-2021-41916",
            "id": "pyup.io-41916",
            "more_info_path": "/vulnerabilities/PVE-2021-41916/41916",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "senaite-queue": [
        {
            "advisory": "Senaite-queue version 1.0.3 improves the reindex security objects process.",
            "cve": "PVE-2021-41940",
            "id": "pyup.io-41940",
            "more_info_path": "/vulnerabilities/PVE-2021-41940/41940",
            "specs": [
                "<1.0.3"
            ],
            "v": "<1.0.3"
        }
    ],
    "sendgrid": [
        {
            "advisory": "Sendgrid 6.9.1 updates its dependency minimum 'starbank-ecdsa' to v2.0.1 to include a security fix.",
            "cve": "CVE-2021-43572",
            "id": "pyup.io-42721",
            "more_info_path": "/vulnerabilities/CVE-2021-43572/42721",
            "specs": [
                ">=6.4.1,<6.9.1"
            ],
            "v": ">=6.4.1,<6.9.1"
        }
    ],
    "sentence-transformers": [
        {
            "advisory": "Sentence-transformers affected versions are vulnerable to arbitrary code execution when loading PyTorch model files. The `torch.load()` function, used without the `weights_only=True` parameter, could deserialize malicious Python objects from manipulated model files. This vulnerability potentially allows attackers to execute arbitrary code on the system.",
            "cve": "PVE-2024-73169",
            "id": "pyup.io-73169",
            "more_info_path": "/vulnerabilities/PVE-2024-73169/73169",
            "specs": [
                "<3.1.0"
            ],
            "v": "<3.1.0"
        }
    ],
    "sentencepiece": [
        {
            "advisory": "Affected versions of the sentencepiece package are vulnerable to Heap-based Buffer Overflow due to passing non-null-terminated string data into trie construction without providing explicit key lengths. The issue occurs in PrefixMatcher::PrefixMatcher in src/normalizer.cc, where Darts::DoubleArray::build() is called with pointers from absl::string_view::data() and a nullptr length array, causing the trie builder to read past the intended buffer boundary when handling a specially crafted model-derived dictionary.",
            "cve": "CVE-2026-1260",
            "id": "pyup.io-85002",
            "more_info_path": "/vulnerabilities/CVE-2026-1260/85002",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "sentinelone": [
        {
            "advisory": "Sentinelone is a malicious package. It steals developer-related data.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-sentinelone-pypi-package-steals-data-from-developers",
            "cve": "PVE-2023-52927",
            "id": "pyup.io-52927",
            "more_info_path": "/vulnerabilities/PVE-2023-52927/52927",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "sentinelone-sdk": [
        {
            "advisory": "Sentinelone is a malicious package. It steals developer-related data.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-sentinelone-pypi-package-steals-data-from-developers",
            "cve": "PVE-2023-52927",
            "id": "pyup.io-55180",
            "more_info_path": "/vulnerabilities/PVE-2023-52927/55180",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "sentinelonesdk": [
        {
            "advisory": "Sentinelone is a malicious package. It steals developer-related data.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-sentinelone-pypi-package-steals-data-from-developers",
            "cve": "PVE-2023-52927",
            "id": "pyup.io-55181",
            "more_info_path": "/vulnerabilities/PVE-2023-52927/55181",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "sentry": [
        {
            "advisory": "Sentry 10.0.0 includes a security update for its dependency \"mixin-deep\".",
            "cve": "CVE-2019-10746",
            "id": "pyup.io-41974",
            "more_info_path": "/vulnerabilities/CVE-2019-10746/41974",
            "specs": [
                "<10.0.0"
            ],
            "v": "<10.0.0"
        },
        {
            "advisory": "Sentry 10.0.0 includes a security update for its dependency \"webpack-dev-server\".",
            "cve": "CVE-2018-14732",
            "id": "pyup.io-41972",
            "more_info_path": "/vulnerabilities/CVE-2018-14732/41972",
            "specs": [
                "<10.0.0"
            ],
            "v": "<10.0.0"
        },
        {
            "advisory": "Sentry 10.0.0 includes a security update for its dependency \"merge\".",
            "cve": "CVE-2018-16469",
            "id": "pyup.io-41975",
            "more_info_path": "/vulnerabilities/CVE-2018-16469/41975",
            "specs": [
                "<10.0.0"
            ],
            "v": "<10.0.0"
        },
        {
            "advisory": "Sentry 10.0.0 includes a security update for its dependency \"set-value\".",
            "cve": "CVE-2019-10747",
            "id": "pyup.io-41973",
            "more_info_path": "/vulnerabilities/CVE-2019-10747/41973",
            "specs": [
                "<10.0.0"
            ],
            "v": "<10.0.0"
        },
        {
            "advisory": "Sentry 20.6.0 updates its dependency \"pillow\" to include security fixes.",
            "cve": "CVE-2020-5311",
            "id": "pyup.io-41978",
            "more_info_path": "/vulnerabilities/CVE-2020-5311/41978",
            "specs": [
                "<20.6.0"
            ],
            "v": "<20.6.0"
        },
        {
            "advisory": "Sentry 20.6.0 updates its dependency \"pillow\" to include security fixes.",
            "cve": "CVE-2019-19911",
            "id": "pyup.io-41980",
            "more_info_path": "/vulnerabilities/CVE-2019-19911/41980",
            "specs": [
                "<20.6.0"
            ],
            "v": "<20.6.0"
        },
        {
            "advisory": "Sentry 20.6.0 updates its dependency \"pillow\" to include security fixes.",
            "cve": "CVE-2020-5313",
            "id": "pyup.io-41976",
            "more_info_path": "/vulnerabilities/CVE-2020-5313/41976",
            "specs": [
                "<20.6.0"
            ],
            "v": "<20.6.0"
        },
        {
            "advisory": "Sentry 20.6.0 updates its dependency \"pillow\" to include security fixes.",
            "cve": "CVE-2020-5312",
            "id": "pyup.io-41977",
            "more_info_path": "/vulnerabilities/CVE-2020-5312/41977",
            "specs": [
                "<20.6.0"
            ],
            "v": "<20.6.0"
        },
        {
            "advisory": "Sentry 20.6.0 updates its dependency \"pillow\" to include security fixes.",
            "cve": "CVE-2020-5310",
            "id": "pyup.io-41979",
            "more_info_path": "/vulnerabilities/CVE-2020-5310/41979",
            "specs": [
                "<20.6.0"
            ],
            "v": "<20.6.0"
        },
        {
            "advisory": "Sentry 21.11.0 validates that the issue alert owner is a member of the organization.\r\nhttps://github.com/getsentry/sentry/pull/29962",
            "cve": "PVE-2022-44565",
            "id": "pyup.io-44565",
            "more_info_path": "/vulnerabilities/PVE-2022-44565/44565",
            "specs": [
                "<21.11.0"
            ],
            "v": "<21.11.0"
        },
        {
            "advisory": "Sentry 21.2.0 updates its dependency \"websocket-extensions\" to a secure version.",
            "cve": "CVE-2020-7662",
            "id": "pyup.io-41971",
            "more_info_path": "/vulnerabilities/CVE-2020-7662/41971",
            "specs": [
                "<21.2.0"
            ],
            "v": "<21.2.0"
        },
        {
            "advisory": "Sentry 21.2.0 updates its dependency 'dot-prop' to a secure version.",
            "cve": "CVE-2020-8116",
            "id": "pyup.io-41970",
            "more_info_path": "/vulnerabilities/CVE-2020-8116/41970",
            "specs": [
                "<21.2.0"
            ],
            "v": "<21.2.0"
        },
        {
            "advisory": "Sentry 21.3.1 updates its dependency 'lxml' to v4.6.3 to include a security fix.",
            "cve": "CVE-2021-28957",
            "id": "pyup.io-41981",
            "more_info_path": "/vulnerabilities/CVE-2021-28957/41981",
            "specs": [
                "<21.3.1"
            ],
            "v": "<21.3.1"
        },
        {
            "advisory": "Sentry 21.3.1 updates its dependency \"pyyaml\" to include a security fix.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-41982",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/41982",
            "specs": [
                "<21.3.1"
            ],
            "v": "<21.3.1"
        },
        {
            "advisory": "Sentry 21.6.0 updates its dependency \"pillow\" to version 8.2.0 to include several security fixes.",
            "cve": "CVE-2021-28678",
            "id": "pyup.io-41986",
            "more_info_path": "/vulnerabilities/CVE-2021-28678/41986",
            "specs": [
                "<21.6.0"
            ],
            "v": "<21.6.0"
        },
        {
            "advisory": "Sentry 21.6.0 updates its dependency \"pillow\" to version 8.2.0 to include several security fixes.",
            "cve": "CVE-2021-28676",
            "id": "pyup.io-41988",
            "more_info_path": "/vulnerabilities/CVE-2021-28676/41988",
            "specs": [
                "<21.6.0"
            ],
            "v": "<21.6.0"
        },
        {
            "advisory": "Sentry 21.6.0 updates its dependency \"pillow\" to version 8.2.0 to include several security fixes.",
            "cve": "CVE-2021-28675",
            "id": "pyup.io-41987",
            "more_info_path": "/vulnerabilities/CVE-2021-28675/41987",
            "specs": [
                "<21.6.0"
            ],
            "v": "<21.6.0"
        },
        {
            "advisory": "Sentry 21.6.0 updates its dependency \"pillow\" to version 8.2.0 to include several security fixes.",
            "cve": "CVE-2021-28677",
            "id": "pyup.io-41989",
            "more_info_path": "/vulnerabilities/CVE-2021-28677/41989",
            "specs": [
                "<21.6.0"
            ],
            "v": "<21.6.0"
        },
        {
            "advisory": "Sentry 21.6.2 updates its NPM dependency \"color-string\" to v1.5.5 to include a security fix.\r\nhttps://github.com/getsentry/sentry/pull/26766",
            "cve": "CVE-2021-29060",
            "id": "pyup.io-41983",
            "more_info_path": "/vulnerabilities/CVE-2021-29060/41983",
            "specs": [
                "<21.6.2"
            ],
            "v": "<21.6.2"
        },
        {
            "advisory": "Sentry 21.9.0 updates its dependency 'Django' to v2.2.24 to include security fixes.",
            "cve": "CVE-2021-33571",
            "id": "pyup.io-41985",
            "more_info_path": "/vulnerabilities/CVE-2021-33571/41985",
            "specs": [
                "<21.9.0"
            ],
            "v": "<21.9.0"
        },
        {
            "advisory": "Sentry 21.9.0 updates its dependency \"django\" to version 2.2.24 to include security fixes.",
            "cve": "CVE-2021-33203",
            "id": "pyup.io-41984",
            "more_info_path": "/vulnerabilities/CVE-2021-33203/41984",
            "specs": [
                "<21.9.0"
            ],
            "v": "<21.9.0"
        },
        {
            "advisory": "Sentry before 6.1.1 is vulnerable to a remote code execution exploit. This only affects servers hosted public clients (e.g. raven.js).",
            "cve": "PVE-2021-26117",
            "id": "pyup.io-26117",
            "more_info_path": "/vulnerabilities/PVE-2021-26117/26117",
            "specs": [
                "<6.1.1"
            ],
            "v": "<6.1.1"
        },
        {
            "advisory": "Sentry before 7.4.0 has a XSS vulnerability with tag values not being escaped (on the group details page).\r\nhttps://github.com/getsentry/sentry/commit/626acc195003cea0d830eada4a338b60ba7ea614",
            "cve": "PVE-2021-26118",
            "id": "pyup.io-26118",
            "more_info_path": "/vulnerabilities/PVE-2021-26118/26118",
            "specs": [
                "<7.4.0"
            ],
            "v": "<7.4.0"
        },
        {
            "advisory": "Sentry 7.7.0 includes a fix for a XSS vulnerability present in tags and the stream filter box.\r\nhttps://github.com/getsentry/sentry/commit/364b959811561de83f29893e105cc590224edbee",
            "cve": "PVE-2021-26120",
            "id": "pyup.io-26120",
            "more_info_path": "/vulnerabilities/PVE-2021-26120/26120",
            "specs": [
                "<7.7.0"
            ],
            "v": "<7.7.0"
        },
        {
            "advisory": "sentry before 8.1.4 has a security issue where a superuser had the ability to inject data into audit logs through the admin UI.",
            "cve": "PVE-2021-26121",
            "id": "pyup.io-26121",
            "more_info_path": "/vulnerabilities/PVE-2021-26121/26121",
            "specs": [
                "<8.1.4"
            ],
            "v": "<8.1.4"
        },
        {
            "advisory": "sentry before 8.1.5 if being run in multi-organization mode, it was possible for a user to craft a URL which would allow them to view membership details of other users.",
            "cve": "PVE-2021-26122",
            "id": "pyup.io-26122",
            "more_info_path": "/vulnerabilities/PVE-2021-26122/26122",
            "specs": [
                "<8.1.5"
            ],
            "v": "<8.1.5"
        },
        {
            "advisory": "sentry before 8.2.2 has a security issue where a superuser had the ability to inject data into audit logs through the admin UI.",
            "cve": "PVE-2021-26123",
            "id": "pyup.io-26123",
            "more_info_path": "/vulnerabilities/PVE-2021-26123/26123",
            "specs": [
                "<8.2.2"
            ],
            "v": "<8.2.2"
        },
        {
            "advisory": "Sentry 8.2.4 fixes a bug which allowed a user to craft a URL which would permit them to view membership details of other users, if sentry was being run in multi-organization mode.\r\nhttps://github.com/getsentry/sentry/commit/415ad476ed90980f583c43fd92d40e83b16bdbe3",
            "cve": "PVE-2021-26124",
            "id": "pyup.io-26124",
            "more_info_path": "/vulnerabilities/PVE-2021-26124/26124",
            "specs": [
                "<8.2.4"
            ],
            "v": "<8.2.4"
        },
        {
            "advisory": "Sentry 8.2.5 and 8.3.3 fix a bug which allowed API keys more permission than granted within the organization.\r\nhttps://github.com/getsentry/sentry/pull/3134",
            "cve": "PVE-2021-26125",
            "id": "pyup.io-26125",
            "more_info_path": "/vulnerabilities/PVE-2021-26125/26125",
            "specs": [
                "<8.2.5",
                ">=8.3.0,<8.3.3"
            ],
            "v": "<8.2.5,>=8.3.0,<8.3.3"
        },
        {
            "advisory": "Sentry 8.4.1 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/getsentry/sentry/commit/04a2027a13c9ffd17fb190126fb8fa36c11d91c7",
            "cve": "PVE-2023-59554",
            "id": "pyup.io-59554",
            "more_info_path": "/vulnerabilities/PVE-2023-59554/59554",
            "specs": [
                "<8.4.1"
            ],
            "v": "<8.4.1"
        },
        {
            "advisory": "Sentry 8.8 includes various security fixes related to CSRF and XSS.\r\nhttps://github.com/getsentry/sentry/commit/33d5aa268e4a6dee5c27daa4d6ebe32d384c4d7a",
            "cve": "PVE-2021-26127",
            "id": "pyup.io-26127",
            "more_info_path": "/vulnerabilities/PVE-2021-26127/26127",
            "specs": [
                "<8.8"
            ],
            "v": "<8.8"
        },
        {
            "advisory": "Sentry 9.0.0rc1 includes a fix for CVE-2016-7401 (backported from Django 1.8.15).",
            "cve": "CVE-2016-7401",
            "id": "pyup.io-41830",
            "more_info_path": "/vulnerabilities/CVE-2016-7401/41830",
            "specs": [
                "<9.0.0rc1"
            ],
            "v": "<9.0.0rc1"
        },
        {
            "advisory": "Affected versions of Sentry are vulnerable to Information Exposure Through Error Messages (CWE-209). When handling invalid responses from third-party integrations, the Search UI component exposes Client ID and Secret credentials in error messages. This occurs when async search components receive invalid third-party responses, triggered through the SelectRequester class. Though exploitation requires specific validation failures and additional API tokens for full access, it risks exposing integration secrets. Fixed in version 24.11.1 by restructuring error handling and implementing proper error message sanitization.",
            "cve": "CVE-2024-53253",
            "id": "pyup.io-74440",
            "more_info_path": "/vulnerabilities/CVE-2024-53253/74440",
            "specs": [
                "==24.11.0"
            ],
            "v": "==24.11.0"
        },
        {
            "advisory": "Affected versions of this package contain an open redirect vulnerability stemming from the 'API Applications' feature's OAuth endpoint. Specifically, if an error arises during OAuth processing, the application will redirect users to a URL specified by the attacker without requiring confirmation, thereby facilitating phishing attacks or the potential for more severe exploits due to combined vulnerabilities.",
            "cve": "PVE-2024-99875",
            "id": "pyup.io-65545",
            "more_info_path": "/vulnerabilities/PVE-2024-99875/65545",
            "specs": [
                ">=0,<20.12.1"
            ],
            "v": ">=0,<20.12.1"
        },
        {
            "advisory": "Various versions of a software package are susceptible to a Regular Expression Denial of Service (ReDoS) vulnerability. This issue arises due to the usage of insecure regex patterns in specific fields, which can be exploited by submitting a string with an excessive number of underscores. This exploitation could lead to an excessive consumption of CPU resources, rendering the system unresponsive and inaccessible to legitimate users.",
            "cve": "PVE-2024-99874",
            "id": "pyup.io-65546",
            "more_info_path": "/vulnerabilities/PVE-2024-99874/65546",
            "specs": [
                ">=0,<22.6.0"
            ],
            "v": ">=0,<22.6.0"
        },
        {
            "advisory": "Sentry is susceptible to Cross-site Scripting (XSS) attacks due to the lack of user input escaping in the z function, impacting versions within an explicit range.",
            "cve": "PVE-2024-99872",
            "id": "pyup.io-65548",
            "more_info_path": "/vulnerabilities/PVE-2024-99872/65548",
            "specs": [
                ">=0,<5.4.4"
            ],
            "v": ">=0,<5.4.4"
        },
        {
            "advisory": "Versions of Sentry are vulnerable to Cross-site Scripting (XSS) due to insufficient escaping in jQuery ajax completion dropdowns.",
            "cve": "PVE-2024-99871",
            "id": "pyup.io-65549",
            "more_info_path": "/vulnerabilities/PVE-2024-99871/65549",
            "specs": [
                ">=0,<5.4.4"
            ],
            "v": ">=0,<5.4.4"
        },
        {
            "advisory": "This vulnerability impacts versions of Sentry and allows for Cross-site Scripting (XSS) attacks through manipulation of the project name field.",
            "cve": "PVE-2024-99870",
            "id": "pyup.io-65550",
            "more_info_path": "/vulnerabilities/PVE-2024-99870/65550",
            "specs": [
                ">=0,<7.0.0"
            ],
            "v": ">=0,<7.0.0"
        },
        {
            "advisory": "Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 23.7.2, an attacker with sufficient client-side exploits could retrieve a valid access token for another user during the OAuth token exchange due to incorrect credential validation. The client ID must be known and the API application must have already been authorized on the targeted user account. Sentry SaaS customers do not need to take any action. Self-hosted installations should upgrade to version 23.7.2 or higher. There are no direct workarounds, but users should review applications authorized on their account and remove any that are no longer needed.",
            "cve": "CVE-2023-39531",
            "id": "pyup.io-65050",
            "more_info_path": "/vulnerabilities/CVE-2023-39531/65050",
            "specs": [
                ">=10.0.0,<23.7.2"
            ],
            "v": ">=10.0.0,<23.7.2"
        },
        {
            "advisory": "An unsanitized payload sent by an Integration platform integration allows the storage of arbitrary HTML tags on the Sentry side. This payload could subsequently be rendered on the Issues page, creating a Stored Cross-Site Scripting (XSS) vulnerability. This vulnerability might lead to the execution of arbitrary scripts in the context of a user\u2019s browser. Self-hosted Sentry users may be impacted if untrustworthy Integration platform integrations send external issues to their Sentry instance.",
            "cve": "CVE-2024-41656",
            "id": "pyup.io-72350",
            "more_info_path": "/vulnerabilities/CVE-2024-41656/72350",
            "specs": [
                ">=10.0.0,<24.7.1"
            ],
            "v": ">=10.0.0,<24.7.1"
        },
        {
            "advisory": "A critical vulnerability was discovered in the SAML SSO implementation of Sentry. It was reported to us via our private bug bounty program. The vulnerability allows an attacker to take over any user account by using a malicious SAML Identity Provider and another organization on the same Sentry instance. The victim's email address must be known to exploit this vulnerability.",
            "cve": "CVE-2025-22146",
            "id": "pyup.io-76359",
            "more_info_path": "/vulnerabilities/CVE-2025-22146/76359",
            "specs": [
                ">=21.12.0,<25.1.0"
            ],
            "v": ">=21.12.0,<25.1.0"
        },
        {
            "advisory": "Sentry is an error tracking and performance monitoring platform. Starting in version 22.1.0 and prior to version 23.7.2, an attacker with access to a token with few or no scopes can query `/api/0/api-tokens/` for a list of all tokens created by a user, including tokens with greater scopes, and use those tokens in other requests. There is no evidence that the issue was exploited on `sentry.io`. For self-hosted users, it is advised to rotate user auth tokens. A fix is available in version 23.7.2 of `sentry` and `self-hosted`. There are no known workarounds.",
            "cve": "CVE-2023-39349",
            "id": "pyup.io-65049",
            "more_info_path": "/vulnerabilities/CVE-2023-39349/65049",
            "specs": [
                ">=22.1.0,<23.7.2"
            ],
            "v": ">=22.1.0,<23.7.2"
        },
        {
            "advisory": "Sentry 22.11.0 includes a fix for CVE-2022-23485: In versions of the sentry python library prior to 22.11.0 an attacker with a known valid invite link could manipulate a cookie to allow the same invite link to be reused on multiple accounts when joining an organization. As a result an attacker with a valid invite link can create multiple users and join an organization they may not have been originally invited to. Sentry SaaS customers do not need to take action. Self-hosted Sentry installs on systems which can not upgrade can disable the invite functionality until they are ready to deploy the patched version by editing their 'sentry.conf.py' file (usually located at '~/.sentry/').\r\nhttps://github.com/getsentry/sentry/security/advisories/GHSA-jv85-mqxj-3f9j",
            "cve": "CVE-2022-23485",
            "id": "pyup.io-52383",
            "more_info_path": "/vulnerabilities/CVE-2022-23485/52383",
            "specs": [
                ">=22.6.0,<=22.10.0"
            ],
            "v": ">=22.6.0,<=22.10.0"
        },
        {
            "advisory": "A vulnerability in Sentry affected versions enables authenticated users to mute alert rules from arbitrary organizations and projects using known rule IDs, bypassing proper authorization checks. This flaw allows unauthorized access and potential disruption of alert systems across multiple organizations. Although Sentry has not detected any exploits, the vulnerability could permit malicious actors to silence critical alerts without detection, potentially causing severe impact. Sentry has patched this vulnerability, implementing proper authorization scoping for alert rule muting requests.\r\nNOTE: While Sentry automatically protects SaaS users, all self-hosted Sentry users must upgrade to version 24.9.0 or higher immediately.",
            "cve": "CVE-2024-45606",
            "id": "pyup.io-73296",
            "more_info_path": "/vulnerabilities/CVE-2024-45606/73296",
            "specs": [
                ">=23.4.0,<24.9.0"
            ],
            "v": ">=23.4.0,<24.9.0"
        },
        {
            "advisory": "Sentry is an error tracking and performance monitoring platform. Starting in version 23.6.0 and prior to version 23.6.2, the Sentry API incorrectly returns the `access-control-allow-credentials: true` HTTP header if the `Origin` request header ends with the `system.base-hostname` option of Sentry installation. This only affects installations that have `system.base-hostname` option explicitly set, as it is empty by default. Impact is limited since recent versions of major browsers have cross-site cookie blocking enabled by default. However, this flaw could allow other multi-step attacks. The patch has been released in Sentry 23.6.2.",
            "cve": "PVE-2024-99897",
            "id": "pyup.io-64993",
            "more_info_path": "/vulnerabilities/PVE-2024-99897/64993",
            "specs": [
                ">=23.6.0,<23.6.2"
            ],
            "v": ">=23.6.0,<23.6.2"
        },
        {
            "advisory": "The Sentry API incorrectly returns the access-control-allow-credentials: true HTTP header if the Origin request header ends with the system.base-hostname option of Sentry installation. This only affects installations that have system.base-hostname option explicitly set, as it is empty by default. The impact is limited since recent versions of major browsers have cross-site cookie blocking enabled by default. However, this flaw could allow other multi-step attacks.",
            "cve": "CVE-2023-36829",
            "id": "pyup.io-71984",
            "more_info_path": "/vulnerabilities/CVE-2023-36829/71984",
            "specs": [
                ">=23.6.0,<23.6.2"
            ],
            "v": ">=23.6.0,<23.6.2"
        },
        {
            "advisory": "A critical vulnerability in Sentry affected versions allowed authenticated users to delete notification settings of any user by supplying the setting's ID. This Insecure Direct Object Reference (IDOR) flaw enabled malicious actors to manipulate other users' notification preferences, potentially causing missed critical alerts. Insufficient authorization checks when deleting notification setting options caused this vulnerability. Sentry has patched this issue, implementing proper user-based access controls and validation. \r\nNOTE: While Sentry automatically protects SaaS users, all self-hosted Sentry users must upgrade to version 24.9.0 or higher immediately.",
            "cve": "CVE-2024-45605",
            "id": "pyup.io-73297",
            "more_info_path": "/vulnerabilities/CVE-2024-45605/73297",
            "specs": [
                ">=23.9.0,<24.9.0"
            ],
            "v": ">=23.9.0,<24.9.0"
        },
        {
            "advisory": "When authenticating as a superuser to a self-hosted Sentry instance with a username and password, the password is leaked as cleartext in logs under the event: auth-index.validate_superuser. An attacker with access to the log data could use these leaked credentials to log in to the Sentry system as a superuser.",
            "cve": "CVE-2024-32474",
            "id": "pyup.io-71926",
            "more_info_path": "/vulnerabilities/CVE-2024-32474/71926",
            "specs": [
                ">=24.3.0,<24.4.1"
            ],
            "v": ">=24.3.0,<24.4.1"
        },
        {
            "advisory": "Affected versions of the sentry package are vulnerable to Information Disclosure due to sensitive request bodies being erroneously logged by the Slack integration. The `sentry.integrations.slack` logger records the full incoming request body\u2014including the deprecated Slack verification token\u2014when handling `slack.*` events, without filtering or redaction. An attacker able to access the logs in self-hosted deployments could potentially retrieve this verification token and use it to forge Slack requests, effectively impersonating the Slack integration. \r\n#Note: This issue affects only the Slack integration.",
            "cve": "CVE-2024-35196",
            "id": "pyup.io-78732",
            "more_info_path": "/vulnerabilities/CVE-2024-35196/78732",
            "specs": [
                ">=24.3.0,<24.5.0"
            ],
            "v": ">=24.3.0,<24.5.0"
        },
        {
            "advisory": "Certain versions of Sentry are susceptible to Denial of Service (DoS) attacks due to the absence of a limit on the number of organizations that can be sent. This can lead to system hangs when an excessively large number of organizations are submitted.",
            "cve": "PVE-2024-99868",
            "id": "pyup.io-65552",
            "more_info_path": "/vulnerabilities/PVE-2024-99868/65552",
            "specs": [
                ">=6.4.0,<8.0.0rc2"
            ],
            "v": ">=6.4.0,<8.0.0rc2"
        },
        {
            "advisory": "Various versions of Sentry are susceptible to Cross-site Scripting (XSS) attacks due to the lack of user input sanitization when adding labels to widgets.",
            "cve": "PVE-2024-99869",
            "id": "pyup.io-65551",
            "more_info_path": "/vulnerabilities/PVE-2024-99869/65551",
            "specs": [
                ">=7.1.0,<7.4.0"
            ],
            "v": ">=7.1.0,<7.4.0"
        },
        {
            "advisory": "Selected versions of Sentry are vulnerable to cross-site scripting (XSS) attacks through the deserialization process in the project selector, allowing attackers to inject and execute arbitrary scripts via the Sentry API.",
            "cve": "PVE-2024-99873",
            "id": "pyup.io-65547",
            "more_info_path": "/vulnerabilities/PVE-2024-99873/65547",
            "specs": [
                ">=8.0.0rc1,<8.7.0"
            ],
            "v": ">=8.0.0rc1,<8.7.0"
        },
        {
            "advisory": "Selected versions of Sentry are exposed to a Denial of Service (DoS) threat due to the absence of password length validation. Long passwords can overload the hashing algorithm, leading to potential service disruption.",
            "cve": "PVE-2024-99867",
            "id": "pyup.io-65553",
            "more_info_path": "/vulnerabilities/PVE-2024-99867/65553",
            "specs": [
                ">=8.11,<8.15.0"
            ],
            "v": ">=8.11,<8.15.0"
        },
        {
            "advisory": "Sentry is an error tracking and performance monitoring platform. Starting in version 8.21.0 and prior to version 23.5.2, an authenticated user can download a debug or artifact bundle from arbitrary organizations and projects with a known bundle ID. The user does not need to be a member of the organization or have permissions on the project. A patch was issued in version 23.5.2 to ensure authorization checks are properly scoped on requests to retrieve debug or artifact bundles. Authenticated users who do not have the necessary permissions on the particular project are no longer able to download them. Sentry SaaS users do not need to take any action. Self-Hosted Sentry users should upgrade to version 23.5.2 or higher.",
            "cve": "CVE-2023-36826",
            "id": "pyup.io-65048",
            "more_info_path": "/vulnerabilities/CVE-2023-36826/65048",
            "specs": [
                ">=8.21.0,<23.5.2"
            ],
            "v": ">=8.21.0,<23.5.2"
        },
        {
            "advisory": "Sentry is an error tracking and performance monitoring platform. Sentry\u2019s integration platform provides a way for external services to interact with Sentry. One of such integrations, the Phabricator integration (maintained by Sentry) with version <=24.1.1 contains a constrained SSRF vulnerability. An attacker could make Sentry send POST HTTP requests to arbitrary URLs (including internal IP addresses) by providing an unsanitized input to the Phabricator integration. However, the body payload is constrained to a specific format. If an attacker has access to a Sentry instance, this allows them to: 1. interact with internal network; 2. scan local/remote ports. This issue has been fixed in Sentry self-hosted release 24.1.2, and has already been mitigated on sentry.io on February 8. Users are advised to upgrade. There are no known workarounds for this vulnerability.",
            "cve": "CVE-2024-24829",
            "id": "pyup.io-66735",
            "more_info_path": "/vulnerabilities/CVE-2024-24829/66735",
            "specs": [
                ">=9.1.0,<24.1.2"
            ],
            "v": ">=9.1.0,<24.1.2"
        }
    ],
    "sentry-cli": [
        {
            "advisory": "Sentry-cli 1.47.0 trims whitespaces in header values to prevent potential header injections through the auth token header.",
            "cve": "PVE-2023-53525",
            "id": "pyup.io-53525",
            "more_info_path": "/vulnerabilities/PVE-2023-53525/53525",
            "specs": [
                "<1.47.0"
            ],
            "v": "<1.47.0"
        },
        {
            "advisory": "Sentry-cli version 1.75.0 has replaced the npmlog dependency to mitigate a known security vulnerability, enhancing the tool's security posture.\r\nhttps://github.com/getsentry/sentry-cli/pull/1445/commits/f5dcc3fddc7a0252e247f767f8db2fbfbf76ccaa",
            "cve": "PVE-2024-65115",
            "id": "pyup.io-65115",
            "more_info_path": "/vulnerabilities/PVE-2024-65115/65115",
            "specs": [
                "<1.75.0"
            ],
            "v": "<1.75.0"
        }
    ],
    "sentry-sdk": [
        {
            "advisory": "Sentry-sdk 1.14.0 includes a fix for CVE-2023-28117: When using the Django integration of versions prior to 1.14.0 of the Sentry SDK in a specific configuration it is possible to leak sensitive cookies values, including the session cookie to Sentry. These sensitive cookies could then be used by someone with access to your Sentry issues to impersonate or escalate their privileges within your application. In order for these sensitive values to be leaked, the Sentry SDK configuration must have 'sendDefaultPII' set to 'True'; one must use a custom name for either 'SESSION_COOKIE_NAME' or 'CSRF_COOKIE_NAME' in one's Django settings; and one must not be configured in one's organization or project settings to use Sentry's data scrubbing features to account for the custom cookie names. As of version 1.14.0, the Django integration of the 'sentry-sdk' will detect the custom cookie names based on one's Django settings and will remove the values from the payload before sending the data to Sentry. As a workaround, use the SDK's filtering mechanism to remove the cookies from the payload that is sent to Sentry. For error events, this can be done with the 'before_send' callback method and for performance related events (transactions) one can use the 'before_send_transaction' callback method. Those who want to handle filtering of these values on the server-side can also use Sentry's advanced data scrubbing feature to account for the custom cookie names. Look for the '$http.cookies', '$http.headers', '$request.cookies', or '$request.headers' fields to target with a scrubbing rule.\r\nhttps://github.com/getsentry/sentry-python/security/advisories/GHSA-29pr-6jr8-q5jm",
            "cve": "CVE-2023-28117",
            "id": "pyup.io-53812",
            "more_info_path": "/vulnerabilities/CVE-2023-28117/53812",
            "specs": [
                "<1.14.0"
            ],
            "v": "<1.14.0"
        },
        {
            "advisory": "Sentry-sdk 1.4.1 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/getsentry/sentry-python/pull/1203",
            "cve": "PVE-2023-59553",
            "id": "pyup.io-59553",
            "more_info_path": "/vulnerabilities/PVE-2023-59553/59553",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        },
        {
            "advisory": "Affected versions of Sentry's Python SDK are vulnerable to unintentional exposure of environment variables to subprocesses despite the env={} setting. In Python's 'subprocess' calls, all environment variables are passed to subprocesses by default. However, if you specifically do not want them to be passed to subprocesses, you may use 'env' argument in 'subprocess' calls. Due to the bug in Sentry SDK, with the Stdlib integration enabled (which is enabled by default), this expectation is not fulfilled, and all environment variables are being passed to subprocesses instead. \r\nAs a workaround, and if passing environment variables to child processes poses a security risk for you, you can disable all default integrations.",
            "cve": "CVE-2024-40647",
            "id": "pyup.io-72260",
            "more_info_path": "/vulnerabilities/CVE-2024-40647/72260",
            "specs": [
                "<2.8.0"
            ],
            "v": "<2.8.0"
        }
    ],
    "sequoia-client-sdk": [
        {
            "advisory": "sequoia-client-sdk 1.2.0 upgrades libraries `urllib3` and `requests` upgraded to solve security issues:",
            "cve": "PVE-2021-36949",
            "id": "pyup.io-36949",
            "more_info_path": "/vulnerabilities/PVE-2021-36949/36949",
            "specs": [
                "<1.2.0"
            ],
            "v": "<1.2.0"
        },
        {
            "advisory": "Sequoia-client-sdk 2.0.0 updates its dependency 'urllib3' to versions 1.25.* to include security fixes.",
            "cve": "CVE-2019-11324",
            "id": "pyup.io-37199",
            "more_info_path": "/vulnerabilities/CVE-2019-11324/37199",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        },
        {
            "advisory": "Sequoia-client-sdk 2.0.0 updates its dependency 'urllib3' to versions 1.25.* to include security fixes.",
            "cve": "CVE-2019-11236",
            "id": "pyup.io-45400",
            "more_info_path": "/vulnerabilities/CVE-2019-11236/45400",
            "specs": [
                "<2.0.0"
            ],
            "v": "<2.0.0"
        }
    ],
    "serialix": [
        {
            "advisory": "Serialix 2.1.1a1 sanitizes some properties in .core.BaseLang.\r\nhttps://github.com/maximilionus/serialix/commit/c64170419b1eeb09e1b5433baa18783c5e3c90bd",
            "cve": "PVE-2022-45391",
            "id": "pyup.io-45391",
            "more_info_path": "/vulnerabilities/PVE-2022-45391/45391",
            "specs": [
                "<2.1.1a1"
            ],
            "v": "<2.1.1a1"
        },
        {
            "advisory": "Serialix 2.1.2 fixed possible code injection vulnerability in setup.py.\r\nhttps://github.com/maximilionus/serialix/commit/4efef5619aa6f1f7dc85aafefabf649b8841e63e",
            "cve": "PVE-2022-45480",
            "id": "pyup.io-45480",
            "more_info_path": "/vulnerabilities/PVE-2022-45480/45480",
            "specs": [
                "<2.1.2"
            ],
            "v": "<2.1.2"
        }
    ],
    "serpscrap": [
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-17461",
            "id": "pyup.io-45073",
            "more_info_path": "/vulnerabilities/CVE-2018-17461/45073",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'sqlalchemy' to v1.3.7 to include security fixes.",
            "cve": "CVE-2019-7548",
            "id": "pyup.io-45100",
            "more_info_path": "/vulnerabilities/CVE-2019-7548/45100",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'lxml' to v4.3.2 to include a security fix.",
            "cve": "CVE-2018-19787",
            "id": "pyup.io-45099",
            "more_info_path": "/vulnerabilities/CVE-2018-19787/45099",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'sqlalchemy' to v1.3.7 to include security fixes.",
            "cve": "CVE-2019-7164",
            "id": "pyup.io-45101",
            "more_info_path": "/vulnerabilities/CVE-2019-7164/45101",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-17458",
            "id": "pyup.io-45070",
            "more_info_path": "/vulnerabilities/CVE-2018-17458/45070",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16076",
            "id": "pyup.io-45086",
            "more_info_path": "/vulnerabilities/CVE-2018-16076/45086",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16086",
            "id": "pyup.io-45096",
            "more_info_path": "/vulnerabilities/CVE-2018-16086/45096",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6136",
            "id": "pyup.io-45056",
            "more_info_path": "/vulnerabilities/CVE-2018-6136/45056",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16088",
            "id": "pyup.io-45098",
            "more_info_path": "/vulnerabilities/CVE-2018-16088/45098",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-17457",
            "id": "pyup.io-45069",
            "more_info_path": "/vulnerabilities/CVE-2018-17457/45069",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-17460",
            "id": "pyup.io-45072",
            "more_info_path": "/vulnerabilities/CVE-2018-17460/45072",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6135",
            "id": "pyup.io-45055",
            "more_info_path": "/vulnerabilities/CVE-2018-6135/45055",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6137",
            "id": "pyup.io-45057",
            "more_info_path": "/vulnerabilities/CVE-2018-6137/45057",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6125",
            "id": "pyup.io-45045",
            "more_info_path": "/vulnerabilities/CVE-2018-6125/45045",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6148",
            "id": "pyup.io-45067",
            "more_info_path": "/vulnerabilities/CVE-2018-6148/45067",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16073",
            "id": "pyup.io-45083",
            "more_info_path": "/vulnerabilities/CVE-2018-16073/45083",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6129",
            "id": "pyup.io-45049",
            "more_info_path": "/vulnerabilities/CVE-2018-6129/45049",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6142",
            "id": "pyup.io-45062",
            "more_info_path": "/vulnerabilities/CVE-2018-6142/45062",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6130",
            "id": "pyup.io-45050",
            "more_info_path": "/vulnerabilities/CVE-2018-6130/45050",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16075",
            "id": "pyup.io-45085",
            "more_info_path": "/vulnerabilities/CVE-2018-16075/45085",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16077",
            "id": "pyup.io-45087",
            "more_info_path": "/vulnerabilities/CVE-2018-16077/45087",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16074",
            "id": "pyup.io-45084",
            "more_info_path": "/vulnerabilities/CVE-2018-16074/45084",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16082",
            "id": "pyup.io-45092",
            "more_info_path": "/vulnerabilities/CVE-2018-16082/45092",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16085",
            "id": "pyup.io-45095",
            "more_info_path": "/vulnerabilities/CVE-2018-16085/45095",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16065",
            "id": "pyup.io-45075",
            "more_info_path": "/vulnerabilities/CVE-2018-16065/45075",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16079",
            "id": "pyup.io-45089",
            "more_info_path": "/vulnerabilities/CVE-2018-16079/45089",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16080",
            "id": "pyup.io-45090",
            "more_info_path": "/vulnerabilities/CVE-2018-16080/45090",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16084",
            "id": "pyup.io-45094",
            "more_info_path": "/vulnerabilities/CVE-2018-16084/45094",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6145",
            "id": "pyup.io-45065",
            "more_info_path": "/vulnerabilities/CVE-2018-6145/45065",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6143",
            "id": "pyup.io-45063",
            "more_info_path": "/vulnerabilities/CVE-2018-6143/45063",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16068",
            "id": "pyup.io-45078",
            "more_info_path": "/vulnerabilities/CVE-2018-16068/45078",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6134",
            "id": "pyup.io-45054",
            "more_info_path": "/vulnerabilities/CVE-2018-6134/45054",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6132",
            "id": "pyup.io-45052",
            "more_info_path": "/vulnerabilities/CVE-2018-6132/45052",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6133",
            "id": "pyup.io-45053",
            "more_info_path": "/vulnerabilities/CVE-2018-6133/45053",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16066",
            "id": "pyup.io-45076",
            "more_info_path": "/vulnerabilities/CVE-2018-16066/45076",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16070",
            "id": "pyup.io-45080",
            "more_info_path": "/vulnerabilities/CVE-2018-16070/45080",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16071",
            "id": "pyup.io-45081",
            "more_info_path": "/vulnerabilities/CVE-2018-16071/45081",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16072",
            "id": "pyup.io-45082",
            "more_info_path": "/vulnerabilities/CVE-2018-16072/45082",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16081",
            "id": "pyup.io-45091",
            "more_info_path": "/vulnerabilities/CVE-2018-16081/45091",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16069",
            "id": "pyup.io-45079",
            "more_info_path": "/vulnerabilities/CVE-2018-16069/45079",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16064",
            "id": "pyup.io-45074",
            "more_info_path": "/vulnerabilities/CVE-2018-16064/45074",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6149",
            "id": "pyup.io-45068",
            "more_info_path": "/vulnerabilities/CVE-2018-6149/45068",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6140",
            "id": "pyup.io-45060",
            "more_info_path": "/vulnerabilities/CVE-2018-6140/45060",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16087",
            "id": "pyup.io-45097",
            "more_info_path": "/vulnerabilities/CVE-2018-16087/45097",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6127",
            "id": "pyup.io-45047",
            "more_info_path": "/vulnerabilities/CVE-2018-6127/45047",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-17459",
            "id": "pyup.io-45071",
            "more_info_path": "/vulnerabilities/CVE-2018-17459/45071",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16067",
            "id": "pyup.io-45077",
            "more_info_path": "/vulnerabilities/CVE-2018-16067/45077",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16078",
            "id": "pyup.io-45088",
            "more_info_path": "/vulnerabilities/CVE-2018-16078/45088",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-16083",
            "id": "pyup.io-45093",
            "more_info_path": "/vulnerabilities/CVE-2018-16083/45093",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6139",
            "id": "pyup.io-45059",
            "more_info_path": "/vulnerabilities/CVE-2018-6139/45059",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6128",
            "id": "pyup.io-45048",
            "more_info_path": "/vulnerabilities/CVE-2018-6128/45048",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6144",
            "id": "pyup.io-45064",
            "more_info_path": "/vulnerabilities/CVE-2018-6144/45064",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6141",
            "id": "pyup.io-45061",
            "more_info_path": "/vulnerabilities/CVE-2018-6141/45061",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6126",
            "id": "pyup.io-45046",
            "more_info_path": "/vulnerabilities/CVE-2018-6126/45046",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6123",
            "id": "pyup.io-37406",
            "more_info_path": "/vulnerabilities/CVE-2018-6123/37406",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6131",
            "id": "pyup.io-45051",
            "more_info_path": "/vulnerabilities/CVE-2018-6131/45051",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6147",
            "id": "pyup.io-45066",
            "more_info_path": "/vulnerabilities/CVE-2018-6147/45066",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6138",
            "id": "pyup.io-45058",
            "more_info_path": "/vulnerabilities/CVE-2018-6138/45058",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Serpscrap 0.13.0 updates its dependency 'chromedriver' to a version >= 76.0.3809.68 to include security fixes.",
            "cve": "CVE-2018-6124",
            "id": "pyup.io-45044",
            "more_info_path": "/vulnerabilities/CVE-2018-6124/45044",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        }
    ],
    "serverlla": [
        {
            "advisory": "Serverlla version 1.23 uses HTTPS when connecting to a website to obtain the public IP.",
            "cve": "PVE-2021-41954",
            "id": "pyup.io-41954",
            "more_info_path": "/vulnerabilities/PVE-2021-41954/41954",
            "specs": [
                "<1.23"
            ],
            "v": "<1.23"
        }
    ],
    "service-affinity-scheduling": [
        {
            "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'service-affinity-scheduling' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.",
            "cve": "PVE-2024-74234",
            "id": "pyup.io-74234",
            "more_info_path": "/vulnerabilities/PVE-2024-74234/74234",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "sesame": [
        {
            "advisory": "sesame 0.3.0 is using a secure extraction/decryption using tempfile.",
            "cve": "PVE-2021-26128",
            "id": "pyup.io-26128",
            "more_info_path": "/vulnerabilities/PVE-2021-26128/26128",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "setriq": [
        {
            "advisory": "Setriq 1.0.0 updates its dependency 'semantic-release' to v17.2.3 to include a security fix.\r\nhttps://github.com/BenTenmann/setriq/commit/c1d4f380568933fb6e5b2c70a5e42ad36dbc103a",
            "cve": "CVE-2020-26226",
            "id": "pyup.io-43432",
            "more_info_path": "/vulnerabilities/CVE-2020-26226/43432",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "setup-tools": [
        {
            "advisory": "setup-tools  is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/",
            "cve": "PVE-2021-34984",
            "id": "pyup.io-34984",
            "more_info_path": "/vulnerabilities/PVE-2021-34984/34984",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "setupbox": [
        {
            "advisory": "SetupBox throughout 1.0 allows absolute path traversal because the Flask send_file function is used unsafely. See CVE-2022-31543.",
            "cve": "CVE-2022-31543",
            "id": "pyup.io-50055",
            "more_info_path": "/vulnerabilities/CVE-2022-31543/50055",
            "specs": [
                "<=1.0"
            ],
            "v": "<=1.0"
        }
    ],
    "setuptools": [
        {
            "advisory": "Setuptools version 0.7 includes a fix for CVE-2013-1633: Easy_install in setuptools before 0.7 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which allows man-in-the-middle attackers to execute arbitrary code via a crafted response to the default use of the product.",
            "cve": "CVE-2013-1633",
            "id": "pyup.io-25809",
            "more_info_path": "/vulnerabilities/CVE-2013-1633/25809",
            "specs": [
                "<0.7"
            ],
            "v": "<0.7"
        },
        {
            "advisory": "setuptools 0.9.5 fixes a security vulnerability in SSL certificate validation.",
            "cve": "PVE-2021-26129",
            "id": "pyup.io-26129",
            "more_info_path": "/vulnerabilities/PVE-2021-26129/26129",
            "specs": [
                "<0.9.5"
            ],
            "v": "<0.9.5"
        },
        {
            "advisory": "Setuptools before 1.3 has a security vulnerability in SSL match_hostname check, similar to CVE-2013-7440.",
            "cve": "PVE-2021-26132",
            "id": "pyup.io-26132",
            "more_info_path": "/vulnerabilities/PVE-2021-26132/26132",
            "specs": [
                "<1.3"
            ],
            "v": "<1.3"
        },
        {
            "advisory": "setuptools 3.0 avoids the potential security vulnerabilities presented by use of tar archives in ez_setup.py. It also leverages the security features added to ZipFile.extract in Python 2.7.4.",
            "cve": "PVE-2021-26133",
            "id": "pyup.io-26133",
            "more_info_path": "/vulnerabilities/PVE-2021-26133/26133",
            "specs": [
                "<3.0"
            ],
            "v": "<3.0"
        },
        {
            "advisory": "Setuptools 65.5.1 includes a fix for CVE-2022-40897: Python Packaging Authority (PyPA) setuptools before 65.5.1 allows remote attackers to cause a denial of service via HTML in a crafted package or custom PackageIndex page. There is a Regular Expression Denial of Service (ReDoS) in package_index.py.",
            "cve": "CVE-2022-40897",
            "id": "pyup.io-52495",
            "more_info_path": "/vulnerabilities/CVE-2022-40897/52495",
            "specs": [
                "<65.5.1"
            ],
            "v": "<65.5.1"
        },
        {
            "advisory": "Affected versions of Setuptools allow for remote code execution via its download functions. These functions, which are used to download packages from URLs provided by users or retrieved from package index servers, are susceptible to code injection. If these functions are exposed to user-controlled inputs, such as package URLs, they can execute arbitrary commands on the system.",
            "cve": "CVE-2024-6345",
            "id": "pyup.io-72236",
            "more_info_path": "/vulnerabilities/CVE-2024-6345/72236",
            "specs": [
                "<70.0.0"
            ],
            "v": "<70.0.0"
        },
        {
            "advisory": "Affected versions of Setuptools are vulnerable to Path Traversal via PackageIndex.download(). The impact is Arbitrary File Overwrite: An attacker would be allowed to write files to arbitrary locations on the filesystem with the permissions of the process running the Python code, which could escalate to RCE depending on the context.",
            "cve": "CVE-2025-47273",
            "id": "pyup.io-76752",
            "more_info_path": "/vulnerabilities/CVE-2025-47273/76752",
            "specs": [
                "<78.1.1"
            ],
            "v": "<78.1.1"
        },
        {
            "advisory": "Versions of setuptools are susceptible to a Denial of Service (DoS) attack due to an algorithmic complexity vulnerability in the ssl.match_hostname function. This flaw enables remote attackers to induce a DoS condition, characterized by excessive CPU consumption, through the use of multiple wildcard characters in the common name of a certificate.",
            "cve": "PVE-2024-99866",
            "id": "pyup.io-65554",
            "more_info_path": "/vulnerabilities/PVE-2024-99866/65554",
            "specs": [
                ">=0,<0.9.5"
            ],
            "v": ">=0,<0.9.5"
        }
    ],
    "sevabot": [
        {
            "advisory": "sevabot before 1.1 allows arbitrary commands to be executed.",
            "cve": "PVE-2021-26134",
            "id": "pyup.io-26134",
            "more_info_path": "/vulnerabilities/PVE-2021-26134/26134",
            "specs": [
                "<1.1"
            ],
            "v": "<1.1"
        }
    ],
    "sfmergeutility": [
        {
            "advisory": "Sfmergeutility version 0.1.6 includes a security patch for the function 'load_and_merge_partial_documents' in 'sfmergeutility/sf_merge_utility.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/Azure/azure-cli-extensions/commit/4c14ac3599c7eddb8a9d9647cd5b6979847f4493#diff-ab3f8debc85e8d89ef9c6ab747f3c92153d4f8d7f0f7eb80580b7c0066df1e99",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-41393",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/41393",
            "specs": [
                "<0.1.6"
            ],
            "v": "<0.1.6"
        }
    ],
    "sftp-cloudfs": [
        {
            "advisory": "sftp-cloudfs before 0.13.1 is using an insecure transitive dependency (ftp-cloudfs<=0.26.1).\r\nhttps://github.com/Memset/sftpcloudfs/commit/a1d8855c576fc3830880e2f200acd205be772da6\r\nhttps://github.com/Memset/sftpcloudfs/issues/13#issuecomment-40093908",
            "cve": "PVE-2023-54977",
            "id": "pyup.io-26135",
            "more_info_path": "/vulnerabilities/PVE-2023-54977/26135",
            "specs": [
                "<0.13.1"
            ],
            "v": "<0.13.1"
        }
    ],
    "sglang": [
        {
            "advisory": "Affected versions of the sglang package are vulnerable to Deserialization of Untrusted Data due to unsafe deserialization of the user-controlled serialized_named_tensors argument in the update_weights_from_tensor main routine. The /update_weights_from_tensor main function accepts a serialized_named_tensors payload and deserialises it without validation or sandboxing, allowing attacker-supplied objects to be instantiated during the weight-update path.",
            "cve": "CVE-2025-10164",
            "id": "pyup.io-81122",
            "more_info_path": "/vulnerabilities/CVE-2025-10164/81122",
            "specs": [
                "<0.5.4"
            ],
            "v": "<0.5.4"
        },
        {
            "advisory": "Affected versions of the sgl-model-gateway package are vulnerable to denial of service due to missing execution timeouts for WebAssembly (WASM) module execution.",
            "cve": "PVE-2026-85006",
            "id": "pyup.io-85006",
            "more_info_path": "/vulnerabilities/PVE-2026-85006/85006",
            "specs": [
                "<0.5.7"
            ],
            "v": "<0.5.7"
        }
    ],
    "sgraph": [
        {
            "advisory": "Sgraph 0.0.7 updates its dependency 'lxml' to versions '~=4.9.1' to include a security fix.",
            "cve": "CVE-2022-2309",
            "id": "pyup.io-51362",
            "more_info_path": "/vulnerabilities/CVE-2022-2309/51362",
            "specs": [
                "<0.0.7"
            ],
            "v": "<0.0.7"
        }
    ],
    "sgx-dcap-quote-verify-python": [
        {
            "advisory": "Sgx-dcap-quote-verify-python 0.0.3 includes a statically linked copy of OpenSSL. The version of OpenSSL included in sgx-dcap-quote-verify-python 0.0.1..0.0.2 is vulnerable to a security issue. More details about the OpenSSL vulnerabilities themselves can be found at https://www.openssl.org/news/secadv/20230207.txt\r\nhttps://github.com/advisories/GHSA-344m-qcjq-xgrf",
            "cve": "CVE-2023-0286",
            "id": "pyup.io-55101",
            "more_info_path": "/vulnerabilities/CVE-2023-0286/55101",
            "specs": [
                "<0.0.3"
            ],
            "v": "<0.0.3"
        }
    ],
    "shaarli-client": [
        {
            "advisory": "Shaarli-client 0.5.0 updates its dependency 'pyjwt' to v2.4.0 to include a security fix.",
            "cve": "CVE-2022-29217",
            "id": "pyup.io-50278",
            "more_info_path": "/vulnerabilities/CVE-2022-29217/50278",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        }
    ],
    "shaasigma": [
        {
            "advisory": "Shaasigma is a malicious package. It triggers the install of W4SP Stealer in your system.",
            "cve": "PVE-2022-51686",
            "id": "pyup.io-51686",
            "more_info_path": "/vulnerabilities/PVE-2022-51686/51686",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "shaka-streamer": [
        {
            "advisory": "Shaka-streamer 0.3.0 fixes the PyYAML deprecation warning and YAML loading vulnerability - see: https://github.com/google/shaka-streamer/issues/35",
            "cve": "PVE-2021-37578",
            "id": "pyup.io-37578",
            "more_info_path": "/vulnerabilities/PVE-2021-37578/37578",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "shiftboiler": [
        {
            "advisory": "shiftboiler before 0.6.5 included a minor security issue: If google login did not return an id, user can takeover another user's account.",
            "cve": "PVE-2021-36542",
            "id": "pyup.io-36542",
            "more_info_path": "/vulnerabilities/PVE-2021-36542/36542",
            "specs": [
                "<0.6.5"
            ],
            "v": "<0.6.5"
        },
        {
            "advisory": "Shiftboiler 0.9.3 contains improvements around application security. For instance session cookies and FlaskLogin's remember me cookies are now set to be secure and http-only by default in production environments. Additionally, flask applications are now CSRF-protected out of the box so you don't have to remember to enable this feature.",
            "cve": "PVE-2021-38472",
            "id": "pyup.io-38472",
            "more_info_path": "/vulnerabilities/PVE-2021-38472/38472",
            "specs": [
                "<0.9.3"
            ],
            "v": "<0.9.3"
        },
        {
            "advisory": "Affected versions of shiftboiler, a Flask framework setup, are susceptible to a user impersonation attack. This vulnerability could allow a malicious user to take over another user's account if the Google login process fails to return an ID.",
            "cve": "PVE-2024-99865",
            "id": "pyup.io-65555",
            "more_info_path": "/vulnerabilities/PVE-2024-99865/65555",
            "specs": [
                ">=0,<0.6.5"
            ],
            "v": ">=0,<0.6.5"
        }
    ],
    "shinken": [
        {
            "advisory": "Shinken Solutions Shinken Monitoring Version 2.4.3 and before are vulnerable to Incorrect Access Control. The SafeUnpickler class found in shinken/safepickle.py implements a weak authentication scheme when unserializing objects passed from monitoring nodes to the Shinken monitoring server.",
            "cve": "CVE-2022-37298",
            "id": "pyup.io-54574",
            "more_info_path": "/vulnerabilities/CVE-2022-37298/54574",
            "specs": [
                ">=0,<=2.4.3"
            ],
            "v": ">=0,<=2.4.3"
        }
    ],
    "shinylive": [
        {
            "advisory": "Shinylive 0.0.8 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.",
            "cve": "CVE-2007-4559",
            "id": "pyup.io-59228",
            "more_info_path": "/vulnerabilities/CVE-2007-4559/59228",
            "specs": [
                "<0.0.8"
            ],
            "v": "<0.0.8"
        }
    ],
    "shiva": [
        {
            "advisory": "Shiva throughout 0.10.0 allows absolute path traversal because the Flask send_file function is used unsafely. See CVE-2022-31558.",
            "cve": "CVE-2022-31558",
            "id": "pyup.io-50070",
            "more_info_path": "/vulnerabilities/CVE-2022-31558/50070",
            "specs": [
                "<=0.10.0"
            ],
            "v": "<=0.10.0"
        }
    ],
    "shopyo": [
        {
            "advisory": "Affected versions of Shopyo are vulnerable to a Improper Authorization flaw.",
            "cve": "PVE-2024-67520",
            "id": "pyup.io-67520",
            "more_info_path": "/vulnerabilities/PVE-2024-67520/67520",
            "specs": [
                "<4.9.1"
            ],
            "v": "<4.9.1"
        }
    ],
    "shot2story": [
        {
            "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'shot2story' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.",
            "cve": "PVE-2024-74240",
            "id": "pyup.io-74240",
            "more_info_path": "/vulnerabilities/PVE-2024-74240/74240",
            "specs": [
                ">=0",
                "<=0"
            ],
            "v": ">=0,<=0"
        }
    ],
    "shub": [
        {
            "advisory": "Shub 2.10.0 upgrades its requests dependency from version 2.10.0 to 2.22.0, addressing the security vulnerability CVE-2018-18074.\r\nhttps://github.com/scrapinghub/shub/pull/353/commits/0ba5d4aeefe11044f5d218ddcf85511fcde29633",
            "cve": "CVE-2017-18342",
            "id": "pyup.io-64311",
            "more_info_path": "/vulnerabilities/CVE-2017-18342/64311",
            "specs": [
                "<2.10.0"
            ],
            "v": "<2.10.0"
        },
        {
            "advisory": "Shub 2.10.0 upgrades its pyyaml dependency from version 3.12 to 5.1.1, addressing the security vulnerability CVE-2018-18074.\r\nhttps://github.com/scrapinghub/shub/pull/353/commits/0ba5d4aeefe11044f5d218ddcf85511fcde29633",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-64247",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/64247",
            "specs": [
                "<2.10.0"
            ],
            "v": "<2.10.0"
        }
    ],
    "shuup": [
        {
            "advisory": "Shuup 1.1.0 uses the more secure get_random_string to generate order keys.\r\nhttps://github.com/shuup/shuup/commit/e3861a0b710212ed0d5a9497452ed223bbe83162",
            "cve": "PVE-2017-47062",
            "id": "pyup.io-47062",
            "more_info_path": "/vulnerabilities/PVE-2017-47062/47062",
            "specs": [
                "<1.1.0"
            ],
            "v": "<1.1.0"
        },
        {
            "advisory": "\u201cShuup\u201d application in versions 0.4.2 to 2.10.8 is affected by the \u201cFormula Injection\u201d vulnerability. A customer can inject payloads in the name input field in the billing address while buying a product. When a store administrator accesses the reports page to export the data as an Excel file and opens it, the payload gets executed.",
            "cve": "CVE-2021-25962",
            "id": "pyup.io-42307",
            "more_info_path": "/vulnerabilities/CVE-2021-25962/42307",
            "specs": [
                ">=0.4.2,<2.11.0"
            ],
            "v": ">=0.4.2,<2.11.0"
        },
        {
            "advisory": "Shuup 2.11.0 includes a fix for CVE-2021-25963: Shuup versions 1.6.0 through 2.10.8 are vulnerable to reflected Cross-Site Scripting (XSS) that allows execution of arbitrary javascript code on a victim browser. This vulnerability exists due to the error page contents not escaped.\r\nhttps://github.com/shuup/shuup/commit/75714c37e32796eb7cbb0d977af5bcaa26573588\r\nhttps://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25963",
            "cve": "CVE-2021-25963",
            "id": "pyup.io-41033",
            "more_info_path": "/vulnerabilities/CVE-2021-25963/41033",
            "specs": [
                ">=1.6.0,<2.11.0"
            ],
            "v": ">=1.6.0,<2.11.0"
        }
    ],
    "sickchill": [
        {
            "advisory": "SickChill is an automatic video library manager for TV shows. A user-controlled login endpoint's next_ parameter takes arbitrary content. Prior to commit c7128a8946c3701df95c285810eb75b2de18bf82, an authenticated attacker may use this to redirect the user to arbitrary destinations, leading to open redirect. Commit c7128a8946c3701df95c285810eb75b2de18bf82 changes the login page to redirect to settings.DEFAULT_PAGE instead of to the next parameter.",
            "cve": "CVE-2024-53995",
            "id": "pyup.io-76365",
            "more_info_path": "/vulnerabilities/CVE-2024-53995/76365",
            "specs": [
                "<2024.3.1"
            ],
            "v": "<2024.3.1"
        }
    ],
    "sickrage": [
        {
            "advisory": "SiCKRAGE versions before 6.0.22 are susceptible to Full Path Disclosure (FPD) due to a returned WEB_ROOT present in get_update_url().",
            "cve": "PVE-2023-99948",
            "id": "pyup.io-60916",
            "more_info_path": "/vulnerabilities/PVE-2023-99948/60916",
            "specs": [
                "<6.0.22"
            ],
            "v": "<6.0.22"
        },
        {
            "advisory": "SickRage before v2018.03.09-1 includes cleartext credentials in HTTP responses.",
            "cve": "CVE-2018-9160",
            "id": "pyup.io-65857",
            "more_info_path": "/vulnerabilities/CVE-2018-9160/65857",
            "specs": [
                "<=9.2.101"
            ],
            "v": "<=9.2.101"
        },
        {
            "advisory": "in SiCKRAGE, versions 4.2.0 to 10.0.11.dev1 are vulnerable to Stored Cross-Site-Scripting (XSS) due to user input not being validated properly when processed by the server. Therefore, an attacker can inject arbitrary JavaScript code inside the application, and possibly steal a user\u2019s sensitive information.",
            "cve": "CVE-2021-25925",
            "id": "pyup.io-54258",
            "more_info_path": "/vulnerabilities/CVE-2021-25925/54258",
            "specs": [
                ">=4.2.0,<10.0.11"
            ],
            "v": ">=4.2.0,<10.0.11"
        },
        {
            "advisory": "In SiCKRAGE, versions 9.3.54.dev1 to 10.0.11.dev1 are vulnerable to Reflected Cross-Site-Scripting (XSS) due to user input not being validated properly in the `quicksearch` feature. Therefore, an attacker can steal a user's sessionID to masquerade as a victim user, to carry out any actions in the context of the user.\r\nhttps://github.com/SiCKRAGE/SiCKRAGE/commit/9f42426727e16609ad3d1337f6637588b8ed28e4",
            "cve": "CVE-2021-25926",
            "id": "pyup.io-54304",
            "more_info_path": "/vulnerabilities/CVE-2021-25926/54304",
            "specs": [
                ">=9.3.54,<10.0.11"
            ],
            "v": ">=9.3.54,<10.0.11"
        }
    ],
    "sigmaiq": [
        {
            "advisory": "Sigmaiq 0.2.1 updates its dependency 'certifi' to version '2023.07.22' to include a fix for a vulnerability.\r\nhttps://github.com/AttackIQ/SigmAIQ/commit/9e9c4376c220af03448e0d3d98c81048d3740cc4",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-60512",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/60512",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "signac-dashboard": [
        {
            "advisory": "Signac-dashboard 0.4.0 requires login to view job and project data.\r\nhttps://github.com/glotzerlab/signac-dashboard/pull/158",
            "cve": "PVE-2022-52399",
            "id": "pyup.io-52399",
            "more_info_path": "/vulnerabilities/PVE-2022-52399/52399",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Signac-dashboard 0.6.0 updates its bundled 'jQuery' version to 3.6.4 to include a security fix.\r\nhttps://github.com/glotzerlab/signac-dashboard/pull/184",
            "cve": "CVE-2020-11023",
            "id": "pyup.io-61424",
            "more_info_path": "/vulnerabilities/CVE-2020-11023/61424",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        },
        {
            "advisory": "Signac-dashboard 0.6.0 updates its bundled 'jQuery' version to 3.6.4 to include a security fix.\r\nhttps://github.com/glotzerlab/signac-dashboard/pull/184",
            "cve": "CVE-2020-11022",
            "id": "pyup.io-60864",
            "more_info_path": "/vulnerabilities/CVE-2020-11022/60864",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "signxml": [
        {
            "advisory": "SignXML is an implementation of the W3C XML Signature standard in Python. When verifying signatures with X509 certificate validation turned off and HMAC shared secret set (`signxml.XMLVerifier.verify(require_x509=False, hmac_key=...`), versions of SignXML prior to 4.0.4 are vulnerable to a potential algorithm confusion attack. Unless the user explicitly limits the expected signature algorithms using the `signxml.XMLVerifier.verify(expect_config=...)` setting, an attacker may supply a signature unexpectedly signed with a key other than the provided HMAC key, using a different (asymmetric key) signature algorithm. Starting with SignXML 4.0.4, specifying `hmac_key` causes the set of accepted signature algorithms to be restricted to HMAC only, if not already restricted by the user.",
            "cve": "CVE-2025-48994",
            "id": "pyup.io-77687",
            "more_info_path": "/vulnerabilities/CVE-2025-48994/77687",
            "specs": [
                "<4.0.4"
            ],
            "v": "<4.0.4"
        },
        {
            "advisory": "SignXML is an implementation of the W3C XML Signature standard in Python. When verifying signatures with X509 certificate validation turned off and HMAC shared secret set (`signxml.XMLVerifier.verify(require_x509=False, hmac_key=...`), versions of SignXML prior to 4.0.4 are vulnerable to a potential timing attack. The verifier may leak information about the correct HMAC when comparing it with the user supplied hash, allowing users to reconstruct the correct HMAC for any data.",
            "cve": "CVE-2025-48995",
            "id": "pyup.io-77688",
            "more_info_path": "/vulnerabilities/CVE-2025-48995/77688",
            "specs": [
                "<4.0.4"
            ],
            "v": "<4.0.4"
        }
    ],
    "sigstore": [
        {
            "advisory": "Affected versions of the sigstore package are vulnerable to Cross-Site Request Forgery (CSRF) due to missing validation of the OAuth \u201cstate\u201d parameter returned in the authentication response. The sigstore _OAuthSession flow generates a unique state value and includes it in the OIDC/OAuth authentication request, but does not appear to cross-check that the state in the server response matches the original value.",
            "cve": "CVE-2026-24408",
            "id": "pyup.io-85154",
            "more_info_path": "/vulnerabilities/CVE-2026-24408/85154",
            "specs": [
                "<4.2.0"
            ],
            "v": "<4.2.0"
        },
        {
            "advisory": "Versions of sigstore-python newer than 2.0.0 but before 3.6.0 perform insufficient validation of the \"integration time\" present in \"v2\" and \"v3\" bundles during the verification flow: the \"integration time\" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect \"v1\" bundles, as the \"v1\" bundle format always requires an inclusion promise.",
            "cve": "CVE-2024-55655",
            "id": "pyup.io-76385",
            "more_info_path": "/vulnerabilities/CVE-2024-55655/76385",
            "specs": [
                ">=2.0.0,<3.6.0"
            ],
            "v": ">=2.0.0,<3.6.0"
        }
    ],
    "siliconcompiler": [
        {
            "advisory": "Siliconcompiler 0.21.6",
            "cve": "PVE-2024-66988",
            "id": "pyup.io-66988",
            "more_info_path": "/vulnerabilities/PVE-2024-66988/66988",
            "specs": [
                "<0.21.6"
            ],
            "v": "<0.21.6"
        }
    ],
    "simiki": [
        {
            "advisory": "Cross Site Scripting (XSS) in Simiki v1.6.2.1 and prior allows remote attackers to execute arbitrary code via line 54 of the component 'simiki/blob/master/simiki/generators.py'.",
            "cve": "CVE-2020-19000",
            "id": "pyup.io-54310",
            "more_info_path": "/vulnerabilities/CVE-2020-19000/54310",
            "specs": [
                ">=0,<1.6.2.2"
            ],
            "v": ">=0,<1.6.2.2"
        },
        {
            "advisory": "Command Injection in Simiki v1.6.2.1 and prior allows remote attackers to execute arbitrary system commands via line 64 of the component 'simiki/blob/master/simiki/config.py'.\n\nAffected functions:\nsimiki.config.parse_config",
            "cve": "CVE-2020-19001",
            "id": "pyup.io-54313",
            "more_info_path": "/vulnerabilities/CVE-2020-19001/54313",
            "specs": [
                ">=0,<1.6.2.2"
            ],
            "v": ">=0,<1.6.2.2"
        }
    ],
    "simpl-cloud": [
        {
            "advisory": "Simpl-cloud 1.2.1 updates its NPM dependency 'node-fetch' to v2.6.7 to include security fixes.",
            "cve": "CVE-2022-0235",
            "id": "pyup.io-49676",
            "more_info_path": "/vulnerabilities/CVE-2022-0235/49676",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        },
        {
            "advisory": "Simpl-cloud 1.2.1 updates its NPM dependency 'node-fetch' to v2.6.7 to include security fixes.",
            "cve": "CVE-2022-1365",
            "id": "pyup.io-49717",
            "more_info_path": "/vulnerabilities/CVE-2022-1365/49717",
            "specs": [
                "<1.2.1"
            ],
            "v": "<1.2.1"
        }
    ],
    "simple-api-client": [
        {
            "advisory": "Simple-api-client 1.0.6 updates its dependency 'Bleach' to v3.3.0 to include a security fix.",
            "cve": "CVE-2021-23980",
            "id": "pyup.io-47938",
            "more_info_path": "/vulnerabilities/CVE-2021-23980/47938",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        },
        {
            "advisory": "Simple-api-client 1.0.7 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-47937",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/47937",
            "specs": [
                "<1.0.7"
            ],
            "v": "<1.0.7"
        }
    ],
    "simple-otp": [
        {
            "advisory": "Simple-otp 0.1.1 uses hmac.compare_digest to avoid timing attacks.\r\nhttps://github.com/nogoodusername/simple-otp/pull/3",
            "cve": "PVE-2022-51326",
            "id": "pyup.io-51326",
            "more_info_path": "/vulnerabilities/PVE-2022-51326/51326",
            "specs": [
                "<0.1.1"
            ],
            "v": "<0.1.1"
        },
        {
            "advisory": "Simple-otp 0.1.1 uses cryptographically secure random numbers.\r\nhttps://github.com/nogoodusername/simple-otp/pull/4",
            "cve": "PVE-2022-51335",
            "id": "pyup.io-51335",
            "more_info_path": "/vulnerabilities/PVE-2022-51335/51335",
            "specs": [
                "<0.1.1"
            ],
            "v": "<0.1.1"
        }
    ],
    "simple-swagger": [
        {
            "advisory": "Simple-swagger 0.1.0 adds basic security support with credentials.",
            "cve": "PVE-2021-40180",
            "id": "pyup.io-40180",
            "more_info_path": "/vulnerabilities/PVE-2021-40180/40180",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        },
        {
            "advisory": "Simple-swagger 0.3.1 adds support for global security.",
            "cve": "PVE-2021-41238",
            "id": "pyup.io-41238",
            "more_info_path": "/vulnerabilities/PVE-2021-41238/41238",
            "specs": [
                "<0.3.1"
            ],
            "v": "<0.3.1"
        }
    ],
    "simple-websocket": [
        {
            "advisory": "Simple-websocket 0.8.1 includes a fix for a potential race condition vulnerability.\r\nhttps://github.com/miguelgrinberg/simple-websocket/issues/18",
            "cve": "PVE-2023-61626",
            "id": "pyup.io-61626",
            "more_info_path": "/vulnerabilities/PVE-2023-61626/61626",
            "specs": [
                "<0.8.1"
            ],
            "v": "<0.8.1"
        }
    ],
    "simpleitk": [
        {
            "advisory": "Affected versions of the SimpleITK package are vulnerable to Out-of-Bounds Read due to a transitive flaw in the ITK DICOM parsing dependency when handling malformed DICOM files with encapsulated PixelData fragments.",
            "cve": "PVE-2025-81789",
            "id": "pyup.io-81789",
            "more_info_path": "/vulnerabilities/PVE-2025-81789/81789",
            "specs": [
                "<2.5.3"
            ],
            "v": "<2.5.3"
        }
    ],
    "simplejson": [
        {
            "advisory": "Simplejson 2.6.1 includes a fix for CVE-2014-4616: Array index error in the scanstring function in the _json module in Python 2.7 through 3.5 and simplejson before 2.6.1 allows context-dependent attackers to read arbitrary process memory via a negative index value in the idx argument to the raw_decode function.\r\nhttps://bugs.python.org/issue21529",
            "cve": "CVE-2014-4616",
            "id": "pyup.io-61644",
            "more_info_path": "/vulnerabilities/CVE-2014-4616/61644",
            "specs": [
                "<2.6.1"
            ],
            "v": "<2.6.1"
        }
    ],
    "simplematrixbotlib": [
        {
            "advisory": "Simplematrixbotlib 2.6.2 fixes a possible code injection vulnerability.\r\nhttps://github.com/i10b/simplematrixbotlib/commit/4a6eea5a3eaa5cf0f06b7087a5b1e851e9d021a8",
            "cve": "PVE-2022-45407",
            "id": "pyup.io-45407",
            "more_info_path": "/vulnerabilities/PVE-2022-45407/45407",
            "specs": [
                "<2.6.2"
            ],
            "v": "<2.6.2"
        }
    ],
    "simplemonitor": [
        {
            "advisory": "simplemonitor 2.7 changes the remote monitor protocol and uses the JSON format for remote monitor protocol (more secure than pickle)",
            "cve": "PVE-2021-37886",
            "id": "pyup.io-37886",
            "more_info_path": "/vulnerabilities/PVE-2021-37886/37886",
            "specs": [
                "<2.7"
            ],
            "v": "<2.7"
        }
    ],
    "simplesockets": [
        {
            "advisory": "Simplesockets 0.1.0 improves security in the self-made secure socket.",
            "cve": "PVE-2021-40604",
            "id": "pyup.io-40604",
            "more_info_path": "/vulnerabilities/PVE-2021-40604/40604",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        }
    ],
    "simulaqron": [
        {
            "advisory": "Simulaqron 3.0.7 updates its dependency 'twisted' minimum requirement to v19.7 to include security fixes.",
            "cve": "CVE-2019-12387",
            "id": "pyup.io-49050",
            "more_info_path": "/vulnerabilities/CVE-2019-12387/49050",
            "specs": [
                "<3.0.7"
            ],
            "v": "<3.0.7"
        },
        {
            "advisory": "Simulaqron 3.0.7 updates its dependency 'twisted' minimum requirement to v19.7 to include security fixes.",
            "cve": "CVE-2019-12855",
            "id": "pyup.io-37571",
            "more_info_path": "/vulnerabilities/CVE-2019-12855/37571",
            "specs": [
                "<3.0.7"
            ],
            "v": "<3.0.7"
        }
    ],
    "siwe": [
        {
            "advisory": "Siwe 2.0.3-beta uses 'verify(params, opts)' instead of  'validate(...)'. This includes the param 'nonce'  that prevents replay attacks.\r\nhttps://github.com/djungle-io/django-djet2/commit/734f3521d8290f6162847ad0b5c33d8ab5e119a9",
            "cve": "PVE-2022-51365",
            "id": "pyup.io-51365",
            "more_info_path": "/vulnerabilities/PVE-2022-51365/51365",
            "specs": [
                "<2.0.3-beta"
            ],
            "v": "<2.0.3-beta"
        },
        {
            "advisory": "Siwe 2.1.4 updates its NPM dependency 'ethers' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/spruceid/siwe/pull/147",
            "cve": "PVE-2023-60587",
            "id": "pyup.io-60587",
            "more_info_path": "/vulnerabilities/PVE-2023-60587/60587",
            "specs": [
                "<2.1.4"
            ],
            "v": "<2.1.4"
        }
    ],
    "sixfab-tool": [
        {
            "advisory": "The Sixfab-Tool in PyPI v0.0.2 to v0.0.3 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.",
            "cve": "CVE-2022-34059",
            "id": "pyup.io-62702",
            "more_info_path": "/vulnerabilities/CVE-2022-34059/62702",
            "specs": [
                ">=0.0.2,<=0.0.3"
            ],
            "v": ">=0.0.2,<=0.0.3"
        }
    ],
    "skale-allocator-cli": [
        {
            "advisory": "Skale-allocator-cli is a malicious package, typosquatting.\r\nhttps://blog.sonatype.com/trojanized-pypi-package-imitates-a-popular-python-server-library",
            "cve": "PVE-2022-47819",
            "id": "pyup.io-47819",
            "more_info_path": "/vulnerabilities/PVE-2022-47819/47819",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "skill-sdk": [
        {
            "advisory": "Skill-sdk 0.10.5 makes its underlying dependency 'Tornado' optional due to a security issue.",
            "cve": "PVE-2021-39692",
            "id": "pyup.io-39692",
            "more_info_path": "/vulnerabilities/PVE-2021-39692/39692",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Skill-sdk version 1.0.6 updates its dependency \"FastAPI\" to v0.65.2 to include a security fix.",
            "cve": "CVE-2021-32677",
            "id": "pyup.io-40667",
            "more_info_path": "/vulnerabilities/CVE-2021-32677/40667",
            "specs": [
                "<1.0.6"
            ],
            "v": "<1.0.6"
        }
    ],
    "skops": [
        {
            "advisory": "skops is a Python library which helps users share and ship their scikit-learn based models. Versions 0.11.0 and below contain an inconsistency in MethodNode, which can be exploited to access unexpected object fields through dot notation. This can be used to achieve arbitrary code execution at load time. While this issue may seem similar to GHSA-m7f4-hrc6-fwg3, it is actually more severe, as it relies on fewer assumptions about trusted types. This is fixed in version 12.0.0.",
            "cve": "CVE-2025-54413",
            "id": "pyup.io-78515",
            "more_info_path": "/vulnerabilities/CVE-2025-54413/78515",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        },
        {
            "advisory": "skops is a Python library which helps users share and ship their scikit-learn based models. Versions 0.11.0 and below contain a inconsistency in the OperatorFuncNode which can be exploited to hide the execution of untrusted operator methods. This can then be used in a code reuse attack to invoke seemingly safe functions and escalate to arbitrary code execution with minimal and misleading trusted types. This is fixed in version 0.12.0.",
            "cve": "CVE-2025-54412",
            "id": "pyup.io-78516",
            "more_info_path": "/vulnerabilities/CVE-2025-54412/78516",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        },
        {
            "advisory": "Affected versions of the skops package are vulnerable to Deserialization of Untrusted Data due to Card.get_model silently falling back to joblib.load for non-zip inputs, bypassing skops\u2019 safe-loading controls. In Card.get_model, a zipfile.is_zipfile check routes \u201c.skops\u201d archives to skops.load with trusted-type validation, but when the file is not a zip archive the method invokes joblib.load on attacker-controlled pickle data, enabling arbitrary code execution.",
            "cve": "CVE-2025-54886",
            "id": "pyup.io-81159",
            "more_info_path": "/vulnerabilities/CVE-2025-54886/81159",
            "specs": [
                "<0.13.0"
            ],
            "v": "<0.13.0"
        },
        {
            "advisory": "Skops 0.6 includes a fix for the persisting :class:'numpy.random.Generator': using the skops format the object could be loaded correctly but security could not be checked.\r\nhttps://github.com/skops-dev/skops/commit/deaf6e275e4f9f0ad8e84cf5b4def5e7a7b118f6",
            "cve": "PVE-2023-54838",
            "id": "pyup.io-54838",
            "more_info_path": "/vulnerabilities/PVE-2023-54838/54838",
            "specs": [
                "<0.6"
            ],
            "v": "<0.6"
        },
        {
            "advisory": "Deserialization of untrusted data can occur in versions 0.6 or newer of the skops python library, enabling a maliciously crafted model to run arbitrary code on an end user's system when loaded. See CVE-2024-37065.",
            "cve": "CVE-2024-37065",
            "id": "pyup.io-71782",
            "more_info_path": "/vulnerabilities/CVE-2024-37065/71782",
            "specs": [
                ">=0.6"
            ],
            "v": ">=0.6"
        }
    ],
    "skypilot": [
        {
            "advisory": "Affected versions of this package are vulnerable to Information Disclosure via Insufficient Job Isolation. The job management system fails to enforce proper access controls and environment isolation between users' jobs. This leads to unauthorized users being able to view other users' pending job information and access leaked environment variables containing sensitive credentials, API keys, and configuration data from other users' managed jobs.",
            "cve": "PVE-2025-82254",
            "id": "pyup.io-82254",
            "more_info_path": "/vulnerabilities/PVE-2025-82254/82254",
            "specs": [
                "<0.10.5"
            ],
            "v": "<0.10.5"
        },
        {
            "advisory": "Affected versions of SkyPilot\u2019s SkyServe are potentially vulnerable to unencrypted data transmission. This flaw exposes sensitive API requests to interception and man-in-the-middle attacks by transmitting traffic over plain HTTP. The vulnerability affects load balancer and service endpoint configurations.",
            "cve": "PVE-2025-75442",
            "id": "pyup.io-75442",
            "more_info_path": "/vulnerabilities/PVE-2025-75442/75442",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        }
    ],
    "skyvern": [
        {
            "advisory": "Skyvern through 0.1.85 is vulnerable to server-side template injection (SSTI) in the Prompt field of workflow blocks such as the Navigation v2 Block. Improper sanitization of Jinja2 template input allows authenticated users to inject crafted expressions that are evaluated on the server, leading to blind remote code execution (RCE).",
            "cve": "CVE-2025-49619",
            "id": "pyup.io-77684",
            "more_info_path": "/vulnerabilities/CVE-2025-49619/77684",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        }
    ],
    "sl-pip": [
        {
            "advisory": "Sl-pip 8.2.1.2 and prior are vulnerable to CVE-2019-20916: Directory Traversal when a URL is given in an install command, because a Content-Disposition header can have dir in a filename, as demonstrated by overwriting the /root/.ssh/authorized_keys file. This occurs in _download_http_url in _internal/download.py.",
            "cve": "CVE-2019-20916",
            "id": "pyup.io-47178",
            "more_info_path": "/vulnerabilities/CVE-2019-20916/47178",
            "specs": [
                "<=8.2.1.2"
            ],
            "v": "<=8.2.1.2"
        }
    ],
    "slackeventsapi": [
        {
            "advisory": "Slackeventsapi 2.1.0 updates minimum Flask version to address security vulnerability.\r\nhttps://github.com/slackapi/python-slack-events-api/pull/45/commits/bdc6abfbb5f6ae50be16750988fc5adddd9a4a80",
            "cve": "CVE-2018-1000656",
            "id": "pyup.io-36729",
            "more_info_path": "/vulnerabilities/CVE-2018-1000656/36729",
            "specs": [
                "<2.1.0"
            ],
            "v": "<2.1.0"
        }
    ],
    "sleap": [
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15358",
            "id": "pyup.io-43805",
            "more_info_path": "/vulnerabilities/CVE-2020-15358/43805",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-13871",
            "id": "pyup.io-43810",
            "more_info_path": "/vulnerabilities/CVE-2020-13871/43810",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15190",
            "id": "pyup.io-43802",
            "more_info_path": "/vulnerabilities/CVE-2020-15190/43802",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2019-19645",
            "id": "pyup.io-43817",
            "more_info_path": "/vulnerabilities/CVE-2019-19645/43817",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2019-19880",
            "id": "pyup.io-43819",
            "more_info_path": "/vulnerabilities/CVE-2019-19880/43819",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2018-19664",
            "id": "pyup.io-43815",
            "more_info_path": "/vulnerabilities/CVE-2018-19664/43815",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-13630",
            "id": "pyup.io-43804",
            "more_info_path": "/vulnerabilities/CVE-2020-13630/43804",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15209",
            "id": "pyup.io-43799",
            "more_info_path": "/vulnerabilities/CVE-2020-15209/43799",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15207",
            "id": "pyup.io-43801",
            "more_info_path": "/vulnerabilities/CVE-2020-15207/43801",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-11656",
            "id": "pyup.io-43806",
            "more_info_path": "/vulnerabilities/CVE-2020-11656/43806",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-13434",
            "id": "pyup.io-43808",
            "more_info_path": "/vulnerabilities/CVE-2020-13434/43808",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15206",
            "id": "pyup.io-43797",
            "more_info_path": "/vulnerabilities/CVE-2020-15206/43797",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15208",
            "id": "pyup.io-43798",
            "more_info_path": "/vulnerabilities/CVE-2020-15208/43798",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-13435",
            "id": "pyup.io-43809",
            "more_info_path": "/vulnerabilities/CVE-2020-13435/43809",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-11655",
            "id": "pyup.io-43807",
            "more_info_path": "/vulnerabilities/CVE-2020-11655/43807",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-13631",
            "id": "pyup.io-43811",
            "more_info_path": "/vulnerabilities/CVE-2020-13631/43811",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2019-13960",
            "id": "pyup.io-43823",
            "more_info_path": "/vulnerabilities/CVE-2019-13960/43823",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15195",
            "id": "pyup.io-43800",
            "more_info_path": "/vulnerabilities/CVE-2020-15195/43800",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-9327",
            "id": "pyup.io-43812",
            "more_info_path": "/vulnerabilities/CVE-2020-9327/43812",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15203",
            "id": "pyup.io-43803",
            "more_info_path": "/vulnerabilities/CVE-2020-15203/43803",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15205",
            "id": "pyup.io-43795",
            "more_info_path": "/vulnerabilities/CVE-2020-15205/43795",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15204",
            "id": "pyup.io-43794",
            "more_info_path": "/vulnerabilities/CVE-2020-15204/43794",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2019-10099",
            "id": "pyup.io-43821",
            "more_info_path": "/vulnerabilities/CVE-2019-10099/43821",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15202",
            "id": "pyup.io-43796",
            "more_info_path": "/vulnerabilities/CVE-2020-15202/43796",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15210",
            "id": "pyup.io-43813",
            "more_info_path": "/vulnerabilities/CVE-2020-15210/43813",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2018-17190",
            "id": "pyup.io-43816",
            "more_info_path": "/vulnerabilities/CVE-2018-17190/43816",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2018-20330",
            "id": "pyup.io-43820",
            "more_info_path": "/vulnerabilities/CVE-2018-20330/43820",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2018-11770",
            "id": "pyup.io-43822",
            "more_info_path": "/vulnerabilities/CVE-2018-11770/43822",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2020-15211",
            "id": "pyup.io-39680",
            "more_info_path": "/vulnerabilities/CVE-2020-15211/39680",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.0.10 updates TensorFlow to v2.1.2 for security reasons.",
            "cve": "CVE-2019-19244",
            "id": "pyup.io-43818",
            "more_info_path": "/vulnerabilities/CVE-2019-19244/43818",
            "specs": [
                "<1.0.10"
            ],
            "v": "<1.0.10"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41224",
            "id": "pyup.io-46233",
            "more_info_path": "/vulnerabilities/CVE-2021-41224/46233",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-26270",
            "id": "pyup.io-46083",
            "more_info_path": "/vulnerabilities/CVE-2020-26270/46083",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-8285",
            "id": "pyup.io-46089",
            "more_info_path": "/vulnerabilities/CVE-2020-8285/46089",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29516",
            "id": "pyup.io-46100",
            "more_info_path": "/vulnerabilities/CVE-2021-29516/46100",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41223",
            "id": "pyup.io-46232",
            "more_info_path": "/vulnerabilities/CVE-2021-41223/46232",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29575",
            "id": "pyup.io-46159",
            "more_info_path": "/vulnerabilities/CVE-2021-29575/46159",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29582",
            "id": "pyup.io-46166",
            "more_info_path": "/vulnerabilities/CVE-2021-29582/46166",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29573",
            "id": "pyup.io-46157",
            "more_info_path": "/vulnerabilities/CVE-2021-29573/46157",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-8169",
            "id": "pyup.io-46085",
            "more_info_path": "/vulnerabilities/CVE-2020-8169/46085",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-13790",
            "id": "pyup.io-46075",
            "more_info_path": "/vulnerabilities/CVE-2020-13790/46075",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41196",
            "id": "pyup.io-46206",
            "more_info_path": "/vulnerabilities/CVE-2021-41196/46206",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41197",
            "id": "pyup.io-46207",
            "more_info_path": "/vulnerabilities/CVE-2021-41197/46207",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29572",
            "id": "pyup.io-46156",
            "more_info_path": "/vulnerabilities/CVE-2021-29572/46156",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41204",
            "id": "pyup.io-46214",
            "more_info_path": "/vulnerabilities/CVE-2021-41204/46214",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29561",
            "id": "pyup.io-46145",
            "more_info_path": "/vulnerabilities/CVE-2021-29561/46145",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29543",
            "id": "pyup.io-46127",
            "more_info_path": "/vulnerabilities/CVE-2021-29543/46127",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29534",
            "id": "pyup.io-46118",
            "more_info_path": "/vulnerabilities/CVE-2021-29534/46118",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41225",
            "id": "pyup.io-46234",
            "more_info_path": "/vulnerabilities/CVE-2021-41225/46234",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29619",
            "id": "pyup.io-46204",
            "more_info_path": "/vulnerabilities/CVE-2021-29619/46204",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29617",
            "id": "pyup.io-46202",
            "more_info_path": "/vulnerabilities/CVE-2021-29617/46202",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41226",
            "id": "pyup.io-46235",
            "more_info_path": "/vulnerabilities/CVE-2021-41226/46235",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29512",
            "id": "pyup.io-46096",
            "more_info_path": "/vulnerabilities/CVE-2021-29512/46096",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41205",
            "id": "pyup.io-46215",
            "more_info_path": "/vulnerabilities/CVE-2021-41205/46215",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41198",
            "id": "pyup.io-46208",
            "more_info_path": "/vulnerabilities/CVE-2021-41198/46208",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29602",
            "id": "pyup.io-46186",
            "more_info_path": "/vulnerabilities/CVE-2021-29602/46186",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-15266",
            "id": "pyup.io-46079",
            "more_info_path": "/vulnerabilities/CVE-2020-15266/46079",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41214",
            "id": "pyup.io-46224",
            "more_info_path": "/vulnerabilities/CVE-2021-41214/46224",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-26268",
            "id": "pyup.io-46082",
            "more_info_path": "/vulnerabilities/CVE-2020-26268/46082",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41212",
            "id": "pyup.io-46222",
            "more_info_path": "/vulnerabilities/CVE-2021-41212/46222",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41209",
            "id": "pyup.io-46219",
            "more_info_path": "/vulnerabilities/CVE-2021-41209/46219",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29565",
            "id": "pyup.io-46149",
            "more_info_path": "/vulnerabilities/CVE-2021-29565/46149",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2019-20838",
            "id": "pyup.io-46074",
            "more_info_path": "/vulnerabilities/CVE-2019-20838/46074",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29526",
            "id": "pyup.io-46110",
            "more_info_path": "/vulnerabilities/CVE-2021-29526/46110",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29613",
            "id": "pyup.io-46198",
            "more_info_path": "/vulnerabilities/CVE-2021-29613/46198",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41218",
            "id": "pyup.io-46228",
            "more_info_path": "/vulnerabilities/CVE-2021-41218/46228",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29618",
            "id": "pyup.io-46203",
            "more_info_path": "/vulnerabilities/CVE-2021-29618/46203",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29608",
            "id": "pyup.io-46192",
            "more_info_path": "/vulnerabilities/CVE-2021-29608/46192",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29593",
            "id": "pyup.io-46177",
            "more_info_path": "/vulnerabilities/CVE-2021-29593/46177",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29552",
            "id": "pyup.io-46136",
            "more_info_path": "/vulnerabilities/CVE-2021-29552/46136",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29538",
            "id": "pyup.io-46122",
            "more_info_path": "/vulnerabilities/CVE-2021-29538/46122",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29610",
            "id": "pyup.io-46194",
            "more_info_path": "/vulnerabilities/CVE-2021-29610/46194",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29579",
            "id": "pyup.io-46163",
            "more_info_path": "/vulnerabilities/CVE-2021-29579/46163",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-26266",
            "id": "pyup.io-46080",
            "more_info_path": "/vulnerabilities/CVE-2020-26266/46080",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29523",
            "id": "pyup.io-46107",
            "more_info_path": "/vulnerabilities/CVE-2021-29523/46107",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-8231",
            "id": "pyup.io-46087",
            "more_info_path": "/vulnerabilities/CVE-2020-8231/46087",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29560",
            "id": "pyup.io-46144",
            "more_info_path": "/vulnerabilities/CVE-2021-29560/46144",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29611",
            "id": "pyup.io-46196",
            "more_info_path": "/vulnerabilities/CVE-2021-29611/46196",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29615",
            "id": "pyup.io-46200",
            "more_info_path": "/vulnerabilities/CVE-2021-29615/46200",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41207",
            "id": "pyup.io-46217",
            "more_info_path": "/vulnerabilities/CVE-2021-41207/46217",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41210",
            "id": "pyup.io-46220",
            "more_info_path": "/vulnerabilities/CVE-2021-41210/46220",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29537",
            "id": "pyup.io-46121",
            "more_info_path": "/vulnerabilities/CVE-2021-29537/46121",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-8284",
            "id": "pyup.io-46088",
            "more_info_path": "/vulnerabilities/CVE-2020-8284/46088",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-8177",
            "id": "pyup.io-46086",
            "more_info_path": "/vulnerabilities/CVE-2020-8177/46086",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29587",
            "id": "pyup.io-46171",
            "more_info_path": "/vulnerabilities/CVE-2021-29587/46171",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29594",
            "id": "pyup.io-46178",
            "more_info_path": "/vulnerabilities/CVE-2021-29594/46178",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-22922",
            "id": "pyup.io-46091",
            "more_info_path": "/vulnerabilities/CVE-2021-22922/46091",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29580",
            "id": "pyup.io-46164",
            "more_info_path": "/vulnerabilities/CVE-2021-29580/46164",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41219",
            "id": "pyup.io-46229",
            "more_info_path": "/vulnerabilities/CVE-2021-41219/46229",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29525",
            "id": "pyup.io-46109",
            "more_info_path": "/vulnerabilities/CVE-2021-29525/46109",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-22926",
            "id": "pyup.io-46095",
            "more_info_path": "/vulnerabilities/CVE-2021-22926/46095",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29588",
            "id": "pyup.io-46172",
            "more_info_path": "/vulnerabilities/CVE-2021-29588/46172",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41213",
            "id": "pyup.io-46223",
            "more_info_path": "/vulnerabilities/CVE-2021-41213/46223",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41221",
            "id": "pyup.io-46230",
            "more_info_path": "/vulnerabilities/CVE-2021-41221/46230",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29528",
            "id": "pyup.io-46112",
            "more_info_path": "/vulnerabilities/CVE-2021-29528/46112",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29574",
            "id": "pyup.io-46158",
            "more_info_path": "/vulnerabilities/CVE-2021-29574/46158",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-8286",
            "id": "pyup.io-46090",
            "more_info_path": "/vulnerabilities/CVE-2020-8286/46090",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29616",
            "id": "pyup.io-46201",
            "more_info_path": "/vulnerabilities/CVE-2021-29616/46201",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29563",
            "id": "pyup.io-46147",
            "more_info_path": "/vulnerabilities/CVE-2021-29563/46147",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29568",
            "id": "pyup.io-46152",
            "more_info_path": "/vulnerabilities/CVE-2021-29568/46152",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29585",
            "id": "pyup.io-46169",
            "more_info_path": "/vulnerabilities/CVE-2021-29585/46169",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29600",
            "id": "pyup.io-46184",
            "more_info_path": "/vulnerabilities/CVE-2021-29600/46184",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29555",
            "id": "pyup.io-46139",
            "more_info_path": "/vulnerabilities/CVE-2021-29555/46139",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29546",
            "id": "pyup.io-46130",
            "more_info_path": "/vulnerabilities/CVE-2021-29546/46130",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29603",
            "id": "pyup.io-46187",
            "more_info_path": "/vulnerabilities/CVE-2021-29603/46187",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-15265",
            "id": "pyup.io-46078",
            "more_info_path": "/vulnerabilities/CVE-2020-15265/46078",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29545",
            "id": "pyup.io-46129",
            "more_info_path": "/vulnerabilities/CVE-2021-29545/46129",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29536",
            "id": "pyup.io-46120",
            "more_info_path": "/vulnerabilities/CVE-2021-29536/46120",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29535",
            "id": "pyup.io-46119",
            "more_info_path": "/vulnerabilities/CVE-2021-29535/46119",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29591",
            "id": "pyup.io-46175",
            "more_info_path": "/vulnerabilities/CVE-2021-29591/46175",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41206",
            "id": "pyup.io-46216",
            "more_info_path": "/vulnerabilities/CVE-2021-41206/46216",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41216",
            "id": "pyup.io-46226",
            "more_info_path": "/vulnerabilities/CVE-2021-41216/46226",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29551",
            "id": "pyup.io-46135",
            "more_info_path": "/vulnerabilities/CVE-2021-29551/46135",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29606",
            "id": "pyup.io-46190",
            "more_info_path": "/vulnerabilities/CVE-2021-29606/46190",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-26271",
            "id": "pyup.io-46084",
            "more_info_path": "/vulnerabilities/CVE-2020-26271/46084",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29599",
            "id": "pyup.io-46183",
            "more_info_path": "/vulnerabilities/CVE-2021-29599/46183",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41211",
            "id": "pyup.io-46221",
            "more_info_path": "/vulnerabilities/CVE-2021-41211/46221",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29569",
            "id": "pyup.io-46153",
            "more_info_path": "/vulnerabilities/CVE-2021-29569/46153",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-14155",
            "id": "pyup.io-46076",
            "more_info_path": "/vulnerabilities/CVE-2020-14155/46076",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29614",
            "id": "pyup.io-46199",
            "more_info_path": "/vulnerabilities/CVE-2021-29614/46199",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29524",
            "id": "pyup.io-46108",
            "more_info_path": "/vulnerabilities/CVE-2021-29524/46108",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41201",
            "id": "pyup.io-46211",
            "more_info_path": "/vulnerabilities/CVE-2021-41201/46211",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41199",
            "id": "pyup.io-46209",
            "more_info_path": "/vulnerabilities/CVE-2021-41199/46209",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29519",
            "id": "pyup.io-46103",
            "more_info_path": "/vulnerabilities/CVE-2021-29519/46103",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29609",
            "id": "pyup.io-46193",
            "more_info_path": "/vulnerabilities/CVE-2021-29609/46193",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-22924",
            "id": "pyup.io-46093",
            "more_info_path": "/vulnerabilities/CVE-2021-22924/46093",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29581",
            "id": "pyup.io-46165",
            "more_info_path": "/vulnerabilities/CVE-2021-29581/46165",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-26267",
            "id": "pyup.io-46081",
            "more_info_path": "/vulnerabilities/CVE-2020-26267/46081",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29586",
            "id": "pyup.io-46170",
            "more_info_path": "/vulnerabilities/CVE-2021-29586/46170",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29548",
            "id": "pyup.io-46132",
            "more_info_path": "/vulnerabilities/CVE-2021-29548/46132",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29559",
            "id": "pyup.io-46143",
            "more_info_path": "/vulnerabilities/CVE-2021-29559/46143",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41200",
            "id": "pyup.io-46210",
            "more_info_path": "/vulnerabilities/CVE-2021-41200/46210",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29590",
            "id": "pyup.io-46174",
            "more_info_path": "/vulnerabilities/CVE-2021-29590/46174",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29596",
            "id": "pyup.io-46180",
            "more_info_path": "/vulnerabilities/CVE-2021-29596/46180",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29566",
            "id": "pyup.io-46150",
            "more_info_path": "/vulnerabilities/CVE-2021-29566/46150",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41227",
            "id": "pyup.io-46236",
            "more_info_path": "/vulnerabilities/CVE-2021-41227/46236",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29531",
            "id": "pyup.io-46115",
            "more_info_path": "/vulnerabilities/CVE-2021-29531/46115",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41228",
            "id": "pyup.io-46237",
            "more_info_path": "/vulnerabilities/CVE-2021-41228/46237",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29571",
            "id": "pyup.io-46155",
            "more_info_path": "/vulnerabilities/CVE-2021-29571/46155",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29564",
            "id": "pyup.io-46148",
            "more_info_path": "/vulnerabilities/CVE-2021-29564/46148",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29520",
            "id": "pyup.io-46104",
            "more_info_path": "/vulnerabilities/CVE-2021-29520/46104",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29583",
            "id": "pyup.io-46167",
            "more_info_path": "/vulnerabilities/CVE-2021-29583/46167",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29521",
            "id": "pyup.io-46105",
            "more_info_path": "/vulnerabilities/CVE-2021-29521/46105",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29533",
            "id": "pyup.io-46117",
            "more_info_path": "/vulnerabilities/CVE-2021-29533/46117",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29517",
            "id": "pyup.io-46101",
            "more_info_path": "/vulnerabilities/CVE-2021-29517/46101",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29530",
            "id": "pyup.io-46114",
            "more_info_path": "/vulnerabilities/CVE-2021-29530/46114",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2020-15250",
            "id": "pyup.io-46077",
            "more_info_path": "/vulnerabilities/CVE-2020-15250/46077",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41215",
            "id": "pyup.io-46225",
            "more_info_path": "/vulnerabilities/CVE-2021-41215/46225",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29540",
            "id": "pyup.io-46124",
            "more_info_path": "/vulnerabilities/CVE-2021-29540/46124",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29556",
            "id": "pyup.io-46140",
            "more_info_path": "/vulnerabilities/CVE-2021-29556/46140",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29612",
            "id": "pyup.io-46197",
            "more_info_path": "/vulnerabilities/CVE-2021-29612/46197",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29607",
            "id": "pyup.io-46191",
            "more_info_path": "/vulnerabilities/CVE-2021-29607/46191",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29547",
            "id": "pyup.io-46131",
            "more_info_path": "/vulnerabilities/CVE-2021-29547/46131",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29584",
            "id": "pyup.io-46168",
            "more_info_path": "/vulnerabilities/CVE-2021-29584/46168",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29604",
            "id": "pyup.io-46188",
            "more_info_path": "/vulnerabilities/CVE-2021-29604/46188",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29539",
            "id": "pyup.io-46123",
            "more_info_path": "/vulnerabilities/CVE-2021-29539/46123",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29513",
            "id": "pyup.io-46097",
            "more_info_path": "/vulnerabilities/CVE-2021-29513/46097",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41202",
            "id": "pyup.io-46212",
            "more_info_path": "/vulnerabilities/CVE-2021-41202/46212",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29595",
            "id": "pyup.io-46179",
            "more_info_path": "/vulnerabilities/CVE-2021-29595/46179",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41195",
            "id": "pyup.io-46205",
            "more_info_path": "/vulnerabilities/CVE-2021-41195/46205",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29605",
            "id": "pyup.io-46189",
            "more_info_path": "/vulnerabilities/CVE-2021-29605/46189",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-22925",
            "id": "pyup.io-46094",
            "more_info_path": "/vulnerabilities/CVE-2021-22925/46094",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29518",
            "id": "pyup.io-46102",
            "more_info_path": "/vulnerabilities/CVE-2021-29518/46102",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41203",
            "id": "pyup.io-46213",
            "more_info_path": "/vulnerabilities/CVE-2021-41203/46213",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29570",
            "id": "pyup.io-46154",
            "more_info_path": "/vulnerabilities/CVE-2021-29570/46154",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41217",
            "id": "pyup.io-46227",
            "more_info_path": "/vulnerabilities/CVE-2021-41217/46227",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29515",
            "id": "pyup.io-46099",
            "more_info_path": "/vulnerabilities/CVE-2021-29515/46099",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29550",
            "id": "pyup.io-46134",
            "more_info_path": "/vulnerabilities/CVE-2021-29550/46134",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29592",
            "id": "pyup.io-46176",
            "more_info_path": "/vulnerabilities/CVE-2021-29592/46176",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29553",
            "id": "pyup.io-46137",
            "more_info_path": "/vulnerabilities/CVE-2021-29553/46137",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29557",
            "id": "pyup.io-46141",
            "more_info_path": "/vulnerabilities/CVE-2021-29557/46141",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29601",
            "id": "pyup.io-46185",
            "more_info_path": "/vulnerabilities/CVE-2021-29601/46185",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29522",
            "id": "pyup.io-46106",
            "more_info_path": "/vulnerabilities/CVE-2021-29522/46106",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29598",
            "id": "pyup.io-46182",
            "more_info_path": "/vulnerabilities/CVE-2021-29598/46182",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41208",
            "id": "pyup.io-46218",
            "more_info_path": "/vulnerabilities/CVE-2021-41208/46218",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29576",
            "id": "pyup.io-46160",
            "more_info_path": "/vulnerabilities/CVE-2021-29576/46160",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29562",
            "id": "pyup.io-46146",
            "more_info_path": "/vulnerabilities/CVE-2021-29562/46146",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29589",
            "id": "pyup.io-46173",
            "more_info_path": "/vulnerabilities/CVE-2021-29589/46173",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29597",
            "id": "pyup.io-46181",
            "more_info_path": "/vulnerabilities/CVE-2021-29597/46181",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29577",
            "id": "pyup.io-46161",
            "more_info_path": "/vulnerabilities/CVE-2021-29577/46161",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29529",
            "id": "pyup.io-46113",
            "more_info_path": "/vulnerabilities/CVE-2021-29529/46113",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29578",
            "id": "pyup.io-46162",
            "more_info_path": "/vulnerabilities/CVE-2021-29578/46162",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29549",
            "id": "pyup.io-46133",
            "more_info_path": "/vulnerabilities/CVE-2021-29549/46133",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29554",
            "id": "pyup.io-46138",
            "more_info_path": "/vulnerabilities/CVE-2021-29554/46138",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-41222",
            "id": "pyup.io-46231",
            "more_info_path": "/vulnerabilities/CVE-2021-41222/46231",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29544",
            "id": "pyup.io-46128",
            "more_info_path": "/vulnerabilities/CVE-2021-29544/46128",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29532",
            "id": "pyup.io-46116",
            "more_info_path": "/vulnerabilities/CVE-2021-29532/46116",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29567",
            "id": "pyup.io-46151",
            "more_info_path": "/vulnerabilities/CVE-2021-29567/46151",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-22923",
            "id": "pyup.io-46092",
            "more_info_path": "/vulnerabilities/CVE-2021-22923/46092",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29514",
            "id": "pyup.io-46098",
            "more_info_path": "/vulnerabilities/CVE-2021-29514/46098",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29558",
            "id": "pyup.io-46142",
            "more_info_path": "/vulnerabilities/CVE-2021-29558/46142",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29527",
            "id": "pyup.io-46111",
            "more_info_path": "/vulnerabilities/CVE-2021-29527/46111",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29541",
            "id": "pyup.io-46125",
            "more_info_path": "/vulnerabilities/CVE-2021-29541/46125",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a0 updates its dependency 'TensorFlow' to v2.7.0 to include security fixes.",
            "cve": "CVE-2021-29542",
            "id": "pyup.io-46126",
            "more_info_path": "/vulnerabilities/CVE-2021-29542/46126",
            "specs": [
                "<1.2.0a0"
            ],
            "v": "<1.2.0a0"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23564",
            "id": "pyup.io-46527",
            "more_info_path": "/vulnerabilities/CVE-2022-23564/46527",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23572",
            "id": "pyup.io-46535",
            "more_info_path": "/vulnerabilities/CVE-2022-23572/46535",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23588",
            "id": "pyup.io-46551",
            "more_info_path": "/vulnerabilities/CVE-2022-23588/46551",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23566",
            "id": "pyup.io-46529",
            "more_info_path": "/vulnerabilities/CVE-2022-23566/46529",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21725",
            "id": "pyup.io-46503",
            "more_info_path": "/vulnerabilities/CVE-2022-21725/46503",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21729",
            "id": "pyup.io-46507",
            "more_info_path": "/vulnerabilities/CVE-2022-21729/46507",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23559",
            "id": "pyup.io-46522",
            "more_info_path": "/vulnerabilities/CVE-2022-23559/46522",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23584",
            "id": "pyup.io-46547",
            "more_info_path": "/vulnerabilities/CVE-2022-23584/46547",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21727",
            "id": "pyup.io-46505",
            "more_info_path": "/vulnerabilities/CVE-2022-21727/46505",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23595",
            "id": "pyup.io-46556",
            "more_info_path": "/vulnerabilities/CVE-2022-23595/46556",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21740",
            "id": "pyup.io-46518",
            "more_info_path": "/vulnerabilities/CVE-2022-21740/46518",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23574",
            "id": "pyup.io-46537",
            "more_info_path": "/vulnerabilities/CVE-2022-23574/46537",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23575",
            "id": "pyup.io-46538",
            "more_info_path": "/vulnerabilities/CVE-2022-23575/46538",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23573",
            "id": "pyup.io-46536",
            "more_info_path": "/vulnerabilities/CVE-2022-23573/46536",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23581",
            "id": "pyup.io-46544",
            "more_info_path": "/vulnerabilities/CVE-2022-23581/46544",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23577",
            "id": "pyup.io-46540",
            "more_info_path": "/vulnerabilities/CVE-2022-23577/46540",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21741",
            "id": "pyup.io-46519",
            "more_info_path": "/vulnerabilities/CVE-2022-21741/46519",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21732",
            "id": "pyup.io-46510",
            "more_info_path": "/vulnerabilities/CVE-2022-21732/46510",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23580",
            "id": "pyup.io-46543",
            "more_info_path": "/vulnerabilities/CVE-2022-23580/46543",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23563",
            "id": "pyup.io-46526",
            "more_info_path": "/vulnerabilities/CVE-2022-23563/46526",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21726",
            "id": "pyup.io-46504",
            "more_info_path": "/vulnerabilities/CVE-2022-21726/46504",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21734",
            "id": "pyup.io-46512",
            "more_info_path": "/vulnerabilities/CVE-2022-21734/46512",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23582",
            "id": "pyup.io-46545",
            "more_info_path": "/vulnerabilities/CVE-2022-23582/46545",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23586",
            "id": "pyup.io-46549",
            "more_info_path": "/vulnerabilities/CVE-2022-23586/46549",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23594",
            "id": "pyup.io-46555",
            "more_info_path": "/vulnerabilities/CVE-2022-23594/46555",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23578",
            "id": "pyup.io-46541",
            "more_info_path": "/vulnerabilities/CVE-2022-23578/46541",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23576",
            "id": "pyup.io-46539",
            "more_info_path": "/vulnerabilities/CVE-2022-23576/46539",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23589",
            "id": "pyup.io-46552",
            "more_info_path": "/vulnerabilities/CVE-2022-23589/46552",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21735",
            "id": "pyup.io-46513",
            "more_info_path": "/vulnerabilities/CVE-2022-21735/46513",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23561",
            "id": "pyup.io-46524",
            "more_info_path": "/vulnerabilities/CVE-2022-23561/46524",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23590",
            "id": "pyup.io-46553",
            "more_info_path": "/vulnerabilities/CVE-2022-23590/46553",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21731",
            "id": "pyup.io-46509",
            "more_info_path": "/vulnerabilities/CVE-2022-21731/46509",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23569",
            "id": "pyup.io-46532",
            "more_info_path": "/vulnerabilities/CVE-2022-23569/46532",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21738",
            "id": "pyup.io-46516",
            "more_info_path": "/vulnerabilities/CVE-2022-21738/46516",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21739",
            "id": "pyup.io-46517",
            "more_info_path": "/vulnerabilities/CVE-2022-21739/46517",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23568",
            "id": "pyup.io-46531",
            "more_info_path": "/vulnerabilities/CVE-2022-23568/46531",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23585",
            "id": "pyup.io-46548",
            "more_info_path": "/vulnerabilities/CVE-2022-23585/46548",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23558",
            "id": "pyup.io-46521",
            "more_info_path": "/vulnerabilities/CVE-2022-23558/46521",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23571",
            "id": "pyup.io-46534",
            "more_info_path": "/vulnerabilities/CVE-2022-23571/46534",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23557",
            "id": "pyup.io-46520",
            "more_info_path": "/vulnerabilities/CVE-2022-23557/46520",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2020-10531",
            "id": "pyup.io-46501",
            "more_info_path": "/vulnerabilities/CVE-2020-10531/46501",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23583",
            "id": "pyup.io-46546",
            "more_info_path": "/vulnerabilities/CVE-2022-23583/46546",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23562",
            "id": "pyup.io-46525",
            "more_info_path": "/vulnerabilities/CVE-2022-23562/46525",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21728",
            "id": "pyup.io-46506",
            "more_info_path": "/vulnerabilities/CVE-2022-21728/46506",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21737",
            "id": "pyup.io-46515",
            "more_info_path": "/vulnerabilities/CVE-2022-21737/46515",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23591",
            "id": "pyup.io-46554",
            "more_info_path": "/vulnerabilities/CVE-2022-23591/46554",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23567",
            "id": "pyup.io-46530",
            "more_info_path": "/vulnerabilities/CVE-2022-23567/46530",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21733",
            "id": "pyup.io-46511",
            "more_info_path": "/vulnerabilities/CVE-2022-21733/46511",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23570",
            "id": "pyup.io-46533",
            "more_info_path": "/vulnerabilities/CVE-2022-23570/46533",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21736",
            "id": "pyup.io-46514",
            "more_info_path": "/vulnerabilities/CVE-2022-21736/46514",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23579",
            "id": "pyup.io-46542",
            "more_info_path": "/vulnerabilities/CVE-2022-23579/46542",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23565",
            "id": "pyup.io-46528",
            "more_info_path": "/vulnerabilities/CVE-2022-23565/46528",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23560",
            "id": "pyup.io-46523",
            "more_info_path": "/vulnerabilities/CVE-2022-23560/46523",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-21730",
            "id": "pyup.io-46508",
            "more_info_path": "/vulnerabilities/CVE-2022-21730/46508",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        },
        {
            "advisory": "Sleap 1.2.0a6 requires Tensorflow v2.6.3 to include security fixes.",
            "cve": "CVE-2022-23587",
            "id": "pyup.io-46550",
            "more_info_path": "/vulnerabilities/CVE-2022-23587/46550",
            "specs": [
                "<1.2.0a6"
            ],
            "v": "<1.2.0a6"
        }
    ],
    "sleekxmpp": [
        {
            "advisory": "An incorrect implementation of \"XEP-0280: Message Carbons\" in multiple XMPP clients allows a remote attacker to impersonate any user, including contacts, in the vulnerable application's display. This allows for various kinds of social engineering attacks. This CVE is for SleekXMPP up to 1.3.1 and Slixmpp all versions up to 1.2.3, as bundled in poezio (0.8 - 0.10) and other products.",
            "cve": "CVE-2017-5591",
            "id": "pyup.io-53959",
            "more_info_path": "/vulnerabilities/CVE-2017-5591/53959",
            "specs": [
                ">=0,<1.3.2"
            ],
            "v": ">=0,<1.3.2"
        }
    ],
    "slenium": [
        {
            "advisory": "Slenium is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.",
            "cve": "PVE-2022-51757",
            "id": "pyup.io-51757",
            "more_info_path": "/vulnerabilities/PVE-2022-51757/51757",
            "specs": [
                ">0"
            ],
            "v": ">0"
        }
    ],
    "slixmpp": [
        {
            "advisory": "An incorrect implementation of \"XEP-0280: Message Carbons\" in multiple XMPP clients allows a remote attacker to impersonate any user, including contacts, in the vulnerable application's display. This allows for various kinds of social engineering attacks. This CVE is for SleekXMPP up to 1.3.1 and Slixmpp all versions up to 1.2.3, as bundled in poezio (0.8 - 0.10) and other products.",
            "cve": "CVE-2017-5591",
            "id": "pyup.io-53960",
            "more_info_path": "/vulnerabilities/CVE-2017-5591/53960",
            "specs": [
                ">=0,<1.2.4"
            ],
            "v": ">=0,<1.2.4"
        },
        {
            "advisory": "slixmpp version before commit 7cd73b594e8122dddf847953fcfc85ab4d316416 contains an incorrect Access Control vulnerability in XEP-0223 plugin (Persistent Storage of Private Data via PubSub) options profile, used for the configuration of default access model that can result in all of the contacts of the victim can see private data having been published to a PEP node. This attack appears to be exploitable if the user of this library publishes any private data on PEP, the node isn't configured to be private. This vulnerability appears to have been fixed in commit 7cd73b594e8122dddf847953fcfc85ab4d316416 which is included in slixmpp 1.4.2.",
            "cve": "CVE-2019-1000021",
            "id": "pyup.io-54209",
            "more_info_path": "/vulnerabilities/CVE-2019-1000021/54209",
            "specs": [
                ">=0,<1.4.2"
            ],
            "v": ">=0,<1.4.2"
        },
        {
            "advisory": "Slixmpp before 1.8.3 lacks SSL Certificate hostname validation in XMLStream, allowing an attacker to pose as any server in the eyes of Slixmpp.",
            "cve": "CVE-2022-45197",
            "id": "pyup.io-54601",
            "more_info_path": "/vulnerabilities/CVE-2022-45197/54601",
            "specs": [
                ">=0,<1.8.3"
            ],
            "v": ">=0,<1.8.3"
        }
    ],
    "slo-generator": [
        {
            "advisory": "SLO generator allows for loading of YAML files that if crafted in a specific format can allow for code execution within the context of the SLO Generator. We recommend upgrading SLO Generator past https://github.com/google/slo-generator/pull/173",
            "cve": "CVE-2021-22557",
            "id": "pyup.io-54343",
            "more_info_path": "/vulnerabilities/CVE-2021-22557/54343",
            "specs": [
                ">=0,<2.0.1"
            ],
            "v": ">=0,<2.0.1"
        }
    ],
    "smac-fastapi-auth": [
        {
            "advisory": "Smac-fastapi-auth versions prior to the update that bumps cryptography to 43.0.1 are potentially vulnerable to security issues, including CVE-2024-4603.",
            "cve": "CVE-2024-4603",
            "id": "pyup.io-73171",
            "more_info_path": "/vulnerabilities/CVE-2024-4603/73171",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        },
        {
            "advisory": "Smac-fastapi-auth 0.3.0 updates its dependency 'starlette' to include a security fix.",
            "cve": "CVE-2024-47874",
            "id": "pyup.io-74789",
            "more_info_path": "/vulnerabilities/CVE-2024-47874/74789",
            "specs": [
                "<0.3.0"
            ],
            "v": "<0.3.0"
        }
    ],
    "smart-app-framework": [
        {
            "advisory": "Smart-app-framework 2.3.0rc5 updates its dependency 'aiohttp' to version '3.8.5' to include a fix for an HTTP Request Smuggling vulnerability.",
            "cve": "CVE-2023-37276",
            "id": "pyup.io-60331",
            "more_info_path": "/vulnerabilities/CVE-2023-37276/60331",
            "specs": [
                "<2.3.0rc5"
            ],
            "v": "<2.3.0rc5"
        },
        {
            "advisory": "Smart-app-framework 2.3.0rc5 updates its dependency 'nltk' to version '3.8.1' to include a fix for a ReDoS vulnerability.",
            "cve": "CVE-2021-43854",
            "id": "pyup.io-60336",
            "more_info_path": "/vulnerabilities/CVE-2021-43854/60336",
            "specs": [
                "<2.3.0rc5"
            ],
            "v": "<2.3.0rc5"
        },
        {
            "advisory": "Smart-app-framework 2.3.0rc5 updates its dependency 'nltk' to version '3.8.1' to include a fix for a ReDoS vulnerability.",
            "cve": "CVE-2021-3842",
            "id": "pyup.io-60335",
            "more_info_path": "/vulnerabilities/CVE-2021-3842/60335",
            "specs": [
                "<2.3.0rc5"
            ],
            "v": "<2.3.0rc5"
        },
        {
            "advisory": "Smart-app-framework 2.3.0rc5 updates its dependency 'PyYAML' to version '6.0.1' to include a fix for an Arbitrary Code Execution vulnerability.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-60339",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/60339",
            "specs": [
                "<2.3.0rc5"
            ],
            "v": "<2.3.0rc5"
        },
        {
            "advisory": "Smart-app-framework 2.3.0rc5 updates its dependency 'PyYAML' to version '6.0.1' to include a fix for an Arbitrary Code Execution vulnerability.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-60340",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/60340",
            "specs": [
                "<2.3.0rc5"
            ],
            "v": "<2.3.0rc5"
        },
        {
            "advisory": "Smart-app-framework 2.3.0rc5 updates its dependency 'nltk' to version '3.8.1' to include a fix for a ReDoS vulnerability.",
            "cve": "CVE-2021-3828",
            "id": "pyup.io-60337",
            "more_info_path": "/vulnerabilities/CVE-2021-3828/60337",
            "specs": [
                "<2.3.0rc5"
            ],
            "v": "<2.3.0rc5"
        }
    ],
    "smb": [
        {
            "advisory": "Smb is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware",
            "cve": "PVE-2022-45437",
            "id": "pyup.io-45437",
            "more_info_path": "/vulnerabilities/PVE-2022-45437/45437",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "smbprotocol": [
        {
            "advisory": "Smbprotocol 1.4.0 adds few important security improvements.",
            "cve": "PVE-2021-40415",
            "id": "pyup.io-40415",
            "more_info_path": "/vulnerabilities/PVE-2021-40415/40415",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        },
        {
            "advisory": "Smbprotocol 1.8.0 fixes unpacking of ACEs which could lead to undesired crashes or running into endless loops.\r\nhttps://github.com/jborean93/smbprotocol/pull/143",
            "cve": "PVE-2021-42734",
            "id": "pyup.io-42734",
            "more_info_path": "/vulnerabilities/PVE-2021-42734/42734",
            "specs": [
                "<1.8.0"
            ],
            "v": "<1.8.0"
        }
    ],
    "smeagol": [
        {
            "advisory": "Smeagol has several known bugs and security issues that need to be addressed before it can be used in production.",
            "cve": "PVE-2021-34818",
            "id": "pyup.io-34818",
            "more_info_path": "/vulnerabilities/PVE-2021-34818/34818",
            "specs": [
                "<=0.1.4"
            ],
            "v": "<=0.1.4"
        }
    ],
    "smok": [
        {
            "advisory": "Smok 0.20.1 includes a fix for a code injection vulnerability.\r\nhttps://github.com/smok-serwis/smok-client/commit/a97b3dac454569f55a8a28a1cac44ae04e3e9cde",
            "cve": "PVE-2022-52432",
            "id": "pyup.io-52432",
            "more_info_path": "/vulnerabilities/PVE-2022-52432/52432",
            "specs": [
                "<0.20.1"
            ],
            "v": "<0.20.1"
        }
    ],
    "smolagents": [
        {
            "advisory": "A sandbox escape vulnerability was identified in huggingface/smolagents version 1.14.0, allowing attackers to bypass the restricted execution environment and achieve remote code execution (RCE). The vulnerability stems from the local_python_executor.py module, which inadequately restricts Python code execution despite employing static and dynamic checks. Attackers can exploit whitelisted modules and functions to execute arbitrary code, compromising the host system. This flaw undermines the core security boundary intended to isolate untrusted code, posing risks such as unauthorized code execution, data leakage, and potential integration-level compromise. The issue is resolved in version 1.17.0.",
            "cve": "CVE-2025-5120",
            "id": "pyup.io-78514",
            "more_info_path": "/vulnerabilities/CVE-2025-5120/78514",
            "specs": [
                "<1.17.0"
            ],
            "v": "<1.17.0"
        },
        {
            "advisory": "Affected versions of the smolagents package are vulnerable to XPath Injection due to unescaped user-supplied text being interpolated directly into an XPath literal. In src/smolagents/vision_web_browser.py, the search_item_ctrl_f function constructed an expression like //*[contains(text(), '{text}')] with the text parameter unescaped, allowing quotes and XPath operators to alter the predicate; the fix adds _escape_xpath_string and uses its output in driver.find_elements to safely embed the literal.",
            "cve": "PVE-2025-79863",
            "id": "pyup.io-79863",
            "more_info_path": "/vulnerabilities/PVE-2025-79863/79863",
            "specs": [
                "<1.22.0"
            ],
            "v": "<1.22.0"
        },
        {
            "advisory": "Affected versions of the smolagents package are vulnerable to XPath Injection due to direct concatenation of user-controlled search text into an XPath expression. The search_item_ctrl_f function in src/smolagents/vision_web_browser.py constructs a By.XPATH selector using an f-string (previously driver.find_elements(By.XPATH, f\"//*[contains(text(), '{text}')]\")) without neutralizing quotes or special characters, allowing crafted input to change the query\u2019s predicate.",
            "cve": "CVE-2025-11844",
            "id": "pyup.io-80586",
            "more_info_path": "/vulnerabilities/CVE-2025-11844/80586",
            "specs": [
                "<1.22.0"
            ],
            "v": "<1.22.0"
        },
        {
            "advisory": "Affected versions of Smolagents are vulnerable to arbitrary code execution. This allows attackers to execute malicious commands with application privileges. The attack vector involves supply chain attacks where a malicious LLM leverages authorized packages. Vulnerable methods include private functions like random._os_system.",
            "cve": "PVE-2025-75159",
            "id": "pyup.io-75159",
            "more_info_path": "/vulnerabilities/PVE-2025-75159/75159",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        },
        {
            "advisory": "Affected versions of the smolagents package are potentially vulnerable to Arbitrary Code Execution through unrestricted invocation of built-in Python functions. The issue resides in the evaluate_call function within src/smolagents/local_python_executor.py, where built-in functions like open or __import__ were previously unrestricted. This issue has been addressed by restricting function invocation to only those built-ins explicitly defined in static_tools.",
            "cve": "PVE-2025-75158",
            "id": "pyup.io-75158",
            "more_info_path": "/vulnerabilities/PVE-2025-75158/75158",
            "specs": [
                "<1.5.0"
            ],
            "v": "<1.5.0"
        }
    ],
    "smoosense": [
        {
            "advisory": "Affected versions of smoosense-gui are vulnerable to SQL Injection. The parseFilters.ts and helpers.ts utility functions fail to escape single quotes in user input before constructing SQL queries with LIKE wildcard operators, leading to arbitrary SQL command execution through malicious filter values containing unescaped single quote characters.",
            "cve": "PVE-2025-81665",
            "id": "pyup.io-81665",
            "more_info_path": "/vulnerabilities/PVE-2025-81665/81665",
            "specs": [
                "<0.1.16"
            ],
            "v": "<0.1.16"
        }
    ],
    "smplejson": [
        {
            "advisory": "Smplejson is a typosquatting package. It shows a malicious behavior, for example, it may leak your sensitive data and/or gain unauthorized persistence in your system.\r\nhttps://www.zdnet.com/article/twelve-malicious-python-libraries-found-and-removed-from-pypi/",
            "cve": "PVE-2022-45417",
            "id": "pyup.io-45417",
            "more_info_path": "/vulnerabilities/PVE-2022-45417/45417",
            "specs": [
                ">0",
                "<0"
            ],
            "v": ">0,<0"
        }
    ],
    "smqtk": [
        {
            "advisory": "Smqtk 0.11.0 includes a number of security and stability fixes for algorithms and the IQR demo web application.",
            "cve": "PVE-2021-38777",
            "id": "pyup.io-38777",
            "more_info_path": "/vulnerabilities/PVE-2021-38777/38777",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "smqtk-core": [
        {
            "advisory": "Smqtk-core 0.18.2 updates its dependency 'ipython' to v7.16.3 to include a security fix.",
            "cve": "CVE-2022-21699",
            "id": "pyup.io-52540",
            "more_info_path": "/vulnerabilities/CVE-2022-21699/52540",
            "specs": [
                "<0.18.2"
            ],
            "v": "<0.18.2"
        },
        {
            "advisory": "Smqtk-core 0.18.2 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-52401",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/52401",
            "specs": [
                "<0.18.2"
            ],
            "v": "<0.18.2"
        }
    ],
    "smqtk-dataprovider": [
        {
            "advisory": "Smqtk-dataprovider 0.17.0 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-52409",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/52409",
            "specs": [
                "<0.17.0"
            ],
            "v": "<0.17.0"
        },
        {
            "advisory": "Smqtk-dataprovider 0.17.0 updates its dependency 'ipython' to v7.16.3 to include a security fix.",
            "cve": "CVE-2022-21699",
            "id": "pyup.io-52535",
            "more_info_path": "/vulnerabilities/CVE-2022-21699/52535",
            "specs": [
                "<0.17.0"
            ],
            "v": "<0.17.0"
        }
    ],
    "smqtk-descriptors": [
        {
            "advisory": "Smqtk-descriptors 0.19.0 updates its dependency 'urllib3' to version '1.26.5' to include a security fix.\r\nhttps://github.com/Kitware/SMQTK-Descriptors/commit/b5bb08b105bab79c595fe07f82d9c5dda47059fe",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-59095",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/59095",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        },
        {
            "advisory": "Smqtk-descriptors 0.19.0 updates its dependency 'pillow' to version '8.3.2' to include a security fix.\r\nhttps://github.com/Kitware/SMQTK-Descriptors/commit/805be76a831b33802b6ebd9ac90496fd93d60a9f",
            "cve": "CVE-2021-25921",
            "id": "pyup.io-59159",
            "more_info_path": "/vulnerabilities/CVE-2021-25921/59159",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        },
        {
            "advisory": "Smqtk-descriptors 0.19.0 updates its dependency 'ipython' to version '7.16.3' to include a security fix.\r\nhttps://github.com/Kitware/SMQTK-Descriptors/commit/64e889344fddb5de64323d6c7d5b2388cfd6483f",
            "cve": "CVE-2022-21699",
            "id": "pyup.io-59106",
            "more_info_path": "/vulnerabilities/CVE-2022-21699/59106",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        },
        {
            "advisory": "Smqtk-descriptors 0.19.0 updates its dependency 'pillow' to version '8.3.2' to include a security fix.\r\nhttps://github.com/Kitware/SMQTK-Descriptors/commit/805be76a831b33802b6ebd9ac90496fd93d60a9f",
            "cve": "CVE-2021-25922",
            "id": "pyup.io-59105",
            "more_info_path": "/vulnerabilities/CVE-2021-25922/59105",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        },
        {
            "advisory": "Smqtk-descriptors 0.19.0 updates its dependency 'pillow' to version '8.3.2' to include a security fix.\r\nhttps://github.com/Kitware/SMQTK-Descriptors/commit/805be76a831b33802b6ebd9ac90496fd93d60a9f",
            "cve": "CVE-2021-25293",
            "id": "pyup.io-59160",
            "more_info_path": "/vulnerabilities/CVE-2021-25293/59160",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        },
        {
            "advisory": "Smqtk-descriptors 0.19.0 updates its dependency 'pillow' to version '8.3.2' to include a security fix.\r\nhttps://github.com/Kitware/SMQTK-Descriptors/commit/805be76a831b33802b6ebd9ac90496fd93d60a9f",
            "cve": "CVE-2021-25291",
            "id": "pyup.io-59162",
            "more_info_path": "/vulnerabilities/CVE-2021-25291/59162",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        },
        {
            "advisory": "Smqtk-descriptors 0.19.0 updates its dependency 'pillow' to version '8.3.2' to include a security fix.\r\nhttps://github.com/Kitware/SMQTK-Descriptors/commit/805be76a831b33802b6ebd9ac90496fd93d60a9f",
            "cve": "CVE-2021-25290",
            "id": "pyup.io-59163",
            "more_info_path": "/vulnerabilities/CVE-2021-25290/59163",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        },
        {
            "advisory": "Smqtk-descriptors 0.19.0 updates its dependency 'pillow' to version '8.3.2' to include a security fix.\r\nhttps://github.com/Kitware/SMQTK-Descriptors/commit/805be76a831b33802b6ebd9ac90496fd93d60a9f",
            "cve": "CVE-2021-25289",
            "id": "pyup.io-59164",
            "more_info_path": "/vulnerabilities/CVE-2021-25289/59164",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        },
        {
            "advisory": "Smqtk-descriptors 0.19.0 updates its dependency 'pillow' to version '8.3.2' to include a security fix.\r\nhttps://github.com/Kitware/SMQTK-Descriptors/commit/805be76a831b33802b6ebd9ac90496fd93d60a9f",
            "cve": "CVE-2021-25292",
            "id": "pyup.io-59161",
            "more_info_path": "/vulnerabilities/CVE-2021-25292/59161",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        }
    ],
    "smqtk-detection": [
        {
            "advisory": "Smqtk-detection 0.17.0 updates its dependency 'pillow' to v8.3.2 to include security fixes.",
            "cve": "CVE-2021-23437",
            "id": "pyup.io-42901",
            "more_info_path": "/vulnerabilities/CVE-2021-23437/42901",
            "specs": [
                "<0.17.0"
            ],
            "v": "<0.17.0"
        },
        {
            "advisory": "Smqtk-detection 0.19.0 updates its dependency 'ipython' to v7.16.3 to include a security fix.",
            "cve": "CVE-2022-21699",
            "id": "pyup.io-49253",
            "more_info_path": "/vulnerabilities/CVE-2022-21699/49253",
            "specs": [
                "<0.19.0"
            ],
            "v": "<0.19.0"
        }
    ],
    "smriprep": [
        {
            "advisory": "Smriprep 0.12.0 includes fixes for XSS vulnerabilities in its dependency 'JQuery'.\r\nhttps://github.com/nipreps/smriprep/pull/332",
            "cve": "CVE-2020-11022",
            "id": "pyup.io-58934",
            "more_info_path": "/vulnerabilities/CVE-2020-11022/58934",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        },
        {
            "advisory": "Smriprep 0.12.0 includes fixes for XSS vulnerabilities in its dependency 'JQuery'.\r\nhttps://github.com/nipreps/smriprep/pull/332",
            "cve": "CVE-2020-11023",
            "id": "pyup.io-59063",
            "more_info_path": "/vulnerabilities/CVE-2020-11023/59063",
            "specs": [
                "<0.12.0"
            ],
            "v": "<0.12.0"
        }
    ],
    "smtpdfix": [
        {
            "advisory": "Smtpdfix 0.2.9 requires a 'cryptography' dependency version 3.4.4 in response to security reports.",
            "cve": "CVE-2020-36242",
            "id": "pyup.io-39708",
            "more_info_path": "/vulnerabilities/CVE-2020-36242/39708",
            "specs": [
                "<0.2.9"
            ],
            "v": "<0.2.9"
        }
    ],
    "snakebids": [
        {
            "advisory": "Snakebids 0.6.1 updates its dependency 'cookiecutter' to versions '^2.1.1' to include a security fix.",
            "cve": "CVE-2022-24065",
            "id": "pyup.io-49434",
            "more_info_path": "/vulnerabilities/CVE-2022-24065/49434",
            "specs": [
                "<0.6.1"
            ],
            "v": "<0.6.1"
        }
    ],
    "snakemake": [
        {
            "advisory": "Snakemake 5.28.0 parses values more securely when using --config.",
            "cve": "PVE-2021-39106",
            "id": "pyup.io-39106",
            "more_info_path": "/vulnerabilities/PVE-2021-39106/39106",
            "specs": [
                "<5.28.0"
            ],
            "v": "<5.28.0"
        },
        {
            "advisory": "Snakemake 6.11.1 addresses a race condition related to the execution of multiple Jupyter notebooks concurrently. It provides a temporary IPYTHONDIR for each notebook execution.\r\nhttps://github.com/snakemake/snakemake/pull/1280\r\nhttps://github.com/snakemake/snakemake/commit/4d70da11f810224ddce192ae1472a6380898865f",
            "cve": "PVE-2024-63790",
            "id": "pyup.io-63790",
            "more_info_path": "/vulnerabilities/PVE-2024-63790/63790",
            "specs": [
                "<6.11.1"
            ],
            "v": "<6.11.1"
        },
        {
            "advisory": "Snakemake 7.25.2 addresses a race condition in the creation of lock directories. \r\nhttps://github.com/snakemake/snakemake/commit/66ea4d199e3d9266b1b5fdb8752772e8137ffdea",
            "cve": "PVE-2024-63788",
            "id": "pyup.io-63788",
            "more_info_path": "/vulnerabilities/PVE-2024-63788/63788",
            "specs": [
                "<7.25.2"
            ],
            "v": "<7.25.2"
        },
        {
            "advisory": "Snakemake 7.9.0 resolves a race condition that involved concurrent writing operations leading to data inconsistencies.\r\nhttps://github.com/snakemake/snakemake/pull/1745\r\nhttps://github.com/snakemake/snakemake/commit/71fe9527bb7011ba01d25fdd21c102c135412c04",
            "cve": "PVE-2024-63789",
            "id": "pyup.io-63789",
            "more_info_path": "/vulnerabilities/PVE-2024-63789/63789",
            "specs": [
                "<7.9.0"
            ],
            "v": "<7.9.0"
        },
        {
            "advisory": "Affected versions of Snakemake are vulnerable to Remote Code Execution (RCE) due to the use of eval with command line input. This vulnerability allows for the execution of arbitrary code.",
            "cve": "PVE-2024-99864",
            "id": "pyup.io-65556",
            "more_info_path": "/vulnerabilities/PVE-2024-99864/65556",
            "specs": [
                ">=0,<5.28.0"
            ],
            "v": ">=0,<5.28.0"
        }
    ],
    "snapcraft": [
        {
            "advisory": "In some conditions, a snap package built by snapcraft includes the current directory in LD_LIBRARY_PATH, allowing a malicious snap to gain code execution within the context of another snap if both plug the home interface or similar. This issue affects snapcraft versions prior to 4.4.4, prior to 2.43.1+16.04.1, and prior to 2.43.1+18.04.1.",
            "cve": "CVE-2020-27348",
            "id": "pyup.io-42291",
            "more_info_path": "/vulnerabilities/CVE-2020-27348/42291",
            "specs": [
                "<4.4.4"
            ],
            "v": "<4.4.4"
        }
    ],
    "snappass": [
        {
            "advisory": "Snappass 1.4.1 includes a fix for CVE-2018-10903: A flaw was found in python-cryptography versions between >=1.9.0 and <2.3. The finalize_with_tag API did not enforce a minimum tag length. If a user did not validate the input length prior to passing it to finalize_with_tag an attacker could craft an invalid payload with a shortened tag (e.g. 1 byte) such that they would have a 1 in 256 chance of passing the MAC check. GCM tag forgeries can cause key leakage.",
            "cve": "CVE-2018-10903",
            "id": "pyup.io-36605",
            "more_info_path": "/vulnerabilities/CVE-2018-10903/36605",
            "specs": [
                "<1.4.1"
            ],
            "v": "<1.4.1"
        }
    ],
    "sncli": [
        {
            "advisory": "Sncli 0.4.0 contains a security fix for an arbitrary code execution bug. Copying text from notes to the clipboard was being performed by building a shell command to execute. This resulted in the line being copied substituted directly into the shell command. A carefully crafted line could run any arbitrary shell command, and some lines could crash the process causing the line to fail to copy. This fixes the issue by not using a shell to interpret the command, and passing the text to be copied directly to stdin.\r\nhttps://github.com/insanum/sncli/commit/ecc410f8f55e7adbbfbec1b14176568ac2a39da5",
            "cve": "PVE-2021-37302",
            "id": "pyup.io-37302",
            "more_info_path": "/vulnerabilities/PVE-2021-37302/37302",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "snowflake-cli": [
        {
            "advisory": "Affected versions of the Snowflake CLI package are vulnerable to an Information Exposure vulnerability (CWE-200). This vulnerability results in plaintext passwords being displayed when users execute the snow connection list command, potentially exposing sensitive credentials to unauthorized individuals. The issue resides in the list_connections function, which fails to mask or omit the password field in the connection parameters. Attackers or unauthorized users with access to the command output could exploit this to gain unauthorized access to Snowflake accounts. To mitigate this issue, users should update to the latest version where passwords are properly masked, and ensure that command outputs containing sensitive information are not shared or logged.",
            "cve": "PVE-2024-73612",
            "id": "pyup.io-73612",
            "more_info_path": "/vulnerabilities/PVE-2024-73612/73612",
            "specs": [
                "<2.1.1"
            ],
            "v": "<2.1.1"
        }
    ],
    "snowflake-connector-python": [
        {
            "advisory": "Snowflake-connector-python 2.8.2 includes a fix for CVE-2022-42965: An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the snowflake-connector-python PyPI package, when an attacker is able to supply arbitrary input to the undocumented get_file_transfer_type method.",
            "cve": "CVE-2022-42965",
            "id": "pyup.io-51802",
            "more_info_path": "/vulnerabilities/CVE-2022-42965/51802",
            "specs": [
                "<2.8.2"
            ],
            "v": "<2.8.2"
        },
        {
            "advisory": "Snowflake-connector-python 3.0.2 includes a fix for CVE-2023-34233: A command injection vulnerability in the Snowflake Python connector via SSO browser URL authentication.\r\nhttps://github.com/snowflakedb/snowflake-connector-python/commit/1cdbd3b1403c5ef520d7f4d9614fe35165e101ac\r\nhttps://github.com/snowflakedb/snowflake-connector-python/pull/1480\r\nhttps://github.com/snowflakedb/snowflake-connector-python/security/advisories/GHSA-5w5m-pfw9-c8fp",
            "cve": "CVE-2023-34233",
            "id": "pyup.io-58971",
            "more_info_path": "/vulnerabilities/CVE-2023-34233/58971",
            "specs": [
                "<3.0.2"
            ],
            "v": "<3.0.2"
        },
        {
            "advisory": "Affected versions of Snowflake Connector for Python are vulnerable to Sensitive Information Exposure (CWE-532). The connector was logging sensitive authentication data including tokens, private keys, and credentials in debug logs. An attacker with access to log files could extract authentication tokens, private keys, and other sensitive data. The vulnerability exists in the Auth class logging functionality and insufficient secret detection patterns. This is exploitable wherever debug logging is enabled. The issue affects _auth.py and secret_detector.py modules, which failed to properly mask all sensitive data formats. Organizations should also rotate any credentials that may have been logged in debug output.",
            "cve": "CVE-2024-49750",
            "id": "pyup.io-73970",
            "more_info_path": "/vulnerabilities/CVE-2024-49750/73970",
            "specs": [
                "<3.12.3"
            ],
            "v": "<3.12.3"
        },
        {
            "advisory": "Affected versions of the snowflake-connector-python package are vulnerable to Insecure File Permissions due to accepting configuration files that are writable by the group or other users. The ConfigManager.read_config path in src/snowflake/connector/config_manager.py previously only warned on permissive read/ownership and did not error when the config file\u2019s mode included stat.S_IWGRP or stat.S_IWOTH, allowing sensitive settings to be modified until commit e3349a3 added an explicit check that raises ConfigSourceError.",
            "cve": "PVE-2025-80257",
            "id": "pyup.io-80257",
            "more_info_path": "/vulnerabilities/PVE-2025-80257/80257",
            "specs": [
                "<4.0.0"
            ],
            "v": "<4.0.0"
        },
        {
            "advisory": "Snowflake-connector-python affected versions are vulnerable to SQL Injection in write_pandas.",
            "cve": "CVE-2025-24793",
            "id": "pyup.io-76347",
            "more_info_path": "/vulnerabilities/CVE-2025-24793/76347",
            "specs": [
                ">=2.2.5,<3.13.1"
            ],
            "v": ">=2.2.5,<3.13.1"
        },
        {
            "advisory": "Snowflake discovered and remediated a vulnerability in the Snowflake Connector for Python. On Linux systems, when temporary credential caching is enabled, the Snowflake Connector for Python will cache temporary credentials locally in a world-readable file.",
            "cve": "CVE-2025-24795",
            "id": "pyup.io-76349",
            "more_info_path": "/vulnerabilities/CVE-2025-24795/76349",
            "specs": [
                ">=2.3.7,<3.13.1"
            ],
            "v": ">=2.3.7,<3.13.1"
        },
        {
            "advisory": "Snowflake-connector-python affected versions are vulnerable to insecure deserialization of the OCSP response cache.",
            "cve": "CVE-2025-24794",
            "id": "pyup.io-76348",
            "more_info_path": "/vulnerabilities/CVE-2025-24794/76348",
            "specs": [
                ">=2.7.12,<3.13.1"
            ],
            "v": ">=2.7.12,<3.13.1"
        }
    ],
    "snudown": [
        {
            "advisory": "Snudown 1.7.0 includes a fix for CVE-2021-41168: In affected versions snudown was found to be vulnerable to denial of service attacks to its reference table implementation. References written in markdown \" [reference_name]: https://www.example.com\" are inserted into a hash table which was found to have a weak hash function, meaning that an attacker can reliably generate a large number of collisions for it. This makes the hash table vulnerable to a hash-collision DoS attack, a type of algorithmic complexity attack. Further, the hash table allows for duplicate entries resulting in long retrieval times. Proofs of concept and further discussion of the hash collision issue are discussed on the snudown GHSA (https://github.com/reddit/snudown/security/advisories/GHSA-6gvv-9q92-w5f6).\r\nhttps://github.com/reddit/snudown/commit/1ac2c130b210539ee1e5d67a7bac93f9d8007c0e",
            "cve": "CVE-2021-41168",
            "id": "pyup.io-42206",
            "more_info_path": "/vulnerabilities/CVE-2021-41168/42206",
            "specs": [
                "<1.7.0"
            ],
            "v": "<1.7.0"
        }
    ],
    "snyk-tags": [
        {
            "advisory": "Snyk-tags 0.4.2 updates its dependency 'httpx' to v0.23.0 to include a security fix.",
            "cve": "CVE-2021-41945",
            "id": "pyup.io-50154",
            "more_info_path": "/vulnerabilities/CVE-2021-41945/50154",
            "specs": [
                "<0.4.2"
            ],
            "v": "<0.4.2"
        },
        {
            "advisory": "Snyk-tags version 2.2.4 updates its dependency on the cryptography library to version 42.0.4. This change is made to address the security issue identified as CVE-2024-26130.",
            "cve": "CVE-2024-26130",
            "id": "pyup.io-67579",
            "more_info_path": "/vulnerabilities/CVE-2024-26130/67579",
            "specs": [
                "<2.2.4"
            ],
            "v": "<2.2.4"
        },
        {
            "advisory": "Snyk-tags version 2.2.4 updates its dependency on the cryptography library to version 42.0.4. This change is made to address the security issue identified as CVE-2024-0727.",
            "cve": "CVE-2024-0727",
            "id": "pyup.io-67576",
            "more_info_path": "/vulnerabilities/CVE-2024-0727/67576",
            "specs": [
                "<2.2.4"
            ],
            "v": "<2.2.4"
        },
        {
            "advisory": "Snyk-tags version 2.2.4 updates its dependency on the cryptography library to version 42.0.4. This change is made to address the security issue identified asCVE-2023-49083.",
            "cve": "CVE-2023-49083",
            "id": "pyup.io-67581",
            "more_info_path": "/vulnerabilities/CVE-2023-49083/67581",
            "specs": [
                "<2.2.4"
            ],
            "v": "<2.2.4"
        },
        {
            "advisory": "Snyk-tags version 2.2.4 updates its dependency on the cryptography library to version 42.0.4. This change is made to address the security issue identified as CVE-2023-50782.",
            "cve": "CVE-2023-50782",
            "id": "pyup.io-67580",
            "more_info_path": "/vulnerabilities/CVE-2023-50782/67580",
            "specs": [
                "<2.2.4"
            ],
            "v": "<2.2.4"
        },
        {
            "advisory": "Snyk-tags version 2.2.4 updates its dependency on the cryptography library to version 42.0.4. This change is made to address the security issue identified as CVE-2023-5678.",
            "cve": "CVE-2023-5678",
            "id": "pyup.io-67575",
            "more_info_path": "/vulnerabilities/CVE-2023-5678/67575",
            "specs": [
                "<2.2.4"
            ],
            "v": "<2.2.4"
        },
        {
            "advisory": "Snyk-tags version 2.2.4 updates its dependency on the cryptography library to version 42.0.4. This change is made to address the security issue identified as CVE-2023-6237.",
            "cve": "CVE-2023-6237",
            "id": "pyup.io-67577",
            "more_info_path": "/vulnerabilities/CVE-2023-6237/67577",
            "specs": [
                "<2.2.4"
            ],
            "v": "<2.2.4"
        },
        {
            "advisory": "Snyk-tags version 2.2.4 updates its dependency on the cryptography library to version 42.0.4. This change is made to address the security issue identified as CVE-2023-6129.",
            "cve": "CVE-2023-6129",
            "id": "pyup.io-67578",
            "more_info_path": "/vulnerabilities/CVE-2023-6129/67578",
            "specs": [
                "<2.2.4"
            ],
            "v": "<2.2.4"
        },
        {
            "advisory": "Snyk-tags version 2.2.4 updates its dependency on the cryptography library to version 42.0.4. This change is made to address the security issue identified as CVE-2023-5363.",
            "cve": "CVE-2023-5363",
            "id": "pyup.io-67567",
            "more_info_path": "/vulnerabilities/CVE-2023-5363/67567",
            "specs": [
                "<2.2.4"
            ],
            "v": "<2.2.4"
        }
    ],
    "soapfish": [
        {
            "advisory": "soapfish before 0.6.0 has a potential security issue - pattern restrictions were not applied correctly.",
            "cve": "PVE-2021-26136",
            "id": "pyup.io-26136",
            "more_info_path": "/vulnerabilities/PVE-2021-26136/26136",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "soappy": [
        {
            "advisory": "soappy before 0.12.6 allows remote attackers to read arbitrary files via a SOAP request containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.",
            "cve": "CVE-2014-3242",
            "id": "pyup.io-26137",
            "more_info_path": "/vulnerabilities/CVE-2014-3242/26137",
            "specs": [
                "<0.12.6"
            ],
            "v": "<0.12.6"
        },
        {
            "advisory": "SOAPpy 0.12.5 does not properly detect recursion during entity expansion, which allows remote attackers to cause a denial of service (memory and CPU consumption) via a crafted SOAP request containing a large number of nested entity references.",
            "cve": "CVE-2014-3243",
            "id": "pyup.io-65820",
            "more_info_path": "/vulnerabilities/CVE-2014-3243/65820",
            "specs": [
                ">=0.0,<0.12.6"
            ],
            "v": ">=0.0,<0.12.6"
        }
    ],
    "soappy-py3": [
        {
            "advisory": "soappy-py3 before 0.12.6 allows remote attackers to read arbitrary files via a SOAP request containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.",
            "cve": "PVE-2021-26138",
            "id": "pyup.io-26138",
            "more_info_path": "/vulnerabilities/PVE-2021-26138/26138",
            "specs": [
                "<0.12.6"
            ],
            "v": "<0.12.6"
        }
    ],
    "social-auth-app-django": [
        {
            "advisory": "Python Social Auth is a social authentication/registration mechanism. Prior to version 5.4.1, due to default case-insensitive collation in MySQL or MariaDB databases, third-party authentication user IDs are not case-sensitive and could cause different IDs to match. This issue has been addressed by a fix released in version 5.4.1. An immediate workaround would be to change collation of the affected field. See CVE-2024-32879.",
            "cve": "CVE-2024-32879",
            "id": "pyup.io-70713",
            "more_info_path": "/vulnerabilities/CVE-2024-32879/70713",
            "specs": [
                "<5.4.1"
            ],
            "v": "<5.4.1"
        },
        {
            "advisory": "Affected versions of the social-auth-app-django package are vulnerable to Authentication Bypass due to unintended email-based account association during the authentication pipeline. In social_django.storage.create_user (invoked by social_core.pipeline.user.create_user), an IntegrityError during user creation triggers a fallback that returns an existing User looked up by e-mail, effectively performing social_core.pipeline.social_auth.associate_by_email even when that step is disabled.",
            "cve": "CVE-2025-61783",
            "id": "pyup.io-80315",
            "more_info_path": "/vulnerabilities/CVE-2025-61783/80315",
            "specs": [
                "<5.6.0"
            ],
            "v": "<5.6.0"
        }
    ],
    "socketshark": [
        {
            "advisory": "Socketshark 0.2.2 includes a fix for a sensitive information exposure vulnerability.\r\nhttps://github.com/closeio/socketshark/pull/42",
            "cve": "PVE-2022-52315",
            "id": "pyup.io-52315",
            "more_info_path": "/vulnerabilities/PVE-2022-52315/52315",
            "specs": [
                "<0.2.2"
            ],
            "v": "<0.2.2"
        },
        {
            "advisory": "Certain versions of socketshark, a WebSocket message router, are susceptible to credential exposure vulnerability due to usernames and passwords potentially appearing in URL strings within logs.",
            "cve": "PVE-2024-99863",
            "id": "pyup.io-65557",
            "more_info_path": "/vulnerabilities/PVE-2024-99863/65557",
            "specs": [
                ">=0,<0.2.2"
            ],
            "v": ">=0,<0.2.2"
        }
    ],
    "sockeye": [
        {
            "advisory": "Sockeye is an open-source sequence-to-sequence framework for Neural Machine Translation built on PyTorch. Sockeye uses YAML to store model and data configurations on disk. Versions below 2.3.24 use unsafe YAML loading, which can be made to execute arbitrary code embedded in config files. An attacker can add malicious code to the config file of a trained model and attempt to convince users to download and run it. If users run the model, the embedded code will run locally. The issue is fixed in version 2.3.24.",
            "cve": "CVE-2021-43811",
            "id": "pyup.io-54246",
            "more_info_path": "/vulnerabilities/CVE-2021-43811/54246",
            "specs": [
                ">=0,<2.3.24"
            ],
            "v": ">=0,<2.3.24"
        }
    ],
    "sockjs-tornado": [
        {
            "advisory": "Sockjs-tornado 1.0.7 includes a fix for a XSS vulnerability. The fix issued for the XSS vuln in 1.0.6 was incomplete.\r\nhttps://github.com/mrjoes/sockjs-tornado/commit/902b19c4a2015f20e1e2be42c8451e971db41a61",
            "cve": "PVE-2021-38215",
            "id": "pyup.io-38215",
            "more_info_path": "/vulnerabilities/PVE-2021-38215/38215",
            "specs": [
                "<1.0.7"
            ],
            "v": "<1.0.7"
        },
        {
            "advisory": "Versions of sockjs-tornado, a Python server side counterpart of SockJS-client browser library utilizing the Tornado framework, are susceptible to a Cross Site Scripting (XSS) vulnerability. This issue arises from the HTMLFILE_HEAD template's incorporation of unsanitized user data, with an incomplete mitigation previously attempted.",
            "cve": "PVE-2024-99862",
            "id": "pyup.io-65558",
            "more_info_path": "/vulnerabilities/PVE-2024-99862/65558",
            "specs": [
                ">=0,<1.0.7"
            ],
            "v": ">=0,<1.0.7"
        }
    ],
    "sofia-image-pipeline": [
        {
            "advisory": "Sofia-image-pipeline 1.3.0 updates its dependency 'pillow' to include a security fix.",
            "cve": "CVE-2023-44271",
            "id": "pyup.io-71412",
            "more_info_path": "/vulnerabilities/CVE-2023-44271/71412",
            "specs": [
                "<1.3.0"
            ],
            "v": "<1.3.0"
        }
    ],
    "softlayer-zeep": [
        {
            "advisory": "Softlayer-zeep 0.4.0 adds defusedxml module to prevent XML injection vulnerabilities.",
            "cve": "PVE-2022-48320",
            "id": "pyup.io-48320",
            "more_info_path": "/vulnerabilities/PVE-2022-48320/48320",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        }
    ],
    "solace-agent-mesh": [
        {
            "advisory": "Affected versions of the solace-agent-mesh package are vulnerable to regular expression denial of service (ReDoS) due to an inefficient template-block parsing regex. The TEMPLATE_BLOCK_REGEX used by resolve_template_blocks_in_string() in src/solace_agent_mesh/common/utils/templates/template_resolver.py relies on a dot-all, backtracking-heavy match across template content, allowing pathological inputs to trigger excessive backtracking.",
            "cve": "PVE-2026-84404",
            "id": "pyup.io-84404",
            "more_info_path": "/vulnerabilities/PVE-2026-84404/84404",
            "specs": [
                "<1.13.2"
            ],
            "v": "<1.13.2"
        }
    ],
    "solana": [
        {
            "advisory": "Solana 0.25.0 updates its dependency 'httpx' requirement to '^0.23' to include a security fix.",
            "cve": "CVE-2021-41945",
            "id": "pyup.io-49576",
            "more_info_path": "/vulnerabilities/CVE-2021-41945/49576",
            "specs": [
                "<0.25.0"
            ],
            "v": "<0.25.0"
        }
    ],
    "solara": [
        {
            "advisory": "A Local File Inclusion (LFI) vulnerability affects widgetti/solara. This vulnerability arises from the application's failure to properly validate URI fragments for directory traversal sequences when serving static files. An attacker can exploit this flaw by manipulating the fragment part of the URI to read arbitrary files on the local file system.",
            "cve": "CVE-2024-39903",
            "id": "pyup.io-72181",
            "more_info_path": "/vulnerabilities/CVE-2024-39903/72181",
            "specs": [
                "<1.35.1"
            ],
            "v": "<1.35.1"
        }
    ],
    "sonnixgres": [
        {
            "advisory": "Affected versions of the sonnixgres package are vulnerable to SQL Injection due to inadequate sanitization of SQL identifiers in utils.sanitize_sql_identifier and the lack of validation for the view_query parameter in core.create_view.",
            "cve": "PVE-2025-81338",
            "id": "pyup.io-81338",
            "more_info_path": "/vulnerabilities/PVE-2025-81338/81338",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "sopel": [
        {
            "advisory": "A security issue involving an improperly named channel logs was fixed in Sopel 4.4.0.",
            "cve": "PVE-2021-26139",
            "id": "pyup.io-26139",
            "more_info_path": "/vulnerabilities/PVE-2021-26139/26139",
            "specs": [
                "<4.4.0"
            ],
            "v": "<4.4.0"
        },
        {
            "advisory": "Sopel 6.3.0 uses the `requests` package for stability and security.",
            "cve": "PVE-2021-27413",
            "id": "pyup.io-27413",
            "more_info_path": "/vulnerabilities/PVE-2021-27413/27413",
            "specs": [
                "<6.3.0"
            ],
            "v": "<6.3.0"
        },
        {
            "advisory": "Sopel version 6.6.6 addresses a potential denial-of-service vulnerability caused by repeated long output in the `.py` and `.calc` commands. This issue has been mitigated by implementing a limit on the maximum flood penalty, ensuring the application remains stable and secure against such attacks.",
            "cve": "PVE-2024-71324",
            "id": "pyup.io-71324",
            "more_info_path": "/vulnerabilities/PVE-2024-71324/71324",
            "specs": [
                "<6.6.6"
            ],
            "v": "<6.6.6"
        }
    ],
    "sopel-modules-weather": [
        {
            "advisory": "Sopel-modules-weather 1.2.4 includes a security fix: If a user is actively blackholing the location or weather APIs, or those APIs become otherwise unavailable, it is possible for the API keys to get leaked to the active IRC channel.\r\nhttps://github.com/sopel-irc/sopel-weather/security/advisories/GHSA-63rq-p8fp-524q",
            "cve": "PVE-2023-55190",
            "id": "pyup.io-55190",
            "more_info_path": "/vulnerabilities/PVE-2023-55190/55190",
            "specs": [
                ">=0,<1.2.4"
            ],
            "v": ">=0,<1.2.4"
        }
    ],
    "sopel-plugins-channelmgnt": [
        {
            "advisory": "Sopel-plugins-channelmgnt v1.0.3 includes a fix for CVE-2020-15251: In the Channelmgnt plugin for Sopel before version 1.0.3, malicious users are able to op/voice and take over a channel. This is an ACL bypass vulnerability.\r\nhttps://github.com/MirahezeBots/sopel-channelmgnt/security/advisories/GHSA-j257-jfvv-h3x5\r\nhttps://github.com/MirahezeBots/sopel-channelmgnt/pull/3",
            "cve": "CVE-2020-15251",
            "id": "pyup.io-38876",
            "more_info_path": "/vulnerabilities/CVE-2020-15251/38876",
            "specs": [
                "<1.0.3"
            ],
            "v": "<1.0.3"
        },
        {
            "advisory": "Sopel-plugins-channelmgnt includes a fix for CVE-2021-21431: In versions prior to 2.0.1, on some IRC servers, restrictions around the removal of the bot using the kick/kickban command could be bypassed when kicking multiple users at once. It is also believed that it may have been possible to remove users from other channels. Freenode is not affected. As a workaround, do not use this plugin on networks where TARGMAX > 1.",
            "cve": "CVE-2021-21431",
            "id": "pyup.io-42306",
            "more_info_path": "/vulnerabilities/CVE-2021-21431/42306",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        }
    ],
    "sosreport": [
        {
            "advisory": "It was found that the ovirt-log-collector/sosreport collects the RHV admin password unfiltered. Fixed in: sos-4.2-20.el8_6, ovirt-log-collector-4.4.7-2.el8ev",
            "cve": "CVE-2022-2806",
            "id": "pyup.io-62629",
            "more_info_path": "/vulnerabilities/CVE-2022-2806/62629",
            "specs": [
                "<4.2-20.el8_6"
            ],
            "v": "<4.2-20.el8_6"
        },
        {
            "advisory": "sosreport 3.2 uses weak permissions for generated sosreport archives, which allows local users with access to /var/tmp/ to obtain sensitive information by reading the contents of the archive.",
            "cve": "CVE-2015-3171",
            "id": "pyup.io-42239",
            "more_info_path": "/vulnerabilities/CVE-2015-3171/42239",
            "specs": [
                "==3.2"
            ],
            "v": "==3.2"
        },
        {
            "advisory": "Sosreport version 3.3 includes a fix for CVE-2015-7529: Sosreport in SoS 3.x allows local users to obtain sensitive information from sosreport files or gain privileges via a symlink attack on an archive file in a temporary directory, as demonstrated by sosreport-$hostname-$date.tar in /tmp/sosreport-$hostname-$date.\r\nhttps://github.com/sosreport/sos/issues/696",
            "cve": "CVE-2015-7529",
            "id": "pyup.io-42211",
            "more_info_path": "/vulnerabilities/CVE-2015-7529/42211",
            "specs": [
                ">=3.0,<3.3"
            ],
            "v": ">=3.0,<3.3"
        }
    ],
    "sosse": [
        {
            "advisory": "Sosse 1.4.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/biolds/sosse/commit/5fa9d5f8fbed4ef5119f1527479b1a02faf76b40",
            "cve": "PVE-2023-60661",
            "id": "pyup.io-60661",
            "more_info_path": "/vulnerabilities/PVE-2023-60661/60661",
            "specs": [
                "<1.4.0"
            ],
            "v": "<1.4.0"
        }
    ],
    "spacepy-x": [
        {
            "advisory": "HTTPS has been re-enabled in spacepy-x 1.0.1 for secure API goodness.",
            "cve": "PVE-2021-37388",
            "id": "pyup.io-37388",
            "more_info_path": "/vulnerabilities/PVE-2021-37388/37388",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        }
    ],
    "spacy-llm": [
        {
            "advisory": "A Server-Side Template Injection (SSTI) vulnerability in Spacy-LLM affected versions allows attackers to execute arbitrary code by injecting a crafted payload into the template field.",
            "cve": "CVE-2025-25362",
            "id": "pyup.io-76319",
            "more_info_path": "/vulnerabilities/CVE-2025-25362/76319",
            "specs": [
                "<0.7.3"
            ],
            "v": "<0.7.3"
        }
    ],
    "spam": [
        {
            "advisory": "The spam project on PyPI was taken over via user account compromise via a phishing attack and new malicious releases made (2.0.2 and 4.0.2) which contained code which some environment variables and downloaded and ran malware at install time.",
            "cve": "PVE-2023-55208",
            "id": "pyup.io-55208",
            "more_info_path": "/vulnerabilities/PVE-2023-55208/55208",
            "specs": [
                "==2.0.2",
                "==4.0.2"
            ],
            "v": "==2.0.2,==4.0.2"
        }
    ],
    "spark-nlp": [
        {
            "advisory": "Spark-nlp 3.4.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/JohnSnowLabs/spark-nlp/pull/6575",
            "cve": "PVE-2023-59634",
            "id": "pyup.io-59634",
            "more_info_path": "/vulnerabilities/PVE-2023-59634/59634",
            "specs": [
                "<3.4.0"
            ],
            "v": "<3.4.0"
        },
        {
            "advisory": "Spark-nlp 4.2.4 updates its dependency 'tensorflow' to v2.7.4 to fix several vulnerabilities affecting confidentiality, integrity and availability.\r\nhttps://github.com/JohnSnowLabs/spark-nlp/commit/8aa3a952d43b335ccf9aef40b5830c2b5ab74899",
            "cve": "PVE-2023-58966",
            "id": "pyup.io-58966",
            "more_info_path": "/vulnerabilities/PVE-2023-58966/58966",
            "specs": [
                "<4.2.4"
            ],
            "v": "<4.2.4"
        },
        {
            "advisory": "Spark-nlp 4.2.5 updates its dependency 'sbt' to v1.8.0 to include several security fixes.\r\nhttps://github.com/advisories/GHSA-wv7w-rj2x-556x\r\nhttps://github.com/JohnSnowLabs/spark-nlp/commit/d137a7a68b50c6b5a82c7fb18ca7c00a52d8037a",
            "cve": "CVE-2022-37866",
            "id": "pyup.io-58979",
            "more_info_path": "/vulnerabilities/CVE-2022-37866/58979",
            "specs": [
                "<4.2.5"
            ],
            "v": "<4.2.5"
        }
    ],
    "spark-on-k8s": [
        {
            "advisory": "Spark-on-k8s updates `apache-airflow` to address the security vulnerability CVE-2024-39877.",
            "cve": "CVE-2024-39877",
            "id": "pyup.io-72360",
            "more_info_path": "/vulnerabilities/CVE-2024-39877/72360",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Spark-on-k8s updates `zipp` to address security vulnerability CVE-2024-5569.",
            "cve": "CVE-2024-5569",
            "id": "pyup.io-72357",
            "more_info_path": "/vulnerabilities/CVE-2024-5569/72357",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Spark-on-k8s updates `apache-airflow` to address security vulnerability CVE-2024-39863.",
            "cve": "CVE-2024-39863",
            "id": "pyup.io-72359",
            "more_info_path": "/vulnerabilities/CVE-2024-39863/72359",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Spark-on-k8s updates setuptools to address security concerns related to CVE-2024-6345.",
            "cve": "CVE-2024-6345",
            "id": "pyup.io-72353",
            "more_info_path": "/vulnerabilities/CVE-2024-6345/72353",
            "specs": [
                "<0.10.0"
            ],
            "v": "<0.10.0"
        },
        {
            "advisory": "Spark-on-k8s version 0.2.0 updates its dependencies on `FastAPI` to version ^0.109.1. This upgrade addresses security concerns detailed in CVE-2024-24762.",
            "cve": "CVE-2024-24762",
            "id": "pyup.io-65493",
            "more_info_path": "/vulnerabilities/CVE-2024-24762/65493",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        },
        {
            "advisory": "Version 0.2.0 of Spark-on-k8s updates its `aiohttp` dependency to require version 3.9.2 or newer. This change aims to protect against the potential security risks outlined in CVE-2024-23829.",
            "cve": "CVE-2024-23829",
            "id": "pyup.io-65465",
            "more_info_path": "/vulnerabilities/CVE-2024-23829/65465",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        },
        {
            "advisory": "Version 0.2.0 of Spark-on-k8s updates its `aiohttp` dependency to require version 3.9.2 or newer. This change aims to protect against the potential security risks outlined in CVE-2024-23334.",
            "cve": "CVE-2024-23334",
            "id": "pyup.io-65492",
            "more_info_path": "/vulnerabilities/CVE-2024-23334/65492",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        },
        {
            "advisory": "Spark-on-k8s version 0.2.1 updates its cryptography dependency to 42.0.4 from 42.0.2, addressing the security vulnerability CVE-2024-26130.\r\nhttps://github.com/hussein-awala/spark-on-k8s/pull/2/commits/346c64cfb775d0ca9970239bc3114d4bc555aa47",
            "cve": "CVE-2024-26130",
            "id": "pyup.io-65646",
            "more_info_path": "/vulnerabilities/CVE-2024-26130/65646",
            "specs": [
                "<0.2.1"
            ],
            "v": "<0.2.1"
        },
        {
            "advisory": "Spark-on-k8s version 0.2.3 updates its flask-appbuilder dependency to version 4.3.11 from 4.3.10, addressing the security vulnerability detailed in CVE-2024-25128.\r\nhttps://github.com/hussein-awala/spark-on-k8s/pull/9/commits/5dbcae8049bc2cdc721db6e2c1c845c40b1e83f5",
            "cve": "CVE-2024-25128",
            "id": "pyup.io-65715",
            "more_info_path": "/vulnerabilities/CVE-2024-25128/65715",
            "specs": [
                "<0.2.3"
            ],
            "v": "<0.2.3"
        },
        {
            "advisory": "Spark-on-k8s version 0.4.0 updates its dependency on Airflow to version 2.8.3 as a proactive measure to address the security issue identified in CVE-2024-28746.\r\nhttps://github.com/hussein-awala/spark-on-k8s/pull/23/commits/6d2675636f768bdeec21bcabc402a9ffd13ea75a",
            "cve": "CVE-2024-28746",
            "id": "pyup.io-66923",
            "more_info_path": "/vulnerabilities/CVE-2024-28746/66923",
            "specs": [
                "<0.4.0"
            ],
            "v": "<0.4.0"
        },
        {
            "advisory": "Spark-on-k8s version 0.5.0 has updated its idna dependency from version 3.6 to 3.7 to address the security vulnerability detailed in CVE-2024-3651.",
            "cve": "CVE-2024-3651",
            "id": "pyup.io-70493",
            "more_info_path": "/vulnerabilities/CVE-2024-3651/70493",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        },
        {
            "advisory": "Spark-on-k8s version 0.5.0 includes a security update to address CVE-2024-29735 by upgrading the Apache Airflow dependency to a more secure version.",
            "cve": "CVE-2024-29735",
            "id": "pyup.io-70484",
            "more_info_path": "/vulnerabilities/CVE-2024-29735/70484",
            "specs": [
                "<0.5.0"
            ],
            "v": "<0.5.0"
        },
        {
            "advisory": "Spark-on-k8s version 0.5.1 updates its Apache Airflow dependency to mitigate risks associated with CVE-2024-31869.",
            "cve": "CVE-2024-31869",
            "id": "pyup.io-70739",
            "more_info_path": "/vulnerabilities/CVE-2024-31869/70739",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Spark-on-k8s version 0.5.1 upgrades its Gunicorn dependency to address security concerns related to CVE-2024-1135.",
            "cve": "CVE-2024-1135",
            "id": "pyup.io-70740",
            "more_info_path": "/vulnerabilities/CVE-2024-1135/70740",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Spark-on-k8s version 0.5.1 updates its aiohttp dependency to address the security vulnerability listed in CVE-2024-27306.",
            "cve": "CVE-2024-27306",
            "id": "pyup.io-70618",
            "more_info_path": "/vulnerabilities/CVE-2024-27306/70618",
            "specs": [
                "<0.5.1"
            ],
            "v": "<0.5.1"
        },
        {
            "advisory": "Affected versions of Spark-on-k8s are vulnerable to sensitive information disclosure. Exception details are returned to the the API users.",
            "cve": "PVE-2024-70850",
            "id": "pyup.io-70850",
            "more_info_path": "/vulnerabilities/PVE-2024-70850/70850",
            "specs": [
                "<0.7.0"
            ],
            "v": "<0.7.0"
        },
        {
            "advisory": "Spark-on-k8s version 0.7.1 upgrades Jinja2 from 3.1.3 to 3.1.4 to address the security issue identified in CVE-2024-34064.",
            "cve": "CVE-2024-34064",
            "id": "pyup.io-70903",
            "more_info_path": "/vulnerabilities/CVE-2024-34064/70903",
            "specs": [
                "<0.7.1"
            ],
            "v": "<0.7.1"
        },
        {
            "advisory": "Spark-on-k8s 0.8.0 updates its urllib3 dependency from version 2.2.0 to 2.2.2 to address a security vulnerability identified as CVE-2024-37891.",
            "cve": "CVE-2024-37891",
            "id": "pyup.io-72057",
            "more_info_path": "/vulnerabilities/CVE-2024-37891/72057",
            "specs": [
                "<0.8.0"
            ],
            "v": "<0.8.0"
        }
    ],
    "sparkfish-python-pptx": [
        {
            "advisory": "Sparkfish-python-pptx version 0.6.12 updates its dependencies to avoid using a vulnerable version of Pillow. The Pillow library version is updated from 2.6.1 to >=3.3.2 to address the security issue identified in CVE-2016-9189.",
            "cve": "CVE-2016-9189",
            "id": "pyup.io-71102",
            "more_info_path": "/vulnerabilities/CVE-2016-9189/71102",
            "specs": [
                "<0.6.12"
            ],
            "v": "<0.6.12"
        },
        {
            "advisory": "Sparkfish-python-pptx version 0.6.12 updates its dependencies to avoid using a vulnerable version of Pillow. The Pillow library version is updated from 2.6.1 to >=3.3.2 to address the security issue identified in CVE-2016-9190.",
            "cve": "CVE-2016-9190",
            "id": "pyup.io-71094",
            "more_info_path": "/vulnerabilities/CVE-2016-9190/71094",
            "specs": [
                "<0.6.12"
            ],
            "v": "<0.6.12"
        },
        {
            "advisory": "Sparkfish-python-pptx version 0.6.23 updates its support for Pillow to version 10+ to address security vulnerabilities, including CVE-2023-44271.",
            "cve": "CVE-2023-44271",
            "id": "pyup.io-71093",
            "more_info_path": "/vulnerabilities/CVE-2023-44271/71093",
            "specs": [
                "<0.6.23"
            ],
            "v": "<0.6.23"
        }
    ],
    "sparkpipelineframework": [
        {
            "advisory": "Sparkpipelineframework 1.0.26 removed any webcrawling features and dependency on Scrapy to fix a transitive vulnerability.",
            "cve": "CVE-2017-14158",
            "id": "pyup.io-50662",
            "more_info_path": "/vulnerabilities/CVE-2017-14158/50662",
            "specs": [
                "<1.0.26"
            ],
            "v": "<1.0.26"
        }
    ],
    "sparselandtools": [
        {
            "advisory": "sparselandtools 1.0.1 requires newer versions of third party packages for security reasons in some cases",
            "cve": "PVE-2021-37929",
            "id": "pyup.io-37929",
            "more_info_path": "/vulnerabilities/PVE-2021-37929/37929",
            "specs": [
                "<1.0.1"
            ],
            "v": "<1.0.1"
        }
    ],
    "sparsify": [
        {
            "advisory": "Sparsify 0.1.1 updates its NPM dependency 'axios' to 0.21.1 to include a security fix.",
            "cve": "CVE-2020-28168",
            "id": "pyup.io-40321",
            "more_info_path": "/vulnerabilities/CVE-2020-28168/40321",
            "specs": [
                "<0.1.1"
            ],
            "v": "<0.1.1"
        },
        {
            "advisory": "Sparsify 0.12.1 updates its NPM dependency 'axios' to v0.21.2 to include a security fix.",
            "cve": "CVE-2021-3749",
            "id": "pyup.io-49715",
            "more_info_path": "/vulnerabilities/CVE-2021-3749/49715",
            "specs": [
                "<0.12.1"
            ],
            "v": "<0.12.1"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'tmpl' to v1.0.5 to include a security fix.",
            "cve": "CVE-2021-3777",
            "id": "pyup.io-50803",
            "more_info_path": "/vulnerabilities/CVE-2021-3777/50803",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'url-parse' to v1.5.10 to include security fixes.",
            "cve": "CVE-2022-0639",
            "id": "pyup.io-50804",
            "more_info_path": "/vulnerabilities/CVE-2022-0639/50804",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'url-parse' to v1.5.10 to include security fixes.",
            "cve": "CVE-2022-0686",
            "id": "pyup.io-50805",
            "more_info_path": "/vulnerabilities/CVE-2022-0686/50805",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'url-parse' to v1.5.10 to include security fixes.",
            "cve": "CVE-2021-3664",
            "id": "pyup.io-50808",
            "more_info_path": "/vulnerabilities/CVE-2021-3664/50808",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'url-parse' to v1.5.10 to include security fixes.",
            "cve": "CVE-2022-0512",
            "id": "pyup.io-50807",
            "more_info_path": "/vulnerabilities/CVE-2022-0512/50807",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'url-parse' to v1.5.10 to include security fixes.",
            "cve": "CVE-2022-0691",
            "id": "pyup.io-50806",
            "more_info_path": "/vulnerabilities/CVE-2022-0691/50806",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'lodash' to v4.17.21 to include security fixes.",
            "cve": "CVE-2021-23337",
            "id": "pyup.io-50798",
            "more_info_path": "/vulnerabilities/CVE-2021-23337/50798",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'path-parse' to v1.0.7 to include a security fix.",
            "cve": "CVE-2021-23343",
            "id": "pyup.io-50802",
            "more_info_path": "/vulnerabilities/CVE-2021-23343/50802",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'follow-redirects' to v1.14.9 to include security fixes.",
            "cve": "CVE-2022-0536",
            "id": "pyup.io-50796",
            "more_info_path": "/vulnerabilities/CVE-2022-0536/50796",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'follow-redirects' to v1.14.9 to include security fixes.",
            "cve": "CVE-2022-0155",
            "id": "pyup.io-50797",
            "more_info_path": "/vulnerabilities/CVE-2022-0155/50797",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'moment' to v2.29.2 to include a security fix.",
            "cve": "CVE-2022-24785",
            "id": "pyup.io-50801",
            "more_info_path": "/vulnerabilities/CVE-2022-24785/50801",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'ws' to v5.2.3 to include a security fix.",
            "cve": "CVE-2021-32640",
            "id": "pyup.io-50810",
            "more_info_path": "/vulnerabilities/CVE-2021-32640/50810",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'url-parse' to v1.5.10 to include security fixes.",
            "cve": "CVE-2021-27515",
            "id": "pyup.io-50809",
            "more_info_path": "/vulnerabilities/CVE-2021-27515/50809",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        },
        {
            "advisory": "Sparsify 1.0.0 updates its NPM dependency 'lodash' to v4.17.21 to include security fixes.",
            "cve": "CVE-2020-28500",
            "id": "pyup.io-50799",
            "more_info_path": "/vulnerabilities/CVE-2020-28500/50799",
            "specs": [
                "<1.0.0"
            ],
            "v": "<1.0.0"
        }
    ],
    "spartan2": [
        {
            "advisory": "Spartan2 0.1.1 adds a security check in FlowScope to prevent data overflow.\r\nhttps://github.com/BGT-M/spartan2/pull/20",
            "cve": "PVE-2021-43025",
            "id": "pyup.io-43025",
            "more_info_path": "/vulnerabilities/PVE-2021-43025/43025",
            "specs": [
                "<0.1.1"
            ],
            "v": "<0.1.1"
        }
    ],
    "spdk": [
        {
            "advisory": "Affected versions of the spdk package are vulnerable to Buffer Overflow due to missing bounds checks when writing NVMe-oF reservation registrant data into a fixed-size array. In lib/nvmf/subsystem.c, the nvmf_ns_update_reservation_info() routine iterates over ns->registrants and previously populated info.registrants without enforcing SPDK_NVMF_MAX_NUM_REGISTRANTS (16) in the PTPL (Persist Through Power Loss) update path, permitting writes past the array boundary.",
            "cve": "CVE-2025-57275",
            "id": "pyup.io-80048",
            "more_info_path": "/vulnerabilities/CVE-2025-57275/80048",
            "specs": [
                "<25.9"
            ],
            "v": "<25.9"
        }
    ],
    "speach": [
        {
            "advisory": "Speach 0.1a13 uses 'defusedxml' automatically instead of Python's default parser to avoid XML injection.\r\nhttps://github.com/neocl/speach/commit/b992031fa2c0acc7924cd2442d9f77da1cfdf4a3",
            "cve": "CVE-2013-1665",
            "id": "pyup.io-44552",
            "more_info_path": "/vulnerabilities/CVE-2013-1665/44552",
            "specs": [
                "<0.1a13"
            ],
            "v": "<0.1a13"
        },
        {
            "advisory": "Speach 0.1a13 uses 'defusedxml' automatically instead of Python's default parser to avoid XML injection.\r\nhttps://github.com/neocl/speach/commit/b992031fa2c0acc7924cd2442d9f77da1cfdf4a3",
            "cve": "CVE-2013-1664",
            "id": "pyup.io-54880",
            "more_info_path": "/vulnerabilities/CVE-2013-1664/54880",
            "specs": [
                "<0.1a13"
            ],
            "v": "<0.1a13"
        }
    ],
    "speakeasy-emulator": [
        {
            "advisory": "A use-after-free vulnerability was identified in the Unicorn Engine v1.0.3, which is employed in speakeasy-emulator versions 1.5.15 and lower. This vulnerability is triggered through the hook function.",
            "cve": "CVE-2022-29692",
            "id": "pyup.io-62633",
            "more_info_path": "/vulnerabilities/CVE-2022-29692/62633",
            "specs": [
                "<1.5.15"
            ],
            "v": "<1.5.15"
        }
    ],
    "spec-classes": [
        {
            "advisory": "Affected versions of the spec_classes package are vulnerable to race conditions (CWE-362). This vulnerability allows multiple threads to concurrently modify the __new__ method, potentially leading to inconsistent class states and unintended behavior. The vulnerability exists in the __new__ method manipulation without proper synchronization. This issue has been resolved by introducing a reentrant lock (RLock) to ensure thread-safe modifications.",
            "cve": "PVE-2024-74605",
            "id": "pyup.io-74605",
            "more_info_path": "/vulnerabilities/PVE-2024-74605/74605",
            "specs": [
                "<1.5.2"
            ],
            "v": "<1.5.2"
        }
    ],
    "specmatic": [
        {
            "advisory": "Specmatic 0.24.0 upgrades its dependency Werkzeug to 2.3.8 to resolve vulnerability issues.\r\nhttps://github.com/znsio/specmatic-python-extensions/commit/c2233710e6195d9392258f68ad5d4cb13436c7a6",
            "cve": "PVE-2023-62019",
            "id": "pyup.io-63208",
            "more_info_path": "/vulnerabilities/PVE-2023-62019/63208",
            "specs": [
                "<0.24.0"
            ],
            "v": "<0.24.0"
        }
    ],
    "spectrafit": [
        {
            "advisory": "Spectrafit 0.11.0 updates python in Dockerfile from '3.8-slim' to '3.9-slim' to include security fixes.",
            "cve": "CVE-2022-34903",
            "id": "pyup.io-51354",
            "more_info_path": "/vulnerabilities/CVE-2022-34903/51354",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        },
        {
            "advisory": "Spectrafit 0.11.0 updates python in Dockerfile from '3.8-slim' to '3.9-slim' to include security fixes.",
            "cve": "CVE-2022-2068",
            "id": "pyup.io-51388",
            "more_info_path": "/vulnerabilities/CVE-2022-2068/51388",
            "specs": [
                "<0.11.0"
            ],
            "v": "<0.11.0"
        }
    ],
    "spf-validator": [
        {
            "advisory": "Spf-validator 1.2.2 updates its dependency 'dnspython' to include a security fix.",
            "cve": "CVE-2023-29483",
            "id": "pyup.io-72377",
            "more_info_path": "/vulnerabilities/CVE-2023-29483/72377",
            "specs": [
                "<1.2.2"
            ],
            "v": "<1.2.2"
        }
    ],
    "sphinx": [
        {
            "advisory": "Sphinx 3.0.4 updates jQuery version from 3.4.1 to 3.5.1 for security reasons.",
            "cve": "CVE-2020-11022",
            "id": "pyup.io-38330",
            "more_info_path": "/vulnerabilities/CVE-2020-11022/38330",
            "specs": [
                "<3.0.4"
            ],
            "v": "<3.0.4"
        },
        {
            "advisory": "Sphinx 3.0.4 updates jQuery version from 3.4.1 to 3.5.1 for security reasons.",
            "cve": "CVE-2020-11023",
            "id": "pyup.io-45775",
            "more_info_path": "/vulnerabilities/CVE-2020-11023/45775",
            "specs": [
                "<3.0.4"
            ],
            "v": "<3.0.4"
        },
        {
            "advisory": "Sphinx 3.3.0 includes a fix for a ReDoS vulnerability in docstring.\r\nhttps://github.com/sphinx-doc/sphinx/issues/8172\r\nhttps://github.com/sphinx-doc/sphinx/commit/f00e75278c5999f40b214d8934357fbf0e705417",
            "cve": "PVE-2023-59910",
            "id": "pyup.io-59910",
            "more_info_path": "/vulnerabilities/PVE-2023-59910/59910",
            "specs": [
                "<3.3.0"
            ],
            "v": "<3.3.0"
        },
        {
            "advisory": "Sphinx 3.3.0 includes a fix for a ReDoS vulnerability in inventory.\r\nhttps://github.com/sphinx-doc/sphinx/issues/8175\r\nhttps://github.com/sphinx-doc/sphinx/commit/f7b872e673f9b359a61fd287a7338a28077840d2",
            "cve": "PVE-2023-59925",
            "id": "pyup.io-59925",
            "more_info_path": "/vulnerabilities/PVE-2023-59925/59925",
            "specs": [
                "<3.3.0"
            ],
            "v": "<3.3.0"
        }
    ],
    "sphinx-bulma": [
        {
            "advisory": "Sphinx-bulma 0.1.0 updates all NPM dev dependencies to versions without security issues.",
            "cve": "PVE-2021-42377",
            "id": "pyup.io-42377",
            "more_info_path": "/vulnerabilities/PVE-2021-42377/42377",
            "specs": [
                "<0.1.0"
            ],
            "v": "<0.1.0"
        }
    ],
    "sphinx-paragraph-extractor": [
        {
            "advisory": "Sphinx-paragraph-extractor 1.0.4 updates its dependency 'requests' to v2.21.0 to include a security fix.",
            "cve": "CVE-2018-18074",
            "id": "pyup.io-54910",
            "more_info_path": "/vulnerabilities/CVE-2018-18074/54910",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        },
        {
            "advisory": "Sphinx-paragraph-extractor 1.0.4 updates its dependency 'jinja2' to v2.10.1 to include a security fix.",
            "cve": "CVE-2019-10906",
            "id": "pyup.io-37082",
            "more_info_path": "/vulnerabilities/CVE-2019-10906/37082",
            "specs": [
                "<1.0.4"
            ],
            "v": "<1.0.4"
        }
    ],
    "sphinx-typo3-theme": [
        {
            "advisory": "Sphinx-typo3-theme version 4.3.0 updates its NPM dependency 'websocket-extensions' to v0.1.4 to include security fixes.",
            "cve": "CVE-2020-7663",
            "id": "pyup.io-49129",
            "more_info_path": "/vulnerabilities/CVE-2020-7663/49129",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        },
        {
            "advisory": "Sphinx-typo3-theme version 4.3.0 updates its NPM dependency 'websocket-extensions' to v0.1.4 to include security fixes.",
            "cve": "CVE-2020-7662",
            "id": "pyup.io-41997",
            "more_info_path": "/vulnerabilities/CVE-2020-7662/41997",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        }
    ],
    "sphinx-wagtail-theme": [
        {
            "advisory": "Sphinx-wagtail-theme 4.3.0 updates its NPM dependency 'websocket-extensions' to v0.1.4 to include security fixes.",
            "cve": "CVE-2020-7662",
            "id": "pyup.io-40027",
            "more_info_path": "/vulnerabilities/CVE-2020-7662/40027",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        },
        {
            "advisory": "Sphinx-wagtail-theme 4.3.0 updates its NPM dependency 'lodash' to v4.17.19 to include a security fix.",
            "cve": "CVE-2020-8203",
            "id": "pyup.io-45785",
            "more_info_path": "/vulnerabilities/CVE-2020-8203/45785",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        },
        {
            "advisory": "Sphinx-wagtail-theme 4.3.0 updates its NPM dependency 'websocket-extensions' to v0.1.4 to include security fixes.",
            "cve": "CVE-2020-7663",
            "id": "pyup.io-45784",
            "more_info_path": "/vulnerabilities/CVE-2020-7663/45784",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        },
        {
            "advisory": "Sphinx-wagtail-theme 4.3.0 updates its NPM dependency 'http-proxy' to v1.18.1 to include a fix for a DoS vulnerability.",
            "cve": "PVE-2022-45786",
            "id": "pyup.io-45786",
            "more_info_path": "/vulnerabilities/PVE-2022-45786/45786",
            "specs": [
                "<4.3.0"
            ],
            "v": "<4.3.0"
        }
    ],
    "sphractal": [
        {
            "advisory": "Sphractal version 0.18.4 updates its certifi dependency to version 2023.7.22 from the previous 2023.5.7, in response to addressing the security concern CVE-2023-37920.\r\nhttps://github.com/Jon-Ting/sphractal/commit/216b0d301c71c9af5bfc716064e46eae090f7775",
            "cve": "CVE-2023-37920",
            "id": "pyup.io-65446",
            "more_info_path": "/vulnerabilities/CVE-2023-37920/65446",
            "specs": [
                "<0.18.4"
            ],
            "v": "<0.18.4"
        }
    ],
    "spid-cie-oidc": [
        {
            "advisory": "Spid-cie-oidc 0.7.1 adds mixups attacks prevention for the CIE profile.\r\nhttps://github.com/italia/spid-cie-oidc-django/commit/c9c0167a19dbfb0ccc912878137bd6ba6c2b1827",
            "cve": "PVE-2022-49332",
            "id": "pyup.io-49332",
            "more_info_path": "/vulnerabilities/PVE-2022-49332/49332",
            "specs": [
                "<0.7.1"
            ],
            "v": "<0.7.1"
        },
        {
            "advisory": "Spid-cie-oidc 0.8.14 includes a fix for an open redirect vulnerability.\r\nhttps://github.com/italia/spid-cie-oidc-django/pull/257",
            "cve": "PVE-2023-53826",
            "id": "pyup.io-53826",
            "more_info_path": "/vulnerabilities/PVE-2023-53826/53826",
            "specs": [
                "<0.8.14"
            ],
            "v": "<0.8.14"
        }
    ],
    "spiffe": [
        {
            "advisory": "Affected versions of the spire package are vulnerable to Improper JWT Validation due to the missing enforcement of the expiration claim requirement. The WorkloadAPI.ValidateJWTSVID endpoint in spire-agent fails to verify that the exp (expiration) claim is present in JWT-SVIDs, violating the SPIFFE specification, which mandates that validators must reject tokens without this claim.",
            "cve": "PVE-2026-84644",
            "id": "pyup.io-84644",
            "more_info_path": "/vulnerabilities/PVE-2026-84644/84644",
            "specs": [
                "<1.12.3"
            ],
            "v": "<1.12.3"
        }
    ],
    "spiffworkflow": [
        {
            "advisory": "Spiffworkflow 1.1.7 drops 'pickle' in the JSON serializer to avoid potential code execution vulnerabilities.\r\nhttps://github.com/sartography/SpiffWorkflow/pull/174",
            "cve": "PVE-2023-58815",
            "id": "pyup.io-58815",
            "more_info_path": "/vulnerabilities/PVE-2023-58815/58815",
            "specs": [
                "<1.1.7"
            ],
            "v": "<1.1.7"
        }
    ],
    "spinetoolbox": [
        {
            "advisory": "Spinetoolbox 0.6.0 updates its dependency 'urllib3' to v1.26.5 to include a security fix.",
            "cve": "CVE-2021-33503",
            "id": "pyup.io-41270",
            "more_info_path": "/vulnerabilities/CVE-2021-33503/41270",
            "specs": [
                "<0.6.0"
            ],
            "v": "<0.6.0"
        }
    ],
    "spintest": [
        {
            "advisory": "spintest 0.2.0 renders the UUID Token invisible in the log to avoid security violation, when spintest is used during the CI/CD tools",
            "cve": "PVE-2021-37859",
            "id": "pyup.io-37859",
            "more_info_path": "/vulnerabilities/PVE-2021-37859/37859",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "splash": [
        {
            "advisory": "Splash before 2.0.1 is vulnerable to a XSS attack in HTTP UI.\r\nhttps://github.com/scrapinghub/splash/commit/9bdb9d1b5b07eab10674852088016e97b63b9c43",
            "cve": "PVE-2021-26140",
            "id": "pyup.io-26140",
            "more_info_path": "/vulnerabilities/PVE-2021-26140/26140",
            "specs": [
                "<2.0.1"
            ],
            "v": "<2.0.1"
        },
        {
            "advisory": "In splash before 2.3.2, xvfb binds to ports in the range 6000-6200 on all available interfaces.\r\nhttps://github.com/scrapinghub/splash/pull/570",
            "cve": "PVE-2021-33045",
            "id": "pyup.io-33045",
            "more_info_path": "/vulnerabilities/PVE-2021-33045/33045",
            "specs": [
                "<2.3.2"
            ],
            "v": "<2.3.2"
        },
        {
            "advisory": "A vulnerability has been identified in Splash, a javascript rendering service using an HTTP API, where attackers can exploit Server-Side Request Forgery (SSRF) through its API endpoints like execute and run. This flaw allows attackers to construct requests that compel the Splash server to make unauthorized requests to targeted servers without needing to know the Splash server's address, leveraging the service\u2019s treatment of URLs with the localhost domain. Attackers can exploit this vulnerability by using pages visited by Splash-based scrapers containing crafted inputs.",
            "cve": "PVE-2024-99860",
            "id": "pyup.io-65560",
            "more_info_path": "/vulnerabilities/PVE-2024-99860/65560",
            "specs": [
                ">=0"
            ],
            "v": ">=0"
        }
    ],
    "splitio-client": [
        {
            "advisory": "Splitio-client 9.1.2 updates its dependency 'pyyaml' minimum requirement to v5.4 to include security fixes.",
            "cve": "CVE-2020-1747",
            "id": "pyup.io-48015",
            "more_info_path": "/vulnerabilities/CVE-2020-1747/48015",
            "specs": [
                "<9.1.2"
            ],
            "v": "<9.1.2"
        },
        {
            "advisory": "Splitio-client 9.1.2 updates its dependency 'pyyaml' minimum requirement to v5.4 to include security fixes.",
            "cve": "CVE-2019-20477",
            "id": "pyup.io-48016",
            "more_info_path": "/vulnerabilities/CVE-2019-20477/48016",
            "specs": [
                "<9.1.2"
            ],
            "v": "<9.1.2"
        },
        {
            "advisory": "Splitio-client 9.1.2 updates its dependency 'pyyaml' minimum requirement to v5.4 to include security fixes.",
            "cve": "CVE-2020-14343",
            "id": "pyup.io-48011",
            "more_info_path": "/vulnerabilities/CVE-2020-14343/48011",
            "specs": [
                "<9.1.2"
            ],
            "v": "<9.1.2"
        }
    ],
    "splitzip": [
        {
            "advisory": "Affected versions of the splitzip package are vulnerable to path traversal (Zip Slip) due to insufficient validation of archive entry names. \r\nhttps://github.com/twwat/splitzip/commit/9255ff06d5f6bdca54703dd435c8de4b79997e03",
            "cve": "PVE-2026-85391",
            "id": "pyup.io-85391",
            "more_info_path": "/vulnerabilities/PVE-2026-85391/85391",
            "specs": [
                "<0.2.0"
            ],
            "v": "<0.2.0"
        }
    ],
    "splunk-sdk": [
        {
            "advisory": "Splunk-sdk 1.6.16 includes a fix for a ReDoS vulnerability.\r\nhttps://github.com/splunk/splunk-sdk-python/pull/312",
            "cve": "PVE-2023-59733",
            "id": "pyup.io-59733",
            "more_info_path": "/vulnerabilities/PVE-2023-59733/59733",
            "specs": [
                "<1.6.16"
            ],
            "v": "<1.6.16"
        },
        {
            "advisory": "Splunk-SDK-Python before 1.6.6 does not properly verify untrusted TLS server certificates, which could result in man-in-the-middle attacks.",
            "cve": "CVE-2019-5729",
            "id": "pyup.io-36969",
            "more_info_path": "/vulnerabilities/CVE-2019-5729/36969",
            "specs": [
                "<1.6.6"
            ],
            "v": "<1.6.6"
        }
    ],
    "spotdl": [
        {
            "advisory": "Spotdl 3.6.0 includes a security fix for the 'xnetcat' dependency.",
            "cve": "PVE-2021-40550",
            "id": "pyup.io-40550",
            "more_info_path": "/vulnerabilities/PVE-2021-40550/40550",
            "specs": [
                "<3.6.0"
            ],
            "v": "<3.6.0"
        }
    ],
    "spotify-gender-ex": [
        {
            "advisory": "Spotify-gender-ex 2.4.0 adds certificate validation of the Spotify 'APK' file to prevent malicious apps from being processed and re-signed.",
            "cve": "PVE-2021-40817",
            "id": "pyup.io-40817",
            "more_info_path": "/vulnerabilities/PVE-2021-40817/40817",
            "specs": [
                "<2.4.0"
            ],
            "v": "<2.4.0"
        },
        {
            "advisory": "Select versions of Spotify-Gender-Ex, a tool designed to remove gender asterisks from the Android version of the Spotify app, are susceptible to a security flaw due to improper certificate validation. This vulnerability could allow a malicious application to be mistakenly accepted and re-signed without verifying the legitimacy of the Spotify APK file.",
            "cve": "PVE-2024-99859",
            "id": "pyup.io-65561",
            "more_info_path": "/vulnerabilities/PVE-2024-99859/65561",
            "specs": [
                ">=0,<2.4.0"
            ],
            "v": ">=0,<2.4.0"
        }
    ],
    "spotipy": [
        {
            "advisory": "Spotipy is a lightweight Python library for the Spotify Web API. The `CacheHandler` class creates a cache file to store the auth token. Prior to version 2.25.1, the file created has `rw-r--r--` (644) permissions by default, when it could be locked down to `rw-------` (600) permissions. This leads to overly broad exposure of the spotify auth token. If this token can be read by an attacker (another user on the machine, or a process running as another user), it can be used to perform administrative actions on the Spotify account, depending on the scope granted to the token. Version 2.25.1 tightens the cache file permissions.",
            "cve": "CVE-2025-27154",
            "id": "pyup.io-76327",
            "more_info_path": "/vulnerabilities/CVE-2025-27154/76327",
            "specs": [
                "<2.25.1"
            ],
            "v": "<2.25.1"
        },
        {
            "advisory": "Affected versions of the `spotipy` package are vulnerable to Cross-site Scripting (XSS) due to improper sanitisation of the error parameter in the OAuth callback handler. The `RequestHandler.do_GET` method in `oauth2.py` directly embeds the unsanitised error URL parameter into the HTML response without applying HTML entity encoding, allowing injected script tags to execute as part of the rendered page content. An attacker can exploit this by crafting a malicious callback URL containing JavaScript payloads in the error parameter and convincing a user to visit it during the OAuth authentication window, enabling execution of arbitrary JavaScript within the localhost origin to access local web services, extract OAuth tokens from browser storage, or perform unauthorised actions on other localhost endpoints.",
            "cve": "PVE-2025-81960",
            "id": "pyup.io-81960",
            "more_info_path": "/vulnerabilities/PVE-2025-81960/81960",
            "specs": [
                "<2.25.2"
            ],
            "v": "<2.25.2"
        },
        {
            "advisory": "Affected versions of the spotipy package are vulnerable to Cross-Site Scripting (XSS) due to unsanitized reflection of the OAuth error parameter into the HTML response produced by the local callback server. The RequestHandler.do_GET method in spotipy/oauth2.py constructs a status string from self.server.error and interpolates it directly into the 

Authentication status: {status}

HTML without applying any HTML escaping or output encoding, allowing attacker-controlled content from the error query parameter to be rendered as executable script.", "cve": "CVE-2025-66040", "id": "pyup.io-82194", "more_info_path": "/vulnerabilities/CVE-2025-66040/82194", "specs": [ "<2.25.2" ], "v": "<2.25.2" }, { "advisory": "Spotipy 2.22.1 includes a fix for CVE-2023-23608: In versions prior to 2.22.1, if a malicious URI is passed to the library, the library can be tricked into performing an operation on a different API endpoint than intended. The code Spotipy uses to parse URIs and URLs allows an attacker to insert arbitrary characters into the path that is used for API requests. Because it is possible to include \"..\", an attacker can redirect for example a track lookup via spotifyApi.track() to an arbitrary API endpoint like playlists, but this is possible for other endpoints as well. The impact of this vulnerability depends heavily on what operations a client application performs when it handles a URI from a user and how it uses the responses it receives from the API.\r\nhttps://github.com/spotipy-dev/spotipy/security/advisories/GHSA-q764-g6fm-555v", "cve": "CVE-2023-23608", "id": "pyup.io-52930", "more_info_path": "/vulnerabilities/CVE-2023-23608/52930", "specs": [ "<=2.22.0" ], "v": "<=2.22.0" } ], "spud": [ { "advisory": "spud before 0.8 doesn't check permissions. Anybody could edit photos.", "cve": "PVE-2021-26141", "id": "pyup.io-26141", "more_info_path": "/vulnerabilities/PVE-2021-26141/26141", "specs": [ "<0.8" ], "v": "<0.8" }, { "advisory": "A vulnerability has been identified in versions of Spud, a Sortable Photo album Using a Django based database, which allows for an Access Restriction Bypass. This issue could enable unauthorized access to restricted features or data. Users are encouraged to review their configurations and follow any mitigation guidance provided.", "cve": "PVE-2024-99858", "id": "pyup.io-65562", "more_info_path": "/vulnerabilities/PVE-2024-99858/65562", "specs": [ ">=0,<0.8" ], "v": ">=0,<0.8" } ], "spyder-terminal": [ { "advisory": "Spyder-terminal 0.3.1 resolves several vulnerabilities. See: .", "cve": "PVE-2021-39132", "id": "pyup.io-39132", "more_info_path": "/vulnerabilities/PVE-2021-39132/39132", "specs": [ "<0.3.1" ], "v": "<0.3.1" } ], "spyne": [ { "advisory": "Spyne 2.14.0 includes a fix for a ReDoS vulnerability.\r\nhttps://github.com/arskom/spyne/commit/12374b4cca64b5ff3aad8aebbeecbc801dcfe8c5", "cve": "PVE-2022-44769", "id": "pyup.io-44769", "more_info_path": "/vulnerabilities/PVE-2022-44769/44769", "specs": [ "<2.14.0" ], "v": "<2.14.0" } ], "spyse-python": [ { "advisory": "Spyse-python 2.0.0 includes fixes for email and vulnerabilities scrolling.", "cve": "PVE-2021-41062", "id": "pyup.io-41062", "more_info_path": "/vulnerabilities/PVE-2021-41062/41062", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "sqla-yaml-fixtures": [ { "advisory": "Sqla_yaml_fixtures 0.9.1 is affected by CVE-2019-3575: It allows local users to execute arbitrary python code via the fixture_text argument in sqla_yaml_fixtures.load.\r\nhttps://github.com/schettino72/sqla_yaml_fixtures/issues/20", "cve": "CVE-2019-3575", "id": "pyup.io-36768", "more_info_path": "/vulnerabilities/CVE-2019-3575/36768", "specs": [ "==0.9.1" ], "v": "==0.9.1" } ], "sqlachemy": [ { "advisory": "Sqlachemy is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.", "cve": "PVE-2022-51758", "id": "pyup.io-51758", "more_info_path": "/vulnerabilities/PVE-2022-51758/51758", "specs": [ ">0" ], "v": ">0" } ], "sqlagg": [ { "advisory": "Affected versions of the sql-agg are potentially vulnerable to SQL injection. The vulnerability arises from unsanitized user input in the ORDER BY clause, potentially allowing attackers to inject and execute arbitrary SQL commands.", "cve": "PVE-2025-76471", "id": "pyup.io-76471", "more_info_path": "/vulnerabilities/PVE-2025-76471/76471", "specs": [ "<0.13.0" ], "v": "<0.13.0" } ], "sqlalcemy": [ { "advisory": "Sqlalcemy is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.", "cve": "PVE-2022-51759", "id": "pyup.io-51759", "more_info_path": "/vulnerabilities/PVE-2022-51759/51759", "specs": [ ">0" ], "v": ">0" } ], "sqlalchemy": [ { "advisory": "Sqlalchemy 0.7.0 includes a fix for CVE-2012-0805: Multiple SQL injection vulnerabilities in SQLAlchemy before 0.7.0b4, as used in Keystone, allow remote attackers to execute arbitrary SQL commands via the (1) limit or (2) offset keyword to the select function, or unspecified vectors to the (3) select.limit or (4) select.offset function.\r\nhttps://docs.sqlalchemy.org/en/20/changelog/changelog_07.html#change-0.7.0", "cve": "CVE-2012-0805", "id": "pyup.io-52946", "more_info_path": "/vulnerabilities/CVE-2012-0805/52946", "specs": [ "<0.7.0" ], "v": "<0.7.0" }, { "advisory": "Sqlalchemy 1.1.14 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/sqlalchemy/sqlalchemy/commit/a3965ea5ff198114c477d18cc8e3c34012c16a0b", "cve": "PVE-2023-60424", "id": "pyup.io-60424", "more_info_path": "/vulnerabilities/PVE-2023-60424/60424", "specs": [ "<1.1.14" ], "v": "<1.1.14" }, { "advisory": "SQLAlchemy affected versions has SQL Injection when the group_by parameter can be controlled.", "cve": "CVE-2019-7548", "id": "pyup.io-71592", "more_info_path": "/vulnerabilities/CVE-2019-7548/71592", "specs": [ "<1.3.0" ], "v": "<1.3.0" }, { "advisory": "Sqlalchemy 2.0.0b1 avoids leaking cleartext passwords to the open for careless uses of str(engine.URL()) in logs and prints.\r\nhttps://github.com/sqlalchemy/sqlalchemy/pull/8563", "cve": "PVE-2022-51668", "id": "pyup.io-51668", "more_info_path": "/vulnerabilities/PVE-2022-51668/51668", "specs": [ "<2.0.0b1" ], "v": "<2.0.0b1" }, { "advisory": "SQLAlchemy through 1.2.17 and 1.3.x through 1.3.0b2 allows SQL Injection via the order_by parameter.\r\nhttps://github.com/sqlalchemy/sqlalchemy/issues/4481", "cve": "CVE-2019-7164", "id": "pyup.io-38497", "more_info_path": "/vulnerabilities/CVE-2019-7164/38497", "specs": [ "<=1.2.17", ">=1.3.0b1,<=1.3.0b2" ], "v": "<=1.2.17,>=1.3.0b1,<=1.3.0b2" } ], "sqlalchemy-cockroachdb": [ { "advisory": "Sqlalchemy-cockroachdb 1.3.0 updates 'urllib3' to v1.25.3 to include security fixes.", "cve": "CVE-2019-11236", "id": "pyup.io-54884", "more_info_path": "/vulnerabilities/CVE-2019-11236/54884", "specs": [ "<1.3.0" ], "v": "<1.3.0" }, { "advisory": "Sqlalchemy-cockroachdb 1.3.0 updates 'urllib3' to v1.25.3 to include security fixes.", "cve": "CVE-2019-11324", "id": "pyup.io-38405", "more_info_path": "/vulnerabilities/CVE-2019-11324/38405", "specs": [ "<1.3.0" ], "v": "<1.3.0" } ], "sqlalchemy-utils": [ { "advisory": "Sqlalchemy-utils from version 0.27.0 'EncryptedType' uses by default AES with CBC mode. The IV that it uses is not random though.\r\nhttps://github.com/kvesteri/sqlalchemy-utils/issues/166\r\nhttps://github.com/kvesteri/sqlalchemy-utils/pull/499", "cve": "PVE-2021-42194", "id": "pyup.io-42194", "more_info_path": "/vulnerabilities/PVE-2021-42194/42194", "specs": [ ">=0.27.0" ], "v": ">=0.27.0" } ], "sqlathanor": [ { "advisory": "Sqlathanor 0.5.0 updates its dependency 'urllib3' to v1.24.2 to include a security fix.", "cve": "CVE-2019-11324", "id": "pyup.io-37403", "more_info_path": "/vulnerabilities/CVE-2019-11324/37403", "specs": [ "<0.5.0" ], "v": "<0.5.0" } ], "sqlatypemodel": [ { "advisory": "Affected versions of the sqlatypemodel package are vulnerable to denial of service (DoS) due to unbounded recursion when processing deeply nested JSON-like structures.", "cve": "PVE-2025-82921", "id": "pyup.io-82921", "more_info_path": "/vulnerabilities/PVE-2025-82921/82921", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Affected versions of the sqlatypemodel package are vulnerable to denial of service (DoS) due to unbounded recursion when processing deeply nested JSON-like structures.", "cve": "PVE-2025-83169", "id": "pyup.io-83169", "more_info_path": "/vulnerabilities/PVE-2025-83169/83169", "specs": [ "<0.8.0" ], "v": "<0.8.0" } ], "sqlean.py": [ { "advisory": "Affected versions of the SQLite statement virtual table module in Sqlean are vulnerable to Integer Overflow (CWE-190) leading to a Heap-based Buffer Overflow (CWE-122). An integer overflow in statement_vtab_best_index can occur when calculating the size for memory allocation without proper checks. This overflow may result in allocating insufficient memory for parameter mappings, causing a buffer overflow when the code writes beyond the allocated buffer. An attacker could exploit this by providing many constraints in a query, potentially leading to arbitrary code execution or denial of service. Users should update to the version where this issue is resolved by implementing proper integer overflow checks and safer memory handling practices.\r\n#NOTE: Sqlean extends SQLite with extra features, and sqlean.py makes these features accessible in Python. Vulnerabilities in Sqlean impact sqlean.py because it directly wraps Sqlean for Python use.", "cve": "PVE-2023-61367", "id": "pyup.io-61367", "more_info_path": "/vulnerabilities/PVE-2023-61367/61367", "specs": [ "<0.21.8" ], "v": "<0.21.8" } ], "sqlfluff": [ { "advisory": "Sqlfluff 0.3.2 moves to `SandboxedEnvironment` rather than `Environment` for jinja templating for security.", "cve": "PVE-2021-38270", "id": "pyup.io-38270", "more_info_path": "/vulnerabilities/PVE-2021-38270/38270", "specs": [ "<0.3.2" ], "v": "<0.3.2" }, { "advisory": "SQLFluff 2.1.2 includes a fix for an Arbitrary Code Execution vulnerability. In environments where untrusted users have access to the config files (e.g. .sqlfluff), there is a potential security vulnerability where those users could use the library_path config value to allow arbitrary Python code to be executed via macros.\r\nhttps://github.com/sqlfluff/sqlfluff/pull/4925\r\nhttps://github.com/sqlfluff/sqlfluff/security/advisories/GHSA-jqhc-m2j3-fjrx", "cve": "CVE-2023-36830", "id": "pyup.io-59276", "more_info_path": "/vulnerabilities/CVE-2023-36830/59276", "specs": [ "<2.1.2" ], "v": "<2.1.2" } ], "sqlite-rx": [ { "advisory": "Sqlite-rx 1.2.0 updates its dependency 'tornado' to v6.3.3 to include a security fix.", "cve": "PVE-2023-99925", "id": "pyup.io-62239", "more_info_path": "/vulnerabilities/PVE-2023-99925/62239", "specs": [ "<1.2.0" ], "v": "<1.2.0" } ], "sqlite-vec": [ { "advisory": "Affected versions of sqlite-vec are vulnerable to heap-buffer overflow (CWE-125). This can result in memory corruption and application crashes when parsing specially crafted Numpy files. The vulnerability is triggered by an out-of-bounds read during token scanning in the npy_token_next function, caused by insufficient boundary checks before calling strncmp. Attackers can exploit this issue by supplying malicious Numpy files.", "cve": "CVE-2024-46488", "id": "pyup.io-73494", "more_info_path": "/vulnerabilities/CVE-2024-46488/73494", "specs": [ "<0.1.3" ], "v": "<0.1.3" } ], "sqlite-web": [ { "advisory": "This affects all versions of the package sqlite-web. The SQL dashboard area allows sensitive actions to be performed without validating that the request originated from the application. This could enable an attacker to trick a user into performing these actions unknowingly through a Cross Site Request Forgery (CSRF) attack. See CVE-2021-23404.\r\nhttps://github.com/coleifer/sqlite-web/blob/2e7c85da3d37f80074ed3ae39b5851069b4f301c/sqlite_web/__main__.py%23L1", "cve": "CVE-2021-23404", "id": "pyup.io-41281", "more_info_path": "/vulnerabilities/CVE-2021-23404/41281", "specs": [ ">=0" ], "v": ">=0" } ], "sqlitedict": [ { "advisory": "SQLitedict, in all versions, contains an insecure deserialization vulnerability that could allow arbitrary code execution when loading untrusted database files. \r\n#NOTE: The maintainers have acknowledged the issue but opted not to patch it, instead recommending a warning to users about the risks of loading untrusted files.", "cve": "CVE-2024-35515", "id": "pyup.io-73282", "more_info_path": "/vulnerabilities/CVE-2024-35515/73282", "specs": [ "<=2.1.0" ], "v": "<=2.1.0" } ], "sqllineage": [ { "advisory": "Sqllineage 1.5.3 updates its dependency 'sqlparse' to v0.5.0 to include a security fix.", "cve": "CVE-2024-4340", "id": "pyup.io-70828", "more_info_path": "/vulnerabilities/CVE-2024-4340/70828", "specs": [ "<1.5.3" ], "v": "<1.5.3" } ], "sqlmesh": [ { "advisory": "Sqlmesh 0.1.0 includes a fix for a Race Condition vulnerability that happens during SQLMesh schema creation in the Airflow plugin.\r\nhttps://github.com/TobikoData/sqlmesh/pull/332", "cve": "PVE-2023-59534", "id": "pyup.io-59534", "more_info_path": "/vulnerabilities/PVE-2023-59534/59534", "specs": [ "<0.1.0" ], "v": "<0.1.0" }, { "advisory": "Sqlmesh bump pdoc to 14.5.1 to address CVE-2024-38526.", "cve": "CVE-2024-38526", "id": "pyup.io-75214", "more_info_path": "/vulnerabilities/CVE-2024-38526/75214", "specs": [ "<0.152.0" ], "v": "<0.152.0" } ], "sqlo": [ { "advisory": "Affected versions of this package are vulnerable to SQL Injection, leading to Mass Data Modification. Multiple query builder functions fail to validate table and column identifiers, enforce type constraints on raw expressions, handle empty IN clauses safely, and require WHERE clauses for destructive operations. This leads to arbitrary SQL execution and unintended data modification.", "cve": "PVE-2025-82091", "id": "pyup.io-82091", "more_info_path": "/vulnerabilities/PVE-2025-82091/82091", "specs": [ "<0.1.0" ], "v": "<0.1.0" } ], "sqlparse": [ { "advisory": "Sqlparse 0.5.0 addresses a potential denial of service (DoS) vulnerability related to recursion errors in deeply nested SQL statements. To mitigate this issue, the update replaces recursion errors with a general SQLParseError, improving the resilience and stability of the parsing process.", "cve": "CVE-2024-4340", "id": "pyup.io-67887", "more_info_path": "/vulnerabilities/CVE-2024-4340/67887", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Affected versions of this package are vulnerable to Denial of Service (DoS) attacks due to Algorithmic Complexity. The SQL parser fails to enforce limits when processing deeply nested tuples and large token sequences, leading to excessive resource consumption through crafted SQL statements with extreme nesting depth or token counts.\r\n\r\n**Note:** This issue is due to an incomplete fix for CVE-2024-4340.", "cve": "PVE-2025-82038", "id": "pyup.io-82038", "more_info_path": "/vulnerabilities/PVE-2025-82038/82038", "specs": [ "<0.5.4" ], "v": "<0.5.4" }, { "advisory": "Sqlparse 0.4.4 includes a fix for CVE-2023-30608: Parser contains a regular expression that is vulnerable to ReDOS (Regular Expression Denial of Service).\r\nhttps://github.com/andialbrecht/sqlparse/security/advisories/GHSA-rrm6-wvj7-cwh2", "cve": "CVE-2023-30608", "id": "pyup.io-55054", "more_info_path": "/vulnerabilities/CVE-2023-30608/55054", "specs": [ ">=0.1.15,<0.4.4" ], "v": ">=0.1.15,<0.4.4" }, { "advisory": "Sqlparse version 0.4.2 includes a fix for CVE-2021-32839: In sqlparse versions 0.4.0 and 0.4.1 there is a Regular Expression Denial of Service vulnerability. The regular expression may cause exponential backtracking on strings containing many repetitions of \"\\r\\n\" in SQL comments. Only the formatting feature that removes comments from SQL statements is affected by this regular expression. As a workaround, avoid using the sqlformat.format function with keyword strip_comments=True or the --strip-comments command line flag when using the sqlformat command line tool.\r\nhttps://github.com/andialbrecht/sqlparse/security/advisories/GHSA-p5w8-wqhj-9hhf\r\nhttps://github.com/andialbrecht/sqlparse/commit/8238a9e450ed1524e40cb3a8b0b3c00606903aeb", "cve": "CVE-2021-32839", "id": "pyup.io-41288", "more_info_path": "/vulnerabilities/CVE-2021-32839/41288", "specs": [ ">=0.4.0,<0.4.2" ], "v": ">=0.4.0,<0.4.2" } ], "srmd-ncnn-vulkan-python": [ { "advisory": "Srmd-ncnn-vulkan-python 1.0.1 throughout 1.0.2 ship with a version of C library 'libwebp' which is affected by a high risk vulnerability.\r\nhttps://inspector.pypi.io/project/srmd-ncnn-vulkan-python/1.0.2/packages/1d/25/a626ad22548228cc72ad12f8b00bca017998783b6c3bbd4f62a253815707/srmd-ncnn-vulkan-python-1.0.2.tar.gz/srmd-ncnn-vulkan-python-1.0.2/srmd_ncnn_vulkan_python/srmd-ncnn-vulkan/src/libwebp/ChangeLog", "cve": "CVE-2023-4863", "id": "pyup.io-62305", "more_info_path": "/vulnerabilities/CVE-2023-4863/62305", "specs": [ ">1.0.0,<=1.0.2" ], "v": ">1.0.0,<=1.0.2" } ], "srp": [ { "advisory": "A vulnerability, which was classified as problematic, has been found in cocagne pysrp up to 1.0.16. This issue affects the function calculate_x of the file srp/_ctsrp.py. The manipulation leads to information exposure through discrepancy. Upgrading to version 1.0.17 can address this issue. The name of the patch is dba52642f5e95d3da7af1780561213ee6053195f. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-216875. Alias: PYSEC-2022-43014", "cve": "CVE-2021-4286", "id": "pyup.io-62687", "more_info_path": "/vulnerabilities/CVE-2021-4286/62687", "specs": [ ">=0,<1.0.17" ], "v": ">=0,<1.0.17" } ], "srsly": [ { "advisory": "Srsly 2.4.3 includes a fix for a CVE-2021-45958.\r\nhttps://github.com/advisories/GHSA-fh56-85cw-5pq6\r\nhttps://github.com/explosion/srsly/commit/6479497df8b7f4f92bf05399a0bc4548dc2eaacc", "cve": "CVE-2021-45958", "id": "pyup.io-59595", "more_info_path": "/vulnerabilities/CVE-2021-45958/59595", "specs": [ "<2.4.3" ], "v": "<2.4.3" }, { "advisory": "Srsly 2.4.4 includes a fix for a CVE-2022-31116.\r\nhttps://github.com/explosion/srsly/commit/99106075199922cb5a70d4c273d4f75e941907a2\r\nhttps://github.com/explosion/srsly/commit/febb6f2d8edab5327847e4d7eeb1c23dbde510c7", "cve": "CVE-2022-31116", "id": "pyup.io-59594", "more_info_path": "/vulnerabilities/CVE-2022-31116/59594", "specs": [ "<2.4.4" ], "v": "<2.4.4" } ], "ssh-audit": [ { "advisory": "Ssh-audit 2.2.0 re-classifies the very common `ssh-rsa` host key type as weak, due to practical SHA-1 attacks - see https://eprint.iacr.org/2020/014.pdf", "cve": "PVE-2021-38046", "id": "pyup.io-38046", "more_info_path": "/vulnerabilities/PVE-2021-38046/38046", "specs": [ "<2.2.0" ], "v": "<2.2.0" }, { "advisory": "Ssh-audit version 3.2.0 now includes an option to simulate the DHEat denial-of-service attack. This feature, accessible via the `--dheat` command, addresses vulnerabilities detailed in CVE-2002-20001.", "cve": "CVE-2002-20001", "id": "pyup.io-68096", "more_info_path": "/vulnerabilities/CVE-2002-20001/68096", "specs": [ "<3.2.0" ], "v": "<3.2.0" } ], "ssh-decorate": [ { "advisory": "Ssh-decorate was compromised. Versions 0.28 through 0.31 were backdoored to steal SSH Credentials.\r\nhttps://www.bleepingcomputer.com/news/security/backdoored-python-library-caught-stealing-ssh-credentials/", "cve": "PVE-2022-45471", "id": "pyup.io-45471", "more_info_path": "/vulnerabilities/PVE-2022-45471/45471", "specs": [ ">=0.28,<=0.31" ], "v": ">=0.28,<=0.31" } ], "ssh-mitm": [ { "advisory": "ssh-mitm before 0.3.11", "cve": "PVE-2021-39436", "id": "pyup.io-39436", "more_info_path": "/vulnerabilities/PVE-2021-39436/39436", "specs": [ "<0.3.11" ], "v": "<0.3.11" } ], "sslyze": [ { "advisory": "Sslyze 3.0.2 improves the check for HTTP security headers by adding support for HTTP redirections.", "cve": "PVE-2021-38197", "id": "pyup.io-38197", "more_info_path": "/vulnerabilities/PVE-2021-38197/38197", "specs": [ "<3.0.2" ], "v": "<3.0.2" } ], "st2client": [ { "advisory": "StackStorm before 3.4.1, in some situations, has an infinite loop that consumes all available memory and disk space. This can occur if Python 3.x is used, the locale is not utf-8, and there is an attempt to log Unicode data (from an action or rule name). See CVE-2021-28667.", "cve": "CVE-2021-28667", "id": "pyup.io-40034", "more_info_path": "/vulnerabilities/CVE-2021-28667/40034", "specs": [ "<3.4.1" ], "v": "<3.4.1" } ], "stanza": [ { "advisory": "Stanza 1.4.1 includes a fix for a catastrophic backtracking vulnerability.\r\nhttps://github.com/stanfordnlp/stanza/pull/1056", "cve": "PVE-2023-61073", "id": "pyup.io-61073", "more_info_path": "/vulnerabilities/PVE-2023-61073/61073", "specs": [ "<1.4.1" ], "v": "<1.4.1" } ], "starcluster-openstack": [ { "advisory": "Starcluster-openstack", "cve": "PVE-2021-26967", "id": "pyup.io-26967", "more_info_path": "/vulnerabilities/PVE-2021-26967/26967", "specs": [ "<0.94.7" ], "v": "<0.94.7" } ], "stargate": [ { "advisory": "stargate before 0.4 has several undisclosed security vulnerabilities.", "cve": "PVE-2021-26143", "id": "pyup.io-26143", "more_info_path": "/vulnerabilities/PVE-2021-26143/26143", "specs": [ "<0.4" ], "v": "<0.4" } ], "starkbank-ecdsa": [ { "advisory": "The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.", "cve": "CVE-2021-43572", "id": "pyup.io-42545", "more_info_path": "/vulnerabilities/CVE-2021-43572/42545", "specs": [ "<2.0.1" ], "v": "<2.0.1" } ], "starknet-py": [ { "advisory": "Starknet-py 0.3.1alpha adds compiled OZ contract with patched security hole (reentrancy).\r\nhttps://github.com/OpenZeppelin/cairo-contracts/issues/344\r\nhttps://github.com/software-mansion/starknet.py/pull/195", "cve": "PVE-2022-51030", "id": "pyup.io-51030", "more_info_path": "/vulnerabilities/PVE-2022-51030/51030", "specs": [ "<0.3.1alpha" ], "v": "<0.3.1alpha" } ], "starlette": [ { "advisory": "Starlette 0.13.5 includes a fix for a Path Traversal vulnerability.\r\n#NOTE: This vulnerability affects only users of Windows.\r\nhttps://github.com/encode/starlette/issues/981", "cve": "PVE-2023-59444", "id": "pyup.io-59444", "more_info_path": "/vulnerabilities/PVE-2023-59444/59444", "specs": [ "<0.13.5" ], "v": "<0.13.5" }, { "advisory": "Starlette 0.25.0 includes a fix for CVE-2023-30798: The MultipartParser usage in Encode's Starlette python framework before versions 0.25.0 allows an unauthenticated and remote attacker to specify any number of form fields or files which can cause excessive memory usage resulting in denial of service of the HTTP service.", "cve": "CVE-2023-30798", "id": "pyup.io-53332", "more_info_path": "/vulnerabilities/CVE-2023-30798/53332", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Affected versions of the Starlette framework are vulnerable to Denial of Service (DoS) attacks due to the lack of restrictions on multipart part sizes. The vulnerability resides in the MultiPartParser class, which previously did not enforce size limits on incoming data. This issue is mitigated by introducing a max_part_size constraint and raises exceptions when limits are exceeded.", "cve": "CVE-2024-47874", "id": "pyup.io-73725", "more_info_path": "/vulnerabilities/CVE-2024-47874/73725", "specs": [ "<0.40.0" ], "v": "<0.40.0" }, { "advisory": "Affected versions of the Starlette package are vulnerable to Denial of Service (DoS) due to inefficient Range header processing behaviour in starlette.responses.FileResponse. The FileResponse._parse_range_header() routine parses multi-range requests and merges intervals using an O(n\u00b2) algorithm, so supplying many non-overlapping ranges causes quadratic CPU usage in routes that return FileResponse or are served via starlette.staticfiles.StaticFiles.", "cve": "CVE-2025-62727", "id": "pyup.io-80876", "more_info_path": "/vulnerabilities/CVE-2025-62727/80876", "specs": [ "<0.49.1" ], "v": "<0.49.1" }, { "advisory": "When using form data, `python-multipart` employs a Regular Expression to parse the HTTP `Content-Type` header. This creates a vulnerability where an attacker can send a specially crafted `Content-Type` option, causing significant CPU resource consumption and indefinitely stalling the server by locking the main event loop, rendering the server unable to process further requests. This issue particularly affects FastAPI servers parsing form data, leading to a Denial of Service (DoS) condition when the number of malicious requests exceeds the number of available server workers. However, this vulnerability does not impact the processing of JSON data through the `/submit_json` endpoint. It is specific to a defined set of versions of FastAPI and `python-multipart` when handling form data.", "cve": "PVE-2024-68094", "id": "pyup.io-68094", "more_info_path": "/vulnerabilities/PVE-2024-68094/68094", "specs": [ "<=0.36.1" ], "v": "<=0.36.1" }, { "advisory": "Starlette 0.27.0 fixes a vulnerability: Path traversal vulnerability in StaticFiles.\r\nhttps://github.com/encode/starlette/security/advisories/GHSA-v5gw-mw7f-84px", "cve": "CVE-2023-29159", "id": "pyup.io-58713", "more_info_path": "/vulnerabilities/CVE-2023-29159/58713", "specs": [ ">=0.13.5,<0.27.0" ], "v": ">=0.13.5,<0.27.0" }, { "advisory": "Affected versions of the `starlette` package are vulnerable to Denial of Service (DoS) due to improper handling of large file uploads in multi-part form parsing. The vulnerability exists in the `UploadFile` class, where the logic fails to adequately check if additional bytes will trigger a file rollover, leading to blocking of the main thread. An attacker can exploit this by uploading large files that exceed the default max spool size, causing the event thread to block and preventing the application from accepting new connections.", "cve": "CVE-2025-54121", "id": "pyup.io-78279", "more_info_path": "/vulnerabilities/CVE-2025-54121/78279", "specs": [ ">=0.13.5,<0.47.2" ], "v": ">=0.13.5,<0.47.2" } ], "starlette-bridge": [ { "advisory": "Starlette-bridge 0.2.0 updates its dependency 'Starlette' to versions '>=0.27.0' to include a security fix.", "cve": "PVE-2023-58713", "id": "pyup.io-58714", "more_info_path": "/vulnerabilities/PVE-2023-58713/58714", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "starlight-protocol": [ { "advisory": "Affected versions of this package are vulnerable to CSS Selector Injection. CSS selector construction fails to escape special characters using escapeCssString, leading to CSS injection attacks where malicious input containing selector metacharacters can break out of selectors to inject arbitrary CSS rules, potentially enabling UI redress attacks, clickjacking, or information disclosure.", "cve": "PVE-2026-84312", "id": "pyup.io-84312", "more_info_path": "/vulnerabilities/PVE-2026-84312/84312", "specs": [ "<3.0.4" ], "v": "<3.0.4" }, { "advisory": "Affected versions of this package are vulnerable to Code Injection. The application uses `eval()` to execute dynamically constructed code, leading to arbitrary JavaScript execution when attacker-controlled input is processed, enabling XSS attacks, session hijacking, data theft, or complete application compromise.", "cve": "PVE-2026-84259", "id": "pyup.io-84259", "more_info_path": "/vulnerabilities/PVE-2026-84259/84259", "specs": [ "<3.0.4" ], "v": "<3.0.4" } ], "starlite": [ { "advisory": "Starlite 1.28.0 adds CSRF protection to templates.\r\nhttps://github.com/starlite-api/starlite/pull/598", "cve": "PVE-2022-51456", "id": "pyup.io-51456", "more_info_path": "/vulnerabilities/PVE-2022-51456/51456", "specs": [ "<1.28.0" ], "v": "<1.28.0" }, { "advisory": "Starlite 1.51.2 includes a fix for CVE-2023-25578: DoS vulnerability when parsing multipart request body.\r\nhttps://github.com/starlite-api/starlite/security/advisories/GHSA-p24m-863f-fm6q", "cve": "CVE-2023-25578", "id": "pyup.io-53638", "more_info_path": "/vulnerabilities/CVE-2023-25578/53638", "specs": [ "<1.51.2" ], "v": "<1.51.2" }, { "advisory": "Affected versions of the starlite package are vulnerable to Denial of Service (DoS) due to unbounded memory allocation when parsing request bodies. The Request methods for parsing JSON, msgpack, and form-data content types use `await self.body()` to read the entire request stream into memory without implementing size limits or validation checks, while the multipart parser expects the complete request body as a single byte string by design. An attacker can exploit this vulnerability by sending extremely large requests with matching content types (such as using `curl -F \"foo==1.37.0,<=1.51.14" ], "v": ">=1.37.0,<=1.51.14" } ], "starwhale": [ { "advisory": "Starwhale 0.3.1 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.", "cve": "CVE-2007-4559", "id": "pyup.io-51719", "more_info_path": "/vulnerabilities/CVE-2007-4559/51719", "specs": [ "<0.3.1" ], "v": "<0.3.1" }, { "advisory": "Starwhale 0.5.5 updates its dependency 'vite' to version '4.4.0' to include a fix for a Path Equivalence vulnerability.\r\nhttps://github.com/star-whale/starwhale/pull/2475", "cve": "CVE-2023-34092", "id": "pyup.io-59460", "more_info_path": "/vulnerabilities/CVE-2023-34092/59460", "specs": [ "<0.5.5" ], "v": "<0.5.5" } ], "stata-mcp": [ { "advisory": "Stata-mcp 1.13.0", "cve": "PVE-2025-81730", "id": "pyup.io-81730", "more_info_path": "/vulnerabilities/PVE-2025-81730/81730", "specs": [ "<1.13.0" ], "v": "<1.13.0" }, { "advisory": "Affected versions of the stata-mcp package are vulnerable to OS command injection due to executing Stata do-files without sanitizing shell-escape directives and invoking the Stata CLI via a shell on Unix-like systems. \r\nhttps://github.com/SepineTam/stata-mcp/commit/52413ce15cc9f4377fab437b7c4a2da57314e2bb", "cve": "PVE-2026-85418", "id": "pyup.io-85418", "more_info_path": "/vulnerabilities/PVE-2026-85418/85418", "specs": [ "<1.13.29" ], "v": "<1.13.29" } ], "statelint": [ { "advisory": "Statelint 1.0.0 updates its dependency 'black' to include a security fix.", "cve": "CVE-2024-21503", "id": "pyup.io-71311", "more_info_path": "/vulnerabilities/CVE-2024-21503/71311", "specs": [ "<1.0.0" ], "v": "<1.0.0" } ], "statsservice": [ { "advisory": "Statsservice 0.5.0 prevents the creation of new admin users (even by an admin).\r\nhttps://github.com/monarc-project/stats-service/commit/257c16fed890bda8974594238a743f8afda0ff5a", "cve": "PVE-2022-49624", "id": "pyup.io-49624", "more_info_path": "/vulnerabilities/PVE-2022-49624/49624", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Statsservice 0.5.0 updates its NPM dependency 'moment' to v2.29.2 to include a security fix.", "cve": "CVE-2022-24785", "id": "pyup.io-49625", "more_info_path": "/vulnerabilities/CVE-2022-24785/49625", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Statsservice 0.5.0 updates its dependency 'urllib3' to v1.26.5 to include a security fix.", "cve": "CVE-2021-33503", "id": "pyup.io-49574", "more_info_path": "/vulnerabilities/CVE-2021-33503/49574", "specs": [ "<0.5.0" ], "v": "<0.5.0" } ], "staty": [ { "advisory": "Staty 1.2.3 updates its dependency 'jinja2' to v2.10.1 to include a security fix.", "cve": "CVE-2019-10906", "id": "pyup.io-37049", "more_info_path": "/vulnerabilities/CVE-2019-10906/37049", "specs": [ "<1.2.3" ], "v": "<1.2.3" }, { "advisory": "Staty 1.2.3 updates its dependency 'pyyaml' to v5.1 to include a security fix.", "cve": "CVE-2017-18342", "id": "pyup.io-44957", "more_info_path": "/vulnerabilities/CVE-2017-18342/44957", "specs": [ "<1.2.3" ], "v": "<1.2.3" } ], "steam": [ { "advisory": "Valve Steam Client before 2019-09-12 allows placing or appending partially controlled filesystem content, as demonstrated by file modifications on Windows in the context of NT AUTHORITY\\SYSTEM. This could lead to denial of service, elevation of privilege, or unspecified other impact.", "cve": "CVE-2019-17180", "id": "pyup.io-54162", "more_info_path": "/vulnerabilities/CVE-2019-17180/54162", "specs": [ ">=0,<2019-09-12" ], "v": ">=0,<2019-09-12" } ], "stegano": [ { "advisory": "Stegano 0.8.6 updates 'requests' version due to a vulnerability found in versions 2.19 and below.", "cve": "CVE-2018-18074", "id": "pyup.io-36625", "more_info_path": "/vulnerabilities/CVE-2018-18074/36625", "specs": [ "<0.8.6" ], "v": "<0.8.6" } ], "stepcount": [ { "advisory": "Stepcount 2.1.1 updates its dependency 'torch' to include a security fix.", "cve": "CVE-2022-45907", "id": "pyup.io-53777", "more_info_path": "/vulnerabilities/CVE-2022-45907/53777", "specs": [ "<2.1.1" ], "v": "<2.1.1" } ], "stomp-py": [ { "advisory": "Stomp.py 4.1.22 reduces verbosity in logging to not include headers unless debug level is turned on. This is a potential Information Disclosure vulnerability.", "cve": "PVE-2021-37046", "id": "pyup.io-37046", "more_info_path": "/vulnerabilities/PVE-2021-37046/37046", "specs": [ "<4.1.22" ], "v": "<4.1.22" }, { "advisory": "Stomp-py version 8.1.1 updates its Dockerfile to use Debian 11, addressing the security issues highlighted in CVE-2023-29491.", "cve": "CVE-2023-29491", "id": "pyup.io-67884", "more_info_path": "/vulnerabilities/CVE-2023-29491/67884", "specs": [ "<8.1.1" ], "v": "<8.1.1" }, { "advisory": "Stomp-py version 8.1.1 updates its Dockerfile to use Debian 11, addressing the security issues highlighted in CVE-2022-29458.", "cve": "CVE-2022-29458", "id": "pyup.io-67894", "more_info_path": "/vulnerabilities/CVE-2022-29458/67894", "specs": [ "<8.1.1" ], "v": "<8.1.1" } ], "storey": [ { "advisory": "Storey 0.10.1 updates its dependency 'aiohttp' to v3.7.4 to include a security fix.", "cve": "CVE-2021-21330", "id": "pyup.io-44570", "more_info_path": "/vulnerabilities/CVE-2021-21330/44570", "specs": [ "<0.10.1" ], "v": "<0.10.1" }, { "advisory": "Storey 1.3.16 updates its dependency 'markdown-it-py' to include a security fix.", "cve": "CVE-2023-26302", "id": "pyup.io-55046", "more_info_path": "/vulnerabilities/CVE-2023-26302/55046", "specs": [ "<1.3.16" ], "v": "<1.3.16" }, { "advisory": "Storey 1.6.17 updates its doc/requirement 'jinja2' to include a security fix.\r\nhttps://github.com/mlrun/storey/pull/495", "cve": "CVE-2024-22195", "id": "pyup.io-64400", "more_info_path": "/vulnerabilities/CVE-2024-22195/64400", "specs": [ ">=1.3.16,<1.6.17" ], "v": ">=1.3.16,<1.6.17" } ], "stork": [ { "advisory": "Stork 3.0.1 includes re-compiled dependencies to fix a security issue in a pinned dependency.", "cve": "PVE-2021-38611", "id": "pyup.io-38611", "more_info_path": "/vulnerabilities/PVE-2021-38611/38611", "specs": [ "<3.0.1" ], "v": "<3.0.1" } ], "storlets": [ { "advisory": "An issue in OpenStack Storlets yoga-eom allows a remote attacker to execute arbitrary code via the gateway.py component.", "cve": "CVE-2024-28717", "id": "pyup.io-70631", "more_info_path": "/vulnerabilities/CVE-2024-28717/70631", "specs": [ "<13.0.0.0rc1" ], "v": "<13.0.0.0rc1" } ], "stormpath": [ { "advisory": "Stormpath before 2.5.0 doesn't validate JWT correctly.\r\nhttps://github.com/stormpath/stormpath-sdk-python/commit/1289135cd5bb73705297bf64cb7897c6f6e457b0", "cve": "PVE-2021-26145", "id": "pyup.io-45713", "more_info_path": "/vulnerabilities/PVE-2021-26145/45713", "specs": [ "<2.5.0" ], "v": "<2.5.0" } ], "stormpath-sdk": [ { "advisory": "Stormpath-sdk before 2.5.0 doesn't validate JWT correctly.\r\nhttps://github.com/stormpath/stormpath-sdk-python/commit/1289135cd5bb73705297bf64cb7897c6f6e457b0", "cve": "PVE-2021-26146", "id": "pyup.io-45714", "more_info_path": "/vulnerabilities/PVE-2021-26146/45714", "specs": [ "<2.5.0" ], "v": "<2.5.0" } ], "strands-agents": [ { "advisory": "Affected versions of the Strands SDK for Python package are vulnerable to Improper Input Validation due to ToolLoader registering dynamically loaded tool modules in sys.modules using unprefixed names that can collide with existing modules. In the pre-commit implementation, the load_tools_from_file_path and load_python_tools helpers inserted module objects into sys.modules under keys taken directly from the tool file\u2019s basename or the tool_name argument (for example sys.modules[module_name] and sys.modules[tool_name]), so loading a tool whose name matched a standard or internal module would overwrite that entry and change later import resolution.", "cve": "PVE-2025-81810", "id": "pyup.io-81810", "more_info_path": "/vulnerabilities/PVE-2025-81810/81810", "specs": [ "<1.18.0" ], "v": "<1.18.0" }, { "advisory": "Affected versions of the strands-agents package are vulnerable to Path Traversal due to improper input validation of the `session_id` and `agent_id` identifiers used to construct filesystem and S3 storage paths. The `FileSessionManager._get_session_path()`, `FileSessionManager._get_agent_path()`, `S3SessionManager._get_session_path()`, and `S3SessionManager._get_agent_path()` functions incorporated user-controlled identifiers into path strings without rejecting path separators, and `Agent.__init__` accepted `agent_id` without validation, permitting traversal outside the intended storage namespace.", "cve": "PVE-2025-79292", "id": "pyup.io-79292", "more_info_path": "/vulnerabilities/PVE-2025-79292/79292", "specs": [ "<1.5.0" ], "v": "<1.5.0" } ], "strawberry-django-auth": [ { "advisory": "Strawberry-django-auth 0.3.4.2 removes 'users' query due to security concerns.", "cve": "PVE-2022-51116", "id": "pyup.io-51116", "more_info_path": "/vulnerabilities/PVE-2022-51116/51116", "specs": [ "<0.3.4.2" ], "v": "<0.3.4.2" } ], "strawberry-graphql": [ { "advisory": "Strawberry-graphql 0.193.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/strawberry-graphql/strawberry/pull/2856", "cve": "PVE-2023-59592", "id": "pyup.io-59592", "more_info_path": "/vulnerabilities/PVE-2023-59592/59592", "specs": [ "<0.193.0" ], "v": "<0.193.0" }, { "advisory": "Affected versions of Strawberry GraphQL are vulnerable to CWE-434: Unrestricted Upload of File with Dangerous Type and CWE-352: Cross-Site Request Forgery (CSRF). These issues allow attackers to upload malicious files or execute unauthorized actions through CSRF attacks. Multipart uploads were enabled by default, and CSRF protection was disabled for Django views. Exploitation involves submitting harmful files or crafting requests to bypass CSRF protections. Users should upgrade to the where multipart uploads are disabled by default, and CSRF protection is enforced, mitigating both vulnerabilities.", "cve": "PVE-2024-73381", "id": "pyup.io-73381", "more_info_path": "/vulnerabilities/PVE-2024-73381/73381", "specs": [ "<0.243.0" ], "v": "<0.243.0" }, { "advisory": "Affected versions of strawberry-graphql are vulnerable to Cross-Site Request Forgery (CSRF) and insufficient security in multipart file uploads. CSRF attacks allow unauthorized actions to be performed on behalf of authenticated users due to the implicit CSRF exemption in Strawberry\u2019s Django integration. Additionally, multipart uploads were enabled by default without proper security controls, making them susceptible to malicious file uploads. These issues are resolved by requiring explicit opt-in for multipart uploads and enforcing CSRF protection.", "cve": "CVE-2024-47082", "id": "pyup.io-73495", "more_info_path": "/vulnerabilities/CVE-2024-47082/73495", "specs": [ "<0.243.0" ], "v": "<0.243.0" }, { "advisory": "Strawberry-graphql patches a security vulnerability where a Relay node resolver with multiple possible types could incorrectly identify the object type, potentially exposing unauthorized data.", "cve": "PVE-2025-74873", "id": "pyup.io-74873", "more_info_path": "/vulnerabilities/PVE-2025-74873/74873", "specs": [ "<0.257.0" ], "v": "<0.257.0" }, { "advisory": "Strawberry-graphql 0.71.0 adds a query depth limit validation rule to guard against malicious queries.", "cve": "PVE-2021-41088", "id": "pyup.io-41088", "more_info_path": "/vulnerabilities/PVE-2021-41088/41088", "specs": [ "<0.71.0" ], "v": "<0.71.0" }, { "advisory": "A type confusion vulnerability exists in Strawberry GraphQL's relay integration that affects multiple ORM integrations (Django, SQLAlchemy, Pydantic). The vulnerability occurs when multiple GraphQL types are mapped to the same underlying model while using the relay node interface.", "cve": "CVE-2025-22151", "id": "pyup.io-76363", "more_info_path": "/vulnerabilities/CVE-2025-22151/76363", "specs": [ ">=0.182.0,<0.257.0" ], "v": ">=0.182.0,<0.257.0" } ], "stream-unzip": [ { "advisory": "Stream-unzip 0.0.90 fixes its dependency version for localtunnel at 2.0.2 specifically to mitigate the security risk posed by the axios vulnerability, designated as CVE-2021-3749.\r\nhttps://github.com/uktrade/stream-unzip/pull/75/commits/1e75270050a1752ceb82ec26accc0a10e6cf4a0a", "cve": "CVE-2021-3749", "id": "pyup.io-64541", "more_info_path": "/vulnerabilities/CVE-2021-3749/64541", "specs": [ "<0.0.90" ], "v": "<0.0.90" } ], "stream-zip": [ { "advisory": "Stream-zip version 0.0.71 updates its localtunnel dependency to version 2.0.2. This change is implemented to mitigate the security risks associated with the axios vulnerability CVE-2023-45857.\r\nhttps://github.com/uktrade/stream-zip/pull/107/commits/4ac7d1037ed62f0095d7a91937a48e30bcc6acb2", "cve": "CVE-2023-45857", "id": "pyup.io-65652", "more_info_path": "/vulnerabilities/CVE-2023-45857/65652", "specs": [ "<0.0.71" ], "v": "<0.0.71" } ], "streamlink": [ { "advisory": "Streamlink 5.3.0 fixes a race condition that affected the proper closure and data flushing of substreams when being muxed using FFMPEG. The issue arose from the incorrect handling of substream buffers, which could result in missing data if the buffers weren't fully drained before the stream was closed. \r\nhttps://github.com/streamlink/streamlink/commit/546386208cf620e7dd90e400f953e0442ca3976d", "cve": "PVE-2024-64212", "id": "pyup.io-64212", "more_info_path": "/vulnerabilities/PVE-2024-64212/64212", "specs": [ "<5.3.0" ], "v": "<5.3.0" }, { "advisory": "Streamlink 5.3.0 fixes a race condition that was present in the DASH stream implementation, where queued segments were being downloaded even after the stream had been closed. This was addressed by ensuring that the downloading of segments is properly stopped when a stream is closed, preventing unnecessary network traffic and potential errors.\r\nhttps://github.com/streamlink/streamlink/commit/498efd523c10672d3c2224b71bb513e0907bbe6e", "cve": "PVE-2024-64310", "id": "pyup.io-64310", "more_info_path": "/vulnerabilities/PVE-2024-64310/64310", "specs": [ "<5.3.0" ], "v": "<5.3.0" } ], "streamlit": [ { "advisory": "The `server.address` config option in streamlit 0.57.0 binds the server to that address for added security.", "cve": "PVE-2021-38121", "id": "pyup.io-38121", "more_info_path": "/vulnerabilities/PVE-2021-38121/38121", "specs": [ "<0.57.0" ], "v": "<0.57.0" }, { "advisory": "Affected versions of Streamlit are susceptible to a vulnerability where improper output neutralization for logs occurs. This specific issue arises if the function `upload_file_request_handler.py` triggers a 400 error that includes the `session_id` value.", "cve": "PVE-2024-99857", "id": "pyup.io-65563", "more_info_path": "/vulnerabilities/PVE-2024-99857/65563", "specs": [ ">=0,<1.27.0" ], "v": ">=0,<1.27.0" }, { "advisory": "Streamlit affected versions have a cross-site scripting (XSS) vulnerability. Hosted Streamlit app(s) users were vulnerable to a reflected XSS vulnerability. An attacker could craft a malicious URL with Javascript payloads to a Streamlit app. The attacker could then trick the user into visiting the malicious URL and, if successful, the server would render the malicious javascript payload as-is, leading to XSS.", "cve": "CVE-2023-27494", "id": "pyup.io-54668", "more_info_path": "/vulnerabilities/CVE-2023-27494/54668", "specs": [ ">=0.63.0,<0.81.0" ], "v": ">=0.63.0,<0.81.0" }, { "advisory": "In Streamlit affected versions, users hosting Streamlit app(s) that use custom components are vulnerable to a directory traversal attack that could leak data from their web server file-system such as: server logs, world-readable files, and potentially other sensitive information. An attacker can craft a malicious URL with file paths and the streamlit server would process that URL and return the contents of that file. This issue has been resolved in version 1.11.1. Users are advised to upgrade. There are no known workarounds for this issue.", "cve": "CVE-2022-35918", "id": "pyup.io-50437", "more_info_path": "/vulnerabilities/CVE-2022-35918/50437", "specs": [ ">=0.63.0,<=1.30.0" ], "v": ">=0.63.0,<=1.30.0" }, { "advisory": "Affected versions of the `Streamlit` package are vulnerable to Path Traversal due to improper handling of file paths in the static file sharing feature. The static file sharing feature fails to sanitize user input, allowing crafted file paths to access arbitrary files on the server. An attacker can exploit this vulnerability on Windows systems to leak sensitive information, such as the password hash of the Windows user running `Streamlit`, by accessing unauthorized files.", "cve": "CVE-2024-42474", "id": "pyup.io-78762", "more_info_path": "/vulnerabilities/CVE-2024-42474/78762", "specs": [ ">=1.17.1,<1.37.0" ], "v": ">=1.17.1,<1.37.0" } ], "streamlit-shortcuts": [ { "advisory": "Affected versions of the streamlit-shortcuts package are vulnerable to Cross-Site Scripting (XSS). The `add_shortcuts()` function fails to properly escape special characters when injecting JavaScript code into the DOM, leading to potential JavaScript injection attacks. The vulnerability was fixed by replacing the insufficient string replacement approach with `json.dumps()` to properly escape all special characters and prevent JavaScript injection attacks.", "cve": "PVE-2025-78613", "id": "pyup.io-78613", "more_info_path": "/vulnerabilities/PVE-2025-78613/78613", "specs": [ "<1.0.1" ], "v": "<1.0.1" } ], "streamlit-webrtc": [ { "advisory": "Streamlit-webrtc 0.44.2 updates its NPM dependency 'json5' to v1.0.2 to include a security fix.", "cve": "CVE-2022-46175", "id": "pyup.io-52737", "more_info_path": "/vulnerabilities/CVE-2022-46175/52737", "specs": [ "<0.44.2" ], "v": "<0.44.2" }, { "advisory": "Streamlit-webrtc 0.44.2 updates its dependency 'gitpython' to v3.1.30 to include a security fix.", "cve": "CVE-2022-24439", "id": "pyup.io-52694", "more_info_path": "/vulnerabilities/CVE-2022-24439/52694", "specs": [ "<0.44.2" ], "v": "<0.44.2" } ], "streampipes": [ { "advisory": "Affected versions of the Apache StreamPipes package are vulnerable to Time-of-Check Time-of-Use (TOCTOU) Race Condition due to a window between email uniqueness validation and account creation. The user self-registration module performs the email uniqueness check and account creation in separate steps without synchronization, allowing concurrent requests to bypass the check and create multiple accounts with the same email address. An attacker can exploit this by sending simultaneous registration requests using the same email, resulting in the creation of duplicate user accounts that can corrupt user management or enable inconsistent identity state.", "cve": "CVE-2024-30471", "id": "pyup.io-78745", "more_info_path": "/vulnerabilities/CVE-2024-30471/78745", "specs": [ "<0.95.0" ], "v": "<0.95.0" }, { "advisory": "Affected versions of the Apache StreamPipes package are vulnerable to Server-Side Request Forgery due to insufficient validation of custom endpoint URLs. The pipeline installation process permits users to configure arbitrary HTTP endpoints without proper validation, allowing the installation mechanism to issue HTTP GET requests to unintended destinations. An attacker can exploit this by supplying a malicious endpoint during pipeline element installation, causing StreamPipes to make requests to arbitrary internal or external systems, which may enable reconnaissance or interaction with sensitive or internal network resources.", "cve": "CVE-2024-31979", "id": "pyup.io-78750", "more_info_path": "/vulnerabilities/CVE-2024-31979/78750", "specs": [ "<0.95.0" ], "v": "<0.95.0" }, { "advisory": "Affected versions of the Apache StreamPipes package are vulnerable to Remote Code Execution due to unrestricted upload of files with dangerous types. The file upload component does not validate or restrict executable file types submitted by authenticated and authorized users, allowing arbitrary file types, including executables, to be stored and potentially invoked. An attacker who is authenticated and authorized can upload a malicious executable file, leading to the execution of arbitrary code on the host running Apache StreamPipes, impacting confidentiality, integrity, and availability.", "cve": "CVE-2024-31411", "id": "pyup.io-78746", "more_info_path": "/vulnerabilities/CVE-2024-31411/78746", "specs": [ "<0.95.0" ], "v": "<0.95.0" }, { "advisory": "Affected versions of the Apache StreamPipes package are vulnerable to Improper Access Control due to missing authorization checks in REST API endpoints. The REST interface fails to properly validate user permissions when accessing resources, only checking if the user is authenticated but not verifying if they have the appropriate privileges to access the requested resource ID.", "cve": "CVE-2024-24778", "id": "pyup.io-78834", "more_info_path": "/vulnerabilities/CVE-2024-24778/78834", "specs": [ "<0.97.0" ], "v": "<0.97.0" } ], "streamsx-kafka": [ { "advisory": "streamsx-kafka 1.5.1 - resolves security vulnerabilities in third-party libs", "cve": "PVE-2021-36807", "id": "pyup.io-36807", "more_info_path": "/vulnerabilities/PVE-2021-36807/36807", "specs": [ "<1.5.1" ], "v": "<1.5.1" } ], "streamsx-messagehub": [ { "advisory": "Streamsx.messagehub 1.5.1 removes 'guava API' usage because it is vulnerable to CVE-2018-10237.", "cve": "CVE-2018-10237", "id": "pyup.io-45715", "more_info_path": "/vulnerabilities/CVE-2018-10237/45715", "specs": [ "<1.5.1" ], "v": "<1.5.1" } ], "streamsx-objectstorage": [ { "advisory": "streamsx-objectstorage 1.7.2 resolves security vulnerabilities in third-party libs #135", "cve": "PVE-2021-36618", "id": "pyup.io-36618", "more_info_path": "/vulnerabilities/PVE-2021-36618/36618", "specs": [ "<1.7.0" ], "v": "<1.7.0" } ], "streamsync": [ { "advisory": "Streamsync 0.1.12 includes a fix for a Drive-by Attack vulnerability. A drive-by attack refers to a cyberattack in which a malicious script causes a program to download and install itself on a user's device, without explicit permission from the user.\r\nhttps://github.com/streamsync-cloud/streamsync/commit/d92da4d75e1f2be833dfea391bc2a29856cf1974", "cve": "PVE-2023-60227", "id": "pyup.io-60227", "more_info_path": "/vulnerabilities/PVE-2023-60227/60227", "specs": [ "<0.1.12" ], "v": "<0.1.12" } ], "strinfer": [ { "advisory": "Strinfer is a malicious package. It triggers the install of W4SP Stealer in your system.", "cve": "PVE-2022-51676", "id": "pyup.io-51676", "more_info_path": "/vulnerabilities/PVE-2022-51676/51676", "specs": [ ">0" ], "v": ">0" } ], "stringe": [ { "advisory": "Stringe is a malicious package. It triggers the install of W4SP Stealer in your system.", "cve": "PVE-2022-51687", "id": "pyup.io-51687", "more_info_path": "/vulnerabilities/PVE-2022-51687/51687", "specs": [ ">0" ], "v": ">0" } ], "structlog-sentry-logger": [ { "advisory": "Structlog-sentry-logger 0.18.0", "cve": "PVE-2022-51971", "id": "pyup.io-51971", "more_info_path": "/vulnerabilities/PVE-2022-51971/51971", "specs": [ "<0.18.0" ], "v": "<0.18.0" } ], "stupidb": [ { "advisory": "Stupidb 6.1.0 updates its dependency 'nixpkgs' to fix a critical vulnerability.\r\nhttps://github.com/cpcloud/stupidb/pull/172/commits/8833da5cfdd26e94ceff43e6b8ea0615a9e03f5e", "cve": "CVE-2021-44228", "id": "pyup.io-43591", "more_info_path": "/vulnerabilities/CVE-2021-44228/43591", "specs": [ "<6.1.0" ], "v": "<6.1.0" }, { "advisory": "Stupidb 7.0.4 and prior uses a version of 'nixpkgs', containing the package 'signald', which is affected by log4j related vulnerabilities.", "cve": "CVE-2021-45105", "id": "pyup.io-43593", "more_info_path": "/vulnerabilities/CVE-2021-45105/43593", "specs": [ "<=7.0.4" ], "v": "<=7.0.4" }, { "advisory": "Stupidb 7.0.4 and prior uses a version of 'nixpkgs', containing the package 'signald', which is affected by log4j related vulnerabilities.", "cve": "CVE-2021-45046", "id": "pyup.io-43592", "more_info_path": "/vulnerabilities/CVE-2021-45046/43592", "specs": [ "<=7.0.4" ], "v": "<=7.0.4" }, { "advisory": "Stupidb 7.0.4 and prior uses a version of 'nixpkgs', containing the package 'signald', which is affected by a medium severity vulnerability.", "cve": "CVE-2021-44832", "id": "pyup.io-44457", "more_info_path": "/vulnerabilities/CVE-2021-44832/44457", "specs": [ "<=7.0.4" ], "v": "<=7.0.4" } ], "style.py": [ { "advisory": "Style.py is a malicious package. It installs information-stealing and RAT (remote access trojan) Malware while using Cloudflare Tunnel to bypass firewall restrictions for remote access.\r\nhttps://www.bleepingcomputer.com/news/security/malicious-pypi-packages-create-cloudflare-tunnels-to-bypass-firewalls", "cve": "PVE-2023-52938", "id": "pyup.io-52938", "more_info_path": "/vulnerabilities/PVE-2023-52938/52938", "specs": [ ">=0" ], "v": ">=0" } ], "suap-notifica-govbr": [ { "advisory": "Suap-notifica-govbr 4.7.1 updates its dependency 'PyJWT' to v1.5.1 to include a security fix.", "cve": "CVE-2017-11424", "id": "pyup.io-44588", "more_info_path": "/vulnerabilities/CVE-2017-11424/44588", "specs": [ "<4.7.1" ], "v": "<4.7.1" } ], "subsearch": [ { "advisory": "Subsearch version 2.44.1 updates the Pillow library from version 10.2.0 to 10.3.0 due to CVE-2024-28219.", "cve": "CVE-2024-28219", "id": "pyup.io-70891", "more_info_path": "/vulnerabilities/CVE-2024-28219/70891", "specs": [ "<2.44.1" ], "v": "<2.44.1" } ], "substra": [ { "advisory": "Substra 0.0.19 fixes a vulnerability in lodash.", "cve": "PVE-2021-38835", "id": "pyup.io-38835", "more_info_path": "/vulnerabilities/PVE-2021-38835/38835", "specs": [ "<0.0.19" ], "v": "<0.0.19" } ], "substrate-interface": [ { "advisory": "Substrate-interface 1.1.5 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/polkascan/py-substrate-interface/commit/a13577e45350b1df9b451bb16f5c221f57bf9c65", "cve": "PVE-2023-60537", "id": "pyup.io-60537", "more_info_path": "/vulnerabilities/PVE-2023-60537/60537", "specs": [ "<1.1.5" ], "v": "<1.1.5" } ], "suds": [ { "advisory": "Suds 0.7.0 includes a fix for CVE-2013-2217, a 'FileCache' default cache location security issue found in the original suds project.", "cve": "CVE-2013-2217", "id": "pyup.io-45118", "more_info_path": "/vulnerabilities/CVE-2013-2217/45118", "specs": [ "<0.7.0" ], "v": "<0.7.0" } ], "suds-community": [ { "advisory": "suds-community 0.7.0 fixes `FileCache` default cache location related security issue.", "cve": "PVE-2021-40552", "id": "pyup.io-40552", "more_info_path": "/vulnerabilities/PVE-2021-40552/40552", "specs": [ "<0.7.0" ], "v": "<0.7.0" }, { "advisory": "Suds-community 0.7.0 addresses CVE-2013-2217.", "cve": "CVE-2013-2217", "id": "pyup.io-36562", "more_info_path": "/vulnerabilities/CVE-2013-2217/36562", "specs": [ ">=0.4.1,<0.7.0" ], "v": ">=0.4.1,<0.7.0" } ], "suffer": [ { "advisory": "Suffer is a malicious package, typosquatting. \"The aforementioned package could be abused to become an entry point for more sophisticated threats, enabling the attacker to execute remote code on the target machine, amass system information, plunder credit card information and passwords auto-saved in Chrome and Edge browsers, and even steal Discord authentication tokens to impersonate the victim\".\r\nhttps://thehackernews.com/2021/07/several-malicious-typosquatted-python.html", "cve": "PVE-2022-45451", "id": "pyup.io-45451", "more_info_path": "/vulnerabilities/PVE-2022-45451/45451", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "suitable-django-autocomplete": [ { "advisory": "Affected versions of suitable-django-autocomplete are vulnerable to Cross-Site Scripting (XSS) due to insufficient output encoding in the autocomplete functionality. The autocomplete components fail to properly sanitize user-controlled input before rendering it in HTML responses, leading to potential XSS attacks where malicious scripts can be executed in users' browsers through autocomplete suggestions or search results.", "cve": "PVE-2025-77902", "id": "pyup.io-77902", "more_info_path": "/vulnerabilities/PVE-2025-77902/77902", "specs": [ "<0.6.0" ], "v": "<0.6.0" } ], "supabase": [ { "advisory": "Supabase 0.7.1 updates its dependency 'httpx' to v0.23.0 to include a security fix.", "cve": "CVE-2021-41945", "id": "pyup.io-52976", "more_info_path": "/vulnerabilities/CVE-2021-41945/52976", "specs": [ "<0.7.1" ], "v": "<0.7.1" } ], "supabase-pydantic": [ { "advisory": "Supabase-pydantic updates Jinja2 to ^3.1.6 to resolve CVE-2025-27516.", "cve": "CVE-2025-27516", "id": "pyup.io-75940", "more_info_path": "/vulnerabilities/CVE-2025-27516/75940", "specs": [ "<0.17.4" ], "v": "<0.17.4" } ], "super-gradients": [ { "advisory": "Super-gradients 3.6.1 updates its ONNX dependency to version 1.16 to address a directory traversal vulnerability found in versions up to 1.15.0. This vulnerability allowed unauthorized access to files outside the intended directories due to an exploitable external_data field in tensor proto, circumventing previous fixes made for CVE-2022-25882.", "cve": "CVE-2022-25882", "id": "pyup.io-67144", "more_info_path": "/vulnerabilities/CVE-2022-25882/67144", "specs": [ "<3.6.1" ], "v": "<3.6.1" } ], "superagi": [ { "advisory": "SuperAGI v0.0.13 was discovered to use a hardcoded key for encryption operations. This vulnerability can lead to the disclosure of information and communications.", "cve": "CVE-2023-48055", "id": "pyup.io-70894", "more_info_path": "/vulnerabilities/CVE-2023-48055/70894", "specs": [ "<=0.0.13" ], "v": "<=0.0.13" } ], "superdesk-planning": [ { "advisory": "Superdesk-planning 2.0.2 includes a security patch which requires authentication for all API endpoints.", "cve": "PVE-2021-39688", "id": "pyup.io-39688", "more_info_path": "/vulnerabilities/PVE-2021-39688/39688", "specs": [ "<2.0.2" ], "v": "<2.0.2" }, { "advisory": "A vulnerability involving selected versions of a software package allows for Improper Authentication. It was identified that multiple API endpoints could be accessed without any form of authentication. The exploit maturity of this vulnerability is currently assessed as Unproven.", "cve": "PVE-2024-99856", "id": "pyup.io-65564", "more_info_path": "/vulnerabilities/PVE-2024-99856/65564", "specs": [ ">=0,<2.0.2" ], "v": ">=0,<2.0.2" } ], "superset": [ { "advisory": "Superset 0.11.0 prevents XSS on FAB list views.\r\nhttps://github.com/apache/superset/pull/1125", "cve": "PVE-2021-26147", "id": "pyup.io-26147", "more_info_path": "/vulnerabilities/PVE-2021-26147/26147", "specs": [ "<0.11.0" ], "v": "<0.11.0" }, { "advisory": "Superset 0.14.0a improves jinja2 security by using SandboxedEnvironment (#1632) and improves the security scheme (#1587).", "cve": "PVE-2021-37486", "id": "pyup.io-37486", "more_info_path": "/vulnerabilities/PVE-2021-37486/37486", "specs": [ "<0.14.0a" ], "v": "<0.14.0a" }, { "advisory": "Superset 0.19.1 prevents XSS in markup viz.\r\nhttps://github.com/apache/superset/pull/3211", "cve": "PVE-2021-37487", "id": "pyup.io-37487", "more_info_path": "/vulnerabilities/PVE-2021-37487/37487", "specs": [ "<0.19.1" ], "v": "<0.19.1" }, { "advisory": "Superset 0.23.0a updates its NPM dependency 'moment' to v2.20.1 to include a security fix.", "cve": "CVE-2017-18214", "id": "pyup.io-45806", "more_info_path": "/vulnerabilities/CVE-2017-18214/45806", "specs": [ "<0.23.0a" ], "v": "<0.23.0a" }, { "advisory": "Superset 0.23.0a updates its NPM dependency 'mathjs' to v3.20.2 to include security fixes.", "cve": "CVE-2017-1001002", "id": "pyup.io-36204", "more_info_path": "/vulnerabilities/CVE-2017-1001002/36204", "specs": [ "<0.23.0a" ], "v": "<0.23.0a" }, { "advisory": "Superset 0.23.0a adds all derived FAB UserModelView views to admin only.\r\nhttps://github.com/apache/superset/pull/4180/commits/74e33eeab9ab388a38892fd4aa2541bf65e7692a", "cve": "PVE-2021-36204", "id": "pyup.io-45804", "more_info_path": "/vulnerabilities/PVE-2021-36204/45804", "specs": [ "<0.23.0a" ], "v": "<0.23.0a" }, { "advisory": "Superset 0.23.0a adds XFO header by default to prevent clickjacking attacks.\r\nhttps://github.com/apache/superset/commit/f113d2b923543ec85983fef6674f2a9f0e2319c6", "cve": "PVE-2022-45808", "id": "pyup.io-45808", "more_info_path": "/vulnerabilities/PVE-2022-45808/45808", "specs": [ "<0.23.0a" ], "v": "<0.23.0a" }, { "advisory": "Superset 0.23.0a fixes XSS vulnerabilities via the markdown library and the 'javascript' link handler.\r\nhttps://github.com/apache/superset/commit/b6fcc22d5a2cb7a5e92599ed5795a0169385a825", "cve": "PVE-2022-45809", "id": "pyup.io-45809", "more_info_path": "/vulnerabilities/PVE-2022-45809/45809", "specs": [ "<0.23.0a" ], "v": "<0.23.0a" }, { "advisory": "Superset 0.23.0a fixes a code execution vulnerability because of using unsafe yaml.load().\r\nhttps://github.com/apache/superset/commit/7e949ee342226c5c213db46760c02a341b7099ff", "cve": "CVE-2017-18342", "id": "pyup.io-45807", "more_info_path": "/vulnerabilities/CVE-2017-18342/45807", "specs": [ "<0.23.0a" ], "v": "<0.23.0a" }, { "advisory": "Superset 0.23.0a updates its NPM dependency 'mathjs' to v3.20.2 to include security fixes.", "cve": "CVE-2017-1001003", "id": "pyup.io-45805", "more_info_path": "/vulnerabilities/CVE-2017-1001003/45805", "specs": [ "<0.23.0a" ], "v": "<0.23.0a" }, { "advisory": "Superset 0.29.0rc8a secures unsecured views and prevent regressions (#6553).", "cve": "PVE-2021-37488", "id": "pyup.io-37488", "more_info_path": "/vulnerabilities/PVE-2021-37488/37488", "specs": [ "<0.29.0rc8a" ], "v": "<0.29.0rc8a" }, { "advisory": "Superset 0.32.0rc2.dev2a includes new, deprecate merge_perm. Also, the FAB method is fixed (#7355).", "cve": "PVE-2021-26584", "id": "pyup.io-26584", "more_info_path": "/vulnerabilities/PVE-2021-26584/26584", "specs": [ "<0.32.0rc2.dev2a" ], "v": "<0.32.0rc2.dev2a" }, { "advisory": "Superset 0.33.0rc1a adds Flask-Talisman.\r\nhttps://github.com/apache/superset/pull/7443", "cve": "PVE-2021-37485", "id": "pyup.io-37485", "more_info_path": "/vulnerabilities/PVE-2021-37485/37485", "specs": [ "<0.33.0rc1a" ], "v": "<0.33.0rc1a" }, { "advisory": "An authenticated user with Gamma role authorization could have access to metadata information using non trivial methods in Apache Superset up to and including 2.0.1", "cve": "CVE-2023-27525", "id": "pyup.io-62903", "more_info_path": "/vulnerabilities/CVE-2023-27525/62903", "specs": [ "<=2.0.1" ], "v": "<=2.0.1" }, { "advisory": "A malicious actor who has been authenticated and granted specific permissions in Apache Superset may use the import dataset feature in order to conduct Server-Side Request Forgery attacks and query internal resources on behalf of the server where Superset\r\nis deployed. This vulnerability exists in Apache Superset versions up to and including 2.0.1.", "cve": "CVE-2023-25504", "id": "pyup.io-62897", "more_info_path": "/vulnerabilities/CVE-2023-25504/62897", "specs": [ "<=2.0.1" ], "v": "<=2.0.1" }, { "advisory": "Session Validation attacks in Apache Superset versions up to and including 2.0.1. Installations that have not altered the default configured SECRET_KEY according to installation instructions allow for an attacker to authenticate and access unauthorized resources. This does not affect Superset administrators who have changed the default value for SECRET_KEY config.", "cve": "CVE-2023-27524", "id": "pyup.io-62901", "more_info_path": "/vulnerabilities/CVE-2023-27524/62901", "specs": [ "<=2.0.1" ], "v": "<=2.0.1" }, { "advisory": "A non Admin authenticated user could incorrectly create resources using the import charts feature, on Apache Superset up to and including 2.1.0.", "cve": "CVE-2023-27526", "id": "pyup.io-62905", "more_info_path": "/vulnerabilities/CVE-2023-27526/62905", "specs": [ "<=2.1.0" ], "v": "<=2.1.0" }, { "advisory": "Improper data authorization check on Jinja templated queries in Apache Superset\u00a0up to and including 2.1.0 allows for an authenticated user to issue queries on database tables they may not have access to.", "cve": "CVE-2023-27523", "id": "pyup.io-62899", "more_info_path": "/vulnerabilities/CVE-2023-27523/62899", "specs": [ "<=2.1.0" ], "v": "<=2.1.0" }, { "advisory": "Apache Superset prior to 1.1.0 allowed for the creation of an external URL that could be malicious. By not checking user input for open redirects the URL shortener functionality would allow for a malicious user to create a short URL for a dashboard that could convince the user to click the link.", "cve": "CVE-2021-28125", "id": "pyup.io-54264", "more_info_path": "/vulnerabilities/CVE-2021-28125/54264", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Versions of Superset prior to 0.23 used an unsafe load method from the pickle library to deserialize data leading to possible remote code execution. Note Superset 0.23 was released prior to any Superset release under the Apache Software Foundation.", "cve": "CVE-2018-8021", "id": "pyup.io-54031", "more_info_path": "/vulnerabilities/CVE-2018-8021/54031", "specs": [ ">=0,<0.23.0" ], "v": ">=0,<0.23.0" }, { "advisory": "An authenticated user with specific data permissions could access database connections stored passwords by requesting a specific REST API.\u00a0This issue affects Apache Superset version 1.3.0 up to 2.0.1.", "cve": "CVE-2023-30776", "id": "pyup.io-64174", "more_info_path": "/vulnerabilities/CVE-2023-30776/64174", "specs": [ ">=1.3.0,<=2.0.1" ], "v": ">=1.3.0,<=2.0.1" } ], "superset-tddv": [ { "advisory": "Superset-tddv (superset fork) 0.15.2 and prior have dependencies with known vulnerabilities (mathjs).", "cve": "CVE-2017-1001002", "id": "pyup.io-47112", "more_info_path": "/vulnerabilities/CVE-2017-1001002/47112", "specs": [ "<=0.15.2" ], "v": "<=0.15.2" }, { "advisory": "Superset-tddv (superset fork) 0.15.2 and prior lets all derived FAB UserModelView views to be accesible for non-admin users.\r\nhttps://github.com/apache/superset/pull/4180/commits/74e33eeab9ab388a38892fd4aa2541bf65e7692a", "cve": "PVE-2021-36204", "id": "pyup.io-48164", "more_info_path": "/vulnerabilities/PVE-2021-36204/48164", "specs": [ "<=0.15.2" ], "v": "<=0.15.2" }, { "advisory": "Superset-tddv (superset fork) 0.15.2 and prior have dependencies with known vulnerabilities (moment).", "cve": "CVE-2017-18214", "id": "pyup.io-48163", "more_info_path": "/vulnerabilities/CVE-2017-18214/48163", "specs": [ "<=0.15.2" ], "v": "<=0.15.2" }, { "advisory": "Superset-tddv (superset fork) 0.15.2 and prior have dependencies with known vulnerabilities (mathjs).", "cve": "CVE-2017-1001003", "id": "pyup.io-48162", "more_info_path": "/vulnerabilities/CVE-2017-1001003/48162", "specs": [ "<=0.15.2" ], "v": "<=0.15.2" }, { "advisory": "Superset-tddv (superset fork) 0.15.2 and prior have a code execution vulnerability because of using unsafe yaml.load().", "cve": "CVE-2017-18342", "id": "pyup.io-48165", "more_info_path": "/vulnerabilities/CVE-2017-18342/48165", "specs": [ "<=0.15.2" ], "v": "<=0.15.2" } ], "supervisor": [ { "advisory": "** Disputed ** Affected versions of Supervisor allow an unauthenticated user to read log files or restart a service when the inet_http_server component is enabled without a password. While this component is not activated by default, failure to secure it with a password exposes the system to unauthorized access. Logged warnings and documentation advisories were added to prevent this risky usage.", "cve": "CVE-2019-12105", "id": "pyup.io-70372", "more_info_path": "/vulnerabilities/CVE-2019-12105/70372", "specs": [ "<4.0.4" ], "v": "<4.0.4" }, { "advisory": "Supervisor versions 3.0.1, 3.1.4, 3.2.4 and 3.3.3 include a fix for CVE-2017-11610: The XML-RPC server in supervisor before 3.0.1, 3.1.x before 3.1.4, 3.2.x before 3.2.4, and 3.3.x before 3.3.3 allows remote authenticated users to execute arbitrary commands via a crafted XML-RPC request, related to nested supervisord namespace lookups.", "cve": "CVE-2017-11610", "id": "pyup.io-34840", "more_info_path": "/vulnerabilities/CVE-2017-11610/34840", "specs": [ ">=3.3,<3.3.3", ">=3.2,<3.2.4", ">=3.1,<3.1.4", "<3.0.1" ], "v": ">=3.3,<3.3.3,>=3.2,<3.2.4,>=3.1,<3.1.4,<3.0.1" } ], "suricata-update": [ { "advisory": "OISF suricata-update version 1.0.0a1 contains an Insecure Deserialization vulnerability in the insecure yaml.load-Function as used in the following files: config.py:136, config.py:142, sources.py:99 and sources.py:131. The \"list-sources\"-command is affected by this bug. that can result in Remote Code Execution(even as root if suricata-update is called by root). This attack appears to be exploitable via a specially crafted yaml-file at https://www.openinfosecfoundation.org/rules/index.yaml. This vulnerability appears to have been fixed in 1.0.0b1.", "cve": "CVE-2018-1000167", "id": "pyup.io-53984", "more_info_path": "/vulnerabilities/CVE-2018-1000167/53984", "specs": [ ">=0,<1.0.0b1" ], "v": ">=0,<1.0.0b1" } ], "sushy-tools": [ { "advisory": "Sushy-tools 0.21.1 includes a fix for CVE-2022-44020: An issue was discovered in OpenStack Sushy-Tools through 0.21.0 and VirtualBMC through 2.2.2. Changing the boot device configuration with these packages removes password protection from the managed libvirt XML domain. NOTE: this only affects an \"unsupported, production-like configuration.\"", "cve": "CVE-2022-44020", "id": "pyup.io-51614", "more_info_path": "/vulnerabilities/CVE-2022-44020/51614", "specs": [ "<=0.21.0" ], "v": "<=0.21.0" } ], "sutiltype": [ { "advisory": "Sutiltype is a malicious package. It triggers the install of W4SP Stealer in your system.", "cve": "PVE-2022-51673", "id": "pyup.io-51673", "more_info_path": "/vulnerabilities/PVE-2022-51673/51673", "specs": [ ">0" ], "v": ">0" } ], "sv-dlp": [ { "advisory": "Sv-dlp 2023.11.12 updates its dependency 'requests' to v2.31.0 to include a security fix.", "cve": "CVE-2023-32681", "id": "pyup.io-62271", "more_info_path": "/vulnerabilities/CVE-2023-32681/62271", "specs": [ "<2023.11.12" ], "v": "<2023.11.12" }, { "advisory": "Sv-dlp 2023.11.12 updates its dependency 'certifi' to v2023.7.22 to include a security fix.", "cve": "CVE-2023-37920", "id": "pyup.io-62265", "more_info_path": "/vulnerabilities/CVE-2023-37920/62265", "specs": [ "<2023.11.12" ], "v": "<2023.11.12" }, { "advisory": "Sv-dlp 2023.2.6.1 updates its dependency 'certifi' to v2022.12.7 to include a security fix.", "cve": "CVE-2022-23491", "id": "pyup.io-53043", "more_info_path": "/vulnerabilities/CVE-2022-23491/53043", "specs": [ "<2023.2.6.1" ], "v": "<2023.2.6.1" }, { "advisory": "Sv-dlp 2023.2.6.1 updates its dependency 'pillow' to v9.3.0 to include security fixes.", "cve": "CVE-2022-45199", "id": "pyup.io-53044", "more_info_path": "/vulnerabilities/CVE-2022-45199/53044", "specs": [ "<2023.2.6.1" ], "v": "<2023.2.6.1" }, { "advisory": "Sv-dlp 2023.2.6.1 updates its dependency 'pillow' to v9.3.0 to include security fixes.", "cve": "CVE-2022-45198", "id": "pyup.io-53045", "more_info_path": "/vulnerabilities/CVE-2022-45198/53045", "specs": [ "<2023.2.6.1" ], "v": "<2023.2.6.1" }, { "advisory": "Sv-dlp 2023.2.6.1 updates its dependency 'protobuf' to v4.21.6 to include a security fix.", "cve": "CVE-2022-1941", "id": "pyup.io-53046", "more_info_path": "/vulnerabilities/CVE-2022-1941/53046", "specs": [ "<2023.2.6.1" ], "v": "<2023.2.6.1" }, { "advisory": "Sv-dlp 2023.2.6.1 updates its dependency 'future' to v0.18.3 to include a security fix.", "cve": "CVE-2022-40899", "id": "pyup.io-53006", "more_info_path": "/vulnerabilities/CVE-2022-40899/53006", "specs": [ "<2023.2.6.1" ], "v": "<2023.2.6.1" } ], "svg-matrix": [ { "advisory": "Affected versions of the SVG-MATRIX package are vulnerable to command injection due to unsafe shell command construction in font-manager.js.\r\nhttps://github.com/Emasoft/SVG-MATRIX/commit/cd8e35cb82a06d9de8031266a486ce05aa6c7cd0", "cve": "PVE-2026-85377", "id": "pyup.io-85377", "more_info_path": "/vulnerabilities/PVE-2026-85377/85377", "specs": [ "<1.3.1" ], "v": "<1.3.1" } ], "svgdigitizer": [ { "advisory": "Svgdigitizer version 0.11.0 upgrades its Pillow dependency to include a security fix. This may introduce compatibility issues with macOS. \r\nhttps://github.com/echemdb/svgdigitizer/commit/d9c6d5773d9e568b2cd7c96f3800ca49c3b8a384", "cve": "CVE-2023-4863", "id": "pyup.io-65726", "more_info_path": "/vulnerabilities/CVE-2023-4863/65726", "specs": [ "<0.11.0" ], "v": "<0.11.0" }, { "advisory": "Svgdigitizer version 0.3.0 upgrades its Pillow dependency to address the security vulnerability CVE-2022-22817\r\nhttps://github.com/echemdb/svgdigitizer/commit/4dbc6dbc558921f79caa43f2ce1fdd267eafbfb0", "cve": "CVE-2022-22817", "id": "pyup.io-65727", "more_info_path": "/vulnerabilities/CVE-2022-22817/65727", "specs": [ "<0.3.0" ], "v": "<0.3.0" } ], "svgelements": [ { "advisory": "Svgelements 1.7.0 includes a fix for a ReDoS vulnerability.\r\nhttps://github.com/meerk40t/svgelements/commit/fad014e37c32481ab29d760780816f2c0b7f004e", "cve": "PVE-2023-60490", "id": "pyup.io-60490", "more_info_path": "/vulnerabilities/PVE-2023-60490/60490", "specs": [ "<1.7.0" ], "v": "<1.7.0" } ], "svglib": [ { "advisory": "The svglib package through 0.9.3 for Python allows XXE attacks via an svg2rlg call. See: CVE-2020-10799.", "cve": "CVE-2020-10799", "id": "pyup.io-38089", "more_info_path": "/vulnerabilities/CVE-2020-10799/38089", "specs": [ "<=0.9.3" ], "v": "<=0.9.3" } ], "svix": [ { "advisory": "Svix 0.43.2 updates its JS dependency 'node-fetch' to v2.6.7 to include a security fix.", "cve": "CVE-2022-0235", "id": "pyup.io-44674", "more_info_path": "/vulnerabilities/CVE-2022-0235/44674", "specs": [ "<0.43.2" ], "v": "<0.43.2" } ], "svmbir": [ { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-28676", "id": "pyup.io-43517", "more_info_path": "/vulnerabilities/CVE-2021-28676/43517", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-25291", "id": "pyup.io-43522", "more_info_path": "/vulnerabilities/CVE-2021-25291/43522", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-25290", "id": "pyup.io-43523", "more_info_path": "/vulnerabilities/CVE-2021-25290/43523", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-25289", "id": "pyup.io-43524", "more_info_path": "/vulnerabilities/CVE-2021-25289/43524", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-27922", "id": "pyup.io-43526", "more_info_path": "/vulnerabilities/CVE-2021-27922/43526", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-25292", "id": "pyup.io-43521", "more_info_path": "/vulnerabilities/CVE-2021-25292/43521", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-25293", "id": "pyup.io-43520", "more_info_path": "/vulnerabilities/CVE-2021-25293/43520", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-28677", "id": "pyup.io-43516", "more_info_path": "/vulnerabilities/CVE-2021-28677/43516", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-25287", "id": "pyup.io-43519", "more_info_path": "/vulnerabilities/CVE-2021-25287/43519", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-27921", "id": "pyup.io-43525", "more_info_path": "/vulnerabilities/CVE-2021-27921/43525", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-27923", "id": "pyup.io-43527", "more_info_path": "/vulnerabilities/CVE-2021-27923/43527", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-25288", "id": "pyup.io-43518", "more_info_path": "/vulnerabilities/CVE-2021-25288/43518", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Svmbir 0.2.3 updates its dependency 'Pillow' to v8.2.0 to include security fixes.", "cve": "CVE-2021-28678", "id": "pyup.io-41046", "more_info_path": "/vulnerabilities/CVE-2021-28678/41046", "specs": [ "<0.2.3" ], "v": "<0.2.3" } ], "sw360": [ { "advisory": "Sw360 1.2.1 updates its dependency 'certifi' to v2022.12.7 to include a security fix.", "cve": "CVE-2022-23491", "id": "pyup.io-52667", "more_info_path": "/vulnerabilities/CVE-2022-23491/52667", "specs": [ "<1.2.1" ], "v": "<1.2.1" }, { "advisory": "Sw360 1.3.1 updates its dependency 'urllib3' to v1.26.18 to include security fixes.", "cve": "CVE-2023-45803", "id": "pyup.io-62270", "more_info_path": "/vulnerabilities/CVE-2023-45803/62270", "specs": [ "<1.3.1" ], "v": "<1.3.1" }, { "advisory": "Sw360 1.3.1 updates its dependency 'urllib3' to v1.26.18 to include security fixes.", "cve": "CVE-2023-43804", "id": "pyup.io-62267", "more_info_path": "/vulnerabilities/CVE-2023-43804/62267", "specs": [ "<1.3.1" ], "v": "<1.3.1" }, { "advisory": "Sw360 version 1.5.0 has updated its dependency on the idna library to version 3.7 in order to address the security vulnerabilities detailed in CVE-2024-3651.", "cve": "CVE-2024-3651", "id": "pyup.io-68051", "more_info_path": "/vulnerabilities/CVE-2024-3651/68051", "specs": [ "<1.5.0" ], "v": "<1.5.0" } ], "swauth": [ { "advisory": "swauth before 1.1.0 has multiple undisclosed security vulnerabilities.", "cve": "PVE-2021-26150", "id": "pyup.io-26150", "more_info_path": "/vulnerabilities/PVE-2021-26150/26150", "specs": [ "<1.1.0" ], "v": "<1.1.0" }, { "advisory": "Swauth v1.3.0 includes a fix for CVE-2017-16613: An issue was discovered in middleware.py in OpenStack Swauth through 1.2.0 when used with OpenStack Swift through 2.15.1. The Swift object store and proxy server are saving (unhashed) tokens retrieved from the Swauth middleware authentication mechanism to a log file as part of a GET URI. This allows attackers to bypass authentication by inserting a token into an X-Auth-Token header of a new request. NOTE: github.com/openstack/swauth URLs do not mean that Swauth is maintained by an official OpenStack project team.\r\nhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882314\r\nhttps://bugs.launchpad.net/swift/+bug/1655781\r\nhttps://github.com/openstack/swauth/commit/70af7986265a3defea054c46efc82d0698917298\r\nhttps://www.debian.org/security/2017/dsa-4044\r\nhttp://www.securityfocus.com/bid/101926", "cve": "CVE-2017-16613", "id": "pyup.io-35717", "more_info_path": "/vulnerabilities/CVE-2017-16613/35717", "specs": [ "<1.3.0" ], "v": "<1.3.0" }, { "advisory": "Swift3 before 1.9 allows remote attackers to conduct replay attacks via an Authorization request that lacks a Date header.", "cve": "CVE-2015-8466", "id": "pyup.io-70416", "more_info_path": "/vulnerabilities/CVE-2015-8466/70416", "specs": [ "<1.9" ], "v": "<1.9" } ], "swift": [ { "advisory": "OpenStack Object Storage (swift) before 1.7.0 uses the loads function in the pickle Python module unsafely when storing and loading metadata in memcached, which allows remote attackers to execute arbitrary code via a crafted pickle object.", "cve": "CVE-2012-4406", "id": "pyup.io-35372", "more_info_path": "/vulnerabilities/CVE-2012-4406/35372", "specs": [ "<1.7.0" ], "v": "<1.7.0" }, { "advisory": "OpenStack Swift before 1.9.1 in Folsom, Grizzly, and Havana allows authenticated users to cause a denial of service (\"superfluous\" tombstone consumption and Swift cluster slowdown) via a DELETE request with a timestamp that is older than expected.", "cve": "CVE-2013-4155", "id": "pyup.io-67987", "more_info_path": "/vulnerabilities/CVE-2013-4155/67987", "specs": [ "<1.9.1" ], "v": "<1.9.1" }, { "advisory": "OpenStack Object Storage (Swift) before 2.2.0 allows remote authenticated users to bypass the max_meta_count and other metadata constraints via multiple crafted requests which exceed the limit when combined.", "cve": "CVE-2014-7960", "id": "pyup.io-70435", "more_info_path": "/vulnerabilities/CVE-2014-7960/70435", "specs": [ "<2.2.0" ], "v": "<2.2.0" }, { "advisory": "Swift 2.28.1 and 2.29.2 include a fix for CVE-2022-47950: An issue was discovered in OpenStack Swift before 2.28.1, 2.29.x before 2.29.2 and 2.30.0. By supplying crafted XML files, an authenticated user may coerce the S3 API into returning arbitrary file contents from the host server, resulting in unauthorized read access to potentially sensitive data. This impacts both s3api deployments (Rocky or later), and swift3 deployments (Queens and earlier, no longer actively developed).\r\nhttps://security.openstack.org/ossa/OSSA-2023-001.html", "cve": "CVE-2022-47950", "id": "pyup.io-52880", "more_info_path": "/vulnerabilities/CVE-2022-47950/52880", "specs": [ "<2.28.1", ">=2.29.0,<2.29.2", "==2.30.0" ], "v": "<2.28.1,>=2.29.0,<2.29.2,==2.30.0" }, { "advisory": "OpenStack Object Storage (Swift) before 2.3.0, when allow_version is configured, allows remote authenticated users to delete the latest version of an object by leveraging listing access to the x-versions-location container.", "cve": "CVE-2015-1856", "id": "pyup.io-70434", "more_info_path": "/vulnerabilities/CVE-2015-1856/70434", "specs": [ "<2.3.0rc1" ], "v": "<2.3.0rc1" }, { "advisory": "OpenStack Object Storage (Swift) before 2.4.0 allows attackers to obtain sensitive information via a PUT tempurl and a DLO object manifest that references an object in another container.", "cve": "CVE-2015-5223", "id": "pyup.io-70415", "more_info_path": "/vulnerabilities/CVE-2015-5223/70415", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "OpenStack Object Storage (Swift) before 2.4.0 does not properly close client connections, which allows remote attackers to cause a denial of service (proxy-server resource consumption) via a series of interrupted requests to a Large Object URL.", "cve": "CVE-2016-0737", "id": "pyup.io-35656", "more_info_path": "/vulnerabilities/CVE-2016-0737/35656", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Swift before 2.6.0 is vulnerable to an attack where an unfinished read of a large object would leak a socket file descriptor and a small amount of memory: CVE-2016-0738.", "cve": "CVE-2016-0738", "id": "pyup.io-26151", "more_info_path": "/vulnerabilities/CVE-2016-0738/26151", "specs": [ "<2.6.0" ], "v": "<2.6.0" }, { "advisory": "In OpenStack Swift through 2.10.1, 2.11.0 through 2.13.0, and 2.14.0, the proxy-server logs full tempurl paths, potentially leaking reusable tempurl signatures to anyone with read access to these logs. All Swift deployments using the tempurl middleware are affected.", "cve": "CVE-2017-8761", "id": "pyup.io-40591", "more_info_path": "/vulnerabilities/CVE-2017-8761/40591", "specs": [ "<=2.10.1", ">=2.11.0,<=2.13.0", "==2.14.0" ], "v": "<=2.10.1,>=2.11.0,<=2.13.0,==2.14.0" }, { "advisory": "Swift 2.0.2 includes a fix for CVE-2013-6396: The OpenStack Python client library for Swift (python-swiftclient) 1.0 through 2.0.2 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.\r\nhttps://bugs.launchpad.net/python-swiftclient/+bug/1199783", "cve": "CVE-2013-6396", "id": "pyup.io-35478", "more_info_path": "/vulnerabilities/CVE-2013-6396/35478", "specs": [ ">=1.0,<2.0.2" ], "v": ">=1.0,<2.0.2" }, { "advisory": "Cross-site scripting (XSS) vulnerability in OpenStack Swift 1.11.0 through 1.13.1 allows remote attackers to inject arbitrary web script or HTML via the WWW-Authenticate header.", "cve": "CVE-2014-3497", "id": "pyup.io-35555", "more_info_path": "/vulnerabilities/CVE-2014-3497/35555", "specs": [ ">=1.11.0,<=1.13.1" ], "v": ">=1.11.0,<=1.13.1" }, { "advisory": "The TempURL middleware in OpenStack Object Storage (Swift) 1.4.6 through 1.8.0, 1.9.0 through 1.10.0, and 1.11.0 allows remote attackers to obtain secret URLs by leveraging an object name and a timing side-channel attack.", "cve": "CVE-2014-0006", "id": "pyup.io-60959", "more_info_path": "/vulnerabilities/CVE-2014-0006/60959", "specs": [ ">=1.4.6,<=1.11.0" ], "v": ">=1.4.6,<=1.11.0" } ], "swifter": [ { "advisory": "Swifter 0.292 fixes a known security vulnerability in parso <= 0.4.0 by requiring parso > 0.4.0", "cve": "PVE-2021-37369", "id": "pyup.io-37369", "more_info_path": "/vulnerabilities/PVE-2021-37369/37369", "specs": [ "<0.292" ], "v": "<0.292" } ], "swig": [ { "advisory": "Swig 3.0.7 fixes potential security exploit in generated Java classes.\r\nhttps://github.com/swig/swig/commit/a1771cb8a0cbba65ffd07bee96a2cb41a9f112fd", "cve": "PVE-2022-50163", "id": "pyup.io-50163", "more_info_path": "/vulnerabilities/PVE-2022-50163/50163", "specs": [ "<3.0.7" ], "v": "<3.0.7" } ], "swiglpk": [ { "advisory": "Swiglpk 5.0.10 updates its C dependency 'GMP' to v6.3.0 to include a security fix.", "cve": "CVE-2021-43618", "id": "pyup.io-62238", "more_info_path": "/vulnerabilities/CVE-2021-43618/62238", "specs": [ "<5.0.10" ], "v": "<5.0.10" } ], "swimlane": [ { "advisory": "Swimlane 10.18.1 updates its certifi dependency from >=2017 to certifi==2024.6.2 to address CVE-2023-37920.", "cve": "CVE-2023-37920", "id": "pyup.io-71826", "more_info_path": "/vulnerabilities/CVE-2023-37920/71826", "specs": [ "<10.18.1" ], "v": "<10.18.1" } ], "swingmusic": [ { "advisory": "Affected versions of the swingmusic package are vulnerable to Path Traversal (Arbitrary File Read) due to insufficient validation of user-supplied file paths in the streaming endpoint. The send_track_file_legacy function in src/swingmusic/api/stream.py failed to validate the filepath query parameter against path traversal sequences and did not verify that the requested file resided within the configured root directories, allowing directory escape via slash-dot-dot-slash sequences.", "cve": "PVE-2026-84675", "id": "pyup.io-84675", "more_info_path": "/vulnerabilities/PVE-2026-84675/84675", "specs": [ "<2.1.0" ], "v": "<2.1.0" }, { "advisory": "Affected versions of the swingmusic package are vulnerable to Path Traversal due to missing path validation and insufficient authorization checks on user-supplied folder paths. The /folder/dir-browser API route invokes list_folders() with a client-controlled folder value. It attempts to \u201cfix\u201d non-existent paths by prepending \u201c/\u201d, but it does not properly normalize or restrict \u201c..\u201d segments to an allowed base directory, enabling traversal outside intended music folders.", "cve": "CVE-2026-23877", "id": "pyup.io-84893", "more_info_path": "/vulnerabilities/CVE-2026-23877/84893", "specs": [ "<2.1.4" ], "v": "<2.1.4" } ], "syft": [ { "advisory": "Syft 0.2.3 uses yaml.safe_load() to fix an arbitrary code execution vulnerability.", "cve": "CVE-2017-18342", "id": "pyup.io-37958", "more_info_path": "/vulnerabilities/CVE-2017-18342/37958", "specs": [ "<0.2.3" ], "v": "<0.2.3" }, { "advisory": "Syft 0.2.3.a1 removes an insecure eval in native tensor interpreter.\r\nhttps://github.com/OpenMined/PySyft/commit/7c6dd8e1164e8319d783f75593596d0ce03f1540", "cve": "PVE-2021-37930", "id": "pyup.io-37930", "more_info_path": "/vulnerabilities/PVE-2021-37930/37930", "specs": [ "<0.2.3.a1" ], "v": "<0.2.3.a1" }, { "advisory": "Syft 0.6.0a0 updates its dependency 'fastapi' to v0.68.0 to include a security fix.", "cve": "CVE-2021-32677", "id": "pyup.io-53713", "more_info_path": "/vulnerabilities/CVE-2021-32677/53713", "specs": [ "<0.6.0a0" ], "v": "<0.6.0a0" }, { "advisory": "Syft 0.8.2b19 removes clear-text logging of sensitive information.\r\nhttps://github.com/OpenMined/PySyft/pull/7961/commits/e78b3b111b06dad059a987202ad2b1eb51aa8b3a", "cve": "PVE-2023-62330", "id": "pyup.io-62330", "more_info_path": "/vulnerabilities/PVE-2023-62330/62330", "specs": [ "<0.8.2b19" ], "v": "<0.8.2b19" }, { "advisory": "Syft 0.8.2b40 updates its dependency 'RestrictedPython' to 6.2 to include a security fix.\r\nhttps://github.com/OpenMined/PySyft/pull/8177/commits/5fb618fbf04ed26cae34d635ddf21d05100367ca", "cve": "CVE-2023-41039", "id": "pyup.io-61959", "more_info_path": "/vulnerabilities/CVE-2023-41039/61959", "specs": [ "<0.8.2b40" ], "v": "<0.8.2b40" }, { "advisory": "Syft 0.8.4b4 updates its dependency 'certifi' to 2023.7.22 to include a security fix on the CVE-2022-23491.\r\nhttps://github.com/OpenMined/PySyft/pull/8356", "cve": "CVE-2022-23491", "id": "pyup.io-63086", "more_info_path": "/vulnerabilities/CVE-2022-23491/63086", "specs": [ "<0.8.4b4" ], "v": "<0.8.4b4" }, { "advisory": "Syft 0.8.4b4 updates its dependency 'pygments' to 2.15.0 to include a security fix on the CVE-2022-40896.\r\nhttps://github.com/OpenMined/PySyft/pull/8356", "cve": "CVE-2022-40896", "id": "pyup.io-63099", "more_info_path": "/vulnerabilities/CVE-2022-40896/63099", "specs": [ "<0.8.4b4" ], "v": "<0.8.4b4" }, { "advisory": "Syft 0.8.4b4 updates its dependency 'certifi' to 2023.7.22 to include a security fix on the CVE-2023-37920.\r\nhttps://github.com/OpenMined/PySyft/pull/8356", "cve": "CVE-2023-37920", "id": "pyup.io-63096", "more_info_path": "/vulnerabilities/CVE-2023-37920/63096", "specs": [ "<0.8.4b4" ], "v": "<0.8.4b4" }, { "advisory": "Syft 0.8.4b4 updates its dependency 'requests' to 2.31.0 to include a security fix on the CVE-2023-32681.\r\nhttps://github.com/OpenMined/PySyft/pull/8356", "cve": "CVE-2023-32681", "id": "pyup.io-63100", "more_info_path": "/vulnerabilities/CVE-2023-32681/63100", "specs": [ "<0.8.4b4" ], "v": "<0.8.4b4" }, { "advisory": "Syft 0.8.4b4 updates its dependency 'pygments' to 2.15.0 to include a security fix on the CVE-2021-20270.\r\nhttps://github.com/OpenMined/PySyft/pull/8356", "cve": "CVE-2021-20270", "id": "pyup.io-63098", "more_info_path": "/vulnerabilities/CVE-2021-20270/63098", "specs": [ "<0.8.4b4" ], "v": "<0.8.4b4" }, { "advisory": "Syft version 0.8.5 updates its setuptools requirement to version 65.5.1 from the prior 39.0.1 to address the security vulnerability identified as CVE-2022-40897.", "cve": "CVE-2022-40897", "id": "pyup.io-65499", "more_info_path": "/vulnerabilities/CVE-2022-40897/65499", "specs": [ "<0.8.5" ], "v": "<0.8.5" }, { "advisory": "Syft version 0.8.5b10 updates its Sphinx dependency to version 3.3.0, addressing a vulnerability to Cross-site Scripting (XSS) as highlighted by CVE-2020-11022. \r\nhttps://github.com/OpenMined/PySyft/pull/8479/commits/4d6787e7a1afc4cea3307926858dd451fc00b609", "cve": "CVE-2020-11022", "id": "pyup.io-66901", "more_info_path": "/vulnerabilities/CVE-2020-11022/66901", "specs": [ "<0.8.5b10" ], "v": "<0.8.5b10" }, { "advisory": "Syft version 0.8.5b10 updates its Sphinx dependency to version 3.3.0, addressing a vulnerability to Cross-site Scripting (XSS) as highlighted by CVE-2020-11023. \r\nhttps://github.com/OpenMined/PySyft/pull/8479/commits/4d6787e7a1afc4cea3307926858dd451fc00b609", "cve": "CVE-2020-11023", "id": "pyup.io-66902", "more_info_path": "/vulnerabilities/CVE-2020-11023/66902", "specs": [ "<0.8.5b10" ], "v": "<0.8.5b10" }, { "advisory": "Syft version 0.8.5b10 updates its Pygments dependency to version 2.15.0, addressing a vulnerability to Regular Expression Denial of Service (ReDoS) as highlighted by CVE-2021-27291. \r\nhttps://github.com/OpenMined/PySyft/pull/8479/commits/4d6787e7a1afc4cea3307926858dd451fc00b609", "cve": "CVE-2021-27291", "id": "pyup.io-66857", "more_info_path": "/vulnerabilities/CVE-2021-27291/66857", "specs": [ "<0.8.5b10", "<0.8.6" ], "v": "<0.8.5b10,<0.8.6" } ], "symphony-bdk-python": [ { "advisory": "Symphony-bdk-python 1.2.0 starts using the more secure defusedxml library to avoid XML vulnerabilities.\r\nhttps://github.com/finos/symphony-bdk-python/commit/114c9abb763cb883d6cdb471cfca38afc32f1adc", "cve": "CVE-2013-1664", "id": "pyup.io-54881", "more_info_path": "/vulnerabilities/CVE-2013-1664/54881", "specs": [ "<1.2.0" ], "v": "<1.2.0" }, { "advisory": "Symphony-bdk-python 1.2.0 starts using the more secure defusedxml library to avoid XML vulnerabilities.\r\nhttps://github.com/finos/symphony-bdk-python/commit/114c9abb763cb883d6cdb471cfca38afc32f1adc", "cve": "CVE-2013-1665", "id": "pyup.io-42121", "more_info_path": "/vulnerabilities/CVE-2013-1665/42121", "specs": [ "<1.2.0" ], "v": "<1.2.0" }, { "advisory": "Symphony-bdk-python version 1.3.5 updates its dependency 'urllib3' to v1.26.5 to include a security fix.", "cve": "CVE-2021-33503", "id": "pyup.io-42120", "more_info_path": "/vulnerabilities/CVE-2021-33503/42120", "specs": [ "<1.3.5" ], "v": "<1.3.5" }, { "advisory": "Symphony-bdk-python 2.0b3 removes potential leak of sensitive information on logs.\r\nhttps://github.com/finos/symphony-bdk-python/pull/185/commits/0d3b600a14a322c69fec977a3bbfd49de4e74978", "cve": "PVE-2022-45399", "id": "pyup.io-45399", "more_info_path": "/vulnerabilities/PVE-2022-45399/45399", "specs": [ "<2.0b3" ], "v": "<2.0b3" } ], "sympy": [ { "advisory": "Sympy 1.12 includes a fix for a XXE vulnerability.", "cve": "PVE-2023-99947", "id": "pyup.io-60917", "more_info_path": "/vulnerabilities/PVE-2023-99947/60917", "specs": [ "<1.12" ], "v": "<1.12" } ], "synadm": [ { "advisory": "Synadm 0.13.1 avoids stating tokens in the debug log file ('~/.local/synadm/debug.log') or in the debug console output ('synadm -vv ...').\r\nhttps://github.com/JOJ0/synadm/commit/d9667f9d4bcdbae40685433ad84cf58dbe2ab088", "cve": "PVE-2021-42832", "id": "pyup.io-42832", "more_info_path": "/vulnerabilities/PVE-2021-42832/42832", "specs": [ "<0.13.1" ], "v": "<0.13.1" } ], "synapse": [ { "advisory": "Synapse 0.0.39 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/vertexproject/synapse/pull/558", "cve": "PVE-2023-59683", "id": "pyup.io-59683", "more_info_path": "/vulnerabilities/PVE-2023-59683/59683", "specs": [ "<0.0.39" ], "v": "<0.0.39" }, { "advisory": "Synapse version 0.0.47 removes 'py' command from the base CLI commands. That could be used to perform authenticated remote code execution as the process running the Daemon object that a user connected to.\r\nhttps://github.com/vertexproject/synapse/pull/633", "cve": "PVE-2021-41800", "id": "pyup.io-41800", "more_info_path": "/vulnerabilities/PVE-2021-41800/41800", "specs": [ "<0.0.47" ], "v": "<0.0.47" }, { "advisory": "Synapse 2.83.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/vertexproject/synapse/pull/2553", "cve": "PVE-2023-59689", "id": "pyup.io-59689", "more_info_path": "/vulnerabilities/PVE-2023-59689/59689", "specs": [ "<2.83.0" ], "v": "<2.83.0" } ], "synapse-downloader": [ { "advisory": "Synapse-downloader 0.0.5 upgrades several dependencies with vulnerabilities.", "cve": "PVE-2021-40828", "id": "pyup.io-40828", "more_info_path": "/vulnerabilities/PVE-2021-40828/40828", "specs": [ "<0.0.5" ], "v": "<0.0.5" } ], "synapseml": [ { "advisory": "Synapseml 0.10.0 updates its NPM dependency 'shelljs' to v0.8.5 to include a security fix.", "cve": "CVE-2022-0144", "id": "pyup.io-50838", "more_info_path": "/vulnerabilities/CVE-2022-0144/50838", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Synapseml 0.10.0 updates its NPM dependency 'nanoid' to v3.2.0 to include a security fix.", "cve": "CVE-2021-23566", "id": "pyup.io-50837", "more_info_path": "/vulnerabilities/CVE-2021-23566/50837", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Synapseml 0.10.0 updates its NPM dependency 'prismjs' to v1.27.0 to include a security fix.", "cve": "CVE-2022-23647", "id": "pyup.io-50835", "more_info_path": "/vulnerabilities/CVE-2022-23647/50835", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Synapseml 0.10.0 updates its NPM dependency 'node-forge' to v1.3.0 to include security fixes.", "cve": "CVE-2022-24771", "id": "pyup.io-50832", "more_info_path": "/vulnerabilities/CVE-2022-24771/50832", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Synapseml 0.10.0 updates its NPM dependency 'node-forge' to v1.3.0 to include security fixes.", "cve": "CVE-2022-24772", "id": "pyup.io-50833", "more_info_path": "/vulnerabilities/CVE-2022-24772/50833", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Synapseml 0.10.0 updates its NPM dependency 'follow-redirects' to v1.14.8 to include a security fix.", "cve": "CVE-2022-0536", "id": "pyup.io-50836", "more_info_path": "/vulnerabilities/CVE-2022-0536/50836", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Synapseml 0.10.0 fixes a vulnerability in Docker.\r\nhttps://github.com/microsoft/SynapseML/pull/1561", "cve": "PVE-2022-50727", "id": "pyup.io-50727", "more_info_path": "/vulnerabilities/PVE-2022-50727/50727", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Synapseml 0.10.0 updates its NPM dependency 'node-forge' to v1.3.0 to include security fixes.", "cve": "CVE-2022-24773", "id": "pyup.io-50834", "more_info_path": "/vulnerabilities/CVE-2022-24773/50834", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Synapseml 0.11.0 updates its NPM dependency 'loader-utils' to v3.2.1 to include security fixes.\r\nhttps://github.com/microsoft/SynapseML/pull/1753/commits/5b3566d8b10f3b35bf46a3032e447ed5fd1ebde0", "cve": "CVE-2022-37599", "id": "pyup.io-55158", "more_info_path": "/vulnerabilities/CVE-2022-37599/55158", "specs": [ "<0.11.0" ], "v": "<0.11.0" }, { "advisory": "Synapseml 0.11.0 updates its NPM dependency 'loader-utils' to v3.2.1 to include security fixes.\r\nhttps://github.com/microsoft/SynapseML/pull/1753/commits/5b3566d8b10f3b35bf46a3032e447ed5fd1ebde0", "cve": "CVE-2022-37603", "id": "pyup.io-55169", "more_info_path": "/vulnerabilities/CVE-2022-37603/55169", "specs": [ "<0.11.0" ], "v": "<0.11.0" }, { "advisory": "Synapseml 0.9.0 updates its dependency 'openjdk' to include several security fixes.\r\nhttps://github.com/microsoft/SynapseML/commit/de4b47b8b6643575eb8dec470dec0dadfd1d836b", "cve": "CVE-2019-3844", "id": "pyup.io-54956", "more_info_path": "/vulnerabilities/CVE-2019-3844/54956", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Synapseml 0.9.0 updates its dependency 'openjdk' to include several security fixes.\r\nhttps://github.com/microsoft/SynapseML/commit/de4b47b8b6643575eb8dec470dec0dadfd1d836b", "cve": "CVE-2020-1967", "id": "pyup.io-54958", "more_info_path": "/vulnerabilities/CVE-2020-1967/54958", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Synapseml 0.9.0 updates its dependency 'openjdk' to include several security fixes.\r\nhttps://github.com/microsoft/SynapseML/commit/de4b47b8b6643575eb8dec470dec0dadfd1d836b", "cve": "CVE-2019-5018", "id": "pyup.io-42702", "more_info_path": "/vulnerabilities/CVE-2019-5018/42702", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Synapseml 0.9.0 updates its dependency 'openjdk' to include several security fixes.\r\nhttps://github.com/microsoft/SynapseML/commit/de4b47b8b6643575eb8dec470dec0dadfd1d836b", "cve": "CVE-2019-3843", "id": "pyup.io-54957", "more_info_path": "/vulnerabilities/CVE-2019-3843/54957", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Synapseml 0.9.0 updates its dependency 'openjdk' to include several security fixes.\r\nhttps://github.com/microsoft/SynapseML/commit/de4b47b8b6643575eb8dec470dec0dadfd1d836b", "cve": "CVE-2019-8457", "id": "pyup.io-54960", "more_info_path": "/vulnerabilities/CVE-2019-8457/54960", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Synapseml 0.9.0 updates its dependency 'openjdk' to include several security fixes.\r\nhttps://github.com/microsoft/SynapseML/commit/de4b47b8b6643575eb8dec470dec0dadfd1d836b", "cve": "CVE-2019-19244", "id": "pyup.io-54959", "more_info_path": "/vulnerabilities/CVE-2019-19244/54959", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Synapseml 0.9.0 updates its dependency 'openjdk' to include several security fixes.\r\nhttps://github.com/microsoft/SynapseML/commit/de4b47b8b6643575eb8dec470dec0dadfd1d836b", "cve": "CVE-2019-12290", "id": "pyup.io-54955", "more_info_path": "/vulnerabilities/CVE-2019-12290/54955", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Synapseml 0.9.0 updates its dependency 'openjdk' to include several security fixes.\r\nhttps://github.com/microsoft/SynapseML/commit/de4b47b8b6643575eb8dec470dec0dadfd1d836b", "cve": "CVE-2020-11655", "id": "pyup.io-54954", "more_info_path": "/vulnerabilities/CVE-2020-11655/54954", "specs": [ "<0.9.0" ], "v": "<0.9.0" } ], "syngen": [ { "advisory": "Syngen 0.5.0 updates its MLflow dependency from version 2.8.0 to 2.8.1 due to the CVE-2023-6015.\r\nhttps://github.com/tdspora/syngen/pull/314/commits/351291b187276f846647544265fe577b94f11e2a", "cve": "CVE-2023-6015", "id": "pyup.io-63682", "more_info_path": "/vulnerabilities/CVE-2023-6015/63682", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Syngen version 0.7.16 upgrades its mlflow dependency to version 2.10.* from 2.9.2 in response to the security vulnerability CVE-2023-6977.", "cve": "CVE-2023-6977", "id": "pyup.io-67017", "more_info_path": "/vulnerabilities/CVE-2023-6977/67017", "specs": [ "<0.7.16" ], "v": "<0.7.16" }, { "advisory": "Syngen version 0.7.16 upgrades its mlflow dependency to version 2.10.* from 2.9.2 in response to the security vulnerability CVE-2023-50447.", "cve": "CVE-2023-50447", "id": "pyup.io-67145", "more_info_path": "/vulnerabilities/CVE-2023-50447/67145", "specs": [ "<0.7.16" ], "v": "<0.7.16" } ], "synology-api": [ { "advisory": "Synology-api 0.2.1 removes an unsecured certificate warning at login.", "cve": "PVE-2021-40549", "id": "pyup.io-40549", "more_info_path": "/vulnerabilities/PVE-2021-40549/40549", "specs": [ "<0.2.1" ], "v": "<0.2.1" } ], "synse": [ { "advisory": "Synse 1.0.0 (python client) updates to work with Synse v3 API version, which contains several security fixes (this one is about a code injection vulnerability in Sanic dependency).", "cve": "PVE-2021-42108", "id": "pyup.io-38512", "more_info_path": "/vulnerabilities/PVE-2021-42108/38512", "specs": [ "<1.0.0" ], "v": "<1.0.0" }, { "advisory": "Synse 1.0.0 (python client) updates to work with Synse v3 API version, which contains several security fixes.", "cve": "CVE-2018-1000518", "id": "pyup.io-45778", "more_info_path": "/vulnerabilities/CVE-2018-1000518/45778", "specs": [ "<1.0.0" ], "v": "<1.0.0" }, { "advisory": "Synse 1.0.0 (python client) updates to work with Synse v3 API version, which contains several security fixes.", "cve": "CVE-2018-18074", "id": "pyup.io-38511", "more_info_path": "/vulnerabilities/CVE-2018-18074/38511", "specs": [ "<1.0.0" ], "v": "<1.0.0" }, { "advisory": "Synse 1.0.0 (python client) updates to work with Synse v3 API version, which contains several security fixes.", "cve": "CVE-2017-18342", "id": "pyup.io-37393", "more_info_path": "/vulnerabilities/CVE-2017-18342/37393", "specs": [ "<1.0.0" ], "v": "<1.0.0" } ], "synthcity": [ { "advisory": "A vulnerability, which was classified as critical, has been found in van_der_Schaar LAB synthcity 0.2.9. Affected by this issue is the function load_from_file of the component PKL File Handler. The manipulation leads to deserialization. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-252182 is the identifier assigned to this vulnerability.", "cve": "CVE-2024-0937", "id": "pyup.io-66734", "more_info_path": "/vulnerabilities/CVE-2024-0937/66734", "specs": [ "<=0.2.9" ], "v": "<=0.2.9" } ], "sys-ej": [ { "advisory": "Sys-ej is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html", "cve": "PVE-2023-52915", "id": "pyup.io-52915", "more_info_path": "/vulnerabilities/PVE-2023-52915/52915", "specs": [ ">0" ], "v": ">0" } ], "system-monitoring-center": [ { "advisory": "System-monitoring-center 0.1.21beta10 fixes code injection vulnerabilities.\r\nhttps://github.com/hakandundar34coding/system-monitoring-center/commit/24da39a821db8db5b6f4af88b21f0cc59a35e633", "cve": "PVE-2022-48245", "id": "pyup.io-48245", "more_info_path": "/vulnerabilities/PVE-2022-48245/48245", "specs": [ "<0.1.21beta10" ], "v": "<0.1.21beta10" } ], "systemds": [ { "advisory": "The Security Team noticed that the termination condition of the for loop in the readExternal method is a controllable variable, which, if tampered with, may lead to CPU exhaustion. As a fix, we added an upper bound and termination condition in the read and write logic. We classify it as a \"low-priority but useful improvement\". SystemDS is a distributed system and needs to serialize/deserialize data but in many code paths (e.g., on Spark broadcast/shuffle or writing to sequence files) the byte stream is anyway protected by additional CRC fingerprints. In this particular case though, the number of decoders is upper-bounded by twice the number of columns, which means an attacker would need to modify two entries in the byte stream in a consistent manner. By adding these checks robustness was strictly improved with almost zero overhead. These code changes are available in versions higher than 2.2.1.", "cve": "CVE-2022-26477", "id": "pyup.io-54463", "more_info_path": "/vulnerabilities/CVE-2022-26477/54463", "specs": [ ">=0,<2.2.2" ], "v": ">=0,<2.2.2" } ], "sysuptoer": [ { "advisory": "Sysuptoer is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html", "cve": "PVE-2023-52918", "id": "pyup.io-52918", "more_info_path": "/vulnerabilities/PVE-2023-52918/52918", "specs": [ ">0" ], "v": ">0" } ], "tableauserverclient": [ { "advisory": "Tableauserverclient 0.18.0 uses defusedxml library to reduce XML attacks surface.\r\nhttps://github.com/tableau/server-client-python/pull/1002", "cve": "PVE-2022-48010", "id": "pyup.io-48010", "more_info_path": "/vulnerabilities/PVE-2022-48010/48010", "specs": [ "<0.17.0.post0.dev8" ], "v": "<0.17.0.post0.dev8" } ], "tablib": [ { "advisory": "Tablib 0.11.5 includes a fix for CVE-2017-2810: An exploitable vulnerability exists in the Databook loading functionality of Tablib 0.11.4. A yaml loaded Databook can execute arbitrary python commands resulting in command execution. An attacker can insert python into loaded yaml to trigger this vulnerability.\r\nhttps://github.com/jazzband/tablib/commit/69abfc3ada5d754cb152119c0b4777043657cb6e", "cve": "CVE-2017-2810", "id": "pyup.io-35731", "more_info_path": "/vulnerabilities/CVE-2017-2810/35731", "specs": [ ">=0.8.1,<0.11.5" ], "v": ">=0.8.1,<0.11.5" } ], "tad-multicharge": [ { "advisory": "Affected versions of tad\u2011multicharge are potentially vulnerable to GitHub Actions credential exposure (CWE\u2011260). The exploit vector is a missing persist\u2011credentials: false setting in actions/checkout, allowing any subsequent workflow step to read on\u2011disk tokens.", "cve": "PVE-2025-76748", "id": "pyup.io-76748", "more_info_path": "/vulnerabilities/PVE-2025-76748/76748", "specs": [ "<0.3.2" ], "v": "<0.3.2" } ], "taegis-magic": [ { "advisory": "Affected versions of taegis_magic are vulnerable to Exposure of Sensitive Information (CWE-200). The use of inspect.currentframe().f_locals in the search function may expose sensitive internal variables such as tenant IDs, regions, or other private data, depending on the local context in which the function is called. This vulnerability could be exploited by unauthorized actors through improper access control, particularly in multi-tenant environments. Mitigation involves replacing f_locals with an explicit dictionary to ensure that only necessary arguments are passed.", "cve": "PVE-2024-73625", "id": "pyup.io-73625", "more_info_path": "/vulnerabilities/PVE-2024-73625/73625", "specs": [ "<2024.10.08" ], "v": "<2024.10.08" } ], "tagmark": [ { "advisory": "Tagmark 0.2.0 updates its dependency 'requests' to v2.31.0 to include a security fix.", "cve": "CVE-2023-32681", "id": "pyup.io-60380", "more_info_path": "/vulnerabilities/CVE-2023-32681/60380", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "taguette": [ { "advisory": "Affected versions of the taguette package are vulnerable to Cross-site Scripting (XSS) due to improper neutralization and lack of HTML escaping in user-controlled project metadata fields. The tag name, tag description, document name, and document description fields are stored and rendered on project load without sanitization, allowing attacker-supplied JavaScript to execute in the page context.", "cve": "CVE-2025-62528", "id": "pyup.io-80475", "more_info_path": "/vulnerabilities/CVE-2025-62528/80475", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Affected versions of the taguette package are vulnerable to External Control of System or Configuration Setting due to improper construction of password reset links from untrusted input. The /reset_password workflow generates the URL embedded in password-reset emails using externally supplied request data, enabling link poisoning of the emailed reset link.", "cve": "CVE-2025-62527", "id": "pyup.io-80474", "more_info_path": "/vulnerabilities/CVE-2025-62527/80474", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Affected versions of the taguette package are vulnerable to Open Redirect due to the use of a user-controlled next parameter in HTTP redirects without validation of the destination. The login handler method go_to_next and the cookies prompt handler in taguette/web/views.py read the next argument via get_argument('next', '') and pass it directly to self.redirect(next) without checking that the URL is relative or belongs to the same host.", "cve": "CVE-2025-67502", "id": "pyup.io-82421", "more_info_path": "/vulnerabilities/CVE-2025-67502/82421", "specs": [ "<1.5.2" ], "v": "<1.5.2" } ], "tahoe-lafs": [ { "advisory": "In tahoe-lafs 1.17.0, the lease-checker now uses JSON instead of pickle to serialize its state. Tahoe will now refuse to run until you either delete all pickle files or migrate them.\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/3825", "cve": "PVE-2021-43046", "id": "pyup.io-43046", "more_info_path": "/vulnerabilities/PVE-2021-43046/43046", "specs": [ "<1.17.0" ], "v": "<1.17.0" }, { "advisory": "Tahoe-lafs 1.17.0 makes the introducer server no longer write the sensitive introducer fURL value to its log at startup time. Instead it writes the well-known path of the file from which this value can be read. \r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/3819", "cve": "PVE-2021-43037", "id": "pyup.io-43037", "more_info_path": "/vulnerabilities/PVE-2021-43037/43037", "specs": [ "<1.17.0" ], "v": "<1.17.0" }, { "advisory": "In tahoe-lafs 1.17.0, the storage server now keeps hashes of lease renew and cancel secrets for all share files instead of keeping the original secrets.\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/3839\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/3841", "cve": "PVE-2021-43048", "id": "pyup.io-43048", "more_info_path": "/vulnerabilities/PVE-2021-43048/43048", "specs": [ "<1.17.0" ], "v": "<1.17.0" }, { "advisory": "Tahoe-lafs 1.17.0 makes the storage protocol operation 'add_lease' now safely reject an attempt to add a 4,294,967,296th lease to an immutable share. Previously this failed with an error after recording the new lease in the share file, resulting in the share file losing track of a one previous lease.\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/3821", "cve": "PVE-2021-43043", "id": "pyup.io-43043", "more_info_path": "/vulnerabilities/PVE-2021-43043/43043", "specs": [ "<1.17.0" ], "v": "<1.17.0" }, { "advisory": "In tahoe-lafs 1.17.0, the storage protocol operation 'readv' now safely rejects attempts to read negative lengths. Previously, these read requests were satisfied with the complete contents of the share file (including trailing metadata) starting from the specified offset.\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/3822", "cve": "PVE-2021-43044", "id": "pyup.io-43044", "more_info_path": "/vulnerabilities/PVE-2021-43044/43044", "specs": [ "<1.17.0" ], "v": "<1.17.0" }, { "advisory": "In tahoe-lafs 1.17.0, the SFTP server no longer accepts password-based credentials for authentication. Public/private key-based credentials are now the only supported authentication type. This removes plaintext password storage from the SFTP credentials file. It also removes a possible timing side-channel vulnerability which might have allowed attackers to discover an account's plaintext password.\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/3827", "cve": "PVE-2021-43047", "id": "pyup.io-43047", "more_info_path": "/vulnerabilities/PVE-2021-43047/43047", "specs": [ "<1.17.0" ], "v": "<1.17.0" }, { "advisory": "In tahoe-lafs 1.17.0, the storage server implementation now respects the 'reserved_space' configuration value when writing lease information and recording corruption advisories. Previously, new leases could be created and written to disk even when the storage server had less remaining space than the configured reserve space value. Now this operation will fail with an exception and the lease will not be created. Similarly, if there is no space available, corruption advisories will be logged but not written to disk.\r\nhttps://tahoe-lafs.org/trac/tahoe-lafs/ticket/3823", "cve": "PVE-2021-43045", "id": "pyup.io-43045", "more_info_path": "/vulnerabilities/PVE-2021-43045/43045", "specs": [ "<1.17.0" ], "v": "<1.17.0" }, { "advisory": "tahoe-lafs before 1.2.0 doesn't make the immutable-file \"ciphertext hash tree\" mandatory.", "cve": "PVE-2021-26152", "id": "pyup.io-26152", "more_info_path": "/vulnerabilities/PVE-2021-26152/26152", "specs": [ "<1.2.0" ], "v": "<1.2.0" }, { "advisory": "Tahoe-lafs 1.4.1 includes a fix for a potential timing attack against the write-enabler.\r\nhttps://github.com/tahoe-lafs/tahoe-lafs/commit/01e2032669d0f4897db90abe5ce96e2f834c0d6b", "cve": "PVE-2021-26153", "id": "pyup.io-26153", "more_info_path": "/vulnerabilities/PVE-2021-26153/26153", "specs": [ "<1.4.1" ], "v": "<1.4.1" }, { "advisory": "tahoe-lafs before 1.8.3 has a flaw that would allow a person who knows a storage index of a file to delete shares of that file.", "cve": "PVE-2021-26154", "id": "pyup.io-26154", "more_info_path": "/vulnerabilities/PVE-2021-26154/26154", "specs": [ "<1.8.3" ], "v": "<1.8.3" }, { "advisory": "Tahoe-LAFS 1.9.0 fails to ensure integrity which allows remote attackers to corrupt mutable files or directories upon retrieval.", "cve": "CVE-2012-0051", "id": "pyup.io-67953", "more_info_path": "/vulnerabilities/CVE-2012-0051/67953", "specs": [ "<1.9.0" ], "v": "<1.9.0" }, { "advisory": "tahoe-lafs before 1.9.1 has a flaw that would allow servers to cause undetected corruption when\r\n retrieving the contents of mutable files (both SDMF and MDMF).", "cve": "PVE-2021-26155", "id": "pyup.io-26155", "more_info_path": "/vulnerabilities/PVE-2021-26155/26155", "specs": [ "<1.9.1" ], "v": "<1.9.1" }, { "advisory": "Tahoe-LAFS v1.3.0 through v1.8.2 could allow unauthorized users to delete immutable files in some cases.", "cve": "CVE-2011-3617", "id": "pyup.io-62024", "more_info_path": "/vulnerabilities/CVE-2011-3617/62024", "specs": [ ">=1.3.0,<=1.8.2" ], "v": ">=1.3.0,<=1.8.2" } ], "tahrir": [ { "advisory": "Affected versions of Tahrir are vulnerable to Cross-Site Request Forgery (CSRF) in several views.", "cve": "PVE-2024-68079", "id": "pyup.io-68079", "more_info_path": "/vulnerabilities/PVE-2024-68079/68079", "specs": [ "<0.8.0" ], "v": "<0.8.0" } ], "taipy": [ { "advisory": "Affected versions of the taipy package (\u2264 3.1.1) are vulnerable to Information Disclosure due to session cookies lacking the Secure and HttpOnly flags. The session management component constructs `document.cookie` without setting Secure and HttpOnly attributes (e.g., `tprh=${tprh};path=/;`), which permits exposure and access to session cookies via insecure channels or client-side scripts. An attacker can exploit this by intercepting the session cookie over non-HTTPS connections or via cross-site scripting, enabling session hijacking and unauthorized access to user sessions.", "cve": "CVE-2024-47833", "id": "pyup.io-78761", "more_info_path": "/vulnerabilities/CVE-2024-47833/78761", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "Affected versions of Taipy have a session cookie missing both the Secure and HttpOnly flags. Without the Secure flag, the cookie can be transmitted over insecure HTTP connections, exposing it to potential interception or tampering. The absence of the HttpOnly flag allows the cookie to be accessed by client-side JavaScript, increasing the risk of cross-site scripting (XSS) attacks.", "cve": "PVE-2024-72965", "id": "pyup.io-72965", "more_info_path": "/vulnerabilities/PVE-2024-72965/72965", "specs": [ ">=0" ], "v": ">=0" } ], "tair": [ { "advisory": "Tair 1.3.3 updates its dependency 'redis' to version '4.4.4' to fix a Race Condition vulnerability.\r\nhttps://github.com/tair-opensource/tair-py/commit/9640ee7b29faba60c06e9b63bf13484b2814c29d", "cve": "CVE-2023-28859", "id": "pyup.io-59672", "more_info_path": "/vulnerabilities/CVE-2023-28859/59672", "specs": [ "<1.3.3" ], "v": "<1.3.3" }, { "advisory": "Tair 1.3.3 updates its dependency 'redis' to version '4.4.4' to fix a Race Condition vulnerability.\r\nhttps://github.com/tair-opensource/tair-py/commit/9640ee7b29faba60c06e9b63bf13484b2814c29d", "cve": "CVE-2023-28858", "id": "pyup.io-59729", "more_info_path": "/vulnerabilities/CVE-2023-28858/59729", "specs": [ "<1.3.3" ], "v": "<1.3.3" } ], "talkpipe": [ { "advisory": "Affected versions of the talkpipe package are vulnerable to Information Disclosure due to permissive Cross-Origin Resource Sharing and a missing authentication check on the Server-Sent Events endpoint. The FastAPI server\u2019s middleware allowed * origins and the /output-stream route lacked an API-key dependency, enabling cross-origin access to streamed responses without verifying the caller.", "cve": "PVE-2025-80146", "id": "pyup.io-80146", "more_info_path": "/vulnerabilities/PVE-2025-80146/80146", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Affected versions of the talkpipe package are vulnerable to Remote Code Execution due to untrusted expression evaluation in the compileLambda helper. The talkpipe.util.data_manipulation.compileLambda function compiled and executed a user-supplied Python expression via eval(...) with insufficient sandboxing and unsafe locals injection, permitting attribute walks such as __mro__/__subclasses__ and other dangerous constructs to bypass the intended safe built-ins.", "cve": "PVE-2025-80076", "id": "pyup.io-80076", "more_info_path": "/vulnerabilities/PVE-2025-80076/80076", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Affected versions of the talkpipe package are vulnerable to Command Injection due to improper use of the system shell when running external commands. The talkpipe.util.os.run_command function invoked subprocess.Popen(..., shell=True) on a user-controlled command string without rigorous validation, enabling injection via metacharacters, pipes, command substitution, or path traversal sequences.", "cve": "PVE-2025-80147", "id": "pyup.io-80147", "more_info_path": "/vulnerabilities/PVE-2025-80147/80147", "specs": [ "<0.9.0" ], "v": "<0.9.0" } ], "talkytrend": [ { "advisory": "Talkytrend from version 1.7.0 started to use 'xmltodict' instead of 'defusedxml' for security concerns.\r\nhttps://github.com/mraniki/talkytrend/commit/60fb19a5c3d22ee262907c211a3cf89355448590", "cve": "PVE-2023-59407", "id": "pyup.io-59407", "more_info_path": "/vulnerabilities/PVE-2023-59407/59407", "specs": [ "<1.7.0" ], "v": "<1.7.0" } ], "tamp": [ { "advisory": "Affected versions of the tamp package before commit 6bdfc102 are potentially vulnerable to Denial of Service (DoS) due to missing bounds checks in the decompression sliding-window offset and length handling.", "cve": "PVE-2025-80794", "id": "pyup.io-80794", "more_info_path": "/vulnerabilities/PVE-2025-80794/80794", "specs": [ "<1.10.3" ], "v": "<1.10.3" } ], "tap-rest-api-msdk": [ { "advisory": "Tap-rest-api-msdk 1.3.2 updates its dependency 'cryptography' to version '41.0.3' to include a fix for an Insufficient Verification of Data Authenticity vulnerability.", "cve": "CVE-2023-2975", "id": "pyup.io-60222", "more_info_path": "/vulnerabilities/CVE-2023-2975/60222", "specs": [ "<1.3.2" ], "v": "<1.3.2" }, { "advisory": "Tap-rest-api-msdk 1.3.2 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a Denial of Service vulnerability.", "cve": "CVE-2023-3446", "id": "pyup.io-60221", "more_info_path": "/vulnerabilities/CVE-2023-3446/60221", "specs": [ "<1.3.2" ], "v": "<1.3.2" }, { "advisory": "Tap-rest-api-msdk 1.3.2 updates its dependency 'cryptography' to version '41.0.3' to include a fix for a Denial of Service vulnerability.\r\nhttps://github.com/Widen/tap-rest-api-msdk/pull/38", "cve": "CVE-2023-3817", "id": "pyup.io-60210", "more_info_path": "/vulnerabilities/CVE-2023-3817/60210", "specs": [ "<1.3.2" ], "v": "<1.3.2" } ], "tapescript": [ { "advisory": "Affected versions of Tapescript are vulnerable to denial of service attacks from the 6 byte script `true loop { dup concat }`. To fix this, a new class `Stack` with item size limits was implemented.", "cve": "PVE-2024-71309", "id": "pyup.io-71309", "more_info_path": "/vulnerabilities/PVE-2024-71309/71309", "specs": [ "<0.5.0" ], "v": "<0.5.0" } ], "tapestry": [ { "advisory": "Tapestry 1.1.0 closed the security issue which could result in recovery from unauthenticated blocks without warning the user.", "cve": "PVE-2021-39374", "id": "pyup.io-39374", "more_info_path": "/vulnerabilities/PVE-2021-39374/39374", "specs": [ "<1.1.0" ], "v": "<1.1.0" } ], "tarantool": [ { "advisory": "Tarantool 0.10.0 updates its dependency 'msgpack' requirement to '>=1.0.4' to include a security fix.", "cve": "PVE-2021-36700", "id": "pyup.io-51788", "more_info_path": "/vulnerabilities/PVE-2021-36700/51788", "specs": [ "<0.10.0" ], "v": "<0.10.0" } ], "targetcli": [ { "advisory": "Open-iSCSI targetcli-fb through 2.1.52 has weak permissions for /etc/target (and for the backup directory and backup files).", "cve": "CVE-2020-13867", "id": "pyup.io-74632", "more_info_path": "/vulnerabilities/CVE-2020-13867/74632", "specs": [ "<2.1.53" ], "v": "<2.1.53" }, { "advisory": "A flaw was found in Linux, in targetcli-fb versions 2.1.50 and 2.1.51 where the socket used by targetclid was world-writable. If a system enables the targetclid socket, a local attacker can use this flaw to modify the iSCSI configuration and escalate their privileges to root.", "cve": "CVE-2020-10699", "id": "pyup.io-74631", "more_info_path": "/vulnerabilities/CVE-2020-10699/74631", "specs": [ "<2.1.53" ], "v": "<2.1.53" } ], "targetcli-fb": [ { "advisory": "Targetcli-fb 2.1.53 includes a fix for CVE-2020-13867: Weak permissions for /etc/target (and for the backup directory and backup files).\r\nhttps://github.com/open-iscsi/targetcli-fb/commit/9f5764dac39b5b75ee6b5d9e4db419d09d64b898", "cve": "CVE-2020-13867", "id": "pyup.io-42275", "more_info_path": "/vulnerabilities/CVE-2020-13867/42275", "specs": [ "<=2.1.52" ], "v": "<=2.1.52" }, { "advisory": "Targetcli-fb 2.1.52 includes a fix for CVE-2020-10699: A flaw was found in Linux, in targetcli-fb versions 2.1.50 and 2.1.51 where the socket used by targetclid was world-writable. If a system enables the targetclid socket, a local attacker can use this flaw to modify the iSCSI configuration and escalate their privileges to root.\r\nhttps://github.com/open-iscsi/targetcli-fb/issues/162", "cve": "CVE-2020-10699", "id": "pyup.io-42271", "more_info_path": "/vulnerabilities/CVE-2020-10699/42271", "specs": [ "==2.1.50", "==2.1.51" ], "v": "==2.1.50,==2.1.51" } ], "tartufo": [ { "advisory": "Tartufo 2.5.0 disabled codecov due to a security breach.", "cve": "PVE-2021-41099", "id": "pyup.io-41099", "more_info_path": "/vulnerabilities/PVE-2021-41099/41099", "specs": [ "<2.5.0" ], "v": "<2.5.0" }, { "advisory": "Tartufo version 4.0.1 upgrades its GitPython dependency to version 3.1.30 in response to security concerns raised by CVE-2022-24439.\r\nhttps://github.com/godaddy/tartufo/pull/448/commits/38501c0c10b3a0c11498cc0230365078867770d7", "cve": "CVE-2022-24439", "id": "pyup.io-66656", "more_info_path": "/vulnerabilities/CVE-2022-24439/66656", "specs": [ "<4.0.1" ], "v": "<4.0.1" } ], "task-queue": [ { "advisory": "Task-queue 2.7.0 includes a fix for a race condition vulnerability.\r\nhttps://github.com/seung-lab/python-task-queue/commit/ec30b4e659975217b0518a7e7c59b27c537f7e90", "cve": "PVE-2023-60908", "id": "pyup.io-60908", "more_info_path": "/vulnerabilities/PVE-2023-60908/60908", "specs": [ "<2.7.0" ], "v": "<2.7.0" } ], "taskgraph": [ { "advisory": "Taskgraph 0.10.0 contains multiple race conditions that may cause the TaskGraph object to become unresponsive during its normal termination procedure. These race conditions do more than just freeze the object; they also pose a risk of initiating a Denial of Service (DoS) attack.\r\nhttps://github.com/natcap/taskgraph/commit/f05e71b0f6b72645768ad2f5ea87ed75c799be16", "cve": "PVE-2023-62055", "id": "pyup.io-62055", "more_info_path": "/vulnerabilities/PVE-2023-62055/62055", "specs": [ "<0.10.0" ], "v": "<0.10.0" }, { "advisory": "Taskgraph 0.8.0 resolves a race condition that could sometimes cause an exception when multiple threads tried to read or write to the completed Task Database at the same time. This issue has additional implications beyond just triggering exceptions. While it's uncertain, there is a potential for this to escalate into something like a Denial of Service (DoS) attack, although executing such an attack might not be straightforward. More critically, the concurrent read and write operations by multiple threads on the same memory location pose a risk of data corruption or even data leakage. These threads are performing different tasks simultaneously, making the system more vulnerable. If exploited intentionally, this could turn into a significant security issue.\r\nhttps://github.com/natcap/taskgraph/commit/e5dbecb7bf02070a3813d13b2d0854e7fdf06c97", "cve": "PVE-2023-62056", "id": "pyup.io-62056", "more_info_path": "/vulnerabilities/PVE-2023-62056/62056", "specs": [ "<0.8.0" ], "v": "<0.8.0" } ], "tasos-apiauth": [ { "advisory": "Tasos-apiauth version 0.1.1 has updated its fastapi dependency to mitigate the CVE-2024-24762 vulnerability, which arises from its starlette dependency and the python-multipart package's susceptibility to a Content-Type Header ReDoS attack.", "cve": "CVE-2024-24762", "id": "pyup.io-66764", "more_info_path": "/vulnerabilities/CVE-2024-24762/66764", "specs": [ "<0.1.1" ], "v": "<0.1.1" }, { "advisory": "Tasos-apiauth 0.2.1 updates its cryptography dependency from version 42.0.2 to 42.0.4 to address a security vulnerability identified as CVE-2024-26130.", "cve": "CVE-2024-26130", "id": "pyup.io-72049", "more_info_path": "/vulnerabilities/CVE-2024-26130/72049", "specs": [ "<0.2.1" ], "v": "<0.2.1" } ], "tatoebatools": [ { "advisory": "Tatoebatools 0.2.2 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.", "cve": "CVE-2007-4559", "id": "pyup.io-59165", "more_info_path": "/vulnerabilities/CVE-2007-4559/59165", "specs": [ "<0.2.2" ], "v": "<0.2.2" } ], "tautulli": [ { "advisory": "Tautulli 2.1.3beta includes a fix for a XSS vulnerability.\r\nhttps://github.com/Tautulli/Tautulli/commit/4fb4410552553ac3993fed641c1d3f251462d072", "cve": "PVE-2023-60556", "id": "pyup.io-60556", "more_info_path": "/vulnerabilities/PVE-2023-60556/60556", "specs": [ "<2.1.3beta" ], "v": "<2.1.3beta" } ], "tbats": [ { "advisory": "Tbats 1.0.7 upgrades its dependencies due to an vulnerability in Jinja2. In Pallets Jinja before 2.10.1, str.format_map allows a sandbox escape.", "cve": "PVE-2022-45137", "id": "pyup.io-37051", "more_info_path": "/vulnerabilities/PVE-2022-45137/37051", "specs": [ "<1.0.7" ], "v": "<1.0.7" }, { "advisory": "Tbats 1.0.8 updates its dependency 'urllib3' to include a security fix.", "cve": "CVE-2019-11324", "id": "pyup.io-37336", "more_info_path": "/vulnerabilities/CVE-2019-11324/37336", "specs": [ "<1.0.8" ], "v": "<1.0.8" } ], "td-ameritrade-python-api": [ { "advisory": "Td-ameritrade-python-api 0.3.2 no longer auto-generates 'credentials.json' in the utility folder out of a concern for security. Instead, the user must specify where they would like to cache their refresh token.", "cve": "PVE-2021-39230", "id": "pyup.io-39230", "more_info_path": "/vulnerabilities/PVE-2021-39230/39230", "specs": [ "<0.3.2" ], "v": "<0.3.2" }, { "advisory": "Versions of the td-ameritrade-python-api library are susceptible to information exposure due to the automatic generation of a credentials.json file in the utility folder, which could potentially expose sensitive information.", "cve": "PVE-2024-99855", "id": "pyup.io-65565", "more_info_path": "/vulnerabilities/PVE-2024-99855/65565", "specs": [ ">=0,<0.3.2" ], "v": ">=0,<0.3.2" } ], "tdd-guard": [ { "advisory": "Affected versions of the tdd-guard package are potentially vulnerable to Regular Expression Denial of Service (ReDoS). The extractFromJsonCodeBlock and extractFromGenericCodeBlock functions rely on overly permissive regexes that can enter catastrophic backtracking when given maliciously crafted input, leading to excessive CPU consumption and unresponsive behaviour.", "cve": "PVE-2025-78214", "id": "pyup.io-78214", "more_info_path": "/vulnerabilities/PVE-2025-78214/78214", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "teamscale-cli": [ { "advisory": "Teamscale-cli 9.1.2 updates its dependency 'gitpython' to v3.1.35 to include a security fix.", "cve": "CVE-2023-41040", "id": "pyup.io-61433", "more_info_path": "/vulnerabilities/CVE-2023-41040/61433", "specs": [ "<9.1.2" ], "v": "<9.1.2" } ], "teiphy": [ { "advisory": "Teiphy 0.1.13 updates its dependency 'jinja2' to include a security fix.", "cve": "CVE-2024-34064", "id": "pyup.io-74100", "more_info_path": "/vulnerabilities/CVE-2024-34064/74100", "specs": [ "<0.1.13" ], "v": "<0.1.13" } ], "telebot-components": [ { "advisory": "Telebot-components version 0.11.1 upgrades its aiohttp dependency to version 3.9.2 from 3.9.1. This update is in response to addressing the security concern identified as CVE-2024-23334.\r\nhttps://github.com/bots-against-war/telebot-components/commit/a33844be3278d4ae491292bf513d7a06f153436f", "cve": "CVE-2024-23334", "id": "pyup.io-64953", "more_info_path": "/vulnerabilities/CVE-2024-23334/64953", "specs": [ "<0.11.1" ], "v": "<0.11.1" }, { "advisory": "Telebot-components version 0.11.2 updates its cryptography version requirement to be at least 41.0.6 but less than 43.0.0, in response to security concerns outlined in CVE-2023-49083.\r\nhttps://github.com/bots-against-war/telebot-components/commit/378539e8150a42d5356a467426b1d98d0730b7b4", "cve": "CVE-2023-49083", "id": "pyup.io-65367", "more_info_path": "/vulnerabilities/CVE-2023-49083/65367", "specs": [ "<0.11.2" ], "v": "<0.11.2" } ], "telegram-stats-bot": [ { "advisory": "Telegram-stats-bot 0.3.1 updates its dependency 'cryptography' to v3.3.1 to include a security fix.", "cve": "CVE-2020-25659", "id": "pyup.io-39382", "more_info_path": "/vulnerabilities/CVE-2020-25659/39382", "specs": [ "<0.3.1" ], "v": "<0.3.1" } ], "telemeta": [ { "advisory": "telemeta before 1.4.31 has a undisclosed security vulnerability in TELEMETA_EXPORT_CACHE_DIR.", "cve": "PVE-2021-26156", "id": "pyup.io-26156", "more_info_path": "/vulnerabilities/PVE-2021-26156/26156", "specs": [ "<1.4.31" ], "v": "<1.4.31" } ], "telemeter": [ { "advisory": "Telemeter version 3.0.4 updates its dependency \"Pydantic\" to v1.7.4 include a security fix.", "cve": "CVE-2021-29510", "id": "pyup.io-41853", "more_info_path": "/vulnerabilities/CVE-2021-29510/41853", "specs": [ "<3.0.4" ], "v": "<3.0.4" } ], "telepay": [ { "advisory": "Telepay 1.0.0 updates its dependency 'httpx' to v0.23.0 to include a security fix.", "cve": "CVE-2021-41945", "id": "pyup.io-49378", "more_info_path": "/vulnerabilities/CVE-2021-41945/49378", "specs": [ "<1.0.0" ], "v": "<1.0.0" } ], "teleserver": [ { "advisory": "Teleserver 2.2.0 increases the security by implementing better user verification. Now there are three ways of accessing teleserver: with GUI credentials, with service principal generated from system tab or with temporary token created via /login route of API.", "cve": "PVE-2021-38021", "id": "pyup.io-38021", "more_info_path": "/vulnerabilities/PVE-2021-38021/38021", "specs": [ "<2.2.0" ], "v": "<2.2.0" } ], "telnet": [ { "advisory": "telnet is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/", "cve": "PVE-2021-34985", "id": "pyup.io-34985", "more_info_path": "/vulnerabilities/PVE-2021-34985/34985", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "telnservrr": [ { "advisory": "Telnservrr is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html", "cve": "PVE-2023-52905", "id": "pyup.io-52905", "more_info_path": "/vulnerabilities/PVE-2023-52905/52905", "specs": [ ">0" ], "v": ">0" } ], "templated-dictionary": [ { "advisory": "Templated-dictionary contains a vulnerability wherein an attacker could potentially exploit privilege escalation, enabling the execution of arbitrary code with root user privileges. This weakness stems from the absence of proper sandboxing during the expansion and execution of Jinja2 templates, which may be included in certain configuration parameters. While the Mock documentation advises treating users added to the mock group as privileged, certain build systems invoking mock on behalf of users might inadvertently permit less privileged users to define configuration tags. These tags could then be passed as parameters to mock during execution, potentially leading to the utilization of Jinja2 templates for remote privilege escalation and the execution of arbitrary code as the root user on the build server.", "cve": "CVE-2023-6395", "id": "pyup.io-65397", "more_info_path": "/vulnerabilities/CVE-2023-6395/65397", "specs": [ ">=0" ], "v": ">=0" } ], "temporai": [ { "advisory": "A vulnerability classified as critical was found in van_der_Schaar LAB TemporAI 0.0.3. Affected by this vulnerability is the function load_from_file of the component PKL File Handler. The manipulation leads to deserialization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-252181 was assigned to this vulnerability. NOTE: The vendor was contacted early and confirmed immediately the existence of the issue.", "cve": "CVE-2024-0936", "id": "pyup.io-66733", "more_info_path": "/vulnerabilities/CVE-2024-0936/66733", "specs": [ "<=0.0.3" ], "v": "<=0.0.3" } ], "temporalio": [ { "advisory": "Temporalio updates to tonic v0.12.3 to Address CVE-2024-47609.", "cve": "CVE-2024-47609", "id": "pyup.io-74737", "more_info_path": "/vulnerabilities/CVE-2024-47609/74737", "specs": [ "<1.9.0" ], "v": "<1.9.0" } ], "tenable-jira-cloud": [ { "advisory": "Tenable for Jira Cloud is an open source project designed to pull Tenable.io vulnerability data, then generate Jira Tasks and sub-tasks based on the vulnerabilities' current state. It published in pypi as \"tenable-jira-cloud\". In tenable-jira-cloud before version 1.1.21, it is possible to run arbitrary commands through the yaml.load() method. This could allow an attacker with local access to the host to run arbitrary code by running the application with a specially crafted YAML configuration file. This is fixed in version 1.1.21 by using yaml.safe_load() instead of yaml.load().", "cve": "CVE-2021-21371", "id": "pyup.io-42301", "more_info_path": "/vulnerabilities/CVE-2021-21371/42301", "specs": [ "<1.1.21" ], "v": "<1.1.21" } ], "tendenci": [ { "advisory": "Tendenci 11.0.1 patches a security hole in payments that could potentially expose user data.", "cve": "PVE-2021-38510", "id": "pyup.io-38510", "more_info_path": "/vulnerabilities/PVE-2021-38510/38510", "specs": [ "<11.0.1" ], "v": "<11.0.1" }, { "advisory": "Tendenci 11.0.4 updates its requirements.txt to require django >=1.11.16 because there are vulnerabilities in Django 1.11.x before 1.11.15.", "cve": "CVE-2018-7536", "id": "pyup.io-49768", "more_info_path": "/vulnerabilities/CVE-2018-7536/49768", "specs": [ "<11.0.4" ], "v": "<11.0.4" }, { "advisory": "Tendenci 11.0.4 updates its requirements.txt to require django >=1.11.16 because there are vulnerabilities in Django 1.11.x before 1.11.15.", "cve": "CVE-2018-7537", "id": "pyup.io-49769", "more_info_path": "/vulnerabilities/CVE-2018-7537/49769", "specs": [ "<11.0.4" ], "v": "<11.0.4" }, { "advisory": "Tendenci 11.0.4 updates its requirements.txt to require django >=1.11.16 because there are vulnerabilities in Django 1.11.x before 1.11.15.", "cve": "CVE-2018-6188", "id": "pyup.io-49767", "more_info_path": "/vulnerabilities/CVE-2018-6188/49767", "specs": [ "<11.0.4" ], "v": "<11.0.4" }, { "advisory": "Tendenci 11.0.4 updates its requirements.txt to require django >=1.11.16 because there are vulnerabilities in Django 1.11.x before 1.11.15.", "cve": "CVE-2017-12794", "id": "pyup.io-38940", "more_info_path": "/vulnerabilities/CVE-2017-12794/38940", "specs": [ "<11.0.4" ], "v": "<11.0.4" }, { "advisory": "Tendenci 11.0.4 updates its requirements.txt to require django >=1.11.16 because there are vulnerabilities in Django 1.11.x before 1.11.15.", "cve": "CVE-2018-14574", "id": "pyup.io-49770", "more_info_path": "/vulnerabilities/CVE-2018-14574/49770", "specs": [ "<11.0.4" ], "v": "<11.0.4" }, { "advisory": "Tendenci 11.1.1 updates Django version to 1.11.20 to include a security fix.", "cve": "CVE-2019-6975", "id": "pyup.io-36888", "more_info_path": "/vulnerabilities/CVE-2019-6975/36888", "specs": [ "<11.1.1" ], "v": "<11.1.1" }, { "advisory": "Tendenci 11.2.12 strips null bytes to avoid null byte injection attacks.", "cve": "PVE-2021-37350", "id": "pyup.io-37350", "more_info_path": "/vulnerabilities/PVE-2021-37350/37350", "specs": [ "<11.2.12" ], "v": "<11.2.12" }, { "advisory": "Tendenci 11.2.8 upgrades its dependency 'bootstrap' from 3.3.1 to 3.4.1. There are several XSS vulnerabilities in versions lower than 3.4.1.", "cve": "CVE-2019-8331", "id": "pyup.io-37150", "more_info_path": "/vulnerabilities/CVE-2019-8331/37150", "specs": [ "<11.2.8" ], "v": "<11.2.8" }, { "advisory": "Tendenci 11.2.8 upgrades its dependency 'bootstrap' from 3.3.1 to 3.4.1. There are several XSS vulnerabilities in versions lower than 3.4.1.", "cve": "CVE-2018-20677", "id": "pyup.io-42992", "more_info_path": "/vulnerabilities/CVE-2018-20677/42992", "specs": [ "<11.2.8" ], "v": "<11.2.8" }, { "advisory": "Tendenci 11.2.8 upgrades its dependency 'bootstrap' from 3.3.1 to 3.4.1. There are several XSS vulnerabilities in versions lower than 3.4.1.", "cve": "CVE-2018-14040", "id": "pyup.io-42994", "more_info_path": "/vulnerabilities/CVE-2018-14040/42994", "specs": [ "<11.2.8" ], "v": "<11.2.8" }, { "advisory": "Tendenci 11.2.8 upgrades its dependency 'bootstrap' from 3.3.1 to 3.4.1. There are several XSS vulnerabilities in versions lower than 3.4.1.", "cve": "CVE-2016-10735", "id": "pyup.io-42996", "more_info_path": "/vulnerabilities/CVE-2016-10735/42996", "specs": [ "<11.2.8" ], "v": "<11.2.8" }, { "advisory": "Tendenci 11.2.8 upgrades its dependency 'bootstrap' from 3.3.1 to 3.4.1. There are several XSS vulnerabilities in versions lower than 3.4.1.", "cve": "CVE-2018-20676", "id": "pyup.io-42993", "more_info_path": "/vulnerabilities/CVE-2018-20676/42993", "specs": [ "<11.2.8" ], "v": "<11.2.8" }, { "advisory": "Tendenci 11.2.8 upgrades its dependency 'bootstrap' from 3.3.1 to 3.4.1. There are several XSS vulnerabilities in versions lower than 3.4.1.", "cve": "CVE-2018-14042", "id": "pyup.io-42995", "more_info_path": "/vulnerabilities/CVE-2018-14042/42995", "specs": [ "<11.2.8" ], "v": "<11.2.8" }, { "advisory": "Tendenci 11.4.7 prevents unauthorized use of renewal URLs.", "cve": "PVE-2021-38509", "id": "pyup.io-38509", "more_info_path": "/vulnerabilities/PVE-2021-38509/38509", "specs": [ "<11.4.7" ], "v": "<11.4.7" }, { "advisory": "Tendenci 11.4.9 handles the case in event registrations when management forms are tampered maliciously.", "cve": "PVE-2021-38939", "id": "pyup.io-38939", "more_info_path": "/vulnerabilities/PVE-2021-38939/38939", "specs": [ "<11.4.9" ], "v": "<11.4.9" }, { "advisory": "Tendenci 12.0.5 removes .doc and .xls from the allowed file upload extensions for security reasons. Besides the general threats, determining the mime type for the .doc and .xls files (generated by old MS Word and MS Excel) requires feeding the entire file content due to their format not complying with the standard.", "cve": "PVE-2021-38274", "id": "pyup.io-38274", "more_info_path": "/vulnerabilities/PVE-2021-38274/38274", "specs": [ "<12.0.5" ], "v": "<12.0.5" }, { "advisory": "Tendenci 12.2 updates Django version to 2.2.16, which fixes two security issues and two data loss bugs in version 2.2.15.", "cve": "CVE-2020-24584", "id": "pyup.io-42477", "more_info_path": "/vulnerabilities/CVE-2020-24584/42477", "specs": [ "<12.2" ], "v": "<12.2" }, { "advisory": "Tendenci 12.2 updates Django version to 2.2.16, which fixes two security issues and two data loss bugs in version 2.2.15.", "cve": "CVE-2020-24583", "id": "pyup.io-38767", "more_info_path": "/vulnerabilities/CVE-2020-24583/38767", "specs": [ "<12.2" ], "v": "<12.2" }, { "advisory": "Tendenci 12.3.1 fixes a HTML Injection vulnerability in the several parameters of the admin backend.\r\nhttps://github.com/tendenci/tendenci/issues/918", "cve": "PVE-2021-38970", "id": "pyup.io-38970", "more_info_path": "/vulnerabilities/PVE-2021-38970/38970", "specs": [ "<12.3.1" ], "v": "<12.3.1" }, { "advisory": "Tendenci 12.3.1 fixes a XSS vulnerability in the the admin backend.\r\nhttps://github.com/tendenci/tendenci/issues/918", "cve": "PVE-2021-42738", "id": "pyup.io-42738", "more_info_path": "/vulnerabilities/PVE-2021-42738/42738", "specs": [ "<12.3.1" ], "v": "<12.3.1" }, { "advisory": "Tendenci 12.3.2 updates exports to prevent potential CSV injection in the exported CSV files.\r\nhttps://github.com/tendenci/tendenci/issues/919", "cve": "PVE-2021-38976", "id": "pyup.io-38976", "more_info_path": "/vulnerabilities/PVE-2021-38976/38976", "specs": [ "<12.3.2" ], "v": "<12.3.2" }, { "advisory": "Tendenci 12.4.13 upgrades its dependency 'jQuery' from 3.4.1 to 3.6.0 to fix a XSS vulnerability.", "cve": "CVE-2020-11022", "id": "pyup.io-40826", "more_info_path": "/vulnerabilities/CVE-2020-11022/40826", "specs": [ "<12.4.13" ], "v": "<12.4.13" }, { "advisory": "Tendenci 12.4.13 upgrades its dependency 'jQuery' from 3.4.1 to 3.6.0 to fix a XSS vulnerability in versions <3.5.0.", "cve": "CVE-2020-11023", "id": "pyup.io-42991", "more_info_path": "/vulnerabilities/CVE-2020-11023/42991", "specs": [ "<12.4.13" ], "v": "<12.4.13" }, { "advisory": "Tendenci 12.4.8 tightens the security check for the password change page.\r\nhttps://github.com/tendenci/tendenci/commit/4101194640b5d5dc99c01efdfa80c34bdba2b158", "cve": "PVE-2021-40133", "id": "pyup.io-43486", "more_info_path": "/vulnerabilities/PVE-2021-40133/43486", "specs": [ "<12.4.8" ], "v": "<12.4.8" }, { "advisory": "Tendenci 12.4.8 updates its dependency 'Pillow' to v8.1.2 to include security fixes.", "cve": "CVE-2021-27923", "id": "pyup.io-43490", "more_info_path": "/vulnerabilities/CVE-2021-27923/43490", "specs": [ "<12.4.8" ], "v": "<12.4.8" }, { "advisory": "Tendenci 12.4.8 updates its dependency 'Pillow' to v8.1.2 to include security fixes.", "cve": "CVE-2021-25292", "id": "pyup.io-43492", "more_info_path": "/vulnerabilities/CVE-2021-25292/43492", "specs": [ "<12.4.8" ], "v": "<12.4.8" }, { "advisory": "Tendenci 12.4.8 updates its dependency 'Pillow' to v8.1.2 to include security fixes.", "cve": "CVE-2021-27922", "id": "pyup.io-43488", "more_info_path": "/vulnerabilities/CVE-2021-27922/43488", "specs": [ "<12.4.8" ], "v": "<12.4.8" }, { "advisory": "Tendenci 12.4.8 updates its dependency 'Pillow' to v8.1.2 to include security fixes.", "cve": "CVE-2021-27921", "id": "pyup.io-43489", "more_info_path": "/vulnerabilities/CVE-2021-27921/43489", "specs": [ "<12.4.8" ], "v": "<12.4.8" }, { "advisory": "Tendenci 12.4.8 updates its dependency 'Pillow' to v8.1.2 to include security fixes.", "cve": "CVE-2021-25291", "id": "pyup.io-43491", "more_info_path": "/vulnerabilities/CVE-2021-25291/43491", "specs": [ "<12.4.8" ], "v": "<12.4.8" }, { "advisory": "Tendenci 12.4.8 updates its dependency 'Pillow' to v8.1.2 to include security fixes.", "cve": "CVE-2021-25289", "id": "pyup.io-40133", "more_info_path": "/vulnerabilities/CVE-2021-25289/40133", "specs": [ "<12.4.8" ], "v": "<12.4.8" }, { "advisory": "Tendenci 12.4.8 updates its dependency 'Pillow' to v8.1.2 to include security fixes.", "cve": "CVE-2021-25290", "id": "pyup.io-43487", "more_info_path": "/vulnerabilities/CVE-2021-25290/43487", "specs": [ "<12.4.8" ], "v": "<12.4.8" }, { "advisory": "Tendenci 12.4.8 updates its dependency 'Pillow' to v8.1.2 to include security fixes.", "cve": "CVE-2021-25293", "id": "pyup.io-43493", "more_info_path": "/vulnerabilities/CVE-2021-25293/43493", "specs": [ "<12.4.8" ], "v": "<12.4.8" }, { "advisory": "Affected versions of the tendenci package are vulnerable to Deserialization of Untrusted Data due to unsafe use of Python pickle deserialization on user-influenced report data. In tendenci/apps/helpdesk/views/staff.py, the Helpdesk /reports/ functionality invokes the run_report() code path that still calls pickle.loads() on attacker-controllable input, representing an incomplete patch of the earlier ticket_list() fix that switched to JSON deserialization. An authenticated attacker with the Staff security level (is_staff) can submit a malicious pickle payload (when the Helpdesk module is enabled) to execute arbitrary code in the context of the Tendenci server process user, leading to Remote Code Execution with impact constrained to that account\u2019s permissions.", "cve": "CVE-2026-23946", "id": "pyup.io-84896", "more_info_path": "/vulnerabilities/CVE-2026-23946/84896", "specs": [ "<15.3.12" ], "v": "<15.3.12" }, { "advisory": "Tendenci 7.4.0 disables GZipMiddleware to prevent BREACH attacks and prevents fraudulent simultaneous reuse of PayPal transactions.", "cve": "PVE-2021-35055", "id": "pyup.io-35055", "more_info_path": "/vulnerabilities/PVE-2021-35055/35055", "specs": [ "<7.4.0" ], "v": "<7.4.0" }, { "advisory": "Tendenci 12.0.10 allows unrestricted deserialization in apps\\helpdesk\\views\\staff.py.", "cve": "CVE-2020-14942", "id": "pyup.io-42276", "more_info_path": "/vulnerabilities/CVE-2020-14942/42276", "specs": [ "==12.0.10" ], "v": "==12.0.10" } ], "teneto": [ { "advisory": "In teneto 0.4.5, save_tenetobids_snapshot to export current teneto settings. save_to_pickle (and corresponding load function) have been removed as they are not secure.", "cve": "PVE-2021-37550", "id": "pyup.io-37550", "more_info_path": "/vulnerabilities/PVE-2021-37550/37550", "specs": [ "<0.4.5" ], "v": "<0.4.5" } ], "tenso": [ { "advisory": "Affected versions of the tenso package are vulnerable to denial-of-service (resource exhaustion) due to missing bounds checks on tensor shape metadata during deserialization.", "cve": "PVE-2025-83107", "id": "pyup.io-83107", "more_info_path": "/vulnerabilities/PVE-2025-83107/83107", "specs": [ "<0.9.0" ], "v": "<0.9.0" } ], "tensorboard": [ { "advisory": "Tensorboard 1.9.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/tensorflow/tensorboard/pull/1235", "cve": "PVE-2023-60278", "id": "pyup.io-60278", "more_info_path": "/vulnerabilities/PVE-2023-60278/60278", "specs": [ "<1.9.0" ], "v": "<1.9.0" } ], "tensorflow": [ { "advisory": "Tensorflow 1.10.0 defaults to use SSL when connecting to a server with tf.Session (except running on Windows).\r\nhttps://github.com/tensorflow/tensorflow/commit/ba9422a8adba18fc97cc1923002b7db8ca63dcfe", "cve": "PVE-2021-36375", "id": "pyup.io-36375", "more_info_path": "/vulnerabilities/PVE-2021-36375/36375", "specs": [ "<1.10.0" ], "v": "<1.10.0" }, { "advisory": "NULL pointer dereference in Google TensorFlow before 1.12.2 could cause a denial of service via an invalid GIF file. See CVE-2019-9635.", "cve": "CVE-2019-9635", "id": "pyup.io-40793", "more_info_path": "/vulnerabilities/CVE-2019-9635/40793", "specs": [ "<1.12.2" ], "v": "<1.12.2" }, { "advisory": "Tensorflow 1.15 includes a fix for CVE-2019-16778: In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-844w-j86r-4x2j\r\nhttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2019-002.md\r\nhttps://github.com/tensorflow/tensorflow/commit/db4f9717c41bccc3ce10099ab61996b246099892", "cve": "CVE-2019-16778", "id": "pyup.io-40792", "more_info_path": "/vulnerabilities/CVE-2019-16778/40792", "specs": [ "<1.15" ], "v": "<1.15" }, { "advisory": "Tensorflow 1.15.0rc0 includes a fix for a potential security vulnerability where decoding variant tensors from proto could result in heap out of bounds memory access.\r\nhttps://github.com/tensorflow/tensorflow/issues/37701", "cve": "PVE-2021-37524", "id": "pyup.io-37524", "more_info_path": "/vulnerabilities/PVE-2021-37524/37524", "specs": [ "<1.15.0rc0" ], "v": "<1.15.0rc0" }, { "advisory": "Tensorflow versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"Apache Spark\" to handle CVE-2019-10099.", "cve": "CVE-2019-10099", "id": "pyup.io-39824", "more_info_path": "/vulnerabilities/CVE-2019-10099/39824", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"SQLite\" to handle CVE-2019-19645.", "cve": "CVE-2019-19645", "id": "pyup.io-39819", "more_info_path": "/vulnerabilities/CVE-2019-19645/39819", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"Apache Spark\" to handle CVE-2018-17190.", "cve": "CVE-2018-17190", "id": "pyup.io-39825", "more_info_path": "/vulnerabilities/CVE-2018-17190/39825", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"SQLite3\" to handle CVE-2019-19244.", "cve": "CVE-2019-19244", "id": "pyup.io-39818", "more_info_path": "/vulnerabilities/CVE-2019-19244/39818", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow versions 1.15.3, 2.0.2 and 2.1.1 update its dependency \"Apache Spark\" to handle CVE-2018-11770.", "cve": "CVE-2018-11770", "id": "pyup.io-39826", "more_info_path": "/vulnerabilities/CVE-2018-11770/39826", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow versions 1.15.3, 2.0.2 and 2.1.1 update its dependency \"SQLite3\" to handle CVE-2019-19880.", "cve": "CVE-2019-19880", "id": "pyup.io-38460", "more_info_path": "/vulnerabilities/CVE-2019-19880/38460", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2019-13960.", "cve": "CVE-2019-13960", "id": "pyup.io-39823", "more_info_path": "/vulnerabilities/CVE-2019-13960/39823", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2018-19664.", "cve": "CVE-2018-19664", "id": "pyup.io-39821", "more_info_path": "/vulnerabilities/CVE-2018-19664/39821", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2018-20330.", "cve": "CVE-2018-20330", "id": "pyup.io-39822", "more_info_path": "/vulnerabilities/CVE-2018-20330/39822", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15208: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a \"DCHECK\" which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue was patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d", "cve": "CVE-2020-15208", "id": "pyup.io-39937", "more_info_path": "/vulnerabilities/CVE-2020-15208/39937", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15209: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a \"nullptr\" buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with \"nullptr\". However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue was patched in commit 0b5662bc.", "cve": "CVE-2020-15209", "id": "pyup.io-39960", "more_info_path": "/vulnerabilities/CVE-2020-15209/39960", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15203: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the 'fill' argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a 'printf' call is constructed. This may result in segmentation fault.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79", "cve": "CVE-2020-15203", "id": "pyup.io-39942", "more_info_path": "/vulnerabilities/CVE-2020-15203/39942", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15195: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of 'SparseFillEmptyRowsGrad' uses a double indexing pattern. It is possible for 'reverse_index_map(i)' to be an index outside of bounds of 'grad_values', thus resulting in a heap buffer overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-63xm-rx5p-xvqr", "cve": "CVE-2020-15195", "id": "pyup.io-39944", "more_info_path": "/vulnerabilities/CVE-2020-15195/39944", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15202: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'Shard' API in TensorFlow expects the last argument to be a function taking two 'int64' (i.e., 'long long') arguments. However, there are several places in TensorFlow where a lambda taking 'int' or 'int32' arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4", "cve": "CVE-2020-15202", "id": "pyup.io-39943", "more_info_path": "/vulnerabilities/CVE-2020-15202/39943", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15204: In eager mode, TensorFlow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling \"tf.raw_ops.GetSessionHandle\" or \"tf.raw_ops.GetSessionHandleV2\" results in a null pointer dereference In linked snippet, in eager mode, \"ctx->session_state()\" returns \"nullptr\". Since code immediately dereferences this, we get a segmentation fault. The issue was patched in commit 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1", "cve": "CVE-2020-15204", "id": "pyup.io-39941", "more_info_path": "/vulnerabilities/CVE-2020-15204/39941", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15207: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses 'ResolveAxis' to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the 'DCHECK' does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34", "cve": "CVE-2020-15207", "id": "pyup.io-39938", "more_info_path": "/vulnerabilities/CVE-2020-15207/39938", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15205: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'data_splits' argument of 'tf.raw_ops.StringNGrams' lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after 'ee ff' are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46", "cve": "CVE-2020-15205", "id": "pyup.io-39940", "more_info_path": "/vulnerabilities/CVE-2020-15205/39940", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15190: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the \"tf.raw_ops.Switch\" operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is \"nullptr\", hence we are binding a reference to \"nullptr\". This is undefined behavior and reported as an error if compiling with \"-fsanitize=null\". In this case, this results in a segmentation fault The issue was patched in commit da8558533d925694483d2c136a9220d6d49d843c\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4g9f-63rx-5cw4", "cve": "CVE-2020-15190", "id": "pyup.io-38813", "more_info_path": "/vulnerabilities/CVE-2020-15190/38813", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15206: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's \"SavedModel\" protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using \"tensorflow-serving\" or other inference-as-a-service installments. Fixed were added in commits f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d. However, this was not enough, as #41097 reported a different failure mode. The issue was finally patched in commit df095206f25471e864a8e63a0f1caef53a0e3a6", "cve": "CVE-2020-15206", "id": "pyup.io-39939", "more_info_path": "/vulnerabilities/CVE-2020-15206/39939", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15211: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor. However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative \"-1\" value as index for these tensors. This results in special casing during validation at model loading time. Unfortunately, this means that the \"-1\" index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays. This results in both read and write gadgets, albeit very limited in scope. The issue was patched in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83). A potential workaround would be to add a custom \"Verifier\" to the model loading code to ensure that only operators which accept optional inputs use the \"-1\" special value and only for the tensors that they expect to be optional. Since this allow-list type approach is error-prone, it's advised upgrading to the patched code.", "cve": "CVE-2020-15211", "id": "pyup.io-39958", "more_info_path": "/vulnerabilities/CVE-2020-15211/39958", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11655.", "cve": "CVE-2020-11655", "id": "pyup.io-39932", "more_info_path": "/vulnerabilities/CVE-2020-11655/39932", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13871.", "cve": "CVE-2020-13871", "id": "pyup.io-39899", "more_info_path": "/vulnerabilities/CVE-2020-13871/39899", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11656.", "cve": "CVE-2020-11656", "id": "pyup.io-39904", "more_info_path": "/vulnerabilities/CVE-2020-11656/39904", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13435.", "cve": "CVE-2020-13435", "id": "pyup.io-39902", "more_info_path": "/vulnerabilities/CVE-2020-13435/39902", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-9327.", "cve": "CVE-2020-9327", "id": "pyup.io-39906", "more_info_path": "/vulnerabilities/CVE-2020-9327/39906", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13631.", "cve": "CVE-2020-13631", "id": "pyup.io-39900", "more_info_path": "/vulnerabilities/CVE-2020-13631/39900", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13630.", "cve": "CVE-2020-13630", "id": "pyup.io-39901", "more_info_path": "/vulnerabilities/CVE-2020-13630/39901", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13434.", "cve": "CVE-2020-13434", "id": "pyup.io-39903", "more_info_path": "/vulnerabilities/CVE-2020-13434/39903", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15210: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x9j7-x98r-r4w2", "cve": "CVE-2020-15210", "id": "pyup.io-39983", "more_info_path": "/vulnerabilities/CVE-2020-15210/39983", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow 2.4.0 includes a fix for CVE-2020-15194: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments. Although `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\"", "cve": "CVE-2020-15194", "id": "pyup.io-39869", "more_info_path": "/vulnerabilities/CVE-2020-15194/39869", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 updates its dependency \"Libjpeg-turbo\" to handle CVE-2020-13790.", "cve": "CVE-2020-13790", "id": "pyup.io-39726", "more_info_path": "/vulnerabilities/CVE-2020-13790/39726", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency \"PCRE\" to fix CVE-2019-20838.", "cve": "CVE-2019-20838", "id": "pyup.io-39406", "more_info_path": "/vulnerabilities/CVE-2019-20838/39406", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow versions 1.15.5, 2.0.4, 2.1.3, 2.2.2 and 2.3.2 update its dependency \"PCRE\" to handle CVE-2020-14155.", "cve": "CVE-2020-14155", "id": "pyup.io-39725", "more_info_path": "/vulnerabilities/CVE-2020-14155/39725", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency 'Junit4' to v4.13.1 to include a security fix.", "cve": "CVE-2020-15250", "id": "pyup.io-39724", "more_info_path": "/vulnerabilities/CVE-2020-15250/39724", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26267: In affected versions, the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes.", "cve": "CVE-2020-26267", "id": "pyup.io-39722", "more_info_path": "/vulnerabilities/CVE-2020-26267/39722", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "TensorFlow versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0 includes a fix for CVE-2020-26266: In affected versions and under certain cases a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers filled with the default value of the type but forgetting to default initialize the quantized floating point types in Eigen.", "cve": "CVE-2020-26266", "id": "pyup.io-39408", "more_info_path": "/vulnerabilities/CVE-2020-26266/39408", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26268: In affected versions, the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden.", "cve": "CVE-2020-26268", "id": "pyup.io-39265", "more_info_path": "/vulnerabilities/CVE-2020-26268/39265", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26270: In affected versions, running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.", "cve": "CVE-2020-26270", "id": "pyup.io-39720", "more_info_path": "/vulnerabilities/CVE-2020-26270/39720", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26271: In affected versions, under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library.", "cve": "CVE-2020-26271", "id": "pyup.io-39719", "more_info_path": "/vulnerabilities/CVE-2020-26271/39719", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent. See CVE-2018-7576.", "cve": "CVE-2018-7576", "id": "pyup.io-40789", "more_info_path": "/vulnerabilities/CVE-2018-7576/40789", "specs": [ "<1.6.0a1" ], "v": "<1.6.0a1" }, { "advisory": "TensorFlow before 1.7.0 has an integer overflow that causes an out-of-bounds read, possibly causing disclosure of the contents of process memory. This occurs in the DecodeBmp feature of the BMP decoder in core/kernels/decode_bmp_op.cc. See CVE-2018-21233.", "cve": "CVE-2018-21233", "id": "pyup.io-40787", "more_info_path": "/vulnerabilities/CVE-2018-21233/40787", "specs": [ "<1.7.0" ], "v": "<1.7.0" }, { "advisory": "Google TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability. The type of exploitation is context-dependent. See CVE-2018-7575.", "cve": "CVE-2018-7575", "id": "pyup.io-40788", "more_info_path": "/vulnerabilities/CVE-2018-7575/40788", "specs": [ "<1.7.0a1" ], "v": "<1.7.0a1" }, { "advisory": "Invalid memory access and/or a heap buffer overflow in the TensorFlow XLA compiler in Google TensorFlow before 1.7.1 could cause a crash or read from other parts of process memory via a crafted configuration file. See CVE-2018-10055.", "cve": "CVE-2018-10055", "id": "pyup.io-40786", "more_info_path": "/vulnerabilities/CVE-2018-10055/40786", "specs": [ "<1.7.1" ], "v": "<1.7.1" }, { "advisory": "Memcpy parameter overlap in Google Snappy library 1.1.4, as used in Google TensorFlow before 1.7.1, could result in a crash or read from other parts of process memory. See CVE-2018-7577.", "cve": "CVE-2018-7577", "id": "pyup.io-40790", "more_info_path": "/vulnerabilities/CVE-2018-7577/40790", "specs": [ "<1.7.1" ], "v": "<1.7.1" }, { "advisory": "Tensorflow 1.7.1 addresses a vulnerability where a specially crafted configuration file, if passed into the TensorFlow XLA compiler, could lead to invalid memory access or a heap buffer overflow.\r\nhttps://github.com/tensorflow/tensorflow/compare/v1.7.0...v1.7.1#diff-f78e350e35c0a0cb564854fc5af8e02e019273199c1a331a117219cfe531f957", "cve": "PVE-2024-64297", "id": "pyup.io-64297", "more_info_path": "/vulnerabilities/PVE-2024-64297/64297", "specs": [ "<1.7.1" ], "v": "<1.7.1" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25668: Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gw97-ff7c-9v96", "cve": "CVE-2023-25668", "id": "pyup.io-53854", "more_info_path": "/vulnerabilities/CVE-2023-25668/53854", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25676: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.ParallelConcat' segfaults with a nullptr dereference when given a parameter 'shape' with rank that is not greater than zero.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6wfh-89q8-44jq", "cve": "CVE-2023-25676", "id": "pyup.io-53862", "more_info_path": "/vulnerabilities/CVE-2023-25676/53862", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25669: Prior to versions 2.12.0 and 2.11.1, if the stride and window size are not positive for 'tf.raw_ops.AvgPoolGrad', it can give a floating point exception.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rcf8-g8jv-vg6p", "cve": "CVE-2023-25669", "id": "pyup.io-53855", "more_info_path": "/vulnerabilities/CVE-2023-25669/53855", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25662: Versions prior to 2.12.0 and 2.11.1 are vulnerable to integer overflow in EditDistance.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7jvm-xxmr-v5cw", "cve": "CVE-2023-25662", "id": "pyup.io-53848", "more_info_path": "/vulnerabilities/CVE-2023-25662/53848", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25659: Prior to versions 2.12.0 and 2.11.1, if the parameter 'indices' for 'DynamicStitch' does not match the shape of the parameter 'data', it can trigger an stack OOB read.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-93vr-9q9m-pj8p", "cve": "CVE-2023-25659", "id": "pyup.io-53846", "more_info_path": "/vulnerabilities/CVE-2023-25659/53846", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25658: Prior to versions 2.12.0 and 2.11.1, an out of bounds read is in GRUBlockCellGrad.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-68v3-g9cm-rmm6", "cve": "CVE-2023-25658", "id": "pyup.io-53845", "more_info_path": "/vulnerabilities/CVE-2023-25658/53845", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25675: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.Bincount' segfaults when given a parameter 'weights' that is neither the same shape as parameter 'arr' nor a length-0 tensor.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7x4v-9gxg-9hwj", "cve": "CVE-2023-25675", "id": "pyup.io-53861", "more_info_path": "/vulnerabilities/CVE-2023-25675/53861", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25674: Versions prior to 2.12.0 and 2.11.1 have a null pointer error in RandomShuffle with XLA enabled.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf97-q72m-7579", "cve": "CVE-2023-25674", "id": "pyup.io-53860", "more_info_path": "/vulnerabilities/CVE-2023-25674/53860", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25672: The function 'tf.raw_ops.LookupTableImportV2' cannot handle scalars in the 'values' parameter and gives an NPE. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25672", "id": "pyup.io-53858", "more_info_path": "/vulnerabilities/CVE-2023-25672/53858", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25665: Prior to versions 2.12.0 and 2.11.1, when 'SparseSparseMaximum' is given invalid sparse tensors as inputs, it can give a null pointer error.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-558h-mq8x-7q9g", "cve": "CVE-2023-25665", "id": "pyup.io-53851", "more_info_path": "/vulnerabilities/CVE-2023-25665/53851", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25673: Versions prior to 2.12.0 and 2.11.1 have a Floating Point Exception in TensorListSplit with XLA. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25673", "id": "pyup.io-53859", "more_info_path": "/vulnerabilities/CVE-2023-25673/53859", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25671: There is out-of-bounds access due to mismatched integer type sizes.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j5w9-hmfh-4cr6", "cve": "CVE-2023-25671", "id": "pyup.io-53857", "more_info_path": "/vulnerabilities/CVE-2023-25671/53857", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25661: In versions prior to 2.11.1 a malicious invalid input crashes a tensorflow model (Check Failed) and can be used to trigger a denial of service attack. A proof of concept can be constructed with the 'Convolution3DTranspose' function. This Convolution3DTranspose layer is a very common API in modern neural networks. The ML models containing such vulnerable components could be deployed in ML applications or as cloud services. This failure could be potentially used to trigger a denial of service attack on ML cloud services. An attacker must have privilege to provide input to a 'Convolution3DTranspose' call.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fxgc-95xx-grvq", "cve": "CVE-2023-25661", "id": "pyup.io-53903", "more_info_path": "/vulnerabilities/CVE-2023-25661/53903", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25667: Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when '2^31 <= num_frames * height * width * channels < 2^32', for example Full HD screencast of at least 346 frames.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqm2-gh8w-gr68", "cve": "CVE-2023-25667", "id": "pyup.io-53853", "more_info_path": "/vulnerabilities/CVE-2023-25667/53853", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25670: Versions prior to 2.12.0 and 2.11.1 have a null point error in QuantizedMatMulWithBiasAndDequantize with MKL enabled.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rq-hwc3-x77w", "cve": "CVE-2023-25670", "id": "pyup.io-53856", "more_info_path": "/vulnerabilities/CVE-2023-25670/53856", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25666: Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2", "cve": "CVE-2023-25666", "id": "pyup.io-53852", "more_info_path": "/vulnerabilities/CVE-2023-25666/53852", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25664: Prior to versions 2.12.0 and 2.11.1, there is a heap buffer overflow in TAvgPoolGrad.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hg6-5c2q-7rcr", "cve": "CVE-2023-25664", "id": "pyup.io-53850", "more_info_path": "/vulnerabilities/CVE-2023-25664/53850", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25660: Prior to versions 2.12.0 and 2.11.1, when the parameter 'summarize' of 'tf.raw_ops.Print' is zero, the new method 'SummarizeArray' will reference to a nullptr, leading to a seg fault.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qjqc-vqcf-5qvj", "cve": "CVE-2023-25660", "id": "pyup.io-53847", "more_info_path": "/vulnerabilities/CVE-2023-25660/53847", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-27579: Constructing a tflite model with a paramater 'filter_input_channel' of less than 1 gives a FPE.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5w96-866f-6rm8", "cve": "CVE-2023-27579", "id": "pyup.io-53864", "more_info_path": "/vulnerabilities/CVE-2023-27579/53864", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25801: Prior to versions 2.12.0 and 2.11.1, 'nn_ops.fractional_avg_pool_v2' and 'nn_ops.fractional_max_pool_v2' require the first and fourth elements of their parameter 'pooling_ratio' to be equal to 1.0, as pooling on batch and channel dimensions is not supported.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f49c-87jh-g47q", "cve": "CVE-2023-25801", "id": "pyup.io-53863", "more_info_path": "/vulnerabilities/CVE-2023-25801/53863", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow 2.11.1 and 2.12.0 include a fix for CVE-2023-25663: Prior to versions 2.12.0 and 2.11.1, when 'ctx->step_containter()' is a null ptr, the Lookup function will be executed with a null pointer.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-64jg-wjww-7c5w", "cve": "CVE-2023-25663", "id": "pyup.io-53849", "more_info_path": "/vulnerabilities/CVE-2023-25663/53849", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Integer Overflow. array_ops.upper_bound' causes a segfault when not given a rank 2 tensor. The flaw was fixed in May 30, 2023, but the CVE was published in July 30, 2024. It was noticed unpublished by the Safety CLI Cyber Security team.", "cve": "CVE-2023-33976", "id": "pyup.io-72424", "more_info_path": "/vulnerabilities/CVE-2023-33976/72424", "specs": [ "<2.12.1", ">=2.13.0rc0,<2.13.0" ], "v": "<2.12.1,>=2.13.0rc0,<2.13.0" }, { "advisory": "TensorFlow updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38546.", "cve": "CVE-2023-38546", "id": "pyup.io-72611", "more_info_path": "/vulnerabilities/CVE-2023-38546/72611", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "TensorFlow 2.14.1 updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38545.", "cve": "CVE-2023-38545", "id": "pyup.io-72612", "more_info_path": "/vulnerabilities/CVE-2023-38545/72612", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "TensorFlow 2.4.0 includes a fix for CVE-2020-15265: In Tensorflow before version 2.4.0, an attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`. This results in accessing a dimension outside the rank of the input tensor in the C++ kernel implementation. However, dim_size only does a DCHECK to validate the argument and then uses it to access the corresponding element of an array. Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.", "cve": "CVE-2020-15265", "id": "pyup.io-40794", "more_info_path": "/vulnerabilities/CVE-2020-15265/40794", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "TensorFlow 2.4.0 includes a fix for CVE-2020-15266: In Tensorflow before version 2.4.0, when the 'boxes' argument of 'tf.image.crop_and_resize' has a very large value, the CPU kernel implementation receives it as a C++ 'nan' floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault.\r\nhttps://github.com/tensorflow/tensorflow/issues/42129\r\nhttps://github.com/tensorflow/tensorflow/pull/42143/commits/3ade2efec2e90c6237de32a19680caaa3ebc2845\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xwhf-g6j5-j5gc", "cve": "CVE-2020-15266", "id": "pyup.io-40795", "more_info_path": "/vulnerabilities/CVE-2020-15266/40795", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41214: In affected versions, the shape inference code for 'tf.ragged.cross' has an undefined behavior due to binding a reference to 'nullptr'. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vwhq-49r4-gj9v\r\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41214", "id": "pyup.io-42461", "more_info_path": "/vulnerabilities/CVE-2021-41214/42461", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "TensorFlow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41225: In affected versions, TensorFlow's Grappler optimizer has a use of unitialized variable. If the 'train_nodes' vector (obtained from the saved model that gets optimized) does not contain a 'Dequeue' node, then 'dequeue_node' is left unitialized. The fix is also included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7r94-xv9v-63jw\r\nhttps://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3", "cve": "CVE-2021-41225", "id": "pyup.io-42472", "more_info_path": "/vulnerabilities/CVE-2021-41225/42472", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41213: In affected versions, the code behind 'tf.function' API can be made to deadlock when two 'tf.function' decorated Python functions are mutually recursive. This occurs due to using a non-reentrant 'Lock' Python object. Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive 'tf.function', although this is not a frequent scenario.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcf\r\nhttps://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7", "cve": "CVE-2021-41213", "id": "pyup.io-42460", "more_info_path": "/vulnerabilities/CVE-2021-41213/42460", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41200: In affected versions, if 'tf.summary.create_file_writer' is called with non-scalar arguments, code crashes due to a 'CHECK'-fail. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh8h-7j2j-qv4f", "cve": "CVE-2021-41200", "id": "pyup.io-42447", "more_info_path": "/vulnerabilities/CVE-2021-41200/42447", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41223: In affected versions, the implementation of 'FusedBatchNorm' kernels is vulnerable to a heap OOB access. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f54p-f6jp-4rhr\r\nhttps://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda", "cve": "CVE-2021-41223", "id": "pyup.io-42470", "more_info_path": "/vulnerabilities/CVE-2021-41223/42470", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41217: In affected versions, the process of building the control flow graph for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not. This occurs because the code assumes that the first node in the pairing (e.g., an 'Enter' node) always exists when encountering the second node (e.g., an 'Exit' node). When this is not the case, 'parent' is 'nullptr' so dereferencing it causes a crash. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5crj-c72x-m7gq\r\nhttps://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff", "cve": "CVE-2021-41217", "id": "pyup.io-42464", "more_info_path": "/vulnerabilities/CVE-2021-41217/42464", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41204: In affected versions, during TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-786j-5qwq-r36x\r\nhttps://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659", "cve": "CVE-2021-41204", "id": "pyup.io-42451", "more_info_path": "/vulnerabilities/CVE-2021-41204/42451", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41228: In affected versions, TensorFlow's 'saved_model_cli' tool is vulnerable to a code injection as it calls 'eval' on user supplied strings. This can be used by attackers to run arbitrary code on the plaform where the CLI tool runs. However, given that the tool is always run manually, the impact of this is not severe. The issue has been patched by adding a 'safe' flag which defaults to 'True' and an explicit warning for users.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3rcw-9p9x-582v\r\nhttps://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7", "cve": "CVE-2021-41228", "id": "pyup.io-42475", "more_info_path": "/vulnerabilities/CVE-2021-41228/42475", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41198: In affected versions, if 'tf.tile' is called with a large input argument, then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2p25-55c9-h58q", "cve": "CVE-2021-41198", "id": "pyup.io-42445", "more_info_path": "/vulnerabilities/CVE-2021-41198/42445", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41201: In affected versions, during execution, 'EinsumHelper::ParseEquation()' is supposed to set the flags in 'input_has_ellipsis' vector and '*output_has_ellipsis' boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to 'true' and never assigns 'false'. This results in unitialized variable access if callers assume that 'EinsumHelper::ParseEquation()' always sets these flags. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j86v-p27c-73fm\r\nhttps://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6", "cve": "CVE-2021-41201", "id": "pyup.io-42448", "more_info_path": "/vulnerabilities/CVE-2021-41201/42448", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41195: In affected versions, the implementation of 'tf.math.segment_*' operations results in a 'CHECK'-fail related abort (and denial of service) if a segment id in 'segment_ids' is large. This is similar to CVE-2021-29584 (and similar to other reported vulnerabilities in TensorFlow localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using 'AddDim'. However, if the number of elements in the tensor overflows an 'int64_t' value, 'AddDim' results in a 'CHECK' failure which provokes a 'std::abort'. Instead, code should use 'AddDimWithStatus'. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cq76-mxrc-vchh", "cve": "CVE-2021-41195", "id": "pyup.io-42442", "more_info_path": "/vulnerabilities/CVE-2021-41195/42442", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41205: In affected versions, the shape inference functions for the 'QuantizeAndDequantizeV*' operations can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rx-x2rw-pc6f\r\nhttps://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d", "cve": "CVE-2021-41205", "id": "pyup.io-42452", "more_info_path": "/vulnerabilities/CVE-2021-41205/42452", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "TensorFlow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41226: In affected versions, the implementation of 'SparseBinCount' is vulnerable to a heap OOB access. This is because of missing validation between the elements of the 'values' argument and the shape of the sparse output. The fix is also included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-374m-jm66-3vj8\r\nhttps://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba", "cve": "CVE-2021-41226", "id": "pyup.io-42473", "more_info_path": "/vulnerabilities/CVE-2021-41226/42473", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22925.", "cve": "CVE-2021-22925", "id": "pyup.io-43749", "more_info_path": "/vulnerabilities/CVE-2021-22925/43749", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22922.", "cve": "CVE-2021-22922", "id": "pyup.io-43613", "more_info_path": "/vulnerabilities/CVE-2021-22922/43613", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41202: In affected versions, while calculating the size of the output within the 'tf.range' kernel, there is a conditional statement of type 'int64 = condition ? int64 : double'. Due to C++ implicit conversion rules, both branches of the condition will be cast to 'double' and the result would be truncated before the assignment. This result in overflows. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xrqm-fpgr-6hhx", "cve": "CVE-2021-41202", "id": "pyup.io-42449", "more_info_path": "/vulnerabilities/CVE-2021-41202/42449", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41196: In affected versions, the Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative. This is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m539-j985-hcr8", "cve": "CVE-2021-41196", "id": "pyup.io-42443", "more_info_path": "/vulnerabilities/CVE-2021-41196/42443", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41218: In affected versions, the shape inference code for 'AllToAll' can be made to execute a division by 0. This occurs whenever the 'split_count' argument is 0. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9crf-c6qr-r273\r\nhttps://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc", "cve": "CVE-2021-41218", "id": "pyup.io-42465", "more_info_path": "/vulnerabilities/CVE-2021-41218/42465", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41219: In affected versions, the code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to 'nullptr'. This occurs whenever the dimensions of 'a' or 'b' are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, it should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4f99-p9c2-3j8x\r\nhttps://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae", "cve": "CVE-2021-41219", "id": "pyup.io-42466", "more_info_path": "/vulnerabilities/CVE-2021-41219/42466", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41210: In affected versions, the shape inference functions for 'SparseCountSparseOutput' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m342-ff57-4jcc\r\nhttps://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2", "cve": "CVE-2021-41210", "id": "pyup.io-42457", "more_info_path": "/vulnerabilities/CVE-2021-41210/42457", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41203: In affected versions, an attacker can trigger undefined behavior, integer overflows, segfaults and 'CHECK'-fail crashes if they can change saved checkpoints from outside of TensorFlow. This is because the checkpoints loading infrastructure is missing validation for invalid file formats.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7pxj-m4jf-r6h2", "cve": "CVE-2021-41203", "id": "pyup.io-42450", "more_info_path": "/vulnerabilities/CVE-2021-41203/42450", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22926.", "cve": "CVE-2021-22926", "id": "pyup.io-43750", "more_info_path": "/vulnerabilities/CVE-2021-22926/43750", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41224: In affected versions, the implementation of 'SparseFillEmptyRows' can be made to trigger a heap OOB access. This occurs whenever the size of 'indices' does not match the size of 'values'. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rg3m-hqc5-344v\r\nhttps://github.com/tensorflow/tensorflow/commit/67bfd9feeecfb3c61d80f0e46d89c170fbee682b", "cve": "CVE-2021-41224", "id": "pyup.io-42471", "more_info_path": "/vulnerabilities/CVE-2021-41224/42471", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41207: In affected versions, the implementation of 'ParallelConcat' misses some input validation and can produce a division by 0. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7v94-64hj-m82h\r\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41207", "id": "pyup.io-42454", "more_info_path": "/vulnerabilities/CVE-2021-41207/42454", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "TensorFlow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41227: In affected versions, the 'ImmutableConst' operation in TensorFlow can be tricked into reading arbitrary memory contents. This is because the 'tstring' TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype. The fix is also included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j8c8-67vp-6mx7\r\nhttps://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b\r\nhttps://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585", "cve": "CVE-2021-41227", "id": "pyup.io-42474", "more_info_path": "/vulnerabilities/CVE-2021-41227/42474", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41209: In affected versions, the implementations for convolution operators trigger a division by 0 if passed empty filter tensor arguments. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hpv-v2rx-c5g6\r\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41209", "id": "pyup.io-42456", "more_info_path": "/vulnerabilities/CVE-2021-41209/42456", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22924.", "cve": "CVE-2021-22924", "id": "pyup.io-43748", "more_info_path": "/vulnerabilities/CVE-2021-22924/43748", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22923.", "cve": "CVE-2021-22923", "id": "pyup.io-43747", "more_info_path": "/vulnerabilities/CVE-2021-22923/43747", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41212: In affected versions, the shape inference code for 'tf.ragged.cross' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fr77-rrx3-cp7g\r\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41212", "id": "pyup.io-42459", "more_info_path": "/vulnerabilities/CVE-2021-41212/42459", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41221: In affected versions, the shape inference code for the 'Cudnn*' operations can be tricked into accessing invalid memory via a heap buffer overflow. This occurs because the ranks of the 'input', 'input_h' and 'input_c' parameters are not validated, but code assumes they have certain values. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqv6-3phm-hcwx\r\nhttps://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6", "cve": "CVE-2021-41221", "id": "pyup.io-42468", "more_info_path": "/vulnerabilities/CVE-2021-41221/42468", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41215: In affected versions, the shape inference code for 'DeserializeSparse' can trigger a null pointer dereference. This is because the shape inference function assumes that the 'serialize_sparse' tensor is a tensor with positive rank (and having '3' as the last dimension). The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x3v8-c8qx-3j3r\r\nhttps://github.com/tensorflow/tensorflow/commit/d3738dd70f1c9ceb547258cbb82d853da8771850", "cve": "CVE-2021-41215", "id": "pyup.io-42462", "more_info_path": "/vulnerabilities/CVE-2021-41215/42462", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41216: In affected versions, the shape inference function for 'Transpose' is vulnerable to a heap buffer overflow. This occurs whenever 'perm' contains negative elements. The shape inference function does not validate that the indices in 'perm' are all valid. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3ff2-r28g-w7h9\r\nhttps://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14", "cve": "CVE-2021-41216", "id": "pyup.io-42463", "more_info_path": "/vulnerabilities/CVE-2021-41216/42463", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41222: In affected versions, the implementation of 'SplitV' can trigger a segfault if an attacker supplies negative arguments. This occurs whenever 'size_splits' contains more than one value and at least one value is negative. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cpf4-wx82-gxp6\r\nhttps://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6", "cve": "CVE-2021-41222", "id": "pyup.io-42469", "more_info_path": "/vulnerabilities/CVE-2021-41222/42469", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41199: In affected versions, if 'tf.image.resize' is called with a large input argument then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hx2-qx8j-qjqm", "cve": "CVE-2021-41199", "id": "pyup.io-42446", "more_info_path": "/vulnerabilities/CVE-2021-41199/42446", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Affected versions of Tensorflow allow tensors to have a large number of dimensions and each dimension can be as large as desired. However, the total number of elements in a tensor must fit within an 'int64_t'. If an overflow occurs, 'MultiplyWithoutOverflow' would return a negative result. In the majority of TensorFlow codebase this then results in a 'CHECK'-failure. Newer constructs exist which return a 'Status' instead of crashing the binary. This is a similar issue to CVE-2021-29584.", "cve": "CVE-2021-41197", "id": "pyup.io-42444", "more_info_path": "/vulnerabilities/CVE-2021-41197/42444", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1", ">=2.7.0rc0,<2.7.0" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1,>=2.7.0rc0,<2.7.0" }, { "advisory": "The Grappler component of TensorFlow has a susceptibility to a denial-of-service through a CHECK-failure during constant folding. This issue arises from the output_prop tensor, which has a user-controlled shape and can trigger one of the PartialTensorShape constructor's CHECKs. This flaw has been designated as TFSA-2021-198.\r\n\r\nThe problem has been addressed and rectified in the GitHub commit be7b286d40bc68cb0b56f702186cc4837d508058, which will be incorporated in TensorFlow 2.8.0. This fix will also be applied to TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3 versions as they too are within the affected and presently supported range.\r\n\r\nFor comprehensive information regarding our security model, how to get in touch with us for any queries or concerns, please refer to our security guide.", "cve": "PVE-2023-99912", "id": "pyup.io-62009", "more_info_path": "/vulnerabilities/PVE-2023-99912/62009", "specs": [ "<2.5.3", "==2.7.0", ">=2.6.0,<2.6.3" ], "v": "<2.5.3,==2.7.0,>=2.6.0,<2.6.3" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3 and 2.7.1 update its dependency 'icu' to v69.1 to include a security fix.", "cve": "CVE-2020-10531", "id": "pyup.io-44763", "more_info_path": "/vulnerabilities/CVE-2020-10531/44763", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23563: In multiple places, TensorFlow uses 'tempfile.mktemp' to create temporary files. While this is acceptable in testing, in utilities and libraries it is dangerous as a different process can create the file between the check for the filename in 'mktemp' and the actual creation of the file by a subsequent operation (a TOC/TOU type of weakness). In several instances, TensorFlow was supposed to actually create a temporary directory instead of a file. This logic bug is hidden away by the 'mktemp' function usage. It was replaced 'mktemp' with the safer 'mkstemp'/'mkdtemp' functions, according to the usage pattern.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wc4g-r73w-x8mm", "cve": "CVE-2022-23563", "id": "pyup.io-44851", "more_info_path": "/vulnerabilities/CVE-2022-23563/44851", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23595: When building an XLA compilation cache, if default settings are used, TensorFlow triggers a null pointer dereference. In the default scenario, all devices are allowed, so 'flr->config_proto' is 'nullptr'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fpcp-9h7m-ffpx", "cve": "CVE-2022-23595", "id": "pyup.io-44880", "more_info_path": "/vulnerabilities/CVE-2022-23595/44880", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that Grappler optimizer would attempt to build a tensor using a reference `dtype`. This would result in a crash due to a `CHECK`-fail in the `Tensor` constructor as reference types are not allowed. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23588", "id": "pyup.io-44873", "more_info_path": "/vulnerabilities/CVE-2022-23588/44873", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateOutputSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve tensors with large enough number of elements. We can have a large enough number of dimensions in `output_shape.dim()` or just a small number of dimensions being large enough to cause an overflow in the multiplication. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23576", "id": "pyup.io-44861", "more_info_path": "/vulnerabilities/CVE-2022-23576/44861", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23581: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'IsSimplifiableReshape' would trigger 'CHECK' failures.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fq86-3f29-px2c", "cve": "CVE-2022-23581", "id": "pyup.io-44866", "more_info_path": "/vulnerabilities/CVE-2022-23581/44866", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23571", "id": "pyup.io-44856", "more_info_path": "/vulnerabilities/CVE-2022-23571/44856", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23569: Multiple operations in TensorFlow can be used to trigger a denial of service via 'CHECK'-fails (i.e., assertion failures). This is similar to CVE-2021-41197 and has a similar fix. It is possible that other similar instances exist.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qj5r-f9mv-rffh", "cve": "CVE-2022-23569", "id": "pyup.io-44796", "more_info_path": "/vulnerabilities/CVE-2022-23569/44796", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21734: The implementation of 'MapStage' is vulnerable to a 'CHECK'-fail if the key tensor is not a scalar.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gcvh-66ff-4mwm", "cve": "CVE-2022-21734", "id": "pyup.io-44786", "more_info_path": "/vulnerabilities/CVE-2022-21734/44786", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21732: The implementation of 'ThreadPoolHandle' can be used to trigger a denial of service attack by allocating too much memory. This is because the 'num_threads' argument is only checked to not be negative, but there is no upper bound on its value.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c582-c96p-r5cq", "cve": "CVE-2022-21732", "id": "pyup.io-44784", "more_info_path": "/vulnerabilities/CVE-2022-21732/44784", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23579: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'SafeToRemoveIdentity' would trigger 'CHECK' failures.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5f2r-qp73-37mr", "cve": "CVE-2022-23579", "id": "pyup.io-44864", "more_info_path": "/vulnerabilities/CVE-2022-23579/44864", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21735: The implementation of 'FractionalMaxPool' can be made to crash a TensorFlow process via a division by 0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-87v6-crgm-2gfj", "cve": "CVE-2022-21735", "id": "pyup.io-44787", "more_info_path": "/vulnerabilities/CVE-2022-21735/44787", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. TensorFlow is vulnerable to a heap OOB write in `Grappler`. The `set_output` function writes to an array at the specified index. Hence, this gives a malicious user a write primitive. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23566", "id": "pyup.io-44854", "more_info_path": "/vulnerabilities/CVE-2022-23566/44854", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized data to a new tensor. This later results in undefined behavior. The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23573", "id": "pyup.io-44858", "more_info_path": "/vulnerabilities/CVE-2022-23573/44858", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateTensorSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve a tensor with large enough number of elements. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23575", "id": "pyup.io-44860", "more_info_path": "/vulnerabilities/CVE-2022-23575/44860", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23565: An attacker can trigger denial of service via assertion failure by altering a 'SavedModel' on disk such that 'AttrDef's of some operation are duplicated.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4v5p-v5h9-6xjx", "cve": "CVE-2022-23565", "id": "pyup.io-44853", "more_info_path": "/vulnerabilities/CVE-2022-23565/44853", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23560: An attacker can craft a TFLite model that would allow limited reads and writes outside of arrays in TFLite. This exploits missing validation in the conversion from sparse tensors to dense tensors.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4hvf-hxvg-f67v", "cve": "CVE-2022-23560", "id": "pyup.io-44848", "more_info_path": "/vulnerabilities/CVE-2022-23560/44848", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23564: When decoding a resource handle tensor from protobuf, a TensorFlow process can encounter cases where a 'CHECK' assertion is invalidated based on user controlled arguments. This allows attackers to cause denial of services in TensorFlow processes.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8rcj-c8pj-v3m3", "cve": "CVE-2022-23564", "id": "pyup.io-44852", "more_info_path": "/vulnerabilities/CVE-2022-23564/44852", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23591: The 'GraphDef' format in TensorFlow does not allow self recursive functions. The runtime assumes that this invariant is satisfied. However, a 'GraphDef' containing a fragment such as the following can be consumed when loading a 'SavedModel'. This would result in a stack overflow during execution as resolving each 'NodeDef' means resolving the function itself and its nodes.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-247x-2f9f-5wp7", "cve": "CVE-2022-23591", "id": "pyup.io-44876", "more_info_path": "/vulnerabilities/CVE-2022-23591/44876", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. When decoding PNG images TensorFlow can produce a memory leak if the image is invalid. After calling `png::CommonInitDecode(..., &decode)`, the `decode` value contains allocated buffers which can only be freed by calling `png::CommonFreeDecode(&decode)`. However, several error case in the function implementation invoke the `OP_REQUIRES` macro which immediately terminates the execution of the function, without allowing for the memory free to occur. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23585", "id": "pyup.io-44870", "more_info_path": "/vulnerabilities/CVE-2022-23585/44870", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. There is a typo in TensorFlow's `SpecializeType` which results in heap OOB read/write. Due to a typo, `arg` is initialized to the `i`th mutable argument in a loop where the loop index is `j`. Hence it is possible to assign to `arg` from outside the vector of arguments. Since this is a mutable proto value, it allows both read and write to outside of bounds data. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23574", "id": "pyup.io-44859", "more_info_path": "/vulnerabilities/CVE-2022-23574/44859", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21727: The implementation of shape inference for 'Dequantize' is vulnerable to an integer overflow weakness. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked, and, since the code computes 'axis + 1', an attacker can trigger an integer overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c6fh-56w7-fvjw", "cve": "CVE-2022-21727", "id": "pyup.io-44779", "more_info_path": "/vulnerabilities/CVE-2022-21727/44779", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that assertions in `function.cc` would be falsified and crash the Python interpreter. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23586", "id": "pyup.io-44871", "more_info_path": "/vulnerabilities/CVE-2022-23586/44871", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23557: An attacker can craft a TFLite model that would trigger a division by zero in 'BiasAndClamp' implementation. There is no check that the 'bias_size' is non zero.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf2j-f278-xh4v", "cve": "CVE-2022-23557", "id": "pyup.io-44845", "more_info_path": "/vulnerabilities/CVE-2022-23557/44845", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21731: The implementation of shape inference for 'ConcatV2' can be used to trigger a denial of service attack via a segfault caused by a type confusion. The 'axis' argument is translated into 'concat_dim' in the 'ConcatShapeHelper' helper function. Then, a value for 'min_rank' is computed based on 'concat_dim'. This is then used to validate that the 'values' tensor has at least the required rank. However, 'WithRankAtLeast' receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented. Due to the fact that 'min_rank' is a 32-bits value and the value of 'axis', the 'rank' argument is a negative value, so the error check is bypassed.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m4hf-j54p-p353", "cve": "CVE-2022-21731", "id": "pyup.io-44783", "more_info_path": "/vulnerabilities/CVE-2022-21731/44783", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21737: The implementation of '*Bincount' operations allows malicious users to cause denial of service by passing in arguments which would trigger a 'CHECK'-fail. There are several conditions that the input arguments must satisfy. Some are not caught during shape inference and others are not caught during kernel implementation. This results in 'CHECK' failures later when the output tensors get allocated.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2vv-v9cg-qhh7", "cve": "CVE-2022-21737", "id": "pyup.io-44789", "more_info_path": "/vulnerabilities/CVE-2022-21737/44789", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23568: The implementation of 'AddManySparseToTensorsMap' is vulnerable to an integer overflow which results in a 'CHECK'-fail when building new 'TensorShape' objects (so, an assert failure based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6445-fm66-fvq2", "cve": "CVE-2022-23568", "id": "pyup.io-44795", "more_info_path": "/vulnerabilities/CVE-2022-23568/44795", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23567: The implementations of 'Sparse*Cwise*' ops are vulnerable to integer overflows. These can be used to trigger large allocations (so, OOM based denial of service) or 'CHECK'-fails when building new 'TensorShape' objects (so, assert failures based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rrx2-r989-2c43", "cve": "CVE-2022-23567", "id": "pyup.io-44794", "more_info_path": "/vulnerabilities/CVE-2022-23567/44794", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23559: An attacker can craft a TFLite model that would cause an integer overflow in embedding lookup operations. Both 'embedding_size' and 'lookup_size' are products of values provided by the user. Hence, a malicious user could trigger overflows in the multiplication. In certain scenarios, this can then result in heap OOB read/write.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98p5-x8x4-c9m5", "cve": "CVE-2022-23559", "id": "pyup.io-44847", "more_info_path": "/vulnerabilities/CVE-2022-23559/44847", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21740: The implementation of 'SparseCountSparseOutput' is vulnerable to a heap overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-44qp-9wwf-734r", "cve": "CVE-2022-21740", "id": "pyup.io-44792", "more_info_path": "/vulnerabilities/CVE-2022-21740/44792", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21728: The implementation of shape inference for 'ReverseSequence' does not fully validate the value of 'batch_dim' and can result in a heap OOB read. There is a check to make sure the value of 'batch_dim' does not go over the rank of the input, but there is no check for negative values. Negative dimensions are allowed in some cases to mimic Python's negative indexing (i.e., indexing from the end of the array), however if the value is too negative then the implementation of 'Dim' would access elements before the start of an array.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6gmv-pjp9-p8w8", "cve": "CVE-2022-21728", "id": "pyup.io-44780", "more_info_path": "/vulnerabilities/CVE-2022-21728/44780", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21733: The implementation of 'StringNGrams' can be used to trigger a denial of service attack by causing an out of memory condition after an integer overflow. There is missing a validation on 'pad_witdh' and that result in computing a negative value for 'ngram_width' which is later used to allocate parts of the output.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98j8-c9q4-r38g", "cve": "CVE-2022-21733", "id": "pyup.io-44785", "more_info_path": "/vulnerabilities/CVE-2022-21733/44785", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow can trigger a null pointer dereference. There are 2 places where this can occur, for the same malicious alteration of a `SavedModel` file (fixing the first one would trigger the same dereference in the second place). First, during constant folding, the `GraphDef` might not have the required nodes for the binary operation. If a node is missing, the correposning `mul_*child` would be null, and the dereference in the subsequent line would be incorrect. We have a similar issue during `IsIdentityConsumingSwitch`. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23589", "id": "pyup.io-44874", "more_info_path": "/vulnerabilities/CVE-2022-23589/44874", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23562: The implementation of 'Range' suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qx3f-p745-w4hr", "cve": "CVE-2022-23562", "id": "pyup.io-44850", "more_info_path": "/vulnerabilities/CVE-2022-23562/44850", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. The implementation of `GetInitOp` is vulnerable to a crash caused by dereferencing a null pointer. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23577", "id": "pyup.io-44862", "more_info_path": "/vulnerabilities/CVE-2022-23577/44862", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow is vulnerable to an integer overflow during cost estimation for crop and resize. Since the cropping parameters are user controlled, a malicious person can trigger undefined behavior. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23587", "id": "pyup.io-44872", "more_info_path": "/vulnerabilities/CVE-2022-23587/44872", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23561: An attacker can craft a TFLite model that would cause a write outside of bounds of an array in TFLite. In fact, the attacker can override the linked list used by the memory allocator. This can be leveraged for an arbitrary write primitive under certain conditions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9c78-vcq7-7vxq", "cve": "CVE-2022-23561", "id": "pyup.io-44849", "more_info_path": "/vulnerabilities/CVE-2022-23561/44849", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, TensorFlow can fail to specialize a type during shape inference. This case is covered by the 'DCHECK' function however, 'DCHECK' is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the 'ValueOrDie' line. This results in an assertion failure as 'ret' contains an error 'Status', not a value. In the second case we also get a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23572", "id": "pyup.io-44857", "more_info_path": "/vulnerabilities/CVE-2022-23572/44857", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a use after free behavior when decoding PNG images. After `png::CommonFreeDecode(&decode)` gets called, the values of `decode.width` and `decode.height` are in an unspecified state. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23584", "id": "pyup.io-44869", "more_info_path": "/vulnerabilities/CVE-2022-23584/44869", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21730: The implementation of 'FractionalAvgPoolGrad' does not consider cases where the input tensors are invalid allowing an attacker to read from outside of bounds of heap.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vjg4-v33c-ggc4", "cve": "CVE-2022-21730", "id": "pyup.io-44782", "more_info_path": "/vulnerabilities/CVE-2022-21730/44782", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21738: The implementation of 'SparseCountSparseOutput' can be made to crash a TensorFlow process by an integer overflow whose result is then used in a memory allocation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x4qx-4fjv-hmw6", "cve": "CVE-2022-21738", "id": "pyup.io-44790", "more_info_path": "/vulnerabilities/CVE-2022-21738/44790", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. If a graph node is invalid, TensorFlow can leak memory in the implementation of `ImmutableExecutorState::Initialize`. Here, we set `item->kernel` to `nullptr` but it is a simple `OpKernel*` pointer so the memory that was previously allocated to it would leak. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23578", "id": "pyup.io-44863", "more_info_path": "/vulnerabilities/CVE-2022-23578/44863", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, TensorFlow might do a null-dereference if attributes of some mutable arguments to some operations are missing from the proto. This is guarded by a `DCHECK`. However, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the dereferencing of the null pointer, whereas in the second case it results in a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23570", "id": "pyup.io-44855", "more_info_path": "/vulnerabilities/CVE-2022-23570/44855", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21739: The implementation of 'QuantizedMaxPool' has an undefined behavior where user controlled inputs can trigger a reference binding to null pointer.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3mw4-6rj6-74g5", "cve": "CVE-2022-21739", "id": "pyup.io-44791", "more_info_path": "/vulnerabilities/CVE-2022-21739/44791", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21736: The implementation of 'SparseTensorSliceDataset' has an undefined behavior: under certain conditions, it can be made to dereference a 'nullptr' value. The 3 input arguments to 'SparseTensorSliceDataset' represent a sparse tensor. However, there are some preconditions that these arguments must satisfy, but these are not validated in the implementation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pfjj-m3jj-9jc9", "cve": "CVE-2022-21736", "id": "pyup.io-44788", "more_info_path": "/vulnerabilities/CVE-2022-21736/44788", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21726: The implementation of 'Dequantize' does not fully validate the value of 'axis' and can result in heap OOB accesses. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked and this results in reading past the end of the array containing the dimensions of the input tensor.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-23hm-7w47-xw72", "cve": "CVE-2022-21726", "id": "pyup.io-44778", "more_info_path": "/vulnerabilities/CVE-2022-21726/44778", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21729: The implementation of 'UnravelIndex' is vulnerable to a division by zero caused by an integer overflow bug.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-34f9-hjfq-rr8j", "cve": "CVE-2022-21729", "id": "pyup.io-44781", "more_info_path": "/vulnerabilities/CVE-2022-21729/44781", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23580: During shape inference, TensorFlow can allocate a large vector based on a value from a tensor controlled by the user.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-627q-g293-49q7", "cve": "CVE-2022-23580", "id": "pyup.io-44865", "more_info_path": "/vulnerabilities/CVE-2022-23580/44865", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a 'SavedModel' such that any binary op would trigger 'CHECK' failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the 'dtype' no longer matches the 'dtype' expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If 'Tin' and 'Tout' don't match the type of data in 'out' and 'input_*' tensors then 'flat<*>' would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a 'CHECK' crash, hence a denial of service. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23583", "id": "pyup.io-44868", "more_info_path": "/vulnerabilities/CVE-2022-23583/44868", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23558: An attacker can craft a TFLite model that would cause an integer overflow in 'TfLiteIntArrayCreate'. The 'TfLiteIntArrayGetSizeInBytes' returns an 'int' instead of a 'size_t'. An attacker can control model inputs such that 'computed_size' overflows the size of 'int' datatype.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9gwq-6cwj-47h3", "cve": "CVE-2022-23558", "id": "pyup.io-44846", "more_info_path": "/vulnerabilities/CVE-2022-23558/44846", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21741: An attacker can craft a TFLite model that would trigger a division by zero in the implementation of depthwise convolutions. The parameters of the convolution can be user controlled and are also used within a division operation to determine the size of the padding that needs to be added before applying the convolution. There is no check before this division that the divisor is strictly positive.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-428x-9xc2-m8mj", "cve": "CVE-2022-21741", "id": "pyup.io-44793", "more_info_path": "/vulnerabilities/CVE-2022-21741/44793", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21725: The estimator for the cost of some convolution operations can be made to execute a division by 0. The function fails to check that the stride argument is strictly positive. Hence, the fix is to add a check for the stride argument to ensure it is valid.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v3f7-j968-4h5f", "cve": "CVE-2022-21725", "id": "pyup.io-44777", "more_info_path": "/vulnerabilities/CVE-2022-21725/44777", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23582: A malicious user can cause a denial of service by altering a 'SavedModel' such that 'TensorByteSize' would trigger 'CHECK' failures. 'TensorShape' constructor throws a 'CHECK'-fail if shape is partial or has a number of elements that would overflow the size of an 'int'. The 'PartialTensorShape' constructor instead does not cause a 'CHECK'-abort if the shape is partial, which is exactly what this function needs to be able to return '-1'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4j82-5ccr-4r8v", "cve": "CVE-2022-23582", "id": "pyup.io-44867", "more_info_path": "/vulnerabilities/CVE-2022-23582/44867", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41206: In affected versions, several TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or 'CHECK'-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible. These issues were discovered internally via tooling while working on improving/testing GPU op determinism. As such, there aren't reproducers and there will be multiple fixes for these issues.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pgcq-h79j-2f69\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-43q8-3fv7-pr5x", "cve": "CVE-2021-41206", "id": "pyup.io-42453", "more_info_path": "/vulnerabilities/CVE-2021-41206/42453", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41208: In affected versions, the code for boosted trees in TensorFlow is still missing validation. As a result, attackers can trigger denial of service (via dereferencing 'nullptr's or via 'CHECK'-failures) as well as abuse undefined behavior (binding references to 'nullptr's). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call. Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. TensorFlow's boosted trees APIs will be deprecated in subsequent releases.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-57wx-m983-2f88\r\nhttps://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6gw-r52c-724r", "cve": "CVE-2021-41208", "id": "pyup.io-42455", "more_info_path": "/vulnerabilities/CVE-2021-41208/42455", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Denial of Service via CHECK-failure (assertion failure) in constant folding. The output_prop tensor has a shape that is controlled by user input and this can result in triggering one of the CHECKs in the PartialTensorShape constructor. This is an instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71510", "id": "pyup.io-71510", "more_info_path": "/vulnerabilities/PVE-2024-71510/71510", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1", ">=2.8.0rc0,<2.8.0" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1,>=2.8.0rc0,<2.8.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29199: Missing validation which causes denial of service via 'LoadAndRemapMatrix'.", "cve": "CVE-2022-29199", "id": "pyup.io-48639", "more_info_path": "/vulnerabilities/CVE-2022-29199/48639", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29196: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29196", "id": "pyup.io-48642", "more_info_path": "/vulnerabilities/CVE-2022-29196/48642", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29216: Code injection in 'saved_model_cli'.", "cve": "CVE-2022-29216", "id": "pyup.io-48629", "more_info_path": "/vulnerabilities/CVE-2022-29216/48629", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29200: Missing validation which causes denial of service via 'LSTMBlockCell'.", "cve": "CVE-2022-29200", "id": "pyup.io-48641", "more_info_path": "/vulnerabilities/CVE-2022-29200/48641", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27775.", "cve": "CVE-2022-27775", "id": "pyup.io-48657", "more_info_path": "/vulnerabilities/CVE-2022-27775/48657", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27782.", "cve": "CVE-2022-27782", "id": "pyup.io-48663", "more_info_path": "/vulnerabilities/CVE-2022-27782/48663", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29211: Segfault when 'tf.histogram_fixed_width' is called with NaN values.", "cve": "CVE-2022-29211", "id": "pyup.io-48651", "more_info_path": "/vulnerabilities/CVE-2022-29211/48651", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29203: Integer overflow in 'SpaceToBatchND'.", "cve": "CVE-2022-29203", "id": "pyup.io-48648", "more_info_path": "/vulnerabilities/CVE-2022-29203/48648", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29198: Missing validation which causes denial of service via 'SparseTensorToCSRSparseMatrix'.", "cve": "CVE-2022-29198", "id": "pyup.io-48640", "more_info_path": "/vulnerabilities/CVE-2022-29198/48640", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Denial of Service in the implementation of depthwise ops via CHECK-failure (assertion failure) caused by overflowing the number of elements in a tensor. This is another instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71511", "id": "pyup.io-71511", "more_info_path": "/vulnerabilities/PVE-2024-71511/71511", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29192: missing validation which crashes 'QuantizeAndDequantizeV4Grad'.", "cve": "CVE-2022-29192", "id": "pyup.io-48634", "more_info_path": "/vulnerabilities/CVE-2022-29192/48634", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29202: Denial of service in 'tf.ragged.constant' due to lack of validation.", "cve": "CVE-2022-29202", "id": "pyup.io-48650", "more_info_path": "/vulnerabilities/CVE-2022-29202/48650", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29204: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29204", "id": "pyup.io-48647", "more_info_path": "/vulnerabilities/CVE-2022-29204/48647", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29209: Type confusion leading to 'CHECK'-failure based denial of service.", "cve": "CVE-2022-29209", "id": "pyup.io-48654", "more_info_path": "/vulnerabilities/CVE-2022-29209/48654", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29191: Missing validation which causes denial of service via 'GetSessionTensor'.", "cve": "CVE-2022-29191", "id": "pyup.io-48636", "more_info_path": "/vulnerabilities/CVE-2022-29191/48636", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27778.", "cve": "CVE-2022-27778", "id": "pyup.io-48659", "more_info_path": "/vulnerabilities/CVE-2022-27778/48659", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29195: Missing validation which causes denial of service via 'StagePeek'.", "cve": "CVE-2022-29195", "id": "pyup.io-48637", "more_info_path": "/vulnerabilities/CVE-2022-29195/48637", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29208: Segfault and OOB write due to incomplete validation in 'EditDistance'.", "cve": "CVE-2022-29208", "id": "pyup.io-48649", "more_info_path": "/vulnerabilities/CVE-2022-29208/48649", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29193: missing validation which causes 'TensorSummaryV2' to crash.", "cve": "CVE-2022-29193", "id": "pyup.io-48633", "more_info_path": "/vulnerabilities/CVE-2022-29193/48633", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29201: Missing validation which results in undefined behavior in 'QuantizedConv2D'.", "cve": "CVE-2022-29201", "id": "pyup.io-48646", "more_info_path": "/vulnerabilities/CVE-2022-29201/48646", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29206: Missing validation which results in undefined behavior in 'SparseTensorDenseAdd'.", "cve": "CVE-2022-29206", "id": "pyup.io-48645", "more_info_path": "/vulnerabilities/CVE-2022-29206/48645", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-22576.", "cve": "CVE-2022-22576", "id": "pyup.io-48655", "more_info_path": "/vulnerabilities/CVE-2022-22576/48655", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27781.", "cve": "CVE-2022-27781", "id": "pyup.io-48662", "more_info_path": "/vulnerabilities/CVE-2022-27781/48662", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29197: Missing validation which causes denial of service via 'UnsortedSegmentJoin'.", "cve": "CVE-2022-29197", "id": "pyup.io-48638", "more_info_path": "/vulnerabilities/CVE-2022-29197/48638", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29213: Crashes stemming from incomplete validation in signal ops.", "cve": "CVE-2022-29213", "id": "pyup.io-48653", "more_info_path": "/vulnerabilities/CVE-2022-29213/48653", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27774.", "cve": "CVE-2022-27774", "id": "pyup.io-48656", "more_info_path": "/vulnerabilities/CVE-2022-27774/48656", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27776.", "cve": "CVE-2022-27776", "id": "pyup.io-48658", "more_info_path": "/vulnerabilities/CVE-2022-27776/48658", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27779.", "cve": "CVE-2022-27779", "id": "pyup.io-48660", "more_info_path": "/vulnerabilities/CVE-2022-27779/48660", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29212: Core dump when loading TFLite models with quantization.", "cve": "CVE-2022-29212", "id": "pyup.io-48652", "more_info_path": "/vulnerabilities/CVE-2022-29212/48652", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29205: Segfault due to missing support for quantized types.", "cve": "CVE-2022-29205", "id": "pyup.io-48644", "more_info_path": "/vulnerabilities/CVE-2022-29205/48644", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27780.", "cve": "CVE-2022-27780", "id": "pyup.io-48661", "more_info_path": "/vulnerabilities/CVE-2022-27780/48661", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-30115.", "cve": "CVE-2022-30115", "id": "pyup.io-48664", "more_info_path": "/vulnerabilities/CVE-2022-30115/48664", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29207: Issues arising from undefined behavior stemming from users supplying invalid resource handles.", "cve": "CVE-2022-29207", "id": "pyup.io-48643", "more_info_path": "/vulnerabilities/CVE-2022-29207/48643", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29194: Missing validation which causes denial of service via 'DeleteSessionTensor'.", "cve": "CVE-2022-29194", "id": "pyup.io-48635", "more_info_path": "/vulnerabilities/CVE-2022-29194/48635", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'zlib' to v1.2.12 to handle CVE-2018-25032.", "cve": "CVE-2018-25032", "id": "pyup.io-48665", "more_info_path": "/vulnerabilities/CVE-2018-25032/48665", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "A vulnerability in TensorFlow's `GatherNd` function can trigger an out-of-bounds memory read or crash when inputs exceed output sizes. This issue is resolved in a GitHub commit, which will be included in an upcoming TensorFlow release. Additionally, the fix will be applied to several previous versions that are still under support. This vulnerability has no known workarounds, so updating to a patched version is recommended.", "cve": "CVE-2022-35938", "id": "pyup.io-71612", "more_info_path": "/vulnerabilities/CVE-2022-35938/71612", "specs": [ "<2.7.2", ">=2.8.0,<2.8.1", ">=2.9.0,<2.9.1" ], "v": "<2.7.2,>=2.8.0,<2.8.1,>=2.9.0,<2.9.1" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35940: Int overflow in 'RaggedRangeOp'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x989-q2pq-4q5x", "cve": "CVE-2022-35940", "id": "pyup.io-51052", "more_info_path": "/vulnerabilities/CVE-2022-35940/51052", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35982: Segfault in 'SparseBincount'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-397c-5g2j-qxpv", "cve": "CVE-2022-35982", "id": "pyup.io-51071", "more_info_path": "/vulnerabilities/CVE-2022-35982/51071", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35993: 'CHECK' fail in 'SetSize'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wq6q-6m32-9rv9", "cve": "CVE-2022-35993", "id": "pyup.io-51082", "more_info_path": "/vulnerabilities/CVE-2022-35993/51082", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35992: 'CHECK' fail in 'TensorListFromTensor'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9v8w-xmr4-wgxp", "cve": "CVE-2022-35992", "id": "pyup.io-51081", "more_info_path": "/vulnerabilities/CVE-2022-35992/51081", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36014: Null-dereference in 'mlir::tfg::TFOp::nameAttr'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7j3m-8g3c-9qqq", "cve": "CVE-2022-36014", "id": "pyup.io-51098", "more_info_path": "/vulnerabilities/CVE-2022-36014/51098", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35971: 'CHECK' fail in 'FakeQuantWithMinMaxVars'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9fpg-838v-wpv7", "cve": "CVE-2022-35971", "id": "pyup.io-51065", "more_info_path": "/vulnerabilities/CVE-2022-35971/51065", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36017: Segfault in 'Requantize'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wqmc-pm8c-2jhc", "cve": "CVE-2022-36017", "id": "pyup.io-51101", "more_info_path": "/vulnerabilities/CVE-2022-36017/51101", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35994: 'CHECK' fail in 'CollectiveGather'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fhfc-2q7x-929f", "cve": "CVE-2022-35994", "id": "pyup.io-51083", "more_info_path": "/vulnerabilities/CVE-2022-35994/51083", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36019: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannel'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9j4v-pp28-mxv7", "cve": "CVE-2022-36019", "id": "pyup.io-51103", "more_info_path": "/vulnerabilities/CVE-2022-36019/51103", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36015: Integer overflow in math ops. \r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rh87-q4vg-m45j", "cve": "CVE-2022-36015", "id": "pyup.io-51099", "more_info_path": "/vulnerabilities/CVE-2022-36015/51099", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35952: 'CHECK' failures in 'UnbatchGradOp'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h5vq-gw2c-pq47", "cve": "CVE-2022-35952", "id": "pyup.io-51054", "more_info_path": "/vulnerabilities/CVE-2022-35952/51054", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35964: Segfault in 'BlockLSTMGradV2'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f7r5-q7cx-h668", "cve": "CVE-2022-35964", "id": "pyup.io-51058", "more_info_path": "/vulnerabilities/CVE-2022-35964/51058", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35937: OOB read in 'Gather_nd' op in TF Lite.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pxrw-j2fv-hx3h", "cve": "CVE-2022-35937", "id": "pyup.io-51049", "more_info_path": "/vulnerabilities/CVE-2022-35937/51049", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35974: Segfault in 'QuantizeDownAndShrinkRange'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vgvh-2pf4-jr2x", "cve": "CVE-2022-35974", "id": "pyup.io-51068", "more_info_path": "/vulnerabilities/CVE-2022-35974/51068", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35990: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannelGradient'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h7ff-cfc9-wmmh", "cve": "CVE-2022-35990", "id": "pyup.io-51079", "more_info_path": "/vulnerabilities/CVE-2022-35990/51079", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36027: Segfault TFLite converter on per-channel quantized transposed convolutions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-79h2-q768-fpxr", "cve": "CVE-2022-36027", "id": "pyup.io-51105", "more_info_path": "/vulnerabilities/CVE-2022-36027/51105", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35997: 'CHECK' fail in 'tf.sparse.cross'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p7hr-f446-x6qf", "cve": "CVE-2022-35997", "id": "pyup.io-51086", "more_info_path": "/vulnerabilities/CVE-2022-35997/51086", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36005: 'CHECK' fail in 'FakeQuantWithMinMaxVarsGradient'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r26c-679w-mrjm", "cve": "CVE-2022-36005", "id": "pyup.io-51094", "more_info_path": "/vulnerabilities/CVE-2022-36005/51094", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36003: 'CHECK' fail in 'RandomPoissonV2'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cv2p-32v3-vhwq", "cve": "CVE-2022-36003", "id": "pyup.io-51092", "more_info_path": "/vulnerabilities/CVE-2022-36003/51092", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36001: 'CHECK' fail in 'DrawBoundingBoxes'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jqm7-m5q7-3hm5", "cve": "CVE-2022-36001", "id": "pyup.io-51090", "more_info_path": "/vulnerabilities/CVE-2022-36001/51090", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35986: Segfault in 'RaggedBincount'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wr9v-g9vf-c74v", "cve": "CVE-2022-35986", "id": "pyup.io-51075", "more_info_path": "/vulnerabilities/CVE-2022-35986/51075", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35985: 'CHECK' fail in 'LRNGrad'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9942-r22v-78cp", "cve": "CVE-2022-35985", "id": "pyup.io-51074", "more_info_path": "/vulnerabilities/CVE-2022-35985/51074", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36000: 'CHECK' fail in 'Eig'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqxc-pvf8-2w9v", "cve": "CVE-2022-36000", "id": "pyup.io-51089", "more_info_path": "/vulnerabilities/CVE-2022-36000/51089", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36011: Null dereference on MLIR on empty function attributes.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fv43-93gv-vm8f", "cve": "CVE-2022-36011", "id": "pyup.io-51095", "more_info_path": "/vulnerabilities/CVE-2022-36011/51095", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35999: 'CHECK' fail in 'Conv2DBackpropInput'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-37jf-mjv6-xfqw", "cve": "CVE-2022-35999", "id": "pyup.io-51088", "more_info_path": "/vulnerabilities/CVE-2022-35999/51088", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35995: 'CHECK' fail in 'AudioSummaryV2'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9h5-vr8m-x2h4", "cve": "CVE-2022-35995", "id": "pyup.io-51084", "more_info_path": "/vulnerabilities/CVE-2022-35995/51084", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36018: 'CHECK' fail in 'RaggedTensorToVariant'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6cv-4fmf-66xf", "cve": "CVE-2022-36018", "id": "pyup.io-51102", "more_info_path": "/vulnerabilities/CVE-2022-36018/51102", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35959: 'CHECK' failures in 'AvgPool3DGrad'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wxjj-cgcx-r3vq", "cve": "CVE-2022-35959", "id": "pyup.io-51055", "more_info_path": "/vulnerabilities/CVE-2022-35959/51055", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35996: Floating point exception in 'Conv2D'. \r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q5jv-m6qw-5g37", "cve": "CVE-2022-35996", "id": "pyup.io-51085", "more_info_path": "/vulnerabilities/CVE-2022-35996/51085", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35988: 'CHECK' fail in 'tf.linalg.matrix_rank'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vqj-64pv-w55c", "cve": "CVE-2022-35988", "id": "pyup.io-51077", "more_info_path": "/vulnerabilities/CVE-2022-35988/51077", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35983: 'CHECK' fail in 'Save' and 'SaveSlices'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6vp-8q9j-whx4", "cve": "CVE-2022-35983", "id": "pyup.io-51072", "more_info_path": "/vulnerabilities/CVE-2022-35983/51072", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35972: Segfault in 'QuantizedBiasAdd'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4pc4-m9mj-v2r9", "cve": "CVE-2022-35972", "id": "pyup.io-51066", "more_info_path": "/vulnerabilities/CVE-2022-35972/51066", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35967: Segfault in 'QuantizedAdd'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v6h3-348g-6h5x", "cve": "CVE-2022-35967", "id": "pyup.io-51061", "more_info_path": "/vulnerabilities/CVE-2022-35967/51061", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35966: Segfault in 'QuantizedAvgPool'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4w68-4x85-mjj9", "cve": "CVE-2022-35966", "id": "pyup.io-51060", "more_info_path": "/vulnerabilities/CVE-2022-35966/51060", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35960: 'CHECK' failure in 'TensorListReserve' via missing validation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v5xg-3q2c-c2r4", "cve": "CVE-2022-35960", "id": "pyup.io-51056", "more_info_path": "/vulnerabilities/CVE-2022-35960/51056", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35963: 'CHECK' failures in 'FractionalAvgPoolGrad'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-84jm-4cf3-9jfm", "cve": "CVE-2022-35963", "id": "pyup.io-51057", "more_info_path": "/vulnerabilities/CVE-2022-35963/51057", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35941: 'CHECK' failure in 'AvgPoolOp'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mgmh-g2v6-mqw5", "cve": "CVE-2022-35941", "id": "pyup.io-51053", "more_info_path": "/vulnerabilities/CVE-2022-35941/51053", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36002: 'CHECK' fail in 'Unbatch'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mh3m-62v7-68xg", "cve": "CVE-2022-36002", "id": "pyup.io-51091", "more_info_path": "/vulnerabilities/CVE-2022-36002/51091", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35984: 'CHECK' fail in 'ParameterizedTruncatedNormal'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2xf-8hgm-hpw5", "cve": "CVE-2022-35984", "id": "pyup.io-51073", "more_info_path": "/vulnerabilities/CVE-2022-35984/51073", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35970: Segfault in 'QuantizedInstanceNorm'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g35r-369w-3fqp", "cve": "CVE-2022-35970", "id": "pyup.io-51064", "more_info_path": "/vulnerabilities/CVE-2022-35970/51064", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35969: 'CHECK' fail in 'Conv2DBackpropInput'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q2c3-jpmc-gfjx", "cve": "CVE-2022-35969", "id": "pyup.io-51063", "more_info_path": "/vulnerabilities/CVE-2022-35969/51063", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36016: 'CHECK'-fail in 'tensorflow::full_type::SubstituteFromAttrs'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g468-qj8g-vcjc", "cve": "CVE-2022-36016", "id": "pyup.io-51100", "more_info_path": "/vulnerabilities/CVE-2022-36016/51100", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36004: 'CHECK' fail in 'tf.random.gamma'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv8m-8x97-937q", "cve": "CVE-2022-36004", "id": "pyup.io-51093", "more_info_path": "/vulnerabilities/CVE-2022-36004/51093", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35981: 'CHECK' fail in 'FractionalMaxPoolGrad'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vxv8-r8q2-63xw", "cve": "CVE-2022-35981", "id": "pyup.io-51070", "more_info_path": "/vulnerabilities/CVE-2022-35981/51070", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35979: Segfault in 'QuantizedRelu' and 'QuantizedRelu6'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v7vw-577f-vp8x", "cve": "CVE-2022-35979", "id": "pyup.io-51069", "more_info_path": "/vulnerabilities/CVE-2022-35979/51069", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35965: Segfault in 'LowerBound' and 'UpperBound'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qxpx-j395-pw36", "cve": "CVE-2022-35965", "id": "pyup.io-51059", "more_info_path": "/vulnerabilities/CVE-2022-35965/51059", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35987: 'CHECK' fail in 'DenseBincount'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w62h-8xjm-fv49", "cve": "CVE-2022-35987", "id": "pyup.io-51076", "more_info_path": "/vulnerabilities/CVE-2022-35987/51076", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35934: 'CHECK' failure in tf.reshape via overflows.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f4w6-h4f5-wx45", "cve": "CVE-2022-35934", "id": "pyup.io-51047", "more_info_path": "/vulnerabilities/CVE-2022-35934/51047", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35939: OOB write in 'scatter_nd' op in TF Lite.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-ffjm-4qwc-7cmf", "cve": "CVE-2022-35939", "id": "pyup.io-51051", "more_info_path": "/vulnerabilities/CVE-2022-35939/51051", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36013: Null-dereference in 'mlir::tfg::GraphDefImporter::ConvertNodeDef'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-828c-5j5q-vrjq", "cve": "CVE-2022-36013", "id": "pyup.io-51097", "more_info_path": "/vulnerabilities/CVE-2022-36013/51097", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35989: 'CHECK' fail in 'MaxPool'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j43h-pgmg-5hjq", "cve": "CVE-2022-35989", "id": "pyup.io-51078", "more_info_path": "/vulnerabilities/CVE-2022-35989/51078", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35998: 'CHECK' fail in 'EmptyTensorList'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhw4-wwr7-gjc5", "cve": "CVE-2022-35998", "id": "pyup.io-51087", "more_info_path": "/vulnerabilities/CVE-2022-35998/51087", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35968: 'CHECK' fail in 'AvgPoolGrad'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2475-53vw-vp25", "cve": "CVE-2022-35968", "id": "pyup.io-51062", "more_info_path": "/vulnerabilities/CVE-2022-35968/51062", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36012: Assertion fail on MLIR empty edge names.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jvhc-5hhr-w3v5", "cve": "CVE-2022-36012", "id": "pyup.io-51096", "more_info_path": "/vulnerabilities/CVE-2022-36012/51096", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36026: 'CHECK' fail in 'QuantizeAndDequantizeV3'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9cr2-8pwr-fhfq", "cve": "CVE-2022-36026", "id": "pyup.io-51104", "more_info_path": "/vulnerabilities/CVE-2022-36026/51104", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "TensorFlow 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35973: Segfault in 'QuantizedMatMul'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-689c-r7h2-fv9v", "cve": "CVE-2022-35973", "id": "pyup.io-51067", "more_info_path": "/vulnerabilities/CVE-2022-35973/51067", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Impact: A recurring instance of CVE-2022-35935 has been observed and addressed. In this case, `SobolSample` is prone to denial of service due to assumed scalar inputs. You can replicate this using the following code in Python:\r\n\r\n```python \r\nimport tensorflow as tf \r\ntf.raw_ops.SobolSample(dim=tf.constant([1,0]), num_results=tf.constant([1]), skip=tf.constant([1])) \r\n```\r\n\r\nPatches: Corrective measures have been taken and the issue has been patched via GitHub commits c65c67f88ad770662e8f191269a907bf2b94b1bf and 02400ea266bd811fc016a848445de1bbff3a23a0. These fixes will be integrated in the forthcoming TensorFlow 2.11 release and will also be added to TensorFlow 2.10.1, 2.9.3, and 2.8.4 as they fall within the supported range. Furthermore, the initial commit will be incorporated into TensorFlow 2.7.4.\r\n\r\nFor more information: You can refer to the TensorFlow's security guide for comprehensive insights into the security model and for details on how to contact them for queries or issues.\r\n\r\nAttribution: This vulnerability was reported by Kang Hong Jin from Singapore Management University, Neophytos Christou from Secure Systems Labs at Brown University, Liu Liyuan from the Information System & Security and Countermeasures Experiments Center at Beijing Institute of Technology, and Pattarakrit Rattankul.", "cve": "PVE-2023-99921", "id": "pyup.io-61990", "more_info_path": "/vulnerabilities/PVE-2023-99921/61990", "specs": [ "<2.8.4", ">=2.10.0,<2.10.1", ">=2.9.0,<2.9.3" ], "v": "<2.8.4,>=2.10.0,<2.10.1,>=2.9.0,<2.9.3" }, { "advisory": "The effect of CVE-2022-35991 was seen once more, where TensorListScatter and TensorListScatterV2 could potentially crash due to non scalar inputs in the element_shape parameter while in eager mode. This issue has been identified and resolved. The issue was identified when the following Python code was executed:\r\n\r\n```python \r\nimport tensorflow as tf \r\narg_0=tf.random.uniform(shape=(2, 2, 2), dtype=tf.float16, maxval=None) \r\narg_1=tf.random.uniform(shape=(2, 2, 2), dtype=tf.int32, maxval=65536) \r\narg_2=tf.random.uniform(shape=(2, 2, 2), dtype=tf.int32, maxval=65536) \r\narg_3='' \r\ntf.raw_ops.TensorListScatter(tensor=arg_0, indices=arg_1, element_shape=arg_2, name=arg_3) \r\n```\r\n\r\nA patch to resolve this issue is available in the GitHub commit bf9932fc907aff0e9e8cccf769e8b00d30fd81a1. This fix will be part of TensorFlow 2.11. Additionally, the commitment will be selected for TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these versions are also known to be affected and still under supported range.\r\n\r\nFor further details, please refer to TensorFlow's security guide. If there is any issue or question, contact us please.\r\n\r\nThe person who brought this vulnerability to our attention is Pattarakrit Rattankul.", "cve": "PVE-2023-99920", "id": "pyup.io-61991", "more_info_path": "/vulnerabilities/PVE-2023-99920/61991", "specs": [ "<2.8.4", ">=2.10.0,<2.10.1", ">=2.9.0,<2.9.3" ], "v": "<2.8.4,>=2.10.0,<2.10.1,>=2.9.0,<2.9.3" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41897: If 'FractionMaxPoolGrad' is given outsize inputs 'row_pooling_sequence' and 'col_pooling_sequence', TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2w8-jw48-fr7j", "cve": "CVE-2022-41897", "id": "pyup.io-51955", "more_info_path": "/vulnerabilities/CVE-2022-41897/51955", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "TensorFlow is an open source platform for machine learning. An input 'sparse_matrix' that is not a matrix with a shape with rank 0 will trigger a 'CHECK' fail in 'tf.raw_ops.SparseMatrixNNZ'. We have patched the issue in GitHub commit f856d02e5322821aad155dad9b3acab1e9f5d693. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.", "cve": "CVE-2022-41901", "id": "pyup.io-51959", "more_info_path": "/vulnerabilities/CVE-2022-41901/51959", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41884: If a numpy array is created with a shape such that one element is zero and the others sum to a large number, an error will be raised. \r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jq6x-99hj-q636", "cve": "CVE-2022-41884", "id": "pyup.io-51943", "more_info_path": "/vulnerabilities/CVE-2022-41884/51943", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41891: If 'tf.raw_ops.TensorListConcat' is given 'element_shape=[]', it results segmentation fault which can be used to trigger a denial of service attack.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-66vq-54fq-6jvv", "cve": "CVE-2022-41891", "id": "pyup.io-51950", "more_info_path": "/vulnerabilities/CVE-2022-41891/51950", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41890: If 'BCast::ToShape' is given input larger than an 'int32', it will crash, despite being supposed to handle up to an 'int64'. An example can be seen in 'tf.experimental.numpy.outer' by passing in large input to the input 'b'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h246-cgh4-7475", "cve": "CVE-2022-41890", "id": "pyup.io-51949", "more_info_path": "/vulnerabilities/CVE-2022-41890/51949", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41889: If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a 'nullptr', which is not caught. An example can be seen in 'tf.compat.v1.extract_volume_patches' by passing in quantized tensors as input 'ksizes'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xxcj-rhqg-m46g", "cve": "CVE-2022-41889", "id": "pyup.io-51948", "more_info_path": "/vulnerabilities/CVE-2022-41889/51948", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41910: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-frqp-wp83-qggv", "cve": "CVE-2022-41910", "id": "pyup.io-52348", "more_info_path": "/vulnerabilities/CVE-2022-41910/52348", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41896: If 'ThreadUnsafeUnigramCandidateSampler' is given input 'filterbank_channel_count' greater than the allowed max size, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rmg2-f698-wq35", "cve": "CVE-2022-41896", "id": "pyup.io-51954", "more_info_path": "/vulnerabilities/CVE-2022-41896/51954", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41902: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cg88-rpvp-cjv5", "cve": "CVE-2022-41902", "id": "pyup.io-52347", "more_info_path": "/vulnerabilities/CVE-2022-41902/52347", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41907: When 'tf.raw_ops.ResizeNearestNeighborGrad' is given a large 'size' input, it overflows.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-368v-7v32-52fx", "cve": "CVE-2022-41907", "id": "pyup.io-51960", "more_info_path": "/vulnerabilities/CVE-2022-41907/51960", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41908: TensorFlow is an open source platform for machine learning. An input 'token' that is not a UTF-8 bytestring will trigger a 'CHECK' fail in 'tf.raw_ops.PyFunc'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv77-9g28-cwg3", "cve": "CVE-2022-41908", "id": "pyup.io-51961", "more_info_path": "/vulnerabilities/CVE-2022-41908/51961", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41895: If 'MirrorPadGrad' is given outsize input 'paddings', TensorFlow will give a heap OOB error.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gq2j-cr96-gvqx", "cve": "CVE-2022-41895", "id": "pyup.io-51953", "more_info_path": "/vulnerabilities/CVE-2022-41895/51953", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41893: If 'tf.raw_ops.TensorListResize' is given a nonscalar value for input 'size', it results 'CHECK' fail which can be used to trigger a denial of service attack.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-67pf-62xr-q35m", "cve": "CVE-2022-41893", "id": "pyup.io-51951", "more_info_path": "/vulnerabilities/CVE-2022-41893/51951", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41900: The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xvwp-h6jv-7472", "cve": "CVE-2022-41900", "id": "pyup.io-51958", "more_info_path": "/vulnerabilities/CVE-2022-41900/51958", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41888: When running on GPU, 'tf.image.generate_bounding_box_proposals' receives a 'scores' input that must be of rank 4 but is not checked.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6x99-gv2v-q76v", "cve": "CVE-2022-41888", "id": "pyup.io-51947", "more_info_path": "/vulnerabilities/CVE-2022-41888/51947", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41898: If 'SparseFillEmptyRowsGrad' is given empty inputs, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hq7g-wwwp-q46h", "cve": "CVE-2022-41898", "id": "pyup.io-51956", "more_info_path": "/vulnerabilities/CVE-2022-41898/51956", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41894: The reference kernel of the 'CONV_3D_TRANSPOSE' TensorFlow Lite operator wrongly increments the data_ptr when adding the bias to the result. Instead of 'data_ptr += num_channels;' it should be 'data_ptr += output_num_channels;' as if the number of input channels is different than the number of output channels, the wrong result will be returned and a buffer overflow will occur if num_channels > output_num_channels. An attacker can craft a model with a specific number of input channels. It is then possible to write specific values through the bias of the layer outside the bounds of the buffer. This attack only works if the reference kernel resolver is used in the interpreter.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6q3-vv32-2cq5", "cve": "CVE-2022-41894", "id": "pyup.io-51952", "more_info_path": "/vulnerabilities/CVE-2022-41894/51952", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41909: An input 'encoded' that is not a valid 'CompositeTensorVariant' tensor will trigger a segfault in 'tf.raw_ops.CompositeTensorVariantToComponents'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjx6-v474-2ch9", "cve": "CVE-2022-41909", "id": "pyup.io-51962", "more_info_path": "/vulnerabilities/CVE-2022-41909/51962", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41899: TensorFlow is an open source platform for machine learning. Inputs 'dense_features' or 'example_state_data' not of rank 2 will trigger a 'CHECK' fail in 'SdcaOptimizer'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-27rc-728f-x5w2", "cve": "CVE-2022-41899", "id": "pyup.io-51957", "more_info_path": "/vulnerabilities/CVE-2022-41899/51957", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41886: When 'tf.raw_ops.ImageProjectiveTransformV2' is given a large output shape, it overflows.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-54pp-c6pp-7fpx", "cve": "CVE-2022-41886", "id": "pyup.io-51945", "more_info_path": "/vulnerabilities/CVE-2022-41886/51945", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41911: When printing a tensor, we get it's data as a 'const char*' array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from 'char' to 'bool' are undefined if the 'char' is not '0' or '1', so sanitizers/fuzzers will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j", "cve": "CVE-2022-41911", "id": "pyup.io-51963", "more_info_path": "/vulnerabilities/CVE-2022-41911/51963", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41880: When the 'BaseCandidateSamplerOp' function receives a value in 'true_classes' larger than 'range_max', a heap oob read occurs.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8w5g-3wcv-9g2j", "cve": "CVE-2022-41880", "id": "pyup.io-51941", "more_info_path": "/vulnerabilities/CVE-2022-41880/51941", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41885: When 'tf.raw_ops.FusedResizeAndPadConv2D' is given a large tensor shape, it overflows.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-762h-vpvw-3rcx", "cve": "CVE-2022-41885", "id": "pyup.io-51944", "more_info_path": "/vulnerabilities/CVE-2022-41885/51944", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "TensorFlow 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35935: 'CHECK' failure in 'SobolSample' via missing validation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-97p7-w86h-vcf9\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqvq-fvhr-v6hc", "cve": "CVE-2022-35935", "id": "pyup.io-51048", "more_info_path": "/vulnerabilities/CVE-2022-35935/51048", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "TensorFlow 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35991: 'CHECK' fail in 'TensorListScatter' and 'TensorListScatterV2'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vm7x-4qhj-rrcq\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xf83-q765-xm6m", "cve": "CVE-2022-35991", "id": "pyup.io-51080", "more_info_path": "/vulnerabilities/CVE-2022-35991/51080", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow 2.9.3 and 2.10.1 include a fix for CVE-2022-41887: 'tf.keras.losses.poisson' receives a 'y_pred' and 'y_true' that are passed through 'functor::mul' in 'BinaryOp'. If the resulting dimensions overflow an 'int32', TensorFlow will crash due to a size mismatch during broadcast assignment.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fvv-46hw-vpg3", "cve": "CVE-2022-41887", "id": "pyup.io-51946", "more_info_path": "/vulnerabilities/CVE-2022-41887/51946", "specs": [ "<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Google TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local). See CVE-2018-8825.", "cve": "CVE-2018-8825", "id": "pyup.io-40791", "more_info_path": "/vulnerabilities/CVE-2018-8825/40791", "specs": [ "<=1.7" ], "v": "<=1.7" }, { "advisory": "Various versions of TensorFlow are susceptible to a NULL Pointer Dereference vulnerability, where decoding specially crafted GIF images can trigger a null pointer dereference.", "cve": "PVE-2024-99851", "id": "pyup.io-65569", "more_info_path": "/vulnerabilities/PVE-2024-99851/65569", "specs": [ ">=0,<1.12.2" ], "v": ">=0,<1.12.2" }, { "advisory": "Some versions of tensorflow are vulnerable to an out-of-bounds read issue, where decoding variant tensors from proto could lead to unauthorized heap memory access. The exploit maturity for this vulnerability is currently unproven.", "cve": "PVE-2024-99850", "id": "pyup.io-65570", "more_info_path": "/vulnerabilities/PVE-2024-99850/65570", "specs": [ ">=0,<2.0.0" ], "v": ">=0,<2.0.0" }, { "advisory": "Affected versions of TensorFlow are susceptible to a Denial of Service (DoS) attack caused by an issue similar to CVE-2022-35991, occurring in TensorListScatter and TensorListScatterV2 when non-scalar inputs are used.", "cve": "PVE-2024-99852", "id": "pyup.io-65568", "more_info_path": "/vulnerabilities/PVE-2024-99852/65568", "specs": [ ">=0,<2.8.4", ">=2.9.0,<2.9.3", ">=2.10.0,<2.10.1" ], "v": ">=0,<2.8.4,>=2.9.0,<2.9.3,>=2.10.0,<2.10.1" }, { "advisory": "Tensorflow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 updates its dependency \"SQLite\" to handle CVE-2020-15358.", "cve": "CVE-2020-15358", "id": "pyup.io-39873", "more_info_path": "/vulnerabilities/CVE-2020-15358/39873", "specs": [ ">=1.15.0rc0,<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=1.15.0rc0,<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow versions 1.15.2 and 2.0.1 update its dependency \"SQLite\" to handle CVE-2019-19646.", "cve": "CVE-2019-19646", "id": "pyup.io-39537", "more_info_path": "/vulnerabilities/CVE-2019-19646/39537", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow versions 1.15.2 and 2.0.1 includes a fix for CVE-2020-5215: In TensorFlow before 1.15.2 and 2.0.1, converting a string (from Python) to a tf.float16 value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode. This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a tf.float16 value. Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar tf.float16 value with a scalar string will trigger this issue due to automatic conversions. This can be easily reproduced by tf.constant(\"hello\", tf.float16), if eager execution is enabled.", "cve": "CVE-2020-5215", "id": "pyup.io-37776", "more_info_path": "/vulnerabilities/CVE-2020-5215/37776", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow versions 1.15.2 and 2.0.1 updates its dependency \"curl\" to handle CVE-2019-5482.", "cve": "CVE-2019-5482", "id": "pyup.io-38039", "more_info_path": "/vulnerabilities/CVE-2019-5482/38039", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow versions 1.15.2 and 2.0.1 updates its dependency \"curl\" to handle CVE-2019-5481.", "cve": "CVE-2019-5481", "id": "pyup.io-39570", "more_info_path": "/vulnerabilities/CVE-2019-5481/39570", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow versions 1.15.2 and 2.0.1 updates 'sqlite3' to handle CVE-2019-16168.", "cve": "CVE-2019-16168", "id": "pyup.io-39568", "more_info_path": "/vulnerabilities/CVE-2019-16168/39568", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 include a fix for CVE-2021-29567: Due to lack of validation in 'tf.raw_ops.SparseDenseCwiseMul', an attacker can trigger denial of service via 'CHECK'-fails or accesses to outside the bounds of heap allocated data. Since the implementation (https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80), it only validates the rank of the input arguments but no constraints between dimensions (https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul) and an attacker can abuse them to trigger internal 'CHECK' assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers.", "cve": "CVE-2021-29567", "id": "pyup.io-40469", "more_info_path": "/vulnerabilities/CVE-2021-29567/40469", "specs": [ ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.5.0rc0,<2.5.0" ], "v": ">=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.5.0rc0,<2.5.0" }, { "advisory": "Tensorflow 2.10.1 includes a fix for CVE-2022-41883: When ops that have specified input sizes receive a differing number of inputs, the executor will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj", "cve": "CVE-2022-41883", "id": "pyup.io-51942", "more_info_path": "/vulnerabilities/CVE-2022-41883/51942", "specs": [ ">=2.10.0rc0,<2.10.1" ], "v": ">=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15193: In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of \"dlpack.to_dlpack\" can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing in a Python object instead of a tensor. The uninitialized memory address is due to a \"reinterpret_cast\". Since the \"PyObject\" is a Python object, not a Tensorflow tensor, the cast to \"EagerTensor\" fails. The issue was patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v", "cve": "CVE-2020-15193", "id": "pyup.io-38823", "more_info_path": "/vulnerabilities/CVE-2020-15193/38823", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15213: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimension of the output tensor, attackers can use a very large value to trigger a large allocation. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps. However, if the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hjmq-236j-8m87", "cve": "CVE-2020-15213", "id": "pyup.io-39851", "more_info_path": "/vulnerabilities/CVE-2020-15213/39851", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15214: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimension of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15214", "id": "pyup.io-39850", "more_info_path": "/vulnerabilities/CVE-2020-15214/39850", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15212: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to \"segment_ids_data\" can alter \"output_index\" and then write to outside of \"output_data\" buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15212", "id": "pyup.io-39852", "more_info_path": "/vulnerabilities/CVE-2020-15212/39852", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15191: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to 'dlpack.to_dlpack' the expected validations will cause variables to bind to 'nullptr' while setting a 'status' variable to the error condition. However, this 'status' argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with '-fsanitize=null'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr", "cve": "CVE-2020-15191", "id": "pyup.io-39872", "more_info_path": "/vulnerabilities/CVE-2020-15191/39872", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15192: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to 'dlpack.to_dlpack' there is a memory leak following an expected validation failure. The issue occurs because the 'status' argument during validation failures is not properly checked. Since each of the above methods can return an error status, the 'status' value must be checked before continuing.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fxw-76px-3rxv", "cve": "CVE-2020-15192", "id": "pyup.io-39871", "more_info_path": "/vulnerabilities/CVE-2020-15192/39871", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow version 2.3.1 includes a fix for CVE-2020-15196: In Tensorflow version 2.3.0, the \"SparseCountSparseOutput\" and \"RaggedCountSparseOutput\" implementations don't validate that the \"weights\" tensor has the same shape as the data. The check exists for \"DenseCountSparseOutput\", where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph", "cve": "CVE-2020-15196", "id": "pyup.io-39867", "more_info_path": "/vulnerabilities/CVE-2020-15196/39867", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow 2.3.1 includes a fix for CVE-2020-15198: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has the same shape as the \"values\" one. The values in these tensors are always accessed in parallel. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3", "cve": "CVE-2020-15198", "id": "pyup.io-39865", "more_info_path": "/vulnerabilities/CVE-2020-15198/39865", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow 2.3.1 includes a fix for CVE-2020-15201: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Hence, the code is prone to heap buffer overflow. If \"split_values\" does not end with a value at least \"num_values\" then the \"while\" loop condition will trigger a read outside of the bounds of \"split_values\" once \"batch_idx\" grows too large. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4", "cve": "CVE-2020-15201", "id": "pyup.io-39862", "more_info_path": "/vulnerabilities/CVE-2020-15201/39862", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow 2.3.1 includes a fix for CVE-2020-15199: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the \"splits\" tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure. Since \"BatchedMap\" is equivalent to a vector, it needs to have at least one element to not be \"nullptr\". If user passes a \"splits\" tensor that is empty or has exactly one element, we get a \"SIGABRT\" signal raised by the operating system. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x5cp-9pcf-pp3h", "cve": "CVE-2020-15199", "id": "pyup.io-39864", "more_info_path": "/vulnerabilities/CVE-2020-15199/39864", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow 2.3.1 includes a fix for CVE-2020-15200: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Thus, the code sets up conditions to cause a heap buffer overflow. A \"BatchedMap\" is equivalent to a vector where each element is a hashmap. However, if the first element of \"splits_values\" is not 0, \"batch_idx\" will never be 1, hence there will be no hashmap at index 0 in \"per_batch_counts\". Trying to access that in the user code results in a segmentation fault. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x7rp-74x2-mjf3", "cve": "CVE-2020-15200", "id": "pyup.io-39863", "more_info_path": "/vulnerabilities/CVE-2020-15200/39863", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow version 2.3.1 includes a fix for CVE-2020-15197: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix. However, malicious users can pass in tensors of different rank, resulting in a \"CHECK\" assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.", "cve": "CVE-2020-15197", "id": "pyup.io-39866", "more_info_path": "/vulnerabilities/CVE-2020-15197/39866", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37671: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.Map*' and 'tf.raw_ops.OrderedMap*' operations. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that 'indices' is in ascending order, but does not check that 'indices' is not empty. The Tensorflow team has patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac.", "cve": "CVE-2021-37671", "id": "pyup.io-41146", "more_info_path": "/vulnerabilities/CVE-2021-37671/41146", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37636: In affected versions the implementation of 'tf.raw_ops.SparseDenseCwiseDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L56) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit d9204be9f49520cdaaeb2541d1dc5187b23f31d9.", "cve": "CVE-2021-37636", "id": "pyup.io-41111", "more_info_path": "/vulnerabilities/CVE-2021-37636/41111", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37635: In affected versions the implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data. The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor. The Tensorflow team has patched the issue in GitHub commit 87158f43f05f2720a374f3e6d22a7aaa3a33f750.", "cve": "CVE-2021-37635", "id": "pyup.io-41110", "more_info_path": "/vulnerabilities/CVE-2021-37635/41110", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37637: It is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid. The Tensorflow team has patched the issue in GitHub commit 5dc7f6981fdaf74c8c5be41f393df705841fb7c5.", "cve": "CVE-2021-37637", "id": "pyup.io-41112", "more_info_path": "/vulnerabilities/CVE-2021-37637/41112", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37689: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. This is caused by the MLIR optimization of 'L2NormalizeReduceAxis' operator. The implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/compiler/mlir/lite/transforms/optimize.cc#L67-L70) unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements. The Tensorflow team has patched the issue in GitHub commit d6b57f461b39fd1aa8c1b870f1b974aac3554955.", "cve": "CVE-2021-37689", "id": "pyup.io-41164", "more_info_path": "/vulnerabilities/CVE-2021-37689/41164", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37667: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.UnicodeEncode'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the 'input_splits' tensor before validating that this tensor is not empty. The Tensorflow team has patched the issue in GitHub commit 2e0ee46f1a47675152d3d865797a18358881d7a6.", "cve": "CVE-2021-37667", "id": "pyup.io-41142", "more_info_path": "/vulnerabilities/CVE-2021-37667/41142", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37683: In affected versions the implementation of division in TFLite is vulnerable to a division by 0 error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc). There is no check that the divisor tensor does not contain zero elements. The Tensorflow team has patched the issue in GitHub commit 1e206baedf8bef0334cca3eb92bab134ef525a28.", "cve": "CVE-2021-37683", "id": "pyup.io-41158", "more_info_path": "/vulnerabilities/CVE-2021-37683/41158", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37680: In affected versions the implementation of fully connected layers in TFLite is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226). The Tensorflow team has patched the issue in GitHub commit 718721986aa137691ee23f03638867151f74935f.", "cve": "CVE-2021-37680", "id": "pyup.io-41155", "more_info_path": "/vulnerabilities/CVE-2021-37680/41155", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37642: In affected versions the implementation of 'tf.raw_ops.ResourceScatterDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit 4aacb30888638da75023e6601149415b39763d76.", "cve": "CVE-2021-37642", "id": "pyup.io-41117", "more_info_path": "/vulnerabilities/CVE-2021-37642/41117", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37648: In affected versions the code for 'tf.raw_ops.SaveV2' does not properly validate the inputs and an attacker can trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses 'ValidateInputs' to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above. However, the validation uses 'OP_REQUIRES' which translates to setting the 'Status' object of the current 'OpKernelContext' to an error status, followed by an empty 'return' statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the nQext line in 'Compute' that follows the call to 'ValidateInputs'. This is equivalent to lacking the validation. The Tensorflow team has patched the issue in GitHub commit 9728c60e136912a12d99ca56e106b7cce7af5986.", "cve": "CVE-2021-37648", "id": "pyup.io-41123", "more_info_path": "/vulnerabilities/CVE-2021-37648/41123", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37664: In affected versions an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range. The Tensorflow team has patched the issue in GitHub commit e84c975313e8e8e38bb2ea118196369c45c51378.", "cve": "CVE-2021-37664", "id": "pyup.io-41139", "more_info_path": "/vulnerabilities/CVE-2021-37664/41139", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37638: Sending invalid argument for 'row_partition_types' of 'tf.raw_ops.RaggedTensorToTensor' API results in a null pointer dereference and undefined behavior. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty. The Tensorflow team has patched the issue in GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314.", "cve": "CVE-2021-37638", "id": "pyup.io-41113", "more_info_path": "/vulnerabilities/CVE-2021-37638/41113", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37651: In affected versions the implementation for 'tf.raw_ops.FractionalAvgPoolGrad' can be tricked into accessing data outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty 'EigenDoubleMatrixMap' and then accesses this buffer with indices that are outside of the empty area. The Tensorflow team has patched the issue in GitHub commit 0f931751fb20f565c4e94aa6df58d54a003cdb30.", "cve": "CVE-2021-37651", "id": "pyup.io-41126", "more_info_path": "/vulnerabilities/CVE-2021-37651/41126", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37639: When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the 'tensor_name' user controlled input and immediately retrieves the tensor at the restoration index (controlled via 'preferred_shard' argument). This occurs without validating that the provided list has enough values. If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements and if the restoration index is outside the bounds, this results in heap OOB read. The Tensorflow team has patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622.", "cve": "CVE-2021-37639", "id": "pyup.io-41114", "more_info_path": "/vulnerabilities/CVE-2021-37639/41114", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37654: In affected versions an attacker can trigger a crash via a 'CHECK'-fail in debug builds of TensorFlow using 'tf.raw_ops.ResourceGather' or a read from outside the bounds of heap allocated data in the same API in a release build. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the 'batch_dims' value that the user supplies is less than the rank of the input tensor. Since the implementation uses several for loops over the dimensions of 'tensor', this results in reading data from outside the bounds of heap allocated buffer backing the tensor. The Tensorflow team has patched the issue in GitHub commit bc9c546ce7015c57c2f15c168b3d9201de679a1d.", "cve": "CVE-2021-37654", "id": "pyup.io-41129", "more_info_path": "/vulnerabilities/CVE-2021-37654/41129", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37647: When a user does not supply arguments that determine a valid sparse tensor, 'tf.raw_ops.SparseTensorSliceDataset' implementation can be made to dereference a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either 'indices' or 'values' are provided for an empty sparse tensor when the other is not. If 'indices' is empty, then code that performs validation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference. If 'indices' as provided by the user is empty, then 'indices' in the C++ code above is backed by an empty 'std::vector', hence calling 'indices->dim_size(0)' results in null pointer dereferencing (same as calling 'std::vector::at()' on an empty vector). The Tensorflow team has patched the issue in GitHub commit 02cc160e29d20631de3859c6653184e3f876b9d7.", "cve": "CVE-2021-37647", "id": "pyup.io-41122", "more_info_path": "/vulnerabilities/CVE-2021-37647/41122", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37652: In affected versions the implementation for 'tf.raw_ops.BoostedTreesCreateEnsemble' can result in a use after free error if an attacker supplies specially crafted arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent 'free'-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed. The Tensorflow team has patched the issue in GitHub commit 5ecec9c6fbdbc6be03295685190a45e7eee726ab.", "cve": "CVE-2021-37652", "id": "pyup.io-41127", "more_info_path": "/vulnerabilities/CVE-2021-37652/41127", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37659: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations). The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr. We have patched the issue in GitHub commit 93f428fd1768df147171ed674fee1fc5ab8309ec.", "cve": "CVE-2021-37659", "id": "pyup.io-41134", "more_info_path": "/vulnerabilities/CVE-2021-37659/41134", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37658: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixSetDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit ff8894044dfae5568ecbf2ed514c1a37dc394f1b.", "cve": "CVE-2021-37658", "id": "pyup.io-41133", "more_info_path": "/vulnerabilities/CVE-2021-37658/41133", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37649: The code for 'tf.raw_ops.UncompressElement' can be made to trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a 'CompressedElement' from a 'Variant' tensor and then proceeds to dereference it for decompressing. There is no check that the 'Variant' tensor contained a 'CompressedElement', so the pointer is actually 'nullptr'. The Tensorflow team has patched the issue in GitHub commit 7bdf50bb4f5c54a4997c379092888546c97c3ebd.", "cve": "CVE-2021-37649", "id": "pyup.io-41124", "more_info_path": "/vulnerabilities/CVE-2021-37649/41124", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37656: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToSparse'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order. The Tensorflow team has patched the issue in GitHub commit 1071f554dbd09f7e101324d366eec5f4fe5a3ece.", "cve": "CVE-2021-37656", "id": "pyup.io-41131", "more_info_path": "/vulnerabilities/CVE-2021-37656/41131", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Several versions of TensorFlow are affected by CVE-2021-37686: In affected versions, the strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for ellipsis in axis definition (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122). An attacker can craft a model such that 'ellipsis_end_idx' is smaller than 'i' (e.g., always negative). In this case, the inner loop does not increase 'i' and the 'continue' statement causes execution to skip over the preincrement at the end of the outer loop. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695.", "cve": "CVE-2021-37686", "id": "pyup.io-41161", "more_info_path": "/vulnerabilities/CVE-2021-37686/41161", "specs": [ ">=2.3.0rc0,<2.3.4rc0", ">=2.4.0rc0,<2.4.3rc0", ">=2.5.0rc0,<=2.5.0", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4rc0,>=2.4.0rc0,<2.4.3rc0,>=2.5.0rc0,<=2.5.0,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.4.0 includes a fix for CVE-2020-26269: In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.", "cve": "CVE-2020-26269", "id": "pyup.io-40796", "more_info_path": "/vulnerabilities/CVE-2020-26269/40796", "specs": [ ">=2.4.0rc0,<2.4.0" ], "v": ">=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow 2.5.0, 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29614: The implementation of 'tf.io.decode_raw' produces incorrect results and crashes the Python interpreter when combining 'fixed_length' and wider datatypes. The implementation of the padded version (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc) is buggy due to a confusion about pointer arithmetic rules. First, the code computes (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L61) the width of each output element by dividing the 'fixed_length' value to the size of the type argument. The 'fixed_length' argument is also used to determine the size needed for the output tensor (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L63-L79). This is followed by reencoding code (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L85-L94). The erroneous code is the last line above: it is moving the 'out_data' pointer by 'fixed_length * sizeof (T)' bytes whereas it only copied at most 'fixed_length' bytes from the input. This results in parts of the input not being decoded into the output. Furthermore, because the pointer advance is far wider than desired, this quickly leads to writing to outside the bounds of the backing data. This OOB write leads to interpreter crash in the reproducer mentioned here, but more severe attacks can be mounted too, given that this gadget allows writing to periodically placed locations in memory.", "cve": "CVE-2021-29614", "id": "pyup.io-40472", "more_info_path": "/vulnerabilities/CVE-2021-29614/40472", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.5.0rc0,<2.5.0" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.5.0rc0,<2.5.0" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29549: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero. Since `vector_num_elements` is determined based on input shapes (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L522-L544), a user can trigger scenarios where this quantity is 0.", "cve": "CVE-2021-29549", "id": "pyup.io-40706", "more_info_path": "/vulnerabilities/CVE-2021-29549/40706", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv2DBackpropInput'. See CVE-2021-29525.", "cve": "CVE-2021-29525", "id": "pyup.io-40684", "more_info_path": "/vulnerabilities/CVE-2021-29525/40684", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a stack overflow in 'ParseAttrValue' with nested tensors. See CVE-2021-29615.", "cve": "CVE-2021-29615", "id": "pyup.io-40767", "more_info_path": "/vulnerabilities/CVE-2021-29615/40767", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.5.0, 2.4.2, 2.3.3, 2.2.3 and 2.1.4 include a fix for CVE-2021-29548: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the op's contract (https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization).", "cve": "CVE-2021-29548", "id": "pyup.io-40468", "more_info_path": "/vulnerabilities/CVE-2021-29548/40468", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a 'CHECK'-fail in 'SparseCross' caused by type confusion. See CVE-2021-29519.", "cve": "CVE-2021-29519", "id": "pyup.io-40678", "more_info_path": "/vulnerabilities/CVE-2021-29519/40678", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29552: An attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar. Since the tensor is empty the `CHECK` involved in `.scalar()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination.", "cve": "CVE-2021-29552", "id": "pyup.io-40710", "more_info_path": "/vulnerabilities/CVE-2021-29552/40710", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29513: Calling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences. The conversion from Python array to C++ array (https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion.", "cve": "CVE-2021-29513", "id": "pyup.io-40465", "more_info_path": "/vulnerabilities/CVE-2021-29513/40465", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by invalid validation in 'SparseMatrixSparseCholesky'. See CVE-2021-29530.", "cve": "CVE-2021-29530", "id": "pyup.io-40688", "more_info_path": "/vulnerabilities/CVE-2021-29530/40688", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix vulnerabilities where session operations in eager mode lead to null pointer dereferences. See CVE-2021-29518.", "cve": "CVE-2021-29518", "id": "pyup.io-40677", "more_info_path": "/vulnerabilities/CVE-2021-29518/40677", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29538: An attacker can cause a division by zero to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments). If all shapes are empty then 'work_unit_size' is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service.", "cve": "CVE-2021-29538", "id": "pyup.io-40697", "more_info_path": "/vulnerabilities/CVE-2021-29538/40697", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29534: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.SparseConcat'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/b432a38fe0e1b4b904a6c222cbce794c39703e87/tensorflow/core/kernels/sparse_concat_op.cc#L76) takes the values specified in 'shapes[0]' as dimensions for the output shape. The 'TensorShape' constructor (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a 'CHECK' operation which triggers when 'InitDims' (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status. This is a legacy implementation of the constructor and operations should use 'BuildTensorShapeBase' or 'AddDimWithStatus' to prevent 'CHECK'-failures in the presence of overflows.", "cve": "CVE-2021-29534", "id": "pyup.io-40694", "more_info_path": "/vulnerabilities/CVE-2021-29534/40694", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a 'CHECK'-fail in 'AddManySparseToTensorsMap'. See CVE-2021-29523.", "cve": "CVE-2021-29523", "id": "pyup.io-40682", "more_info_path": "/vulnerabilities/CVE-2021-29523/40682", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix fixes a heap buffer overflow caused by rounding. See CVE-2021-29529.", "cve": "CVE-2021-29529", "id": "pyup.io-40689", "more_info_path": "/vulnerabilities/CVE-2021-29529/40689", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv3DBackprop*'. See CVE-2021-29522.", "cve": "CVE-2021-29522", "id": "pyup.io-40681", "more_info_path": "/vulnerabilities/CVE-2021-29522/40681", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29537: An attacker can cause a heap buffer overflow in `QuantizedResizeBilinear` by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/50711818d2e61ccce012591eeb4fdf93a8496726/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L705-L706) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly.", "cve": "CVE-2021-29537", "id": "pyup.io-40695", "more_info_path": "/vulnerabilities/CVE-2021-29537/40695", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'tf.raw_ops.EncodePng'. See CVE-2021-29531.", "cve": "CVE-2021-29531", "id": "pyup.io-40690", "more_info_path": "/vulnerabilities/CVE-2021-29531/40690", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29532: An attacker can force accesses outside the bounds of heap allocated arrays by passing in invalid tensor values to `tf.raw_ops.RaggedCross`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/efea03b38fb8d3b81762237dc85e579cc5fc6e87/tensorflow/core/kernels/ragged_cross_op.cc#L456-L487) lacks validation for the user supplied arguments. Each of the above branches call a helper function after accessing array elements via a `*_list[next_*]` pattern, followed by incrementing the `next_*` index. However, as there is no validation that the `next_*` values are in the valid range for the corresponding `*_list` arrays, this results in heap OOB reads.", "cve": "CVE-2021-29532", "id": "pyup.io-40691", "more_info_path": "/vulnerabilities/CVE-2021-29532/40691", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29539: TensorFlow is an end-to-end open source platform for machine learning. Calling `tf.raw_ops.ImmutableConst`(https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars. We have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. If using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument.", "cve": "CVE-2021-29539", "id": "pyup.io-40467", "more_info_path": "/vulnerabilities/CVE-2021-29539/40467", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 includes a fix for CVE-2021-29533: An attacker can trigger a denial of service via a 'CHECK' failure by passing an empty image to 'tf.raw_ops.DrawBoundingBoxes'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/ea34a18dc3f5c8d80a40ccca1404f343b5d55f91/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L148-L165) uses 'CHECK_*' assertions instead of 'OP_REQUIRES' to validate user controlled inputs. Whereas 'OP_REQUIRES' allows returning an error condition back to the user, the 'CHECK_*' macros result in a crash if the condition is false, similar to 'assert'. In this case, 'height' is 0 from the 'images' input. This results in 'max_box_row_clamp' being negative and the assertion being falsified, followed by aborting program execution.", "cve": "CVE-2021-29533", "id": "pyup.io-40692", "more_info_path": "/vulnerabilities/CVE-2021-29533/40692", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv2DBackpropFilter'. See CVE-2021-29524.", "cve": "CVE-2021-29524", "id": "pyup.io-40683", "more_info_path": "/vulnerabilities/CVE-2021-29524/40683", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a heap buffer overflow in 'Conv3DBackprop*'. See CVE-2021-29520.", "cve": "CVE-2021-29520", "id": "pyup.io-40680", "more_info_path": "/vulnerabilities/CVE-2021-29520/40680", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a segfault in 'SparseCountSparseOutput'. See CVE-2021-29521.", "cve": "CVE-2021-29521", "id": "pyup.io-40679", "more_info_path": "/vulnerabilities/CVE-2021-29521/40679", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'StringNGrams'. See CVE-2021-29541.", "cve": "CVE-2021-29541", "id": "pyup.io-40700", "more_info_path": "/vulnerabilities/CVE-2021-29541/40700", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29535: An attacker can cause a heap buffer overflow in 'QuantizedMul' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/87cf4d3ea9949051e50ca3f071fc909538a51cd0/tensorflow/core/kernels/quantized_mul_op.cc#L287-L290) assumes that the 4 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29535", "id": "pyup.io-40693", "more_info_path": "/vulnerabilities/CVE-2021-29535/40693", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'StringNGrams'. See CVE-2021-29542.", "cve": "CVE-2021-29542", "id": "pyup.io-40699", "more_info_path": "/vulnerabilities/CVE-2021-29542/40699", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29536: An attacker can cause a heap buffer overflow in 'QuantizedReshape' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/a324ac84e573fba362a5e53d4e74d5de6729933e/tensorflow/core/kernels/quantized_reshape_op.cc#L38-L55) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29536", "id": "pyup.io-40696", "more_info_path": "/vulnerabilities/CVE-2021-29536/40696", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29544: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.QuantizeAndDequantizeV4Grad'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the 'input_*' tensors. In turn, this results in the tensors being passes as they are to 'QuantizeAndDequantizePerChannelGradientImpl' (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306). However, the 'vec' method, requires the rank to 1 and triggers a 'CHECK' failure otherwise.", "cve": "CVE-2021-29544", "id": "pyup.io-40701", "more_info_path": "/vulnerabilities/CVE-2021-29544/40701", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29543: An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks.", "cve": "CVE-2021-29543", "id": "pyup.io-40702", "more_info_path": "/vulnerabilities/CVE-2021-29543/40702", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29540: TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L495-L497) computes the size of the filter tensor but does not validate that it matches the number of elements in 'filter_sizes'. Later, when reading/writing to this buffer, code uses the value computed here, instead of the number of elements in the tensor.", "cve": "CVE-2021-29540", "id": "pyup.io-40698", "more_info_path": "/vulnerabilities/CVE-2021-29540/40698", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update its dependency 'curl' to version 7.76.0 to handle CVE-2020-8169.", "cve": "CVE-2020-8169", "id": "pyup.io-40772", "more_info_path": "/vulnerabilities/CVE-2020-8169/40772", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in 'Conv3D'. See CVE-2021-29517.", "cve": "CVE-2021-29517", "id": "pyup.io-40676", "more_info_path": "/vulnerabilities/CVE-2021-29517/40676", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix fixes a null pointer dereference via invalid Ragged Tensors. See CVE-2021-29516.", "cve": "CVE-2021-29516", "id": "pyup.io-40675", "more_info_path": "/vulnerabilities/CVE-2021-29516/40675", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a reference binding to null pointer in 'MatrixDiag*' ops. See CVE-2021-29515.", "cve": "CVE-2021-29515", "id": "pyup.io-40673", "more_info_path": "/vulnerabilities/CVE-2021-29515/40673", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'EmbeddingLookup'. See CVE-2021-29596.", "cve": "CVE-2021-29596", "id": "pyup.io-40748", "more_info_path": "/vulnerabilities/CVE-2021-29596/40748", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's convolution code. See CVE-2021-29594.", "cve": "CVE-2021-29594", "id": "pyup.io-40747", "more_info_path": "/vulnerabilities/CVE-2021-29594/40747", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29558: An attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset.", "cve": "CVE-2021-29558", "id": "pyup.io-40715", "more_info_path": "/vulnerabilities/CVE-2021-29558/40715", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29551: The implementation of 'MatrixTriangularSolve' (https://github.com/tensorflow/tensorflow/blob/8cae746d8449c7dda5298327353d68613f16e798/tensorflow/core/kernels/linalg/matrix_triangular_solve_op_impl.h#L160-L240) fails to terminate kernel execution if one validation condition fails.", "cve": "CVE-2021-29551", "id": "pyup.io-40708", "more_info_path": "/vulnerabilities/CVE-2021-29551/40708", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29545: An attacker can trigger a denial of service via a 'CHECK'-fail in converting sparse tensors to CSR Sparse matrices. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/800346f2c03a27e182dd4fba48295f65e7790739/tensorflow/core/kernels/sparse/kernels.cc#L66) does a double redirection to access an element of an array allocated on the heap. If the value at 'indices(i, 0)' is such that 'indices(i, 0) + 1' is outside the bounds of 'csr_row_ptr', this results in writing outside of bounds of heap allocated data.", "cve": "CVE-2021-29545", "id": "pyup.io-40703", "more_info_path": "/vulnerabilities/CVE-2021-29545/40703", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in TFLite's 'Reshape' operator. See CVE-2021-29592.", "cve": "CVE-2021-29592", "id": "pyup.io-40744", "more_info_path": "/vulnerabilities/CVE-2021-29592/40744", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29617: An attacker can cause a denial of service via `CHECK`-fail in `tf.strings.substr` with invalid arguments.", "cve": "CVE-2021-29617", "id": "pyup.io-40770", "more_info_path": "/vulnerabilities/CVE-2021-29617/40770", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a segfault in 'CTCBeamSearchDecoder'. See CVE-2021-29581.", "cve": "CVE-2021-29581", "id": "pyup.io-40734", "more_info_path": "/vulnerabilities/CVE-2021-29581/40734", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an undefined behavior in 'MaxPool3DGradGrad'. See CVE-2021-29574.", "cve": "CVE-2021-29574", "id": "pyup.io-40728", "more_info_path": "/vulnerabilities/CVE-2021-29574/40728", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 include a fix for CVE-2021-29512: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433). Before the 'for' loop, 'batch_idx' is set to 0. The user controls the 'splits' array, making it contain only one element, 0. Thus, the code in the 'while' loop would increment 'batch_idx' and then try to read 'splits(1)', which is outside of bounds.", "cve": "CVE-2021-29512", "id": "pyup.io-40464", "more_info_path": "/vulnerabilities/CVE-2021-29512/40464", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29556: An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.Reverse`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/36229ea9e9451dac14a8b1f4711c435a1d84a594/tensorflow/core/kernels/reverse_op.cc#L75-L76) performs a division based on the first dimension of the tensor argument.", "cve": "CVE-2021-29556", "id": "pyup.io-40714", "more_info_path": "/vulnerabilities/CVE-2021-29556/40714", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'tf.raw_ops.CTCLoss'. See CVE-2021-29613.", "cve": "CVE-2021-29613", "id": "pyup.io-40766", "more_info_path": "/vulnerabilities/CVE-2021-29613/40766", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'Conv2D'. See CVE-2021-29526.", "cve": "CVE-2021-29526", "id": "pyup.io-40685", "more_info_path": "/vulnerabilities/CVE-2021-29526/40685", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'LoadAndRemapMatrix'. See CVE-2021-29561.", "cve": "CVE-2021-29561", "id": "pyup.io-40718", "more_info_path": "/vulnerabilities/CVE-2021-29561/40718", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'QuantizedConv2D'. See CVE-2021-29527.", "cve": "CVE-2021-29527", "id": "pyup.io-40686", "more_info_path": "/vulnerabilities/CVE-2021-29527/40686", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29595: The implementation of the `DepthToSpace` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69). An attacker can craft a model such that `params->block_size` is 0.", "cve": "CVE-2021-29595", "id": "pyup.io-40746", "more_info_path": "/vulnerabilities/CVE-2021-29595/40746", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29585: The TFLite computation for size of output after padding, `ComputeOutSize`(https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division. Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0.", "cve": "CVE-2021-29585", "id": "pyup.io-40738", "more_info_path": "/vulnerabilities/CVE-2021-29585/40738", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'TransposeConv'. See CVE-2021-29588.", "cve": "CVE-2021-29588", "id": "pyup.io-40742", "more_info_path": "/vulnerabilities/CVE-2021-29588/40742", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB access in unicode ops. See CVE-2021-29559.", "cve": "CVE-2021-29559", "id": "pyup.io-40716", "more_info_path": "/vulnerabilities/CVE-2021-29559/40716", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29589: The reference implementation of the `GatherNd` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/reference_ops.h#L966). An attacker can craft a model such that `params` input would be an empty tensor. In turn, `params_shape.Dims(.)` would be zero, in at least one dimension.", "cve": "CVE-2021-29589", "id": "pyup.io-40741", "more_info_path": "/vulnerabilities/CVE-2021-29589/40741", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'FusedBatchNorm'. See CVE-2021-29555.", "cve": "CVE-2021-29555", "id": "pyup.io-40712", "more_info_path": "/vulnerabilities/CVE-2021-29555/40712", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap out of bounds read in 'MaxPoolGradWithArgmax'. See CVE-2021-29570.", "cve": "CVE-2021-29570", "id": "pyup.io-40724", "more_info_path": "/vulnerabilities/CVE-2021-29570/40724", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'BandedTriangularSolve'. See CVE-2021-29612.", "cve": "CVE-2021-29612", "id": "pyup.io-40765", "more_info_path": "/vulnerabilities/CVE-2021-29612/40765", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29514: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L446). Before the 'for' loop, 'batch_idx' is set to 0. The attacker sets 'splits(0)' to be 7, hence the 'while' loop does not execute and 'batch_idx' remains 0. This then results in writing to 'out(-1, bin)', which is before the heap allocated buffer for the output tensor.", "cve": "CVE-2021-29514", "id": "pyup.io-40466", "more_info_path": "/vulnerabilities/CVE-2021-29514/40466", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'SparseMatMul'. See CVE-2021-29557.", "cve": "CVE-2021-29557", "id": "pyup.io-40713", "more_info_path": "/vulnerabilities/CVE-2021-29557/40713", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'MaxPoolGrad'. See CVE-2021-29579.", "cve": "CVE-2021-29579", "id": "pyup.io-40733", "more_info_path": "/vulnerabilities/CVE-2021-29579/40733", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29566: An attacker can write outside the bounds of heap allocated arrays by passing invalid arguments to 'tf.raw_ops.Dilation2DBackpropInput'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/afd954e65f15aea4d438d0a219136fc4a63a573d/tensorflow/core/kernels/dilation_ops.cc#L321-L322) does not validate before writing to the output array. The values for 'h_out' and 'w_out' are guaranteed to be in range for 'out_backprop' (as they are loop indices bounded by the size of the array). However, there are no similar guarantees relating 'h_in_max'/'w_in_max' and 'in_backprop'.", "cve": "CVE-2021-29566", "id": "pyup.io-40722", "more_info_path": "/vulnerabilities/CVE-2021-29566/40722", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap out of bounds read in 'RequantizationRange'. See CVE-2021-29569.", "cve": "CVE-2021-29569", "id": "pyup.io-40725", "more_info_path": "/vulnerabilities/CVE-2021-29569/40725", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB in 'QuantizeAndDequantizeV3'. See CVE-2021-29553.", "cve": "CVE-2021-29553", "id": "pyup.io-40709", "more_info_path": "/vulnerabilities/CVE-2021-29553/40709", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'Split'. See CVE-2021-29599.", "cve": "CVE-2021-29599", "id": "pyup.io-40752", "more_info_path": "/vulnerabilities/CVE-2021-29599/40752", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update its dependency \"curl\" to v7.76.0 to include security fixes.", "cve": "CVE-2020-8231", "id": "pyup.io-40774", "more_info_path": "/vulnerabilities/CVE-2020-8231/40774", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'EditDistance'. See CVE-2021-29564.", "cve": "CVE-2021-29564", "id": "pyup.io-40721", "more_info_path": "/vulnerabilities/CVE-2021-29564/40721", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of hashtable lookup. See CVE-2021-29604.", "cve": "CVE-2021-29604", "id": "pyup.io-40755", "more_info_path": "/vulnerabilities/CVE-2021-29604/40755", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'QuantizedMul'. See CVE-2021-29528.", "cve": "CVE-2021-29528", "id": "pyup.io-40687", "more_info_path": "/vulnerabilities/CVE-2021-29528/40687", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'OneHot'. See CVE-2021-29600.", "cve": "CVE-2021-29600", "id": "pyup.io-40753", "more_info_path": "/vulnerabilities/CVE-2021-29600/40753", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29550: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values. The user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor operation results in `output_size[i]` being 0. The `DCHECK_GT` line is a no-op outside of debug mode, so in released versions of TF this does not trigger. Later, these computed values are used as arguments (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to `GeneratePoolingSequence`(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation. Since `output_length` can be 0, this results in runtime crashing.", "cve": "CVE-2021-29550", "id": "pyup.io-40707", "more_info_path": "/vulnerabilities/CVE-2021-29550/40707", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29568: An attacker can trigger undefined behavior by binding to null pointer in `tf.raw_ops.ParameterizedTruncatedNormal`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/3f6fe4dfef6f57e768260b48166c27d148f3015f/tensorflow/core/kernels/parameterized_truncated_normal_op.cc#L630) does not validate input arguments before accessing the first element of `shape`. If `shape` argument is empty, then `shape_tensor.flat()` is an empty array.", "cve": "CVE-2021-29568", "id": "pyup.io-40723", "more_info_path": "/vulnerabilities/CVE-2021-29568/40723", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'BatchToSpaceNd'. See CVE-2021-29593.", "cve": "CVE-2021-29593", "id": "pyup.io-40749", "more_info_path": "/vulnerabilities/CVE-2021-29593/40749", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29610: The validation in 'tf.raw_ops.QuantizeAndDequantizeV2' allows invalid values for 'axis' argument:. The validation (https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses '||' to mix two different conditions. If 'axis_ < -1' the condition in 'OP_REQUIRES' will still be true, but this value of 'axis_' results in heap underflow. This allows attackers to read/write to other data on the heap.", "cve": "CVE-2021-29610", "id": "pyup.io-40764", "more_info_path": "/vulnerabilities/CVE-2021-29610/40764", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'SparseFillEmptyRows'. See CVE-2021-29565.", "cve": "CVE-2021-29565", "id": "pyup.io-40778", "more_info_path": "/vulnerabilities/CVE-2021-29565/40778", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29587: TensorFlow is an end-to-end open source platform for machine learning. The `Prepare` step of the `SpaceToDepth` TFLite operator does not check for 0 before division (https://github.com/tensorflow/tensorflow/blob/5f7975d09eac0f10ed8a17dbb6f5964977725adc/tensorflow/lite/kernels/space_to_depth.cc#L63-L67). An attacker can craft a model such that `params->block_size` would be zero.", "cve": "CVE-2021-29587", "id": "pyup.io-40740", "more_info_path": "/vulnerabilities/CVE-2021-29587/40740", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB read in 'tf.raw_ops.Dequantize'. See CVE-2021-29582.", "cve": "CVE-2021-29582", "id": "pyup.io-40735", "more_info_path": "/vulnerabilities/CVE-2021-29582/40735", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'DepthwiseConv'. See CVE-2021-29602.", "cve": "CVE-2021-29602", "id": "pyup.io-40754", "more_info_path": "/vulnerabilities/CVE-2021-29602/40754", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 updates 'curl' to '7.76.0' to handle CVE-2020-8286: curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response.", "cve": "CVE-2020-8286", "id": "pyup.io-40777", "more_info_path": "/vulnerabilities/CVE-2020-8286/40777", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB read in TFLite's implementation of 'Minimum' or 'Maximum'. See CVE-2021-29590.", "cve": "CVE-2021-29590", "id": "pyup.io-40743", "more_info_path": "/vulnerabilities/CVE-2021-29590/40743", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseAdd'. See CVE-2021-29609.", "cve": "CVE-2021-29609", "id": "pyup.io-40761", "more_info_path": "/vulnerabilities/CVE-2021-29609/40761", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'MaxPoolGradWithArgmax'. See CVE-2021-29573.", "cve": "CVE-2021-29573", "id": "pyup.io-40727", "more_info_path": "/vulnerabilities/CVE-2021-29573/40727", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29546: TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger an integer division by zero undefined behavior in `tf.raw_ops.QuantizedBiasAdd`. This is because the implementation of the Eigen kernel (https://github.com/tensorflow/tensorflow/blob/61bca8bd5ba8a68b2d97435ddfafcdf2b85672cd/tensorflow/core/kernels/quantization_utils.h#L812-L849) does a division by the number of elements of the smaller input (based on shape) without checking that this is not zero.", "cve": "CVE-2021-29546", "id": "pyup.io-40704", "more_info_path": "/vulnerabilities/CVE-2021-29546/40704", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a integer overflow in TFLite memory allocation. See CVE-2021-29605.", "cve": "CVE-2021-29605", "id": "pyup.io-40757", "more_info_path": "/vulnerabilities/CVE-2021-29605/40757", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in optimized pooling implementations in TFLite. See CVE-2021-29586.", "cve": "CVE-2021-29586", "id": "pyup.io-40739", "more_info_path": "/vulnerabilities/CVE-2021-29586/40739", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'tf.raw_ops.IRFFT'. See CVE-2021-29562.", "cve": "CVE-2021-29562", "id": "pyup.io-40719", "more_info_path": "/vulnerabilities/CVE-2021-29562/40719", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29560: An attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel. Since the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when 'parent_output_index' is shorter than 'row_split'.", "cve": "CVE-2021-29560", "id": "pyup.io-40717", "more_info_path": "/vulnerabilities/CVE-2021-29560/40717", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'AvgPool3DGrad'. See CVE-2021-29577.", "cve": "CVE-2021-29577", "id": "pyup.io-40730", "more_info_path": "/vulnerabilities/CVE-2021-29577/40730", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow versions 2.5.0, 2.4.2, 2.3.3, 2.2.3 and 2.1.4 updates its dependency \"curl\" to a secure version (7.76.0).", "cve": "CVE-2020-8285", "id": "pyup.io-40776", "more_info_path": "/vulnerabilities/CVE-2020-8285/40776", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB write in TFLite. See CVE-2021-29603.", "cve": "CVE-2021-29603", "id": "pyup.io-40758", "more_info_path": "/vulnerabilities/CVE-2021-29603/40758", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a integer overflow in TFLite concatentation. See CVE-2021-29601.", "cve": "CVE-2021-29601", "id": "pyup.io-40756", "more_info_path": "/vulnerabilities/CVE-2021-29601/40756", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'SpaceToBatchNd'. See CVE-2021-29597.", "cve": "CVE-2021-29597", "id": "pyup.io-40750", "more_info_path": "/vulnerabilities/CVE-2021-29597/40750", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail due to integer overflow. See CVE-2021-29584.", "cve": "CVE-2021-29584", "id": "pyup.io-40736", "more_info_path": "/vulnerabilities/CVE-2021-29584/40736", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29618: Passing a complex argument to `tf.transpose` at the same time as passing 'conjugate=True' argument results in a crash.", "cve": "CVE-2021-29618", "id": "pyup.io-40769", "more_info_path": "/vulnerabilities/CVE-2021-29618/40769", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29583: The implementation of 'tf.raw_ops.FusedBatchNorm' is vulnerable to a heap buffer overflow. If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers. The implementation(https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that 'scale', 'offset', 'mean' and 'variance' (the last two only when required) all have the same number of elements as the number of channels of 'x'. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary. If the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior.", "cve": "CVE-2021-29583", "id": "pyup.io-40737", "more_info_path": "/vulnerabilities/CVE-2021-29583/40737", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix fixes a heap OOB read in TFLite. See CVE-2021-29606.", "cve": "CVE-2021-29606", "id": "pyup.io-40759", "more_info_path": "/vulnerabilities/CVE-2021-29606/40759", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29571: The implementation of 'tf.raw_ops.MaxPoolGradWithArgmax' can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation (https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of 'boxes' input is 4, as required by the op (https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption. If the last dimension in 'boxes' is less than 4, accesses similar to 'tboxes(b, bb, 3)' will access data outside of bounds. Further during code execution there are also writes to these indices.", "cve": "CVE-2021-29571", "id": "pyup.io-40470", "more_info_path": "/vulnerabilities/CVE-2021-29571/40470", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update 'curl' to '7.76.0' to handle CVE-2020-8177.", "cve": "CVE-2020-8177", "id": "pyup.io-40773", "more_info_path": "/vulnerabilities/CVE-2020-8177/40773", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an undefined behavior and a 'CHECK'-fail in 'FractionalMaxPoolGrad'. See CVE-2021-29580.", "cve": "CVE-2021-29580", "id": "pyup.io-40731", "more_info_path": "/vulnerabilities/CVE-2021-29580/40731", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'SVDF'. See CVE-2021-29598.", "cve": "CVE-2021-29598", "id": "pyup.io-40751", "more_info_path": "/vulnerabilities/CVE-2021-29598/40751", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'DenseCountSparseOutput'. See CVE-2021-29554.", "cve": "CVE-2021-29554", "id": "pyup.io-40711", "more_info_path": "/vulnerabilities/CVE-2021-29554/40711", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29547: An attacker can cause a segfault and denial of service via accessing data outside of bounds in 'tf.raw_ops.QuantizedBatchNormWithGlobalNormalization'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc#L176-L189) assumes the inputs are not empty. If any of these inputs is empty, '.flat()' is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds.", "cve": "CVE-2021-29547", "id": "pyup.io-40705", "more_info_path": "/vulnerabilities/CVE-2021-29547/40705", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29608: TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in 'tf.raw_ops.RaggedTensorToTensor', an attacker can exploit an undefined behavior if input arguments are empty. The implementation (https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones. There are multiple 'DCHECK' validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything.", "cve": "CVE-2021-29608", "id": "pyup.io-40760", "more_info_path": "/vulnerabilities/CVE-2021-29608/40760", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.5.0, 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29572: The implementation of `tf.raw_ops.SdcaOptimizer` triggers undefined behavior due to dereferencing a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/60a45c8b6192a4699f2e2709a2645a751d435cc3/tensorflow/core/kernels/sdca_internal.cc) does not validate that the user supplied arguments satisfy all constraints expected by the op(https://www.tensorflow.org/api_docs/python/tf/raw_ops/SdcaOptimizer).", "cve": "CVE-2021-29572", "id": "pyup.io-40471", "more_info_path": "/vulnerabilities/CVE-2021-29572/40471", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'FractionalAvgPoolGrad'. See CVE-2021-29578.", "cve": "CVE-2021-29578", "id": "pyup.io-40732", "more_info_path": "/vulnerabilities/CVE-2021-29578/40732", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseSparseMinimum'. See CVE-2021-29607.", "cve": "CVE-2021-29607", "id": "pyup.io-40762", "more_info_path": "/vulnerabilities/CVE-2021-29607/40762", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseReshape'. See CVE-2021-29611.", "cve": "CVE-2021-29611", "id": "pyup.io-40763", "more_info_path": "/vulnerabilities/CVE-2021-29611/40763", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29616: The implementation of TrySimplify (https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/grappler/optimizers/arithmetic_optimizer.cc#L390-L401) has undefined behavior due to dereferencing a null pointer in corner cases that result in optimizing a node with no inputs.", "cve": "CVE-2021-29616", "id": "pyup.io-40768", "more_info_path": "/vulnerabilities/CVE-2021-29616/40768", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29563: An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`. Eigen code operating on an empty matrix can trigger on an assertion and will cause program termination.", "cve": "CVE-2021-29563", "id": "pyup.io-40720", "more_info_path": "/vulnerabilities/CVE-2021-29563/40720", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an overflow and a denial of service in 'tf.raw_ops.ReverseSequence'. See CVE-2021-29575.", "cve": "CVE-2021-29575", "id": "pyup.io-40726", "more_info_path": "/vulnerabilities/CVE-2021-29575/40726", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a stack overflow due to looping TFLite subgraph. See CVE-2021-29591.", "cve": "CVE-2021-29591", "id": "pyup.io-40745", "more_info_path": "/vulnerabilities/CVE-2021-29591/40745", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a segfault in 'tf.raw_ops.SparseCountSparseOutput'. See CVE-2021-29619.", "cve": "CVE-2021-29619", "id": "pyup.io-40771", "more_info_path": "/vulnerabilities/CVE-2021-29619/40771", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 update its dependency \"curl\" to handle CVE-2020-8284.", "cve": "CVE-2020-8284", "id": "pyup.io-40775", "more_info_path": "/vulnerabilities/CVE-2020-8284/40775", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'MaxPool3DGradGrad'. See CVE-2021-29576.", "cve": "CVE-2021-29576", "id": "pyup.io-40729", "more_info_path": "/vulnerabilities/CVE-2021-29576/40729", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37645: In affected versions the implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit 96f364a1ca3009f98980021c4b32be5fdcca33a1.", "cve": "CVE-2021-37645", "id": "pyup.io-41120", "more_info_path": "/vulnerabilities/CVE-2021-37645/41120", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37691: In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). The Tensorflow team has patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9.", "cve": "CVE-2021-37691", "id": "pyup.io-41167", "more_info_path": "/vulnerabilities/CVE-2021-37691/41167", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37688: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer. The Tensorflow team has patched the issue in GitHub commit 15691e456c7dc9bd6be203b09765b063bf4a380c.", "cve": "CVE-2021-37688", "id": "pyup.io-41163", "more_info_path": "/vulnerabilities/CVE-2021-37688/41163", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "TensorFlow 2.5.1 and 2.6.0 include a fix for CVE-2021-37640: In affected versions the implementation of 'tf.raw_ops.SparseReshape' can be made to trigger an integral division by 0 exception. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements. The reshape functor (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0. The Tensorflow team has patched the issue in GitHub commit 4923de56ec94fff7770df259ab7f2288a74feb41.", "cve": "CVE-2021-37640", "id": "pyup.io-41115", "more_info_path": "/vulnerabilities/CVE-2021-37640/41115", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow versions 2.5.1 and 2.6.0 include a fix for CVE-2021-37692:\r\nIn affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, \"C.TF_TString_Dealloc\" is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until \"NewTensor\" returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. The Tensorflow team has patched the issue in GitHub commit:\r\nhttps://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22\r\nhttps://github.com/tensorflow/tensorflow/pull/50508\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cmgw-8vpc-rc59", "cve": "CVE-2021-37692", "id": "pyup.io-41168", "more_info_path": "/vulnerabilities/CVE-2021-37692/41168", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow versions 2.3.4, 2.4.3, 2.5.1, and 2.6.0 update its dependency \"curl\" to include a fix for CVE-2021-22898", "cve": "CVE-2021-22898", "id": "pyup.io-41105", "more_info_path": "/vulnerabilities/CVE-2021-22898/41105", "specs": [ ">=2.6.0a1,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0a1,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37657: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. The Tensorflow team has checked that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit f2a673bd34f0d64b8e40a551ac78989d16daad09.", "cve": "CVE-2021-37657", "id": "pyup.io-41132", "more_info_path": "/vulnerabilities/CVE-2021-37657/41132", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37665:\r\nIn affected versions, due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the \"input\" tensor. A similar issue occurs in \"MklRequantizePerChannelOp\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments. The Tensorflow team has patched the issue in GitHub commit 9e62869465573cb2d9b5053f1fa02a81fce21d69 and in the Github commit 203214568f5bc237603dbab6e1fd389f1572f5c9.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v82p-hv3v-p6qp\r\nhttps://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9\r\nhttps://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69", "cve": "CVE-2021-37665", "id": "pyup.io-41140", "more_info_path": "/vulnerabilities/CVE-2021-37665/41140", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37675: In affected versions most implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations. The Tensorflow team has patched the issue in GitHub commit 8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4.", "cve": "CVE-2021-37675", "id": "pyup.io-41150", "more_info_path": "/vulnerabilities/CVE-2021-37675/41150", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37653: In affected versions an attacker can trigger a crash via a floating point exception in 'tf.raw_ops.ResourceGather'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, 'batch_size', and then divides by it without checking that this value is not 0. The Tensorflow team has patched the issue in GitHub commit ac117ee8a8ea57b73d34665cdf00ef3303bc0b11.", "cve": "CVE-2021-37653", "id": "pyup.io-41128", "more_info_path": "/vulnerabilities/CVE-2021-37653/41128", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37676: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.SparseFillEmptyRows'. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors. The Tensorflow team has patched the issue in GitHub commit 578e634b4f1c1c684d4b4294f9e5281b2133b3ed.", "cve": "CVE-2021-37676", "id": "pyup.io-41151", "more_info_path": "/vulnerabilities/CVE-2021-37676/41151", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37663:\r\nIn affected versions, due to incomplete validation in \"tf.raw_ops.QuantizeV2\", an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that \"min_range\" and \"max_range\" both have the same non-zero number of elements. If \"axis\" is provided (i.e., not \"-1\"), then validation should check that it is a value in range for the rank of \"input\" tensor and then the lengths of \"min_range\" and \"max_range\" inputs match the \"axis\" dimension of the \"input\" tensor. The Tensorflow team has patched the issue in GitHub commit 6da6620efad397c85493b8f8667b821403516708. \r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g25h-jr74-qp5j\r\nhttps://github.com/tensorflow/tensorflow/commit/6da6620efad397c85493b8f8667b821403516708", "cve": "CVE-2021-37663", "id": "pyup.io-41138", "more_info_path": "/vulnerabilities/CVE-2021-37663/41138", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37660: In affected versions an attacker can cause a floating point exception by calling inplace operations with crafted arguments that would result in a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/inplace_ops.cc#L283) has a logic error: it should skip processing if 'x' and 'v' are empty but the code uses '||' instead of '&&'. The Tensorflow team has patched the issue in GitHub commit e86605c0a336c088b638da02135ea6f9f6753618.", "cve": "CVE-2021-37660", "id": "pyup.io-41135", "more_info_path": "/vulnerabilities/CVE-2021-37660/41135", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37668:\r\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.UnravelIndex\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by \"dims\" is not empty. Hence, if one element of \"dims\" is 0, the implementation does a division by 0. The Tensorflow team has patched the issue in GitHub commit a776040a5e7ebf76eeb7eb923bf1ae417dd4d233.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2wmv-37vq-52g5\r\nhttps://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233", "cve": "CVE-2021-37668", "id": "pyup.io-41143", "more_info_path": "/vulnerabilities/CVE-2021-37668/41143", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37685: In affected versions TFLite's 'expand_dims.cc' (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data. If 'axis' is a large negative value (e.g., '-100000'), then after the first 'if' it would still be negative. The check following the 'if' statement will pass and the 'for' loop would read one element before the start of 'input_dims.data' (when 'i = 0'). The Tensorflow team has patched the issue in GitHub commit d94ffe08a65400f898241c0374e9edc6fa8ed257.", "cve": "CVE-2021-37685", "id": "pyup.io-41160", "more_info_path": "/vulnerabilities/CVE-2021-37685/41160", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37687: In affected versions TFLite's 'GatherNd' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation. Hence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in 'indices'. Similar issue exists in 'Gather' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc). The Tensorflow team has patched the issue in GitHub commits bb6a0383ed553c286f87ca88c207f6774d5c4a8f and eb921122119a6b6e470ee98b89e65d721663179d.", "cve": "CVE-2021-37687", "id": "pyup.io-41162", "more_info_path": "/vulnerabilities/CVE-2021-37687/41162", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37661: In affected versions an attacker can cause a denial of service in 'boosted_trees_create_quantile_stream_resource' by using negative arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that 'num_streams' only contains non-negative numbers. In turn, this results in using this value to allocate memory (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40). However, 'reserve' receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library. The Tensorflow team has patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992.", "cve": "CVE-2021-37661", "id": "pyup.io-41136", "more_info_path": "/vulnerabilities/CVE-2021-37661/41136", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37666: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToVariant'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty. The Tensorflow team has patched the issue in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612.", "cve": "CVE-2021-37666", "id": "pyup.io-41141", "more_info_path": "/vulnerabilities/CVE-2021-37666/41141", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37646: In affected versions the implementation of 'tf.raw_ops.StringNGrams' is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls 'reserve' on a 'tstring' with a value that sometimes can be negative if user supplies negative 'ngram_widths'. The 'reserve' method calls 'TF_TString_Reserve' which has an 'unsigned long' argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5.", "cve": "CVE-2021-37646", "id": "pyup.io-41121", "more_info_path": "/vulnerabilities/CVE-2021-37646/41121", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37684: In affected versions the implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695 (https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).", "cve": "CVE-2021-37684", "id": "pyup.io-41159", "more_info_path": "/vulnerabilities/CVE-2021-37684/41159", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37641: In affected versions if the arguments to 'tf.raw_ops.RaggedGather' don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by 'params_nested_splits' is not an empty list of tensors. The Tensorflow team has patched the issue in GitHub commit a2b743f6017d7b97af1fe49087ae15f0ac634373.", "cve": "CVE-2021-37641", "id": "pyup.io-41116", "more_info_path": "/vulnerabilities/CVE-2021-37641/41116", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37681: In affected versions the implementation of SVDF in TFLite is vulnerable to a null pointer error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313). The 'GetVariableInput' function (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but 'GetTensorData' assumes that the argument is always a valid tensor. Furthermore, because 'GetVariableInput' calls 'GetMutableInput' (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return 'nullptr', the 'tensor->is_variable' expression can also trigger a null pointer exception. The Tensorflow team has patched the issue in GitHub commit 5b048e87e4e55990dae6b547add4dae59f4e1c76.", "cve": "CVE-2021-37681", "id": "pyup.io-41156", "more_info_path": "/vulnerabilities/CVE-2021-37681/41156", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37644: In affected versions providing a negative element to 'num_elements' list argument of 'tf.raw_ops.TensorListReserve' causes the runtime to abort the process due to reallocating a 'std::vector' to have a negative number of elements. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls 'std::vector.resize()' with the new size controlled by input given by the user, without checking that this input is valid. The Tensorflow team has patched the issue in GitHub commit 8a6e874437670045e6c7dc6154c7412b4a2135e2.", "cve": "CVE-2021-37644", "id": "pyup.io-41119", "more_info_path": "/vulnerabilities/CVE-2021-37644/41119", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37643: If a user does not provide a valid padding value to 'tf.raw_ops.MatrixDiagPartOp', then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from. The Tensorflow team has patched the issue in GitHub commit 482da92095c4d48f8784b1f00dda4f81c28d2988.", "cve": "CVE-2021-37643", "id": "pyup.io-41118", "more_info_path": "/vulnerabilities/CVE-2021-37643/41118", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37662: In affected versions an attacker can generate undefined behavior via a reference binding to nullptr in 'BoostedTreesCalculateBestGainsPerFeature' and similar attack can occur in 'BoostedTreesCalculateBestFeatureSplitV2'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values. The Tensorflow team has patched the issue in GitHub commit 9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad and in commit 429f009d2b2c09028647dd4bb7b3f6f414bbaad7.", "cve": "CVE-2021-37662", "id": "pyup.io-41137", "more_info_path": "/vulnerabilities/CVE-2021-37662/41137", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37690:\r\nIn affected versions when running shape functions, some functions (such as 'MutableHashTableShape') produce extra output information in the form of a 'ShapeAndType' struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault. 'ShapeRefiner' is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but the Tensorflow team was not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types. The Tensorflow team has patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3hxh-8cp2-g4hg\r\nhttps://github.com/tensorflow/tensorflow/commit/ee119d4a498979525046fba1c3dd3f13a039fbb1", "cve": "CVE-2021-37690", "id": "pyup.io-41166", "more_info_path": "/vulnerabilities/CVE-2021-37690/41166", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37682:\r\nIn affected versions all TFLite operations that use quantization can be made to use unitialized values. (For example, https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200). The issue stems from the fact that \"quantization.params\" is only valid if \"quantization.type\" is different that \"kTfLiteNoQuantization\". However, these checks are missing in large parts of the code. The Tensorflow team has patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4c4g-crqm-xrxw\r\nhttps://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5\r\nhttps://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887\r\nhttps://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538", "cve": "CVE-2021-37682", "id": "pyup.io-41157", "more_info_path": "/vulnerabilities/CVE-2021-37682/41157", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22876", "id": "pyup.io-41107", "more_info_path": "/vulnerabilities/CVE-2021-22876/41107", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37655: TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to 'tf.raw_ops.ResourceScatterUpdate'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of 'indices' and 'updates': instead of checking that the shape of 'indices' is a prefix of the shape of 'updates' (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. The Tensorflow team has patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f.", "cve": "CVE-2021-37655", "id": "pyup.io-41130", "more_info_path": "/vulnerabilities/CVE-2021-37655/41130", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37672:\r\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.SdcaOptimizerV2\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of \"example_labels\" is the same as the number of examples. The Tensorflow team has patched the issue in GitHub commit a4e138660270e7599793fa438cd7b2fc2ce215a6.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hj3-vjjf-f5m7\r\nhttps://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6", "cve": "CVE-2021-37672", "id": "pyup.io-41147", "more_info_path": "/vulnerabilities/CVE-2021-37672/41147", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37677: In affected versions the shape inference code for \"tf.raw_ops.Dequantize\" has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses \"axis\" to select between two different values for \"minmax_rank\" which is then used to retrieve tensor dimensions. However, code assumes that \"axis\" can be either \"-1\" or a value greater than \"-1\", with no validation for the other values. The Tensorflow team has patched the issue in GitHub commit da857cfa0fde8f79ad0afdbc94e88b5d4bbec764.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qfpc-5pjr-mh26\r\nhttps://github.com/tensorflow/tensorflow/commit/da857cfa0fde8f79ad0afdbc94e88b5d4bbec764", "cve": "CVE-2021-37677", "id": "pyup.io-41152", "more_info_path": "/vulnerabilities/CVE-2021-37677/41152", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37674:\r\nIn affected versions, an attacker can trigger a denial of service via a segmentation fault in \"tf.raw_ops.MaxPoolGrad\" caused by missing validation. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the \"orig_input\" and \"orig_output\" tensors. The fixes for CVE-2021-29579 were incomplete. The Tensorflow team has patched the issue in GitHub commit 136b51f10903e044308cf77117c0ed9871350475.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7ghq-fvr3-pj2x\r\nhttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-068.md\r\nhttps://github.com/tensorflow/tensorflow/commit/136b51f10903e044308cf77117c0ed9871350475", "cve": "CVE-2021-37674", "id": "pyup.io-41149", "more_info_path": "/vulnerabilities/CVE-2021-37674/41149", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37673:\r\nIn affected versions, an attacker can trigger a denial of service via a \"CHECK\"-fail in \"tf.raw_ops.MapStage\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the \"key\" input is a valid non-empty tensor. The Tensorflow team has patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-278g-rq84-9hmg\r\nhttps://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d", "cve": "CVE-2021-37673", "id": "pyup.io-41148", "more_info_path": "/vulnerabilities/CVE-2021-37673/41148", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22897", "id": "pyup.io-41106", "more_info_path": "/vulnerabilities/CVE-2021-22897/41106", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37670:\r\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.UpperBound\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of \"sorted_input\" argument. A similar issue occurs in \"tf.raw_ops.LowerBound\". The Tensorflow team has patched the issue in GitHub commit 42459e4273c2e47a3232cc16c4f4fff3b3a35c38.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9697-98pf-4rw7\r\nhttps://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38", "cve": "CVE-2021-37670", "id": "pyup.io-41145", "more_info_path": "/vulnerabilities/CVE-2021-37670/41145", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "TensorFlow 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37650: In affected versions the implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types. The Tensorflow team has patched the issue in GitHub commit e0b6e58c328059829c3eb968136f17aa72b6c876.", "cve": "CVE-2021-37650", "id": "pyup.io-41125", "more_info_path": "/vulnerabilities/CVE-2021-37650/41125", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37669:\r\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.NonMaxSuppressionV5\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a \"std::vector\". However, as \"std::vector::resize\" takes the size argument as a \"size_t\" and \"output_size\" is an \"int\", there is an implicit conversion to unsigned. If the attacker supplies a negative value, this conversion results in a crash. A similar issue occurs in \"CombinedNonMaxSuppression\". The Tensorflow team has patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c\r\nhttps://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d\r\nhttps://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58", "cve": "CVE-2021-37669", "id": "pyup.io-41144", "more_info_path": "/vulnerabilities/CVE-2021-37669/41144", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22901", "id": "pyup.io-41104", "more_info_path": "/vulnerabilities/CVE-2021-22901/41104", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37679:\r\nIn affected versions it is possible to nest a \"tf.map_fn\" within another \"tf.map_fn\" call. However, if the input tensor is a \"RaggedTensor\" and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap. The \"t\" and \"z\" outputs should be identical, however this is not the case. The last row of \"t\" contains data from the heap which can be used to leak other memory information. The bug lies in the conversion from a \"Variant\" tensor to a \"RaggedTensor\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions. The same implementation can result in data loss, if input tensor is tweaked. The Tensorflow team has patched the issue in GitHub commit 4e2565483d0ffcadc719bd44893fb7f609bb5f12.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g8wg-cjwc-xhhp\r\nhttps://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12", "cve": "CVE-2021-37679", "id": "pyup.io-41154", "more_info_path": "/vulnerabilities/CVE-2021-37679/41154", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow version 2.3.4, 2.4.3, 2.5.1, 2.6.0 and 2.7.0 include a fix for CVE-2021-37678:\r\nIn affected versions, TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The implementation(https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses \"yaml.unsafe_load\" which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, the Tensorflow team has removed it for now. The Tensorflow team has patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r\r\nhttps://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012", "cve": "CVE-2021-37678", "id": "pyup.io-41153", "more_info_path": "/vulnerabilities/CVE-2021-37678/41153", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.7.0rc0,<2.7.0" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.7.0rc0,<2.7.0" }, { "advisory": "Tensorflow version 2.6.1 includes a fix for CVE-2021-41211: In affected versions, the shape inference code for 'QuantizeV2' can trigger a read outside of bounds of heap allocated array. This occurs whenever 'axis' is a negative value less than '-1'. In this case, we are accessing data before the start of a heap buffer. The code allows 'axis' to be an optional argument ('s' would contain an 'error::NOT_FOUND' error code). Otherwise, it assumes that 'axis' is a valid index into the dimensions of the 'input' tensor. If 'axis' is less than '-1' then this results in a heap OOB read. The fix is included in TensorFlow 2.7.0. \r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvgx-3v3q-m36c\r\nhttps://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244", "cve": "CVE-2021-41211", "id": "pyup.io-42458", "more_info_path": "/vulnerabilities/CVE-2021-41211/42458", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow version 2.6.1 includes a fix for CVE-2021-41220: In affected versions, the async implementation of 'CollectiveReduceV2' suffers from a memory leak and a use after free. This occurs due to the asynchronous computation and the fact that objects that have been 'std::move()'d are still accessed. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gpfh-jvf9-7wg5\r\nhttps://github.com/tensorflow/tensorflow/commit/ca38dab9d3ee66c5de06f11af9a4b1200da5ef75", "cve": "CVE-2021-41220", "id": "pyup.io-42467", "more_info_path": "/vulnerabilities/CVE-2021-41220/42467", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. The TFG dialect of TensorFlow (MLIR) makes several assumptions about the incoming `GraphDef` before converting it to the MLIR-based dialect. If an attacker changes the `SavedModel` format on disk to invalidate these assumptions and the `GraphDef` is then converted to MLIR-based IR then they can cause a crash in the Python interpreter. Under certain scenarios, heap OOB read/writes are possible. These issues have been discovered via fuzzing and it is possible that more weaknesses exist. We will patch them as they are discovered.", "cve": "CVE-2022-23594", "id": "pyup.io-44879", "more_info_path": "/vulnerabilities/CVE-2022-23594/44879", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.7.1 and 2.8.0 include a fix for CVE-2022-23590: A 'GraphDef' from a TensorFlow 'SavedModel' can be maliciously altered to cause a TensorFlow process to crash due to encountering a 'StatusOr' value that is an error and forcibly extracting the value from it.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pqrv-8r2f-7278", "cve": "CVE-2022-23590", "id": "pyup.io-44875", "more_info_path": "/vulnerabilities/CVE-2022-23590/44875", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow version 2.8.0 includes a fix for CVE-2022-23592: TensorFlow's type inference can cause a heap out of bounds read as the bounds checking is done in a 'DCHECK' (which is a no-op during production). An attacker can control the 'input_idx' variable such that 'ix' would be larger than the number of values in 'node_t.args'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vq36-27g6-p492", "cve": "CVE-2022-23592", "id": "pyup.io-44877", "more_info_path": "/vulnerabilities/CVE-2022-23592/44877", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow 2.8.0 includes a fix for CVE-2022-23593: The 'simplifyBroadcast' function in the MLIR-TFRT infrastructure in TensorFlow is vulnerable to a segfault (hence, denial of service), if called with scalar shapes. If all shapes are scalar, then 'maxRank' is 0, so we build an empty 'SmallVector'. \r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gwcx-jrx4-92w2", "cve": "CVE-2022-23593", "id": "pyup.io-44878", "more_info_path": "/vulnerabilities/CVE-2022-23593/44878", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow version 2.8.1 and 2.9.0 include a fix for CVE-2022-29210: Heap buffer overflow due to incorrect hash function.", "cve": "CVE-2022-29210", "id": "pyup.io-48627", "more_info_path": "/vulnerabilities/CVE-2022-29210/48627", "specs": [ ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": ">=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" } ], "tensorflow-aarch64": [ { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25661: In versions prior to 2.11.1 a malicious invalid input crashes a tensorflow model (Check Failed) and can be used to trigger a denial of service attack. A proof of concept can be constructed with the 'Convolution3DTranspose' function. This Convolution3DTranspose layer is a very common API in modern neural networks. The ML models containing such vulnerable components could be deployed in ML applications or as cloud services. This failure could be potentially used to trigger a denial of service attack on ML cloud services. An attacker must have privilege to provide input to a 'Convolution3DTranspose' call.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fxgc-95xx-grvq", "cve": "CVE-2023-25661", "id": "pyup.io-56379", "more_info_path": "/vulnerabilities/CVE-2023-25661/56379", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25676: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.ParallelConcat' segfaults with a nullptr dereference when given a parameter 'shape' with rank that is not greater than zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6wfh-89q8-44jq", "cve": "CVE-2023-25676", "id": "pyup.io-56375", "more_info_path": "/vulnerabilities/CVE-2023-25676/56375", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25673: Versions prior to 2.12.0 and 2.11.1 have a Floating Point Exception in TensorListSplit with XLA. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25673", "id": "pyup.io-56373", "more_info_path": "/vulnerabilities/CVE-2023-25673/56373", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25660: Prior to versions 2.12.0 and 2.11.1, when the parameter 'summarize' of 'tf.raw_ops.Print' is zero, the new method 'SummarizeArray' will reference to a nullptr, leading to a seg fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qjqc-vqcf-5qvj", "cve": "CVE-2023-25660", "id": "pyup.io-56391", "more_info_path": "/vulnerabilities/CVE-2023-25660/56391", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25670: Versions prior to 2.12.0 and 2.11.1 have a null point error in QuantizedMatMulWithBiasAndDequantize with MKL enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rq-hwc3-x77w", "cve": "CVE-2023-25670", "id": "pyup.io-56385", "more_info_path": "/vulnerabilities/CVE-2023-25670/56385", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25675: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.Bincount' segfaults when given a parameter 'weights' that is neither the same shape as parameter 'arr' nor a length-0 tensor.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7x4v-9gxg-9hwj", "cve": "CVE-2023-25675", "id": "pyup.io-56381", "more_info_path": "/vulnerabilities/CVE-2023-25675/56381", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25668: Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gw97-ff7c-9v96", "cve": "CVE-2023-25668", "id": "pyup.io-56387", "more_info_path": "/vulnerabilities/CVE-2023-25668/56387", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25665: Prior to versions 2.12.0 and 2.11.1, when 'SparseSparseMaximum' is given invalid sparse tensors as inputs, it can give a null pointer error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-558h-mq8x-7q9g", "cve": "CVE-2023-25665", "id": "pyup.io-56382", "more_info_path": "/vulnerabilities/CVE-2023-25665/56382", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25671: There is out-of-bounds access due to mismatched integer type sizes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j5w9-hmfh-4cr6", "cve": "CVE-2023-25671", "id": "pyup.io-56384", "more_info_path": "/vulnerabilities/CVE-2023-25671/56384", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-27579: Constructing a tflite model with a paramater 'filter_input_channel' of less than 1 gives a FPE.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5w96-866f-6rm8", "cve": "CVE-2023-27579", "id": "pyup.io-56383", "more_info_path": "/vulnerabilities/CVE-2023-27579/56383", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25666: Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2", "cve": "CVE-2023-25666", "id": "pyup.io-56376", "more_info_path": "/vulnerabilities/CVE-2023-25666/56376", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25664: Prior to versions 2.12.0 and 2.11.1, there is a heap buffer overflow in TAvgPoolGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hg6-5c2q-7rcr", "cve": "CVE-2023-25664", "id": "pyup.io-56388", "more_info_path": "/vulnerabilities/CVE-2023-25664/56388", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25667: Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when '2^31 <= num_frames * height * width * channels < 2^32', for example Full HD screencast of at least 346 frames.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqm2-gh8w-gr68", "cve": "CVE-2023-25667", "id": "pyup.io-56377", "more_info_path": "/vulnerabilities/CVE-2023-25667/56377", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25674: Versions prior to 2.12.0 and 2.11.1 have a null pointer error in RandomShuffle with XLA enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf97-q72m-7579", "cve": "CVE-2023-25674", "id": "pyup.io-56378", "more_info_path": "/vulnerabilities/CVE-2023-25674/56378", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25662: Versions prior to 2.12.0 and 2.11.1 are vulnerable to integer overflow in EditDistance.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7jvm-xxmr-v5cw", "cve": "CVE-2023-25662", "id": "pyup.io-56390", "more_info_path": "/vulnerabilities/CVE-2023-25662/56390", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25663: Prior to versions 2.12.0 and 2.11.1, when 'ctx->step_containter()' is a null ptr, the Lookup function will be executed with a null pointer.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-64jg-wjww-7c5w", "cve": "CVE-2023-25663", "id": "pyup.io-56389", "more_info_path": "/vulnerabilities/CVE-2023-25663/56389", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25672: The function 'tf.raw_ops.LookupTableImportV2' cannot handle scalars in the 'values' parameter and gives an NPE. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25672", "id": "pyup.io-56374", "more_info_path": "/vulnerabilities/CVE-2023-25672/56374", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25659: Prior to versions 2.12.0 and 2.11.1, if the parameter 'indices' for 'DynamicStitch' does not match the shape of the parameter 'data', it can trigger an stack OOB read.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-93vr-9q9m-pj8p", "cve": "CVE-2023-25659", "id": "pyup.io-56392", "more_info_path": "/vulnerabilities/CVE-2023-25659/56392", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25801: Prior to versions 2.12.0 and 2.11.1, 'nn_ops.fractional_avg_pool_v2' and 'nn_ops.fractional_max_pool_v2' require the first and fourth elements of their parameter 'pooling_ratio' to be equal to 1.0, as pooling on batch and channel dimensions is not supported.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f49c-87jh-g47q", "cve": "CVE-2023-25801", "id": "pyup.io-56380", "more_info_path": "/vulnerabilities/CVE-2023-25801/56380", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25669: Prior to versions 2.12.0 and 2.11.1, if the stride and window size are not positive for 'tf.raw_ops.AvgPoolGrad', it can give a floating point exception.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rcf8-g8jv-vg6p", "cve": "CVE-2023-25669", "id": "pyup.io-56386", "more_info_path": "/vulnerabilities/CVE-2023-25669/56386", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-aarch64 2.11.1 and 2.12.0 include a fix for CVE-2023-25658: Prior to versions 2.12.0 and 2.11.1, an out of bounds read is in GRUBlockCellGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-68v3-g9cm-rmm6", "cve": "CVE-2023-25658", "id": "pyup.io-56393", "more_info_path": "/vulnerabilities/CVE-2023-25658/56393", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Integer Overflow. array_ops.upper_bound' causes a segfault when not given a rank 2 tensor. The flaw was fixed in May 30, 2023, but the CVE was published in July 30, 2024. It was noticed unpublished by the Safety CLI Cyber Security team.", "cve": "CVE-2023-33976", "id": "pyup.io-72427", "more_info_path": "/vulnerabilities/CVE-2023-33976/72427", "specs": [ "<2.12.1", ">=2.13.0rc0,<2.13.0" ], "v": "<2.12.1,>=2.13.0rc0,<2.13.0" }, { "advisory": "Tensorflow-aarch64 2.14.1 updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38545.", "cve": "CVE-2023-38545", "id": "pyup.io-72936", "more_info_path": "/vulnerabilities/CVE-2023-38545/72936", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "TensorFlow-aarch64 updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38546.", "cve": "CVE-2023-38546", "id": "pyup.io-72935", "more_info_path": "/vulnerabilities/CVE-2023-38546/72935", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "Tensorflow-aarch64 before version 2.7.3 is vulnerable to several vulnerabilities, affecting confidentiality, integrity and availability.", "cve": "PVE-2023-56372", "id": "pyup.io-56372", "more_info_path": "/vulnerabilities/PVE-2023-56372/56372", "specs": [ "<2.7.3" ], "v": "<2.7.3" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35970: Segfault in 'QuantizedInstanceNorm'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g35r-369w-3fqp", "cve": "CVE-2022-35970", "id": "pyup.io-56465", "more_info_path": "/vulnerabilities/CVE-2022-35970/56465", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35934: 'CHECK' failure in tf.reshape via overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f4w6-h4f5-wx45", "cve": "CVE-2022-35934", "id": "pyup.io-56431", "more_info_path": "/vulnerabilities/CVE-2022-35934/56431", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36011: Null dereference on MLIR on empty function attributes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fv43-93gv-vm8f", "cve": "CVE-2022-36011", "id": "pyup.io-56452", "more_info_path": "/vulnerabilities/CVE-2022-36011/56452", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35937: OOB read in 'Gather_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pxrw-j2fv-hx3h", "cve": "CVE-2022-35937", "id": "pyup.io-56421", "more_info_path": "/vulnerabilities/CVE-2022-35937/56421", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35965: Segfault in 'LowerBound' and 'UpperBound'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qxpx-j395-pw36", "cve": "CVE-2022-35965", "id": "pyup.io-56461", "more_info_path": "/vulnerabilities/CVE-2022-35965/56461", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36027: Segfault TFLite converter on per-channel quantized transposed convolutions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-79h2-q768-fpxr", "cve": "CVE-2022-36027", "id": "pyup.io-56453", "more_info_path": "/vulnerabilities/CVE-2022-36027/56453", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36016: 'CHECK'-fail in 'tensorflow::full_type::SubstituteFromAttrs'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g468-qj8g-vcjc", "cve": "CVE-2022-36016", "id": "pyup.io-56459", "more_info_path": "/vulnerabilities/CVE-2022-36016/56459", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36014: Null-dereference in 'mlir::tfg::TFOp::nameAttr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7j3m-8g3c-9qqq", "cve": "CVE-2022-36014", "id": "pyup.io-56457", "more_info_path": "/vulnerabilities/CVE-2022-36014/56457", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36013: Null-dereference in 'mlir::tfg::GraphDefImporter::ConvertNodeDef'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-828c-5j5q-vrjq", "cve": "CVE-2022-36013", "id": "pyup.io-56442", "more_info_path": "/vulnerabilities/CVE-2022-36013/56442", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36005: 'CHECK' fail in 'FakeQuantWithMinMaxVarsGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r26c-679w-mrjm", "cve": "CVE-2022-36005", "id": "pyup.io-56476", "more_info_path": "/vulnerabilities/CVE-2022-36005/56476", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36004: 'CHECK' fail in 'tf.random.gamma'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv8m-8x97-937q", "cve": "CVE-2022-36004", "id": "pyup.io-56473", "more_info_path": "/vulnerabilities/CVE-2022-36004/56473", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36001: 'CHECK' fail in 'DrawBoundingBoxes'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jqm7-m5q7-3hm5", "cve": "CVE-2022-36001", "id": "pyup.io-56468", "more_info_path": "/vulnerabilities/CVE-2022-36001/56468", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35998: 'CHECK' fail in 'EmptyTensorList'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhw4-wwr7-gjc5", "cve": "CVE-2022-35998", "id": "pyup.io-56441", "more_info_path": "/vulnerabilities/CVE-2022-35998/56441", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35996: Floating point exception in 'Conv2D'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q5jv-m6qw-5g37", "cve": "CVE-2022-35996", "id": "pyup.io-56436", "more_info_path": "/vulnerabilities/CVE-2022-35996/56436", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35988: 'CHECK' fail in 'tf.linalg.matrix_rank'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vqj-64pv-w55c", "cve": "CVE-2022-35988", "id": "pyup.io-56460", "more_info_path": "/vulnerabilities/CVE-2022-35988/56460", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35992: 'CHECK' fail in 'TensorListFromTensor'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9v8w-xmr4-wgxp", "cve": "CVE-2022-35992", "id": "pyup.io-56445", "more_info_path": "/vulnerabilities/CVE-2022-35992/56445", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36019: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannel'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9j4v-pp28-mxv7", "cve": "CVE-2022-36019", "id": "pyup.io-56462", "more_info_path": "/vulnerabilities/CVE-2022-36019/56462", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36018: 'CHECK' fail in 'RaggedTensorToVariant'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6cv-4fmf-66xf", "cve": "CVE-2022-36018", "id": "pyup.io-56474", "more_info_path": "/vulnerabilities/CVE-2022-36018/56474", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35941: 'CHECK' failure in 'AvgPoolOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mgmh-g2v6-mqw5", "cve": "CVE-2022-35941", "id": "pyup.io-56458", "more_info_path": "/vulnerabilities/CVE-2022-35941/56458", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35995: 'CHECK' fail in 'AudioSummaryV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9h5-vr8m-x2h4", "cve": "CVE-2022-35995", "id": "pyup.io-56471", "more_info_path": "/vulnerabilities/CVE-2022-35995/56471", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35987: 'CHECK' fail in 'DenseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w62h-8xjm-fv49", "cve": "CVE-2022-35987", "id": "pyup.io-56449", "more_info_path": "/vulnerabilities/CVE-2022-35987/56449", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35986: Segfault in 'RaggedBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wr9v-g9vf-c74v", "cve": "CVE-2022-35986", "id": "pyup.io-56446", "more_info_path": "/vulnerabilities/CVE-2022-35986/56446", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36002: 'CHECK' fail in 'Unbatch'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mh3m-62v7-68xg", "cve": "CVE-2022-36002", "id": "pyup.io-56432", "more_info_path": "/vulnerabilities/CVE-2022-36002/56432", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35989: 'CHECK' fail in 'MaxPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j43h-pgmg-5hjq", "cve": "CVE-2022-35989", "id": "pyup.io-56475", "more_info_path": "/vulnerabilities/CVE-2022-35989/56475", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35985: 'CHECK' fail in 'LRNGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9942-r22v-78cp", "cve": "CVE-2022-35985", "id": "pyup.io-56429", "more_info_path": "/vulnerabilities/CVE-2022-35985/56429", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35982: Segfault in 'SparseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-397c-5g2j-qxpv", "cve": "CVE-2022-35982", "id": "pyup.io-56454", "more_info_path": "/vulnerabilities/CVE-2022-35982/56454", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35981: 'CHECK' fail in 'FractionalMaxPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vxv8-r8q2-63xw", "cve": "CVE-2022-35981", "id": "pyup.io-56443", "more_info_path": "/vulnerabilities/CVE-2022-35981/56443", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35974: Segfault in 'QuantizeDownAndShrinkRange'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vgvh-2pf4-jr2x", "cve": "CVE-2022-35974", "id": "pyup.io-56447", "more_info_path": "/vulnerabilities/CVE-2022-35974/56447", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35973: Segfault in 'QuantizedMatMul'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-689c-r7h2-fv9v", "cve": "CVE-2022-35973", "id": "pyup.io-56448", "more_info_path": "/vulnerabilities/CVE-2022-35973/56448", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35972: Segfault in 'QuantizedBiasAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4pc4-m9mj-v2r9", "cve": "CVE-2022-35972", "id": "pyup.io-56455", "more_info_path": "/vulnerabilities/CVE-2022-35972/56455", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35971: 'CHECK' fail in 'FakeQuantWithMinMaxVars'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9fpg-838v-wpv7", "cve": "CVE-2022-35971", "id": "pyup.io-56472", "more_info_path": "/vulnerabilities/CVE-2022-35971/56472", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35969: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q2c3-jpmc-gfjx", "cve": "CVE-2022-35969", "id": "pyup.io-56430", "more_info_path": "/vulnerabilities/CVE-2022-35969/56430", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35968: 'CHECK' fail in 'AvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2475-53vw-vp25", "cve": "CVE-2022-35968", "id": "pyup.io-56464", "more_info_path": "/vulnerabilities/CVE-2022-35968/56464", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35967: Segfault in 'QuantizedAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v6h3-348g-6h5x", "cve": "CVE-2022-35967", "id": "pyup.io-56463", "more_info_path": "/vulnerabilities/CVE-2022-35967/56463", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35966: Segfault in 'QuantizedAvgPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4w68-4x85-mjj9", "cve": "CVE-2022-35966", "id": "pyup.io-56451", "more_info_path": "/vulnerabilities/CVE-2022-35966/56451", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35960: 'CHECK' failure in 'TensorListReserve' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v5xg-3q2c-c2r4", "cve": "CVE-2022-35960", "id": "pyup.io-56424", "more_info_path": "/vulnerabilities/CVE-2022-35960/56424", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35959: 'CHECK' failures in 'AvgPool3DGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wxjj-cgcx-r3vq", "cve": "CVE-2022-35959", "id": "pyup.io-56438", "more_info_path": "/vulnerabilities/CVE-2022-35959/56438", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35952: 'CHECK' failures in 'UnbatchGradOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h5vq-gw2c-pq47", "cve": "CVE-2022-35952", "id": "pyup.io-56423", "more_info_path": "/vulnerabilities/CVE-2022-35952/56423", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35940: Int overflow in 'RaggedRangeOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x989-q2pq-4q5x", "cve": "CVE-2022-35940", "id": "pyup.io-56467", "more_info_path": "/vulnerabilities/CVE-2022-35940/56467", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35939: OOB write in 'scatter_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-ffjm-4qwc-7cmf", "cve": "CVE-2022-35939", "id": "pyup.io-56422", "more_info_path": "/vulnerabilities/CVE-2022-35939/56422", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35990: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannelGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h7ff-cfc9-wmmh", "cve": "CVE-2022-35990", "id": "pyup.io-56437", "more_info_path": "/vulnerabilities/CVE-2022-35990/56437", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35997: 'CHECK' fail in 'tf.sparse.cross'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p7hr-f446-x6qf", "cve": "CVE-2022-35997", "id": "pyup.io-56440", "more_info_path": "/vulnerabilities/CVE-2022-35997/56440", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35994: 'CHECK' fail in 'CollectiveGather'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fhfc-2q7x-929f", "cve": "CVE-2022-35994", "id": "pyup.io-56466", "more_info_path": "/vulnerabilities/CVE-2022-35994/56466", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36003: 'CHECK' fail in 'RandomPoissonV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cv2p-32v3-vhwq", "cve": "CVE-2022-36003", "id": "pyup.io-56428", "more_info_path": "/vulnerabilities/CVE-2022-36003/56428", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35999: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-37jf-mjv6-xfqw", "cve": "CVE-2022-35999", "id": "pyup.io-56470", "more_info_path": "/vulnerabilities/CVE-2022-35999/56470", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36026: 'CHECK' fail in 'QuantizeAndDequantizeV3'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9cr2-8pwr-fhfq", "cve": "CVE-2022-36026", "id": "pyup.io-56450", "more_info_path": "/vulnerabilities/CVE-2022-36026/56450", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35964: Segfault in 'BlockLSTMGradV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f7r5-q7cx-h668", "cve": "CVE-2022-35964", "id": "pyup.io-56439", "more_info_path": "/vulnerabilities/CVE-2022-35964/56439", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35983: 'CHECK' fail in 'Save' and 'SaveSlices'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6vp-8q9j-whx4", "cve": "CVE-2022-35983", "id": "pyup.io-56434", "more_info_path": "/vulnerabilities/CVE-2022-35983/56434", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35963: 'CHECK' failures in 'FractionalAvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-84jm-4cf3-9jfm", "cve": "CVE-2022-35963", "id": "pyup.io-56469", "more_info_path": "/vulnerabilities/CVE-2022-35963/56469", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36000: 'CHECK' fail in 'Eig'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqxc-pvf8-2w9v", "cve": "CVE-2022-36000", "id": "pyup.io-56444", "more_info_path": "/vulnerabilities/CVE-2022-36000/56444", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36015: Integer overflow in math ops. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rh87-q4vg-m45j", "cve": "CVE-2022-36015", "id": "pyup.io-56427", "more_info_path": "/vulnerabilities/CVE-2022-36015/56427", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35979: Segfault in 'QuantizedRelu' and 'QuantizedRelu6'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v7vw-577f-vp8x", "cve": "CVE-2022-35979", "id": "pyup.io-56425", "more_info_path": "/vulnerabilities/CVE-2022-35979/56425", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36017: Segfault in 'Requantize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wqmc-pm8c-2jhc", "cve": "CVE-2022-36017", "id": "pyup.io-56426", "more_info_path": "/vulnerabilities/CVE-2022-36017/56426", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35984: 'CHECK' fail in 'ParameterizedTruncatedNormal'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2xf-8hgm-hpw5", "cve": "CVE-2022-35984", "id": "pyup.io-56435", "more_info_path": "/vulnerabilities/CVE-2022-35984/56435", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35993: 'CHECK' fail in 'SetSize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wq6q-6m32-9rv9", "cve": "CVE-2022-35993", "id": "pyup.io-56456", "more_info_path": "/vulnerabilities/CVE-2022-35993/56456", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36012: Assertion fail on MLIR empty edge names.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jvhc-5hhr-w3v5", "cve": "CVE-2022-36012", "id": "pyup.io-56433", "more_info_path": "/vulnerabilities/CVE-2022-36012/56433", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41880: When the 'BaseCandidateSamplerOp' function receives a value in 'true_classes' larger than 'range_max', a heap oob read occurs.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8w5g-3wcv-9g2j", "cve": "CVE-2022-41880", "id": "pyup.io-56408", "more_info_path": "/vulnerabilities/CVE-2022-41880/56408", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41889: If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a 'nullptr', which is not caught. An example can be seen in 'tf.compat.v1.extract_volume_patches' by passing in quantized tensors as input 'ksizes'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xxcj-rhqg-m46g", "cve": "CVE-2022-41889", "id": "pyup.io-56400", "more_info_path": "/vulnerabilities/CVE-2022-41889/56400", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41910: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-frqp-wp83-qggv", "cve": "CVE-2022-41910", "id": "pyup.io-56415", "more_info_path": "/vulnerabilities/CVE-2022-41910/56415", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1.", "cve": "CVE-2022-41902", "id": "pyup.io-56410", "more_info_path": "/vulnerabilities/CVE-2022-41902/56410", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41908: TensorFlow is an open source platform for machine learning. An input 'token' that is not a UTF-8 bytestring will trigger a 'CHECK' fail in 'tf.raw_ops.PyFunc'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv77-9g28-cwg3", "cve": "CVE-2022-41908", "id": "pyup.io-56405", "more_info_path": "/vulnerabilities/CVE-2022-41908/56405", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41907: When 'tf.raw_ops.ResizeNearestNeighborGrad' is given a large 'size' input, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-368v-7v32-52fx", "cve": "CVE-2022-41907", "id": "pyup.io-56409", "more_info_path": "/vulnerabilities/CVE-2022-41907/56409", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41900: The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xvwp-h6jv-7472", "cve": "CVE-2022-41900", "id": "pyup.io-56406", "more_info_path": "/vulnerabilities/CVE-2022-41900/56406", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41899: TensorFlow is an open source platform for machine learning. Inputs 'dense_features' or 'example_state_data' not of rank 2 will trigger a 'CHECK' fail in 'SdcaOptimizer'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-27rc-728f-x5w2", "cve": "CVE-2022-41899", "id": "pyup.io-56402", "more_info_path": "/vulnerabilities/CVE-2022-41899/56402", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41897: If 'FractionMaxPoolGrad' is given outsize inputs 'row_pooling_sequence' and 'col_pooling_sequence', TensorFlow will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2w8-jw48-fr7j", "cve": "CVE-2022-41897", "id": "pyup.io-56413", "more_info_path": "/vulnerabilities/CVE-2022-41897/56413", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41896: If 'ThreadUnsafeUnigramCandidateSampler' is given input 'filterbank_channel_count' greater than the allowed max size, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rmg2-f698-wq35", "cve": "CVE-2022-41896", "id": "pyup.io-56411", "more_info_path": "/vulnerabilities/CVE-2022-41896/56411", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41894: The reference kernel of the 'CONV_3D_TRANSPOSE' TensorFlow Lite operator wrongly increments the data_ptr when adding the bias to the result. Instead of 'data_ptr += num_channels;' it should be 'data_ptr += output_num_channels;' as if the number of input channels is different than the number of output channels, the wrong result will be returned and a buffer overflow will occur if num_channels > output_num_channels. An attacker can craft a model with a specific number of input channels. It is then possible to write specific values through the bias of the layer outside the bounds of the buffer. This attack only works if the reference kernel resolver is used in the interpreter.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6q3-vv32-2cq5", "cve": "CVE-2022-41894", "id": "pyup.io-56418", "more_info_path": "/vulnerabilities/CVE-2022-41894/56418", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41893: If 'tf.raw_ops.TensorListResize' is given a nonscalar value for input 'size', it results 'CHECK' fail which can be used to trigger a denial of service attack.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-67pf-62xr-q35m", "cve": "CVE-2022-41893", "id": "pyup.io-56403", "more_info_path": "/vulnerabilities/CVE-2022-41893/56403", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41891: If 'tf.raw_ops.TensorListConcat' is given 'element_shape=[]', it results segmentation fault which can be used to trigger a denial of service attack.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-66vq-54fq-6jvv", "cve": "CVE-2022-41891", "id": "pyup.io-56398", "more_info_path": "/vulnerabilities/CVE-2022-41891/56398", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41888: When running on GPU, 'tf.image.generate_bounding_box_proposals' receives a 'scores' input that must be of rank 4 but is not checked.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6x99-gv2v-q76v", "cve": "CVE-2022-41888", "id": "pyup.io-56416", "more_info_path": "/vulnerabilities/CVE-2022-41888/56416", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41886: When 'tf.raw_ops.ImageProjectiveTransformV2' is given a large output shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-54pp-c6pp-7fpx", "cve": "CVE-2022-41886", "id": "pyup.io-56414", "more_info_path": "/vulnerabilities/CVE-2022-41886/56414", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41884: If a numpy array is created with a shape such that one element is zero and the others sum to a large number, an error will be raised. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jq6x-99hj-q636", "cve": "CVE-2022-41884", "id": "pyup.io-56412", "more_info_path": "/vulnerabilities/CVE-2022-41884/56412", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41909: An input 'encoded' that is not a valid 'CompositeTensorVariant' tensor will trigger a segfault in 'tf.raw_ops.CompositeTensorVariantToComponents'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjx6-v474-2ch9", "cve": "CVE-2022-41909", "id": "pyup.io-56404", "more_info_path": "/vulnerabilities/CVE-2022-41909/56404", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41898: If 'SparseFillEmptyRowsGrad' is given empty inputs, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hq7g-wwwp-q46h", "cve": "CVE-2022-41898", "id": "pyup.io-56417", "more_info_path": "/vulnerabilities/CVE-2022-41898/56417", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41911: When printing a tensor, we get it's data as a 'const char*' array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from 'char' to 'bool' are undefined if the 'char' is not '0' or '1', so sanitizers/fuzzers will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j", "cve": "CVE-2022-41911", "id": "pyup.io-56399", "more_info_path": "/vulnerabilities/CVE-2022-41911/56399", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41885: When 'tf.raw_ops.FusedResizeAndPadConv2D' is given a large tensor shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-762h-vpvw-3rcx", "cve": "CVE-2022-41885", "id": "pyup.io-56401", "more_info_path": "/vulnerabilities/CVE-2022-41885/56401", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41890: If 'BCast::ToShape' is given input larger than an 'int32', it will crash, despite being supposed to handle up to an 'int64'. An example can be seen in 'tf.experimental.numpy.outer' by passing in large input to the input 'b'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h246-cgh4-7475", "cve": "CVE-2022-41890", "id": "pyup.io-56407", "more_info_path": "/vulnerabilities/CVE-2022-41890/56407", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41895: If 'MirrorPadGrad' is given outsize input 'paddings', TensorFlow will give a heap OOB error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gq2j-cr96-gvqx", "cve": "CVE-2022-41895", "id": "pyup.io-56397", "more_info_path": "/vulnerabilities/CVE-2022-41895/56397", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41901: An input 'sparse_matrix' that is not a matrix with a shape with rank 0 will trigger a 'CHECK' fail in 'tf.raw_ops.SparseMatrixNNZ'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9fm-r5mm-rf9f", "cve": "CVE-2022-41901", "id": "pyup.io-56396", "more_info_path": "/vulnerabilities/CVE-2022-41901/56396", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35991: 'CHECK' fail in 'TensorListScatter' and 'TensorListScatterV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vm7x-4qhj-rrcq\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xf83-q765-xm6m", "cve": "CVE-2022-35991", "id": "pyup.io-56420", "more_info_path": "/vulnerabilities/CVE-2022-35991/56420", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-aarch64 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35935: 'CHECK' failure in 'SobolSample' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-97p7-w86h-vcf9\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqvq-fvhr-v6hc", "cve": "CVE-2022-35935", "id": "pyup.io-56419", "more_info_path": "/vulnerabilities/CVE-2022-35935/56419", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-aarch64 2.9.3 and 2.10.1 include a fix for CVE-2022-41887: 'tf.keras.losses.poisson' receives a 'y_pred' and 'y_true' that are passed through 'functor::mul' in 'BinaryOp'. If the resulting dimensions overflow an 'int32', TensorFlow will crash due to a size mismatch during broadcast assignment.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fvv-46hw-vpg3", "cve": "CVE-2022-41887", "id": "pyup.io-56395", "more_info_path": "/vulnerabilities/CVE-2022-41887/56395", "specs": [ "<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-aarch64 2.10.1 includes a fix for CVE-2022-41883: When ops that have specified input sizes receive a differing number of inputs, the executor will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj", "cve": "CVE-2022-41883", "id": "pyup.io-56394", "more_info_path": "/vulnerabilities/CVE-2022-41883/56394", "specs": [ ">=2.10.0rc0,<2.10.1" ], "v": ">=2.10.0rc0,<2.10.1" }, { "advisory": "TensorFlow is an open source platform for machine learning. In version 2.8.0, the 'TensorKey' hash function used total estimated 'AllocatedBytes()', which (a) is an estimate per tensor, and (b) is a very poor hash function for constants (e.g. 'int32_t'). It also tried to access individual tensor bytes through 'tensor.data()' of size 'AllocatedBytes()'. This led to ASAN failures because the 'AllocatedBytes()' is an estimate of total bytes allocated by a tensor, including any pointed-to constructs (e.g. strings), and does not refer to contiguous bytes in the '.data()' buffer. The discoverers could not use this byte vector anyway because types such as 'tstring' include pointers, whereas they needed to hash the string values themselves. This issue is patched in Tensorflow versions 2.9.0 and 2.8.1.", "cve": "CVE-2022-29210", "id": "pyup.io-56477", "more_info_path": "/vulnerabilities/CVE-2022-29210/56477", "specs": [ ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": ">=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" } ], "tensorflow-cpu": [ { "advisory": "Tensorflow-cpu 1.15 includes a fix for CVE-2019-16778: In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-844w-j86r-4x2j\nhttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2019-002.md\nhttps://github.com/tensorflow/tensorflow/commit/db4f9717c41bccc3ce10099ab61996b246099892", "cve": "CVE-2019-16778", "id": "pyup.io-55886", "more_info_path": "/vulnerabilities/CVE-2019-16778/55886", "specs": [ "<1.15" ], "v": "<1.15" }, { "advisory": "The original changelog reads: \"Tensorflow-cpu 2.0 fixes a potential security vulnerability where decoding variant tensors from proto could result in heap out of bounds memory access.\" However, it was later confirmed that the fix was already included in 1.15 and later. See: .", "cve": "PVE-2021-37524", "id": "pyup.io-55885", "more_info_path": "/vulnerabilities/PVE-2021-37524/55885", "specs": [ "<1.15.0" ], "v": "<1.15.0" }, { "advisory": "Tensorflow-cpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2018-20330.", "cve": "CVE-2018-20330", "id": "pyup.io-55874", "more_info_path": "/vulnerabilities/CVE-2018-20330/55874", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-cpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2018-19664.", "cve": "CVE-2018-19664", "id": "pyup.io-55873", "more_info_path": "/vulnerabilities/CVE-2018-19664/55873", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-cpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2019-13960.", "cve": "CVE-2019-13960", "id": "pyup.io-55875", "more_info_path": "/vulnerabilities/CVE-2019-13960/55875", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-cpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"SQLite3\" to handle CVE-2019-19244.", "cve": "CVE-2019-19244", "id": "pyup.io-55871", "more_info_path": "/vulnerabilities/CVE-2019-19244/55871", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-cpu versions 1.15.3, 2.0.2 and 2.1.1 update its dependency \"SQLite3\" to handle CVE-2019-19880.", "cve": "CVE-2019-19880", "id": "pyup.io-55870", "more_info_path": "/vulnerabilities/CVE-2019-19880/55870", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-cpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"SQLite\" to handle CVE-2019-19645.", "cve": "CVE-2019-19645", "id": "pyup.io-55872", "more_info_path": "/vulnerabilities/CVE-2019-19645/55872", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-cpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"Apache Spark\" to handle CVE-2019-10099.", "cve": "CVE-2019-10099", "id": "pyup.io-55878", "more_info_path": "/vulnerabilities/CVE-2019-10099/55878", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-cpu versions 1.15.3, 2.0.2 and 2.1.1 update its dependency \"Apache Spark\" to handle CVE-2018-11770.", "cve": "CVE-2018-11770", "id": "pyup.io-55877", "more_info_path": "/vulnerabilities/CVE-2018-11770/55877", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-cpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"Apache Spark\" to handle CVE-2018-17190.", "cve": "CVE-2018-17190", "id": "pyup.io-55876", "more_info_path": "/vulnerabilities/CVE-2018-17190/55876", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15209: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a \"nullptr\" buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with \"nullptr\". However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue was patched in commit 0b5662bc.", "cve": "CVE-2020-15209", "id": "pyup.io-55852", "more_info_path": "/vulnerabilities/CVE-2020-15209/55852", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15208: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a \"DCHECK\" which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue was patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d", "cve": "CVE-2020-15208", "id": "pyup.io-55849", "more_info_path": "/vulnerabilities/CVE-2020-15208/55849", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15206: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's \"SavedModel\" protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using \"Tensorflow-cpu-serving\" or other inference-as-a-service installments. Fixed were added in commits f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d. However, this was not enough, as #41097 reported a different failure mode. The issue was finally patched in commit df095206f25471e864a8e63a0f1caef53a0e3a6", "cve": "CVE-2020-15206", "id": "pyup.io-55847", "more_info_path": "/vulnerabilities/CVE-2020-15206/55847", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15202: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'Shard' API in TensorFlow expects the last argument to be a function taking two 'int64' (i.e., 'long long') arguments. However, there are several places in TensorFlow where a lambda taking 'int' or 'int32' arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4", "cve": "CVE-2020-15202", "id": "pyup.io-55851", "more_info_path": "/vulnerabilities/CVE-2020-15202/55851", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15195: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of 'SparseFillEmptyRowsGrad' uses a double indexing pattern. It is possible for 'reverse_index_map(i)' to be an index outside of bounds of 'grad_values', thus resulting in a heap buffer overflow.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-63xm-rx5p-xvqr", "cve": "CVE-2020-15195", "id": "pyup.io-55846", "more_info_path": "/vulnerabilities/CVE-2020-15195/55846", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15190: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the \"tf.raw_ops.Switch\" operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is \"nullptr\", hence we are binding a reference to \"nullptr\". This is undefined behavior and reported as an error if compiling with \"-fsanitize=null\". In this case, this results in a segmentation fault The issue was patched in commit da8558533d925694483d2c136a9220d6d49d843c\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4g9f-63rx-5cw4", "cve": "CVE-2020-15190", "id": "pyup.io-55850", "more_info_path": "/vulnerabilities/CVE-2020-15190/55850", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15211: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor. However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative \"-1\" value as index for these tensors. This results in special casing during validation at model loading time. Unfortunately, this means that the \"-1\" index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays. This results in both read and write gadgets, albeit very limited in scope. The issue was patched in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83). A potential workaround would be to add a custom \"Verifier\" to the model loading code to ensure that only operators which accept optional inputs use the \"-1\" special value and only for the tensors that they expect to be optional. Since this allow-list type approach is error-prone, it's advised upgrading to the patched code.", "cve": "CVE-2020-15211", "id": "pyup.io-55848", "more_info_path": "/vulnerabilities/CVE-2020-15211/55848", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15207: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses 'ResolveAxis' to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the 'DCHECK' does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34", "cve": "CVE-2020-15207", "id": "pyup.io-55855", "more_info_path": "/vulnerabilities/CVE-2020-15207/55855", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15205: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'data_splits' argument of 'tf.raw_ops.StringNGrams' lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after 'ee ff' are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46", "cve": "CVE-2020-15205", "id": "pyup.io-55853", "more_info_path": "/vulnerabilities/CVE-2020-15205/55853", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15204: In eager mode, TensorFlow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling \"tf.raw_ops.GetSessionHandle\" or \"tf.raw_ops.GetSessionHandleV2\" results in a null pointer dereference In linked snippet, in eager mode, \"ctx->session_state()\" returns \"nullptr\". Since code immediately dereferences this, we get a segmentation fault. The issue was patched in commit 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1", "cve": "CVE-2020-15204", "id": "pyup.io-55845", "more_info_path": "/vulnerabilities/CVE-2020-15204/55845", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15203: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the 'fill' argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a 'printf' call is constructed. This may result in segmentation fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79", "cve": "CVE-2020-15203", "id": "pyup.io-55854", "more_info_path": "/vulnerabilities/CVE-2020-15203/55854", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13434.", "cve": "CVE-2020-13434", "id": "pyup.io-55837", "more_info_path": "/vulnerabilities/CVE-2020-13434/55837", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-9327.", "cve": "CVE-2020-9327", "id": "pyup.io-55838", "more_info_path": "/vulnerabilities/CVE-2020-9327/55838", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13871.", "cve": "CVE-2020-13871", "id": "pyup.io-55835", "more_info_path": "/vulnerabilities/CVE-2020-13871/55835", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11656.", "cve": "CVE-2020-11656", "id": "pyup.io-55840", "more_info_path": "/vulnerabilities/CVE-2020-11656/55840", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13435.", "cve": "CVE-2020-13435", "id": "pyup.io-55842", "more_info_path": "/vulnerabilities/CVE-2020-13435/55842", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11655.", "cve": "CVE-2020-11655", "id": "pyup.io-55839", "more_info_path": "/vulnerabilities/CVE-2020-11655/55839", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13631.", "cve": "CVE-2020-13631", "id": "pyup.io-55841", "more_info_path": "/vulnerabilities/CVE-2020-13631/55841", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13630.", "cve": "CVE-2020-13630", "id": "pyup.io-55836", "more_info_path": "/vulnerabilities/CVE-2020-13630/55836", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15210: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x9j7-x98r-r4w2", "cve": "CVE-2020-15210", "id": "pyup.io-55843", "more_info_path": "/vulnerabilities/CVE-2020-15210/55843", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu 2.4.0 includes a fix for CVE-2020-15194: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments. Although `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\"", "cve": "CVE-2020-15194", "id": "pyup.io-55844", "more_info_path": "/vulnerabilities/CVE-2020-15194/55844", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency 'Junit4' to v4.13.1 to include a security fix.", "cve": "CVE-2020-15250", "id": "pyup.io-55822", "more_info_path": "/vulnerabilities/CVE-2020-15250/55822", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-cpu versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 updates its dependency \"Libjpeg-turbo\" to handle CVE-2020-13790.", "cve": "CVE-2020-13790", "id": "pyup.io-55824", "more_info_path": "/vulnerabilities/CVE-2020-13790/55824", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-cpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2 and 2.3.2 update its dependency \"PCRE\" to handle CVE-2020-14155.", "cve": "CVE-2020-14155", "id": "pyup.io-55823", "more_info_path": "/vulnerabilities/CVE-2020-14155/55823", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-cpu versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency \"PCRE\" to fix CVE-2019-20838.", "cve": "CVE-2019-20838", "id": "pyup.io-55821", "more_info_path": "/vulnerabilities/CVE-2019-20838/55821", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-cpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0 includes a fix for CVE-2020-26266: In affected versions and under certain cases a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers filled with the default value of the type but forgetting to default initialize the quantized floating point types in Eigen.", "cve": "CVE-2020-26266", "id": "pyup.io-55827", "more_info_path": "/vulnerabilities/CVE-2020-26266/55827", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-cpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26270: In affected versions, running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.", "cve": "CVE-2020-26270", "id": "pyup.io-55829", "more_info_path": "/vulnerabilities/CVE-2020-26270/55829", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-cpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26271: In affected versions, under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library.", "cve": "CVE-2020-26271", "id": "pyup.io-55825", "more_info_path": "/vulnerabilities/CVE-2020-26271/55825", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-cpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26268: In affected versions, the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden.", "cve": "CVE-2020-26268", "id": "pyup.io-55828", "more_info_path": "/vulnerabilities/CVE-2020-26268/55828", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-cpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26267: In affected versions, the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes.", "cve": "CVE-2020-26267", "id": "pyup.io-55826", "more_info_path": "/vulnerabilities/CVE-2020-26267/55826", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25666: Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2", "cve": "CVE-2023-25666", "id": "pyup.io-55415", "more_info_path": "/vulnerabilities/CVE-2023-25666/55415", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25669: Prior to versions 2.12.0 and 2.11.1, if the stride and window size are not positive for 'tf.raw_ops.AvgPoolGrad', it can give a floating point exception.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rcf8-g8jv-vg6p", "cve": "CVE-2023-25669", "id": "pyup.io-55425", "more_info_path": "/vulnerabilities/CVE-2023-25669/55425", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25661: In versions prior to 2.11.1 a malicious invalid input crashes a tensorflow model (Check Failed) and can be used to trigger a denial of service attack. A proof of concept can be constructed with the 'Convolution3DTranspose' function. This Convolution3DTranspose layer is a very common API in modern neural networks. The ML models containing such vulnerable components could be deployed in ML applications or as cloud services. This failure could be potentially used to trigger a denial of service attack on ML cloud services. An attacker must have privilege to provide input to a 'Convolution3DTranspose' call.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fxgc-95xx-grvq", "cve": "CVE-2023-25661", "id": "pyup.io-55418", "more_info_path": "/vulnerabilities/CVE-2023-25661/55418", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25673: Versions prior to 2.12.0 and 2.11.1 have a Floating Point Exception in TensorListSplit with XLA. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25673", "id": "pyup.io-55412", "more_info_path": "/vulnerabilities/CVE-2023-25673/55412", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25658: Prior to versions 2.12.0 and 2.11.1, an out of bounds read is in GRUBlockCellGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-68v3-g9cm-rmm6", "cve": "CVE-2023-25658", "id": "pyup.io-55432", "more_info_path": "/vulnerabilities/CVE-2023-25658/55432", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25663: Prior to versions 2.12.0 and 2.11.1, when 'ctx->step_containter()' is a null ptr, the Lookup function will be executed with a null pointer.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-64jg-wjww-7c5w", "cve": "CVE-2023-25663", "id": "pyup.io-55428", "more_info_path": "/vulnerabilities/CVE-2023-25663/55428", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25660: Prior to versions 2.12.0 and 2.11.1, when the parameter 'summarize' of 'tf.raw_ops.Print' is zero, the new method 'SummarizeArray' will reference to a nullptr, leading to a seg fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qjqc-vqcf-5qvj", "cve": "CVE-2023-25660", "id": "pyup.io-55430", "more_info_path": "/vulnerabilities/CVE-2023-25660/55430", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25676: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.ParallelConcat' segfaults with a nullptr dereference when given a parameter 'shape' with rank that is not greater than zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6wfh-89q8-44jq", "cve": "CVE-2023-25676", "id": "pyup.io-55414", "more_info_path": "/vulnerabilities/CVE-2023-25676/55414", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25667: Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when '2^31 <= num_frames * height * width * channels < 2^32', for example Full HD screencast of at least 346 frames.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqm2-gh8w-gr68", "cve": "CVE-2023-25667", "id": "pyup.io-55416", "more_info_path": "/vulnerabilities/CVE-2023-25667/55416", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25665: Prior to versions 2.12.0 and 2.11.1, when 'SparseSparseMaximum' is given invalid sparse tensors as inputs, it can give a null pointer error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-558h-mq8x-7q9g", "cve": "CVE-2023-25665", "id": "pyup.io-55421", "more_info_path": "/vulnerabilities/CVE-2023-25665/55421", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25801: Prior to versions 2.12.0 and 2.11.1, 'nn_ops.fractional_avg_pool_v2' and 'nn_ops.fractional_max_pool_v2' require the first and fourth elements of their parameter 'pooling_ratio' to be equal to 1.0, as pooling on batch and channel dimensions is not supported.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f49c-87jh-g47q", "cve": "CVE-2023-25801", "id": "pyup.io-55419", "more_info_path": "/vulnerabilities/CVE-2023-25801/55419", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25672: The function 'tf.raw_ops.LookupTableImportV2' cannot handle scalars in the 'values' parameter and gives an NPE. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25672", "id": "pyup.io-55413", "more_info_path": "/vulnerabilities/CVE-2023-25672/55413", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25664: Prior to versions 2.12.0 and 2.11.1, there is a heap buffer overflow in TAvgPoolGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hg6-5c2q-7rcr", "cve": "CVE-2023-25664", "id": "pyup.io-55427", "more_info_path": "/vulnerabilities/CVE-2023-25664/55427", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25675: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.Bincount' segfaults when given a parameter 'weights' that is neither the same shape as parameter 'arr' nor a length-0 tensor.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7x4v-9gxg-9hwj", "cve": "CVE-2023-25675", "id": "pyup.io-55420", "more_info_path": "/vulnerabilities/CVE-2023-25675/55420", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25659: Prior to versions 2.12.0 and 2.11.1, if the parameter 'indices' for 'DynamicStitch' does not match the shape of the parameter 'data', it can trigger an stack OOB read.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-93vr-9q9m-pj8p", "cve": "CVE-2023-25659", "id": "pyup.io-55431", "more_info_path": "/vulnerabilities/CVE-2023-25659/55431", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-27579: Constructing a tflite model with a paramater 'filter_input_channel' of less than 1 gives a FPE.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5w96-866f-6rm8", "cve": "CVE-2023-27579", "id": "pyup.io-55422", "more_info_path": "/vulnerabilities/CVE-2023-27579/55422", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25674: Versions prior to 2.12.0 and 2.11.1 have a null pointer error in RandomShuffle with XLA enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf97-q72m-7579", "cve": "CVE-2023-25674", "id": "pyup.io-55417", "more_info_path": "/vulnerabilities/CVE-2023-25674/55417", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25662: Versions prior to 2.12.0 and 2.11.1 are vulnerable to integer overflow in EditDistance.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7jvm-xxmr-v5cw", "cve": "CVE-2023-25662", "id": "pyup.io-55429", "more_info_path": "/vulnerabilities/CVE-2023-25662/55429", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25671: There is out-of-bounds access due to mismatched integer type sizes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j5w9-hmfh-4cr6", "cve": "CVE-2023-25671", "id": "pyup.io-55423", "more_info_path": "/vulnerabilities/CVE-2023-25671/55423", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25670: Versions prior to 2.12.0 and 2.11.1 have a null point error in QuantizedMatMulWithBiasAndDequantize with MKL enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rq-hwc3-x77w", "cve": "CVE-2023-25670", "id": "pyup.io-55424", "more_info_path": "/vulnerabilities/CVE-2023-25670/55424", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25668: Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gw97-ff7c-9v96", "cve": "CVE-2023-25668", "id": "pyup.io-55426", "more_info_path": "/vulnerabilities/CVE-2023-25668/55426", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Integer Overflow. array_ops.upper_bound' causes a segfault when not given a rank 2 tensor. The flaw was fixed in May 30, 2023, but the CVE was published in July 30, 2024. It was noticed unpublished by the Safety CLI Cyber Security team.", "cve": "CVE-2023-33976", "id": "pyup.io-72425", "more_info_path": "/vulnerabilities/CVE-2023-33976/72425", "specs": [ "<2.12.1", ">=2.13.0rc0,<2.13.0" ], "v": "<2.12.1,>=2.13.0rc0,<2.13.0" }, { "advisory": "TensorFlow-CPU 2.14.1 updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38545.", "cve": "CVE-2023-38545", "id": "pyup.io-72613", "more_info_path": "/vulnerabilities/CVE-2023-38545/72613", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "TensorFlow-GPU updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38546.", "cve": "CVE-2023-38546", "id": "pyup.io-72616", "more_info_path": "/vulnerabilities/CVE-2023-38546/72616", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "Tensorflow-cpu 2.4.0 includes a fix for CVE-2020-15265: In Tensorflow before version 2.4.0, an attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`. This results in accessing a dimension outside the rank of the input tensor in the C++ kernel implementation. However, dim_size only does a DCHECK to validate the argument and then uses it to access the corresponding element of an array. Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.", "cve": "CVE-2020-15265", "id": "pyup.io-55833", "more_info_path": "/vulnerabilities/CVE-2020-15265/55833", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Tensorflow-cpu 2.4.0 includes a fix for CVE-2020-15266: In Tensorflow before version 2.4.0, when the 'boxes' argument of 'tf.image.crop_and_resize' has a very large value, the CPU kernel implementation receives it as a C++ 'nan' floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault.\nhttps://github.com/tensorflow/tensorflow/issues/42129\nhttps://github.com/tensorflow/tensorflow/pull/42143/commits/3ade2efec2e90c6237de32a19680caaa3ebc2845\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xwhf-g6j5-j5gc", "cve": "CVE-2020-15266", "id": "pyup.io-55831", "more_info_path": "/vulnerabilities/CVE-2020-15266/55831", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41226: In affected versions, the implementation of 'SparseBinCount' is vulnerable to a heap OOB access. This is because of missing validation between the elements of the 'values' argument and the shape of the sparse output. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-374m-jm66-3vj8\nhttps://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba", "cve": "CVE-2021-41226", "id": "pyup.io-55633", "more_info_path": "/vulnerabilities/CVE-2021-41226/55633", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41223: In affected versions, the implementation of 'FusedBatchNorm' kernels is vulnerable to a heap OOB access. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f54p-f6jp-4rhr\nhttps://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda", "cve": "CVE-2021-41223", "id": "pyup.io-55621", "more_info_path": "/vulnerabilities/CVE-2021-41223/55621", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41202: In affected versions, while calculating the size of the output within the 'tf.range' kernel, there is a conditional statement of type 'int64 = condition ? int64 : double'. Due to C++ implicit conversion rules, both branches of the condition will be cast to 'double' and the result would be truncated before the assignment. This result in overflows. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xrqm-fpgr-6hhx", "cve": "CVE-2021-41202", "id": "pyup.io-55631", "more_info_path": "/vulnerabilities/CVE-2021-41202/55631", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22924.", "cve": "CVE-2021-22924", "id": "pyup.io-55627", "more_info_path": "/vulnerabilities/CVE-2021-22924/55627", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22925.", "cve": "CVE-2021-22925", "id": "pyup.io-55610", "more_info_path": "/vulnerabilities/CVE-2021-22925/55610", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41219: In affected versions, the code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to 'nullptr'. This occurs whenever the dimensions of 'a' or 'b' are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, it should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4f99-p9c2-3j8x\nhttps://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae", "cve": "CVE-2021-41219", "id": "pyup.io-55626", "more_info_path": "/vulnerabilities/CVE-2021-41219/55626", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41216: In affected versions, the shape inference function for 'Transpose' is vulnerable to a heap buffer overflow. This occurs whenever 'perm' contains negative elements. The shape inference function does not validate that the indices in 'perm' are all valid. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3ff2-r28g-w7h9\nhttps://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14", "cve": "CVE-2021-41216", "id": "pyup.io-55629", "more_info_path": "/vulnerabilities/CVE-2021-41216/55629", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22922.", "cve": "CVE-2021-22922", "id": "pyup.io-55611", "more_info_path": "/vulnerabilities/CVE-2021-22922/55611", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41213: In affected versions, the code behind 'tf.function' API can be made to deadlock when two 'tf.function' decorated Python functions are mutually recursive. This occurs due to using a non-reentrant 'Lock' Python object. Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive 'tf.function', although this is not a frequent scenario.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcf\nhttps://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7", "cve": "CVE-2021-41213", "id": "pyup.io-55636", "more_info_path": "/vulnerabilities/CVE-2021-41213/55636", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41218: In affected versions, the shape inference code for 'AllToAll' can be made to execute a division by 0. This occurs whenever the 'split_count' argument is 0. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9crf-c6qr-r273\nhttps://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc", "cve": "CVE-2021-41218", "id": "pyup.io-55613", "more_info_path": "/vulnerabilities/CVE-2021-41218/55613", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41200: In affected versions, if 'tf.summary.create_file_writer' is called with non-scalar arguments, code crashes due to a 'CHECK'-fail. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh8h-7j2j-qv4f", "cve": "CVE-2021-41200", "id": "pyup.io-55638", "more_info_path": "/vulnerabilities/CVE-2021-41200/55638", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41217: In affected versions, the process of building the control flow graph for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not. This occurs because the code assumes that the first node in the pairing (e.g., an 'Enter' node) always exists when encountering the second node (e.g., an 'Exit' node). When this is not the case, 'parent' is 'nullptr' so dereferencing it causes a crash. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5crj-c72x-m7gq\nhttps://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff", "cve": "CVE-2021-41217", "id": "pyup.io-55623", "more_info_path": "/vulnerabilities/CVE-2021-41217/55623", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41196: In affected versions, the Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative. This is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m539-j985-hcr8", "cve": "CVE-2021-41196", "id": "pyup.io-55614", "more_info_path": "/vulnerabilities/CVE-2021-41196/55614", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22923.", "cve": "CVE-2021-22923", "id": "pyup.io-55628", "more_info_path": "/vulnerabilities/CVE-2021-22923/55628", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41222: In affected versions, the implementation of 'SplitV' can trigger a segfault if an attacker supplies negative arguments. This occurs whenever 'size_splits' contains more than one value and at least one value is negative. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cpf4-wx82-gxp6\nhttps://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6", "cve": "CVE-2021-41222", "id": "pyup.io-55637", "more_info_path": "/vulnerabilities/CVE-2021-41222/55637", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41195: In affected versions, the implementation of 'tf.math.segment_*' operations results in a 'CHECK'-fail related abort (and denial of service) if a segment id in 'segment_ids' is large. This is similar to CVE-2021-29584 (and similar to other reported vulnerabilities in TensorFlow localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using 'AddDim'. However, if the number of elements in the tensor overflows an 'int64_t' value, 'AddDim' results in a 'CHECK' failure which provokes a 'std::abort'. Instead, code should use 'AddDimWithStatus'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cq76-mxrc-vchh", "cve": "CVE-2021-41195", "id": "pyup.io-55617", "more_info_path": "/vulnerabilities/CVE-2021-41195/55617", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41210: In affected versions, the shape inference functions for 'SparseCountSparseOutput' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m342-ff57-4jcc\r\nhttps://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2", "cve": "CVE-2021-41210", "id": "pyup.io-55643", "more_info_path": "/vulnerabilities/CVE-2021-41210/55643", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41228: In affected versions, TensorFlow's 'saved_model_cli' tool is vulnerable to a code injection as it calls 'eval' on user supplied strings. This can be used by attackers to run arbitrary code on the plaform where the CLI tool runs. However, given that the tool is always run manually, the impact of this is not severe. The issue has been patched by adding a 'safe' flag which defaults to 'True' and an explicit warning for users.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3rcw-9p9x-582v\nhttps://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7", "cve": "CVE-2021-41228", "id": "pyup.io-55618", "more_info_path": "/vulnerabilities/CVE-2021-41228/55618", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41201: In affected versions, during execution, 'EinsumHelper::ParseEquation()' is supposed to set the flags in 'input_has_ellipsis' vector and '*output_has_ellipsis' boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to 'true' and never assigns 'false'. This results in unitialized variable access if callers assume that 'EinsumHelper::ParseEquation()' always sets these flags. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j86v-p27c-73fm\nhttps://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6", "cve": "CVE-2021-41201", "id": "pyup.io-55615", "more_info_path": "/vulnerabilities/CVE-2021-41201/55615", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41205: In affected versions, the shape inference functions for the 'QuantizeAndDequantizeV*' operations can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rx-x2rw-pc6f\nhttps://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d", "cve": "CVE-2021-41205", "id": "pyup.io-55624", "more_info_path": "/vulnerabilities/CVE-2021-41205/55624", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22926.", "cve": "CVE-2021-22926", "id": "pyup.io-55619", "more_info_path": "/vulnerabilities/CVE-2021-22926/55619", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41209: In affected versions, the implementations for convolution operators trigger a division by 0 if passed empty filter tensor arguments. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hpv-v2rx-c5g6\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41209", "id": "pyup.io-55616", "more_info_path": "/vulnerabilities/CVE-2021-41209/55616", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41214: In affected versions, the shape inference code for 'tf.ragged.cross' has an undefined behavior due to binding a reference to 'nullptr'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vwhq-49r4-gj9v\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41214", "id": "pyup.io-55625", "more_info_path": "/vulnerabilities/CVE-2021-41214/55625", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41215: In affected versions, the shape inference code for 'DeserializeSparse' can trigger a null pointer dereference. This is because the shape inference function assumes that the 'serialize_sparse' tensor is a tensor with positive rank (and having '3' as the last dimension). The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x3v8-c8qx-3j3r\nhttps://github.com/tensorflow/tensorflow/commit/d3738dd70f1c9ceb547258cbb82d853da8771850", "cve": "CVE-2021-41215", "id": "pyup.io-55620", "more_info_path": "/vulnerabilities/CVE-2021-41215/55620", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41198: In affected versions, if 'tf.tile' is called with a large input argument, then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2p25-55c9-h58q", "cve": "CVE-2021-41198", "id": "pyup.io-55642", "more_info_path": "/vulnerabilities/CVE-2021-41198/55642", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41212: In affected versions, the shape inference code for 'tf.ragged.cross' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fr77-rrx3-cp7g\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41212", "id": "pyup.io-55640", "more_info_path": "/vulnerabilities/CVE-2021-41212/55640", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41225: In affected versions, TensorFlow's Grappler optimizer has a use of unitialized variable. If the 'train_nodes' vector (obtained from the saved model that gets optimized) does not contain a 'Dequeue' node, then 'dequeue_node' is left unitialized. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7r94-xv9v-63jw\nhttps://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3", "cve": "CVE-2021-41225", "id": "pyup.io-55641", "more_info_path": "/vulnerabilities/CVE-2021-41225/55641", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41199: In affected versions, if 'tf.image.resize' is called with a large input argument then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hx2-qx8j-qjqm", "cve": "CVE-2021-41199", "id": "pyup.io-55634", "more_info_path": "/vulnerabilities/CVE-2021-41199/55634", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41204: In affected versions, during TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-786j-5qwq-r36x\nhttps://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659", "cve": "CVE-2021-41204", "id": "pyup.io-55632", "more_info_path": "/vulnerabilities/CVE-2021-41204/55632", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41203: In affected versions, an attacker can trigger undefined behavior, integer overflows, segfaults and 'CHECK'-fail crashes if they can change saved checkpoints from outside of TensorFlow. This is because the checkpoints loading infrastructure is missing validation for invalid file formats.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7pxj-m4jf-r6h2", "cve": "CVE-2021-41203", "id": "pyup.io-55635", "more_info_path": "/vulnerabilities/CVE-2021-41203/55635", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41224: In affected versions, the implementation of 'SparseFillEmptyRows' can be made to trigger a heap OOB access. This occurs whenever the size of 'indices' does not match the size of 'values'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rg3m-hqc5-344v\nhttps://github.com/tensorflow/tensorflow/commit/67bfd9feeecfb3c61d80f0e46d89c170fbee682b", "cve": "CVE-2021-41224", "id": "pyup.io-55622", "more_info_path": "/vulnerabilities/CVE-2021-41224/55622", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41227: In affected versions, the 'ImmutableConst' operation in TensorFlow can be tricked into reading arbitrary memory contents. This is because the 'tstring' TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j8c8-67vp-6mx7\nhttps://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b\nhttps://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585", "cve": "CVE-2021-41227", "id": "pyup.io-55612", "more_info_path": "/vulnerabilities/CVE-2021-41227/55612", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41221: In affected versions, the shape inference code for the 'Cudnn*' operations can be tricked into accessing invalid memory via a heap buffer overflow. This occurs because the ranks of the 'input', 'input_h' and 'input_c' parameters are not validated, but code assumes they have certain values. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqv6-3phm-hcwx\nhttps://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6", "cve": "CVE-2021-41221", "id": "pyup.io-55639", "more_info_path": "/vulnerabilities/CVE-2021-41221/55639", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41207: In affected versions, the implementation of 'ParallelConcat' misses some input validation and can produce a division by 0. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7v94-64hj-m82h\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41207", "id": "pyup.io-55630", "more_info_path": "/vulnerabilities/CVE-2021-41207/55630", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Affected versions of Tensorflow-Cpu allow tensors to have a large number of dimensions and each dimension can be as large as desired. However, the total number of elements in a tensor must fit within an 'int64_t'. If an overflow occurs, 'MultiplyWithoutOverflow' would return a negative result. In the majority of TensorFlow codebase this then results in a 'CHECK'-failure. Newer constructs exist which return a 'Status' instead of crashing the binary. This is a similar issue to CVE-2021-29584.", "cve": "CVE-2021-41197", "id": "pyup.io-71512", "more_info_path": "/vulnerabilities/CVE-2021-41197/71512", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1", ">=2.7.0rc0,<2.7.0" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1,>=2.7.0rc0,<2.7.0" }, { "advisory": "The TensorFlow Grappler component is susceptible to a denial of service due to a `CHECK`-failure during constant folding. This issue arises when the user-controlled `output_prop` tensor's shape triggers one of the `CHECK`s in the `PartialTensorShape` constructor. This vulnerability has been identified as TFSA-2021-198.\r\n\r\nThe problem has been resolved in GitHub commit be7b286d40bc68cb0b56f702186cc4837d508058, and the fix will be implemented in TensorFlow 2.8.0. Additionally, this patched commit will be incorporated into TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these versions are also affected and within the currently supported range.\r\n\r\nFurther information on this issue, along with details about our security model and how to get in touch with us for queries or concerns, can be found in our security guide.", "cve": "PVE-2023-99918", "id": "pyup.io-61994", "more_info_path": "/vulnerabilities/PVE-2023-99918/61994", "specs": [ "<2.5.3", "==2.7.0", ">=2.6.0,<2.6.3" ], "v": "<2.5.3,==2.7.0,>=2.6.0,<2.6.3" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3 and 2.7.1 update its dependency 'icu' to v69.1 to include a security fix.", "cve": "CVE-2020-10531", "id": "pyup.io-55557", "more_info_path": "/vulnerabilities/CVE-2020-10531/55557", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that assertions in `function.cc` would be falsified and crash the Python interpreter. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23586", "id": "pyup.io-55583", "more_info_path": "/vulnerabilities/CVE-2022-23586/55583", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23582: A malicious user can cause a denial of service by altering a 'SavedModel' such that 'TensorByteSize' would trigger 'CHECK' failures. 'TensorShape' constructor throws a 'CHECK'-fail if shape is partial or has a number of elements that would overflow the size of an 'int'. The 'PartialTensorShape' constructor instead does not cause a 'CHECK'-abort if the shape is partial, which is exactly what this function needs to be able to return '-1'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4j82-5ccr-4r8v", "cve": "CVE-2022-23582", "id": "pyup.io-55606", "more_info_path": "/vulnerabilities/CVE-2022-23582/55606", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21728: The implementation of shape inference for 'ReverseSequence' does not fully validate the value of 'batch_dim' and can result in a heap OOB read. There is a check to make sure the value of 'batch_dim' does not go over the rank of the input, but there is no check for negative values. Negative dimensions are allowed in some cases to mimic Python's negative indexing (i.e., indexing from the end of the array), however if the value is too negative then the implementation of 'Dim' would access elements before the start of an array.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6gmv-pjp9-p8w8", "cve": "CVE-2022-21728", "id": "pyup.io-55559", "more_info_path": "/vulnerabilities/CVE-2022-21728/55559", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23560: An attacker can craft a TFLite model that would allow limited reads and writes outside of arrays in TFLite. This exploits missing validation in the conversion from sparse tensors to dense tensors.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4hvf-hxvg-f67v", "cve": "CVE-2022-23560", "id": "pyup.io-55588", "more_info_path": "/vulnerabilities/CVE-2022-23560/55588", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. TensorFlow is vulnerable to a heap OOB write in `Grappler`. The `set_output` function writes to an array at the specified index. Hence, this gives a malicious user a write primitive. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23566", "id": "pyup.io-55600", "more_info_path": "/vulnerabilities/CVE-2022-23566/55600", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. When decoding PNG images TensorFlow can produce a memory leak if the image is invalid. After calling `png::CommonInitDecode(..., &decode)`, the `decode` value contains allocated buffers which can only be freed by calling `png::CommonFreeDecode(&decode)`. However, several error case in the function implementation invoke the `OP_REQUIRES` macro which immediately terminates the execution of the function, without allowing for the memory free to occur. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23585", "id": "pyup.io-55567", "more_info_path": "/vulnerabilities/CVE-2022-23585/55567", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23581: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'IsSimplifiableReshape' would trigger 'CHECK' failures.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fq86-3f29-px2c", "cve": "CVE-2022-23581", "id": "pyup.io-55573", "more_info_path": "/vulnerabilities/CVE-2022-23581/55573", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. The implementation of `GetInitOp` is vulnerable to a crash caused by dereferencing a null pointer. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23577", "id": "pyup.io-55596", "more_info_path": "/vulnerabilities/CVE-2022-23577/55596", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, TensorFlow might do a null-dereference if attributes of some mutable arguments to some operations are missing from the proto. This is guarded by a `DCHECK`. However, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the dereferencing of the null pointer, whereas in the second case it results in a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23570", "id": "pyup.io-55565", "more_info_path": "/vulnerabilities/CVE-2022-23570/55565", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateTensorSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve a tensor with large enough number of elements. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23575", "id": "pyup.io-55577", "more_info_path": "/vulnerabilities/CVE-2022-23575/55577", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow is vulnerable to an integer overflow during cost estimation for crop and resize. Since the cropping parameters are user controlled, a malicious person can trigger undefined behavior. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23587", "id": "pyup.io-55589", "more_info_path": "/vulnerabilities/CVE-2022-23587/55589", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. A malicious user can cause a use after free behavior when decoding PNG images. After `png::CommonFreeDecode(&decode)` gets called, the values of `decode.width` and `decode.height` are in an unspecified state. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23584", "id": "pyup.io-55605", "more_info_path": "/vulnerabilities/CVE-2022-23584/55605", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a 'SavedModel' such that any binary op would trigger 'CHECK' failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the 'dtype' no longer matches the 'dtype' expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If 'Tin' and 'Tout' don't match the type of data in 'out' and 'input_*' tensors then 'flat<*>' would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a 'CHECK' crash, hence a denial of service. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23583", "id": "pyup.io-55569", "more_info_path": "/vulnerabilities/CVE-2022-23583/55569", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23580: During shape inference, TensorFlow can allocate a large vector based on a value from a tensor controlled by the user.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-627q-g293-49q7", "cve": "CVE-2022-23580", "id": "pyup.io-55595", "more_info_path": "/vulnerabilities/CVE-2022-23580/55595", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23579: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'SafeToRemoveIdentity' would trigger 'CHECK' failures.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5f2r-qp73-37mr", "cve": "CVE-2022-23579", "id": "pyup.io-55601", "more_info_path": "/vulnerabilities/CVE-2022-23579/55601", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateOutputSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve tensors with large enough number of elements. We can have a large enough number of dimensions in `output_shape.dim()` or just a small number of dimensions being large enough to cause an overflow in the multiplication. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23576", "id": "pyup.io-55568", "more_info_path": "/vulnerabilities/CVE-2022-23576/55568", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21726: The implementation of 'Dequantize' does not fully validate the value of 'axis' and can result in heap OOB accesses. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked and this results in reading past the end of the array containing the dimensions of the input tensor.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-23hm-7w47-xw72", "cve": "CVE-2022-21726", "id": "pyup.io-55607", "more_info_path": "/vulnerabilities/CVE-2022-21726/55607", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21738: The implementation of 'SparseCountSparseOutput' can be made to crash a TensorFlow process by an integer overflow whose result is then used in a memory allocation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x4qx-4fjv-hmw6", "cve": "CVE-2022-21738", "id": "pyup.io-55603", "more_info_path": "/vulnerabilities/CVE-2022-21738/55603", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21725: The estimator for the cost of some convolution operations can be made to execute a division by 0. The function fails to check that the stride argument is strictly positive. Hence, the fix is to add a check for the stride argument to ensure it is valid.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v3f7-j968-4h5f", "cve": "CVE-2022-21725", "id": "pyup.io-55590", "more_info_path": "/vulnerabilities/CVE-2022-21725/55590", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21727: The implementation of shape inference for 'Dequantize' is vulnerable to an integer overflow weakness. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked, and, since the code computes 'axis + 1', an attacker can trigger an integer overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c6fh-56w7-fvjw", "cve": "CVE-2022-21727", "id": "pyup.io-55584", "more_info_path": "/vulnerabilities/CVE-2022-21727/55584", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23569: Multiple operations in TensorFlow can be used to trigger a denial of service via 'CHECK'-fails (i.e., assertion failures). This is similar to CVE-2021-41197 and has a similar fix. It is possible that other similar instances exist.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qj5r-f9mv-rffh", "cve": "CVE-2022-23569", "id": "pyup.io-55576", "more_info_path": "/vulnerabilities/CVE-2022-23569/55576", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21741: An attacker can craft a TFLite model that would trigger a division by zero in the implementation of depthwise convolutions. The parameters of the convolution can be user controlled and are also used within a division operation to determine the size of the padding that needs to be added before applying the convolution. There is no check before this division that the divisor is strictly positive.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-428x-9xc2-m8mj", "cve": "CVE-2022-21741", "id": "pyup.io-55564", "more_info_path": "/vulnerabilities/CVE-2022-21741/55564", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. There is a typo in TensorFlow's `SpecializeType` which results in heap OOB read/write. Due to a typo, `arg` is initialized to the `i`th mutable argument in a loop where the loop index is `j`. Hence it is possible to assign to `arg` from outside the vector of arguments. Since this is a mutable proto value, it allows both read and write to outside of bounds data. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23574", "id": "pyup.io-55575", "more_info_path": "/vulnerabilities/CVE-2022-23574/55575", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23564: When decoding a resource handle tensor from protobuf, a TensorFlow process can encounter cases where a 'CHECK' assertion is invalidated based on user controlled arguments. This allows attackers to cause denial of services in TensorFlow processes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8rcj-c8pj-v3m3", "cve": "CVE-2022-23564", "id": "pyup.io-55586", "more_info_path": "/vulnerabilities/CVE-2022-23564/55586", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23563: In multiple places, TensorFlow uses 'tempfile.mktemp' to create temporary files. While this is acceptable in testing, in utilities and libraries it is dangerous as a different process can create the file between the check for the filename in 'mktemp' and the actual creation of the file by a subsequent operation (a TOC/TOU type of weakness). In several instances, TensorFlow was supposed to actually create a temporary directory instead of a file. This logic bug is hidden away by the 'mktemp' function usage. It was replaced 'mktemp' with the safer 'mkstemp'/'mkdtemp' functions, according to the usage pattern.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wc4g-r73w-x8mm", "cve": "CVE-2022-23563", "id": "pyup.io-55560", "more_info_path": "/vulnerabilities/CVE-2022-23563/55560", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21734: The implementation of 'MapStage' is vulnerable to a 'CHECK'-fail if the key tensor is not a scalar.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gcvh-66ff-4mwm", "cve": "CVE-2022-21734", "id": "pyup.io-55566", "more_info_path": "/vulnerabilities/CVE-2022-21734/55566", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23559: An attacker can craft a TFLite model that would cause an integer overflow in embedding lookup operations. Both 'embedding_size' and 'lookup_size' are products of values provided by the user. Hence, a malicious user could trigger overflows in the multiplication. In certain scenarios, this can then result in heap OOB read/write.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98p5-x8x4-c9m5", "cve": "CVE-2022-23559", "id": "pyup.io-55581", "more_info_path": "/vulnerabilities/CVE-2022-23559/55581", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23568: The implementation of 'AddManySparseToTensorsMap' is vulnerable to an integer overflow which results in a 'CHECK'-fail when building new 'TensorShape' objects (so, an assert failure based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6445-fm66-fvq2", "cve": "CVE-2022-23568", "id": "pyup.io-55558", "more_info_path": "/vulnerabilities/CVE-2022-23568/55558", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21731: The implementation of shape inference for 'ConcatV2' can be used to trigger a denial of service attack via a segfault caused by a type confusion. The 'axis' argument is translated into 'concat_dim' in the 'ConcatShapeHelper' helper function. Then, a value for 'min_rank' is computed based on 'concat_dim'. This is then used to validate that the 'values' tensor has at least the required rank. However, 'WithRankAtLeast' receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented. Due to the fact that 'min_rank' is a 32-bits value and the value of 'axis', the 'rank' argument is a negative value, so the error check is bypassed.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m4hf-j54p-p353", "cve": "CVE-2022-21731", "id": "pyup.io-55609", "more_info_path": "/vulnerabilities/CVE-2022-21731/55609", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21739: The implementation of 'QuantizedMaxPool' has an undefined behavior where user controlled inputs can trigger a reference binding to null pointer.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3mw4-6rj6-74g5", "cve": "CVE-2022-21739", "id": "pyup.io-55580", "more_info_path": "/vulnerabilities/CVE-2022-21739/55580", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23561: An attacker can craft a TFLite model that would cause a write outside of bounds of an array in TFLite. In fact, the attacker can override the linked list used by the memory allocator. This can be leveraged for an arbitrary write primitive under certain conditions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9c78-vcq7-7vxq", "cve": "CVE-2022-23561", "id": "pyup.io-55608", "more_info_path": "/vulnerabilities/CVE-2022-23561/55608", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23557: An attacker can craft a TFLite model that would trigger a division by zero in 'BiasAndClamp' implementation. There is no check that the 'bias_size' is non zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf2j-f278-xh4v", "cve": "CVE-2022-23557", "id": "pyup.io-55592", "more_info_path": "/vulnerabilities/CVE-2022-23557/55592", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23562: The implementation of 'Range' suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qx3f-p745-w4hr", "cve": "CVE-2022-23562", "id": "pyup.io-55602", "more_info_path": "/vulnerabilities/CVE-2022-23562/55602", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that Grappler optimizer would attempt to build a tensor using a reference `dtype`. This would result in a crash due to a `CHECK`-fail in the `Tensor` constructor as reference types are not allowed. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23588", "id": "pyup.io-55604", "more_info_path": "/vulnerabilities/CVE-2022-23588/55604", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21740: The implementation of 'SparseCountSparseOutput' is vulnerable to a heap overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-44qp-9wwf-734r", "cve": "CVE-2022-21740", "id": "pyup.io-55599", "more_info_path": "/vulnerabilities/CVE-2022-21740/55599", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21735: The implementation of 'FractionalMaxPool' can be made to crash a TensorFlow process via a division by 0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-87v6-crgm-2gfj", "cve": "CVE-2022-21735", "id": "pyup.io-55591", "more_info_path": "/vulnerabilities/CVE-2022-21735/55591", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21729: The implementation of 'UnravelIndex' is vulnerable to a division by zero caused by an integer overflow bug.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-34f9-hjfq-rr8j", "cve": "CVE-2022-21729", "id": "pyup.io-55582", "more_info_path": "/vulnerabilities/CVE-2022-21729/55582", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21730: The implementation of 'FractionalAvgPoolGrad' does not consider cases where the input tensors are invalid allowing an attacker to read from outside of bounds of heap.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vjg4-v33c-ggc4", "cve": "CVE-2022-21730", "id": "pyup.io-55561", "more_info_path": "/vulnerabilities/CVE-2022-21730/55561", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, TensorFlow can fail to specialize a type during shape inference. This case is covered by the 'DCHECK' function however, 'DCHECK' is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the 'ValueOrDie' line. This results in an assertion failure as 'ret' contains an error 'Status', not a value. In the second case we also get a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23572", "id": "pyup.io-55593", "more_info_path": "/vulnerabilities/CVE-2022-23572/55593", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow can trigger a null pointer dereference. There are 2 places where this can occur, for the same malicious alteration of a `SavedModel` file (fixing the first one would trigger the same dereference in the second place). First, during constant folding, the `GraphDef` might not have the required nodes for the binary operation. If a node is missing, the correposning `mul_*child` would be null, and the dereference in the subsequent line would be incorrect. We have a similar issue during `IsIdentityConsumingSwitch`. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23589", "id": "pyup.io-55572", "more_info_path": "/vulnerabilities/CVE-2022-23589/55572", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23565: An attacker can trigger denial of service via assertion failure by altering a 'SavedModel' on disk such that 'AttrDef's of some operation are duplicated.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4v5p-v5h9-6xjx", "cve": "CVE-2022-23565", "id": "pyup.io-55594", "more_info_path": "/vulnerabilities/CVE-2022-23565/55594", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23567: The implementations of 'Sparse*Cwise*' ops are vulnerable to integer overflows. These can be used to trigger large allocations (so, OOM based denial of service) or 'CHECK'-fails when building new 'TensorShape' objects (so, assert failures based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rrx2-r989-2c43", "cve": "CVE-2022-23567", "id": "pyup.io-55579", "more_info_path": "/vulnerabilities/CVE-2022-23567/55579", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21736: The implementation of 'SparseTensorSliceDataset' has an undefined behavior: under certain conditions, it can be made to dereference a 'nullptr' value. The 3 input arguments to 'SparseTensorSliceDataset' represent a sparse tensor. However, there are some preconditions that these arguments must satisfy, but these are not validated in the implementation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pfjj-m3jj-9jc9", "cve": "CVE-2022-21736", "id": "pyup.io-55562", "more_info_path": "/vulnerabilities/CVE-2022-21736/55562", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21737: The implementation of '*Bincount' operations allows malicious users to cause denial of service by passing in arguments which would trigger a 'CHECK'-fail. There are several conditions that the input arguments must satisfy. Some are not caught during shape inference and others are not caught during kernel implementation. This results in 'CHECK' failures later when the output tensors get allocated.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2vv-v9cg-qhh7", "cve": "CVE-2022-21737", "id": "pyup.io-55574", "more_info_path": "/vulnerabilities/CVE-2022-21737/55574", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21733: The implementation of 'StringNGrams' can be used to trigger a denial of service attack by causing an out of memory condition after an integer overflow. There is missing a validation on 'pad_witdh' and that result in computing a negative value for 'ngram_width' which is later used to allocate parts of the output.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98j8-c9q4-r38g", "cve": "CVE-2022-21733", "id": "pyup.io-55587", "more_info_path": "/vulnerabilities/CVE-2022-21733/55587", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23571", "id": "pyup.io-55585", "more_info_path": "/vulnerabilities/CVE-2022-23571/55585", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23595: When building an XLA compilation cache, if default settings are used, TensorFlow triggers a null pointer dereference. In the default scenario, all devices are allowed, so 'flr->config_proto' is 'nullptr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fpcp-9h7m-ffpx", "cve": "CVE-2022-23595", "id": "pyup.io-55563", "more_info_path": "/vulnerabilities/CVE-2022-23595/55563", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. The 'GraphDef' format in TensorFlow does not allow self recursive functions. The runtime assumes that this invariant is satisfied. However, a 'GraphDef' containing a fragment such as the following can be consumed when loading a 'SavedModel'. This would result in a stack overflow during execution as resolving each 'NodeDef' means resolving the function itself and its nodes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23591", "id": "pyup.io-55597", "more_info_path": "/vulnerabilities/CVE-2022-23591/55597", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. If a graph node is invalid, TensorFlow can leak memory in the implementation of `ImmutableExecutorState::Initialize`. Here, we set `item->kernel` to `nullptr` but it is a simple `OpKernel*` pointer so the memory that was previously allocated to it would leak. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23578", "id": "pyup.io-55571", "more_info_path": "/vulnerabilities/CVE-2022-23578/55571", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized data to a new tensor. This later results in undefined behavior. The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23573", "id": "pyup.io-55570", "more_info_path": "/vulnerabilities/CVE-2022-23573/55570", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23558: An attacker can craft a TFLite model that would cause an integer overflow in 'TfLiteIntArrayCreate'. The 'TfLiteIntArrayGetSizeInBytes' returns an 'int' instead of a 'size_t'. An attacker can control model inputs such that 'computed_size' overflows the size of 'int' datatype.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9gwq-6cwj-47h3", "cve": "CVE-2022-23558", "id": "pyup.io-55578", "more_info_path": "/vulnerabilities/CVE-2022-23558/55578", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21732: The implementation of 'ThreadPoolHandle' can be used to trigger a denial of service attack by allocating too much memory. This is because the 'num_threads' argument is only checked to not be negative, but there is no upper bound on its value.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c582-c96p-r5cq", "cve": "CVE-2022-21732", "id": "pyup.io-55598", "more_info_path": "/vulnerabilities/CVE-2022-21732/55598", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41208: In affected versions, the code for boosted trees in TensorFlow is still missing validation. As a result, attackers can trigger denial of service (via dereferencing 'nullptr's or via 'CHECK'-failures) as well as abuse undefined behavior (binding references to 'nullptr's). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call. Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. TensorFlow's boosted trees APIs will be deprecated in subsequent releases.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-57wx-m983-2f88\nhttps://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6gw-r52c-724r", "cve": "CVE-2021-41208", "id": "pyup.io-55556", "more_info_path": "/vulnerabilities/CVE-2021-41208/55556", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Tensorflow-cpu versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41206: In affected versions, several TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or 'CHECK'-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible. These issues were discovered internally via tooling while working on improving/testing GPU op determinism. As such, there aren't reproducers and there will be multiple fixes for these issues.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pgcq-h79j-2f69\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-43q8-3fv7-pr5x", "cve": "CVE-2021-41206", "id": "pyup.io-55555", "more_info_path": "/vulnerabilities/CVE-2021-41206/55555", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Affected versions of Tensorflow-Cpu are vulnerable to Denial of Service via CHECK-failure (assertion failure) in constant folding. The output_prop tensor has a shape that is controlled by user input and this can result in triggering one of the CHECKs in the PartialTensorShape constructor. This is an instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71510", "id": "pyup.io-71514", "more_info_path": "/vulnerabilities/PVE-2024-71510/71514", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1", ">=2.8.0rc0,<2.8.0" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1,>=2.8.0rc0,<2.8.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29202: Denial of service in 'tf.ragged.constant' due to lack of validation.", "cve": "CVE-2022-29202", "id": "pyup.io-55536", "more_info_path": "/vulnerabilities/CVE-2022-29202/55536", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29207: Issues arising from undefined behavior stemming from users supplying invalid resource handles.", "cve": "CVE-2022-29207", "id": "pyup.io-55523", "more_info_path": "/vulnerabilities/CVE-2022-29207/55523", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29199: Missing validation which causes denial of service via 'LoadAndRemapMatrix'.", "cve": "CVE-2022-29199", "id": "pyup.io-55544", "more_info_path": "/vulnerabilities/CVE-2022-29199/55544", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27774.", "cve": "CVE-2022-27774", "id": "pyup.io-55529", "more_info_path": "/vulnerabilities/CVE-2022-27774/55529", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29208: Segfault and OOB write due to incomplete validation in 'EditDistance'.", "cve": "CVE-2022-29208", "id": "pyup.io-55525", "more_info_path": "/vulnerabilities/CVE-2022-29208/55525", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27775.", "cve": "CVE-2022-27775", "id": "pyup.io-55516", "more_info_path": "/vulnerabilities/CVE-2022-27775/55516", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27779.", "cve": "CVE-2022-27779", "id": "pyup.io-55531", "more_info_path": "/vulnerabilities/CVE-2022-27779/55531", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29198: Missing validation which causes denial of service via 'SparseTensorToCSRSparseMatrix'.", "cve": "CVE-2022-29198", "id": "pyup.io-55521", "more_info_path": "/vulnerabilities/CVE-2022-29198/55521", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29191: Missing validation which causes denial of service via 'GetSessionTensor'.", "cve": "CVE-2022-29191", "id": "pyup.io-55549", "more_info_path": "/vulnerabilities/CVE-2022-29191/55549", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27778.", "cve": "CVE-2022-27778", "id": "pyup.io-55530", "more_info_path": "/vulnerabilities/CVE-2022-27778/55530", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'zlib' to v1.2.12 to handle CVE-2018-25032.", "cve": "CVE-2018-25032", "id": "pyup.io-55534", "more_info_path": "/vulnerabilities/CVE-2018-25032/55534", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-22576.", "cve": "CVE-2022-22576", "id": "pyup.io-55546", "more_info_path": "/vulnerabilities/CVE-2022-22576/55546", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29201: Missing validation which results in undefined behavior in 'QuantizedConv2D'.", "cve": "CVE-2022-29201", "id": "pyup.io-55537", "more_info_path": "/vulnerabilities/CVE-2022-29201/55537", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29206: Missing validation which results in undefined behavior in 'SparseTensorDenseAdd'.", "cve": "CVE-2022-29206", "id": "pyup.io-55538", "more_info_path": "/vulnerabilities/CVE-2022-29206/55538", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29203: Integer overflow in 'SpaceToBatchND'.", "cve": "CVE-2022-29203", "id": "pyup.io-55535", "more_info_path": "/vulnerabilities/CVE-2022-29203/55535", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29197: Missing validation which causes denial of service via 'UnsortedSegmentJoin'.", "cve": "CVE-2022-29197", "id": "pyup.io-55524", "more_info_path": "/vulnerabilities/CVE-2022-29197/55524", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27780.", "cve": "CVE-2022-27780", "id": "pyup.io-55542", "more_info_path": "/vulnerabilities/CVE-2022-27780/55542", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27782.", "cve": "CVE-2022-27782", "id": "pyup.io-55548", "more_info_path": "/vulnerabilities/CVE-2022-27782/55548", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29204: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29204", "id": "pyup.io-55539", "more_info_path": "/vulnerabilities/CVE-2022-29204/55539", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-30115.", "cve": "CVE-2022-30115", "id": "pyup.io-55533", "more_info_path": "/vulnerabilities/CVE-2022-30115/55533", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27781.", "cve": "CVE-2022-27781", "id": "pyup.io-55532", "more_info_path": "/vulnerabilities/CVE-2022-27781/55532", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29216: Code injection in 'saved_model_cli'.", "cve": "CVE-2022-29216", "id": "pyup.io-55517", "more_info_path": "/vulnerabilities/CVE-2022-29216/55517", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27776.", "cve": "CVE-2022-27776", "id": "pyup.io-55519", "more_info_path": "/vulnerabilities/CVE-2022-27776/55519", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29209: Type confusion leading to 'CHECK'-failure based denial of service.", "cve": "CVE-2022-29209", "id": "pyup.io-55547", "more_info_path": "/vulnerabilities/CVE-2022-29209/55547", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Affected versions of Tensorflow-Cpu are vulnerable to Denial of Service in the implementation of depthwise ops via CHECK-failure (assertion failure) caused by overflowing the number of elements in a tensor. This is another instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71511", "id": "pyup.io-71516", "more_info_path": "/vulnerabilities/PVE-2024-71511/71516", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29200: Missing validation which causes denial of service via 'LSTMBlockCell'.", "cve": "CVE-2022-29200", "id": "pyup.io-55520", "more_info_path": "/vulnerabilities/CVE-2022-29200/55520", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29212: Core dump when loading TFLite models with quantization.", "cve": "CVE-2022-29212", "id": "pyup.io-55550", "more_info_path": "/vulnerabilities/CVE-2022-29212/55550", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29213: Crashes stemming from incomplete validation in signal ops.", "cve": "CVE-2022-29213", "id": "pyup.io-55545", "more_info_path": "/vulnerabilities/CVE-2022-29213/55545", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29211: Segfault when 'tf.histogram_fixed_width' is called with NaN values.", "cve": "CVE-2022-29211", "id": "pyup.io-55540", "more_info_path": "/vulnerabilities/CVE-2022-29211/55540", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29205: Segfault due to missing support for quantized types.", "cve": "CVE-2022-29205", "id": "pyup.io-55543", "more_info_path": "/vulnerabilities/CVE-2022-29205/55543", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29196: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29196", "id": "pyup.io-55522", "more_info_path": "/vulnerabilities/CVE-2022-29196/55522", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29195: Missing validation which causes denial of service via 'StagePeek'.", "cve": "CVE-2022-29195", "id": "pyup.io-55526", "more_info_path": "/vulnerabilities/CVE-2022-29195/55526", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29193: missing validation which causes 'TensorSummaryV2' to crash.", "cve": "CVE-2022-29193", "id": "pyup.io-55518", "more_info_path": "/vulnerabilities/CVE-2022-29193/55518", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29194: Missing validation which causes denial of service via 'DeleteSessionTensor'.", "cve": "CVE-2022-29194", "id": "pyup.io-55527", "more_info_path": "/vulnerabilities/CVE-2022-29194/55527", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29192: missing validation which crashes 'QuantizeAndDequantizeV4Grad'.", "cve": "CVE-2022-29192", "id": "pyup.io-55541", "more_info_path": "/vulnerabilities/CVE-2022-29192/55541", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35995: 'CHECK' fail in 'AudioSummaryV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9h5-vr8m-x2h4", "cve": "CVE-2022-35995", "id": "pyup.io-55509", "more_info_path": "/vulnerabilities/CVE-2022-35995/55509", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36026: 'CHECK' fail in 'QuantizeAndDequantizeV3'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9cr2-8pwr-fhfq", "cve": "CVE-2022-36026", "id": "pyup.io-55488", "more_info_path": "/vulnerabilities/CVE-2022-36026/55488", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35970: Segfault in 'QuantizedInstanceNorm'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g35r-369w-3fqp", "cve": "CVE-2022-35970", "id": "pyup.io-55503", "more_info_path": "/vulnerabilities/CVE-2022-35970/55503", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36001: 'CHECK' fail in 'DrawBoundingBoxes'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jqm7-m5q7-3hm5", "cve": "CVE-2022-36001", "id": "pyup.io-55506", "more_info_path": "/vulnerabilities/CVE-2022-36001/55506", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35988: 'CHECK' fail in 'tf.linalg.matrix_rank'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vqj-64pv-w55c", "cve": "CVE-2022-35988", "id": "pyup.io-55498", "more_info_path": "/vulnerabilities/CVE-2022-35988/55498", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35972: Segfault in 'QuantizedBiasAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4pc4-m9mj-v2r9", "cve": "CVE-2022-35972", "id": "pyup.io-55493", "more_info_path": "/vulnerabilities/CVE-2022-35972/55493", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35985: 'CHECK' fail in 'LRNGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9942-r22v-78cp", "cve": "CVE-2022-35985", "id": "pyup.io-55467", "more_info_path": "/vulnerabilities/CVE-2022-35985/55467", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35982: Segfault in 'SparseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-397c-5g2j-qxpv", "cve": "CVE-2022-35982", "id": "pyup.io-55492", "more_info_path": "/vulnerabilities/CVE-2022-35982/55492", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35969: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q2c3-jpmc-gfjx", "cve": "CVE-2022-35969", "id": "pyup.io-55468", "more_info_path": "/vulnerabilities/CVE-2022-35969/55468", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35979: Segfault in 'QuantizedRelu' and 'QuantizedRelu6'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v7vw-577f-vp8x", "cve": "CVE-2022-35979", "id": "pyup.io-55463", "more_info_path": "/vulnerabilities/CVE-2022-35979/55463", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36017: Segfault in 'Requantize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wqmc-pm8c-2jhc", "cve": "CVE-2022-36017", "id": "pyup.io-55464", "more_info_path": "/vulnerabilities/CVE-2022-36017/55464", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36016: 'CHECK'-fail in 'tensorflow::full_type::SubstituteFromAttrs'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g468-qj8g-vcjc", "cve": "CVE-2022-36016", "id": "pyup.io-55497", "more_info_path": "/vulnerabilities/CVE-2022-36016/55497", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36011: Null dereference on MLIR on empty function attributes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fv43-93gv-vm8f", "cve": "CVE-2022-36011", "id": "pyup.io-55490", "more_info_path": "/vulnerabilities/CVE-2022-36011/55490", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35997: 'CHECK' fail in 'tf.sparse.cross'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p7hr-f446-x6qf", "cve": "CVE-2022-35997", "id": "pyup.io-55478", "more_info_path": "/vulnerabilities/CVE-2022-35997/55478", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35986: Segfault in 'RaggedBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wr9v-g9vf-c74v", "cve": "CVE-2022-35986", "id": "pyup.io-55484", "more_info_path": "/vulnerabilities/CVE-2022-35986/55484", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35974: Segfault in 'QuantizeDownAndShrinkRange'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vgvh-2pf4-jr2x", "cve": "CVE-2022-35974", "id": "pyup.io-55485", "more_info_path": "/vulnerabilities/CVE-2022-35974/55485", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35973: Segfault in 'QuantizedMatMul'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-689c-r7h2-fv9v", "cve": "CVE-2022-35973", "id": "pyup.io-55486", "more_info_path": "/vulnerabilities/CVE-2022-35973/55486", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35963: 'CHECK' failures in 'FractionalAvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-84jm-4cf3-9jfm", "cve": "CVE-2022-35963", "id": "pyup.io-55507", "more_info_path": "/vulnerabilities/CVE-2022-35963/55507", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35971: 'CHECK' fail in 'FakeQuantWithMinMaxVars'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9fpg-838v-wpv7", "cve": "CVE-2022-35971", "id": "pyup.io-55510", "more_info_path": "/vulnerabilities/CVE-2022-35971/55510", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35960: 'CHECK' failure in 'TensorListReserve' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v5xg-3q2c-c2r4", "cve": "CVE-2022-35960", "id": "pyup.io-55462", "more_info_path": "/vulnerabilities/CVE-2022-35960/55462", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35996: Floating point exception in 'Conv2D'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q5jv-m6qw-5g37", "cve": "CVE-2022-35996", "id": "pyup.io-55474", "more_info_path": "/vulnerabilities/CVE-2022-35996/55474", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35939: OOB write in 'scatter_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-ffjm-4qwc-7cmf", "cve": "CVE-2022-35939", "id": "pyup.io-55460", "more_info_path": "/vulnerabilities/CVE-2022-35939/55460", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35999: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-37jf-mjv6-xfqw", "cve": "CVE-2022-35999", "id": "pyup.io-55508", "more_info_path": "/vulnerabilities/CVE-2022-35999/55508", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36019: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannel'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9j4v-pp28-mxv7", "cve": "CVE-2022-36019", "id": "pyup.io-55500", "more_info_path": "/vulnerabilities/CVE-2022-36019/55500", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35964: Segfault in 'BlockLSTMGradV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f7r5-q7cx-h668", "cve": "CVE-2022-35964", "id": "pyup.io-55477", "more_info_path": "/vulnerabilities/CVE-2022-35964/55477", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35992: 'CHECK' fail in 'TensorListFromTensor'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9v8w-xmr4-wgxp", "cve": "CVE-2022-35992", "id": "pyup.io-55483", "more_info_path": "/vulnerabilities/CVE-2022-35992/55483", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35959: 'CHECK' failures in 'AvgPool3DGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wxjj-cgcx-r3vq", "cve": "CVE-2022-35959", "id": "pyup.io-55476", "more_info_path": "/vulnerabilities/CVE-2022-35959/55476", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36027: Segfault TFLite converter on per-channel quantized transposed convolutions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-79h2-q768-fpxr", "cve": "CVE-2022-36027", "id": "pyup.io-55491", "more_info_path": "/vulnerabilities/CVE-2022-36027/55491", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36012: Assertion fail on MLIR empty edge names.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jvhc-5hhr-w3v5", "cve": "CVE-2022-36012", "id": "pyup.io-55471", "more_info_path": "/vulnerabilities/CVE-2022-36012/55471", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36000: 'CHECK' fail in 'Eig'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqxc-pvf8-2w9v", "cve": "CVE-2022-36000", "id": "pyup.io-55482", "more_info_path": "/vulnerabilities/CVE-2022-36000/55482", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35940: Int overflow in 'RaggedRangeOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x989-q2pq-4q5x", "cve": "CVE-2022-35940", "id": "pyup.io-55505", "more_info_path": "/vulnerabilities/CVE-2022-35940/55505", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36002: 'CHECK' fail in 'Unbatch'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mh3m-62v7-68xg", "cve": "CVE-2022-36002", "id": "pyup.io-55470", "more_info_path": "/vulnerabilities/CVE-2022-36002/55470", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35994: 'CHECK' fail in 'CollectiveGather'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fhfc-2q7x-929f", "cve": "CVE-2022-35994", "id": "pyup.io-55504", "more_info_path": "/vulnerabilities/CVE-2022-35994/55504", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36014: Null-dereference in 'mlir::tfg::TFOp::nameAttr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7j3m-8g3c-9qqq", "cve": "CVE-2022-36014", "id": "pyup.io-55495", "more_info_path": "/vulnerabilities/CVE-2022-36014/55495", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35983: 'CHECK' fail in 'Save' and 'SaveSlices'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6vp-8q9j-whx4", "cve": "CVE-2022-35983", "id": "pyup.io-55472", "more_info_path": "/vulnerabilities/CVE-2022-35983/55472", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35981: 'CHECK' fail in 'FractionalMaxPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vxv8-r8q2-63xw", "cve": "CVE-2022-35981", "id": "pyup.io-55481", "more_info_path": "/vulnerabilities/CVE-2022-35981/55481", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35965: Segfault in 'LowerBound' and 'UpperBound'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qxpx-j395-pw36", "cve": "CVE-2022-35965", "id": "pyup.io-55499", "more_info_path": "/vulnerabilities/CVE-2022-35965/55499", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35993: 'CHECK' fail in 'SetSize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wq6q-6m32-9rv9", "cve": "CVE-2022-35993", "id": "pyup.io-55494", "more_info_path": "/vulnerabilities/CVE-2022-35993/55494", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36005: 'CHECK' fail in 'FakeQuantWithMinMaxVarsGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r26c-679w-mrjm", "cve": "CVE-2022-36005", "id": "pyup.io-55514", "more_info_path": "/vulnerabilities/CVE-2022-36005/55514", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35968: 'CHECK' fail in 'AvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2475-53vw-vp25", "cve": "CVE-2022-35968", "id": "pyup.io-55502", "more_info_path": "/vulnerabilities/CVE-2022-35968/55502", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36004: 'CHECK' fail in 'tf.random.gamma'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv8m-8x97-937q", "cve": "CVE-2022-36004", "id": "pyup.io-55511", "more_info_path": "/vulnerabilities/CVE-2022-36004/55511", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36003: 'CHECK' fail in 'RandomPoissonV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cv2p-32v3-vhwq", "cve": "CVE-2022-36003", "id": "pyup.io-55466", "more_info_path": "/vulnerabilities/CVE-2022-36003/55466", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35998: 'CHECK' fail in 'EmptyTensorList'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhw4-wwr7-gjc5", "cve": "CVE-2022-35998", "id": "pyup.io-55479", "more_info_path": "/vulnerabilities/CVE-2022-35998/55479", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36015: Integer overflow in math ops. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rh87-q4vg-m45j", "cve": "CVE-2022-36015", "id": "pyup.io-55465", "more_info_path": "/vulnerabilities/CVE-2022-36015/55465", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36018: 'CHECK' fail in 'RaggedTensorToVariant'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6cv-4fmf-66xf", "cve": "CVE-2022-36018", "id": "pyup.io-55512", "more_info_path": "/vulnerabilities/CVE-2022-36018/55512", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35990: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannelGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h7ff-cfc9-wmmh", "cve": "CVE-2022-35990", "id": "pyup.io-55475", "more_info_path": "/vulnerabilities/CVE-2022-35990/55475", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35989: 'CHECK' fail in 'MaxPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j43h-pgmg-5hjq", "cve": "CVE-2022-35989", "id": "pyup.io-55513", "more_info_path": "/vulnerabilities/CVE-2022-35989/55513", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35987: 'CHECK' fail in 'DenseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w62h-8xjm-fv49", "cve": "CVE-2022-35987", "id": "pyup.io-55487", "more_info_path": "/vulnerabilities/CVE-2022-35987/55487", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35984: 'CHECK' fail in 'ParameterizedTruncatedNormal'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2xf-8hgm-hpw5", "cve": "CVE-2022-35984", "id": "pyup.io-55473", "more_info_path": "/vulnerabilities/CVE-2022-35984/55473", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35967: Segfault in 'QuantizedAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v6h3-348g-6h5x", "cve": "CVE-2022-35967", "id": "pyup.io-55501", "more_info_path": "/vulnerabilities/CVE-2022-35967/55501", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35966: Segfault in 'QuantizedAvgPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4w68-4x85-mjj9", "cve": "CVE-2022-35966", "id": "pyup.io-55489", "more_info_path": "/vulnerabilities/CVE-2022-35966/55489", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35941: 'CHECK' failure in 'AvgPoolOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mgmh-g2v6-mqw5", "cve": "CVE-2022-35941", "id": "pyup.io-55496", "more_info_path": "/vulnerabilities/CVE-2022-35941/55496", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35937: OOB read in 'Gather_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pxrw-j2fv-hx3h", "cve": "CVE-2022-35937", "id": "pyup.io-55459", "more_info_path": "/vulnerabilities/CVE-2022-35937/55459", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35934: 'CHECK' failure in tf.reshape via overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f4w6-h4f5-wx45", "cve": "CVE-2022-35934", "id": "pyup.io-55469", "more_info_path": "/vulnerabilities/CVE-2022-35934/55469", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36013: Null-dereference in 'mlir::tfg::GraphDefImporter::ConvertNodeDef'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-828c-5j5q-vrjq", "cve": "CVE-2022-36013", "id": "pyup.io-55480", "more_info_path": "/vulnerabilities/CVE-2022-36013/55480", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35952: 'CHECK' failures in 'UnbatchGradOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h5vq-gw2c-pq47", "cve": "CVE-2022-35952", "id": "pyup.io-55461", "more_info_path": "/vulnerabilities/CVE-2022-35952/55461", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41891: If 'tf.raw_ops.TensorListConcat' is given 'element_shape=[]', it results segmentation fault which can be used to trigger a denial of service attack.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-66vq-54fq-6jvv", "cve": "CVE-2022-41891", "id": "pyup.io-55437", "more_info_path": "/vulnerabilities/CVE-2022-41891/55437", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41886: When 'tf.raw_ops.ImageProjectiveTransformV2' is given a large output shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-54pp-c6pp-7fpx", "cve": "CVE-2022-41886", "id": "pyup.io-55453", "more_info_path": "/vulnerabilities/CVE-2022-41886/55453", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41885: When 'tf.raw_ops.FusedResizeAndPadConv2D' is given a large tensor shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-762h-vpvw-3rcx", "cve": "CVE-2022-41885", "id": "pyup.io-55440", "more_info_path": "/vulnerabilities/CVE-2022-41885/55440", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41899: TensorFlow is an open source platform for machine learning. Inputs 'dense_features' or 'example_state_data' not of rank 2 will trigger a 'CHECK' fail in 'SdcaOptimizer'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-27rc-728f-x5w2", "cve": "CVE-2022-41899", "id": "pyup.io-55441", "more_info_path": "/vulnerabilities/CVE-2022-41899/55441", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41893: If 'tf.raw_ops.TensorListResize' is given a nonscalar value for input 'size', it results 'CHECK' fail which can be used to trigger a denial of service attack.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-67pf-62xr-q35m", "cve": "CVE-2022-41893", "id": "pyup.io-55442", "more_info_path": "/vulnerabilities/CVE-2022-41893/55442", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41889: If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a 'nullptr', which is not caught. An example can be seen in 'tf.compat.v1.extract_volume_patches' by passing in quantized tensors as input 'ksizes'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xxcj-rhqg-m46g", "cve": "CVE-2022-41889", "id": "pyup.io-55439", "more_info_path": "/vulnerabilities/CVE-2022-41889/55439", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1.", "cve": "CVE-2022-41902", "id": "pyup.io-55449", "more_info_path": "/vulnerabilities/CVE-2022-41902/55449", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41909: An input 'encoded' that is not a valid 'CompositeTensorVariant' tensor will trigger a segfault in 'tf.raw_ops.CompositeTensorVariantToComponents'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjx6-v474-2ch9", "cve": "CVE-2022-41909", "id": "pyup.io-55443", "more_info_path": "/vulnerabilities/CVE-2022-41909/55443", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41908: TensorFlow is an open source platform for machine learning. An input 'token' that is not a UTF-8 bytestring will trigger a 'CHECK' fail in 'tf.raw_ops.PyFunc'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv77-9g28-cwg3", "cve": "CVE-2022-41908", "id": "pyup.io-55444", "more_info_path": "/vulnerabilities/CVE-2022-41908/55444", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41901: An input 'sparse_matrix' that is not a matrix with a shape with rank 0 will trigger a 'CHECK' fail in 'tf.raw_ops.SparseMatrixNNZ'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9fm-r5mm-rf9f", "cve": "CVE-2022-41901", "id": "pyup.io-55435", "more_info_path": "/vulnerabilities/CVE-2022-41901/55435", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41900: The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xvwp-h6jv-7472", "cve": "CVE-2022-41900", "id": "pyup.io-55445", "more_info_path": "/vulnerabilities/CVE-2022-41900/55445", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41910: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-frqp-wp83-qggv", "cve": "CVE-2022-41910", "id": "pyup.io-55454", "more_info_path": "/vulnerabilities/CVE-2022-41910/55454", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41894: The reference kernel of the 'CONV_3D_TRANSPOSE' TensorFlow Lite operator wrongly increments the data_ptr when adding the bias to the result. Instead of 'data_ptr += num_channels;' it should be 'data_ptr += output_num_channels;' as if the number of input channels is different than the number of output channels, the wrong result will be returned and a buffer overflow will occur if num_channels > output_num_channels. An attacker can craft a model with a specific number of input channels. It is then possible to write specific values through the bias of the layer outside the bounds of the buffer. This attack only works if the reference kernel resolver is used in the interpreter.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6q3-vv32-2cq5", "cve": "CVE-2022-41894", "id": "pyup.io-55456", "more_info_path": "/vulnerabilities/CVE-2022-41894/55456", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41884: If a numpy array is created with a shape such that one element is zero and the others sum to a large number, an error will be raised. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jq6x-99hj-q636", "cve": "CVE-2022-41884", "id": "pyup.io-55451", "more_info_path": "/vulnerabilities/CVE-2022-41884/55451", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41911: When printing a tensor, we get it's data as a 'const char*' array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from 'char' to 'bool' are undefined if the 'char' is not '0' or '1', so sanitizers/fuzzers will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j", "cve": "CVE-2022-41911", "id": "pyup.io-55438", "more_info_path": "/vulnerabilities/CVE-2022-41911/55438", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41880: When the 'BaseCandidateSamplerOp' function receives a value in 'true_classes' larger than 'range_max', a heap oob read occurs.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8w5g-3wcv-9g2j", "cve": "CVE-2022-41880", "id": "pyup.io-55447", "more_info_path": "/vulnerabilities/CVE-2022-41880/55447", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41897: If 'FractionMaxPoolGrad' is given outsize inputs 'row_pooling_sequence' and 'col_pooling_sequence', TensorFlow will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2w8-jw48-fr7j", "cve": "CVE-2022-41897", "id": "pyup.io-55452", "more_info_path": "/vulnerabilities/CVE-2022-41897/55452", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41896: If 'ThreadUnsafeUnigramCandidateSampler' is given input 'filterbank_channel_count' greater than the allowed max size, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rmg2-f698-wq35", "cve": "CVE-2022-41896", "id": "pyup.io-55450", "more_info_path": "/vulnerabilities/CVE-2022-41896/55450", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41890: If 'BCast::ToShape' is given input larger than an 'int32', it will crash, despite being supposed to handle up to an 'int64'. An example can be seen in 'tf.experimental.numpy.outer' by passing in large input to the input 'b'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h246-cgh4-7475", "cve": "CVE-2022-41890", "id": "pyup.io-55446", "more_info_path": "/vulnerabilities/CVE-2022-41890/55446", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41907: When 'tf.raw_ops.ResizeNearestNeighborGrad' is given a large 'size' input, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-368v-7v32-52fx", "cve": "CVE-2022-41907", "id": "pyup.io-55448", "more_info_path": "/vulnerabilities/CVE-2022-41907/55448", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41895: If 'MirrorPadGrad' is given outsize input 'paddings', TensorFlow will give a heap OOB error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gq2j-cr96-gvqx", "cve": "CVE-2022-41895", "id": "pyup.io-55436", "more_info_path": "/vulnerabilities/CVE-2022-41895/55436", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41898: If 'SparseFillEmptyRowsGrad' is given empty inputs, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hq7g-wwwp-q46h", "cve": "CVE-2022-41898", "id": "pyup.io-55455", "more_info_path": "/vulnerabilities/CVE-2022-41898/55455", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35935: 'CHECK' failure in 'SobolSample' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-97p7-w86h-vcf9\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqvq-fvhr-v6hc", "cve": "CVE-2022-35935", "id": "pyup.io-55457", "more_info_path": "/vulnerabilities/CVE-2022-35935/55457", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-cpu 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35991: 'CHECK' fail in 'TensorListScatter' and 'TensorListScatterV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vm7x-4qhj-rrcq\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xf83-q765-xm6m", "cve": "CVE-2022-35991", "id": "pyup.io-55458", "more_info_path": "/vulnerabilities/CVE-2022-35991/55458", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-cpu 2.9.3 and 2.10.1 include a fix for CVE-2022-41887: 'tf.keras.losses.poisson' receives a 'y_pred' and 'y_true' that are passed through 'functor::mul' in 'BinaryOp'. If the resulting dimensions overflow an 'int32', TensorFlow will crash due to a size mismatch during broadcast assignment.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fvv-46hw-vpg3", "cve": "CVE-2022-41887", "id": "pyup.io-55434", "more_info_path": "/vulnerabilities/CVE-2022-41887/55434", "specs": [ "<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Some versions of tensorflow-cpu are susceptible to a Denial of Service (DoS) attack, triggered by another instance of CVE-2022-35935, involving SobolSample and the assumption of scalar inputs.", "cve": "PVE-2024-99848", "id": "pyup.io-65572", "more_info_path": "/vulnerabilities/PVE-2024-99848/65572", "specs": [ ">=0,<2.8.4", ">=2.9.0,<2.9.3", ">=2.10.0,<2.10.1" ], "v": ">=0,<2.8.4,>=2.9.0,<2.9.3,>=2.10.0,<2.10.1" }, { "advisory": "Some versions of tensorflow-cpu are susceptible to a Denial of Service (DoS) attack using a method similar to CVE-2022-35991, exploiting TensorListScatter and TensorListScatterV2 with non-scalar inputs.", "cve": "PVE-2024-99847", "id": "pyup.io-65573", "more_info_path": "/vulnerabilities/PVE-2024-99847/65573", "specs": [ ">=0,<2.8.4", ">=2.9.0,<2.9.3", ">=2.10.0,<2.10.1" ], "v": ">=0,<2.8.4,>=2.9.0,<2.9.3,>=2.10.0,<2.10.1" }, { "advisory": "Tensorflow-cpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 updates its dependency \"SQLite\" to handle CVE-2020-15358.", "cve": "CVE-2020-15358", "id": "pyup.io-55856", "more_info_path": "/vulnerabilities/CVE-2020-15358/55856", "specs": [ ">=1.15.0rc0,<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=1.15.0rc0,<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 1.15.2 and 2.0.1 includes a fix for CVE-2020-5215: In TensorFlow before 1.15.2 and 2.0.1, converting a string (from Python) to a tf.float16 value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode. This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a tf.float16 value. Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar tf.float16 value with a scalar string will trigger this issue due to automatic conversions. This can be easily reproduced by tf.constant(\"hello\", tf.float16), if eager execution is enabled.", "cve": "CVE-2020-5215", "id": "pyup.io-55883", "more_info_path": "/vulnerabilities/CVE-2020-5215/55883", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-cpu versions 1.15.2 and 2.0.1 updates its dependency \"curl\" to handle CVE-2019-5481.", "cve": "CVE-2019-5481", "id": "pyup.io-55879", "more_info_path": "/vulnerabilities/CVE-2019-5481/55879", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-cpu versions 1.15.2 and 2.0.1 update its dependency \"SQLite\" to handle CVE-2019-19646.", "cve": "CVE-2019-19646", "id": "pyup.io-55882", "more_info_path": "/vulnerabilities/CVE-2019-19646/55882", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-cpu versions 1.15.2 and 2.0.1 updates 'sqlite3' to handle CVE-2019-16168.", "cve": "CVE-2019-16168", "id": "pyup.io-55880", "more_info_path": "/vulnerabilities/CVE-2019-16168/55880", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-cpu versions 1.15.2 and 2.0.1 updates its dependency \"curl\" to handle CVE-2019-5482.", "cve": "CVE-2019-5482", "id": "pyup.io-55881", "more_info_path": "/vulnerabilities/CVE-2019-5482/55881", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-cpu versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 include a fix for CVE-2021-29567: Due to lack of validation in 'tf.raw_ops.SparseDenseCwiseMul', an attacker can trigger denial of service via 'CHECK'-fails or accesses to outside the bounds of heap allocated data. Since the implementation (https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80), it only validates the rank of the input arguments but no constraints between dimensions (https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul) and an attacker can abuse them to trigger internal 'CHECK' assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers.", "cve": "CVE-2021-29567", "id": "pyup.io-55869", "more_info_path": "/vulnerabilities/CVE-2021-29567/55869", "specs": [ ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.5.0rc0,<2.5.0" ], "v": ">=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.5.0rc0,<2.5.0" }, { "advisory": "Tensorflow-cpu 2.10.1 includes a fix for CVE-2022-41883: When ops that have specified input sizes receive a differing number of inputs, the executor will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj", "cve": "CVE-2022-41883", "id": "pyup.io-55433", "more_info_path": "/vulnerabilities/CVE-2022-41883/55433", "specs": [ ">=2.10.0rc0,<2.10.1" ], "v": ">=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15192: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to 'dlpack.to_dlpack' there is a memory leak following an expected validation failure. The issue occurs because the 'status' argument during validation failures is not properly checked. Since each of the above methods can return an error status, the 'status' value must be checked before continuing.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fxw-76px-3rxv", "cve": "CVE-2020-15192", "id": "pyup.io-55867", "more_info_path": "/vulnerabilities/CVE-2020-15192/55867", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15193: In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of \"dlpack.to_dlpack\" can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing in a Python object instead of a tensor. The uninitialized memory address is due to a \"reinterpret_cast\". Since the \"PyObject\" is a Python object, not a Tensorflow tensor, the cast to \"EagerTensor\" fails. The issue was patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v", "cve": "CVE-2020-15193", "id": "pyup.io-55868", "more_info_path": "/vulnerabilities/CVE-2020-15193/55868", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15213: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimension of the output tensor, attackers can use a very large value to trigger a large allocation. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps. However, if the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hjmq-236j-8m87", "cve": "CVE-2020-15213", "id": "pyup.io-55864", "more_info_path": "/vulnerabilities/CVE-2020-15213/55864", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15214: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimension of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15214", "id": "pyup.io-55866", "more_info_path": "/vulnerabilities/CVE-2020-15214/55866", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15212: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to \"segment_ids_data\" can alter \"output_index\" and then write to outside of \"output_data\" buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15212", "id": "pyup.io-55865", "more_info_path": "/vulnerabilities/CVE-2020-15212/55865", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15191: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to 'dlpack.to_dlpack' the expected validations will cause variables to bind to 'nullptr' while setting a 'status' variable to the error condition. However, this 'status' argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with '-fsanitize=null'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr", "cve": "CVE-2020-15191", "id": "pyup.io-55863", "more_info_path": "/vulnerabilities/CVE-2020-15191/55863", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu 2.3.1 includes a fix for CVE-2020-15200: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Thus, the code sets up conditions to cause a heap buffer overflow. A \"BatchedMap\" is equivalent to a vector where each element is a hashmap. However, if the first element of \"splits_values\" is not 0, \"batch_idx\" will never be 1, hence there will be no hashmap at index 0 in \"per_batch_counts\". Trying to access that in the user code results in a segmentation fault. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x7rp-74x2-mjf3", "cve": "CVE-2020-15200", "id": "pyup.io-55860", "more_info_path": "/vulnerabilities/CVE-2020-15200/55860", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu 2.3.1 includes a fix for CVE-2020-15201: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Hence, the code is prone to heap buffer overflow. If \"split_values\" does not end with a value at least \"num_values\" then the \"while\" loop condition will trigger a read outside of the bounds of \"split_values\" once \"batch_idx\" grows too large. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4", "cve": "CVE-2020-15201", "id": "pyup.io-55862", "more_info_path": "/vulnerabilities/CVE-2020-15201/55862", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu 2.3.1 includes a fix for CVE-2020-15199: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the \"splits\" tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure. Since \"BatchedMap\" is equivalent to a vector, it needs to have at least one element to not be \"nullptr\". If user passes a \"splits\" tensor that is empty or has exactly one element, we get a \"SIGABRT\" signal raised by the operating system. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x5cp-9pcf-pp3h", "cve": "CVE-2020-15199", "id": "pyup.io-55861", "more_info_path": "/vulnerabilities/CVE-2020-15199/55861", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu version 2.3.1 includes a fix for CVE-2020-15197: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix. However, malicious users can pass in tensors of different rank, resulting in a \"CHECK\" assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.", "cve": "CVE-2020-15197", "id": "pyup.io-55857", "more_info_path": "/vulnerabilities/CVE-2020-15197/55857", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu version 2.3.1 includes a fix for CVE-2020-15196: In Tensorflow version 2.3.0, the \"SparseCountSparseOutput\" and \"RaggedCountSparseOutput\" implementations don't validate that the \"weights\" tensor has the same shape as the data. The check exists for \"DenseCountSparseOutput\", where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph", "cve": "CVE-2020-15196", "id": "pyup.io-55859", "more_info_path": "/vulnerabilities/CVE-2020-15196/55859", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu 2.3.1 includes a fix for CVE-2020-15198: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has the same shape as the \"values\" one. The values in these tensors are always accessed in parallel. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3", "cve": "CVE-2020-15198", "id": "pyup.io-55858", "more_info_path": "/vulnerabilities/CVE-2020-15198/55858", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37680: In affected versions the implementation of fully connected layers in TFLite is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226). The Tensorflow team has patched the issue in GitHub commit 718721986aa137691ee23f03638867151f74935f.", "cve": "CVE-2021-37680", "id": "pyup.io-55818", "more_info_path": "/vulnerabilities/CVE-2021-37680/55818", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37648: In affected versions the code for 'tf.raw_ops.SaveV2' does not properly validate the inputs and an attacker can trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses 'ValidateInputs' to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above. However, the validation uses 'OP_REQUIRES' which translates to setting the 'Status' object of the current 'OpKernelContext' to an error status, followed by an empty 'return' statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the nQext line in 'Compute' that follows the call to 'ValidateInputs'. This is equivalent to lacking the validation. The Tensorflow team has patched the issue in GitHub commit 9728c60e136912a12d99ca56e106b7cce7af5986.", "cve": "CVE-2021-37648", "id": "pyup.io-55813", "more_info_path": "/vulnerabilities/CVE-2021-37648/55813", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37683: In affected versions the implementation of division in TFLite is vulnerable to a division by 0 error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc). There is no check that the divisor tensor does not contain zero elements. The Tensorflow team has patched the issue in GitHub commit 1e206baedf8bef0334cca3eb92bab134ef525a28.", "cve": "CVE-2021-37683", "id": "pyup.io-55816", "more_info_path": "/vulnerabilities/CVE-2021-37683/55816", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37642: In affected versions the implementation of 'tf.raw_ops.ResourceScatterDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit 4aacb30888638da75023e6601149415b39763d76.", "cve": "CVE-2021-37642", "id": "pyup.io-55820", "more_info_path": "/vulnerabilities/CVE-2021-37642/55820", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37689: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. This is caused by the MLIR optimization of 'L2NormalizeReduceAxis' operator. The implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/compiler/mlir/lite/transforms/optimize.cc#L67-L70) unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements. The Tensorflow team has patched the issue in GitHub commit d6b57f461b39fd1aa8c1b870f1b974aac3554955.", "cve": "CVE-2021-37689", "id": "pyup.io-55812", "more_info_path": "/vulnerabilities/CVE-2021-37689/55812", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37671: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.Map*' and 'tf.raw_ops.OrderedMap*' operations. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that 'indices' is in ascending order, but does not check that 'indices' is not empty. The Tensorflow team has patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac.", "cve": "CVE-2021-37671", "id": "pyup.io-55811", "more_info_path": "/vulnerabilities/CVE-2021-37671/55811", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37635: In affected versions the implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data. The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor. The Tensorflow team has patched the issue in GitHub commit 87158f43f05f2720a374f3e6d22a7aaa3a33f750.", "cve": "CVE-2021-37635", "id": "pyup.io-55814", "more_info_path": "/vulnerabilities/CVE-2021-37635/55814", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37636: In affected versions the implementation of 'tf.raw_ops.SparseDenseCwiseDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L56) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit d9204be9f49520cdaaeb2541d1dc5187b23f31d9.", "cve": "CVE-2021-37636", "id": "pyup.io-55819", "more_info_path": "/vulnerabilities/CVE-2021-37636/55819", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37637: It is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid. The Tensorflow team has patched the issue in GitHub commit 5dc7f6981fdaf74c8c5be41f393df705841fb7c5.", "cve": "CVE-2021-37637", "id": "pyup.io-55817", "more_info_path": "/vulnerabilities/CVE-2021-37637/55817", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37667: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.UnicodeEncode'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the 'input_splits' tensor before validating that this tensor is not empty. The Tensorflow team has patched the issue in GitHub commit 2e0ee46f1a47675152d3d865797a18358881d7a6.", "cve": "CVE-2021-37667", "id": "pyup.io-55815", "more_info_path": "/vulnerabilities/CVE-2021-37667/55815", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37654: In affected versions an attacker can trigger a crash via a 'CHECK'-fail in debug builds of TensorFlow using 'tf.raw_ops.ResourceGather' or a read from outside the bounds of heap allocated data in the same API in a release build. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the 'batch_dims' value that the user supplies is less than the rank of the input tensor. Since the implementation uses several for loops over the dimensions of 'tensor', this results in reading data from outside the bounds of heap allocated buffer backing the tensor. The Tensorflow team has patched the issue in GitHub commit bc9c546ce7015c57c2f15c168b3d9201de679a1d.", "cve": "CVE-2021-37654", "id": "pyup.io-55802", "more_info_path": "/vulnerabilities/CVE-2021-37654/55802", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37639: When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the 'tensor_name' user controlled input and immediately retrieves the tensor at the restoration index (controlled via 'preferred_shard' argument). This occurs without validating that the provided list has enough values. If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements and if the restoration index is outside the bounds, this results in heap OOB read. The Tensorflow team has patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622.", "cve": "CVE-2021-37639", "id": "pyup.io-55805", "more_info_path": "/vulnerabilities/CVE-2021-37639/55805", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37664: In affected versions an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range. The Tensorflow team has patched the issue in GitHub commit e84c975313e8e8e38bb2ea118196369c45c51378.", "cve": "CVE-2021-37664", "id": "pyup.io-55809", "more_info_path": "/vulnerabilities/CVE-2021-37664/55809", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37651: In affected versions the implementation for 'tf.raw_ops.FractionalAvgPoolGrad' can be tricked into accessing data outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty 'EigenDoubleMatrixMap' and then accesses this buffer with indices that are outside of the empty area. The Tensorflow team has patched the issue in GitHub commit 0f931751fb20f565c4e94aa6df58d54a003cdb30.", "cve": "CVE-2021-37651", "id": "pyup.io-55803", "more_info_path": "/vulnerabilities/CVE-2021-37651/55803", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37638: Sending invalid argument for 'row_partition_types' of 'tf.raw_ops.RaggedTensorToTensor' API results in a null pointer dereference and undefined behavior. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty. The Tensorflow team has patched the issue in GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314.", "cve": "CVE-2021-37638", "id": "pyup.io-55801", "more_info_path": "/vulnerabilities/CVE-2021-37638/55801", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37652: In affected versions the implementation for 'tf.raw_ops.BoostedTreesCreateEnsemble' can result in a use after free error if an attacker supplies specially crafted arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent 'free'-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed. The Tensorflow team has patched the issue in GitHub commit 5ecec9c6fbdbc6be03295685190a45e7eee726ab.", "cve": "CVE-2021-37652", "id": "pyup.io-55800", "more_info_path": "/vulnerabilities/CVE-2021-37652/55800", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37659: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations). The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr. We have patched the issue in GitHub commit 93f428fd1768df147171ed674fee1fc5ab8309ec.", "cve": "CVE-2021-37659", "id": "pyup.io-55808", "more_info_path": "/vulnerabilities/CVE-2021-37659/55808", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37649: The code for 'tf.raw_ops.UncompressElement' can be made to trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a 'CompressedElement' from a 'Variant' tensor and then proceeds to dereference it for decompressing. There is no check that the 'Variant' tensor contained a 'CompressedElement', so the pointer is actually 'nullptr'. The Tensorflow team has patched the issue in GitHub commit 7bdf50bb4f5c54a4997c379092888546c97c3ebd.", "cve": "CVE-2021-37649", "id": "pyup.io-55807", "more_info_path": "/vulnerabilities/CVE-2021-37649/55807", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37647: When a user does not supply arguments that determine a valid sparse tensor, 'tf.raw_ops.SparseTensorSliceDataset' implementation can be made to dereference a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either 'indices' or 'values' are provided for an empty sparse tensor when the other is not. If 'indices' is empty, then code that performs validation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference. If 'indices' as provided by the user is empty, then 'indices' in the C++ code above is backed by an empty 'std::vector', hence calling 'indices->dim_size(0)' results in null pointer dereferencing (same as calling 'std::vector::at()' on an empty vector). The Tensorflow team has patched the issue in GitHub commit 02cc160e29d20631de3859c6653184e3f876b9d7.", "cve": "CVE-2021-37647", "id": "pyup.io-55810", "more_info_path": "/vulnerabilities/CVE-2021-37647/55810", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37656: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToSparse'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order. The Tensorflow team has patched the issue in GitHub commit 1071f554dbd09f7e101324d366eec5f4fe5a3ece.", "cve": "CVE-2021-37656", "id": "pyup.io-55804", "more_info_path": "/vulnerabilities/CVE-2021-37656/55804", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37658: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixSetDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit ff8894044dfae5568ecbf2ed514c1a37dc394f1b.", "cve": "CVE-2021-37658", "id": "pyup.io-55806", "more_info_path": "/vulnerabilities/CVE-2021-37658/55806", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Several versions of TensorFlow are affected by CVE-2021-37686: In affected versions, the strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for ellipsis in axis definition (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122). An attacker can craft a model such that 'ellipsis_end_idx' is smaller than 'i' (e.g., always negative). In this case, the inner loop does not increase 'i' and the 'continue' statement causes execution to skip over the preincrement at the end of the outer loop. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695.", "cve": "CVE-2021-37686", "id": "pyup.io-55799", "more_info_path": "/vulnerabilities/CVE-2021-37686/55799", "specs": [ ">=2.3.0rc0,<2.3.4rc0", ">=2.4.0rc0,<2.4.3rc0", ">=2.5.0rc0,<=2.5.0", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4rc0,>=2.4.0rc0,<2.4.3rc0,>=2.5.0rc0,<=2.5.0,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.4.0 includes a fix for CVE-2020-26269: In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.", "cve": "CVE-2020-26269", "id": "pyup.io-55832", "more_info_path": "/vulnerabilities/CVE-2020-26269/55832", "specs": [ ">=2.4.0rc0,<2.4.0" ], "v": ">=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-cpu 2.5.0, 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29614: The implementation of 'tf.io.decode_raw' produces incorrect results and crashes the Python interpreter when combining 'fixed_length' and wider datatypes. The implementation of the padded version (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc) is buggy due to a confusion about pointer arithmetic rules. First, the code computes (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L61) the width of each output element by dividing the 'fixed_length' value to the size of the type argument. The 'fixed_length' argument is also used to determine the size needed for the output tensor (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L63-L79). This is followed by reencoding code (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L85-L94). The erroneous code is the last line above: it is moving the 'out_data' pointer by 'fixed_length * sizeof (T)' bytes whereas it only copied at most 'fixed_length' bytes from the input. This results in parts of the input not being decoded into the output. Furthermore, because the pointer advance is far wider than desired, this quickly leads to writing to outside the bounds of the backing data. This OOB write leads to interpreter crash in the reproducer mentioned here, but more severe attacks can be mounted too, given that this gadget allows writing to periodically placed locations in memory.", "cve": "CVE-2021-29614", "id": "pyup.io-55798", "more_info_path": "/vulnerabilities/CVE-2021-29614/55798", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.5.0rc0,<2.5.0" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.5.0rc0,<2.5.0" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a heap buffer overflow in 'Conv3DBackprop*'. See CVE-2021-29520.", "cve": "CVE-2021-29520", "id": "pyup.io-55788", "more_info_path": "/vulnerabilities/CVE-2021-29520/55788", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv2DBackpropInput'. See CVE-2021-29525.", "cve": "CVE-2021-29525", "id": "pyup.io-55777", "more_info_path": "/vulnerabilities/CVE-2021-29525/55777", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29552: An attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar. Since the tensor is empty the `CHECK` involved in `.scalar()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination.", "cve": "CVE-2021-29552", "id": "pyup.io-55785", "more_info_path": "/vulnerabilities/CVE-2021-29552/55785", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 includes a fix for CVE-2021-29533: An attacker can trigger a denial of service via a 'CHECK' failure by passing an empty image to 'tf.raw_ops.DrawBoundingBoxes'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/ea34a18dc3f5c8d80a40ccca1404f343b5d55f91/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L148-L165) uses 'CHECK_*' assertions instead of 'OP_REQUIRES' to validate user controlled inputs. Whereas 'OP_REQUIRES' allows returning an error condition back to the user, the 'CHECK_*' macros result in a crash if the condition is false, similar to 'assert'. In this case, 'height' is 0 from the 'images' input. This results in 'max_box_row_clamp' being negative and the assertion being falsified, followed by aborting program execution.", "cve": "CVE-2021-29533", "id": "pyup.io-55787", "more_info_path": "/vulnerabilities/CVE-2021-29533/55787", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a stack overflow in 'ParseAttrValue' with nested tensors. See CVE-2021-29615.", "cve": "CVE-2021-29615", "id": "pyup.io-55796", "more_info_path": "/vulnerabilities/CVE-2021-29615/55796", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29549: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero. Since `vector_num_elements` is determined based on input shapes (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L522-L544), a user can trigger scenarios where this quantity is 0.", "cve": "CVE-2021-29549", "id": "pyup.io-55794", "more_info_path": "/vulnerabilities/CVE-2021-29549/55794", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.5.0, 2.4.2, 2.3.3, 2.2.3 and 2.1.4 include a fix for CVE-2021-29548: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the op's contract (https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization).", "cve": "CVE-2021-29548", "id": "pyup.io-55786", "more_info_path": "/vulnerabilities/CVE-2021-29548/55786", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv3DBackprop*'. See CVE-2021-29522.", "cve": "CVE-2021-29522", "id": "pyup.io-55779", "more_info_path": "/vulnerabilities/CVE-2021-29522/55779", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29534: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.SparseConcat'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/b432a38fe0e1b4b904a6c222cbce794c39703e87/tensorflow/core/kernels/sparse_concat_op.cc#L76) takes the values specified in 'shapes[0]' as dimensions for the output shape. The 'TensorShape' constructor (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a 'CHECK' operation which triggers when 'InitDims' (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status. This is a legacy implementation of the constructor and operations should use 'BuildTensorShapeBase' or 'AddDimWithStatus' to prevent 'CHECK'-failures in the presence of overflows.", "cve": "CVE-2021-29534", "id": "pyup.io-55789", "more_info_path": "/vulnerabilities/CVE-2021-29534/55789", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix vulnerabilities where session operations in eager mode lead to null pointer dereferences. See CVE-2021-29518.", "cve": "CVE-2021-29518", "id": "pyup.io-55782", "more_info_path": "/vulnerabilities/CVE-2021-29518/55782", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29532: An attacker can force accesses outside the bounds of heap allocated arrays by passing in invalid tensor values to `tf.raw_ops.RaggedCross`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/efea03b38fb8d3b81762237dc85e579cc5fc6e87/tensorflow/core/kernels/ragged_cross_op.cc#L456-L487) lacks validation for the user supplied arguments. Each of the above branches call a helper function after accessing array elements via a `*_list[next_*]` pattern, followed by incrementing the `next_*` index. However, as there is no validation that the `next_*` values are in the valid range for the corresponding `*_list` arrays, this results in heap OOB reads.", "cve": "CVE-2021-29532", "id": "pyup.io-55780", "more_info_path": "/vulnerabilities/CVE-2021-29532/55780", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29539: TensorFlow is an end-to-end open source platform for machine learning. Calling `tf.raw_ops.ImmutableConst`(https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars. We have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. If using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument.", "cve": "CVE-2021-29539", "id": "pyup.io-55797", "more_info_path": "/vulnerabilities/CVE-2021-29539/55797", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix fixes a heap buffer overflow caused by rounding. See CVE-2021-29529.", "cve": "CVE-2021-29529", "id": "pyup.io-55784", "more_info_path": "/vulnerabilities/CVE-2021-29529/55784", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv2DBackpropFilter'. See CVE-2021-29524.", "cve": "CVE-2021-29524", "id": "pyup.io-55781", "more_info_path": "/vulnerabilities/CVE-2021-29524/55781", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29538: An attacker can cause a division by zero to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments). If all shapes are empty then 'work_unit_size' is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service.", "cve": "CVE-2021-29538", "id": "pyup.io-55793", "more_info_path": "/vulnerabilities/CVE-2021-29538/55793", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by invalid validation in 'SparseMatrixSparseCholesky'. See CVE-2021-29530.", "cve": "CVE-2021-29530", "id": "pyup.io-55776", "more_info_path": "/vulnerabilities/CVE-2021-29530/55776", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a 'CHECK'-fail in 'AddManySparseToTensorsMap'. See CVE-2021-29523.", "cve": "CVE-2021-29523", "id": "pyup.io-55783", "more_info_path": "/vulnerabilities/CVE-2021-29523/55783", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29537: An attacker can cause a heap buffer overflow in `QuantizedResizeBilinear` by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/50711818d2e61ccce012591eeb4fdf93a8496726/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L705-L706) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly.", "cve": "CVE-2021-29537", "id": "pyup.io-55795", "more_info_path": "/vulnerabilities/CVE-2021-29537/55795", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'tf.raw_ops.EncodePng'. See CVE-2021-29531.", "cve": "CVE-2021-29531", "id": "pyup.io-55791", "more_info_path": "/vulnerabilities/CVE-2021-29531/55791", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a segfault in 'SparseCountSparseOutput'. See CVE-2021-29521.", "cve": "CVE-2021-29521", "id": "pyup.io-55792", "more_info_path": "/vulnerabilities/CVE-2021-29521/55792", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a 'CHECK'-fail in 'SparseCross' caused by type confusion. See CVE-2021-29519.", "cve": "CVE-2021-29519", "id": "pyup.io-55778", "more_info_path": "/vulnerabilities/CVE-2021-29519/55778", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29513: Calling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences. The conversion from Python array to C++ array (https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion.", "cve": "CVE-2021-29513", "id": "pyup.io-55790", "more_info_path": "/vulnerabilities/CVE-2021-29513/55790", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29535: An attacker can cause a heap buffer overflow in 'QuantizedMul' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/87cf4d3ea9949051e50ca3f071fc909538a51cd0/tensorflow/core/kernels/quantized_mul_op.cc#L287-L290) assumes that the 4 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29535", "id": "pyup.io-55775", "more_info_path": "/vulnerabilities/CVE-2021-29535/55775", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'StringNGrams'. See CVE-2021-29541.", "cve": "CVE-2021-29541", "id": "pyup.io-55774", "more_info_path": "/vulnerabilities/CVE-2021-29541/55774", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'StringNGrams'. See CVE-2021-29542.", "cve": "CVE-2021-29542", "id": "pyup.io-55773", "more_info_path": "/vulnerabilities/CVE-2021-29542/55773", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29536: An attacker can cause a heap buffer overflow in 'QuantizedReshape' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/a324ac84e573fba362a5e53d4e74d5de6729933e/tensorflow/core/kernels/quantized_reshape_op.cc#L38-L55) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29536", "id": "pyup.io-55772", "more_info_path": "/vulnerabilities/CVE-2021-29536/55772", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29544: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.QuantizeAndDequantizeV4Grad'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the 'input_*' tensors. In turn, this results in the tensors being passes as they are to 'QuantizeAndDequantizePerChannelGradientImpl' (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306). However, the 'vec' method, requires the rank to 1 and triggers a 'CHECK' failure otherwise.", "cve": "CVE-2021-29544", "id": "pyup.io-55771", "more_info_path": "/vulnerabilities/CVE-2021-29544/55771", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29543: An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks.", "cve": "CVE-2021-29543", "id": "pyup.io-55770", "more_info_path": "/vulnerabilities/CVE-2021-29543/55770", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29540: TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L495-L497) computes the size of the filter tensor but does not validate that it matches the number of elements in 'filter_sizes'. Later, when reading/writing to this buffer, code uses the value computed here, instead of the number of elements in the tensor.", "cve": "CVE-2021-29540", "id": "pyup.io-55769", "more_info_path": "/vulnerabilities/CVE-2021-29540/55769", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update its dependency 'curl' to version 7.76.0 to handle CVE-2020-8169.", "cve": "CVE-2020-8169", "id": "pyup.io-55768", "more_info_path": "/vulnerabilities/CVE-2020-8169/55768", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in 'Conv3D'. See CVE-2021-29517.", "cve": "CVE-2021-29517", "id": "pyup.io-55767", "more_info_path": "/vulnerabilities/CVE-2021-29517/55767", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix fixes a null pointer dereference via invalid Ragged Tensors. See CVE-2021-29516.", "cve": "CVE-2021-29516", "id": "pyup.io-55766", "more_info_path": "/vulnerabilities/CVE-2021-29516/55766", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a reference binding to null pointer in 'MatrixDiag*' ops. See CVE-2021-29515.", "cve": "CVE-2021-29515", "id": "pyup.io-55765", "more_info_path": "/vulnerabilities/CVE-2021-29515/55765", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'EmbeddingLookup'. See CVE-2021-29596.", "cve": "CVE-2021-29596", "id": "pyup.io-55764", "more_info_path": "/vulnerabilities/CVE-2021-29596/55764", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's convolution code. See CVE-2021-29594.", "cve": "CVE-2021-29594", "id": "pyup.io-55763", "more_info_path": "/vulnerabilities/CVE-2021-29594/55763", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29558: An attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset.", "cve": "CVE-2021-29558", "id": "pyup.io-55762", "more_info_path": "/vulnerabilities/CVE-2021-29558/55762", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29551: The implementation of 'MatrixTriangularSolve' (https://github.com/tensorflow/tensorflow/blob/8cae746d8449c7dda5298327353d68613f16e798/tensorflow/core/kernels/linalg/matrix_triangular_solve_op_impl.h#L160-L240) fails to terminate kernel execution if one validation condition fails.", "cve": "CVE-2021-29551", "id": "pyup.io-55760", "more_info_path": "/vulnerabilities/CVE-2021-29551/55760", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29545: An attacker can trigger a denial of service via a 'CHECK'-fail in converting sparse tensors to CSR Sparse matrices. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/800346f2c03a27e182dd4fba48295f65e7790739/tensorflow/core/kernels/sparse/kernels.cc#L66) does a double redirection to access an element of an array allocated on the heap. If the value at 'indices(i, 0)' is such that 'indices(i, 0) + 1' is outside the bounds of 'csr_row_ptr', this results in writing outside of bounds of heap allocated data.", "cve": "CVE-2021-29545", "id": "pyup.io-55761", "more_info_path": "/vulnerabilities/CVE-2021-29545/55761", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in TFLite's 'Reshape' operator. See CVE-2021-29592.", "cve": "CVE-2021-29592", "id": "pyup.io-55759", "more_info_path": "/vulnerabilities/CVE-2021-29592/55759", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 include a fix for CVE-2021-29512: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433). Before the 'for' loop, 'batch_idx' is set to 0. The user controls the 'splits' array, making it contain only one element, 0. Thus, the code in the 'while' loop would increment 'batch_idx' and then try to read 'splits(1)', which is outside of bounds.", "cve": "CVE-2021-29512", "id": "pyup.io-55757", "more_info_path": "/vulnerabilities/CVE-2021-29512/55757", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a segfault in 'CTCBeamSearchDecoder'. See CVE-2021-29581.", "cve": "CVE-2021-29581", "id": "pyup.io-55755", "more_info_path": "/vulnerabilities/CVE-2021-29581/55755", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29617: An attacker can cause a denial of service via `CHECK`-fail in `tf.strings.substr` with invalid arguments.", "cve": "CVE-2021-29617", "id": "pyup.io-55756", "more_info_path": "/vulnerabilities/CVE-2021-29617/55756", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an undefined behavior in 'MaxPool3DGradGrad'. See CVE-2021-29574.", "cve": "CVE-2021-29574", "id": "pyup.io-55758", "more_info_path": "/vulnerabilities/CVE-2021-29574/55758", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'tf.raw_ops.CTCLoss'. See CVE-2021-29613.", "cve": "CVE-2021-29613", "id": "pyup.io-55754", "more_info_path": "/vulnerabilities/CVE-2021-29613/55754", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29556: An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.Reverse`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/36229ea9e9451dac14a8b1f4711c435a1d84a594/tensorflow/core/kernels/reverse_op.cc#L75-L76) performs a division based on the first dimension of the tensor argument.", "cve": "CVE-2021-29556", "id": "pyup.io-55753", "more_info_path": "/vulnerabilities/CVE-2021-29556/55753", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'Conv2D'. See CVE-2021-29526.", "cve": "CVE-2021-29526", "id": "pyup.io-55752", "more_info_path": "/vulnerabilities/CVE-2021-29526/55752", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'LoadAndRemapMatrix'. See CVE-2021-29561.", "cve": "CVE-2021-29561", "id": "pyup.io-55749", "more_info_path": "/vulnerabilities/CVE-2021-29561/55749", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'QuantizedConv2D'. See CVE-2021-29527.", "cve": "CVE-2021-29527", "id": "pyup.io-55750", "more_info_path": "/vulnerabilities/CVE-2021-29527/55750", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29595: The implementation of the `DepthToSpace` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69). An attacker can craft a model such that `params->block_size` is 0.", "cve": "CVE-2021-29595", "id": "pyup.io-55751", "more_info_path": "/vulnerabilities/CVE-2021-29595/55751", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29585: The TFLite computation for size of output after padding, `ComputeOutSize`(https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division. Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0.", "cve": "CVE-2021-29585", "id": "pyup.io-55748", "more_info_path": "/vulnerabilities/CVE-2021-29585/55748", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'FusedBatchNorm'. See CVE-2021-29555.", "cve": "CVE-2021-29555", "id": "pyup.io-55746", "more_info_path": "/vulnerabilities/CVE-2021-29555/55746", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'BandedTriangularSolve'. See CVE-2021-29612.", "cve": "CVE-2021-29612", "id": "pyup.io-55742", "more_info_path": "/vulnerabilities/CVE-2021-29612/55742", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap out of bounds read in 'MaxPoolGradWithArgmax'. See CVE-2021-29570.", "cve": "CVE-2021-29570", "id": "pyup.io-55743", "more_info_path": "/vulnerabilities/CVE-2021-29570/55743", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'TransposeConv'. See CVE-2021-29588.", "cve": "CVE-2021-29588", "id": "pyup.io-55740", "more_info_path": "/vulnerabilities/CVE-2021-29588/55740", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'SparseMatMul'. See CVE-2021-29557.", "cve": "CVE-2021-29557", "id": "pyup.io-55741", "more_info_path": "/vulnerabilities/CVE-2021-29557/55741", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB access in unicode ops. See CVE-2021-29559.", "cve": "CVE-2021-29559", "id": "pyup.io-55745", "more_info_path": "/vulnerabilities/CVE-2021-29559/55745", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29589: The reference implementation of the `GatherNd` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/reference_ops.h#L966). An attacker can craft a model such that `params` input would be an empty tensor. In turn, `params_shape.Dims(.)` would be zero, in at least one dimension.", "cve": "CVE-2021-29589", "id": "pyup.io-55744", "more_info_path": "/vulnerabilities/CVE-2021-29589/55744", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29514: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L446). Before the 'for' loop, 'batch_idx' is set to 0. The attacker sets 'splits(0)' to be 7, hence the 'while' loop does not execute and 'batch_idx' remains 0. This then results in writing to 'out(-1, bin)', which is before the heap allocated buffer for the output tensor.", "cve": "CVE-2021-29514", "id": "pyup.io-55747", "more_info_path": "/vulnerabilities/CVE-2021-29514/55747", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'SVDF'. See CVE-2021-29598.", "cve": "CVE-2021-29598", "id": "pyup.io-55729", "more_info_path": "/vulnerabilities/CVE-2021-29598/55729", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29610: The validation in 'tf.raw_ops.QuantizeAndDequantizeV2' allows invalid values for 'axis' argument:. The validation (https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses '||' to mix two different conditions. If 'axis_ < -1' the condition in 'OP_REQUIRES' will still be true, but this value of 'axis_' results in heap underflow. This allows attackers to read/write to other data on the heap.", "cve": "CVE-2021-29610", "id": "pyup.io-55739", "more_info_path": "/vulnerabilities/CVE-2021-29610/55739", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseSparseMinimum'. See CVE-2021-29607.", "cve": "CVE-2021-29607", "id": "pyup.io-55694", "more_info_path": "/vulnerabilities/CVE-2021-29607/55694", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29608: TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in 'tf.raw_ops.RaggedTensorToTensor', an attacker can exploit an undefined behavior if input arguments are empty. The implementation (https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones. There are multiple 'DCHECK' validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything.", "cve": "CVE-2021-29608", "id": "pyup.io-55698", "more_info_path": "/vulnerabilities/CVE-2021-29608/55698", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseAdd'. See CVE-2021-29609.", "cve": "CVE-2021-29609", "id": "pyup.io-55699", "more_info_path": "/vulnerabilities/CVE-2021-29609/55699", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a integer overflow in TFLite concatentation. See CVE-2021-29601.", "cve": "CVE-2021-29601", "id": "pyup.io-55725", "more_info_path": "/vulnerabilities/CVE-2021-29601/55725", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'DepthwiseConv'. See CVE-2021-29602.", "cve": "CVE-2021-29602", "id": "pyup.io-55702", "more_info_path": "/vulnerabilities/CVE-2021-29602/55702", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an undefined behavior and a 'CHECK'-fail in 'FractionalMaxPoolGrad'. See CVE-2021-29580.", "cve": "CVE-2021-29580", "id": "pyup.io-55734", "more_info_path": "/vulnerabilities/CVE-2021-29580/55734", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an overflow and a denial of service in 'tf.raw_ops.ReverseSequence'. See CVE-2021-29575.", "cve": "CVE-2021-29575", "id": "pyup.io-55688", "more_info_path": "/vulnerabilities/CVE-2021-29575/55688", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in optimized pooling implementations in TFLite. See CVE-2021-29586.", "cve": "CVE-2021-29586", "id": "pyup.io-55727", "more_info_path": "/vulnerabilities/CVE-2021-29586/55727", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29563: An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`. Eigen code operating on an empty matrix can trigger on an assertion and will cause program termination.", "cve": "CVE-2021-29563", "id": "pyup.io-55730", "more_info_path": "/vulnerabilities/CVE-2021-29563/55730", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29550: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values. The user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor operation results in `output_size[i]` being 0. The `DCHECK_GT` line is a no-op outside of debug mode, so in released versions of TF this does not trigger. Later, these computed values are used as arguments (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to `GeneratePoolingSequence`(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation. Since `output_length` can be 0, this results in runtime crashing.", "cve": "CVE-2021-29550", "id": "pyup.io-55735", "more_info_path": "/vulnerabilities/CVE-2021-29550/55735", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a integer overflow in TFLite memory allocation. See CVE-2021-29605.", "cve": "CVE-2021-29605", "id": "pyup.io-55711", "more_info_path": "/vulnerabilities/CVE-2021-29605/55711", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'AvgPool3DGrad'. See CVE-2021-29577.", "cve": "CVE-2021-29577", "id": "pyup.io-55708", "more_info_path": "/vulnerabilities/CVE-2021-29577/55708", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseReshape'. See CVE-2021-29611.", "cve": "CVE-2021-29611", "id": "pyup.io-55733", "more_info_path": "/vulnerabilities/CVE-2021-29611/55733", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29566: An attacker can write outside the bounds of heap allocated arrays by passing invalid arguments to 'tf.raw_ops.Dilation2DBackpropInput'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/afd954e65f15aea4d438d0a219136fc4a63a573d/tensorflow/core/kernels/dilation_ops.cc#L321-L322) does not validate before writing to the output array. The values for 'h_out' and 'w_out' are guaranteed to be in range for 'out_backprop' (as they are loop indices bounded by the size of the array). However, there are no similar guarantees relating 'h_in_max'/'w_in_max' and 'in_backprop'.", "cve": "CVE-2021-29566", "id": "pyup.io-55718", "more_info_path": "/vulnerabilities/CVE-2021-29566/55718", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'MaxPool3DGradGrad'. See CVE-2021-29576.", "cve": "CVE-2021-29576", "id": "pyup.io-55712", "more_info_path": "/vulnerabilities/CVE-2021-29576/55712", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'MaxPoolGradWithArgmax'. See CVE-2021-29573.", "cve": "CVE-2021-29573", "id": "pyup.io-55726", "more_info_path": "/vulnerabilities/CVE-2021-29573/55726", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29560: An attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel. Since the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when 'parent_output_index' is shorter than 'row_split'.", "cve": "CVE-2021-29560", "id": "pyup.io-55738", "more_info_path": "/vulnerabilities/CVE-2021-29560/55738", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB write in TFLite. See CVE-2021-29603.", "cve": "CVE-2021-29603", "id": "pyup.io-55716", "more_info_path": "/vulnerabilities/CVE-2021-29603/55716", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of hashtable lookup. See CVE-2021-29604.", "cve": "CVE-2021-29604", "id": "pyup.io-55717", "more_info_path": "/vulnerabilities/CVE-2021-29604/55717", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a segfault in 'tf.raw_ops.SparseCountSparseOutput'. See CVE-2021-29619.", "cve": "CVE-2021-29619", "id": "pyup.io-55700", "more_info_path": "/vulnerabilities/CVE-2021-29619/55700", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix fixes a heap OOB read in TFLite. See CVE-2021-29606.", "cve": "CVE-2021-29606", "id": "pyup.io-55690", "more_info_path": "/vulnerabilities/CVE-2021-29606/55690", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'Split'. See CVE-2021-29599.", "cve": "CVE-2021-29599", "id": "pyup.io-55693", "more_info_path": "/vulnerabilities/CVE-2021-29599/55693", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 update its dependency \"curl\" to handle CVE-2020-8284.", "cve": "CVE-2020-8284", "id": "pyup.io-55709", "more_info_path": "/vulnerabilities/CVE-2020-8284/55709", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'tf.raw_ops.IRFFT'. See CVE-2021-29562.", "cve": "CVE-2021-29562", "id": "pyup.io-55691", "more_info_path": "/vulnerabilities/CVE-2021-29562/55691", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29616: The implementation of TrySimplify (https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/grappler/optimizers/arithmetic_optimizer.cc#L390-L401) has undefined behavior due to dereferencing a null pointer in corner cases that result in optimizing a node with no inputs.", "cve": "CVE-2021-29616", "id": "pyup.io-55696", "more_info_path": "/vulnerabilities/CVE-2021-29616/55696", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29618: Passing a complex argument to `tf.transpose` at the same time as passing 'conjugate=True' argument results in a crash.", "cve": "CVE-2021-29618", "id": "pyup.io-55737", "more_info_path": "/vulnerabilities/CVE-2021-29618/55737", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update 'curl' to '7.76.0' to handle CVE-2020-8177.", "cve": "CVE-2020-8177", "id": "pyup.io-55704", "more_info_path": "/vulnerabilities/CVE-2020-8177/55704", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29583: The implementation of 'tf.raw_ops.FusedBatchNorm' is vulnerable to a heap buffer overflow. If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers. The implementation(https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that 'scale', 'offset', 'mean' and 'variance' (the last two only when required) all have the same number of elements as the number of channels of 'x'. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary. If the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior.", "cve": "CVE-2021-29583", "id": "pyup.io-55697", "more_info_path": "/vulnerabilities/CVE-2021-29583/55697", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB read in 'tf.raw_ops.Dequantize'. See CVE-2021-29582.", "cve": "CVE-2021-29582", "id": "pyup.io-55689", "more_info_path": "/vulnerabilities/CVE-2021-29582/55689", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'FractionalAvgPoolGrad'. See CVE-2021-29578.", "cve": "CVE-2021-29578", "id": "pyup.io-55701", "more_info_path": "/vulnerabilities/CVE-2021-29578/55701", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'EditDistance'. See CVE-2021-29564.", "cve": "CVE-2021-29564", "id": "pyup.io-55714", "more_info_path": "/vulnerabilities/CVE-2021-29564/55714", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'DenseCountSparseOutput'. See CVE-2021-29554.", "cve": "CVE-2021-29554", "id": "pyup.io-55707", "more_info_path": "/vulnerabilities/CVE-2021-29554/55707", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger undefined behavior by binding to null pointer in 'tf.raw_ops.ParameterizedTruncatedNormal'. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/3f6fe4dfef6f57e768260b48166c27d148f3015f/tensorflow/core/kernels/parameterized_truncated_normal_op.cc#L630) does not validate input arguments before accessing the first element of 'shape'. If 'shape' argument is empty, then 'shape_tensor.flat()' is an empty array. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.", "cve": "CVE-2021-29568", "id": "pyup.io-55720", "more_info_path": "/vulnerabilities/CVE-2021-29568/55720", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu versions 2.5.0, 2.4.2, 2.3.3, 2.2.3 and 2.1.4 updates its dependency \"curl\" to a secure version (7.76.0).", "cve": "CVE-2020-8285", "id": "pyup.io-55724", "more_info_path": "/vulnerabilities/CVE-2020-8285/55724", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'SparseFillEmptyRows'. See CVE-2021-29565.", "cve": "CVE-2021-29565", "id": "pyup.io-55695", "more_info_path": "/vulnerabilities/CVE-2021-29565/55695", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'MaxPoolGrad'. See CVE-2021-29579.", "cve": "CVE-2021-29579", "id": "pyup.io-55710", "more_info_path": "/vulnerabilities/CVE-2021-29579/55710", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'BatchToSpaceNd'. See CVE-2021-29593.", "cve": "CVE-2021-29593", "id": "pyup.io-55706", "more_info_path": "/vulnerabilities/CVE-2021-29593/55706", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'SpaceToBatchNd'. See CVE-2021-29597.", "cve": "CVE-2021-29597", "id": "pyup.io-55692", "more_info_path": "/vulnerabilities/CVE-2021-29597/55692", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 updates 'curl' to '7.76.0' to handle CVE-2020-8286: curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response.", "cve": "CVE-2020-8286", "id": "pyup.io-55705", "more_info_path": "/vulnerabilities/CVE-2020-8286/55705", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update its dependency \"curl\" to v7.76.0 to include security fixes.", "cve": "CVE-2020-8231", "id": "pyup.io-55703", "more_info_path": "/vulnerabilities/CVE-2020-8231/55703", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29571: The implementation of 'tf.raw_ops.MaxPoolGradWithArgmax' can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation (https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of 'boxes' input is 4, as required by the op (https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption. If the last dimension in 'boxes' is less than 4, accesses similar to 'tboxes(b, bb, 3)' will access data outside of bounds. Further during code execution there are also writes to these indices.", "cve": "CVE-2021-29571", "id": "pyup.io-55721", "more_info_path": "/vulnerabilities/CVE-2021-29571/55721", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'OneHot'. See CVE-2021-29600.", "cve": "CVE-2021-29600", "id": "pyup.io-55713", "more_info_path": "/vulnerabilities/CVE-2021-29600/55713", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29587: TensorFlow is an end-to-end open source platform for machine learning. The `Prepare` step of the `SpaceToDepth` TFLite operator does not check for 0 before division (https://github.com/tensorflow/tensorflow/blob/5f7975d09eac0f10ed8a17dbb6f5964977725adc/tensorflow/lite/kernels/space_to_depth.cc#L63-L67). An attacker can craft a model such that `params->block_size` would be zero.", "cve": "CVE-2021-29587", "id": "pyup.io-55719", "more_info_path": "/vulnerabilities/CVE-2021-29587/55719", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail due to integer overflow. See CVE-2021-29584.", "cve": "CVE-2021-29584", "id": "pyup.io-55686", "more_info_path": "/vulnerabilities/CVE-2021-29584/55686", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap out of bounds read in 'RequantizationRange'. See CVE-2021-29569.", "cve": "CVE-2021-29569", "id": "pyup.io-55722", "more_info_path": "/vulnerabilities/CVE-2021-29569/55722", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.5.0, 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29572: The implementation of `tf.raw_ops.SdcaOptimizer` triggers undefined behavior due to dereferencing a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/60a45c8b6192a4699f2e2709a2645a751d435cc3/tensorflow/core/kernels/sdca_internal.cc) does not validate that the user supplied arguments satisfy all constraints expected by the op(https://www.tensorflow.org/api_docs/python/tf/raw_ops/SdcaOptimizer).", "cve": "CVE-2021-29572", "id": "pyup.io-55723", "more_info_path": "/vulnerabilities/CVE-2021-29572/55723", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29547: An attacker can cause a segfault and denial of service via accessing data outside of bounds in 'tf.raw_ops.QuantizedBatchNormWithGlobalNormalization'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc#L176-L189) assumes the inputs are not empty. If any of these inputs is empty, '.flat()' is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds.", "cve": "CVE-2021-29547", "id": "pyup.io-55715", "more_info_path": "/vulnerabilities/CVE-2021-29547/55715", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29546: TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger an integer division by zero undefined behavior in `tf.raw_ops.QuantizedBiasAdd`. This is because the implementation of the Eigen kernel (https://github.com/tensorflow/tensorflow/blob/61bca8bd5ba8a68b2d97435ddfafcdf2b85672cd/tensorflow/core/kernels/quantization_utils.h#L812-L849) does a division by the number of elements of the smaller input (based on shape) without checking that this is not zero.", "cve": "CVE-2021-29546", "id": "pyup.io-55736", "more_info_path": "/vulnerabilities/CVE-2021-29546/55736", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'QuantizedMul'. See CVE-2021-29528.", "cve": "CVE-2021-29528", "id": "pyup.io-55731", "more_info_path": "/vulnerabilities/CVE-2021-29528/55731", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB in 'QuantizeAndDequantizeV3'. See CVE-2021-29553.", "cve": "CVE-2021-29553", "id": "pyup.io-55732", "more_info_path": "/vulnerabilities/CVE-2021-29553/55732", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a stack overflow due to looping TFLite subgraph. See CVE-2021-29591.", "cve": "CVE-2021-29591", "id": "pyup.io-55687", "more_info_path": "/vulnerabilities/CVE-2021-29591/55687", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB read in TFLite's implementation of 'Minimum' or 'Maximum'. See CVE-2021-29590.", "cve": "CVE-2021-29590", "id": "pyup.io-55728", "more_info_path": "/vulnerabilities/CVE-2021-29590/55728", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37688: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer. The Tensorflow team has patched the issue in GitHub commit 15691e456c7dc9bd6be203b09765b063bf4a380c.", "cve": "CVE-2021-37688", "id": "pyup.io-55683", "more_info_path": "/vulnerabilities/CVE-2021-37688/55683", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37645: In affected versions the implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit 96f364a1ca3009f98980021c4b32be5fdcca33a1.", "cve": "CVE-2021-37645", "id": "pyup.io-55684", "more_info_path": "/vulnerabilities/CVE-2021-37645/55684", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37691: In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). The Tensorflow team has patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9.", "cve": "CVE-2021-37691", "id": "pyup.io-55685", "more_info_path": "/vulnerabilities/CVE-2021-37691/55685", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu versions 2.5.1 and 2.6.0 include a fix for CVE-2021-37692:\nIn affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, \"C.TF_TString_Dealloc\" is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until \"NewTensor\" returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. The Tensorflow team has patched the issue in GitHub commit:\nhttps://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22\nhttps://github.com/tensorflow/tensorflow/pull/50508\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cmgw-8vpc-rc59", "cve": "CVE-2021-37692", "id": "pyup.io-55681", "more_info_path": "/vulnerabilities/CVE-2021-37692/55681", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu 2.5.1 and 2.6.0 include a fix for CVE-2021-37640: In affected versions the implementation of 'tf.raw_ops.SparseReshape' can be made to trigger an integral division by 0 exception. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements. The reshape functor (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0. The Tensorflow team has patched the issue in GitHub commit 4923de56ec94fff7770df259ab7f2288a74feb41.", "cve": "CVE-2021-37640", "id": "pyup.io-55682", "more_info_path": "/vulnerabilities/CVE-2021-37640/55682", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-cpu versions 2.3.4, 2.4.3, 2.5.1, and 2.6.0 update its dependency \"curl\" to include a fix for CVE-2021-22898", "cve": "CVE-2021-22898", "id": "pyup.io-55680", "more_info_path": "/vulnerabilities/CVE-2021-22898/55680", "specs": [ ">=2.6.0a1,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0a1,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37661: In affected versions an attacker can cause a denial of service in 'boosted_trees_create_quantile_stream_resource' by using negative arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that 'num_streams' only contains non-negative numbers. In turn, this results in using this value to allocate memory (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40). However, 'reserve' receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library. The Tensorflow team has patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992.", "cve": "CVE-2021-37661", "id": "pyup.io-55673", "more_info_path": "/vulnerabilities/CVE-2021-37661/55673", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37676: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.SparseFillEmptyRows'. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors. The Tensorflow team has patched the issue in GitHub commit 578e634b4f1c1c684d4b4294f9e5281b2133b3ed.", "cve": "CVE-2021-37676", "id": "pyup.io-55677", "more_info_path": "/vulnerabilities/CVE-2021-37676/55677", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37665:\nIn affected versions, due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the \"input\" tensor. A similar issue occurs in \"MklRequantizePerChannelOp\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments. The Tensorflow team has patched the issue in GitHub commit 9e62869465573cb2d9b5053f1fa02a81fce21d69 and in the Github commit 203214568f5bc237603dbab6e1fd389f1572f5c9.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v82p-hv3v-p6qp\nhttps://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9\nhttps://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69", "cve": "CVE-2021-37665", "id": "pyup.io-55674", "more_info_path": "/vulnerabilities/CVE-2021-37665/55674", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37668:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.UnravelIndex\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by \"dims\" is not empty. Hence, if one element of \"dims\" is 0, the implementation does a division by 0. The Tensorflow team has patched the issue in GitHub commit a776040a5e7ebf76eeb7eb923bf1ae417dd4d233.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2wmv-37vq-52g5\nhttps://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233", "cve": "CVE-2021-37668", "id": "pyup.io-55670", "more_info_path": "/vulnerabilities/CVE-2021-37668/55670", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37663:\nIn affected versions, due to incomplete validation in \"tf.raw_ops.QuantizeV2\", an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that \"min_range\" and \"max_range\" both have the same non-zero number of elements. If \"axis\" is provided (i.e., not \"-1\"), then validation should check that it is a value in range for the rank of \"input\" tensor and then the lengths of \"min_range\" and \"max_range\" inputs match the \"axis\" dimension of the \"input\" tensor. The Tensorflow team has patched the issue in GitHub commit 6da6620efad397c85493b8f8667b821403516708. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g25h-jr74-qp5j\nhttps://github.com/tensorflow/tensorflow/commit/6da6620efad397c85493b8f8667b821403516708", "cve": "CVE-2021-37663", "id": "pyup.io-55671", "more_info_path": "/vulnerabilities/CVE-2021-37663/55671", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37675: In affected versions most implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations. The Tensorflow team has patched the issue in GitHub commit 8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4.", "cve": "CVE-2021-37675", "id": "pyup.io-55675", "more_info_path": "/vulnerabilities/CVE-2021-37675/55675", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37657: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. The Tensorflow team has checked that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit f2a673bd34f0d64b8e40a551ac78989d16daad09.", "cve": "CVE-2021-37657", "id": "pyup.io-55669", "more_info_path": "/vulnerabilities/CVE-2021-37657/55669", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37687: In affected versions TFLite's 'GatherNd' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation. Hence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in 'indices'. Similar issue exists in 'Gather' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc). The Tensorflow team has patched the issue in GitHub commits bb6a0383ed553c286f87ca88c207f6774d5c4a8f and eb921122119a6b6e470ee98b89e65d721663179d.", "cve": "CVE-2021-37687", "id": "pyup.io-55676", "more_info_path": "/vulnerabilities/CVE-2021-37687/55676", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37685: In affected versions TFLite's 'expand_dims.cc' (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data. If 'axis' is a large negative value (e.g., '-100000'), then after the first 'if' it would still be negative. The check following the 'if' statement will pass and the 'for' loop would read one element before the start of 'input_dims.data' (when 'i = 0'). The Tensorflow team has patched the issue in GitHub commit d94ffe08a65400f898241c0374e9edc6fa8ed257.", "cve": "CVE-2021-37685", "id": "pyup.io-55672", "more_info_path": "/vulnerabilities/CVE-2021-37685/55672", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37660: In affected versions an attacker can cause a floating point exception by calling inplace operations with crafted arguments that would result in a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/inplace_ops.cc#L283) has a logic error: it should skip processing if 'x' and 'v' are empty but the code uses '||' instead of '&&'. The Tensorflow team has patched the issue in GitHub commit e86605c0a336c088b638da02135ea6f9f6753618.", "cve": "CVE-2021-37660", "id": "pyup.io-55679", "more_info_path": "/vulnerabilities/CVE-2021-37660/55679", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37653: In affected versions an attacker can trigger a crash via a floating point exception in 'tf.raw_ops.ResourceGather'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, 'batch_size', and then divides by it without checking that this value is not 0. The Tensorflow team has patched the issue in GitHub commit ac117ee8a8ea57b73d34665cdf00ef3303bc0b11.", "cve": "CVE-2021-37653", "id": "pyup.io-55678", "more_info_path": "/vulnerabilities/CVE-2021-37653/55678", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37643: If a user does not provide a valid padding value to 'tf.raw_ops.MatrixDiagPartOp', then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from. The Tensorflow team has patched the issue in GitHub commit 482da92095c4d48f8784b1f00dda4f81c28d2988.", "cve": "CVE-2021-37643", "id": "pyup.io-55663", "more_info_path": "/vulnerabilities/CVE-2021-37643/55663", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37681: In affected versions the implementation of SVDF in TFLite is vulnerable to a null pointer error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313). The 'GetVariableInput' function (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but 'GetTensorData' assumes that the argument is always a valid tensor. Furthermore, because 'GetVariableInput' calls 'GetMutableInput' (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return 'nullptr', the 'tensor->is_variable' expression can also trigger a null pointer exception. The Tensorflow team has patched the issue in GitHub commit 5b048e87e4e55990dae6b547add4dae59f4e1c76.", "cve": "CVE-2021-37681", "id": "pyup.io-55665", "more_info_path": "/vulnerabilities/CVE-2021-37681/55665", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37666: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToVariant'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty. The Tensorflow team has patched the issue in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612.", "cve": "CVE-2021-37666", "id": "pyup.io-55668", "more_info_path": "/vulnerabilities/CVE-2021-37666/55668", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37662: In affected versions an attacker can generate undefined behavior via a reference binding to nullptr in 'BoostedTreesCalculateBestGainsPerFeature' and similar attack can occur in 'BoostedTreesCalculateBestFeatureSplitV2'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values. The Tensorflow team has patched the issue in GitHub commit 9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad and in commit 429f009d2b2c09028647dd4bb7b3f6f414bbaad7.", "cve": "CVE-2021-37662", "id": "pyup.io-55662", "more_info_path": "/vulnerabilities/CVE-2021-37662/55662", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37644: In affected versions providing a negative element to 'num_elements' list argument of 'tf.raw_ops.TensorListReserve' causes the runtime to abort the process due to reallocating a 'std::vector' to have a negative number of elements. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls 'std::vector.resize()' with the new size controlled by input given by the user, without checking that this input is valid. The Tensorflow team has patched the issue in GitHub commit 8a6e874437670045e6c7dc6154c7412b4a2135e2.", "cve": "CVE-2021-37644", "id": "pyup.io-55666", "more_info_path": "/vulnerabilities/CVE-2021-37644/55666", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37641: In affected versions if the arguments to 'tf.raw_ops.RaggedGather' don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by 'params_nested_splits' is not an empty list of tensors. The Tensorflow team has patched the issue in GitHub commit a2b743f6017d7b97af1fe49087ae15f0ac634373.", "cve": "CVE-2021-37641", "id": "pyup.io-55664", "more_info_path": "/vulnerabilities/CVE-2021-37641/55664", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37684: In affected versions the implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695 (https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).", "cve": "CVE-2021-37684", "id": "pyup.io-55661", "more_info_path": "/vulnerabilities/CVE-2021-37684/55661", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37646: In affected versions the implementation of 'tf.raw_ops.StringNGrams' is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls 'reserve' on a 'tstring' with a value that sometimes can be negative if user supplies negative 'ngram_widths'. The 'reserve' method calls 'TF_TString_Reserve' which has an 'unsigned long' argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5.", "cve": "CVE-2021-37646", "id": "pyup.io-55667", "more_info_path": "/vulnerabilities/CVE-2021-37646/55667", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37682:\nIn affected versions all TFLite operations that use quantization can be made to use unitialized values. (For example, https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200). The issue stems from the fact that \"quantization.params\" is only valid if \"quantization.type\" is different that \"kTfLiteNoQuantization\". However, these checks are missing in large parts of the code. The Tensorflow team has patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4c4g-crqm-xrxw\nhttps://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5\nhttps://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887\nhttps://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538", "cve": "CVE-2021-37682", "id": "pyup.io-55659", "more_info_path": "/vulnerabilities/CVE-2021-37682/55659", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37690:\nIn affected versions when running shape functions, some functions (such as 'MutableHashTableShape') produce extra output information in the form of a 'ShapeAndType' struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault. 'ShapeRefiner' is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but the Tensorflow team was not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types. The Tensorflow team has patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3hxh-8cp2-g4hg\nhttps://github.com/tensorflow/tensorflow/commit/ee119d4a498979525046fba1c3dd3f13a039fbb1", "cve": "CVE-2021-37690", "id": "pyup.io-55660", "more_info_path": "/vulnerabilities/CVE-2021-37690/55660", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22901", "id": "pyup.io-55650", "more_info_path": "/vulnerabilities/CVE-2021-22901/55650", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. In affected versions the shape inference code for 'tf.raw_ops.Dequantize' has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments. The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses 'axis' to select between two different values for 'minmax_rank' which is then used to retrieve tensor dimensions. However, code assumes that 'axis' can be either '-1' or a value greater than '-1', with no validation for the other values. We have patched the issue in GitHub commit da857cfa0fde8f79ad0afdbc94e88b5d4bbec764. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.", "cve": "CVE-2021-37677", "id": "pyup.io-55657", "more_info_path": "/vulnerabilities/CVE-2021-37677/55657", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22897", "id": "pyup.io-55651", "more_info_path": "/vulnerabilities/CVE-2021-22897/55651", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a denial of service via a segmentation fault in 'tf.raw_ops.MaxPoolGrad' caused by missing validation. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the 'orig_input' and 'orig_output' tensors. The fixes for CVE-2021-29579 were incomplete. We have patched the issue in GitHub commit 136b51f10903e044308cf77117c0ed9871350475. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.", "cve": "CVE-2021-37674", "id": "pyup.io-55655", "more_info_path": "/vulnerabilities/CVE-2021-37674/55655", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22876", "id": "pyup.io-55652", "more_info_path": "/vulnerabilities/CVE-2021-22876/55652", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37670:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.UpperBound\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of \"sorted_input\" argument. A similar issue occurs in \"tf.raw_ops.LowerBound\". The Tensorflow team has patched the issue in GitHub commit 42459e4273c2e47a3232cc16c4f4fff3b3a35c38.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9697-98pf-4rw7\nhttps://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38", "cve": "CVE-2021-37670", "id": "pyup.io-55648", "more_info_path": "/vulnerabilities/CVE-2021-37670/55648", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37672:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.SdcaOptimizerV2\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of \"example_labels\" is the same as the number of examples. The Tensorflow team has patched the issue in GitHub commit a4e138660270e7599793fa438cd7b2fc2ce215a6.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hj3-vjjf-f5m7\nhttps://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6", "cve": "CVE-2021-37672", "id": "pyup.io-55647", "more_info_path": "/vulnerabilities/CVE-2021-37672/55647", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37673:\nIn affected versions, an attacker can trigger a denial of service via a \"CHECK\"-fail in \"tf.raw_ops.MapStage\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the \"key\" input is a valid non-empty tensor. The Tensorflow team has patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-278g-rq84-9hmg\nhttps://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d", "cve": "CVE-2021-37673", "id": "pyup.io-55653", "more_info_path": "/vulnerabilities/CVE-2021-37673/55653", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37650: In affected versions the implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types. The Tensorflow team has patched the issue in GitHub commit e0b6e58c328059829c3eb968136f17aa72b6c876.", "cve": "CVE-2021-37650", "id": "pyup.io-55654", "more_info_path": "/vulnerabilities/CVE-2021-37650/55654", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37669:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.NonMaxSuppressionV5\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a \"std::vector\". However, as \"std::vector::resize\" takes the size argument as a \"size_t\" and \"output_size\" is an \"int\", there is an implicit conversion to unsigned. If the attacker supplies a negative value, this conversion results in a crash. A similar issue occurs in \"CombinedNonMaxSuppression\". The Tensorflow team has patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c\nhttps://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d\nhttps://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58", "cve": "CVE-2021-37669", "id": "pyup.io-55656", "more_info_path": "/vulnerabilities/CVE-2021-37669/55656", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37655: TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to 'tf.raw_ops.ResourceScatterUpdate'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of 'indices' and 'updates': instead of checking that the shape of 'indices' is a prefix of the shape of 'updates' (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. The Tensorflow team has patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f.", "cve": "CVE-2021-37655", "id": "pyup.io-55646", "more_info_path": "/vulnerabilities/CVE-2021-37655/55646", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37679:\nIn affected versions it is possible to nest a \"tf.map_fn\" within another \"tf.map_fn\" call. However, if the input tensor is a \"RaggedTensor\" and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap. The \"t\" and \"z\" outputs should be identical, however this is not the case. The last row of \"t\" contains data from the heap which can be used to leak other memory information. The bug lies in the conversion from a \"Variant\" tensor to a \"RaggedTensor\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions. The same implementation can result in data loss, if input tensor is tweaked. The Tensorflow team has patched the issue in GitHub commit 4e2565483d0ffcadc719bd44893fb7f609bb5f12.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g8wg-cjwc-xhhp\nhttps://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12", "cve": "CVE-2021-37679", "id": "pyup.io-55649", "more_info_path": "/vulnerabilities/CVE-2021-37679/55649", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-cpu version 2.3.4, 2.4.3, 2.5.1, 2.6.0 and 2.7.0 include a fix for CVE-2021-37678:\nIn affected versions, TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The implementation(https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses \"yaml.unsafe_load\" which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, the Tensorflow team has removed it for now. The Tensorflow team has patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r\nhttps://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012", "cve": "CVE-2021-37678", "id": "pyup.io-55658", "more_info_path": "/vulnerabilities/CVE-2021-37678/55658", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.7.0rc0,<2.7.0" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.7.0rc0,<2.7.0" }, { "advisory": "Tensorflow-cpu version 2.6.1 includes a fix for CVE-2021-41211: In affected versions, the shape inference code for 'QuantizeV2' can trigger a read outside of bounds of heap allocated array. This occurs whenever 'axis' is a negative value less than '-1'. In this case, we are accessing data before the start of a heap buffer. The code allows 'axis' to be an optional argument ('s' would contain an 'error::NOT_FOUND' error code). Otherwise, it assumes that 'axis' is a valid index into the dimensions of the 'input' tensor. If 'axis' is less than '-1' then this results in a heap OOB read. The fix is included in TensorFlow 2.7.0. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvgx-3v3q-m36c\nhttps://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244", "cve": "CVE-2021-41211", "id": "pyup.io-55645", "more_info_path": "/vulnerabilities/CVE-2021-41211/55645", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu version 2.6.1 includes a fix for CVE-2021-41220: In affected versions, the async implementation of 'CollectiveReduceV2' suffers from a memory leak and a use after free. This occurs due to the asynchronous computation and the fact that objects that have been 'std::move()'d are still accessed. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gpfh-jvf9-7wg5\nhttps://github.com/tensorflow/tensorflow/commit/ca38dab9d3ee66c5de06f11af9a4b1200da5ef75", "cve": "CVE-2021-41220", "id": "pyup.io-55644", "more_info_path": "/vulnerabilities/CVE-2021-41220/55644", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-cpu versions 2.7.1 and 2.8.0 include a fix for CVE-2022-23590: A 'GraphDef' from a TensorFlow 'SavedModel' can be maliciously altered to cause a TensorFlow process to crash due to encountering a 'StatusOr' value that is an error and forcibly extracting the value from it.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pqrv-8r2f-7278", "cve": "CVE-2022-23590", "id": "pyup.io-55553", "more_info_path": "/vulnerabilities/CVE-2022-23590/55553", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu is an Open Source Machine Learning Framework. The TFG dialect of TensorFlow (MLIR) makes several assumptions about the incoming `GraphDef` before converting it to the MLIR-based dialect. If an attacker changes the `SavedModel` format on disk to invalidate these assumptions and the `GraphDef` is then converted to MLIR-based IR then they can cause a crash in the Python interpreter. Under certain scenarios, heap OOB read/writes are possible. These issues have been discovered via fuzzing and it is possible that more weaknesses exist. We will patch them as they are discovered.", "cve": "CVE-2022-23594", "id": "pyup.io-55554", "more_info_path": "/vulnerabilities/CVE-2022-23594/55554", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Certain versions of TensorFlow-CPU contain a vulnerability that leads to a Denial of Service (DoS) through a CHECK-failure (assertion failure) triggered by an overflow in the tensor's element count. This flaw specifically affects the implementation of depthwise operations, where a particular configuration involving the size of elements can cause the system to halt. The vulnerability can be exemplified by an overflow caused when specifying an excessively large value for the tensor's element count in operations like `DepthwiseConv2dNativeBackpropFilter`. This issue is identified as stemming from an incomplete resolution of CVE-2021-41197.", "cve": "PVE-2024-99849", "id": "pyup.io-65571", "more_info_path": "/vulnerabilities/PVE-2024-99849/65571", "specs": [ ">=2.8.0,<2.8.1", ">=2.7.0,<2.7.2", ">=0,<2.6.4" ], "v": ">=2.8.0,<2.8.1,>=2.7.0,<2.7.2,>=0,<2.6.4" }, { "advisory": "Tensorflow-cpu version 2.8.0 includes a fix for CVE-2022-23592: TensorFlow's type inference can cause a heap out of bounds read as the bounds checking is done in a 'DCHECK' (which is a no-op during production). An attacker can control the 'input_idx' variable such that 'ix' would be larger than the number of values in 'node_t.args'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vq36-27g6-p492", "cve": "CVE-2022-23592", "id": "pyup.io-55551", "more_info_path": "/vulnerabilities/CVE-2022-23592/55551", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-cpu 2.8.0 includes a fix for CVE-2022-23593: The 'simplifyBroadcast' function in the MLIR-TFRT infrastructure in TensorFlow is vulnerable to a segfault (hence, denial of service), if called with scalar shapes. If all shapes are scalar, then 'maxRank' is 0, so we build an empty 'SmallVector'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gwcx-jrx4-92w2", "cve": "CVE-2022-23593", "id": "pyup.io-55552", "more_info_path": "/vulnerabilities/CVE-2022-23593/55552", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "TensorFlow is an open source platform for machine learning. In version 2.8.0, the 'TensorKey' hash function used total estimated 'AllocatedBytes()', which (a) is an estimate per tensor, and (b) is a very poor hash function for constants (e.g. 'int32_t'). It also tried to access individual tensor bytes through 'tensor.data()' of size 'AllocatedBytes()'. This led to ASAN failures because the 'AllocatedBytes()' is an estimate of total bytes allocated by a tensor, including any pointed-to constructs (e.g. strings), and does not refer to contiguous bytes in the '.data()' buffer. The discoverers could not use this byte vector anyway because types such as 'tstring' include pointers, whereas they needed to hash the string values themselves. This issue is patched in Tensorflow versions 2.9.0 and 2.8.1.", "cve": "CVE-2022-29210", "id": "pyup.io-55515", "more_info_path": "/vulnerabilities/CVE-2022-29210/55515", "specs": [ ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": ">=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" } ], "tensorflow-cpu-aws": [ { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25801: Prior to versions 2.12.0 and 2.11.1, 'nn_ops.fractional_avg_pool_v2' and 'nn_ops.fractional_max_pool_v2' require the first and fourth elements of their parameter 'pooling_ratio' to be equal to 1.0, as pooling on batch and channel dimensions is not supported.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f49c-87jh-g47q", "cve": "CVE-2023-25801", "id": "pyup.io-58524", "more_info_path": "/vulnerabilities/CVE-2023-25801/58524", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25676: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.ParallelConcat' segfaults with a nullptr dereference when given a parameter 'shape' with rank that is not greater than zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6wfh-89q8-44jq", "cve": "CVE-2023-25676", "id": "pyup.io-58519", "more_info_path": "/vulnerabilities/CVE-2023-25676/58519", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25675: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.Bincount' segfaults when given a parameter 'weights' that is neither the same shape as parameter 'arr' nor a length-0 tensor.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7x4v-9gxg-9hwj", "cve": "CVE-2023-25675", "id": "pyup.io-58525", "more_info_path": "/vulnerabilities/CVE-2023-25675/58525", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25674: Versions prior to 2.12.0 and 2.11.1 have a null pointer error in RandomShuffle with XLA enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf97-q72m-7579", "cve": "CVE-2023-25674", "id": "pyup.io-58522", "more_info_path": "/vulnerabilities/CVE-2023-25674/58522", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25673: Versions prior to 2.12.0 and 2.11.1 have a Floating Point Exception in TensorListSplit with XLA. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25673", "id": "pyup.io-58517", "more_info_path": "/vulnerabilities/CVE-2023-25673/58517", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25672: The function 'tf.raw_ops.LookupTableImportV2' cannot handle scalars in the 'values' parameter and gives an NPE. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25672", "id": "pyup.io-58518", "more_info_path": "/vulnerabilities/CVE-2023-25672/58518", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25671: There is out-of-bounds access due to mismatched integer type sizes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j5w9-hmfh-4cr6", "cve": "CVE-2023-25671", "id": "pyup.io-58528", "more_info_path": "/vulnerabilities/CVE-2023-25671/58528", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25670: Versions prior to 2.12.0 and 2.11.1 have a null point error in QuantizedMatMulWithBiasAndDequantize with MKL enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rq-hwc3-x77w", "cve": "CVE-2023-25670", "id": "pyup.io-58529", "more_info_path": "/vulnerabilities/CVE-2023-25670/58529", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25669: Prior to versions 2.12.0 and 2.11.1, if the stride and window size are not positive for 'tf.raw_ops.AvgPoolGrad', it can give a floating point exception.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rcf8-g8jv-vg6p", "cve": "CVE-2023-25669", "id": "pyup.io-58530", "more_info_path": "/vulnerabilities/CVE-2023-25669/58530", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25666: Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2", "cve": "CVE-2023-25666", "id": "pyup.io-58520", "more_info_path": "/vulnerabilities/CVE-2023-25666/58520", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25660: Prior to versions 2.12.0 and 2.11.1, when the parameter 'summarize' of 'tf.raw_ops.Print' is zero, the new method 'SummarizeArray' will reference to a nullptr, leading to a seg fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qjqc-vqcf-5qvj", "cve": "CVE-2023-25660", "id": "pyup.io-58535", "more_info_path": "/vulnerabilities/CVE-2023-25660/58535", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25661: In versions prior to 2.11.1 a malicious invalid input crashes a tensorflow model (Check Failed) and can be used to trigger a denial of service attack. A proof of concept can be constructed with the 'Convolution3DTranspose' function. This Convolution3DTranspose layer is a very common API in modern neural networks. The ML models containing such vulnerable components could be deployed in ML applications or as cloud services. This failure could be potentially used to trigger a denial of service attack on ML cloud services. An attacker must have privilege to provide input to a 'Convolution3DTranspose' call.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fxgc-95xx-grvq", "cve": "CVE-2023-25661", "id": "pyup.io-58523", "more_info_path": "/vulnerabilities/CVE-2023-25661/58523", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25668: Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gw97-ff7c-9v96", "cve": "CVE-2023-25668", "id": "pyup.io-58531", "more_info_path": "/vulnerabilities/CVE-2023-25668/58531", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25659: Prior to versions 2.12.0 and 2.11.1, if the parameter 'indices' for 'DynamicStitch' does not match the shape of the parameter 'data', it can trigger an stack OOB read.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-93vr-9q9m-pj8p", "cve": "CVE-2023-25659", "id": "pyup.io-58536", "more_info_path": "/vulnerabilities/CVE-2023-25659/58536", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25665: Prior to versions 2.12.0 and 2.11.1, when 'SparseSparseMaximum' is given invalid sparse tensors as inputs, it can give a null pointer error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-558h-mq8x-7q9g", "cve": "CVE-2023-25665", "id": "pyup.io-58526", "more_info_path": "/vulnerabilities/CVE-2023-25665/58526", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25667: Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when '2^31 <= num_frames * height * width * channels < 2^32', for example Full HD screencast of at least 346 frames.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqm2-gh8w-gr68", "cve": "CVE-2023-25667", "id": "pyup.io-58521", "more_info_path": "/vulnerabilities/CVE-2023-25667/58521", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25662: Versions prior to 2.12.0 and 2.11.1 are vulnerable to integer overflow in EditDistance.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7jvm-xxmr-v5cw", "cve": "CVE-2023-25662", "id": "pyup.io-58534", "more_info_path": "/vulnerabilities/CVE-2023-25662/58534", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-27579: Constructing a tflite model with a paramater 'filter_input_channel' of less than 1 gives a FPE.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5w96-866f-6rm8", "cve": "CVE-2023-27579", "id": "pyup.io-58527", "more_info_path": "/vulnerabilities/CVE-2023-27579/58527", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25663: Prior to versions 2.12.0 and 2.11.1, when 'ctx->step_containter()' is a null ptr, the Lookup function will be executed with a null pointer.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-64jg-wjww-7c5w", "cve": "CVE-2023-25663", "id": "pyup.io-58533", "more_info_path": "/vulnerabilities/CVE-2023-25663/58533", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25664: Prior to versions 2.12.0 and 2.11.1, there is a heap buffer overflow in TAvgPoolGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hg6-5c2q-7rcr", "cve": "CVE-2023-25664", "id": "pyup.io-58532", "more_info_path": "/vulnerabilities/CVE-2023-25664/58532", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-cpu-aws 2.11.1 and 2.12.0 include a fix for CVE-2023-25658: Prior to versions 2.12.0 and 2.11.1, an out of bounds read is in GRUBlockCellGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-68v3-g9cm-rmm6", "cve": "CVE-2023-25658", "id": "pyup.io-58537", "more_info_path": "/vulnerabilities/CVE-2023-25658/58537", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Integer Overflow. array_ops.upper_bound' causes a segfault when not given a rank 2 tensor. The flaw was fixed in May 30, 2023, but the CVE was published in July 30, 2024. It was noticed unpublished by the Safety CLI Cyber Security team.", "cve": "CVE-2023-33976", "id": "pyup.io-72432", "more_info_path": "/vulnerabilities/CVE-2023-33976/72432", "specs": [ "<2.12.1", ">=2.13.0rc0,<2.13.0" ], "v": "<2.12.1,>=2.13.0rc0,<2.13.0" }, { "advisory": "Tensorflow-cpu-aws updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38546.", "cve": "CVE-2023-38546", "id": "pyup.io-72942", "more_info_path": "/vulnerabilities/CVE-2023-38546/72942", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "Tensorflow-cpu-aws 2.14.1 updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38545.", "cve": "CVE-2023-38545", "id": "pyup.io-72941", "more_info_path": "/vulnerabilities/CVE-2023-38545/72941", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35959: 'CHECK' failures in 'AvgPool3DGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wxjj-cgcx-r3vq", "cve": "CVE-2022-35959", "id": "pyup.io-58582", "more_info_path": "/vulnerabilities/CVE-2022-35959/58582", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36019: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannel'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9j4v-pp28-mxv7", "cve": "CVE-2022-36019", "id": "pyup.io-58606", "more_info_path": "/vulnerabilities/CVE-2022-36019/58606", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35941: 'CHECK' failure in 'AvgPoolOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mgmh-g2v6-mqw5", "cve": "CVE-2022-35941", "id": "pyup.io-58602", "more_info_path": "/vulnerabilities/CVE-2022-35941/58602", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35998: 'CHECK' fail in 'EmptyTensorList'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhw4-wwr7-gjc5", "cve": "CVE-2022-35998", "id": "pyup.io-58585", "more_info_path": "/vulnerabilities/CVE-2022-35998/58585", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35999: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-37jf-mjv6-xfqw", "cve": "CVE-2022-35999", "id": "pyup.io-58614", "more_info_path": "/vulnerabilities/CVE-2022-35999/58614", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36026: 'CHECK' fail in 'QuantizeAndDequantizeV3'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9cr2-8pwr-fhfq", "cve": "CVE-2022-36026", "id": "pyup.io-58594", "more_info_path": "/vulnerabilities/CVE-2022-36026/58594", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35987: 'CHECK' fail in 'DenseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w62h-8xjm-fv49", "cve": "CVE-2022-35987", "id": "pyup.io-58593", "more_info_path": "/vulnerabilities/CVE-2022-35987/58593", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35996: Floating point exception in 'Conv2D'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q5jv-m6qw-5g37", "cve": "CVE-2022-35996", "id": "pyup.io-58580", "more_info_path": "/vulnerabilities/CVE-2022-35996/58580", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35982: Segfault in 'SparseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-397c-5g2j-qxpv", "cve": "CVE-2022-35982", "id": "pyup.io-58598", "more_info_path": "/vulnerabilities/CVE-2022-35982/58598", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36011: Null dereference on MLIR on empty function attributes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fv43-93gv-vm8f", "cve": "CVE-2022-36011", "id": "pyup.io-58596", "more_info_path": "/vulnerabilities/CVE-2022-36011/58596", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36027: Segfault TFLite converter on per-channel quantized transposed convolutions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-79h2-q768-fpxr", "cve": "CVE-2022-36027", "id": "pyup.io-58597", "more_info_path": "/vulnerabilities/CVE-2022-36027/58597", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36017: Segfault in 'Requantize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wqmc-pm8c-2jhc", "cve": "CVE-2022-36017", "id": "pyup.io-58570", "more_info_path": "/vulnerabilities/CVE-2022-36017/58570", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36015: Integer overflow in math ops. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rh87-q4vg-m45j", "cve": "CVE-2022-36015", "id": "pyup.io-58571", "more_info_path": "/vulnerabilities/CVE-2022-36015/58571", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36014: Null-dereference in 'mlir::tfg::TFOp::nameAttr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7j3m-8g3c-9qqq", "cve": "CVE-2022-36014", "id": "pyup.io-58601", "more_info_path": "/vulnerabilities/CVE-2022-36014/58601", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36013: Null-dereference in 'mlir::tfg::GraphDefImporter::ConvertNodeDef'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-828c-5j5q-vrjq", "cve": "CVE-2022-36013", "id": "pyup.io-58586", "more_info_path": "/vulnerabilities/CVE-2022-36013/58586", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35952: 'CHECK' failures in 'UnbatchGradOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h5vq-gw2c-pq47", "cve": "CVE-2022-35952", "id": "pyup.io-58567", "more_info_path": "/vulnerabilities/CVE-2022-35952/58567", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36005: 'CHECK' fail in 'FakeQuantWithMinMaxVarsGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r26c-679w-mrjm", "cve": "CVE-2022-36005", "id": "pyup.io-58620", "more_info_path": "/vulnerabilities/CVE-2022-36005/58620", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35972: Segfault in 'QuantizedBiasAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4pc4-m9mj-v2r9", "cve": "CVE-2022-35972", "id": "pyup.io-58599", "more_info_path": "/vulnerabilities/CVE-2022-35972/58599", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36003: 'CHECK' fail in 'RandomPoissonV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cv2p-32v3-vhwq", "cve": "CVE-2022-36003", "id": "pyup.io-58572", "more_info_path": "/vulnerabilities/CVE-2022-36003/58572", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36002: 'CHECK' fail in 'Unbatch'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mh3m-62v7-68xg", "cve": "CVE-2022-36002", "id": "pyup.io-58576", "more_info_path": "/vulnerabilities/CVE-2022-36002/58576", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36000: 'CHECK' fail in 'Eig'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqxc-pvf8-2w9v", "cve": "CVE-2022-36000", "id": "pyup.io-58588", "more_info_path": "/vulnerabilities/CVE-2022-36000/58588", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35995: 'CHECK' fail in 'AudioSummaryV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9h5-vr8m-x2h4", "cve": "CVE-2022-35995", "id": "pyup.io-58615", "more_info_path": "/vulnerabilities/CVE-2022-35995/58615", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35994: 'CHECK' fail in 'CollectiveGather'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fhfc-2q7x-929f", "cve": "CVE-2022-35994", "id": "pyup.io-58610", "more_info_path": "/vulnerabilities/CVE-2022-35994/58610", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35993: 'CHECK' fail in 'SetSize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wq6q-6m32-9rv9", "cve": "CVE-2022-35993", "id": "pyup.io-58600", "more_info_path": "/vulnerabilities/CVE-2022-35993/58600", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35992: 'CHECK' fail in 'TensorListFromTensor'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9v8w-xmr4-wgxp", "cve": "CVE-2022-35992", "id": "pyup.io-58589", "more_info_path": "/vulnerabilities/CVE-2022-35992/58589", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35968: 'CHECK' fail in 'AvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2475-53vw-vp25", "cve": "CVE-2022-35968", "id": "pyup.io-58608", "more_info_path": "/vulnerabilities/CVE-2022-35968/58608", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35997: 'CHECK' fail in 'tf.sparse.cross'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p7hr-f446-x6qf", "cve": "CVE-2022-35997", "id": "pyup.io-58584", "more_info_path": "/vulnerabilities/CVE-2022-35997/58584", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36012: Assertion fail on MLIR empty edge names.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jvhc-5hhr-w3v5", "cve": "CVE-2022-36012", "id": "pyup.io-58577", "more_info_path": "/vulnerabilities/CVE-2022-36012/58577", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36018: 'CHECK' fail in 'RaggedTensorToVariant'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6cv-4fmf-66xf", "cve": "CVE-2022-36018", "id": "pyup.io-58618", "more_info_path": "/vulnerabilities/CVE-2022-36018/58618", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35967: Segfault in 'QuantizedAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v6h3-348g-6h5x", "cve": "CVE-2022-35967", "id": "pyup.io-58607", "more_info_path": "/vulnerabilities/CVE-2022-35967/58607", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35989: 'CHECK' fail in 'MaxPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j43h-pgmg-5hjq", "cve": "CVE-2022-35989", "id": "pyup.io-58619", "more_info_path": "/vulnerabilities/CVE-2022-35989/58619", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35990: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannelGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h7ff-cfc9-wmmh", "cve": "CVE-2022-35990", "id": "pyup.io-58581", "more_info_path": "/vulnerabilities/CVE-2022-35990/58581", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36016: 'CHECK'-fail in 'tensorflow::full_type::SubstituteFromAttrs'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g468-qj8g-vcjc", "cve": "CVE-2022-36016", "id": "pyup.io-58603", "more_info_path": "/vulnerabilities/CVE-2022-36016/58603", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35986: Segfault in 'RaggedBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wr9v-g9vf-c74v", "cve": "CVE-2022-35986", "id": "pyup.io-58590", "more_info_path": "/vulnerabilities/CVE-2022-35986/58590", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35985: 'CHECK' fail in 'LRNGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9942-r22v-78cp", "cve": "CVE-2022-35985", "id": "pyup.io-58573", "more_info_path": "/vulnerabilities/CVE-2022-35985/58573", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35984: 'CHECK' fail in 'ParameterizedTruncatedNormal'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2xf-8hgm-hpw5", "cve": "CVE-2022-35984", "id": "pyup.io-58579", "more_info_path": "/vulnerabilities/CVE-2022-35984/58579", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35981: 'CHECK' fail in 'FractionalMaxPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vxv8-r8q2-63xw", "cve": "CVE-2022-35981", "id": "pyup.io-58587", "more_info_path": "/vulnerabilities/CVE-2022-35981/58587", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35979: Segfault in 'QuantizedRelu' and 'QuantizedRelu6'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v7vw-577f-vp8x", "cve": "CVE-2022-35979", "id": "pyup.io-58569", "more_info_path": "/vulnerabilities/CVE-2022-35979/58569", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35974: Segfault in 'QuantizeDownAndShrinkRange'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vgvh-2pf4-jr2x", "cve": "CVE-2022-35974", "id": "pyup.io-58591", "more_info_path": "/vulnerabilities/CVE-2022-35974/58591", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35973: Segfault in 'QuantizedMatMul'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-689c-r7h2-fv9v", "cve": "CVE-2022-35973", "id": "pyup.io-58592", "more_info_path": "/vulnerabilities/CVE-2022-35973/58592", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35971: 'CHECK' fail in 'FakeQuantWithMinMaxVars'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9fpg-838v-wpv7", "cve": "CVE-2022-35971", "id": "pyup.io-58616", "more_info_path": "/vulnerabilities/CVE-2022-35971/58616", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35970: Segfault in 'QuantizedInstanceNorm'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g35r-369w-3fqp", "cve": "CVE-2022-35970", "id": "pyup.io-58609", "more_info_path": "/vulnerabilities/CVE-2022-35970/58609", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35969: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q2c3-jpmc-gfjx", "cve": "CVE-2022-35969", "id": "pyup.io-58574", "more_info_path": "/vulnerabilities/CVE-2022-35969/58574", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35966: Segfault in 'QuantizedAvgPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4w68-4x85-mjj9", "cve": "CVE-2022-35966", "id": "pyup.io-58595", "more_info_path": "/vulnerabilities/CVE-2022-35966/58595", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35965: Segfault in 'LowerBound' and 'UpperBound'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qxpx-j395-pw36", "cve": "CVE-2022-35965", "id": "pyup.io-58605", "more_info_path": "/vulnerabilities/CVE-2022-35965/58605", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35964: Segfault in 'BlockLSTMGradV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f7r5-q7cx-h668", "cve": "CVE-2022-35964", "id": "pyup.io-58583", "more_info_path": "/vulnerabilities/CVE-2022-35964/58583", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35963: 'CHECK' failures in 'FractionalAvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-84jm-4cf3-9jfm", "cve": "CVE-2022-35963", "id": "pyup.io-58613", "more_info_path": "/vulnerabilities/CVE-2022-35963/58613", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35940: Int overflow in 'RaggedRangeOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x989-q2pq-4q5x", "cve": "CVE-2022-35940", "id": "pyup.io-58611", "more_info_path": "/vulnerabilities/CVE-2022-35940/58611", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35939: OOB write in 'scatter_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-ffjm-4qwc-7cmf", "cve": "CVE-2022-35939", "id": "pyup.io-58566", "more_info_path": "/vulnerabilities/CVE-2022-35939/58566", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35934: 'CHECK' failure in tf.reshape via overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f4w6-h4f5-wx45", "cve": "CVE-2022-35934", "id": "pyup.io-58575", "more_info_path": "/vulnerabilities/CVE-2022-35934/58575", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35988: 'CHECK' fail in 'tf.linalg.matrix_rank'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vqj-64pv-w55c", "cve": "CVE-2022-35988", "id": "pyup.io-58604", "more_info_path": "/vulnerabilities/CVE-2022-35988/58604", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36004: 'CHECK' fail in 'tf.random.gamma'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv8m-8x97-937q", "cve": "CVE-2022-36004", "id": "pyup.io-58617", "more_info_path": "/vulnerabilities/CVE-2022-36004/58617", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35983: 'CHECK' fail in 'Save' and 'SaveSlices'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6vp-8q9j-whx4", "cve": "CVE-2022-35983", "id": "pyup.io-58578", "more_info_path": "/vulnerabilities/CVE-2022-35983/58578", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35960: 'CHECK' failure in 'TensorListReserve' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v5xg-3q2c-c2r4", "cve": "CVE-2022-35960", "id": "pyup.io-58568", "more_info_path": "/vulnerabilities/CVE-2022-35960/58568", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35937: OOB read in 'Gather_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pxrw-j2fv-hx3h", "cve": "CVE-2022-35937", "id": "pyup.io-58565", "more_info_path": "/vulnerabilities/CVE-2022-35937/58565", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36001: 'CHECK' fail in 'DrawBoundingBoxes'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jqm7-m5q7-3hm5", "cve": "CVE-2022-36001", "id": "pyup.io-58612", "more_info_path": "/vulnerabilities/CVE-2022-36001/58612", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41889: If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a 'nullptr', which is not caught. An example can be seen in 'tf.compat.v1.extract_volume_patches' by passing in quantized tensors as input 'ksizes'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xxcj-rhqg-m46g", "cve": "CVE-2022-41889", "id": "pyup.io-58544", "more_info_path": "/vulnerabilities/CVE-2022-41889/58544", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41911: When printing a tensor, we get it's data as a 'const char*' array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from 'char' to 'bool' are undefined if the 'char' is not '0' or '1', so sanitizers/fuzzers will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j", "cve": "CVE-2022-41911", "id": "pyup.io-58543", "more_info_path": "/vulnerabilities/CVE-2022-41911/58543", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41910: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-frqp-wp83-qggv", "cve": "CVE-2022-41910", "id": "pyup.io-58559", "more_info_path": "/vulnerabilities/CVE-2022-41910/58559", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41898: If 'SparseFillEmptyRowsGrad' is given empty inputs, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hq7g-wwwp-q46h", "cve": "CVE-2022-41898", "id": "pyup.io-58561", "more_info_path": "/vulnerabilities/CVE-2022-41898/58561", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41897: If 'FractionMaxPoolGrad' is given outsize inputs 'row_pooling_sequence' and 'col_pooling_sequence', TensorFlow will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2w8-jw48-fr7j", "cve": "CVE-2022-41897", "id": "pyup.io-58557", "more_info_path": "/vulnerabilities/CVE-2022-41897/58557", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41894: The reference kernel of the 'CONV_3D_TRANSPOSE' TensorFlow Lite operator wrongly increments the data_ptr when adding the bias to the result. Instead of 'data_ptr += num_channels;' it should be 'data_ptr += output_num_channels;' as if the number of input channels is different than the number of output channels, the wrong result will be returned and a buffer overflow will occur if num_channels > output_num_channels. An attacker can craft a model with a specific number of input channels. It is then possible to write specific values through the bias of the layer outside the bounds of the buffer. This attack only works if the reference kernel resolver is used in the interpreter.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6q3-vv32-2cq5", "cve": "CVE-2022-41894", "id": "pyup.io-58562", "more_info_path": "/vulnerabilities/CVE-2022-41894/58562", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41884: If a numpy array is created with a shape such that one element is zero and the others sum to a large number, an error will be raised. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jq6x-99hj-q636", "cve": "CVE-2022-41884", "id": "pyup.io-58556", "more_info_path": "/vulnerabilities/CVE-2022-41884/58556", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41893: If 'tf.raw_ops.TensorListResize' is given a nonscalar value for input 'size', it results 'CHECK' fail which can be used to trigger a denial of service attack.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-67pf-62xr-q35m", "cve": "CVE-2022-41893", "id": "pyup.io-58547", "more_info_path": "/vulnerabilities/CVE-2022-41893/58547", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41908: TensorFlow is an open source platform for machine learning. An input 'token' that is not a UTF-8 bytestring will trigger a 'CHECK' fail in 'tf.raw_ops.PyFunc'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv77-9g28-cwg3", "cve": "CVE-2022-41908", "id": "pyup.io-58549", "more_info_path": "/vulnerabilities/CVE-2022-41908/58549", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41901: An input 'sparse_matrix' that is not a matrix with a shape with rank 0 will trigger a 'CHECK' fail in 'tf.raw_ops.SparseMatrixNNZ'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9fm-r5mm-rf9f", "cve": "CVE-2022-41901", "id": "pyup.io-58540", "more_info_path": "/vulnerabilities/CVE-2022-41901/58540", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41895: If 'MirrorPadGrad' is given outsize input 'paddings', TensorFlow will give a heap OOB error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gq2j-cr96-gvqx", "cve": "CVE-2022-41895", "id": "pyup.io-58541", "more_info_path": "/vulnerabilities/CVE-2022-41895/58541", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41900: The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xvwp-h6jv-7472", "cve": "CVE-2022-41900", "id": "pyup.io-58550", "more_info_path": "/vulnerabilities/CVE-2022-41900/58550", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41896: If 'ThreadUnsafeUnigramCandidateSampler' is given input 'filterbank_channel_count' greater than the allowed max size, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rmg2-f698-wq35", "cve": "CVE-2022-41896", "id": "pyup.io-58555", "more_info_path": "/vulnerabilities/CVE-2022-41896/58555", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41891: If 'tf.raw_ops.TensorListConcat' is given 'element_shape=[]', it results segmentation fault which can be used to trigger a denial of service attack.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-66vq-54fq-6jvv", "cve": "CVE-2022-41891", "id": "pyup.io-58542", "more_info_path": "/vulnerabilities/CVE-2022-41891/58542", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41886: When 'tf.raw_ops.ImageProjectiveTransformV2' is given a large output shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-54pp-c6pp-7fpx", "cve": "CVE-2022-41886", "id": "pyup.io-58558", "more_info_path": "/vulnerabilities/CVE-2022-41886/58558", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41888: When running on GPU, 'tf.image.generate_bounding_box_proposals' receives a 'scores' input that must be of rank 4 but is not checked.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6x99-gv2v-q76v", "cve": "CVE-2022-41888", "id": "pyup.io-58560", "more_info_path": "/vulnerabilities/CVE-2022-41888/58560", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41907: When 'tf.raw_ops.ResizeNearestNeighborGrad' is given a large 'size' input, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-368v-7v32-52fx", "cve": "CVE-2022-41907", "id": "pyup.io-58553", "more_info_path": "/vulnerabilities/CVE-2022-41907/58553", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41909: An input 'encoded' that is not a valid 'CompositeTensorVariant' tensor will trigger a segfault in 'tf.raw_ops.CompositeTensorVariantToComponents'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjx6-v474-2ch9", "cve": "CVE-2022-41909", "id": "pyup.io-58548", "more_info_path": "/vulnerabilities/CVE-2022-41909/58548", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41899: TensorFlow is an open source platform for machine learning. Inputs 'dense_features' or 'example_state_data' not of rank 2 will trigger a 'CHECK' fail in 'SdcaOptimizer'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-27rc-728f-x5w2", "cve": "CVE-2022-41899", "id": "pyup.io-58546", "more_info_path": "/vulnerabilities/CVE-2022-41899/58546", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41890: If 'BCast::ToShape' is given input larger than an 'int32', it will crash, despite being supposed to handle up to an 'int64'. An example can be seen in 'tf.experimental.numpy.outer' by passing in large input to the input 'b'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h246-cgh4-7475", "cve": "CVE-2022-41890", "id": "pyup.io-58551", "more_info_path": "/vulnerabilities/CVE-2022-41890/58551", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41885: When 'tf.raw_ops.FusedResizeAndPadConv2D' is given a large tensor shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-762h-vpvw-3rcx", "cve": "CVE-2022-41885", "id": "pyup.io-58545", "more_info_path": "/vulnerabilities/CVE-2022-41885/58545", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41880: When the 'BaseCandidateSamplerOp' function receives a value in 'true_classes' larger than 'range_max', a heap oob read occurs.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8w5g-3wcv-9g2j", "cve": "CVE-2022-41880", "id": "pyup.io-58552", "more_info_path": "/vulnerabilities/CVE-2022-41880/58552", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41902: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cg88-rpvp-cjv5", "cve": "CVE-2022-41902", "id": "pyup.io-58554", "more_info_path": "/vulnerabilities/CVE-2022-41902/58554", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35991: 'CHECK' fail in 'TensorListScatter' and 'TensorListScatterV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vm7x-4qhj-rrcq\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xf83-q765-xm6m", "cve": "CVE-2022-35991", "id": "pyup.io-58564", "more_info_path": "/vulnerabilities/CVE-2022-35991/58564", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-cpu-aws 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35935: 'CHECK' failure in 'SobolSample' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-97p7-w86h-vcf9\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqvq-fvhr-v6hc", "cve": "CVE-2022-35935", "id": "pyup.io-58563", "more_info_path": "/vulnerabilities/CVE-2022-35935/58563", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-cpu-aws 2.9.3 and 2.10.1 include a fix for CVE-2022-41887: 'tf.keras.losses.poisson' receives a 'y_pred' and 'y_true' that are passed through 'functor::mul' in 'BinaryOp'. If the resulting dimensions overflow an 'int32', TensorFlow will crash due to a size mismatch during broadcast assignment.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fvv-46hw-vpg3", "cve": "CVE-2022-41887", "id": "pyup.io-58539", "more_info_path": "/vulnerabilities/CVE-2022-41887/58539", "specs": [ "<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-cpu-aws 2.10.1 includes a fix for CVE-2022-41883: When ops that have specified input sizes receive a differing number of inputs, the executor will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj", "cve": "CVE-2022-41883", "id": "pyup.io-58538", "more_info_path": "/vulnerabilities/CVE-2022-41883/58538", "specs": [ ">=2.10.0rc0,<2.10.1" ], "v": ">=2.10.0rc0,<2.10.1" } ], "tensorflow-directml": [ { "advisory": "Tensorflow-directml 1.15.3 updates its dependency 'SQLite' to v3.31.01 to include security fixes.", "cve": "CVE-2019-19645", "id": "pyup.io-39828", "more_info_path": "/vulnerabilities/CVE-2019-19645/39828", "specs": [ "<1.15.3" ], "v": "<1.15.3" }, { "advisory": "Tensorflow-directml 1.15.3 updates libjpeg-turbo to 2.0.4 to handle CVE-2018-19664, CVE-2018-20330 and CVE-2019-13960.", "cve": "CVE-2018-19664", "id": "pyup.io-39832", "more_info_path": "/vulnerabilities/CVE-2018-19664/39832", "specs": [ "<1.15.3" ], "v": "<1.15.3" }, { "advisory": "Tensorflow-directml 1.15.3 updates its dependency 'Apache Spark' to v2.4.5 to include a security fix.", "cve": "CVE-2019-10099", "id": "pyup.io-39835", "more_info_path": "/vulnerabilities/CVE-2019-10099/39835", "specs": [ "<1.15.3" ], "v": "<1.15.3" }, { "advisory": "Tensorflow-directml 1.15.3 updates libjpeg-turbo to 2.0.4 to handle CVE-2018-19664, CVE-2018-20330 and CVE-2019-13960.", "cve": "CVE-2018-20330", "id": "pyup.io-39831", "more_info_path": "/vulnerabilities/CVE-2018-20330/39831", "specs": [ "<1.15.3" ], "v": "<1.15.3" }, { "advisory": "Tensorflow-directml 1.15.3 updates Apache Spark to 2.4.5 to handle CVE-2019-10099, CVE-2018-17190 and CVE-2018-11770.", "cve": "CVE-2018-17190", "id": "pyup.io-39834", "more_info_path": "/vulnerabilities/CVE-2018-17190/39834", "specs": [ "<1.15.3" ], "v": "<1.15.3" }, { "advisory": "Tensorflow-directml 1.15.3 updates 'SQLite3' to v3.31.01 to include security fixes.", "cve": "CVE-2019-19244", "id": "pyup.io-39827", "more_info_path": "/vulnerabilities/CVE-2019-19244/39827", "specs": [ "<1.15.3" ], "v": "<1.15.3" }, { "advisory": "Tensorflow-directml 1.15.3 updates Apache Spark to 2.4.5 to handle CVE-2019-10099, CVE-2018-17190 and CVE-2018-11770.", "cve": "CVE-2018-11770", "id": "pyup.io-39833", "more_info_path": "/vulnerabilities/CVE-2018-11770/39833", "specs": [ "<1.15.3" ], "v": "<1.15.3" }, { "advisory": "Tensorflow-directml 1.15.3 updates 'SQLite3' to v3.31.01 to include security fixes.", "cve": "CVE-2019-19880", "id": "pyup.io-38778", "more_info_path": "/vulnerabilities/CVE-2019-19880/38778", "specs": [ "<1.15.3" ], "v": "<1.15.3" }, { "advisory": "Tensorflow-directml 1.15.3 updates libjpeg-turbo to 2.0.4 to handle CVE-2018-19664, CVE-2018-20330 and CVE-2019-13960.", "cve": "CVE-2019-13960", "id": "pyup.io-39830", "more_info_path": "/vulnerabilities/CVE-2019-13960/39830", "specs": [ "<1.15.3" ], "v": "<1.15.3" }, { "advisory": "Tensorflow-directml 1.15.4 updates its dependency \"SQlite3\" to v3.33.0 to include security fixes.", "cve": "CVE-2020-11655", "id": "pyup.io-40362", "more_info_path": "/vulnerabilities/CVE-2020-11655/40362", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 updates its dependency \"SQlite3\" to v3.33.0 to include security fixes.", "cve": "CVE-2020-11656", "id": "pyup.io-40363", "more_info_path": "/vulnerabilities/CVE-2020-11656/40363", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 includes a fix for CVE-2020-15190: In Tensorflow before version 1.15.4 the \"tf.raw_ops.Switch\" operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is \"nullptr\", hence we are binding a reference to \"nullptr\". This is undefined behavior and reported as an error if compiling with \"-fsanitize=null\". In this case, this results in a segmentation fault. The issue was patched in commit da8558533d925694483d2c136a9220d6d49d843c.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4g9f-63rx-5cw4", "cve": "CVE-2020-15190", "id": "pyup.io-39317", "more_info_path": "/vulnerabilities/CVE-2020-15190/39317", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml version 1.15.4 includes a fix for CVE-2020-15209: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a \"nullptr\" buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with \"nullptr\". However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue is patched in commit 0b5662bc.", "cve": "CVE-2020-15209", "id": "pyup.io-40358", "more_info_path": "/vulnerabilities/CVE-2020-15209/40358", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 includes a fix for CVE-2020-13435: SQLite through 3.32.0 has a segmentation fault in sqlite3ExprCodeTarget in expr.c.", "cve": "CVE-2020-13435", "id": "pyup.io-40365", "more_info_path": "/vulnerabilities/CVE-2020-13435/40365", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml version 1.15.4 includes a fix for CVE-2020-15204: In eager mode, tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling \"tf.raw_ops.GetSessionHandle\" or \"tf.raw_ops.GetSessionHandleV2\" results in a null pointer dereference In linked snippet, in eager mode, \"ctx->session_state()\" returns \"nullptr\". Since code immediately dereferences this, we get a segmentation fault. The issue is patched in commit 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1", "cve": "CVE-2020-15204", "id": "pyup.io-40353", "more_info_path": "/vulnerabilities/CVE-2020-15204/40353", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 includes a fix for CVE-2020-15210: In tensorflow-lite before versions 1.15.4, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, it leads to segmentation fault or just memory corruption.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x9j7-x98r-r4w2", "cve": "CVE-2020-15210", "id": "pyup.io-40359", "more_info_path": "/vulnerabilities/CVE-2020-15210/40359", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml version 1.15.4 includes a fix for CVE-2020-15208: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a \"DCHECK\" which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue is patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d.", "cve": "CVE-2020-15208", "id": "pyup.io-40357", "more_info_path": "/vulnerabilities/CVE-2020-15208/40357", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml version 1.15.4 includes a fix for CVE-2020-15211: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor. However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative \"-1\" value as index for these tensors. This results in special casing during validation at model loading time. Unfortunately, this means that the \"-1\" index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays. This results in both read and write gadgets, albeit very limited in scope. A potential workaround would be to add a custom \"Verifier\" to the model loading code to ensure that only operators which accept optional inputs use the \"-1\" special value and only for the tensors that they expect to be optional. Since this allow-list type approach is error-prone, its advised upgrading to the patched code. The issue is patched in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83).", "cve": "CVE-2020-15211", "id": "pyup.io-40360", "more_info_path": "/vulnerabilities/CVE-2020-15211/40360", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 includes a fix for CVE-2020-15207: In tensorflow-lite before versions 1.15.4, to mimic Python's indexing with negative values, TFLite uses 'ResolveAxis' to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the 'DCHECK' does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34", "cve": "CVE-2020-15207", "id": "pyup.io-40356", "more_info_path": "/vulnerabilities/CVE-2020-15207/40356", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml version 1.15.4 includes a fix for CVE-2020-15206: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's \"SavedModel\" protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using \"tensorflow-serving\" or other inference-as-a-service installments. The issue is patched in commit adf095206f25471e864a8e63a0f1caef53a0e3a6.", "cve": "CVE-2020-15206", "id": "pyup.io-40355", "more_info_path": "/vulnerabilities/CVE-2020-15206/40355", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 includes a fix for CVE-2020-15205: In Tensorflow before versions 1.15.4, the 'data_splits' argument of 'tf.raw_ops.StringNGrams' lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after 'ee ff' are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46", "cve": "CVE-2020-15205", "id": "pyup.io-40354", "more_info_path": "/vulnerabilities/CVE-2020-15205/40354", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 includes a fix for CVE-2020-15203: In Tensorflow before version 1.15.4, by controlling the 'fill' argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a 'printf' call is constructed. This may result in segmentation fault.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79", "cve": "CVE-2020-15203", "id": "pyup.io-40352", "more_info_path": "/vulnerabilities/CVE-2020-15203/40352", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 includes a fix for CVE-2020-15195: In Tensorflow before version 1.15.4, the implementation of 'SparseFillEmptyRowsGrad' uses a double indexing pattern. It is possible for 'reverse_index_map(i)' to be an index outside of bounds of 'grad_values', thus resulting in a heap buffer overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-63xm-rx5p-xvqr", "cve": "CVE-2020-15195", "id": "pyup.io-40350", "more_info_path": "/vulnerabilities/CVE-2020-15195/40350", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 includes a fix for CVE-2020-15194: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments. Although `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\"", "cve": "CVE-2020-15194", "id": "pyup.io-40349", "more_info_path": "/vulnerabilities/CVE-2020-15194/40349", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 updates its dependency \"SQlite3\" to 3.33.0 to fix CVE-2020-15358.", "cve": "CVE-2020-15358", "id": "pyup.io-40369", "more_info_path": "/vulnerabilities/CVE-2020-15358/40369", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 updates its dependency \"SQlite\" to 3.32.3 to fix CVE-2020-13871.", "cve": "CVE-2020-13871", "id": "pyup.io-40368", "more_info_path": "/vulnerabilities/CVE-2020-13871/40368", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 updates 'sqlite3' to '3.33.0' to handle several CVEs. One of them is CVE-2020-13630.", "cve": "CVE-2020-13630", "id": "pyup.io-40366", "more_info_path": "/vulnerabilities/CVE-2020-13630/40366", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 updates its dependency \"SQlite3\" to 3.33.0 to fix CVE-2020-13434.", "cve": "CVE-2020-13434", "id": "pyup.io-40364", "more_info_path": "/vulnerabilities/CVE-2020-13434/40364", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 updates its dependency \"SQlite3\" to v3.33.0 to include security fixes.", "cve": "CVE-2020-9327", "id": "pyup.io-40361", "more_info_path": "/vulnerabilities/CVE-2020-9327/40361", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 includes a fix for CVE-2020-15202: In Tensorflow before version 1.15.4, the 'Shard' API in TensorFlow expects the last argument to be a function taking two 'int64' (i.e., 'long long') arguments. However, there are several places in TensorFlow where a lambda taking 'int' or 'int32' arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4", "cve": "CVE-2020-15202", "id": "pyup.io-40351", "more_info_path": "/vulnerabilities/CVE-2020-15202/40351", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.4 updates its dependency \"SQlite3\" to v3.33.0 to include security fixes.", "cve": "CVE-2020-13631", "id": "pyup.io-40367", "more_info_path": "/vulnerabilities/CVE-2020-13631/40367", "specs": [ "<1.15.4" ], "v": "<1.15.4" }, { "advisory": "Tensorflow-directml 1.15.5 updates its dependency \"PCRE\" to version 8.44 to fix CVE-2019-20838.", "cve": "CVE-2019-20838", "id": "pyup.io-40339", "more_info_path": "/vulnerabilities/CVE-2019-20838/40339", "specs": [ "<1.15.5" ], "v": "<1.15.5" }, { "advisory": "Tensorflow-directml 1.15.5 fixes a 'CHECK'-fail in LSTM with zero-length input (CVE-2020-26270).", "cve": "CVE-2020-26270", "id": "pyup.io-40335", "more_info_path": "/vulnerabilities/CVE-2020-26270/40335", "specs": [ "<1.15.5" ], "v": "<1.15.5" }, { "advisory": "Tensorflow-directml 1.15.5 fixes a vulnerability caused by attempting to write to immutable memory region in 'tf.raw_ops.ImmutableConst' (CVE-2020-26268).", "cve": "CVE-2020-26268", "id": "pyup.io-40334", "more_info_path": "/vulnerabilities/CVE-2020-26268/40334", "specs": [ "<1.15.5" ], "v": "<1.15.5" }, { "advisory": "Tensorflow-directml 1.15.5 includes a fix for CVE-2020-26267: In affected versions of TensorFlow the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.", "cve": "CVE-2020-26267", "id": "pyup.io-40333", "more_info_path": "/vulnerabilities/CVE-2020-26267/40333", "specs": [ "<1.15.5" ], "v": "<1.15.5" }, { "advisory": "Tensorflow-directml 1.15.5 fixes a security vulnerability caused by accessing heap data outside of bounds when loading a specially crafted 'SavedModel' (CVE-2020-26271).", "cve": "CVE-2020-26271", "id": "pyup.io-40336", "more_info_path": "/vulnerabilities/CVE-2020-26271/40336", "specs": [ "<1.15.5" ], "v": "<1.15.5" }, { "advisory": "Tensorflow-directml 1.15.5 updates its dependency 'Junit4' to v4.13.1 to include a security fix.", "cve": "CVE-2020-15250", "id": "pyup.io-40338", "more_info_path": "/vulnerabilities/CVE-2020-15250/40338", "specs": [ "<1.15.5" ], "v": "<1.15.5" }, { "advisory": "Tensorflow-directml 1.15.5 fixes an access to unitialized memory in the 'Eigen' code (CVE-2020-26266).", "cve": "CVE-2020-26266", "id": "pyup.io-40322", "more_info_path": "/vulnerabilities/CVE-2020-26266/40322", "specs": [ "<1.15.5" ], "v": "<1.15.5" }, { "advisory": "Tensorflow-directml 1.15.5 updates its dependency \"PCRE\" to version 8.44 to fix CVE-2020-14155.", "cve": "CVE-2020-14155", "id": "pyup.io-40340", "more_info_path": "/vulnerabilities/CVE-2020-14155/40340", "specs": [ "<1.15.5" ], "v": "<1.15.5" }, { "advisory": "Tensorflow-directml 1.15.5 updates the 'libjpeg-turbo' dependency to 2.0.5 to handle a security vulnerability (CVE-2020-13790).", "cve": "CVE-2020-13790", "id": "pyup.io-40337", "more_info_path": "/vulnerabilities/CVE-2020-13790/40337", "specs": [ "<1.15.5" ], "v": "<1.15.5" } ], "tensorflow-estimator": [ { "advisory": "Tensorflow-estimator 2.9.0 removes all boosted trees code due to security issues.", "cve": "PVE-2022-48551", "id": "pyup.io-48551", "more_info_path": "/vulnerabilities/PVE-2022-48551/48551", "specs": [ "<2.9.0" ], "v": "<2.9.0" } ], "tensorflow-federated": [ { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-30115", "id": "pyup.io-49296", "more_info_path": "/vulnerabilities/CVE-2022-30115/49296", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-27781", "id": "pyup.io-49270", "more_info_path": "/vulnerabilities/CVE-2022-27781/49270", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-27780", "id": "pyup.io-49269", "more_info_path": "/vulnerabilities/CVE-2022-27780/49269", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29216", "id": "pyup.io-49295", "more_info_path": "/vulnerabilities/CVE-2022-29216/49295", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29213", "id": "pyup.io-49294", "more_info_path": "/vulnerabilities/CVE-2022-29213/49294", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29210", "id": "pyup.io-49291", "more_info_path": "/vulnerabilities/CVE-2022-29210/49291", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29206", "id": "pyup.io-49287", "more_info_path": "/vulnerabilities/CVE-2022-29206/49287", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29205", "id": "pyup.io-49286", "more_info_path": "/vulnerabilities/CVE-2022-29205/49286", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29204", "id": "pyup.io-49285", "more_info_path": "/vulnerabilities/CVE-2022-29204/49285", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29203", "id": "pyup.io-49284", "more_info_path": "/vulnerabilities/CVE-2022-29203/49284", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29200", "id": "pyup.io-49281", "more_info_path": "/vulnerabilities/CVE-2022-29200/49281", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29196", "id": "pyup.io-49277", "more_info_path": "/vulnerabilities/CVE-2022-29196/49277", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29208", "id": "pyup.io-49289", "more_info_path": "/vulnerabilities/CVE-2022-29208/49289", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29192", "id": "pyup.io-49273", "more_info_path": "/vulnerabilities/CVE-2022-29192/49273", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29191", "id": "pyup.io-49272", "more_info_path": "/vulnerabilities/CVE-2022-29191/49272", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-27774", "id": "pyup.io-49264", "more_info_path": "/vulnerabilities/CVE-2022-27774/49264", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29198", "id": "pyup.io-49279", "more_info_path": "/vulnerabilities/CVE-2022-29198/49279", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29193", "id": "pyup.io-49274", "more_info_path": "/vulnerabilities/CVE-2022-29193/49274", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-27775", "id": "pyup.io-49265", "more_info_path": "/vulnerabilities/CVE-2022-27775/49265", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-27779", "id": "pyup.io-49268", "more_info_path": "/vulnerabilities/CVE-2022-27779/49268", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29202", "id": "pyup.io-49283", "more_info_path": "/vulnerabilities/CVE-2022-29202/49283", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-27776", "id": "pyup.io-49266", "more_info_path": "/vulnerabilities/CVE-2022-27776/49266", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29207", "id": "pyup.io-49288", "more_info_path": "/vulnerabilities/CVE-2022-29207/49288", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29212", "id": "pyup.io-49293", "more_info_path": "/vulnerabilities/CVE-2022-29212/49293", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-22576", "id": "pyup.io-49263", "more_info_path": "/vulnerabilities/CVE-2022-22576/49263", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29199", "id": "pyup.io-49280", "more_info_path": "/vulnerabilities/CVE-2022-29199/49280", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29194", "id": "pyup.io-49275", "more_info_path": "/vulnerabilities/CVE-2022-29194/49275", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29211", "id": "pyup.io-49292", "more_info_path": "/vulnerabilities/CVE-2022-29211/49292", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29197", "id": "pyup.io-49278", "more_info_path": "/vulnerabilities/CVE-2022-29197/49278", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-27778", "id": "pyup.io-49267", "more_info_path": "/vulnerabilities/CVE-2022-27778/49267", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29201", "id": "pyup.io-49282", "more_info_path": "/vulnerabilities/CVE-2022-29201/49282", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-27782", "id": "pyup.io-49271", "more_info_path": "/vulnerabilities/CVE-2022-27782/49271", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29195", "id": "pyup.io-49276", "more_info_path": "/vulnerabilities/CVE-2022-29195/49276", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2022-29209", "id": "pyup.io-49290", "more_info_path": "/vulnerabilities/CVE-2022-29209/49290", "specs": [ "<0.25.0" ], "v": "<0.25.0" }, { "advisory": "Tensorflow-federated 0.25.0 updates its dependency 'TensorFlow' to v2.9.0 to include security fixes.", "cve": "CVE-2018-25032", "id": "pyup.io-49261", "more_info_path": "/vulnerabilities/CVE-2018-25032/49261", "specs": [ "<0.25.0" ], "v": "<0.25.0" } ], "tensorflow-gpu": [ { "advisory": "Tensorflow-gpu before 1.10.0 uses an insecure grpc dependency.", "cve": "PVE-2021-36375", "id": "pyup.io-56365", "more_info_path": "/vulnerabilities/PVE-2021-36375/56365", "specs": [ "<1.10.0" ], "v": "<1.10.0" }, { "advisory": "NULL pointer dereference in Google TensorFlow before 1.12.2 could cause a denial of service via an invalid GIF file. See CVE-2019-9635.", "cve": "CVE-2019-9635", "id": "pyup.io-56364", "more_info_path": "/vulnerabilities/CVE-2019-9635/56364", "specs": [ "<1.12.2" ], "v": "<1.12.2" }, { "advisory": "Tensorflow-gpu 1.15 includes a fix for CVE-2019-16778: In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-844w-j86r-4x2j\nhttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2019-002.md\nhttps://github.com/tensorflow/tensorflow/commit/db4f9717c41bccc3ce10099ab61996b246099892", "cve": "CVE-2019-16778", "id": "pyup.io-56363", "more_info_path": "/vulnerabilities/CVE-2019-16778/56363", "specs": [ "<1.15" ], "v": "<1.15" }, { "advisory": "The original changelog reads: \"Tensorflow-gpu 2.0 fixes a potential security vulnerability where decoding variant tensors from proto could result in heap out of bounds memory access.\" However, it was later confirmed that the fix was already included in 1.15 and later. See: .", "cve": "PVE-2021-37524", "id": "pyup.io-56362", "more_info_path": "/vulnerabilities/PVE-2021-37524/56362", "specs": [ "<1.15.0" ], "v": "<1.15.0" }, { "advisory": "Tensorflow-gpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2019-13960.", "cve": "CVE-2019-13960", "id": "pyup.io-56352", "more_info_path": "/vulnerabilities/CVE-2019-13960/56352", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-gpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"Apache Spark\" to handle CVE-2018-17190.", "cve": "CVE-2018-17190", "id": "pyup.io-56353", "more_info_path": "/vulnerabilities/CVE-2018-17190/56353", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-gpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2018-20330.", "cve": "CVE-2018-20330", "id": "pyup.io-56351", "more_info_path": "/vulnerabilities/CVE-2018-20330/56351", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-gpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"SQLite3\" to handle CVE-2019-19244.", "cve": "CVE-2019-19244", "id": "pyup.io-56348", "more_info_path": "/vulnerabilities/CVE-2019-19244/56348", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-gpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2018-19664.", "cve": "CVE-2018-19664", "id": "pyup.io-56350", "more_info_path": "/vulnerabilities/CVE-2018-19664/56350", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-gpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"Apache Spark\" to handle CVE-2019-10099.", "cve": "CVE-2019-10099", "id": "pyup.io-56355", "more_info_path": "/vulnerabilities/CVE-2019-10099/56355", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-gpu versions 1.15.3, 2.0.2 and 2.1.1 update its dependency \"SQLite3\" to handle CVE-2019-19880.", "cve": "CVE-2019-19880", "id": "pyup.io-56347", "more_info_path": "/vulnerabilities/CVE-2019-19880/56347", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-gpu versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"SQLite\" to handle CVE-2019-19645.", "cve": "CVE-2019-19645", "id": "pyup.io-56349", "more_info_path": "/vulnerabilities/CVE-2019-19645/56349", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-gpu versions 1.15.3, 2.0.2 and 2.1.1 update its dependency \"Apache Spark\" to handle CVE-2018-11770.", "cve": "CVE-2018-11770", "id": "pyup.io-56354", "more_info_path": "/vulnerabilities/CVE-2018-11770/56354", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15190: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the \"tf.raw_ops.Switch\" operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is \"nullptr\", hence we are binding a reference to \"nullptr\". This is undefined behavior and reported as an error if compiling with \"-fsanitize=null\". In this case, this results in a segmentation fault The issue was patched in commit da8558533d925694483d2c136a9220d6d49d843c\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4g9f-63rx-5cw4", "cve": "CVE-2020-15190", "id": "pyup.io-56327", "more_info_path": "/vulnerabilities/CVE-2020-15190/56327", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15211: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor. However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative \"-1\" value as index for these tensors. This results in special casing during validation at model loading time. Unfortunately, this means that the \"-1\" index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays. This results in both read and write gadgets, albeit very limited in scope. The issue was patched in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83). A potential workaround would be to add a custom \"Verifier\" to the model loading code to ensure that only operators which accept optional inputs use the \"-1\" special value and only for the tensors that they expect to be optional. Since this allow-list type approach is error-prone, it's advised upgrading to the patched code.", "cve": "CVE-2020-15211", "id": "pyup.io-56325", "more_info_path": "/vulnerabilities/CVE-2020-15211/56325", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15205: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'data_splits' argument of 'tf.raw_ops.StringNGrams' lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after 'ee ff' are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46", "cve": "CVE-2020-15205", "id": "pyup.io-56330", "more_info_path": "/vulnerabilities/CVE-2020-15205/56330", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15208: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a \"DCHECK\" which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue was patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d", "cve": "CVE-2020-15208", "id": "pyup.io-56326", "more_info_path": "/vulnerabilities/CVE-2020-15208/56326", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15207: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses 'ResolveAxis' to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the 'DCHECK' does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34", "cve": "CVE-2020-15207", "id": "pyup.io-56332", "more_info_path": "/vulnerabilities/CVE-2020-15207/56332", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15206: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's \"SavedModel\" protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using \"tensorflow-serving\" or other inference-as-a-service installments. Fixed were added in commits f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d. However, this was not enough, as #41097 reported a different failure mode. The issue was finally patched in commit df095206f25471e864a8e63a0f1caef53a0e3a6", "cve": "CVE-2020-15206", "id": "pyup.io-56324", "more_info_path": "/vulnerabilities/CVE-2020-15206/56324", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15203: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the 'fill' argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a 'printf' call is constructed. This may result in segmentation fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79", "cve": "CVE-2020-15203", "id": "pyup.io-56331", "more_info_path": "/vulnerabilities/CVE-2020-15203/56331", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15204: In eager mode, TensorFlow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling \"tf.raw_ops.GetSessionHandle\" or \"tf.raw_ops.GetSessionHandleV2\" results in a null pointer dereference In linked snippet, in eager mode, \"ctx->session_state()\" returns \"nullptr\". Since code immediately dereferences this, we get a segmentation fault. The issue was patched in commit 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1", "cve": "CVE-2020-15204", "id": "pyup.io-56322", "more_info_path": "/vulnerabilities/CVE-2020-15204/56322", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15195: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of 'SparseFillEmptyRowsGrad' uses a double indexing pattern. It is possible for 'reverse_index_map(i)' to be an index outside of bounds of 'grad_values', thus resulting in a heap buffer overflow.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-63xm-rx5p-xvqr", "cve": "CVE-2020-15195", "id": "pyup.io-56323", "more_info_path": "/vulnerabilities/CVE-2020-15195/56323", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15209: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a \"nullptr\" buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with \"nullptr\". However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue was patched in commit 0b5662bc.", "cve": "CVE-2020-15209", "id": "pyup.io-56329", "more_info_path": "/vulnerabilities/CVE-2020-15209/56329", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15202: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'Shard' API in TensorFlow expects the last argument to be a function taking two 'int64' (i.e., 'long long') arguments. However, there are several places in TensorFlow where a lambda taking 'int' or 'int32' arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4", "cve": "CVE-2020-15202", "id": "pyup.io-56328", "more_info_path": "/vulnerabilities/CVE-2020-15202/56328", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11655.", "cve": "CVE-2020-11655", "id": "pyup.io-56316", "more_info_path": "/vulnerabilities/CVE-2020-11655/56316", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11656.", "cve": "CVE-2020-11656", "id": "pyup.io-56317", "more_info_path": "/vulnerabilities/CVE-2020-11656/56317", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13871.", "cve": "CVE-2020-13871", "id": "pyup.io-56312", "more_info_path": "/vulnerabilities/CVE-2020-13871/56312", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13630.", "cve": "CVE-2020-13630", "id": "pyup.io-56313", "more_info_path": "/vulnerabilities/CVE-2020-13630/56313", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13434.", "cve": "CVE-2020-13434", "id": "pyup.io-56314", "more_info_path": "/vulnerabilities/CVE-2020-13434/56314", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-9327.", "cve": "CVE-2020-9327", "id": "pyup.io-56315", "more_info_path": "/vulnerabilities/CVE-2020-9327/56315", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13631.", "cve": "CVE-2020-13631", "id": "pyup.io-56318", "more_info_path": "/vulnerabilities/CVE-2020-13631/56318", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13435.", "cve": "CVE-2020-13435", "id": "pyup.io-56319", "more_info_path": "/vulnerabilities/CVE-2020-13435/56319", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15210: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x9j7-x98r-r4w2", "cve": "CVE-2020-15210", "id": "pyup.io-56320", "more_info_path": "/vulnerabilities/CVE-2020-15210/56320", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu 2.4.0 includes a fix for CVE-2020-15194: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments. Although `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\"", "cve": "CVE-2020-15194", "id": "pyup.io-56321", "more_info_path": "/vulnerabilities/CVE-2020-15194/56321", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency \"PCRE\" to fix CVE-2019-20838.", "cve": "CVE-2019-20838", "id": "pyup.io-56298", "more_info_path": "/vulnerabilities/CVE-2019-20838/56298", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-gpu versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency 'Junit4' to v4.13.1 to include a security fix.", "cve": "CVE-2020-15250", "id": "pyup.io-56299", "more_info_path": "/vulnerabilities/CVE-2020-15250/56299", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-gpu versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 updates its dependency \"Libjpeg-turbo\" to handle CVE-2020-13790.", "cve": "CVE-2020-13790", "id": "pyup.io-56301", "more_info_path": "/vulnerabilities/CVE-2020-13790/56301", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-gpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2 and 2.3.2 update its dependency \"PCRE\" to handle CVE-2020-14155.", "cve": "CVE-2020-14155", "id": "pyup.io-56300", "more_info_path": "/vulnerabilities/CVE-2020-14155/56300", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-gpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26271: In affected versions, under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library.", "cve": "CVE-2020-26271", "id": "pyup.io-56302", "more_info_path": "/vulnerabilities/CVE-2020-26271/56302", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-gpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26270: In affected versions, running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.", "cve": "CVE-2020-26270", "id": "pyup.io-56306", "more_info_path": "/vulnerabilities/CVE-2020-26270/56306", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-gpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26267: In affected versions, the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes.", "cve": "CVE-2020-26267", "id": "pyup.io-56303", "more_info_path": "/vulnerabilities/CVE-2020-26267/56303", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-gpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0 includes a fix for CVE-2020-26266: In affected versions and under certain cases a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers filled with the default value of the type but forgetting to default initialize the quantized floating point types in Eigen.", "cve": "CVE-2020-26266", "id": "pyup.io-56304", "more_info_path": "/vulnerabilities/CVE-2020-26266/56304", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-gpu versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26268: In affected versions, the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden.", "cve": "CVE-2020-26268", "id": "pyup.io-56305", "more_info_path": "/vulnerabilities/CVE-2020-26268/56305", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent. See CVE-2018-7576.", "cve": "CVE-2018-7576", "id": "pyup.io-56371", "more_info_path": "/vulnerabilities/CVE-2018-7576/56371", "specs": [ "<1.6.0a1" ], "v": "<1.6.0a1" }, { "advisory": "Tensorflow-gpu before 1.7.0 has an integer overflow that causes an out-of-bounds read, possibly causing disclosure of the contents of process memory. This occurs in the DecodeBmp feature of the BMP decoder in core/kernels/decode_bmp_op.cc. See CVE-2018-21233.", "cve": "CVE-2018-21233", "id": "pyup.io-56370", "more_info_path": "/vulnerabilities/CVE-2018-21233/56370", "specs": [ "<1.7.0" ], "v": "<1.7.0" }, { "advisory": "Google TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability. The type of exploitation is context-dependent. See CVE-2018-7575.", "cve": "CVE-2018-7575", "id": "pyup.io-56369", "more_info_path": "/vulnerabilities/CVE-2018-7575/56369", "specs": [ "<1.7.0a1" ], "v": "<1.7.0a1" }, { "advisory": "Memcpy parameter overlap in Google Snappy library 1.1.4, as used in Google TensorFlow before 1.7.1, could result in a crash or read from other parts of process memory. See CVE-2018-7577.", "cve": "CVE-2018-7577", "id": "pyup.io-56367", "more_info_path": "/vulnerabilities/CVE-2018-7577/56367", "specs": [ "<1.7.1" ], "v": "<1.7.1" }, { "advisory": "Invalid memory access and/or a heap buffer overflow in the TensorFlow XLA compiler in Google TensorFlow before 1.7.1 could cause a crash or read from other parts of process memory via a crafted configuration file. See CVE-2018-10055.", "cve": "CVE-2018-10055", "id": "pyup.io-56368", "more_info_path": "/vulnerabilities/CVE-2018-10055/56368", "specs": [ "<1.7.1" ], "v": "<1.7.1" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25661: In versions prior to 2.11.1 a malicious invalid input crashes a tensorflow model (Check Failed) and can be used to trigger a denial of service attack. A proof of concept can be constructed with the 'Convolution3DTranspose' function. This Convolution3DTranspose layer is a very common API in modern neural networks. The ML models containing such vulnerable components could be deployed in ML applications or as cloud services. This failure could be potentially used to trigger a denial of service attack on ML cloud services. An attacker must have privilege to provide input to a 'Convolution3DTranspose' call.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fxgc-95xx-grvq", "cve": "CVE-2023-25661", "id": "pyup.io-55894", "more_info_path": "/vulnerabilities/CVE-2023-25661/55894", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-27579: Constructing a tflite model with a paramater 'filter_input_channel' of less than 1 gives a FPE.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5w96-866f-6rm8", "cve": "CVE-2023-27579", "id": "pyup.io-55898", "more_info_path": "/vulnerabilities/CVE-2023-27579/55898", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25676: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.ParallelConcat' segfaults with a nullptr dereference when given a parameter 'shape' with rank that is not greater than zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6wfh-89q8-44jq", "cve": "CVE-2023-25676", "id": "pyup.io-55890", "more_info_path": "/vulnerabilities/CVE-2023-25676/55890", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25672: The function 'tf.raw_ops.LookupTableImportV2' cannot handle scalars in the 'values' parameter and gives an NPE. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25672", "id": "pyup.io-55889", "more_info_path": "/vulnerabilities/CVE-2023-25672/55889", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25671: There is out-of-bounds access due to mismatched integer type sizes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j5w9-hmfh-4cr6", "cve": "CVE-2023-25671", "id": "pyup.io-55899", "more_info_path": "/vulnerabilities/CVE-2023-25671/55899", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25670: Versions prior to 2.12.0 and 2.11.1 have a null point error in QuantizedMatMulWithBiasAndDequantize with MKL enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rq-hwc3-x77w", "cve": "CVE-2023-25670", "id": "pyup.io-55900", "more_info_path": "/vulnerabilities/CVE-2023-25670/55900", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25669: Prior to versions 2.12.0 and 2.11.1, if the stride and window size are not positive for 'tf.raw_ops.AvgPoolGrad', it can give a floating point exception.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rcf8-g8jv-vg6p", "cve": "CVE-2023-25669", "id": "pyup.io-55901", "more_info_path": "/vulnerabilities/CVE-2023-25669/55901", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25667: Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when '2^31 <= num_frames * height * width * channels < 2^32', for example Full HD screencast of at least 346 frames.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqm2-gh8w-gr68", "cve": "CVE-2023-25667", "id": "pyup.io-55892", "more_info_path": "/vulnerabilities/CVE-2023-25667/55892", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25666: Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2", "cve": "CVE-2023-25666", "id": "pyup.io-55891", "more_info_path": "/vulnerabilities/CVE-2023-25666/55891", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25665: Prior to versions 2.12.0 and 2.11.1, when 'SparseSparseMaximum' is given invalid sparse tensors as inputs, it can give a null pointer error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-558h-mq8x-7q9g", "cve": "CVE-2023-25665", "id": "pyup.io-55897", "more_info_path": "/vulnerabilities/CVE-2023-25665/55897", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25664: Prior to versions 2.12.0 and 2.11.1, there is a heap buffer overflow in TAvgPoolGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hg6-5c2q-7rcr", "cve": "CVE-2023-25664", "id": "pyup.io-55903", "more_info_path": "/vulnerabilities/CVE-2023-25664/55903", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25662: Versions prior to 2.12.0 and 2.11.1 are vulnerable to integer overflow in EditDistance.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7jvm-xxmr-v5cw", "cve": "CVE-2023-25662", "id": "pyup.io-55905", "more_info_path": "/vulnerabilities/CVE-2023-25662/55905", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25660: Prior to versions 2.12.0 and 2.11.1, when the parameter 'summarize' of 'tf.raw_ops.Print' is zero, the new method 'SummarizeArray' will reference to a nullptr, leading to a seg fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qjqc-vqcf-5qvj", "cve": "CVE-2023-25660", "id": "pyup.io-55906", "more_info_path": "/vulnerabilities/CVE-2023-25660/55906", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25658: Prior to versions 2.12.0 and 2.11.1, an out of bounds read is in GRUBlockCellGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-68v3-g9cm-rmm6", "cve": "CVE-2023-25658", "id": "pyup.io-55908", "more_info_path": "/vulnerabilities/CVE-2023-25658/55908", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25663: Prior to versions 2.12.0 and 2.11.1, when 'ctx->step_containter()' is a null ptr, the Lookup function will be executed with a null pointer.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-64jg-wjww-7c5w", "cve": "CVE-2023-25663", "id": "pyup.io-55904", "more_info_path": "/vulnerabilities/CVE-2023-25663/55904", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25673: Versions prior to 2.12.0 and 2.11.1 have a Floating Point Exception in TensorListSplit with XLA. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25673", "id": "pyup.io-55888", "more_info_path": "/vulnerabilities/CVE-2023-25673/55888", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25674: Versions prior to 2.12.0 and 2.11.1 have a null pointer error in RandomShuffle with XLA enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf97-q72m-7579", "cve": "CVE-2023-25674", "id": "pyup.io-55893", "more_info_path": "/vulnerabilities/CVE-2023-25674/55893", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25801: Prior to versions 2.12.0 and 2.11.1, 'nn_ops.fractional_avg_pool_v2' and 'nn_ops.fractional_max_pool_v2' require the first and fourth elements of their parameter 'pooling_ratio' to be equal to 1.0, as pooling on batch and channel dimensions is not supported.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f49c-87jh-g47q", "cve": "CVE-2023-25801", "id": "pyup.io-55895", "more_info_path": "/vulnerabilities/CVE-2023-25801/55895", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25675: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.Bincount' segfaults when given a parameter 'weights' that is neither the same shape as parameter 'arr' nor a length-0 tensor.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7x4v-9gxg-9hwj", "cve": "CVE-2023-25675", "id": "pyup.io-55896", "more_info_path": "/vulnerabilities/CVE-2023-25675/55896", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25668: Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gw97-ff7c-9v96", "cve": "CVE-2023-25668", "id": "pyup.io-55902", "more_info_path": "/vulnerabilities/CVE-2023-25668/55902", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-gpu 2.11.1 and 2.12.0 include a fix for CVE-2023-25659: Prior to versions 2.12.0 and 2.11.1, if the parameter 'indices' for 'DynamicStitch' does not match the shape of the parameter 'data', it can trigger an stack OOB read.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-93vr-9q9m-pj8p", "cve": "CVE-2023-25659", "id": "pyup.io-55907", "more_info_path": "/vulnerabilities/CVE-2023-25659/55907", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Integer Overflow. array_ops.upper_bound' causes a segfault when not given a rank 2 tensor. The flaw was fixed in May 30, 2023, but the CVE was published in July 30, 2024. It was noticed unpublished by the Safety CLI Cyber Security team.", "cve": "CVE-2023-33976", "id": "pyup.io-72426", "more_info_path": "/vulnerabilities/CVE-2023-33976/72426", "specs": [ "<2.12.1", ">=2.13.0rc0,<2.13.0" ], "v": "<2.12.1,>=2.13.0rc0,<2.13.0" }, { "advisory": "TensorFlow-GPU uses a version of curl vulnerable to CVE-2023-38545.", "cve": "CVE-2023-38545", "id": "pyup.io-72615", "more_info_path": "/vulnerabilities/CVE-2023-38545/72615", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "TensorFlow-GPU updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38546.", "cve": "CVE-2023-38546", "id": "pyup.io-72614", "more_info_path": "/vulnerabilities/CVE-2023-38546/72614", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "Tensorflow-gpu 2.4.0 includes a fix for CVE-2020-15265: In Tensorflow before version 2.4.0, an attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`. This results in accessing a dimension outside the rank of the input tensor in the C++ kernel implementation. However, dim_size only does a DCHECK to validate the argument and then uses it to access the corresponding element of an array. Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.", "cve": "CVE-2020-15265", "id": "pyup.io-56310", "more_info_path": "/vulnerabilities/CVE-2020-15265/56310", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Tensorflow-gpu 2.4.0 includes a fix for CVE-2020-15266: In Tensorflow before version 2.4.0, when the 'boxes' argument of 'tf.image.crop_and_resize' has a very large value, the CPU kernel implementation receives it as a C++ 'nan' floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault.\nhttps://github.com/tensorflow/tensorflow/issues/42129\nhttps://github.com/tensorflow/tensorflow/pull/42143/commits/3ade2efec2e90c6237de32a19680caaa3ebc2845\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xwhf-g6j5-j5gc", "cve": "CVE-2020-15266", "id": "pyup.io-56308", "more_info_path": "/vulnerabilities/CVE-2020-15266/56308", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41217: In affected versions, the process of building the control flow graph for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not. This occurs because the code assumes that the first node in the pairing (e.g., an 'Enter' node) always exists when encountering the second node (e.g., an 'Exit' node). When this is not the case, 'parent' is 'nullptr' so dereferencing it causes a crash. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5crj-c72x-m7gq\nhttps://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff", "cve": "CVE-2021-41217", "id": "pyup.io-56100", "more_info_path": "/vulnerabilities/CVE-2021-41217/56100", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22923.", "cve": "CVE-2021-22923", "id": "pyup.io-56105", "more_info_path": "/vulnerabilities/CVE-2021-22923/56105", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22926.", "cve": "CVE-2021-22926", "id": "pyup.io-56096", "more_info_path": "/vulnerabilities/CVE-2021-22926/56096", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22925.", "cve": "CVE-2021-22925", "id": "pyup.io-56087", "more_info_path": "/vulnerabilities/CVE-2021-22925/56087", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22924.", "cve": "CVE-2021-22924", "id": "pyup.io-56104", "more_info_path": "/vulnerabilities/CVE-2021-22924/56104", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41216: In affected versions, the shape inference function for 'Transpose' is vulnerable to a heap buffer overflow. This occurs whenever 'perm' contains negative elements. The shape inference function does not validate that the indices in 'perm' are all valid. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3ff2-r28g-w7h9\nhttps://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14", "cve": "CVE-2021-41216", "id": "pyup.io-56106", "more_info_path": "/vulnerabilities/CVE-2021-41216/56106", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41201: In affected versions, during execution, 'EinsumHelper::ParseEquation()' is supposed to set the flags in 'input_has_ellipsis' vector and '*output_has_ellipsis' boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to 'true' and never assigns 'false'. This results in unitialized variable access if callers assume that 'EinsumHelper::ParseEquation()' always sets these flags. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j86v-p27c-73fm\nhttps://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6", "cve": "CVE-2021-41201", "id": "pyup.io-56092", "more_info_path": "/vulnerabilities/CVE-2021-41201/56092", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41218: In affected versions, the shape inference code for 'AllToAll' can be made to execute a division by 0. This occurs whenever the 'split_count' argument is 0. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9crf-c6qr-r273\nhttps://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc", "cve": "CVE-2021-41218", "id": "pyup.io-56090", "more_info_path": "/vulnerabilities/CVE-2021-41218/56090", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41223: In affected versions, the implementation of 'FusedBatchNorm' kernels is vulnerable to a heap OOB access. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f54p-f6jp-4rhr\nhttps://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda", "cve": "CVE-2021-41223", "id": "pyup.io-56098", "more_info_path": "/vulnerabilities/CVE-2021-41223/56098", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41219: In affected versions, the code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to 'nullptr'. This occurs whenever the dimensions of 'a' or 'b' are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, it should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4f99-p9c2-3j8x\nhttps://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae", "cve": "CVE-2021-41219", "id": "pyup.io-56103", "more_info_path": "/vulnerabilities/CVE-2021-41219/56103", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41205: In affected versions, the shape inference functions for the 'QuantizeAndDequantizeV*' operations can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rx-x2rw-pc6f\nhttps://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d", "cve": "CVE-2021-41205", "id": "pyup.io-56101", "more_info_path": "/vulnerabilities/CVE-2021-41205/56101", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41214: In affected versions, the shape inference code for 'tf.ragged.cross' has an undefined behavior due to binding a reference to 'nullptr'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vwhq-49r4-gj9v\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41214", "id": "pyup.io-56102", "more_info_path": "/vulnerabilities/CVE-2021-41214/56102", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41204: In affected versions, during TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-786j-5qwq-r36x\nhttps://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659", "cve": "CVE-2021-41204", "id": "pyup.io-56109", "more_info_path": "/vulnerabilities/CVE-2021-41204/56109", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41213: In affected versions, the code behind 'tf.function' API can be made to deadlock when two 'tf.function' decorated Python functions are mutually recursive. This occurs due to using a non-reentrant 'Lock' Python object. Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive 'tf.function', although this is not a frequent scenario.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcf\nhttps://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7", "cve": "CVE-2021-41213", "id": "pyup.io-56113", "more_info_path": "/vulnerabilities/CVE-2021-41213/56113", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41225: In affected versions, TensorFlow's Grappler optimizer has a use of unitialized variable. If the 'train_nodes' vector (obtained from the saved model that gets optimized) does not contain a 'Dequeue' node, then 'dequeue_node' is left unitialized. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7r94-xv9v-63jw\nhttps://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3", "cve": "CVE-2021-41225", "id": "pyup.io-56118", "more_info_path": "/vulnerabilities/CVE-2021-41225/56118", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41198: In affected versions, if 'tf.tile' is called with a large input argument, then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2p25-55c9-h58q", "cve": "CVE-2021-41198", "id": "pyup.io-56119", "more_info_path": "/vulnerabilities/CVE-2021-41198/56119", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41215: In affected versions, the shape inference code for 'DeserializeSparse' can trigger a null pointer dereference. This is because the shape inference function assumes that the 'serialize_sparse' tensor is a tensor with positive rank (and having '3' as the last dimension). The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x3v8-c8qx-3j3r\nhttps://github.com/tensorflow/tensorflow/commit/d3738dd70f1c9ceb547258cbb82d853da8771850", "cve": "CVE-2021-41215", "id": "pyup.io-56097", "more_info_path": "/vulnerabilities/CVE-2021-41215/56097", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41200: In affected versions, if 'tf.summary.create_file_writer' is called with non-scalar arguments, code crashes due to a 'CHECK'-fail. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh8h-7j2j-qv4f", "cve": "CVE-2021-41200", "id": "pyup.io-56115", "more_info_path": "/vulnerabilities/CVE-2021-41200/56115", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41221: In affected versions, the shape inference code for the 'Cudnn*' operations can be tricked into accessing invalid memory via a heap buffer overflow. This occurs because the ranks of the 'input', 'input_h' and 'input_c' parameters are not validated, but code assumes they have certain values. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqv6-3phm-hcwx\nhttps://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6", "cve": "CVE-2021-41221", "id": "pyup.io-56116", "more_info_path": "/vulnerabilities/CVE-2021-41221/56116", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41226: In affected versions, the implementation of 'SparseBinCount' is vulnerable to a heap OOB access. This is because of missing validation between the elements of the 'values' argument and the shape of the sparse output. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-374m-jm66-3vj8\nhttps://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba", "cve": "CVE-2021-41226", "id": "pyup.io-56110", "more_info_path": "/vulnerabilities/CVE-2021-41226/56110", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41224: In affected versions, the implementation of 'SparseFillEmptyRows' can be made to trigger a heap OOB access. This occurs whenever the size of 'indices' does not match the size of 'values'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rg3m-hqc5-344v\nhttps://github.com/tensorflow/tensorflow/commit/67bfd9feeecfb3c61d80f0e46d89c170fbee682b", "cve": "CVE-2021-41224", "id": "pyup.io-56099", "more_info_path": "/vulnerabilities/CVE-2021-41224/56099", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41212: In affected versions, the shape inference code for 'tf.ragged.cross' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fr77-rrx3-cp7g\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41212", "id": "pyup.io-56117", "more_info_path": "/vulnerabilities/CVE-2021-41212/56117", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41195: In affected versions, the implementation of 'tf.math.segment_*' operations results in a 'CHECK'-fail related abort (and denial of service) if a segment id in 'segment_ids' is large. This is similar to CVE-2021-29584 (and similar to other reported vulnerabilities in TensorFlow localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using 'AddDim'. However, if the number of elements in the tensor overflows an 'int64_t' value, 'AddDim' results in a 'CHECK' failure which provokes a 'std::abort'. Instead, code should use 'AddDimWithStatus'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cq76-mxrc-vchh", "cve": "CVE-2021-41195", "id": "pyup.io-56094", "more_info_path": "/vulnerabilities/CVE-2021-41195/56094", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41222: In affected versions, the implementation of 'SplitV' can trigger a segfault if an attacker supplies negative arguments. This occurs whenever 'size_splits' contains more than one value and at least one value is negative. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cpf4-wx82-gxp6\nhttps://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6", "cve": "CVE-2021-41222", "id": "pyup.io-56114", "more_info_path": "/vulnerabilities/CVE-2021-41222/56114", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41210: In affected versions, the shape inference functions for 'SparseCountSparseOutput' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m342-ff57-4jcc\r\nhttps://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2", "cve": "CVE-2021-41210", "id": "pyup.io-56120", "more_info_path": "/vulnerabilities/CVE-2021-41210/56120", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41228: In affected versions, TensorFlow's 'saved_model_cli' tool is vulnerable to a code injection as it calls 'eval' on user supplied strings. This can be used by attackers to run arbitrary code on the plaform where the CLI tool runs. However, given that the tool is always run manually, the impact of this is not severe. The issue has been patched by adding a 'safe' flag which defaults to 'True' and an explicit warning for users.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3rcw-9p9x-582v\nhttps://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7", "cve": "CVE-2021-41228", "id": "pyup.io-56095", "more_info_path": "/vulnerabilities/CVE-2021-41228/56095", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41227: In affected versions, the 'ImmutableConst' operation in TensorFlow can be tricked into reading arbitrary memory contents. This is because the 'tstring' TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j8c8-67vp-6mx7\nhttps://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b\nhttps://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585", "cve": "CVE-2021-41227", "id": "pyup.io-56089", "more_info_path": "/vulnerabilities/CVE-2021-41227/56089", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41209: In affected versions, the implementations for convolution operators trigger a division by 0 if passed empty filter tensor arguments. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hpv-v2rx-c5g6\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41209", "id": "pyup.io-56093", "more_info_path": "/vulnerabilities/CVE-2021-41209/56093", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41207: In affected versions, the implementation of 'ParallelConcat' misses some input validation and can produce a division by 0. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7v94-64hj-m82h\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41207", "id": "pyup.io-56107", "more_info_path": "/vulnerabilities/CVE-2021-41207/56107", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41202: In affected versions, while calculating the size of the output within the 'tf.range' kernel, there is a conditional statement of type 'int64 = condition ? int64 : double'. Due to C++ implicit conversion rules, both branches of the condition will be cast to 'double' and the result would be truncated before the assignment. This result in overflows. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xrqm-fpgr-6hhx", "cve": "CVE-2021-41202", "id": "pyup.io-56108", "more_info_path": "/vulnerabilities/CVE-2021-41202/56108", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41203: In affected versions, an attacker can trigger undefined behavior, integer overflows, segfaults and 'CHECK'-fail crashes if they can change saved checkpoints from outside of TensorFlow. This is because the checkpoints loading infrastructure is missing validation for invalid file formats.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7pxj-m4jf-r6h2", "cve": "CVE-2021-41203", "id": "pyup.io-56112", "more_info_path": "/vulnerabilities/CVE-2021-41203/56112", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41199: In affected versions, if 'tf.image.resize' is called with a large input argument then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hx2-qx8j-qjqm", "cve": "CVE-2021-41199", "id": "pyup.io-56111", "more_info_path": "/vulnerabilities/CVE-2021-41199/56111", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41196: In affected versions, the Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative. This is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m539-j985-hcr8", "cve": "CVE-2021-41196", "id": "pyup.io-56091", "more_info_path": "/vulnerabilities/CVE-2021-41196/56091", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22922.", "cve": "CVE-2021-22922", "id": "pyup.io-56088", "more_info_path": "/vulnerabilities/CVE-2021-22922/56088", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Affected versions of Tensorflow-Gpu allow tensors to have a large number of dimensions and each dimension can be as large as desired. However, the total number of elements in a tensor must fit within an 'int64_t'. If an overflow occurs, 'MultiplyWithoutOverflow' would return a negative result. In the majority of TensorFlow codebase this then results in a 'CHECK'-failure. Newer constructs exist which return a 'Status' instead of crashing the binary. This is a similar issue to CVE-2021-29584.", "cve": "CVE-2021-41197", "id": "pyup.io-71513", "more_info_path": "/vulnerabilities/CVE-2021-41197/71513", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1", ">=2.7.0rc0,<2.7.0" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1,>=2.7.0rc0,<2.7.0" }, { "advisory": "The Grappler component within TensorFlow has a vulnerability that may result in a denial of service. The flaw arises from the use of `CHECK`-failure in constant folding. This is linked to the `output_prop` tensor, which takes on a shape influenced by user input, thus potentially activating one of the `CHECK`s in the `PartialTensorShape` constructor.\r\n\r\nThis issue is identified as TFSA-2021-198.\r\n\r\nFor remediation, a modification has been made to solve this problem is in the GitHub commit be7b286d40bc68cb0b56f702186cc4837d508058. This fix will be seen in the TensorFlow 2.8.0 release. Retroactive solutions will also be applied to TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these versions are also vulnerable and continue to be within the supported range. \r\n\r\nFor a comprehensive understanding of our security protocol or to share issues and ask questions, please refer to our security guide.", "cve": "PVE-2023-99919", "id": "pyup.io-61992", "more_info_path": "/vulnerabilities/PVE-2023-99919/61992", "specs": [ "<2.5.3", "==2.7.0", ">=2.6.0,<2.6.3" ], "v": "<2.5.3,==2.7.0,>=2.6.0,<2.6.3" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3 and 2.7.1 update its dependency 'icu' to v69.1 to include a security fix.", "cve": "CVE-2020-10531", "id": "pyup.io-56034", "more_info_path": "/vulnerabilities/CVE-2020-10531/56034", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21737: The implementation of '*Bincount' operations allows malicious users to cause denial of service by passing in arguments which would trigger a 'CHECK'-fail. There are several conditions that the input arguments must satisfy. Some are not caught during shape inference and others are not caught during kernel implementation. This results in 'CHECK' failures later when the output tensors get allocated.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2vv-v9cg-qhh7", "cve": "CVE-2022-21737", "id": "pyup.io-56051", "more_info_path": "/vulnerabilities/CVE-2022-21737/56051", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23581: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'IsSimplifiableReshape' would trigger 'CHECK' failures.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fq86-3f29-px2c", "cve": "CVE-2022-23581", "id": "pyup.io-56050", "more_info_path": "/vulnerabilities/CVE-2022-23581/56050", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21727: The implementation of shape inference for 'Dequantize' is vulnerable to an integer overflow weakness. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked, and, since the code computes 'axis + 1', an attacker can trigger an integer overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c6fh-56w7-fvjw", "cve": "CVE-2022-21727", "id": "pyup.io-56061", "more_info_path": "/vulnerabilities/CVE-2022-21727/56061", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. When decoding PNG images TensorFlow can produce a memory leak if the image is invalid. After calling `png::CommonInitDecode(..., &decode)`, the `decode` value contains allocated buffers which can only be freed by calling `png::CommonFreeDecode(&decode)`. However, several error case in the function implementation invoke the `OP_REQUIRES` macro which immediately terminates the execution of the function, without allowing for the memory free to occur. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23585", "id": "pyup.io-56044", "more_info_path": "/vulnerabilities/CVE-2022-23585/56044", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23557: An attacker can craft a TFLite model that would trigger a division by zero in 'BiasAndClamp' implementation. There is no check that the 'bias_size' is non zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf2j-f278-xh4v", "cve": "CVE-2022-23557", "id": "pyup.io-56069", "more_info_path": "/vulnerabilities/CVE-2022-23557/56069", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. A malicious user can cause a use after free behavior when decoding PNG images. After `png::CommonFreeDecode(&decode)` gets called, the values of `decode.width` and `decode.height` are in an unspecified state. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23584", "id": "pyup.io-56082", "more_info_path": "/vulnerabilities/CVE-2022-23584/56082", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23559: An attacker can craft a TFLite model that would cause an integer overflow in embedding lookup operations. Both 'embedding_size' and 'lookup_size' are products of values provided by the user. Hence, a malicious user could trigger overflows in the multiplication. In certain scenarios, this can then result in heap OOB read/write.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98p5-x8x4-c9m5", "cve": "CVE-2022-23559", "id": "pyup.io-56058", "more_info_path": "/vulnerabilities/CVE-2022-23559/56058", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21729: The implementation of 'UnravelIndex' is vulnerable to a division by zero caused by an integer overflow bug.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-34f9-hjfq-rr8j", "cve": "CVE-2022-21729", "id": "pyup.io-56059", "more_info_path": "/vulnerabilities/CVE-2022-21729/56059", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateOutputSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve tensors with large enough number of elements. We can have a large enough number of dimensions in `output_shape.dim()` or just a small number of dimensions being large enough to cause an overflow in the multiplication. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23576", "id": "pyup.io-56045", "more_info_path": "/vulnerabilities/CVE-2022-23576/56045", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23567: The implementations of 'Sparse*Cwise*' ops are vulnerable to integer overflows. These can be used to trigger large allocations (so, OOM based denial of service) or 'CHECK'-fails when building new 'TensorShape' objects (so, assert failures based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rrx2-r989-2c43", "cve": "CVE-2022-23567", "id": "pyup.io-56056", "more_info_path": "/vulnerabilities/CVE-2022-23567/56056", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23568: The implementation of 'AddManySparseToTensorsMap' is vulnerable to an integer overflow which results in a 'CHECK'-fail when building new 'TensorShape' objects (so, an assert failure based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6445-fm66-fvq2", "cve": "CVE-2022-23568", "id": "pyup.io-56035", "more_info_path": "/vulnerabilities/CVE-2022-23568/56035", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23595: When building an XLA compilation cache, if default settings are used, TensorFlow triggers a null pointer dereference. In the default scenario, all devices are allowed, so 'flr->config_proto' is 'nullptr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fpcp-9h7m-ffpx", "cve": "CVE-2022-23595", "id": "pyup.io-56040", "more_info_path": "/vulnerabilities/CVE-2022-23595/56040", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. The 'GraphDef' format in TensorFlow does not allow self recursive functions. The runtime assumes that this invariant is satisfied. However, a 'GraphDef' containing a fragment such as the following can be consumed when loading a 'SavedModel'. This would result in a stack overflow during execution as resolving each 'NodeDef' means resolving the function itself and its nodes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23591", "id": "pyup.io-56074", "more_info_path": "/vulnerabilities/CVE-2022-23591/56074", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow can trigger a null pointer dereference. There are 2 places where this can occur, for the same malicious alteration of a `SavedModel` file (fixing the first one would trigger the same dereference in the second place). First, during constant folding, the `GraphDef` might not have the required nodes for the binary operation. If a node is missing, the correposning `mul_*child` would be null, and the dereference in the subsequent line would be incorrect. We have a similar issue during `IsIdentityConsumingSwitch`. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23589", "id": "pyup.io-56049", "more_info_path": "/vulnerabilities/CVE-2022-23589/56049", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that Grappler optimizer would attempt to build a tensor using a reference `dtype`. This would result in a crash due to a `CHECK`-fail in the `Tensor` constructor as reference types are not allowed. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23588", "id": "pyup.io-56081", "more_info_path": "/vulnerabilities/CVE-2022-23588/56081", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow is vulnerable to an integer overflow during cost estimation for crop and resize. Since the cropping parameters are user controlled, a malicious person can trigger undefined behavior. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23587", "id": "pyup.io-56066", "more_info_path": "/vulnerabilities/CVE-2022-23587/56066", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that assertions in `function.cc` would be falsified and crash the Python interpreter. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23586", "id": "pyup.io-56060", "more_info_path": "/vulnerabilities/CVE-2022-23586/56060", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a 'SavedModel' such that any binary op would trigger 'CHECK' failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the 'dtype' no longer matches the 'dtype' expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If 'Tin' and 'Tout' don't match the type of data in 'out' and 'input_*' tensors then 'flat<*>' would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a 'CHECK' crash, hence a denial of service. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23583", "id": "pyup.io-56046", "more_info_path": "/vulnerabilities/CVE-2022-23583/56046", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23582: A malicious user can cause a denial of service by altering a 'SavedModel' such that 'TensorByteSize' would trigger 'CHECK' failures. 'TensorShape' constructor throws a 'CHECK'-fail if shape is partial or has a number of elements that would overflow the size of an 'int'. The 'PartialTensorShape' constructor instead does not cause a 'CHECK'-abort if the shape is partial, which is exactly what this function needs to be able to return '-1'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4j82-5ccr-4r8v", "cve": "CVE-2022-23582", "id": "pyup.io-56083", "more_info_path": "/vulnerabilities/CVE-2022-23582/56083", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23580: During shape inference, TensorFlow can allocate a large vector based on a value from a tensor controlled by the user.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-627q-g293-49q7", "cve": "CVE-2022-23580", "id": "pyup.io-56072", "more_info_path": "/vulnerabilities/CVE-2022-23580/56072", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23579: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'SafeToRemoveIdentity' would trigger 'CHECK' failures.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5f2r-qp73-37mr", "cve": "CVE-2022-23579", "id": "pyup.io-56078", "more_info_path": "/vulnerabilities/CVE-2022-23579/56078", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. If a graph node is invalid, TensorFlow can leak memory in the implementation of `ImmutableExecutorState::Initialize`. Here, we set `item->kernel` to `nullptr` but it is a simple `OpKernel*` pointer so the memory that was previously allocated to it would leak. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23578", "id": "pyup.io-56048", "more_info_path": "/vulnerabilities/CVE-2022-23578/56048", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. The implementation of `GetInitOp` is vulnerable to a crash caused by dereferencing a null pointer. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23577", "id": "pyup.io-56073", "more_info_path": "/vulnerabilities/CVE-2022-23577/56073", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21731: The implementation of shape inference for 'ConcatV2' can be used to trigger a denial of service attack via a segfault caused by a type confusion. The 'axis' argument is translated into 'concat_dim' in the 'ConcatShapeHelper' helper function. Then, a value for 'min_rank' is computed based on 'concat_dim'. This is then used to validate that the 'values' tensor has at least the required rank. However, 'WithRankAtLeast' receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented. Due to the fact that 'min_rank' is a 32-bits value and the value of 'axis', the 'rank' argument is a negative value, so the error check is bypassed.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m4hf-j54p-p353", "cve": "CVE-2022-21731", "id": "pyup.io-56086", "more_info_path": "/vulnerabilities/CVE-2022-21731/56086", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21738: The implementation of 'SparseCountSparseOutput' can be made to crash a TensorFlow process by an integer overflow whose result is then used in a memory allocation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x4qx-4fjv-hmw6", "cve": "CVE-2022-21738", "id": "pyup.io-56080", "more_info_path": "/vulnerabilities/CVE-2022-21738/56080", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21740: The implementation of 'SparseCountSparseOutput' is vulnerable to a heap overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-44qp-9wwf-734r", "cve": "CVE-2022-21740", "id": "pyup.io-56076", "more_info_path": "/vulnerabilities/CVE-2022-21740/56076", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21739: The implementation of 'QuantizedMaxPool' has an undefined behavior where user controlled inputs can trigger a reference binding to null pointer.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3mw4-6rj6-74g5", "cve": "CVE-2022-21739", "id": "pyup.io-56057", "more_info_path": "/vulnerabilities/CVE-2022-21739/56057", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21736: The implementation of 'SparseTensorSliceDataset' has an undefined behavior: under certain conditions, it can be made to dereference a 'nullptr' value. The 3 input arguments to 'SparseTensorSliceDataset' represent a sparse tensor. However, there are some preconditions that these arguments must satisfy, but these are not validated in the implementation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pfjj-m3jj-9jc9", "cve": "CVE-2022-21736", "id": "pyup.io-56039", "more_info_path": "/vulnerabilities/CVE-2022-21736/56039", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21730: The implementation of 'FractionalAvgPoolGrad' does not consider cases where the input tensors are invalid allowing an attacker to read from outside of bounds of heap.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vjg4-v33c-ggc4", "cve": "CVE-2022-21730", "id": "pyup.io-56038", "more_info_path": "/vulnerabilities/CVE-2022-21730/56038", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21728: The implementation of shape inference for 'ReverseSequence' does not fully validate the value of 'batch_dim' and can result in a heap OOB read. There is a check to make sure the value of 'batch_dim' does not go over the rank of the input, but there is no check for negative values. Negative dimensions are allowed in some cases to mimic Python's negative indexing (i.e., indexing from the end of the array), however if the value is too negative then the implementation of 'Dim' would access elements before the start of an array.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6gmv-pjp9-p8w8", "cve": "CVE-2022-21728", "id": "pyup.io-56036", "more_info_path": "/vulnerabilities/CVE-2022-21728/56036", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateTensorSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve a tensor with large enough number of elements. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23575", "id": "pyup.io-56054", "more_info_path": "/vulnerabilities/CVE-2022-23575/56054", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. There is a typo in TensorFlow's `SpecializeType` which results in heap OOB read/write. Due to a typo, `arg` is initialized to the `i`th mutable argument in a loop where the loop index is `j`. Hence it is possible to assign to `arg` from outside the vector of arguments. Since this is a mutable proto value, it allows both read and write to outside of bounds data. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23574", "id": "pyup.io-56052", "more_info_path": "/vulnerabilities/CVE-2022-23574/56052", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized data to a new tensor. This later results in undefined behavior. The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23573", "id": "pyup.io-56047", "more_info_path": "/vulnerabilities/CVE-2022-23573/56047", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, TensorFlow can fail to specialize a type during shape inference. This case is covered by the 'DCHECK' function however, 'DCHECK' is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the 'ValueOrDie' line. This results in an assertion failure as 'ret' contains an error 'Status', not a value. In the second case we also get a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23572", "id": "pyup.io-56070", "more_info_path": "/vulnerabilities/CVE-2022-23572/56070", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23571", "id": "pyup.io-56062", "more_info_path": "/vulnerabilities/CVE-2022-23571/56062", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, TensorFlow might do a null-dereference if attributes of some mutable arguments to some operations are missing from the proto. This is guarded by a `DCHECK`. However, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the dereferencing of the null pointer, whereas in the second case it results in a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23570", "id": "pyup.io-56042", "more_info_path": "/vulnerabilities/CVE-2022-23570/56042", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. TensorFlow is vulnerable to a heap OOB write in `Grappler`. The `set_output` function writes to an array at the specified index. Hence, this gives a malicious user a write primitive. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23566", "id": "pyup.io-56077", "more_info_path": "/vulnerabilities/CVE-2022-23566/56077", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23565: An attacker can trigger denial of service via assertion failure by altering a 'SavedModel' on disk such that 'AttrDef's of some operation are duplicated.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4v5p-v5h9-6xjx", "cve": "CVE-2022-23565", "id": "pyup.io-56071", "more_info_path": "/vulnerabilities/CVE-2022-23565/56071", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23564: When decoding a resource handle tensor from protobuf, a TensorFlow process can encounter cases where a 'CHECK' assertion is invalidated based on user controlled arguments. This allows attackers to cause denial of services in TensorFlow processes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8rcj-c8pj-v3m3", "cve": "CVE-2022-23564", "id": "pyup.io-56063", "more_info_path": "/vulnerabilities/CVE-2022-23564/56063", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23563: In multiple places, TensorFlow uses 'tempfile.mktemp' to create temporary files. While this is acceptable in testing, in utilities and libraries it is dangerous as a different process can create the file between the check for the filename in 'mktemp' and the actual creation of the file by a subsequent operation (a TOC/TOU type of weakness). In several instances, TensorFlow was supposed to actually create a temporary directory instead of a file. This logic bug is hidden away by the 'mktemp' function usage. It was replaced 'mktemp' with the safer 'mkstemp'/'mkdtemp' functions, according to the usage pattern.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wc4g-r73w-x8mm", "cve": "CVE-2022-23563", "id": "pyup.io-56037", "more_info_path": "/vulnerabilities/CVE-2022-23563/56037", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23562: The implementation of 'Range' suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qx3f-p745-w4hr", "cve": "CVE-2022-23562", "id": "pyup.io-56079", "more_info_path": "/vulnerabilities/CVE-2022-23562/56079", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23561: An attacker can craft a TFLite model that would cause a write outside of bounds of an array in TFLite. In fact, the attacker can override the linked list used by the memory allocator. This can be leveraged for an arbitrary write primitive under certain conditions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9c78-vcq7-7vxq", "cve": "CVE-2022-23561", "id": "pyup.io-56085", "more_info_path": "/vulnerabilities/CVE-2022-23561/56085", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23560: An attacker can craft a TFLite model that would allow limited reads and writes outside of arrays in TFLite. This exploits missing validation in the conversion from sparse tensors to dense tensors.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4hvf-hxvg-f67v", "cve": "CVE-2022-23560", "id": "pyup.io-56065", "more_info_path": "/vulnerabilities/CVE-2022-23560/56065", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23558: An attacker can craft a TFLite model that would cause an integer overflow in 'TfLiteIntArrayCreate'. The 'TfLiteIntArrayGetSizeInBytes' returns an 'int' instead of a 'size_t'. An attacker can control model inputs such that 'computed_size' overflows the size of 'int' datatype.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9gwq-6cwj-47h3", "cve": "CVE-2022-23558", "id": "pyup.io-56055", "more_info_path": "/vulnerabilities/CVE-2022-23558/56055", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21735: The implementation of 'FractionalMaxPool' can be made to crash a TensorFlow process via a division by 0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-87v6-crgm-2gfj", "cve": "CVE-2022-21735", "id": "pyup.io-56068", "more_info_path": "/vulnerabilities/CVE-2022-21735/56068", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21732: The implementation of 'ThreadPoolHandle' can be used to trigger a denial of service attack by allocating too much memory. This is because the 'num_threads' argument is only checked to not be negative, but there is no upper bound on its value.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c582-c96p-r5cq", "cve": "CVE-2022-21732", "id": "pyup.io-56075", "more_info_path": "/vulnerabilities/CVE-2022-21732/56075", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21726: The implementation of 'Dequantize' does not fully validate the value of 'axis' and can result in heap OOB accesses. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked and this results in reading past the end of the array containing the dimensions of the input tensor.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-23hm-7w47-xw72", "cve": "CVE-2022-21726", "id": "pyup.io-56084", "more_info_path": "/vulnerabilities/CVE-2022-21726/56084", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21734: The implementation of 'MapStage' is vulnerable to a 'CHECK'-fail if the key tensor is not a scalar.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gcvh-66ff-4mwm", "cve": "CVE-2022-21734", "id": "pyup.io-56043", "more_info_path": "/vulnerabilities/CVE-2022-21734/56043", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21741: An attacker can craft a TFLite model that would trigger a division by zero in the implementation of depthwise convolutions. The parameters of the convolution can be user controlled and are also used within a division operation to determine the size of the padding that needs to be added before applying the convolution. There is no check before this division that the divisor is strictly positive.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-428x-9xc2-m8mj", "cve": "CVE-2022-21741", "id": "pyup.io-56041", "more_info_path": "/vulnerabilities/CVE-2022-21741/56041", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23569: Multiple operations in TensorFlow can be used to trigger a denial of service via 'CHECK'-fails (i.e., assertion failures). This is similar to CVE-2021-41197 and has a similar fix. It is possible that other similar instances exist.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qj5r-f9mv-rffh", "cve": "CVE-2022-23569", "id": "pyup.io-56053", "more_info_path": "/vulnerabilities/CVE-2022-23569/56053", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21725: The estimator for the cost of some convolution operations can be made to execute a division by 0. The function fails to check that the stride argument is strictly positive. Hence, the fix is to add a check for the stride argument to ensure it is valid.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v3f7-j968-4h5f", "cve": "CVE-2022-21725", "id": "pyup.io-56067", "more_info_path": "/vulnerabilities/CVE-2022-21725/56067", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21733: The implementation of 'StringNGrams' can be used to trigger a denial of service attack by causing an out of memory condition after an integer overflow. There is missing a validation on 'pad_witdh' and that result in computing a negative value for 'ngram_width' which is later used to allocate parts of the output.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98j8-c9q4-r38g", "cve": "CVE-2022-21733", "id": "pyup.io-56064", "more_info_path": "/vulnerabilities/CVE-2022-21733/56064", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41206: In affected versions, several TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or 'CHECK'-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible. These issues were discovered internally via tooling while working on improving/testing GPU op determinism. As such, there aren't reproducers and there will be multiple fixes for these issues.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pgcq-h79j-2f69\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-43q8-3fv7-pr5x", "cve": "CVE-2021-41206", "id": "pyup.io-56032", "more_info_path": "/vulnerabilities/CVE-2021-41206/56032", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Tensorflow-gpu versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41208: In affected versions, the code for boosted trees in TensorFlow is still missing validation. As a result, attackers can trigger denial of service (via dereferencing 'nullptr's or via 'CHECK'-failures) as well as abuse undefined behavior (binding references to 'nullptr's). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call. Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. TensorFlow's boosted trees APIs will be deprecated in subsequent releases.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-57wx-m983-2f88\nhttps://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6gw-r52c-724r", "cve": "CVE-2021-41208", "id": "pyup.io-56033", "more_info_path": "/vulnerabilities/CVE-2021-41208/56033", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Affected versions of Tensorflow-Gpu are vulnerable to Denial of Service via CHECK-failure (assertion failure) in constant folding. The output_prop tensor has a shape that is controlled by user input and this can result in triggering one of the CHECKs in the PartialTensorShape constructor. This is an instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71510", "id": "pyup.io-71515", "more_info_path": "/vulnerabilities/PVE-2024-71510/71515", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1", ">=2.8.0rc0,<2.8.0" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1,>=2.8.0rc0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27780.", "cve": "CVE-2022-27780", "id": "pyup.io-56019", "more_info_path": "/vulnerabilities/CVE-2022-27780/56019", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27779.", "cve": "CVE-2022-27779", "id": "pyup.io-56008", "more_info_path": "/vulnerabilities/CVE-2022-27779/56008", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27778.", "cve": "CVE-2022-27778", "id": "pyup.io-56007", "more_info_path": "/vulnerabilities/CVE-2022-27778/56007", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27776.", "cve": "CVE-2022-27776", "id": "pyup.io-55996", "more_info_path": "/vulnerabilities/CVE-2022-27776/55996", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27775.", "cve": "CVE-2022-27775", "id": "pyup.io-55993", "more_info_path": "/vulnerabilities/CVE-2022-27775/55993", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'zlib' to v1.2.12 to handle CVE-2018-25032.", "cve": "CVE-2018-25032", "id": "pyup.io-56011", "more_info_path": "/vulnerabilities/CVE-2018-25032/56011", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27774.", "cve": "CVE-2022-27774", "id": "pyup.io-56006", "more_info_path": "/vulnerabilities/CVE-2022-27774/56006", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-22576.", "cve": "CVE-2022-22576", "id": "pyup.io-56023", "more_info_path": "/vulnerabilities/CVE-2022-22576/56023", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Affected versions of Tensorflow-Gpu are vulnerable to Denial of Service in the implementation of depthwise ops via CHECK-failure (assertion failure) caused by overflowing the number of elements in a tensor. This is another instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71511", "id": "pyup.io-71517", "more_info_path": "/vulnerabilities/PVE-2024-71511/71517", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29216: Code injection in 'saved_model_cli'.", "cve": "CVE-2022-29216", "id": "pyup.io-55994", "more_info_path": "/vulnerabilities/CVE-2022-29216/55994", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29208: Segfault and OOB write due to incomplete validation in 'EditDistance'.", "cve": "CVE-2022-29208", "id": "pyup.io-56002", "more_info_path": "/vulnerabilities/CVE-2022-29208/56002", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29194: Missing validation which causes denial of service via 'DeleteSessionTensor'.", "cve": "CVE-2022-29194", "id": "pyup.io-56004", "more_info_path": "/vulnerabilities/CVE-2022-29194/56004", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29204: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29204", "id": "pyup.io-56016", "more_info_path": "/vulnerabilities/CVE-2022-29204/56016", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-30115.", "cve": "CVE-2022-30115", "id": "pyup.io-56010", "more_info_path": "/vulnerabilities/CVE-2022-30115/56010", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27781.", "cve": "CVE-2022-27781", "id": "pyup.io-56009", "more_info_path": "/vulnerabilities/CVE-2022-27781/56009", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the 'tf.compat.v1.signal.rfft2d' and 'tf.compat.v1.signal.rfft3d' lack input validation and under certain condition can result in crashes (due to 'CHECK'-failures). Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.", "cve": "CVE-2022-29213", "id": "pyup.io-56022", "more_info_path": "/vulnerabilities/CVE-2022-29213/56022", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29212: Core dump when loading TFLite models with quantization.", "cve": "CVE-2022-29212", "id": "pyup.io-56027", "more_info_path": "/vulnerabilities/CVE-2022-29212/56027", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29211: Segfault when 'tf.histogram_fixed_width' is called with NaN values.", "cve": "CVE-2022-29211", "id": "pyup.io-56017", "more_info_path": "/vulnerabilities/CVE-2022-29211/56017", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29209: Type confusion leading to 'CHECK'-failure based denial of service.", "cve": "CVE-2022-29209", "id": "pyup.io-56024", "more_info_path": "/vulnerabilities/CVE-2022-29209/56024", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29205: Segfault due to missing support for quantized types.", "cve": "CVE-2022-29205", "id": "pyup.io-56020", "more_info_path": "/vulnerabilities/CVE-2022-29205/56020", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29203: Integer overflow in 'SpaceToBatchND'.", "cve": "CVE-2022-29203", "id": "pyup.io-56012", "more_info_path": "/vulnerabilities/CVE-2022-29203/56012", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29201: Missing validation which results in undefined behavior in 'QuantizedConv2D'.", "cve": "CVE-2022-29201", "id": "pyup.io-56014", "more_info_path": "/vulnerabilities/CVE-2022-29201/56014", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29207: Issues arising from undefined behavior stemming from users supplying invalid resource handles.", "cve": "CVE-2022-29207", "id": "pyup.io-56000", "more_info_path": "/vulnerabilities/CVE-2022-29207/56000", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29200: Missing validation which causes denial of service via 'LSTMBlockCell'.", "cve": "CVE-2022-29200", "id": "pyup.io-55997", "more_info_path": "/vulnerabilities/CVE-2022-29200/55997", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29199: Missing validation which causes denial of service via 'LoadAndRemapMatrix'.", "cve": "CVE-2022-29199", "id": "pyup.io-56021", "more_info_path": "/vulnerabilities/CVE-2022-29199/56021", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29196: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29196", "id": "pyup.io-55999", "more_info_path": "/vulnerabilities/CVE-2022-29196/55999", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29202: Denial of service in 'tf.ragged.constant' due to lack of validation.", "cve": "CVE-2022-29202", "id": "pyup.io-56013", "more_info_path": "/vulnerabilities/CVE-2022-29202/56013", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27782.", "cve": "CVE-2022-27782", "id": "pyup.io-56025", "more_info_path": "/vulnerabilities/CVE-2022-27782/56025", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29198: Missing validation which causes denial of service via 'SparseTensorToCSRSparseMatrix'.", "cve": "CVE-2022-29198", "id": "pyup.io-55998", "more_info_path": "/vulnerabilities/CVE-2022-29198/55998", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29197: Missing validation which causes denial of service via 'UnsortedSegmentJoin'.", "cve": "CVE-2022-29197", "id": "pyup.io-56001", "more_info_path": "/vulnerabilities/CVE-2022-29197/56001", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29193: missing validation which causes 'TensorSummaryV2' to crash.", "cve": "CVE-2022-29193", "id": "pyup.io-55995", "more_info_path": "/vulnerabilities/CVE-2022-29193/55995", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29206: Missing validation which results in undefined behavior in 'SparseTensorDenseAdd'.", "cve": "CVE-2022-29206", "id": "pyup.io-56015", "more_info_path": "/vulnerabilities/CVE-2022-29206/56015", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29195: Missing validation which causes denial of service via 'StagePeek'.", "cve": "CVE-2022-29195", "id": "pyup.io-56003", "more_info_path": "/vulnerabilities/CVE-2022-29195/56003", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29192: missing validation which crashes 'QuantizeAndDequantizeV4Grad'.", "cve": "CVE-2022-29192", "id": "pyup.io-56018", "more_info_path": "/vulnerabilities/CVE-2022-29192/56018", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29191: Missing validation which causes denial of service via 'GetSessionTensor'.", "cve": "CVE-2022-29191", "id": "pyup.io-56026", "more_info_path": "/vulnerabilities/CVE-2022-29191/56026", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35985: 'CHECK' fail in 'LRNGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9942-r22v-78cp", "cve": "CVE-2022-35985", "id": "pyup.io-55944", "more_info_path": "/vulnerabilities/CVE-2022-35985/55944", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35952: 'CHECK' failures in 'UnbatchGradOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h5vq-gw2c-pq47", "cve": "CVE-2022-35952", "id": "pyup.io-55938", "more_info_path": "/vulnerabilities/CVE-2022-35952/55938", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35979: Segfault in 'QuantizedRelu' and 'QuantizedRelu6'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v7vw-577f-vp8x", "cve": "CVE-2022-35979", "id": "pyup.io-55940", "more_info_path": "/vulnerabilities/CVE-2022-35979/55940", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36015: Integer overflow in math ops. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rh87-q4vg-m45j", "cve": "CVE-2022-36015", "id": "pyup.io-55942", "more_info_path": "/vulnerabilities/CVE-2022-36015/55942", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36017: Segfault in 'Requantize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wqmc-pm8c-2jhc", "cve": "CVE-2022-36017", "id": "pyup.io-55941", "more_info_path": "/vulnerabilities/CVE-2022-36017/55941", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35934: 'CHECK' failure in tf.reshape via overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f4w6-h4f5-wx45", "cve": "CVE-2022-35934", "id": "pyup.io-55946", "more_info_path": "/vulnerabilities/CVE-2022-35934/55946", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35969: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q2c3-jpmc-gfjx", "cve": "CVE-2022-35969", "id": "pyup.io-55945", "more_info_path": "/vulnerabilities/CVE-2022-35969/55945", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35990: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannelGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h7ff-cfc9-wmmh", "cve": "CVE-2022-35990", "id": "pyup.io-55952", "more_info_path": "/vulnerabilities/CVE-2022-35990/55952", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35984: 'CHECK' fail in 'ParameterizedTruncatedNormal'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2xf-8hgm-hpw5", "cve": "CVE-2022-35984", "id": "pyup.io-55950", "more_info_path": "/vulnerabilities/CVE-2022-35984/55950", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35996: Floating point exception in 'Conv2D'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q5jv-m6qw-5g37", "cve": "CVE-2022-35996", "id": "pyup.io-55951", "more_info_path": "/vulnerabilities/CVE-2022-35996/55951", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35964: Segfault in 'BlockLSTMGradV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f7r5-q7cx-h668", "cve": "CVE-2022-35964", "id": "pyup.io-55954", "more_info_path": "/vulnerabilities/CVE-2022-35964/55954", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35981: 'CHECK' fail in 'FractionalMaxPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vxv8-r8q2-63xw", "cve": "CVE-2022-35981", "id": "pyup.io-55958", "more_info_path": "/vulnerabilities/CVE-2022-35981/55958", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35974: Segfault in 'QuantizeDownAndShrinkRange'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vgvh-2pf4-jr2x", "cve": "CVE-2022-35974", "id": "pyup.io-55962", "more_info_path": "/vulnerabilities/CVE-2022-35974/55962", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35987: 'CHECK' fail in 'DenseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w62h-8xjm-fv49", "cve": "CVE-2022-35987", "id": "pyup.io-55964", "more_info_path": "/vulnerabilities/CVE-2022-35987/55964", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35966: Segfault in 'QuantizedAvgPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4w68-4x85-mjj9", "cve": "CVE-2022-35966", "id": "pyup.io-55966", "more_info_path": "/vulnerabilities/CVE-2022-35966/55966", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35972: Segfault in 'QuantizedBiasAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4pc4-m9mj-v2r9", "cve": "CVE-2022-35972", "id": "pyup.io-55970", "more_info_path": "/vulnerabilities/CVE-2022-35972/55970", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35982: Segfault in 'SparseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-397c-5g2j-qxpv", "cve": "CVE-2022-35982", "id": "pyup.io-55969", "more_info_path": "/vulnerabilities/CVE-2022-35982/55969", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35993: 'CHECK' fail in 'SetSize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wq6q-6m32-9rv9", "cve": "CVE-2022-35993", "id": "pyup.io-55971", "more_info_path": "/vulnerabilities/CVE-2022-35993/55971", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36019: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannel'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9j4v-pp28-mxv7", "cve": "CVE-2022-36019", "id": "pyup.io-55977", "more_info_path": "/vulnerabilities/CVE-2022-36019/55977", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35965: Segfault in 'LowerBound' and 'UpperBound'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qxpx-j395-pw36", "cve": "CVE-2022-35965", "id": "pyup.io-55976", "more_info_path": "/vulnerabilities/CVE-2022-35965/55976", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35968: 'CHECK' fail in 'AvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2475-53vw-vp25", "cve": "CVE-2022-35968", "id": "pyup.io-55979", "more_info_path": "/vulnerabilities/CVE-2022-35968/55979", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35999: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-37jf-mjv6-xfqw", "cve": "CVE-2022-35999", "id": "pyup.io-55985", "more_info_path": "/vulnerabilities/CVE-2022-35999/55985", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35963: 'CHECK' failures in 'FractionalAvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-84jm-4cf3-9jfm", "cve": "CVE-2022-35963", "id": "pyup.io-55984", "more_info_path": "/vulnerabilities/CVE-2022-35963/55984", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36018: 'CHECK' fail in 'RaggedTensorToVariant'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6cv-4fmf-66xf", "cve": "CVE-2022-36018", "id": "pyup.io-55989", "more_info_path": "/vulnerabilities/CVE-2022-36018/55989", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35971: 'CHECK' fail in 'FakeQuantWithMinMaxVars'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9fpg-838v-wpv7", "cve": "CVE-2022-35971", "id": "pyup.io-55987", "more_info_path": "/vulnerabilities/CVE-2022-35971/55987", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36027: Segfault TFLite converter on per-channel quantized transposed convolutions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-79h2-q768-fpxr", "cve": "CVE-2022-36027", "id": "pyup.io-55968", "more_info_path": "/vulnerabilities/CVE-2022-36027/55968", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36016: 'CHECK'-fail in 'tensorflow::full_type::SubstituteFromAttrs'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g468-qj8g-vcjc", "cve": "CVE-2022-36016", "id": "pyup.io-55974", "more_info_path": "/vulnerabilities/CVE-2022-36016/55974", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36014: Null-dereference in 'mlir::tfg::TFOp::nameAttr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7j3m-8g3c-9qqq", "cve": "CVE-2022-36014", "id": "pyup.io-55972", "more_info_path": "/vulnerabilities/CVE-2022-36014/55972", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36011: Null dereference on MLIR on empty function attributes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fv43-93gv-vm8f", "cve": "CVE-2022-36011", "id": "pyup.io-55967", "more_info_path": "/vulnerabilities/CVE-2022-36011/55967", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35973: Segfault in 'QuantizedMatMul'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-689c-r7h2-fv9v", "cve": "CVE-2022-35973", "id": "pyup.io-55963", "more_info_path": "/vulnerabilities/CVE-2022-35973/55963", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36005: 'CHECK' fail in 'FakeQuantWithMinMaxVarsGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r26c-679w-mrjm", "cve": "CVE-2022-36005", "id": "pyup.io-55991", "more_info_path": "/vulnerabilities/CVE-2022-36005/55991", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35970: Segfault in 'QuantizedInstanceNorm'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g35r-369w-3fqp", "cve": "CVE-2022-35970", "id": "pyup.io-55980", "more_info_path": "/vulnerabilities/CVE-2022-35970/55980", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35995: 'CHECK' fail in 'AudioSummaryV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9h5-vr8m-x2h4", "cve": "CVE-2022-35995", "id": "pyup.io-55986", "more_info_path": "/vulnerabilities/CVE-2022-35995/55986", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36004: 'CHECK' fail in 'tf.random.gamma'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv8m-8x97-937q", "cve": "CVE-2022-36004", "id": "pyup.io-55988", "more_info_path": "/vulnerabilities/CVE-2022-36004/55988", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36003: 'CHECK' fail in 'RandomPoissonV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cv2p-32v3-vhwq", "cve": "CVE-2022-36003", "id": "pyup.io-55943", "more_info_path": "/vulnerabilities/CVE-2022-36003/55943", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36002: 'CHECK' fail in 'Unbatch'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mh3m-62v7-68xg", "cve": "CVE-2022-36002", "id": "pyup.io-55947", "more_info_path": "/vulnerabilities/CVE-2022-36002/55947", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36001: 'CHECK' fail in 'DrawBoundingBoxes'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jqm7-m5q7-3hm5", "cve": "CVE-2022-36001", "id": "pyup.io-55983", "more_info_path": "/vulnerabilities/CVE-2022-36001/55983", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36000: 'CHECK' fail in 'Eig'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqxc-pvf8-2w9v", "cve": "CVE-2022-36000", "id": "pyup.io-55959", "more_info_path": "/vulnerabilities/CVE-2022-36000/55959", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35998: 'CHECK' fail in 'EmptyTensorList'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhw4-wwr7-gjc5", "cve": "CVE-2022-35998", "id": "pyup.io-55956", "more_info_path": "/vulnerabilities/CVE-2022-35998/55956", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35997: 'CHECK' fail in 'tf.sparse.cross'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p7hr-f446-x6qf", "cve": "CVE-2022-35997", "id": "pyup.io-55955", "more_info_path": "/vulnerabilities/CVE-2022-35997/55955", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35994: 'CHECK' fail in 'CollectiveGather'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fhfc-2q7x-929f", "cve": "CVE-2022-35994", "id": "pyup.io-55981", "more_info_path": "/vulnerabilities/CVE-2022-35994/55981", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35992: 'CHECK' fail in 'TensorListFromTensor'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9v8w-xmr4-wgxp", "cve": "CVE-2022-35992", "id": "pyup.io-55960", "more_info_path": "/vulnerabilities/CVE-2022-35992/55960", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36026: 'CHECK' fail in 'QuantizeAndDequantizeV3'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9cr2-8pwr-fhfq", "cve": "CVE-2022-36026", "id": "pyup.io-55965", "more_info_path": "/vulnerabilities/CVE-2022-36026/55965", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35989: 'CHECK' fail in 'MaxPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j43h-pgmg-5hjq", "cve": "CVE-2022-35989", "id": "pyup.io-55990", "more_info_path": "/vulnerabilities/CVE-2022-35989/55990", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35986: Segfault in 'RaggedBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wr9v-g9vf-c74v", "cve": "CVE-2022-35986", "id": "pyup.io-55961", "more_info_path": "/vulnerabilities/CVE-2022-35986/55961", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35983: 'CHECK' fail in 'Save' and 'SaveSlices'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6vp-8q9j-whx4", "cve": "CVE-2022-35983", "id": "pyup.io-55949", "more_info_path": "/vulnerabilities/CVE-2022-35983/55949", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35967: Segfault in 'QuantizedAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v6h3-348g-6h5x", "cve": "CVE-2022-35967", "id": "pyup.io-55978", "more_info_path": "/vulnerabilities/CVE-2022-35967/55978", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35959: 'CHECK' failures in 'AvgPool3DGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wxjj-cgcx-r3vq", "cve": "CVE-2022-35959", "id": "pyup.io-55953", "more_info_path": "/vulnerabilities/CVE-2022-35959/55953", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35941: 'CHECK' failure in 'AvgPoolOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mgmh-g2v6-mqw5", "cve": "CVE-2022-35941", "id": "pyup.io-55973", "more_info_path": "/vulnerabilities/CVE-2022-35941/55973", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35940: Int overflow in 'RaggedRangeOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x989-q2pq-4q5x", "cve": "CVE-2022-35940", "id": "pyup.io-55982", "more_info_path": "/vulnerabilities/CVE-2022-35940/55982", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35939: OOB write in 'scatter_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-ffjm-4qwc-7cmf", "cve": "CVE-2022-35939", "id": "pyup.io-55937", "more_info_path": "/vulnerabilities/CVE-2022-35939/55937", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35937: OOB read in 'Gather_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pxrw-j2fv-hx3h", "cve": "CVE-2022-35937", "id": "pyup.io-55936", "more_info_path": "/vulnerabilities/CVE-2022-35937/55936", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35988: 'CHECK' fail in 'tf.linalg.matrix_rank'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vqj-64pv-w55c", "cve": "CVE-2022-35988", "id": "pyup.io-55975", "more_info_path": "/vulnerabilities/CVE-2022-35988/55975", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36012: Assertion fail on MLIR empty edge names.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jvhc-5hhr-w3v5", "cve": "CVE-2022-36012", "id": "pyup.io-55948", "more_info_path": "/vulnerabilities/CVE-2022-36012/55948", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35960: 'CHECK' failure in 'TensorListReserve' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v5xg-3q2c-c2r4", "cve": "CVE-2022-35960", "id": "pyup.io-55939", "more_info_path": "/vulnerabilities/CVE-2022-35960/55939", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36013: Null-dereference in 'mlir::tfg::GraphDefImporter::ConvertNodeDef'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-828c-5j5q-vrjq", "cve": "CVE-2022-36013", "id": "pyup.io-55957", "more_info_path": "/vulnerabilities/CVE-2022-36013/55957", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41889: If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a 'nullptr', which is not caught. An example can be seen in 'tf.compat.v1.extract_volume_patches' by passing in quantized tensors as input 'ksizes'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xxcj-rhqg-m46g", "cve": "CVE-2022-41889", "id": "pyup.io-55915", "more_info_path": "/vulnerabilities/CVE-2022-41889/55915", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41910: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-frqp-wp83-qggv", "cve": "CVE-2022-41910", "id": "pyup.io-55930", "more_info_path": "/vulnerabilities/CVE-2022-41910/55930", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41911: When printing a tensor, we get it's data as a 'const char*' array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from 'char' to 'bool' are undefined if the 'char' is not '0' or '1', so sanitizers/fuzzers will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j", "cve": "CVE-2022-41911", "id": "pyup.io-55914", "more_info_path": "/vulnerabilities/CVE-2022-41911/55914", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41908: TensorFlow is an open source platform for machine learning. An input 'token' that is not a UTF-8 bytestring will trigger a 'CHECK' fail in 'tf.raw_ops.PyFunc'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv77-9g28-cwg3", "cve": "CVE-2022-41908", "id": "pyup.io-55920", "more_info_path": "/vulnerabilities/CVE-2022-41908/55920", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41898: If 'SparseFillEmptyRowsGrad' is given empty inputs, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hq7g-wwwp-q46h", "cve": "CVE-2022-41898", "id": "pyup.io-55932", "more_info_path": "/vulnerabilities/CVE-2022-41898/55932", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41897: If 'FractionMaxPoolGrad' is given outsize inputs 'row_pooling_sequence' and 'col_pooling_sequence', TensorFlow will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2w8-jw48-fr7j", "cve": "CVE-2022-41897", "id": "pyup.io-55928", "more_info_path": "/vulnerabilities/CVE-2022-41897/55928", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41895: If 'MirrorPadGrad' is given outsize input 'paddings', TensorFlow will give a heap OOB error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gq2j-cr96-gvqx", "cve": "CVE-2022-41895", "id": "pyup.io-55912", "more_info_path": "/vulnerabilities/CVE-2022-41895/55912", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41894: The reference kernel of the 'CONV_3D_TRANSPOSE' TensorFlow Lite operator wrongly increments the data_ptr when adding the bias to the result. Instead of 'data_ptr += num_channels;' it should be 'data_ptr += output_num_channels;' as if the number of input channels is different than the number of output channels, the wrong result will be returned and a buffer overflow will occur if num_channels > output_num_channels. An attacker can craft a model with a specific number of input channels. It is then possible to write specific values through the bias of the layer outside the bounds of the buffer. This attack only works if the reference kernel resolver is used in the interpreter.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6q3-vv32-2cq5", "cve": "CVE-2022-41894", "id": "pyup.io-55933", "more_info_path": "/vulnerabilities/CVE-2022-41894/55933", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41893: If 'tf.raw_ops.TensorListResize' is given a nonscalar value for input 'size', it results 'CHECK' fail which can be used to trigger a denial of service attack.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-67pf-62xr-q35m", "cve": "CVE-2022-41893", "id": "pyup.io-55918", "more_info_path": "/vulnerabilities/CVE-2022-41893/55918", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41891: If 'tf.raw_ops.TensorListConcat' is given 'element_shape=[]', it results segmentation fault which can be used to trigger a denial of service attack.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-66vq-54fq-6jvv", "cve": "CVE-2022-41891", "id": "pyup.io-55913", "more_info_path": "/vulnerabilities/CVE-2022-41891/55913", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41884: If a numpy array is created with a shape such that one element is zero and the others sum to a large number, an error will be raised. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jq6x-99hj-q636", "cve": "CVE-2022-41884", "id": "pyup.io-55927", "more_info_path": "/vulnerabilities/CVE-2022-41884/55927", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1.", "cve": "CVE-2022-41902", "id": "pyup.io-55925", "more_info_path": "/vulnerabilities/CVE-2022-41902/55925", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41885: When 'tf.raw_ops.FusedResizeAndPadConv2D' is given a large tensor shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-762h-vpvw-3rcx", "cve": "CVE-2022-41885", "id": "pyup.io-55916", "more_info_path": "/vulnerabilities/CVE-2022-41885/55916", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41900: The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xvwp-h6jv-7472", "cve": "CVE-2022-41900", "id": "pyup.io-55921", "more_info_path": "/vulnerabilities/CVE-2022-41900/55921", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41890: If 'BCast::ToShape' is given input larger than an 'int32', it will crash, despite being supposed to handle up to an 'int64'. An example can be seen in 'tf.experimental.numpy.outer' by passing in large input to the input 'b'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h246-cgh4-7475", "cve": "CVE-2022-41890", "id": "pyup.io-55922", "more_info_path": "/vulnerabilities/CVE-2022-41890/55922", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41907: When 'tf.raw_ops.ResizeNearestNeighborGrad' is given a large 'size' input, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-368v-7v32-52fx", "cve": "CVE-2022-41907", "id": "pyup.io-55924", "more_info_path": "/vulnerabilities/CVE-2022-41907/55924", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41886: When 'tf.raw_ops.ImageProjectiveTransformV2' is given a large output shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-54pp-c6pp-7fpx", "cve": "CVE-2022-41886", "id": "pyup.io-55929", "more_info_path": "/vulnerabilities/CVE-2022-41886/55929", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41901: An input 'sparse_matrix' that is not a matrix with a shape with rank 0 will trigger a 'CHECK' fail in 'tf.raw_ops.SparseMatrixNNZ'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9fm-r5mm-rf9f", "cve": "CVE-2022-41901", "id": "pyup.io-55911", "more_info_path": "/vulnerabilities/CVE-2022-41901/55911", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41896: If 'ThreadUnsafeUnigramCandidateSampler' is given input 'filterbank_channel_count' greater than the allowed max size, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rmg2-f698-wq35", "cve": "CVE-2022-41896", "id": "pyup.io-55926", "more_info_path": "/vulnerabilities/CVE-2022-41896/55926", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41899: TensorFlow is an open source platform for machine learning. Inputs 'dense_features' or 'example_state_data' not of rank 2 will trigger a 'CHECK' fail in 'SdcaOptimizer'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-27rc-728f-x5w2", "cve": "CVE-2022-41899", "id": "pyup.io-55917", "more_info_path": "/vulnerabilities/CVE-2022-41899/55917", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41909: An input 'encoded' that is not a valid 'CompositeTensorVariant' tensor will trigger a segfault in 'tf.raw_ops.CompositeTensorVariantToComponents'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjx6-v474-2ch9", "cve": "CVE-2022-41909", "id": "pyup.io-55919", "more_info_path": "/vulnerabilities/CVE-2022-41909/55919", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41880: When the 'BaseCandidateSamplerOp' function receives a value in 'true_classes' larger than 'range_max', a heap oob read occurs.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8w5g-3wcv-9g2j", "cve": "CVE-2022-41880", "id": "pyup.io-55923", "more_info_path": "/vulnerabilities/CVE-2022-41880/55923", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41888: When running on GPU, 'tf.image.generate_bounding_box_proposals' receives a 'scores' input that must be of rank 4 but is not checked.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6x99-gv2v-q76v", "cve": "CVE-2022-41888", "id": "pyup.io-55931", "more_info_path": "/vulnerabilities/CVE-2022-41888/55931", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35991: 'CHECK' fail in 'TensorListScatter' and 'TensorListScatterV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vm7x-4qhj-rrcq\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xf83-q765-xm6m", "cve": "CVE-2022-35991", "id": "pyup.io-55935", "more_info_path": "/vulnerabilities/CVE-2022-35991/55935", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-gpu 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35935: 'CHECK' failure in 'SobolSample' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-97p7-w86h-vcf9\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqvq-fvhr-v6hc", "cve": "CVE-2022-35935", "id": "pyup.io-55934", "more_info_path": "/vulnerabilities/CVE-2022-35935/55934", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-gpu 2.9.3 and 2.10.1 include a fix for CVE-2022-41887: 'tf.keras.losses.poisson' receives a 'y_pred' and 'y_true' that are passed through 'functor::mul' in 'BinaryOp'. If the resulting dimensions overflow an 'int32', TensorFlow will crash due to a size mismatch during broadcast assignment.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fvv-46hw-vpg3", "cve": "CVE-2022-41887", "id": "pyup.io-55910", "more_info_path": "/vulnerabilities/CVE-2022-41887/55910", "specs": [ "<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Google TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local). See CVE-2018-8825.", "cve": "CVE-2018-8825", "id": "pyup.io-56366", "more_info_path": "/vulnerabilities/CVE-2018-8825/56366", "specs": [ "<=1.7" ], "v": "<=1.7" }, { "advisory": "Versions susceptible to a Denial of Service (DoS) vulnerability exist in tensorflow-gpu, arising from a repeat instance of CVE-2022-35935, linked to SobolSample's handling of assumed scalar inputs.", "cve": "PVE-2024-99845", "id": "pyup.io-65575", "more_info_path": "/vulnerabilities/PVE-2024-99845/65575", "specs": [ ">=0,<2.8.4", ">=2.9.0,<2.9.3", ">=2.10.0,<2.10.1" ], "v": ">=0,<2.8.4,>=2.9.0,<2.9.3,>=2.10.0,<2.10.1" }, { "advisory": "Some versions of tensorflow-gpu are susceptible to a Denial of Service (DoS) attack stemming from a vulnerability related to CVE-2022-35991, observed in TensorListScatter and TensorListScatterV2 when non-scalar inputs are used.", "cve": "PVE-2024-99844", "id": "pyup.io-65576", "more_info_path": "/vulnerabilities/PVE-2024-99844/65576", "specs": [ ">=0,<2.8.4", ">=2.9.0,<2.9.3", ">=2.10.0,<2.10.1" ], "v": ">=0,<2.8.4,>=2.9.0,<2.9.3,>=2.10.0,<2.10.1" }, { "advisory": "Tensorflow-gpu versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 updates its dependency \"SQLite\" to handle CVE-2020-15358.", "cve": "CVE-2020-15358", "id": "pyup.io-56333", "more_info_path": "/vulnerabilities/CVE-2020-15358/56333", "specs": [ ">=1.15.0rc0,<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=1.15.0rc0,<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 1.15.2 and 2.0.1 update its dependency \"SQLite\" to handle CVE-2019-19646.", "cve": "CVE-2019-19646", "id": "pyup.io-56359", "more_info_path": "/vulnerabilities/CVE-2019-19646/56359", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-gpu versions 1.15.2 and 2.0.1 updates its dependency \"curl\" to handle CVE-2019-5482.", "cve": "CVE-2019-5482", "id": "pyup.io-56358", "more_info_path": "/vulnerabilities/CVE-2019-5482/56358", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-gpu versions 1.15.2 and 2.0.1 updates its dependency \"curl\" to handle CVE-2019-5481.", "cve": "CVE-2019-5481", "id": "pyup.io-56356", "more_info_path": "/vulnerabilities/CVE-2019-5481/56356", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-gpu versions 1.15.2 and 2.0.1 updates 'sqlite3' to handle CVE-2019-16168.", "cve": "CVE-2019-16168", "id": "pyup.io-56357", "more_info_path": "/vulnerabilities/CVE-2019-16168/56357", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-gpu versions 1.15.2 and 2.0.1 includes a fix for CVE-2020-5215: In TensorFlow before 1.15.2 and 2.0.1, converting a string (from Python) to a tf.float16 value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode. This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a tf.float16 value. Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar tf.float16 value with a scalar string will trigger this issue due to automatic conversions. This can be easily reproduced by tf.constant(\"hello\", tf.float16), if eager execution is enabled.", "cve": "CVE-2020-5215", "id": "pyup.io-56360", "more_info_path": "/vulnerabilities/CVE-2020-5215/56360", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-gpu versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 include a fix for CVE-2021-29567: Due to lack of validation in 'tf.raw_ops.SparseDenseCwiseMul', an attacker can trigger denial of service via 'CHECK'-fails or accesses to outside the bounds of heap allocated data. Since the implementation (https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80), it only validates the rank of the input arguments but no constraints between dimensions (https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul) and an attacker can abuse them to trigger internal 'CHECK' assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers.", "cve": "CVE-2021-29567", "id": "pyup.io-56346", "more_info_path": "/vulnerabilities/CVE-2021-29567/56346", "specs": [ ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.5.0rc0,<2.5.0" ], "v": ">=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.5.0rc0,<2.5.0" }, { "advisory": "Tensorflow-gpu 2.10.1 includes a fix for CVE-2022-41883: When ops that have specified input sizes receive a differing number of inputs, the executor will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj", "cve": "CVE-2022-41883", "id": "pyup.io-55909", "more_info_path": "/vulnerabilities/CVE-2022-41883/55909", "specs": [ ">=2.10.0rc0,<2.10.1" ], "v": ">=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-gpu versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15193: In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of \"dlpack.to_dlpack\" can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing in a Python object instead of a tensor. The uninitialized memory address is due to a \"reinterpret_cast\". Since the \"PyObject\" is a Python object, not a Tensorflow tensor, the cast to \"EagerTensor\" fails. The issue was patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v", "cve": "CVE-2020-15193", "id": "pyup.io-56345", "more_info_path": "/vulnerabilities/CVE-2020-15193/56345", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15214: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimension of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15214", "id": "pyup.io-56343", "more_info_path": "/vulnerabilities/CVE-2020-15214/56343", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15212: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to \"segment_ids_data\" can alter \"output_index\" and then write to outside of \"output_data\" buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15212", "id": "pyup.io-56342", "more_info_path": "/vulnerabilities/CVE-2020-15212/56342", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15192: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to 'dlpack.to_dlpack' there is a memory leak following an expected validation failure. The issue occurs because the 'status' argument during validation failures is not properly checked. Since each of the above methods can return an error status, the 'status' value must be checked before continuing.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fxw-76px-3rxv", "cve": "CVE-2020-15192", "id": "pyup.io-56344", "more_info_path": "/vulnerabilities/CVE-2020-15192/56344", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15191: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to 'dlpack.to_dlpack' the expected validations will cause variables to bind to 'nullptr' while setting a 'status' variable to the error condition. However, this 'status' argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with '-fsanitize=null'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr", "cve": "CVE-2020-15191", "id": "pyup.io-56340", "more_info_path": "/vulnerabilities/CVE-2020-15191/56340", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15213: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimension of the output tensor, attackers can use a very large value to trigger a large allocation. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps. However, if the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hjmq-236j-8m87", "cve": "CVE-2020-15213", "id": "pyup.io-56341", "more_info_path": "/vulnerabilities/CVE-2020-15213/56341", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu 2.3.1 includes a fix for CVE-2020-15199: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the \"splits\" tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure. Since \"BatchedMap\" is equivalent to a vector, it needs to have at least one element to not be \"nullptr\". If user passes a \"splits\" tensor that is empty or has exactly one element, we get a \"SIGABRT\" signal raised by the operating system. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x5cp-9pcf-pp3h", "cve": "CVE-2020-15199", "id": "pyup.io-56338", "more_info_path": "/vulnerabilities/CVE-2020-15199/56338", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu 2.3.1 includes a fix for CVE-2020-15201: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Hence, the code is prone to heap buffer overflow. If \"split_values\" does not end with a value at least \"num_values\" then the \"while\" loop condition will trigger a read outside of the bounds of \"split_values\" once \"batch_idx\" grows too large. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4", "cve": "CVE-2020-15201", "id": "pyup.io-56339", "more_info_path": "/vulnerabilities/CVE-2020-15201/56339", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu version 2.3.1 includes a fix for CVE-2020-15197: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix. However, malicious users can pass in tensors of different rank, resulting in a \"CHECK\" assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.", "cve": "CVE-2020-15197", "id": "pyup.io-56334", "more_info_path": "/vulnerabilities/CVE-2020-15197/56334", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu 2.3.1 includes a fix for CVE-2020-15200: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Thus, the code sets up conditions to cause a heap buffer overflow. A \"BatchedMap\" is equivalent to a vector where each element is a hashmap. However, if the first element of \"splits_values\" is not 0, \"batch_idx\" will never be 1, hence there will be no hashmap at index 0 in \"per_batch_counts\". Trying to access that in the user code results in a segmentation fault. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x7rp-74x2-mjf3", "cve": "CVE-2020-15200", "id": "pyup.io-56337", "more_info_path": "/vulnerabilities/CVE-2020-15200/56337", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu version 2.3.1 includes a fix for CVE-2020-15196: In Tensorflow version 2.3.0, the \"SparseCountSparseOutput\" and \"RaggedCountSparseOutput\" implementations don't validate that the \"weights\" tensor has the same shape as the data. The check exists for \"DenseCountSparseOutput\", where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph", "cve": "CVE-2020-15196", "id": "pyup.io-56336", "more_info_path": "/vulnerabilities/CVE-2020-15196/56336", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu 2.3.1 includes a fix for CVE-2020-15198: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has the same shape as the \"values\" one. The values in these tensors are always accessed in parallel. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3", "cve": "CVE-2020-15198", "id": "pyup.io-56335", "more_info_path": "/vulnerabilities/CVE-2020-15198/56335", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37671: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.Map*' and 'tf.raw_ops.OrderedMap*' operations. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that 'indices' is in ascending order, but does not check that 'indices' is not empty. The Tensorflow team has patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac.", "cve": "CVE-2021-37671", "id": "pyup.io-56288", "more_info_path": "/vulnerabilities/CVE-2021-37671/56288", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37680: In affected versions the implementation of fully connected layers in TFLite is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226). The Tensorflow team has patched the issue in GitHub commit 718721986aa137691ee23f03638867151f74935f.", "cve": "CVE-2021-37680", "id": "pyup.io-56295", "more_info_path": "/vulnerabilities/CVE-2021-37680/56295", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37683: In affected versions the implementation of division in TFLite is vulnerable to a division by 0 error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc). There is no check that the divisor tensor does not contain zero elements. The Tensorflow team has patched the issue in GitHub commit 1e206baedf8bef0334cca3eb92bab134ef525a28.", "cve": "CVE-2021-37683", "id": "pyup.io-56293", "more_info_path": "/vulnerabilities/CVE-2021-37683/56293", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37637: It is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid. The Tensorflow team has patched the issue in GitHub commit 5dc7f6981fdaf74c8c5be41f393df705841fb7c5.", "cve": "CVE-2021-37637", "id": "pyup.io-56294", "more_info_path": "/vulnerabilities/CVE-2021-37637/56294", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37636: In affected versions the implementation of 'tf.raw_ops.SparseDenseCwiseDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L56) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit d9204be9f49520cdaaeb2541d1dc5187b23f31d9.", "cve": "CVE-2021-37636", "id": "pyup.io-56296", "more_info_path": "/vulnerabilities/CVE-2021-37636/56296", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37689: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. This is caused by the MLIR optimization of 'L2NormalizeReduceAxis' operator. The implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/compiler/mlir/lite/transforms/optimize.cc#L67-L70) unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements. The Tensorflow team has patched the issue in GitHub commit d6b57f461b39fd1aa8c1b870f1b974aac3554955.", "cve": "CVE-2021-37689", "id": "pyup.io-56289", "more_info_path": "/vulnerabilities/CVE-2021-37689/56289", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37635: In affected versions the implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data. The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor. The Tensorflow team has patched the issue in GitHub commit 87158f43f05f2720a374f3e6d22a7aaa3a33f750.", "cve": "CVE-2021-37635", "id": "pyup.io-56291", "more_info_path": "/vulnerabilities/CVE-2021-37635/56291", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37667: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.UnicodeEncode'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the 'input_splits' tensor before validating that this tensor is not empty. The Tensorflow team has patched the issue in GitHub commit 2e0ee46f1a47675152d3d865797a18358881d7a6.", "cve": "CVE-2021-37667", "id": "pyup.io-56292", "more_info_path": "/vulnerabilities/CVE-2021-37667/56292", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37648: In affected versions the code for 'tf.raw_ops.SaveV2' does not properly validate the inputs and an attacker can trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses 'ValidateInputs' to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above. However, the validation uses 'OP_REQUIRES' which translates to setting the 'Status' object of the current 'OpKernelContext' to an error status, followed by an empty 'return' statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the nQext line in 'Compute' that follows the call to 'ValidateInputs'. This is equivalent to lacking the validation. The Tensorflow team has patched the issue in GitHub commit 9728c60e136912a12d99ca56e106b7cce7af5986.", "cve": "CVE-2021-37648", "id": "pyup.io-56290", "more_info_path": "/vulnerabilities/CVE-2021-37648/56290", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37642: In affected versions the implementation of 'tf.raw_ops.ResourceScatterDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit 4aacb30888638da75023e6601149415b39763d76.", "cve": "CVE-2021-37642", "id": "pyup.io-56297", "more_info_path": "/vulnerabilities/CVE-2021-37642/56297", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37658: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixSetDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit ff8894044dfae5568ecbf2ed514c1a37dc394f1b.", "cve": "CVE-2021-37658", "id": "pyup.io-56283", "more_info_path": "/vulnerabilities/CVE-2021-37658/56283", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37659: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations). The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr. We have patched the issue in GitHub commit 93f428fd1768df147171ed674fee1fc5ab8309ec.", "cve": "CVE-2021-37659", "id": "pyup.io-56285", "more_info_path": "/vulnerabilities/CVE-2021-37659/56285", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37651: In affected versions the implementation for 'tf.raw_ops.FractionalAvgPoolGrad' can be tricked into accessing data outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty 'EigenDoubleMatrixMap' and then accesses this buffer with indices that are outside of the empty area. The Tensorflow team has patched the issue in GitHub commit 0f931751fb20f565c4e94aa6df58d54a003cdb30.", "cve": "CVE-2021-37651", "id": "pyup.io-56280", "more_info_path": "/vulnerabilities/CVE-2021-37651/56280", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37652: In affected versions the implementation for 'tf.raw_ops.BoostedTreesCreateEnsemble' can result in a use after free error if an attacker supplies specially crafted arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent 'free'-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed. The Tensorflow team has patched the issue in GitHub commit 5ecec9c6fbdbc6be03295685190a45e7eee726ab.", "cve": "CVE-2021-37652", "id": "pyup.io-56277", "more_info_path": "/vulnerabilities/CVE-2021-37652/56277", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37664: In affected versions an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range. The Tensorflow team has patched the issue in GitHub commit e84c975313e8e8e38bb2ea118196369c45c51378.", "cve": "CVE-2021-37664", "id": "pyup.io-56286", "more_info_path": "/vulnerabilities/CVE-2021-37664/56286", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37647: When a user does not supply arguments that determine a valid sparse tensor, 'tf.raw_ops.SparseTensorSliceDataset' implementation can be made to dereference a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either 'indices' or 'values' are provided for an empty sparse tensor when the other is not. If 'indices' is empty, then code that performs validation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference. If 'indices' as provided by the user is empty, then 'indices' in the C++ code above is backed by an empty 'std::vector', hence calling 'indices->dim_size(0)' results in null pointer dereferencing (same as calling 'std::vector::at()' on an empty vector). The Tensorflow team has patched the issue in GitHub commit 02cc160e29d20631de3859c6653184e3f876b9d7.", "cve": "CVE-2021-37647", "id": "pyup.io-56287", "more_info_path": "/vulnerabilities/CVE-2021-37647/56287", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37656: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToSparse'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order. The Tensorflow team has patched the issue in GitHub commit 1071f554dbd09f7e101324d366eec5f4fe5a3ece.", "cve": "CVE-2021-37656", "id": "pyup.io-56281", "more_info_path": "/vulnerabilities/CVE-2021-37656/56281", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37654: In affected versions an attacker can trigger a crash via a 'CHECK'-fail in debug builds of TensorFlow using 'tf.raw_ops.ResourceGather' or a read from outside the bounds of heap allocated data in the same API in a release build. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the 'batch_dims' value that the user supplies is less than the rank of the input tensor. Since the implementation uses several for loops over the dimensions of 'tensor', this results in reading data from outside the bounds of heap allocated buffer backing the tensor. The Tensorflow team has patched the issue in GitHub commit bc9c546ce7015c57c2f15c168b3d9201de679a1d.", "cve": "CVE-2021-37654", "id": "pyup.io-56279", "more_info_path": "/vulnerabilities/CVE-2021-37654/56279", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37649: The code for 'tf.raw_ops.UncompressElement' can be made to trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a 'CompressedElement' from a 'Variant' tensor and then proceeds to dereference it for decompressing. There is no check that the 'Variant' tensor contained a 'CompressedElement', so the pointer is actually 'nullptr'. The Tensorflow team has patched the issue in GitHub commit 7bdf50bb4f5c54a4997c379092888546c97c3ebd.", "cve": "CVE-2021-37649", "id": "pyup.io-56284", "more_info_path": "/vulnerabilities/CVE-2021-37649/56284", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37639: When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the 'tensor_name' user controlled input and immediately retrieves the tensor at the restoration index (controlled via 'preferred_shard' argument). This occurs without validating that the provided list has enough values. If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements and if the restoration index is outside the bounds, this results in heap OOB read. The Tensorflow team has patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622.", "cve": "CVE-2021-37639", "id": "pyup.io-56282", "more_info_path": "/vulnerabilities/CVE-2021-37639/56282", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37638: Sending invalid argument for 'row_partition_types' of 'tf.raw_ops.RaggedTensorToTensor' API results in a null pointer dereference and undefined behavior. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty. The Tensorflow team has patched the issue in GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314.", "cve": "CVE-2021-37638", "id": "pyup.io-56278", "more_info_path": "/vulnerabilities/CVE-2021-37638/56278", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Several versions of TensorFlow are affected by CVE-2021-37686: In affected versions, the strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for ellipsis in axis definition (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122). An attacker can craft a model such that 'ellipsis_end_idx' is smaller than 'i' (e.g., always negative). In this case, the inner loop does not increase 'i' and the 'continue' statement causes execution to skip over the preincrement at the end of the outer loop. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695.", "cve": "CVE-2021-37686", "id": "pyup.io-56276", "more_info_path": "/vulnerabilities/CVE-2021-37686/56276", "specs": [ ">=2.3.0rc0,<2.3.4rc0", ">=2.4.0rc0,<2.4.3rc0", ">=2.5.0rc0,<=2.5.0", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4rc0,>=2.4.0rc0,<2.4.3rc0,>=2.5.0rc0,<=2.5.0,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.4.0 includes a fix for CVE-2020-26269: In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.", "cve": "CVE-2020-26269", "id": "pyup.io-56309", "more_info_path": "/vulnerabilities/CVE-2020-26269/56309", "specs": [ ">=2.4.0rc0,<2.4.0" ], "v": ">=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-gpu 2.5.0, 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29614: The implementation of 'tf.io.decode_raw' produces incorrect results and crashes the Python interpreter when combining 'fixed_length' and wider datatypes. The implementation of the padded version (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc) is buggy due to a confusion about pointer arithmetic rules. First, the code computes (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L61) the width of each output element by dividing the 'fixed_length' value to the size of the type argument. The 'fixed_length' argument is also used to determine the size needed for the output tensor (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L63-L79). This is followed by reencoding code (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L85-L94). The erroneous code is the last line above: it is moving the 'out_data' pointer by 'fixed_length * sizeof (T)' bytes whereas it only copied at most 'fixed_length' bytes from the input. This results in parts of the input not being decoded into the output. Furthermore, because the pointer advance is far wider than desired, this quickly leads to writing to outside the bounds of the backing data. This OOB write leads to interpreter crash in the reproducer mentioned here, but more severe attacks can be mounted too, given that this gadget allows writing to periodically placed locations in memory.", "cve": "CVE-2021-29614", "id": "pyup.io-56275", "more_info_path": "/vulnerabilities/CVE-2021-29614/56275", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.5.0rc0,<2.5.0" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.5.0rc0,<2.5.0" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv2DBackpropInput'. See CVE-2021-29525.", "cve": "CVE-2021-29525", "id": "pyup.io-56254", "more_info_path": "/vulnerabilities/CVE-2021-29525/56254", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv2DBackpropFilter'. See CVE-2021-29524.", "cve": "CVE-2021-29524", "id": "pyup.io-56258", "more_info_path": "/vulnerabilities/CVE-2021-29524/56258", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29534: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.SparseConcat'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/b432a38fe0e1b4b904a6c222cbce794c39703e87/tensorflow/core/kernels/sparse_concat_op.cc#L76) takes the values specified in 'shapes[0]' as dimensions for the output shape. The 'TensorShape' constructor (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a 'CHECK' operation which triggers when 'InitDims' (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status. This is a legacy implementation of the constructor and operations should use 'BuildTensorShapeBase' or 'AddDimWithStatus' to prevent 'CHECK'-failures in the presence of overflows.", "cve": "CVE-2021-29534", "id": "pyup.io-56266", "more_info_path": "/vulnerabilities/CVE-2021-29534/56266", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29537: An attacker can cause a heap buffer overflow in `QuantizedResizeBilinear` by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/50711818d2e61ccce012591eeb4fdf93a8496726/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L705-L706) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly.", "cve": "CVE-2021-29537", "id": "pyup.io-56272", "more_info_path": "/vulnerabilities/CVE-2021-29537/56272", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29549: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero. Since `vector_num_elements` is determined based on input shapes (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L522-L544), a user can trigger scenarios where this quantity is 0.", "cve": "CVE-2021-29549", "id": "pyup.io-56271", "more_info_path": "/vulnerabilities/CVE-2021-29549/56271", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.5.0, 2.4.2, 2.3.3, 2.2.3 and 2.1.4 include a fix for CVE-2021-29548: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the op's contract (https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization).", "cve": "CVE-2021-29548", "id": "pyup.io-56263", "more_info_path": "/vulnerabilities/CVE-2021-29548/56263", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29552: An attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar. Since the tensor is empty the `CHECK` involved in `.scalar()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination.", "cve": "CVE-2021-29552", "id": "pyup.io-56262", "more_info_path": "/vulnerabilities/CVE-2021-29552/56262", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29539: TensorFlow is an end-to-end open source platform for machine learning. Calling `tf.raw_ops.ImmutableConst`(https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars. We have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. If using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument.", "cve": "CVE-2021-29539", "id": "pyup.io-56274", "more_info_path": "/vulnerabilities/CVE-2021-29539/56274", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'tf.raw_ops.EncodePng'. See CVE-2021-29531.", "cve": "CVE-2021-29531", "id": "pyup.io-56268", "more_info_path": "/vulnerabilities/CVE-2021-29531/56268", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by invalid validation in 'SparseMatrixSparseCholesky'. See CVE-2021-29530.", "cve": "CVE-2021-29530", "id": "pyup.io-56253", "more_info_path": "/vulnerabilities/CVE-2021-29530/56253", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix fixes a heap buffer overflow caused by rounding. See CVE-2021-29529.", "cve": "CVE-2021-29529", "id": "pyup.io-56261", "more_info_path": "/vulnerabilities/CVE-2021-29529/56261", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a heap buffer overflow in 'Conv3DBackprop*'. See CVE-2021-29520.", "cve": "CVE-2021-29520", "id": "pyup.io-56265", "more_info_path": "/vulnerabilities/CVE-2021-29520/56265", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a 'CHECK'-fail in 'AddManySparseToTensorsMap'. See CVE-2021-29523.", "cve": "CVE-2021-29523", "id": "pyup.io-56260", "more_info_path": "/vulnerabilities/CVE-2021-29523/56260", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 includes a fix for CVE-2021-29533: An attacker can trigger a denial of service via a 'CHECK' failure by passing an empty image to 'tf.raw_ops.DrawBoundingBoxes'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/ea34a18dc3f5c8d80a40ccca1404f343b5d55f91/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L148-L165) uses 'CHECK_*' assertions instead of 'OP_REQUIRES' to validate user controlled inputs. Whereas 'OP_REQUIRES' allows returning an error condition back to the user, the 'CHECK_*' macros result in a crash if the condition is false, similar to 'assert'. In this case, 'height' is 0 from the 'images' input. This results in 'max_box_row_clamp' being negative and the assertion being falsified, followed by aborting program execution.", "cve": "CVE-2021-29533", "id": "pyup.io-56264", "more_info_path": "/vulnerabilities/CVE-2021-29533/56264", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv3DBackprop*'. See CVE-2021-29522.", "cve": "CVE-2021-29522", "id": "pyup.io-56256", "more_info_path": "/vulnerabilities/CVE-2021-29522/56256", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a 'CHECK'-fail in 'SparseCross' caused by type confusion. See CVE-2021-29519.", "cve": "CVE-2021-29519", "id": "pyup.io-56255", "more_info_path": "/vulnerabilities/CVE-2021-29519/56255", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix vulnerabilities where session operations in eager mode lead to null pointer dereferences. See CVE-2021-29518.", "cve": "CVE-2021-29518", "id": "pyup.io-56259", "more_info_path": "/vulnerabilities/CVE-2021-29518/56259", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29513: Calling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences. The conversion from Python array to C++ array (https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion.", "cve": "CVE-2021-29513", "id": "pyup.io-56267", "more_info_path": "/vulnerabilities/CVE-2021-29513/56267", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a segfault in 'SparseCountSparseOutput'. See CVE-2021-29521.", "cve": "CVE-2021-29521", "id": "pyup.io-56269", "more_info_path": "/vulnerabilities/CVE-2021-29521/56269", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29532: An attacker can force accesses outside the bounds of heap allocated arrays by passing in invalid tensor values to `tf.raw_ops.RaggedCross`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/efea03b38fb8d3b81762237dc85e579cc5fc6e87/tensorflow/core/kernels/ragged_cross_op.cc#L456-L487) lacks validation for the user supplied arguments. Each of the above branches call a helper function after accessing array elements via a `*_list[next_*]` pattern, followed by incrementing the `next_*` index. However, as there is no validation that the `next_*` values are in the valid range for the corresponding `*_list` arrays, this results in heap OOB reads.", "cve": "CVE-2021-29532", "id": "pyup.io-56257", "more_info_path": "/vulnerabilities/CVE-2021-29532/56257", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29538: An attacker can cause a division by zero to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments). If all shapes are empty then 'work_unit_size' is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service.", "cve": "CVE-2021-29538", "id": "pyup.io-56270", "more_info_path": "/vulnerabilities/CVE-2021-29538/56270", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a stack overflow in 'ParseAttrValue' with nested tensors. See CVE-2021-29615.", "cve": "CVE-2021-29615", "id": "pyup.io-56273", "more_info_path": "/vulnerabilities/CVE-2021-29615/56273", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29535: An attacker can cause a heap buffer overflow in 'QuantizedMul' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/87cf4d3ea9949051e50ca3f071fc909538a51cd0/tensorflow/core/kernels/quantized_mul_op.cc#L287-L290) assumes that the 4 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29535", "id": "pyup.io-56252", "more_info_path": "/vulnerabilities/CVE-2021-29535/56252", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'StringNGrams'. See CVE-2021-29541.", "cve": "CVE-2021-29541", "id": "pyup.io-56251", "more_info_path": "/vulnerabilities/CVE-2021-29541/56251", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'StringNGrams'. See CVE-2021-29542.", "cve": "CVE-2021-29542", "id": "pyup.io-56250", "more_info_path": "/vulnerabilities/CVE-2021-29542/56250", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29536: An attacker can cause a heap buffer overflow in 'QuantizedReshape' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/a324ac84e573fba362a5e53d4e74d5de6729933e/tensorflow/core/kernels/quantized_reshape_op.cc#L38-L55) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29536", "id": "pyup.io-56249", "more_info_path": "/vulnerabilities/CVE-2021-29536/56249", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29544: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.QuantizeAndDequantizeV4Grad'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the 'input_*' tensors. In turn, this results in the tensors being passes as they are to 'QuantizeAndDequantizePerChannelGradientImpl' (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306). However, the 'vec' method, requires the rank to 1 and triggers a 'CHECK' failure otherwise.", "cve": "CVE-2021-29544", "id": "pyup.io-56248", "more_info_path": "/vulnerabilities/CVE-2021-29544/56248", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29543: An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks.", "cve": "CVE-2021-29543", "id": "pyup.io-56247", "more_info_path": "/vulnerabilities/CVE-2021-29543/56247", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29540: TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L495-L497) computes the size of the filter tensor but does not validate that it matches the number of elements in 'filter_sizes'. Later, when reading/writing to this buffer, code uses the value computed here, instead of the number of elements in the tensor.", "cve": "CVE-2021-29540", "id": "pyup.io-56246", "more_info_path": "/vulnerabilities/CVE-2021-29540/56246", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update its dependency 'curl' to version 7.76.0 to handle CVE-2020-8169.", "cve": "CVE-2020-8169", "id": "pyup.io-56245", "more_info_path": "/vulnerabilities/CVE-2020-8169/56245", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a reference binding to null pointer in 'MatrixDiag*' ops. See CVE-2021-29515.", "cve": "CVE-2021-29515", "id": "pyup.io-56242", "more_info_path": "/vulnerabilities/CVE-2021-29515/56242", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in 'Conv3D'. See CVE-2021-29517.", "cve": "CVE-2021-29517", "id": "pyup.io-56244", "more_info_path": "/vulnerabilities/CVE-2021-29517/56244", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix fixes a null pointer dereference via invalid Ragged Tensors. See CVE-2021-29516.", "cve": "CVE-2021-29516", "id": "pyup.io-56243", "more_info_path": "/vulnerabilities/CVE-2021-29516/56243", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's convolution code. See CVE-2021-29594.", "cve": "CVE-2021-29594", "id": "pyup.io-56240", "more_info_path": "/vulnerabilities/CVE-2021-29594/56240", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'EmbeddingLookup'. See CVE-2021-29596.", "cve": "CVE-2021-29596", "id": "pyup.io-56241", "more_info_path": "/vulnerabilities/CVE-2021-29596/56241", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29558: An attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset.", "cve": "CVE-2021-29558", "id": "pyup.io-56239", "more_info_path": "/vulnerabilities/CVE-2021-29558/56239", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29551: The implementation of 'MatrixTriangularSolve' (https://github.com/tensorflow/tensorflow/blob/8cae746d8449c7dda5298327353d68613f16e798/tensorflow/core/kernels/linalg/matrix_triangular_solve_op_impl.h#L160-L240) fails to terminate kernel execution if one validation condition fails.", "cve": "CVE-2021-29551", "id": "pyup.io-56237", "more_info_path": "/vulnerabilities/CVE-2021-29551/56237", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29545: An attacker can trigger a denial of service via a 'CHECK'-fail in converting sparse tensors to CSR Sparse matrices. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/800346f2c03a27e182dd4fba48295f65e7790739/tensorflow/core/kernels/sparse/kernels.cc#L66) does a double redirection to access an element of an array allocated on the heap. If the value at 'indices(i, 0)' is such that 'indices(i, 0) + 1' is outside the bounds of 'csr_row_ptr', this results in writing outside of bounds of heap allocated data.", "cve": "CVE-2021-29545", "id": "pyup.io-56238", "more_info_path": "/vulnerabilities/CVE-2021-29545/56238", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in TFLite's 'Reshape' operator. See CVE-2021-29592.", "cve": "CVE-2021-29592", "id": "pyup.io-56236", "more_info_path": "/vulnerabilities/CVE-2021-29592/56236", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an undefined behavior in 'MaxPool3DGradGrad'. See CVE-2021-29574.", "cve": "CVE-2021-29574", "id": "pyup.io-56235", "more_info_path": "/vulnerabilities/CVE-2021-29574/56235", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29617: An attacker can cause a denial of service via `CHECK`-fail in `tf.strings.substr` with invalid arguments.", "cve": "CVE-2021-29617", "id": "pyup.io-56233", "more_info_path": "/vulnerabilities/CVE-2021-29617/56233", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 include a fix for CVE-2021-29512: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433). Before the 'for' loop, 'batch_idx' is set to 0. The user controls the 'splits' array, making it contain only one element, 0. Thus, the code in the 'while' loop would increment 'batch_idx' and then try to read 'splits(1)', which is outside of bounds.", "cve": "CVE-2021-29512", "id": "pyup.io-56234", "more_info_path": "/vulnerabilities/CVE-2021-29512/56234", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a segfault in 'CTCBeamSearchDecoder'. See CVE-2021-29581.", "cve": "CVE-2021-29581", "id": "pyup.io-56232", "more_info_path": "/vulnerabilities/CVE-2021-29581/56232", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'tf.raw_ops.CTCLoss'. See CVE-2021-29613.", "cve": "CVE-2021-29613", "id": "pyup.io-56231", "more_info_path": "/vulnerabilities/CVE-2021-29613/56231", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29556: An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.Reverse`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/36229ea9e9451dac14a8b1f4711c435a1d84a594/tensorflow/core/kernels/reverse_op.cc#L75-L76) performs a division based on the first dimension of the tensor argument.", "cve": "CVE-2021-29556", "id": "pyup.io-56230", "more_info_path": "/vulnerabilities/CVE-2021-29556/56230", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'Conv2D'. See CVE-2021-29526.", "cve": "CVE-2021-29526", "id": "pyup.io-56229", "more_info_path": "/vulnerabilities/CVE-2021-29526/56229", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'LoadAndRemapMatrix'. See CVE-2021-29561.", "cve": "CVE-2021-29561", "id": "pyup.io-56226", "more_info_path": "/vulnerabilities/CVE-2021-29561/56226", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'QuantizedConv2D'. See CVE-2021-29527.", "cve": "CVE-2021-29527", "id": "pyup.io-56227", "more_info_path": "/vulnerabilities/CVE-2021-29527/56227", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29595: The implementation of the `DepthToSpace` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69). An attacker can craft a model such that `params->block_size` is 0.", "cve": "CVE-2021-29595", "id": "pyup.io-56228", "more_info_path": "/vulnerabilities/CVE-2021-29595/56228", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29585: The TFLite computation for size of output after padding, `ComputeOutSize`(https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division. Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0.", "cve": "CVE-2021-29585", "id": "pyup.io-56225", "more_info_path": "/vulnerabilities/CVE-2021-29585/56225", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'TransposeConv'. See CVE-2021-29588.", "cve": "CVE-2021-29588", "id": "pyup.io-56217", "more_info_path": "/vulnerabilities/CVE-2021-29588/56217", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap out of bounds read in 'MaxPoolGradWithArgmax'. See CVE-2021-29570.", "cve": "CVE-2021-29570", "id": "pyup.io-56220", "more_info_path": "/vulnerabilities/CVE-2021-29570/56220", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29589: The reference implementation of the `GatherNd` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/reference_ops.h#L966). An attacker can craft a model such that `params` input would be an empty tensor. In turn, `params_shape.Dims(.)` would be zero, in at least one dimension.", "cve": "CVE-2021-29589", "id": "pyup.io-56221", "more_info_path": "/vulnerabilities/CVE-2021-29589/56221", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'BandedTriangularSolve'. See CVE-2021-29612.", "cve": "CVE-2021-29612", "id": "pyup.io-56219", "more_info_path": "/vulnerabilities/CVE-2021-29612/56219", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'SparseMatMul'. See CVE-2021-29557.", "cve": "CVE-2021-29557", "id": "pyup.io-56218", "more_info_path": "/vulnerabilities/CVE-2021-29557/56218", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'FusedBatchNorm'. See CVE-2021-29555.", "cve": "CVE-2021-29555", "id": "pyup.io-56223", "more_info_path": "/vulnerabilities/CVE-2021-29555/56223", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29514: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L446). Before the 'for' loop, 'batch_idx' is set to 0. The attacker sets 'splits(0)' to be 7, hence the 'while' loop does not execute and 'batch_idx' remains 0. This then results in writing to 'out(-1, bin)', which is before the heap allocated buffer for the output tensor.", "cve": "CVE-2021-29514", "id": "pyup.io-56224", "more_info_path": "/vulnerabilities/CVE-2021-29514/56224", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB access in unicode ops. See CVE-2021-29559.", "cve": "CVE-2021-29559", "id": "pyup.io-56222", "more_info_path": "/vulnerabilities/CVE-2021-29559/56222", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29608: TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in 'tf.raw_ops.RaggedTensorToTensor', an attacker can exploit an undefined behavior if input arguments are empty. The implementation (https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones. There are multiple 'DCHECK' validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything.", "cve": "CVE-2021-29608", "id": "pyup.io-56175", "more_info_path": "/vulnerabilities/CVE-2021-29608/56175", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'EditDistance'. See CVE-2021-29564.", "cve": "CVE-2021-29564", "id": "pyup.io-56191", "more_info_path": "/vulnerabilities/CVE-2021-29564/56191", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update 'curl' to '7.76.0' to handle CVE-2020-8177.", "cve": "CVE-2020-8177", "id": "pyup.io-56181", "more_info_path": "/vulnerabilities/CVE-2020-8177/56181", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update its dependency \"curl\" to v7.76.0 to include security fixes.", "cve": "CVE-2020-8231", "id": "pyup.io-56180", "more_info_path": "/vulnerabilities/CVE-2020-8231/56180", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB read in TFLite's implementation of 'Minimum' or 'Maximum'. See CVE-2021-29590.", "cve": "CVE-2021-29590", "id": "pyup.io-56205", "more_info_path": "/vulnerabilities/CVE-2021-29590/56205", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of hashtable lookup. See CVE-2021-29604.", "cve": "CVE-2021-29604", "id": "pyup.io-56194", "more_info_path": "/vulnerabilities/CVE-2021-29604/56194", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a integer overflow in TFLite memory allocation. See CVE-2021-29605.", "cve": "CVE-2021-29605", "id": "pyup.io-56188", "more_info_path": "/vulnerabilities/CVE-2021-29605/56188", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a integer overflow in TFLite concatentation. See CVE-2021-29601.", "cve": "CVE-2021-29601", "id": "pyup.io-56202", "more_info_path": "/vulnerabilities/CVE-2021-29601/56202", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'OneHot'. See CVE-2021-29600.", "cve": "CVE-2021-29600", "id": "pyup.io-56190", "more_info_path": "/vulnerabilities/CVE-2021-29600/56190", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in optimized pooling implementations in TFLite. See CVE-2021-29586.", "cve": "CVE-2021-29586", "id": "pyup.io-56204", "more_info_path": "/vulnerabilities/CVE-2021-29586/56204", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix fixes a heap OOB read in TFLite. See CVE-2021-29606.", "cve": "CVE-2021-29606", "id": "pyup.io-56167", "more_info_path": "/vulnerabilities/CVE-2021-29606/56167", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29571: The implementation of 'tf.raw_ops.MaxPoolGradWithArgmax' can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation (https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of 'boxes' input is 4, as required by the op (https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption. If the last dimension in 'boxes' is less than 4, accesses similar to 'tboxes(b, bb, 3)' will access data outside of bounds. Further during code execution there are also writes to these indices.", "cve": "CVE-2021-29571", "id": "pyup.io-56198", "more_info_path": "/vulnerabilities/CVE-2021-29571/56198", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB write in TFLite. See CVE-2021-29603.", "cve": "CVE-2021-29603", "id": "pyup.io-56193", "more_info_path": "/vulnerabilities/CVE-2021-29603/56193", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'tf.raw_ops.IRFFT'. See CVE-2021-29562.", "cve": "CVE-2021-29562", "id": "pyup.io-56168", "more_info_path": "/vulnerabilities/CVE-2021-29562/56168", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'AvgPool3DGrad'. See CVE-2021-29577.", "cve": "CVE-2021-29577", "id": "pyup.io-56185", "more_info_path": "/vulnerabilities/CVE-2021-29577/56185", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29566: An attacker can write outside the bounds of heap allocated arrays by passing invalid arguments to 'tf.raw_ops.Dilation2DBackpropInput'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/afd954e65f15aea4d438d0a219136fc4a63a573d/tensorflow/core/kernels/dilation_ops.cc#L321-L322) does not validate before writing to the output array. The values for 'h_out' and 'w_out' are guaranteed to be in range for 'out_backprop' (as they are loop indices bounded by the size of the array). However, there are no similar guarantees relating 'h_in_max'/'w_in_max' and 'in_backprop'.", "cve": "CVE-2021-29566", "id": "pyup.io-56195", "more_info_path": "/vulnerabilities/CVE-2021-29566/56195", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu versions 2.5.0, 2.4.2, 2.3.3, 2.2.3 and 2.1.4 updates its dependency \"curl\" to a secure version (7.76.0).", "cve": "CVE-2020-8285", "id": "pyup.io-56201", "more_info_path": "/vulnerabilities/CVE-2020-8285/56201", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 updates 'curl' to '7.76.0' to handle CVE-2020-8286: curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response.", "cve": "CVE-2020-8286", "id": "pyup.io-56182", "more_info_path": "/vulnerabilities/CVE-2020-8286/56182", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a segfault in 'tf.raw_ops.SparseCountSparseOutput'. See CVE-2021-29619.", "cve": "CVE-2021-29619", "id": "pyup.io-56177", "more_info_path": "/vulnerabilities/CVE-2021-29619/56177", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'BatchToSpaceNd'. See CVE-2021-29593.", "cve": "CVE-2021-29593", "id": "pyup.io-56183", "more_info_path": "/vulnerabilities/CVE-2021-29593/56183", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29616: The implementation of TrySimplify (https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/grappler/optimizers/arithmetic_optimizer.cc#L390-L401) has undefined behavior due to dereferencing a null pointer in corner cases that result in optimizing a node with no inputs.", "cve": "CVE-2021-29616", "id": "pyup.io-56173", "more_info_path": "/vulnerabilities/CVE-2021-29616/56173", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseReshape'. See CVE-2021-29611.", "cve": "CVE-2021-29611", "id": "pyup.io-56210", "more_info_path": "/vulnerabilities/CVE-2021-29611/56210", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29610: The validation in 'tf.raw_ops.QuantizeAndDequantizeV2' allows invalid values for 'axis' argument:. The validation (https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses '||' to mix two different conditions. If 'axis_ < -1' the condition in 'OP_REQUIRES' will still be true, but this value of 'axis_' results in heap underflow. This allows attackers to read/write to other data on the heap.", "cve": "CVE-2021-29610", "id": "pyup.io-56216", "more_info_path": "/vulnerabilities/CVE-2021-29610/56216", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'MaxPoolGrad'. See CVE-2021-29579.", "cve": "CVE-2021-29579", "id": "pyup.io-56187", "more_info_path": "/vulnerabilities/CVE-2021-29579/56187", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseAdd'. See CVE-2021-29609.", "cve": "CVE-2021-29609", "id": "pyup.io-56176", "more_info_path": "/vulnerabilities/CVE-2021-29609/56176", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'FractionalAvgPoolGrad'. See CVE-2021-29578.", "cve": "CVE-2021-29578", "id": "pyup.io-56178", "more_info_path": "/vulnerabilities/CVE-2021-29578/56178", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a stack overflow due to looping TFLite subgraph. See CVE-2021-29591.", "cve": "CVE-2021-29591", "id": "pyup.io-56164", "more_info_path": "/vulnerabilities/CVE-2021-29591/56164", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29587: TensorFlow is an end-to-end open source platform for machine learning. The `Prepare` step of the `SpaceToDepth` TFLite operator does not check for 0 before division (https://github.com/tensorflow/tensorflow/blob/5f7975d09eac0f10ed8a17dbb6f5964977725adc/tensorflow/lite/kernels/space_to_depth.cc#L63-L67). An attacker can craft a model such that `params->block_size` would be zero.", "cve": "CVE-2021-29587", "id": "pyup.io-56196", "more_info_path": "/vulnerabilities/CVE-2021-29587/56196", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29583: The implementation of 'tf.raw_ops.FusedBatchNorm' is vulnerable to a heap buffer overflow. If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers. The implementation(https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that 'scale', 'offset', 'mean' and 'variance' (the last two only when required) all have the same number of elements as the number of channels of 'x'. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary. If the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior.", "cve": "CVE-2021-29583", "id": "pyup.io-56174", "more_info_path": "/vulnerabilities/CVE-2021-29583/56174", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'MaxPoolGradWithArgmax'. See CVE-2021-29573.", "cve": "CVE-2021-29573", "id": "pyup.io-56203", "more_info_path": "/vulnerabilities/CVE-2021-29573/56203", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an undefined behavior and a 'CHECK'-fail in 'FractionalMaxPoolGrad'. See CVE-2021-29580.", "cve": "CVE-2021-29580", "id": "pyup.io-56211", "more_info_path": "/vulnerabilities/CVE-2021-29580/56211", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'MaxPool3DGradGrad'. See CVE-2021-29576.", "cve": "CVE-2021-29576", "id": "pyup.io-56189", "more_info_path": "/vulnerabilities/CVE-2021-29576/56189", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail due to integer overflow. See CVE-2021-29584.", "cve": "CVE-2021-29584", "id": "pyup.io-56163", "more_info_path": "/vulnerabilities/CVE-2021-29584/56163", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'SpaceToBatchNd'. See CVE-2021-29597.", "cve": "CVE-2021-29597", "id": "pyup.io-56169", "more_info_path": "/vulnerabilities/CVE-2021-29597/56169", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.5.0, 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29572: The implementation of `tf.raw_ops.SdcaOptimizer` triggers undefined behavior due to dereferencing a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/60a45c8b6192a4699f2e2709a2645a751d435cc3/tensorflow/core/kernels/sdca_internal.cc) does not validate that the user supplied arguments satisfy all constraints expected by the op(https://www.tensorflow.org/api_docs/python/tf/raw_ops/SdcaOptimizer).", "cve": "CVE-2021-29572", "id": "pyup.io-56200", "more_info_path": "/vulnerabilities/CVE-2021-29572/56200", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap out of bounds read in 'RequantizationRange'. See CVE-2021-29569.", "cve": "CVE-2021-29569", "id": "pyup.io-56199", "more_info_path": "/vulnerabilities/CVE-2021-29569/56199", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'SparseFillEmptyRows'. See CVE-2021-29565.", "cve": "CVE-2021-29565", "id": "pyup.io-56172", "more_info_path": "/vulnerabilities/CVE-2021-29565/56172", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29546: TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger an integer division by zero undefined behavior in `tf.raw_ops.QuantizedBiasAdd`. This is because the implementation of the Eigen kernel (https://github.com/tensorflow/tensorflow/blob/61bca8bd5ba8a68b2d97435ddfafcdf2b85672cd/tensorflow/core/kernels/quantization_utils.h#L812-L849) does a division by the number of elements of the smaller input (based on shape) without checking that this is not zero.", "cve": "CVE-2021-29546", "id": "pyup.io-56213", "more_info_path": "/vulnerabilities/CVE-2021-29546/56213", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an overflow and a denial of service in 'tf.raw_ops.ReverseSequence'. See CVE-2021-29575.", "cve": "CVE-2021-29575", "id": "pyup.io-56165", "more_info_path": "/vulnerabilities/CVE-2021-29575/56165", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29563: An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`. Eigen code operating on an empty matrix can trigger on an assertion and will cause program termination.", "cve": "CVE-2021-29563", "id": "pyup.io-56207", "more_info_path": "/vulnerabilities/CVE-2021-29563/56207", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29618: Passing a complex argument to `tf.transpose` at the same time as passing 'conjugate=True' argument results in a crash.", "cve": "CVE-2021-29618", "id": "pyup.io-56214", "more_info_path": "/vulnerabilities/CVE-2021-29618/56214", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'DepthwiseConv'. See CVE-2021-29602.", "cve": "CVE-2021-29602", "id": "pyup.io-56179", "more_info_path": "/vulnerabilities/CVE-2021-29602/56179", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'Split'. See CVE-2021-29599.", "cve": "CVE-2021-29599", "id": "pyup.io-56170", "more_info_path": "/vulnerabilities/CVE-2021-29599/56170", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB in 'QuantizeAndDequantizeV3'. See CVE-2021-29553.", "cve": "CVE-2021-29553", "id": "pyup.io-56209", "more_info_path": "/vulnerabilities/CVE-2021-29553/56209", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29560: An attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel. Since the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when 'parent_output_index' is shorter than 'row_split'.", "cve": "CVE-2021-29560", "id": "pyup.io-56215", "more_info_path": "/vulnerabilities/CVE-2021-29560/56215", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29550: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values. The user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor operation results in `output_size[i]` being 0. The `DCHECK_GT` line is a no-op outside of debug mode, so in released versions of TF this does not trigger. Later, these computed values are used as arguments (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to `GeneratePoolingSequence`(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation. Since `output_length` can be 0, this results in runtime crashing.", "cve": "CVE-2021-29550", "id": "pyup.io-56212", "more_info_path": "/vulnerabilities/CVE-2021-29550/56212", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB read in 'tf.raw_ops.Dequantize'. See CVE-2021-29582.", "cve": "CVE-2021-29582", "id": "pyup.io-56166", "more_info_path": "/vulnerabilities/CVE-2021-29582/56166", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseSparseMinimum'. See CVE-2021-29607.", "cve": "CVE-2021-29607", "id": "pyup.io-56171", "more_info_path": "/vulnerabilities/CVE-2021-29607/56171", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'DenseCountSparseOutput'. See CVE-2021-29554.", "cve": "CVE-2021-29554", "id": "pyup.io-56184", "more_info_path": "/vulnerabilities/CVE-2021-29554/56184", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29547: An attacker can cause a segfault and denial of service via accessing data outside of bounds in 'tf.raw_ops.QuantizedBatchNormWithGlobalNormalization'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc#L176-L189) assumes the inputs are not empty. If any of these inputs is empty, '.flat()' is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds.", "cve": "CVE-2021-29547", "id": "pyup.io-56192", "more_info_path": "/vulnerabilities/CVE-2021-29547/56192", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'SVDF'. See CVE-2021-29598.", "cve": "CVE-2021-29598", "id": "pyup.io-56206", "more_info_path": "/vulnerabilities/CVE-2021-29598/56206", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger undefined behavior by binding to null pointer in 'tf.raw_ops.ParameterizedTruncatedNormal'. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/3f6fe4dfef6f57e768260b48166c27d148f3015f/tensorflow/core/kernels/parameterized_truncated_normal_op.cc#L630) does not validate input arguments before accessing the first element of 'shape'. If 'shape' argument is empty, then 'shape_tensor.flat()' is an empty array. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.", "cve": "CVE-2021-29568", "id": "pyup.io-56197", "more_info_path": "/vulnerabilities/CVE-2021-29568/56197", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'QuantizedMul'. See CVE-2021-29528.", "cve": "CVE-2021-29528", "id": "pyup.io-56208", "more_info_path": "/vulnerabilities/CVE-2021-29528/56208", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 update its dependency \"curl\" to handle CVE-2020-8284.", "cve": "CVE-2020-8284", "id": "pyup.io-56186", "more_info_path": "/vulnerabilities/CVE-2020-8284/56186", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37691: In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). The Tensorflow team has patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9.", "cve": "CVE-2021-37691", "id": "pyup.io-56162", "more_info_path": "/vulnerabilities/CVE-2021-37691/56162", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37645: In affected versions the implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit 96f364a1ca3009f98980021c4b32be5fdcca33a1.", "cve": "CVE-2021-37645", "id": "pyup.io-56161", "more_info_path": "/vulnerabilities/CVE-2021-37645/56161", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37688: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer. The Tensorflow team has patched the issue in GitHub commit 15691e456c7dc9bd6be203b09765b063bf4a380c.", "cve": "CVE-2021-37688", "id": "pyup.io-56160", "more_info_path": "/vulnerabilities/CVE-2021-37688/56160", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu versions 2.5.1 and 2.6.0 include a fix for CVE-2021-37692:\nIn affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, \"C.TF_TString_Dealloc\" is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until \"NewTensor\" returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. The Tensorflow team has patched the issue in GitHub commit:\nhttps://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22\nhttps://github.com/tensorflow/tensorflow/pull/50508\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cmgw-8vpc-rc59", "cve": "CVE-2021-37692", "id": "pyup.io-56158", "more_info_path": "/vulnerabilities/CVE-2021-37692/56158", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu 2.5.1 and 2.6.0 include a fix for CVE-2021-37640: In affected versions the implementation of 'tf.raw_ops.SparseReshape' can be made to trigger an integral division by 0 exception. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements. The reshape functor (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0. The Tensorflow team has patched the issue in GitHub commit 4923de56ec94fff7770df259ab7f2288a74feb41.", "cve": "CVE-2021-37640", "id": "pyup.io-56159", "more_info_path": "/vulnerabilities/CVE-2021-37640/56159", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-gpu versions 2.3.4, 2.4.3, 2.5.1, and 2.6.0 update its dependency \"curl\" to include a fix for CVE-2021-22898", "cve": "CVE-2021-22898", "id": "pyup.io-56157", "more_info_path": "/vulnerabilities/CVE-2021-22898/56157", "specs": [ ">=2.6.0a1,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0a1,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37657: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. The Tensorflow team has checked that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit f2a673bd34f0d64b8e40a551ac78989d16daad09.", "cve": "CVE-2021-37657", "id": "pyup.io-56146", "more_info_path": "/vulnerabilities/CVE-2021-37657/56146", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37663:\nIn affected versions, due to incomplete validation in \"tf.raw_ops.QuantizeV2\", an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that \"min_range\" and \"max_range\" both have the same non-zero number of elements. If \"axis\" is provided (i.e., not \"-1\"), then validation should check that it is a value in range for the rank of \"input\" tensor and then the lengths of \"min_range\" and \"max_range\" inputs match the \"axis\" dimension of the \"input\" tensor. The Tensorflow team has patched the issue in GitHub commit 6da6620efad397c85493b8f8667b821403516708. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g25h-jr74-qp5j\nhttps://github.com/tensorflow/tensorflow/commit/6da6620efad397c85493b8f8667b821403516708", "cve": "CVE-2021-37663", "id": "pyup.io-56148", "more_info_path": "/vulnerabilities/CVE-2021-37663/56148", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37685: In affected versions TFLite's 'expand_dims.cc' (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data. If 'axis' is a large negative value (e.g., '-100000'), then after the first 'if' it would still be negative. The check following the 'if' statement will pass and the 'for' loop would read one element before the start of 'input_dims.data' (when 'i = 0'). The Tensorflow team has patched the issue in GitHub commit d94ffe08a65400f898241c0374e9edc6fa8ed257.", "cve": "CVE-2021-37685", "id": "pyup.io-56149", "more_info_path": "/vulnerabilities/CVE-2021-37685/56149", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37661: In affected versions an attacker can cause a denial of service in 'boosted_trees_create_quantile_stream_resource' by using negative arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that 'num_streams' only contains non-negative numbers. In turn, this results in using this value to allocate memory (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40). However, 'reserve' receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library. The Tensorflow team has patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992.", "cve": "CVE-2021-37661", "id": "pyup.io-56150", "more_info_path": "/vulnerabilities/CVE-2021-37661/56150", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37668:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.UnravelIndex\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by \"dims\" is not empty. Hence, if one element of \"dims\" is 0, the implementation does a division by 0. The Tensorflow team has patched the issue in GitHub commit a776040a5e7ebf76eeb7eb923bf1ae417dd4d233.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2wmv-37vq-52g5\nhttps://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233", "cve": "CVE-2021-37668", "id": "pyup.io-56147", "more_info_path": "/vulnerabilities/CVE-2021-37668/56147", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37665:\nIn affected versions, due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the \"input\" tensor. A similar issue occurs in \"MklRequantizePerChannelOp\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments. The Tensorflow team has patched the issue in GitHub commit 9e62869465573cb2d9b5053f1fa02a81fce21d69 and in the Github commit 203214568f5bc237603dbab6e1fd389f1572f5c9.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v82p-hv3v-p6qp\nhttps://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9\nhttps://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69", "cve": "CVE-2021-37665", "id": "pyup.io-56151", "more_info_path": "/vulnerabilities/CVE-2021-37665/56151", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37687: In affected versions TFLite's 'GatherNd' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation. Hence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in 'indices'. Similar issue exists in 'Gather' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc). The Tensorflow team has patched the issue in GitHub commits bb6a0383ed553c286f87ca88c207f6774d5c4a8f and eb921122119a6b6e470ee98b89e65d721663179d.", "cve": "CVE-2021-37687", "id": "pyup.io-56153", "more_info_path": "/vulnerabilities/CVE-2021-37687/56153", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37676: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.SparseFillEmptyRows'. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors. The Tensorflow team has patched the issue in GitHub commit 578e634b4f1c1c684d4b4294f9e5281b2133b3ed.", "cve": "CVE-2021-37676", "id": "pyup.io-56154", "more_info_path": "/vulnerabilities/CVE-2021-37676/56154", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37675: In affected versions most implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations. The Tensorflow team has patched the issue in GitHub commit 8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4.", "cve": "CVE-2021-37675", "id": "pyup.io-56152", "more_info_path": "/vulnerabilities/CVE-2021-37675/56152", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37660: In affected versions an attacker can cause a floating point exception by calling inplace operations with crafted arguments that would result in a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/inplace_ops.cc#L283) has a logic error: it should skip processing if 'x' and 'v' are empty but the code uses '||' instead of '&&'. The Tensorflow team has patched the issue in GitHub commit e86605c0a336c088b638da02135ea6f9f6753618.", "cve": "CVE-2021-37660", "id": "pyup.io-56156", "more_info_path": "/vulnerabilities/CVE-2021-37660/56156", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37653: In affected versions an attacker can trigger a crash via a floating point exception in 'tf.raw_ops.ResourceGather'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, 'batch_size', and then divides by it without checking that this value is not 0. The Tensorflow team has patched the issue in GitHub commit ac117ee8a8ea57b73d34665cdf00ef3303bc0b11.", "cve": "CVE-2021-37653", "id": "pyup.io-56155", "more_info_path": "/vulnerabilities/CVE-2021-37653/56155", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37662: In affected versions an attacker can generate undefined behavior via a reference binding to nullptr in 'BoostedTreesCalculateBestGainsPerFeature' and similar attack can occur in 'BoostedTreesCalculateBestFeatureSplitV2'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values. The Tensorflow team has patched the issue in GitHub commit 9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad and in commit 429f009d2b2c09028647dd4bb7b3f6f414bbaad7.", "cve": "CVE-2021-37662", "id": "pyup.io-56139", "more_info_path": "/vulnerabilities/CVE-2021-37662/56139", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37646: In affected versions the implementation of 'tf.raw_ops.StringNGrams' is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls 'reserve' on a 'tstring' with a value that sometimes can be negative if user supplies negative 'ngram_widths'. The 'reserve' method calls 'TF_TString_Reserve' which has an 'unsigned long' argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5.", "cve": "CVE-2021-37646", "id": "pyup.io-56144", "more_info_path": "/vulnerabilities/CVE-2021-37646/56144", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37641: In affected versions if the arguments to 'tf.raw_ops.RaggedGather' don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by 'params_nested_splits' is not an empty list of tensors. The Tensorflow team has patched the issue in GitHub commit a2b743f6017d7b97af1fe49087ae15f0ac634373.", "cve": "CVE-2021-37641", "id": "pyup.io-56141", "more_info_path": "/vulnerabilities/CVE-2021-37641/56141", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37684: In affected versions the implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695 (https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).", "cve": "CVE-2021-37684", "id": "pyup.io-56138", "more_info_path": "/vulnerabilities/CVE-2021-37684/56138", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37681: In affected versions the implementation of SVDF in TFLite is vulnerable to a null pointer error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313). The 'GetVariableInput' function (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but 'GetTensorData' assumes that the argument is always a valid tensor. Furthermore, because 'GetVariableInput' calls 'GetMutableInput' (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return 'nullptr', the 'tensor->is_variable' expression can also trigger a null pointer exception. The Tensorflow team has patched the issue in GitHub commit 5b048e87e4e55990dae6b547add4dae59f4e1c76.", "cve": "CVE-2021-37681", "id": "pyup.io-56142", "more_info_path": "/vulnerabilities/CVE-2021-37681/56142", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37666: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToVariant'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty. The Tensorflow team has patched the issue in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612.", "cve": "CVE-2021-37666", "id": "pyup.io-56145", "more_info_path": "/vulnerabilities/CVE-2021-37666/56145", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37644: In affected versions providing a negative element to 'num_elements' list argument of 'tf.raw_ops.TensorListReserve' causes the runtime to abort the process due to reallocating a 'std::vector' to have a negative number of elements. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls 'std::vector.resize()' with the new size controlled by input given by the user, without checking that this input is valid. The Tensorflow team has patched the issue in GitHub commit 8a6e874437670045e6c7dc6154c7412b4a2135e2.", "cve": "CVE-2021-37644", "id": "pyup.io-56143", "more_info_path": "/vulnerabilities/CVE-2021-37644/56143", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37643: If a user does not provide a valid padding value to 'tf.raw_ops.MatrixDiagPartOp', then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from. The Tensorflow team has patched the issue in GitHub commit 482da92095c4d48f8784b1f00dda4f81c28d2988.", "cve": "CVE-2021-37643", "id": "pyup.io-56140", "more_info_path": "/vulnerabilities/CVE-2021-37643/56140", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37682:\nIn affected versions all TFLite operations that use quantization can be made to use unitialized values. (For example, https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200). The issue stems from the fact that \"quantization.params\" is only valid if \"quantization.type\" is different that \"kTfLiteNoQuantization\". However, these checks are missing in large parts of the code. The Tensorflow team has patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4c4g-crqm-xrxw\nhttps://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5\nhttps://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887\nhttps://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538", "cve": "CVE-2021-37682", "id": "pyup.io-56136", "more_info_path": "/vulnerabilities/CVE-2021-37682/56136", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37690:\nIn affected versions when running shape functions, some functions (such as 'MutableHashTableShape') produce extra output information in the form of a 'ShapeAndType' struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault. 'ShapeRefiner' is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but the Tensorflow team was not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types. The Tensorflow team has patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3hxh-8cp2-g4hg\nhttps://github.com/tensorflow/tensorflow/commit/ee119d4a498979525046fba1c3dd3f13a039fbb1", "cve": "CVE-2021-37690", "id": "pyup.io-56137", "more_info_path": "/vulnerabilities/CVE-2021-37690/56137", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37669:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.NonMaxSuppressionV5\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a \"std::vector\". However, as \"std::vector::resize\" takes the size argument as a \"size_t\" and \"output_size\" is an \"int\", there is an implicit conversion to unsigned. If the attacker supplies a negative value, this conversion results in a crash. A similar issue occurs in \"CombinedNonMaxSuppression\". The Tensorflow team has patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c\nhttps://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d\nhttps://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58", "cve": "CVE-2021-37669", "id": "pyup.io-56133", "more_info_path": "/vulnerabilities/CVE-2021-37669/56133", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37672:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.SdcaOptimizerV2\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of \"example_labels\" is the same as the number of examples. The Tensorflow team has patched the issue in GitHub commit a4e138660270e7599793fa438cd7b2fc2ce215a6.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hj3-vjjf-f5m7\nhttps://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6", "cve": "CVE-2021-37672", "id": "pyup.io-56124", "more_info_path": "/vulnerabilities/CVE-2021-37672/56124", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22876", "id": "pyup.io-56129", "more_info_path": "/vulnerabilities/CVE-2021-22876/56129", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22897", "id": "pyup.io-56128", "more_info_path": "/vulnerabilities/CVE-2021-22897/56128", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37650: In affected versions the implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types. The Tensorflow team has patched the issue in GitHub commit e0b6e58c328059829c3eb968136f17aa72b6c876.", "cve": "CVE-2021-37650", "id": "pyup.io-56131", "more_info_path": "/vulnerabilities/CVE-2021-37650/56131", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37670:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.UpperBound\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of \"sorted_input\" argument. A similar issue occurs in \"tf.raw_ops.LowerBound\". The Tensorflow team has patched the issue in GitHub commit 42459e4273c2e47a3232cc16c4f4fff3b3a35c38.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9697-98pf-4rw7\nhttps://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38", "cve": "CVE-2021-37670", "id": "pyup.io-56125", "more_info_path": "/vulnerabilities/CVE-2021-37670/56125", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. In affected versions the shape inference code for 'tf.raw_ops.Dequantize' has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments. The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses 'axis' to select between two different values for 'minmax_rank' which is then used to retrieve tensor dimensions. However, code assumes that 'axis' can be either '-1' or a value greater than '-1', with no validation for the other values. We have patched the issue in GitHub commit da857cfa0fde8f79ad0afdbc94e88b5d4bbec764. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.", "cve": "CVE-2021-37677", "id": "pyup.io-56134", "more_info_path": "/vulnerabilities/CVE-2021-37677/56134", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22901", "id": "pyup.io-56127", "more_info_path": "/vulnerabilities/CVE-2021-22901/56127", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37679:\nIn affected versions it is possible to nest a \"tf.map_fn\" within another \"tf.map_fn\" call. However, if the input tensor is a \"RaggedTensor\" and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap. The \"t\" and \"z\" outputs should be identical, however this is not the case. The last row of \"t\" contains data from the heap which can be used to leak other memory information. The bug lies in the conversion from a \"Variant\" tensor to a \"RaggedTensor\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions. The same implementation can result in data loss, if input tensor is tweaked. The Tensorflow team has patched the issue in GitHub commit 4e2565483d0ffcadc719bd44893fb7f609bb5f12.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g8wg-cjwc-xhhp\nhttps://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12", "cve": "CVE-2021-37679", "id": "pyup.io-56126", "more_info_path": "/vulnerabilities/CVE-2021-37679/56126", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a denial of service via a segmentation fault in 'tf.raw_ops.MaxPoolGrad' caused by missing validation. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the 'orig_input' and 'orig_output' tensors. The fixes for CVE-2021-29579 were incomplete. We have patched the issue in GitHub commit 136b51f10903e044308cf77117c0ed9871350475. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.", "cve": "CVE-2021-37674", "id": "pyup.io-56132", "more_info_path": "/vulnerabilities/CVE-2021-37674/56132", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37673:\nIn affected versions, an attacker can trigger a denial of service via a \"CHECK\"-fail in \"tf.raw_ops.MapStage\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the \"key\" input is a valid non-empty tensor. The Tensorflow team has patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-278g-rq84-9hmg\nhttps://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d", "cve": "CVE-2021-37673", "id": "pyup.io-56130", "more_info_path": "/vulnerabilities/CVE-2021-37673/56130", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37655: TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to 'tf.raw_ops.ResourceScatterUpdate'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of 'indices' and 'updates': instead of checking that the shape of 'indices' is a prefix of the shape of 'updates' (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. The Tensorflow team has patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f.", "cve": "CVE-2021-37655", "id": "pyup.io-56123", "more_info_path": "/vulnerabilities/CVE-2021-37655/56123", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-gpu version 2.3.4, 2.4.3, 2.5.1, 2.6.0 and 2.7.0 include a fix for CVE-2021-37678:\nIn affected versions, TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The implementation(https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses \"yaml.unsafe_load\" which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, the Tensorflow team has removed it for now. The Tensorflow team has patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r\nhttps://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012", "cve": "CVE-2021-37678", "id": "pyup.io-56135", "more_info_path": "/vulnerabilities/CVE-2021-37678/56135", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.7.0rc0,<2.7.0" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.7.0rc0,<2.7.0" }, { "advisory": "Tensorflow-gpu version 2.6.1 includes a fix for CVE-2021-41211: In affected versions, the shape inference code for 'QuantizeV2' can trigger a read outside of bounds of heap allocated array. This occurs whenever 'axis' is a negative value less than '-1'. In this case, we are accessing data before the start of a heap buffer. The code allows 'axis' to be an optional argument ('s' would contain an 'error::NOT_FOUND' error code). Otherwise, it assumes that 'axis' is a valid index into the dimensions of the 'input' tensor. If 'axis' is less than '-1' then this results in a heap OOB read. The fix is included in TensorFlow 2.7.0. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvgx-3v3q-m36c\nhttps://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244", "cve": "CVE-2021-41211", "id": "pyup.io-56122", "more_info_path": "/vulnerabilities/CVE-2021-41211/56122", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu version 2.6.1 includes a fix for CVE-2021-41220: In affected versions, the async implementation of 'CollectiveReduceV2' suffers from a memory leak and a use after free. This occurs due to the asynchronous computation and the fact that objects that have been 'std::move()'d are still accessed. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gpfh-jvf9-7wg5\nhttps://github.com/tensorflow/tensorflow/commit/ca38dab9d3ee66c5de06f11af9a4b1200da5ef75", "cve": "CVE-2021-41220", "id": "pyup.io-56121", "more_info_path": "/vulnerabilities/CVE-2021-41220/56121", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-gpu is an Open Source Machine Learning Framework. The TFG dialect of TensorFlow (MLIR) makes several assumptions about the incoming `GraphDef` before converting it to the MLIR-based dialect. If an attacker changes the `SavedModel` format on disk to invalidate these assumptions and the `GraphDef` is then converted to MLIR-based IR then they can cause a crash in the Python interpreter. Under certain scenarios, heap OOB read/writes are possible. These issues have been discovered via fuzzing and it is possible that more weaknesses exist. We will patch them as they are discovered.", "cve": "CVE-2022-23594", "id": "pyup.io-56031", "more_info_path": "/vulnerabilities/CVE-2022-23594/56031", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu versions 2.7.1 and 2.8.0 include a fix for CVE-2022-23590: A 'GraphDef' from a TensorFlow 'SavedModel' can be maliciously altered to cause a TensorFlow process to crash due to encountering a 'StatusOr' value that is an error and forcibly extracting the value from it.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pqrv-8r2f-7278", "cve": "CVE-2022-23590", "id": "pyup.io-56030", "more_info_path": "/vulnerabilities/CVE-2022-23590/56030", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Some versions of tensorflow-gpu are susceptible to a Denial of Service (DoS) through a vulnerability in the depthwise operations implementation, where a tensor's element count can overflow and cause an assertion failure. This issue arises from an incomplete mitigation of CVE-2021-41197.", "cve": "PVE-2024-99846", "id": "pyup.io-65574", "more_info_path": "/vulnerabilities/PVE-2024-99846/65574", "specs": [ ">=2.8.0,<2.8.1", ">=2.7.0,<2.7.2", ">=0,<2.6.4" ], "v": ">=2.8.0,<2.8.1,>=2.7.0,<2.7.2,>=0,<2.6.4" }, { "advisory": "Tensorflow-gpu 2.8.0 includes a fix for CVE-2022-23593: The 'simplifyBroadcast' function in the MLIR-TFRT infrastructure in TensorFlow is vulnerable to a segfault (hence, denial of service), if called with scalar shapes. If all shapes are scalar, then 'maxRank' is 0, so we build an empty 'SmallVector'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gwcx-jrx4-92w2", "cve": "CVE-2022-23593", "id": "pyup.io-56029", "more_info_path": "/vulnerabilities/CVE-2022-23593/56029", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-gpu version 2.8.0 includes a fix for CVE-2022-23592: TensorFlow's type inference can cause a heap out of bounds read as the bounds checking is done in a 'DCHECK' (which is a no-op during production). An attacker can control the 'input_idx' variable such that 'ix' would be larger than the number of values in 'node_t.args'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vq36-27g6-p492", "cve": "CVE-2022-23592", "id": "pyup.io-56028", "more_info_path": "/vulnerabilities/CVE-2022-23592/56028", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "TensorFlow is an open source platform for machine learning. In version 2.8.0, the 'TensorKey' hash function used total estimated 'AllocatedBytes()', which (a) is an estimate per tensor, and (b) is a very poor hash function for constants (e.g. 'int32_t'). It also tried to access individual tensor bytes through 'tensor.data()' of size 'AllocatedBytes()'. This led to ASAN failures because the 'AllocatedBytes()' is an estimate of total bytes allocated by a tensor, including any pointed-to constructs (e.g. strings), and does not refer to contiguous bytes in the '.data()' buffer. The discoverers could not use this byte vector anyway because types such as 'tstring' include pointers, whereas they needed to hash the string values themselves. This issue is patched in Tensorflow versions 2.9.0 and 2.8.1.", "cve": "CVE-2022-29210", "id": "pyup.io-55992", "more_info_path": "/vulnerabilities/CVE-2022-29210/55992", "specs": [ ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": ">=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" } ], "tensorflow-intel": [ { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36027: Segfault TFLite converter on per-channel quantized transposed convolutions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-79h2-q768-fpxr", "cve": "CVE-2022-36027", "id": "pyup.io-56575", "more_info_path": "/vulnerabilities/CVE-2022-36027/56575", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35965: Segfault in 'LowerBound' and 'UpperBound'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qxpx-j395-pw36", "cve": "CVE-2022-35965", "id": "pyup.io-56583", "more_info_path": "/vulnerabilities/CVE-2022-35965/56583", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36026: 'CHECK' fail in 'QuantizeAndDequantizeV3'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9cr2-8pwr-fhfq", "cve": "CVE-2022-36026", "id": "pyup.io-56572", "more_info_path": "/vulnerabilities/CVE-2022-36026/56572", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35988: 'CHECK' fail in 'tf.linalg.matrix_rank'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vqj-64pv-w55c", "cve": "CVE-2022-35988", "id": "pyup.io-56582", "more_info_path": "/vulnerabilities/CVE-2022-35988/56582", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35994: 'CHECK' fail in 'CollectiveGather'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fhfc-2q7x-929f", "cve": "CVE-2022-35994", "id": "pyup.io-56588", "more_info_path": "/vulnerabilities/CVE-2022-35994/56588", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35934: 'CHECK' failure in tf.reshape via overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f4w6-h4f5-wx45", "cve": "CVE-2022-35934", "id": "pyup.io-56553", "more_info_path": "/vulnerabilities/CVE-2022-35934/56553", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35967: Segfault in 'QuantizedAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v6h3-348g-6h5x", "cve": "CVE-2022-35967", "id": "pyup.io-56585", "more_info_path": "/vulnerabilities/CVE-2022-35967/56585", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36003: 'CHECK' fail in 'RandomPoissonV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cv2p-32v3-vhwq", "cve": "CVE-2022-36003", "id": "pyup.io-56550", "more_info_path": "/vulnerabilities/CVE-2022-36003/56550", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35937: OOB read in 'Gather_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pxrw-j2fv-hx3h", "cve": "CVE-2022-35937", "id": "pyup.io-56543", "more_info_path": "/vulnerabilities/CVE-2022-35937/56543", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36017: Segfault in 'Requantize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wqmc-pm8c-2jhc", "cve": "CVE-2022-36017", "id": "pyup.io-56548", "more_info_path": "/vulnerabilities/CVE-2022-36017/56548", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36016: 'CHECK'-fail in 'tensorflow::full_type::SubstituteFromAttrs'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g468-qj8g-vcjc", "cve": "CVE-2022-36016", "id": "pyup.io-56581", "more_info_path": "/vulnerabilities/CVE-2022-36016/56581", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36011: Null dereference on MLIR on empty function attributes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fv43-93gv-vm8f", "cve": "CVE-2022-36011", "id": "pyup.io-56574", "more_info_path": "/vulnerabilities/CVE-2022-36011/56574", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36002: 'CHECK' fail in 'Unbatch'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mh3m-62v7-68xg", "cve": "CVE-2022-36002", "id": "pyup.io-56554", "more_info_path": "/vulnerabilities/CVE-2022-36002/56554", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35973: Segfault in 'QuantizedMatMul'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-689c-r7h2-fv9v", "cve": "CVE-2022-35973", "id": "pyup.io-56570", "more_info_path": "/vulnerabilities/CVE-2022-35973/56570", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35999: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-37jf-mjv6-xfqw", "cve": "CVE-2022-35999", "id": "pyup.io-56592", "more_info_path": "/vulnerabilities/CVE-2022-35999/56592", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35998: 'CHECK' fail in 'EmptyTensorList'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhw4-wwr7-gjc5", "cve": "CVE-2022-35998", "id": "pyup.io-56563", "more_info_path": "/vulnerabilities/CVE-2022-35998/56563", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36015: Integer overflow in math ops. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rh87-q4vg-m45j", "cve": "CVE-2022-36015", "id": "pyup.io-56549", "more_info_path": "/vulnerabilities/CVE-2022-36015/56549", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36000: 'CHECK' fail in 'Eig'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqxc-pvf8-2w9v", "cve": "CVE-2022-36000", "id": "pyup.io-56566", "more_info_path": "/vulnerabilities/CVE-2022-36000/56566", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36004: 'CHECK' fail in 'tf.random.gamma'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv8m-8x97-937q", "cve": "CVE-2022-36004", "id": "pyup.io-56595", "more_info_path": "/vulnerabilities/CVE-2022-36004/56595", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35996: Floating point exception in 'Conv2D'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q5jv-m6qw-5g37", "cve": "CVE-2022-35996", "id": "pyup.io-56558", "more_info_path": "/vulnerabilities/CVE-2022-35996/56558", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35993: 'CHECK' fail in 'SetSize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wq6q-6m32-9rv9", "cve": "CVE-2022-35993", "id": "pyup.io-56578", "more_info_path": "/vulnerabilities/CVE-2022-35993/56578", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36019: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannel'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9j4v-pp28-mxv7", "cve": "CVE-2022-36019", "id": "pyup.io-56584", "more_info_path": "/vulnerabilities/CVE-2022-36019/56584", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35985: 'CHECK' fail in 'LRNGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9942-r22v-78cp", "cve": "CVE-2022-35985", "id": "pyup.io-56551", "more_info_path": "/vulnerabilities/CVE-2022-35985/56551", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35979: Segfault in 'QuantizedRelu' and 'QuantizedRelu6'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v7vw-577f-vp8x", "cve": "CVE-2022-35979", "id": "pyup.io-56547", "more_info_path": "/vulnerabilities/CVE-2022-35979/56547", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35974: Segfault in 'QuantizeDownAndShrinkRange'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vgvh-2pf4-jr2x", "cve": "CVE-2022-35974", "id": "pyup.io-56569", "more_info_path": "/vulnerabilities/CVE-2022-35974/56569", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35972: Segfault in 'QuantizedBiasAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4pc4-m9mj-v2r9", "cve": "CVE-2022-35972", "id": "pyup.io-56577", "more_info_path": "/vulnerabilities/CVE-2022-35972/56577", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35971: 'CHECK' fail in 'FakeQuantWithMinMaxVars'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9fpg-838v-wpv7", "cve": "CVE-2022-35971", "id": "pyup.io-56594", "more_info_path": "/vulnerabilities/CVE-2022-35971/56594", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35970: Segfault in 'QuantizedInstanceNorm'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g35r-369w-3fqp", "cve": "CVE-2022-35970", "id": "pyup.io-56587", "more_info_path": "/vulnerabilities/CVE-2022-35970/56587", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35964: Segfault in 'BlockLSTMGradV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f7r5-q7cx-h668", "cve": "CVE-2022-35964", "id": "pyup.io-56561", "more_info_path": "/vulnerabilities/CVE-2022-35964/56561", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35959: 'CHECK' failures in 'AvgPool3DGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wxjj-cgcx-r3vq", "cve": "CVE-2022-35959", "id": "pyup.io-56560", "more_info_path": "/vulnerabilities/CVE-2022-35959/56560", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35952: 'CHECK' failures in 'UnbatchGradOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h5vq-gw2c-pq47", "cve": "CVE-2022-35952", "id": "pyup.io-56545", "more_info_path": "/vulnerabilities/CVE-2022-35952/56545", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35940: Int overflow in 'RaggedRangeOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x989-q2pq-4q5x", "cve": "CVE-2022-35940", "id": "pyup.io-56589", "more_info_path": "/vulnerabilities/CVE-2022-35940/56589", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35939: OOB write in 'scatter_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-ffjm-4qwc-7cmf", "cve": "CVE-2022-35939", "id": "pyup.io-56544", "more_info_path": "/vulnerabilities/CVE-2022-35939/56544", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35969: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q2c3-jpmc-gfjx", "cve": "CVE-2022-35969", "id": "pyup.io-56552", "more_info_path": "/vulnerabilities/CVE-2022-35969/56552", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35984: 'CHECK' fail in 'ParameterizedTruncatedNormal'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2xf-8hgm-hpw5", "cve": "CVE-2022-35984", "id": "pyup.io-56557", "more_info_path": "/vulnerabilities/CVE-2022-35984/56557", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35986: Segfault in 'RaggedBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wr9v-g9vf-c74v", "cve": "CVE-2022-35986", "id": "pyup.io-56568", "more_info_path": "/vulnerabilities/CVE-2022-35986/56568", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35990: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannelGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h7ff-cfc9-wmmh", "cve": "CVE-2022-35990", "id": "pyup.io-56559", "more_info_path": "/vulnerabilities/CVE-2022-35990/56559", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35966: Segfault in 'QuantizedAvgPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4w68-4x85-mjj9", "cve": "CVE-2022-35966", "id": "pyup.io-56573", "more_info_path": "/vulnerabilities/CVE-2022-35966/56573", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35987: 'CHECK' fail in 'DenseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w62h-8xjm-fv49", "cve": "CVE-2022-35987", "id": "pyup.io-56571", "more_info_path": "/vulnerabilities/CVE-2022-35987/56571", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35992: 'CHECK' fail in 'TensorListFromTensor'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9v8w-xmr4-wgxp", "cve": "CVE-2022-35992", "id": "pyup.io-56567", "more_info_path": "/vulnerabilities/CVE-2022-35992/56567", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36012: Assertion fail on MLIR empty edge names.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jvhc-5hhr-w3v5", "cve": "CVE-2022-36012", "id": "pyup.io-56555", "more_info_path": "/vulnerabilities/CVE-2022-36012/56555", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36013: Null-dereference in 'mlir::tfg::GraphDefImporter::ConvertNodeDef'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-828c-5j5q-vrjq", "cve": "CVE-2022-36013", "id": "pyup.io-56564", "more_info_path": "/vulnerabilities/CVE-2022-36013/56564", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35968: 'CHECK' fail in 'AvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2475-53vw-vp25", "cve": "CVE-2022-35968", "id": "pyup.io-56586", "more_info_path": "/vulnerabilities/CVE-2022-35968/56586", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36005: 'CHECK' fail in 'FakeQuantWithMinMaxVarsGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r26c-679w-mrjm", "cve": "CVE-2022-36005", "id": "pyup.io-56598", "more_info_path": "/vulnerabilities/CVE-2022-36005/56598", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35963: 'CHECK' failures in 'FractionalAvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-84jm-4cf3-9jfm", "cve": "CVE-2022-35963", "id": "pyup.io-56591", "more_info_path": "/vulnerabilities/CVE-2022-35963/56591", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35983: 'CHECK' fail in 'Save' and 'SaveSlices'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6vp-8q9j-whx4", "cve": "CVE-2022-35983", "id": "pyup.io-56556", "more_info_path": "/vulnerabilities/CVE-2022-35983/56556", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36018: 'CHECK' fail in 'RaggedTensorToVariant'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6cv-4fmf-66xf", "cve": "CVE-2022-36018", "id": "pyup.io-56596", "more_info_path": "/vulnerabilities/CVE-2022-36018/56596", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35995: 'CHECK' fail in 'AudioSummaryV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9h5-vr8m-x2h4", "cve": "CVE-2022-35995", "id": "pyup.io-56593", "more_info_path": "/vulnerabilities/CVE-2022-35995/56593", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35981: 'CHECK' fail in 'FractionalMaxPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vxv8-r8q2-63xw", "cve": "CVE-2022-35981", "id": "pyup.io-56565", "more_info_path": "/vulnerabilities/CVE-2022-35981/56565", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35989: 'CHECK' fail in 'MaxPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j43h-pgmg-5hjq", "cve": "CVE-2022-35989", "id": "pyup.io-56597", "more_info_path": "/vulnerabilities/CVE-2022-35989/56597", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35997: 'CHECK' fail in 'tf.sparse.cross'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p7hr-f446-x6qf", "cve": "CVE-2022-35997", "id": "pyup.io-56562", "more_info_path": "/vulnerabilities/CVE-2022-35997/56562", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35960: 'CHECK' failure in 'TensorListReserve' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v5xg-3q2c-c2r4", "cve": "CVE-2022-35960", "id": "pyup.io-56546", "more_info_path": "/vulnerabilities/CVE-2022-35960/56546", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36014: Null-dereference in 'mlir::tfg::TFOp::nameAttr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7j3m-8g3c-9qqq", "cve": "CVE-2022-36014", "id": "pyup.io-56579", "more_info_path": "/vulnerabilities/CVE-2022-36014/56579", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35941: 'CHECK' failure in 'AvgPoolOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mgmh-g2v6-mqw5", "cve": "CVE-2022-35941", "id": "pyup.io-56580", "more_info_path": "/vulnerabilities/CVE-2022-35941/56580", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-35982: Segfault in 'SparseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-397c-5g2j-qxpv", "cve": "CVE-2022-35982", "id": "pyup.io-56576", "more_info_path": "/vulnerabilities/CVE-2022-35982/56576", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.10.0 includes a fix for CVE-2022-36001: 'CHECK' fail in 'DrawBoundingBoxes'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jqm7-m5q7-3hm5", "cve": "CVE-2022-36001", "id": "pyup.io-56590", "more_info_path": "/vulnerabilities/CVE-2022-36001/56590", "specs": [ "<2.10.0" ], "v": "<2.10.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25664: Prior to versions 2.12.0 and 2.11.1, there is a heap buffer overflow in TAvgPoolGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hg6-5c2q-7rcr", "cve": "CVE-2023-25664", "id": "pyup.io-56510", "more_info_path": "/vulnerabilities/CVE-2023-25664/56510", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25661: In versions prior to 2.11.1 a malicious invalid input crashes a tensorflow model (Check Failed) and can be used to trigger a denial of service attack. A proof of concept can be constructed with the 'Convolution3DTranspose' function. This Convolution3DTranspose layer is a very common API in modern neural networks. The ML models containing such vulnerable components could be deployed in ML applications or as cloud services. This failure could be potentially used to trigger a denial of service attack on ML cloud services. An attacker must have privilege to provide input to a 'Convolution3DTranspose' call.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fxgc-95xx-grvq", "cve": "CVE-2023-25661", "id": "pyup.io-56501", "more_info_path": "/vulnerabilities/CVE-2023-25661/56501", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-27579: Constructing a tflite model with a paramater 'filter_input_channel' of less than 1 gives a FPE.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5w96-866f-6rm8", "cve": "CVE-2023-27579", "id": "pyup.io-56505", "more_info_path": "/vulnerabilities/CVE-2023-27579/56505", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25801: Prior to versions 2.12.0 and 2.11.1, 'nn_ops.fractional_avg_pool_v2' and 'nn_ops.fractional_max_pool_v2' require the first and fourth elements of their parameter 'pooling_ratio' to be equal to 1.0, as pooling on batch and channel dimensions is not supported.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f49c-87jh-g47q", "cve": "CVE-2023-25801", "id": "pyup.io-56502", "more_info_path": "/vulnerabilities/CVE-2023-25801/56502", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25673: Versions prior to 2.12.0 and 2.11.1 have a Floating Point Exception in TensorListSplit with XLA. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25673", "id": "pyup.io-56495", "more_info_path": "/vulnerabilities/CVE-2023-25673/56495", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25672: The function 'tf.raw_ops.LookupTableImportV2' cannot handle scalars in the 'values' parameter and gives an NPE. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25672", "id": "pyup.io-56496", "more_info_path": "/vulnerabilities/CVE-2023-25672/56496", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25670: Versions prior to 2.12.0 and 2.11.1 have a null point error in QuantizedMatMulWithBiasAndDequantize with MKL enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rq-hwc3-x77w", "cve": "CVE-2023-25670", "id": "pyup.io-56507", "more_info_path": "/vulnerabilities/CVE-2023-25670/56507", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25669: Prior to versions 2.12.0 and 2.11.1, if the stride and window size are not positive for 'tf.raw_ops.AvgPoolGrad', it can give a floating point exception.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rcf8-g8jv-vg6p", "cve": "CVE-2023-25669", "id": "pyup.io-56508", "more_info_path": "/vulnerabilities/CVE-2023-25669/56508", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25665: Prior to versions 2.12.0 and 2.11.1, when 'SparseSparseMaximum' is given invalid sparse tensors as inputs, it can give a null pointer error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-558h-mq8x-7q9g", "cve": "CVE-2023-25665", "id": "pyup.io-56504", "more_info_path": "/vulnerabilities/CVE-2023-25665/56504", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25663: Prior to versions 2.12.0 and 2.11.1, when 'ctx->step_containter()' is a null ptr, the Lookup function will be executed with a null pointer.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-64jg-wjww-7c5w", "cve": "CVE-2023-25663", "id": "pyup.io-56511", "more_info_path": "/vulnerabilities/CVE-2023-25663/56511", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25659: Prior to versions 2.12.0 and 2.11.1, if the parameter 'indices' for 'DynamicStitch' does not match the shape of the parameter 'data', it can trigger an stack OOB read.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-93vr-9q9m-pj8p", "cve": "CVE-2023-25659", "id": "pyup.io-56514", "more_info_path": "/vulnerabilities/CVE-2023-25659/56514", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25658: Prior to versions 2.12.0 and 2.11.1, an out of bounds read is in GRUBlockCellGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-68v3-g9cm-rmm6", "cve": "CVE-2023-25658", "id": "pyup.io-56515", "more_info_path": "/vulnerabilities/CVE-2023-25658/56515", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25674: Versions prior to 2.12.0 and 2.11.1 have a null pointer error in RandomShuffle with XLA enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf97-q72m-7579", "cve": "CVE-2023-25674", "id": "pyup.io-56500", "more_info_path": "/vulnerabilities/CVE-2023-25674/56500", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25668: Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gw97-ff7c-9v96", "cve": "CVE-2023-25668", "id": "pyup.io-56509", "more_info_path": "/vulnerabilities/CVE-2023-25668/56509", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25676: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.ParallelConcat' segfaults with a nullptr dereference when given a parameter 'shape' with rank that is not greater than zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6wfh-89q8-44jq", "cve": "CVE-2023-25676", "id": "pyup.io-56497", "more_info_path": "/vulnerabilities/CVE-2023-25676/56497", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25660: Prior to versions 2.12.0 and 2.11.1, when the parameter 'summarize' of 'tf.raw_ops.Print' is zero, the new method 'SummarizeArray' will reference to a nullptr, leading to a seg fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qjqc-vqcf-5qvj", "cve": "CVE-2023-25660", "id": "pyup.io-56513", "more_info_path": "/vulnerabilities/CVE-2023-25660/56513", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25667: Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when '2^31 <= num_frames * height * width * channels < 2^32', for example Full HD screencast of at least 346 frames.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqm2-gh8w-gr68", "cve": "CVE-2023-25667", "id": "pyup.io-56499", "more_info_path": "/vulnerabilities/CVE-2023-25667/56499", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25662: Versions prior to 2.12.0 and 2.11.1 are vulnerable to integer overflow in EditDistance.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7jvm-xxmr-v5cw", "cve": "CVE-2023-25662", "id": "pyup.io-56512", "more_info_path": "/vulnerabilities/CVE-2023-25662/56512", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25671: There is out-of-bounds access due to mismatched integer type sizes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j5w9-hmfh-4cr6", "cve": "CVE-2023-25671", "id": "pyup.io-56506", "more_info_path": "/vulnerabilities/CVE-2023-25671/56506", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25675: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.Bincount' segfaults when given a parameter 'weights' that is neither the same shape as parameter 'arr' nor a length-0 tensor.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7x4v-9gxg-9hwj", "cve": "CVE-2023-25675", "id": "pyup.io-56503", "more_info_path": "/vulnerabilities/CVE-2023-25675/56503", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.11.1 and 2.12.0 include a fix for CVE-2023-25666: Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2", "cve": "CVE-2023-25666", "id": "pyup.io-56498", "more_info_path": "/vulnerabilities/CVE-2023-25666/56498", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-intel 2.12 includes a fix for an Authenticated Local Privilege Escalation vulnerability.\r\nhttps://github.com/advisories/GHSA-m2f8-v8q4-3m59", "cve": "CVE-2023-27506", "id": "pyup.io-60349", "more_info_path": "/vulnerabilities/CVE-2023-27506/60349", "specs": [ "<2.12" ], "v": "<2.12" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Integer Overflow. array_ops.upper_bound' causes a segfault when not given a rank 2 tensor. The flaw was fixed in May 30, 2023, but the CVE was published in July 30, 2024. It was noticed unpublished by the Safety CLI Cyber Security team.", "cve": "CVE-2023-33976", "id": "pyup.io-72428", "more_info_path": "/vulnerabilities/CVE-2023-33976/72428", "specs": [ "<2.12.1", ">=2.13.0rc0,<2.13.0" ], "v": "<2.12.1,>=2.13.0rc0,<2.13.0" }, { "advisory": "Tensorflow-intel updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38546.", "cve": "CVE-2023-38546", "id": "pyup.io-72937", "more_info_path": "/vulnerabilities/CVE-2023-38546/72937", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "Tensorflow-intel 2.14.1 updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38545.", "cve": "CVE-2023-38545", "id": "pyup.io-72938", "more_info_path": "/vulnerabilities/CVE-2023-38545/72938", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41893: If 'tf.raw_ops.TensorListResize' is given a nonscalar value for input 'size', it results 'CHECK' fail which can be used to trigger a denial of service attack.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-67pf-62xr-q35m", "cve": "CVE-2022-41893", "id": "pyup.io-56525", "more_info_path": "/vulnerabilities/CVE-2022-41893/56525", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41889: If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a 'nullptr', which is not caught. An example can be seen in 'tf.compat.v1.extract_volume_patches' by passing in quantized tensors as input 'ksizes'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xxcj-rhqg-m46g", "cve": "CVE-2022-41889", "id": "pyup.io-56522", "more_info_path": "/vulnerabilities/CVE-2022-41889/56522", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41909: An input 'encoded' that is not a valid 'CompositeTensorVariant' tensor will trigger a segfault in 'tf.raw_ops.CompositeTensorVariantToComponents'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjx6-v474-2ch9", "cve": "CVE-2022-41909", "id": "pyup.io-56526", "more_info_path": "/vulnerabilities/CVE-2022-41909/56526", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41908: TensorFlow is an open source platform for machine learning. An input 'token' that is not a UTF-8 bytestring will trigger a 'CHECK' fail in 'tf.raw_ops.PyFunc'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv77-9g28-cwg3", "cve": "CVE-2022-41908", "id": "pyup.io-56527", "more_info_path": "/vulnerabilities/CVE-2022-41908/56527", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41907: When 'tf.raw_ops.ResizeNearestNeighborGrad' is given a large 'size' input, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-368v-7v32-52fx", "cve": "CVE-2022-41907", "id": "pyup.io-56531", "more_info_path": "/vulnerabilities/CVE-2022-41907/56531", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41900: The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xvwp-h6jv-7472", "cve": "CVE-2022-41900", "id": "pyup.io-56528", "more_info_path": "/vulnerabilities/CVE-2022-41900/56528", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41899: TensorFlow is an open source platform for machine learning. Inputs 'dense_features' or 'example_state_data' not of rank 2 will trigger a 'CHECK' fail in 'SdcaOptimizer'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-27rc-728f-x5w2", "cve": "CVE-2022-41899", "id": "pyup.io-56524", "more_info_path": "/vulnerabilities/CVE-2022-41899/56524", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41897: If 'FractionMaxPoolGrad' is given outsize inputs 'row_pooling_sequence' and 'col_pooling_sequence', TensorFlow will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2w8-jw48-fr7j", "cve": "CVE-2022-41897", "id": "pyup.io-56535", "more_info_path": "/vulnerabilities/CVE-2022-41897/56535", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41896: If 'ThreadUnsafeUnigramCandidateSampler' is given input 'filterbank_channel_count' greater than the allowed max size, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rmg2-f698-wq35", "cve": "CVE-2022-41896", "id": "pyup.io-56533", "more_info_path": "/vulnerabilities/CVE-2022-41896/56533", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41894: The reference kernel of the 'CONV_3D_TRANSPOSE' TensorFlow Lite operator wrongly increments the data_ptr when adding the bias to the result. Instead of 'data_ptr += num_channels;' it should be 'data_ptr += output_num_channels;' as if the number of input channels is different than the number of output channels, the wrong result will be returned and a buffer overflow will occur if num_channels > output_num_channels. An attacker can craft a model with a specific number of input channels. It is then possible to write specific values through the bias of the layer outside the bounds of the buffer. This attack only works if the reference kernel resolver is used in the interpreter.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6q3-vv32-2cq5", "cve": "CVE-2022-41894", "id": "pyup.io-56540", "more_info_path": "/vulnerabilities/CVE-2022-41894/56540", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41886: When 'tf.raw_ops.ImageProjectiveTransformV2' is given a large output shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-54pp-c6pp-7fpx", "cve": "CVE-2022-41886", "id": "pyup.io-56536", "more_info_path": "/vulnerabilities/CVE-2022-41886/56536", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41884: If a numpy array is created with a shape such that one element is zero and the others sum to a large number, an error will be raised. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jq6x-99hj-q636", "cve": "CVE-2022-41884", "id": "pyup.io-56534", "more_info_path": "/vulnerabilities/CVE-2022-41884/56534", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41880: When the 'BaseCandidateSamplerOp' function receives a value in 'true_classes' larger than 'range_max', a heap oob read occurs.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8w5g-3wcv-9g2j", "cve": "CVE-2022-41880", "id": "pyup.io-56530", "more_info_path": "/vulnerabilities/CVE-2022-41880/56530", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1.", "cve": "CVE-2022-41902", "id": "pyup.io-56532", "more_info_path": "/vulnerabilities/CVE-2022-41902/56532", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41891: If 'tf.raw_ops.TensorListConcat' is given 'element_shape=[]', it results segmentation fault which can be used to trigger a denial of service attack.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-66vq-54fq-6jvv", "cve": "CVE-2022-41891", "id": "pyup.io-56520", "more_info_path": "/vulnerabilities/CVE-2022-41891/56520", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41911: When printing a tensor, we get it's data as a 'const char*' array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from 'char' to 'bool' are undefined if the 'char' is not '0' or '1', so sanitizers/fuzzers will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j", "cve": "CVE-2022-41911", "id": "pyup.io-56521", "more_info_path": "/vulnerabilities/CVE-2022-41911/56521", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41898: If 'SparseFillEmptyRowsGrad' is given empty inputs, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hq7g-wwwp-q46h", "cve": "CVE-2022-41898", "id": "pyup.io-56539", "more_info_path": "/vulnerabilities/CVE-2022-41898/56539", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41888: When running on GPU, 'tf.image.generate_bounding_box_proposals' receives a 'scores' input that must be of rank 4 but is not checked.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6x99-gv2v-q76v", "cve": "CVE-2022-41888", "id": "pyup.io-56538", "more_info_path": "/vulnerabilities/CVE-2022-41888/56538", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41895: If 'MirrorPadGrad' is given outsize input 'paddings', TensorFlow will give a heap OOB error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gq2j-cr96-gvqx", "cve": "CVE-2022-41895", "id": "pyup.io-56519", "more_info_path": "/vulnerabilities/CVE-2022-41895/56519", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41910: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-frqp-wp83-qggv", "cve": "CVE-2022-41910", "id": "pyup.io-56537", "more_info_path": "/vulnerabilities/CVE-2022-41910/56537", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41890: If 'BCast::ToShape' is given input larger than an 'int32', it will crash, despite being supposed to handle up to an 'int64'. An example can be seen in 'tf.experimental.numpy.outer' by passing in large input to the input 'b'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h246-cgh4-7475", "cve": "CVE-2022-41890", "id": "pyup.io-56529", "more_info_path": "/vulnerabilities/CVE-2022-41890/56529", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41901: An input 'sparse_matrix' that is not a matrix with a shape with rank 0 will trigger a 'CHECK' fail in 'tf.raw_ops.SparseMatrixNNZ'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9fm-r5mm-rf9f", "cve": "CVE-2022-41901", "id": "pyup.io-56518", "more_info_path": "/vulnerabilities/CVE-2022-41901/56518", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41885: When 'tf.raw_ops.FusedResizeAndPadConv2D' is given a large tensor shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-762h-vpvw-3rcx", "cve": "CVE-2022-41885", "id": "pyup.io-56523", "more_info_path": "/vulnerabilities/CVE-2022-41885/56523", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35991: 'CHECK' fail in 'TensorListScatter' and 'TensorListScatterV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vm7x-4qhj-rrcq\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xf83-q765-xm6m", "cve": "CVE-2022-35991", "id": "pyup.io-56542", "more_info_path": "/vulnerabilities/CVE-2022-35991/56542", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-intel 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35935: 'CHECK' failure in 'SobolSample' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-97p7-w86h-vcf9\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqvq-fvhr-v6hc", "cve": "CVE-2022-35935", "id": "pyup.io-56541", "more_info_path": "/vulnerabilities/CVE-2022-35935/56541", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-intel 2.9.3 and 2.10.1 include a fix for CVE-2022-41887: 'tf.keras.losses.poisson' receives a 'y_pred' and 'y_true' that are passed through 'functor::mul' in 'BinaryOp'. If the resulting dimensions overflow an 'int32', TensorFlow will crash due to a size mismatch during broadcast assignment.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fvv-46hw-vpg3", "cve": "CVE-2022-41887", "id": "pyup.io-56517", "more_info_path": "/vulnerabilities/CVE-2022-41887/56517", "specs": [ "<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-intel 2.10.1 includes a fix for CVE-2022-41883: When ops that have specified input sizes receive a differing number of inputs, the executor will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj", "cve": "CVE-2022-41883", "id": "pyup.io-56516", "more_info_path": "/vulnerabilities/CVE-2022-41883/56516", "specs": [ ">=2.10.0rc0,<2.10.1" ], "v": ">=2.10.0rc0,<2.10.1" } ], "tensorflow-macos": [ { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25661: In versions prior to 2.11.1 a malicious invalid input crashes a tensorflow model (Check Failed) and can be used to trigger a denial of service attack. A proof of concept can be constructed with the 'Convolution3DTranspose' function. This Convolution3DTranspose layer is a very common API in modern neural networks. The ML models containing such vulnerable components could be deployed in ML applications or as cloud services. This failure could be potentially used to trigger a denial of service attack on ML cloud services. An attacker must have privilege to provide input to a 'Convolution3DTranspose' call.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fxgc-95xx-grvq", "cve": "CVE-2023-25661", "id": "pyup.io-58248", "more_info_path": "/vulnerabilities/CVE-2023-25661/58248", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25676: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.ParallelConcat' segfaults with a nullptr dereference when given a parameter 'shape' with rank that is not greater than zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6wfh-89q8-44jq", "cve": "CVE-2023-25676", "id": "pyup.io-58244", "more_info_path": "/vulnerabilities/CVE-2023-25676/58244", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25674: Versions prior to 2.12.0 and 2.11.1 have a null pointer error in RandomShuffle with XLA enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf97-q72m-7579", "cve": "CVE-2023-25674", "id": "pyup.io-58247", "more_info_path": "/vulnerabilities/CVE-2023-25674/58247", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25673: Versions prior to 2.12.0 and 2.11.1 have a Floating Point Exception in TensorListSplit with XLA. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25673", "id": "pyup.io-58242", "more_info_path": "/vulnerabilities/CVE-2023-25673/58242", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25672: The function 'tf.raw_ops.LookupTableImportV2' cannot handle scalars in the 'values' parameter and gives an NPE. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25672", "id": "pyup.io-58243", "more_info_path": "/vulnerabilities/CVE-2023-25672/58243", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25671: There is out-of-bounds access due to mismatched integer type sizes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j5w9-hmfh-4cr6", "cve": "CVE-2023-25671", "id": "pyup.io-58253", "more_info_path": "/vulnerabilities/CVE-2023-25671/58253", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25669: Prior to versions 2.12.0 and 2.11.1, if the stride and window size are not positive for 'tf.raw_ops.AvgPoolGrad', it can give a floating point exception.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rcf8-g8jv-vg6p", "cve": "CVE-2023-25669", "id": "pyup.io-58255", "more_info_path": "/vulnerabilities/CVE-2023-25669/58255", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25668: Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gw97-ff7c-9v96", "cve": "CVE-2023-25668", "id": "pyup.io-58256", "more_info_path": "/vulnerabilities/CVE-2023-25668/58256", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25667: Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when '2^31 <= num_frames * height * width * channels < 2^32', for example Full HD screencast of at least 346 frames.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqm2-gh8w-gr68", "cve": "CVE-2023-25667", "id": "pyup.io-58246", "more_info_path": "/vulnerabilities/CVE-2023-25667/58246", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25663: Prior to versions 2.12.0 and 2.11.1, when 'ctx->step_containter()' is a null ptr, the Lookup function will be executed with a null pointer.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-64jg-wjww-7c5w", "cve": "CVE-2023-25663", "id": "pyup.io-58258", "more_info_path": "/vulnerabilities/CVE-2023-25663/58258", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25659: Prior to versions 2.12.0 and 2.11.1, if the parameter 'indices' for 'DynamicStitch' does not match the shape of the parameter 'data', it can trigger an stack OOB read.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-93vr-9q9m-pj8p", "cve": "CVE-2023-25659", "id": "pyup.io-58261", "more_info_path": "/vulnerabilities/CVE-2023-25659/58261", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25662: Versions prior to 2.12.0 and 2.11.1 are vulnerable to integer overflow in EditDistance.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7jvm-xxmr-v5cw", "cve": "CVE-2023-25662", "id": "pyup.io-58259", "more_info_path": "/vulnerabilities/CVE-2023-25662/58259", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25660: Prior to versions 2.12.0 and 2.11.1, when the parameter 'summarize' of 'tf.raw_ops.Print' is zero, the new method 'SummarizeArray' will reference to a nullptr, leading to a seg fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qjqc-vqcf-5qvj", "cve": "CVE-2023-25660", "id": "pyup.io-58260", "more_info_path": "/vulnerabilities/CVE-2023-25660/58260", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25670: Versions prior to 2.12.0 and 2.11.1 have a null point error in QuantizedMatMulWithBiasAndDequantize with MKL enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rq-hwc3-x77w", "cve": "CVE-2023-25670", "id": "pyup.io-58254", "more_info_path": "/vulnerabilities/CVE-2023-25670/58254", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25664: Prior to versions 2.12.0 and 2.11.1, there is a heap buffer overflow in TAvgPoolGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hg6-5c2q-7rcr", "cve": "CVE-2023-25664", "id": "pyup.io-58257", "more_info_path": "/vulnerabilities/CVE-2023-25664/58257", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25801: Prior to versions 2.12.0 and 2.11.1, 'nn_ops.fractional_avg_pool_v2' and 'nn_ops.fractional_max_pool_v2' require the first and fourth elements of their parameter 'pooling_ratio' to be equal to 1.0, as pooling on batch and channel dimensions is not supported.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f49c-87jh-g47q", "cve": "CVE-2023-25801", "id": "pyup.io-58249", "more_info_path": "/vulnerabilities/CVE-2023-25801/58249", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25658: Prior to versions 2.12.0 and 2.11.1, an out of bounds read is in GRUBlockCellGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-68v3-g9cm-rmm6", "cve": "CVE-2023-25658", "id": "pyup.io-58262", "more_info_path": "/vulnerabilities/CVE-2023-25658/58262", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25675: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.Bincount' segfaults when given a parameter 'weights' that is neither the same shape as parameter 'arr' nor a length-0 tensor.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7x4v-9gxg-9hwj", "cve": "CVE-2023-25675", "id": "pyup.io-58250", "more_info_path": "/vulnerabilities/CVE-2023-25675/58250", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-27579: Constructing a tflite model with a paramater 'filter_input_channel' of less than 1 gives a FPE.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5w96-866f-6rm8", "cve": "CVE-2023-27579", "id": "pyup.io-58252", "more_info_path": "/vulnerabilities/CVE-2023-27579/58252", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25665: Prior to versions 2.12.0 and 2.11.1, when 'SparseSparseMaximum' is given invalid sparse tensors as inputs, it can give a null pointer error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-558h-mq8x-7q9g", "cve": "CVE-2023-25665", "id": "pyup.io-58251", "more_info_path": "/vulnerabilities/CVE-2023-25665/58251", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-macos 2.11.1 and 2.12.0 include a fix for CVE-2023-25666: Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2", "cve": "CVE-2023-25666", "id": "pyup.io-58245", "more_info_path": "/vulnerabilities/CVE-2023-25666/58245", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Integer Overflow. array_ops.upper_bound' causes a segfault when not given a rank 2 tensor. The flaw was fixed in May 30, 2023, but the CVE was published in July 30, 2024. It was noticed unpublished by the Safety CLI Cyber Security team.", "cve": "CVE-2023-33976", "id": "pyup.io-72431", "more_info_path": "/vulnerabilities/CVE-2023-33976/72431", "specs": [ "<2.12.1", ">=2.13.0rc0,<2.13.0" ], "v": "<2.12.1,>=2.13.0rc0,<2.13.0" }, { "advisory": "Tensorflow-macos 2.14.1 updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38545.", "cve": "CVE-2023-38545", "id": "pyup.io-72940", "more_info_path": "/vulnerabilities/CVE-2023-38545/72940", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "Tensorflow-macos updates its curl dependency from version 8.2.1 to 8.4.0 to address CVE-2023-38546.", "cve": "CVE-2023-38546", "id": "pyup.io-72939", "more_info_path": "/vulnerabilities/CVE-2023-38546/72939", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41205: In affected versions, the shape inference functions for the 'QuantizeAndDequantizeV*' operations can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rx-x2rw-pc6f\nhttps://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d", "cve": "CVE-2021-41205", "id": "pyup.io-58455", "more_info_path": "/vulnerabilities/CVE-2021-41205/58455", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22925.", "cve": "CVE-2021-22925", "id": "pyup.io-58441", "more_info_path": "/vulnerabilities/CVE-2021-22925/58441", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41218: In affected versions, the shape inference code for 'AllToAll' can be made to execute a division by 0. This occurs whenever the 'split_count' argument is 0. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9crf-c6qr-r273\nhttps://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc", "cve": "CVE-2021-41218", "id": "pyup.io-58444", "more_info_path": "/vulnerabilities/CVE-2021-41218/58444", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41214: In affected versions, the shape inference code for 'tf.ragged.cross' has an undefined behavior due to binding a reference to 'nullptr'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vwhq-49r4-gj9v\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41214", "id": "pyup.io-58456", "more_info_path": "/vulnerabilities/CVE-2021-41214/58456", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41204: In affected versions, during TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-786j-5qwq-r36x\nhttps://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659", "cve": "CVE-2021-41204", "id": "pyup.io-58463", "more_info_path": "/vulnerabilities/CVE-2021-41204/58463", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41199: In affected versions, if 'tf.image.resize' is called with a large input argument then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hx2-qx8j-qjqm", "cve": "CVE-2021-41199", "id": "pyup.io-58465", "more_info_path": "/vulnerabilities/CVE-2021-41199/58465", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41195: In affected versions, the implementation of 'tf.math.segment_*' operations results in a 'CHECK'-fail related abort (and denial of service) if a segment id in 'segment_ids' is large. This is similar to CVE-2021-29584 (and similar to other reported vulnerabilities in TensorFlow localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using 'AddDim'. However, if the number of elements in the tensor overflows an 'int64_t' value, 'AddDim' results in a 'CHECK' failure which provokes a 'std::abort'. Instead, code should use 'AddDimWithStatus'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cq76-mxrc-vchh", "cve": "CVE-2021-41195", "id": "pyup.io-58448", "more_info_path": "/vulnerabilities/CVE-2021-41195/58448", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22922.", "cve": "CVE-2021-22922", "id": "pyup.io-58442", "more_info_path": "/vulnerabilities/CVE-2021-22922/58442", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41207: In affected versions, the implementation of 'ParallelConcat' misses some input validation and can produce a division by 0. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7v94-64hj-m82h\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41207", "id": "pyup.io-58461", "more_info_path": "/vulnerabilities/CVE-2021-41207/58461", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41215: In affected versions, the shape inference code for 'DeserializeSparse' can trigger a null pointer dereference. This is because the shape inference function assumes that the 'serialize_sparse' tensor is a tensor with positive rank (and having '3' as the last dimension). The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x3v8-c8qx-3j3r\nhttps://github.com/tensorflow/tensorflow/commit/d3738dd70f1c9ceb547258cbb82d853da8771850", "cve": "CVE-2021-41215", "id": "pyup.io-58451", "more_info_path": "/vulnerabilities/CVE-2021-41215/58451", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41226: In affected versions, the implementation of 'SparseBinCount' is vulnerable to a heap OOB access. This is because of missing validation between the elements of the 'values' argument and the shape of the sparse output. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-374m-jm66-3vj8\nhttps://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba", "cve": "CVE-2021-41226", "id": "pyup.io-58464", "more_info_path": "/vulnerabilities/CVE-2021-41226/58464", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41203: In affected versions, an attacker can trigger undefined behavior, integer overflows, segfaults and 'CHECK'-fail crashes if they can change saved checkpoints from outside of TensorFlow. This is because the checkpoints loading infrastructure is missing validation for invalid file formats.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7pxj-m4jf-r6h2", "cve": "CVE-2021-41203", "id": "pyup.io-58466", "more_info_path": "/vulnerabilities/CVE-2021-41203/58466", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41228: In affected versions, TensorFlow's 'saved_model_cli' tool is vulnerable to a code injection as it calls 'eval' on user supplied strings. This can be used by attackers to run arbitrary code on the plaform where the CLI tool runs. However, given that the tool is always run manually, the impact of this is not severe. The issue has been patched by adding a 'safe' flag which defaults to 'True' and an explicit warning for users.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3rcw-9p9x-582v\nhttps://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7", "cve": "CVE-2021-41228", "id": "pyup.io-58449", "more_info_path": "/vulnerabilities/CVE-2021-41228/58449", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41225: In affected versions, TensorFlow's Grappler optimizer has a use of unitialized variable. If the 'train_nodes' vector (obtained from the saved model that gets optimized) does not contain a 'Dequeue' node, then 'dequeue_node' is left unitialized. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7r94-xv9v-63jw\nhttps://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3", "cve": "CVE-2021-41225", "id": "pyup.io-58472", "more_info_path": "/vulnerabilities/CVE-2021-41225/58472", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22926.", "cve": "CVE-2021-22926", "id": "pyup.io-58450", "more_info_path": "/vulnerabilities/CVE-2021-22926/58450", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41212: In affected versions, the shape inference code for 'tf.ragged.cross' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fr77-rrx3-cp7g\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41212", "id": "pyup.io-58471", "more_info_path": "/vulnerabilities/CVE-2021-41212/58471", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41223: In affected versions, the implementation of 'FusedBatchNorm' kernels is vulnerable to a heap OOB access. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f54p-f6jp-4rhr\nhttps://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda", "cve": "CVE-2021-41223", "id": "pyup.io-58452", "more_info_path": "/vulnerabilities/CVE-2021-41223/58452", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41202: In affected versions, while calculating the size of the output within the 'tf.range' kernel, there is a conditional statement of type 'int64 = condition ? int64 : double'. Due to C++ implicit conversion rules, both branches of the condition will be cast to 'double' and the result would be truncated before the assignment. This result in overflows. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xrqm-fpgr-6hhx", "cve": "CVE-2021-41202", "id": "pyup.io-58462", "more_info_path": "/vulnerabilities/CVE-2021-41202/58462", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41224: In affected versions, the implementation of 'SparseFillEmptyRows' can be made to trigger a heap OOB access. This occurs whenever the size of 'indices' does not match the size of 'values'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rg3m-hqc5-344v\nhttps://github.com/tensorflow/tensorflow/commit/67bfd9feeecfb3c61d80f0e46d89c170fbee682b", "cve": "CVE-2021-41224", "id": "pyup.io-58453", "more_info_path": "/vulnerabilities/CVE-2021-41224/58453", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41219: In affected versions, the code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to 'nullptr'. This occurs whenever the dimensions of 'a' or 'b' are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, it should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4f99-p9c2-3j8x\nhttps://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae", "cve": "CVE-2021-41219", "id": "pyup.io-58457", "more_info_path": "/vulnerabilities/CVE-2021-41219/58457", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41210: In affected versions, the shape inference functions for 'SparseCountSparseOutput' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m342-ff57-4jcc\r\nhttps://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2", "cve": "CVE-2021-41210", "id": "pyup.io-58474", "more_info_path": "/vulnerabilities/CVE-2021-41210/58474", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22924.", "cve": "CVE-2021-22924", "id": "pyup.io-58458", "more_info_path": "/vulnerabilities/CVE-2021-22924/58458", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41200: In affected versions, if 'tf.summary.create_file_writer' is called with non-scalar arguments, code crashes due to a 'CHECK'-fail. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh8h-7j2j-qv4f", "cve": "CVE-2021-41200", "id": "pyup.io-58469", "more_info_path": "/vulnerabilities/CVE-2021-41200/58469", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41222: In affected versions, the implementation of 'SplitV' can trigger a segfault if an attacker supplies negative arguments. This occurs whenever 'size_splits' contains more than one value and at least one value is negative. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cpf4-wx82-gxp6\nhttps://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6", "cve": "CVE-2021-41222", "id": "pyup.io-58468", "more_info_path": "/vulnerabilities/CVE-2021-41222/58468", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41216: In affected versions, the shape inference function for 'Transpose' is vulnerable to a heap buffer overflow. This occurs whenever 'perm' contains negative elements. The shape inference function does not validate that the indices in 'perm' are all valid. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3ff2-r28g-w7h9\nhttps://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14", "cve": "CVE-2021-41216", "id": "pyup.io-58460", "more_info_path": "/vulnerabilities/CVE-2021-41216/58460", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41209: In affected versions, the implementations for convolution operators trigger a division by 0 if passed empty filter tensor arguments. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hpv-v2rx-c5g6\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41209", "id": "pyup.io-58447", "more_info_path": "/vulnerabilities/CVE-2021-41209/58447", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41227: In affected versions, the 'ImmutableConst' operation in TensorFlow can be tricked into reading arbitrary memory contents. This is because the 'tstring' TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j8c8-67vp-6mx7\nhttps://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b\nhttps://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585", "cve": "CVE-2021-41227", "id": "pyup.io-58443", "more_info_path": "/vulnerabilities/CVE-2021-41227/58443", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41221: In affected versions, the shape inference code for the 'Cudnn*' operations can be tricked into accessing invalid memory via a heap buffer overflow. This occurs because the ranks of the 'input', 'input_h' and 'input_c' parameters are not validated, but code assumes they have certain values. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqv6-3phm-hcwx\nhttps://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6", "cve": "CVE-2021-41221", "id": "pyup.io-58470", "more_info_path": "/vulnerabilities/CVE-2021-41221/58470", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41213: In affected versions, the code behind 'tf.function' API can be made to deadlock when two 'tf.function' decorated Python functions are mutually recursive. This occurs due to using a non-reentrant 'Lock' Python object. Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive 'tf.function', although this is not a frequent scenario.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcf\nhttps://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7", "cve": "CVE-2021-41213", "id": "pyup.io-58467", "more_info_path": "/vulnerabilities/CVE-2021-41213/58467", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41217: In affected versions, the process of building the control flow graph for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not. This occurs because the code assumes that the first node in the pairing (e.g., an 'Enter' node) always exists when encountering the second node (e.g., an 'Exit' node). When this is not the case, 'parent' is 'nullptr' so dereferencing it causes a crash. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5crj-c72x-m7gq\nhttps://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff", "cve": "CVE-2021-41217", "id": "pyup.io-58454", "more_info_path": "/vulnerabilities/CVE-2021-41217/58454", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41201: In affected versions, during execution, 'EinsumHelper::ParseEquation()' is supposed to set the flags in 'input_has_ellipsis' vector and '*output_has_ellipsis' boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to 'true' and never assigns 'false'. This results in unitialized variable access if callers assume that 'EinsumHelper::ParseEquation()' always sets these flags. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j86v-p27c-73fm\nhttps://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6", "cve": "CVE-2021-41201", "id": "pyup.io-58446", "more_info_path": "/vulnerabilities/CVE-2021-41201/58446", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41198: In affected versions, if 'tf.tile' is called with a large input argument, then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2p25-55c9-h58q", "cve": "CVE-2021-41198", "id": "pyup.io-58473", "more_info_path": "/vulnerabilities/CVE-2021-41198/58473", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41196: In affected versions, the Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative. This is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m539-j985-hcr8", "cve": "CVE-2021-41196", "id": "pyup.io-58445", "more_info_path": "/vulnerabilities/CVE-2021-41196/58445", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22923.", "cve": "CVE-2021-22923", "id": "pyup.io-58459", "more_info_path": "/vulnerabilities/CVE-2021-22923/58459", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3 and 2.7.1 update its dependency 'icu' to v69.1 to include a security fix.", "cve": "CVE-2020-10531", "id": "pyup.io-58388", "more_info_path": "/vulnerabilities/CVE-2020-10531/58388", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow is vulnerable to an integer overflow during cost estimation for crop and resize. Since the cropping parameters are user controlled, a malicious person can trigger undefined behavior. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23587", "id": "pyup.io-58420", "more_info_path": "/vulnerabilities/CVE-2022-23587/58420", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. When decoding PNG images TensorFlow can produce a memory leak if the image is invalid. After calling `png::CommonInitDecode(..., &decode)`, the `decode` value contains allocated buffers which can only be freed by calling `png::CommonFreeDecode(&decode)`. However, several error case in the function implementation invoke the `OP_REQUIRES` macro which immediately terminates the execution of the function, without allowing for the memory free to occur. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23585", "id": "pyup.io-58398", "more_info_path": "/vulnerabilities/CVE-2022-23585/58398", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23563: In multiple places, TensorFlow uses 'tempfile.mktemp' to create temporary files. While this is acceptable in testing, in utilities and libraries it is dangerous as a different process can create the file between the check for the filename in 'mktemp' and the actual creation of the file by a subsequent operation (a TOC/TOU type of weakness). In several instances, TensorFlow was supposed to actually create a temporary directory instead of a file. This logic bug is hidden away by the 'mktemp' function usage. It was replaced 'mktemp' with the safer 'mkstemp'/'mkdtemp' functions, according to the usage pattern.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wc4g-r73w-x8mm", "cve": "CVE-2022-23563", "id": "pyup.io-58391", "more_info_path": "/vulnerabilities/CVE-2022-23563/58391", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow can trigger a null pointer dereference. There are 2 places where this can occur, for the same malicious alteration of a `SavedModel` file (fixing the first one would trigger the same dereference in the second place). First, during constant folding, the `GraphDef` might not have the required nodes for the binary operation. If a node is missing, the correposning `mul_*child` would be null, and the dereference in the subsequent line would be incorrect. We have a similar issue during `IsIdentityConsumingSwitch`. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23589", "id": "pyup.io-58403", "more_info_path": "/vulnerabilities/CVE-2022-23589/58403", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23581: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'IsSimplifiableReshape' would trigger 'CHECK' failures.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fq86-3f29-px2c", "cve": "CVE-2022-23581", "id": "pyup.io-58404", "more_info_path": "/vulnerabilities/CVE-2022-23581/58404", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. TensorFlow is vulnerable to a heap OOB write in `Grappler`. The `set_output` function writes to an array at the specified index. Hence, this gives a malicious user a write primitive. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23566", "id": "pyup.io-58431", "more_info_path": "/vulnerabilities/CVE-2022-23566/58431", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. If a graph node is invalid, TensorFlow can leak memory in the implementation of `ImmutableExecutorState::Initialize`. Here, we set `item->kernel` to `nullptr` but it is a simple `OpKernel*` pointer so the memory that was previously allocated to it would leak. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23578", "id": "pyup.io-58402", "more_info_path": "/vulnerabilities/CVE-2022-23578/58402", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23572: Under certain scenarios, TensorFlow can fail to specialize a type during shape inference. This case is covered by the `DCHECK` function however, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the `ValueOrDie` line. This results in an assertion failure as `ret` contains an error `Status`, not a value. In the second case we also get a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23572", "id": "pyup.io-58424", "more_info_path": "/vulnerabilities/CVE-2022-23572/58424", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21735: The implementation of 'FractionalMaxPool' can be made to crash a TensorFlow process via a division by 0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-87v6-crgm-2gfj", "cve": "CVE-2022-21735", "id": "pyup.io-58422", "more_info_path": "/vulnerabilities/CVE-2022-21735/58422", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateTensorSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve a tensor with large enough number of elements. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23575", "id": "pyup.io-58408", "more_info_path": "/vulnerabilities/CVE-2022-23575/58408", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23580: During shape inference, TensorFlow can allocate a large vector based on a value from a tensor controlled by the user.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-627q-g293-49q7", "cve": "CVE-2022-23580", "id": "pyup.io-58426", "more_info_path": "/vulnerabilities/CVE-2022-23580/58426", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23558: An attacker can craft a TFLite model that would cause an integer overflow in 'TfLiteIntArrayCreate'. The 'TfLiteIntArrayGetSizeInBytes' returns an 'int' instead of a 'size_t'. An attacker can control model inputs such that 'computed_size' overflows the size of 'int' datatype.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9gwq-6cwj-47h3", "cve": "CVE-2022-23558", "id": "pyup.io-58409", "more_info_path": "/vulnerabilities/CVE-2022-23558/58409", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21739: The implementation of 'QuantizedMaxPool' has an undefined behavior where user controlled inputs can trigger a reference binding to null pointer.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3mw4-6rj6-74g5", "cve": "CVE-2022-21739", "id": "pyup.io-58411", "more_info_path": "/vulnerabilities/CVE-2022-21739/58411", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21731: The implementation of shape inference for 'ConcatV2' can be used to trigger a denial of service attack via a segfault caused by a type confusion. The 'axis' argument is translated into 'concat_dim' in the 'ConcatShapeHelper' helper function. Then, a value for 'min_rank' is computed based on 'concat_dim'. This is then used to validate that the 'values' tensor has at least the required rank. However, 'WithRankAtLeast' receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented. Due to the fact that 'min_rank' is a 32-bits value and the value of 'axis', the 'rank' argument is a negative value, so the error check is bypassed.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m4hf-j54p-p353", "cve": "CVE-2022-21731", "id": "pyup.io-58440", "more_info_path": "/vulnerabilities/CVE-2022-21731/58440", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21730: The implementation of 'FractionalAvgPoolGrad' does not consider cases where the input tensors are invalid allowing an attacker to read from outside of bounds of heap.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vjg4-v33c-ggc4", "cve": "CVE-2022-21730", "id": "pyup.io-58392", "more_info_path": "/vulnerabilities/CVE-2022-21730/58392", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23561: An attacker can craft a TFLite model that would cause a write outside of bounds of an array in TFLite. In fact, the attacker can override the linked list used by the memory allocator. This can be leveraged for an arbitrary write primitive under certain conditions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9c78-vcq7-7vxq", "cve": "CVE-2022-23561", "id": "pyup.io-58439", "more_info_path": "/vulnerabilities/CVE-2022-23561/58439", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21728: The implementation of shape inference for 'ReverseSequence' does not fully validate the value of 'batch_dim' and can result in a heap OOB read. There is a check to make sure the value of 'batch_dim' does not go over the rank of the input, but there is no check for negative values. Negative dimensions are allowed in some cases to mimic Python's negative indexing (i.e., indexing from the end of the array), however if the value is too negative then the implementation of 'Dim' would access elements before the start of an array.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6gmv-pjp9-p8w8", "cve": "CVE-2022-21728", "id": "pyup.io-58390", "more_info_path": "/vulnerabilities/CVE-2022-21728/58390", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23595: When building an XLA compilation cache, if default settings are used, TensorFlow triggers a null pointer dereference. In the default scenario, all devices are allowed, so 'flr->config_proto' is 'nullptr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fpcp-9h7m-ffpx", "cve": "CVE-2022-23595", "id": "pyup.io-58394", "more_info_path": "/vulnerabilities/CVE-2022-23595/58394", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. The 'GraphDef' format in TensorFlow does not allow self recursive functions. The runtime assumes that this invariant is satisfied. However, a 'GraphDef' containing a fragment such as the following can be consumed when loading a 'SavedModel'. This would result in a stack overflow during execution as resolving each 'NodeDef' means resolving the function itself and its nodes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23591", "id": "pyup.io-58428", "more_info_path": "/vulnerabilities/CVE-2022-23591/58428", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that Grappler optimizer would attempt to build a tensor using a reference `dtype`. This would result in a crash due to a `CHECK`-fail in the `Tensor` constructor as reference types are not allowed. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23588", "id": "pyup.io-58435", "more_info_path": "/vulnerabilities/CVE-2022-23588/58435", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that assertions in `function.cc` would be falsified and crash the Python interpreter. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23586", "id": "pyup.io-58414", "more_info_path": "/vulnerabilities/CVE-2022-23586/58414", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. A malicious user can cause a use after free behavior when decoding PNG images. After `png::CommonFreeDecode(&decode)` gets called, the values of `decode.width` and `decode.height` are in an unspecified state. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23584", "id": "pyup.io-58436", "more_info_path": "/vulnerabilities/CVE-2022-23584/58436", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a 'SavedModel' such that any binary op would trigger 'CHECK' failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the 'dtype' no longer matches the 'dtype' expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If 'Tin' and 'Tout' don't match the type of data in 'out' and 'input_*' tensors then 'flat<*>' would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a 'CHECK' crash, hence a denial of service. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23583", "id": "pyup.io-58400", "more_info_path": "/vulnerabilities/CVE-2022-23583/58400", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21726: The implementation of 'Dequantize' does not fully validate the value of 'axis' and can result in heap OOB accesses. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked and this results in reading past the end of the array containing the dimensions of the input tensor.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-23hm-7w47-xw72", "cve": "CVE-2022-21726", "id": "pyup.io-58438", "more_info_path": "/vulnerabilities/CVE-2022-21726/58438", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21738: The implementation of 'SparseCountSparseOutput' can be made to crash a TensorFlow process by an integer overflow whose result is then used in a memory allocation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x4qx-4fjv-hmw6", "cve": "CVE-2022-21738", "id": "pyup.io-58434", "more_info_path": "/vulnerabilities/CVE-2022-21738/58434", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21733: The implementation of 'StringNGrams' can be used to trigger a denial of service attack by causing an out of memory condition after an integer overflow. There is missing a validation on 'pad_witdh' and that result in computing a negative value for 'ngram_width' which is later used to allocate parts of the output.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98j8-c9q4-r38g", "cve": "CVE-2022-21733", "id": "pyup.io-58418", "more_info_path": "/vulnerabilities/CVE-2022-21733/58418", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21727: The implementation of shape inference for 'Dequantize' is vulnerable to an integer overflow weakness. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked, and, since the code computes 'axis + 1', an attacker can trigger an integer overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c6fh-56w7-fvjw", "cve": "CVE-2022-21727", "id": "pyup.io-58415", "more_info_path": "/vulnerabilities/CVE-2022-21727/58415", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21729: The implementation of 'UnravelIndex' is vulnerable to a division by zero caused by an integer overflow bug.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-34f9-hjfq-rr8j", "cve": "CVE-2022-21729", "id": "pyup.io-58413", "more_info_path": "/vulnerabilities/CVE-2022-21729/58413", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23567: The implementations of 'Sparse*Cwise*' ops are vulnerable to integer overflows. These can be used to trigger large allocations (so, OOM based denial of service) or 'CHECK'-fails when building new 'TensorShape' objects (so, assert failures based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rrx2-r989-2c43", "cve": "CVE-2022-23567", "id": "pyup.io-58410", "more_info_path": "/vulnerabilities/CVE-2022-23567/58410", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23569: Multiple operations in TensorFlow can be used to trigger a denial of service via 'CHECK'-fails (i.e., assertion failures). This is similar to CVE-2021-41197 and has a similar fix. It is possible that other similar instances exist.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qj5r-f9mv-rffh", "cve": "CVE-2022-23569", "id": "pyup.io-58407", "more_info_path": "/vulnerabilities/CVE-2022-23569/58407", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21737: The implementation of '*Bincount' operations allows malicious users to cause denial of service by passing in arguments which would trigger a 'CHECK'-fail. There are several conditions that the input arguments must satisfy. Some are not caught during shape inference and others are not caught during kernel implementation. This results in 'CHECK' failures later when the output tensors get allocated.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2vv-v9cg-qhh7", "cve": "CVE-2022-21737", "id": "pyup.io-58405", "more_info_path": "/vulnerabilities/CVE-2022-21737/58405", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23582: A malicious user can cause a denial of service by altering a 'SavedModel' such that 'TensorByteSize' would trigger 'CHECK' failures. 'TensorShape' constructor throws a 'CHECK'-fail if shape is partial or has a number of elements that would overflow the size of an 'int'. The 'PartialTensorShape' constructor instead does not cause a 'CHECK'-abort if the shape is partial, which is exactly what this function needs to be able to return '-1'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4j82-5ccr-4r8v", "cve": "CVE-2022-23582", "id": "pyup.io-58437", "more_info_path": "/vulnerabilities/CVE-2022-23582/58437", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21736: The implementation of 'SparseTensorSliceDataset' has an undefined behavior: under certain conditions, it can be made to dereference a 'nullptr' value. The 3 input arguments to 'SparseTensorSliceDataset' represent a sparse tensor. However, there are some preconditions that these arguments must satisfy, but these are not validated in the implementation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pfjj-m3jj-9jc9", "cve": "CVE-2022-21736", "id": "pyup.io-58393", "more_info_path": "/vulnerabilities/CVE-2022-21736/58393", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23568: The implementation of 'AddManySparseToTensorsMap' is vulnerable to an integer overflow which results in a 'CHECK'-fail when building new 'TensorShape' objects (so, an assert failure based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6445-fm66-fvq2", "cve": "CVE-2022-23568", "id": "pyup.io-58389", "more_info_path": "/vulnerabilities/CVE-2022-23568/58389", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23579: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'SafeToRemoveIdentity' would trigger 'CHECK' failures.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5f2r-qp73-37mr", "cve": "CVE-2022-23579", "id": "pyup.io-58432", "more_info_path": "/vulnerabilities/CVE-2022-23579/58432", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. The implementation of `GetInitOp` is vulnerable to a crash caused by dereferencing a null pointer. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23577", "id": "pyup.io-58427", "more_info_path": "/vulnerabilities/CVE-2022-23577/58427", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateOutputSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve tensors with large enough number of elements. We can have a large enough number of dimensions in `output_shape.dim()` or just a small number of dimensions being large enough to cause an overflow in the multiplication. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23576", "id": "pyup.io-58399", "more_info_path": "/vulnerabilities/CVE-2022-23576/58399", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. There is a typo in TensorFlow's `SpecializeType` which results in heap OOB read/write. Due to a typo, `arg` is initialized to the `i`th mutable argument in a loop where the loop index is `j`. Hence it is possible to assign to `arg` from outside the vector of arguments. Since this is a mutable proto value, it allows both read and write to outside of bounds data. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23574", "id": "pyup.io-58406", "more_info_path": "/vulnerabilities/CVE-2022-23574/58406", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized data to a new tensor. This later results in undefined behavior. The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23573", "id": "pyup.io-58401", "more_info_path": "/vulnerabilities/CVE-2022-23573/58401", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23571", "id": "pyup.io-58416", "more_info_path": "/vulnerabilities/CVE-2022-23571/58416", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, TensorFlow might do a null-dereference if attributes of some mutable arguments to some operations are missing from the proto. This is guarded by a `DCHECK`. However, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the dereferencing of the null pointer, whereas in the second case it results in a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23570", "id": "pyup.io-58396", "more_info_path": "/vulnerabilities/CVE-2022-23570/58396", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23565: An attacker can trigger denial of service via assertion failure by altering a 'SavedModel' on disk such that 'AttrDef's of some operation are duplicated.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4v5p-v5h9-6xjx", "cve": "CVE-2022-23565", "id": "pyup.io-58425", "more_info_path": "/vulnerabilities/CVE-2022-23565/58425", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23564: When decoding a resource handle tensor from protobuf, a TensorFlow process can encounter cases where a 'CHECK' assertion is invalidated based on user controlled arguments. This allows attackers to cause denial of services in TensorFlow processes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8rcj-c8pj-v3m3", "cve": "CVE-2022-23564", "id": "pyup.io-58417", "more_info_path": "/vulnerabilities/CVE-2022-23564/58417", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23562: The implementation of 'Range' suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qx3f-p745-w4hr", "cve": "CVE-2022-23562", "id": "pyup.io-58433", "more_info_path": "/vulnerabilities/CVE-2022-23562/58433", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23560: An attacker can craft a TFLite model that would allow limited reads and writes outside of arrays in TFLite. This exploits missing validation in the conversion from sparse tensors to dense tensors.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4hvf-hxvg-f67v", "cve": "CVE-2022-23560", "id": "pyup.io-58419", "more_info_path": "/vulnerabilities/CVE-2022-23560/58419", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23559: An attacker can craft a TFLite model that would cause an integer overflow in embedding lookup operations. Both 'embedding_size' and 'lookup_size' are products of values provided by the user. Hence, a malicious user could trigger overflows in the multiplication. In certain scenarios, this can then result in heap OOB read/write.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98p5-x8x4-c9m5", "cve": "CVE-2022-23559", "id": "pyup.io-58412", "more_info_path": "/vulnerabilities/CVE-2022-23559/58412", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23557: An attacker can craft a TFLite model that would trigger a division by zero in 'BiasAndClamp' implementation. There is no check that the 'bias_size' is non zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf2j-f278-xh4v", "cve": "CVE-2022-23557", "id": "pyup.io-58423", "more_info_path": "/vulnerabilities/CVE-2022-23557/58423", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21740: The implementation of 'SparseCountSparseOutput' is vulnerable to a heap overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-44qp-9wwf-734r", "cve": "CVE-2022-21740", "id": "pyup.io-58430", "more_info_path": "/vulnerabilities/CVE-2022-21740/58430", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21732: The implementation of 'ThreadPoolHandle' can be used to trigger a denial of service attack by allocating too much memory. This is because the 'num_threads' argument is only checked to not be negative, but there is no upper bound on its value.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c582-c96p-r5cq", "cve": "CVE-2022-21732", "id": "pyup.io-58429", "more_info_path": "/vulnerabilities/CVE-2022-21732/58429", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21734: The implementation of 'MapStage' is vulnerable to a 'CHECK'-fail if the key tensor is not a scalar.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gcvh-66ff-4mwm", "cve": "CVE-2022-21734", "id": "pyup.io-58397", "more_info_path": "/vulnerabilities/CVE-2022-21734/58397", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21725: The estimator for the cost of some convolution operations can be made to execute a division by 0. The function fails to check that the stride argument is strictly positive. Hence, the fix is to add a check for the stride argument to ensure it is valid.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v3f7-j968-4h5f", "cve": "CVE-2022-21725", "id": "pyup.io-58421", "more_info_path": "/vulnerabilities/CVE-2022-21725/58421", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21741: An attacker can craft a TFLite model that would trigger a division by zero in the implementation of depthwise convolutions. The parameters of the convolution can be user controlled and are also used within a division operation to determine the size of the padding that needs to be added before applying the convolution. There is no check before this division that the divisor is strictly positive.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-428x-9xc2-m8mj", "cve": "CVE-2022-21741", "id": "pyup.io-58395", "more_info_path": "/vulnerabilities/CVE-2022-21741/58395", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41208: In affected versions, the code for boosted trees in TensorFlow is still missing validation. As a result, attackers can trigger denial of service (via dereferencing 'nullptr's or via 'CHECK'-failures) as well as abuse undefined behavior (binding references to 'nullptr's). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call. Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. TensorFlow's boosted trees APIs will be deprecated in subsequent releases.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-57wx-m983-2f88\nhttps://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6gw-r52c-724r", "cve": "CVE-2021-41208", "id": "pyup.io-58387", "more_info_path": "/vulnerabilities/CVE-2021-41208/58387", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Tensorflow-macos versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41206: In affected versions, several TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or 'CHECK'-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible. These issues were discovered internally via tooling while working on improving/testing GPU op determinism. As such, there aren't reproducers and there will be multiple fixes for these issues.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pgcq-h79j-2f69\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-43q8-3fv7-pr5x", "cve": "CVE-2021-41206", "id": "pyup.io-58386", "more_info_path": "/vulnerabilities/CVE-2021-41206/58386", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Affected versions of Tensorflow-macos are vulnerable to Denial of Service via CHECK-failure (assertion failure) in constant folding. The output_prop tensor has a shape that is controlled by user input and this can result in triggering one of the CHECKs in the PartialTensorShape constructor. This is an instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71510", "id": "pyup.io-71770", "more_info_path": "/vulnerabilities/PVE-2024-71510/71770", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1", ">=2.8.0rc0,<2.8.0" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1,>=2.8.0rc0,<2.8.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27779.", "cve": "CVE-2022-27779", "id": "pyup.io-58362", "more_info_path": "/vulnerabilities/CVE-2022-27779/58362", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27775.", "cve": "CVE-2022-27775", "id": "pyup.io-58347", "more_info_path": "/vulnerabilities/CVE-2022-27775/58347", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27774.", "cve": "CVE-2022-27774", "id": "pyup.io-58360", "more_info_path": "/vulnerabilities/CVE-2022-27774/58360", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27780.", "cve": "CVE-2022-27780", "id": "pyup.io-58373", "more_info_path": "/vulnerabilities/CVE-2022-27780/58373", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29206: Missing validation which results in undefined behavior in 'SparseTensorDenseAdd'.", "cve": "CVE-2022-29206", "id": "pyup.io-58369", "more_info_path": "/vulnerabilities/CVE-2022-29206/58369", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29196: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29196", "id": "pyup.io-58353", "more_info_path": "/vulnerabilities/CVE-2022-29196/58353", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29216: Code injection in 'saved_model_cli'.", "cve": "CVE-2022-29216", "id": "pyup.io-58348", "more_info_path": "/vulnerabilities/CVE-2022-29216/58348", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29213: Crashes stemming from incomplete validation in signal ops.", "cve": "CVE-2022-29213", "id": "pyup.io-58376", "more_info_path": "/vulnerabilities/CVE-2022-29213/58376", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29194: Missing validation which causes denial of service via 'DeleteSessionTensor'.", "cve": "CVE-2022-29194", "id": "pyup.io-58358", "more_info_path": "/vulnerabilities/CVE-2022-29194/58358", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29191: Missing validation which causes denial of service via 'GetSessionTensor'.", "cve": "CVE-2022-29191", "id": "pyup.io-58380", "more_info_path": "/vulnerabilities/CVE-2022-29191/58380", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29207: Issues arising from undefined behavior stemming from users supplying invalid resource handles.", "cve": "CVE-2022-29207", "id": "pyup.io-58354", "more_info_path": "/vulnerabilities/CVE-2022-29207/58354", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29192: missing validation which crashes 'QuantizeAndDequantizeV4Grad'.", "cve": "CVE-2022-29192", "id": "pyup.io-58372", "more_info_path": "/vulnerabilities/CVE-2022-29192/58372", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'zlib' to v1.2.12 to handle CVE-2018-25032.", "cve": "CVE-2018-25032", "id": "pyup.io-58365", "more_info_path": "/vulnerabilities/CVE-2018-25032/58365", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-22576.", "cve": "CVE-2022-22576", "id": "pyup.io-58377", "more_info_path": "/vulnerabilities/CVE-2022-22576/58377", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27778.", "cve": "CVE-2022-27778", "id": "pyup.io-58361", "more_info_path": "/vulnerabilities/CVE-2022-27778/58361", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27781.", "cve": "CVE-2022-27781", "id": "pyup.io-58363", "more_info_path": "/vulnerabilities/CVE-2022-27781/58363", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29209: Type confusion leading to 'CHECK'-failure based denial of service.", "cve": "CVE-2022-29209", "id": "pyup.io-58378", "more_info_path": "/vulnerabilities/CVE-2022-29209/58378", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29204: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29204", "id": "pyup.io-58370", "more_info_path": "/vulnerabilities/CVE-2022-29204/58370", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27776.", "cve": "CVE-2022-27776", "id": "pyup.io-58350", "more_info_path": "/vulnerabilities/CVE-2022-27776/58350", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29211: Segfault when 'tf.histogram_fixed_width' is called with NaN values.", "cve": "CVE-2022-29211", "id": "pyup.io-58371", "more_info_path": "/vulnerabilities/CVE-2022-29211/58371", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29208: Segfault and OOB write due to incomplete validation in 'EditDistance'.", "cve": "CVE-2022-29208", "id": "pyup.io-58356", "more_info_path": "/vulnerabilities/CVE-2022-29208/58356", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29205: Segfault due to missing support for quantized types.", "cve": "CVE-2022-29205", "id": "pyup.io-58374", "more_info_path": "/vulnerabilities/CVE-2022-29205/58374", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-30115.", "cve": "CVE-2022-30115", "id": "pyup.io-58364", "more_info_path": "/vulnerabilities/CVE-2022-30115/58364", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29203: Integer overflow in 'SpaceToBatchND'.", "cve": "CVE-2022-29203", "id": "pyup.io-58366", "more_info_path": "/vulnerabilities/CVE-2022-29203/58366", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27782.", "cve": "CVE-2022-27782", "id": "pyup.io-58379", "more_info_path": "/vulnerabilities/CVE-2022-27782/58379", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29202: Denial of service in 'tf.ragged.constant' due to lack of validation.", "cve": "CVE-2022-29202", "id": "pyup.io-58367", "more_info_path": "/vulnerabilities/CVE-2022-29202/58367", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29201: Missing validation which results in undefined behavior in 'QuantizedConv2D'.", "cve": "CVE-2022-29201", "id": "pyup.io-58368", "more_info_path": "/vulnerabilities/CVE-2022-29201/58368", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29200: Missing validation which causes denial of service via 'LSTMBlockCell'.", "cve": "CVE-2022-29200", "id": "pyup.io-58351", "more_info_path": "/vulnerabilities/CVE-2022-29200/58351", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29199: Missing validation which causes denial of service via 'LoadAndRemapMatrix'.", "cve": "CVE-2022-29199", "id": "pyup.io-58375", "more_info_path": "/vulnerabilities/CVE-2022-29199/58375", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29198: Missing validation which causes denial of service via 'SparseTensorToCSRSparseMatrix'.", "cve": "CVE-2022-29198", "id": "pyup.io-58352", "more_info_path": "/vulnerabilities/CVE-2022-29198/58352", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29197: Missing validation which causes denial of service via 'UnsortedSegmentJoin'.", "cve": "CVE-2022-29197", "id": "pyup.io-58355", "more_info_path": "/vulnerabilities/CVE-2022-29197/58355", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29195: Missing validation which causes denial of service via 'StagePeek'.", "cve": "CVE-2022-29195", "id": "pyup.io-58357", "more_info_path": "/vulnerabilities/CVE-2022-29195/58357", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29193: missing validation which causes 'TensorSummaryV2' to crash.", "cve": "CVE-2022-29193", "id": "pyup.io-58349", "more_info_path": "/vulnerabilities/CVE-2022-29193/58349", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29212: Core dump when loading TFLite models with quantization.", "cve": "CVE-2022-29212", "id": "pyup.io-58381", "more_info_path": "/vulnerabilities/CVE-2022-29212/58381", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Affected versions of Tensorflow-macos are vulnerable to Denial of Service in the implementation of depthwise ops via CHECK-failure (assertion failure) caused by overflowing the number of elements in a tensor. This is another instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71511", "id": "pyup.io-71771", "more_info_path": "/vulnerabilities/PVE-2024-71511/71771", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Affected versions of Tensorflow-macos allow tensors to have a large number of dimensions and each dimension can be as large as desired. However, the total number of elements in a tensor must fit within an 'int64_t'. If an overflow occurs, 'MultiplyWithoutOverflow' would return a negative result. In the majority of TensorFlow codebase this then results in a 'CHECK'-failure. Newer constructs exist which return a 'Status' instead of crashing the binary. This is a similar issue to CVE-2021-29584.", "cve": "CVE-2021-41197", "id": "pyup.io-58359", "more_info_path": "/vulnerabilities/CVE-2021-41197/58359", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35993: 'CHECK' fail in 'SetSize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wq6q-6m32-9rv9", "cve": "CVE-2022-35993", "id": "pyup.io-58325", "more_info_path": "/vulnerabilities/CVE-2022-35993/58325", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36012: Assertion fail on MLIR empty edge names.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jvhc-5hhr-w3v5", "cve": "CVE-2022-36012", "id": "pyup.io-58302", "more_info_path": "/vulnerabilities/CVE-2022-36012/58302", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36019: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannel'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9j4v-pp28-mxv7", "cve": "CVE-2022-36019", "id": "pyup.io-58331", "more_info_path": "/vulnerabilities/CVE-2022-36019/58331", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36014: Null-dereference in 'mlir::tfg::TFOp::nameAttr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7j3m-8g3c-9qqq", "cve": "CVE-2022-36014", "id": "pyup.io-58326", "more_info_path": "/vulnerabilities/CVE-2022-36014/58326", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36003: 'CHECK' fail in 'RandomPoissonV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cv2p-32v3-vhwq", "cve": "CVE-2022-36003", "id": "pyup.io-58297", "more_info_path": "/vulnerabilities/CVE-2022-36003/58297", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35989: 'CHECK' fail in 'MaxPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j43h-pgmg-5hjq", "cve": "CVE-2022-35989", "id": "pyup.io-58344", "more_info_path": "/vulnerabilities/CVE-2022-35989/58344", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35979: Segfault in 'QuantizedRelu' and 'QuantizedRelu6'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v7vw-577f-vp8x", "cve": "CVE-2022-35979", "id": "pyup.io-58294", "more_info_path": "/vulnerabilities/CVE-2022-35979/58294", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35970: Segfault in 'QuantizedInstanceNorm'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g35r-369w-3fqp", "cve": "CVE-2022-35970", "id": "pyup.io-58334", "more_info_path": "/vulnerabilities/CVE-2022-35970/58334", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35967: Segfault in 'QuantizedAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v6h3-348g-6h5x", "cve": "CVE-2022-35967", "id": "pyup.io-58332", "more_info_path": "/vulnerabilities/CVE-2022-35967/58332", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35982: Segfault in 'SparseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-397c-5g2j-qxpv", "cve": "CVE-2022-35982", "id": "pyup.io-58323", "more_info_path": "/vulnerabilities/CVE-2022-35982/58323", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35966: Segfault in 'QuantizedAvgPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4w68-4x85-mjj9", "cve": "CVE-2022-35966", "id": "pyup.io-58320", "more_info_path": "/vulnerabilities/CVE-2022-35966/58320", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36015: Integer overflow in math ops. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rh87-q4vg-m45j", "cve": "CVE-2022-36015", "id": "pyup.io-58296", "more_info_path": "/vulnerabilities/CVE-2022-36015/58296", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35959: 'CHECK' failures in 'AvgPool3DGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wxjj-cgcx-r3vq", "cve": "CVE-2022-35959", "id": "pyup.io-58307", "more_info_path": "/vulnerabilities/CVE-2022-35959/58307", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35998: 'CHECK' fail in 'EmptyTensorList'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhw4-wwr7-gjc5", "cve": "CVE-2022-35998", "id": "pyup.io-58310", "more_info_path": "/vulnerabilities/CVE-2022-35998/58310", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35960: 'CHECK' failure in 'TensorListReserve' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v5xg-3q2c-c2r4", "cve": "CVE-2022-35960", "id": "pyup.io-58293", "more_info_path": "/vulnerabilities/CVE-2022-35960/58293", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35973: Segfault in 'QuantizedMatMul'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-689c-r7h2-fv9v", "cve": "CVE-2022-35973", "id": "pyup.io-58317", "more_info_path": "/vulnerabilities/CVE-2022-35973/58317", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36027: Segfault TFLite converter on per-channel quantized transposed convolutions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-79h2-q768-fpxr", "cve": "CVE-2022-36027", "id": "pyup.io-58322", "more_info_path": "/vulnerabilities/CVE-2022-36027/58322", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36017: Segfault in 'Requantize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wqmc-pm8c-2jhc", "cve": "CVE-2022-36017", "id": "pyup.io-58295", "more_info_path": "/vulnerabilities/CVE-2022-36017/58295", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36013: Null-dereference in 'mlir::tfg::GraphDefImporter::ConvertNodeDef'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-828c-5j5q-vrjq", "cve": "CVE-2022-36013", "id": "pyup.io-58311", "more_info_path": "/vulnerabilities/CVE-2022-36013/58311", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36005: 'CHECK' fail in 'FakeQuantWithMinMaxVarsGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r26c-679w-mrjm", "cve": "CVE-2022-36005", "id": "pyup.io-58345", "more_info_path": "/vulnerabilities/CVE-2022-36005/58345", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36004: 'CHECK' fail in 'tf.random.gamma'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv8m-8x97-937q", "cve": "CVE-2022-36004", "id": "pyup.io-58342", "more_info_path": "/vulnerabilities/CVE-2022-36004/58342", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36001: 'CHECK' fail in 'DrawBoundingBoxes'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jqm7-m5q7-3hm5", "cve": "CVE-2022-36001", "id": "pyup.io-58337", "more_info_path": "/vulnerabilities/CVE-2022-36001/58337", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36000: 'CHECK' fail in 'Eig'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqxc-pvf8-2w9v", "cve": "CVE-2022-36000", "id": "pyup.io-58313", "more_info_path": "/vulnerabilities/CVE-2022-36000/58313", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35999: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-37jf-mjv6-xfqw", "cve": "CVE-2022-35999", "id": "pyup.io-58339", "more_info_path": "/vulnerabilities/CVE-2022-35999/58339", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35997: 'CHECK' fail in 'tf.sparse.cross'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p7hr-f446-x6qf", "cve": "CVE-2022-35997", "id": "pyup.io-58309", "more_info_path": "/vulnerabilities/CVE-2022-35997/58309", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36002: 'CHECK' fail in 'Unbatch'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mh3m-62v7-68xg", "cve": "CVE-2022-36002", "id": "pyup.io-58301", "more_info_path": "/vulnerabilities/CVE-2022-36002/58301", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35996: Floating point exception in 'Conv2D'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q5jv-m6qw-5g37", "cve": "CVE-2022-35996", "id": "pyup.io-58305", "more_info_path": "/vulnerabilities/CVE-2022-35996/58305", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35995: 'CHECK' fail in 'AudioSummaryV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9h5-vr8m-x2h4", "cve": "CVE-2022-35995", "id": "pyup.io-58340", "more_info_path": "/vulnerabilities/CVE-2022-35995/58340", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35994: 'CHECK' fail in 'CollectiveGather'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fhfc-2q7x-929f", "cve": "CVE-2022-35994", "id": "pyup.io-58335", "more_info_path": "/vulnerabilities/CVE-2022-35994/58335", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35992: 'CHECK' fail in 'TensorListFromTensor'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9v8w-xmr4-wgxp", "cve": "CVE-2022-35992", "id": "pyup.io-58314", "more_info_path": "/vulnerabilities/CVE-2022-35992/58314", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36016: 'CHECK'-fail in 'tensorflow::full_type::SubstituteFromAttrs'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g468-qj8g-vcjc", "cve": "CVE-2022-36016", "id": "pyup.io-58328", "more_info_path": "/vulnerabilities/CVE-2022-36016/58328", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36026: 'CHECK' fail in 'QuantizeAndDequantizeV3'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9cr2-8pwr-fhfq", "cve": "CVE-2022-36026", "id": "pyup.io-58319", "more_info_path": "/vulnerabilities/CVE-2022-36026/58319", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35983: 'CHECK' fail in 'Save' and 'SaveSlices'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6vp-8q9j-whx4", "cve": "CVE-2022-35983", "id": "pyup.io-58303", "more_info_path": "/vulnerabilities/CVE-2022-35983/58303", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36018: 'CHECK' fail in 'RaggedTensorToVariant'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6cv-4fmf-66xf", "cve": "CVE-2022-36018", "id": "pyup.io-58343", "more_info_path": "/vulnerabilities/CVE-2022-36018/58343", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35990: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannelGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h7ff-cfc9-wmmh", "cve": "CVE-2022-35990", "id": "pyup.io-58306", "more_info_path": "/vulnerabilities/CVE-2022-35990/58306", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36011: Null dereference on MLIR on empty function attributes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fv43-93gv-vm8f", "cve": "CVE-2022-36011", "id": "pyup.io-58321", "more_info_path": "/vulnerabilities/CVE-2022-36011/58321", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35987: 'CHECK' fail in 'DenseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w62h-8xjm-fv49", "cve": "CVE-2022-35987", "id": "pyup.io-58318", "more_info_path": "/vulnerabilities/CVE-2022-35987/58318", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35986: Segfault in 'RaggedBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wr9v-g9vf-c74v", "cve": "CVE-2022-35986", "id": "pyup.io-58315", "more_info_path": "/vulnerabilities/CVE-2022-35986/58315", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35985: 'CHECK' fail in 'LRNGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9942-r22v-78cp", "cve": "CVE-2022-35985", "id": "pyup.io-58298", "more_info_path": "/vulnerabilities/CVE-2022-35985/58298", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35984: 'CHECK' fail in 'ParameterizedTruncatedNormal'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2xf-8hgm-hpw5", "cve": "CVE-2022-35984", "id": "pyup.io-58304", "more_info_path": "/vulnerabilities/CVE-2022-35984/58304", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35981: 'CHECK' fail in 'FractionalMaxPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vxv8-r8q2-63xw", "cve": "CVE-2022-35981", "id": "pyup.io-58312", "more_info_path": "/vulnerabilities/CVE-2022-35981/58312", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35974: Segfault in 'QuantizeDownAndShrinkRange'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vgvh-2pf4-jr2x", "cve": "CVE-2022-35974", "id": "pyup.io-58316", "more_info_path": "/vulnerabilities/CVE-2022-35974/58316", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35972: Segfault in 'QuantizedBiasAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4pc4-m9mj-v2r9", "cve": "CVE-2022-35972", "id": "pyup.io-58324", "more_info_path": "/vulnerabilities/CVE-2022-35972/58324", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35971: 'CHECK' fail in 'FakeQuantWithMinMaxVars'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9fpg-838v-wpv7", "cve": "CVE-2022-35971", "id": "pyup.io-58341", "more_info_path": "/vulnerabilities/CVE-2022-35971/58341", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35969: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q2c3-jpmc-gfjx", "cve": "CVE-2022-35969", "id": "pyup.io-58299", "more_info_path": "/vulnerabilities/CVE-2022-35969/58299", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35968: 'CHECK' fail in 'AvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2475-53vw-vp25", "cve": "CVE-2022-35968", "id": "pyup.io-58333", "more_info_path": "/vulnerabilities/CVE-2022-35968/58333", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35965: Segfault in 'LowerBound' and 'UpperBound'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qxpx-j395-pw36", "cve": "CVE-2022-35965", "id": "pyup.io-58330", "more_info_path": "/vulnerabilities/CVE-2022-35965/58330", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35964: Segfault in 'BlockLSTMGradV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f7r5-q7cx-h668", "cve": "CVE-2022-35964", "id": "pyup.io-58308", "more_info_path": "/vulnerabilities/CVE-2022-35964/58308", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35963: 'CHECK' failures in 'FractionalAvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-84jm-4cf3-9jfm", "cve": "CVE-2022-35963", "id": "pyup.io-58338", "more_info_path": "/vulnerabilities/CVE-2022-35963/58338", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35952: 'CHECK' failures in 'UnbatchGradOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h5vq-gw2c-pq47", "cve": "CVE-2022-35952", "id": "pyup.io-58292", "more_info_path": "/vulnerabilities/CVE-2022-35952/58292", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35941: 'CHECK' failure in 'AvgPoolOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mgmh-g2v6-mqw5", "cve": "CVE-2022-35941", "id": "pyup.io-58327", "more_info_path": "/vulnerabilities/CVE-2022-35941/58327", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35940: Int overflow in 'RaggedRangeOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x989-q2pq-4q5x", "cve": "CVE-2022-35940", "id": "pyup.io-58336", "more_info_path": "/vulnerabilities/CVE-2022-35940/58336", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35939: OOB write in 'scatter_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-ffjm-4qwc-7cmf", "cve": "CVE-2022-35939", "id": "pyup.io-58291", "more_info_path": "/vulnerabilities/CVE-2022-35939/58291", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35937: OOB read in 'Gather_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pxrw-j2fv-hx3h", "cve": "CVE-2022-35937", "id": "pyup.io-58290", "more_info_path": "/vulnerabilities/CVE-2022-35937/58290", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35934: 'CHECK' failure in tf.reshape via overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f4w6-h4f5-wx45", "cve": "CVE-2022-35934", "id": "pyup.io-58300", "more_info_path": "/vulnerabilities/CVE-2022-35934/58300", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35988: 'CHECK' fail in 'tf.linalg.matrix_rank'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vqj-64pv-w55c", "cve": "CVE-2022-35988", "id": "pyup.io-58329", "more_info_path": "/vulnerabilities/CVE-2022-35988/58329", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41889: If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a 'nullptr', which is not caught. An example can be seen in 'tf.compat.v1.extract_volume_patches' by passing in quantized tensors as input 'ksizes'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xxcj-rhqg-m46g", "cve": "CVE-2022-41889", "id": "pyup.io-58269", "more_info_path": "/vulnerabilities/CVE-2022-41889/58269", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41910: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-frqp-wp83-qggv", "cve": "CVE-2022-41910", "id": "pyup.io-58284", "more_info_path": "/vulnerabilities/CVE-2022-41910/58284", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41901: An input 'sparse_matrix' that is not a matrix with a shape with rank 0 will trigger a 'CHECK' fail in 'tf.raw_ops.SparseMatrixNNZ'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9fm-r5mm-rf9f", "cve": "CVE-2022-41901", "id": "pyup.io-58265", "more_info_path": "/vulnerabilities/CVE-2022-41901/58265", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41899: TensorFlow is an open source platform for machine learning. Inputs 'dense_features' or 'example_state_data' not of rank 2 will trigger a 'CHECK' fail in 'SdcaOptimizer'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-27rc-728f-x5w2", "cve": "CVE-2022-41899", "id": "pyup.io-58271", "more_info_path": "/vulnerabilities/CVE-2022-41899/58271", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41897: If 'FractionMaxPoolGrad' is given outsize inputs 'row_pooling_sequence' and 'col_pooling_sequence', TensorFlow will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2w8-jw48-fr7j", "cve": "CVE-2022-41897", "id": "pyup.io-58282", "more_info_path": "/vulnerabilities/CVE-2022-41897/58282", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41896: If 'ThreadUnsafeUnigramCandidateSampler' is given input 'filterbank_channel_count' greater than the allowed max size, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rmg2-f698-wq35", "cve": "CVE-2022-41896", "id": "pyup.io-58280", "more_info_path": "/vulnerabilities/CVE-2022-41896/58280", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41895: If 'MirrorPadGrad' is given outsize input 'paddings', TensorFlow will give a heap OOB error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gq2j-cr96-gvqx", "cve": "CVE-2022-41895", "id": "pyup.io-58266", "more_info_path": "/vulnerabilities/CVE-2022-41895/58266", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41894: The reference kernel of the 'CONV_3D_TRANSPOSE' TensorFlow Lite operator wrongly increments the data_ptr when adding the bias to the result. Instead of 'data_ptr += num_channels;' it should be 'data_ptr += output_num_channels;' as if the number of input channels is different than the number of output channels, the wrong result will be returned and a buffer overflow will occur if num_channels > output_num_channels. An attacker can craft a model with a specific number of input channels. It is then possible to write specific values through the bias of the layer outside the bounds of the buffer. This attack only works if the reference kernel resolver is used in the interpreter.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6q3-vv32-2cq5", "cve": "CVE-2022-41894", "id": "pyup.io-58287", "more_info_path": "/vulnerabilities/CVE-2022-41894/58287", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41893: If 'tf.raw_ops.TensorListResize' is given a nonscalar value for input 'size', it results 'CHECK' fail which can be used to trigger a denial of service attack.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-67pf-62xr-q35m", "cve": "CVE-2022-41893", "id": "pyup.io-58272", "more_info_path": "/vulnerabilities/CVE-2022-41893/58272", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41891: If 'tf.raw_ops.TensorListConcat' is given 'element_shape=[]', it results segmentation fault which can be used to trigger a denial of service attack.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-66vq-54fq-6jvv", "cve": "CVE-2022-41891", "id": "pyup.io-58267", "more_info_path": "/vulnerabilities/CVE-2022-41891/58267", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41890: If 'BCast::ToShape' is given input larger than an 'int32', it will crash, despite being supposed to handle up to an 'int64'. An example can be seen in 'tf.experimental.numpy.outer' by passing in large input to the input 'b'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h246-cgh4-7475", "cve": "CVE-2022-41890", "id": "pyup.io-58276", "more_info_path": "/vulnerabilities/CVE-2022-41890/58276", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41888: When running on GPU, 'tf.image.generate_bounding_box_proposals' receives a 'scores' input that must be of rank 4 but is not checked.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6x99-gv2v-q76v", "cve": "CVE-2022-41888", "id": "pyup.io-58285", "more_info_path": "/vulnerabilities/CVE-2022-41888/58285", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41885: When 'tf.raw_ops.FusedResizeAndPadConv2D' is given a large tensor shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-762h-vpvw-3rcx", "cve": "CVE-2022-41885", "id": "pyup.io-58270", "more_info_path": "/vulnerabilities/CVE-2022-41885/58270", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1.", "cve": "CVE-2022-41902", "id": "pyup.io-58279", "more_info_path": "/vulnerabilities/CVE-2022-41902/58279", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41900: The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xvwp-h6jv-7472", "cve": "CVE-2022-41900", "id": "pyup.io-58275", "more_info_path": "/vulnerabilities/CVE-2022-41900/58275", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41886: When 'tf.raw_ops.ImageProjectiveTransformV2' is given a large output shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-54pp-c6pp-7fpx", "cve": "CVE-2022-41886", "id": "pyup.io-58283", "more_info_path": "/vulnerabilities/CVE-2022-41886/58283", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41884: If a numpy array is created with a shape such that one element is zero and the others sum to a large number, an error will be raised. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jq6x-99hj-q636", "cve": "CVE-2022-41884", "id": "pyup.io-58281", "more_info_path": "/vulnerabilities/CVE-2022-41884/58281", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41908: TensorFlow is an open source platform for machine learning. An input 'token' that is not a UTF-8 bytestring will trigger a 'CHECK' fail in 'tf.raw_ops.PyFunc'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv77-9g28-cwg3", "cve": "CVE-2022-41908", "id": "pyup.io-58274", "more_info_path": "/vulnerabilities/CVE-2022-41908/58274", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41880: When the 'BaseCandidateSamplerOp' function receives a value in 'true_classes' larger than 'range_max', a heap oob read occurs.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8w5g-3wcv-9g2j", "cve": "CVE-2022-41880", "id": "pyup.io-58277", "more_info_path": "/vulnerabilities/CVE-2022-41880/58277", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41909: An input 'encoded' that is not a valid 'CompositeTensorVariant' tensor will trigger a segfault in 'tf.raw_ops.CompositeTensorVariantToComponents'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjx6-v474-2ch9", "cve": "CVE-2022-41909", "id": "pyup.io-58273", "more_info_path": "/vulnerabilities/CVE-2022-41909/58273", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41911: When printing a tensor, we get it's data as a 'const char*' array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from 'char' to 'bool' are undefined if the 'char' is not '0' or '1', so sanitizers/fuzzers will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j", "cve": "CVE-2022-41911", "id": "pyup.io-58268", "more_info_path": "/vulnerabilities/CVE-2022-41911/58268", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41898: If 'SparseFillEmptyRowsGrad' is given empty inputs, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hq7g-wwwp-q46h", "cve": "CVE-2022-41898", "id": "pyup.io-58286", "more_info_path": "/vulnerabilities/CVE-2022-41898/58286", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41907: When 'tf.raw_ops.ResizeNearestNeighborGrad' is given a large 'size' input, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-368v-7v32-52fx", "cve": "CVE-2022-41907", "id": "pyup.io-58278", "more_info_path": "/vulnerabilities/CVE-2022-41907/58278", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35935: 'CHECK' failure in 'SobolSample' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-97p7-w86h-vcf9\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqvq-fvhr-v6hc", "cve": "CVE-2022-35935", "id": "pyup.io-58288", "more_info_path": "/vulnerabilities/CVE-2022-35935/58288", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-macos 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35991: 'CHECK' fail in 'TensorListScatter' and 'TensorListScatterV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vm7x-4qhj-rrcq\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xf83-q765-xm6m", "cve": "CVE-2022-35991", "id": "pyup.io-58289", "more_info_path": "/vulnerabilities/CVE-2022-35991/58289", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-macos 2.9.3 and 2.10.1 include a fix for CVE-2022-41887: 'tf.keras.losses.poisson' receives a 'y_pred' and 'y_true' that are passed through 'functor::mul' in 'BinaryOp'. If the resulting dimensions overflow an 'int32', TensorFlow will crash due to a size mismatch during broadcast assignment.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fvv-46hw-vpg3", "cve": "CVE-2022-41887", "id": "pyup.io-58264", "more_info_path": "/vulnerabilities/CVE-2022-41887/58264", "specs": [ "<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.10.1 includes a fix for CVE-2022-41883: When ops that have specified input sizes receive a differing number of inputs, the executor will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj", "cve": "CVE-2022-41883", "id": "pyup.io-58263", "more_info_path": "/vulnerabilities/CVE-2022-41883/58263", "specs": [ ">=2.10.0rc0,<2.10.1" ], "v": ">=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37688: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer. The Tensorflow team has patched the issue in GitHub commit 15691e456c7dc9bd6be203b09765b063bf4a380c.", "cve": "CVE-2021-37688", "id": "pyup.io-58514", "more_info_path": "/vulnerabilities/CVE-2021-37688/58514", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37691: In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). The Tensorflow team has patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9.", "cve": "CVE-2021-37691", "id": "pyup.io-58516", "more_info_path": "/vulnerabilities/CVE-2021-37691/58516", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37645: In affected versions the implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit 96f364a1ca3009f98980021c4b32be5fdcca33a1.", "cve": "CVE-2021-37645", "id": "pyup.io-58515", "more_info_path": "/vulnerabilities/CVE-2021-37645/58515", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-macos versions 2.5.1 and 2.6.0 include a fix for CVE-2021-37692:\nIn affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, \"C.TF_TString_Dealloc\" is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until \"NewTensor\" returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. The Tensorflow team has patched the issue in GitHub commit:\nhttps://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22\nhttps://github.com/tensorflow/tensorflow/pull/50508\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cmgw-8vpc-rc59", "cve": "CVE-2021-37692", "id": "pyup.io-58512", "more_info_path": "/vulnerabilities/CVE-2021-37692/58512", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-macos 2.5.1 and 2.6.0 include a fix for CVE-2021-37640: In affected versions the implementation of 'tf.raw_ops.SparseReshape' can be made to trigger an integral division by 0 exception. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements. The reshape functor (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0. The Tensorflow team has patched the issue in GitHub commit 4923de56ec94fff7770df259ab7f2288a74feb41.", "cve": "CVE-2021-37640", "id": "pyup.io-58513", "more_info_path": "/vulnerabilities/CVE-2021-37640/58513", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-macos versions 2.3.4, 2.4.3, 2.5.1, and 2.6.0 update its dependency \"curl\" to include a fix for CVE-2021-22898", "cve": "CVE-2021-22898", "id": "pyup.io-58511", "more_info_path": "/vulnerabilities/CVE-2021-22898/58511", "specs": [ ">=2.6.0a1,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0a1,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37657: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. The Tensorflow team has checked that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit f2a673bd34f0d64b8e40a551ac78989d16daad09.", "cve": "CVE-2021-37657", "id": "pyup.io-58500", "more_info_path": "/vulnerabilities/CVE-2021-37657/58500", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37668:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.UnravelIndex\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by \"dims\" is not empty. Hence, if one element of \"dims\" is 0, the implementation does a division by 0. The Tensorflow team has patched the issue in GitHub commit a776040a5e7ebf76eeb7eb923bf1ae417dd4d233.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2wmv-37vq-52g5\nhttps://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233", "cve": "CVE-2021-37668", "id": "pyup.io-58501", "more_info_path": "/vulnerabilities/CVE-2021-37668/58501", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37685: In affected versions TFLite's 'expand_dims.cc' (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data. If 'axis' is a large negative value (e.g., '-100000'), then after the first 'if' it would still be negative. The check following the 'if' statement will pass and the 'for' loop would read one element before the start of 'input_dims.data' (when 'i = 0'). The Tensorflow team has patched the issue in GitHub commit d94ffe08a65400f898241c0374e9edc6fa8ed257.", "cve": "CVE-2021-37685", "id": "pyup.io-58503", "more_info_path": "/vulnerabilities/CVE-2021-37685/58503", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37687: In affected versions TFLite's 'GatherNd' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation. Hence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in 'indices'. Similar issue exists in 'Gather' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc). The Tensorflow team has patched the issue in GitHub commits bb6a0383ed553c286f87ca88c207f6774d5c4a8f and eb921122119a6b6e470ee98b89e65d721663179d.", "cve": "CVE-2021-37687", "id": "pyup.io-58507", "more_info_path": "/vulnerabilities/CVE-2021-37687/58507", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37653: In affected versions an attacker can trigger a crash via a floating point exception in 'tf.raw_ops.ResourceGather'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, 'batch_size', and then divides by it without checking that this value is not 0. The Tensorflow team has patched the issue in GitHub commit ac117ee8a8ea57b73d34665cdf00ef3303bc0b11.", "cve": "CVE-2021-37653", "id": "pyup.io-58509", "more_info_path": "/vulnerabilities/CVE-2021-37653/58509", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37665:\nIn affected versions, due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the \"input\" tensor. A similar issue occurs in \"MklRequantizePerChannelOp\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments. The Tensorflow team has patched the issue in GitHub commit 9e62869465573cb2d9b5053f1fa02a81fce21d69 and in the Github commit 203214568f5bc237603dbab6e1fd389f1572f5c9.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v82p-hv3v-p6qp\nhttps://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9\nhttps://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69", "cve": "CVE-2021-37665", "id": "pyup.io-58505", "more_info_path": "/vulnerabilities/CVE-2021-37665/58505", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37663:\nIn affected versions, due to incomplete validation in \"tf.raw_ops.QuantizeV2\", an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that \"min_range\" and \"max_range\" both have the same non-zero number of elements. If \"axis\" is provided (i.e., not \"-1\"), then validation should check that it is a value in range for the rank of \"input\" tensor and then the lengths of \"min_range\" and \"max_range\" inputs match the \"axis\" dimension of the \"input\" tensor. The Tensorflow team has patched the issue in GitHub commit 6da6620efad397c85493b8f8667b821403516708. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g25h-jr74-qp5j\nhttps://github.com/tensorflow/tensorflow/commit/6da6620efad397c85493b8f8667b821403516708", "cve": "CVE-2021-37663", "id": "pyup.io-58502", "more_info_path": "/vulnerabilities/CVE-2021-37663/58502", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37676: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.SparseFillEmptyRows'. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors. The Tensorflow team has patched the issue in GitHub commit 578e634b4f1c1c684d4b4294f9e5281b2133b3ed.", "cve": "CVE-2021-37676", "id": "pyup.io-58508", "more_info_path": "/vulnerabilities/CVE-2021-37676/58508", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37675: In affected versions most implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations. The Tensorflow team has patched the issue in GitHub commit 8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4.", "cve": "CVE-2021-37675", "id": "pyup.io-58506", "more_info_path": "/vulnerabilities/CVE-2021-37675/58506", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37661: In affected versions an attacker can cause a denial of service in 'boosted_trees_create_quantile_stream_resource' by using negative arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that 'num_streams' only contains non-negative numbers. In turn, this results in using this value to allocate memory (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40). However, 'reserve' receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library. The Tensorflow team has patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992.", "cve": "CVE-2021-37661", "id": "pyup.io-58504", "more_info_path": "/vulnerabilities/CVE-2021-37661/58504", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37660: In affected versions an attacker can cause a floating point exception by calling inplace operations with crafted arguments that would result in a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/inplace_ops.cc#L283) has a logic error: it should skip processing if 'x' and 'v' are empty but the code uses '||' instead of '&&'. The Tensorflow team has patched the issue in GitHub commit e86605c0a336c088b638da02135ea6f9f6753618.", "cve": "CVE-2021-37660", "id": "pyup.io-58510", "more_info_path": "/vulnerabilities/CVE-2021-37660/58510", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37643: If a user does not provide a valid padding value to 'tf.raw_ops.MatrixDiagPartOp', then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from. The Tensorflow team has patched the issue in GitHub commit 482da92095c4d48f8784b1f00dda4f81c28d2988.", "cve": "CVE-2021-37643", "id": "pyup.io-58494", "more_info_path": "/vulnerabilities/CVE-2021-37643/58494", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37644: In affected versions providing a negative element to 'num_elements' list argument of 'tf.raw_ops.TensorListReserve' causes the runtime to abort the process due to reallocating a 'std::vector' to have a negative number of elements. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls 'std::vector.resize()' with the new size controlled by input given by the user, without checking that this input is valid. The Tensorflow team has patched the issue in GitHub commit 8a6e874437670045e6c7dc6154c7412b4a2135e2.", "cve": "CVE-2021-37644", "id": "pyup.io-58497", "more_info_path": "/vulnerabilities/CVE-2021-37644/58497", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37684: In affected versions the implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695 (https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).", "cve": "CVE-2021-37684", "id": "pyup.io-58492", "more_info_path": "/vulnerabilities/CVE-2021-37684/58492", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37681: In affected versions the implementation of SVDF in TFLite is vulnerable to a null pointer error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313). The 'GetVariableInput' function (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but 'GetTensorData' assumes that the argument is always a valid tensor. Furthermore, because 'GetVariableInput' calls 'GetMutableInput' (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return 'nullptr', the 'tensor->is_variable' expression can also trigger a null pointer exception. The Tensorflow team has patched the issue in GitHub commit 5b048e87e4e55990dae6b547add4dae59f4e1c76.", "cve": "CVE-2021-37681", "id": "pyup.io-58496", "more_info_path": "/vulnerabilities/CVE-2021-37681/58496", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37666: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToVariant'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty. The Tensorflow team has patched the issue in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612.", "cve": "CVE-2021-37666", "id": "pyup.io-58499", "more_info_path": "/vulnerabilities/CVE-2021-37666/58499", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37662: In affected versions an attacker can generate undefined behavior via a reference binding to nullptr in 'BoostedTreesCalculateBestGainsPerFeature' and similar attack can occur in 'BoostedTreesCalculateBestFeatureSplitV2'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values. The Tensorflow team has patched the issue in GitHub commit 9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad and in commit 429f009d2b2c09028647dd4bb7b3f6f414bbaad7.", "cve": "CVE-2021-37662", "id": "pyup.io-58493", "more_info_path": "/vulnerabilities/CVE-2021-37662/58493", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37646: In affected versions the implementation of 'tf.raw_ops.StringNGrams' is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls 'reserve' on a 'tstring' with a value that sometimes can be negative if user supplies negative 'ngram_widths'. The 'reserve' method calls 'TF_TString_Reserve' which has an 'unsigned long' argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5.", "cve": "CVE-2021-37646", "id": "pyup.io-58498", "more_info_path": "/vulnerabilities/CVE-2021-37646/58498", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37641: In affected versions if the arguments to 'tf.raw_ops.RaggedGather' don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by 'params_nested_splits' is not an empty list of tensors. The Tensorflow team has patched the issue in GitHub commit a2b743f6017d7b97af1fe49087ae15f0ac634373.", "cve": "CVE-2021-37641", "id": "pyup.io-58495", "more_info_path": "/vulnerabilities/CVE-2021-37641/58495", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37690:\nIn affected versions when running shape functions, some functions (such as 'MutableHashTableShape') produce extra output information in the form of a 'ShapeAndType' struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault. 'ShapeRefiner' is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but the Tensorflow team was not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types. The Tensorflow team has patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3hxh-8cp2-g4hg\nhttps://github.com/tensorflow/tensorflow/commit/ee119d4a498979525046fba1c3dd3f13a039fbb1", "cve": "CVE-2021-37690", "id": "pyup.io-58491", "more_info_path": "/vulnerabilities/CVE-2021-37690/58491", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37682:\nIn affected versions all TFLite operations that use quantization can be made to use unitialized values. (For example, https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200). The issue stems from the fact that \"quantization.params\" is only valid if \"quantization.type\" is different that \"kTfLiteNoQuantization\". However, these checks are missing in large parts of the code. The Tensorflow team has patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4c4g-crqm-xrxw\nhttps://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5\nhttps://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887\nhttps://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538", "cve": "CVE-2021-37682", "id": "pyup.io-58490", "more_info_path": "/vulnerabilities/CVE-2021-37682/58490", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22901", "id": "pyup.io-58481", "more_info_path": "/vulnerabilities/CVE-2021-22901/58481", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22897", "id": "pyup.io-58482", "more_info_path": "/vulnerabilities/CVE-2021-22897/58482", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22876", "id": "pyup.io-58483", "more_info_path": "/vulnerabilities/CVE-2021-22876/58483", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37669:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.NonMaxSuppressionV5\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a \"std::vector\". However, as \"std::vector::resize\" takes the size argument as a \"size_t\" and \"output_size\" is an \"int\", there is an implicit conversion to unsigned. If the attacker supplies a negative value, this conversion results in a crash. A similar issue occurs in \"CombinedNonMaxSuppression\". The Tensorflow team has patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c\nhttps://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d\nhttps://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58", "cve": "CVE-2021-37669", "id": "pyup.io-58487", "more_info_path": "/vulnerabilities/CVE-2021-37669/58487", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos versions 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37677: In affected versions the shape inference code for \"tf.raw_ops.Dequantize\" has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses \"axis\" to select between two different values for \"minmax_rank\" which is then used to retrieve tensor dimensions. However, code assumes that \"axis\" can be either \"-1\" or a value greater than \"-1\", with no validation for the other values.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qfpc-5pjr-mh26\r\nhttps://github.com/tensorflow/tensorflow/commit/da857cfa0fde8f79ad0afdbc94e88b5d4bbec764", "cve": "CVE-2021-37677", "id": "pyup.io-58488", "more_info_path": "/vulnerabilities/CVE-2021-37677/58488", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37655: TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to 'tf.raw_ops.ResourceScatterUpdate'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of 'indices' and 'updates': instead of checking that the shape of 'indices' is a prefix of the shape of 'updates' (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. The Tensorflow team has patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f.", "cve": "CVE-2021-37655", "id": "pyup.io-58477", "more_info_path": "/vulnerabilities/CVE-2021-37655/58477", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37673:\nIn affected versions, an attacker can trigger a denial of service via a \"CHECK\"-fail in \"tf.raw_ops.MapStage\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the \"key\" input is a valid non-empty tensor. The Tensorflow team has patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-278g-rq84-9hmg\nhttps://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d", "cve": "CVE-2021-37673", "id": "pyup.io-58484", "more_info_path": "/vulnerabilities/CVE-2021-37673/58484", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37672:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.SdcaOptimizerV2\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of \"example_labels\" is the same as the number of examples. The Tensorflow team has patched the issue in GitHub commit a4e138660270e7599793fa438cd7b2fc2ce215a6.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hj3-vjjf-f5m7\nhttps://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6", "cve": "CVE-2021-37672", "id": "pyup.io-58478", "more_info_path": "/vulnerabilities/CVE-2021-37672/58478", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37670:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.UpperBound\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of \"sorted_input\" argument. A similar issue occurs in \"tf.raw_ops.LowerBound\". The Tensorflow team has patched the issue in GitHub commit 42459e4273c2e47a3232cc16c4f4fff3b3a35c38.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9697-98pf-4rw7\nhttps://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38", "cve": "CVE-2021-37670", "id": "pyup.io-58479", "more_info_path": "/vulnerabilities/CVE-2021-37670/58479", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37679:\nIn affected versions it is possible to nest a \"tf.map_fn\" within another \"tf.map_fn\" call. However, if the input tensor is a \"RaggedTensor\" and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap. The \"t\" and \"z\" outputs should be identical, however this is not the case. The last row of \"t\" contains data from the heap which can be used to leak other memory information. The bug lies in the conversion from a \"Variant\" tensor to a \"RaggedTensor\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions. The same implementation can result in data loss, if input tensor is tweaked. The Tensorflow team has patched the issue in GitHub commit 4e2565483d0ffcadc719bd44893fb7f609bb5f12.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g8wg-cjwc-xhhp\nhttps://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12", "cve": "CVE-2021-37679", "id": "pyup.io-58480", "more_info_path": "/vulnerabilities/CVE-2021-37679/58480", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos versions 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37674: In affected versions, an attacker can trigger a denial of service via a segmentation fault in \"tf.raw_ops.MaxPoolGrad\" caused by missing validation. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the \"orig_input\" and \"orig_output\" tensors. The fixes for CVE-2021-29579 were incomplete. The Tensorflow team has patched the issue in GitHub commit 136b51f10903e044308cf77117c0ed9871350475.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7ghq-fvr3-pj2x\r\nhttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-068.md\r\nhttps://github.com/tensorflow/tensorflow/commit/136b51f10903e044308cf77117c0ed9871350475", "cve": "CVE-2021-37674", "id": "pyup.io-58486", "more_info_path": "/vulnerabilities/CVE-2021-37674/58486", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37650: In affected versions the implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types. The Tensorflow team has patched the issue in GitHub commit e0b6e58c328059829c3eb968136f17aa72b6c876.", "cve": "CVE-2021-37650", "id": "pyup.io-58485", "more_info_path": "/vulnerabilities/CVE-2021-37650/58485", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-macos version 2.3.4, 2.4.3, 2.5.1, 2.6.0 and 2.7.0 include a fix for CVE-2021-37678:\nIn affected versions, TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The implementation(https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses \"yaml.unsafe_load\" which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, the Tensorflow team has removed it for now. The Tensorflow team has patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r\nhttps://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012", "cve": "CVE-2021-37678", "id": "pyup.io-58489", "more_info_path": "/vulnerabilities/CVE-2021-37678/58489", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.7.0rc0,<2.7.0" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.7.0rc0,<2.7.0" }, { "advisory": "Tensorflow-macos version 2.6.1 includes a fix for CVE-2021-41211: In affected versions, the shape inference code for 'QuantizeV2' can trigger a read outside of bounds of heap allocated array. This occurs whenever 'axis' is a negative value less than '-1'. In this case, we are accessing data before the start of a heap buffer. The code allows 'axis' to be an optional argument ('s' would contain an 'error::NOT_FOUND' error code). Otherwise, it assumes that 'axis' is a valid index into the dimensions of the 'input' tensor. If 'axis' is less than '-1' then this results in a heap OOB read. The fix is included in TensorFlow 2.7.0. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvgx-3v3q-m36c\nhttps://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244", "cve": "CVE-2021-41211", "id": "pyup.io-58476", "more_info_path": "/vulnerabilities/CVE-2021-41211/58476", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos version 2.6.1 includes a fix for CVE-2021-41220: In affected versions, the async implementation of 'CollectiveReduceV2' suffers from a memory leak and a use after free. This occurs due to the asynchronous computation and the fact that objects that have been 'std::move()'d are still accessed. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gpfh-jvf9-7wg5\nhttps://github.com/tensorflow/tensorflow/commit/ca38dab9d3ee66c5de06f11af9a4b1200da5ef75", "cve": "CVE-2021-41220", "id": "pyup.io-58475", "more_info_path": "/vulnerabilities/CVE-2021-41220/58475", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-macos versions 2.7.1 and 2.8.0 include a fix for CVE-2022-23590: A 'GraphDef' from a TensorFlow 'SavedModel' can be maliciously altered to cause a TensorFlow process to crash due to encountering a 'StatusOr' value that is an error and forcibly extracting the value from it.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pqrv-8r2f-7278", "cve": "CVE-2022-23590", "id": "pyup.io-58384", "more_info_path": "/vulnerabilities/CVE-2022-23590/58384", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos is an Open Source Machine Learning Framework. The TFG dialect of TensorFlow (MLIR) makes several assumptions about the incoming `GraphDef` before converting it to the MLIR-based dialect. If an attacker changes the `SavedModel` format on disk to invalidate these assumptions and the `GraphDef` is then converted to MLIR-based IR then they can cause a crash in the Python interpreter. Under certain scenarios, heap OOB read/writes are possible. These issues have been discovered via fuzzing and it is possible that more weaknesses exist. We will patch them as they are discovered.", "cve": "CVE-2022-23594", "id": "pyup.io-58385", "more_info_path": "/vulnerabilities/CVE-2022-23594/58385", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos 2.8.0 includes a fix for CVE-2022-23593: The 'simplifyBroadcast' function in the MLIR-TFRT infrastructure in TensorFlow is vulnerable to a segfault (hence, denial of service), if called with scalar shapes. If all shapes are scalar, then 'maxRank' is 0, so we build an empty 'SmallVector'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gwcx-jrx4-92w2", "cve": "CVE-2022-23593", "id": "pyup.io-58383", "more_info_path": "/vulnerabilities/CVE-2022-23593/58383", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-macos version 2.8.0 includes a fix for CVE-2022-23592: TensorFlow's type inference can cause a heap out of bounds read as the bounds checking is done in a 'DCHECK' (which is a no-op during production). An attacker can control the 'input_idx' variable such that 'ix' would be larger than the number of values in 'node_t.args'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vq36-27g6-p492", "cve": "CVE-2022-23592", "id": "pyup.io-58382", "more_info_path": "/vulnerabilities/CVE-2022-23592/58382", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "TensorFlow is an open source platform for machine learning. In version 2.8.0, the 'TensorKey' hash function used total estimated 'AllocatedBytes()', which (a) is an estimate per tensor, and (b) is a very poor hash function for constants (e.g. 'int32_t'). It also tried to access individual tensor bytes through 'tensor.data()' of size 'AllocatedBytes()'. This led to ASAN failures because the 'AllocatedBytes()' is an estimate of total bytes allocated by a tensor, including any pointed-to constructs (e.g. strings), and does not refer to contiguous bytes in the '.data()' buffer. The discoverers could not use this byte vector anyway because types such as 'tstring' include pointers, whereas they needed to hash the string values themselves. This issue is patched in Tensorflow versions 2.9.0 and 2.8.1.", "cve": "CVE-2022-29210", "id": "pyup.io-58346", "more_info_path": "/vulnerabilities/CVE-2022-29210/58346", "specs": [ ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": ">=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" } ], "tensorflow-model-analysis": [ { "advisory": "Tensorflow-model-analysis 0.14.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/tensorflow/model-analysis/commit/4c2a9f16f8f07b28b17e956089eaf359d1b6997b", "cve": "PVE-2023-60390", "id": "pyup.io-60390", "more_info_path": "/vulnerabilities/PVE-2023-60390/60390", "specs": [ "<0.14.0" ], "v": "<0.14.0" } ], "tensorflow-rocm": [ { "advisory": "Tensorflow-rocm versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"SQLite\" to handle CVE-2019-19645.", "cve": "CVE-2019-19645", "id": "pyup.io-58005", "more_info_path": "/vulnerabilities/CVE-2019-19645/58005", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-rocm versions 1.15.3, 2.0.2 and 2.1.1 update its dependency \"Apache Spark\" to handle CVE-2018-11770.", "cve": "CVE-2018-11770", "id": "pyup.io-58010", "more_info_path": "/vulnerabilities/CVE-2018-11770/58010", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-rocm versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"Apache Spark\" to handle CVE-2018-17190.", "cve": "CVE-2018-17190", "id": "pyup.io-58009", "more_info_path": "/vulnerabilities/CVE-2018-17190/58009", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-rocm versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2018-20330.", "cve": "CVE-2018-20330", "id": "pyup.io-58007", "more_info_path": "/vulnerabilities/CVE-2018-20330/58007", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-rocm versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2019-13960.", "cve": "CVE-2019-13960", "id": "pyup.io-58008", "more_info_path": "/vulnerabilities/CVE-2019-13960/58008", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-rocm versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"SQLite3\" to handle CVE-2019-19244.", "cve": "CVE-2019-19244", "id": "pyup.io-58004", "more_info_path": "/vulnerabilities/CVE-2019-19244/58004", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-rocm versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"Apache Spark\" to handle CVE-2019-10099.", "cve": "CVE-2019-10099", "id": "pyup.io-58011", "more_info_path": "/vulnerabilities/CVE-2019-10099/58011", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-rocm versions 1.15.3, 2.0.2 and 2.1.1 updates its dependency \"libjpeg-turbo\" to handle CVE-2018-19664.", "cve": "CVE-2018-19664", "id": "pyup.io-58006", "more_info_path": "/vulnerabilities/CVE-2018-19664/58006", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-rocm versions 1.15.3, 2.0.2 and 2.1.1 update its dependency \"SQLite3\" to handle CVE-2019-19880.", "cve": "CVE-2019-19880", "id": "pyup.io-58003", "more_info_path": "/vulnerabilities/CVE-2019-19880/58003", "specs": [ "<1.15.3", ">=2.0.0a0,<2.0.2", ">=2.1.0rc0,<2.1.1" ], "v": "<1.15.3,>=2.0.0a0,<2.0.2,>=2.1.0rc0,<2.1.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15208: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a \"DCHECK\" which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue was patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d", "cve": "CVE-2020-15208", "id": "pyup.io-57982", "more_info_path": "/vulnerabilities/CVE-2020-15208/57982", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15207: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses 'ResolveAxis' to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the 'DCHECK' does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34", "cve": "CVE-2020-15207", "id": "pyup.io-57988", "more_info_path": "/vulnerabilities/CVE-2020-15207/57988", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15205: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'data_splits' argument of 'tf.raw_ops.StringNGrams' lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after 'ee ff' are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46", "cve": "CVE-2020-15205", "id": "pyup.io-57986", "more_info_path": "/vulnerabilities/CVE-2020-15205/57986", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15211: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor. However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative \"-1\" value as index for these tensors. This results in special casing during validation at model loading time. Unfortunately, this means that the \"-1\" index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays. This results in both read and write gadgets, albeit very limited in scope. The issue was patched in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83). A potential workaround would be to add a custom \"Verifier\" to the model loading code to ensure that only operators which accept optional inputs use the \"-1\" special value and only for the tensors that they expect to be optional. Since this allow-list type approach is error-prone, it's advised upgrading to the patched code.", "cve": "CVE-2020-15211", "id": "pyup.io-57981", "more_info_path": "/vulnerabilities/CVE-2020-15211/57981", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15209: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a \"nullptr\" buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with \"nullptr\". However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue was patched in commit 0b5662bc.", "cve": "CVE-2020-15209", "id": "pyup.io-57985", "more_info_path": "/vulnerabilities/CVE-2020-15209/57985", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15206: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's \"SavedModel\" protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using \"tensorflow-serving\" or other inference-as-a-service installments. Fixed were added in commits f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d. However, this was not enough, as #41097 reported a different failure mode. The issue was finally patched in commit df095206f25471e864a8e63a0f1caef53a0e3a6", "cve": "CVE-2020-15206", "id": "pyup.io-57980", "more_info_path": "/vulnerabilities/CVE-2020-15206/57980", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15203: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the 'fill' argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a 'printf' call is constructed. This may result in segmentation fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79", "cve": "CVE-2020-15203", "id": "pyup.io-57987", "more_info_path": "/vulnerabilities/CVE-2020-15203/57987", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15204: In eager mode, TensorFlow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling \"tf.raw_ops.GetSessionHandle\" or \"tf.raw_ops.GetSessionHandleV2\" results in a null pointer dereference In linked snippet, in eager mode, \"ctx->session_state()\" returns \"nullptr\". Since code immediately dereferences this, we get a segmentation fault. The issue was patched in commit 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1", "cve": "CVE-2020-15204", "id": "pyup.io-57978", "more_info_path": "/vulnerabilities/CVE-2020-15204/57978", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15195: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of 'SparseFillEmptyRowsGrad' uses a double indexing pattern. It is possible for 'reverse_index_map(i)' to be an index outside of bounds of 'grad_values', thus resulting in a heap buffer overflow.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-63xm-rx5p-xvqr", "cve": "CVE-2020-15195", "id": "pyup.io-57979", "more_info_path": "/vulnerabilities/CVE-2020-15195/57979", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15190: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the \"tf.raw_ops.Switch\" operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is \"nullptr\", hence we are binding a reference to \"nullptr\". This is undefined behavior and reported as an error if compiling with \"-fsanitize=null\". In this case, this results in a segmentation fault The issue was patched in commit da8558533d925694483d2c136a9220d6d49d843c\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4g9f-63rx-5cw4", "cve": "CVE-2020-15190", "id": "pyup.io-57983", "more_info_path": "/vulnerabilities/CVE-2020-15190/57983", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15202: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'Shard' API in TensorFlow expects the last argument to be a function taking two 'int64' (i.e., 'long long') arguments. However, there are several places in TensorFlow where a lambda taking 'int' or 'int32' arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4", "cve": "CVE-2020-15202", "id": "pyup.io-57984", "more_info_path": "/vulnerabilities/CVE-2020-15202/57984", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13631.", "cve": "CVE-2020-13631", "id": "pyup.io-57974", "more_info_path": "/vulnerabilities/CVE-2020-13631/57974", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11656.", "cve": "CVE-2020-11656", "id": "pyup.io-57973", "more_info_path": "/vulnerabilities/CVE-2020-11656/57973", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11655.", "cve": "CVE-2020-11655", "id": "pyup.io-57972", "more_info_path": "/vulnerabilities/CVE-2020-11655/57972", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13871.", "cve": "CVE-2020-13871", "id": "pyup.io-57968", "more_info_path": "/vulnerabilities/CVE-2020-13871/57968", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-9327.", "cve": "CVE-2020-9327", "id": "pyup.io-57971", "more_info_path": "/vulnerabilities/CVE-2020-9327/57971", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13435.", "cve": "CVE-2020-13435", "id": "pyup.io-57975", "more_info_path": "/vulnerabilities/CVE-2020-13435/57975", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13630.", "cve": "CVE-2020-13630", "id": "pyup.io-57969", "more_info_path": "/vulnerabilities/CVE-2020-13630/57969", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13434.", "cve": "CVE-2020-13434", "id": "pyup.io-57970", "more_info_path": "/vulnerabilities/CVE-2020-13434/57970", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm 2.4.0 includes a fix for CVE-2020-15194: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments. Although `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\"", "cve": "CVE-2020-15194", "id": "pyup.io-57977", "more_info_path": "/vulnerabilities/CVE-2020-15194/57977", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15210: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x9j7-x98r-r4w2", "cve": "CVE-2020-15210", "id": "pyup.io-57976", "more_info_path": "/vulnerabilities/CVE-2020-15210/57976", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.5, 2.0.4, 2.1.3, 2.2.2 and 2.3.2 update its dependency \"PCRE\" to handle CVE-2020-14155.", "cve": "CVE-2020-14155", "id": "pyup.io-57956", "more_info_path": "/vulnerabilities/CVE-2020-14155/57956", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-rocm versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency \"PCRE\" to fix CVE-2019-20838.", "cve": "CVE-2019-20838", "id": "pyup.io-57954", "more_info_path": "/vulnerabilities/CVE-2019-20838/57954", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-rocm versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 updates its dependency \"Libjpeg-turbo\" to handle CVE-2020-13790.", "cve": "CVE-2020-13790", "id": "pyup.io-57957", "more_info_path": "/vulnerabilities/CVE-2020-13790/57957", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-rocm versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency 'Junit4' to v4.13.1 to include a security fix.", "cve": "CVE-2020-15250", "id": "pyup.io-57955", "more_info_path": "/vulnerabilities/CVE-2020-15250/57955", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-rocm versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26270: In affected versions, running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.", "cve": "CVE-2020-26270", "id": "pyup.io-57962", "more_info_path": "/vulnerabilities/CVE-2020-26270/57962", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26267: In affected versions, the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes.", "cve": "CVE-2020-26267", "id": "pyup.io-57959", "more_info_path": "/vulnerabilities/CVE-2020-26267/57959", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26271: In affected versions, under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library.", "cve": "CVE-2020-26271", "id": "pyup.io-57958", "more_info_path": "/vulnerabilities/CVE-2020-26271/57958", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0 includes a fix for CVE-2020-26266: In affected versions and under certain cases a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers filled with the default value of the type but forgetting to default initialize the quantized floating point types in Eigen.", "cve": "CVE-2020-26266", "id": "pyup.io-57960", "more_info_path": "/vulnerabilities/CVE-2020-26266/57960", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26268: In affected versions, the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden.", "cve": "CVE-2020-26268", "id": "pyup.io-57961", "more_info_path": "/vulnerabilities/CVE-2020-26268/57961", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-27579: Constructing a tflite model with a paramater 'filter_input_channel' of less than 1 gives a FPE.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5w96-866f-6rm8", "cve": "CVE-2023-27579", "id": "pyup.io-57554", "more_info_path": "/vulnerabilities/CVE-2023-27579/57554", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25801: Prior to versions 2.12.0 and 2.11.1, 'nn_ops.fractional_avg_pool_v2' and 'nn_ops.fractional_max_pool_v2' require the first and fourth elements of their parameter 'pooling_ratio' to be equal to 1.0, as pooling on batch and channel dimensions is not supported.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f49c-87jh-g47q", "cve": "CVE-2023-25801", "id": "pyup.io-57551", "more_info_path": "/vulnerabilities/CVE-2023-25801/57551", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25675: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.Bincount' segfaults when given a parameter 'weights' that is neither the same shape as parameter 'arr' nor a length-0 tensor.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7x4v-9gxg-9hwj", "cve": "CVE-2023-25675", "id": "pyup.io-57552", "more_info_path": "/vulnerabilities/CVE-2023-25675/57552", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25674: Versions prior to 2.12.0 and 2.11.1 have a null pointer error in RandomShuffle with XLA enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf97-q72m-7579", "cve": "CVE-2023-25674", "id": "pyup.io-57549", "more_info_path": "/vulnerabilities/CVE-2023-25674/57549", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25673: Versions prior to 2.12.0 and 2.11.1 have a Floating Point Exception in TensorListSplit with XLA. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25673", "id": "pyup.io-57544", "more_info_path": "/vulnerabilities/CVE-2023-25673/57544", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25672: The function 'tf.raw_ops.LookupTableImportV2' cannot handle scalars in the 'values' parameter and gives an NPE. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.", "cve": "CVE-2023-25672", "id": "pyup.io-57545", "more_info_path": "/vulnerabilities/CVE-2023-25672/57545", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25670: Versions prior to 2.12.0 and 2.11.1 have a null point error in QuantizedMatMulWithBiasAndDequantize with MKL enabled.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rq-hwc3-x77w", "cve": "CVE-2023-25670", "id": "pyup.io-57556", "more_info_path": "/vulnerabilities/CVE-2023-25670/57556", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25669: Prior to versions 2.12.0 and 2.11.1, if the stride and window size are not positive for 'tf.raw_ops.AvgPoolGrad', it can give a floating point exception.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rcf8-g8jv-vg6p", "cve": "CVE-2023-25669", "id": "pyup.io-57557", "more_info_path": "/vulnerabilities/CVE-2023-25669/57557", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25666: Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2", "cve": "CVE-2023-25666", "id": "pyup.io-57547", "more_info_path": "/vulnerabilities/CVE-2023-25666/57547", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25665: Prior to versions 2.12.0 and 2.11.1, when 'SparseSparseMaximum' is given invalid sparse tensors as inputs, it can give a null pointer error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-558h-mq8x-7q9g", "cve": "CVE-2023-25665", "id": "pyup.io-57553", "more_info_path": "/vulnerabilities/CVE-2023-25665/57553", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25664: Prior to versions 2.12.0 and 2.11.1, there is a heap buffer overflow in TAvgPoolGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hg6-5c2q-7rcr", "cve": "CVE-2023-25664", "id": "pyup.io-57559", "more_info_path": "/vulnerabilities/CVE-2023-25664/57559", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25659: Prior to versions 2.12.0 and 2.11.1, if the parameter 'indices' for 'DynamicStitch' does not match the shape of the parameter 'data', it can trigger an stack OOB read.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-93vr-9q9m-pj8p", "cve": "CVE-2023-25659", "id": "pyup.io-57563", "more_info_path": "/vulnerabilities/CVE-2023-25659/57563", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25658: Prior to versions 2.12.0 and 2.11.1, an out of bounds read is in GRUBlockCellGrad.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-68v3-g9cm-rmm6", "cve": "CVE-2023-25658", "id": "pyup.io-57564", "more_info_path": "/vulnerabilities/CVE-2023-25658/57564", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25676: When running versions prior to 2.12.0 and 2.11.1 with XLA, 'tf.raw_ops.ParallelConcat' segfaults with a nullptr dereference when given a parameter 'shape' with rank that is not greater than zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6wfh-89q8-44jq", "cve": "CVE-2023-25676", "id": "pyup.io-57546", "more_info_path": "/vulnerabilities/CVE-2023-25676/57546", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25661: In versions prior to 2.11.1 a malicious invalid input crashes a tensorflow model (Check Failed) and can be used to trigger a denial of service attack. A proof of concept can be constructed with the 'Convolution3DTranspose' function. This Convolution3DTranspose layer is a very common API in modern neural networks. The ML models containing such vulnerable components could be deployed in ML applications or as cloud services. This failure could be potentially used to trigger a denial of service attack on ML cloud services. An attacker must have privilege to provide input to a 'Convolution3DTranspose' call.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fxgc-95xx-grvq", "cve": "CVE-2023-25661", "id": "pyup.io-57550", "more_info_path": "/vulnerabilities/CVE-2023-25661/57550", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25668: Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gw97-ff7c-9v96", "cve": "CVE-2023-25668", "id": "pyup.io-57558", "more_info_path": "/vulnerabilities/CVE-2023-25668/57558", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25671: There is out-of-bounds access due to mismatched integer type sizes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j5w9-hmfh-4cr6", "cve": "CVE-2023-25671", "id": "pyup.io-57555", "more_info_path": "/vulnerabilities/CVE-2023-25671/57555", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25660: Prior to versions 2.12.0 and 2.11.1, when the parameter 'summarize' of 'tf.raw_ops.Print' is zero, the new method 'SummarizeArray' will reference to a nullptr, leading to a seg fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qjqc-vqcf-5qvj", "cve": "CVE-2023-25660", "id": "pyup.io-57562", "more_info_path": "/vulnerabilities/CVE-2023-25660/57562", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25667: Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when '2^31 <= num_frames * height * width * channels < 2^32', for example Full HD screencast of at least 346 frames.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqm2-gh8w-gr68", "cve": "CVE-2023-25667", "id": "pyup.io-57548", "more_info_path": "/vulnerabilities/CVE-2023-25667/57548", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25662: Versions prior to 2.12.0 and 2.11.1 are vulnerable to integer overflow in EditDistance.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7jvm-xxmr-v5cw", "cve": "CVE-2023-25662", "id": "pyup.io-57561", "more_info_path": "/vulnerabilities/CVE-2023-25662/57561", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Tensorflow-rocm 2.11.0* and previous versions are affected by CVE-2023-25663: Prior to versions 2.12.0 and 2.11.1, when 'ctx->step_containter()' is a null ptr, the Lookup function will be executed with a null pointer.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-64jg-wjww-7c5w", "cve": "CVE-2023-25663", "id": "pyup.io-57560", "more_info_path": "/vulnerabilities/CVE-2023-25663/57560", "specs": [ "<2.11.1", ">=2.12.0rc0,<2.12.0" ], "v": "<2.11.1,>=2.12.0rc0,<2.12.0" }, { "advisory": "Affected versions of Tensorflow are vulnerable to Integer Overflow. array_ops.upper_bound' causes a segfault when not given a rank 2 tensor. The flaw was fixed in May 30, 2023, but the CVE was published in July 30, 2024. It was noticed unpublished by the Safety CLI Cyber Security team.", "cve": "CVE-2023-33976", "id": "pyup.io-72430", "more_info_path": "/vulnerabilities/CVE-2023-33976/72430", "specs": [ "<2.12.1", ">=2.13.0rc0,<2.13.0" ], "v": "<2.12.1,>=2.13.0rc0,<2.13.0" }, { "advisory": "Tensorflow-rocm 2.4.0 includes a fix for CVE-2020-15265: In Tensorflow before version 2.4.0, an attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`. This results in accessing a dimension outside the rank of the input tensor in the C++ kernel implementation. However, dim_size only does a DCHECK to validate the argument and then uses it to access the corresponding element of an array. Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.", "cve": "CVE-2020-15265", "id": "pyup.io-57966", "more_info_path": "/vulnerabilities/CVE-2020-15265/57966", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Tensorflow-rocm 2.4.0 includes a fix for CVE-2020-15266: In Tensorflow before version 2.4.0, when the 'boxes' argument of 'tf.image.crop_and_resize' has a very large value, the CPU kernel implementation receives it as a C++ 'nan' floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault.\nhttps://github.com/tensorflow/tensorflow/issues/42129\nhttps://github.com/tensorflow/tensorflow/pull/42143/commits/3ade2efec2e90c6237de32a19680caaa3ebc2845\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xwhf-g6j5-j5gc", "cve": "CVE-2020-15266", "id": "pyup.io-57964", "more_info_path": "/vulnerabilities/CVE-2020-15266/57964", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22923.", "cve": "CVE-2021-22923", "id": "pyup.io-57761", "more_info_path": "/vulnerabilities/CVE-2021-22923/57761", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22924.", "cve": "CVE-2021-22924", "id": "pyup.io-57760", "more_info_path": "/vulnerabilities/CVE-2021-22924/57760", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41219: In affected versions, the code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to 'nullptr'. This occurs whenever the dimensions of 'a' or 'b' are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, it should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4f99-p9c2-3j8x\nhttps://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae", "cve": "CVE-2021-41219", "id": "pyup.io-57759", "more_info_path": "/vulnerabilities/CVE-2021-41219/57759", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22925.", "cve": "CVE-2021-22925", "id": "pyup.io-57743", "more_info_path": "/vulnerabilities/CVE-2021-22925/57743", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41221: In affected versions, the shape inference code for the 'Cudnn*' operations can be tricked into accessing invalid memory via a heap buffer overflow. This occurs because the ranks of the 'input', 'input_h' and 'input_c' parameters are not validated, but code assumes they have certain values. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqv6-3phm-hcwx\nhttps://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6", "cve": "CVE-2021-41221", "id": "pyup.io-57772", "more_info_path": "/vulnerabilities/CVE-2021-41221/57772", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22922.", "cve": "CVE-2021-22922", "id": "pyup.io-57744", "more_info_path": "/vulnerabilities/CVE-2021-22922/57744", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41209: In affected versions, the implementations for convolution operators trigger a division by 0 if passed empty filter tensor arguments. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6hpv-v2rx-c5g6\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41209", "id": "pyup.io-57749", "more_info_path": "/vulnerabilities/CVE-2021-41209/57749", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41218: In affected versions, the shape inference code for 'AllToAll' can be made to execute a division by 0. This occurs whenever the 'split_count' argument is 0. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9crf-c6qr-r273\nhttps://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc", "cve": "CVE-2021-41218", "id": "pyup.io-57746", "more_info_path": "/vulnerabilities/CVE-2021-41218/57746", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41214: In affected versions, the shape inference code for 'tf.ragged.cross' has an undefined behavior due to binding a reference to 'nullptr'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vwhq-49r4-gj9v\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41214", "id": "pyup.io-57758", "more_info_path": "/vulnerabilities/CVE-2021-41214/57758", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41223: In affected versions, the implementation of 'FusedBatchNorm' kernels is vulnerable to a heap OOB access. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f54p-f6jp-4rhr\nhttps://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda", "cve": "CVE-2021-41223", "id": "pyup.io-57754", "more_info_path": "/vulnerabilities/CVE-2021-41223/57754", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41205: In affected versions, the shape inference functions for the 'QuantizeAndDequantizeV*' operations can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rx-x2rw-pc6f\nhttps://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d", "cve": "CVE-2021-41205", "id": "pyup.io-57757", "more_info_path": "/vulnerabilities/CVE-2021-41205/57757", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41228: In affected versions, TensorFlow's 'saved_model_cli' tool is vulnerable to a code injection as it calls 'eval' on user supplied strings. This can be used by attackers to run arbitrary code on the plaform where the CLI tool runs. However, given that the tool is always run manually, the impact of this is not severe. The issue has been patched by adding a 'safe' flag which defaults to 'True' and an explicit warning for users.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3rcw-9p9x-582v\nhttps://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7", "cve": "CVE-2021-41228", "id": "pyup.io-57751", "more_info_path": "/vulnerabilities/CVE-2021-41228/57751", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41196: In affected versions, the Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative. This is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m539-j985-hcr8", "cve": "CVE-2021-41196", "id": "pyup.io-57747", "more_info_path": "/vulnerabilities/CVE-2021-41196/57747", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41207: In affected versions, the implementation of 'ParallelConcat' misses some input validation and can produce a division by 0. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7v94-64hj-m82h\nhttps://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235", "cve": "CVE-2021-41207", "id": "pyup.io-57763", "more_info_path": "/vulnerabilities/CVE-2021-41207/57763", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41217: In affected versions, the process of building the control flow graph for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not. This occurs because the code assumes that the first node in the pairing (e.g., an 'Enter' node) always exists when encountering the second node (e.g., an 'Exit' node). When this is not the case, 'parent' is 'nullptr' so dereferencing it causes a crash. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5crj-c72x-m7gq\nhttps://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff", "cve": "CVE-2021-41217", "id": "pyup.io-57756", "more_info_path": "/vulnerabilities/CVE-2021-41217/57756", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 update its dependency 'curl' to v7.78.0 to handle CVE-2021-22926.", "cve": "CVE-2021-22926", "id": "pyup.io-57752", "more_info_path": "/vulnerabilities/CVE-2021-22926/57752", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41215: In affected versions, the shape inference code for 'DeserializeSparse' can trigger a null pointer dereference. This is because the shape inference function assumes that the 'serialize_sparse' tensor is a tensor with positive rank (and having '3' as the last dimension). The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x3v8-c8qx-3j3r\nhttps://github.com/tensorflow/tensorflow/commit/d3738dd70f1c9ceb547258cbb82d853da8771850", "cve": "CVE-2021-41215", "id": "pyup.io-57753", "more_info_path": "/vulnerabilities/CVE-2021-41215/57753", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41212: In affected versions, the shape inference code for 'tf.ragged.cross' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fr77-rrx3-cp7g\nhttps://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8", "cve": "CVE-2021-41212", "id": "pyup.io-57773", "more_info_path": "/vulnerabilities/CVE-2021-41212/57773", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41216: In affected versions, the shape inference function for 'Transpose' is vulnerable to a heap buffer overflow. This occurs whenever 'perm' contains negative elements. The shape inference function does not validate that the indices in 'perm' are all valid. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3ff2-r28g-w7h9\nhttps://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14", "cve": "CVE-2021-41216", "id": "pyup.io-57762", "more_info_path": "/vulnerabilities/CVE-2021-41216/57762", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41200: In affected versions, if 'tf.summary.create_file_writer' is called with non-scalar arguments, code crashes due to a 'CHECK'-fail. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh8h-7j2j-qv4f", "cve": "CVE-2021-41200", "id": "pyup.io-57771", "more_info_path": "/vulnerabilities/CVE-2021-41200/57771", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41210: In affected versions, the shape inference functions for 'SparseCountSparseOutput' can trigger a read outside of bounds of heap allocated array. The fix is included in TensorFlow 2.7.0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m342-ff57-4jcc\r\nhttps://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2", "cve": "CVE-2021-41210", "id": "pyup.io-57776", "more_info_path": "/vulnerabilities/CVE-2021-41210/57776", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41195: In affected versions, the implementation of 'tf.math.segment_*' operations results in a 'CHECK'-fail related abort (and denial of service) if a segment id in 'segment_ids' is large. This is similar to CVE-2021-29584 (and similar to other reported vulnerabilities in TensorFlow localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using 'AddDim'. However, if the number of elements in the tensor overflows an 'int64_t' value, 'AddDim' results in a 'CHECK' failure which provokes a 'std::abort'. Instead, code should use 'AddDimWithStatus'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cq76-mxrc-vchh", "cve": "CVE-2021-41195", "id": "pyup.io-57750", "more_info_path": "/vulnerabilities/CVE-2021-41195/57750", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41213: In affected versions, the code behind 'tf.function' API can be made to deadlock when two 'tf.function' decorated Python functions are mutually recursive. This occurs due to using a non-reentrant 'Lock' Python object. Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive 'tf.function', although this is not a frequent scenario.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcf\nhttps://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7", "cve": "CVE-2021-41213", "id": "pyup.io-57769", "more_info_path": "/vulnerabilities/CVE-2021-41213/57769", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41225: In affected versions, TensorFlow's Grappler optimizer has a use of unitialized variable. If the 'train_nodes' vector (obtained from the saved model that gets optimized) does not contain a 'Dequeue' node, then 'dequeue_node' is left unitialized. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7r94-xv9v-63jw\nhttps://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3", "cve": "CVE-2021-41225", "id": "pyup.io-57774", "more_info_path": "/vulnerabilities/CVE-2021-41225/57774", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41227: In affected versions, the 'ImmutableConst' operation in TensorFlow can be tricked into reading arbitrary memory contents. This is because the 'tstring' TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j8c8-67vp-6mx7\nhttps://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b\nhttps://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585", "cve": "CVE-2021-41227", "id": "pyup.io-57745", "more_info_path": "/vulnerabilities/CVE-2021-41227/57745", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41222: In affected versions, the implementation of 'SplitV' can trigger a segfault if an attacker supplies negative arguments. This occurs whenever 'size_splits' contains more than one value and at least one value is negative. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cpf4-wx82-gxp6\nhttps://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6", "cve": "CVE-2021-41222", "id": "pyup.io-57770", "more_info_path": "/vulnerabilities/CVE-2021-41222/57770", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41202: In affected versions, while calculating the size of the output within the 'tf.range' kernel, there is a conditional statement of type 'int64 = condition ? int64 : double'. Due to C++ implicit conversion rules, both branches of the condition will be cast to 'double' and the result would be truncated before the assignment. This result in overflows. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xrqm-fpgr-6hhx", "cve": "CVE-2021-41202", "id": "pyup.io-57764", "more_info_path": "/vulnerabilities/CVE-2021-41202/57764", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41226: In affected versions, the implementation of 'SparseBinCount' is vulnerable to a heap OOB access. This is because of missing validation between the elements of the 'values' argument and the shape of the sparse output. The fix is also included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-374m-jm66-3vj8\nhttps://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba", "cve": "CVE-2021-41226", "id": "pyup.io-57766", "more_info_path": "/vulnerabilities/CVE-2021-41226/57766", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41224: In affected versions, the implementation of 'SparseFillEmptyRows' can be made to trigger a heap OOB access. This occurs whenever the size of 'indices' does not match the size of 'values'. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rg3m-hqc5-344v\nhttps://github.com/tensorflow/tensorflow/commit/67bfd9feeecfb3c61d80f0e46d89c170fbee682b", "cve": "CVE-2021-41224", "id": "pyup.io-57755", "more_info_path": "/vulnerabilities/CVE-2021-41224/57755", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41204: In affected versions, during TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-786j-5qwq-r36x\nhttps://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659", "cve": "CVE-2021-41204", "id": "pyup.io-57765", "more_info_path": "/vulnerabilities/CVE-2021-41204/57765", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41203: In affected versions, an attacker can trigger undefined behavior, integer overflows, segfaults and 'CHECK'-fail crashes if they can change saved checkpoints from outside of TensorFlow. This is because the checkpoints loading infrastructure is missing validation for invalid file formats.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7pxj-m4jf-r6h2", "cve": "CVE-2021-41203", "id": "pyup.io-57768", "more_info_path": "/vulnerabilities/CVE-2021-41203/57768", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41201: In affected versions, during execution, 'EinsumHelper::ParseEquation()' is supposed to set the flags in 'input_has_ellipsis' vector and '*output_has_ellipsis' boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to 'true' and never assigns 'false'. This results in unitialized variable access if callers assume that 'EinsumHelper::ParseEquation()' always sets these flags. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j86v-p27c-73fm\nhttps://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6", "cve": "CVE-2021-41201", "id": "pyup.io-57748", "more_info_path": "/vulnerabilities/CVE-2021-41201/57748", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41199: In affected versions, if 'tf.image.resize' is called with a large input argument then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hx2-qx8j-qjqm", "cve": "CVE-2021-41199", "id": "pyup.io-57767", "more_info_path": "/vulnerabilities/CVE-2021-41199/57767", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm versions 2.4.4, 2.5.2 and 2.6.1 include a fix for CVE-2021-41198: In affected versions, if 'tf.tile' is called with a large input argument, then the TensorFlow process will crash due to a 'CHECK'-failure caused by an overflow. The number of elements in the output tensor is too much for the 'int64_t' type and the overflow is detected via a 'CHECK' statement. This aborts the process. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2p25-55c9-h58q", "cve": "CVE-2021-41198", "id": "pyup.io-57775", "more_info_path": "/vulnerabilities/CVE-2021-41198/57775", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1" }, { "advisory": "Affected versions of Tensorflow-rocm allow tensors to have a large number of dimensions and each dimension can be as large as desired. However, the total number of elements in a tensor must fit within an 'int64_t'. If an overflow occurs, 'MultiplyWithoutOverflow' would return a negative result. In the majority of TensorFlow codebase this then results in a 'CHECK'-failure. Newer constructs exist which return a 'Status' instead of crashing the binary. This is a similar issue to CVE-2021-29584.", "cve": "CVE-2021-41197", "id": "pyup.io-57661", "more_info_path": "/vulnerabilities/CVE-2021-41197/57661", "specs": [ "<2.4.4", ">=2.5.0rc0,<2.5.2", ">=2.6.0rc0,<2.6.1", ">=2.7.0rc0,<2.7.0" ], "v": "<2.4.4,>=2.5.0rc0,<2.5.2,>=2.6.0rc0,<2.6.1,>=2.7.0rc0,<2.7.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3 and 2.7.1 update its dependency 'icu' to v69.1 to include a security fix.", "cve": "CVE-2020-10531", "id": "pyup.io-57690", "more_info_path": "/vulnerabilities/CVE-2020-10531/57690", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, TensorFlow might do a null-dereference if attributes of some mutable arguments to some operations are missing from the proto. This is guarded by a `DCHECK`. However, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the dereferencing of the null pointer, whereas in the second case it results in a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23570", "id": "pyup.io-57698", "more_info_path": "/vulnerabilities/CVE-2022-23570/57698", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23557: An attacker can craft a TFLite model that would trigger a division by zero in 'BiasAndClamp' implementation. There is no check that the 'bias_size' is non zero.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf2j-f278-xh4v", "cve": "CVE-2022-23557", "id": "pyup.io-57725", "more_info_path": "/vulnerabilities/CVE-2022-23557/57725", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. TensorFlow is vulnerable to a heap OOB write in `Grappler`. The `set_output` function writes to an array at the specified index. Hence, this gives a malicious user a write primitive. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23566", "id": "pyup.io-57733", "more_info_path": "/vulnerabilities/CVE-2022-23566/57733", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21728: The implementation of shape inference for 'ReverseSequence' does not fully validate the value of 'batch_dim' and can result in a heap OOB read. There is a check to make sure the value of 'batch_dim' does not go over the rank of the input, but there is no check for negative values. Negative dimensions are allowed in some cases to mimic Python's negative indexing (i.e., indexing from the end of the array), however if the value is too negative then the implementation of 'Dim' would access elements before the start of an array.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6gmv-pjp9-p8w8", "cve": "CVE-2022-21728", "id": "pyup.io-57692", "more_info_path": "/vulnerabilities/CVE-2022-21728/57692", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21732: The implementation of 'ThreadPoolHandle' can be used to trigger a denial of service attack by allocating too much memory. This is because the 'num_threads' argument is only checked to not be negative, but there is no upper bound on its value.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c582-c96p-r5cq", "cve": "CVE-2022-21732", "id": "pyup.io-57731", "more_info_path": "/vulnerabilities/CVE-2022-21732/57731", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. There is a typo in TensorFlow's `SpecializeType` which results in heap OOB read/write. Due to a typo, `arg` is initialized to the `i`th mutable argument in a loop where the loop index is `j`. Hence it is possible to assign to `arg` from outside the vector of arguments. Since this is a mutable proto value, it allows both read and write to outside of bounds data. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23574", "id": "pyup.io-57708", "more_info_path": "/vulnerabilities/CVE-2022-23574/57708", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21727: The implementation of shape inference for 'Dequantize' is vulnerable to an integer overflow weakness. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked, and, since the code computes 'axis + 1', an attacker can trigger an integer overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-c6fh-56w7-fvjw", "cve": "CVE-2022-21727", "id": "pyup.io-57717", "more_info_path": "/vulnerabilities/CVE-2022-21727/57717", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23563: In multiple places, TensorFlow uses 'tempfile.mktemp' to create temporary files. While this is acceptable in testing, in utilities and libraries it is dangerous as a different process can create the file between the check for the filename in 'mktemp' and the actual creation of the file by a subsequent operation (a TOC/TOU type of weakness). In several instances, TensorFlow was supposed to actually create a temporary directory instead of a file. This logic bug is hidden away by the 'mktemp' function usage. It was replaced 'mktemp' with the safer 'mkstemp'/'mkdtemp' functions, according to the usage pattern.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wc4g-r73w-x8mm", "cve": "CVE-2022-23563", "id": "pyup.io-57693", "more_info_path": "/vulnerabilities/CVE-2022-23563/57693", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow can trigger a null pointer dereference. There are 2 places where this can occur, for the same malicious alteration of a `SavedModel` file (fixing the first one would trigger the same dereference in the second place). First, during constant folding, the `GraphDef` might not have the required nodes for the binary operation. If a node is missing, the correposning `mul_*child` would be null, and the dereference in the subsequent line would be incorrect. We have a similar issue during `IsIdentityConsumingSwitch`. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23589", "id": "pyup.io-57705", "more_info_path": "/vulnerabilities/CVE-2022-23589/57705", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23595: When building an XLA compilation cache, if default settings are used, TensorFlow triggers a null pointer dereference. In the default scenario, all devices are allowed, so 'flr->config_proto' is 'nullptr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fpcp-9h7m-ffpx", "cve": "CVE-2022-23595", "id": "pyup.io-57696", "more_info_path": "/vulnerabilities/CVE-2022-23595/57696", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. The 'GraphDef' format in TensorFlow does not allow self recursive functions. The runtime assumes that this invariant is satisfied. However, a 'GraphDef' containing a fragment such as the following can be consumed when loading a 'SavedModel'. This would result in a stack overflow during execution as resolving each 'NodeDef' means resolving the function itself and its nodes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23591", "id": "pyup.io-57730", "more_info_path": "/vulnerabilities/CVE-2022-23591/57730", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that Grappler optimizer would attempt to build a tensor using a reference `dtype`. This would result in a crash due to a `CHECK`-fail in the `Tensor` constructor as reference types are not allowed. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23588", "id": "pyup.io-57737", "more_info_path": "/vulnerabilities/CVE-2022-23588/57737", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow is vulnerable to an integer overflow during cost estimation for crop and resize. Since the cropping parameters are user controlled, a malicious person can trigger undefined behavior. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23587", "id": "pyup.io-57722", "more_info_path": "/vulnerabilities/CVE-2022-23587/57722", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that assertions in `function.cc` would be falsified and crash the Python interpreter. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23586", "id": "pyup.io-57716", "more_info_path": "/vulnerabilities/CVE-2022-23586/57716", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. When decoding PNG images TensorFlow can produce a memory leak if the image is invalid. After calling `png::CommonInitDecode(..., &decode)`, the `decode` value contains allocated buffers which can only be freed by calling `png::CommonFreeDecode(&decode)`. However, several error case in the function implementation invoke the `OP_REQUIRES` macro which immediately terminates the execution of the function, without allowing for the memory free to occur. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23585", "id": "pyup.io-57700", "more_info_path": "/vulnerabilities/CVE-2022-23585/57700", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. A malicious user can cause a use after free behavior when decoding PNG images. After `png::CommonFreeDecode(&decode)` gets called, the values of `decode.width` and `decode.height` are in an unspecified state. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23584", "id": "pyup.io-57738", "more_info_path": "/vulnerabilities/CVE-2022-23584/57738", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a 'SavedModel' such that any binary op would trigger 'CHECK' failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the 'dtype' no longer matches the 'dtype' expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If 'Tin' and 'Tout' don't match the type of data in 'out' and 'input_*' tensors then 'flat<*>' would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a 'CHECK' crash, hence a denial of service. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23583", "id": "pyup.io-57702", "more_info_path": "/vulnerabilities/CVE-2022-23583/57702", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23582: A malicious user can cause a denial of service by altering a 'SavedModel' such that 'TensorByteSize' would trigger 'CHECK' failures. 'TensorShape' constructor throws a 'CHECK'-fail if shape is partial or has a number of elements that would overflow the size of an 'int'. The 'PartialTensorShape' constructor instead does not cause a 'CHECK'-abort if the shape is partial, which is exactly what this function needs to be able to return '-1'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4j82-5ccr-4r8v", "cve": "CVE-2022-23582", "id": "pyup.io-57739", "more_info_path": "/vulnerabilities/CVE-2022-23582/57739", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21731: The implementation of shape inference for 'ConcatV2' can be used to trigger a denial of service attack via a segfault caused by a type confusion. The 'axis' argument is translated into 'concat_dim' in the 'ConcatShapeHelper' helper function. Then, a value for 'min_rank' is computed based on 'concat_dim'. This is then used to validate that the 'values' tensor has at least the required rank. However, 'WithRankAtLeast' receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented. Due to the fact that 'min_rank' is a 32-bits value and the value of 'axis', the 'rank' argument is a negative value, so the error check is bypassed.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m4hf-j54p-p353", "cve": "CVE-2022-21731", "id": "pyup.io-57742", "more_info_path": "/vulnerabilities/CVE-2022-21731/57742", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21726: The implementation of 'Dequantize' does not fully validate the value of 'axis' and can result in heap OOB accesses. The 'axis' argument can be '-1' (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked and this results in reading past the end of the array containing the dimensions of the input tensor.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-23hm-7w47-xw72", "cve": "CVE-2022-21726", "id": "pyup.io-57740", "more_info_path": "/vulnerabilities/CVE-2022-21726/57740", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23581: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'IsSimplifiableReshape' would trigger 'CHECK' failures.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fq86-3f29-px2c", "cve": "CVE-2022-23581", "id": "pyup.io-57706", "more_info_path": "/vulnerabilities/CVE-2022-23581/57706", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21735: The implementation of 'FractionalMaxPool' can be made to crash a TensorFlow process via a division by 0.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-87v6-crgm-2gfj", "cve": "CVE-2022-21735", "id": "pyup.io-57724", "more_info_path": "/vulnerabilities/CVE-2022-21735/57724", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21725: The estimator for the cost of some convolution operations can be made to execute a division by 0. The function fails to check that the stride argument is strictly positive. Hence, the fix is to add a check for the stride argument to ensure it is valid.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v3f7-j968-4h5f", "cve": "CVE-2022-21725", "id": "pyup.io-57723", "more_info_path": "/vulnerabilities/CVE-2022-21725/57723", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21733: The implementation of 'StringNGrams' can be used to trigger a denial of service attack by causing an out of memory condition after an integer overflow. There is missing a validation on 'pad_witdh' and that result in computing a negative value for 'ngram_width' which is later used to allocate parts of the output.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98j8-c9q4-r38g", "cve": "CVE-2022-21733", "id": "pyup.io-57720", "more_info_path": "/vulnerabilities/CVE-2022-21733/57720", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21739: The implementation of 'QuantizedMaxPool' has an undefined behavior where user controlled inputs can trigger a reference binding to null pointer.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3mw4-6rj6-74g5", "cve": "CVE-2022-21739", "id": "pyup.io-57713", "more_info_path": "/vulnerabilities/CVE-2022-21739/57713", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21737: The implementation of '*Bincount' operations allows malicious users to cause denial of service by passing in arguments which would trigger a 'CHECK'-fail. There are several conditions that the input arguments must satisfy. Some are not caught during shape inference and others are not caught during kernel implementation. This results in 'CHECK' failures later when the output tensors get allocated.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2vv-v9cg-qhh7", "cve": "CVE-2022-21737", "id": "pyup.io-57707", "more_info_path": "/vulnerabilities/CVE-2022-21737/57707", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21741: An attacker can craft a TFLite model that would trigger a division by zero in the implementation of depthwise convolutions. The parameters of the convolution can be user controlled and are also used within a division operation to determine the size of the padding that needs to be added before applying the convolution. There is no check before this division that the divisor is strictly positive.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-428x-9xc2-m8mj", "cve": "CVE-2022-21741", "id": "pyup.io-57697", "more_info_path": "/vulnerabilities/CVE-2022-21741/57697", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23580: During shape inference, TensorFlow can allocate a large vector based on a value from a tensor controlled by the user.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-627q-g293-49q7", "cve": "CVE-2022-23580", "id": "pyup.io-57728", "more_info_path": "/vulnerabilities/CVE-2022-23580/57728", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23568: The implementation of 'AddManySparseToTensorsMap' is vulnerable to an integer overflow which results in a 'CHECK'-fail when building new 'TensorShape' objects (so, an assert failure based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6445-fm66-fvq2", "cve": "CVE-2022-23568", "id": "pyup.io-57691", "more_info_path": "/vulnerabilities/CVE-2022-23568/57691", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23579: The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a 'SavedModel' such that 'SafeToRemoveIdentity' would trigger 'CHECK' failures.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5f2r-qp73-37mr", "cve": "CVE-2022-23579", "id": "pyup.io-57734", "more_info_path": "/vulnerabilities/CVE-2022-23579/57734", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. If a graph node is invalid, TensorFlow can leak memory in the implementation of `ImmutableExecutorState::Initialize`. Here, we set `item->kernel` to `nullptr` but it is a simple `OpKernel*` pointer so the memory that was previously allocated to it would leak. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23578", "id": "pyup.io-57704", "more_info_path": "/vulnerabilities/CVE-2022-23578/57704", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. The implementation of `GetInitOp` is vulnerable to a crash caused by dereferencing a null pointer. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23577", "id": "pyup.io-57729", "more_info_path": "/vulnerabilities/CVE-2022-23577/57729", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateOutputSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve tensors with large enough number of elements. We can have a large enough number of dimensions in `output_shape.dim()` or just a small number of dimensions being large enough to cause an overflow in the multiplication. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23576", "id": "pyup.io-57701", "more_info_path": "/vulnerabilities/CVE-2022-23576/57701", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateTensorSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve a tensor with large enough number of elements. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23575", "id": "pyup.io-57710", "more_info_path": "/vulnerabilities/CVE-2022-23575/57710", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized data to a new tensor. This later results in undefined behavior. The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23573", "id": "pyup.io-57703", "more_info_path": "/vulnerabilities/CVE-2022-23573/57703", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, TensorFlow can fail to specialize a type during shape inference. This case is covered by the 'DCHECK' function however, 'DCHECK' is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the 'ValueOrDie' line. This results in an assertion failure as 'ret' contains an error 'Status', not a value. In the second case we also get a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23572", "id": "pyup.io-57726", "more_info_path": "/vulnerabilities/CVE-2022-23572/57726", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.", "cve": "CVE-2022-23571", "id": "pyup.io-57718", "more_info_path": "/vulnerabilities/CVE-2022-23571/57718", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23565: An attacker can trigger denial of service via assertion failure by altering a 'SavedModel' on disk such that 'AttrDef's of some operation are duplicated.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4v5p-v5h9-6xjx", "cve": "CVE-2022-23565", "id": "pyup.io-57727", "more_info_path": "/vulnerabilities/CVE-2022-23565/57727", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23564: When decoding a resource handle tensor from protobuf, a TensorFlow process can encounter cases where a 'CHECK' assertion is invalidated based on user controlled arguments. This allows attackers to cause denial of services in TensorFlow processes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8rcj-c8pj-v3m3", "cve": "CVE-2022-23564", "id": "pyup.io-57719", "more_info_path": "/vulnerabilities/CVE-2022-23564/57719", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23562: The implementation of 'Range' suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qx3f-p745-w4hr", "cve": "CVE-2022-23562", "id": "pyup.io-57735", "more_info_path": "/vulnerabilities/CVE-2022-23562/57735", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23561: An attacker can craft a TFLite model that would cause a write outside of bounds of an array in TFLite. In fact, the attacker can override the linked list used by the memory allocator. This can be leveraged for an arbitrary write primitive under certain conditions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9c78-vcq7-7vxq", "cve": "CVE-2022-23561", "id": "pyup.io-57741", "more_info_path": "/vulnerabilities/CVE-2022-23561/57741", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23560: An attacker can craft a TFLite model that would allow limited reads and writes outside of arrays in TFLite. This exploits missing validation in the conversion from sparse tensors to dense tensors.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4hvf-hxvg-f67v", "cve": "CVE-2022-23560", "id": "pyup.io-57721", "more_info_path": "/vulnerabilities/CVE-2022-23560/57721", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23558: An attacker can craft a TFLite model that would cause an integer overflow in 'TfLiteIntArrayCreate'. The 'TfLiteIntArrayGetSizeInBytes' returns an 'int' instead of a 'size_t'. An attacker can control model inputs such that 'computed_size' overflows the size of 'int' datatype.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9gwq-6cwj-47h3", "cve": "CVE-2022-23558", "id": "pyup.io-57711", "more_info_path": "/vulnerabilities/CVE-2022-23558/57711", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21738: The implementation of 'SparseCountSparseOutput' can be made to crash a TensorFlow process by an integer overflow whose result is then used in a memory allocation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x4qx-4fjv-hmw6", "cve": "CVE-2022-21738", "id": "pyup.io-57736", "more_info_path": "/vulnerabilities/CVE-2022-21738/57736", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23559: An attacker can craft a TFLite model that would cause an integer overflow in embedding lookup operations. Both 'embedding_size' and 'lookup_size' are products of values provided by the user. Hence, a malicious user could trigger overflows in the multiplication. In certain scenarios, this can then result in heap OOB read/write.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98p5-x8x4-c9m5", "cve": "CVE-2022-23559", "id": "pyup.io-57714", "more_info_path": "/vulnerabilities/CVE-2022-23559/57714", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21729: The implementation of 'UnravelIndex' is vulnerable to a division by zero caused by an integer overflow bug.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-34f9-hjfq-rr8j", "cve": "CVE-2022-21729", "id": "pyup.io-57715", "more_info_path": "/vulnerabilities/CVE-2022-21729/57715", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21730: The implementation of 'FractionalAvgPoolGrad' does not consider cases where the input tensors are invalid allowing an attacker to read from outside of bounds of heap.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vjg4-v33c-ggc4", "cve": "CVE-2022-21730", "id": "pyup.io-57694", "more_info_path": "/vulnerabilities/CVE-2022-21730/57694", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21734: The implementation of 'MapStage' is vulnerable to a 'CHECK'-fail if the key tensor is not a scalar.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gcvh-66ff-4mwm", "cve": "CVE-2022-21734", "id": "pyup.io-57699", "more_info_path": "/vulnerabilities/CVE-2022-21734/57699", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23569: Multiple operations in TensorFlow can be used to trigger a denial of service via 'CHECK'-fails (i.e., assertion failures). This is similar to CVE-2021-41197 and has a similar fix. It is possible that other similar instances exist.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qj5r-f9mv-rffh", "cve": "CVE-2022-23569", "id": "pyup.io-57709", "more_info_path": "/vulnerabilities/CVE-2022-23569/57709", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21740: The implementation of 'SparseCountSparseOutput' is vulnerable to a heap overflow.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-44qp-9wwf-734r", "cve": "CVE-2022-21740", "id": "pyup.io-57732", "more_info_path": "/vulnerabilities/CVE-2022-21740/57732", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-23567: The implementations of 'Sparse*Cwise*' ops are vulnerable to integer overflows. These can be used to trigger large allocations (so, OOM based denial of service) or 'CHECK'-fails when building new 'TensorShape' objects (so, assert failures based denial of service). There are missing some validation on the shapes of the input tensors as well as directly constructing a large 'TensorShape' with user-provided dimensions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rrx2-r989-2c43", "cve": "CVE-2022-23567", "id": "pyup.io-57712", "more_info_path": "/vulnerabilities/CVE-2022-23567/57712", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3, 2.7.1 and 2.8.0 include a fix for CVE-2022-21736: The implementation of 'SparseTensorSliceDataset' has an undefined behavior: under certain conditions, it can be made to dereference a 'nullptr' value. The 3 input arguments to 'SparseTensorSliceDataset' represent a sparse tensor. However, there are some preconditions that these arguments must satisfy, but these are not validated in the implementation.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pfjj-m3jj-9jc9", "cve": "CVE-2022-21736", "id": "pyup.io-57695", "more_info_path": "/vulnerabilities/CVE-2022-21736/57695", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41208: In affected versions, the code for boosted trees in TensorFlow is still missing validation. As a result, attackers can trigger denial of service (via dereferencing 'nullptr's or via 'CHECK'-failures) as well as abuse undefined behavior (binding references to 'nullptr's). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call. Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. TensorFlow's boosted trees APIs will be deprecated in subsequent releases.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-57wx-m983-2f88\nhttps://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6gw-r52c-724r", "cve": "CVE-2021-41208", "id": "pyup.io-57689", "more_info_path": "/vulnerabilities/CVE-2021-41208/57689", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Tensorflow-rocm versions 2.5.3, 2.6.3 and 2.7.1 include a fix for CVE-2021-41206: In affected versions, several TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or 'CHECK'-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible. These issues were discovered internally via tooling while working on improving/testing GPU op determinism. As such, there aren't reproducers and there will be multiple fixes for these issues.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pgcq-h79j-2f69\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-43q8-3fv7-pr5x", "cve": "CVE-2021-41206", "id": "pyup.io-57688", "more_info_path": "/vulnerabilities/CVE-2021-41206/57688", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1" }, { "advisory": "Affected versions of Tensorflow-rocm are vulnerable to Denial of Service via CHECK-failure (assertion failure) in constant folding. The output_prop tensor has a shape that is controlled by user input and this can result in triggering one of the CHECKs in the PartialTensorShape constructor. This is an instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71510", "id": "pyup.io-71768", "more_info_path": "/vulnerabilities/PVE-2024-71510/71768", "specs": [ "<2.5.3", ">=2.6.0rc0,<2.6.3", ">=2.7.0rc0,<2.7.1", ">=2.8.0rc0,<2.8.0" ], "v": "<2.5.3,>=2.6.0rc0,<2.6.3,>=2.7.0rc0,<2.7.1,>=2.8.0rc0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27778.", "cve": "CVE-2022-27778", "id": "pyup.io-57663", "more_info_path": "/vulnerabilities/CVE-2022-27778/57663", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27775.", "cve": "CVE-2022-27775", "id": "pyup.io-57649", "more_info_path": "/vulnerabilities/CVE-2022-27775/57649", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27782.", "cve": "CVE-2022-27782", "id": "pyup.io-57681", "more_info_path": "/vulnerabilities/CVE-2022-27782/57681", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Affected versions of Tensorflow-rocm are vulnerable to Denial of Service in the implementation of depthwise ops via CHECK-failure (assertion failure) caused by overflowing the number of elements in a tensor. This is another instance of TFSA-2021-198 (CVE-2021-41197).", "cve": "PVE-2024-71511", "id": "pyup.io-71769", "more_info_path": "/vulnerabilities/PVE-2024-71511/71769", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-22576.", "cve": "CVE-2022-22576", "id": "pyup.io-57679", "more_info_path": "/vulnerabilities/CVE-2022-22576/57679", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29207: Issues arising from undefined behavior stemming from users supplying invalid resource handles.", "cve": "CVE-2022-29207", "id": "pyup.io-57656", "more_info_path": "/vulnerabilities/CVE-2022-29207/57656", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27780.", "cve": "CVE-2022-27780", "id": "pyup.io-57675", "more_info_path": "/vulnerabilities/CVE-2022-27780/57675", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29204: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29204", "id": "pyup.io-57672", "more_info_path": "/vulnerabilities/CVE-2022-29204/57672", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29196: Missing validation which causes denial of service via 'Conv3DBackpropFilterV2'.", "cve": "CVE-2022-29196", "id": "pyup.io-57655", "more_info_path": "/vulnerabilities/CVE-2022-29196/57655", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29199: Missing validation which causes denial of service via 'LoadAndRemapMatrix'.", "cve": "CVE-2022-29199", "id": "pyup.io-57677", "more_info_path": "/vulnerabilities/CVE-2022-29199/57677", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29212: Core dump when loading TFLite models with quantization.", "cve": "CVE-2022-29212", "id": "pyup.io-57683", "more_info_path": "/vulnerabilities/CVE-2022-29212/57683", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27781.", "cve": "CVE-2022-27781", "id": "pyup.io-57665", "more_info_path": "/vulnerabilities/CVE-2022-27781/57665", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27779.", "cve": "CVE-2022-27779", "id": "pyup.io-57664", "more_info_path": "/vulnerabilities/CVE-2022-27779/57664", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-30115.", "cve": "CVE-2022-30115", "id": "pyup.io-57666", "more_info_path": "/vulnerabilities/CVE-2022-30115/57666", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29216: Code injection in 'saved_model_cli'.", "cve": "CVE-2022-29216", "id": "pyup.io-57650", "more_info_path": "/vulnerabilities/CVE-2022-29216/57650", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27776.", "cve": "CVE-2022-27776", "id": "pyup.io-57652", "more_info_path": "/vulnerabilities/CVE-2022-27776/57652", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29211: Segfault when 'tf.histogram_fixed_width' is called with NaN values.", "cve": "CVE-2022-29211", "id": "pyup.io-57673", "more_info_path": "/vulnerabilities/CVE-2022-29211/57673", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29209: Type confusion leading to 'CHECK'-failure based denial of service.", "cve": "CVE-2022-29209", "id": "pyup.io-57680", "more_info_path": "/vulnerabilities/CVE-2022-29209/57680", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29208: Segfault and OOB write due to incomplete validation in 'EditDistance'.", "cve": "CVE-2022-29208", "id": "pyup.io-57658", "more_info_path": "/vulnerabilities/CVE-2022-29208/57658", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29206: Missing validation which results in undefined behavior in 'SparseTensorDenseAdd'.", "cve": "CVE-2022-29206", "id": "pyup.io-57671", "more_info_path": "/vulnerabilities/CVE-2022-29206/57671", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29205: Segfault due to missing support for quantized types.", "cve": "CVE-2022-29205", "id": "pyup.io-57676", "more_info_path": "/vulnerabilities/CVE-2022-29205/57676", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29203: Integer overflow in 'SpaceToBatchND'.", "cve": "CVE-2022-29203", "id": "pyup.io-57668", "more_info_path": "/vulnerabilities/CVE-2022-29203/57668", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29202: Denial of service in 'tf.ragged.constant' due to lack of validation.", "cve": "CVE-2022-29202", "id": "pyup.io-57669", "more_info_path": "/vulnerabilities/CVE-2022-29202/57669", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29201: Missing validation which results in undefined behavior in 'QuantizedConv2D'.", "cve": "CVE-2022-29201", "id": "pyup.io-57670", "more_info_path": "/vulnerabilities/CVE-2022-29201/57670", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29200: Missing validation which causes denial of service via 'LSTMBlockCell'.", "cve": "CVE-2022-29200", "id": "pyup.io-57653", "more_info_path": "/vulnerabilities/CVE-2022-29200/57653", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29198: Missing validation which causes denial of service via 'SparseTensorToCSRSparseMatrix'.", "cve": "CVE-2022-29198", "id": "pyup.io-57654", "more_info_path": "/vulnerabilities/CVE-2022-29198/57654", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29195: Missing validation which causes denial of service via 'StagePeek'.", "cve": "CVE-2022-29195", "id": "pyup.io-57659", "more_info_path": "/vulnerabilities/CVE-2022-29195/57659", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29193: missing validation which causes 'TensorSummaryV2' to crash.", "cve": "CVE-2022-29193", "id": "pyup.io-57651", "more_info_path": "/vulnerabilities/CVE-2022-29193/57651", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29194: Missing validation which causes denial of service via 'DeleteSessionTensor'.", "cve": "CVE-2022-29194", "id": "pyup.io-57660", "more_info_path": "/vulnerabilities/CVE-2022-29194/57660", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29192: missing validation which crashes 'QuantizeAndDequantizeV4Grad'.", "cve": "CVE-2022-29192", "id": "pyup.io-57674", "more_info_path": "/vulnerabilities/CVE-2022-29192/57674", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29191: Missing validation which causes denial of service via 'GetSessionTensor'.", "cve": "CVE-2022-29191", "id": "pyup.io-57682", "more_info_path": "/vulnerabilities/CVE-2022-29191/57682", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'curl' to v7.83.1 to handle CVE-2022-27774.", "cve": "CVE-2022-27774", "id": "pyup.io-57662", "more_info_path": "/vulnerabilities/CVE-2022-27774/57662", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29197: Missing validation which causes denial of service via 'UnsortedSegmentJoin'.", "cve": "CVE-2022-29197", "id": "pyup.io-57657", "more_info_path": "/vulnerabilities/CVE-2022-29197/57657", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 update 'zlib' to v1.2.12 to handle CVE-2018-25032.", "cve": "CVE-2018-25032", "id": "pyup.io-57667", "more_info_path": "/vulnerabilities/CVE-2018-25032/57667", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow versions 2.6.4, 2.7.2, 2.8.1 and 2.9.0 include a fix for CVE-2022-29213: Crashes stemming from incomplete validation in signal ops.", "cve": "CVE-2022-29213", "id": "pyup.io-57678", "more_info_path": "/vulnerabilities/CVE-2022-29213/57678", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35934: 'CHECK' failure in tf.reshape via overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f4w6-h4f5-wx45", "cve": "CVE-2022-35934", "id": "pyup.io-57602", "more_info_path": "/vulnerabilities/CVE-2022-35934/57602", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35990: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannelGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h7ff-cfc9-wmmh", "cve": "CVE-2022-35990", "id": "pyup.io-57608", "more_info_path": "/vulnerabilities/CVE-2022-35990/57608", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36000: 'CHECK' fail in 'Eig'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fqxc-pvf8-2w9v", "cve": "CVE-2022-36000", "id": "pyup.io-57615", "more_info_path": "/vulnerabilities/CVE-2022-36000/57615", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36027: Segfault TFLite converter on per-channel quantized transposed convolutions.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-79h2-q768-fpxr", "cve": "CVE-2022-36027", "id": "pyup.io-57624", "more_info_path": "/vulnerabilities/CVE-2022-36027/57624", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36015: Integer overflow in math ops. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rh87-q4vg-m45j", "cve": "CVE-2022-36015", "id": "pyup.io-57598", "more_info_path": "/vulnerabilities/CVE-2022-36015/57598", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36014: Null-dereference in 'mlir::tfg::TFOp::nameAttr'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-7j3m-8g3c-9qqq", "cve": "CVE-2022-36014", "id": "pyup.io-57628", "more_info_path": "/vulnerabilities/CVE-2022-36014/57628", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36013: Null-dereference in 'mlir::tfg::GraphDefImporter::ConvertNodeDef'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-828c-5j5q-vrjq", "cve": "CVE-2022-36013", "id": "pyup.io-57613", "more_info_path": "/vulnerabilities/CVE-2022-36013/57613", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36005: 'CHECK' fail in 'FakeQuantWithMinMaxVarsGradient'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r26c-679w-mrjm", "cve": "CVE-2022-36005", "id": "pyup.io-57647", "more_info_path": "/vulnerabilities/CVE-2022-36005/57647", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36003: 'CHECK' fail in 'RandomPoissonV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cv2p-32v3-vhwq", "cve": "CVE-2022-36003", "id": "pyup.io-57599", "more_info_path": "/vulnerabilities/CVE-2022-36003/57599", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36002: 'CHECK' fail in 'Unbatch'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mh3m-62v7-68xg", "cve": "CVE-2022-36002", "id": "pyup.io-57603", "more_info_path": "/vulnerabilities/CVE-2022-36002/57603", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35998: 'CHECK' fail in 'EmptyTensorList'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhw4-wwr7-gjc5", "cve": "CVE-2022-35998", "id": "pyup.io-57612", "more_info_path": "/vulnerabilities/CVE-2022-35998/57612", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35997: 'CHECK' fail in 'tf.sparse.cross'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p7hr-f446-x6qf", "cve": "CVE-2022-35997", "id": "pyup.io-57611", "more_info_path": "/vulnerabilities/CVE-2022-35997/57611", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35995: 'CHECK' fail in 'AudioSummaryV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9h5-vr8m-x2h4", "cve": "CVE-2022-35995", "id": "pyup.io-57642", "more_info_path": "/vulnerabilities/CVE-2022-35995/57642", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35994: 'CHECK' fail in 'CollectiveGather'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fhfc-2q7x-929f", "cve": "CVE-2022-35994", "id": "pyup.io-57637", "more_info_path": "/vulnerabilities/CVE-2022-35994/57637", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35993: 'CHECK' fail in 'SetSize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wq6q-6m32-9rv9", "cve": "CVE-2022-35993", "id": "pyup.io-57627", "more_info_path": "/vulnerabilities/CVE-2022-35993/57627", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35992: 'CHECK' fail in 'TensorListFromTensor'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9v8w-xmr4-wgxp", "cve": "CVE-2022-35992", "id": "pyup.io-57616", "more_info_path": "/vulnerabilities/CVE-2022-35992/57616", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36019: 'CHECK' fail in 'FakeQuantWithMinMaxVarsPerChannel'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9j4v-pp28-mxv7", "cve": "CVE-2022-36019", "id": "pyup.io-57633", "more_info_path": "/vulnerabilities/CVE-2022-36019/57633", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36018: 'CHECK' fail in 'RaggedTensorToVariant'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6cv-4fmf-66xf", "cve": "CVE-2022-36018", "id": "pyup.io-57645", "more_info_path": "/vulnerabilities/CVE-2022-36018/57645", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36012: Assertion fail on MLIR empty edge names.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jvhc-5hhr-w3v5", "cve": "CVE-2022-36012", "id": "pyup.io-57604", "more_info_path": "/vulnerabilities/CVE-2022-36012/57604", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35987: 'CHECK' fail in 'DenseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w62h-8xjm-fv49", "cve": "CVE-2022-35987", "id": "pyup.io-57620", "more_info_path": "/vulnerabilities/CVE-2022-35987/57620", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35986: Segfault in 'RaggedBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wr9v-g9vf-c74v", "cve": "CVE-2022-35986", "id": "pyup.io-57617", "more_info_path": "/vulnerabilities/CVE-2022-35986/57617", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35983: 'CHECK' fail in 'Save' and 'SaveSlices'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-m6vp-8q9j-whx4", "cve": "CVE-2022-35983", "id": "pyup.io-57605", "more_info_path": "/vulnerabilities/CVE-2022-35983/57605", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35982: Segfault in 'SparseBincount'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-397c-5g2j-qxpv", "cve": "CVE-2022-35982", "id": "pyup.io-57625", "more_info_path": "/vulnerabilities/CVE-2022-35982/57625", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35981: 'CHECK' fail in 'FractionalMaxPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vxv8-r8q2-63xw", "cve": "CVE-2022-35981", "id": "pyup.io-57614", "more_info_path": "/vulnerabilities/CVE-2022-35981/57614", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35979: Segfault in 'QuantizedRelu' and 'QuantizedRelu6'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v7vw-577f-vp8x", "cve": "CVE-2022-35979", "id": "pyup.io-57596", "more_info_path": "/vulnerabilities/CVE-2022-35979/57596", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35974: Segfault in 'QuantizeDownAndShrinkRange'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vgvh-2pf4-jr2x", "cve": "CVE-2022-35974", "id": "pyup.io-57618", "more_info_path": "/vulnerabilities/CVE-2022-35974/57618", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35971: 'CHECK' fail in 'FakeQuantWithMinMaxVars'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9fpg-838v-wpv7", "cve": "CVE-2022-35971", "id": "pyup.io-57643", "more_info_path": "/vulnerabilities/CVE-2022-35971/57643", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35969: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q2c3-jpmc-gfjx", "cve": "CVE-2022-35969", "id": "pyup.io-57601", "more_info_path": "/vulnerabilities/CVE-2022-35969/57601", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35968: 'CHECK' fail in 'AvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2475-53vw-vp25", "cve": "CVE-2022-35968", "id": "pyup.io-57635", "more_info_path": "/vulnerabilities/CVE-2022-35968/57635", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35966: Segfault in 'QuantizedAvgPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4w68-4x85-mjj9", "cve": "CVE-2022-35966", "id": "pyup.io-57622", "more_info_path": "/vulnerabilities/CVE-2022-35966/57622", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35965: Segfault in 'LowerBound' and 'UpperBound'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qxpx-j395-pw36", "cve": "CVE-2022-35965", "id": "pyup.io-57632", "more_info_path": "/vulnerabilities/CVE-2022-35965/57632", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35964: Segfault in 'BlockLSTMGradV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f7r5-q7cx-h668", "cve": "CVE-2022-35964", "id": "pyup.io-57610", "more_info_path": "/vulnerabilities/CVE-2022-35964/57610", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35963: 'CHECK' failures in 'FractionalAvgPoolGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-84jm-4cf3-9jfm", "cve": "CVE-2022-35963", "id": "pyup.io-57640", "more_info_path": "/vulnerabilities/CVE-2022-35963/57640", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35960: 'CHECK' failure in 'TensorListReserve' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v5xg-3q2c-c2r4", "cve": "CVE-2022-35960", "id": "pyup.io-57595", "more_info_path": "/vulnerabilities/CVE-2022-35960/57595", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35959: 'CHECK' failures in 'AvgPool3DGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wxjj-cgcx-r3vq", "cve": "CVE-2022-35959", "id": "pyup.io-57609", "more_info_path": "/vulnerabilities/CVE-2022-35959/57609", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35952: 'CHECK' failures in 'UnbatchGradOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h5vq-gw2c-pq47", "cve": "CVE-2022-35952", "id": "pyup.io-57594", "more_info_path": "/vulnerabilities/CVE-2022-35952/57594", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35941: 'CHECK' failure in 'AvgPoolOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mgmh-g2v6-mqw5", "cve": "CVE-2022-35941", "id": "pyup.io-57629", "more_info_path": "/vulnerabilities/CVE-2022-35941/57629", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35940: Int overflow in 'RaggedRangeOp'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x989-q2pq-4q5x", "cve": "CVE-2022-35940", "id": "pyup.io-57638", "more_info_path": "/vulnerabilities/CVE-2022-35940/57638", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35937: OOB read in 'Gather_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pxrw-j2fv-hx3h", "cve": "CVE-2022-35937", "id": "pyup.io-57592", "more_info_path": "/vulnerabilities/CVE-2022-35937/57592", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35996: Floating point exception in 'Conv2D'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q5jv-m6qw-5g37", "cve": "CVE-2022-35996", "id": "pyup.io-57607", "more_info_path": "/vulnerabilities/CVE-2022-35996/57607", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36001: 'CHECK' fail in 'DrawBoundingBoxes'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jqm7-m5q7-3hm5", "cve": "CVE-2022-36001", "id": "pyup.io-57639", "more_info_path": "/vulnerabilities/CVE-2022-36001/57639", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36011: Null dereference on MLIR on empty function attributes.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-fv43-93gv-vm8f", "cve": "CVE-2022-36011", "id": "pyup.io-57623", "more_info_path": "/vulnerabilities/CVE-2022-36011/57623", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35989: 'CHECK' fail in 'MaxPool'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-j43h-pgmg-5hjq", "cve": "CVE-2022-35989", "id": "pyup.io-57646", "more_info_path": "/vulnerabilities/CVE-2022-35989/57646", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36016: 'CHECK'-fail in 'tensorflow::full_type::SubstituteFromAttrs'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g468-qj8g-vcjc", "cve": "CVE-2022-36016", "id": "pyup.io-57630", "more_info_path": "/vulnerabilities/CVE-2022-36016/57630", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35939: OOB write in 'scatter_nd' op in TF Lite.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-ffjm-4qwc-7cmf", "cve": "CVE-2022-35939", "id": "pyup.io-57593", "more_info_path": "/vulnerabilities/CVE-2022-35939/57593", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36017: Segfault in 'Requantize'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-wqmc-pm8c-2jhc", "cve": "CVE-2022-36017", "id": "pyup.io-57597", "more_info_path": "/vulnerabilities/CVE-2022-36017/57597", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35985: 'CHECK' fail in 'LRNGrad'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9942-r22v-78cp", "cve": "CVE-2022-35985", "id": "pyup.io-57600", "more_info_path": "/vulnerabilities/CVE-2022-35985/57600", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35984: 'CHECK' fail in 'ParameterizedTruncatedNormal'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2xf-8hgm-hpw5", "cve": "CVE-2022-35984", "id": "pyup.io-57606", "more_info_path": "/vulnerabilities/CVE-2022-35984/57606", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35988: 'CHECK' fail in 'tf.linalg.matrix_rank'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vqj-64pv-w55c", "cve": "CVE-2022-35988", "id": "pyup.io-57631", "more_info_path": "/vulnerabilities/CVE-2022-35988/57631", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35999: 'CHECK' fail in 'Conv2DBackpropInput'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-37jf-mjv6-xfqw", "cve": "CVE-2022-35999", "id": "pyup.io-57641", "more_info_path": "/vulnerabilities/CVE-2022-35999/57641", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36026: 'CHECK' fail in 'QuantizeAndDequantizeV3'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9cr2-8pwr-fhfq", "cve": "CVE-2022-36026", "id": "pyup.io-57621", "more_info_path": "/vulnerabilities/CVE-2022-36026/57621", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35973: Segfault in 'QuantizedMatMul'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-689c-r7h2-fv9v", "cve": "CVE-2022-35973", "id": "pyup.io-57619", "more_info_path": "/vulnerabilities/CVE-2022-35973/57619", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35970: Segfault in 'QuantizedInstanceNorm'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g35r-369w-3fqp", "cve": "CVE-2022-35970", "id": "pyup.io-57636", "more_info_path": "/vulnerabilities/CVE-2022-35970/57636", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35967: Segfault in 'QuantizedAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v6h3-348g-6h5x", "cve": "CVE-2022-35967", "id": "pyup.io-57634", "more_info_path": "/vulnerabilities/CVE-2022-35967/57634", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-36004: 'CHECK' fail in 'tf.random.gamma'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv8m-8x97-937q", "cve": "CVE-2022-36004", "id": "pyup.io-57644", "more_info_path": "/vulnerabilities/CVE-2022-36004/57644", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.7.4, 2.8.3 and 2.9.2 include a fix for CVE-2022-35972: Segfault in 'QuantizedBiasAdd'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4pc4-m9mj-v2r9", "cve": "CVE-2022-35972", "id": "pyup.io-57626", "more_info_path": "/vulnerabilities/CVE-2022-35972/57626", "specs": [ "<2.7.4", ">=2.8.0rc0,<2.8.3", ">=2.9.0rc0,<2.9.2" ], "v": "<2.7.4,>=2.8.0rc0,<2.8.3,>=2.9.0rc0,<2.9.2" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41889: If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a 'nullptr', which is not caught. An example can be seen in 'tf.compat.v1.extract_volume_patches' by passing in quantized tensors as input 'ksizes'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xxcj-rhqg-m46g", "cve": "CVE-2022-41889", "id": "pyup.io-57571", "more_info_path": "/vulnerabilities/CVE-2022-41889/57571", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41907: When 'tf.raw_ops.ResizeNearestNeighborGrad' is given a large 'size' input, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-368v-7v32-52fx", "cve": "CVE-2022-41907", "id": "pyup.io-57580", "more_info_path": "/vulnerabilities/CVE-2022-41907/57580", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41900: The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xvwp-h6jv-7472", "cve": "CVE-2022-41900", "id": "pyup.io-57577", "more_info_path": "/vulnerabilities/CVE-2022-41900/57577", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41899: TensorFlow is an open source platform for machine learning. Inputs 'dense_features' or 'example_state_data' not of rank 2 will trigger a 'CHECK' fail in 'SdcaOptimizer'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-27rc-728f-x5w2", "cve": "CVE-2022-41899", "id": "pyup.io-57573", "more_info_path": "/vulnerabilities/CVE-2022-41899/57573", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41898: If 'SparseFillEmptyRowsGrad' is given empty inputs, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hq7g-wwwp-q46h", "cve": "CVE-2022-41898", "id": "pyup.io-57588", "more_info_path": "/vulnerabilities/CVE-2022-41898/57588", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41897: If 'FractionMaxPoolGrad' is given outsize inputs 'row_pooling_sequence' and 'col_pooling_sequence', TensorFlow will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2w8-jw48-fr7j", "cve": "CVE-2022-41897", "id": "pyup.io-57584", "more_info_path": "/vulnerabilities/CVE-2022-41897/57584", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41895: If 'MirrorPadGrad' is given outsize input 'paddings', TensorFlow will give a heap OOB error.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gq2j-cr96-gvqx", "cve": "CVE-2022-41895", "id": "pyup.io-57568", "more_info_path": "/vulnerabilities/CVE-2022-41895/57568", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41888: When running on GPU, 'tf.image.generate_bounding_box_proposals' receives a 'scores' input that must be of rank 4 but is not checked.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-6x99-gv2v-q76v", "cve": "CVE-2022-41888", "id": "pyup.io-57587", "more_info_path": "/vulnerabilities/CVE-2022-41888/57587", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41886: When 'tf.raw_ops.ImageProjectiveTransformV2' is given a large output shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-54pp-c6pp-7fpx", "cve": "CVE-2022-41886", "id": "pyup.io-57585", "more_info_path": "/vulnerabilities/CVE-2022-41886/57585", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41885: When 'tf.raw_ops.FusedResizeAndPadConv2D' is given a large tensor shape, it overflows.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-762h-vpvw-3rcx", "cve": "CVE-2022-41885", "id": "pyup.io-57572", "more_info_path": "/vulnerabilities/CVE-2022-41885/57572", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41884: If a numpy array is created with a shape such that one element is zero and the others sum to a large number, an error will be raised. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jq6x-99hj-q636", "cve": "CVE-2022-41884", "id": "pyup.io-57583", "more_info_path": "/vulnerabilities/CVE-2022-41884/57583", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1.", "cve": "CVE-2022-41902", "id": "pyup.io-57581", "more_info_path": "/vulnerabilities/CVE-2022-41902/57581", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41910: The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-frqp-wp83-qggv", "cve": "CVE-2022-41910", "id": "pyup.io-57586", "more_info_path": "/vulnerabilities/CVE-2022-41910/57586", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41911: When printing a tensor, we get it's data as a 'const char*' array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from 'char' to 'bool' are undefined if the 'char' is not '0' or '1', so sanitizers/fuzzers will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j", "cve": "CVE-2022-41911", "id": "pyup.io-57570", "more_info_path": "/vulnerabilities/CVE-2022-41911/57570", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41880: When the 'BaseCandidateSamplerOp' function receives a value in 'true_classes' larger than 'range_max', a heap oob read occurs.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8w5g-3wcv-9g2j", "cve": "CVE-2022-41880", "id": "pyup.io-57579", "more_info_path": "/vulnerabilities/CVE-2022-41880/57579", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41894: The reference kernel of the 'CONV_3D_TRANSPOSE' TensorFlow Lite operator wrongly increments the data_ptr when adding the bias to the result. Instead of 'data_ptr += num_channels;' it should be 'data_ptr += output_num_channels;' as if the number of input channels is different than the number of output channels, the wrong result will be returned and a buffer overflow will occur if num_channels > output_num_channels. An attacker can craft a model with a specific number of input channels. It is then possible to write specific values through the bias of the layer outside the bounds of the buffer. This attack only works if the reference kernel resolver is used in the interpreter.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6q3-vv32-2cq5", "cve": "CVE-2022-41894", "id": "pyup.io-57589", "more_info_path": "/vulnerabilities/CVE-2022-41894/57589", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41908: TensorFlow is an open source platform for machine learning. An input 'token' that is not a UTF-8 bytestring will trigger a 'CHECK' fail in 'tf.raw_ops.PyFunc'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv77-9g28-cwg3", "cve": "CVE-2022-41908", "id": "pyup.io-57576", "more_info_path": "/vulnerabilities/CVE-2022-41908/57576", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41890: If 'BCast::ToShape' is given input larger than an 'int32', it will crash, despite being supposed to handle up to an 'int64'. An example can be seen in 'tf.experimental.numpy.outer' by passing in large input to the input 'b'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h246-cgh4-7475", "cve": "CVE-2022-41890", "id": "pyup.io-57578", "more_info_path": "/vulnerabilities/CVE-2022-41890/57578", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41893: If 'tf.raw_ops.TensorListResize' is given a nonscalar value for input 'size', it results 'CHECK' fail which can be used to trigger a denial of service attack.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-67pf-62xr-q35m", "cve": "CVE-2022-41893", "id": "pyup.io-57574", "more_info_path": "/vulnerabilities/CVE-2022-41893/57574", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41896: If 'ThreadUnsafeUnigramCandidateSampler' is given input 'filterbank_channel_count' greater than the allowed max size, TensorFlow will crash.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rmg2-f698-wq35", "cve": "CVE-2022-41896", "id": "pyup.io-57582", "more_info_path": "/vulnerabilities/CVE-2022-41896/57582", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41901: An input 'sparse_matrix' that is not a matrix with a shape with rank 0 will trigger a 'CHECK' fail in 'tf.raw_ops.SparseMatrixNNZ'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g9fm-r5mm-rf9f", "cve": "CVE-2022-41901", "id": "pyup.io-57567", "more_info_path": "/vulnerabilities/CVE-2022-41901/57567", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41909: An input 'encoded' that is not a valid 'CompositeTensorVariant' tensor will trigger a segfault in 'tf.raw_ops.CompositeTensorVariantToComponents'.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjx6-v474-2ch9", "cve": "CVE-2022-41909", "id": "pyup.io-57575", "more_info_path": "/vulnerabilities/CVE-2022-41909/57575", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow 2.8.4, 2.9.3 and 2.10.1 include a fix for CVE-2022-41891: If 'tf.raw_ops.TensorListConcat' is given 'element_shape=[]', it results segmentation fault which can be used to trigger a denial of service attack.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-66vq-54fq-6jvv", "cve": "CVE-2022-41891", "id": "pyup.io-57569", "more_info_path": "/vulnerabilities/CVE-2022-41891/57569", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35991: 'CHECK' fail in 'TensorListScatter' and 'TensorListScatterV2'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vm7x-4qhj-rrcq\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xf83-q765-xm6m", "cve": "CVE-2022-35991", "id": "pyup.io-57591", "more_info_path": "/vulnerabilities/CVE-2022-35991/57591", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-rocm 2.8.4, 2.9.3, 2.10.1 and 2.11.0 include a fix for CVE-2022-35935: 'CHECK' failure in 'SobolSample' via missing validation.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-97p7-w86h-vcf9\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqvq-fvhr-v6hc", "cve": "CVE-2022-35935", "id": "pyup.io-57590", "more_info_path": "/vulnerabilities/CVE-2022-35935/57590", "specs": [ "<2.8.4", ">=2.9.0rc0,<2.9.3", ">=2.10.0rc0,<2.10.1", ">=2.11.0rc0,<2.11.0" ], "v": "<2.8.4,>=2.9.0rc0,<2.9.3,>=2.10.0rc0,<2.10.1,>=2.11.0rc0,<2.11.0" }, { "advisory": "Tensorflow-rocm 2.9.3 and 2.10.1 include a fix for CVE-2022-41887: 'tf.keras.losses.poisson' receives a 'y_pred' and 'y_true' that are passed through 'functor::mul' in 'BinaryOp'. If the resulting dimensions overflow an 'int32', TensorFlow will crash due to a size mismatch during broadcast assignment.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fvv-46hw-vpg3", "cve": "CVE-2022-41887", "id": "pyup.io-57566", "more_info_path": "/vulnerabilities/CVE-2022-41887/57566", "specs": [ "<2.9.3", ">=2.10.0rc0,<2.10.1" ], "v": "<2.9.3,>=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm includes a vulnerable dependency, `curl` version 8.2.1, which is affected by CVE-2023-38545.", "cve": "CVE-2023-38545", "id": "pyup.io-72951", "more_info_path": "/vulnerabilities/CVE-2023-38545/72951", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Tensorflow-rocm includes a vulnerable dependency, `curl` version 8.2.1, which is affected by CVE-2023-38546.", "cve": "CVE-2023-38546", "id": "pyup.io-72949", "more_info_path": "/vulnerabilities/CVE-2023-38546/72949", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Tensorflow-rocm versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 updates its dependency \"SQLite\" to handle CVE-2020-15358.", "cve": "CVE-2020-15358", "id": "pyup.io-57989", "more_info_path": "/vulnerabilities/CVE-2020-15358/57989", "specs": [ ">=1.15.0rc0,<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=1.15.0rc0,<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 1.15.2 and 2.0.1 update its dependency \"SQLite\" to handle CVE-2019-19646.", "cve": "CVE-2019-19646", "id": "pyup.io-58015", "more_info_path": "/vulnerabilities/CVE-2019-19646/58015", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-rocm versions 1.15.2 and 2.0.1 updates its dependency \"curl\" to handle CVE-2019-5482.", "cve": "CVE-2019-5482", "id": "pyup.io-58014", "more_info_path": "/vulnerabilities/CVE-2019-5482/58014", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-rocm versions 1.15.2 and 2.0.1 updates 'sqlite3' to handle CVE-2019-16168.", "cve": "CVE-2019-16168", "id": "pyup.io-58013", "more_info_path": "/vulnerabilities/CVE-2019-16168/58013", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-rocm versions 1.15.2 and 2.0.1 updates its dependency \"curl\" to handle CVE-2019-5481.", "cve": "CVE-2019-5481", "id": "pyup.io-58012", "more_info_path": "/vulnerabilities/CVE-2019-5481/58012", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-rocm versions 1.15.2 and 2.0.1 includes a fix for CVE-2020-5215: In TensorFlow before 1.15.2 and 2.0.1, converting a string (from Python) to a tf.float16 value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode. This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a tf.float16 value. Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar tf.float16 value with a scalar string will trigger this issue due to automatic conversions. This can be easily reproduced by tf.constant(\"hello\", tf.float16), if eager execution is enabled.", "cve": "CVE-2020-5215", "id": "pyup.io-58016", "more_info_path": "/vulnerabilities/CVE-2020-5215/58016", "specs": [ ">=2.0.0a0,<2.0.1", "<1.15.2" ], "v": ">=2.0.0a0,<2.0.1,<1.15.2" }, { "advisory": "Tensorflow-rocm versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 include a fix for CVE-2021-29567: Due to lack of validation in 'tf.raw_ops.SparseDenseCwiseMul', an attacker can trigger denial of service via 'CHECK'-fails or accesses to outside the bounds of heap allocated data. Since the implementation (https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80), it only validates the rank of the input arguments but no constraints between dimensions (https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul) and an attacker can abuse them to trigger internal 'CHECK' assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers.", "cve": "CVE-2021-29567", "id": "pyup.io-58002", "more_info_path": "/vulnerabilities/CVE-2021-29567/58002", "specs": [ ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.5.0rc0,<2.5.0" ], "v": ">=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.5.0rc0,<2.5.0" }, { "advisory": "Tensorflow-rocm 2.10.1 includes a fix for CVE-2022-41883: When ops that have specified input sizes receive a differing number of inputs, the executor will crash.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj", "cve": "CVE-2022-41883", "id": "pyup.io-57565", "more_info_path": "/vulnerabilities/CVE-2022-41883/57565", "specs": [ ">=2.10.0rc0,<2.10.1" ], "v": ">=2.10.0rc0,<2.10.1" }, { "advisory": "Tensorflow-rocm versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15193: In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of \"dlpack.to_dlpack\" can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing in a Python object instead of a tensor. The uninitialized memory address is due to a \"reinterpret_cast\". Since the \"PyObject\" is a Python object, not a Tensorflow tensor, the cast to \"EagerTensor\" fails. The issue was patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v", "cve": "CVE-2020-15193", "id": "pyup.io-58001", "more_info_path": "/vulnerabilities/CVE-2020-15193/58001", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15213: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimension of the output tensor, attackers can use a very large value to trigger a large allocation. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps. However, if the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hjmq-236j-8m87", "cve": "CVE-2020-15213", "id": "pyup.io-57997", "more_info_path": "/vulnerabilities/CVE-2020-15213/57997", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15212: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to \"segment_ids_data\" can alter \"output_index\" and then write to outside of \"output_data\" buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15212", "id": "pyup.io-57998", "more_info_path": "/vulnerabilities/CVE-2020-15212/57998", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15192: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to 'dlpack.to_dlpack' there is a memory leak following an expected validation failure. The issue occurs because the 'status' argument during validation failures is not properly checked. Since each of the above methods can return an error status, the 'status' value must be checked before continuing.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fxw-76px-3rxv", "cve": "CVE-2020-15192", "id": "pyup.io-58000", "more_info_path": "/vulnerabilities/CVE-2020-15192/58000", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15191: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to 'dlpack.to_dlpack' the expected validations will cause variables to bind to 'nullptr' while setting a 'status' variable to the error condition. However, this 'status' argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with '-fsanitize=null'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr", "cve": "CVE-2020-15191", "id": "pyup.io-57996", "more_info_path": "/vulnerabilities/CVE-2020-15191/57996", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15214: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimension of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15214", "id": "pyup.io-57999", "more_info_path": "/vulnerabilities/CVE-2020-15214/57999", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm 2.3.1 includes a fix for CVE-2020-15201: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Hence, the code is prone to heap buffer overflow. If \"split_values\" does not end with a value at least \"num_values\" then the \"while\" loop condition will trigger a read outside of the bounds of \"split_values\" once \"batch_idx\" grows too large. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4", "cve": "CVE-2020-15201", "id": "pyup.io-57995", "more_info_path": "/vulnerabilities/CVE-2020-15201/57995", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm 2.3.1 includes a fix for CVE-2020-15200: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Thus, the code sets up conditions to cause a heap buffer overflow. A \"BatchedMap\" is equivalent to a vector where each element is a hashmap. However, if the first element of \"splits_values\" is not 0, \"batch_idx\" will never be 1, hence there will be no hashmap at index 0 in \"per_batch_counts\". Trying to access that in the user code results in a segmentation fault. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x7rp-74x2-mjf3", "cve": "CVE-2020-15200", "id": "pyup.io-57993", "more_info_path": "/vulnerabilities/CVE-2020-15200/57993", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm 2.3.1 includes a fix for CVE-2020-15199: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the \"splits\" tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure. Since \"BatchedMap\" is equivalent to a vector, it needs to have at least one element to not be \"nullptr\". If user passes a \"splits\" tensor that is empty or has exactly one element, we get a \"SIGABRT\" signal raised by the operating system. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x5cp-9pcf-pp3h", "cve": "CVE-2020-15199", "id": "pyup.io-57994", "more_info_path": "/vulnerabilities/CVE-2020-15199/57994", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm 2.3.1 includes a fix for CVE-2020-15198: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has the same shape as the \"values\" one. The values in these tensors are always accessed in parallel. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3", "cve": "CVE-2020-15198", "id": "pyup.io-57991", "more_info_path": "/vulnerabilities/CVE-2020-15198/57991", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm version 2.3.1 includes a fix for CVE-2020-15197: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix. However, malicious users can pass in tensors of different rank, resulting in a \"CHECK\" assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.", "cve": "CVE-2020-15197", "id": "pyup.io-57990", "more_info_path": "/vulnerabilities/CVE-2020-15197/57990", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm version 2.3.1 includes a fix for CVE-2020-15196: In Tensorflow version 2.3.0, the \"SparseCountSparseOutput\" and \"RaggedCountSparseOutput\" implementations don't validate that the \"weights\" tensor has the same shape as the data. The check exists for \"DenseCountSparseOutput\", where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph", "cve": "CVE-2020-15196", "id": "pyup.io-57992", "more_info_path": "/vulnerabilities/CVE-2020-15196/57992", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37689: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. This is caused by the MLIR optimization of 'L2NormalizeReduceAxis' operator. The implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/compiler/mlir/lite/transforms/optimize.cc#L67-L70) unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements. The Tensorflow team has patched the issue in GitHub commit d6b57f461b39fd1aa8c1b870f1b974aac3554955.", "cve": "CVE-2021-37689", "id": "pyup.io-57945", "more_info_path": "/vulnerabilities/CVE-2021-37689/57945", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37671: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.Map*' and 'tf.raw_ops.OrderedMap*' operations. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that 'indices' is in ascending order, but does not check that 'indices' is not empty. The Tensorflow team has patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac.", "cve": "CVE-2021-37671", "id": "pyup.io-57944", "more_info_path": "/vulnerabilities/CVE-2021-37671/57944", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37637: It is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid. The Tensorflow team has patched the issue in GitHub commit 5dc7f6981fdaf74c8c5be41f393df705841fb7c5.", "cve": "CVE-2021-37637", "id": "pyup.io-57950", "more_info_path": "/vulnerabilities/CVE-2021-37637/57950", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37635: In affected versions the implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data. The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor. The Tensorflow team has patched the issue in GitHub commit 87158f43f05f2720a374f3e6d22a7aaa3a33f750.", "cve": "CVE-2021-37635", "id": "pyup.io-57947", "more_info_path": "/vulnerabilities/CVE-2021-37635/57947", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37683: In affected versions the implementation of division in TFLite is vulnerable to a division by 0 error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc). There is no check that the divisor tensor does not contain zero elements. The Tensorflow team has patched the issue in GitHub commit 1e206baedf8bef0334cca3eb92bab134ef525a28.", "cve": "CVE-2021-37683", "id": "pyup.io-57949", "more_info_path": "/vulnerabilities/CVE-2021-37683/57949", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37680: In affected versions the implementation of fully connected layers in TFLite is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226). The Tensorflow team has patched the issue in GitHub commit 718721986aa137691ee23f03638867151f74935f.", "cve": "CVE-2021-37680", "id": "pyup.io-57951", "more_info_path": "/vulnerabilities/CVE-2021-37680/57951", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37667: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.UnicodeEncode'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the 'input_splits' tensor before validating that this tensor is not empty. The Tensorflow team has patched the issue in GitHub commit 2e0ee46f1a47675152d3d865797a18358881d7a6.", "cve": "CVE-2021-37667", "id": "pyup.io-57948", "more_info_path": "/vulnerabilities/CVE-2021-37667/57948", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37642: In affected versions the implementation of 'tf.raw_ops.ResourceScatterDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit 4aacb30888638da75023e6601149415b39763d76.", "cve": "CVE-2021-37642", "id": "pyup.io-57953", "more_info_path": "/vulnerabilities/CVE-2021-37642/57953", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37636: In affected versions the implementation of 'tf.raw_ops.SparseDenseCwiseDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L56) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit d9204be9f49520cdaaeb2541d1dc5187b23f31d9.", "cve": "CVE-2021-37636", "id": "pyup.io-57952", "more_info_path": "/vulnerabilities/CVE-2021-37636/57952", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37648: In affected versions the code for 'tf.raw_ops.SaveV2' does not properly validate the inputs and an attacker can trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses 'ValidateInputs' to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above. However, the validation uses 'OP_REQUIRES' which translates to setting the 'Status' object of the current 'OpKernelContext' to an error status, followed by an empty 'return' statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the nQext line in 'Compute' that follows the call to 'ValidateInputs'. This is equivalent to lacking the validation. The Tensorflow team has patched the issue in GitHub commit 9728c60e136912a12d99ca56e106b7cce7af5986.", "cve": "CVE-2021-37648", "id": "pyup.io-57946", "more_info_path": "/vulnerabilities/CVE-2021-37648/57946", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37649: The code for 'tf.raw_ops.UncompressElement' can be made to trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a 'CompressedElement' from a 'Variant' tensor and then proceeds to dereference it for decompressing. There is no check that the 'Variant' tensor contained a 'CompressedElement', so the pointer is actually 'nullptr'. The Tensorflow team has patched the issue in GitHub commit 7bdf50bb4f5c54a4997c379092888546c97c3ebd.", "cve": "CVE-2021-37649", "id": "pyup.io-57940", "more_info_path": "/vulnerabilities/CVE-2021-37649/57940", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37658: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixSetDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit ff8894044dfae5568ecbf2ed514c1a37dc394f1b.", "cve": "CVE-2021-37658", "id": "pyup.io-57939", "more_info_path": "/vulnerabilities/CVE-2021-37658/57939", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37638: Sending invalid argument for 'row_partition_types' of 'tf.raw_ops.RaggedTensorToTensor' API results in a null pointer dereference and undefined behavior. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty. The Tensorflow team has patched the issue in GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314.", "cve": "CVE-2021-37638", "id": "pyup.io-57934", "more_info_path": "/vulnerabilities/CVE-2021-37638/57934", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37654: In affected versions an attacker can trigger a crash via a 'CHECK'-fail in debug builds of TensorFlow using 'tf.raw_ops.ResourceGather' or a read from outside the bounds of heap allocated data in the same API in a release build. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the 'batch_dims' value that the user supplies is less than the rank of the input tensor. Since the implementation uses several for loops over the dimensions of 'tensor', this results in reading data from outside the bounds of heap allocated buffer backing the tensor. The Tensorflow team has patched the issue in GitHub commit bc9c546ce7015c57c2f15c168b3d9201de679a1d.", "cve": "CVE-2021-37654", "id": "pyup.io-57935", "more_info_path": "/vulnerabilities/CVE-2021-37654/57935", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37647: When a user does not supply arguments that determine a valid sparse tensor, 'tf.raw_ops.SparseTensorSliceDataset' implementation can be made to dereference a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either 'indices' or 'values' are provided for an empty sparse tensor when the other is not. If 'indices' is empty, then code that performs validation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference. If 'indices' as provided by the user is empty, then 'indices' in the C++ code above is backed by an empty 'std::vector', hence calling 'indices->dim_size(0)' results in null pointer dereferencing (same as calling 'std::vector::at()' on an empty vector). The Tensorflow team has patched the issue in GitHub commit 02cc160e29d20631de3859c6653184e3f876b9d7.", "cve": "CVE-2021-37647", "id": "pyup.io-57943", "more_info_path": "/vulnerabilities/CVE-2021-37647/57943", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37652: In affected versions the implementation for 'tf.raw_ops.BoostedTreesCreateEnsemble' can result in a use after free error if an attacker supplies specially crafted arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent 'free'-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed. The Tensorflow team has patched the issue in GitHub commit 5ecec9c6fbdbc6be03295685190a45e7eee726ab.", "cve": "CVE-2021-37652", "id": "pyup.io-57933", "more_info_path": "/vulnerabilities/CVE-2021-37652/57933", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37664: In affected versions an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range. The Tensorflow team has patched the issue in GitHub commit e84c975313e8e8e38bb2ea118196369c45c51378.", "cve": "CVE-2021-37664", "id": "pyup.io-57942", "more_info_path": "/vulnerabilities/CVE-2021-37664/57942", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37659: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations). The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr. We have patched the issue in GitHub commit 93f428fd1768df147171ed674fee1fc5ab8309ec.", "cve": "CVE-2021-37659", "id": "pyup.io-57941", "more_info_path": "/vulnerabilities/CVE-2021-37659/57941", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37651: In affected versions the implementation for 'tf.raw_ops.FractionalAvgPoolGrad' can be tricked into accessing data outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty 'EigenDoubleMatrixMap' and then accesses this buffer with indices that are outside of the empty area. The Tensorflow team has patched the issue in GitHub commit 0f931751fb20f565c4e94aa6df58d54a003cdb30.", "cve": "CVE-2021-37651", "id": "pyup.io-57936", "more_info_path": "/vulnerabilities/CVE-2021-37651/57936", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37639: When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the 'tensor_name' user controlled input and immediately retrieves the tensor at the restoration index (controlled via 'preferred_shard' argument). This occurs without validating that the provided list has enough values. If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements and if the restoration index is outside the bounds, this results in heap OOB read. The Tensorflow team has patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622.", "cve": "CVE-2021-37639", "id": "pyup.io-57938", "more_info_path": "/vulnerabilities/CVE-2021-37639/57938", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37656: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToSparse'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order. The Tensorflow team has patched the issue in GitHub commit 1071f554dbd09f7e101324d366eec5f4fe5a3ece.", "cve": "CVE-2021-37656", "id": "pyup.io-57937", "more_info_path": "/vulnerabilities/CVE-2021-37656/57937", "specs": [ ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Several versions of Tensorflow-rocm are affected by CVE-2021-37686: In affected versions, the strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for ellipsis in axis definition (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122). An attacker can craft a model such that 'ellipsis_end_idx' is smaller than 'i' (e.g., always negative). In this case, the inner loop does not increase 'i' and the 'continue' statement causes execution to skip over the preincrement at the end of the outer loop. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695.", "cve": "CVE-2021-37686", "id": "pyup.io-57932", "more_info_path": "/vulnerabilities/CVE-2021-37686/57932", "specs": [ ">=2.3.0rc0,<2.3.4rc0", ">=2.4.0rc0,<2.4.3rc0", ">=2.5.0rc0,<=2.5.0", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.3.0rc0,<2.3.4rc0,>=2.4.0rc0,<2.4.3rc0,>=2.5.0rc0,<=2.5.0,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.4.0 includes a fix for CVE-2020-26269: In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.", "cve": "CVE-2020-26269", "id": "pyup.io-57965", "more_info_path": "/vulnerabilities/CVE-2020-26269/57965", "specs": [ ">=2.4.0rc0,<2.4.0" ], "v": ">=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm 2.5.0, 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29614: The implementation of 'tf.io.decode_raw' produces incorrect results and crashes the Python interpreter when combining 'fixed_length' and wider datatypes. The implementation of the padded version (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc) is buggy due to a confusion about pointer arithmetic rules. First, the code computes (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L61) the width of each output element by dividing the 'fixed_length' value to the size of the type argument. The 'fixed_length' argument is also used to determine the size needed for the output tensor (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L63-L79). This is followed by reencoding code (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L85-L94). The erroneous code is the last line above: it is moving the 'out_data' pointer by 'fixed_length * sizeof (T)' bytes whereas it only copied at most 'fixed_length' bytes from the input. This results in parts of the input not being decoded into the output. Furthermore, because the pointer advance is far wider than desired, this quickly leads to writing to outside the bounds of the backing data. This OOB write leads to interpreter crash in the reproducer mentioned here, but more severe attacks can be mounted too, given that this gadget allows writing to periodically placed locations in memory.", "cve": "CVE-2021-29614", "id": "pyup.io-57931", "more_info_path": "/vulnerabilities/CVE-2021-29614/57931", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.5.0rc0,<2.5.0" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.5.0rc0,<2.5.0" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a stack overflow in 'ParseAttrValue' with nested tensors. See CVE-2021-29615.", "cve": "CVE-2021-29615", "id": "pyup.io-57929", "more_info_path": "/vulnerabilities/CVE-2021-29615/57929", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv2DBackpropFilter'. See CVE-2021-29524.", "cve": "CVE-2021-29524", "id": "pyup.io-57914", "more_info_path": "/vulnerabilities/CVE-2021-29524/57914", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29552: An attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar. Since the tensor is empty the `CHECK` involved in `.scalar()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination.", "cve": "CVE-2021-29552", "id": "pyup.io-57918", "more_info_path": "/vulnerabilities/CVE-2021-29552/57918", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.5.0, 2.4.2, 2.3.3, 2.2.3 and 2.1.4 include a fix for CVE-2021-29548: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the op's contract (https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization).", "cve": "CVE-2021-29548", "id": "pyup.io-57919", "more_info_path": "/vulnerabilities/CVE-2021-29548/57919", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 includes a fix for CVE-2021-29533: An attacker can trigger a denial of service via a 'CHECK' failure by passing an empty image to 'tf.raw_ops.DrawBoundingBoxes'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/ea34a18dc3f5c8d80a40ccca1404f343b5d55f91/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L148-L165) uses 'CHECK_*' assertions instead of 'OP_REQUIRES' to validate user controlled inputs. Whereas 'OP_REQUIRES' allows returning an error condition back to the user, the 'CHECK_*' macros result in a crash if the condition is false, similar to 'assert'. In this case, 'height' is 0 from the 'images' input. This results in 'max_box_row_clamp' being negative and the assertion being falsified, followed by aborting program execution.", "cve": "CVE-2021-29533", "id": "pyup.io-57920", "more_info_path": "/vulnerabilities/CVE-2021-29533/57920", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'tf.raw_ops.EncodePng'. See CVE-2021-29531.", "cve": "CVE-2021-29531", "id": "pyup.io-57924", "more_info_path": "/vulnerabilities/CVE-2021-29531/57924", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix fixes a heap buffer overflow caused by rounding. See CVE-2021-29529.", "cve": "CVE-2021-29529", "id": "pyup.io-57917", "more_info_path": "/vulnerabilities/CVE-2021-29529/57917", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29537: An attacker can cause a heap buffer overflow in `QuantizedResizeBilinear` by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/50711818d2e61ccce012591eeb4fdf93a8496726/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L705-L706) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly.", "cve": "CVE-2021-29537", "id": "pyup.io-57928", "more_info_path": "/vulnerabilities/CVE-2021-29537/57928", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a 'CHECK'-fail in 'SparseCross' caused by type confusion. See CVE-2021-29519.", "cve": "CVE-2021-29519", "id": "pyup.io-57911", "more_info_path": "/vulnerabilities/CVE-2021-29519/57911", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv3DBackprop*'. See CVE-2021-29522.", "cve": "CVE-2021-29522", "id": "pyup.io-57912", "more_info_path": "/vulnerabilities/CVE-2021-29522/57912", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a segfault in 'SparseCountSparseOutput'. See CVE-2021-29521.", "cve": "CVE-2021-29521", "id": "pyup.io-57925", "more_info_path": "/vulnerabilities/CVE-2021-29521/57925", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix vulnerabilities where session operations in eager mode lead to null pointer dereferences. See CVE-2021-29518.", "cve": "CVE-2021-29518", "id": "pyup.io-57915", "more_info_path": "/vulnerabilities/CVE-2021-29518/57915", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a division by 0 in 'Conv2DBackpropInput'. See CVE-2021-29525.", "cve": "CVE-2021-29525", "id": "pyup.io-57910", "more_info_path": "/vulnerabilities/CVE-2021-29525/57910", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a 'CHECK'-fail in 'AddManySparseToTensorsMap'. See CVE-2021-29523.", "cve": "CVE-2021-29523", "id": "pyup.io-57916", "more_info_path": "/vulnerabilities/CVE-2021-29523/57916", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29534: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.SparseConcat'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/b432a38fe0e1b4b904a6c222cbce794c39703e87/tensorflow/core/kernels/sparse_concat_op.cc#L76) takes the values specified in 'shapes[0]' as dimensions for the output shape. The 'TensorShape' constructor (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a 'CHECK' operation which triggers when 'InitDims' (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status. This is a legacy implementation of the constructor and operations should use 'BuildTensorShapeBase' or 'AddDimWithStatus' to prevent 'CHECK'-failures in the presence of overflows.", "cve": "CVE-2021-29534", "id": "pyup.io-57922", "more_info_path": "/vulnerabilities/CVE-2021-29534/57922", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29532: An attacker can force accesses outside the bounds of heap allocated arrays by passing in invalid tensor values to `tf.raw_ops.RaggedCross`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/efea03b38fb8d3b81762237dc85e579cc5fc6e87/tensorflow/core/kernels/ragged_cross_op.cc#L456-L487) lacks validation for the user supplied arguments. Each of the above branches call a helper function after accessing array elements via a `*_list[next_*]` pattern, followed by incrementing the `next_*` index. However, as there is no validation that the `next_*` values are in the valid range for the corresponding `*_list` arrays, this results in heap OOB reads.", "cve": "CVE-2021-29532", "id": "pyup.io-57913", "more_info_path": "/vulnerabilities/CVE-2021-29532/57913", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a heap buffer overflow in 'Conv3DBackprop*'. See CVE-2021-29520.", "cve": "CVE-2021-29520", "id": "pyup.io-57921", "more_info_path": "/vulnerabilities/CVE-2021-29520/57921", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29539: TensorFlow is an end-to-end open source platform for machine learning. Calling `tf.raw_ops.ImmutableConst`(https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars. We have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. If using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument.", "cve": "CVE-2021-29539", "id": "pyup.io-57930", "more_info_path": "/vulnerabilities/CVE-2021-29539/57930", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29513: Calling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences. The conversion from Python array to C++ array (https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion.", "cve": "CVE-2021-29513", "id": "pyup.io-57923", "more_info_path": "/vulnerabilities/CVE-2021-29513/57923", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29549: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero. Since `vector_num_elements` is determined based on input shapes (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L522-L544), a user can trigger scenarios where this quantity is 0.", "cve": "CVE-2021-29549", "id": "pyup.io-57927", "more_info_path": "/vulnerabilities/CVE-2021-29549/57927", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29538: An attacker can cause a division by zero to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments). If all shapes are empty then 'work_unit_size' is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service.", "cve": "CVE-2021-29538", "id": "pyup.io-57926", "more_info_path": "/vulnerabilities/CVE-2021-29538/57926", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by invalid validation in 'SparseMatrixSparseCholesky'. See CVE-2021-29530.", "cve": "CVE-2021-29530", "id": "pyup.io-57909", "more_info_path": "/vulnerabilities/CVE-2021-29530/57909", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'StringNGrams'. See CVE-2021-29541.", "cve": "CVE-2021-29541", "id": "pyup.io-57907", "more_info_path": "/vulnerabilities/CVE-2021-29541/57907", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29535: An attacker can cause a heap buffer overflow in 'QuantizedMul' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/87cf4d3ea9949051e50ca3f071fc909538a51cd0/tensorflow/core/kernels/quantized_mul_op.cc#L287-L290) assumes that the 4 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29535", "id": "pyup.io-57908", "more_info_path": "/vulnerabilities/CVE-2021-29535/57908", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'StringNGrams'. See CVE-2021-29542.", "cve": "CVE-2021-29542", "id": "pyup.io-57906", "more_info_path": "/vulnerabilities/CVE-2021-29542/57906", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29536: An attacker can cause a heap buffer overflow in 'QuantizedReshape' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/a324ac84e573fba362a5e53d4e74d5de6729933e/tensorflow/core/kernels/quantized_reshape_op.cc#L38-L55) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29536", "id": "pyup.io-57905", "more_info_path": "/vulnerabilities/CVE-2021-29536/57905", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29543: An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks.", "cve": "CVE-2021-29543", "id": "pyup.io-57903", "more_info_path": "/vulnerabilities/CVE-2021-29543/57903", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29544: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.QuantizeAndDequantizeV4Grad'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the 'input_*' tensors. In turn, this results in the tensors being passes as they are to 'QuantizeAndDequantizePerChannelGradientImpl' (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306). However, the 'vec' method, requires the rank to 1 and triggers a 'CHECK' failure otherwise.", "cve": "CVE-2021-29544", "id": "pyup.io-57904", "more_info_path": "/vulnerabilities/CVE-2021-29544/57904", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29540: TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L495-L497) computes the size of the filter tensor but does not validate that it matches the number of elements in 'filter_sizes'. Later, when reading/writing to this buffer, code uses the value computed here, instead of the number of elements in the tensor.", "cve": "CVE-2021-29540", "id": "pyup.io-57902", "more_info_path": "/vulnerabilities/CVE-2021-29540/57902", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update its dependency 'curl' to version 7.76.0 to handle CVE-2020-8169.", "cve": "CVE-2020-8169", "id": "pyup.io-57901", "more_info_path": "/vulnerabilities/CVE-2020-8169/57901", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in 'Conv3D'. See CVE-2021-29517.", "cve": "CVE-2021-29517", "id": "pyup.io-57900", "more_info_path": "/vulnerabilities/CVE-2021-29517/57900", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix fixes a null pointer dereference via invalid Ragged Tensors. See CVE-2021-29516.", "cve": "CVE-2021-29516", "id": "pyup.io-57899", "more_info_path": "/vulnerabilities/CVE-2021-29516/57899", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 fix a reference binding to null pointer in 'MatrixDiag*' ops. See CVE-2021-29515.", "cve": "CVE-2021-29515", "id": "pyup.io-57898", "more_info_path": "/vulnerabilities/CVE-2021-29515/57898", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'EmbeddingLookup'. See CVE-2021-29596.", "cve": "CVE-2021-29596", "id": "pyup.io-57897", "more_info_path": "/vulnerabilities/CVE-2021-29596/57897", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's convolution code. See CVE-2021-29594.", "cve": "CVE-2021-29594", "id": "pyup.io-57896", "more_info_path": "/vulnerabilities/CVE-2021-29594/57896", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29558: An attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset.", "cve": "CVE-2021-29558", "id": "pyup.io-57895", "more_info_path": "/vulnerabilities/CVE-2021-29558/57895", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29551: The implementation of 'MatrixTriangularSolve' (https://github.com/tensorflow/tensorflow/blob/8cae746d8449c7dda5298327353d68613f16e798/tensorflow/core/kernels/linalg/matrix_triangular_solve_op_impl.h#L160-L240) fails to terminate kernel execution if one validation condition fails.", "cve": "CVE-2021-29551", "id": "pyup.io-57893", "more_info_path": "/vulnerabilities/CVE-2021-29551/57893", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29545: An attacker can trigger a denial of service via a 'CHECK'-fail in converting sparse tensors to CSR Sparse matrices. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/800346f2c03a27e182dd4fba48295f65e7790739/tensorflow/core/kernels/sparse/kernels.cc#L66) does a double redirection to access an element of an array allocated on the heap. If the value at 'indices(i, 0)' is such that 'indices(i, 0) + 1' is outside the bounds of 'csr_row_ptr', this results in writing outside of bounds of heap allocated data.", "cve": "CVE-2021-29545", "id": "pyup.io-57894", "more_info_path": "/vulnerabilities/CVE-2021-29545/57894", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in TFLite's 'Reshape' operator. See CVE-2021-29592.", "cve": "CVE-2021-29592", "id": "pyup.io-57892", "more_info_path": "/vulnerabilities/CVE-2021-29592/57892", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an undefined behavior in 'MaxPool3DGradGrad'. See CVE-2021-29574.", "cve": "CVE-2021-29574", "id": "pyup.io-57891", "more_info_path": "/vulnerabilities/CVE-2021-29574/57891", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a segfault in 'CTCBeamSearchDecoder'. See CVE-2021-29581.", "cve": "CVE-2021-29581", "id": "pyup.io-57888", "more_info_path": "/vulnerabilities/CVE-2021-29581/57888", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 include a fix for CVE-2021-29512: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433). Before the 'for' loop, 'batch_idx' is set to 0. The user controls the 'splits' array, making it contain only one element, 0. Thus, the code in the 'while' loop would increment 'batch_idx' and then try to read 'splits(1)', which is outside of bounds.", "cve": "CVE-2021-29512", "id": "pyup.io-57890", "more_info_path": "/vulnerabilities/CVE-2021-29512/57890", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29617: An attacker can cause a denial of service via `CHECK`-fail in `tf.strings.substr` with invalid arguments.", "cve": "CVE-2021-29617", "id": "pyup.io-57889", "more_info_path": "/vulnerabilities/CVE-2021-29617/57889", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'tf.raw_ops.CTCLoss'. See CVE-2021-29613.", "cve": "CVE-2021-29613", "id": "pyup.io-57887", "more_info_path": "/vulnerabilities/CVE-2021-29613/57887", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29556: An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.Reverse`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/36229ea9e9451dac14a8b1f4711c435a1d84a594/tensorflow/core/kernels/reverse_op.cc#L75-L76) performs a division based on the first dimension of the tensor argument.", "cve": "CVE-2021-29556", "id": "pyup.io-57886", "more_info_path": "/vulnerabilities/CVE-2021-29556/57886", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'Conv2D'. See CVE-2021-29526.", "cve": "CVE-2021-29526", "id": "pyup.io-57885", "more_info_path": "/vulnerabilities/CVE-2021-29526/57885", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'LoadAndRemapMatrix'. See CVE-2021-29561.", "cve": "CVE-2021-29561", "id": "pyup.io-57882", "more_info_path": "/vulnerabilities/CVE-2021-29561/57882", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'QuantizedConv2D'. See CVE-2021-29527.", "cve": "CVE-2021-29527", "id": "pyup.io-57883", "more_info_path": "/vulnerabilities/CVE-2021-29527/57883", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29595: The implementation of the `DepthToSpace` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69). An attacker can craft a model such that `params->block_size` is 0.", "cve": "CVE-2021-29595", "id": "pyup.io-57884", "more_info_path": "/vulnerabilities/CVE-2021-29595/57884", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29585: The TFLite computation for size of output after padding, `ComputeOutSize`(https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division. Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0.", "cve": "CVE-2021-29585", "id": "pyup.io-57881", "more_info_path": "/vulnerabilities/CVE-2021-29585/57881", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29514: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L446). Before the 'for' loop, 'batch_idx' is set to 0. The attacker sets 'splits(0)' to be 7, hence the 'while' loop does not execute and 'batch_idx' remains 0. This then results in writing to 'out(-1, bin)', which is before the heap allocated buffer for the output tensor.", "cve": "CVE-2021-29514", "id": "pyup.io-57880", "more_info_path": "/vulnerabilities/CVE-2021-29514/57880", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'TransposeConv'. See CVE-2021-29588.", "cve": "CVE-2021-29588", "id": "pyup.io-57873", "more_info_path": "/vulnerabilities/CVE-2021-29588/57873", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'SparseMatMul'. See CVE-2021-29557.", "cve": "CVE-2021-29557", "id": "pyup.io-57874", "more_info_path": "/vulnerabilities/CVE-2021-29557/57874", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'BandedTriangularSolve'. See CVE-2021-29612.", "cve": "CVE-2021-29612", "id": "pyup.io-57875", "more_info_path": "/vulnerabilities/CVE-2021-29612/57875", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29589: The reference implementation of the `GatherNd` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/reference_ops.h#L966). An attacker can craft a model such that `params` input would be an empty tensor. In turn, `params_shape.Dims(.)` would be zero, in at least one dimension.", "cve": "CVE-2021-29589", "id": "pyup.io-57877", "more_info_path": "/vulnerabilities/CVE-2021-29589/57877", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'FusedBatchNorm'. See CVE-2021-29555.", "cve": "CVE-2021-29555", "id": "pyup.io-57879", "more_info_path": "/vulnerabilities/CVE-2021-29555/57879", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap out of bounds read in 'MaxPoolGradWithArgmax'. See CVE-2021-29570.", "cve": "CVE-2021-29570", "id": "pyup.io-57876", "more_info_path": "/vulnerabilities/CVE-2021-29570/57876", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB access in unicode ops. See CVE-2021-29559.", "cve": "CVE-2021-29559", "id": "pyup.io-57878", "more_info_path": "/vulnerabilities/CVE-2021-29559/57878", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.1.0rc0,<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.1.0rc0,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of hashtable lookup. See CVE-2021-29604.", "cve": "CVE-2021-29604", "id": "pyup.io-57850", "more_info_path": "/vulnerabilities/CVE-2021-29604/57850", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB read in 'tf.raw_ops.Dequantize'. See CVE-2021-29582.", "cve": "CVE-2021-29582", "id": "pyup.io-57822", "more_info_path": "/vulnerabilities/CVE-2021-29582/57822", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29616: The implementation of TrySimplify (https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/grappler/optimizers/arithmetic_optimizer.cc#L390-L401) has undefined behavior due to dereferencing a null pointer in corner cases that result in optimizing a node with no inputs.", "cve": "CVE-2021-29616", "id": "pyup.io-57829", "more_info_path": "/vulnerabilities/CVE-2021-29616/57829", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'OneHot'. See CVE-2021-29600.", "cve": "CVE-2021-29600", "id": "pyup.io-57846", "more_info_path": "/vulnerabilities/CVE-2021-29600/57846", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'EditDistance'. See CVE-2021-29564.", "cve": "CVE-2021-29564", "id": "pyup.io-57847", "more_info_path": "/vulnerabilities/CVE-2021-29564/57847", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix fixes a heap OOB read in TFLite. See CVE-2021-29606.", "cve": "CVE-2021-29606", "id": "pyup.io-57823", "more_info_path": "/vulnerabilities/CVE-2021-29606/57823", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29583: The implementation of 'tf.raw_ops.FusedBatchNorm' is vulnerable to a heap buffer overflow. If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers. The implementation(https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that 'scale', 'offset', 'mean' and 'variance' (the last two only when required) all have the same number of elements as the number of channels of 'x'. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary. If the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior.", "cve": "CVE-2021-29583", "id": "pyup.io-57830", "more_info_path": "/vulnerabilities/CVE-2021-29583/57830", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail in 'tf.raw_ops.IRFFT'. See CVE-2021-29562.", "cve": "CVE-2021-29562", "id": "pyup.io-57824", "more_info_path": "/vulnerabilities/CVE-2021-29562/57824", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a integer overflow in TFLite memory allocation. See CVE-2021-29605.", "cve": "CVE-2021-29605", "id": "pyup.io-57844", "more_info_path": "/vulnerabilities/CVE-2021-29605/57844", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'BatchToSpaceNd'. See CVE-2021-29593.", "cve": "CVE-2021-29593", "id": "pyup.io-57839", "more_info_path": "/vulnerabilities/CVE-2021-29593/57839", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update 'curl' to '7.76.0' to handle CVE-2020-8177.", "cve": "CVE-2020-8177", "id": "pyup.io-57837", "more_info_path": "/vulnerabilities/CVE-2020-8177/57837", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'AvgPool3DGrad'. See CVE-2021-29577.", "cve": "CVE-2021-29577", "id": "pyup.io-57841", "more_info_path": "/vulnerabilities/CVE-2021-29577/57841", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'MaxPoolGrad'. See CVE-2021-29579.", "cve": "CVE-2021-29579", "id": "pyup.io-57843", "more_info_path": "/vulnerabilities/CVE-2021-29579/57843", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a stack overflow due to looping TFLite subgraph. See CVE-2021-29591.", "cve": "CVE-2021-29591", "id": "pyup.io-57820", "more_info_path": "/vulnerabilities/CVE-2021-29591/57820", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29610: The validation in 'tf.raw_ops.QuantizeAndDequantizeV2' allows invalid values for 'axis' argument:. The validation (https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses '||' to mix two different conditions. If 'axis_ < -1' the condition in 'OP_REQUIRES' will still be true, but this value of 'axis_' results in heap underflow. This allows attackers to read/write to other data on the heap.", "cve": "CVE-2021-29610", "id": "pyup.io-57872", "more_info_path": "/vulnerabilities/CVE-2021-29610/57872", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseAdd'. See CVE-2021-29609.", "cve": "CVE-2021-29609", "id": "pyup.io-57832", "more_info_path": "/vulnerabilities/CVE-2021-29609/57832", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29608: TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in 'tf.raw_ops.RaggedTensorToTensor', an attacker can exploit an undefined behavior if input arguments are empty. The implementation (https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones. There are multiple 'DCHECK' validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything.", "cve": "CVE-2021-29608", "id": "pyup.io-57831", "more_info_path": "/vulnerabilities/CVE-2021-29608/57831", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseSparseMinimum'. See CVE-2021-29607.", "cve": "CVE-2021-29607", "id": "pyup.io-57827", "more_info_path": "/vulnerabilities/CVE-2021-29607/57827", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'SpaceToBatchNd'. See CVE-2021-29597.", "cve": "CVE-2021-29597", "id": "pyup.io-57825", "more_info_path": "/vulnerabilities/CVE-2021-29597/57825", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB read in TFLite's implementation of 'Minimum' or 'Maximum'. See CVE-2021-29590.", "cve": "CVE-2021-29590", "id": "pyup.io-57861", "more_info_path": "/vulnerabilities/CVE-2021-29590/57861", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29587: TensorFlow is an end-to-end open source platform for machine learning. The `Prepare` step of the `SpaceToDepth` TFLite operator does not check for 0 before division (https://github.com/tensorflow/tensorflow/blob/5f7975d09eac0f10ed8a17dbb6f5964977725adc/tensorflow/lite/kernels/space_to_depth.cc#L63-L67). An attacker can craft a model such that `params->block_size` would be zero.", "cve": "CVE-2021-29587", "id": "pyup.io-57852", "more_info_path": "/vulnerabilities/CVE-2021-29587/57852", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in optimized pooling implementations in TFLite. See CVE-2021-29586.", "cve": "CVE-2021-29586", "id": "pyup.io-57860", "more_info_path": "/vulnerabilities/CVE-2021-29586/57860", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a 'CHECK'-fail due to integer overflow. See CVE-2021-29584.", "cve": "CVE-2021-29584", "id": "pyup.io-57819", "more_info_path": "/vulnerabilities/CVE-2021-29584/57819", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an undefined behavior and a 'CHECK'-fail in 'FractionalMaxPoolGrad'. See CVE-2021-29580.", "cve": "CVE-2021-29580", "id": "pyup.io-57867", "more_info_path": "/vulnerabilities/CVE-2021-29580/57867", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap out of bounds read in 'RequantizationRange'. See CVE-2021-29569.", "cve": "CVE-2021-29569", "id": "pyup.io-57855", "more_info_path": "/vulnerabilities/CVE-2021-29569/57855", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger undefined behavior by binding to null pointer in 'tf.raw_ops.ParameterizedTruncatedNormal'. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/3f6fe4dfef6f57e768260b48166c27d148f3015f/tensorflow/core/kernels/parameterized_truncated_normal_op.cc#L630) does not validate input arguments before accessing the first element of 'shape'. If 'shape' argument is empty, then 'shape_tensor.flat()' is an empty array. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.", "cve": "CVE-2021-29568", "id": "pyup.io-57853", "more_info_path": "/vulnerabilities/CVE-2021-29568/57853", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a null pointer dereference in 'SparseFillEmptyRows'. See CVE-2021-29565.", "cve": "CVE-2021-29565", "id": "pyup.io-57828", "more_info_path": "/vulnerabilities/CVE-2021-29565/57828", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29550: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values. The user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor operation results in `output_size[i]` being 0. The `DCHECK_GT` line is a no-op outside of debug mode, so in released versions of TF this does not trigger. Later, these computed values are used as arguments (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to `GeneratePoolingSequence`(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation. Since `output_length` can be 0, this results in runtime crashing.", "cve": "CVE-2021-29550", "id": "pyup.io-57868", "more_info_path": "/vulnerabilities/CVE-2021-29550/57868", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29547: An attacker can cause a segfault and denial of service via accessing data outside of bounds in 'tf.raw_ops.QuantizedBatchNormWithGlobalNormalization'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc#L176-L189) assumes the inputs are not empty. If any of these inputs is empty, '.flat()' is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds.", "cve": "CVE-2021-29547", "id": "pyup.io-57848", "more_info_path": "/vulnerabilities/CVE-2021-29547/57848", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29546: TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger an integer division by zero undefined behavior in `tf.raw_ops.QuantizedBiasAdd`. This is because the implementation of the Eigen kernel (https://github.com/tensorflow/tensorflow/blob/61bca8bd5ba8a68b2d97435ddfafcdf2b85672cd/tensorflow/core/kernels/quantization_utils.h#L812-L849) does a division by the number of elements of the smaller input (based on shape) without checking that this is not zero.", "cve": "CVE-2021-29546", "id": "pyup.io-57869", "more_info_path": "/vulnerabilities/CVE-2021-29546/57869", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB write in TFLite. See CVE-2021-29603.", "cve": "CVE-2021-29603", "id": "pyup.io-57849", "more_info_path": "/vulnerabilities/CVE-2021-29603/57849", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'QuantizedMul'. See CVE-2021-29528.", "cve": "CVE-2021-29528", "id": "pyup.io-57864", "more_info_path": "/vulnerabilities/CVE-2021-29528/57864", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'Split'. See CVE-2021-29599.", "cve": "CVE-2021-29599", "id": "pyup.io-57826", "more_info_path": "/vulnerabilities/CVE-2021-29599/57826", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'SVDF'. See CVE-2021-29598.", "cve": "CVE-2021-29598", "id": "pyup.io-57862", "more_info_path": "/vulnerabilities/CVE-2021-29598/57862", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'MaxPoolGradWithArgmax'. See CVE-2021-29573.", "cve": "CVE-2021-29573", "id": "pyup.io-57859", "more_info_path": "/vulnerabilities/CVE-2021-29573/57859", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap OOB in 'QuantizeAndDequantizeV3'. See CVE-2021-29553.", "cve": "CVE-2021-29553", "id": "pyup.io-57865", "more_info_path": "/vulnerabilities/CVE-2021-29553/57865", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29566: An attacker can write outside the bounds of heap allocated arrays by passing invalid arguments to 'tf.raw_ops.Dilation2DBackpropInput'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/afd954e65f15aea4d438d0a219136fc4a63a573d/tensorflow/core/kernels/dilation_ops.cc#L321-L322) does not validate before writing to the output array. The values for 'h_out' and 'w_out' are guaranteed to be in range for 'out_backprop' (as they are loop indices bounded by the size of the array). However, there are no similar guarantees relating 'h_in_max'/'w_in_max' and 'in_backprop'.", "cve": "CVE-2021-29566", "id": "pyup.io-57851", "more_info_path": "/vulnerabilities/CVE-2021-29566/57851", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'MaxPool3DGradGrad'. See CVE-2021-29576.", "cve": "CVE-2021-29576", "id": "pyup.io-57845", "more_info_path": "/vulnerabilities/CVE-2021-29576/57845", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm versions 2.5.0, 2.4.2, 2.3.3, 2.2.3 and 2.1.4 updates its dependency \"curl\" to a secure version (7.76.0).", "cve": "CVE-2020-8285", "id": "pyup.io-57857", "more_info_path": "/vulnerabilities/CVE-2020-8285/57857", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm versions 2.1.4, 2.2.3, 2.3.3, 2.4.2 and 2.5.0 update its dependency \"curl\" to handle CVE-2020-8284.", "cve": "CVE-2020-8284", "id": "pyup.io-57842", "more_info_path": "/vulnerabilities/CVE-2020-8284/57842", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix an overflow and a denial of service in 'tf.raw_ops.ReverseSequence'. See CVE-2021-29575.", "cve": "CVE-2021-29575", "id": "pyup.io-57821", "more_info_path": "/vulnerabilities/CVE-2021-29575/57821", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by 0 in 'DenseCountSparseOutput'. See CVE-2021-29554.", "cve": "CVE-2021-29554", "id": "pyup.io-57840", "more_info_path": "/vulnerabilities/CVE-2021-29554/57840", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.5.0, 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29572: The implementation of `tf.raw_ops.SdcaOptimizer` triggers undefined behavior due to dereferencing a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/60a45c8b6192a4699f2e2709a2645a751d435cc3/tensorflow/core/kernels/sdca_internal.cc) does not validate that the user supplied arguments satisfy all constraints expected by the op(https://www.tensorflow.org/api_docs/python/tf/raw_ops/SdcaOptimizer).", "cve": "CVE-2021-29572", "id": "pyup.io-57856", "more_info_path": "/vulnerabilities/CVE-2021-29572/57856", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29618: Passing a complex argument to `tf.transpose` at the same time as passing 'conjugate=True' argument results in a crash.", "cve": "CVE-2021-29618", "id": "pyup.io-57870", "more_info_path": "/vulnerabilities/CVE-2021-29618/57870", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a division by zero in TFLite's implementation of 'DepthwiseConv'. See CVE-2021-29602.", "cve": "CVE-2021-29602", "id": "pyup.io-57835", "more_info_path": "/vulnerabilities/CVE-2021-29602/57835", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 updates 'curl' to '7.76.0' to handle CVE-2020-8286: curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response.", "cve": "CVE-2020-8286", "id": "pyup.io-57838", "more_info_path": "/vulnerabilities/CVE-2020-8286/57838", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix vulnerabilities caused by incomplete validation in 'SparseReshape'. See CVE-2021-29611.", "cve": "CVE-2021-29611", "id": "pyup.io-57866", "more_info_path": "/vulnerabilities/CVE-2021-29611/57866", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29571: The implementation of 'tf.raw_ops.MaxPoolGradWithArgmax' can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation (https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of 'boxes' input is 4, as required by the op (https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption. If the last dimension in 'boxes' is less than 4, accesses similar to 'tboxes(b, bb, 3)' will access data outside of bounds. Further during code execution there are also writes to these indices.", "cve": "CVE-2021-29571", "id": "pyup.io-57854", "more_info_path": "/vulnerabilities/CVE-2021-29571/57854", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 update its dependency \"curl\" to v7.76.0 to include security fixes.", "cve": "CVE-2020-8231", "id": "pyup.io-57836", "more_info_path": "/vulnerabilities/CVE-2020-8231/57836", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a segfault in 'tf.raw_ops.SparseCountSparseOutput'. See CVE-2021-29619.", "cve": "CVE-2021-29619", "id": "pyup.io-57833", "more_info_path": "/vulnerabilities/CVE-2021-29619/57833", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29560: An attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel. Since the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when 'parent_output_index' is shorter than 'row_split'.", "cve": "CVE-2021-29560", "id": "pyup.io-57871", "more_info_path": "/vulnerabilities/CVE-2021-29560/57871", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a heap buffer overflow in 'FractionalAvgPoolGrad'. See CVE-2021-29578.", "cve": "CVE-2021-29578", "id": "pyup.io-57834", "more_info_path": "/vulnerabilities/CVE-2021-29578/57834", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 fix a integer overflow in TFLite concatentation. See CVE-2021-29601.", "cve": "CVE-2021-29601", "id": "pyup.io-57858", "more_info_path": "/vulnerabilities/CVE-2021-29601/57858", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.1.4, 2.2.3, 2.3.3, 2.4.2, and 2.5.0 include a fix for CVE-2021-29563: An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`. Eigen code operating on an empty matrix can trigger on an assertion and will cause program termination.", "cve": "CVE-2021-29563", "id": "pyup.io-57863", "more_info_path": "/vulnerabilities/CVE-2021-29563/57863", "specs": [ ">=2.5.0rc0,<2.5.0", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.1.0rc0,<2.1.4" ], "v": ">=2.5.0rc0,<2.5.0,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.1.0rc0,<2.1.4" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37691: In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). The Tensorflow team has patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9.", "cve": "CVE-2021-37691", "id": "pyup.io-57818", "more_info_path": "/vulnerabilities/CVE-2021-37691/57818", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37645: In affected versions the implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit 96f364a1ca3009f98980021c4b32be5fdcca33a1.", "cve": "CVE-2021-37645", "id": "pyup.io-57817", "more_info_path": "/vulnerabilities/CVE-2021-37645/57817", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37688: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer. The Tensorflow team has patched the issue in GitHub commit 15691e456c7dc9bd6be203b09765b063bf4a380c.", "cve": "CVE-2021-37688", "id": "pyup.io-57816", "more_info_path": "/vulnerabilities/CVE-2021-37688/57816", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm 2.5.1 and 2.6.0 include a fix for CVE-2021-37640: In affected versions the implementation of 'tf.raw_ops.SparseReshape' can be made to trigger an integral division by 0 exception. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements. The reshape functor (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0. The Tensorflow team has patched the issue in GitHub commit 4923de56ec94fff7770df259ab7f2288a74feb41.", "cve": "CVE-2021-37640", "id": "pyup.io-57815", "more_info_path": "/vulnerabilities/CVE-2021-37640/57815", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm versions 2.5.1 and 2.6.0 include a fix for CVE-2021-37692:\nIn affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, \"C.TF_TString_Dealloc\" is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until \"NewTensor\" returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. The Tensorflow team has patched the issue in GitHub commit:\nhttps://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22\nhttps://github.com/tensorflow/tensorflow/pull/50508\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cmgw-8vpc-rc59", "cve": "CVE-2021-37692", "id": "pyup.io-57814", "more_info_path": "/vulnerabilities/CVE-2021-37692/57814", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm versions 2.3.4, 2.4.3, 2.5.1, and 2.6.0 update its dependency \"curl\" to include a fix for CVE-2021-22898", "cve": "CVE-2021-22898", "id": "pyup.io-57813", "more_info_path": "/vulnerabilities/CVE-2021-22898/57813", "specs": [ ">=2.6.0a1,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0a1,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37668:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.UnravelIndex\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by \"dims\" is not empty. Hence, if one element of \"dims\" is 0, the implementation does a division by 0. The Tensorflow team has patched the issue in GitHub commit a776040a5e7ebf76eeb7eb923bf1ae417dd4d233.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2wmv-37vq-52g5\nhttps://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233", "cve": "CVE-2021-37668", "id": "pyup.io-57803", "more_info_path": "/vulnerabilities/CVE-2021-37668/57803", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37685: In affected versions TFLite's 'expand_dims.cc' (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data. If 'axis' is a large negative value (e.g., '-100000'), then after the first 'if' it would still be negative. The check following the 'if' statement will pass and the 'for' loop would read one element before the start of 'input_dims.data' (when 'i = 0'). The Tensorflow team has patched the issue in GitHub commit d94ffe08a65400f898241c0374e9edc6fa8ed257.", "cve": "CVE-2021-37685", "id": "pyup.io-57805", "more_info_path": "/vulnerabilities/CVE-2021-37685/57805", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37675: In affected versions most implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations. The Tensorflow team has patched the issue in GitHub commit 8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4.", "cve": "CVE-2021-37675", "id": "pyup.io-57808", "more_info_path": "/vulnerabilities/CVE-2021-37675/57808", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37665:\nIn affected versions, due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the \"input\" tensor. A similar issue occurs in \"MklRequantizePerChannelOp\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments. The Tensorflow team has patched the issue in GitHub commit 9e62869465573cb2d9b5053f1fa02a81fce21d69 and in the Github commit 203214568f5bc237603dbab6e1fd389f1572f5c9.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v82p-hv3v-p6qp\nhttps://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9\nhttps://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69", "cve": "CVE-2021-37665", "id": "pyup.io-57807", "more_info_path": "/vulnerabilities/CVE-2021-37665/57807", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37653: In affected versions an attacker can trigger a crash via a floating point exception in 'tf.raw_ops.ResourceGather'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, 'batch_size', and then divides by it without checking that this value is not 0. The Tensorflow team has patched the issue in GitHub commit ac117ee8a8ea57b73d34665cdf00ef3303bc0b11.", "cve": "CVE-2021-37653", "id": "pyup.io-57811", "more_info_path": "/vulnerabilities/CVE-2021-37653/57811", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37687: In affected versions TFLite's 'GatherNd' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation. Hence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in 'indices'. Similar issue exists in 'Gather' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc). The Tensorflow team has patched the issue in GitHub commits bb6a0383ed553c286f87ca88c207f6774d5c4a8f and eb921122119a6b6e470ee98b89e65d721663179d.", "cve": "CVE-2021-37687", "id": "pyup.io-57809", "more_info_path": "/vulnerabilities/CVE-2021-37687/57809", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37657: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. The Tensorflow team has checked that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit f2a673bd34f0d64b8e40a551ac78989d16daad09.", "cve": "CVE-2021-37657", "id": "pyup.io-57802", "more_info_path": "/vulnerabilities/CVE-2021-37657/57802", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37663:\nIn affected versions, due to incomplete validation in \"tf.raw_ops.QuantizeV2\", an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that \"min_range\" and \"max_range\" both have the same non-zero number of elements. If \"axis\" is provided (i.e., not \"-1\"), then validation should check that it is a value in range for the rank of \"input\" tensor and then the lengths of \"min_range\" and \"max_range\" inputs match the \"axis\" dimension of the \"input\" tensor. The Tensorflow team has patched the issue in GitHub commit 6da6620efad397c85493b8f8667b821403516708. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g25h-jr74-qp5j\nhttps://github.com/tensorflow/tensorflow/commit/6da6620efad397c85493b8f8667b821403516708", "cve": "CVE-2021-37663", "id": "pyup.io-57804", "more_info_path": "/vulnerabilities/CVE-2021-37663/57804", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37676: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.SparseFillEmptyRows'. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors. The Tensorflow team has patched the issue in GitHub commit 578e634b4f1c1c684d4b4294f9e5281b2133b3ed.", "cve": "CVE-2021-37676", "id": "pyup.io-57810", "more_info_path": "/vulnerabilities/CVE-2021-37676/57810", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37661: In affected versions an attacker can cause a denial of service in 'boosted_trees_create_quantile_stream_resource' by using negative arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that 'num_streams' only contains non-negative numbers. In turn, this results in using this value to allocate memory (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40). However, 'reserve' receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library. The Tensorflow team has patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992.", "cve": "CVE-2021-37661", "id": "pyup.io-57806", "more_info_path": "/vulnerabilities/CVE-2021-37661/57806", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37660: In affected versions an attacker can cause a floating point exception by calling inplace operations with crafted arguments that would result in a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/inplace_ops.cc#L283) has a logic error: it should skip processing if 'x' and 'v' are empty but the code uses '||' instead of '&&'. The Tensorflow team has patched the issue in GitHub commit e86605c0a336c088b638da02135ea6f9f6753618.", "cve": "CVE-2021-37660", "id": "pyup.io-57812", "more_info_path": "/vulnerabilities/CVE-2021-37660/57812", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37641: In affected versions if the arguments to 'tf.raw_ops.RaggedGather' don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by 'params_nested_splits' is not an empty list of tensors. The Tensorflow team has patched the issue in GitHub commit a2b743f6017d7b97af1fe49087ae15f0ac634373.", "cve": "CVE-2021-37641", "id": "pyup.io-57797", "more_info_path": "/vulnerabilities/CVE-2021-37641/57797", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37646: In affected versions the implementation of 'tf.raw_ops.StringNGrams' is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls 'reserve' on a 'tstring' with a value that sometimes can be negative if user supplies negative 'ngram_widths'. The 'reserve' method calls 'TF_TString_Reserve' which has an 'unsigned long' argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5.", "cve": "CVE-2021-37646", "id": "pyup.io-57800", "more_info_path": "/vulnerabilities/CVE-2021-37646/57800", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37662: In affected versions an attacker can generate undefined behavior via a reference binding to nullptr in 'BoostedTreesCalculateBestGainsPerFeature' and similar attack can occur in 'BoostedTreesCalculateBestFeatureSplitV2'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values. The Tensorflow team has patched the issue in GitHub commit 9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad and in commit 429f009d2b2c09028647dd4bb7b3f6f414bbaad7.", "cve": "CVE-2021-37662", "id": "pyup.io-57795", "more_info_path": "/vulnerabilities/CVE-2021-37662/57795", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37681: In affected versions the implementation of SVDF in TFLite is vulnerable to a null pointer error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313). The 'GetVariableInput' function (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but 'GetTensorData' assumes that the argument is always a valid tensor. Furthermore, because 'GetVariableInput' calls 'GetMutableInput' (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return 'nullptr', the 'tensor->is_variable' expression can also trigger a null pointer exception. The Tensorflow team has patched the issue in GitHub commit 5b048e87e4e55990dae6b547add4dae59f4e1c76.", "cve": "CVE-2021-37681", "id": "pyup.io-57798", "more_info_path": "/vulnerabilities/CVE-2021-37681/57798", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37684: In affected versions the implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695 (https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).", "cve": "CVE-2021-37684", "id": "pyup.io-57794", "more_info_path": "/vulnerabilities/CVE-2021-37684/57794", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37643: If a user does not provide a valid padding value to 'tf.raw_ops.MatrixDiagPartOp', then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from. The Tensorflow team has patched the issue in GitHub commit 482da92095c4d48f8784b1f00dda4f81c28d2988.", "cve": "CVE-2021-37643", "id": "pyup.io-57796", "more_info_path": "/vulnerabilities/CVE-2021-37643/57796", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37644: In affected versions providing a negative element to 'num_elements' list argument of 'tf.raw_ops.TensorListReserve' causes the runtime to abort the process due to reallocating a 'std::vector' to have a negative number of elements. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls 'std::vector.resize()' with the new size controlled by input given by the user, without checking that this input is valid. The Tensorflow team has patched the issue in GitHub commit 8a6e874437670045e6c7dc6154c7412b4a2135e2.", "cve": "CVE-2021-37644", "id": "pyup.io-57799", "more_info_path": "/vulnerabilities/CVE-2021-37644/57799", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37666: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToVariant'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty. The Tensorflow team has patched the issue in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612.", "cve": "CVE-2021-37666", "id": "pyup.io-57801", "more_info_path": "/vulnerabilities/CVE-2021-37666/57801", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37682:\nIn affected versions all TFLite operations that use quantization can be made to use unitialized values. (For example, https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200). The issue stems from the fact that \"quantization.params\" is only valid if \"quantization.type\" is different that \"kTfLiteNoQuantization\". However, these checks are missing in large parts of the code. The Tensorflow team has patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4c4g-crqm-xrxw\nhttps://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5\nhttps://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887\nhttps://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538", "cve": "CVE-2021-37682", "id": "pyup.io-57792", "more_info_path": "/vulnerabilities/CVE-2021-37682/57792", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37690:\nIn affected versions when running shape functions, some functions (such as 'MutableHashTableShape') produce extra output information in the form of a 'ShapeAndType' struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault. 'ShapeRefiner' is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but the Tensorflow team was not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types. The Tensorflow team has patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3hxh-8cp2-g4hg\nhttps://github.com/tensorflow/tensorflow/commit/ee119d4a498979525046fba1c3dd3f13a039fbb1", "cve": "CVE-2021-37690", "id": "pyup.io-57793", "more_info_path": "/vulnerabilities/CVE-2021-37690/57793", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22897", "id": "pyup.io-57784", "more_info_path": "/vulnerabilities/CVE-2021-22897/57784", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37650: In affected versions the implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types. The Tensorflow team has patched the issue in GitHub commit e0b6e58c328059829c3eb968136f17aa72b6c876.", "cve": "CVE-2021-37650", "id": "pyup.io-57787", "more_info_path": "/vulnerabilities/CVE-2021-37650/57787", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a denial of service via a segmentation fault in 'tf.raw_ops.MaxPoolGrad' caused by missing validation. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the 'orig_input' and 'orig_output' tensors. The fixes for CVE-2021-29579 were incomplete. We have patched the issue in GitHub commit 136b51f10903e044308cf77117c0ed9871350475. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.", "cve": "CVE-2021-37674", "id": "pyup.io-57788", "more_info_path": "/vulnerabilities/CVE-2021-37674/57788", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22876", "id": "pyup.io-57785", "more_info_path": "/vulnerabilities/CVE-2021-22876/57785", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37672:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.SdcaOptimizerV2\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of \"example_labels\" is the same as the number of examples. The Tensorflow team has patched the issue in GitHub commit a4e138660270e7599793fa438cd7b2fc2ce215a6.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hj3-vjjf-f5m7\nhttps://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6", "cve": "CVE-2021-37672", "id": "pyup.io-57780", "more_info_path": "/vulnerabilities/CVE-2021-37672/57780", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37670:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.UpperBound\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of \"sorted_input\" argument. A similar issue occurs in \"tf.raw_ops.LowerBound\". The Tensorflow team has patched the issue in GitHub commit 42459e4273c2e47a3232cc16c4f4fff3b3a35c38.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9697-98pf-4rw7\nhttps://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38", "cve": "CVE-2021-37670", "id": "pyup.io-57781", "more_info_path": "/vulnerabilities/CVE-2021-37670/57781", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37669:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.NonMaxSuppressionV5\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a \"std::vector\". However, as \"std::vector::resize\" takes the size argument as a \"size_t\" and \"output_size\" is an \"int\", there is an implicit conversion to unsigned. If the attacker supplies a negative value, this conversion results in a crash. A similar issue occurs in \"CombinedNonMaxSuppression\". The Tensorflow team has patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c\nhttps://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d\nhttps://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58", "cve": "CVE-2021-37669", "id": "pyup.io-57789", "more_info_path": "/vulnerabilities/CVE-2021-37669/57789", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37655: TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to 'tf.raw_ops.ResourceScatterUpdate'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of 'indices' and 'updates': instead of checking that the shape of 'indices' is a prefix of the shape of 'updates' (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. The Tensorflow team has patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f.", "cve": "CVE-2021-37655", "id": "pyup.io-57779", "more_info_path": "/vulnerabilities/CVE-2021-37655/57779", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. In affected versions the shape inference code for 'tf.raw_ops.Dequantize' has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments. The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses 'axis' to select between two different values for 'minmax_rank' which is then used to retrieve tensor dimensions. However, code assumes that 'axis' can be either '-1' or a value greater than '-1', with no validation for the other values. We have patched the issue in GitHub commit da857cfa0fde8f79ad0afdbc94e88b5d4bbec764. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.", "cve": "CVE-2021-37677", "id": "pyup.io-57790", "more_info_path": "/vulnerabilities/CVE-2021-37677/57790", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm 2.3.4, 2.4.3, 2.5.1, and 2.6.0 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22901", "id": "pyup.io-57783", "more_info_path": "/vulnerabilities/CVE-2021-22901/57783", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37679:\nIn affected versions it is possible to nest a \"tf.map_fn\" within another \"tf.map_fn\" call. However, if the input tensor is a \"RaggedTensor\" and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap. The \"t\" and \"z\" outputs should be identical, however this is not the case. The last row of \"t\" contains data from the heap which can be used to leak other memory information. The bug lies in the conversion from a \"Variant\" tensor to a \"RaggedTensor\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions. The same implementation can result in data loss, if input tensor is tweaked. The Tensorflow team has patched the issue in GitHub commit 4e2565483d0ffcadc719bd44893fb7f609bb5f12.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g8wg-cjwc-xhhp\nhttps://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12", "cve": "CVE-2021-37679", "id": "pyup.io-57782", "more_info_path": "/vulnerabilities/CVE-2021-37679/57782", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1 and 2.6.0 include a fix for CVE-2021-37673:\nIn affected versions, an attacker can trigger a denial of service via a \"CHECK\"-fail in \"tf.raw_ops.MapStage\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the \"key\" input is a valid non-empty tensor. The Tensorflow team has patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-278g-rq84-9hmg\nhttps://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d", "cve": "CVE-2021-37673", "id": "pyup.io-57786", "more_info_path": "/vulnerabilities/CVE-2021-37673/57786", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4" }, { "advisory": "Tensorflow-rocm version 2.3.4, 2.4.3, 2.5.1, 2.6.0 and 2.7.0 include a fix for CVE-2021-37678:\nIn affected versions, TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The implementation(https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses \"yaml.unsafe_load\" which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, the Tensorflow team has removed it for now. The Tensorflow team has patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r\nhttps://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012", "cve": "CVE-2021-37678", "id": "pyup.io-57791", "more_info_path": "/vulnerabilities/CVE-2021-37678/57791", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.7.0rc0,<2.7.0" ], "v": ">=2.6.0rc0,<2.6.0,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.7.0rc0,<2.7.0" }, { "advisory": "Tensorflow-rocm version 2.6.1 includes a fix for CVE-2021-41211: In affected versions, the shape inference code for 'QuantizeV2' can trigger a read outside of bounds of heap allocated array. This occurs whenever 'axis' is a negative value less than '-1'. In this case, we are accessing data before the start of a heap buffer. The code allows 'axis' to be an optional argument ('s' would contain an 'error::NOT_FOUND' error code). Otherwise, it assumes that 'axis' is a valid index into the dimensions of the 'input' tensor. If 'axis' is less than '-1' then this results in a heap OOB read. The fix is included in TensorFlow 2.7.0. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvgx-3v3q-m36c\nhttps://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244", "cve": "CVE-2021-41211", "id": "pyup.io-57778", "more_info_path": "/vulnerabilities/CVE-2021-41211/57778", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm version 2.6.1 includes a fix for CVE-2021-41220: In affected versions, the async implementation of 'CollectiveReduceV2' suffers from a memory leak and a use after free. This occurs due to the asynchronous computation and the fact that objects that have been 'std::move()'d are still accessed. The fix is included in TensorFlow 2.7.0.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gpfh-jvf9-7wg5\nhttps://github.com/tensorflow/tensorflow/commit/ca38dab9d3ee66c5de06f11af9a4b1200da5ef75", "cve": "CVE-2021-41220", "id": "pyup.io-57777", "more_info_path": "/vulnerabilities/CVE-2021-41220/57777", "specs": [ ">=2.6.0rc0,<2.6.1" ], "v": ">=2.6.0rc0,<2.6.1" }, { "advisory": "Tensorflow-rocm is an Open Source Machine Learning Framework. The TFG dialect of TensorFlow (MLIR) makes several assumptions about the incoming `GraphDef` before converting it to the MLIR-based dialect. If an attacker changes the `SavedModel` format on disk to invalidate these assumptions and the `GraphDef` is then converted to MLIR-based IR then they can cause a crash in the Python interpreter. Under certain scenarios, heap OOB read/writes are possible. These issues have been discovered via fuzzing and it is possible that more weaknesses exist. We will patch them as they are discovered.", "cve": "CVE-2022-23594", "id": "pyup.io-57687", "more_info_path": "/vulnerabilities/CVE-2022-23594/57687", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm versions 2.7.1 and 2.8.0 include a fix for CVE-2022-23590: A 'GraphDef' from a TensorFlow 'SavedModel' can be maliciously altered to cause a TensorFlow process to crash due to encountering a 'StatusOr' value that is an error and forcibly extracting the value from it.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pqrv-8r2f-7278", "cve": "CVE-2022-23590", "id": "pyup.io-57686", "more_info_path": "/vulnerabilities/CVE-2022-23590/57686", "specs": [ ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": ">=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm version 2.8.0 includes a fix for CVE-2022-23592: TensorFlow's type inference can cause a heap out of bounds read as the bounds checking is done in a 'DCHECK' (which is a no-op during production). An attacker can control the 'input_idx' variable such that 'ix' would be larger than the number of values in 'node_t.args'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vq36-27g6-p492", "cve": "CVE-2022-23592", "id": "pyup.io-57684", "more_info_path": "/vulnerabilities/CVE-2022-23592/57684", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "Tensorflow-rocm 2.8.0 includes a fix for CVE-2022-23593: The 'simplifyBroadcast' function in the MLIR-TFRT infrastructure in TensorFlow is vulnerable to a segfault (hence, denial of service), if called with scalar shapes. If all shapes are scalar, then 'maxRank' is 0, so we build an empty 'SmallVector'. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gwcx-jrx4-92w2", "cve": "CVE-2022-23593", "id": "pyup.io-57685", "more_info_path": "/vulnerabilities/CVE-2022-23593/57685", "specs": [ ">=2.8.0a0,<2.8.0" ], "v": ">=2.8.0a0,<2.8.0" }, { "advisory": "TensorFlow is an open source platform for machine learning. In version 2.8.0, the 'TensorKey' hash function used total estimated 'AllocatedBytes()', which (a) is an estimate per tensor, and (b) is a very poor hash function for constants (e.g. 'int32_t'). It also tried to access individual tensor bytes through 'tensor.data()' of size 'AllocatedBytes()'. This led to ASAN failures because the 'AllocatedBytes()' is an estimate of total bytes allocated by a tensor, including any pointed-to constructs (e.g. strings), and does not refer to contiguous bytes in the '.data()' buffer. The discoverers could not use this byte vector anyway because types such as 'tstring' include pointers, whereas they needed to hash the string values themselves. This issue is patched in Tensorflow versions 2.9.0 and 2.8.1.", "cve": "CVE-2022-29210", "id": "pyup.io-57648", "more_info_path": "/vulnerabilities/CVE-2022-29210/57648", "specs": [ ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": ">=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" } ], "tensorflow-rocm-enhanced": [ { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15206: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's \"SavedModel\" protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using \"tensorflow-serving\" or other inference-as-a-service installments. Fixed were added in commits f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d. However, this was not enough, as #41097 reported a different failure mode. The issue was finally patched in commit df095206f25471e864a8e63a0f1caef53a0e3a6", "cve": "CVE-2020-15206", "id": "pyup.io-58218", "more_info_path": "/vulnerabilities/CVE-2020-15206/58218", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15208: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a \"DCHECK\" which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue was patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d", "cve": "CVE-2020-15208", "id": "pyup.io-58220", "more_info_path": "/vulnerabilities/CVE-2020-15208/58220", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15190: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the \"tf.raw_ops.Switch\" operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is \"nullptr\", hence we are binding a reference to \"nullptr\". This is undefined behavior and reported as an error if compiling with \"-fsanitize=null\". In this case, this results in a segmentation fault The issue was patched in commit da8558533d925694483d2c136a9220d6d49d843c\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4g9f-63rx-5cw4", "cve": "CVE-2020-15190", "id": "pyup.io-58221", "more_info_path": "/vulnerabilities/CVE-2020-15190/58221", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15211: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor. However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative \"-1\" value as index for these tensors. This results in special casing during validation at model loading time. Unfortunately, this means that the \"-1\" index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays. This results in both read and write gadgets, albeit very limited in scope. The issue was patched in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83). A potential workaround would be to add a custom \"Verifier\" to the model loading code to ensure that only operators which accept optional inputs use the \"-1\" special value and only for the tensors that they expect to be optional. Since this allow-list type approach is error-prone, it's advised upgrading to the patched code.", "cve": "CVE-2020-15211", "id": "pyup.io-58219", "more_info_path": "/vulnerabilities/CVE-2020-15211/58219", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15209: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a \"nullptr\" buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with \"nullptr\". However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue was patched in commit 0b5662bc.", "cve": "CVE-2020-15209", "id": "pyup.io-58223", "more_info_path": "/vulnerabilities/CVE-2020-15209/58223", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15203: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the 'fill' argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a 'printf' call is constructed. This may result in segmentation fault.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79", "cve": "CVE-2020-15203", "id": "pyup.io-58225", "more_info_path": "/vulnerabilities/CVE-2020-15203/58225", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 include a fix for CVE-2020-15204: In eager mode, TensorFlow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling \"tf.raw_ops.GetSessionHandle\" or \"tf.raw_ops.GetSessionHandleV2\" results in a null pointer dereference In linked snippet, in eager mode, \"ctx->session_state()\" returns \"nullptr\". Since code immediately dereferences this, we get a segmentation fault. The issue was patched in commit 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1", "cve": "CVE-2020-15204", "id": "pyup.io-58216", "more_info_path": "/vulnerabilities/CVE-2020-15204/58216", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15195: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of 'SparseFillEmptyRowsGrad' uses a double indexing pattern. It is possible for 'reverse_index_map(i)' to be an index outside of bounds of 'grad_values', thus resulting in a heap buffer overflow.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-63xm-rx5p-xvqr", "cve": "CVE-2020-15195", "id": "pyup.io-58217", "more_info_path": "/vulnerabilities/CVE-2020-15195/58217", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15207: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses 'ResolveAxis' to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the 'DCHECK' does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34", "cve": "CVE-2020-15207", "id": "pyup.io-58226", "more_info_path": "/vulnerabilities/CVE-2020-15207/58226", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15205: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'data_splits' argument of 'tf.raw_ops.StringNGrams' lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after 'ee ff' are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46", "cve": "CVE-2020-15205", "id": "pyup.io-58224", "more_info_path": "/vulnerabilities/CVE-2020-15205/58224", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15202: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the 'Shard' API in TensorFlow expects the last argument to be a function taking two 'int64' (i.e., 'long long') arguments. However, there are several places in TensorFlow where a lambda taking 'int' or 'int32' arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4", "cve": "CVE-2020-15202", "id": "pyup.io-58222", "more_info_path": "/vulnerabilities/CVE-2020-15202/58222", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0a0,<2.1.2", ">=2.2.0a0,<2.2.1", ">=2.3.0a0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0a0,<2.1.2,>=2.2.0a0,<2.2.1,>=2.3.0a0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13871.", "cve": "CVE-2020-13871", "id": "pyup.io-58206", "more_info_path": "/vulnerabilities/CVE-2020-13871/58206", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11656.", "cve": "CVE-2020-11656", "id": "pyup.io-58211", "more_info_path": "/vulnerabilities/CVE-2020-11656/58211", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-11655.", "cve": "CVE-2020-11655", "id": "pyup.io-58210", "more_info_path": "/vulnerabilities/CVE-2020-11655/58210", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13434.", "cve": "CVE-2020-13434", "id": "pyup.io-58208", "more_info_path": "/vulnerabilities/CVE-2020-13434/58208", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13435.", "cve": "CVE-2020-13435", "id": "pyup.io-58213", "more_info_path": "/vulnerabilities/CVE-2020-13435/58213", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 update its dependency \"SQLite\" to handle CVE-2020-9327.", "cve": "CVE-2020-9327", "id": "pyup.io-58209", "more_info_path": "/vulnerabilities/CVE-2020-9327/58209", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13631.", "cve": "CVE-2020-13631", "id": "pyup.io-58212", "more_info_path": "/vulnerabilities/CVE-2020-13631/58212", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2 and 2.2.1 updates its dependency \"SQLite\" to handle CVE-2020-13630.", "cve": "CVE-2020-13630", "id": "pyup.io-58207", "more_info_path": "/vulnerabilities/CVE-2020-13630/58207", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1" }, { "advisory": "Tensorflow-rocm-enhanced 2.4.0 includes a fix for CVE-2020-15194: In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments. Although `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\"", "cve": "CVE-2020-15194", "id": "pyup.io-58215", "more_info_path": "/vulnerabilities/CVE-2020-15194/58215", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 include a fix for CVE-2020-15210: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x9j7-x98r-r4w2", "cve": "CVE-2020-15210", "id": "pyup.io-58214", "more_info_path": "/vulnerabilities/CVE-2020-15210/58214", "specs": [ "<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": "<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency \"PCRE\" to fix CVE-2019-20838.", "cve": "CVE-2019-20838", "id": "pyup.io-58192", "more_info_path": "/vulnerabilities/CVE-2019-20838/58192", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.5, 2.0.4, 2.1.3, 2.2.2 and 2.3.2 update its dependency \"PCRE\" to handle CVE-2020-14155.", "cve": "CVE-2020-14155", "id": "pyup.io-58194", "more_info_path": "/vulnerabilities/CVE-2020-14155/58194", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 updates its dependency \"Libjpeg-turbo\" to handle CVE-2020-13790.", "cve": "CVE-2020-13790", "id": "pyup.io-58195", "more_info_path": "/vulnerabilities/CVE-2020-13790/58195", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.3.2, 2.2.2, 2.1.3, 2.0.4 and 1.15.5 update its dependency 'Junit4' to v4.13.1 to include a security fix.", "cve": "CVE-2020-15250", "id": "pyup.io-58193", "more_info_path": "/vulnerabilities/CVE-2020-15250/58193", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26270: In affected versions, running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.", "cve": "CVE-2020-26270", "id": "pyup.io-58200", "more_info_path": "/vulnerabilities/CVE-2020-26270/58200", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26267: In affected versions, the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes.", "cve": "CVE-2020-26267", "id": "pyup.io-58197", "more_info_path": "/vulnerabilities/CVE-2020-26267/58197", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26271: In affected versions, under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library.", "cve": "CVE-2020-26271", "id": "pyup.io-58196", "more_info_path": "/vulnerabilities/CVE-2020-26271/58196", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0 includes a fix for CVE-2020-26266: In affected versions and under certain cases a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers filled with the default value of the type but forgetting to default initialize the quantized floating point types in Eigen.", "cve": "CVE-2020-26266", "id": "pyup.io-58198", "more_info_path": "/vulnerabilities/CVE-2020-26266/58198", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 and 2.4.0 includes a fix for CVE-2020-26268: In affected versions, the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden.", "cve": "CVE-2020-26268", "id": "pyup.io-58199", "more_info_path": "/vulnerabilities/CVE-2020-26268/58199", "specs": [ "<1.15.5", ">=2.0.0a0,<2.0.4", ">=2.1.0rc0,<2.1.3", ">=2.2.0rc0,<2.2.2", ">=2.3.0rc0,<2.3.2", ">=2.4.0rc0,<2.4.0" ], "v": "<1.15.5,>=2.0.0a0,<2.0.4,>=2.1.0rc0,<2.1.3,>=2.2.0rc0,<2.2.2,>=2.3.0rc0,<2.3.2,>=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29567: Due to lack of validation in 'tf.raw_ops.SparseDenseCwiseMul', an attacker can trigger denial of service via 'CHECK'-fails or accesses to outside the bounds of heap allocated data. Since the implementation (https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80), it only validates the rank of the input arguments but no constraints between dimensions (https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul) and an attacker can abuse them to trigger internal 'CHECK' assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers.", "cve": "CVE-2021-29567", "id": "pyup.io-58240", "more_info_path": "/vulnerabilities/CVE-2021-29567/58240", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29534: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.SparseConcat'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/b432a38fe0e1b4b904a6c222cbce794c39703e87/tensorflow/core/kernels/sparse_concat_op.cc#L76) takes the values specified in 'shapes[0]' as dimensions for the output shape. The 'TensorShape' constructor (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a 'CHECK' operation which triggers when 'InitDims' (https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status. This is a legacy implementation of the constructor and operations should use 'BuildTensorShapeBase' or 'AddDimWithStatus' to prevent 'CHECK'-failures in the presence of overflows.", "cve": "CVE-2021-29534", "id": "pyup.io-58161", "more_info_path": "/vulnerabilities/CVE-2021-29534/58161", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29552: An attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar. Since the tensor is empty the `CHECK` involved in `.scalar()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination.", "cve": "CVE-2021-29552", "id": "pyup.io-58157", "more_info_path": "/vulnerabilities/CVE-2021-29552/58157", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29539: TensorFlow is an end-to-end open source platform for machine learning. Calling `tf.raw_ops.ImmutableConst`(https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars. We have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. If using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument.", "cve": "CVE-2021-29539", "id": "pyup.io-58169", "more_info_path": "/vulnerabilities/CVE-2021-29539/58169", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a 'CHECK'-fail in 'tf.raw_ops.EncodePng'. See CVE-2021-29531.", "cve": "CVE-2021-29531", "id": "pyup.io-58163", "more_info_path": "/vulnerabilities/CVE-2021-29531/58163", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29532: An attacker can force accesses outside the bounds of heap allocated arrays by passing in invalid tensor values to `tf.raw_ops.RaggedCross`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/efea03b38fb8d3b81762237dc85e579cc5fc6e87/tensorflow/core/kernels/ragged_cross_op.cc#L456-L487) lacks validation for the user supplied arguments. Each of the above branches call a helper function after accessing array elements via a `*_list[next_*]` pattern, followed by incrementing the `next_*` index. However, as there is no validation that the `next_*` values are in the valid range for the corresponding `*_list` arrays, this results in heap OOB reads.", "cve": "CVE-2021-29532", "id": "pyup.io-58152", "more_info_path": "/vulnerabilities/CVE-2021-29532/58152", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 includes a fix for CVE-2021-29533: An attacker can trigger a denial of service via a 'CHECK' failure by passing an empty image to 'tf.raw_ops.DrawBoundingBoxes'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/ea34a18dc3f5c8d80a40ccca1404f343b5d55f91/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L148-L165) uses 'CHECK_*' assertions instead of 'OP_REQUIRES' to validate user controlled inputs. Whereas 'OP_REQUIRES' allows returning an error condition back to the user, the 'CHECK_*' macros result in a crash if the condition is false, similar to 'assert'. In this case, 'height' is 0 from the 'images' input. This results in 'max_box_row_clamp' being negative and the assertion being falsified, followed by aborting program execution.", "cve": "CVE-2021-29533", "id": "pyup.io-58159", "more_info_path": "/vulnerabilities/CVE-2021-29533/58159", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29549: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero. Since `vector_num_elements` is determined based on input shapes (https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L522-L544), a user can trigger scenarios where this quantity is 0.", "cve": "CVE-2021-29549", "id": "pyup.io-58166", "more_info_path": "/vulnerabilities/CVE-2021-29549/58166", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a segfault in 'SparseCountSparseOutput'. See CVE-2021-29521.", "cve": "CVE-2021-29521", "id": "pyup.io-58164", "more_info_path": "/vulnerabilities/CVE-2021-29521/58164", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix vulnerabilities where session operations in eager mode lead to null pointer dereferences. See CVE-2021-29518.", "cve": "CVE-2021-29518", "id": "pyup.io-58154", "more_info_path": "/vulnerabilities/CVE-2021-29518/58154", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29513: Calling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences. The conversion from Python array to C++ array (https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion.", "cve": "CVE-2021-29513", "id": "pyup.io-58162", "more_info_path": "/vulnerabilities/CVE-2021-29513/58162", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix vulnerabilities caused by invalid validation in 'SparseMatrixSparseCholesky'. See CVE-2021-29530.", "cve": "CVE-2021-29530", "id": "pyup.io-58148", "more_info_path": "/vulnerabilities/CVE-2021-29530/58148", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'Conv3DBackprop*'. See CVE-2021-29522.", "cve": "CVE-2021-29522", "id": "pyup.io-58151", "more_info_path": "/vulnerabilities/CVE-2021-29522/58151", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'Conv2DBackpropInput'. See CVE-2021-29525.", "cve": "CVE-2021-29525", "id": "pyup.io-58149", "more_info_path": "/vulnerabilities/CVE-2021-29525/58149", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix fixes a heap buffer overflow caused by rounding. See CVE-2021-29529.", "cve": "CVE-2021-29529", "id": "pyup.io-58156", "more_info_path": "/vulnerabilities/CVE-2021-29529/58156", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'Conv2DBackpropFilter'. See CVE-2021-29524.", "cve": "CVE-2021-29524", "id": "pyup.io-58153", "more_info_path": "/vulnerabilities/CVE-2021-29524/58153", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.4.2, 2.3.3, 2.2.3 and 2.1.4 include a fix for CVE-2021-29548: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the op's contract (https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization).", "cve": "CVE-2021-29548", "id": "pyup.io-58158", "more_info_path": "/vulnerabilities/CVE-2021-29548/58158", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a 'CHECK'-fail in 'SparseCross' caused by type confusion. See CVE-2021-29519.", "cve": "CVE-2021-29519", "id": "pyup.io-58150", "more_info_path": "/vulnerabilities/CVE-2021-29519/58150", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29537: An attacker can cause a heap buffer overflow in `QuantizedResizeBilinear` by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/50711818d2e61ccce012591eeb4fdf93a8496726/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L705-L706) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly.", "cve": "CVE-2021-29537", "id": "pyup.io-58167", "more_info_path": "/vulnerabilities/CVE-2021-29537/58167", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29538: An attacker can cause a division by zero to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments). If all shapes are empty then 'work_unit_size' is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service.", "cve": "CVE-2021-29538", "id": "pyup.io-58165", "more_info_path": "/vulnerabilities/CVE-2021-29538/58165", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a 'CHECK'-fail in 'AddManySparseToTensorsMap'. See CVE-2021-29523.", "cve": "CVE-2021-29523", "id": "pyup.io-58155", "more_info_path": "/vulnerabilities/CVE-2021-29523/58155", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap buffer overflow in 'Conv3DBackprop*'. See CVE-2021-29520.", "cve": "CVE-2021-29520", "id": "pyup.io-58160", "more_info_path": "/vulnerabilities/CVE-2021-29520/58160", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a stack overflow in 'ParseAttrValue' with nested tensors. See CVE-2021-29615.", "cve": "CVE-2021-29615", "id": "pyup.io-58168", "more_info_path": "/vulnerabilities/CVE-2021-29615/58168", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a null pointer dereference in 'StringNGrams'. See CVE-2021-29541.", "cve": "CVE-2021-29541", "id": "pyup.io-58146", "more_info_path": "/vulnerabilities/CVE-2021-29541/58146", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29535: An attacker can cause a heap buffer overflow in 'QuantizedMul' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/87cf4d3ea9949051e50ca3f071fc909538a51cd0/tensorflow/core/kernels/quantized_mul_op.cc#L287-L290) assumes that the 4 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29535", "id": "pyup.io-58147", "more_info_path": "/vulnerabilities/CVE-2021-29535/58147", "specs": [ "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": "<2.1.4,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap buffer overflow in 'StringNGrams'. See CVE-2021-29542.", "cve": "CVE-2021-29542", "id": "pyup.io-58145", "more_info_path": "/vulnerabilities/CVE-2021-29542/58145", "specs": [ "<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": "<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29536: An attacker can cause a heap buffer overflow in 'QuantizedReshape' by passing in invalid thresholds for the quantization. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/a324ac84e573fba362a5e53d4e74d5de6729933e/tensorflow/core/kernels/quantized_reshape_op.cc#L38-L55) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then '.flat()' is an empty buffer and accessing the element at position 0 results in overflow.", "cve": "CVE-2021-29536", "id": "pyup.io-58144", "more_info_path": "/vulnerabilities/CVE-2021-29536/58144", "specs": [ "<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3" ], "v": "<2.1.4,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29544: An attacker can trigger a denial of service via a 'CHECK'-fail in 'tf.raw_ops.QuantizeAndDequantizeV4Grad'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the 'input_*' tensors. In turn, this results in the tensors being passes as they are to 'QuantizeAndDequantizePerChannelGradientImpl' (https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306). However, the 'vec' method, requires the rank to 1 and triggers a 'CHECK' failure otherwise.", "cve": "CVE-2021-29544", "id": "pyup.io-58143", "more_info_path": "/vulnerabilities/CVE-2021-29544/58143", "specs": [ "<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": "<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29543: An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks.", "cve": "CVE-2021-29543", "id": "pyup.io-58142", "more_info_path": "/vulnerabilities/CVE-2021-29543/58142", "specs": [ "<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": "<2.1.4,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29540: TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow to occur in 'Conv2DBackpropFilter'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L495-L497) computes the size of the filter tensor but does not validate that it matches the number of elements in 'filter_sizes'. Later, when reading/writing to this buffer, code uses the value computed here, instead of the number of elements in the tensor.", "cve": "CVE-2021-29540", "id": "pyup.io-58141", "more_info_path": "/vulnerabilities/CVE-2021-29540/58141", "specs": [ "<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": "<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37668:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.UnravelIndex\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by \"dims\" is not empty. Hence, if one element of \"dims\" is 0, the implementation does a division by 0. The Tensorflow team has patched the issue in GitHub commit a776040a5e7ebf76eeb7eb923bf1ae417dd4d233.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-2wmv-37vq-52g5\nhttps://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233", "cve": "CVE-2021-37668", "id": "pyup.io-58044", "more_info_path": "/vulnerabilities/CVE-2021-37668/58044", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37657: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. The Tensorflow team has checked that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit f2a673bd34f0d64b8e40a551ac78989d16daad09.", "cve": "CVE-2021-37657", "id": "pyup.io-58043", "more_info_path": "/vulnerabilities/CVE-2021-37657/58043", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37662: In affected versions an attacker can generate undefined behavior via a reference binding to nullptr in 'BoostedTreesCalculateBestGainsPerFeature' and similar attack can occur in 'BoostedTreesCalculateBestFeatureSplitV2'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values. The Tensorflow team has patched the issue in GitHub commit 9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad and in commit 429f009d2b2c09028647dd4bb7b3f6f414bbaad7.", "cve": "CVE-2021-37662", "id": "pyup.io-58036", "more_info_path": "/vulnerabilities/CVE-2021-37662/58036", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37646: In affected versions the implementation of 'tf.raw_ops.StringNGrams' is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls 'reserve' on a 'tstring' with a value that sometimes can be negative if user supplies negative 'ngram_widths'. The 'reserve' method calls 'TF_TString_Reserve' which has an 'unsigned long' argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5.", "cve": "CVE-2021-37646", "id": "pyup.io-58041", "more_info_path": "/vulnerabilities/CVE-2021-37646/58041", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37685: In affected versions TFLite's 'expand_dims.cc' (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data. If 'axis' is a large negative value (e.g., '-100000'), then after the first 'if' it would still be negative. The check following the 'if' statement will pass and the 'for' loop would read one element before the start of 'input_dims.data' (when 'i = 0'). The Tensorflow team has patched the issue in GitHub commit d94ffe08a65400f898241c0374e9edc6fa8ed257.", "cve": "CVE-2021-37685", "id": "pyup.io-58046", "more_info_path": "/vulnerabilities/CVE-2021-37685/58046", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37687: In affected versions TFLite's 'GatherNd' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation. Hence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in 'indices'. Similar issue exists in 'Gather' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc). The Tensorflow team has patched the issue in GitHub commits bb6a0383ed553c286f87ca88c207f6774d5c4a8f and eb921122119a6b6e470ee98b89e65d721663179d.", "cve": "CVE-2021-37687", "id": "pyup.io-58050", "more_info_path": "/vulnerabilities/CVE-2021-37687/58050", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37643: If a user does not provide a valid padding value to 'tf.raw_ops.MatrixDiagPartOp', then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from. The Tensorflow team has patched the issue in GitHub commit 482da92095c4d48f8784b1f00dda4f81c28d2988.", "cve": "CVE-2021-37643", "id": "pyup.io-58037", "more_info_path": "/vulnerabilities/CVE-2021-37643/58037", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37644: In affected versions providing a negative element to 'num_elements' list argument of 'tf.raw_ops.TensorListReserve' causes the runtime to abort the process due to reallocating a 'std::vector' to have a negative number of elements. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls 'std::vector.resize()' with the new size controlled by input given by the user, without checking that this input is valid. The Tensorflow team has patched the issue in GitHub commit 8a6e874437670045e6c7dc6154c7412b4a2135e2.", "cve": "CVE-2021-37644", "id": "pyup.io-58040", "more_info_path": "/vulnerabilities/CVE-2021-37644/58040", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37660: In affected versions an attacker can cause a floating point exception by calling inplace operations with crafted arguments that would result in a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/inplace_ops.cc#L283) has a logic error: it should skip processing if 'x' and 'v' are empty but the code uses '||' instead of '&&'. The Tensorflow team has patched the issue in GitHub commit e86605c0a336c088b638da02135ea6f9f6753618.", "cve": "CVE-2021-37660", "id": "pyup.io-58053", "more_info_path": "/vulnerabilities/CVE-2021-37660/58053", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37641: In affected versions if the arguments to 'tf.raw_ops.RaggedGather' don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by 'params_nested_splits' is not an empty list of tensors. The Tensorflow team has patched the issue in GitHub commit a2b743f6017d7b97af1fe49087ae15f0ac634373.", "cve": "CVE-2021-37641", "id": "pyup.io-58038", "more_info_path": "/vulnerabilities/CVE-2021-37641/58038", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37663:\nIn affected versions, due to incomplete validation in \"tf.raw_ops.QuantizeV2\", an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that \"min_range\" and \"max_range\" both have the same non-zero number of elements. If \"axis\" is provided (i.e., not \"-1\"), then validation should check that it is a value in range for the rank of \"input\" tensor and then the lengths of \"min_range\" and \"max_range\" inputs match the \"axis\" dimension of the \"input\" tensor. The Tensorflow team has patched the issue in GitHub commit 6da6620efad397c85493b8f8667b821403516708. \nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g25h-jr74-qp5j\nhttps://github.com/tensorflow/tensorflow/commit/6da6620efad397c85493b8f8667b821403516708", "cve": "CVE-2021-37663", "id": "pyup.io-58045", "more_info_path": "/vulnerabilities/CVE-2021-37663/58045", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37684: In affected versions the implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695 (https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).", "cve": "CVE-2021-37684", "id": "pyup.io-58035", "more_info_path": "/vulnerabilities/CVE-2021-37684/58035", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37661: In affected versions an attacker can cause a denial of service in 'boosted_trees_create_quantile_stream_resource' by using negative arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that 'num_streams' only contains non-negative numbers. In turn, this results in using this value to allocate memory (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40). However, 'reserve' receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library. The Tensorflow team has patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992.", "cve": "CVE-2021-37661", "id": "pyup.io-58047", "more_info_path": "/vulnerabilities/CVE-2021-37661/58047", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37665:\nIn affected versions, due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the \"input\" tensor. A similar issue occurs in \"MklRequantizePerChannelOp\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments. The Tensorflow team has patched the issue in GitHub commit 9e62869465573cb2d9b5053f1fa02a81fce21d69 and in the Github commit 203214568f5bc237603dbab6e1fd389f1572f5c9.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-v82p-hv3v-p6qp\nhttps://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9\nhttps://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69", "cve": "CVE-2021-37665", "id": "pyup.io-58048", "more_info_path": "/vulnerabilities/CVE-2021-37665/58048", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37681: In affected versions the implementation of SVDF in TFLite is vulnerable to a null pointer error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313). The 'GetVariableInput' function (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but 'GetTensorData' assumes that the argument is always a valid tensor. Furthermore, because 'GetVariableInput' calls 'GetMutableInput' (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return 'nullptr', the 'tensor->is_variable' expression can also trigger a null pointer exception. The Tensorflow team has patched the issue in GitHub commit 5b048e87e4e55990dae6b547add4dae59f4e1c76.", "cve": "CVE-2021-37681", "id": "pyup.io-58039", "more_info_path": "/vulnerabilities/CVE-2021-37681/58039", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37676: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.SparseFillEmptyRows'. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors. The Tensorflow team has patched the issue in GitHub commit 578e634b4f1c1c684d4b4294f9e5281b2133b3ed.", "cve": "CVE-2021-37676", "id": "pyup.io-58051", "more_info_path": "/vulnerabilities/CVE-2021-37676/58051", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37675: In affected versions most implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations. The Tensorflow team has patched the issue in GitHub commit 8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4.", "cve": "CVE-2021-37675", "id": "pyup.io-58049", "more_info_path": "/vulnerabilities/CVE-2021-37675/58049", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37666: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToVariant'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty. The Tensorflow team has patched the issue in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612.", "cve": "CVE-2021-37666", "id": "pyup.io-58042", "more_info_path": "/vulnerabilities/CVE-2021-37666/58042", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37653: In affected versions an attacker can trigger a crash via a floating point exception in 'tf.raw_ops.ResourceGather'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, 'batch_size', and then divides by it without checking that this value is not 0. The Tensorflow team has patched the issue in GitHub commit ac117ee8a8ea57b73d34665cdf00ef3303bc0b11.", "cve": "CVE-2021-37653", "id": "pyup.io-58052", "more_info_path": "/vulnerabilities/CVE-2021-37653/58052", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37689: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. This is caused by the MLIR optimization of 'L2NormalizeReduceAxis' operator. The implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/compiler/mlir/lite/transforms/optimize.cc#L67-L70) unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements. The Tensorflow team has patched the issue in GitHub commit d6b57f461b39fd1aa8c1b870f1b974aac3554955.", "cve": "CVE-2021-37689", "id": "pyup.io-58183", "more_info_path": "/vulnerabilities/CVE-2021-37689/58183", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37637: It is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid. The Tensorflow team has patched the issue in GitHub commit 5dc7f6981fdaf74c8c5be41f393df705841fb7c5.", "cve": "CVE-2021-37637", "id": "pyup.io-58188", "more_info_path": "/vulnerabilities/CVE-2021-37637/58188", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37636: In affected versions the implementation of 'tf.raw_ops.SparseDenseCwiseDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L56) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit d9204be9f49520cdaaeb2541d1dc5187b23f31d9.", "cve": "CVE-2021-37636", "id": "pyup.io-58190", "more_info_path": "/vulnerabilities/CVE-2021-37636/58190", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37642: In affected versions the implementation of 'tf.raw_ops.ResourceScatterDiv' is vulnerable to a division by 0 error. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately. The Tensorflow team has patched the issue in GitHub commit 4aacb30888638da75023e6601149415b39763d76.", "cve": "CVE-2021-37642", "id": "pyup.io-58191", "more_info_path": "/vulnerabilities/CVE-2021-37642/58191", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37654: In affected versions an attacker can trigger a crash via a 'CHECK'-fail in debug builds of TensorFlow using 'tf.raw_ops.ResourceGather' or a read from outside the bounds of heap allocated data in the same API in a release build. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the 'batch_dims' value that the user supplies is less than the rank of the input tensor. Since the implementation uses several for loops over the dimensions of 'tensor', this results in reading data from outside the bounds of heap allocated buffer backing the tensor. The Tensorflow team has patched the issue in GitHub commit bc9c546ce7015c57c2f15c168b3d9201de679a1d.", "cve": "CVE-2021-37654", "id": "pyup.io-58173", "more_info_path": "/vulnerabilities/CVE-2021-37654/58173", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37651: In affected versions the implementation for 'tf.raw_ops.FractionalAvgPoolGrad' can be tricked into accessing data outside of bounds of heap allocated buffers. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty 'EigenDoubleMatrixMap' and then accesses this buffer with indices that are outside of the empty area. The Tensorflow team has patched the issue in GitHub commit 0f931751fb20f565c4e94aa6df58d54a003cdb30.", "cve": "CVE-2021-37651", "id": "pyup.io-58174", "more_info_path": "/vulnerabilities/CVE-2021-37651/58174", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37648: In affected versions the code for 'tf.raw_ops.SaveV2' does not properly validate the inputs and an attacker can trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses 'ValidateInputs' to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above. However, the validation uses 'OP_REQUIRES' which translates to setting the 'Status' object of the current 'OpKernelContext' to an error status, followed by an empty 'return' statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the nQext line in 'Compute' that follows the call to 'ValidateInputs'. This is equivalent to lacking the validation. The Tensorflow team has patched the issue in GitHub commit 9728c60e136912a12d99ca56e106b7cce7af5986.", "cve": "CVE-2021-37648", "id": "pyup.io-58184", "more_info_path": "/vulnerabilities/CVE-2021-37648/58184", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37635: In affected versions the implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data. The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor. The Tensorflow team has patched the issue in GitHub commit 87158f43f05f2720a374f3e6d22a7aaa3a33f750.", "cve": "CVE-2021-37635", "id": "pyup.io-58185", "more_info_path": "/vulnerabilities/CVE-2021-37635/58185", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37656: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.RaggedTensorToSparse'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order. The Tensorflow team has patched the issue in GitHub commit 1071f554dbd09f7e101324d366eec5f4fe5a3ece.", "cve": "CVE-2021-37656", "id": "pyup.io-58175", "more_info_path": "/vulnerabilities/CVE-2021-37656/58175", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37658: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type 'tf.raw_ops.MatrixSetDiagV*'. The implementation (https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of 'k' is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. The Tensorflow team has patched the issue in GitHub commit ff8894044dfae5568ecbf2ed514c1a37dc394f1b.", "cve": "CVE-2021-37658", "id": "pyup.io-58177", "more_info_path": "/vulnerabilities/CVE-2021-37658/58177", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37683: In affected versions the implementation of division in TFLite is vulnerable to a division by 0 error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc). There is no check that the divisor tensor does not contain zero elements. The Tensorflow team has patched the issue in GitHub commit 1e206baedf8bef0334cca3eb92bab134ef525a28.", "cve": "CVE-2021-37683", "id": "pyup.io-58187", "more_info_path": "/vulnerabilities/CVE-2021-37683/58187", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37649: The code for 'tf.raw_ops.UncompressElement' can be made to trigger a null pointer dereference. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a 'CompressedElement' from a 'Variant' tensor and then proceeds to dereference it for decompressing. There is no check that the 'Variant' tensor contained a 'CompressedElement', so the pointer is actually 'nullptr'. The Tensorflow team has patched the issue in GitHub commit 7bdf50bb4f5c54a4997c379092888546c97c3ebd.", "cve": "CVE-2021-37649", "id": "pyup.io-58178", "more_info_path": "/vulnerabilities/CVE-2021-37649/58178", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37647: When a user does not supply arguments that determine a valid sparse tensor, 'tf.raw_ops.SparseTensorSliceDataset' implementation can be made to dereference a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either 'indices' or 'values' are provided for an empty sparse tensor when the other is not. If 'indices' is empty, then code that performs validation (https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference. If 'indices' as provided by the user is empty, then 'indices' in the C++ code above is backed by an empty 'std::vector', hence calling 'indices->dim_size(0)' results in null pointer dereferencing (same as calling 'std::vector::at()' on an empty vector). The Tensorflow team has patched the issue in GitHub commit 02cc160e29d20631de3859c6653184e3f876b9d7.", "cve": "CVE-2021-37647", "id": "pyup.io-58181", "more_info_path": "/vulnerabilities/CVE-2021-37647/58181", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37680: In affected versions the implementation of fully connected layers in TFLite is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226). The Tensorflow team has patched the issue in GitHub commit 718721986aa137691ee23f03638867151f74935f.", "cve": "CVE-2021-37680", "id": "pyup.io-58189", "more_info_path": "/vulnerabilities/CVE-2021-37680/58189", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37671: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.Map*' and 'tf.raw_ops.OrderedMap*' operations. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that 'indices' is in ascending order, but does not check that 'indices' is not empty. The Tensorflow team has patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac.", "cve": "CVE-2021-37671", "id": "pyup.io-58182", "more_info_path": "/vulnerabilities/CVE-2021-37671/58182", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37667: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in 'tf.raw_ops.UnicodeEncode'. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the 'input_splits' tensor before validating that this tensor is not empty. The Tensorflow team has patched the issue in GitHub commit 2e0ee46f1a47675152d3d865797a18358881d7a6.", "cve": "CVE-2021-37667", "id": "pyup.io-58186", "more_info_path": "/vulnerabilities/CVE-2021-37667/58186", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37652: In affected versions the implementation for 'tf.raw_ops.BoostedTreesCreateEnsemble' can result in a use after free error if an attacker supplies specially crafted arguments. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent 'free'-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed. The Tensorflow team has patched the issue in GitHub commit 5ecec9c6fbdbc6be03295685190a45e7eee726ab.", "cve": "CVE-2021-37652", "id": "pyup.io-58171", "more_info_path": "/vulnerabilities/CVE-2021-37652/58171", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37664: In affected versions an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range. The Tensorflow team has patched the issue in GitHub commit e84c975313e8e8e38bb2ea118196369c45c51378.", "cve": "CVE-2021-37664", "id": "pyup.io-58180", "more_info_path": "/vulnerabilities/CVE-2021-37664/58180", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37659: In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations). The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr. We have patched the issue in GitHub commit 93f428fd1768df147171ed674fee1fc5ab8309ec.", "cve": "CVE-2021-37659", "id": "pyup.io-58179", "more_info_path": "/vulnerabilities/CVE-2021-37659/58179", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37639: When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the 'tensor_name' user controlled input and immediately retrieves the tensor at the restoration index (controlled via 'preferred_shard' argument). This occurs without validating that the provided list has enough values. If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements and if the restoration index is outside the bounds, this results in heap OOB read. The Tensorflow team has patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622.", "cve": "CVE-2021-37639", "id": "pyup.io-58176", "more_info_path": "/vulnerabilities/CVE-2021-37639/58176", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37638: Sending invalid argument for 'row_partition_types' of 'tf.raw_ops.RaggedTensorToTensor' API results in a null pointer dereference and undefined behavior. The implementation (https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty. The Tensorflow team has patched the issue in GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314.", "cve": "CVE-2021-37638", "id": "pyup.io-58172", "more_info_path": "/vulnerabilities/CVE-2021-37638/58172", "specs": [ "<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.6.0rc0,<2.6.0" ], "v": "<2.3.4,>=2.4.0rc0,<2.4.3,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.4.0 includes a fix for CVE-2020-15265: In Tensorflow before version 2.4.0, an attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`. This results in accessing a dimension outside the rank of the input tensor in the C++ kernel implementation. However, dim_size only does a DCHECK to validate the argument and then uses it to access the corresponding element of an array. Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.", "cve": "CVE-2020-15265", "id": "pyup.io-58204", "more_info_path": "/vulnerabilities/CVE-2020-15265/58204", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.4.0 includes a fix for CVE-2020-15266: In Tensorflow before version 2.4.0, when the 'boxes' argument of 'tf.image.crop_and_resize' has a very large value, the CPU kernel implementation receives it as a C++ 'nan' floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault.\nhttps://github.com/tensorflow/tensorflow/issues/42129\nhttps://github.com/tensorflow/tensorflow/pull/42143/commits/3ade2efec2e90c6237de32a19680caaa3ebc2845\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-xwhf-g6j5-j5gc", "cve": "CVE-2020-15266", "id": "pyup.io-58202", "more_info_path": "/vulnerabilities/CVE-2020-15266/58202", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.4.3 and prior versions are vulnerable to several security issues (affecting Tensorflow) compromising Confidentiality, Integrity and Availability.", "cve": "PVE-2023-58018", "id": "pyup.io-58018", "more_info_path": "/vulnerabilities/PVE-2023-58018/58018", "specs": [ "<=2.4.3" ], "v": "<=2.4.3" }, { "advisory": "TensorFlow-ROCm-enhanced, optimized for AMD GPUs, continues to ship with a CURL dependency affected by CVE-2023-38546.", "cve": "CVE-2023-38546", "id": "pyup.io-73090", "more_info_path": "/vulnerabilities/CVE-2023-38546/73090", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "TensorFlow-ROCm-enhanced, optimized for AMD GPUs, continues to ship with a CURL dependency affected by CVE-2023-38545.", "cve": "CVE-2023-38545", "id": "pyup.io-73089", "more_info_path": "/vulnerabilities/CVE-2023-38545/73089", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Tensorflow-rocm-enhanced versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1 updates its dependency \"SQLite\" to handle CVE-2020-15358.", "cve": "CVE-2020-15358", "id": "pyup.io-58227", "more_info_path": "/vulnerabilities/CVE-2020-15358/58227", "specs": [ ">=1.15.0rc0,<1.15.4", ">=2.0.0a0,<2.0.3", ">=2.1.0rc0,<2.1.2", ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=1.15.0rc0,<1.15.4,>=2.0.0a0,<2.0.3,>=2.1.0rc0,<2.1.2,>=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15193: In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of \"dlpack.to_dlpack\" can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing in a Python object instead of a tensor. The uninitialized memory address is due to a \"reinterpret_cast\". Since the \"PyObject\" is a Python object, not a Tensorflow tensor, the cast to \"EagerTensor\" fails. The issue was patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v", "cve": "CVE-2020-15193", "id": "pyup.io-58239", "more_info_path": "/vulnerabilities/CVE-2020-15193/58239", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15212: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to \"segment_ids_data\" can alter \"output_index\" and then write to outside of \"output_data\" buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15212", "id": "pyup.io-58236", "more_info_path": "/vulnerabilities/CVE-2020-15212/58236", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15213: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimension of the output tensor, attackers can use a very large value to trigger a large allocation. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps. However, if the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-hjmq-236j-8m87", "cve": "CVE-2020-15213", "id": "pyup.io-58235", "more_info_path": "/vulnerabilities/CVE-2020-15213/58235", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.2.1 and 2.3.1 includes a fix for CVE-2020-15214: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimension of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue was patched in commit 204945b19e44b57906c9344c0d00120eeeae178a. A potential workaround is to add a custom \"Verifier\" to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.", "cve": "CVE-2020-15214", "id": "pyup.io-58237", "more_info_path": "/vulnerabilities/CVE-2020-15214/58237", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15191: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to 'dlpack.to_dlpack' the expected validations will cause variables to bind to 'nullptr' while setting a 'status' variable to the error condition. However, this 'status' argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with '-fsanitize=null'.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr", "cve": "CVE-2020-15191", "id": "pyup.io-58234", "more_info_path": "/vulnerabilities/CVE-2020-15191/58234", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.2.1 and 2.3.1 include a fix for CVE-2020-15192: In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to 'dlpack.to_dlpack' there is a memory leak following an expected validation failure. The issue occurs because the 'status' argument during validation failures is not properly checked. Since each of the above methods can return an error status, the 'status' value must be checked before continuing.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fxw-76px-3rxv", "cve": "CVE-2020-15192", "id": "pyup.io-58238", "more_info_path": "/vulnerabilities/CVE-2020-15192/58238", "specs": [ ">=2.2.0rc0,<2.2.1", ">=2.3.0rc0,<2.3.1" ], "v": ">=2.2.0rc0,<2.2.1,>=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 update its dependency 'curl' to version 7.76.0 to handle CVE-2020-8169.", "cve": "CVE-2020-8169", "id": "pyup.io-58140", "more_info_path": "/vulnerabilities/CVE-2020-8169/58140", "specs": [ ">=2.2.0rc0,<2.2.3", "<2.1.4", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.2.0rc0,<2.2.3,<2.1.4,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in 'Conv3D'. See CVE-2021-29517.", "cve": "CVE-2021-29517", "id": "pyup.io-58139", "more_info_path": "/vulnerabilities/CVE-2021-29517/58139", "specs": [ ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", "<2.1.4" ], "v": ">=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a reference binding to null pointer in 'MatrixDiag*' ops. See CVE-2021-29515.", "cve": "CVE-2021-29515", "id": "pyup.io-58137", "more_info_path": "/vulnerabilities/CVE-2021-29515/58137", "specs": [ ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", "<2.1.4" ], "v": ">=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix fixes a null pointer dereference via invalid Ragged Tensors. See CVE-2021-29516.", "cve": "CVE-2021-29516", "id": "pyup.io-58138", "more_info_path": "/vulnerabilities/CVE-2021-29516/58138", "specs": [ ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", "<2.1.4" ], "v": ">=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's implementation of 'EmbeddingLookup'. See CVE-2021-29596.", "cve": "CVE-2021-29596", "id": "pyup.io-58136", "more_info_path": "/vulnerabilities/CVE-2021-29596/58136", "specs": [ ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4" ], "v": ">=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's convolution code. See CVE-2021-29594.", "cve": "CVE-2021-29594", "id": "pyup.io-58135", "more_info_path": "/vulnerabilities/CVE-2021-29594/58135", "specs": [ ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4" ], "v": ">=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.1 includes a fix for CVE-2020-15198: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has the same shape as the \"values\" one. The values in these tensors are always accessed in parallel. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3", "cve": "CVE-2020-15198", "id": "pyup.io-58229", "more_info_path": "/vulnerabilities/CVE-2020-15198/58229", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.1 includes a fix for CVE-2020-15200: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Thus, the code sets up conditions to cause a heap buffer overflow. A \"BatchedMap\" is equivalent to a vector where each element is a hashmap. However, if the first element of \"splits_values\" is not 0, \"batch_idx\" will never be 1, hence there will be no hashmap at index 0 in \"per_batch_counts\". Trying to access that in the user code results in a segmentation fault. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x7rp-74x2-mjf3", "cve": "CVE-2020-15200", "id": "pyup.io-58231", "more_info_path": "/vulnerabilities/CVE-2020-15200/58231", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.1 includes a fix for CVE-2020-15201: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the \"splits\" tensor generate a valid partitioning of the \"values\" tensor. Hence, the code is prone to heap buffer overflow. If \"split_values\" does not end with a value at least \"num_values\" then the \"while\" loop condition will trigger a read outside of the bounds of \"split_values\" once \"batch_idx\" grows too large. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4", "cve": "CVE-2020-15201", "id": "pyup.io-58233", "more_info_path": "/vulnerabilities/CVE-2020-15201/58233", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.1 includes a fix for CVE-2020-15197: In Tensorflow before version 2.3.1, the \"SparseCountSparseOutput\" implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the \"indices\" tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix. However, malicious users can pass in tensors of different rank, resulting in a \"CHECK\" assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.", "cve": "CVE-2020-15197", "id": "pyup.io-58228", "more_info_path": "/vulnerabilities/CVE-2020-15197/58228", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.1 includes a fix for CVE-2020-15196: In Tensorflow version 2.3.0, the \"SparseCountSparseOutput\" and \"RaggedCountSparseOutput\" implementations don't validate that the \"weights\" tensor has the same shape as the data. The check exists for \"DenseCountSparseOutput\", where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph", "cve": "CVE-2020-15196", "id": "pyup.io-58230", "more_info_path": "/vulnerabilities/CVE-2020-15196/58230", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.1 includes a fix for CVE-2020-15199: In Tensorflow before version 2.3.1, the \"RaggedCountSparseOutput\" does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the \"splits\" tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure. Since \"BatchedMap\" is equivalent to a vector, it needs to have at least one element to not be \"nullptr\". If user passes a \"splits\" tensor that is empty or has exactly one element, we get a \"SIGABRT\" signal raised by the operating system. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-x5cp-9pcf-pp3h", "cve": "CVE-2020-15199", "id": "pyup.io-58232", "more_info_path": "/vulnerabilities/CVE-2020-15199/58232", "specs": [ ">=2.3.0rc0,<2.3.1" ], "v": ">=2.3.0rc0,<2.3.1" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29558: An attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset.", "cve": "CVE-2021-29558", "id": "pyup.io-58134", "more_info_path": "/vulnerabilities/CVE-2021-29558/58134", "specs": [ ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4", ">=2.4.0rc0,<2.4.2" ], "v": ">=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4,>=2.4.0rc0,<2.4.2" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29551: The implementation of 'MatrixTriangularSolve' (https://github.com/tensorflow/tensorflow/blob/8cae746d8449c7dda5298327353d68613f16e798/tensorflow/core/kernels/linalg/matrix_triangular_solve_op_impl.h#L160-L240) fails to terminate kernel execution if one validation condition fails.", "cve": "CVE-2021-29551", "id": "pyup.io-58132", "more_info_path": "/vulnerabilities/CVE-2021-29551/58132", "specs": [ ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", "<2.1.4" ], "v": ">=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29545: An attacker can trigger a denial of service via a 'CHECK'-fail in converting sparse tensors to CSR Sparse matrices. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/800346f2c03a27e182dd4fba48295f65e7790739/tensorflow/core/kernels/sparse/kernels.cc#L66) does a double redirection to access an element of an array allocated on the heap. If the value at 'indices(i, 0)' is such that 'indices(i, 0) + 1' is outside the bounds of 'csr_row_ptr', this results in writing outside of bounds of heap allocated data.", "cve": "CVE-2021-29545", "id": "pyup.io-58133", "more_info_path": "/vulnerabilities/CVE-2021-29545/58133", "specs": [ ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", ">=2.4.0rc0,<2.4.2", "<2.1.4" ], "v": ">=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,>=2.4.0rc0,<2.4.2,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a null pointer dereference in TFLite's 'Reshape' operator. See CVE-2021-29592.", "cve": "CVE-2021-29592", "id": "pyup.io-58131", "more_info_path": "/vulnerabilities/CVE-2021-29592/58131", "specs": [ ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", "<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a segfault in 'CTCBeamSearchDecoder'. See CVE-2021-29581.", "cve": "CVE-2021-29581", "id": "pyup.io-58127", "more_info_path": "/vulnerabilities/CVE-2021-29581/58127", "specs": [ ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29617: An attacker can cause a denial of service via `CHECK`-fail in `tf.strings.substr` with invalid arguments.", "cve": "CVE-2021-29617", "id": "pyup.io-58128", "more_info_path": "/vulnerabilities/CVE-2021-29617/58128", "specs": [ ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix an undefined behavior in 'MaxPool3DGradGrad'. See CVE-2021-29574.", "cve": "CVE-2021-29574", "id": "pyup.io-58130", "more_info_path": "/vulnerabilities/CVE-2021-29574/58130", "specs": [ ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29512: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433). Before the 'for' loop, 'batch_idx' is set to 0. The user controls the 'splits' array, making it contain only one element, 0. Thus, the code in the 'while' loop would increment 'batch_idx' and then try to read 'splits(1)', which is outside of bounds.", "cve": "CVE-2021-29512", "id": "pyup.io-58129", "more_info_path": "/vulnerabilities/CVE-2021-29512/58129", "specs": [ ">=2.3.0rc0,<2.3.3", ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.3.0rc0,<2.3.3,>=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.4.0 includes a fix for CVE-2020-26269: In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.", "cve": "CVE-2020-26269", "id": "pyup.io-58203", "more_info_path": "/vulnerabilities/CVE-2020-26269/58203", "specs": [ ">=2.4.0rc0,<2.4.0" ], "v": ">=2.4.0rc0,<2.4.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix vulnerabilities caused by incomplete validation in 'tf.raw_ops.CTCLoss'. See CVE-2021-29613.", "cve": "CVE-2021-29613", "id": "pyup.io-58126", "more_info_path": "/vulnerabilities/CVE-2021-29613/58126", "specs": [ ">=2.4.0rc0,<2.4.2", "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.4.0rc0,<2.4.2,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29556: An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.Reverse`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/36229ea9e9451dac14a8b1f4711c435a1d84a594/tensorflow/core/kernels/reverse_op.cc#L75-L76) performs a division based on the first dimension of the tensor argument.", "cve": "CVE-2021-29556", "id": "pyup.io-58125", "more_info_path": "/vulnerabilities/CVE-2021-29556/58125", "specs": [ ">=2.4.0rc0,<2.4.2", "<2.1.4", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.4.0rc0,<2.4.2,<2.1.4,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'Conv2D'. See CVE-2021-29526.", "cve": "CVE-2021-29526", "id": "pyup.io-58124", "more_info_path": "/vulnerabilities/CVE-2021-29526/58124", "specs": [ ">=2.4.0rc0,<2.4.2", "<2.1.4", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.4.0rc0,<2.4.2,<2.1.4,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a 'CHECK'-fail in 'LoadAndRemapMatrix'. See CVE-2021-29561.", "cve": "CVE-2021-29561", "id": "pyup.io-58121", "more_info_path": "/vulnerabilities/CVE-2021-29561/58121", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", "<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'QuantizedConv2D'. See CVE-2021-29527.", "cve": "CVE-2021-29527", "id": "pyup.io-58122", "more_info_path": "/vulnerabilities/CVE-2021-29527/58122", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", "<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29595: The implementation of the `DepthToSpace` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69). An attacker can craft a model such that `params->block_size` is 0.", "cve": "CVE-2021-29595", "id": "pyup.io-58123", "more_info_path": "/vulnerabilities/CVE-2021-29595/58123", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", "<2.1.4", ">=2.3.0rc0,<2.3.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,<2.1.4,>=2.3.0rc0,<2.3.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29585: The TFLite computation for size of output after padding, `ComputeOutSize`(https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division. Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0.", "cve": "CVE-2021-29585", "id": "pyup.io-58120", "more_info_path": "/vulnerabilities/CVE-2021-29585/58120", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.2.0rc0,<2.2.3", ">=2.3.0rc0,<2.3.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.2.0rc0,<2.2.3,>=2.3.0rc0,<2.3.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'SparseMatMul'. See CVE-2021-29557.", "cve": "CVE-2021-29557", "id": "pyup.io-58113", "more_info_path": "/vulnerabilities/CVE-2021-29557/58113", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap OOB access in unicode ops. See CVE-2021-29559.", "cve": "CVE-2021-29559", "id": "pyup.io-58117", "more_info_path": "/vulnerabilities/CVE-2021-29559/58117", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap out of bounds read in 'MaxPoolGradWithArgmax'. See CVE-2021-29570.", "cve": "CVE-2021-29570", "id": "pyup.io-58115", "more_info_path": "/vulnerabilities/CVE-2021-29570/58115", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29589: The reference implementation of the `GatherNd` TFLite operator is vulnerable to a division by zero error (https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/reference_ops.h#L966). An attacker can craft a model such that `params` input would be an empty tensor. In turn, `params_shape.Dims(.)` would be zero, in at least one dimension.", "cve": "CVE-2021-29589", "id": "pyup.io-58116", "more_info_path": "/vulnerabilities/CVE-2021-29589/58116", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'FusedBatchNorm'. See CVE-2021-29555.", "cve": "CVE-2021-29555", "id": "pyup.io-58118", "more_info_path": "/vulnerabilities/CVE-2021-29555/58118", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap buffer overflow in 'BandedTriangularSolve'. See CVE-2021-29612.", "cve": "CVE-2021-29612", "id": "pyup.io-58114", "more_info_path": "/vulnerabilities/CVE-2021-29612/58114", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29514: If the 'splits' argument of 'RaggedBincount' does not specify a valid 'SparseTensor' (https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the 'splits' tensor buffer in the implementation of the 'RaggedBincount' op (https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L446). Before the 'for' loop, 'batch_idx' is set to 0. The attacker sets 'splits(0)' to be 7, hence the 'while' loop does not execute and 'batch_idx' remains 0. This then results in writing to 'out(-1, bin)', which is before the heap allocated buffer for the output tensor.", "cve": "CVE-2021-29514", "id": "pyup.io-58119", "more_info_path": "/vulnerabilities/CVE-2021-29514/58119", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's implementation of 'TransposeConv'. See CVE-2021-29588.", "cve": "CVE-2021-29588", "id": "pyup.io-58112", "more_info_path": "/vulnerabilities/CVE-2021-29588/58112", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", "<2.1.4", ">=2.2.0rc0,<2.2.3" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,<2.1.4,>=2.2.0rc0,<2.2.3" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap OOB read in 'tf.raw_ops.Dequantize'. See CVE-2021-29582.", "cve": "CVE-2021-29582", "id": "pyup.io-58061", "more_info_path": "/vulnerabilities/CVE-2021-29582/58061", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 updates 'curl' to '7.76.0' to handle CVE-2020-8286: curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response.", "cve": "CVE-2020-8286", "id": "pyup.io-58077", "more_info_path": "/vulnerabilities/CVE-2020-8286/58077", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29616: The implementation of TrySimplify (https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/grappler/optimizers/arithmetic_optimizer.cc#L390-L401) has undefined behavior due to dereferencing a null pointer in corner cases that result in optimizing a node with no inputs.", "cve": "CVE-2021-29616", "id": "pyup.io-58068", "more_info_path": "/vulnerabilities/CVE-2021-29616/58068", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29571: The implementation of 'tf.raw_ops.MaxPoolGradWithArgmax' can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation (https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of 'boxes' input is 4, as required by the op (https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption. If the last dimension in 'boxes' is less than 4, accesses similar to 'tboxes(b, bb, 3)' will access data outside of bounds. Further during code execution there are also writes to these indices.", "cve": "CVE-2021-29571", "id": "pyup.io-58093", "more_info_path": "/vulnerabilities/CVE-2021-29571/58093", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a integer overflow in TFLite memory allocation. See CVE-2021-29605.", "cve": "CVE-2021-29605", "id": "pyup.io-58083", "more_info_path": "/vulnerabilities/CVE-2021-29605/58083", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29563: An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`. Eigen code operating on an empty matrix can trigger on an assertion and will cause program termination.", "cve": "CVE-2021-29563", "id": "pyup.io-58102", "more_info_path": "/vulnerabilities/CVE-2021-29563/58102", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a 'CHECK'-fail in 'tf.raw_ops.IRFFT'. See CVE-2021-29562.", "cve": "CVE-2021-29562", "id": "pyup.io-58063", "more_info_path": "/vulnerabilities/CVE-2021-29562/58063", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap buffer overflow in 'FractionalAvgPoolGrad'. See CVE-2021-29578.", "cve": "CVE-2021-29578", "id": "pyup.io-58073", "more_info_path": "/vulnerabilities/CVE-2021-29578/58073", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29618: Passing a complex argument to `tf.transpose` at the same time as passing 'conjugate=True' argument results in a crash.", "cve": "CVE-2021-29618", "id": "pyup.io-58109", "more_info_path": "/vulnerabilities/CVE-2021-29618/58109", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'DenseCountSparseOutput'. See CVE-2021-29554.", "cve": "CVE-2021-29554", "id": "pyup.io-58079", "more_info_path": "/vulnerabilities/CVE-2021-29554/58079", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.1.4, 2.2.3, 2.3.3 and 2.4.2 update its dependency \"curl\" to handle CVE-2020-8284.", "cve": "CVE-2020-8284", "id": "pyup.io-58081", "more_info_path": "/vulnerabilities/CVE-2020-8284/58081", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 update its dependency \"curl\" to v7.76.0 to include security fixes.", "cve": "CVE-2020-8231", "id": "pyup.io-58075", "more_info_path": "/vulnerabilities/CVE-2020-8231/58075", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29587: TensorFlow is an end-to-end open source platform for machine learning. The `Prepare` step of the `SpaceToDepth` TFLite operator does not check for 0 before division (https://github.com/tensorflow/tensorflow/blob/5f7975d09eac0f10ed8a17dbb6f5964977725adc/tensorflow/lite/kernels/space_to_depth.cc#L63-L67). An attacker can craft a model such that `params->block_size` would be zero.", "cve": "CVE-2021-29587", "id": "pyup.io-58091", "more_info_path": "/vulnerabilities/CVE-2021-29587/58091", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29610: The validation in 'tf.raw_ops.QuantizeAndDequantizeV2' allows invalid values for 'axis' argument:. The validation (https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses '||' to mix two different conditions. If 'axis_ < -1' the condition in 'OP_REQUIRES' will still be true, but this value of 'axis_' results in heap underflow. This allows attackers to read/write to other data on the heap.", "cve": "CVE-2021-29610", "id": "pyup.io-58111", "more_info_path": "/vulnerabilities/CVE-2021-29610/58111", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix vulnerabilities caused by incomplete validation in 'SparseSparseMinimum'. See CVE-2021-29607.", "cve": "CVE-2021-29607", "id": "pyup.io-58066", "more_info_path": "/vulnerabilities/CVE-2021-29607/58066", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix fixes a heap OOB read in TFLite. See CVE-2021-29606.", "cve": "CVE-2021-29606", "id": "pyup.io-58062", "more_info_path": "/vulnerabilities/CVE-2021-29606/58062", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap OOB write in TFLite. See CVE-2021-29603.", "cve": "CVE-2021-29603", "id": "pyup.io-58088", "more_info_path": "/vulnerabilities/CVE-2021-29603/58088", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's implementation of 'Split'. See CVE-2021-29599.", "cve": "CVE-2021-29599", "id": "pyup.io-58065", "more_info_path": "/vulnerabilities/CVE-2021-29599/58065", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap buffer overflow in 'MaxPoolGrad'. See CVE-2021-29579.", "cve": "CVE-2021-29579", "id": "pyup.io-58082", "more_info_path": "/vulnerabilities/CVE-2021-29579/58082", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap buffer overflow in 'MaxPool3DGradGrad'. See CVE-2021-29576.", "cve": "CVE-2021-29576", "id": "pyup.io-58084", "more_info_path": "/vulnerabilities/CVE-2021-29576/58084", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.5.0, 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29572: The implementation of `tf.raw_ops.SdcaOptimizer` triggers undefined behavior due to dereferencing a null pointer. The implementation (https://github.com/tensorflow/tensorflow/blob/60a45c8b6192a4699f2e2709a2645a751d435cc3/tensorflow/core/kernels/sdca_internal.cc) does not validate that the user supplied arguments satisfy all constraints expected by the op(https://www.tensorflow.org/api_docs/python/tf/raw_ops/SdcaOptimizer).", "cve": "CVE-2021-29572", "id": "pyup.io-58095", "more_info_path": "/vulnerabilities/CVE-2021-29572/58095", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap out of bounds read in 'RequantizationRange'. See CVE-2021-29569.", "cve": "CVE-2021-29569", "id": "pyup.io-58094", "more_info_path": "/vulnerabilities/CVE-2021-29569/58094", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a null pointer dereference in 'SparseFillEmptyRows'. See CVE-2021-29565.", "cve": "CVE-2021-29565", "id": "pyup.io-58067", "more_info_path": "/vulnerabilities/CVE-2021-29565/58067", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29583: The implementation of 'tf.raw_ops.FusedBatchNorm' is vulnerable to a heap buffer overflow. If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers. The implementation(https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that 'scale', 'offset', 'mean' and 'variance' (the last two only when required) all have the same number of elements as the number of channels of 'x'. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary. If the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior.", "cve": "CVE-2021-29583", "id": "pyup.io-58069", "more_info_path": "/vulnerabilities/CVE-2021-29583/58069", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a null pointer dereference in 'EditDistance'. See CVE-2021-29564.", "cve": "CVE-2021-29564", "id": "pyup.io-58086", "more_info_path": "/vulnerabilities/CVE-2021-29564/58086", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a stack overflow due to looping TFLite subgraph. See CVE-2021-29591.", "cve": "CVE-2021-29591", "id": "pyup.io-58059", "more_info_path": "/vulnerabilities/CVE-2021-29591/58059", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix vulnerabilities caused by incomplete validation in 'SparseAdd'. See CVE-2021-29609.", "cve": "CVE-2021-29609", "id": "pyup.io-58071", "more_info_path": "/vulnerabilities/CVE-2021-29609/58071", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's implementation of 'OneHot'. See CVE-2021-29600.", "cve": "CVE-2021-29600", "id": "pyup.io-58085", "more_info_path": "/vulnerabilities/CVE-2021-29600/58085", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a 'CHECK'-fail due to integer overflow. See CVE-2021-29584.", "cve": "CVE-2021-29584", "id": "pyup.io-58058", "more_info_path": "/vulnerabilities/CVE-2021-29584/58058", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix an overflow and a denial of service in 'tf.raw_ops.ReverseSequence'. See CVE-2021-29575.", "cve": "CVE-2021-29575", "id": "pyup.io-58060", "more_info_path": "/vulnerabilities/CVE-2021-29575/58060", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a integer overflow in TFLite concatentation. See CVE-2021-29601.", "cve": "CVE-2021-29601", "id": "pyup.io-58097", "more_info_path": "/vulnerabilities/CVE-2021-29601/58097", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap buffer overflow in 'AvgPool3DGrad'. See CVE-2021-29577.", "cve": "CVE-2021-29577", "id": "pyup.io-58080", "more_info_path": "/vulnerabilities/CVE-2021-29577/58080", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix vulnerabilities caused by incomplete validation in 'SparseReshape'. See CVE-2021-29611.", "cve": "CVE-2021-29611", "id": "pyup.io-58105", "more_info_path": "/vulnerabilities/CVE-2021-29611/58105", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'MaxPoolGradWithArgmax'. See CVE-2021-29573.", "cve": "CVE-2021-29573", "id": "pyup.io-58098", "more_info_path": "/vulnerabilities/CVE-2021-29573/58098", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in optimized pooling implementations in TFLite. See CVE-2021-29586.", "cve": "CVE-2021-29586", "id": "pyup.io-58099", "more_info_path": "/vulnerabilities/CVE-2021-29586/58099", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap OOB read in TFLite's implementation of 'Minimum' or 'Maximum'. See CVE-2021-29590.", "cve": "CVE-2021-29590", "id": "pyup.io-58100", "more_info_path": "/vulnerabilities/CVE-2021-29590/58100", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by 0 in 'QuantizedMul'. See CVE-2021-29528.", "cve": "CVE-2021-29528", "id": "pyup.io-58103", "more_info_path": "/vulnerabilities/CVE-2021-29528/58103", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29608: TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in 'tf.raw_ops.RaggedTensorToTensor', an attacker can exploit an undefined behavior if input arguments are empty. The implementation (https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones. There are multiple 'DCHECK' validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything.", "cve": "CVE-2021-29608", "id": "pyup.io-58070", "more_info_path": "/vulnerabilities/CVE-2021-29608/58070", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29546: TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger an integer division by zero undefined behavior in `tf.raw_ops.QuantizedBiasAdd`. This is because the implementation of the Eigen kernel (https://github.com/tensorflow/tensorflow/blob/61bca8bd5ba8a68b2d97435ddfafcdf2b85672cd/tensorflow/core/kernels/quantization_utils.h#L812-L849) does a division by the number of elements of the smaller input (based on shape) without checking that this is not zero.", "cve": "CVE-2021-29546", "id": "pyup.io-58108", "more_info_path": "/vulnerabilities/CVE-2021-29546/58108", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29560: An attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel. Since the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when 'parent_output_index' is shorter than 'row_split'.", "cve": "CVE-2021-29560", "id": "pyup.io-58110", "more_info_path": "/vulnerabilities/CVE-2021-29560/58110", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a heap OOB in 'QuantizeAndDequantizeV3'. See CVE-2021-29553.", "cve": "CVE-2021-29553", "id": "pyup.io-58104", "more_info_path": "/vulnerabilities/CVE-2021-29553/58104", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's implementation of 'SpaceToBatchNd'. See CVE-2021-29597.", "cve": "CVE-2021-29597", "id": "pyup.io-58064", "more_info_path": "/vulnerabilities/CVE-2021-29597/58064", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's implementation of 'BatchToSpaceNd'. See CVE-2021-29593.", "cve": "CVE-2021-29593", "id": "pyup.io-58078", "more_info_path": "/vulnerabilities/CVE-2021-29593/58078", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a segfault in 'tf.raw_ops.SparseCountSparseOutput'. See CVE-2021-29619.", "cve": "CVE-2021-29619", "id": "pyup.io-58072", "more_info_path": "/vulnerabilities/CVE-2021-29619/58072", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29566: An attacker can write outside the bounds of heap allocated arrays by passing invalid arguments to 'tf.raw_ops.Dilation2DBackpropInput'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/afd954e65f15aea4d438d0a219136fc4a63a573d/tensorflow/core/kernels/dilation_ops.cc#L321-L322) does not validate before writing to the output array. The values for 'h_out' and 'w_out' are guaranteed to be in range for 'out_backprop' (as they are loop indices bounded by the size of the array). However, there are no similar guarantees relating 'h_in_max'/'w_in_max' and 'in_backprop'.", "cve": "CVE-2021-29566", "id": "pyup.io-58090", "more_info_path": "/vulnerabilities/CVE-2021-29566/58090", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.5.0, 2.4.2, 2.3.3, 2.2.3 and 2.1.4 updates its dependency \"curl\" to a secure version (7.76.0).", "cve": "CVE-2020-8285", "id": "pyup.io-58096", "more_info_path": "/vulnerabilities/CVE-2020-8285/58096", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29550: An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values. The user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor operation results in `output_size[i]` being 0. The `DCHECK_GT` line is a no-op outside of debug mode, so in released versions of TF this does not trigger. Later, these computed values are used as arguments (https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to `GeneratePoolingSequence`(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation. Since `output_length` can be 0, this results in runtime crashing.", "cve": "CVE-2021-29550", "id": "pyup.io-58107", "more_info_path": "/vulnerabilities/CVE-2021-29550/58107", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's implementation of hashtable lookup. See CVE-2021-29604.", "cve": "CVE-2021-29604", "id": "pyup.io-58089", "more_info_path": "/vulnerabilities/CVE-2021-29604/58089", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 include a fix for CVE-2021-29547: An attacker can cause a segfault and denial of service via accessing data outside of bounds in 'tf.raw_ops.QuantizedBatchNormWithGlobalNormalization'. This is because the implementation (https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc#L176-L189) assumes the inputs are not empty. If any of these inputs is empty, '.flat()' is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds.", "cve": "CVE-2021-29547", "id": "pyup.io-58087", "more_info_path": "/vulnerabilities/CVE-2021-29547/58087", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's implementation of 'DepthwiseConv'. See CVE-2021-29602.", "cve": "CVE-2021-29602", "id": "pyup.io-58074", "more_info_path": "/vulnerabilities/CVE-2021-29602/58074", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger undefined behavior by binding to null pointer in 'tf.raw_ops.ParameterizedTruncatedNormal'. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/3f6fe4dfef6f57e768260b48166c27d148f3015f/tensorflow/core/kernels/parameterized_truncated_normal_op.cc#L630) does not validate input arguments before accessing the first element of 'shape'. If 'shape' argument is empty, then 'shape_tensor.flat()' is an empty array. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.", "cve": "CVE-2021-29568", "id": "pyup.io-58092", "more_info_path": "/vulnerabilities/CVE-2021-29568/58092", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 update 'curl' to '7.76.0' to handle CVE-2020-8177.", "cve": "CVE-2020-8177", "id": "pyup.io-58076", "more_info_path": "/vulnerabilities/CVE-2020-8177/58076", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix a division by zero in TFLite's implementation of 'SVDF'. See CVE-2021-29598.", "cve": "CVE-2021-29598", "id": "pyup.io-58101", "more_info_path": "/vulnerabilities/CVE-2021-29598/58101", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.1.4, 2.2.3, 2.3.3 and 2.4.2 fix an undefined behavior and a 'CHECK'-fail in 'FractionalMaxPoolGrad'. See CVE-2021-29580.", "cve": "CVE-2021-29580", "id": "pyup.io-58106", "more_info_path": "/vulnerabilities/CVE-2021-29580/58106", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.4.2, 2.3.3, 2.2.3, and 2.1.4 include a fix for CVE-2021-29614: The implementation of 'tf.io.decode_raw' produces incorrect results and crashes the Python interpreter when combining 'fixed_length' and wider datatypes. The implementation of the padded version (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc) is buggy due to a confusion about pointer arithmetic rules. First, the code computes (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L61) the width of each output element by dividing the 'fixed_length' value to the size of the type argument. The 'fixed_length' argument is also used to determine the size needed for the output tensor (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L63-L79). This is followed by reencoding code (https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L85-L94). The erroneous code is the last line above: it is moving the 'out_data' pointer by 'fixed_length * sizeof (T)' bytes whereas it only copied at most 'fixed_length' bytes from the input. This results in parts of the input not being decoded into the output. Furthermore, because the pointer advance is far wider than desired, this quickly leads to writing to outside the bounds of the backing data. This OOB write leads to interpreter crash in the reproducer mentioned here, but more severe attacks can be mounted too, given that this gadget allows writing to periodically placed locations in memory.", "cve": "CVE-2021-29614", "id": "pyup.io-58170", "more_info_path": "/vulnerabilities/CVE-2021-29614/58170", "specs": [ ">=2.4.0rc0,<2.4.2", ">=2.3.0rc0,<2.3.3", ">=2.2.0rc0,<2.2.3", "<2.1.4", ">=2.5.0rc0,<2.5.0" ], "v": ">=2.4.0rc0,<2.4.2,>=2.3.0rc0,<2.3.3,>=2.2.0rc0,<2.2.3,<2.1.4,>=2.5.0rc0,<2.5.0" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37669:\nIn affected versions, an attacker can cause denial of service in applications serving models using \"tf.raw_ops.NonMaxSuppressionV5\" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a \"std::vector\". However, as \"std::vector::resize\" takes the size argument as a \"size_t\" and \"output_size\" is an \"int\", there is an implicit conversion to unsigned. If the attacker supplies a negative value, this conversion results in a crash. A similar issue occurs in \"CombinedNonMaxSuppression\". The Tensorflow team has patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c\nhttps://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d\nhttps://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58", "cve": "CVE-2021-37669", "id": "pyup.io-58030", "more_info_path": "/vulnerabilities/CVE-2021-37669/58030", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37690:\nIn affected versions when running shape functions, some functions (such as 'MutableHashTableShape') produce extra output information in the form of a 'ShapeAndType' struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault. 'ShapeRefiner' is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but the Tensorflow team was not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types. The Tensorflow team has patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-3hxh-8cp2-g4hg\nhttps://github.com/tensorflow/tensorflow/commit/ee119d4a498979525046fba1c3dd3f13a039fbb1", "cve": "CVE-2021-37690", "id": "pyup.io-58034", "more_info_path": "/vulnerabilities/CVE-2021-37690/58034", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22901", "id": "pyup.io-58024", "more_info_path": "/vulnerabilities/CVE-2021-22901/58024", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22897", "id": "pyup.io-58025", "more_info_path": "/vulnerabilities/CVE-2021-22897/58025", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37650: In affected versions the implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types. The Tensorflow team has patched the issue in GitHub commit e0b6e58c328059829c3eb968136f17aa72b6c876.", "cve": "CVE-2021-37650", "id": "pyup.io-58028", "more_info_path": "/vulnerabilities/CVE-2021-37650/58028", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4, 2.4.3, 2.5.1, 2.6.0 and 2.7.0 include a fix for CVE-2021-37678:\nIn affected versions, TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The implementation(https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses \"yaml.unsafe_load\" which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, the Tensorflow team has removed it for now. The Tensorflow team has patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r\nhttps://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012", "cve": "CVE-2021-37678", "id": "pyup.io-58032", "more_info_path": "/vulnerabilities/CVE-2021-37678/58032", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37672:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.SdcaOptimizerV2\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of \"example_labels\" is the same as the number of examples. The Tensorflow team has patched the issue in GitHub commit a4e138660270e7599793fa438cd7b2fc2ce215a6.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hj3-vjjf-f5m7\nhttps://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6", "cve": "CVE-2021-37672", "id": "pyup.io-58021", "more_info_path": "/vulnerabilities/CVE-2021-37672/58021", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 updates its dependency 'curl' to v7.77.0 to include security fixes.", "cve": "CVE-2021-22876", "id": "pyup.io-58026", "more_info_path": "/vulnerabilities/CVE-2021-22876/58026", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37670:\nIn affected versions, an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to \"tf.raw_ops.UpperBound\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of \"sorted_input\" argument. A similar issue occurs in \"tf.raw_ops.LowerBound\". The Tensorflow team has patched the issue in GitHub commit 42459e4273c2e47a3232cc16c4f4fff3b3a35c38.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9697-98pf-4rw7\nhttps://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38", "cve": "CVE-2021-37670", "id": "pyup.io-58022", "more_info_path": "/vulnerabilities/CVE-2021-37670/58022", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37682:\nIn affected versions all TFLite operations that use quantization can be made to use unitialized values. (For example, https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200). The issue stems from the fact that \"quantization.params\" is only valid if \"quantization.type\" is different that \"kTfLiteNoQuantization\". However, these checks are missing in large parts of the code. The Tensorflow team has patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4c4g-crqm-xrxw\nhttps://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5\nhttps://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887\nhttps://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538", "cve": "CVE-2021-37682", "id": "pyup.io-58033", "more_info_path": "/vulnerabilities/CVE-2021-37682/58033", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37673:\nIn affected versions, an attacker can trigger a denial of service via a \"CHECK\"-fail in \"tf.raw_ops.MapStage\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the \"key\" input is a valid non-empty tensor. The Tensorflow team has patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-278g-rq84-9hmg\nhttps://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d", "cve": "CVE-2021-37673", "id": "pyup.io-58027", "more_info_path": "/vulnerabilities/CVE-2021-37673/58027", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.3.4 and 2.4.3 include a fix for CVE-2021-37677: In affected versions the shape inference code for \"tf.raw_ops.Dequantize\" has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments. The shape inference implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses \"axis\" to select between two different values for \"minmax_rank\" which is then used to retrieve tensor dimensions. However, code assumes that \"axis\" can be either \"-1\" or a value greater than \"-1\", with no validation for the other values. The Tensorflow team has patched the issue in GitHub commit da857cfa0fde8f79ad0afdbc94e88b5d4bbec764.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-qfpc-5pjr-mh26\r\nhttps://github.com/tensorflow/tensorflow/commit/da857cfa0fde8f79ad0afdbc94e88b5d4bbec764", "cve": "CVE-2021-37677", "id": "pyup.io-58031", "more_info_path": "/vulnerabilities/CVE-2021-37677/58031", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced versions 2.3.4 and 2.4.3 update its dependency \"curl\" to include a fix for CVE-2021-22898", "cve": "CVE-2021-22898", "id": "pyup.io-58054", "more_info_path": "/vulnerabilities/CVE-2021-22898/58054", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a denial of service via a segmentation fault in 'tf.raw_ops.MaxPoolGrad' caused by missing validation. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the 'orig_input' and 'orig_output' tensors. The fixes for CVE-2021-29579 were incomplete. We have patched the issue in GitHub commit 136b51f10903e044308cf77117c0ed9871350475. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.", "cve": "CVE-2021-37674", "id": "pyup.io-58029", "more_info_path": "/vulnerabilities/CVE-2021-37674/58029", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37655: TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to 'tf.raw_ops.ResourceScatterUpdate'. The implementation (https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of 'indices' and 'updates': instead of checking that the shape of 'indices' is a prefix of the shape of 'updates' (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. The Tensorflow team has patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f.", "cve": "CVE-2021-37655", "id": "pyup.io-58020", "more_info_path": "/vulnerabilities/CVE-2021-37655/58020", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37679:\nIn affected versions it is possible to nest a \"tf.map_fn\" within another \"tf.map_fn\" call. However, if the input tensor is a \"RaggedTensor\" and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap. The \"t\" and \"z\" outputs should be identical, however this is not the case. The last row of \"t\" contains data from the heap which can be used to leak other memory information. The bug lies in the conversion from a \"Variant\" tensor to a \"RaggedTensor\". The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions. The same implementation can result in data loss, if input tensor is tweaked. The Tensorflow team has patched the issue in GitHub commit 4e2565483d0ffcadc719bd44893fb7f609bb5f12.\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-g8wg-cjwc-xhhp\nhttps://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12", "cve": "CVE-2021-37679", "id": "pyup.io-58023", "more_info_path": "/vulnerabilities/CVE-2021-37679/58023", "specs": [ ">=2.4.0rc0,<2.4.3", "<2.3.4" ], "v": ">=2.4.0rc0,<2.4.3,<2.3.4" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37645: In affected versions the implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer. The Tensorflow team has patched the issue in GitHub commit 96f364a1ca3009f98980021c4b32be5fdcca33a1.", "cve": "CVE-2021-37645", "id": "pyup.io-58056", "more_info_path": "/vulnerabilities/CVE-2021-37645/58056", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", "<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37691: In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). The Tensorflow team has patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9.", "cve": "CVE-2021-37691", "id": "pyup.io-58057", "more_info_path": "/vulnerabilities/CVE-2021-37691/58057", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", "<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tensorflow-rocm-enhanced 2.3.4 and 2.4.3 include a fix for CVE-2021-37688: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer. The Tensorflow team has patched the issue in GitHub commit 15691e456c7dc9bd6be203b09765b063bf4a380c.", "cve": "CVE-2021-37688", "id": "pyup.io-58055", "more_info_path": "/vulnerabilities/CVE-2021-37688/58055", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", "<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,<2.3.4,>=2.6.0rc0,<2.6.0" } ], "tensorhive": [ { "advisory": "Tensorhive 0.3.1 updates its dependency 'webpack-bundle-analyzer' to v3.3.2.\r\nhttps://hackerone.com/reports/463380", "cve": "PVE-2022-44753", "id": "pyup.io-44753", "more_info_path": "/vulnerabilities/PVE-2022-44753/44753", "specs": [ "<0.3.1" ], "v": "<0.3.1" }, { "advisory": "Tensorhive 0.3.5 fixes security issues in Reservation controller.\r\nhttps://github.com/roscisz/TensorHive/pull/304", "cve": "PVE-2022-44752", "id": "pyup.io-44752", "more_info_path": "/vulnerabilities/PVE-2022-44752/44752", "specs": [ "<0.3.5" ], "v": "<0.3.5" } ], "tensorpy": [ { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-5482", "id": "pyup.io-44387", "more_info_path": "/vulnerabilities/CVE-2019-5482/44387", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15211", "id": "pyup.io-44400", "more_info_path": "/vulnerabilities/CVE-2020-15211/44400", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-11655", "id": "pyup.io-44409", "more_info_path": "/vulnerabilities/CVE-2020-11655/44409", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "PVE-2021-37524", "id": "pyup.io-44389", "more_info_path": "/vulnerabilities/PVE-2021-37524/44389", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15202", "id": "pyup.io-44405", "more_info_path": "/vulnerabilities/CVE-2020-15202/44405", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-19880", "id": "pyup.io-44395", "more_info_path": "/vulnerabilities/CVE-2019-19880/44395", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2018-11770", "id": "pyup.io-44398", "more_info_path": "/vulnerabilities/CVE-2018-11770/44398", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2018-17190", "id": "pyup.io-44392", "more_info_path": "/vulnerabilities/CVE-2018-17190/44392", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2018-19664", "id": "pyup.io-44391", "more_info_path": "/vulnerabilities/CVE-2018-19664/44391", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2018-20330", "id": "pyup.io-44396", "more_info_path": "/vulnerabilities/CVE-2018-20330/44396", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-5215", "id": "pyup.io-44386", "more_info_path": "/vulnerabilities/CVE-2020-5215/44386", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-11656", "id": "pyup.io-44408", "more_info_path": "/vulnerabilities/CVE-2020-11656/44408", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15194", "id": "pyup.io-44402", "more_info_path": "/vulnerabilities/CVE-2020-15194/44402", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-13435", "id": "pyup.io-44411", "more_info_path": "/vulnerabilities/CVE-2020-13435/44411", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-16778", "id": "pyup.io-44388", "more_info_path": "/vulnerabilities/CVE-2019-16778/44388", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-19244", "id": "pyup.io-44394", "more_info_path": "/vulnerabilities/CVE-2019-19244/44394", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-19645", "id": "pyup.io-44393", "more_info_path": "/vulnerabilities/CVE-2019-19645/44393", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-19646", "id": "pyup.io-38821", "more_info_path": "/vulnerabilities/CVE-2019-19646/38821", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-5481", "id": "pyup.io-44384", "more_info_path": "/vulnerabilities/CVE-2019-5481/44384", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-10099", "id": "pyup.io-44397", "more_info_path": "/vulnerabilities/CVE-2019-10099/44397", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-13960", "id": "pyup.io-44399", "more_info_path": "/vulnerabilities/CVE-2019-13960/44399", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2019-16168", "id": "pyup.io-44385", "more_info_path": "/vulnerabilities/CVE-2019-16168/44385", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15210", "id": "pyup.io-44420", "more_info_path": "/vulnerabilities/CVE-2020-15210/44420", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15209", "id": "pyup.io-44414", "more_info_path": "/vulnerabilities/CVE-2020-15209/44414", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15207", "id": "pyup.io-44417", "more_info_path": "/vulnerabilities/CVE-2020-15207/44417", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15206", "id": "pyup.io-44406", "more_info_path": "/vulnerabilities/CVE-2020-15206/44406", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15205", "id": "pyup.io-44404", "more_info_path": "/vulnerabilities/CVE-2020-15205/44404", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15203", "id": "pyup.io-44419", "more_info_path": "/vulnerabilities/CVE-2020-15203/44419", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15204", "id": "pyup.io-44403", "more_info_path": "/vulnerabilities/CVE-2020-15204/44403", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15195", "id": "pyup.io-44416", "more_info_path": "/vulnerabilities/CVE-2020-15195/44416", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15190", "id": "pyup.io-44418", "more_info_path": "/vulnerabilities/CVE-2020-15190/44418", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-15208", "id": "pyup.io-44407", "more_info_path": "/vulnerabilities/CVE-2020-15208/44407", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-13871", "id": "pyup.io-44412", "more_info_path": "/vulnerabilities/CVE-2020-13871/44412", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-13631", "id": "pyup.io-44413", "more_info_path": "/vulnerabilities/CVE-2020-13631/44413", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-13434", "id": "pyup.io-44410", "more_info_path": "/vulnerabilities/CVE-2020-13434/44410", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-9327", "id": "pyup.io-44415", "more_info_path": "/vulnerabilities/CVE-2020-9327/44415", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy 1.5.0 updates Tensorflow to v1.15.4 to include security fixes.", "cve": "CVE-2020-13630", "id": "pyup.io-44401", "more_info_path": "/vulnerabilities/CVE-2020-13630/44401", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-22923", "id": "pyup.io-46570", "more_info_path": "/vulnerabilities/CVE-2021-22923/46570", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23575", "id": "pyup.io-46640", "more_info_path": "/vulnerabilities/CVE-2022-23575/46640", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-26270", "id": "pyup.io-46567", "more_info_path": "/vulnerabilities/CVE-2020-26270/46567", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21733", "id": "pyup.io-46614", "more_info_path": "/vulnerabilities/CVE-2022-21733/46614", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21738", "id": "pyup.io-46619", "more_info_path": "/vulnerabilities/CVE-2022-21738/46619", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23558", "id": "pyup.io-46623", "more_info_path": "/vulnerabilities/CVE-2022-23558/46623", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23557", "id": "pyup.io-46622", "more_info_path": "/vulnerabilities/CVE-2022-23557/46622", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-26266", "id": "pyup.io-46564", "more_info_path": "/vulnerabilities/CVE-2020-26266/46564", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21732", "id": "pyup.io-46613", "more_info_path": "/vulnerabilities/CVE-2022-21732/46613", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23565", "id": "pyup.io-46630", "more_info_path": "/vulnerabilities/CVE-2022-23565/46630", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23574", "id": "pyup.io-46639", "more_info_path": "/vulnerabilities/CVE-2022-23574/46639", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23578", "id": "pyup.io-46643", "more_info_path": "/vulnerabilities/CVE-2022-23578/46643", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23580", "id": "pyup.io-46645", "more_info_path": "/vulnerabilities/CVE-2022-23580/46645", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23587", "id": "pyup.io-46652", "more_info_path": "/vulnerabilities/CVE-2022-23587/46652", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23562", "id": "pyup.io-46627", "more_info_path": "/vulnerabilities/CVE-2022-23562/46627", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23595", "id": "pyup.io-46656", "more_info_path": "/vulnerabilities/CVE-2022-23595/46656", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21725", "id": "pyup.io-46606", "more_info_path": "/vulnerabilities/CVE-2022-21725/46606", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-13790", "id": "pyup.io-46559", "more_info_path": "/vulnerabilities/CVE-2020-13790/46559", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2019-20838", "id": "pyup.io-46557", "more_info_path": "/vulnerabilities/CVE-2019-20838/46557", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41196", "id": "pyup.io-46575", "more_info_path": "/vulnerabilities/CVE-2021-41196/46575", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-22924", "id": "pyup.io-46571", "more_info_path": "/vulnerabilities/CVE-2021-22924/46571", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-22922", "id": "pyup.io-46569", "more_info_path": "/vulnerabilities/CVE-2021-22922/46569", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41199", "id": "pyup.io-46578", "more_info_path": "/vulnerabilities/CVE-2021-41199/46578", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-26268", "id": "pyup.io-46566", "more_info_path": "/vulnerabilities/CVE-2020-26268/46566", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41215", "id": "pyup.io-46593", "more_info_path": "/vulnerabilities/CVE-2021-41215/46593", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41218", "id": "pyup.io-46596", "more_info_path": "/vulnerabilities/CVE-2021-41218/46596", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41222", "id": "pyup.io-46599", "more_info_path": "/vulnerabilities/CVE-2021-41222/46599", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41200", "id": "pyup.io-46579", "more_info_path": "/vulnerabilities/CVE-2021-41200/46579", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41221", "id": "pyup.io-46598", "more_info_path": "/vulnerabilities/CVE-2021-41221/46598", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41209", "id": "pyup.io-46588", "more_info_path": "/vulnerabilities/CVE-2021-41209/46588", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23572", "id": "pyup.io-46637", "more_info_path": "/vulnerabilities/CVE-2022-23572/46637", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41210", "id": "pyup.io-46589", "more_info_path": "/vulnerabilities/CVE-2021-41210/46589", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-22926", "id": "pyup.io-46573", "more_info_path": "/vulnerabilities/CVE-2021-22926/46573", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41204", "id": "pyup.io-46583", "more_info_path": "/vulnerabilities/CVE-2021-41204/46583", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-10531", "id": "pyup.io-46558", "more_info_path": "/vulnerabilities/CVE-2020-10531/46558", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41205", "id": "pyup.io-46584", "more_info_path": "/vulnerabilities/CVE-2021-41205/46584", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-26267", "id": "pyup.io-46565", "more_info_path": "/vulnerabilities/CVE-2020-26267/46565", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21739", "id": "pyup.io-46620", "more_info_path": "/vulnerabilities/CVE-2022-21739/46620", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21740", "id": "pyup.io-46621", "more_info_path": "/vulnerabilities/CVE-2022-21740/46621", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23591", "id": "pyup.io-46655", "more_info_path": "/vulnerabilities/CVE-2022-23591/46655", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23589", "id": "pyup.io-46654", "more_info_path": "/vulnerabilities/CVE-2022-23589/46654", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23588", "id": "pyup.io-46653", "more_info_path": "/vulnerabilities/CVE-2022-23588/46653", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23586", "id": "pyup.io-46651", "more_info_path": "/vulnerabilities/CVE-2022-23586/46651", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23585", "id": "pyup.io-46650", "more_info_path": "/vulnerabilities/CVE-2022-23585/46650", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23584", "id": "pyup.io-46649", "more_info_path": "/vulnerabilities/CVE-2022-23584/46649", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23583", "id": "pyup.io-46648", "more_info_path": "/vulnerabilities/CVE-2022-23583/46648", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23582", "id": "pyup.io-46647", "more_info_path": "/vulnerabilities/CVE-2022-23582/46647", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23581", "id": "pyup.io-46646", "more_info_path": "/vulnerabilities/CVE-2022-23581/46646", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23579", "id": "pyup.io-46644", "more_info_path": "/vulnerabilities/CVE-2022-23579/46644", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23577", "id": "pyup.io-46642", "more_info_path": "/vulnerabilities/CVE-2022-23577/46642", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23576", "id": "pyup.io-46641", "more_info_path": "/vulnerabilities/CVE-2022-23576/46641", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23573", "id": "pyup.io-46638", "more_info_path": "/vulnerabilities/CVE-2022-23573/46638", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23571", "id": "pyup.io-46636", "more_info_path": "/vulnerabilities/CVE-2022-23571/46636", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23570", "id": "pyup.io-46635", "more_info_path": "/vulnerabilities/CVE-2022-23570/46635", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23566", "id": "pyup.io-46631", "more_info_path": "/vulnerabilities/CVE-2022-23566/46631", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23564", "id": "pyup.io-46629", "more_info_path": "/vulnerabilities/CVE-2022-23564/46629", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23563", "id": "pyup.io-46628", "more_info_path": "/vulnerabilities/CVE-2022-23563/46628", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23561", "id": "pyup.io-46626", "more_info_path": "/vulnerabilities/CVE-2022-23561/46626", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23560", "id": "pyup.io-46625", "more_info_path": "/vulnerabilities/CVE-2022-23560/46625", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23559", "id": "pyup.io-46624", "more_info_path": "/vulnerabilities/CVE-2022-23559/46624", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21734", "id": "pyup.io-46615", "more_info_path": "/vulnerabilities/CVE-2022-21734/46615", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23568", "id": "pyup.io-46633", "more_info_path": "/vulnerabilities/CVE-2022-23568/46633", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21730", "id": "pyup.io-46611", "more_info_path": "/vulnerabilities/CVE-2022-21730/46611", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21731", "id": "pyup.io-46612", "more_info_path": "/vulnerabilities/CVE-2022-21731/46612", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21737", "id": "pyup.io-46618", "more_info_path": "/vulnerabilities/CVE-2022-21737/46618", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21729", "id": "pyup.io-46610", "more_info_path": "/vulnerabilities/CVE-2022-21729/46610", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21736", "id": "pyup.io-46617", "more_info_path": "/vulnerabilities/CVE-2022-21736/46617", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23567", "id": "pyup.io-46632", "more_info_path": "/vulnerabilities/CVE-2022-23567/46632", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21726", "id": "pyup.io-46607", "more_info_path": "/vulnerabilities/CVE-2022-21726/46607", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21727", "id": "pyup.io-46608", "more_info_path": "/vulnerabilities/CVE-2022-21727/46608", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21735", "id": "pyup.io-46616", "more_info_path": "/vulnerabilities/CVE-2022-21735/46616", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-23569", "id": "pyup.io-46634", "more_info_path": "/vulnerabilities/CVE-2022-23569/46634", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41216", "id": "pyup.io-46594", "more_info_path": "/vulnerabilities/CVE-2021-41216/46594", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41224", "id": "pyup.io-46601", "more_info_path": "/vulnerabilities/CVE-2021-41224/46601", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-26271", "id": "pyup.io-46568", "more_info_path": "/vulnerabilities/CVE-2020-26271/46568", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-15265", "id": "pyup.io-46562", "more_info_path": "/vulnerabilities/CVE-2020-15265/46562", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-15250", "id": "pyup.io-46561", "more_info_path": "/vulnerabilities/CVE-2020-15250/46561", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41212", "id": "pyup.io-46590", "more_info_path": "/vulnerabilities/CVE-2021-41212/46590", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-15266", "id": "pyup.io-46563", "more_info_path": "/vulnerabilities/CVE-2020-15266/46563", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41227", "id": "pyup.io-46604", "more_info_path": "/vulnerabilities/CVE-2021-41227/46604", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41225", "id": "pyup.io-46602", "more_info_path": "/vulnerabilities/CVE-2021-41225/46602", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41219", "id": "pyup.io-46597", "more_info_path": "/vulnerabilities/CVE-2021-41219/46597", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2020-14155", "id": "pyup.io-46560", "more_info_path": "/vulnerabilities/CVE-2020-14155/46560", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41203", "id": "pyup.io-46582", "more_info_path": "/vulnerabilities/CVE-2021-41203/46582", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41213", "id": "pyup.io-46591", "more_info_path": "/vulnerabilities/CVE-2021-41213/46591", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41207", "id": "pyup.io-46586", "more_info_path": "/vulnerabilities/CVE-2021-41207/46586", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41206", "id": "pyup.io-46585", "more_info_path": "/vulnerabilities/CVE-2021-41206/46585", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41226", "id": "pyup.io-46603", "more_info_path": "/vulnerabilities/CVE-2021-41226/46603", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41223", "id": "pyup.io-46600", "more_info_path": "/vulnerabilities/CVE-2021-41223/46600", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41228", "id": "pyup.io-46605", "more_info_path": "/vulnerabilities/CVE-2021-41228/46605", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41208", "id": "pyup.io-46587", "more_info_path": "/vulnerabilities/CVE-2021-41208/46587", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41202", "id": "pyup.io-46581", "more_info_path": "/vulnerabilities/CVE-2021-41202/46581", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41217", "id": "pyup.io-46595", "more_info_path": "/vulnerabilities/CVE-2021-41217/46595", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41214", "id": "pyup.io-46592", "more_info_path": "/vulnerabilities/CVE-2021-41214/46592", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41201", "id": "pyup.io-46580", "more_info_path": "/vulnerabilities/CVE-2021-41201/46580", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41198", "id": "pyup.io-46577", "more_info_path": "/vulnerabilities/CVE-2021-41198/46577", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41197", "id": "pyup.io-46576", "more_info_path": "/vulnerabilities/CVE-2021-41197/46576", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-41195", "id": "pyup.io-46574", "more_info_path": "/vulnerabilities/CVE-2021-41195/46574", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2021-22925", "id": "pyup.io-46572", "more_info_path": "/vulnerabilities/CVE-2021-22925/46572", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" }, { "advisory": "Tensorpy versions 1.6.1 and prior require as dependency TensorFlow v1.15.4 or lower, that have several known vulnerabilities.", "cve": "CVE-2022-21728", "id": "pyup.io-46609", "more_info_path": "/vulnerabilities/CVE-2022-21728/46609", "specs": [ "<=1.6.1" ], "v": "<=1.6.1" } ], "tensorrt-llm": [ { "advisory": "Affected versions of the TensorRT\u2011LLM package are potentially vulnerable to a Race Condition (Denial of Service). The MoeLoadBalancer::startIter and MoeLoadBalancer::workerThread methods fail to properly synchronize per-iteration metadata under a condition variable, leading to lost wake\u2011ups and stale state.", "cve": "PVE-2025-78234", "id": "pyup.io-78234", "more_info_path": "/vulnerabilities/PVE-2025-78234/78234", "specs": [ "<0.21.0rc0" ], "v": "<0.21.0rc0" } ], "tenzir": [ { "advisory": "Affected versions of the `tenzir` package are vulnerable to Denial of Service due to a race condition in the query execution path when exporters time out during meta index lookup operations. The query handling logic fails to properly handle timeout conditions in the meta index lookup phase, causing the query execution thread to enter a deadlock state where it neither completes nor returns an error, indefinitely blocking the query slot. An attacker can exploit this by submitting queries designed to trigger exporter timeouts during meta index lookups, causing query slots to become permanently occupied and eventually exhausting all available query resources, preventing legitimate users from executing queries and effectively rendering the system unable to process any data export requests.", "cve": "PVE-2025-81712", "id": "pyup.io-81712", "more_info_path": "/vulnerabilities/PVE-2025-81712/81712", "specs": [ "<1.1.2" ], "v": "<1.1.2" }, { "advisory": "Affected versions of the `tenzir` package are vulnerable to Information Disclosure due to a race condition in the index logic during export operations. The `vast export` command contains improper synchronisation when querying indexed data, causing concurrent access to shared index structures to produce inconsistent read operations that result in incomplete or empty result sets being returned to users. An attacker can exploit this by triggering concurrent export operations or timing queries during index updates to cause the system to omit sensitive data from query results, potentially hiding malicious activity in logs, evading detection mechanisms, or causing compliance violations through incomplete data exports.", "cve": "PVE-2025-81721", "id": "pyup.io-81721", "more_info_path": "/vulnerabilities/PVE-2025-81721/81721", "specs": [ "<2020.01.31" ], "v": "<2020.01.31" } ], "tequests": [ { "advisory": "Tequests is a malicious package, typosquatting the popular Python 'requests' library. It embeds source code that retrieves a Golang-based ransomware binary from a remote server.\r\nhttps://thehackernews.com/2022/12/malware-strains-targeting-python-and.html", "cve": "PVE-2023-52906", "id": "pyup.io-52906", "more_info_path": "/vulnerabilities/PVE-2023-52906/52906", "specs": [ ">0" ], "v": ">0" } ], "termius": [ { "advisory": "Termius 1.2.13 removed storing of passwords and passphrases locally.", "cve": "PVE-2021-39270", "id": "pyup.io-39270", "more_info_path": "/vulnerabilities/PVE-2021-39270/39270", "specs": [ "<1.2.13" ], "v": "<1.2.13" }, { "advisory": "Termius 1.2.15 updates its dependency 'cryptography' to v3.2 to include security fixes.", "cve": "CVE-2018-10903", "id": "pyup.io-39250", "more_info_path": "/vulnerabilities/CVE-2018-10903/39250", "specs": [ "<1.2.15" ], "v": "<1.2.15" }, { "advisory": "Termius 1.2.15 updates its dependency 'cryptography' to v3.2 to include security fixes.", "cve": "CVE-2017-3735", "id": "pyup.io-50764", "more_info_path": "/vulnerabilities/CVE-2017-3735/50764", "specs": [ "<1.2.15" ], "v": "<1.2.15" }, { "advisory": "Termius 1.2.15 updates its dependency 'cryptography' to v3.2 to include security fixes.", "cve": "CVE-2017-3736", "id": "pyup.io-50763", "more_info_path": "/vulnerabilities/CVE-2017-3736/50763", "specs": [ "<1.2.15" ], "v": "<1.2.15" } ], "tern": [ { "advisory": "Tern 2.5.0 updates its dependency 'urllib3' to v1.26.4 due to security issues.", "cve": "CVE-2021-28363", "id": "pyup.io-40054", "more_info_path": "/vulnerabilities/CVE-2021-28363/40054", "specs": [ "<2.5.0" ], "v": "<2.5.0" } ], "terra-notebook-utils": [ { "advisory": "Affected versions of terra-notebook-utils are vulnerable to a race condition in task submission due to improper thread synchronization. The issue could lead to crashes or inconsistent task states when tasks are submitted from background threads. This vulnerability has been resolved by ensuring that task pruning operations are restricted to the main thread.", "cve": "PVE-2024-73029", "id": "pyup.io-73029", "more_info_path": "/vulnerabilities/PVE-2024-73029/73029", "specs": [ "<0.8.0" ], "v": "<0.8.0" } ], "tesserocr": [ { "advisory": "Tesserocr 2.6.1 ships with a version of C library 'libwebp' which is affected by a high risk vulnerability. Only mac OS X wheels on PyPI were affected.\r\nhttps://inspector.pypi.io/project/tesserocr/2.6.1/packages/05/bb/603ec678bb2682b690c8af2b7f45099aa7666865c381ae27d5a0d2633f75/tesserocr-2.6.1-cp310-cp310-macosx_10_9_x86_64.whl", "cve": "CVE-2023-4863", "id": "pyup.io-62316", "more_info_path": "/vulnerabilities/CVE-2023-4863/62316", "specs": [ "==2.6.1" ], "v": "==2.6.1" } ], "testinfra-bdd": [ { "advisory": "Testinfra-bdd 2.2.4 pins its dependency 'setuptools' to versions '>=65.5.1' to include a security fix.", "cve": "CVE-2022-40897", "id": "pyup.io-52656", "more_info_path": "/vulnerabilities/CVE-2022-40897/52656", "specs": [ "<2.2.4" ], "v": "<2.2.4" }, { "advisory": "Testinfra-bdd 2.2.4 updates its dependency 'GitPython' to v3.1.30 to include a security fix.", "cve": "CVE-2022-24439", "id": "pyup.io-52602", "more_info_path": "/vulnerabilities/CVE-2022-24439/52602", "specs": [ "<2.2.4" ], "v": "<2.2.4" } ], "testing-pip-confusion": [ { "advisory": "Testing-pip-confusion is a malicious package, typosquatting.\r\nhttps://blog.sonatype.com/trojanized-pypi-package-imitates-a-popular-python-server-library", "cve": "PVE-2022-47821", "id": "pyup.io-47821", "more_info_path": "/vulnerabilities/PVE-2022-47821/47821", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "testrail-api": [ { "advisory": "Testrail-api 1.12.1 updates its dependency 'requests' to v2.31.0 to include a security fix.", "cve": "CVE-2023-32681", "id": "pyup.io-61288", "more_info_path": "/vulnerabilities/CVE-2023-32681/61288", "specs": [ "<1.12.1" ], "v": "<1.12.1" }, { "advisory": "Affected versions of Testrail-api update its dependency 'black', to include a security fix.", "cve": "CVE-2024-21503", "id": "pyup.io-71544", "more_info_path": "/vulnerabilities/CVE-2024-21503/71544", "specs": [ "<1.13.1" ], "v": "<1.13.1" }, { "advisory": "Affected versions of `testrail-api` are potentially vulnerable due to a dependency on `requests` version 2.31.0, which is impacted by a vulnerability that can possibly allow an attacker to exploit a flaw in handling certain HTTP responses, leading to unintended behaviors or security issues.", "cve": "CVE-2024-35195", "id": "pyup.io-71559", "more_info_path": "/vulnerabilities/CVE-2024-35195/71559", "specs": [ "<1.13.1" ], "v": "<1.13.1" } ], "tethys-platform": [ { "advisory": "Tethys-platform 3.2.0 updates its dependency 'jQuery' to v3.5.1 to include security fixes.", "cve": "CVE-2020-11022", "id": "pyup.io-44918", "more_info_path": "/vulnerabilities/CVE-2020-11022/44918", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Tethys-platform 3.2.0 updates its dependency 'jQuery' to v3.5.1 to include security fixes.", "cve": "CVE-2020-11023", "id": "pyup.io-44920", "more_info_path": "/vulnerabilities/CVE-2020-11023/44920", "specs": [ "<3.2.0" ], "v": "<3.2.0" }, { "advisory": "Tethys-platform 3.3.0 removes EXIF, IPTC, and XMP metadata from all Tethys Portal images to address metadata leakage.\r\nhttps://github.com/tethysplatform/tethys/issues/630", "cve": "PVE-2022-44917", "id": "pyup.io-44917", "more_info_path": "/vulnerabilities/PVE-2022-44917/44917", "specs": [ "<3.3.0" ], "v": "<3.3.0" } ], "texbld": [ { "advisory": "Texbld 0.2 patches an arbitrary FS access vulnerability.\r\nhttps://github.com/texbld/texbld/commit/06d0d7db7f2f1263269b50439e7d6f458063279e", "cve": "PVE-2022-50170", "id": "pyup.io-50170", "more_info_path": "/vulnerabilities/PVE-2022-50170/50170", "specs": [ "<0.2" ], "v": "<0.2" }, { "advisory": "Texbld 0.2.0 prevents arbitrary FS access. An attacker may upload an image to Github from which scaffolding can result in arbitrary changes to a filesystem (via relative paths).\r\nhttps://github.com/texbld/texbld/commit/06d0d7db7f2f1263269b50439e7d6f458063279e", "cve": "PVE-2022-49726", "id": "pyup.io-49726", "more_info_path": "/vulnerabilities/PVE-2022-49726/49726", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "texercise": [ { "advisory": "The Texercise package in PyPI v0.0.1 to v0.0.12 was discovered to contain a code execution backdoor. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.", "cve": "CVE-2022-34066", "id": "pyup.io-62705", "more_info_path": "/vulnerabilities/CVE-2022-34066/62705", "specs": [ ">=0.0.1,<=0.0.12" ], "v": ">=0.0.1,<=0.0.12" } ], "text-generation": [ { "advisory": "Affected versions of the text-generation package are vulnerable to Code Injection due to insecure handling of the github.head_ref user input in the GitHub Actions workflow. The `autodocs.yml` workflow dynamically constructs a shell command for installing a software package by embedding the unvalidated `github.head_ref` value, allowing arbitrary command injection. An attacker can exploit this by forking the repository, naming a branch with a crafted malicious payload, and opening a pull request to trigger execution of arbitrary commands on the GitHub Actions runner.", "cve": "CVE-2024-3924", "id": "pyup.io-78740", "more_info_path": "/vulnerabilities/CVE-2024-3924/78740", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "text2qti": [ { "advisory": "Text2qti version 0.4.0 has addressed a vulnerability related to catastrophic backtracking in LaTeX math regex.", "cve": "PVE-2023-62064", "id": "pyup.io-62064", "more_info_path": "/vulnerabilities/PVE-2023-62064/62064", "specs": [ "<0.4.0" ], "v": "<0.4.0" } ], "textattack": [ { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37678", "id": "pyup.io-42605", "more_info_path": "/vulnerabilities/CVE-2021-37678/42605", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37690", "id": "pyup.io-42617", "more_info_path": "/vulnerabilities/CVE-2021-37690/42617", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37638", "id": "pyup.io-42565", "more_info_path": "/vulnerabilities/CVE-2021-37638/42565", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37641", "id": "pyup.io-42568", "more_info_path": "/vulnerabilities/CVE-2021-37641/42568", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37668", "id": "pyup.io-42595", "more_info_path": "/vulnerabilities/CVE-2021-37668/42595", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37646", "id": "pyup.io-42573", "more_info_path": "/vulnerabilities/CVE-2021-37646/42573", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37653", "id": "pyup.io-42580", "more_info_path": "/vulnerabilities/CVE-2021-37653/42580", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37672", "id": "pyup.io-42599", "more_info_path": "/vulnerabilities/CVE-2021-37672/42599", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-22901", "id": "pyup.io-42623", "more_info_path": "/vulnerabilities/CVE-2021-22901/42623", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37683", "id": "pyup.io-42610", "more_info_path": "/vulnerabilities/CVE-2021-37683/42610", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37663", "id": "pyup.io-42590", "more_info_path": "/vulnerabilities/CVE-2021-37663/42590", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37680", "id": "pyup.io-42607", "more_info_path": "/vulnerabilities/CVE-2021-37680/42607", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37661", "id": "pyup.io-42588", "more_info_path": "/vulnerabilities/CVE-2021-37661/42588", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37645", "id": "pyup.io-42572", "more_info_path": "/vulnerabilities/CVE-2021-37645/42572", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-22876", "id": "pyup.io-42620", "more_info_path": "/vulnerabilities/CVE-2021-22876/42620", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-22897", "id": "pyup.io-42621", "more_info_path": "/vulnerabilities/CVE-2021-22897/42621", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37684", "id": "pyup.io-42611", "more_info_path": "/vulnerabilities/CVE-2021-37684/42611", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37656", "id": "pyup.io-42583", "more_info_path": "/vulnerabilities/CVE-2021-37656/42583", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37647", "id": "pyup.io-42574", "more_info_path": "/vulnerabilities/CVE-2021-37647/42574", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37671", "id": "pyup.io-42598", "more_info_path": "/vulnerabilities/CVE-2021-37671/42598", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37666", "id": "pyup.io-42593", "more_info_path": "/vulnerabilities/CVE-2021-37666/42593", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37655", "id": "pyup.io-42582", "more_info_path": "/vulnerabilities/CVE-2021-37655/42582", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37662", "id": "pyup.io-42589", "more_info_path": "/vulnerabilities/CVE-2021-37662/42589", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37640", "id": "pyup.io-42567", "more_info_path": "/vulnerabilities/CVE-2021-37640/42567", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37658", "id": "pyup.io-42585", "more_info_path": "/vulnerabilities/CVE-2021-37658/42585", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37687", "id": "pyup.io-42614", "more_info_path": "/vulnerabilities/CVE-2021-37687/42614", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37669", "id": "pyup.io-42596", "more_info_path": "/vulnerabilities/CVE-2021-37669/42596", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37692", "id": "pyup.io-42619", "more_info_path": "/vulnerabilities/CVE-2021-37692/42619", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37659", "id": "pyup.io-42586", "more_info_path": "/vulnerabilities/CVE-2021-37659/42586", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37682", "id": "pyup.io-42609", "more_info_path": "/vulnerabilities/CVE-2021-37682/42609", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37689", "id": "pyup.io-42616", "more_info_path": "/vulnerabilities/CVE-2021-37689/42616", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37635", "id": "pyup.io-42544", "more_info_path": "/vulnerabilities/CVE-2021-37635/42544", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37649", "id": "pyup.io-42576", "more_info_path": "/vulnerabilities/CVE-2021-37649/42576", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37685", "id": "pyup.io-42612", "more_info_path": "/vulnerabilities/CVE-2021-37685/42612", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37657", "id": "pyup.io-42584", "more_info_path": "/vulnerabilities/CVE-2021-37657/42584", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-22898", "id": "pyup.io-42622", "more_info_path": "/vulnerabilities/CVE-2021-22898/42622", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37691", "id": "pyup.io-42618", "more_info_path": "/vulnerabilities/CVE-2021-37691/42618", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37677", "id": "pyup.io-42604", "more_info_path": "/vulnerabilities/CVE-2021-37677/42604", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37637", "id": "pyup.io-42564", "more_info_path": "/vulnerabilities/CVE-2021-37637/42564", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37665", "id": "pyup.io-42592", "more_info_path": "/vulnerabilities/CVE-2021-37665/42592", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37670", "id": "pyup.io-42597", "more_info_path": "/vulnerabilities/CVE-2021-37670/42597", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37679", "id": "pyup.io-42606", "more_info_path": "/vulnerabilities/CVE-2021-37679/42606", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37674", "id": "pyup.io-42601", "more_info_path": "/vulnerabilities/CVE-2021-37674/42601", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37673", "id": "pyup.io-42600", "more_info_path": "/vulnerabilities/CVE-2021-37673/42600", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37675", "id": "pyup.io-42602", "more_info_path": "/vulnerabilities/CVE-2021-37675/42602", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37688", "id": "pyup.io-42615", "more_info_path": "/vulnerabilities/CVE-2021-37688/42615", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37686", "id": "pyup.io-42613", "more_info_path": "/vulnerabilities/CVE-2021-37686/42613", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37681", "id": "pyup.io-42608", "more_info_path": "/vulnerabilities/CVE-2021-37681/42608", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37676", "id": "pyup.io-42603", "more_info_path": "/vulnerabilities/CVE-2021-37676/42603", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37667", "id": "pyup.io-42594", "more_info_path": "/vulnerabilities/CVE-2021-37667/42594", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37652", "id": "pyup.io-42579", "more_info_path": "/vulnerabilities/CVE-2021-37652/42579", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37648", "id": "pyup.io-42575", "more_info_path": "/vulnerabilities/CVE-2021-37648/42575", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37664", "id": "pyup.io-42591", "more_info_path": "/vulnerabilities/CVE-2021-37664/42591", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37654", "id": "pyup.io-42581", "more_info_path": "/vulnerabilities/CVE-2021-37654/42581", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37651", "id": "pyup.io-42578", "more_info_path": "/vulnerabilities/CVE-2021-37651/42578", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37650", "id": "pyup.io-42577", "more_info_path": "/vulnerabilities/CVE-2021-37650/42577", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37644", "id": "pyup.io-42571", "more_info_path": "/vulnerabilities/CVE-2021-37644/42571", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37643", "id": "pyup.io-42570", "more_info_path": "/vulnerabilities/CVE-2021-37643/42570", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37639", "id": "pyup.io-42566", "more_info_path": "/vulnerabilities/CVE-2021-37639/42566", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37660", "id": "pyup.io-42587", "more_info_path": "/vulnerabilities/CVE-2021-37660/42587", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37636", "id": "pyup.io-42563", "more_info_path": "/vulnerabilities/CVE-2021-37636/42563", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Textattack 0.3.4 updates its dependency 'tensorflow' to v2.5.1 to include several security fixes.", "cve": "CVE-2021-37642", "id": "pyup.io-42569", "more_info_path": "/vulnerabilities/CVE-2021-37642/42569", "specs": [ "<0.3.4" ], "v": "<0.3.4" } ], "textharmony": [ { "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'textharmony' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.", "cve": "PVE-2024-74250", "id": "pyup.io-74250", "more_info_path": "/vulnerabilities/PVE-2024-74250/74250", "specs": [ ">=0", "<=0" ], "v": ">=0,<=0" } ], "textract": [ { "advisory": "Textract 1.5.0 includes a fix for CVE-2016-10320: Textract before 1.5.0 allows OS Command Injection attacks via a filename in a call to the process function. This may be a remote attack if a web application accepts names of arbitrary uploaded files.", "cve": "CVE-2016-10320", "id": "pyup.io-26157", "more_info_path": "/vulnerabilities/CVE-2016-10320/26157", "specs": [ "<1.5.0" ], "v": "<1.5.0" } ], "textract-py3": [ { "advisory": "Textract-py3 1.5.0 includes a fix for a potential shell injection vulnerability.", "cve": "PVE-2025-75645", "id": "pyup.io-75645", "more_info_path": "/vulnerabilities/PVE-2025-75645/75645", "specs": [ "<1.5.0" ], "v": "<1.5.0" } ], "textworld": [ { "advisory": "Textworld 1.5.3 updates its dependency 'jquery' to v3.5.0 to include security fixes.", "cve": "CVE-2020-11023", "id": "pyup.io-55299", "more_info_path": "/vulnerabilities/CVE-2020-11023/55299", "specs": [ "<1.5.3" ], "v": "<1.5.3" }, { "advisory": "Textworld 1.5.3 updates its dependency 'jquery' to v3.5.0 to include security fixes.", "cve": "CVE-2020-11022", "id": "pyup.io-55292", "more_info_path": "/vulnerabilities/CVE-2020-11022/55292", "specs": [ "<1.5.3" ], "v": "<1.5.3" } ], "tf-encrypted": [ { "advisory": "Tf-encrypted 0.4.0 implements cryptographically secure random numbers everywhere.\r\nhttps://github.com/tf-encrypted/tf-encrypted/commit/9346b7217be7c55952f6d9d51293ef13fca0215d", "cve": "PVE-2021-36687", "id": "pyup.io-36687", "more_info_path": "/vulnerabilities/PVE-2021-36687/36687", "specs": [ "<0.4.0" ], "v": "<0.4.0" }, { "advisory": "Tf-encrypted before 0.5.1 did not include a secure version of `tf.negative`.", "cve": "PVE-2021-37058", "id": "pyup.io-37058", "more_info_path": "/vulnerabilities/PVE-2021-37058/37058", "specs": [ "<0.5.1" ], "v": "<0.5.1" }, { "advisory": "Tf-encrypted 0.5.6 improves handling for cases where the secure random operation is not available.", "cve": "PVE-2021-37373", "id": "pyup.io-37373", "more_info_path": "/vulnerabilities/PVE-2021-37373/37373", "specs": [ "<0.5.6" ], "v": "<0.5.6" }, { "advisory": "Tf-encrypted 0.9.1 secures randomness using tensors of big shape.\r\nhttps://github.com/tf-encrypted/tf-encrypted/compare/0.9.0...0.9.1", "cve": "PVE-2023-53050", "id": "pyup.io-53050", "more_info_path": "/vulnerabilities/PVE-2023-53050/53050", "specs": [ "<0.9.1" ], "v": "<0.9.1" } ], "tf-models-official": [ { "advisory": "Tf-Models-Official version 2.5.0 includes a security patch for the function 'read_yaml_to_params_dict' in 'official/modeling/hyperparams/params_dict.py'. It used unsafe yaml.load(), allowing instantiation of arbitrary objects. \r\nhttps://github.com/tensorflow/models/commit/f6e9eda85f7e764e54199169ed829b94bcd07871#diff-8deb13e0080ce9697c0238e886a9de510faad3144427a5e794714b353d5ad8dc", "cve": "CVE-2020-14343", "id": "pyup.io-41394", "more_info_path": "/vulnerabilities/CVE-2020-14343/41394", "specs": [ "<2.5.0" ], "v": "<2.5.0" } ], "tflite-runtime": [ { "advisory": "Tflite-runtime 2.11.0 and prior versions are affected by CVE-2023-27579: Constructing a tflite model with a paramater 'filter_input_channel' of less than 1 gives a FPE.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-5w96-866f-6rm8", "cve": "CVE-2023-27579", "id": "pyup.io-56479", "more_info_path": "/vulnerabilities/CVE-2023-27579/56479", "specs": [ "<2.11.1" ], "v": "<2.11.1" }, { "advisory": "Tflite-runtime 2.8.0 includes a fix for CVE-2022-23561: An attacker can craft a TFLite model that would cause a write outside of bounds of an array in TFLite. In fact, the attacker can override the linked list used by the memory allocator. This can be leveraged for an arbitrary write primitive under certain conditions.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9c78-vcq7-7vxq", "cve": "CVE-2022-23561", "id": "pyup.io-56485", "more_info_path": "/vulnerabilities/CVE-2022-23561/56485", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tflite-runtime 2.8.0 includes a fix for CVE-2022-23558: An attacker can craft a TFLite model that would cause an integer overflow in 'TfLiteIntArrayCreate'. The 'TfLiteIntArrayGetSizeInBytes' returns an 'int' instead of a 'size_t'. An attacker can control model inputs such that 'computed_size' overflows the size of 'int' datatype.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-9gwq-6cwj-47h3", "cve": "CVE-2022-23558", "id": "pyup.io-56482", "more_info_path": "/vulnerabilities/CVE-2022-23558/56482", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tflite-runtime 2.8.0 includes a fix for CVE-2022-23557: An attacker can craft a TFLite model that would trigger a division by zero in 'BiasAndClamp' implementation. There is no check that the 'bias_size' is non zero.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf2j-f278-xh4v", "cve": "CVE-2022-23557", "id": "pyup.io-56484", "more_info_path": "/vulnerabilities/CVE-2022-23557/56484", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tflite-runtime 2.8.0 includes a fix for CVE-2022-23559: An attacker can craft a TFLite model that would cause an integer overflow in embedding lookup operations. Both 'embedding_size' and 'lookup_size' are products of values provided by the user. Hence, a malicious user could trigger overflows in the multiplication. In certain scenarios, this can then result in heap OOB read/write.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-98p5-x8x4-c9m5", "cve": "CVE-2022-23559", "id": "pyup.io-56483", "more_info_path": "/vulnerabilities/CVE-2022-23559/56483", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tflite-runtime 2.8.0 includes a fix for CVE-2022-21741: An attacker can craft a TFLite model that would trigger a division by zero in the implementation of depthwise convolutions. The parameters of the convolution can be user controlled and are also used within a division operation to determine the size of the padding that needs to be added before applying the convolution. There is no check before this division that the divisor is strictly positive.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-428x-9xc2-m8mj", "cve": "CVE-2022-21741", "id": "pyup.io-56481", "more_info_path": "/vulnerabilities/CVE-2022-21741/56481", "specs": [ "<2.5.3", ">=2.6.0a0,<2.6.3", ">=2.7.0a0,<2.7.1", ">=2.8.0a0,<2.8.0" ], "v": "<2.5.3,>=2.6.0a0,<2.6.3,>=2.7.0a0,<2.7.1,>=2.8.0a0,<2.8.0" }, { "advisory": "Tflite-runtime 2.9.0 includes a fix for CVE-2022-29212: Core dump when loading TFLite models with quantization.", "cve": "CVE-2022-29212", "id": "pyup.io-56480", "more_info_path": "/vulnerabilities/CVE-2022-29212/56480", "specs": [ "<2.6.4", ">=2.7.0rc0,<2.7.2", ">=2.8.0rc0,<2.8.1", ">=2.9.0rc0,<2.9.0" ], "v": "<2.6.4,>=2.7.0rc0,<2.7.2,>=2.8.0rc0,<2.8.1,>=2.9.0rc0,<2.9.0" }, { "advisory": "Tflite-runtime 2.7.0 includes a fix for CVE-2021-37691: In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). The Tensorflow team has patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9.", "cve": "CVE-2021-37691", "id": "pyup.io-56492", "more_info_path": "/vulnerabilities/CVE-2021-37691/56492", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tflite-runtime 2.7.0 includes a fix for CVE-2021-37688: In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer. The Tensorflow team has patched the issue in GitHub commit 15691e456c7dc9bd6be203b09765b063bf4a380c.", "cve": "CVE-2021-37688", "id": "pyup.io-56491", "more_info_path": "/vulnerabilities/CVE-2021-37688/56491", "specs": [ ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.6.0rc0,<2.6.0" ], "v": ">=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.6.0rc0,<2.6.0" }, { "advisory": "Tflite-runtime 2.7.0 includes a fix for CVE-2021-37687: In affected versions TFLite's 'GatherNd' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation. Hence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in 'indices'. Similar issue exists in 'Gather' implementation (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc). The Tensorflow team has patched the issue in GitHub commits bb6a0383ed553c286f87ca88c207f6774d5c4a8f and eb921122119a6b6e470ee98b89e65d721663179d.", "cve": "CVE-2021-37687", "id": "pyup.io-56490", "more_info_path": "/vulnerabilities/CVE-2021-37687/56490", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tflite-runtime 2.7.0 includes a fix for CVE-2021-37685: In affected versions TFLite's 'expand_dims.cc' (https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data. If 'axis' is a large negative value (e.g., '-100000'), then after the first 'if' it would still be negative. The check following the 'if' statement will pass and the 'for' loop would read one element before the start of 'input_dims.data' (when 'i = 0'). The Tensorflow team has patched the issue in GitHub commit d94ffe08a65400f898241c0374e9edc6fa8ed257.", "cve": "CVE-2021-37685", "id": "pyup.io-56489", "more_info_path": "/vulnerabilities/CVE-2021-37685/56489", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.4.0rc0,<2.4.3", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.4.0rc0,<2.4.3,>=2.5.0rc0,<2.5.1" }, { "advisory": "Tflite-runtime 2.7.0 includes a fix for CVE-2021-37684: In affected versions the implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0. The Tensorflow team has patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695 (https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).", "cve": "CVE-2021-37684", "id": "pyup.io-56487", "more_info_path": "/vulnerabilities/CVE-2021-37684/56487", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tflite-runtime 2.7.0 includes a fix for CVE-2021-37681: In affected versions the implementation of SVDF in TFLite is vulnerable to a null pointer error (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313). The 'GetVariableInput' function (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but 'GetTensorData' assumes that the argument is always a valid tensor. Furthermore, because 'GetVariableInput' calls 'GetMutableInput' (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return 'nullptr', the 'tensor->is_variable' expression can also trigger a null pointer exception. The Tensorflow team has patched the issue in GitHub commit 5b048e87e4e55990dae6b547add4dae59f4e1c76.", "cve": "CVE-2021-37681", "id": "pyup.io-56488", "more_info_path": "/vulnerabilities/CVE-2021-37681/56488", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1", ">=2.4.0rc0,<2.4.3" ], "v": ">=2.6.0rc0,<2.6.0,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1,>=2.4.0rc0,<2.4.3" }, { "advisory": "Tflite-runtime version 2.7.0 includes a fix for CVE-2021-37682:\r\nIn affected versions all TFLite operations that use quantization can be made to use unitialized values. (For example, https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200). The issue stems from the fact that \"quantization.params\" is only valid if \"quantization.type\" is different that \"kTfLiteNoQuantization\". However, these checks are missing in large parts of the code. The Tensorflow team has patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538.\r\nhttps://github.com/tensorflow/tensorflow/security/advisories/GHSA-4c4g-crqm-xrxw\r\nhttps://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5\r\nhttps://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887\r\nhttps://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538", "cve": "CVE-2021-37682", "id": "pyup.io-56486", "more_info_path": "/vulnerabilities/CVE-2021-37682/56486", "specs": [ ">=2.6.0rc0,<2.6.0", ">=2.4.0rc0,<2.4.3", ">=2.3.0rc0,<2.3.4", ">=2.5.0rc0,<2.5.1" ], "v": ">=2.6.0rc0,<2.6.0,>=2.4.0rc0,<2.4.3,>=2.3.0rc0,<2.3.4,>=2.5.0rc0,<2.5.1" } ], "tftpy": [ { "advisory": "Tftpy 0.4.6 adds some security checks around the 'tftproot'.", "cve": "PVE-2021-41170", "id": "pyup.io-41170", "more_info_path": "/vulnerabilities/PVE-2021-41170/41170", "specs": [ "<0.4.6" ], "v": "<0.4.6" }, { "advisory": "Affected versions of the Python TFTP library, tftpy, are susceptible to a Directory Traversal vulnerability that allows unauthorized access beyond the tftproot directory. This occurs due to the library's inability to detect instances where sibling files or directories exist alongside tftproot, sharing a common prefix with it.", "cve": "PVE-2024-99843", "id": "pyup.io-65577", "more_info_path": "/vulnerabilities/PVE-2024-99843/65577", "specs": [ ">=0,<0.8.1" ], "v": ">=0,<0.8.1" } ], "tfx": [ { "advisory": "Tfx 0.30.0 uses yaml.SafeLoader() to avoid a code execution vulnerability.\r\nhttps://github.com/tensorflow/tfx/commit/2692c9ab437d76b5d9517996bfe2596862e0791d#diff-68603411e5359dc496f3e5d7469be772aaca79b3e6950d4df9bdb616b519d3ce", "cve": "CVE-2020-14343", "id": "pyup.io-41395", "more_info_path": "/vulnerabilities/CVE-2020-14343/41395", "specs": [ "<0.30.0" ], "v": "<0.30.0" }, { "advisory": "Tfx 1.14.0 updates its dependency 'scikit-learn' to include a security fix.", "cve": "PVE-2022-52255", "id": "pyup.io-61011", "more_info_path": "/vulnerabilities/PVE-2022-52255/61011", "specs": [ "<1.14.0" ], "v": "<1.14.0" } ], "tg": [ { "advisory": "Tg 0.1.3 makes 'file_path' setting in config file shell escaped for security reasons.", "cve": "PVE-2021-40256", "id": "pyup.io-40256", "more_info_path": "/vulnerabilities/PVE-2021-40256/40256", "specs": [ "<0.1.3" ], "v": "<0.1.3" }, { "advisory": "Versions of tg, a Terminal Telegram client, are susceptible to Command Injection through the file_path variable. This vulnerability allows for unauthorized command execution by manipulating the file path input.", "cve": "PVE-2024-99842", "id": "pyup.io-65578", "more_info_path": "/vulnerabilities/PVE-2024-99842/65578", "specs": [ ">=0,<0.1.3" ], "v": ">=0,<0.1.3" } ], "tg-login": [ { "advisory": "Tg-login 0.0.2 avoids printing the session string on screen.\r\nhttps://github.com/aahnik/tg-login/commit/4f2b34ad76ac6ffec9fd708103ae0ed02653fd2c", "cve": "PVE-2022-52083", "id": "pyup.io-52083", "more_info_path": "/vulnerabilities/PVE-2022-52083/52083", "specs": [ "<0.0.2" ], "v": "<0.0.2" } ], "tgmix": [ { "advisory": "Affected versions of the tgmix package are vulnerable to Path Traversal due to improper path canonicalization and missing directory-boundary enforcement in the media processor. In tgmix.media_processor, the process method previously combined self.base_dir with the user-controlled message[media_type] filename and invoked mark_media/copy_media_file without resolving the canonical path or verifying that the target remained within the export directory, permitting .. segments and symbolic links to escape self.base_dir.", "cve": "PVE-2025-79815", "id": "pyup.io-79815", "more_info_path": "/vulnerabilities/PVE-2025-79815/79815", "specs": [ "<0.9.0" ], "v": "<0.9.0" } ], "thamos": [ { "advisory": "Thamos 0.1.0 uses yaml.safe_load for security reasons.", "cve": "PVE-2021-37295", "id": "pyup.io-37295", "more_info_path": "/vulnerabilities/PVE-2021-37295/37295", "specs": [ "<0.1.0" ], "v": "<0.1.0" } ], "that-depends": [ { "advisory": "That-depends fixes a race condition that could lead to multiple instances being created, causing inconsistent states or denial of service. The update ensures proper synchronization to prevent these issues.", "cve": "PVE-2024-72763", "id": "pyup.io-72763", "more_info_path": "/vulnerabilities/PVE-2024-72763/72763", "specs": [ "<1.16.2" ], "v": "<1.16.2" } ], "thefuck": [ { "advisory": "The thefuck (aka The Fuck) package before 3.31 for Python allows Path Traversal that leads to arbitrary file deletion via the \"undo archive operation\" feature.\r\nhttps://github.com/nvbn/thefuck/commit/e343c577cd7da4d304b837d4a07ab4df1e023092", "cve": "CVE-2021-34363", "id": "pyup.io-40651", "more_info_path": "/vulnerabilities/CVE-2021-34363/40651", "specs": [ "<3.31" ], "v": "<3.31" } ], "thera-py": [ { "advisory": "Thera-py 0.3.10 and 0.5.0.dev0 update its dependency 'starlette' to include a security fix.", "cve": "CVE-2023-30798", "id": "pyup.io-62259", "more_info_path": "/vulnerabilities/CVE-2023-30798/62259", "specs": [ "<0.3.10", ">=0.4.dev0,<0.5.0.dev0" ], "v": "<0.3.10,>=0.4.dev0,<0.5.0.dev0" }, { "advisory": "Thera-py 0.3.10 and 0.5.0.dev0 update its dependency 'ipython' to include a security fix.", "cve": "CVE-2023-24816", "id": "pyup.io-62237", "more_info_path": "/vulnerabilities/CVE-2023-24816/62237", "specs": [ "<0.3.10", ">=0.4.dev0,<0.5.0.dev0" ], "v": "<0.3.10,>=0.4.dev0,<0.5.0.dev0" }, { "advisory": "Thera-py 0.3.5 updates its dependency 'pyjwt' to v2.4.0 to include a security fix.", "cve": "CVE-2022-29217", "id": "pyup.io-49317", "more_info_path": "/vulnerabilities/CVE-2022-29217/49317", "specs": [ "<0.3.5" ], "v": "<0.3.5" }, { "advisory": "Thera-py 0.3.5 updates its dependency 'notebook' to v6.4.11 to include a security fix.", "cve": "CVE-2022-24758", "id": "pyup.io-49007", "more_info_path": "/vulnerabilities/CVE-2022-24758/49007", "specs": [ "<0.3.5" ], "v": "<0.3.5" } ], "thermostat": [ { "advisory": "Thermostat 1.7.5 pins its dependency 'certifi' to versions '>=2022.12.07' to include a security fix.", "cve": "CVE-2022-23491", "id": "pyup.io-52695", "more_info_path": "/vulnerabilities/CVE-2022-23491/52695", "specs": [ "<1.7.5" ], "v": "<1.7.5" } ], "thinc": [ { "advisory": "Thinc 8.0.4 starts to avoid the 'Pydantic' versions with security vulnerabilities.", "cve": "PVE-2021-40660", "id": "pyup.io-40660", "more_info_path": "/vulnerabilities/PVE-2021-40660/40660", "specs": [ "<8.0.4" ], "v": "<8.0.4" } ], "thingsboard-gateway": [ { "advisory": "Thingsboard-gateway 3.3 includes a fix for a potential race condition vulnerability.\r\nhttps://github.com/thingsboard/thingsboard-gateway/pull/1114", "cve": "PVE-2023-61344", "id": "pyup.io-61344", "more_info_path": "/vulnerabilities/PVE-2023-61344/61344", "specs": [ "<3.3" ], "v": "<3.3" } ], "thorn": [ { "advisory": "thorn before 1.1.0 has several security vulnerabilities: Now provides HMAC signing by default, No longer dispatches webhooks to internal networks, Now only dispatches to HTTP and HTTPS URLs by default, Now only dispatches to ports 80 and 443 by default, Adds recipient validators", "cve": "PVE-2021-26158", "id": "pyup.io-26158", "more_info_path": "/vulnerabilities/PVE-2021-26158/26158", "specs": [ "<1.1.0" ], "v": "<1.1.0" } ], "thoth": [ { "advisory": "Thoth 0.1.0 changes to use yaml.safe_load() to avoid a code execution vulnerability.\r\nhttps://github.com/thoth-station/thamos/commit/b2e21df92a927c5ff753e2d9b4cf744417c7efcc", "cve": "PVE-2022-49682", "id": "pyup.io-49682", "more_info_path": "/vulnerabilities/PVE-2022-49682/49682", "specs": [ "<0.1.0" ], "v": "<0.1.0" } ], "threedi-modelchecker": [ { "advisory": "Threedi-modelchecker 0.23 adds integrity and other additional checks on connection for untrusted sqlite input.\r\nhttps://github.com/nens/threedi-modelchecker/commit/c90ae2c53fa8c26efb5256f66631a0de2ffb6c83", "cve": "PVE-2022-44498", "id": "pyup.io-44498", "more_info_path": "/vulnerabilities/PVE-2022-44498/44498", "specs": [ "<0.23" ], "v": "<0.23" } ], "thrift": [ { "advisory": "Affected versions of Thrift are vulnerable to Denial Of Service. A server or client may run into an endless loop when feed with specific input data.", "cve": "CVE-2019-0205", "id": "pyup.io-74892", "more_info_path": "/vulnerabilities/CVE-2019-0205/74892", "specs": [ "<0.13.0" ], "v": "<0.13.0" } ], "thumbor": [ { "advisory": "Thumbor 7.0.3 updates its `pillow` dependency ffrom versions >=8.4.0,<9 to >=9.0.0 due to security concerns. This change was made in response to the CVE-2022-22815 vulnerability. \r\nhttps://github.com/thumbor/thumbor/pull/1390/commits/d260ee348ec59fece5bf60f6a98372ab86c1aaf6", "cve": "CVE-2022-22815", "id": "pyup.io-63745", "more_info_path": "/vulnerabilities/CVE-2022-22815/63745", "specs": [ "<7.0.3" ], "v": "<7.0.3" }, { "advisory": "Thumbor 7.0.3 updates its `pillow` dependency ffrom versions >=8.4.0,<9 to >=9.0.0 due to security concerns. This change was made in response to the CVE-2022-22816 vulnerability. \r\nhttps://github.com/thumbor/thumbor/pull/1390/commits/d260ee348ec59fece5bf60f6a98372ab86c1aaf6", "cve": "CVE-2022-22816", "id": "pyup.io-63528", "more_info_path": "/vulnerabilities/CVE-2022-22816/63528", "specs": [ "<7.0.3" ], "v": "<7.0.3" } ], "thunor": [ { "advisory": "Thunor Web affected versions are vulnerable to Cross-Site Scripting (XSS) attacks. The vulnerability stems from inadequate escaping of user-supplied data in HTTP responses, potentially allowing attackers to inject malicious scripts. This affects multiple views, including dataset groupings and plot generation. The patch implements proper output escaping using Django's `escape` function, significantly reducing the risk of script injection.", "cve": "PVE-2024-73162", "id": "pyup.io-73162", "more_info_path": "/vulnerabilities/PVE-2024-73162/73162", "specs": [ "<0.5.5" ], "v": "<0.5.5" } ], "tiddlyweb": [ { "advisory": "tiddlyweb before 1.2.18 allowed empty passwords to authenticate.", "cve": "PVE-2021-26159", "id": "pyup.io-26159", "more_info_path": "/vulnerabilities/PVE-2021-26159/26159", "specs": [ "<1.2.18" ], "v": "<1.2.18" }, { "advisory": "Some versions of TiddlyWeb, an extensible HTTP datastore for tiddlers, are susceptible to an Access Restriction Bypass vulnerability. This flaw allows unauthorized users to bypass access controls and obtain data they should not have access to.", "cve": "PVE-2024-99841", "id": "pyup.io-65579", "more_info_path": "/vulnerabilities/PVE-2024-99841/65579", "specs": [ ">=0,<1.2.18" ], "v": ">=0,<1.2.18" } ], "tile-generator": [ { "advisory": "An issue was discovered in Pivotal PCF Tile Generator versions prior to 6.0.0. Tiles created by the PCF Tile Generator create a running open security group that overrides security groups set by the operator.", "cve": "CVE-2017-4975", "id": "pyup.io-67431", "more_info_path": "/vulnerabilities/CVE-2017-4975/67431", "specs": [ "<6.0.0" ], "v": "<6.0.0" } ], "tiledb": [ { "advisory": "Tiledb 2.7.0rc1 introduces a fix for a race condition that was causing inconsistencies during schema evolution operations. The fix involves setting a timestamp range to avoid conflicts during concurrent schema evolutions. This update could potentially lead to data integrity issues, unauthorized data access or modification, and even denial of service attacks if a race condition is exploited. Inc/TileDB/pull/2776/commits/6dfa2cb2ce3b60b811eabd893118cadce13b8c2a", "cve": "PVE-2024-63531", "id": "pyup.io-63531", "more_info_path": "/vulnerabilities/PVE-2024-63531/63531", "specs": [ "<2.7.0rc1" ], "v": "<2.7.0rc1" } ], "time-series-metadata": [ { "advisory": "Time-series-metadata 0.1.1 updates its dependency 'py' to v1.10.0 to include a security fix.", "cve": "CVE-2020-29651", "id": "pyup.io-40376", "more_info_path": "/vulnerabilities/CVE-2020-29651/40376", "specs": [ "<0.1.1" ], "v": "<0.1.1" } ], "timeit": [ { "advisory": "Timeit is a typosquatting package. It shows a malicious behavior, for example, it may leak your sensitive data and/or gain unauthorized persistence in your system.\r\nhttps://www.zdnet.com/article/twelve-malicious-python-libraries-found-and-removed-from-pypi/", "cve": "PVE-2022-45419", "id": "pyup.io-45419", "more_info_path": "/vulnerabilities/PVE-2022-45419/45419", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "timesketch": [ { "advisory": "Timesketch upgrade urllib3 from version 1.22 to 1.24.1 to address CVE-2019-11324 vulnerability.", "cve": "CVE-2019-11324", "id": "pyup.io-72884", "more_info_path": "/vulnerabilities/CVE-2019-11324/72884", "specs": [ "<20240508.1" ], "v": "<20240508.1" } ], "timetagger": [ { "advisory": "Timetagger 21.3.3 improves the authentication system to make it more secure (can revoke access).", "cve": "PVE-2021-40164", "id": "pyup.io-40164", "more_info_path": "/vulnerabilities/PVE-2021-40164/40164", "specs": [ "<21.3.3" ], "v": "<21.3.3" }, { "advisory": "Affected versions of TimeTagger are vulnerable to Improper Access Control (CWE-284). The application's default configuration binds to all network interfaces (0.0.0.0:80) while allowing localhost authentication bypass functionality, potentially enabling remote attackers to obtain authentication tokens by spoofing localhost requests. The vulnerability exists in get_webtoken_localhost() which didn't verify if the server was actually bound to localhost. Remote exploitation is possible when the server is exposed on 0.0.0.0. To remediate, upgrade to versions containing commit 79fc32a or later, which changes the default binding to 127.0.0.1:8080 and adds explicit localhost binding verification. This vulnerability primarily affects Unix-like systems where the application is exposed to external networks.", "cve": "PVE-2024-74607", "id": "pyup.io-74607", "more_info_path": "/vulnerabilities/PVE-2024-74607/74607", "specs": [ "<24.12.2" ], "v": "<24.12.2" } ], "timezonefinder": [ { "advisory": "Timezonefinder 6.0.2 updates its dependency 'numpy' to v1.22.4 to include security fixes.", "cve": "CVE-2021-34141", "id": "pyup.io-49800", "more_info_path": "/vulnerabilities/CVE-2021-34141/49800", "specs": [ "<6.0.2" ], "v": "<6.0.2" }, { "advisory": "Timezonefinder 6.0.2 updates its dependency 'numpy' to v1.22.4 to include security fixes.", "cve": "CVE-2021-41496", "id": "pyup.io-49902", "more_info_path": "/vulnerabilities/CVE-2021-41496/49902", "specs": [ "<6.0.2" ], "v": "<6.0.2" }, { "advisory": "Timezonefinder 6.0.2 updates its dependency 'numpy' to v1.22.4 to include security fixes.", "cve": "CVE-2021-41495", "id": "pyup.io-49903", "more_info_path": "/vulnerabilities/CVE-2021-41495/49903", "specs": [ "<6.0.2" ], "v": "<6.0.2" } ], "tink": [ { "advisory": "The AES-CTR-HMAC-AEAD keys and the EncryptThenAuthenticate subtle implementation in tink versions before 1.4.0 may be vulnerable to chosen-ciphertext attacks. An attacker can generate ciphertexts that bypass the HMAC verification if and only if all of the following conditions are true:\r\n* Tink C++ is used on systems where size_t is a 32-bit integer. This is usually the case on 32-bit machines.\r\n* The attacker can specify long (>= 2^29 bytes ~ 536MB) associated data.", "cve": "PVE-2021-38579", "id": "pyup.io-38579", "more_info_path": "/vulnerabilities/PVE-2021-38579/38579", "specs": [ "<1.4.0" ], "v": "<1.4.0" }, { "advisory": "A mis-handling of invalid unicode characters in the Java implementation of Tink versions prior to 1.5 allows an attacker to change the ID part of a ciphertext, which result in the creation of a second ciphertext that can decrypt to the same plaintext. This can be a problem with encrypting deterministic AEAD with a single key, and rely on a unique ciphertext-per-plaintext.", "cve": "CVE-2020-8929", "id": "pyup.io-54232", "more_info_path": "/vulnerabilities/CVE-2020-8929/54232", "specs": [ ">=0,<1.5.0" ], "v": ">=0,<1.5.0" } ], "tiny-gnupg": [ { "advisory": "Tiny-gnupg 0.3.0 overhauls the ``gen_key()`` which now creates a different set of default keys. It no longer creates one primary key which does certifying & signing, with one subkey which handles encryption. Instead, tiny-gnupg 0.3.0 creates one certifying primary key, with three subkeys, one each for handling encryption, authentication, & signing. This is a more theoretically secure default key setup, & represents a common best-practice.", "cve": "PVE-2021-37692", "id": "pyup.io-37692", "more_info_path": "/vulnerabilities/PVE-2021-37692/37692", "specs": [ "<0.3.0" ], "v": "<0.3.0" } ], "tiny-scientist": [ { "advisory": "Affected versions of the tiny-scientist package are vulnerable to Path Traversal due to direct use of a user-supplied file path without canonicalization or directory restriction. In backend/app.py, the review_paper handler accepts a pdf_path parameter and, in the non-API branch, assigns absolute_pdf_path = pdf_path without normalizing the path or enforcing that it remains under project_root/generated, allowing absolute paths or .. segments to resolve outside the intended directory. An unauthenticated attacker can send a POST request to /api/review with a crafted pdf_path to read arbitrary server-accessible files, resulting in sensitive information disclosure and aiding targeted attacks.", "cve": "CVE-2025-55149", "id": "pyup.io-78705", "more_info_path": "/vulnerabilities/CVE-2025-55149/78705", "specs": [ "<=1.1.0" ], "v": "<=1.1.0" } ], "tinydb": [ { "advisory": "tinydb-serialization before 2.0.0 has an insecure implementation in ``ConcurrencyMiddleware``.\r\nhttps://github.com/msiemens/tinydb/issues/18", "cve": "PVE-2021-26160", "id": "pyup.io-26160", "more_info_path": "/vulnerabilities/PVE-2021-26160/26160", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "tiramisu-brulee": [ { "advisory": "Tiramisu-brulee 0.1.30 updates its dependency 'pip' to v21.1 to include a security fix.", "cve": "CVE-2021-3572", "id": "pyup.io-42697", "more_info_path": "/vulnerabilities/CVE-2021-3572/42697", "specs": [ "<0.1.30" ], "v": "<0.1.30" } ], "titiler": [ { "advisory": "A vulnerability in TiTiler's HTML templates could allow an attacker to inject malicious content through compromised CDN resources. The absence of integrity checks on external scripts and stylesheets made the application susceptible to supply chain attacks. This could lead to cross-site scripting (XSS) or other client-side attacks if the CDN was compromised or the connection hijacked. The fix implements Subresource Integrity (SRI) checks and adds referrer policies to mitigate the risk.", "cve": "PVE-2024-73273", "id": "pyup.io-73273", "more_info_path": "/vulnerabilities/PVE-2024-73273/73273", "specs": [ "<0.18.7" ], "v": "<0.18.7" } ], "tkeasygui": [ { "advisory": "Affected versions of the TkEasyGUI package are vulnerable to an Uncontrolled Search Path Element due to resolving helper executables and resources using an untrusted search path. The package relies on the process search order (for example, directories in `PATH`) when locating external programs, matching CWE-427\u2019s pattern in which attacker-controllable locations are included in the lookup sequence and can be selected ahead of trusted targets.", "cve": "CVE-2025-55671", "id": "pyup.io-79465", "more_info_path": "/vulnerabilities/CVE-2025-55671/79465", "specs": [ "<1.0.22" ], "v": "<1.0.22" }, { "advisory": "Affected versions of the TkEasyGUI package are vulnerable to OS Command Injection due to constructing operating system command lines from untrusted message content. The `popup_notify` helper in `TkEasyGUI/dialogs.py` composes a platform-specific notification command from caller-supplied strings and executes it without proper neutralization, enabling injection into the spawned shell.", "cve": "CVE-2025-55037", "id": "pyup.io-79464", "more_info_path": "/vulnerabilities/CVE-2025-55037/79464", "specs": [ "<1.0.22" ], "v": "<1.0.22" } ], "tkniter": [ { "advisory": "Tkniter is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.", "cve": "PVE-2022-51760", "id": "pyup.io-51760", "more_info_path": "/vulnerabilities/PVE-2022-51760/51760", "specs": [ ">0" ], "v": ">0" } ], "tksvg": [ { "advisory": "Tksvg 0.6 applies security patches for DoS vulnerabilities.\r\nhttps://github.com/TkinterEP/python-tksvg/commit/92c23d7c3a01ab4ba225815d32bc1b8eff16df00", "cve": "PVE-2021-39839", "id": "pyup.io-39839", "more_info_path": "/vulnerabilities/PVE-2021-39839/39839", "specs": [ "<0.6" ], "v": "<0.6" } ], "tkvideoplayer": [ { "advisory": "TkVideoplayer is a simple library to play video files in tkinter. Uncontrolled memory consumption in versions of TKVideoplayer prior to 2.0.0 can theoretically lead to performance degradation. There are no known workarounds. This issue has been patched and users are advised to upgrade to version 2.0.0 or later.", "cve": "CVE-2022-24902", "id": "pyup.io-54440", "more_info_path": "/vulnerabilities/CVE-2022-24902/54440", "specs": [ ">=0,<2.0.0" ], "v": ">=0,<2.0.0" } ], "tlslite": [ { "advisory": "The tlslite library before 0.4.9 for Python allows remote attackers to trigger a denial of service (runtime exception and process crash).", "cve": "CVE-2015-3220", "id": "pyup.io-35614", "more_info_path": "/vulnerabilities/CVE-2015-3220/35614", "specs": [ "<0.4.9" ], "v": "<0.4.9" } ], "tlslite-ng": [ { "advisory": "Tlslite-ng versions 0.7.6 and 0.8.0-alpha39 include a fix for CVE-2020-26263: Tlslite-ng is an open source python library that implements SSL and TLS cryptographic protocols. In tlslite-ng before versions 0.7.6 and 0.8.0-alpha39, the code that performs decryption and padding check in RSA PKCS#1 v1.5 decryption is data dependent. In particular, the code has multiple ways in which it leaks information about the decrypted ciphertext. It aborts as soon as the plaintext doesn't start with 0x00, 0x02. All TLS servers that enable RSA key exchange as well as applications that use the RSA decryption API directly are vulnerable. \r\nNote: the patches depend on Python processing the individual bytes in side-channel free manner, this is known to not the case (see reference). As such, users that require side-channel resistance are recommended to use different TLS implementations, as stated in the security policy of tlslite-ng.\r\nhttps://github.com/tlsfuzzer/tlslite-ng/security/advisories/GHSA-wvcv-832q-fjg7\r\nhttps://github.com/tlsfuzzer/tlslite-ng/commit/c28d6d387bba59d8bd5cb3ba15edc42edf54b368\r\nhttps://github.com/tlsfuzzer/tlslite-ng/pull/438\r\nhttps://github.com/tlsfuzzer/tlslite-ng/pull/439\r\nhttps://securitypitfalls.wordpress.com/2018/08/03/constant-time-compare-in-python/", "cve": "CVE-2020-26263", "id": "pyup.io-39343", "more_info_path": "/vulnerabilities/CVE-2020-26263/39343", "specs": [ "<0.7.6", ">=0.8.0-alpha1,<0.8.0-alpha39" ], "v": "<0.7.6,>=0.8.0-alpha1,<0.8.0-alpha39" }, { "advisory": "tlslite-ng version 0.7.3 and earlier, since commit d7b288316bca7bcdd082e6ccff5491e241305233 contains a CWE-354: Improper Validation of Integrity Check Value vulnerability in TLS implementation, tlslite/utils/constanttime.py: ct_check_cbc_mac_and_pad(); line \"end_pos = data_len - 1 - mac.digest_size\" that can result in an attacker manipulating the TLS ciphertext which will not be detected by receiving tlslite-ng. This attack appears to be exploitable via man in the middle on a network connection. This vulnerability appears to have been fixed after commit 3674815d1b0f7484454995e2737a352e0a6a93d8.", "cve": "CVE-2018-1000159", "id": "pyup.io-54208", "more_info_path": "/vulnerabilities/CVE-2018-1000159/54208", "specs": [ ">=0,<0.7.4" ], "v": ">=0,<0.7.4" } ], "tmt": [ { "advisory": "Rmt 0.19 makes the discover step a little bit more secure.", "cve": "PVE-2021-38635", "id": "pyup.io-38635", "more_info_path": "/vulnerabilities/PVE-2021-38635/38635", "specs": [ "<0.19" ], "v": "<0.19" } ], "toga-core": [ { "advisory": "Toga-core 0.3.0.dev15 updates its dependency 'Django' minimum requirement to versions ~2.2 to include security fixes.", "cve": "CVE-2017-7234", "id": "pyup.io-47144", "more_info_path": "/vulnerabilities/CVE-2017-7234/47144", "specs": [ "<0.3.0.dev15" ], "v": "<0.3.0.dev15" }, { "advisory": "Toga-core 0.3.0.dev15 updates its dependency 'Django' minimum requirement to versions ~2.2 to include security fixes.", "cve": "CVE-2017-7233", "id": "pyup.io-48157", "more_info_path": "/vulnerabilities/CVE-2017-7233/48157", "specs": [ "<0.3.0.dev15" ], "v": "<0.3.0.dev15" }, { "advisory": "Toga-core 0.3.0.dev15 updates its NPM dependency 'webpack-dev-server' minimum requirement to versions >=3.1.11 to include a security fix.", "cve": "CVE-2018-14732", "id": "pyup.io-48155", "more_info_path": "/vulnerabilities/CVE-2018-14732/48155", "specs": [ "<0.3.0.dev15" ], "v": "<0.3.0.dev15" }, { "advisory": "Toga-core 0.3.0.dev15 updates its NPM dependency 'eslint' minimum requirement to versions >=4.18.2 to include a fix for a ReDoS vulnerability.", "cve": "PVE-2017-47145", "id": "pyup.io-47145", "more_info_path": "/vulnerabilities/PVE-2017-47145/47145", "specs": [ "<0.3.0.dev15" ], "v": "<0.3.0.dev15" }, { "advisory": "Toga-core 0.3.0.dev15 updates its NPM dependency 'bootstrap' minimum requirement to versions >=4.3.1 to include a security fix.", "cve": "CVE-2019-8331", "id": "pyup.io-48156", "more_info_path": "/vulnerabilities/CVE-2019-8331/48156", "specs": [ "<0.3.0.dev15" ], "v": "<0.3.0.dev15" } ], "toggl-to-sqlite": [ { "advisory": "Toggl-to-sqlite 0.3.1 removes the 'api_token' from the workspaces table. The presence of this field presented a security issue if a user published their 'SQLite' database to a public source (like 'Vercel').", "cve": "PVE-2021-40617", "id": "pyup.io-40617", "more_info_path": "/vulnerabilities/PVE-2021-40617/40617", "specs": [ "<0.3.1" ], "v": "<0.3.1" }, { "advisory": "Certain versions of toggl-to-sqlite are vulnerable due to Insecure Defaults related to the `api_token` field. This vulnerability presents a security risk when users publish their SQLite database containing Toggl account data to public platforms.", "cve": "PVE-2024-99840", "id": "pyup.io-65580", "more_info_path": "/vulnerabilities/PVE-2024-99840/65580", "specs": [ ">=0,<0.3.1" ], "v": ">=0,<0.3.1" } ], "togglee": [ { "advisory": "The Togglee package in PyPI version v0.0.8 was discovered to contain a code execution backdoor. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.", "cve": "CVE-2022-34060", "id": "pyup.io-49647", "more_info_path": "/vulnerabilities/CVE-2022-34060/49647", "specs": [ "==0.0.8" ], "v": "==0.0.8" } ], "tomcatmanager": [ { "advisory": "Tomcatmanager 5.0.0 removed support for Python 3.6, which will not receive more security updates after 2021-12-23.", "cve": "CVE-2020-10735", "id": "pyup.io-42744", "more_info_path": "/vulnerabilities/CVE-2020-10735/42744", "specs": [ "<5.0.0" ], "v": "<5.0.0" } ], "tomproxies": [ { "advisory": "Tomproxies is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html", "cve": "PVE-2023-52914", "id": "pyup.io-52914", "more_info_path": "/vulnerabilities/PVE-2023-52914/52914", "specs": [ ">0" ], "v": ">0" } ], "tomtoolkit": [ { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2020-13596", "id": "pyup.io-38397", "more_info_path": "/vulnerabilities/CVE-2020-13596/38397", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2019-14235", "id": "pyup.io-49472", "more_info_path": "/vulnerabilities/CVE-2019-14235/49472", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2020-7471", "id": "pyup.io-49468", "more_info_path": "/vulnerabilities/CVE-2020-7471/49468", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2019-14233", "id": "pyup.io-49473", "more_info_path": "/vulnerabilities/CVE-2019-14233/49473", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2019-14232", "id": "pyup.io-49474", "more_info_path": "/vulnerabilities/CVE-2019-14232/49474", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2019-19118", "id": "pyup.io-49470", "more_info_path": "/vulnerabilities/CVE-2019-19118/49470", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2020-9402", "id": "pyup.io-49467", "more_info_path": "/vulnerabilities/CVE-2020-9402/49467", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2019-19844", "id": "pyup.io-49469", "more_info_path": "/vulnerabilities/CVE-2019-19844/49469", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2019-14234", "id": "pyup.io-49471", "more_info_path": "/vulnerabilities/CVE-2019-14234/49471", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2019-12781", "id": "pyup.io-49475", "more_info_path": "/vulnerabilities/CVE-2019-12781/49475", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2020-13254", "id": "pyup.io-49466", "more_info_path": "/vulnerabilities/CVE-2020-13254/49466", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 1.6.1 updates its dependency 'Django' requirement to '>=3.0.7' to include security fixes.", "cve": "CVE-2019-12308", "id": "pyup.io-49476", "more_info_path": "/vulnerabilities/CVE-2019-12308/49476", "specs": [ "<1.6.1" ], "v": "<1.6.1" }, { "advisory": "Tomtoolkit 2.14.1 disables multiple file uploads to fix CVE-2023-31047.\r\nhttps://github.com/TOMToolkit/tom_base/commit/eb2d7903e29f6f592452544d2c48e1a1236ca1e7", "cve": "CVE-2023-31047", "id": "pyup.io-58742", "more_info_path": "/vulnerabilities/CVE-2023-31047/58742", "specs": [ "<2.14.1" ], "v": "<2.14.1" } ], "toodledo": [ { "advisory": "Toodledo 1.5.0 adds a 'clear' keyword argument to TaskCache initialization. Setting 'clear' to True during initialization will clear and reload the cache.\r\nhttps://github.com/jikamens/toodledo-python/commit/2e84231eb58e7cba46e590aa43a4f0d2e7030449", "cve": "PVE-2024-63215", "id": "pyup.io-63215", "more_info_path": "/vulnerabilities/PVE-2024-63215/63215", "specs": [ "<1.5.0" ], "v": "<1.5.0" }, { "advisory": "Toodledo 1.5.0 addresses an edge-case bug in the logic surrounding caching rescheduled tasks. Previously, if a task was rescheduled after being cached, the cache would not reflect this change, leading to potential inconsistencies. This release fixes this issue, ensuring that rescheduled tasks are correctly updated in the cache.\r\nhttps://github.com/jikamens/toodledo-python/commit/207f97a75f273ff6a8b8c36c7e8829b735201062", "cve": "PVE-2024-63213", "id": "pyup.io-63213", "more_info_path": "/vulnerabilities/PVE-2024-63213/63213", "specs": [ "<1.5.0" ], "v": "<1.5.0" } ], "toolium": [ { "advisory": "Toolium 3.1.1 upgrades its readthedocs-sphinx-search to 0.3.2 to fix a security vulnerability.\r\nhttps://github.com/Telefonica/toolium/commit/3fe3e3b2564ea8fa8841568fc291eae6e7156941", "cve": "PVE-2024-64832", "id": "pyup.io-64832", "more_info_path": "/vulnerabilities/PVE-2024-64832/64832", "specs": [ "<3.1.1" ], "v": "<3.1.1" } ], "topobank-contact": [ { "advisory": "Topobank-contact 1.1.1 includes a fix for a CSRF vulnerability.\r\nhttps://github.com/ContactEngineering/topobank-contact/commit/fb71fd0893af91269dd61cd3af11250a50b77e88", "cve": "PVE-2023-60213", "id": "pyup.io-60213", "more_info_path": "/vulnerabilities/PVE-2023-60213/60213", "specs": [ "<1.1.1" ], "v": "<1.1.1" } ], "topobank-statistics": [ { "advisory": "Topobank-statistics 1.1.1 includes a fix for a CSRF vulnerability.\r\nhttps://github.com/ContactEngineering/topobank-statistics/commit/c842e7dd077170f7cc72ff5289fa62bd5cc460bc", "cve": "PVE-2023-60214", "id": "pyup.io-60214", "more_info_path": "/vulnerabilities/PVE-2023-60214/60214", "specs": [ "<1.1.1" ], "v": "<1.1.1" } ], "topydo": [ { "advisory": "topydo contains a CWE-20: Improper Input Validation vulnerability in ListFormatParser::parse, file topydo/lib/ListFormat.py line 292 as of d4f843dac71308b2f29a7c2cdc76f055c3841523 that can result in Injection of arbitrary bytes to the terminal, including terminal escape code sequences. This attack appear to be exploitable via The victim must open a todo.txt with at least one specially crafted line..", "cve": "CVE-2018-1000523", "id": "pyup.io-53987", "more_info_path": "/vulnerabilities/CVE-2018-1000523/53987", "specs": [ ">=0" ], "v": ">=0" } ], "torbot": [ { "advisory": "Torbot 4.0.0 includes a fix for CVE-2023-45813: In affected versions the 'torbot.modules.validators.validate_link function' uses the python-validators URL validation regex. This particular regular expression has an exponential complexity which allows an attacker to cause an application crash using a well-crafted argument. An attacker can use a well-crafted URL argument to exploit the vulnerability in the regular expression and cause a Denial of Service on the system. The validators file has been removed in version 4.0.0.\r\nhttps://github.com/DedSecInside/TorBot/security/advisories/GHSA-72qw-p7hh-m3ff", "cve": "CVE-2023-45813", "id": "pyup.io-61923", "more_info_path": "/vulnerabilities/CVE-2023-45813/61923", "specs": [ "<4.0.0" ], "v": "<4.0.0" } ], "torch": [ { "advisory": "Torch 1.10.0 addresses a data race condition in the torch.jit.annotations.parse_type_line function which allowed simultaneous reading and writing the set of devices without synchronizing.\r\nhttps://github.com/pytorch/pytorch/pull/58753", "cve": "PVE-2024-64663", "id": "pyup.io-64663", "more_info_path": "/vulnerabilities/PVE-2024-64663/64663", "specs": [ "<1.10.0" ], "v": "<1.10.0" }, { "advisory": "Torch 1.13 addresses a race condition issue in its database management. The bug occurred due to concurrent access to shared resources without adequate synchronization, causing unpredictable system behavior. The commit introduces changes to the torch::jit::GraphExecutor class in C++, improving the robustness of the system.\r\nhttps://github.com/pytorch/pytorch/commit/24a084eda69f2c636537a7614060382032565521", "cve": "PVE-2024-64660", "id": "pyup.io-64660", "more_info_path": "/vulnerabilities/PVE-2024-64660/64660", "specs": [ "<1.13" ], "v": "<1.13" }, { "advisory": "Torch 1.13.1 addresses a security vulnerability in the torch.jit.annotations.parse_type_line function, which could potentially allow command injection attacks. This was fixed by introducing the _eval_no_call method, which evaluates statements only if they do not contain any calls, thus preventing potential exploits. This update ensures that the torch.jit.annotations.get_signature function does not result in calling random code, enhancing the security of PyTorch applications.\r\nhttps://github.com/pytorch/pytorch/pull/89189/commits/4772e84f2067b474e0c50d8665a8586a05006861", "cve": "PVE-2024-64661", "id": "pyup.io-64661", "more_info_path": "/vulnerabilities/PVE-2024-64661/64661", "specs": [ "<1.13.1" ], "v": "<1.13.1" }, { "advisory": "PyTorch before v2.2.0 was discovered to contain a heap buffer overflow vulnerability in the component /runtime/vararg_functions.cpp. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted input.", "cve": "CVE-2024-31580", "id": "pyup.io-71671", "more_info_path": "/vulnerabilities/CVE-2024-31580/71671", "specs": [ "<2.2.0" ], "v": "<2.2.0" }, { "advisory": "Pytorch before version v2.2.0 was discovered to contain a use-after-free vulnerability in torch/csrc/jit/mobile/interpreter.cpp.", "cve": "CVE-2024-31583", "id": "pyup.io-71672", "more_info_path": "/vulnerabilities/CVE-2024-31583/71672", "specs": [ "<2.2.0" ], "v": "<2.2.0" }, { "advisory": "PyTorch is a Python package that provides tensor computation with strong GPU acceleration and deep neural networks built on a tape-based autograd system. In version 2.5.1 and prior, a Remote Command Execution (RCE) vulnerability exists in PyTorch when loading a model using torch.load with weights_only=True. This issue has been patched in version 2.6.0.", "cve": "CVE-2025-32434", "id": "pyup.io-76771", "more_info_path": "/vulnerabilities/CVE-2025-32434/76771", "specs": [ "<2.6.0" ], "v": "<2.6.0" }, { "advisory": "Affected versions of the PyTorch package are vulnerable to Denial of Service (DoS) due to improper handling in the MKLDNN pooling implementation. The torch.mkldnn_max_pool2d function fails to properly validate input parameters, allowing crafted inputs to trigger resource exhaustion or crashes in the underlying MKLDNN library. An attacker with local access can exploit this vulnerability by passing specially crafted tensor dimensions or parameters to the max pooling function, causing the application to become unresponsive or crash.", "cve": "CVE-2025-2953", "id": "pyup.io-78828", "more_info_path": "/vulnerabilities/CVE-2025-2953/78828", "specs": [ "<2.7.1-rc1" ], "v": "<2.7.1-rc1" }, { "advisory": "*Disputed* A vulnerability, which was classified as problematic, was found in PyTorch 2.6.0. Affected is the function torch.nn.functional.ctc_loss of the file aten/src/ATen/native/LossCTC.cpp. The manipulation leads to denial of service. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The name of the patch is 46fc5d8e360127361211cb237d5f9eef0223e567. It is recommended to apply a patch to fix this issue.", "cve": "CVE-2025-3730", "id": "pyup.io-76769", "more_info_path": "/vulnerabilities/CVE-2025-3730/76769", "specs": [ "<2.8.0" ], "v": "<2.8.0" }, { "advisory": "In PyTorch before trunk/89695, torch.jit.annotations.parse_type_line can cause arbitrary code execution because eval is used unsafely.", "cve": "CVE-2022-45907", "id": "pyup.io-54718", "more_info_path": "/vulnerabilities/CVE-2022-45907/54718", "specs": [ ">=0,<1.13.1" ], "v": ">=0,<1.13.1" } ], "torchgeo": [ { "advisory": "Affected versions of the TorchGeo package are vulnerable to Remote Code Execution due to improper control of code generation in the package's input processing functionality. The vulnerability exists in Microsoft TorchGeo versions before 0.6.1, where insufficient validation of user-supplied input allows injection of malicious code that gets executed by the application without proper sanitization. An unauthenticated remote attacker can exploit this vulnerability by sending specially crafted requests to an application using TorchGeo, achieving arbitrary code execution with the privileges of the running application and potentially compromising the confidentiality, integrity, and availability of the affected system.", "cve": "CVE-2024-49048", "id": "pyup.io-78817", "more_info_path": "/vulnerabilities/CVE-2024-49048/78817", "specs": [ "<0.6.1" ], "v": "<0.6.1" } ], "torchserve": [ { "advisory": "In the latest version of pytorch/serve, the script 'uploadresultsto_s3.sh' references the S3 bucket 'benchmarkai-metrics-prod' without ensuring its ownership or confirming its accessibility. This could lead to potential security vulnerabilities or unauthorized access to the bucket if it is not properly secured or claimed by the appropriate entity. The issue may result in data breaches, exposure of proprietary information, or unauthorized modifications to stored data.", "cve": "CVE-2024-6577", "id": "pyup.io-76252", "more_info_path": "/vulnerabilities/CVE-2024-6577/76252", "specs": [ "<0.11.0" ], "v": "<0.11.0" }, { "advisory": "TorchServe 's check on allowed_urls configuration can be bypassed if the URL contains characters such as \"..\" but it does not prevent the model from being downloaded into the model store. Once a file is downloaded, it can be referenced without providing a URL the second time, which effectively bypasses the allowed_urls security check. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are unaffected.", "cve": "CVE-2024-35198", "id": "pyup.io-72281", "more_info_path": "/vulnerabilities/CVE-2024-35198/72281", "specs": [ "<0.11.0" ], "v": "<0.11.0" }, { "advisory": "Torchserve 0.5.1 updates its dependency 'log4j' to v2.16.0 to include a fix for a critical vulnerability.", "cve": "CVE-2021-44228", "id": "pyup.io-43736", "more_info_path": "/vulnerabilities/CVE-2021-44228/43736", "specs": [ "<0.5.1" ], "v": "<0.5.1" }, { "advisory": "Torchserve 0.5.1 updates its dependency 'log4j2' to v2.16.0 to fix critical vulnerabilities.", "cve": "CVE-2021-45046", "id": "pyup.io-43744", "more_info_path": "/vulnerabilities/CVE-2021-45046/43744", "specs": [ "<0.5.1" ], "v": "<0.5.1" }, { "advisory": "Torchserve 0.5.2 updates its dependency 'log4j2' to v2.17.0 to fix a vulnerability.", "cve": "CVE-2021-45105", "id": "pyup.io-43735", "more_info_path": "/vulnerabilities/CVE-2021-45105/43735", "specs": [ "<0.5.2" ], "v": "<0.5.2" }, { "advisory": "Torchserve 0.5.3 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "PVE-2021-44525", "id": "pyup.io-48565", "more_info_path": "/vulnerabilities/PVE-2021-44525/48565", "specs": [ "<0.5.3" ], "v": "<0.5.3" }, { "advisory": "Torchserve 0.5.3 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22815", "id": "pyup.io-48563", "more_info_path": "/vulnerabilities/CVE-2022-22815/48563", "specs": [ "<0.5.3" ], "v": "<0.5.3" }, { "advisory": "Torchserve 0.5.3 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "PVE-2022-44524", "id": "pyup.io-48566", "more_info_path": "/vulnerabilities/PVE-2022-44524/48566", "specs": [ "<0.5.3" ], "v": "<0.5.3" }, { "advisory": "Torchserve 0.5.3 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22816", "id": "pyup.io-48564", "more_info_path": "/vulnerabilities/CVE-2022-22816/48564", "specs": [ "<0.5.3" ], "v": "<0.5.3" }, { "advisory": "Torchserve 0.5.3 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2021-34552", "id": "pyup.io-48562", "more_info_path": "/vulnerabilities/CVE-2021-34552/48562", "specs": [ "<0.5.3" ], "v": "<0.5.3" }, { "advisory": "Torchserve 0.5.3 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2021-23437", "id": "pyup.io-48553", "more_info_path": "/vulnerabilities/CVE-2021-23437/48553", "specs": [ "<0.5.3" ], "v": "<0.5.3" }, { "advisory": "Torchserve 0.6.1 updates its MAVEN dependency 'gson' to v2.9.0 to include a security fix.", "cve": "CVE-2022-25647", "id": "pyup.io-52398", "more_info_path": "/vulnerabilities/CVE-2022-25647/52398", "specs": [ "<0.6.1" ], "v": "<0.6.1" }, { "advisory": "TorchServe is a tool for serving and scaling PyTorch models in production. Starting in version 0.1.0 and prior to version 0.9.0, using the model/workflow management API, there is a chance of uploading potentially harmful archives that contain files that are extracted to any location on the filesystem that is within the process permissions. Leveraging this issue could aid third-party actors in hiding harmful code in open-source/public models, which can be downloaded from the internet, and take advantage of machines running Torchserve. The ZipSlip issue in TorchServe has been fixed by validating the paths of files contained within a zip archive before extracting them. TorchServe release 0.9.0 includes fixes to address the ZipSlip vulnerability.", "cve": "CVE-2023-48299", "id": "pyup.io-65345", "more_info_path": "/vulnerabilities/CVE-2023-48299/65345", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Torchserve 0.5.2 includes a version of'log4j2' affected by a medium severity vulnerability.", "cve": "CVE-2021-44832", "id": "pyup.io-44463", "more_info_path": "/vulnerabilities/CVE-2021-44832/44463", "specs": [ "<=0.5.2" ], "v": "<=0.5.2" }, { "advisory": "TorchServe is a tool for serving and scaling PyTorch models in production. TorchServe default configuration lacks proper input validation, enabling third parties to invoke remote HTTP download requests and write files to the disk. This issue could be taken advantage of to compromise the integrity of the system and sensitive data. This issue is present in versions 0.1.0 to 0.8.1. A user is able to load the model of their choice from any URL that they would like to use. The user of TorchServe is responsible for configuring both the allowed_urls and specifying the model URL to be used. A pull request to warn the user when the default value for allowed_urls is used has been merged in PR #2534. TorchServe release 0.8.2 includes this change. Users are advised to upgrade. There are no known workarounds for this issue.", "cve": "CVE-2023-43654", "id": "pyup.io-65346", "more_info_path": "/vulnerabilities/CVE-2023-43654/65346", "specs": [ ">=0.1.0,<0.8.2" ], "v": ">=0.1.0,<0.8.2" }, { "advisory": "In affected versions, the two gRPC ports 7070 and 7071, are not bound to localhost by default, so when TorchServe is launched, these two interfaces are bound to all interfaces. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are unaffected.", "cve": "CVE-2024-35199", "id": "pyup.io-72280", "more_info_path": "/vulnerabilities/CVE-2024-35199/72280", "specs": [ ">=0.3.0,<0.11.0" ], "v": ">=0.3.0,<0.11.0" }, { "advisory": "Certain versions of TorchServe are susceptible to an OS Command Injection vulnerability due to improper neutralization of special elements used in an operating system command. This flaw allows attackers to execute arbitrary OS commands, potentially leading to unauthorized actions or data access. To mitigate this risk, users should review their system configurations and apply recommended security practices for TorchServe.", "cve": "PVE-2024-68053", "id": "pyup.io-68053", "more_info_path": "/vulnerabilities/PVE-2024-68053/68053", "specs": [ ">=0.3.0,<0.8.2" ], "v": ">=0.3.0,<0.8.2" } ], "torchtriton": [ { "advisory": "Torchtriton is malicious package that impersonated the library with the same name published on the PyTorch-nightly's repo. This one steals your sensitive files when imported.\r\nhttps://www.bleepingcomputer.com/news/security/pytorch-discloses-malicious-dependency-chain-compromise-over-holidays", "cve": "PVE-2023-52923", "id": "pyup.io-52923", "more_info_path": "/vulnerabilities/PVE-2023-52923/52923", "specs": [ ">0" ], "v": ">0" } ], "tornado": [ { "advisory": "CRLF injection vulnerability in the tornado.web.RequestHandler.set_header function in Tornado before 2.2.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via crafted input.", "cve": "CVE-2012-2374", "id": "pyup.io-26161", "more_info_path": "/vulnerabilities/CVE-2012-2374/26161", "specs": [ "<2.2.1" ], "v": "<2.2.1" }, { "advisory": "Tornado 6.3.2 includes a fix for CVE-2023-28370: Open redirect vulnerability in Tornado versions 6.3.1 and earlier allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having user access a specially crafted URL.", "cve": "CVE-2023-28370", "id": "pyup.io-59071", "more_info_path": "/vulnerabilities/CVE-2023-28370/59071", "specs": [ "<6.3.2" ], "v": "<6.3.2" }, { "advisory": "Summary: Tornado's interpretation of symbols `-`, `+`, and `_` within chunk lengths and 'Content-Length' values contradicts the HTTP RFCs stipulations, potentially creating an avenue for request smuggling. This issue is generally found when Tornado operates behind specific proxies that understand these non-standard characters diversely, mostly observed in earlier versions of 'haproxy'; however, the latest version remains unaffected.\r\n\r\nDetails: Tornado utilizes the 'int' constructor to decipher the 'Content-Length' headers and chunk lengths in the locations mentioned below:\r\n\r\n`tornado/http1connection.py:445`\r\nPython3 code: self._expected_content_remaining = int(headers[\"Content-Length\"])\r\n\r\n`tornado/http1connection.py:621`\r\nPython3 code: content_length = int(headers[\"Content-Length\"])\r\n\r\n`tornado/http1connection.py:671`\r\nPython3 code: chunk_len = int(chunk_len_str.strip(), 16)\r\n\r\nNotably, though the equation `int(\"0_0\")` equates to `int(\"+0\")`, `int(\"-0\")`, and `int(\"0\")`, using the 'int' constructor as a strategy for validating and parsing strings containing ASCII digits only is proven inadequate.", "cve": "PVE-2023-99925", "id": "pyup.io-61949", "more_info_path": "/vulnerabilities/PVE-2023-99925/61949", "specs": [ "<6.3.3" ], "v": "<6.3.3" }, { "advisory": "Tornado\u2019s curl_httpclient.CurlAsyncHTTPClient class is vulnerable to CRLF (carriage return/line feed) injection in the request headers.", "cve": "PVE-2024-71956", "id": "pyup.io-71956", "more_info_path": "/vulnerabilities/PVE-2024-71956/71956", "specs": [ "<6.4.1" ], "v": "<6.4.1" }, { "advisory": "Tornado web framework affected versions contain a performance vulnerability in their HTTP cookie parser. When processing specially crafted malicious cookie headers, the parser's algorithm can exhibit quadratic time complexity. Since this parsing happens in the main event loop thread, it can cause the server to become unresponsive and block the processing of other incoming requests due to excessive CPU usage.", "cve": "CVE-2024-52804", "id": "pyup.io-74439", "more_info_path": "/vulnerabilities/CVE-2024-52804/74439", "specs": [ "<6.4.2" ], "v": "<6.4.2" }, { "advisory": "When Tornado's multipart/form-data parser encounters certain errors, it logs a warning but continues trying to parse the remainder of the data. This allows remote attackers to generate an extremely high volume of logs, constituting a DoS attack. This DoS is compounded by the fact that the logging subsystem is synchronous.", "cve": "CVE-2025-47287", "id": "pyup.io-77319", "more_info_path": "/vulnerabilities/CVE-2025-47287/77319", "specs": [ "<6.5.0" ], "v": "<6.5.0" }, { "advisory": "When Tornado receives a request with two Transfer-Encoding: chunked headers, it ignores them both. This enables request smuggling when Tornado is deployed behind a proxy server that emits such requests. Pound does this.", "cve": "PVE-2024-71957", "id": "pyup.io-71957", "more_info_path": "/vulnerabilities/PVE-2024-71957/71957", "specs": [ "<=6.4.0" ], "v": "<=6.4.0" }, { "advisory": "Tornado before 3.2.2 sends arbitrary responses that contain a fixed CSRF token and may be sent with HTTP compression, which makes it easier for remote attackers to conduct a BREACH attack and determine this token via a series of crafted requests.", "cve": "CVE-2014-9720", "id": "pyup.io-54090", "more_info_path": "/vulnerabilities/CVE-2014-9720/54090", "specs": [ ">=0,<3.2.2" ], "v": ">=0,<3.2.2" }, { "advisory": "The versions of Tornado from v3.1.0 to v4.2.0 contain a path traversal vulnerability.", "cve": "PVE-2023-99976", "id": "pyup.io-60832", "more_info_path": "/vulnerabilities/PVE-2023-99976/60832", "specs": [ ">=3.1.0,<4.2.1" ], "v": ">=3.1.0,<4.2.1" } ], "tortoise-orm": [ { "advisory": "Tortoise-orm versions 0.15.23 and 0.16.6 include a fix for CVE-2020-11010: In Tortoise ORM before versions 0.15.23 and 0.16.6, various forms of SQL injection have been found for MySQL and when filtering or doing mass-updates on char/text fields. SQLite and PostgreSQL are only affected when filtering with contains, starts_with, or ends_with filters (and their case-insensitive counterparts).\r\nhttps://github.com/tortoise/tortoise-orm/commit/91c364053e0ddf77edc5442914c6f049512678b3\r\nhttps://github.com/tortoise/tortoise-orm/security/advisories/GHSA-9j2c-x8qm-qmjq", "cve": "CVE-2020-11010", "id": "pyup.io-38916", "more_info_path": "/vulnerabilities/CVE-2020-11010/38916", "specs": [ "<0.15.23", ">=0.16.0,<0.16.6" ], "v": "<0.15.23,>=0.16.0,<0.16.6" } ], "toucan-connectors": [ { "advisory": "Toucan-connectors 3.18.2 sanitizes SQL for athena connector in order to prevent SQL injection.\r\nhttps://github.com/ToucanToco/toucan-connectors/pull/649", "cve": "PVE-2022-50729", "id": "pyup.io-50729", "more_info_path": "/vulnerabilities/PVE-2022-50729/50729", "specs": [ "<3.18.2" ], "v": "<3.18.2" } ], "toui": [ { "advisory": "Toui 2.4.1 includes a fix for CVE-2023-33175: ToUI is using Flask-Caching (SimpleCache) to store user variables. These are stored in the server side. Websites that use 'Website.user_vars' property are affected.\r\nhttps://github.com/mubarakalmehairbi/ToUI/security/advisories/GHSA-hh7j-pg39-q563", "cve": "CVE-2023-33175", "id": "pyup.io-58838", "more_info_path": "/vulnerabilities/CVE-2023-33175/58838", "specs": [ ">=2.0.1,<2.4.1" ], "v": ">=2.0.1,<2.4.1" } ], "tqdm": [ { "advisory": "The tqdm._version module in tqdm versions before 4.11.2 allows local users to execute arbitrary code via a crafted repo with a malicious git log in the current working directory.", "cve": "CVE-2016-10075", "id": "pyup.io-34741", "more_info_path": "/vulnerabilities/CVE-2016-10075/34741", "specs": [ "<4.11.2" ], "v": "<4.11.2" }, { "advisory": "Tqdm version 4.66.3 addresses CVE-2024-34062, a vulnerability where optional non-boolean CLI arguments like `--delim`, `--buf-size`, and `--manpath` were passed through Python's `eval`, allowing for arbitrary code execution. This security risk, only locally exploitable, has been mitigated in this release. Users are advised to upgrade to version 4.66.3 immediately as there are no workarounds for this issue.", "cve": "CVE-2024-34062", "id": "pyup.io-70790", "more_info_path": "/vulnerabilities/CVE-2024-34062/70790", "specs": [ ">=4.4.0,<4.66.3" ], "v": ">=4.4.0,<4.66.3" } ], "trac": [ { "advisory": "Trac before 0.8.4 allows remote attackers to read or upload arbitrary files via a full pathname in the id parameter to the (1) upload or (2) attachment viewer scripts.", "cve": "CVE-2005-2147", "id": "pyup.io-61155", "more_info_path": "/vulnerabilities/CVE-2005-2147/61155", "specs": [ "<0.8.4" ], "v": "<0.8.4" }, { "advisory": "Directory traversal vulnerability in Edgewall Trac 0.8.3 and earlier allows remote attackers to read or write arbitrary files via a .. (dot dot) in the id parameter to the (1) upload or (2) attachment scripts.", "cve": "CVE-2005-2007", "id": "pyup.io-61153", "more_info_path": "/vulnerabilities/CVE-2005-2007/61153", "specs": [ "<=0.8.3" ], "v": "<=0.8.3" }, { "advisory": "SQL injection vulnerability in the ticket query module in Edgewall Trac 0.9 and possibly earlier allows remote attackers to execute arbitrary SQL commands via the group parameter.", "cve": "CVE-2005-3980", "id": "pyup.io-61138", "more_info_path": "/vulnerabilities/CVE-2005-3980/61138", "specs": [ "<=0.9" ], "v": "<=0.9" }, { "advisory": "Cross-site scripting (XSS) vulnerability in Edgewall Software Trac 0.9.4 and earlier allows remote attackers to inject arbitrary web script or HTML via unknown attack vectors related to a \"wiki macro.\"", "cve": "CVE-2006-2106", "id": "pyup.io-61140", "more_info_path": "/vulnerabilities/CVE-2006-2106/61140", "specs": [ "<=0.9.4" ], "v": "<=0.9.4" }, { "advisory": "Trac 0.11.6 does not properly check workflow permissions before modifying a ticket. This can be exploited by an attacker to change the status and resolution of tickets without having proper permissions.", "cve": "CVE-2010-5108", "id": "pyup.io-61744", "more_info_path": "/vulnerabilities/CVE-2010-5108/61744", "specs": [ ">0.11.5,<0.11.7" ], "v": ">0.11.5,<0.11.7" }, { "advisory": "Cross-site scripting (XSS) vulnerability in the HTML WikiProcessor in Edgewall Trac 0.9.2 allows remote attackers to inject arbitrary web script or HTML via javascript in the SRC attribute of an IMG tag.", "cve": "CVE-2005-4644", "id": "pyup.io-53871", "more_info_path": "/vulnerabilities/CVE-2005-4644/53871", "specs": [ ">=0,<0.10" ], "v": ">=0,<0.10" }, { "advisory": "Trac before 0.10.3.1 does not send a Content-Disposition HTTP header specifying an attachment in certain \"unsafe\" situations, which has unknown impact and remote attack vectors.", "cve": "CVE-2007-1406", "id": "pyup.io-53966", "more_info_path": "/vulnerabilities/CVE-2007-1406/53966", "specs": [ ">=0,<0.10.3.1" ], "v": ">=0,<0.10.3.1" }, { "advisory": "Cross-site scripting (XSS) vulnerability in the \"download wiki page as text\" feature in Trac before 0.10.3.1, when Microsoft Internet Explorer is used, allows remote attackers to inject arbitrary web script or HTML via unspecified parameters.", "cve": "CVE-2007-1405", "id": "pyup.io-53965", "more_info_path": "/vulnerabilities/CVE-2007-1405/53965", "specs": [ ">=0,<0.10.3.1" ], "v": ">=0,<0.10.3.1" }, { "advisory": "Open redirect vulnerability in the search script in Trac before 0.10.5 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the q parameter, possibly related to the quickjump function.", "cve": "CVE-2008-2951", "id": "pyup.io-54036", "more_info_path": "/vulnerabilities/CVE-2008-2951/54036", "specs": [ ">=0,<0.10.5" ], "v": ">=0,<0.10.5" }, { "advisory": "Cross-site scripting (XSS) vulnerability in the wiki engine in Trac before 0.10.5 allows remote attackers to inject arbitrary web script or HTML via unknown vectors.", "cve": "CVE-2008-3328", "id": "pyup.io-54037", "more_info_path": "/vulnerabilities/CVE-2008-3328/54037", "specs": [ ">=0,<0.10.5" ], "v": ">=0,<0.10.5" }, { "advisory": "Cross-site request forgery (CSRF) vulnerability in Edgewall Trac 0.10 and earlier allows remote attackers to perform unauthorized actions as other users via unknown vectors.", "cve": "CVE-2006-5878", "id": "pyup.io-53919", "more_info_path": "/vulnerabilities/CVE-2006-5878/53919", "specs": [ ">=0,<0.11" ], "v": ">=0,<0.11" }, { "advisory": "Unspecified vulnerability in Trac before 0.11.2 allows attackers to cause a denial of service via unknown attack vectors related to \"certain wiki markup.\"", "cve": "CVE-2008-5646", "id": "pyup.io-54211", "more_info_path": "/vulnerabilities/CVE-2008-5646/54211", "specs": [ ">=0,<0.11.2" ], "v": ">=0,<0.11.2" }, { "advisory": "Unspecified vulnerability in the HTML sanitizer filter in Trac before 0.11.2 allows attackers to conduct phishing attacks via unknown attack vectors.", "cve": "CVE-2008-5647", "id": "pyup.io-54038", "more_info_path": "/vulnerabilities/CVE-2008-5647/54038", "specs": [ ">=0,<0.11.2" ], "v": ">=0,<0.11.2" }, { "advisory": "Multiple unspecified vulnerabilities in Trac before 0.11.6 have unknown impact and attack vectors, possibly related to (1) 'policy checks in report results when using alternate formats' or (2) a 'check for the raw role that is missing in docutils < 0.6.'", "cve": "CVE-2009-4405", "id": "pyup.io-54212", "more_info_path": "/vulnerabilities/CVE-2009-4405/54212", "specs": [ ">=0,<0.11.6" ], "v": ">=0,<0.11.6" }, { "advisory": "Trac before 0.9.6 does not disable the \"raw\" or \"include\" commands when providing untrusted users with restructured text (reStructuredText) functionality from docutils, which allows remote attackers to read arbitrary files, perform cross-site scripting (XSS) attacks, or cause a denial of service via unspecified vectors. NOTE: this might be related to CVE-2006-3458.", "cve": "CVE-2006-3695", "id": "pyup.io-53918", "more_info_path": "/vulnerabilities/CVE-2006-3695/53918", "specs": [ ">=0,<0.9.6" ], "v": ">=0,<0.9.6" }, { "advisory": "SQL injection vulnerability in the search module in Edgewall Trac before 0.9.2 allows remote attackers to execute arbitrary SQL commands via unknown vectors.", "cve": "CVE-2005-4065", "id": "pyup.io-61285", "more_info_path": "/vulnerabilities/CVE-2005-4065/61285", "specs": [ ">=0.7.1,<0.9.2" ], "v": ">=0.7.1,<0.9.2" }, { "advisory": "Cross-site scripting (XSS) vulnerability in Edgewall Trac 0.9, 0.9.1, and 0.9.2 allows remote attackers to inject arbitrary web script or HTML via the URL, which is not properly sanitized before it is returned in an error page.", "cve": "CVE-2005-4305", "id": "pyup.io-61139", "more_info_path": "/vulnerabilities/CVE-2005-4305/61139", "specs": [ ">=0.9,<=0.9.2" ], "v": ">=0.9,<=0.9.2" } ], "tracauthopenid": [ { "advisory": "Tracauthopenid before 0.4.4 does not properly authorize if no email address was returned via AX or SREG. The 'email_white_list' config option was being ignored. Now, if 'email_white_list' is set and no email address can be determined, authorization will be denied.", "cve": "PVE-2021-26162", "id": "pyup.io-26162", "more_info_path": "/vulnerabilities/PVE-2021-26162/26162", "specs": [ "<0.4.4" ], "v": "<0.4.4" }, { "advisory": "Select versions of the tracauthopenid, an OpenID plugin for Trac, are susceptible to Access Restriction Bypass. This vulnerability is triggered when an email address is not returned through AX or SREG protocols, resulting in the email_white_list configuration option being overlooked.", "cve": "PVE-2024-99838", "id": "pyup.io-65582", "more_info_path": "/vulnerabilities/PVE-2024-99838/65582", "specs": [ ">=0,<0.4.4" ], "v": ">=0,<0.4.4" } ], "trackthenews": [ { "advisory": "Trackthenews 0.1.10 includes a security patch for the function 'main' in 'trackthenews/core.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load(). \r\nhttps://github.com/freedomofpress/trackthenews/commit/7ef1ae9d3ac2793e55d9df4161eddb46ff9a9fde", "cve": "CVE-2017-18342", "id": "pyup.io-41397", "more_info_path": "/vulnerabilities/CVE-2017-18342/41397", "specs": [ "<0.1.10" ], "v": "<0.1.10" } ], "transformers": [ { "advisory": "Transformers version 2.0 updates its tensorflow dependency from 2.8.1 to 2.11.1 to address the security vulnerability identified as CVE-2023-25668.", "cve": "CVE-2023-25668", "id": "pyup.io-71289", "more_info_path": "/vulnerabilities/CVE-2023-25668/71289", "specs": [ "<2.0" ], "v": "<2.0" }, { "advisory": "Affected versions of Hugging Face Transformers are potentially vulnerable to a shell injection vulnerability. The issue occurs in the workflow configuration where the branch name is directly passed to the benchmark entry point script.", "cve": "PVE-2025-76057", "id": "pyup.io-76057", "more_info_path": "/vulnerabilities/PVE-2025-76057/76057", "specs": [ "<3.1" ], "v": "<3.1" }, { "advisory": "Transformers 4.23.0 includes a fix for a link vulnerable to repojacking.\r\nhttps://github.com/huggingface/transformers/commit/ce2620194b4a8f070cd29504d34a79758affdf95", "cve": "PVE-2022-51450", "id": "pyup.io-51450", "more_info_path": "/vulnerabilities/PVE-2022-51450/51450", "specs": [ "<4.23.0" ], "v": "<4.23.0" }, { "advisory": "Transformers 4.23.0 updates its dependency 'protobuf' requirement to '<=3.20.2' to include a security fix.", "cve": "CVE-2022-1941", "id": "pyup.io-51396", "more_info_path": "/vulnerabilities/CVE-2022-1941/51396", "specs": [ "<4.23.0" ], "v": "<4.23.0" }, { "advisory": "Transformers 4.30.0 includes a fix for an Insecure Temporary File vulnerability.\r\nhttps://github.com/huggingface/transformers/commit/80ca92470938bbcc348e2d9cf4734c7c25cb1c43", "cve": "CVE-2023-2800", "id": "pyup.io-60235", "more_info_path": "/vulnerabilities/CVE-2023-2800/60235", "specs": [ "<4.30.0" ], "v": "<4.30.0" }, { "advisory": "Transformers is affected by a shell injection vulnerability. It appears that while this issue is generally not critical for the library's primary use cases, it can become more significant in specific production environments. Particularly in scenarios where the library interacts with user-generated input \u2014 such as in web application backends, desktop applications, and cloud-based ML services \u2014 the risk of arbitrary code execution increases.\r\nhttps://github.com/huggingface/transformers/pull/28299", "cve": "PVE-2024-64402", "id": "pyup.io-64402", "more_info_path": "/vulnerabilities/PVE-2024-64402/64402", "specs": [ "<4.37.0" ], "v": "<4.37.0" }, { "advisory": "The huggingface/transformers library is vulnerable to arbitrary code execution through deserialization of untrusted data within the `load_repo_checkpoint()` function of the `TFPreTrainedModel()` class. Attackers can execute arbitrary code and commands by crafting a malicious serialized payload, exploiting the use of `pickle.load()` on data from potentially untrusted sources. This vulnerability allows for remote code execution (RCE) by deceiving victims into loading a seemingly harmless checkpoint during a normal training process, thereby enabling attackers to execute arbitrary code on the targeted machine.", "cve": "CVE-2024-3568", "id": "pyup.io-71601", "more_info_path": "/vulnerabilities/CVE-2024-3568/71601", "specs": [ "<4.38.0" ], "v": "<4.38.0" }, { "advisory": "Transformers version 4.41.0 updates its `aiohttp` dependency from version 3.8.5 to 3.9.0 to address the security vulnerability identified as CVE-2023-49082.", "cve": "CVE-2023-49082", "id": "pyup.io-71048", "more_info_path": "/vulnerabilities/CVE-2023-49082/71048", "specs": [ "<4.41.0" ], "v": "<4.41.0" }, { "advisory": "Transformers version 4.41.0 updates its `aiohttp` dependency from version 3.8.5 to 3.9.0 to address the security vulnerability identified as CVE-2023-49081.", "cve": "CVE-2023-49081", "id": "pyup.io-71037", "more_info_path": "/vulnerabilities/CVE-2023-49081/71037", "specs": [ "<4.41.0" ], "v": "<4.41.0" }, { "advisory": "Transformers version 4.41.0 updates its `black` dependency from version 22.1.0 to 24.3.0 to address the security vulnerability identified as CVE-2024-21503.", "cve": "CVE-2024-21503", "id": "pyup.io-71049", "more_info_path": "/vulnerabilities/CVE-2024-21503/71049", "specs": [ "<4.41.0" ], "v": "<4.41.0" }, { "advisory": "Affected versions of the transformers package are vulnerable to Deserialization of Untrusted Data due to improper validation when handling Trax model files. The vulnerability exists in versions before 4.48.0, where the model file parsing functionality lacks proper validation of user-supplied data, allowing deserialization of malicious payloads embedded in model files without verification. An attacker can exploit this vulnerability by crafting a malicious Trax model file and convincing a target user to load it through the application, resulting in arbitrary code execution within the context of the current user when the model is processed.", "cve": "CVE-2024-11394", "id": "pyup.io-78822", "more_info_path": "/vulnerabilities/CVE-2024-11394/78822", "specs": [ "<4.48.0" ], "v": "<4.48.0" }, { "advisory": "Affected versions of the transformers package are vulnerable to Deserialization of Untrusted Data due to improper validation when handling MobileViTV2 configuration files. The vulnerability exists in versions before 4.48.0, where the configuration file parsing functionality fails to properly validate user-supplied data, allowing malicious YAML configuration files to be deserialized without proper sanitization checks. An attacker can exploit this vulnerability by crafting a malicious configuration file and convincing a target user to process it using the convert_mlcvnets_to_pytorch.py script, resulting in arbitrary code execution within the context of the current user when the configuration is loaded.", "cve": "CVE-2024-11392", "id": "pyup.io-78823", "more_info_path": "/vulnerabilities/CVE-2024-11392/78823", "specs": [ "<4.48.0" ], "v": "<4.48.0" }, { "advisory": "Transformers 4.5.0 includes various vulnerability fixes.", "cve": "PVE-2021-40187", "id": "pyup.io-40187", "more_info_path": "/vulnerabilities/PVE-2021-40187/40187", "specs": [ "<4.5.0" ], "v": "<4.5.0" }, { "advisory": "Affected versions of the Transformers package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks in multiple tokenizer components. The vulnerability exists in regex patterns used by the Nougat, GPTSan Japanese, and GPT-NeoX Japanese tokenizers that are susceptible to catastrophic backtracking. \r\n\r\nA remote attacker can exploit this vulnerability by providing specially crafted input strings to these tokenizers, causing excessive CPU consumption through exponential time complexity in regex processing, resulting in service disruption and resource exhaustion.\r\n\r\nThe vulnerability was fixed by refactoring the vulnerable regex patterns to eliminate backtracking potential. The fix converts problematic patterns that use nested quantifiers and alternations into more efficient implementations.", "cve": "CVE-2025-1194", "id": "pyup.io-77149", "more_info_path": "/vulnerabilities/CVE-2025-1194/77149", "specs": [ "<4.50.0" ], "v": "<4.50.0" }, { "advisory": "A vulnerability in the `preprocess_string()` function of the `transformers.testing_utils` module in huggingface/transformers version v4.48.3 allows for a Regular Expression Denial of Service (ReDoS) attack. The regular expression used to process code blocks in docstrings contains nested quantifiers, leading to exponential backtracking when processing input with a large number of newline characters. An attacker can exploit this by providing a specially crafted payload, causing high CPU usage and potential application downtime, effectively resulting in a Denial of Service (DoS) scenario.", "cve": "CVE-2025-2099", "id": "pyup.io-77714", "more_info_path": "/vulnerabilities/CVE-2025-2099/77714", "specs": [ "<4.50.0" ], "v": "<4.50.0" }, { "advisory": "A Regular Expression Denial of Service (ReDoS) vulnerability was discovered in the Hugging Face Transformers library, specifically in the `get_configuration_file()` function within the `transformers.configuration_utils` module. The affected version is 4.49.0, and the issue is resolved in version 4.51.0. The vulnerability arises from the use of a regular expression pattern `config\\.(.*)\\.json` that can be exploited to cause excessive CPU consumption through crafted input strings, leading to catastrophic backtracking. This can result in model serving disruption, resource exhaustion, and increased latency in applications using the library.", "cve": "CVE-2025-3263", "id": "pyup.io-77985", "more_info_path": "/vulnerabilities/CVE-2025-3263/77985", "specs": [ "<4.51.0" ], "v": "<4.51.0" }, { "advisory": "A Regular Expression Denial of Service (ReDoS) vulnerability was discovered in the Hugging Face Transformers library, specifically in the `get_imports()` function within `dynamic_module_utils.py`. This vulnerability affects versions 4.49.0 and is fixed in version 4.51.0. The issue arises from a regular expression pattern `\\s*try\\s*:.*?except.*?:` used to filter out try/except blocks from Python code, which can be exploited to cause excessive CPU consumption through crafted input strings due to catastrophic backtracking. This vulnerability can lead to remote code loading disruption, resource exhaustion in model serving, supply chain attack vectors, and development pipeline disruption.", "cve": "CVE-2025-3264", "id": "pyup.io-77988", "more_info_path": "/vulnerabilities/CVE-2025-3264/77988", "specs": [ "<4.51.0" ], "v": "<4.51.0" }, { "advisory": "Hugging Face Transformers versions up to 4.49.0 are affected by an improper input validation vulnerability in the `image_utils.py` file. The vulnerability arises from insecure URL validation using the `startswith()` method, which can be bypassed through URL username injection. This allows attackers to craft URLs that appear to be from YouTube but resolve to malicious domains, potentially leading to phishing attacks, malware distribution, or data exfiltration. The issue is fixed in version 4.52.1.", "cve": "CVE-2025-3777", "id": "pyup.io-77986", "more_info_path": "/vulnerabilities/CVE-2025-3777/77986", "specs": [ "<4.52.1" ], "v": "<4.52.1" }, { "advisory": "Affected versions of the Hugging Face Transformers package are vulnerable to Regular Expression Denial of Service (ReDoS) due to an inefficient regex pattern in weight name conversion. The convert_tf_weight_name_to_pt_weight_name() function uses the regular expression pattern /[^/]*___([^/]*)/, which is susceptible to catastrophic backtracking when processing specially crafted TensorFlow weight names. An attacker can exploit this vulnerability by providing malicious weight names during model conversion between TensorFlow and PyTorch formats, causing excessive CPU consumption and potentially rendering the service unresponsive.", "cve": "CVE-2025-5197", "id": "pyup.io-78688", "more_info_path": "/vulnerabilities/CVE-2025-5197/78688", "specs": [ "<4.53.0" ], "v": "<4.53.0" }, { "advisory": "Affected versions of the transformers package are vulnerable to Regular Expression Denial of Service (ReDoS) due to inefficient regular expressions in the EnglishNormalizer.normalize_numbers() method. The normalize_numbers() implementation in src/transformers/models/clvp/number_normalizer.py applies number-matching patterns such as ([0-9][0-9,]+[0-9]) to untrusted input without atomic grouping or bounds, allowing catastrophic backtracking and excessive CPU consumption.", "cve": "CVE-2025-6051", "id": "pyup.io-79595", "more_info_path": "/vulnerabilities/CVE-2025-6051/79595", "specs": [ "<4.53.0" ], "v": "<4.53.0" }, { "advisory": "Affected versions of the transformers package are vulnerable to Regular Expression Denial of Service (ReDoS) due to inefficient regular expressions in the MarianTokenizer.remove_language_code() method. The method compiles a language-code pattern and uses language_code_re.match() and language_code_re.sub() on untrusted text (e.g., matching \">>...<<\"), which allows crafted inputs to cause catastrophic backtracking and high CPU utilization. An attacker can submit specially formed strings to any service that tokenizes text with MarianTokenizer\u2014without authentication\u2014to slow the process dramatically and potentially cause a denial of service.", "cve": "CVE-2025-6638", "id": "pyup.io-79596", "more_info_path": "/vulnerabilities/CVE-2025-6638/79596", "specs": [ "<4.53.0" ], "v": "<4.53.0" }, { "advisory": "Affected versions of the transformers package are vulnerable to Regular Expression Denial of Service (ReDoS) due to unbounded evaluation of user-supplied regular expressions in the AdamWeightDecay._do_use_weight_decay method. The TensorFlow optimizer\u2019s _do_use_weight_decay iterates over include_in_weight_decay and exclude_from_weight_decay lists and calls re.search on each pattern against parameter names, enabling catastrophic backtracking on crafted inputs. An attacker who can control these lists can provide pathological patterns that saturate the CPU and cause processes using transformers to hang, resulting in a Denial of Service.", "cve": "CVE-2025-6921", "id": "pyup.io-79855", "more_info_path": "/vulnerabilities/CVE-2025-6921/79855", "specs": [ "<4.53.0" ], "v": "<4.53.0" }, { "advisory": "Affected versions of the transformers package are vulnerable to insecure deserialization leading to arbitrary code execution due to loading an attacker-controlled RNG-state file with an unsafe torch.load() call.", "cve": "PVE-2026-85102", "id": "pyup.io-85102", "more_info_path": "/vulnerabilities/PVE-2026-85102/85102", "specs": [ "<5.0.0" ], "v": "<5.0.0" }, { "advisory": "Deserialization of Untrusted Data in GitHub repository huggingface/transformers prior to 4.36.", "cve": "CVE-2023-6730", "id": "pyup.io-65215", "more_info_path": "/vulnerabilities/CVE-2023-6730/65215", "specs": [ ">=0,<4.36.0" ], "v": ">=0,<4.36.0" }, { "advisory": "Deserialization of Untrusted Data in GitHub repository huggingface/transformers prior to 4.36.", "cve": "CVE-2023-7018", "id": "pyup.io-65398", "more_info_path": "/vulnerabilities/CVE-2023-7018/65398", "specs": [ ">=0,<4.36.0" ], "v": ">=0,<4.36.0" }, { "advisory": "Affected versions of the `transformers` package are vulnerable to Regular Expression Denial of Service (ReDoS) due to unbounded regular expression complexity. The `DonutProcessor` class's `token2json()` method employs the regex pattern ``, which can be manipulated to trigger catastrophic backtracking with crafted input strings. An attacker can exploit this by providing malicious input to the method, leading to excessive CPU consumption and potential service disruption during document processing tasks.", "cve": "CVE-2025-3933", "id": "pyup.io-78153", "more_info_path": "/vulnerabilities/CVE-2025-3933/78153", "specs": [ ">=4.22.0,<4.52.0" ], "v": ">=4.22.0,<4.52.0" }, { "advisory": "Affected versions of the `transformers` package are vulnerable to Regular Expression Denial of Service (ReDoS) due to unbounded regular expression complexity in the Nougat tokenizer's `post_process_single` method. The method employs a regex pattern which includes nested quantifiers and overlapping character classes, causing excessive backtracking. An attacker can exploit this by submitting crafted markdown-style headers that trigger the regex to consume significant processing time, potentially leading to service disruption.", "cve": "CVE-2024-12720", "id": "pyup.io-76262", "more_info_path": "/vulnerabilities/CVE-2024-12720/76262", "specs": [ ">=4.34.0,<4.48.0" ], "v": ">=4.34.0,<4.48.0" }, { "advisory": "Affected versions of the Hugging Face Transformers package are vulnerable to Regular Expression Denial of Service (ReDoS) due to inefficient regex patterns in multiple components. The vulnerable regular expressions in `serve.py`, `user.py`, and `utils.py` fail to handle catastrophic backtracking efficiently when processing specially crafted input strings, allowing exponential time complexity. \r\n\r\nA remote attacker can exploit this vulnerability by providing malicious input strings that cause excessive CPU consumption during regex matching operations, resulting in a denial of service. The vulnerability was fixed by refactoring the problematic regex patterns to use more efficient alternatives. \r\n\r\nThe fix replaces complex regex operations with simpler string manipulation methods, implements input validation before regex processing, and rewrites patterns to avoid nested quantifiers and catastrophic backtracking. Specifically, the commit modifies regex handling in the model serving components and user input processing functions to prevent ReDoS attacks.", "cve": "CVE-2025-3262", "id": "pyup.io-77990", "more_info_path": "/vulnerabilities/CVE-2025-3262/77990", "specs": [ ">=4.49.0,<4.51.0" ], "v": ">=4.49.0,<4.51.0" } ], "transifex-client": [ { "advisory": "Transifex command-line client before 0.9 does not validate X.509 certificates, which allows man-in-the-middle attackers to spoof a Transifex server via an arbitrary certificate.", "cve": "CVE-2013-2073", "id": "pyup.io-67970", "more_info_path": "/vulnerabilities/CVE-2013-2073/67970", "specs": [ "<0.9" ], "v": "<0.9" }, { "advisory": "Transifex command-line client before 0.10 does not validate X.509 certificates for data transfer connections, which allows man-in-the-middle attackers to spoof a Transifex server via an arbitrary certificate. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-2073.", "cve": "CVE-2013-7110", "id": "pyup.io-54067", "more_info_path": "/vulnerabilities/CVE-2013-7110/54067", "specs": [ ">=0,<0.11.0" ], "v": ">=0,<0.11.0" } ], "transmute-core": [ { "advisory": "Unsafe YAML deserialization in yaml.Loader in transmute-core before 1.13.5 allows attackers to execute arbitrary Python code.\r\nhttps://github.com/toumorokoshi/transmute-core/pull/58", "cve": "CVE-2023-47204", "id": "pyup.io-62150", "more_info_path": "/vulnerabilities/CVE-2023-47204/62150", "specs": [ "<1.13.5" ], "v": "<1.13.5" } ], "trash-cli": [ { "advisory": "Trash-cli before 0.17.1.14 has a bug that causes trash-put to use $topdir/.Trash/UID trashcan even when it is not secure and $topdir/.Trash-UID should be used instead.", "cve": "PVE-2021-34319", "id": "pyup.io-34319", "more_info_path": "/vulnerabilities/PVE-2021-34319/34319", "specs": [ "<0.17.1.14" ], "v": "<0.17.1.14" } ], "treillage": [ { "advisory": "Treillage 0.2.1 updates its dependency 'PyJWT' to include a security fix.", "cve": "CVE-2022-29217", "id": "pyup.io-51419", "more_info_path": "/vulnerabilities/CVE-2022-29217/51419", "specs": [ "<0.2.1" ], "v": "<0.2.1" } ], "treq": [ { "advisory": "Treq 22.1.0 includes a fix for CVE-2022-23607: Treq's request methods ('treq.get', 'treq.post', etc.) and 'treq.client.HTTPClient' constructor accept cookies as a dictionary. Such cookies are not bound to a single domain, and are therefore sent to *every* domain (\"supercookies\"). This can potentially cause sensitive information to leak upon an HTTP redirect to a different domain., e.g. should 'https://example.com' redirect to 'http://cloudstorageprovider.com' the latter will receive the cookie 'session'. Treq 22.1.0 and later bind cookies given to request methods ('treq.request', 'treq.get', 'HTTPClient.request', 'HTTPClient.get', etc.) to the origin of the *url* parameter. For users unable to upgrade, instead of passing a dictionary as the *cookies* argument, pass a 'http.cookiejar.CookieJar' instance with properly domain- and scheme-scoped cookies in it.\r\nhttps://github.com/twisted/treq/security/advisories/GHSA-fhpf-pp6p-55qc", "cve": "CVE-2022-23607", "id": "pyup.io-44726", "more_info_path": "/vulnerabilities/CVE-2022-23607/44726", "specs": [ "<22.1.0" ], "v": "<22.1.0" } ], "trex": [ { "advisory": "Trex 0.1.7 updates its dependency 'gitpython' to version '3.1.30' to include a security fix.\r\nhttps://github.com/berrysauce/trex/commit/08c9630caaf81f1dc6f0dd549f88084eca5236ac", "cve": "CVE-2022-24439", "id": "pyup.io-59301", "more_info_path": "/vulnerabilities/CVE-2022-24439/59301", "specs": [ "<0.1.7" ], "v": "<0.1.7" }, { "advisory": "Trex 0.1.7 updates its dependency 'requests' to version '2.31.0' to include a security fix.\r\nhttps://github.com/berrysauce/trex/commit/c7e427cd33301fda2d290580b9023337c5fd46a4", "cve": "CVE-2023-32681", "id": "pyup.io-59303", "more_info_path": "/vulnerabilities/CVE-2023-32681/59303", "specs": [ "<0.1.7" ], "v": "<0.1.7" }, { "advisory": "Trex 0.1.7 updates its dependency 'certifi' to version '2022.12.7' to include a security fix.\r\nhttps://github.com/berrysauce/trex/commit/cf3f91f9ac665cdb2753984c1d30ef79c38bb790", "cve": "CVE-2022-23491", "id": "pyup.io-59302", "more_info_path": "/vulnerabilities/CVE-2022-23491/59302", "specs": [ "<0.1.7" ], "v": "<0.1.7" } ], "triage": [ { "advisory": "Triage 3.3.0 updates its dependency 'pyyaml' to versions '>=4.2b1' to include a security fix.", "cve": "CVE-2017-18342", "id": "pyup.io-64434", "more_info_path": "/vulnerabilities/CVE-2017-18342/64434", "specs": [ "<3.3.0" ], "v": "<3.3.0" } ], "trialtracker": [ { "advisory": "Trialtracker 0.1.7 and prior releases ship with a version of C library 'libwebp' which is affected by a high risk vulnerability.\r\nhttps://github.com/ProtocolData/trialtracker/blob/3cbcfee719e8586067f9a587fadceabce034057b/env/requirements.txt#L108", "cve": "CVE-2023-4863", "id": "pyup.io-62307", "more_info_path": "/vulnerabilities/CVE-2023-4863/62307", "specs": [ "<=0.1.7" ], "v": "<=0.1.7" } ], "tribler": [ { "advisory": "Tribler 6.4.1 addresses an issue regarding RSA encryption, noting its research context rather than practical use in tunnels. The discussion originates from work on homomorphic encryption for a 2013 paper, exploring Private Set Intersection problems in P2P systems. A specific RSA approach highlighted for its homomorphic properties required a unique implementation, leading to the creation of a \"compatible_key\" method. This was due to limitations in existing cryptographic libraries.\r\nhttps://github.com/Tribler/tribler/pull/1188", "cve": "PVE-2024-66824", "id": "pyup.io-66824", "more_info_path": "/vulnerabilities/PVE-2024-66824/66824", "specs": [ "<6.4.1" ], "v": "<6.4.1" }, { "advisory": "Tribler version 7.11.0rc1 has updated its Pygments dependency from version 2.5.2 to 2.7.4 to address the Regular Expression Denial of Service (ReDoS) vulnerability identified by CVE-2021-27291.\r\nhttps://github.com/Tribler/tribler/pull/6204/commits/c17ce53a03493a1e469f2860fc8a09154f5cc89d", "cve": "CVE-2021-27291", "id": "pyup.io-66809", "more_info_path": "/vulnerabilities/CVE-2021-27291/66809", "specs": [ "<7.11.0rc1" ], "v": "<7.11.0rc1" }, { "advisory": "Tribler version 7.11.0rc1 has updated its Sphinx dependency from version 1.8.5 to 3.0.4 to address the Cross-site Scripting (XSS)vulnerability identified by CVE-2021-27291.\r\nhttps://github.com/Tribler/tribler/pull/6204/commits/c17ce53a03493a1e469f2860fc8a09154f5cc89d", "cve": "CVE-2020-11023", "id": "pyup.io-66856", "more_info_path": "/vulnerabilities/CVE-2020-11023/66856", "specs": [ "<7.11.0rc1" ], "v": "<7.11.0rc1" }, { "advisory": "Tribler version 7.11.0rc1 has updated its Sphinx dependency from version 1.8.5 to 3.0.4 to address the Cross-site Scripting (XSS) vulnerability identified by CVE-2021-27291.\r\nhttps://github.com/Tribler/tribler/pull/6204/commits/c17ce53a03493a1e469f2860fc8a09154f5cc89d", "cve": "CVE-2020-11022", "id": "pyup.io-66855", "more_info_path": "/vulnerabilities/CVE-2020-11022/66855", "specs": [ "<7.11.0rc1" ], "v": "<7.11.0rc1" }, { "advisory": "Tribler version 7.11.0rc1 has updated its Pygments dependency from version 2.5.2 to 2.7.4 to address the Denial of Service (DoS) vulnerability identified by CVE-2021-20270.\r\nhttps://github.com/Tribler/tribler/pull/6204/commits/c17ce53a03493a1e469f2860fc8a09154f5cc89d", "cve": "PVE-2024-66854", "id": "pyup.io-66854", "more_info_path": "/vulnerabilities/PVE-2024-66854/66854", "specs": [ "<7.11.0rc1" ], "v": "<7.11.0rc1" }, { "advisory": "Tribler 7.11.0rc2 introduces a fix for a rare race condition that could result in a reply being unintentionally overwritten, possibly due to a previous call to destruct.\r\nhttps://github.com/Tribler/tribler/pull/6664/commits/8179a89dd044cb3f65f40d6d5e9d459a44774631", "cve": "PVE-2024-66808", "id": "pyup.io-66808", "more_info_path": "/vulnerabilities/PVE-2024-66808/66808", "specs": [ "<7.11.0rc2" ], "v": "<7.11.0rc2" }, { "advisory": "Tribler version 7.13.1 addresses a race condition in the SlowCoroWatchingThread #7613, potentially enhancing stability and preventing unpredictable software behavior or errors that could impact user experience and data integrity.\r\nhttps://github.com/Tribler/tribler/pull/7613/commits/222e6896db5db0e21f7572bb85d7ab162b12b1a0", "cve": "PVE-2024-66801", "id": "pyup.io-66801", "more_info_path": "/vulnerabilities/PVE-2024-66801/66801", "specs": [ "<7.13.1" ], "v": "<7.13.1" }, { "advisory": "Tribler 7.2.0 fixes UnicodeDecodeError on incoming remote search.\r\nhttps://github.com/Tribler/tribler/commit/b26919e7f3426d2e7ee9d2a2325857997fc00ebc", "cve": "PVE-2024-66818", "id": "pyup.io-66818", "more_info_path": "/vulnerabilities/PVE-2024-66818/66818", "specs": [ "<7.2.0" ], "v": "<7.2.0" } ], "triplea": [ { "advisory": "Triplea 0.0.2 updates its dependency 'tornado' to v6.3.2 to include a security fix.", "cve": "CVE-2023-28370", "id": "pyup.io-61560", "more_info_path": "/vulnerabilities/CVE-2023-28370/61560", "specs": [ "<0.0.2" ], "v": "<0.0.2" } ], "tripleo-ansible": [ { "advisory": "A flaw was found in tripleo-ansible. Due to an insecure default configuration, the permissions of a sensitive file are not sufficiently restricted. This flaw allows a local attacker to use brute force to explore the relevant directory and discover the file, leading to information disclosure of important configuration details from the OpenStack deployment.\r\nhttps://github.com/advisories/GHSA-7x96-2w32-w3gw", "cve": "CVE-2022-3101", "id": "pyup.io-53827", "more_info_path": "/vulnerabilities/CVE-2022-3101/53827", "specs": [ "<=6.0.0" ], "v": "<=6.0.0" }, { "advisory": "A flaw was found in tripleo-ansible. Due to an insecure default configuration, the permissions of a sensitive file are not sufficiently restricted. This flaw allows a local attacker to use brute force to explore the relevant directory and discover the file. This issue leads to information disclosure of important configuration details from the OpenStack deployment.\r\nhttps://github.com/advisories/GHSA-w4x6-6w3r-9h2m", "cve": "CVE-2022-3146", "id": "pyup.io-53828", "more_info_path": "/vulnerabilities/CVE-2022-3146/53828", "specs": [ "<=6.0.0" ], "v": "<=6.0.0" }, { "advisory": "Tripleo-ansible is affected by CVE-2023-6725: An access-control flaw was found in the OpenStack Designate component where private configuration information including access keys to BIND were improperly made world readable. A malicious attacker with access to any container could exploit this flaw to access sensitive information.", "cve": "CVE-2023-6725", "id": "pyup.io-66950", "more_info_path": "/vulnerabilities/CVE-2023-6725/66950", "specs": [ "<=6.0.0" ], "v": "<=6.0.0" } ], "tripleo-heat-templates": [ { "advisory": "The TripleO Heat templates (tripleo-heat-templates), when deployed via the commandline interface, allow remote attackers to spoof OpenStack Networking metadata requests by leveraging knowledge of the default value of the NeutronMetadataProxySharedSecret parameter.", "cve": "CVE-2015-5303", "id": "pyup.io-26163", "more_info_path": "/vulnerabilities/CVE-2015-5303/26163", "specs": [ "<0.8.10", "==1.0.0" ], "v": "<0.8.10,==1.0.0" }, { "advisory": "Tripleo-heat-templates 0.8.7 includes a fix for CVE-2015-5271: A flaw was discovered in the pipeline ordering of OpenStack Object Storage's staticweb middleware in the swiftproxy configuration generated from the openstack-tripleo-heat-templates package (OpenStack director). The staticweb middleware was incorrectly configured before the Identity Service, and under some conditions an attacker could use this flaw to gain unauthenticated access to private data.\r\nhttps://opendev.org/openstack/tripleo-heat-templates/commit/1730d95acdbee7c7bbcfe1eba8a48ef2b0cc1476", "cve": "CVE-2015-5271", "id": "pyup.io-26164", "more_info_path": "/vulnerabilities/CVE-2015-5271/26164", "specs": [ "<0.8.7" ], "v": "<0.8.7" }, { "advisory": "Tripleo-heat-templates 11.6.1 includes a fix for CVE-2021-4180: An information exposure flaw in openstack-tripleo-heat-templates allows an external user to discover the internal IP or hostname. An attacker could exploit this by checking the www_authenticate_uri parameter (which is visible to all end users) in configuration files. This would give sensitive information which may aid in additional system exploitation.", "cve": "CVE-2021-4180", "id": "pyup.io-47767", "more_info_path": "/vulnerabilities/CVE-2021-4180/47767", "specs": [ "<11.6.1" ], "v": "<11.6.1" }, { "advisory": "When libvirtd is configured by OSP director (tripleo-heat-templates) to use the TLS transport it defaults to the same certificate authority as all non-libvirtd services. As no additional authentication is configured this allows these services to connect to libvirtd (which is equivalent to root access). If a vulnerability exists in another service it could, combined with this flaw, be exploited to escalate privileges to gain control over compute nodes.", "cve": "CVE-2017-15114", "id": "pyup.io-66672", "more_info_path": "/vulnerabilities/CVE-2017-15114/66672", "specs": [ "<8.0.0.0b2" ], "v": "<8.0.0.0b2" }, { "advisory": "A vulnerability was found in openstack-tripleo-heat-templates before version 8.0.2-40. When deployed using Director using default configuration, Opendaylight in RHOSP13 is configured with easily guessable default credentials.", "cve": "CVE-2018-10898", "id": "pyup.io-36355", "more_info_path": "/vulnerabilities/CVE-2018-10898/36355", "specs": [ "<8.0.3" ], "v": "<8.0.3" }, { "advisory": "Tripleo-heat-templates 9.4.1 and 10.6.1 include a fix for CVE-2021-3585: Plain passwords from RHSM exist in the logs during OSP13 deployment with subscription-manager.", "cve": "CVE-2021-3585", "id": "pyup.io-50790", "more_info_path": "/vulnerabilities/CVE-2021-3585/50790", "specs": [ "<9.4.1", ">=10.0.0,<10.6.1" ], "v": "<9.4.1,>=10.0.0,<10.6.1" }, { "advisory": "The TripleO Heat templates (tripleo-heat-templates), as used in Red Hat Enterprise Linux OpenStack Platform 7.0, do not properly use the configured RabbitMQ credentials, which makes it easier for remote attackers to obtain access to services in deployed overclouds by leveraging knowledge of the default credentials.", "cve": "CVE-2015-5329", "id": "pyup.io-66671", "more_info_path": "/vulnerabilities/CVE-2015-5329/66671", "specs": [ "<=0.8.6" ], "v": "<=0.8.6" }, { "advisory": "Affected versions of the OpenStack Designate package are vulnerable to Information Disclosure due to world-readable RNDC configuration files that expose credentials for controlling BIND. In Red Hat OpenStack Platform 17.1 deployments generated by tripleo-ansible, the /etc/designate and /etc/designate/private directories and files such as /etc/designate/private/bind1.conf are installed with permissive modes, making the RNDC keys readable to any local user within the Designate container.", "cve": "CVE-2023-6725", "id": "pyup.io-71382", "more_info_path": "/vulnerabilities/CVE-2023-6725/71382", "specs": [ "<=18.0.0" ], "v": "<=18.0.0" }, { "advisory": "A resource-permission flaw was found in the openstack-tripleo-heat-templates package where ceph.client.openstack.keyring is created as world-readable. A local attacker with access to the key could read or modify data on Ceph cluster pools for OpenStack as though the attacker were the OpenStack service, thus potentially reading or modifying data in an OpenStack Block Storage volume.", "cve": "CVE-2017-12155", "id": "pyup.io-65811", "more_info_path": "/vulnerabilities/CVE-2017-12155/65811", "specs": [ ">=0,<8.0.0.0b2" ], "v": ">=0,<8.0.0.0b2" } ], "trosnoth": [ { "advisory": "trosnoth before 1.13.0 had insecure hard-coded server settings in the configuration file.", "cve": "PVE-2021-36954", "id": "pyup.io-36954", "more_info_path": "/vulnerabilities/PVE-2021-36954/36954", "specs": [ "<1.13.0" ], "v": "<1.13.0" } ], "trove": [ { "advisory": "The _write_config function in trove/guestagent/datastore/experimental/mongodb/service.py, reset_configuration function in trove/guestagent/datastore/experimental/postgresql/service/config.py, write_config function in trove/guestagent/datastore/experimental/redis/service.py, _write_mycnf function in trove/guestagent/datastore/mysql/service.py, InnoBackupEx::_run_prepare function in trove/guestagent/strategies/restore/mysql_impl.py, InnoBackupEx::cmd function in trove/guestagent/strategies/backup/mysql_impl.py, MySQLDump::cmd in trove/guestagent/strategies/backup/mysql_impl.py, InnoBackupExIncremental::cmd function in trove/guestagent/strategies/backup/mysql_impl.py, _get_actual_db_status function in trove/guestagent/datastore/experimental/cassandra/system.py and trove/guestagent/datastore/experimental/cassandra/service.py, and multiple class CbBackup methods in trove/guestagent/strategies/backup/experimental/couchbase_impl.py in Openstack DBaaS (aka Trove) as packaged in Openstack before 2015.1.0 (aka Kilo) allows local users to write to configuration files via a symlink attack on a temporary file.", "cve": "CVE-2015-3156", "id": "pyup.io-70414", "more_info_path": "/vulnerabilities/CVE-2015-3156/70414", "specs": [ "<2015.1.0" ], "v": "<2015.1.0" } ], "trrfab": [ { "advisory": "Trrfab is a malicious package, typosquatting. It steals Discord access tokens, passwords, and even stage dependency confusion attacks.\r\nhttps://thehackernews.com/2021/11/11-malicious-pypi-python-libraries.html", "cve": "PVE-2022-45460", "id": "pyup.io-45460", "more_info_path": "/vulnerabilities/PVE-2022-45460/45460", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "trustpilot": [ { "advisory": "Trustpilot 6.1.0 includes security upgrades of the requests and urllib dependencies.", "cve": "PVE-2021-38105", "id": "pyup.io-38105", "more_info_path": "/vulnerabilities/PVE-2021-38105/38105", "specs": [ "<6.1.0" ], "v": "<6.1.0" } ], "tryton": [ { "advisory": "model/modelstorage.py in the Tryton application framework (trytond) before 2.4.0 for Python does not properly restrict access to the Many2Many field in the relation model, which allows remote authenticated users to modify the privileges of arbitrary users via a (1) create, (2) write, (3) delete, or (4) copy rpc call.", "cve": "CVE-2012-0215", "id": "pyup.io-26165", "more_info_path": "/vulnerabilities/CVE-2012-0215/26165", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Directory traversal vulnerability in the client in Tryton 3.0.0, as distributed before 20131104 and earlier, allows remote servers to write arbitrary files via path separators in the extension of a report.", "cve": "CVE-2013-4510", "id": "pyup.io-54062", "more_info_path": "/vulnerabilities/CVE-2013-4510/54062", "specs": [ ">=0,<3.0.1" ], "v": ">=0,<3.0.1" }, { "advisory": "The client in Tryton 5.x before 5.0.1 tries to make a connection to the bus in cleartext instead of encrypted under certain circumstances in bus.py and jsonrpc.py. This connection attempt fails, but it contains in the header the current session of the user. This session could then be stolen by a man-in-the-middle.", "cve": "CVE-2018-19443", "id": "pyup.io-54015", "more_info_path": "/vulnerabilities/CVE-2018-19443/54015", "specs": [ ">=5.0.0,<5.0.1" ], "v": ">=5.0.0,<5.0.1" } ], "trytond": [ { "advisory": "model/modelstorage.py in the Tryton application framework (trytond) before 2.4.0 for Python does not properly restrict access to the Many2Many field in the relation model, which allows remote authenticated users to modify the privileges of arbitrary users via a (1) create, (2) write, (3) delete, or (4) copy rpc call.", "cve": "CVE-2012-0215", "id": "pyup.io-26166", "more_info_path": "/vulnerabilities/CVE-2012-0215/26166", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "file_open in Tryton before 3.2.17, 3.4.x before 3.4.14, 3.6.x before 3.6.12, 3.8.x before 3.8.8, and 4.x before 4.0.4 allows remote authenticated users with certain permissions to read arbitrary files via the name parameter or unspecified other vectors.", "cve": "CVE-2016-1242", "id": "pyup.io-54111", "more_info_path": "/vulnerabilities/CVE-2016-1242/54111", "specs": [ ">=0,<3.2.17", ">=3.4,<3.4.14", ">=3.6,<3.6.12", ">=3.8,<3.8.8", ">=4.0,<4.0.4" ], "v": ">=0,<3.2.17,>=3.4,<3.4.14,>=3.6,<3.6.12,>=3.8,<3.8.8,>=4.0,<4.0.4" }, { "advisory": "Tryton 3.x before 3.2.17, 3.4.x before 3.4.14, 3.6.x before 3.6.12, 3.8.x before 3.8.8, and 4.x before 4.0.4 allow remote authenticated users to discover user password hashes via unspecified vectors.", "cve": "CVE-2016-1241", "id": "pyup.io-54110", "more_info_path": "/vulnerabilities/CVE-2016-1241/54110", "specs": [ ">=0,<3.2.17", ">=3.4,<3.4.14", ">=3.6,<3.6.12", ">=3.8,<3.8.8", ">=4.0,<4.0.4" ], "v": ">=0,<3.2.17,>=3.4,<3.4.14,>=3.6,<3.6.12,>=3.8,<3.8.8,>=4.0,<4.0.4" }, { "advisory": "trytond 2.4: ModelView.button fails to validate authorization", "cve": "CVE-2012-2238", "id": "pyup.io-54073", "more_info_path": "/vulnerabilities/CVE-2012-2238/54073", "specs": [ ">=2.4.0,<2.4.2" ], "v": ">=2.4.0,<2.4.2" }, { "advisory": "Trytond 3.2.3, 3.0.7, 2.8.11, 2.6.14 and 2.4.15 include a fix for CVE-2014-6633: The safe_eval function in trytond in Tryton before 2.4.15, 2.6.x before 2.6.14, 2.8.x before 2.8.11, 3.0.x before 3.0.7, and 3.2.x before 3.2.3 allows remote authenticated users to execute arbitrary commands via shell metacharacters in (1) the collection.domain in the webdav module or (2) the formula field in the price_list module.\r\nhttps://foss.heptapod.net/tryton/tryton/-/issues/4155", "cve": "CVE-2014-6633", "id": "pyup.io-54087", "more_info_path": "/vulnerabilities/CVE-2014-6633/54087", "specs": [ ">=2.6.0,<2.6.14", ">=2.8.0,<2.8.11", ">=3.2.0,<3.2.3", ">=3.0.0,<3.0.7", "<2.4.15" ], "v": ">=2.6.0,<2.6.14,>=2.8.0,<2.8.11,>=3.2.0,<3.2.3,>=3.0.0,<3.0.7,<2.4.15" }, { "advisory": "Trytond 4.4.0 includes a fix CVE-2017-0360: file_open in Tryton 3.x and 4.x through 4.4.0 allows remote authenticated users with certain permissions to read arbitrary files via a \"same root name but with a suffix\" attack. This vulnerability exists because of an incomplete fix for CVE-2016-1242.\r\nhttps://github.com/tryton/trytond/commit/30e978593733385db3144f8c583eeb4679575cf0", "cve": "CVE-2017-0360", "id": "pyup.io-53924", "more_info_path": "/vulnerabilities/CVE-2017-0360/53924", "specs": [ ">=3.0.0,<4.4.0" ], "v": ">=3.0.0,<4.4.0" }, { "advisory": "model/modelstorage.py in trytond 3.2.x before 3.2.10, 3.4.x before 3.4.8, 3.6.x before 3.6.5, and 3.8.x before 3.8.1 allows remote authenticated users to bypass intended access restrictions and write to arbitrary fields via a sequence of records.", "cve": "CVE-2015-0861", "id": "pyup.io-54095", "more_info_path": "/vulnerabilities/CVE-2015-0861/54095", "specs": [ ">=3.2.0,<3.2.10", ">=3.4.0,<3.4.8", ">=3.6.0,<3.6.5", ">=3.8.0,<3.8.1" ], "v": ">=3.2.0,<3.2.10,>=3.4.0,<3.4.8,>=3.6.0,<3.6.5,>=3.8.0,<3.8.1" }, { "advisory": "In trytond/model/modelstorage.py in Tryton 4.2 before 4.2.21, 4.4 before 4.4.19, 4.6 before 4.6.14, 4.8 before 4.8.10, and 5.0 before 5.0.6, an authenticated user can order records based on a field for which he has no access right. This may allow the user to guess values.", "cve": "CVE-2019-10868", "id": "pyup.io-54134", "more_info_path": "/vulnerabilities/CVE-2019-10868/54134", "specs": [ ">=4.2.0,<4.2.21", ">=4.4.0,<4.4.19", ">=4.6.0,<4.6.14", ">=4.8.0,<4.8.10", ">=5.0.0,<5.0.6" ], "v": ">=4.2.0,<4.2.21,>=4.4.0,<4.4.19,>=4.6.0,<4.6.14,>=4.8.0,<4.8.10,>=5.0.0,<5.0.6" }, { "advisory": "An XXE issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. An authenticated user can make the server parse a crafted XML SEPA file to access arbitrary files on the system.", "cve": "CVE-2022-26661", "id": "pyup.io-54404", "more_info_path": "/vulnerabilities/CVE-2022-26661/54404", "specs": [ ">=5.0.0,<5.0.46", ">=6.0.0,<6.0.16", ">=6.1.0,<6.2.6" ], "v": ">=5.0.0,<5.0.46,>=6.0.0,<6.0.16,>=6.1.0,<6.2.6" }, { "advisory": "An XML Entity Expansion (XEE) issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. An unauthenticated user can send a crafted XML-RPC message to consume all the resources of the server.", "cve": "CVE-2022-26662", "id": "pyup.io-54402", "more_info_path": "/vulnerabilities/CVE-2022-26662/54402", "specs": [ ">=5.0.0,<5.0.46", ">=6.0.0,<6.0.16", ">=6.1.0,<6.2.6" ], "v": ">=5.0.0,<5.0.46,>=6.0.0,<6.0.16,>=6.1.0,<6.2.6" }, { "advisory": "Affected versions of the trytond package are vulnerable to Information Disclosure due to improper error handling that returns full Python trace-backs to clients. The JSON-RPC API, including methods such as model.party.party.create, propagates unexpected exceptions (for example, an unhandled KeyError on unknown fields) through an error-handling path that embeds the complete Python stack trace and server setup details directly in the HTTP response instead of a sanitized error message.", "cve": "CVE-2025-66422", "id": "pyup.io-82238", "more_info_path": "/vulnerabilities/CVE-2025-66422/82238", "specs": [ ">=7.5.0,<7.6.11", ">=7.1.0,<7.4.21", ">=7.0.0,<7.0.40", "<6.0.70" ], "v": ">=7.5.0,<7.6.11,>=7.1.0,<7.4.21,>=7.0.0,<7.0.40,<6.0.70" }, { "advisory": "Affected versions of the trytond package are vulnerable to Incorrect Authorization due to missing access control checks on the HTML editor route. The HTML editor route in trytond, which is used to edit rich-text fields such as user signatures, does not properly verify that the authenticated caller has the correct access rights to the targeted signature resource, allowing requests to succeed even when the user should not be allowed to access that data.", "cve": "CVE-2025-66423", "id": "pyup.io-82200", "more_info_path": "/vulnerabilities/CVE-2025-66423/82200", "specs": [ ">=7.5.0,<7.6.11", ">=7.1.0,<7.4.21", ">=7.0.0,<7.0.40", ">=6.0.0,<6.0.70" ], "v": ">=7.5.0,<7.6.11,>=7.1.0,<7.4.21,>=7.0.0,<7.0.40,>=6.0.0,<6.0.70" }, { "advisory": "Affected versions of the trytond package are vulnerable to Information Disclosure due to missing enforcement of access rights on data export operations. In affected versions, the data export functionality in the trytond server does not consistently apply the configured access control rules of the requesting user when building the exported dataset, so records outside the user\u2019s authorized read domain may be included in the export.", "cve": "CVE-2025-66424", "id": "pyup.io-82239", "more_info_path": "/vulnerabilities/CVE-2025-66424/82239", "specs": [ ">=7.5.0,<7.6.11", ">=7.1.0,<7.4.21", ">=7.0.0,<7.0.40", ">=6.0.0,<6.0.70" ], "v": ">=7.5.0,<7.6.11,>=7.1.0,<7.4.21,>=7.0.0,<7.0.40,>=6.0.0,<6.0.70" } ], "tsgettoolbox": [ { "advisory": "Tsgettoolbox 23.21.0 pins its indirect dependency 'pygments' to a version >=2.7.4 to include security fixes.", "cve": "CVE-2015-8557", "id": "pyup.io-44898", "more_info_path": "/vulnerabilities/CVE-2015-8557/44898", "specs": [ "<23.21.0" ], "v": "<23.21.0" }, { "advisory": "Tsgettoolbox 23.21.0 pins its indirect dependency 'pygments' to a version >=2.7.4 to include security fixes.", "cve": "CVE-2021-20270", "id": "pyup.io-44881", "more_info_path": "/vulnerabilities/CVE-2021-20270/44881", "specs": [ "<23.21.0" ], "v": "<23.21.0" }, { "advisory": "Tsgettoolbox 23.21.0 pins its indirect dependency 'pygments' to a version >=2.7.4 to include security fixes.", "cve": "CVE-2021-27291", "id": "pyup.io-44895", "more_info_path": "/vulnerabilities/CVE-2021-27291/44895", "specs": [ "<23.21.0" ], "v": "<23.21.0" }, { "advisory": "Tsgettoolbox 23.21.0 pins its indirect dependency 'sphinx' to a version >=3.0.4 to include security fixes.", "cve": "CVE-2020-11022", "id": "pyup.io-44896", "more_info_path": "/vulnerabilities/CVE-2020-11022/44896", "specs": [ "<23.21.0" ], "v": "<23.21.0" }, { "advisory": "Tsgettoolbox 23.21.0 pins its indirect dependency 'sphinx' to a version >=3.0.4 to include security fixes.", "cve": "CVE-2020-11023", "id": "pyup.io-44897", "more_info_path": "/vulnerabilities/CVE-2020-11023/44897", "specs": [ "<23.21.0" ], "v": "<23.21.0" } ], "tstoolbox": [ { "advisory": "Tstoolbox 103.15.0 pins its dependency 'sphinx' to versions >=3.0.4 to include security fixes.", "cve": "CVE-2020-11022", "id": "pyup.io-44905", "more_info_path": "/vulnerabilities/CVE-2020-11022/44905", "specs": [ "<103.15.0" ], "v": "<103.15.0" }, { "advisory": "Tstoolbox 103.15.0 pins its dependency 'pygments' to versions >=2.7.4 to include security fixes.", "cve": "CVE-2021-27291", "id": "pyup.io-44903", "more_info_path": "/vulnerabilities/CVE-2021-27291/44903", "specs": [ "<103.15.0" ], "v": "<103.15.0" }, { "advisory": "Tstoolbox 103.15.0 pins its dependency 'pygments' to versions >=2.7.4 to include security fixes.", "cve": "CVE-2015-8557", "id": "pyup.io-44904", "more_info_path": "/vulnerabilities/CVE-2015-8557/44904", "specs": [ "<103.15.0" ], "v": "<103.15.0" }, { "advisory": "Tstoolbox 103.15.0 pins its dependency 'sphinx' to versions >=3.0.4 to include security fixes.", "cve": "CVE-2020-11023", "id": "pyup.io-44906", "more_info_path": "/vulnerabilities/CVE-2020-11023/44906", "specs": [ "<103.15.0" ], "v": "<103.15.0" }, { "advisory": "Tstoolbox 103.15.0 pins its dependency 'pygments' to versions >=2.7.4 to include security fixes.", "cve": "CVE-2021-20270", "id": "pyup.io-44836", "more_info_path": "/vulnerabilities/CVE-2021-20270/44836", "specs": [ "<103.15.0" ], "v": "<103.15.0" } ], "ttrv": [ { "advisory": "Ttrv 1.12.1 fixes a security vulnerability where malicious URLs could inject python code.", "cve": "PVE-2021-38370", "id": "pyup.io-45724", "more_info_path": "/vulnerabilities/PVE-2021-38370/45724", "specs": [ "<1.12.1" ], "v": "<1.12.1" }, { "advisory": "Some versions of Tilde Terminal Reddit Viewer (ttrv) are susceptible to arbitrary code injection, where malicious URLs can inject Python code. This vulnerability threatens the security of the application by allowing unauthorized code execution through specially crafted links.", "cve": "PVE-2024-99837", "id": "pyup.io-65583", "more_info_path": "/vulnerabilities/PVE-2024-99837/65583", "specs": [ ">=0,<1.27.0" ], "v": ">=0,<1.27.0" } ], "tts": [ { "advisory": "Tts 0.9.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/coqui-ai/TTS/pull/1807", "cve": "PVE-2023-60098", "id": "pyup.io-60098", "more_info_path": "/vulnerabilities/PVE-2023-60098/60098", "specs": [ "<0.9.0" ], "v": "<0.9.0" } ], "ttsfm": [ { "advisory": "Affected versions of the ttsfm package are vulnerable to Information Disclosure due to verbose error handling in FFmpeg-related operations that exposes sensitive system details in API responses. The application's exception handling for FFmpeg processes includes raw error messages containing internal file paths, stack traces, system configuration details, and environment information directly in user-facing error responses without sanitisation. An attacker can exploit this by intentionally triggering FFmpeg errors through malformed audio requests or unsupported format conversions, collecting exposed information such as absolute file system paths, installed software versions, directory structures, and process execution details to perform reconnaissance and identify potential attack vectors for subsequent targeted exploitation.", "cve": "PVE-2025-82866", "id": "pyup.io-82866", "more_info_path": "/vulnerabilities/PVE-2025-82866/82866", "specs": [ "<3.4.2" ], "v": "<3.4.2" } ], "tuf": [ { "advisory": "Tuf 0.11.1 prevents a persistent freeze attack - see: https://github.com/theupdateframework/tuf/pull/737", "cve": "PVE-2021-36279", "id": "pyup.io-36279", "more_info_path": "/vulnerabilities/PVE-2021-36279/36279", "specs": [ "<0.11.1" ], "v": "<0.11.1" }, { "advisory": "Tuf 0.12.0 includes a fix for CVE-2020-15163: Python TUF reference implementation before version 0.12 incorrectly trusts previously downloaded root metadata files which failed verification at download time. This allows an attacker who is able to serve multiple new versions of root metadata (i.e. by a person-in-the-middle attack) culminating in a version which has not been correctly signed to control the trust chain for future updates.\r\nhttps://github.com/theupdateframework/python-tuf/security/advisories/GHSA-f8mr-jv2c-v8mg", "cve": "CVE-2020-15163", "id": "pyup.io-38769", "more_info_path": "/vulnerabilities/CVE-2020-15163/38769", "specs": [ "<0.12.0" ], "v": "<0.12.0" }, { "advisory": "Tuf version 0.19 includes a fix for CVE-2021-41131: In both clients ('tuf/client' and 'tuf/ngclient'), there is a path traversal vulnerability that in the worst case can overwrite files ending in '.json' anywhere on the client system on a call to 'get_one_valid_targetinfo()'. It occurs because the rolename is used to form the filename, and may contain path traversal characters (ie '../../name.json'). The impact is mitigated by a few facts: \r\n- It only affects implementations that allow arbitrary rolename selection for delegated targets metadata.\r\n- The attack requires the ability to A) insert new metadata for the path-traversing role and B) get the role delegated by an existing targets metadata.\r\n- The written file content is heavily restricted since it needs to be a valid, signed targets file. \r\n- The file extension is always .json. \r\nThere are no workarounds that do not require code changes. Clients can restrict the allowed character set for rolenames, or they can store metadata in files named in a way that is not vulnerable: neither of these approaches is possible without modifying python-tuf.\r\nhttps://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr\r\nhttps://github.com/theupdateframework/python-tuf/commit/4ad7ae48fda594b640139c3b7eae21ed5155a102\r\nhttps://github.com/theupdateframework/python-tuf/issues/1527", "cve": "CVE-2021-41131", "id": "pyup.io-42183", "more_info_path": "/vulnerabilities/CVE-2021-41131/42183", "specs": [ "<0.19.0" ], "v": "<0.19.0" }, { "advisory": "TUF 3.1.1 addresses GHSA-77hh-43cm-v8j6 by fixing a security flaw in how delegated roles are verified, particularly under \"succinct delegation.\" The issue could mislead users of tuf.api.metadata into trusting incorrectly delegated roles, though tuf.ngclient users remain unaffected. The vulnerability's impact is deemed low due to the specific conditions required for exploitation and the fact that actual signature verification processes are not compromised. This scenario mainly affects users employing succinct delegations in a manner susceptible to the outlined exploit.", "cve": "PVE-2024-67478", "id": "pyup.io-67478", "more_info_path": "/vulnerabilities/PVE-2024-67478/67478", "specs": [ "<3.1.1" ], "v": "<3.1.1" }, { "advisory": "TUF (aka The Update Framework) through 0.12.1 has Improper Verification of a Cryptographic Signature.", "cve": "CVE-2020-6174", "id": "pyup.io-54200", "more_info_path": "/vulnerabilities/CVE-2020-6174/54200", "specs": [ ">=0,<0.12.2" ], "v": ">=0,<0.12.2" }, { "advisory": "Tuf 0.16.0 includes a security fix: The function '_verify_root_self_signed()', introduced in v0.14.0, and which verifies self-signatures in a new root metadata file, counted multiple signatures by any new root key towards the new threshold. That is, any single new root key could theoretically provide enough signatures to meet the threshold for new key self-signatures required during root metadata update. A scenario where this attack could be relevant is amazingly unlikely in practice to the point where labeling this issue as a security advisory is potentially overstating the impact of the issue. Given that new root keys only become trusted by the client after a successful root metadata update, which also requires the quorum of signatures from old trusted root keys, this issue has been evaluated as low in severity. In particular, in order to exploit this vulnerability, an attacker must:\r\n1. Control one new root key.\r\n2. Craft a new root metadata file such that there is a number of signatures by this new root key greater than or equal to the new threshold.\r\n3. Cause a valid threshold of the old root keys to sign this new root metadata file.\r\n4. Cause this new root metadata file to be published on the repository.\r\n5. Cause clients to rotate to this new root metadata file.", "cve": "PVE-2023-55201", "id": "pyup.io-55201", "more_info_path": "/vulnerabilities/PVE-2023-55201/55201", "specs": [ ">=0.14.0,<0.16.0" ], "v": ">=0.14.0,<0.16.0" }, { "advisory": "TUF (aka The Update Framework) 0.7.2 through 0.12.1 allows Uncontrolled Resource Consumption.", "cve": "CVE-2020-6173", "id": "pyup.io-54198", "more_info_path": "/vulnerabilities/CVE-2020-6173/54198", "specs": [ ">=0.7.5,<0.12.2" ], "v": ">=0.7.5,<0.12.2" }, { "advisory": "A vulnerability has been identified in selected versions of the tuf secure updater framework, where the Improper Verification of Cryptographic Signature occurs during the Targets.get_delegated_role process. This issue arises in scenarios involving the use of tuf.api.metadata, specifically when a delegated_role argument, not actually delegated by the Targets, is employed with succinct delegation. It's of note that this vulnerability does not affect users who adhere to the standard client workflow, which relies on the trusted delegating Targets to derive the delegated role name. Furthermore, the integrity of actual signature verification remains intact, as any verified metadata must still be correctly signed by the keys specified in the delegating role.", "cve": "PVE-2024-99759", "id": "pyup.io-66732", "more_info_path": "/vulnerabilities/PVE-2024-99759/66732", "specs": [ ">=2.0.0,<3.1.1" ], "v": ">=2.0.0,<3.1.1" } ], "tuitse-tsusin": [ { "advisory": "TuiTse-TsuSin is a package for organizing the comparative corpus of Taiwanese Chinese characters and Roman characters, and extracting sentences of the Taiwanese Chinese characters and the Roman characters. Prior to version 1.3.2, when using `tuitse_html` without quoting the input, there is a html injection vulnerability. Version 1.3.2 contains a patch for the issue. As a workaround, sanitize Taigi input with HTML quotation.", "cve": "CVE-2024-23341", "id": "pyup.io-66731", "more_info_path": "/vulnerabilities/CVE-2024-23341/66731", "specs": [ "<1.3.2" ], "v": "<1.3.2" } ], "tulflow": [ { "advisory": "Tulflow 0.9.1 updates its dependency 'apache-airflow' to v2.4.3 to include security fixes.", "cve": "CVE-2022-43982", "id": "pyup.io-58737", "more_info_path": "/vulnerabilities/CVE-2022-43982/58737", "specs": [ "<0.9.1" ], "v": "<0.9.1" }, { "advisory": "Tulflow 0.9.1 updates its dependency 'apache-airflow' to v2.4.3 to include security fixes.", "cve": "CVE-2022-45402", "id": "pyup.io-58741", "more_info_path": "/vulnerabilities/CVE-2022-45402/58741", "specs": [ "<0.9.1" ], "v": "<0.9.1" }, { "advisory": "Tulflow 0.9.1 updates its dependency 'apache-airflow' to v2.4.3 to include security fixes.", "cve": "CVE-2022-43985", "id": "pyup.io-58740", "more_info_path": "/vulnerabilities/CVE-2022-43985/58740", "specs": [ "<0.9.1" ], "v": "<0.9.1" } ], "turbinia": [ { "advisory": "Turbinia version 20240614.1 addresses a path traversal vulnerability in the UI router. This update fixes an issue that could potentially allow unauthorized access to files outside the intended directory, enhancing the overall security of the application.", "cve": "PVE-2024-71540", "id": "pyup.io-71540", "more_info_path": "/vulnerabilities/PVE-2024-71540/71540", "specs": [ "<20240614.1" ], "v": "<20240614.1" } ], "turbogears": [ { "advisory": "A vulnerability classified as critical has been found in OnShift TurboGears. This affects an unknown part of the file turbogears/controllers.py of the component HTTP Header Handler. The manipulation leads to http response splitting. It is possible to initiate the attack remotely.\r\n# The fix commit belongs to a fork version of TurboGears that is not in PyPi.", "cve": "CVE-2019-25101", "id": "pyup.io-54647", "more_info_path": "/vulnerabilities/CVE-2019-25101/54647", "specs": [ ">=0" ], "v": ">=0" } ], "tutor": [ { "advisory": "Tutor 10.0.5 applies upstream XSS security fixes for the 'edx-platform' underlying dependency.\r\nhttps://github.com/overhangio/tutor/commit/1773e2a347e6a9b3e378886ab2f8878dc6d80530", "cve": "PVE-2021-40919", "id": "pyup.io-40919", "more_info_path": "/vulnerabilities/PVE-2021-40919/40919", "specs": [ "<10.0.5" ], "v": "<10.0.5" }, { "advisory": "Tutor 10.1.0 includes upstream XSS security fixes for the 'edx-platform' underlying dependency.\r\nhttps://github.com/overhangio/tutor/commit/8e2a06dc6fc2c1819ee82e46f44490602a065766", "cve": "PVE-2021-40918", "id": "pyup.io-40918", "more_info_path": "/vulnerabilities/PVE-2021-40918/40918", "specs": [ "<10.1.0" ], "v": "<10.1.0" }, { "advisory": "Tutor 10.2.0 includes a security patch for JavaScript code in the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40917", "id": "pyup.io-40917", "more_info_path": "/vulnerabilities/PVE-2021-40917/40917", "specs": [ "<10.2.0" ], "v": "<10.2.0" }, { "advisory": "Tutor 10.5.3 applies upstream security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40916", "id": "pyup.io-40916", "more_info_path": "/vulnerabilities/PVE-2021-40916/40916", "specs": [ "<10.5.3" ], "v": "<10.5.3" }, { "advisory": "Tutor 11.0.1 applies a security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40915", "id": "pyup.io-40915", "more_info_path": "/vulnerabilities/PVE-2021-40915/40915", "specs": [ "<11.0.1" ], "v": "<11.0.1" }, { "advisory": "Tutor 11.0.6 applies a security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40914", "id": "pyup.io-40914", "more_info_path": "/vulnerabilities/PVE-2021-40914/40914", "specs": [ "<11.0.6" ], "v": "<11.0.6" }, { "advisory": "Tutor 11.0.7 includes a security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40913", "id": "pyup.io-40913", "more_info_path": "/vulnerabilities/PVE-2021-40913/40913", "specs": [ "<11.0.7" ], "v": "<11.0.7" }, { "advisory": "Tutor 11.1.1 includes a security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40912", "id": "pyup.io-40912", "more_info_path": "/vulnerabilities/PVE-2021-40912/40912", "specs": [ "<11.1.1" ], "v": "<11.1.1" }, { "advisory": "Tutor 11.1.3 includes a security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40911", "id": "pyup.io-40911", "more_info_path": "/vulnerabilities/PVE-2021-40911/40911", "specs": [ "<11.1.3" ], "v": "<11.1.3" }, { "advisory": "Tutor 11.1.4 applies a security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40910", "id": "pyup.io-40910", "more_info_path": "/vulnerabilities/PVE-2021-40910/40910", "specs": [ "<11.1.4" ], "v": "<11.1.4" }, { "advisory": "Tutor 11.1.5 includes security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40909", "id": "pyup.io-40909", "more_info_path": "/vulnerabilities/PVE-2021-40909/40909", "specs": [ "<11.1.5" ], "v": "<11.1.5" }, { "advisory": "Tutor 11.2.10 applies security patches for the 'Django' dependency by upgrading from 2.2.20 to 2.2.23.", "cve": "CVE-2021-32052", "id": "pyup.io-40906", "more_info_path": "/vulnerabilities/CVE-2021-32052/40906", "specs": [ "<11.2.10" ], "v": "<11.2.10" }, { "advisory": "Tutor 11.2.10 applies security patches for the 'Django' dependency by upgrading from 2.2.20 to 2.2.23.", "cve": "CVE-2021-31542", "id": "pyup.io-49771", "more_info_path": "/vulnerabilities/CVE-2021-31542/49771", "specs": [ "<11.2.10" ], "v": "<11.2.10" }, { "advisory": "Tutor 11.2.10 applies security patches for the 'Django' dependency by upgrading from 2.2.20 to 2.2.23.", "cve": "CVE-2021-28658", "id": "pyup.io-49772", "more_info_path": "/vulnerabilities/CVE-2021-28658/49772", "specs": [ "<11.2.10" ], "v": "<11.2.10" }, { "advisory": "Tutor 11.2.2 includes a security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40908", "id": "pyup.io-40908", "more_info_path": "/vulnerabilities/PVE-2021-40908/40908", "specs": [ "<11.2.2" ], "v": "<11.2.2" }, { "advisory": "Tutor 11.2.7 applies a security patch for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40907", "id": "pyup.io-40907", "more_info_path": "/vulnerabilities/PVE-2021-40907/40907", "specs": [ "<11.2.7" ], "v": "<11.2.7" }, { "advisory": "Tutor 12.0.4 applies security patch.\r\nhttps://github.com/edx/edx-platform/pull/28442", "cve": "PVE-2021-41730", "id": "pyup.io-41730", "more_info_path": "/vulnerabilities/PVE-2021-41730/41730", "specs": [ "<12.0.4" ], "v": "<12.0.4" }, { "advisory": "Tutor 13.0.0 converts all NodePort services to ClusterIP resources so to avoid they are exposed to the outside world, specially using Kubernetes.\r\nhttps://github.com/overhangio/tutor/commit/7c1e85ef4ba94cce1d597a1a3ea69cedbc2bde49", "cve": "PVE-2021-43583", "id": "pyup.io-43583", "more_info_path": "/vulnerabilities/PVE-2021-43583/43583", "specs": [ "<13.0.0" ], "v": "<13.0.0" }, { "advisory": "Tutor 13.1.11 fixes a vulnerability in SAML configuration.\r\nhttps://github.com/overhangio/tutor/commit/16b2378165006ba951c420f5a32b0651c01d57c0", "cve": "PVE-2022-48110", "id": "pyup.io-48110", "more_info_path": "/vulnerabilities/PVE-2022-48110/48110", "specs": [ "<13.1.11" ], "v": "<13.1.11" }, { "advisory": "Tutor 13.1.3 fixes an invalid enrollment vulnerability.\r\nhttps://github.com/overhangio/edx-platform/commit/e9369cffde92e765117bbd4dfbee7dc29213493a", "cve": "PVE-2022-44747", "id": "pyup.io-44747", "more_info_path": "/vulnerabilities/PVE-2022-44747/44747", "specs": [ "<13.1.3" ], "v": "<13.1.3" }, { "advisory": "Tutor 13.1.4 fixes vulnerability in redirect url during authentication.\r\nhttps://github.com/overhangio/edx-platform/commit/06550411e34c04376fa3d757e1f068f464f816e6", "cve": "PVE-2022-44885", "id": "pyup.io-44885", "more_info_path": "/vulnerabilities/PVE-2022-44885/44885", "specs": [ "<13.1.4" ], "v": "<13.1.4" }, { "advisory": "Tutor 13.1.9 fixes an open redirect vulnerability in inactive user flow.\r\nhttps://github.com/rgraber/edx-platform/commit/fbbcfe71832e700f16aad3636b0ccb35585d1c95", "cve": "PVE-2022-48012", "id": "pyup.io-48012", "more_info_path": "/vulnerabilities/PVE-2022-48012/48012", "specs": [ "<13.1.9" ], "v": "<13.1.9" }, { "advisory": "Tutor 13.2.0 fixes a rate limiting bypass vulnerability that was possible by using a spoofed X-Forwarded-For header.\r\nhttps://github.com/overhangio/edx-platform/commit/b5723e416e628cac4fa84392ca13e1b72817674f", "cve": "PVE-2022-48258", "id": "pyup.io-48258", "more_info_path": "/vulnerabilities/PVE-2022-48258/48258", "specs": [ "<13.2.0" ], "v": "<13.2.0" }, { "advisory": "Tutor 13.3.0 applies a security fix in logout redirect urls.\r\nhttps://github.com/overhangio/tutor/commit/79eca380f6cdb14b418475fa8872662fa46efad8", "cve": "PVE-2022-49260", "id": "pyup.io-49260", "more_info_path": "/vulnerabilities/PVE-2022-49260/49260", "specs": [ "<13.3.0" ], "v": "<13.3.0" }, { "advisory": "Tutor 14.1.1 fixes a vulnerability in xblock ajax handler.\r\nhttps://github.com/overhangio/tutor/commit/3ba53655378cbe00245354bce159d720fb2cbbd6", "cve": "PVE-2022-51540", "id": "pyup.io-51540", "more_info_path": "/vulnerabilities/PVE-2022-51540/51540", "specs": [ "<14.1.1" ], "v": "<14.1.1" }, { "advisory": "Tutor 14.1.2 includes a fix for an XSS vulnerability on \"next\" parameter, imported from 'edx-platform'.\r\nhttps://github.com/overhangio/tutor/commit/b46a7b0fa806604eddaed8646a2a8712a8508c79.", "cve": "PVE-2022-51649", "id": "pyup.io-51649", "more_info_path": "/vulnerabilities/PVE-2022-51649/51649", "specs": [ "<14.1.2" ], "v": "<14.1.2" }, { "advisory": "Tutor 14.2.2 fixes a XSS vulnerability in drag-n-drop v2 xblock.\r\nhttps://github.com/overhangio/tutor/commit/0e8f55798c5eeb745edf4d4a003d746f209e1a5a", "cve": "PVE-2022-52099", "id": "pyup.io-52099", "more_info_path": "/vulnerabilities/PVE-2022-52099/52099", "specs": [ "<14.2.2" ], "v": "<14.2.2" }, { "advisory": "Tutor 15.3.0 includes a fix for CVE-2023-23611: Any LTI tool that is integrated with on the Open edX platform can post a grade back for any LTI XBlock so long as it knows or can guess the block location for that XBlock.\r\nhttps://github.com/overhangio/tutor/commit/9df3b18c31ff79d3ba325b028c8effbf3de89c9b", "cve": "CVE-2023-23611", "id": "pyup.io-53221", "more_info_path": "/vulnerabilities/CVE-2023-23611/53221", "specs": [ "<15.3.0" ], "v": "<15.3.0" }, { "advisory": "Tutor 3.12.3 applies most recent security patches for the 'edx-platform' underlying dependency.", "cve": "PVE-2021-40920", "id": "pyup.io-40920", "more_info_path": "/vulnerabilities/PVE-2021-40920/40920", "specs": [ "<3.12.3" ], "v": "<3.12.3" }, { "advisory": "Tutor 3.3.5 updates the 'Jinja2' underlying dependency to v2.10.1 to fix a security vulnerability.", "cve": "CVE-2019-10906", "id": "pyup.io-40925", "more_info_path": "/vulnerabilities/CVE-2019-10906/40925", "specs": [ "<3.3.5" ], "v": "<3.3.5" }, { "advisory": "Tutor 3.5.2 includes a fix for an XSS vulnerability affecting 'edx-platform'.\r\nhttps://github.com/overhangio/tutor/commit/c02fabb493b5e5b6ca6e2ad5612219e6c9803791", "cve": "CVE-2019-20513", "id": "pyup.io-40924", "more_info_path": "/vulnerabilities/CVE-2019-20513/40924", "specs": [ "<3.5.2" ], "v": "<3.5.2" }, { "advisory": "Tutor 3.6.0 fixes insecure static asset loading when web proxy is enabled.", "cve": "PVE-2021-40923", "id": "pyup.io-40923", "more_info_path": "/vulnerabilities/PVE-2021-40923/40923", "specs": [ "<3.6.0" ], "v": "<3.6.0" }, { "advisory": "Tutor 3.6.3 fixes a template injection vulnerability in 'CustomTagModule'.\r\nhttps://github.com/overhangio/tutor/commit/bcf1ffe556151745c0ae38dcd13fe8dfc4d77a6c", "cve": "PVE-2021-40922", "id": "pyup.io-40922", "more_info_path": "/vulnerabilities/PVE-2021-40922/40922", "specs": [ "<3.6.3" ], "v": "<3.6.3" }, { "advisory": "Tutor 3.9.0 includes security patches for the 'Django' underlying dependency (1.11.21 -> 1.11.27).", "cve": "CVE-2019-19118", "id": "pyup.io-49778", "more_info_path": "/vulnerabilities/CVE-2019-19118/49778", "specs": [ "<3.9.0" ], "v": "<3.9.0" }, { "advisory": "Tutor 3.9.0 includes security patches for the 'Django' underlying dependency (1.11.21 -> 1.11.27).", "cve": "CVE-2019-14232", "id": "pyup.io-49774", "more_info_path": "/vulnerabilities/CVE-2019-14232/49774", "specs": [ "<3.9.0" ], "v": "<3.9.0" }, { "advisory": "Tutor 3.9.0 includes security patches for the 'Django' underlying dependency (1.11.21 -> 1.11.27).", "cve": "CVE-2019-14233", "id": "pyup.io-49775", "more_info_path": "/vulnerabilities/CVE-2019-14233/49775", "specs": [ "<3.9.0" ], "v": "<3.9.0" }, { "advisory": "Tutor 3.9.0 includes security patches for the 'Django' underlying dependency (1.11.21 -> 1.11.27).", "cve": "CVE-2019-14235", "id": "pyup.io-49777", "more_info_path": "/vulnerabilities/CVE-2019-14235/49777", "specs": [ "<3.9.0" ], "v": "<3.9.0" }, { "advisory": "Tutor 3.9.0 includes security patches for the 'Django' underlying dependency (1.11.21 -> 1.11.27).", "cve": "CVE-2019-12308", "id": "pyup.io-40921", "more_info_path": "/vulnerabilities/CVE-2019-12308/40921", "specs": [ "<3.9.0" ], "v": "<3.9.0" }, { "advisory": "Tutor 3.9.0 includes security patches for the 'Django' underlying dependency (1.11.21 -> 1.11.27).", "cve": "CVE-2019-14234", "id": "pyup.io-49776", "more_info_path": "/vulnerabilities/CVE-2019-14234/49776", "specs": [ "<3.9.0" ], "v": "<3.9.0" }, { "advisory": "Tutor 3.9.0 includes security patches for the 'Django' underlying dependency (1.11.21 -> 1.11.27).", "cve": "CVE-2019-12781", "id": "pyup.io-49773", "more_info_path": "/vulnerabilities/CVE-2019-12781/49773", "specs": [ "<3.9.0" ], "v": "<3.9.0" }, { "advisory": "Tutor 3.9.0 includes security patches for the 'Django' underlying dependency (1.11.21 -> 1.11.27).", "cve": "CVE-2019-19844", "id": "pyup.io-49779", "more_info_path": "/vulnerabilities/CVE-2019-19844/49779", "specs": [ "<3.9.0" ], "v": "<3.9.0" }, { "advisory": "Affected versions of the tutor package are vulnerable to Information Disclosure due to improper cache-control and session handling after logout. In Overhang.IO Tutor (tutor-open-edx) 20.0.2, responses for authenticated pages, such as the account settings view, are returned without Cache-Control headers and without a client-side check that the user is still logged in, allowing previously rendered pages containing personally identifiable information to be served directly from the browser cache.", "cve": "CVE-2025-65681", "id": "pyup.io-82202", "more_info_path": "/vulnerabilities/CVE-2025-65681/82202", "specs": [ "<=20.0.2" ], "v": "<=20.0.2" } ], "tweepy": [ { "advisory": "Tweepy does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate, related to use of the Python httplib library.", "cve": "CVE-2012-5825", "id": "pyup.io-26168", "more_info_path": "/vulnerabilities/CVE-2012-5825/26168", "specs": [ "<3.0" ], "v": "<3.0" } ], "twilio": [ { "advisory": "twilio before 3.5.0 is vulnerable to a timing attack vector in signature validation.", "cve": "PVE-2021-26169", "id": "pyup.io-26169", "more_info_path": "/vulnerabilities/PVE-2021-26169/26169", "specs": [ "<3.5.0" ], "v": "<3.5.0" }, { "advisory": "Twilio 7.16.2 requires 'pygments>=2.7.4' to include security fixes.", "cve": "CVE-2021-27291", "id": "pyup.io-53125", "more_info_path": "/vulnerabilities/CVE-2021-27291/53125", "specs": [ "<7.16.2" ], "v": "<7.16.2" }, { "advisory": "Twilio 7.16.2 requires 'pygments>=2.7.4' to include security fixes.", "cve": "CVE-2021-20270", "id": "pyup.io-53071", "more_info_path": "/vulnerabilities/CVE-2021-20270/53071", "specs": [ "<7.16.2" ], "v": "<7.16.2" }, { "advisory": "Twilio version 9.0.5 has updated its certifi library from version 2021.10.8 to 2023.7.22 in response to the security concerns outlined in CVE-2023-32681.", "cve": "CVE-2023-32681", "id": "pyup.io-68034", "more_info_path": "/vulnerabilities/CVE-2023-32681/68034", "specs": [ "<9.0.5" ], "v": "<9.0.5" }, { "advisory": "Twilio version 9.0.5 has updated its certifi library from version 2021.10.8 to 2023.7.22 to address the security vulnerability identified in CVE-2022-23491.", "cve": "CVE-2022-23491", "id": "pyup.io-67976", "more_info_path": "/vulnerabilities/CVE-2022-23491/67976", "specs": [ "<9.0.5" ], "v": "<9.0.5" }, { "advisory": "Twilio version 9.0.5 has upgraded its certifi library from version 2021.10.8 to 2023.7.22 in response to the security issue detailed in CVE-2023-37920.", "cve": "CVE-2023-37920", "id": "pyup.io-68033", "more_info_path": "/vulnerabilities/CVE-2023-37920/68033", "specs": [ "<9.0.5" ], "v": "<9.0.5" }, { "advisory": "Twilio version 9.1.0 includes a security upgrade for the aiohttp dependency, updating it from version 3.8.6 to 3.9.4. This update addresses the vulnerability identified as CVE-2024-27306.", "cve": "CVE-2024-27306", "id": "pyup.io-71167", "more_info_path": "/vulnerabilities/CVE-2024-27306/71167", "specs": [ "<9.1.0" ], "v": "<9.1.0" } ], "twine": [ { "advisory": "Twine 2.0.0 updates requests to 2.20 (or later) to include a security fix.", "cve": "CVE-2018-18074", "id": "pyup.io-37504", "more_info_path": "/vulnerabilities/CVE-2018-18074/37504", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "twirp": [ { "advisory": "A security vulnerability was discovered in twirp before 5.5.1 in the 'requirements.txt' file that is used to test Python-generated code, and could be used as sub-dependency checks for Python projects using Twirp.", "cve": "PVE-2021-39334", "id": "pyup.io-39334", "more_info_path": "/vulnerabilities/PVE-2021-39334/39334", "specs": [ "<5.5.1" ], "v": "<5.5.1" } ], "twisted": [ { "advisory": "Twisted Web 16.4.0 includes the following three security fixes:\r\n- A bug in twisted.web.server.Site.makeSession which may lead to predictable session IDs was fixed. Session IDs are now generated securely using `os.urandom`.\r\n- twisted.web.server.Request.getSession will now, for a request sent over HTTPS, set a \"Secure\" cookie, preventing the secure session from being sent over plain-text HTTP. \r\n- twisted.web.twcgi.CGIScript will now not pass the \"Proxy\" header to CGI scripts, as a mitigation to CVE-2016-1000111.", "cve": "CVE-2016-1000111", "id": "pyup.io-38551", "more_info_path": "/vulnerabilities/CVE-2016-1000111/38551", "specs": [ "<16.4.0" ], "v": "<16.4.0" }, { "advisory": "In twisted Core 17.1.0, twisted.internet.ssl.CertificateOptions has the new constructor argument 'raiseMinimumTo', allowing you to increase the minimum TLS version to this version or Twisted's default, whichever is higher. The additional new constructor arguments 'lowerMaximumSecurityTo' and 'insecurelyLowerMinimumTo' allow finer grained control over negotiated versions that don't honour Twisted's defaults, for working around broken peers, at the cost of reducing the security of the TLS it will negotiate. (#6800)", "cve": "PVE-2021-34914", "id": "pyup.io-34914", "more_info_path": "/vulnerabilities/PVE-2021-34914/34914", "specs": [ "<17.1.0" ], "v": "<17.1.0" }, { "advisory": "Twisted 19.10.0 includes security fixes to HTTP/2 DoS Attacks: Ping, Reset, and Settings Floods.\r\nhttps://github.com/advisories/GHSA-32gv-6cf3-wcmq", "cve": "CVE-2019-9515", "id": "pyup.io-55100", "more_info_path": "/vulnerabilities/CVE-2019-9515/55100", "specs": [ "<19.10.0" ], "v": "<19.10.0" }, { "advisory": "Twisted 19.10.0 includes security fixes to HTTP/2 DoS Attacks: Ping, Reset, and Settings Floods.\r\nhttps://github.com/advisories/GHSA-32gv-6cf3-wcmq", "cve": "CVE-2019-9514", "id": "pyup.io-55099", "more_info_path": "/vulnerabilities/CVE-2019-9514/55099", "specs": [ "<19.10.0" ], "v": "<19.10.0" }, { "advisory": "Twisted 19.10.0 includes security fixes to HTTP/2 DoS Attacks: Ping, Reset, and Settings Floods.\r\nhttps://github.com/advisories/GHSA-32gv-6cf3-wcmq", "cve": "CVE-2019-9512", "id": "pyup.io-55098", "more_info_path": "/vulnerabilities/CVE-2019-9512/55098", "specs": [ "<19.10.0" ], "v": "<19.10.0" }, { "advisory": "Before twisted 19.2.0, the twisted.web.client.Request and twisted.web.client.HTTPClient were both vulnerable to header injection attacks. They now replace linear whitespace ('\\r', '\\n', and '\\r\\n') with a single space. (#9421)", "cve": "PVE-2021-37040", "id": "pyup.io-37040", "more_info_path": "/vulnerabilities/PVE-2021-37040/37040", "specs": [ "<19.2.0" ], "v": "<19.2.0" }, { "advisory": "In Twisted before 19.2.1, twisted.web did not validate or sanitize URIs or HTTP methods, allowing an attacker to inject invalid characters such as CRLF.", "cve": "CVE-2019-12387", "id": "pyup.io-37209", "more_info_path": "/vulnerabilities/CVE-2019-12387/37209", "specs": [ "<19.2.1" ], "v": "<19.2.1" }, { "advisory": "In twisted 19.7.0, twisted.words.protocols.jabber.xmlstream.TLSInitiatingInitializer properly verifies the server's certificate against platform CAs and the stream's domain, mitigating CVE-2019-12855. (#9561)", "cve": "CVE-2019-12855", "id": "pyup.io-37554", "more_info_path": "/vulnerabilities/CVE-2019-12855/37554", "specs": [ "<19.7.0" ], "v": "<19.7.0" }, { "advisory": "Twisted 20.3.0 includes a fix for CVE-2020-10108: In Twisted Web through 19.10.0, there was an HTTP request splitting vulnerability. When presented with two content-length headers, it ignored the first header. When the second content-length value was set to zero, the request body was interpreted as a pipelined request.", "cve": "CVE-2020-10108", "id": "pyup.io-38085", "more_info_path": "/vulnerabilities/CVE-2020-10108/38085", "specs": [ "<20.3.0" ], "v": "<20.3.0" }, { "advisory": "Twisted 22.4.0rc1 includes a fix for CVE-2022-24801: Prior to version 22.4.0rc1, the Twisted Web HTTP 1.1 server, located in the 'twisted.web.http' module, parsed several HTTP request constructs more leniently than permitted by RFC 7230. This non-conformant parsing can lead to desync if requests pass through multiple HTTP parsers, potentially resulting in HTTP request smuggling. Users who may be affected use Twisted Web's HTTP 1.1 server and/or proxy and also pass requests through a different HTTP server and/or proxy. The Twisted Web client is not affected. The HTTP 2.0 server uses a different parser, so it is not affected. Two workarounds are available: Ensure any vulnerabilities in upstream proxies have been addressed, such as by upgrading them; or filtering malformed requests by other means, such as configurating an upstream proxy.\r\nhttps://github.com/twisted/twisted/security/advisories/GHSA-c2jg-hw38-jrqq", "cve": "CVE-2022-24801", "id": "pyup.io-47974", "more_info_path": "/vulnerabilities/CVE-2022-24801/47974", "specs": [ "<22.4.0rc1" ], "v": "<22.4.0rc1" }, { "advisory": "Affected versions of Twisted are vulnerable to XSS. The `twisted.web.util.redirectTo` function contains an HTML injection vulnerability. If application code allows an attacker to control the redirect URL this vulnerability may result in Reflected Cross-Site Scripting (XSS) in the redirect response HTML body.", "cve": "CVE-2024-41810", "id": "pyup.io-73795", "more_info_path": "/vulnerabilities/CVE-2024-41810/73795", "specs": [ "<24.7.0rc1" ], "v": "<24.7.0rc1" }, { "advisory": "Affected versions of Twisted are vulnerable to HTTP Request Smuggling. The HTTP 1.0 and 1.1 server provided by twisted.web could process pipelined HTTP requests out-of-order, possibly resulting in information disclosure.", "cve": "CVE-2024-41671", "id": "pyup.io-73800", "more_info_path": "/vulnerabilities/CVE-2024-41671/73800", "specs": [ "<24.7.0rc1" ], "v": "<24.7.0rc1" }, { "advisory": "Twisted 20.3.0 includes a fix for CVE-2020-10109: In Twisted Web through 19.10.0, there was an HTTP request splitting vulnerability. When presented with a content-length and a chunked encoding header, the content-length took precedence and the remainder of the request body was interpreted as a pipelined request.", "cve": "CVE-2020-10109", "id": "pyup.io-39557", "more_info_path": "/vulnerabilities/CVE-2020-10109/39557", "specs": [ "<=19.10.0" ], "v": "<=19.10.0" }, { "advisory": "Twisted 14.0 trustRoot is not respected in HTTP client.\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-7143", "cve": "CVE-2014-7143", "id": "pyup.io-37757", "more_info_path": "/vulnerabilities/CVE-2014-7143/37757", "specs": [ "==14.0" ], "v": "==14.0" }, { "advisory": "Twisted 22.2.0 includes a fix for CVE-2022-21716: Prior to 22.2.0, Twisted SSH client and server implementation is able to accept an infinite amount of data for the peer's SSH version identifier. This ends up with a buffer using all the available memory.\r\nhttps://github.com/twisted/twisted/security/advisories/GHSA-rv6r-3f5q-9rgx", "cve": "CVE-2022-21716", "id": "pyup.io-45554", "more_info_path": "/vulnerabilities/CVE-2022-21716/45554", "specs": [ ">21.7.0,<22.2.0" ], "v": ">21.7.0,<22.2.0" }, { "advisory": "Affected versions of Twisted, an event-driven network framework, are susceptible to HTTP Request Smuggling. This vulnerability arises from inadequate validation of modified request headers, enabling an attacker to smuggle requests through several techniques: employing multiple Content-Length headers, combining a Content-Length header with a Transfer-Encoding header, or utilizing a Transfer-Encoding header with values other than 'chunked' or 'identity'. This flaw compromises the framework's ability to securely process HTTP requests.", "cve": "PVE-2024-99836", "id": "pyup.io-65584", "more_info_path": "/vulnerabilities/PVE-2024-99836/65584", "specs": [ ">=0,<20.3.0" ], "v": ">=0,<20.3.0" }, { "advisory": "Twisted 22.10.0rc1 includes a fix for CVE-2022-39348: NameVirtualHost Host header injection.\r\nhttps://github.com/twisted/twisted/security/advisories/GHSA-vg46-2rrj-3647", "cve": "CVE-2022-39348", "id": "pyup.io-51619", "more_info_path": "/vulnerabilities/CVE-2022-39348/51619", "specs": [ ">=0.9.4,<22.10.0rc1" ], "v": ">=0.9.4,<22.10.0rc1" }, { "advisory": "Twisted 22.1 includes a fix for CVE-2022-21712: In affected versions, twisted exposes cookies and authorization headers when following cross-origin redirects. This issue is present in the 'twisted.web.RedirectAgent' and 'twisted.web.BrowserLikeRedirectAgent' functions. There are no known workarounds.", "cve": "CVE-2022-21712", "id": "pyup.io-44844", "more_info_path": "/vulnerabilities/CVE-2022-21712/44844", "specs": [ ">=11.1,<22.1" ], "v": ">=11.1,<22.1" }, { "advisory": "Twisted 23.10.0rc1 includes a fix for CVE-2023-46137: Disordered HTTP pipeline response in twisted.web. \r\n#NOTE: The data we include in this advisory differs from the publicly available on nist.nvd.gov. As indicated in the project's changelog, the vulnerability was introduced in Twisted 16.3.0.\r\nhttps://github.com/twisted/twisted/security/advisories/GHSA-xc8x-vp79-p3wm", "cve": "CVE-2023-46137", "id": "pyup.io-62105", "more_info_path": "/vulnerabilities/CVE-2023-46137/62105", "specs": [ ">=16.3.0,<23.10.0rc1" ], "v": ">=16.3.0,<23.10.0rc1" } ], "twitchirc": [ { "advisory": "twitchirc before 1.3 does not include a secure option to [`Connection`](twitchirc/twitchirc/connection.py)", "cve": "PVE-2021-37820", "id": "pyup.io-37820", "more_info_path": "/vulnerabilities/PVE-2021-37820/37820", "specs": [ "<1.3" ], "v": "<1.3" } ], "twodolib": [ { "advisory": "Twodolib 0.5.1 updates its dependency 'requests' to v2.20.1 to include a security fix.", "cve": "CVE-2018-18074", "id": "pyup.io-37306", "more_info_path": "/vulnerabilities/CVE-2018-18074/37306", "specs": [ "<0.5.1" ], "v": "<0.5.1" } ], "twyn": [ { "advisory": "Twyn 2.5.7 updates its dependency 'pygments' to version '2.15.1' to include a fix for a ReDoS vulnerability.\r\nhttps://github.com/elementsinteractive/twyn/pull/30", "cve": "CVE-2022-40896", "id": "pyup.io-59793", "more_info_path": "/vulnerabilities/CVE-2022-40896/59793", "specs": [ "<2.5.7" ], "v": "<2.5.7" }, { "advisory": "Twyn Updates jinja2 from 3.1.4 to 3.1.5 to address CVE-2024-56201.", "cve": "CVE-2024-56201", "id": "pyup.io-74748", "more_info_path": "/vulnerabilities/CVE-2024-56201/74748", "specs": [ "<2.8.9" ], "v": "<2.8.9" } ], "twyne": [ { "advisory": "Twyne is a malicious package. It triggers the install of W4SP Stealer in your system.", "cve": "PVE-2022-51679", "id": "pyup.io-51679", "more_info_path": "/vulnerabilities/PVE-2022-51679/51679", "specs": [ ">0" ], "v": ">0" } ], "txaws": [ { "advisory": "txAWS (all current versions) fail to perform complete certificate verification resulting in vulnerability to MitM attacks and information disclosure.", "cve": "CVE-2017-1000007", "id": "pyup.io-42244", "more_info_path": "/vulnerabilities/CVE-2017-1000007/42244", "specs": [ ">0" ], "v": ">0" } ], "type-color": [ { "advisory": "Type-color is a malicious package. It triggers the install of W4SP Stealer in your system.", "cve": "PVE-2022-51698", "id": "pyup.io-51698", "more_info_path": "/vulnerabilities/PVE-2022-51698/51698", "specs": [ ">0" ], "v": ">0" } ], "typed-ast": [ { "advisory": "Typed_ast 1.3.0 and 1.3.1 have a handle_keywordonly_args out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not execute) Python code. (This issue also affected certain Python 3.8.0-alpha prereleases.) See: CVE-2019-19274.", "cve": "CVE-2019-19274", "id": "pyup.io-37767", "more_info_path": "/vulnerabilities/CVE-2019-19274/37767", "specs": [ "<=1.3.2" ], "v": "<=1.3.2" }, { "advisory": "Typed_ast 1.3.0 and 1.3.1 have an ast_for_arguments out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not execute) Python code. (This issue also affected certain Python 3.8.0-alpha prereleases.) See: CVE-2019-19275.", "cve": "CVE-2019-19275", "id": "pyup.io-37768", "more_info_path": "/vulnerabilities/CVE-2019-19275/37768", "specs": [ "<=1.3.2" ], "v": "<=1.3.2" } ], "typed-ffmpeg": [ { "advisory": "Typed-ffmpeg 1.0.4 enhances security by restricting class loading exclusively to the ffmpeg module, preventing unauthorized or unsafe class loading practices.", "cve": "PVE-2024-67006", "id": "pyup.io-67006", "more_info_path": "/vulnerabilities/PVE-2024-67006/67006", "specs": [ "<1.0.4" ], "v": "<1.0.4" } ], "typedb-client": [ { "advisory": "Typedb-client 2.1.1 implements secure channels for authentication. SSL is now required for connections to TypeDB cluster.", "cve": "PVE-2021-41727", "id": "pyup.io-41727", "more_info_path": "/vulnerabilities/PVE-2021-41727/41727", "specs": [ "<2.1.1" ], "v": "<2.1.1" } ], "typedb-driver": [ { "advisory": "Typedb-driver 2.1.1 includes a fix for an unsafe defaults vulnerability: SSL is now required for connections to TypeDB cluster.\r\nhttps://github.com/vaticle/typedb-driver-python/pull/225", "cve": "PVE-2023-61485", "id": "pyup.io-61485", "more_info_path": "/vulnerabilities/PVE-2023-61485/61485", "specs": [ "<2.1.1" ], "v": "<2.1.1" } ], "typesafe-conductr-cli": [ { "advisory": "Typesafe-conductr-cli 0.58 secures bundle and bundle configuration files.\r\nhttps://github.com/typesafehub/conductr-cli/pull/161/commits/2732f66d575772213af809aa17fb2214d62dc678", "cve": "PVE-2017-47604", "id": "pyup.io-47604", "more_info_path": "/vulnerabilities/PVE-2017-47604/47604", "specs": [ "<0.58" ], "v": "<0.58" } ], "typesense": [ { "advisory": "Typesense 0.13.0 allows one to generate API keys with fine-grained access control restrictions for better security.", "cve": "PVE-2021-38798", "id": "pyup.io-38798", "more_info_path": "/vulnerabilities/PVE-2021-38798/38798", "specs": [ "<0.13.0" ], "v": "<0.13.0" }, { "advisory": "Affected versions of Typesense are potentially vulnerable to a race condition in the image embedding module. The issue affects the embed and batch_embed methods in the CLIPImageEmbedder class.", "cve": "PVE-2025-75993", "id": "pyup.io-75993", "more_info_path": "/vulnerabilities/PVE-2025-75993/75993", "specs": [ "<28.0" ], "v": "<28.0" } ], "typestring": [ { "advisory": "Typestring is a malicious package. It triggers the install of W4SP Stealer in your system.", "cve": "PVE-2022-51672", "id": "pyup.io-51672", "more_info_path": "/vulnerabilities/PVE-2022-51672/51672", "specs": [ ">0" ], "v": ">0" } ], "typesutil": [ { "advisory": "Typesutil is a malicious package. It triggers the install of W4SP Stealer in your system.", "cve": "PVE-2022-51671", "id": "pyup.io-51671", "more_info_path": "/vulnerabilities/PVE-2022-51671/51671", "specs": [ ">0" ], "v": ">0" } ], "typst": [ { "advisory": "Typst version 0.11.1 addresses a security vulnerability that allowed image files from known paths outside of the project directory to be embedded into the PDF. This update ensures that only files within the project directory can be embedded, preventing unauthorized access to and inclusion of external files.", "cve": "PVE-2024-71076", "id": "pyup.io-71076", "more_info_path": "/vulnerabilities/PVE-2024-71076/71076", "specs": [ "<0.11.1" ], "v": "<0.11.1" } ], "ua-parser": [ { "advisory": "Certain versions of ua_parser, a Python library for parsing browser user agents, are susceptible to arbitrary code execution attacks due to the use of the insecure YAML.load() function.", "cve": "PVE-2024-99835", "id": "pyup.io-65594", "more_info_path": "/vulnerabilities/PVE-2024-99835/65594", "specs": [ ">=0,<0.5.1" ], "v": ">=0,<0.5.1" } ], "ubi-reader": [ { "advisory": "A vulnerability, which was classified as problematic, has been found in UBI Reader up to 0.8.0. Affected by this issue is the function ubireader_extract_files of the file ubireader/ubifs/output.py of the component UBIFS File Handler. The manipulation leads to path traversal. The attack may be launched remotely. Upgrading to version 0.8.5 can address this issue. The name of the patch is d5d68e6b1b9f7070c29df5f67fc060f579ae9139. It is recommended to upgrade the affected component. VDB-216146 is the identifier assigned to this vulnerability.", "cve": "CVE-2022-4572", "id": "pyup.io-54605", "more_info_path": "/vulnerabilities/CVE-2022-4572/54605", "specs": [ ">=0,<0.8.5" ], "v": ">=0,<0.8.5" }, { "advisory": "ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory). This is due to the fact that a node name (dent_node.name) is considered trusted and joined to the extraction directory path during processing, then the node content is written to that joined path. By crafting a malicious UBIFS file with node names holding path traversal payloads (e.g. ../../tmp/outside.txt), it's possible to force ubi_reader to write outside of the extraction directory. This issue affects ubi-reader before 0.8.5.\n\nAffected functions:\nubireader.ubifs.output.extract_dents", "cve": "CVE-2023-0591", "id": "pyup.io-54623", "more_info_path": "/vulnerabilities/CVE-2023-0591/54623", "specs": [ ">=0,<0.8.5" ], "v": ">=0,<0.8.5" } ], "udata": [ { "advisory": "Udata 1.3.7 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/opendatateam/udata/pull/1606", "cve": "PVE-2023-59607", "id": "pyup.io-59607", "more_info_path": "/vulnerabilities/PVE-2023-59607/59607", "specs": [ "<1.3.7" ], "v": "<1.3.7" }, { "advisory": "Udata 1.6.16 prevents Google ranking spam attacks on reuse pages (`rel=nofollow` on reuse link) - see: https://github.com/opendatateam/udata/pull/2320", "cve": "PVE-2021-37589", "id": "pyup.io-37589", "more_info_path": "/vulnerabilities/PVE-2021-37589/37589", "specs": [ "<1.6.16" ], "v": "<1.6.16" }, { "advisory": "Affected versions of the udata package are vulnerable to Denial of Service (DoS) attacks due to unhandled exceptions that occur during email confirmation failures. The init_app method in udata/auth/__init__.py lacked a defined SECURITY_CONFIRM_ERROR_VIEW, causing the confirmation endpoint to crash instead of redirecting when an error occurred.", "cve": "PVE-2025-80412", "id": "pyup.io-80412", "more_info_path": "/vulnerabilities/PVE-2025-80412/80412", "specs": [ "<12.0.1" ], "v": "<12.0.1" }, { "advisory": "Udata 2.0.2 disallow html tags in markdown-it (JS markdown rendering) for security reasons. See: .", "cve": "PVE-2021-38161", "id": "pyup.io-38161", "more_info_path": "/vulnerabilities/PVE-2021-38161/38161", "specs": [ "<2.0.2" ], "v": "<2.0.2" }, { "advisory": "Udata 5.0.2 updates its dependency 'flask-security-too' to v4.0.0 to include a fix for a reachable vulnerability.\r\nhttps://github.com/opendatateam/udata/pull/2772", "cve": "PVE-2022-52104", "id": "pyup.io-52104", "more_info_path": "/vulnerabilities/PVE-2022-52104/52104", "specs": [ "<5.0.2" ], "v": "<5.0.2" }, { "advisory": "Udata 6.1.3 includes a fix for a XSS vulnerability.\r\nhttps://github.com/opendatateam/udata/pull/2843", "cve": "PVE-2023-55058", "id": "pyup.io-55058", "more_info_path": "/vulnerabilities/PVE-2023-55058/55058", "specs": [ "<6.1.3" ], "v": "<6.1.3" }, { "advisory": "Udata 6.2.0 adds 'SESSION_COOKIE_SECURE = True' by default.\r\nhttps://github.com/opendatateam/udata/pull/2910", "cve": "PVE-2023-62199", "id": "pyup.io-62199", "more_info_path": "/vulnerabilities/PVE-2023-62199/62199", "specs": [ "<6.2.0" ], "v": "<6.2.0" } ], "udata-front": [ { "advisory": "Udata-front version 1.1.0 unsets .vue delimiters used in HTML templates to prevent injections.\r\nhttps://github.com/etalab/udata-front/pull/11", "cve": "PVE-2021-42173", "id": "pyup.io-42173", "more_info_path": "/vulnerabilities/PVE-2021-42173/42173", "specs": [ "<1.1.0" ], "v": "<1.1.0" }, { "advisory": "Udata-front 3.1.3@lhci/cli updates its NPM dependency 'lhci' to v0.10.0 to include security fixes.\r\nhttps://github.com/etalab/udata-front/pull/211", "cve": "PVE-2023-53517", "id": "pyup.io-53517", "more_info_path": "/vulnerabilities/PVE-2023-53517/53517", "specs": [ "<3.1.3" ], "v": "<3.1.3" }, { "advisory": "Udata-front 3.2.1 updates its NPM dependency 'browserslist' to v4.21.5 to include a security fix.", "cve": "CVE-2021-23364", "id": "pyup.io-53904", "more_info_path": "/vulnerabilities/CVE-2021-23364/53904", "specs": [ "<3.2.1" ], "v": "<3.2.1" }, { "advisory": "Udata-front 3.2.2 updates its dependency 'wtforms' to version '3.0.1' to include a security fix.\r\nhttps://github.com/etalab/udata-front/pull/224", "cve": "PVE-2021-42852", "id": "pyup.io-59116", "more_info_path": "/vulnerabilities/PVE-2021-42852/59116", "specs": [ "<3.2.2" ], "v": "<3.2.2" } ], "ugoira": [ { "advisory": "Ugoira 0.5.0 uses secure protocol (HTTPS) instead of naive (HTTP).", "cve": "PVE-2021-37200", "id": "pyup.io-37200", "more_info_path": "/vulnerabilities/PVE-2021-37200/37200", "specs": [ "<0.5.0" ], "v": "<0.5.0" } ], "uharfbuzz": [ { "advisory": "HarfBuzz 2.9.0 has an out-of-bounds write in hb_bit_set_invertible_t::set (called from hb_sparseset_t::set and hb_set_copy).", "cve": "CVE-2021-45931", "id": "pyup.io-62200", "more_info_path": "/vulnerabilities/CVE-2021-45931/62200", "specs": [ "==2.9.0" ], "v": "==2.9.0" } ], "uiautomator2": [ { "advisory": "Uiautomator2 2.13.2 updates its dependency 'atx-agent' to v0.9.6 to include a security fix.\r\nhttps://github.com/openatx/uiautomator2/commit/858b4aa48bc63c4000364c0665d82823b641d4dd", "cve": "PVE-2021-41029", "id": "pyup.io-41029", "more_info_path": "/vulnerabilities/PVE-2021-41029/41029", "specs": [ "<2.13.2" ], "v": "<2.13.2" } ], "ujson": [ { "advisory": "Ujson 5.4.0 includes a fix for CVE-2022-31117: In versions prior to 5.4.0 an error occurring while reallocating a buffer for string decoding can cause the buffer to get freed twice. Due to how UltraJSON uses the internal decoder, this double free is impossible to trigger from Python.\r\nhttps://github.com/ultrajson/ultrajson/security/advisories/GHSA-fm67-cv37-96ff", "cve": "CVE-2022-31117", "id": "pyup.io-49755", "more_info_path": "/vulnerabilities/CVE-2022-31117/49755", "specs": [ "<5.4.0" ], "v": "<5.4.0" }, { "advisory": "Ujson 5.4.0 includes a fix for CVE-2022-31116: Incorrect handling of invalid surrogate pair characters.\r\nhttps://github.com/ultrajson/ultrajson/security/advisories/GHSA-wpqr-jcpx-745r", "cve": "CVE-2022-31116", "id": "pyup.io-49754", "more_info_path": "/vulnerabilities/CVE-2022-31116/49754", "specs": [ "<5.4.0" ], "v": "<5.4.0" }, { "advisory": "UltraJSON (aka ujson) through 5.1.0 has a stack-based buffer overflow in Buffer_AppendIndentUnchecked (called from encode). Exploitation can, for example, use a large amount of indentation.", "cve": "CVE-2021-45958", "id": "pyup.io-46499", "more_info_path": "/vulnerabilities/CVE-2021-45958/46499", "specs": [ "<=5.1.0" ], "v": "<=5.1.0" } ], "ultralytics": [ { "advisory": "Ultralytics version 8.0.5 implements a security update that addresses two significant vulnerabilities: command injection and path traversal. If exploited, it could allow unauthorized execution of arbitrary commands and unauthorized access to files on the server. \r\nhttps://github.com/ultralytics/ultralytics/pull/888/files", "cve": "PVE-2024-64065", "id": "pyup.io-64065", "more_info_path": "/vulnerabilities/PVE-2024-64065/64065", "specs": [ "<8.0.5" ], "v": "<8.0.5" }, { "advisory": "Affected versions of the ultralytics package are potentially vulnerable to Code Injection due to the unsafe use of eval() on attacker-controllable strings before commit 699866c. The cfg.smart_value function, the string-handling branch in utils.checks.check_imgsz, and the initializer in utils/triton.py evaluated arbitrary text with eval() (e.g., parsing imgsz or Triton metadata), instead of a safe parser like ast.literal_eval(), enabling execution of embedded Python expressions.", "cve": "PVE-2025-81385", "id": "pyup.io-81385", "more_info_path": "/vulnerabilities/PVE-2025-81385/81385", "specs": [ "<8.3.226" ], "v": "<8.3.226" }, { "advisory": "Ultralytics 8.3.41, 8.3.42, 8.3.45 and 8.3.46 contain malicious code. The tampered code downloaded 'XMRig', a cryptocurrency miner. Hackers infiltrated the project\u2019s build environment, which prepares the software for release. The content in the GitHub repository did not match the content of the matching PyPI package, as malicious actors compromised the build environment and injected malicious code after the code review process was completed.", "cve": "PVE-2024-74473", "id": "pyup.io-74473", "more_info_path": "/vulnerabilities/PVE-2024-74473/74473", "specs": [ "==8.3.41", "==8.3.42", "==8.3.45", "==8.3.46" ], "v": "==8.3.41,==8.3.42,==8.3.45,==8.3.46" } ], "ultralytics-actions": [ { "advisory": "The Ultralytics-actions dependency has been updated to require requests library version 2.32.3 or higher. This update was made to address the security vulnerability identified by CVE-2024-35195.", "cve": "CVE-2024-35195", "id": "pyup.io-74821", "more_info_path": "/vulnerabilities/CVE-2024-35195/74821", "specs": [ "<0.0.35" ], "v": "<0.0.35" } ], "uma-sdk": [ { "advisory": "Prior versions of the uma package may be vulnerable to improper input validation in the LNURLP request parsing function. The receiver address component of the URL was not validated, potentially allowing malicious input. This could lead to unexpected behavior or vulnerabilities in systems processing this data. The issue is fixed by implementing a strict regex pattern to validate the receiver address. Users should update to the latest version containing this fix to ensure proper input validation and mitigate potential security risks associated with malformed or malicious LNURLP requests.", "cve": "PVE-2024-73332", "id": "pyup.io-73332", "more_info_path": "/vulnerabilities/PVE-2024-73332/73332", "specs": [ "<1.2.2" ], "v": "<1.2.2" } ], "unbabel-comet": [ { "advisory": "Unbabel-comet 1.1.0 updates its dependency 'pytorch-lightning' to v1.6.0 to include security fixes.", "cve": "CVE-2021-4118", "id": "pyup.io-49247", "more_info_path": "/vulnerabilities/CVE-2021-4118/49247", "specs": [ "<1.1.0" ], "v": "<1.1.0" }, { "advisory": "Unbabel-comet 1.1.0 updates its dependency 'pytorch-lightning' to v1.6.0 to include security fixes.", "cve": "CVE-2022-0845", "id": "pyup.io-49297", "more_info_path": "/vulnerabilities/CVE-2022-0845/49297", "specs": [ "<1.1.0" ], "v": "<1.1.0" } ], "unearth": [ { "advisory": "Unearth 0.11.2 includes a security fix: Validate the package name extracted from the part before the last hyphen.\r\nhttps://github.com/frostming/unearth/pull/77", "cve": "PVE-2023-61901", "id": "pyup.io-61901", "more_info_path": "/vulnerabilities/PVE-2023-61901/61901", "specs": [ "<0.11.2" ], "v": "<0.11.2" }, { "advisory": "Unearth 0.11.2 includes a fix for CVE-2023-45805: It's possible to craft a malicious pdm.lock file that could allow e.g. an insider or a malicious open source project to appear to depend on a trusted PyPI project, but actually install another project.\r\nhttps://github.com/frostming/unearth/pull/77", "cve": "CVE-2023-45805", "id": "pyup.io-61951", "more_info_path": "/vulnerabilities/CVE-2023-45805/61951", "specs": [ "<0.11.2" ], "v": "<0.11.2" } ], "uniapi": [ { "advisory": "Uniapi version 1.0.7 introduces code that would execute on import of the module and download a script from a remote URL, and would then execute the downloaded script in a thread. The downloaded script would harvest system information and POST the information to another remote URL. This code was found in the PyPI release artifacts and was not present in the public GitHub repository.", "cve": "PVE-2025-76351", "id": "pyup.io-76351", "more_info_path": "/vulnerabilities/PVE-2025-76351/76351", "specs": [ ">=0" ], "v": ">=0" } ], "unicef-locations": [ { "advisory": "Unicef-locations 3.1 allows as dependency an insecure version of Django.", "cve": "CVE-2021-35042", "id": "pyup.io-43670", "more_info_path": "/vulnerabilities/CVE-2021-35042/43670", "specs": [ "<=3.1" ], "v": "<=3.1" } ], "unicef-rest-export": [ { "advisory": "Unicef-rest-export 0.5.2 updates its dependency 'Pyyaml' to v5.1 to include a security patch.", "cve": "CVE-2017-18342", "id": "pyup.io-43455", "more_info_path": "/vulnerabilities/CVE-2017-18342/43455", "specs": [ "<0.5.2" ], "v": "<0.5.2" }, { "advisory": "Unicef-rest-export 0.5.2 updates its dependency 'Django' to v2.1.7 to include a security patch.", "cve": "CVE-2019-6975", "id": "pyup.io-36990", "more_info_path": "/vulnerabilities/CVE-2019-6975/36990", "specs": [ "<0.5.2" ], "v": "<0.5.2" } ], "unicms": [ { "advisory": "Unicms 0.30.2 includes a fix for a XSS vulnerability.\r\nhttps://github.com/UniversitaDellaCalabria/uniCMS/commit/05476a93ecd3e3c2511077629ec5da7d6c07d2bf", "cve": "PVE-2021-43424", "id": "pyup.io-43424", "more_info_path": "/vulnerabilities/PVE-2021-43424/43424", "specs": [ "<0.30.2" ], "v": "<0.30.2" } ], "unicorn": [ { "advisory": "Unicorn Engine v2.0.0-rc7 contains memory leaks caused by an incomplete unicorn engine initialization.", "cve": "CVE-2022-29695", "id": "pyup.io-62636", "more_info_path": "/vulnerabilities/CVE-2022-29695/62636", "specs": [ "<2.0.0" ], "v": "<2.0.0" }, { "advisory": "Unicorn Engine v2.0.0-rc7 and below was discovered to contain a NULL pointer dereference via qemu_ram_free.", "cve": "CVE-2022-29694", "id": "pyup.io-62635", "more_info_path": "/vulnerabilities/CVE-2022-29694/62635", "specs": [ "<2.0.0" ], "v": "<2.0.0" }, { "advisory": "Unicorn Engine v2.0.0-rc7 and below was discovered to contain a memory leak via the function uc_close at /my/unicorn/uc.c.", "cve": "CVE-2022-29693", "id": "pyup.io-62634", "more_info_path": "/vulnerabilities/CVE-2022-29693/62634", "specs": [ "<2.0.0" ], "v": "<2.0.0" }, { "advisory": "Unicorn 2.1.3 inncludes a fix for a Use After Free vulnerability on flatview copy.", "cve": "PVE-2025-75764", "id": "pyup.io-75764", "more_info_path": "/vulnerabilities/PVE-2025-75764/75764", "specs": [ "<2.1.3" ], "v": "<2.1.3" }, { "advisory": "Unicorn Engine 1.0.2 has an out-of-bounds write in helper_wfe_arm.", "cve": "CVE-2020-36431", "id": "pyup.io-70608", "more_info_path": "/vulnerabilities/CVE-2020-36431/70608", "specs": [ "<=1.0.2" ], "v": "<=1.0.2" }, { "advisory": "Unicorn Engine v1.0.3 was discovered to contain a use-after-free vulnerability via the hook function.", "cve": "CVE-2022-29692", "id": "pyup.io-62631", "more_info_path": "/vulnerabilities/CVE-2022-29692/62631", "specs": [ "==1.0.3" ], "v": "==1.0.3" }, { "advisory": "An issue was discovered in split_region in uc.c in Unicorn Engine before 2.0.0-rc5. It allows local attackers to escape the sandbox. An attacker must first obtain the ability to execute crafted code in the target sandbox in order to exploit this vulnerability. The specific flaw exists within the virtual memory manager. The issue results from the faulty comparison of GVA and GPA while calling uc_mem_map_ptr to free part of a claimed memory block. An attacker can leverage this vulnerability to escape the sandbox and execute arbitrary code on the host machine.", "cve": "CVE-2021-44078", "id": "pyup.io-54096", "more_info_path": "/vulnerabilities/CVE-2021-44078/54096", "specs": [ ">=0,<2.0.0rc1" ], "v": ">=0,<2.0.0rc1" } ], "unicorn-binance-local-depth-cache": [ { "advisory": "Unicorn-binance-local-depth-cache version 2.0.0 updates its `certifi` dependency due to CVE-2023-37920, which has a high severity score of 9.8. This vulnerability involved certifi versions 1.0.1 through 2023.5.7 recognizing \"e-Tugra\" root certificates, which were found to have security issues. Certifi version 2023.07.22 removes these root certificates from the root store to address the vulnerability.", "cve": "CVE-2023-37920", "id": "pyup.io-71050", "more_info_path": "/vulnerabilities/CVE-2023-37920/71050", "specs": [ "<2.0.0" ], "v": "<2.0.0" }, { "advisory": "Unicorn-binance-local-depth-cache version 2.0.0 updates its `cryptography` dependency due to CVE-2023-38325, which has a high severity score of 7.5. This vulnerability affects versions prior to 41.0.2 of the cryptography package for Python and involves mishandling SSH certificates with critical options.", "cve": "CVE-2023-38325", "id": "pyup.io-71038", "more_info_path": "/vulnerabilities/CVE-2023-38325/71038", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "unicorn-binance-rest-api": [ { "advisory": "Unicorn-binance-rest-api version 2.4.0 has raised the minimum required version of `cryptography` to `42.0.4` due to identified vulnerabilities in previous versions, including CVE-2023-38325.", "cve": "CVE-2023-38325", "id": "pyup.io-70978", "more_info_path": "/vulnerabilities/CVE-2023-38325/70978", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Unicorn-binance-rest-api version 2.4.0 has updated the minimum required version of `requests` to `2.31.0` due to vulnerabilities discovered in prior versions, including CVE-2023-32681.", "cve": "CVE-2023-32681", "id": "pyup.io-70979", "more_info_path": "/vulnerabilities/CVE-2023-32681/70979", "specs": [ "<2.4.0" ], "v": "<2.4.0" }, { "advisory": "Unicorn-binance-rest-api version 2.4.0 has increased the minimum required version of `certifi` to `2023.7.22` due to vulnerabilities found in earlier versions, notably CVE-2023-37920.", "cve": "CVE-2023-37920", "id": "pyup.io-70973", "more_info_path": "/vulnerabilities/CVE-2023-37920/70973", "specs": [ "<2.4.0" ], "v": "<2.4.0" } ], "unicorn-binance-websocket-api": [ { "advisory": "Unicorn-binance-websocket-api 2.7.1 updates its dependency 'requests' to include a security fix.", "cve": "CVE-2023-32681", "id": "pyup.io-70996", "more_info_path": "/vulnerabilities/CVE-2023-32681/70996", "specs": [ "<2.7.1" ], "v": "<2.7.1" }, { "advisory": "Unicorn-binance-websocket-api 2.7.1 updates its dependency 'cryptography' to include a security fix.", "cve": "CVE-2023-49083", "id": "pyup.io-71002", "more_info_path": "/vulnerabilities/CVE-2023-49083/71002", "specs": [ "<2.7.1" ], "v": "<2.7.1" }, { "advisory": "Unicorn-binance-websocket-api 2.7.1 updates its dependency 'cryptography' to include a security fix.", "cve": "CVE-2023-38325", "id": "pyup.io-71001", "more_info_path": "/vulnerabilities/CVE-2023-38325/71001", "specs": [ "<2.7.1" ], "v": "<2.7.1" }, { "advisory": "Unicorn-binance-websocket-api 2.7.1 updates its dependency 'certifi' to include a security fix.", "cve": "CVE-2023-37920", "id": "pyup.io-71000", "more_info_path": "/vulnerabilities/CVE-2023-37920/71000", "specs": [ "<2.7.1" ], "v": "<2.7.1" } ], "unipacker": [ { "advisory": "A heap-based buffer overflow was discovered in upx, during the variable 'bucket' points to an inaccessible address. The issue is being triggered in the function PackLinuxElf32::invert_pt_dynamic at p_lx_elf.cpp:1688.", "cve": "CVE-2021-43313", "id": "pyup.io-70905", "more_info_path": "/vulnerabilities/CVE-2021-43313/70905", "specs": [ "<4.0.0" ], "v": "<4.0.0" } ], "uniplot": [ { "advisory": "Uniplot version 0.8.1 updates its numpy dependency to version 1.22.0 or later, responding to CVE-2021-41496.\r\nhttps://github.com/olavolav/uniplot/commit/bd978d09a9b637e8a8bbd90d0cbb2a951b66e5b1", "cve": "CVE-2021-41496", "id": "pyup.io-65868", "more_info_path": "/vulnerabilities/CVE-2021-41496/65868", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Uniplot version 0.8.1 updates its numpy dependency to version 1.22.0 or later, responding to CVE-2021-34141.\r\nhttps://github.com/olavolav/uniplot/commit/bd978d09a9b637e8a8bbd90d0cbb2a951b66e5b1", "cve": "CVE-2021-34141", "id": "pyup.io-65886", "more_info_path": "/vulnerabilities/CVE-2021-34141/65886", "specs": [ "<0.8.1" ], "v": "<0.8.1" } ], "unixgpt": [ { "advisory": "Unixgpt 0.1.6 includes mitigation to avoid prompt injections.\r\nhttps://github.com/jamino30/unixgpt/issues/2", "cve": "PVE-2023-62179", "id": "pyup.io-62179", "more_info_path": "/vulnerabilities/PVE-2023-62179/62179", "specs": [ "<0.1.6" ], "v": "<0.1.6" } ], "unkey.py": [ { "advisory": "Unkey.py version 0.7.2 resolves a race condition within its protected decorator, which occurred when a single client session was initiated and terminated amidst multiple simultaneous requests.", "cve": "PVE-2024-70858", "id": "pyup.io-70858", "more_info_path": "/vulnerabilities/PVE-2024-70858/70858", "specs": [ "<0.7.2" ], "v": "<0.7.2" } ], "unleashclient": [ { "advisory": "Unleashclient 1.0.2 updates its dependency 'requests' to address a security issue.", "cve": "CVE-2018-18074", "id": "pyup.io-36585", "more_info_path": "/vulnerabilities/CVE-2018-18074/36585", "specs": [ "<1.0.2" ], "v": "<1.0.2" } ], "unmanic": [ { "advisory": "Unmanic 0.2.2 updates front-end dependencies to include security fixes.\r\nhttps://github.com/Unmanic/unmanic/commit/2faf7cf79edc77df116df48dbe49c10eb04474b6", "cve": "PVE-2022-48405", "id": "pyup.io-48405", "more_info_path": "/vulnerabilities/PVE-2022-48405/48405", "specs": [ "<0.2.2" ], "v": "<0.2.2" } ], "unoconv": [ { "advisory": "The unoconv package before 0.9 mishandles untrusted pathnames, leading to SSRF and local file inclusion.", "cve": "CVE-2019-17400", "id": "pyup.io-54163", "more_info_path": "/vulnerabilities/CVE-2019-17400/54163", "specs": [ ">=0,<0.9.0" ], "v": ">=0,<0.9.0" } ], "unstructured": [ { "advisory": "Unstructured v.0.14.2 and before is vulnerable to XML External Entity (XXE) via the XMLParser.", "cve": "CVE-2024-46455", "id": "pyup.io-76387", "more_info_path": "/vulnerabilities/CVE-2024-46455/76387", "specs": [ "<0.14.3" ], "v": "<0.14.3" }, { "advisory": "Unstructured fixes a security issue where rst and org files could read files in the local filesystem**. Certain filetypes could 'include' or 'import' local files into their content, allowing partitioning of arbitrary files from the local filesystem. Partitioning of these files is now sandboxed.", "cve": "PVE-2025-75338", "id": "pyup.io-75338", "more_info_path": "/vulnerabilities/PVE-2025-75338/75338", "specs": [ "<0.16.20" ], "v": "<0.16.20" }, { "advisory": "Affected versions of unstructured are vulnerable to Path Traversal attacks. The `partition_msg` function fails to sanitize attachment filenames in email MSG files, leading to malicious attachments with path traversal sequences being able to write files to arbitrary locations outside the intended root directory.\r\n\r\nThis refers to the `GHSA-gm8q-m8mv-jj5m` advisory.", "cve": "PVE-2025-81341", "id": "pyup.io-81341", "more_info_path": "/vulnerabilities/PVE-2025-81341/81341", "specs": [ "<0.18.18" ], "v": "<0.18.18" } ], "untangle": [ { "advisory": "Untangle 1.2.0 prevents XXE attacks by disabling feature_external_ges.\r\nhttps://github.com/stchris/untangle/commit/5c7b7ad87cae6f5f77e55e0948435be0cf80769c", "cve": "PVE-2022-49720", "id": "pyup.io-49720", "more_info_path": "/vulnerabilities/PVE-2022-49720/49720", "specs": [ "<1.2.0" ], "v": "<1.2.0" }, { "advisory": "Untangle 1.2.1 uses 'defusedxml' to prevent XXE attacks.\r\nhttps://github.com/stchris/untangle/pull/94", "cve": "PVE-2022-49723", "id": "pyup.io-49723", "more_info_path": "/vulnerabilities/PVE-2022-49723/49723", "specs": [ "<1.2.1" ], "v": "<1.2.1" }, { "advisory": "Untangle 1.2.1 includes a fix for CVE-2022-33977: Untangle versions 1.2.0 and earlier improperly restricts recursive entity references in DTDs. By exploiting this vulnerability, a remote unauthenticated attacker may cause a denial-of-service (DoS) condition on the server where the product is running.", "cve": "CVE-2022-33977", "id": "pyup.io-50275", "more_info_path": "/vulnerabilities/CVE-2022-33977/50275", "specs": [ "<=1.2.0" ], "v": "<=1.2.0" }, { "advisory": "Untangle 1.2.1 includes a fix for CVE-2022-31471: Untangle versions 1.2.0 and earlier improperly restricts XML external entity references. By exploiting this vulnerability, a remote unauthenticated attacker may read the contents of local files.", "cve": "CVE-2022-31471", "id": "pyup.io-50274", "more_info_path": "/vulnerabilities/CVE-2022-31471/50274", "specs": [ "<=1.2.0" ], "v": "<=1.2.0" } ], "up42-py": [ { "advisory": "Up42-py version 0.37.2 updates its dependency on the pillow library, upgrading from version 10.2.0 to 10.3.0. This update addresses the security vulnerability identified in CVE-2024-28219.", "cve": "CVE-2024-28219", "id": "pyup.io-67975", "more_info_path": "/vulnerabilities/CVE-2024-28219/67975", "specs": [ "<0.37.2" ], "v": "<0.37.2" }, { "advisory": "Up42-py version 0.37.2 updates its dependency on the black library, upgrading from version 22.12.0 to 24.3.0. This update addresses the security vulnerability identified in CVE-2024-21503.", "cve": "CVE-2024-21503", "id": "pyup.io-67942", "more_info_path": "/vulnerabilities/CVE-2024-21503/67942", "specs": [ "<0.37.2" ], "v": "<0.37.2" } ], "upamonkws": [ { "advisory": "Upamonkws is a malicious package. It delivers the W4SP Stealer Malware to your system.\r\nhttps://thehackernews.com/2022/12/w4sp-stealer-discovered-in-multiple.html", "cve": "PVE-2023-52920", "id": "pyup.io-52920", "more_info_path": "/vulnerabilities/PVE-2023-52920/52920", "specs": [ ">0" ], "v": ">0" } ], "upsonic": [ { "advisory": "Affected versions of the Upsonic package are vulnerable to Deserialization of Untrusted Data due to unsafe pickle deserialization in the tool management functionality. The cloudpickle.loads function in the /tools/add_tool endpoint of the Pickle Handler component deserializes user-provided data without proper validation or sanitization, allowing arbitrary Python object deserialization.", "cve": "CVE-2025-6279", "id": "pyup.io-78843", "more_info_path": "/vulnerabilities/CVE-2025-6279/78843", "specs": [ "<0.56.0" ], "v": "<0.56.0" }, { "advisory": "Affected versions of the Upsonic package are vulnerable to Path Traversal due to improper input validation in file path construction. The os.path.join function in markdown/server.py directly uses the file.filename parameter without sanitizing directory traversal sequences, allowing attackers to access files outside the intended directory structure. An attacker can exploit this vulnerability by providing a crafted filename containing directory traversal sequences to read, write, or access arbitrary files on the server filesystem, potentially exposing sensitive configuration files, source code, or other confidential data.", "cve": "CVE-2025-6278", "id": "pyup.io-78842", "more_info_path": "/vulnerabilities/CVE-2025-6278/78842", "specs": [ "<0.56.0" ], "v": "<0.56.0" } ], "upydev": [ { "advisory": "An issue in /upydev/keygen.py in upydev v0.4.3 allows attackers to decrypt sensitive information via weak encryption padding.", "cve": "CVE-2023-48051", "id": "pyup.io-65251", "more_info_path": "/vulnerabilities/CVE-2023-48051/65251", "specs": [ ">=0,<=0.4.3" ], "v": ">=0,<=0.4.3" } ], "urbansim": [ { "advisory": "Urbansim 3.2 includes a security patch for the function 'from_yaml' in 'urbansim/utils/networks.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load(). \r\nhttps://github.com/UDST/urbansim/commit/44ca1d47e50fc9d6e12048329a6ff8907fbbf381", "cve": "CVE-2017-18342", "id": "pyup.io-41398", "more_info_path": "/vulnerabilities/CVE-2017-18342/41398", "specs": [ "<3.2" ], "v": "<3.2" } ], "url-regex": [ { "advisory": "All versions of package url-regex are vulnerable to Regular Expression Denial of Service (ReDoS) which can cause the CPU usage to crash.", "cve": "CVE-2022-21195", "id": "pyup.io-49146", "more_info_path": "/vulnerabilities/CVE-2022-21195/49146", "specs": [ ">0" ], "v": ">0" } ], "urlgrabber": [ { "advisory": "Urlgrabber 4.0.0 includes a fix for CVE-2022-43754: An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in spacewalk/Uyuni of SUSE Linux Enterprise Module for SUSE Manager Server 4.2, SUSE Linux Enterprise Module for SUSE Manager Server 4.3, SUSE Manager Server 4.2 allows remote attackers to embed Javascript code via /rhn/audit/scap/Search.do This issue affects: SUSE Linux Enterprise Module for SUSE Manager Server 4.2 hub-xmlrpc-api-0.7-150300.3.9.2, inter-server-sync-0.2.4-150300.8.25.2, locale-formula-0.3-150300.3.3.2, py27-compat-salt-3000.3-150300.7.7.26.2, python-urlgrabber-3.10.2.1py2_3-150300.3.3.2, spacecmd-4.2.20-150300.4.30.2, spacewalk-backend-4.2.25-150300.4.32.4, spacewalk-client-tools-4.2.21-150300.4.27.3, spacewalk-java-4.2.43-150300.3.48.2, spacewalk-utils-4.2.18-150300.3.21.2, spacewalk-web-4.2.30-150300.3.30.3, susemanager-4.2.38-150300.3.44.3, susemanager-doc-indexes-4.2-150300.12.36.3, susemanager-docs_en-4.2-150300.12.36.2, susemanager-schema-4.2.25-150300.3.30.3, susemanager-sls versions prior to 4.2.28. SUSE Linux Enterprise Module for SUSE Manager Server 4.3 spacewalk-java versions prior to 4.3.39. SUSE Manager Server 4.2 release-notes-susemanager versions prior to 4.2.10.", "cve": "CVE-2022-43754", "id": "pyup.io-51820", "more_info_path": "/vulnerabilities/CVE-2022-43754/51820", "specs": [ ">=3.3.2,<=3.10.2" ], "v": ">=3.3.2,<=3.10.2" }, { "advisory": "Urlgrabber 4.0.0 includes a fix for CVE-2022-43753: A Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in spacewalk/Uyuni of SUSE Linux Enterprise Module for SUSE Manager Server 4.2, SUSE Linux Enterprise Module for SUSE Manager Server 4.3, SUSE Manager Server 4.2 allows remote attackers to read files available to the user running the process, typically tomcat. This issue affects: SUSE Linux Enterprise Module for SUSE Manager Server 4.2 hub-xmlrpc-api-0.7-150300.3.9.2, inter-server-sync-0.2.4-150300.8.25.2, locale-formula-0.3-150300.3.3.2, py27-compat-salt-3000.3-150300.7.7.26.2, python-urlgrabber-3.10.2.1py2_3-150300.3.3.2, spacecmd-4.2.20-150300.4.30.2, spacewalk-backend-4.2.25-150300.4.32.4, spacewalk-client-tools-4.2.21-150300.4.27.3, spacewalk-java-4.2.43-150300.3.48.2, spacewalk-utils-4.2.18-150300.3.21.2, spacewalk-web-4.2.30-150300.3.30.3, susemanager-4.2.38-150300.3.44.3, susemanager-doc-indexes-4.2-150300.12.36.3, susemanager-docs_en-4.2-150300.12.36.2, susemanager-schema-4.2.25-150300.3.30.3, susemanager-sls versions prior to 4.2.28. SUSE Linux Enterprise Module for SUSE Manager Server 4.3 spacewalk-java versions prior to 4.3.39. SUSE Manager Server 4.2 release-notes-susemanager versions prior to 4.2.10.", "cve": "CVE-2022-43753", "id": "pyup.io-51819", "more_info_path": "/vulnerabilities/CVE-2022-43753/51819", "specs": [ ">=3.3.2,<=3.10.2" ], "v": ">=3.3.2,<=3.10.2" }, { "advisory": "Urlgrabber 4.0.0 includes a fix for CVE-2022-31255: An Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in spacewalk/Uyuni of SUSE Linux Enterprise Module for SUSE Manager Server 4.2, SUSE Linux Enterprise Module for SUSE Manager Server 4.3, SUSE Manager Server 4.2 allows remote attackers to read files available to the user running the process, typically tomcat. This issue affects: SUSE Linux Enterprise Module for SUSE Manager Server 4.2 hub-xmlrpc-api-0.7-150300.3.9.2, inter-server-sync-0.2.4-150300.8.25.2, locale-formula-0.3-150300.3.3.2, py27-compat-salt-3000.3-150300.7.7.26.2, python-urlgrabber-3.10.2.1py2_3-150300.3.3.2, spacecmd-4.2.20-150300.4.30.2, spacewalk-backend-4.2.25-150300.4.32.4, spacewalk-client-tools-4.2.21-150300.4.27.3, spacewalk-java-4.2.43-150300.3.48.2, spacewalk-utils-4.2.18-150300.3.21.2, spacewalk-web-4.2.30-150300.3.30.3, susemanager-4.2.38-150300.3.44.3, susemanager-doc-indexes-4.2-150300.12.36.3, susemanager-docs_en-4.2-150300.12.36.2, susemanager-schema-4.2.25-150300.3.30.3, susemanager-sls versions prior to 4.2.28. SUSE Linux Enterprise Module for SUSE Manager Server 4.3 spacewalk-java versions prior to 4.3.39. SUSE Manager Server 4.2 release-notes-susemanager versions prior to 4.2.10.", "cve": "CVE-2022-31255", "id": "pyup.io-51817", "more_info_path": "/vulnerabilities/CVE-2022-31255/51817", "specs": [ ">=3.3.2,<=3.10.2" ], "v": ">=3.3.2,<=3.10.2" } ], "urlib3": [ { "advisory": "urlib3 is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/", "cve": "PVE-2021-34986", "id": "pyup.io-34986", "more_info_path": "/vulnerabilities/PVE-2021-34986/34986", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "urllib": [ { "advisory": "urllib is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/", "cve": "PVE-2021-34987", "id": "pyup.io-34987", "more_info_path": "/vulnerabilities/PVE-2021-34987/34987", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "urllib3": [ { "advisory": "Urllib3 before version 1.23 does not remove the Authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the Authorization header to be exposed to unintended hosts or transmitted in cleartext.", "cve": "CVE-2018-20060", "id": "pyup.io-36541", "more_info_path": "/vulnerabilities/CVE-2018-20060/36541", "specs": [ "<1.23" ], "v": "<1.23" }, { "advisory": "Affected versions of urllib3 are vulnerable Improper Certificate Validation. Urllib3 mishandles certain cases where the desired set of CA certificates is different from the OS store of CA certificates, which results in SSL connections succeeding in situations where a verification failure is the correct outcome. This is related to the use of the ssl_context, ca_certs, or ca_certs_dir argument.", "cve": "CVE-2019-11324", "id": "pyup.io-37071", "more_info_path": "/vulnerabilities/CVE-2019-11324/37071", "specs": [ "<1.24.2" ], "v": "<1.24.2" }, { "advisory": "Affected versions of urllib3 affected versions are vulnerable due to an issue where the authorization HTTP header is not removed when following a cross-origin redirect. This can result in credentials within the authorization header being exposed to unintended hosts or transmitted in cleartext. This vulnerability exists because of an incomplete fix for CVE-2018-20060, which addressed a similar issue case-sensitively.", "cve": "CVE-2018-25091", "id": "pyup.io-71562", "more_info_path": "/vulnerabilities/CVE-2018-25091/71562", "specs": [ "<1.24.2" ], "v": "<1.24.2" }, { "advisory": "Urllib3 1.24.3 includes a fix for CVE-2019-11236: CRLF injection is possible if the attacker controls the request parameter.\r\nhttps://github.com/urllib3/urllib3/commit/5d523706c7b03f947dc50a7e783758a2bfff0532\r\nhttps://github.com/urllib3/urllib3/issues/1553", "cve": "CVE-2019-11236", "id": "pyup.io-37055", "more_info_path": "/vulnerabilities/CVE-2019-11236/37055", "specs": [ "<1.24.3" ], "v": "<1.24.3" }, { "advisory": "Urllib3 1.25.9 includes a fix for CVE-2020-26137: Urllib3 before 1.25.9 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of putrequest(). NOTE: this is similar to CVE-2020-26116.\r\nhttps://github.com/python/cpython/issues/83784\r\nhttps://github.com/urllib3/urllib3/pull/1800", "cve": "CVE-2020-26137", "id": "pyup.io-38834", "more_info_path": "/vulnerabilities/CVE-2020-26137/38834", "specs": [ "<1.25.9" ], "v": "<1.25.9" }, { "advisory": "Urllib3 1.26.17 and 2.0.5 include a fix for CVE-2023-43804: Urllib3 doesn't treat the 'Cookie' HTTP header special or provide any helpers for managing cookies over HTTP, that is the responsibility of the user. However, it is possible for a user to specify a 'Cookie' header and unknowingly leak information via HTTP redirects to a different origin if that user doesn't disable redirects explicitly.\r\nhttps://github.com/urllib3/urllib3/security/advisories/GHSA-v845-jxx5-vc9f", "cve": "CVE-2023-43804", "id": "pyup.io-61601", "more_info_path": "/vulnerabilities/CVE-2023-43804/61601", "specs": [ "<1.26.17", ">=2.0.0a1,<2.0.5" ], "v": "<1.26.17,>=2.0.0a1,<2.0.5" }, { "advisory": "Affected versions of urllib3 are vulnerable to an HTTP redirect handling vulnerability that fails to remove the HTTP request body when a POST changes to a GET via 301, 302, or 303 responses. This flaw can expose sensitive request data if the origin service is compromised and redirects to a malicious endpoint, though exploitability is low when no sensitive data is used. The vulnerability affects automatic redirect behavior. It is fixed in versions 1.26.18 and 2.0.7; update or disable redirects using redirects=False.\r\nThis vulnerability is specific to Python's urllib3 library.", "cve": "CVE-2023-45803", "id": "pyup.io-61893", "more_info_path": "/vulnerabilities/CVE-2023-45803/61893", "specs": [ "<1.26.18", ">=2.0.0a1,<2.0.7" ], "v": "<1.26.18,>=2.0.0a1,<2.0.7" }, { "advisory": "Urllib3 1.26.5 includes a fix for CVE-2021-33503: When provided with a URL containing many @ characters in the authority component, the authority regular expression exhibits catastrophic backtracking, causing a denial of service if a URL were passed as a parameter or redirected to via an HTTP redirect.\r\nhttps://github.com/advisories/GHSA-q2q7-5pp4-w6pg", "cve": "CVE-2021-33503", "id": "pyup.io-43975", "more_info_path": "/vulnerabilities/CVE-2021-33503/43975", "specs": [ "<1.26.5" ], "v": "<1.26.5" }, { "advisory": "urllib3 is a user-friendly HTTP client library for Python. Prior to 2.5.0, it is possible to disable redirects for all requests by instantiating a PoolManager and specifying retries in a way that disable redirects. By default, requests and botocore users are not affected. An application attempting to mitigate SSRF or open redirect vulnerabilities by disabling redirects at the PoolManager level will remain vulnerable. This issue has been patched in version 2.5.0.", "cve": "CVE-2025-50181", "id": "pyup.io-77744", "more_info_path": "/vulnerabilities/CVE-2025-50181/77744", "specs": [ "<2.5.0" ], "v": "<2.5.0" }, { "advisory": "Urllib3's ProxyManager ensures that the Proxy-Authorization header is correctly directed only to configured proxies. However, when HTTP requests bypass urllib3's proxy support, there's a risk of inadvertently setting the Proxy-Authorization header, which remains ineffective without a forwarding or tunneling proxy. Urllib3 does not recognize this header as carrying authentication data, failing to remove it during cross-origin redirects. While this scenario is uncommon and poses low risk to most users, urllib3 now proactively removes the Proxy-Authorization header during cross-origin redirects as a precautionary measure. Users are advised to utilize urllib3's proxy support or disable automatic redirects to handle the Proxy-Authorization header securely. Despite these precautions, urllib3 defaults to stripping the header to safeguard users who may inadvertently misconfigure requests.", "cve": "CVE-2024-37891", "id": "pyup.io-71608", "more_info_path": "/vulnerabilities/CVE-2024-37891/71608", "specs": [ "<=1.26.18", ">=2.0.0a1,<=2.2.1" ], "v": "<=1.26.18,>=2.0.0a1,<=2.2.1" }, { "advisory": "Urllib3 version 1.18.1 includes a fix for CVE-2016-9015: Versions 1.17 and 1.18 of the Python urllib3 library suffer from a vulnerability that can cause them, in certain configurations, to not correctly validate TLS certificates. This places users of the library with those configurations at risk of man-in-the-middle and information leakage attacks. This vulnerability affects users using versions 1.17 and 1.18 of the urllib3 library, who are using the optional PyOpenSSL support for TLS instead of the regular standard library TLS backend, and who are using OpenSSL 1.1.0 via PyOpenSSL. This is an extremely uncommon configuration, so the security impact of this vulnerability is low.\r\nhttps://www.openwall.com/lists/oss-security/2016/10/27/6", "cve": "CVE-2016-9015", "id": "pyup.io-35691", "more_info_path": "/vulnerabilities/CVE-2016-9015/35691", "specs": [ "==1.17", "==1.18" ], "v": "==1.17,==1.18" }, { "advisory": "Affected versions of urllib3 contain insecure default SSL/TLS settings, exposing users to Man-in-the-Middle (MITM) attacks. The inclusion of weak ciphers such as RC4 and MD5 in the default configuration allows attackers to decrypt traffic or perform downgrade attacks. This vulnerability impacts any SSL/TLS communication using the default cipher list. The patch mitigates this risk by updating the cipher list to include stronger, more secure ciphers like ECDHE and AES-GCM.", "cve": "PVE-2024-99834", "id": "pyup.io-65595", "more_info_path": "/vulnerabilities/PVE-2024-99834/65595", "specs": [ ">=0,<1.8" ], "v": ">=0,<1.8" }, { "advisory": "Affected versions of the urllib3 package are vulnerable to Denial of Service (DoS) due to improper handling of highly compressed HTTP response bodies during streaming decompression. The urllib3.HTTPResponse methods stream(), read(), read1(), read_chunked(), and readinto() may fully decompress a minimal but highly compressed payload based on the Content-Encoding header into an internal buffer instead of limiting the decompressed output to the requested chunk size, causing excessive CPU usage and massive memory allocation on the client side.", "cve": "CVE-2025-66471", "id": "pyup.io-82332", "more_info_path": "/vulnerabilities/CVE-2025-66471/82332", "specs": [ ">=1.0,<2.6.0" ], "v": ">=1.0,<2.6.0" }, { "advisory": "Affected versions of the urllib3 package are vulnerable to Denial of Service (DoS) due to redirect handling that drains connections by decompressing redirect response bodies without enforcing streaming read limits. The issue occurs when using urllib3\u2019s streaming mode (for example, preload_content=False) while allowing redirects, because urllib3.response.HTTPResponse.drain_conn() would call HTTPResponse.read() in a way that decoded/decompressed the entire redirect response body even before any streaming reads were performed, effectively bypassing decompression-bomb safeguards.", "cve": "CVE-2026-21441", "id": "pyup.io-84031", "more_info_path": "/vulnerabilities/CVE-2026-21441/84031", "specs": [ ">=1.22,<2.6.3" ], "v": ">=1.22,<2.6.3" }, { "advisory": "Affected versions of the urllib3 package are vulnerable to Denial of Service (DoS) due to allowing an unbounded number of content-encoding decompression steps for HTTP responses. The HTTPResponse content decoding pipeline in urllib3 follows the Content-Encoding header and applies each advertised compression algorithm in sequence without enforcing a maximum chain length or effective output size, so a malicious peer can send a response with a very long encoding chain that triggers excessive CPU use and massive memory allocation during decompression.", "cve": "CVE-2025-66418", "id": "pyup.io-82331", "more_info_path": "/vulnerabilities/CVE-2025-66418/82331", "specs": [ ">=1.24,<2.6.0" ], "v": ">=1.24,<2.6.0" }, { "advisory": "The _encode_invalid_chars function in util/url.py in the urllib3 library 1.25.2 through 1.25.7 for Python allows a denial of service (CPU consumption) because of an inefficient algorithm. The percent_encodings array contains all matches of percent encodings. It is not deduplicated. For a URL of length N, the size of percent_encodings may be up to O(N). The next step (normalize existing percent-encoded bytes) also takes up to O(N) for each step, so the total time is O(N^2). If percent_encodings were deduplicated, the time to compute _encode_invalid_chars would be O(kN), where k is at most 484 ((10+6*2)^2). See: CVE-2020-7212.", "cve": "CVE-2020-7212", "id": "pyup.io-27519", "more_info_path": "/vulnerabilities/CVE-2020-7212/27519", "specs": [ ">=1.25.2,<=1.25.7" ], "v": ">=1.25.2,<=1.25.7" }, { "advisory": "Urllib3 1.26.4 includes a fix for CVE-2021-28363: The urllib3 library 1.26.x before 1.26.4 for Python omits SSL certificate validation in some cases involving HTTPS to HTTPS proxies. The initial connection to the HTTPS proxy (if an SSLContext isn't given via proxy_config) doesn't verify the hostname of the certificate. This means certificates for different servers that still validate properly with the default urllib3 SSLContext will be silently accepted.", "cve": "CVE-2021-28363", "id": "pyup.io-40014", "more_info_path": "/vulnerabilities/CVE-2021-28363/40014", "specs": [ ">=1.26.0,<1.26.4" ], "v": ">=1.26.0,<1.26.4" }, { "advisory": "Urllib3 is a user-friendly HTTP client library for Python. Starting in version 2.2.0 and before 2.5.0, urllib3 does not control redirects in browsers and Node.js. urllib3 supports being used in a Pyodide runtime, utilizing the JavaScript Fetch API or falling back on XMLHttpRequest. This means Python libraries can be used to make HTTP requests from a browser or Node.js. Additionally, urllib3 provides a mechanism to control redirects, but the retries and redirect parameters are ignored with Pyodide; the runtime itself determines redirect behaviour. This issue has been patched in version 2.5.0.", "cve": "CVE-2025-50182", "id": "pyup.io-77745", "more_info_path": "/vulnerabilities/CVE-2025-50182/77745", "specs": [ ">=2.2.0,<2.5.0" ], "v": ">=2.2.0,<2.5.0" } ], "urllib3-future": [ { "advisory": "Affected versions of urllib3 are vulnerable to improper handling of HTTP redirect request bodies. Sensitive data in request bodies may be exposed if a compromised origin service redirects using 301, 302, or 303. The vulnerability affects automatic removal of request bodies when the method changes from POST to GET. Exploitability is low. Users should update to 1.26.18 or 2.0.7, or disable automatic redirects with redirects=False.", "cve": "CVE-2023-45803", "id": "pyup.io-61979", "more_info_path": "/vulnerabilities/CVE-2023-45803/61979", "specs": [ "<2.1.902" ], "v": "<2.1.902" }, { "advisory": "Affected versions of this package are vulnerable to Denial of Service (DoS) due to allowing an unbounded number of content-encoding decompression steps for HTTP responses. The HTTPResponse content decoding pipeline in urllib3 follows the Content-Encoding header and applies each advertised compression algorithm in sequence without enforcing a maximum chain length or effective output size, so a malicious peer can send a response with a very long encoding chain that triggers excessive CPU use and massive memory allocation during decompression.", "cve": "CVE-2025-66418", "id": "pyup.io-82755", "more_info_path": "/vulnerabilities/CVE-2025-66418/82755", "specs": [ "<2.15.900" ], "v": "<2.15.900" } ], "urlllib": [ { "advisory": "Urlllib is a malicious package. It injects obfuscated JS code that replaces crypto addresses in developer clipboards.", "cve": "PVE-2022-51761", "id": "pyup.io-51761", "more_info_path": "/vulnerabilities/PVE-2022-51761/51761", "specs": [ ">0" ], "v": ">0" } ], "usd-core": [ { "advisory": "Affected versions of the usd-core package are vulnerable to Use-After-Free due to missing validation of the primChildren list when parsing USD crate (.usdc) files. The Sdf_CrateDataImpl logic in pxr/usd/sdf/crateData.cpp accepted SdfChildrenKeys->PrimChildren entries without confirming that identifiers were valid, that corresponding child paths existed, or that names were not duplicated, which could lead to dangling references and unsafe memory access during later child traversal, causing erroneous behaviour.", "cve": "PVE-2025-80987", "id": "pyup.io-80987", "more_info_path": "/vulnerabilities/PVE-2025-80987/80987", "specs": [ "<25.11" ], "v": "<25.11" }, { "advisory": "Affected versions of the usd-core package are vulnerable to Use-After-Free due to unsynchronised destruction of `Sdf_PrimPathNode` objects in the `Sdf_PathNode` module that permits access to freed memory. The `pxr/usd/sdf/path.cpp` code path involving `Sdf_PrimPathNode::~Sdf_PrimPathNode` can be exercised concurrently, creating a race in which one thread frees a node while another continues to reference it, as evidenced by crashes observed across OpenUSD tools such as `sdfdump`, `usdtree`, `usdcat`, and `sdffilter`.", "cve": "PVE-2025-79463", "id": "pyup.io-79463", "more_info_path": "/vulnerabilities/PVE-2025-79463/79463", "specs": [ "<25.8" ], "v": "<25.8" } ], "uv": [ { "advisory": "Uv version 0.2.6 addresses a race condition in OnceMap::wait_blocking that could cause an inserted value to be missed, potentially leading to a deadlock.", "cve": "PVE-2024-71336", "id": "pyup.io-71336", "more_info_path": "/vulnerabilities/PVE-2024-71336/71336", "specs": [ "<0.2.6" ], "v": "<0.2.6" }, { "advisory": "Affected versions of the uv package are vulnerable to Improper Input Validation due to inadequate verification of ZIP central directory data and End-of-Central-Directory offsets in the streaming extractor. The vulnerable path is uv\u2019s asynchronous ZIP parser (rs-async-zip) used by the wheel installation modules (uv-extract and uv-install-wheel), which trusts local file headers, permits duplicate or missing central-directory entries, and interprets the EOCD offset in a way that causes divergent extraction behaviour across installers.", "cve": "CVE-2025-54368", "id": "pyup.io-79083", "more_info_path": "/vulnerabilities/CVE-2025-54368/79083", "specs": [ "<0.8.6" ], "v": "<0.8.6" }, { "advisory": "Affected versions of the uv package are vulnerable to Type Confusion due to inconsistent parsing of PAX header size overrides in TAR archives. The source-distribution unpacking path in uv, implemented via the astral-tokio-tar module, may ignore a PAX \u201csize\u201d override when the ustar header reports size 0, causing file data to be misinterpreted as additional TAR headers and producing a different extracted file set than other Python installers.", "cve": "PVE-2025-80507", "id": "pyup.io-80507", "more_info_path": "/vulnerabilities/PVE-2025-80507/80507", "specs": [ "<0.9.5" ], "v": "<0.9.5" }, { "advisory": "Affected versions of the uv package (<= 0.9.5) are vulnerable to Improper Input Validation due to inconsistent parsing of ZIP central directory comment fields and ambiguous filename handling. The ZIP archive parser in uv assumes central directory comments are absent and does not properly validate the filename fields in local headers and central directory entries (including names containing NUL bytes), which can lead uv to misinterpret comment bytes as control structures and to skip files that other Python installers extract, creating an interpretation conflict.", "cve": "PVE-2025-80986", "id": "pyup.io-80986", "more_info_path": "/vulnerabilities/PVE-2025-80986/80986", "specs": [ "<0.9.6" ], "v": "<0.9.6" } ], "uvicorn": [ { "advisory": "Uvicorn before 0.11.7 is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.", "cve": "CVE-2020-7695", "id": "pyup.io-38665", "more_info_path": "/vulnerabilities/CVE-2020-7695/38665", "specs": [ "<0.11.7" ], "v": "<0.11.7" }, { "advisory": "The request logger provided by Uvicorn prior to version 0.11.7 is vulnerable to ASNI escape sequence injection. Whenever any HTTP request is received, the default behaviour of uvicorn is to log its details to either the console or a log file. When attackers request crafted URLs with percent-encoded escape sequences, the logging component will log the URL after it's been processed with urllib.parse.unquote, therefore converting any percent-encoded characters into their single-character equivalent, which can have special meaning in terminal emulators. By requesting URLs with crafted paths, attackers can: * Pollute uvicorn's access logs, therefore jeopardising the integrity of such files. * Use ANSI sequence codes to attempt to interact with the terminal emulator that's displaying the logs (either in real time or from a file). See: CVE-2020-7694.", "cve": "CVE-2020-7694", "id": "pyup.io-38664", "more_info_path": "/vulnerabilities/CVE-2020-7694/38664", "specs": [ "<0.11.7" ], "v": "<0.11.7" }, { "advisory": "Uvicorn 0.12.3 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/encode/uvicorn/pull/848", "cve": "PVE-2023-59576", "id": "pyup.io-59576", "more_info_path": "/vulnerabilities/PVE-2023-59576/59576", "specs": [ "<0.12.3" ], "v": "<0.12.3" } ], "uwsgi": [ { "advisory": "Uwsgi 1.9.9 reduces security problems caused by wrong configurations by making the router_basicauth plugin return \"break\" instead of \"next\" if authorization fails.", "cve": "PVE-2021-34418", "id": "pyup.io-34418", "more_info_path": "/vulnerabilities/PVE-2021-34418/34418", "specs": [ "<1.9.9" ], "v": "<1.9.9" }, { "advisory": "Uwsgi 2.0.10 avoids lowering security standards with gcc 4.9.\r\nhttps://github.com/unbit/uwsgi/pull/759", "cve": "PVE-2021-34422", "id": "pyup.io-34422", "more_info_path": "/vulnerabilities/PVE-2021-34422/34422", "specs": [ "<2.0.10" ], "v": "<2.0.10" }, { "advisory": "Affected versions of Uwsgi are vulnerable to HTTP Response splitting. An attacker that can inject malicious response headers into backend applications to cause an HTTP desynchronization attack.", "cve": "CVE-2023-27522", "id": "pyup.io-71321", "more_info_path": "/vulnerabilities/CVE-2023-27522/71321", "specs": [ "<2.0.26" ], "v": "<2.0.26" }, { "advisory": "uWSGI before 2.0.17 mishandles a DOCUMENT_ROOT check during use of the --php-docroot option, allowing directory traversal.", "cve": "CVE-2018-7490", "id": "pyup.io-54028", "more_info_path": "/vulnerabilities/CVE-2018-7490/54028", "specs": [ ">=0,<2.0.17" ], "v": ">=0,<2.0.17" } ], "v3io-frames": [ { "advisory": "The gRPC dependency in V3io-frames has been upgraded from version 1.20.0 to version 1.56.3 in the 0.10.11 update, in response to CVE-2023-44487.", "cve": "CVE-2023-44487", "id": "pyup.io-64445", "more_info_path": "/vulnerabilities/CVE-2023-44487/64445", "specs": [ "<0.10.11" ], "v": "<0.10.11" }, { "advisory": "V3io-frames 0.11.3 updates its GO dependency 'golang.org/x/net' to v0.7.0' to include a security fix.", "cve": "CVE-2022-41723", "id": "pyup.io-53396", "more_info_path": "/vulnerabilities/CVE-2022-41723/53396", "specs": [ "<0.11.3" ], "v": "<0.11.3" } ], "v3iofs": [ { "advisory": "V3iofs 0.1.18 upgrades its PyArrow dependency to versions greater than 14.0.1 but less than 15, in response to the security vulnerability CVE-2019-12408.", "cve": "CVE-2019-12408", "id": "pyup.io-64287", "more_info_path": "/vulnerabilities/CVE-2019-12408/64287", "specs": [ "<0.1.18" ], "v": "<0.1.18" } ], "validators": [ { "advisory": "Validators 0.21.0 includes a fix for CVE-2023-45813: Inefficient Regular Expression Complexity in validate_link.\r\nhttps://github.com/DedSecInside/TorBot/security/advisories/GHSA-72qw-p7hh-m3ff\r\nhttps://github.com/python-validators/validators/pull/243", "cve": "CVE-2023-45813", "id": "pyup.io-61924", "more_info_path": "/vulnerabilities/CVE-2023-45813/61924", "specs": [ ">=0.11.0,<0.21.0" ], "v": ">=0.11.0,<0.21.0" }, { "advisory": "The validators package 0.12.2 through 0.12.5 for Python enters an infinite loop when validators.domain is called with a crafted domain string. This is fixed in 0.12.6. See: CVE-2019-19588.", "cve": "CVE-2019-19588", "id": "pyup.io-37769", "more_info_path": "/vulnerabilities/CVE-2019-19588/37769", "specs": [ ">=0.12.2,<=0.12.5" ], "v": ">=0.12.2,<=0.12.5" } ], "vanna": [ { "advisory": "Vanna uses a prompt function to present the user with visualized results, it is possible to alter the prompt using prompt injection and run arbitrary Python code instead of the intended visualization code. Specifically - allowing external input to the library\u2019s \u201cask\u201d method with \"visualize\" set to True (default behavior) leads to remote code execution.", "cve": "CVE-2024-5565", "id": "pyup.io-71786", "more_info_path": "/vulnerabilities/CVE-2024-5565/71786", "specs": [ "<=0.6.2" ], "v": "<=0.6.2" }, { "advisory": "In affected versions, the `vanna.ask` function is vulnerable to remote code execution due to prompt injection. The root cause is the lack of a sandbox when executing LLM-generated code, allowing an attacker to manipulate the code executed by the `exec` function in `src/vanna/base/base.py`. This vulnerability can be exploited by an attacker to achieve remote code execution on the app backend server, potentially gaining full control of the server.", "cve": "CVE-2024-5826", "id": "pyup.io-72090", "more_info_path": "/vulnerabilities/CVE-2024-5826/72090", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "vanna-ai/vanna version affected versions are vulnerable to SQL injection in some file-critical functions such as `pg_read_file()`. This vulnerability allows unauthenticated remote users to read arbitrary local files on the victim server, including sensitive files like `/etc/passwd`, by exploiting the exposed SQL queries via a Python Flask API.", "cve": "CVE-2024-5753", "id": "pyup.io-72081", "more_info_path": "/vulnerabilities/CVE-2024-5753/72081", "specs": [ ">=0" ], "v": ">=0" } ], "vantage6": [ { "advisory": "vantage6 is privacy preserving federated learning infrastructure. The endpoint /api/collaboration/{id}/task is used to collect all tasks from a certain collaboration. To get such tasks, a user should have permission to view the collaboration and to view the tasks in it. However, prior to version 4.0.0, it is only checked if the user has permission to view the collaboration. Version 4.0.0 contains a patch. There are no known workarounds.", "cve": "CVE-2023-41882", "id": "pyup.io-65239", "more_info_path": "/vulnerabilities/CVE-2023-41882/65239", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is privacy preserving federated learning infrastructure. Prior to version 4.0.0, malicious users may try to get access to resources they are not allowed to see, by creating resources with integers as names. One example where this is a risk, is when users define which users are allowed to run algorithms on their node. This may be defined by username or user id. Now, for example, if user id 13 is allowed to run tasks, and an attacker creates a username with username '13', they would be wrongly allowed to run an algorithm. There may also be other places in the code where such a mixup of resource ID or name leads to issues. Version 4.0.0 contains a patch for this issue. The best solution is to check when resources are created or modified, that the resource name always starts with a character.", "cve": "CVE-2023-28635", "id": "pyup.io-62909", "more_info_path": "/vulnerabilities/CVE-2023-28635/62909", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "Vantage6 4.0.0 includes a fix for CVE-2023-23930: Versions prior to 4.0.0 use pickle, which has known security issue, as a default serialization module but that has known security issues. All users of vantage6 that post tasks with the default serialization are affected. Users may specify JSON serialization as a workaround.\r\nhttps://github.com/vantage6/vantage6/security/advisories/GHSA-5m22-cfq9-86x6", "cve": "CVE-2023-23930", "id": "pyup.io-61778", "more_info_path": "/vulnerabilities/CVE-2023-23930/61778", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is privacy preserving federated learning infrastructure. When a collaboration is deleted, the linked resources (such as tasks from that collaboration) should be deleted. This is partly to manage data properly, but also to prevent a potential (but unlikely) side-effect that affects versions prior to 4.0.0, where if a collaboration with id=10 is deleted, and subsequently a new collaboration is created with id=10, the authenticated users in that collaboration could potentially see results of the deleted collaboration in some cases. Version 4.0.0 contains a patch for this issue. There are no known workarounds.", "cve": "CVE-2023-41881", "id": "pyup.io-65244", "more_info_path": "/vulnerabilities/CVE-2023-41881/65244", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is a framework to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). In affected versions a node does not check if an image is allowed to run if a `parent_id` is set. A malicious party that breaches the server may modify it to set a fake `parent_id` and send a task of a non-whitelisted algorithm. The node will then execute it because the `parent_id` that is set prevents checks from being run. This impacts all servers that are breached by an expert user. This vulnerability has been patched in version 4.1.2. All users are advised to upgrade. There are no known workarounds for this vulnerability.", "cve": "CVE-2023-47631", "id": "pyup.io-65236", "more_info_path": "/vulnerabilities/CVE-2023-47631/65236", "specs": [ "<4.1.2" ], "v": "<4.1.2" }, { "advisory": "Affected versions of this package are vulnerable to Brute Force attacks due to missing rate limiting on the password change functionality. The patch() method in the password change endpoint fails to implement any brute-force protection mechanisms, leading to unlimited password-guessing attempts by authenticated attackers. An attacker with access to an authenticated session can repeatedly call the change password route to systematically guess the current password, as the endpoint provides immediate feedback on whether the submitted password is correct or incorrect without any throttling or attempt limitations.", "cve": "CVE-2025-43863", "id": "pyup.io-77727", "more_info_path": "/vulnerabilities/CVE-2025-43863/77727", "specs": [ "<4.11.0" ], "v": "<4.11.0" }, { "advisory": "The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). There are no checks on whether the input is encrypted if a task is created in an encrypted collaboration. Therefore, a user may accidentally create a task with sensitive input data that will then be stored unencrypted in a database. Users should ensure they set the encryption setting correctly. This vulnerability is patched in 4.2.0.", "cve": "CVE-2024-22193", "id": "pyup.io-66723", "more_info_path": "/vulnerabilities/CVE-2024-22193/66723", "specs": [ "<4.2.0" ], "v": "<4.2.0" }, { "advisory": "The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). Nodes and servers get a ssh config by default that permits root login with password authentication. In a proper deployment, the SSH service is not exposed so there is no risk, but not all deployments are ideal. The default should therefore be less permissive. The vulnerability can be mitigated by removing the ssh part from the docker file and rebuilding the docker image. Version 4.2.0 patches the vulnerability.", "cve": "CVE-2024-21653", "id": "pyup.io-66727", "more_info_path": "/vulnerabilities/CVE-2024-21653/66727", "specs": [ "<4.2.0" ], "v": "<4.2.0" }, { "advisory": "The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). It is possible to find out usernames from the response time of login requests. This could aid attackers in credential attacks. Version 4.2.0 patches this vulnerability.", "cve": "CVE-2024-21671", "id": "pyup.io-66725", "more_info_path": "/vulnerabilities/CVE-2024-21671/66725", "specs": [ "<4.2.0" ], "v": "<4.2.0" }, { "advisory": "The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). Prior to 4.2.0, authenticated users could inject code into algorithm environment variables, resulting in remote code execution. This vulnerability is patched in 4.2.0.", "cve": "CVE-2024-21649", "id": "pyup.io-66729", "more_info_path": "/vulnerabilities/CVE-2024-21649/66729", "specs": [ "<4.2.0" ], "v": "<4.2.0" }, { "advisory": "Affected versions of the vantage6 package are vulnerable to Information Disclosure due to timing attacks and differential responses in authentication endpoints. The `/recover/lost` and `/2fa/lost` API routes exhibit observable differences in response times and return distinct error messages when processing requests for existing versus non-existing usernames, specifically returning \"Failed to login\" for valid usernames.", "cve": "CVE-2024-24770", "id": "pyup.io-71945", "more_info_path": "/vulnerabilities/CVE-2024-24770/71945", "specs": [ "<4.3.0" ], "v": "<4.3.0" }, { "advisory": "vantage6 is an open-source infrastructure for privacy preserving analysis. Collaboration administrators can add extra organizations to their collaboration that can extend their influence. For example, organizations that they include can then create new users for which they know the passwords, and use that to read task results of other collaborations that that organization is involved in. This is only relatively trusted users - with access to manage a collaboration - are able to do this, which reduces the impact.", "cve": "CVE-2024-32969", "id": "pyup.io-71944", "more_info_path": "/vulnerabilities/CVE-2024-32969/71944", "specs": [ "<4.5.0rc3" ], "v": "<4.5.0rc3" }, { "advisory": "vantage6 is an open source framework built to enable, manage and deploy privacy enhancing technologies like Federated Learning and Multi-Party Computation. The vantage6 server has no restrictions on CORS settings. It should be possible for people to set the allowed origins of the server. The impact is limited because v6 does not use session cookies.", "cve": "CVE-2024-23823", "id": "pyup.io-71946", "more_info_path": "/vulnerabilities/CVE-2024-23823/71946", "specs": [ "<=4.2.2" ], "v": "<=4.2.2" }, { "advisory": "### Impact\nWe are incorporating the password policies listed in https://github.com/vantage6/vantage6/issues/59. One measure is that we don't let the user know in case of wrong username/password combination if the username actually exists, to prevent that bots can guess usernames. However, if a wrong password is entered a number of times, the user account is blocked temporarily. This way you could still find out which usernames exist.\n\n### Patches\nUpdate to 3.8.0+\n\n### Workarounds\nNo\n\n### References\nhttps://github.com/vantage6/vantage6/issues/59\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [vantage6@iknl.nl](mailto:vantage6@iknl.nl)\n", "cve": "CVE-2022-39228", "id": "pyup.io-54659", "more_info_path": "/vulnerabilities/CVE-2022-39228/54659", "specs": [ ">=0,<3.8.0" ], "v": ">=0,<3.8.0" }, { "advisory": "### Impact\nAssigning existing users to a different organization is currently possible. It may lead to unintended access: if a user from organization A is accidentally assigned to organization B, they will retain their permissions and therefore might be able to access stuff they should not be allowed to access.\n\n### Patches\nUpdate to 3.8.0\n\n### Workarounds\nNone\n\n### References\nNone\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [vantage6@iknl.nl](mailto:vantage6@iknl.nl)\n", "cve": "CVE-2023-22738", "id": "pyup.io-54660", "more_info_path": "/vulnerabilities/CVE-2023-22738/54660", "specs": [ ">=0,<3.8.0" ], "v": ">=0,<3.8.0" }, { "advisory": "From issue: \n\nProblem description\nCurrently, the refresh token is valid indefinitely. This is bad security practice.\n\nDesired solution\nThe refresh token should get a validity of 24-48 hours.\n\nAdditional context\n\nWhen implementing this, also check that the refresh token returns a new refresh token\nWhen implementing this, also adapt the UI so that it logs out if refresh token is no longer valid.\nWhen implementing this, ensure that nodes refresh their token periodically so that they do not have to be restarted manually.\n\n\n### Impact\n### Patches\nNone available \n\n### Workarounds\nNone available\n\n", "cve": "CVE-2023-23929", "id": "pyup.io-54661", "more_info_path": "/vulnerabilities/CVE-2023-23929/54661", "specs": [ ">=0,<3.8.0" ], "v": ">=0,<3.8.0" } ], "vantage6-client": [ { "advisory": "vantage6 is privacy preserving federated learning infrastructure. The endpoint /api/collaboration/{id}/task is used to collect all tasks from a certain collaboration. To get such tasks, a user should have permission to view the collaboration and to view the tasks in it. However, prior to version 4.0.0, it is only checked if the user has permission to view the collaboration. Version 4.0.0 contains a patch. There are no known workarounds.", "cve": "CVE-2023-41882", "id": "pyup.io-65240", "more_info_path": "/vulnerabilities/CVE-2023-41882/65240", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is privacy preserving federated learning infrastructure. Prior to version 4.0.0, malicious users may try to get access to resources they are not allowed to see, by creating resources with integers as names. One example where this is a risk, is when users define which users are allowed to run algorithms on their node. This may be defined by username or user id. Now, for example, if user id 13 is allowed to run tasks, and an attacker creates a username with username '13', they would be wrongly allowed to run an algorithm. There may also be other places in the code where such a mixup of resource ID or name leads to issues. Version 4.0.0 contains a patch for this issue. The best solution is to check when resources are created or modified, that the resource name always starts with a character.", "cve": "CVE-2023-28635", "id": "pyup.io-62911", "more_info_path": "/vulnerabilities/CVE-2023-28635/62911", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is privacy preserving federated learning infrastructure. When a collaboration is deleted, the linked resources (such as tasks from that collaboration) should be deleted. This is partly to manage data properly, but also to prevent a potential (but unlikely) side-effect that affects versions prior to 4.0.0, where if a collaboration with id=10 is deleted, and subsequently a new collaboration is created with id=10, the authenticated users in that collaboration could potentially see results of the deleted collaboration in some cases. Version 4.0.0 contains a patch for this issue. There are no known workarounds.", "cve": "CVE-2023-41881", "id": "pyup.io-65245", "more_info_path": "/vulnerabilities/CVE-2023-41881/65245", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is a framework to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). In affected versions a node does not check if an image is allowed to run if a `parent_id` is set. A malicious party that breaches the server may modify it to set a fake `parent_id` and send a task of a non-whitelisted algorithm. The node will then execute it because the `parent_id` that is set prevents checks from being run. This impacts all servers that are breached by an expert user. This vulnerability has been patched in version 4.1.2. All users are advised to upgrade. There are no known workarounds for this vulnerability.", "cve": "CVE-2023-47631", "id": "pyup.io-65237", "more_info_path": "/vulnerabilities/CVE-2023-47631/65237", "specs": [ "<4.1.2" ], "v": "<4.1.2" } ], "vantage6-common": [ { "advisory": "vantage6 is privacy preserving federated learning infrastructure. The endpoint /api/collaboration/{id}/task is used to collect all tasks from a certain collaboration. To get such tasks, a user should have permission to view the collaboration and to view the tasks in it. However, prior to version 4.0.0, it is only checked if the user has permission to view the collaboration. Version 4.0.0 contains a patch. There are no known workarounds.", "cve": "CVE-2023-41882", "id": "pyup.io-65241", "more_info_path": "/vulnerabilities/CVE-2023-41882/65241", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is privacy preserving federated learning infrastructure. When a collaboration is deleted, the linked resources (such as tasks from that collaboration) should be deleted. This is partly to manage data properly, but also to prevent a potential (but unlikely) side-effect that affects versions prior to 4.0.0, where if a collaboration with id=10 is deleted, and subsequently a new collaboration is created with id=10, the authenticated users in that collaboration could potentially see results of the deleted collaboration in some cases. Version 4.0.0 contains a patch for this issue. There are no known workarounds.", "cve": "CVE-2023-41881", "id": "pyup.io-65246", "more_info_path": "/vulnerabilities/CVE-2023-41881/65246", "specs": [ "<4.0.0" ], "v": "<4.0.0" } ], "vantage6-node": [ { "advisory": "vantage6 is privacy preserving federated learning infrastructure. The endpoint /api/collaboration/{id}/task is used to collect all tasks from a certain collaboration. To get such tasks, a user should have permission to view the collaboration and to view the tasks in it. However, prior to version 4.0.0, it is only checked if the user has permission to view the collaboration. Version 4.0.0 contains a patch. There are no known workarounds.", "cve": "CVE-2023-41882", "id": "pyup.io-65242", "more_info_path": "/vulnerabilities/CVE-2023-41882/65242", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is privacy preserving federated learning infrastructure. Prior to version 4.0.0, malicious users may try to get access to resources they are not allowed to see, by creating resources with integers as names. One example where this is a risk, is when users define which users are allowed to run algorithms on their node. This may be defined by username or user id. Now, for example, if user id 13 is allowed to run tasks, and an attacker creates a username with username '13', they would be wrongly allowed to run an algorithm. There may also be other places in the code where such a mixup of resource ID or name leads to issues. Version 4.0.0 contains a patch for this issue. The best solution is to check when resources are created or modified, that the resource name always starts with a character.", "cve": "CVE-2023-28635", "id": "pyup.io-62910", "more_info_path": "/vulnerabilities/CVE-2023-28635/62910", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is privacy preserving federated learning infrastructure. When a collaboration is deleted, the linked resources (such as tasks from that collaboration) should be deleted. This is partly to manage data properly, but also to prevent a potential (but unlikely) side-effect that affects versions prior to 4.0.0, where if a collaboration with id=10 is deleted, and subsequently a new collaboration is created with id=10, the authenticated users in that collaboration could potentially see results of the deleted collaboration in some cases. Version 4.0.0 contains a patch for this issue. There are no known workarounds.", "cve": "CVE-2023-41881", "id": "pyup.io-65247", "more_info_path": "/vulnerabilities/CVE-2023-41881/65247", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is a framework to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). In affected versions a node does not check if an image is allowed to run if a `parent_id` is set. A malicious party that breaches the server may modify it to set a fake `parent_id` and send a task of a non-whitelisted algorithm. The node will then execute it because the `parent_id` that is set prevents checks from being run. This impacts all servers that are breached by an expert user. This vulnerability has been patched in version 4.1.2. All users are advised to upgrade. There are no known workarounds for this vulnerability.", "cve": "CVE-2023-47631", "id": "pyup.io-65238", "more_info_path": "/vulnerabilities/CVE-2023-47631/65238", "specs": [ "<4.1.2" ], "v": "<4.1.2" } ], "vantage6-server": [ { "advisory": "vantage6 is privacy preserving federated learning infrastructure. When a collaboration is deleted, the linked resources (such as tasks from that collaboration) should be deleted. This is partly to manage data properly, but also to prevent a potential (but unlikely) side-effect that affects versions prior to 4.0.0, where if a collaboration with id=10 is deleted, and subsequently a new collaboration is created with id=10, the authenticated users in that collaboration could potentially see results of the deleted collaboration in some cases. Version 4.0.0 contains a patch for this issue. There are no known workarounds.", "cve": "CVE-2023-41881", "id": "pyup.io-65248", "more_info_path": "/vulnerabilities/CVE-2023-41881/65248", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is privacy preserving federated learning infrastructure. The endpoint /api/collaboration/{id}/task is used to collect all tasks from a certain collaboration. To get such tasks, a user should have permission to view the collaboration and to view the tasks in it. However, prior to version 4.0.0, it is only checked if the user has permission to view the collaboration. Version 4.0.0 contains a patch. There are no known workarounds.", "cve": "CVE-2023-41882", "id": "pyup.io-65243", "more_info_path": "/vulnerabilities/CVE-2023-41882/65243", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is privacy preserving federated learning infrastructure. Prior to version 4.0.0, malicious users may try to get access to resources they are not allowed to see, by creating resources with integers as names. One example where this is a risk, is when users define which users are allowed to run algorithms on their node. This may be defined by username or user id. Now, for example, if user id 13 is allowed to run tasks, and an attacker creates a username with username '13', they would be wrongly allowed to run an algorithm. There may also be other places in the code where such a mixup of resource ID or name leads to issues. Version 4.0.0 contains a patch for this issue. The best solution is to check when resources are created or modified, that the resource name always starts with a character.", "cve": "CVE-2023-28635", "id": "pyup.io-62912", "more_info_path": "/vulnerabilities/CVE-2023-28635/62912", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "vantage6 is a framework to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). In affected versions a node does not check if an image is allowed to run if a `parent_id` is set. A malicious party that breaches the server may modify it to set a fake `parent_id` and send a task of a non-whitelisted algorithm. The node will then execute it because the `parent_id` that is set prevents checks from being run. This impacts all servers that are breached by an expert user. This vulnerability has been patched in version 4.1.2. All users are advised to upgrade. There are no known workarounds for this vulnerability.", "cve": "CVE-2023-47631", "id": "pyup.io-65235", "more_info_path": "/vulnerabilities/CVE-2023-47631/65235", "specs": [ "<4.1.2" ], "v": "<4.1.2" }, { "advisory": "Affected versions of this package are vulnerable to JWT Token Forgery due to the use of cryptographically weak UUID1 for auto-generating JWT secret keys. The JWT secret key generation mechanism fails to use cryptographically secure randomness, leading to predictable secret keys that can be exploited by attackers to forge valid JWT tokens. UUID1 values are partially predictable as they incorporate timestamp and MAC address information, making them unsuitable for cryptographic purposes. This vulnerability allows attackers to potentially predict or brute-force the JWT secret key, enabling them to create arbitrary valid tokens and bypass authentication mechanisms. The fix involves replacing UUID1 with UUID4 for generating API keys and JWT secrets, as UUID4 uses cryptographically secure pseudo-random number generation, making the generated secrets unpredictable and suitable for security-critical applications.", "cve": "CVE-2025-43866", "id": "pyup.io-77728", "more_info_path": "/vulnerabilities/CVE-2025-43866/77728", "specs": [ "<4.11.0" ], "v": "<4.11.0" }, { "advisory": "The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). Nodes and servers get a ssh config by default that permits root login with password authentication. In a proper deployment, the SSH service is not exposed so there is no risk, but not all deployments are ideal. The default should therefore be less permissive. The vulnerability can be mitigated by removing the ssh part from the docker file and rebuilding the docker image. Version 4.2.0 patches the vulnerability.", "cve": "CVE-2024-21653", "id": "pyup.io-66728", "more_info_path": "/vulnerabilities/CVE-2024-21653/66728", "specs": [ "<4.2.0" ], "v": "<4.2.0" }, { "advisory": "The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). There are no checks on whether the input is encrypted if a task is created in an encrypted collaboration. Therefore, a user may accidentally create a task with sensitive input data that will then be stored unencrypted in a database. Users should ensure they set the encryption setting correctly. This vulnerability is patched in 4.2.0.", "cve": "CVE-2024-22193", "id": "pyup.io-66724", "more_info_path": "/vulnerabilities/CVE-2024-22193/66724", "specs": [ "<4.2.0" ], "v": "<4.2.0" }, { "advisory": "The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). Prior to 4.2.0, authenticated users could inject code into algorithm environment variables, resulting in remote code execution. This vulnerability is patched in 4.2.0.", "cve": "CVE-2024-21649", "id": "pyup.io-66730", "more_info_path": "/vulnerabilities/CVE-2024-21649/66730", "specs": [ "<4.2.0" ], "v": "<4.2.0" }, { "advisory": "The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). It is possible to find out usernames from the response time of login requests. This could aid attackers in credential attacks. Version 4.2.0 patches this vulnerability.", "cve": "CVE-2024-21671", "id": "pyup.io-66726", "more_info_path": "/vulnerabilities/CVE-2024-21671/66726", "specs": [ "<4.2.0" ], "v": "<4.2.0" } ], "vault-cli": [ { "advisory": "Vault-cli 3.0.0 includes a fix for CVE-2021-43837: In versions before 3.0.0 vault-cli features the ability for rendering templated values. When a secret starts with the prefix '!template!', vault-cli interprets the rest of the contents of the secret as a Jinja2 template. Jinja2 is a powerful templating engine and is not designed to safely render arbitrary templates. An attacker controlling a jinja2 template rendered on a machine can trigger arbitrary code, making this a Remote Code Execution (RCE) risk. If the content of the vault can be completely trusted, then this is not a problem. Otherwise, if your threat model includes cases where an attacker can manipulate a secret value read from the vault using vault-cli, then this vulnerability may impact you. In 3.0.0, the code related to interpreting vault templated secrets has been removed entirely. Users are advised to upgrade as soon as possible. For users unable to upgrade a workaround does exist. Using the environment variable 'VAULT_CLI_RENDER=false' or the flag '--no-render' (placed between 'vault-cli' and the subcommand, e.g. 'vault-cli --no-render get-all') or adding 'render: false' to the vault-cli configuration yaml file disables rendering and removes the vulnerability. Using the python library, you can use: 'vault_cli.get_client(render=False)' when creating your client to get a client that will not render templated secrets and thus operates securely.\r\nhttps://github.com/peopledoc/vault-cli/security/advisories/GHSA-q34h-97wf-8r8j", "cve": "CVE-2021-43837", "id": "pyup.io-43454", "more_info_path": "/vulnerabilities/CVE-2021-43837/43454", "specs": [ ">=0.7.0,<3.0.0" ], "v": ">=0.7.0,<3.0.0" } ], "vcert": [ { "advisory": "Vcert 0.16.0 updates its dependency 'cryptography' to v40.0.2 to include a security fix.", "cve": "CVE-2023-23931", "id": "pyup.io-58904", "more_info_path": "/vulnerabilities/CVE-2023-23931/58904", "specs": [ "<0.16.0" ], "v": "<0.16.0" } ], "vcspull": [ { "advisory": "Vcspull 1.11.1 updates its dependency 'libvcs' to v0.11.1 to fix a command injection vulnerability.", "cve": "CVE-2022-21187", "id": "pyup.io-45849", "more_info_path": "/vulnerabilities/CVE-2022-21187/45849", "specs": [ "<1.11.1" ], "v": "<1.11.1" } ], "vector2dggs": [ { "advisory": "Affected versions of the vector2dggs package are vulnerable to SQL injection due to constructing SQL statements by directly interpolating untrusted identifiers into query strings. In vector2dggs/common.py, the PostGIS ingestion path in index() builds queries like SELECT ... FROM {layer} (and similarly includes id_field/geom_col) and passes them to gpd.read_postgis, so crafted values can alter the intended SQL. \r\nhttps://github.com/manaakiwhenua/vector2dggs/commit/3559c9a5cc202d2dea49154e8dd0919faffd09f2", "cve": "PVE-2026-84980", "id": "pyup.io-84980", "more_info_path": "/vulnerabilities/PVE-2026-84980/84980", "specs": [ "<0.11.1" ], "v": "<0.11.1" } ], "velesdb": [ { "advisory": "Affected versions of the velesdb-core package are vulnerable to denial of service (memory exhaustion/OOM) due to missing validation of snapshot entry_count before allocating memory. The load_snapshot snapshot parser in crates/velesdb-core/src/storage/log_payload.rs trusts an attacker-controlled entry_count and can attempt allocations proportional to that value, and the remediation adds entry_count validation before allocation (delivered in fix commit 61c52a36156ed5388dd38cb3079c2159f6bd2466).", "cve": "PVE-2026-83823", "id": "pyup.io-83823", "more_info_path": "/vulnerabilities/PVE-2026-83823/83823", "specs": [ "<0.8.10" ], "v": "<0.8.10" } ], "vellum-ai": [ { "advisory": "Affected versions of the vellum-python-sdks package are potentially vulnerable to improper handling of generated files in nested workflows. The issue arises from the previous implementation's failure to include generated_files in the WorkflowContext when initiating nested workflows.", "cve": "PVE-2025-76494", "id": "pyup.io-76494", "more_info_path": "/vulnerabilities/PVE-2025-76494/76494", "specs": [ "<0.14.33" ], "v": "<0.14.33" } ], "venafi-vcert-gitlab-integration": [ { "advisory": "Venafi-vcert-gitlab-integration 2.1.0 updates its dependency 'VCert' to include a fix for log4j vulnerability.", "cve": "CVE-2021-44228", "id": "pyup.io-52975", "more_info_path": "/vulnerabilities/CVE-2021-44228/52975", "specs": [ "<2.1.0" ], "v": "<2.1.0" } ], "vendi": [ { "advisory": "Vendi 0.1.2 updates its dependency, wandb, to version 0.15.8 or higher to address known security issues that were present in older versions of wandb.\r\nhttps://github.com/vendi-ai/declarai/pull/53/commits/3c0cd3d240b69d665a45fee02c060ce3b4ff99e3", "cve": "PVE-2024-63279", "id": "pyup.io-63279", "more_info_path": "/vulnerabilities/PVE-2024-63279/63279", "specs": [ "<0.1.2" ], "v": "<0.1.2" } ], "verbs": [ { "advisory": "Verbs 0.4.1 has updated its h2 library from version 0.3.25 to 0.3.26 to address a security concern related to Denial of Service (DoS) vulnerabilities.", "cve": "PVE-2024-67588", "id": "pyup.io-67588", "more_info_path": "/vulnerabilities/PVE-2024-67588/67588", "specs": [ "<0.4.1" ], "v": "<0.4.1" } ], "verifone": [ { "advisory": "Verifone 0.1.8 updates its dependecy 'pyyaml' to v4.2b1 to include a security fix.", "cve": "CVE-2017-18342", "id": "pyup.io-36774", "more_info_path": "/vulnerabilities/CVE-2017-18342/36774", "specs": [ "<0.1.8" ], "v": "<0.1.8" } ], "veritensor": [ { "advisory": "Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) due to unrestricted network calls during remote scanning. The vulnerability arises because the scanner allows network requests to any domain, which can be exploited to perform unauthorized actions or access sensitive information on internal networks. An attacker can exploit this vulnerability by tricking the scanner into making requests to unintended domains, potentially leading to data exfiltration or unauthorized access to internal services.", "cve": "PVE-2026-84346", "id": "pyup.io-84346", "more_info_path": "/vulnerabilities/PVE-2026-84346/84346", "specs": [ "<1.2.0" ], "v": "<1.2.0" }, { "advisory": "Affected versions of this package are vulnerable to Denial of Service (DoS) due to insufficient memory usage restrictions when parsing malicious archives. The vulnerability exists because the scanner does not adequately limit memory consumption, which can lead to Out-Of-Memory (OOM) crashes when processing zip files. An attacker can exploit this vulnerability by crafting a malicious archive designed to consume excessive memory, potentially causing the system to crash or become unresponsive.", "cve": "PVE-2026-84231", "id": "pyup.io-84231", "more_info_path": "/vulnerabilities/PVE-2026-84231/84231", "specs": [ "<1.2.0" ], "v": "<1.2.0" } ], "vermin": [ { "advisory": "Vermin 0.10.1 fixes the security advisory by upgrading bleach from 3.1.0 to 3.1.1.", "cve": "PVE-2021-38033", "id": "pyup.io-38033", "more_info_path": "/vulnerabilities/PVE-2021-38033/38033", "specs": [ "<0.10.1" ], "v": "<0.10.1" }, { "advisory": "Vermin 0.10.2 upgrades bleach from 3.1.1 to 3.1.2 and 3.1.2 to 3.1.4 to fix a security advisory.", "cve": "PVE-2021-38692", "id": "pyup.io-38692", "more_info_path": "/vulnerabilities/PVE-2021-38692/38692", "specs": [ "<0.10.2" ], "v": "<0.10.2" }, { "advisory": "Vermin 0.4.11 updates its dependency PyYAML to v4.2b1 to include a security fix.", "cve": "CVE-2017-18342", "id": "pyup.io-36942", "more_info_path": "/vulnerabilities/CVE-2017-18342/36942", "specs": [ "<0.4.11" ], "v": "<0.4.11" }, { "advisory": "Vermin 0.4.8 updates 'requests' to v2.20.0 to include a security fix.", "cve": "CVE-2018-18074", "id": "pyup.io-36603", "more_info_path": "/vulnerabilities/CVE-2018-18074/36603", "specs": [ "<0.4.8" ], "v": "<0.4.8" }, { "advisory": "Vermin 0.4.9 updates its dependency \"urllib3\" to include a security fix.", "cve": "CVE-2019-11236", "id": "pyup.io-36725", "more_info_path": "/vulnerabilities/CVE-2019-11236/36725", "specs": [ "<0.4.9" ], "v": "<0.4.9" }, { "advisory": "Vermin 0.5.0 updates its dependency 'urllib3' to v1.24.2 to include a security fix.", "cve": "CVE-2019-11324", "id": "pyup.io-37094", "more_info_path": "/vulnerabilities/CVE-2019-11324/37094", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Vermin 1.1.1 updates its dependency 'PyYAML' to version '5.4' to include a security fix.\r\nhttps://github.com/netromdk/vermin/commit/91ec9b504afc4b3a0ab99829db66fe1dbf9b63f5\r\nhttps://github.com/advisories/GHSA-8q59-q68h-6hv4", "cve": "CVE-2020-14343", "id": "pyup.io-59080", "more_info_path": "/vulnerabilities/CVE-2020-14343/59080", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Vermin 1.1.1 updates its dependency 'pygments' to version '2.7.4' to include a security fix.\r\nhttps://github.com/netromdk/vermin/commit/8fd8769a5630befdea82a3882377f6e92b012e22\r\nhttps://github.com/advisories/GHSA-pq64-v7f5-gqh8", "cve": "CVE-2021-27291", "id": "pyup.io-59088", "more_info_path": "/vulnerabilities/CVE-2021-27291/59088", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Vermin 1.1.1 updates its dependency 'bleach' to version '3.3.0' to include a security fix.\r\nhttps://github.com/netromdk/vermin/commit/aa66cf0701ae60a9bf41c254e7e7612827d152e3\r\nhttps://github.com/advisories/GHSA-vv2x-vrpj-qqpq", "cve": "CVE-2021-23980", "id": "pyup.io-59089", "more_info_path": "/vulnerabilities/CVE-2021-23980/59089", "specs": [ "<1.1.1" ], "v": "<1.1.1" }, { "advisory": "Vermin 1.2.1 updates its dependency 'urllib3' to version '1.26.5' to include a security fix.\r\nhttps://github.com/netromdk/vermin/commit/6c0185de735d3c347ee4f659df77b0d33084717a\r\nhttps://github.com/advisories/GHSA-q2q7-5pp4-w6pg", "cve": "CVE-2021-33503", "id": "pyup.io-59079", "more_info_path": "/vulnerabilities/CVE-2021-33503/59079", "specs": [ "<1.2.1" ], "v": "<1.2.1" }, { "advisory": "Vermin 1.5.2 updates its dependency 'certifi' to version '2022.12.07' to include a security fix.\r\nhttps://github.com/netromdk/vermin/pull/135/files\r\nhttps://github.com/advisories/GHSA-43fp-rhv2-5gv8", "cve": "CVE-2022-23491", "id": "pyup.io-59078", "more_info_path": "/vulnerabilities/CVE-2022-23491/59078", "specs": [ "<1.5.2" ], "v": "<1.5.2" }, { "advisory": "Vermin 1.5.2 updates its dependency 'GitPython' to version '3.1.30' to include a security fix.\r\nhttps://github.com/netromdk/vermin/pull/157", "cve": "CVE-2022-24439", "id": "pyup.io-59087", "more_info_path": "/vulnerabilities/CVE-2022-24439/59087", "specs": [ "<1.5.2" ], "v": "<1.5.2" } ], "vfb-connect": [ { "advisory": "VFB-Connect has updated its Pillow library dependencies in response to CVE-2023-4863.", "cve": "CVE-2023-4863", "id": "pyup.io-73049", "more_info_path": "/vulnerabilities/CVE-2023-4863/73049", "specs": [ "<2.2.10" ], "v": "<2.2.10" } ], "vhcalc": [ { "advisory": "Vhcalc 0.2.4 updates its dependency 'pillow' to v9.1.1 to include a security fix.", "cve": "CVE-2022-30595", "id": "pyup.io-49139", "more_info_path": "/vulnerabilities/CVE-2022-30595/49139", "specs": [ "<0.2.4" ], "v": "<0.2.4" }, { "advisory": "Vhcalc 0.2.5 updates Dockerfile to \"python:3.9-slim-buster\" to include security fixes.", "cve": "CVE-2022-0563", "id": "pyup.io-49304", "more_info_path": "/vulnerabilities/CVE-2022-0563/49304", "specs": [ "<0.2.5" ], "v": "<0.2.5" }, { "advisory": "Vhcalc 0.2.5 updates Dockerfile to \"python:3.9-slim-buster\" to include security fixes.", "cve": "CVE-2022-1664", "id": "pyup.io-49138", "more_info_path": "/vulnerabilities/CVE-2022-1664/49138", "specs": [ "<0.2.5" ], "v": "<0.2.5" }, { "advisory": "Vhcalc 0.2.5 updates Dockerfile to \"python:3.9-slim-buster\" to include security fixes.", "cve": "CVE-2022-1587", "id": "pyup.io-49302", "more_info_path": "/vulnerabilities/CVE-2022-1587/49302", "specs": [ "<0.2.5" ], "v": "<0.2.5" }, { "advisory": "Vhcalc 0.2.5 updates Dockerfile to \"python:3.9-slim-buster\" to include security fixes.", "cve": "CVE-2022-1292", "id": "pyup.io-49301", "more_info_path": "/vulnerabilities/CVE-2022-1292/49301", "specs": [ "<0.2.5" ], "v": "<0.2.5" }, { "advisory": "Vhcalc 0.2.5 updates Dockerfile to \"python:3.9-slim-buster\" to include security fixes.", "cve": "CVE-2022-1586", "id": "pyup.io-49303", "more_info_path": "/vulnerabilities/CVE-2022-1586/49303", "specs": [ "<0.2.5" ], "v": "<0.2.5" } ], "videomass": [ { "advisory": "Videomass is affected by a Improper Privilege Management vulnerability in Preset Manager. This behavior could have been harmful if a user logged in with administrator privileges ran the program during the automatic update task to the new version of local presets.\r\nhttps://github.com/jeanslack/Videomass/pull/258/commits/918539f5e6966c42691d7aaf7f6a057d9dc27b5b", "cve": "PVE-2024-64508", "id": "pyup.io-64508", "more_info_path": "/vulnerabilities/PVE-2024-64508/64508", "specs": [ "<5.0.4" ], "v": "<5.0.4" } ], "vineyard": [ { "advisory": "Vineyard 0.1.2 avoids DoS that could occur if being attacked by an invalid client.\r\nhttps://github.com/v6d-io/v6d/pull/64/commits/31a7083d4f6dc42896e1acf4bf0ab69eb6c4bf8c", "cve": "PVE-2021-39346", "id": "pyup.io-39346", "more_info_path": "/vulnerabilities/PVE-2021-39346/39346", "specs": [ "<0.1.2" ], "v": "<0.1.2" }, { "advisory": "Versions of Vineyard, an in-memory immutable data manager, are susceptible to a Denial of Service (DoS) attack due to a vulnerability within the `SocketConnection::doReadBody()` function in `src/server/async/socket_server.cc`. This issue exposes systems to potential service disruptions.", "cve": "PVE-2024-99833", "id": "pyup.io-65596", "more_info_path": "/vulnerabilities/PVE-2024-99833/65596", "specs": [ ">=0,<0.1.2" ], "v": ">=0,<0.1.2" } ], "vips-hash": [ { "advisory": "Vips-hash 0.2.0 updates its dependency 'pycryptodome' requirement to '>=3.6.6,<4' to include a security fix.", "cve": "CVE-2018-15560", "id": "pyup.io-37354", "more_info_path": "/vulnerabilities/CVE-2018-15560/37354", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "virl2-client": [ { "advisory": "Virl2-client 2.2.1post2 updates its dependency 'urllib3' to v1.26.7 to include a security fix.", "cve": "CVE-2021-33503", "id": "pyup.io-46417", "more_info_path": "/vulnerabilities/CVE-2021-33503/46417", "specs": [ "<2.2.1post2" ], "v": "<2.2.1post2" } ], "virtme-ng": [ { "advisory": "vulnerability fix in Virtme-ng 1.33 | SSH port exposure vulnerability fix and security-related improvements\r\n- Fixed Versions: v1.33\r\n - Affected Versions: <1.33", "cve": "PVE-2025-75633", "id": "pyup.io-75633", "more_info_path": "/vulnerabilities/PVE-2025-75633/75633", "specs": [ "<1.33" ], "v": "<1.33" } ], "virtool-core": [ { "advisory": "Virtool-core 0.4.0 updates its dependency 'aiohttp' to v3.8.1 to include a security fix.", "cve": "PVE-2021-42692", "id": "pyup.io-43003", "more_info_path": "/vulnerabilities/PVE-2021-42692/43003", "specs": [ "<0.4.0" ], "v": "<0.4.0" }, { "advisory": "Virtool-core 2.39.1 includes a fix for CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.", "cve": "CVE-2007-4559", "id": "pyup.io-52059", "more_info_path": "/vulnerabilities/CVE-2007-4559/52059", "specs": [ "<2.39.1" ], "v": "<2.39.1" } ], "virtualbmc": [ { "advisory": "Virtualbmc 3.0.0 includes a fix for CVE-2022-44020: An issue was discovered in OpenStack Sushy-Tools through 0.21.0 and VirtualBMC through 2.2.2. Changing the boot device configuration with these packages removes password protection from the managed libvirt XML domain. \r\nNOTE: this only affects an \"unsupported, production-like configuration.\"", "cve": "CVE-2022-44020", "id": "pyup.io-51632", "more_info_path": "/vulnerabilities/CVE-2022-44020/51632", "specs": [ "<=2.2.2" ], "v": "<=2.2.2" } ], "virtualenv": [ { "advisory": "virtualenv.py in virtualenv before 1.5 allows local users to overwrite arbitrary files via a symlink attack on a certain file in /tmp/.", "cve": "CVE-2011-4617", "id": "pyup.io-26172", "more_info_path": "/vulnerabilities/CVE-2011-4617/26172", "specs": [ "<1.5" ], "v": "<1.5" }, { "advisory": "Virtualenv version 20.21.0 addresses a race condition in `virtualenv.cli_run` where a `FileNotFoundError` could occur for a JSON file in `pypa/virtualenv/py_info/1`. This error happens if the underlying interpreter is updated, causing the JSON file to be deleted and rewritten.", "cve": "PVE-2024-68477", "id": "pyup.io-68477", "more_info_path": "/vulnerabilities/PVE-2024-68477/68477", "specs": [ "<20.21.0" ], "v": "<20.21.0" }, { "advisory": "Affected versions of the virtualenv package are vulnerable to Command Injection due to improper quoting of template string placeholders in activation scripts. The vulnerability exists in the ViaTemplateActivator class, where magic template strings like __VIRTUAL_ENV__ are replaced in shell activation scripts without proper escaping or quoting, allowing shell metacharacters to be interpreted as commands during string substitution. An attacker can exploit this vulnerability by creating a virtual environment with a specially crafted directory name containing shell commands (such as \"';uname -a;':\"), which will be executed when the activation script is sourced, resulting in arbitrary command execution with the privileges of the user activating the virtual environment.", "cve": "CVE-2024-53899", "id": "pyup.io-78825", "more_info_path": "/vulnerabilities/CVE-2024-53899/78825", "specs": [ "<20.26.6" ], "v": "<20.26.6" }, { "advisory": "Affected versions of the virtualenv package (up to and including 20.36.1) are vulnerable to Race Condition (TOCTOU) attacks due to non-atomic directory creation that is performed using check-then-act filesystem logic. The issue occurs in virtualenv\u2019s directory creation operations for its app_data path and related lock file handling, where a directory existence check can be raced so a symlink is inserted before the subsequent creation or access step, redirecting operations to an unintended location.", "cve": "CVE-2026-22702", "id": "pyup.io-84416", "more_info_path": "/vulnerabilities/CVE-2026-22702/84416", "specs": [ "<20.36.1" ], "v": "<20.36.1" } ], "virtualnv": [ { "advisory": "Virtualnv is a typosquatting package. It installs malware in your system that leaks your data.\r\nhttps://github.com/rsc-dev/pypi_malware", "cve": "PVE-2022-45438", "id": "pyup.io-45438", "more_info_path": "/vulnerabilities/PVE-2022-45438/45438", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "virustotal-python": [ { "advisory": "Virustotal-python 0.0.3 updates its dependency 'urllib3' to v1.24.2 to include a security fix.", "cve": "CVE-2019-11236", "id": "pyup.io-37078", "more_info_path": "/vulnerabilities/CVE-2019-11236/37078", "specs": [ "<0.0.3" ], "v": "<0.0.3" }, { "advisory": "Virustotal-python 0.0.8 updates its dependency 'bleach' to v3.1.1 to include a security fix.", "cve": "CVE-2020-6802", "id": "pyup.io-37960", "more_info_path": "/vulnerabilities/CVE-2020-6802/37960", "specs": [ "<0.0.8" ], "v": "<0.0.8" }, { "advisory": "Virustotal-python 0.0.9 updates its dependency 'bleach' to v3.1.4 to include security fixes.", "cve": "CVE-2020-6817", "id": "pyup.io-38227", "more_info_path": "/vulnerabilities/CVE-2020-6817/38227", "specs": [ "<0.0.9" ], "v": "<0.0.9" }, { "advisory": "Virustotal-python 0.0.9 updates its dependency 'bleach' to v3.1.4 to include security fixes.", "cve": "CVE-2020-6816", "id": "pyup.io-45021", "more_info_path": "/vulnerabilities/CVE-2020-6816/45021", "specs": [ "<0.0.9" ], "v": "<0.0.9" }, { "advisory": "Virustotal-python 0.1.2 updates its dependency 'urllib3' to v1.26.4 to include a security fix.", "cve": "CVE-2021-28363", "id": "pyup.io-40663", "more_info_path": "/vulnerabilities/CVE-2021-28363/40663", "specs": [ "<0.1.2" ], "v": "<0.1.2" }, { "advisory": "Virustotal-python 0.1.3 updates its dependency 'urllib3' to v1.26.5 to include a security fix.", "cve": "CVE-2021-33503", "id": "pyup.io-48032", "more_info_path": "/vulnerabilities/CVE-2021-33503/48032", "specs": [ "<0.1.3" ], "v": "<0.1.3" } ], "viscid": [ { "advisory": "Viscid version 1.0.0 includes a security patch for the function 'plot_opts_to_kwargs' in 'viscid/plot/vpyplot.py'. It uses the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load().\r\nhttps://github.com/viscid-hub/Viscid/commit/892052a5c12aa7aa865de277945c55defcc7e9f7", "cve": "CVE-2017-18342", "id": "pyup.io-41400", "more_info_path": "/vulnerabilities/CVE-2017-18342/41400", "specs": [ "<1.0.0" ], "v": "<1.0.0" } ], "visidata": [ { "advisory": "For security reasons, `.py` loader moved out of VisiData core version 2.-2 and into snippets.", "cve": "PVE-2021-38871", "id": "pyup.io-38871", "more_info_path": "/vulnerabilities/PVE-2021-38871/38871", "specs": [ "<2.-2" ], "v": "<2.-2" } ], "visyn-core": [ { "advisory": "Visyn-core 6.0.0 includes a fix for a CSV injection vulnerability.\r\nhttps://github.com/datavisyn/visyn_core/pull/108", "cve": "PVE-2023-62405", "id": "pyup.io-62405", "more_info_path": "/vulnerabilities/PVE-2023-62405/62405", "specs": [ "<6.0.0" ], "v": "<6.0.0" } ], "viur-core": [ { "advisory": "Viur-core 3.4.0rc1 includes an authorization bypass vulnerability: Logins via Google or other custom login handlers were able to authenticate users disabled by the system.\r\nhttps://github.com/viur-framework/viur-core/pull/710", "cve": "PVE-2023-55057", "id": "pyup.io-55057", "more_info_path": "/vulnerabilities/PVE-2023-55057/55057", "specs": [ "<3.4.0rc1" ], "v": "<3.4.0rc1" }, { "advisory": "Viur-core 3.4.0.rc2 includes a security fix: Custom login handlers where able to authenticate users which were disabled by the system.\r\nhttps://github.com/viur-framework/viur-core/pull/710", "cve": "PVE-2023-55214", "id": "pyup.io-55214", "more_info_path": "/vulnerabilities/PVE-2023-55214/55214", "specs": [ "<3.4.0rc2" ], "v": "<3.4.0rc2" }, { "advisory": "Viur-core 3.6.0 eliminates the default setting P.html = True from its prototypes to enhance security. Now, by default, modules are not accessible through any render except by the admin. This change ensures data is not inadvertently rendered through the default view.html template in viur-base, unless explicitly permitted, safeguarding against unauthorized data exposure.\r\nhttps://github.com/viur-framework/viur-core/pull/1037", "cve": "PVE-2024-66861", "id": "pyup.io-66861", "more_info_path": "/vulnerabilities/PVE-2024-66861/66861", "specs": [ "<3.6.0" ], "v": "<3.6.0" } ], "vizable": [ { "advisory": "Vizable version 0.12.0 addresses a security issue by updating the `idna` package from version 3.6 to 3.7.", "cve": "PVE-2024-70374", "id": "pyup.io-70374", "more_info_path": "/vulnerabilities/PVE-2024-70374/70374", "specs": [ "<0.12.0" ], "v": "<0.12.0" } ], "vizro": [ { "advisory": "Vizro 0.1.4 updates 'pydantic' requirement to '>=1.10.13, <2' to include a security fix.", "cve": "PVE-2023-61416", "id": "pyup.io-61685", "more_info_path": "/vulnerabilities/PVE-2023-61416/61685", "specs": [ "<0.1.4" ], "v": "<0.1.4" } ], "vllm": [ { "advisory": "Affected versions of the Mura package are vulnerable to Cross-site Scripting (XSS) due to improper sanitization of user-supplied input in the moduleid parameter within the admin interface. The vulnerable component fails to escape HTML special characters before rendering the parameter value in the management panel, allowing arbitrary JavaScript execution in the victim\u2019s browser.", "cve": "CVE-2025-59425", "id": "pyup.io-80182", "more_info_path": "/vulnerabilities/CVE-2025-59425/80182", "specs": [ "<0.11.0" ], "v": "<0.11.0" }, { "advisory": "Affected versions of the vllm package are vulnerable to Remote Code Execution due to improper enforcement of the trust_remote_code safety boundary when dynamically resolving model configuration classes from auto_map entries. The Nemotron_Nano_VL_Config.__init__ constructor uses get_class_from_dynamic_module(*vision_config[\"auto_map\"][\"AutoConfig\"].split(\"--\")[::-1]) to fetch and instantiate a class referenced by vision_config[\"auto_map\"] inside vllm.transformers_utils.config.get_config, causing Python code to be loaded and executed from a remote Hugging Face repository even when trust_remote_code=False and without validating whether the auto_map target belongs to the same repository.", "cve": "CVE-2025-66448", "id": "pyup.io-82198", "more_info_path": "/vulnerabilities/CVE-2025-66448/82198", "specs": [ "<0.11.1" ], "v": "<0.11.1" }, { "advisory": "Affected versions of the vllm package are vulnerable to Server-Side Request Forgery (SSRF) due to inconsistent URL parsing that allows the allowed-host restriction to be bypassed. The MediaConnector.load_from_url and MediaConnector.load_from_url_async methods validate hostnames using urllib.parse.urlparse (via _assert_url_in_allowed_media_domains), but fetch content using requests (backed by urllib3.parse_url), and their different handling of backslashes (\\) lets a crafted URL slip past the hostname check.", "cve": "CVE-2026-24779", "id": "pyup.io-85255", "more_info_path": "/vulnerabilities/CVE-2026-24779/85255", "specs": [ "<0.14.1" ], "v": "<0.14.1" }, { "advisory": "Vllm 0.2.1 includes a security fix: Vulnerable memory modification to GPU shared memory.\r\nhttps://github.com/vllm-project/vllm/pull/1241", "cve": "PVE-2023-61866", "id": "pyup.io-61866", "more_info_path": "/vulnerabilities/PVE-2023-61866/61866", "specs": [ "<0.2.1" ], "v": "<0.2.1" }, { "advisory": "vllm-project vllm version 0.6.0 contains a vulnerability in the AsyncEngineRPCServer() RPC server entrypoints. The core functionality run_server_loop() calls the function _make_handler_coro(), which directly uses cloudpickle.loads() on received messages without any sanitization. This can result in remote code execution by deserializing malicious pickle data.", "cve": "CVE-2024-9053", "id": "pyup.io-76192", "more_info_path": "/vulnerabilities/CVE-2024-9053/76192", "specs": [ "<0.6.0" ], "v": "<0.6.0" }, { "advisory": "The vllm/modelexecutor/weightutils.py implements hfmodelweightsiterator to load the model checkpoint, which is downloaded from huggingface. It use torch.load function and weightsonly parameter is default value False. There is a security warning on https://pytorch.org/docs/stable/generated/torch.load.html, when torch.load load a malicious pickle data it will execute arbitrary code during unpickling.", "cve": "CVE-2025-24357", "id": "pyup.io-76350", "more_info_path": "/vulnerabilities/CVE-2025-24357/76350", "specs": [ "<0.7.0" ], "v": "<0.7.0" }, { "advisory": "Maliciously constructed prompts can lead to hash collisions, resulting in prefix cache reuse, which can interfere with subsequent responses and cause unintended behavior.", "cve": "CVE-2025-25183", "id": "pyup.io-76340", "more_info_path": "/vulnerabilities/CVE-2025-25183/76340", "specs": [ "<0.7.2" ], "v": "<0.7.2" }, { "advisory": "Affected versions of the vLLM package are vulnerable to Denial of Service through unbounded filesystem cache growth in the Outlines guided decoding backend. The outlines_logits_processors.py module fails to limit the size of the grammar compilation cache, allowing unlimited cache entries to be created. \r\n\r\nA remote attacker can exploit this vulnerability by sending numerous requests with unique schemas through the OpenAI-compatible API server, causing each request to add a new entry to the cache, resulting in filesystem exhaustion and service unavailability. Additionally, the cache was enabled by default without administrative controls, making all V0 engine deployments vulnerable.\r\n\r\nThe vulnerability was fixed by disabling the Outlines cache by default and introducing the VLLM_V0_USE_OUTLINES_CACHE environment variable for administrators who wish to explicitly enable it. The V1 engine is not affected by this vulnerability.", "cve": "CVE-2025-29770", "id": "pyup.io-76302", "more_info_path": "/vulnerabilities/CVE-2025-29770/76302", "specs": [ "<0.8.0" ], "v": "<0.8.0" }, { "advisory": "vLLM is an inference and serving engine for large language models (LLMs). Prior to version 0.9.0, when a new prompt is processed, if the PageAttention mechanism finds a matching prefix chunk, the prefill process speeds up, which is reflected in the TTFT (Time to First Token). These timing differences caused by matching chunks are significant enough to be recognized and exploited. This issue has been patched in version 0.9.0.", "cve": "CVE-2025-46570", "id": "pyup.io-77700", "more_info_path": "/vulnerabilities/CVE-2025-46570/77700", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Affected versions of the vllm-project vLLM package are vulnerable to Remote Code Execution (RCE). The MessageQueue.dequeue() API function fails to sanitize user input before deserialization, using pickle.loads to parse received socket data, directly leading to arbitrary code execution. An unauthenticated attacker can exploit this vulnerability by sending a specially crafted malicious pickle payload to the MessageQueue service, resulting in the execution of arbitrary code with the same privileges as the vLLM application process.", "cve": "CVE-2024-11041", "id": "pyup.io-76277", "more_info_path": "/vulnerabilities/CVE-2024-11041/76277", "specs": [ "<=0.6.2" ], "v": "<=0.6.2" }, { "advisory": "Affected versions of the vLLM package are vulnerable to Deserialization of Untrusted Data due to unsafe pickle deserialization in the distributed training API. The vllm.distributed.GroupCoordinator.recv_object() function uses pickle.loads() to deserialize received object bytes without any input validation or sanitization, allowing arbitrary Python object deserialization.", "cve": "CVE-2024-9052", "id": "pyup.io-78833", "more_info_path": "/vulnerabilities/CVE-2024-9052/78833", "specs": [ "<=0.8.1" ], "v": "<=0.8.1" }, { "advisory": "Improper handling of the 'best_of' parameter in the ilab model serve component's vllm JSON web API can lead to a Denial of Service (DoS) vulnerability. When attackers set this parameter to a large value during LLM-based sentence or chat completion requests, the API fails to manage timeouts or resource exhaustion effectively. This oversight allows malicious actors to consume excessive system resources, rendering the API unresponsive and blocking legitimate users from accessing the service. The vulnerability stems from the API's attempt to return the best completion from several options without proper safeguards against resource-intensive requests.", "cve": "CVE-2024-8939", "id": "pyup.io-73285", "more_info_path": "/vulnerabilities/CVE-2024-8939/73285", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Affected versions of the vLLM package are vulnerable to Denial of Service (DoS) attacks due to insufficient input validation on HTTP headers. The HTTP server implementation fails to enforce size limits on request headers, allowing attackers to send headers with extremely large values, such as the `X-Forwarded-For` header containing billions of characters.", "cve": "CVE-2025-48956", "id": "pyup.io-79028", "more_info_path": "/vulnerabilities/CVE-2025-48956/79028", "specs": [ ">=0.1.0,<0.10.1.1" ], "v": ">=0.1.0,<0.10.1.1" }, { "advisory": "Affected versions of the vLLM package are vulnerable to Remote Code Execution (RCE) due to unsafe deserialization in the Qwen3 Coder tool call parser. The parser's parameter conversion process contains a code path that invokes Python's `eval()` function to handle unknown data types when processing tool call parameters, creating an arbitrary code execution vector.", "cve": "CVE-2025-9141", "id": "pyup.io-79029", "more_info_path": "/vulnerabilities/CVE-2025-9141/79029", "specs": [ ">=0.10.0,<0.10.1.1" ], "v": ">=0.10.0,<0.10.1.1" }, { "advisory": "Affected versions of the vllm package are vulnerable to Remote Code Execution due to loading Hugging Face auto_map dynamic modules without gating on trust_remote_code. During model resolution, vllm/model_executor/models/registry.py iterates auto_map entries from the model configuration and calls try_get_class_from_dynamic_module in vllm/transformers_utils/dynamic_module.py, which delegates to Transformers\u2019 get_class_from_dynamic_module and executes the referenced module\u2019s Python code. An attacker who can influence the model repository or path (for example, by supplying a malicious local directory or a remote Hugging Face model repo that an operator loads) can have attacker-controlled code run during vLLM server startup, leading to arbitrary code execution on the host.", "cve": "CVE-2026-22807", "id": "pyup.io-84895", "more_info_path": "/vulnerabilities/CVE-2026-22807/84895", "specs": [ ">=0.10.1,<0.14.0" ], "v": ">=0.10.1,<0.14.0" }, { "advisory": "Affected versions of the vllm package are vulnerable to Denial of Service (DoS) due to missing sparse tensor validation when the prompt embeds feature is enabled. vllm does not enforce sparse tensor invariant checks (for example, ensuring indices are non-negative and within bounds) on user-influenced embedding tensors, because PyTorch sparse tensor validation can be disabled by default for performance and vllm previously relied on that default behaviour.", "cve": "PVE-2026-84338", "id": "pyup.io-84338", "more_info_path": "/vulnerabilities/PVE-2026-84338/84338", "specs": [ ">=0.10.2,<0.11.1" ], "v": ">=0.10.2,<0.11.1" }, { "advisory": "Affected versions of the vllm package are vulnerable to Deserialization of Untrusted Data due to missing validation of user-supplied prompt embedding tensors before they are deserialized and converted to dense form. In the Completions API endpoint, the _load_and_validate_embed function in vllm/entrypoints/renderer.py uses torch.load on base64-encoded, user-controlled tensors with weights_only=True and then calls tensor.to_dense() without enabling sparse tensor integrity checks introduced in PyTorch 2.8.0, allowing malicious sparse tensors to trigger an out-of-bounds memory write in the underlying deserialization logic.", "cve": "CVE-2025-62164", "id": "pyup.io-81792", "more_info_path": "/vulnerabilities/CVE-2025-62164/81792", "specs": [ ">=0.10.2,<0.11.1" ], "v": ">=0.10.2,<0.11.1" }, { "advisory": "A flaw was found in the vLLM library. A completions API request with an empty prompt will crash the vLLM API server, resulting in a denial of service.", "cve": "CVE-2024-8768", "id": "pyup.io-73284", "more_info_path": "/vulnerabilities/CVE-2024-8768/73284", "specs": [ ">=0.4.3,<0.5.5" ], "v": ">=0.4.3,<0.5.5" }, { "advisory": "Affected versions of the vLLM package are vulnerable to Server-Side Request Forgery (SSRF) due to unrestricted fetching of user-supplied media URLs in the MediaConnector. The MediaConnector.load_from_url and MediaConnector.load_from_url_async methods accept http/https (and file) URLs provided by clients without host validation or blocking of private/loopback ranges, allowing requests to internal network resources.", "cve": "CVE-2025-6242", "id": "pyup.io-80237", "more_info_path": "/vulnerabilities/CVE-2025-6242/80237", "specs": [ ">=0.5.0,<0.11.0" ], "v": ">=0.5.0,<0.11.0" }, { "advisory": "Affected versions of the vllm package are vulnerable to Denial of Service (DoS) due to acceptance of user-controlled Jinja chat templates via the chat_template and chat_template_kwargs parameters without resource limits in the OpenAI-Compatible Server endpoints. In vllm/entrypoints/openai/serving_engine.py the server merges user input into _chat_template_kwargs using dict.update and forwards it to apply_hf_chat_template, enabling a crafted template\u2014supplied directly through chat_template or by overriding that key inside chat_template_kwargs\u2014to consume excessive CPU and memory.", "cve": "CVE-2025-61620", "id": "pyup.io-80235", "more_info_path": "/vulnerabilities/CVE-2025-61620/80235", "specs": [ ">=0.5.1,<0.11.0" ], "v": ">=0.5.1,<0.11.0" }, { "advisory": "vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Versions starting from 0.5.2 and prior to 0.8.5 are vulnerable to denial of service and data exposure via ZeroMQ on multi-node vLLM deployment. In a multi-node vLLM deployment, vLLM uses ZeroMQ for some multi-node communication purposes. The primary vLLM host opens an XPUB ZeroMQ socket and binds it to ALL interfaces. While the socket is always opened for a multi-node deployment, it is only used when doing tensor parallelism across multiple hosts. Any client with network access to this host can connect to this XPUB socket unless its port is blocked by a firewall. Once connected, these arbitrary clients will receive all of the same data broadcasted to all of the secondary vLLM hosts. This data is internal vLLM state information that is not useful to an attacker. By potentially connecting to this socket many times and not reading data published to them, an attacker can also cause a denial of service by slowing down or potentially blocking the publisher. This issue has been patched in version 0.8.5.", "cve": "CVE-2025-30202", "id": "pyup.io-77148", "more_info_path": "/vulnerabilities/CVE-2025-30202/77148", "specs": [ ">=0.5.2,<0.8.5" ], "v": ">=0.5.2,<0.8.5" }, { "advisory": "Affected versions of the vLLM package are vulnerable to Remote Code Execution through unsafe deserialization in multi-node deployments using the V0 engine. The shm_broadcast.py module fails to validate data received on ZeroMQ SUB sockets before deserializing it with pickle, allowing arbitrary code execution. \r\n\r\nA remote attacker can exploit this vulnerability by sending malicious pickle payloads to secondary vLLM hosts through the ZeroMQ communication channel, resulting in complete system compromise. Additionally, attackers could leverage network attacks such as ARP cache poisoning to redirect traffic and deliver malicious payloads without requiring access to the primary host.\r\n\r\nThe vulnerability affects only the V0 engine in tensor parallelism deployments across multiple hosts. Since V0 has been off by default since v0.8.0 and the fix would be invasive, the maintainers have decided not to patch this issue. Users should ensure their deployments are on secure networks and migrate to the V1 engine, which is not affected by this vulnerability.", "cve": "CVE-2025-30165", "id": "pyup.io-77142", "more_info_path": "/vulnerabilities/CVE-2025-30165/77142", "specs": [ ">=0.5.2,<=0.8.5.post1" ], "v": ">=0.5.2,<=0.8.5.post1" }, { "advisory": "Affected versions of the vllm package are vulnerable to Denial of Service (DoS) due to insufficient validation of multimodal embedding tensor shapes in the input processing pipeline. The MultiModalDataParser component validates only the tensor ndim and not the full shape, allowing malformed multimodal embedding inputs to reach get_input_embeddings or be scattered into inputs_embeds, which triggers out-of-bounds access and crashes the vLLM engine process. An attacker with network access and low-privileged access to a multimodal vLLM endpoint can repeatedly submit tensors with a correct number of dimensions but incorrect hidden size, causing the engine to terminate and making all models served by that instance unavailable until it is restarted, resulting in Denial of Service.", "cve": "CVE-2025-62372", "id": "pyup.io-81793", "more_info_path": "/vulnerabilities/CVE-2025-62372/81793", "specs": [ ">=0.5.5,<0.11.1" ], "v": ">=0.5.5,<0.11.1" }, { "advisory": "Affected versions of the vllm package are vulnerable to Denial of Service (DoS) due to unvalidated chat_template_kwargs parameters that allow users to trigger expensive tokenization during chat template processing. In vllm.entrypoints.openai.serving_engine._preprocess_chat, the chat_template_kwargs dict is unpacked directly into keyword arguments for chat_utils.apply_hf_chat_template without validating keys or values, so calls made through the /v1/chat/completions and /tokenize endpoints in serving_chat.py and serving_tokenization.py can override the tokenize flag and cause tokenization to run synchronously on large inputs.", "cve": "CVE-2025-62426", "id": "pyup.io-81796", "more_info_path": "/vulnerabilities/CVE-2025-62426/81796", "specs": [ ">=0.5.5,<0.11.1" ], "v": ">=0.5.5,<0.11.1" }, { "advisory": "A review identified several regular expressions in the vLLM codebase that are susceptible to Regular Expression Denial of Service (ReDoS) attacks. These patterns, if fed with crafted or malicious input, may cause severe performance degradation due to catastrophic backtracking.", "cve": "PVE-2025-77701", "id": "pyup.io-77701", "more_info_path": "/vulnerabilities/PVE-2025-77701/77701", "specs": [ ">=0.6.3,<0.9.0" ], "v": ">=0.6.3,<0.9.0" }, { "advisory": "Affected versions of the vllm package are vulnerable to Denial of Service (DoS) due to ambiguous 1x1 pixel image dimensions being misinterpreted during Idefics3 vision preprocessing. In vllm/model_executor/models/idefics3.py, _process_image_input can treat an HWC image shaped (1, 1, 3) as CHW, miscalculate num_patches, and then fail at image_features.split(num_patches.tolist()) with an unhandled RuntimeError when the split sizes do not match the tensor\u2019s dimension.", "cve": "CVE-2026-22773", "id": "pyup.io-84414", "more_info_path": "/vulnerabilities/CVE-2026-22773/84414", "specs": [ ">=0.6.4,<0.12.0" ], "v": ">=0.6.4,<0.12.0" }, { "advisory": "vLLM, an inference and serving engine for large language models (LLMs), has an issue in versions 0.6.5 through 0.8.4 that ONLY impacts environments using the `PyNcclPipe` KV cache transfer integration with the V0 engine. No other configurations are affected. vLLM supports the use of the `PyNcclPipe` class to establish a peer-to-peer communication domain for data transmission between distributed nodes. The GPU-side KV-Cache transmission is implemented through the `PyNcclCommunicator` class, while CPU-side control message passing is handled via the `send_obj` and `recv_obj` methods on the CPU side.\u200b The intention was that this interface should only be exposed to a private network using the IP address specified by the `--kv-ip` CLI parameter. The vLLM documentation covers how this must be limited to a secured network. The default and intentional behavior from PyTorch is that the `TCPStore` interface listens on ALL interfaces, regardless of what IP address is provided. The IP address given was only used as a client-side address to use. vLLM was fixed to use a workaround to force the `TCPStore` instance to bind its socket to a specified private interface. As of version 0.8.5, vLLM limits the `TCPStore` socket to the private interface as configured.", "cve": "CVE-2025-47277", "id": "pyup.io-77711", "more_info_path": "/vulnerabilities/CVE-2025-47277/77711", "specs": [ ">=0.6.4,<0.8.5" ], "v": ">=0.6.4,<0.8.5" }, { "advisory": "vLLM, an inference and serving engine for large language models (LLMs), has a Regular Expression Denial of Service (ReDoS) vulnerability in the file `vllm/entrypoints/openai/tool_parsers/pythonic_tool_parser.py` of versions 0.6.4 up to but excluding 0.9.0. The root cause is the use of a highly complex and nested regular expression for tool call detection, which can be exploited by an attacker to cause severe performance degradation or make the service unavailable. The pattern contains multiple nested quantifiers, optional groups, and inner repetitions which make it vulnerable to catastrophic backtracking. Version 0.9.0 contains a patch for the issue.", "cve": "CVE-2025-48887", "id": "pyup.io-77702", "more_info_path": "/vulnerabilities/CVE-2025-48887/77702", "specs": [ ">=0.6.4,<0.9.0" ], "v": ">=0.6.4,<0.9.0" }, { "advisory": "When vLLM is configured to use Mooncake, unsafe deserialization exposed directly over ZMQ/TCP will allow attackers to execute remote code on distributed hosts.", "cve": "CVE-2025-29783", "id": "pyup.io-76301", "more_info_path": "/vulnerabilities/CVE-2025-29783/76301", "specs": [ ">=0.6.5,<0.8.0" ], "v": ">=0.6.5,<0.8.0" }, { "advisory": "vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Versions starting from 0.6.5 and prior to 0.8.5, having vLLM integration with mooncake, are vulnerable to remote code execution due to using pickle based serialization over unsecured ZeroMQ sockets. The vulnerable sockets were set to listen on all network interfaces, increasing the likelihood that an attacker is able to reach the vulnerable ZeroMQ sockets to carry out an attack. vLLM instances that do not make use of the mooncake integration are not vulnerable. This issue has been patched in version 0.8.5.", "cve": "CVE-2025-32444", "id": "pyup.io-77147", "more_info_path": "/vulnerabilities/CVE-2025-32444/77147", "specs": [ ">=0.6.5,<0.8.5" ], "v": ">=0.6.5,<0.8.5" }, { "advisory": "vLLM is an inference and serving engine for large language models (LLMs). In versions starting from 0.7.0 to before 0.9.0, in the file vllm/multimodal/hasher.py, the MultiModalHasher class has a security and data integrity issue in its image hashing method. Currently, it serializes PIL.Image.Image objects using only obj.tobytes(), which returns only the raw pixel data, without including metadata such as the image\u2019s shape (width, height, mode). As a result, two images of different sizes (e.g., 30x100 and 100x30) with the same pixel byte sequence could generate the same hash value. This may lead to hash collisions, incorrect cache hits, and even data leakage or security risks. This issue has been patched in version 0.9.0.", "cve": "CVE-2025-46722", "id": "pyup.io-77699", "more_info_path": "/vulnerabilities/CVE-2025-46722/77699", "specs": [ ">=0.7.0,<0.9.0" ], "v": ">=0.7.0,<0.9.0" }, { "advisory": "vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Versions starting from 0.8.0 and prior to 0.8.5 are affected by a critical performance vulnerability in the input preprocessing logic of the multimodal tokenizer. The code dynamically replaces placeholder tokens (e.g., <|audio_|>, <|image_|>) with repeated tokens based on precomputed lengths. Due to \u200b\u200binefficient list concatenation operations\u200b\u200b, the algorithm exhibits \u200b\u200bquadratic time complexity (O(n\u00b2))\u200b\u200b, allowing malicious actors to trigger resource exhaustion via specially crafted inputs. This issue has been patched in version 0.8.5.", "cve": "CVE-2025-46560", "id": "pyup.io-77146", "more_info_path": "/vulnerabilities/CVE-2025-46560/77146", "specs": [ ">=0.8.0,<0.8.5" ], "v": ">=0.8.0,<0.8.5" }, { "advisory": "vLLM is an inference and serving engine for large language models (LLMs). Version 0.8.0 up to but excluding 0.9.0 have a Denial of Service (ReDoS) that causes the vLLM server to crash if an invalid regex was provided while using structured output. This vulnerability is similar to GHSA-6qc9-v4r8-22xg/CVE-2025-48942, but for regex instead of a JSON schema. Version 0.9.0 fixes the issue.", "cve": "CVE-2025-48943", "id": "pyup.io-77697", "more_info_path": "/vulnerabilities/CVE-2025-48943/77697", "specs": [ ">=0.8.0,<0.9.0" ], "v": ">=0.8.0,<0.9.0" }, { "advisory": "vLLM is an inference and serving engine for large language models (LLMs). In versions 0.8.0 up to but excluding 0.9.0, hitting the /v1/completions API with a invalid json_schema as a Guided Param kills the vllm server. This vulnerability is similar GHSA-9hcf-v7m4-6m2j/CVE-2025-48943, but for regex instead of a JSON schema. Version 0.9.0 fixes the issue.", "cve": "CVE-2025-48942", "id": "pyup.io-77698", "more_info_path": "/vulnerabilities/CVE-2025-48942/77698", "specs": [ ">=0.8.0,<0.9.0" ], "v": ">=0.8.0,<0.9.0" }, { "advisory": "vLLM is an inference and serving engine for large language models (LLMs). In version 0.8.0 up to but excluding 0.9.0, the vLLM backend used with the /v1/chat/completions OpenAPI endpoint fails to validate unexpected or malformed input in the \"pattern\" and \"type\" fields when the tools functionality is invoked. These inputs are not validated before being compiled or parsed, causing a crash of the inference worker with a single request. The worker will remain down until it is restarted. Version 0.9.0 fixes the issue.", "cve": "CVE-2025-48944", "id": "pyup.io-77696", "more_info_path": "/vulnerabilities/CVE-2025-48944/77696", "specs": [ ">=0.8.0,<0.9.0" ], "v": ">=0.8.0,<0.9.0" } ], "vmware-aria-operations-integration-sdk": [ { "advisory": "Vmware-aria-operations-integration-sdk 1.0.1 updates it dependency 'gitpython' to v3.1.34 to include a security fix.", "cve": "CVE-2023-40590", "id": "pyup.io-61251", "more_info_path": "/vulnerabilities/CVE-2023-40590/61251", "specs": [ "<1.0.1" ], "v": "<1.0.1" } ], "vncauthproxy": [ { "advisory": "Vncauthproxy 1.2.0 includes a fix for CVE-2022-36436: Authentication bypass in RFB security handshake.\r\nhttps://github.com/osuosl/twisted_vncauthproxy/pull/1", "cve": "CVE-2022-36436", "id": "pyup.io-50325", "more_info_path": "/vulnerabilities/CVE-2022-36436/50325", "specs": [ "<1.2.0" ], "v": "<1.2.0" } ], "vnccollab-theme": [ { "advisory": "Vnccollab.theme before 1.5.2 has an undisclosed vulnerability in VNC Zimlet.", "cve": "PVE-2021-26173", "id": "pyup.io-26173", "more_info_path": "/vulnerabilities/PVE-2021-26173/26173", "specs": [ "<1.5.2" ], "v": "<1.5.2" }, { "advisory": "Vnccollab-theme before 1.5.2 has an undisclosed vulnerability in VNC Zimlet.", "cve": "PVE-2021-35976", "id": "pyup.io-35976", "more_info_path": "/vulnerabilities/PVE-2021-35976/35976", "specs": [ "<1.5.2" ], "v": "<1.5.2" } ], "vng-api-common": [ { "advisory": "Affected versions of the vng-api-common package are vulnerable to Improper Input Validation due to vng-api-common.middleware.AuthMiddleware passing the string \"HS256\" to PyJWT\u2019s algorithms parameter instead of a list, enabling substring matching on the alg header. The middleware\u2019s JWT verification logic compares the client-supplied alg value using Python\u2019s in operator, so any alg that is a substring of \"HS256\" (for example, \"HS25\" or \"HS2\") would erroneously satisfy the allow-check, though PyJWT\u2019s explicit allow-list of supported algorithms prevents practical misuse.", "cve": "PVE-2024-68087", "id": "pyup.io-68086", "more_info_path": "/vulnerabilities/PVE-2024-68087/68086", "specs": [ "<=2.0.5" ], "v": "<=2.0.5" } ], "vng-api-common-utrecht": [ { "advisory": "Affected versions of the vng-api-common-utrecht package are vulnerable to Improper Input Validation due to vng-api-common.middleware.AuthMiddleware passing the string \"HS256\" to PyJWT\u2019s algorithms parameter instead of a list, enabling substring matching on the alg header. The middleware\u2019s JWT verification logic compares the client-supplied alg value using Python\u2019s in operator, so any alg that is a substring of \"HS256\" (for example, \"HS25\" or \"HS2\") would erroneously satisfy the allow-check, though PyJWT\u2019s explicit allow-list of supported algorithms prevents practical misuse.", "cve": "PVE-2024-68087", "id": "pyup.io-68087", "more_info_path": "/vulnerabilities/PVE-2024-68087/68087", "specs": [ "<=1.3.2" ], "v": "<=1.3.2" } ], "voila": [ { "advisory": "Collabora Online is a collaborative online office suite based on LibreOffice technology. Any deployment of the voil\u00e0 dashboard allows local file inclusion. Any file on a filesystem that is readable by the user that runs the voil\u00e0 dashboard server can be downloaded by someone with network access to the server. Whether this still requires authentication depends on how voil\u00e0 is deployed.", "cve": "CVE-2024-30265", "id": "pyup.io-71958", "more_info_path": "/vulnerabilities/CVE-2024-30265/71958", "specs": [ ">=0.0.2,<0.2.17", ">=0.3.0a0,<0.3.8", ">=0.4.0a0,<0.4.4", ">=0.5.0a0,<0.5.6" ], "v": ">=0.0.2,<0.2.17,>=0.3.0a0,<0.3.8,>=0.4.0a0,<0.4.4,>=0.5.0a0,<0.5.6" } ], "volcengine": [ { "advisory": "Volcengine 1.0.62 updates APIs to prevent injection attacks.\r\nhttps://github.com/volcengine/volc-sdk-python/commit/7f00052c6687ba31dca771c27b36bda8c676e847", "cve": "PVE-2022-51829", "id": "pyup.io-51829", "more_info_path": "/vulnerabilities/PVE-2022-51829/51829", "specs": [ "<1.0.62" ], "v": "<1.0.62" } ], "volttron": [ { "advisory": "Volttron affected versions contained a potential security vulnerability in the RPC subsystem, where capability checks for RPC methods were commented out. This flaw could allow unauthorized access to sensitive methods. Re-enabling these checks has resolved the issue, ensuring that only properly authenticated and authorized agents can execute restricted RPC methods.", "cve": "PVE-2024-72956", "id": "pyup.io-72956", "more_info_path": "/vulnerabilities/PVE-2024-72956/72956", "specs": [ "<9.0.1" ], "v": "<9.0.1" } ], "volttron-core": [ { "advisory": "Affected versions of the VOLTTRON package are potentially vulnerable to Improper Authorization (CWE-285). The issue lies in how configuration stores were managed, potentially allowing unauthorized users to modify or delete configuration files. This vulnerability could be exploited remotely if the configuration store is not properly protected, leading to unauthorized access and system misconfigurations. Mitigation involves upgrading to a version where automated authorization (AuthEntry) is enforced, ensuring proper access control for sensitive operations in the configuration store.", "cve": "PVE-2024-73537", "id": "pyup.io-73537", "more_info_path": "/vulnerabilities/PVE-2024-73537/73537", "specs": [ "<10.0.5rc1" ], "v": "<10.0.5rc1" }, { "advisory": "Volttron-core fixes CVE-2007-4559: Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.", "cve": "CVE-2007-4559", "id": "pyup.io-75936", "more_info_path": "/vulnerabilities/CVE-2007-4559/75936", "specs": [ "<2.0.0rc5" ], "v": "<2.0.0rc5" } ], "volumio-buddy": [ { "advisory": "Volumio-buddy 3.0.3 updates its dependency 'pillow' to v9.3.0 to include security fixes.", "cve": "CVE-2022-45199", "id": "pyup.io-52497", "more_info_path": "/vulnerabilities/CVE-2022-45199/52497", "specs": [ "<3.0.3" ], "v": "<3.0.3" }, { "advisory": "Volumio-buddy 3.0.3 updates its dependency 'pillow' to v9.3.0 to include security fixes.", "cve": "CVE-2022-30595", "id": "pyup.io-52498", "more_info_path": "/vulnerabilities/CVE-2022-30595/52498", "specs": [ "<3.0.3" ], "v": "<3.0.3" }, { "advisory": "Volumio-buddy 3.0.3 updates its dependency 'pillow' to v9.3.0 to include security fixes.", "cve": "CVE-2022-45198", "id": "pyup.io-52471", "more_info_path": "/vulnerabilities/CVE-2022-45198/52471", "specs": [ "<3.0.3" ], "v": "<3.0.3" } ], "vorta": [ { "advisory": "Vorta 0.6.21 includes a not further specified, small security improvement.", "cve": "PVE-2021-37332", "id": "pyup.io-37332", "more_info_path": "/vulnerabilities/PVE-2021-37332/37332", "specs": [ "<0.6.21" ], "v": "<0.6.21" }, { "advisory": "Vorta 0.9.1beta1 ships with Borg 1.2.6 when using the macOS app to include a security fix.", "cve": "CVE-2023-36811", "id": "pyup.io-61457", "more_info_path": "/vulnerabilities/CVE-2023-36811/61457", "specs": [ "<0.9.1beta1" ], "v": "<0.9.1beta1" } ], "vpype": [ { "advisory": "Vpype 1.8.1 updates 'Pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22815", "id": "pyup.io-44521", "more_info_path": "/vulnerabilities/CVE-2022-22815/44521", "specs": [ "<1.8.1" ], "v": "<1.8.1" }, { "advisory": "Vpype 1.8.1 updates 'Pillow' to v9.0.0 to include security fixes.", "cve": "PVE-2022-44524", "id": "pyup.io-44527", "more_info_path": "/vulnerabilities/PVE-2022-44524/44527", "specs": [ "<1.8.1" ], "v": "<1.8.1" }, { "advisory": "Vpype 1.8.1 updates 'Pillow' to v9.0.0 to include security fixes.", "cve": "PVE-2021-44525", "id": "pyup.io-44526", "more_info_path": "/vulnerabilities/PVE-2021-44525/44526", "specs": [ "<1.8.1" ], "v": "<1.8.1" }, { "advisory": "Vpype 1.8.1 updates 'Pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22817", "id": "pyup.io-44523", "more_info_path": "/vulnerabilities/CVE-2022-22817/44523", "specs": [ "<1.8.1" ], "v": "<1.8.1" }, { "advisory": "Vpype 1.8.1 updates 'Pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22816", "id": "pyup.io-44522", "more_info_path": "/vulnerabilities/CVE-2022-22816/44522", "specs": [ "<1.8.1" ], "v": "<1.8.1" } ], "vresutils": [ { "advisory": "Vresutils version 0.3.1 includes a security patch for the function 'init' in 'vresutils/snakemake.py'. It used the unsafe yaml.load(), that allows instantiation of arbitrary objects. Consider yaml.safe_load(). \r\nhttps://github.com/FRESNA/vresutils/commit/5d5fbb5d19454042c5bc1c379b4634d1182cfd6a", "cve": "CVE-2017-18342", "id": "pyup.io-41401", "more_info_path": "/vulnerabilities/CVE-2017-18342/41401", "specs": [ "<0.3.1" ], "v": "<0.3.1" } ], "vtk": [ { "advisory": "Vtk 9.2.5 includes a fix for CVE-2021-42521: There is a NULL pointer dereference vulnerability in VTK before 9.2.5, and it lies in IO/Infovis/vtkXMLTreeReader.cxx. The vendor didn't check the return value of libxml2 API 'xmlDocGetRootElement', and try to dereference it. It is unsafe as the return value can be NULL and that NULL pointer dereference may crash the application.\r\nhttps://gitlab.kitware.com/vtk/vtk/-/commit/f14698e98877b371b0859df164a232f36bd7c3de", "cve": "CVE-2021-42521", "id": "pyup.io-54470", "more_info_path": "/vulnerabilities/CVE-2021-42521/54470", "specs": [ "<9.2.5" ], "v": "<9.2.5" } ], "vtvqa": [ { "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'vtvqa' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.", "cve": "PVE-2024-74232", "id": "pyup.io-74232", "more_info_path": "/vulnerabilities/PVE-2024-74232/74232", "specs": [ ">=0", "<=0" ], "v": ">=0,<=0" } ], "vulcan-sql": [ { "advisory": "Vulcan-sql 0.2.1 includes a fix for a SQL Injection vulnerability.\r\nhttps://github.com/Canner/vulcan-sql/pull/23\r\nhttps://github.com/Canner/vulcan-sql/pull/40", "cve": "PVE-2023-59296", "id": "pyup.io-59296", "more_info_path": "/vulnerabilities/PVE-2023-59296/59296", "specs": [ "<0.2.1" ], "v": "<0.2.1" } ], "vulnix": [ { "advisory": "Vulnix 1.3.1 fixes an arbitrary code execution vulnerability in the derivation evaluation.\r\nhttps://github.com/flyingcircusio/vulnix/commit/cc1195c57c3258b504cac9d69fe86972a22e2c5d", "cve": "PVE-2022-44834", "id": "pyup.io-44834", "more_info_path": "/vulnerabilities/PVE-2022-44834/44834", "specs": [ "<1.3.1" ], "v": "<1.3.1" } ], "vunnel": [ { "advisory": "Vunnel 0.18.0 fixes a race condition that occurred due to the incremental fetching of the CVE list over an extended period, which could lead to inconsistencies and intermittent failures in the quality gate as the underlying API might change the results during this time.\r\nhttps://github.com/anchore/vunnel/pull/438/commits/4f973fd80a887b7be4e7848d65cd5063454c3196", "cve": "PVE-2024-64219", "id": "pyup.io-64219", "more_info_path": "/vulnerabilities/PVE-2024-64219/64219", "specs": [ "<0.18.0" ], "v": "<0.18.0" } ], "vvspy": [ { "advisory": "Vvspy version 2.1.0 has dropped support for Python 3.6 and 3.7 to address the vulnerability CVE-2024-35195 in its `requests` dependency. This update ensures that the package remains secure by leveraging the improvements and fixes available in later versions of Python and the `requests` library.", "cve": "CVE-2024-35195", "id": "pyup.io-71104", "more_info_path": "/vulnerabilities/CVE-2024-35195/71104", "specs": [ "<2.1.0" ], "v": "<2.1.0" } ], "vyper": [ { "advisory": "Vyper 0.2.12 includes a security fix: Memory corruption using function calls within arrays.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-22wc-c9wj-6q2v", "cve": "PVE-2021-41012", "id": "pyup.io-41012", "more_info_path": "/vulnerabilities/PVE-2021-41012/41012", "specs": [ "<0.2.12" ], "v": "<0.2.12" }, { "advisory": "Vyper 0.2.6 includes a security fix: Memory corruption using function calls within tuples / nested calls.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-2r3x-4mrv-mcxf", "cve": "PVE-2023-55096", "id": "pyup.io-55096", "more_info_path": "/vulnerabilities/PVE-2023-55096/55096", "specs": [ "<0.2.6" ], "v": "<0.2.6" }, { "advisory": "Vyper version 0.3.0 includes a fix for CVE-2021-41122: In affected versions, external functions don't properly validate the bounds of decimal arguments. That can lead to logic errors.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-c7pr-343r-5c46\r\nhttps://github.com/vyperlang/vyper/pull/2447", "cve": "CVE-2021-41122", "id": "pyup.io-42051", "more_info_path": "/vulnerabilities/CVE-2021-41122/42051", "specs": [ "<0.3.0" ], "v": "<0.3.0" }, { "advisory": "In Vyper prior to version 0.3.0, default functions don't respect nonreentrancy keys and the lock isn't emitted. No vulnerable production contracts were found. Additionally, using a lock on a `default` function is a very sparsely used pattern. As such, the impact is low.", "cve": "CVE-2024-32648", "id": "pyup.io-70711", "more_info_path": "/vulnerabilities/CVE-2024-32648/70711", "specs": [ "<0.3.0" ], "v": "<0.3.0" }, { "advisory": "Vyper version 0.3.0 includes a fix for CVE-2021-41121: In affected versions, when performing a function call inside a literal struct, there is a memory corruption issue that occurs because of an incorrect pointer to the the top of the stack.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-xv8x-pr4h-73jv\r\nhttps://github.com/vyperlang/vyper/pull/2447", "cve": "CVE-2021-41121", "id": "pyup.io-42056", "more_info_path": "/vulnerabilities/CVE-2021-41121/42056", "specs": [ "<0.3.0" ], "v": "<0.3.0" }, { "advisory": "Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. If an excessively large value is specified as the starting index for an array in `_abi_decode`, it can cause the read position to overflow. This results in the decoding of values outside the intended array bounds, potentially leading to exploitations in contracts that use arrays within `_abi_decode`. This vulnerability affects 0.3.10 and earlier versions. See CVE-2024-26149.", "cve": "CVE-2024-26149", "id": "pyup.io-65700", "more_info_path": "/vulnerabilities/CVE-2024-26149/65700", "specs": [ "<0.3.10" ], "v": "<0.3.10" }, { "advisory": "Vyper is affected by CVE-2023-42443: In version 0.3.9 and prior, under certain conditions, the memory used by the builtins 'raw_call', 'create_from_blueprint' and 'create_copy_of' can be corrupted.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-c647-pxm2-c52w", "cve": "CVE-2023-42443", "id": "pyup.io-61308", "more_info_path": "/vulnerabilities/CVE-2023-42443/61308", "specs": [ "<0.3.10" ], "v": "<0.3.10" }, { "advisory": "Vyper 0.3.10 includes a fix for CVE-2023-41052: In affected versions the order of evaluation of the arguments of the builtin functions 'uint256_addmod', 'uint256_mulmod', 'ecadd' and 'ecmul' does not follow source order. This behaviour is problematic when the evaluation of one of the arguments produces side effects that other arguments depend on. A patch is currently being developed on pull request #3583. When using builtins from the list above, users should make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-4hg4-9mf5-wxxq", "cve": "CVE-2023-41052", "id": "pyup.io-60966", "more_info_path": "/vulnerabilities/CVE-2023-41052/60966", "specs": [ "<0.3.10" ], "v": "<0.3.10" }, { "advisory": "Vyper 0.3.2 includes a fix for CVE-2022-24787: In version 0.3.1 and prior, bytestrings can have dirty bytes in them, resulting in the word-for-word comparisons giving incorrect results. Even without dirty nonzero bytes, two bytestrings can compare to equal if one ends with \"\\x00\" because there is no comparison of the length. \r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-7vrm-3jc8-5wwm", "cve": "CVE-2022-24787", "id": "pyup.io-47973", "more_info_path": "/vulnerabilities/CVE-2022-24787/47973", "specs": [ "<0.3.2" ], "v": "<0.3.2" }, { "advisory": "Vyper 0.3.2 includes a fix for CVE-2022-24845: In affected versions, the return of '.returns_int128()' is not validated to fall within the bounds of 'int128'. This issue can result in a misinterpretation of the integer value and lead to incorrect behavior. As of v0.3.0, '.returns_int128()' is validated in simple expressions, but not complex expressions.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-j2x6-9323-fp7h", "cve": "CVE-2022-24845", "id": "pyup.io-48133", "more_info_path": "/vulnerabilities/CVE-2022-24845/48133", "specs": [ "<0.3.2" ], "v": "<0.3.2" }, { "advisory": "Vyper 0.3.2 includes a fix for CVE-2022-24788: Versions of Vyper prior to 0.3.2 suffer from a potential buffer overrun. Importing a function from a JSON interface which returns 'bytes' generates bytecode which does not clamp bytes length, potentially resulting in a buffer overrun.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-4mrx-6fxm-8jpg", "cve": "CVE-2022-24788", "id": "pyup.io-48132", "more_info_path": "/vulnerabilities/CVE-2022-24788/48132", "specs": [ "<0.3.2" ], "v": "<0.3.2" }, { "advisory": "Vyper 0.3.4 includes a fix for CVE-2022-29255: In versions prior to 0.3.4 when a calling an external contract with no return value, the contract address (including side effects) could be evaluated twice. This may result in incorrect outcomes for contracts.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-4v9q-cgpw-cf38", "cve": "CVE-2022-29255", "id": "pyup.io-49348", "more_info_path": "/vulnerabilities/CVE-2022-29255/49348", "specs": [ "<0.3.4" ], "v": "<0.3.4" }, { "advisory": "Vyper 0.3.8 includes a fix for CVE-2023-32675: In contracts with more than one regular nonpayable function, it is possible to send funds to the default function, even if the default function is marked 'nonpayable'. This applies to contracts compiled with vyper versions prior to 0.3.8. This issue was fixed by the removal of the global 'calldatasize' check in commit '02339dfda'. Users unable to upgrade should avoid use of nonpayable default functions.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-vxmm-cwh2-q762", "cve": "CVE-2023-32675", "id": "pyup.io-58743", "more_info_path": "/vulnerabilities/CVE-2023-32675/58743", "specs": [ "<0.3.8" ], "v": "<0.3.8" }, { "advisory": "Vyper 0.3.8 includes a fix for CVE-2023-30837: The storage allocator does not guard against allocation overflows in versions prior to 0.3.8. An attacker can overwrite the owner variable.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-mgv8-gggw-mrg6", "cve": "CVE-2023-30837", "id": "pyup.io-58241", "more_info_path": "/vulnerabilities/CVE-2023-30837/58241", "specs": [ "<0.3.8" ], "v": "<0.3.8" }, { "advisory": "Vyper 0.3.8 includes a fix for CVE-2023-32058: Prior to version 0.3.8, due to missing overflow check for loop variables, by assigning the iterator of a loop to a variable, it is possible to overflow the type of the latter. The issue seems to happen only in loops of type 'for i in range(a, a + N)' as in loops of type 'for i in range(start, stop)' and 'for i in range(stop)', the compiler is able to raise a 'TypeMismatch' when trying to overflow the variable.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-6r8q-pfpv-7cgj", "cve": "CVE-2023-32058", "id": "pyup.io-58659", "more_info_path": "/vulnerabilities/CVE-2023-32058/58659", "specs": [ "<0.3.8" ], "v": "<0.3.8" }, { "advisory": "Vyper 0.3.8 includes a fix for CVE-2023-32059: Prior to version 0.3.8, internal calls with default arguments are compiled incorrectly. Depending on the number of arguments provided in the call, the defaults are added not right-to-left, but left-to-right. If the types are incompatible, typechecking is bypassed. The ability to pass kwargs to internal functions is an undocumented feature that is not well known about.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-ph9x-4vc9-m39g", "cve": "CVE-2023-32059", "id": "pyup.io-58660", "more_info_path": "/vulnerabilities/CVE-2023-32059/58660", "specs": [ "<0.3.8" ], "v": "<0.3.8" }, { "advisory": "Vyper 0.3.8 includes a fix for CVE-2023-31146: Prior to version 0.3.8, during codegen, the length word of a dynarray is written before the data, which can result in out-of-bounds array access in the case where the dynarray is on both the lhs and rhs of an assignment. The issue can cause data corruption across call frames. The expected behavior is to revert due to out-of-bounds array access.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-3p37-3636-q8wv", "cve": "CVE-2023-31146", "id": "pyup.io-58658", "more_info_path": "/vulnerabilities/CVE-2023-31146/58658", "specs": [ "<0.3.8" ], "v": "<0.3.8" }, { "advisory": "In affected versions of Vyper, when using the built-in `extract32(b, start)`, if the `start` index provided has for side effect to update `b`, the byte array to extract `32` bytes from, it could be that some dirty memory is read and returned by `extract32`.", "cve": "CVE-2024-24564", "id": "pyup.io-71710", "more_info_path": "/vulnerabilities/CVE-2024-24564/71710", "specs": [ "<0.4.0" ], "v": "<0.4.0" }, { "advisory": "Affected versions of Vyper are vulnerable to AugAssign evaluation order causing OOB write within the object. Vyper handles AugAssign statements by first caching the target location to avoid double evaluation. However, in the case when target is an access to a DynArray and the rhs modifies the array, the cached target will evaluate first, and the bounds check will not be re-evaluated during the write portion of the statement.", "cve": "CVE-2025-27105", "id": "pyup.io-75741", "more_info_path": "/vulnerabilities/CVE-2025-27105/75741", "specs": [ "<0.4.1" ], "v": "<0.4.1" }, { "advisory": "Affected versions of Vyper are vulnerable to sqrt doesn't define rounding behavior. Vyper's sqrt() builtin uses the babylonian method to calculate square roots of decimals. Unfortunately, improper handling of the oscillating final states may lead to sqrt incorrectly returning rounded up results.", "cve": "CVE-2025-26622", "id": "pyup.io-75739", "more_info_path": "/vulnerabilities/CVE-2025-26622/75739", "specs": [ "<0.4.1" ], "v": "<0.4.1" }, { "advisory": "Affected versions of Vyper are vulnerable to Success of Certain Precompile Calls not Checked. When the Vyper Compiler uses the precompiles EcRecover (0x1) and Identity (0x4), the success flag of the call is not checked. As a consequence an attacker can provide a specific amount of gas to make these calls fail but let the overall execution continue. Then the execution result can be incorrect.\r\nBased on EVM's rules, after the failed precompile the remaining code has only 1/64 of the pre-call-gas left (as 63/64 were forwarded and spent). Hence, only fairly simple executions can follow the failed precompile calls. Therefore, it was found no significantly impacted real-world contracts.", "cve": "CVE-2025-21607", "id": "pyup.io-75740", "more_info_path": "/vulnerabilities/CVE-2025-21607/75740", "specs": [ "<0.4.1" ], "v": "<0.4.1" }, { "advisory": "Affected versions of Vyper are vulnerable to Multiple eval in For List Iter. Multiple evaluation of a single expression is possible in the iterator target of a for loop. While the iterator expression cannot produce multiple writes, it can consume side effects produced in the loop body (e.g. read a storage variable updated in the loop body) and thus lead to unexpected program behavior. Specifically, reads in iterators which contain an ifexp (e.g. for s: uint256 in ([read(), read()] if True else [])) may interleave reads with writes in the loop body.", "cve": "CVE-2025-27104", "id": "pyup.io-75665", "more_info_path": "/vulnerabilities/CVE-2025-27104/75665", "specs": [ "<0.4.1" ], "v": "<0.4.1" }, { "advisory": "Affected versions of Vyper (\u2264 0.4.2rc1) are vulnerable to side-effect elision in the slice() builtin (CVE-2025-47774), allowing slice(msg.data, self.do_side_effect(), 0) to skip the self.do_side_effect() call . This stems from a missing length >= 1 check for ad-hoc sources in vyper/builtins/functions.py .", "cve": "CVE-2025-47774", "id": "pyup.io-77318", "more_info_path": "/vulnerabilities/CVE-2025-47774/77318", "specs": [ "<0.4.2rc1" ], "v": "<0.4.2rc1" }, { "advisory": "A security flaw was detected in Vyper up to version 0.1.0b16. The vulnerability arises when interfaces return integer types smaller than 256 bits and uint256 is employed, allowing for potential manipulation.", "cve": "PVE-2023-99970", "id": "pyup.io-60869", "more_info_path": "/vulnerabilities/PVE-2023-99970/60869", "specs": [ "<=0.1.0b16" ], "v": "<=0.1.0b16" }, { "advisory": "A vulnerability involving insufficient validation has been identified in specific versions of Vyper, a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). This issue arises when users make assumptions about the return values of certain interface types, potentially leading to unexpected behavior or exploitation. The exploit maturity for this vulnerability is currently classified as unproven.", "cve": "PVE-2024-99830", "id": "pyup.io-65599", "more_info_path": "/vulnerabilities/PVE-2024-99830/65599", "specs": [ "<=0.1.0b16" ], "v": "<=0.1.0b16" }, { "advisory": "In Vyper versions 0.3.10 and prior, incorrect values can be logged when `raw_log` builtin is called with memory or storage arguments to be used as topics. A contract search was performed and no vulnerable contracts were found in production. The `build_IR` function of the `RawLog` class fails to properly unwrap the variables provided as topics. Consequently, incorrect values are logged as topics.", "cve": "CVE-2024-32645", "id": "pyup.io-70708", "more_info_path": "/vulnerabilities/CVE-2024-32645/70708", "specs": [ "<=0.3.10" ], "v": "<=0.3.10" }, { "advisory": "Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. When calls to external contracts are made, we write the input buffer starting at byte 28, and allocate the return buffer to start at byte 0 (overlapping with the input buffer). When checking RETURNDATASIZE for dynamic types, the size is compared only to the minimum allowed size for that type, and not to the returned value's length. As a result, malformed return data can cause the contract to mistake data from the input buffer for returndata. When the called contract returns invalid ABIv2 encoded data, the calling contract can read different invalid data (from the dirty buffer) than the called contract returned. See CVE-2024-24560.", "cve": "CVE-2024-24560", "id": "pyup.io-65289", "more_info_path": "/vulnerabilities/CVE-2024-24560/65289", "specs": [ "<=0.3.10" ], "v": "<=0.3.10" }, { "advisory": "In Vyper versions 0.3.10 and prior, using the `create_from_blueprint` builtin can result in a double eval vulnerability when `raw_args=True` and the `args` argument has side-effects. It can be seen that the `_build_create_IR` function of the `create_from_blueprint` builtin doesn't cache the mentioned `args` argument to the stack. As such, it can be evaluated multiple times (instead of retrieving the value from the stack). No vulnerable production contracts were found. Additionally, double evaluation of side-effects should be easily discoverable in client tests. As such, the impact is low.", "cve": "CVE-2024-32647", "id": "pyup.io-70710", "more_info_path": "/vulnerabilities/CVE-2024-32647/70710", "specs": [ "<=0.3.10" ], "v": "<=0.3.10" }, { "advisory": "Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. Arrays can be keyed by a signed integer, while they are defined for unsigned integers only. The typechecker doesn't throw when spotting the usage of an `int` as an index for an array. The typechecker allows the usage of signed integers to be used as indexes to arrays. The vulnerability is present in different forms in all versions, including `0.3.10`. For ints, the 2's complement representation is used. Because the array was declared very large, the bounds checking will pass Negative values will simply be represented as very large numbers. As of time of publication, a fixed version does not exist.\r\nThere are three potential vulnerability classes: unpredictable behavior, accessing inaccessible elements and denial of service. Class 1: If it is possible to index an array with a negative integer without reverting, this is most likely not anticipated by the developer and such accesses can cause unpredictable behavior for the contract. Class 2: If a contract has an invariant in the form `assert index < x`, the developer will suppose that no elements on indexes `y | y >= x` are accessible. However, by using negative indexes, this can be bypassed. Class 3: If the index is dependent on the state of the contract, this poses a risk of denial of service. If the state of the contract can be manipulated in such way that the index will be forced to be negative, the array access can always revert (because most likely the array won't be declared extremely large). However, all these the scenarios are highly unlikely. Most likely behavior is a revert on the bounds check.", "cve": "CVE-2024-24563", "id": "pyup.io-66722", "more_info_path": "/vulnerabilities/CVE-2024-24563/66722", "specs": [ "<=0.3.10" ], "v": "<=0.3.10" }, { "advisory": "In affected versions of Vyper, using the `sqrt` builtin can result in double eval vulnerability when the argument has side-effects. It can be seen that the `build_IR` function of the `sqrt` builtin doesn't cache the argument to the stack. As such, it can be evaluated multiple times (instead of retrieving the value from the stack). No vulnerable production contracts were found. Additionally, double evaluation of side-effects should be easily discoverable in client tests. As such, the impact is low.", "cve": "CVE-2024-32649", "id": "pyup.io-70712", "more_info_path": "/vulnerabilities/CVE-2024-32649/70712", "specs": [ "<=0.3.10" ], "v": "<=0.3.10" }, { "advisory": "Vyper is a Pythonic Smart Contract Language for the EVM. There is an error in the stack management when compiling the `IR` for `sha3_64`. Concretely, the `height` variable is miscalculated. The vulnerability can't be triggered without writing the `IR` by hand (that is, it cannot be triggered from regular vyper code). `sha3_64` is used for retrieval in mappings. No flow that would cache the `key` was found so the issue shouldn't be possible to trigger when compiling the compiler-generated `IR`. This issue isn't triggered during normal compilation of vyper code so the impact is low. At the time of publication there is no patch available. See CVE-2024-24559.", "cve": "CVE-2024-24559", "id": "pyup.io-65288", "more_info_path": "/vulnerabilities/CVE-2024-24559/65288", "specs": [ "<=0.3.10" ], "v": "<=0.3.10" }, { "advisory": "In Vyper versions 0.3.10 and prior, using the `slice` builtin can result in a double eval vulnerability when the buffer argument is either `msg.data`, `self.code` or `
.code` and either the `start` or `length` arguments have side-effects. It is much harder (but not impossible!) to trigger the bug since 0.3.4 since the unique symbol fence was introduced. No vulnerable production contracts were found. Additionally, double evaluation of side-effects should be easily discoverable in client tests. As such, the impact is low.", "cve": "CVE-2024-32646", "id": "pyup.io-70709", "more_info_path": "/vulnerabilities/CVE-2024-32646/70709", "specs": [ "<=0.3.10" ], "v": "<=0.3.10" }, { "advisory": "Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.10 and earlier, the bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice() function uses a non-literal argument for the start or length variable, this creates the ability for an attacker to overflow the bounds check. This issue can be used to do OOB access to storage, memory or calldata addresses. It can also be used to corrupt the length slot of the respective array. See CVE-2024-24561.", "cve": "CVE-2024-24561", "id": "pyup.io-65290", "more_info_path": "/vulnerabilities/CVE-2024-24561/65290", "specs": [ "<=0.3.10" ], "v": "<=0.3.10" }, { "advisory": "Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. Vyper compiler allows passing a value in builtin raw_call even if the call is a delegatecall or a staticcall. But in the context of delegatecall and staticcall the handling of value is not possible due to the semantics of the respective opcodes, and vyper will silently ignore the value= argument. If the semantics of the EVM are unknown to the developer, he could suspect that by specifying the `value` kwarg, exactly the given amount will be sent along to the target. This vulnerability affects 0.3.10 and earlier versions. See CVE-2024-24567.", "cve": "CVE-2024-24567", "id": "pyup.io-65292", "more_info_path": "/vulnerabilities/CVE-2024-24567/65292", "specs": [ "<=0.3.10" ], "v": "<=0.3.10" }, { "advisory": "Vyper, a Pythonic language for Ethereum Virtual Machine (EVM) smart contracts, had an issue where contracts with large arrays might underallocate the number of slots they need by one. This issue was addressed in version 0.3.8, which corrected a calculation that could produce a rounding error. The calculation, math.ceil(type_.size_in_bytes / 32), could overestimate or underestimate the number of slots needed. The bug is referenced as CVE-2023-46247.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-6m97-7527-mh74", "cve": "CVE-2023-46247", "id": "pyup.io-62837", "more_info_path": "/vulnerabilities/CVE-2023-46247/62837", "specs": [ "<=0.3.7" ], "v": "<=0.3.7" }, { "advisory": "Vyper is affected by CVE-2023-40015: For the following (probably non-exhaustive) list of expressions, the compiler evaluates the arguments from right to left instead of left to right. 'unsafe_add, unsafe_sub, unsafe_mul, unsafe_div, pow_mod256, |, &, ^ (bitwise operators), bitwise_or (deprecated), bitwise_and (deprecated), bitwise_xor (deprecated), raw_call, <, >, <=, >=, ==, !=, in, not in (when lhs and rhs are enums)'. This behavior becomes a problem when the evaluation of one of the arguments produces side effects that other arguments depend on. The following expressions can produce side-effect: state modifying external call , state modifying internal call, 'raw_call', 'pop()' when used on a Dynamic Array stored in the storage, 'create_minimal_proxy_to', 'create_copy_of', 'create_from_blueprint'. This issue has not yet been patched. Users are advised to make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-g2xh-c426-v8mf", "cve": "CVE-2023-40015", "id": "pyup.io-60965", "more_info_path": "/vulnerabilities/CVE-2023-40015/60965", "specs": [ "<=0.3.9" ], "v": "<=0.3.9" }, { "advisory": "Vyper 0.3.10 includes a fix for a vulnerability. Prior to version 0.3.10, the ecrecover precompile does not fill the output buffer if the signature does not verify. However, the ecrecover builtin will still return whatever is at memory location 0. This means that if the compiler has been convinced to write to the 0 memory location with specially crafted data, just before the ecrecover, a signature check might pass on an invalid signature.\r\nhttps://github.com/vyperlang/vyper/commit/019a37ab98ff53f04fecfadf602b6cd5ac748f7f\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-f5x6-7qgp-jhf3", "cve": "CVE-2023-37902", "id": "pyup.io-59955", "more_info_path": "/vulnerabilities/CVE-2023-37902/59955", "specs": [ "<=0.3.9" ], "v": "<=0.3.9" }, { "advisory": "In versions up to and including 0.4.2rc1, `concat()` may skip evaluation of side effects when the length of an argument is zero. This is due to a fastpath in the implementation, which skips evaluation of argument expressions when their length is zero. In practice, it would be very unusual in user code to construct zero-length bytestrings using an expression with side-effects, since zero-length bytestrings are typically constructed with the empty literal `b\"\"`; the only way to construct an empty bytestring which has side effects would be with the ternary operator introduced in v0.3.8, e.g. `b\"\" if self.do_some_side_effect() else b\"\"`. The fix is available in pull request 4644 and expected to be part of the 0.4.2 release. As a workaround, don't have side effects in expressions which construct zero-length bytestrings.", "cve": "CVE-2025-47285", "id": "pyup.io-77320", "more_info_path": "/vulnerabilities/CVE-2025-47285/77320", "specs": [ "<=0.4.2rc1" ], "v": "<=0.4.2rc1" }, { "advisory": "Vyper has an unfixed vulnerability: An unexpectedly large value (> 255) returned by calling ERC20.decimal() (which a malicious contract writer might write) would allow an attacker to manipulate or bypass certain logic depending on this value.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-mr6r-mvw4-736g", "cve": "PVE-2023-55176", "id": "pyup.io-55176", "more_info_path": "/vulnerabilities/PVE-2023-55176/55176", "specs": [ ">=0" ], "v": ">=0" }, { "advisory": "Versions susceptible to a vulnerability within Vyper, a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM), are exposed to memory corruption. This issue specifically affects instances where forwarder-style proxies are deployed utilizing Vyper's create_forwarder_to function, without employing EIP-1167 style forwarders. For memory corruption to occur, a unique set of conditions must be met: the deployment of a forwarder-style proxy via the create_forwarder_to function, the presence of a function returning data exceeding 4096 bytes, and the absence of data sanitation mechanisms for the returned values.", "cve": "PVE-2024-99832", "id": "pyup.io-65597", "more_info_path": "/vulnerabilities/PVE-2024-99832/65597", "specs": [ ">=0,<0.2.9" ], "v": ">=0,<0.2.9" }, { "advisory": "Vyper 0.2.9 includes a security fix: Incorrect 'returndatasize' when using simple forwarder proxies deployed prior to EIP-1167 adoption.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-375m-5fvv-xq23", "cve": "PVE-2023-55187", "id": "pyup.io-55187", "more_info_path": "/vulnerabilities/PVE-2023-55187/55187", "specs": [ ">=0,<0.2.9" ], "v": ">=0,<0.2.9" }, { "advisory": "A reentrancy attack vulnerability exists in some versions of Vyper, specifically through the Crowdfund.refund() function, in the context of Pythonic smart contract language for the Ethereum Virtual Machine (EVM).", "cve": "PVE-2024-99831", "id": "pyup.io-65598", "more_info_path": "/vulnerabilities/PVE-2024-99831/65598", "specs": [ ">=0,<0.3.2" ], "v": ">=0,<0.3.2" }, { "advisory": "Vyper 0.2.15 includes a security fix: Storage variables overwritten by re-entrancy locks.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-7f92-rr6w-cq64", "cve": "PVE-2023-55172", "id": "pyup.io-55172", "more_info_path": "/vulnerabilities/PVE-2023-55172/55172", "specs": [ ">=0.2.13,<0.2.15" ], "v": ">=0.2.13,<0.2.15" }, { "advisory": "Vyper 0.3.1 includes a fix for an Improper Synchronization vulnerability. In vulnerable versions, 0.2.15, 0.2.16, and 0.3.0, named re-entrance locks are allocated incorrectly. Each function using a named re-entrance lock gets a unique lock regardless of the key, allowing cross-function re-entrance in contracts compiled with the susceptible versions.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-5824-cm3x-3c38", "cve": "CVE-2023-39363", "id": "pyup.io-60260", "more_info_path": "/vulnerabilities/CVE-2023-39363/60260", "specs": [ ">=0.2.15,<0.3.1" ], "v": ">=0.2.15,<0.3.1" }, { "advisory": "Vyper is affected by CVE-2023-42441: Starting in version 0.2.9 and prior to version 0.3.10, locks of the type '@nonreentrant(\"\")' or '@nonreentrant('')' do not produce reentrancy checks at runtime. As a workaround, ensure the lock name is a non-empty string.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-3hg2-r75x-g69m", "cve": "CVE-2023-42441", "id": "pyup.io-61307", "more_info_path": "/vulnerabilities/CVE-2023-42441/61307", "specs": [ ">=0.2.9,<0.3.10" ], "v": ">=0.2.9,<0.3.10" }, { "advisory": "Vyper 0.3.8 includes a fix for CVE-2023-30629: In versions 0.3.1 through 0.3.7, the Vyper compiler generates the wrong bytecode. Any contract that uses the 'raw_call' with 'revert_on_failure=False' and 'max_outsize=0' receives the wrong response from 'raw_call'. Depending on the memory garbage, the result can be either 'True' or 'False'. A patch is available and, as of time of publication, anticipated to be part of Vyper 0.3.8. As a workaround, one may always put 'max_outsize>0'.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-w9g2-3w7p-72g9", "cve": "CVE-2023-30629", "id": "pyup.io-55159", "more_info_path": "/vulnerabilities/CVE-2023-30629/55159", "specs": [ ">=0.3.1,<=0.3.7" ], "v": ">=0.3.1,<=0.3.7" }, { "advisory": "In affected versions of Vyper, the `concat` built-in can write over the bounds of the memory buffer that was allocated for it and thus overwrite existing valid data. The root cause is that the `build_IR` for `concat` doesn't properly adhere to the API of copy functions (for `>=0.3.2` the `copy_bytes` function). A contract search was performed and no vulnerable contracts were found in production. The buffer overflow can result in the change of semantics of the contract. The overflow is length-dependent and thus it might go unnoticed during contract testing. However, certainly not all usages of concat will result in overwritten valid data as we require it to be in an internal function and close to the return statement where other memory allocations don't occur.", "cve": "CVE-2024-22419", "id": "pyup.io-71700", "more_info_path": "/vulnerabilities/CVE-2024-22419/71700", "specs": [ ">=0.3.2,<0.4.0" ], "v": ">=0.3.2,<0.4.0" }, { "advisory": "Vyper versions before 0.3.10 are affected by CVE-2023-42460: The '_abi_decode()' function does not validate input when it is nested in an expression. Uses of '_abi_decode()' can be constructed which allow for bounds checking to be bypassed resulting in incorrect results.\r\nhttps://github.com/vyperlang/vyper/security/advisories/GHSA-cx2q-hfxr-rj97", "cve": "CVE-2023-42460", "id": "pyup.io-61478", "more_info_path": "/vulnerabilities/CVE-2023-42460/61478", "specs": [ ">=0.3.4,<0.3.10" ], "v": ">=0.3.4,<0.3.10" }, { "advisory": "Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. Starting in version 0.3.8 and prior to version 0.4.0b1, when looping over a `range` of the form `range(start, start + N)`, if `start` is negative, the execution will always revert. This issue is caused by an incorrect assertion inserted by the code generation of the range `stmt.parse_For_range()`. The issue arises when `start` is signed, instead of using `sle`, `le` is used and `start` is interpreted as an unsigned integer for the comparison. If it is a negative number, its 255th bit is set to `1` and is hence interpreted as a very large unsigned integer making the assertion always fail. Any contract having a `range(start, start + N)` where `start` is a signed integer with the possibility for `start` to be negative is affected. If a call goes through the loop while supplying a negative `start` the execution will revert. Version 0.4.0b1 fixes the issue. See CVE-2024-32481.", "cve": "CVE-2024-32481", "id": "pyup.io-70707", "more_info_path": "/vulnerabilities/CVE-2024-32481/70707", "specs": [ ">=0.3.8,<0.4.0" ], "v": ">=0.3.8,<0.4.0" } ], "wafer": [ { "advisory": "Wafer 0.11.0 includes a different markdown renderer for pages and user-generated content to handle better the risk of XSS.\r\nhttps://github.com/CTPUG/wafer/pull/603", "cve": "PVE-2021-41818", "id": "pyup.io-41818", "more_info_path": "/vulnerabilities/PVE-2021-41818/41818", "specs": [ "<0.11.0" ], "v": "<0.11.0" } ], "wagtail": [ { "advisory": "A cross-site scripting vulnerability exists in versions 2.13-2.13.1, versions 2.12-2.12.4, and versions prior to 2.11.8. When the `{% include_block %}` template tag is used to output the value of a plain-text StreamField block (`CharBlock`, `TextBlock` or a similar user-defined block derived from `FieldBlock`), and that block does not specify a template for rendering, the tag output is not properly escaped as HTML. This could allow users to insert arbitrary HTML or scripting. This vulnerability is only exploitable by users with the ability to author StreamField content (i.e. users with 'editor' access to the Wagtail admin). Patched versions have been released as Wagtail 2.11.8 (for the LTS 2.11 branch), Wagtail 2.12.5, and Wagtail 2.13.2 (for the current 2.13 branch). As a workaround, site implementors who are unable to upgrade to a current supported version should audit their use of `{% include_block %}` to ensure it is not used to output `CharBlock` / `TextBlock` values with no associated template. Note that this only applies where `{% include_block %}` is used directly on that block (uses of `include_block` on a block _containing_ a CharBlock / TextBlock, such as a StructBlock, are unaffected). In these cases, the tag can be replaced with Django's `{{ ... }}` syntax - e.g. `{% include_block my_title_block %}` becomes `{{ my_title_block }}`.", "cve": "CVE-2021-32681", "id": "pyup.io-40803", "more_info_path": "/vulnerabilities/CVE-2021-32681/40803", "specs": [ "<2.11.8", ">=2.13rc1,<=2.13.1", ">=2.12rc1,<=2.12.4" ], "v": "<2.11.8,>=2.13rc1,<=2.13.1,>=2.12rc1,<=2.12.4" }, { "advisory": "Affected versions of Wagtail are vulnerable to cross-site scripting (XSS) on the page revision comparison view within the Wagtail admin interface. A user with a limited-permission editor account for the Wagtail admin could potentially craft a page revision history that, when viewed by a user with higher privileges, could perform actions with that user's credentials. The vulnerability is not exploitable by an ordinary site visitor without access tothe Wagtail admin.", "cve": "CVE-2020-11001", "id": "pyup.io-38184", "more_info_path": "/vulnerabilities/CVE-2020-11001/38184", "specs": [ "<2.7.2", ">=2.8rc1,<2.8.1" ], "v": "<2.7.2,>=2.8rc1,<2.8.1" }, { "advisory": "Affected versions of Wagtail are vulnerable to a potential timing attack on pages or documents that have been protected with a shared password through Wagtail's \"Privacy\" controls. This password check is performed through a character-by-character string comparison, and so an attacker who is able to measure the time taken by this check to a high degree of accuracy could potentially use timing differences to gain knowledge of the password. This is understood to be feasible on a local network, but not on the public internet.\r\nPrivacy settings that restrict access to pages/documents on a per-user or per-group basis (as opposed to a shared password) are unaffected by this vulnerability.", "cve": "CVE-2020-11037", "id": "pyup.io-38249", "more_info_path": "/vulnerabilities/CVE-2020-11037/38249", "specs": [ "<2.7.3", ">=2.8.0,<2.8.2" ], "v": "<2.7.3,>=2.8.0,<2.8.2" }, { "advisory": "Wagtail 2.7.4 includes a fix for CVE-2020-15118 to prevent HTML injection through the form field help text.", "cve": "CVE-2020-15118", "id": "pyup.io-38922", "more_info_path": "/vulnerabilities/CVE-2020-15118/38922", "specs": [ "<2.7.4" ], "v": "<2.7.4" }, { "advisory": "Wagtail 4.1.4 and 4.2.2 include a fix for CVE-2023-28837: Prior to versions 4.1.4 and 4.2.2, a memory exhaustion bug exists in Wagtail's handling of uploaded images and documents. For both images and documents, files are loaded into memory during upload for additional processing. A user with access to upload images or documents through the Wagtail admin interface could upload a file so large that it results in a crash of denial of service. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. It can only be exploited by admin users with permission to upload images or documents. Image uploads are restricted to 10MB by default, however this validation only happens on the frontend and on the backend after the vulnerable code. Patched versions have been released as Wagtail 4.1.4 and Wagtail 4.2.2). Site owners who are unable to upgrade to the new versions are encouraged to add extra protections outside of Wagtail to limit the size of uploaded files.", "cve": "CVE-2023-28837", "id": "pyup.io-54841", "more_info_path": "/vulnerabilities/CVE-2023-28837/54841", "specs": [ "<4.1.4", ">=4.2rc1,<4.2.2" ], "v": "<4.1.4,>=4.2rc1,<4.2.2" }, { "advisory": "Wagtail 5.0.4 and 4.1.8 update its requirement 'pillow' spec to '>=6.0.0,<11.0.0' to include a security fix.\r\nhttps://github.com/wagtail/wagtail/commit/1ea8a0e3603c8cccbaba03f75b706955d531c999", "cve": "CVE-2023-4863", "id": "pyup.io-61487", "more_info_path": "/vulnerabilities/CVE-2023-4863/61487", "specs": [ "<4.1.8", ">=5.0rc1,<5.0.4" ], "v": "<4.1.8,>=5.0rc1,<5.0.4" }, { "advisory": "Wagtail 4.1.9, 5.0.5 and 5.1.3 include a fix for CVE-2023-45809: A user with a limited-permission editor account for the Wagtail admin can make a direct URL request to the admin view that handles bulk actions on user accounts. While authentication rules prevent the user from making any changes, the error message discloses the display names of user accounts, and by modifying URL parameters, the user can retrieve the display name for any user. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.\r\nhttps://github.com/wagtail/wagtail/security/advisories/GHSA-fc75-58r8-rm3h", "cve": "CVE-2023-45809", "id": "pyup.io-61943", "more_info_path": "/vulnerabilities/CVE-2023-45809/61943", "specs": [ "<4.1.9", ">=5.1rc1,<5.1.3", ">=4.2rc1,<5.0.5" ], "v": "<4.1.9,>=5.1rc1,<5.1.3,>=4.2rc1,<5.0.5" }, { "advisory": "Wagtail addresses a regular expression denial-of-service (ReDoS) vulnerability in search query parsing. A bug in Wagtail's 'parse_query_string' would result in it taking a long time to process suitably crafted inputs. When used to parse sufficiently long strings of characters without a space, 'parse_query_string' would take an unexpectedly large amount of time to process, resulting in a denial of service. In an initial Wagtail installation, the vulnerability can be exploited by any Wagtail admin user. It cannot be exploited by end users. If your Wagtail site has a custom search implementation which uses 'parse_query_string', it may be exploitable by other users (e.g. unauthenticated users).", "cve": "CVE-2024-39317", "id": "pyup.io-72127", "more_info_path": "/vulnerabilities/CVE-2024-39317/72127", "specs": [ "<5.2.6", ">=6.0rc1,<6.0.6", ">=6.1rc1,<6.1.3" ], "v": "<5.2.6,>=6.0rc1,<6.0.6,>=6.1rc1,<6.1.3" }, { "advisory": "The Wagtail 5.2rc1 release includes a fix for a race condition that could cause uniqueness errors when inserting reference index entries. This issue was addressed by ignoring conflicts during these insert operations. \r\nhttps://github.com/wagtail/wagtail/commit/4219488a3ce93642781e5be2eda938718380d40d", "cve": "PVE-2024-64506", "id": "pyup.io-64506", "more_info_path": "/vulnerabilities/PVE-2024-64506/64506", "specs": [ "<5.2rc1" ], "v": "<5.2rc1" }, { "advisory": "The Wagtail 5.2rc1 release addresses a race condition issue that could occur when two processes load the edit view of a page without a subscription. This situation could lead to an integrity error. The fix implemented uses the get_or_create method for editor page subscriptions, which ensures that a subscription exists before creating one if it doesn't exist already. \r\nhttps://github.com/wagtail/wagtail/commit/7131a855326b385c04c1e35cef677c25ea1bbc4f", "cve": "PVE-2024-64464", "id": "pyup.io-64464", "more_info_path": "/vulnerabilities/PVE-2024-64464/64464", "specs": [ "<5.2rc1" ], "v": "<5.2rc1" }, { "advisory": "Wagtail is a Django content management system. In affected versions of Wagtail, when saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. See referenced GitHub advisory for additional details, including a workaround. Patched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch). See CVE-2021-29434.", "cve": "CVE-2021-29434", "id": "pyup.io-40230", "more_info_path": "/vulnerabilities/CVE-2021-29434/40230", "specs": [ ">=2.11a1,<2.11.7", ">=2.12a1,<2.12.4" ], "v": ">=2.11a1,<2.11.7,>=2.12a1,<2.12.4" }, { "advisory": "Wagtail 2.15.2 includes a fix for CVE-2022-21683: When notifications for new replies in comment threads are sent, they are sent to all users who have replied or commented anywhere on the site, rather than only in the relevant threads. This means that a user could listen in to new comment replies on pages they have not have editing access to, as long as they have left a comment or reply somewhere on the site. A patched version has been released as Wagtail 2.15.2, which restores the intended behaviour - to send notifications for new replies to the participants in the active thread only (editing permissions are not considered). New comments can be disabled by setting 'WAGTAILADMIN_COMMENTS_ENABLED = False' in the Django settings file.\r\nhttps://github.com/wagtail/wagtail/security/advisories/GHSA-xqxm-2rpm-3889", "cve": "CVE-2022-21683", "id": "pyup.io-44608", "more_info_path": "/vulnerabilities/CVE-2022-21683/44608", "specs": [ ">=2.13a0,<2.15.2" ], "v": ">=2.13a0,<2.15.2" }, { "advisory": "Wagtail 4.1.4 and 4.2.2 include a fix for CVE-2023-28836: Starting in version 1.5 and prior to versions 4.1.4 and 4.2.2, a stored cross-site scripting (XSS) vulnerability exists on ModelAdmin views within the Wagtail admin interface. A user with a limited-permission editor account for the Wagtail admin could potentially craft pages and documents that, when viewed by a user with higher privileges, could perform actions with that user's credentials. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin, and only affects sites with ModelAdmin enabled. For page, the vulnerability is in the \"Choose a parent page\" ModelAdmin view ('ChooseParentView'), available when managing pages via ModelAdmin. For documents, the vulnerability is in the ModelAdmin Inspect view ('InspectView') when displaying document fields. Patched versions have been released as Wagtail 4.1.4 and Wagtail 4.2.2. Site owners who are unable to upgrade to the new versions can disable or override the corresponding functionality.", "cve": "CVE-2023-28836", "id": "pyup.io-54840", "more_info_path": "/vulnerabilities/CVE-2023-28836/54840", "specs": [ ">=4.2rc1,<4.2.2", ">=1.5rc1,<4.1.4" ], "v": ">=4.2rc1,<4.2.2,>=1.5rc1,<4.1.4" }, { "advisory": "Wagtail is an open source content management system built on Django. Due to an improperly applied permission check in the `wagtail.contrib.settings` module, a user with access to the Wagtail admin and knowledge of the URL of the edit view for a settings model can access and update that setting, even when they have not been granted permission over the model. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. Patched versions have been released as Wagtail 6.0.5 and 6.1.2. Wagtail releases prior to 6.0 are unaffected. Users are advised to upgrade. Site owners who are unable to upgrade to a patched version can avoid the vulnerability in `ModelViewSet` by registering the model as a snippet instead. No workaround is available for `wagtail.contrib.settings`. See CVE-2024-35228.", "cve": "CVE-2024-35228", "id": "pyup.io-71780", "more_info_path": "/vulnerabilities/CVE-2024-35228/71780", "specs": [ ">=6.0,<6.0.4", ">=6.1rc2,<6.1.1" ], "v": ">=6.0,<6.0.4,>=6.1rc2,<6.1.1" }, { "advisory": "Wagtail is an open source content management system built on Django. In affected versions if a model has been made available for editing through the `wagtail.contrib.settings` module or `ModelViewSet`, and the `permission` argument on `FieldPanel` has been used to further restrict access to one or more fields of the model, a user with edit permission over the model but not the specific field can craft an HTTP POST request that bypasses the permission check on the individual field, allowing them to update its value. This vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin, or by a user who has not been granted edit access to the model in question. The editing interfaces for pages and snippets are also unaffected. Patched versions have been released as Wagtail 6.0.3 and 6.1. Wagtail releases prior to 6.0 are unaffected. Users are advised to upgrade. Site owners who are unable to upgrade to a patched version can avoid the vulnerability as follows: 1.For models registered through `ModelViewSet`, register the model as a snippet instead; 2. For settings models, place the restricted fields in a separate settings model, and configure permission at the model level. See CVE-2024-32882.", "cve": "CVE-2024-32882", "id": "pyup.io-71238", "more_info_path": "/vulnerabilities/CVE-2024-32882/71238", "specs": [ ">=6.0.2,<6.0.3", ">=6.0rc1,<6.1" ], "v": ">=6.0.2,<6.0.3,>=6.0rc1,<6.1" } ], "wagtail-2fa": [ { "advisory": "Wagtail-2fa 1.1.0 requires the user to enter their password when creating a new token. This is done based on feedback of a security test by an external company.", "cve": "PVE-2021-37614", "id": "pyup.io-37614", "more_info_path": "/vulnerabilities/PVE-2021-37614/37614", "specs": [ "<1.1.0" ], "v": "<1.1.0" }, { "advisory": "Wagtail-2fa version 1.3.0 includes a fix for CVE-2019-16766: When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS.", "cve": "CVE-2019-16766", "id": "pyup.io-41209", "more_info_path": "/vulnerabilities/CVE-2019-16766/41209", "specs": [ "<1.3.0" ], "v": "<1.3.0" }, { "advisory": "Wagtail-2fa version 1.4.1 includes a fix for CVE-2020-5240: In wagtail-2fa before 1.4.1, any user with access to the CMS can view and delete other users 2FA devices by going to the correct path. The user does not require special permissions in order to do so. By deleting the other users device they can disable the target users 2FA devices and potentially compromise the account if they figure out their password.", "cve": "CVE-2020-5240", "id": "pyup.io-37860", "more_info_path": "/vulnerabilities/CVE-2020-5240/37860", "specs": [ "<1.4.1" ], "v": "<1.4.1" } ], "wagtail-autocomplete": [ { "advisory": "Wagtail-autocomplete 0.11 updates its NPM dependency 'tough-cookie' to include a security fix.", "cve": "CVE-2023-26136", "id": "pyup.io-75697", "more_info_path": "/vulnerabilities/CVE-2023-26136/75697", "specs": [ "<0.11" ], "v": "<0.11" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'mixin-deep' to v1.3.2 to include a security fix.", "cve": "CVE-2019-10746", "id": "pyup.io-53802", "more_info_path": "/vulnerabilities/CVE-2019-10746/53802", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'elliptic' to v6.5.4 to include security fixes.", "cve": "CVE-2020-13822", "id": "pyup.io-53800", "more_info_path": "/vulnerabilities/CVE-2020-13822/53800", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'yargs-parser' to v5.0.1 to include a security fix.", "cve": "CVE-2020-7608", "id": "pyup.io-53807", "more_info_path": "/vulnerabilities/CVE-2020-7608/53807", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'handlebars' to v4.7.7 to include security fixes.", "cve": "CVE-2021-23383", "id": "pyup.io-53794", "more_info_path": "/vulnerabilities/CVE-2021-23383/53794", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'ua-parser-js' to v0.7.28 to include security fixes.", "cve": "CVE-2021-27292", "id": "pyup.io-53796", "more_info_path": "/vulnerabilities/CVE-2021-27292/53796", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'lodash.merge' to v4.6.2 to include security fixes.", "cve": "CVE-2018-16487", "id": "pyup.io-53803", "more_info_path": "/vulnerabilities/CVE-2018-16487/53803", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'axios' to v0.21.1 to include security fixes.", "cve": "CVE-2019-10742", "id": "pyup.io-53806", "more_info_path": "/vulnerabilities/CVE-2019-10742/53806", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'handlebars' to v4.7.7 to include security fixes.", "cve": "CVE-2021-23369", "id": "pyup.io-53795", "more_info_path": "/vulnerabilities/CVE-2021-23369/53795", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'lodash' to v4.17.21 to include security fixes.", "cve": "CVE-2021-23337", "id": "pyup.io-53791", "more_info_path": "/vulnerabilities/CVE-2021-23337/53791", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'y18n' to v3.2.2 to include a security fix.", "cve": "CVE-2020-7774", "id": "pyup.io-53801", "more_info_path": "/vulnerabilities/CVE-2020-7774/53801", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'ua-parser-js' to v0.7.28 to include security fixes.", "cve": "CVE-2020-7733", "id": "pyup.io-53798", "more_info_path": "/vulnerabilities/CVE-2020-7733/53798", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'axios' to v0.21.1 to include security fixes.", "cve": "CVE-2020-28168", "id": "pyup.io-53805", "more_info_path": "/vulnerabilities/CVE-2020-28168/53805", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'lodash.merge' to v4.6.2 to include security fixes.", "cve": "CVE-2018-3721", "id": "pyup.io-53804", "more_info_path": "/vulnerabilities/CVE-2018-3721/53804", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'lodash' to v4.17.21 to include security fixes.", "cve": "CVE-2020-8203", "id": "pyup.io-53793", "more_info_path": "/vulnerabilities/CVE-2020-8203/53793", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'hosted-git-info' to v2.8.9 to include a security fix.", "cve": "CVE-2021-23362", "id": "pyup.io-53788", "more_info_path": "/vulnerabilities/CVE-2021-23362/53788", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'lodash' to v4.17.21 to include security fixes.", "cve": "CVE-2020-28500", "id": "pyup.io-53792", "more_info_path": "/vulnerabilities/CVE-2020-28500/53792", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'ua-parser-js' to v0.7.28 to include security fixes.", "cve": "CVE-2020-7793", "id": "pyup.io-53797", "more_info_path": "/vulnerabilities/CVE-2020-7793/53797", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'path-parse' to v1.0.7 to include a security fix.", "cve": "CVE-2021-23343", "id": "pyup.io-53808", "more_info_path": "/vulnerabilities/CVE-2021-23343/53808", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.7 updates its NPM dependency 'elliptic' to v6.5.4 to include security fixes.", "cve": "CVE-2020-28498", "id": "pyup.io-53799", "more_info_path": "/vulnerabilities/CVE-2020-28498/53799", "specs": [ "<0.7" ], "v": "<0.7" }, { "advisory": "Wagtail-autocomplete 0.8.1 updates its NPM dependency 'follow-redirects' to v1.15.0 to include security fixes.", "cve": "CVE-2022-0536", "id": "pyup.io-53810", "more_info_path": "/vulnerabilities/CVE-2022-0536/53810", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Wagtail-autocomplete 0.8.1 updates its NPM dependency 'async' to v2.6.4 to include a security fix.", "cve": "CVE-2021-43138", "id": "pyup.io-53787", "more_info_path": "/vulnerabilities/CVE-2021-43138/53787", "specs": [ "<0.8.1" ], "v": "<0.8.1" }, { "advisory": "Wagtail-autocomplete 0.8.1 updates its NPM dependency 'follow-redirects' to v1.15.0 to include security fixes.", "cve": "CVE-2022-0155", "id": "pyup.io-53809", "more_info_path": "/vulnerabilities/CVE-2022-0155/53809", "specs": [ "<0.8.1" ], "v": "<0.8.1" } ], "wagtail-herald": [ { "advisory": "Affected versions of the wagtail-herald package are vulnerable to cross-site scripting (XSS) due to custom head HTML injection being rendered into pages.", "cve": "PVE-2025-82898", "id": "pyup.io-82898", "more_info_path": "/vulnerabilities/PVE-2025-82898/82898", "specs": [ "<0.1.0" ], "v": "<0.1.0" } ], "waifu2x-ncnn-vulkan-python": [ { "advisory": "Waifu2x-ncnn-vulkan-python 1.0.4 and prior releases ship with a version of C library 'libwebp' which is affected by a high risk vulnerability.\r\nhttps://inspector.pypi.io/project/waifu2x-ncnn-vulkan-python/1.0.4/packages/42/28/a5ed9e1e843732709d07a0e1c8d50a71a1933a923883905aa4d11191b297/waifu2x-ncnn-vulkan-python-1.0.4.tar.gz/waifu2x-ncnn-vulkan-python-1.0.4/waifu2x_ncnn_vulkan_python/waifu2x-ncnn-vulkan/src/libwebp/ChangeLog", "cve": "CVE-2023-4863", "id": "pyup.io-62302", "more_info_path": "/vulnerabilities/CVE-2023-4863/62302", "specs": [ "<=1.0.4" ], "v": "<=1.0.4" } ], "waitress": [ { "advisory": "Waitress 0.9.0 checks for line feed/carriage to prevent HTTP Response Splitting attacks in the status line or the key of a header. \r\nhttps://github.com/Pylons/waitress/pull/124\r\nhttps://github.com/Pylons/waitress/issues/122", "cve": "PVE-2021-36764", "id": "pyup.io-36764", "more_info_path": "/vulnerabilities/PVE-2021-36764/36764", "specs": [ "<0.9.0" ], "v": "<0.9.0" }, { "advisory": "Waitress before 1.0.0 drops HTTP headers that contain an underscore in the key when received from a client. This is to stop any possible underscore/dash conflation that may lead to security issues. See: https://github.com/Pylons/waitress/pull/80 and https://www.djangoproject.com/weblog/2015/jan/13/security/", "cve": "PVE-2021-26174", "id": "pyup.io-26174", "more_info_path": "/vulnerabilities/PVE-2021-26174/26174", "specs": [ "<1.0.0" ], "v": "<1.0.0" }, { "advisory": "waitress 1.2.0b1 provides a new security feature when using Waitress behind a proxy in that it is possible to remove untrusted proxy headers thereby making sure that downstream WSGI applications don't accidentally use those proxy headers to make security decisions", "cve": "PVE-2021-26390", "id": "pyup.io-26390", "more_info_path": "/vulnerabilities/PVE-2021-26390/26390", "specs": [ "<1.2.0b1" ], "v": "<1.2.0b1" }, { "advisory": "Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: \"Transfer-Encoding: gzip, chunked\" would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0.", "cve": "CVE-2019-16786", "id": "pyup.io-39556", "more_info_path": "/vulnerabilities/CVE-2019-16786/39556", "specs": [ "<1.4.0" ], "v": "<1.4.0" }, { "advisory": "Waitress 1.4.0 includes a fix for CVE-2019-16785: Waitress through version 1.3.1 implemented a \"MAY\" part of the RFC7230 which states: \"Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR.\" Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. \r\nhttps://github.com/Pylons/waitress/security/advisories/GHSA-pg36-wpm5-g57p", "cve": "CVE-2019-16785", "id": "pyup.io-37822", "more_info_path": "/vulnerabilities/CVE-2019-16785/37822", "specs": [ "<1.4.0" ], "v": "<1.4.0" }, { "advisory": "In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure. This issue is fixed in Waitress 1.4.1 through more strict HTTP field validation.", "cve": "CVE-2019-16789", "id": "pyup.io-37674", "more_info_path": "/vulnerabilities/CVE-2019-16789/37674", "specs": [ "<1.4.1" ], "v": "<1.4.1" }, { "advisory": "Waitress 2.1.1 includes a fix for CVE-2022-24761: When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python's 'int()' to parse strings into integers, leading to '+10' to be parsed as '10'', or '0x01' to be parsed as '1', where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. A workaround is available. When deploying a proxy in front of waitress, turning on functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality.\r\nhttps://github.com/Pylons/waitress/security/advisories/GHSA-4f7p-27jc-3c36", "cve": "CVE-2022-24761", "id": "pyup.io-46436", "more_info_path": "/vulnerabilities/CVE-2022-24761/46436", "specs": [ "<2.1.1" ], "v": "<2.1.1" }, { "advisory": "Affected versions of Waitress are vulnerable to a Race Condition leading to Denial of Service (CWE-362). The unconditional connection closure on socket errors could lead to premature termination of valid connections during high-load scenarios. The vulnerability exists in the wasyncore.dispatcher.send() method, where any disconnection error triggers immediate connection closure. This could be exploited by attackers to force connection terminations during partial sends, potentially leading to denial of service. The attacker could time requests to coincide with partial buffer flushes. Fixed by making connection closure conditional and allowing the application layer to control closure behavior.", "cve": "PVE-2024-73921", "id": "pyup.io-73921", "more_info_path": "/vulnerabilities/PVE-2024-73921/73921", "specs": [ "<2.1.2" ], "v": "<2.1.2" }, { "advisory": "Affected versions of Waitress are vulnerable to a Race Condition (CWE-362). The asynchronous dispatcher implementation could lead to an exploitable race condition during socket connection state management. An attacker could potentially exploit the time window between connection checks and actual operations to cause denial of service or potentially execute unauthorized operations. The vulnerability exists in the dispatcher.connect() and connection state verification methods. The race condition is exploitable when multiple threads interact with the same socket connection. The issue is fixed by simplifying the connection state management and moving the connection handling directly into HTTPChannel class, removing the race condition window.", "cve": "CVE-2024-49769", "id": "pyup.io-73920", "more_info_path": "/vulnerabilities/CVE-2024-49769/73920", "specs": [ "<3.0.1" ], "v": "<3.0.1" }, { "advisory": "Waitress through version 1.3.1 allows request smuggling by sending the Content-Length header twice. Waitress would fold a double Content-Length header and due to being unable to cast the now comma separated value to an integer would set the Content-Length to 0 internally. If two Content-Length headers are sent in a single request, Waitress would treat the request as having no body, thereby treating the body of the request as a new request in HTTP pipelining. This issue is fixed in Waitress 1.4.0.", "cve": "CVE-2019-16792", "id": "pyup.io-42265", "more_info_path": "/vulnerabilities/CVE-2019-16792/42265", "specs": [ "<=1.3.1" ], "v": "<=1.3.1" }, { "advisory": "Waitress 1.4.2 allows a DOS attack when waitress receives a header that contains invalid characters. When a header like \"Bad-header: xxxxxxxxxxxxxxx\\x10\" is received, it will cause the regular expression engine to catastrophically backtrack causing the process to use 100% CPU time and blocking any other interactions. This allows an attacker to send a single request with an invalid header and take the service offline. This issue was introduced in version 1.4.2 when the regular expression was updated to attempt to match the behavior required by errata associated with RFC7230. The regular expression that was used to validate incoming headers has been updated in version 1.4.3.", "cve": "CVE-2020-5236", "id": "pyup.io-42295", "more_info_path": "/vulnerabilities/CVE-2020-5236/42295", "specs": [ "==1.4.2" ], "v": "==1.4.2" }, { "advisory": "Selected versions of waitress are susceptible to HTTP response splitting attacks. This vulnerability arises when an attacker embeds either a \\r or \\n character into the header value of an HTTP response, enabling the setting of arbitrary headers. This issue threatens the integrity of web server environments by allowing malicious manipulation of HTTP responses.", "cve": "PVE-2024-99829", "id": "pyup.io-65600", "more_info_path": "/vulnerabilities/PVE-2024-99829/65600", "specs": [ ">=0,<0.8.11b0" ], "v": ">=0,<0.8.11b0" }, { "advisory": "Affected versions of Waitress are vulnerable to a Race Condition (CWE-362). A race condition between thread handlers could allow processing of data on connections that are marked for closure, potentially leading to denial of service or memory exhaustion. The vulnerability exists in the HTTPChannel.received() method, where data processing could continue even after the connection was marked for closure. The race condition occurs between the main thread's readable() check and the service thread's connection closure handling. This is fixed by adding proper synchronization checks within the requests_lock context. The fix ensures connection state is verified while holding the lock, preventing the race condition.", "cve": "CVE-2024-49768", "id": "pyup.io-73954", "more_info_path": "/vulnerabilities/CVE-2024-49768/73954", "specs": [ ">=2.0.0b0,<3.0.1" ], "v": ">=2.0.0b0,<3.0.1" }, { "advisory": "Waitress 2.1.2 includes a fix for CVE-2022-31015: Waitress versions 2.1.0 and 2.1.1 may terminate early due to a thread closing a socket while the main thread is about to call select(). This will lead to the main thread raising an exception that is not handled and then causing the entire application to be killed. This issue has been fixed in Waitress 2.1.2 by no longer allowing the WSGI thread to close the socket. Instead, that is always delegated to the main thread. There is no workaround for this issue, however, users using waitress behind a reverse proxy server are less likely to have issues if the reverse proxy always reads the full response.\r\nhttps://github.com/Pylons/waitress/security/advisories/GHSA-f5x9-8jwc-25rw", "cve": "CVE-2022-31015", "id": "pyup.io-49257", "more_info_path": "/vulnerabilities/CVE-2022-31015/49257", "specs": [ ">=2.1.0,<2.1.2" ], "v": ">=2.1.0,<2.1.2" } ], "wallycore": [ { "advisory": "Wallycore 0.8.9 updates its C dependency 'libsecp256k1' to fix a potential timing leak when compiling with clang v14 or later.\r\nhttps://github.com/BlockstreamResearch/secp256k1-zkp/compare/71a206fa5bbcbba5792fc6f9eb7e07c69555f2df...6ec1ff6040164cbc3fafb665e28449870e6a9113", "cve": "PVE-2023-55020", "id": "pyup.io-55020", "more_info_path": "/vulnerabilities/PVE-2023-55020/55020", "specs": [ "<0.8.9" ], "v": "<0.8.9" } ], "wandb": [ { "advisory": "Wandb 0.12.12 fixes an unsafe temporary file creation vulnerability.\r\nhttps://github.com/wandb/client/pull/3360", "cve": "PVE-2022-47988", "id": "pyup.io-47988", "more_info_path": "/vulnerabilities/PVE-2022-47988/47988", "specs": [ "<0.12.12" ], "v": "<0.12.12" }, { "advisory": "Wandb 0.12.18 updates its dependency 'rsa' to v4.7 to include security fixes.", "cve": "CVE-2020-13757", "id": "pyup.io-49367", "more_info_path": "/vulnerabilities/CVE-2020-13757/49367", "specs": [ "<0.12.18" ], "v": "<0.12.18" }, { "advisory": "Wandb 0.12.18 updates its dependency 'urllib3' to v1.26.5 to include security fixes.", "cve": "CVE-2021-33503", "id": "pyup.io-49369", "more_info_path": "/vulnerabilities/CVE-2021-33503/49369", "specs": [ "<0.12.18" ], "v": "<0.12.18" }, { "advisory": "Wandb 0.12.18 updates its dependency 'rsa' to v4.7 to include security fixes.", "cve": "CVE-2020-25658", "id": "pyup.io-49366", "more_info_path": "/vulnerabilities/CVE-2020-25658/49366", "specs": [ "<0.12.18" ], "v": "<0.12.18" }, { "advisory": "Wandb 0.12.18 updates its dependency 'urllib3' to v1.26.5 to include security fixes.", "cve": "CVE-2020-7212", "id": "pyup.io-49370", "more_info_path": "/vulnerabilities/CVE-2020-7212/49370", "specs": [ "<0.12.18" ], "v": "<0.12.18" }, { "advisory": "Wandb 0.12.18 updates its dependency 'httplib2' to v0.19.0 to include security fixes.", "cve": "CVE-2021-21240", "id": "pyup.io-49358", "more_info_path": "/vulnerabilities/CVE-2021-21240/49358", "specs": [ "<0.12.18" ], "v": "<0.12.18" }, { "advisory": "Wandb 0.12.18 updates its dependency 'httplib2' to v0.19.0 to include security fixes.", "cve": "CVE-2020-11078", "id": "pyup.io-49365", "more_info_path": "/vulnerabilities/CVE-2020-11078/49365", "specs": [ "<0.12.18" ], "v": "<0.12.18" }, { "advisory": "Wandb 0.12.18 updates its dependency 'urllib3' to v1.26.5 to include security fixes.", "cve": "CVE-2020-26137", "id": "pyup.io-49368", "more_info_path": "/vulnerabilities/CVE-2020-26137/49368", "specs": [ "<0.12.18" ], "v": "<0.12.18" }, { "advisory": "A race condition and inconsistent control handling vulnerability were identified in the wandb package's Handler and Writer components. This issue could lead to data corruption, unauthorized data exposure, or improper record handling, especially in concurrent environments. The vulnerability has been mitigated by introducing record cloning and standardized control flag application.", "cve": "PVE-2024-72896", "id": "pyup.io-72896", "more_info_path": "/vulnerabilities/PVE-2024-72896/72896", "specs": [ "<0.15.10" ], "v": "<0.15.10" }, { "advisory": "A race condition and inconsistent cleanup vulnerability in wandb's LaunchAgent allowed unsynchronized access to job status data across threads. If multiple threads accessed or modified job status simultaneously, this could lead to data corruption or incomplete resource cleanup. The vulnerability is resolved by enforcing thread-safe data access and ensuring reliable cleanup even when exceptions occur.", "cve": "PVE-2024-72895", "id": "pyup.io-72895", "more_info_path": "/vulnerabilities/PVE-2024-72895/72895", "specs": [ "<0.15.12" ], "v": "<0.15.12" }, { "advisory": "Socket in wandb 0.8.0 only binds to localhost for improved security and prevents firewall warnings in OSX.", "cve": "PVE-2021-37149", "id": "pyup.io-37149", "more_info_path": "/vulnerabilities/PVE-2021-37149/37149", "specs": [ "<0.8.0" ], "v": "<0.8.0" }, { "advisory": "Wandb 0.8.2 updates the pyyaml requirement to address a CVE. No CVE number was mentioned, but it is probably CVE-2017-18342.", "cve": "CVE-2017-18342", "id": "pyup.io-38548", "more_info_path": "/vulnerabilities/CVE-2017-18342/38548", "specs": [ "<0.8.2" ], "v": "<0.8.2" } ], "wandelbots-nova": [ { "advisory": "Affected versions of wandelbots-nova are potentially vulnerable to command injection. Improper handling of PR titles allows attackers to execute arbitrary shell commands in GitHub Actions, leading to potential CI environment compromise. The issue occurs in the pr-title-check workflow, where special characters (e.g., backticks) are not properly escaped.", "cve": "PVE-2025-75842", "id": "pyup.io-75842", "more_info_path": "/vulnerabilities/PVE-2025-75842/75842", "specs": [ "<0.47.0" ], "v": "<0.47.0" } ], "warfit-learn": [ { "advisory": "Warfit-learn 0.2 includes minor security improvements for dependencies.", "cve": "PVE-2021-39213", "id": "pyup.io-39213", "more_info_path": "/vulnerabilities/PVE-2021-39213/39213", "specs": [ "<0.2" ], "v": "<0.2" } ], "wasmer": [ { "advisory": "Wasmer 0.1.4 updates 'wasmer-runtime' to v0.2.1, that includes a security fix: the hashing algorithm for caching was made crypto-secure.\r\nhttps://github.com/wasmerio/wasmer/pull/214", "cve": "PVE-2021-37044", "id": "pyup.io-37044", "more_info_path": "/vulnerabilities/PVE-2021-37044/37044", "specs": [ "<0.1.4" ], "v": "<0.1.4" } ], "wasmtime": [ { "advisory": "Wasmtime 0.27.0 (Python bindings) downloads a new precompiled version of Wastime core that includes security fixes.", "cve": "CVE-2021-32629", "id": "pyup.io-40530", "more_info_path": "/vulnerabilities/CVE-2021-32629/40530", "specs": [ "<0.27.0" ], "v": "<0.27.0" }, { "advisory": "Wasmtime version 0.30.0 (Python bindings) downloads a new precompiled version of Wastime core that includes security fixes.", "cve": "CVE-2021-39219", "id": "pyup.io-41963", "more_info_path": "/vulnerabilities/CVE-2021-39219/41963", "specs": [ "<0.30.0" ], "v": "<0.30.0" }, { "advisory": "Wasmtime 0.35.0 (Python bindings) downloads a new precompiled version of Wastime core that includes security fixes.", "cve": "CVE-2022-23636", "id": "pyup.io-45751", "more_info_path": "/vulnerabilities/CVE-2022-23636/45751", "specs": [ "<0.35.0" ], "v": "<0.35.0" }, { "advisory": "Wasmtime 0.36.0 (Python bindings) downloads a new precompiled version of Wastime core that includes security fixes.", "cve": "CVE-2022-24791", "id": "pyup.io-48294", "more_info_path": "/vulnerabilities/CVE-2022-24791/48294", "specs": [ "<0.36.0" ], "v": "<0.36.0" }, { "advisory": "Wasmtime 0.39.1 and 0.38.3 (Python bindings) download a new precompiled version of Wastime core that includes security fixes.", "cve": "CVE-2022-31146", "id": "pyup.io-50269", "more_info_path": "/vulnerabilities/CVE-2022-31146/50269", "specs": [ "<0.38.3", ">=0.39.0,<0.39.1" ], "v": "<0.38.3,>=0.39.0,<0.39.1" }, { "advisory": "Wasmtime 0.39.1 (Python bindings) downloads a new precompiled version of Wastime core that includes security fixes.", "cve": "CVE-2022-31169", "id": "pyup.io-50251", "more_info_path": "/vulnerabilities/CVE-2022-31169/50251", "specs": [ "<0.39.1" ], "v": "<0.39.1" }, { "advisory": "Wasmtime 15.0.1 (Python bindings) downloads a precompiled version of Wasmtime core (15.0.1) that includes a security fix for the CVE-2022-31104.\r\nhttps://github.com/bytecodealliance/wasmtime/pull/4317\r\nhttps://github.com/bytecodealliance/wasmtime/commit/8bb07523e22df1ab3cbd265c77e836bf84186eb7", "cve": "CVE-2022-31104", "id": "pyup.io-62849", "more_info_path": "/vulnerabilities/CVE-2022-31104/62849", "specs": [ "<15.0.1" ], "v": "<15.0.1" }, { "advisory": "Wasmtime 3.0.0 (Python bindings) downloads a precompiled version of Wastime core that includes security fixes.\r\nhttps://github.com/bytecodealliance/wasmtime-py/commit/18a742a3457d6edfab7e96af466721e19d2e12cd", "cve": "CVE-2022-39392", "id": "pyup.io-51995", "more_info_path": "/vulnerabilities/CVE-2022-39392/51995", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "Wasmtime 3.0.0 (Python bindings) downloads a precompiled version of Wastime core that includes security fixes.\r\nhttps://github.com/bytecodealliance/wasmtime-py/commit/18a742a3457d6edfab7e96af466721e19d2e12cd", "cve": "CVE-2022-39394", "id": "pyup.io-51998", "more_info_path": "/vulnerabilities/CVE-2022-39394/51998", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "Wasmtime 3.0.0 (Python bindings) downloads a precompiled version of Wastime core that includes security fixes.\r\nhttps://github.com/bytecodealliance/wasmtime-py/commit/18a742a3457d6edfab7e96af466721e19d2e12cd", "cve": "CVE-2022-39393", "id": "pyup.io-51997", "more_info_path": "/vulnerabilities/CVE-2022-39393/51997", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "Wasmtime (Python bindings) 7.0.0 downloads a precompiled version of Wastime core that includes security fixes.\r\nhttps://github.com/bytecodealliance/wasmtime-py/commit/4a52ebbe0a7e577721a30a38170b7472aa153329", "cve": "CVE-2023-27477", "id": "pyup.io-53756", "more_info_path": "/vulnerabilities/CVE-2023-27477/53756", "specs": [ "<7.0.0" ], "v": "<7.0.0" }, { "advisory": "Wasmtime (Python bindings) 7.0.0 downloads a precompiled version of Wasmtime core that includes security fixes.\r\nhttps://github.com/bytecodealliance/wasmtime-py/commit/4a52ebbe0a7e577721a30a38170b7472aa153329", "cve": "CVE-2023-26489", "id": "pyup.io-53755", "more_info_path": "/vulnerabilities/CVE-2023-26489/53755", "specs": [ "<7.0.0" ], "v": "<7.0.0" }, { "advisory": "Wasmtime 9.0.0 (Python bindings) downloads a precompiled version of Wasmtime core (9.0.0) that includes a security fix.\r\nhttps://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-ch89-5g45-qwc7", "cve": "CVE-2023-30624", "id": "pyup.io-58761", "more_info_path": "/vulnerabilities/CVE-2023-30624/58761", "specs": [ "<9.0.0" ], "v": "<9.0.0" }, { "advisory": "Wasmtime 0.30.0 (Python bindings) downloads a new precompiled version of Wastime core that includes security fixes.", "cve": "CVE-2021-39216", "id": "pyup.io-41831", "more_info_path": "/vulnerabilities/CVE-2021-39216/41831", "specs": [ ">=0.19.0,<0.30.0" ], "v": ">=0.19.0,<0.30.0" }, { "advisory": "Wastime 0.30.0 (Python bindings) downloads a new precompiled version of Wastime core that includes security fixes.", "cve": "CVE-2021-39218", "id": "pyup.io-41962", "more_info_path": "/vulnerabilities/CVE-2021-39218/41962", "specs": [ ">=0.26.0,<0.30.0" ], "v": ">=0.26.0,<0.30.0" }, { "advisory": "Wasmtime 13.0.0 (Python bindings) downloads a precompiled version of Wasmtime core (13.0.0) that includes a security fix.\r\nhttps://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-gw5p-q8mj-p7gh", "cve": "CVE-2023-41880", "id": "pyup.io-61339", "more_info_path": "/vulnerabilities/CVE-2023-41880/61339", "specs": [ ">=10.0.0,<13.0.0" ], "v": ">=10.0.0,<13.0.0" } ], "watchmaker": [ { "advisory": "watchmaker 0.14.0 implements additional Salt states to address security scan issues", "cve": "PVE-2021-36948", "id": "pyup.io-36948", "more_info_path": "/vulnerabilities/PVE-2021-36948/36948", "specs": [ "<0.14.0" ], "v": "<0.14.0" } ], "watchui": [ { "advisory": "Watchui 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "PVE-2022-44524", "id": "pyup.io-46492", "more_info_path": "/vulnerabilities/PVE-2022-44524/46492", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Watchui 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "PVE-2021-44525", "id": "pyup.io-46493", "more_info_path": "/vulnerabilities/PVE-2021-44525/46493", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Watchui 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22816", "id": "pyup.io-46432", "more_info_path": "/vulnerabilities/CVE-2022-22816/46432", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Watchui 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22815", "id": "pyup.io-46490", "more_info_path": "/vulnerabilities/CVE-2022-22815/46490", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Watchui 2.0.1 updates its dependency 'pillow' to v9.0.0 to include security fixes.", "cve": "CVE-2022-22817", "id": "pyup.io-46491", "more_info_path": "/vulnerabilities/CVE-2022-22817/46491", "specs": [ "<2.0.1" ], "v": "<2.0.1" }, { "advisory": "Watchui 2.0.9 updates its dependency 'pillow' to v9.2.0 to include a security fix.", "cve": "CVE-2022-45198", "id": "pyup.io-51930", "more_info_path": "/vulnerabilities/CVE-2022-45198/51930", "specs": [ "<2.0.9" ], "v": "<2.0.9" } ], "watertools": [ { "advisory": "The Watertools package in PyPI v0.0.0 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.", "cve": "CVE-2022-34056", "id": "pyup.io-62872", "more_info_path": "/vulnerabilities/CVE-2022-34056/62872", "specs": [ "==0.0.0" ], "v": "==0.0.0" } ], "watools": [ { "advisory": "The watools package in PyPI v0.0.1 to v0.0.8 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.", "cve": "CVE-2022-33003", "id": "pyup.io-62693", "more_info_path": "/vulnerabilities/CVE-2022-33003/62693", "specs": [ ">=0.0.1,<=0.0.8" ], "v": ">=0.0.1,<=0.0.8" } ], "wdmtoolbox": [ { "advisory": "Wdmtoolbox 12.9.3 pins the dependency 'numpy>=1.22.2' to include security fixes.", "cve": "CVE-2021-41495", "id": "pyup.io-49447", "more_info_path": "/vulnerabilities/CVE-2021-41495/49447", "specs": [ "<12.9.3" ], "v": "<12.9.3" }, { "advisory": "Wdmtoolbox 12.9.3 pins the dependency 'numpy>=1.22.2' to include security fixes.", "cve": "CVE-2021-41496", "id": "pyup.io-49501", "more_info_path": "/vulnerabilities/CVE-2021-41496/49501", "specs": [ "<12.9.3" ], "v": "<12.9.3" }, { "advisory": "Wdmtoolbox 12.9.3 pins the dependency 'pygments>=2.7.4' to include security fixes.", "cve": "CVE-2021-20270", "id": "pyup.io-49502", "more_info_path": "/vulnerabilities/CVE-2021-20270/49502", "specs": [ "<12.9.3" ], "v": "<12.9.3" }, { "advisory": "Wdmtoolbox 12.9.3 pins the dependency 'numpy>=1.22.2' to include security fixes.", "cve": "CVE-2020-11023", "id": "pyup.io-49505", "more_info_path": "/vulnerabilities/CVE-2020-11023/49505", "specs": [ "<12.9.3" ], "v": "<12.9.3" }, { "advisory": "Wdmtoolbox 12.9.3 pins the dependency 'pygments>=2.7.4' to include security fixes.", "cve": "CVE-2021-27291", "id": "pyup.io-49503", "more_info_path": "/vulnerabilities/CVE-2021-27291/49503", "specs": [ "<12.9.3" ], "v": "<12.9.3" }, { "advisory": "Wdmtoolbox 12.9.3 pins the dependency 'sphinx>=3.0.4' to include security fixes.", "cve": "CVE-2020-11022", "id": "pyup.io-49504", "more_info_path": "/vulnerabilities/CVE-2020-11022/49504", "specs": [ "<12.9.3" ], "v": "<12.9.3" } ], "weasyprint": [ { "advisory": "Affected versions of the weasyprint package are vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of redirect destinations in the URL fetching mechanism. The default_url_fetcher function in weasyprint/urls.py relies on Python's urllib.request.urlopen, which automatically follows HTTP redirects (301, 302, 307) without re-invoking the developer's custom url_fetcher validation logic, creating a Time-of-Check to Time-of-Use (TOCTOU) condition. An attacker can supply an external URL that passes initial security checks but redirects to internal network resources such as localhost services or cloud metadata endpoints, enabling exfiltration of sensitive data, including instance credentials.", "cve": "CVE-2025-68616", "id": "pyup.io-84841", "more_info_path": "/vulnerabilities/CVE-2025-68616/84841", "specs": [ "<68.0" ], "v": "<68.0" }, { "advisory": "Affected versions of WeasyPrint are vulnerable to an arbitrary file content attachment vulnerability. This issue enables attackers to attach content from arbitrary files and URLs to generated PDF documents, bypassing restrictions imposed by the configured `url_fetcher`. The attack vector exploits weaknesses in WeasyPrint\u2019s file and URL handling during PDF generation. Mitigation involves upgrading to version 61.2 or later, which patches the vulnerability and reinforces content source validation for secure PDF creation. This vulnerability specifically impacts web developers using WeasyPrint for PDF document generation.", "cve": "CVE-2024-28184", "id": "pyup.io-71637", "more_info_path": "/vulnerabilities/CVE-2024-28184/71637", "specs": [ ">=61.0,<=61.1" ], "v": ">=61.0,<=61.1" } ], "weave": [ { "advisory": "A path traversal vulnerability has been identified in the Weave server's file serving functionality. It could allow an attacker to access files outside the intended directory, potentially exposing sensitive system information. The issue stems from insufficient path validation in the `send_local_file` function. Exploiting this vulnerability could lead to unauthorized access to files, information disclosure, or in severe cases, remote code execution. The fix commit resolves this vulnerability by implementing proper path validation and using a more secure method to send files.", "cve": "PVE-2024-73194", "id": "pyup.io-73194", "more_info_path": "/vulnerabilities/PVE-2024-73194/73194", "specs": [ "<0.50.8" ], "v": "<0.50.8" }, { "advisory": "Affected versions of the weave package are vulnerable to Path Traversal due to insufficient input validation of file path parameters. The Weave server API\u2019s file-fetching endpoint constructs paths from unvalidated user-supplied input, enabling directory traversal beyond the intended directory and permitting arbitrary file access. An attacker with low-level privileges can exploit this by crafting requests to retrieve sensitive files\u2014such as configuration files or credentials\u2014potentially escalating to server admin privileges and compromising confidentiality, integrity, and availability.", "cve": "CVE-2024-7340", "id": "pyup.io-78754", "more_info_path": "/vulnerabilities/CVE-2024-7340/78754", "specs": [ "<0.50.8" ], "v": "<0.50.8" } ], "weaviate-client": [ { "advisory": "Weaviate-client fixes a vulnerability in the .graphql namespace methods of the weaviate.Client object. This issue has been present in affected versions, where backslash (\\) characters were not escaped appropriately. This flaw allowed for malicious plain-text strings in the .with_where method to query database-wide data, potentially leading to unauthorized data access.", "cve": "PVE-2024-71922", "id": "pyup.io-71922", "more_info_path": "/vulnerabilities/PVE-2024-71922/71922", "specs": [ "<3.26.5" ], "v": "<3.26.5" }, { "advisory": "Weaviate-client addresses a GQL injection vulnerability affecting the `.graphql` namespace methods of the `weaviate.Client` object from version v3.23.0 onward. The fix ensures that `\\` characters are properly escaped, preventing malicious plain-text strings in the `.with_where` method from querying database-wide data.", "cve": "PVE-2024-72347", "id": "pyup.io-72347", "more_info_path": "/vulnerabilities/PVE-2024-72347/72347", "specs": [ "<4.7.0" ], "v": "<4.7.0" } ], "web-py": [ { "advisory": "Web-py 0.21 prevents bad characters in headers. This is a security fix.", "cve": "PVE-2021-38615", "id": "pyup.io-38615", "more_info_path": "/vulnerabilities/PVE-2021-38615/38615", "specs": [ "<0.21" ], "v": "<0.21" }, { "advisory": "Web.py 0.21 prevents bad characters in headers.\r\nhttps://github.com/webpy/webpy/commit/a773a8491de1b15dca9792271d594387983160f3", "cve": "PVE-2022-45469", "id": "pyup.io-45469", "more_info_path": "/vulnerabilities/PVE-2022-45469/45469", "specs": [ "<0.21" ], "v": "<0.21" }, { "advisory": "Web-py before 0.23 did not support secure cookies.", "cve": "PVE-2021-38614", "id": "pyup.io-38614", "more_info_path": "/vulnerabilities/PVE-2021-38614/38614", "specs": [ "<0.23" ], "v": "<0.23" }, { "advisory": "Web-py 0.36 adds the `secure` option to a session.", "cve": "PVE-2021-38613", "id": "pyup.io-38613", "more_info_path": "/vulnerabilities/PVE-2021-38613/38613", "specs": [ "<0.36" ], "v": "<0.36" }, { "advisory": "Web.py 0.39 fixes a XSS vulnerability in the form module.\r\nhttps://github.com/webpy/webpy/commit/fa6646121d6d741efa838ff3662cdb501502643b", "cve": "PVE-2022-45466", "id": "pyup.io-45466", "more_info_path": "/vulnerabilities/PVE-2022-45466/45466", "specs": [ "<0.39" ], "v": "<0.39" }, { "advisory": "Web-py 0.39 fixes a security issue with the form module. Additionally, it fixes a security issue with the db module.", "cve": "PVE-2021-38612", "id": "pyup.io-38612", "more_info_path": "/vulnerabilities/PVE-2021-38612/38612", "specs": [ "<0.39" ], "v": "<0.39" }, { "advisory": "Web.py 0.39 fixes a injection vulnerability in the db module.\r\nhttps://github.com/webpy/webpy/commit/becbfb92d7601ddb0aededfdc9a91696bde2430f", "cve": "PVE-2022-45490", "id": "pyup.io-45490", "more_info_path": "/vulnerabilities/PVE-2022-45490/45490", "specs": [ "<0.39" ], "v": "<0.39" } ], "web2py": [ { "advisory": "web2py before 2.14.1, when using the standalone version, allows remote attackers to obtain environment variable values via a direct request to examples/template_examples/beautify. NOTE: this issue can be leveraged by remote attackers to gain administrative access.", "cve": "CVE-2016-3952", "id": "pyup.io-70561", "more_info_path": "/vulnerabilities/CVE-2016-3952/70561", "specs": [ "<2.14.1" ], "v": "<2.14.1" }, { "advisory": "The secure_load function in gluon/utils.py in web2py before 2.14.2 uses pickle.loads to deserialize session information stored in cookies, which might allow remote attackers to execute arbitrary code by leveraging knowledge of encryption_key.", "cve": "CVE-2016-3957", "id": "pyup.io-65861", "more_info_path": "/vulnerabilities/CVE-2016-3957/65861", "specs": [ "<2.14.2" ], "v": "<2.14.2" }, { "advisory": "The sample web application in web2py before 2.14.2 might allow remote attackers to execute arbitrary code via vectors involving use of a hardcoded encryption key when calling the session.connect function.", "cve": "CVE-2016-3953", "id": "pyup.io-65860", "more_info_path": "/vulnerabilities/CVE-2016-3953/65860", "specs": [ "<2.14.2" ], "v": "<2.14.2" }, { "advisory": "web2py before 2.14.2 allows remote attackers to obtain the session_cookie_key value via a direct request to examples/simple_examples/status. NOTE: this issue can be leveraged by remote attackers to execute arbitrary code using CVE-2016-3957.", "cve": "CVE-2016-3954", "id": "pyup.io-65833", "more_info_path": "/vulnerabilities/CVE-2016-3954/65833", "specs": [ "<2.14.2" ], "v": "<2.14.2" }, { "advisory": "web2py before 2.14.6 does not properly check if a host is denied before verifying passwords, allowing a remote attacker to perform brute-force attacks.", "cve": "CVE-2016-10321", "id": "pyup.io-65859", "more_info_path": "/vulnerabilities/CVE-2016-10321/65859", "specs": [ "<2.14.6" ], "v": "<2.14.6" }, { "advisory": "Web2py versions 2.14.5 and below was affected by Local File Inclusion vulnerability, which allows a malicious intended user to read/access web server sensitive files.", "cve": "CVE-2016-4806", "id": "pyup.io-70528", "more_info_path": "/vulnerabilities/CVE-2016-4806/70528", "specs": [ "<=2.14.5" ], "v": "<=2.14.5" }, { "advisory": "Web2py versions 2.14.5 and below was affected by Reflected XSS vulnerability, which allows an attacker to perform an XSS attack on logged in user (admin).", "cve": "CVE-2016-4807", "id": "pyup.io-70529", "more_info_path": "/vulnerabilities/CVE-2016-4807/70529", "specs": [ "<=2.14.5" ], "v": "<=2.14.5" }, { "advisory": "Web2py versions 2.14.5 and below was affected by CSRF (Cross Site Request Forgery) vulnerability, which allows an attacker to trick a logged in user to perform some unwanted actions i.e An attacker can trick an victim to disable the installed application just by sending a URL to victim.", "cve": "CVE-2016-4808", "id": "pyup.io-65834", "more_info_path": "/vulnerabilities/CVE-2016-4808/65834", "specs": [ "<=2.14.5" ], "v": "<=2.14.5" }, { "advisory": "A vulnerability in versions of web2py up to 2.24.1 involves an OS command injection risk when configured to use notifySendHandler for logging. This condition allows for the execution of arbitrary OS commands on the web server via specially crafted web requests.", "cve": "CVE-2023-45158", "id": "pyup.io-70381", "more_info_path": "/vulnerabilities/CVE-2023-45158/70381", "specs": [ "<=2.24.1" ], "v": "<=2.24.1" }, { "advisory": "Open redirect vulnerability in gluon/tools.py in Web2py 2.9.11 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the _next parameter to user/logout.", "cve": "CVE-2015-6961", "id": "pyup.io-65858", "more_info_path": "/vulnerabilities/CVE-2015-6961/65858", "specs": [ "==2.9.11" ], "v": "==2.9.11" }, { "advisory": "Open redirect vulnerability in web2py versions prior to 2.22.5 allows a remote attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having a user to access a specially crafted URL.", "cve": "CVE-2022-33146", "id": "pyup.io-54428", "more_info_path": "/vulnerabilities/CVE-2022-33146/54428", "specs": [ ">=0,<2.22.5" ], "v": ">=0,<2.22.5" }, { "advisory": "Open redirect vulnerability exists in web2py versions prior to 2.23.1. When using the tool, a web2py user may be redirected to an arbitrary website by accessing a specially crafted URL. As a result, the user may become a victim of a phishing attack.", "cve": "CVE-2023-22432", "id": "pyup.io-54662", "more_info_path": "/vulnerabilities/CVE-2023-22432/54662", "specs": [ ">=0,<2.23.1" ], "v": ">=0,<2.23.1" }, { "advisory": "Cross-site scripting (XSS) vulnerability in static/js/share.js (aka the social bookmarking widget) in Web2py before 2.3.1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.", "cve": "CVE-2013-2311", "id": "pyup.io-65832", "more_info_path": "/vulnerabilities/CVE-2013-2311/65832", "specs": [ ">=0,<2.3.2" ], "v": ">=0,<2.3.2" } ], "web3": [ { "advisory": "Web3 4.7.0 upgrades eth-hash to 0.2.0 with pycryptodome 3.6.6 which resolves a vulnerability.", "cve": "CVE-2018-15560", "id": "pyup.io-36480", "more_info_path": "/vulnerabilities/CVE-2018-15560/36480", "specs": [ "<4.7.0" ], "v": "<4.7.0" } ], "webappdirac": [ { "advisory": "Webappdirac 5.0.3 and 5.1.0a5 escape url parameters to avoid XSS vulnerabilities.\r\nhttps://github.com/DIRACGrid/WebAppDIRAC/pull/712", "cve": "PVE-2022-52475", "id": "pyup.io-52475", "more_info_path": "/vulnerabilities/PVE-2022-52475/52475", "specs": [ "<5.0.3", ">=5.1.0a1,<5.1.0a5" ], "v": "<5.0.3,>=5.1.0a1,<5.1.0a5" } ], "webargs": [ { "advisory": "webargs 5.1.3 fixes race condition between parallel requests when the cache is used. See: CVE-2019-9710.", "cve": "CVE-2019-9710", "id": "pyup.io-36963", "more_info_path": "/vulnerabilities/CVE-2019-9710/36963", "specs": [ "<5.1.3" ], "v": "<5.1.3" }, { "advisory": "Webargs 5.5.2 and 6.0.0b4 include a fix for CVE-2020-7965: Flaskparser.py in Webargs doesn't check that the Content-Type header is application/json when receiving JSON input. If the request body is valid JSON, it will accept it even if the content type is application/x-www-form-urlencoded. This allows for JSON POST requests to be made across domains, leading to CSRF.", "cve": "CVE-2020-7965", "id": "pyup.io-37684", "more_info_path": "/vulnerabilities/CVE-2020-7965/37684", "specs": [ ">=6.0.0b1,<=6.0.0b4", ">=5.0.0b1,<5.5.2" ], "v": ">=6.0.0b1,<=6.0.0b4,>=5.0.0b1,<5.5.2" } ], "webauthn-rp": [ { "advisory": "Webauthn-rp 0.0.10 updates its dependency 'cryptography' to v3.2 to include a security fix.", "cve": "CVE-2020-25659", "id": "pyup.io-40260", "more_info_path": "/vulnerabilities/CVE-2020-25659/40260", "specs": [ "<0.0.10" ], "v": "<0.0.10" } ], "webchanges": [ { "advisory": "Webchanges 3.10.2 fixes an unsafe permissions vulnerability. On Linux and macOS systems, now is checked that the hooks file and the directory it is located in are owned and writable by only the user who is running the job (and not by its group or by other users. An explanatory ImportWarning message is now issued if the permissions are not correct and the import of the hooks module is skipped.", "cve": "PVE-2022-49342", "id": "pyup.io-49342", "more_info_path": "/vulnerabilities/PVE-2022-49342/49342", "specs": [ "<3.10.2" ], "v": "<3.10.2" }, { "advisory": "Webchanges 3.7.0 and 3.7.1 introduce a new 'execute' filter to filter the data using an executable without invoking the shell (as 'shellpipe' does) and therefore exposing to additional security risks. Versions 3.7.0 and 3.7.1 also strengthen the security with 'bandit' to catch common security issues.", "cve": "PVE-2021-40868", "id": "pyup.io-40868", "more_info_path": "/vulnerabilities/PVE-2021-40868/40868", "specs": [ "<3.7.0" ], "v": "<3.7.0" } ], "webchecks": [ { "advisory": "Webchecks version 0.1.2 updates its `requests` dependency from version 2.31.0 to 2.32.0 to address the security vulnerability identified in CVE-2024-35195. This update ensures the package remains secure by mitigating the potential risks associated with the older version of the `requests` library.", "cve": "CVE-2024-35195", "id": "pyup.io-71079", "more_info_path": "/vulnerabilities/CVE-2024-35195/71079", "specs": [ "<0.1.2" ], "v": "<0.1.2" } ], "webcomix": [ { "advisory": "Webcomix v3.5.1 updates its dependency \"scrapy-splash\" to 0.8.0 to include a security fix.", "cve": "CVE-2021-41124", "id": "pyup.io-42063", "more_info_path": "/vulnerabilities/CVE-2021-41124/42063", "specs": [ "<3.5.1" ], "v": "<3.5.1" } ], "weblate": [ { "advisory": "In versions 2.0 to 2.13 of Weblate, a user may be allowed to modify their password, but the session credentials continue to be operational even after the password has been altered.", "cve": "PVE-2023-99946", "id": "pyup.io-60918", "more_info_path": "/vulnerabilities/PVE-2023-99946/60918", "specs": [ "<2.14" ], "v": "<2.14" }, { "advisory": "Weblate 2.14 includes a fix for a XSS vulnerability.", "cve": "PVE-2023-99945", "id": "pyup.io-60920", "more_info_path": "/vulnerabilities/PVE-2023-99945/60920", "specs": [ "<2.14" ], "v": "<2.14" }, { "advisory": "Weblate 2.14 includes a fix for a Content Spoofing vulnerability in error message.", "cve": "PVE-2023-99943", "id": "pyup.io-60922", "more_info_path": "/vulnerabilities/PVE-2023-99943/60922", "specs": [ "<2.14" ], "v": "<2.14" }, { "advisory": "Weblate 2.14 includes a fix for a Denial of Service vulnerability in weblate/accounts/forms.py.", "cve": "PVE-2023-99942", "id": "pyup.io-60923", "more_info_path": "/vulnerabilities/PVE-2023-99942/60923", "specs": [ "<2.14" ], "v": "<2.14" }, { "advisory": "Weblate 2.14 includes a fix for a CSV Injection vulnerability in the CSV export feature.", "cve": "PVE-2023-99944", "id": "pyup.io-60921", "more_info_path": "/vulnerabilities/PVE-2023-99944/60921", "specs": [ "<2.14" ], "v": "<2.14" }, { "advisory": "Weblate 4.11.1 includes a fix for CVE-2022-23915: The package weblate from 0 and before 4.11.1 are vulnerable to Remote Code Execution (RCE) via argument injection when using git or mercurial repositories. Authenticated users, can change the behavior of the application in an unintended way, leading to command execution.", "cve": "CVE-2022-23915", "id": "pyup.io-45558", "more_info_path": "/vulnerabilities/CVE-2022-23915/45558", "specs": [ "<4.11.1" ], "v": "<4.11.1" }, { "advisory": "Weblate versions up to 4.14.1 experienced an issue where the 'Remove Account' function had no rate limiting, which could lead to massive mailings. From version 4.14.2 onwards, this has been addressed by imposing limits on not only the number of activities executed, but also on the number of outgoing emails.", "cve": "PVE-2023-99940", "id": "pyup.io-60925", "more_info_path": "/vulnerabilities/PVE-2023-99940/60925", "specs": [ "<4.14.2" ], "v": "<4.14.2" }, { "advisory": "In versions of Weblate before 4.18, there's a flaw that allows one to log in without credentials after logging out, potentially causing sensitive data exposure.", "cve": "PVE-2023-99939", "id": "pyup.io-60926", "more_info_path": "/vulnerabilities/PVE-2023-99939/60926", "specs": [ "<4.18" ], "v": "<4.18" }, { "advisory": "Weblate 4.3 includes a fix for a CSRF vulnerability.", "cve": "PVE-2023-99941", "id": "pyup.io-60924", "more_info_path": "/vulnerabilities/PVE-2023-99941/60924", "specs": [ "<4.3" ], "v": "<4.3" }, { "advisory": "When creating a new component from an existing component that has a source code repository URL specified in settings, this URL is included in the client's URL parameters during the creation process. If, for example, the source code repository URL contains GitHub credentials, the confidential PAT and username are shown in plaintext and get saved into browser history. Moreover, if the request URL is logged, the credentials are written to the logs in plaintext.", "cve": "CVE-2025-32021", "id": "pyup.io-76767", "more_info_path": "/vulnerabilities/CVE-2025-32021/76767", "specs": [ "<5.11" ], "v": "<5.11" }, { "advisory": "Affected versions of this package are vulnerable to Brute Force attacks due to the absence of rate limiting on the second-factor authentication endpoint. The two-factor authentication verification mechanism fails to implement proper rate-limiting controls, leading to automated OTP (One-Time Password) guessing attacks. An attacker with valid primary credentials can exploit this vulnerability by systematically attempting to guess the second authentication factor through automated requests without being throttled or blocked.", "cve": "CVE-2025-47951", "id": "pyup.io-77738", "more_info_path": "/vulnerabilities/CVE-2025-47951/77738", "specs": [ "<5.12" ], "v": "<5.12" }, { "advisory": "Affected versions of this package are vulnerable to Information Disclosure due to insufficient sanitization of sensitive data in audit log notifications sent via email. The notification system fails to anonymize IP addresses before including them in email communications, leading to exposure of users' personal IP addresses to third-party systems.", "cve": "CVE-2025-49134", "id": "pyup.io-77739", "more_info_path": "/vulnerabilities/CVE-2025-49134/77739", "specs": [ "<5.12" ], "v": "<5.12" }, { "advisory": "Affected versions of the Weblate package are vulnerable to Authentication Bypass due to excessive session expiry duration during second-factor verification. The two-factor authentication verification process maintains sessions with inappropriately long expiration times, which undermines the rate-limiting mechanisms designed to prevent brute force attacks on the second authentication factor.", "cve": "CVE-2025-58352", "id": "pyup.io-79192", "more_info_path": "/vulnerabilities/CVE-2025-58352/79192", "specs": [ "<5.13.1" ], "v": "<5.13.1" }, { "advisory": "Affected versions of the Weblate package are vulnerable to Information Disclosure due to audit log entries exposing the inviter\u2019s IP address to invited users. The AuditLogManager.create() logic in weblate/accounts/models.py recorded IP addresses for admin-triggered actions such as sending an invitation, and those entries were visible via the project audit log, allowing the invitee to see the inviter\u2019s address. An invited user can view the project\u2019s audit log to obtain the inviting member\u2019s IP address.", "cve": "CVE-2025-64326", "id": "pyup.io-81289", "more_info_path": "/vulnerabilities/CVE-2025-64326/81289", "specs": [ "<5.14.1" ], "v": "<5.14.1" }, { "advisory": "Affected versions of the Weblate package are vulnerable to Improper Input Validation due to insufficient validation of webhook payload fields used for repository matching. In weblate/trans/views/hooks.py, the ServiceHookView.post() webhook handler accepts a user-controlled full_name value and can fall back to overly broad matching when that value is blank or malformed (the fix introduces validate_full_name() checks and also guards bitbucket_hook_helper()).", "cve": "CVE-2025-67492", "id": "pyup.io-82836", "more_info_path": "/vulnerabilities/CVE-2025-67492/82836", "specs": [ "<5.15" ], "v": "<5.15" }, { "advisory": "Affected versions of the Weblate package are vulnerable to Information Disclosure due to broken authorization checks in REST API resources that expose user-related data (IDOR). In particular, the REST API user management views in weblate/api/views.py (including UserViewSet permission handling and the user notifications route referenced as api:user-notifications) did not consistently enforce the intended access controls for listing users and accessing notification settings.", "cve": "CVE-2025-67715", "id": "pyup.io-82835", "more_info_path": "/vulnerabilities/CVE-2025-67715/82835", "specs": [ "<5.15" ], "v": "<5.15" }, { "advisory": "Affected versions of the Weblate package are vulnerable to Improper Input Validation due to the absence of validation logic in the invitation acceptance workflow. The accept invitation functionality in Weblate fails to properly validate which user opened an invitation before allowing its acceptance, allowing a logged-in user to accept an invitation that another user opened.", "cve": "CVE-2025-64725", "id": "pyup.io-82723", "more_info_path": "/vulnerabilities/CVE-2025-64725/82723", "specs": [ "<5.15" ], "v": "<5.15" }, { "advisory": "Affected versions of the Weblate package are vulnerable to Remote Code Execution due to improper validation of user-controlled file paths that can overwrite Git configuration. Weblate\u2019s file-handling path checks in weblate/utils/validators.py did not reliably reject prohibited paths such as .git/config, allowing an attacker-supplied filename to target Git metadata and modify repository configuration used by Weblate\u2019s VCS operations.", "cve": "CVE-2025-68398", "id": "pyup.io-83153", "more_info_path": "/vulnerabilities/CVE-2025-68398/83153", "specs": [ "<5.15.1" ], "v": "<5.15.1" }, { "advisory": "Affected versions of the Weblate package are vulnerable to Path Traversal due to improper symbolic link validation when accessing repository files. The download_file() function in weblate/api/views.py and the download_translation_file() and zip_download() functions in weblate/utils/views.py can read and package file paths derived from component repositories without reliably rejecting os.path.islink() targets or enforcing that resolved paths remain within the repository root.", "cve": "CVE-2025-68279", "id": "pyup.io-83152", "more_info_path": "/vulnerabilities/CVE-2025-68279/83152", "specs": [ "<5.15.1" ], "v": "<5.15.1" }, { "advisory": "Affected versions of the Weblate package are vulnerable to Information Disclosure due to screenshot images being served without proper access control. Weblate\u2019s screenshot assets were exposed via direct static media URLs (for example, using image.url/MEDIA_URL) rather than being routed through permission-enforcing code in weblate/screenshots/views.py, allowing access checks (such as those in screenshot-related views) to be bypassed.", "cve": "CVE-2026-21889", "id": "pyup.io-84468", "more_info_path": "/vulnerabilities/CVE-2026-21889/84468", "specs": [ "<5.15.2" ], "v": "<5.15.2" }, { "advisory": "The password reset form in Weblate before 2.10.1 provides different error messages depending on whether the email address is associated with an account, which allows remote attackers to enumerate user accounts via a series of requests.", "cve": "CVE-2017-5537", "id": "pyup.io-53958", "more_info_path": "/vulnerabilities/CVE-2017-5537/53958", "specs": [ ">=0,<2.10.1" ], "v": ">=0,<2.10.1" }, { "advisory": "Weblate is a copyleft software web-based continuous localization system. Versions prior to 4.11 do not properly neutralize user input used in user name and language fields. Due to this improper neutralization it is possible to perform cross-site scripting via these fields. The issues were fixed in the 4.11 release. Users unable to upgrade are advised to add their own neutralize logic.", "cve": "CVE-2022-24710", "id": "pyup.io-54321", "more_info_path": "/vulnerabilities/CVE-2022-24710/54321", "specs": [ ">=0,<4.11" ], "v": ">=0,<4.11" }, { "advisory": "Weblate affected versions didn't correctly validate filenames when restoring the project back up. It may be possible to gain unauthorized access to files on the server using a crafted ZIP file. As a workaround, do not allow untrusted users to create projects.", "cve": "CVE-2024-39303", "id": "pyup.io-72087", "more_info_path": "/vulnerabilities/CVE-2024-39303/72087", "specs": [ ">=4.14,<5.6.2" ], "v": ">=4.14,<5.6.2" } ], "webob": [ { "advisory": "The WebOb affected versions have a critical security vulnerability related to improper handling of the HTTP Location header during URL redirection. The issue arises when WebOb normalizes the Location header by combining the request's hostname with the destination URL using Python's `urlparse` and `urljoin` functions. If the destination URL begins with \"//\", `urlparse` interprets it as a URI without a scheme, using the following string as the hostname. Consequently, `urljoin` replaces the original request hostname with this new hostname, potentially redirecting users to a malicious site. This vulnerability could allow attackers to craft URLs that redirect users from trusted domains to malicious sites, posing significant security risks. The WebOb update ensures that such scenarios are handled correctly, preventing unintended redirects and securing the application against this attack.", "cve": "CVE-2024-42353", "id": "pyup.io-72631", "more_info_path": "/vulnerabilities/CVE-2024-42353/72631", "specs": [ "<1.8.8" ], "v": "<1.8.8" } ], "webp": [ { "advisory": "Webp 1.0.1 adds further security related hardening in libwebp & libwebpmux.", "cve": "PVE-2021-36726", "id": "pyup.io-36726", "more_info_path": "/vulnerabilities/PVE-2021-36726/36726", "specs": [ "<0.1.2" ], "v": "<0.1.2" }, { "advisory": "Webp 0.3.0 bundles 'libwebp' 1.3.2 (formerly 1.0.3) to address CVE-2023-4863, a high-risk vulnerability.\r\nhttps://github.com/anibali/pywebp/security/advisories/GHSA-f9pm-4g9p-6vm3", "cve": "CVE-2023-4863", "id": "pyup.io-61640", "more_info_path": "/vulnerabilities/CVE-2023-4863/61640", "specs": [ "<0.3.0" ], "v": "<0.3.0" } ], "webptools": [ { "advisory": "Webptools 0.0.9 and prior releases ship with C library 'libwebp' version 1.1.0, which is affected by a high-risk vulnerability.\r\nhttps://github.com/scionoftech/webptools/blob/master/lib/version_info.txt", "cve": "CVE-2023-4863", "id": "pyup.io-61583", "more_info_path": "/vulnerabilities/CVE-2023-4863/61583", "specs": [ "<=0.0.9" ], "v": "<=0.0.9" }, { "advisory": "Webptools is vulnerable to shell command injection in filename or options due to lack of validation.\r\nhttps://github.com/scionoftech/webptools/issues/4", "cve": "PVE-2023-61582", "id": "pyup.io-61582", "more_info_path": "/vulnerabilities/PVE-2023-61582/61582", "specs": [ "<=0.0.9" ], "v": "<=0.0.9" } ], "webscrapbook": [ { "advisory": "Webscrapbook 0.20.0 added content security policy restriction for served web pages. They can no longer send AJAX requests and form actions to prevent a potential attack. A config `app.content_security_policy` is added to change the behavior.", "cve": "PVE-2021-38854", "id": "pyup.io-38854", "more_info_path": "/vulnerabilities/PVE-2021-38854/38854", "specs": [ "<0.20.0" ], "v": "<0.20.0" }, { "advisory": "Webscrapbook 0.27.0 dropped support of JavaScript when viewing a page archive, due to a security concern.", "cve": "PVE-2021-38853", "id": "pyup.io-38853", "more_info_path": "/vulnerabilities/PVE-2021-38853/38853", "specs": [ "<0.27.0" ], "v": "<0.27.0" }, { "advisory": "Webscrapbook 0.39.0 fixes a security issue that may allow the user to access any directory on Windows.", "cve": "PVE-2021-40219", "id": "pyup.io-40219", "more_info_path": "/vulnerabilities/PVE-2021-40219/40219", "specs": [ "<0.39.0" ], "v": "<0.39.0" }, { "advisory": "Affected versions of WebScrapBook, a backend toolkit for managing WebScrapBook collections, are susceptible to Directory Traversal through exploitation of the localpath parameter. This vulnerability could allow unauthorized access to file systems by navigating the directory structure outside of the intended web directory.", "cve": "PVE-2024-99828", "id": "pyup.io-65601", "more_info_path": "/vulnerabilities/PVE-2024-99828/65601", "specs": [ ">=0,<0.39.0" ], "v": ">=0,<0.39.0" } ], "websockets": [ { "advisory": "Websockets 10.0 includes a fix for a DoS vulnerability.\r\nhttps://github.com/aaugustin/websockets/commit/0a935b8ec16f4430ffe638cdbfbe45f6f9d7f684", "cve": "PVE-2022-50473", "id": "pyup.io-50473", "more_info_path": "/vulnerabilities/PVE-2022-50473/50473", "specs": [ "<10.0" ], "v": "<10.0" }, { "advisory": "Websockets 5.0 includes a fix for CVE-2018-1000518: aaugustin websockets version 4 contains a CWE-409 -Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Servers and clients, unless configured with compression=None that can result in Denial of Service by memory exhaustion. This attack appear to be exploitable via sending a specially crafted frame on an established connection.\r\nhttps://github.com/aaugustin/websockets/pull/407", "cve": "CVE-2018-1000518", "id": "pyup.io-42249", "more_info_path": "/vulnerabilities/CVE-2018-1000518/42249", "specs": [ ">=4.0.0,<5.0.0" ], "v": ">=4.0.0,<5.0.0" }, { "advisory": "Websockets before 9.1 has an Observable Timing Discrepancy on servers when HTTP Basic Authentication is enabled with basic_auth_protocol_factory(credentials=...). An attacker may be able to guess a password via a timing attack.", "cve": "CVE-2021-33880", "id": "pyup.io-40622", "more_info_path": "/vulnerabilities/CVE-2021-33880/40622", "specs": [ ">=8.0,<9.1" ], "v": ">=8.0,<9.1" } ], "webssh": [ { "advisory": "Webssh 0.7.3 stops storing plaintext passwords in local storage.", "cve": "PVE-2022-48411", "id": "pyup.io-48411", "more_info_path": "/vulnerabilities/PVE-2022-48411/48411", "specs": [ "<0.7.3" ], "v": "<0.7.3" }, { "advisory": "Affected versions of the webssh package are vulnerable to Cross-site Scripting (XSS) due to improper neutralization of the hostname and port parameters on the login page. The login page renders these user-controlled query parameters without adequate HTML escaping, allowing attacker-supplied script to be reflected into the page context.", "cve": "CVE-2025-7885", "id": "pyup.io-81130", "more_info_path": "/vulnerabilities/CVE-2025-7885/81130", "specs": [ "<1.6.3" ], "v": "<1.6.3" } ], "weixin-python": [ { "advisory": "Weixin-python 0.5.5 includes a fix for CVE-2018-25082: This issue affects the function validate/to_xml. The manipulation leads to xml external entity reference. The attack may be initiated remotely.", "cve": "CVE-2018-25082", "id": "pyup.io-53781", "more_info_path": "/vulnerabilities/CVE-2018-25082/53781", "specs": [ "<0.5.5" ], "v": "<0.5.5" } ], "werkzeug": [ { "advisory": "Cross-site scripting (XSS) vulnerability in the render_full function in debug/tbtools.py in the debugger in Pallets Werkzeug before 0.11.11 (as used in Pallets Flask and other products) allows remote attackers to inject arbitrary web script or HTML via a field that contains an exception message.", "cve": "CVE-2016-10516", "id": "pyup.io-35661", "more_info_path": "/vulnerabilities/CVE-2016-10516/35661", "specs": [ "<0.11.11" ], "v": "<0.11.11" }, { "advisory": "Werkzeug before 0.11.6 includes an open redirect vulnerability via a double slash in the URL. See CVE-2020-28724.", "cve": "CVE-2020-28724", "id": "pyup.io-39160", "more_info_path": "/vulnerabilities/CVE-2020-28724/39160", "specs": [ "<0.11.6" ], "v": "<0.11.6" }, { "advisory": "The defaults of 'generate_password_hash' in werkzeug 0.12 have been changed to more secure ones.\r\nhttps://github.com/pallets/werkzeug/pull/753", "cve": "PVE-2021-26435", "id": "pyup.io-26435", "more_info_path": "/vulnerabilities/PVE-2021-26435/26435", "specs": [ "<0.12" ], "v": "<0.12" }, { "advisory": "Werkzeug 0.3.1 prevents a timing attack against 'werkzeug.contrib.SecureCookie'.\r\nhttps://github.com/pallets/werkzeug/commit/3b1cb999459f564c8d2cc15063f878e381d0d355", "cve": "PVE-2021-26428", "id": "pyup.io-26428", "more_info_path": "/vulnerabilities/PVE-2021-26428/26428", "specs": [ "<0.3.1" ], "v": "<0.3.1" }, { "advisory": "werkzeug before 0.8 allowed newlines in the header datastructure, allowing header injection attacks.", "cve": "PVE-2021-26175", "id": "pyup.io-26175", "more_info_path": "/vulnerabilities/PVE-2021-26175/26175", "specs": [ "<0.8" ], "v": "<0.8" }, { "advisory": "Werkzeug 0.8.3 fixes an XSS problem with redirect targets coming from untrusted sources.\r\nhttps://github.com/pallets/werkzeug/commit/7b8d887d33c768a77f40dd15ff5ac6ebbbab25b9", "cve": "PVE-2021-26427", "id": "pyup.io-26427", "more_info_path": "/vulnerabilities/PVE-2021-26427/26427", "specs": [ "<0.8.3" ], "v": "<0.8.3" }, { "advisory": "Werkzeug 2.2.3 includes a fix for CVE-2023-25577: Prior to version 2.2.3, Werkzeug's multipart form data parser will parse an unlimited number of parts, including file parts. Parts can be a small amount of bytes, but each requires CPU time to parse and may use more memory as Python data. If a request can be made to an endpoint that accesses 'request.data', 'request.form', 'request.files', or 'request.get_data(parse_form_data=False)', it can cause unexpectedly high resource usage. This allows an attacker to cause a denial of service by sending crafted multipart data to an endpoint that will parse it. The amount of CPU time required can block worker processes from handling legitimate requests. The amount of RAM required can trigger an out of memory kill of the process. Unlimited file parts can use up memory and file handles. If many concurrent requests are sent continuously, this can exhaust or kill all available workers.\r\nhttps://github.com/pallets/werkzeug/security/advisories/GHSA-xg9f-g7g7-2323", "cve": "CVE-2023-25577", "id": "pyup.io-53325", "more_info_path": "/vulnerabilities/CVE-2023-25577/53325", "specs": [ "<2.2.3" ], "v": "<2.2.3" }, { "advisory": "Werkzeug 2.2.3 includes a fix for CVE-2023-23934: Browsers may allow \"nameless\" cookies that look like '=value' instead of 'key=value'. A vulnerable browser may allow a compromised application on an adjacent subdomain to exploit this to set a cookie like '=__Host-test=bad' for another subdomain. Werkzeug prior to 2.2.3 will parse the cookie '=__Host-test=bad' as __Host-test=bad'. If a Werkzeug application is running next to a vulnerable or malicious subdomain which sets such a cookie using a vulnerable browser, the Werkzeug application will see the bad cookie value but the valid cookie key.\r\nhttps://github.com/pallets/werkzeug/security/advisories/GHSA-px8h-6qxv-m22q", "cve": "CVE-2023-23934", "id": "pyup.io-53326", "more_info_path": "/vulnerabilities/CVE-2023-23934/53326", "specs": [ "<2.2.3" ], "v": "<2.2.3" }, { "advisory": "Werkzeug is a comprehensive WSGI web application library. The debugger in affected versions of Werkzeug can allow an attacker to execute code on a developer's machine under some circumstances. This requires the attacker to get the developer to interact with a domain and subdomain they control, and enter the debugger PIN, but if they are successful it allows access to the debugger even if it is only running on localhost. This also requires the attacker to guess a URL in the developer's application that will trigger the debugger.", "cve": "CVE-2024-34069", "id": "pyup.io-71594", "more_info_path": "/vulnerabilities/CVE-2024-34069/71594", "specs": [ "<3.0.3" ], "v": "<3.0.3" }, { "advisory": "Affected versions of Werkzeug are potentially vulnerable to resource exhaustion when parsing file data in forms. Applications using 'werkzeug.formparser.MultiPartParser' to parse 'multipart/form-data' requests (e.g. all flask applications) are vulnerable to a relatively simple but effective resource exhaustion (denial of service) attack. A specifically crafted form submission request can cause the parser to allocate and block 3 to 8 times the upload size in main memory. There is no upper limit; a single upload at 1 Gbit/s can exhaust 32 GB of RAM in less than 60 seconds.", "cve": "CVE-2024-49767", "id": "pyup.io-73889", "more_info_path": "/vulnerabilities/CVE-2024-49767/73889", "specs": [ "<3.0.6" ], "v": "<3.0.6" }, { "advisory": "Affected versions of Werkzeug are vulnerable to Path Traversal (CWE-22) on Windows systems running Python versions below 3.11. The safe_join() function failed to properly detect certain absolute paths on Windows, allowing attackers to potentially access files outside the intended directory. An attacker could craft special paths starting with \"/\" that bypass the directory restrictions on Windows systems. The vulnerability exists in the safe_join() function which relied solely on os.path.isabs() for path validation. This is exploitable on Windows systems by passing paths starting with \"/\" to safe_join(). To remediate, upgrade to the latest version which includes additional path validation checks. \r\nNOTE: This vulnerability specifically affects Windows systems running Python versions below 3.11 where ntpath.isabs() behavior differs.", "cve": "CVE-2024-49766", "id": "pyup.io-73969", "more_info_path": "/vulnerabilities/CVE-2024-49766/73969", "specs": [ "<3.0.6" ], "v": "<3.0.6" }, { "advisory": "Affected versions of the Werkzeug package are vulnerable to Denial of Service (DoS) due to improper handling of Windows special device names in the safe_join function. In Werkzeug versions before 3.1.4, safe_join permits path segments such as \u201cCON\u201d or \u201cAUX\u201d to pass validation, allowing send_from_directory to construct a path that resolves to a Windows device file, which opens successfully but then blocks indefinitely when read.", "cve": "CVE-2025-66221", "id": "pyup.io-82196", "more_info_path": "/vulnerabilities/CVE-2025-66221/82196", "specs": [ "<3.1.4" ], "v": "<3.1.4" }, { "advisory": "Affected versions of the Werkzeug package are vulnerable to Improper Handling of Windows Device Names due to incomplete validation of Windows reserved device names in user-controlled path segments. In werkzeug.security.safe_join, path components ending with special device names (for example CON or AUX) are not reliably rejected when they include compound extensions (for example CON.txt.html) or trailing spaces, and werkzeug.utils.send_from_directory relies on safe_join when resolving a requested filename.", "cve": "CVE-2026-21860", "id": "pyup.io-84324", "more_info_path": "/vulnerabilities/CVE-2026-21860/84324", "specs": [ "<3.1.5" ], "v": "<3.1.5" }, { "advisory": "Werkzeug is a comprehensive WSGI web application library. If an upload of a file that starts with CR or LF and then is followed by megabytes of data without these characters: all of these bytes are appended chunk by chunk into internal bytearray and lookup for boundary is performed on growing buffer. This allows an attacker to cause a denial of service by sending crafted multipart data to an endpoint that will parse it. The amount of CPU time required can block worker processes from handling legitimate requests.", "cve": "CVE-2023-46136", "id": "pyup.io-71595", "more_info_path": "/vulnerabilities/CVE-2023-46136/71595", "specs": [ "<=2.3.7", ">=3.0.0,<3.0.1" ], "v": "<=2.3.7,>=3.0.0,<3.0.1" }, { "advisory": "Werkzeug 3.0.1 and 2.3.8 include a security fix: Slow multipart parsing for large parts potentially enabling DoS attacks.\r\nhttps://github.com/pallets/werkzeug/commit/b1916c0c083e0be1c9d887ee2f3d696922bfc5c1", "cve": "PVE-2023-62019", "id": "pyup.io-62019", "more_info_path": "/vulnerabilities/PVE-2023-62019/62019", "specs": [ "==3.0.0", "<2.3.8" ], "v": "==3.0.0,<2.3.8" }, { "advisory": "This vulnerability occurs in certain versions of werkzeug where an attacker can initiate Cross-site Scripting (XSS) attacks using the plaintext variable on the debug page.", "cve": "PVE-2024-99827", "id": "pyup.io-65602", "more_info_path": "/vulnerabilities/PVE-2024-99827/65602", "specs": [ ">=0,<0.11.11" ], "v": ">=0,<0.11.11" }, { "advisory": "Pallets Werkzeug before 0.15.3, when used with Docker, has insufficient debugger PIN randomness because Docker containers share the same machine id.", "cve": "CVE-2019-14806", "id": "pyup.io-54681", "more_info_path": "/vulnerabilities/CVE-2019-14806/54681", "specs": [ ">=0,<0.15.3" ], "v": ">=0,<0.15.3" }, { "advisory": "In Pallets Werkzeug before 0.15.5, SharedDataMiddleware mishandles drive names (such as C:) in Windows pathnames.", "cve": "CVE-2019-14322", "id": "pyup.io-54148", "more_info_path": "/vulnerabilities/CVE-2019-14322/54148", "specs": [ ">=0,<0.15.5" ], "v": ">=0,<0.15.5" }, { "advisory": "Werkzeug 0.15.5 includes a fix for an information disclosure vulnerability.\r\nhttps://github.com/pallets/werkzeug/pull/1592", "cve": "PVE-2021-37276", "id": "pyup.io-37276", "more_info_path": "/vulnerabilities/PVE-2021-37276/37276", "specs": [ ">=0.15.0,<0.15.5" ], "v": ">=0.15.0,<0.15.5" } ], "wger": [ { "advisory": "Cross Site Request Forgery (CSRF) vulnerability in wger Project wger Workout Manager 2.2.0a3 allows a remote attacker to gain privileges via the user-management feature in the gym/views/gym.py, templates/gym/reset_user_password.html, templates/user/overview.html, core/views/user.py, and templates/user/preferences.html, core/forms.py components.", "cve": "CVE-2023-38759", "id": "pyup.io-64997", "more_info_path": "/vulnerabilities/CVE-2023-38759/64997", "specs": [ "<=2.2.0a3" ], "v": "<=2.2.0a3" }, { "advisory": "Cross Site Scripting vulnerability in wger Project wger Workout Manager v.2.2.0a3 allows a remote attacker to gain privileges via the license_author field in the add-ingredient function in the templates/ingredients/view.html, models/ingredients.py, and views/ingredients.py components.", "cve": "CVE-2023-38758", "id": "pyup.io-64996", "more_info_path": "/vulnerabilities/CVE-2023-38758/64996", "specs": [ "<=2.2.0a3" ], "v": "<=2.2.0a3" }, { "advisory": "Wger software before 1.7 is susceptible to Denial-of-Service (DoS) attacks due to the lack of limit checks on CSV file uploads. This vulnerability allows attackers to upload large files, causing the server to exhaust resources while processing these files, thus making the service unavailable to legitimate users.", "cve": "PVE-2024-99765", "id": "pyup.io-66673", "more_info_path": "/vulnerabilities/PVE-2024-99765/66673", "specs": [ ">=0,<1.7" ], "v": ">=0,<1.7" }, { "advisory": "Improper Restriction of Excessive Authentication Attempts in GitHub repository wger-project/wger prior to 2.2.", "cve": "CVE-2022-2650", "id": "pyup.io-54581", "more_info_path": "/vulnerabilities/CVE-2022-2650/54581", "specs": [ ">=0,<2.2" ], "v": ">=0,<2.2" } ], "whatsapp-chat-exporter": [ { "advisory": "The Whatsapp-Chat-Exporter contains a security flaw due to inadequate sanitization of input during the production of a web page, which could result in Cross-site Scripting (XSS).", "cve": "PVE-2023-99924", "id": "pyup.io-61950", "more_info_path": "/vulnerabilities/PVE-2023-99924/61950", "specs": [ "<0.9.5" ], "v": "<0.9.5" }, { "advisory": "Whatsapp-chat-exporter 0.9.5 includes a fix for a XSS vulnerability.\r\nhttps://github.com/KnugiHK/WhatsApp-Chat-Exporter/commit/032af6cdcf3377e2736badaaaee36fdc91673be5", "cve": "PVE-2023-59192", "id": "pyup.io-59192", "more_info_path": "/vulnerabilities/PVE-2023-59192/59192", "specs": [ "<0.9.5" ], "v": "<0.9.5" }, { "advisory": "Versions of whatsapp-chat-exporter, a tool for parsing WhatsApp databases into HTML and JSON formats, are susceptible to Cross-site Scripting (XSS) because of inadequate sanitization of user input in the HTML chat outputs. This vulnerability arises because the Jinja template engine's auto-escape function, intended to prevent XSS, was not correctly implemented\u2014the environment was set without `autoescape=True`. Although the risk is considered low since the HTML output is viewed offline, there remains a potential for attackers to inject harmful payloads into chats via WhatsApp.", "cve": "PVE-2024-99826", "id": "pyup.io-65603", "more_info_path": "/vulnerabilities/PVE-2024-99826/65603", "specs": [ ">=0,<0.9.5" ], "v": ">=0,<0.9.5" } ], "wheel": [ { "advisory": "Wheel 0.38.1 includes a fix for CVE-2022-40898: An issue discovered in Python Packaging Authority (PyPA) Wheel 0.37.1 and earlier allows remote attackers to cause a denial of service via attacker controlled input to wheel cli.\r\nhttps://pyup.io/posts/pyup-discovers-redos-vulnerabilities-in-top-python-packages", "cve": "CVE-2022-40898", "id": "pyup.io-51499", "more_info_path": "/vulnerabilities/CVE-2022-40898/51499", "specs": [ "<0.38.1" ], "v": "<0.38.1" }, { "advisory": "Affected versions of the wheel package are vulnerable to Path Traversal due to applying extracted file permissions using an unsanitized archive pathname. The vulnerable logic is in wheel.cli.unpack.unpack (and setuptools._vendor.wheel.cli.unpack.unpack), where the code calls wf.extract(zinfo, destination) but then performs destination.joinpath(zinfo.filename).chmod(permissions) using zinfo.filename directly, allowing dot-dot-slash sequences to escape the intended directory.", "cve": "CVE-2026-24049", "id": "pyup.io-84961", "more_info_path": "/vulnerabilities/CVE-2026-24049/84961", "specs": [ "<0.46.2" ], "v": "<0.46.2" } ], "whispers": [ { "advisory": "Whispers 1.3.9 updates its dependency 'lxml' to v4.6.2 to include a security fix.", "cve": "CVE-2020-27783", "id": "pyup.io-39466", "more_info_path": "/vulnerabilities/CVE-2020-27783/39466", "specs": [ "<1.3.9" ], "v": "<1.3.9" } ], "whist-server": [ { "advisory": "Whist-server 0.1.0 updates its dependency 'fastapi' to v0.65.2 to include a security fix.", "cve": "CVE-2021-32677", "id": "pyup.io-44803", "more_info_path": "/vulnerabilities/CVE-2021-32677/44803", "specs": [ "<0.1.0" ], "v": "<0.1.0" }, { "advisory": "Whist-server 0.2.0 secures routes which shouldn't be available without authentication.\r\nhttps://github.com/Whist-Team/Whist-Server/pull/262", "cve": "PVE-2022-49683", "id": "pyup.io-49683", "more_info_path": "/vulnerabilities/PVE-2022-49683/49683", "specs": [ "<0.2.0" ], "v": "<0.2.0" } ], "whitenoise": [ { "advisory": "Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows.\r\nhttps://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6", "cve": "PVE-2021-37275", "id": "pyup.io-37275", "more_info_path": "/vulnerabilities/PVE-2021-37275/37275", "specs": [ "<4.1.3" ], "v": "<4.1.3" } ], "whoisit": [ { "advisory": "Whoisit 2.6.0 defaults to skip unsafe (HTTP) RDAP endpoints.\r\nhttps://github.com/meeb/whoisit/commit/9f954d8289ecda30c39f5b46fde1837568be0a93", "cve": "PVE-2022-49792", "id": "pyup.io-49792", "more_info_path": "/vulnerabilities/PVE-2022-49792/49792", "specs": [ "<2.6.0" ], "v": "<2.6.0" } ], "whoogle-search": [ { "advisory": "Whoogle-search 0.7.2 patches a XSS vulnerability on the Whoogle error template.", "cve": "PVE-2022-48297", "id": "pyup.io-48297", "more_info_path": "/vulnerabilities/PVE-2022-48297/48297", "specs": [ "<0.7.2" ], "v": "<0.7.2" }, { "advisory": "Whoogle-search 0.7.2 includes a fix for CVE-2022-25303: Cross-site Scripting (XSS) via the query string parameter q. error_message() is rendered using the | safe filter, meaning the user input is not escaped.", "cve": "CVE-2022-25303", "id": "pyup.io-50116", "more_info_path": "/vulnerabilities/CVE-2022-25303/50116", "specs": [ "<0.7.2" ], "v": "<0.7.2" }, { "advisory": "Whoogle-search 0.7.2 updates its Python image to python:3.11.0a5-alpine to include a security fix.", "cve": "CVE-2022-23990", "id": "pyup.io-48299", "more_info_path": "/vulnerabilities/CVE-2022-23990/48299", "specs": [ "<0.7.2" ], "v": "<0.7.2" }, { "advisory": "Whoogle-search 0.7.2 fixes an issue where 307 redirected on HTTP and not HTTPS.", "cve": "PVE-2022-48300", "id": "pyup.io-48300", "more_info_path": "/vulnerabilities/PVE-2022-48300/48300", "specs": [ "<0.7.2" ], "v": "<0.7.2" }, { "advisory": "Whoogle Search is a self-hosted metasearch engine. In versions 0.8.3 and prior, the `window` endpoint does not sanitize user-supplied input from the `location` variable and passes it to the `send` method which sends a `GET` request on lines 339-343 in `request.py,` which leads to a server-side request forgery. This issue allows for crafting GET requests to internal and external resources on behalf of the server. For example, this issue would allow for accessing resources on the internal network that the server has access to, even though these resources may not be accessible on the internet. This issue is fixed in version 0.8.4.", "cve": "CVE-2024-22205", "id": "pyup.io-66720", "more_info_path": "/vulnerabilities/CVE-2024-22205/66720", "specs": [ "<0.8.4" ], "v": "<0.8.4" }, { "advisory": "Whoogle Search is a self-hosted metasearch engine. In versions 0.8.3 and prior, the `element` method in `app/routes.py` does not validate the user-controlled `src_type` and `element_url` variables and passes them to the `send` method which sends a `GET` request on lines 339-343 in `requests.py`. The returned contents of the URL are then passed to and reflected back to the user in the `send_file` function on line 484, together with the user-controlled `src_type`, which allows the attacker to control the HTTP response content type leading to a cross-site scripting vulnerability. An attacker could craft a special URL to point to a malicious website and send the link to a victim. The fact that the link would contain a trusted domain (e.g. from one of public Whoogle instances) could be used to trick the user into clicking the link. The malicious website could, for example, be a copy of a real website, meant to steal a person\u2019s credentials to the website, or trick that person in another way. Version 0.8.4 contains a patch for this issue.", "cve": "CVE-2024-22417", "id": "pyup.io-66719", "more_info_path": "/vulnerabilities/CVE-2024-22417/66719", "specs": [ "<0.8.4" ], "v": "<0.8.4" }, { "advisory": "Whoogle Search is a self-hosted metasearch engine. In versions prior to 0.8.4, the `element` method in `app/routes.py` does not validate the user-controlled `src_type` and `element_url` variables and passes them to the `send` method which sends a GET request on lines 339-343 in `request.py`, which leads to a server-side request forgery. This issue allows for crafting GET requests to internal and external resources on behalf of the server. For example, this issue would allow for accessing resources on the internal network that the server has access to, even though these resources may not be accessible on the internet. This issue is fixed in version 0.8.4.", "cve": "CVE-2024-22203", "id": "pyup.io-70405", "more_info_path": "/vulnerabilities/CVE-2024-22203/70405", "specs": [ "<0.8.4" ], "v": "<0.8.4" }, { "advisory": "Whoogle-search 0.8.4 fixes a potential vulnerability where an element or window endpoint could retrieve file contents from a service hosted on another port.\r\nhttps://github.com/benbusby/whoogle-search/commit/3a2e0b262e4a076a20416b45e6b6f23fd265aeda", "cve": "PVE-2023-62133", "id": "pyup.io-62133", "more_info_path": "/vulnerabilities/PVE-2023-62133/62133", "specs": [ "<0.8.4" ], "v": "<0.8.4" }, { "advisory": "Whoogle Search is a self-hosted metasearch engine. Versions 0.8.3 and prior have a limited file write vulnerability when the configuration options in Whoogle are enabled. The `config` function in `app/routes.py` does not validate the user-controlled `name` variable on line 447 and `config_data` variable on line 437. The `name` variable is insecurely concatenated in `os.path.join`, leading to path manipulation. The POST data from the `config_data` variable is saved with `pickle.dump` which leads to a limited file write. However, the data that is saved is earlier transformed into a dictionary and the `url` key value pair is added before the file is saved on the system. All in all, the issue allows us to save and overwrite files on the system that the application has permissions to, with a dictionary containing arbitrary data and the `url` key value, which is a limited file write. Version 0.8.4 contains a patch for this issue.", "cve": "CVE-2024-22204", "id": "pyup.io-66721", "more_info_path": "/vulnerabilities/CVE-2024-22204/66721", "specs": [ "<0.8.4" ], "v": "<0.8.4" }, { "advisory": "An issue in the component /models/config.py of Whoogle search v0.9.0 allows attackers to execute arbitrary code via supplying a crafted search query.", "cve": "CVE-2024-53305", "id": "pyup.io-76768", "more_info_path": "/vulnerabilities/CVE-2024-53305/76768", "specs": [ "<0.9.1" ], "v": "<0.9.1" } ], "wiki": [ { "advisory": "All historical installations of django-wiki are vulnerable to maliciously crafted article content, that can cause severe use of server CPU through a regular expression loop.", "cve": "CVE-2024-28865", "id": "pyup.io-71927", "more_info_path": "/vulnerabilities/CVE-2024-28865/71927", "specs": [ "<0.10.1" ], "v": "<0.10.1" }, { "advisory": "Wiki 0.7.9 includes a fix for CVE-2021-25986: In Django-wiki, versions 0.0.20 to 0.7.8 are vulnerable to Stored Cross-Site Scripting (XSS) in Notifications Section. An attacker who has access to edit pages can inject JavaScript payload in the title field. When a victim gets a notification regarding the changes made in the application, the payload in the notification panel renders and loads external JavaScript.\r\nhttps://github.com/django-wiki/django-wiki/commit/9eaccc7519e4206a4d2f22640882f0737b2da9c5\r\nhttps://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25986", "cve": "CVE-2021-25986", "id": "pyup.io-42807", "more_info_path": "/vulnerabilities/CVE-2021-25986/42807", "specs": [ ">=0.0.20,<0.7.9" ], "v": ">=0.0.20,<0.7.9" } ], "wikibaseintegrator": [ { "advisory": "Wikibaseintegrator 0.10.1 includes OAuth 1.0a and OAuth 2.0 owner-only consumer support. These are now the best methods to securely authenticate against a MediaWiki instance.", "cve": "PVE-2021-41226", "id": "pyup.io-41226", "more_info_path": "/vulnerabilities/PVE-2021-41226/41226", "specs": [ "<0.10.1" ], "v": "<0.10.1" } ], "wikifaces": [ { "advisory": "The wikifaces package in PyPI v1.0 included a code execution backdoor inserted by a third party.", "cve": "CVE-2022-34509", "id": "pyup.io-62706", "more_info_path": "/vulnerabilities/CVE-2022-34509/62706", "specs": [ "==1.0.0" ], "v": "==1.0.0" } ], "wikirepo": [ { "advisory": "Wikirepo 0.1.1.5 includes fixes to vulnerabilities through exception use.", "cve": "PVE-2021-40303", "id": "pyup.io-40303", "more_info_path": "/vulnerabilities/PVE-2021-40303/40303", "specs": [ "<0.1.1.5" ], "v": "<0.1.1.5" } ], "wikitextparser": [ { "advisory": "Wikitextparser 0.28.1 includes a fix for a catastrophic backtracking vulnerability.\r\nhttps://github.com/5j9/wikitextparser/issues/22\r\nhttps://github.com/5j9/wikitextparser/commit/27b805f3483e27e2e829d2e44f8684e7bdb6200b", "cve": "PVE-2023-59355", "id": "pyup.io-59355", "more_info_path": "/vulnerabilities/PVE-2023-59355/59355", "specs": [ "<0.28.1" ], "v": "<0.28.1" }, { "advisory": "Wikitextparser 0.37.1 includes a fix for a catastrophic backtracking vulnerability.\r\nhttps://github.com/5j9/wikitextparser/commit/1a4dd6f496986acd0b6fbabbeabde864edc0ec13", "cve": "PVE-2023-59354", "id": "pyup.io-59354", "more_info_path": "/vulnerabilities/PVE-2023-59354/59354", "specs": [ "<0.37.1" ], "v": "<0.37.1" }, { "advisory": "Wikitextparser 0.45.1 includes a fix for a catastrophic backtracking vulnerability.\r\nhttps://github.com/5j9/wikitextparser/commit/9b8250177203936b1e755f179499919f46865e5a\r\nhttps://github.com/5j9/wikitextparser/issues/60", "cve": "PVE-2023-59353", "id": "pyup.io-59353", "more_info_path": "/vulnerabilities/PVE-2023-59353/59353", "specs": [ "<0.45.1" ], "v": "<0.45.1" } ], "will": [ { "advisory": "will before 0.5.4 uses a insecure transitive dependency (bottle).", "cve": "PVE-2021-35046", "id": "pyup.io-35046", "more_info_path": "/vulnerabilities/PVE-2021-35046/35046", "specs": [ "<0.5.4" ], "v": "<0.5.4" } ], "windsor": [ { "advisory": "Windsor version 1.0.1 includes a security fix for the function 'install' in 'windsor/cdkdependencies.py'. It contained an OS injection vulnerability: subprocess call with shell=True.\r\nhttps://github.com/westpoint-io/windsor/commit/ee9ab719500b6eef202f320bde11f84ef30b45e0#diff-713f6f14611f12ebebb0963b023a3d972511c1e04d5f80f97d072b60f486e14f", "cve": "PVE-2021-41402", "id": "pyup.io-41402", "more_info_path": "/vulnerabilities/PVE-2021-41402/41402", "specs": [ "<1.0.1" ], "v": "<1.0.1" } ], "wirecloud-keycloak": [ { "advisory": "Wirecloud-keycloak 0.3.4 fixes auth token injection when using WireCloud's proxy.", "cve": "PVE-2021-40905", "id": "pyup.io-40905", "more_info_path": "/vulnerabilities/PVE-2021-40905/40905", "specs": [ "<0.3.4" ], "v": "<0.3.4" } ], "wiredtiger": [ { "advisory": "Wiredtiger 2.9.0, 3.0.14, 3.2.9 and 3.3.11 restrict where statistics log files can be created to remove a vulnerability.\r\nhttps://jira.mongodb.org/browse/WT-2711", "cve": "PVE-2023-52687", "id": "pyup.io-52687", "more_info_path": "/vulnerabilities/PVE-2023-52687/52687", "specs": [ "<2.9.0", ">=3.0.0,<3.0.14", ">=3.1.0,<3.2.9", ">=3.3.0,<3.3.11" ], "v": "<2.9.0,>=3.0.0,<3.0.14,>=3.1.0,<3.2.9,>=3.3.0,<3.3.11" } ], "wiremock": [ { "advisory": "Wiremock 2.5.0 updates 'wiremock-standalone.jar' to version 2.35.0 to include a fix for a path traversal vulnerability.\r\nhttps://github.com/wiremock/python-wiremock/pull/48\r\nhttps://github.com/wiremock/wiremock/pull/1930", "cve": "PVE-2023-59418", "id": "pyup.io-59418", "more_info_path": "/vulnerabilities/PVE-2023-59418/59418", "specs": [ "<2.5.0" ], "v": "<2.5.0" }, { "advisory": "WireMock is a tool for mocking HTTP services. WireMock can be configured to only permit proxying (and therefore recording) to certain addresses. This is achieved via a list of allowed address rules and a list of denied address rules, where the allowed list is evaluated first. Until WireMock Webhooks Extension 3.0.0-beta-15, the filtering of target addresses from the proxy mode DID NOT work for Webhooks, so the users were potentially vulnerable regardless of the `limitProxyTargets` settings. Via the WireMock webhooks configuration, POST requests from a webhook might be forwarded to an arbitrary service reachable from WireMock\u2019s instance. For example, If someone is running the WireMock docker Container inside a private cluster, they can trigger internal POST requests against unsecured APIs or even against secure ones by passing a token, discovered using another exploit, via authentication headers. This issue has been addressed in versions 2.35.1 and 3.0.3 of wiremock. Wiremock studio has been discontinued and will not see a fix. Users unable to upgrade should use external firewall rules to define the list of permitted destinations.", "cve": "CVE-2023-41327", "id": "pyup.io-78502", "more_info_path": "/vulnerabilities/CVE-2023-41327/78502", "specs": [ "<2.6.1" ], "v": "<2.6.1" }, { "advisory": "Wiremock 2.6.1 includes a fix for CVE-2023-41329: Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio webhooks, proxy and recorder modes.\r\nhttps://github.com/wiremock/wiremock/security/advisories/GHSA-pmxq-pj47-j8j4", "cve": "CVE-2023-41329", "id": "pyup.io-61041", "more_info_path": "/vulnerabilities/CVE-2023-41329/61041", "specs": [ "<2.6.1" ], "v": "<2.6.1" } ], "wirepas-backend-client": [ { "advisory": "Wirepas-backend-client 1.2.0rc2 hides credentials when printing to stdout - see https://github.com/wirepas/backend-client/issues/48", "cve": "PVE-2021-37522", "id": "pyup.io-37522", "more_info_path": "/vulnerabilities/PVE-2021-37522/37522", "specs": [ "<1.2.0rc2" ], "v": "<1.2.0rc2" } ], "wlc": [ { "advisory": "Affected versions of the wlc package are vulnerable to Information Disclosure due to loading and using unscoped API keys from arbitrary configuration sections without URL scoping. The wlc WeblateConfig.get_url_key() logic could obtain an API key from non-[keys] sections (such as a legacy key setting) and then apply that credential when communicating with a different Weblate server than originally intended.", "cve": "CVE-2026-22251", "id": "pyup.io-84359", "more_info_path": "/vulnerabilities/CVE-2026-22251/84359", "specs": [ "<1.17.0" ], "v": "<1.17.0" }, { "advisory": "Affected versions of the wlc package are vulnerable to Improper Certificate Validation due to incorrect localhost detection when deciding whether to verify TLS certificates. In wlc/init.py, Weblate._should_verify_ssl (used by Weblate.invoke_request to set the requests verify flag) relies on url.netloc.startswith(\"127.0.0.1\"), so hostnames like 127.0.0.1.example.com are misclassified as localhost and certificate verification is skipped for those crafted URLs.", "cve": "CVE-2026-22250", "id": "pyup.io-84358", "more_info_path": "/vulnerabilities/CVE-2026-22250/84358", "specs": [ "<1.17.0" ], "v": "<1.17.0" }, { "advisory": "Affected versions of the wlc package are vulnerable to Path Traversal due to unsanitized API slugs being used to construct download file paths. The wlc download multi-translation download logic incorporates server-controlled slug values into the destination pathname without sufficiently normalizing or restricting path traversal, allowing the resolved path to escape the intended output directory.", "cve": "CVE-2026-23535", "id": "pyup.io-84604", "more_info_path": "/vulnerabilities/CVE-2026-23535/84604", "specs": [ "<1.17.2" ], "v": "<1.17.2" } ], "wmagent": [ { "advisory": "WMAgent v1.3.3rc2 and 1.3.3rc1, reqmgr2 1.4.1rc5 and 1.4.0rc2, reqmon 1.4.1rc5, and global-workqueue 1.4.1rc5 allows attackers to execute arbitrary code via a crafted dbs-client package.", "cve": "CVE-2022-34558", "id": "pyup.io-54120", "more_info_path": "/vulnerabilities/CVE-2022-34558/54120", "specs": [ ">=1.3.3rc1,<2.0.4" ], "v": ">=1.3.3rc1,<2.0.4" } ], "wmcore": [ { "advisory": "Wmcore 2.0.4 updates its dependency 'PyJWT' requirement to '~=2.4.0' to include a security fix.", "cve": "CVE-2022-29217", "id": "pyup.io-49584", "more_info_path": "/vulnerabilities/CVE-2022-29217/49584", "specs": [ "<2.0.4" ], "v": "<2.0.4" } ], "wolfcrypt": [ { "advisory": "wolfSSL and wolfCrypt 4.0.0 and earlier (when configured without --enable-fpecc, --enable-sp, or --enable-sp-math) contain a timing side channel in ECDSA signature generation. This allows a local attacker, able to precisely measure the duration of signature operations, to infer information about the nonces used and potentially mount a lattice attack to recover the private key used. The issue occurs because ecc.c scalar multiplication might leak the bit length.", "cve": "CVE-2019-13628", "id": "pyup.io-70562", "more_info_path": "/vulnerabilities/CVE-2019-13628/70562", "specs": [ "<=4.0.0" ], "v": "<=4.0.0" } ], "wolfssl": [ { "advisory": "Affected versions of the wolfssl package are vulnerable to Improper Authentication due to missing the fail-closed verification flag when verify_mode is set to require client certificates. In wolfssl-py, the SSLContext.verify_mode configuration relies on constants defined in wolfssl/__init__.py, where CERT_REQUIRED did not include the _SSL_VERIFY_FAIL_IF_NO_PEER_CERT bit, causing CERT_REQUIRED to behave like CERT_OPTIONAL and accept connections even when no peer certificate was presented.", "cve": "CVE-2025-15346", "id": "pyup.io-84322", "more_info_path": "/vulnerabilities/CVE-2025-15346/84322", "specs": [ "<5.8.4-stable" ], "v": "<5.8.4-stable" } ], "wolkenbrot": [ { "advisory": "Wolkenbrot 0.3 updates its dependency 'cryptography' to v3.3.2 to include security fixes.", "cve": "CVE-2020-36242", "id": "pyup.io-42171", "more_info_path": "/vulnerabilities/CVE-2020-36242/42171", "specs": [ "<0.3" ], "v": "<0.3" }, { "advisory": "Wolkenbrot 0.3 updates its dependency 'cryptography' to v3.3.2 to include security fixes.", "cve": "CVE-2020-25659", "id": "pyup.io-42217", "more_info_path": "/vulnerabilities/CVE-2020-25659/42217", "specs": [ "<0.3" ], "v": "<0.3" } ], "wordops": [ { "advisory": "Wordops 3.15.2 avoids dumping sensitive information in logs.\r\nhttps://github.com/WordOps/WordOps/commit/192b88452943a78d9a97508ed8c714691da72975", "cve": "PVE-2022-51175", "id": "pyup.io-51175", "more_info_path": "/vulnerabilities/PVE-2022-51175/51175", "specs": [ "<3.15.2" ], "v": "<3.15.2" }, { "advisory": "Affected versions of Wordops are vulnerable to TOCTOU (Time-of-Check to Time-of-Use) race condition in `wo/cli/plugins/stack_pref.py`. This vulnerability occurred because the 'os.open' call did not use a mode parameter during file creation.", "cve": "CVE-2024-34528", "id": "pyup.io-71463", "more_info_path": "/vulnerabilities/CVE-2024-34528/71463", "specs": [ "<3.21.0" ], "v": "<3.21.0" }, { "advisory": "The hsts flag in on site wordops before 3.9.5 was not secure with letsencrypt.", "cve": "PVE-2021-37541", "id": "pyup.io-37541", "more_info_path": "/vulnerabilities/PVE-2021-37541/37541", "specs": [ "<3.9.5" ], "v": "<3.9.5" }, { "advisory": "Wordops 3.9.6 adds fail2ban with custom jails to secure WordPress & SSH.", "cve": "PVE-2021-37540", "id": "pyup.io-37540", "more_info_path": "/vulnerabilities/PVE-2021-37540/37540", "specs": [ "<3.9.6" ], "v": "<3.9.6" }, { "advisory": "Wordops 3.9.7 secures the proftpd stack with TLS.", "cve": "PVE-2021-37539", "id": "pyup.io-37539", "more_info_path": "/vulnerabilities/PVE-2021-37539/37539", "specs": [ "<3.9.7" ], "v": "<3.9.7" }, { "advisory": "Wordops 3.9.9 adds `wo secure --ssh` to harden ssh security.", "cve": "PVE-2021-37534", "id": "pyup.io-37534", "more_info_path": "/vulnerabilities/PVE-2021-37534/37534", "specs": [ "<3.9.9" ], "v": "<3.9.9" }, { "advisory": "Wordops 3.9.9.1 improves the sshd_config template according to Mozilla Infosec guidelines.", "cve": "PVE-2021-37533", "id": "pyup.io-37533", "more_info_path": "/vulnerabilities/PVE-2021-37533/37533", "specs": [ "<3.9.9.1" ], "v": "<3.9.9.1" } ], "wpull": [ { "advisory": "wpull before 0.1006.1 is leaking HTTP header fields when transitioning from HTTP to HTTPS.", "cve": "PVE-2021-26176", "id": "pyup.io-26176", "more_info_path": "/vulnerabilities/PVE-2021-26176/26176", "specs": [ "<0.1006.1" ], "v": "<0.1006.1" }, { "advisory": "Select versions of wpull, a Wget-compatible web downloader and crawler, have an Information Exposure vulnerability. This issue arises when HTTP content is requested from a HTTPS source, leading to the unconditional setting of the referer field, which results in information leakage.", "cve": "PVE-2024-99825", "id": "pyup.io-65604", "more_info_path": "/vulnerabilities/PVE-2024-99825/65604", "specs": [ ">=0,<0.1006.1" ], "v": ">=0,<0.1006.1" } ], "wsgidav": [ { "advisory": "Wsgidav 4.1.0 includes a fix for CVE-2022-41905: Cross Site Scripting vulnerability in wsgidav when directory browsing is enabled.\r\nhttps://github.com/mar10/wsgidav/security/advisories/GHSA-xx6g-jj35-pxjv", "cve": "CVE-2022-41905", "id": "pyup.io-53380", "more_info_path": "/vulnerabilities/CVE-2022-41905/53380", "specs": [ ">=3.0.0a1,<4.1.0" ], "v": ">=3.0.0a1,<4.1.0" } ], "wslink": [ { "advisory": "Wslink 1.5.3 blocks further actions if no valid token is sent.\r\nhttps://github.com/kitware/wslink/commit/06bec0d5d4b98da90310dc5eca6fc1add09e33e4", "cve": "PVE-2022-48145", "id": "pyup.io-48145", "more_info_path": "/vulnerabilities/PVE-2022-48145/48145", "specs": [ "<1.5.3" ], "v": "<1.5.3" }, { "advisory": "Wslink 1.8.3 fixes an authentication bypass vulnerability.\r\nhttps://github.com/Kitware/wslink/pull/119", "cve": "PVE-2022-51430", "id": "pyup.io-51430", "more_info_path": "/vulnerabilities/PVE-2022-51430/51430", "specs": [ "<1.8.3" ], "v": "<1.8.3" } ], "wsnet": [ { "advisory": "Wsnet 0.0.14 adds secure defaults to wsserver.\r\nhttps://github.com/skelsec/wsnet/commit/949015d367f40015a6858167454091ed0e61b49e", "cve": "PVE-2023-62460", "id": "pyup.io-62460", "more_info_path": "/vulnerabilities/PVE-2023-62460/62460", "specs": [ "<0.0.14" ], "v": "<0.0.14" } ], "wtforms": [ { "advisory": "Wtforms 3.0.0a1 escape unsafe characters in label text, patching a potential XSS vulnerability.\r\nhttps://github.com/wtforms/wtforms/commit/8529b953a0919300794f95e01a7713162908c8a6", "cve": "PVE-2021-42852", "id": "pyup.io-42852", "more_info_path": "/vulnerabilities/PVE-2021-42852/42852", "specs": [ "<3.0.0a1" ], "v": "<3.0.0a1" }, { "advisory": "Specific versions of WTForms, a Python web development library, are vulnerable to Cross-site Scripting (XSS) attacks because label names are not escaped. This vulnerability exposes applications to potential malicious scripting through improperly sanitized label fields in forms.", "cve": "PVE-2024-99824", "id": "pyup.io-65605", "more_info_path": "/vulnerabilities/PVE-2024-99824/65605", "specs": [ ">=0,<2.3.0" ], "v": ">=0,<2.3.0" } ], "x-portrait": [ { "advisory": "The OpenSSF Package Analysis project has identified the PyPI package 'x-portrait' version 99.6 as malicious because it communicates with a domain associated with malicious activity, indicating potential security risks.", "cve": "PVE-2024-74243", "id": "pyup.io-74243", "more_info_path": "/vulnerabilities/PVE-2024-74243/74243", "specs": [ ">=0", "<=0" ], "v": ">=0,<=0" } ], "xaisuite": [ { "advisory": "Xaisuite 0.6.7 adds validation to prevent a code execution vulnerability.\r\nhttps://github.com/11301858/XAISuite/commit/418c75195c7a056a627317bfe08cad874c498fff", "cve": "PVE-2022-52583", "id": "pyup.io-52583", "more_info_path": "/vulnerabilities/PVE-2022-52583/52583", "specs": [ "<0.6.7" ], "v": "<0.6.7" } ], "xaitk-saliency": [ { "advisory": "Xaitk-saliency 0.5.0 updates its dependency 'pillow' to v8.3.2 to include a security fix.", "cve": "CVE-2021-23437", "id": "pyup.io-49340", "more_info_path": "/vulnerabilities/CVE-2021-23437/49340", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Xaitk-saliency 0.5.0 updates its dependency 'ipython' to v7.31.1 to include a security fix.", "cve": "CVE-2022-21699", "id": "pyup.io-49392", "more_info_path": "/vulnerabilities/CVE-2022-21699/49392", "specs": [ "<0.5.0" ], "v": "<0.5.0" }, { "advisory": "Xaitk-saliency 0.6.0 updates its dependency 'notebook' to version '6.4.10' to include a security fix.\r\nhttps://github.com/XAITK/xaitk-saliency/commit/0c511d896afb55ab35be5715e82bde8db7a7af90", "cve": "CVE-2022-24758", "id": "pyup.io-59101", "more_info_path": "/vulnerabilities/CVE-2022-24758/59101", "specs": [ "<0.6.0" ], "v": "<0.6.0" }, { "advisory": "Xaitk-saliency 0.7.0 updates its dependency 'notebook' to version '6.4.12' to include a security fix.\r\nhttps://github.com/XAITK/xaitk-saliency/commit/0cc205eaf644503fb49cb784299e28ff466be957", "cve": "CVE-2022-29238", "id": "pyup.io-59100", "more_info_path": "/vulnerabilities/CVE-2022-29238/59100", "specs": [ "<0.7.0" ], "v": "<0.7.0" } ], "xalpha": [ { "advisory": "xalpha v0.11.4 is vulnerable to Remote Command Execution (RCE).", "cve": "CVE-2023-37659", "id": "pyup.io-64995", "more_info_path": "/vulnerabilities/CVE-2023-37659/64995", "specs": [ ">=0.11.4,<0.11.9" ], "v": ">=0.11.4,<0.11.9" } ], "xata": [ { "advisory": "Xata 0.7.0 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/xataio/xata-py/issues/42\r\nhttps://github.com/xataio/xata-py/pull/45", "cve": "PVE-2023-59596", "id": "pyup.io-59596", "more_info_path": "/vulnerabilities/PVE-2023-59596/59596", "specs": [ "<0.7.0" ], "v": "<0.7.0" } ], "xblock-drag-and-drop-v2": [ { "advisory": "Xblock-drag-and-drop-v2 3.0.0 sanitizes HTML tags to prevent XSS vulnerabilities.", "cve": "PVE-2023-53521", "id": "pyup.io-53521", "more_info_path": "/vulnerabilities/PVE-2023-53521/53521", "specs": [ "<3.0.0" ], "v": "<3.0.0" }, { "advisory": "### Impact\nXSS Vulnerability in multiple XBlock Fields. Any platform that has deployed the XBlock will be impacted.\n\n### Patches\nhttps://github.com/openedx/xblock-drag-and-drop-v2/commit/53c4482f9bb6d8c7ccdf5253bd82c84a222b2492\n\nThe fix is compatible with all Open edX releases newer than Lilac.\n\n### Workarounds\nNone.\n\n### References\nhttps://github.com/openedx/xblock-drag-and-drop-v2/pull/295#issuecomment-1277693864\n", "cve": "CVE-2022-46147", "id": "pyup.io-54594", "more_info_path": "/vulnerabilities/CVE-2022-46147/54594", "specs": [ ">=0,<3.0.0" ], "v": ">=0,<3.0.0" } ], "xdg": [ { "advisory": "A code injection issue was discovered in PyXDG before 0.26 via crafted Python code in a Category element of a Menu XML document in a .menu file. XDG_CONFIG_DIRS must be set up to trigger xdg.Menu.parse parsing within the directory containing this file. This is due to a lack of sanitization in xdg/Menu.py before an eval call. See: CVE-2019-12761.", "cve": "CVE-2019-12761", "id": "pyup.io-37203", "more_info_path": "/vulnerabilities/CVE-2019-12761/37203", "specs": [ "<0.26" ], "v": "<0.26" }, { "advisory": "Race condition in the xdg.BaseDirectory.get_runtime_dir function in python-xdg 0.25 allows local users to overwrite arbitrary files by pre-creating /tmp/pyxdg-runtime-dir-fallback-victim to point to a victim-owned location, then replacing it with a symlink to an attacker-controlled location once the get_runtime_dir function is called.", "cve": "CVE-2014-1624", "id": "pyup.io-35521", "more_info_path": "/vulnerabilities/CVE-2014-1624/35521", "specs": [ "<=0.25" ], "v": "<=0.25" } ], "xerosdk": [ { "advisory": "Xerosdk 0.14.3 updates its dependency 'requests' to v2.32.3 to include a security fix.", "cve": "PVE-2025-75656", "id": "pyup.io-75656", "more_info_path": "/vulnerabilities/PVE-2025-75656/75656", "specs": [ "<0.14.3" ], "v": "<0.14.3" } ], "xgrammar": [ { "advisory": "Xgrammar includes a cache for compiled grammars to increase performance with repeated use of the same grammar. This cache is held in memory. Since the cache is unbounded, a system making use of xgrammar can be abused to fill up a host's memory and cause a denial of service. For example, sending many small requests to an LLM inference server with unique JSON schemas would eventually cause this denial of service to occur.", "cve": "CVE-2025-32381", "id": "pyup.io-76612", "more_info_path": "/vulnerabilities/CVE-2025-32381/76612", "specs": [ "<0.1.18" ], "v": "<0.1.18" }, { "advisory": "Affected versions of the xgrammar package are vulnerable to Denial of Service due to infinite recursion in grammar processing. The GrammarMatcherBase::ExpandEquivalentStackElements method at grammar_matcher_base.cc:179 enters an infinite recursive loop when processing certain JSON schema patterns, causing stack overflow and segmentation faults during grammar compilation.", "cve": "CVE-2025-57809", "id": "pyup.io-79076", "more_info_path": "/vulnerabilities/CVE-2025-57809/79076", "specs": [ "<0.1.21" ], "v": "<0.1.21" }, { "advisory": "Affected versions of the xgrammar package are vulnerable to Denial of Service (DoS) due to unbounded processing time in the grammar optimizer when handling very large JSON Schema\u2013derived enumerations. The `xgr.Grammar.from_json_schema()` code path constructs an oversized grammar from attacker-provided enum lists and invokes the v0.1.23 optimizer, whose performance degrades severely on inputs exceeding \\~100k characters, leading to multi-minute parsing.", "cve": "CVE-2025-58446", "id": "pyup.io-79468", "more_info_path": "/vulnerabilities/CVE-2025-58446/79468", "specs": [ "<0.1.24" ], "v": "<0.1.24" } ], "xhtml2pdf": [ { "advisory": "Affected versions of the xhtml2pdf package are vulnerable to Regular Expression Denial of Service due to inefficient complexity in the getcolor function\u2019s pattern processing. The getcolor function in utils.py fails to handle crafted input in a constant-time or complexity-bounded manner, allowing a malicious string to trigger excessive backtracking and resource consumption. An attacker can exploit this by supplying a specially crafted string to the getcolor function, causing high CPU usage that may render the host system unresponsive or significantly degrade the availability of services relying on xhtml2pdf.", "cve": "CVE-2024-25885", "id": "pyup.io-78802", "more_info_path": "/vulnerabilities/CVE-2024-25885/78802", "specs": [ "<=0.2.16" ], "v": "<=0.2.16" } ], "xiaogpt": [ { "advisory": "Xiaogpt version 2.31 is susceptible to a denial of service vulnerability due to issues with how idna.encode handles specially crafted inputs.", "cve": "CVE-2022-45061", "id": "pyup.io-67881", "more_info_path": "/vulnerabilities/CVE-2022-45061/67881", "specs": [ "<2.31" ], "v": "<2.31" } ], "xknx": [ { "advisory": "Xknx 2.0.0 updates its dependency 'cryptography' to v38.0.3 to include security fixes.", "cve": "CVE-2022-3786", "id": "pyup.io-52070", "more_info_path": "/vulnerabilities/CVE-2022-3786/52070", "specs": [ "<2.0.0" ], "v": "<2.0.0" }, { "advisory": "Xknx 2.0.0 updates its dependency 'cryptography' to v38.0.3 to include security fixes.", "cve": "CVE-2022-3602", "id": "pyup.io-52177", "more_info_path": "/vulnerabilities/CVE-2022-3602/52177", "specs": [ "<2.0.0" ], "v": "<2.0.0" } ], "xml2dict": [ { "advisory": "XXE vulnerability in 'XML2Dict' version 0.2.2 allows an attacker to cause a denial of service. The parse function does not properly restrict recursive entity references.", "cve": "CVE-2021-25951", "id": "pyup.io-54305", "more_info_path": "/vulnerabilities/CVE-2021-25951/54305", "specs": [ ">=0" ], "v": ">=0" } ], "xml2rfc": [ { "advisory": "Xml2rfc 3.12.4 addresses an issue where affected versions were vulnerable to XSS attacks, allowing script elements in SVG sources. \r\nhttps://github.com/ietf-tools/xml2rfc/commit/df99f948b53ca4836d830ac55ec84eb4023e81dahttps://github.com/advisories/GHSA-cf4q-4cqr-7g7w", "cve": "PVE-2024-63455", "id": "pyup.io-63455", "more_info_path": "/vulnerabilities/PVE-2024-63455/63455", "specs": [ "<3.12.4" ], "v": "<3.12.4" }, { "advisory": "Xml2rfc has file inclusion irregularities.", "cve": "PVE-2025-76339", "id": "pyup.io-76339", "more_info_path": "/vulnerabilities/PVE-2025-76339/76339", "specs": [ "<3.27.0" ], "v": "<3.27.0" }, { "advisory": "Affected versions of the xml2rfc package are vulnerable to Path Traversal due to improper validation of link element targets during PDF generation. The PDF output path in xml2rfc processes XML link elements with rel=\"attachment\" and resolves their href values directly on the local filesystem without normalizing or restricting paths to a safe directory.", "cve": "CVE-2025-11058", "id": "pyup.io-81121", "more_info_path": "/vulnerabilities/CVE-2025-11058/81121", "specs": [ "<3.30.1" ], "v": "<3.30.1" }, { "advisory": "Affected versions of the xml2rfc package are vulnerable to Path Traversal due to insufficient sanitisation of `` elements in prepped RFCXML consumed during PDF generation. When handling \u201cprepped\u201d XML inputs, the generation pipeline failed to remove or constrain attachment links before use, allowing the PDF writer to dereference a user-controlled `href` path; specifically, the flow into `run.main` proceeded without invoking a parser sanitisation step (e.g., `parser.sanitize` / `xml2rfc.utils.strip_link_attachments`) to neutralise these elements.", "cve": "CVE-2025-11059", "id": "pyup.io-79492", "more_info_path": "/vulnerabilities/CVE-2025-11059/79492", "specs": [ "<3.30.2" ], "v": "<3.30.2" }, { "advisory": "Some versions of xml2rfc are susceptible to Cross-site Scripting (XSS) through script elements embedded in SVG sources.", "cve": "PVE-2024-99823", "id": "pyup.io-65606", "more_info_path": "/vulnerabilities/PVE-2024-99823/65606", "specs": [ ">=0,<3.12.4" ], "v": ">=0,<3.12.4" }, { "advisory": "Xml2rfc 3.12.4 includes a security fix: xml2rfc allows 'script' elements in SVG sources. In HTML output having these script elements can lead to XSS attacks.", "cve": "PVE-2023-55196", "id": "pyup.io-55196", "more_info_path": "/vulnerabilities/PVE-2023-55196/55196", "specs": [ ">=0,<3.12.4" ], "v": ">=0,<3.12.4" } ], "xml2xlsx": [ { "advisory": "Xml2xlsx throughout 1.0.1 is vulnerable to XML External Entity (XEE) vulnerability. The function 'xml2xlsx()' does not restrict external entities while parsing the specially crafted XML document. An attacker is able to read local files by defining an external entity with a file:// URI as shown by the PoC:\r\nfrom xml2xlsx import xml2xlsx \r\ntemplate_id = \"\"\" ]> vulnerable &ent; // ----------------------------------- \"\"\" \r\nf = open('test.xlsx', 'wb') \r\nf.write(xml2xlsx(template_id)) \r\nf.close()", "cve": "PVE-2023-99969", "id": "pyup.io-60870", "more_info_path": "/vulnerabilities/PVE-2023-99969/60870", "specs": [ "<=1.0.1" ], "v": "<=1.0.1" } ], "xml4h": [ { "advisory": "Xml4h is vulnerable to XML External Entity (XEE) attacks. The function 'parse()' does not restrict external entities while parsing a specially crafted XML document. Due to this flaw, an attacker could read local files by defining an external entity with a file:// URI as showed by the PoC:\r\nimport xml4h \r\ndoc = xml4h.parse('simple.xml') \r\nprint(doc.userInfo.lastName.text) \r\n# simple.xml content: ]> John &ent; ", "cve": "PVE-2023-99938", "id": "pyup.io-60927", "more_info_path": "/vulnerabilities/PVE-2023-99938/60927", "specs": [ "<=1.0" ], "v": "<=1.0" } ], "xmlschema-acue": [ { "advisory": "Xmlschema-acue 0.9.27 prevents XML attacks with the use of the defusedxml package.", "cve": "CVE-2013-1665", "id": "pyup.io-45726", "more_info_path": "/vulnerabilities/CVE-2013-1665/45726", "specs": [ "<0.9.27" ], "v": "<0.9.27" }, { "advisory": "Xmlschema-acue 0.9.27 prevents XML attacks with the use of the defusedxml package.", "cve": "CVE-2013-1664", "id": "pyup.io-54878", "more_info_path": "/vulnerabilities/CVE-2013-1664/54878", "specs": [ "<0.9.27" ], "v": "<0.9.27" } ], "xmltodict": [ { "advisory": "Affected versions of the xmltodict package are vulnerable to Improper Input Validation due to insufficient validation of XML element, attribute, and `xmlns` prefix names. The `xmltodict._validate_name` function did not reject the `\"`, `'`, and `=` characters, allowing `unparse` to serialize keys into tag or attribute names containing illegal tokens and produce ill-formed XML.", "cve": "CVE-2025-9375", "id": "pyup.io-79408", "more_info_path": "/vulnerabilities/CVE-2025-9375/79408", "specs": [ "<0.15.1" ], "v": "<0.15.1" } ], "xmpp-http-upload": [ { "advisory": "In xmpp-http-upload before version 0.4.0, when the GET method is attacked, attackers can read files which have a `.data` suffix and which are accompanied by a JSON file with the `.meta` suffix. This can lead to Information Disclosure and in some shared-hosting scenarios also to circumvention of authentication or other limitations on the outbound (GET) traffic. For example, in a scenario where a single server has multiple instances of the application running (with separate DATA_ROOT settings), an attacker who has knowledge about the directory structure is able to read files from any other instance to which the process has read access. If instances have individual authentication (for example, HTTP authentication via a reverse proxy, source IP based filtering) or other restrictions (such as quotas), attackers may circumvent those limits in such a scenario by using the Directory Traversal to retrieve data from the other instances. If the associated XMPP server (or anyone knowing the SECRET_KEY) is malicious, they can write files outside the DATA_ROOT. The files which are written are constrained to have the `.meta` and the `.data` suffixes; the `.meta` file will contain the JSON with the Content-Type of the original request and the `.data` file will contain the payload. The issue is patched in version 0.4.0.", "cve": "CVE-2020-15239", "id": "pyup.io-42279", "more_info_path": "/vulnerabilities/CVE-2020-15239/42279", "specs": [ "<0.4.0" ], "v": "<0.4.0" } ], "xontrib-output-search": [ { "advisory": "Xontrib-output-search 0.0.2 no longer uses 'XONSH_STORE_STDOUT'. Now, the only output stored is the last not empty command in memory. This is a more secure solution.", "cve": "PVE-2021-38310", "id": "pyup.io-38310", "more_info_path": "/vulnerabilities/PVE-2021-38310/38310", "specs": [ "<0.0.2" ], "v": "<0.0.2" } ], "xorq": [ { "advisory": "Xorq updates its dependency black to 24.3.0 due to the CVE-2024-21503.", "cve": "CVE-2024-21503", "id": "pyup.io-75556", "more_info_path": "/vulnerabilities/CVE-2024-21503/75556", "specs": [ "<0.1.5" ], "v": "<0.1.5" }, { "advisory": "Xorq updates Snowflake-connector-python to 3.13.2 due to the CVE-2025-24795.", "cve": "PVE-2025-75555", "id": "pyup.io-75555", "more_info_path": "/vulnerabilities/PVE-2025-75555/75555", "specs": [ "<0.1.9" ], "v": "<0.1.9" } ], "xpra": [ { "advisory": "Xpra 0.0.7.34 restricts access to the 'run-xpra' script (chmod) and fixes a problem when cursor data sent to the client was too big (exposing server memory).", "cve": "PVE-2021-40248", "id": "pyup.io-40248", "more_info_path": "/vulnerabilities/PVE-2021-40248/40248", "specs": [ "<0.0.7.34" ], "v": "<0.0.7.34" }, { "advisory": "Xpra 0.1.0 includes a security patch for strict filtering of packet handlers until a connection is authenticated.", "cve": "PVE-2021-40247", "id": "pyup.io-40247", "more_info_path": "/vulnerabilities/PVE-2021-40247/40247", "specs": [ "<0.1.0" ], "v": "<0.1.0" }, { "advisory": "Xpra 0.13.9 uses the secure \"compare_digest\" if available.", "cve": "PVE-2021-40245", "id": "pyup.io-40245", "more_info_path": "/vulnerabilities/PVE-2021-40245/40245", "specs": [ "<0.13.9" ], "v": "<0.13.9" }, { "advisory": "Xpra 0.15.8 fixes validation of the 'mmap' security token.", "cve": "PVE-2021-40244", "id": "pyup.io-40244", "more_info_path": "/vulnerabilities/PVE-2021-40244/40244", "specs": [ "<0.15.8" ], "v": "<0.15.8" }, { "advisory": "Xpra 2.3 adds custom http headers to support the content security policy.", "cve": "PVE-2021-40242", "id": "pyup.io-40242", "more_info_path": "/vulnerabilities/PVE-2021-40242/40242", "specs": [ "<2.3" ], "v": "<2.3" }, { "advisory": "Xpra 3.1.1 includes a fix for a Use of Cryptographically Weak Pseudo-Random Number Generator vulnerability.\r\nhttps://github.com/Xpra-org/xpra/commit/73f80840aacba21dd19f8a096f12ce6b88886d63", "cve": "PVE-2023-60575", "id": "pyup.io-60575", "more_info_path": "/vulnerabilities/PVE-2023-60575/60575", "specs": [ "<3.1.1" ], "v": "<3.1.1" }, { "advisory": "Xpra 3.1.1 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/Xpra-org/xpra/commit/d0fc0a889188e70f2d2451089c397a86ce0f71cc", "cve": "PVE-2023-60576", "id": "pyup.io-60576", "more_info_path": "/vulnerabilities/PVE-2023-60576/60576", "specs": [ "<3.1.1" ], "v": "<3.1.1" }, { "advisory": "Selected versions of Xpra, a multi-platform screen and application forwarding system, are susceptible to a race condition vulnerability in proxy_instance.py.", "cve": "PVE-2024-99822", "id": "pyup.io-65607", "more_info_path": "/vulnerabilities/PVE-2024-99822/65607", "specs": [ ">=3.0,<3.1.1" ], "v": ">=3.0,<3.1.1" }, { "advisory": "Xpra 4.2.3 includes a fix for a Race Condition vulnerability.\r\nhttps://github.com/Xpra-org/xpra/commit/e113aa1bc4908d32b1e1725821cdf9f7324304ef", "cve": "PVE-2023-60574", "id": "pyup.io-60574", "more_info_path": "/vulnerabilities/PVE-2023-60574/60574", "specs": [ ">=4.0,<4.2.3" ], "v": ">=4.0,<4.2.3" } ], "xpresso": [ { "advisory": "Xpresso 0.17.0 removes all security features.\r\nhttps://github.com/adriangb/xpresso/pull/60", "cve": "PVE-2022-44949", "id": "pyup.io-44949", "more_info_path": "/vulnerabilities/PVE-2022-44949/44949", "specs": [ ">=0.17.0" ], "v": ">=0.17.0" } ], "xraysink": [ { "advisory": "Xraysink 1.6.2 updates its dependency 'certifi' to version '2023.7.22' to include a fix for a vulnerability.\r\nhttps://github.com/garyd203/xraysink/commit/3859f878f030ae4762592e7e900e079ac9e7f298", "cve": "CVE-2023-37920", "id": "pyup.io-60637", "more_info_path": "/vulnerabilities/CVE-2023-37920/60637", "specs": [ "<1.6.2" ], "v": "<1.6.2" } ], "xscrapers": [ { "advisory": "Xscrapers 127.0.0.150077", "cve": "PVE-2021-39640", "id": "pyup.io-39640", "more_info_path": "/vulnerabilities/PVE-2021-39640/39640", "specs": [ "<127.0.0.150077" ], "v": "<127.0.0.150077" } ], "xss": [ { "advisory": "Xss is a malicious package, typosquatting. It steals your Roblox security cookies and Discord tokens.\r\nhttps://securityboulevard.com/2022/02/malicious-roblox-cookie-and-discord-token-stealers-hit-pypi-repository", "cve": "PVE-2022-45442", "id": "pyup.io-45442", "more_info_path": "/vulnerabilities/PVE-2022-45442/45442", "specs": [ ">0", "<0" ], "v": ">0,<0" } ], "xstatic-lodash": [ { "advisory": "Xstatic-lodash (xstatic-packaged version of node JS module \"lodash\" v4.16.4) is affected by CVE-2019-1010266: Lodash prior to 4.17.11 is affected by 'CWE-400: Uncontrolled Resource Consumption'. The impact is Denial of Service (DoS). The component affected is the Date handler. The attack vector consists in the attacker providing very long strings, which the library attempts to match using a regular expression.", "cve": "CVE-2019-1010266", "id": "pyup.io-42210", "more_info_path": "/vulnerabilities/CVE-2019-1010266/42210", "specs": [ "<4.17.11" ], "v": "<4.17.11" }, { "advisory": "Xstatic-lodash (xstatic-packaged version of node JS module \"lodash\" v4.16.4) is affected by CVE-2018-3721: Lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of \"Object\" via __proto__, causing the addition or modification of an existing property that will exist on all objects.", "cve": "CVE-2018-3721", "id": "pyup.io-42209", "more_info_path": "/vulnerabilities/CVE-2018-3721/42209", "specs": [ "<4.17.5" ], "v": "<4.17.5" } ], "xstatic-moment": [ { "advisory": "Xstatic-moment (xstatic-packaged version of JS library \"moment\" v2.8.4) is affected by CVE-2016-4055: The duration function in the moment package before 2.11.2 for Node.js allows remote attackers to cause a denial of service (CPU consumption) via a long string, aka a \"regular expression Denial of Service (ReDoS).\"", "cve": "CVE-2016-4055", "id": "pyup.io-42208", "more_info_path": "/vulnerabilities/CVE-2016-4055/42208", "specs": [ "<2.11.2" ], "v": "<2.11.2" }, { "advisory": "Xstatic-moment (xstatic-packaged version of JS library \"moment\" v2.8.4) is affected by CVE-2017-18214: The moment module before 2.19.3 for Node.js is prone to a regular expression denial of service via a crafted date string, a different vulnerability than CVE-2016-4055.", "cve": "CVE-2017-18214", "id": "pyup.io-42207", "more_info_path": "/vulnerabilities/CVE-2017-18214/42207", "specs": [ "<2.19.3" ], "v": "<2.19.3" } ], "xtea3": [ { "advisory": "xtea3 1.0.0 change: Removal of CBCMAC (security reasons)", "cve": "PVE-2021-37222", "id": "pyup.io-37222", "more_info_path": "/vulnerabilities/PVE-2021-37222/37222", "specs": [ "<1.0.0" ], "v": "<1.0.0" } ], "xtgeo": [ { "advisory": "Xtgeo 2.17.1 drops dependency on 'pillow' to avoid security issues with versions <=8.4.\r\nhttps://github.com/equinor/xtgeo/pull/748", "cve": "PVE-2022-44524", "id": "pyup.io-48286", "more_info_path": "/vulnerabilities/PVE-2022-44524/48286", "specs": [ "<2.17.1" ], "v": "<2.17.1" }, { "advisory": "Xtgeo 2.17.1 drops dependency on 'pillow' to avoid security issues affecting versions <=8.4.\r\nhttps://github.com/equinor/xtgeo/pull/748", "cve": "CVE-2022-24303", "id": "pyup.io-48264", "more_info_path": "/vulnerabilities/CVE-2022-24303/48264", "specs": [ "<2.17.1" ], "v": "<2.17.1" }, { "advisory": "Xtgeo 2.17.1 drops dependency on 'pillow' to avoid security issues with versions <=8.4.\r\nhttps://github.com/equinor/xtgeo/pull/748", "cve": "CVE-2022-22817", "id": "pyup.io-48284", "more_info_path": "/vulnerabilities/CVE-2022-22817/48284", "specs": [ "<2.17.1" ], "v": "<2.17.1" }, { "advisory": "Xtgeo 2.17.1 drops dependency on 'pillow' to avoid security issues with versions <=8.4.\r\nhttps://github.com/equinor/xtgeo/pull/748", "cve": "CVE-2022-22815", "id": "pyup.io-48288", "more_info_path": "/vulnerabilities/CVE-2022-22815/48288", "specs": [ "<2.17.1" ], "v": "<2.17.1" }, { "advisory": "Xtgeo 2.17.1 drops dependency on 'pillow' to avoid security issues with versions <=8.4.\r\nhttps://github.com/equinor/xtgeo/pull/748", "cve": "PVE-2021-44525", "id": "pyup.io-48285", "more_info_path": "/vulnerabilities/PVE-2021-44525/48285", "specs": [ "<2.17.1" ], "v": "<2.17.1" }, { "advisory": "Xtgeo 2.17.1 drops dependency on 'pillow' to avoid security issues with versions <=8.4.\r\nhttps://github.com/equinor/xtgeo/pull/748", "cve": "CVE-2022-22816", "id": "pyup.io-48287", "more_info_path": "/vulnerabilities/CVE-2022-22816/48287", "specs": [ "<2.17.1" ], "v": "<2.17.1" } ], "xtts-api-server": [ { "advisory": "Xtts-api-server 0.8.5 addresses a path traversal vulnerability.\r\nhttps://github.com/daswer123/xtts-api-server/pull/61/commits/50683bb818802116ae056c8e9f129d5ec4b1763d", "cve": "PVE-2024-65541", "id": "pyup.io-65541", "more_info_path": "/vulnerabilities/PVE-2024-65541/65541", "specs": [ "<0.8.5" ], "v": "<0.8.5" } ], "xuper": [ { "advisory": "xuper 3.2.0 validates autogen tx to avoid fake transaction attack; Fix UTXO with negative frozen heigh could pass transaction check; Check the number of coinbase transactions in a block to avoid byzantine miner;", "cve": "PVE-2021-37718", "id": "pyup.io-37718", "more_info_path": "/vulnerabilities/PVE-2021-37718/37718", "specs": [ "<3.2.0" ], "v": "<3.2.0" } ], "yahoo-earnings-calendar": [ { "advisory": "yahoo-earnings-calendar 0.4.0 - fix(security): upgrade requests (14)", "cve": "PVE-2021-36697", "id": "pyup.io-36697", "more_info_path": "/vulnerabilities/PVE-2021-36697/36697", "specs": [ "<0.4.0" ], "v": "<0.4.0" }, { "advisory": "Yahoo-earnings-calendar 0.5.2 upgrades urllib3 to 1.24.2 for security reasons.", "cve": "PVE-2021-37079", "id": "pyup.io-37079", "more_info_path": "/vulnerabilities/PVE-2021-37079/37079", "specs": [ "<0.5.2" ], "v": "<0.5.2" } ], "yamale": [ { "advisory": "Yamale 3.0.8 includes a fix for CVE-2021-38305: 23andMe Yamale before 3.0.8 allows remote attackers to execute arbitrary code via a crafted schema file. The schema parser uses eval as part of its processing, and tries to protect from malicious expressions by limiting the builtins that are passed to the eval. When processing the schema, each line is run through Python's eval function to make the validator available. A well-constructed string within the schema rules can execute system commands; thus, by exploiting the vulnerability, an attacker can run arbitrary code on the image that invokes Yamale.\r\nhttps://github.com/23andMe/Yamale/pull/165\r\nhttps://github.com/23andMe/Yamale/releases/tag/3.0.8", "cve": "CVE-2021-38305", "id": "pyup.io-41094", "more_info_path": "/vulnerabilities/CVE-2021-38305/41094", "specs": [ "<3.0.8" ], "v": "<3.0.8" }, { "advisory": "Yamale version 4.0.0 includes a fix for a RCE vulnerability.\r\nhttps://github.com/23andMe/Yamale/issues/167", "cve": "PVE-2021-42118", "id": "pyup.io-42118", "more_info_path": "/vulnerabilities/PVE-2021-42118/42118", "specs": [ "<4.0.0" ], "v": "<4.0.0" }, { "advisory": "Yamale does not protect against intentionally malicious schemas. Ensure that your schema definitions come from internal or trusted sources.", "cve": "PVE-2021-42188", "id": "pyup.io-42188", "more_info_path": "/vulnerabilities/PVE-2021-42188/42188", "specs": [ ">0" ], "v": ">0" } ], "yaml-mako": [ { "advisory": "Yaml-Mako version 1.0.0 includes a security patch in 'yaml_mako.py'. The use of unsafe yaml.load() allows instantiation of arbitrary objects.\r\nhttps://github.com/haarcuba/yaml_mako/commit/8e54bf48bf0a95495eaaf4e66cb42d8241c56f66#diff-98273dbb1f4888f07033576daad480b434f9fa909d2646e4a1e20f4691c9c757", "cve": "CVE-2017-18342", "id": "pyup.io-41404", "more_info_path": "/vulnerabilities/CVE-2017-18342/41404", "specs": [ "<1.0.0" ], "v": "<1.0.0" } ], "yaml-rs": [ { "advisory": "Affected versions of this package are vulnerable to Security Filter Bypass. The encoding crate fails to properly handle malformed input by silently ignoring invalid bytes, leading to attackers being able to craft byte sequences that bypass security filters through invalid byte stripping, such as <\\xFF\\xFEscript> becoming