ecosystem stringclasses 14 values | vuln_id stringlengths 10 19 | summary stringlengths 4 267 ⌀ | details stringlengths 9 13.5k | aliases stringlengths 17 144 ⌀ | modified_date stringdate 2010-05-27 05:47:00 2022-05-10 08:46:52 | published_date stringdate 2005-12-31 05:00:00 2022-05-10 08:46:50 | severity stringclasses 5 values | score float64 0 10 ⌀ | cwe_id stringclasses 988 values | refs stringlengths 30 17.7k ⌀ | introduced stringlengths 75 4.26k ⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
PyPI | GHSA-5mc5-5j6c-qmf9 | High severity vulnerability that affects cfscrape | 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-2017-7235'} | 2022-03-03T05:13:44.492678Z | 2018-07-13T16:01:01Z | HIGH | null | {'CWE-20'} | {'https://github.com/advisories/GHSA-5mc5-5j6c-qmf9', 'https://github.com/Anorov/cloudflare-scrape/issues/97', 'http://www.securityfocus.com/bid/97191', 'https://nvd.nist.gov/vuln/detail/CVE-2017-7235', 'https://github.com/Anorov/cloudflare-scrape/releases/tag/1.8.0', 'https://github.com/Anorov/cloudflare-scrape'} | null |
PyPI | GHSA-rpx7-33j2-xx9x | Arbitrary file deletion in NeMo ASR webapp | ### Description
NVIDIA NeMo contains a vulnerability in ASR WebApp, where Relative Path Traversal (CWE-23) may lead to deletion of any directory through the "../" structure when admin privileges are available.
CVSS Score = 2.0
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N
### Impact
When the optional tool ASR Webapp (https://github.com/NVIDIA/NeMo/tree/main/tools/asr_webapp) is used prior to commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0, some interfaces do not verify user input. Malicious attackers can construct malicious requests to delete any directory through the "../" structure.
The vulnerability affects only cases where this particular web app is started by a user with superuser permissions. The web application is *not* a part of the regular pip release or the corresponding container, and impacts only users that clone the repository in its entirety and execute the web app (while also possessing superuser permissions).
## Patches
This vulnerability has been patched via https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0, which is effectively any clone of the repository post r1.5.1 branch. Since the web app is not distributed via pip release or container, users who clone the main branch post this commit will possess the patch.
### Workarounds
The changes in commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0 can be applied to any version of the web app without any adverse effect.
### Additional Information
Exploit Found on: 2021.12.16
Exploit Found by: @haby0
| null | 2022-04-15T19:46:57.518536Z | 2022-02-15T01:57:18Z | LOW | null | null | {'https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0', 'https://github.com/NVIDIA/NeMo/security/advisories/GHSA-rpx7-33j2-xx9x', 'https://github.com/NVIDIA/NeMo'} | null |
PyPI | PYSEC-2021-461 | null | TensorFlow is an end-to-end open source platform for machine learning. 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. 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. | {'GHSA-393f-2jr3-cp69', 'CVE-2021-29533'} | 2021-12-09T06:34:48.500169Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/b432a38fe0e1b4b904a6c222cbce794c39703e87', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-393f-2jr3-cp69'} | null |
PyPI | PYSEC-2019-132 | null | In the urllib3 library through 1.24.1 for Python, CRLF injection is possible if the attacker controls the request parameter. | {'CVE-2019-11236'} | 2019-06-13T04:29:00Z | 2019-04-15T15:29:00Z | null | null | null | {'https://access.redhat.com/errata/RHSA-2019:2272', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/R62XGEYPUTXMRHGX5I37EBCGQ5COHGKR/', 'https://lists.debian.org/debian-lts-announce/2019/06/msg00016.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XOSA2NT4DUQDBEIWE6O7KKD24XND7TE2/', 'http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00041.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TBI45HO533KYHNB5YRO43TBYKA3E3VRL/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NKGPJLVLVYCL4L4B4G5TIOTVK4BKPG72/', 'https://github.com/urllib3/urllib3/issues/1553', 'https://usn.ubuntu.com/3990-2/', 'https://usn.ubuntu.com/3990-1/', 'http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00039.html', 'https://access.redhat.com/errata/RHSA-2019:3335', 'https://access.redhat.com/errata/RHSA-2019:3590'} | null |
PyPI | PYSEC-2022-52 | null | Tensorflow is an Open Source Machine Learning Framework. 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. 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. | {'GHSA-6gmv-pjp9-p8w8', 'CVE-2022-21728'} | 2022-03-09T00:17:30.293594Z | 2022-02-03T11:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/ops/array_ops.cc#L1636-L1671', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6gmv-pjp9-p8w8', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/framework/shape_inference.h#L415-L428', 'https://github.com/tensorflow/tensorflow/commit/37c01fb5e25c3d80213060460196406c43d31995'} | null |
PyPI | PYSEC-2020-174 | null | 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-2019-16791', 'GHSA-h92m-42h4-82f6'} | 2020-10-23T18:18:00Z | 2020-01-22T02:15:00Z | null | null | null | {'https://gist.github.com/Snawoot/b9da85d6b26dea5460673b29df1adc6b', 'https://github.com/Snawoot/postfix-mta-sts-resolver/security/advisories/GHSA-h92m-42h4-82f6'} | null |
PyPI | GHSA-4w8p-x6g8-fv64 | Server-Side Request Forgery in calibreweb | calibreweb prior to version 0.6.16 contains a Server-Side Request Forgery (SSRF) vulnerability. | {'CVE-2022-0339'} | 2022-04-04T21:46:56.538317Z | 2022-02-01T00:48:54Z | MODERATE | null | {'CWE-918'} | {'https://huntr.dev/bounties/499688c4-6ac4-4047-a868-7922c3eab369', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0339', 'https://github.com/janeczku/calibre-web/releases/tag/0.6.16', 'https://github.com/janeczku/calibre-web/commit/3b216bfa07ec7992eff03e55d61732af6df9bb92', 'https://github.com/janeczku/calibre-web/commit/35f6f4c727c887f8f3607fe3233dbc1980d15020', 'https://github.com/janeczku/calibre-web'} | null |
PyPI | PYSEC-2020-80 | null | 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-2020-11538', 'GHSA-43fq-w8qq-v88h'} | 2020-07-27T19:15:00Z | 2020-06-25T19:15:00Z | null | null | null | {'https://pillow.readthedocs.io/en/stable/releasenotes/index.html', 'https://github.com/advisories/GHSA-43fq-w8qq-v88h', 'https://github.com/python-pillow/Pillow/pull/4538', 'https://usn.ubuntu.com/4430-2/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/', 'https://usn.ubuntu.com/4430-1/', 'https://github.com/python-pillow/Pillow/pull/4504', 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/'} | null |
PyPI | PYSEC-2021-174 | null | TensorFlow is an end-to-end open source platform for machine learning. 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. 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. | {'GHSA-8c89-2vwr-chcq', 'CVE-2021-29537'} | 2021-08-27T03:22:28.012732Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/f6c40f0c6cbf00d46c7717a26419f2062f2f8694', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8c89-2vwr-chcq'} | null |
PyPI | PYSEC-2016-18 | null | Django before 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3, when settings.DEBUG is True, allow remote attackers to conduct DNS rebinding attacks by leveraging failure to validate the HTTP Host header against settings.ALLOWED_HOSTS. | {'CVE-2016-9014'} | 2021-07-15T02:22:10.532243Z | 2016-12-09T20:59:00Z | null | null | null | {'http://www.securitytracker.com/id/1037159', 'http://www.debian.org/security/2017/dsa-3835', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QXDKJYHN74BWY3P7AR2UZDVJREQMRE6S/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OG5ROMUPS6C7BXELD3TAUUH7OBYV56WQ/', 'http://www.ubuntu.com/usn/USN-3115-1', 'https://www.djangoproject.com/weblog/2016/nov/01/security-releases/', 'http://www.securityfocus.com/bid/94068'} | null |
PyPI | PYSEC-2014-25 | null | The from_yaml method in serializers.py in Django Tastypie before 0.9.10 does not properly deserialize YAML data, which allows remote attackers to execute arbitrary Python code via vectors related to the yaml.load method. | {'CVE-2011-4104'} | 2021-07-25T23:34:28.733002Z | 2014-10-27T01:55:00Z | null | null | null | {'http://www.openwall.com/lists/oss-security/2011/11/02/1', 'https://github.com/toastdriven/django-tastypie/commit/e8af315211b07c8f48f32a063233cc3f76dd5bc2', 'https://groups.google.com/forum/#!topic/django-tastypie/i2aNGDHTUBI', 'http://www.openwall.com/lists/oss-security/2011/11/02/7', 'https://www.djangoproject.com/weblog/2011/nov/01/piston-and-tastypie-security-releases/'} | null |
PyPI | PYSEC-2021-524 | null | TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `EmbeddingLookup` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/e4b29809543b250bc9b19678ec4776299dd569ba/tensorflow/lite/kernels/embedding_lookup.cc#L73-L74). An attacker can craft a model such that the first dimension of the `value` input is 0. 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. | {'GHSA-4vrf-ff7v-hpgr', 'CVE-2021-29596'} | 2021-12-09T06:34:58.287349Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4vrf-ff7v-hpgr', 'https://github.com/tensorflow/tensorflow/commit/f61c57bd425878be108ec787f4d96390579fb83e'} | null |
PyPI | GHSA-q4xr-rc97-m4xx | OS Command Injection in celery | This affects the package celery before 5.2.2. It 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-2021-23727'} | 2022-03-03T05:13:29.263125Z | 2022-01-06T22:22:02Z | HIGH | null | {'CWE-78', 'CWE-77'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23727', 'https://github.com/celery/celery', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SYXRGHWHD2WWMHBWCVD5ULVINPKNY3P5/', 'https://snyk.io/vuln/SNYK-PYTHON-CELERY-2314953', 'https://github.com/celery/celery/blob/master/Changelog.rst%23522'} | null |
PyPI | PYSEC-2021-42 | null | 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. | {'GHSA-95q3-8gr9-gm8w', 'CVE-2021-27923'} | 2021-03-23T19:48:00Z | 2021-03-03T09:15:00Z | null | null | null | {'https://github.com/advisories/GHSA-95q3-8gr9-gm8w', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZTSY25UJU7NJUFHH3HWT575LT4TDFWBZ/', 'https://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S7G44Z33J4BNI2DPDROHWGVG2U7ZH5JU/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TQQY6472RX4J2SUJENWDZAWKTJJGP2ML/'} | null |
PyPI | PYSEC-2021-748 | null | TensorFlow is an end-to-end open source platform for machine learning. 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. We have patched the issue in GitHub commit 5dc7f6981fdaf74c8c5be41f393df705841fb7c5. 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-2021-37637', 'GHSA-c9qf-r67m-p7cg'} | 2021-12-09T06:35:35.492639Z | 2021-08-12T19:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/5dc7f6981fdaf74c8c5be41f393df705841fb7c5', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c9qf-r67m-p7cg'} | null |
PyPI | PYSEC-2021-318 | null | 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. | {'CVE-2021-21996'} | 2022-03-28T17:35:08.348296Z | 2021-09-08T15:15:00Z | null | null | null | {'https://saltproject.io/security_announcements/salt-security-advisory-2021-sep-02/'} | null |
PyPI | GHSA-p7h9-vf92-5fj5 | Moderate severity vulnerability that affects Products.CMFPlone and Products.PasswordResetTool | 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. | {'CVE-2011-1948'} | 2022-03-03T05:13:12.912723Z | 2018-07-23T19:50:57Z | MODERATE | null | {'CWE-79'} | {'https://exchange.xforce.ibmcloud.com/vulnerabilities/67693', 'https://nvd.nist.gov/vuln/detail/CVE-2011-1948', 'http://plone.org/products/plone/security/advisories/CVE-2011-1948', 'http://secunia.com/advisories/44775', 'http://osvdb.org/72727', 'http://securityreason.com/securityalert/8269', 'http://www.securityfocus.com/archive/1/518155/100/0/threaded', 'https://github.com/advisories/GHSA-p7h9-vf92-5fj5', 'http://www.securityfocus.com/bid/48005', 'http://secunia.com/advisories/44776'} | null |
PyPI | GHSA-89rj-5ggj-3p9p | Reachable Assertion in OpenCV. | 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-2018-5269'} | 2022-03-03T05:13:21.993398Z | 2021-10-12T22:03:41Z | MODERATE | null | {'CWE-617'} | {'https://lists.debian.org/debian-lts-announce/2018/04/msg00019.html', 'https://lists.debian.org/debian-lts-announce/2021/10/msg00028.html', 'http://www.securityfocus.com/bid/106945', 'https://github.com/opencv/opencv/pull/10563', 'https://nvd.nist.gov/vuln/detail/CVE-2018-5269', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00030.html', 'https://github.com/opencv/opencv/issues/10540', 'https://github.com/opencv/opencv-python'} | null |
PyPI | PYSEC-2020-318 | null | 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. The issue is patched in commit 33be22c65d86256e6826666662e40dbdfe70ee83, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | {'GHSA-xmq7-7fxm-rr79', 'CVE-2020-15203'} | 2021-12-09T06:35:13.671465Z | 2020-09-25T19:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/tensorflow/tensorflow/commit/33be22c65d86256e6826666662e40dbdfe70ee83'} | null |
PyPI | PYSEC-2017-35 | null | 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-2017-12791'} | 2021-09-29T02:54:43.147751Z | 2017-08-23T14:29:00Z | null | null | null | {'https://bugzilla.redhat.com/show_bug.cgi?id=1482006', 'http://www.securityfocus.com/bid/100384', 'https://docs.saltstack.com/en/latest/topics/releases/2017.7.1.html', 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872399', 'https://docs.saltstack.com/en/2016.11/topics/releases/2016.11.7.html', 'https://github.com/saltstack/salt/pull/42944'} | null |
PyPI | GHSA-6445-fm66-fvq2 | Integer overflows in Tensorflow | ### Impact
The [implementation of `AddManySparseToTensorsMap`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_tensors_map_ops.cc) 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):
```python
import tensorflow as tf
import numpy as np
tf.raw_ops.AddManySparseToTensorsMap(
sparse_indices=[(0,0),(0,1),(0,2),(4,3),(5,0),(5,1)],
sparse_values=[1,1,1,1,1,1],
sparse_shape=[2**32,2**32],
container='',
shared_name='',
name=None)
```
We are missing some validation on the shapes of the input tensors as well as directly constructing a large `TensorShape` with user-provided dimensions. The latter is an instance of [TFSA-2021-198](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md) (CVE-2021-41197) and is easily fixed by replacing a call to `TensorShape` constructor with a call to `BuildTensorShape` static helper factory.
### Patches
We have patched the issue in GitHub commits [b51b82fe65ebace4475e3c54eb089c18a4403f1c](https://github.com/tensorflow/tensorflow/commit/b51b82fe65ebace4475e3c54eb089c18a4403f1c) and [a68f68061e263a88321c104a6c911fe5598050a8](https://github.com/tensorflow/tensorflow/commit/a68f68061e263a88321c104a6c911fe5598050a8).
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.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia. | {'CVE-2022-23568'} | 2022-03-03T05:13:28.738493Z | 2022-02-09T23:39:11Z | MODERATE | null | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/commit/b51b82fe65ebace4475e3c54eb089c18a4403f1c', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23568', 'https://github.com/tensorflow/tensorflow', 'https://github.com/tensorflow/tensorflow/commit/a68f68061e263a88321c104a6c911fe5598050a8', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6445-fm66-fvq2', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_tensors_map_ops.cc'} | null |
PyPI | PYSEC-2020-38 | null | django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database. | {'GHSA-fvx8-v524-8579', 'CVE-2020-17495'} | 2020-08-14T20:09:00Z | 2020-08-11T21:15:00Z | null | null | null | {'https://github.com/advisories/GHSA-fvx8-v524-8579', 'https://github.com/celery/django-celery-results/issues/142'} | null |
PyPI | PYSEC-2019-165 | null | 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-2018-12680', 'GHSA-5xc6-fpc7-4qvg'} | 2021-08-25T04:57:20.831477Z | 2019-04-02T20:29:00Z | null | null | null | {'https://github.com/Tanganelli/CoAPthon/issues/135', 'https://github.com/advisories/GHSA-5xc6-fpc7-4qvg'} | null |
PyPI | GHSA-w9m4-7w72-r766 | Improper Access Control in Onionshare | Between September 26, 2021 and October 8, 2021, [Radically Open Security](https://www.radicallyopensecurity.com/) conducted a penetration test of OnionShare 2.4, funded by the Open Technology Fund's [Red Team lab](https://www.opentech.fund/labs/red-team-lab/). This is an issue from that penetration test.
- Vulnerability ID: OTF-004
- Vulnerability type: Improper Access Control
- Threat level: Moderate
## Description:
Chat participants can spoof their channel leave message, tricking others into assuming they left the chatroom.
## Technical description:
This series of screenshots show Alice, Bob and Eve joined a chatroom and are the only participants in the chatroom. Eve seemingly leaves the chatroom, which leads Bob and Alice to believe they are having a private chat. The last screenshot shows that Eve only emitted the leave message and is still able to read the chat and possibly write messages.
This can be reproduced by joining the chat with two different instances, where one instance has slightly modified the client-side JavaScript code similar to OTF-003 (page 22). The joined emit needs to be removed from the connect event handler. Therefore the modified client is not listed in the userlist and has no active session. The modified non-listed user also needs to change their username to Eve, which is not shown in the chatroom. The modified client then emits the disconnect event and their connection is no longer usable.
This results in the leave message for Eve and the removal from the user-list but not in removal of the original session of the Eve who announced to join the chat.
## Impact:
An adversary with access to the chat environment can spoof his leave event but still persist in the chat with access to all sent messages and the possibility to write in the chat using OTF-003 (page 22).
## Recommendation:
- Implement proper session handling | {'CVE-2022-21691'} | 2022-03-03T05:13:23.081879Z | 2022-01-21T23:20:22Z | MODERATE | null | {'CWE-306'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21691', 'https://github.com/onionshare/onionshare/security/advisories/GHSA-w9m4-7w72-r766', 'https://github.com/onionshare/onionshare/releases/tag/v2.5', 'https://github.com/onionshare/onionshare'} | null |
PyPI | PYSEC-2021-436 | null | Synapse is a package for Matrix homeservers written in Python 3/Twisted. Prior to version 1.47.1, Synapse instances with the media repository enabled can be tricked into downloading a file from a remote server into an arbitrary directory. No authentication is required for the affected endpoint. The last 2 directories and file name of the path are chosen randomly by Synapse and cannot be controlled by an attacker, which limits the impact. Homeservers with the media repository disabled are unaffected. Homeservers with a federation whitelist are also unaffected, since Synapse will check the remote hostname, including the trailing `../`s, against the whitelist. Server administrators should upgrade to 1.47.1 or later. Server administrators using a reverse proxy could, at the expense of losing media functionality, may block the certain endpoints as a workaround. Alternatively, non-containerized deployments can be adapted to use the hardened systemd config. | {'CVE-2021-41281', 'GHSA-3hfw-x7gx-437c'} | 2021-11-29T23:11:29.870597Z | 2021-11-23T20:15:00Z | null | null | null | {'https://github.com/matrix-org/synapse/security/advisories/GHSA-3hfw-x7gx-437c', 'https://github.com/matrix-org/synapse/releases/tag/v1.47.1', 'https://github.com/matrix-org/synapse/commit/91f2bd090'} | null |
PyPI | PYSEC-2021-573 | null | TensorFlow is an end-to-end open source platform for machine learning. 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 `&&`. We have patched the issue in GitHub commit e86605c0a336c088b638da02135ea6f9f6753618. 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. | {'GHSA-cm5x-837x-jf3c', 'CVE-2021-37660'} | 2021-12-09T06:35:04.091418Z | 2021-08-12T18:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/e86605c0a336c088b638da02135ea6f9f6753618', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cm5x-837x-jf3c'} | null |
PyPI | PYSEC-2014-72 | null | 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-2013-7110'} | 2021-07-25T23:34:56.578427Z | 2014-05-02T01:59:00Z | null | null | null | {'http://www.openwall.com/lists/oss-security/2013/12/13/5', 'https://github.com/transifex/transifex-client/issues/42', 'http://www.openwall.com/lists/oss-security/2013/12/15/3'} | null |
PyPI | PYSEC-2021-123 | null | The Python "Flask-Security-Too" package is used for adding security features to your Flask application. It is an is an independently maintained version of Flask-Security based on the 3.0.0 version of Flask-Security. All versions of Flask-Security-Too allow redirects after many successful views (e.g. /login) by honoring the ?next query param. There is code in FS to validate that the url specified in the next parameter is either relative OR has the same netloc (network location) as the requesting URL. This check utilizes Pythons urlsplit library. However many browsers are very lenient on the kind of URL they accept and 'fill in the blanks' when presented with a possibly incomplete URL. As a concrete example - setting http://login?next=\\\github.com will pass FS's relative URL check however many browsers will gladly convert this to http://github.com. Thus an attacker could send such a link to an unwitting user, using a legitimate site and have it redirect to whatever site they want. This is considered a low severity due to the fact that if Werkzeug is used (which is very common with Flask applications) as the WSGI layer, it by default ALWAYS ensures that the Location header is absolute - thus making this attack vector mute. It is possible for application writers to modify this default behavior by setting the `autocorrect_location_header=False`. | {'GHSA-6qmf-fj6m-686c', 'CVE-2021-32618'} | 2021-08-25T04:30:09.653075Z | 2021-05-17T18:15:00Z | null | null | null | {'https://github.com/Flask-Middleware/flask-security/issues/486', 'https://github.com/Flask-Middleware/flask-security/security/advisories/GHSA-6qmf-fj6m-686c'} | null |
PyPI | PYSEC-2018-51 | null | An issue was discovered in Bleach 2.1.x before 2.1.3. 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. | {'GHSA-m9mq-p2f9-cfqv', 'CVE-2018-7753'} | 2021-07-15T02:22:07.141398Z | 2018-03-07T23:29:00Z | null | null | null | {'https://github.com/advisories/GHSA-m9mq-p2f9-cfqv', 'https://github.com/mozilla/bleach/commit/c5df5789ec3471a31311f42c2d19fc2cf21b35ef', 'https://github.com/mozilla/bleach/releases/tag/v2.1.3', 'https://bugs.debian.org/892252'} | null |
PyPI | GHSA-2xgj-xhgf-ggjv | Heap buffer overflow in `BandedTriangularSolve` | ### Impact
An attacker can trigger a heap buffer overflow in Eigen implementation of `tf.raw_ops.BandedTriangularSolve`:
```python
import tensorflow as tf
import numpy as np
matrix_array = np.array([])
matrix_tensor = tf.convert_to_tensor(np.reshape(matrix_array,(0,1)),dtype=tf.float32)
rhs_array = np.array([1,1])
rhs_tensor = tf.convert_to_tensor(np.reshape(rhs_array,(1,2)),dtype=tf.float32)
tf.raw_ops.BandedTriangularSolve(matrix=matrix_tensor,rhs=rhs_tensor)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L269-L278) calls `ValidateInputTensors` for input validation but fails to validate that the two tensors are not empty:
```cc
void ValidateInputTensors(OpKernelContext* ctx, const Tensor& in0, const Tensor& in1) {
OP_REQUIRES(
ctx, in0.dims() >= 2,
errors::InvalidArgument("In[0] ndims must be >= 2: ", in0.dims()));
OP_REQUIRES(
ctx, in1.dims() >= 2,
errors::InvalidArgument("In[1] ndims must be >= 2: ", in1.dims()));
}
```
Furthermore, since `OP_REQUIRES` macro only stops execution of current function after setting `ctx->status()` to a non-OK value, callers of helper functions that use `OP_REQUIRES` must check value of `ctx->status()` before continuing. This doesn't happen [in this op's implementation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L219), hence the validation that is present is also not effective.
### Patches
We have patched the issue in GitHub commit [ba6822bd7b7324ba201a28b2f278c29a98edbef2](https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2) followed by GitHub commit [0ab290774f91a23bebe30a358fde4e53ab4876a0](https://github.com/tensorflow/tensorflow/commit/0ab290774f91a23bebe30a358fde4e53ab4876a0).
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.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Ye Zhang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-29612'} | 2022-03-03T05:12:03.570252Z | 2021-05-21T14:28:37Z | LOW | null | {'CWE-120'} | {'https://github.com/tensorflow/tensorflow/commit/0ab290774f91a23bebe30a358fde4e53ab4876a0', 'https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29612', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2xgj-xhgf-ggjv'} | null |
PyPI | PYSEC-2021-820 | null | TensorFlow is an open source platform for machine learning. 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. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range. | {'GHSA-h67m-xg8f-fxcf', 'CVE-2021-41213'} | 2021-12-09T06:35:43.109542Z | 2021-11-05T23:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcf', 'https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7'} | null |
PyPI | PYSEC-2010-31 | null | 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-2010-2491'} | 2021-08-27T03:22:19.672970Z | 2010-09-24T19:00:00Z | null | null | null | {'http://sourceforge.net/mailarchive/message.php?msg_name=AANLkTimIYtyRzTAReGmTSCEqPYBvwkkxrP6YKrdVm_nU%40mail.gmail.com', 'http://lists.fedoraproject.org/pipermail/package-announce/2010-September/048221.html', 'http://roundup.svn.sourceforge.net/viewvc/roundup/roundup/trunk/roundup/cgi/client.py?r1=4486&r2=4485&pathrev=4486', 'http://bugs.gentoo.org/show_bug.cgi?id=326395', 'http://roundup.svn.sourceforge.net/viewvc/roundup?view=revision&revision=4486', 'http://secunia.com/advisories/41585', 'http://secunia.com/advisories/40433', 'http://www.openwall.com/lists/oss-security/2010/07/02/3', 'http://www.securityfocus.com/bid/41326', 'http://www.openwall.com/lists/oss-security/2010/07/02/12', 'https://bugzilla.redhat.com/show_bug.cgi?id=610861', 'http://lists.fedoraproject.org/pipermail/package-announce/2010-September/048061.html', 'http://issues.roundup-tracker.org/issue2550654', 'http://lists.fedoraproject.org/pipermail/package-announce/2010-September/048018.html'} | null |
PyPI | PYSEC-2020-123 | null | 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 is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. | {'CVE-2020-15200', 'GHSA-x7rp-74x2-mjf3'} | 2021-09-01T08:19:33.281926Z | 2020-09-25T19:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x7rp-74x2-mjf3'} | null |
PyPI | GHSA-6rvj-pw9w-jcvc | Information disclosure vulnerability in OnionShare | 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-2021-41867'} | 2022-03-03T05:12:50.763741Z | 2021-11-19T20:39:35Z | MODERATE | null | {'CWE-200'} | {'https://github.com/onionshare/onionshare/compare/v2.3.3...v2.4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41867', 'https://www.ihteam.net/advisory/onionshare/', 'https://github.com/onionshare/onionshare'} | null |
PyPI | GHSA-c87f-fq5g-63r2 | Cross-site scripting in Unicorn framework | The Unicorn framework through 0.35.3 for Django allows XSS via component.name. | {'CVE-2021-42053'} | 2022-03-03T05:14:06.409650Z | 2021-10-12T17:51:11Z | MODERATE | null | {'CWE-79'} | {'https://github.com/adamghill/django-unicorn/compare/0.35.3...0.36.0', 'https://github.com/adamghill/django-unicorn/pull/288/commits/aa5b9835d946bd9893ef02e556859e3ea62cc5e2', 'https://github.com/adamghill/django-unicorn', 'http://packetstormsecurity.com/files/164442/django-unicorn-0.35.3-Cross-Site-Scripting.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42053'} | null |
PyPI | PYSEC-2021-15 | null | git-big-picture before 1.0.0 mishandles ' characters in a branch name, leading to code execution. | {'CVE-2021-3028'} | 2021-01-19T14:43:00Z | 2021-01-13T17:15:00Z | null | null | null | {'https://github.com/git-big-picture/git-big-picture/pull/62', 'https://github.com/git-big-picture/git-big-picture/releases/tag/v1.0.0', 'https://github.com/git-big-picture/git-big-picture/pull/27'} | null |
PyPI | GHSA-8849-5h85-98qw | Out-of-bounds Write in OpenCV | 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. Product: AndroidVersions: Android-10Android ID: A-110986616 | {'CVE-2019-9423'} | 2022-03-03T05:13:31.666148Z | 2021-10-12T22:22:17Z | HIGH | null | {'CWE-787'} | {'http://www.openwall.com/lists/oss-security/2019/10/27/1', 'https://nvd.nist.gov/vuln/detail/CVE-2019-9423', 'https://source.android.com/security/bulletin/android-10', 'http://www.openwall.com/lists/oss-security/2020/12/05/1', 'http://www.openwall.com/lists/oss-security/2019/10/25/17', 'http://www.openwall.com/lists/oss-security/2019/11/07/1', 'https://github.com/opencv/opencv-python'} | null |
PyPI | PYSEC-2017-62 | null | 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. | {'CVE-2016-7139'} | 2021-07-25T23:34:49.468488Z | 2017-03-07T16:59:00Z | null | null | null | {'http://seclists.org/fulldisclosure/2016/Oct/80', 'http://www.securityfocus.com/archive/1/539572/100/0/threaded', 'http://www.securityfocus.com/bid/92752', 'http://www.openwall.com/lists/oss-security/2016/09/05/5', 'http://www.openwall.com/lists/oss-security/2016/09/05/4', 'http://packetstormsecurity.com/files/139110/Plone-CMS-4.3.11-5.0.6-XSS-Traversal-Open-Redirection.html', 'https://plone.org/security/hotfix/20160830/non-persistent-xss-in-plone'} | null |
PyPI | GHSA-2647-c639-qv2j | Server-Side Request Forgery in calibreweb | calibreweb prior to version 0.6.17 is vulnerable to server-side request forgery (SSRF). This is due to an incomplete fix for [CVE-2022-0339](https://github.com/advisories/GHSA-4w8p-x6g8-fv64). The blacklist does not check for `0.0.0.0`, which would result in a payload of `0.0.0.0` resolving to `localhost`. | {'CVE-2022-0766'} | 2022-03-18T21:32:04.972354Z | 2022-03-08T00:00:31Z | CRITICAL | null | {'CWE-918'} | {'https://github.com/janeczku/calibre-web', 'https://huntr.dev/bounties/7f2a5bb4-e6c7-4b6a-b8eb-face9e3add7b', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0766', 'https://github.com/janeczku/calibre-web/commit/965352c8d96c9eae7a6867ff76b0db137d04b0b8'} | null |
PyPI | PYSEC-2015-9 | null | The utils.http.is_safe_url function in Django before 1.4.20, 1.5.x, 1.6.x before 1.6.11, 1.7.x before 1.7.7, and 1.8.x before 1.8c1 does not properly validate URLs, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a control character in a URL, as demonstrated by a \x08javascript: URL. | {'CVE-2015-2317'} | 2021-09-01T08:35:43.249549Z | 2015-03-25T14:59:00Z | null | null | null | {'http://lists.opensuse.org/opensuse-updates/2015-04/msg00001.html', 'http://ubuntu.com/usn/usn-2539-1', 'http://www.securityfocus.com/bid/73319', 'http://www.debian.org/security/2015/dsa-3204', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-June/160263.html', 'http://lists.opensuse.org/opensuse-updates/2015-09/msg00035.html', 'http://www.mandriva.com/security/advisories?name=MDVSA-2015:195', 'http://www.oracle.com/technetwork/topics/security/bulletinapr2015-2511959.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-April/155421.html', 'https://www.djangoproject.com/weblog/2015/mar/18/security-releases/'} | null |
PyPI | GHSA-f6f2-pwrj-64h3 | Moderate severity vulnerability that affects tryton | 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-2019-10868'} | 2022-03-03T05:13:05.667566Z | 2019-04-10T14:31:37Z | MODERATE | null | {'CWE-862'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10868', 'https://seclists.org/bugtraq/2019/Apr/14', 'https://github.com/advisories/GHSA-f6f2-pwrj-64h3', 'https://discuss.tryton.org/t/security-release-for-issue8189/1262', 'https://hg.tryton.org/trytond/rev/f58bbfe0aefb', 'https://www.debian.org/security/2019/dsa-4426'} | null |
PyPI | GHSA-58c7-px5v-82hh | Potential sensitive information disclosed in error reports | django-registration is a user-registration application for Django.
### Impact
The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django.
Triggering this requires the following conditions:
* A site is using django-registration < 3.1.2
* The site has detailed error reports (such as Django's [emailed error reports to site staff/developers](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#email-reports)) enabled
* A server-side error (HTTP 5xx) occurs during an attempt by a user to register an account
Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).
### Patches
As of version 3.1.2, django-registration properly applies Django's `sensitive_post_parameters()` decorator to the base user-registration view, which will cause all data from the HTTP request body to be filtered from detailed error reports in the event of a server-side crash during user account registration.
Note that as applied, this filters *all* HTTP request data from error reports. To selectively allow some fields but not others, see Django's own documentation (in references) and the notes below for how to apply `sensitive_post_parameters()` manually to a particular codebase's `RegistrationView` subclass(es).
### Workarounds
Users who cannot upgrade quickly can apply the `django.views.decorators.debug.sensitive_post_parameters()` decorator to their own registration views. The decorator should be applied on the `dispatch()` method of the appropriate `RegistrationView` class, using Django's `method_decorator()` helper. For example:
```python
from django.utils.decorators import method_decorator
from django.views.decorators.debug import sensitive_post_parameters
from django_registration.views import RegistrationView
class MyRegistrationView(RegistrationView):
"""
A RegistrationView subclass manually protected against sensitive information disclosure
in error reports.
"""
@method_decorator(sensitive_post_parameters())
def dispatch(self, *args, **kwargs):
return super().dispatch(*args, **kwargs)
```
### References
* Django's documentation on [error reporting in production](https://docs.djangoproject.com/en/3.1/howto/error-reporting/)
* [How Django's sensitive-data filters work](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#filtering-error-reports) | {'CVE-2021-21416'} | 2022-03-03T05:13:33.983589Z | 2021-04-06T17:28:59Z | LOW | null | {'CWE-201', 'CWE-209'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21416', 'https://github.com/ubernostrum/django-registration/security/advisories/GHSA-58c7-px5v-82hh'} | null |
PyPI | GHSA-r4c4-5fpq-56wg | Heap OOB in boosted trees | ### Impact
An attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`:
```python
import tensorflow as tf
tf.raw_ops.BoostedTreesSparseCalculateBestFeatureSplit(
node_id_range=[0,10],
stats_summary_indices=[[1, 2, 3, 0x1000000]],
stats_summary_values=[1.0],
stats_summary_shape=[1,1,1,1],
l1=l2=[1.0],
tree_complexity=[0.5],
min_node_weight=[1.0],
logits_dimension=3,
split_type='inequality')
```
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.
### Patches
We have patched the issue in GitHub commit [e84c975313e8e8e38bb2ea118196369c45c51378](https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378).
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.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37664'} | 2022-03-03T05:13:33.318020Z | 2021-08-25T14:42:20Z | HIGH | null | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r4c4-5fpq-56wg', 'https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37664'} | null |
PyPI | GHSA-hc6c-75p4-hmq4 | Reference binding to null pointer in `MatrixDiag*` ops | ### Impact
The implementation of [`MatrixDiag*` operations](https://github.com/tensorflow/tensorflow/blob/4c4f420e68f1cfaf8f4b6e8e3eb857e9e4c3ff33/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L195-L197) does not validate that the tensor arguments are non-empty:
```cc
num_rows = context->input(2).flat<int32>()(0);
num_cols = context->input(3).flat<int32>()(0);
padding_value = context->input(4).flat<T>()(0);
```
Thus, users can trigger null pointer dereferences if any of the above tensors are null:
```python
import tensorflow as tf
d = tf.convert_to_tensor([],dtype=tf.float32)
p = tf.convert_to_tensor([],dtype=tf.float32)
tf.raw_ops.MatrixDiagV2(diagonal=d, k=0, num_rows=0, num_cols=0, padding_value=p)
```
Changing from `tf.raw_ops.MatrixDiagV2` to `tf.raw_ops.MatrixDiagV3` still reproduces the issue.
### Patches
We have patched the issue in GitHub commit [a7116dd3913c4a4afd2a3a938573aa7c785fdfc6](https://github.com/tensorflow/tensorflow/commit/a7116dd3913c4a4afd2a3a938573aa7c785fdfc6).
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.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Ye Zhang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-29515'} | 2022-03-03T05:13:41.020454Z | 2021-05-21T14:20:54Z | LOW | null | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/commit/a7116dd3913c4a4afd2a3a938573aa7c785fdfc6', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hc6c-75p4-hmq4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29515'} | null |
PyPI | GHSA-v82p-hv3v-p6qp | Incomplete validation in MKL requantization | ### Impact
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:
```python
import tensorflow as tf
tf.raw_ops.RequantizationRangePerChannel(
input=[],
input_min=[0,0,0,0,0],
input_max=[1,1,1,1,1],
clip_value_max=1)
```
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`:
```python
import tensorflow as tf
from tensorflow.python.ops import gen_math_ops
gen_math_ops.requantize_per_channel(
input=[],
input_min=[-100,-100,-100,-100,-100],
input_max=[-100,-100,-100],
requested_output_min=[-100,-100,-100,-100,-100],
requested_output_max=[],
out_type=tf.int)
```
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.
### Patches
We have patched the issue in GitHub commit [9e62869465573cb2d9b5053f1fa02a81fce21d69](https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69) and in the Github commit [203214568f5bc237603dbab6e1fd389f1572f5c9](https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9).
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.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37665'} | 2022-03-03T05:13:28.232290Z | 2021-08-25T14:42:16Z | HIGH | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37665', 'https://github.com/tensorflow/tensorflow', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-v82p-hv3v-p6qp', 'https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69', 'https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9'} | null |
PyPI | PYSEC-2013-21 | null | The is_safe_url function in utils/http.py in Django 1.4.x before 1.4.6, 1.5.x before 1.5.2, and 1.6 before beta 2 treats a URL's scheme as safe even if it is not HTTP or HTTPS, which might introduce cross-site scripting (XSS) or other vulnerabilities into Django applications that use this function, as demonstrated by "the login view in django.contrib.auth.views" and the javascript: scheme. | {'CVE-2013-6044'} | 2021-07-15T02:22:09.088856Z | 2013-10-04T17:55:00Z | null | null | null | {'https://exchange.xforce.ibmcloud.com/vulnerabilities/86437', 'http://lists.opensuse.org/opensuse-updates/2013-10/msg00015.html', 'https://github.com/django/django/commit/ec67af0bd609c412b76eaa4cc89968a2a8e5ad6a', 'http://secunia.com/advisories/54476', 'https://github.com/django/django/commit/1a274ccd6bc1afbdac80344c9b6e5810c1162b5f', 'http://seclists.org/oss-sec/2013/q3/411', 'http://rhn.redhat.com/errata/RHSA-2013-1521.html', 'http://www.securitytracker.com/id/1028915', 'https://www.djangoproject.com/weblog/2013/aug/13/security-releases-issued', 'http://www.debian.org/security/2013/dsa-2740', 'http://seclists.org/oss-sec/2013/q3/369', 'http://www.securityfocus.com/bid/61777', 'https://github.com/django/django/commit/ae3535169af804352517b7fea94a42a1c9c4b762'} | null |
PyPI | GHSA-hm45-mgqm-gjm4 | Remote Code Execution (RCE) Exploit on Cross Site Scripting (XSS) Vulnerability | ### Impact
A RCE exploit has been discovered in the Red Discord Bot - Dashboard Webserver: 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.
### Patches
This high severity exploit has been fixed on version `0.1.7a`.
### Workarounds
There are no workarounds, bot owners must upgrade their relevant packages (Dashboard module and Dashboard webserver) in order to patch this issue
### References
- 99d88b8
- a6b9785
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Cog-Creators/Red-Dashboard](https://github.com/Cog-Creators/Red-Dashboard/issues/new/choose)
* Over on the official [Red Server](https://discord.gg/red) or at the Third Party Server [Toxic Layer](https://discord.gg/vQZTdB9) | {'CVE-2020-26249'} | 2022-03-03T05:13:57.306089Z | 2020-12-08T23:55:54Z | HIGH | null | {'CWE-79'} | {'https://github.com/Cog-Creators/Red-Dashboard/security/advisories/GHSA-hm45-mgqm-gjm4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26249', 'https://github.com/Cog-Creators/Red-Dashboard/commit/a6b9785338003ec87fb75305e7d1cc2d40c7ab91', 'https://pypi.org/project/Red-Dashboard', 'https://github.com/Cog-Creators/Red-Dashboard/commit/99d88b840674674166ce005b784ae8e31e955ab1'} | null |
PyPI | PYSEC-2021-420 | null | TensorFlow is an open source platform for machine learning. 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. We have patched this by adding a `safe` flag which defaults to `True` and an explicit warning for users. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range. | {'GHSA-3rcw-9p9x-582v', 'CVE-2021-41228'} | 2021-11-13T06:52:46.380831Z | 2021-11-05T23:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3rcw-9p9x-582v', 'https://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7'} | null |
PyPI | GHSA-3448-vrgh-85xr | NULL Pointer Dereference in OpenCV. | 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-2019-14493'} | 2022-03-03T05:14:17.781507Z | 2021-10-12T22:21:43Z | HIGH | null | {'CWE-476'} | {'https://lists.debian.org/debian-lts-announce/2021/10/msg00028.html', 'https://github.com/opencv/opencv/compare/371bba8...ddbd10c', 'https://github.com/opencv/opencv/issues/15127', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14493', 'https://github.com/opencv/opencv-python'} | null |
PyPI | PYSEC-2019-173 | null | In Apache Incubator Superset before 0.32, a user can view database names that he has no access to on a dropdown list in SQLLab | {'CVE-2019-12414', 'GHSA-9c29-9h4m-wg5p'} | 2019-12-19T18:24:00Z | 2019-12-16T22:15:00Z | null | null | null | {'https://lists.apache.org/thread.html/396034aabe08dd349ff44eb062c718aadcf1b4e86f6372c7d5e988c0%40%3Cdev.superset.apache.org%3E', 'https://github.com/advisories/GHSA-9c29-9h4m-wg5p'} | null |
PyPI | GHSA-wh4h-v3f2-r2pp | Moderate severity vulnerability that affects django | Django 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied value to the django.utils.numberformat.format() function. | {'CVE-2019-6975'} | 2022-03-03T05:12:50.822993Z | 2019-02-12T15:36:37Z | HIGH | null | {'CWE-770'} | {'https://github.com/django/django', 'https://www.openwall.com/lists/oss-security/2019/02/11/1', 'https://usn.ubuntu.com/3890-1/', 'https://seclists.org/bugtraq/2019/Jul/10', 'https://www.djangoproject.com/weblog/2019/feb/11/security-releases/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/66WMXHGBXD7GSM3PEXVCMCAGLMQYHZCU/', 'https://github.com/advisories/GHSA-wh4h-v3f2-r2pp', 'https://www.debian.org/security/2019/dsa-4476', 'http://www.securityfocus.com/bid/106964', 'https://docs.djangoproject.com/en/dev/releases/security/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-6975', 'https://groups.google.com/forum/#!topic/django-announce/WTwEAprR0IQ', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVXDOVCXLD74SHR2BENGCE2OOYYYWJHZ/'} | null |
PyPI | GHSA-7wph-fc4w-wqp2 | Moderate severity vulnerability that affects django | The password reset functionality in django.contrib.auth in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not validate the length of a string representing a base36 timestamp, which allows remote attackers to cause a denial of service (resource consumption) via a URL that specifies a large base36 integer. | {'CVE-2010-4535'} | 2022-03-03T05:12:54.357268Z | 2018-07-23T19:51:59Z | MODERATE | null | {'CWE-20'} | {'http://www.vupen.com/english/advisories/2011/0098', 'https://github.com/django/django', 'https://nvd.nist.gov/vuln/detail/CVE-2010-4535', 'http://secunia.com/advisories/42913', 'http://www.vupen.com/english/advisories/2011/0048', 'http://secunia.com/advisories/42827', 'http://www.securityfocus.com/bid/45563', 'https://github.com/advisories/GHSA-7wph-fc4w-wqp2', 'http://www.openwall.com/lists/oss-security/2011/01/03/5', 'http://www.ubuntu.com/usn/USN-1040-1', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053041.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053072.html', 'http://www.djangoproject.com/weblog/2010/dec/22/security/', 'http://www.openwall.com/lists/oss-security/2010/12/23/4', 'https://bugzilla.redhat.com/show_bug.cgi?id=665373', 'http://code.djangoproject.com/changeset/15032', 'http://secunia.com/advisories/42715'} | null |
PyPI | PYSEC-2022-13 | null | Wagtail is a Django based content management system focused on flexibility and user experience. 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. | {'GHSA-xqxm-2rpm-3889', 'CVE-2022-21683'} | 2022-01-26T19:22:48.977586Z | 2022-01-18T18:15:00Z | null | null | null | {'https://github.com/wagtail/wagtail/security/advisories/GHSA-xqxm-2rpm-3889', 'https://github.com/wagtail/wagtail/releases/tag/v2.15.2', 'https://github.com/wagtail/wagtail/commit/5fe901e5d86ed02dbbb63039a897582951266afd'} | null |
PyPI | PYSEC-2020-135 | null | 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 is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be 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. | {'GHSA-hx2x-85gr-wrpq', 'CVE-2020-15212'} | 2020-10-01T18:20:00Z | 2020-09-25T19:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hx2x-85gr-wrpq', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a'} | null |
PyPI | PYSEC-2010-27 | null | Race condition in ZEO/StorageServer.py in Zope Object Database (ZODB) before 3.10.0 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, an unexpected value of None for the address, or an ECONNABORTED, EAGAIN, or EWOULDBLOCK error, a related issue to CVE-2010-3492. | {'CVE-2010-3495'} | 2021-07-16T01:31:36.925737Z | 2010-10-19T20:00:00Z | null | null | null | {'http://bugs.python.org/issue6706', 'http://www.openwall.com/lists/oss-security/2010/09/11/2', 'http://lists.opensuse.org/opensuse-security-announce/2010-12/msg00006.html', 'http://pypi.python.org/pypi/ZODB3/3.10.0#id1', 'http://www.openwall.com/lists/oss-security/2010/09/09/6', 'http://www.openwall.com/lists/oss-security/2010/09/24/3', 'http://secunia.com/advisories/41755', 'https://bugs.launchpad.net/zodb/+bug/135108', 'http://www.openwall.com/lists/oss-security/2010/09/22/3'} | null |
PyPI | PYSEC-2021-836 | null | Invenio-Drafts-Resources is a submission/deposit module for Invenio, a software framework for research data management. Invenio-Drafts-Resources prior to versions 0.13.7 and 0.14.6 does not properly check permissions when a record is published. The vulnerability is exploitable in a default installation of InvenioRDM. An authenticated a user is able via REST API calls to publish draft records of other users if they know the record identifier and the draft validates (e.g. all require fields filled out). An attacker is not able to modify the data in the record, and thus e.g. *cannot* change a record from restricted to public. The problem is patched in Invenio-Drafts-Resources v0.13.7 and 0.14.6, which is part of InvenioRDM v6.0.1 and InvenioRDM v7.0 respectively. | {'CVE-2021-43781', 'GHSA-xr38-w74q-r8jv'} | 2021-12-09T07:29:22.280279Z | 2021-12-06T18:15:00Z | null | null | null | {'https://github.com/inveniosoftware/invenio-drafts-resources/commit/039b0cff1ad4b952000f4d8c3a93f347108b6626', 'https://github.com/inveniosoftware/invenio-drafts-resources/security/advisories/GHSA-xr38-w74q-r8jv'} | null |
PyPI | PYSEC-2018-47 | null | Cross-site scripting (XSS) vulnerability in the link dialogue in GUI editor in MoinMoin before 1.9.10 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. | {'GHSA-42fp-4hm3-j8r7', 'CVE-2017-5934'} | 2021-07-05T00:01:23.080305Z | 2018-10-15T19:29:00Z | null | null | null | {'https://www.debian.org/security/2018/dsa-4318', 'http://moinmo.in/SecurityFixes', 'https://usn.ubuntu.com/3794-1/', 'https://github.com/moinwiki/moin-1.9/commit/70955a8eae091cc88fd9a6e510177e70289ec024', 'http://lists.opensuse.org/opensuse-security-announce/2018-10/msg00024.html', 'https://lists.debian.org/debian-lts-announce/2018/10/msg00007.html', 'https://github.com/advisories/GHSA-42fp-4hm3-j8r7'} | null |
PyPI | PYSEC-2021-135 | null | Synapse is a Matrix reference homeserver written in python (pypi package matrix-synapse). Matrix is an ecosystem for open federated Instant Messaging and VoIP. In Synapse before version 1.33.2 "Push rules" can specify conditions under which they will match, including `event_match`, which matches event content against a pattern including wildcards. Certain patterns can cause very poor performance in the matching engine, leading to a denial-of-service when processing moderate length events. The issue is patched in version 1.33.2. A potential workaround might be to prevent users from making custom push rules, by blocking such requests at a reverse-proxy. | {'GHSA-x345-32rc-8h85', 'CVE-2021-29471'} | 2021-08-27T03:22:06.756710Z | 2021-05-11T15:15:00Z | null | null | null | {'https://github.com/matrix-org/synapse/releases/tag/v1.33.2', 'https://github.com/matrix-org/synapse/commit/03318a766cac9f8b053db2214d9c332a977d226c', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-x345-32rc-8h85'} | null |
PyPI | GHSA-hxmp-pqch-c8mm | Denial of service attack via incorrect parameters in Matrix Synapse | ### Impact
A malicious or poorly-implemented homeserver can inject malformed events into a room by specifying a different room id in the path of a `/send_join`, `/send_leave`, `/invite` or `/exchange_third_party_invite` request.
This can lead to a denial of service in which future events will not be correctly sent to other servers over federation.
This affects any server which accepts federation requests from untrusted servers.
### Patches
Issue is resolved by https://github.com/matrix-org/synapse/pull/8776.
### Workarounds
Homeserver administrators could limit access to the federation API to trusted servers (for example via `federation_domain_whitelist`). | {'CVE-2020-26257'} | 2022-03-03T05:12:45.625321Z | 2020-12-09T18:21:29Z | LOW | null | {'CWE-400', 'CWE-74', 'CWE-79'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QR4MMYZKX5N5GYGH4H5LBUUC5TLAFHI7/', 'https://github.com/matrix-org/synapse/blob/develop/CHANGES.md#synapse-1231-2020-12-09', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26257', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DBTIU3ZNBFWZ56V4X7JIAD33V5H2GOMC/', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-hxmp-pqch-c8mm', 'https://github.com/matrix-org/synapse/pull/8776', 'https://github.com/matrix-org/synapse/commit/3ce2f303f15f6ac3dc352298972dc6e04d9b7a8b'} | null |
PyPI | PYSEC-2014-64 | null | 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-2013-4200'} | 2021-07-25T23:34:47.517338Z | 2014-01-21T16:06:00Z | null | null | null | {'http://plone.org/products/plone-hotfix/releases/20130618', 'http://www.securityfocus.com/archive/1/530787/100/0/threaded', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-4200', 'http://www.openwall.com/lists/oss-security/2013/08/01/2', 'http://plone.org/products/plone/security/advisories/20130618-announcement'} | null |
PyPI | PYSEC-2021-565 | null | TensorFlow is an end-to-end open source platform for machine learning. 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. We have patched the issue in GitHub commit 5ecec9c6fbdbc6be03295685190a45e7eee726ab. 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-2021-37652', 'GHSA-m7fm-4jfh-jrg6'} | 2021-12-09T06:35:03.429357Z | 2021-08-12T22:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/5ecec9c6fbdbc6be03295685190a45e7eee726ab', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m7fm-4jfh-jrg6'} | null |
PyPI | GHSA-83rh-hx5x-q9p5 | Out-of-bounds Read in OpenCV | 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-2017-18009'} | 2022-03-03T05:13:35.314834Z | 2021-10-12T22:03:23Z | HIGH | null | {'CWE-125'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-18009', 'https://github.com/opencv/opencv/issues/10479', 'http://www.securityfocus.com/bid/106945', 'https://github.com/opencv/opencv/pull/10480/commits/4ca89db22dea962690f31c1781bce5937ee91837', 'https://github.com/opencv/opencv-python'} | null |
PyPI | GHSA-75f6-78jr-4656 | Null pointer dereference in `EditDistance` | ### Impact
An attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.EditDistance`:
```python
import tensorflow as tf
hypothesis_indices = tf.constant([247, 247, 247], shape=[1, 3], dtype=tf.int64)
hypothesis_values = tf.constant([-9.9999], shape=[1], dtype=tf.float32)
hypothesis_shape = tf.constant([0, 0, 0], shape=[3], dtype=tf.int64)
truth_indices = tf.constant([], shape=[0, 3], dtype=tf.int64)
truth_values = tf.constant([], shape=[0], dtype=tf.float32)
truth_shape = tf.constant([0, 0, 0], shape=[3], dtype=tf.int64)
tf.raw_ops.EditDistance(
hypothesis_indices=hypothesis_indices, hypothesis_values=hypothesis_values,
hypothesis_shape=hypothesis_shape, truth_indices=truth_indices,
truth_values=truth_values, truth_shape=truth_shape, normalize=True)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/79865b542f9ffdc9caeb255631f7c56f1d4b6517/tensorflow/core/kernels/edit_distance_op.cc#L103-L159) has incomplete validation of the input parameters.
In the above scenario, an attacker causes an allocation of an empty tensor for the output:
```cc
OP_REQUIRES_OK(ctx, ctx->allocate_output("output", output_shape, &output));
auto output_t = output->flat<float>();
output_t.setZero();
```
Because `output_shape` has 0 elements, the result of `output->flat<T>()` has an empty buffer, so calling `setZero` would result in a null dereference.
### Patches
We have patched the issue in GitHub commit [f4c364a5d6880557f6f5b6eb5cee2c407f0186b3](https://github.com/tensorflow/tensorflow/commit/f4c364a5d6880557f6f5b6eb5cee2c407f0186b3).
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.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team. | {'CVE-2021-29564'} | 2022-03-03T05:12:50.250682Z | 2021-05-21T14:25:08Z | LOW | null | {'CWE-476'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29564', 'https://github.com/tensorflow/tensorflow/commit/f4c364a5d6880557f6f5b6eb5cee2c407f0186b3', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-75f6-78jr-4656'} | null |
PyPI | PYSEC-2021-709 | null | TensorFlow is an end-to-end open source platform for machine learning. 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. 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. | {'GHSA-9xh4-23q4-v6wr', 'CVE-2021-29583'} | 2021-12-09T06:35:29.040868Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9xh4-23q4-v6wr'} | null |
PyPI | GHSA-c2w9-48qc-qpj4 | High severity vulnerability that affects ansible | 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. | {'CVE-2017-2809'} | 2022-03-03T05:12:59.249805Z | 2018-07-13T15:16:54Z | HIGH | null | {'CWE-94'} | {'https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0305', 'https://github.com/tomoh1r/ansible-vault/issues/4', 'https://nvd.nist.gov/vuln/detail/CVE-2017-2809', 'https://github.com/advisories/GHSA-c2w9-48qc-qpj4', 'https://github.com/tomoh1r/ansible-vault/blob/v1.0.5/CHANGES.txt', 'http://www.securityfocus.com/bid/100824', 'https://github.com/tomoh1r/ansible-vault/commit/3f8f659ef443ab870bb19f95d43543470168ae04', 'https://github.com/tomoh1r/ansible-vault'} | null |
PyPI | PYSEC-2021-359 | null | Flask-AppBuilder is an application development framework, built on top of Flask. In affected versions if using Flask-AppBuilder OAuth, an attacker can share a carefully crafted URL with a trusted domain for an application built with Flask-AppBuilder, this URL can redirect a user to a malicious site. This is an open redirect vulnerability. To resolve this issue upgrade to Flask-AppBuilder 3.2.2 or above. If upgrading is infeasible users may filter HTTP traffic containing `?next={next-site}` where the `next-site` domain is different from the application you are protecting as a workaround. | {'GHSA-624f-cqvr-3qw4', 'CVE-2021-32805'} | 2021-10-11T01:16:40.573932Z | 2021-09-08T18:15:00Z | null | null | null | {'https://github.com/dpgaspar/Flask-AppBuilder/commit/6af28521589599b1dbafd6313256229ee9a4fa74', 'https://github.com/dpgaspar/Flask-AppBuilder/security/advisories/GHSA-624f-cqvr-3qw4'} | null |
PyPI | GHSA-5crj-c72x-m7gq | Null pointer exception when `Exit` node is not preceded by `Enter` op | ### Impact
The [process of building the control flow graph](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/common_runtime/immutable_executor_state.cc#L284-L346) for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not:
```python
import tensorflow as tf
@tf.function
def func():
return tf.raw_ops.Exit(data=[False,False])
func()
```
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):
```cc
...
} else if (IsExit(curr_node)) {
// Exit to the parent frame.
parent = parent_nodes[curr_id];
frame_name = cf_info->frame_names[parent->id()];
...
```
When this is not the case, `parent` is `nullptr` so dereferencing it causes a crash.
### Patches
We have patched the issue in GitHub commit [05cbebd3c6bb8f517a158b0155debb8df79017ff](https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-41217'} | 2022-03-03T05:13:47.828697Z | 2021-11-10T18:55:11Z | MODERATE | null | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow', 'https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5crj-c72x-m7gq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41217'} | null |
PyPI | GHSA-cqv6-3phm-hcwx | Access to invalid memory during shape inference in `Cudnn*` ops | ### Impact
The [shape inference code](https://github.com/tensorflow/tensorflow/blob/9ff27787893f76d6971dcd1552eb5270d254f31b/tensorflow/core/ops/cudnn_rnn_ops.cc) for the `Cudnn*` operations in TensorFlow can be tricked into accessing invalid memory, via a heap buffer overflow:
```python
import tensorflow as tf
@tf.function
def func():
return tf.raw_ops.CudnnRNNV3(
input=[0.1, 0.1],
input_h=[0.5],
input_c=[0.1, 0.1, 0.1],
params=[0.5, 0.5],
sequence_lengths=[-1, 0, 1])
func()
```
This occurs because the ranks of the `input`, `input_h` and `input_c` parameters are not validated, but code assumes they have certain values:
```cc
auto input_shape = c->input(0);
auto input_h_shape = c->input(1);
auto seq_length = c->Dim(input_shape, 0);
auto batch_size = c->Dim(input_shape, 1); // assumes rank >= 2
auto num_units = c->Dim(input_h_shape, 2); // assumes rank >= 3
```
### Patches
We have patched the issue in GitHub commit [af5fcebb37c8b5d71c237f4e59c6477015c78ce6](https://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-41221'} | 2022-03-03T05:13:53.720856Z | 2021-11-10T18:50:17Z | HIGH | null | {'CWE-120', 'CWE-787'} | {'https://github.com/tensorflow/tensorflow', 'https://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41221', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqv6-3phm-hcwx'} | null |
PyPI | PYSEC-2017-74 | null | The tqdm._version module in tqdm versions 4.4.1 and 4.10 allows local users to execute arbitrary code via a crafted repo with a malicious git log in the current working directory. | {'CVE-2016-10075'} | 2021-07-25T23:34:56.013301Z | 2017-01-19T20:59:00Z | null | null | null | {'http://www.securityfocus.com/bid/95143', 'http://www.openwall.com/lists/oss-security/2016/12/28/8', 'https://github.com/tqdm/tqdm/issues/328', 'https://security.gentoo.org/glsa/201807-01'} | null |
PyPI | GHSA-f4g9-h89h-jgv9 | SAML XML Signature wrapping in PySAML2 | ### Impact
All users of pysaml2 that use the default `CryptoBackendXmlSec1` backend and need to verify signed SAML documents are impacted. `pysaml2 <= 6.4.1` does not validate the SAML document against an XML schema. This allows invalid XML documents to trick the verification process, by presenting elements with a valid signature inside elements whose content has been malformed. The verification is offloaded to `xmlsec1` and `xmlsec1` will not validate every signature in the given document, but only the first it finds in the given scope.
### Patches
Users should upgrade to pysaml2 `v6.5.0`.
### Workarounds
No workaround provided at this point.
### References
No references provided at this point.
### Credits
- Victor Schönfelder Garcia (isits AG International School of IT Security)
- Juraj Somorovsky (Paderborn University)
- Vladislav Mladenov (Ruhr University Bochum)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [pysaml2](https://github.com/IdentityPython/pysaml2)
* Email us at [the incident-response address](mailto:incident-response@idpy.org) | {'CVE-2021-21238'} | 2022-03-03T05:13:23.568436Z | 2021-01-21T14:12:16Z | LOW | null | {'CWE-347'} | {'https://github.com/IdentityPython/pysaml2/releases/tag/v6.5.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21238', 'https://github.com/IdentityPython/pysaml2/commit/1d8fd268f5bf887480a403a7a5ef8f048157cc14', 'https://pypi.org/project/pysaml2', 'https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-f4g9-h89h-jgv9'} | null |
PyPI | PYSEC-2020-79 | null | In libImaging/Jpeg2KDecode.c in Pillow before 7.1.0, there are multiple out-of-bounds reads via a crafted JP2 file. | {'GHSA-vj42-xq3r-hr3r', 'CVE-2020-10994'} | 2020-07-27T19:15:00Z | 2020-06-25T19:15:00Z | null | null | null | {'https://github.com/python-pillow/Pillow/pull/4505', 'https://pillow.readthedocs.io/en/stable/releasenotes/', 'https://github.com/advisories/GHSA-vj42-xq3r-hr3r', 'https://github.com/python-pillow/Pillow/pull/4538', 'https://github.com/python-pillow/Pillow/commits/master/src/libImaging/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/', 'https://usn.ubuntu.com/4430-1/', 'https://usn.ubuntu.com/4430-2/', 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/'} | null |
PyPI | PYSEC-2022-44 | null | 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-2022-21693', 'GHSA-jgm9-xpfj-4fq6'} | 2022-03-09T00:16:43.325615Z | 2022-01-18T22:15:00Z | null | null | null | {'https://github.com/onionshare/onionshare/security/advisories/GHSA-jgm9-xpfj-4fq6', 'https://github.com/onionshare/onionshare/releases/tag/v2.5'} | null |
PyPI | PYSEC-2019-124 | null | SQLAlchemy 1.2.17 has SQL Injection when the group_by parameter can be controlled. | {'GHSA-38fc-9xqv-7f7q', 'CVE-2019-7548'} | 2021-01-20T15:15:00Z | 2019-02-06T21:29:00Z | null | null | null | {'http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00087.html', 'https://github.com/sqlalchemy/sqlalchemy/issues/4481#issuecomment-461204518', 'https://github.com/advisories/GHSA-38fc-9xqv-7f7q', 'http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00016.html', 'https://access.redhat.com/errata/RHSA-2019:0984', 'http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00010.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://github.com/no-security/sqlalchemy_test', 'https://access.redhat.com/errata/RHSA-2019:0981', 'https://lists.debian.org/debian-lts-announce/2019/03/msg00020.html'} | null |
PyPI | PYSEC-2021-477 | null | TensorFlow is an end-to-end open source platform for machine learning. 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. 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. | {'GHSA-x83m-p7pv-ch8v', 'CVE-2021-29549'} | 2021-12-09T06:34:50.949292Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x83m-p7pv-ch8v', 'https://github.com/tensorflow/tensorflow/commit/744009c9e5cc5d0447f0dc39d055f917e1fd9e16'} | null |
PyPI | PYSEC-2021-532 | null | TensorFlow is an end-to-end open source platform for machine learning. The TFLite implementation of hashtable lookup is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/1a8e885b864c818198a5b2c0cbbeca5a1e833bc8/tensorflow/lite/kernels/hashtable_lookup.cc#L114-L115) An attacker can craft a model such that `values`'s first dimension would be 0. 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. | {'GHSA-8rm6-75mf-7r7r', 'CVE-2021-29604'} | 2021-12-09T06:34:59.535781Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/5117e0851348065ed59c991562c0ec80d9193db2', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8rm6-75mf-7r7r'} | null |
PyPI | PYSEC-2008-10 | null | 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-2008-1475'} | 2021-08-27T03:22:19.634629Z | 2008-03-24T22:44:00Z | null | null | null | {'https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00452.html', 'http://secunia.com/advisories/32805', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/41240', 'http://secunia.com/advisories/29375', 'https://www.redhat.com/archives/fedora-package-announce/2008-March/msg00375.html', 'http://www.securityfocus.com/bid/28238', 'https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00478.html', 'http://www.vupen.com/english/advisories/2008/0891', 'https://www.redhat.com/archives/fedora-package-announce/2008-March/msg00264.html', 'http://sourceforge.net/tracker/index.php?func=detail&aid=1907211&group_id=31577&atid=402788', 'http://secunia.com/advisories/29336', 'http://security.gentoo.org/glsa/glsa-200805-21.xml', 'https://bugzilla.redhat.com/show_bug.cgi?id=436546', 'http://secunia.com/advisories/30274'} | null |
PyPI | PYSEC-2014-33 | null | 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-2012-5491'} | 2021-09-01T08:44:29.513262Z | 2014-09-30T14:55:00Z | null | null | null | {'https://github.com/plone/Products.CMFPlone/blob/4.2.3/docs/CHANGES.txt', 'https://plone.org/products/plone/security/advisories/20121106/07', 'https://plone.org/products/plone-hotfix/releases/20121106', 'http://www.openwall.com/lists/oss-security/2012/11/10/1'} | null |
PyPI | PYSEC-2021-162 | null | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropInput`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/b40060c9f697b044e3107917c797ba052f4506ab/tensorflow/core/kernels/conv_grad_input_ops.h#L625-L655) does a division by a quantity that is controlled by the caller. 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. | {'GHSA-xm2v-8rrw-w9pm', 'CVE-2021-29525'} | 2021-08-27T03:22:25.775857Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xm2v-8rrw-w9pm', 'https://github.com/tensorflow/tensorflow/commit/2be2cdf3a123e231b16f766aa0e27d56b4606535'} | null |
PyPI | PYSEC-2021-8 | null | In Django 2.2 before 2.2.22, 3.1 before 3.1.10, and 3.2 before 3.2.2 (with Python 3.9.5+), URLValidator does not prohibit newlines and tabs (unless the URLField form field is used). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because HttpResponse prohibits newlines in HTTP headers. | {'GHSA-qm57-vhq3-3fwf', 'CVE-2021-32052'} | 2021-05-12T08:15:00Z | 2021-05-06T16:15:00Z | null | null | null | {'https://groups.google.com/forum/#!forum/django-announce', 'https://github.com/advisories/GHSA-qm57-vhq3-3fwf', 'https://docs.djangoproject.com/en/3.2/releases/security/', 'http://www.openwall.com/lists/oss-security/2021/05/06/1', 'https://www.djangoproject.com/weblog/2021/may/06/security-releases/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZVKYPHR3TKR2ESWXBPOJEKRO2OSJRZUE/'} | null |
PyPI | PYSEC-2021-498 | null | TensorFlow is an end-to-end open source platform for machine learning. 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/ef0c008ee84bad91ec6725ddc42091e19a30cf0e/tensorflow/core/kernels/maxpooling_op.cc#L1016-L1017) uses the same value to index in two different arrays but there is no guarantee that the sizes are identical. 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-2021-29570', 'GHSA-545v-42p7-98fq'} | 2021-12-09T06:34:54.218525Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-545v-42p7-98fq', 'https://github.com/tensorflow/tensorflow/commit/dcd7867de0fea4b72a2b34bd41eb74548dc23886'} | null |
PyPI | GHSA-c3xq-cj8f-7829 | Inadequate Encryption Strength in python-keystoneclient | python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache encryption bypass | {'CVE-2013-2166'} | 2022-03-23T20:00:07.261776Z | 2021-10-12T16:31:43Z | CRITICAL | null | {'CWE-326'} | {'http://www.openwall.com/lists/oss-security/2013/06/19/5', 'https://github.com/openstack/python-keystoneclient', 'http://rhn.redhat.com/errata/RHSA-2013-0992.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2013-August/113944.html', 'https://nvd.nist.gov/vuln/detail/CVE-2013-2166', 'https://github.com/openstack/python-keystoneclient/commit/eeefb784f24c37d5f56a421e1ccc911cace9385e', 'http://www.securityfocus.com/bid/60684', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-2166', 'https://access.redhat.com/security/cve/cve-2013-2166', 'https://security-tracker.debian.org/tracker/CVE-2013-2166', 'https://bugzilla.suse.com/show_bug.cgi?id=CVE-2013-2166'} | null |
PyPI | PYSEC-2020-96 | null | 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. | {'GHSA-6757-jp84-gxfx', 'CVE-2020-1747'} | 2021-03-26T02:44:00Z | 2020-03-24T15:15:00Z | null | null | null | {'http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00017.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/K5HEPD7LEVDPCITY5IMDYWXUMX37VFMY/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZBJA3SGNJKCAYPSHOHWY3KBCWNM5NYK2/', 'https://github.com/yaml/pyyaml/pull/386', 'http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00017.html', 'https://github.com/advisories/GHSA-6757-jp84-gxfx', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1747', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MMQXSZXNJT6ERABJZAAICI3DQSQLCP3D/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7PPAS6C4SZRDQLR7C22A5U3QOLXY33JX/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WORRFHPQVAFKKXXWLSSW6XKUYLWM6CSH/'} | null |
PyPI | PYSEC-2018-10 | null | Kotti before 1.3.2 and 2.x before 2.0.0b2 has CSRF in the local roles implementation, as demonstrated by triggering a permission change via a /admin-document/@@share request. | {'CVE-2018-9856', 'GHSA-3hq4-f2v6-q338'} | 2021-06-10T06:51:50.431238Z | 2018-04-09T07:29:00Z | null | null | null | {'https://github.com/advisories/GHSA-3hq4-f2v6-q338', 'https://github.com/Kotti/Kotti/issues/551'} | null |
PyPI | GHSA-rv6r-3f5q-9rgx | Twisted SSH client and server deny of service during SSH handshake. | ### Impact
The Twisted SSH client and server implementation naively accepted an infinite amount of data for the peer's SSH version identifier.
A malicious peer can trivially craft a request that uses all available memory and crash the server, resulting in denial of service. The attack is as simple as `nc -rv localhost 22 < /dev/zero`.
### Patches
The issue was fix in GitHub commit https://github.com/twisted/twisted/commit/98387b39e9f0b21462f6abc7a1325dc370fcdeb1
A fix is available in Twisted 22.2.0.
### Workarounds
* Limit access to the SSH server only to trusted source IP addresses.
* Connect over SSH only to trusted destination IP addresses.
### References
Reported at https://twistedmatrix.com/trac/ticket/10284
Discussions at https://github.com/twisted/twisted/security/advisories/GHSA-rv6r-3f5q-9rgx
### For more information
Found by vin01 | {'CVE-2022-21716'} | 2022-04-22T15:47:19.222481Z | 2022-03-03T19:02:08Z | HIGH | null | {'CWE-120'} | {'https://github.com/twisted/twisted/security/advisories/GHSA-rv6r-3f5q-9rgx', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21716', 'https://github.com/twisted/twisted/commit/89c395ee794e85a9657b112c4351417850330ef9', 'https://github.com/twisted/twisted/commit/98387b39e9f0b21462f6abc7a1325dc370fcdeb1', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00009.html', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/twisted/twisted', 'https://twistedmatrix.com/trac/ticket/10284', 'https://github.com/twisted/twisted/releases/tag/twisted-22.2.0'} | null |
PyPI | GHSA-9vpm-rcf4-9wqw | Division by 0 in `MaxPoolGradWithArgmax` | ### Impact
The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` is vulnerable to a division by 0:
```python
import tensorflow as tf
input = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)
grad = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)
argmax = tf.constant([], shape=[0], dtype=tf.int64)
ksize = [1, 1, 1, 1]
strides = [1, 1, 1, 1]
tf.raw_ops.MaxPoolGradWithArgmax(
input=input, grad=grad, argmax=argmax, ksize=ksize, strides=strides,
padding='SAME', include_batch_in_index=False)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/279bab6efa22752a2827621b7edb56a730233bd8/tensorflow/core/kernels/maxpooling_op.cc#L1033-L1034) fails to validate that the batch dimension of the tensor is non-zero, before dividing by this quantity.
### Patches
We have patched the issue in GitHub commit [376c352a37ce5a68b721406dc7e77ac4b6cf483d](https://github.com/tensorflow/tensorflow/commit/376c352a37ce5a68b721406dc7e77ac4b6cf483d).
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.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-29573'} | 2022-03-03T05:14:00.057449Z | 2021-05-21T14:26:07Z | LOW | null | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vpm-rcf4-9wqw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29573', 'https://github.com/tensorflow/tensorflow/commit/376c352a37ce5a68b721406dc7e77ac4b6cf483d'} | null |
PyPI | PYSEC-2021-861 | null | 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. This issue has been addressed in aws-c-io submodule versions 0.9.13 onward. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.3.3 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.5.18 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on Microsoft Windows. | {'GHSA-94jq-q5v2-76wj', 'CVE-2021-40828'} | 2022-01-05T02:16:12.381648Z | 2021-11-23T00:15:00Z | null | null | null | {'https://github.com/aws/aws-iot-device-sdk-java-v2', 'https://github.com/aws/aws-iot-device-sdk-python-v2', 'https://github.com/aws/aws-iot-device-sdk-js-v2', 'https://github.com/aws/aws-iot-device-sdk-cpp-v2', 'https://github.com/advisories/GHSA-94jq-q5v2-76wj', 'https://github.com/awslabs/aws-c-io/'} | null |
PyPI | PYSEC-2020-162 | null | 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. | {'GHSA-rjvg-q57v-mjjc', 'CVE-2019-12398'} | 2020-01-21T16:21:00Z | 2020-01-14T17:15:00Z | null | null | null | {'https://lists.apache.org/thread.html/r72487ad6b23d18689896962782f8c93032afe5c72a6bfd23b253352b@%3Cdev.airflow.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2020/01/14/2', 'https://github.com/advisories/GHSA-rjvg-q57v-mjjc', 'https://lists.apache.org/thread.html/r72487ad6b23d18689896962782f8c93032afe5c72a6bfd23b253352b%40%3Cusers.airflow.apache.org%3E'} | null |
PyPI | PYSEC-2021-54 | null | 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.) | {'CVE-2021-3144'} | 2021-03-31T14:15:00Z | 2021-02-27T05:15:00Z | null | null | null | {'https://github.com/saltstack/salt/releases', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YOGNT2XWPOYV7YT75DN7PS4GIYWFKOK5/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FUGLOJ6NXLCIFRD2JTXBYQEMAEF2B6XH/', 'https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/', 'https://security.gentoo.org/glsa/202103-01', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7GRVZ5WAEI3XFN2BDTL6DDXFS5HYSDVB/'} | null |
PyPI | GHSA-95rw-fx8r-36v6 | Cross-site Scripting in Django | The {% debug %} template tag in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2 does not properly encode the current context. This may lead to XSS. | {'CVE-2022-22818'} | 2022-03-03T05:13:25.233938Z | 2022-02-04T00:00:33Z | MODERATE | null | {'CWE-79'} | {'https://github.com/django/django', 'https://groups.google.com/forum/#!forum/django-announce', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B4SQG2EAF4WCI2SLRL6XRDJ3RPK3ZRDV/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22818', 'https://www.djangoproject.com/weblog/2022/feb/01/security-releases/', 'https://docs.djangoproject.com/en/4.0/releases/security/', 'https://security.netapp.com/advisory/ntap-20220221-0003/'} | null |
PyPI | PYSEC-2017-23 | null | 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-2017-16616'} | 2021-07-05T00:01:24.581595Z | 2017-11-08T03:29:00Z | null | null | null | {'https://joel-malwarebenchmark.github.io/blog/2017/11/08/cve-2017-16616-yamlparser-in-pyanyapi/', 'https://github.com/Stranger6667/pyanyapi/releases/tag/0.6.1', 'https://pypi.python.org/pypi/pyanyapi/0.6.1', 'https://github.com/Stranger6667/pyanyapi/issues/41'} | null |
PyPI | PYSEC-2021-549 | null | TensorFlow is an end-to-end open source platform for machine learning. 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. We have patched the issue in GitHub commit d9204be9f49520cdaaeb2541d1dc5187b23f31d9. 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-2021-37636', 'GHSA-hp4c-x6r7-6555'} | 2021-12-09T06:35:02.050023Z | 2021-08-12T18:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/d9204be9f49520cdaaeb2541d1dc5187b23f31d9', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hp4c-x6r7-6555'} | null |
PyPI | PYSEC-2014-48 | null | 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-2012-5506'} | 2021-09-01T08:44:31.097145Z | 2014-09-30T14:55:00Z | null | null | null | {'https://github.com/plone/Products.CMFPlone/blob/4.2.3/docs/CHANGES.txt', 'https://plone.org/products/plone-hotfix/releases/20121106', 'http://www.openwall.com/lists/oss-security/2012/11/10/1', 'https://plone.org/products/plone/security/advisories/20121106/22'} | null |
PyPI | PYSEC-2021-119 | null | 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. | {'GHSA-435p-f82x-mxwm', 'CVE-2021-38305'} | 2021-08-17T20:30:12.776802Z | 2021-08-09T21:15:00Z | null | null | null | {'https://github.com/advisories/GHSA-435p-f82x-mxwm', 'https://github.com/23andMe/Yamale/releases/tag/3.0.8', 'https://github.com/23andMe/Yamale/pull/165'} | null |
PyPI | PYSEC-2020-119 | null | 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 is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. | {'GHSA-pg59-2f92-5cph', 'CVE-2020-15196'} | 2021-09-01T08:19:33.034745Z | 2020-09-25T19:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph'} | null |
PyPI | GHSA-27j5-4p9v-pp67 | `std::abort` raised from `TensorListReserve` | ### Impact
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:
```python
import tensorflow as tf
tf.raw_ops.TensorListReserve(
element_shape = tf.constant([1]),
num_elements=tf.constant([-1]),
element_dtype = tf.int32)
```
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.
### Patches
We have patched the issue in GitHub commit [8a6e874437670045e6c7dc6154c7412b4a2135e2](https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2).
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.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37644'} | 2022-03-03T05:13:01.903089Z | 2021-08-25T14:43:40Z | MODERATE | null | {'CWE-617'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-27j5-4p9v-pp67', 'https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37644'} | null |
PyPI | GHSA-37cf-r3w2-gjfw | django-nopassword stores secrets in cleartext | django-nopassword before 5.0.0 stores cleartext secrets in the database. | {'CVE-2019-10682'} | 2022-03-03T05:12:46.065476Z | 2020-06-05T16:09:19Z | HIGH | null | {'CWE-522', 'CWE-312'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10682', 'https://github.com/relekang/django-nopassword/compare/v4.0.1...v5.0.0', 'https://github.com/relekang/django-nopassword/commit/d8b4615f5fbfe3997d96cf4cb3e342406396193c', 'https://github.com/relekang/django-nopassword/blob/8e8cfc765ee00adfed120c2c79bf71ef856e9022/nopassword/models.py#L14'} | null |
PyPI | PYSEC-2018-84 | null | JSNAPy is an open source python version of Junos Snapshot Administrator developed by Juniper available through github. The default configuration and sample files of JSNAPy automation tool versions prior to 1.3.0 are created world writable. This insecure file and directory permission allows unprivileged local users to alter the files under this directory including inserting operations not intended by the package maintainer, system administrator, or other users. This issue only affects users who downloaded and installed JSNAPy from github. | {'CVE-2018-0023', 'GHSA-qc55-vm3j-74gp'} | 2021-08-27T03:22:05.101975Z | 2018-04-11T19:29:00Z | null | null | null | {'https://kb.juniper.net/JSA10856', 'https://github.com/advisories/GHSA-qc55-vm3j-74gp', 'http://www.securityfocus.com/bid/103745'} | null |
PyPI | PYSEC-2009-8 | null | Unspecified vulnerability in Zope Object Database (ZODB) before 3.8.2, when certain Zope Enterprise Objects (ZEO) database sharing is enabled, allows remote attackers to execute arbitrary Python code via vectors involving the ZEO network protocol. | {'CVE-2009-0668'} | 2021-07-16T01:31:36.649414Z | 2009-08-07T19:30:00Z | null | null | null | {'http://osvdb.org/56827', 'http://pypi.python.org/pypi/ZODB3/3.8.2#whats-new-in-zodb-3-8-2', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/52377', 'http://www.vupen.com/english/advisories/2009/2217', 'http://www.securityfocus.com/bid/35987', 'http://mail.zope.org/pipermail/zope-announce/2009-August/002220.html', 'http://secunia.com/advisories/36204', 'http://secunia.com/advisories/36205'} | null |
PyPI | PYSEC-2022-110 | null | Tensorflow is an Open Source Machine Learning Framework. 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. 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-2022-21731', 'GHSA-m4hf-j54p-p353'} | 2022-03-09T00:18:23.826464Z | 2022-02-03T12:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/08d7b00c0a5a20926363849f611729f53f3ec022', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/framework/shape_inference.cc#L345-L358', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m4hf-j54p-p353', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/framework/common_shape_fns.cc#L1961-L2059'} | null |
PyPI | PYSEC-2017-58 | null | 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-2016-7135'} | 2021-07-25T23:34:48.755213Z | 2017-03-07T16:59:00Z | null | null | null | {'https://plone.org/security/hotfix/20160830/filesystem-information-leak', 'http://seclists.org/fulldisclosure/2016/Oct/80', 'http://www.securityfocus.com/archive/1/539572/100/0/threaded', 'http://www.securityfocus.com/bid/92752', 'http://www.openwall.com/lists/oss-security/2016/09/05/5', 'http://www.openwall.com/lists/oss-security/2016/09/05/4', 'http://packetstormsecurity.com/files/139110/Plone-CMS-4.3.11-5.0.6-XSS-Traversal-Open-Redirection.html'} | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.