ecosystem
stringclasses 11
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
220
⌀ | details
stringlengths 34
13.5k
| aliases
stringlengths 17
87
⌀ | modified_date
stringdate 2019-03-26 14:13:00
2022-05-10 08:46:52
| published_date
stringdate 2012-06-17 03:41:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 581
values | refs
stringlengths 82
11.6k
| introduced
stringclasses 843
values | code_refs
stringlengths 46
940
| commits
stringlengths 46
940
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
GHSA | GHSA-4rvg-955w-h68q | Path Traversal in angular-http-server | Affected versions of `angular-http-server` are vulnerable to path traversal allowing a remote attacker to read files from the server that uses `angular-http-server`.
## Recommendation
Update to version 1.6.0 or later.
:exclamation: Note: This was originally thought to be fixed in version 1.4.3, though according to [this issue](https://github.com/ossf-cve-benchmark/ossf-cve-benchmark/issues/117#issuecomment-803872454) the vulnerability was not completely fixed until version 1.6.0. | {'CVE-2018-3713'} | 2021-03-23T21:44:03Z | 2018-07-26T14:47:40Z | HIGH | 0 | {'CWE-22'} | {'https://hackerone.com/reports/309120', 'https://github.com/simonh1000/angular-http-server/pull/21', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3713', 'https://github.com/simonh1000/angular-http-server/commit/34d4bd0cd0f00c46db30855a8c4aabae27eb0ac8', 'https://www.npmjs.com/advisories/589', 'https://github.com/advisories/GHSA-4rvg-955w-h68q'} | null | {'https://github.com/simonh1000/angular-http-server/commit/34d4bd0cd0f00c46db30855a8c4aabae27eb0ac8'} | {'https://github.com/simonh1000/angular-http-server/commit/34d4bd0cd0f00c46db30855a8c4aabae27eb0ac8'} |
GHSA | GHSA-qfc5-mcwq-26q8 | Double Free in psutil | psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. | {'CVE-2019-18874'} | 2021-08-19T22:13:44Z | 2020-03-12T17:02:50Z | HIGH | 7.5 | {'CWE-415'} | {'https://github.com/giampaolo/psutil/pull/1616', 'https://github.com/advisories/GHSA-qfc5-mcwq-26q8', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2P7QI7MOTZTFXQYU23CP3RAWXCERMOAS/', 'https://usn.ubuntu.com/4204-1/', 'https://github.com/giampaolo/psutil/commit/7d512c8e4442a896d56505be3e78f1156f443465', 'https://github.com/giampaolo/psutil/blob/master/HISTORY.rst#566', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OLETTJYZL2SMBUI4Q2NGBMGPDPP54SRG/', 'https://lists.debian.org/debian-lts-announce/2019/11/msg00018.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-18874'} | null | {'https://github.com/giampaolo/psutil/commit/7d512c8e4442a896d56505be3e78f1156f443465'} | {'https://github.com/giampaolo/psutil/commit/7d512c8e4442a896d56505be3e78f1156f443465'} |
GHSA | GHSA-hggm-jpg3-v476 | RSA decryption vulnerable to Bleichenbacher timing vulnerability | ### Impact
RSA decryption was vulnerable to Bleichenbacher timing vulnerabilities, which would impact people using RSA decryption in online scenarios.
### Patches
This is fixed in cryptography 3.2. https://github.com/pyca/cryptography/commit/58494b41d6ecb0f56b7c5f05d5f5e3ca0320d494 is the resolving commit. | {'CVE-2020-25659'} | 2022-04-25T21:36:49Z | 2020-10-27T20:33:13Z | MODERATE | 5.9 | {'CWE-385'} | {'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/pyca/cryptography/commit/58494b41d6ecb0f56b7c5f05d5f5e3ca0320d494', 'https://github.com/advisories/GHSA-hggm-jpg3-v476', 'https://github.com/pyca/cryptography/pull/5507/commits/ce1bef6f1ee06ac497ca0c837fbd1c7ef6c2472b', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25659', 'https://github.com/pyca/cryptography/security/advisories/GHSA-hggm-jpg3-v476', 'https://pypi.org/project/cryptography/'} | null | {'https://github.com/pyca/cryptography/pull/5507/commits/ce1bef6f1ee06ac497ca0c837fbd1c7ef6c2472b', 'https://github.com/pyca/cryptography/commit/58494b41d6ecb0f56b7c5f05d5f5e3ca0320d494'} | {'https://github.com/pyca/cryptography/commit/58494b41d6ecb0f56b7c5f05d5f5e3ca0320d494', 'https://github.com/pyca/cryptography/pull/5507/commits/ce1bef6f1ee06ac497ca0c837fbd1c7ef6c2472b'} |
GHSA | GHSA-hwj3-m3p6-hj38 | dom4j allows External Entities by default which might enable XXE attacks | dom4j before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.
Note: This advisory applies to `dom4j:dom4j` version 1.x legacy artifacts. To resolve this a change to the latest version of `org.dom4j:dom4j` is recommended. | {'CVE-2020-10683'} | 2022-02-08T22:06:13Z | 2020-06-05T16:13:36Z | CRITICAL | 9.8 | {'CWE-611'} | {'https://github.com/dom4j/dom4j/commit/a8228522a99a02146106672a34c104adbda5c658', 'https://github.com/dom4j/dom4j/issues/87', 'https://security.netapp.com/advisory/ntap-20200518-0002/', 'https://lists.apache.org/thread.html/r91c64cd51e68e97d524395474eaa25362d564572276b9917fcbf5c32@%3Cdev.velocity.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.html', 'https://usn.ubuntu.com/4575-1/', 'https://github.com/dom4j/dom4j/commits/version-2.0.3', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://github.com/advisories/GHSA-hwj3-m3p6-hj38', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/dom4j/dom4j/releases/tag/version-2.1.3', 'https://lists.apache.org/thread.html/r51f3f9801058e47153c0ad9bc6209d57a592fc0e7aefd787760911b8@%3Cdev.velocity.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00061.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=1694235', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10683', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/rb1b990d7920ae0d50da5109b73b92bab736d46c9788dd4b135cb1a51@%3Cnotifications.freemarker.apache.org%3E', 'https://github.com/dom4j/dom4j/commit/1707bf3d898a8ada3b213acb0e3b38f16eaae73d', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/dom4j/dom4j/commit/a8228522a99a02146106672a34c104adbda5c658', 'https://github.com/dom4j/dom4j/commit/1707bf3d898a8ada3b213acb0e3b38f16eaae73d'} | {'https://github.com/dom4j/dom4j/commit/a8228522a99a02146106672a34c104adbda5c658', 'https://github.com/dom4j/dom4j/commit/1707bf3d898a8ada3b213acb0e3b38f16eaae73d'} |
GHSA | GHSA-325j-24f4-qv5x | Regular Expression Denial of Service in ssri | Version of `ssri` prior to 5.2.2 are vulnerable to regular expression denial of service (ReDoS) when using strict mode.
## Recommendation
Update to version 5.2.2 or later. | {'CVE-2018-7651'} | 2021-08-31T20:21:07Z | 2018-03-07T22:22:20Z | MODERATE | 5.9 | {'CWE-400'} | {'https://github.com/zkat/ssri/issues/10', 'https://github.com/zkat/ssri/commit/d0ebcdc22cb5c8f47f89716d08b3518b2485d65d', 'https://nvd.nist.gov/vuln/detail/CVE-2018-7651', 'https://nodesecurity.io/advisories/565', 'https://github.com/advisories/GHSA-325j-24f4-qv5x', 'https://www.npmjs.com/advisories/565'} | null | {'https://github.com/zkat/ssri/commit/d0ebcdc22cb5c8f47f89716d08b3518b2485d65d'} | {'https://github.com/zkat/ssri/commit/d0ebcdc22cb5c8f47f89716d08b3518b2485d65d'} |
GHSA | GHSA-fpqv-x9hm-35j9 | Potential XSS vulnerability in Kitodo.Presentation | ### Impact
Kitodo.Presentation fails to properly encode URL parameters for output in HTML making it vulnerable to Cross Site Scripting (XSS). Only sites using the `ListView`, `Navigation` or `PageView` plugins are affected.
It also includes jQuery 3.4.1 which is known to be vulnerable against Cross Site Scripting, although there is currently no known way to exploit this in Kitodo.Presentation.
### Patches
An updated version of Kitodo.Presentation is available on [GitHub](https://github.com/kitodo/kitodo-presentation/releases/tag/v3.1.2), [Packagist](https://packagist.org/packages/kitodo/presentation#v3.1.2) and in the [TYPO3 Extension Repository](https://extensions.typo3.org/extension/dlf/). Users are advised to update as soon as possible.
The issue was also fixed in release 2.3.1 of the 2.x branch, although it is generally not recommended to run this branch since it depends on an outdated TYPO3 version.
### References
TYPO3 Security Advisory [TYPO3-EXT-SA-2020-015](https://typo3.org/security/advisory/typo3-ext-sa-2020-015)
jQuery Security Advisory [GHSA-gxr4-xjj5-5px2](https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2)
Open Bug Bounty Report [OBB-1219978](https://www.openbugbounty.org/reports/1219978/)
### Contact
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/kitodo/kitodo-presentation/issues/new/choose)
* Email us at [security@kitodo.org](mailto:security@kitodo.org) | {'CVE-2020-16095'} | 2022-04-19T19:02:32Z | 2020-07-31T17:39:22Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-fpqv-x9hm-35j9', 'https://github.com/kitodo/kitodo-presentation/security/advisories/GHSA-fpqv-x9hm-35j9', 'https://github.com/kitodo/kitodo-presentation/commit/6a67256388350cc69efa7f36bbaee50c919ca23c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16095', 'https://typo3.org/help/security-advisories', 'https://typo3.org/security/advisory/typo3-ext-sa-2020-015'} | null | {'https://github.com/kitodo/kitodo-presentation/commit/6a67256388350cc69efa7f36bbaee50c919ca23c'} | {'https://github.com/kitodo/kitodo-presentation/commit/6a67256388350cc69efa7f36bbaee50c919ca23c'} |
GHSA | GHSA-f93j-hmcr-jcwh | Data Injection Vulnerability in moped Rubygem | The Moped::BSON::ObjecId.legal? method in rubygem-moped before commit dd5a7c14b5d2e466f7875d079af71ad19774609b allows remote attackers to cause a denial of service (worker resource consumption) or perform a cross-site scripting (XSS) attack via a crafted string. | {'CVE-2015-4410'} | 2021-09-23T18:56:26Z | 2020-08-19T16:45:49Z | HIGH | 7.5 | {'CWE-20'} | {'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/moped/CVE-2015-4410.yml', 'https://rubygems.org/gems/moped/versions', 'https://nvd.nist.gov/vuln/detail/CVE-2015-4410', 'http://sakurity.com/blog/2015/06/04/mongo_ruby_regexp.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161987.html', 'https://www.securityfocus.com/bid/75045', 'https://sakurity.com/blog/2015/06/04/mongo_ruby_regexp.html', 'http://www.securityfocus.com/bid/75045', 'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24', 'https://github.com/advisories/GHSA-f93j-hmcr-jcwh', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161964.html', 'https://seclists.org/oss-sec/2015/q2/653', 'https://homakov.blogspot.ru/2012/05/saferweb-injects-in-various-ruby.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=1229757', 'http://www.openwall.com/lists/oss-security/2015/06/06/3'} | null | {'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24'} | {'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24'} |
GHSA | GHSA-jwf9-w5xm-f437 | Heap OOB in TFLite's `Gather*` implementations | ### Impact
TFLite's [`GatherNd` implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation.
Hence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in `indices`.
Similar issue exists in [`Gather` implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc).
```python
import tensorflow as tf
import numpy as np
tf.compat.v1.disable_v2_behavior()
params = tf.compat.v1.placeholder(name="params", dtype=tf.int64, shape=(1,))
indices = tf.compat.v1.placeholder(name="indices", dtype=tf.int64, shape=())
out = tf.gather(params, indices, name='out')
with tf.compat.v1.Session() as sess:
converter = tf.compat.v1.lite.TFLiteConverter.from_session(sess, [params, indices], [out])
tflite_model = converter.convert()
interpreter = tf.lite.Interpreter(model_content=tflite_model)
interpreter.allocate_tensors()
input_details = interpreter.get_input_details()
output_details = interpreter.get_output_details()
params_data = np.reshape(np.array([1], dtype=np.int64), newshape=(1,))
indices_data = np.reshape(np.array(-10, dtype=np.int64), newshape=())
interpreter.set_tensor(input_details[0]['index'], params_data)
interpreter.set_tensor(input_details[1]['index'], indices_data)
interpreter.invoke()
```
### Patches
We have patched the issue in GitHub commits [bb6a0383ed553c286f87ca88c207f6774d5c4a8f](https://github.com/tensorflow/tensorflow/commit/bb6a0383ed553c286f87ca88c207f6774d5c4a8f) and [eb921122119a6b6e470ee98b89e65d721663179d](https://github.com/tensorflow/tensorflow/commit/eb921122119a6b6e470ee98b89e65d721663179d).
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 Yakun Zhang of Baidu Security. | {'CVE-2021-37687'} | 2021-08-25T14:40:02Z | 2021-08-25T14:40:02Z | MODERATE | 5.5 | {'CWE-125'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37687', 'https://github.com/advisories/GHSA-jwf9-w5xm-f437', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-jwf9-w5xm-f437', 'https://github.com/tensorflow/tensorflow/commit/bb6a0383ed553c286f87ca88c207f6774d5c4a8f', 'https://github.com/tensorflow/tensorflow/commit/eb921122119a6b6e470ee98b89e65d721663179d'} | null | {'https://github.com/tensorflow/tensorflow/commit/bb6a0383ed553c286f87ca88c207f6774d5c4a8f', 'https://github.com/tensorflow/tensorflow/commit/eb921122119a6b6e470ee98b89e65d721663179d'} | {'https://github.com/tensorflow/tensorflow/commit/bb6a0383ed553c286f87ca88c207f6774d5c4a8f', 'https://github.com/tensorflow/tensorflow/commit/eb921122119a6b6e470ee98b89e65d721663179d'} |
GHSA | GHSA-9rpc-5v9q-5r7f | Incomplete validation in `SparseReshape` | ### Impact
Incomplete validation in `SparseReshape` results in a denial of service based on a `CHECK`-failure.
```python
import tensorflow as tf
input_indices = tf.constant(41, shape=[1, 1], dtype=tf.int64)
input_shape = tf.zeros([11], dtype=tf.int64)
new_shape = tf.zeros([1], dtype=tf.int64)
tf.raw_ops.SparseReshape(input_indices=input_indices,
input_shape=input_shape,
new_shape=new_shape)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/e87b51ce05c3eb172065a6ea5f48415854223285/tensorflow/core/kernels/sparse_reshape_op.cc#L40) has no validation that the input arguments specify a valid sparse tensor.
### Patches
We have patched the issue in GitHub commit [1d04d7d93f4ed3854abf75d6b712d72c3f70d6b6](https://github.com/tensorflow/tensorflow/commit/1d04d7d93f4ed3854abf75d6b712d72c3f70d6b6).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are the only affected versions.
### 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-29611'} | 2021-05-21T14:28:35Z | 2021-05-21T14:28:35Z | LOW | 3.6 | {'CWE-665', 'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29611', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9rpc-5v9q-5r7f', 'https://github.com/advisories/GHSA-9rpc-5v9q-5r7f', 'https://github.com/tensorflow/tensorflow/commit/1d04d7d93f4ed3854abf75d6b712d72c3f70d6b6'} | null | {'https://github.com/tensorflow/tensorflow/commit/1d04d7d93f4ed3854abf75d6b712d72c3f70d6b6'} | {'https://github.com/tensorflow/tensorflow/commit/1d04d7d93f4ed3854abf75d6b712d72c3f70d6b6'} |
GHSA | GHSA-v659-54cx-g4qr | Prototype Pollution in deep-override | Prototype pollution vulnerability in 'deep-override' versions 1.0.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2021-25941'} | 2021-05-25T20:44:53Z | 2021-05-17T20:57:25Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://github.com/ASaiAnudeep/deep-override/commit/2aced17651fb684959a6e04b1465a8329b3d5268', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25941', 'https://github.com/advisories/GHSA-v659-54cx-g4qr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25941'} | null | {'https://github.com/ASaiAnudeep/deep-override/commit/2aced17651fb684959a6e04b1465a8329b3d5268'} | {'https://github.com/ASaiAnudeep/deep-override/commit/2aced17651fb684959a6e04b1465a8329b3d5268'} |
GHSA | GHSA-9xh4-23q4-v6wr | Heap buffer overflow and undefined behavior in `FusedBatchNorm` | ### Impact
The implementation of `tf.raw_ops.FusedBatchNorm` is vulnerable to a heap buffer overflow:
```python
import tensorflow as tf
x = tf.zeros([10, 10, 10, 6], dtype=tf.float32)
scale = tf.constant([0.0], shape=[1], dtype=tf.float32)
offset = tf.constant([0.0], shape=[1], dtype=tf.float32)
mean = tf.constant([0.0], shape=[1], dtype=tf.float32)
variance = tf.constant([0.0], shape=[1], dtype=tf.float32)
epsilon = 0.0
exponential_avg_factor = 0.0
data_format = "NHWC"
is_training = False
tf.raw_ops.FusedBatchNorm(
x=x, scale=scale, offset=offset, mean=mean, variance=variance,
epsilon=epsilon, exponential_avg_factor=exponential_avg_factor,
data_format=data_format, is_training=is_training)
```
If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers:
```python
import tensorflow as tf
import numpy as np
x = tf.zeros([10, 10, 10, 1], dtype=tf.float32)
scale = tf.constant([], shape=[0], dtype=tf.float32)
offset = tf.constant([], shape=[0], dtype=tf.float32)
mean = tf.constant([], shape=[0], dtype=tf.float32)
variance = tf.constant([], shape=[0], dtype=tf.float32)
epsilon = 0.0
exponential_avg_factor = 0.0
data_format = "NHWC"
is_training = False
tf.raw_ops.FusedBatchNorm(
x=x, scale=scale, offset=offset, mean=mean, variance=variance,
epsilon=epsilon, exponential_avg_factor=exponential_avg_factor,
data_format=data_format, is_training=is_training)
```
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.
### Patches
We have patched the issue in GitHub commit [6972f9dfe325636b3db4e0bc517ee22a159365c0](https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0).
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-29583'} | 2022-04-26T18:09:37Z | 2021-05-21T14:26:35Z | LOW | 2.5 | {'CWE-476', 'CWE-787', 'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9xh4-23q4-v6wr', 'https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29583', 'https://github.com/advisories/GHSA-9xh4-23q4-v6wr'} | null | {'https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0'} | {'https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0'} |
GHSA | GHSA-v528-7hrm-frqp | Improper Check for Unusual or Exceptional Conditions in json-smart | An issue was discovered in netplex json-smart-v1 through 2015-10-23 and json-smart-v2 through 2.4. An exception is thrown from a function, but it is not caught, as demonstrated by NumberFormatException. When it is not caught, it may cause programs using the library to crash or expose sensitive information. | {'CVE-2021-27568'} | 2022-04-26T20:59:54Z | 2021-06-16T18:03:47Z | CRITICAL | 9.1 | {'CWE-754'} | {'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.apache.org/thread.html/rf70210b4d63191c0bfb2a0d5745e104484e71703bf5ad9cb01c980c6@%3Ccommits.druid.apache.org%3E', 'https://github.com/netplex/json-smart-v1/issues/7', 'https://github.com/netplex/json-smart-v2/issues/60', 'https://lists.apache.org/thread.html/rb6287f5aa628c8d9af52b5401ec6cc51b6fc28ab20d318943453e396@%3Ccommits.druid.apache.org%3E', 'https://github.com/netplex/json-smart-v2/pull/72', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27568', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/advisories/GHSA-v528-7hrm-frqp', 'https://github.com/netplex/json-smart-v1/commit/768db58ee0e3e344fcdb574b7629765308a1d0af', 'https://lists.apache.org/thread.html/re237267da268c690df5e1c6ea6a38a7fc11617725e8049490f58a6fa@%3Ccommits.druid.apache.org%3E', 'https://github.com/netplex/json-smart-v2/issues/62', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/netplex/json-smart-v1/commit/768db58ee0e3e344fcdb574b7629765308a1d0af'} | {'https://github.com/netplex/json-smart-v1/commit/768db58ee0e3e344fcdb574b7629765308a1d0af'} |
GHSA | GHSA-g5v4-5x39-vwhx | Zip slip directory exploit in github.com/deislabs/oras | ### Impact
The directory support (#55) allows the downloaded gzipped tarballs to be automatically extracted to the user-specified directory where the tarball can have symbolic links and hard links.
A well-crafted tarball or tarballs allow malicious artifact providers linking, writing, or overwriting specific files on the host filesystem outside of the user-specified directory unexpectedly with the same permissions as the user who runs `oras pull`.
Precisely, the following users of the affected versions are impacted
- `oras` CLI users who runs `oras pull`.
- Go programs, which invokes `github.com/deislabs/oras/pkg/content.FileStore`.
### Patches
The problem has been patched by the PR linked with this advisory. Users should upgrade their `oras` CLI and packages to `0.9.0`.
### Workarounds
For `oras` CLI users, there is no workarounds other than pulling from a trusted artifact provider.
For `oras` package users, the workaround is to not use `github.com/deislabs/oras/pkg/content.FileStore`, and use other content stores instead, or pull from a trusted artifact provider.
### References
- [Zip Slip](https://github.com/snyk/zip-slip-vulnerability)
### For more information
If you have any questions or comments about this advisory:
* Open an issue on the [GitHub repo](https://github.com/deislabs/oras)
* Email the [list of maintainers](https://github.com/deislabs/oras/blob/main/MAINTAINERS) | {'CVE-2021-21272'} | 2022-04-19T19:02:44Z | 2022-02-15T00:32:04Z | HIGH | 6.5 | {'CWE-29', 'CWE-22'} | {'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e', 'https://pkg.go.dev/github.com/deislabs/oras/pkg/oras', 'https://github.com/advisories/GHSA-g5v4-5x39-vwhx', 'https://github.com/deislabs/oras/security/advisories/GHSA-g5v4-5x39-vwhx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21272', 'https://github.com/deislabs/oras/releases/tag/v0.9.0'} | null | {'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e'} | {'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e'} |
GHSA | GHSA-46c5-pfj8-fv65 | Improperly checked metadata on tools/armour itemstacks received from the client | ### Impact
Due to a workaround applied in 1.13, an attacker may send a negative damage/meta value in a tool or armour item's NBT, which `TypeConverter` then blindly uses as if it was valid without being checked.
When this invalid metadata value reaches `Durable->setDamage()`, an exception is thrown because the metadata is not within the expected range for damage values.
This can be reproduced with either a too-large damage value, or a negative one.
### Patches
c8e1cfcbee4945fd4b63d2a7e96025c59744d4f1
### Workarounds
In theory this can be checked by plugins using a custom `TypeConverter`, but this is likely to be very cumbersome.
### For more information
* Email us at [team@pmmp.io](mailto:team@pmmp.io)
| null | 2022-03-22T18:46:09Z | 2022-03-18T22:36:03Z | HIGH | 7.5 | {'CWE-704'} | {'https://github.com/pmmp/PocketMine-MP/commit/c8e1cfcbee4945fd4b63d2a7e96025c59744d4f1', 'https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-46c5-pfj8-fv65', 'https://github.com/advisories/GHSA-46c5-pfj8-fv65'} | null | {'https://github.com/pmmp/PocketMine-MP/commit/c8e1cfcbee4945fd4b63d2a7e96025c59744d4f1'} | {'https://github.com/pmmp/PocketMine-MP/commit/c8e1cfcbee4945fd4b63d2a7e96025c59744d4f1'} |
GHSA | GHSA-7fcj-pq9j-wh2r | Local Privilege Escalation in PyInstaller | ### Impact
Local Privilege Escalation in all Windows software frozen by PyInstaller in "onefile" mode.
The vulnerability is present only on Windows and in this particular case: If a **software frozen by PyInstaller in "onefile" mode** is launched by a (privileged) user who has **his/her "TempPath" resolving to a world writable directory**. This is the case e.g. if the software is launched as a service or as a scheduled task using a system account (in which case TempPath will default to C:\Windows\Temp).
In order to be exploitable the software has to be (re)started after the attacker has launched the exploit program. So for a service launched at startup, a service restart is needed (e.g. after a crash or an upgrade).
While PyInstaller itself was not vulnerable, all Windows software frozen by PyInstaller in "onefile" mode is vulnerable.
CVSSv3 score 7.0 (High)
CVSSv3 vector CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected
- all Windows software frozen by PyInstaller in "onefile" mode
No affected
- PyInstaller itself (except if frozen by PyInstaller in "onefile" mode on Windows)
- software frozen in "one*dir*" mode
- other platforms (GNU/Linux, OS X, BSD, etc.)
### Patches
The problem is patched in commits 42a67148b3bdf9211fda8499fdc5b63acdd7e6cc (fixed code) and be948cf0954707671aa499da17b10c86b6fa5e5c (recompiled bootloaders). Users should upgrade to PyInstaller version 3.6 and rebuild their software.
### Workarounds
There is no known workaround. Users using PyInstaller to freeze their Windows software using "onefile" mode should upgrade PyInstaller and rebuild their software.
### Credits
This vulnerability was discovered and reported by Farid AYOUJIL (@faridtsl), David HA, Florent LE NIGER and Yann GASCUEL (@lnv42) from Alter Solutions (@AlterSolutions) and fixed in collaboration with
Hartmut Goebel (@htgoebel, maintainer of PyInstaller).
### Funding Development
PyInstaller is in urgent need of funding to make future security fixes happen, see <https://github.com/pyinstaller/pyinstaller/issues/4404> for details. | {'CVE-2019-16784'} | 2022-04-19T19:02:24Z | 2020-01-16T22:18:27Z | HIGH | 7 | {'CWE-250'} | {'https://github.com/pyinstaller/pyinstaller/security/advisories/GHSA-7fcj-pq9j-wh2r', 'https://github.com/pyinstaller/pyinstaller/commit/42a67148b3bdf9211fda8499fdc5b63acdd7e6cc', 'https://github.com/pyinstaller/pyinstaller/commit/be948cf0954707671aa499da17b10c86b6fa5e5c', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16784', 'https://github.com/advisories/GHSA-7fcj-pq9j-wh2r'} | null | {'https://github.com/pyinstaller/pyinstaller/commit/42a67148b3bdf9211fda8499fdc5b63acdd7e6cc', 'https://github.com/pyinstaller/pyinstaller/commit/be948cf0954707671aa499da17b10c86b6fa5e5c'} | {'https://github.com/pyinstaller/pyinstaller/commit/be948cf0954707671aa499da17b10c86b6fa5e5c', 'https://github.com/pyinstaller/pyinstaller/commit/42a67148b3bdf9211fda8499fdc5b63acdd7e6cc'} |
GHSA | GHSA-86qr-9vqc-pgc6 | Code execution in Spring Integration | Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the "deserialization gadgets" exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown "deserialization gadgets" when configuring Kryo in code. | {'CVE-2020-5413'} | 2022-04-25T23:06:11Z | 2020-08-05T14:53:06Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/spring-projects/spring-integration/commit/6a02b5abe97fabab6003d51b98dd45ab009a6e05', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5413', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://tanzu.vmware.com/security/cve-2020-5413', 'https://github.com/advisories/GHSA-86qr-9vqc-pgc6', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/spring-projects/spring-integration/commit/6a02b5abe97fabab6003d51b98dd45ab009a6e05'} | {'https://github.com/spring-projects/spring-integration/commit/6a02b5abe97fabab6003d51b98dd45ab009a6e05'} |
GHSA | GHSA-hf5h-hh56-3vrg | Denial of Service in uws | Affected versions of `uws` do not properly handle large websocket messages when `permessage-deflate` is enabled, which may result in a denial of service condition.
If `uws` recieves a 256Mb websocket message when `permessage-deflate` is enabled, the server will compress the message prior to executing the length check, and subsequently extract the message prior to processing. This can result in a situation where an excessively large websocket message passes the length checks, yet still gets cast from a Buffer to a string, which will exceed v8's maximum string size and crash the process.
## Recommendation
Update to version 0.10.9 or later.
Alternatively, disable `permessage-deflate`. | {'CVE-2016-10544'} | 2021-01-08T21:17:01Z | 2020-09-01T16:02:29Z | HIGH | 0 | {'CWE-400'} | {'https://github.com/advisories/GHSA-hf5h-hh56-3vrg', 'https://nodesecurity.io/advisories/149', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10544', 'https://www.npmjs.com/advisories/149', 'https://github.com/uWebSockets/uWebSockets/commit/37deefd01f0875e133ea967122e3a5e421b8fcd9'} | null | {'https://github.com/uWebSockets/uWebSockets/commit/37deefd01f0875e133ea967122e3a5e421b8fcd9'} | {'https://github.com/uWebSockets/uWebSockets/commit/37deefd01f0875e133ea967122e3a5e421b8fcd9'} |
GHSA | GHSA-r9c2-cr39-c8g6 | Moderate severity vulnerability that affects rails-html-sanitizer | Cross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem 1.0.2 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via an HTML entity that is mishandled by the Rails::Html::FullSanitizer class. | {'CVE-2015-7579'} | 2021-09-17T14:45:38Z | 2017-10-24T18:33:36Z | MODERATE | 6.1 | {'CWE-79'} | {'http://www.securitytracker.com/id/1034816', 'http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00053.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2016-February/178046.html', 'http://www.openwall.com/lists/oss-security/2016/01/25/12', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7579', 'https://github.com/advisories/GHSA-r9c2-cr39-c8g6', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00024.html', 'https://github.com/rails/rails-html-sanitizer/commit/49dfc1584c5b8e35a4ffabf8356ba3df025e8d3f', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00014.html', 'https://groups.google.com/forum/message/raw?msg=ruby-security-ann/OU9ugTZcbjc/uksRkSxZEgAJ', 'http://lists.fedoraproject.org/pipermail/package-announce/2016-February/178064.html'} | null | {'https://github.com/rails/rails-html-sanitizer/commit/49dfc1584c5b8e35a4ffabf8356ba3df025e8d3f'} | {'https://github.com/rails/rails-html-sanitizer/commit/49dfc1584c5b8e35a4ffabf8356ba3df025e8d3f'} |
GHSA | GHSA-mmhj-4w6j-76h7 | Misuse of `Reference` and other transferable APIs may lead to access to nodejs isolate | Versions of `isolated-vm` before v4.0.0, and especially before v3.0.0, have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate.
`Reference` objects allow access to the underlying reference's full prototype chain. In an environment where the implementer has exposed a `Reference` instance to an attacker they would be able to use it to acquire a `Reference` to the nodejs context's `Function` object.
Similar application-specific attacks could be possible by modifying the local prototype of other API objects.
Access to `NativeModule` objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution.
To address these issues the following changes were made in v4.0.0:
- Documentation was updated with more explicit guidelines on building secure applications.
- `Reference` instances will no longer follow prototype chains by default, nor will they invoke accessors or proxies.
- All `isolated-vm` API prototypes are now immutable.
- `NativeModule` constructor may only be invoked from a nodejs isolate. | {'CVE-2021-21413'} | 2022-04-19T19:02:46Z | 2021-04-06T17:22:55Z | HIGH | 8 | {'CWE-913'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21413', 'https://github.com/laverdet/isolated-vm/blob/main/CHANGELOG.md#v400', 'https://github.com/laverdet/isolated-vm/commit/27151bfecc260e96714443613880e3b2e6596704', 'https://github.com/advisories/GHSA-mmhj-4w6j-76h7', 'https://github.com/laverdet/isolated-vm/security/advisories/GHSA-mmhj-4w6j-76h7', 'https://github.com/laverdet/isolated-vm/commit/2646e6c1558bac66285daeab54c7d490ed332b15'} | null | {'https://github.com/laverdet/isolated-vm/commit/27151bfecc260e96714443613880e3b2e6596704', 'https://github.com/laverdet/isolated-vm/commit/2646e6c1558bac66285daeab54c7d490ed332b15'} | {'https://github.com/laverdet/isolated-vm/commit/2646e6c1558bac66285daeab54c7d490ed332b15', 'https://github.com/laverdet/isolated-vm/commit/27151bfecc260e96714443613880e3b2e6596704'} |
GHSA | GHSA-p92x-r36w-9395 | Type confusion in mpath | This affects the package mpath before 0.8.4. A type confusion vulnerability can lead to a bypass of CVE-2018-16490. In particular, the condition ignoreProperties.indexOf(parts[i]) !== -1 returns -1 if parts[i] is ['__proto__']. This is because the method that has been called if the input is an array is Array.prototype.indexOf() and not String.prototype.indexOf(). They behave differently depending on the type of the input. | {'CVE-2021-23438'} | 2021-09-13T20:27:08Z | 2021-09-02T22:02:25Z | CRITICAL | 5.6 | {'CWE-843'} | {'https://github.com/aheckmann/mpath/commit/89402d2880d4ea3518480a8c9847c541f2d824fc', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1579548', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23438', 'https://snyk.io/vuln/SNYK-JS-MPATH-1577289', 'https://github.com/advisories/GHSA-p92x-r36w-9395'} | null | {'https://github.com/aheckmann/mpath/commit/89402d2880d4ea3518480a8c9847c541f2d824fc'} | {'https://github.com/aheckmann/mpath/commit/89402d2880d4ea3518480a8c9847c541f2d824fc'} |
GHSA | GHSA-q863-cchm-c6c6 | SQL Injection in Fork CMS | Fork CMS contains a SQL injection vulnerability in versions prior to version 5.11.1. When deleting submissions which belong to a formular (made with module `FormBuilder`), the parameter `id[]` is vulnerable to SQL injection. | {'CVE-2022-0153'} | 2022-03-30T20:34:44Z | 2022-03-25T00:00:33Z | HIGH | 7.5 | {'CWE-89'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0153', 'https://github.com/forkcms/forkcms/commit/7a12046a67ae5d8cf04face3ee75e55f03a1a608', 'https://huntr.dev/bounties/841503dd-311c-470a-a8ec-d4579b3274eb', 'https://github.com/advisories/GHSA-q863-cchm-c6c6'} | null | {'https://github.com/forkcms/forkcms/commit/7a12046a67ae5d8cf04face3ee75e55f03a1a608'} | {'https://github.com/forkcms/forkcms/commit/7a12046a67ae5d8cf04face3ee75e55f03a1a608'} |
GHSA | GHSA-jg4m-q6w8-vrjp | High severity vulnerability that affects rgpg | The self.run_gpg function in lib/rgpg/gpg_helper.rb in the rgpg gem before 0.2.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors. | {'CVE-2013-4203'} | 2021-09-14T19:42:52Z | 2017-10-24T18:33:37Z | HIGH | 0 | {'CWE-94'} | {'http://www.openwall.com/lists/oss-security/2013/08/03/2', 'https://github.com/rcook/rgpg/commit/b819b13d198495f3ecd2762a0dbe27bb6fae3505', 'https://github.com/advisories/GHSA-jg4m-q6w8-vrjp', 'https://nvd.nist.gov/vuln/detail/CVE-2013-4203'} | null | {'https://github.com/rcook/rgpg/commit/b819b13d198495f3ecd2762a0dbe27bb6fae3505'} | {'https://github.com/rcook/rgpg/commit/b819b13d198495f3ecd2762a0dbe27bb6fae3505'} |
GHSA | GHSA-qpgw-2c72-4c89 | Mautic users able to download any files from server using filemanager | ### Impact
Mautic versions 1.0.0 - 2.11.0 are vulnerable to allowing any authorized Mautic user session (must be logged into Mautic) to use the Filemanager to download any file from the server that the web user has access to.
### Patches
Update to 2.12.0 or later.
### Workarounds
None
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@mautic.org](mailto:security@mautic.org) | {'CVE-2017-1000490'} | 2022-04-19T19:02:45Z | 2021-01-19T20:50:38Z | HIGH | 6.5 | {'CWE-22'} | {'https://github.com/mautic/mautic/commit/3b01786433ae15e9a23f1eb9b0d3dfdb065b6241', 'https://github.com/mautic/mautic/releases/tag/2.12.0', 'https://github.com/advisories/GHSA-qpgw-2c72-4c89', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000490', 'https://github.com/mautic/mautic/security/advisories/GHSA-qpgw-2c72-4c89'} | null | {'https://github.com/mautic/mautic/commit/3b01786433ae15e9a23f1eb9b0d3dfdb065b6241'} | {'https://github.com/mautic/mautic/commit/3b01786433ae15e9a23f1eb9b0d3dfdb065b6241'} |
GHSA | GHSA-8v3j-jfg3-v3fv | Prototype Pollution in Sails.js | Sails.js <= 1.5.2 is vulnerable to Prototype Pollution via controller/load-action-modules.js, function loadActionModules(). A [patch](https://github.com/balderdashy/sails/commit/7c5379a656bb305c958df1dcc2b51a9668830358) is available in the `master` branch of Sails.js's GItHub repository. | {'CVE-2021-44908'} | 2022-03-29T21:42:44Z | 2022-03-18T00:01:11Z | MODERATE | 9.8 | {'CWE-1321'} | {'https://github.com/balderdashy/sails/blob/master/lib/app/private/controller/load-action-modules.js#L32', 'https://github.com/advisories/GHSA-8v3j-jfg3-v3fv', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44908', 'https://github.com/balderdashy/sails/commit/7c5379a656bb305c958df1dcc2b51a9668830358', 'https://github.com/Marynk/JavaScript-vulnerability-detection/blob/main/sailsJS%20PoC.zip', 'https://github.com/balderdashy/sails/issues/7209'} | null | {'https://github.com/balderdashy/sails/commit/7c5379a656bb305c958df1dcc2b51a9668830358'} | {'https://github.com/balderdashy/sails/commit/7c5379a656bb305c958df1dcc2b51a9668830358'} |
GHSA | GHSA-px8v-hxxx-2rgh | Potential Code Injection in Sprout Forms | ### Impact
A potential Server-Side Template Injection vulnerability exists in Sprout Forms which could lead to the execution of Twig code.
### Patches
The problem is fixed in`barrelstrength/sprout-forms:v3.9.0` which upgrades to `barrelstrength/sprout-base-email:v1.2.7`
### Workarounds
Users unable to upgrade should update any Notification Emails to use the "Basic Notification (Sprout Email)" template and avoid using the "Basic Notification (Sprout Forms)" template or any custom templates that display Form Fields.
### References
- See the release notes in the [CHANGELOG](https://github.com/barrelstrength/craft-sprout-forms/blob/v3/CHANGELOG.md#390---2020-04-09-critical)
- Credits to Paweł Hałdrzyński, Daniel Kalinowski from [ISEC.PL](https://isec.pl/) for discovery and responsible disclosure
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Sprout Forms repo](https://github.com/barrelstrength/craft-sprout-forms/issues)
* Email us at [sprout@barrelstrengthdesign.com](mailto:sprout@barrelstrengthdesign.com) | {'CVE-2020-11056'} | 2022-04-19T19:02:25Z | 2020-05-08T21:00:02Z | CRITICAL | 7.4 | {'CWE-94', 'CWE-74'} | {'https://github.com/barrelstrength/craft-sprout-forms/security/advisories/GHSA-px8v-hxxx-2rgh', 'https://github.com/barrelstrength/craft-sprout-forms/blob/v3/CHANGELOG.md#390---2020-04-09-critical', 'https://github.com/barrelstrength/craft-sprout-base-email/commit/5ef759f4713ede6dbf77c9d9df9f992876e43a49', 'https://github.com/advisories/GHSA-px8v-hxxx-2rgh', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11056'} | null | {'https://github.com/barrelstrength/craft-sprout-base-email/commit/5ef759f4713ede6dbf77c9d9df9f992876e43a49'} | {'https://github.com/barrelstrength/craft-sprout-base-email/commit/5ef759f4713ede6dbf77c9d9df9f992876e43a49'} |
GHSA | GHSA-mw6v-crh8-8533 | Integer Overflow or Wraparound in Google TensorFlow | Google TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability. The type of exploitation is context-dependent. | {'CVE-2018-7575'} | 2022-03-23T22:28:48Z | 2019-04-30T15:36:41Z | CRITICAL | 9.8 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/commit/d107fee1e4a9a4462f01564798d345802acc2aef', 'https://github.com/advisories/GHSA-mw6v-crh8-8533', 'https://nvd.nist.gov/vuln/detail/CVE-2018-7575', 'https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2018-004.md'} | null | {'https://github.com/tensorflow/tensorflow/commit/d107fee1e4a9a4462f01564798d345802acc2aef'} | {'https://github.com/tensorflow/tensorflow/commit/d107fee1e4a9a4462f01564798d345802acc2aef'} |
GHSA | GHSA-g4gq-j4p2-j8fr | Remote Code Execution via Script (Python) objects under Python 3 | ### Impact
Background: The optional add-on package `Products.PythonScripts` adds `Script (Python)` to the list of content items a user can add to the Zope object database. Inside these scripts users can write Python code that is executed when rendered through the web. The code environment in these script objects is limited, it relies on the `RestrictedPython` package to provide a "safe" subset of Python instructions as well as the `AccessControl` package that defines security policies for execution in the context of a Zope application.
Recently the `AccessControl` package was updated to fix a remote code execution security issue. A link to the security advisory is provided in the References section below. The bug tightens the `AccessControl` security policies for Zope by blocking access to unsafe classes inside the Python `string` module.
You are only affected if the following are true:
- You use Python 3 for your Zope deployment (Zope 4 on Python 2 is not affected)
- You run Zope 4 below version 4.6.3 or Zope 5 below version 5.3
- You have installed the optional `Products.PythonScripts` add-on package
By default, you need to have the admin-level Zope "Manager" role to add or edit Script (Python) objects through the web. Only sites that allow untrusted users to add/edit these scripts through the web - which would be a very unusual configuration to begin with - are at risk.
### Patches
The problem has been fixed in `AccessControl` versions 4.3 and 5.2. Zope releases 4.6.3 and 5.3 now require these new `AccessControl` releases.
### Workarounds
A site administrator can restrict adding/editing Script (Python) objects through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing these scripts through the web should be restricted to trusted users only. This is the default configuration in Zope.
### References
* [AccessControl security advisory GHSA-qcx9-j53g-ccgf](https://github.com/zopefoundation/AccessControl/security/advisories/GHSA-qcx9-j53g-ccgf)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Zope issue tracker](https://github.com/zopefoundation/Zope/issues)
* Email us at [security@plone.org](mailto:security@plone.org)
| {'CVE-2021-32811'} | 2021-08-30T23:21:30Z | 2021-08-05T17:00:37Z | HIGH | 7.5 | {'CWE-915'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32811', 'https://github.com/zopefoundation/Zope/security/advisories/GHSA-g4gq-j4p2-j8fr', 'https://github.com/zopefoundation/Zope/commit/f72a18dda8e9bf2aedb46168761668464a4be988', 'https://github.com/zopefoundation/AccessControl/security/advisories/GHSA-qcx9-j53g-ccgf', 'https://github.com/advisories/GHSA-g4gq-j4p2-j8fr'} | null | {'https://github.com/zopefoundation/Zope/commit/f72a18dda8e9bf2aedb46168761668464a4be988'} | {'https://github.com/zopefoundation/Zope/commit/f72a18dda8e9bf2aedb46168761668464a4be988'} |
GHSA | GHSA-9gp4-qrff-c648 | Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 | In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack. For BC 1.55 and older, in an environment where timings can be easily observed, it is possible with enough observations to identify when the decryption is failing due to padding. | {'CVE-2016-1000345'} | 2021-09-07T21:35:31Z | 2018-10-18T18:04:13Z | MODERATE | 5.9 | null | {'https://nvd.nist.gov/vuln/detail/CVE-2016-1000345', 'https://github.com/advisories/GHSA-9gp4-qrff-c648', 'https://security.netapp.com/advisory/ntap-20181127-0004/', 'https://access.redhat.com/errata/RHSA-2018:2927', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/bcgit/bc-java/commit/21dcb3d9744c83dcf2ff8fcee06dbca7bfa4ef35#diff-4439ce586bf9a13bfec05c0d113b8098', 'https://access.redhat.com/errata/RHSA-2018:2669', 'https://usn.ubuntu.com/3727-1/', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html'} | null | {'https://github.com/bcgit/bc-java/commit/21dcb3d9744c83dcf2ff8fcee06dbca7bfa4ef35#diff-4439ce586bf9a13bfec05c0d113b8098'} | {'https://github.com/bcgit/bc-java/commit/21dcb3d9744c83dcf2ff8fcee06dbca7bfa4ef35#diff-4439ce586bf9a13bfec05c0d113b8098'} |
GHSA | GHSA-94jq-q5v2-76wj | Improper certificate management in AWS IoT Device SDK v2 | 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. | {'CVE-2021-40828'} | 2021-12-03T15:21:37Z | 2021-11-24T21:02:24Z | MODERATE | 6.3 | {'CWE-295'} | {'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/67950ad2a02f2f9355c310b69dc9226b017f32f2', 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/fd4c0ba04b35eab9e20c635af5548fcc5a92d8be', 'https://github.com/aws/aws-iot-device-sdk-python-v2', 'https://github.com/awslabs/aws-c-io/', 'https://github.com/aws/aws-iot-device-sdk-cpp-v2', 'https://github.com/advisories/GHSA-94jq-q5v2-76wj', 'https://github.com/aws/aws-iot-device-sdk-js-v2', 'https://github.com/aws/aws-iot-device-sdk-java-v2', 'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/4be41394f1aee979e6f4b012fcb01eecabd0c08d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-40828'} | null | {'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/67950ad2a02f2f9355c310b69dc9226b017f32f2', 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/fd4c0ba04b35eab9e20c635af5548fcc5a92d8be', 'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/4be41394f1aee979e6f4b012fcb01eecabd0c08d'} | {'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/67950ad2a02f2f9355c310b69dc9226b017f32f2', 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/fd4c0ba04b35eab9e20c635af5548fcc5a92d8be', 'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/4be41394f1aee979e6f4b012fcb01eecabd0c08d'} |
GHSA | GHSA-7p99-3798-f85c | URL Redirection to Untrusted Site ('Open Redirect') in express-openid-connect | ### Impact
Users of the `requiresAuth` middleware, either directly or through the default `authRequired` option, are vulnerable to an Open Redirect when the middleware is applied to a catch all route.
If all routes under `example.com` are protected with the `requiresAuth` middleware, a visit to `http://example.com//google.com` will be redirected to `google.com` after login because the original url reported by the Express framework is not properly sanitised.
### Am I affected?
You are affected by this vulnerability if you are using the `requiresAuth` middleware on a catch all route or the default `authRequired` option and `express-openid-connect` version `<=2.7.1`.
### How to fix that?
Upgrade to version `>=2.7.2`
### Will this update impact my users?
The fix provided in the patch will not affect your users.
| {'CVE-2022-24794'} | 2022-04-09T15:03:35Z | 2022-03-31T22:44:47Z | HIGH | 7.5 | {'CWE-601'} | {'https://github.com/auth0/express-openid-connect/commit/0947b92164a2c5f661ebcc183d37e7f21de719ad', 'https://github.com/auth0/express-openid-connect/security/advisories/GHSA-7p99-3798-f85c', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24794', 'https://github.com/advisories/GHSA-7p99-3798-f85c'} | null | {'https://github.com/auth0/express-openid-connect/commit/0947b92164a2c5f661ebcc183d37e7f21de719ad'} | {'https://github.com/auth0/express-openid-connect/commit/0947b92164a2c5f661ebcc183d37e7f21de719ad'} |
GHSA | GHSA-j8c8-67vp-6mx7 | Arbitrary memory read in `ImmutableConst` | ### Impact
The `ImmutableConst` operation in TensorFlow can be tricked into reading arbitrary memory contents:
```python
import tensorflow as tf
with open('/tmp/test','wb') as f:
f.write(b'\xe2'*128)
data = tf.raw_ops.ImmutableConst(dtype=tf.string,shape=3,memory_region_name='/tmp/test')
print(data)
```
This is because the `tstring` TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype.
### Patches
We have patched the issue in GitHub commit [3712a2d3455e6ccb924daa5724a3652a86f6b585](https://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585) and GitHub commit [1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b](https://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b).
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-41227'} | 2021-11-10T18:34:49Z | 2021-11-10T18:34:49Z | MODERATE | 6.6 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41227', 'https://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585', 'https://github.com/advisories/GHSA-j8c8-67vp-6mx7', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j8c8-67vp-6mx7'} | null | {'https://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b', 'https://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585'} | {'https://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585', 'https://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b'} |
GHSA | GHSA-cmch-296j-wfvw | Arbitrary File Write in iobroker.js-controller | Versions of `iobroker.controller` prior to 2.0.25 are vulnerable to Path Traversal. The package fails to restrict access to folders outside of the intended `/adapter/<adapter-name>` folder, which may allow attackers to include arbitrary files in the system. An attacker would need to be authenticated to perform the attack but the package has authentication disabled by default.
## Recommendation
Upgrade to version 2.0.25 or later. | {'CVE-2019-10767'} | 2021-08-19T15:11:16Z | 2019-12-02T18:06:14Z | HIGH | 7.5 | {'CWE-22'} | {'https://www.npmjs.com/advisories/1419', 'https://snyk.io/vuln/SNYK-JS-IOBROKERJSCONTROLLER-534881', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10767', 'https://github.com/advisories/GHSA-cmch-296j-wfvw', 'https://github.com/ioBroker/ioBroker.js-controller/commit/f6e292c6750a491a5000d0f851b2fede4f9e2fda'} | null | {'https://github.com/ioBroker/ioBroker.js-controller/commit/f6e292c6750a491a5000d0f851b2fede4f9e2fda'} | {'https://github.com/ioBroker/ioBroker.js-controller/commit/f6e292c6750a491a5000d0f851b2fede4f9e2fda'} |
GHSA | GHSA-v4rr-65x6-g69f | XXE vulnerability in Jenkins Flaky Test Handler Plugin | Jenkins Flaky Test Handler Plugin 1.2.1 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. | {'CVE-2022-28140'} | 2022-05-03T20:56:23Z | 2022-03-30T00:00:25Z | HIGH | 8.1 | {'CWE-611'} | {'https://www.jenkins.io/security/advisory/2022-03-29/#SECURITY-1896', 'https://github.com/advisories/GHSA-v4rr-65x6-g69f', 'http://www.openwall.com/lists/oss-security/2022/03/29/1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-28140', 'https://github.com/jenkinsci/flaky-test-handler-plugin/commit/c4ab38fef3658a02315a00288b934bdd9981b3a4'} | null | {'https://github.com/jenkinsci/flaky-test-handler-plugin/commit/c4ab38fef3658a02315a00288b934bdd9981b3a4'} | {'https://github.com/jenkinsci/flaky-test-handler-plugin/commit/c4ab38fef3658a02315a00288b934bdd9981b3a4'} |
GHSA | GHSA-6gmv-pjp9-p8w8 | Out of bounds read in Tensorflow | ### Impact
The [implementation of shape inference for `ReverseSequence`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/ops/array_ops.cc#L1636-L1671) does not fully validate the value of `batch_dim` and can result in a heap OOB read:
```python
import tensorflow as tf
@tf.function
def test():
y = tf.raw_ops.ReverseSequence(
input = ['aaa','bbb'],
seq_lengths = [1,1,1],
seq_dim = -10,
batch_dim = -10 )
return y
test()
```
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:
```cc
const int32_t input_rank = c->Rank(input);
if (batch_dim >= input_rank) {
return errors::InvalidArgument(
"batch_dim must be < input rank: ", batch_dim, " vs. ", input_rank);
}
// ...
DimensionHandle batch_dim_dim = c->Dim(input, batch_dim);
```
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`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/framework/shape_inference.h#L415-L428) would access elements before the start of an array:
```cc
DimensionHandle Dim(ShapeHandle s, int64_t idx) {
if (!s.Handle() || s->rank_ == kUnknownRank) {
return UnknownDim();
}
return DimKnownRank(s, idx);
}
·
static DimensionHandle DimKnownRank(ShapeHandle s, int64_t idx) {
CHECK_NE(s->rank_, kUnknownRank);
if (idx < 0) {
return s->dims_[s->dims_.size() + idx];
}
return s->dims_[idx];
}
```
### Patches
We have patched the issue in GitHub commit [37c01fb5e25c3d80213060460196406c43d31995](https://github.com/tensorflow/tensorflow/commit/37c01fb5e25c3d80213060460196406c43d31995).
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 Yu Tian of Qihoo 360 AIVul Team. | {'CVE-2022-21728'} | 2022-02-10T00:17:52Z | 2022-02-09T18:29:24Z | HIGH | 8.1 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/ops/array_ops.cc#L1636-L1671', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21728', 'https://github.com/tensorflow/tensorflow/commit/37c01fb5e25c3d80213060460196406c43d31995', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/framework/shape_inference.h#L415-L428', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6gmv-pjp9-p8w8', 'https://github.com/advisories/GHSA-6gmv-pjp9-p8w8'} | null | {'https://github.com/tensorflow/tensorflow/commit/37c01fb5e25c3d80213060460196406c43d31995'} | {'https://github.com/tensorflow/tensorflow/commit/37c01fb5e25c3d80213060460196406c43d31995'} |
GHSA | GHSA-j878-43hm-8gr5 | Unrestricted Upload of File with Dangerous Type in Microweber | In Microweber prior to 1.2.12, a malicious actor may abuse the Backup/Restore feature to achieve Remote Code Execution. | {'CVE-2022-0921'} | 2022-03-23T15:35:21Z | 2022-03-12T00:00:30Z | MODERATE | 6.7 | {'CWE-434'} | {'https://github.com/advisories/GHSA-j878-43hm-8gr5', 'https://github.com/microweber/microweber/commit/867bdda1b4660b0795ad7f87ab5abe9e44b2b318', 'https://huntr.dev/bounties/e368be37-1cb4-4292-8d48-07132725f622', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0921'} | null | {'https://github.com/microweber/microweber/commit/867bdda1b4660b0795ad7f87ab5abe9e44b2b318'} | {'https://github.com/microweber/microweber/commit/867bdda1b4660b0795ad7f87ab5abe9e44b2b318'} |
GHSA | GHSA-p6mr-pxg4-68hx | Symlink Arbitrary File Overwrite in bower | Versions of `bower` prior to 1.8.8 are affected by an arbitrary file write vulnerability. The vulnerability occurs because `bower` does not verify that extracted symbolic links do not resolve to targets outside of the extraction root directory.
## Recommendation
Update to version 1.8.8 or later | {'CVE-2019-5484'} | 2021-01-08T20:41:10Z | 2019-09-17T23:21:34Z | HIGH | 0 | {'CWE-22'} | {'https://github.com/bower/bower/commit/45c6bfa86f6e57731b153baca9e0b41a1cc699e3', 'https://snyk.io/blog/severe-security-vulnerability-in-bowers-zip-archive-extraction', 'https://www.npmjs.com/advisories/776', 'https://github.com/nodejs/security-wg/blob/master/vuln/npm/487.json', 'https://github.com/advisories/GHSA-p6mr-pxg4-68hx', 'https://nvd.nist.gov/vuln/detail/CVE-2019-5484', 'https://lists.apache.org/thread.html/r8ba4c628fba7181af58817d452119481adce4ba92e889c643e4c7dd3@%3Ccommits.netbeans.apache.org%3E', 'https://hackerone.com/reports/473811', 'https://lists.apache.org/thread.html/rb5ac16fad337d1f3bb7079549f97d8166d0ef3082629417c39f12d63@%3Cnotifications.netbeans.apache.org%3E'} | null | {'https://github.com/bower/bower/commit/45c6bfa86f6e57731b153baca9e0b41a1cc699e3'} | {'https://github.com/bower/bower/commit/45c6bfa86f6e57731b153baca9e0b41a1cc699e3'} |
GHSA | GHSA-4mqv-gcr3-pff9 | "Cross-site scripting in phpoffice/phpspreadsheet" | "This affects the package phpoffice/phpspreadsheet. The library is vulnerable to XSS when creating an html output from an excel file by adding a comment on any cell. The root cause of this issue is within the HTML writer where user comments are concatenated as part of link and this is returned as HTML." | {'CVE-2020-7776'} | 2021-05-06T18:53:37Z | 2021-05-06T18:53:37Z | MODERATE | 6.4 | {'CWE-79'} | {'https://github.com/PHPOffice/PhpSpreadsheet/blob/master/src/PhpSpreadsheet/Writer/Html.php%23L1792', 'https://snyk.io/vuln/SNYK-PHP-PHPOFFICEPHPSPREADSHEET-1048856', 'https://github.com/PHPOffice/PhpSpreadsheet/commit/0ed5b800be2136bcb8fa9c1bdf59abc957a98845', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7776', 'https://github.com/advisories/GHSA-4mqv-gcr3-pff9'} | null | {'https://github.com/PHPOffice/PhpSpreadsheet/commit/0ed5b800be2136bcb8fa9c1bdf59abc957a98845'} | {'https://github.com/PHPOffice/PhpSpreadsheet/commit/0ed5b800be2136bcb8fa9c1bdf59abc957a98845'} |
GHSA | GHSA-7fvx-3jfc-2cpc | Heap OOB in `ResourceScatterUpdate` | ### Impact
An attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to `tf.raw_ops.ResourceScatterUpdate`:
```python
import tensorflow as tf
v = tf.Variable([b'vvv'])
tf.raw_ops.ResourceScatterUpdate(
resource=v.handle,
indices=[0],
updates=['1', '2', '3', '4', '5'])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of `indices` and `updates`: instead of checking that the shape of `indices` is a prefix of the shape of `updates` (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship.
### Patches
We have patched the issue in GitHub commit [01cff3f986259d661103412a20745928c727326f](https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f).
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-37655'} | 2021-08-25T14:42:58Z | 2021-08-25T14:42:58Z | HIGH | 7.3 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f', 'https://github.com/advisories/GHSA-7fvx-3jfc-2cpc', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7fvx-3jfc-2cpc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37655'} | null | {'https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f'} | {'https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f'} |
GHSA | GHSA-8j9v-h2vp-2hhv | XSS in HtmlSanitizer | ### Impact
If you have explicitly allowed the `<style>` tag, an attacker could craft HTML that includes script after passing through the sanitizer. The default settings disallow the `<style>` tag so there is no risk if you have not explicitly allowed the `<style>` tag.
### Patches
The problem has been fixed in version 5.0.372.
### Workarounds
Remove the `<style>` tag from the set of allowed tags.
### For more information
If you have any questions or comments about this advisory open an issue in https://github.com/mganss/HtmlSanitizer
### Credits
This issue was discovered by Michal Bentkowski of Securitum. | {'CVE-2020-26293'} | 2021-01-08T18:14:26Z | 2021-01-04T18:22:11Z | LOW | 6.1 | {'CWE-74', 'CWE-79'} | {'https://github.com/mganss/HtmlSanitizer/commit/a3a7602a44d4155d51ec0fbbedc2a49e9c7e2eb8', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26293', 'https://github.com/mganss/HtmlSanitizer/releases/tag/v5.0.372', 'https://github.com/mganss/HtmlSanitizer/security/advisories/GHSA-8j9v-h2vp-2hhv', 'https://www.nuget.org/packages/HtmlSanitizer/', 'https://github.com/advisories/GHSA-8j9v-h2vp-2hhv'} | null | {'https://github.com/mganss/HtmlSanitizer/commit/a3a7602a44d4155d51ec0fbbedc2a49e9c7e2eb8'} | {'https://github.com/mganss/HtmlSanitizer/commit/a3a7602a44d4155d51ec0fbbedc2a49e9c7e2eb8'} |
GHSA | GHSA-jjvm-3mfq-7gc7 | Cross-site Scripting in microweber | microweber version 1.2.10 and prior is vulnerable to cross-site scripting. | {'CVE-2022-0506'} | 2022-02-15T00:17:21Z | 2022-02-09T00:00:31Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/microweber/microweber/commit/05d55f2befb1b25375ca5371875ff535d6cc5f70', 'https://github.com/advisories/GHSA-jjvm-3mfq-7gc7', 'https://huntr.dev/bounties/0a5ec24c-343e-4cc4-b27b-2beb19a1c35f', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0506'} | null | {'https://github.com/microweber/microweber/commit/05d55f2befb1b25375ca5371875ff535d6cc5f70'} | {'https://github.com/microweber/microweber/commit/05d55f2befb1b25375ca5371875ff535d6cc5f70'} |
GHSA | GHSA-xp7p-3gx7-j6wx | calibre-web is vulnerable to Business Logic Errors | calibre-web is vulnerable to Business Logic Errors | {'CVE-2021-4171'} | 2022-03-21T19:12:08Z | 2022-01-21T23:44:15Z | CRITICAL | 9.8 | null | {'https://nvd.nist.gov/vuln/detail/CVE-2021-4171', 'https://huntr.dev/bounties/1117f439-133c-4563-afb2-6cd80607bd5c', 'https://github.com/janeczku/calibre-web/commit/3e0d8763c377d2146462811e3e4ccf13f0d312ce', 'https://github.com/advisories/GHSA-xp7p-3gx7-j6wx'} | null | {'https://github.com/janeczku/calibre-web/commit/3e0d8763c377d2146462811e3e4ccf13f0d312ce'} | {'https://github.com/janeczku/calibre-web/commit/3e0d8763c377d2146462811e3e4ccf13f0d312ce'} |
GHSA | GHSA-4r4m-hjwj-43p8 | Insecure Defaults Allow MITM Over TLS in engine.io-client | Affected versions of `engine.io-client` do not verify certificates by default, and as such may be vulnerable to Man-in-the-Middle attacks.
The vulnerability is related to the way that node.js handles the `rejectUnauthorized` setting. If the value is something that evaluates to false, such as undefined or null, certificate verification will be disabled.
## Recommendation
Update to version 1.6.9 or later.
If you are unable to upgrade, ensure all calls to socket.io to have a `rejectedUnauthorized: true` flag. | {'CVE-2016-10536'} | 2021-01-08T19:53:57Z | 2019-02-18T23:39:50Z | MODERATE | 0 | {'CWE-300'} | {'https://www.npmjs.com/advisories/99', 'https://www.cigital.com/blog/node-js-socket-io/', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10536', 'https://nodesecurity.io/advisories/99', 'https://github.com/advisories/GHSA-4r4m-hjwj-43p8', 'https://github.com/socketio/engine.io-client/commit/2c55b278a491bf45313ecc0825cf800e2f7ff5c1'} | null | {'https://github.com/socketio/engine.io-client/commit/2c55b278a491bf45313ecc0825cf800e2f7ff5c1'} | {'https://github.com/socketio/engine.io-client/commit/2c55b278a491bf45313ecc0825cf800e2f7ff5c1'} |
GHSA | GHSA-vpwq-6cp4-ffqc | Stored Cross-site Scripting in ShowDoc | ShowDoc prior to version 2.10.4 is vulnerable to stored cross-site scripting viva `axd` and `cshtml` file upload. | {'CVE-2022-0945'} | 2022-03-29T21:28:25Z | 2022-03-16T00:00:49Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-vpwq-6cp4-ffqc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0945', 'https://github.com/star7th/showdoc/commit/ba45d19e1d77a7eea866dab30eff5da552694891', 'https://huntr.dev/bounties/8702e2bf-4af2-4391-b651-c8c89e7d089e'} | null | {'https://github.com/star7th/showdoc/commit/ba45d19e1d77a7eea866dab30eff5da552694891'} | {'https://github.com/star7th/showdoc/commit/ba45d19e1d77a7eea866dab30eff5da552694891'} |
GHSA | GHSA-w3v3-cxq5-9vr4 | Incorrect Default Permissions and Improper Access Control in snipe-it | snipe-it is vulnerable to Improper Access Control/Incorrect Default Permissions. | {'CVE-2022-0179'} | 2022-01-21T23:58:07Z | 2022-01-21T23:58:07Z | MODERATE | 6.3 | {'CWE-284', 'CWE-276'} | {'https://github.com/advisories/GHSA-w3v3-cxq5-9vr4', 'https://huntr.dev/bounties/efdf2ead-f9d1-4767-9f02-d11f762d15e7', 'https://github.com/snipe/snipe-it/commit/cf14a0222c67472086cd08b2155f045edaf75f2e', 'https://github.com/snipe/snipe-it/pull/10498', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0179'} | null | {'https://github.com/snipe/snipe-it/commit/cf14a0222c67472086cd08b2155f045edaf75f2e'} | {'https://github.com/snipe/snipe-it/commit/cf14a0222c67472086cd08b2155f045edaf75f2e'} |
GHSA | GHSA-hmv2-79q8-fv6g | Uncontrolled Resource Consumption in urllib3 | The _encode_invalid_chars function in util/url.py in the urllib3 library 1.25.2 through 1.25.7 for Python allows a denial of service (CPU consumption) because of an inefficient algorithm. The percent_encodings array contains all matches of percent encodings. It is not deduplicated. For a URL of length N, the size of percent_encodings may be up to O(N). The next step (normalize existing percent-encoded bytes) also takes up to O(N) for each step, so the total time is O(N^2). If percent_encodings were deduplicated, the time to compute _encode_invalid_chars would be O(kN), where k is at most 484 ((10+6*2)^2). | {'CVE-2020-7212'} | 2021-04-30T17:31:43Z | 2021-04-30T17:31:43Z | HIGH | 7.5 | {'CWE-400'} | {'https://pypi.org/project/urllib3/1.25.8/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7212', 'https://github.com/urllib3/urllib3/commit/a74c9cfbaed9f811e7563cfc3dce894928e0221a', 'https://github.com/urllib3/urllib3/blob/master/CHANGES.rst', 'https://github.com/advisories/GHSA-hmv2-79q8-fv6g'} | null | {'https://github.com/urllib3/urllib3/commit/a74c9cfbaed9f811e7563cfc3dce894928e0221a'} | {'https://github.com/urllib3/urllib3/commit/a74c9cfbaed9f811e7563cfc3dce894928e0221a'} |
GHSA | GHSA-gg9m-x3cg-69vh | Access key stored in plain text by Jenkins Metrics Plugin | Jenkins Metrics Plugin 4.0.2.8 and earlier stores an access key unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system. | {'CVE-2022-20621'} | 2022-05-04T21:00:00Z | 2022-01-13T00:00:57Z | MODERATE | 0 | {'CWE-522'} | {'https://github.com/advisories/GHSA-gg9m-x3cg-69vh', 'http://www.openwall.com/lists/oss-security/2022/01/12/6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-20621', 'https://github.com/jenkinsci/metrics-plugin/commit/9810480370d4c5e04a2b710934db5461bde0d1b6', 'https://www.jenkins.io/security/advisory/2022-01-12/#SECURITY-1624'} | null | {'https://github.com/jenkinsci/metrics-plugin/commit/9810480370d4c5e04a2b710934db5461bde0d1b6'} | {'https://github.com/jenkinsci/metrics-plugin/commit/9810480370d4c5e04a2b710934db5461bde0d1b6'} |
GHSA | GHSA-fg47-3c2x-m2wr | TimelockController vulnerability in OpenZeppelin Contracts | ### Impact
A vulnerability in `TimelockController` allowed an actor with the executor role to take immediate control of the timelock, by resetting the delay to 0 and escalating privileges, thus gaining unrestricted access to assets held in the contract. Instances with the executor role set to "open" allow anyone to use the executor role, thus leaving the timelock at risk of being taken over by an attacker.
### Patches
A fix is included in the following releases of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`:
- 4.3.1
- 3.4.2
- 3.4.2-solc-0.7
Deployed instances of `TimelockController` should be replaced with a fixed version by migrating all assets, ownership, and roles.
### Workarounds
Revoke the executor role from accounts not strictly under the team's control. We recommend revoking all executors that are not also proposers. When applying this mitigation, ensure there is at least one proposer and executor remaining.
### References
[Post-mortem](https://forum.openzeppelin.com/t/timelockcontroller-vulnerability-postmortem/14958).
### Credits
The issue was identified by an anonymous white hat hacker through [Immunefi](https://immunefi.com/).
### For more information
If you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.
| {'CVE-2021-39167'} | 2021-09-13T20:30:11Z | 2021-08-30T16:12:38Z | CRITICAL | 10 | {'CWE-269'} | {'https://github.com/OpenZeppelin/openzeppelin-contracts/commit/cec4f2ef57495d8b1742d62846da212515d99dd5', 'https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/CHANGELOG.md#431', 'https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-fg47-3c2x-m2wr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39167', 'https://github.com/advisories/GHSA-fg47-3c2x-m2wr'} | null | {'https://github.com/OpenZeppelin/openzeppelin-contracts/commit/cec4f2ef57495d8b1742d62846da212515d99dd5'} | {'https://github.com/OpenZeppelin/openzeppelin-contracts/commit/cec4f2ef57495d8b1742d62846da212515d99dd5'} |
GHSA | GHSA-gg6x-xx78-448c | Reflected XSS when importing CSV in OctoberCMS | ### Impact
A user with the ability to use the import functionality of the `ImportExportController` behavior could be socially engineered by an attacker to upload a maliciously crafted CSV file which could result in a reflected XSS attack on the user in question
### Patches
Issue has been patched in Build 466 (v1.0.466).
### Workarounds
Apply https://github.com/octobercms/october/commit/cd0b6a791f995d86071a024464c1702efc50f46c to your installation manually if unable to upgrade to Build 466.
### References
Reported by [Sivanesh Ashok](https://stazot.com/)
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat assessment:
<img width="1100" alt="Screen Shot 2020-03-31 at 2 01 52 PM" src="https://user-images.githubusercontent.com/7253840/78070158-8f7ef580-7358-11ea-950c-226533f6a0a3.png"> | {'CVE-2020-5298'} | 2022-04-19T19:02:26Z | 2020-06-03T21:58:32Z | MODERATE | 4 | {'CWE-87'} | {'https://github.com/octobercms/october/commit/cd0b6a791f995d86071a024464c1702efc50f46c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5298', 'https://github.com/advisories/GHSA-gg6x-xx78-448c', 'https://github.com/octobercms/october/security/advisories/GHSA-gg6x-xx78-448c', 'http://packetstormsecurity.com/files/158730/October-CMS-Build-465-XSS-File-Read-File-Deletion-CSV-Injection.html', 'http://seclists.org/fulldisclosure/2020/Aug/2'} | null | {'https://github.com/octobercms/october/commit/cd0b6a791f995d86071a024464c1702efc50f46c'} | {'https://github.com/octobercms/october/commit/cd0b6a791f995d86071a024464c1702efc50f46c'} |
GHSA | GHSA-8gv3-57p6-g35r | Heap buffer overflow in `RaggedTensorToTensor` | ### Impact
An attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`:
```python
import tensorflow as tf
shape = tf.constant([10, 10], shape=[2], dtype=tf.int64)
values = tf.constant(0, shape=[1], dtype=tf.int64)
default_value = tf.constant(0, dtype=tf.int64)
l = [849, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
row = tf.constant(l, shape=[5, 43], dtype=tf.int64)
rows = [row]
types = ['ROW_SPLITS']
tf.raw_ops.RaggedTensorToTensor(
shape=shape, values=values, default_value=default_value,
row_partition_tensors=rows, row_partition_types=types)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel:
```cc
for (INDEX_TYPE i = 0; i < row_split_size - 1; ++i) {
INDEX_TYPE row_length = row_split(i + 1) - row_split(i);
INDEX_TYPE real_length = std::min(output_size, row_length);
INDEX_TYPE parent_output_index_current = parent_output_index[i];
...
}
```
Since the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when `parent_output_index` is shorter than `row_split`.
### Patches
We have patched the issue in GitHub commit [a84358aa12f0b1518e606095ab9cfddbf597c121](https://github.com/tensorflow/tensorflow/commit/a84358aa12f0b1518e606095ab9cfddbf597c121).
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-29560'} | 2022-04-26T18:10:15Z | 2021-05-21T14:24:57Z | LOW | 2.5 | {'CWE-787', 'CWE-125'} | {'https://github.com/advisories/GHSA-8gv3-57p6-g35r', 'https://github.com/tensorflow/tensorflow/commit/a84358aa12f0b1518e606095ab9cfddbf597c121', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8gv3-57p6-g35r', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29560'} | null | {'https://github.com/tensorflow/tensorflow/commit/a84358aa12f0b1518e606095ab9cfddbf597c121'} | {'https://github.com/tensorflow/tensorflow/commit/a84358aa12f0b1518e606095ab9cfddbf597c121'} |
GHSA | GHSA-j2x6-9323-fp7h | Integer bounds error in Vyper | ### Impact
in the following code, the return of `<iface>.returns_int128()` is not validated to fall within the bounds of `int128`. as of v0.3.0, `<iface>.returns_int128()` is validated in simple expressions, but not complex expressions.
```vyper
interface iface:
def returns_int128() -> int128: view
def returns_Bytes33() -> Bytes[33]: view
x: iface
@external
def call_out():
x: int128 = self.x.returns_int128() # affected, <0.3.0
y: uint256 = convert(self.x.returns_int128(), uint256) # affected, <0.3.2
z: Bytes[33] = concat(self.x.returns_Bytes33(), b"") # affected >= 0.3.0, <0.3.2
```
### Patches
0.3.2 (as of https://github.com/vyperlang/vyper/commit/049dbdc647b2ce838fae7c188e6bb09cf16e470b)
### Workarounds
Break up operations involving external calls into multiple statements. For instance, instead of the example above, use
```
x: int128 = self.x.returns_int128()
y: uint256 = convert(x, uint256)
``` | {'CVE-2022-24845'} | 2022-04-22T20:24:15Z | 2022-04-22T20:24:13Z | HIGH | 8.8 | {'CWE-190'} | {'https://github.com/vyperlang/vyper/security/advisories/GHSA-j2x6-9323-fp7h', 'https://github.com/advisories/GHSA-j2x6-9323-fp7h', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24845', 'https://github.com/vyperlang/vyper/commit/049dbdc647b2ce838fae7c188e6bb09cf16e470b'} | null | {'https://github.com/vyperlang/vyper/commit/049dbdc647b2ce838fae7c188e6bb09cf16e470b'} | {'https://github.com/vyperlang/vyper/commit/049dbdc647b2ce838fae7c188e6bb09cf16e470b'} |
GHSA | GHSA-q5pq-pgrv-fh89 | Critical severity vulnerability that affects dns-sync | The dns-sync module before 0.1.1 for node.js allows context-dependent attackers to execute arbitrary commands via shell metacharacters in the first argument to the resolve API function. | {'CVE-2014-9682'} | 2021-09-16T19:33:41Z | 2017-10-24T18:33:36Z | CRITICAL | 0 | {'CWE-77'} | {'https://nvd.nist.gov/vuln/detail/CVE-2014-9682', 'https://github.com/advisories/GHSA-q5pq-pgrv-fh89', 'http://www.openwall.com/lists/oss-security/2014/11/11/6', 'https://github.com/skoranga/node-dns-sync/commit/d9abaae384b198db1095735ad9c1c73d7b890a0d', 'https://github.com/skoranga/node-dns-sync/issues/1'} | null | {'https://github.com/skoranga/node-dns-sync/commit/d9abaae384b198db1095735ad9c1c73d7b890a0d'} | {'https://github.com/skoranga/node-dns-sync/commit/d9abaae384b198db1095735ad9c1c73d7b890a0d'} |
GHSA | GHSA-v4cp-h94r-m7xf | Use after free passing `externref`s to Wasm in Wasmtime | ### Impact
There was a use-after-free bug when passing `externref`s from the host to guest Wasm content.
To trigger the bug, you have to explicitly pass multiple `externref`s from the host to a Wasm instance at the same time, either by
* passing multiple `externref`s as arguments from host code to a Wasm function,
* or returning multiple `externref`s to Wasm from a multi-value return function defined in the host.
If you do not have host code that matches one of these shapes, then you are not impacted.
If Wasmtime's [`VMExternRefActivationsTable`](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/crates/runtime/src/externref.rs#L493) became filled to capacity after passing the first `externref` in, then passing in the second `externref` could trigger a garbage collection. However the first `externref` is not rooted until we pass control to Wasm, and therefore could be reclaimed by the collector if nothing else was holding a reference to it or otherwise keeping it alive. Then, when control was passed to Wasm after the garbage collection, Wasm could use the first `externref`, which at this point has already been freed.
We have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare.
### Patches
The bug has been fixed, and users should upgrade to Wasmtime 0.30.0.
Additionally, we have updated [our primary `externref` fuzz target](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/fuzz/fuzz_targets/table_ops.rs) such that it better exercises these code paths and we can have greater confidence in their correctness going forward.
### Workarounds
If you cannot upgrade Wasmtime yet, you can avoid the bug by disabling reference types support in Wasmtime by passing `false` to [`wasmtime::Config::wasm_reference_types`](https://docs.rs/wasmtime/0.29.0/wasmtime/struct.Config.html#method.wasm_reference_types).
### References
* [The reference types Wasm proposal, which introduces `externref`](https://github.com/WebAssembly/reference-types/)
### For more information
If you have any questions or comments about this advisory:
* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)
* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/) | {'CVE-2021-39216'} | 2022-04-19T19:03:08Z | 2021-09-20T19:54:05Z | MODERATE | 6.3 | {'CWE-416'} | {'https://github.com/advisories/GHSA-v4cp-h94r-m7xf', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WAVBRYDDUIY2ZR3K3FO4BVYJKIMJ5TP7/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z2Z33FTXFQ6EOINVEQIP4DFBG53G5XIY/', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-v4cp-h94r-m7xf', 'https://github.com/bytecodealliance/wasmtime/commit/101998733b74624cbd348a2366d05760b40181f3', 'https://crates.io/crates/wasmtime', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39216'} | null | {'https://github.com/bytecodealliance/wasmtime/commit/101998733b74624cbd348a2366d05760b40181f3'} | {'https://github.com/bytecodealliance/wasmtime/commit/101998733b74624cbd348a2366d05760b40181f3'} |
GHSA | GHSA-c3g4-w6cv-6v7h | Non-empty default inheritable capabilities for linux container in Buildah | A bug was found in Buildah where containers were created with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2).
This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set.
| {'CVE-2022-27651'} | 2022-04-19T18:02:47Z | 2022-04-01T13:56:42Z | MODERATE | 6.8 | {'CWE-276'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=2066840', 'https://github.com/containers/buildah/security/advisories/GHSA-c3g4-w6cv-6v7h', 'https://github.com/containers/buildah/pull/3855', 'https://github.com/containers/buildah/commit/e7e55c988c05dd74005184ceb64f097a0cfe645b', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7NETC7I6RTMMBRJJQVJOJUPDK4W4PQSJ/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2VWH6X6HOFPO6HTESF42HIJZEPXSWVIO/', 'https://github.com/advisories/GHSA-c3g4-w6cv-6v7h', 'https://github.com/containers/buildah/commit/90b3254c7404039c1c786999ac189654228f6e0e', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27651'} | null | {'https://github.com/containers/buildah/commit/90b3254c7404039c1c786999ac189654228f6e0e', 'https://github.com/containers/buildah/commit/e7e55c988c05dd74005184ceb64f097a0cfe645b'} | {'https://github.com/containers/buildah/commit/90b3254c7404039c1c786999ac189654228f6e0e', 'https://github.com/containers/buildah/commit/e7e55c988c05dd74005184ceb64f097a0cfe645b'} |
GHSA | GHSA-hj2j-77xm-mc5v | High severity vulnerability that affects Jinja2 | In Pallets Jinja before 2.8.1, str.format allows a sandbox escape. | {'CVE-2016-10745'} | 2021-09-14T17:21:43Z | 2019-04-10T14:30:13Z | HIGH | 8.6 | {'CWE-134'} | {'http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00030.html', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10745', 'http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00064.html', 'https://access.redhat.com/errata/RHSA-2019:4062', 'https://access.redhat.com/errata/RHSA-2019:3964', 'https://access.redhat.com/errata/RHSA-2019:1022', 'https://palletsprojects.com/blog/jinja-281-released/', 'https://access.redhat.com/errata/RHSA-2019:1237', 'https://github.com/advisories/GHSA-hj2j-77xm-mc5v', 'https://usn.ubuntu.com/4011-1/', 'https://usn.ubuntu.com/4011-2/', 'https://github.com/pallets/jinja/commit/9b53045c34e61013dc8f09b7e52a555fa16bed16', 'https://access.redhat.com/errata/RHSA-2019:1260'} | null | {'https://github.com/pallets/jinja/commit/9b53045c34e61013dc8f09b7e52a555fa16bed16'} | {'https://github.com/pallets/jinja/commit/9b53045c34e61013dc8f09b7e52a555fa16bed16'} |
GHSA | GHSA-hf6p-4rv2-9qrp | Path Traversal in bikshed | This affects the package bikeshed before 3.0.0. This can occur when an untrusted source file containing include, include-code or include-raw block is processed. The contents of arbitrary files could be disclosed in the HTML output. | {'CVE-2021-23423'} | 2021-08-30T16:25:42Z | 2021-08-30T16:25:42Z | MODERATE | 5.5 | {'CWE-22'} | {'https://github.com/advisories/GHSA-hf6p-4rv2-9qrp', 'https://snyk.io/vuln/SNYK-PYTHON-BIKESHED-1537647', 'https://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2dd', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23423'} | null | {'https://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2dd'} | {'https://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2dd'} |
GHSA | GHSA-7cqg-8449-rmfv | Observable Discrepancy in libsecp256k1-rs | A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack. | {'CVE-2019-20399'} | 2021-08-25T21:01:27Z | 2021-08-25T21:01:27Z | MODERATE | 5.9 | {'CWE-362', 'CWE-203'} | {'https://github.com/paritytech/libsecp256k1/commit/11ba23a9766a5079918cd9f515bc100bc8164b50', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20399', 'https://github.com/advisories/GHSA-7cqg-8449-rmfv'} | null | {'https://github.com/paritytech/libsecp256k1/commit/11ba23a9766a5079918cd9f515bc100bc8164b50'} | {'https://github.com/paritytech/libsecp256k1/commit/11ba23a9766a5079918cd9f515bc100bc8164b50'} |
GHSA | GHSA-cvgx-3v3q-m36c | Heap OOB in shape inference for `QuantizeV2` | ### Impact
The [shape inference code for `QuantizeV2`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/framework/common_shape_fns.cc#L2509-L2530) can trigger a read outside of bounds of heap allocated array:
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeV2(
input=[1.0,1.0],
min_range=[1.0,10.0],
max_range=[1.0,10.0],
T=tf.qint32,
mode='MIN_COMBINED',
round_mode='HALF_TO_EVEN',
narrow_range=False,
axis=-100,
ensure_minimum_range=10)
return data
test()
```
This occurs whenever `axis` is a negative value less than `-1`. In this case, we are accessing data before the start of a heap buffer:
```cc
int axis = -1;
Status s = c->GetAttr("axis", &axis);
if (!s.ok() && s.code() != error::NOT_FOUND) {
return s;
}
...
if (axis != -1) {
...
TF_RETURN_IF_ERROR(
c->Merge(c->Dim(minmax, 0), c->Dim(input, axis), &depth));
}
```
The code allows `axis` to be an optional argument (`s` would contain an `error::NOT_FOUND` error code). Otherwise, it assumes that `axis` is a valid index into the dimensions of the `input` tensor. If `axis` is less than `-1` then this results in a heap OOB read.
### Patches
We have patched the issue in GitHub commit [a0d64445116c43cf46a5666bd4eee28e7a82f244](https://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.
### 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-41211'} | 2021-11-10T19:01:03Z | 2021-11-10T19:01:03Z | HIGH | 7.1 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244', 'https://github.com/advisories/GHSA-cvgx-3v3q-m36c', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvgx-3v3q-m36c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41211'} | null | {'https://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244'} | {'https://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244'} |
GHSA | GHSA-9689-rx4v-cqgc | Open Redirect | Pivotal Concourse Release, versions 4.x prior to 4.2.2, login flow allows redirects to untrusted websites. A remote unauthenticated attacker could convince a user to click on a link using the oAuth redirect link with an untrusted website and gain access to that user's access token in Concourse. | {'CVE-2018-15798'} | 2022-04-12T22:10:05Z | 2022-02-15T01:57:18Z | MODERATE | 5.4 | {'CWE-601'} | {'https://github.com/concourse/concourse/blob/release/5.2.x/release-notes/v5.2.8.md', 'https://nvd.nist.gov/vuln/detail/CVE-2018-15798', 'https://github.com/concourse/concourse/pull/5350/commits/38cb4cc025e5ed28764b4adc363a0bbf41f3c7cb', 'https://github.com/advisories/GHSA-9689-rx4v-cqgc', 'https://pivotal.io/security/cve-2018-15798'} | null | {'https://github.com/concourse/concourse/pull/5350/commits/38cb4cc025e5ed28764b4adc363a0bbf41f3c7cb'} | {'https://github.com/concourse/concourse/pull/5350/commits/38cb4cc025e5ed28764b4adc363a0bbf41f3c7cb'} |
GHSA | GHSA-62g9-6hw5-rwfp | Path Traversal in resolve-path | Versions of `resolve-path` before 1.4.0 are vulnerable to path traversal. `resolve-path` relative path resolving suffers from a lack of file path sanitization for windows based paths.
## Recommendation
Update to version 1.4.0 or later. | {'CVE-2018-3732'} | 2021-01-08T21:07:10Z | 2018-07-18T21:20:25Z | HIGH | 0 | {'CWE-22'} | {'https://github.com/advisories/GHSA-62g9-6hw5-rwfp', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3732', 'https://hackerone.com/reports/315760', 'https://github.com/pillarjs/resolve-path/commit/fe5b8052cafd35fcdafe9210e100e9050b37d2a0', 'https://www.npmjs.com/advisories/573'} | null | {'https://github.com/pillarjs/resolve-path/commit/fe5b8052cafd35fcdafe9210e100e9050b37d2a0'} | {'https://github.com/pillarjs/resolve-path/commit/fe5b8052cafd35fcdafe9210e100e9050b37d2a0'} |
GHSA | GHSA-cq27-v7xp-c356 | Moderate severity vulnerability that affects pycrypto | Heap-based buffer overflow in the ALGnew function in block_templace.c in Python Cryptography Toolkit (aka pycrypto) allows remote attackers to execute arbitrary code as demonstrated by a crafted iv parameter to cryptmsg.py. | {'CVE-2013-7459'} | 2021-09-09T20:09:53Z | 2018-12-14T18:51:38Z | CRITICAL | 9.8 | {'CWE-119'} | {'https://github.com/dlitz/pycrypto/commit/8dbe0dc3eea5c689d4f76b37b93fe216cf1f00d4', 'https://security.gentoo.org/glsa/201702-14', 'https://github.com/advisories/GHSA-cq27-v7xp-c356', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RJ37R2YLX56YZABFNAOWV4VTHTGYREAE/', 'https://nvd.nist.gov/vuln/detail/CVE-2013-7459', 'https://pony7.fr/ctf:public:32c3:cryptmsg', 'https://bugzilla.redhat.com/show_bug.cgi?id=1409754', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C6BWNADPLKDBBQBUT3P75W7HAJCE7M3B/', 'https://github.com/dlitz/pycrypto/issues/176', 'http://www.securityfocus.com/bid/95122', 'http://www.openwall.com/lists/oss-security/2016/12/27/8'} | null | {'https://github.com/dlitz/pycrypto/commit/8dbe0dc3eea5c689d4f76b37b93fe216cf1f00d4'} | {'https://github.com/dlitz/pycrypto/commit/8dbe0dc3eea5c689d4f76b37b93fe216cf1f00d4'} |
GHSA | GHSA-wvhm-4hhf-97x9 | Cross-Site Scripting in Prism | ### Impact
The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer.
This impacts all Safari and Internet Explorer users of Prism >=v1.1.0 that use the _Previewers_ plugin (>=v1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0).
### Patches
This problem is patched in v1.21.0.
### Workarounds
To workaround the issue without upgrading, [disable the easing preview](https://prismjs.com/plugins/previewers/#disabling-a-previewer) on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround.
### References
The vulnerability was introduced by this [commit](https://github.com/PrismJS/prism/commit/4303c940d3d3a20e8ce7635bf23331c75060f5c5) on Sep 29, 2015 and fixed by [Masato Kinugawa](https://twitter.com/kinugawamasato) (#2506).
### For more information
If you have any questions or comments about this advisory, please [open an issue](https://github.com/PrismJS/prism/issues). | {'CVE-2020-15138'} | 2022-04-19T19:02:32Z | 2020-08-07T22:28:30Z | HIGH | 7.1 | {'CWE-79'} | {'https://prismjs.com/plugins/previewers/#disabling-a-previewer', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15138', 'https://github.com/PrismJS/prism/pull/2506/commits/7bd7de05edf71112a3a77f87901a2409c9c5c20c', 'https://github.com/advisories/GHSA-wvhm-4hhf-97x9', 'https://github.com/PrismJS/prism/security/advisories/GHSA-wvhm-4hhf-97x9'} | null | {'https://github.com/PrismJS/prism/pull/2506/commits/7bd7de05edf71112a3a77f87901a2409c9c5c20c'} | {'https://github.com/PrismJS/prism/pull/2506/commits/7bd7de05edf71112a3a77f87901a2409c9c5c20c'} |
GHSA | GHSA-88cw-3m6x-49f7 | Out-of-bounds Write in ChakraCore | Chakra Scripting Engine Memory Corruption Vulnerability This CVE ID is unique from CVE-2020-17048. | {'CVE-2020-17054'} | 2021-08-02T17:25:58Z | 2021-08-02T17:25:58Z | HIGH | 7.5 | {'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-17054', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-17054', 'https://github.com/chakra-core/ChakraCore/pull/6528/commits/e81e8a51ec7ba3d0dfb6089254f166c2733216e1', 'https://github.com/chakra-core/ChakraCore/pull/6528', 'https://github.com/advisories/GHSA-88cw-3m6x-49f7'} | null | {'https://github.com/chakra-core/ChakraCore/pull/6528/commits/e81e8a51ec7ba3d0dfb6089254f166c2733216e1'} | {'https://github.com/chakra-core/ChakraCore/pull/6528/commits/e81e8a51ec7ba3d0dfb6089254f166c2733216e1'} |
GHSA | GHSA-57f3-gghm-9mhc | Regular Expression Denial of Service (ReDoS) | This affects the package jspdf before 2.3.1. ReDoS is possible via the addImage function. | {'CVE-2021-23353'} | 2021-03-25T00:18:31Z | 2021-03-12T21:28:46Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-57f3-gghm-9mhc', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1083287', 'https://github.com/MrRio/jsPDF/pull/3091', 'https://github.com/MrRio/jsPDF/commit/d8bb3b39efcd129994f7a3b01b632164144ec43e', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1083286', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBMRRIO-1083288', 'https://snyk.io/vuln/SNYK-JS-JSPDF-1073626', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23353', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1083289'} | null | {'https://github.com/MrRio/jsPDF/commit/d8bb3b39efcd129994f7a3b01b632164144ec43e'} | {'https://github.com/MrRio/jsPDF/commit/d8bb3b39efcd129994f7a3b01b632164144ec43e'} |
GHSA | GHSA-5fxf-x22x-5q38 | Cross-site Scripting in microweber | XSS on dynamic_text module in GitHub repository microweber/microweber prior to 1.2.12. | {'CVE-2022-0929'} | 2022-03-22T20:02:31Z | 2022-03-13T00:00:54Z | MODERATE | 6.8 | {'CWE-79'} | {'https://huntr.dev/bounties/66abf7ec-2dd7-4cb7-87f5-e91375883f03', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0929', 'https://github.com/microweber/microweber/commit/de6d17b52d261902653fbdd2ecefcaac82e54256', 'https://github.com/advisories/GHSA-5fxf-x22x-5q38'} | null | {'https://github.com/microweber/microweber/commit/de6d17b52d261902653fbdd2ecefcaac82e54256'} | {'https://github.com/microweber/microweber/commit/de6d17b52d261902653fbdd2ecefcaac82e54256'} |
GHSA | GHSA-8wr4-2wm6-w3pr | B2 Command Line Tool TOCTOU application key disclosure | ### Impact
Linux and Mac releases of the B2 command-line tool version 3.2.0 and below contain a key disclosure vulnerability that, in certain conditions, can be exploited by local attackers through a time-of-check-time-of-use (TOCTOU) race condition.
The command line tool saves API keys (and bucket name-to-id mapping) in a local database file (`$XDG_CONFIG_HOME/b2/account_info`, `~/.b2_account_info` or a user-defined path) when `b2 authorize-account` is first run. This happens regardless of whether a valid key is provided or not. When first created, the file is world readable and is (typically a few milliseconds) later altered to be private to the user. If the directory is readable by a local attacker and the user did not yet run `b2 authorize-account` then during the brief period between file creation and permission modification, a local attacker can race to open the file and maintain a handle to it. This allows the local attacker to read the contents after the file after the sensitive information has been saved to it.
### Remediation
Users that have not yet run `b2 authorize-account` should upgrade to B2 Command-Line Tool v3.2.1 before running it.
Users that have run `b2 authorize-account` are safe if at the time of the file creation no other local users had read access to the local configuration file.
Users that have run `b2 authorize-account` where the designated path could be opened by another local user should upgrade to B2 Command-Line Tool v3.2.1 and remove the database and regenerate all application keys. Note that `b2 clear-account` does not remove the database file and it should not be used to ensure that all open handles to the file are invalidated.
### Workarounds
If B2 Command-Line Tool cannot be upgraded to v3.2.1 due to a dependency conflict, a binary release can be used instead. Alternatively a new version could be installed within a virtualenv, or the permissions can be changed to prevent local users from opening the database file.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [B2 Command-Line Tool](https://github.com/Backblaze/B2_Command_Line_Tool) mentioning the CVE id in the issue title
* Email us at [security@backblaze.com](mailto:security@backblaze.com)
| {'CVE-2022-23653'} | 2022-04-19T19:03:23Z | 2022-02-24T13:11:51Z | MODERATE | 4.7 | {'CWE-367'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23653', 'https://github.com/Backblaze/B2_Command_Line_Tool/security/advisories/GHSA-8wr4-2wm6-w3pr', 'https://github.com/advisories/GHSA-8wr4-2wm6-w3pr', 'https://github.com/Backblaze/B2_Command_Line_Tool/commit/c74029f9f75065e8f7e3c3ec8e0a23fb8204feeb'} | null | {'https://github.com/Backblaze/B2_Command_Line_Tool/commit/c74029f9f75065e8f7e3c3ec8e0a23fb8204feeb'} | {'https://github.com/Backblaze/B2_Command_Line_Tool/commit/c74029f9f75065e8f7e3c3ec8e0a23fb8204feeb'} |
GHSA | GHSA-m3rf-7m4w-r66q | Improper Authentication in Flask-AppBuilder | ### Impact
Improper authentication on the REST API. Allows for a malicious actor with a carefully crafted request to successfully authenticate and gain access to existing protected REST API endpoints. Only affects non database authentication types, and new REST API endpoints.
### Patches
Upgrade to Flask-AppBuilder 3.3.4
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/dpgaspar/Flask-AppBuilder
| {'CVE-2021-41265'} | 2021-12-10T18:29:56Z | 2021-12-09T19:09:07Z | HIGH | 8.1 | {'CWE-287'} | {'https://github.com/dpgaspar/Flask-AppBuilder/releases/tag/v3.3.4', 'https://github.com/dpgaspar/Flask-AppBuilder/commit/eba517aab121afa3f3f2edb011ec6bc4efd61fbc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41265', 'https://github.com/dpgaspar/Flask-AppBuilder/security/advisories/GHSA-m3rf-7m4w-r66q', 'https://github.com/advisories/GHSA-m3rf-7m4w-r66q'} | null | {'https://github.com/dpgaspar/Flask-AppBuilder/commit/eba517aab121afa3f3f2edb011ec6bc4efd61fbc'} | {'https://github.com/dpgaspar/Flask-AppBuilder/commit/eba517aab121afa3f3f2edb011ec6bc4efd61fbc'} |
GHSA | GHSA-v7m9-9497-p9gr | Possible pod name collisions in jupyterhub-kubespawner | ### Impact
_What kind of vulnerability is it? Who is impacted?_
JupyterHub deployments using:
- KubeSpawner <= 0.11.1 (e.g. zero-to-jupyterhub 0.9.0) and
- enabled named_servers (not default), and
- an Authenticator that allows:
- usernames with hyphens or other characters that require escape (e.g. `user-hyphen` or `user@email`), and
- usernames which may match other usernames up to but not including the escaped character (e.g. `user` in the above cases)
In this circumstance, certain usernames will be able to craft particular server names which will grant them access to the default server of other users who have matching usernames.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
Patch will be released in kubespawner 0.12 and zero-to-jupyterhub 0.9.1
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
#### KubeSpawner
Specify configuration:
for KubeSpawner
```python
from traitlets import default
from kubespawner import KubeSpawner
class PatchedKubeSpawner(KubeSpawner):
@default("pod_name_template")
def _default_pod_name_template(self):
if self.name:
return "jupyter-{username}-{servername}"
else:
return "jupyter-{username}"
@default("pvc_name_template")
def _default_pvc_name_template(self):
if self.name:
return "claim-{username}-{servername}"
else:
return "claim-{username}"
c.JupyterHub.spawner_class = PatchedKubeSpawner
```
**Note for KubeSpawner:** this configuration will behave differently before and after the upgrade, so will need to be removed when upgrading. Only apply this configuration while still using KubeSpawner ≤ 0.11.1 and remove it after upgrade to ensure consistent pod and pvc naming.
Changing the name template means pvcs for named servers will have different names. This will result in orphaned PVCs for named servers across Hub upgrade! This may appear as data loss for users, depending on configuration, but the orphaned PVCs will still be around and data can be migrated manually (or new PVCs created manually to reference existing PVs) before deleting the old PVCs and/or PVs.
### References
_Are there any links users can visit to find out more?_
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [kubespawner](https://github.com/jupyterhub/kubespawner)
* Email us at [security@ipython.org](mailto:security@ipython.org)
Credit: Jining Huang | {'CVE-2020-15110'} | 2021-11-19T15:44:02Z | 2020-07-22T23:07:16Z | MODERATE | 6.8 | {'CWE-863'} | {'https://github.com/advisories/GHSA-v7m9-9497-p9gr', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15110', 'https://github.com/jupyterhub/kubespawner/security/advisories/GHSA-v7m9-9497-p9gr', 'https://github.com/jupyterhub/kubespawner/commit/3dfe870a7f5e98e2e398b01996ca6b8eff4bb1d0'} | null | {'https://github.com/jupyterhub/kubespawner/commit/3dfe870a7f5e98e2e398b01996ca6b8eff4bb1d0'} | {'https://github.com/jupyterhub/kubespawner/commit/3dfe870a7f5e98e2e398b01996ca6b8eff4bb1d0'} |
GHSA | GHSA-vxrc-68xx-x48g | Sandbox Information Disclosure | A sandbox information disclosure exists in Twig before 1.38.0 and 2.x before 2.7.0 because, under some circumstances, it is possible to call the __toString() method on an object even if not allowed by the security policy in place. | {'CVE-2019-9942'} | 2022-04-06T20:28:17Z | 2022-03-26T00:25:25Z | LOW | 3.7 | null | {'https://seclists.org/bugtraq/2019/Mar/60', 'https://www.debian.org/security/2019/dsa-4419', 'https://github.com/twigphp/Twig/commit/eac5422956e1dcca89a3669a03a3ff32f0502077', 'https://symfony.com/blog/twig-sandbox-information-disclosure', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/twig/twig/CVE-2019-9942.yaml', 'https://github.com/advisories/GHSA-vxrc-68xx-x48g', 'https://nvd.nist.gov/vuln/detail/CVE-2019-9942'} | null | {'https://github.com/twigphp/Twig/commit/eac5422956e1dcca89a3669a03a3ff32f0502077'} | {'https://github.com/twigphp/Twig/commit/eac5422956e1dcca89a3669a03a3ff32f0502077'} |
GHSA | GHSA-v73w-r9xg-7cr9 | Use of insecure jQuery version in OctoberCMS | ### Impact
Passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code.
### Patches
Issue has been patched in Build 466 (v1.0.466) by applying the recommended patch from @jquery.
### Workarounds
Apply https://github.com/octobercms/october/commit/5c7ba9fbe9f2b596b2f0e3436ee06b91b97e5892 to your installation manually if unable to upgrade to Build 466.
### References
- https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11022
- https://jquery.com/upgrade-guide/3.5/
### For more information
If you have any questions or comments about this advisory:
* Email us at [octobercms@luketowers.ca](mailto:octobercms@luketowers.ca) & [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat Assessment
Assessed as Moderate by the @jquery team.
### Acknowledgements
Thanks to @mrgswift for reporting the issue to the October CMS team. | null | 2022-04-19T19:02:27Z | 2020-06-05T19:37:49Z | MODERATE | 0 | null | {'https://github.com/advisories/GHSA-v73w-r9xg-7cr9', 'https://github.com/octobercms/october/commit/5c7ba9fbe9f2b596b2f0e3436ee06b91b97e5892', 'https://github.com/octobercms/october/issues/5097', 'https://github.com/octobercms/october/security/advisories/GHSA-v73w-r9xg-7cr9'} | null | {'https://github.com/octobercms/october/commit/5c7ba9fbe9f2b596b2f0e3436ee06b91b97e5892'} | {'https://github.com/octobercms/october/commit/5c7ba9fbe9f2b596b2f0e3436ee06b91b97e5892'} |
GHSA | GHSA-8843-m7mw-mxqm | Buffer overflow in Pillow | In Pillow before 6.2.3 and 7.x before 7.0.1, there are two Buffer Overflows in libImaging/TiffDecode.c. | {'CVE-2020-10379'} | 2021-09-22T21:45:09Z | 2020-07-27T21:52:41Z | HIGH | 7.8 | {'CWE-120'} | {'https://github.com/python-pillow/Pillow/commits/master/src/libImaging', 'https://github.com/python-pillow/Pillow/commit/46f4a349b88915787fea3fb91348bb1665831bbb#diff-9478f2787e3ae9668a15123b165c23ac', 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.3.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10379', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/', 'https://snyk.io/vuln/SNYK-PYTHON-PILLOW-574577', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/', 'https://usn.ubuntu.com/4430-2/', 'https://github.com/advisories/GHSA-8843-m7mw-mxqm', 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html', 'https://github.com/python-pillow/Pillow/pull/4538'} | null | {'https://github.com/python-pillow/Pillow/commit/46f4a349b88915787fea3fb91348bb1665831bbb#diff-9478f2787e3ae9668a15123b165c23ac'} | {'https://github.com/python-pillow/Pillow/commit/46f4a349b88915787fea3fb91348bb1665831bbb#diff-9478f2787e3ae9668a15123b165c23ac'} |
GHSA | GHSA-m2wv-m5pf-284r | Cross-site Scripting in teampass | Teampass 2.1.26 allows reflected XSS via the index.php PATH_INFO. Someone must open a link for the Teampass Password Manager index page containing malicious payload. | {'CVE-2022-26980'} | 2022-04-05T21:07:47Z | 2022-03-29T00:01:09Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-26980', 'https://github.com/advisories/GHSA-m2wv-m5pf-284r', 'https://github.com/nilsteampassnet/TeamPass/commits/teampass_2', 'https://gist.github.com/RNPG/6919286e0daebce7634d0a744e060dca'} | null | {'https://github.com/nilsteampassnet/TeamPass/commits/teampass_2'} | {'https://github.com/nilsteampassnet/TeamPass/commits/teampass_2'} |
GHSA | GHSA-gx7g-wjxg-jwwj | Cross-Site Request Forgery in YOURLS | YOURLS versions 1.8.2 and prior are vulnerable to Cross-Site Request Forgery. | {'CVE-2022-0088'} | 2022-04-18T22:17:43Z | 2022-04-04T00:00:55Z | LOW | 3.5 | {'CWE-352'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0088', 'https://github.com/yourls/yourls/commit/1de256d8694b0ec7d4df2ac1d5976d4055e09d59', 'https://huntr.dev/bounties/d01f0726-1a0f-4575-ae17-4b5319b11c29', 'https://github.com/YOURLS/YOURLS/pull/3264', 'https://github.com/YOURLS/YOURLS/issues/3170', 'https://github.com/advisories/GHSA-gx7g-wjxg-jwwj'} | null | {'https://github.com/yourls/yourls/commit/1de256d8694b0ec7d4df2ac1d5976d4055e09d59'} | {'https://github.com/yourls/yourls/commit/1de256d8694b0ec7d4df2ac1d5976d4055e09d59'} |
GHSA | GHSA-9hgc-wpc5-v8p9 | An attacker can execute malicious javascript in Live Helper Chat | Cross-site Scripting (XSS) in GitHub repository livehelperchat/livehelperchat prior to 3.99v. Attacker can execute malicious javascript on application. | {'CVE-2022-1530'} | 2022-05-03T20:49:16Z | 2022-04-30T00:00:37Z | LOW | 0 | {'CWE-79'} | {'https://github.com/livehelperchat/livehelperchat/commit/edef7a8387be718d0de2dfd1e722789afb0461bc', 'https://huntr.dev/bounties/8fd8de01-7e83-4324-9cc8-a97acb9b70d6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1530', 'https://github.com/advisories/GHSA-9hgc-wpc5-v8p9'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/edef7a8387be718d0de2dfd1e722789afb0461bc'} | {'https://github.com/livehelperchat/livehelperchat/commit/edef7a8387be718d0de2dfd1e722789afb0461bc'} |
GHSA | GHSA-h5g2-38x9-4gv3 | High severity vulnerability that affects archive-tar-minitar and minitar | Directory traversal vulnerability in the minitar before 0.6 and archive-tar-minitar 0.5.2 gems for Ruby allows remote attackers to write to arbitrary files via a .. (dot dot) in a TAR archive entry. | {'CVE-2016-10173'} | 2021-09-13T16:33:15Z | 2017-10-24T18:33:35Z | HIGH | 7.5 | {'CWE-22'} | {'https://security.gentoo.org/glsa/201702-32', 'https://github.com/advisories/GHSA-h5g2-38x9-4gv3', 'https://github.com/halostatue/minitar/commit/e25205ecbb6277ae8a3df1e6a306d7ed4458b6e4', 'https://puppet.com/security/cve/cve-2016-10173', 'http://www.securityfocus.com/bid/95874', 'https://github.com/halostatue/minitar/issues/16', 'http://www.openwall.com/lists/oss-security/2017/01/24/7', 'http://www.debian.org/security/2017/dsa-3778', 'http://www.openwall.com/lists/oss-security/2017/01/29/1', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10173'} | null | {'https://github.com/halostatue/minitar/commit/e25205ecbb6277ae8a3df1e6a306d7ed4458b6e4'} | {'https://github.com/halostatue/minitar/commit/e25205ecbb6277ae8a3df1e6a306d7ed4458b6e4'} |
GHSA | GHSA-v222-6mr4-qj29 | Command Injection vulnerability in asciidoctor-include-ext | ### Impact
Applications using [Asciidoctor (Ruby)](https://github.com/asciidoctor/asciidoctor) with [asciidoctor-include-ext](https://github.com/jirutka/asciidoctor-include-ext) (prior to version 0.4.0), which render user-supplied input in AsciiDoc markup, may allow an attacker to execute arbitrary system commands on the host operating system. ~~This attack is possible even when `allow-uri-read` is disabled!~~ (EDIT: it’s not)
### Patches
The vulnerability has been fixed in commit c7ea001 (and further improved in cbaccf3), which is included in version [0.4.0](https://rubygems.org/gems/asciidoctor-include-ext/versions/0.4.0).
### Workarounds
```rb
require 'asciidoctor/include_ext'
class Asciidoctor::IncludeExt::IncludeProcessor
# Overrides superclass private method to mitigate Command Injection
# vulnerability in asciidoctor-include-ext <0.4.0.
def target_uri?(target)
target.downcase.start_with?('http://', 'https://') \
&& URI.parse(target).is_a?(URI::HTTP)
rescue URI::InvalidURIError
false
end
end
```
### References
* https://sakurity.com/blog/2015/02/28/openuri.html
### Credits
This vulnerability was discovered by Joern Schneeweisz from the GitLab Security Research Team.
### For more information
See commit message c7ea001.
If you have any questions or comments about this advisory open an issue in [jirutka/asciidoctor-include-ext](https://github.com/jirutka/asciidoctor-include-ext/issues/). | {'CVE-2022-24803'} | 2022-04-06T21:24:00Z | 2022-03-31T23:27:15Z | CRITICAL | 10 | {'CWE-78'} | {'https://github.com/advisories/GHSA-v222-6mr4-qj29', 'https://github.com/jirutka/asciidoctor-include-ext/security/advisories/GHSA-v222-6mr4-qj29', 'https://github.com/jirutka/asciidoctor-include-ext/commit/cbaccf3de533cbca224bf61d0b74e4b84d41d8ee', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24803', 'https://github.com/jirutka/asciidoctor-include-ext/commit/c7ea001a597c7033575342c51483dab7b87ae155'} | null | {'https://github.com/jirutka/asciidoctor-include-ext/commit/cbaccf3de533cbca224bf61d0b74e4b84d41d8ee', 'https://github.com/jirutka/asciidoctor-include-ext/commit/c7ea001a597c7033575342c51483dab7b87ae155'} | {'https://github.com/jirutka/asciidoctor-include-ext/commit/c7ea001a597c7033575342c51483dab7b87ae155', 'https://github.com/jirutka/asciidoctor-include-ext/commit/cbaccf3de533cbca224bf61d0b74e4b84d41d8ee'} |
GHSA | GHSA-5gjh-5j4f-cpwv | Unrestricted Upload of File with Dangerous Type in Gogs | ### Impact
The malicious user is able to upload a crafted `config` file into repository's `.git` directory with to gain SSH access to the server. All installations with [repository upload enabled (default)](https://github.com/gogs/gogs/blob/f36eeedbf89328ee70cc3a2e239f6314f9021f58/conf/app.ini#L127-L129) are affected.
### Patches
Repository file uploads are prohibited to its `.git` directory. Users should upgrade to 0.12.6 or the latest 0.13.0+dev.
### Workarounds
[Disable repository files upload](https://github.com/gogs/gogs/blob/f36eeedbf89328ee70cc3a2e239f6314f9021f58/conf/app.ini#L128-L129).
### References
https://huntr.dev/bounties/b4928cfe-4110-462f-a180-6d5673797902/
### For more information
If you have any questions or comments about this advisory, please post on #6833.
| {'CVE-2022-0415'} | 2022-03-29T22:02:35Z | 2022-03-28T16:46:41Z | HIGH | 8.8 | {'CWE-434', 'CWE-20'} | {'https://github.com/gogs/gogs/commit/0fef3c9082269e9a4e817274942a5d7c50617284', 'https://huntr.dev/bounties/b4928cfe-4110-462f-a180-6d5673797902', 'https://github.com/gogs/gogs/security/advisories/GHSA-5gjh-5j4f-cpwv', 'https://github.com/gogs/gogs/pull/6838', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0415', 'https://github.com/gogs/gogs/issues/6833', 'https://github.com/advisories/GHSA-5gjh-5j4f-cpwv'} | null | {'https://github.com/gogs/gogs/commit/0fef3c9082269e9a4e817274942a5d7c50617284'} | {'https://github.com/gogs/gogs/commit/0fef3c9082269e9a4e817274942a5d7c50617284'} |
GHSA | GHSA-6898-wx94-8jq8 | Potential Command Injection in libnotify | Versions 1.0.3 and earlier of libnotify are affected by a shell command injection vulnerability. This may result in execution of arbitrary shell commands, if user input is passed into libnotify.notify.
Untrusted input passed in the call to libnotify.notify could result in execution of shell commands. Callers may be unaware of this.
### Example
```
var libnotify = require('libnotify')
libnotify.notify('UNTRUSTED INPUT', { title: \"\" }, function () {
console.log(arguments);
})
```
Special thanks to Neal Poole for submitting the pull request to fix this issue.
## Recommendation
Update to version 1.0.4 or greater | {'CVE-2013-7381'} | 2021-09-23T20:55:30Z | 2020-08-31T22:50:48Z | CRITICAL | 9.8 | {'CWE-74'} | {'https://nvd.nist.gov/vuln/detail/CVE-2013-7381', 'https://nodesecurity.io/advisories/libnotify_potential_command_injection_in_libnotify.notify', 'https://www.npmjs.com/advisories/20', 'https://github.com/advisories/GHSA-6898-wx94-8jq8', 'https://github.com/mytrile/node-libnotify/commit/dfe7801d73a0dda10663a0ff3d0ec8b4d5f0d448', 'http://www.openwall.com/lists/oss-security/2014/05/15/2', 'http://www.openwall.com/lists/oss-security/2014/05/13/1'} | null | {'https://github.com/mytrile/node-libnotify/commit/dfe7801d73a0dda10663a0ff3d0ec8b4d5f0d448'} | {'https://github.com/mytrile/node-libnotify/commit/dfe7801d73a0dda10663a0ff3d0ec8b4d5f0d448'} |
GHSA | GHSA-fjqm-246c-mwqg | In Bouncy Castle JCE Provider the other party DH public key is not fully validated | In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of release 1.56 the key parameters are checked on agreement calculation. | {'CVE-2016-1000346'} | 2022-04-27T13:35:25Z | 2018-10-17T16:27:28Z | LOW | 3.7 | null | {'https://security.netapp.com/advisory/ntap-20181127-0004/', 'https://access.redhat.com/errata/RHSA-2018:2927', 'https://github.com/advisories/GHSA-fjqm-246c-mwqg', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000346', 'https://access.redhat.com/errata/RHSA-2018:2669', 'https://usn.ubuntu.com/3727-1/', 'https://github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714c194e7495#diff-d525a20b8acaed791ae2f0f770eb5937', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html'} | null | {'https://github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714c194e7495#diff-d525a20b8acaed791ae2f0f770eb5937'} | {'https://github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714c194e7495#diff-d525a20b8acaed791ae2f0f770eb5937'} |
GHSA | GHSA-2p89-5f22-8qvf | Exposure of Sensitive Information to an Unauthorized Actor | Shopware is an open source eCommerce platform. Versions prior to 6.3.5.1 may leak of information via Store-API. The vulnerability could only be fixed by changing the API system, which involves a non-backward-compatible change. Only consumers of the Store-API should be affected by this change. We recommend to update to the current version 6.3.5.1. You can get the update to 6.3.5.1 regularly via the Auto-Updater or directly via the download overview. https://www.shopware.com/en/download/#shopware-6 The vulnerability could only be fixed by changing the API system, which involves a non-backward-compatible change. Only consumers of the Store-API should be affected by this change. Please check your plugins if you have it in use. Detailed technical information can be found in the upgrade information. https://github.com/shopware/platform/blob/v6.3.5.1/UPGRADE-6.3.md#6351 ### Workarounds For older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version. https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659 ### For more information https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021 | {'CVE-2021-32711'} | 2021-09-08T18:00:32Z | 2021-09-08T18:00:32Z | CRITICAL | 9.1 | {'CWE-200'} | {'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021', 'https://github.com/shopware/platform/commit/157fb84a8b3b4ace4be165a033d559826704829b', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32711', 'https://github.com/shopware/platform/security/advisories/GHSA-f2vv-h5x4-57gr', 'https://github.com/advisories/GHSA-2p89-5f22-8qvf'} | null | {'https://github.com/shopware/platform/commit/157fb84a8b3b4ace4be165a033d559826704829b'} | {'https://github.com/shopware/platform/commit/157fb84a8b3b4ace4be165a033d559826704829b'} |
GHSA | GHSA-ph98-v78f-jqrm | SQL injection in jackalope/jackalope-doctrine-dbal | ### Impact
Users can provoke SQL injections if they can specify a node name or query.
### Patches
Upgrade to version 1.7.4
If that is not possible, you can escape all places where `$property` is used to filter `sv:name` in the class `Jackalope\Transport\DoctrineDBAL\Query\QOMWalker`: `XPath::escape($property)`.
### Workarounds
Node names and xpaths can contain `"` or `;` according to the JCR specification. The jackalope component that translates the query object model into doctrine dbal queries does not properly escape the names and paths, so that a accordingly crafted node name can lead to an SQL injection.
If queries are never done from user input, or if you validate the user input to not contain `;`, you are not affected.
### References
No further references.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [jackalope/jackalope-doctrine-dbal repo](https://github.com/jackalope/jackalope-doctrine-dbal/issues)
| {'CVE-2021-43822'} | 2022-04-19T19:03:17Z | 2021-12-14T21:08:13Z | HIGH | 8.5 | {'CWE-89'} | {'https://github.com/jackalope/jackalope-doctrine-dbal/security/advisories/GHSA-ph98-v78f-jqrm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43822', 'https://github.com/advisories/GHSA-ph98-v78f-jqrm', 'https://github.com/jackalope/jackalope-doctrine-dbal/commit/9d179a36d320330ddb303ea3a7c98d3a33d231db'} | null | {'https://github.com/jackalope/jackalope-doctrine-dbal/commit/9d179a36d320330ddb303ea3a7c98d3a33d231db'} | {'https://github.com/jackalope/jackalope-doctrine-dbal/commit/9d179a36d320330ddb303ea3a7c98d3a33d231db'} |
GHSA | GHSA-fgv8-vj5c-2ppq | Incorrect Authorization in runc | runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory. | {'CVE-2019-16884'} | 2022-02-26T01:52:03Z | 2022-02-22T15:38:08Z | HIGH | 5.4 | {'CWE-863'} | {'http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00009.html', 'https://github.com/opencontainers/runc/pull/2129', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/62OQ2P7K5YDZ5BRCH2Q6DHUJIHQD3QCD/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SPK4JWP32BUIVDJ3YODZSOEVEW6BHQCF/', 'https://github.com/opencontainers/runc/issues/2128', 'https://security.netapp.com/advisory/ntap-20220221-0004/', 'https://access.redhat.com/errata/RHSA-2019:3940', 'https://security.gentoo.org/glsa/202003-21', 'https://access.redhat.com/errata/RHSA-2019:4269', 'https://github.com/advisories/GHSA-fgv8-vj5c-2ppq', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DGK6IV5JGVDXHOXEKJOJWKOVNZLT6MYR/', 'https://access.redhat.com/errata/RHSA-2019:4074', 'https://github.com/crosbymichael/runc/commit/78dce1cf1ec36bbe7fe6767bdb81f7cbf6d34d70', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16884', 'http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00073.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00010.html', 'https://usn.ubuntu.com/4297-1/'} | null | {'https://github.com/crosbymichael/runc/commit/78dce1cf1ec36bbe7fe6767bdb81f7cbf6d34d70'} | {'https://github.com/crosbymichael/runc/commit/78dce1cf1ec36bbe7fe6767bdb81f7cbf6d34d70'} |
GHSA | GHSA-5w8q-x7hc-jhp6 | Directory Traversal in node-simple-router | Affected versions of `node-simple-router` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.
Example request:
```
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
```
## Recommendation
Update to v0.10.1 or later. | {'CVE-2017-16083'} | 2021-01-08T19:48:06Z | 2018-07-24T19:42:39Z | HIGH | 0 | {'CWE-22'} | {'https://github.com/JacksonGL/NPM-Vuln-PoC/tree/master/directory-traversal/node-simple-router', 'https://github.com/advisories/GHSA-5w8q-x7hc-jhp6', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16083', 'https://nodesecurity.io/advisories/352', 'https://github.com/sandy98/node-simple-router/commit/dfdd52e2e80607af433097d940b3834fd96df488', 'https://www.npmjs.com/advisories/352'} | null | {'https://github.com/sandy98/node-simple-router/commit/dfdd52e2e80607af433097d940b3834fd96df488'} | {'https://github.com/sandy98/node-simple-router/commit/dfdd52e2e80607af433097d940b3834fd96df488'} |
GHSA | GHSA-f93p-f762-vr53 | Reflected Cross-Site Scripting in Apache CXF | By default, Apache CXF creates a /services page containing a listing of the available endpoint names and addresses. This webpage is vulnerable to a reflected Cross-Site Scripting (XSS) attack, which allows a malicious actor to inject javascript into the web page. Please note that the attack exploits a feature which is not typically not present in modern browsers, who remove dot segments before sending the request. However, Mobile applications may be vulnerable. | {'CVE-2019-17573'} | 2021-06-17T19:57:01Z | 2020-06-10T20:02:33Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-17573', 'https://lists.apache.org/thread.html/r36e44ffc1a9b365327df62cdfaabe85b9a5637de102cea07d79b2dbf@%3Ccommits.cxf.apache.org%3E', 'http://cxf.apache.org/security-advisories.data/CVE-2019-17573.txt.asc?version=1&modificationDate=1579178542000&api=v2', 'https://lists.apache.org/thread.html/rf3b50583fefce2810cbd37c3d358cbcd9a03e750005950bf54546194@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/r51fdd73548290b2dfd0b48f7ab69bf9ae064dd100364cd8a15f0b3ec@%3Cdev.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rec7160382badd3ef4ad017a22f64a266c7188b9ba71394f0d321e2d4@%3Ccommits.cxf.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://github.com/apache/cxf/commit/a02e96ba1095596bef481919f16a90c5e80a92c8', 'https://lists.apache.org/thread.html/rff42cfa5e7d75b7c1af0e37589140a8f1999e578a75738740b244bd4@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rd49aabd984ed540c8ff7916d4d79405f3fa311d2fdbcf9ed307839a6@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/r51fdd73548290b2dfd0b48f7ab69bf9ae064dd100364cd8a15f0b3ec@%3Cusers.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rfb87e0bf3995e7d560afeed750fac9329ff5f1ad49da365129b7f89e@%3Ccommits.cxf.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://lists.apache.org/thread.html/r81a41a2915985d49bc3ea57dde2018b03584a863878a8532a89f993f@%3Cusers.cxf.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2020/11/12/2', 'https://github.com/advisories/GHSA-f93p-f762-vr53', 'https://lists.apache.org/thread.html/r51fdd73548290b2dfd0b48f7ab69bf9ae064dd100364cd8a15f0b3ec@%3Cannounce.apache.org%3E'} | null | {'https://github.com/apache/cxf/commit/a02e96ba1095596bef481919f16a90c5e80a92c8'} | {'https://github.com/apache/cxf/commit/a02e96ba1095596bef481919f16a90c5e80a92c8'} |
GHSA | GHSA-qvf8-p83w-v58j | Podman's default inheritable capabilities for linux container not empty | A bug was found in Podman where containers were created with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2).
This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. | {'CVE-2022-27649'} | 2022-05-02T17:42:54Z | 2022-04-01T20:52:29Z | HIGH | 7.5 | {'CWE-276'} | {'https://github.com/containers/podman/releases/tag/v4.0.3', 'https://bugzilla.redhat.com/show_bug.cgi?id=2066568', 'https://github.com/containers/podman/security/advisories/GHSA-qvf8-p83w-v58j', 'https://github.com/containers/podman/commit/aafa80918a245edcbdaceb1191d749570f1872d0', 'https://github.com/advisories/GHSA-qvf8-p83w-v58j', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27649', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J5WPM42UR6XIBQNQPNQHM32X7S4LJTRX/'} | null | {'https://github.com/containers/podman/commit/aafa80918a245edcbdaceb1191d749570f1872d0'} | {'https://github.com/containers/podman/commit/aafa80918a245edcbdaceb1191d749570f1872d0'} |
GHSA | GHSA-89mq-4x47-5v83 | Prototype Pollution in angular | Versions of `angular ` prior to 1.7.9 are vulnerable to prototype pollution. The deprecated API function `merge()` does not restrict the modification of an Object's prototype in the , which may allow an attacker to add or modify an existing property that will exist on all objects.
## Recommendation
Upgrade to version 1.7.9 or later. The function was already deprecated and upgrades are not expected to break functionality. | {'CVE-2019-10768'} | 2022-01-04T19:51:21Z | 2019-11-20T15:29:43Z | HIGH | 7.5 | {'CWE-20', 'CWE-915'} | {'https://snyk.io/vuln/SNYK-JS-ANGULAR-534884', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10768', 'https://github.com/angular/angular.js/pull/16913', 'https://www.npmjs.com/advisories/1343', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://github.com/angular/angular.js/commit/add78e62004e80bb1e16ab2dfe224afa8e513bc3', 'https://github.com/advisories/GHSA-89mq-4x47-5v83'} | null | {'https://github.com/angular/angular.js/commit/add78e62004e80bb1e16ab2dfe224afa8e513bc3'} | {'https://github.com/angular/angular.js/commit/add78e62004e80bb1e16ab2dfe224afa8e513bc3'} |
GHSA | GHSA-wf5p-f5xr-c4jj | SQL Injection in rosariosis | An unauthenticated SQL Injection vulnerability in Rosario Student Information System (aka rosariosis) before 8.1.1 allows remote attackers to execute PostgreSQL statements (e.g., SELECT, INSERT, UPDATE, and DELETE) through /Side.php via the syear parameter. | {'CVE-2021-44427'} | 2021-12-02T17:48:53Z | 2021-12-02T17:48:53Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://github.com/advisories/GHSA-wf5p-f5xr-c4jj', 'https://gitlab.com/francoisjacquet/rosariosis/-/commit/e001430aa9fb53d2502fb6f036f6c51c578d2016', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44427', 'https://github.com/francoisjacquet/rosariosis/commit/e001430aa9fb53d2502fb6f036f6c51c578d2016', 'https://gitlab.com/francoisjacquet/rosariosis/blob/mobile/CHANGES.md#changes-in-811', 'https://gitlab.com/francoisjacquet/rosariosis/-/issues/328'} | null | {'https://gitlab.com/francoisjacquet/rosariosis/-/commit/e001430aa9fb53d2502fb6f036f6c51c578d2016', 'https://github.com/francoisjacquet/rosariosis/commit/e001430aa9fb53d2502fb6f036f6c51c578d2016'} | {'https://github.com/francoisjacquet/rosariosis/commit/e001430aa9fb53d2502fb6f036f6c51c578d2016'} |
GHSA | GHSA-fjqg-w8g6-hhq8 | Improper Authentication and Improper Access Control in Dolibarr | In “Dolibarr” application, v3.3.beta1_20121221 to v13.0.2 have “Modify” access for admin level users to change other user’s details but fails to validate already existing “Login” name, while renaming the user “Login”. This leads to complete account takeover of the victim user. This happens since the password gets overwritten for the victim user having a similar login name. | {'CVE-2021-25956'} | 2021-10-21T14:19:44Z | 2021-09-02T17:16:28Z | HIGH | 7.2 | {'CWE-287', 'CWE-284'} | {'https://github.com/Dolibarr/dolibarr/commit/c4cba43bade736ab89e31013a6ccee59a6e077ee', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25956', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25956', 'https://github.com/advisories/GHSA-fjqg-w8g6-hhq8'} | null | {'https://github.com/Dolibarr/dolibarr/commit/c4cba43bade736ab89e31013a6ccee59a6e077ee'} | {'https://github.com/Dolibarr/dolibarr/commit/c4cba43bade736ab89e31013a6ccee59a6e077ee'} |
GHSA | GHSA-pgww-xf46-h92r | XSS in lxml | A XSS vulnerability was discovered in python-lxml's clean module. The module's parser didn't properly imitate browsers, which caused different behaviors between the sanitizer and the user's page. A remote attacker could exploit this flaw to run arbitrary HTML/JS code. | {'CVE-2020-27783'} | 2021-05-25T21:45:11Z | 2021-01-07T21:54:01Z | MODERATE | 6.1 | {'CWE-79'} | {'https://www.debian.org/security/2020/dsa-4810', 'https://github.com/advisories/GHSA-pgww-xf46-h92r', 'https://advisory.checkmarx.net/advisory/CX-2020-4286', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TMHVKRUT22LVWNL3TB7HPSDHJT74Q3JK/', 'https://lists.debian.org/debian-lts-announce/2020/12/msg00028.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27783', 'https://github.com/lxml/lxml/commit/a105ab8dc262ec6735977c25c13f0bdfcdec72a7', 'https://security.netapp.com/advisory/ntap-20210521-0003/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1901633', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JKG67GPGTV23KADT4D4GK4RMHSO4CIQL/', 'https://pypi.org/project/lxml/', 'https://snyk.io/vuln/SNYK-PYTHON-LXML-1047473'} | null | {'https://github.com/lxml/lxml/commit/a105ab8dc262ec6735977c25c13f0bdfcdec72a7'} | {'https://github.com/lxml/lxml/commit/a105ab8dc262ec6735977c25c13f0bdfcdec72a7'} |
GHSA | GHSA-w4hp-pcp8-qhf3 | Cross-site Scripting in livehelperchat | Stored XSS is found in Settings>Live help configuration>Departments->Departments groups->edit When a user creates a new webhook under the NAME field and puts a payload {{constructor.constructor('alert(1)')()}}, the input gets stored, at user edit groupname , the payload gets executed. | {'CVE-2022-0387'} | 2022-02-03T20:16:40Z | 2022-01-28T23:06:32Z | MODERATE | 5.4 | {'CWE-79'} | {'https://huntr.dev/bounties/2e09035b-8f98-4930-b7e8-7abe5f722b98', 'https://github.com/livehelperchat/livehelperchat/commit/ff70c7dd641b68b9afb170b89ec1ef003a4e3444', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0387', 'https://github.com/advisories/GHSA-w4hp-pcp8-qhf3'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/ff70c7dd641b68b9afb170b89ec1ef003a4e3444'} | {'https://github.com/livehelperchat/livehelperchat/commit/ff70c7dd641b68b9afb170b89ec1ef003a4e3444'} |
GHSA | GHSA-rgg3-3wh7-w935 | Unrestricted Upload of File with Dangerous Type in Zenario CMS | Zenario CMS 9.0.54156 is vulnerable to File Upload. The web server can be compromised by uploading and executing a web-shell which can run commands, browse system files, browse local resources, attack other servers, and exploit the local vulnerabilities, and so forth. | {'CVE-2021-42171'} | 2022-04-01T20:11:34Z | 2022-03-15T00:00:58Z | CRITICAL | 9.8 | {'CWE-434'} | {'https://github.com/advisories/GHSA-rgg3-3wh7-w935', 'https://github.com/TribalSystems/Zenario/commit/4566d8a9ac6755f098b3373252fdb17754a77007', 'https://github.com/hieuminhnv/Zenario-CMS-9.0-last-version/issues/2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42171', 'https://github.com/TribalSystems/Zenario/releases/tag/9.0.55141', 'https://minhnq22.medium.com/file-upload-to-rce-on-zenario-9-0-54156-cms-fa05fcc6cf74'} | null | {'https://github.com/TribalSystems/Zenario/commit/4566d8a9ac6755f098b3373252fdb17754a77007'} | {'https://github.com/TribalSystems/Zenario/commit/4566d8a9ac6755f098b3373252fdb17754a77007'} |
GHSA | GHSA-4r9c-jghc-cx5m | Cross-site Scripting in apostrophe | Apostrophe CMS versions between 2.63.0 to 3.3.1 are vulnerable to Stored XSS where an editor uploads an SVG file that contains malicious JavaScript onto the Images module, which triggers XSS once viewed. | {'CVE-2021-25978'} | 2021-11-10T16:45:34Z | 2021-11-10T16:45:34Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-4r9c-jghc-cx5m', 'https://github.com/apostrophecms/apostrophe/commit/c8b94ee9c79468f1ce28e31966cb0e0839165e59', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25978'} | null | {'https://github.com/apostrophecms/apostrophe/commit/c8b94ee9c79468f1ce28e31966cb0e0839165e59'} | {'https://github.com/apostrophecms/apostrophe/commit/c8b94ee9c79468f1ce28e31966cb0e0839165e59'} |
GHSA | GHSA-m9cj-v55f-8x26 | Authentication Bypass in keycloak | A flaw was found in Keycloak before version 12.0.0 where it is possible to update the user's metadata attributes using Account REST API. This flaw allows an attacker to change its own NameID attribute to impersonate the admin user for any particular application. | {'CVE-2020-27826'} | 2022-03-21T20:47:56Z | 2022-03-18T17:55:26Z | HIGH | 8.8 | {'CWE-250'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1905089', 'https://github.com/advisories/GHSA-m9cj-v55f-8x26', 'https://github.com/keycloak/keycloak/commit/dae4a3eaf26590b8d441b8e4bec3b700ee303b72', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27826', 'https://access.redhat.com/security/cve/cve-2020-27826'} | null | {'https://github.com/keycloak/keycloak/commit/dae4a3eaf26590b8d441b8e4bec3b700ee303b72'} | {'https://github.com/keycloak/keycloak/commit/dae4a3eaf26590b8d441b8e4bec3b700ee303b72'} |
GHSA | GHSA-xrr4-74mc-rpjc | Pyro mishandles pid files in temporary directory locations and opening the pid file as root | pyro before 3.15 unsafely handles pid files in temporary directory locations and opening the pid file as root. An attacker can use this flaw to overwrite arbitrary files via symlinks. | {'CVE-2011-2765'} | 2022-04-26T18:22:27Z | 2018-08-21T17:01:29Z | HIGH | 7.5 | {'CWE-59'} | {'https://bugs.debian.org/631912', 'https://github.com/advisories/GHSA-xrr4-74mc-rpjc', 'https://pythonhosted.org/Pyro/12-changes.html', 'https://github.com/irmen/Pyro3/commit/554e095a62c4412c91f981e72fd34a936ac2bf1e', 'https://nvd.nist.gov/vuln/detail/CVE-2011-2765'} | null | {'https://github.com/irmen/Pyro3/commit/554e095a62c4412c91f981e72fd34a936ac2bf1e'} | {'https://github.com/irmen/Pyro3/commit/554e095a62c4412c91f981e72fd34a936ac2bf1e'} |
GHSA | GHSA-8j72-p2wm-6738 | Persistent XSS vulnerability in filename of attached file in PrivateBin | On 24th of December 2019 one of the [property based unit tests](https://github.com/PrivateBin/PrivateBin/blob/master/tst/README.md#property-based-unit-testing) reported a [failure](https://travis-ci.org/PrivateBin/PrivateBin/jobs/629180605#L782). Upon investigation, [@elrido](https://github.com/elrido) discovered that the failure was due to unescaped HTML, which allowed the user provided attachment file name to inject HTML under certain conditions leading to a persistent [Cross-site scripting (XSS)](https://en.wikipedia.org/wiki/Cross-site_scripting) vulnerability. After committing an [initial fix](https://github.com/PrivateBin/PrivateBin/commit/8d0ac336d23cd8c98e71d5f21cdadcae9c8a26e6) to the master branch, the [issue was reported](https://github.com/PrivateBin/PrivateBin/issues/554) on 25th of December. Vulnerability write-up done by [@rugk](https://github.com/rugk) and [@elrido](https://github.com/elrido).
The vulnerability has been fixed in [PrivateBin v1.3.2 & v1.2.2](https://privatebin.info/news/v1.3.2-v1.2.2-release.html). Admins are urged to upgrade to these versions to protect the affected users.
## Affected versions
Any PrivateBin version since 1.2.
## Conditions
* The configuration setting `fileupload` has to be enabled, as 1.3 displays an error when trying to open a paste with attachment.
* The CSP header rules don't get applied. For example:
* They are unsupported or disabled in the visitors browser.
* They are filtered out by a some proxy server at the server or client side.
* The header is disabled/commented in the PHP-logic.
* The rules have been relaxed in the `cspheader` configuration setting.
* A paste with a malicious filename is created.
* A visitor of that paste clicks on the "Clone" button.
## Proof of concept
The following method is just one possibility to exploit this issue and is provided as a proof of concept with steps to reproduce the issue. To avoid having to create an actual file with a rogue filename, one could use the [Python CLI client for PrivateBin](https://github.com/r4sas/PBinCLI/) and [edit line 56 in `format.py`](https://github.com/r4sas/PBinCLI/blob/682b47fbd3e24a8a53c3b484ba896a5dbc85cda2/pbincli/format.py#L56) as follows:
```diff
- self._attachment_name = path_leaf(path)
+ self._attachment_name = '<script>alert("☹️");//<a'
```
The paste then can be created on a vulnerable instance:
```shell
$ python pbincli/cli.py send -t " " -f /dev/null -s https://privatebin.net/
```
Visiting the created paste on a vulnerable instance, with `fileupload` enabled and the CSP header weakened or disabled, and clicking the clone button will insert the HTML unescaped. In the above example, a pop-up would appear, when the script is executed.
## Impact
On a vulnerable site pastes with malicious filenames can be created and users visiting these could inadvertently trigger the code execution when they click the "Clone" button. They could be instigated to do so via social engineering, like a paste text suggesting to "clone and share" the paste in question.
The attached file itself doesn't have to be empty and could be an image or document that would still be displayed inline as usual. The execution of the script triggered by clicking on the "Clone" button may occur silently in the background without showing any noticeable signs in browser. It may for instance be used to track visitors, start drive-by-downloads or similar. While we focus on script injection here, as it is the easiest exploit vector, it has to be said that anything else can be injected like CSS, images, videos, although the default CSP will block inline CSS and images, e.g.
On first visit, the filename isn't visible and is properly escaped when inserted into the download attribute. Only when clicking the "Download attachment" link would open a file save dialog with an odd name pre-filled, although browsers will convert illegal characters into valid ones, so it may not be identical to the one provided. Only when the "Clone" button has been clicked and after the exploit has already been triggered, the filename gets displayed. Note that an attacker can of course prevent this indicator of compromise to be shown and e.g. change the displayed text or obfuscate the filename by starting it with something harmless, like `image.png`, before opening the HTML tag.
### Impact restrictions
The impact is mitigated by the fact that the vulnerability is, as far as our investigation concluded, paste-specific, i.e. opening a vulnerable paste can only compromise this one paste and no other pastes.
Furthermore, as stated before, the impact is mitigated by the fact that we deploy a strong [CSP](https://content-security-policy.com/) that, by default, does not allow inline JS or other potentially easy methods that would allow an easy exploitation of the vulnerability.
That said, we have to make users aware, that there may always be tricks to bypass such a CSP and the simple injection of HTML tags, e.g. destroying, faking or somehow phishing an HTML page does always remain a possibility.
As such, we treat this as a security vulnerability with medium severity. It is critical on it's own, but we believe that the deployed security mechanisms should prevent an exploit in practice in most cases.
## Real-life impact
We checked all instances listed in the [PrivateBin directory in the Wiki](https://github.com/PrivateBin/PrivateBin/wiki/PrivateBin-Directory) and didn't find any 1.1, 1.2 or 1.3 instances that had the CSP headers disabled or in a state we know to be vulnerable. We used the following script, that may be adapted to check the CSP headers of any single instance:
```shell
for URL in $(
curl -s https://raw.githubusercontent.com/wiki/PrivateBin/PrivateBin/PrivateBin-Directory.md | grep -Po '^http.*?(?= )'
)
do
echo -n "$URL: "
curl -sLI $URL | grep -Poi 'content-security-policy.*script-src.?\K.*?(?=;)' || echo 'No CSP detected!'
done
```
Some of the above sites do offer file uploads. On these instances, it is still possible that a visitor could have CSP support disabled in their browser, i.e. via a transparent proxy at their internet uplink or due to a browser plugin or some other locally installed, misguided security solution.
**Important:** This scan is only a cursory check and _must not_ be taken as a security analysis of any means! You are always responsible for the security of your own instance. Please do check it manually!
## Mitigation
As server administrators can't detect if a paste contains file attachments at all (apart from their size) in version 1.3 and due to the encrypted filename in older versions, as well as the risk for clients that don't apply the CSP settings, we urge them to upgrade to versions 1.3.2 or 1.2.2.
If you use v1.3, you could disable the `fileupload` setting to prevent pastes from getting displayed that may contain this vulnerability. Note that this will break all existing pastes with uploads, however, so we do _not_ recommend this, but advise you to upgrade to a fixed version instead.
## Further information
We want to make potential third-party client authors aware of this vulnerability and urge them to double-check their implementations. If they develop a client that displays untrusted foreign data from a paste in a HTML site, please make sure to escape it to prevent XSS attacks. Such attacks can only be prevented when the paste is displayed, a mitigation when a paste is created is pointless, as a different client can be used during creation.
We do also acknowledge and want to highlight the benefit of the CSP, which has first been [introduced in PrivateBin v1.0](https://github.com/PrivateBin/PrivateBin/issues/10).
However, we want to make you again aware that a whitelist-based CSP as we use, may [sometimes still be bypassed](https://csp.withgoogle.com/docs/faq.html#problems-with-whitelists), e.g. if you host a copy of the Angular library on the same domain as your PrivateBin instance.
We are aware of that and [do consider](https://github.com/PrivateBin/PrivateBin/issues/108) upgrading to a stronger CSP in the future.
### Issue discovery
While it is satisfying that our hard work on introducing unit tests has payed off in the discovery and mitigation of this vulnerability, it does also show a limitation of unit testing. A third party doing a code review would have certainly focused on how the project handles user provided input and may have discovered this much quicker.
The discovery wasn't due to the unit test checking for HTML input to get properly escaped, on the contrary, the test assumed input would not be changed. So other instances of HTML tags generated would have happily passed the test. Only when the test generated a fragment of a link (`<a`) it failed, because the DOM silently removed it when it inserted the string, as links within links aren't allowed. While the test was written to throw arbitrary strings at the `AttachmentViewer.moveAttachmentTo()` method, the test would only check that these got inserted into the DOM unchanged, oblivious of their potential significance when interpreted as HTML.
The [test had been introduced](https://github.com/PrivateBin/PrivateBin/commit/39860dfdc434c00d18342b4fb3bc6f5d0960030d) on December 3rd, 2017, 570 commits ago. Every commit on master and in PRs since introduction in that commit triggers these tests to run for every supported PHP version. Additional test cycles get run on developers local environments during working on commits. Hence the test suite must have run a few thousand times, testing 100 random strings each time. And only after more then 2 years a string containing `<a` got generated, triggered the error condition and 22 shrinks later the smallest failing test case was presented as:
```
Failed after 65 tests and 22 shrinks. rngState: 8b8f0d4ec2a67139b5; Counterexample: "image/png"; ""; "\u0000"; "<a"; "";
```
Discussion about a potential problem with that code, [did spark last September](https://github.com/PrivateBin/PrivateBin/pull/508#commitcomment-34943221), when the vulnerable code part was changed to the one before before the current fix, but was [incorrectly judged](https://github.com/PrivateBin/PrivateBin/pull/508#commitcomment-34944396) as not being a problem, because all of our translation strings are hardcoded. The fact that we do actually add some untrusted user-provided content, wasn't considered at that point.
It should also be mentioned, that the coverage report released for version 1.3.1 did highlight the line that caused this vulnerability as not being covered during testing:
So, in conclusion, it is great to have all of these tools at our disposal, but the code quality would benefit a lot more from having more eyeballs and brains on it.
## Timeline
* 2019-12-24 – Property based unit test fails in a commit pushed to a PR.
* 2019-12-25 – Issue investigated, preliminary patch and issue description published.
* 2019-12-30 – Further investigations, proof-of-concept exploit demonstrated on a vulnerable test instance.
* 2020-01-03 – Discussed broader mitigation of user provided content injections, reviewed other possible cases.
* 2020-01-04 – Published a second patch based on review, escapes HTML in translation.
* 2020-01-05 – Started writing vulnerability report.
* 2020-01-07 – Backported fix for 1.2.1.
* 2020-01-11 – [Release published](https://github.com/PrivateBin/PrivateBin/releases/tag/1.3.2).
* 2020-01-11 – Vulnerability details published. | {'CVE-2020-5223'} | 2021-01-14T17:43:41Z | 2020-01-14T20:19:33Z | MODERATE | 6.1 | {'CWE-79'} | {'https://privatebin.info/news/v1.3.2-v1.2.2-release.html', 'https://github.com/PrivateBin/PrivateBin/security/advisories/GHSA-8j72-p2wm-6738', 'https://github.com/PrivateBin/PrivateBin/commit/8d0ac336d23cd8c98e71d5f21cdadcae9c8a26e6', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5223', 'https://github.com/advisories/GHSA-8j72-p2wm-6738', 'https://github.com/PrivateBin/PrivateBin/issues/554'} | null | {'https://github.com/PrivateBin/PrivateBin/commit/8d0ac336d23cd8c98e71d5f21cdadcae9c8a26e6'} | {'https://github.com/PrivateBin/PrivateBin/commit/8d0ac336d23cd8c98e71d5f21cdadcae9c8a26e6'} |
GHSA | GHSA-xm9f-vxmx-4m58 | Data Flow Sanitation Issue Fix | ### Impact
Due to missing sanitation in data flow it was possible for admin users to upload arbitrary executable files to the server. | {'CVE-2021-32759'} | 2021-08-30T17:20:41Z | 2021-08-30T17:20:41Z | HIGH | 0 | {'CWE-20'} | {'https://github.com/OpenMage/magento-lts/security/advisories/GHSA-xm9f-vxmx-4m58', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32759', 'https://github.com/OpenMage/magento-lts/releases/tag/v20.0.13', 'https://github.com/OpenMage/magento-lts/releases/tag/v19.4.15', 'https://github.com/advisories/GHSA-xm9f-vxmx-4m58', 'https://github.com/OpenMage/magento-lts/commit/34709ac642d554aa1824892059186dd329db744b'} | null | {'https://github.com/OpenMage/magento-lts/commit/34709ac642d554aa1824892059186dd329db744b'} | {'https://github.com/OpenMage/magento-lts/commit/34709ac642d554aa1824892059186dd329db744b'} |
GHSA | GHSA-cvp7-c586-cmf4 | Withdrawn: Code Injection in loguru | # Withdrawn
This advisory has been withdrawn after the maintainers of loguru noted this issue is not a security vulnerability and the CVE has been revoked. We have [stopped](https://github.com/Delgan/loguru/issues/563#issuecomment-1025223732) Dependabot alerts regarding this issue.
## Original Description
In versions of loguru up to and including 0.5.3 a lack of sanitization on log serialization can lead to arbitrary code execution. The maintainer disputes the issue, but has altered behavior of the library in commit 4b0070a4f30cbf6d5e12e6274b242b62ea11c81b. See https://github.com/Delgan/loguru/issues/563 for further discussion of the issue. The function in question is intended for internal use only, but is not restricted. This has been patched in version 0.6.0. | {'CVE-2022-0329'} | 2022-02-01T16:00:39Z | 2022-01-28T22:01:45Z | LOW | 0 | {'CWE-94'} | {'https://github.com/delgan/loguru/commit/4b0070a4f30cbf6d5e12e6274b242b62ea11c81b', 'https://huntr.dev/bounties/1-pypi-loguru', 'https://tomforb.es/cve-2022-0329-and-the-problems-with-automated-vulnerability-management/', 'https://github.com/Delgan/loguru/issues/563', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0329', 'https://github.com/advisories/GHSA-cvp7-c586-cmf4'} | null | {'https://github.com/delgan/loguru/commit/4b0070a4f30cbf6d5e12e6274b242b62ea11c81b'} | {'https://github.com/delgan/loguru/commit/4b0070a4f30cbf6d5e12e6274b242b62ea11c81b'} |
GHSA | GHSA-vwfx-hh3w-fj99 | Potential XSS injection in the newsletter conditions field | ### Impact
An employee can inject javascript in the newsletter condition field that will then be executed on the front office
### Patches
The issue has been fixed in 2.6.1 | {'CVE-2021-21418'} | 2021-04-06T17:24:14Z | 2021-04-06T17:24:14Z | MODERATE | 4.6 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21418', 'https://github.com/PrestaShop/ps_emailsubscription/security/advisories/GHSA-vwfx-hh3w-fj99', 'https://github.com/advisories/GHSA-vwfx-hh3w-fj99', 'https://github.com/PrestaShop/ps_emailsubscription/releases/tag/v2.6.1', 'https://github.com/PrestaShop/ps_emailsubscription/commit/664ffb225e2afb4a32640bbedad667dc6e660b70', 'https://packagist.org/packages/prestashop/ps_emailsubscription'} | null | {'https://github.com/PrestaShop/ps_emailsubscription/commit/664ffb225e2afb4a32640bbedad667dc6e660b70'} | {'https://github.com/PrestaShop/ps_emailsubscription/commit/664ffb225e2afb4a32640bbedad667dc6e660b70'} |
GHSA | GHSA-r9ch-m4fh-fc7q | Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 | In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack. Where timings can be closely observed for the generation of signatures, the lack of blinding in 1.55, or earlier, may allow an attacker to gain information about the signature's k value and ultimately the private value as well. | {'CVE-2016-1000341'} | 2021-09-17T14:46:46Z | 2018-10-17T16:24:00Z | MODERATE | 5.9 | null | {'https://github.com/advisories/GHSA-r9ch-m4fh-fc7q', 'https://security.netapp.com/advisory/ntap-20181127-0004/', 'https://access.redhat.com/errata/RHSA-2018:2927', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/bcgit/bc-java/commit/acaac81f96fec91ab45bd0412beaf9c3acd8defa#diff-e75226a9ca49217a7276b29242ec59ce', 'https://access.redhat.com/errata/RHSA-2018:2669', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000341', 'https://usn.ubuntu.com/3727-1/', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html'} | null | {'https://github.com/bcgit/bc-java/commit/acaac81f96fec91ab45bd0412beaf9c3acd8defa#diff-e75226a9ca49217a7276b29242ec59ce'} | {'https://github.com/bcgit/bc-java/commit/acaac81f96fec91ab45bd0412beaf9c3acd8defa#diff-e75226a9ca49217a7276b29242ec59ce'} |
GHSA | GHSA-3v6h-hqm4-2rg6 | Arbitrary File Write in adm-zip | Versions of `adm-zip` before 0.4.9 are vulnerable to arbitrary file write when used to extract a specifically crafted archive that contains path traversal filenames (`../../file.txt` for example).
## Recommendation
Update to version 0.4.9 or later. | {'CVE-2018-1002204'} | 2021-01-08T19:58:40Z | 2018-07-27T17:07:14Z | HIGH | 0 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1002204', 'https://www.npmjs.com/advisories/681', 'https://github.com/advisories/GHSA-3v6h-hqm4-2rg6', 'https://www.npmjs.com/advisories/994', 'https://github.com/cthackers/adm-zip/pull/212', 'https://github.com/snyk/zip-slip-vulnerability', 'http://www.securityfocus.com/bid/107001', 'https://github.com/cthackers/adm-zip/commit/62f64004fefb894c523a7143e8a88ebe6c84df25', 'https://snyk.io/research/zip-slip-vulnerability', 'https://hackerone.com/reports/362118', 'https://snyk.io/vuln/npm:adm-zip:20180415'} | null | {'https://github.com/cthackers/adm-zip/commit/62f64004fefb894c523a7143e8a88ebe6c84df25'} | {'https://github.com/cthackers/adm-zip/commit/62f64004fefb894c523a7143e8a88ebe6c84df25'} |
GHSA | GHSA-f62v-xpxf-3v68 | Code injection in Apache Ant | As mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so that only the current user was allowed to access them. Unfortunately the fixcrlf task deleted the temporary file and created a new one without said protection, effectively nullifying the effort. This would still allow an attacker to inject modified source files into the build process. | {'CVE-2020-11979'} | 2022-04-22T17:18:45Z | 2021-02-03T19:16:35Z | HIGH | 7.5 | {'CWE-94', 'CWE-74'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DYBRN5C2RW7JRY75IB7Q7ZVKZCHWAQWS/', 'https://lists.apache.org/thread.html/raaeddc41da8f3afb1cb224876084a45f68e437a0afd9889a707e4b0c@%3Cdev.creadur.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U3NRQQ7ECII4ZNGW7GBC225LVYMPQEKB/', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.apache.org/thread.html/rc3c8ef9724b5b1e171529b47f4b35cb7920edfb6e917fa21eb6c64ea%40%3Cdev.ant.apache.org%3E', 'https://lists.apache.org/thread.html/r4ca33fad3fb39d130cda287d5a60727d9e706e6f2cf2339b95729490@%3Cdev.creadur.apache.org%3E', 'https://lists.apache.org/thread.html/r5e1cdd79f019162f76414708b2092acad0a6703d666d72d717319305@%3Cdev.creadur.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AALW42FWNQ35F7KB3JVRC6NBVV7AAYYI/', 'https://lists.apache.org/thread.html/r2306b67f20c24942b872b0a41fbdc9330e8467388158bcd19c1094e0@%3Cdev.creadur.apache.org%3E', 'https://lists.apache.org/thread.html/r1dc8518dc99c42ecca5ff82d0d2de64cd5d3a4fa691eb9ee0304781e@%3Cdev.creadur.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/apache/ant/commit/87ac51d3c22bcf7cfd0dc07cb0bd04a496e0d428', 'https://github.com/gradle/gradle/security/advisories/GHSA-j45w-qrgf-25vm', 'https://github.com/advisories/GHSA-f62v-xpxf-3v68', 'https://lists.apache.org/thread.html/rbfe9ba28b74f39f46ec1bbbac3bef313f35017cf3aac13841a84483a@%3Cdev.creadur.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11979', 'https://lists.apache.org/thread.html/r107ea1b1a7a214bc72fe1a04207546ccef542146ae22952e1013b5cc@%3Cdev.creadur.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://security.gentoo.org/glsa/202011-18', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/apache/ant/commit/87ac51d3c22bcf7cfd0dc07cb0bd04a496e0d428'} | {'https://github.com/apache/ant/commit/87ac51d3c22bcf7cfd0dc07cb0bd04a496e0d428'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.