Dataset Viewer
ecosystem
stringclasses 14
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
267
⌀ | details
stringlengths 9
13.5k
| aliases
stringlengths 17
144
⌀ | modified_date
stringdate 2010-05-27 05:47:00
2022-05-10 08:46:52
| published_date
stringdate 2005-12-31 05:00:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 988
values | refs
stringlengths 30
17.7k
⌀ | introduced
stringlengths 75
4.26k
⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
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://nvd.nist.gov/vuln/detail/CVE-2021-27516', 'https://github.com/medialize/URI.js/releases/tag/v1.19.6', 'https://github.com/medialize/URI.js/commit/a1ad8bcbc39a4d136d7e252e76e957f3ece70839', 'https://github.com/advisories/GHSA-p6j9-7xhc-rhwp', 'https://github.com/medialize/URI.js/security/advisories/GHSA-p6j9-7xhc-rhwp', 'https://advisory.checkmarx.net/advisory/CX-2021-4305'} | null |
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://nvd.nist.gov/vuln/detail/CVE-2021-29610', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mq5c-prh3-3f3h', 'https://github.com/tensorflow/tensorflow/commit/c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9', 'https://github.com/advisories/GHSA-mq5c-prh3-3f3h'} | null |
GHSA | GHSA-g4g4-3pqw-8m7f | Use After Free in rusqlite | An issue was discovered in the rusqlite crate 0.25.x before 0.25.4 and 0.26.x before 0.26.2 for Rust. rollback_hook has a use-after-free. | {'CVE-2021-45718'} | 2022-01-06T22:02:01Z | 2022-01-06T22:02:01Z | HIGH | 7.5 | {'CWE-416'} | {'https://rustsec.org/advisories/RUSTSEC-2021-0128.html', 'https://github.com/advisories/GHSA-g4g4-3pqw-8m7f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45718', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/rusqlite/RUSTSEC-2021-0128.md'} | null |
GHSA | GHSA-vpch-rxw3-fgx8 | Cross-Site Scripting in @risingstack/protect | All versions of `@risingstack/protect` are vulnerable to Cross-Site Scripting. The `isXss()` XSS validator has several bypasses that may allow attackers to execute arbitrary JavaScript in a victim's browser.
## Recommendation
No fix is currently available. Consider using an alternative package. The package is not actively maintained and will not be patched. | {'CVE-2018-1000160'} | 2021-09-20T22:10:10Z | 2018-04-25T14:30:43Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1000160', 'https://www.npmjs.com/advisories/1116', 'https://github.com/RisingStack/protect/blob/60b0c91e86686d34e5202419ce9ae7e8dc08edcd/lib/rules/xss.js#L4-L13', 'https://github.com/advisories/GHSA-vpch-rxw3-fgx8', 'https://github.com/RisingStack/protect/issues/16', 'http://embed.plnkr.co/xHbhB29JWWyMUMeHsLrm', 'https://snyk.io/vuln/SNYK-JS-RISINGSTACKPROTECT-455402'} | null |
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/advisories/GHSA-9v62-24cr-58cx', 'https://github.com/sass/node-sass/commit/338fd7a14d3b8bd374a382336df16f9c6792b884'} | null |
GHSA | GHSA-4mvj-rq4v-2fxw | Prototype Pollution in x-assign | This affects all versions of package x-assign. The global proto object can be polluted using the __proto__ object. | {'CVE-2021-23452'} | 2021-10-26T17:31:53Z | 2021-10-21T17:50:44Z | HIGH | 8.6 | {'CWE-1321', 'CWE-915'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23452', 'https://runkit.com/embed/sq8qjwemyn8t', 'https://github.com/advisories/GHSA-4mvj-rq4v-2fxw', 'https://snyk.io/vuln/SNYK-JS-XASSIGN-1759314'} | null |
GHSA | GHSA-mf22-92pm-m8p8 | Cross site scripting in @awsui/components-react | ### Impact
Components could potentially allow cross-site scripting (XSS) in certain circumstances. These components could render content without adequate neutralization.
### Patches
Fixed in 3.0.367. | {'CVE-2022-24709'} | 2022-03-09T21:13:02Z | 2022-02-25T15:36:47Z | HIGH | 8.8 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24709', 'https://github.com/advisories/GHSA-mf22-92pm-m8p8', 'https://github.com/aws/awsui-documentation/security/advisories/GHSA-mf22-92pm-m8p8', 'https://www.npmjs.com/package/@awsui/components-react'} | null |
GHSA | GHSA-rh5w-82wh-jhr8 | XSS vulnerability on asset view | ### Impact
Mautic versions before 3.3.4 / 4.0.0 are vulnerable to an inline JS XSS attack when viewing Mautic assets by utilizing inline JS in the title and adding a broken image URL as a remote asset. This can only be leveraged by an authenticated user with permission to create or edit assets.
### Patches
Upgrade to 3.3.4 or 4.0.0
### Workarounds
No
### References
https://github.com/mautic/mautic/releases/tag/3.3.4
https://github.com/mautic/mautic/releases/tag/4.0.0
### For more information
If you have any questions or comments about this advisory:
* Email us at [[email protected]](mailto:[email protected])
| {'CVE-2021-27912'} | 2022-04-19T19:03:05Z | 2021-09-01T18:40:31Z | HIGH | 7.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-rh5w-82wh-jhr8', 'https://github.com/mautic/mautic/security/advisories/GHSA-rh5w-82wh-jhr8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27912'} | null |
GHSA | GHSA-5rrv-m36h-qwf8 | Use-after-free in chttp | An issue was discovered in the chttp crate before 0.1.3 for Rust. There is a use-after-free during buffer conversion. | {'CVE-2019-16140'} | 2021-08-25T20:44:40Z | 2021-08-25T20:44:40Z | CRITICAL | 9.8 | {'CWE-416'} | {'https://rustsec.org/advisories/RUSTSEC-2019-0016.html', 'https://github.com/sagebind/isahc/issues/2', 'https://github.com/advisories/GHSA-5rrv-m36h-qwf8', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16140'} | null |
GHSA | GHSA-5wv5-4vpf-pj6m | Unexpected memory usage in Pallets Project Flask | The Pallets Project Flask before 1.0 is affected by unexpected memory usage. The impact is denial of service. The attack vector is crafted encoded JSON data. The fixed version is 1. NOTE this may overlap CVE-2018-1000656. | {'CVE-2019-1010083'} | 2021-08-17T18:25:36Z | 2019-07-19T16:12:46Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-5wv5-4vpf-pj6m', 'https://www.palletsprojects.com/blog/flask-1-0-released/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1010083'} | null |
GHSA | GHSA-4x5j-v9v9-w8gw | Downloads Resources over HTTP in httpsync | Affected versions of `httpsync` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `httpsync`.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees. | {'CVE-2016-10614'} | 2021-01-08T19:52:33Z | 2019-02-18T23:47:40Z | HIGH | 0 | {'CWE-311'} | {'https://nvd.nist.gov/vuln/detail/CVE-2016-10614', 'https://github.com/advisories/GHSA-4x5j-v9v9-w8gw', 'https://www.npmjs.com/advisories/210', 'https://nodesecurity.io/advisories/210'} | null |
GHSA | GHSA-qpxw-6473-ppww | Session Fixation in Subrion CMS | Subrion CMS 4.2.1 allows session fixation via an alphanumeric value in a session cookie. | {'CVE-2020-12467'} | 2021-06-22T15:23:04Z | 2021-06-22T15:23:04Z | MODERATE | 6.5 | {'CWE-384'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-12467', 'https://github.com/advisories/GHSA-qpxw-6473-ppww', 'https://github.com/belong2yourself/vulnerabilities/tree/master/Subrion%20CMS/Session%20Fixation'} | null |
GHSA | GHSA-36rh-ggpr-j3gj | Azure DevOps token leakage in logs | ### Impact
Applies to Azure DevOps users only. The bot's token may be exposed in server or pipeline logs due to the `http.extraheader=AUTHORIZATION` parameter being logged without redaction. It is recommended that Azure DevOps users revoke their existing bot credentials and generate new ones after upgrading if there's a potential that logs have been saved to a location that others can view.
### Patches
Fixed in 23.25.1
### Workarounds
Do not share Renovate logs with anyone who cannot be trusted with access to the token.
### For more information
If you have any questions or comments about this advisory:
* Email us at [[email protected]](mailto:[email protected]) | null | 2022-04-19T19:02:34Z | 2020-09-14T16:38:40Z | MODERATE | 0 | null | {'https://github.com/renovatebot/renovate/security/advisories/GHSA-36rh-ggpr-j3gj', 'https://github.com/advisories/GHSA-36rh-ggpr-j3gj'} | null |
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://github.com/advisories/GHSA-h6wf-hvwc-fm77', 'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0914', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0914'} | null |
GHSA | GHSA-gqf6-75v8-vr26 | Arbitrary File Write in bin-links | Versions of `bin-links` prior to 1.1.5 are vulnerable to an Arbitrary File Write. The package fails to restrict access to folders outside of the intended `node_modules` folder through the `bin` field. This allows attackers to create arbitrary files in the system. Note it is not possible to overwrite files that already exist.
## Recommendation
Upgrade to version 1.1.5 or later. | null | 2020-09-04T16:56:11Z | 2020-09-04T16:56:11Z | LOW | 0 | null | {'https://www.npmjs.com/advisories/1427', 'https://github.com/advisories/GHSA-gqf6-75v8-vr26'} | null |
GHSA | GHSA-jhq3-57xh-6643 | Privilege Escalation due to Blind NoSQL Injection in flintcms | Versions of `flintcms` before version 1.1.10 are vulnerable to account takeover due to blind MongoDB injection in the password reset.
## Recommendation
Update to version 1.1.10 or later. | {'CVE-2018-3783'} | 2021-09-14T19:42:56Z | 2018-08-21T17:03:59Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://hackerone.com/reports/386807', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3783', 'https://www.npmjs.com/advisories/689', 'https://github.com/advisories/GHSA-jhq3-57xh-6643'} | null |
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 <[email protected]>. | {'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://nvd.nist.gov/vuln/detail/CVE-2021-29136', 'https://github.com/opencontainers/umoci/commit/d9efc31daf2206f7d3fdb839863cf7a576a2eb57'} | null |
GHSA | GHSA-4999-659w-mq36 | Authentication bypass issue in the Operator Console | During an internal security audit, we detected an authentication bypass issue in the Operator Console when an external IDP is enabled. The security issue has been reported internally. We have not observed this exploit in the wild or reported elsewhere in the community at large. All users are advised to upgrade ASAP.
### Impact
All users on release v0.12.2 and before are affected.
### Patches
This issue was fixed by PR https://github.com/minio/console/pull/1217, users should upgrade to latest release.
### Workarounds
Add `automountServiceAccountToken: false` to the operator-console deployment in Kubernetes so no service account token will get mounted inside the pod, then disable the external identity provider authentication by unset the `CONSOLE_IDP_URL`, `CONSOLE_IDP_CLIENT_ID`, `CONSOLE_IDP_SECRET` and `CONSOLE_IDP_CALLBACK` environment variable and instead use the Kubernetes service account token.
### References
#1217 for more information on the fix and how it was fixed.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [console issues](https://github.com/minio/console/issues)
* Email us at [[email protected]](mailto:[email protected])
| {'CVE-2021-41266'} | 2022-04-19T19:03:14Z | 2021-11-15T23:16:49Z | HIGH | 8.6 | {'CWE-306'} | {'https://github.com/advisories/GHSA-4999-659w-mq36', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41266', 'https://github.com/minio/console/pull/1217', 'https://github.com/minio/console/security/advisories/GHSA-4999-659w-mq36'} | null |
GHSA | GHSA-r4m5-47cq-6qg8 | Server-Side Request Forgery in ftp-srv | All versions of `ftp-srv` are vulnerable to Server-Side Request Forgery (SSRF). The package fails to prevent remote clients to access other resources in the network, for example when connecting to the server through telnet. This allows attackers to access any network resources available to the server, including private resources in the hosting environment.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available. | null | 2022-03-24T22:19:54Z | 2020-09-04T17:25:13Z | HIGH | 0 | {'CWE-918'} | {'https://www.npmjs.com/advisories/1445', 'https://github.com/advisories/GHSA-r4m5-47cq-6qg8'} | null |
GHSA | GHSA-q6pj-jh94-5fpr | OS Command Injection in docker-compose-remote-api | docker-compose-remote-api through 0.1.4 allows execution of arbitrary commands. Within 'index.js' of the package, the function 'exec(serviceName, cmd, fnStdout, fnStderr, fnExit)' uses the variable 'serviceName' which can be controlled by users without any sanitization. | {'CVE-2020-7606'} | 2021-07-28T21:23:11Z | 2021-05-07T16:14:39Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7606', 'https://snyk.io/vuln/SNYK-JS-DOCKERCOMPOSEREMOTEAPI-560125', 'https://github.com/advisories/GHSA-q6pj-jh94-5fpr'} | null |
GHSA | GHSA-3pcr-4982-548m | Exposure of .env if project root is configured as web root in shopware/production | ### Impact
The .env and other sensitive files can be leaked if the project root and not `/public` is configured as the web root.
### Patches
We recommend to update to the current version 6.3.5.3. You can get the update to 6.3.5.3 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
You should always use `/public` as the web root.
For older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
### For more information
https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2021 | null | 2021-04-13T15:13:37Z | 2021-04-13T15:13:37Z | MODERATE | 0 | {'CWE-552'} | {'https://github.com/advisories/GHSA-3pcr-4982-548m', 'https://github.com/shopware/platform/security/advisories/GHSA-3pcr-4982-548m'} | null |
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'} | {'https://www.npmjs.com/advisories/27', 'http://www.openwall.com/lists/oss-security/2014/05/15/2', 'https://nvd.nist.gov/vuln/detail/CVE-2014-3741', 'https://github.com/tojocky/node-printer/commit/e001e38738c17219a1d9dd8c31f7d82b9c0013c7', 'https://github.com/advisories/GHSA-5c8j-xr24-2665', 'https://nodesecurity.io/advisories/printer_potential_command_injection', 'http://www.openwall.com/lists/oss-security/2014/05/13/1'} | null |
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/commit/da5ff2daf618591f64b2b62d9d9803951b945e9f', 'https://github.com/advisories/GHSA-qg48-85hg-mqc5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29554', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qg48-85hg-mqc5'} | null |
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://nvd.nist.gov/vuln/detail/CVE-2019-10773', 'https://access.redhat.com/errata/RHSA-2020:0475', 'https://snyk.io/vuln/SNYK-JS-YARN-537806,', 'https://lists.fedoraproject.org/archives/list/[email protected]/message/ITY5BC63CCC647DFNUQRQ5AJDKUKUNBI/', 'https://blog.daniel-ruf.de/critical-design-flaw-npm-pnpm-yarn/', 'https://github.com/yarnpkg/yarn/issues/7761#issuecomment-565493023', 'https://github.com/yarnpkg/yarn/commit/039bafd74b7b1a88a53a54f8fa6fa872615e90e7', 'https://lists.fedoraproject.org/archives/list/[email protected]/message/3HIZW4NZVV5QY5WWGW2JRP3FHYKZ6ZJ5/', 'https://github.com/yarnpkg/yarn/pull/7755', 'https://github.com/advisories/GHSA-5xf4-f2fq-f69j'} | null |
GHSA | GHSA-wg6j-r28m-7293 | Code Injection in simple_captcha2 | The simple_captcha2 gem 0.2.3 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party. | {'CVE-2019-14282'} | 2021-08-17T20:23:37Z | 2019-07-31T04:21:19Z | CRITICAL | 9.8 | {'CWE-94'} | {'https://github.com/advisories/GHSA-wg6j-r28m-7293', 'https://github.com/rubygems/rubygems.org/issues/2073', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14282', 'https://rubygems.org/gems/simple_captcha2/versions/'} | null |
GHSA | GHSA-37pw-qw47-4jxm | Privilege escalation vulnerability in Apache Hadoop | In Apache Hadoop versions 3.0.0-alpha1 to 3.1.0, 2.9.0 to 2.9.1, and 2.2.0 to 2.8.4, a user who can escalate to yarn user can possibly run arbitrary commands as root user. | {'CVE-2018-8029'} | 2021-09-21T16:29:03Z | 2019-05-31T16:09:15Z | HIGH | 8.8 | {'CWE-285'} | {'https://lists.apache.org/thread.html/r4dddf1705dbedfa94392913b2dad1cd2d1d89040facd389eea0b3510@%3Ccommits.druid.apache.org%3E', 'http://www.securityfocus.com/bid/108518', 'https://nvd.nist.gov/vuln/detail/CVE-2018-8029', 'https://lists.apache.org/thread.html/a97c53a81e639ca2fc7b8f61a4fcd1842c2a78544041244a7c624727@%3Cissues.hbase.apache.org%3E', 'https://lists.apache.org/thread.html/17084c09e6dedf60efe08028b429c92ffd28aacc28454e4fa924578a@%3Cgeneral.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/0b8d58e02dbd0fb8bf7320c514fe58da1d6728bdc150f1ba04e0d9fc@%3Cissues.hbase.apache.org%3E', 'https://lists.apache.org/thread.html/rb21df54a4e39732ce653d2aa5672e36a792b59eb6717f2a06bb8d02a@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/a0164b87660223a2d491f83c88f905fe1a9fa8dc795148d9b0d968c8@%3Cdev.hbase.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20190617-0001/', 'https://github.com/advisories/GHSA-37pw-qw47-4jxm'} | null |
GHSA | GHSA-fvx8-v524-8579 | Cleartext Storage of Sensitive Information | django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database. | {'CVE-2020-17495'} | 2021-06-04T21:46:52Z | 2021-06-04T21:46:52Z | HIGH | 7.5 | {'CWE-312'} | {'https://github.com/celery/django-celery-results/issues/142', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17495', 'https://github.com/advisories/GHSA-fvx8-v524-8579'} | null |
GHSA | GHSA-r4x3-g983-9g48 | Moderate severity vulnerability that affects sprockets | Withdrawn, accidental duplicate publish.
Multiple directory traversal vulnerabilities in server.rb in Sprockets before 2.0.5, 2.1.x before 2.1.4, 2.2.x before 2.2.3, 2.3.x before 2.3.3, 2.4.x before 2.4.6, 2.5.x before 2.5.1, 2.6.x and 2.7.x before 2.7.1, 2.8.x before 2.8.3, 2.9.x before 2.9.4, 2.10.x before 2.10.2, 2.11.x before 2.11.3, 2.12.x before 2.12.3, and 3.x before 3.0.0.beta.3, as distributed with Ruby on Rails 3.x and 4.x, allow remote attackers to determine the existence of files outside the application root via a ../ (dot dot slash) sequence with (1) double slashes or (2) URL encoding. | null | 2021-12-03T14:21:11Z | 2018-10-10T17:29:34Z | MODERATE | 0 | null | {'https://nvd.nist.gov/vuln/detail/CVE-2014-7819', 'https://github.com/advisories/GHSA-r4x3-g983-9g48'} | null |
GHSA | GHSA-wfcc-pff6-rgc5 | Exposure of Sensitive Information in org.eclipse.jetty:jetty-server | Jetty through 9.4.x is prone to a timing channel in util/security/Password.java, which makes it easier for remote attackers to obtain access by observing elapsed times before rejection of incorrect passwords. | {'CVE-2017-9735'} | 2022-03-18T20:17:00Z | 2018-10-19T16:15:46Z | HIGH | 7.5 | {'CWE-200', 'CWE-203'} | {'https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/advisories/GHSA-wfcc-pff6-rgc5', 'https://github.com/eclipse/jetty.project/issues/1556', 'https://lists.apache.org/thread.html/f887a5978f5e4c62b9cfe876336628385cff429e796962649649ec8a@%3Ccommon-issues.hadoop.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html', 'https://bugs.debian.org/864631', 'https://lists.apache.org/thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272@%3Cissues.activemq.apache.org%3E', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://lists.apache.org/thread.html/36870f6c51f5bc25e6f7bb1fcace0e57e81f1524019b11f466738559@%3Ccommon-dev.hadoop.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/05/msg00016.html', 'http://www.securityfocus.com/bid/99104', 'https://nvd.nist.gov/vuln/detail/CVE-2017-9735', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html'} | null |
GHSA | GHSA-4363-x42f-xph6 | Malicious Package in hw-trnasport-u2f | All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | null | 2021-10-01T21:03:01Z | 2020-09-03T17:05:14Z | CRITICAL | 9.1 | {'CWE-506'} | {'https://github.com/advisories/GHSA-4363-x42f-xph6', 'https://www.npmjs.com/advisories/1400'} | null |
GHSA | GHSA-hf8c-xr89-vfm5 | Command Injection in ungit | The package ungit before 1.5.20 are vulnerable to Remote Code Execution (RCE) via argument injection. The issue occurs when calling the /api/fetch endpoint. User controlled values (remote and ref) are passed to the git fetch command. By injecting some git options it was possible to get arbitrary command execution. | {'CVE-2022-25766'} | 2022-03-30T16:46:12Z | 2022-03-22T00:00:41Z | HIGH | 8.8 | {'CWE-77'} | {'https://github.com/FredrikNoren/ungit/blob/master/CHANGELOG.md%231520', 'https://github.com/advisories/GHSA-hf8c-xr89-vfm5', 'https://snyk.io/vuln/SNYK-JS-UNGIT-2414099', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25766', 'https://github.com/FredrikNoren/ungit/pull/1510', 'https://github.com/FredrikNoren/ungit/pull/1511'} | null |
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://packagist.org/packages/getkirby/cms', 'https://github.com/getkirby/kirby/releases/tag/3.3.6', 'https://github.com/getkirby/kirby/security/advisories/GHSA-2ccx-2gf3-8xvv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26253', 'https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa', 'https://packagist.org/packages/getkirby/panel', 'https://github.com/advisories/GHSA-2ccx-2gf3-8xvv'} | null |
GHSA | GHSA-vqwg-4v6f-h6x5 | Stored XSS vulnerability in Matrix Project Plugin | Jenkins Matrix Project Plugin 1.19 and earlier does not escape HTML metacharacters in node and label names, and label descriptions, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Agent/Configure permission. | {'CVE-2022-20615'} | 2022-04-29T04:33:52Z | 2022-01-13T00:01:04Z | MODERATE | 5.4 | {'CWE-79'} | {'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://nvd.nist.gov/vuln/detail/CVE-2022-20615', 'https://github.com/advisories/GHSA-vqwg-4v6f-h6x5', 'http://www.openwall.com/lists/oss-security/2022/01/12/6', 'https://www.jenkins.io/security/advisory/2022-01-12/#SECURITY-2017'} | null |
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/advisories/GHSA-3rcw-9p9x-582v', 'https://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3rcw-9p9x-582v', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41228'} | null |
GHSA | GHSA-c3hr-wwh3-qm54 | Directory Traversal in fsk-server | Affected versions of `fsk-server` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.
Example request:
```
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
```
## Recommendation
No patch is available for this vulnerability.
It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead. | {'CVE-2017-16090'} | 2021-01-14T15:55:35Z | 2020-09-01T16:47:09Z | HIGH | 0 | {'CWE-22'} | {'https://www.npmjs.com/advisories/345', 'https://github.com/advisories/GHSA-c3hr-wwh3-qm54', 'https://nodesecurity.io/advisories/345', 'https://github.com/JacksonGL/NPM-Vuln-PoC/tree/master/directory-traversal/fsk-server', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16090'} | null |
GHSA | GHSA-p6p8-q4pj-f74m | Improper Certificate Validation in twitter-stream | In voloko twitter-stream 0.1.16, missing TLS hostname validation allows an attacker to perform a man-in-the-middle attack against users of the library (because eventmachine is misused). | {'CVE-2020-24392'} | 2021-03-29T16:28:42Z | 2021-03-29T16:28:42Z | MODERATE | 5.9 | {'CWE-295'} | {'https://securitylab.github.com/advisories/GHSL-2020-097-voloko-twitter-stream', 'https://github.com/advisories/GHSA-p6p8-q4pj-f74m', 'https://github.com/voloko/twitter-stream', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24392'} | null |
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://github.com/faye/websocket-extensions-node/security/advisories/GHSA-g78m-2chm-r7qv', 'https://snyk.io/vuln/SNYK-JS-WEBSOCKETEXTENSIONS-570623', 'https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions', 'https://github.com/advisories/GHSA-g78m-2chm-r7qv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7662', 'https://github.com/faye/websocket-extensions-node/commit/29496f6838bfadfe5a2f85dff33ed0ba33873237'} | null |
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://github.com/advisories/GHSA-xw22-wv29-3299', 'https://github.com/creharmony/node-etsy-client/security/advisories/GHSA-xw22-wv29-3299', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21421', 'https://github.com/creharmony/node-etsy-client/commit/b4beb8ef080366c1a87dbf9e163051a446acaa7d'} | null |
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://github.com/ruby/tmpdir/commit/93798c01cb7c10476e50a4d80130a329ba47f348', 'https://rubygems.org/gems/tmpdir', 'https://www.ruby-lang.org/en/news/2021/04/05/tempfile-path-traversal-on-windows-cve-2021-28966/', 'https://github.com/advisories/GHSA-46f2-3v63-3xrp', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/tmpdir/CVE-2021-28966.yml', 'https://hackerone.com/reports/1131465', 'https://github.com/ruby/tmpdir/pull/8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28966', 'https://security.netapp.com/advisory/ntap-20210902-0004/'} | null |
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/security/advisories/GHSA-vvmr-8829-6whx', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23601', 'https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50', 'https://github.com/advisories/GHSA-vvmr-8829-6whx'} | null |
GHSA | GHSA-g3p2-hfqr-9m25 | Improper file handling in concrete5/core | A bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Concrete CMS (concrete5) versions 8.5.6 and below. The external file upload feature stages files in the public directory even if they have disallowed file extensions. They are stored in a directory with a random name, but it's possible to stall the uploads and brute force the directory name. You have to be an admin with the ability to upload files, but this bug gives you the ability to upload restricted file types and execute them depending on server configuration. To fix this, a check for allowed file extensions was added before downloading files to a tmp directory | {'CVE-2021-22968'} | 2021-11-23T17:54:26Z | 2021-11-23T17:54:26Z | MODERATE | 0 | {'CWE-98'} | {'https://github.com/advisories/GHSA-g3p2-hfqr-9m25', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22968', 'https://hackerone.com/reports/1350444', 'https://documentation.concretecms.org/developers/introduction/version-history/857-release-notes'} | null |
GHSA | GHSA-wvhv-rr3v-vhpj | Out-of-bounds write in ChakraCore | A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848. | {'CVE-2020-0823'} | 2021-07-28T18:57:11Z | 2021-07-28T18:57:11Z | HIGH | 7.5 | {'CWE-787'} | {'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0823', 'https://nvd.nist.gov/vuln/detail/CVE-2020-0823', 'https://github.com/advisories/GHSA-wvhv-rr3v-vhpj'} | null |
GHSA | GHSA-v9j4-cp63-qv62 | Tarslip in go-unarr | unarr.go in go-unarr (aka Go bindings for unarr) 0.1.1 allows Directory Traversal via ../ in a pathname within a TAR archive. | {'CVE-2021-38197'} | 2021-09-01T18:32:02Z | 2021-09-01T18:32:02Z | CRITICAL | 9.8 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-38197', 'https://github.com/gen2brain/go-unarr/issues/21', 'https://github.com/advisories/GHSA-v9j4-cp63-qv62'} | null |
GHSA | GHSA-p7xc-35m8-57pr | FedMsg not properly completing message validation | FedMsg 0.18.1 and older is vulnerable to a message validation flaw resulting in message validation not being enabled if configured to be on. | {'CVE-2017-1000001'} | 2022-04-26T18:14:01Z | 2018-07-13T15:17:14Z | HIGH | 7.5 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-1000001', 'https://github.com/advisories/GHSA-p7xc-35m8-57pr', 'https://github.com/fedora-infra/fedmsg/blob/0.18.2/CHANGELOG.rst'} | null |
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://nvd.nist.gov/vuln/detail/CVE-2020-7789', 'https://snyk.io/vuln/SNYK-JS-NODENOTIFIER-1035794', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1050371', 'https://github.com/advisories/GHSA-5fw9-fq32-wv5p', 'https://github.com/mikaelbr/node-notifier/commit/5d62799dab88505a709cd032653b2320c5813fce', 'https://github.com/mikaelbr/node-notifier/blob/master/lib/utils.js%23L303'} | null |
GHSA | GHSA-754x-4jwp-cqp6 | Cross-Site Scripting in http_server | All versions of `http_server` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available. | {'CVE-2019-15600'} | 2021-01-08T20:24:38Z | 2020-03-31T17:02:26Z | HIGH | 0 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-15600', 'https://hackerone.com/reports/578138', 'https://hackerone.com/reports/692262', 'https://github.com/advisories/GHSA-754x-4jwp-cqp6', 'https://www.npmjs.com/advisories/1170'} | null |
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 [email protected]
| {'CVE-2021-41189'} | 2022-04-19T19:03:13Z | 2021-11-01T19:18:16Z | HIGH | 7.2 | {'CWE-863'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41189', 'https://github.com/DSpace/DSpace/commit/c3bea16ab911606e15ae96c97a1575e1ffb14f8a', 'https://github.com/advisories/GHSA-cf2j-vf36-c6w8', 'https://github.com/DSpace/DSpace/security/advisories/GHSA-cf2j-vf36-c6w8', 'https://github.com/DSpace/DSpace/issues/7928', 'https://github.com/DSpace/DSpace/commit/277b499a5cd3a4f5eb2370513a1b7e4ec2a6e041'} | null |
GHSA | GHSA-fvq6-392h-6mjj | Out-of-bounds Read in OpenCV | OpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds read error in the function icvCvt_BGRA2BGR_8u_C4C3R when reading an image file by using cv::imread. | {'CVE-2017-12599'} | 2021-11-18T00:06:52Z | 2021-10-12T22:01:08Z | HIGH | 8.8 | {'CWE-125'} | {'https://github.com/opencv/opencv-python/releases/tag/9', 'https://github.com/opencv/opencv-python/releases/tag/11', 'https://lists.debian.org/debian-lts-announce/2021/10/msg00028.html', 'https://github.com/opencv/opencv/pull/9376', 'https://security.gentoo.org/glsa/201712-02', 'https://nvd.nist.gov/vuln/detail/CVE-2017-12599', 'https://github.com/opencv/opencv/issues/9309', 'https://github.com/advisories/GHSA-fvq6-392h-6mjj', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00030.html', 'https://github.com/xiaoqx/pocs/blob/master/opencv.md'} | null |
GHSA | GHSA-xm9m-2vj8-fmfr | Uninitialized memory access in toodee | An issue was discovered in the toodee crate before 0.3.0 for Rust. The row-insertion feature allows attackers to read the contents of uninitialized memory locations. | {'CVE-2021-28029'} | 2021-09-01T18:30:40Z | 2021-09-01T18:30:40Z | HIGH | 7.5 | {'CWE-908'} | {'https://rustsec.org/advisories/RUSTSEC-2021-0028.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28029', 'https://github.com/advisories/GHSA-xm9m-2vj8-fmfr'} | null |
GHSA | GHSA-xv8x-pr4h-73jv | Memory corruption when returning a literal struct with a private call inside of it | ### Impact
When performing a function call inside a literal struct, there is a memory corruption issue that occurs because of an incorrect pointer to the the top of the stack.
### Patches
0.3.0 / #2447
* | {'CVE-2021-41121'} | 2021-10-18T18:40:16Z | 2021-10-12T15:59:29Z | HIGH | 7.5 | {'CWE-119'} | {'https://github.com/vyperlang/vyper/pull/2447', 'https://github.com/advisories/GHSA-xv8x-pr4h-73jv', 'https://github.com/vyperlang/vyper/security/advisories/GHSA-xv8x-pr4h-73jv', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41121'} | null |
GHSA | GHSA-8r98-rqg5-4vm3 | Downloads Resources over HTTP in node-browser | Affected versions of `node-browser` insecurely downloads resources over HTTP.
In scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees. | {'CVE-2016-10618'} | 2021-01-08T20:58:05Z | 2019-02-18T23:56:50Z | HIGH | 0 | {'CWE-311'} | {'https://www.npmjs.com/advisories/214', 'https://nodesecurity.io/advisories/214', 'https://github.com/advisories/GHSA-8r98-rqg5-4vm3', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10618'} | null |
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://access.redhat.com/errata/RHSA-2019:3200', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14439', 'https://lists.apache.org/thread.html/34717424b4d08b74f65c09a083d6dd1cb0763f37a15d6de135998c1d@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.apache.org/thread.html/ee0a051428d2c719acfa297d0854a189ea5e284ef3ed491fa672f4be@%3Cdev.tomee.apache.org%3E', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://lists.fedoraproject.org/archives/list/[email protected]/message/TXRVXNRFHJSQWFHPRJQRI5UPMZ63B544/', 'https://github.com/FasterXML/jackson-databind/commit/ad418eeb974e357f2797aef64aa0e3ffaaa6125b', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://lists.apache.org/thread.html/5fc0e16b7af2590bf1e97c76c136291c4fdb244ee63c65c485c9a7a1@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/940b4c3fef002461b89a050935337056d4a036a65ef68e0bbd4621ef@%3Cdev.struts.apache.org%3E', 'https://lists.apache.org/thread.html/87e46591de8925f719664a845572d184027258c5a7af0a471b53c77b@%3Cdev.tomee.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/compare/jackson-databind-2.9.9.1...jackson-databind-2.9.9.2', 'https://github.com/advisories/GHSA-gwp4-hfv6-p7hw', 'https://security.netapp.com/advisory/ntap-20190814-0001/', 'https://www.debian.org/security/2019/dsa-4542', 'https://lists.apache.org/thread.html/3f99ae8dcdbd69438cb733d745ee3ad5e852068490719a66509b4592@%3Ccommits.cassandra.apache.org%3E', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://seclists.org/bugtraq/2019/Oct/6', 'https://lists.fedoraproject.org/archives/list/[email protected]/message/OVRZDN2T6AZ6DJCZJ3VSIQIVHBVMVWBL/', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://lists.apache.org/thread.html/5ecc333113b139429f4f05000d4aa2886974d4df3269c1dd990bb319@%3Cdev.tomee.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/issues/2389', 'https://lists.debian.org/debian-lts-announce/2019/08/msg00011.html', 'https://lists.apache.org/thread.html/0d4b630d9ee724aee50703397d9d1afa2b2befc9395ba7797d0ccea9@%3Cdev.tomee.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://lists.apache.org/thread.html/56c8042873595b8c863054c7bfccab4bf2c01c6f5abedae249d914b9@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/2d2a76440becb610b9a9cb49b15eac3934b02c2dbcaacde1000353e4@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E'} | null |
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://github.com/OpenMage/magento-lts/releases/tag/v20.0.13', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32758', 'https://github.com/advisories/GHSA-26rr-v2j2-25fh', 'https://github.com/OpenMage/magento-lts/releases/tag/v19.4.15', 'https://github.com/OpenMage/magento-lts/security/advisories/GHSA-26rr-v2j2-25fh', 'https://github.com/OpenMage/magento-lts/commit/b99307d00b59c4a226a1e3e4083f02cf2fc8fce7'} | null |
GHSA | GHSA-rvww-x6m4-4vc2 | Malicious Package in blubird | Version 3.5.0 of `blubird` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.
## Recommendation
Remove the package from your environment and verify whether your system is running the cryptocurrency miner. | null | 2021-09-30T22:00:24Z | 2020-09-11T21:12:39Z | CRITICAL | 9.8 | {'CWE-506'} | {'https://www.npmjs.com/advisories/921', 'https://github.com/advisories/GHSA-rvww-x6m4-4vc2'} | null |
GHSA | GHSA-6rxj-58jh-436r | Moderate severity vulnerability that affects org.apache.tomcat.embed:tomcat-embed-core | The URL pattern of "" (the empty string) which exactly maps to the context root was not correctly handled in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 when used as part of a security constraint definition. This caused the constraint to be ignored. It was, therefore, possible for unauthorised users to gain access to web application resources that should have been protected. Only security constraints with a URL pattern of the empty string were affected. | {'CVE-2018-1304'} | 2021-09-02T18:25:01Z | 2018-10-17T16:31:17Z | MODERATE | 5.9 | null | {'https://access.redhat.com/errata/RHSA-2018:0466', 'https://lists.apache.org/thread.html/845312a10aabbe2c499fca94003881d2c79fc993d85f34c1f5c77424@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/eb6efa8d59c45a7a9eff94c4b925467d3b3fec8ba7697f3daa314b04@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/r48c1444845fe15a823e1374674bfc297d5008a5453788099ea14caf0@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/r6ccee4e849bc77df0840c7f853f6bd09d426f6741247da2b7429d5d9@%3Cdev.tomcat.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20180706-0001/', 'https://lists.apache.org/thread.html/3d19773b4cf0377db62d1e9328bf9160bf1819f04f988315086931d7@%3Cdev.tomcat.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2018:1450', 'https://access.redhat.com/errata/RHSA-2018:1451', 'https://lists.apache.org/thread.html/343558d982879bf88ec20dbf707f8c11255f8e219e81d45c4f8d0551@%3Cdev.tomcat.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00044.html', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://github.com/advisories/GHSA-6rxj-58jh-436r', 'https://lists.apache.org/thread.html/1dd0a59c1295cc08ce4c9e7edae5ad2268acc9ba55adcefa0532e5ba@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/b1d7e2425d6fd2cebed40d318f9365b44546077e10949b01b1f8a0fb@%3Cannounce.tomcat.apache.org%3E', 'http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html', 'http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html', 'http://www.securitytracker.com/id/1040427', 'https://lists.debian.org/debian-lts-announce/2018/06/msg00008.html', 'https://lists.apache.org/thread.html/b5e3f51d28cd5d9b1809f56594f2cf63dcd6a90429e16ea9f83bbedc@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/5c0e00fd31efc11e147bf99d0f03c00a734447d3b131ab0818644cdb@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/6af47120905aa7d8fe12f42e8ff2284fb338ba141d3b77b8c7cb61b3@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/88855876c33f2f9c532ffb75bfee570ccf0b17ffa77493745af9a17a@%3Cdev.tomcat.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2018:0465', 'https://access.redhat.com/errata/RHSA-2018:2939', 'https://lists.apache.org/thread.html/raba0fabaf4d56d4325ab2aca8814f0b30a237ab83d8106b115ee279a@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/e85e83e9954f169bbb77b44baae5a33d8de878df557bb32b7f793661@%3Cdev.tomcat.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2018/03/msg00004.html', 'https://access.redhat.com/errata/RHSA-2019:2205', 'https://lists.apache.org/thread.html/r9136ff5b13e4f1941360b5a309efee2c114a14855578c3a2cbe5d19c@%3Cdev.tomcat.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2018:1448', 'https://lists.apache.org/thread.html/r3bbb800a816d0a51eccc5a228c58736960a9fffafa581a225834d97d@%3Cdev.tomcat.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2018:1447', 'https://access.redhat.com/errata/RHSA-2018:1449', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://lists.apache.org/thread.html/388a323769f1dff84c9ec905455aa73fbcb20338e3c7eb131457f708@%3Cdev.tomcat.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2018:1320', 'http://www.securityfocus.com/bid/103170', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1304', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://www.debian.org/security/2018/dsa-4281', 'https://usn.ubuntu.com/3665-1/'} | null |
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://github.com/bpmn-io/min-dash/blob/c4d579c0eb2ed0739592111c3906b198921d3f52/lib/object.js%23L32', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2342127', 'https://github.com/bpmn-io/min-dash/pull/21', 'https://snyk.io/vuln/SNYK-JS-MINDASH-2340605', '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'} | null |
GHSA | GHSA-2xwv-3cc9-fp7c | Sensitive Data Exposure in seneca | Versions of `seneca` prior to 3.9.0 are vulnerable to Sensitive Data Exposure. When a process using the package crashes all environment variables are printed. This may leak sensitive data such as access keys, especially given scenarios when log-monitoring systems store the error output.
## Recommendation
Upgrade to version 3.9.0 or later. | {'CVE-2019-5483'} | 2021-01-08T20:41:17Z | 2019-09-11T23:07:57Z | LOW | 0 | {'CWE-209'} | {'https://github.com/nodejs/security-wg/blob/master/vuln/npm/501.json', 'https://github.com/advisories/GHSA-2xwv-3cc9-fp7c', 'https://nvd.nist.gov/vuln/detail/CVE-2019-5483', 'https://www.npmjs.com/advisories/1155', 'https://hackerone.com/reports/526258'} | null |
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/security/advisories/GHSA-7r96-8g3x-g36m', '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/commit/a121b34a45e289d775c62e58841522891dee686b'} | null |
GHSA | GHSA-65p8-3hm4-h9h8 | Denial of Service in rgb2hex | All versions of `rgb2hex` are vulnerable to Regular Expression Denial of Service (ReDoS) when an attacker can pass in a specially crafted invalid color value.
## Recommendation
Update to version 0.1.6 or later. | null | 2021-08-17T21:30:46Z | 2019-08-23T00:04:48Z | MODERATE | 6.5 | {'CWE-400'} | {'https://hackerone.com/reports/319629', 'https://snyk.io/vuln/npm:rgb2hex:20180429', 'https://www.npmjs.com/advisories/647', 'https://github.com/advisories/GHSA-65p8-3hm4-h9h8', 'https://github.com/christian-bromann/rgb2hex/blob/v0.1.0/index.js#L25', 'https://nodesecurity.io/advisories/647'} | null |
GHSA | GHSA-45p7-c959-rgcm | Process crashes when the cell used as DepGroup is not alive | ### Impact
It's easy to create a malign transaction which uses the dead cell as the DepGroup in the DepCells. The transaction can crash all the receiving nodes. | null | 2022-04-19T19:02:43Z | 2021-08-25T21:01:18Z | CRITICAL | 0 | null | {'https://github.com/nervosnetwork/ckb/security/advisories/GHSA-45p7-c959-rgcm', 'https://github.com/advisories/GHSA-45p7-c959-rgcm'} | null |
GHSA | GHSA-c69w-jj56-834w | Improper Certificate Validation and Improper Validation of Certificate with Host Mismatch in Apache Sling Commons Messaging Mail | Apache Sling Commons Messaging Mail provides a simple layer on top of JavaMail/Jakarta Mail for OSGi to send mails via SMTPS. To reduce the risk of "man in the middle" attacks additional server identity checks must be performed when accessing mail servers. For compatibility reasons these additional checks are disabled by default in JavaMail/Jakarta Mail. The SimpleMailService in Apache Sling Commons Messaging Mail 1.0 lacks an option to enable these checks for the shared mail session. A user could enable these checks nevertheless by accessing the session via the message created by SimpleMessageBuilder and setting the property mail.smtps.ssl.checkserveridentity to true. Apache Sling Commons Messaging Mail 2.0 adds support for enabling server identity checks and these checks are enabled by default. - https://javaee.github.io/javamail/docs/SSLNOTES.txt - https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html - https://github.com/eclipse-ee4j/mail/issues/429 | {'CVE-2021-44549'} | 2022-01-04T19:09:34Z | 2021-12-16T14:12:49Z | HIGH | 7.4 | {'CWE-297', 'CWE-295'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-44549', 'https://lists.apache.org/thread/l8p9h2bqvkj6rhv4w8kzctb817415b7f', 'https://github.com/advisories/GHSA-c69w-jj56-834w', 'https://javaee.github.io/javamail/docs/SSLNOTES.txt', 'https://github.com/eclipse-ee4j/mail/issues/429', 'https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html'} | null |
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/commit/2be2cdf3a123e231b16f766aa0e27d56b4606535', 'https://github.com/advisories/GHSA-xm2v-8rrw-w9pm', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xm2v-8rrw-w9pm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29525'} | null |
GHSA | GHSA-6q48-vjq2-mwcj | Command Injection in umount | All versions of `umount ` are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `umount` function . This may allow attackers to execute arbitrary code in the system if the `device` value passed to the function is user-controlled.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available. | {'CVE-2020-7628'} | 2021-07-28T22:37:18Z | 2020-06-10T20:28:03Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://www.npmjs.com/advisories/1512', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7628', 'https://snyk.io/vuln/SNYK-JS-UMOUNT-564265', 'https://github.com/advisories/GHSA-6q48-vjq2-mwcj'} | null |
GHSA | GHSA-p28m-34f6-967q | High severity vulnerability that affects pyopenssl | Python Cryptographic Authority pyopenssl version prior to version 17.5.0 contains a CWE-416: Use After Free vulnerability in X509 object handling that can result in Use after free can lead to possible denial of service or remote code execution.. This attack appear to be exploitable via Depends on the calling application and if it retains a reference to the memory.. This vulnerability appears to have been fixed in 17.5.0. | {'CVE-2018-1000807'} | 2021-08-31T21:16:25Z | 2018-10-10T16:10:38Z | HIGH | 8.1 | {'CWE-416'} | {'https://github.com/advisories/GHSA-p28m-34f6-967q', 'https://github.com/pyca/pyopenssl/pull/723', 'https://access.redhat.com/errata/RHSA-2019:0085', 'http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00014.html', 'https://usn.ubuntu.com/3813-1/', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000807'} | null |
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://github.com/microweber/microweber/commit/955471c27e671c49e4b012e3b120b004082ac3f7', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0954', 'https://github.com/advisories/GHSA-8c76-mxv5-w4g8'} | null |
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/security/advisories/GHSA-x5cp-9pcf-pp3h', 'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://github.com/advisories/GHSA-x5cp-9pcf-pp3h'} | null |
GHSA | GHSA-7x9j-7223-rg5m | High severity vulnerability that affects commons-fileupload:commons-fileupload | Apache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution | {'CVE-2016-1000031'} | 2021-10-21T21:32:11Z | 2018-12-21T17:51:51Z | CRITICAL | 9.8 | {'CWE-284'} | {'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451@%3Csolr-user.lucene.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://www.tenable.com/security/research/tra-2016-23', 'https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'http://www.securityfocus.com/bid/93604', 'http://www.zerodayinitiative.com/advisories/ZDI-16-570/', 'https://security.netapp.com/advisory/ntap-20190212-0001/', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html', 'https://issues.apache.org/jira/browse/FILEUPLOAD-279', 'https://www.tenable.com/security/research/tra-2016-12', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000031', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://issues.apache.org/jira/browse/WW-4812', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/advisories/GHSA-7x9j-7223-rg5m', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://www.tenable.com/security/research/tra-2016-30', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html', 'https://lists.apache.org/thread.html/d66657323fd25e437face5e84899c8ca404ccd187e81c3f2fa8b6080@%3Cannounce.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00036.html'} | null |
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://github.com/tensorflow/tensorflow/commit/49f73c55d56edffebde4bca4a407ad69c1cae433', 'https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2018-001.md', 'https://github.com/advisories/GHSA-h98h-8mxr-m8gx', 'https://nvd.nist.gov/vuln/detail/CVE-2018-21233'} | null |
GHSA | GHSA-ppqp-78xx-3r38 | Out of bounds write in calamine | An issue was discovered in the calamine crate before 0.17.0 for Rust. It allows attackers to overwrite heap-memory locations because Vec::set_len is used without proper memory claiming, and this uninitialized memory is used for a user-provided Read operation, as demonstrated by Sectors::get. | {'CVE-2021-26951'} | 2022-04-26T18:11:55Z | 2021-08-25T20:53:25Z | CRITICAL | 9.8 | {'CWE-787'} | {'https://github.com/tafia/calamine/issues/199', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26951', 'https://github.com/advisories/GHSA-ppqp-78xx-3r38', 'https://rustsec.org/advisories/RUSTSEC-2021-0015.html'} | null |
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 |
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/advisories/GHSA-545v-42p7-98fq', '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'} | null |
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://nvd.nist.gov/vuln/detail/CVE-2021-40823', 'https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9', 'https://matrix.org/blog/2021/09/13/vulnerability-disclosure-key-sharing', 'https://github.com/matrix-org/matrix-js-sdk/releases/tag/v12.4.1', 'https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-23cm-x6j7-6hq3', 'https://github.com/advisories/GHSA-23cm-x6j7-6hq3'} | null |
GHSA | GHSA-mvjj-gqq2-p4hw | Cross-Site Scripting in react-dom | Affected versions of `react-dom` are vulnerable to Cross-Site Scripting (XSS). The package fails to validate attribute names in HTML tags which may lead to Cross-Site Scripting in specific scenarios. This may allow attackers to execute arbitrary JavaScript in the victim's browser. To be affected by this vulnerability, the application needs to:
- be a server-side React app
- be rendered to HTML using `ReactDOMServer`
- include an attribute name from user input in an HTML tag
## Recommendation
If you are using `react-dom` 16.0.x, upgrade to 16.0.1 or later.
If you are using `react-dom` 16.1.x, upgrade to 16.1.2 or later.
If you are using `react-dom` 16.2.x, upgrade to 16.2.1 or later.
If you are using `react-dom` 16.3.x, upgrade to 16.3.3 or later.
If you are using `react-dom` 16.4.x, upgrade to 16.4.2 or later. | {'CVE-2018-6341'} | 2021-01-08T18:26:02Z | 2019-01-04T19:05:35Z | LOW | 0 | {'CWE-79'} | {'https://snyk.io/vuln/npm:react-dom:20180802', 'https://www.npmjs.com/advisories/1421', 'https://github.com/advisories/GHSA-mvjj-gqq2-p4hw', 'https://reactjs.org/blog/2018/08/01/react-v-16-4-2.html', 'https://twitter.com/reactjs/status/1024745321987887104', 'https://nvd.nist.gov/vuln/detail/CVE-2018-6341'} | null |
GHSA | GHSA-qpjr-ch72-2qq4 | Use after free in portaudio-rs | An issue was discovered in the portaudio-rs crate through 0.3.1 for Rust. There is a use-after-free with resultant arbitrary code execution because of a lack of unwind safety in stream_callback and stream_finished_callback. | {'CVE-2019-16881'} | 2021-08-25T20:45:17Z | 2021-08-25T20:45:17Z | CRITICAL | 9.8 | {'CWE-416'} | {'https://github.com/advisories/GHSA-qpjr-ch72-2qq4', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16881', 'https://rustsec.org/advisories/RUSTSEC-2019-0022.html', 'https://github.com/mvdnes/portaudio-rs/issues/20'} | null |
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://nvd.nist.gov/vuln/detail/CVE-2020-8929', 'https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r', 'https://github.com/advisories/GHSA-g5vf-v6wf-7w2r', 'https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899'} | null |
GHSA | GHSA-jqqr-c2r2-9cvr | Improper Certificate Validation in security-framework | An issue was discovered in the security-framework crate before 0.1.12 for Rust. Hostname verification for certificates does not occur if ClientBuilder uses custom root certificates. | {'CVE-2017-18588'} | 2021-08-25T20:42:59Z | 2021-08-25T20:42:59Z | MODERATE | 5.3 | {'CWE-295'} | {'https://github.com/advisories/GHSA-jqqr-c2r2-9cvr', 'https://github.com/sfackler/rust-security-framework/pull/27', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18588', 'https://rustsec.org/advisories/RUSTSEC-2017-0003.html'} | null |
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://huntr.dev/bounties/62408fa4-2c16-4fcd-8b34-41fcdccb779e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4049', 'https://github.com/livehelperchat/livehelperchat/commit/e7fe1aa6a087d4d21b2e8a0dadd2e08f42acbb57', 'https://github.com/advisories/GHSA-h86j-6h6m-qjqw'} | null |
GHSA | GHSA-432j-4fw9-2g6f | Downloads Resources over HTTP in libsbml | Affected versions of `libsbml` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `libsbml`.
## Recommendation
No patch is currently available for this vulnerability, and the package has not seen an update since 2013.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees. | {'CVE-2016-10668'} | 2021-01-08T19:57:40Z | 2019-02-18T23:44:33Z | HIGH | 0 | {'CWE-311'} | {'https://www.npmjs.com/advisories/272', 'https://nodesecurity.io/advisories/272', 'https://github.com/advisories/GHSA-432j-4fw9-2g6f', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10668'} | null |
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/[email protected]/message/PECHIY2XLWUH2WLCNPDGNFMPHPRPCEDZ/', 'https://github.com/twigphp/Twig/security/advisories/GHSA-5mv2-rx3q-4w2v', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23614', 'https://lists.fedoraproject.org/archives/list/[email protected]/message/SIGZCFSYLPP7UVJ4E4NLHSOQSKYNXSAD/', 'https://github.com/twigphp/Twig/commit/2eb33080558611201b55079d07ac88f207b466d5', 'https://lists.fedoraproject.org/archives/list/[email protected]/message/I2PVV5DUTRUECTIHMTWRI5Z7DVNYQ2YO/', 'https://github.com/twigphp/Twig/commit/22b9dc3c03ee66d7e21d9ed2ca76052b134cb9e9', 'https://github.com/advisories/GHSA-5mv2-rx3q-4w2v', 'https://lists.fedoraproject.org/archives/list/[email protected]/message/OTN4273U4RHVIXED64T7DSMJ3VYTPRE7/', 'https://www.debian.org/security/2022/dsa-5107'} | null |
GHSA | GHSA-943p-xc6m-c6gr | Rejected CVE ID | ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2018-7576,
CVE-2018-21233. Reason: this candidate was intended for one issue, but the
description and references inadvertently combined multiple issues. Notes:
All CVE users should consult CVE-2018-7576 and CVE-2018-21233 to determine
which ID is appropriate. All references and descriptions in this candidate
have been removed to prevent accidental usage. | {'CVE-2018-7574'} | 2021-12-03T14:34:42Z | 2019-04-30T15:37:27Z | HIGH | 0 | null | {'https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2018-001.md', 'https://nvd.nist.gov/vuln/detail/CVE-2018-7574', 'https://github.com/advisories/GHSA-943p-xc6m-c6gr'} | null |
GHSA | GHSA-p639-xxv5-j383 | Moderate severity vulnerability that affects org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service | In Apache Hive 2.1.0 to 2.3.2, when 'COPY FROM FTP' statement is run using HPL/SQL extension to Hive, a compromised/malicious FTP server can cause the file to be written to an arbitrary location on the cluster where the command is run from. This is because FTP client code in HPL/SQL does not verify the destination location of the downloaded file. This does not affect hive cli user and hiveserver2 user as hplsql is a separate command line script and needs to be invoked differently. | {'CVE-2018-1315'} | 2021-09-15T21:30:19Z | 2018-11-21T22:24:08Z | LOW | 3.7 | {'CWE-732'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1315', 'https://lists.apache.org/thread.html/d5da94ef60312c01a8d2348466680d1b5fb70702c71a3e84e94f7933@%3Cdev.hive.apache.org%3E', 'https://github.com/advisories/GHSA-p639-xxv5-j383'} | null |
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 |
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://nvd.nist.gov/vuln/detail/CVE-2021-29513', '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'} | null |
GHSA | GHSA-m6xf-fq7q-8743 | mutation XSS via whitelisted math or svg and raw tag in Bleach | ### Impact
A [mutation XSS](https://cure53.de/fp170.pdf) affects users calling `bleach.clean` with all of:
* the `svg` or `math` in the allowed/whitelisted tags
* an RCDATA tag (see below) in the allowed/whitelisted tags
* the keyword argument `strip=False`
### Patches
Users are encouraged to upgrade to bleach v3.1.2 or greater.
### Workarounds
* modify `bleach.clean` calls to use `strip=True`, or not whitelist `math` or `svg` tags and one or more of the following tags:
```
script
noscript
style
noframes
xmp
noembed
iframe
```
* A strong [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) without `unsafe-inline` and `unsafe-eval` [`script-src`s](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src)) will also help mitigate the risk.
### References
* https://bugzilla.mozilla.org/show_bug.cgi?id=1621692
* https://cure53.de/fp170.pdf
* https://nvd.nist.gov/vuln/detail/CVE-2020-6816
* https://www.checkmarx.com/blog/vulnerabilities-discovered-in-mozilla-bleach
### Credits
* Reported by [Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec group at Checkmarx
### For more information
If you have any questions or comments about this advisory:
* Open an issue at [https://github.com/mozilla/bleach/issues](https://github.com/mozilla/bleach/issues)
* Email us at [[email protected]](mailto:[email protected]) | {'CVE-2020-6816'} | 2021-04-05T20:33:35Z | 2020-03-24T15:06:32Z | MODERATE | 0 | {'CWE-79'} | {'https://advisory.checkmarx.net/advisory/CX-2020-4277', 'https://lists.fedoraproject.org/archives/list/[email protected]/message/EDQU2SZLZMSSACCBUBJ6NOSRNNBDYFW5/', 'https://www.checkmarx.com/blog/vulnerabilities-discovered-in-mozilla-bleach', 'https://github.com/advisories/GHSA-m6xf-fq7q-8743', 'https://nvd.nist.gov/vuln/detail/CVE-2020-6816', 'https://github.com/mozilla/bleach/releases/tag/v3.1.2', 'https://github.com/mozilla/bleach/security/advisories/GHSA-m6xf-fq7q-8743'} | null |
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://bugzilla.redhat.com/show_bug.cgi?id=1538763', 'https://github.com/advisories/GHSA-p55x-7x9v-q8m4', 'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e', 'https://github.com/miekg/dns/issues/627', 'https://nvd.nist.gov/vuln/detail/CVE-2017-15133', 'https://github.com/miekg/dns/pull/631'} | null |
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://snyk.io/vuln/SNYK-JS-TOTAL4-1130527', 'https://github.com/totaljs/framework4/blob/master/utils.js%23L5430-L5455', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23390', 'https://github.com/advisories/GHSA-g7mq-rfj2-25wq', 'https://github.com/totaljs/framework4/commit/8a72d8c20f38bbcac031a76a51238aa528f68821'} | null |
GHSA | GHSA-h9x2-5rm7-x4gm | Insecure Comparison in secure-compare | Versions of `secure-compare` prior to 3.0.1 are affected by a vulnerability that results in the package always returning true when comparing two strings of the same length, despite differences in the contents of those strings.
## Recommendation
Upgrade to version 3.0.1 or later. | {'CVE-2015-9238'} | 2021-01-08T20:54:52Z | 2019-06-03T17:28:23Z | HIGH | 0 | {'CWE-697'} | {'https://www.npmjs.com/advisories/50', 'https://github.com/advisories/GHSA-h9x2-5rm7-x4gm', 'https://nodesecurity.io/advisories/50', 'https://github.com/vdemedes/secure-compare/pull/1', 'https://nvd.nist.gov/vuln/detail/CVE-2015-9238'} | null |
GHSA | GHSA-5h9j-q6j2-253f | Unescaped exception messages in error responses in Jetty | In Eclipse Jetty versions 9.4.21.v20190926, 9.4.22.v20191022, and 9.4.23.v20191118, the generation of default unhandled Error response content (in text/html and text/json Content-Type) does not escape Exception messages in stacktraces included in error output. | {'CVE-2019-17632'} | 2021-06-15T17:23:28Z | 2019-12-02T18:13:28Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-17632', 'https://lists.fedoraproject.org/archives/list/[email protected]/message/SAITZ27GKPD2CCNHGT2VBT4VWIBUJJNS/', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/advisories/GHSA-5h9j-q6j2-253f', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://bugs.eclipse.org/bugs/show_bug.cgi?id=553443'} | null |
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://github.com/karma-runner/karma/commit/ff7edbb2ffbcdd69761bece86b7dc1ef0740508d', 'https://github.com/advisories/GHSA-rc3x-jf5g-xvc5', 'https://snyk.io/vuln/SNYK-JS-KARMA-2396325', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23495', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2412347'} | null |
GHSA | GHSA-32v7-ghpr-c8hg | Mishandling of format strings in ncurses | An issue was discovered in the ncurses crate for Rust. There are format string issues in printw functions because C format arguments are mishandled. | {'CVE-2019-15547'} | 2021-08-25T20:58:47Z | 2021-08-25T20:58:47Z | HIGH | 7.5 | {'CWE-134'} | {'https://github.com/advisories/GHSA-32v7-ghpr-c8hg', 'https://github.com/jeaye/ncurses-rs/issues/172', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15547', 'https://rustsec.org/advisories/RUSTSEC-2019-0006.html', 'https://github.com/RustSec/advisory-db/issues/106'} | null |
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://github.com/tensorflow/tensorflow/security/advisories/GHSA-h9px-9vqg-222h', 'https://github.com/tensorflow/tensorflow/commit/99085e8ff02c3763a0ec2263e44daec416f6a387', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29553'} | null |
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://github.com/baserproject/basercms/commit/7f4b905b90954e394ec10dd35bad2a5dec505371', 'https://github.com/baserproject/basercms/security/advisories/GHSA-cpxc-67rc-c775', 'https://basercms.net/security/20200827', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15154', 'https://github.com/advisories/GHSA-cpxc-67rc-c775'} | null |
GHSA | GHSA-h7qh-3h6f-w79p | Unexpected panic in multihash | An issue was discovered in the multihash crate before 0.11.3 for Rust. The from_slice parsing code can panic via unsanitized data from a network server. | {'CVE-2020-35909'} | 2021-08-25T20:49:41Z | 2021-08-25T20:49:41Z | HIGH | 7.5 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-35909', 'https://github.com/advisories/GHSA-h7qh-3h6f-w79p', 'https://rustsec.org/advisories/RUSTSEC-2020-0068.html', 'https://github.com/multiformats/rust-multihash/pull/72'} | null |
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://nvd.nist.gov/vuln/detail/CVE-2017-1000248', 'https://github.com/advisories/GHSA-2w67-526p-gm73', 'https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e'} | null |
GHSA | GHSA-pgf9-h69p-pcgf | High severity vulnerability that affects org.springframework:spring-core | Under some situations, the Spring Framework 4.2.0 to 4.2.1, 4.0.0 to 4.1.7, 3.2.0 to 3.2.14 and older unsupported versions is vulnerable to a Reflected File Download (RFD) attack. The attack involves a malicious user crafting a URL with a batch script extension that results in the response being downloaded rather than rendered and also includes some input reflected in the response. | {'CVE-2015-5211'} | 2021-09-16T17:30:16Z | 2018-10-17T20:29:33Z | HIGH | 8.6 | {'CWE-20'} | {'https://lists.debian.org/debian-lts-announce/2019/07/msg00012.html', 'https://pivotal.io/security/cve-2015-5211', 'https://github.com/advisories/GHSA-pgf9-h69p-pcgf', 'https://www.trustwave.com/Resources/SpiderLabs-Blog/Reflected-File-Download---A-New-Web-Attack-Vector/', 'https://nvd.nist.gov/vuln/detail/CVE-2015-5211'} | null |
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 [email protected] | null | 2020-01-08T03:10:44Z | 2020-01-08T03:10:44Z | HIGH | 0 | null | {'https://github.com/advisories/GHSA-769f-539v-f5jg', 'https://github.com/PrestaShop/gamification/commit/5044bda903a7ea9596c21faa2b9a42244763568c', 'https://build.prestashop.com/news/critical-security-vulnerability-in-prestashop-modules/', 'https://github.com/PrestaShop/gamification/security/advisories/GHSA-769f-539v-f5jg'} | null |
GHSA | GHSA-qq89-hq3f-393p | Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links | ### Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.
This logic was insufficient when extracting tar files that contained two directories and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. It led to bypassing node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.
The v3 branch of `node-tar` has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of `node-tar`. If this is not possible, a workaround is available below.
### Patches
6.1.9 || 5.0.10 || 4.4.18
### Workarounds
Users may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.
```js
const tar = require('tar')
tar.x({
file: 'archive.tgz',
filter: (file, entry) => {
if (entry.type === 'SymbolicLink') {
return false
} else {
return true
}
}
})
```
Users are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves.
#### Fix
The problem is addressed in the following ways, when comparing paths in the directory cache and path reservation systems:
1. The `String.normalize('NFKD')` method is used to first normalize all unicode to its maximally compatible and multi-code-point form.
2. All slashes are normalized to `/` on Windows systems (on posix systems, `\` is a valid filename character, and thus left intact).
3. When a symbolic link is encountered on Windows systems, the entire directory cache is cleared. Collisions related to use of 8.3 short names to replace directories with other (non-symlink) types of entries may make archives fail to extract properly, but will not result in arbitrary file writes.
| {'CVE-2021-37712'} | 2022-03-11T20:16:55Z | 2021-08-31T16:05:17Z | HIGH | 8.2 | {'CWE-59', 'CWE-22'} | {'https://www.npmjs.com/package/tar', 'https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p', 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf', 'https://github.com/advisories/GHSA-qq89-hq3f-393p', 'https://www.debian.org/security/2021/dsa-5008', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37712'} | null |
GHSA | GHSA-8336-mxp6-v5h9 | Moderate severity vulnerability that affects OPCFoundation.NetStandard.Opc.Ua | Failure to validate certificates in OPC Foundation UA Client Applications communicating without security allows attackers with control over a piece of network infrastructure to decrypt passwords. | {'CVE-2018-12087'} | 2021-06-11T15:34:21Z | 2018-10-16T19:51:18Z | MODERATE | 5.3 | {'CWE-295'} | {'https://github.com/advisories/GHSA-8336-mxp6-v5h9', 'https://opcfoundation-onlineapplications.org/faq/SecurityBulletins/OPC_Foundation_Security_Bulletin_CVE-2018-12087.pdf', 'https://nvd.nist.gov/vuln/detail/CVE-2018-12087'} | null |
GHSA | GHSA-xg59-m7wx-853q | Cross-site Scripting in node-red-dashboard | It is possible to inject JavaScript within node-red-dashboard versions prior to version 2.17.0 due to the ui_notification node accepting raw HTML by default. | {'CVE-2019-10756'} | 2021-08-18T22:03:53Z | 2019-10-25T19:41:24Z | MODERATE | 5.4 | {'CWE-79'} | {'https://snyk.io/vuln/SNYK-JS-NODEREDDASHBOARD-471939', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10756', 'https://github.com/advisories/GHSA-xg59-m7wx-853q'} | null |
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://huntr.dev/bounties/55fd06cd-9054-4d80-83be-eb5a454be78c', 'https://security.netapp.com/advisory/ntap-20220325-0006/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0686', 'https://github.com/advisories/GHSA-hgjh-723h-mx2j'} | null |
End of preview. Expand
in Data Studio
license: mit
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
- 25