Datasets:
TQRG
/

Modalities:
Text
Formats:
parquet
ArXiv:
Libraries:
Datasets
pandas
Dataset Viewer
Auto-converted to Parquet
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-p6j9-7xhc-rhwp
Hostname spoofing via backslashes in URL
### Impact If using affected versions to determine a URL's hostname, the hostname can be spoofed by using a backslash (`\`) character as part of the scheme delimiter, e.g. `scheme:/\hostname`. If the hostname is used in security decisions, the decision may be incorrect. Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior. Example URL: `https:/\expected-example.com/path` Escaped string: `https:/\\expected-example.com/path` (JavaScript strings must escape backslash) Affected versions incorrectly return no hostname. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html). ### Patches Version 1.19.6 is patched against all known payload variants. ### References https://github.com/medialize/URI.js/releases/tag/v1.19.6 (fix for this particular bypass) https://github.com/medialize/URI.js/releases/tag/v1.19.4 (fix for related bypass) https://github.com/medialize/URI.js/releases/tag/v1.19.3 (fix for related bypass) [PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling) ### For more information If you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js ### Reporter credit [Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec team at Checkmarx
{'CVE-2021-27516'}
2022-04-19T19:02:48Z
2021-03-01T20:03:53Z
MODERATE
0
{'CWE-20'}
{'https://github.com/medialize/URI.js/commit/a1ad8bcbc39a4d136d7e252e76e957f3ece70839', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27516', 'https://advisory.checkmarx.net/advisory/CX-2021-4305', 'https://github.com/medialize/URI.js/security/advisories/GHSA-p6j9-7xhc-rhwp', 'https://github.com/medialize/URI.js/releases/tag/v1.19.6', 'https://github.com/advisories/GHSA-p6j9-7xhc-rhwp'}
null
{'https://github.com/medialize/URI.js/commit/a1ad8bcbc39a4d136d7e252e76e957f3ece70839'}
{'https://github.com/medialize/URI.js/commit/a1ad8bcbc39a4d136d7e252e76e957f3ece70839'}
GHSA
GHSA-mq5c-prh3-3f3h
Invalid validation in `QuantizeAndDequantizeV2`
### Impact The validation in `tf.raw_ops.QuantizeAndDequantizeV2` allows invalid values for `axis` argument: ```python import tensorflow as tf input_tensor = tf.constant([0.0], shape=[1], dtype=float) input_min = tf.constant(-10.0) input_max = tf.constant(-10.0) tf.raw_ops.QuantizeAndDequantizeV2( input=input_tensor, input_min=input_min, input_max=input_max, signed_input=False, num_bits=1, range_given=False, round_mode='HALF_TO_EVEN', narrow_range=False, axis=-2) ``` The [validation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses `||` to mix two different conditions: ```cc OP_REQUIRES(ctx, (axis_ == -1 || axis_ < input.shape().dims()), errors::InvalidArgument(...)); ``` If `axis_ < -1` the condition in `OP_REQUIRES` will still be true, but this value of `axis_` results in heap underflow. This allows attackers to read/write to other data on the heap. ### Patches We have patched the issue in GitHub commit [c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9](https://github.com/tensorflow/tensorflow/commit/c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9). 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-29610'}
2021-05-21T14:28:32Z
2021-05-21T14:28:32Z
LOW
3.6
{'CWE-665'}
{'https://github.com/tensorflow/tensorflow/commit/c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29610', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mq5c-prh3-3f3h', 'https://github.com/advisories/GHSA-mq5c-prh3-3f3h'}
null
{'https://github.com/tensorflow/tensorflow/commit/c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9'}
{'https://github.com/tensorflow/tensorflow/commit/c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9'}
GHSA
GHSA-9v62-24cr-58cx
Denial of Service in node-sass
Affected versions of `node-sass` are vulnerable to Denial of Service (DoS). Crafted objects passed to the `renderSync` function may trigger C++ assertions in `CustomImporterBridge::get_importer_entry` and `CustomImporterBridge::post_process_return_value` that crash the Node process. This may allow attackers to crash the system's running Node process and lead to Denial of Service. ## Recommendation Upgrade to version 4.13.1 or later
null
2021-09-28T16:08:18Z
2020-09-11T21:12:39Z
MODERATE
5.9
{'CWE-400'}
{'https://www.npmjs.com/advisories/961', 'https://github.com/sass/node-sass/commit/338fd7a14d3b8bd374a382336df16f9c6792b884', 'https://github.com/advisories/GHSA-9v62-24cr-58cx'}
null
{'https://github.com/sass/node-sass/commit/338fd7a14d3b8bd374a382336df16f9c6792b884'}
{'https://github.com/sass/node-sass/commit/338fd7a14d3b8bd374a382336df16f9c6792b884'}
GHSA
GHSA-h6wf-hvwc-fm77
Out-of-bounds write
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.
{'CVE-2019-0914'}
2021-03-29T21:00:02Z
2021-03-29T21:00:02Z
HIGH
7.5
{'CWE-787'}
{'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0914', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0914', 'https://github.com/advisories/GHSA-h6wf-hvwc-fm77', 'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f'}
null
{'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7'}
{'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f'}
GHSA
GHSA-9m95-8hx6-7p9v
Improper input validation in umoci
### Impact umoci 0.4.6 and earlier can be tricked into modifying host files by creating a malicious layer that has a symlink with the name "." (or "/"). Because umoci deletes inodes if they change types, this results in the rootfs directory being replaced with an attacker-controlled symlink. Subsequent image layers will then be applied on top of the target of the symlink (which could be any directory on the host filesystem the user running umoci has access to). While umoci does have defences against symlink-based attacks, they are all implemented by resolving things relative to the rootfs directory -- if the rootfs itself is a symlink, umoci resolves it first. This vulnerability affects both "umoci unpack" and "umoci raw unpack". ### Patches This issue has been patched in umoci 0.4.7, see the references section for the specific commit which fixed this vulnerability. ### Workarounds Note that if you use umoci as an unprivileged user (using the --rootless flag) then umoci will not be able to overwrite any files that your user doesn't have access to. Other possible mitigations are to run umoci under an LSM profile such as AppArmor or SELinux to restrict the level of access it has outside of container image directories. ### References * [oss-security public disclosure](https://www.openwall.com/lists/oss-security/2021/04/06/2) * [patch](https://github.com/opencontainers/umoci/commit/d9efc31daf2206f7d3fdb839863cf7a576a2eb57) ### Credits Thanks to Robin Peraglie from Cure53 for discovering and reporting this vulnerability. ### For more information If you have any questions or comments about this advisory * Open an issue in <https://github.com/opencontainers/umoci>. * Email us at <security@opencontainers.org>.
{'CVE-2021-29136'}
2022-03-15T21:39:43Z
2022-02-15T01:17:37Z
MODERATE
5.5
{'CWE-20'}
{'https://github.com/advisories/GHSA-9m95-8hx6-7p9v', 'https://github.com/opencontainers/umoci/security/advisories/GHSA-9m95-8hx6-7p9v', 'http://www.openwall.com/lists/oss-security/2021/04/06/2', 'https://github.com/opencontainers/umoci/commit/d9efc31daf2206f7d3fdb839863cf7a576a2eb57', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29136'}
null
{'https://github.com/opencontainers/umoci/commit/d9efc31daf2206f7d3fdb839863cf7a576a2eb57'}
{'https://github.com/opencontainers/umoci/commit/d9efc31daf2206f7d3fdb839863cf7a576a2eb57'}
GHSA
GHSA-5c8j-xr24-2665
Potential Command Injection in printer
Versions 0.0.1 and earlier of `printer` are affected by a command injection vulnerability resulting from a failure to sanitize command arguments properly in the `printDirect()` function. ## Recommendation Update to version 0.0.2 or later.
{'CVE-2014-3741'}
2021-09-01T21:34:21Z
2017-11-28T22:44:52Z
CRITICAL
9.8
{'CWE-77'}
{'http://www.openwall.com/lists/oss-security/2014/05/13/1', 'https://nvd.nist.gov/vuln/detail/CVE-2014-3741', 'https://www.npmjs.com/advisories/27', 'https://github.com/advisories/GHSA-5c8j-xr24-2665', 'http://www.openwall.com/lists/oss-security/2014/05/15/2', 'https://github.com/tojocky/node-printer/commit/e001e38738c17219a1d9dd8c31f7d82b9c0013c7', 'https://nodesecurity.io/advisories/printer_potential_command_injection'}
null
{'https://github.com/tojocky/node-printer/commit/e001e38738c17219a1d9dd8c31f7d82b9c0013c7'}
{'https://github.com/tojocky/node-printer/commit/e001e38738c17219a1d9dd8c31f7d82b9c0013c7'}
GHSA
GHSA-qg48-85hg-mqc5
Division by 0 in `DenseCountSparseOutput`
### Impact An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.DenseCountSparseOutput`: ```python import tensorflow as tf values = tf.constant([], shape=[0, 0], dtype=tf.int64) weights = tf.constant([]) tf.raw_ops.DenseCountSparseOutput( values=values, weights=weights, minlength=-1, maxlength=58, binary_output=True) ``` This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/efff014f3b2d8ef6141da30c806faf141297eca1/tensorflow/core/kernels/count_ops.cc#L123-L127) computes a divisor value from user data but does not check that the result is 0 before doing the division: ```cc int num_batch_elements = 1; for (int i = 0; i < num_batch_dimensions; ++i) { num_batch_elements *= data.shape().dim_size(i); } int num_value_elements = data.shape().num_elements() / num_batch_elements; ``` Since `data` is given by the `values` argument, `num_batch_elements` is 0. ### Patches We have patched the issue in GitHub commit [da5ff2daf618591f64b2b62d9d9803951b945e9f](https://github.com/tensorflow/tensorflow/commit/da5ff2daf618591f64b2b62d9d9803951b945e9f). The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, and TensorFlow 2.3.3, as these are also affected. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.
{'CVE-2021-29554'}
2021-05-21T14:23:55Z
2021-05-21T14:23:55Z
LOW
2.5
{'CWE-369'}
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qg48-85hg-mqc5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29554', 'https://github.com/advisories/GHSA-qg48-85hg-mqc5', 'https://github.com/tensorflow/tensorflow/commit/da5ff2daf618591f64b2b62d9d9803951b945e9f'}
null
{'https://github.com/tensorflow/tensorflow/commit/da5ff2daf618591f64b2b62d9d9803951b945e9f'}
{'https://github.com/tensorflow/tensorflow/commit/da5ff2daf618591f64b2b62d9d9803951b945e9f'}
GHSA
GHSA-5xf4-f2fq-f69j
Improper link resolution before file access (Link Following)
In Yarn before 1.21.1, the package install functionality can be abused to generate arbitrary symlinks on the host filesystem by using specially crafted "bin" keys. Existing files could be overwritten depending on the current user permission set.
{'CVE-2019-10773'}
2021-08-19T17:16:28Z
2020-02-14T23:10:16Z
HIGH
7.8
{'CWE-78'}
{'https://github.com/advisories/GHSA-5xf4-f2fq-f69j', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ITY5BC63CCC647DFNUQRQ5AJDKUKUNBI/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10773', 'https://blog.daniel-ruf.de/critical-design-flaw-npm-pnpm-yarn/', 'https://snyk.io/vuln/SNYK-JS-YARN-537806,', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3HIZW4NZVV5QY5WWGW2JRP3FHYKZ6ZJ5/', 'https://github.com/yarnpkg/yarn/commit/039bafd74b7b1a88a53a54f8fa6fa872615e90e7', 'https://github.com/yarnpkg/yarn/issues/7761#issuecomment-565493023', 'https://access.redhat.com/errata/RHSA-2020:0475', 'https://github.com/yarnpkg/yarn/pull/7755'}
null
{'https://github.com/yarnpkg/yarn/commit/039bafd74b7b1a88a53a54f8fa6fa872615e90e7'}
{'https://github.com/yarnpkg/yarn/commit/039bafd74b7b1a88a53a54f8fa6fa872615e90e7'}
GHSA
GHSA-2ccx-2gf3-8xvv
.dev domains and some reverse proxy setups were treated as local in Kirby
### Impact #### About our registration block In order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server. In this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk. To be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site. #### The issue As noted by [Jukka Rautanen](https://github.com/jukra), this installation block implementation in Kirby versions before 3.3.6 still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our installation block is no longer working as expected if you use a .dev domain for your Kirby site. In fixing this issue, we've also found out that the local installation check may also fail if your site is behind a reverse proxy. #### Am I affected? You are only affected if: 1. you use a .dev domain or your site is behind a reverse proxy & 2. you have not yet registered your first Panel account on the public server & 3. someone finds your site and tries to login at `yourdomain.dev/panel` before you register your first account. You are not affected if you have already created one or multiple Panel accounts (no matter if on a .dev domain or behind a reverse proxy). ### Patches The problem has been patched in [Kirby 2.5.14](https://github.com/getkirby-v2/panel/releases/tag/2.5.14) and [Kirby 3.3.6](https://github.com/getkirby/kirby/releases/tag/3.3.6). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerability. **Note:** Kirby 2 reaches end of life on December 31, 2020. We therefore recommend to upgrade your Kirby 2 sites to Kirby 3. If you cannot upgrade, we still recommend to update to Kirby 2.5.14. ### Workarounds Kirby 2 sites on older releases can also be patched by applying the [changes from this commit](https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa).
{'CVE-2020-26253'}
2022-04-19T19:02:41Z
2021-01-14T19:15:19Z
MODERATE
6.8
{'CWE-346'}
{'https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa', 'https://github.com/getkirby/kirby/security/advisories/GHSA-2ccx-2gf3-8xvv', 'https://packagist.org/packages/getkirby/panel', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26253', 'https://packagist.org/packages/getkirby/cms', 'https://github.com/getkirby/kirby/releases/tag/3.3.6', 'https://github.com/advisories/GHSA-2ccx-2gf3-8xvv'}
null
{'https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa'}
{'https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa'}
GHSA
GHSA-3rcw-9p9x-582v
Code injection in `saved_model_cli`
### Impact TensorFlow's `saved_model_cli` tool is vulnerable to a code injection as it [calls `eval` on user supplied strings](https://github.com/tensorflow/tensorflow/blob/87462bfac761435a46641ff2f10ad0b6e5414a4b/tensorflow/python/tools/saved_model_cli.py#L524-L550) ```python def preprocess_input_exprs_arg_string(input_exprs_str): ... for input_raw in filter(bool, input_exprs_str.split(';')): ... input_key, expr = input_raw.split('=', 1) input_dict[input_key] = eval(expr) ... ``` This can be used by attackers to run arbitrary code on the plaform where the CLI tool runs. However, given that the tool is always run manually, the impact of this is not severe. We have patched this by adding a `safe` flag which defaults to `True` and an explicit warning for users. ### Patches We have patched the issue in GitHub commit [8b202f08d52e8206af2bdb2112a62fafbc546ec7](https://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7). The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Omer Kaspi from Vdoo.
{'CVE-2021-41228'}
2021-11-10T16:54:02Z
2021-11-10T16:54:02Z
HIGH
7.5
{'CWE-94', 'CWE-78'}
{'https://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41228', 'https://github.com/advisories/GHSA-3rcw-9p9x-582v', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3rcw-9p9x-582v'}
null
{'https://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7'}
{'https://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7'}
GHSA
GHSA-g78m-2chm-r7qv
Regular Expression Denial of Service in websocket-extensions (NPM package)
### Impact The ReDoS flaw allows an attacker to exhaust the server's capacity to process incoming requests by sending a WebSocket handshake request containing a header of the following form: Sec-WebSocket-Extensions: a; b="\c\c\c\c\c\c\c\c\c\c ... That is, a header containing an unclosed string parameter value whose content is a repeating two-byte sequence of a backslash and some other character. The parser takes exponential time to reject this header as invalid, and this will block the processing of any other work on the same thread. Thus if you are running a single-threaded server, such a request can render your service completely unavailable. ### Patches Users should upgrade to version 0.1.4. ### Workarounds There are no known work-arounds other than disabling any public-facing WebSocket functionality you are operating. ### References - https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions/
{'CVE-2020-7662'}
2021-08-25T21:51:06Z
2020-06-05T16:16:12Z
HIGH
8.2
{'CWE-400'}
{'https://nvd.nist.gov/vuln/detail/CVE-2020-7662', 'https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions', 'https://github.com/faye/websocket-extensions-node/commit/29496f6838bfadfe5a2f85dff33ed0ba33873237', 'https://github.com/advisories/GHSA-g78m-2chm-r7qv', 'https://github.com/faye/websocket-extensions-node/security/advisories/GHSA-g78m-2chm-r7qv', 'https://snyk.io/vuln/SNYK-JS-WEBSOCKETEXTENSIONS-570623'}
null
{'https://github.com/faye/websocket-extensions-node/commit/29496f6838bfadfe5a2f85dff33ed0ba33873237'}
{'https://github.com/faye/websocket-extensions-node/commit/29496f6838bfadfe5a2f85dff33ed0ba33873237'}
GHSA
GHSA-xw22-wv29-3299
ApiKey secret could be revelated on network issue
### Impact _What kind of vulnerability is it? Who is impacted?_ Applications that are using node-etsy-client and reporting client error to the end user will offer api key value too ### Patches _Has the problem been patched? What versions should users upgrade to?_ creharmony/node-etsy-client#18 fixes this issue. This is fixed in [node-etsy-client v0.3.0](https://github.com/creharmony/node-etsy-client/tree/v0.3.0) and later. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Do not report or log etsy client error if you are using version <= v0.2.0 Update your version of node-etsy-client ### References _Are there any links users can visit to find out more?_ - https://github.com/creharmony/node-etsy-client/issues/17 : On connect error secret appears in error #17 ### For more information If you have any questions or comments about this advisory: * Open an issue in [github.com/creharmony/node-etsy-client/issues](https://github.com/creharmony/node-etsy-client/issues/)
{'CVE-2021-21421'}
2022-04-19T19:02:52Z
2021-04-06T17:29:52Z
HIGH
8.1
{'CWE-200'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-21421', 'https://github.com/creharmony/node-etsy-client/commit/b4beb8ef080366c1a87dbf9e163051a446acaa7d', 'https://github.com/advisories/GHSA-xw22-wv29-3299', 'https://github.com/creharmony/node-etsy-client/security/advisories/GHSA-xw22-wv29-3299'}
null
{'https://github.com/creharmony/node-etsy-client/commit/b4beb8ef080366c1a87dbf9e163051a446acaa7d'}
{'https://github.com/creharmony/node-etsy-client/commit/b4beb8ef080366c1a87dbf9e163051a446acaa7d'}
GHSA
GHSA-46f2-3v63-3xrp
Path traversal in Tempfile on Windows
There is an unintentional directory creation vulnerability in `tmpdir` library bundled with Ruby on Windows. And there is also an unintentional file creation vulnerability in tempfile library bundled with Ruby on Windows, because it uses tmpdir internally.
{'CVE-2021-28966'}
2021-09-03T20:36:32Z
2021-05-06T15:01:36Z
MODERATE
7.5
{'CWE-22'}
{'https://hackerone.com/reports/1131465', 'https://security.netapp.com/advisory/ntap-20210902-0004/', 'https://github.com/advisories/GHSA-46f2-3v63-3xrp', 'https://www.ruby-lang.org/en/news/2021/04/05/tempfile-path-traversal-on-windows-cve-2021-28966/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28966', 'https://rubygems.org/gems/tmpdir', 'https://github.com/ruby/tmpdir/pull/8', 'https://github.com/ruby/tmpdir/commit/93798c01cb7c10476e50a4d80130a329ba47f348', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/tmpdir/CVE-2021-28966.yml'}
null
{'https://github.com/ruby/tmpdir/commit/93798c01cb7c10476e50a4d80130a329ba47f348'}
{'https://github.com/ruby/tmpdir/commit/93798c01cb7c10476e50a4d80130a329ba47f348'}
GHSA
GHSA-vvmr-8829-6whx
CSRF token missing in Symfony
Description ----------- The Symfony form component provides a CSRF protection mechanism by using a random token injected in the form and using the session to store and control the token submitted by the user. When using the FrameworkBundle, this protection can be enabled or disabled with the configuration. If the configuration is not specified, by default, the mechanism is enabled as long as the session is enabled. In a recent change in the way the configuration is loaded, the default behavior has been dropped and, as a result, the CSRF protection is not enabled in form when not explicitly enabled, which makes the application sensible to CSRF attacks. Resolution ---------- Symfony restored the default configuration to enable the CSRF protection by default. The patch for this issue is available [here](https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50) for branch 5.3. Credits ------- We would like to thank Catalin Dan and David Lochner for reporting the issue and Jérémy Derussé for fixing the issue.
{'CVE-2022-23601'}
2022-04-19T19:03:21Z
2022-02-01T00:46:57Z
HIGH
8.1
{'CWE-352'}
{'https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50', 'https://github.com/advisories/GHSA-vvmr-8829-6whx', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23601', 'https://github.com/symfony/symfony/security/advisories/GHSA-vvmr-8829-6whx'}
null
{'https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50'}
{'https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50'}
GHSA
GHSA-5fw9-fq32-wv5p
OS Command Injection in node-notifier
This affects the package node-notifier before 8.0.1. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.
{'CVE-2020-7789'}
2021-01-07T22:35:02Z
2020-12-21T16:04:07Z
MODERATE
5.6
{'CWE-78'}
{'https://github.com/mikaelbr/node-notifier/commit/5d62799dab88505a709cd032653b2320c5813fce', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1050371', 'https://github.com/advisories/GHSA-5fw9-fq32-wv5p', 'https://github.com/mikaelbr/node-notifier/blob/master/lib/utils.js%23L303', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7789', 'https://snyk.io/vuln/SNYK-JS-NODENOTIFIER-1035794'}
null
{'https://github.com/mikaelbr/node-notifier/commit/5d62799dab88505a709cd032653b2320c5813fce'}
{'https://github.com/mikaelbr/node-notifier/commit/5d62799dab88505a709cd032653b2320c5813fce'}
GHSA
GHSA-cf2j-vf36-c6w8
Communities and collections administrators can escalate their privilege up to system administrator
### Impact Any community or collection administrator can escalate their permission up to become system administrator. This vulnerability only existed in 7.0 and does not impact 6.x or below. ### Patches Fix is included in [7.1](https://github.com/DSpace/DSpace/releases/tag/dspace-7.1). Please upgrade to 7.1 at your earliest convenience. ### Workarounds In 7.0, temporarily disable the ability for community or collection administrators to manage permissions or workflows settings, i.e. set the following properties in your local.cfg / dspace.cfg file ``` core.authorization.collection-admin.policies = false core.authorization.community-admin.policies = false core.authorization.community-admin.collection.workflows = false ``` Once upgraded to 7.1, these settings can be safely reverted to the default values of `true`. ### References Discovered during investigation of https://github.com/DSpace/DSpace/issues/7928 ### For more information If you have any questions or comments about this advisory: * Email us at security@dspace.org
{'CVE-2021-41189'}
2022-04-19T19:03:13Z
2021-11-01T19:18:16Z
HIGH
7.2
{'CWE-863'}
{'https://github.com/advisories/GHSA-cf2j-vf36-c6w8', 'https://github.com/DSpace/DSpace/commit/277b499a5cd3a4f5eb2370513a1b7e4ec2a6e041', 'https://github.com/DSpace/DSpace/commit/c3bea16ab911606e15ae96c97a1575e1ffb14f8a', 'https://github.com/DSpace/DSpace/security/advisories/GHSA-cf2j-vf36-c6w8', 'https://github.com/DSpace/DSpace/issues/7928', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41189'}
null
{'https://github.com/DSpace/DSpace/commit/c3bea16ab911606e15ae96c97a1575e1ffb14f8a', 'https://github.com/DSpace/DSpace/commit/277b499a5cd3a4f5eb2370513a1b7e4ec2a6e041'}
{'https://github.com/DSpace/DSpace/commit/c3bea16ab911606e15ae96c97a1575e1ffb14f8a', 'https://github.com/DSpace/DSpace/commit/277b499a5cd3a4f5eb2370513a1b7e4ec2a6e041'}
GHSA
GHSA-gwp4-hfv6-p7hw
Deserialization of untrusted data in FasterXML jackson-databind
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9.2. This occurs when Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the logback jar in the classpath.
{'CVE-2019-14439'}
2021-04-12T22:02:24Z
2019-08-01T19:18:06Z
HIGH
7.5
{'CWE-502'}
{'https://lists.apache.org/thread.html/ee0a051428d2c719acfa297d0854a189ea5e284ef3ed491fa672f4be@%3Cdev.tomee.apache.org%3E', 'https://www.debian.org/security/2019/dsa-4542', 'https://lists.apache.org/thread.html/940b4c3fef002461b89a050935337056d4a036a65ef68e0bbd4621ef@%3Cdev.struts.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:3200', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://security.netapp.com/advisory/ntap-20190814-0001/', 'https://lists.debian.org/debian-lts-announce/2019/08/msg00011.html', 'https://lists.apache.org/thread.html/2d2a76440becb610b9a9cb49b15eac3934b02c2dbcaacde1000353e4@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/34717424b4d08b74f65c09a083d6dd1cb0763f37a15d6de135998c1d@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/5fc0e16b7af2590bf1e97c76c136291c4fdb244ee63c65c485c9a7a1@%3Cdev.tomee.apache.org%3E', 'https://github.com/advisories/GHSA-gwp4-hfv6-p7hw', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E', 'https://seclists.org/bugtraq/2019/Oct/6', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.apache.org/thread.html/5ecc333113b139429f4f05000d4aa2886974d4df3269c1dd990bb319@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/56c8042873595b8c863054c7bfccab4bf2c01c6f5abedae249d914b9@%3Cdev.tomee.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OVRZDN2T6AZ6DJCZJ3VSIQIVHBVMVWBL/', 'https://github.com/FasterXML/jackson-databind/compare/jackson-databind-2.9.9.1...jackson-databind-2.9.9.2', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14439', 'https://lists.apache.org/thread.html/87e46591de8925f719664a845572d184027258c5a7af0a471b53c77b@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/commit/ad418eeb974e357f2797aef64aa0e3ffaaa6125b', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://lists.apache.org/thread.html/0d4b630d9ee724aee50703397d9d1afa2b2befc9395ba7797d0ccea9@%3Cdev.tomee.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://lists.apache.org/thread.html/3f99ae8dcdbd69438cb733d745ee3ad5e852068490719a66509b4592@%3Ccommits.cassandra.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/issues/2389', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TXRVXNRFHJSQWFHPRJQRI5UPMZ63B544/'}
null
{'https://github.com/FasterXML/jackson-databind/commit/ad418eeb974e357f2797aef64aa0e3ffaaa6125b'}
{'https://github.com/FasterXML/jackson-databind/commit/ad418eeb974e357f2797aef64aa0e3ffaaa6125b'}
GHSA
GHSA-26rr-v2j2-25fh
Layout XML Arbitrary Code Fix
### Impact Layout XML enabled admin users to execute arbitrary commands via block methods.
{'CVE-2021-32758'}
2021-08-30T17:20:52Z
2021-08-30T17:20:52Z
HIGH
0
{'CWE-91'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-32758', 'https://github.com/OpenMage/magento-lts/security/advisories/GHSA-26rr-v2j2-25fh', 'https://github.com/OpenMage/magento-lts/commit/b99307d00b59c4a226a1e3e4083f02cf2fc8fce7', 'https://github.com/OpenMage/magento-lts/releases/tag/v20.0.13', 'https://github.com/OpenMage/magento-lts/releases/tag/v19.4.15', 'https://github.com/advisories/GHSA-26rr-v2j2-25fh'}
null
{'https://github.com/OpenMage/magento-lts/commit/b99307d00b59c4a226a1e3e4083f02cf2fc8fce7'}
{'https://github.com/OpenMage/magento-lts/commit/b99307d00b59c4a226a1e3e4083f02cf2fc8fce7'}
GHSA
GHSA-fm93-fhh2-cg2c
Prototype Pollution in min-dash
The package min-dash before 3.8.1 are vulnerable to Prototype Pollution via the set method due to missing enforcement of key types.
{'CVE-2021-23460'}
2022-01-27T14:21:53Z
2022-01-27T14:21:53Z
HIGH
7.5
{'CWE-1321'}
{'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2342127', 'https://github.com/bpmn-io/min-dash/blob/c4d579c0eb2ed0739592111c3906b198921d3f52/lib/object.js%23L32', 'https://github.com/bpmn-io/min-dash/pull/21/commits/5ab05cbc4fd8d5eafb7db540c491ed0906b9d320', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23460', 'https://github.com/advisories/GHSA-fm93-fhh2-cg2c', 'https://github.com/bpmn-io/min-dash/pull/21', 'https://snyk.io/vuln/SNYK-JS-MINDASH-2340605'}
null
{'https://github.com/bpmn-io/min-dash/pull/21/commits/5ab05cbc4fd8d5eafb7db540c491ed0906b9d320'}
{'https://github.com/bpmn-io/min-dash/pull/21/commits/5ab05cbc4fd8d5eafb7db540c491ed0906b9d320'}
GHSA
GHSA-5w25-hxp5-h8c9
Improper Verification of Cryptographic Signature
tEnvoy contains the PGP, NaCl, and PBKDF2 in node.js and the browser (hashing, random, encryption, decryption, signatures, conversions), used by TogaTech.org. In versions prior to 7.0.3, the `verifyWithMessage` method of `tEnvoyNaClSigningKey` always returns `true` for any signature that has a SHA-512 hash matching the SHA-512 hash of the message even if the signature was invalid. This issue is patched in version 7.0.3. As a workaround: In `tenvoy.js` under the `verifyWithMessage` method definition within the `tEnvoyNaClSigningKey` class, ensure that the return statement call to `this.verify` ends in `.verified`.
{'CVE-2021-32685'}
2021-06-21T17:12:13Z
2021-06-21T17:12:13Z
CRITICAL
9.8
{'CWE-347'}
{'https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b', 'https://github.com/advisories/GHSA-5w25-hxp5-h8c9', 'https://github.com/TogaTech/tEnvoy/releases/tag/v7.0.3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32685', 'https://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m'}
null
{'https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b'}
{'https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b'}
GHSA
GHSA-xm2v-8rrw-w9pm
Division by 0 in `Conv2DBackpropInput`
### Impact An attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropInput`: ```python import tensorflow as tf input_tensor = tf.constant([52, 1, 1, 5], shape=[4], dtype=tf.int32) filter_tensor = tf.constant([], shape=[0, 1, 5, 0], dtype=tf.float32) out_backprop = tf.constant([], shape=[52, 1, 1, 0], dtype=tf.float32) tf.raw_ops.Conv2DBackpropInput(input_sizes=input_tensor, filter=filter_tensor, out_backprop=out_backprop, strides=[1, 1, 1, 1], use_cudnn_on_gpu=True, padding='SAME', explicit_paddings=[], data_format='NHWC', dilations=[1, 1, 1, 1]) ``` This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/b40060c9f697b044e3107917c797ba052f4506ab/tensorflow/core/kernels/conv_grad_input_ops.h#L625-L655) does a division by a quantity that is controlled by the caller: ```cc const size_t size_A = output_image_size * dims.out_depth; const size_t size_B = filter_total_size * dims.out_depth; const size_t size_C = output_image_size * filter_total_size; const size_t work_unit_size = size_A + size_B + size_C; ... const size_t shard_size = use_parallel_contraction ? 1 : (target_working_set_size + work_unit_size - 1) / work_unit_size; ``` ### Patches We have patched the issue in GitHub commit [2be2cdf3a123e231b16f766aa0e27d56b4606535](https://github.com/tensorflow/tensorflow/commit/2be2cdf3a123e231b16f766aa0e27d56b4606535). 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-29525'}
2021-05-21T14:21:51Z
2021-05-21T14:21:51Z
LOW
2.5
{'CWE-369'}
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xm2v-8rrw-w9pm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29525', 'https://github.com/tensorflow/tensorflow/commit/2be2cdf3a123e231b16f766aa0e27d56b4606535', 'https://github.com/advisories/GHSA-xm2v-8rrw-w9pm'}
null
{'https://github.com/tensorflow/tensorflow/commit/2be2cdf3a123e231b16f766aa0e27d56b4606535'}
{'https://github.com/tensorflow/tensorflow/commit/2be2cdf3a123e231b16f766aa0e27d56b4606535'}
GHSA
GHSA-8c76-mxv5-w4g8
Stored Cross-site Scripting in Microweber
Microweber 1.2.11 and prior contains multiple stored cross-site scripting vulnerabilities in Shop's Other Settings, Shop's Autorespond E-mail Settings and Shops' Payments Methods.
{'CVE-2022-0954'}
2022-03-28T17:25:38Z
2022-03-16T00:00:48Z
MODERATE
6.8
{'CWE-79'}
{'https://huntr.dev/bounties/b99517c0-37fc-4efa-ab1a-3591da7f4d26', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0954', 'https://github.com/microweber/microweber/commit/955471c27e671c49e4b012e3b120b004082ac3f7', 'https://github.com/advisories/GHSA-8c76-mxv5-w4g8'}
null
{'https://github.com/microweber/microweber/commit/955471c27e671c49e4b012e3b120b004082ac3f7'}
{'https://github.com/microweber/microweber/commit/955471c27e671c49e4b012e3b120b004082ac3f7'}
GHSA
GHSA-x5cp-9pcf-pp3h
Denial of Service in Tensorflow
### Impact The `RaggedCountSparseOutput` does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the `splits` tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L241-L244 Since `BatchedMap` is equivalent to a vector, it needs to have at least one element to not be `nullptr`. If user passes a `splits` tensor that is empty or has exactly one element, we get a `SIGABRT` signal raised by the operating system. ### Patches We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release. We recommend users to upgrade to TensorFlow 2.3.1. ### 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 is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)
{'CVE-2020-15199'}
2021-08-26T15:11:58Z
2020-09-25T18:28:24Z
MODERATE
5.9
{'CWE-20'}
{'https://nvd.nist.gov/vuln/detail/CVE-2020-15199', 'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x5cp-9pcf-pp3h', 'https://github.com/advisories/GHSA-x5cp-9pcf-pp3h', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'}
null
{'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'}
{'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'}
GHSA
GHSA-h98h-8mxr-m8gx
Out-of-bounds read in TensorFlow possibly causing disclosure of the contents of process memory.
TensorFlow before 1.7.0 has an integer overflow that causes an out-of-bounds read, possibly causing disclosure of the contents of process memory. This occurs in the DecodeBmp feature of the BMP decoder in core/kernels/decode_bmp_op.cc.
{'CVE-2018-21233'}
2021-08-25T21:09:13Z
2020-05-13T16:01:35Z
MODERATE
6.5
{'CWE-125'}
{'https://nvd.nist.gov/vuln/detail/CVE-2018-21233', 'https://github.com/advisories/GHSA-h98h-8mxr-m8gx', 'https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2018-001.md', 'https://github.com/tensorflow/tensorflow/commit/49f73c55d56edffebde4bca4a407ad69c1cae433'}
null
{'https://github.com/tensorflow/tensorflow/commit/49f73c55d56edffebde4bca4a407ad69c1cae433'}
{'https://github.com/tensorflow/tensorflow/commit/49f73c55d56edffebde4bca4a407ad69c1cae433'}
GHSA
GHSA-grfp-q2mm-hfp6
Redirect URL matching ignores character casing
### Impact Before version v0.34.1, the OAuth 2.0 Client's registered redirect URLs and the redirect URL provided at the OAuth2 Authorization Endpoint where compared using `strings.ToLower` while they should have been compared with a simple string match: 1. Registering a client with allowed redirect URL `https://example.com/callback` 2. Performing OAuth2 flow and requesting redirect URL `https://example.com/CALLBACK` 3. Instead of an error (invalid redirect URL), the browser is redirected to `https://example.com/CALLBACK` with a potentially successful OAuth2 response, depending on the state of the overall OAuth2 flow (the user might still deny the request for example).
{'CVE-2020-15234'}
2022-04-19T19:02:36Z
2021-05-24T17:00:05Z
MODERATE
6.1
{'CWE-20', 'CWE-178', 'CWE-601'}
{'https://nvd.nist.gov/vuln/detail/CVE-2020-15234', 'https://github.com/ory/fosite/security/advisories/GHSA-grfp-q2mm-hfp6', 'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf', 'https://github.com/advisories/GHSA-grfp-q2mm-hfp6'}
null
{'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf'}
{'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf'}
GHSA
GHSA-545v-42p7-98fq
Heap out of bounds read in `MaxPoolGradWithArgmax`
### Impact The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs: ```python import tensorflow as tf input = tf.constant([10.0, 10.0, 10.0], shape=[1, 1, 3, 1], dtype=tf.float32) grad = tf.constant([10.0, 10.0, 10.0, 10.0], shape=[1, 1, 1, 4], dtype=tf.float32) argmax = tf.constant([1], shape=[1], dtype=tf.int64) ksize = [1, 1, 1, 1] strides = [1, 1, 1, 1] tf.raw_ops.MaxPoolGradWithArgmax( input=input, grad=grad, argmax=argmax, ksize=ksize, strides=strides, padding='SAME', include_batch_in_index=False) ``` The [implementation](https://github.com/tensorflow/tensorflow/blob/ef0c008ee84bad91ec6725ddc42091e19a30cf0e/tensorflow/core/kernels/maxpooling_op.cc#L1016-L1017) uses the same value to index in two different arrays but there is no guarantee that the sizes are identical. ### Patches We have patched the issue in GitHub commit [dcd7867de0fea4b72a2b34bd41eb74548dc23886](https://github.com/tensorflow/tensorflow/commit/dcd7867de0fea4b72a2b34bd41eb74548dc23886). The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.
{'CVE-2021-29570'}
2021-05-21T14:25:25Z
2021-05-21T14:25:25Z
LOW
2.5
{'CWE-125'}
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-545v-42p7-98fq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29570', 'https://github.com/tensorflow/tensorflow/commit/dcd7867de0fea4b72a2b34bd41eb74548dc23886', 'https://github.com/advisories/GHSA-545v-42p7-98fq'}
null
{'https://github.com/tensorflow/tensorflow/commit/dcd7867de0fea4b72a2b34bd41eb74548dc23886'}
{'https://github.com/tensorflow/tensorflow/commit/dcd7867de0fea4b72a2b34bd41eb74548dc23886'}
GHSA
GHSA-23cm-x6j7-6hq3
matrix-js-sdk can be tricked into disclosing E2EE room keys to a participating homeserver
### Impact A logic error in the room key sharing functionality of matrix-js-sdk before 12.4.1 allows a malicious Matrix homeserver† participating in an encrypted room to steal room encryption keys from affected Matrix clients participating in that room. This allows the homeserver to decrypt end-to-end encrypted messages sent by affected clients. † Or anyone with access to the account of the original recipient of an encrypted message. Known clients affected (via their use of vulnerable versions of matrix-js-sdk): - Element Web (1.8.2 and earlier) - Element Desktop (1.8.2 and earlier) - SchildiChat Web (1.7.32-sc1 and earlier) - SchildiChat Desktop (1.7.32-sc1 and earlier) - Cinny (1.2.0 and earlier) ### Patch This was fixed in https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9. ### Workarounds To prevent a homeserver from being able to steal the room keys, vulnerable clients can be taken offline or signed out. If signing out, care should be taken to either set up Secure Backup or export E2E room keys in order to preserve access to past messages.
{'CVE-2021-40823'}
2022-04-19T19:03:08Z
2021-09-14T20:24:18Z
MODERATE
5.9
{'CWE-200'}
{'https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-23cm-x6j7-6hq3', 'https://github.com/matrix-org/matrix-js-sdk/releases/tag/v12.4.1', 'https://matrix.org/blog/2021/09/13/vulnerability-disclosure-key-sharing', 'https://github.com/advisories/GHSA-23cm-x6j7-6hq3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-40823', 'https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9'}
null
{'https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9'}
{'https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9'}
GHSA
GHSA-g5vf-v6wf-7w2r
Ciphertext Malleability Issue in Tink Java
### Impact Tink's Java version before 1.5 under some circumstances allowed attackers to change the key ID part of the ciphertext, resulting in the attacker creating a second ciphertext that will decrypt to the same plaintext. This can be a problem in particular in the case of encrypting with a deterministic AEAD with a single key, and relying on the fact that there is only a single valid ciphertext per plaintext. No loss of confidentiality or loss of plaintext integrity occurs due to this problem, only ciphertext integrity is compromised. ### Patches The issue was fixed in this [pull request](https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899). ### Workarounds The only workaround is to backport the fixing [pull request](https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899). ### Details Tink uses the first five bytes of a ciphertext for a version byte and a four byte key ID. Since each key has a well defined prefix, this extends non-malleability properties (but technically not indistinguishability). However, in the Java version this prefix lookup used a hash map indexed by unicode strings instead of the byte array, which means that invalid Unicode characters would be [replaced by U+FFFD](https://en.wikipedia.org/wiki/UTF-8#Invalid_sequences_and_error_handling) by the [Java API's default behavior](https://docs.oracle.com/javase/7/docs/api/java/lang/String.html#String(byte[],%20java.nio.charset.Charset)). This means several different values for the five bytes would result in the same hash table key, which allows an attacker to exchange one invalid byte sequence for another, creating a mutated ciphertext that still decrypts (to the same plaintext). ### Acknowledgements We'd like to thank Peter Esbensen for finding this issue and raising it internally. ### For more information If you have any questions or comments about this advisory: * Open an issue in [Tink](https://github.com/google/tink/issues)
{'CVE-2020-8929'}
2022-04-19T19:02:38Z
2020-10-16T00:51:24Z
LOW
5.3
{'CWE-327', 'CWE-176'}
{'https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r', 'https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8929', 'https://github.com/advisories/GHSA-g5vf-v6wf-7w2r'}
null
{'https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899'}
{'https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899'}
GHSA
GHSA-h86j-6h6m-qjqw
Cross-Site Request Forgery in remdex/livehelperchat
An attacker is able to log out a user if a logged-in user visits the attacker's website. While this cannot harm a user's account, it can be a great annoyance and is a valid CSRF.
{'CVE-2021-4049'}
2021-12-10T20:26:34Z
2021-12-10T20:26:34Z
LOW
0
{'CWE-352'}
{'https://github.com/livehelperchat/livehelperchat/commit/e7fe1aa6a087d4d21b2e8a0dadd2e08f42acbb57', 'https://github.com/advisories/GHSA-h86j-6h6m-qjqw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4049', 'https://huntr.dev/bounties/62408fa4-2c16-4fcd-8b34-41fcdccb779e'}
null
{'https://github.com/livehelperchat/livehelperchat/commit/e7fe1aa6a087d4d21b2e8a0dadd2e08f42acbb57'}
{'https://github.com/livehelperchat/livehelperchat/commit/e7fe1aa6a087d4d21b2e8a0dadd2e08f42acbb57'}
GHSA
GHSA-5mv2-rx3q-4w2v
Code injection in Twig
# Description When in a sandbox mode, the `arrow` parameter of the `sort` filter must be a closure to avoid attackers being able to run arbitrary PHP functions. # Resolution We now disallow calling non Closure in the `sort` filter like we already did for some other filters. # Credits We would like to thank Marlon Starkloff for reporting the issue and Fabien Potencier for fixing the issue.
{'CVE-2022-23614'}
2022-03-29T22:07:03Z
2022-02-10T22:21:48Z
HIGH
8.8
{'CWE-74'}
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PECHIY2XLWUH2WLCNPDGNFMPHPRPCEDZ/', 'https://www.debian.org/security/2022/dsa-5107', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23614', 'https://github.com/twigphp/Twig/commit/2eb33080558611201b55079d07ac88f207b466d5', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/I2PVV5DUTRUECTIHMTWRI5Z7DVNYQ2YO/', 'https://github.com/twigphp/Twig/commit/22b9dc3c03ee66d7e21d9ed2ca76052b134cb9e9', 'https://github.com/advisories/GHSA-5mv2-rx3q-4w2v', 'https://github.com/twigphp/Twig/security/advisories/GHSA-5mv2-rx3q-4w2v', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OTN4273U4RHVIXED64T7DSMJ3VYTPRE7/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SIGZCFSYLPP7UVJ4E4NLHSOQSKYNXSAD/'}
null
{'https://github.com/twigphp/Twig/commit/22b9dc3c03ee66d7e21d9ed2ca76052b134cb9e9', 'https://github.com/twigphp/Twig/commit/2eb33080558611201b55079d07ac88f207b466d5'}
{'https://github.com/twigphp/Twig/commit/22b9dc3c03ee66d7e21d9ed2ca76052b134cb9e9', 'https://github.com/twigphp/Twig/commit/2eb33080558611201b55079d07ac88f207b466d5'}
GHSA
GHSA-4hrh-9vmp-2jgg
Heap buffer overflow in `StringNGrams`
### Impact An attacker can cause a heap buffer overflow by passing crafted inputs to `tf.raw_ops.StringNGrams`: ```python import tensorflow as tf separator = b'\x02\x00' ngram_widths = [7, 6, 11] left_pad = b'\x7f\x7f\x7f\x7f\x7f' right_pad = b'\x7f\x7f\x25\x5d\x53\x74' pad_width = 50 preserve_short_sequences = True l = ['', '', '', '', '', '', '', '', '', '', ''] data = tf.constant(l, shape=[11], dtype=tf.string) l2 = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3] data_splits = tf.constant(l2, shape=[116], dtype=tf.int64) out = tf.raw_ops.StringNGrams(data=data, data_splits=data_splits, separator=separator, ngram_widths=ngram_widths, left_pad=left_pad, right_pad=right_pad, pad_width=pad_width, preserve_short_sequences=preserve_short_sequences) ``` This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L171-L185) fails to consider corner cases where input would be split in such a way that the generated tokens should only contain padding elements: ```cc for (int ngram_index = 0; ngram_index < num_ngrams; ++ngram_index) { int pad_width = get_pad_width(ngram_width); int left_padding = std::max(0, pad_width - ngram_index); int right_padding = std::max(0, pad_width - (num_ngrams - (ngram_index + 1))); int num_tokens = ngram_width - (left_padding + right_padding); int data_start_index = left_padding > 0 ? 0 : ngram_index - pad_width; ... tstring* ngram = &output[ngram_index]; ngram->reserve(ngram_size); for (int n = 0; n < left_padding; ++n) { ngram->append(left_pad_); ngram->append(separator_); } for (int n = 0; n < num_tokens - 1; ++n) { ngram->append(data[data_start_index + n]); ngram->append(separator_); } ngram->append(data[data_start_index + num_tokens - 1]); // <<< for (int n = 0; n < right_padding; ++n) { ngram->append(separator_); ngram->append(right_pad_); } ... } ``` If input is such that `num_tokens` is 0, then, for `data_start_index=0` (when left padding is present), the marked line would result in reading `data[-1]`. ### Patches We have patched the issue in GitHub commit [ba424dd8f16f7110eea526a8086f1a155f14f22b](https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b). 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-29542'}
2022-04-26T18:10:15Z
2021-05-21T14:23:15Z
LOW
2.5
{'CWE-131', 'CWE-787'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-29542', 'https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b', 'https://github.com/advisories/GHSA-4hrh-9vmp-2jgg', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4hrh-9vmp-2jgg'}
null
{'https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b'}
{'https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b'}
GHSA
GHSA-452g-f7fp-9jf7
Type confusion during tensor casts lead to dereferencing null pointers
### Impact Calling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences. There are multiple ways to reproduce this, listing a few examples here: ```python import tensorflow as tf import numpy as np data = tf.random.truncated_normal(shape=1,mean=np.float32(20.8739),stddev=779.973,dtype=20,seed=64) ``` ```python import tensorflow as tf import numpy as np data = tf.random.stateless_truncated_normal(shape=1,seed=[63,70],mean=np.float32(20.8739),stddev=779.973,dtype=20) ``` ```python import tensorflow as tf import numpy as np data = tf.one_hot(indices=[62,50],depth=136,on_value=np.int32(237),off_value=158,axis=856,dtype=20) ``` ```python import tensorflow as tf import numpy as np data = tf.range(start=np.int32(214),limit=660,delta=129,dtype=20) ``` ```python import tensorflow as tf import numpy as np data = tf.raw_ops.ResourceCountUpTo(resource=np.int32(30), limit=872, T=3) ``` ```python import tensorflow as tf import numpy as np writer_array = np.array([1,2],dtype=np.int32) writer_tensor = tf.convert_to_tensor(writer_array,dtype=tf.resource) ``` All these examples and similar ones have the same behavior: the [conversion from Python array to C++ array](https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion: ```cc int pyarray_type = PyArray_TYPE(array); PyArray_Descr* descr = PyArray_DESCR(array); switch (pyarray_type) { ... case NPY_VOID: // Quantized types are currently represented as custom struct types. // PyArray_TYPE returns NPY_VOID for structs, and we should look into // descr to derive the actual type. // Direct feeds of certain types of ResourceHandles are represented as a // custom struct type. return PyArrayDescr_to_TF_DataType(descr, out_tf_datatype); ... } ``` For the tensor types involved in the above example, the `pyarray_type` is `NPY_VOID` but the `descr` field is such that `descr->field = NULL`. Then [`PyArrayDescr_to_TF_DataType`](https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L72-L77) will trigger a null dereference: ```cc Status PyArrayDescr_to_TF_DataType(PyArray_Descr* descr, TF_DataType* out_tf_datatype) { PyObject* key; PyObject* value; Py_ssize_t pos = 0; if (PyDict_Next(descr->fields, &pos, &key, &value)) { ... } } ``` This is because the Python's `PyDict_Next` implementation would dereference the first argument. ### Patches We have patched the issue in GitHub commit [030af767d357d1b4088c4a25c72cb3906abac489](https://github.com/tensorflow/tensorflow/commit/030af767d357d1b4088c4a25c72cb3906abac489). 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 as well as Ye Zhang and Yakun Zhang of Baidu X-Team.
{'CVE-2021-29513'}
2021-05-21T14:20:46Z
2021-05-21T14:20:46Z
LOW
2.5
{'CWE-476'}
{'https://github.com/tensorflow/tensorflow/commit/030af767d357d1b4088c4a25c72cb3906abac489', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-452g-f7fp-9jf7', 'https://github.com/advisories/GHSA-452g-f7fp-9jf7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29513'}
null
{'https://github.com/tensorflow/tensorflow/commit/030af767d357d1b4088c4a25c72cb3906abac489'}
{'https://github.com/tensorflow/tensorflow/commit/030af767d357d1b4088c4a25c72cb3906abac489'}
GHSA
GHSA-p55x-7x9v-q8m4
Denial of Service in miekg-dns
A denial of service flaw was found in miekg-dns before 1.0.4. A remote attacker could use carefully timed TCP packets to block the DNS server from accepting new connections.
{'CVE-2017-15133'}
2021-06-29T21:45:07Z
2021-06-29T21:45:07Z
HIGH
7.5
{'CWE-400'}
{'https://github.com/miekg/dns/pull/631', 'https://github.com/advisories/GHSA-p55x-7x9v-q8m4', 'https://github.com/miekg/dns/issues/627', 'https://bugzilla.redhat.com/show_bug.cgi?id=1538763', 'https://nvd.nist.gov/vuln/detail/CVE-2017-15133', 'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'}
null
{'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'}
{'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'}
GHSA
GHSA-g7mq-rfj2-25wq
Code Injection in total4
The package total4 before 0.0.43 are vulnerable to Arbitrary Code Execution via the U.set() and U.get() functions.
{'CVE-2021-23390'}
2021-12-10T17:26:33Z
2021-12-10T17:26:33Z
CRITICAL
9.8
{'CWE-94'}
{'https://github.com/totaljs/framework4/blob/master/utils.js%23L5430-L5455', 'https://github.com/advisories/GHSA-g7mq-rfj2-25wq', 'https://github.com/totaljs/framework4/commit/8a72d8c20f38bbcac031a76a51238aa528f68821', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23390', 'https://snyk.io/vuln/SNYK-JS-TOTAL4-1130527'}
null
{'https://github.com/totaljs/framework4/commit/8a72d8c20f38bbcac031a76a51238aa528f68821'}
{'https://github.com/totaljs/framework4/commit/8a72d8c20f38bbcac031a76a51238aa528f68821'}
GHSA
GHSA-rc3x-jf5g-xvc5
Open redirect in karma
Karma before 6.3.16 is vulnerable to Open Redirect due to missing validation of the return_url query parameter.
{'CVE-2021-23495'}
2022-03-09T21:08:21Z
2022-02-26T00:00:38Z
MODERATE
5.4
{'CWE-601'}
{'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2412347', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23495', 'https://snyk.io/vuln/SNYK-JS-KARMA-2396325', 'https://github.com/karma-runner/karma/commit/ff7edbb2ffbcdd69761bece86b7dc1ef0740508d', 'https://github.com/advisories/GHSA-rc3x-jf5g-xvc5'}
null
{'https://github.com/karma-runner/karma/commit/ff7edbb2ffbcdd69761bece86b7dc1ef0740508d'}
{'https://github.com/karma-runner/karma/commit/ff7edbb2ffbcdd69761bece86b7dc1ef0740508d'}
GHSA
GHSA-h9px-9vqg-222h
Heap OOB in `QuantizeAndDequantizeV3`
### Impact An attacker can read data outside of bounds of heap allocated buffer in `tf.raw_ops.QuantizeAndDequantizeV3`: ```python import tensorflow as tf tf.raw_ops.QuantizeAndDequantizeV3( input=[2.5,2.5], input_min=[0,0], input_max=[1,1], num_bits=[30], signed_input=False, range_given=False, narrow_range=False, axis=3) ``` This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/11ff7f80667e6490d7b5174aa6bf5e01886e770f/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L237) does not validate the value of user supplied `axis` attribute before using it to index in the array backing the `input` argument: ```cc const int depth = (axis_ == -1) ? 1 : input.dim_size(axis_); ``` ### Patches We have patched the issue in GitHub commit [99085e8ff02c3763a0ec2263e44daec416f6a387](https://github.com/tensorflow/tensorflow/commit/99085e8ff02c3763a0ec2263e44daec416f6a387). 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 Aivul Team from Qihoo 360.
{'CVE-2021-29553'}
2021-05-21T14:23:51Z
2021-05-21T14:23:51Z
LOW
2.5
{'CWE-125'}
{'https://github.com/advisories/GHSA-h9px-9vqg-222h', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29553', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h9px-9vqg-222h', 'https://github.com/tensorflow/tensorflow/commit/99085e8ff02c3763a0ec2263e44daec416f6a387'}
null
{'https://github.com/tensorflow/tensorflow/commit/99085e8ff02c3763a0ec2263e44daec416f6a387'}
{'https://github.com/tensorflow/tensorflow/commit/99085e8ff02c3763a0ec2263e44daec416f6a387'}
GHSA
GHSA-cpxc-67rc-c775
Cross Site Scripting in baserCMS
baserCMS 4.3.6 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: content_fields.php, content_info.php, content_options.php, content_related.php, index_list_tree.php, jquery.bcTree.js * Tested baserCMS Version : 4.3.6 (Latest) * Affected baserCMS Version : 4.0.0 ~ 4.3.6 * Patches : https://basercms.net/security/20200827 Found by Aquilao Null
{'CVE-2020-15154'}
2022-04-19T19:02:32Z
2020-08-28T20:48:12Z
LOW
7.3
{'CWE-79'}
{'https://basercms.net/security/20200827', 'https://github.com/baserproject/basercms/security/advisories/GHSA-cpxc-67rc-c775', 'https://github.com/baserproject/basercms/commit/7f4b905b90954e394ec10dd35bad2a5dec505371', 'https://github.com/advisories/GHSA-cpxc-67rc-c775', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15154'}
null
{'https://github.com/baserproject/basercms/commit/7f4b905b90954e394ec10dd35bad2a5dec505371'}
{'https://github.com/baserproject/basercms/commit/7f4b905b90954e394ec10dd35bad2a5dec505371'}
GHSA
GHSA-2w67-526p-gm73
redis-store deserializes untrusted data the affected version range and description should be adjust to match as well
Redis-store <=v1.3.0 allows unsafe objects to be loaded from redis
{'CVE-2017-1000248'}
2022-04-25T22:08:36Z
2017-12-06T16:41:25Z
CRITICAL
9.8
{'CWE-502'}
{'https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000248', 'https://github.com/advisories/GHSA-2w67-526p-gm73'}
null
{'https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e'}
{'https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e'}
GHSA
GHSA-769f-539v-f5jg
PrestaShop gamification module ZIP archives were vulnerable from CVE-2017-9841
### Impact We have identified that some gamification module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE. This vulnerability impacts - phpunit before 4.8.28 and 5.x before 5.6.3 as reported in [CVE-2017-9841](https://nvd.nist.gov/vuln/detail/CVE-2017-9841) - phpunit >= 5.63 before 7.5.19 and 8.5.1 (this is a newly found vulnerability that is currently being submitted as a CVE after disclosure was provided to phpunit maintainers) You can read PrestaShop official statement about this vulnerability [here](https://build.prestashop.com/news/critical-security-vulnerability-in-prestashop-modules/). ### Patches In the [security patch](https://github.com/PrestaShop/gamification/releases/tag/v2.3.2), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading. ### Workarounds Users can also simply remove the unwanted vendor/phpunit folder. ### References https://nvd.nist.gov/vuln/detail/CVE-2017-9841 ### For more information If you have any questions or comments about this advisory, email us at security@prestashop.com
null
2020-01-08T03:10:44Z
2020-01-08T03:10:44Z
HIGH
0
null
{'https://build.prestashop.com/news/critical-security-vulnerability-in-prestashop-modules/', 'https://github.com/advisories/GHSA-769f-539v-f5jg', 'https://github.com/PrestaShop/gamification/security/advisories/GHSA-769f-539v-f5jg', 'https://github.com/PrestaShop/gamification/commit/5044bda903a7ea9596c21faa2b9a42244763568c'}
null
{'https://github.com/PrestaShop/gamification/commit/5044bda903a7ea9596c21faa2b9a42244763568c'}
{'https://github.com/PrestaShop/gamification/commit/5044bda903a7ea9596c21faa2b9a42244763568c'}
GHSA
GHSA-hgjh-723h-mx2j
Authorization Bypass Through User-Controlled Key in url-parse
url-parse prior to version 1.5.8 is vulnerable to Authorization Bypass Through User-Controlled Key.
{'CVE-2022-0686'}
2022-03-29T22:13:52Z
2022-02-21T00:00:21Z
CRITICAL
9.1
{'CWE-639'}
{'https://github.com/unshiftio/url-parse/commit/d5c64791ef496ca5459ae7f2176a31ea53b127e5', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0686', 'https://huntr.dev/bounties/55fd06cd-9054-4d80-83be-eb5a454be78c', 'https://security.netapp.com/advisory/ntap-20220325-0006/', 'https://github.com/advisories/GHSA-hgjh-723h-mx2j'}
null
{'https://github.com/unshiftio/url-parse/commit/d5c64791ef496ca5459ae7f2176a31ea53b127e5'}
{'https://github.com/unshiftio/url-parse/commit/d5c64791ef496ca5459ae7f2176a31ea53b127e5'}
GHSA
GHSA-vxf6-w9mp-95hm
Low severity vulnerability that affects puppet
lib/puppet/network/authstore.rb in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames without warning of potential risks, which might allow remote attackers to spoof an agent by acquiring a previously used IP address.
{'CVE-2012-3408'}
2021-09-20T22:23:47Z
2017-10-24T18:33:38Z
LOW
0
{'CWE-287'}
{'https://nvd.nist.gov/vuln/detail/CVE-2012-3408', 'https://github.com/advisories/GHSA-vxf6-w9mp-95hm', 'http://puppetlabs.com/security/cve/cve-2012-3408/', 'https://github.com/puppetlabs/puppet/commit/ab9150baa1b738467a33b01df1d90e076253fbbd', 'https://bugzilla.redhat.com/show_bug.cgi?id=839166'}
null
{'https://github.com/puppetlabs/puppet/commit/ab9150baa1b738467a33b01df1d90e076253fbbd'}
{'https://github.com/puppetlabs/puppet/commit/ab9150baa1b738467a33b01df1d90e076253fbbd'}
GHSA
GHSA-vmqm-g3vh-847m
Denial of service in Apache Xerces2
Apache Xerces2 Java Parser before 2.12.0 allows remote attackers to cause a denial of service (CPU consumption) via a crafted message to an XML service, which triggers hash table collisions.
{'CVE-2012-0881'}
2021-09-29T18:00:54Z
2020-06-15T18:51:38Z
HIGH
7.5
{'CWE-400'}
{'https://github.com/apache/xerces2-j/commit/992b5d9c24102ad20330d36c0a71162753a37449', 'https://lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451@%3Csolr-user.lucene.apache.org%3E', 'https://bugzilla.redhat.com/show_bug.cgi?id=787104', 'http://www.openwall.com/lists/oss-security/2014/07/08/11', 'https://lists.apache.org/thread.html/rea7b831dceeb2a2fa817be6f63b08722042e3647fb2d47c144370a56@%3Ccommon-issues.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://issues.apache.org/jira/browse/XERCESJ-1685', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://github.com/advisories/GHSA-vmqm-g3vh-847m', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2012-0881', 'https://lists.apache.org/thread.html/r204ba2a9ea750f38d789d2bb429cc0925ad6133deea7cbc3001d96b5@%3Csolr-user.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/49dc6702104a86ecbb40292dcd329ce9ae4c32b74733199ecab14a73@%3Cj-users.xerces.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html'}
null
{'https://github.com/apache/xerces2-j/commit/992b5d9c24102ad20330d36c0a71162753a37449'}
{'https://github.com/apache/xerces2-j/commit/992b5d9c24102ad20330d36c0a71162753a37449'}
GHSA
GHSA-9m4x-8w29-r78g
Server-Side Request Forgery in @uppy/companion
The @uppy/companion npm package before versions 1.13.2 and 2.0.0-alpha.5 is vulnerable to a Server-Side Request Forgery (SSRF) vulnerability, which allows an attacker to scan local or external networks or otherwise interact with internal systems.
{'CVE-2020-8205'}
2021-01-08T20:55:35Z
2020-08-13T18:54:19Z
MODERATE
0
{'CWE-918'}
{'https://github.com/transloadit/uppy/pull/2322/commits/dbf2f4f30aeaf3bcc5971bb867bb0b5984084828', 'https://hackerone.com/reports/891270', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8205', 'https://github.com/transloadit/uppy/blob/master/CHANGELOG.md#1161', 'https://github.com/advisories/GHSA-9m4x-8w29-r78g'}
null
{'https://github.com/transloadit/uppy/pull/2322/commits/dbf2f4f30aeaf3bcc5971bb867bb0b5984084828'}
{'https://github.com/transloadit/uppy/pull/2322/commits/dbf2f4f30aeaf3bcc5971bb867bb0b5984084828'}
GHSA
GHSA-vw27-fwjf-5qxm
Arbitrary command execution on Windows via qutebrowserurl: URL handler
### Impact Starting with qutebrowser v1.7.0, the Windows installer for qutebrowser registers it as a handler for certain URL schemes. With some applications such as Outlook Desktop, opening a specially crafted URL can lead to argument injection, allowing execution of qutebrowser commands, which in turn allows arbitrary code execution via commands such as `:spawn` or `:debug-pyeval`. Only Windows installs where qutebrowser is registered as URL handler are affected. It does *not* have to be set as default browser for the exploit to work. ### Patches The issue has been fixed in [qutebrowser v2.4.0](https://github.com/qutebrowser/qutebrowser/releases/tag/v2.4.0) in commit 8f46ba3f6dc7b18375f7aa63c48a1fe461190430. The fix also adds additional hardening for potential similar issues on Linux (by adding the new `--untrusted-args` flag to the `.desktop` file), though no such vulnerabilities are known. Backported patches for older versions are available, but no further releases are planned: - v1.7.x: d1ceaab - v1.8.x: ca7155d - v1.9.x: 157d871 - v1.10.x: 94a6125 - v1.11.x: 10acfbb - v1.12.x: 363a18f - v1.13.x: 410f262 - v1.14.x: e4f4d93 - v2.0.x: 15a1654 - v2.1.x: 509ddf2 - v2.2.x: 03dcba5 - v2.3.x: 00a694c (commits are referring to qutebrowser/qutebrowser on GitHub) ### Workarounds Remove qutebrowser from the default browser settings entirely, so that it does not handle any kind of URLs. Make sure to remove *all* handlers, including an (accidental) `qutebrowserURL` handler, e.g. using [NirSoft URLProtocolView](https://www.nirsoft.net/utils/url_protocol_view.html). ### Timeline 2021-10-15: Issue reported via security@qutebrowser.org by Ping Fan (Zetta) Ke of [Valkyrie-X Security Research Group (VXRL)](https://www.vxrl.hk/) 2021-10-15: Issue confirmed by @The-Compiler (lead developer), author of installer (@bitraid) contacted for help/review 2021-10-15: CVE assigned by GitHub 2021-10-15 to 2021-10-17: Fix developed 2021-10-17: Additional core developer (@toofar) contacted for help/review 2021-10-21: v2.4.0 released containing the fix 2021-10-21: Advisory and fix published ### References See the [commit message](https://github.com/qutebrowser/qutebrowser/commit/8f46ba3f6dc7b18375f7aa63c48a1fe461190430) for additional information and references to various similar issues in other projects. ### Acknowledgements Thanks to Ping Fan (Zetta) Ke of [Valkyrie-X Security Research Group](https://www.vxrl.hk/) (VXRL/@vxresearch) for finding and responsibly disclosing this issue. ### Contact If you have any questions or comments about this advisory, please email [security@qutebrowser.org](mailto:security@qutebrowser.org).
{'CVE-2021-41146'}
2021-10-22T16:20:10Z
2021-10-22T16:20:10Z
HIGH
8.8
{'CWE-88', 'CWE-77', 'CWE-641'}
{'https://github.com/advisories/GHSA-vw27-fwjf-5qxm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41146', 'https://github.com/qutebrowser/qutebrowser/commit/8f46ba3f6dc7b18375f7aa63c48a1fe461190430', 'https://github.com/qutebrowser/qutebrowser/security/advisories/GHSA-vw27-fwjf-5qxm'}
null
{'https://github.com/qutebrowser/qutebrowser/commit/8f46ba3f6dc7b18375f7aa63c48a1fe461190430'}
{'https://github.com/qutebrowser/qutebrowser/commit/8f46ba3f6dc7b18375f7aa63c48a1fe461190430'}
GHSA
GHSA-c968-pq7h-7fxv
Division by 0 in `Conv3DBackprop*`
### Impact The `tf.raw_ops.Conv3DBackprop*` operations fail to validate that the input tensors are not empty. In turn, this would result in a division by 0: ```python import tensorflow as tf input_sizes = tf.constant([0, 0, 0, 0, 0], shape=[5], dtype=tf.int32) filter_tensor = tf.constant([], shape=[0, 0, 0, 1, 0], dtype=tf.float32) out_backprop = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32) tf.raw_ops.Conv3DBackpropInputV2(input_sizes=input_sizes, filter=filter_tensor, out_backprop=out_backprop, strides=[1, 1, 1, 1, 1], padding='SAME', data_format='NDHWC', dilations=[1, 1, 1, 1, 1]) ``` ```python import tensorflow as tf input_sizes = tf.constant([1], shape=[1, 1, 1, 1, 1], dtype=tf.float32) filter_tensor = tf.constant([0, 0, 0, 1, 0], shape=[5], dtype=tf.int32) out_backprop = tf.constant([], shape=[1, 1, 1, 1, 0], dtype=tf.float32) tf.raw_ops.Conv3DBackpropFilterV2(input=input_sizes, filter_sizes=filter_tensor, out_backprop=out_backprop, strides=[1, 1, 1, 1, 1], padding='SAME', data_format='NDHWC', dilations=[1, 1, 1, 1, 1]) ``` This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/a91bb59769f19146d5a0c20060244378e878f140/tensorflow/core/kernels/conv_grad_ops_3d.cc#L430-L450) does not check that the divisor used in computing the shard size is not zero: ```cc const int64 size_A = output_image_size * dims.out_depth; const int64 size_B = filter_total_size * dims.out_depth; const int64 size_C = output_image_size * filter_total_size; const int64 work_unit_size = size_A + size_B + size_C; ... const size_t shard_size = use_parallel_contraction ? 1 : (target_working_set_size + work_unit_size - 1) / work_unit_size; ``` Thus, if attacker controls the input sizes, they can trigger a denial of service via a division by zero error. ### Patches We have patched the issue in GitHub commit [311403edbc9816df80274bd1ea8b3c0c0f22c3fa](https://github.com/tensorflow/tensorflow/commit/311403edbc9816df80274bd1ea8b3c0c0f22c3fa). 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-29522'}
2021-05-21T14:21:39Z
2021-05-21T14:21:39Z
LOW
2.5
{'CWE-369'}
{'https://github.com/tensorflow/tensorflow/commit/311403edbc9816df80274bd1ea8b3c0c0f22c3fa', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29522', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c968-pq7h-7fxv', 'https://github.com/advisories/GHSA-c968-pq7h-7fxv'}
null
{'https://github.com/tensorflow/tensorflow/commit/311403edbc9816df80274bd1ea8b3c0c0f22c3fa'}
{'https://github.com/tensorflow/tensorflow/commit/311403edbc9816df80274bd1ea8b3c0c0f22c3fa'}
GHSA
GHSA-f78f-353m-cf4j
Code Injection in node-rules
node-rules including 3.0.0 and prior to 5.0.0 allows injection of arbitrary commands. The argument rules of function "fromJSON()" can be controlled by users without any sanitization.
{'CVE-2020-7609'}
2021-12-10T20:05:37Z
2021-12-10T20:05:37Z
CRITICAL
9.8
{'CWE-94'}
{'https://snyk.io/vuln/SNYK-JS-NODERULES-560426', 'https://github.com/advisories/GHSA-f78f-353m-cf4j', 'https://github.com/mithunsatheesh/node-rules/commit/100862223904bb6478fcc33b701c7dee11f7b832,', 'https://github.com/mithunsatheesh/node-rules/commit/100862223904bb6478fcc33b701c7dee11f7b832', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7609'}
null
{'https://github.com/mithunsatheesh/node-rules/commit/100862223904bb6478fcc33b701c7dee11f7b832,', 'https://github.com/mithunsatheesh/node-rules/commit/100862223904bb6478fcc33b701c7dee11f7b832'}
{'https://github.com/mithunsatheesh/node-rules/commit/100862223904bb6478fcc33b701c7dee11f7b832,', 'https://github.com/mithunsatheesh/node-rules/commit/100862223904bb6478fcc33b701c7dee11f7b832'}
GHSA
GHSA-w942-gw6m-p62c
Denial of service in GJSON
GJSON before 1.6.4 allows attackers to cause a denial of service via crafted JSON.
{'CVE-2020-35380'}
2021-06-23T17:53:05Z
2021-06-23T17:53:05Z
HIGH
7.5
{'CWE-400'}
{'https://github.com/tidwall/gjson/issues/192', 'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35380', 'https://github.com/advisories/GHSA-w942-gw6m-p62c'}
null
{'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc'}
{'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc'}
GHSA
GHSA-6m26-25q2-cq46
Cross-site Scripting in microweber
Microweber Cross-site Scripting (XSS) - Stored XSS vulnerability on admin page up to version 1.3.
{'CVE-2022-0763'}
2022-03-09T20:36:47Z
2022-02-27T00:00:15Z
MODERATE
4.8
{'CWE-79'}
{'https://github.com/advisories/GHSA-6m26-25q2-cq46', 'https://huntr.dev/bounties/6de9c621-740d-4d7a-9d77-d90c6c87f3b6', 'https://github.com/microweber/microweber/commit/c897d0dc159849763a813184d9b75b966c6360bf', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0763'}
null
{'https://github.com/microweber/microweber/commit/c897d0dc159849763a813184d9b75b966c6360bf'}
{'https://github.com/microweber/microweber/commit/c897d0dc159849763a813184d9b75b966c6360bf'}
GHSA
GHSA-qh4w-7pw3-p4rp
Potential denial of service in bson rubygem
The Moped::BSON::ObjecId.legal? method in mongodb/bson-ruby before 3.0.4 as used in rubygem-moped allows remote attackers to cause a denial of service (worker resource consumption) via a crafted string. NOTE: This issue is due to an incomplete fix to CVE-2015-4410.
{'CVE-2015-4411'}
2021-08-25T21:02:03Z
2020-04-29T15:34:50Z
HIGH
7.5
{'CWE-400'}
{'https://github.com/mongodb/bson-ruby/compare/7446d7c6764dfda8dc4480ce16d5c023e74be5ca...28f34978a85b689a4480b4d343389bf4886522e7', 'https://github.com/advisories/GHSA-qh4w-7pw3-p4rp', 'https://nvd.nist.gov/vuln/detail/CVE-2015-4411', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161987.html', 'https://www.securityfocus.com/bid/75045', 'https://sakurity.com/blog/2015/06/04/mongo_ruby_regexp.html', 'http://www.securityfocus.com/bid/75045', 'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161964.html', 'https://github.com/mongodb/bson-ruby/commit/fef6f75413511d653c76bf924a932374a183a24f#diff-8c8558c185bbb548ccb5a6d6ac4bfee5R191', 'https://bugzilla.redhat.com/show_bug.cgi?id=1229706', 'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999', 'https://seclists.org/oss-sec/2015/q2/653', 'https://homakov.blogspot.ru/2012/05/saferweb-injects-in-various-ruby.html', 'http://www.openwall.com/lists/oss-security/2015/06/06/3', 'https://security-tracker.debian.org/tracker/CVE-2015-4411'}
null
{'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999', 'https://github.com/mongodb/bson-ruby/commit/fef6f75413511d653c76bf924a932374a183a24f#diff-8c8558c185bbb548ccb5a6d6ac4bfee5R191', 'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24'}
{'https://github.com/mongodb/bson-ruby/commit/fef6f75413511d653c76bf924a932374a183a24f#diff-8c8558c185bbb548ccb5a6d6ac4bfee5R191', 'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999', 'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24'}
GHSA
GHSA-w3f4-3q6j-rh82
Deserialization of Untrusted Data in jackson-databind
FasterXML jackson-databind through 2.8.11 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 and CVE-2017-17485 deserialization flaws. This is exploitable via two different gadgets that bypass a blacklist.
{'CVE-2018-5968'}
2021-09-22T18:44:20Z
2020-06-30T20:40:50Z
HIGH
8.1
{'CWE-184', 'CWE-502'}
{'https://github.com/FasterXML/jackson-databind/issues/1899', 'https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03902en_us', 'https://access.redhat.com/errata/RHSA-2018:0481', 'https://access.redhat.com/errata/RHSA-2019:3149', 'https://access.redhat.com/errata/RHSA-2018:0478', 'https://access.redhat.com/errata/RHSA-2018:0479', 'https://nvd.nist.gov/vuln/detail/CVE-2018-5968', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://github.com/GulajavaMinistudio/jackson-databind/pull/92/commits/038b471e2efde2e8f96b4e0be958d3e5a1ff1d05', 'https://www.debian.org/security/2018/dsa-4114', 'https://github.com/advisories/GHSA-w3f4-3q6j-rh82', 'https://access.redhat.com/errata/RHSA-2018:1525', 'https://security.netapp.com/advisory/ntap-20180423-0002/', 'https://access.redhat.com/errata/RHSA-2018:0480'}
null
{'https://github.com/GulajavaMinistudio/jackson-databind/pull/92/commits/038b471e2efde2e8f96b4e0be958d3e5a1ff1d05'}
{'https://github.com/GulajavaMinistudio/jackson-databind/pull/92/commits/038b471e2efde2e8f96b4e0be958d3e5a1ff1d05'}
GHSA
GHSA-xqfj-cr6q-pc8w
Crash in `tf.transpose` with complex inputs
### Impact Passing a complex argument to `tf.transpose` at the same time as passing `conjugate=True` argument results in a crash: ```python import tensorflow as tf tf.transpose(conjugate=True, a=complex(1)) ``` ### Patches We have received a patch for the issue in GitHub commit [1dc6a7ce6e0b3e27a7ae650bfc05b195ca793f88](https://github.com/tensorflow/tensorflow/commit/1dc6a7ce6e0b3e27a7ae650bfc05b195ca793f88). 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 in [#42105](https://github.com/tensorflow/issues/42105) and fixed in [#46973](https://github.com/tensorflow/issues/46973).
{'CVE-2021-29618'}
2021-05-21T14:28:58Z
2021-05-21T14:28:58Z
LOW
2.5
{'CWE-755'}
{'https://github.com/advisories/GHSA-xqfj-cr6q-pc8w', 'https://github.com/tensorflow/issues/46973', 'https://github.com/tensorflow/tensorflow/commit/1dc6a7ce6e0b3e27a7ae650bfc05b195ca793f88', 'https://github.com/tensorflow/issues/42105', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xqfj-cr6q-pc8w', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29618'}
null
{'https://github.com/tensorflow/tensorflow/commit/1dc6a7ce6e0b3e27a7ae650bfc05b195ca793f88'}
{'https://github.com/tensorflow/tensorflow/commit/1dc6a7ce6e0b3e27a7ae650bfc05b195ca793f88'}
GHSA
GHSA-wppj-3pjr-9w79
crater is vulnerable to Unrestricted Upload of File with Dangerous Type
crater is vulnerable to Unrestricted Upload of File with Dangerous Type
{'CVE-2021-4080'}
2022-01-21T23:55:11Z
2022-01-21T23:55:11Z
HIGH
8.8
{'CWE-434'}
{'https://github.com/crater-invoice/crater/commit/cdc913d16cf624aee852bc9163a7c6ffc8d1da9d', 'https://github.com/advisories/GHSA-wppj-3pjr-9w79', 'https://huntr.dev/bounties/d7453360-baca-4e56-985f-481275fa38db', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4080'}
null
{'https://github.com/crater-invoice/crater/commit/cdc913d16cf624aee852bc9163a7c6ffc8d1da9d'}
{'https://github.com/crater-invoice/crater/commit/cdc913d16cf624aee852bc9163a7c6ffc8d1da9d'}
GHSA
GHSA-hpcf-8vf9-q4gj
XSS in dialog closeText in jquery-ui
Affected versions of `jquery-ui` are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the `closeText` parameter in the `dialog` function. jQuery-UI is a library for manipulating UI elements via jQuery. Version 1.11.4 has a cross site scripting (XSS) vulnerability in the `closeText` parameter of the `dialog` function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector. ## Recommendation Upgrade to jQuery-UI 1.12.0 or later.
{'CVE-2016-7103'}
2022-02-08T22:08:51Z
2017-10-24T18:33:35Z
HIGH
6.1
{'CWE-79'}
{'http://rhn.redhat.com/errata/RHSA-2017-0161.html', 'http://rhn.redhat.com/errata/RHSA-2016-2933.html', 'https://security.netapp.com/advisory/ntap-20190416-0007/', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://github.com/jquery/jquery-ui/commit/9644e7bae9116edaf8d37c5b38cb32b892f10ff6', 'https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8@%3Ccommits.pulsar.apache.org%3E', 'http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html', 'https://lists.apache.org/thread.html/ba79cf1658741e9f146e4c59b50aee56656ea95d841d358d006c18b6@%3Ccommits.roller.apache.org%3E', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://nodesecurity.io/advisories/127', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://github.com/jquery/api.jqueryui.com/issues/281', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'http://www.securityfocus.com/bid/104823', 'https://www.tenable.com/security/tns-2016-19', 'https://nvd.nist.gov/vuln/detail/CVE-2016-7103', 'http://rhn.redhat.com/errata/RHSA-2016-2932.html', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://jqueryui.com/changelog/1.12.0/', 'https://www.npmjs.com/advisories/127', 'https://lists.debian.org/debian-lts-announce/2022/01/msg00014.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/E2I4UHPIW26FIALH7GGZ3IYUUA53VOOJ/', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://www.drupal.org/sa-core-2022-002', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://github.com/advisories/GHSA-hpcf-8vf9-q4gj', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://github.com/jquery/jquery-ui/pull/1622', 'https://www.oracle.com//security-alerts/cpujul2021.html'}
null
{'https://github.com/jquery/jquery-ui/commit/9644e7bae9116edaf8d37c5b38cb32b892f10ff6'}
{'https://github.com/jquery/jquery-ui/commit/9644e7bae9116edaf8d37c5b38cb32b892f10ff6'}
GHSA
GHSA-c3h9-896r-86jm
Improper Input Validation in GoGo Protobuf
An issue was discovered in GoGo Protobuf before 1.3.2. plugin/unmarshal/unmarshal.go lacks certain index validation, aka the "skippy peanut butter" issue.
{'CVE-2021-3121'}
2022-03-29T21:02:00Z
2022-03-28T20:28:00Z
HIGH
8.6
{'CWE-20', 'CWE-129'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-3121', 'https://discuss.hashicorp.com/t/hcsec-2021-23-consul-exposed-to-denial-of-service-in-gogo-protobuf-dependency/29025', 'https://lists.apache.org/thread.html/r88d69555cb74a129a7bf84838073b61259b4a3830190e05a3b87994e@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r68032132c0399c29d6cdc7bd44918535da54060a10a12b1591328bff@%3Cnotifications.skywalking.apache.org%3E', 'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc', 'https://security.netapp.com/advisory/ntap-20210219-0006/', 'https://lists.apache.org/thread.html/rc1e9ff22c5641d73701ba56362fb867d40ed287cca000b131dcf4a44@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/advisories/GHSA-c3h9-896r-86jm', 'https://github.com/gogo/protobuf/compare/v1.3.1...v1.3.2'}
null
{'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc'}
{'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc'}
GHSA
GHSA-q24h-5rq3-63j9
Incorrect Authorization in @uppy/companion
@uppy/companion prior to version 3.3.1 is vulnerable to incorrect authorization. A user with URL upload access could enumerate internal companion server networks, send local webservers files to the destination server, and finally download them If each of these files had a guessable and regular name.
{'CVE-2022-0528'}
2022-03-11T23:24:58Z
2022-03-04T00:00:19Z
HIGH
7.5
{'CWE-200', 'CWE-863'}
{'https://github.com/advisories/GHSA-q24h-5rq3-63j9', 'https://github.com/transloadit/uppy/commit/267c34045a1e62c98406d8c31261c604a11e544a', 'https://huntr.dev/bounties/8b060cc3-2420-468e-8293-b9216620175b', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0528'}
null
{'https://github.com/transloadit/uppy/commit/267c34045a1e62c98406d8c31261c604a11e544a'}
{'https://github.com/transloadit/uppy/commit/267c34045a1e62c98406d8c31261c604a11e544a'}
GHSA
GHSA-qqxw-m5fj-f7gv
The pattern '/\domain.com' is not disallowed when redirecting, allowing for open redirect
### Impact An open redirect vulnerability has been found in `oauth2_proxy`. Anyone who uses `oauth2_proxy` may potentially be impacted. For a context [detectify] have an in depth blog post about the potential impact of an open redirect. Particularly see the OAuth section. **tl;dr**: People's authentication tokens could be silently harvested by an attacker. e.g: `facebook.com/oauth.php?clientid=123&state=abc&redirect_url=https://yourdomain.com/red.php?url%3dhttps://attacker.com/` ### Patches @sauyon found the issue, and has submitted a patch. ``` diff --git a/oauthproxy.go b/oauthproxy.go index 72ab580..f420df6 100644 --- a/oauthproxy.go +++ b/oauthproxy.go @@ -517,7 +517,7 @@ func (p *OAuthProxy) GetRedirect(req *http.Request) (redirect string, err error) // IsValidRedirect checks whether the redirect URL is whitelisted func (p *OAuthProxy) IsValidRedirect(redirect string) bool { switch { - case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//"): + case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !strings.HasPrefix(redirect, "/\\"): return true case strings.HasPrefix(redirect, "http://") || strings.HasPrefix(redirect, "https://"): redirectURL, err := url.Parse(redirect) ``` This patch will be applied to the next release, which is scheduled for when this is publicly disclosed. ### Workarounds At this stage there is no work around.
{'CVE-2020-5233'}
2022-04-19T19:02:24Z
2021-12-20T18:02:38Z
MODERATE
5.9
{'CWE-601'}
{'https://github.com/advisories/GHSA-qqxw-m5fj-f7gv', 'https://github.com/oauth2-proxy/oauth2_proxy/commit/a316f8a06f3c0ca2b5fc5fa18a91781b313607b2', 'https://github.com/oauth2-proxy/oauth2_proxy/releases/tag/v5.0.0', 'https://blog.detectify.com/2019/05/16/the-real-impact-of-an-open-redirect/', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-qqxw-m5fj-f7gv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5233'}
null
{'https://github.com/oauth2-proxy/oauth2_proxy/commit/a316f8a06f3c0ca2b5fc5fa18a91781b313607b2'}
{'https://github.com/oauth2-proxy/oauth2_proxy/commit/a316f8a06f3c0ca2b5fc5fa18a91781b313607b2'}
GHSA
GHSA-553q-hpvp-q8pc
Server-Side Request Forgery in snipe/snipe-it
Admin users on the external network can perform blind POST-based SSRF (issue requests on behalf of the server into the internal network) via the Slack Integration. This vulnerability is capable of port-scanning of the internal network, issue POST requests to web servers on the internal network which can be escalated to higher-impact.
{'CVE-2021-4075'}
2021-12-10T20:22:15Z
2021-12-10T20:22:15Z
HIGH
7.2
{'CWE-918'}
{'https://github.com/snipe/snipe-it/commit/4612b9e711b3ff5d2bcddbec5b18866d25f8e34e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4075', 'https://github.com/advisories/GHSA-553q-hpvp-q8pc', 'https://huntr.dev/bounties/4386fd8b-8c80-42bb-87b8-b506c46597de'}
null
{'https://github.com/snipe/snipe-it/commit/4612b9e711b3ff5d2bcddbec5b18866d25f8e34e'}
{'https://github.com/snipe/snipe-it/commit/4612b9e711b3ff5d2bcddbec5b18866d25f8e34e'}
GHSA
GHSA-4jqc-8m5r-9rpr
Prototype Pollution in set-value
This affects the package `set-value` before 2.0.1, and starting with 3.0.0 but prior to 4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
{'CVE-2021-23440'}
2022-03-30T21:18:08Z
2021-09-13T20:09:36Z
HIGH
7.3
{'CWE-843', 'CWE-1321'}
{'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1584212', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23440', 'https://snyk.io/vuln/SNYK-JS-SETVALUE-1540541', 'https://github.com/jonschlinkert/set-value/pull/33', 'https://github.com/advisories/GHSA-4jqc-8m5r-9rpr', 'https://github.com/jonschlinkert/set-value/commit/7cf8073bb06bf0c15e08475f9f952823b4576452', 'https://www.huntr.dev/bounties/2eae1159-01de-4f82-a177-7478a408c4a2/'}
null
{'https://github.com/jonschlinkert/set-value/commit/7cf8073bb06bf0c15e08475f9f952823b4576452'}
{'https://github.com/jonschlinkert/set-value/commit/7cf8073bb06bf0c15e08475f9f952823b4576452'}
GHSA
GHSA-cpqf-3c3r-c9g2
Cobbler before 3.3.0 allows log poisoning
Cobbler before 3.3.0 allows log poisoning, and resultant Remote Code Execution, via an XMLRPC method that logs to the logfile for template injection.
{'CVE-2021-40323'}
2021-10-13T17:27:09Z
2021-10-05T17:53:20Z
HIGH
0
{'CWE-94'}
{'https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a', 'https://nvd.nist.gov/vuln/detail/CVE-2021-40323', 'https://github.com/advisories/GHSA-cpqf-3c3r-c9g2', 'https://github.com/cobbler/cobbler/releases/tag/v3.3.0'}
null
{'https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a'}
{'https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a'}
GHSA
GHSA-gjq4-69wj-p6pr
Path traversal in pimcore
The application doesn't perform a check/filter against the value of "importFile" parameter at endpoint "/admin/translation/import". After the API is executed, PHP unlink function will proceed to delete the file.
{'CVE-2022-0665'}
2022-03-03T13:27:26Z
2022-02-23T00:00:59Z
MODERATE
6.5
{'CWE-22'}
{'https://huntr.dev/bounties/423df64d-c591-4ad9-bf1c-411bcbc06ba3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0665', 'https://github.com/pimcore/pimcore/commit/28945649a6234ccaa8c94c6cd83d1954603baf3e', 'https://github.com/advisories/GHSA-gjq4-69wj-p6pr'}
null
{'https://github.com/pimcore/pimcore/commit/28945649a6234ccaa8c94c6cd83d1954603baf3e'}
{'https://github.com/pimcore/pimcore/commit/28945649a6234ccaa8c94c6cd83d1954603baf3e'}
GHSA
GHSA-vh95-rmgr-6w4m
Prototype Pollution in minimist
Affected versions of `minimist` are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of `Object`, causing the addition or modification of an existing property that will exist on all objects. Parsing the argument `--__proto__.y=Polluted` adds a `y` property with value `Polluted` to all objects. The argument `--__proto__=Polluted` raises and uncaught error and crashes the application. This is exploitable if attackers have control over the arguments being passed to `minimist`. ## Recommendation Upgrade to versions 0.2.1, 1.2.3 or later.
{'CVE-2020-7598'}
2022-04-26T21:01:40Z
2020-04-03T21:48:32Z
MODERATE
5.6
{'CWE-1321'}
{'https://github.com/substack/minimist/commit/38a4d1caead72ef99e824bb420a2528eec03d9ab', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7598', 'https://www.npmjs.com/advisories/1179', 'https://github.com/advisories/GHSA-vh95-rmgr-6w4m', 'http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00024.html', 'https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94', 'https://github.com/substack/minimist/commit/4cf1354839cb972e38496d35e12f806eea92c11f#diff-a1e0ee62c91705696ddb71aa30ad4f95', 'https://snyk.io/vuln/SNYK-JS-MINIMIST-559764'}
null
{'https://github.com/substack/minimist/commit/4cf1354839cb972e38496d35e12f806eea92c11f#diff-a1e0ee62c91705696ddb71aa30ad4f95', 'https://github.com/substack/minimist/commit/38a4d1caead72ef99e824bb420a2528eec03d9ab', 'https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94'}
{'https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94', 'https://github.com/substack/minimist/commit/4cf1354839cb972e38496d35e12f806eea92c11f#diff-a1e0ee62c91705696ddb71aa30ad4f95', 'https://github.com/substack/minimist/commit/38a4d1caead72ef99e824bb420a2528eec03d9ab'}
GHSA
GHSA-g6wq-qcwm-j5g2
Regular Expression Denial of Service in websocket-extensions (RubyGem)
### Impact The ReDoS flaw allows an attacker to exhaust the server's capacity to process incoming requests by sending a WebSocket handshake request containing a header of the following form: Sec-WebSocket-Extensions: a; b="\c\c\c\c\c\c\c\c\c\c ... That is, a header containing an unclosed string parameter value whose content is a repeating two-byte sequence of a backslash and some other character. The parser takes exponential time to reject this header as invalid, and this will block the processing of any other work on the same thread. Thus if you are running a single-threaded server, such a request can render your service completely unavailable. ### Patches Users should upgrade to version 0.1.5. ### Workarounds There are no known work-arounds other than disabling any public-facing WebSocket functionality you are operating. ### References - https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions/
{'CVE-2020-7663'}
2021-08-25T21:51:51Z
2020-06-05T14:21:29Z
HIGH
8.2
{'CWE-400'}
{'https://snyk.io/vuln/SNYK-RUBY-WEBSOCKETEXTENSIONS-570830', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00031.html', 'https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7663', 'https://usn.ubuntu.com/4502-1/', 'https://github.com/advisories/GHSA-g6wq-qcwm-j5g2', 'https://github.com/faye/websocket-extensions-ruby/security/advisories/GHSA-g6wq-qcwm-j5g2', 'https://github.com/faye/websocket-extensions-ruby/commit/aa156a439da681361ed6f53f1a8131892418838b'}
null
{'https://github.com/faye/websocket-extensions-ruby/commit/aa156a439da681361ed6f53f1a8131892418838b'}
{'https://github.com/faye/websocket-extensions-ruby/commit/aa156a439da681361ed6f53f1a8131892418838b'}
GHSA
GHSA-3f8r-4qwm-r7jf
Improper Authentication in Apache Traffic Control
Improper authentication is possible in Apache Traffic Control versions 3.0.0 and 3.0.1 if LDAP is enabled for login in the Traffic Ops API component. Given a username for a user that can be authenticated via LDAP, it is possible to improperly authenticate as that user without that user's correct password.
{'CVE-2019-12405'}
2021-10-13T17:25:42Z
2021-05-18T15:39:16Z
CRITICAL
9.8
{'CWE-287'}
{'https://github.com/advisories/GHSA-3f8r-4qwm-r7jf', 'https://nvd.nist.gov/vuln/detail/CVE-2019-12405', 'https://lists.apache.org/thread.html/rc8bfd7d4f71d61e9193efcd4699eccbab3c202ec1d75ed9d502f08bf@%3Ccommits.trafficcontrol.apache.org%3E', 'https://lists.apache.org/thread.html/e128e9d382f3b0d074e2b597ac58e1d92139394509d81ddbc9e3700e@%3Cusers.trafficcontrol.apache.org%3E', 'https://lists.apache.org/thread.html/r3c675031ac220b5eae64a9c84a03ee60045c6045738607dca4a96cb8@%3Ccommits.trafficcontrol.apache.org%3E', 'https://support.f5.com/csp/article/K84141859', 'https://support.f5.com/csp/article/K84141859?utm_source=f5support&amp;utm_medium=RSS', 'https://github.com/apache/trafficcontrol/commit/f780aff77a52d52a37b4d1cc3e8e801c0b557356'}
null
{'https://github.com/apache/trafficcontrol/commit/f780aff77a52d52a37b4d1cc3e8e801c0b557356'}
{'https://github.com/apache/trafficcontrol/commit/f780aff77a52d52a37b4d1cc3e8e801c0b557356'}
GHSA
GHSA-2gjg-5x33-mmp2
Path Traversal in localhost-now
Versions of `localhost-now` before 1.0.2 are vulnerable to path traversal. This allows a remote attacker to read the content of an arbitrary file. ## Recommendation Update to version 1.0.2 or later.
{'CVE-2018-3729'}
2021-01-08T20:08:59Z
2018-07-25T22:44:05Z
HIGH
0
{'CWE-22'}
{'https://www.npmjs.com/advisories/582', 'https://hackerone.com/reports/312889', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3729', 'https://github.com/DCKT/localhost-now/commit/30b004c7f145d677df8800a106c2edc982313995#diff-b9cfc7f2cdf78a7f4b91a753d10865a2', 'https://github.com/advisories/GHSA-2gjg-5x33-mmp2'}
null
{'https://github.com/DCKT/localhost-now/commit/30b004c7f145d677df8800a106c2edc982313995#diff-b9cfc7f2cdf78a7f4b91a753d10865a2'}
{'https://github.com/DCKT/localhost-now/commit/30b004c7f145d677df8800a106c2edc982313995#diff-b9cfc7f2cdf78a7f4b91a753d10865a2'}
GHSA
GHSA-gv26-jpj9-c8gq
Incomplete validation in `SparseSparseMinimum`
### Impact Incomplete validation in `SparseAdd` results in allowing attackers to exploit undefined behavior (dereferencing null pointers) as well as write outside of bounds of heap allocated data: ```python import tensorflow as tf a_indices = tf.ones([45, 92], dtype=tf.int64) a_values = tf.ones([45], dtype=tf.int64) a_shape = tf.ones([1], dtype=tf.int64) b_indices = tf.ones([1, 1], dtype=tf.int64) b_values = tf.ones([1], dtype=tf.int64) b_shape = tf.ones([1], dtype=tf.int64) tf.raw_ops.SparseSparseMinimum(a_indices=a_indices, a_values=a_values, a_shape=a_shape, b_indices=b_indices, b_values=b_values, b_shape=b_shape) ``` The [implementation](https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/sparse_sparse_binary_op_shared.cc) has a large set of validation for the two sparse tensor inputs (6 tensors in total), but does not validate that the tensors are not empty or that the second dimension of `*_indices` matches the size of corresponding `*_shape`. This allows attackers to send tensor triples that represent invalid sparse tensors to abuse code assumptions that are not protected by validation. ### Patches We have patched the issue in GitHub commit [ba6822bd7b7324ba201a28b2f278c29a98edbef2](https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2) followed by GitHub commit [f6fde895ef9c77d848061c0517f19d0ec2682f3a](https://github.com/tensorflow/tensorflow/commit/f6fde895ef9c77d848061c0517f19d0ec2682f3a). The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.
{'CVE-2021-29607'}
2022-03-21T20:38:04Z
2022-03-18T17:52:25Z
MODERATE
5.3
{'CWE-754'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-29607', 'https://github.com/advisories/GHSA-gv26-jpj9-c8gq', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gv26-jpj9-c8gq', 'https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2', 'https://github.com/tensorflow/tensorflow/commit/f6fde895ef9c77d848061c0517f19d0ec2682f3a'}
null
{'https://github.com/tensorflow/tensorflow/commit/f6fde895ef9c77d848061c0517f19d0ec2682f3a', 'https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2'}
{'https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2', 'https://github.com/tensorflow/tensorflow/commit/f6fde895ef9c77d848061c0517f19d0ec2682f3a'}
GHSA
GHSA-73xv-w5gp-frxh
Logic error in Legion of the Bouncy Castle BC Java
An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password, allowing incorrect passwords to indicate they were matching with previously hashed ones that were different.
{'CVE-2020-28052'}
2022-04-22T17:24:18Z
2021-04-30T16:14:15Z
HIGH
8.1
{'CWE-670'}
{'https://www.bouncycastle.org/releasenotes.html', 'https://lists.apache.org/thread.html/rf9abfc0223747a56694825c050cc6b66627a293a32ea926b3de22402@%3Cissues.karaf.apache.org%3E', 'https://lists.apache.org/thread.html/rdfd2901b8b697a3f6e2c9c6ecc688fd90d7f881937affb5144d61d6e@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rfc0db1f3c375087e69a239f9284ded72d04fbb55849eadde58fa9dc2@%3Cissues.karaf.apache.org%3E', 'https://lists.apache.org/thread.html/rdcbad6d8ce72c79827ed8c635f9a62dd919bb21c94a0b64cab2efc31@%3Cissues.karaf.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.apache.org/thread.html/r77af3ac7c3bfbd5454546e13faf7aec21d627bdcf36c9ca240436b94@%3Cissues.karaf.apache.org%3E', 'https://github.com/bcgit/bc-java/wiki/CVE-2020-28052', 'https://github.com/advisories/GHSA-73xv-w5gp-frxh', 'https://lists.apache.org/thread.html/r25d53acd06f29244b8a103781b0339c5e7efee9099a4d52f0c230e4a@%3Ccommits.druid.apache.org%3E', 'https://github.com/bcgit/bc-java/commit/97578f9b7ed277e6ecb58834e85e3d18385a4219', 'https://lists.apache.org/thread.html/rc9e441c1576bdc4375d32526d5cf457226928e9c87b9f54ded26271c@%3Cissues.karaf.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://lists.apache.org/thread.html/rcd37d9214b08067a2e8f2b5b4fd123a1f8cb6008698d11ef44028c21@%3Cissues.karaf.apache.org%3E', 'https://lists.apache.org/thread.html/r954d80fd18e9dafef6e813963eb7e08c228151c2b6268ecd63b35d1f@%3Ccommits.druid.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.apache.org/thread.html/r167dbc42ef7c59802c2ca1ac14735ef9cf687c25208229993d6206fe@%3Cissues.karaf.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28052', 'https://lists.apache.org/thread.html/r8c36ba34e80e05eecb1f80071cc834d705616f315b634ec0c7d8f42e@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r175f5a25d100dbe2b1bd3459b3ce882a84c3ff91b120ed4ff2d57b53@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/rddd2237b8636a48d573869006ee809262525efb2b6ffa6eff50d2a2d@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r37d332c0bf772f4982d1fdeeb2f88dd71dab6451213e69e43734eadc@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r2ddabd06d94b60cfb0141e4abb23201c628ab925e30742f61a04d013@%3Cissues.karaf.apache.org%3E', 'https://www.synopsys.com/blogs/software-security/cve-2020-28052-bouncy-castle/', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r30a139c165b3da6e0d5536434ab1550534011b1fdfcd2f5d95892c5b@%3Cissues.karaf.apache.org%3E', 'https://lists.apache.org/thread.html/r4e1619cfefcd031fac62064a3858f5c9229eef907bd5d8ef14c594fc@%3Cissues.karaf.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html'}
null
{'https://github.com/bcgit/bc-java/commit/97578f9b7ed277e6ecb58834e85e3d18385a4219'}
{'https://github.com/bcgit/bc-java/commit/97578f9b7ed277e6ecb58834e85e3d18385a4219'}
GHSA
GHSA-r7c9-c69m-rph8
Code Injection in PHPUnit
Util/PHP/eval-stdin.php in PHPUnit starting with 4.8.19 and before 4.8.28, as well as 5.x before 5.6.3, allows remote attackers to execute arbitrary PHP code via HTTP POST data beginning with a `<?php ` substring, as demonstrated by an attack on a site with an exposed /vendor folder, i.e., external access to the /vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php URI.
{'CVE-2017-9841'}
2022-04-19T20:16:50Z
2022-03-26T00:19:30Z
CRITICAL
9.8
{'CWE-94'}
{'http://www.securitytracker.com/id/1039812', 'http://web.archive.org/web/20170701212357/', 'https://github.com/sebastianbergmann/phpunit/commit/284a69fb88a2d0845d23f42974a583d8f59bf5a5', 'https://github.com/sebastianbergmann/phpunit/pull/1955', 'https://github.com/advisories/GHSA-r7c9-c69m-rph8', 'http://', 'https://github.com/sebastianbergmann/phpunit/pull/1956', 'https://nvd.nist.gov/vuln/detail/CVE-2017-9841', 'https://github.com/sebastianbergmann/phpunit/commit/3aaddb1c5bd9b9b8d070b4cf120e71c36fd08412', 'https://security.gentoo.org/glsa/201711-15', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'http://www.securityfocus.com/bid/101798', 'http://phpunit.vulnbusters.com/'}
null
{'https://github.com/sebastianbergmann/phpunit/commit/284a69fb88a2d0845d23f42974a583d8f59bf5a5', 'https://github.com/sebastianbergmann/phpunit/commit/3aaddb1c5bd9b9b8d070b4cf120e71c36fd08412'}
{'https://github.com/sebastianbergmann/phpunit/commit/3aaddb1c5bd9b9b8d070b4cf120e71c36fd08412', 'https://github.com/sebastianbergmann/phpunit/commit/284a69fb88a2d0845d23f42974a583d8f59bf5a5'}
GHSA
GHSA-8j3f-mhq8-gmh4
Reject unauthorized access with GitHub PATs
### Impact _What kind of vulnerability is it? Who is impacted?_ The additional auth mechanism added within https://github.com/go-vela/server/pull/246 enables some malicious user to obtain secrets utilizing the injected credentials within the `~/.netrc` file. Steps to reproduce 1. Create Vela server 2. Login to Vela UI 3. Promote yourself to Vela administrator - `UPDATE users SET admin = 't' WHERE name = <username>` 4. Activate repository within Vela 5. Add `.vela.yml` to the repository with the following content ```yaml version: "1" steps: - name: steal image: alpine commands: - cat ~/.netrc ``` 1. Look at build logs to find the following content ``` $ cat ~/.netrc machine <GITHUB URL> login x-oauth-basic password <token> ``` 1. Copy the password to be utilized in some later step 1. Add secret(s) to activated repo 1. Copy the following script into `main.go` ```golang package main import ( "fmt" "github.com/go-vela/sdk-go/vela" "os" ) func main() { // create client to connect to vela client, err := vela.NewClient(os.Getenv("VELA_SERVER_ADDR"), "vela", nil) if err != nil { panic(err) } // add PAT to request client.Authentication.SetPersonalAccessTokenAuth(os.Getenv("VELA_TOKEN")) secrets, _, err := client.Admin.Secret.GetAll(&vela.ListOptions{}) if err != nil { panic(err) } for _, secret := range *secrets { fmt.Println(*secret.Name) fmt.Println(*secret.Value) } } ``` 1. Run the `main.go` with environment specific settings - `VELA_SERVER_ADDR=http://localhost:8080 VELA_TOKEN=<token obtained previously> go run main.go` The previously posted script could be updated to utilize any API endpoint(s) the activated user has access against. ### Patches _Has the problem been patched? What versions should users upgrade to?_ * Upgrade to `v0.7.5` or later ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ * No known workarounds ### References _Are there any links users can visit to find out more?_ * https://github.com/go-vela/server/pull/246 * https://docs.github.com/en/enterprise-server@3.0/rest/reference/apps#check-a-token ### For more information If you have any questions or comments about this advisory * Email us at [vela@target.com](mailto:vela@target.com)
{'CVE-2021-21432'}
2022-04-19T19:02:53Z
2022-02-15T01:57:18Z
HIGH
7.5
{'CWE-863', 'CWE-285'}
{'https://github.com/go-vela/server/pull/337', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21432', 'https://github.com/go-vela/server/releases/tag/v0.7.5', 'https://pkg.go.dev/github.com/go-vela/server', 'https://github.com/advisories/GHSA-8j3f-mhq8-gmh4', 'https://github.com/go-vela/server/security/advisories/GHSA-8j3f-mhq8-gmh4', 'https://github.com/go-vela/server/commit/cb4352918b8ecace9fe969b90404d337b0744d46'}
null
{'https://github.com/go-vela/server/commit/cb4352918b8ecace9fe969b90404d337b0744d46'}
{'https://github.com/go-vela/server/commit/cb4352918b8ecace9fe969b90404d337b0744d46'}
GHSA
GHSA-c36v-fmgq-m8hx
Prototype Pollution in immer
immer is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
{'CVE-2021-3757'}
2021-09-13T20:32:41Z
2021-09-07T22:57:14Z
HIGH
7.5
{'CWE-1321', 'CWE-915'}
{'https://github.com/immerjs/immer/commit/fa671e55ee9bd42ae08cc239102b665a23958237', 'https://github.com/advisories/GHSA-c36v-fmgq-m8hx', 'https://huntr.dev/bounties/23d38099-71cd-42ed-a77a-71e68094adfa', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3757'}
null
{'https://github.com/immerjs/immer/commit/fa671e55ee9bd42ae08cc239102b665a23958237'}
{'https://github.com/immerjs/immer/commit/fa671e55ee9bd42ae08cc239102b665a23958237'}
GHSA
GHSA-vwhc-pww7-72x6
Code Injection in total.js
Total.js framework (npm package total.js) is a framework for Node.js platfrom written in pure JavaScript similar to PHP's Laravel or Python's Django or ASP.NET MVC. In total.js framework before version 3.4.9, calling the utils.set function with user-controlled values leads to code-injection. This can cause a variety of impacts that include arbitrary code execution. This is fixed in version 3.4.9.
{'CVE-2021-32831'}
2021-09-01T18:24:05Z
2021-09-01T18:24:05Z
HIGH
7.5
{'CWE-94'}
{'https://www.npmjs.com/package/total.js', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32831', 'https://securitylab.github.com/advisories/GHSL-2021-066-totaljs-totaljs/', 'https://github.com/totaljs/framework/blob/e644167d5378afdc45cb0156190349b2c07ef235/changes.txt#L11', 'https://github.com/advisories/GHSA-vwhc-pww7-72x6', 'https://github.com/totaljs/framework/commit/887b0fa9e162ef7a2dd9cec20a5ca122726373b3'}
null
{'https://github.com/totaljs/framework/commit/887b0fa9e162ef7a2dd9cec20a5ca122726373b3'}
{'https://github.com/totaljs/framework/commit/887b0fa9e162ef7a2dd9cec20a5ca122726373b3'}
GHSA
GHSA-959q-32g8-vvp7
Moderate severity vulnerability that affects org.keycloak:keycloak-core
It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attacks.
{'CVE-2017-12161'}
2021-01-08T19:05:50Z
2018-10-18T16:50:05Z
MODERATE
0
{'CWE-602'}
{'https://github.com/advisories/GHSA-959q-32g8-vvp7', 'https://bugzilla.redhat.com/show_bug.cgi?id=1484564', 'https://github.com/keycloak/keycloak-documentation/pull/268/commits/a2b58aadee42af2c375b72e86dffc2cf23cc3770', 'https://nvd.nist.gov/vuln/detail/CVE-2017-12161'}
null
{'https://github.com/keycloak/keycloak-documentation/pull/268/commits/a2b58aadee42af2c375b72e86dffc2cf23cc3770'}
{'https://github.com/keycloak/keycloak-documentation/pull/268/commits/a2b58aadee42af2c375b72e86dffc2cf23cc3770'}
GHSA
GHSA-h9ph-jcgh-gf69
Cross-site Scripting in Limesurvey
The "File upload question" functionality in LimeSurvey 3.x-LTS through 3.27.18 allows XSS in assets/scripts/modaldialog.js and assets/scripts/uploader.js.
{'CVE-2021-42112'}
2021-11-17T21:26:06Z
2021-10-12T16:40:28Z
MODERATE
6.1
{'CWE-79'}
{'https://www.on-x.com/sites/default/files/on-x_-_security_advisory_-_limesurvey_-_cve-2021-42112.pdf', 'https://github.com/advisories/GHSA-h9ph-jcgh-gf69', 'https://github.com/LimeSurvey/LimeSurvey/commit/d56619a50cfd191bbffd0adb660638a5e438070d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42112', 'https://github.com/LimeSurvey/LimeSurvey/pull/2044', 'https://bugs.limesurvey.org/view.php?id=17562'}
null
{'https://github.com/LimeSurvey/LimeSurvey/commit/d56619a50cfd191bbffd0adb660638a5e438070d'}
{'https://github.com/LimeSurvey/LimeSurvey/commit/d56619a50cfd191bbffd0adb660638a5e438070d'}
GHSA
GHSA-fc42-h7q4-qp8h
Command Injection in killport
This affects the package killport before 1.0.2. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization. Running this PoC will cause the command touch success to be executed, leading to the creation of a file called success.
{'CVE-2021-23360'}
2021-04-13T15:16:20Z
2021-04-13T15:16:20Z
HIGH
7.5
{'CWE-77'}
{'https://github.com/advisories/GHSA-fc42-h7q4-qp8h', 'https://github.com/ssnau/killport/blob/5268f23ea8f152e47182b263d8f7ef20c12a9f28/index.js%23L9', 'https://github.com/ssnau/killport/commit/bec8e371f170a12e11cd222ffc7a6e1ae9942638', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23360', 'https://snyk.io/vuln/SNYK-JS-KILLPORT-1078535'}
null
{'https://github.com/ssnau/killport/commit/bec8e371f170a12e11cd222ffc7a6e1ae9942638'}
{'https://github.com/ssnau/killport/commit/bec8e371f170a12e11cd222ffc7a6e1ae9942638'}
GHSA
GHSA-frxp-xxx8-hrg6
Missing Authorization in DayByDay CRM
In Daybyday CRM, versions 2.0.0 through 2.2.0 are vulnerable to Missing Authorization. An attacker that has the lowest privileges account (employee type user), can view the absences of all users in the system including administrators. This type of user is not authorized to view this kind of information.
{'CVE-2022-22108'}
2022-01-08T00:31:52Z
2022-01-08T00:31:52Z
MODERATE
4.3
{'CWE-862'}
{'https://github.com/advisories/GHSA-frxp-xxx8-hrg6', 'https://github.com/Bottelet/DaybydayCRM/commit/fe842ea5ede237443f1f45a99aeb839133115d8b', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2022-22108', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22108'}
null
{'https://github.com/Bottelet/DaybydayCRM/commit/fe842ea5ede237443f1f45a99aeb839133115d8b'}
{'https://github.com/Bottelet/DaybydayCRM/commit/fe842ea5ede237443f1f45a99aeb839133115d8b'}
GHSA
GHSA-7ph6-5cmq-xgjq
Path traversal in xwiki-platform-skin-skinx
### Impact AbstractSxExportURLFactoryActionHandler#processSx does not escape anything from SSX document reference when serializing it on filesystem, so it's easy to mess up the HTML export process with reference elements containing filesystem syntax like "../", "./". or "/" in general (the last two not causing any security threat, but can cause conflicts with others serialized files). ### Patches Fixed in 13.6-rc-1 ### Workarounds * giving script or subwiki admin right only to trusted people * disabling HTML/PDF export ### References https://jira.xwiki.org/browse/XWIKI-18819 ### For more information If you have any questions or comments about this advisory: * Open an issue in [JIRA](https://jira.xwiki.org) * Email us at [XWiki Security Mailing list](mailto:security@xwiki.org)
{'CVE-2022-23620'}
2022-02-11T15:00:33Z
2022-02-09T21:53:29Z
MODERATE
6.8
{'CWE-22'}
{'https://github.com/advisories/GHSA-7ph6-5cmq-xgjq', 'https://jira.xwiki.org/browse/XWIKI-18819', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23620', 'https://github.com/xwiki/xwiki-platform/commit/ab778254fb8f71c774e1c1239368c44fe3b6bba5', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-7ph6-5cmq-xgjq'}
null
{'https://github.com/xwiki/xwiki-platform/commit/ab778254fb8f71c774e1c1239368c44fe3b6bba5'}
{'https://github.com/xwiki/xwiki-platform/commit/ab778254fb8f71c774e1c1239368c44fe3b6bba5'}
GHSA
GHSA-v3jv-wrf4-5845
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
{'CVE-2013-4116'}
2021-09-23T21:38:19Z
2020-09-01T16:03:34Z
LOW
0
{'CWE-59'}
{'https://github.com/advisories/GHSA-v3jv-wrf4-5845', 'https://nvd.nist.gov/vuln/detail/CVE-2013-4116', 'https://bugzilla.redhat.com/show_bug.cgi?id=983917', 'https://github.com/npm/npm/commit/f4d31693', 'https://github.com/npm/npm/issues/3635', 'http://www.openwall.com/lists/oss-security/2013/07/10/17', 'https://www.npmjs.com/advisories/152', 'http://www.openwall.com/lists/oss-security/2013/07/11/9', 'http://www.securityfocus.com/bid/61083', 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715325', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/87141'}
null
{'https://github.com/npm/npm/commit/f4d31693'}
{'https://github.com/npm/npm/commit/f4d31693'}
GHSA
GHSA-5pg7-v24c-9rp9
Prototype pollution in controlled-merge
Prototype pollution vulnerability in 'controlled-merge' versions 1.0.0 through 1.2.0 allows attacker to cause a denial of service and may lead to remote code execution.
{'CVE-2020-28268'}
2021-07-28T22:07:01Z
2021-05-18T01:53:46Z
HIGH
7.5
{'CWE-1321'}
{'https://www.npmjs.com/package/controlled-merge', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28268', 'https://github.com/hlfshell/controlled-merge/commit/5a4b2e9ffe5a0be7f8843d4ab038599d3ae5f9d4', 'https://github.com/advisories/GHSA-5pg7-v24c-9rp9', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28268'}
null
{'https://github.com/hlfshell/controlled-merge/commit/5a4b2e9ffe5a0be7f8843d4ab038599d3ae5f9d4'}
{'https://github.com/hlfshell/controlled-merge/commit/5a4b2e9ffe5a0be7f8843d4ab038599d3ae5f9d4'}
GHSA
GHSA-f7q6-xxph-mfm8
Cross-site Scripting in Pimcore
Pimcore prior to version 10.2.10 contains a cross-site scripting vulnerability.
{'CVE-2022-0251'}
2022-02-10T22:24:52Z
2022-01-27T00:01:26Z
MODERATE
5.4
{'CWE-79'}
{'https://github.com/advisories/GHSA-f7q6-xxph-mfm8', 'https://github.com/pimcore/pimcore/commit/3ae96b9d41c117aafa45873ad10077d4b873a3cb', 'https://huntr.dev/bounties/eb4b08f9-cf8b-4335-b3b8-ed44e5fa80a5', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0251'}
null
{'https://github.com/pimcore/pimcore/commit/3ae96b9d41c117aafa45873ad10077d4b873a3cb'}
{'https://github.com/pimcore/pimcore/commit/3ae96b9d41c117aafa45873ad10077d4b873a3cb'}
GHSA
GHSA-m3xv-x3ph-mq22
Server-side Template Injection in nystudio107/craft-seomatic
A Server-side Template Injection (SSTI) vulnerability exists in Nystudio107 Seomatic prior to 3.4.12 in src/helpers/UrlHelper.php via the host header.
{'CVE-2021-44618'}
2022-03-24T13:44:50Z
2022-03-12T00:00:34Z
HIGH
9.8
{'CWE-94'}
{'https://github.com/nystudio107/craft-seomatic/commit/0c5c0c0e0cb61000d12ec55ebf174745a5bf6469', 'https://github.com/advisories/GHSA-m3xv-x3ph-mq22', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44618', 'https://github.com/nystudio107/craft-seomatic/releases/tag/3.4.12'}
null
{'https://github.com/nystudio107/craft-seomatic/commit/0c5c0c0e0cb61000d12ec55ebf174745a5bf6469'}
{'https://github.com/nystudio107/craft-seomatic/commit/0c5c0c0e0cb61000d12ec55ebf174745a5bf6469'}
GHSA
GHSA-p43w-g3c5-g5mq
Out of bounds read in Pillow
An issue was discovered in Pillow before 8.1.1. There is an out-of-bounds read in SGIRleDecode.c.
{'CVE-2021-25293'}
2021-12-02T15:31:01Z
2021-03-29T16:35:27Z
HIGH
7.5
{'CWE-125'}
{'https://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html', 'https://github.com/advisories/GHSA-p43w-g3c5-g5mq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25293', 'https://security.gentoo.org/glsa/202107-33', 'https://github.com/python-pillow/Pillow/commit/4853e522bddbec66022c0915b9a56255d0188bf9'}
null
{'https://github.com/python-pillow/Pillow/commit/4853e522bddbec66022c0915b9a56255d0188bf9'}
{'https://github.com/python-pillow/Pillow/commit/4853e522bddbec66022c0915b9a56255d0188bf9'}
GHSA
GHSA-4fcw-pq4r-f4q7
Server-Side Request Forgery in Spinnaker Orca
The Spinnaker template resolution functionality is vulnerable to Server-Side Request Forgery (SSRF), which allows an attacker to send requests on behalf of Spinnaker potentially leading to sensitive data disclosure.
{'CVE-2020-9298'}
2021-05-07T15:54:31Z
2021-05-07T15:54:31Z
HIGH
7.5
{'CWE-918'}
{'https://github.com/advisories/GHSA-4fcw-pq4r-f4q7', 'https://github.com/Netflix/security-bulletins/blob/master/advisories/nflx-2020-003.md', 'https://github.com/spinnaker/orca/releases/tag/v8.7.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9298', 'https://github.com/spinnaker/orca/pull/3706/commits/4f3c07da8fcacd67bb1984aef11b2066f2c0d11c'}
null
{'https://github.com/spinnaker/orca/pull/3706/commits/4f3c07da8fcacd67bb1984aef11b2066f2c0d11c'}
{'https://github.com/spinnaker/orca/pull/3706/commits/4f3c07da8fcacd67bb1984aef11b2066f2c0d11c'}
GHSA
GHSA-c7fh-chf7-jr5x
ReDOS in Vfsjfilechooser2
A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Vfsjfilechooser2 which occurs when the application attempts to validate crafted URIs.
{'CVE-2021-29061'}
2022-01-06T18:44:27Z
2022-01-06T18:44:27Z
HIGH
7.5
{'CWE-770'}
{'https://github.com/fracpete/vfsjfilechooser2/issues/7', 'https://github.com/fracpete/vfsjfilechooser2/commit/9c9f2c317f3de5ece60a3ae28c371e9796e3909b', 'https://github.com/fracpete/vfsjfilechooser2/releases/tag/vfsjfilechooser2-0.2.9', 'https://github.com/yetingli/PoCs/blob/main/CVE-2021-29061/Vfsjfilechooser2.md', 'https://github.com/advisories/GHSA-c7fh-chf7-jr5x', 'https://github.com/yetingli/SaveResults/blob/main/md/vfsjfilechooser2.md', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29061'}
null
{'https://github.com/fracpete/vfsjfilechooser2/commit/9c9f2c317f3de5ece60a3ae28c371e9796e3909b'}
{'https://github.com/fracpete/vfsjfilechooser2/commit/9c9f2c317f3de5ece60a3ae28c371e9796e3909b'}
GHSA
GHSA-cmc7-mfmr-xqrx
Logic error in authentication in proxy.py
before_upstream_connection in AuthPlugin in http/proxy/auth.py in proxy.py before 2.3.1 accepts incorrect Proxy-Authorization header data because of a boolean confusion (and versus or).
{'CVE-2021-3116'}
2021-04-07T21:01:25Z
2021-04-07T21:01:25Z
HIGH
7.5
{'CWE-287', 'CWE-480'}
{'https://github.com/abhinavsingh/proxy.py/pull/482/commits/9b00093288237f5073c403f2c4f62acfdfa8ed46', 'https://cardaci.xyz/advisories/2021/01/10/proxy.py-2.3.0-broken-basic-authentication/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3116', 'https://pypi.org/project/proxy.py/2.3.1/#history', 'https://github.com/advisories/GHSA-cmc7-mfmr-xqrx'}
null
{'https://github.com/abhinavsingh/proxy.py/pull/482/commits/9b00093288237f5073c403f2c4f62acfdfa8ed46'}
{'https://github.com/abhinavsingh/proxy.py/pull/482/commits/9b00093288237f5073c403f2c4f62acfdfa8ed46'}
GHSA
GHSA-2xwq-h7r9-6w27
Cross-site Scripting in kimai2
Cross site request forgery vulnerability is present in delete functionality of doctor feature. This vulnerability is capable of deleting system logs
{'CVE-2021-3957'}
2021-11-23T17:59:40Z
2021-11-23T17:59:40Z
MODERATE
4.6
{'CWE-352'}
{'https://github.com/kevinpapst/kimai2/commit/6b49535b523dcd36ec59462ee4e67e2b3a9151f3', 'https://huntr.dev/bounties/5fa3098a-ba02-45e0-af56-645e34dbc691', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3957', 'https://github.com/advisories/GHSA-2xwq-h7r9-6w27'}
null
{'https://github.com/kevinpapst/kimai2/commit/6b49535b523dcd36ec59462ee4e67e2b3a9151f3'}
{'https://github.com/kevinpapst/kimai2/commit/6b49535b523dcd36ec59462ee4e67e2b3a9151f3'}
GHSA
GHSA-q8qj-fc9q-cphr
Undefined behavior in Tensorflow
### Impact If a user passes an invalid argument to `dlpack.to_dlpack` the expected validations will cause variables to bind to `nullptr` while setting a `status` variable to the error condition. However, this `status` argument is not properly checked: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267 Hence, code following these methods will bind references to null pointers: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L279-L285 This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. ### Patches We have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions. We recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1. ### 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 discovered during variant analysis of [GHSA-rjjg-hgv6-h69v](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v).
{'CVE-2020-15191'}
2021-11-19T15:19:57Z
2020-09-25T18:28:25Z
MODERATE
5.3
{'CWE-252', 'CWE-20', 'CWE-476'}
{'https://github.com/advisories/GHSA-q8qj-fc9q-cphr', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15191', 'https://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'}
null
{'https://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8'}
{'https://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8'}
GHSA
GHSA-cvh5-p6r6-g2qc
Exposed phpinfo() leadked via documentation files
### Impact The `phpinfo()` can be exposed if the `/vendor` is not protected from public access. This is a rare situation today since the vendor directory is often located outside the web directory or protected via server rule (.htaccess, etc). ### Patches Only the v6, v7 and v8 will be patched respectively in 8.0.7, 7.1.2, 6.1.5. Older versions such as v5, v4 are not longer supported and will **NOT** be patched. ### Workarounds Protect the `/vendor` directory from public access. ### References The first issue revealing this vulnerability is located here: https://github.com/flextype/flextype/issues/567 V6 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/815 V7 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/814 V8 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/813 ### For more information If you have any questions or comments about this advisory: * Open an issue in [our issue tracker](https://github.com/PHPSocialNetwork/phpfastcache/issues) * Email us at [security@geolim4.com](mailto:security@geolim4.com)
{'CVE-2021-37704'}
2021-08-30T16:13:40Z
2021-08-30T16:13:40Z
MODERATE
5.4
{'CWE-200', 'CWE-668'}
{'https://github.com/PHPSocialNetwork/phpfastcache/pull/814', 'https://github.com/PHPSocialNetwork/phpfastcache/commit/41a77d0d8f126dbd6fbedcd9e6a82e86cdaafa51', 'https://github.com/flextype/flextype/issues/567', 'https://github.com/advisories/GHSA-cvh5-p6r6-g2qc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37704', 'https://packagist.org/packages/phpfastcache/phpfastcache', 'https://github.com/PHPSocialNetwork/phpfastcache/pull/813', 'https://github.com/PHPSocialNetwork/phpfastcache/pull/815', 'https://github.com/PHPSocialNetwork/phpfastcache/security/advisories/GHSA-cvh5-p6r6-g2qc', 'https://github.com/PHPSocialNetwork/phpfastcache/blob/master/CHANGELOG.md#807'}
null
{'https://github.com/PHPSocialNetwork/phpfastcache/commit/41a77d0d8f126dbd6fbedcd9e6a82e86cdaafa51'}
{'https://github.com/PHPSocialNetwork/phpfastcache/commit/41a77d0d8f126dbd6fbedcd9e6a82e86cdaafa51'}
GHSA
GHSA-gcx2-gvj7-pxv3
Insufficient Protection against HTTP Request Smuggling in mitmproxy
### Impact In mitmproxy 7.0.4 and below, a malicious client or server is able to perform [HTTP request smuggling](https://en.wikipedia.org/wiki/HTTP_request_smuggling) attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless you use mitmproxy to protect an HTTP/1 service, no action is required. ### Patches The vulnerability has been fixed in mitmproxy 8.0.0 and above. ### Acknowledgements We thank Zeyu Zhang (@zeyu2001) for responsibly disclosing this vulnerability to the mitmproxy team. ### Timeline - **2022-03-15**: Received initial report. - **2022-03-15**: Verified report and confirmed receipt. - **2022-03-16**: Shared patch with researcher. - **2022-03-16**: Received confirmation that patch is working. - **2022-03-19**: Published patched release and advisory.
{'CVE-2022-24766'}
2022-03-22T19:32:46Z
2022-03-22T19:22:59Z
CRITICAL
9.8
{'CWE-444'}
{'https://github.com/advisories/GHSA-gcx2-gvj7-pxv3', 'https://github.com/mitmproxy/mitmproxy/commit/b06fb6d157087d526bd02e7aadbe37c56865c71b', 'https://mitmproxy.org/posts/releases/mitmproxy8/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24766', 'https://github.com/mitmproxy/mitmproxy/security/advisories/GHSA-gcx2-gvj7-pxv3'}
null
{'https://github.com/mitmproxy/mitmproxy/commit/b06fb6d157087d526bd02e7aadbe37c56865c71b'}
{'https://github.com/mitmproxy/mitmproxy/commit/b06fb6d157087d526bd02e7aadbe37c56865c71b'}
GHSA
GHSA-52qp-gwwh-qrg4
Missing Handler in @scandipwa/magento-scripts
### Impact After changing the function from synchronous to asynchronous there wasn't implemented handler in the [start](https://docs.create-magento-app.com/getting-started/available-commands/start), [stop](https://docs.create-magento-app.com/getting-started/available-commands/stop), [exec](https://docs.create-magento-app.com/getting-started/available-commands/exec) and [logs](https://docs.create-magento-app.com/getting-started/available-commands/logs) commands, effectively making them unusable. ### Patches [Version 1.5.3](https://github.com/scandipwa/create-magento-app/releases/tag/%40scandipwa%2Fmagento-scripts%401.5.3) contains patches for the problems described above. ### Workarounds Upgrade to patched or latest (recommended) version `npm i @scandipwa/magento-scripts@1.5.3` or `npm i @scandipwa/magento-scripts@latest`. ### References New releases always available here: https://github.com/scandipwa/create-magento-app/releases ### For more information If you have any questions or comments about this advisory: * Open an issue in [create-magento-app](https://github.com/scandipwa/create-magento-app/issues)
{'CVE-2021-32684'}
2021-06-21T17:10:02Z
2021-06-21T17:10:02Z
MODERATE
6.2
{'CWE-670'}
{'https://github.com/scandipwa/create-magento-app/security/advisories/GHSA-52qp-gwwh-qrg4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32684', 'https://github.com/advisories/GHSA-52qp-gwwh-qrg4', 'https://github.com/scandipwa/create-magento-app/commit/89115db7031e181eb8fb4ec2822bc6cab88e7071'}
null
{'https://github.com/scandipwa/create-magento-app/commit/89115db7031e181eb8fb4ec2822bc6cab88e7071'}
{'https://github.com/scandipwa/create-magento-app/commit/89115db7031e181eb8fb4ec2822bc6cab88e7071'}
GHSA
GHSA-5v95-v8c8-3rh6
Privilege escalation in rbac
### Impact Using a carefully crafted request or malicious proxy, a user with `UserWrite` permissions could create another user with higher privileges than their own due to insufficient checks on the allowed set of permissions. The event would be captured in the Event Log. ### Patches The issue has been fixed in 0.24.0 and 0.23.1. ### Workarounds For users who are unable to upgrade, we recommend auditing users who have `UserWrite` permissions and regularly reviewing the Event Log for malicious activity. ### Kudos Thank you to Michael Mazzolini (Ethical Hacker at WHO) for finding and disclosing this vulnerability.
{'CVE-2021-22538'}
2021-05-21T14:32:55Z
2021-05-21T14:32:55Z
HIGH
8.8
{'CWE-276'}
{'https://github.com/advisories/GHSA-5v95-v8c8-3rh6', 'https://github.com/google/exposure-notifications-verification-server/security/advisories/GHSA-5v95-v8c8-3rh6', 'https://github.com/google/exposure-notifications-verification-server/releases/tag/v0.24.0', 'https://github.com/google/exposure-notifications-verification-server/releases/tag/v0.23.1', 'https://github.com/google/exposure-notifications-verification-server/commit/eb8cf40b12dbe79304f1133c06fb73419383cd95', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22538'}
null
{'https://github.com/google/exposure-notifications-verification-server/commit/eb8cf40b12dbe79304f1133c06fb73419383cd95'}
{'https://github.com/google/exposure-notifications-verification-server/commit/eb8cf40b12dbe79304f1133c06fb73419383cd95'}
GHSA
GHSA-7cj4-gj8m-m2f7
Authentication bypass in Apache Shiro
Apache Shiro before 1.7.0, when using Apache Shiro with Spring, a specially crafted HTTP request may cause an authentication bypass.
{'CVE-2020-17510'}
2021-08-31T21:06:40Z
2021-04-22T16:13:23Z
CRITICAL
9.8
{'CWE-287'}
{'https://github.com/advisories/GHSA-7cj4-gj8m-m2f7', 'https://lists.apache.org/thread.html/r575301804bfac87a064359cf4b4ae9d514f2d10db7d44120765f4129@%3Cdev.shiro.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/08/msg00002.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17510', 'https://lists.apache.org/thread.html/rc2cff2538b683d480426393eecf1ce8dd80e052fbef49303b4f47171%40%3Cdev.shiro.apache.org%3E', 'https://github.com/apache/shiro/commit/dc194fc977ab6cfbf3c1ecb085e2bac5db14af6d', 'https://lists.apache.org/thread.html/rb47d88af224e396ee34ffb88ee99fb6d04510de5722cf14b7137e6bc@%3Cdev.shiro.apache.org%3E', 'https://lists.apache.org/thread.html/r70098e336d02047ce4d4e69293fe8d558cd68cde06f6430398959bc4@%3Cdev.shiro.apache.org%3E', 'https://lists.apache.org/thread.html/re25b8317b00a50272a7252c4552cf1a81a97984cc2111ef7728e48e0@%3Cdev.shiro.apache.org%3E', 'https://lists.apache.org/thread.html/r852971e28f54cafa7d325bd7033115c67d613b112a2a1076817390ac@%3Cdev.shiro.apache.org%3E', 'https://lists.apache.org/thread.html/r9d93dfb5df016b1a71a808486bc8f9fbafebbdbc8533625f91253f1d@%3Cdev.shiro.apache.org%3E', 'https://lists.apache.org/thread.html/r95bdf3703858b5f958b5e190d747421771b430d97095880db91980d6@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/r70b907ccb306e9391145e2b10f56cc6914a245f91720a17a486c020a@%3Cdev.shiro.apache.org%3E'}
null
{'https://github.com/apache/shiro/commit/dc194fc977ab6cfbf3c1ecb085e2bac5db14af6d'}
{'https://github.com/apache/shiro/commit/dc194fc977ab6cfbf3c1ecb085e2bac5db14af6d'}
GHSA
GHSA-54qq-9chj-rxhv
Cross-site Scripting in LiveHelperChat
LiveHelperChat prior to version 3.93 contains a cross-site scripting vulnerability.
{'CVE-2022-0395'}
2022-02-10T22:25:23Z
2022-01-29T00:00:33Z
MODERATE
5.4
{'CWE-79'}
{'https://huntr.dev/bounties/36abbd6e-239e-4739-8c77-ba212b946a4a', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0395', 'https://github.com/advisories/GHSA-54qq-9chj-rxhv', 'https://github.com/livehelperchat/livehelperchat/commit/8fdb4f67ac1a095331aa0fb4630ef9dfe8e75dcb'}
null
{'https://github.com/livehelperchat/livehelperchat/commit/8fdb4f67ac1a095331aa0fb4630ef9dfe8e75dcb'}
{'https://github.com/livehelperchat/livehelperchat/commit/8fdb4f67ac1a095331aa0fb4630ef9dfe8e75dcb'}
GHSA
GHSA-8phj-f9w2-cjcc
Arbitrary file reading vulnerability in Aim
### Impact A path traversal attack aims to access files and directories that are stored outside the web root folder. By manipulating variables that reference files with “dot-dot-slash (../)” sequences and its variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system including application source code or configuration and critical system files. Vulnerable code: https://github.com/aimhubio/aim/blob/0b99c6ca08e0ba7e7011453a2f68033e9b1d1bce/aim/web/api/views.py#L9-L16 ### Patches The vulnerability issue is resolved in Aim v3.1.0. ### References https://owasp.org/www-community/attacks/Path_Traversal
{'CVE-2021-43775'}
2022-04-19T19:03:15Z
2021-11-23T22:03:23Z
HIGH
8.6
{'CWE-22'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-43775', 'https://github.com/aimhubio/aim/issues/999', 'https://github.com/aimhubio/aim/blob/0b99c6ca08e0ba7e7011453a2f68033e9b1d1bce/aim/web/api/views.py#L9-L16', 'https://github.com/aimhubio/aim/pull/1003/commits/f01266a1a479ef11d7d6c539e7dd89e9d5639738', 'https://github.com/aimhubio/aim/pull/1003', 'https://github.com/aimhubio/aim/security/advisories/GHSA-8phj-f9w2-cjcc', 'https://github.com/advisories/GHSA-8phj-f9w2-cjcc'}
null
{'https://github.com/aimhubio/aim/pull/1003/commits/f01266a1a479ef11d7d6c539e7dd89e9d5639738'}
{'https://github.com/aimhubio/aim/pull/1003/commits/f01266a1a479ef11d7d6c539e7dd89e9d5639738'}
GHSA
GHSA-jjp3-m93h-5jm4
Cross-site Scripting in microweber
Microweber drag and drop website builder and CMS with e-commerce. Cross-site Scripting (XSS) discovered in microweber prior to 1.2.12. There is currently no known workaround, users are recommended to update to version 1.2.12.
{'CVE-2022-0928'}
2022-03-24T23:19:36Z
2022-03-12T00:00:34Z
MODERATE
6.8
{'CWE-79'}
{'https://github.com/microweber/microweber/commit/fc9137c031f7edec5f50d73b300919fb519c924a', 'https://github.com/advisories/GHSA-jjp3-m93h-5jm4', 'https://huntr.dev/bounties/085aafdd-ba50-44c7-9650-fa573da29bcd', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0928'}
null
{'https://github.com/microweber/microweber/commit/fc9137c031f7edec5f50d73b300919fb519c924a'}
{'https://github.com/microweber/microweber/commit/fc9137c031f7edec5f50d73b300919fb519c924a'}
GHSA
GHSA-g4xp-36c3-f7mr
Hidden Directories Always Served in inert
Versions 1.1.1 and earlier of `inert` are vulnerable to an information leakage vulnerability which causes files in hidden directories to be served, even when showHidden is false. The inert directory handler always allows files in hidden directories to be served, even when `showHidden` is false. ## Recommendation Update to version >= 1.1.1.
{'CVE-2014-10068'}
2021-01-07T23:37:01Z
2020-08-31T22:47:41Z
MODERATE
0
{'CWE-22'}
{'https://github.com/hapijs/inert/pull/15', 'https://github.com/advisories/GHSA-g4xp-36c3-f7mr', 'https://nodesecurity.io/advisories/14', 'https://www.npmjs.com/advisories/14', 'https://nvd.nist.gov/vuln/detail/CVE-2014-10068', 'https://github.com/hapijs/inert/commit/e8f99f94da4cb08e8032eda984761c3f111e3e82'}
null
{'https://github.com/hapijs/inert/commit/e8f99f94da4cb08e8032eda984761c3f111e3e82'}
{'https://github.com/hapijs/inert/commit/e8f99f94da4cb08e8032eda984761c3f111e3e82'}
GHSA
GHSA-43q8-3fv7-pr5x
Improper Validation of Integrity Check Value in TensorFlow
### Impact The implementation of [`tf.sparse.split`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_split_op.cc#L26-L102) does not fully validate the input arguments. Hence, a malicious user can trigger a denial of service via a segfault or a heap OOB read: ```python import tensorflow as tf data = tf.random.uniform([1, 32, 32], dtype=tf.float32) axis = [1, 2] x = tf.sparse.from_dense(data) result = tf.sparse.split(x,3, axis=axis) ``` The code assumes `axis` is a scalar. This is another instance of [TFSA-2021-190](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-190.md) (CVE-2021-41206). ### Patches We have patched the issue in GitHub commit [61bf91e768173b001d56923600b40d9a95a04ad5](https://github.com/tensorflow/tensorflow/commit/61bf91e768173b001d56923600b40d9a95a04ad5) (merging [#53695](https://github.com/tensorflow/tensorflow/pull/53695)). The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/53660).
null
2022-02-09T23:37:55Z
2022-02-09T23:37:55Z
HIGH
7
{'CWE-354'}
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-43q8-3fv7-pr5x', 'https://github.com/advisories/GHSA-43q8-3fv7-pr5x', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pgcq-h79j-2f69', 'https://github.com/tensorflow/tensorflow/pull/53695', 'https://github.com/tensorflow/tensorflow/commit/61bf91e768173b001d56923600b40d9a95a04ad5'}
null
{'https://github.com/tensorflow/tensorflow/commit/61bf91e768173b001d56923600b40d9a95a04ad5'}
{'https://github.com/tensorflow/tensorflow/commit/61bf91e768173b001d56923600b40d9a95a04ad5'}
GHSA
GHSA-qc36-q22q-cjw3
SMTP command injection in lettre
### Impact Affected versions of lettre allowed SMTP command injection through an attacker's controlled message body. The module for escaping lines starting with a period wouldn't catch a period that was placed after a double CRLF sequence, allowing the attacker to end the current message and write arbitrary SMTP commands after it. ### Fix The flaw is fixed by correctly handling consecutive CRLF sequences. ### References * [RUSTSEC-2021-0069](https://rustsec.org/advisories/RUSTSEC-2021-0069.html)
{'CVE-2021-38189'}
2022-04-19T19:02:58Z
2021-07-12T17:03:27Z
CRITICAL
9.8
{'CWE-147'}
{'https://github.com/lettre/lettre/security/advisories/GHSA-qc36-q22q-cjw3', 'https://github.com/advisories/GHSA-qc36-q22q-cjw3', 'https://rustsec.org/advisories/RUSTSEC-2021-0069.html', 'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2', 'https://github.com/lettre/lettre/commit/8bfc20506cc5e098fe6eb3d1cafe3bea791215ce'}
null
{'https://github.com/lettre/lettre/commit/8bfc20506cc5e098fe6eb3d1cafe3bea791215ce', 'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2'}
{'https://github.com/lettre/lettre/commit/8bfc20506cc5e098fe6eb3d1cafe3bea791215ce', 'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2'}
GHSA
GHSA-mpjm-v997-c4h4
Sandboxed renderers can obtain thumbnails of arbitrary files through the nativeImage API
### Impact This vulnerability allows a sandboxed renderer to request a "thumbnail" image of an arbitrary file on the user's system. The thumbnail can potentially include significant parts of the original file, including textual data in many cases. All current stable versions of Electron are affected. ### Patches This was fixed with #30728, and the following Electron versions contain the fix: - 15.0.0-alpha.10 - 14.0.0 - 13.3.0 - 12.1.0 - 11.5.0 ### Workarounds If your app enables `contextIsolation`, this vulnerability is significantly more difficult for an attacker to exploit. Further, if your app does not depend on the `createThumbnailFromPath` API, then you can simply disable the functionality. In the main process, before the 'ready' event: ```js delete require('electron').nativeImage.createThumbnailFromPath ``` ### For more information If you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org).
{'CVE-2021-39184'}
2022-04-19T19:03:06Z
2021-10-12T21:59:13Z
MODERATE
6.8
{'CWE-668'}
{'https://github.com/electron/electron/pull/30728/commits/8fed645bd671f359ee52d806c075ec4e07eda17f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39184', 'https://github.com/electron/electron/pull/30728', 'https://github.com/advisories/GHSA-mpjm-v997-c4h4', 'https://github.com/electron/electron/security/advisories/GHSA-mpjm-v997-c4h4'}
null
{'https://github.com/electron/electron/pull/30728/commits/8fed645bd671f359ee52d806c075ec4e07eda17f'}
{'https://github.com/electron/electron/pull/30728/commits/8fed645bd671f359ee52d806c075ec4e07eda17f'}
GHSA
GHSA-9wrv-g75h-8ccc
Improper Access Control in Shopware
Shopware 6 is an open commerce platform based on Symfony Framework and Vue and supported by a worldwide community and more than 1.500 community extensions. Permissions set to sales channel context by admin-api are still useable within normal user session. 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. 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-24872'}
2022-05-04T03:52:20Z
2022-04-22T21:04:27Z
HIGH
8.1
{'CWE-732'}
{'https://github.com/shopware/platform/security/advisories/GHSA-9wrv-g75h-8ccc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24872', 'https://github.com/shopware/platform/commit/083765e2d64a00315050c4891800c9e98ba0c77c', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2022', 'https://github.com/advisories/GHSA-9wrv-g75h-8ccc'}
null
{'https://github.com/shopware/platform/commit/083765e2d64a00315050c4891800c9e98ba0c77c'}
{'https://github.com/shopware/platform/commit/083765e2d64a00315050c4891800c9e98ba0c77c'}
GHSA
GHSA-qrqm-fpv6-6r8g
Command Injection Vulnerability in Mechanize
This security advisory has been created for public disclosure of a Command Injection vulnerability that was responsibly reported by @kyoshidajp (Katsuhiko YOSHIDA). ### Impact Mechanize `>= v2.0`, `< v2.7.7` allows for OS commands to be injected using several classes' methods which implicitly use Ruby's `Kernel.open` method. Exploitation is possible only if untrusted input is used as a local filename and passed to any of these calls: - `Mechanize::CookieJar#load`: since v2.0 (see 208e3ed) - `Mechanize::CookieJar#save_as`: since v2.0 (see 5b776a4) - `Mechanize#download`: since v2.2 (see dc91667) - `Mechanize::Download#save` and `#save!` since v2.1 (see 98b2f51, bd62ff0) - `Mechanize::File#save` and `#save_as`: since v2.1 (see 2bf7519) - `Mechanize::FileResponse#read_body`: since v2.0 (see 01039f5) ### Patches These vulnerabilities are patched in Mechanize v2.7.7. ### Workarounds No workarounds are available. We recommend upgrading to v2.7.7 or later. ### References See https://docs.rubocop.org/rubocop/cops_security.html#securityopen for background on why `Kernel.open` should not be used with untrusted input. ### For more information If you have any questions or comments about this advisory, please open an issue in [sparklemotion/mechanize](https://github.com/sparklemotion/mechanize/issues/new).
{'CVE-2021-21289'}
2022-04-27T20:24:22Z
2021-02-02T18:50:27Z
HIGH
7.4
{'CWE-78'}
{'https://github.com/sparklemotion/mechanize/commit/66a6a1bfa653a5f13274a396a5e5441238656aa0', 'https://security.gentoo.org/glsa/202107-17', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YNFZ7ROYS6V4J5L5PRAJUG2AWC7VXR2V/', 'https://github.com/advisories/GHSA-qrqm-fpv6-6r8g', 'https://lists.debian.org/debian-lts-announce/2021/02/msg00021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LBVVJUL4P4KCJH4IQTHFZ4ATXY7XXZPV/', 'https://github.com/sparklemotion/mechanize/releases/tag/v2.7.7', 'https://github.com/sparklemotion/mechanize/security/advisories/GHSA-qrqm-fpv6-6r8g', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21289', 'https://rubygems.org/gems/mechanize/'}
null
{'https://github.com/sparklemotion/mechanize/commit/66a6a1bfa653a5f13274a396a5e5441238656aa0'}
{'https://github.com/sparklemotion/mechanize/commit/66a6a1bfa653a5f13274a396a5e5441238656aa0'}
GHSA
GHSA-w32p-76xr-88pc
Out-of-bounds write
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0989, CVE-2019-0991, CVE-2019-0992, CVE-2019-0993, CVE-2019-1002, CVE-2019-1024, CVE-2019-1051, CVE-2019-1052.
{'CVE-2019-1003'}
2021-03-29T20:59:06Z
2021-03-29T20:59:06Z
HIGH
7.5
{'CWE-787'}
{'https://github.com/advisories/GHSA-w32p-76xr-88pc', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1003', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1003', 'https://github.com/chakra-core/ChakraCore/commit/90f67afac6362828c750f3bccbcc1c360caf29e4', 'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee'}
null
{'https://github.com/chakra-core/ChakraCore/commit/90f67afac6362828c750f3bccbcc1c360caf29e4', 'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee'}
{'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/90f67afac6362828c750f3bccbcc1c360caf29e4'}
End of preview. Expand in Data Studio

A Ground-Truth Dataset of Real Security Patches

This dataset provides a ground-truth collection of real-world security patches gathered from public GitHub repositories, cross-referenced with CVE records, and enriched with natural language artifacts and metadata. It is intended to support research in areas such as vulnerability detection, security patch understanding, commit classification, and software security best practices.

Citation

If you use this dataset, please cite:

@misc{reis2021groundtruthdatasetrealsecurity,
  title={A ground-truth dataset of real security patches}, 
  author={Sofia Reis and Rui Abreu},
  year={2021},
  eprint={2110.09635},
  archivePrefix={arXiv},
  primaryClass={cs.CR},
  url={https://arxiv.org/abs/2110.09635}, 
}
Downloads last month
21